Database Develop

[Q] Yellow Triangle, Security Warning, Customer ID error

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

[Q] HELP!!! Unroot Attempt - Different Fastboot than the normal

Hello All,
Here's my dilemma. I successfully rooted my HTC One (AT&T), and was recently attempting to unroot it. I followed this one here http://forum.xda-developers.com/showthread.php?t=2182823. Since I have the AT&T version, I downloaded the first one the list found there, however it wouldn't verify. Next I downloaded the AT&T AIO here http://forum.xda-developers.com/showthread.php?t=2242635. I was able to use that to figure out according to the info it displayed that I actually needed the Google Edition one from the previous link. I thought that was weird since I dont have the google edition one. But when I fast booted that one, everything appeared to go through with a hitch.....Until it restarted.
After it restarted, I only have a black screen. No start up. I restarted the phone and went into the bootloader and to my surprise, the bootloader was black instead of the normal white.
I've tried several RUUs found here http://www.androidruu.com/index.php?developer=M7
I've tried both the exe and flashing the zip.
I have no clue what to try next. Please XDA, your my only hope.

Are you s-off? I would assume so if you've been able to run multiple RUUs and are getting weird signature results. What mods/roms did you do to your phone before you started all this?
If you can get to bootloader, you're not bricked. You're on the 3.06 GE hboot, but it's not clear why you can't boot up.

iElvis said:
Are you s-off? I would assume so if you've been able to run multiple RUUs and are getting weird signature results. What mods/roms did you do to your phone before you started all this?
If you can get to bootloader, you're not bricked. You're on the 3.06 GE hboot, but it's not clear why you can't boot up.
Click to expand...
Click to collapse
----From the top of bootloader down----
***Tampered***
***Relocked***
M7_UL PVT SHIP S-ON RH
HBOOT-1.54.0000
RADIO-4A.18.3263.15
OpenDSO-V31.120.274.0617
(in red) OS-3.03.1700.10 (3.06.1700.10)
eMMC-boot 2048MB
Aug 1 2013, 18:48:40.0
Does that help at all?

Tylegn said:
----From the top of bootloader down----
***Tampered***
***Relocked***
M7_UL PVT SHIP S-ON RH
HBOOT-1.54.0000
RADIO-4A.18.3263.15
OpenDSO-V31.120.274.0617
(in red) OS-3.03.1700.10 (3.06.1700.10)
eMMC-boot 2048MB
Aug 1 2013, 18:48:40.0
Does that help at all?
Click to expand...
Click to collapse
Were you ever s-off? You should not have been able to run that GE RUU on an s-on AT&T phone.

iElvis said:
Were you ever s-off? You should not have been able to run that GE RUU on an s-on AT&T phone.
Click to expand...
Click to collapse
I hate to say.... I have no clue if I was before or not. I just relocked it like the directions told me. Is there any saving me? Also, thank you for your quick responses.

Tylegn said:
I hate to say.... I have no clue if I was before or not. I just relocked it like the directions told me. Is there any saving me? Also, thank you for your quick responses.
Click to expand...
Click to collapse
You bought it new? Not used from someone else? If so, it was always s-on.
You're on GE firmware somehow. It's possible you have a conflict with your model or carrier ID. Can you run through the exact steps you took when you started trying to unroot? Exactly which files you used and how you ran them?

iElvis said:
You bought it new? Not used from someone else? If so, it was always s-on.
You're on GE firmware somehow. It's possible you have a conflict with your model or carrier ID. Can you run through the exact steps you took when you started trying to unroot? Exactly which files you used and how you ran them?
Click to expand...
Click to collapse
I received the phone directly from HTC through a sell to earn contest.
Not sure if it matters much but I unlocked the bootloader through HTC Dev.
To unroot,
1) Put phone in bootloader with fastboot
2) Relocked bootloader
3) fastboot oem rebootRUU
4) fastboot flash zip 2.24.401.1.zip (failed)
Used one of the AIOs that stated I had modelid: PN0712000 and cidnum: CWS__001. That when I grabbed the GE version.
5) fastboot flash zip 3.06.1700.10.zip
6) Phone finished, rebooted to a black screen
7) Rebooted into bootloader (Which is now black instead of white)
8) Sad ever since....

Where did you get that GE zip? I'm not sure why the AIO toolkit told you that you were GE but I'd like to check the file.
I suspect the problem is that you have 4.3 GE firmware but a 4.1 OS. Flashing a 4.2 or 4.3 rom might fix.

ageldea consider
iElvis said:
Where did you get that GE zip? I'm not sure why the AIO toolkit told you that you were GE but I'd like to check the file.
I suspect the problem is that you have 4.3 GE firmware but a 4.1 OS. Flashing a 4.2 or 4.3 rom might fix.
Click to expand...
Click to collapse
This is where I got:
http://forum.xda-developers.com/showthread.php?t=2182823
I'll need a step by step from you if you can because, I'm having a h3ll of a time trying to get anything to flash.

