Can i unlock my atrix if i used the official att update is it safe i wanna flash a new rom i have the instructions how to just not sure if its safe i read all these people saying its not on some of these forums
Sent from my MB860 using XDA Premium App
Nobody wants too help me
Sent from my MB860 using XDA Premium App
http://forum.xda-developers.com/showthread.php?t=1154600
Yes, but when you flash pudding, you will get soft bricked (don't worry) you'll have 5 seconds to put your phone is fastboot mode, when done just continue the process and you should be fine. I unlocked on official 2.3.4, and I'm doing good
Sent from my MB860 using XDA App
http://forum.xda-developers.com/showthread.php?t=1182526&highlight=sbf+2.3.4
this thread has a ton of information on what to expect. I did it and its worked fine
mvolkhart said:
http://forum.xda-developers.com/showthread.php?t=1182526&highlight=sbf+2.3.4
this thread has a ton of information on what to expect. I did it and its worked fine
Click to expand...
Click to collapse
OP says "i used the official att update", so I'm assuming he's already on Gingerbread. No need to flash a full SBF just to unlock it then, and flashing full SBFs is no longer recommended except as a last resort.
Pudding.sbf is the way to go (just a megabyte), and here's the easiest way to do it:
Automatic bootloader UNLOCK/ROOT for AT&T 1.26/1.57/1.83/4.5.91
http://forum.xda-developers.com/showthread.php?t=1182871
OP, this is as safe as it gets. If you are already on GB then you will get a soft brick after the initial unlock attempt but mramirezusa script warns you of this and tells you exactly what to do about it. Just make sure that you have the latest Motorola USB drivers installed before you do any of this.
The script will unlock your phone, install a special ClockworkMod for Atrix 4G, and install su for root access. After this is all done you will want to apply any future updates via ClockworkMod in your phone's Fastboot menu. Don't mess around with SBFs unless you absolutely need to, and definitely do not apply an SBF for an earlier version of the phone's firmware or you will hard brick your phone.
Good luck!
Javi97100 said:
Yes, but when you flash pudding, you will get soft bricked (don't worry) you'll have 5 seconds to put your phone is fastboot mode, when done just continue the process and you should be fine. I unlocked on official 2.3.4, and I'm doing good
Click to expand...
Click to collapse
^^^ THIS ^^^
mramirezusa's script rocks.
Thanku man now I was scared to softbrick my phone so I used my older atrix that I have laying around I unlocked using that method but im on 4.1.26 now the prob im having is how to safley update to gb now without losing my unlock any ideas
Sent from my MB860 using XDA Premium App
For your 4.1.26 unlocked phone it would be easiest to just do the full 4.5.91 SBF with unlocked bootloader and /preinstall root as another poster suggested: http://forum.xda-developers.com/showthread.php?t=1182526&highlight=sbf+2.3.4
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
So guys I really wanna unlock the bootloader and flash some roms but this is my third atrix. Im using the 14 day grace period very very graciously. Anyways first atrix kept locking up- exchanged. Second one I tried to unlock it with pudding. Did the rsd thing with the. Sbf file and I was doing it. Then toward the end it failed. Complete brick- exchanged.
Anyways is there something else I should do, possibly a different route? Im using an AT&T atrix. Thanks.
Wait for official release and get it officially unlocked?
Sent from my MB860 using XDA Premium App
tsouza said:
Wait for official release and get it officially unlocked?
Sent from my MB860 using XDA Premium App
Click to expand...
Click to collapse
I can wait for the release, but are they unlocking it with it. For sure?
Well, IMO better hope for it than risk another brick...
Sent from my MB860 using XDA Premium App
tsouza said:
Well, IMO better hope for it than risk another brick...
Sent from my MB860 using XDA Premium App
Click to expand...
Click to collapse
True. Very true.
magicriggs said:
So guys I really wanna unlock the bootloader and flash some roms but this is my third atrix. Im using the 14 day grace period very very graciously. Anyways first atrix kept locking up- exchanged. Second one I tried to unlock it with pudding. Did the rsd thing with the. Sbf file and I was doing it. Then toward the end it failed. Complete brick- exchanged.
Anyways is there something else I should do, possibly a different route? Im using an AT&T atrix. Thanks.
Click to expand...
Click to collapse
I think you might have returned the first 2 prematurely.
1st one probably could have factory reset or flashed a new sbf
2nd one was probably a fixable soft brick.
So I'd say you're safe, but up to you as there's always a risk.
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/showthread.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/showthread.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.
Sent from my MB860 using Tapatalk
magicriggs said:
I can wait for the release, but are they unlocking it with it. For sure?
Click to expand...
Click to collapse
not sure. i got a leaked 4.5.91 build, it's not unlocked (although early beta does). you still have to flash the pudding img yourself.
delect this post
The returns were genuine. I did a factory reset on the first one and it still kept locking up, on the wake up. Had to pull battery out to turn back on. Multiple times. Second one was a complete brick. I couldn't get into rsd, wouldn't turn on and computer didn't recognize it in any mode. Im pretty familiar with rsd, used it with OG and X but this one got me walking om egg shells.
magicriggs said:
The returns were genuine. I did a factory reset on the first one and it still kept locking up, on the wake up. Had to pull battery out to turn back on. Multiple times. Second one was a complete brick. I couldn't get into rsd, wouldn't turn on and computer didn't recognize it in any mode. Im pretty familiar with rsd, used it with OG and X but this one got me walking om egg shells.
Click to expand...
Click to collapse
hmm you are very unlucky then. You're the only one to hard brick from pudding. Probably advise you not to do anything with your phone.
Jnewell05 said:
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.
Click to expand...
Click to collapse
im on build number 4_1.8.3 and i check for updates and it says my device is up to date. any
ideas?
magicriggs said:
im on build number 4_1.8.3 and i check for updates and it says my device is up to date. any
ideas?
Click to expand...
Click to collapse
4.1.83 is a great point to unlock the bootloader. DO NOT install the 4.5.91 OTA udpate, too risky to hard brick if you flashed an sbf. Of course, you don't have to sbf back anymore, but I would steer way clear of that when there are perfectly good options available. Only use customized ones like Kenneth's or the CherryBlur ROM. More will start flowing soon.
So what your advising is not to even unlock it. All I really want is volume wake.
magicriggs said:
So what your advising is not to even unlock it. All I really want is volume wake.
Click to expand...
Click to collapse
That's the exact opposite of what I'm advising. I knew I was taking some level of risk when I unlocked, but it's a risk well worth taking. Very, very low failure rate. Recoverable. But I can't accept the risk for your phone.
OSNPA said:
That's the exact opposite of what I'm advising. I knew I was taking some level of risk when I unlocked, but it's a risk well worth taking. Very, very low failure rate. Recoverable. But I can't accept the risk for your phone.
Click to expand...
Click to collapse
Oh gotcha. Thanks for the info.
Jnewell05 said:
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/showthread.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/showthread.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.
Sent from my MB860 using Tapatalk
Click to expand...
Click to collapse
i used update.zip ..did not flash back to 1.83...update.zip (blur 1.83 etc etc) was from leaked moto servers...i have new bootloader cause my andriod recovery is different...of course BL is locked....can i still unlock??
I reviewed all the threads but can't resolve the information I need to plan next step!
I want to revert back to stock since I am experiencing battery drain (I believe).
I did not root or unlock before using the OTG (thumbdrive) method for insrtalling the OTA 4.5.91 zip.
After finding out that was ill advised I did not unlock and left unrooted. I have been out of town and can't backtrack throught the threads to determine what is the best course.
Is there a concise thread for my situation?
Thanks in advance
If you want to confirm your status, please adb, su, and "cat /sys/firmware/fuse/ReservedOdm" or just open the file in Root Explorer. If you see something like:
10000000000010001000300004000
Then you should NOT SBF anything from Motorola"
If you want to post your ReservedOdm to look and see if you will be fine to SBF 1.83 again
Probably you are safe if you actually installed Kenth by CDW or moto-fastboot (boot.img and system.img)
But if you actually run the update.zip or any update trought the normal android recovery screen and if you saw the following legend "updating AP20 bootloader" in that case you CAN NOT flash any SBF from Motorola
JiminSD said:
I reviewed all the threads but can't resolve the information I need to plan next step!
I want to revert back to stock since I am experiencing battery drain (I believe).
I did not root or unlock before using the OTG (thumbdrive) method for insrtalling the OTA 4.5.91 zip.
After finding out that was ill advised I did not unlock and left unrooted. I have been out of town and can't backtrack throught the threads to determine what is the best course.
Is there a concise thread for my situation?
Thanks in advance
Click to expand...
Click to collapse
Sent from my MB860 using XDA App
mramirezusa said:
If you want to confirm your status, please adb, su, and "cat /sys/firmware/fuse/ReservedOdm" or just open the file in Root Explorer. If you see something like:
10000000000010001000300004000
Then you should NOT SBF anything from Motorola"
If you want to post your ReservedOdm to look and see if you will be fine to SBF 1.83 again
Probably you are safe if you actually installed Kenth by CDW or moto-fastboot (boot.img and system.img)
But if you actually run the update.zip or any update trought the normal android recovery screen and if you saw the following legend "updating AP20 bootloader" in that case you CAN NOT flash any SBF from Motorola
Click to expand...
Click to collapse
Thanks I am sure I can't flash rsd sbf, I am wondering if it is safe to root. I am not rooted nor unlocked.
Sent from my MB860 using XDA App
Yes it is safe to root. I am on 4.5.91 and can't flash back. I un locked rooted and installed CWM. With no issues. Wouldnt use .sbf flashes though.
Sent from my MB860 using Tapatalk
mramirezusa said:
If you want to confirm your status, please adb, su, and "cat /sys/firmware/fuse/ReservedOdm" or just open the file in Root Explorer. If you see something like:
10000000000010001000300004000
Then you should NOT SBF anything from Motorola"
If you want to post your ReservedOdm to look and see if you will be fine to SBF 1.83 again
Probably you are safe if you actually installed Kenth by CDW or moto-fastboot (boot.img and system.img)
But if you actually run the update.zip or any update trought the normal android recovery screen and if you saw the following legend "updating AP20 bootloader" in that case you CAN NOT flash any SBF from Motorola
Sent from my MB860 using XDA App
Click to expand...
Click to collapse
I am on KP's 4.5.91 beta 3...........When I look at this file I have :
10000000000010001000100004000
Now KP's version of 4.5.91 is supposed to be safe to flash back and go ahead with Moto updates. If I follow what you are saying, it cannot be done?
CaelanT said:
I am on KP's 4.5.91 beta 3...........When I look at this file I have :
10000000000010001000100004000
Now KP's version of 4.5.91 is supposed to be safe to flash back and go ahead with Moto updates. If I follow what you are saying, it cannot be done?
Click to expand...
Click to collapse
10000000000010001000100004000
ok here it is:
10000000000010001000100004000
4= BL "unlock" did you ever unlock you BL with pudding?
0= BL lock
10000000000010001000100004000
1=NO UPDATE BL TO AP20 Ver. , so you applied GB by moto-fastboot process or by CDW
3=YOU HAVE A NEW BL AP20 Ver., so you indeed applied GB OTA by Android Recovery from the sdcard
so in other words the ones we are in "confirmed" brick land if we RSD any MOTOROLA SBF are the ones with "3"
So you seem you indeed apply unlock bootloader (please confirm?) but you never applied GB OTA by Android Recover update.zip, and as you already confirm you applied GB Kenneth version by CDW or moto-fastboot.
CaelanT said:
I am on KP's 4.5.91 beta 3...........When I look at this file I have :
10000000000010001000100004000
Now KP's version of 4.5.91 is supposed to be safe to flash back and go ahead with Moto updates. If I follow what you are saying, it cannot be done?
Click to expand...
Click to collapse
Status
1. Locked and rooted phone
2. I ran 1.2.6 sbf with RSD to return to a stock build
3. I unrooted phone
4. I ran OTA 1.8.3
5. I ran the Motorola Build 4.5.91 "not KP's" with Motorola cable from update.zip through USB flash drive
6. "Stopped Here" this is my current state
Unfortunately I did not use KP's version, and I don't know how to check for blown fuses since I haven't rooted and did not flash pudding "stopped after flashing OTA for fear of bricking" . I believe I have read that some have installed pudding from my current state to with a recoverable softbrick and then used fast booted flashing img of 1.8.3.
can anybody verify doing this safely? Sorry if this thread is repetitive but there is much confusion in here and I was gone two days from the forum when this all was taking place.
Much appreciated.
JiminSD I recommend you to root first by preinstall method first so you can check first the "fuses" to make sure how to proceed. To do the root you DO NOT need to be "unlock". If you need help just tell and I can guide you for the root process
JiminSD said:
Unfortunately I did not use KP's version, and I don't now how to check for blown fuses since I haven't rooted and did not flash pudding "stopped after flashing OTA for fear of bricking" . I believe I have read that some have installed pudding from my current state to with a recoverable softbrick and then used fast booted flashing img of 1.8.3.
can anybody verify doing this safely? Sorry if this thread is repetitive but there is much confusion in here and I was gone two days from the forum when this all was taking place.
Much appreciated.
Click to expand...
Click to collapse
Sent from my MB860 using XDA App
mramirezusa said:
10000000000010001000100004000
ok here it is:
10000000000010001000100004000
4= BL "unlock" did you ever unlock you BL with pudding?
0= BL lock
10000000000010001000100004000
1=NO UPDATE BL TO AP20 Ver. , so you applied GB by moto-fastboot process or by CDW
3=YOU HAVE A NEW BL AP20 Ver., so you indeed applied GB OTA by Android Recovery from the sdcard
so in other words the ones we are in "confirmed" brick land if we RSD any MOTOROLA SBF are the ones with "3"
So you seem you indeed apply unlock bootloader (please confirm?) but you never applied GB OTA by Android Recover update.zip, and as you already confirm you applied GB Kenneth version by CDW or moto-fastboot.
Click to expand...
Click to collapse
Yes, I unlocked with pudding following the instructions here ---> http://briefmobile.com/how-to-unlock-the-atrix-4g-bootloader, and yes I did flash KP's 4.5.91 and not the OTA.
Thanks for the clarification. Much appreciated!
So you are in the group of the lucky ones that actually can RSD "full" 1.83 or 1.57
The only thing you will lost the tag "unlocked" at the startup, so to get it back just RSD pudding again
I think you are asking this to return you phone to "stock" to be able to received the official OTA from moto/att right?
CaelanT said:
Yes, I unlocked with pudding following the instructions here ---> http://briefmobile.com/how-to-unlock-the-atrix-4g-bootloader, and yes I did flash KP's 4.5.91 and not the OTA.
Thanks for the clarification. Much appreciated!
Click to expand...
Click to collapse
Sent from my MB860 using XDA App
mramirezusa said:
So you are in the group of the lucky ones that actually can RSD "full" 1.83 or 1.57
The only thing you will lost the tag "unlocked" at the startup, so to get it back just RSD pudding again
I think you are asking this to return you phone to "stock" to be able to received the official OTA from moto/att right?
Sent from my MB860 using XDA App
Click to expand...
Click to collapse
I am thinking about it, but I may let some other brave souls try first, as I believe it will cause the issues the current leaked OTA has caused. My phone runs great at the moment on KP's 4.5.91.
Prior to this, I flashed back a couple of times on 4.1.83 and did what you said to get "unlocked" back on my boot screen. I think everyone is more or less worried about what the actual release version of GB might do if you are unlocked already.
I am in same situation as OP. From private discussions and reading different threads it seems that I can go from stock 2.3.4 OTA (no mods) with a locked bootloader to anything if I just use the small unlock/pudding followed by fastboot unlock commands and fastboot install cwm....then fruitcakes or any rom should be good to go. But im waiting for GB to go fully public....just gonna enjoy 2.3.4 for now until everything is all sorted out.
Sent from my MB860 using XDA Premium App
Agree. I think the first things to do when the real OTA is out is actually compare with the leak one, so at least we have an idea how to proceed.
Good Luck!
CaelanT said:
I am thinking about it, but I may let some other brave souls try first, as I believe it will cause the issues the current leaked OTA has caused. My phone runs great at the moment on KP's 4.5.91.
Prior to this, I flashed back a couple of times on 4.1.83 and did what you said to get "unlocked" back on my boot screen. I think everyone is more or less worried about what the actual release version of GB might do if you are unlocked already.
Click to expand...
Click to collapse
Sent from my MB860 using XDA App
Sorry but this is NOT TRUE:
"I can go from stock 2.3.4 OTA (no mods) with a locked bootloader to anything "
Anything in this case mean: NEED TO UNLOCK BL, NEED TO APPLIED ANY ROM BY CWM OR MOTO-FASTBOOT WAY
But here it is the CONs: UNTIL TODAY IF YOU APPLIED THE LEAK STOCK GB YOU CAN NOT RSD ANY MOTOROLA SBF, THAT MEAN INCLUDED GB SBF BECAUSE IS NOT OUT THERE YET, SO YOU NEVER WILL GET BACT TO "REAL" STOCK OR BE SURE 100% YOU CAN RECEIVED IN THE FUTURE ANY OTA DIRECTLY FROM MOTO/ATT IS NOT BEEN TESTED YET
NibblerWeather said:
I am in same situation as OP. From private discussions and reading different threads it seems that I can go from stock 2.3.4 OTA (no mods) with a locked bootloader to anything if I just use the small unlock/pudding followed by fastboot unlock commands and fastboot install cwm....then fruitcakes or any rom should be good to go. But im waiting for GB to go fully public....just gonna enjoy 2.3.4 for now until everything is all sorted out.
Sent from my MB860 using XDA Premium App
Click to expand...
Click to collapse
Sent from my MB860 using XDA App
Good clarification mrramirez.
My bad...should not have carelessly said "any". If ur on OTA 2.3.4 just stay put, and stay away from moto sbf
Sent from my MB860 using XDA Premium App
Thanks to all my question has been answered. I will stay put and not install any sbf's regardless of source until the new OTA is studied by developers.
So Guess who got an Atrix today? me! Guess who also probably bricked their atrix today? me!
So here is what happened:
1: I have an unlocked, rooted Atrix 4G from AT&T running 2.2 1.5.7 I believe.
2: I wanted to flash some roms, so I so I attempted to flash tenfar's CWM, but that didn't work, it said install succeeded but I could not get into CWM ( I tried everything, believe me, I'm no noob)
3: I then attempted to flash CWM from Rom Manager and so I did and I flashed the Atrix version, I then hit boot into recovery from within Rom Manager.
4: What I got next is a screen that says "failed to boot 2, starting RSD mode", now I cannot get passed that screen when it powers up.
5: Worst of all, using MSU (moto sw update), it says device is connected but not what kind, meaning I can't restore it, probably because I had adb mode turned on previosly.
update: after attempting to flash a new SBF, the phone told me it failed because the phone did not re-enumerate. Now I have the same problem, but with a new error message on the boot screen: Battery to low to flash!
I have searched everywhere, now I need to resort to you, xda community, Thanks So Much!!!
If you can get into RSD , check to see if fastboot is an option. If you can get into that I would advise to start over by erasing recovery. Command is fastboot erase recovery, then flash romracers recovery thru fastboot. Once you have recovery reboot into it and flash any ROM like Alien, Aura whatever you like.
Alien Atrix
See the thing is, fastboot is not an option , it immediately goes to RSD mode. I may have found a fix, and I am now flashing a new SFB with rsdlite
That's another option, noticed you were on 1.5.7 so I would advise 1.8.3 fruitcake sbf. Make sure you battery is fully charged, if your battery gives out during sbf flash you will hard brick your phone.
Alien Atrix
while I was flashing the sfb, the device failed to reenumerate and now it gives me a low battery warning, with no way to charge it, regardless, I have a friend who will let me borrow his battery tommorrow then Ill try to flash again, really I should use the 1.8.3? I just tried to flash the 1.2.6, so Your saying its ok to go forward with a SFB flash? I come from a world of Samsung's so these are all new to me besides the time I had a backflip for a week (ugh).
Are you sure your unlocked the bootloader? If you successfully unlocked you would have unlocked on top right corner of boot screen and have fastboot also.
Alien Atrix
I'm not sure if I have there is nothing that says "unlocked" at the top of the screen, and I could previously access the recovery and fastboot before this. I did not get this phone new, it came from the AT&T dev center or something like that. My dad works there.
You need to charge the battery. I stripped an old USB cable down and used the red with the positive side of the battery and black with the negative using tape to hold them in place then inserted the battery in the phone and plugged the USB in the computer. This allowed me to flash a ROM and unlock bootloader. Etc.
Warning this could harm you're phone. If you cross the wrong wires or touch more then just negative or positive areas of the phone and or battery. Although I didn't have any trouble with it you might.
If in doubt do it the right way buy a battery charger for your battery, use someone's battery or phone to charge yours.
Sent from my MB860 using Tapatalk
Ok Im at my computer, If you are unsure of unlocked bootloader I now recommend you RSD either 1.8.3 with unlocker & preinstall or the newest is 2.3.4 with unlocker & preinstall read this thread about 3 times first http://forum.xda-developers.com/showthread.php?t=1136261
Unlock using fastboot, after you get phone to boot for first time, ADB commands for preinstall root, after root use Root Explorer app then delete "install-recovery.sh" @ /system/etc.
Now you are ready to install the newest recovery by Romracer 3.2, Tenfars is outdated and no support from the developer. Read this thread 2 times http://forum.xda-developers.com/showthread.php?t=1204500 I recomend flashing this recovery thru fastboot per Romracer.
Now you are ready to flash your choice of ROM, follow proper procedure to flash new ROMs thru Recovery.
Also check out the unlocked sim codes thread in general, unlock sim.
If I helped click the thanks button
what Im confused on is what exactly i should flash if I am stuck in a kind of RSD mode bootloop/soft brick?
On your first post you said you were on 1.5.7 correct?
Atrix first released with 1.2.6 then updated to 1.5.7 then updated again to 1.8.3
Bootloader was unlocked with the 1.8.3 update
I updated to 1.2.6>1.5.7>1.8.3 then followed this tutorial http://briefmobile.com/how-to-unlock-the-atrix-4g-bootloader[/UR
ok thanks very much! Ill get back to you later once I get a fresh battery.
Ok so I'm about to flash the Pudding .sbf, am I doing this right?
iCracked said:
Ok so I'm about to flash the Pudding .sbf, am I doing this right?
Click to expand...
Click to collapse
yes, that's what you should have done in the first place. you can't do anything with "ROM" in its name without unlocking your bootloader which is why you're in this predicament. unlocked phone (maybe you mean SIM unlocked, free to use on any carrier) is not the same as an unlocked bootloader.
The title of this thread is epic. I lol'd.
Sent from my MB860 using XDA App
defnow said:
The title of this thread is epic. I lol'd.
Sent from my MB860 using XDA App
Click to expand...
Click to collapse
Definitely laughed myself. I knew it was a 'i bricked my pants'.
I voided my warranty.
pukemon said:
Definitely laughed myself. I knew it was a 'i bricked my pants'.
I voided my warranty.
Click to expand...
Click to collapse
haha thanks guys, yes I am SIM unlocked and everything just said unlocked so maybe I thought the reason they where specific to carrier locking was the radios? haha but I was wrong
I am using a Motorola Atrix with 4.5.91 build. I rooted my Atrix without unlocking the bootloader which is why I am getting a (Failed to boot 2 Starting in RSD Mode) message when i try to use Rom Manager to back up my current Rom. Do I have to unroot my Atrix in order to unlock it and if so how do I unroot it.
You have to unlock your bootloader n root your phone. Search the topics
Lovepeacestudios
My question was does it have to be done in that certain order. Unlock Bootloader then root.
Sousuke_Kira_Alexein said:
My question was does it have to be done in that certain order. Unlock Bootloader then root.
Click to expand...
Click to collapse
No it doesn't matter...
Sent from my GT-I9000 using xda premium
Sousuke_Kira_Alexein said:
I am using a Motorola Atrix with 4.5.91 build. I rooted my Atrix without unlocking the bootloader which is why I am getting a (Failed to boot 2 Starting in RSD Mode) message when i try to use Rom Manager to back up my current Rom. Do I have to unroot my Atrix in order to unlock it and if so how do I unroot it.
Click to expand...
Click to collapse
try to follow the order and see if its worked. any particular reason why you need not to follow the order?
Sousuke_Kira_Alexein said:
My question was does it have to be done in that certain order. Unlock Bootloader then root.
Click to expand...
Click to collapse
mramirezusa's auto scripts really help on this. Here's the thread:
http://forum.xda-developers.com/showthread.php?t=1182871