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.....
Related
HI hope someone can help me with this, i have tried without success to unlock my bootloader, i have updated to hboot 1.02 but when i try to do the fastboot flash unlocktoken Unlock_code.bin it sits at 0percent and doesn't move and no errors, i've tried this with my goldcard in and out of the phone and with cyanogen and b08 roms, also for some reason i can't flash the stock rom so i can get the required update from htc(thinking that's y the unlock code won't go), i've tried getting numerous ruu's and i was getting signature verification fails every time, i tried with windows the exe and also exracted the rom.zip and still no luck, i prefer using linux and adb though and tried numerous ways to get this to work with no success, i've also tried signing a rom.zip and the phone just says no signature, also tried renaming to LEGEIMG.zip and update.zip and just can't flash stock rom, also made a new goldcard thinking the other was bad and did the htcdev for the unlock code with a goldcard and without, also tried the ruu.exe in windows with new said goldcard and i think the other was bad because i get a different error now for reason it can't update my rom(was using the rom i originally rooted with which has sense). it says wrong bootloader version when i try and update, anyone know what i can do, i'm running outta ideas, thanks in advance
I Unlocked my bootloader with HTCdev. You said you tried. What went wrong?
If you have updated your phone to one of the ruus HTC gives you ( execute the exe ), there shouldn't be any problem : the HTC guide is clear and easy. If you have successuffly unlocked the bootloader, now you have to flash the clockwork recovery.
when i go to fastboot it stays on copying at 0 percent with the unlock_code.bin....My phone has root access before i ran the hboot update and still does but i can't flash the new ruu, it won't allow me to, i tried running the htc ruu and it fails with can't update, bootloader version incorrect, i tried with the b-08 rom, i can't get back to stock
Have you tried flashing this? ----> http://forum.xda-developers.com/showthread.php?t=1497357
If you don't install one of the updates given by HTC, bootloader unlock won't work. If you have the same problems that I had ( my Legend also wasn't rooted ) the RUUs won't install, right? I flashed first this one and then one of the HTC RUUs and after this everything worked perfectly.
nope, i didn't try that one yet, but the thing is my legend was rooted before i tried flashing these htc ruus, i just want my bootloader unlocked, i had cyanogen on it then flashed a rooted one with sense (b08) thinking that would let me update but it didn't, so i'm downloading that one you pointed me to now, i'll try and flash it and let you know how it goes.
When i flash that rom i get a main version is older error when i rename it to LEGEIMG and flash it via fastboot, what can i do now?
I followed Blayo's guide http://forum.xda-developers.com/showpost.php?p=22613990&postcount=62 with my already rooted Legend. Try to follow exactly. You said using a gold card - don't think this is even necessary. At least I did not use one, and it is working perfectly.
After flashing the new bootloader, did you really unlock?
(last step of guide above: follow the instructions on HTCdev from Step 8 to unlock)
Wait, all the RUUs you have to flash before unlocking are HTC's executable files ( .exe ). You have updated your phone executing them, haven't you? After that I just rebooted my phone to fastboot and connected it. I found the unlock code, sent it to HTCdev, received an e-mail with the file to complete unlock and then unlocked. I never used anything like UPDATE.zip or LEGEIMG. I tried following the BlaYo's instructions but they didn't work for me. I just did what HTC said ( easyer and safer ).
hmmmmm
hello guys... pwde ba ko mag unlock ng bootloader my x8 stiker is 11w48?
astig_king24 said:
hello guys... pwde ba ko mag unlock ng bootloader my x8 stiker is 11w48?
Click to expand...
Click to collapse
keyboard error?!
i solved my problem, i sold the phone and bought another legend. LOL, no seriously though, i did sell it and got another but i tried everything and couldn't unlock bootloader, i tried the exe files from htc, tried extracting the zip files, tried fastboot and renaming to LEGEIMG, just couldn't get it unlocked, so i flashed the latest cyanogen 7.2 and sold the darn thing, now i got another and made 50$ in the process as i bought the new one 50$ cheaper and i'm going to go through the htc channels to unlock the bootloader but does anyone know if i'll be able to flash cm7 after i do that?
bootloader
I have a similar problem with my Legend i had already rooted my legend following this guide http://chrg.zxq.net/htc-legend-root.html. I decided to unlock the bootloader folowing the guide on HTC dev to the letter and it worked fine bootloader unlocked. Only prolem is after rooting the phone again and flashing cm7 the bootloader is now locked again. What to do any ideas id be very greatfull.
sam0056 said:
I have a similar problem with my Legend i had already rooted my legend following this guide http://chrg.zxq.net/htc-legend-root.html. I decided to unlock the bootloader folowing the guide on HTC dev to the letter and it worked fine bootloader unlocked. Only prolem is after rooting the phone again and flashing cm7 the bootloader is now locked again. What to do any ideas id be very greatfull.
Click to expand...
Click to collapse
What do you mean with 'rooting again'? Once you have unlocked bootloader, you are able to flash a recovery, and then CM, which is rooted. See http://forum.xda-developers.com/showthread.php?p=24102979 for latest Recovery and latest CM7.2 builds
Ok just to update i flashed the HTC dev bin file again and had restore cm7 backup and bootloader is unlocked once again.
got her goin good now, unlocked bootloader with htcdev, fastboot flashed cwm, then i was able to flash cm7.2 and gapps no problem at all, now if we could only s-off the legend???
dantheman1977 said:
... now if we could only s-off the legend???
Click to expand...
Click to collapse
For what reason? It's quite similar
Because it's still not totally unlocked
dantheman1977 said:
i solved my problem, i sold the phone and bought another legend. LOL, no seriously though, i did sell it and got another but i tried everything and couldn't unlock bootloader, i tried the exe files from htc, tried extracting the zip files, tried fastboot and renaming to LEGEIMG, just couldn't get it unlocked, so i flashed the latest cyanogen 7.2 and sold the darn thing, now i got another and made 50$ in the process as i bought the new one 50$ cheaper and i'm going to go through the htc channels to unlock the bootloader but does anyone know if i'll be able to flash cm7 after i do that?
Click to expand...
Click to collapse
After unlocking boot loader:
1. Use htcsupertoolv3 to root
2. Install rom manager and titanium backup
3. Run titanium backup. It will ask you to update su. accept (i'm not sure if this step is required, but this is how i done it)
4. Copy recovery-clockwork-5.0.2.0-legend to your Android folder created during bootloader unlock
5. With your phone on fastboot mode open terminal in your PC android folder and type:
fastboot flash recovery recovery-clockwork-5.0.2.0-legend.img
Your phone will go to recovery mode.
6. Reboot your phone in normal mode
7. From now on, each time you want to go into recovery, use rom manager
Done
dantheman1977 said:
Because it's still not totally unlocked
Click to expand...
Click to collapse
So for what I have understood from HTCdev, you can do everything similar to S-OFF, with one exception: you cannot unlock a SIM lock.
Oops... said:
So for what I have understood from HTCdev, you can do everything similar to S-OFF, with one exception: you cannot unlock a SIM lock.
Click to expand...
Click to collapse
True, you can't. I'm not sure if flashing a custom rom will unlock it, as my phone sim card was unlocked from very beginning. Probably not?
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...
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?
I'm trying to unlock the bootloader on my dna that's on 2.06 firmware. Please do not tell me to use moonshine, I have to unlock my bootloader first before trying. I've already had issues with it.
I unlocked my bootloader on earlier firmware (1.xx - I forget the exact version) so I have an old Unlock_code.bin from HTCDev. I already have SuperCID (all 1's), so I figured I didn't need to use jcase's newer method, which said it only worked on devices on 1.x anyway. I went through HTCDev anyway to make sure I could still unlock, but when I put in my device identifier token, I got error 160: MID not allowed.
As I said, I could just use the old Unlock_code.bin, but I want to do this the right way. Do I have to run jcase's exploit (even though it's only supposed to be for 1.x), or should I just use my old unlock code?
SOLVED
The answer is yes, you can use your old Unlock_code.bin, and you may have to. This will only work if you previously unlocked the bootloader and got SuperCID.
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.