ATT Atrix w/ 2.3.4 & 4.5.91
Trying to help roommate with phone but not familiar with Atrix (I have a Fascinate) so I'm having some issues. Already rooted but having trouble unlocking bootloader. In cmd prompt I get the error "(bootloader) oem unlock is not implemented." Tried flashing unlock sbf with rsd lite but got an error as well. The last thing I want to do is hard brick a phone that isn't mine so I've been wary of just trying random things until something works. Any help?
I've been having allot of fun with my attempts documented here http://briefmobile.com/how-to-unlock-the-atrix-4g-bootloader
HOWEVER, if your friends phone shipped with a version 1.8.3 or earlier then i recommend searching the forums as i hear that version was much more successfully unlocked and cracked
ertDeath said:
I've been having allot of fun with my attempts documented here http://briefmobile.com/how-to-unlock-the-atrix-4g-bootloader
HOWEVER, if your friends phone shipped with a version 1.8.3 or earlier then i recommend searching the forums as i hear that version was much more successfully unlocked and cracked
Click to expand...
Click to collapse
Hey there,
i heard that once you had upgrade to 2.3.4 you cant use the same method to unlock your bootloader. it will brick your Atrix.
Related
Okay guys, i flashed the 2.3.4 ota as soon as it came out (before all this trouble with it of course) and now i am stuck because i was under the impression that the new bootloader would be unlocked so i had never even though about eating any pudding before the fact. Now i come to my trouble, im running a totally stock 2.3.4 att and i cant seem to find a way out.
Question #1- If i have a locked bootloader can i fruitcake back?
Question #2- Is there a possible way to unlock the new bootloader?
Question #3- How in heck do i get root, im on windows 7 and i recently tried the two bat files that one of the devs released and they were a no go, it didnt seem to flash the preinstall when i tried to look for it, it wasnt there. I have been quietly trying to fix this on my own for days now i am asking for a little help. Im stumped.
I got root using the /preinstall method with those 2 .bat files posted yesterday.
From page 30-35 is the guidance I followed from mramirezusa.
Other than that we are in the same boat.. I read puddings will flash relatively safely.http://forum.xda-developers.com/showthread.php?t=1159950&page=30
cthomas5714 said:
Okay guys, i flashed the 2.3.4 ota as soon as it came out (before all this trouble with it of course) and now i am stuck because i was under the impression that the new bootloader would be unlocked so i had never even though about eating any pudding before the fact. Now i come to my trouble, im running a totally stock 2.3.4 att and i cant seem to find a way out.
Question #1- If i have a locked bootloader can i fruitcake back?
Question #2- Is there a possible way to unlock the new bootloader?
Question #3- How in heck do i get root, im on windows 7 and i recently tried the two bat files that one of the devs released and they were a no go, it didnt seem to flash the preinstall when i tried to look for it, it wasnt there. I have been quietly trying to fix this on my own for days now i am asking for a little help. Im stumped.
Click to expand...
Click to collapse
Question #2- Is there a possible way to unlock the new bootloader? yes use pudding
cthomas5714 said:
Okay guys, i flashed the 2.3.4 ota as soon as it came out (before all this trouble with it of course) and now i am stuck because i was under the impression that the new bootloader would be unlocked so i had never even though about eating any pudding before the fact. Now i come to my trouble, im running a totally stock 2.3.4 att and i cant seem to find a way out.
Question #1- If i have a locked bootloader can i fruitcake back?
Question #2- Is there a possible way to unlock the new bootloader?
Question #3- How in heck do i get root, im on windows 7 and i recently tried the two bat files that one of the devs released and they were a no go, it didnt seem to flash the preinstall when i tried to look for it, it wasnt there. I have been quietly trying to fix this on my own for days now i am asking for a little help. Im stumped.
Click to expand...
Click to collapse
hey man first things first. dont panic, you are not stuck. this is temporary at best, in the mean while theres plenty of stuff you can do, sbf is not safe to begin with. so actually be gladd you only got to use RSD one time
first things first, get yourselfed unlocked, pudding will do the trick. once after pudding, you never have to touch RSD
Once you are done with pudding go ahead and get tenfars unlocked cwm
once you are done with that you are free to flash pretty much all the roms, as usually custom roms, or fruit cakes dont have bl, only the rest
enjoy
Okay guys, thanks for your help. but let me get this clear, i do not have a unlocked bootloader, im a pudding virgin. I can simply rsd the 1.83 with pudding and thats it? No worries no nothing?
cthomas5714 said:
Okay guys, thanks for your help. but let me get this clear, i do not have a unlocked bootloader, im a pudding virgin. I can simply rsd the 1.83 with pudding and thats it? No worries no nothing?
Click to expand...
Click to collapse
Yes but you still can't use any other sbf. I'd use the raw pudding sbf, unlock, then use CWM from here on out. No more rsd
Sorry about that. There is just the unlock and then the unlock packaged with 1.8.3. The one that has has been causing bricks from my understanding is the packaged one. Be sure you flash just the unlock.
Anyone know what exactly will be erased from /data after flashing the unlock? Also I don't want to restore backed up files that will conflict with new ones. Any guidance on this is appreciated.
snudmusk said:
Sorry about that. There is just the unlock and then the unlock packaged with 1.8.3. The one that has has been causing bricks from my understanding is the packaged one. Be sure you flash just the unlock.
Anyone know what exactly will be erased from /data after flashing the unlock? Also I don't want to restore backed up files that will conflict with new ones. Any guidance on this is appreciated.
Click to expand...
Click to collapse
All user data is wiped when unlocking. The 1.8.3 sbf with pudding is safe to flash but i recommend just using pudding and then CWM and ditch rsd.
jruweaver said:
All user data is wiped when unlocking. The 1.8.3 sbf with pudding is safe to flash but i recommend just using pudding and then CWM and ditch rsd.
Click to expand...
Click to collapse
Agree, just use the pudding only sbf. to unlock , then preinstall to get root.
Make sure to have 50 or so battery so you don't run into the trouble I had with battery being to low to fastboot. Also once you flash pudding you wont be able to boot the phone, don't panic just follow steps to fastboot oem unlock and phone will boot fine afterwards.
Sent from my MB860 using Tapatalk
woahh no bad idea, im scared. I did exactly as you all said and it acts like its hard bricked, SVF:105 error but then it says no OS detected and i have 14 options
1RSD
2Fastboot
3Nvflash
4-9BP something
9Android recovery
10Boot android (no bp)
11Device UID
12Console
13early usb enumeration
14BP tools
WHAT DO I DO?
cthomas5714 said:
woahh no bad idea, im scared. I did exactly as you all said and it acts like its hard bricked, SVF:105 error but then it says no OS detected and i have 14 options
1RSD
2Fastboot
3Nvflash
4-9BP something
9Android recovery
10Boot android (no bp)
11Device UID
12Console
13early usb enumeration
14BP tools
WHAT DO I DO?
Click to expand...
Click to collapse
Which did you flash? Pudding or 1.8.3 with pudding?
Try connecting your phone to pc select fastboot and finish the pudding instructions (fastboot oem unlock)
It might boot then.
Sent from my MB860 using XDA Premium App
Here is what I did.
1. If you were to update to the OTA 4.5.91. Or already on the OTA 4.5.91 you can still unlock your bootloader.
2. Flash pudding only SBF so you can unlock the bootloader. http://diamantephoto.com/fastboot.rar direct link. Flash this one.
http://forum.xda-developers.com/show....php?t=1136261 Original Post about pudding.
It will go to a text only 14 option screen and say something like boot failed 0x1000. Don't freak out and tell me you bricked you phone blah blah blah. You still have to unlock the bootloader by choosing fastboot from your phone and connecting it to the computer via usb. Make sure you have ADB with fastboot tools installed on you computer.
Open command prompt from you computer and type fastboot oem unlock. It'll display warning about voiding warranty and a unique device id. Type again fastboot oem unlock ############. The # are the unique device numbers. Don't type # it wont work. The instructions are posted on the pudding thread if you would like to read more about it.
Then type fastboot reboot to reboot. Unlock should be displayed on top left of screen and it'll take 5 long mins to boot up.
3.Then you need to install CWM and root.
You'll find instructions in the developers form. But if your lazy here is the CWM link. http://forum.xda-developers.com/show....php?t=1138541 follow the instructions or every time you reboot you will loose CWM. For root there are two available for gingerbread. http://forum.xda-developers.com/show....php?t=1140110 I used this one and got root.
http://forum.xda-developers.com/show....php?t=1138204 I hear this works too.. Haven't tested read the post if you want to use this method.
As always don't blame me for bricking if you happen to do so. DO IT AT YOUR OWN RISK. these are the steps I took to unlock and everything works great. Absolutely no problems with my phone after wards.
One thing unlocking your bootloader will format/erase data. Basically a factory data reset so make sure you backup everything with titanium or you favorite app. I would not restore system apps as i've had a few problems with email and motoblur force closes.
Is there a way to root without unlocking the bootloader?
five3zero said:
Is there a way to root without unlocking the bootloader?
Click to expand...
Click to collapse
Yes.
Follow the instructions listed on here:
http://forum.xda-developers.com/showthread.php?p=15023030
The 3rd post has the instructions I followed.
If you have problems be sure to read through the thread as someone else has most likely already had the same issue.
This worked for me.
cthomas5714 said:
woahh no bad idea, im scared. I did exactly as you all said and it acts like its hard bricked, SVF:105 error but then it says no OS detected and i have 14 options
1RSD
2Fastboot
3Nvflash
4-9BP something
9Android recovery
10Boot android (no bp)
11Device UID
12Console
13early usb enumeration
14BP tools
WHAT DO I DO?
Click to expand...
Click to collapse
Just do: fastboot oem unlock (or whatever tthe code is)
Them: fastboot reboot
Sent from my MB860 using XDA App
I bought the phone a week ago and then it said I had an update so I updated over my wifi connection in the house.
Since I did this do I still use the RSD Lite to unlock the bootloader or is it unlocked already(reading sooo much stuff has confused me)? If I use RSD Lite do I dl the 2.3.4 sbf from the list on here?
I really dont want to brck my phone so any help is appreciated, thanks!
that OTA update will not unlock is the official moto update. Your bootloader is not unlocked unless it says "unlocked" in the top left corner of the screen when you're booting.
Look up "pudding" and use fastboot to unlock the bootloader
edit: you can use rsd if you want. Whatever your preference is.
I currently have no preference because I havent used either, which is easier to use?
supermerkin said:
I currently have no preference because I havent used either, which is easier to use?
Click to expand...
Click to collapse
read the posts in the dev forum...
pudding by far.
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
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.
So tired of searching for this file. Everyone keeps saying i need to find 2.3.6 .spf for RSD to unlock bootloader but all th elinks are broken. Can anyone get me a link to the 2.3.6 SPF please?
att atrix 4g 2.3.6
I foud 2.3.4....
http://www.filefactory.com/f/89f588286a560e39/
will this work? top one..or do i need 2.3.6 if im currently 2.3.6?..
edit: well top one isnt right... i dont know wich of these is for ATT US version heh...theres a 2.3.6 but its for Bell ...
Here ya go. das8nt is a big help here on xda and on the atrixforums. http://www.das8nt.com/sbffiles.html Make sure you got the motorola drivers, read the guide a couple times before attempting if you haven't used RSDlite before. Don't downgrade, use the version SBF that your on now currently. Downgrading will result in a hard brick! If you're looking to unlock your bootloader you need the pudding file here Unlocker for 1.8.3 and 4.5.91 ATT firmwares. It worked for me when I unlocked on 2.3.4, should work on 2.3.6.
smenes said:
Here ya go. das8nt is a big help here on xda and on the atrixforums. http://www.das8nt.com/sbffiles.html Make sure you got the motorola drivers, read the guide a couple times before attempting if you haven't used RSDlite before. Don't downgrade, use the version SBF that your on now currently. Downgrading will result in a hard brick! If you're looking to unlock your bootloader you need the pudding file here Unlocker for 1.8.3 and 4.5.91 ATT firmwares. It worked for me when I unlocked on 2.3.4, should work on 2.3.6.
Click to expand...
Click to collapse
Got it! Thanks! Now for some reason adb shell isnt working like it was yesterday. Shrug* sigh ideas?
After you flashed the pudding, did you boot to fastboot and issue the 'fastboot oem unlock' command to unlock the bootloader as described here? Do you have root? what do you get when you type 'adb devices' ? You have usb debugging enabled while booted in android?
smenes said:
After you flashed the pudding, did you boot to fastboot and issue the 'fastboot oem unlock' command to unlock the bootloader as described here? Do you have root? what do you get when you type 'adb devices' ? You have usb debugging enabled while booted in android?
Click to expand...
Click to collapse
Device says unlocked. Im good there. When i install a recovery per the suggested install it says written but when i try to go to it i get the aNDROID sitting there with a yeild ! sign, so i have to reboot....somethings wrong cause when i try to get CWM to install it for me from the phone itself it says error flashing... any ideas?
EDIT : i didnt think about renabling debugging one minute
not sure that did anything.
Edit: i only had to install super user lol thanks for all ur help