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.
Related
Guys I'm new to the forum but have been messing around with custom pseudo-roms for the Atrix for a little while now. I was running Adeo, then Gingerblur, then Greyblur all without a hitch when I heard about the new OTA update coming to the phone and Gingerbread coming up, so I wanted to go back to any build that would allow me to get the HSUPA update as well as the gingerbread update, but when I went to flash my phone to sbf using rsdlite, it said internal programming fail and nothing else happened. I installed gingerblur over greyblur in an attempt to see if it would flash, but nothing. Have done a factory data wipe, still can't flash. I can't even get into the stock Android Recovery, all that comes up is a triangle and exclamation point. Could someone please help me out here, I'm running gingerblur on a rooted Atrix on 1.5.7 and cannot get it to flash sbf, all I want to do is go back to stock att rom for the coming updates.
Thanks,
BK
Hey,
I have the same exact set up as you. It seems vague in your post if you re-flashed back to 1.26, and that may be why you're getting errors? Every time I update roms, I re-flash to 1.26 using the method in the link below.
http://forum.xda-developers.com/showthread.php?t=991072
Then I ran Gladroot to unlock, enable sideloading, etc.
http://forum.xda-developers.com/showthread.php?t=1016060
Downloaded and install the 1.83 update online (not on-air because I didn't get prompted)
http://www.motorola.com/consumers/v/index.jsp?vgnextoid=9098bc50a569f210VgnVCM10000081bbb00aRCRD
I ran the 'afterupdate.bat' on Gladroot after installing the update.
And I now have 2.2.2 / 1.8.3
Thanks bud, what I ended up doing was trying to manually uninstall gingerblur and greyblur and the adeo rom by using scripts etc but it never worked. My phone started acting weird, the home button stopped working, no 3g connectivity, it would say I have superuser but it wouldn't be rooted... something was seriously messed up. I tried to get into the stock android recovery but it wouldn't boot, I think something was corrupted. I knew sbf files rewrite system and boot data, so I went into tenfar's custom recovery (after rooting for the 10th time) and deleted system and boot data, system data was deleted, but boot data had an error. I wiped the caches and all and I tried to sbf flash to 1.8.3 but nothing and the phone bricked. I then tried it on another computer with more memory than mine (mine was running kind of low because of a linux partition) and the flash worked and I'm on 1.8.3. I think I'll wait for official gingerbread and unlocked bootloader in July before I mess with my phone again.
I'm sorry if somebody already posted that, i swear I had a look
I have a SIM unlocked AT&T MB860 Atrix with gingerblur 4.5, and I would like to try some real gingerbread goods, which means bootloader unlock and 2.3.4 HKTW.
Do I have to flash back to 1.8.3 stock sbf before actually unlocking and installing gingerbread? I heard people saying is not safe to flash sbf for SIM-Unlocked Atrix because it can cause Wi-Fi problems, is it still the case?
Second problem: I had my phone rooted, but now I don't have an external micro SD card, so I wouldn't be able to root with gingerbreak-similar methods, is this a deal breaker or there is another way to complete the process all the way through?
Thanks a lot
As a general rule, it's best to flash back to stock before flashing anything else. Because Gingerblur requires Tenfar's recovery to run, I believe this will be the best way to do this. If someone else could chime in about the SIM-unlock/wifi issue, that would be great.
As for the rooting method on 2.3.4 HKTW, it works by installing a ZIP through recovery. In my own experience, it only seems to read external SD cards. If you can make it read the internal somehow, then you should be able to root.
i was on GingerBlur 3.1 (rooted via GladRoot), and did the following over the weekend
- flashed the unlocker SBF (still on 1.8.3)
- flashed the new CWM onto the phone via fastboot
- flashed GingerBlur 4.5 using that CWM, just for a few days
- flashed the 2.3.4 IMG using the Windows x64 guide in the general forum.
ran into no problems, and the GB build was already rooted when it booted up.
dLo GSR said:
i was on GingerBlur 3.1 (rooted via GladRoot), and did the following over the weekend
- flashed the unlocker SBF (still on 1.8.3)
- flashed the new CWM onto the phone via fastboot
- flashed GingerBlur 4.5 using that CWM, just for a few days
- flashed the 2.3.4 IMG using the Windows x64 guide in the general forum.
ran into no problems, and the GB build was already rooted when it booted up.
Click to expand...
Click to collapse
Good to know, thanks!
Did you clear data or anything like that after flashing?
jwhited said:
Good to know, thanks!
Did you clear data or anything like that after flashing?
Click to expand...
Click to collapse
oh, right, forgot. i did do the fastboot -w beforehand.
i have simunlocked atrix as well, it makes no difference.
I went from Greyblur straight to GB with no issues.
Thanks guys
This is worth a try
If I wanted to return to the stock ROM after flashing 2.3.4, all I have to do is RSDLite flash 1.8.3 back correct and then restore using CWM?
kshiuan said:
If I wanted to return to the stock ROM after flashing 2.3.4, all I have to do is RSDLite flash 1.8.3 back correct and then restore using CWM?
Click to expand...
Click to collapse
I just did this tonight, and for some reason, I had some problems flashing the 1.8.3 SBF directly. So I downloaded the 1.2.6 (shipping) firmware and just did the updates.
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...
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?
Hi,
I got a refurb Atrix 4G from AT&T today in the mail to replace my Atrix 4G that had the wifi/bluetooth radio go bad.
Anyways, I attempted to root this new Atrix using the method from here: Atrix Forums root 4G using fastboot.
If you'll note, those instructions omit the 'chmod' command that is found on the instructions here on xda (I downloaded the preinstall.img from xda, since the other link was bad)
After I rooted, (but I have not rebooted) I transferred using USB mass storage everything that was on my old atrix (I told windows to overwrite everything during the copy)
I also used ADB to push Titanium Backup APK.
After that, the phone restarted unexpectedly.
The phone would startup and restart partially through the startup, occassionally I would see the unlock screen for a moment, but usually it would constantly cycle through the Motorola animation then turn off with the green led, then back on.
I figured I messed up the root or something, so I used the Android Recovery to wipe my user data and cache, that didn't work, so I used RSD Lite and pushed the signed ATT 4.5.91 SBF to the phone. I wiped the user data/cache using Android Recovery again after the sbf. Still the same reboot cycle.
Anything else I can try to revive it?
forum.xda-developers.com/showthread.php?t=1421261
This, then SBF again (with the latest RSD lite).
Still broken?
If you aren't unlocked, do so, then maybe try a fruitcake.
PM me with issues.
I got errors from fastboot when it erased system/boot/webstop/preinstall... Trying RSDLite again.. then unlock, will report back.
I erased partitions (with errors see above), rsd'd the OTA locked sbf again, then I unlocked, still rebooting.
I'm thinking it's something hardware-related since the phone will get all the way to the unlock/motoblur setup screen after a battery pull. but will only do the moto-logo after that.
Can I undo the unlock if I need to send it back? It's not clear to me if using RSD lite with the OTA locked signed ATT 4.5.91 sbf will brick it..
tuxp3 said:
Can I undo the unlock if I need to send it back? It's not clear to me if using RSD lite with the OTA locked signed ATT 4.5.91 sbf will brick it..
Click to expand...
Click to collapse
Can't lock it again.
Great, will ATT take it back? I've only had it a few hours and the problems began before I unlocked.
Dunno. I personally haven't read any reports of phones being rejected for warranty because of an unlocked bootloader, but since you only just got it as a replacement for another one, they may scrutinize you more.
Does it seem like it could be a battery issue? I'd like to think it's not, but my old phone had a similiar rebooting problem (although it would reboot well after startup)