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 soft-bricked my ONE MAX after doing the update to Android 4.4.2 (Kitkat) yesterday.
It definitely turns on, but cant get past the htc one logo. Although, prior to that, screen goes green and pink.
Bootloader shows
*** TAMPERED***
*** RELOCKED***
T6UL PVT SHIP S-ON RH
HBOOT-2.46.0000
RADIO-4T.21.3218.01
OpenDSP-v33.120.274_T6.0829
QSC-
OS-1.19.708.2
eMMC-boot 2048MB
Oct 5 2013, 16:14:06.0
FYI, my phone isn't rooted. Although I did try in the past, I've used one click root (Didn't work) and the SUPER TOOL from Kwongger (Also didnt work for me). So I relocked the boot loader, couple of weeks its fine, just after updating to kitkat yesterday when it started happening.
Since its not rooted, I believe that's one of the reasons its not letting me flash a ROM or recovery. It's just saying device not found when using Squabbis kit.
I really need help, please.
Ok, You may follow these steps if your phone is an international version cause the rom in this post is for international version only. You may search the forum for a rom fitting your phone if it is not the international one but the procedures remain the same... ( Please note that my phone was not rooted too).
First of all
Last time I was facing the same problem. A special Thank to Pradeepvizz for his help.
So to install recovery, You need to unlock your bootloader AGAIN cause I also relocked my bootloader and getting the TAMPERED RELOCKED AND S ON. My phone freeze at boot on the HTC Screen.
1. Re - unlock your bootloader using the same unlock.bin file,( fyi, i've done it by htcdev.com), I think your adb and fastboot drivers working fine if you've been able to unlock before.
2. I follow the procedures of punk9 from - One Max Android Development > [Guide] S-OFF / Root.Your HTC One Max. to know how to install a recovery software using cmd prompt.
3. I've used TWRP as recovery (DON'T USE CWM, i'VE GOT MANY ISSUES WITH,and i was not the only one to get issues) downloaded from - One Max Original Android Development > [RECOVERY] TWRP 2.6.3.0 touch recovery posted by Flyhalf205.
4. I've downloaded and install a clean stock rom already rooted with original kernel which i downloaded from One Max Android Development > [ROM] HTC One MAX Stock ROM | ROOT | INTERNATIONAL | DEODEXED |1.54.401.1 posted by pradeepvizz.
5. After the rom successfully installed, reboot, (btw, it took more than 5mins to boot the first time for me, so if you find that it is screw at HTC Screen, be patient...)
After configuration (language setup, wifi connection, google account and so on), I've S-OFF my phone using firewater. PLEASE make sure your phone is connected to internet during the process. I've follow these step to S-OFF my phone: One Max General > Firewater S-OFF posted by pradeepvizz.
After, these procedures I've noticed, when booting in fastboot mode, that the TAMPERED STAMP and S-ON disappeared and change to UNLOCKED and S-OFF.
When I switch my phone on, I get the Red message (watermark) about the disclaimer and you may remove it by following this guide( I did not do it cause the red watermark does not matter to me) : One Max Android Development > ★ ☆ [MOD] Remove Red Text on Splash screen | hboot | Vzw/Spr/Int | 11-30-13 | ☆ ★ posted by santod040..
Althought I've unlocked my bootloader via htcdev, I've noticed that fingerprint sensor working fine but anyway you may search the forum to get the solution for this issue.
Hope It helps.
hellxprexx said:
Ok, You may follow these steps if your phone is an international version cause the rom in this post is for international version only. You may search the forum for a rom fitting your phone if it is not the international one but the procedures remain the same... ( Please note that my phone was not rooted too).
First of all
Last time I was facing the same problem. A special Thank to Pradeepvizz for his help.
So to install recovery, You need to unlock your bootloader AGAIN cause I also relocked my bootloader and getting the TAMPERED RELOCKED AND S ON. My phone freeze at boot on the HTC Screen.
1. Re - unlock your bootloader using the same unlock.bin file,( fyi, i've done it by htcdev.com), I think your adb and fastboot drivers working fine if you've been able to unlock before.
2. I follow the procedures of punk9 from - One Max Android Development > [Guide] S-OFF / Root.Your HTC One Max. to know how to install a recovery software using cmd prompt.
3. I've used TWRP as recovery (DON'T USE CWM, i'VE GOT MANY ISSUES WITH,and i was not the only one to get issues) downloaded from - One Max Original Android Development > [RECOVERY] TWRP 2.6.3.0 touch recovery posted by Flyhalf205.
4. I've downloaded and install a clean stock rom already rooted with original kernel which i downloaded from One Max Android Development > [ROM] HTC One MAX Stock ROM | ROOT | INTERNATIONAL | DEODEXED |1.54.401.1 posted by pradeepvizz.
5. After the rom successfully installed, reboot, (btw, it took more than 5mins to boot the first time for me, so if you find that it is screw at HTC Screen, be patient...)
After configuration (language setup, wifi connection, google account and so on), I've S-OFF my phone using firewater. PLEASE make sure your phone is connected to internet during the process. I've follow these step to S-OFF my phone: One Max General > Firewater S-OFF posted by pradeepvizz.
After, these procedures I've noticed, when booting in fastboot mode, that the TAMPERED STAMP and S-ON disappeared and change to UNLOCKED and S-OFF.
When I switch my phone on, I get the Red message (watermark) about the disclaimer and you may remove it by following this guide( I did not do it cause the red watermark does not matter to me) : One Max Android Development > ★ ☆ [MOD] Remove Red Text on Splash screen | hboot | Vzw/Spr/Int | 11-30-13 | ☆ ★ posted by santod040..
Althought I've unlocked my bootloader via htcdev, I've noticed that fingerprint sensor working fine but anyway you may search the forum to get the solution for this issue.
Hope It helps.
Click to expand...
Click to collapse
Super thanks for taking your time to reply to my post. I tried following this but it's not working. Only thing I can think of is because I was able to do a factory reset, so Im guessing maybe the usb debugging is/was disabled so its saying here that "Device not found". I cant unlock my bootloader anymore
timflores07 said:
Super thanks for taking your time to reply to my post. I tried following this but it's not working. Only thing I can think of is because I was able to do a factory reset, so Im guessing maybe the usb debugging is/was disabled so its saying here that "Device not found". I cant unlock my bootloader anymore
Click to expand...
Click to collapse
Impossible, it has to work.
timflores07 said:
Super thanks for taking your time to reply to my post. I tried following this but it's not working. Only thing I can think of is because I was able to do a factory reset, so Im guessing maybe the usb debugging is/was disabled so its saying here that "Device not found". I cant unlock my bootloader anymore
Click to expand...
Click to collapse
You don't need USB debugging to unlock, make sure your phone shows fastboot USB mode and that should be shown on the phone. You probably are in HBOOT and that is why it says device not found.
timflores07 said:
Super thanks for taking your time to reply to my post. I tried following this but it's not working. Only thing I can think of is because I was able to do a factory reset, so Im guessing maybe the usb debugging is/was disabled so its saying here that "Device not found". I cant unlock my bootloader anymore
Click to expand...
Click to collapse
I'm guessing a problem about your cable or your connection, or adb drivers. Are all the items needed in same folder? in directory c:/ ?? Adb, fastboot drivers and unlock.bin should be in same folder. No need to enable usb debugging when unlocking. it will take place only when flashing the rom or recovery. Did you follow the procedures from htcdev??
I did not give the procedures of unlocking bootloader as htcdev procedures are clear. check your connection, re install adb and fast boot drivers. use another usb port on your pc.
It must work.
I am curious to know how you are trying to install KitKat on a Sprint One Max as HTC has not yet released the update? If you are trying to use the release for the HTC One, that may be your problem. Rooting is fairly simple using HTCDev to unlock the bootloader, Use TWRP 2.6... and SuperSU 1.91. If you will need to be able to install a custom rom (none of which are available for Sprint yet), you will ultimately want S-Off. For this you will need to use the rumrunner tool as your One Max is using Hboot 2.46. Once you're S-Off you will be able to remove your tampered flag and re-lock which will once again enable your fingerprint scanner.
FYI if you were forced to factory reset, you will need to re-enable adb bugging in settings - developer options, AND disable fast boot in settings - power. Then start over from scratch.
hellxprexx said:
I'm guessing a problem about your cable or your connection, or adb drivers. Are all the items needed in same folder? in directory c:/ ?? Adb, fastboot drivers and unlock.bin should be in same folder. No need to enable usb debugging when unlocking. it will take place only when flashing the rom or recovery. Did you follow the procedures from htcdev??
I did not give the procedures of unlocking bootloader as htcdev procedures are clear. check your connection, re install adb and fast boot drivers. use another usb port on your pc.
It must work.
Click to expand...
Click to collapse
Bro, thanks I finally got it working. My girlfriend was actually the one who worked with it, followed your guide and other people's. Apparently, my htc drivers weren't updated thats why it wasnt working on my laptop. Again, thanks to the people that took their time to provide some help.
neodiver said:
I am curious to know how you are trying to install KitKat on a Sprint One Max as HTC has not yet released the update? If you are trying to use the release for the HTC One, that may be your problem. Rooting is fairly simple using HTCDev to unlock the bootloader, Use TWRP 2.6... and SuperSU 1.91. If you will need to be able to install a custom rom (none of which are available for Sprint yet), you will ultimately want S-Off. For this you will need to use the rumrunner tool as your One Max is using Hboot 2.46. Once you're S-Off you will be able to remove your tampered flag and re-lock which will once again enable your fingerprint scanner.
FYI if you were forced to factory reset, you will need to re-enable adb bugging in settings - developer options, AND disable fast boot in settings - power. Then start over from scratch.
Click to expand...
Click to collapse
I did it while checking for updates. Here's a screenie
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
andrdnl said:
Impossible, it has to work.
Click to expand...
Click to collapse
It's good to see "CONFIDENCE". Makes people try harder and more careful to follow instructions.
It's not confidence, it's based on some experince
Sent from my HTC One max using Tapatalk
andrdnl said:
It's not confidence, it's based on some experince
Sent from my HTC One max using Tapatalk
Click to expand...
Click to collapse
Best teacher is experience
timflores07 said:
Bro, thanks I finally got it working. My girlfriend was actually the one who worked with it, followed your guide and other people's. Apparently, my htc drivers weren't updated thats why it wasnt working on my laptop. Again, thanks to the people that took their time to provide some help.
Click to expand...
Click to collapse
Happy it helps bro!
HTC one max need help
andrdnl said:
Impossible, it has to work.
Click to expand...
Click to collapse
will it work for me
***TAMPERED***
***UNLOCKED***
T6WHL PVT SHIP S-ON
H-BOOT-2. 49 . 0000
RADIO 1.48.50.0425
OPENDSP-v33.120.274_T6.0829
QSC-
OS-3.02.651.5
eMMC-boot 2048MB
Apr 28 2014 15:06: 18.0
guys just pm me I know how to fix bricked phone Specially HTC one max....
guys just pm me I know how to fix bricked phone Specially HTC one max....
BootLoad Freezes
Hello.
I'm sorry I don't speak English very well. I'm French.
I have a HTC One max of origin Stock (no hack)
Overnight my phone will not start.
So I started by "Volume -" + "On"
The bootload load.
But if I chosen any choice FASTBOOT / RECOVERY / FACTORY REST Etc ...
The phone freezes.
If I stay pressed the power button restarts (HTC Green Screen make WHITE) but after black screen.
Black on the screen my computer detects a device: QHSUSB_DLOAD
I found lots of tutorial but for phone S-OFF or UNLOCKED while my phone is:
LOCKED
T6UL PVT SHIP ON S-HR
HBOOT-2.49.0000
RADIO 4T.36.3218.06
OpenDSP-v33.120.274_T6.0829
I have no ADB is housed and no USB debugging mode when the phone was working.
Can you help me...? :angel:
thank you in advance
Hello guys.
I need help. My device (T6UL) is bricked. Windows detect it how HS-USB QDLoader 9008. To unbrick him, I need full eMMc dump (/dev/block/mmcblk0).
Anybody can do it?
Sorry for my English, i am from Russia.
Hi all of a sudden after years of trouble free and non interfered with use just this morning my HTC One Max 803s will simply NOT switch on...it is fully charged and nothing that I do will get even a glimmer of life on the screen...the tiny green LED in the top left hand corner, which usually indicates a fully charged phone, is on permanently...I have taken out the SD card and SIM and replaced them as this was all that I could think of doing...HELP and HELP again...any ideas anyone???...thanx in advance for all your help...kind regards dizzy
dizzyblond said:
Hi all of a sudden after years of trouble free and non interfered with use just this morning my HTC One Max 803s will simply NOT switch on...it is fully charged and nothing that I do will get even a glimmer of life on the screen...the tiny green LED in the top left hand corner, which usually indicates a fully charged phone, is on permanently...I have taken out the SD card and SIM and replaced them as this was all that I could think of doing...HELP and HELP again...any ideas anyone???...thanx in advance for all your help...kind regards dizzy
Click to expand...
Click to collapse
Are you able to reboot into recovery mode via TWRP ?
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?