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 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 bought the phone a week ago and then it said I had an update so I updated over my wifi connection in the house.
Since I did this do I still use the RSD Lite to unlock the bootloader or is it unlocked already(reading sooo much stuff has confused me)? If I use RSD Lite do I dl the 2.3.4 sbf from the list on here?
I really dont want to brck my phone so any help is appreciated, thanks!
that OTA update will not unlock is the official moto update. Your bootloader is not unlocked unless it says "unlocked" in the top left corner of the screen when you're booting.
Look up "pudding" and use fastboot to unlock the bootloader
edit: you can use rsd if you want. Whatever your preference is.
I currently have no preference because I havent used either, which is easier to use?
supermerkin said:
I currently have no preference because I havent used either, which is easier to use?
Click to expand...
Click to collapse
read the posts in the dev forum...
pudding by far.
I want to thank everyone who has given great information here as my last two phones this place has been invaluable place of information.
I am now trying to be more "carefull" for a mistake I made. I ended up hard bricking a phone with the dreaded Failed to boot 0X1000. I have rooted phones before and understand the process enough to get by.
However I am back at square one I was months ago when I bricked my phone (since have gotten a new atrix), Im ready to try this again. I have done ALOT of reading but to be honest there seems to be do this and do thats than people in the world. I dont want to make the same mistake again.
Trying to find "the way" seems to be at issue. Ive seen everything from avoid RSD to using it to things not addressing as if the brick issue even happened. I feel like theres no path to follow. Im wondering how many others feel this way too who are at the crossroads of doing it.
My phone is rooted, and has Android 2.3.4 and System 4.5.91.MB860.ATT.en.US if that help to point me in the right direction.
Thank you!
You need to go to the IHOP thread, I believe it is stickied, and download only the unlock sbf. You will flash that with RSD and then follow the unlocking directions.. I.e. boot to fastboot, then issue the command "fastboot oem unlock" and follow the instructions on screen. Once done, you will be unlocked. You can then flash recovery via fastboot. You are then free to flash ROMs.
The only reason to ever have to flash an SBF after this is for warranty reasons. However, DO NOT flash a froyo one. Only flash gingerbread based ones or you will hard brick again.
Any questions?
Sent from my MB860 using xda premium
Yes if you follow the instructions in the IHOP thread you shouldn't have a problem:
http://forum.xda-developers.com/showthread.php?t=1136261&highlight=international+house+of+pudding
Here is a useful step-by-step guide to unlocking bootloader:
http://briefmobile.com/how-to-unlock-the-atrix-4g-bootloader
I personally would use the pudding file over the unlock file linked in the Briefmobile walkthrough, i'm sure they are the same but i know for a fact the pudding file works. This at least gives you the step-by-step procedure you are wanting.
Here's a video as well:http://www.youtube.com/watch?v=K4Bf9QIZsRI
I was pretty new to all this when i unlocked my atrix and didn't have any issues, just make sure you follow the instructions properly. Also as d3athsd00r stated try to avoid flashing SBF files via RSD after your bootloader is unlocked, the safest way to flash stuff is via CWM recovery.
My husband and I got our phones through AT&T (US) on Froyo; after the Gingerbread update I unlocked my bootloader & went the custom rom route while he stuck with root access.
So he unrooted & took the 4.5.141 update OTA; I took mine via Nottachtrix. Now he's asking about unlocking his BL too.
a) Is it possible without bricking? Seriously. Was the bricking issue earlier this year related to folks with unlocked BLs taking the OTA update, or folks trying to unlock after taking the OTA update?
b) I did mine by flashing pudding and unlocking through fastboot (then soft-bricking, then proceeding with fastboot anyway yada yada). Now I see this one-click-tool thing being thrown about. Should I be using that instead, or is there an updated "pudding" SBF I should be using?
c) Since megaupload went to pot, how valid are the original threads that contain these files? Still feels weird to think of "old" things as being ~10 months past. Ah well.
Use the unlocking sbf in the Android Development section sticky (pudding thread). It shouldn't give you any chance of a brick. It's called "try sbf" or something along those lines. Once flashed via RSD Lite, you fastboot oem unlock, copy your unique code and fastboot oem unlock "code" (without quotations). You have a chance of brick if you SBF down to a firmware lower than your current one, as it tries to flash new bootloader and will fail. AFAIK, you're even safe to reflash 4.5.141 OTA but people don't encourage it as you can easily confuse yourself and flash Froyo instead which WILL make you brick.