You make it sound easy bud!!!Ahhh, the following of explicit instructions prevails yet again.
Ahhh, the following of explicit instructions prevails yet again.
Sorry that it took me so long, thread stickied.
OB
If you follow this guide, I can help you. If you follow another guide, please post in that thread...I can't unlock the bootloader on my phone I get this when I try to flash the unlock code
C:\QADERSO\Root>fastboot flash unlocktoken Unlock_code.bin
sending 'unlocktoken' (0 KB)...
OKAY [ 0.140s]
writing 'unlocktoken'...
FAILED (remote: unlock token check failed)
finished. total time: 0.156s
I've tried it about 20 times yesterday and it wouldn't work I have a stock phone with the latest update
Yes, but it wouldn't hurt to activate before either. Either way, I'd recommend being on a stock-based sense ROM when you activate.Ok, just double checking: I can activate the phone AFTER I do all this right?
Like I can have a new phone out of the box, do these steps, and when I'm done I can call Virgin Mobile and activate it, right?
If you follow this guide, I can help you. If you follow another guide, please post in that thread...
Your folder structure tells me you did not follow this guide when you pasted what you did above...
I can't unlock the bootloader on my phone I get this when I try to flash the unlock code
C:\QADERSO\Root>fastboot flash unlocktoken Unlock_code.bin
sending 'unlocktoken' (0 KB)...
OKAY [ 0.140s]
writing 'unlocktoken'...
FAILED (remote: unlock token check failed)
finished. total time: 0.156s
I've tried it about 20 times yesterday and it wouldn't work I have a stock phone with the latest update
If you follow this guide, I can help you. If you follow another guide, please post in that thread...
I suggest starting over from the beginning of this guide and see if remanifest can help you.They all bring me here I've tried about 3 ways the htcdev website and two other ways from different forums and I get the same result in all of them
I suggest starting over from the beginning of this guide and see if remanifest can help you.
Having said that, if you do a Google search for that error you will find that many Evo 3D users that have had their motherboards replaced get that error and can't HTC unlock. If that is the case with your phone, you can only hope that the Ultimate Recovery Tool for getting S-OFF without HTC unlock that remanifest has been working on with unknownforce at XDA eventually works for the Evo V, but I'm not optimistic about that.
Some users have been able to resolve HTC unlock errors by flashing the latest RUU but that's not possible in your case since you've already applied the latest OTA update and the VM RUU can't be installed with hboot 1.58.
ramjet73
If you sent it to HTC they probably replaced the motherboard and that may be what is preventing HTC unlock from working for you. Since the only currently working method for getting root and S-OFF for the Evo V requires the HTC bootloader unlock your best bet would be to find something else that is wrong with the phone and exchange it with VM not HTC. They seem to be pretty liberal in their replacement policy and a different phone (as opposed to one that has been repaired by HTC) could probably be unlocked successfully.Thanks, so basically I can't unlock then? I'm not sure if the motherboard has been replacedi sent the device to HTC due to the phone freezing when touching the screen with two fingers but I don't know what they did to fix it
If you're willing, and you understand the risk, I would be happy to help you with unknownforce's downgrade tool.Thanks, so basically I can't unlock then? I'm not sure if the motherboard has been replacedi sent the device to HTC due to the phone freezing when touching the screen with two fingers but I don't know what they did to fix it
He seems to be preoccupied with his S4 now and it's hard to blame him for that.unknownforce was saying that after bricking, you should be able to use a hex editor to change the CID at the beginning of partition 17, then flash that new partition back on the phone with the Sprint CID. I've been really busy these past few weeks, so I haven't tried it yet. I was hoping he'd build it into his binary release - it would make the process much more approachable.
If you sent it to HTC they probably replaced the motherboard and that may be what is preventing HTC unlock from working for you. Since the only currently working method for getting root and S-OFF for the Evo V requires the HTC bootloader unlock your best bet would be to find something else that is wrong with the phone and exchange it with VM not HTC. They seem to be pretty liberal in their replacement policy and a different phone (as opposed to one that has been repaired by HTC) could probably be unlocked successfully.
ramjet73
If you're willing, and you understand the risk, I would be happy to help you with unknownforce's downgrade tool.
Basically, you temporarily brick your phone, then you downgrade your HBOOT and run the Sprint RUU. After that, you use the revolutionary S-OFF tool to get S-OFF. From there, you can flash whatever HBOOT and ROM you want. In your case, with the EVO V, we'd also perform a backup of partition 17, edit it, and then restore it
Which is why I referred him back to this thread.Then again, I do not know exactly what is stored on what partitions... it's a definite risk, but it may also yield a favorable result. If I was in the same boat, I'd personally give it a shot. If it winds up a brick or something, I'd just do a Virgin Mobile replacement on it -- they wouldn't know the difference.
We've been tracking upcoming products and ranking the best tech since 2007. Thanks for trusting our opinion: we get rewarded through affiliate links that earn us a commission and we invite you to learn more about us.