Alright, lets get into this. My camera has purple tint, so I was going to return to stock and take it in. This isn't my first attempt at returning to stock, last time I failed but was able to flash the GPE RUU. I'm with Rogers, so on this attempt I once again tried using the rogers RUU, I changed my CID back to ROGER001, I re-locked bootloader and put S-ON. Ran the RUU and got error 155. So I re-acquired s-off with Rumrunner. Then I locked the bootloader and put S-ON again. When I tried rebooting I got Tampered, Locked, Security Warning. Recovery seems to have disappeared, any attempt to reboot brings me back to the bootloader. I've attempted flashing a rogers recovery from an OTA, I've tried flashing the rom.zip out of the Rogers RUU, I've tried flashing the GPE RUU zip. Basically anything I try ends with (bootloader) signature checking... FAILED (remote: signature verify fail). I've tried unlocking the bootloader from HTCDEV, the screen prompt to unlock the bootloader doesn't appear on my device. I've tried running fastboot oem unlock (because it was GPE). Anything I could think of I tried.
TLR I bricked it good. Do I have any options?
Cazrelleum said:
Alright, lets get into this. My camera has purple tint, so I was going to return to stock and take it in. This isn't my first attempt at returning to stock, last time I failed but was able to flash the GPE RUU. I'm with Rogers, so on this attempt I once again tried using the rogers RUU, I changed my CID back to ROGER001, I re-locked bootloader and put S-ON. Ran the RUU and got error 155. So I re-acquired s-off with Rumrunner. Then I locked the bootloader and put S-ON again. When I tried rebooting I got Tampered, Locked, Security Warning. Recovery seems to have disappeared, any attempt to reboot brings me back to the bootloader. I've attempted flashing a rogers recovery from an OTA, I've tried flashing the rom.zip out of the Rogers RUU, I've tried flashing the GPE RUU zip. Basically anything I try ends with (bootloader) signature checking... FAILED (remote: signature verify fail). I've tried unlocking the bootloader from HTCDEV, the screen prompt to unlock the bootloader doesn't appear on my device. I've tried running fastboot oem unlock (because it was GPE). Anything I could think of I tried.
TLR I bricked it good. Do I have any options?
Click to expand...
Click to collapse
nope your pretty much done, you could have run over it with a truck ..same effect
http://forum.xda-developers.com/showthread.php?t=2664757
Cazrelleum said:
Alright, lets get into this. My camera has purple tint, so I was going to return to stock and take it in. This isn't my first attempt at returning to stock, last time I failed but was able to flash the GPE RUU. I'm with Rogers, so on this attempt I once again tried using the rogers RUU, I changed my CID back to ROGER001, I re-locked bootloader and put S-ON. Ran the RUU and got error 155. So I re-acquired s-off with Rumrunner. Then I locked the bootloader and put S-ON again. When I tried rebooting I got Tampered, Locked, Security Warning. Recovery seems to have disappeared, any attempt to reboot brings me back to the bootloader. I've attempted flashing a rogers recovery from an OTA, I've tried flashing the rom.zip out of the Rogers RUU, I've tried flashing the GPE RUU zip. Basically anything I try ends with (bootloader) signature checking... FAILED (remote: signature verify fail). I've tried unlocking the bootloader from HTCDEV, the screen prompt to unlock the bootloader doesn't appear on my device. I've tried running fastboot oem unlock (because it was GPE). Anything I could think of I tried.
TLR I bricked it good. Do I have any options?
Click to expand...
Click to collapse
GPE bootloader 1.54+ can not be unlocked (the well known GPE bootloader bug)
You did the final blow when turning it back S-ON.
Now that you can't boot it, you can't achieve s-off anymore and the only work around for the GPE bootloader unlock bug require S-OFF.
So you are stuck with a non-bootable, non s-off'able, non-unlockable phone, well, a brick with written proof that you have caused it yourself (tampered flag in the bootloader)
Sorry :crying:
Now time to send your phone for repair or to buy another one.
Try this
http://forum.xda-developers.com/showthread.php?t=2363516
Thread closed and cleaned up at OP's request.
Related
I'm trying to go back to stock bootloader, stock ROM, and I keep getting this "signature verify fail." Sometimes with a "12" in front of it. It's frustrating, because right now my phone doesn't work. I've Googled some stuff, but it all seems to require putting something onto an SD card, which doesn't work with the HTC One. Currently "relocked" bootloader.
EDIT: Fixed. I unlocked the bootloader, and now it's booting to Android.
Are you flashing a ruu?
Guich said:
Are you flashing a ruu?
Click to expand...
Click to collapse
Yes.
Did you chech if this ruu is compatible with your cid and your hboot version?
Because, without s-off, you can't flash a ruu with a old bootloader...
I don't know how to check that, but I unlocked the bootloader again and now it's working just fine.
So I was fine yesterday, went through all the steps to get a full GE One. Was very curious
I like sense better though personally, so I wanted to go back. I have changed my MID back to it's original values and the CID to HTC__001.
In RUU mode after entering fastboot, it will no longer allow me to flash anything, with a 'unknown 99 error.' I also wanted to get S-on again, so I went through the steps and all was well. Or so I thought. Kept getting error -6 and error -1. I also relocked the bootloader. But now I can't boot into Android, and there are three tags over the Bootloader now. **TAMPERED** **RELOCKED** and **Security Warning**. If I try to boot to the OS or recovery it brings me straight back to HBOOT. Anything I can do to resolve this mess? Thanks in advance.
EDIT: I forgot to mention that I flashed back to an original HBOOT before attempting any of this. 1.54.
I think this has happened because you've relocked your bootloader, whilst having a custom recovery installed.
Just use htcdev.com to unlock your boatloader
Hey guys... Ok I am in a very unique situation. I was recently testing to get 4.2.2 ROMs to work on sprint with a kernel...
Well, it ended up not working, and a few things ended up getting jittery. So i relocked bootloader, did a fastboot oem rebootRUU, and went ahead and ruu'd the phone. Here is where it gets weird...
After the RUU finished succesfully, I went into bootloader, and it showed "RELOCKED S-OFF", and figured that cant be good, so i proceeded to do a fastboot oem writesecureflag 3, and re-relocked via RevONE. Bootloader now showed "LOCKED S-ON", so RUU'd again. Now, my CID is still unlocked which has nothing to do with hboot i know. Either way, I did the fastboot flash unlocktoken......, and got HTCDEV unlocked. I then proceed to unlock via RevONE with all successful. I even flashed the boot_unsecure.img (kernel) on the stock RUU rom.
Bootloader shows "UNLOCKED S-OFF"... But I am not S-Off, simply my flag shows it. I cannot flash a different hboot, nor can i flash a radio (and yes i tried flashing within rebootRUU). It gives me the stupid "remote - not allowed".
Would there be a way to DD the mmcblk? Does anyone on an ENG S-Off bootloader have the mmcblk partition number? Mine does not show the hboot label... cat /proc/emmc.
Anyone ideas? Moonshine does not work either.
Update... MMCBLK0P12 hboot
Solved
Lol that was easy... Just had to do a low level overwrite (DD) to an ENG hboot, so that i could then truely S-Off, and flash other hboots and radios... sheesh...
Tilde88 said:
Hey guys... Ok I am in a very unique situation. I was recently testing to get 4.2.2 ROMs to work on sprint with a kernel...
Well, it ended up not working, and a few things ended up getting jittery. So i relocked bootloader, did a fastboot oem rebootRUU, and went ahead and ruu'd the phone. Here is where it gets weird...
After the RUU finished succesfully, I went into bootloader, and it showed "RELOCKED S-OFF", and figured that cant be good, so i proceeded to do a fastboot oem writesecureflag 3, and re-relocked via RevONE. Bootloader now showed "LOCKED S-ON", so RUU'd again. Now, my CID is still unlocked which has nothing to do with hboot i know. Either way, I did the fastboot flash unlocktoken......, and got HTCDEV unlocked. I then proceed to unlock via RevONE with all successful. I even flashed the boot_unsecure.img (kernel) on the stock RUU rom.
Bootloader shows "UNLOCKED S-OFF"... But I am not S-Off, simply my flag shows it. I cannot flash a different hboot, nor can i flash a radio (and yes i tried flashing within rebootRUU). It gives me the stupid "remote - not allowed".
Would there be a way to DD the mmcblk? Does anyone on an ENG S-Off bootloader have the mmcblk partition number? Mine does not show the hboot label... cat /proc/emmc.
Anyone ideas? Moonshine does not work either.
Update... MMCBLK0P12 hboot
Solved
Lol that was easy... Just had to do a low level overwrite (DD) to an ENG hboot, so that i could then truely S-Off, and flash other hboots and radios... sheesh...
Click to expand...
Click to collapse
I thought once soff always soff I have ruu 2 times already after soff revone and was still able to flash the radio from the newest firmware. After every ruu it always said soff
Sent from my GT-P3113 using xda app-developers app
Just out of curisosity, could anyone explain why that happened? What made the security flag change?
Also, why did you say "this cannot be good" when you saw "RELOCKED S-OFF"? Were you S-OFF to begin with? You can lock the bootloader and still remain S-Off, correct?
karn101 said:
Just out of curisosity, could anyone explain why that happened? What made the security flag change?
Also, why did you say "this cannot be good" when you saw "RELOCKED S-OFF"? Were you S-OFF to begin with? You can lock the bootloader and still remain S-Off, correct?
Click to expand...
Click to collapse
Yes, but I figured that while it was relocked, it would overwrite the hboot to stock if I RUU'd, thus making the flag S-On. however, this needed to be manually done with fastboot apparently.
Tbh, I think this all started from a ROM flash, it was an international ROM, and I hadn't bothered to check to know the partition layouts were different. Kernel ended up flashing to recovery, and system almost went to radio, lol idk how it didn't brick.... but yea.
Tilde88 said:
Yes, but I figured that while it was relocked, it would overwrite the hboot to stock if I RUU'd, thus making the flag S-On. however, this needed to be manually done with fastboot apparently.
Tbh, I think this all started from a ROM flash, it was an international ROM, and I hadn't bothered to check to know the partition layouts were different. Kernel ended up flashing to recovery, and system almost went to radio, lol idk how it didn't brick.... but yea.
Click to expand...
Click to collapse
Oh, so you were more concerned that it said relocked than S-OFF. S-OFF was bolded so I thought you were saying "Uh oh" to the S-Off.
I posted in the Verizon forums a day ago, but have received little to no help. Now I hope that someone can help me here.
Original post http://forum.xda-developers.com/showthread.php?t=2599610
I used this thread to unroot and return to stock http://forum.xda-developers.com/show...highlight=s-on
I had done this before with one of CM 10 and I kept the files used in this thread.
I switched to AOKP kitkat 12-30-13. I wanted to return to stock and unrooted.
I got to the oem ruu and kept receiving this message. FAILED (remote: 90 hboot pre-update! please flush image again immediately)
I did this repeatedly as followed. It went over 5 times. I figured this was a problem. Now I am stuck in the bootloader where my phone is locked and S-on. I tried to flash it again and now I get remote: 12 signature verify failed.
It also says ***TAMPERED*** at the top of bootloader, above ***LOCKED***
Edit: I wanted to mention that I do have a backup of my kitkat state at the beginning of all of this. It is in twrp, but I can't flash install the twrp.img, signature verify failed.
What exactly was the order you did this in? When I set my phone back to stock, I did it in the following order:
1. run RUU
2. lock bootloader
3. S-ON
I'm guessing you did not do it in that order, since you are trying to flash the RUU with a locked bootloader and S-ON.
Since the RUU failed to flash, you should still have TWRP. You said signature verification failed, but I believe there is an option in TWRP that lets you toggle signature verification. Once you have turned off signature verification, try restoring your backup.
If your backup restores successfully, you need to S-OFF your phone and unlock your bootloader, as you will need the unlocked bootloader later on.
The following is the gist of what you need to do. Check here for a more detailed explanation:
http://forum.xda-developers.com/showthread.php?t=2358738
Once you S-OFF your phone, set your CID to stock and run the RUU. You should be back with stock ROM and stock recovery. However, to lock the bootloader and S-ON your phone, you need superuser. You need to flash TWRP (which is why the bootloader needs to be unlocked at this point) so that you can flash superuser (SuperSU).
Once you have superuser, flash the stock recovery through fastboot. This will only work with an unlocked bootloader, which is why you must flash the stock recovery before you lock the bootloader.
Superuser is still functional with stock recovery. Run through the commands to reset the tamper flag, lock the bootloader, and set your phone back to S-ON. You can then unroot through the SuperSU app.
sweetnsour said:
What exactly was the order you did this in? When I set my phone back to stock, I did it in the following order:
1. run RUU
2. lock bootloader
3. S-ON
I'm guessing you did not do it in that order, since you are trying to flash the RUU with a locked bootloader and S-ON.
Since the RUU failed to flash, you should still have TWRP. You said signature verification failed, but I believe there is an option in TWRP that lets you toggle signature verification. Once you have turned off signature verification, try restoring your backup.
If your backup restores successfully, you need to S-OFF your phone and unlock your bootloader, as you will need the unlocked bootloader later on.
The following is the gist of what you need to do. Check here for a more detailed explanation:
http://forum.xda-developers.com/showthread.php?t=2358738
Once you S-OFF your phone, set your CID to stock and run the RUU. You should be back with stock ROM and stock recovery. However, to lock the bootloader and S-ON your phone, you need superuser. You need to flash TWRP (which is why the bootloader needs to be unlocked at this point) so that you can flash superuser (SuperSU).
Once you have superuser, flash the stock recovery through fastboot. This will only work with an unlocked bootloader, which is why you must flash the stock recovery before you lock the bootloader.
Superuser is still functional with stock recovery. Run through the commands to reset the tamper flag, lock the bootloader, and set your phone back to S-ON. You can then unroot through the SuperSU app.
Click to expand...
Click to collapse
Using the procedure shown, I followed the steps exactly stated in the post. However you are right, about switching the methods 2 and 3. I didn't realize what using the last step, switching to s-on would do. I failed to flash the stock rom, and then proceeded to s-on, and during that I guess the bootloader locked, or it locked before when it was trying to flash stock.
Anyways...I only briefly read the links you posted, but it seems most of the stuff, and the download files are for sprint, att, t-mobile, google, etc but not Verizon. I'm not sure if these methods will help much with a verizon phone, or I might get stuck along the way looking for Verizon actions.
Also in the very red for the s-off revone it says that it does not support hboot 1.54, which is what I have.
geeibara said:
Using the procedure shown, I followed the steps exactly stated in the post. However you are right, about switching the methods 2 and 3. I didn't realize what using the last step, switching to s-on would do. I failed to flash the stock rom, and then proceeded to s-on, and during that I guess the bootloader locked, or it locked before when it was trying to flash stock.
Anyways...I only briefly read the links you posted, but it seems most of the stuff, and the download files are for sprint, att, t-mobile, google, etc but not Verizon. I'm not sure if these methods will help much with a verizon phone, or I might get stuck along the way looking for Verizon actions.
Also in the very red for the s-off revone it says that it does not support hboot 1.54, which is what I have.
Click to expand...
Click to collapse
The method should work no matter the carrier; just be sure you have the appropriate files. What I mean is, the only time you need to consider the carrier is for the RUU file.
hboot 1.54 is not be supported by revone, but it is supported by rumrunner.
I think for now, you should just try to get your phone booted. Were you able to restore your backup?
sweetnsour said:
The method should work no matter the carrier; just be sure you have the appropriate files. What I mean is, the only time you need to consider the carrier is for the RUU file.
hboot 1.54 is not be supported by revone, but it is supported by rumrunner.
I think for now, you should just try to get your phone booted. Were you able to restore your backup?
Click to expand...
Click to collapse
I couldn't access twrp, when I try to go to recovery from the bootloader, it takes me back to fastboot. So I was unable to do that.
I don't know how to gain s-off from my point. You said rumrunner should support it, but I tried running it, and it failed, it didn't get to the first step because it had to recognize the device, where adb commands cant recognize it.
Anyways, I gave up and asked for a warranty replacement.
geeibara said:
I couldn't access twrp, when I try to go to recovery from the bootloader, it takes me back to fastboot. So I was unable to do that.
I don't know how to gain s-off from my point. You said rumrunner should support it, but I tried running it, and it failed, it didn't get to the first step because it had to recognize the device, where adb commands cant recognize it.
Anyways, I gave up and asked for a warranty replacement.
Click to expand...
Click to collapse
to be able to reflash twrp you need to unlock your bootloader that is why you are getting signature fail error
Hi guys,
I had back to completely stock my m7 for guarantee 2 weeks ago. Yesterday i tried every possible way to s-off but i can't get it. So i tried run RUU for downgrade OS,hboot etc. relock bootloader. But accidentally RUU removed OS; no main version in getvar, stock recovery, relocked and there is a warning under relocked title it says ''security warning''
Run RUU or flash update.zip,rom.zip,ruu.zip no matter what,I get 'failed: remote signiture verify fail'. Phone does not boot, because no OS, so no adb. Is only way J-tag for ressurrect it
blitzzkrieg said:
Hi guys,
I had back to completely stock my m7 for guarantee 2 weeks ago. Yesterday i tried every possible way to s-off but i can't get it. So i tried run RUU for downgrade OS,hboot etc. relock bootloader. But accidentally RUU removed OS; no main version in getvar, stock recovery, relocked and there is a warning under relocked title it says ''security warning''
Run RUU or flash update.zip,rom.zip,ruu.zip no matter what,I get 'failed: remote signiture verify fail'. Phone does not boot, because no OS, so no adb. Is only way J-tag for ressurrect it
Click to expand...
Click to collapse
you can not downgrade with s-on!
re-unlock your bootloader, flash a custom recovery and a rom and achieve s-off with sunshine then follow nkk71's guide to return stock (linked in my sig)
alray said:
you can not downgrade with s-on!
re-unlock your bootloader, flash a custom recovery and a rom and achieve s-off with sunshine then follow nkk71's guide to return stock (linked in my sig)
Click to expand...
Click to collapse
I can't unlock bootloader back, flashing unlock_code.bin and allow prompt from phone, it goes to update screen, 2 minutes later i get red triangle screen. I have to unlock my bootloader without unlock_code but my hboot 1.57. So i think my device is dead
Try generating another unlock bin