Hi all,
My Incredible S now refuses to boot and I can't flash it. Here's the story:
It was a factory unlocked device with S-ON. AlphaRevX successfully managed to get rid of that, and GingerBreak rooted the device in the first attempt. It was working fine until, for a stupid reason, I decided to go back to factory ROM. So I downloaded one from another thread here and ended up with famous yellow triangle. Removed the battery and the problem started.
It keeps showing HTC logo then restarts.
I've tried many ROMS but all of them ended up with Customer ID error. I see "Security Warning" message on the Bootloader screen and S-ON is back.
Here's all the information I can gather from bootloader screen:
VIVO PVT SHIP S-ON RL
HBOOT 1.09.0000
RADIO 3805.04.03.27_M
I'd appreciate any kind of help.
Regards,
Hossein
I am in the exact same boat and I made a thread about it here:
http://forum.xda-developers.com/showthread.php?t=1136041
Read through the posts to find out what you can do to fix (its not much).
Let me know if you can actually fix it...
Shojaee said:
Hi all,
My Incredible S now refuses to boot and I can't flash it. Here's the story:
It was a factory unlocked device with S-ON. AlphaRevX successfully managed to get rid of that, and GingerBreak rooted the device in the first attempt. It was working fine until, for a stupid reason, I decided to go back to factory ROM. So I downloaded one from another thread here and ended up with famous yellow triangle. Removed the battery and the problem started.
It keeps showing HTC logo then restarts.
I've tried many ROMS but all of them ended up with Customer ID error. I see "Security Warning" message on the Bootloader screen and S-ON is back.
Here's all the information I can gather from bootloader screen:
VIVO PVT SHIP S-ON RL
HBOOT 1.09.0000
RADIO 3805.04.03.27_M
I'd appreciate any kind of help.
Regards,
Hossein
Click to expand...
Click to collapse
Whenever you get an invalid CID or customer ID when trying to flash a ROM, it means that you need to create a goldcard to flash the ROM because your phone may be S-OFF, but it is not carrier unlocked.
You situation is not unique however. You are the 3rd thread that has posted the 'Security Warning' and getting set back to S-ON. You may want to check out the other threads to see if they were ever able to get it resolved.
ClaudiuJer said:
I am in the exact same boat and I made a thread about it here:
http://forum.xda-developers.com/showthread.php?t=1136041
Read through the posts to find out what you can do to fix (its not much).
Let me know if you can actually fix it...
Click to expand...
Click to collapse
Hi,
Thanks for the link. I actually cannot try XTC Clip as I don't have it. Gold Card is not an option as I simply don't know what is the CID of my device.
I tried to flash mine with stock RUU, but this time got "Bootloader version" error which means I can't downgrade. It is an Arabic ROM (the latest OTA update for my device named "OTA_Vivo_Gingerbread_S_HTC_ARA_2.30.415.1-2.12.415.5") so I guess I need a stock Gingerbread Arabic ROM for HTC Incredible S, which is not available AFAIK.
Regards,
Hossein
tpbklake said:
Whenever you get an invalid CID or customer ID when trying to flash a ROM, it means that you need to create a goldcard to flash the ROM because your phone may be S-OFF, but it is not carrier unlocked.
You situation is not unique however. You are the 3rd thread that has posted the 'Security Warning' and getting set back to S-ON. You may want to check out the other threads to see if they were ever able to get it resolved.
Click to expand...
Click to collapse
Hi,
It is S-ON and carrier unlocked but either way I believe I need to know my CID to create a gold card (please correct me if I'm wrong). As the device is not booting up, I can't read the CID, unless there's a way to read it in bootloader mode.
Regards,
Hossein
I have the same problem,I flash the eng-hboot and then i used goldcard to flash the ruu,the bootloader was s-on and when i power on,it only enter fastboot mode,some one know how to do ? jtag now can't fix it
Related
So got the Incredible S in the beginning of July and was very happy with it, beat the hell out of my old HD2 who got bricked Desided not to root this one cause it was already android and i didnt want to break the warranty. But then the 2.3.3 update came and i didnt recieve text and calls was dismissed. (it is an own thread about this issue on the forums) so i desided to try a rom from XDA to see if this could help solve the issue. It did not but i rooted the phone (S-off right?) and used it with GSM only.. today i talked with HTC support and got a hold of the RUU_Vivo_HTC_WWE_1.36.405.1_Radio_Radio_20.23.30.0 802U_38.02.01.11_M_release_172670_signed.. the cusomter support guy uploaded it and i installed it with the USB cable.. the installer said everything went fine.. the phone reebots.. boots to the HTC logo screen and turns off again.. and keeps on going in the same cycle..
I can get into bootloader, but when i press "power" to choose recovery it goes straight to the white htc screen again and reebots.. what to do now? Is this one dead also?
Tried rename RUU to PG32IMG and put it on the memory card.. still no luck it says "Bootloader - Bypasses"
"TP - Bypassed"
"TP - Bypassed"
Why? And still no luck tried with two signed RUU's now.. The bootloader says
Vivo PVT SHIP S-OFF RL
HBOOT 6.13.1002
At least i want all the Revolutionary stuff gone.. Any idea? Im out of ideas right now.. Oh geez, it booted the 2.1.3 RUU.. nice.
But why would not the other room work? This is the one i have to get workin.. Any ideas?
Does the RUU got a radio in it? Please share this RUU cause I believe this is not avaible anywhere. I would give it a try then and report if I have issues.
Sent from my HTC Incredible S using xda premium
Yes I think it can be a radio conflict too, perhaps you downgraded it.
Here you go Please give a report if it work on your device
I also want to gain S-ON on my Incredible, used AlphaRevX Beta to get the S-OFF but i need it to be S-ON again, and i cant really fint the information on how to do it. These forums are amazing but very hard to navigate true, and find the information you are looking for.
Was thinking... You said you are S-OFF and then installed the 1.36 RUU. Possibly this RUU or ROM needs an older bootloader. Cause the bootloader cannot be overwritten (I assume you used Alpharev), the installation is aborted.
The newer RUU accepts the current bootloader and therefore is being installed.
I think, when you first downgrade your Hboot to the one that can be overwritten, the RUU should work and you can enjoy Froyo again!
So did it work ?
Sent from my xxx using Tapatalk .
wallytax said:
Was thinking... You said you are S-OFF and then installed the 1.36 RUU. Possibly this RUU or ROM needs an older bootloader. Cause the bootloader cannot be overwritten (I assume you used Alpharev), the installation is aborted.
The newer RUU accepts the current bootloader and therefore is being installed.
I think, when you first downgrade your Hboot to the one that can be overwritten, the RUU should work and you can enjoy Froyo again!
Click to expand...
Click to collapse
How to do this? Do i need to S-ON first? Or?
HTC Holiday - At&t Vivid
***RELOCKED***
HBOOT-1.85.0024
S-ON RL
CID: CWS_001
Version Installed:
3.26.502.54 710RD
Kernel Version:
3.0.16-gea0e914
[email protected] #1
Baseband:
3.02.4740.14_34.22.701040.19L
Build:
3.25.502.54 CL302737
Issue:
I am trying to return to stock so I can sell this phone. I RELOCKED it using the "fastboot oem relock" and got the famous error message that it failed with "too many links". But it still shows that it is relocked.
When running the RUU with the phone booted it errors out with error 155. When I try and run it through fastboot it just sits on "Sending" and doesn't go anywhere. I had it sit for 12 hours yesterday and it didn't budge.
I've tried these two files, which are the exact same I know...
htc_vivid_att_RUU_3.26.502.56_US.exe
RUU_HOLIDAY_ICS_35_S_Cingular_US_3.26.502.56_Radio_3.02.4740.14_34.22.701040.19_release_246712_signed.exe
I need to re-flash something to it, whenever the damn thing boots up (even after a factory reset) it says "Updating Android". And it says it every time. I can't sell a phone that does that.
I have tried to unlock and lock again. It's been while since I have done this, but I thought it had something to do with the error while re-locking, or the HBOOT version.
I've read some other places that I need to get S-OFF first to be able to return to stock, WTF, unless something has change, I've never had to do that before with this device to return to stock.
**EDIT**
I just tried to go into the recovery to see if there was one still installed and it flashed back to the fastboot screen and now says ***SECURITY WARNING*** under the relock. I have not seen that before.
Squeaky369 said:
HTC Holiday - At&t Vivid
***RELOCKED***
HBOOT-1.85.0024
S-ON RL
CID: CWS_001
Version Installed:
3.26.502.54 710RD
Kernel Version:
3.0.16-gea0e914
[email protected] #1
Baseband:
3.02.4740.14_34.22.701040.19L
Build:
3.25.502.54 CL302737
Issue:
I am trying to return to stock so I can sell this phone. I RELOCKED it using the "fastboot oem relock" and got the famous error message that it failed with "too many links". But it still shows that it is relocked.
When running the RUU with the phone booted it errors out with error 155. When I try and run it through fastboot it just sits on "Sending" and doesn't go anywhere. I had it sit for 12 hours yesterday and it didn't budge.
I've tried these two files, which are the exact same I know...
htc_vivid_att_RUU_3.26.502.56_US.exe
RUU_HOLIDAY_ICS_35_S_Cingular_US_3.26.502.56_Radio_3.02.4740.14_34.22.701040.19_release_246712_signed.exe
I need to re-flash something to it, whenever the damn thing boots up (even after a factory reset) it says "Updating Android". And it says it every time. I can't sell a phone that does that.
I have tried to unlock and lock again. It's been while since I have done this, but I thought it had something to do with the error while re-locking, or the HBOOT version.
I've read some other places that I need to get S-OFF first to be able to return to stock, WTF, unless something has change, I've never had to do that before with this device to return to stock.
**EDIT**
I just tried to go into the recovery to see if there was one still installed and it flashed back to the fastboot screen and now says ***SECURITY WARNING*** under the relock. I have not seen that before.
Click to expand...
Click to collapse
First of all, I must say, THANKS for posting so many details! That makes it much easier to fully understand your issue. I wish everyone would be so concise.
Next, these are errors I have never seen.. This Security Warning is news to me... I wonder if you should maybe try to re-flash the original HBOOT... That is the most risky of all flashes, so I'd maybe wait for someone who has experienced this issue to pipe up before attempting it.
It sounds to me that HBOOT is where your problem lies though. I hope someone else can be of more help on this issue.
ess.boyer said:
First of all, I must say, THANKS for posting so many details! That makes it much easier to fully understand your issue. I wish everyone would be so concise.
Next, these are errors I have never seen.. This Security Warning is news to me... I wonder if you should maybe try to re-flash the original HBOOT... That is the most risky of all flashes, so I'd maybe wait for someone who has experienced this issue to pipe up before attempting it.
It sounds to me that HBOOT is where your problem lies though. I hope someone else can be of more help on this issue.
Click to expand...
Click to collapse
Thank you! I've been around this site for around 4 years now and it's EXTREMELY annoying when searching for answers when someone just posts:
"i cant flash"
Or whatever...
As for the actual issue, that's what I was thinking. There was something awhile back I thought I had read about that version of the HBOOT being an issue. So, hopefully someone around here can help out. I searched for it but I couldn't find anything. So either I am thinking of another phone or it's just lost in the depths of the unknown.
Squeaky369 said:
Thank you! I've been around this site for around 4 years now and it's EXTREMELY annoying when searching for answers when someone just posts:
"i cant flash"
Click to expand...
Click to collapse
Amen to that!
As for the actual issue, that's what I was thinking. There was something awhile back I thought I had read about that version of the HBOOT being an issue. So, hopefully someone around here can help out. I searched for it but I couldn't find anything. So either I am thinking of another phone or it's just lost in the depths of the unknown.
Click to expand...
Click to collapse
I think your best bet may be to just try reflashing the HBOOT. Check Hasoons All-in-one tool kit as I believe it contains the original HBOOT and the one that comes with the S-OFF tools. If it's not there, you should be able to find it somewhere around the forum. Maybe there's a link in the superguide.
Hopefully with a fresh HBOOT, you can get locked, and the RUU will work again. I have flashed the RUU a few times, and each time for me, relocking the bootloader worked fine.
It's worth a whirl.
http://forum.xda-developers.com/showthread.php?t=1416836
SECOND OPTION (PH39IMG.zip flash)
- Put this file for AT&T or this file for Rogers on a microSD card as is (it should be named PH39IMG.zip)
- Power down the phone, insert microSD and boot back into bootloader (power button + vol down)
- It should automatically find the zip file and flash the stock image (this includes recovery, system, everything stock.)
- If you returned to stock because of a bug or issue, and want to root again, make sure to go back and follow the steps PRECISELY to perm root, flash CWM, flash a ROM, flash a kernel, etc. Remember, flash ROM IMMEDIATELY after flashing the kernel
Click to expand...
Click to collapse
ess.boyer said:
Amen to that!
I think your best bet may be to just try reflashing the HBOOT. Check Hasoons All-in-one tool kit as I believe it contains the original HBOOT and the one that comes with the S-OFF tools. If it's not there, you should be able to find it somewhere around the forum. Maybe there's a link in the superguide.
Hopefully with a fresh HBOOT, you can get locked, and the RUU will work again. I have flashed the RUU a few times, and each time for me, relocking the bootloader worked fine.
It's worth a whirl.
Click to expand...
Click to collapse
Ripped the original HBOOT out of the RUU that I had from HTC.
When I try and flash though I get this:
---------------------------------------------------------------------------------------------------------
C:\Android>fastboot flash hboot hboot.nb0
sending 'hboot' (1023 KB)... OKAY [ 0.297s]
writing 'hboot'... FAILED (remote: not allowed)
finished. total time: 0.614s
---------------------------------------------------------------------------------------------------------
I don't need to be S-OFF to flash the HBOOT do I? I unlocked the bootloader again, so that is not what is causing the issue.
Brand New said:
http://forum.xda-developers.com/showthread.php?t=1416836
Click to expand...
Click to collapse
That's the first thread I went through when starting this
I have actually been looking for the PH39IMG.zip file for At&t because that's how I used to do this...
But the file in that link isn't there anymore. It seems that every search I do and find where someone has posted it, it's been removed because of copyright infringement or some other stupid political BS.
Got it.
Created my own PH39IMG.zip using the RUU I got from HTC and got the HBOOT updated and everything returned to stock.
Thank you for the assistance everyone.
Ha! Rocking! Glad you're back up and running.
Squeaky369 said:
Got it.
Created my own PH39IMG.zip using the RUU I got from HTC and got the HBOOT updated and everything returned to stock.
Thank you for the assistance everyone.
Click to expand...
Click to collapse
I am having the exact same issue. Any chance you could share that PH39IMG.zip you made or explain how you did it?
I'll be putting the links up for the PH39IMG.zip in the next hour or so
---------- Post added at 11:36 AM ---------- Previous post was at 11:30 AM ----------
For both AT&T and Rogers Ripped straight from the RUU
I heard that android 4.3 came out today so I wanted to convert my HTC One to a Google Play edition. I unlocked the boot loader through HTC dev. I then tried to S-OFF but that didn't work because I got errors. So I factory reset the phone and when I turned it back on the WiFi didn't work. It just says error. I tried dialing *#*#526#*#* but nothing came up. I then tried to go into recover but It just shows up a red triangle with an exclamation point. The boot loader says *** TAMPERED *** *** UNLOCKED ***
I'm shaking right now. I am really scared that I just wasted $500 on this phone. Can anyone please help me. This is serious. :crying:
EDIT: I leave on vacation in 3 days so this is really urgent. There are also some bugs where when I download apps they are invalid or they cant be saved to the sd card.
Woror said:
I heard that android 4.3 came out today so I wanted to convert my HTC One to a Google Play edition. I unlocked the boot loader through HTC dev. I then tried to S-OFF but that didn't work because I got errors. So I factory reset the phone and when I turned it back on the WiFi didn't work. It just says error. I tried dialing *#*#526#*#* but nothing came up. I then tried to go into recover but It just shows up a red triangle with an exclamation point. The boot loader says *** TAMPERED *** *** UNLOCKED ***
I'm shaking right now. I am really scared that I just wasted $500 on this phone. Can anyone please help me. This is serious. :crying:
EDIT: I leave on vacation in 3 days so this is really urgent. There are also some bugs where when I download apps they are invalid or they cant be saved to the sd card.
Click to expand...
Click to collapse
reflash recovery and then do a full wipe and proceed to flash arhd google edition or some other rom
xnknown said:
reflash recovery and then do a full wipe and proceed to flash arhd google edition or some other rom
Click to expand...
Click to collapse
I'm sorry but I forgot to mention the fact that I am new to the world of android modificarion. If you could please explain what you mean or refer me to a tutorial, that would be amazing.
http://forum.xda-developers.com/showthread.php?t=2265618
full guide, you can download the custom recovery referred to in the guide at the link below
http://goo.im/devs/OpenRecovery/m7/
xnknown said:
http://forum.xda-developers.com/showthread.php?t=2265618
full guide, you can download the custom recovery referred to in the guide at the link below
http://goo.im/devs/OpenRecovery/m7/
Click to expand...
Click to collapse
So do you know if you have to be S-Off to change the RUU? I wanted to follow this tutorial. http://htc-one.wonderhowto.com/how-...with-bootloader-recovery-ota-updates-0148068/[1]
EDIT: I have a different model apparently. Mine is PN0713000, it says you're suppose to have PN0712000. To change it it also says you're suppose to have S-OFF but I keep getting errors with both Moonshine and revone.
Woror said:
So do you know if you have to be S-Off to change the RUU? I wanted to follow this tutorial. http://htc-one.wonderhowto.com/how-...with-bootloader-recovery-ota-updates-0148068/[1]
Click to expand...
Click to collapse
you can flash a RUU with s-on too, but you need to have matching CID..
herwegan said:
you can flash a RUU with s-on too, but you need to have matching CID..
Click to expand...
Click to collapse
I don't even have the correct model id, mine is PN0713000, it says you're suppose to have PN0712000. To change it it also says you're suppose to have S-OFF but I keep getting errors with both Moonshine and revone.
Hi guys.
First time posting, but have used the site extensively over the past 6-8 months. I have an AT&T HTC One. I had unlocked it, s-off, rooted, installed GPe, and decided to go back. The ROM I went back to was supposed to be MY stock ROM, but it turns out it was unbranded 4.2.2. I thought nothing of it, and as of yesterday, had sold my phone on ebay. I decided to wipe my phone to get ready to ship. I locked my bootloader and went to s-on, but when I went to factory reset, I got a "security warning" and it won't reboot into recovery. I've tried everything- tried to re-unlock it with htcdev, which freezes at the bootloader. I've tried to unlock via revone, since I still have root (root checker verified this to be the case), but get the -6 error when using terminal emulator in ROM Toolbox, and get the same error when doing it via adb commands. I've tried probably 50 different things about 10 different times, and am about to pull my hair out! I've read and searched probably hundreds of threads over the past 24 hours. Trying to flash stock RUU (the exe) just freezes as well. Any help would be appreciated! Let me know what info you need from me.
Android 4.2.2
Hboot 1.44
Software number 2.24.401.8
HTC SDK API level 5.34
Kernel version 3.4.10-g28df0d6 [email protected] #1 SMP PREEMPT
Baseband version 4A.18.3263.15_10.38h.1157.04L
Build number 2.24.401.8 CL235216 release-keys
Thanks guys! Awesome community!
I think you need to read Vomers guide and install using the ADB Method
http://forum.xda-developers.com/showthread.php?t=2365506&page=4
but also Read Mike 1986's Return to stock Guide before - this will ensure you are aware of what needs doing before you start to do it
http://forum.xda-developers.com/showthread.php?t=2265618
:fingers-crossed::fingers-crossed::fingers-crossed::fingers-crossed:
The search option would have found these for you and saved some time and heartache :highfive:
L0rdNels0n said:
I think you need to read Vomers guide and install using the ADB Method
http://forum.xda-developers.com/showthread.php?t=2365506&page=4
Click to expand...
Click to collapse
I have (almost) the same problem as OP: bootloader (HBOOT 1.44) shows "locked", "tampered" and "S-ON". The radio is apparently broken and I want a new unit, so I installed mike1986's "stock 4.2.2" ROM, because htc1guru.com is broken and androidruu.com apparently has corrupt RUU downloads (every RUU I've tried fails miserably, and extracted rom.zips don't work either). It's rooted, with SuperSU. I relocked and S-ONed the bootloader with revone, but then found a stock backup and tried to unlock/S-OFF so I could install TWRP back.
Unfortunately for me (and OP), revone -P fails with error -6. revone -s 0 -u fails with error -1. revone -t reports success, but the tampered flag remains there. Trying to flash TWRP with a market app freezes Android. Trying to unlock the bootloader with HTCDev reports success in fastboot, but the unlock prompt never shows up, and the bootloader freezes.
Read again: revone fails. That guide, as well as the other 4 or so similar ones floating around, are useless in this case.
If anyone has any ideas (or an HTC EastEurope RUU download that doesn't fail), I'm open to hearing them.
AndyM3 said:
I have (almost) the same problem as OP: bootloader (HBOOT 1.44) shows "locked", "tampered" and "S-ON". The radio is apparently broken and I want a new unit, so I installed mike1986's "stock 4.2.2" ROM, because htc1guru.com is broken and androidruu.com apparently has corrupt RUU downloads. It's rooted, with SuperSU. I relocked and S-ONed the bootloader with revone, but then found a stock backup and tried to unlock/S-OFF so I could install TWRP back.
Unfortunately for me (and OP), revone -P fails with error -6. revone -s 0 -u fails with error -1. revone -t reports success, but the tampered flag remains there. Trying to flash TWRP with a market app freezes Android. Trying to unlock the bootloader with HTCDev reports success in fastboot, but the unlock prompt never shows up, and the bootloader freezes.
Read again: revone fails. That guide, as well as the other 4 or so similar ones floating around, are useless in this case.
If anyone has any ideas (or an HTC EastEurope RUU download that doesn't fail), I'm open to hearing them.
Click to expand...
Click to collapse
What's the date of your hboot? If it's after May 2013, it might be a patched version (applies to AT&T and T-Mobile), otherwise revone will work.
Read here: http://forum.xda-developers.com/showthread.php?t=2431515 for the prerequisites to get S-Off.
Try that, and report back and we'll go from there.
PS: keep S-Off, no need to ever to back S-On even for repair because some devices are shipped S-Off. The repair center can't prove you've done anything to your phone, unless they see "LOCKED / RELOCKED / TAMPERED"
nkk71 said:
What's the date of your hboot? If it's after May 2013, it might be a patched version (applies to AT&T and T-Mobile), otherwise revone will work.
Read here: http://forum.xda-developers.com/showthread.php?t=2431515 for the prerequisites to get S-Off.
Try that, and report back and we'll go from there.
PS: keep S-Off, no need to ever to back S-On even for repair because some devices are shipped S-Off. The repair center can't prove you've done anything to your phone, unless they see "LOCKED / RELOCKED / TAMPERED"
Click to expand...
Click to collapse
Bootloader date is May 3, 2013. It's a downloaded "stock unmodified" 1.44 HBOOT. I'm not in the US.
On the other hand, I'm on a 4.2.2 ROM right now. Should I try to downgrade? If yes, can anyone point me in the direction of an HTC RUU that actually works? (CID is HTC__032)
AndyM3 said:
Bootloader date is May 3, 2013. It's a downloaded "stock unmodified" 1.44 HBOOT. I'm not in the US.
On the other hand, I'm on a 4.2.2 ROM right now. Should I try to downgrade? If yes, can anyone point me in the direction of an HTC RUU that actually works? (CID is HTC__032)
Click to expand...
Click to collapse
May 3 is good, revone should work. If it's not working on your ROM now, try downgrading to a 4.1.2 ROM to try to make it work.
For the RUU, have you looked here: http://forum.xda-developers.com/showthread.php?t=2158151
Otherwise try to get @Mike1986 odexed ROM, it worked a couple of days ago for someone else: http://forum.xda-developers.com/showthread.php?t=2457354 (read last post)
nkk71 said:
May 3 is good, revone should work. If it's not working on your ROM now, try downgrading to a 4.1.2 ROM to try to make it work.
For the RUU, have you looked here: http://forum.xda-developers.com/showthread.php?t=2158151
Otherwise try to get @Mike1986 odexed ROM, it worked a couple of days ago for someone else: http://forum.xda-developers.com/showthread.php?t=2457354 (read last post)
Click to expand...
Click to collapse
I downloaded a 1.20.401 RUU (should be 4.1.2, probably), and I am on mike1986's odexed ROM right now. I'd downgrade, but how? I can't install a custom recovery.
Edit: RUU exited with a "bootloader version error". Could I have downloaded a corrupt HBOOT or something? revone gave success messages about five times now, but the bootloader still says "LOCKED" and "S-ON".
AndyM3 said:
the bootloader still says "LOCKED" and "S-OFF".
Click to expand...
Click to collapse
So S-Off achieved great.
What's still the problem?
nkk71 said:
So S-Off achieved great.
What's still the problem?
Click to expand...
Click to collapse
Typo, sorry. It's S-ON.
AndyM3 said:
Typo, sorry. It's S-ON.
Click to expand...
Click to collapse
Hi Andy,
I just re-read your original post, and am getting a bit confused cause you said "bootloader (HBOOT 1.44) shows "locked", "tampered" and "S-ON"." you mean RELOCKED?
Probably best if you post your "fastboot getvar all" (remove IMEI and serial number) , full details of the ROM you're using, and a screenshot of your bootloader.
As for "HTCDev reports success in fastboot, but the unlock prompt never shows up", maybe you should try the process from the beginning again and get a new unlocktocken.
nkk71 said:
Hi Andy,
I just re-read your original post, and am getting a bit confused cause you said "bootloader (HBOOT 1.44) shows "locked", "tampered" and "S-ON"." you mean RELOCKED?
Probably best if you post your "fastboot getvar all" (remove IMEI and serial number) , full details of the ROM you're using, and a screenshot of your bootloader.
As for "HTCDev reports success in fastboot, but the unlock prompt never shows up", maybe you should try the process from the beginning again and get a new unlocktocken.
Click to expand...
Click to collapse
I did mean "locked". I used revone -l to restore the lock status. On the other hand, now I accidentally installed HBOOT 1.54 instead (figured the bootloader may be broken and installed a 2.24 firmware package). I tried HTCDev Unlock twice (the whole process), and it... still doesn't work. To be more specific, fastboot flash unlocktoken reports success, but the next fastboot command, whatever that may be (getvar, reboot, etc), errors out with something to the effect of "could not load custom splash". Trying to flash any sort of different HBOOT (older/newer) complains about signatures, or maybe that's just my downloads.
Of course, revone doesn't work with 1.54, so I'm pretty much ****ed. Might as well take the damn thing back to Orange.
AndyM3 said:
I did mean "locked". I used revone -l to restore the lock status. On the other hand, now I accidentally installed HBOOT 1.54 instead (figured the bootloader may be broken and installed a 2.24 firmware package). I tried HTCDev Unlock twice (the whole process), and it... still doesn't work. To be more specific, fastboot flash unlocktoken reports success, but the next fastboot command, whatever that may be (getvar, reboot, etc), errors out with something to the effect of "could not load custom splash". Trying to flash any sort of different HBOOT (older/newer) complains about signatures, or maybe that's just my downloads.
Of course, revone doesn't work with 1.54, so I'm pretty much ****ed. Might as well take the damn thing back to Orange.
Click to expand...
Click to collapse
Sometimes a factory reset can help with the unlock token, but since you're on 1.54 now it would make little difference.
Sorry & good luck
Sent from my HTC One using xda app-developers app
Yep. I'm in exactly the same boat. Actually, I am on 1.44 HBOOT, dated May 3rd, and none of the available options worked. And yes, I've tried the links included in subsequent posts. And I'm "locked" via same way as above. Since I was selling the phone and trying to revert to stock, my only option was to manually erase everything and send it off. I couldn't do a factory reset, because it just kicked me to bootloader with a "security warning" error. Couldn't install older RUU, as it would just hang at the HTC black screen with no green progress bar.
AndyM3 said:
Bootloader date is May 3, 2013. It's a downloaded "stock unmodified" 1.44 HBOOT. I'm not in the US.
On the other hand, I'm on a 4.2.2 ROM right now. Should I try to downgrade? If yes, can anyone point me in the direction of an HTC RUU that actually works? (CID is HTC__032)
Click to expand...
Click to collapse
Same problem
Hey guys, I have a same problem, and I'm pissed off and depressed :crying:
I tried GPE, but then I wanted to go back to Sense, and then everything went wrong. I have HBOOT 1.54, S-ON, RELOCKED, TAMPERED. I can't unlock the bootloader, although cmd writes that writing was successful, and the phone still says "RELOCKED". I can't get to system and recovery because always get into bootloader with the message "Security Warning". I can't upload any RUU, recovery, nothing ... always cmd writes "failed", in case RUU (1.28.401.7 - my regional which should work) writes "Error 155".
Please guys, help me. I do not know what to do and I'm clueless.
PlaviiCZ said:
Hey guys, I have a same problem, and I'm pissed off and depressed :crying:
I tried GPE, but then I wanted to go back to Sense, and then everything went wrong. I have HBOOT 1.54, S-ON, RELOCKED, TAMPERED. I can't unlock the bootloader, although cmd writes that writing was successful, and the phone still says "RELOCKED". I can't get to system and recovery because always get into bootloader with the message "Security Warning". I can't upload any RUU, recovery, nothing ... always cmd writes "failed", in case RUU (1.28.401.7 - my regional which should work) writes "Error 155".
Please guys, help me. I do not know what to do and I'm clueless.
Sorry for my bad english, but I hope hope you'll understand.
Click to expand...
Click to collapse
You have google CID and s-on and relocked .. your pretty much screwed near as i can tell. did you try fastboot oem unlock ?
clsA said:
You have google CID and s-on and relocked .. your pretty much screwed near as i can tell. did you try fastboot oem unlock ?
Click to expand...
Click to collapse
Yeah, I'm dumbass...Yes, I did, and nothing...just "failed" in cmd. Should I try again to tell you, what is in cmd exactly written?
EDIT: Please help (
No one knows anything?
Hi guys, I have a completely stock HTC one m7 that one day decided to get stuck in a boot loop. I've tried going into the bootloader(?) and doing a factory reset, as well as accessing the recovery menu with no success. It just goes back into the loop.
I've been told that flashing it(?) in fastboot might help? I honestly have very little idea what to do when it comes to this, so I was wondering if you guys would be able to help me, and explain in fairly simple terms what I need to do.
I've looked through similar threads but most of them seem to be problems relating to already modded phones. I hope you guys can help!
Thanks.
Milo89 said:
Hi guys, I have a completely stock HTC one m7 that one day decided to get stuck in a boot loop. I've tried going into the bootloader(?) and doing a factory reset, as well as accessing the recovery menu with no success. It just goes back into the loop.
I've been told that flashing it(?) in fastboot might help? I honestly have very little idea what to do when it comes to this, so I was wondering if you guys would be able to help me, and explain in fairly simple terms what I need to do.
I've looked through similar threads but most of them seem to be problems relating to already modded phones. I hope you guys can help!
Thanks.
Click to expand...
Click to collapse
You can try a RUU (Rom Update Utility) we need the information in the bootloader screen to help you find the correct one for your device
Carrier / software version / hboot / and any other information you can give about the phone
clsA said:
You can try a RUU (Rom Update Utility) we need the information in the bootloader screen to help you find the correct one for your device
Carrier / software version / hboot / and any other information you can give about the phone
Click to expand...
Click to collapse
Ok, on the bootloader screen it says:
*** LOCKED ***
M7_UL PVT SHIP S-ON RH
HBOOT-1.57.000
RADIO-4T.28.3218.04
OpenDSP-v32.120.274.0909
OS-6.16.61.1
eMMC-boot 2048MB
Aug 22 2014, 18:39:28.0
Click to expand...
Click to collapse
Thanks for the fast reply!
*edit* oh and my carrier is T-mobile in the UK
Milo89 said:
Ok, on the bootloader screen it says:
Thanks for the fast reply!
*edit* oh and my carrier is T-mobile in the UK
Click to expand...
Click to collapse
There is no RUU for 6.16.61.1 version and nothing that I can find online (nandroid backup or other useful files). You might want to unlock your bootloader at HTCDev.com, flash TWRP recovery 2.6.3.3 and then flash a custom rom like ARHD 84 and see if your device can boot.
I had the exact same issue, so I ran a RUU that had a slightly newer firmware since I had HBOOT 1.57 and S-ON. it apparently took the update but went straight back to a boot loop. Called HTC, they said there's most likely corrupted sectors in the boot portion and the device can't be repaired. Hope your problem isn't quite that severe.