I really want to try out the GB 2.3.4 update on my atrix, but I want to make sure that its as easy to flash back to stock as it is to flash the Gingerbread rom.
I'm already unlocked, and fairly familiar with RSDLite
I wouldn't recommend doing this - I tried 2.3.4 and now, when trying to flash sbf 1.8.3 My phone goes into boot loop, red led is blinking and then it goes from Motorola logo to blank screen.
Couldn't find solution yet.
****update:
I have managed to solve this issue easily: Flashed unlocked bootloader again after flashing sbf of 1.8.3 - So now, from my point of view the only the difference between now and then if you want to revert back is that you may need to keep unlocked bootloader (unlocked is written when booting so it may be an issue if someone plans on returning/replacing his headset) I don't care since I earned a decent recovery mode and if anything goes wrong I won't be able to step into at&t anyway.. (live overseas)
btw, when I tried to fastboot oem lock it says option is not implemented
Related
Has any one made a safe way to flash back to 2.2 without bricking the phone ? I don't like 2.3 at all and would like to flash back till it comes out officaly and the bugs are gone.
Yes. I unlocked my AT&T Atrix to flash 2.3.4. I had no issues flashing 2.3.4 but didn't really like the ROM. I installed the (full) 1.83 SBF using RSD lite and had no issues with the downgrade.
Be sure you use the full SBF, if you use a service release you will run into issues.
I flashed the 4.1.83 SBF, but the "Unlocked" disappeared from the boot screen. I suppose that's good if you need to send your phone back for warranty service, hehe. However, I like to see that my phone is unlocked every time I reboot it so I just flashed the unlock SBF again to get it back. You just have to flash it, not go through the unlock ID and all that.
Tikerz said:
I flashed the 4.1.83 SBF, but the "Unlocked" disappeared from the boot screen. I suppose that's good if you need to send your phone back for warranty service, hehe. However, I like to see that my phone is unlocked every time I reboot it so I just flashed the unlock SBF again to get it back. You just have to flash it, not go through the unlock ID and all that.
Click to expand...
Click to collapse
It's not as good as you think. The phone is still unlocked, the indicator just disappears. If you try to re-flash the unlock SBF, it won't write and you'll get a message that the phone is already unlocked.
Once unlocked, I'm pretty sure that it stays that way (unless Motorola re-locks it).
bal3wolf said:
Has any one made a safe way to flash back to 2.2 without bricking the phone ? I don't like 2.3 at all and would like to flash back till it comes out officaly and the bugs are gone.
Click to expand...
Click to collapse
This is why u always backup before u flash anything.
Sent from my MB860 using Tapatalk
If I flash back to the stock firmware using the motorola sbf files, will my bootloader remain unlocked? I flashed back and flashed the unlocking sbf file. When my phone booted up it said unlocked, even though I didn't run the fastboot commands. I then ran the fastboot commands anyway and it said the bootloader was already unlocked. So will the unlocked bootloader always remain unlocked?
No. It's locked again
Sent from my MB860 using XDA App
it stays unlocked... despite what ^^^ said >.>
but it wont show until you just flash the pudding sbf like you did
P.S. no known way to re-lock as of yet
xepter said:
it stays unlocked... despite what ^^^ said >.>
but it wont show until you just flash the pudding sbf like you did
P.S. no known way to re-lock as of yet
Click to expand...
Click to collapse
Ok, thanks. I wasn't planning on relocking, I was just curious. So next time I won't even have to flash the sbf? The sbf just makes the unlocking text show up when it boots up, but it should still allow me to do stuff like install the new CWM recovery without that, right?
Another thing, when I flashed that sbf, I didn't go into RSD mode. I was in a hurry and I forgot so I just ran the RSD program, and it detected my phone, so I clicked start. I realized later that I hadn't booted up into RSD mode...
Should I be worried? Was the RSD mode just an unnecessary precaution?
You can't relock..............it's a hardware unlock (fuse lock). When you unlock a fuse burns out, and that's end of story.
If you flash back to a different firmware the word "unlocked" will go away, but you are still unlocked. You can unlock again to make the word "unlocked" reappear on the boot screen.
EU sbf on AT&T possible?
I am going to use an unlocked AT&T Atrix in Europe.
I am on 1.83 firmware with root (made with gingerbreak to get rid of AT&T boot animation etc.).
If I go on with unlocking the bootloader, can I flash any european sbf/rom? Are there any simfree european tock sbf/rom-s out there, and which is best? What about the french 2.1.1 sbf?
I just need a stable stock firmware without the AT&T limitations, do not want changing roms all the time.
Also, do I get sw updates if I do this?
Ok here is the case.
I have couple of AT&T atrix here which belongs to friends. I am going to point down what is the current situation so someone out there help / warn me before I do something stupid.
1. I had unlocked the bootloader, rooted the phones and enabled sideloading on 1.8.3
2. OTA was flashed on these phones as soon as it was made available.
3. I received no warning or failed update. The update was successful and phone booted fine into gingerbread.
4. New bootloader was flashed hence I lost the Unlocked bootloader.
Now this is what I plan to do.
1 Use pudding to unlock the bootloader again.
2. I have seen people who get soft brick when they do this on OTA which is recoverable.
Now my question is, can i directly flash the new 2.3.4 SBF which is pudding + root + unlocked bootloader using RSD?
If yes, can I install latest CWM after I flash the new combined SBF using RSD. I know I can recover from soft brick by unlocking bootloader and flashing the SBF again as it goes back to fastboot after softbrick ( i recovered mine from soft brick couple of days back ). Just wanted some clarification regarding this particular situation.
I am not exactly a noob, but there are conflicting responses when I tried to search this. Thanks in advance,
Also can someone tell me where to check the status of efuse on atrix (location, original value and modified value to expect in case of blown fuse). All phones are rooted. So wanted to check if I have blown any fuse or not.
Hello to all
I receive an atrix 4g locked to at&t usa. I unlocked with a code, after i unlock the BL.
I install cwm and romracer and flash CM7(2.3.6) rom from sd.
After i flash Darkside(2.3.5) rom. Now i want to return back to stock.
I have some small problems, the soft keys light is very dimm and the wifi signal is very low compared with my previous iphone 4.
The question is: is it safe to flash 4.5.91(2.3.4) stock sbf with rsd?
I know that the other option are fruitcakes but i just want to know if i can flash this vers with rsd.
System version: 4.5.133.mb860.att.en.us
Android version 2.3.5
Baseband: N_01.77.30P
I read many threads about but i'm still in the "fog". I know that the answer is somewere on the forum and sorry for opening another thread.
Thanks a lot for understanding.
While it's not recommended to use RSDlite after unlocking the bootloader, it will work as long as you only use the 4.5.91 GB2.3.4 SBF (signed). I have done it twice but at my own risk of course.
If you need to return to stock you can flash the fruitcakes, which are stock files. This method is definitely recommended over sbf.
M_Alin said:
Hello to all
I receive an atrix 4g locked to at&t usa. I unlocked with a code, after i unlock the BL.
I install cwm and romracer and flash CM7(2.3.6) rom from sd.
After i flash Darkside(2.3.5) rom. Now i want to return back to stock.
I have some small problems, the soft keys light is very dimm and the wifi signal is very low compared with my previous iphone 4.
The question is: is it safe to flash 4.5.91(2.3.4) stock sbf with rsd?
I know that the other option are fruitcakes but i just want to know if i can flash this vers with rsd.
System version: 4.5.133.mb860.att.en.us
Android version 2.3.5
Baseband: N_01.77.30P
I read many threads about but i'm still in the "fog". I know that the answer is somewere on the forum and sorry for opening another thread.
Thanks a lot for understanding.
Click to expand...
Click to collapse
live4nyy said:
While it's not recommended to use RSDlite after unlocking the bootloader, it will work as long as you only use the 4.5.91 GB2.3.4 SBF (signed). I have done it twice but at my own risk of course.
If you need to return to stock you can flash the fruitcakes, which are stock files. This method is definitely recommended over sbf.
Click to expand...
Click to collapse
Will flashing the SBF via RSD re-lock the bootloader? I need to take my phone in for a warranty swap (hardware issue) and don't want them to know I unlocked the phone.
It will hide the "unlocked" text during boot but it does not actually re-lock the bootloader. But when you think about it, even though they never intended for the end user to unlock the phone (hence the encrypted/locked bootloader), they still put the warning in if/when anyone unlocked the bootloader. It's there for a reason but I doubt they will find out.
ItsLunchBOX said:
Will flashing the SBF via RSD re-lock the bootloader? I need to take my phone in for a warranty swap (hardware issue) and don't want them to know I unlocked the phone.
Click to expand...
Click to collapse
live4nyy said:
It will hide the "unlocked" text during boot but it does not actually re-lock the bootloader. But when you think about it, even though they never intended for the end user to unlock the phone (hence the encrypted/locked bootloader), they still put the warning in if/when anyone unlocked the bootloader. It's there for a reason but I doubt they will find out.
Click to expand...
Click to collapse
So yeah I was impatient and tried to flash it without waiting for a reply. It kept failing and then all I would get on my phone was "Failed to boot 4 Starting RSD Protocol".
I ended up having to re-flash pudding, which was an adventure in itself (upgrading RSD, rebooting computer, trying different USB ports & cables before it would finally take). I think I will just take it in tomorrow even with it saying "Unlocked" and see if they will swap it out. I'm having touch screen issues with intermittent dead spots and ghost touches.
Did you try the stock SBF with the same combination of port and cable as you did when you successfully flashed pudding? I've heard those two factors can cause a bad flash in the past. I've read that a back port on the computer is recommended for sufficient power and using the actual OEM cable the phone came with is highly recommended as well.
Oh well, hope you get it swapped out, the people at the AT&T stores (if that's where you got it) usually don't pay no mind to that anyways.
ItsLunchBOX said:
So yeah I was impatient and tried to flash it without waiting for a reply. It kept failing and then all I would get on my phone was "Failed to boot 4 Starting RSD Protocol".
I ended up having to re-flash pudding, which was an adventure in itself (upgrading RSD, rebooting computer, trying different USB ports & cables before it would finally take). I think I will just take it in tomorrow even with it saying "Unlocked" and see if they will swap it out. I'm having touch screen issues with intermittent dead spots and ghost touches.
Click to expand...
Click to collapse
Hi,
I do have the same kind of query. I have AT&T Motorola Atrix 4G. I unlocked SIM, unlocked BL, rooted and installed CWM recovery, De-dexed and Webtop over HDMI hacked. I am still on AT&T Stock ROM 2.3.4 / Build # 4.5.91
I am facing random reboot problem while using 3G data service. I want to re-flash Stock 2.3.4 ROM. As per your reply in this thread I can only do this by flashing Fruitcakes as I have unlocked BL ... right? But in this link I am bit confused which file to download and flash amongst 2.3.4 / 2.3.5 att 4.5.133 / ATT 4.5.140 - 2.3.6? Also, after flashing a fruitcake can I still flash a custom ROM later on and at any point of time revert back to stock?
Thanks so much.
live4nyy said:
While it's not recommended to use RSDlite after unlocking the bootloader, it will work as long as you only use the 4.5.91 GB2.3.4 SBF (signed). I have done it twice but at my own risk of course.
If you need to return to stock you can flash the fruitcakes, which are stock files. This method is definitely recommended over sbf.
Click to expand...
Click to collapse
If you want to go back to stock, as in the last "Official" build released by Motorola, then you want the 2.3.4 build. And as long as you use the fruitcakes you can go back to a custom rom at any time.
sony108 said:
Hi,
I do have the same kind of query. I have AT&T Motorola Atrix 4G. I unlocked SIM, unlocked BL, rooted and installed CWM recovery, De-dexed and Webtop over HDMI hacked. I am still on AT&T Stock ROM 2.3.4 / Build # 4.5.91
I am facing random reboot problem while using 3G data service. I want to re-flash Stock 2.3.4 ROM. As per your reply in this thread I can only do this by flashing Fruitcakes as I have unlocked BL ... right? But in this link I am bit confused which file to download and flash amongst 2.3.4 / 2.3.5 att 4.5.133 / ATT 4.5.140 - 2.3.6? Also, after flashing a fruitcake can I still flash a custom ROM later on and at any point of time revert back to stock?
Thanks so much.
Click to expand...
Click to collapse
Thanks for your early reply ... Just one thing more I wanna ask that if I flash ATT 4.5.140 - 2.3.6 fruitcake, then can I flash ATT 2.3.4 - 4.5.91 over it? Is the brick warning for going back to stock ATT ROM only after having BL unlocked?
Thanks for your help
live4nyy said:
If you want to go back to stock, as in the last "Official" build released by Motorola, then you want the 2.3.4 build. And as long as you use the fruitcakes you can go back to a custom rom at any time.
Click to expand...
Click to collapse
Yes, you can flash 2.3.4 fruitcake over a 2.3.6 fruitcake. Just make sure to do the "wipes" (clear data/cache/factory reset/fastboot wipe/etc).
As far as I understand, the fruitcakes will not brick your device, as long as you follow the directions. The risk for bricking applies to using an SBF file and RSDlite.
sony108 said:
Thanks for your early reply ... Just one thing more I wanna ask that if I flash ATT 4.5.140 - 2.3.6 fruitcake, then can I flash ATT 2.3.4 - 4.5.91 over it? Is the brick warning for going back to stock ATT ROM only after having BL unlocked?
Thanks for your help
Click to expand...
Click to collapse
It's looking like, at least for some users, unlocking the bootloader on OTA 4.5.141 is causing more issues than the expected soft brick that happens with 4.5.91. When new users are asking about unlocking the latest version, I see the standard advice offered:
- flash pudding sbf (just the unlocker)
- probably get soft-bricked
- issue "fastboot oem unlock" command anyway, reboot & life is great
OR use the one-click BL unlock script.
-----------------
But Nottach said he nearly hard-bricked after flashing pudding while unlocking a stock phone on 4.5.141. He had to do a vol up + power combo WHILE inserting the battery in order to bring it back...
and this user apparently had to do at least a battery pull to complete the process (not sure since posts were edited)...
and still other users are reporting success with the one-click tool.
-----------------
So: is it a fair statement that BL unlocking on the latest version runs an increased risk of bricking the phone, compared with 4.5.91? Is there something else I'm missing here? If I had a stock phone on the latest update I'd be thinking twice about unlocking it.
sheeparecurious said:
It's looking like, at least for some users, unlocking the bootloader on OTA 4.5.141 is causing more issues than the expected soft brick that happens with 4.5.91. When new users are asking about unlocking the latest version, I see the standard advice offered:
- flash pudding sbf (just the unlocker)
- probably get soft-bricked
- issue "fastboot oem unlock" command anyway, reboot & life is great
OR use the one-click BL unlock script.
-----------------
But Nottach said he nearly hard-bricked after flashing pudding while unlocking a stock phone on 4.5.141. He had to do a vol up + power combo WHILE inserting the battery in order to bring it back...
and this user apparently had to do at least a battery pull to complete the process (not sure since posts were edited)...
and still other users are reporting success with the one-click tool.
-----------------
So: is it a fair statement that BL unlocking on the latest version runs an increased risk of bricking the phone, compared with 4.5.91? Is there something else I'm missing here? If I had a stock phone on the latest update I'd be thinking twice about unlocking it.
Click to expand...
Click to collapse
Anybody?
Had to replace my Atrix today, new one already has 4.5.141 on it. Is it safe to unlock the BL using pudding? Or should I wait till the Dev's get it fully worked out?
I'll post my experience/method that I did several times over on my 2 Atrix phones (Both AT&T)
Both phones had unlocked bootloader
I upgraded both phones via the Automatic Update (Motorola Website tool...it downloads the SBF and flashes it to your phone)
At that point you're at 141, stock, unrooted (I did this over unlocked bootloader)
Then I used the Automatic Bootloader Unlock 4.2 to do fastboot oem unlock
I root using preinstall method and restore from Titanium Backup
I have not run into any problems going to and from 141 with unlocked bootloader (I did not try going to FroYo but GB works fine)
I release two ATRIX with GB 2.3.6 Version 4.5.141 very easy
Use RSD Lite 5.7
but the pudding in this link:
http://forum.xda-developers.com/showthread.php?t=1136261
First go to applications and places the phone in debug mode, then turn it off, and plug it in RSD mode and flash with RSD Lite SBF
If for some reason fails you failed to boot OS 0x1000 not detected, goin to RSD mode in 5 seconds
Then use this software
http://forum.xda-developers.com/showthread.php?t=1182871
And utliza the Options for Failed To Apply FIX 0x1000 Boot ", the cel should be in fastboot mode
Write down the key will throw you via commands and then put it again when prompted, after this and you will the unlocked bootloader.
regards
psychephylax said:
I'll post my experience/method that I did several times over on my 2 Atrix phones (Both AT&T)
Both phones had unlocked bootloader
I upgraded both phones via the Automatic Update (Motorola Website tool...it downloads the SBF and flashes it to your phone)
At that point you're at 141, stock, unrooted (I did this over unlocked bootloader)
Click to expand...
Click to collapse
When you did this, did you not get soft-bricked? I know I did.
psychephylax said:
Then I used the Automatic Bootloader Unlock 4.2 to do fastboot oem unlock
I root using preinstall method and restore from Titanium Backup
Click to expand...
Click to collapse
I've done the preinstall, but I can't get CWM to flash the recovery partition.
Can anybody help with reinstalling CWM? Should I flash a pudding / SBF again though I know (based on the contents of ReservedOdm that my BL is still unlocked)?
just wanted to post my experience as i did this a couple of days ago...
i flashed the pudding file (not the one that the automatic unlocker script uses when choosing the 2.3.4/4.5.91 option), got the failed to boot error, put the phone into fastboot mode and did the oem unlock commands (on a PC running winXP), and my bootloader was successfully unlocked. at this point i was able to boot into the stock ROM, with the data partition freshly wiped. i then flashed romracer's cwm using fastboot mode, and then installed the nottachtrix rom. btw i noticed that on the stock rom, cwm would not stay loaded. seems like it gets wiped out after reboot? not sure.
i had previously created a tarball of my data partition and restored it after installing the new rom, but this was a bad idea. better to just use the batch functions of TiBu for the apps, and some sort of sms backup app (from the play store) for keeping your messages.
Just the topic I was looking for. I was trying to unlock my bootloader for this version, but haven't been able to find a guide showing me how and this is my first time.