Hello,
I've been searching the forums for this but basically I did Gingerbreak/Gingerblur 4.5 from the now zombified post. I have since over looked the update 4.5.91 because I don't want to hard brick the phone, but now it looks as though I'm stuck on Gingerblur.
1) I CANNOT restore to factory settings via the phone (Get stuck in Failed to Boot 2 Starting RSD Mode lock out) no matter what I do.
2) After going into RSD protocol support, It will not recognize my phone at all on RSDLite v5.0 (so can't flash SBF files)
3) If I select Android Recovery it will result in "Failed to Boot 2"
I've been looking at the threads for the latest stuff, but none of them seem to address my issue. Any thoughts on how the heck I get this thing fixed? I'd like ideally to get Android 2.3.4 and the latest and greatest, but don't want to brick the phone. Any help would be greatly appreciated
BTW it works just fine in Gingerblur, but I'd like not to be stuck with that forever...
You are not unlocked. Feel free to flash an sbf as hard brick has to do with unlock and bootloader stuff.
My thoughts would be to just unlock your bootloader. Start with the pudding thread
sent from my Atrix via XDA premium
Well, perhaps I should have gone back to stock image first before doing Pudding.
Soft bricked my phone now. Stuck in Failed to Boot 2 - Starting RSD Mode
I will download the 1.26 from here:
http://forum.xda-developers.com/showthread.php?t=991072
and try to do a restore...I hope I haven't screwed my phone up...
I did the same and flashed it back to stock i used rsdlite 5.5 and used my country specific SBF.
It is back to stock but webtop Isnt working
Actually sorry. To clarify, I'm using this thread instead for the SBF.
http://forum.xda-developers.com/showthread.php?t=1125944
Will see if web top is a concern IF the stock file flashes properly...
Being on anything won't effect an sbf flash. Go ahead and rsd to gingerbread. Or pudding
sent from my Atrix via XDA premium
I got it back to 1.26
One thing people don't mention is if you have an older version of RSD Lite it will NOT recognize the phone with the latest drivers...(and there are a wealth of older RSDLites floating around so to a newer person it's not quite evident which is latest)
It's now on 1.26. I will try the bootloader unlock, pudding, etc later when I feel more comfortable...
Related
Has anyone done this? i bricked my phone in this process. it fails while flashing at the BP pass through stage and asks for some driver which i dont have and while switching phone it writes modem did not power up switching to rsd mode.
Try RSD to 1.2.6 first then after that try sbf 1.5.7 or 1.8.3
Sent from my Over Clocked Rooted Debloated Gingerblured4.5 ATRIX4g
I RDS'd straight to 1.8.3 the first time I tried out the rom, before all the fixes and whatnot.
amrutpritam said:
Has anyone done this? i bricked my phone in this process. it fails while flashing at the BP pass through stage and asks for some driver which i dont have and while switching phone it writes modem did not power up switching to rsd mode.
Click to expand...
Click to collapse
I had the same issue, scared the crap out of me. I flashed second time, artist again. Third time sbf flash worked. Don't know why, but taking out external sd card and sim card helped.
Sent from my MB860 using XDA Premium App
I did it twice. flashed 1.83 thru RSD lite then unlocked the bootloader and used gingerbreak to root.
I used the full SBF of 1.57 so I could use the OC kernel and I didn't have any issues.
I just did last night. Just reboot into RSD mode, flash the full (not service) 1.8.3 SBF, boot and sign into Motoblur (Probably not needed but its what I did), reboot back into RSD, flash the pudding SBF, reboot into fastboot and flash CWM. No issues.
I just pulled and installed the 2.3.4 OTA.. after the install and reboot I am stuck at the Motorola M... I have tried a Factory Reset as I can get into FastBoot etc..
What would be my best course of action? Should I just flash a ROM like Ninja?? or try to go back to stock 1.26 then update from there or will I Brick going that route? Any help would be greatly Appreciated!
What were you on before the update?
Beamed from WinBorg 4G via XDA Premium
I was running stock 1.83 Rooted. Only other thing was flashed 2.3.4 radio..
Same issue as OP (stock 1.83) but I didn't flash a radio, I only rooted with gingerbreak. OTA update installed and rebooted, went to the M logo screen (the version that isn't flashing/pulsing) and stays there. Grabbed the update off motorola's site, put it on my SD card, booted to recovery and installed with that, rebooted, same result
I've got the same issue. Was running stock 1.83 before, rooted and with a custom boot animation. Applied the update and now stuck at the dual core splash screen, even after a factory reset from the Android Recovery screen.
Adrian, I am now up and running....
I unlocked the bootloader using pudding and then flashed 2.3.4 using fastboot from KennethP...
However now there seems to be an all-in-one SBF that I actually just installed on my phone as well that is at the top of the pudding thread:
http://forum.xda-developers.com/showthread.php?t=1136261
Where it says Update July 23... where it says "Download ATT 2.3.4 Pudding+root here... " After flashing that via RSDLite you can click on the link right before that link in the same statement.. "root in preinstall (don't ask questions, read the post in this link)" to Root the 2.3.4 Atrix.. Hope this helps!
Thanks- I tried that route but ended up totally bricking. As in will not even turn on. Hopefully that's so bad that AT&T will replace the phone.
Adrian, I am sorry to hear that.. I would try AT&T and tell them that you pulled and installed the OTA. Hopefully they will do a replace.
I JUST undated to 2.3.4, from 1.8.3 on gingerblur there were no problems. Then I tried to unlock using the unlocker SBF on this thread: http://forum.xda-developers.com/showthread.php?t=1136261
Flashing the SBF failed, and now I am receiving this error from RSD lite. failed flashing process. Unable to retrieve interface handle (ox7027) phone is connected
When I put my battery in the phone fails to boot and goes to RSD mode, but I still cant flash anything to it. I have tried a few SBF files from the above metioned thread, but they all fail, with the same error message. Does anybody have any ideas for me?
Warning!
Don't try to flash any more SBF files because flashing to a lower build than 2.3.4 will hardbrick your device...as in for good!
Instead, try unlocking your bootloader, flashing over Tenfar's recovery, and then installing an atrix gingerbread stock image. It's your best bet.
fixed
Thanks, though you did not give specifics, I got it working. I guess I was just too tired at 2 am
hello, same thing happened to me, could you solve?
Should have went to stock 1.8.3 before updating. You updated over a deodexed file system, thus it screwed things up. Did you Ota update or flash a fruitcake. If you ota updated to 234 you can never use rsd again. Pudding is the only thing that can be used with rsd. If you unlocked then delete rsd.
Sent from my MB860 using XDA App
So here is my problem, i've wiped my phone so many times to try out every rom/kernel that is posted. The last time i clicked the wrong file to sbf to unlock it and ended up flashing the 235 electrify pudding sbf. (had them all in the same folder...dumbass)
I was able to get rid of the 108 svf error by flashing the boot.img back to the photon ones via fastboot. But still would get the 106 anytime i went to try and flash the sbf.
I've tried in Ubuntu as well as windows 7 to flash it back but nothing has worked since it wants a 235 sbf, and it locked the bootloader.
So I said screw it and tried flashing the electrify 2.3.5 and it loaded up and everything, but i'm stuck on the activation screen and cant get past it. (tires to activate through Verizon)
The 2.3.5 update also removed the bootloader unlock in fast boot even with the id number.
So as easy as it was to flash it right to the electrify sbf, i think once the sprint 2.3.5 sbf is out i should be able to go back. Or once an unlock is found to unlock the bootloader, i can flash the files via fastboot.
I haven't tried messing around with nvflash, since my computer doesn't show the apx when its in that mode.
Update: Was able to bypass activation by booting in to "Boot Android {No BP}" like on the droid x2.
Did you get bootstrap working?
TrojanZulu said:
So here is my problem, i've wiped my phone so many times to try out every rom/kernel that is posted. The last time i clicked the wrong file to sbf to unlock it and ended up flashing the 235 electrify pudding sbf. (had them all in the same folder...dumbass)
I was able to get rid of the 108 svf error by flashing the boot.img back to the photon ones via fastboot. But still would get the 106 anytime i went to try and flash the sbf.
I've tried in Ubuntu as well as windows 7 to flash it back but nothing has worked since it wants a 235 sbf, and it locked the bootloader.
So I said screw it and tried flashing the electrify 2.3.5 and it loaded up and everything, but i'm stuck on the activation screen and cant get past it. (tires to activate through Verizon)
The 2.3.5 update also removed the bootloader unlock in fast boot even with the id number.
So as easy as it was to flash it right to the electrify sbf, i think once the sprint 2.3.5 sbf is out i should be able to go back. Or once an unlock is found to unlock the bootloader, i can flash the files via fastboot.
I haven't tried messing around with nvflash, since my computer doesn't show the apx when its in that mode.
Update: Was able to bypass activation by booting in to "Boot Android {No BP}" like on the droid x2.
Click to expand...
Click to collapse
Sent from my MB855 using XDA App
Was able to root it via the photon torpedo, even though it says it fails, it wont install the apks from the root program but it is rooted. Just downloaded them off market and ran root updater.
Was able to get system recovery to install and booted in to it just fine. but it soft bricks after i install the skiny4g zip file, boots up the first time all the way to the US Cellular boot screen then resets, and then loops the Moto Dual Core icon. Tried the "Boot Android {No BP}, and same effect, also tried just wiping cache and then wiping the system and still the same results.
Update: Finely got Skinny4G to boot, took 3 tires and the last time i wiped system 2 times in mounts and storage, shows up as sprint and 2.3.4 and its looking at sprint wireless towers, just trying to activate it now.
Phone activated on sprint, 3g works with out any issue, but the wifi and 4g is dead, now i just have to wait for the electrify unlock or 2.3.5 sbf for sprint.
Hey man, i did the same i flashed 235pudding by mistake, so i tried using the 2.3.5 sbf form electrify and it was going great until !switching phone to bp.. something else" then it stopped on 99% and failed to flash... i waited for 5 minutes just to be sure nothing else happened... it didnt
Then i pulled battery and powered the phone again this time it didnt said the "failed to boot 2" but it didnt started it just sits on the motorola dual core logo.
I pulled battery and powered it trying to go into RSD mode and it just doesnt appears :O
I pulled battery and tried to go into fastboot and doesnt appears either.... i just can turn it on and it sits on moto logo.... any help ideas? Tnks
__________________________________
Edit: I pressed vol up and down while power button and it finally appeared RSD mode.... but battery too low to flash, im gonna charge the battery on an external charger for an hour and report later if RSD lite actually recognizes the device.
_____________________________________
YEAH! After charging battery the process completed, im an international user so its not very imporanto to me Spront or US cellular, the phone boots good without my sim... but as soon as i put it in it says " modem did not power up (0)" so...
Does Anyone knows where to go form here?
Thanks
jokersax11 said:
Did you get bootstrap working?
Sent from my MB855 using XDA App
Click to expand...
Click to collapse
Bootstrap install just fine after rooting.
Unbrick yourself
I want to thank Koriotto and everyone else who suggested and or tried the idea of flashing a 2.3.5 rom to save our backs. Now to everyone who has flashed 2.3.5 electrify pudding into their photons:
Disclaimer:
1°This will bootlock your phone until a working pudding for 2.3.5 is released.
2°I have no idea whether this will work with sprint whatsoever since I can't try it out being an "international" user, but at least your phone won't be a total brick. However, my common sense tells me this most likely won't work with Sprint.
3ºThere is a leaked Photon 2.3.5.sbf lurking amid devs, but as far I know it hasn't been released to the public yet. However, in case you do get ahold of it, please provide me the link so that we can try it out and see if we can help the Sprint folks get back to a stock Sprint rom. "Internationals" most likely won't care.
1°Try to get as much juice as you can into your battery.If you can, use someone else's fully loaded battery or charge yours with an universal battery charger (extremely cheap and easy to find). Your phone won't charge while in rsd or fastboot mode.
2°Download and install the appropriate Motorola drivers (x32 or x64 according to your windows flavor)
3°Download Electrify 2.3.5 SBF from here: https://rapidshare.com/#!download|8...19.0-19-release-keys-signed-USC-US.rar|530398
4°Get your device into RSD mode. If your loader says RSD mode, go to step 5. If your loader says nothing or is stuck on "Flashboot", don't worry. Power off your device and then press Volume down + power. The phone will turn on and then off. Then power on normally and you will be on RSD mode. If this doesn't happen the first time you try it, just keep repeating the forementioned process until you get into RSD mode.
5°Flash the SBF file you downloaded with RSD Lite
6°Live to win!
UPDATE: link from Team US Cellular seems to be down. I'll personally upload the file once I get home tonight.
Yeah. Praise US Cellular.
Sprint can I haz 2.3.5 yet?
Thanks so much for unbricking my Photon
Worked like a charm for mine !
Thanks !!!!
firtermish said:
I want to thank Koriotto and everyone else who suggested and or tried the idea of flashing a 2.3.5 rom to save our backs. Now to everyone who has flashed 2.3.5 electrify pudding into their photons:
Disclaimer:
1°This will bootlock your phone until a working pudding for 2.3.5 is released.
2°I have no idea whether this will work with sprint whatsoever since I can't try it out being an "international" user, but at least your phone won't be a total brick. However, my common sense tells me this most likely won't work with Sprint.
1°Try to get as much juice as you can to your battery.If you can, use someone else's fully loaded battery or charge yours with an universal battery charger (extremely cheap and easy to find). Your phone won't charge while in rsd or fastboot mode.
2°Download and install the appropriate Motorola drivers (x32 or x64 according to your windows flavor)
Click to expand...
Click to collapse
the download link doesn't work,would u plz give u a new download link,I need to unbrick my phone.
Thank u.
motiam4 said:
the download link doesn't work,would u plz give u a new download link,I need to unbrick my phone.
Thank u.
Click to expand...
Click to collapse
Original link went went down. Already corrected with one from Team US Cellular. Happy downloading
any updates with unlocking the bootloader for 2.3.5 flashed from sbf?
I tried to reload the stock 4.5.141 image using the instructions in post 4 of the Solutions to Common Problems thread.
I erased cache, erased userdata, flashed boot and flashed system, and all the messages looked OK. On reboot I got the dreaded message. I can't get back to fastboot.
I have downloaded RSD Lite 6.1.4 and it sees the phone, so I hope it's possible to get something on the phone.
What now?
kjmck said:
I tried to reload the stock 4.5.141 image using the instructions in post 4 of the Solutions to Common Problems thread.
I erased cache, erased userdata, flashed boot and flashed system, and all the messages looked OK. On reboot I got the dreaded message. I can't get back to fastboot.
I have downloaded RSD Lite 6.1.4 and it sees the phone, so I hope it's possible to get something on the phone.
What now?
Click to expand...
Click to collapse
C
Download 4.5.141 sbf use rsd lite..rsd always fixed mine bricked many times.if u was on 234 must lock boot loader use 234 sbf rsd.then go up.to 236
markwoo said:
C
Download 4.5.141 sbf use rsd lite..rsd always fixed mine bricked many times.if u was on 234 must lock boot loader use 234 sbf rsd.then go up.to 236
Click to expand...
Click to collapse
Thank you. I kept looking after I posted, but all the links to .sbf from this forum were dead. I was on Android 2.3.6, build 4.5.141.
The only .sbf I could find was entitled "1FF-olympus-user-2.3.6-4.5.141-111212-release-keys-signed-ATT-US-GAS_NA_OLPSGBATTSPE_P012.sbf".
Now I need to find someplace to charge the battery to attempt the re-flash. Screwing up the previous flash also killed the battery.
I understand that if I'm "Starting RSD mode" the only thing I can do to get a working phone is flash a .sbf using RSD Lite.
Is that true?
kjmck said:
Thank you. I kept looking after I posted, but all the links to .sbf from this forum were dead.
Click to expand...
Click to collapse
All SBF files have been removed from XDA because they are too dangerous.
ravilov said:
All SBF files have been removed from XDA because they are too dangerous.
Click to expand...
Click to collapse
Can you recommend a "safe" alternative for me?
kjmck said:
Can you recommend a "safe" alternative for me?
Click to expand...
Click to collapse
Did you go through this thread? There's a common solution to the "failed to boot" problem.
That said, there are times when you just have to use a SBF and there is no alternative. However, since dealing with SBFs is potentially dangerous, no one around here with experience will ever recommend you that, nor will they give you support. It's just too much responsibility. Kinda sad to say, but if that is really the case (that there is no other way but SBF), you're pretty much on your own.
It's worse now.
I went back to the linked thread, downloaded Automatic Bootloader Unlock 4.2 and fired it up.
Option 3 only works for people who can get to fastboot. That's not me.
I looked at the bold note below about flashing the 4.5.91 sbf using RSD Lite 5.3.1. So I uninstalled RSD Lite 6.x and installed RSD Lite 5.3.1. When I tried to flash 4.5.91 it got to the end and gave a message "Internal error programming phone".
Now I still see "Failed to boot 4" (NOT 0x1000) and "Starting RSD mode", but now RSD doesn't see the phone.
Am I REALLY SCREWED now?
It's better now.
I tried nottach's way of getting fastboot: hold power and volume-up while inserting the battery.
Once I had fastboot I tried again flashing 2.3.6, with the same result.
I still had fastboot, so I tried to flash recovery using Autounlock 4.2. It failed with
Code:
erasing 'recovery' ... FAILED (status read failed (too many links))
sending 'recovery' ... OK
writing 'recovery' ... FAILED (status read failed (too many links))
My phone came newly-refurbished from Motorola, with 2.3.6 build 4.5.141. I had rooted (but not unlocked) my previous phone and backed up everything with Titanium Backup. I had rooted and restored everything to the new phone, but the system would not allow me to register fingerprints and would not perform a factory reset. So I had tried to flash a fresh system; that's how I got to "Failed to boot 4".
I may still be able to return this phone to Best Buy on the grounds that it would not do fingerprints or resets, so I am reluctant to try unlocking the BL unless I'm reasonably sure it will work, but if I can get to a working system I could at least use the phone.
I have a working Eclipse environment on my laptop. Might this be a way to re-format the partitions on the phone so I can flash recovery, boot and a system?
I reviewed more carefully posts 2 & 4 in the Solutions to Common Problems thread, and realized I had slightly different command files (no fastboot.exe, just moto-fastboot.exe). I downloaded the one specified in the post, and tried to flash AT&TGB234_boot.img and AT&TGB234_system.img (I renamed them to boot.img and system.img).
When I rebooted this time I got
Code:
SVF:108:2
Failed to boot 3
Starting RSD mode
I'm still looking for a way to a working phone.
Try flashing the unlock SBF (pudding) before going to fastboot, and then try flashing boot and system from fastboot.
ravilov said:
Try flashing the unlock SBF (pudding) before going to fastboot, and then try flashing boot and system from fastboot.
Click to expand...
Click to collapse
SORRY for ur problem i know they say sbf are not safe but me i never had 1 single issue using it mine said the same thing and went failed to boot fastboot all i did was plug the phone into rsd used the 236.sbf you mentioned early and restored it back never failed me used rsd over 100 times with 5 different atrixes never had a single issue i can recall...i had to cut a usb cable tape red wire to + and black to - on the battery my phone was in fastboot that was all had to work with but it ran rsd fixed it i have seen failed to boot a few times using rom manager to install recovery before if u can get the sbf u talked about its worth trying i have it but dont know how to share it with u. mine was under warrranty i told AT&T i got the over the air 236 update and it said failed to boot they called motorola moto said give that man a new phone i didnt however share the fact the bootloader was unlocked and rooted and had tried many diffrent roms on it over a period of time but however i did end up fixing it and sent the replacment back.if u are usa att not sure about internation the sbf u mentioned is the 1 i use....not sure what u was trying to do that got u into this the sbf pudding mentioned is safe and have used it in the 234 days but to me since 236 has come out rsd never seemed to me to be an issue..mine is 4.5.151 now they say u cant go back haven't tryed that..lol but i dont use the phone now got me htc one x+ now.hope u fix ur phone man....
ravilov said:
Try flashing the unlock SBF (pudding) before going to fastboot, and then try flashing boot and system from fastboot.
Click to expand...
Click to collapse
THANK YOU!
I knew I had seen "pudding" before, and I found it in the Automatic Unlock 4.2 folder. I had tried doing this from the menu, but it failed. I opened Main.bat and found the SDL command line to flash pudding, and when I did it from the command line it worked!
Installing 4.5.141 from fastboot failed, so I tried to flash recovery but that failed too.
I went back to Automatic Unlock. Unlock completed successfully, but the follow-ons did not. I should have made notes as I went.
I was able to boot the phone into 4.5.141, and installed SuperUser.apk, SetCPU and Titanium Backup * Root. SetCPU runs, so I'm both unlocked and rooted.
If I hadn't seen your message I'd have taken the phone to Best Buy today. Your suggestion was the key. I have my phone back, and you have my thanks.