Database Develop

[Q] revone s-off, tampered flag, is s-on safe?

I've read revone leaves hboot stock... is that even after changing the flag? Is it safe to s-on again?
After hunreds of pages read I haven't seen it explicitly stated so just wanted to confirm I am not set up for failure.
Also will it still not say tampered?
Thanks!

I'd just leave it S-OFF. It's recommended only to go back to S-ON again if you're running a 100% stock device (e.g. you've just run an RUU) as it can brick the phone otherwise

EddyOS said:
I'd just leave it S-OFF. It's recommended only to go back to S-ON again if you're running a 100% stock device (e.g. you've just run an RUU) as it can brick the phone otherwise
Click to expand...
Click to collapse
How about with an adb backup restored, flag off and relocked?
I guess my concern is what does the flag change and should I turn it back on before s-on or just leave it? This is purely informative.

Turning your security flag back on will re enable the checks the phone does when booting. It's making sure all the parts (hboot, radio, etc....) are signed. If you flashed a radio or hboot that's unsigned (like the one from revone or moonshine) the device will simply not boot. One of the ways to cause a Perma brick which can only be fixed with a jtag jig which doesn't exist yet for the one
Sent from my Tricked out HTC One

The first post of the thread used to say it's safe to do (although as I type it I feel like I spelt it wrong)
fastboot oem writesecureflag 3
It's fine, if you want to do it, but there's little point before flashing everything else to stock and returning it for warranty.

[Q] Is it possible to flash HBOOT when you are eMMC bricked?

Title says all.

anonymousthing said:
Title says all.
Click to expand...
Click to collapse
Can you get to the bootloader screen by hold Volume Down + Power button?
If not, then no.

Yes, I can. But when I try and flash the stock HBOOT back, it says 'can not roll back hboot version'.
I'm trying to restore the stock HBOOT so I can send it in for warranty without big black "Blackrose" text along the top

anonymousthing said:
Yes, I can. But when I try and flash the stock HBOOT back, it says 'can not roll back hboot version'.
I'm trying to restore the stock HBOOT so I can send it in for warranty without big black "Blackrose" text along the top
Click to expand...
Click to collapse
I think you have to uninstall Blackrose before you can restore anything, open the Blackrose program, there should be an option to uninstall

Gizmo648 said:
I think you have to uninstall Blackrose before you can restore anything, open the Blackrose program, there should be an option to uninstall
Click to expand...
Click to collapse
I believe Blackrose gave a similar error, though I'll need to go check the specifics

anonymousthing said:
I believe Blackrose gave a similar error, though I'll need to go check the specifics
Click to expand...
Click to collapse
Yes if you have BlackRose S-OFF HBOOT, the only way to replace it is to run the BlackRose installer with the /uninstall option.

Very strange - I booted into CWM recovery and when I run adb devices, it detects my phone
But when I run BlackRose_IS.exe /uninstall, it gives *Waiting for device* and stays stuck there. Any ideas? Can BlackRose even be installed/uninstalled from recovery? :\

Never mind, I have successfully removed Blackrose by booting into an SD card bootable CM7.1 image, then using terminal emulator and dd to force write a new hboot. I tried writing the stock hboot that came with the virgin mobile RUU, but now I'm getting "security warning" and I'm stuck to the bootloader. I'll search through the forums now for what to do... thanks guys anyway!

anonymousthing said:
Never mind, I have successfully removed Blackrose by booting into an SD card bootable CM7.1 image, then using terminal emulator and dd to force write a new hboot. I tried writing the stock hboot that came with the virgin mobile RUU, but now I'm getting "security warning" and I'm stuck to the bootloader. I'll search through the forums now for what to do... thanks guys anyway!
Click to expand...
Click to collapse
With the security warning you should now be able to flash the official HTC ICS RUU.

Yup, I successfully flashed it and now it's back to what appears to be the factory settings, so hopefully the service guy will replace my mobo when I send it in.
On a side note, does the bootloader, when locked by HTC (and you unlock using htcdev.com) normally say *LOCKED* along the top? Mine doesn't say this (I don't really care about getting that back anyway, just wondering)

anonymousthing said:
Yup, I successfully flashed it and now it's back to what appears to be the factory settings, so hopefully the service guy will replace my mobo when I send it in.
On a side note, does the bootloader, when locked by HTC (and you unlock using htcdev.com) normally say *LOCKED* along the top? Mine doesn't say this (I don't really care about getting that back anyway, just wondering)
Click to expand...
Click to collapse
There are 3 statuses: "LOCKED", "UNLOCKED" and "RELOCKED" if your HBOOT is 2.00.0000 or above. If your HBOOT is version 1.13.0000 or 1.16.0000, then they did not show that type of status on the HBOOT screen.

