Im back with another problem im now unlocking the bootloader and i followed the instructions from [PUDDING] International House of Pudding! BL Unlock/root thread so when i go into cmd and type "fastboot oem unlock" i get this message:
<bootloader> OEM unlock is not implemented
OKAY [0.000s]
finished. total time: 0.016s
any ideas?
It seems Pudding didn't take. If my memory serves me correct, the message you received is for when the bootloader is still "encrypted". Can you give a brief "step-by-step" of what you did and what you saw on your phone while using Pudding?
carolinakidd said:
Im back with another problem im now unlocking the bootloader and i followed the instructions from [PUDDING] International House of Pudding! BL Unlock/root thread so when i go into cmd and type "fastboot oem unlock" i get this message:
<bootloader> OEM unlock is not implemented
OKAY [0.000s]
finished. total time: 0.016s
any ideas?
Click to expand...
Click to collapse
i used the instructions from here http://briefmobile.com/how-to-unlock-the-atrix-4g-bootloader and jumped to step 13 like it said in the guide cause i have 2.3.4 stock on my phone. i did what it said..got into fastboot mode, vol up to got into Fastboot protocol support mode and went into cmd found where i dl the extracted fastboot files and when i did the fastboot oem unlock i got that message on cmd
Unfortunately, that article was written before the "Official" release of gingerbread. At that time, they only had a "leaked" build that actually already had the un-encrypted bootloader. Since you have the "Official" build you will need to do all the steps.
carolinakidd said:
i used the instructions from here http://briefmobile.com/how-to-unlock-the-atrix-4g-bootloader and jumped to step 13 like it said in the guide cause i have 2.3.4 stock on my phone. i did what it said..got into fastboot mode, vol up to got into Fastboot protocol support mode and went into cmd found where i dl the extracted fastboot files and when i did the fastboot oem unlock i got that message on cmd
Click to expand...
Click to collapse
Ah well have to done tonight when I get off work lol thanks fir the info and help
Sent from my T-Mobile Atrix using xda
I do have 1 question when I do all that will I loose my sim unlock status and have to redo the unlock code?
Sent from my T-Mobile Atrix using xda
I'm almost positive you will not lose your sim unlock.
carolinakidd said:
I do have 1 question when I do all that will I loose my sim unlock status and have to redo the unlock code?
Sent from my T-Mobile Atrix using xda
Click to expand...
Click to collapse
Lol ok good looking out
Sent from my T-Mobile Motorola Atrix using xda
I did a Google search and found a bunch of results of people saying that you will not lose the sim unlock by flashing custom ROMs and doing OTA updates. SO, I'm guessing you should be safe but, as always, use caution.
carolinakidd said:
Lol ok good looking out
Sent from my T-Mobile Motorola Atrix using xda
Click to expand...
Click to collapse
*wipes brow* the operation was a success lol it jus said unlocked when it rebooted..i was kinda worried when i got the
SVF:105.1:2
Failed to boot 0X1000 error but it had a whole bunch of numbered options with it so i jus continued the fastboot process and wha-la i have a unlocked bootloader lol
Related
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
Does the US ATT OTA update to 4.5.91 unlock the bootloader or do i still need to manually do it with pudding after updating... i want to load a custom rom and want to be sure so i dont accidentally brick my phone
mscott998 said:
Does the US ATT OTA update to 4.5.91 unlock the bootloader or do i still need to manually do it with pudding after updating... i want to load a custom rom and want to be sure so i dont accidentally brick my phone
Click to expand...
Click to collapse
You must do it after updating. Flashing pudding on 4.5.91 will cause a soft brick which you immediately fix by entering the fastboot oem unlock command. Don't be fearful of the soft brick, it happens to everyone flashing pudding to 4.5.91.
dcarpenter85 said:
You must do it after updating. Flashing pudding on 4.5.91 will cause a soft brick which you immediately fix by entering the fastboot oem unlock command. Don't be fearful of the soft brick, it happens to everyone flashing pudding to 4.5.91.
Click to expand...
Click to collapse
i tried that and this is what i got in the command prompt
C:\root>fastboot oem unlock
< waiting for device >
...
(bootloader) OEM unlock is not implemented
OKAY [ 0.029s]
finished. total time: 0.029s
mscott998 said:
i tried that and this is what i got in the command prompt
C:\root>fastboot oem unlock
< waiting for device >
...
(bootloader) OEM unlock is not implemented
OKAY [ 0.029s]
finished. total time: 0.029s
Click to expand...
Click to collapse
This means you haven't flashed pudding
OK.. how do I flash pudding for stock 4.5.91? Pudding thread is vague
Sent from my MB860 using XDA App
mscott998 said:
OK.. how do I flash pudding for stock 4.5.91? Pudding thread is vague
Sent from my MB860 using XDA App
Click to expand...
Click to collapse
It's not vague. You download pudding and flash with RSD.
There's even a link to a step by step list
http://briefmobile.com/how-to-unlock-the-atrix-4g-bootloader
Just make sure you do ALL the steps. Don't skip to step 13. You have to flash pudding.
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.
Hi all,
So I spent like the whole afternoon tryin to unlock bootloader on my MB860 (rooted) with no luck. This is international version with 2.3.4 system updated OTA.
I tried to unlock bootloader with fastboot - no luck:
Code:
OEM Unlock is not implemented
So i tried flash unlocked sbf file (intl-fix-try1.sbf), still no luck:
Code:
Failed to boot 1
So, I've flashed whole sbf file: 1FF-olympus_emara-user-2.3.4-4.5.2A-74_OLE-31.20-release-keys-signed-NonEFIGSRetail-EU.sbf
Phone started and all was same as before this operation,
next - I tried another full sbf's:
1FF-olympus_emara-user-2.3.4-4.5.2A-74_OLE-31-release-keys-signed-Retail-GB.sbf
1FF-olympus_latam-user-2.3.6-4.5.2A-51_OLL-17.8-111109-release-keys-signed-BellMobility-CA-GAS_NA_OLYMPUSGBCANADABELL_P019.sbf
On both - failed to boot 1
so in the end only sbf that actually allows me to boot my cell is 1FF-olympus_emara-user-2.3.4-4.5.2A-74_OLE-31.20-release-keys-signed-NonEFIGSRetail-EU.sbf
And the question is - how to get unlocked bootloader for this one?
You really should have searched and read up ahead of time. "Failed to boot XXX" is a perfectly normal and expected thing to happen when unlocking the BL. You shouldn't have messed with any more SBFs. You can still try running the fixer script as mentioned in that thread, hopefully you didn't mess it up too bad.
Thank you ravilov, but isn't this script only for ATT devices?
I am fairly certain it can be used on an international device as well.
Thanks, will try later on today, so what I'm lookin for is this thread:
http://forum.xda-developers.com/showthread.php?t=1182871
and option no.3 is what i should use from this script to have it fixed?
just for the records - the phone is working after i installed only sbf working, all setings and data were not affected, only will need to root it again
stingu said:
so what I'm lookin for is this thread:
http://forum.xda-developers.com/showthread.php?t=1182871
and option no.3 is what i should use from this script to have it fixed?
Click to expand...
Click to collapse
Yes.
stingu said:
just for the records - the phone is working after i installed only sbf working, all setings and data were not affected, only will need to root it again
Click to expand...
Click to collapse
Yeah, that's to be expected.
I think the worst case scenario would be that you won't be able to unlock, in which case you might be one of the unlucky people with the non-unlockable bootloader. If not, this script should help in unlocking your BL.
so, with the script and option number 3 i got the same thing:
Code:
(bootloader) OEM unlock is not implemented
OKAY [ -0.000s]
finished. total time: -0.000s
Or should i first flash small sbf and then use the script?
any other suggestions or am I stuck with soft 2.3.4?
You did flash the pudding/ihop SBF, right? If not, try doing that before you attempt to run oem unlock. If you did already... Well, I'm out of ideas then. I guess while waiting for someone else to chime in, you might as well start mentally preparing that you might indeed stay stuck with the stock firmware.
Well, made it unlocked, it was little bit tricky, so what I did:
-flashed IHOP
-got failed to boot 1 error message again - here, where i was not aware of - I pressed vol up and it switched to fastboot protocol support with boot error present
-did the script, fail to boot error was still there after reboot
-did those 2 points with flashboot application (whole instruction available here http://forum.xda-developers.com/showthread.php?t=1302423):
Code:
13.back in your command prompt window type "fastboot oem unlock" no quotes
14.You will now receive a warning along with a unique device ID
15.Type the following commands using your unique device ID (the numbers in the command prompt) in place of the ####•
fastboot oem unlock ####
fastboot reboot
Now its time to install CWM somehow...