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.
Deleted by user
I suggest you to completely charge your phone for half a day and then try to power it on. It should at least get stuck in the M logo.
Sent from my MB525 using XDA App
Mine has done the same thing, i left it connected to rsd lite to flash, went to bed, and now its stuck at a black screen and won't boot up at all. Same white light when plugged in to the pc, but rsd doesn't recognize. please help.
Was your battery low when you tried flashing? It will not charge in bootloader mode so if you're battery is low you will have issues. If you boot with volume up pressed does it give you a message?
Try the Mcgyver battery fix found in this forum.
skateguitar00 said:
Mine has done the same thing, i left it connected to rsd lite to flash, went to bed, and now its stuck at a black screen and won't boot up at all. Same white light when plugged in to the pc, but rsd doesn't recognize. please help.
Click to expand...
Click to collapse
Deleted by user
I had that problem while trying the "Flash FroYo without losing downgradeability" solution: SBF Problem
After downloading, flashing every other available official ROM, and failing with each one, and seeing that no other SBF fro T-Mo exists anywhere, I bit the bullet and flashed the T-Mo signed FroYo ROM. And it worked!
So now I may have screwed myself over by flashing the leaked ROM but hey, it works well and is fast. Plus, it's FroYo so I now have A2SD and built-in Tethering...
gookia2000 said:
Hi all, I am a proud owner of a t-mobile defy (for about 2 months now!) and my hands got itchy today and went ahead to "debrand" it following the guide by Higgsy.
I was trying to flash a uk 2.21 rom onto my t-mobile defy (rooted with z4root).
Well, I managed to do all the steps of the guide. my phone was recognised by rsdlite, i selected the uk 2.21 sbf file, i clicked start, and it started flashing the different code groups. Finally, it said "finished" and "PASS". Here is when the problem started. The phone did not reboot into android. It was just a blank screen with a white light on the top (where the green led is to inform you about new messages.)
i panicked and disconnected the phone (the white light turns off after disconnecting), took out the battery, tried rebooting, tried rebooting into recovery (power + vol down), tried rebooting into bootloader (power + vol up). Nothing worked. it just stayed dead.
I then plugged it back into the computer. immediately the white light came back on and rsdlite recognised my phone. i tried flashing again - same result. I then tried flashing the 2.52 uk rom - same result.
even more panicky now, i unplugged everything and decided to take a nap and hopefully think of some ingenious solution to the problem. now, after a 3 hour rest, i tried plugging the phone back into the computer. the white light comes on, but now rsdlite doesnt even recognise the phone.
In essence, is my phone bricked? I cannot:
1) load into recovery to do a nandroid restore (yes, i have a nandroid backup copy)
2) load sbf files from rsdlite. every sbf file i tried doesnt seem to work. now its worse as rsdlite doesnt even recognise my phone.
i have even tried doing a nandroid restore via adb. but i get the error message that no phone was detected in the command prompt. perhaps its because the phone was not started in recovery mode.
The only explanation i can think of is that i have recently updated to the t-mobile 3.6.360 update and that might be the reason why so many people before me were able to flash their defy's roms successfully while i got stuck.
Can anyone please help? I LOVED my defy more than any other phone, and 2 months was too shortlived!
Click to expand...
Click to collapse
skateguitar00 said:
Mine has done the same thing, i left it connected to rsd lite to flash, went to bed, and now its stuck at a black screen and won't boot up at all. Same white light when plugged in to the pc, but rsd doesn't recognize. please help.
Click to expand...
Click to collapse
Deleted by user
Actually, all you have to do is press the power button while the LED is on and RSDLite is running. You will hear the USB detection sound and your phone will appear on the list. It won't appear as it normally would but it will be listed.
Then just choose the Froyo ROM and then click start to flash it. It'll take less than 10 minutes...
There's no other way that I know of to get it working. Even in the link that I posted, you can check and see that no one even bothered to give me an idea of what to do. I had to figure this out myself.
I figured it was the bootloader protection that was causing the problem so the logical choice was to flash the only T-Mo ROM available which happens to be the leaked Froyo.
It's been almost 24 hours and I've had no problems with FroYo so as far as I'm concerned, I'm good.
gookia2000 said:
Beach Head, thanks for your reply. you have provided me with a glimmer of hope!!! the leaked tmobile froyo sbf is one i have not tried. I will certainly try to flash my defy with that once i have gotten it recognised by rsdlite.
I believe my phone is currently not being recognised by rsdlite due to insufficient battery. (cant confirm this, as all i see when i plug in the usb is a white light on my phone. but ever since i started this entire nightmare, i think i have attempted flashing at least 5 different sbf files and considerable battery has been drained.) I will try the Mcgyver battery fix next.
skateguitar, THERE IS HOPE!!! i havent confirmed it yet but i think we all got stuck cos we were trying to flash from a "non-downgradeable" 3.6.360 firmware. and rsdlite does not recognise our phones due to low battery (your phone was left with a white light on after flashing for 1 whole night.) SO... i propose this course of action: 1) perform the Mcgyver battery fix and try to get our phones recognised by rsdlite first. 2) once recognised, flash with the leaked tmobile froyo sbf.
Does anyone have any better suggestions before i plunge head first to save my phone?
Click to expand...
Click to collapse
Yes all i wanted to say was that you might have lost your downgradability and thats why phone does not boot. Simple thing is to flash the original sbf like what beachhead suggested. It definitely should work.
Sent from my MB525 using XDA App
Guess what, it works!!!
Deleted by user
Glad I could help you out!
Enjoy Froyo!
gookia2000 said:
OHMYGOODNESS!!! I LOVE YOU GUYS!!!
My Defy has been flashed with the t-mobile froyo leaked rom and IT WORKS!!! I was so mentally set with the idea that my defy has been bricked and I just threw $400 down the drain... NOW I AM SO HAPPY!!!
Anyway, just for your information, here is what I did:
- I first tried to get my defy recognised by rsdlite. I tried Beach Head's suggestion of pressing the power button while the led is on to no effect. I reckon that the battery has just been drained too low. So, i went ahead with the McGuyver battery fix.
- Alas, with the wires protruding precariously from my phone, rsdlite finally recognised my phone. I went to load the leaked t-mobile froyo rom and went ahead flashing it.
- And, guess what, IT WORKS!!!
Thank you all so much, especially beach head, for your help in this forum! I would have gone to the mobile store to get another phone if not for you guys!!!
Click to expand...
Click to collapse
I have the same problem, and will probably end up trying to flash the leaked Tmobile Rom.
Can you point me to where you downloaded this file? I think I found the thread, but I want to be sure
Deleted by user
got it! Thanks!
Now to ultimately decide if I want to flash this, since it's non-downgradeable
To update, flashing this rom has fixed my phone. Yay! Thanks!
I wonder if it was the 3.66x update that Moto pushed out - this phone was brand new, bought in Dec 2010, no other hacking done on it...
Beach_Head said:
I had that problem while trying the "Flash FroYo without losing downgradeability" solution: SBF Problem
After downloading, flashing every other available official ROM, and failing with each one, and seeing that no other SBF fro T-Mo exists anywhere, I bit the bullet and flashed the T-Mo signed FroYo ROM. And it worked!
So now I may have screwed myself over by flashing the leaked ROM but hey, it works well and is fast. Plus, it's FroYo so I now have A2SD and built-in Tethering...
Click to expand...
Click to collapse
How did you get it to show up in rsd
I'm not working on my phone because i think i messed it up enough, so i took it to a store that fixes phones. The guy told me that he had my battery on a universal charger and he still cant get rsd lite to recognize it... What can i do
Another Happy Defy User
Just to confirm, I was seeing the same thing gookia2000 was seeing. Here was my resolution in case it helps anyone:
I was able to get mine working by flashing the US Stock Froyo build as explained in this thread: http://forum.xda-developers.com/showthread.php?t=938708&highlight=bricked&page=2
I found this thread to be super helpful as it helped me confirm my suspicion that the battery being low was the issue: http://forum.xda-developers.com/wik...#Recover_Nearly_Bricked_Phone_.28hopefully.29
Thankfully my wife has the same phone so I borrowed her battery, otherwise I would have been going McGyver style per Sorensiim (da' man) as seen here:
http://forum.xda-developers.com/showthread.php?t=892026
So happy this nightmare is over - running Froyo is a little bonus love!
Thanks to all @ XDA!!!
-Dave
Defy wont come on get a white light!
im having the same prob i did the the steps but its not working is there anything else i can do or is there a video of the proceeder
I have the same issue with a Telstra defy. I can get RSD to recognise something is connected but it isnt listed as MB525 like before but as "S Flash OMAP3630" I have flashed various SBF files but nothing is changing.
Long story short, I think I'm soft bricked.
I've tried wading through DG's soft brick recovery thread and ADB is just kinda beyond me.
As well, I cannot enter fast boot. I've tried holding both volume up + power and volume down + power, and both flash the white letters "Failed to boot 4" then the next line reads "Starting RSD mode"
Honestly, I'm just looking for help that I can understand, or a pretty forgiving walkthrough.
Thanks in advance to anybody who can help.
xyrovice said:
Long story short, I think I'm soft bricked.
I've tried wading through DG's soft brick recovery thread and ADB is just kinda beyond me.
As well, I cannot enter fast boot. I've tried holding both volume up + power and volume down + power, and both flash the white letters "Failed to boot 4" then the next line reads "Starting RSD mode"
Honestly, I'm just looking for help that I can understand, or a pretty forgiving walkthrough.
Thanks in advance to anybody who can help.
Click to expand...
Click to collapse
If you get the starting RSD mode you might have a chance. Put your phone back into that mode and try flash back to stock SBF using rsd lite. Follow this guide: http://forum.xda-developers.com/showthread.php?t=991072&highlight=flash+sbf
What version of software were you running before the brick? 1.26, 1.57 or 1.83? You will need RSD Lite - Download As well as the sbf for your version of software. Post back your version and I can give more guidance.
You may not need to flash all the way back to 1.26, I soft bricked today - as in can't get past the initial Moto screen with a flashing red light, and flashed 1.83 sbf.
I've actually tried to flash some of the SBFs- well, all of them, now that I think of it.
It always ends up in an error, though, and stops.
If you give me a sec, I'll try and recreate it. Off the top of my head, I remember it saying something about "Bypassing BP" or something like that.
Thanks for the fast responses. Lemme try and RSD flash here right quick.
PS (EDIT): I was on 1.5.7 running GladiAtrix 4.2.3 (if that makes any difference). I just started flashing 1.2.6 via RSD. I'll let it sit and see where it sinks.
Thanks again guys.
EDIT #2: So it gets to "Interface AP-OS: Flashing Code Group 57" - 13%, then it just chills for a few minutes, then says [Phone 0000]: Switching device to BP passthrough mode" - still at 13%, then it stops and says "Flashing Process Failed" and, if it hadn't stopped responding, it looks like it would go on to say something about "Interface A..." and the ellipses is where it's cut off. I'm sorry about that.
Any thoughts?
If you were on 1.57 I would try flashing the 1.57 SBF - this will retain a lot of your info, whereas the 1.26 will wipe your phone clean and take more work.
1.57 SBF Thread
You will need to root with gingerbreak to regain root if you flash the 1.57 SBF, Gingerbreak Thread. Make sure to copy the contents of mnt/sdcard and mnt/sdcard-ext to your computer so you can replace them after gingerbreak cleans them out.
xyrovice said:
EDIT #2: So it gets to "Interface AP-OS: Flashing Code Group 57" - 13%, then it just chills for a few minutes, then says [Phone 0000]: Switching device to BP passthrough mode" - still at 13%, then it stops and says "Flashing Process Failed" and, if it hadn't stopped responding, it looks like it would go on to say something about "Interface A..." and the ellipses is where it's cut off. I'm sorry about that.
Any thoughts?
Click to expand...
Click to collapse
Just putting that up there.
Also, I was in the process of trying to wipe my phone for a clean 1.8.3 flash, so a 1.57 flash to retain info isn't a big deal.
I went straight to 1.2.6 in the hopes that the retail version would be more likely to go through (for whatever reason).
Thanks for bearing with me.
Take out your SIM card and SD card if you have one, restart your computer and don't start any other programs besides RSD Lite to allow it the most resources (I've had it fail a few times without enough resources). Start RSD Lite and load up the SBF, turn on the phone and boot to RSD mode with the volume up button, once in RSD mode plug the phone in and start the flash. I don't know if any of this will work for sure but these are all steps to help the process.
try multiple cables, computers, OS's, and USB ports. Sometimes any combination of things helps
Got it. Rebooting now and starting nothing but RSD Lite. Also gonna change the USB port. (SIM and SD gone as of awhile ago, so no worries there. Thanks for checking though)
Well.
I. Will. Be.
I never thought I'd be happy to see that Motoblur login screen.
Phone's up and running. Looks like the reboot + USB port swap did the trick.
And you bros, no matter how simple your advice may have been, are pure gods right now.
Thank you thank you thank you a million times (little girl style- yet there is no shame in prostrating myself before you pros).
Seriously though, I owe you guys a lot. Thanks a ton.
xyrovice said:
Well.
I. Will. Be.
I never thought I'd be happy to see that Motoblur login screen.
Phone's up and running. Looks like the reboot + USB port swap did the trick.
And you bros, no matter how simple your advice may have been, are pure gods right now.
Thank you thank you thank you a million times (little girl style- yet there is no shame in prostrating myself before you pros).
Seriously though, I owe you guys a lot. Thanks a ton.
Click to expand...
Click to collapse
Glad to hear it worked for you, I know what its like to sh*t bricks over a phone snafu so congrats and welcome back to the land of the living.
Bricks? That may have happened when I flashed Adeo and got the red lights.
This time, I sh*t absolute trains.
And I'm beginning to like the Atrix more and more. I didn't lay down all that I had already done trying to recover my phone when I realized things had gone awry, but I'm sure that, on a software level, it was equivalent to repeatedly napalming a small Hawaiian tiki hut.
Thank you again, my friend. I'm almost done flashing 1.83 at this point, and I couldn't have done it without you guys.
Message to delete
I would think your problem lies in trying to flash US At&t software to your French Orange phone. Go to: http://forum.xda-developers.com/showthread.php?t=1125944 and find the French Orange firmware (there are two of them) and download them. If those don't work, try starting your own thread either here or in Q&A. Good luck!
Tim
It works
Happy
Thanks you
My full apologies in advance if there has been a similar thread, I've honestly been looking for the past couple of hours. If there is one and I've just missed it, feel free to open-fire on me.
I have an AT&T Atrix running on 2.3.4 Gingerbread; rooted and unlocked bootloader with the Alien 4 ROM and the Alien 4 Theme. I'm really new to rooting and have only been rooted for about a week now. Today though, I was going to trade my Atrix for an HTC Inspire. I used to have one, switched to the Atrix, and I've come to the conclusion that I prefer the Inspire. While wiping my personal info off of my phone, I did something I clearly shouldn't have though, and everything went downhill from there. Not really thinking, I had already wiped my SD card (which had the Alien ROM), and I still needed to clear off the phone itself, so I figured it'd be okay to just go to the Settings and wipe my phone through the Privacy option. When it booted back up I saw that almost all apps (including necessary ones like Phone and Browser, among others) were gone. I didn't think it'd be a problem and I could just download them again through the Market, but my Settings app was also gone, so I couldn't configure a Wifi connection. I couldn't configure anything. My SIM card didn't work either, nor did the SIM of the person I had met to trade for an Inspire.
When I got home, I went through the different options in Android Recovery on my phone... Still nothing. So I fired up RSDLite on the Windows 7 comp in the computer room, downloaded the 1.5.2 Atrix SBF from here to try and flash it back to the stock Atrix ROM, and clicked Start. My phone rebooted once or twice and it looked fine, but then RSD said that the flash had failed. Now whenever I try to turn my phone on, it stays at the big M logo with "Dual Core Technology" underneath (it doesn't even change to the pulsing M). I haven't been able to boot it up since... Sorry for the novel, but it'd be really greatly appreciated if someone could help me out here. Thanks for your time.
hayatohuseman said:
My full apologies in advance if there has been a similar thread, I've honestly been looking for the past couple of hours. If there is one and I've just missed it, feel free to open-fire on me.
I have an AT&T Atrix running on 2.3.4 Gingerbread; rooted and unlocked bootloader with the Alien 4 ROM and the Alien 4 Theme. I'm really new to rooting and have only been rooted for about a week now. Today though, I was going to trade my Atrix for an HTC Inspire. I used to have one, switched to the Atrix, and I've come to the conclusion that I prefer the Inspire. While wiping my personal info off of my phone, I did something I clearly shouldn't have though, and everything went downhill from there. Not really thinking, I had already wiped my SD card (which had the Alien ROM), and I still needed to clear off the phone itself, so I figured it'd be okay to just go to the Settings and wipe my phone through the Privacy option. When it booted back up I saw that almost all apps (including necessary ones like Phone and Browser, among others) were gone. I didn't think it'd be a problem and I could just download them again through the Market, but my Settings app was also gone, so I couldn't configure a Wifi connection. I couldn't configure anything. My SIM card didn't work either, nor did the SIM of the person I had met to trade for an Inspire.
When I got home, I went through the different options in Android Recovery on my phone... Still nothing. So I fired up RSDLite on the Windows 7 comp in the computer room, downloaded the 1.5.2 Atrix SBF from here to try and flash it back to the stock Atrix ROM, and clicked Start. My phone rebooted once or twice and it looked fine, but then RSD said that the flash had failed. Now whenever I try to turn my phone on, it stays at the big M logo with "Dual Core Technology" underneath (it doesn't even change to the pulsing M). I haven't been able to boot it up since... Sorry for the novel, but it'd be really greatly appreciated if someone could help me out here. Thanks for your time.
Click to expand...
Click to collapse
That definetly doesn't sound like a hard brick. Use romracers recovery and try to flash a fruitcake http://forum.xda-developers.com/showthread.php?t=1163009 which are much safer then sbfs.
By the way theres no need to apologize when posting in the "correct" forum .General or QandA is where this thread belongs. if this were development though then you'd be in a world of ****! LOL
if you are on big M (without any "failed to boot" ) you're soft bricked,
try to power on button+ volume down button...
if says "fastboot" then just volume up,
download the .img files in the fruitcakes section and follow the fastboot mode instructions...
you'll get back your phone.
read carefully the instruction where to put the files in your windows 7 user directory etc etc, 90% of the problem is because people don't understand where to place executables and run them
hope it helps
Thank you guys so much!! The solution was actually even simpler than what you both suggested; all I had to do was flash to 2.3.4 with moto-fastboot. I had never used fastboot before, so it took me forever to figure it out, but I finally got it and my Atrix is back to the way it came. Thanks again, you two. Cheers!
hayatohuseman said:
Thank you guys so much!! The solution was actually even simpler than what you both suggested; all I had to do was flash to 2.3.4 with moto-fastboot. I had never used fastboot before, so it took me forever to figure it out, but I finally got it and my Atrix is back to the way it came. Thanks again, you two. Cheers!
Click to expand...
Click to collapse
Kudos for doing some research and figuring out how to resolve the problem. Not enough of that going on. Doesn't it feel like more of an accomplishment?!
KeRmiT80 said:
follow the fastboot mode instructions...
you'll get back your phone.
Click to expand...
Click to collapse
hayatohuseman said:
all I had to do was flash to 2.3.4 with moto-fastboot
Click to expand...
Click to collapse
* 10chars
Night before last my Droid X was upgraded via OTA from Froyo 2.2.1 to Gingerbread 2.3.4 , at which I lost my Root. So I started searching YouTube for videos on taking my phone back to Froyo. And I found just what I was looking for. Return your Droid back to Froyo. So I followed the instructions to the letter, I downloaded - RDS Lite 4.9 - Motorola Helper_2.1.40_5.5.0 - VRZ_M810_2.3.34_IFF_01 . According to RSD Lite the flash was successful. Droid X reboots, and this is what I was left with.
Bootloader
30.04
Err:A5,70,70,00,1F
MEM_MAP Blank
Service Req'd
Battery OK
OK to Program'Transfer Mode:
USB
I have tried SBFing twice and RSD Lite sees the phone, goes thru the flash, reboots the phone but I get the same responce on the phone as stated above. Although in my computer, the Droid is not detected.
In your opinions, have I done an unrecoverable bricking to my Droid?
Go ahead, I can take it.
TIA
I used 4.5.621 SBF file, and was able to bring my phone back to the way it was before I got in a bind (Droid X SBF Files - Motorola SBF Files). It is alive with all of my Apps, so I'm not sure just what happened to it. But to whoever is responsible for the web site, I think P3 Thanks
Great job on getting back to .621.
Unfortunately, being on .621 makes it impossible to flash back to Froyo.
However, you can root and install custom roms.
Sent from my DROIDX using Tapatalk 2
yeah I know, but at this point I'm just happy to have my phone back in good working order. I had just bricked my Droid X2 @ 2 weeks ago, so now I don't have to face my wife with another $200.00 paper weight.
I have the same issue. Someone pointed me to this forum so I'll just include my text.
So I just got my first droid yesterday, it's a droidx from motorola. I initially factory reset it and cache cleared and it was working like a charm. Anyways, today I got the idea after reading over cyanogenmod following these instructions. Since I didn't have much on it I didn't backup. I remember vaguely updating the system previous to this, I think I was at 2.34. Anyways, I get done with flashing it- as far as I know it was successful- rdslite said it was complete. I try to do another factory reset, can't get into it. Just the bootloader comes up saying : Bootloader30.04 Err:A5,70,70,00,1F and a few things about to plug usb in and that it needs service...
I see something on cyanogen's page that I overlooked before:
WARNING: The 2.3.4 OTA release, the bootloader was patched to version 30.04. If an attempt is made to downgrade to an earlier version through the SBF method below, the bootloader will throw an error and the phone will not boot.
FLICK.
I tried the 1kds cd and it says it installed properly, I turn it on only to see same bootloader issue. I tried another rom and same thing. The last one I used was apparantly a 2.34 one and now my phone says code corrupt on the bootloader screen.
I need to find a way to charge the battery. I feel bad because it was a present to me from my girlfriends sister, and I don't want to see her and tell her I broke it already
But, can you guys help me with this? I don't really know where to go from here.
Sbf
Sbf is the only way. And from what I understand if you did the. 621, you won't be able to do previous releases.
I could be wrong.
When it comes yo moto flashing, donkey skip reading anything lol
Sent from my DROIDX using xda premium