Tylegn said:
This is where I got:
http://forum.xda-developers.com/showthread.php?t=2182823
I'll need a step by step from you if you can because, I'm having a h3ll of a time trying to get anything to flash.
Click to expand...
Click to collapse
:facepalm: Just realized the issue.
Your bootloader is locked and you still have custom recovery installed, I'm guessing. Can you select Recovery in bootloader and see what happens? If you're still with TWRP or CWM, that's the issue; you can't boot locked on custom recovery.
You have to unlock again or flash the stock recovery in fastboot. Unlocking will wipe your phone, unfortunately.
Flashing recovery in fastboot is easy if you have the stock recovery file.
fastboot flash recovery [filename].img

iElvis said:
:facepalm: Just realized the issue.
Your bootloader is locked and you still have custom recovery installed, I'm guessing. Can you select Recovery in bootloader and see what happens? If you're still with TWRP or CWM, that's the issue; you can't boot locked on custom recovery.
You have to unlock again or flash the stock recovery in fastboot. Unlocking will wipe your phone, unfortunately.
Flashing recovery in fastboot is easy if you have the stock recovery file.
fastboot flash recovery [filename].img
Click to expand...
Click to collapse
You are right about having the recovery option in the bootloader but when I try to select that option, Android shows up with the spinning blue thing in it's stomach, then it dies with a red triangle.
I'll try flashing the recovery again. After I find a stock recovery img. LOL
Thanks again!!!
I'll post what's going on as I do it.

iElvis said:
:facepalm: Just realized the issue.
Your bootloader is locked and you still have custom recovery installed, I'm guessing. Can you select Recovery in bootloader and see what happens? If you're still with TWRP or CWM, that's the issue; you can't boot locked on custom recovery.
You have to unlock again or flash the stock recovery in fastboot. Unlocking will wipe your phone, unfortunately.
Flashing recovery in fastboot is easy if you have the stock recovery file.
fastboot flash recovery [filename].img
Click to expand...
Click to collapse
Found the stock recovery. Attempted to flash it and got this:
sending 'recovery' <16303 KB>...
OKAY [ 1.786s]
writing 'recovery'...
<bootloader> signature checking...
FAILED <remote: 12 signature verify fail>
finished. total time: 3.178s
Is there a different way I should be doing it.
HTC One has the Gray HTC logo chilling on the screen...
Also tried in normal fastboot mode...

Tylegn said:
You are right about having the recovery option in the bootloader but when I try to select that option, Android shows up with the spinning blue thing in it's stomach, then it dies with a red triangle.
I'll try flashing the recovery again. After I find a stock recovery img. LOL
Thanks again!!!
I'll post what's going on as I do it.
Click to expand...
Click to collapse
Actually, I think that red triangle is stock recovery. I think to get to the recovery options you press power+vol up on that screen. But it doesn't matter because clearly you're not on custom recovery.
I don't see that 3.06 firmware package in the OP of that thread. Can you find the post you found it attached to?

iElvis said:
Actually, I think that red triangle is stock recovery. I think to get to the recovery options you press power+vol up on that screen. But it doesn't matter because clearly you're not on custom recovery.
I don't see that 3.06 firmware package in the OP of that thread. Can you find the post you found it attached to?
Click to expand...
Click to collapse
If you click on the download link in that post for the GE it downloads as that 3.06 firmware..
Also, not sure if it was smart or not but I unlocked the bootloader again to see if it would fix the conflicts you mentioned before. Haven't tried flashing anything yet...
ADD: I just successfully flashed the stock recovery.... Too scared to muck something up so I'll waif for your superior guidance!
Thanks again

Tylegn said:
If you click on the download link in that post for the GE it downloads as that 3.06 firmware..
Also, not sure if it was smart or not but I unlocked the bootloader again to see if it would fix the conflicts you mentioned before. Haven't tried flashing anything yet...
Click to expand...
Click to collapse
I forgot Mike updated that link.
Okay, I see what you did now. You've essentially upgraded your phone to a GE because the android-info.txt in this official firmware matched your MID and CID; that allowed it to run. The problem is that you can't go back now because you're s-on. Your phone won't boot because you have the GE kernel installed but I assume a Sense rom.
This should be easy to fix. You can flash custom recovery now that you've unlocked, then flash a custom rom. This will get your kernel and rom consistent again and you should be able to boot.
Unrooting is a different story. You can't go back to the stock configuration you had when you got the phone without s-off, which you can't get on 1.54 hboot. I'm afraid you're stuck until AT&T releases 4.3 and you can run a RUU.

iElvis said:
I forgot Mike updated that link.
Okay, I see what you did now. You've essentially upgraded your phone to a GE because the android-info.txt in this official firmware matched your MID and CID; that allowed it to run. The problem is that you can't go back now because you're s-on. Your phone won't boot because you have the GE kernel installed but I assume a Sense rom.
This should be easy to fix. You can flash custom recovery now that you've unlocked, then flash a custom rom. This will get your kernel and rom consistent again and you should be able to boot.
Unrooting is a different story. You can't go back to the stock configuration you had when you got the phone without s-off, which you can't get on 1.54 hboot. I'm afraid you're stuck until AT&T releases 4.3 and you can run a RUU.
Click to expand...
Click to collapse
So no getting my white bootloader back till next release? That's ok.
However, how do I flash the custom ROM. I got the customer recovery going but I don't know how to get the ROM on there.... Flashing isn't working, still getting signature failures.
Sorry

