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 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.
Sorry for the question but seriously too much info (yes I've tried reading it all). The stickied thread is not entirely clear on this issue.
For stock locked OTA to 2.3 AT&T phone (but rooted), I just RSDlite the following SBF (using the briefmobile method), is that correct?
http://diamantephoto.com/trololol-unlock234.rar
Do I need to re-install my ROM, radio etc. after that or is it untouched aside from data loss? Do I lose root? I plan on using titanium to restore so don't mind if I have to run preinstall again.
use file located here and it's a nice tutorial..
http://forum.xda-developers.com/showthread.php?t=1136261&highlight=unlock
and stay away from RSD software...but for unlocking a bootloader you have to use it...if you even wanna go flash froyo or GB...i would suggest..
1) unlock bootloader (which you are doing already)
2) install CWM here is an instruction... http://forum.xda-developers.com/showthread.php?t=1138541...
3) fruit cake http://forum.xda-developers.com/showthread.php?t=1163009
wintermute000 said:
Sorry for the question but seriously too much info (yes I've tried reading it all). The stickied thread is not entirely clear on this issue.
For stock locked OTA to 2.3 AT&T phone (but rooted), I just RSDlite the following SBF (using the briefmobile method), is that correct?
http://diamantephoto.com/trololol-unlock234.rar
Do I need to re-install my ROM, radio etc. after that or is it untouched aside from data loss? Do I lose root? I plan on using titanium to restore so don't mind if I have to run preinstall again.
Click to expand...
Click to collapse
unlocking a bootloader does wipe out all the data...but won't effect rooting...
deziguy420 said:
use file located here and it's a nice tutorial..
http://forum.xda-developers.com/showthread.php?t=1136261&highlight=unlock
and stay away from RSD software...but for unlocking a bootloader you have to use it...if you even wanna go flash froyo or GB...i would suggest..
1) unlock bootloader (which you are doing already)
2) install CWM here is an instruction... http://forum.xda-developers.com/showthread.php?t=1138541...
3) fruit cake http://forum.xda-developers.com/showthread.php?t=1163009
Click to expand...
Click to collapse
Thanks mate I've read that post which is where I'm getting that link from. However its not entirely clear, and just wanted confirmation that the correct pudding to use is below. I don't want hard brick and there are so many posts about people going 2.3 OTA then bricking
http://diamantephoto.com/trololol-unlock234.rar ATT ONLY - Unlocker specifically for 2.3.4 [LOCKED] phones.
And I plan on using this procedure? with above pudding file.
http://briefmobile.com/how-to-unlock-the-atrix-4g-bootloader
As for wiping, no sweat, I'll manually move my titanium offline.
I'm not new to custom ROM or root etc. but new to Motorola and esp as the dev scene for this is relatively immature (due to locked BL) the info is hard to collate and digest. I'm not in US so I have no warranty recourse should I hard brick. I apologise again.
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 ).
My phone currently is rooted with CM7 installed, but I've been having some connectivity issues, so I need to send it back to AT&T to get it fixed/replaced.
Is it possible to get it all the way back to stock so that they will still honor my warranty?
What is wrong with you people that refuse to search and read!? Dont just expect us to answer the same questions over and over because you are too lazy to read and too dumb to understand you voided your warranty.
I understand I voided my warranty, and I knew what I was doing when I rooted/unlocked bootloader/installed CM7. I wasn't fully expecting to be able to get it back to stock, but I figured it couldn't hurt to ask.
It def wont hurt to search and read since this same question has been asked and answered 17 times. It does hurt to start a new thread about the same old subject.
Just rsd back to stock. If on gingerbread then use fruitcakes from samcripp
Alright, I'm sorry. You can go ahead and lock this then.
EDIT: At Shadow, I have a backup in CWM of stock. The main part I was worried about was the unlocked bootloader, but I guess that's not removable.
From what i've read, you can use rsd to flash the stock sbf and the unlocked text will be removed. There are a few posts here and also a video on youtube about relocking the ATRIX bootloader.
Sent from my MB860 using Tapatalk
Alright, thank you.
Aaronneyer said:
Alright, I'm sorry. You can go ahead and lock this then.
EDIT: At Shadow, I have a backup in CWM of stock. The main part I was worried about was the unlocked bootloader, but I guess that's not removable.
Click to expand...
Click to collapse
Correct, the unlocked bootloader is going to remain unlocked (although it's possible to get rid of the unlocked message when you boot up) and use fruitcakes from here: http://forum.xda-developers.com/showthread.php?t=1163009 if you're on gingerbread to go back to a stock rom. Just use intall from zip in CWM. If you're not on gingerbread use this: http://forum.xda-developers.com/showthread.php?t=991072
gsingh2011 said:
Correct, the unlocked bootloader is going to remain unlocked (although it's possible to get rid of the unlocked message when you boot up) and use fruitcakes from here: http://forum.xda-developers.com/showthread.php?t=1163009 if you're on gingerbread to go back to a stock rom. Just use intall from zip in CWM. If you're not on gingerbread use this: http://forum.xda-developers.com/showthread.php?t=991072
Click to expand...
Click to collapse
So does using the fruitcakes through cwm remove the unlocked? I was under the impression that using fruitcakes was just like flashing any other .zip rom and the "unlocked" would remain.
Sent from my MB860 using Tapatalk
EzEddie said:
So does using the fruitcakes through cwm remove the unlocked? I was under the impression that using fruitcakes was just like flashing any other .zip rom and the "unlocked" would remain.
Sent from my MB860 using Tapatalk
Click to expand...
Click to collapse
Back when I flashed older stock versions with RSD, the unlocked would disappear. Yesterday I flashed a fruitcake for the first time, but the unlocked was still there. So something about the sbf files got rid of the unlocked text. This means that installing a fruitcake won't get rid of it, but it's definitely possible. I don't know how though, sorry. You could try flashing a 2.3.4 sbf but that's highly discourage because it causes hard bricks.
Aaronneyer said:
My phone currently is rooted with CM7 installed, but I've been having some connectivity issues, so I need to send it back to AT&T to get it fixed/replaced.
Is it possible to get it all the way back to stock so that they will still honor my warranty?
Click to expand...
Click to collapse
Go to the restroom