[Q] Help with update to gingerbread!!! - Atrix 4G Q&A, Help & Troubleshooting

Hi, there are probably numerous questions similar to mine, but I couldn't find the right thread for me.
I recently unlocked my atrix's bootloader, and tried to update to the gingerbread update. Ultimately, I wanted to flash the Alien rom, but the gingerbread update (not the OTA one), caused my phone to be stuck on the Moto logo, so I flashed the 1.2.6 sbf on my phone.
Now, I'm not sure what I should do to update my phone to gingerbread since I read that if I update directly from 1.2.6, I will hard break my phone. What should I do?
By the way, I have been having troubles with an update to 1.8.3 via sbf. It keeps saying that the phone did not enumerate.
Thanks for all the help!!

phillyf8n said:
Hi, there are probably numerous questions similar to mine, but I couldn't find the right thread for me.
I recently unlocked my atrix's bootloader, and tried to update to the gingerbread update. Ultimately, I wanted to flash the Alien rom, but the gingerbread update (not the OTA one), caused my phone to be stuck on the Moto logo, so I flashed the 1.2.6 sbf on my phone.
Now, I'm not sure what I should do to update my phone to gingerbread since I read that if I update directly from 1.2.6, I will hard break my phone. What should I do?
By the way, I have been having troubles with an update to 1.8.3 via sbf. It keeps saying that the phone did not enumerate.
Thanks for all the help!!
Click to expand...
Click to collapse
I'm surprised you aren't already hardbricked.. Use the OTA updates until 1.8.3 (RSD shouldn't be used at all really) and then re-root and unlock whatever using: http://forum.xda-developers.com/showthread.php?t=1182871.
If it did not reenumerate, then all you should do is boot back into RSD and see whether that fixes it.

http://forum.xda-developers.com/showthread.php?t=1163342
this gives stock 2.3.4 without touching bootloader

Related

[Q] Still asking for update on 1.8.3 and gingerblur 3.5

So i have flashed back to both 1.26 and 1.57 then went OTA to 1.83 and i have also flashed 1.83 and then rooted installed gingerblur and i still have the update notification. i have looked at the build.prop and it tells me i am on 2.2.2 and at 4_1.8.3. Has anyone found out how to fix this without freezing the updater?
roughriduz said:
So i have flashed back to both 1.26 and 1.57 then went OTA to 1.83 and i have also flashed 1.83 and then rooted installed gingerblur and i still have the update notification. i have looked at the build.prop and it tells me i am on 2.2.2 and at 4_1.8.3. Has anyone found out how to fix this without freezing the updater?
Click to expand...
Click to collapse
This has been discussed several times in several forums. Just freeze "Updater 2.2.2" in Titanium Backup and the message won't show again.
Search tool is your friend
Freezing will prevent future updates, as the updater will keep telling you to update to 4.1.83 after you thaw it before it will allow you to OTA to next update. While this may not be an issue if a sbf file comes out for the next OTA, it will be an issue if there is not one available for a while after the OTA goes beta and live.
I flash back to 4.1.26, then OTA to 4.1.57 and 4.1.83 before rooting and installing the "ROM" of choice and have not seen this issue. Most posts I have seen relating to this are after people have flashed the 4.1.83 sbf.

[Q] Gobstopper Bell 2.2.2 - 2.3.4 OTA

Hi Guys,
I have successfully installed Gobstopper Bell 2.2.2 and then proceed with updating thru OTA to 2.3.4. It all went well and my phone is working.
after a few minutes, i realized i do not have the CWM recovery anymore and my phone is no longer unlocked.
Can i still use the Ihop unlocker here. http://forum.xda-developers.com/showthread.php?t=1136261
and can someone please explain to me the 1.8.3 bricks coz i keep seeing this revision, that if you go higher than 1.8.3 and then revert back to a lower version, you will get a brick. ive been trying to understand this for days now but i can't find it anywhere. is this the android version? baseband? system version or kernel?
If ur att atrix user and after ota 2.3.4 u sbf back to old version ull brick ur phone.
If ur int user, and want to go back use gobstoper or fruitcake it will be like a chicken.

[Q] [q] Failed to boot 2 - hard root or no?

Yes I made a mistake (**** happens) and now when I boot my phone i get "Failed to boot 2"
and it goes into SBF mode. prior to this I was on gingerbread 2.3.4, on bell in canada.
I've seen guides offering a 2.1.1 SBF that can be used to fix a phone, but I'm worried using this will brick my phone since I'm on 2.3.4
I've seen plenty of warnings not to use an ATT SBF, but nothing about using an older bell version.
derkinit said:
Yes I made a mistake (**** happens) and now when I boot my phone i get "Failed to boot 2"
and it goes into SBF mode. prior to this I was on gingerbread 2.3.4, on bell in canada.
I've seen guides offering a 2.1.1 SBF that can be used to fix a phone, but I'm worried using this will brick my phone since I'm on 2.3.4
I've seen plenty of warnings not to use an ATT SBF, but nothing about using an older bell version.
Click to expand...
Click to collapse
why don't you just reflash a 2.3.4 sbf? i wouldn't risk hard bricking your phone; as long as you can get into RSD mode and can flash a sbf with RSD Lite, then you're fixable.
or better yet, reflashing the pudding .sbf (if you're unlocked)
btw, what was the mistake you made? this can help me solve your problem.
there is no 2.3.4 sbf available for bell, and i didnt unlock
my mistake was trying to install CM without unlocking the bootloader, i misread some things, and I'm kicking it myself now.
I did see one thread during my searching of a guy who successfully used an AT&T 2.3.4 SBF on his bell atrix, so I'm contemplating trying that
other than that I can try sending it in and getting the phone repaired (which will most lilely be denied based on me voiding the warranty) and past that, I drop 500 bucks on a new phone, and being a teenager saving for univeristy, thats annoying.
So I loaded up the AT&T sbf in RSD lite, and it wouldnt even let me try to flash it
as a shot in the dark i tried using pudding (IHOP), and it tried, and failed.
pretty much out of ideas at this point, only bell has the sbf my phone truly needs so I'm gonna take it in tomorrow and hope for the best.

[Q] Clarifications on Updating to 2.3.6

Ok, I know there are a lot of posts already on updating to 2.3.6 and root, but there appears to be a lot of different situations and limited information that is causing me some confusion.
So, what I want to do is get some clear details about probably the second most common situation: A Motorola Atrix 4G running the stock ROM with root access and an unlocked bootloader.
With regards to updating, aside from the obvious actions (i.e. TiBu, maybe a Nandroid), is there anything else that needs to be done to perform the update?
Additionally, I would like to keep root/unlocked even with the update, but I am willing to re-do root after the update. I can't find clear information on what methods work to keep root or to restore root after updating.
That is pretty much all that I am trying to do. I can not afford to brick my phone, so I want to make sure that I understand everything before I update.
P.S. Curse Motorola and it's stupid locked bootloaders!
I'm in the same shoes and looking to do the same thing...I want to keep root, not brick my phone...Apply the 141 update. I don't mind a little work (re-root, re-modify some files)
I'm running an unlocked bootloader, AT&T Atrix with 4.5.91 which is rooted with some custom changes (tethering, 2g/3g toggle, unlock APNs, agps)
Seems it could be possible to rebuild Blur_Version_91.4.5.141.MB860ATT.en.US available from Motorola and exclude the bootloader portions to keep the phone from bricking?
psychephylax said:
I'm in the same shoes and looking to do the same thing...I want to keep root, not brick my phone...Apply the 141 update. I don't mind a little work (re-root, re-modify some files)
I'm running an unlocked bootloader, AT&T Atrix with 4.5.91 which is rooted with some custom changes (tethering, 2g/3g toggle, unlock APNs, agps)
Click to expand...
Click to collapse
Yeah, I used the script that applied the tethering/hotspot tweak. That's about it. I haven't had to use any agps or anything, it's got amazing gps as it is.
Glad I'm not the only one though
If you have a stock rom unlocked bootloader with root don't do the ota update.I just soft bricked my phone.
Sadly, I did just that. I just wasn't paying attention.
Update: resorted to a factory reset. Now I have 2.3.6 running. Just going to take some time to restore my apps and settings.
Looks like I'm in the same boat. What's the best way to recover from a soft-brick in this situation?
thatguy193 said:
If you have a stock rom unlocked bootloader with root don't do the ota update.I just soft bricked my phone.
Click to expand...
Click to collapse
Yeah, this is exactly why I have asked. I read at least one post somewhere where someone tried both the SD Card and the OTA update and the SD didn't work, but the 2nd OTA try did. I don't know if they said they had unlocked or not.
Johnston212 said:
Yeah, this is exactly why I have asked. I read at least one post somewhere where someone tried both the SD Card and the OTA update and the SD didn't work, but the 2nd OTA try did. I don't know if they said they had unlocked or not.
Click to expand...
Click to collapse
Well I found this threadhttp://forum.xda-developers.com/showthread.php?t=1498856 was trying the auto updater as suggested but my phone wont stay on long enough for it to work.It does the auto shutdown and tries re-installing the OTA update which gives me the android triangle guy.
I recently made an update of my Atrix 4G's System from 2.3.4 to 2.3.6.
My 2.3.4 version was unlocked and rooted. It is on ATT.
Initially I received a notification in my phone about the new System update available. I tried three times OTA, but each time the process failed. When it was booting up always gave me the Android Icon with an Exclamation mark inside of a triangle. But nothing else happens. My phone continued working but with the 2.3.4 version.
Then I went to this page:
Because I haven't less than 8 post in this site I can't post any URL.
But, go for the "Motorola software update" in the Motorola's web page or Google it and get it.
And installed the "Motorola Software update" application. I had to restart my PC in order to make the software to recognize and connect to my Atrix 4G. When the Atrix was connected, by USB port, I had to select the "Windows media Sync" in the USB connection options list to make the connection to work.
Then, all that I had to do was wait until the process got completed.
I hadn't see nothing different with the new update.
I conserved my "unlocked" condition but I lost my "Rooted" condition. But that is not a big issue, there are several thread in the web that help you to get rooted again.
Hope this can help, It works for me.
cjfermin said:
I conserved my "unlocked" condition but I lost my "Rooted" condition. But that is not a big issue, there are several thread in the web that help you to get rooted again.
Hope this can help, It works for me.
Click to expand...
Click to collapse
You have an unlocked bootloader? Or sim-unlocked phone?
I'm in the same situation of @cjfermin and the 2.3.6 was flashed without any problem.
Of course I've lost ROOT, but I've followed simple instructions on the web (using Fasboot) and I've re-rooted the Atrix in 3 minutes.
PS: my Atrix was/is sim-unlocked and with unlocked bootloader.
emandt said:
I'm in the same situation of @cjfermin and the 2.3.6 was flashed without any problem.
Of course I've lost ROOT, but I've followed simple instructions on the web (using Fasboot) and I've re-rooted the Atrix in 3 minutes.
PS: my Atrix was/is sim-unlocked and with unlocked bootloader.
Click to expand...
Click to collapse
Thanks, that is exactly what I was needing to find out. I've heard yes and no's on different re-rooting methods. Could you link the one that you used? I was thinking about using Gingerbreak or OneClickRoot
I was trying to apply the OTA 4.5.141, on my rooted AT&T Motorola Atrix stock rom 2.3.4 and after the first reboot, following the instructions from the update, I am getting the message “failed to boot 2 starting rds mode” and just sit there. After removing the battery and booting up again, the phone seems to booting up normally and then when the phone finishes loading most of the widgets, I get a message saying “turning off” and the same cycle keeps repeating.
This is my primary phone and I am really desperate right now and I do not know what to do.
Please I need some help,
Johnston212 said:
Could you link the one that you used?
Click to expand...
Click to collapse
Here: http://www.android-advice.com/2012/root-the-motorola-atrix-4g-running-4-5-141/
Hope that helps you!
Alverik said:
I was trying to apply the OTA 4.5.141, on my rooted AT&T Motorola Atrix stock rom 2.3.4 and after the first reboot, following the instructions from the update, I am getting the message “failed to boot 2 starting rds mode” and just sit there. After removing the battery and booting up again, the phone seems to booting up normally and then when the phone finishes loading most of the widgets, I get a message saying “turning off” and the same cycle keeps repeating.
This is my primary phone and I am really desperate right now and I do not know what to do.
Please I need some help,
Click to expand...
Click to collapse
Ok, is your bootloader unlocked as well? I googled the "failed to boot 2 starting RSD mode" that you mentioned and there are a number of posts on it from over the years. It seems that you may need to flash a SBF file, but I don't know enough about your situation to competently tell you more than that.
Johnston212 said:
Ok, is your bootloader unlocked as well? I googled the "failed to boot 2 starting RSD mode" that you mentioned and there are a number of posts on it from over the years. It seems that you may need to flash a SBF file, but I don't know enough about your situation to competently tell you more than that.
Click to expand...
Click to collapse
I am on stock rom 2.3.4 and have only rooted my phone nothing else. It seems that because it was a rooted phone the update could not finish the process.
Now I don’t know what to do.
Should I try to flash to 2.3.4 using RDS lite and then update using OTA 4.5.141 or flash using 4.5.141 (I don’t know where to find it)?
Help please, this is my only phone.
Alverik said:
I am on stock rom 2.3.4 and have only rooted my phone nothing else. It seems that because it was a rooted phone the update could not finish the process.
Now I don’t know what to do.
Should I try to flash to 2.3.4 using RDS lite and then update using OTA 4.5.141 or flash using 4.5.141 (I don’t know where to find it)?
Help please, this is my only phone.
Click to expand...
Click to collapse
If the only thing you've ever done to the phone is root then flashing the official 2.3.4 (not fruitcake) with RSDlite and then applying the 141 OTA update should be ok. Things to note:
1) Make sure the phone is fully charged
2) Apply the 141 OTA update from sd card. Go to motorola's website . I've had mixed results when applying previous updates when downloading over wifi.
3) Be VERY sure you've done nothing else to your phone other than root, i.e. unlock, mess with the bootloader and/or recovery (unlock, ROMs).
gnahc79 said:
If the only thing you've ever done to the phone is root then flashing the official 2.3.4 (not fruitcake) with RSDlite and then applying the 141 OTA update should be ok. Things to note:
1) Make sure the phone is fully charged
2) Apply the 141 OTA update from sd card. Go to motorola's website . I've had mixed results when applying previous updates when downloading over wifi.
3) Be VERY sure you've done nothing else to your phone other than root, i.e. unlock, mess with the bootloader and/or recovery (unlock, ROMs).
Click to expand...
Click to collapse
The only thing that I have done other than rooting my phone it’s unlocking the sim card.
I don't have a SIM unlocked phone, so I can't with 100% certainty say you will be ok. You should be fine though. Maybe others with SIM unlocked phones will chime in.
gnahc79 said:
I don't have a SIM unlocked phone, so I can't with 100% certainty say you will be ok. You should be fine though. Maybe others with SIM unlocked phones will chime in.
Click to expand...
Click to collapse
I am not able to copy the update file to the SD card because I get a message saying “turning off” a little bit after the phone loads the sd card and then I get the "failed to boot 2 starting RSD mode" and after that the only way to take it out of that mode, it’s by removing the battery.
What options do I have now?
Thank you,