Tylegn said:
So no getting my white bootloader back till next release? That's ok.
However, how do I flash the custom ROM. I got the customer recovery going but I don't know how to get the ROM on there.... Flashing isn't working, still getting signature failures.
Sorry
Click to expand...
Click to collapse
You can only run a later firmware. When the signed 4.3 Sense firmware is released (it may be there now), you should be able to run that and get back the stock HTC bootloader.
You need to adb push the rom file onto your phone. There is a tutorial for doing it here: http://forum.xda-developers.com/showthread.php?t=2317986

iElvis said:
You can only run a later firmware. When the signed 4.3 Sense firmware is released (it may be there now), you should be able to run that and get back the stock HTC bootloader.
You need to adb push the rom file onto your phone. There is a tutorial for doing it here: http://forum.xda-developers.com/showthread.php?t=2317986
Click to expand...
Click to collapse
Thank you so much! I believe I can take it from here.....Until I brick my phone when the signed 4.3 comes out. LOL
Until next time. Thanks iElivis you are a BADA$$!:good::good::good:

[Q] Help! Problems to unroot M7_UL!

Hello everyone,
This is my fisrt time writing in this forum, hope you guys can share some knowledge with me. Here is my issue:
I bought a HTC One to a guy a few weeks ago with barely no use. The thing is that I didn´t know at that time that the device was rooted with the MaximusHD. When I realized about it I reset my phone to factory settings and the new 4.3 3.22.1540.1 got installed. Thought it was ok but it is still doing some weird things so I decided to unroot the device to stock, also for warranty porpuses.
The problem comes when I try to download the RUU for my device due to I cannot find it. Should I do it through other method? Do I have to S-off to downgrade and install the RUU 1.29?
My phone is the following:
M7_UL PVT Ship S-On RH
Baseband 4A.17.3250.14
Hboot 1.54.0000
OpenDSP v31.120.274.0617
It is the european unlocked/international version bought in Spain.
I would really appreciate if someone could give a hand on this and guide me in through this process. I was an iPhone guy and now I'm freaking lost.
Thanks so much!

kikinhorap said:
Hello everyone,
This is my fisrt time writing in this forum, hope you guys can share some knowledge with me. Here is my issue:
I bought a HTC One to a guy a few weeks ago with barely no use. The thing is that I didn´t know at that time that the device was rooted with the MaximusHD. When I realized about it I reset my phone to factory settings and the new 4.3 3.22.1540.1 got installed. Thought it was ok but it is still doing some weird things so I decided to unroot the device to stock, also for warranty porpuses.
The problem comes when I try to download the RUU for my device due to I cannot find it. Should I do it through other method? Do I have to S-off to downgrade and install the RUU 1.29?
My phone is the following:
M7_UL PVT Ship S-On RH
Baseband 4A.17.3250.14
Hboot 1.54.0000
OpenDSP v31.120.274.0617
It is the european unlocked/international version bought in Spain.
I would really appreciate if someone could give a hand on this and guide me in through this process. I was an iPhone guy and now I'm freaking lost.
Thanks so much!
Click to expand...
Click to collapse
Your bootloader should already be unlocked, so simply get S-OFF using Rumrunner, then follow this guide.

Answer
attanasi0 said:
Your bootloader should already be unlocked, so simply get S-OFF using Rumrunner, then follow this guide.
Click to expand...
Click to collapse
Thanks for the reply. I've tried to s-off my htc but it hasnt worked. So I downloaded the recovery stock version and after installing it, the device told me that my phone doesnt appear to be rooted and if i wanted to install supersu, i declined and then made a recovery. Phone looks like unrooted, although within the bootloader it still shows "tampered" and "Unlocked". The recovery mode that the phone had installed has disappeared so I dont know what to do now, should I continue to s-off the device and then put it down to hboot 1.44 and follow the unroot guide???
I would like to make sure my device is unrooted in order to gain warranty privilages just in case i need to send out my phone to htc...
Thanks!

kikinhorap said:
Thanks for the reply. I've tried to s-off my htc but it hasnt worked. So I downloaded the recovery stock version and after installing it, the device told me that my phone doesnt appear to be rooted and if i wanted to install supersu, i declined and then made a recovery. Phone looks like unrooted, although within the bootloader it still shows "tampered" and "Unlocked". The recovery mode that the phone had installed has disappeared so I dont know what to do now, should I continue to s-off the device and then put it down to hboot 1.44 and follow the unroot guide???
I would like to make sure my device is unrooted in order to gain warranty privilages just in case i need to send out my phone to htc...
Thanks!
Click to expand...
Click to collapse
You don't really have a choice, unless you have the RUU for your phone. Can you post the results of "fastboot getvar all" so we can try to figure out what to do.

