[WARNING] v4.5.141 Causing Problems

[gnahc79]

That post more or less just describes what you do if you try the update and it fails and to just not update, unless im just reading it wrong.

If i am reading it wrong, and you can update, then i dont get his last point for sure.

You run the risk of a soft brick if you do a straight up OTA update on an unlocked bootloader with non-stock recovery. One or more of the conditions seems to fubar the update: unlocked bootloader, non-stock recovery, rooted. Following step#1 restores everything except for the bootloader I think.
Or just use TiBu to freeze Updater to get rid of the notification update and deal with all of this whenever the official ICS comes around.

 

[eclypse3demons]

I see a lot of posts that are all over the map, so I'm just going to put it all down here (what I know anyway). This applies to US/AT&T devices only but may work elsewhere.

1. If you RSD back to 4.5.91 then update you will have no issues.

2. If you use CWM to restore an un-rooted 4.5.91 (which also means you have an unlocked bootloader), after you get the OTA update it will apply the update but you will get a "failed to boot 4, starting RSD" message. To clear this, use RSD to re-install pudding. The device will reboot, perhaps twice, then start up on the .141 build with no further issues and you will remain unlocked.

3. If you didn't bother to make a backup of your stock image and rooted, re-root before accepting the update.

4. I don't know if there is a way to stop the update notifications. From what I understand there isn't unless you do some tweaking/hacking. I'm sure a search will yield results.