Red Developer warning message on splash screen at boot

hey guys, I plan to sell my one as I just bough the nexus 5, and I want to return the phone back to stock. However,the link in the faq seems to refer more towards the boot loader text, not the splash screen warning message. Would running of the RUU get rid of it? I am s-off.
Sorry updated my post to be more clear was driving when I wrote it.

If the red text states things about it being a developmental devices then that is due to your device being S-Off. Once you re-enable the security flag then it will disappear but you need to do this while rooted so you can then use Revone to remove "Tampered" and to "Lock" the device instead of "Relock".

Simply changing the s-off flag will get rid of the message on the splash screen when you boot the phone?

EPayne123 said:
If the red text states things about it being a developmental devices then that is due to your device being S-Off. Once you re-enable the security flag then it will disappear but you need to do this while rooted so you can then use Revone to remove "Tampered" and to "Lock" the device instead of "Relock".
Click to expand...
Click to collapse
Actually I think it will work even if he isnt rooted, in fact I would recommend flashing the stock ruu first then use the write secure flag command. Its always confusing to figure out which lock command from revone locks the bootloader and which one relocks the bootloader lol

Failed: Return to stock and unrooted (Verizon)

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

[Q] Confirm Stock HBOOT?

I converted my phone to a Developer Edition phone a while back, and in the process went S-OFF. I would like to S-ON, as I have read this removes the 'test device' status that apparently sends HTC information. I also read that going S-ON with a custom HBOOT is a very bad thing, but how do I tell if my HBOOT is custom? The top just reads M7_UL PVT SHIP S-OFF RH and the version is HBOOT 1.56.

hjjfffaa said:
I converted my phone to a Developer Edition phone a while back, and in the process went S-OFF. I would like to S-ON, as I have read this removes the 'test device' status that apparently sends HTC information. I also read that going S-ON with a custom HBOOT is a very bad thing, but how do I tell if my HBOOT is custom? The top just reads M7_UL PVT SHIP S-OFF RH and the version is HBOOT 1.56.
Click to expand...
Click to collapse
From Rumrunner documentation
How to get rid of S-OFF warnings
There are two visual differences that will indicate that your device is S-OFF (other than checking in the bootloader):
1. Go to Settings > About. You should see "Tell HTC and error reporting" option right under "Software updates".
If you don't see that option, then you're already using a custom ROM and you can skip this step. But if you see the "Tell HTC and error reporting" option, select it and scroll down to read a warning message in red text. The "Tell HTC" option is permanently enabled and cannot be turned off without flashing a custom ROM. If you are not comfortable with HTC collecting information from your device, you can load your custom recovery, wipe data, cache, dalvik and install a custom ROM - the "Tell HTC and error reporting" option will be gone.
2. Boot up or restart your phone. In the boot splash screen, if you see a warning message in red text: "This build is for development purposes only..." you can remove it by flashing a custom hboot, now supplied by the developers of Rumrunner: http://rumrunner.us/hboots/. If your phone's firmware and carrier are not listed, the custom Hboots provided on the Rumrunner site will not work and you will likely brick your device. But you can look for other sources. Try this one: http://forum.xda-developers.com/show....php?t=2316726. Alternatively, you can request for a custom Rumrunner Hboot for your specific firmware and carrier. Instructions: Do fastboot getvar all and don't forget to remove your serialno and imei. Paste the info into an email. Upload your RUU or firmware.zip from OTA to dropbox and add link in email and don't forget to mention your carrier, if any. Send to: [email protected]. Then, check the Rumrunner Hboots page regularly for the update: http://rumrunner.us/hboots/.

