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
Just curious if the new 2.3.4 gingerbread OTA can be unlocked using pudding. I'm having to get my atrix replaced via warranty and if the replacement happens to come with gingerbread already on it i want to know if i'll be able to unlock it or if i'll be stuck using p-roms.
You should be able to unlock it with pudding since its the same version of gingerbread that we have. Also, don't flash any sbf files (except pudding) because it has the new bootloader and you'll hard brick it if you do.
You can unlock with pudding and fastboot BUT there's a high chance you'll soft brick first with 0x1000 ... all you need to do is get into fastboot mode and redo the oem unlock command.
mysticdrew said:
You can unlock with pudding and fastboot BUT there's a high chance you'll soft brick first with 0x1000 ... all you need to do is get into fastboot mode and redo the oem unlock command.
Click to expand...
Click to collapse
Alright, just to be absolutely, completely, all the way, 101% sure: does this OTA have ANY bootloader restrictions, be they a brick or non-unlockable bootloader. Has anybody tried to unlock the bootloader and run a custom ROM on the AT&T OTA? I just want to be able to run custom ROM's down the road (as in full ROM's, as in Cyanogenmod).
Do the OTA and never, never go back to any older stock version via RSD. Or you'll brick your phone.
@Chairsofter1138: the ota bootloader is locked. flash the pudding to unlock.
Alright, has anyone actually attempted to unlock the OTA via the pudding method? I'm being extra cautious here because I don't want to be stuck with a permanently locked down phone. Does it matter, then, if I use Kenthepenns (sp?) installation method or OTA straight from AT&T/ Motorola?
Chairsofter1138 said:
Alright, has anyone actually attempted to unlock the OTA via the pudding method? I'm being extra cautious here because I don't want to be stuck with a permanently locked down phone. Does it matter, then, if I use Kenthepenns (sp?) installation method or OTA straight from AT&T/ Motorola?
Click to expand...
Click to collapse
Yes everyone has been unlocking via pudidng because it's the same leaked version that has been out for the past couple weeks.
Yes Going to this OTA will make a brickable phone. You WILL NOT BE ABLE TO DOWNGRADE via traditional SBF.
This is the question everyone has been asking on every thread and the devs aren't answering.
I am locked and stock on 1.83. My fuse HAS not been burnt. I want to be
1. On Gingerbread
2. Unlocked
The problem is that all the current gingerbread sbfs said you had to be ALREADY unlocked to flash them, so I don't know how anyone has been testing this OTA with a locked bootloader. If you had the new Gingerbread, you were already unlocked, is how I understood it.
Questions in follow up to the above:
1. If I OTA before unlocking, what do I flash afterwards to unlock? Saying 'pudding' because there's 10,000 files in that thread, including links to an 'unlocker.sbf', as well as a full sbf operating system. What specific file?
2. Lots of new builds say they have an 'unlocked bootloader' built in, but nobody can figure out what that means. Does that mean you can flash them without being unlocked to unlock? What do you need to do to unlock after you flash them?
3. If I unlock now at stock 1.83, and take the OTA, what happens, is the bootloader locked again? I know OTA installs a new bootloader.
Please someone help me understand. There's too much hard bricking and misinformation out there on all the dev threads. What's true (and please tell us how you know).
I noticed everyone talking about the OTA. I saw on the Moto site that the new update is only available OTA but there's a link for download for the file "Blur_Version.4.5.91.MB860.ATT.en.US". Can anyone confirm that this can be installed without brick on an unlocked bootloader? I've seen other threads stating so but they're not really clear on what's being said.
m0use1 said:
This is the question everyone has been asking on every thread and the devs aren't answering.
I am locked and stock on 1.83. My fuse HAS not been burnt. I want to be
1. On Gingerbread
2. Unlocked
The problem is that all the current gingerbread sbfs said you had to be ALREADY unlocked to flash them, so I don't know how anyone has been testing this OTA with a locked bootloader. If you had the new Gingerbread, you were already unlocked, is how I understood it.
Questions in follow up to the above:
1. If I OTA before unlocking, what do I flash afterwards to unlock? Saying 'pudding' because there's 10,000 files in that thread, including links to an 'unlocker.sbf', as well as a full sbf operating system. What specific file?
2. Lots of new builds say they have an 'unlocked bootloader' built in, but nobody can figure out what that means. Does that mean you can flash them without being unlocked to unlock? What do you need to do to unlock after you flash them?
3. If I unlock now at stock 1.83, and take the OTA, what happens, is the bootloader locked again? I know OTA installs a new bootloader.
Please someone help me understand. There's too much hard bricking and misinformation out there on all the dev threads. What's true (and please tell us how you know).
Click to expand...
Click to collapse
+1 to everything this guy said..There is a ton of guests in this forum wondering the same **** too. Devs are doing a fantastic job, but us end users (including myself) don't really have a sense of direction right now.
So I started with an official 2.2.2 firmware from Bell. I think this thread might serve 2 purposes, because I had a really hard time figure out all the steps from start to finish as they were in separate threads. So if someone starts off with stock 2.2.2 and wants to get a custom rom, that's the way I manged to do it. Second purpose of this post is for me to find out how I could return my Bell Atrix to stock OTA and what it would imply. Thanks a lot in advance for your inputs.
-I rooted with SuperOneClick
-Unlocked BL with
http://forum.xda-developers.com/showthread.php?t=1136261
-Installed Tenfar's CWM
http://forum.xda-developers.com/showthread.php?t=1138541
-Verified which kernel to use D00 or 1100 and dled it:
http://forum.xda-developers.com/showthread.php?t=1169409
-Then I flashed Alien Rom Build #2 with Tenfar's CWM:
http://forum.xda-developers.com/showthread.php?t=1186537&highlight=bell
-Then tried to do the D00 Intl kernel in CWM without rebooting, that didn't work ... so I rebooted and went directly to fastboot and installed the kernel as the instructions say in the link:
http://forum.xda-developers.com/showthread.php?t=1169409
-Then booted for the first time, rebooted, and flashed the ninja theme in CWM
What I want to know is if ever I wanted to go back to stock with the new GB OTA from Bell 0.37.23 what would it imply:
-Rooting is still available, but is unlocking ? and could I still unlock the APN menu.
-My BL would get relocked? What would that imply for future updates.
Also if I decided to take that route; I would
1) http://forum.xda-developers.com/showthread.php?p=15975211#post15975211
2) Download the new OTA and install
3) Root and unlock...
Thank you for you input,
NiK
You just install the gobstopper. There is no new bell gb OTA from my understanding. Only the new ATT gb ota.
The gobstopper puts you on full 2.2.2.
Thought the latest OTA was for GB .. oh well ... what you be the implications of going back to stock ... would that affect the unlocked BL, would it relock it, would it make future mods more difficult of impossible .... I come from iPhone world so updating a firmware would have a lot of future implications ...
yes gobstopper would put you back to stock 2.2.2 and re-lock the bootloader...so yes you would have a boring ass atrix again...the only time (personal opinion) i would ever revert back is for warranty purposes. This way they can't tell you f'ed with your phone.
and yes it would make future mods impossible....basically all the mods and stuff out there right now would be useless to you...in fact if you did want to mod your phone you would only be able to deodex and theme..with a few other tiny modifications...that aren't even supported by the dev' who made them anymore because everyone is using GB now lol...i'm not sure why anyone would want to go back except for warranty purposes or they are selling to someone who is new to android and doesn't want to hack their phone...
/rant
cheers bro =)
J-Roc said:
yes gobstopper would put you back to stock 2.2.2 and re-lock the bootloader...so yes you would have a boring ass atrix again...the only time (personal opinion) i would ever revert back is for warranty purposes. This way they can't tell you f'ed with your phone.
and yes it would make future mods impossible....basically all the mods and stuff out there right now would be useless to you...in fact if you did want to mod your phone you would only be able to deodex and theme..with a few other tiny modifications...that aren't even supported by the dev' who made them anymore because everyone is using GB now lol...i'm not sure why anyone would want to go back except for warranty purposes or they are selling to someone who is new to android and doesn't want to hack their phone...
/rant
cheers bro =)
Click to expand...
Click to collapse
Hi,
That is incorrect. Once you are unlocked, you are always unlocked. You either have a bootloader that knows what unlocked means or you don't.
In this case you can always go back to IHOP to be unlocked. There is no permanent relock.
The point in going back to stock is to get OTA updates from Bell, not warranty claims because if you can get back to stock you don't need a warranty. It's when your phone is locked up that you want to use your warranty and by then it's too late.
Cheers!
Ok so once the bootloader has been unlocked, whatever happens I can't relock it even when applying an OTA upgrade that upgrades the bootloader ? That sounds like the exact opposite of what happened with iPhones or PS3s or whatever electronics that needed to be jailbroken, unlocked of whatever.
NiKTaMeR said:
Ok so once the bootloader has been unlocked, whatever happens I can't relock it even when applying an OTA upgrade that upgrades the bootloader ? That sounds like the exact opposite of what happened with iPhones or PS3s or whatever electronics that needed to be jailbroken, unlocked of whatever.
Click to expand...
Click to collapse
A fuse gets blown in this case. oem lock does nothing.
What you can do is install a bootloader that doesn't know about unlocking or that that paticular fuse means it's supposed to be unlocked, So the unlocked message doesn't show up on the main screen during boot and fastboot no longer works for signed partitions. However, restoring the unlocked bootloader restores the unlock by checking the blown fuse, and oem unlock no longer has to be done.
Cheers!
Thanks a lot to everyone for your replies.
P.S NF I'm waiting to try your gobstopper 2.3.4 stupid slow upload speeds
NiKTaMeR said:
Thanks a lot to everyone for your replies.
P.S NF I'm waiting to try your gobstopper 2.3.4 stupid slow upload speeds
Click to expand...
Click to collapse
It's done if you were waiting.
Sent from my MB860 using XDA Premium App
Hello. The subject matter says it all.
I currently have a rooted and unlocked AT&T Atrix on 1.26 version (yeah...still in ice age ) with a locked bootloader. Im with a non-US telco carrier. It came unlocked and rooted so that was great. No hassle but now I have started doing research on custom roms and webtop mods. I am trying to get around the info overload, so pls bear with my questions.
The overall goal is to have a stock/custom rom devoid of all the bloatwares and can run webtop2sd, and if that is not possible then, webtop. Very simple needs.
Option 1
======
To remain on stock rom and update to 1.83 version, and then to install the webtop2sd mod. Ideally I would like to boot off Debian from the microsd card. There was a post in which a forumer mentioned that he was able to "frankenstein" the webtop2sd and webtop mods. Thats great if I understood correctly.
Option 2
======
To update to 4.5.91 (probably a custom rom like Aura) and then install the webtop2sd/webtop mod.
What should be done?
I am going to update 1.26 -> 1.57 -> 1.83 -> 4.5.91 via system update. (which means I now have to signed with moto account...yes I have not as I read that there were some privacy issues.)
Through the update process, I would lose root. To keep everything clean, I am going to go through factory reset and then perform the update.
Once I am in 1.83 or 4.5.91, I will apply the root and unlock the bootloader. Which is the best way to go about this? Should I just follow the instruction here or this way. Or is there any other better way?
This is all I have for now until I install the webtop mod or the custom rom...
update your phone to wherever you want it at, then use this script to unlock the bootloader:
http://forum.xda-developers.com/showthread.php?t=1182871
after that, you can easily root your phone using the preinstall method found here:
http://forum.xda-developers.com/showthread.php?t=1138204 (second post)
if you update to 4.5.91 though, as you attempt to unlock the bootloader you will get a semi-hard brick, just have it boot up into fastboot mode and continue using the script. easy as pie!
I never got a semi-hard or *soft* brick from unlocking but that's just cause I must love to eat pudding =D . Do all the OTA updates, unlock / root, and then install the 2.3.4 fruitcake and install webtop. Best option by far, IMO, as far as the ease of transition goes. Should be cake. That's what I did and as long as you don't RSD lite with an .SBF back once on 2.3.4 OTA yer good to go.
eat yer fruitcake once updated to 2.3.4 OTA *stock gingerbread*-http://forum.xda-developers.com/showthread.php?t=1163009
Install a custom kernel if ya wanna overclock or undervolt, I would personally suggest Faux123's. -http://forum.xda-developers.com/showthread.php?t=1156040
aaand freeeze all that bloatware!-http://forum.xda-developers.com/showthread.php?t=972459
I read that its easier to update via SBF than OTA? What have your experiences been so far?
Alcapone263 said:
if you update to 4.5.91 though, as you attempt to unlock the bootloader you will get a semi-hard brick, just have it boot up into fastboot mode and continue using the script. easy as pie!
Click to expand...
Click to collapse
Maybe I should try to unlock it now... And then update.
tech_girl said:
I read that its easier to update via SBF than OTA? What have your experiences been so far?
Click to expand...
Click to collapse
well, i can't find it anymore but there is an SBF in the development forum that will allow you to update to 2.3.4 android without getting the brickable bootloader, but i personally don't see a point in using SBF. it's not meant for the end user, and using it can be risky.
SBF flashing is faster i believe, but as i said can also potentially harm your device if you're unsure of what you're doing.
SamCripp, one of the most esteemed devs here, suggests for the average person to completely stay away from sbf flashing after you've unlocked your bootloader unless you absolutely have to use it for something.
remember though, if you use the OTA update you CANNOT downgrade your device through SBF flashing, you HAVE to use the fruitcakes method. it WILL brick your device to downgrade, but only with the OTA update.
EDIT: and it's a semi-hard brick, it doesn't hurt your device in the least. you might panic at first, but it's as simple as booting into fastboot mode and finishing the script. or if you're more tech inclined, you can just do the fastboot oem unlock command through fastboot.
Phalanx7621 said:
....
eat yer fruitcake once updated to 2.3.4 OTA *stock gingerbread*-....
Click to expand...
Click to collapse
Alcapone263 said:
......
remember though, if you use the OTA update you CANNOT downgrade your device through SBF flashing, you HAVE to use the fruitcakes method.....
Click to expand...
Click to collapse
Fruitcakes??? All this jargon.... Hmmm...gotta check this out.
http://forum.xda-developers.com/showthread.php?t=1163009
yep, Fruitcakes. it's a CWM alternative to sbf flashing, much safer since it doesn't edit the bootloader at all, so there's no risk in hard bricking your device.
after you unlock your bootloader, you should install Romracer's CWM recovery here: http://forum.xda-developers.com/showthread.php?t=1204500
do all of your flashing through CWM after you unlock your bootloader, just remember to clear cache/dalvik/data between each ROM or you might get stuck in a bootloop.
Ok...CWM sounds more familiar....
If I understand correctly, I actually dont have to go via OTA. As long as I have the img file for flashing to each version, I could just use the CWM and not via OTA, right?
tech_girl said:
Ok...CWM sounds more familiar....
If I understand correctly, I actually dont have to go via OTA. As long as I have the img file for flashing to each version, I could just use the CWM and not via OTA, right?
Click to expand...
Click to collapse
well, you have to have an unlocked bootloader to get CWM. and to unlock your bootloader, you have to update to 1.8.3 or later.
after you unlock your bootloader, you can install CWM and proceed to just use CWM for your flashing needs.
i repeat again though, after you unlock your bootloader you should stay away from SBF flashing altogether. it's the quickest way to brick your device.
Alcapone263 said:
well, you have to have an unlocked bootloader to get CWM. and to unlock your bootloader, you have to update to 1.8.3 or later.
after you unlock your bootloader, you can install CWM and proceed to just use CWM for your flashing needs.
i repeat again though, after you unlock your bootloader you should stay away from SBF flashing altogether. it's the quickest way to brick your device.
Click to expand...
Click to collapse
+1
Once you unlock and get CWM installed its just a case of wiping the device and flashing zip files.
Yep after unlocking and getting rom racers cwm in, you get to have lots of fun and almost zero chance of hard bricking. Make sure you understand the pudding part. After you unlock throw rsd lite away.
After updating to 1.83 and unlocked, can I immediately installing a GB custom rom like Aura or Alien? Or do I need to update to 4.5.91 stock before I can install a custom rom? Which I assume is pre-rooted, which mean I dont have to root it..
tech_girl said:
After updating to 1.83 and unlocked, can I immediately installing a GB custom rom like Aura or Alien? Or do I need to update to 4.5.91 stock before I can install a custom rom? Which I assume is pre-rooted, which mean I dont have to root it..
Click to expand...
Click to collapse
You should be able to start flashing if you used pudding. No need to upgrade to .91 stock. I didn't. I think most roms are pre rooted now. Not that the rooting method was hard for the atrix.
I voided my warranty.
pukemon said:
You should be able to start flashing if you used pudding. No need to upgrade to .91 stock. I didn't. I think most roms are pre rooted now. Not that the rooting method was hard for the atrix.
I voided my warranty.
Click to expand...
Click to collapse
Yep thats how it works. once BL unlocked and CWM installed you can flash anything, including yes .91 stock.
Note that .91 stock OTA is not only the operating system but also modifies the bootloader hence all the hard brick warnings about flashing sbfs. When you flash zip files you don't touch the bootloader, so there is no chance of hard bricking. i.e. if you flash .91 stock from zip file from CWM as opposed to OTA, you get only the OS, not the bootloader update (which doesn't matter ).
Hello to all
I receive an atrix 4g locked to at&t usa. I unlocked with a code, after i unlock the BL.
I install cwm and romracer and flash CM7(2.3.6) rom from sd.
After i flash Darkside(2.3.5) rom. Now i want to return back to stock.
I have some small problems, the soft keys light is very dimm and the wifi signal is very low compared with my previous iphone 4.
The question is: is it safe to flash 4.5.91(2.3.4) stock sbf with rsd?
I know that the other option are fruitcakes but i just want to know if i can flash this vers with rsd.
System version: 4.5.133.mb860.att.en.us
Android version 2.3.5
Baseband: N_01.77.30P
I read many threads about but i'm still in the "fog". I know that the answer is somewere on the forum and sorry for opening another thread.
Thanks a lot for understanding.
While it's not recommended to use RSDlite after unlocking the bootloader, it will work as long as you only use the 4.5.91 GB2.3.4 SBF (signed). I have done it twice but at my own risk of course.
If you need to return to stock you can flash the fruitcakes, which are stock files. This method is definitely recommended over sbf.
M_Alin said:
Hello to all
I receive an atrix 4g locked to at&t usa. I unlocked with a code, after i unlock the BL.
I install cwm and romracer and flash CM7(2.3.6) rom from sd.
After i flash Darkside(2.3.5) rom. Now i want to return back to stock.
I have some small problems, the soft keys light is very dimm and the wifi signal is very low compared with my previous iphone 4.
The question is: is it safe to flash 4.5.91(2.3.4) stock sbf with rsd?
I know that the other option are fruitcakes but i just want to know if i can flash this vers with rsd.
System version: 4.5.133.mb860.att.en.us
Android version 2.3.5
Baseband: N_01.77.30P
I read many threads about but i'm still in the "fog". I know that the answer is somewere on the forum and sorry for opening another thread.
Thanks a lot for understanding.
Click to expand...
Click to collapse
live4nyy said:
While it's not recommended to use RSDlite after unlocking the bootloader, it will work as long as you only use the 4.5.91 GB2.3.4 SBF (signed). I have done it twice but at my own risk of course.
If you need to return to stock you can flash the fruitcakes, which are stock files. This method is definitely recommended over sbf.
Click to expand...
Click to collapse
Will flashing the SBF via RSD re-lock the bootloader? I need to take my phone in for a warranty swap (hardware issue) and don't want them to know I unlocked the phone.
It will hide the "unlocked" text during boot but it does not actually re-lock the bootloader. But when you think about it, even though they never intended for the end user to unlock the phone (hence the encrypted/locked bootloader), they still put the warning in if/when anyone unlocked the bootloader. It's there for a reason but I doubt they will find out.
ItsLunchBOX said:
Will flashing the SBF via RSD re-lock the bootloader? I need to take my phone in for a warranty swap (hardware issue) and don't want them to know I unlocked the phone.
Click to expand...
Click to collapse
live4nyy said:
It will hide the "unlocked" text during boot but it does not actually re-lock the bootloader. But when you think about it, even though they never intended for the end user to unlock the phone (hence the encrypted/locked bootloader), they still put the warning in if/when anyone unlocked the bootloader. It's there for a reason but I doubt they will find out.
Click to expand...
Click to collapse
So yeah I was impatient and tried to flash it without waiting for a reply. It kept failing and then all I would get on my phone was "Failed to boot 4 Starting RSD Protocol".
I ended up having to re-flash pudding, which was an adventure in itself (upgrading RSD, rebooting computer, trying different USB ports & cables before it would finally take). I think I will just take it in tomorrow even with it saying "Unlocked" and see if they will swap it out. I'm having touch screen issues with intermittent dead spots and ghost touches.
Did you try the stock SBF with the same combination of port and cable as you did when you successfully flashed pudding? I've heard those two factors can cause a bad flash in the past. I've read that a back port on the computer is recommended for sufficient power and using the actual OEM cable the phone came with is highly recommended as well.
Oh well, hope you get it swapped out, the people at the AT&T stores (if that's where you got it) usually don't pay no mind to that anyways.
ItsLunchBOX said:
So yeah I was impatient and tried to flash it without waiting for a reply. It kept failing and then all I would get on my phone was "Failed to boot 4 Starting RSD Protocol".
I ended up having to re-flash pudding, which was an adventure in itself (upgrading RSD, rebooting computer, trying different USB ports & cables before it would finally take). I think I will just take it in tomorrow even with it saying "Unlocked" and see if they will swap it out. I'm having touch screen issues with intermittent dead spots and ghost touches.
Click to expand...
Click to collapse
Hi,
I do have the same kind of query. I have AT&T Motorola Atrix 4G. I unlocked SIM, unlocked BL, rooted and installed CWM recovery, De-dexed and Webtop over HDMI hacked. I am still on AT&T Stock ROM 2.3.4 / Build # 4.5.91
I am facing random reboot problem while using 3G data service. I want to re-flash Stock 2.3.4 ROM. As per your reply in this thread I can only do this by flashing Fruitcakes as I have unlocked BL ... right? But in this link I am bit confused which file to download and flash amongst 2.3.4 / 2.3.5 att 4.5.133 / ATT 4.5.140 - 2.3.6? Also, after flashing a fruitcake can I still flash a custom ROM later on and at any point of time revert back to stock?
Thanks so much.
live4nyy said:
While it's not recommended to use RSDlite after unlocking the bootloader, it will work as long as you only use the 4.5.91 GB2.3.4 SBF (signed). I have done it twice but at my own risk of course.
If you need to return to stock you can flash the fruitcakes, which are stock files. This method is definitely recommended over sbf.
Click to expand...
Click to collapse
If you want to go back to stock, as in the last "Official" build released by Motorola, then you want the 2.3.4 build. And as long as you use the fruitcakes you can go back to a custom rom at any time.
sony108 said:
Hi,
I do have the same kind of query. I have AT&T Motorola Atrix 4G. I unlocked SIM, unlocked BL, rooted and installed CWM recovery, De-dexed and Webtop over HDMI hacked. I am still on AT&T Stock ROM 2.3.4 / Build # 4.5.91
I am facing random reboot problem while using 3G data service. I want to re-flash Stock 2.3.4 ROM. As per your reply in this thread I can only do this by flashing Fruitcakes as I have unlocked BL ... right? But in this link I am bit confused which file to download and flash amongst 2.3.4 / 2.3.5 att 4.5.133 / ATT 4.5.140 - 2.3.6? Also, after flashing a fruitcake can I still flash a custom ROM later on and at any point of time revert back to stock?
Thanks so much.
Click to expand...
Click to collapse
Thanks for your early reply ... Just one thing more I wanna ask that if I flash ATT 4.5.140 - 2.3.6 fruitcake, then can I flash ATT 2.3.4 - 4.5.91 over it? Is the brick warning for going back to stock ATT ROM only after having BL unlocked?
Thanks for your help
live4nyy said:
If you want to go back to stock, as in the last "Official" build released by Motorola, then you want the 2.3.4 build. And as long as you use the fruitcakes you can go back to a custom rom at any time.
Click to expand...
Click to collapse
Yes, you can flash 2.3.4 fruitcake over a 2.3.6 fruitcake. Just make sure to do the "wipes" (clear data/cache/factory reset/fastboot wipe/etc).
As far as I understand, the fruitcakes will not brick your device, as long as you follow the directions. The risk for bricking applies to using an SBF file and RSDlite.
sony108 said:
Thanks for your early reply ... Just one thing more I wanna ask that if I flash ATT 4.5.140 - 2.3.6 fruitcake, then can I flash ATT 2.3.4 - 4.5.91 over it? Is the brick warning for going back to stock ATT ROM only after having BL unlocked?
Thanks for your help
Click to expand...
Click to collapse