Related
Hi
my problem
i have Evo 3D Hboot 1.49.0018 middle east
my Evo was unlock but i gave it HTC for repairing it stooped work suddenly
they changed Motherbord
any way
now im tryin again um trying to unloack it as before by HTCDEV method
when i reach step 12 it give me failed Msg
sending 'unlocktoken' (0 KB)...
OKAY [ 0.141s]
writing 'unlocktoken'...
FAILED (remote: unlock token check failed)
finished. total time: 0.141s
i read a lot but i could not solve my problem or find an answer on the same old thread
thanks alot
You used the same token as before? If you have then there you got the reason why it is not working.
You have an new motherboard so you should have an new unlock token to.
Sometimes the unlock process won't work. Just install the RUU if you are having issues, and then try to unlock it and you will be successful.
Here is the link for the RUU: http://www.multiupload.com/09NOXKCUN0
EDIT: Mult-upload is down. I fogot. lol. The name of the RUU is 2.08.651.2 Install that and then try unlocking again.
yes I know the new Mb mean I have a new pocket
I start unlocking from 1 step
Seven times from a different pcs
Same fail msg appear
DexterMorganNL said:
You used the same token as before? If you have then there you got the reason why it is not working.
You have an new motherboard so you should have an new unlock token to.
Click to expand...
Click to collapse
How I can get the last middle east RUU ?
Thanks
mh7 said:
yes I know the new Mb mean I have a new pocket
I start unlocking from 1 step
Seven times from a different pcs
Same fail msg appear
Click to expand...
Click to collapse
You are having issues because the motherboard changed by htc was preloaded with 2.17.651.5 and some of the phones preloaded with this SW number have issues.
i found a link for RUU_Shooter_U_HTC_ARA_1.24.415.6
same that i I'm using
i will flash and see if it solve the problem
i falshed RUU
and started unlocke steps from step 1
same msg :
"sending 'unlocktoken' (0 KB)...
OKAY [ 0.140s]
writing 'unlocktoken'...
FAILED (remote: unlock token check failed)
finished. total time: 0.150s"
i tried
RUU_Shooter_U_HTC_ARA_1.24.415.6
it give me same Hboot 1.49.0018
and
RUU_Shooter_U_HTC_ARA_1.24.415.2
with Hboot.1.49.0012
for sure im starting unlock from step 1
same Msg appearing
I'm guessing you mistakenly included an extra space at the end of the unlock token when you copied/pasted. It's a common error
Sent from my PG86100 using Tapatalk
greeg32 said:
I'm guessing you mistakenly included an extra space at the end of the unlock token when you copied/pasted. It's a common error
Sent from my PG86100 using Tapatalk
Click to expand...
Click to collapse
i checked that many time there is no space between
and HTC accept the code successfully !!
the problem that i did unlock before to my Evo before changing M.B
thanks to all who try to help
Is there any way to root my EVO without unlock
And sure not temporary
mh7 said:
Is there any way to root my EVO without unlock
And sure not temporary
Click to expand...
Click to collapse
there is a program ,developed by the people here at XDA ,called GingerBreak that does work for some phones and versions of gingerbread...read up on it before trying and use at your own risk
any new solution ?!!
you should have any problems with this. i did it too, and had no problems. is your device s-on or s-off?
stefanschroen said:
you should have any problems with this. i did it too, and had no problems. is your device s-on or s-off?
Click to expand...
Click to collapse
Sry for jumpin' in.. but did what?
stefanschroen said:
you should have any problems with this. i did it too, and had no problems. is your device s-on or s-off?
Click to expand...
Click to collapse
If I have s-off I won't open this topic: D
unlock failed
did you use the original unlock token that you downloaded the from the first time you unlocked it or did you download another unlock token
sure i start a new steps cause i have a new M.B
i think no way to use HTC unlock
and to change CID should start with unlock bootloder
i think only way to sell it and purchase a new one
So I know I'm a dumb ass but here's what happened:
HTC Rezound S-off
Amon Ra 3.15
Hboot 2.27
ViperRez 1.0.3
My phone was acting a little buggy and my friend kept telling me I should flash a firmware update so I flashed
this " PH98IMG-firmware.zip - 33.02 MB " from here: http://forum.xda-developers.com/showthread.php?t=1835811&highlight=ruu&nocache=1
I checked the MD5 when I dl'd to PC BUT not when I copied to sd card. When flashing, all steps were successful except for 2: MDM9K - FAIL-UZ & RADIO_V2 - FAIL-UZ
I rebooted and got stuck at the white HTC screen. Battery pop and I tried to flash again. This time almost everything returned -- FAIL-PU except for the two above which still said FAIL-UZ.
Adding insult to injury I tried flashing two more RUU's from android police, I have a screenshot attached of one of my failed attempts.
ADB Devices doesn't recognize my phone but FASTBOOT devices returns a serial number. Boot loader also changes from " fastboot" to "fastboot-usb" when I plug into a PC but my PC doesn't see my phone.
I think it was a corrupted RUU because I decided to check the MD5 of a RUU on my sd card after the damage was done and it was bad. I then copied the same file over to my sd card a bunch of times, checking each MD5 and more than half the time they were bad.
I appreciate any suggestions anyone might have.
Sorry, thought I was in the Q & A section. (I already said I was a dumb ass)
Try this one http://forum.xda-developers.com/showthread.php?t=1835039
Sent from my ADR6425LVW using xda app-developers app
Thanks Squirrel...tried that one. That's actually the RUU that I ran for the screenshot. I think the problem has to do with updating my partition in the internal memory.
Squirrel1620 said:
Try this one http://forum.xda-developers.com/showthread.php?t=1835039
Sent from my ADR6425LVW using xda app-developers app
Click to expand...
Click to collapse
I tried flashing in fastboot...heres what I got:
c:\mini-adb_vigor>fastboot devices
HT19RS207848 fastboot
c:\mini-adb_vigor> fastboot -w update rezound_AndroidPolice_4.03.605.2_PH98IMG.z
ip
Whoops: didn't find expected signature
read_central_directory_entry failed
²ετ╪»╛g[ÑÖ╥yïS¬☼û÷A☼├║f:e{ûhh%►ÉÉW└|'╢σG╣S╙τφN}┐{S
c:\mini-adb_vigor>
Yikes!!
Try this in fastboot. Make sure you have the rezound_AndroidPolice_4.03.605.2_PH98IMG.zip in the same directory with fastboot.exe Make sure it is way over 33MB.
fastboot oem rebootRUU
fastboot flash zip rezound_AndroidPolice_4.03.605.2_PH98IMG.zip
Here we go....
c:\mini-adb_vigor>fastboot devices
HT19RS207848 fastboot
c:\mini-adb_vigor>fastboot oem rebootRUU
... INFO[SD_HW_ERR] read data fail in CMD18
INFO[SD_HW_ERR] SD: Read data fail..
INFO[ERR] partition_read_emmc(732): error 1
INFOStart Verify: 0
INFO[SD_HW_ERR] read data fail in CMD18
INFO[SD_HW_ERR] SD: Read data fail..
INFO[ERR] partition_read_emmc(732): error 1
INFOStart Verify: 0
INFOerase sector 130560 ~ 131071 (512)
INFOemmc_erase(1853): sd_write_sector failed!
OKAY [ 0.082s]
finished. total time: 0.083s
c:\mini-adb_vigor>
Flyhalf205 said:
Try this in fastboot. Make sure you have the rezound_AndroidPolice_4.03.605.2_PH98IMG.zip in the same directory with fastboot.exe Make sure it is way over 33MB.
fastboot oem rebootRUU
fastboot flash zip rezound_AndroidPolice_4.03.605.2_PH98IMG.zip
Click to expand...
Click to collapse
jksell07 said:
Here we go....
c:\mini-adb_vigor>fastboot devices
HT19RS207848 fastboot
c:\mini-adb_vigor>fastboot oem rebootRUU
... INFO[SD_HW_ERR] read data fail in CMD18
INFO[SD_HW_ERR] SD: Read data fail..
INFO[ERR] partition_read_emmc(732): error 1
INFOStart Verify: 0
INFO[SD_HW_ERR] read data fail in CMD18
INFO[SD_HW_ERR] SD: Read data fail..
INFO[ERR] partition_read_emmc(732): error 1
INFOStart Verify: 0
INFOerase sector 130560 ~ 131071 (512)
INFOemmc_erase(1853): sd_write_sector failed!
OKAY [ 0.082s]
finished. total time: 0.083s
c:\mini-adb_vigor>
Click to expand...
Click to collapse
Stinks to say but it looks like if you have bad blocks I don't think it can be fixed.
You can try unlocking and if it will unlock. Download a recovery. CWM. AmonRA. or TWRP. A fastboot command would be fastboot boot recovery.img or fastboot flash recovery recovery.img. Use the first command if you can't flash the recovery. If you can get a recovery to load. Flash a rom
Just an idea here. I would go here http://shipped-roms.com/index.php?category=android&model=Vigor and down load one of the "EXE" RUU and try it. These are windows executables, so just double click on the file after downloading. Start with a ICS first and if that dont work try the GB
mclass55 said:
Just an idea here. I would go here http://shipped-roms.com/index.php?category=android&model=Vigor and down load one of the "EXE" RUU and try it. These are windows executables, so just double click on the file after downloading. Start with a ICS first and if that dont work try the GB
Click to expand...
Click to collapse
The .exe basically does the same thing as fastboot oem rebootRUU. Just does it for you in a GUI.
Wish I could help here but curious about something, if he some how flashed a bad dl of an ruu, which contains hboot, and radio's etc..I know that if you have a bad dl of an hboot, or radio and you flash it it would brick your phone. could it be possible he bricked his phone due to this same theory? Except by running an ruu, or could that even be a possibility when updating via ruu? Just my 2cent and ??
Sent from my ADR6425LVW using xda app-developers app
Maybe he can try flashing just the hboot then trying the ruu again
Sent from my ADR6425LVW using xda app-developers app
Squirrel1620 said:
Maybe he can try flashing just the hboot then trying the ruu again
Sent from my ADR6425LVW using xda app-developers app
Click to expand...
Click to collapse
Agreed, he is s-off.. you can try doing everything seperately, make sure you check your md5s.. start with your hboot..
Sent from my ADR6425LVW using xda app-developers app
I just got home and my internet connection's out. I'm tethered to my OG droid right now and it is slooooooowww. When it rains, it pours.
" Stinks to say but it looks like if you have bad blocks I don't think it can be fixed.
You can try unlocking and if it will unlock. " Thanks Flyhalf205, I already tried unlocking and that was a no go.
I tried messing around in a linux terminal:
" Detect the device using the script provided. Type this in the terminal: ./brickdetect.sh "
(I got this from here - http://forum.xda-developers.com/showthread.php?t=1833530&page=6)
It said something like permission denied.
I'll try flashing an hboot...I had thought about that but since its the only thing working on my phone I was a little hesitant. First I have to get my internet back up and running. I'll check back later.
Everyones help is much appreciated.
jksell07 said:
I just got home and my internet connection's out. I'm tethered to my OG droid right now and it is slooooooowww. When it rains, it pours.
" Stinks to say but it looks like if you have bad blocks I don't think it can be fixed.
You can try unlocking and if it will unlock. " Thanks Flyhalf205, I already tried unlocking and that was a no go.
I tried messing around in a linux terminal:
" Detect the device using the script provided. Type this in the terminal: ./brickdetect.sh "
(I got this from here - http://forum.xda-developers.com/showthread.php?t=1833530&page=6)
It said something like permission denied.
I'll try flashing an hboot...I had thought about that but since its the only thing working on my phone I was a little hesitant. First I have to get my internet back up and running. I'll check back later.
Everyones help is much appreciated.
Click to expand...
Click to collapse
Can't wait to hear if it worked. But as famouscollin said, check check and triple check that MD5. A bad hboot = permanent brick
Sent from my ADR6425LVW using xda app-developers app
Here are some confirmed working hboots, in case you were unsure of where to get them or which to use. They are based on the latest release, but have fastboot enabled without HTCDev unlock, and have the "LOCKED" at the top replaced with various other words.
Internet's back up but I won't have a chance to play with my phone until Tuesday night, so I'll post again when I have something to report. :good:
Like to hear how it went for you
mclass55 said:
Like to hear how it went for you
Click to expand...
Click to collapse
Not good. Nothing will flash. The only thing I have left to try is some fastboot erase commands. That might be the nail in the coffin though if I lose hboot.
Heres something else I tried...extracted the img from a RUU:
c:\mini-adb_vigor>fastboot flash mdm9k mdm9k.img
sending 'mdm9k' (23389 KB)... OKAY [ 3.259s]
writing 'mdm9k'... FAILED (remote: not allowed)
finished. total time: 3.575s
Flyhalf205 said:
Stinks to say but it looks like if you have bad blocks
Click to expand...
Click to collapse
If your'e still around, when you say bad blocks, is that something physically wrong like fried or just that the blocks are not accessible? Even if my phone is toast, I'm still curious as to what exactly happened.
I've been rooting phones for a few years now and no matter how bad I messed up my phone, I've always been able to bring it back from the brink. I was starting to think that bricking your phone wasn't really possible. It's like your dog dying and learning about death for the first time.
That's weird, I've only seen the remote not allowed when the bootloader is locked and you are s on
Can you try and unlock even though you are s off?
Sent from my ADR6425LVW using xda app-developers app
jksell07 said:
If your'e still around, when you say bad blocks, is that something physically wrong like fried or just that the blocks are not accessible? Even if my phone is toast, I'm still curious as to what exactly happened.
Click to expand...
Click to collapse
A bad HBOOT will cause a bad block. I am not sure how I can explain it. But the original MD5 did not match the one you downloaded and so it was a bad flash but this time a bad flash that can't be undone.
I know this sounds crazy. But trying doing the wire trick again and if asked to flash HBOOT. Do it!
Edit dfownloads removed as the host started serving malware.
I dont have these files anymore, sorry, please dont ask for them
For other HTC devices supported by FacePalm, please see this thread: http://forum.xda-developers.com/showthread.php?t=2155069
Welcome to Facepalm S-Off for modern HTC phones.
Credits and terms:
Exploit by beaups, full guide, testing, and concept by jcase and beaups. Thanks to dsb9938 and dr_drache for support and testing. Thanks also to all of the regulars at teamandirc. Additional thanks to indirect for Evo LTE testing.
Both beaups and jcase will collect the applicable active bounties. Further donations are greatly appreciated and can be sent to:
beaups - [email protected] - http://forum.xda-developers.com/donatetome.php?u=711482
jcase - [email protected] - http://forum.xda-developers.com/donatetome.php?u=2376614
dsb9938 - [email protected] - http://forum.xda-developers.com/donatetome.php?u=2963256
dr_drache - [email protected] - https://www.paypal.com/cgi-bin/webscr?cmd=_s-xclick&hosted_button_id=6LRSY8MT8P3A6
You can also come by irc for support or just to say thanks: #FacePalm http://chat.andirc.net:8080/?channels=facepalm
While this process shouldn’t be too risky, bricks can happen. None of us will be accountable. If you are worried, don’t do it.
This is a pretty simple method, however, you will need to have a working adb and fastboot environment. This method will work on any operating system that supports adb and fastboot. You should understand how to use a terminal window in your O/S. If you don’t understand adb and fastboot, you probably don’t need S-off.
Lastly, the work herein should not be stolen, repackaged, one clicked, bat’d, etc. soffbin3 is not GPL and may not be reused, integrated into other work, reposted, or redistributed without our permission.
For this to work, you must be rooted and have superCID (unlock/custom recovery is optional), see the threads below for help and information regarding obtaining superCID, unlock, root, etc. Note these threads are provided for convenience only. Please look for support for them in each respective thread if you need it, do NOT clutter this thread with support requests regarding obtaining superCID and/or root! If you try this process without superCID, it will not work, and you may have issues!:
SuperCID for HTC Evo 4G LTE:
Code:
adb shell
su
echo -ne "22222222" | dd of=/dev/block/mmcblk0p5 bs=1 seek=20
1)
Code:
adb reboot bootloader
2)
Code:
fastboot oem rebootRUU
(wait for black HTC Screen)
3)
Code:
fastboot flash zip PJ7510000-EvoLTE.zip
After a while, You should see the following error “FAILED (remote: 92 supercid! please flush image again immediately)”
7) Immediately issue the following command:
Code:
fastboot boot EvoLTE-rescue.img
(this is fastboot boot, NOT fastboot flash!)
8) Allow device to boot (may not fully boot on some custom roms)
Code:
adb reboot bootloader
9) You should see what you are looking for!
If you need help or just care to say thanks, join us on IRC: #FacePalm http://chat.andirc.net:8080/?channels=facepalm
Enjoy.
Took me all of 2 minutes to get s-off.
Extra info: This works on 3.16 firmware and subsequently 3.15 as well.
Indirect said:
Took me all of 2 minutes to get s-off.
Extra info: This works on 3.16 firmware and subsequently 3.15 as well.
Click to expand...
Click to collapse
Probably worked on 3.16 for you as you already had supercid, I'm guessing the recent 3.16 update prevents changing the CID.
I dont think so because we've never used CID on this phone before. Only way to find out is to test.
Thanks for bringing this to the evo lte! I have windows 8 so this is gonna make it much easier compared to dirtyracun, thanks!
Thread cleaned. Going forward let's see about keeping it respectful in here.
You guys are freaking awesome thanks to all involved
Sent from my PoS MoPho
This is super easy! You guys rock. Thanks 4 this
Sorry for the stupid question, but what is supercid.?
Sent from my EVO using Tapatalk 2
Chocorico said:
Sorry for the stupid question, but what is supercid.?
Sent from my EVO using Tapatalk 2
Click to expand...
Click to collapse
Pretty sure it's that first 3 lines of code - makes your phone believe it has older firmware so you can flash older RUUs/updates. Swear there used to be a thread for it around here somewhere.
Help! I'm bricked.
C:\android-sdk-windows\platform-tools>fastboot devices
HT25KS405806 fastboot
C:\android-sdk-windows\platform-tools>adb reboot bootloader
C:\android-sdk-windows\platform-tools>fastboot oem rebootRUU
...
(bootloader) Start Verify: 3
OKAY [ 0.059s]
finished. total time: 0.062s
C:\android-sdk-windows\platform-tools>fastboot flash zip PJ7510000-EvoLTE.zip
sending 'zip' (35863 KB)...
OKAY [ 2.435s]
writing 'zip'...
(bootloader) adopting the signature contained in this image...
FAILED (remote: 92 supercid! please flush image again immediately)
finished. total time: 3.450s
C:\android-sdk-windows\platform-tools>fastboot boot EvoLTE-rescue.img
downloading 'boot.img'...
OKAY [ 0.853s]
booting...
OKAY [ 0.005s]
finished. total time: 0.862s
Then my phone never booted back up.
Hold power for 40 seconds, nothing in that should be causing bricks.
EDIT:
Apparently you were not bricked, we can only support stock roms, can't control how it behaves on AOSP, given it should still work, but it might not until you do a reboot. Please next time confirm that you are bricked before posting that you are.
[23:24:30] <BB15> I'm actually not bricked. I got it to boot back up and I'm s-off, but now I get prompted to activate my phone
BB15 said:
Help! I'm bricked.
C:\android-sdk-windows\platform-tools>fastboot devices
HT25KS405806 fastboot
C:\android-sdk-windows\platform-tools>adb reboot bootloader
C:\android-sdk-windows\platform-tools>fastboot oem rebootRUU
...
(bootloader) Start Verify: 3
OKAY [ 0.059s]
finished. total time: 0.062s
C:\android-sdk-windows\platform-tools>fastboot flash zip PJ7510000-EvoLTE.zip
sending 'zip' (35863 KB)...
OKAY [ 2.435s]
writing 'zip'...
(bootloader) adopting the signature contained in this image...
FAILED (remote: 92 supercid! please flush image again immediately)
finished. total time: 3.450s
C:\android-sdk-windows\platform-tools>fastboot boot EvoLTE-rescue.img
downloading 'boot.img'...
OKAY [ 0.853s]
booting...
OKAY [ 0.005s]
finished. total time: 0.862s
Then my phone never booted back up.
Click to expand...
Click to collapse
jcase said:
Hold power for 40 seconds, nothing in that should be causing bricks.
EDIT:
Apparently you were not bricked, we can only support stock roms, can't control how it behaves on AOSP, given it should still work, but it might not until you do a reboot. Please next time confirm that you are bricked before posting that you are.
[23:24:30] I'm actually not bricked. I got it to boot back up and I'm s-off, but now I get prompted to activate my phone
Click to expand...
Click to collapse
Yeah, I wasn't bricked. After waiting for some time for my phone to reboot after running FacePalm I unplugged the USB and held the power button and it booted right up. Rebooted the bootloader and verified that I was s-off. Then I ran into the activation problem. Just flashed MeanBean and ran through the activation, now all is good. Your work on this is much appreciated.
Thankkssssss S-off already
Chocorico said:
Sorry for the stupid question, but what is supercid.?
Sent from my EVO using Tapatalk 2
Click to expand...
Click to collapse
mildlydisturbed said:
Pretty sure it's that first 3 lines of code - makes your phone believe it has older firmware so you can flash older RUUs/updates. Swear there used to be a thread for it around here somewhere.
Click to expand...
Click to collapse
here you go:
[SUPERCID] SuperCID For EVO LTE(Ruu to older firmware(not hboots))
So for clarity, the superCID commands are run from the phone while booted? or in bootloader? It looks from the way its written thats its meant to be done while the device is booted
Edit:
Thanks OCN
Finally have s-off!!!!
Thx to Facepalm S-Off I now have s-off. Finally,after a long year and a half of trying to get s-off.....
I must have been doing a few things wrong this whole time or Facepalm S-Off has done it right...
Rxpert said:
So for clarity, the superCID commands are run from the phone while booted? or in bootloader? It looks from the way its written thats its meant to be done while the device is booted
Edit:
Thanks OCN
Click to expand...
Click to collapse
I ran it while booted. No issues.
Sent from my EVO using Tapatalk 2
Fantastic job.
Already S off but props given.
Very nice.
Wow, this was incredibly easy. Soff in less than 2 minutes. I just followed the directions and flashed stock rom to be safe. $$ coming to you guys on payday!!
Hey Guys, I've got a DNA that has to go back to VZW with hardware issues, i have the bootloader locked, but I am still displaying S-OFF and CID - 2222222 ... is there any way to change that? do they even check when I mail it back to them ?? any help is VERY APPRECIATED. thank you !
Just run this command in fastboot.
fastboot oem writesecureflag 3
It will make you s on and your bootloader won't display your cid anymore.
Sent from my HTC6435LVW using xda app-developers app
Bigandrewgold said:
Just run this command in fastboot.
fastboot oem writesecureflag 3
It will make you s on and your bootloader won't display your cid anymore.
Sent from my HTC6435LVW using xda app-developers app
Click to expand...
Click to collapse
That gem is saved for future use. Tyvm bro
Sent from my HTC6435LVW using xda premium
Bigandrewgold said:
Just run this command in fastboot.
fastboot oem writesecureflag 3
It will make you s on and your bootloader won't display your cid anymore.
Sent from my HTC6435LVW using xda app-developers app
Click to expand...
Click to collapse
tried this but kept getting partition errors:
C:\adb>fastboot oem writesecureflag 3
...
(bootloader) partition hboot signature error
(bootloader) writesecureflag: partitions siganture failed
OKAY [ 0.933s]
finished. total time: 0.935s
I sent my first DNA in when it said s-off and cid showing 222222...had no issues with warranty. At least not that I know of. Haven't been charged anything extra etc.
Sent from my HTC6435LVW using xda app-developers app
regulator207 said:
tried this but kept getting partition errors:
C:\adb>fastboot oem writesecureflag 3
...
(bootloader) partition hboot signature error
(bootloader) writesecureflag: partitions siganture failed
OKAY [ 0.933s]
finished. total time: 0.935s
Click to expand...
Click to collapse
Run a ruu then try again.
Sent from my HTC6435LVW using xda app-developers app
Make sure you guys aren't doing this with the Eng hboot.
I recommend scottys threads in the DNA Android Development section, the last few pages of both threads are really useful.
Edit here's one http://forum.xda-developers.com/showthread.php?p=38325198
Sent from my HTC6435LVW using Tapatalk 2
THANK YOU!
this worked flawlessly, I started to panic when I was told that software modification including unlocked bootloader could result in a 299 charge to me. My VZW phone service rep was a total tool.. This is my third DNA that has issues with the 'no sim' error and terrible connectivity. I'm giving it one more go, then demanding something totally different. I LOVE the phone, just hat the errors
Hi all,
I just tried to unlock the bootloader of my Desire 610 through HTCDev but it does not work for me.
I type "fastboot flash unlocktoken Unlock_code.bin" and confirm with volume up + power button that I want to unlock.
E:\fastboot>fastboot flash unlocktoken Unlock_code.bin
sending 'unlocktoken' (0 KB)...
OKAY [ 0.108s]
writing 'unlocktoken'...
(bootloader) unlock token check successfully
OKAY [ 0.004s]
finished. total time: 0.113s
The phone restarts, does a hard reset but when I go to bootloader to check, it still says "Locked".
Weird because I do not get any error message. The entire process (10 steps) goes straight forward.
It just won't unlock no matter how many times I try.
Does anyone else have the same issue with this device or any other device?
I'm on :
A3_UL PVT SHIP S-ON
HBOOT : 3.18.0.0000
Radio : 1.101.1102.15.31
OpenDSP-v27.2.2.00546.0311
OS-1.18.401.4
Thanks
Am I the only one to have such an issue?
Dragon99OG said:
Am I the only one to have such an issue?
Click to expand...
Click to collapse
You need to be in the same directory as the Unlock_bin. You can tell from the amount of kbs it's trying to transfer that it's an empty bin.
Redownload the bin, and cd to the same directory.
AdriVelazquez said:
You need to be in the same directory as the Unlock_bin. You can tell from the amount of kbs it's trying to transfer that it's an empty bin.
Redownload the bin, and cd to the same directory.
Click to expand...
Click to collapse
my unlock bin is 0.25 kb ,but the same not unlocked ,i tried 4 time no luck
I just got this phone but am curious about this. How/why does the m8 unlock token work?
Sent from my HTC Desire 610 using XDA Premium 4 mobile app
i tryed to pop up "unlock bootloader" menu and it works with .bin but i dont have time yet to do backup of my current data so i could test if it realy works(since you lose all data when you unlock bootloader)..
my device is @ 1.18.401 software number and i recieved 1.31.401 update at start of this week because htc rolled out updates for m8 too..
dont want to update yet cuz i want to try root and flash twrp and try to make image of 1.18 so i could share it here. then do the same with 1.31..
i got some expirience of flashing mine old xperia x8 and some more htc models from friends..
if anyone got some tips what is best way to get original image of htc's 4.4.2 kitkat just PM me. i need little help..
best regards from Croatia
We have a twrp build that works also?
Sent from my HTC Desire 610 using XDA Premium 4 mobile app
I was able to unlock my Bootloader and I will make a thread about it soon.
Sent from my HTC Desire 610 using Tapatalk
Eagerly awaiting your experience.
Hi.
So, somebody unlocked it?
P.S what model are u choose on HTCdev, htc one or other models?
Cheers.
He advised me he used the " Desire *" method, however the star indicates that it flashes the bootloader from the original htc desire to your device. Until we get confirmation that nothing is broken and it actually works as intended, I cannot yet recommend this method. If you're in dire need for some reason, feel free to try it, but don't hold them liable if something goes wrong. I'm in contact with htc dev team right now awaiting a response on the proper way to unlock. If I get no response, we'll try this method perhaps.
Yes, I managed to unlock it with HTCDev. I used HTC Desire* as device.
Sent from my HTC Desire 610 using Tapatalk
So, now we can push superuser and install cwm or twrp trough the adb using for example, strawmetal guide, right?
Cheers.
If you wanna try that method, I suppose. We don't have an official method for any of that yet, nor do we have a recovery build to flash or a way to flash superuser. Nor do we have a way to elevate adb to root to allow that installation yet.
So in essence, no. But if you're willing to risk your device also, try the unlock method Nixing used lol.
Confirmed
Yeup using the HTC Desire* has done the trick after hours of searching last night I decided to use the HTCdev way and it worked 1st time no problems !!!!!!! next up Root...:laugh:
Good deal. I'd still avoid that though, and use the "all other supported devices" instead. The star means it loads a different bootloader. The desire and desire 610 are not the same device, and that could be very bad. The all other supported devices option does not load a new bootloader. Unless perhaps they go by the device unlock code you provide and it can tell you don't have a desire.
Fair enough...I have successfully rooted my device too.
Sent from my HTC Desire 610 using XDA Free mobile app
Excellent! we're moving on up lol
i have a same problem!
i try many way of htcdev but nothing happened.
phone bootloader is still locked!
plz help me if someone fix this problem
thanks in advanced.
I´m having no luck
tried both
Desire * and
"all other supported devices"
Code:
fastboot flash unlocktoken Unlock_code.bin
< waiting for device >
sending 'unlocktoken' (0 KB)...
OKAY [ 0.138s]
writing 'unlocktoken'...
(bootloader) unlock token check successfully
OKAY [ 0.010s]
finished. total time: 0.148s
Still says *** LOCKED ***