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...
Related
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'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?
Hey,
So I updated my Nexus 9 with today's OTA, after which I'm greeted with the dead android 'No command.'.
I've attempted to wipe the cache data and factory reset from the recovery menu, and factory reset from the power + volume down menu.
My boot-loader is locked as I've never felt the need of rooting or running custom roms - so the tablet is entirely stock.
I also attempted to run fastboot which is throwing errors due to the boot-loader being locked.
I tried to re-apply the patch using adb from the recovery menu, however after the patch is verified I'm receiving this error: system partition has unexpected contents
Is there anything I can do to fix this myself at this point?
I've contacted Google but haven't heard back from them yet.
Any help is greatly appreciated or guidance!
Kind Regards,
Since you already factory reset your device (and lost your data) the best way to recover is flashing the whole factory image.
Just unlock the bootloader and flash the latest factory image following the instructions from here:
https://developers.google.com/android/nexus/images
The problem is, I never enabled USB debugging so my bootloader is locked or am I missunderstanding this?
Cellzor said:
The problem is, I never enabled USB debugging so my bootloader is locked or am I missunderstanding this?
Click to expand...
Click to collapse
It's not USB debugging that is necessary in your case. It's the option to "enable OEM unlock".
PS: Two hints for future success on XDA: 1) don't post questions in the General Section. 2) Don't double post the same question.
I was rooted and tried to do a flash stock plus unroot with no wipe using the new LM48YI image on a n9 wifi with lmy48x using the wug toolkit and ran into the same issue yesterday. In my case, multiple restore to stock/reset did not help and the device hard bricked during a reset. The fact that this happens on stock unrooted devices is very very worrying to say the least.
add me to the list of completely factory N9's getting bricked from the OTA. All I can do is get into fastboot and any reboot will just sit at the spinning dots forever. Most fastboot commands just get denied since the device is locked. Thanks google. Looks like it is email to google time or just throw it away.
My wifes Nexus 9 is now in the same boat. From what I can tell, you cannot run the "fastboot oem unlock" command successfully unless you had previously checked the "allow oem unlock" button in Settings. When trying this I get this:
<bootloader> ability is 0
<bootloader> Permission denied for this command!
OKAY [ 0.031s]
finished. total time: 0.031s
I tried sideloading the OTA instead of flashing the factory image, but it got to 48% and then said this:
error: system partition has unexpected contents
Because the bootloader is locked, I can't flash, and sideloading the OTA seems to be a no go.
Does anyone have any suggestions as to what I could try next?
@Rigger007
Return it for repair/replacement. RMA.
Hi guys!
A little background. I am trying to unlock the bootloader, after seeing the root status: unknown, a second time after re-flashing back to stock rom. I could unlock the bootloader perfectly fine on the first try on firmware .251 but after updating to .260, the
Code:
fastboot -i 0x0fce oem unlock 0x<key>
command keeps failing. I was trying to flash a custom rom from FreeXperia, but after several attempts of not being able to send the system.img into the tablet, I decided to re-flash to stock using Flashtool, and had selected all the option for wipe and no exclude.
Which leads to my question: Does the
Code:
fastboot getvar all
retrieves anything at all? I also tried
Code:
fastboot getvar boot
fastboot getvar version-main
but also retrieves nothing.
This is the log:
Code:
C:\Users\Aotsubame\AppData\Local\Android\sdk\platform-tools>fastboot devices
CB5A27L24G fastboot
C:\Users\Aotsubame\AppData\Local\Android\sdk\platform-tools>fastboot getvar all
all:
finished. total time: 0.007s
C:\Users\Aotsubame\AppData\Local\Android\sdk\platform-tools>fastboot getvar version-main
version-main:
finished. total time: 0.006s
C:\Users\Aotsubame\AppData\Local\Android\sdk\platform-tools>fastboot getvar boot
boot:
finished. total time: 0.013s
C:\Users\Aotsubame\AppData\Local\Android\sdk\platform-tools>fastboot -i 0x0fce oem unlock 0x<key>
...
FAILED (remote: Command not allowed)
finished. total time: 0.014s
special flash command for the large partitions
flash system like outlined here:
http://developer.sonymobile.com/kno...ocked-xperia-devices/#build-aosp-lollipop-5-1
What do you expect from the getvar command?
DHGE said:
flash system like outlined here:
What do you expect from the getvar command?
Click to expand...
Click to collapse
Hi, thanks for the reply! I was trying to get back root and unlock bootloader after splendidly failing to successfully flash a custom rom to my Z4 tablet. I was searching around Google for the remote: command not allowed error, and actually found out that some of the users actually have output for the getvar all command, which was bootloader version information and other stuff. I should also point out that I have successfully unlocked the bootloader the first time but not the second time.
Another question: Will downgrading the firmware change the rooting status in the service menu?
Edit: Will re-flashing the stock rom lock the bootloader?
Going to try the link you posted! Will report back if there's any disaster that I've made.
you better search here on XDA and not on the web
SONY devices are a bit special in terms of partitions and bootloaders:
http://forum.xda-developers.com/crossdevice-dev/sony/noob-guide-to-sony-ericsson-xperia-t3209012
AFAIK bootloader stays unlocked whatever you flash after unlocking and only using Flashtool or SONY PC Companoin (the latter useless for unlocked devices) you should be on the safe side.
fastboot flash ... is a bit more dangerous but I would never flash anything were I have a hunch the developer is taking too many chances and were there is no README. And it really has to be for your specific device!
Sometimes I think people complaining here have flashed obscure phone ROMs to their tablet or Wifi ROM to their LTE device or any weird pre Lollipop root tricks (there are scams easiliy found via web search).
I just tried downloading the Flashtool from Sony's website. The Emma one.
However, the program says that my bootloader is locked for some odd reason. I'm inclined to think I am in a state where I can't unlock my bootloader any more though.
I also did enable My Xperia after I reflashed the stock rom during the initial setup, but immediately deactivated it. I wonder if this is causing it to have this error.
the fora for newer Xperia devices are plastered with MyXperia "accidents"
riveria said:
I also did enable My Xperia after I reflashed the stock rom during the initial setup, but immediately deactivated it. I wonder if this is causing it to have this error.
Click to expand...
Click to collapse
Emma is useless. Does not work on our Lollipop devices. Updates of Emma seem to be automatic but no improvement. Maybe they forgot to switch off their update bot.
You bricked your device.
From SONY (READ before you do risky things!!!):
After unlocking your device, you should not enable My Xperia (found in the settings menu under security on some devices running Android 5.0) as this might cause the device to malfunction.
Click to expand...
Click to collapse
source: http://developer.sonymobile.com/unlockbootloader/
DHGE said:
Emma is useless. Does not work on our Lollipop devices. Updates of Emma seem to be automatic but no improvement. Maybe they forgot to switch off their update bot.
You bricked your device.
From SONY (READ before you do risky things!!!):
Click to expand...
Click to collapse
Oh ok, so there's no chance of me unlocking the bootloader? The device still boots up normally though.
riveria said:
Oh ok, so there's no chance of me unlocking the bootloader?
Click to expand...
Click to collapse
I do not know.
I do not think so though - if you could unlock the MyXperia Software would be no protection at all. Thieves could just unlock the BL of the stolen device and lough at SONY.
The device still boots up normally though.
Click to expand...
Click to collapse
You are lucky then - there are reports where only a repair at SONY could revive the device:
http://fxpblog.co/2015/07/03/dont-destroy-your-unlocked-device.html
DHGE said:
I do not know.
I do not think so though - if you could unlock the MyXperia Software would be no protection at all. Thieves could just unlock the BL of the stolen device and lough at SONY.
You are lucky then - there are reports where only a repair at SONY could revive the device
Click to expand...
Click to collapse
Alright! Thanks for the help! I guess no more rooting for me then. I'll try reflashing the stock rom again and see what are the results.
Reflashing doesn't change the rooting status. So a reminder to all: Don't enable My Xperia.