[Q] Big problem after OTA 4.5.141

I was trying to apply the OTA 4.5.141, on my rooted AT&T Motorola Atrix stock rom 2.3.4 and after the first reboot, following the instructions from the update, I am getting the message “failed to boot 2 starting rds mode” and just sit there. After removing the battery and booting up again, the phone seems to booting up normally and then when the phone finishes loading most of the widgets, I get a message saying “turning off” and the same cycle keeps repeating.
This is my primary phone and I am really desperate right now and I do not know what to do.
Please I need some help,
You could try to use RSDlite to flash the official 4.5.91 SBF, info in the 2.3.6 OTA thread and then apply the 141 OTA. There's still a chance that the update will fail though . Worst case you will have to use fruitcake 2.3.4/2.3.6. Info on that is also in the same thread. If you just want your phone to work with no hassle use fruitcake and don't apply the official OTA update.
Thank you for the information it was very helpful.
I am pretty new on android and my experience has been on windows mobile phones mainly (flashing, unlocking and installing roms) and I can see know that my problem it’s that I tried to update my phone without removing the root access.
Now I have RDS lite 5.6 and I am trying to find the official 2.3.6 stock rom and because this is my first time flashing an Android phone, I am very nervous to tell you the truth and I don’t want to brick my phone. It’s there any tips you have to not screw up the whole thing.
I am following a guide found on atrix forums to use RDS lite to flahs my phone. [HOW TO] Use RSD Lite to Flash a SBF File - Motorola Atrix.
Thank you again,
I got it working again following the suggestions from Atrixforums.com. What I did was to flash my phone with RDS lite v5.6 using the file 1FF-olympus-user-2.3.4-4.5.91-110625-release-keys-signed-ATT-US-GAS_NA_OLPSGBATTSPE_P011 and that fixed my phone and it’s been working normally.
Notes:
My phone was using the stock rom version 2.3.4
Rooted (I did not remove the root access before applying OTA 4.5.141 and this is reason why I got in this problem)
Locked bootloader (I am not sure if this method will work with an unlocked bootloader)
Unlocked sim card
Thank you,

Categories

Resources