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
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
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
I've looked around and I can't seem to find a way to unlock the bootloader on my 2.3.6 Atrix. Most tuts are for 2.3.4. What's the best way to do it?
http://dl.dropbox.com/u/34025287/4547-fix-try2.sbf
Flash this with RSD lite - run the fastboot oem unlock commands if needed. Its as simple as that
G-Man. said:
http://dl.dropbox.com/u/34025287/4547-fix-try2.sbf
Flash this with RSD lite - run the fastboot oem unlock commands if needed. Its as simple as that
Click to expand...
Click to collapse
You just run those in ADB, right?
mugabuga said:
You just run those in ADB, right?
Click to expand...
Click to collapse
Yes that's correct. You shouldn't need to if you unlocked your bootloader before the .141 update. To re-root use this method, it will give a couple errors at a certain point, just disregard the errors and continue with the commands and reboot your Atrix when you've finished - http://www.atrixforums.com/forum/mo...ing-stock-locked-2-3-4-2-3-6-a.html#post47155
G-Man. said:
Yes that's correct. You shouldn't need to if you unlocked your bootloader before the .141 update. To re-root use this method, it will give a couple errors at a certain point, just disregard the errors and continue with the commands - http://www.atrixforums.com/forum/mo...ing-stock-locked-2-3-4-2-3-6-a.html#post47155
Click to expand...
Click to collapse
But even if I've never unlocked it, it should still work?
mugabuga said:
But even if I've never unlocked it, it should still work?
Click to expand...
Click to collapse
If you've never unlocked it, it will act like a soft brick and hang on the first reboot - this is normal. You should have a screen pop up with a list of a dozen or more options, you'll need to select 'fastboot' and then run the command in ADB - fastboot oem unlock - this will give you a unique ID # - repeat the fastboot oem unlock command with the # at the end like this - fastboot oem unlock <unique ID # here> and press enter, it will give a warning about voiding your warranty, select yes and continue. From there, it should proceed with the unlock. After wards you'll need to let it fully reboot. Then boot your Atrix BACK into fastboot again, and flash RomRacers latest recovery with ADB. You can find the thread in the Development section. Then you load your ROM of choice onto your internal SD card and boot into CWM Recovery (RomRacers) and flash the ROM - give your Atrix 10-15 mins to fully boot after you install your ROM.
G-Man. said:
If you've never unlocked it, it will act like a soft brick and hang on the first reboot - this is normal. You should have a screen pop up with a list of a dozen or more options, you'll need to select 'fastboot' and then run the command in ADB - fastboot oem unlock - this will give you a unique ID # - repeat the fastboot oem unlock command with the # at the end like this - fastboot oem unlock <unique ID # here> and press enter, it will give a warning about voiding your warranty, select yes and continue. From there, it should proceed with the unlock. After wards you'll need to let it fully reboot. Then boot your Atrix BACK into fastboot again, and flash RomRacers latest recovery with ADB. You can find the thread in the Development section. Then you load your ROM of choice onto your internal SD card and boot into CWM Recovery (RomRacers) and flash the ROM - give your Atrix 10-15 mins to fully boot after you install your ROM.
Click to expand...
Click to collapse
EDIT: Fixed the problem by pulling the batt and unpluging from the computer.
mugabuga said:
Alright. It says it worked on the phone, but my RSD Lite claims it failed with an error switching phone to BP Pass through mode (0x70BE). Its just hanging at the success screen on my phone.
Click to expand...
Click to collapse
Can you upload a pic of the screen you are seeing?
[edit] I gotta get to bed, I'll check back here tomorrow if someone else is unable to assist you tonight. Its after midnight here and I'm getting over a bad cold still. I will check back here tomorrow.
mugabuga said:
EDIT: Fixed the problem by pulling the batt and unpluging from the computer.
Click to expand...
Click to collapse
Glad to hear that Ya had me a bit concerned for a minute there...
Has anyone ever seen this before? I have reflashed stock recovery to the phone and before i could switch options in the boot menu i was stuck to only rsd or fastboot. I am on 2.3.5 I sent rdl3 to the phone it restarted in bootloader or fastboot just a moto logo i sent the fastboot oem unlock command, peices of derpunlock and also a system.img. now i can choose android recovery in my boot menu but system still wont load.
Did u try doing factory reset from boot menu
Sent from my MB855 using xda app-developers app
Yes i did try that along with every other option given system still not booting up... but another strange thing ive noticed is that the android recovery is now letting me choose what zip i want to install from my sd card although i cannot because everything keeps failing the signature check. Has anyone been in this same situation?
I think i flashed the ap20bl.img with sv1 but i havnt flashed the microboot because i didnt know what command to issue in fastboot mode. for the bootloader i typed something along the lines of "fastboot flash rdl3.bin rdl3_unlocked.smg" then i think it restarted to only the moto logo was there and i typed fastboot devices it showed my phone so i took the cg file from derpunlock and typed a command like fastboot flash boot cg42_000somthing.smg it said ok finished... ???
sunny530 said:
Has anyone ever seen this before? I have reflashed stock recovery to the phone and before i could switch options in the boot menu i was stuck to only rsd or fastboot. I am on 2.3.5 I sent rdl3 to the phone it restarted in bootloader or fastboot just a moto logo i sent the fastboot oem unlock command, peices of derpunlock and also a system.img. now i can choose android recovery in my boot menu but system still wont load.
Click to expand...
Click to collapse
are you saying you're on 2.3.5? if you are, your bootloader is permanently locked. it won't do any good to try and unlock it, unless you don't mind bricking. otherwise i have never seen this error before.
if you are on 2.3.5 i'd recommend flashing the electrify 2.3.5 sbf method to hopefully unbrick and return to stock.
Thanx for the reply na7q but I am pretty sure when software says unrecoverable error you have just killed it. When you torpedo root doesnt that kill the xorg server? as soon as its dead BAM!!! your rooted lol i would really like it if some very knowledgeable people on this subject would take a look at this and if they all tell me to do the same thing then 2.3.5 electrify here i come, However, i am not concerned of getting my phone in working order if my phone remains dead for the next few days i dont mind as long is it contributes to this bootloader being unlocked.
sunny530 said:
Thanx for the reply na7q but I am pretty sure when software says unrecoverable error you have just killed it. When you torpedo root doesnt that kill the xorg server? as soon as its dead BAM!!! your rooted lol i would really like it if some very knowledgeable people on this subject would take a look at this and if they all tell me to do the same thing then 2.3.5 electrify here i come, However, i am not concerned of getting my phone in working order if my phone remains dead for the next few days i dont mind as long is it contributes to this bootloader being unlocked.
Click to expand...
Click to collapse
with 2.3.5 you aren't unlocking anything. can almost guarantee it! it's going to take a miracle! i'd say just restore it with the SBF if possible and continue on with life haha. i rooted like a year ago so i don't remember anything about it at this point haha. the only thing that was important was unlocking the bootloader! we need a breakthrough on that for these locked users. that miracle hasn't happened yet. or even gotten close.
Try flashing signed boot.img. This seems to me like failed to boot 2 in other words.
You can flash almost anything into the phone, the signature is checked after reboot, so "flashing ok" in fastboot is normal feedback, sometimes even if it's not ok (radio).
Also with recovery, you can choose whatever zip you want, but when you hit install, signature is checked.
Well you see i receive no failure to boot 1-4 i just get stuck at the moto dual core screen with nothing written at the top. Is it possible that i flashed the bootloader sucsessfully and did not flash the microboot? i didnt know the command to issue to flash microboot. The unrecoverable bootloader error seems interesting to me how would i find out what kernal i should/can flash and what would be the command would it be in fastboot? can i install a system.img via recovery or install bootstrap through fastboot or stock recovery?
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...