Not sure if this is really a tip or not, but this worked for me. I hate seeing that "Tampered" warning in my Bootloader.
Now that I am S-OFF, when I flash a new radio via fastboot, then reboot my bootloader, the "Tampered" warning goes away. Can anyone else confirm this? Thanks.
Sent from my HTC One S using xda app-developers app
Did you use fastboot flash radio radio.img?
Sent from my HTC One S using Tapatalk 2
blackwing182 said:
Did you use fastboot flash radio radio.img?
Sent from my HTC One S using Tapatalk 2
Click to expand...
Click to collapse
Yes
Sent from my HTC One S using xda app-developers app
I attempted to flash the new 1.13 radio, but it failed, however, my "Tampered" warning disappeared.
Sent from my HTC One S using xda app-developers app
troby86 said:
I attempted to flash the new 1.13 radio, but it failed, however, my "Tampered" warning disappeared.
Sent from my HTC One S using xda app-developers app
Click to expand...
Click to collapse
Did you run any othe comand, like fastboot reboot bootloader or something?
Sent from my HTC One S using Tapatalk 2
Just tried flashing a radio zip and I still have tampered.
blackwing182 said:
Did you run any othe comand, like fastboot reboot bootloader or something?
Sent from my HTC One S using Tapatalk 2
Click to expand...
Click to collapse
Yea, after "fastboot flash radio radio.img" I ran "fastboot reboot-bootloader"
Sent from my HTC One S using xda app-developers app
Darknites said:
Just tried flashing a radio zip and I still have tampered.
Click to expand...
Click to collapse
No, flash it via fastboot
Sent from my HTC One S using Tapatalk 2
Darknites said:
Just tried flashing a radio zip and I still have tampered.
Click to expand...
Click to collapse
Flash the radio.img via fastboot, not the zip.
Sent from my HTC One S using xda app-developers app
Here's exactly what I did:
Downloaded the new OTA that Behold provided yesterday.
Unzipped it, then unzipped the firmware zip that was inside.
Pulled the radio.img from inside the firmware folder.
Flashed the radio via fastboot, (it will probably fail depending on your HBOOT) then rebooted my bootloader, and the "Tampered" was gone and hasn't came back.
Sent from my HTC One S using xda app-developers app
blackwing182 said:
No, flash it via fastboot
Sent from my HTC One S using Tapatalk 2
Click to expand...
Click to collapse
Ya I trying to be lazy lol but will try that in a bit.
Writing radio with fastboot flash radio fails here, doesn't matter which one. hboot is 1.06, device is s-off.
D:\Android\android-sdk\platform-tools>fastboot flash radio radio.img
sending 'radio' (34345 KB)...
OKAY [ 2.590s]
writing 'radio'...
FAILED (remote: not allowed)
finished. total time: 2.621s
fastboot reboot-bootloader right after didn't do the trick as well. ****
This didn't work for me either with hboot 1.06/s-off. I understood we needed and engineering hboot to flash a radio from fastboot.
I have hboot 1.06, before s-off i can flash radio with fastboot without any problem, with S-OFF i can't flash with fastboot.
But i can flash on recovery with this Sense-Radio-Installer-V4.zip
http://forum.xda-developers.com/showthread.php?t=1998270
troby86 said:
Here's exactly what I did:
Downloaded the new OTA that Behold provided yesterday.
Unzipped it, then unzipped the firmware zip that was inside.
Pulled the radio.img from inside the firmware folder.
Flashed the radio via fastboot, (it will probably fail depending on your HBOOT) then rebooted my bootloader, and the "Tampered" was gone and hasn't came back.
Sent from my HTC One S using xda app-developers app
Click to expand...
Click to collapse
whats your hboot? and can you link me to the thread of the radio you used. thx
veeny101 said:
whats your hboot? and can you link me to the thread of the radio you used. thx
Click to expand...
Click to collapse
The link is in the General thread named "Just another 50mb update"....I am on HBOOT 1.14
Again, the radio flash failed, which is what I expected, but the warning did disappear for me.
Sent from my HTC One S using xda app-developers app
troby86 said:
The link is in the General thread named "Just another 50mb update"....I am on HBOOT 1.14
Again, the radio flash failed, which is what I expected, but the warning did disappear for me.
Sent from my HTC One S using xda app-developers app
Click to expand...
Click to collapse
I will try it now. Hope it works. Crossed Finger.
Tried it, it pretended to be successful but was not and tampered is still there. I am on hboot 1.06 with s-off.
troby86 said:
Not sure if this is really a tip or not, but this worked for me. I hate seeing that "Tampered" warning in my Bootloader.
Now that I am S-OFF, when I flash a new radio via fastboot, then reboot my bootloader, the "Tampered" warning goes away. Can anyone else confirm this? Thanks.
Sent from my HTC One S using xda app-developers app
Click to expand...
Click to collapse
Interesting. I'll try this method on my HTC One XL. So far it hasn't worked, but I'm very curious now. My HOX has HBOOT 1.09 so I guess it might not work. Regardless I'm going to experiment.
LibertyMonger said:
Tried it, it pretended to be successful but was not and tampered is still there. I am 0n hboot 1.06 with s-off.
Click to expand...
Click to collapse
Same... HBoot 1.06 with S-Off... still showing Tampered
Related
Is it possible?
I atomize if this had been answered but the xda app Darcy function is pretty "meh".
Sent from my HTC Sensation using xda premium
Sleef said:
Is it possible?
I atomize if this had been answered but the xda app Darcy function is pretty "meh".
Sent from my HTC Sensation using xda premium
Click to expand...
Click to collapse
Not possible
Sent from my HTC Sensation XE with Beats Audio Z715e using xda premium
Hrm.
Well, I am on bootloader 1.20 without super cid. The zip meant to roll me back to 1.17 is giving me an error about an incorrect model id.
Sleef said:
Hrm.
Well, I am on bootloader 1.20 without super cid. The zip meant to roll me back to 1.17 is giving me an error about an incorrect model id.
Click to expand...
Click to collapse
You need to add your CID and MID into.android-info.txt in the zip file.
fastboot getvar cid
fastboot getvar mid
Those are the commands I think
Sent from my HTC Sensation XE with Beats Audio Z715e using xda premium
Gotcha. At that point, I should be able to use fastboot to super cid then flash the new firmware, correct?
Sleef said:
Gotcha. At that point, I should be able to use fastboot to super cid then flash the new firmware, correct?
Click to expand...
Click to collapse
Won't be able to use fastboot flash because that is an extended fastboot command and the new hboot doesn't support extended, only basic so you will have to flash the PG58IMG.zip through hboot
Sent from my HTC Sensation XE with Beats Audio Z715e using xda premium
Okay. (Intermittently doing work right now. Thanks so much for the help.)
I add my cid and mid info to the zip that rolls me back to 1.17. Have that on my sd and boot into bootloader.
Now, I'd be 1.17, which should allow me to use fasboot to be super cid.
At this point, I can use an update zip for the new firmware, again putting it on the sd card and going into the bootloader.
Am I missing a step?
you can use fastboot on hboot 1.20. just supercid your phone and then flash the zip without changing anything
xxemoeskimoxx said:
you can use fastboot on hboot 1.20. just supercid your phone and then flash the zip without changing anything
Click to expand...
Click to collapse
Awesome. I thought that might be the case but wasn't completely sure.
Sleef said:
Hrm.
Well, I am on bootloader 1.20 without super cid. The zip meant to roll me back to 1.17 is giving me an error about an incorrect model id.
Click to expand...
Click to collapse
I have the same problem but I cannot get my Cid and Mid as Hboot 1.20 does not support the fastboot commands to get these. I've tried and it just hangs on waiting for device.
Hi All,
I am fairly new to all this, I have read countless posts and done everything I can but I am stuck.
I have a HBOOT 2.14 currently with S-ON.
I have installed TWRP in recovery but no custom mods work due to the HBOOT version.
SuperCID is 111111111 and is already set.
I want to be able to S-OFF my device so i can downgrade the HBOOT and use the custom roms.
I ran through the facepalm S-OFF procedure, it all runs correctly, although upon reboot it still says S-ON.
Does anyone know why this would be? Is there something I am missing?
I am doing this some the TWRP recovery mode as that is the only place I can access adb commands currently.
There is no working ROM currently installed, CM 10.1 is installed although it can't be used because the touchscreen doesn't work.
Any information people can provide me to get all this working would be of great help.
Happy to donate/pay someone to help me via teamviewer or whatever.
Thanks,
Tabmowtez
What version of twrp are you using? 2.3.3.1 ?
Sent from my HTC One X using xda premium
Venomtester said:
What version of twrp are you using? 2.3.3.1 ?
Sent from my HTC One X using xda premium
Click to expand...
Click to collapse
v2.4.4.0
I have heard that 2.3.3.1 works better for your hboot and you can also downgrade your touch panel firmware and get cm to work.
Sent from my HTC One X using xda premium
Venomtester said:
I have heard that 2.3.3.1 works better for your hboot and you can also downgrade your touch panel firmware and get cm to work.
Sent from my HTC One X using xda premium
Click to expand...
Click to collapse
Really? I haven't seen this said anywhere? Do you have any references to the procedures or the TP firmware?
There is a thread down the page hboot question that addresses this.
Sent from my HTC One X using xda premium
Venomtester said:
There is a thread down the page hboot question that addresses this.
Sent from my HTC One X using xda premium
Click to expand...
Click to collapse
Yes that's the one I posted, it still requires S-OFF.
It seems all the fixes need S-OFF and that is the one thing I can't seem to get working as there is no ROM installed so I can't use supersu?
Have you tried flashing a sense based Rom like viper using adb to flash boot image? Just to see if you can get phone working?
Sent from my HTC One X using xda premium
Venomtester said:
Have you tried flashing a sense based Rom like viper using adb to flash boot image? Just to see if you can get phone working?
Sent from my HTC One X using xda premium
Click to expand...
Click to collapse
I will download ViperX3.4.0.zip and use the boot.img to flash it from adb and see how it goes.
I have tried AOSP and CM Roms and all have had the same issue of the TP not working though.
I'll see how this goes.
Just to confirm, it seems all ROMS based off of the 3.17 kernel and higher work with S-ON.
I have the HatkaXL-evita-v4.2.5_Sense5Elements ROM working after I did the following steps:
Place boot.img in sdk platform tools folder
Boot phone into fastboot usb
open your command prompt from the sdk files folder. (shift+right click-select open command window)
type: fastboot erase cache
type: fastboot flash boot boot.img
type: fastboot erase cache (just to be safe)
On phone select bootloader, then recovery.
Once TWRP loads (I'm using 2.4.4.0) go to wipe and select factory reset then wipe system and both caches
Then install the rom and go through setup
once setup is complete, UNCHECK restart now so it leaves the rom and goes back to TWRP.
Click on clear cache/davlik and then click reboot
Settings application keeps on crashing so I am going to try the aokp_evita_jb-mr1_build-4 ROM now after a backup.
I still have issues getting adb to recognise the device once the ROM is booted but that's a separate issue for now...
Are you sure your getting error 92 and not 99 when you flash the zip for s-off cause if your getting 99 you need to fastboot write your cid then reboot and try again
Sent from my One X using Xparent Green Tapatalk 2
I'm definitely getting the error 92. My CID is already a SuperCID so would I have to do that again?
I have the ViperX ROM running now so I am happy, would still like to S-OFF though so I can try CM etc. after a hboot downgrade.
Sent from my HTC One X using xda app-developers app
When I did the s-off to my One XL, the error 92 is normal and I just followed the steps in this thread and it worked fine
http://forum.xda-developers.com/showthread.php?t=2155071
That is the same thread I follow, I will try again now that I have a working ROM and see how it goes.
Sent from my HTC One X using xda app-developers app
All good, I successfully S-OFF'd my device and downgraded my hboot to 1.09. Hopefully this means I can put any mod on now without flashing from fastboot first and having the touchscreen work!
Sent from my HTC One X using xda app-developers app
Is there an easier way of rooting after running ruu 3.18 update if I was already s-off?
Sent from my HTC One X using xda premium
If your bootloader is unlocked just flash twrp 2.3.3.1 or under. Then you can flash su or wipe everything and flash a ROM.
Sent from my One X using xda app-developers app
exad said:
If your bootloader is unlocked just flash twrp 2.3.3.1 or under. Then you can flash su or wipe everything and flash a ROM.
Sent from my One X using xda app-developers app
Click to expand...
Click to collapse
I've unlocked bootloader and installed twrp also flashed su and tried to flash CM10. I wiped cashe and and then installed CM10.1 and now it freezes on "HTC quitly briliant" screen and some warning notes under it.. what to do?
Is it necessary tu S-off?
Wipe everything not just cache. Then fastboot flash boot boot.IMG right before or after flashing the ROM. The boot.img should be extracted from the ROM you're flashing.
Sent from my One X using xda app-developers app
exad said:
Wipe everything not just cache. Then fastboot flash boot boot.IMG right before or after flashing the ROM. The boot.img should be extracted from the ROM you're flashing.
Sent from my One X using xda app-developers app
Click to expand...
Click to collapse
Is it necessary to S-off?
Only if you wish to ruu without bricking after supercid
Sent from my Sony Tablet S using xda app-developers app
Wouldn't the ruu lock the bootloader tho?
Nevermind it worked!
Sent from my HTC One X using xda app-developers app
mircony said:
Wouldn't the ruu lock the bootloader tho?
Click to expand...
Click to collapse
No. RUU doesn't "lock" anything. If S-on, you typically need to relock the bootloader to run an RUU (but as mentioned, running the 3.18 RUU with S-on and SuperCID will brick the device).
But with S-off, it doesn't matter if bootloader is locked or not.
I've been running AOSP ROM's on my evita for a while now, but apparently with the 3.4 kernel you now need hboot 2.14 or higher and mine's at 1.09. My phone was unlocked with S-ON, but I did "fastboot oem lock" this morning because I read that it's necessary for an RUU. I downloaded the 2.20 RUU and tried to run the installer but I always get an Error [170] USB Connection Error. I have the HTC and adb drivers installed successfully and have tried to run the RUU as admin in both Sense and fastboot (bootloader). I'm a bit stumped and would really like to get AOSP back on my phone.
You need to S-off first.
Sent from my HTC One X using xda premium
tlazarus said:
You need to S-off first.
Sent from my HTC One X using xda premium
Click to expand...
Click to collapse
Should I use facepalm for that then?
EDIT
I got s-off, but still no go. Still the error 170.
I know on my old Incredible I was able to rename the rom.zip from the RUU as PB99IMG.zip and put it on the root of my sdcard. Then in hboot it would detect it and ask to flash it. This isn't happening on my evita though. Is there a way to do that, or is that only for older htc devices?
Put phone into fastboot and try again. Check error log to see if it fails to identify your phone.
Open command prompt and type adb devices, if it does not see it then try installing new drivers. If it does see it then enter " adb shell reboot oem-78" that will reboot your phone in to RUU ready fastboot. Open ruu and try running it again.
Sent from my HTC One X using xda premium
Venomtester said:
Put phone into fastboot and try again. Check error log to see if it fails to identify your phone.
Open command prompt and type adb devices, if it does not see it then try installing new drivers. If it does see it then enter " adb shell reboot oem-78" that will reboot your phone in to RUU ready fastboot. Open ruu and try running it again.
Sent from my HTC One X using xda premium
Click to expand...
Click to collapse
Where can I find this error log? It did see my device, I did that command (which ended at the black htc screen) and I ran the RUU again but I still get the error 170. I'm also using this RUU http://bugsylawson.com/index.php/fi...320911-2-101053225l-release-271865-signedexe/
Sounds like a bad download. Is it 568.22 mbs? Try roomyshare.com/ruu-evita-ul-cingular.html
You can find it in the list.
Sent from my HTC One X using xda premium
Venomtester said:
Sounds like a bad download. Is it 568.22 mbs? Try roomyshare.com/ruu-evita-ul-cingular.html
You can find it in the list.
Sent from my HTC One X using xda premium
Click to expand...
Click to collapse
It is that size, though I may try the link you gave.
EDIT
Okay, I think I found out what I've been doing wrong. I found this link http://forum.xda-developers.com/showthread.php?t=2119610 and it turns out that the file I've been trying does NOT include the 2.14 hboot that I need. The one I need is the latest JB release, but someone said that if you flash it with superCID and S-ON that it will brick your device. I have superCID but S-OFF, does anyone think that will brick my device? Should I flash the RUU with the 1.09 hboot (which I'm running) first, and then flash the newest RUU? Also, it looks like the link I provided offers flashable OTA's of each update. Would those work/be recommended for TWRP?
Change cid to cingular "cws_001" I think. Super cid can cause brick.
Sent from my HTC One X using xda premium
Venomtester said:
Change cid to cingular "cws_001" I think. Super cid can cause brick.
Sent from my HTC One X using xda premium
Click to expand...
Click to collapse
Well I didn't do that...haha. I read on another forum that TWRP doesn't support that cid check function or something and to just remove it from the updater-script so I tried that and flashed the latest OTA zip in TWRP and it failed after a few steps. I tried booting and it didn't get to the boot animation so I rebooted to recovery and restored my backup. I'm going to try a stock zip without the modified updater-script and restore my CID to normal and try again.
EDIT
Well, I restored the CID to CWS__001 and I still get that check_cid error
dshoe said:
Well I didn't do that...haha. I read on another forum that TWRP doesn't support that cid check function or something and to just remove it from the updater-script so I tried that and flashed the latest OTA zip in TWRP and it failed after a few steps. I tried booting and it didn't get to the boot animation so I rebooted to recovery and restored my backup. I'm going to try a stock zip without the modified updater-script and restore my CID to normal and try again.
EDIT
Well, I restored the CID to CWS__001 and I still get that check_cid error
Click to expand...
Click to collapse
To run a ota you need to flash stock recovery image.. and bootloader needs to be unlocked for that
Sent from my HTC One XL using xda premium
31ken31 said:
To run a ota you need to flash stock recovery image.. and bootloader needs to be unlocked for that
Sent from my HTC One XL using xda premium
Click to expand...
Click to collapse
Hm, okay then, let me ask another question. I'm on hboot 1.09 and I need 2.14 to run AOSP ROM's now. What's the best way to get there if I already have ROM's installed. Is it what I'm doing right now or should it be something else?
EDIT
The latest JB RUU is picking up my device now and offering the update, 2 seconds away from doing it....
dshoe said:
Hm, okay then, let me ask another question. I'm on hboot 1.09 and I need 2.14 to run AOSP ROM's now. What's the best way to get there if I already have ROM's installed. Is it what I'm doing right now or should it be something else?
EDIT
The latest JB RUU is picking up my device now and offering the update, 2 seconds away from doing it....
Click to expand...
Click to collapse
Just make sure you are s-off before running ruu or risk a brick..
Sent from my HTC One XL using xda premium
Hi. I am looking my update my hboot from 1.09 to 2.14. I am S-OFF now, also running the Sense 5 rom now(TWRP recovery).
I have downloaded the Latest JB 3.18 RUU from instructions here http://forum.xda-developers.com/showthread.php?t=2064621.
What else do I need to do before flashing the RUU to the device?
For what it's worth, I was on stock 2.20, got s-off and unlocked bootloader with superCID, and ran the 3.18 RUU with no problems. I didn't need to relock or anything.
knanda said:
Hi. I am looking my update my hboot from 1.09 to 2.14. I am S-OFF now, also running the Sense 5 rom now(TWRP recovery).
I have downloaded the Latest JB 3.18 RUU from instructions here http://forum.xda-developers.com/showthread.php?t=2064621.
What else do I need to do before flashing the RUU to the device?
Click to expand...
Click to collapse
You can go ahead and run the RUU. No real risk because you're s-off. Maybe make a backup though.
Sent from my Evita
i just want to know how you use a ruu? i want to upgrade to 3.18 just dont know how to use the ruu
Just plug in your phone and run it. It's an exe file.
Be sure you're s-off, though, unless you're stock.
Sent from my evita
RollTribe said:
Just plug in your phone and run it. It's an exe file.
Be sure you're s-off, though, unless you're stock.
Sent from my evita
Click to expand...
Click to collapse
i am s-off will i have to re root my phone after i use the ruu?
The RUU will return your phone to completely stock, so of course you will not have root anymore. But, your unlocked bootloader and s-off status will survive the process so all you need to do is flash TWRP again and then you can flash a rooted ROM.
Sent from my Evita
timmaaa said:
The RUU will return your phone to completely stock, so of course you will not have root anymore. But, your unlocked bootloader and s-off status will survive the process so all you need to do is flash TWRP again and then you can flash a rooted ROM.
Sent from my Evita
Click to expand...
Click to collapse
awsome so do i just fastboot flash a recovery?
Yep. I recommend TWRP 2.6
Sent from my Evita
timmaaa said:
Yep. I recommend TWRP 2.6
Sent from my Evita
Click to expand...
Click to collapse
ok oh and timmaaa you the man iv asked questions here before and you always come thru with a good answer
No worries mate. I only ask that you share your knowledge and help others where you can
Sent from my Evita
timmaaa said:
Yep. I recommend TWRP 2.6
Sent from my Evita
Click to expand...
Click to collapse
yo time im having troubles getting twrp 2.6 flashed. when i fastboot flash recovery openrecovery-twrp-2.6.0.0-evita it does nothing?
696kris969 said:
yo time im having troubles getting twrp 2.6 flashed. when i fastboot flash recovery openrecovery-twrp-2.6.0.0-evita it does nothing?
Click to expand...
Click to collapse
You are putting the ".img" on the end of the command right?
Sent from my Evita
I S-OFF'd and ran the 3.18 RUU in order to run CM 10.1 nightlies. I'm thinking about selling this phone, so would I just run the same RUU again in order to return to stock AT&T status?
Sent from my One X using Tapatalk 4
jkel777 said:
I S-OFF'd and ran the 3.18 RUU in order to run CM 10.1 nightlies. I'm thinking about selling this phone, so would I just run the same RUU again in order to return to stock AT&T status?
Sent from my One X using Tapatalk 4
Click to expand...
Click to collapse
You could relock if you want to, but it doesn't really matter.
Sent from my evita
RollTribe said:
Just plug in your phone and run it. It's an exe file.
Be sure you're s-off, though, unless you're stock.
Sent from my evita
Click to expand...
Click to collapse
Maybe a stupid question but does the phone have to be in fastboot mode to run the ruu?
Sent from my HTC One XL using xda premium
MrMiami81 said:
Maybe a stupid question but does the phone have to be in fastboot mode to run the ruu?
Sent from my HTC One XL using xda premium
Click to expand...
Click to collapse
Yes, I believe it does have to be in fastboot.
Sent from my HTC One X using Tapatalk 4
jkel777 said:
Yes, I believe it does have to be in fastboot.
Sent from my HTC One X using Tapatalk 4
Click to expand...
Click to collapse
Yes. Fastboot to run the ruu exe.
Fastboot -----> fastboot oem rebootRUU to use the ruu zip
Fastboot flash zip rom.zip
Sent from my HTC One using Tapatalk 2