I recently bought a Verizon/HTC Incredible 4g LTE and I was wanting to install cyanogenmod. I was able to find many tutorials to unlock the bootloader, but none of them have been successful.
I keep getting linked to this post:
Code:
http://forum.xda-developers.com/showthread.php?t=1986346&
It works until I get to "adb restore fakebackup.ab" where my phone goes to "Full Restore" but asks for device encryption password, and restore my data is greyed out.
I continued to the next step anyways to get the error: "link failed No such file or directory" endlessly
Since it said there would be errors i continued anyways and had a $ at the end instead of #
Please help!!
elijahkan14 said:
I recently bought a Verizon/HTC Incredible 4g LTE and I was wanting to install cyanogenmod. I was able to find many tutorials to unlock the bootloader, but none of them have been successful.
I keep getting linked to this post:
Code:
http://forum.xda-developers.com/showthread.php?t=1986346&
It works until I get to "adb restore fakebackup.ab" where my phone goes to "Full Restore" but asks for device encryption password, and restore my data is greyed out.
I continued to the next step anyways to get the error: "link failed No such file or directory" endlessly
Since it said there would be errors i continued anyways and had a $ at the end instead of #
Please help!!
Click to expand...
Click to collapse
Have you tried the automatic method on the same link you just mentioned? That's the way I did it. I had a few snags myself but they all disappeared when I tried it on a different computer. I also read several places to try a new USB. You could also try this all-in-one tool kit — http://forum.xda-developers.com/showthread.php?t=1758682 I've used it for a couple of different thins and it has been very usefull. You can use it to unlock your bootloader.
I'm not sure about your specific problem but I hope this is helpful.
Kienan said:
Have you tried the automatic method on the same link you just mentioned? That's the way I did it. I had a few snags myself but they all disappeared when I tried it on a different computer. I also read several places to try a new USB. You could also try this all-in-one tool kit — http://forum.xda-developers.com/showthread.php?t=1758682 I've used it for a couple of different thins and it has been very usefull. You can use it to unlock your bootloader.
I'm not sure about your specific problem but I hope this is helpful.
Click to expand...
Click to collapse
I can't get any of these methods to work
elijahkan14 said:
I can't get any of these methods to work
Click to expand...
Click to collapse
1. Make sure you are on the latest software: 2.17.605.2
2. Factory reset your phone
3. Slowly go through the manual instructions here: [Script] Automated Unlock/SuperCID/Temp-Root scripts for Windows and Linux
So, I've unlocked this phone before.
Just got a replacement.
EVERYTIME I put the token code in and summit I get failed!
screenshot of the error:
http://s28.postimg.org/z8obp6h58/Untitled.jpg
I tired a few different codes and nothing.
HELP?
I'm on bootloader 1.60000
Still no luck.
It tells me in bootloader its tampered but with s-on and still locked.
BlowUpTheOutsideWorld said:
I'm on bootloader 1.60000
Still no luck.
It tells me in bootloader its tampered but with s-on and still locked.
Click to expand...
Click to collapse
I was having difficulty with the SuperCID hack, and it appears that it was due to an OTA update. I was able to following the directions prescribed here, but I had HBOOT 1.15 and not 1.16. The basic idea is to
1. Gain "temp-root" access using the loop-restore trick together with the fake_backup.ab file.
The next steps were failing for me. I was able to verify that mmcblk0p4 had been copied over correctly, with the "modded" version, but each time the boot loader was rebooted, it would be replaced with the original version containing VZW__001, and not 11111111. However apparently all that needed to be done to reach S-OFF status was:
2. Run Rumrunner after obtaining temp-root status. The Rumrunner binary unlocks the phone and places it in S-OFF status.
Related
I bought used Rezound and figured I'd unlock the bootloader using HTCDev.com
I go through all the steps and at the last part after I enter the token I get this:
Unlocking Bootloader Failed!
Sorry it didn't work out. Here's why:
We're sorry, but it appears your attempt to unlock the bootloader on this device has failed. This could be caused by several factors including simple errors in the entry of the unlock token, problems with your device, or a lack of manufacturer support for the unlocking process. Please see the specific error code listed below, and try again if necessary.
Error Code: 173.
Error Reason: Check Rule Fail with exception.
I noticed the top of the screen on my phone says ***RELOCKED***
Is there not a way to unlock it once its relocked?
diablo2jz said:
I bought used Rezound and figured I'd unlock the bootloader using HTCDev.com
I go through all the steps and at the last part after I enter the token I get this:
Unlocking Bootloader Failed!
Sorry it didn't work out. Here's why:
We're sorry, but it appears your attempt to unlock the bootloader on this device has failed. This could be caused by several factors including simple errors in the entry of the unlock token, problems with your device, or a lack of manufacturer support for the unlocking process. Please see the specific error code listed below, and try again if necessary.
Error Code: 173.
Error Reason: Check Rule Fail with exception.
I noticed the top of the screen on my phone says ***RELOCKED***
Is there not a way to unlock it once its relocked?
Click to expand...
Click to collapse
no, you can unlock it once it's relocked. Most of us that have taken the OTA by RUUing had to unlock and relock . So, I would go through the process again , just check and double check the steps. I had an issue where it failed 8 straight attemtps and it turned out I was actually copying a space in the code..once I removed the space it went right through.
I made sure I wasn't copying the spaces, tried again and took a screen shot.
Gave same error
diablo2jz said:
I made sure I wasn't copying the spaces, tried again and took a screen shot.
Gave same error
Click to expand...
Click to collapse
It has let me redo the HTC Dec steps with my phone multiple times. I finally figuired out once you get the unlock.bin file you can always reuse it. I do what is stopping you. :/
Sent from my ADR6425LVW using XDA App
Yeah I googled the heck out of everything I could think of and searched XDA and found almost nothing.
Guess I'm just lucky
diablo2jz said:
I made sure I wasn't copying the spaces, tried again and took a screen shot.
Gave same error
Click to expand...
Click to collapse
Maybe a dumb question, but your not including "please cut the following " part in it when you submit are you ?
Nope only pasted what I have highlighted in post 3.
Not to mention I have purposely copied them or some stuff out, and get a normal error to the extent of "You're token is to long, or to short" ect.
Same issue
Error Code: 173.
Error Reason: Check Rule Fail with exception
Anyone else getting this?
diablo2jz said:
Nope only pasted what I have highlighted in post 3.
Not to mention I have purposely copied them or some stuff out, and get a normal error to the extent of "You're token is to long, or to short" ect.
Click to expand...
Click to collapse
Sorry, no idea then ..
So wait, where did you get this phone? Is it possible the old owner unlocked it, relocked it, then sold it? If so, anybody know if he will be able to unlock since he probably doesn't have the original key?
Comicazy said:
Is it possible the old owner unlocked it, relocked it, then sold it?
Click to expand...
Click to collapse
That is correct. I had no idea but that's what I realized.
If I can't I'm going to sell this damn thing for a Nexus.
Unlocking Bootloader Failed! 173
I am getting the same error. I just activated the phone yesterday and have tried the process on a PC and a Mac now. Are the token identifiers supposed to change every time? I noticed that every time I type the command fastboot oem get_identifier_token I get a different token. I read some other posts where they were having problems and it ended up being a hardware issue. Any thoughts?
timothydye79 said:
I am getting the same error. I just activated the phone yesterday and have tried the process on a PC and a Mac now. Are the token identifiers supposed to change every time? I noticed that every time I type the command fastboot oem get_identifier_token I get a different token. I read some other posts where they were having problems and it ended up being a hardware issue. Any thoughts?
Click to expand...
Click to collapse
I have unlocked and relocked my phone 2 times now, and got a different token and identifier every time, so it shouldn't matter if he has the original unlock token or not.
mjh68 said:
I have unlocked and relocked my phone 2 times now, and got a different token and identifier every time, so it shouldn't matter if he has the original unlock token or not.
Click to expand...
Click to collapse
but if you want to re-unlock you can re use the same unlock bin file without generating a new token. If you make a new token your bin file is invalidated.
https://twitter.com/#!/Jmz_Software/status/164817446841221120
known issue now
diablo2jz said:
I bought used Rezound and figured I'd unlock the bootloader using HTCDev.com
I go through all the steps and at the last part after I enter the token I get this:
Unlocking Bootloader Failed!
Sorry it didn't work out. Here's why:
We're sorry, but it appears your attempt to unlock the bootloader on this device has failed. This could be caused by several factors including simple errors in the entry of the unlock token, problems with your device, or a lack of manufacturer support for the unlocking process. Please see the specific error code listed below, and try again if necessary.
Error Code: 173.
Error Reason: Check Rule Fail with exception.
I noticed the top of the screen on my phone says ***RELOCKED***
Is there not a way to unlock it once its relocked?
Click to expand...
Click to collapse
if you've bought a used rezound, that means the person
who sold probably unlocked the phone first.
why not ask that person for the unlocked token he used?
con247 said:
but if you want to re-unlock you can re use the same unlock bin file without generating a new token. If you make a new token your bin file is invalidated.
Click to expand...
Click to collapse
Ah, gotcha .. I had already deleted the first token so didn't have a choice hehe
This is an issue with the website, not the phone. I'm dealing with the same bull****.
I had the same problem. I relocked to get the update and could not unlock. I don't know what the fix is. Fortunately I saved the file from the first time I unlocked and it worked fine.
diablo2jz said:
I made sure I wasn't copying the spaces, tried again and took a screen shot.
Gave same error
Click to expand...
Click to collapse
You know, I don't know if that's sensitive info but you may want to black some of that out just in case since it pertains to your particular device. Probably doesn't matter but I always opt for the safe route since I'm a paranoid android.
EDIT: Looks like HTC fixed the issue and people are getting their unlock codes now.
http://forum.xda-developers.com/showthread.php?t=1475864&page=2
I have repeated the process to unlock the bootloader on my HTC EVO LTE, but after reboot it still says "LOCKED". I successfully submitted the token and even got the prompt on the phone whether I wanted to unlock, and I selected the first option "Yes". But, it's still locked upon reboot. Any ideas???
thambikutty said:
I have repeated the process to unlock the bootloader on my HTC EVO LTE, but after reboot it still says "LOCKED". I successfully submitted the token and even got the prompt on the phone whether I wanted to unlock, and I selected the first option "Yes". But, it's still locked upon reboot. Any ideas???
Click to expand...
Click to collapse
Anybody?
You simply must follow instructions exactly, not overlooking anything.
First go to htcdev-dot-com
Then click on the "Unlock Bootloader" link.
Follow the instructions exactly, submitting a valid email address with registration, and receive your unlock code file.
There are many more instructions on this forum for using this information to successfully unlock your bootloader.
I have had to use the same methods several times within the past few hours, just to perform a successful S-OFF
on my device. You can even stay at the htcdev website, submitting new device IDs as neccessary, until you
achieve your goal.
There may be other methods to unlock the bootloader, but I have no knowledge of them.
Hey guys. Need a big hand here. So I have a HTC One on contract from Three in the UK.
I rooted the phone and all that jazz and decided on putting a custom ROM on my device.
However while in TWRP I wiped the phone and seemingly all the contents on it, including TWRP.
Now I have a bricked phone that boots into recovery/ the bootloader only. I've tried flasing
RUU files on but it fails with the error code 140? I don't know much about this I'm quite a noob.
In recovery the information is as follows:
*** TAMPERED ***
*** RELOCKED ***
*** SECURITY WARNING ***
M7_UL PVT SHIP S-ON RH
HBOOT- 1.54.0000
RADIO-4A. 17. 3250. 14
OpenDSP-v31.120.274.0617
OS-2.24.401.0
eMMC-boot 2048MB
Please help me. I've read through wonderful guides by other patrons on this website but nothing seems to work.
I'm at my wits end.
Thank you in advance for any help.
I know very little about this, but just to brainstorm (and confirm a few basic facts):
When you rooted originally, did you use HTC's bootloader unlocker or a different method to unlock the bootloader?
How are you flashing ROMS? Are you doing everything through the phone (example, using one-touch-root apps) or are you using the Android Debug Bridge?
The bootloader typically comes with options to reboot, boot into recovery, factory reset, etc. Can you confirm that these options have disappeared (or never existed in the first place)?
My knee-jerk reaction is that you didn't use an HTC bootloader unlocker and, therefore, the HTC GUU detects a bootloader mismatch and aborts. Therefore, you need to see if there's a way to flash a stock HTC bootloader (which, I can tell you from experience, is usually a one-way-trip to super-bricking) or see if the bootloader you already have installed can be unlocked through the ADB.
In my very limited experience and understanding of Android, it's generally pretty difficult to wipe the recovery partition from within the phone - one generally as to flash it from ADB or screw with the bootloader in some way to wipe it. I wonder, therefore, whether the recovery partition is just fine but maybe the bootloader is throwing a fit because it's not the HTC default.
I'm sure you've tried or thought of all of this, but since nobody else is stepping up, I thought I'd help brainstorm a bit and keep the thread fresh.
Borden Rhodes said:
I know very little about this, but just to brainstorm (and confirm a few basic facts):
When you rooted originally, did you use HTC's bootloader unlocker or a different method to unlock the bootloader?
How are you flashing ROMS? Are you doing everything through the phone (example, using one-touch-root apps) or are you using the Android Debug Bridge?
The bootloader typically comes with options to reboot, boot into recovery, factory reset, etc. Can you confirm that these options have disappeared (or never existed in the first place)?
My knee-jerk reaction is that you didn't use an HTC bootloader unlocker and, therefore, the HTC GUU detects a bootloader mismatch and aborts. Therefore, you need to see if there's a way to flash a stock HTC bootloader (which, I can tell you from experience, is usually a one-way-trip to super-bricking) or see if the bootloader you already have installed can be unlocked through the ADB.
In my very limited experience and understanding of Android, it's generally pretty difficult to wipe the recovery partition from within the phone - one generally as to flash it from ADB or screw with the bootloader in some way to wipe it. I wonder, therefore, whether the recovery partition is just fine but maybe the bootloader is throwing a fit because it's not the HTC default.
I'm sure you've tried or thought of all of this, but since nobody else is stepping up, I thought I'd help brainstorm a bit and keep the thread fresh.
Click to expand...
Click to collapse
I unlocked the bootloader originally by getting a specific code from HTC and using it through the command prompt I think. I can go into the bootloader and it has all the fastboot, recovery, factory reset business there. Trying factory reset does nothing. I've downloaded HTC toolkit 2.2 and I tried initially pushing ROMS to flash to TWRP, but it would never detect my phone. Then I stupidly did a full wipe through TWRP and now that's disappeared. All that's left is the bootloader now. I've tried forcing RUU updates through the HTC toolkit but it always fails. So does running the normal RUU process. I can't seem to find the correct one for Three UK. The most I've been able to do is re-lock the bootloader and I'm running out of ideas. Thank you for your reply. I feel so helpless!.
If I've read your message correctly, you are doing everything through the HTC toolkit and not through the Android SDK. Frankly, I don't know how the former works. Especially if the HTC Toolkit isn't detecting your phone, you may want to run over to http://developer.android.com/sdk/ and fetch the SDK for your system and set it up. You don't need the ADT Bundle, just the SDK Tools link at the bottom. This may make it easier for other, more knowledgeable people debug your phone, since they all use the SDK. The weaponry you'll be using is all in the <sdk install location>/tools directory, so get a command prompt window pointed there (by the by, are you using Windows, Mac or Linux?)
If you already have your SDK up, or once you do, you'll want to get familiar with the fastboot command, described in this post: forum.xda-developers.com/showthread.php?t=2277112 . What we want to do is see whether we can flash a new recovery ROM.
As long as you don't attempt to flash over the bootloader, you shouldn't super-brick your phone. Based on the message in your original post, your bootloader may have relocked itself. If your first attempt at installing a new recovery ROM doesn't work, then you'll have to use the procedure you used originally to unlock your bootloader. If you've forgotten how to do that, then these instructions (which assume you're using the SDK) should help: http://wiki.cyanogenmod.org/w/Install_CM_for_m7.
You're currently using TWRP, which I've personally found buggy. Until you have a functioning phone again, you may want to use ClockworkMod (CWM) Recovery instead: http://www.clockworkmod.com/rommanager. It has fewer features, but at least they work properly. If flashing ROMs over fastboot is new to you, there are plenty of guides on the Interwebs to help you. I'll also try to walk you through it if you let me know where you're getting stuck. The critical thing, considering that there are many types of HTC One, is to make sure that you flash the ROM that exactly matches your phone. If you flash the wrong ROM, you probably won't break your phone any more than it is, but let's try not to test that theory. If you're not positive which phone you have, say so and we'll help you find out.
Let us know once you have CWM on your phone or where you got stuck. The advantage of using the SDK, too, is that you can copy and paste the output right back to the forum.
I hope I understood everything correctly. Let me know if I haven't.
Hello,
I am sure this has been posted before and I apologize but I need help.
I have an AT&T branded unlocked HTC One M8 that I am using with T-Mobile.
I am able to get everything except for MMS I have been looking at different forums and posts and all over Google trying to figure out the best and easiest way to get MMS working. I unlocked the bootloader, rooted and s-off I have also changed the CID to T-Mobile however I can't seem to change the MID as I get the "device not found" error in the cmd prompt. I also read I can just flash the T-MO RUU but in trying that the RUU downloads on my computer but nothing else.
I am a newbie so I don't want to brick my phone trying to flash different things where I really don't know what I am doing. lol
Can someone please point me in the right direction with updated information on what I can do? I have tried different apns as well for T-mobile and nothing is working. I have also tried different 3rd party sms apps and still no MMS.
Thank you for any help you can give.
-T
tivo1704 said:
Hello,
I am sure this has been posted before and I apologize but I need help.
I have an AT&T branded unlocked HTC One M8 that I am using with T-Mobile.
I am able to get everything except for MMS I have been looking at different forums and posts and all over Google trying to figure out the best and easiest way to get MMS working. I unlocked the bootloader, rooted and s-off I have also changed the CID to T-Mobile however I can't seem to change the MID as I get the "device not found" error in the cmd prompt. I also read I can just flash the T-MO RUU but in trying that the RUU downloads on my computer but nothing else.
I am a newbie so I don't want to brick my phone trying to flash different things where I really don't know what I am doing. lol
Can someone please point me in the right direction with updated information on what I can do? I have tried different apns as well for T-mobile and nothing is working. I have also tried different 3rd party sms apps and still no MMS.
Thank you for any help you can give.
-T
Click to expand...
Click to collapse
OK so cid is done in fastboot and mid is adb so did you have usb debugging on,and was attempting to change your mid the first time you used adb with your htc?
S-OFF offers it's advantages with flashing ruu in the external sdcard "0P6BIMG.zip" method
http://forum.xda-developers.com/htc-one-m8/development/firmware-flashing-panic-attacks-t2824048
jball said:
OK so cid is done in fastboot and mid is adb so did you have usb debugging on, and was attempting to change your mid the first time you used adb with your htc?
S-OFF offers it's advantages with flashing ruu in the external sdcard "0P6BIMG.zip" method
http://forum.xda-developers.com/htc-one-m8/development/firmware-flashing-panic-attacks-t2824048
Click to expand...
Click to collapse
Hi,
Yes USB debugging is on and I followed all steps to a Tee from the post found on here (to change MID without Eng) I still get the same Device not found error even after inputting other commands that show my Serial Number so I am not sure what I am doing wrong. All I want is to update my software so I can start sending/receiving MMS.
What folder is your
adb/fastboot .open the folder and Shift+right-click to open a command prompt and try it again .
Did you use a Toolkit to unlock the bootloader and to install custom recovery?
Just trying to go over what's different if you used just
adb/fastboot from the very start out of the box
Have you manually entered T-Mobile's APN info into the phone? This is typically required to use any device that is not purchased from your carrier (carrier branded).
BTW, what is with all the bad thread titles today? At least 4 threads in this forum titled "HELP", "[Q]" or something similar. This this is a Q&A and help forum, so of course you are asking for help and have a question. But please try to give your thread a specific title describing your issue, to help keep the forum organized.
I am a total newbie to Android modifications, and tried to find a way of specifying custom notifications on my HTC One Max. I have later found the application Ringdroid that fixes everything that I needed, but before I did that, I believed that I had to root the phone to achieve this. So, I read a lot of stuff, downloaded a lot of files, messed with adb, clockworkmod, rumrunner etc. without really knowing what I was doing, and in the end gave up, since it didn't look like I managed to root the phone properly after all. But, anyway, I understood that something had changed, since a couple of applications were missing. Anyway, the phone has worked fine since then, until recently, when I got a notice that software update 4.13.401.7, containing Android 5.0 Lollipop, and various other stuff, was ready for installation. So, I downloaded the update, and told it to install. The phone reboots, and then I get the following message:
CWM-based Recovery v6.0.5.1
E: Invalid command argument
E: Invalid command argument
Finding update package...
E: unknown volume for path [INTERNALSDCARD:0/Do
wnload/OTA_T6_UL_L50_SENSE60_MR_HTC_Europe_4.1
3.401.7-3.23.401.1_release_4360116ezjvoz69qm8r
zky.zip]
E: Can't mount INTERNALSDCARD:0/Download/OTA_T6
_UL_L50_SENSE60_MR_HTC_Eutope_4.13.401.7-3.23.
401.1_release_4360116ezjvoz69qm8rzky.zip
Installation aborted.
Rebooting...
Is there a way of letting me a) reset my phone to the default settings, thus allowing me to perform the Lollipop upgrade? (the preferred solution), or b), perform this upgrade without resetting it?
If not s-off,locked mudt flash stock recovery,must relock boot loader imo unroot and then take the update
[email protected] said:
I am a total newbie to Android modifications, and tried to find a way of specifying custom notifications on my HTC One Max. I have later found the application Ringdroid that fixes everything that I needed, but before I did that, I believed that I had to root the phone to achieve this. So, I read a lot of stuff, downloaded a lot of files, messed with adb, clockworkmod, rumrunner etc. without really knowing what I was doing, and in the end gave up, since it didn't look like I managed to root the phone properly after all. But, anyway, I understood that something had changed, since a couple of applications were missing. Anyway, the phone has worked fine since then, until recently, when I got a notice that software update 4.13.401.7, containing Android 5.0 Lollipop, and various other stuff, was ready for installation. So, I downloaded the update, and told it to install. The phone reboots, and then I get the following message:
CWM-based Recovery v6.0.5.1
E: Invalid command argument
E: Invalid command argument
Finding update package...
E: unknown volume for path [INTERNALSDCARD:0/Do
wnload/OTA_T6_UL_L50_SENSE60_MR_HTC_Europe_4.1
3.401.7-3.23.401.1_release_4360116ezjvoz69qm8r
zky.zip]
E: Can't mount INTERNALSDCARD:0/Download/OTA_T6
_UL_L50_SENSE60_MR_HTC_Eutope_4.13.401.7-3.23.
401.1_release_4360116ezjvoz69qm8rzky.zip
Installation aborted.
Rebooting...
Is there a way of letting me a) reset my phone to the default settings, thus allowing me to perform the Lollipop upgrade? (the preferred solution), or b), perform this upgrade without resetting it?
Click to expand...
Click to collapse
Wonders_Never_Cease said:
If not s-off,locked mudt flash stock recovery,must relock boot loader imo unroot and then take the update
Click to expand...
Click to collapse
Thanks a lot, Wonders_Never_Cease. However, as stated in my original post, I'm a total newbie here, so I need detailed instructions on how to "flash stock recovery", "relock boot loader" etc. If you (or anyone else) could be so kind as to provide me with detailed step-by-step instrucions, I would be eternally grateful.
Sigurd
Command would be the same as when flashed clockwork mod recovery
Download stock recovery for your build that's on the phone now
Reboot device into bootloader
Open command prompt
CD to where adb/fastboot is located
Copy downloaded stock recovery to that location
Connect phone to computer
Type into command prompt window "fastboot flash (recovery name)" minus parentheses)
Once it finishes type in command prompt "fastboot reboot-bootloader" (minus parentheses)
Once device reboots into bootloader
Type into command prompt "fastboot oem lock" (minus parentheses) this will relock the bootloader
Should be able to take ota without incident
Now you will probably have to redo the unlock process via htc site, or you may be able to use original bin you unlocked device to begin with, unsure...
hopefully I covered all steps been awhile
Good luck
WNC
[email protected] said:
Thanks a lot, Wonders_Never_Cease. However, as stated in my original post, I'm a total newbie here, so I need detailed instructions on how to "flash stock recovery", "relock boot loader" etc. If you (or anyone else) could be so kind as to provide me with detailed step-by-step instrucions, I would be eternally grateful.
Sigurd
Click to expand...
Click to collapse
Is there a way to downgrade the stock ROM to use rumrunner? I foolishly installed the latest ota and rumrunner won't work. $25 for sunshine seems a bit steep.