A
attanasi0 said:
You don't really have a choice, unless you have the RUU for your phone. Can you post the results of "fastboot getvar all" so we can try to figure out what to do.
Click to expand...
Click to collapse
I've attached the results in a jpg file. The only thing that has changed is the baseband...it went up to 4A.20.3263.16

kikinhorap said:
I've attached the results in a jpg file. The only thing that has changed is the baseband...it went up to 4A.20.3263.16
Click to expand...
Click to collapse
Just a quick note here, "version-main: <blank>" I never like that.
BTW, when posting "fastboot getvar all" it's preferably to remove IMEI and s/n; we don't need to see that.
You should probably get s-off as @attanasi0 suggested and then run a "HTC__304" downgrade RUU. (You can only downgrade if you're S-Off)
Just my two cents

nkk71 said:
Just a quick note here, "version-main: <blank>" I never like that.
BTW, when posting "fastboot getvar all" it's preferably to remove IMEI and s/n; we don't need to see that.
You should probably get s-off as @attanasi0 suggested and then run a "HTC__304" downgrade RUU. (You can only downgrade if you're S-Off)
Just my two cents
Click to expand...
Click to collapse
Im sorry about the pic, I'll edit my msg later. Im trying to s-off but it fails everytime. Dunno what to try now...
In regards to the "version main", I tried lots of times but it was blank all of them, dunno why. Some of you guys know what the reason could be?

kikinhorap said:
Im sorry about the pic, I'll edit my msg later. Im trying to s-off but it fails everytime. Dunno what to try now...
In regards to the "version main", I tried lots of times but it was blank all of them, dunno why. Some of you guys know what the reason could be?
Click to expand...
Click to collapse
When you boot to bootloader does it also show nothing in OS (7th line down or so)? Can you remember the last OTA you took?

nkk71 said:
When you boot to bootloader does it also show nothing in OS (7th line down or so)? Can you remember the last OTA you took?
Click to expand...
Click to collapse
Right, it shows just OS- but nothing else...when i bought it the guy had installed the MaximusHD 13 and I updated through OTA to the MaximusHD 20 but wasnt going smooth so I reset it to factory settings and It installed the JB 4.3 (3.22.1540.1).
Today after trying to s-off without success, I downloaded the recovery stock version for the rom I had and flashed it and the recovery mode that I had before disappeared and the baseband upgraded to 4A.20...instead of the 4A.17 that I had before that. Did the guy who sold me the htc messed it up? is there anything I can do to set my device to factory settings?
Thanks for the help guys! I appreciate it!

kikinhorap said:
Right, it shows just OS- but nothing else...when i bought it the guy had installed the MaximusHD 13 and I updated through OTA to the MaximusHD 20 but wasnt going smooth so I reset it to factory settings and It installed the JB 4.3 (3.22.1540.1).
Today after trying to s-off without success, I downloaded the recovery stock version for the rom I had and flashed it and the recovery mode that I had before disappeared and the baseband upgraded to 4A.20...instead of the 4A.17 that I had before that. Did the guy who sold me the htc messed it up? is there anything I can do to set my device to factory settings?
Thanks for the help guys! I appreciate it!
Click to expand...
Click to collapse
Well from the information available, you have
- hboot 1.54
- m7_ul
- PN0710000
- CID HTC__304
this would lead me to assume you have a 2.24.401.x based phone.
I would try to get one of the following Guru Reset ROM:
2.24.401.8 : http://www.htc1guru.com/dld/guru_reset_m7_2-24-401-8-zip/
2.24.401.1 : http://www.htc1guru.com/dld/guru_reset_m7_2-24-401-1-zip/
flash one of them in recovery, then follow the rumrunner steps to try to achieve S-Off.
If that is successful, then you can downgrade back to stock, using this RUU (exe): http://www.htc1guru.com/dld/ruu_m7_...1-27_10-31-1131-05_release_310878_signed-exe/
check your "fastboot getvar all" after that.
Once you've done all that you can use revone (or http://forum.xda-developers.com/showthread.php?t=2477792) to remove "TAMPERED"
and also revone (or http://forum.xda-developers.com/showthread.php?t=2475914) to get you're phone "LOCKED" if you so wish
Keep S-Off !!
PS: hit the thanks button if someone has helped you
Awaiting your feedback

nkk71 said:
Well from the information available, you have
- hboot 1.54
- m7_ul
- PN0710000
- CID HTC__304
this would lead me to assume you have a 2.24.401.x based phone.
I would try to get one of the following Guru Reset ROM:
2.24.401.8 : http://www.htc1guru.com/dld/guru_reset_m7_2-24-401-8-zip/
2.24.401.1 : http://www.htc1guru.com/dld/guru_reset_m7_2-24-401-1-zip/
flash one of them in recovery, then follow the rumrunner steps to try to achieve S-Off.
If that is successful, then you can downgrade back to stock, using this RUU (exe): http://www.htc1guru.com/dld/ruu_m7_...1-27_10-31-1131-05_release_310878_signed-exe/
check your "fastboot getvar all" after that.
Once you've done all that you can use revone (or http://forum.xda-developers.com/showthread.php?t=2477792) to remove "TAMPERED"
and also revone (or http://forum.xda-developers.com/showthread.php?t=2475914) to get you're phone "LOCKED" if you so wish
Keep S-Off !!
PS: hit the thanks button if someone has helped you
Awaiting your feedback
Click to expand...
Click to collapse
Thanks for the help. I have downloaded the Rom you gave me the link for but I dunno how to flash it due to I lost access to the teamwin recovery mode and when I click recovery onto the bootloader it goes to a black screen with a caution simbol in red and I have to reboot it.
I have tried with the goomanager to flash that rom but it doesnt let me. Any advice in this regard? I can tell goomanager to find an open recovery script (openrecovery-twrp-2.6.1.0-m7.img), should i do this? Or Im gonna end up with a bricked phone?
Thanks!

kikinhorap said:
Thanks for the help. I have downloaded the Rom you gave me the link for but I dunno how to flash it due to I lost access to the teamwin recovery mode and when I click recovery onto the bootloader it goes to a black screen with a caution simbol in red and I have to reboot it.
I have tried with the goomanager to flash that rom but it doesnt let me. Any advice in this regard? I can tell goomanager to find an open recovery script (openrecovery-twrp-2.6.1.0-m7.img), should i do this? Or Im gonna end up with a bricked phone?
Thanks!
Click to expand...
Click to collapse
"black screen with a caution simbol in red" that's stock recovery, you need to flash back a custom recovery. download (if you dont have one) from the xda threads, then enter bootloader (shut off phone, hold POWER + VOLDOWN) enter FASTBOOT, connect to PC and it should change to FASTBOOT USB
then
fastboot erase cache
fastboot flash recovery <name of recovery>.img
fastboot erase cache
fastboot reboot-bootloader
-> enter RECOVERY
then "install ZIP" in Aroma, deselect "stock recovery" so you don't need to flash it again.

nkk71 said:
"black screen with a caution simbol in red" that's stock recovery, you need to flash back a custom recovery. download (if you dont have one) from the xda threads, then enter bootloader (shut off phone, hold POWER + VOLDOWN) enter FASTBOOT, connect to PC and it should change to FASTBOOT USB
then
fastboot erase cache
fastboot flash recovery <name of recovery>.img
fastboot erase cache
fastboot reboot-bootloader
-> enter RECOVERY
then "install ZIP" in Aroma, deselect "stock recovery" so you don't need to flash it again.
Click to expand...
Click to collapse
Is the one I posted it before (openrecovery-twpr-2.6....img) ok? or should I install a different one?
Thanks for the help man, I would be even more lost than Im now without your help!

kikinhorap said:
Is the one I posted it before (openrecovery-twpr-2.6....img) ok? or should I install a different one?
Thanks for the help man, I would be even more lost than Im now without your help!
Click to expand...
Click to collapse
No problem, TWRP you mentioned should work just fine. It's the same as installing a custom ROM. I havent used TWRP but it should say something like "install zip", then find the zip and flash away.
Hopefully, that will give you a chance to successfully run rumrunner; remember to read and follow the instructions to the letter!
Good luck and keep us posted (fingers crossed)

nkk71 said:
No problem, TWRP you mentioned should work just fine. It's the same as installing a custom ROM. I havent used TWRP but it should say something like "install zip", then find the zip and flash away.
Hopefully, that will give you a chance to successfully run rumrunner; remember to read and follow the instructions to the letter!
Good luck and keep us posted (fingers crossed)
Click to expand...
Click to collapse
Well I installed the custom recovery, then flashed the stock rom 2.24.401.8 as you told me. Once I did that I ran rumrunner successfully gainning S-off.
Now I have to run the RUU but the one you suggested me is the "RUU M7 UL JB 50 HTC Europe 1.28.401.7 Radio 4A.13.3231.27 10.31.1131.05 Release 310878" but my radio is 4A.17.3250.14_10.39.1150.04L. Should I try to install it anyways? I've taken a look at the rest of RUUs and none fits my features...
btw every time I flash the stock version at the end it tells me that my phone doesnt appear to be rooted and if i want to install supersu, i always say no and after that my recovery always goes to stock, i guess it is normal, isnt it?

kikinhorap said:
Well I installed the custom recovery, then flashed the stock rom 2.24.401.8 as you told me. Once I did that I ran rumrunner successfully gainning S-off.
Click to expand...
Click to collapse
Excellent :good:
kikinhorap said:
btw every time I flash the stock version at the end it tells me that my phone doesnt appear to be rooted and if i want to install supersu, i always say no and after that my recovery always goes to stock, i guess it is normal, isnt it?
Click to expand...
Click to collapse
That's normal, dont worry about it.
kikinhorap said:
Now I have to run the RUU but the one you suggested me is the "RUU M7 UL JB 50 HTC Europe 1.28.401.7 Radio 4A.13.3231.27 10.31.1131.05 Release 310878" but my radio is 4A.17.3250.14_10.39.1150.04L. Should I try to install it anyways? I've taken a look at the rest of RUUs and none fits my features...
Click to expand...
Click to collapse
Go ahead and flash it, it will downgrade everything (now possible thanks to S-Off), and you will then receive the latest OTA package(s) to get to the most current version including radio.

nkk71 said:
Excellent :good:
That's normal, dont worry about it.
Go ahead and flash it, it will downgrade everything (now possible thanks to S-Off), and you will then receive the latest OTA package(s) to get to the most current version including radio.
Click to expand...
Click to collapse
Done!!!!! Sweet!! it worked just fine! Tampered disappeared and bootloader only shows unlocked. I have to relock it, havent I? That wouldnt mess up with my carrier right? It is just for locking the bootloader, isnt it?
Well many many thanks for your help, I couldnt have done it without it and I have learnt so much through the process Soon I'll be ready to re-root the phone again and try some custom roms hehe
Peace and greetings from Spain!

kikinhorap said:
Done!!!!! Sweet!! it worked just fine! Tampered disappeared and bootloader only shows unlocked. I have to relock it, havent I? That wouldnt mess up with my carrier right? It is just for locking the bootloader, isnt it?
Well many many thanks for your help, I couldnt have done it without it and I have learnt so much through the process Soon I'll be ready to re-root the phone again and try some custom roms hehe
Peace and greetings from Spain!
Click to expand...
Click to collapse
you should set it to LOCKED not RELOCKED using revone or http://forum.xda-developers.com/showthread.php?t=2475914
keep S-Off !!
anyway, don't why anybody would want to be on stock ROM

nkk71 said:
you should set it to LOCKED not RELOCKED using revone or http://forum.xda-developers.com/showthread.php?t=2475914
keep S-Off !!
anyway, don't why anybody would want to be on stock ROM
Click to expand...
Click to collapse
Hey! I have tried to lock it but after typing adb shell I get this "[email protected]:\ $" instead of the # that you are getting. I've tried to type "su" after that but it says that the command cannot be found. Also, when I type the code "echo -ne..." it says that I have permission denied so dunno what to do now...
Im asking in the lock/unlock threat but they just told me that its because im not rooted and that i have to install a recovery and install superuser in order to be able to introduce the code, dont really understand why I have to root it afer unrooted it :S

kikinhorap said:
Hey! I have tried to lock it but after typing adb shell I get this "[email protected]:\ $" instead of the # that you are getting. I've tried to type "su" after that but it says that the command cannot be found. Also, when I type the code "echo -ne..." it says that I have permission denied so dunno what to do now...
Im asking in the lock/unlock threat but they just told me that its because im not rooted and that i have to install a recovery and install superuser in order to be able to introduce the code, dont really understand why I have to root it afer unrooted it :S
Click to expand...
Click to collapse
You should have LOCKED it before running the RUU, because that's what made you loose root.
So before proceeding, can you give me an update of your status:
bootloader: locked/relocked/unlocked?
tampered?
ROM?
"fastboot getvar all" (remove IMEI and s/n)

{Q} Regarding 'Tampered' flag

I'm trying to regain full stock of my AT&T device and I followed a tutorial on gaining 100% stock with no traces of tampering. I go through all the steps in order, returning to stock CID, flashing stock RUU through fastboot, then returning to S-on and relocking the bootloader. The last step was removing the "tampered" stamp in the fastboot screen but I can't get rid of the thing. In fact, I originally, when i first modded, got rid of it, but after regaining S-on, the tampered came up again. So I ran the last command for removing it. But it won't go away. I tried it the manual way, running ADB commands, then i tried it with the All in One Toolkit. I almost bricked the thing trying different ways, including unlocking the boot and regaining S-off again. luckily i found a small tutorial for fixing that.
This is what I used to go back to stock: http://forum.xda-developers.com/showthread.php?t=2358738
This i used to unbrick: http://forum.xda-developers.com/showthread.php?t=2301007
And after unbricking, I used the toolkit. And both times, after gaining S-on following the exact steps, the tampered comes up, and I can't get rid of it. As it stands now, my phone is Locked w/ tampered, S-on, and i put my CID back to CWS__001 with the toolkit, but it isn't showing up in Fastboot. I'm going to see if i can go back and manually write that CID back in then going to bed. Any help would be appreciated. I need to return this phone very soon. Thank you.
Edit: I ran getvar and it gave me the correct CID, despite it not showing in fastboot. I'm not screwing with it anymore til i can get some advice.....

whitetiger_0603 said:
I'm trying to regain full stock of my AT&T device and I followed a tutorial on gaining 100% stock with no traces of tampering. I go through all the steps in order, returning to stock CID, flashing stock RUU through fastboot, then returning to S-on and relocking the bootloader. The last step was removing the "tampered" stamp in the fastboot screen but I can't get rid of the thing. In fact, I originally, when i first modded, got rid of it, but after regaining S-on, the tampered came up again. So I ran the last command for removing it. But it won't go away. I tried it the manual way, running ADB commands, then i tried it with the All in One Toolkit. I almost bricked the thing trying different ways, including unlocking the boot and regaining S-off again. luckily i found a small tutorial for fixing that.
This is what I used to go back to stock: http://forum.xda-developers.com/showthread.php?t=2358738
This i used to unbrick: http://forum.xda-developers.com/showthread.php?t=2301007
And after unbricking, I used the toolkit. And both times, after gaining S-on following the exact steps, the tampered comes up, and I can't get rid of it. As it stands now, my phone is Locked w/ tampered, S-on, and i put my CID back to CWS__001 with the toolkit, but it isn't showing up in Fastboot. I'm going to see if i can go back and manually write that CID back in then going to bed. Any help would be appreciated. I need to return this phone very soon. Thank you.
Edit: I ran getvar and it gave me the correct CID, despite it not showing in fastboot. I'm not screwing with it anymore til i can get some advice.....
Click to expand...
Click to collapse
Unlock ur bootloader. Gain S-OFF nd root access
then flash then zip from this link: http://www.htc1guru.com/guides/guru-bootloader-reset/
from TWRP/CWM. It will be an Aroma installer for removing the tampered logo and locking the bootloader
Here, choose Remove Tampered and lock ur bootloader(DON'T RELOCK. CHOOSE LOCK BOOTLOADER. then proceed to flash the RUU

whitetiger_0603 said:
I'm trying to regain full stock of my AT&T device and I followed a tutorial on gaining 100% stock with no traces of tampering. I go through all the steps in order, returning to stock CID, flashing stock RUU through fastboot, then returning to S-on and relocking the bootloader. The last step was removing the "tampered" stamp in the fastboot screen but I can't get rid of the thing. In fact, I originally, when i first modded, got rid of it, but after regaining S-on, the tampered came up again. So I ran the last command for removing it. But it won't go away. I tried it the manual way, running ADB commands, then i tried it with the All in One Toolkit. I almost bricked the thing trying different ways, including unlocking the boot and regaining S-off again. luckily i found a small tutorial for fixing that.
This is what I used to go back to stock: http://forum.xda-developers.com/showthread.php?t=2358738
This i used to unbrick: http://forum.xda-developers.com/showthread.php?t=2301007
And after unbricking, I used the toolkit. And both times, after gaining S-on following the exact steps, the tampered comes up, and I can't get rid of it. As it stands now, my phone is Locked w/ tampered, S-on, and i put my CID back to CWS__001 with the toolkit, but it isn't showing up in Fastboot. I'm going to see if i can go back and manually write that CID back in then going to bed. Any help would be appreciated. I need to return this phone very soon. Thank you.
Edit: I ran getvar and it gave me the correct CID, despite it not showing in fastboot. I'm not screwing with it anymore til i can get some advice.....
Click to expand...
Click to collapse
I'll highly suggest you read nkk71's guide linked in my signature. Don't forget that if you turn s-on on hboot 1.55, the tampered flag will come back after a few reboot so make sure you go back s-on on hboot 1.44 or 1.54. Anyway, its all explained in that guide

alray said:
I'll highly suggest you read nkk71's guide linked in my signature. Don't forget that if you turn s-on on hboot 1.55, the tampered flag will come back after a few reboot so make sure you go back s-on on hboot 1.44 or 1.54. Anyway, its all explained in that guide
Click to expand...
Click to collapse
raghav kapur said:
Unlock ur bootloader. Gain S-OFF nd root access
then flash then zip from this link: http://www.htc1guru.com/guides/guru-bootloader-reset/
from TWRP/CWM. It will be an Aroma installer for removing the tampered logo and locking the bootloader
Here, choose Remove Tampered and lock ur bootloader(DON'T RELOCK. CHOOSE LOCK BOOTLOADER. then proceed to flash the RUU
Click to expand...
Click to collapse
Thank you both. Alray, I looked through that thread last night before finally asking forh lep, but it seemed confusing as to what i needed exactly. I'll go through it again, maybe it was just late night brain fuzzies that made it look confusing to me. Raghav, I saw that as well, and will give it a shot. I appreciate you both responding.
I triple checked my hboot, and it's 1.44. I never changed it. Guess I'll check in if i have any more questions or have fixed the issue. Thanks again.

whitetiger_0603 said:
Thank you both. Alray, I looked through that thread last night before finally asking forh lep, but it seemed confusing as to what i needed exactly. I'll go through it again, maybe it was just late night brain fuzzies that made it look confusing to me. Raghav, I saw that as well, and will give it a shot. I appreciate you both responding.
I triple checked my hboot, and it's 1.44. I never changed it. Guess I'll check in if i have any more questions or have fixed the issue. Thanks again.
Click to expand...
Click to collapse
post a "fastboot getvar all" (excluding IMEI and s/n) and let me know which parts are confusing or need further explanation.
please note the guide was written (and rewritten) with in a certain sequence to avoid potential problems; if you have questions as to "why do this at that point" or other questions, feel free to ask

Ok, so in the order you guys gave me, I:
Unlocked bootloader via HTC-Dev..again...
I still had root access so I flashed CWMT
Regained S-off with the Toolkit
Flashed the zip you all provided, in recovery to "lock bootloader' and remove tampered
Tried using the toolkit again to flash the RUU. That failed so I manually ran ADB to do it.
It went through the whole process then at the end, says "FAILED (unknown status code). The RUU mode screen seems to be done. I know the green status bar never finishes completely, but I'm concerned with that failed message in cmd. Should i reboot to see what happens?
Edit: It looks like it worked. So, assuming I no longer have root access, cause if I remember correctly the RUU removes it, how do I go back to S-on, without the tampered popping up again?

whitetiger_0603 said:
Ok, so in the order you guys gave me, I:
Unlocked bootloader via HTC-Dev..again...
I still had root access so I flashed CWMT
Regained S-off with the Toolkit
Flashed the zip you all provided, in recovery to "lock bootloader' and remove tampered
Tried using the toolkit again to flash the RUU. That failed so I manually ran ADB to do it.
It went through the whole process then at the end, says "FAILED (unknown status code). The RUU mode screen seems to be done. I know the green status bar never finishes completely, but I'm concerned with that failed message in cmd. Should i reboot to see what happens?
Click to expand...
Click to collapse
stop using that toolkit and do it by yourself, best way to know what is going wrong....
What ruu did you used? Also if you are using a ruu.zip you have to flash it with fastboot in ruu mode not with adb.
You should go read and follow post #3 of nkk's guide.
EDIT: you still haven't posted your ''fastboot getvar all'' as @nkk71 asked for earlier.

alray said:
stop using that toolkit and do it by yourself, best way to know what is going wrong....
What ruu did you used? Also if you are using a ruu.zip you have to flash it with fastboot in ruu mode not with adb.
You should go read and follow post #3 of nkk's guide.
Click to expand...
Click to collapse
Noted, I think the toolkit is what keeps having the tampered pop up anyhow...
Guess I should have been more detailed. Rebooted into bootloader, then to RUU mode. Ran adb cmd to flash RUU. I know I have the correct file for that.
Double checked the guide you referenced... it seems to cluttered to me... but I found the part I need. Giving it a shot now.
Yup..that did it. I remember using that cmd line in the beginning but i didn't know that was for S-on, rather just for tampered. Just factory reset my phone now. Thank you again.
Edit: didn't post the getvar, as i thought it was only requested if i came up with another issue. My mistake. Thank you all again.

alray said:
stop using that toolkit and do it by yourself, best way to know what is going wrong....
Click to expand...
Click to collapse
+8
stop using toolkits
whitetiger_0603 said:
it seems to cluttered to me... but I found the part I need.
Click to expand...
Click to collapse
cluttered :crying::crying:
i knew this was gonna happen :crying::crying:
suggestions are welcome

nkk71 said:
+8
stop using toolkits
cluttered :crying::crying:
i knew this was gonna happen :crying::crying:
suggestions are welcome
Click to expand...
Click to collapse
Lol, I'm sorry... you're guid is very comprehensive. No lie there. I personally, just couldn't get around through it. It may just have been me. I just thought it could ahve been more organized. But hey, no big. I found what I needed and I appreciate it.:laugh:

whitetiger_0603 said:
Lol, I'm sorry... you're guid is very comprehensive. No lie there. I personally, just couldn't get around through it. It may just have been me. I just thought it could ahve been more organized. But hey, no big. I found what I needed and I appreciate it.:laugh:
Click to expand...
Click to collapse
Which parts did you find unorganized, I always appreciate constructive criticism :cyclops:

[Q] Going back to stock Bell Canada

So, I want to go back to stock 100% for repairs and I've followed every guide i could find, i promise this is not without many hours of trying...
I restored the Stock_JB_4.3_BM___001_TWRP_3.23.666.1_htc_one_m7 - which may or may not have been what came stock on the phone...
Firmware right now is 4A.14.3250.13
my CID is correct i believe (BM___001 <-- 3 underscores)
HBOOT is 1.44.
I flashed stock recovery and used revone to un-Tamper, lock, and S-ON. But the minute I boot up the phone to a usable state it says "Tamper Detected!" and reboots and HBOOT shows "Tamper" and "Security Warning". Been at this all day and the only thing i can come up with is that I must have either the wrong firmware or the wrong recovery? or the wrong combination of everything?? haha
Anyone encountered something like this? Tips?
Edit: currently sitting S-Off, Unlocked, Tampered..

I swear, i should just give up more often... Naturally the minute i hit post on this thread, after trying all day, i find the piece of the puzzle..Will update when i'm sure but i think the missing link was a mismatched recovery.

*FacePalm* wrong recovery all along. didnt see that huge thread with all the different recovery's available till now.
Things are working. Sorry to waste your kilobytes!