Yeah too bad I did not read the forums this morning when I saw my phone info stating there was an update. I was on 4.5.91 stock but rooted and bl unlocked, did the OTA, it rebooted, started the package install and got to about 25% or so and then errored with just a droid dude with an ! and a green triangle. Could not get past that point, pulled the battery rebooted it got back to the main screen, swipe to get to the desktop and then the phone would reboot and try the update on its own in a loop. Since I needed my phone fast I quickly blasted CM7 from the image stored on my SDCARD but now I have to go back and revert to 4.5.91 and see how to get the update again =( never runs smooth let me tell you.

 

[live4nyy]

I have seen many people stumped by the "Triangle w/ ! and Android character". That's just the stock Android Recovery screen. Has anyone just tried to press both Vol up and Vol down and see if it goes to the recovery menu?

Yeah too bad I did not read the forums this morning when I saw my phone info stating there was an update. I was on 4.5.91 stock but rooted and bl unlocked, did the OTA, it rebooted, started the package install and got to about 25% or so and then errored with just a droid dude with an ! and a green triangle. Could not get past that point, pulled the battery rebooted it got back to the main screen, swipe to get to the desktop and then the phone would reboot and try the update on its own in a loop. Since I needed my phone fast I quickly blasted CM7 from the image stored on my SDCARD but now I have to go back and revert to 4.5.91 and see how to get the update again =( never runs smooth let me tell you.

 

[eclypse3demons]

I have seen many people stumped by the "Triangle w/ ! and Android character". That's just the stock Android Recovery screen. Has anyone just tried to press both Vol up and Vol down and see if it goes to the recovery menu?

That did not work for me but rebooting the phone and using the normal key/button combos all worked with no issues.

I used moto-fastboot to revert my phone back to 4.5.91, cleared the data, then booted up as normal, then after setting up the phone I was able to use the software update tool directly from Motos website to do the update without any problems (unlocked bootloader). However I am not sure if the BL is still unlocked at this time after the update I assume its not.

 

[eclypse3demons]

I was able to root, but not use cwm after flashing recovery trying to get into recovery results in "failed to boot 2" error the it goes to rsd mode :/

Sent from my MB860 using XDA App

 

[t.s.eliot]

If you have an unlocked bootloader and used the pre-rooted SBF of 2.3.4 you'll soft brick every time. I tried it three times, soft brick each time. I was able to recover by an SBF of the pre-rooted 2.3.4 again.

I managed to upgrade successfully by using the Motorola upgrade tool on their support web page. Still had to redo the bootloader unlocking SBF, and the "fastboot oem unlock". However, after that everything seemed fine.

 

[againareku]

This is my current set up

2.3.4 stock (from phone not update or sbf)
rooted (1 click)
Unlocked bootloader
cwm recovery
Clemsyn kernel
2.3.6 leak radio
Pink theme (nottach i believe)
Bloat frozen with mybackup pro

So what do I want to do to not brick? Can I just unroot and ota update, reroot, flash the theme and clemsyn kernel? Or is there a longer safer process WITHOuT losing apps, settings, and texts?

I have mybackup pro so i can do it the long way but if i can avoid the hassle i would rather just ota update

 

[teeth_03]

Motorola software update tool

 

[dlgary13]

For the sake of clarity, will an unlocked bootloader with everything else, including recovery, being stock soft brick with the update?

Sent from my MB860 using xda premium

 

[UncleCemka]

For the sake of clarity, will an unlicked bootloader with everything else, including recovery, soft brick with the update?

Sent from my MB860 using xda premium

Seems like a mixed bag, some do, some don't. Try this method to make sure you don't brick: http://forum.xda-developers.com/showthread.php?t=1504519

 

[againareku]

More than one person has told me online and even offline once the bootloader is unlocked NOTHING can unlock it, the only thing that happens is the mssage gets erased but the bootloader is still unlocked

Anyways, so I tried the moto software tool and it couldn't find an update. What is to blame? the radio I was using from the 2.3.6 leak [36p not 37p] or the Clemsyn enhanced 1.0 kernel?

Since ALL the multiupload megaupload and mediafire links are dead..because they no longer exist, I could not find the original radio and kernel to flash

I also tried the OTA, it stopped half way and the screen displayed the android in triangle warning logo. Battery pull to get the phone back up, it forced reboot to attempt update again, so I reboot into recovery and wipe cache which stopped the reboot/install loop [displayed update failed message afterwards]

So I am kind of annoyed the only method is the manual one and all the restoring and recovering that comes with it.

I went ahead and flashed the 37p radio just to at least have the newest radio, for anyone who is stock rooted unlocked who hasn't, it definitely is worth it, wifi locks on almost instantly, obstructions don't slow down the signal, and I have slightly faster speed tests when using AT&T SIGNAL

but I really wish I could do an update without having to reinstall and restore everything. I'll do it for ICS because it is a major revision but I don't want to do 2 hours of work for a few unimportant security fixes [especially since the new radio fixed any wifi problem i had]

 

[UncleCemka]

Idea for you

More than one person has told me online and even offline once the bootloader is unlocked NOTHING can unlock it, the only thing that happens is the mssage gets erased but the bootloader is still unlocked

Anyways, so I tried the moto software tool and it couldn't find an update. What is to blame? the radio I was using from the 2.3.6 leak [36p not 37p] or the Clemsyn enhanced 1.0 kernel?

Since ALL the multiupload megaupload and mediafire links are dead..because they no longer exist, I could not find the original radio and kernel to flash

I also tried the OTA, it stopped half way and the screen displayed the android in triangle warning logo. Battery pull to get the phone back up, it forced reboot to attempt update again, so I reboot into recovery and wipe cache which stopped the reboot/install loop [displayed update failed message afterwards]

So I am kind of annoyed the only method is the manual one and all the restoring and recovering that comes with it.

I went ahead and flashed the 37p radio just to at least have the newest radio, for anyone who is stock rooted unlocked who hasn't, it definitely is worth it, wifi locks on almost instantly, obstructions don't slow down the signal, and I have slightly faster speed tests when using AT&T SIGNAL

but I really wish I could do an update without having to reinstall and restore everything. I'll do it for ICS because it is a major revision but I don't want to do 2 hours of work for a few unimportant security fixes [especially since the new radio fixed any wifi problem i had]

I've been playing with the following idea, that you might be able to use:
http://forum.xda-developers.com/showpost.php?p=22997305&postcount=22

 

[PanNet]

Wrong! I went back to stock and had "failed to boot 4, starting RSD mode" EVERY TIME!!!! Its this update period - its ****... something is effed up in it....

Hi, How did you get rid "Failed to boot 4, Starting RSD mode"?

 

[sunny1119]

Hi, How did you get rid "Failed to boot 4, Starting RSD mode"?

Not sure if it would work on not,but worked on mine....i got the same error while upgrading to 2.3.6 with unlocked bootloader using RSD lite, i just flashed again with RSD lite again and got a PASS

 

[BlueHarford]

I was able to recovery this issue on my fathers phone, i went into a panic when i saw that warning and read it was the same as what i had. i fixed it by


fastboot oem unlock

<get uid>

fastboot oem unlock <uid>
"say you accept on the phone"
fastboot reboot


i dont know if it forgot that it was unlocked but it worked for me, once his phone rebooted it worked. booted as normal.

 

[brandonmangan]

Deleted CWM (Somehow) How to recover softbrick.

I don't own an atrix myself, I'm sitting with a droid 3 but a friend of mine has a rooted Atrix, (As far as I can tell that must mean he has an unlocked bootloader?) and he somehow deleted CWM at some point a few days prior to receiving the new OTA. I've done an hour and a half of searching for links and how tos of flashing sbf/pudding to get back to stock via fastboot but every link I attempt to access is broken (as far as sbfs are concerned). This is foreign to me and I was wondering if any of you guys could tell me how to get on my way and restore his phone (I don't need to retain root or anything, I don't want this happening again), it'll be appreciated tremendously.

 

[consolation]

Root != unlocked + cwm. I'd try the automatic unlock tool, then flash a new recovery (as opposed to the old one installed by automatic tool, it won't work with most roms), then flash a cwm ROM.

 

[ladytya]

I'm getting errors in moto-fastboot

Error: cannot load CG59_0x00000130.smg, anyone else getting these errors?

 

[gnahc79]

Error: cannot load CG59_0x00000130.smg, anyone else getting these errors?

cg59 is the boot.img, is your phone bootloader unlocked? if so there's various threads here on how to get 141 on a bootloader unlocked phone.

 

[KSoD]

Well I have had a strange month with my Atrix. The story goes like this. First I was trying to get back to Stock. I had dropped my Atrix and the screen was not calibrating in the top inch of the screen. At the time I was on the Jokersax ICS CM9 KANG. I had hopes that a quick flash back to stock would allow me to fix the issue since I was reading reports about touch issues.

Instead I hard bricked my phone. Luckily I was 2 days before my warranty ran out and I got the call in time to get my replacement sent out. So I got my new (Refurbished) Atrix in with the 141 update. Needless to say I wasnt happy.

So first I tried to unlock it, but naturally all my means didnt work. I tried to see if I could unlock the bootloader which lead me to the dreaded:

Failed to boot 0X1000

I thought it was done for. But I got it fixed with this:

http://forum.xda-developers.com/showthread.php?t=1182871

Option #3 fixed the issue, unlocked my bootloader and got the phone booted back to Android. It was still unrooted, but the simple fact was it was working again. From there I installed CWM and flashed a new ROM as quickly as I could and have my Atrix back up and running.

Not sure if it will help anyone else out there. But this tool worked for me to get my phone away from the dreaded Failed to Boot.