Related
I update to 2.3.4 through android recovery...but i did something wrong doing an sbf through RSD lite. But now i have this :
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
IDK if i can flash anything else...can somebody help me...
well you have the fastboot option, did you try to fastboot a good IMG?
i haven't tried anything...how can i fastboot an IMG?
darth_twins said:
i haven't tried anything...how can i fastboot an IMG?
Click to expand...
Click to collapse
go to the dev forum and learn how to install via fastboot. you should be able to download the .img files for a specific OS, and then via your computer and USB flash it onto your phone.
http://forum.xda-developers.com/showthread.php?t=1163342
p.s. some "just checking" questions:
1. did you unlock your bootloader?
2. do you have tenfar's most recent CWM installed?
3. how far into the 2.3.4 install did you get, before it failed, and what version of SBF did you try to flash back to?
ok...
1. i never unlock the bootloader
2. i don't have a CMW installed
3 i installed sucessfully the 2.3.4 but then tried to unlock the bootloader ...well that's how i get in this mess
in that case, you probably should have read this thread then (stickied at the top of the dev forum):
http://forum.xda-developers.com/showthread.php?t=1160408
you've got a hard brick... hard lesson to learn. next time make sure you're more familiar with what you're doing with the device and all the risks and solutions. sorry
My understanding of hard brick is that you wouldn't have rsd or fastboot access. Based on the stickie threads that could happen after trying to flash a full sbf only, not the pudding one. I think you have a soft brick and there are lots of threads on how to recover from that, just search around. You should be able to use fastboot from here to flash some new boot and system images. Good luck.
Edit: whatever you do, do not rsd a full sbf from where you are, which will cause a hard brick.
Sent from my MB860 using XDA App
You can rsd a full image if it has pudding included.
Sent from my MB860 using XDA Premium App
Use rsd to flash this sbf it should work.
http://www.multiupload.com/4K3C9VS9IJ
Sent from my MB860 using XDA Premium App
Am I understanding that people are getting this error just trying to use the pudding to unlock the bootloader?? I thought it was still safe to do, even if you did already use the "official" OTA update through android recovery.
Its getting so confusing around here.
Sent from my MB860 using XDA App
One thing before we begin, unlocking your bootloader will format/erase data. Basically a factory data reset so make sure you backup everything.
Here is what I did to unlock my bootloader and gain root.
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.
DO NOT FLASH ANY SBF UNTILL YOU COMPLETE THE ENTIRE STEP OR YOU WILL HARD BRICK aka phone will be a paper weight.
Once you flash pudding phone won't boot instead will go to a text only 14 option screen and say something like, No OS found, failed to boot 0x1000. Here is a picture for people who are freaking out. http://forum.xda-developers.com/attachment.php?attachmentid=651901&d=1310422138 .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 afterwards.
Jnewell05 said:
One thing before we begin, unlocking your bootloader will format/erase data. Basically a factory data reset so make sure you backup everything.
Here is what I did to unlock my bootloader and gain root.
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.
DO NOT FLASH ANY SBF UNTILL YOU COMPLETE THE ENTIRE STEP OR YOU WILL HARD BRICK aka phone will be a paper weight.
Once you flash pudding phone won't boot instead will go to a text only 14 option screen and say something like, No OS found, failed to boot 0x1000. Here is a picture for people who are freaking out. http://forum.xda-developers.com/attachment.php?attachmentid=651901&d=1310422138 .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 afterwards.
Click to expand...
Click to collapse
Thanks for clearing that up, I thought we could still do it.
Sent from my MB860 using XDA App
Jnewell05 said:
One thing before we begin, unlocking your bootloader will format/erase data. Basically a factory data reset so make sure you backup everything.
Here is what I did to unlock my bootloader and gain root.
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.
DO NOT FLASH ANY SBF UNTILL YOU COMPLETE THE ENTIRE STEP OR YOU WILL HARD BRICK aka phone will be a paper weight.
Once you flash pudding phone won't boot instead will go to a text only 14 option screen and say something like, No OS found, failed to boot 0x1000. Here is a picture for people who are freaking out. http://forum.xda-developers.com/attachment.php?attachmentid=651901&d=1310422138 .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 afterwards.
Click to expand...
Click to collapse
I have the same error "Failed to boot 0x1000" but i don't have the available modes menu. the phone shows this message for about 3 seconds and then shuts off ... any help will be appreciated.
Just a note this happened after me installing the new 4.5.9.1
hakemcpu said:
Just a note this happened after me installing the new 4.5.9.1
Click to expand...
Click to collapse
And then what did you do?
mysticdrew said:
And then what did you do?
Click to expand...
Click to collapse
I then tried to support Arabic for the GB using this link
http://forum.xda-developers.com/showthread.php?t=1062761
when copying "libandroid_runtime.so" and "libicuuc-arabic.so" the phone turned off and when i tried to open it, it stayed at the motorola sign.
at that time i was able to to see the boot menu when i press and hold the volume down, I tried to restore the system the way it was before GB, some posts stated that downgrading to 4.1.83 will hard brick the phone, so i tried to install 4.1.57 Stock rom and Now i am stuck with this error
If anybody could help because it is not possible for me to return it to the US to get fixed and then get it back here.
Any help is appreciated.
hakemcpu said:
I then tried to support Arabic for the GB using this link
http://forum.xda-developers.com/showthread.php?t=1062761
when copying "libandroid_runtime.so" and "libicuuc-arabic.so" the phone turned off and when i tried to open it, it stayed at the motorola sign.
at that time i was able to to see the boot menu when i press and hold the volume down, tried to install 4.1.5.2 Stock rom and Now i am stuck with this error
If anybody could help because it is not possible for me to return it to the US to get fixed and then get it back here.
Any help is appreciated.
Click to expand...
Click to collapse
how did you try to install the 4.1.5.2 stock rom? sbf RSD? If so, then you're likely hard bricked with no chance of recovery. Sorry. If you can still get into fastboot mode then you have a chance.
mysticdrew said:
how did you try to install the 4.1.5.2 stock rom? sbf RSD? If so, then you're likely hard bricked with no chance of recovery. Sorry. If you can still get into fastboot mode then you have a chance.
Click to expand...
Click to collapse
yes i used RSD mode
mysticdrew said:
how did you try to install the 4.1.5.2 stock rom? sbf RSD? If so, then you're likely hard bricked with no chance of recovery. Sorry. If you can still get into fastboot mode then you have a chance.
Click to expand...
Click to collapse
isn't there any other way even if it is difficult i can give it a shot
hakemcpu said:
isn't there any other way even if it is difficult i can give it a shot
Click to expand...
Click to collapse
No sorry it is dead. There were warnings all over the forum.
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
Failed to boot 2
Starting RSD mode.
I tried to flash the new Ninja Rom from the Gingerblur rom. I am now stuck on the dual core screen with the message above stuck there. Someone please help, I looked through the forms but it seems like I should be able to get into recovery still, which I cannot... If you need any other info please let me know....
rp2gardner said:
Failed to boot 2
Starting RSD mode.
I tried to flash the new Ninja Rom from the Gingerblur rom. I am now stuck on the dual core screen with the message above stuck there. Someone please help, I looked through the forms but it seems like I should be able to get into recovery still, which I cannot... If you need any other info please let me know....
Click to expand...
Click to collapse
Were you unlocked before trying to flash Ninja rom?
unlocked... no at least I dont think? Obviously I was rooted but unlocked i dunno...
That is why, your bootloader has to be unlocked.
Sent from my MB860 using XDA Premium App
rp2gardner said:
unlocked... no at least I dont think? Obviously I was rooted but unlocked i dunno...
Click to expand...
Click to collapse
Ah ok... gingerblur was a pseudo-rom... made before we were able to install custom roms because we couldn't unlock our bootloader. That changed last month when devs figured it out and thus the newer custom roms. To install them you need to unlocked your bootloader.
Please read this thread for information on how to unlock
http://forum.xda-developers.com/showthread.php?t=1136261
Now, since you're already softbricks, running that may not work right now. BUT it's start.
My suggestion- read the thread, follow the instructions and see if that gets you to boot up properly after running the oem unlock.
If not, then download a fresh stock 1.8.3 SBF form the development thread and RSD flash that.
Ok thank you for your help, will post a question if I come to one. How would I download the stock 1.8.3 SBF if I am stuck on the boot screen? Im feeling like Im in over my head, Paypal donation to anyone who can walk me through this....
rp2gardner said:
Ok thank you for your help, will post a question if I come to one. How would I download the stock 1.8.3 SBF if I am stuck on the boot screen? Im feeling like Im in over my head, Paypal donation to anyone who can walk me through this....
Click to expand...
Click to collapse
Stock SBFs are in the development forum as well.
I guess first things first, do you have the tools needed
Do you have or know how to use RSD?
How about Fastboot?
Just downloaded RSD lite and flashed the SBF..
"Open and extract the Fastboot package from above" is the step I am on.. Not sure where to go from here.
The phone rebooted to the same screen that it was at before with the error message but says PASS in RSDLite for the sbf flash
rp2gardner said:
Just downloaded RSD lite and flashed the SBF..
"Open and extract the Fastboot package from above" is the step I am on.. Not sure where to go from here.
The phone rebooted to the same screen that it was at before with the error message but says PASS in RSDLite for the sbf flash
Click to expand...
Click to collapse
Which SBF? The pudding/unlock?
If you flashed the pudding SBF, then you need to do the fastboot steps next.
Did you download and unzip the fastboot package to your computer?
I did, I just dont know what to do with fastboot. Do I run it or what?.. THANKS A TON BY THE WAY...
Ok, I still have the failed to boot 2, but I am now getting the Starting Fastboot protocol support. I dont understand this step..
Type the following command:
fastboot oem unlock
rp2gardner said:
I did, I just dont know what to do with fastboot. Do I run it or what?.. THANKS A TON BY THE WAY...
Click to expand...
Click to collapse
let's say you saved and extracted the fastboot files to c:\fastboot
then you have to open up CMD (start - run - cmd )
then cd to the directory it's saved (in this example c:\fastboot )
Now you have to get your phone into fastboot mode (directions are in the link), but in short, as you turn on your phone, hold the down button. THen it should say fastboot, then hit volume up, should say entering fastboot
Then back on computer in the command window
while your in the fastboot directory
type the oem unlock command (specific command in the instruction).
after it's all done, type fastboot reboot.
I have to go now for a while, but if all that doesn't work. I suggest flashing via RSD the 1.83 SBF with Pudding built in.
The download is in the pudding thread near the top "1. All phones If you have unlocked then try to use 2.3.4 update zip from Motorola servers, then revert back to a "pre-unlock" version(1.8.3 or earlier on ATT) you will get bricked! Do not use the OTA via experimental servers and revert to older versions WITHOUT pudding preinstalled in your sbf.
ATT ONLY Get your 1.8.3 with pudding from gitbrew or multiupload."
I cant figure out where to type the command in (fastboot oem unlock) i have the screen that came up when i located the fastboot. It has a list of commands, but nothing about oem unlock...
rp2gardner said:
I cant figure out where to type the command in (fastboot oem unlock) i have the screen that came up when i located the fastboot. It has a list of commands, but nothing about oem unlock...
Click to expand...
Click to collapse
Is your phone in fastboot mode and connected?
All you gotta do is just type the command in the command window
C:\fastboo\ fastboot oem unlock
Hello All,
I'm new here, so I'm not exactly sure if this is the correct forum to be posting this, but here's my question:
When I attempt to unlock my bootloader using fastboot and the "fastboot oem unlock" command, it simply returns:
Code:
... INFOOEM unlock is not implemented
OKAY [ 0.001s]
Has anyone else gotten this message or anything like it? Or am I doing something wrong?
I'm rooted and running the 4.5.91 (ATT) update, and I updated from Gingerblur 3.5 using the PC update program.
The only way to unlock bootloader at this time is flashing pudding and then running fastboot OEM commands
SevenandForty said:
Hello All,
I'm new here, so I'm not exactly sure if this is the correct forum to be posting this, but here's my question:
When I attempt to unlock my bootloader using fastboot and the "fastboot oem unlock" command, it simply returns:
Code:
... INFOOEM unlock is not implemented
OKAY [ 0.001s]
Has anyone else gotten this message or anything like it? Or am I doing something wrong?
I'm rooted and running the 4.5.91 (ATT) update, and I updated from Gingerblur 3.5 using the PC update program.
Click to expand...
Click to collapse
Sent from my MB860 using XDA App
Really? Huh- I found that fastboot method on this website
briefmobile(dot)com/how-to-unlock-the-atrix-4g-bootloader
It says to use the command prompt to run fastboot and unlock it- I'm not sure if this was disabled or something, because it seems to have worked for most people on the 2.3.4 beta.
SevenandForty said:
Oh, really? I found that fastboot method on this website
briefmobile(dot)com/how-to-unlock-the-atrix-4g-bootloader
It says to use the command prompt to run fastboot and unlock it- I'm not sure if this was disabled or something, because it seems to have worked for most people on the 2.3.4 beta.
Click to expand...
Click to collapse
if you're running the ota update, then you don't have an unlockable bootloader. you need to flash a pudding sbf to get one, which you can find instructions to on either the general forum or the dev forum.
Oh, I see. Thanks!
same problem
I also have the same problem but I have a stock 2.3 atrix does it make a difference?
I had to flash the 4.5.91 pre root sbf Via rsd lite then run that fastboot command.
Sent from my MB860 using XDA App
You need to flash the unlock sbf first. Just remember that if you're on 2.3.4, after you flash the sbf, the phone will reboot and soft brick - that's normal. Be ready to fastboot flash RomRacer's CWM recovery, and have the two 2.3.4 Fruitcake builds on your external sdcard beforehand.
Once you've flashed RomRacer's recovery successfully, pull the battery, put in your SIM and sdcard again, boot into recovery, and then install both fruitcake builds.
After that, your phone will boot and you can root it at your leisure.
SevenandForty said:
Hello All,
I'm new here, so I'm not exactly sure if this is the correct forum to be posting this, but here's my question:
When I attempt to unlock my bootloader using fastboot and the "fastboot oem unlock" command, it simply returns:
Code:
... INFOOEM unlock is not implemented
OKAY [ 0.001s]
Has anyone else gotten this message or anything like it? Or am I doing something wrong?
I'm rooted and running the 4.5.91 (ATT) update, and I updated from Gingerblur 3.5 using the PC update program.
Click to expand...
Click to collapse
Are you flashing the .sbf first? If not, that is your problem or you have the same luck as me.. One or the other. Anyway, this is how I fixed mine:
I had this issue too.. Very irritating. I was using Linux to get my phone unlocked. When I went home from work, I tried again on windows 7 this time using RSDLite. It kinda worked. RSDLite got to 98%, the phone crashed and the flash status displayed failed. However, at 98%, the only thing left to do was for the phone to turn back on and verify the flashed image as far as I was concerned. Anyway, the phone said "Operating system not found" and went into fastboot mode from there. I felt I had nothing to lose by moving on. I issued a fastboot oem restore, and was able to get my code. I then reissued the command and typed in the whole code as windows wouldn't let me copy/paste from the command prompt (thanks Bill..). After doing this and pressing enter, my bootloader was nice and unlocked in about half a second. I rebooted using fastboot, and it locked up, so a battery pull got me working just fine. Hope this helps someone.
same problem
i have the same problem
1. i did use the sdf. but in the end it says FAIL in RSD
2. cant continue
3. still searching for answer:crying:
---------- Post added at 06:18 PM ---------- Previous post was at 06:07 PM ----------
hammerlock13 said:
Are you flashing the .sbf first? If not, that is your problem or you have the same luck as me.. One or the other. Anyway, this is how I fixed mine:
I had this issue too.. Very irritating. I was using Linux to get my phone unlocked. When I went home from work, I tried again on windows 7 this time using RSDLite. It kinda worked. RSDLite got to 98%, the phone crashed and the flash status displayed failed. However, at 98%, the only thing left to do was for the phone to turn back on and verify the flashed image as far as I was concerned. Anyway, the phone said "Operating system not found" and went into fastboot mode from there. I felt I had nothing to lose by moving on. I issued a fastboot oem restore, and was able to get my code. I then reissued the command and typed in the whole code as windows wouldn't let me copy/paste from the command prompt (thanks Bill..). After doing this and pressing enter, my bootloader was nice and unlocked in about half a second. I rebooted using fastboot, and it locked up, so a battery pull got me working just fine. Hope this helps someone.
Click to expand...
Click to collapse
sir, could you kindly pls. give the codes step by step, it will help a lot, i can not use my Atrix Thanks in Advance
OEM unlock is not implemented
I also have this issue
I am desperately looking for a solution without luck for my rooted
Atrix 4G Buld 4.5.2A
GB 2.3.4
If someone can point me to a solution I will be very glad
Thanks
Eli
i'm in the same situation....
help please
FIXED it and now my phone is unlocked
you have to flash the phone with RSD this file http://diamantephoto.com/IHOP_Bell.rar
and rerun the command to give you the phone ID
hope it helps for you
I'm new to rooting phones I have a Moto Photon 4G. Ido have root access but when i try to boot into Android Recovery i get a message saying fail boot 2 entering RSD mode. So I'm not able to flash any roms to my phone. It's getting frustrating I have used google to find a solution but I'm a NOOB haha so I'm not really sure what I'm looking for. Please can anyone help?
Have you unlocked it? Can't do much without unlocking and installing a custom recovery.
If not, start here.
I'm pretty sure it's unlocked but how can I be sure. I used Root check basic and it confirmed I do have root accsess.
Root and unlocking are two separate processes. When you boot the phone, if you're unlocked, it will say unlocked in the upper left on the screen with the red m.
Sent from my MB855 using XDA
My phone is not unlock so what is the next step I need to take to unlock it? Thank you all for your help. I'm begging lol please help it's making me crazy
The link Kevets gave you will tell you everything you need to know. And if you look for qbking77 on youtube he has walkthroughs for the process.
Sent from my MB855 using XDA
if you email me i'll give you the link i can't post links yet.
shows step by step how to unlock my phone but i get stuck on this part below
Now click your start menu and type "cmd", right click the cmd program and copy it to your unlock pack directory.
i'm not sure how to copy it.
Open the newly copied cmd.exe and type "fastboot oem unlock xxxxxxxxxxxxxxxx" WITHOUT THE " " MARKS and replaces the x's with your code that you got from the above step.
The links were helpful but some are outdated or my comp says they contain malware and wont allow me to proceed any further and yes qbking77 has very helpful videos
bigdaddy619 said:
motorolaphoton.webs.com/ unlocking
shows step by step how to unlock my phone but i get stuck on this part below
Now click your start menu and type "cmd", right click the cmd program and copy it to your unlock pack directory.
i'm not sure how to copy it.
Open the newly copied cmd.exe and type "fastboot oem unlock xxxxxxxxxxxxxxxx" WITHOUT THE " " MARKS and replaces the x's with your code that you got from the above step.
The links were helpful but some are outdated or my comp says they contain malware and wont allow me to proceed any further and yes qbking77 has very helpful videos
Click to expand...
Click to collapse
Once the cmd.exe comes up in your start menu, right click it and choose "copy." Then open your unlock pack directory (where you unzipped the unlock pack zip file) and right click, then choose "paste." Then double click the pasted cmd.exe. I'm not sure what has you stuck exactly.
Sent from my MB855 using XDA
I give up apparently I'm to stupid to do it Thanks for your help
I have watched qbking77 videos
How to install the Android SDK, ADB and Fastboot on your PC
How to unlock the Motorola Photon 4G bootloader
Installing Android SDK, ADB and Fastboot didn't work for me.
Hope this helps
Try my site and tell me if that helps.
https://sites.google.com/site/mophocorner/
You need to unlock your phone and flash CWM in order to put a custom rom on it. Rooting it is he easy stuff. If you flash a custom rom 99.5% of the time it is pre rooted so...
I have tried that method with no success. Thanks for your help
You have to use RSD-lite to flash the stock phone rom back onto your phone before you can unlock it.
I did the same thing you did when I first tried to load a custom rom, and many other people here have done the same thing as well, we have all gotten through it. It took me about 5 hours of trying to get everything straightened out, and the next day I was running overclocked CM7 with jokers kernel.
Close please
Sent from my MB855 using xda app-developers app