Separate names with a comma.
Discussion in 'Android Hacks and Help' started by Sam, Apr 14, 2010.
How do you do that?
Two things - when I first tried this, it said "fail" every time, now my phone says battery too low to boot. If I just plug it in and the white light comes on, does that mean it's charging?
This is the best and most useful post that I have ever came across. One thing that I have experienced, is that if you don't have the USB drivers installed correctly to 2.0, it will fail when it tries to "Phone: Waiting for re-enumeration". Then it gets a 0x703e error message. After updating my laptop drivers to make it 2.0 - worked like a charm.
I flashed the the 2.0.1 sbf like two hours ago and I haven't received the OTA update notification for 2.1/2.2...what the hell?
When I did it before in the past using the 2.0.1 sbf, I'd get an OTA notification for 2.1 almost immediately after booting my phone for the first time... now I don't..
Go into dialer and type this
*#*# CHECKIN #*#* this checks in and see's if there's an update! or go into settings and check for update.
And now for my question. This entire thread. If I do this, I can still power on, and mess around with the phone right. I'm trying to fix a borked Droid but I'm not a verizon customer. So will i be stuck trying to activate it. or will it still work, just no network data?
RSD lite FAIL
I'm trying to get my droid 1 back to stock and I get all the way to when RSD lite says "waiting for re-enumeration", and it stays there for a little while and then says failed flashing process and has FAIL in the result column. I've been looking for help for this on droid forums and I can't seem to find a solution. Any suggestions?
Thanks very much to anyone who replies
This is quoted from above.... Always a good idea to read thru the thread...
"This is the best and most useful post that I have ever came across. One thing that I have experienced, is that if you don't have the USB drivers installed correctly to 2.0, it will fail when it tries to "Phone: Waiting for re-enumeration". Then it gets a 0x703e error message. After updating my laptop drivers to make it 2.0 - worked like a charm"
OMFG so i did 2.2 sbf to unroot and my RSD took forever then said FAIL!!! said that is was not flashed and then my phone said completed...booted back up and perfect! So people if you try this and it says fail, then you still may have a chance.
Where's the 2.2 sbf
So my screen broke and i flashed 2.2 stock to unroot it. RSD said everything was fine and then said to manually reboot the phone. Well i turn on the phone and i cant tell if it worked since i cant get screen capture to recognize the phone in sdk.
Should i just try again? I didnt get a fail message, just a manually reboot phone message.
OK, so I finally decided to try this as I was able to get CM6 to boot once, and now I'm back to my old boot-loop problem.
I ran the 2.0.1 sbf file and it got all the way to where it's supposed to boot and I STILL get a bootloop on the Red eye. RDS Lite does say Executed 100% but the result column still says in Process. and it says to Please manually power up the phone. That is because it's boot-looping. I think there might be a hardware problem.
I just dont understand why after wiping, installing SPRecovery and flashing CM6 I was able to get it to actually boot once and work fine, and after i rebooted I'm boot-looping again. and now it's still doing it after a full sbf redo.. I think that was a lucky boot and the phones just messed up inside. but idk