Hey,
I'm trying to get the bootloader (S-ON) to say "LOCKED" instead of "RE-LOCKED" for warranty purposes (e-bay store- random reboots down long before I unlocked/rooted it. The HTC Amaze tool from the Play store, wiping system/re-flashing ROMs, using different/stock ROM/kernels don't help). From what I've read, using "mainver error fix" with Hasoon2000's tool seems to be the key, but everytime I engage the command, it states that the "device isn't found." Android debugging is definitely on (I've checked like 5 times) and it's in "Fastboot USB" mode (hence the computer [Win7] is registering the device). What am I doing wrong? Any helped be appreciated.
Ugh, do you think they'll even care whether or not it's "Re-locked" instead of "Locked"?
==
Also, S-off doesn't seem to be possible with this phone; one of the contact points in the back of the phone (not GND) seems to be missing the brass (or brass-colored) contact points
Related
Just as the title states...
I have completed the process on the HTCDev site many many times. The process itself works fantastic. Each step responds exactly how they state it should. I submit the token code and get a Bin file. Using fastboot to flash the Bin file results in the phone prompting me to unlock the bootloader. I select yes using the volume up and then hit power. The phone powers off and reboots restoring everything to factory. So it would seem that everything works correctly. I get no error messages during the process. I get nothing but the results that I should be expecting...EXCEPT...
The bootloader remains locked.
I'm beyond frustrated at this point. I've followed every single set of instructions just thinking maybe there's a step missing in one of them. Yet they all perform the same. End result...Bootloader still locked. No idea what is going on. Called HTC Tech Support and they weren't any help at all. Basically they said to leave a comment on the HTCDev site.
Any ideas???
Have you tried flashing anything even though it still says locked? It is a longshot, but there is a chance it is unlocked but just still says locked.
rultin said:
Just as the title states...
I have completed the process on the HTCDev site many many times. The process itself works fantastic. Each step responds exactly how they state it should. I submit the token code and get a Bin file. Using fastboot to flash the Bin file results in the phone prompting me to unlock the bootloader. I select yes using the volume up and then hit power. The phone powers off and reboots restoring everything to factory. So it would seem that everything works correctly. I get no error messages during the process. I get nothing but the results that I should be expecting...EXCEPT...
The bootloader remains locked.
I'm beyond frustrated at this point. I've followed every single set of instructions just thinking maybe there's a step missing in one of them. Yet they all perform the same. End result...Bootloader still locked. No idea what is going on. Called HTC Tech Support and they weren't any help at all. Basically they said to leave a comment on the HTCDev site.
Any ideas???
Click to expand...
Click to collapse
Since it's getting wiped anyway, exchange the phone for a new one.
MrSmith317 said:
Since it's getting wiped anyway, exchange the phone for a new one.
Click to expand...
Click to collapse
I second that, I had a problem Unlocking my Rezound, I called HTC they said they dont replace phones and to call VZW. I called VZW told them that HTC told me to call for a replacement, they gave me a hard time. I told them as a developer, not being able to unlock my phone is a detrimental to my livelyhood. They sent me a refurb (standard) and I had no problems unlocking it. I posted my saga over in general you can see it here http://forum.xda-developers.com/showthread.php?t=1416472
I know this seems like a dumb question but I assure you there is some logic to it.
My dopey friend started to unlock his Prime, but his connection via USB came undone and he says that the unlocking "failed". He came to me asking if it worked or not. I'm no expert, but I am curious.
Here are the variables:
1. When I attempt to run Unlock Device, everything prompts you like it's never been done.
2. When booting with power and voldown, it quickly flashes something like "android userh bootloader version 1.20 us_eepad blah blah" then gives the option for cold boot or wipe data.
3. ROM manager doesn't have CWM installed and when selecting boot into recovery, it simply restarts the device.
The device seems to be rooted though.
Thoughts?
Contact Asus through e-mail or phone call, give them the serial number and ask if it's unlocked.
Or see if you can download the OTA update, if it bricks, then it's unlocked.
If it does not give you the fastboot option together with wipe data and cold boot it is not unlocked
There should be a file called Unlock_Time.txt on your tablets memory.(at least I think that's created when you unlock the device)
Okay, I have tried three different ways to unlock my bootloader, and all of them are hanging at the same spot. I have tried fenguepays method, the htcdev method, and hasoon2000 all in one, and all of the hang while "waiting for device" when trying to get the identifier token. I have installed, and re-installed all of the sync drivers, and have tried to disable HTC sync like everyone says, but still all of this is to no avail. I was just wondering if someone could list all of the necessary drivers, and possibly tell me how to disable HTC sync, I'm not sure if I'm doing that right.
Are you in the bootloader when doing the fastboot commands? You have to be in the bootloader with the phone plugged in and it has to say fastboot usb. Also, I bet if you do a search on the method you'll find your answer...Its all over the forums.
My T-Mobile HTC ONE M7 had very low battery life and eventually died before I could get to my charger. When I plugged it in and attempted to turn it on this screen appeared on my phone:
*** TAMPERED ***
*** LOCKED ***
*** Security Warning ***
M7_UL PVT SHIP S-ON RH
HBOOT-1.44.0000
RADIO-4A.17.3250.20
OpenDSP-v31.120.274.0617
eMMC-boot
Jun 21 2013,20:19:45:9912
After doing quite a bit of research it appears as if my phone is stuck in a "bootloader loop". I left the phone on the charger last night and I have tried rebooting from this menu and even a factory reset however all the phone does is power off and return to this screen. I have NOT tampered with the phone, have not attempted to unlock or root it, or any other type of modification. I work for T-Mobile and know well enough that doing so would void any warranty. Which is why I am troubled by the fact that it states *** TAMPERED *** (otherwise I would have just performed a simple warranty exchange, however due to the tampered tag I have feeling they would reject my claim)
Any assistance would be greatly appreciated! Has this happened to anyone else with a critically low battery?
ohbeeasy said:
My T-Mobile HTC ONE M7 had very low battery life and eventually died before I could get to my charger. When I plugged it in and attempted to turn it on this screen appeared on my phone:
*** TAMPERED ***
*** LOCKED ***
*** Security Warning ***
M7_UL PVT SHIP S-ON RH
HBOOT-1.44.0000
RADIO-4A.17.3250.20
OpenDSP-v31.120.274.0617
eMMC-boot
Jun 21 2013,20:19:45:9912
After doing quite a bit of research it appears as if my phone is stuck in a "bootloader loop". I left the phone on the charger last night and I have tried rebooting from this menu and even a factory reset however all the phone does is power off and return to this screen. I have NOT tampered with the phone, have not attempted to unlock or root it, or any other type of modification. I work for T-Mobile and know well enough that doing so would void any warranty. Which is why I am troubled by the fact that it states *** TAMPERED *** (otherwise I would have just performed a simple warranty exchange, however due to the tampered tag I have feeling they would reject my claim)
Any assistance would be greatly appreciated! Has this happened to anyone else with a critically low battery?
Click to expand...
Click to collapse
I just exchanged my first One for case issues, but it also happened to crash to 0% battery several times (due to Google services wakelocks). In no instance did it crash hard enough to ruin the entire phone.
So...I'm going to be cynical first:
TAMPERED usually comes up once you have flashed a custom partition (recovery, so on...), and the Security Warning *typically* occurs when you try to re-lock your HTCDev-unlocked phone while you still have your custom recovery installed (you have to reflash a stock recovery before attempting a re-lock). If you had done something in the past and relocked your bootloader to bring it back to 'stock' without restoring your recovery, you would see things like this. The solution would be to unlock the bootloader again, flash stock recovery, then relock.
But since you have never done anything like that:
It's *possible* that your phone shut down in a very awkward/damaging way and now doesn't recognize the signature of your never-modified OS--that would require that there was damage or corruption across the non-OS partitions. If that's the case, then you could try to reload an official RUU yourself (if you had the appropriate software to do so, which you would need to get...), or take it to a T-Mobile location and ask them to try to push a new stock image to your phone. As long as you are able to see menu options under those warnings that you can navigate with the volume buttons, then the stock ROM should be able to reload all those 'tampered' partitions. If that doesn't work, though, you'd have to take your chances with T-Mobile support.
tuxkamen said:
I just exchanged my first One for case issues, but it also happened to crash to 0% battery several times (due to Google services wakelocks). In no instance did it crash hard enough to ruin the entire phone.
So...I'm going to be cynical first:
TAMPERED usually comes up once you have flashed a custom partition (recovery, so on...), and the Security Warning *typically* occurs when you try to re-lock your HTCDev-unlocked phone while you still have your custom recovery installed (you have to reflash a stock recovery before attempting a re-lock). If you had done something in the past and relocked your bootloader to bring it back to 'stock' without restoring your recovery, you would see things like this. The solution would be to unlock the bootloader again, flash stock recovery, then relock.
But since you have never done anything like that:
It's *possible* that your phone shut down in a very awkward/damaging way and now doesn't recognize the signature of your never-modified OS--that would require that there was damage or corruption across the non-OS partitions. If that's the case, then you could try to reload an official RUU yourself (if you had the appropriate software to do so, which you would need to get...), or take it to a T-Mobile location and ask them to try to push a new stock image to your phone. As long as you are able to see menu options under those warnings that you can navigate with the volume buttons, then the stock ROM should be able to reload all those 'tampered' partitions. If that doesn't work, though, you'd have to take your chances with T-Mobile support.
Click to expand...
Click to collapse
Thanks for your response, I probably should have mentioned that this device is not new, it was a replacement device through Asurion as the result of the insurance claim. So it sounds like whoever may have had the phone previously may have done some "tampering". The phone eventually cut off and has refused to turn on entirely. I went to T-Mobile and had an assistant manager memo the account with the information I provided above. I'm familiar with the bootloading screen but have never seen it not respond like mine was doing. I'm going to read up on the forums and see if I can become a little more familiar with the process so I can learn how to fix something like this in the future. Thanks for your quick reply!
ohbeeasy said:
Thanks for your response, I probably should have mentioned that this device is not new, it was a replacement device through Asurion as the result of the insurance claim. So it sounds like whoever may have had the phone previously may have done some "tampering". The phone eventually cut off and has refused to turn on entirely. I went to T-Mobile and had an assistant manager memo the account with the information I provided above. I'm familiar with the bootloading screen but have never seen it not respond like mine was doing. I'm going to read up on the forums and see if I can become a little more familiar with the process so I can learn how to fix something like this in the future. Thanks for your quick reply!
Click to expand...
Click to collapse
Try flashing the RUU. but since you are 1.44 can your revone and s-off first?
I would s-off before RUU.
Hello all,
I'm a little desparate with an error that occurred some time ago. My HTC One was updated and suddenly was encrypted.
Factory reset is not working and Recovery option is not working as well.
What I've done so far, after several forum messages:
1. I tried to execute the HTC dev (unlock_code.bin) hint in a way to unlock the bootloader, but with no success at all. I always get the "*** LOCKED ***" (S-ON) option enabled. Then, I saw a lot of messages in foruns regarding the HBOOT version 1.55 that is installed in my device. It seems that with this version, it's not possible to change the configuration to S-OFF.
2. No fastboot commands work, including all the flash writing options. All of them with signature failures. Again in this case it seems to be a issue related to S-ON/S-OFF.
3. I couldn't run the cellphone in USB debugging (after the boot, I'm presented with the infamous: "type password to decrypt storage", which obviously I don't have the password).
4. Runrunner didn't work.
At this very moment my device is a paperweight... Does anybody have another idea about what could be done in this case?
All my problems seem to be focused on my inability to change the option S-ON to S-OFF.
Any help is very appreciated!
Paulo