Hello. The subject matter says it all.
I currently have a rooted and unlocked AT&T Atrix on 1.26 version (yeah...still in ice age ) with a locked bootloader. Im with a non-US telco carrier. It came unlocked and rooted so that was great. No hassle but now I have started doing research on custom roms and webtop mods. I am trying to get around the info overload, so pls bear with my questions.
The overall goal is to have a stock/custom rom devoid of all the bloatwares and can run webtop2sd, and if that is not possible then, webtop. Very simple needs.
Option 1
======
To remain on stock rom and update to 1.83 version, and then to install the webtop2sd mod. Ideally I would like to boot off Debian from the microsd card. There was a post in which a forumer mentioned that he was able to "frankenstein" the webtop2sd and webtop mods. Thats great if I understood correctly.
Option 2
======
To update to 4.5.91 (probably a custom rom like Aura) and then install the webtop2sd/webtop mod.
What should be done?
I am going to update 1.26 -> 1.57 -> 1.83 -> 4.5.91 via system update. (which means I now have to signed with moto account...yes I have not as I read that there were some privacy issues.)
Through the update process, I would lose root. To keep everything clean, I am going to go through factory reset and then perform the update.
Once I am in 1.83 or 4.5.91, I will apply the root and unlock the bootloader. Which is the best way to go about this? Should I just follow the instruction here or this way. Or is there any other better way?
This is all I have for now until I install the webtop mod or the custom rom...
update your phone to wherever you want it at, then use this script to unlock the bootloader:
http://forum.xda-developers.com/showthread.php?t=1182871
after that, you can easily root your phone using the preinstall method found here:
http://forum.xda-developers.com/showthread.php?t=1138204 (second post)
if you update to 4.5.91 though, as you attempt to unlock the bootloader you will get a semi-hard brick, just have it boot up into fastboot mode and continue using the script. easy as pie!
I never got a semi-hard or *soft* brick from unlocking but that's just cause I must love to eat pudding =D . Do all the OTA updates, unlock / root, and then install the 2.3.4 fruitcake and install webtop. Best option by far, IMO, as far as the ease of transition goes. Should be cake. That's what I did and as long as you don't RSD lite with an .SBF back once on 2.3.4 OTA yer good to go.
eat yer fruitcake once updated to 2.3.4 OTA *stock gingerbread*-http://forum.xda-developers.com/showthread.php?t=1163009
Install a custom kernel if ya wanna overclock or undervolt, I would personally suggest Faux123's. -http://forum.xda-developers.com/showthread.php?t=1156040
aaand freeeze all that bloatware!-http://forum.xda-developers.com/showthread.php?t=972459
I read that its easier to update via SBF than OTA? What have your experiences been so far?
Alcapone263 said:
if you update to 4.5.91 though, as you attempt to unlock the bootloader you will get a semi-hard brick, just have it boot up into fastboot mode and continue using the script. easy as pie!
Click to expand...
Click to collapse
Maybe I should try to unlock it now... And then update.
tech_girl said:
I read that its easier to update via SBF than OTA? What have your experiences been so far?
Click to expand...
Click to collapse
well, i can't find it anymore but there is an SBF in the development forum that will allow you to update to 2.3.4 android without getting the brickable bootloader, but i personally don't see a point in using SBF. it's not meant for the end user, and using it can be risky.
SBF flashing is faster i believe, but as i said can also potentially harm your device if you're unsure of what you're doing.
SamCripp, one of the most esteemed devs here, suggests for the average person to completely stay away from sbf flashing after you've unlocked your bootloader unless you absolutely have to use it for something.
remember though, if you use the OTA update you CANNOT downgrade your device through SBF flashing, you HAVE to use the fruitcakes method. it WILL brick your device to downgrade, but only with the OTA update.
EDIT: and it's a semi-hard brick, it doesn't hurt your device in the least. you might panic at first, but it's as simple as booting into fastboot mode and finishing the script. or if you're more tech inclined, you can just do the fastboot oem unlock command through fastboot.
Phalanx7621 said:
....
eat yer fruitcake once updated to 2.3.4 OTA *stock gingerbread*-....
Click to expand...
Click to collapse
Alcapone263 said:
......
remember though, if you use the OTA update you CANNOT downgrade your device through SBF flashing, you HAVE to use the fruitcakes method.....
Click to expand...
Click to collapse
Fruitcakes??? All this jargon.... Hmmm...gotta check this out.
http://forum.xda-developers.com/showthread.php?t=1163009
yep, Fruitcakes. it's a CWM alternative to sbf flashing, much safer since it doesn't edit the bootloader at all, so there's no risk in hard bricking your device.
after you unlock your bootloader, you should install Romracer's CWM recovery here: http://forum.xda-developers.com/showthread.php?t=1204500
do all of your flashing through CWM after you unlock your bootloader, just remember to clear cache/dalvik/data between each ROM or you might get stuck in a bootloop.
Ok...CWM sounds more familiar....
If I understand correctly, I actually dont have to go via OTA. As long as I have the img file for flashing to each version, I could just use the CWM and not via OTA, right?
tech_girl said:
Ok...CWM sounds more familiar....
If I understand correctly, I actually dont have to go via OTA. As long as I have the img file for flashing to each version, I could just use the CWM and not via OTA, right?
Click to expand...
Click to collapse
well, you have to have an unlocked bootloader to get CWM. and to unlock your bootloader, you have to update to 1.8.3 or later.
after you unlock your bootloader, you can install CWM and proceed to just use CWM for your flashing needs.
i repeat again though, after you unlock your bootloader you should stay away from SBF flashing altogether. it's the quickest way to brick your device.
Alcapone263 said:
well, you have to have an unlocked bootloader to get CWM. and to unlock your bootloader, you have to update to 1.8.3 or later.
after you unlock your bootloader, you can install CWM and proceed to just use CWM for your flashing needs.
i repeat again though, after you unlock your bootloader you should stay away from SBF flashing altogether. it's the quickest way to brick your device.
Click to expand...
Click to collapse
+1
Once you unlock and get CWM installed its just a case of wiping the device and flashing zip files.
Yep after unlocking and getting rom racers cwm in, you get to have lots of fun and almost zero chance of hard bricking. Make sure you understand the pudding part. After you unlock throw rsd lite away.
After updating to 1.83 and unlocked, can I immediately installing a GB custom rom like Aura or Alien? Or do I need to update to 4.5.91 stock before I can install a custom rom? Which I assume is pre-rooted, which mean I dont have to root it..
tech_girl said:
After updating to 1.83 and unlocked, can I immediately installing a GB custom rom like Aura or Alien? Or do I need to update to 4.5.91 stock before I can install a custom rom? Which I assume is pre-rooted, which mean I dont have to root it..
Click to expand...
Click to collapse
You should be able to start flashing if you used pudding. No need to upgrade to .91 stock. I didn't. I think most roms are pre rooted now. Not that the rooting method was hard for the atrix.
I voided my warranty.
pukemon said:
You should be able to start flashing if you used pudding. No need to upgrade to .91 stock. I didn't. I think most roms are pre rooted now. Not that the rooting method was hard for the atrix.
I voided my warranty.
Click to expand...
Click to collapse
Yep thats how it works. once BL unlocked and CWM installed you can flash anything, including yes .91 stock.
Note that .91 stock OTA is not only the operating system but also modifies the bootloader hence all the hard brick warnings about flashing sbfs. When you flash zip files you don't touch the bootloader, so there is no chance of hard bricking. i.e. if you flash .91 stock from zip file from CWM as opposed to OTA, you get only the OS, not the bootloader update (which doesn't matter ).
Related
Just curious if the new 2.3.4 gingerbread OTA can be unlocked using pudding. I'm having to get my atrix replaced via warranty and if the replacement happens to come with gingerbread already on it i want to know if i'll be able to unlock it or if i'll be stuck using p-roms.
You should be able to unlock it with pudding since its the same version of gingerbread that we have. Also, don't flash any sbf files (except pudding) because it has the new bootloader and you'll hard brick it if you do.
You can unlock with pudding and fastboot BUT there's a high chance you'll soft brick first with 0x1000 ... all you need to do is get into fastboot mode and redo the oem unlock command.
mysticdrew said:
You can unlock with pudding and fastboot BUT there's a high chance you'll soft brick first with 0x1000 ... all you need to do is get into fastboot mode and redo the oem unlock command.
Click to expand...
Click to collapse
Alright, just to be absolutely, completely, all the way, 101% sure: does this OTA have ANY bootloader restrictions, be they a brick or non-unlockable bootloader. Has anybody tried to unlock the bootloader and run a custom ROM on the AT&T OTA? I just want to be able to run custom ROM's down the road (as in full ROM's, as in Cyanogenmod).
Do the OTA and never, never go back to any older stock version via RSD. Or you'll brick your phone.
@Chairsofter1138: the ota bootloader is locked. flash the pudding to unlock.
Alright, has anyone actually attempted to unlock the OTA via the pudding method? I'm being extra cautious here because I don't want to be stuck with a permanently locked down phone. Does it matter, then, if I use Kenthepenns (sp?) installation method or OTA straight from AT&T/ Motorola?
Chairsofter1138 said:
Alright, has anyone actually attempted to unlock the OTA via the pudding method? I'm being extra cautious here because I don't want to be stuck with a permanently locked down phone. Does it matter, then, if I use Kenthepenns (sp?) installation method or OTA straight from AT&T/ Motorola?
Click to expand...
Click to collapse
Yes everyone has been unlocking via pudidng because it's the same leaked version that has been out for the past couple weeks.
Yes Going to this OTA will make a brickable phone. You WILL NOT BE ABLE TO DOWNGRADE via traditional SBF.
This is the question everyone has been asking on every thread and the devs aren't answering.
I am locked and stock on 1.83. My fuse HAS not been burnt. I want to be
1. On Gingerbread
2. Unlocked
The problem is that all the current gingerbread sbfs said you had to be ALREADY unlocked to flash them, so I don't know how anyone has been testing this OTA with a locked bootloader. If you had the new Gingerbread, you were already unlocked, is how I understood it.
Questions in follow up to the above:
1. If I OTA before unlocking, what do I flash afterwards to unlock? Saying 'pudding' because there's 10,000 files in that thread, including links to an 'unlocker.sbf', as well as a full sbf operating system. What specific file?
2. Lots of new builds say they have an 'unlocked bootloader' built in, but nobody can figure out what that means. Does that mean you can flash them without being unlocked to unlock? What do you need to do to unlock after you flash them?
3. If I unlock now at stock 1.83, and take the OTA, what happens, is the bootloader locked again? I know OTA installs a new bootloader.
Please someone help me understand. There's too much hard bricking and misinformation out there on all the dev threads. What's true (and please tell us how you know).
I noticed everyone talking about the OTA. I saw on the Moto site that the new update is only available OTA but there's a link for download for the file "Blur_Version.4.5.91.MB860.ATT.en.US". Can anyone confirm that this can be installed without brick on an unlocked bootloader? I've seen other threads stating so but they're not really clear on what's being said.
m0use1 said:
This is the question everyone has been asking on every thread and the devs aren't answering.
I am locked and stock on 1.83. My fuse HAS not been burnt. I want to be
1. On Gingerbread
2. Unlocked
The problem is that all the current gingerbread sbfs said you had to be ALREADY unlocked to flash them, so I don't know how anyone has been testing this OTA with a locked bootloader. If you had the new Gingerbread, you were already unlocked, is how I understood it.
Questions in follow up to the above:
1. If I OTA before unlocking, what do I flash afterwards to unlock? Saying 'pudding' because there's 10,000 files in that thread, including links to an 'unlocker.sbf', as well as a full sbf operating system. What specific file?
2. Lots of new builds say they have an 'unlocked bootloader' built in, but nobody can figure out what that means. Does that mean you can flash them without being unlocked to unlock? What do you need to do to unlock after you flash them?
3. If I unlock now at stock 1.83, and take the OTA, what happens, is the bootloader locked again? I know OTA installs a new bootloader.
Please someone help me understand. There's too much hard bricking and misinformation out there on all the dev threads. What's true (and please tell us how you know).
Click to expand...
Click to collapse
+1 to everything this guy said..There is a ton of guests in this forum wondering the same **** too. Devs are doing a fantastic job, but us end users (including myself) don't really have a sense of direction right now.
Ok Iv noticed that things are getting really really confusing around here with people saying one thing then someone else saying something else. I want to have a thread that is straight forward coming from people that know what they are talking about and not just assuming.
Now my phone has never had an unlocked bootloader. Before I updated to GB OTA i was on .83 rooted with all the mods added to it (webtop dock, blah, blah blah) I RSD back to .26 (that very old file) and just started doing OTA updates one by one once i logged in with my blurr account. I updated to GB via the official OTA update that was pushed to my phone when i selected to system update under settings.
I was able to Root this ATT OFFICIAL version pushed to my phone using This Pre-install method and that is all that i have done.
What i want to do now is Unlock the bootloader. From what i have read Pudding is the best way of doing this.
Q1: Does this method (Pudding) work with the Official ATT OTA version pushed to phones and not Kenns modded version, and is it the only way to unlock the bootloader?
Q2: Once unlocked what version of CWR do I install to be able to flash ROMs? Would i be able to just install ROM Manager and do the installation from there, Or possibly both ROM Manager and CWR?
Q3: Since RSD is out of the picture for me, if for some reason I'm to soft brick my phone and can still get into Recovery mode, what .sbf do i flash, would it have to be the same one that was pushed to phones that if not already available on here will be really soon?
Thanks for all the help if anyone helps out.
StyleUkno
Q2, if you unlock your phone, cwM of tenfars, the 2nd version for unlocked. Rom manager with official CWM have released before some days, but yet it doesn't support external sd.
As for question 1, and the unlocking pudding. The OTA gb you installed, might updated you bootloader, and maybe can't use that pudding.
For that be very carefull of your next steps.. Personally I would have send a pm to the2dcour, or another dev that knows as much..
Sent from my MB860 using XDA App
Bump to see if any other responses come.
Q1: Does this method (Pudding) work with the Official ATT OTA version pushed to phones and not Kenns modded version, and is it the only way to unlock the bootloader?
Yes, pudding works and is the only way. Have to Flash pudding and run OEM unlock command in fastboot. Because you are already on OTA, there's a high chance you will need an extra couple steps. It will likely soft brick with 0x1000 error but wit fastboot option. From there you need to fastboot and re do the oem unlock command another time. Then you are fine.
Q2: Once unlocked what version of CWR do I install to be able to flash ROMs? Would i be able to just install ROM Manager and do the installation from there, Or possibly both ROM Manager and CWR?
Tenfar's 6/30 unlocked CWM. ROM Manager version doesn't properly wipe as of yet. You can update if you dont' care about wiping, but that usually leads to boot loops when installing roms. Also most devs here are using update scripts tailored for tenfars version
Q3: Since RSD is out of the picture for me, if for some reason I'm to soft brick my phone and can still get into Recovery mode, what .sbf do i flash, would it have to be the same one that was pushed to phones that if not already available on here will be really soon?
if you softbrick (other than the initial unlock soft brick where you just run oem unlock again) then depends on what you want to get to. CWM a rom.zip/fruitcake for the version you want would be ideal. If not then a fastboot version if available. I'd RSD the GB 4.5 with pudding sbf as a last resort.
StyleUkno said:
Ok Iv noticed that things are getting really really confusing around here with people saying one thing then someone else saying something else. I want to have a thread that is straight forward coming from people that know what they are talking about and not just assuming.
Now my phone has never had an unlocked bootloader. Before I updated to GB OTA i was on .83 rooted with all the mods added to it (webtop dock, blah, blah blah) I RSD back to .26 (that very old file) and just started doing OTA updates one by one once i logged in with my blurr account. I updated to GB via the official OTA update that was pushed to my phone when i selected to system update under settings.
I was able to Root this ATT OFFICIAL version pushed to my phone using This Pre-install method and that is all that i have done.
What i want to do now is Unlock the bootloader. From what i have read Pudding is the best way of doing this.
Q1: Does this method (Pudding) work with the Official ATT OTA version pushed to phones and not Kenns modded version, and is it the only way to unlock the bootloader?
If you use the pudding you will hard brick on the OTA (from what people have been saying)
Q2: Once unlocked what version of CWR do I install to be able to flash ROMs? Would i be able to just install ROM Manager and do the installation from there, Or possibly both ROM Manager and CWR?
Out of the picture becuase you cant unlock I think
Q3: Since RSD is out of the picture for me, if for some reason I'm to soft brick my phone and can still get into Recovery mode, what .sbf do i flash, would it have to be the same one that was pushed to phones that if not already available on here will be really soon?
Thanks for all the help if anyone helps out.
StyleUkno
Click to expand...
Click to collapse
asldkjghaa
I've seen many bricks around. and i want to know which ways currently so we can avoid the hard brick. Thanks
Simple once you unlock your bootloader & update to Gingerbread (2.3.4), DO NOT RSD flash a earlier .sbf (i.e. 1.8.3, 1.5.7 etc.). If you want to return to 1.8.3 after updating and unlocking, you can flash the fruitcake via CWM.... so pretty much stay away from RSD Lite and .sbf flashes after you unlock bootloader.
i've have the latest OTA update, that mean my phone bootloader is unlocked?
Lordareon said:
i've have the latest OTA update, that mean my phone bootloader is unlocked?
Click to expand...
Click to collapse
Not unless you unlocked it before updating... If you want to unlock your bootloader, root, etc. just go take a look here:
http://forum.xda-developers.com/showthread.php?t=1154600
Which Rom Acttually provides better stability and perfomance?
Lordareon said:
Which Rom Acttually provides better stability and perfomance?
Click to expand...
Click to collapse
I happen to like Alien myself, just b/c it gets rid of a lot of the bloatware (use my own theme). But different strokes for different folks.
Well i want one to mainly play games, i took a look at the table and alien and aria looks amazing. should i wait cyanogen mod? im using the latest OTA from motorola. Will i notice perfomance increase?
Swiftks said:
Simple once you unlock your bootloader & update to Gingerbread (2.3.4), DO NOT RSD flash a earlier .sbf (i.e. 1.8.3, 1.5.7 etc.). If you want to return to 1.8.3 after updating and unlocking, you can flash the fruitcake via CWM.... so pretty much stay away from RSD Lite and .sbf flashes after you unlock bootloader.
Click to expand...
Click to collapse
Don't have to unlock. If you OTA'd to 2.3.4, you can't downgrade via RSD.
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
Hi guys! I have a couple of questions. I just updated my Atrix to 2.3.4 by OTA update, so i created a brickable device, haven't i? I would like to know what i have to do know, i want to root the phone and unlock the bootloader to install custom roms, but im afraid to brick my new phone. I have read a lot the past two hours, but im still not sure about what to do now in order to unlock the phone and achieve root.
Also, the device will brick if i try to flash any 2.2 rom, no matter how i flash it (via CWM for example)? Or only if i flash a 1.8.3 SBF via RSDLite? Are there any other files that i have to avoid if i don't want to brick my phone?
Thanks for helping me out guys!
djluis48 said:
Hi guys! I have a couple of questions. I just updated my Atrix to 2.3.4 by OTA update, so i created a brickable device, haven't i? I would like to know what i have to do know, i want to root the phone and unlock the bootloader to install custom roms, but im afraid to brick my new phone. I have read a lot the past two hours, but im still not sure about what to do now in order to unlock the phone and achieve root.
Also, the device will brick if i try to flash any 2.2 rom, no matter how i flash it (via CWM for example)? Or only if i flash a 1.8.3 SBF via RSDLite? Are there any other files that i have to avoid if i don't want to brick my phone?
Thanks for helping me out guys!
Click to expand...
Click to collapse
After you unlock the boot loader, do not flash any sbf prior to 4.5.91. In fact after you unlock the boot loader, there's no need to flash a sbf at all, b/c you can just flash a fruitcake to return to stock.
As far as picking a ROM, it doesn't really matter... any ROM that requires a unlocked boot loader (which they all do), it is at least based off of gingerbread Android 2.3.4+
Use the pudding unlock sbf to unlock your boot loader. Most rooms include root. See my sig for further info.
Sent from my CM7 Atrix 4G
Swiftks said:
After you unlock the boot loader, do not flash any sbf prior to 4.5.91. In fact after you unlock the boot loader, there's no need to flash a sbf at all, b/c you can just flash a fruitcake to return to stock.
As far as picking a ROM, it doesn't really matter... any ROM that requires a unlocked boot loader (which they all do), it is at least based off of gingerbread Android 2.3.4+
Use the pudding unlock sbf to unlock your boot loader. Most rooms include root. See my sig for further info.
Sent from my CM7 Atrix 4G
Click to expand...
Click to collapse
Thanks for your fast response! So, if i use the auto-unlocker on that thread, it wont brick my device right? Thanks for pointing me that, it seems very usefull. Now, this leads me to the next question, i also have to SIM Unlock my Atrix, because its locked to ATT and im trying to use it outside the US, so i need to SIM unlock it, i have seen several threads of users reporting problems SIM unlocking the phone, should i wait for the SIM Unlock code before proceding to unlock the bootloader? I have already ordered one, the guys should email it any time now, it will take less than 24hrs, and no less than 2hrs (which have already passed).
Thanks for your answers guys!
EDIT: Couldn't resist, unlocked the bootloader and achieved root. It was super easy with the automated batch. I hope i don't run into problems when i try to SIM unlock the phone lol