Guest squidlr Posted November 23, 2010 Report Posted November 23, 2010 (edited) My lovely San Fran running FLB 2.2 Froyo crashed today. I was using the phone as normal and after about 30 seconds and several Force Close error messages were displayed from gmail and a few other programs, so I powered the phone off hoping to reboot it to solve the problem. Now, when I switch it back on: 1. It does not boot, stuck on green Android logo 2. Unable to boot into Clockwordmod recovery mode using volume keys. 3. Followed the guides on modaco for OSX and Ubuntu, unable to reinstall clockworkmod - I'm getting the <waiting for device> message, with no end to it. 4. 'fastboot devices' command lists nothing, so I guess theres a problem with USB. Cable seems fine as it supplies power to the phone, and has been working with no problems before today It does not appear to show up as a USB device. I doubt it's a driver problem, as I've tried both Linux and OS X to try and reinstall clockword mod. Is my phone bricked? I've searched threads but seen no solution. Any help appreciated! Gonna to be a sickner if it's bricked, as Orange obviously won't replace it with Android logo staring at them when they test it out! Edited November 23, 2010 by squidlr
Guest squidlr Posted November 23, 2010 Report Posted November 23, 2010 Have you tried "adb devices" ? Thx, tried it and terminal reported 'List of Devices' and a blank space. I then tried 'adb shell' and this reports 'device not found'
Guest JCPren Posted November 23, 2010 Report Posted November 23, 2010 Orange obviously won't replace it with Android logo staring at them when they test it out! They might. Even an unmodified San Francisco displays the Android logo on startup, and it sounds like it would be difficult for them to find out what ROM's on it, since the USB connection isn't working. Besides, if you arrange a replacement by phone, I understand that a courier drops off your replacement at the same time as picking up the faulty handset. All you have to do is persuade them that it's faulty when you speak to them on the phone (and by the sounds of it, you'd be telling the truth).
Guest squidlr Posted November 23, 2010 Report Posted November 23, 2010 (edited) They might. Even an unmodified San Francisco displays the Android logo on startup, and it sounds like it would be difficult for them to find out what ROM's on it, since the USB connection isn't working. Besides, if you arrange a replacement by phone, I understand that a courier drops off your replacement at the same time as picking up the faulty handset. All you have to do is persuade them that it's faulty when you speak to them on the phone (and by the sounds of it, you'd be telling the truth). Hey, you're right! The Android logo is the 1st thing seen on boot! Totally forgot. Going to make a few phone calls tomorrow I think. Thx for the advice. Would be nice if I could avoid this and get it fixed through some tinkering. I wonder what happened that messed up my phone. Maybe it's linked to Titanium Pro. I installed it yesterday, backed up all my apps then emptied the dalvik cache. Who knows. *Update* New phone winging it's way from Orange Edited November 24, 2010 by squidlr
Recommended Posts
Please sign in to comment
You will be able to leave a comment after signing in
Sign In Now