Pls I need help, I've unlocked the bootloader and rooted my phone but now the red warning appears, i'm 4.16.709.xx firmware, however now i'm using viper rom and still get the warning, how can i remove that?
As far as i know, only stock state removes that red warning.
Beamed in by telepathy.
Or you flash a NoRedText aboot (S-OFF required). However, you need to be aware that these modified aboots can lead to unrecoverable bricks if the modifications didn't get done correctly. Therefore, I personally recommend ignoring the red text in lieu of flashing such an aboot.
Related
Hey, I've been reading up on what needs to be done to get my device back to stock everything so that they don't bill me for the repair (there's a dead pixel on the screen). I was only running the stock ROM with SuperSU and TWRP recovery. I've already returned the recovery back to the stock recovery I backed up, however my device still says *** TAMPERED *** on the HBOOT screen. I've looked up how to remove this flag, but all the info I have found assumes I have a device that came with a locked bootloader, and mentions something about S-OFF. Since I have the developer edition, I don't want to lock the bootloader since it was never locked to begin with. What steps should I take to remove the tampered flag? Do I still need to worry about S-OFF?
Dr.Preston said:
Hey, I've been reading up on what needs to be done to get my device back to stock everything so that they don't bill me for the repair (there's a dead pixel on the screen). I was only running the stock ROM with SuperSU and TWRP recovery. I've already returned the recovery back to the stock recovery I backed up, however my device still says *** TAMPERED *** on the HBOOT screen. I've looked up how to remove this flag, but all the info I have found assumes I have a device that came with a locked bootloader, and mentions something about S-OFF. Since I have the developer edition, I don't want to lock the bootloader since it was never locked to begin with. What steps should I take to remove the tampered flag? Do I still need to worry about S-OFF?
Click to expand...
Click to collapse
You need to be S-OFF to remove the tampered flag.
[how to] remove your "tampered" banner
Though I'll find it funny if they have issues with a tampered flag on a developer edition seeing as the bootloader comes unlocked already. Pretty obvious someone is gonna do some "developing" of some sorts on it. Anyways...
BerndM14 said:
You need to be S-OFF to remove the tampered flag.
[how to] remove your "tampered" banner
Though I'll find it funny if they have issues with a tampered flag on a developer edition seeing as the bootloader comes unlocked already. Pretty obvious someone is gonna do some "developing" of some sorts on it. Anyways...
Click to expand...
Click to collapse
Thanks. Firewater didn't work so I had to use Sunshine
You would think they wouldn't care but when I was on the phone with them they weren't sure. Since I opted to have them overnight me a replacement and have me ship them back my defective unit afterwards, I don't really get to negotiate any "out of warranty" issues, even if they are unrelated to the defect.
Hello,
My UK Vodafone branded phone has been rooted with custom recovery installed. Its still s-on.
I searched XDA and getting some mixed information hence I decided to open a new topic to get so answers.
I would like to achieve full STOCK without flags.
In case of a warranty claim I believe I need to install stock recovery, unroot and lock the boot loader. However locking boot loader again - will create RELOCKED message instead of Locked. Which is still not good for warranty claim.
In order to removed RELOCKED I would need to get S-Off and modify flags manually via commands. However having latest FW OTA installed it is not possible to get S-OFF (according to my knowledge). Having said that it will not be possible to remove any flags such as relocked so basically I'm stuck.
Please correct me if I'm wrong here or give me so hope
Thanks for your help.
All correct sir.
Hope you say ?
Sunshine should be updated soon and it should handle latest firmware
a bit disappointed
did not know that rooting will invalidate warranty for good
So, I unlocked by bootloader and went s-off in order to turn my HTC 10 into the US Unlocked version, so that I could get Nougat. Everything went well, I unlocked it using HTC dev, installed TWRP, flashed super su, installed Sunshine, went S-OFF, changed CID and MID, relocked, used the RUU.exe to get Nougat.
But now, even when the bootloader is relocked, I still get that red warning text that appears when the phone is booting up. Is it normal? Back on my old M8, relocking the bootloader took out the red text, as far as I remember. I tried to go back to S-ON, but the command failed.
Is there any way to get rid of that red text?
something like this?
http://forum.xda-developers.com/htc-10/development/bad-sprouts-hidden-red-text-aboots-t3397548 you need something like this just follow it step by step
Yes, that text. But there is no firmware for the Nougat version I have on my HTC right now, and returning to Marshmallow to get rid of that text would pretty much cancel the thing I made this for from the beginning.
TheMadKing said:
So, I unlocked by bootloader and went s-off in order to turn my HTC 10 into the US Unlocked version, so that I could get Nougat. Everything went well, I unlocked it using HTC dev, installed TWRP, flashed super su, installed Sunshine, went S-OFF, changed CID and MID, relocked, used the RUU.exe to get Nougat.
But now, even when the bootloader is relocked, I still get that red warning text that appears when the phone is booting up. Is it normal? Back on my old M8, relocking the bootloader took out the red text, as far as I remember. I tried to go back to S-ON, but the command failed.
Is there any way to get rid of that red text?
Click to expand...
Click to collapse
Hi, just a bit of warning when using the modified aboot, flashing this carelessly will result in an unrecoverable brick, search for the Sneakyghost thread for flashable zips, he explains very well why he dropped support for them, too many bricks.
http://forum.xda-developers.com/htc-10/how-to/2016-05-27-fastboot-flashing-firmware-t3387520/page112
This is an example of someone bricking their phone:
http://forum.xda-developers.com/htc-10/help/htc-10-brick-t3521251
For your particular case, I think I read somewhere that changing the MID could cause the red text to appear, but I'm not 100% sure on that, in my case I only changed the CID for the US unlocked one and left the MID the same, I don't have the red text and I'm on Nougat, S-Off and unlocked, so relocking is not necessary to get rid of it.
I have seen the red text but only flashing a different kernel, running the Nougat RUU got rid of it.
Just my 2 cents, maybe it's not worth to have a brick just to get rid of some text you only see when rebooting.
ReaperHack said:
Hi, just a bit of warning when using the modified aboot, flashing this carelessly will result in an unrecoverable brick, search for the Sneakyghost thread for flashable zips, he explains very well why he dropped support for them, too many bricks.
http://forum.xda-developers.com/htc-10/how-to/2016-05-27-fastboot-flashing-firmware-t3387520/page112
This is an example of someone bricking their phone:
http://forum.xda-developers.com/htc-10/help/htc-10-brick-t3521251
For your particular case, I think I read somewhere that changing the MID could cause the red text to appear, but I'm not 100% sure on that, in my case I only changed the CID for the US unlocked one and left the MID the same, I don't have the red text and I'm on Nougat, S-Off and unlocked, so relocking is not necessary to get rid of it.
I have seen the red text but only flashing a different kernel, running the Nougat RUU got rid of it.
Just my 2 cents, maybe it's not worth to have a brick just to get rid of some text you only see when rebooting.
Click to expand...
Click to collapse
Well, I surely didn't want to risk that, so I did what you mentioned. Yeah, the problem might have been from the MID. I changed it back, and flashed the RUU with the original software I had, locked the bootloader, and the text is gone. Thanks!
Hi guys,
Got a phone a need to revive. I received unusable. Mother gave it to my sisters friend and she said it doesnt work. I now see why cause he was trying to mod it.
I managed to once get into TWRP but cant anymore. It was UNLOCKED but now RELOCKED which I possibly made it a little harder for me.
So currently "fastboot getvars" reports back all the info. It's showing version-main 6.13.206.5 and I just want official O2 stock so can use the phone. Ideally sim unlocked but could hassle O2 for that later since it was my mother's contract.
Basically just want to get a working recovery image on and then flash stock. CID is 02__001
Any suggestion to revive this welcomed, please.
So it still have twrp on it ? If yes, boot to twrp recovery then restore the stock backup.
You can find all you need in my thread - https://forum.xda-developers.com/htc-one-m8/help/tutorial-how-to-stock-stock-twrp-t3086860
Post #1 - how-to
Post #3 - you'll find the O2 stock backup
Post #5 - you'll find O2 firmware, install firmware after you restore the backup
ckpv5 said:
So it still have twrp on it ? If yes, boot to twrp recovery then restore the stock backup.
You can find all you need in my thread - https://forum.xda-developers.com/htc-one-m8/help/tutorial-how-to-stock-stock-twrp-t3086860
Post #1 - how-to
Post #3 - you'll find the O2 stock backup
Post #5 - you'll find O2 firmware, install firmware after you restore the backup
Click to expand...
Click to collapse
No, I cannot get into it. When I select HBOOT, then select recovery it just shows white screen, ANDROID and then back to the menu. TWRP no longer works. That's what I'm trying to fix or put on a stock recovery image and then stock OS/firmware.
Just wondering if I need to UNLOCK it again and also do I need USB debug on. I cannot boot into OS so unable to set USB debug.
To UNLOCK bootloader can that be done if you can only get into bootloader menu? S-ON is enabled but not 100% that will stop recovering it? That's just for signed rom/firmware and I just need something stock.
You don't need usb debugging on to unlock the bootloader as it is done on fastboot mode (bootloader).
First I suggest you install the O2 firmware only then see whether you can boot to OS (assuming the OS is still stock base)
Second, re unlock bootloader with unlock_code.bin that you can get from htcdev.com, install twrp 3.x and restore the stock backup and relock bootloader and reflash firmware. This will get your device to fully stock.
So far, I don't see any RUU for your device version that you can get for free, only paid site has it.
Tainted said:
I managed to once get into TWRP but cant anymore. It was UNLOCKED but now RELOCKED which I possibly made it a little harder for me.
Click to expand...
Click to collapse
Relocking the bootloader renders the phone unable to boot into OS by definition, as it expects RUU to be run (but as mentioned, RUU is not available for your CID unless you pay - but it's not needed).
Also, you can't flash TWRP with a locked bootloader, again by definition. The primary limitation of an unlocked bootloader, is that it prohibits flashing unsigned recovery images.
So as suggested, simply unlock the bootloader again (with existing unlock bin code, or get a new one using the HTCDev.com process again). Then flash TWRP and a stock TWRP backup using ckpv5's backup collection (linked in his signature).
redpoint73 said:
Relocking the bootloader renders the phone unable to boot into OS by definition, as it expects RUU to be run (but as mentioned, RUU is not available for your CID unless you pay - but it's not needed).
Also, you can't flash TWRP with a locked bootloader, again by definition. The primary limitation of an unlocked bootloader, is that it prohibits flashing unsigned recovery images.
So as suggested, simply unlock the bootloader again (with existing unlock bin code, or get a new one using the HTCDev.com process again). Then flash TWRP and a stock TWRP backup using ckpv5's backup collection (linked in his signature).
Click to expand...
Click to collapse
ok, well made some progress.
unlocked the bootloader the official way. Very quick which I was surprised.
This then repoened up the recovery menu working.
then used fastboot to install latest twrp
then installed S.Team-JW-7.5.0.zip !!!
The install and everything looked good, no errors and now just not turning on. I think now it's a brick? Does not seem to be coming back to the bootloader menu and certainly does not try to boot.
Wondering if end of the line. Any suggestions? I assume need to get into TWRP and flash stock update from ckpv5.
Must say thanks for replies guys. ckpv5 you done some good work on here.
Tainted said:
The install and everything looked good, no errors and now just not turning on. I think now it's a brick? Does not seem to be coming back to the bootloader menu and certainly does not try to boot.
Click to expand...
Click to collapse
It's really hard to brick this phone (especially with s-on) just flashing TWRP and flashing ROMs. Probably not a brick.
At what point exactly did it shut down/not reboot? ROM installed with no errors, and when you tried to reboot, it went dark? You aren't specific on this point.
How much charge was on the battery when you were flashing the ROM? Did you leave it a long time flashing the ROM, or rebooting, that simply may have drained the battery to shutdown?
Try leaving the phone on charger for several hours, then hold power+vol up for a minute or so, and see if any change (even if just stuck on HTC logo screen).
redpoint73 said:
It's really hard to brick this phone (especially with s-on) just flashing TWRP and flashing ROMs. Probably not a brick.
At what point exactly did it shut down/not reboot? ROM installed with no errors, and when you tried to reboot, it went dark? You aren't specific on this point.
How much charge was on the battery when you were flashing the ROM? Did you leave it a long time flashing the ROM, or rebooting, that simply may have drained the battery to shutdown?
Try leaving the phone on charger for several hours, then hold power+vol up for a minute or so, and see if any change (even if just stuck on HTC logo screen).
Click to expand...
Click to collapse
Hi there,
Well I expect the bootloader to be separate from the rest so we can get into TWRP and normally get out of this situation?
The ROM install finished, battery was at about 80% and everything looked good and I let it reboot the phone. And then it went dead. Right now the PC keeps beeping as a device has just connected and then again as though it's disconnected. I'm watching the device manager and dont see it listed during the connect but device manager tree refreshes. My S7 edge shows up. It flash an orage dot twice, so appears to be a in loop.
I charged the phoned and no luck with any of the power+ vol +/- keys. No response from any of those? I let the phone sit till flat and no orange light and then charged it today and still nothing. Not sure if it's a bad battery but it was up at 83% showing in the TWRP menu and working plugged or unplugged.
It's become a challenge now to make it work, I havent had to mod phones since my HTC One which got heavily modded and then back to stock. I stopped doing that after modding every phone I had since HTC Desire Android 2.3. So been about 4 years since doing all this again. Never had one that was totally bricked.
Tainted said:
Well I expect the bootloader to be separate from the rest so we can get into TWRP and normally get out of this situation?
Click to expand...
Click to collapse
You are correct that bootloader (AKA hboot) is a separate partition, isn't touched by TWRP, and in fact is "protected", and can't be modified with s-on. Only an official signed zip (RUU, OTA, zip) can write to hboot when s-on, which is one of the reasons why I say this phone is hard to brick with s-on, just by flashing TWRP and flashing ROMs.
Tainted said:
Right now the PC keeps beeping as a device has just connected and then again as though it's disconnected. I'm watching the device manager and dont see it listed during the connect but device manager tree refreshes.
Click to expand...
Click to collapse
You won't connect to the phone by PC in any way, unless you can get the phone to power on, at least to bootloader.
A few additional suggestions/comments I made to another user (in another thread) who by strange coincidence has a very similar condition (apparent brick after flashing a ROM): https://forum.xda-developers.com/showpost.php?p=73062871&postcount=10
But to be honest, it's not looking too good, since the condition hasn't changed after charging and trying the button combos.
redpoint73 said:
You are correct that bootloader (AKA hboot) is a separate partition, isn't touched by TWRP, and in fact is "protected", and can't be modified with s-on. Only an official signed zip (RUU, OTA, zip) can write to hboot when s-on, which is one of the reasons why I say this phone is hard to brick with s-on, just by flashing TWRP and flashing ROMs.
You won't connect to the phone by PC in any way, unless you can get the phone to power on, at least to bootloader.
A few additional suggestions/comments I made to another user (in another thread) who by strange coincidence has a very similar condition (apparent brick after flashing a ROM): https://forum.xda-developers.com/showpost.php?p=73062871&postcount=10
But to be honest, it's not looking too good, since the condition hasn't changed after charging and trying the button combos.
Click to expand...
Click to collapse
Cheers for that. Not getting much except for the 2 brief flashes of orange light.
Any chance the battery is totally messed and this is the problem?
Tainted said:
Any chance the battery is totally messed and this is the problem?
Click to expand...
Click to collapse
It's possible. Or it might be something else like motherboard or emmc. It's impossible to say for sure.
It doesn't let me update my phone OTA or manually - it says 'we have determined that your phone may be running a modified version of its system software. please revert your phone to the official HTC system software to update.' Phone is locked S-ON, software version 3.35.617.12. What should I do to enable update access to the current version of my phone? Can you send me a link with the appropriate software? If you need any more information, I can send.
P.S. I have bought two identical phones - one for which I was able to update via OTA without no problem, but not the other. They both have S-ON and both are locked.
If you already tried flashing a RUU and that didn't fix the issue then I'd say chances are very high that the phone had been S-OFF in the past and that it's currently using the SuperCID/SCID (11111111) instead of the CID that actually belongs to your current firmware. Unlike on older HTC devices, the SCID breaks the ability to receive official OTAs on the M9. There have been many similar threads to yours in the past. People bought phones that got converted by the sellers before the sale. However, the conversion didn't get completed (in other words: the phones still had the SCID) although the sellers reverted the S-OFF status back to S-ON.
Boot your phone to download mode* and see what CID your phone is using, at the moment. BS_US001 or BS_US002 are both fine. Everything else isn't.
You'll need to re-S-OFF the phone if want to change your phone's CID. The needed instructions can be found in the ReadMe thread (Root & S-OFF, Change the CID).
* Power off the device, wait some seconds and turn it on again while you keep volume down pressed until you see a black screen with red, blue and yellow text. If you see a white screen with multicoloured text then you're facing the Bootloader mode. In that case you can navigate to "Boot to Download Mode" with the volume keys and select the option with the power button.
Unlock bootloader,
flash twrp,
flash root,
s-off for $25
Change cid via "htc_fastboot" to BS_001 or BS_002.
Download the stock FIRMWARE "ZIP" that is the same as your current version*,
rename to 0PJAIMG.zip**,
copy to external sdcard,
put card in the phone and boot the phone to download mode
Press vol+ to flash.
Sit back for 5 mins while it flashes and you'll have an updatable phone at the end. No data lost.
*, the first and third octets must match eg 3.xx.617.xx (xx can be anything). Version and region are important.
** double check the filename as different regions have different filenames. It could be 0PJA10000..
Hello,
I have the same situation but my phone is already S-OFF (locked, scid 11111111).
Do I need Unlock bootloader, flash twrp, flash root or can I go straight to cid change and stock flash?