I haven't been using this device since last year because i got a new phone but now when i put the phone to charge it reboots into the bootloader and i get a tampered security warning.This i really strange because this is the only device that I didn’t do any modifications to, it even has a locked bootloader!
When i try to exit the bootloader it wont,and all the options bring me back to the main bootloader page! This device is some how bootlooped even through I haven’t done anything to it! If any one knows how to unbootloop it it would very much be appreciated.
Thanks.
Related
Ok guys I just move to Pennsylvania from Florida a few days ago and i was having problems with my data connection so i decided to call sprint and spend about an hr on the phone with costumer service try everything to restart my service and get better data, but nothing work so she tell me my last option was to take it back to sprint, so I decided to relock and to run the RRU, so i did the relocked on fastboot comand window and the phone restart to fasboot and now says ***relocked*** and under it it says ***security warning*** I try everything (rebbot, factory reset, power of ect.) all the the phone does is restart to splash screen and go back to fastboot plz i need help asap, thanks.
prboy25 said:
Ok guys I just move to Pennsylvania from Florida a few days ago and i was having problems with my data connection so i decided to call sprint and spend about an hr on the phone with costumer service try everything to restart my service and get better data, but nothing work so she tell me my last option was to take it back to sprint, so I decided to relock and to run the RRU, so i did the relocked on fastboot comand window and the phone restart to fasboot and now says ***relocked*** and under it it says ***security warning*** I try everything (rebbot, factory reset, power of ect.) all the the phone does is restart to splash screen and go back to fastboot plz i need help asap, thanks.
Click to expand...
Click to collapse
Nothing to worry about. Please read my previous reply to a similar problem. Remember: if the phone does something it is not a brick, and since it is Android it can be fixed. So cheer up!!!
Are you working off the latest Jewel RUU here:
http://forum.xda-developers.com/showthread.php?t=1655733
Here all available RUU for Jewel
http://www.filefactory.com/f/b6eb73c80cc97030/
How to unroot/unbrick device video: (Thanks to qbking77)
If you have unlocked device, you should lock it first with command fastboot oem lock, otherwise you won't be able to install RUU.
http://www.youtube.com/watch?v=NChdbyaHy3k
georgikol said:
Nothing to worry about. Please read my previous reply to a similar problem. Remember: if the phone does something it is not a brick, and since it is Android it can be fixed. So cheer up!!!
Click to expand...
Click to collapse
thanks try to run the RRU one more time and it works
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.
I am currently residing in a house with several others. Two days ago I left my phone (HTC ONE MAX SPRINT) on my desk and when I returned I found someone had tampered with it. The phone will only boot into Bootloader/Fastboot. When I try to goto recovery the htc logo screen appears for less than two seconds and then loops back to the fastboot screen.
Before anyone asks let me answer the following:
I don't know how it got to this state or what was done to get it here.
When I try to flash ANYTHING I get either signature verification denial, or remote denial
The screen says the following by order of appearance:
***TAMPERED***
***RELOCKED***
T6WHL PVT SHIP S-ON RH
H-Boot=2.40.0000
Radio-1.48.50.0109
OpenDsp=v.33.120.274_T6.0029
QSC=
OS=2/09/651/1
eMMc= boot 2048mb
PLEASE I NEED HELP ASAP family emergency. I spoke with HTC two days and they were very kind and sympathetic but the development team was supposed to contact me with a solution when they arrived at one but I have not heard anything.
I would appreciate any support immensely.
frodofied said:
I am currently residing in a house with several others. Two days ago I left my phone (HTC ONE MAX SPRINT) on my desk and when I returned I found someone had tampered with it. The phone will only boot into Bootloader/Fastboot. When I try to goto recovery the htc logo screen appears for less than two seconds and then loops back to the fastboot screen.
Before anyone asks let me answer the following:
I don't know how it got to this state or what was done to get it here.
When I try to flash ANYTHING I get either signature verification denial, or remote denial
The screen says the following by order of appearance:
***TAMPERED***
***RELOCKED***
T6WHL PVT SHIP S-ON RH
H-Boot=2.40.0000
Radio-1.48.50.0109
OpenDsp=v.33.120.274_T6.0029
QSC=
OS=2/09/651/1
eMMc= boot 2048mb
PLEASE I NEED HELP ASAP family emergency. I spoke with HTC two days and they were very kind and sympathetic but the development team was supposed to contact me with a solution when they arrived at one but I have not heard anything.
I would appreciate any support immensely.
Click to expand...
Click to collapse
Sounds to me step one try to s-off. Your boot loader is locked and you aren't s-off.
Sent from my HTC0P3P7 using xda app-developers app
frodofied said:
I am currently residing in a house with several others. Two days ago I left my phone (HTC ONE MAX SPRINT) on my desk and when I returned I found someone had tampered with it. The phone will only boot into Bootloader/Fastboot. When I try to goto recovery the htc logo screen appears for less than two seconds and then loops back to the fastboot screen.
Before anyone asks let me answer the following:
I don't know how it got to this state or what was done to get it here.
When I try to flash ANYTHING I get either signature verification denial, or remote denial
The screen says the following by order of appearance:
***TAMPERED***
***RELOCKED***
T6WHL PVT SHIP S-ON RH
H-Boot=2.40.0000
Radio-1.48.50.0109
OpenDsp=v.33.120.274_T6.0029
QSC=
OS=2/09/651/1
eMMc= boot 2048mb
PLEASE I NEED HELP ASAP family emergency. I spoke with HTC two days and they were very kind and sympathetic but the development team was supposed to contact me with a solution when they arrived at one but I have not heard anything.
I would appreciate any support immensely.
Click to expand...
Click to collapse
Go to HTC Dev and use your original unlock token to unlock the boot loader. Flash custom recovery. Boot to custom recovery. Then either side load a custom stock rom or put one on your physical SD card and flash it from there.
Sent from my Nexus 7 using Tapatalk
Thank you...
Hey! Thank you so much for the quick replies.
I must tell you that I have only moderate knowledge and experience when it comes to these issues.
Next, everything I try to do in terms of flashing returns with a signature not verified denial or a remote not allowed denial. I can't flash or otherwise access anything onto the phone.
frodofied said:
Hey! Thank you so much for the quick replies.
I must tell you that I have only moderate knowledge and experience when it comes to these issues.
Next, everything I try to do in terms of flashing returns with a signature not verified denial or a remote not allowed denial. I can't flash or otherwise access anything onto the phone.
Click to expand...
Click to collapse
That's why you need unlock token from HTC Dev. If this is truly your phone, you must know how to do that as this phone is relocked. Meaning it was unlocked before. The failure to fastboot flash anything is due to the relocked boot loader.
Sent from my Nexus 7 using Tapatalk
Alright guys, Ive been trying to fix my friends DNA i guess from what he said is that he had a system update happen on his phone and it would just stay on the "HTC Quite Brilliant" Page. I tried a factory reset, and that didn't do anything, I went into recovery to wipe cache partition. I also tried wipe data/factory reset from recovery as well as hboot. so i got adb and i plugged the phone in while on fastboot. "adb devices" Shows nothing its just blank underneath the listed devices. So i figured that the drivers wont install i installed htc sync manager as advertised has the supporting drivers. Htc sync manager reads the device but doesn't say its a DNA it just says that its rom number. I tried to go to fastboot and put a previous dated RUU on but it had a error and just couldn't do anything with the phone. So now i went into the recovery and behind the menu screen it says "updating software from verizon wireless" but theres a issue with that is that the sim card in it isnt activated anymore so theres no data going to that phone if it is updating and if it downloaded the os to the phone it should be wiped since i did a factory reset 3 times and wiped cache 3 times as well.
So What i think is wrong is that:
I need usb Debugging on
S is on
Drivers wont install properly
I may need a active sim card to pass the updating?
MoNARUDO PVT S-ON RH
HBOOT-1.57.0000
Radio-1.01.01.1112
OpenDSP-v10.120.274.0520
OS-4.09.605.1
eMMC-boot 2048MB
Mar 13 2014, 19:19:14.0
I really hope that you guys can help me out thank you!
HTVdev
I tried to unlock the device to see if this would help out and i got it connected and i went and i got the token for the device and went to get the tocken and it came back with a error code
Error Code: 160.
Error Reason: MID Not Allowed.
Can someone please help me out here?
I was missing android sdk and i installed android sdk, and my device will read in adb but when i got to flash a udate it will read signature error. but im not using the word update im using "fastboot flash hboot hboot.img" and so forth and its not working i still cant get the hboot to unlock. please help me figure out if its possible to fix this phone im really determined to fix it and i need alittle bit of help.
Unfortunately, unless you can boot into the ROM, you cannot unlock this phone. I suggest contacting HTC support and let them know the update soft bricked the device and since you cannot unlock it, you need their help in getting it to boot again. HTC is very good when it comes to support, even for phones that are out of warranty. Support staff have been instructed to fix any m7 even if out of warranty period for the camera issue (talked to a rep personally on this issue today when making small talk). I am sure if their update borked your phone and it hasn't been tampered, they will fix it free of charge. What's the worse they can say, no?
Sent from my One using XDA Free mobile app
I contacted there support 2 times on the phone and once trying to live chat and i got hung up on twice.. so im at loss here
Im really not happy with htc they cant tell me anything to any cause to why there update would cause the softbrick on the phone itself did anyone else have a issue with 4.09 update bricking your phone?? and did anyone find a solution for it?
I was flashing a google play edition rom onto my phone and when i did that i also had the harman karmon speakers flashed and my phone went into the HTC boot screen. The screen never loaded into the phone so i waited for it to die. After it died i went into the bootloader and tried to boot into recovery to wipe the phone, but when i got into the bootloader my phone said CID incorrect
"press the power button to restart". I did this and it just does the same thing, never loads into the phone and always says CID incorrect. please help. My phone is rooted, has s-off, and unlocked bootloader. any suggestions would be appreciated
If you installed HK by the following thread, it says right there it doesn't work with GPE: http://forum.xda-developers.com/showthread.php?t=2737498
Or did you follow some other process?
Is anything else showing up on the bootloader screen, is it trying to install an update? I don't think I've seen this before, where it says incorrect CID in bootloader, unless its trying to install something.