Related
Hi,
I am unable to unlock my HTC EVO 3D.
It's currently running : RUU_Shooter_U_hTC_Asia_WWE_1.22.707.2_Radio_10.55.9020.00_10.13.9020.29_M_release_207422_signed
I've gone to the htcdev site, submitted the identifier token; received the unlock_code.bin file; followed their instruction and got this :
C:\Android>fastboot flash unlocktoken Unlock_code.bin
sending 'unlocktoken' (0 KB)...
OKAY [ 0.143s]
writing 'unlocktoken'...
FAILED (remote: unlock token check failed)
finished. total time: 0.150s
-------------------------------------------------------------------------
I've also tried using a GoldCard thinking I could load another region's RUU but didn't work either
I've tried almost everything and so I am turning to the xda gurus. Please help
mainboardnya prnah diganti?
Not sure if the motherboard has been changed. (Tak pasti jika motherboardnya pernah diganti)
Sent from my HTC EVO 3D X515m using XDA
mine cant be unlock again after htc replaced the board. many user had this problem too.
I am facing the same problem. Any other solution?
You can try to run the RUU first and then try to unlock it again. It solves most problems
I'm having the same problem HBOOT versiyon 1.49.0018 Do not have a solution ?
Did you managed to unlock it ? Mine also came back from HTC repair (after bricking it ), and I cannot unlock it for the same reason : 'unlock token check failed'
Why are u trying it the way use rev.io
Sent from my HTC EVO 3D X515m using XDA Premium App
It's so easy to get s-off now that you should just do that really. It also allows for more reliable flashing of ICS ROMs than s-on.
Sent from my PG86100 using Tapatalk 2
geordie 34 said:
Why are u trying it the way use rev.io
Sent from my HTC EVO 3D X515m using XDA Premium App
Click to expand...
Click to collapse
Thank (button used) you. It worked fine
kitarolivier said:
Thank (button used) you. It worked fine
Click to expand...
Click to collapse
u got the supported hboot by rev ??? mine was 1.49.00011
I am having the same problem, i have my board replaced because of Frequent BOOT LOOPS
after that i am not able to unlock the boot loader. Even i tried to install the Latest Asian RUU in my phone it gave me error. 131 Customer Code do not match
Then i went to fastboot and just gave command
for changing the cid, and it worked! without evan unlocking the bootloader
before my cid was 038, now in CID Getter it shows 001, So hopefully that worked
and after that again i tried to run the RUU but still the same error!
So dont know now what to do ?
skchokshi said:
I am having the same problem, i have my board replaced because of Frequent BOOT LOOPS
after that i am not able to unlock the boot loader. Even i tried to install the Latest Asian RUU in my phone it gave me error. 131 Customer Code do not match
Then i went to fastboot and just gave command
for changing the cid, and it worked! without evan unlocking the bootloader
before my cid was 038, now in CID Getter it shows 001, So hopefully that worked
and after that again i tried to run the RUU but still the same error!
So dont know now what to do ?
Click to expand...
Click to collapse
which tutorial you used for changing the cid mate? and where i can find the latest asian ruu? tks
klebengan said:
which tutorial you used for changing the cid mate? and where i can find the latest asian ruu? tks
Click to expand...
Click to collapse
I used this guide to crack the bootloader
http://forum.xda-developers.com/showthread.php?t=1471246
In this guide it says first we have have to bootloader but, just skip that part.
Temp Root your phone with automated scripts (HTC Super Tool V3)
And then you do as the guide says. It is working
My bootloader was locked too. After downgrading your phone, just unlock the bootloader with Revolutionary Method.
Then install 4EXT Recovery. And then you can install custom Roms.
Solution for your problem?
kitarolivier said:
Did you managed to unlock it ? Mine also came back from HTC repair (after bricking it ), and I cannot unlock it for the same reason : 'unlock token check failed'
Click to expand...
Click to collapse
Have you solved the problem with unlock the bootloader? I have the same problem at the moment. So if you know how to fix it.........
Same problem
sgremmen said:
Have you solved the problem with unlock the bootloader? I have the same problem at the moment. So if you know how to fix it.........
Click to expand...
Click to collapse
Already a solution how to unlock the bootloader?
As the title says, I'd like to restore the backup it creates. I have a problem with my phone where it receives zero signal regardless of what rom installed. I have seen a different thread on this problem but there was no clear answer on how to solve it so I'm trying to backtrack my steps. I did the following all at the same time, htc unlock, s-off exploit with Juopunut, and sim unlock using config.dat. They all seemed to work perfectly until I got this problem. I'd ask for support at umlimited.io but when I did they insisted they didn't create the problem and if I persisted in asking how to restore their Juopunut backup I'd be kicked...which was kinda rude, but what are you going to do? Thanks in advance for any help.
what is your radio version? I'd suggest updating to latest radios. or maybe you did something wrong with the sim unlock
EM|NEM said:
what is your radio version? I'd suggest updating to latest radios. or maybe you did something wrong with the sim unlock
Click to expand...
Click to collapse
Didn't even know the radio version could be upgraded/ downgraded. I did a quick search for this but didn't find where to grab a download. Where can I find an update for this? The radio version is 11.25.3504.06_M Also note that this is a GSM phone. So if this is a different incompatible version let me know!
Edit: So, I managed to find some, but when the bootloader trys to flash it it'll give me the message "Model ID incorrect!" This is from the GSM thread...what's going on?
your CID is incompatible. I'd suggest you run an RUU with the latest radios. then flash recovery and then rom.
EM|NEM said:
your CID is incompatible. I'd suggest you run an RUU with the latest radios. then flash recovery and then rom.
Click to expand...
Click to collapse
It's not the CID, I just rewrote it to HTC__001, unless it's expecting something else? It was originally ROGER001 I think.
Edit: I just noticed something, when in fastboot mode the model name is SHOOTER_U, Is there always a underscore there?
hmm not sure about this. If you want to get back to stock you should run the Rogers ICS RUU. see if you get signals back
EM|NEM said:
hmm not sure about this. If you want to get back to stock you should run the Rogers ICS RUU. see if you get signals back
Click to expand...
Click to collapse
Alright, will do. Is there anything I have to do in preparation, relock bootloader, etc?
yes you do need to relock. sorry i forgot to mention that
Well, the RUU update software completely fails. It fails at trying to get the phone to boot into the bootloader and then just pops up a message saying unknown error 155. Anyone know what the hell is going on with my phone?
i think the problem may be your hboot. Try flashing this hboot
http://forum.xda-developers.com/showthread.php?t=1906172
then make sure its locked/relocked then run RUU
Finally got it to install, I had to extract the rom.zip from the .exe and then rename it so that hboot would detect it. Installed fine, but the problem still persists. I have no signal what so ever. Is there no fix for this?
you just installed the rom. u need the radio with it too. Any ways i think some1 else should post in here as im all out of ideas
Does your phone see your sim card? Have you set up your apn's? Can you find a wifi and connect?
Sent from my Evo 3D GSM using Tapatalk 2
Yes, wifi connects, bluetooth connects. I'm pretty sure that the rom.zip is actually everything, it ha s a check list when installing, one of those things was called radio...so I'm pretty sure it installed a new or reinstalled that version. ALso, APNs don't do anything. It's almost like a driver issue or something, the radio just won't get a signal, android doesn't even detect it. When in the options the mobile network toggle is greyed out.
Ok and what rom are you trying to use?
Sent from my Evo 3D GSM using Tapatalk 2
It's the stock ROGERS RUU, I had to extract the ROM.zip file from it because the .exe gave me a unknown error. renaming the .zip to PG86IMG.zip seemed to work. I'm now on stock. The previous roms were nonsense and coolsense. I should also note that originally I tried to install a cdma miui rom that obviously failed.
So your mobile data is still greyed out? Have you tried to find a network through the mobile data settings
Sent from my Evo 3D GSM using Tapatalk 2
---------- Post added at 03:27 PM ---------- Previous post was at 03:20 PM ----------
And count yourself lucky because you could have bricked your phone if you had flashed a cdma firmware package
Sent from my Evo 3D GSM using Tapatalk 2
Yes, it searches for a while, then find a few networks which I'm taking a as a good sign that it even did that, but will not connect at all. When I select one it trys to open a toast error but then is closed immediately after, so I can't even read the error. When I check the network info in the android phone identity it just shows nothing, zero for signal, no network, etc.
Could be sim unlock that did? But I am guessing
Sent from my Evo 3D GSM using Tapatalk 2
Alright, so I've made some progress. I found that this is actually model PG8631000 instead of PG8630000 which is why it failed checks. A quick edit of the android-info.txt in the zip files allows it to flash. No problems with that, flashed new hboots and radios. However, the problem is still there. So finally I found a radio fix program for linux. Booted it up and it appears that my phone won't give any MEID values, they were probably wiped or something. I can't progress because with the wrong values I can completely brick the phone. This makes sense that the phone doesn't have the right values, it feels like the radio works, but has the incorrect values (which is why it finds services but won't connect). Is there any way to restore the MEID?
Edit: Well I'm an idiot, MEID is for CDMA phones. My phone status shows values for the network so that isn't it either....I'm so lost.
Facepalm s off mrthod has changed IMEI of my htc one s,even image crc shows the new changed imei. I think it is because of flashing PJ4010000 zip . how to get my imei restored back to original ?
does anyone know of a way to fix this problem? I tried reverting to stock to fix my radio issue while on mdmower's CyanogenMod 10.1, and did this:
fastboot oem lock
and then this:
fastboot oem writecid VZW_0001
thats the wrong CID and it still accepted it and now i am screwed. it was at 11111111, and i need it to be at VZW__001 (two underscores, and i got it wrong...)
now that i am s-on, it is asking me for a smart_io.crd file that gives me temporary s-off privileges to update that CID. i cannot find that file and dont know how to fix this, so i am stuck in hboot with an invalid CID and cannot update it while s-on, and can't RUU while CID is invalid... i really screwed up here and you guys might be able to help. its a soft brick, but i cant understand what to do.
Here is a picture of hboot:
Sent from my ADR6400L using xda app-developers app
cyberkeeper1 said:
does anyone know of a way to fix this problem? I tried reverting to stock to fix my radio issue while on mdmower's CyanogenMod 10.1, and did this:
fastboot oem lock
and then this:
fastboot oem writecid VZW_0001
thats the wrong CID and it still accepted it and now i am screwed. it was at 11111111, and i need it to be at VZW__001 (two underscores, and i got it wrong...)
now that i am s-on, it is asking me for a smart_io.crd file that gives me temporary s-off privileges to update that CID. i cannot find that file and dont know how to fix this, so i am stuck in hboot with an invalid CID and cannot update it while s-on, and can't RUU while CID is invalid... i really screwed up here and you guys might be able to help. its a soft brick, but i cant understand what to do.
Click to expand...
Click to collapse
Something I don't understand here: how were you able to run fastboot oem writecid while S-ON? Have you since gone S-ON after writing the incorrect CID?
Furthermore, why in the world would you venture from my explicit instructions on how to fix the radio? I can't imagine any reason you would want to re-lock the bootloader or go S-ON. As I keep saying: if you are already unlocked or S-OFF, I almost never see a legitimate reason to run the RUU!
I assume you still can boot into CyanogenMod? If so, follow these instructions (Windows):
Set this in CM: Settings > Developer options > Root access > Apps and ADB
Download the latest unlock script package (we will not run the script, but we do need the files there)
Extract the unlock script package and open a command window in that directory
Type these commands:
Code:
adb root
adb shell "dd if=/dev/block/mmcblk0p4 of=/sdcard/cid"
adb pull /sdcard/cid
hexalter cid 0x214=0x56,0x5A,0x57,0x5F,0x5F,0x30,0x30,0x31
adb push cid /sdcard/
adb shell "dd if=/sdcard/cid of=/dev/block/mmcblk0p4"
This should revert your CID back to VZW__001.
deleted
cyberkeeper1 said:
See I wish I could boot. I didn't understand why it accepted an oem command while s-on either. But alas, it did. I wrote that command after relocking. I am not s-off. Never was, hence my entire problem. I was afraid to try s-off because of the higher possibility of bricking my phone. It's not like the thunderbolt where it always works. If I was s-off I would know what to do and could flash hotdogs as my Cid if I wanted. My first problem is being stuck in hboot and can't restore. I wiped everything. Boot, data, system, recovery all in prep for stock since I am s-on
Click to expand...
Click to collapse
From the bootloader, what is the output this?
Code:
fastboot getvar cid
deleted
cyberkeeper1 said:
The output is:
VZW_0001
Click to expand...
Click to collapse
I can't even explain the number of ways you shot yourself in the foot. You really wiped recovery and boot too? How did you come to believe this would be a good idea? Or is necessary at all?
I believe the only option you have is to try and flash the stock signed recovery through fastboot (not even sure if it'll work), and then use ruu mode to TRY and fix things up:
Code:
fastboot erase cache
fastboot oem rebootRUU
fastboot flash zip ruu.zip
I suspect even that will complain about the incorrect CID though. Perhaps jose has some other ideas.
deleted
deleted
deleted
deleted
deleted
YESSSSSSSSSSSSSS! I GOT IT! I GOT IT! I GOT IT!
When i want something done, i try the impossible...
so... here is the thing... and COMPLETELY unexpected it is. Apparently, you can submit the following cid as an unlock token to HTCdev and get returned a valid unlock code BIN file. with VZW_0001 (obviously incorrect) i STILL received the file and it said token submitted successfully. downloaded, flashed and now unlocked. still s-on, but WAY more room for fixing now. i flashed the CID back to the proper VZW__001 using adb root shell in recovery. worked great! thanks MDMOWER for the codes to revert. now i can flash my custom ROM backup back to the device after flashing just the stock rom (NO RELOCKING THIS TIME FOR ME!) to fix the radios the way i was supposed to. ( being tired = not reading + not using glasses) i don't understand it myself, but i bet this one is going to through you for a loop. the only conclusion i can come up with is the fact that another device actually DOES use the CID of VZW_0001 and is not an officially supported device. that would explain why i was even able to be successful. but its speculation at best until confirmed.
cyberkeeper1 said:
YESSSSSSSSSSSSSS! I GOT IT! I GOT IT! I GOT IT!
When i want something done, i try the impossible...
so... here is the thing... and COMPLETELY unexpected it is. Apparently, you can submit the following cid as an unlock token to HTCdev and get returned a valid unlock code BIN file. with VZW_0001 (obviously incorrect) i STILL received the file and it said token submitted successfully. downloaded, flashed and now unlocked. still s-on, but WAY more room for fixing now. i flashed the CID back to the proper VZW__001 using adb root shell in recovery. worked great! thanks MDMOWER for the codes to revert. now i can flash my custom ROM backup back to the device after flashing just the stock rom (NO RELOCKING THIS TIME FOR ME!) to fix the radios the way i was supposed to. ( being tired = not reading + not using glasses) i don't understand it myself, but i bet this one is going to through you for a loop. the only conclusion i can come up with is the fact that another device actually DOES use the CID of VZW_0001 and is not an officially supported device. that would explain why i was even able to be successful. but its speculation at best until confirmed.
Click to expand...
Click to collapse
moderators, after a few replies from the users, i don't mind if you close my thread because my problem is solved.
EDIT: maybe not yet... bootlooping after fix and restore of last backup before the incident. do i have to have the Super CID written to boot from any custom rom?
cyberkeeper1 said:
does anyone know of a way to fix this problem? I tried reverting to stock to fix my radio issue while on mdmower's CyanogenMod 10.1, and did this:
fastboot oem lock
and then this:
fastboot oem writecid VZW_0001
thats the wrong CID and it still accepted it and now i am screwed. it was at 11111111, and i need it to be at VZW__001 (two underscores, and i got it wrong...)
now that i am s-on, it is asking me for a smart_io.crd file that gives me temporary s-off privileges to update that CID. i cannot find that file and dont know how to fix this, so i am stuck in hboot with an invalid CID and cannot update it while s-on, and can't RUU while CID is invalid... i really screwed up here and you guys might be able to help. its a soft brick, but i cant understand what to do.
Here is a picture of hboot:
Sent from my ADR6400L using xda app-developers app
Click to expand...
Click to collapse
are you rooted?
EDIT: got confused and was thinking this was a new thread sorry
jose51197 said:
you rooted?
Click to expand...
Click to collapse
i am now that i fixed everything. well the recovery partition is rooted. i cant get my phone to boot now though. i tried using the backup i made right before returning to stock and it no longer works. i get a boot loop from the first boot screen. loads HTC logo, then legal warning in red. screen turns black and back again. it never loads into the CM10.1. i manually flashed the kernel from my backup since i am still s-on. i am going to try fresh installing a rom.
cyberkeeper1 said:
i am now that i fixed everything. well the recovery partition is rooted. i cant get my phone to boot now though. i tried using the backup i made right before returning to stock and it no longer works. i get a boot loop from the first boot screen. loads HTC logo, then legal warning in red. screen turns black and back again. it never loads into the CM10.1. i manually flashed the kernel from my backup since i am still s-on. i am going to try fresh installing a rom.
Click to expand...
Click to collapse
You messed a lot with you phone man, better install stock rom throught ruu or mdmowers way then s off revert cid and flash cm10
Sent from my ADR6410LVW using xda app-developers app
jose51197 said:
You messed a lot with you phone man, better install stock rom throught ruu or mdmowers way then s off revert cid and flash cm10
Sent from my ADR6410LVW using xda app-developers app
Click to expand...
Click to collapse
i am inclined to agree based on what its doing, but wanted to be sure. i just didnt want to have to re-re unlock again. lol. i'll see what happens.
I was able to successfully flash cyanogenmod, but my phone only works for data, not for calls or texts. I assume this is because I'm still on Super CID (11111111). When I try to revert to the VZW cid, i receive an error executing the adb shell. It tells me that it's a read only file system. I'm rooted, s off, and bootloader unlocked. Any help would be greatly appreciated as my phone is only half usable right now
Don't use adb shell once you're s-off. Use these commands:
Code:
adb reboot bootloader
Once in fastboot, issue this command to revert to the VZW CID:
Code:
fastboot oem writecid VZW__001
that's it.
Sent from my Incredible 4G LTE using xda app-developers app
Thanks so much for the quick response. I knew I was overthinking it. Just applied the change, rebooting now. I'll follow up with my findings.
---------- Post added at 06:27 PM ---------- Previous post was at 06:16 PM ----------
Well, it changed the CID, but the issue still persists. If I look in about phone > status, it says my mobile phone number is 000-000-0000. I'm definitely preplexed to say the least.
Guys, im from chile so my english is bad xD
i was trying to change the rom of my phone and i tried with this Android_Revolution_HD-One_M8_43.0_391da9.zip
so when i installed the phone just went black ... it never started so i forced restarted the phone,
the problem doesnt fixes im trying to install another roms but its still here, my phone is S-OFF and Unlocked fastboot.
another tip is when i enter fastboot and a message shows "Sd checking ... no image and another that says no image or wrong image"
i need help guys .
Pd : I can enter recovery to install another roms and restart to get into fastbot.
Thx you so much!.
Fastboot erase cache, then flash TWRP again via fastboot. Make sure its the current TWRP version 2.8.7.
If you still can't flash ROMs after that, try the Lollipop RUU linked in my Index: http://forum.xda-developers.com/showthread.php?t=2751432.
Problem still here
i did erase cache and flash twrp again with the last version 2.8.7 and i still cant flash when i try the ruu it doesnt recognize my phone
and tried the hboot with the 0P6BIMG.zip but it says model id error ... thx you man
Edit :
No, i cant install another roms , when i do it and restart it just go to fastboot so i dont know why the so is not starting
KitexK said:
i did erase cache and flash twrp again with the last version 2.8.7 and i still cant flash when i try the ruu it doesnt recognize my phone
and tried the hboot with the 0P6BIMG.zip but it says model id error ... thx you man
Edit :
No, i cant install another roms , when i do it and restart it just go to fastboot so i dont know why the so is not starting
Click to expand...
Click to collapse
Are you using an AT&T HTC ONE M8?
Really i dont know i bought from a old friend the last year ... in the model says op6b700 so if that helps
other information in the fast boot screen:
m8_whl pvt ship s-off
....
hboot-3.19.0.0000
radio-1.08.20.0916
opendsp-v46.2.2.00564-m8974.f0.0811
os-3.30.651.2
eMMC-boot 2048MB
Thx for your help man
KitexK said:
Really i dont know i bought from a old friend the last year ... in the model says op6b700 so if that helps
Click to expand...
Click to collapse
If you don't know what version of the M8, you shouldn't be posting here (just causing confusion for those trying to help). This section is specific to the AT&T version.
You also can't be running RUUs recklessly. RUU needs to match your phone's CID and MID. Its a good thing it failed those checks, otherwise running the GSM RUU on the CDMA (Sprint) model probably would have bricked your phone.
Your MID is Sprint. Try the RUU at the bottom of the following webpage: http://www.htc.com/us/support/htc-one-m8-sprint/news/
---------- Post added at 09:19 AM ---------- Previous post was at 09:16 AM ----------
KitexK said:
when i try the ruu it doesnt recognize my phone
Click to expand...
Click to collapse
Did you run the RUU with the phone in fastboot mode? If not, that is required.
If you were in fastboot mode, than you have a fundamental connectivity issue, probably on the PC side, that you should fix first. Uninstall and re-install HTC Sync, HTC drivers. Try another USB port, and another cable. If you have WIn10, the RUU won't work.
Omg im so noob xDD, thx you so much man , i installed a sprint rom and now im on android , im so sorry about this, really you are great.
THX YOU!