ok so writesecureflag brings back
~/android/sdk/platform-tools$ fastboot oem writesecureflag 0
...
(bootloader) This project does not support SD card
OKAY [ 0.000s]
finished. total time: 0.000s
now would it be possible to trick the device into thinking sdcard and let it load off it self?
No, because the bootloader won't just allow you to change the s flag. The bootloader doesn't even have access to change it if it wanted to.
CastleBravo said:
No, because the bootloader won't just allow you to change the s flag. The bootloader doesn't even have access to change it if it wanted to.
Click to expand...
Click to collapse
well what allows to writesecureflag?i know 0 is unlock and 3 is oem lock . i am working very hard on figuring this out although no one will tell me anything about ways others have done it. though it is normally a file from oem placed on sdcard and flashed to radio or bootloader?but as far as i can tell if writescure will not work ever then the exploit has to be either flashed with ruu somehow or through usb
also brute force would take forever to crack a 256byte data encyption key wouldnt it?
Related
Hello
I tried to unlock my EVO bootloader but allways failed
sending 'unlocktoken' (0 KB)...
OKAY [ 0.141s]
writing 'unlocktoken'...
FAILED (remote: unlock token check failed)
finished. total time: 0.141s
I think i need to flash with a RUu ,tried different RUU with Goldcard but its impossible ,. SIGNARURE ERROR. HARD RESETED , SAME
ANY HELP ,
MY DEVICE IS 10.55.9020.00U_10.13.9020.29_M BUILD 1.22.707.3
SN HT18BV204792
i would suggest you try the unlocking method on another computer. make sure u have installed all the right drivers or just install htc sync
Are you a cdma or gsm phone ? You need the latest ruu for your phone make sure you get the right one. If your gsm grab latest ruu ....
Make sure you run the right one otherwise you can brick something.....
This will get you working again once done reapply the unlock code bin...
Though people comment about the ruu first of all - my phone failed to unlock the first time, when I copy and pasted the unlock token.
The second time, I consciously added a column while copying the token - and all of a sudden, it worked. In otherwords - I selected a larger area than what was visible in the token.
I don't know if it was coincidence or not - but it worked when I tried that, so I think it's worth a shot.
Tried more 2 pc.
its a GSM ASIA WWE .
I flashed the latest RUU 1.22.707.3
Retried again ,same ;problem
Any way of flashing another RUU ,Goldcard doesnt work .
I don't know if the same applys for gsm phones....
But on HTC DEV you need to have the lates java JDK installed among ADB and the latest HTC sync Drivers.....
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...
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.
I need to do a warranty exchange and my bootloader is unlocked, how can i relock it?
How can i relock it without using a USB?
Cannot relock without USB. You would need to run
fastboot oem lock
Sent from my LG-H901 using Tapatalk
Did you end up successfully locking it? Does it still display the 'unlocked' message on the logo boot screen?
-LBT- said:
Did you end up successfully locking it? Does it still display the 'unlocked' message on the logo boot screen?
Click to expand...
Click to collapse
Necro to say: YES, you can run "fastboot oem lock" to RELOCK the bootloader. "fastboot getvar unlocked" returns "unlocked: no".
Just tried it on my (two hour old) phone here.
Code:
C:\Assorted Programs\LGV10 Toolkit>fastboot getvar unlocked
unlocked: no
finished. total time: 0.007s
C:\Assorted Programs\LGV10 Toolkit>fastboot oem unlock
...
OKAY [ 3.374s]
finished. total time: 3.374s
C:\Assorted Programs\LGV10 Toolkit>fastboot getvar unlocked
unlocked: yes
finished. total time: 0.008s
C:\Assorted Programs\LGV10 Toolkit>fastboot oem lock
...
OKAY [ 1.764s]
finished. total time: 1.765s
C:\Assorted Programs\LGV10 Toolkit>fastboot getvar unlocked
unlocked: no
finished. total time: 0.005s
hi guys
am not able to boot into bootloader to unlock it
I tried
adb reboot bootloader
and
adb reboot boot-loader
it's just making a restart
even I tired the manual way by pwr + - volume but didn't work
my model is LG-H960
any ideas!!
I'm going to be upgrading real soon and I'm stuck between the v10 and note 5. I must have root
Sent from my Nexus 6 using Tapatalk
How did you unlock the bootloader ?
melorib said:
How did you unlock the bootloader ?
Click to expand...
Click to collapse
It will factory reset your device so make sure you are sure that you actually want to do it
reboot to bootloader then use the following:
Code:
fastboot oem lock
Sent from my S7 Edge using XDA Labs
KAsp3rd said:
It will factory reset your device so make sure you are sure that you actually want to do it
reboot to bootloader then use the following:
Code:
fastboot oem lock
Sent from my S7 Edge using XDA Labs
Click to expand...
Click to collapse
Thanks, I will do it when/if I move to marshmallow
melorib said:
Thanks, I will do it when/if I move to marshmallow
Click to expand...
Click to collapse
Hi, Have you been able to Relcok it successfully? Does bootloader unlock still appears on your screen or it is gone?
Waxim1 said:
Hi, Have you been able to Relcok it successfully? Does bootloader unlock still appears on your screen or it is gone?
Click to expand...
Click to collapse
I dont think my phone bootloader was ever unlocked, at least I never noticed such message, but since I rooted in lolipop I get this funny screen everytime I reboot, even after upgrading to marshmallow
KAsp3rd said:
It will factory reset your device so make sure you are sure that you actually want to do it
reboot to bootloader then use the following:
Code:
fastboot oem lock
Sent from my S7 Edge using XDA Labs
Click to expand...
Click to collapse
Thanks, it worked
if we relock the bootloader after doing root and debloat the stock rom, when they factory reset everything the root stay or just be gone after do the relock? are we able to unlock it again if we need TWRP?
other thing, the "cant check software for corruption" message will still appear or be gone when re-locked?
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.