I know that the new roms use a new kernel now.
I'm on 1.14 Hboot
S-ON
*UNLOCKED
*TAMPERED
I am rooted (Not sure if supercid but I assume so)
Since you have to be on 3.18 now, and be S-OFF, Do I have to go back to stock, do official 3.18 OTA and then unlock bootloader and root again?
I'm kind of confused.
(At&t One X)
The best way to do it is just to become s-off and then run the RUU. You need to have SuperCID to get s-off so you'll need to clarify that first. Boot into bootloader, connect your phone to pc (I'm assuming you have adb/fastboot installed on your pc), make sure it says fastboot usb on your phone screen, then open a command prompt in your fastboot folder and issue the following command:
fastboot oem readcid
Hopefully it'll come up as 11111111 or 22222222 and you can continue to the s-off thread here. If it turns out you don't have SuperCID, you'll need to do that first.
While you're doing that you might as well start downloading the 3.18 RUU, then run it once you've completed the previously mentioned steps.
Once the RUU is finished you'll need to flash a custom recovery again, I recommend using TWRP 2.6. Use the following commands:
fastboot flash recovery "TWRP.img"
(Whatever the exact name of the recovery file is, without the talking marks)
fastboot erase cache
fastboot reboot-bootloader
Now you should be able to select recovery and flash whatever ROM you want to.
Sent from my Evita
timmaaa said:
The best way to do it is just to become s-off and then run the RUU. You need to have SuperCID to get s-off so you'll need to clarify that first. Boot into bootloader, connect your phone to pc (I'm assuming you have adb/fastboot installed on your pc), make sure it says fastboot usb on your phone screen, then open a command prompt in your fastboot folder and issue the following command:
fastboot oem readcid
Hopefully it'll come up as 11111111 or 22222222 and you can continue to the s-off thread here. If it turns out you don't have SuperCID, you'll need to do that first.
While you're doing that you might as well start downloading the 3.18 RUU, then run it once you've completed the previously mentioned steps.
Once the RUU is finished you'll need to flash a custom recovery again, I recommend using TWRP 2.6. Use the following commands:
fastboot flash recovery "TWRP.img"
(Whatever the exact name of the recovery file is, without the talking marks)
fastboot erase cache
fastboot reboot-bootloader
Now you should be able to select recovery and flash whatever ROM you want to.
Sent from my Evita
Click to expand...
Click to collapse
I'm trying to get back to stock.
Just sick of this phone.
I didn't know about the 2.20 to 3.18 bricking problem with s-on. so I bricked my phone. warranty replacement on it. got the new on, did the ota update to 3.18. used hasoon's tool to root and unlock the bootloader. got soff, downgraded my touch to use the cm10.1 nightly. and just have had a TON of problems since.
phone turning off, getting stuck in boot loops. tried going to cm10.0 and had the same issues, was able to load a backup from the htc sense rom before I put CM on and even that will reboot and get stuck in a boot loop.
I wish I hadn't touched the damn thing.
Now I'm scared to run the RUU 3.18 because last time it bricked my phone.
I do have my boot loader unlocked, on hboot 2.14 and have s-off.
Should I be okay to run that RUU you listed?
Yeah if you're s-off you can just run the RUU and you'll be back to stock.
Sent from my Evita
timmaaa said:
Yeah if you're s-off you can just run the RUU and you'll be back to stock.
Sent from my Evita
Click to expand...
Click to collapse
Thank you so much! I followed everything you said and it worked, only problem is the TWRP, it freezes for a sec when I click to reboot and then goes unresponsive until it restarts.
Related
If you're constantly getting ERROR 155 when trying to flash an RUU even though you've already returned your phone to stock, you also need to RELOCK the bootloader!
I'm writing this because for some reason just getting the phone back to stock (i.e. restore image of stock ROM through custom recovery then flash stock recovery) didn't work for me. It only worked after I RELOCKED the bootloader.
Step 0. Restore your phone to stock FIRST, i.e. restore stock ROM from image using custom recovery then flash stock recovery.
Step 1. Restart your phone into bootloader either by hard-off (i.e. keep power button pressed for min. 10 sec) then volume up + power button or by adb at the command prompt:
Code:
C:\> adb reboot-bootloader
Step 2. Type this command at the command prompt:
Code:
C:\> fastboot oem lock
Don't worry if it says FAILED anywhere in the output, it should all be fine regardless. The phone should reboot automatically into bootloader and should say RELOCKED.
Now you can flash any RUU (EDIT: only if compatible with your CID) and you can also check for and install OTA updates. Once you've done this, your HBOOT and RADIO should be updated to the latest version so you can UNLOCK again using the HTCDev method and then flash whatever you want to flash.
Hope this helps you guys!
P.S. I think it's worth also trying this for other ERROR codes... you never know, it may help.
Getting error 131 didn't help. But much thanks for trying help
i hear voices in my head
Any RUU or still only the specific carrier RUU?
Sent from my HTC One S using xda premium
I think the prob is that i have VODAP102 CID in ruu 1.5... and 1.78
i hear voices in my head
had that error too, worked for me with locking bootloader
again, starting ruu-exe after that.
thanks
ovimunt said:
If you're constantly getting ERROR 155 when trying to flash an RUU even though you've already returned your phone to stock, you also need to RELOCK the bootloader!
I'm writing this because for some reason just getting the phone back to stock (i.e. restore image of stock ROM through custom recovery then flash stock recovery) didn't work for me. It only worked after I RELOCKED the bootloader.
Step 0. Restore your phone to stock FIRST, i.e. restore stock ROM from image using custom recovery then flash stock recovery.
Step 1. Restart your phone into bootloader either by hard-off (i.e. keep power button pressed for min. 10 sec) then volume up + power button or by adb at the command prompt:
Code:
C:\> adb reboot-bootloader
Step 2. Type this command at the command prompt:
Code:
C:\> fastboot oem lock
Don't worry if it says FAILED anywhere in the output, it should all be fine regardless. The phone should reboot automatically into bootloader and should say RELOCKED.
Now you can flash any RUU (EDIT: only if compatible with your CID) and you can also check for and install OTA updates. Once you've done this, your HBOOT and RADIO should be updated to the latest version so you can UNLOCK again using the HTCDev method and then flash whatever you want to flash.
Hope this helps you guys!
P.S. I think it's worth also trying this for other ERROR codes... you never know, it may help.
Click to expand...
Click to collapse
now I get error 132 : signature error. I have superCID help?
I don't know how you can sort out the CID issue. I have a SIM free phone so I haven't really looked into that. Sorry....
are you refering to recovery stock (step 1)?
i get error 155 but i have stock recovery and locked bootloader,
my bootloader says security warning though which is strange.
current rom is the ir1 modaco stock rom
i had 155, i put stockrecovery back and relocked bootloader, then 155 changed to battery too low error, so turned it off, charged for 2hrs, and the ruu worked for the first time
I have HTC One S z560e and i want to go back to stock but even with the bootloader unlocked i still get 155error.... what should i do?
Hey people.
Can someone tell what version of RUU i can use for HTC one S4 im in portugal?
Tks
Aplogies if this is not the best starting point but have been reading for 10 hours and am reluctant to take a next step after failure of s-off that has stuck phone in bootloader.
Details
Copied all SD card data to PC
Rooted phone as described by HTCdev
Used SKG utility to attempt s-off
Controlbear got stuck in some strage loop waiting for device after process had started. Never even got prompted to try the wire trick :-( 30 mins later I had to pull the pin
rebooting phone gave me the Controlbear black screen with Green arrow but could now not connect to the device using controlbear just said waiting for device then press any key to exit
Phone will not boot to android OS
when USB connected to phone in bootloader it says FASTBOOT USB and
fastboot devices lists my connected device so USB is OK
Followed instructions at unlimited.io/troubleshooting to try to recover controlbear -f seemed to do somthing so then did
fastboot flash boot recovery_backup.img
which failed could not find image !!!!! der
downloaded 4ext recovery.img
fastboot flash boot recovery.img
worked
Now have
Details of boot
*** UNLOCKED ***
Pyramid PVT SHIP S-ON RL
HBOOT 1.27.0000
Radio 11.24.3504.10_M
OpenADSP-v)2.6.0.2226.00.0131
cMMC-boot
CID reported by fastboot getvar cid is BM__001
Just tried everything from bootloader but always got back bootloader screen no Controlbear screen with arrow as before
At a whim I ran the controlbear -f again and whammo it came up with the 4ext recovery which I was happy to see. Despite doing a backup before starting anything 4ext says no backup present :-(
How can I recover device? I have downloaded the Bell stock RUU which should be correct for this device. Running it says device image version is 3.32.666.13Hesitant to try anything without some good advice. Hopefully I can recover and try the s-off agin but it's been a painful ride. Is it just as simple as clicking update on the RUU exe?
thanks
The backups are not present its saying when you are doing controlbear -f
That means you have no backup present in that controlbear folder
This can be either because of
1.you have another copy of controlbear folder where you done the soff process and where the controlbear saved the backups
(there will be boot_backup.img, recovery_ backup.img)
2.you deleted those images from the controlbear folder
Now what you can do is
1.just find the boot_backup.img and flash it via bootloader
fastboot flash boot boot_backup.img
That will get you out of the Juopunutbear screen..
No need to run the ruu in this case
Edit: and with regards to the 4EXT backup.. The backup will be stored in sdcard and during soff process the sdcard will be wiped.. That's why 4EXT said no backup present.. Just format your sdcard again.. Copy the sdcard backup from your pc (at least copy the Clockworkmod/backup folder to sdcard with the same path in sdcard... It holds your rom backup if you did any)
Then try the 4EXT backup
Sent from my pyramid.. Through blazing fast sonic waves
If your problem was solved, it's a good idea to add [SOLVED] to the topic.
Still in trouble
HI thanks for the advice. Went to the io help and they said relock boot and reflash RUU. Now I have not RUU'd at all as have not been able to find a suitable one. But did fastboot oem lock as suggested. Can I now unlock it again as your post made way more sense and I found the recovery stuff you are speaking of. Just need to unlock and I should be able to recover. is there an unlock command?
markwatson said:
HI thanks for the advice. Went to the io help and they said relock boot and reflash RUU. Now I have not RUU'd at all as have not been able to find a suitable one. But did fastboot oem lock as suggested. Can I now unlock it again as your post made way more sense and I found the recovery stuff you are speaking of. Just need to unlock and I should be able to recover. is there an unlock command?
Click to expand...
Click to collapse
Copy the unlock_code.bin to the folder with adb & fastboot.
Then
Code:
fastboot flash unlocktoken unlock_code.bin
Also, please come down to this channel for support. (I'm only going to help there because you used the tool)
SOLVED
Solved Problem
Hi All Thanks to some sterling efforts by KGS1992 my problem was solved. Take care ye all to ensure that you ensure you get the correct version of controlbear there are many and you need the correct one for your android version. I'll post a detailed summary tomorrow I'm bushed.
I don't like starting new threads especially but I have searched and searched and not come up with an answer/problem quite the same as mine. I am not a TOTAL noob and do understand s-on, s-off, htcdev unlock etc. Here goes
I got a Sensation from a friend who acuired it from God knows when but he asked me if it can be fixed. Its currently stuck in fastboot mode. Its Locked S-OFF however NOTHING I try works. Here is some info
BOOTLOADER
*** Locked ***
PYRAMID PVT SHIP S-OFF RL
HBOOT-1.27.0000
eMMC-boot
Jan 13 2012,17:33:34
CID
Is already Super CID = 11111111
RECOVERY
There is no custom recovery flashed and trying to flash recovery via fastboot fails saying "remote: not allowed"
FASTBOOT COMMANDS
Fastboot commands work to get cid etc but get a "remote: not allowed" to erase or flash boot,img, any rom or any hboot or ANYTHING
BOOTLOADER FLASHING
If I try to flash a firmware file through Bootloader, it parses the P58IMG.zip but fails on Bootload saying Fail-PU Partition update failed
FLASH SHIPPED RUU
Trying a shipped ROM also fails. Goes smoothly, reads current image on phone as 1.45.401.3 but once it starts updating, it sticks in waiting for boatloader and gives ERROR[171] while phone has restarted in FASTBOOT mode
HTCDEV Unlock
I thought I would give the HTCDEV method a go even though I know this is redundant since I am already supposedly s-off but even that fails cuz no lock, unlock screen comes up. Flashing of Unlock_boot.bin goes fine
I am at a TOTAL loss now cuz since I am already S-OFF, I should have been able to flash recover or flash a rom or boot image to get phone working again. NOTHING works!!
Any ideas anyone? Apologies if this has been covered before and I couldnt find it.
tabi13 said:
I don't like starting new threads especially but I have searched and searched and not come up with an answer/problem quite the same as mine. I am not a TOTAL noob and do understand s-on, s-off, htcdev unlock etc. Here goes
I got a Sensation from a friend who acuired it from God knows when but he asked me if it can be fixed. Its currently stuck in fastboot mode. Its Locked S-OFF however NOTHING I try works. Here is some info
BOOTLOADER
PYRAMID PVT SHIP S-OFF RL
HBOOT-1.27.0000
eMMC-boot
Jan 13 2012,17:33:34
CID
Is already Super CID = 11111111
RECOVERY
There is no custom recovery flashed and trying to flash recovery via fastboot fails saying "remote: not allowed"
FASTBOOT COMMANDS
Fastboot commands work to get cid etc but get a "remote: not allowed" to erase or flash boot,img, any rom or any hboot or ANYTHING
BOOTLOADER FLASHING
If I try to flash a firmware file through Bootloader, it parses the P58IMG.zip but fails on Bootload saying Fail-PU Partition update failed
FLASH SHIPPED RUU
Trying a shipped ROM also fails. Goes smoothly, reads current image on phone as 1.45.401.3 but once it starts updating, it sticks in waiting for boatloader and gives ERROR[171] while phone has restarted in FASTBOOT mode
HTCDEV Unlock
I thought I would give the HTCDEV method a go even though I know this is redundant since I am already supposedly s-off but even that fails cuz no lock, unlock screen comes up. Flashing of Unlock_boot.bin goes fine
I am at a TOTAL loss now cuz since I am already S-OFF, I should have been able to flash recover or flash a rom or boot image to get phone working again. NOTHING works!!
Any ideas anyone? Apologies if this has been covered before and I couldnt find it.
Click to expand...
Click to collapse
Have you tried playing with fastboot commander? Mabe try formatting all partitions, then installing RUU or PG58IMG ?Or try with different RUUs? The last thing I can think of is to lock the bootloader back, and try to send it to HTC with warranty.
Even fastboot commander, the same as entering commands manually can not flash anything or erase any partition. Dead end there.
tabi13 said:
Even fastboot commander, the same as entering commands manually can not flash anything or erase any partition. Dead end there.
Click to expand...
Click to collapse
what about locking it back to s-on? did you tried it? does it "run" a custom rom ?
First off to use all the fastboot commands you need to have a eng Hboot on the device. You can not use all fastboot commands with a stock Hboot which is what the Hboot 1.27.0000 that you have is. Click on this link to download the JuopunutBear eng Hboot and follow the below instructions to flash it via fastboot.
Code:
fastboot erase cache
fastboot oem rebootRUU
fastboot flash zip jb_hboot.zip
If you still can not get the device up and going using fastboot after flashing the eng Hboot, or if the Hboot will not flash you may have screwed up partitions on the the device. There is a fastboot or a adb command you can use to get a read out of the partitions but I can not remember it right now, just google it you will find it. I mention this because of the "Fail-PU Partition update failed" message you mentioned.
If it does flash the eng Hboot then you should be able to flash a custom recovery or anything else you want to flash via fastboot. If all else fails though do as gallardo5 sayed and flash the stock ROM via RUU while in fastboot and connected to your computer via USB. Then you can try to start from scratch rooting and installing a custom recovery.
T-Macgnolia said:
First off to use all the fastboot commands you need to have a eng Hboot on the device. You can not use all fastboot commands with a stock Hboot which is what the Hboot 1.27.0000 that you have is. Click on this link to download the JuopunutBear eng Hboot and follow the below instructions to flash it via fastboot.
Code:
fastboot erase cache
fastboot oem rebootRUU
fastboot flash zip jb_hboot.zip
If you still can not get the device up and going using fastboot after flashing the eng Hboot, or if the Hboot will not flash you may have screwed up partitions on the the device. There is a fastboot or a adb command you can use to get a read out of the partitions but I can not remember it right now, just google it you will find it. I mention this because of the "Fail-PU Partition update failed" message you mentioned.
If it does flash the eng Hboot then you should be able to flash a custom recovery or anything else you want to flash via fastboot. If all else fails though do as gallardo5 sayed and flash the stock ROM via RUU while in fastboot and connected to your computer via USB. Then you can try to start from scratch rooting and installing a custom recovery.
Click to expand...
Click to collapse
Oh yes, I should have mentioned it. I did even try flashing the JB-hboots, both GB and ICS versions. Neither worked.
It gives error on erase cache, oem rebootRUU reboots back to fastboot and then flashing fails
I think you are spot on about the partitions about being mssed up. Even if they can be read out (i saw the commands somewhere myself) can they be repaired at all?
p.s. Thanks for your help
One more thing I should have mentioned and dont know how I missed, the FASTBOOT page says *** Locked *** not *** Unlocked ***. I dont know if this can/should be changed.
I am sorry in advance if I am being silly
tabi13 said:
One more thing I should have mentioned and dont know how I missed, the FASTBOOT page says *** Locked *** not *** Unlocked ***. I dont know if this can/should be changed.
I am sorry in advance if I am being silly
Click to expand...
Click to collapse
If you have a messed up partition you can not fix it without replacing the whole board. And about the locked in fastboot that is why your fastboot commands are not working. But the fact that you can not flash the eng Hboot sorta tells me you got a bad partition and it will not take the flash. Blackwing had the same issue with his Sensation and all the best guys I know that are over on the IRC Help Now channel could not come up with a fix and finally diagnosed it as bad partitions. Hid was the exact same it would give aerroron erase cache. Find the command to get a read out on the partitions and post the read out here.
T-Macgnolia said:
If you have a messed up partition you can not fix it without replacing the whole board. And about the locked in fastboot that is why your fastboot commands are not working. But the fact that you can not flash the eng Hboot sorta tells me you got a bad partition and it will not take the flash. Blackwing had the same issue with his Sensation and all the best guys I know that are over on the IRC Help Now channel could not come up with a fix and finally diagnosed it as bad partitions. Hid was the exact same it would give aerroron erase cache. Find the command to get a read out on the partitions and post the read out here.
Click to expand...
Click to collapse
Tmac.. I solved one guys FAIL-PU errors.. If the op can boot to recovery.. Maybe we can fix it.. Remember I said we CAN so there's a possibility
Edit: but not now.. Or at least until 20th August.. I'm out of station (as I need to do remotely everything)
Sent from my HTC Sensation 4G using xda premium
gameshp, let me know when you can help me out. IF my friend hasnt given up by then. Thank you
I have the same situation, so I'm really hoping for a solution.
-Revolutionary-
PYRAMID PVT SHIP S-OFF RL
HBOOT-1.27.1100
eMMC-boot
Jan 13 2012,17:33:34
hey ppl im ready ..check your PM's ..and let me know
Did you try to navigate back to "HBOOT" and do a "Factory reset"?
If it does not work, maybe you should flash firmware using JTAG.
marcusgolden said:
I have the same situation, so I'm really hoping for a solution.
-Revolutionary-
PYRAMID PVT SHIP S-OFF RL
HBOOT-1.27.1100
eMMC-boot
Jan 13 2012,17:33:34
Click to expand...
Click to collapse
No you don't have the same problem, cause your bootloader is unlocked
Flash the firmware again and try to flash recovery
I've looked everywhere for something like this, and so far no one has experienced this.
Okay, so check this out:
I've already rooted and S-Off and SuperCID and all of that, the works. Had ViperROM XL and everything. I got curious to try out KarbonRom 4.4, and tried to flash it in TWRP, didn't work obviously, blah blah blah, short story is, I RELOCKED and installed the AT&T 3.18 RUU. At that point, TAMPERED was gone, and I had RELOCKED there instead, S-Off and SuperCID persisted.
I used the WinDroid Toolkit to originally root and S-Off my Evita. I tried it again. I succeeded in unlocking the bootloader, no problems there. When I go to flash TWRP on it, it says it succeeds. Now, here's when things get weird: I go to push Superuser, and at first it gave me all kinds of hassle, saying the toolkit wasn't detecting my phone, to saying it failed and to try again in a few moments. It was only until I booted back to stock and tried pushing Superuser that it gave me a success message and began to reboot to recovery. It's here that the phone fails to do this, every time. The screen goes black, and when plugged into my PC a Found New Hardware message pops up, asking me to search for drivers for QHSUSB_DLOAD, or something or other. I'm like, "no, that's not right." So after figuring out the 2-button reset to go back to HBOOT, I try to manually boot into recovery; no dice. Same results. So basically, I cannot access any recovery. Furthermore, my HBOOT says UNLOCKED and S-Off and CID-11111111, but TAMPERED is MIA. Not sure if that has anything to do with this, but I certainly did not have this problem the first time I unlocked everything. For your information, I'm on 2.14 HBOOT, 3.18 RUU. Thanks for any points in the right direction.
First thing, you didn't need to relock your bootloader to run the RUU, having s-off means that isn't necessary. Secondly, ditch the toolkit, it's unnecessary and causing problems.
I think you're possibly a bit confused about what you need to be doing. If your end goal was to flash a KitKat ROM why were you attempting to root the stock ROM? The tampered flag is missing from your bootloader because you don't have a custom recovery installed. Exactly which version of TWRP did the toolkit say it was installing? Hopefully all you need to do is flash a working recovery, then you can flash a ROM.
Download the modified version of TWRP 2.6.3.0 from here. Put the file in your fastboot folder. Connect phone in fastboot mode, open command prompt from within fastboot folder, issue the following commands:
Code:
fastboot flash recovery "filename.img"
(the exact filename, minus the talking marks)
Code:
fastboot erase cache
Code:
fastboot reboot-bootloader
Now hopefully you can enter recovery.
Sent from my Evita
timmaaa said:
First thing, you didn't need to relock your bootloader to run the RUU, having s-off means that isn't necessary. Secondly, ditch the toolkit, it's unnecessary and causing problems.
I think you're possibly a bit confused about what you need to be doing. If your end goal was to flash a KitKat ROM why were you attempting to root the stock ROM? The tampered flag is missing from your bootloader because you don't have a custom recovery installed. Exactly which version of TWRP did the toolkit say it was installing? Hopefully all you need to do is flash a working recovery, then you can flash a ROM.
Download the modified version of TWRP 2.6.3.0 from here. Put the file in your fastboot folder. Connect phone in fastboot mode, open command prompt from within fastboot folder, issue the following commands:
Code:
fastboot flash recovery "filename.img"
(the exact filename, minus the talking marks)
Code:
fastboot erase cache
Code:
fastboot reboot-bootloader
Now hopefully you can enter recovery.
Sent from my Evita
Click to expand...
Click to collapse
Thanks for the swift reply, I'm gonna go ahead and give this a try. To answer your question, through trying to flash KarbonRom, I wiped and factory reset without backing anything up, silly, I know, but I live a little too dangerously I suppose. I tend to get to cocky with this stuff, through all the devices I've rooted and so on. After failing to flash it, I knew I was stuck, which is why I came to the conclusion the only way out was to revert to stock RUU. If there was anything else I could do, I wasn't thinking of it. In hindsight, I suppose I could have ADB Sideloaded Viper XL again. Also, I was unaware that I didn't need to relock the bootloader to install the stock RUU, this is news to me, so thank you for that. I'll reply again after trying your link.
EDIT: This worked, thank you again. You've made me wiser in the ways.
One thing I forgot to mention. The QHSUSB_DLOAD that your phone was showing up as when connected to your PC usually means that a device is bricked. So, under no circumstances should you use that toolkit ever again, because whatever it was doing wasn't good at all.
Sent from my Evita
timmaaa said:
One thing I forgot to mention. The QHSUSB_DLOAD that your phone was showing up as when connected to your PC usually means that a device is bricked. So, under no circumstances should you use that toolkit ever again, because whatever it was doing wasn't good at all.
Sent from my Evita
Click to expand...
Click to collapse
Thanks for the heads up, I'll keep it in mind. It seems the most reliable way to do this stuff is just do it yourself. I'm still green to the ways of adb and fastboot, I've always let one-clicks and toolkits do the work for me, but I'm learning that just doing it yourself is the most reliable method. Thanks again, man, your insight has always helped me out of tough situations.
Doing it yourself is definitely the most reliable method. It might seem daunting at first, but I can assure you it's totally simple, and once you've done it a couple times you'll see that. The manual way is the best way, hands down. A bonus is that it feels great to learn something and to have an extra bit if control over your device.
Sent from my Evita
I'm having a problem with my One X and returning it to stock. I've been rooted with S-ON for quite some time now and had the Viper ROM installed. Now it's time to trade it in to Amazon and I wanted to return it to stock and hopefully remove the tampered text. I seem to have gotten myself in to a pickle though and I'm stuck at the bootloader.
I've been using the WinDroid Universal HTC Toolkit to install stuff, I have the unlock.bin file from HTC, and I've been able to communicate with the phone through my Windows 7 computer no problem. But after the last attempt I relocked the phone and not I'm stuck. Here's what it says on the bootloader screen:
*** TAMPERED
*** RELOCKED
*** Security Warning
EVITA PVT SHIP S-ON RL
HBOOT-1.09.0000
Using the WinDroid kit it shows that it successfully unlocked the bootloader and loaded TWRP, but since it's in fastboot, WinDroid doesn't recognize the phone model and won't let me send any files to it though. When I reboot the phone in to recovery, it returns me to the bootloader.
Anyone have any advice?
First piece of advice: ditch the toolkit, you don't need it. The best way for you to go about this is to follow these steps:
1) Unlock the bootloader again.
2) Flash TWRP again.
3) Flash a ROM.
4) Get s-off (this is the most important step, and all the previous steps were all leading to this).
5) Run an at&t RUU (to return the phone to stock, I'm assuming it's the at&t model?).
6) Return the CID to the original CID.
Code:
fastboot oem writecid CWS__001
7) Relock the bootloader.
Code:
fastboot oem lock
8) Return the phone to s-on.
Code:
fastboot oem writesecureflag 3
Voila.
Sent from my Evita
Wow. Nice Tim !!!
Sent from my Inspire 4G using Tapatalk
Thanks for the help so far. Under your advice I'm using fastboot commands manually to try and get this to work. So now I'm unlocked again, but I'm having a problem flashing TWRP. I downloaded the latest TWRP for the Evita and ran fastboot flash recovery evita.img (that's what I renamed the file to). It tells me that sending and writing was OKAY, so it should work. Then I try to reboot to recovery from the bootloader menu, and it fails after this. It appears to boot something up, I get a blank screen, then it reboots again on it's own without showing the TWRP menus.
What am I doing wrong?
You can't reboot to the recovery, you can only reboot to the bootloader and then manually select recovery using the hardware buttons (volume = scroll, power = select). The whole process should go like this:
Code:
fastboot flash recovery evita.img
Code:
fastboot erase cache
Code:
fastboot reboot-bootloader
Now you can manually select recovery and it should hopefully boot into it.
Sent from my Evita
That's what I did, although I just tried these steps again. When I used the volume/power buttons and chose recovery, it reboots as it should, then it tries to load the recovery, fails, then reboots and starts up the phone. I should note, and this might be the problem, is that phone boots up totally in to the full blown OS. It's Android 4.1.1 with the 3.18 kernel.
I have SuperCID, and the phone says it is unlocked with S-ON.
Does it make sense and try to flash the 2.15 firmware at this point since my HBOOT is older?
I tried another thing since I can actually use the phone and I'm rooted, I installed GooManager from the store and let that install the recovery then rebooted. It did the same thing. At the very least, if I could only get TWRP working I could recover a TWRP backup I made.
And ultimately, the phone works at this point, I just want to remove the tampered text and keep it at stock. Since I have a working ROM, should I just follow your steps 6, 7 and 8? Do I still need to achieve S-Off and worry about the recovery?
You need s-off, otherwise running the RUU will brick your phone. Just try getting s-off without the recovery. Which ROM is currently installed?
Sent from my Evita
I have an AT&T stock deodexed ROM version 3.18.502.6.
Ok, scratch that, without root you cannot get s-off. What's the exact filename of the recovery you've tried to flash?
Sent from my Evita