Related
Hey guys, I have done a ton of reading and researching about modding android phones since recently migrating from iPhones. I got a Droid1 and did some basic root/rom/overclock etc.
I just got a DX a few days ago and right away decided to start with the modding. Anyways, In a nutshell I attempted to go about the ROMing process in a similar manner to my Droid1 and ended up going to the Rubix1.6 ROM without ever backing up my stock OS.
I wanted to be able to jump back and forth to a blurless/blurred ROM to get a good feel for what I want outta it but am not sure how I should go about getting the stock OS stuff back on. I've read up about the SBF, but is that the only way to go?
Thanx for any help guys, greatly appreciated.
Sam G
Sadly, yes. Since you didn't back up before you started you will have to SBF to get a stock ROM. Be sure to make a nandroid of your modded ROM, SBF, root, backup, then flash back and forth.
Now as far as a Nandroid backup you mean just a backup through clockwork recovery correct?
CBX133 said:
Now as far as a Nandroid backup you mean just a backup through clockwork recovery correct?
Click to expand...
Click to collapse
yea. a nandroid backup is the backup you create in cw recovery
Ok So I did it and restored nicely after doing a wipe after.. Now I can't ACTIVATE my phone. Any ideas why it would mess with the activation. When I hit activate and then 1 it just says to enter the number.. SHIIT
CBX133 said:
Ok So I did it and restored nicely after doing a wipe after.. Now I can't ACTIVATE my phone. Any ideas why it would mess with the activation. When I hit activate and then 1 it just says to enter the number.. SHIIT
Click to expand...
Click to collapse
the activation system has been down for a few hours now. You can try *22899. Or do it online here http://www.verizonwireless.com/b2c/activate. Or just call the 1800 number and do it with a csr.
Ok, I'm hoping it is just a bad coincidence that the activation server is down. I'll pack it up and try again in the morning. If that's what it is then I am all set otherwise. Thanx!
CBX133 said:
Ok, I'm hoping it is just a bad coincidence that the activation server is down. I'll pack it up and try again in the morning. If that's what it is then I am all set otherwise. Thanx!
Click to expand...
Click to collapse
of course it's just a coincidence. flashing a rom or doing an sbf to your phone does not cause the verizon activation system to crash. lol. whenever you sbf your phone or do a factory reset, you have to do the *228 to reactivate. thats normal.
Just some info... when I wipe out my phone and boot it up (skipping) activation it works already. Found this out by wiping my phone, booting it up, and I got a text message immediately. Lol.
CBX133 said:
Hey guys, I have done a ton of reading and researching about modding android phones since recently migrating from iPhones. I got a Droid1 and did some basic root/rom/overclock etc.
I just got a DX a few days ago and right away decided to start with the modding. Anyways, In a nutshell I attempted to go about the ROMing process in a similar manner to my Droid1 and ended up going to the Rubix1.6 ROM without ever backing up my stock OS.
I wanted to be able to jump back and forth to a blurless/blurred ROM to get a good feel for what I want outta it but am not sure how I should go about getting the stock OS stuff back on. I've read up about the SBF, but is that the only way to go?
Thanx for any help guys, greatly appreciated.
Sam G
Click to expand...
Click to collapse
'
Just consider your SBF your 2.3.15 backup copy. It's not a pain. It's easy and it should be a tool in every modder's arsenal. IMO, people who don't know how to sbf, are destined to have to anyway, eventually, if they mod enough. The only thing is that when they have to, they won't know how and will kinda panic. I say be ready to sbf before you root, so you're ready when trouble comes.
Me? I love modifications and will sometimes go too far or make a mistake at 2 am, when I really should be sleeping instead and I wind up bricked. No problem. Just SBF and I'm on my way. If you need further info or how to's feel free to ask.
Steven
Steven58 said:
'
Just consider your SBF your 2.3.15 backup copy. It's not a pain. It's easy and it should be a tool in every modder's arsenal. IMO, people who don't know how to sbf, are destined to have to anyway, eventually, if they mod enough. The only thing is that when they have to, they won't know how and will kinda panic. I say be ready to sbf before you root, so you're ready when trouble comes.
Me? I love modifications and will sometimes go too far or make a mistake at 2 am, when I really should be sleeping instead and I wind up bricked. No problem. Just SBF and I'm on my way. If you need further info or how to's feel free to ask.
Steven
Click to expand...
Click to collapse
Hey just got my replacement x today already rooted and have fly x on it. The sbf back up category is my only weakness. When my phone goes belly up im kinda lost. Do you have or know of any threads walktbroughs on bow to.bring a bricked phone back to life. Im putts replacements for this year through asurion and will have to do this if im bricked again. I was stuck on the tranquility logo couldn't get out. Thanx.
Sent from my DROIDX using Tapatalk
illcat2000 said:
Hey just got my replacement x today already rooted and have fly x on it. The sbf back up category is my only weakness. When my phone goes belly up im kinda lost. Do you have or know of any threads walktbroughs on bow to.bring a bricked phone back to life. Im putts replacements for this year through asurion and will have to do this if im bricked again. I was stuck on the tranquility logo couldn't get out. Thanx.
Sent from my DROIDX using Tapatalk
Click to expand...
Click to collapse
Here's what I used to guide me through the sbf...
Here is a link to the guide I used. It is for the 2.1 SBF though.
http://www.intomobile.com/2010/09/21/droid-x-stock-android/
Here are the instructions with my modifications for 2.2...
IMPORTANT!!! - the directions are for restoring 2.1 so you do not do some of the steps! They were the best I could find. I followed them except for things that did not apply.
instructions:
1. First off, choose the right version of Motorola USB drivers for your computer and install them (32bit) (64bit)
2. Download & install RSD Lite 4.7 (download)
I did not use 4.7 as it is not current. I used 4.9
You will need to patch this after installing. There is an .ini file included in the folder that needs to be placed in your install directory. /Program Files/Motorola/RSD Lite
I used 4.9 and did not have to patch any files- the above step was unnecessary.
3. Download the Droid X Android 2.1 SBF file, which you can find here
of course I used the 2.2 SBF file here...
http://rootzwiki.com/
4. Unzip the SBF file to your desktop
i did not unzip mine to the desktop- i put it where i stash my android files- it made no difference.
5. Run RSD Lite, and click the “…” button, then find the SBF file that you just unzipped to your desktop and select it.
Starting here i followed the directions to the "t". Went through all the steps. !!!!!MAKE SURE YOU START WITH 100% BATTERY!!!!!! It takes a long time and if your phone dies during the process it is a nightmare.
6. Plug your Droid X into your computer and power it down
Go into the Bootloader (with phone off, hold the CAMERA button and VOLUME DOWN, then hit the POWER button)
After holding for 2-3 seconds, release the buttons and RSD Lite should recognize your Droid X
7. Click the start button to flash Android 2.1 to your phone.
of course we are flashing 2.2
8. When the flashing is complete, unplug your phone
The Droid X will likely not boot up all the way, so pull the battery out
Put the battery back into the phone and reboot into Recovery mode ( Hold the HOME button and press POWER until you get an exclamation mark. Release the HOME button and press the SEARCH button)
Using the VOLUME UP/DOWN buttons, navigate to “wipe data/ factory reset” option on the screen, and press the CAMERA button halfway down to execute.
When complete, choose to reboot your phone
9. It takes a while. Hope this helps. And I hope it goes smoothly. It was nerve racking for me. After you have finished the process you will not be rooted. Use the market app "Z4root" or which ever method you prefer.
good luck.
Click to expand...
Click to collapse
thepolishguy said:
Here's what I used to guide me through the sbf...
Click to expand...
Click to collapse
i really appreaciate the guide and quick response im going to try to save these for future refrence.
just tried this method for the experience on the droid i bricked. worked like a charm was a bit easier too. phone rebooted on its own. i wiped just to make sure since i need to send it back to vz i already got my replacement. but this definetly gives me a little more confidence knowing i can bring it back from the dead if i have to. thanks again.
detailed sbf restoration instructions
illcat2000 said:
Hey just got my replacement x today already rooted and have fly x on it. The sbf back up category is my only weakness. When my phone goes belly up im kinda lost. Do you have or know of any threads walktbroughs on bow to.bring a bricked phone back to life. Im putts replacements for this year through asurion and will have to do this if im bricked again. I was stuck on the tranquility logo couldn't get out. Thanx.
Sent from my DROIDX using Tapatalk
Click to expand...
Click to collapse
sure! from http://androidforums.com/droid-x-al...ing-custom-rom-theme-how-unbrick-droid-x.html
*my note: make sure you install moto dx drivers on your PC: http://www.motorola.com/consumers/v/index.jsp?vgnextoid=bda09ec8009a0210VgnVCM1000008806b00aRCRD
C. UnBRICKING INSTRUCTIONS:
HELP ME. Ima noob! I BRICKED MY PHONE!
1. go to Home and DL the leaked full OTA FROYO 2.2 .SBF file.
2. Download and install RSDLite v4.8 (it should be on Home if not, go Google it.)
3. If your phone is stuck on the load screen, pull the battery, wait a minute, push the battery back in and restart with the phone’s Boot Loader Mode (do this by pressing the red camera button + volume down + power button hold all of them in the order that I stated until your phone flashes briefly). Your phone should flash white and a Boot Loader menu will come up. Make sure there is at least 20 to 25 percent battery life remaining in order for the reformat of you phone to complete. If your phone dies in the middle of this process GOD HELP YOU.
4. Run the RSDLite File and connect your Droid X to your computer via USB.
5. Browse for the .SBF file you downloaded in step 1 and click “Start”, at which point the program should run and your phone will proceed to unbrick
6. EASY RIGHT?
7. Once unbricking you will have to go through reactivation of your phone. This is normal so just go through the steps you did when you first started.
8. GUESS WHAT? You made a backup of your previous customizations REMEMBER? If you don’t want to deal with the hassle of re-downloading your entire life onto your phone again follow the “ROOTING” instructions in Part A and redownload Bootstrap and reboot into recovery mode to RESTORE the backup you made by following steps 2-11 in Part B….except you won’t be going to “install from sdcard” you will going to “Backup and Restore” and “Restore from sdcard”.
HELP Please - Error running SBF in RSD Lite
First off, I'm a newbie, so please go easy on me if these are dumb questions. I get the following error while trying to run "VRZ_MB810_2.3.15_1FF_01.sbf" in RSD Lite 4.7 while in boot mode. I don't know what else to do. My phone won't work. Thank you for any advice you can give.
Failed flashing process. [Phone 0000]: Phone is not compatabile with multi-interlace interface super-file. (0x703B): Phone connected.
rossi28usa said:
First off, I'm a newbie, so please go easy on me if these are dumb questions. I get the following error while trying to run "VRZ_MB810_2.3.15_1FF_01.sbf" in RSD Lite 4.7 while in boot mode. I don't know what else to do. My phone won't work. Thank you for any advice you can give.
Failed flashing process. [Phone 0000]: Phone is not compatabile with multi-interlace interface super-file. (0x703B): Phone connected.
Click to expand...
Click to collapse
did you put the patched pst_flash.ini file in the rsdlite install directory?
I put that file in program files>motorola>rsd lite. I did it after installing the program if that matters. The zip file folder name was RSD Lite 4.7+Patch. Also, in RSD Lite in order for the program to recognize my droid x i had to select the "first come first serve device id mode" under the device id options in the config menu. Don't know if this matters, just trying to give as much info as possible. Thanks.
rossi28usa said:
I put that file in program files>motorola>rsd lite. I did it after installing the program if that matters. The zip file folder name was RSD Lite 4.7+Patch. Also, in RSD Lite in order for the program to recognize my droid x i had to select the "first come first serve device id mode" under the device id options in the config menu. Don't know if this matters, just trying to give as much info as possible. Thanks.
Click to expand...
Click to collapse
yea, you can only do it after installing the program. it has to be closed though when you do it and you have to overwrite existing file. if you did all that properly, then it may be a corrupted sbf. I would just install rsdlite 4.8 or 4.9 and retry. those dont require a patch.. if no workie, then redownload sbf.
rsd lite 4.8 is here http://www.multiupload.com/HL0ZAL9GK8
I can't remember the order I did it in so I'll re-install with the instructions you gave. Thank you! I'll report back.
Ooookay, so I'm really hoping I don't have a bricked phone here, but it isn't looking too good.
I have a Bell Legend and I decided to try the modified alpharev iso to S-OFF my phone. Using the counting method I managed to get through the first two steps just fine, but at step 3 my timing must have been off and the phone froze, not letting me hit fastboot. I kept trying, and waited another 20 minutes, but after it was obvious nothing would happen, I pulled the battery to start over.
I was able to fake-flash my way back into clockwork recovery and then restored a previous nandroid backup, but my phone simply would not boot back into the OS after the restore, it just hangs at the HTC logo indefinitely. I let it sit for over half an hour and still NOTHING.
Is my phone bricked? If not, is there anything I can do to fix this?
Oh, and if it helps, when the alpharev utility prompted me about whether I wanted to flash its custom clockworkmod recovery I said yes.. not sure if that was the right call.
And I never got to/through step 3 of the flash, and that's supposedly the only part of the process during which bricking the phone could occur, so I'm pretty lost on what's happening here, but I would really appreciate some help :S
If you are still able to turn it on I guess you haven't bricked your phone.
Btw your thread title is wrong, Alpharev never brick your phone. It is you as the user that brick it, you should know the risk (mentioned very clearly) and yet still attempt the procedure.
Sent from my Legend using Tapatalk
Maybe my memory is off or the procedure for Bell Legends are different, but aren't the 3rd step straight foreward? I mean no timing? Anyway I don't think your phone is bricked, unless you pulled the connection/battery after the procedure started flashing the bootloader.
Edit: I see that you never got to step 3 if I understand correctly. Maybe wiping and reflashing helps.
Sent from my Legend using XDA App
Just run the alpharev once more to try for step 3 again.. tried several times myself before getting the timing right.. as yes as mentioned.. Alpharev never brick phones.. Users does..
Sent from my Legend using XDA App
fatthumb said:
If you are still able to turn it on I guess you haven't bricked your phone.
Btw your thread title is wrong, Alpharev never brick your phone. It is you as the user that brick it, you should know the risk (mentioned very clearly) and yet still attempt the procedure.
Sent from my Legend using Tapatalk
Click to expand...
Click to collapse
Yes, I'm very much aware that it was my own silly actions that led to my predicament and I in no way blame the alpharev team, they've done a great job. I just made that the thread title so that people would be aware of what I was doing before I messed up my phone, but again, totally my fault, not alpharev's
Anyways, I've solved the problem, probably won't try to S-OFF my phone again until I do some more reading.
MaBlo said:
Maybe my memory is off or the procedure for Bell Legends are different, but aren't the 3rd step straight foreward? I mean no timing? Anyway I don't think your phone is bricked, unless you pulled the connection/battery after the procedure started flashing the bootloader.
Edit: I see that you never got to step 3 if I understand correctly. Maybe wiping and reflashing helps.
Sent from my Legend using XDA App
Click to expand...
Click to collapse
No, your memory is spot on, I'm mistaken. I meant steps 1 and 2, I guess I didn't make it to step 3. If I messed up at step 3 only THEN would I have been completely screwed. Fixed the problem, I must have had a corrupt nandroid backup. Restored an earlier backup and now the phone is running fine. Premature panicking!
Hey all there,
i just bought for some cheap money a milestone 2 on the bay with bootloop problems.
it startsup like this:
just power on with the power button:
red m logo, after some seconds it turns for about a half second to a black screen, again red m logo, and again and again and again
enter the bootloader works fine - 70.13
enter the system recovery works on charger, wiping out didn't help
flashing with rsd lite worked, but didn't change the situation with the bootloop. even after flashing, and wipe out after that.
i'm using windows 7 32bit and x64 on another computer in combination with rsd-lite 5.6
with rsd-lite 4.9 or earlier my device isn't recognized. admin and compitibility is on at all versions of rsd-lite.
anone an idea how to get this stone working again?
i'm a little confused, cause i saw so many posts, of people getting the stone back after flashing with rsd...hmm any help is pleased
greetz
Download rom GingerBread of UK
http://www.multiupload.com/TUZHXCGLMZ
Flash with RSD Lite 5.6... reboot
make wipes (POWER and X....... Vol + and Vol -)... reboot
has to boot normally ...
Just tried several versions of firmware. nothing did work.
i'm thinking about getting the 70.13 bootloader file and flash the bootloader once more.
or give it a try and flash the phone with an update.zip over recovery mode.
but first problem is: i don't have the booloader and the only mirror was megaload, at second i don't have any oem update.zip files. well i will look forward. can't understand why the phone is still looping.
would be happy about any other good suggestions.
greetz
Bootloader 70.13
thanks a lot for the bootloader, but did not help. still bootloop.
now i tried all german, DACH, UK GB fimware.
always rebooting and wiping.
Tha phone is still in bootloop.
May be an OEM update.zip could help. i still got access to the recovery mode.
is it possible to boot from the recovery mode into openrecovery, when the bootloader is original? don't think so, but will try that now.
still happy about an help here.
greetz
MKSilver said:
thanks a lot for the bootloader, but did not help. still bootloop.
now i tried all german, DACH, UK GB fimware.
always rebooting and wiping.
Tha phone is still in bootloop.
May be an OEM update.zip could help. i still got access to the recovery mode.
is it possible to boot from the recovery mode into openrecovery, when the bootloader is original? don't think so, but will try that now.
still happy about an help here.
greetz
Click to expand...
Click to collapse
Don't use a 2 ou 2.2 android..I think it's on GB so you can't downgrade..
Charge your battery to 100%
Folow the step here with a 2.3.4 SBF take here
Have a nice day.
Hey all there,
i already tried to flash GB 2.3.4 Firmware for: Germany, DACH, UK - didn't work out.
of course i did a wipe after installing.
also i tried a rebuilt by renaming CG66.img into CG37img - didn't work out.
just saw, that when i rebuilt the firmware after changing cg66.img to cg37.img, the cg37.img file doesn't appear in the new built SBF.
any reason for that? hmm...
while depacking and rebuilt a SBF i saw, that the RAMDLD.img (ramdownloader) in the 2.3.4 GB DE retail SBF is in version 70.12. i'm no expert in built SBF files, just did this the first time, but could this have an incompatibility with the 70.13 bootloader?
well cause the phone was quite cheap, i will go on trying. may be some more of you guys have any ideas.
the standing now is:
reflash 70.13 bootloader - didn't work out,
flash any 2.3.4 GB SBF and wiping out data after flash - didn't work out
flash update.zip from recovery mode - haven't tried yet - need update.zip file or instruction how to built one.
the last point is my next step i think. i will now go reading how to get this manage.
any help is welcome!
greetz
Okay just learned, that flashing an update.zip with system recovery, doesn't erase any data on the phone, so will look forward, trying flash the phone with sbf under linux live cd.
may be this will help.
does anyone of you know some hardware testing tools for the milestone 2?
to test the ram/rom hardware...
i'm starting to think, that some of the hardware chips may be damaged.
hmm i always thought, that it is not possible to brick a stone with original bootloader/rom-image/firmware. just starting to learn, that it is possible although.
any help is welcome guys! my ideas are going to end.
greetz
Got still no luck and tried to flash it with sfb about 16 times now. RSD-Lite tells me it was everything okay, but still bootloop.
Any good ideas?
Greetz
You have no real idea of the phones history, so you may have to accept the possibilty that it could be a hardware issue. Perhaps it has taken some water damage (the indicators do not always end up going off btw - I fell into a pool fully clothed and the nokia i had at the time wouldn't ever recognize a sim again, yet no water damage indicators get wet somehow . Yet the rest was soaking)
---------- Post added at 10:20 AM ---------- Previous post was at 10:16 AM ----------
A thought occurs.... does it actually have a sim card slot? Like... is it possibly a Droid 2? :S
---------- Post added at 10:25 AM ---------- Previous post was at 10:20 AM ----------
Mikevhl said:
I know it's a bit extreme to do, but it might help for you. Try installing ubuntu or wubi, then use sbf_flash on ubuntu. It takes some time, but if you REALLY need to SBF you should give it a try. Usage is:
chmod 777 sbf_flash
./sbf_flash /path/to/sbf/file
Click to expand...
Click to collapse
Got that from the recovery thread.
I dug up this guide to using ubuntu live cd to flash sbf's for the droid 2, hopefully you are switched on enough to workout what you need to do differently for the MS2
http://forum.xda-developers.com/showthread.php?t=804088
I'd try that and see what happen
Hey guys,
first: thx to DreadPirateDan. you're right, i don't know enough about the phone. So i sat down after work and startet to read and with all the basic information i know about the phone. While analysing all the things i just saw a special thing in the bootloader:
When the phone is switched on into bootloader, the screen shows:
"Bootloader Fastboot mode
70.13
Battery OK
OK to Program
Transfer Mode:
USB"
So it seems that i've got the fastboot script active. So i should do everything with the phone i want to do, right?
i will go on reading. maybe i will find any way to check all the files.
Is it possible, that the phone loops because of fastboot mode and a secret saftyissue which bans all phones booting with active fastboot?
May any of u check on a not rooted and for difference rooted milestone 2, if the fastboot notify is standard?
Btw - got a Sim-Slot, so it seems to be a Milestone 2.
greetz
This ones a long shot - but if you have another USB cable available, try using that. Perhaps the one you are using is somewhat damaged - not enough to cause errors flashing, but enough to corrupt data? I don't know but i'd certainly give it a try! .
---------- Post added at 08:00 AM ---------- Previous post was at 07:59 AM ----------
Yeah that's the screen of bootloader saying it's all sweet to flash with rsd-lite
So that's a good sign
I'm concerned perhaps it's had some physical damage to the system storage.
I'm just confused, your steps appear to be all correct, what you've done allready, and it should have worked allready!
How did u get into Bootloader Fastboot mode???
Are you sure it says 'Fastboot' coz Fastboot could mean unlockable bootloader?
May be some developer could throw some more light on this.
When we first got the Chinese GB link I remember there were a couple of guys who had deceloper phones.. They never explained how they'd got them though lol
Sent from my MotoA953 using xda premium
Fastboot confirmed
Hey Guys,
well its definitly Fastboot. I installed Android SDK yesterday and tested a little bit.
I can flash images through fastboot and all those things.
Poblem is, i'm not so familiar with all those things. I know a little bit of electronics but not so much about how software and specially android works with the hardware. Just started yesterday to read about this.
Attached are some pics of my phone during bootloader and how it looks.
Now it would be first nice, to get this thing work!
Because at the moment it hangs still during booting, cause i don't know so much about how to flash from fastboot.
When it is true, that this could help this forum here, i won't sell it anymore. But i need help to work all this out.
I contated parallely the customer service of motorola at my country, to ask, if this device has still waranty via IMEI, but they don't have this IMEI in their database.
So come on guys, more information, how get the phone work again, may be with any rom we wish someday without hacking anything
greetz
I have the same problem. tried to bootstrap after ive installed cyanogen 7 and now im stuck on the M logo. wiping cache or factory reset won't work
thing is the links for sbf files at and-developers won't work :\ so now i cant flash anything
plz help
Alot of file sharing stuff got shut down just recently that's why all the links are dead
if you had previously upgraded to gingerbread, that is your problem - cm7 doesn't work with it. Have a crack at the dowgrade method endless7 has and then you can flash cm7 with CWM.
ok, i figured it out. just searched google for one of the builds. flashed it and it turned out to be a french retail version of froyo. installed MIUI rom. works fine
I maybe resurrecting this but I need help. I got my milestone 2 yesterday and then I rooted it successfully and then I tried to use ClockworkMod (Rom Manger mainly) to flash CM7. and well my phone is stuck in a boot loop now. It starts with a red M logo and then it goes to the CM android sliding in and the circle spinning then freezing and going again. I can only get into bootloader mode and when ever I plug my phone into my computer to use RSD it says chip error 43. I can't even find an SBF for my phone since all the links where to Megaupload. Please help
EDIT:
Okay so I just used the newest version of RSD and got a SBF for my phone but still the same thing happened. This time RSD kept on going and the CM android did what it was doing before.
Nikunj3xP said:
I maybe resurrecting this but I need help. I got my milestone 2 yesterday and then I rooted it successfully and then I tried to use ClockworkMod (Rom Manger mainly) to flash CM7. and well my phone is stuck in a boot loop now. It starts with a red M logo and then it goes to the CM android sliding in and the circle spinning then freezing and going again. I can only get into bootloader mode and when ever I plug my phone into my computer to use RSD it says chip error 43. I can't even find an SBF for my phone since all the links where to Megaupload. Please help
EDIT:
Okay so I just used the newest version of RSD and got a SBF for my phone but still the same thing happened. This time RSD kept on going and the CM android did what it was doing before.
Click to expand...
Click to collapse
hi,
Can you please explain clearly if you are able to boot CWM recovery or are you just getting a boot loop and unable to boot to recovery? As far as I know you won't be able to flash clockwork mod recovery for the Milestone 2 using ROMManager .You need to use Droid 2 bootstrap recovery.
Hello all,
So I have in my hands a Droid 2 on VZW which is currently not working. All I know is this:
It was rooted when my friend bought it. He received a notification for an update sometime today, installed it, and now it seems to only boot to the bootloader.
The screen basically just says:
Bootloader
D2.37
Err:A5,70,00,00,23
Battery OK
OK to Program
Connect USB
Data Cable
So, I've never used a Motorola phone before, and I'm not sure where to start. Can anyone guide me with a little hand holding to get this thing working for him again?
Thanks all.
As an update. Read around a bit, tried clearing cache, then did a full wipe, and it still ends up at the same screen each time.
did you try, rerunning the update, from recovery
not sure where it's stored or if it would be gone, from data wipe
if that doesn't work, take to verizon store, if that is an option
there is a fix for the, Droid 2 Global, here [How-to]unbricking downgraded 629 & root normal function OTA 629
someone I'm sure will, use the method, for fix for the D2
they will need a copy of the update
looks like the update is saved in the cache
so if you wipe cache or data, it should be gone
so it's verizon, wait for SBF (official or repacked)
or update failed, maybe just use old SBF 2.3.20,SBF Mirror
Tutorial/Walkthrough for flashing an .sbf to Droid 2 (rooting/factory restore)
Sbf will ether work, or bootloader will change to MEM-MAP Blank error
Is it advisable to try the old sbf, or will that be bricking his phone permanently?
Thanks!
sbf will brick phone, till correct sbf is found
Sent from my DROID X2 using xda premium
xiton said:
Hey shadow,
Did the newest sbf ever come out? I'm still trying to fix this VZW Droid 2
Click to expand...
Click to collapse
no SBF yet
does phone still say
Bootloader
D2.37
Err:A5,70,00,00,23
Battery OK
OK to Program
Connect USB
Data Cable
if so can you get to android recovery?
Booting into Recovery
Power down the phone.
Slide out the keyboard.
Press and hold the X button on the physical keyboard.
Press the lock/power button.
Once you see a warning sign with an android robot appear, press Volume Up and Down buttons.
Click to expand...
Click to collapse
DROID Wiki.
maybe you can install update, unlikely but worth a try, need to be able to put it on sd card, and rename update.zip
then select apply sdcard:update.zip in android recovery
maybe you'll get lucky
xiton said:
Hey sd_shadow,
I see the sbf file finally came out for me to fix my friends phone. I have one problem though. The battery is almost dead and I can't get the phone to charge. What can I do to get it to charge?
Thanks!
Click to expand...
Click to collapse
safest way is to buy a $5 spare battery charger like http://www.amazon.com/MOTOROLA-Droi..._1_6?s=wireless&ie=UTF8&qid=1338740850&sr=1-6
take to verizon store to charge battery,
or use the MacGyver method but I do not recommend, because you can fry your phone
edit: changed link
Hello,
hope you can help me.
today i tried (noob as i am) to downgrade my phone from JB to GB. for some reason i needed (wanted) to flash the kernel and somewhere in that process when i connected my phone to my pc in the wrong way, windows told me to better format it. i was unable to connect to RSD lite and tried a bunch so i deceided to do so. and all was gone. stuck on motorola logo and stuff. finally managed to flash kernel with rsd but now i cant install any roms. im not alowed. and have the most basic bootinstaller ever (only 4 options).
i feel like i need to root my phone again but cant figure out how. or maybe the solution is something else i dont know. can anyone help me with this?
marzell88 said:
Hello,
hope you can help me.
today i tried (noob as i am) to downgrade my phone from JB to GB. for some reason i needed (wanted) to flash the kernel and somewhere in that process when i connected my phone to my pc in the wrong way, windows told me to better format it. i was unable to connect to RSD lite and tried a bunch so i deceided to do so. and all was gone. stuck on motorola logo and stuff. finally managed to flash kernel with rsd but now i cant install any roms. im not alowed. and have the most basic bootinstaller ever (only 4 options).
i feel like i need to root my phone again but cant figure out how. or maybe the solution is something else i dont know. can anyone help me with this?
Click to expand...
Click to collapse
are you able to put your phone in bootloader mode ? and witch version you use to flash your phone with RSD use one of those
http://sbf.droid-developers.org/umts_milestone2/list.php
yes i used the retail british 2.4
i am able to flash sbf file but it still wont go past moto logo and stock recovery cant install any roms. not allowed to install or something like that.
1 get to recovery mod (x button+power) do a wipe data then full reset
2 update the last boot loader with rsd
3 repeat step 1
4 sbf your phone with retail 2.3.6 like retail brazil then be patient and your phone will power up after many reboot (before that prepare (bootstrap.apk) in memory card)
5 root your phone using super one click then install bootstrap and get bootstrap recovery and you can install CM10 now it will make your phone boot normally
jakkokko said:
1 get to recovery mod (x button+power) do a wipe data then full reset
2 update the last boot loader with rsd
3 repeat step 1
4 sbf your phone with retail 2.3.6 like retail brazil then be patient and your phone will power up after many reboot (before that prepare (bootstrap.apk) in memory card)
5 root your phone using super one click then install bootstrap and get bootstrap recovery and you can install CM10 now it will make your phone boot normally
Click to expand...
Click to collapse
thank you i will try this. the battery is currently drained, so i need to recharge first. using wall charger (usb unit) but it didnt charge yet. keeps telling me the batt is low. any tips for that? only thing i found on here is to use a wall charger.
use this for low battery problem
http://forum.xda-developers.com/showthread.php?p=10163846
jakkokko said:
use this for low battery problem
http://forum.xda-developers.com/showthread.php?p=10163846
Click to expand...
Click to collapse
this worked as far as the batery problem, pita to do thou. now hope i can root the thing, since i did not yet succeed to run the adb drivers..
update: well, i fear the worst. after the last time flashing the sbf it wont turn on anymore. guess i did screw up the wire-DIY. will update if there is any good news. but for now it seems i should start looking for a new phone.,.