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
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.
Hello Atrix users! I recently just received this phone about a week ago and have rooted, unlocked the bootloader and also flashed the cwm. Now, whenever I try to update via OTA or sd card I get an error stating that the update has failed. I'm very new to Android phones and I was wondering what the procedure for updating would be? BTW I'm on 1.8.3
Thanks a lot
first of all i dont think your suppose to rsd or ota after you have unlocked the BL you have to flash GB through moto-fastboot or fastboot when u have GB on your external SD and run the commands through a command window, GOOGLE IS YOUR FRIEND and so is XDA just a do a search and you should find wat your looking for,
wat i have done is i was already on 1.8.3 and unlocked the BL, but i forgot to root the phone, and i couldnt root idk why, so i had to use the aroot method(do quick search on it) which had me rsd back to 1.2.6 then reboot, after that the words UNLOCKED where gone, so i think rsd back to 1.2.6 either took the unlock away or just got rid of the words and BL was still unlocked idk, but any way did a wi-fi ota update to 1.5.7 than ran afterupdate.bat and it retained the root, then just ran the unlock again with rsd rebooted and the words unlocked were back, but im not on 1.8.3, idk if i should try to ota to it, or rsd back to the beginning which is 1.2.6 and just ota all the way to the offical newest update of gingerbread then unlock the bl again and do the preinstall root method, thats where im stuck at,
That seems like a ton of work just for the OTA. I unlocked my boot loader and flash the cherry blur rom (v.1.4) this was the easiest way I have found to get 2.3.3 on my phone and without blur over taking the interface.
Sent from my MB860 using XDA Premium App
from wat i have read you should be good with wat ever u do with rsd or flashing back to a stock rom AS LONG AS YOU HAVENT UPDATED TO THE NEWEST OTA UPDATE SENT TO YOU OTA BUT IF YOU HAVE ACCEPTED THE OTA UPDATE YOU WILL HARD BRICK YOUR PHONE IF U TRY FLASHING BACK TO A STOCK LIKE 1.2.6 i think that is how it goes from wat i have read
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 ).
Hello everyone. I am new to the world of android, but I'm a quick enough learner. Here is my specific problem:
I have an AT&T Atrix 4g. It is currently superuser rooted. It is currently running Android ROM 2.3.4.
Shortly after rooting the device, I downloaded ROM Manager and successfully installed through the application Clockwork Recovery. I tried to select the option to back up the current ROM (the stock android) on my SD card.. however, during the load screen, I got an error message stating
"Failed to boot 2
Starting RSD protocol support"
So doing some research, I came upon the conclusion that the reason I can't backup or really do anything with ROMs is that I needed an unlocked bootloader.
I went to Atrix4ghacks and followed the instructions on how to unlock bootloader and install permanent recovery.
This is the critical part: When I entered into the command prompt "fastboot oem unlock", instead of proceeding normally I got the return message:
"OEM unlock is not implemented"
Again, did a google search and read that Android 2.3.4 on Atrix 4g does NOT allow unlocked bootloaders.
So, the questions that I have that result from this are:
1.) Can someone here confirm that, in fact, I am unable to unlock the bootloader on my phone?
2.) If so, is there a viable workaround that is both reasonably safe and not overly complicated? Please note that I have no backup in case something goes wrong, leading me to
3.) Is there a way to backup my stock 2.3.4 ROM without an unlocked bootloader?
4.) Can I revert safely to an older android version that supports unlocked bootloaders?
5.) Can you actually install new ROMs without an unlocked bootloader?
6.) Am I totally screwed?
HUGE THANKS to anyone who actually bothered reading this, and even more thanks to anyone who can answer/point me in the right direction. Much appreciated!!!
thats becouse u havent flashed yet the bootloader ill give a post related to this and esay way to do it
http://forum.xda-developers.com/showthread.php?t=1182871
and you CANT go back to 2.2 or 2.3 u can hard brick your phone
tufo430 said:
thats becouse u havent flashed yet the bootloader ill give a post related to this and esay way to do it
http://forum.xda-developers.com/showthread.php?t=1182871
and you CANT go back to 2.2 or 2.3 u can hard brick your phone
Click to expand...
Click to collapse
Thanks a ton for that link. I'm sorry to ask once again, but I'm very wary of possibly bricking my phone... so I must ask: Is your solution possible with 2.3.4? Or will the phone softbrick?
If you did the Over The Air (OTA) update to 2.3.4 then yes your phone will softbrick after flashing the bootloader. Re-enter fastboot and issue the unlock commands and everything will be fine when you reboot.
My husband and I got our phones through AT&T (US) on Froyo; after the Gingerbread update I unlocked my bootloader & went the custom rom route while he stuck with root access.
So he unrooted & took the 4.5.141 update OTA; I took mine via Nottachtrix. Now he's asking about unlocking his BL too.
a) Is it possible without bricking? Seriously. Was the bricking issue earlier this year related to folks with unlocked BLs taking the OTA update, or folks trying to unlock after taking the OTA update?
b) I did mine by flashing pudding and unlocking through fastboot (then soft-bricking, then proceeding with fastboot anyway yada yada). Now I see this one-click-tool thing being thrown about. Should I be using that instead, or is there an updated "pudding" SBF I should be using?
c) Since megaupload went to pot, how valid are the original threads that contain these files? Still feels weird to think of "old" things as being ~10 months past. Ah well.
Use the unlocking sbf in the Android Development section sticky (pudding thread). It shouldn't give you any chance of a brick. It's called "try sbf" or something along those lines. Once flashed via RSD Lite, you fastboot oem unlock, copy your unique code and fastboot oem unlock "code" (without quotations). You have a chance of brick if you SBF down to a firmware lower than your current one, as it tries to flash new bootloader and will fail. AFAIK, you're even safe to reflash 4.5.141 OTA but people don't encourage it as you can easily confuse yourself and flash Froyo instead which WILL make you brick.