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
If I flash back to the stock firmware using the motorola sbf files, will my bootloader remain unlocked? I flashed back and flashed the unlocking sbf file. When my phone booted up it said unlocked, even though I didn't run the fastboot commands. I then ran the fastboot commands anyway and it said the bootloader was already unlocked. So will the unlocked bootloader always remain unlocked?
No. It's locked again
Sent from my MB860 using XDA App
it stays unlocked... despite what ^^^ said >.>
but it wont show until you just flash the pudding sbf like you did
P.S. no known way to re-lock as of yet
xepter said:
it stays unlocked... despite what ^^^ said >.>
but it wont show until you just flash the pudding sbf like you did
P.S. no known way to re-lock as of yet
Click to expand...
Click to collapse
Ok, thanks. I wasn't planning on relocking, I was just curious. So next time I won't even have to flash the sbf? The sbf just makes the unlocking text show up when it boots up, but it should still allow me to do stuff like install the new CWM recovery without that, right?
Another thing, when I flashed that sbf, I didn't go into RSD mode. I was in a hurry and I forgot so I just ran the RSD program, and it detected my phone, so I clicked start. I realized later that I hadn't booted up into RSD mode...
Should I be worried? Was the RSD mode just an unnecessary precaution?
You can't relock..............it's a hardware unlock (fuse lock). When you unlock a fuse burns out, and that's end of story.
If you flash back to a different firmware the word "unlocked" will go away, but you are still unlocked. You can unlock again to make the word "unlocked" reappear on the boot screen.
EU sbf on AT&T possible?
I am going to use an unlocked AT&T Atrix in Europe.
I am on 1.83 firmware with root (made with gingerbreak to get rid of AT&T boot animation etc.).
If I go on with unlocking the bootloader, can I flash any european sbf/rom? Are there any simfree european tock sbf/rom-s out there, and which is best? What about the french 2.1.1 sbf?
I just need a stable stock firmware without the AT&T limitations, do not want changing roms all the time.
Also, do I get sw updates if I do this?
Hi All,
I have an ATT Atrix and I flashed the 2.3.4 beta from http://forum.xda-developers.com/show....php?t=1159385 and forgot to unlock the bootloader. I already have the 1.8.3 radio. Right now the phone froze on Dual Core Screen. I guess this has something to do with not unlocking the bootloader. The phone can still boot to fastboot, the original Android recovery and RSD. But, It won't flash all roms I downloaded saying the signature validation is incorrect. And I tried to flashed the unlock sbf and try to unlock the bootloader. And the RSD lite kept saying unable to retrieve interface and thereby failed.
What do I need to do on this case?
Thanks for you help!!! Sincerely!!!!!!
There is a way around it it isn't easy.
There is a post back in dev section. DO NOT FLASH ANY RSD FILE TO YOUR PHONE AT ALL YOU WILL HARD BRICK IT.
Sent from my MB860 using XDA Premium App
I installed the Bell Gingerbread OTA update and not I have the Fastboot menu on the phone boot.
It does not say that the phone is unlocked.
Do I have an unlocked bootloader? Do I need to do something else to get it unlocked (IHOP?)? Is there a guide for it?
If there isn't unlocked on the startup, the bootloader doesn't unlocked.
Guide: http://forum.xda-developers.com/showthread.php?t=1136261
The Gingerbread update only gives you "Gingerbread". You still need to manually use IHOP to unlock the Bootloader...
Sent from my GT-I9000 using xda premium
my phone B/L is already unlocked. Will it be safe to flash this ROM via SD card?
so i unlocked my photon and when i booted it it up i seen at the moto screen that my phone was unlocked. now my question is i flashed the latest spf to update my phone and i dont see that unlocked at the moto screen when i boot up am i unlocked? if not do i have to go through with the whole procedure agian? and if i do will my system not be up to date
ajoerivera said:
so i unlocked my photon and when i booted it it up i seen at the moto screen that my phone was unlocked. now my question is i flashed the latest spf to update my phone and i dont see that unlocked at the moto screen when i boot up am i unlocked? if not do i have to go through with the whole procedure agian? and if i do will my system not be up to date
Click to expand...
Click to collapse
You will re-lock the phone by flashing the SBF. To unlock reflash the unlock file..you'll still be on the latest SBF.
I unlocked my bootloader by going into fastboot and typing fastboot oem unlock, then it asked my to type it with my device id, so i copied the device id so i typed fastboot oem unlock ******** and it worked, it says unlocked and works
Sent from my MB855 using XDA App
I had the same issue. If you click the link below to go to my thread the answer is posted by dcowboy. It works great and takes like 5 seconds.
http://forum.xda-developers.com/showthread.php?t=1352875
Hope this helps. If you have any questions let me know and I will see what I can help you with.