mb_guy said:
From Rumrunner documentation
How to get rid of S-OFF warnings
There are two visual differences that will indicate that your device is S-OFF (other than checking in the bootloader):
1. Go to Settings > About. You should see "Tell HTC and error reporting" option right under "Software updates".
If you don't see that option, then you're already using a custom ROM and you can skip this step. But if you see the "Tell HTC and error reporting" option, select it and scroll down to read a warning message in red text. The "Tell HTC" option is permanently enabled and cannot be turned off without flashing a custom ROM. If you are not comfortable with HTC collecting information from your device, you can load your custom recovery, wipe data, cache, dalvik and install a custom ROM - the "Tell HTC and error reporting" option will be gone.
2. Boot up or restart your phone. In the boot splash screen, if you see a warning message in red text: "This build is for development purposes only..." you can remove it by flashing a custom hboot, now supplied by the developers of Rumrunner: http://rumrunner.us/hboots/. If your phone's firmware and carrier are not listed, the custom Hboots provided on the Rumrunner site will not work and you will likely brick your device. But you can look for other sources. Try this one: http://forum.xda-developers.com/show....php?t=2316726. Alternatively, you can request for a custom Rumrunner Hboot for your specific firmware and carrier. Instructions: Do fastboot getvar all and don't forget to remove your serialno and imei. Paste the info into an email. Upload your RUU or firmware.zip from OTA to dropbox and add link in email and don't forget to mention your carrier, if any. Send to: [email protected]. Then, check the Rumrunner Hboots page regularly for the update: http://rumrunner.us/hboots/.
Click to expand...
Click to collapse
I'm aware of these options, but would rather not have anything custom to worry about. According to this a custom ROM or HBOOT is the only way to actually disable the reporting while keeping S-OFF, which I do not care to keep.

hjjfffaa said:
I'm aware of these options, but would rather not have anything custom to worry about. According to this a custom ROM or HBOOT is the only way to actually disable the reporting while keeping S-OFF, which I do not care to keep.
Click to expand...
Click to collapse
Bump. Just need to know if I have the hboot for the Developer Edition so I can run the RUU and S-ON, or where I could find it. Been searching.

hjjfffaa said:
Bump. Just need to know if I have the hboot for the Developer Edition so I can run the RUU and S-ON, or where I could find it. Been searching.
Click to expand...
Click to collapse
After running the RUU you know for sure you have stock hboot because the RUU installs it
I still can't recommend s-on for any reason

hjjfffaa said:
I'm aware of these options, but would rather not have anything custom to worry about. According to this a custom ROM or HBOOT is the only way to actually disable the reporting while keeping S-OFF, which I do not care to keep.
Click to expand...
Click to collapse
You understand correctly.
If you *really* object to the Tell HTC reporting *and* you do not wish to run a custom ROM, S-ON may be your only choice, and I have to say I personally would never S-ON not even for warranty repair.
As you correctly concluded, going S-ON with a custom HBOOT is fatal. If there is no question (ie you had total control over the phone during its entire lifetime and prefect memory of what you did to it), just go S-ON . Odds are, unless you *know* you flashed a custom HBOOT (which is invariably for the sole purpose of getting rid of annoying red warning text), you have a stock HBOOT. Life is short. It's only a phone. Just flash.
If you're *not* sure what HBOOT you may have flashed, the best way to prevent disaster is to just take total control of the situation and manually flash a stock HBOOT yourself just before attempting S-ON. There are plenty of threads that have the zip files you need. One caveat, a failed HBOOT flash is also fatal, so start with a fully charged battery and if you see "FAILED" during flashing, be sure NOT to reboot the phone before you fix it and confirm success.
Or, as suggested above, just RUU. Drastic, but failsafe.
Note *any* stock HBOOT, regardless of version, will allow the phone to boot after S-ON, although good style dictates you use one of the same vintage as all the other firmware and software you are running.
Sent from my HTC One using xda app-developers app

NxNW said:
Or, as suggested above, just RUU. Drastic, but failsafe.
Click to expand...
Click to collapse
Thank for taking all the time to write this up. Am I to gather from this sentence here that an RUU will reinstall the stock HBOOT? I'm not bothered about wiping the phone since I am not keeping it and already have all of my data backed up. I have had total control of the phone, the only problem was that I was getting android-info parse errors trying to run the Developer Edition RUU with the stock, but S-OFF, HBOOT. Someone provided an HBOOT for me that apparently had the correct android-info setup and it worked perfectly.

Well, yes, RUU touches every partition and puts each one back exactly the way HTC approves of, including the partition containing HBOOT. (And the write method it uses is safer than flashing things manually.)
But you have already observed it can be a pain to get RUU's to succeed sometimes. In your case, S-OFF helps greatly so you should eventually be able to run a RUU just fine. If, in the process, you change your CID to "SuperCID" (11111111) be sure to change it back to your phone's real CID before going S-ON. S-ON is the absolute last step in any procedure you are contemplating.
Sent from my HTC One using xda app-developers app