Hi everybody,
I unlocked the bootloader of my One S successfully with htcdev.com and next I wanted to flash a recovery image via fastboot, what succeeded. I used this thread:
http://forum.xda-developers.com/showthread.php?t=1583427
But when try to start the recovery, the phone hangs in the boot screen with the red text "This build is for development..." and does not start recovery.
I tried several recovery images for the ville but none could be started.
What i recognized is, that in the Video "How to Install Recovery in HTC One S" in the thread mentioned above, the Bootloader screen locks slightly different, than mine.
First of all, mine only says "Unlocked" but NOT "Tampered" and second the first green line says:
VILLEC2 PVT SHIP S-ON RL
whereas in the video one can see the line
VLE PVT SHIP S-ON RL
I attached a pic of my bootloader.
So I think my phone is a newer One S, right? Is there already working Recovery out there?
Or am I missing something else?
Thx a lot in advance for any hint
Do you have CWM installed?
sure, as I wrote in my first post. I tried several CWM Recovery Images... the interim one, the actual original one for the One S... no image boots...
Well, it doesnt look like the your phone is rooted.
Try TWRP. Quality recovery.
Sent from my HTC VLE_U using xda premium
Tampered means rooted. Everything else looks updated. Try to root then see what happens. You may need to root to flash cwm over stock. Not really sure. I just do both always and they work.
Sent from my HTC VLE_U using xda premium
What am I missing?
I unlocked the Bootloader on htcdev.com, did the whole thing with entering the token, download the Unlock_code.bin, upload it to phone, said "Yes, unlock bootloader" and so on.. and the bootloader sais, it IS unlocked. If it where not, I wouldn't be able at all to flash a recovery image with fastboot, but this also succeeds (fastboot said "OKAY" when uploaded to phone and "OKAY" when flashed), right?
And the next step after unlocking bootloader IS flashing a recovery image like CWM for then using it to flash the Superuser.zip for gaining root, isn't it? Or am I completely wrong?
Try booting normaly and then connecting the phone to your computer and do adb reboot recovery i know i had problems similar to this when i first flashed a recovery and doing that for the first time fixed it
Sent from my HTC One X using Tapatalk 2
You can gain root access through stock recovery as long as you unlocked bootloader. Did you try Hasoon2000's all in one tool kit?
Sent from my HTC VLE_U using xda premium
Yeah Try the adb reboot recovery method, If that fails, flash the superboot root image, then use something like rom manager to download CWM to the phone.
@stumpyz9: This did not work, same as if i would start recovery from Bootloader
@dooshbag45: I re-locked and unlocked the bootloader again, nothing changed, it is "UNLOCKED" but not "TAMPERED". Yes, I also tried Hasoon2000's Root Kit and recognized, it just does nothing other, than 1. unlock bootloader and 2. flash a Recovery Image. This had the identical result...
I meanwhile tried these recoveries:
r2-modaco-recovery-clockwork-touch-ville.img
recovery-clockwork-touch-5.8.2.4-ville.img
recovery-clockwork-touch-5.8.3.1-ville.img
twrp217.img (inculded in Hasoon2000's Kit)
CWM5824.img (inculded in Hasoon2000's Kit)
Now I tried to recover the stock recovery image from the modaco.com site, named "ville_recovery_signed.img"
but this doesn't start either... WTF...
Tampered does not mean ur rooted I had that problem left phone on stock for a week then tried same method again must of been doing Something wrong learn how to do it manually but if u can't download all in one toolkit HTC.one s I think that's what's it called it will unlock bootloader flash and root
Sent from my HTC One S using xda premium
@azzledazzle: the superboot method didn't work either... downloaded it, fastbooted it, the phone boots but..... remains in the red-text screen as it does when try to boot a recovery image .... I really think it has something to do with the newer HBOOT Version and the "VILLEC2" thing.. something in booting images works other than in the version before...
Just download all in one toolkit HTC one s
Sent from my HTC One S using xda premium
@k1llacanon: The All-in-one toolkit didn't work as I posted earlier. This was one of the first things I tried...
I had that problem when rooting mine left it for a week learnt more about my phone and did it and it worked u must be doing Something wrong
Sent from my HTC One S using xda premium
Direct fastboot booting of a recovery image also does not work:
"fastboot boot r2-modaco-recovery-clockwork-touch-ville.img"
same result...
@k1llacanon: This is not the first phone I root... did it with the Wildfire S and the old Desire... it worked the same way... unlock bootloader, flash recovery image.. what can be done wrong with these 2 simple steps? What did you do other?
Have you got
Fastboot (unticked)
USB Debugging (ticked)
snoopy1978 said:
Direct fastboot booting of a recovery image also does not work:
"fastboot boot r2-modaco-recovery-clockwork-touch-ville.img"
same result...
@k1llacanon: This is not the first phone I root... did it with the Wildfire S and the old Desire... it worked the same way... unlock bootloader, flash recovery image.. what can be done wrong with these 2 simple steps? What did you do other?
Click to expand...
Click to collapse
Dont pay attention to that idiot, he obviously has no idea what hes doing either.
And if you think it is because of this newer version have you checked to see if anyone else with the newer version has been having the same problems? Just to confirm thats it
Sent from my HTC One X using Tapatalk 2
stumpyz9 said:
Dont pay attention to that idiot, he obviously has no idea what hes doing either.
And if you think it is because of this newer version have you checked to see if anyone else with the newer version has been having the same problems? Just to confirm thats it
Sent from my HTC One X using Tapatalk 2
Click to expand...
Click to collapse
Stfu
Sent from my HTC One S using xda premium
Related
So i was in the middle of following the steps in the s-off and perma root thread and i ran into a problem. Hope someone here is nice enough to help me out.
So i ran revolutionary and everything went smooth. I already had the clockwork mod zip in the root of my sd card so i just rebooted the phone into hboot. When i went into hboot it detected the pg58img file and ran it, it prompted me if i wanted to update and so i did. It rebooted the phone and then i went back into hboot. The hboot said it was 1.23 and said Locked instead of Revolutionary as it displayed previously.
When i try to run the pg58 file in hboot an error occurs and said it is not compatible and only asks me to power off. So now at this moment it displays 1.23 version of hboot and s-off and says locked.
What can i do after this point? Any help i can get would be fantastic, thanks.
You're still good.
You're locked out of some of the most advanced fastboot commands. But that's it.
You still have S-Off. ADB will still work. You can flash ROM's. Etc etc etc....
It's a known problem. But it's not really a problem.
It's not like you divided by zero and destroyed the fabric of the universe or anything.
This is a noob question but how would i install clockwork recovery? I thought i would try dl from market but it said i didnt have root permission(obviously)
Is there a thread that has a solution to my issue or maybe you can quickly guide me out of this? lol Just kind of confused as to what i should do next lol.
Look in the development section for a thread called guide to s-off.
Skip the s-off part since you've done that.
Go right to the part about installing recovery. Following the directions. It's incredibly easy. It'll take about 3 minutes.
Once you have clcokwork recovery you can flash custom ROMs. You don't actually have to root the stock ROM. (Though you should make a backup of it just for kicks. You can do it all through clockwork recovery)
Yea I tried it multiple times already. I have the pg58 file in the root of the sd and when i go to the hboot it says
"Model ID incorrect!
Update Fail!
Press <POWER> to reboot."
Thats the only option it gives me so i am not able to install clockwork recovery.
Do you have SuperCID?
no i do not, would that fix the issue? i thought that is just for installing any rom on the device. My issue is that i cant get recovery to work.
I would think that is the next step after i run the perma root zip.
jonslaught said:
no i do not, would that fix the issue? i thought that is just for installing any rom on the device. My issue is that i cant get recovery to work.
I would think that is the next step after i run the perma root zip.
Click to expand...
Click to collapse
It should. Follow the SuperCID instructions here. Then update your firmware via the bootloader with this package that rmk made. It includes ClockworkMod Recovery.
Cool, thanks. I will definately try this as soon as I get off work later today and post up a status regarding the issue
Sent from my HTC Sensation 4G using xda premium
aNYthing24 said:
It should. Follow the SuperCID instructions here. Then update your firmware via the bootloader with this package that rmk made. It includes ClockworkMod Recovery.
Click to expand...
Click to collapse
He doesn't have use of Fastboot commands. I am pretty sure they are needed for super CID. Let me check.
He can't super CID as Fastboot commands are used.
Have you tried to run the correct RUU.exe? I think that would change back your h boot. There are zips in the development section you can use to downgrade but you may need super CID to use them.
Sent from my HTC Sensation 4G XE with Beats Audio using xda premium
Rhiannon224 said:
He doesn't have use of Fastboot commands. I am pretty sure they are needed for super CID. Let me check.
He can't super CID as Fastboot commands are used.
Click to expand...
Click to collapse
Yes, he does. CID commands will work with 1.23.xxxx. I've done it myself. Advanced fastboot commands won't work (he can't flash a radio through fastboot).
aNYthing24 said:
Yes, he does. CID commands will work with 1.23.xxxx. I've done it myself. Advanced fastboot commands won't work (he can't flash a radio through fastboot).
Click to expand...
Click to collapse
So basic Fastboot commands work with h boot 1.23? Good to know, my bad.
Sent from my HTC Sensation 4G XE with Beats Audio using xda premium
Rhiannon224 said:
So basic Fastboot commands work with h boot 1.23? Good to know, my bad.
Click to expand...
Click to collapse
Yeah, I had SuperCID to flash the new firmware to use an ICS ROM, then changed it back to the T-Mobile one after. No worries, it's confusing.
aNYthing24 said:
It should. Follow the SuperCID instructions here. Then update your firmware via the bootloader with this package that rmk made. It includes ClockworkMod Recovery.
Click to expand...
Click to collapse
I have the same problem. The Super CID does not work for me because when I type adb devices two blank lines show up, can't get the device number. I followed the instructions to the letter and usb debugging is on.
eagle_101 said:
I have the same problem. The Super CID does not work for me because when I type adb devices two blank lines show up, can't get the device number. I followed the instructions to the letter and usb debugging is on.
Click to expand...
Click to collapse
Do you have the correct drivers installed?
Sent from my HTC Sensation 4G XE with Beats Audio using xda premium
eagle_101 said:
I have the same problem. The Super CID does not work for me because when I type adb devices two blank lines show up, can't get the device number. I followed the instructions to the letter and usb debugging is on.
Click to expand...
Click to collapse
What mode are you in when you are in adb?
Rhiannon224 said:
Do you have the correct drivers installed?
Sent from my HTC Sensation 4G XE with Beats Audio using xda premium
Click to expand...
Click to collapse
I have adb tools only.
im having the same problem, but i can access recovery and i flashed a ROM but my screen freezes during boot. when i go into bootloader is says locked, 1.23.0000 s-off i can access fastboot and recovery i just dont know what to do from here, i installed a ROM and it was successful but i cant get passed the beats audio screen during boot up.
eagle_101 said:
I have adb tools only.
Click to expand...
Click to collapse
Okay, I am not near a pc atm so I cannot look where they are located, if you have the adb tools you also need another program called Net Framework installed on your pc.
Make sure your phone is powered onvand usb debugging checked when plugged into pc. I find it easiest to hold the mouse over the adb tools folder, press alt & ctrl keys and right click on the mouse and choose open command window here. Now type the command "adb devices".
Good luck.
Sent from my HTC Sensation 4G XE with Beats Audio using xda premium
shehade08 said:
im having the same problem, but i can access recovery and i flashed a ROM but my screen freezes during boot. when i go into bootloader is says locked, 1.23.0000 s-off i can access fastboot and recovery i just dont know what to do from here, i installed a ROM and it was successful but i cant get passed the beats audio screen during boot up.
Click to expand...
Click to collapse
First boot can take 10 minutes to load as the Davilk cache is being recreated. Also, did you perform a full wipe first and check the Md5 checksums, make sure your downloaded ROM is not corrupt.
Sent from my HTC Sensation 4G XE with Beats Audio using xda premium
Hey Guys,
My phone is stuck on the HTC logo with the little red message about development blah blah blah........... What do I do????
That depends on what you did or what you were trying to do.
You gotta give us more than that. Are you rooted? Unlocked boot loader? Can you reach recovery (hold down bottom volume rocker and power button)? If so, go to recovery, and use the 1.85 RUU found in the development section. Make sure your phone is in recovery.
Sent from my HTC One X using xda app-developers app
ethomas94 said:
You gotta give us more than that. Are you rooted? Unlocked boot loader? Can you reach recovery (hold down bottom volume rocker and power button)? If so, go to recovery, and use the 1.85 RUU found in the development section. Make sure your phone is in recovery.
Sent from my HTC One X using xda app-developers app
Click to expand...
Click to collapse
Ok tried running 1.85 RUU while in Recovery (TWRP) still erroring out. I'm unlocked and rooted. Any ideas??????????????
nonono. dont do the ruu when you are in recovery. instead of going to recovery in bootloader, go to fastboot. then on pc fastboot oem lock and run ruu, this will most likely fix your problem. whether or not you're problem can be fixed with an easier solution i do not know.
ethantarheels123 said:
nonono. dont do the ruu when you are in recovery. instead of going to recovery in bootloader, go to fastboot. then on pc fastboot oem lock and run ruu, this will most likely fix your problem. whether or not you're problem can be fixed with an easier solution i do not know.
Click to expand...
Click to collapse
Thanks man finally!! Now how would i go about rooting again and flashing a rom since the phone is not rooted and locked again??? Sorry for newb questions iphone user for 6 yrs.... Thanks for all your help!!
do you still have the unlock_code.bin file from when you unlocked it? if not on your computer check your email cuz htc emailed them to you. then boot phone into fastboot and fastboot oem unlock with the unlock code. then look in some of the stickies for how to root 1.85 to get a batch file that flashes cwm for you automatically. once you flash cwm, flash the super user root file to root it. then you're good to go!! however i recommend you immediately install twrp over cwm.
ethantarheels123 said:
do you still have the unlock_code.bin file from when you unlocked it? if not on your computer check your email cuz htc emailed them to you. then boot phone into fastboot and fastboot oem unlock with the unlock code. then look in some of the stickies for how to root 1.85 to get a batch file that flashes cwm for you automatically. once you flash cwm, flash the super user root file to root it. then you're good to go!! however i recommend you immediately install twrp over cwm.
Click to expand...
Click to collapse
I updated to 4.0.4 is their root for this???
ealvinito said:
I updated to 4.0.4 is their root for this???
Click to expand...
Click to collapse
There's not gonna be root for 4.0.4 for a while. But sit tight.
Sent from my HTC One X
Unlock the bootloader again install twrp recovery. Then install root. Done.
gunnyman said:
Unlock the bootloader again install twrp recovery. Then install root. Done.
Click to expand...
Click to collapse
Done. Unlocked and rooted running illuminati 4.0.4 and loving the smoothness. Thanks for the input.
Sent from my HTC One X using xda premium
gunnyman said:
Unlock the bootloader again install twrp recovery. Then install root. Done.
Click to expand...
Click to collapse
Yeah I don't know why in the age of TWRP people still use CWM. Unless your ROM requires it that is. Swiping vs messing around with the volume button, nuff said
Hello all
As you can tell Im new to this and thought i would be able to root my device..
Here what I have done I unlocked my device with HTCDev installed CWM 6.0.2.7 treid to boot to recovery no go just stays on a black screen. So then install TWRP 2.4.1.0 Booted to recovery and still the back screen.. so I re-locked the phone and now for some reason all my phone will boot up to is
***TAMPERED***
***Relocked***
EVITA PVT SHIP S-ON RL
HBOOT-2.14.0000
RADIO-0.23a.32.02.29
OpenDSP-v31.1.0.45.28.15
eMMC-boot
Nov 26 2013
So I would like to know before I go buy a new device If this one can be fix and if it can would some one be able to inform me of the steps ? I can still unlock the device but cant boot to any recovery....
I also Tried to Reload the rogers Ruu and keep getting errors.
Please help
Tookie.
Some one please Help I have been working on this for like 20 hours now and I dont have a phone that can be used :S
tookie69 said:
Hello all
As you can tell Im new to this and thought i would be able to root my device..
Here what I have done I unlocked my device with HTCDev installed CWM 6.0.2.7 treid to boot to recovery no go just stays on a black screen. So then install TWRP 2.4.1.0 Booted to recovery and still the back screen.. so I re-locked the phone and now for some reason all my phone will boot up to is
***TAMPERED***
***Relocked***
EVITA PVT SHIP S-ON RL
HBOOT-2.14.0000
RADIO-0.23a.32.02.29
OpenDSP-v31.1.0.45.28.15
eMMC-boot
Nov 26 2013
So I would like to know before I go buy a new device If this one can be fix and if it can would some one be able to inform me of the steps ? I can still unlock the device but cant boot to any recovery....
I also Tried to Reload the rogers Ruu and keep getting errors.
Please help
Tookie.
Some one please Help I have been working on this for like 20 hours now and I dont have a phone that can be used :S
Click to expand...
Click to collapse
Just reflash your unlock code from HTC dev install twrp then flash away
Sent from my HTC One X using Tapatalk 2
Don't panic, this should be an easy fix.
Once you relock, you have to run a ruu or unlock again. But you're trying to run a ruu for older firmware, which is why it's failing.
Just push the unlock token again, and you should be able to boot to recovery. If not, push the recovery image again. I don't recommend CWM, even though it's been ported to this phone. That version of TWRP should work, just confirm that you've got the Evita version.
OK i have unlocked again and re pushed recovery TWRP 2.4.1.0
But I still cant boot into the recovery option..
PLease tell me what im doing wrong..
iElvis said:
Don't panic, this should be an easy fix.
Once you relock, you have to run a ruu or unlock again. But you're trying to run a ruu for older firmware, which is why it's failing.
Just push the unlock token again, and you should be able to boot to recovery. If not, push the recovery image again. I don't recommend CWM, even though it's been ported to this phone. That version of TWRP should work, just confirm that you've got the Evita version.
Click to expand...
Click to collapse
I reflashed the unlcok code I reinstall TWRP but i cant boot into recovery..
is there another way to flash away ?
Kole_Ackerson said:
Just reflash your unlock code from HTC dev install twrp then flash away
Sent from my HTC One X using Tapatalk 2
Click to expand...
Click to collapse
tookie69 said:
I reflashed the unlcok code I reinstall TWRP but i cant boot into recovery..
is there another way to flash away ?
Click to expand...
Click to collapse
I believe through adv but is way simpler to do it through recovery. Try a earlier version of twrp
Sent from my HTC One X using Tapatalk 2
did you verify you are unlocked now, or did you just assume since you pushed the token again?
Also, are you certain you're using the right version of TWRP and not one for another phone (like the endeavour/Tegra One X)?
I pushed the same token and rebooted the device at the top its now says unlocked
DvineLord said:
did you verify you are unlocked now, or did you just assume since you pushed the token again?
Click to expand...
Click to collapse
make sure to run "fastboot erase cache" after changing recovery
IM pretty sure.. I also tried and older TWRP still same issue would you happen to have a link ? I have been using the all in one for HTC one X Tool
iElvis said:
Also, are you certain you're using the right version of TWRP and not one for another phone (like the endeavour/Tegra One X)?
Click to expand...
Click to collapse
bah, all-in-one don't learn anything without doing it yourself. evita is a pretty easy phone once you learn the basics. the op link for twrp in the dev section lists every twrp version officially released for our phone. http://techerrata.com/browse/twrp2/evita
ok i loaded that last night before i went to bed I went this morning to look at the phone and now it just goes to a black screen no madder what I do i put it in the computer the computer goes beep now when its plugged in my computer only the red light at the top flashes and then it disconnects from my computer because i can here the beep of adding and removing hard ware.
is my phone now bricked ?
DvineLord said:
bah, all-in-one don't learn anything without doing it yourself. evita is a pretty easy phone once you learn the basics. the op link for twrp in the dev section lists every twrp version officially released for our phone. http://techerrata.com/browse/twrp2/evita
Click to expand...
Click to collapse
Just relock and boot into boot loader the tampered screen then run a ruu am you should be back to stock
Although I had a EVO before that I flashed the wroung bootloader an bricked it an it wouldn't go anywhere but the bootloader
Sent from my HTC One X using xda premium
If I were you I'd reinstall drivers and manually push the recovery via adb. Use this command- fastboot flash recovery (filename).img
Sent from my HTC One X using Tapatalk 2
Thanks
Thanks for all the help maybe a little late but the issue was the main board on the phone was messed up sent it to HTC and they replaced the board and the battery.. but now i dont need the phone got the HTC one
Rom installation fails on Rogers HTC One X, S-ON, EVITA, HBOOT 2.14.0000
tookie69 said:
Thanks for all the help maybe a little late but the issue was the main board on the phone was messed up sent it to HTC and they replaced the board and the battery.. but now i dont need the phone got the HTC one
Click to expand...
Click to collapse
Hi Guys,
I have the same phone as the specs mentioned below. This is my first android phone and my first time playing around with it.
Here are the specs for "Rogers HTC One X":
***TAMPERED***
***Relocked***
EVITA PVT SHIP S-ON RL
HBOOT-2.14.0000
RADIO-0.23a.32.02.29
OpenDSP-v31.1.0.45.28.15
eMMC-boot
Nov 26 2013
Here is my accomplishments so far:
- Unlocked with HTC Dec, therefore it says unlocked as mentioned above
- Installed TWRP v2.5.0.0, and can successfully boot into recovery
Yet to be done and do not know how to:
- S-OFF
- Super CID
- Permanent Root
Problems installing ROM:
- unable to install. Various errors with different roms, such as:
1) unable to mount sdcard
2) assert failed: getprop("ro.product.device")
3) error executing updater binary in zip
Please advise. Thank you for your time.
Note: the device is locked to Rogers. It is currently in bootloop. I do not know what I did but before installing TWRP, the device went in bootloop after unlocking bootloader and it would simply not start. Although, as mentioned I can successfully boot into the recovery and mount the sdcard from there to transfer files to the phone.
iccrcmember said:
Hi Guys,
I have the same phone as the specs mentioned below. This is my first android phone and my first time playing around with it.
Here are the specs for "Rogers HTC One X":
***TAMPERED***
***Relocked***
EVITA PVT SHIP S-ON RL
HBOOT-2.14.0000
RADIO-0.23a.32.02.29
OpenDSP-v31.1.0.45.28.15
eMMC-boot
Nov 26 2013
Here is my accomplishments so far:
- Unlocked with HTC Dec, therefore it says unlocked as mentioned above
- Installed TWRP v2.5.0.0, and can successfully boot into recovery
Yet to be done and do not know how to:
- S-OFF
- Super CID
- Permanent Root
Problems installing ROM:
- unable to install. Various errors with different roms, such as:
1) unable to mount sdcard
2) assert failed: getprop("ro.product.device")
3) error executing updater binary in zip
Please advise. Thank you for your time.
Note: the device is locked to Rogers. It is currently in bootloop. I do not know what I did but before installing TWRP, the device went in bootloop after unlocking bootloader and it would simply not start. Although, as mentioned I can successfully boot into the recovery and mount the sdcard from there to transfer files to the phone.
Click to expand...
Click to collapse
Why are you relocked?
Unlock again and update TWRP, then try to flash a ROM again. What ROM(s) are you trying to flash.
Be aware that since you are s-off, you will need to extract boot.img from the ROM you are trying to flash, and manually flash with fastboot. You will need to do this every time you flash a ROM, unless you get s-off.
Also, I don't know why you posted to this old thread. Aside from the OP also having the Rogers version, it has nothing to do with your issue. Should have started your own thread.
I'll just clarify that when Redpoint said you need to update TWRP you should update it to TWRP 2.6, your current version (2.5) is very buggy. Also, he means since you are s-on you need to flash the boot.img, when you get s-off this will no longer be required.
Sent from my Evita
Thank you redpoint73
redpoint73 said:
Why are you relocked?
Unlock again and update TWRP, then try to flash a ROM again. What ROM(s) are you trying to flash.
Be aware that since you are s-off, you will need to extract boot.img from the ROM you are trying to flash, and manually flash with fastboot. You will need to do this every time you flash a ROM, unless you get s-off.
Also, I don't know why you posted to this old thread. Aside from the OP also having the Rogers version, it has nothing to do with your issue. Should have started your own thread.
Click to expand...
Click to collapse
I made an error. my bootloader was already unlocked. Any how flashing the boot.img of the Rom before installing the Rom worked. Thank you for your insight. My phone is up and running.
For others: below is the rom i flashed:
[ROM] 10/10 Team Venom ViperX 4.0.4 - Sense 5 JellyBean | orig. OTA | Tweaks
http://forum.xda-developers.com/showthread.php?t=2087443
AT&T HOX from Android 4.2.1, with 3.18 firmware. Attempting to get to CM 10.1
Rooted and flashed TWRP via http://forum.xda-developers.com/showpost.php?p=41830252&postcount=201
Moved on to Facepalm S-off http://forum.xda-developers.com/showthread.php?t=2155071, was getting error 99.
Used the Viper solution from ChongoDroid on page 17 http://forum.xda-developers.com/showpost.php?p=38186473&postcount=163 using viper from http://forum.xda-developers.com/showthread.php?t=2087443
Install Viper from TWRP, Viper install stops at 0.00%, will not progress. Hard restart via power button battery remove sim, attempted s-off again. At some point I ended up getting the correct error 92. Success! Run 'fastboot oem boot', get list of errors, wait for boot into Android. Boot stops at white HTC splash screen, android will not boot.
Panic, hard restart back into bootloader, and this is where things go hazy (it was 5 in the morning by now). At this point I'm sure I put in some commands I should not have via adb (don't remember which ones), and did a factory reset via hboot. Recovery now brings me back into the bootloader. Bootloader shows *** TAMPERED ***, ***RELOCKED *** and *** Security Warning ***. I'm still S-ON with hboot 2.14.0000.
When in fastboot, my phone will not list via 'adb devices'. FAQ Q16 (http://forum.xda-developers.com/showthread.php?t=2136172) says if I did a factory reset in hboot, my SD mem is wiped and i need to format it from device manager. Device Manager shows my phone as Android USB Devices > My HTC and options are Update Driver Software..., Disable, and Uninstall. Updating drivers gives me a drivers up to date notice. No option to format the SD
Word is that if it turns on, it isn't bricked, but if I can't get my adb to recognize my phone, what is there that I can do to fix it? I'm on 64 bit Windows 7.
alright, first off, you flashed a ROM for the international quad core One X and you're lucky not to have bricked your phone. Secondly, what you're gonna need to do is run the 3.18 ruu and restore your phone to factory settings with that. That's the only way to recover from factory reset in bootloader. Before you do, you need to be S-Off. Which you are, correct?
Edit: re-reading this, it appears you're not s-off. I'm gonna need to call in some help here because 3.18 ruu with SuperCID will brick you, but I don't think you can use a lower RUU since you're s-on. Anyone know what to do? If you are s-off and I just misread your post, then go ahead and run the ruu.
If it turns on, there's always a way to fix it!
Adb requires an os to work, since you can't boot to your os, no Adb
That being said, in bootloader, you should be able to access your phone with fastboot. Boot to bootloader/fastboot with your phone plugged in to your pc.
Do: fastboot devices and confirm that fastboot commands reach your phone, then we will move on to the next step.
Sent from my HTC One X using xda app-developers app
Correct, I am still s-off, and 'adb devices' gives an empty list, and does not list my phone. I cannot send commands to my phone via adb commands.
You just said in your first post you're still s-on......
These details are extremely important so please be sure of what you've typed prior to posting.
Sent from my HTC One X using xda app-developers app
exad said:
Adb requires an os to work, since you can't boot to your os, no Adb
That being said, in bootloader, you should be able to access your phone with fastboot. Boot to bootloader/fastboot with your phone plugged in to your pc.
Do: fastboot devices and confirm that fastboot commands reach your phone, then we will move on to the next step.
Sent from my HTC One X using xda app-developers app
Click to expand...
Click to collapse
exad said:
You just said in your first post you're still s-on......
These details are extremely important so please be sure of what you've typed prior to posting.
Sent from my HTC One X using xda app-developers app
Click to expand...
Click to collapse
Yes, sorry. I realized my mistake as soon as I posted, but since I'm a new member I can only edit or reply every 5 minutes.
Yes, I am S-ON. S-ON, not S-OFF.
And aha, yes. 'fastboot devices' does list my phone.
Good good. So first you'll want to unlock your bootloader again since it's relocked. Just flash the unlock_code.bin or whatever it's called again that you previously used.
Sometimes if you're relocked it does the unlock process like it's going to unlock but then leaves you relocked. If this happens press and hold power to simulate a battery pull and try again. It should work eventually. Might take several tries.
Sent from my HTC One X using xda app-developers app
Korad said:
Yes, sorry. I realized my mistake as soon as I posted, but since I'm a new member I can only edit or reply every 5 minutes.
Yes, I am S-ON. S-ON, not S-OFF.
And aha, yes. 'fastboot devices' does list my phone.
Click to expand...
Click to collapse
I'm assuming you have supercid already?
I would reflash twrp.. nothing higher that 2.3.3.1
Then load a sense Rom from this forum through twrp. Just to get a running os on the phone. Then you can s-off and run 3.18 ruu
Sent from my HTC One XL using xda premium
exad said:
Good good. So first you'll want to unlock your bootloader again since it's relocked. Just flash the unlock_code.bin or whatever it's called again that you previously used.
Sometimes if you're relocked it does the unlock process like it's going to unlock but then leaves you relocked. If this happens press and hold power to simulate a battery pull and try again. It should work eventually. Might take several tries.
Sent from my HTC One X using xda app-developers app
Click to expand...
Click to collapse
Okay, flashed Unlock_code.bin on first try, now showing *** UNLOCKED ***
Korad said:
Okay, flashed Unlock_code.bin on first try, now showing *** UNLOCKED ***
Click to expand...
Click to collapse
Do as ken posted above though twrp 2.6 is supposedly stable and fine too.
Roms from here are safe to flash: http://forum.xda-developers.com/forumdisplay.php?f=1541
And... Here: http://forum.xda-developers.com/forumdisplay.php?f=1726
Sent from my HTC One X using xda app-developers app
exad said:
Do as ken posted above though twrp 2.6 is supposedly stable and fine too.
Roms from here are safe to flash: http://forum.xda-developers.com/forumdisplay.php?f=1541
And...:
Sent from my HTC One X using xda app-developers app
Click to expand...
Click to collapse
Have you flashed 2.6 yet? I've heard it works as well but was waiting for more input
Sent from my HTC One XL using xda premium
Not yet, going to when I get home. Jacobas92 said hes been using it though and I trust him.
Sent from my HTC One X using xda app-developers app
Well I'll take ur word for it. Gonna download and flash now and test the hell out of all options.
Sent from my HTC One XL using xda premium
31ken31 said:
I'm assuming you have supercid already?
I would reflash twrp.. nothing higher that 2.3.3.1
Then load a sense Rom from this forum through twrp. Just to get a running os on the phone. Then you can s-off and run 3.18 ruu
Sent from my HTC One XL using xda premium
Click to expand...
Click to collapse
So I'm waiting on ViperXL to download (going very slowly), but if I'm looking to get to CM 10.1, and have root with TWRP, do I need to flash a ROM with TWRP first or can I do the Facepalm S-Off and move straight to CM 10.1 without flashing a middle-man ROM?
Korad said:
So I'm waiting on ViperXL to download (going very slowly), but if I'm looking to get to CM 10.1, and have root with TWRP, do I need to flash a ROM with TWRP first or can I do the Facepalm S-Off and move straight to CM 10.1 without flashing a middle-man ROM?
Click to expand...
Click to collapse
I believe you need to be on a rooted ROM to get s-off.
Korad said:
So I'm waiting on ViperXL to download (going very slowly), but if I'm looking to get to CM 10.1, and have root with TWRP, do I need to flash a ROM with TWRP first or can I do the Facepalm S-Off and move straight to CM 10.1 without flashing a middle-man ROM?
Click to expand...
Click to collapse
Viper xl will work fine that's what I used to s-off. Not with the new cm10.1 kernel you have to ruu up to 3.18 before you install it.
Sent from my HTC One XL using xda premium
31ken31 said:
Viper xl will work fine that's what I used to s-off. Not with the new cm10.1 kernel you have to ruu up to 3.18 before you install it.
Sent from my HTC One XL using xda premium
Click to expand...
Click to collapse
hes already on 3.18
If I'm using ViperXL as my ROM during S-Off, will I want to use ChongoDroid's extra steps when installing ViperXL or should I only need to do those if the Facepalm S-Off steps don't work by themselves?
Korad said:
If I'm using ViperXL as my ROM during S-Off, will I want to use ChongoDroid's extra steps when installing ViperXL or should I only need to do those if the Facepalm S-Off steps don't work by themselves?
Click to expand...
Click to collapse
You should be able to S-OFF with viperxl without any problems just by flashing viperxl and following the S-OFF thread right after.
So ViperXL finally finished downloading, and I've sent the command to push the .zip to /sdcard in prep to install it with TWRP, but it's been stuck there for 15+ minutes. Should I be worried? Should I restart?
Hey Guys,
This is my first post, so excuse me if I sound like I don't know what I'm talking about.
a few days ago i tried to connect to my wifi at home and it was not picking it up although i was inside my own house. so i thought i should restart my phone. well after trying to restart it it got stuck in a boot loop. it would load the htc screen then start loading the venom logo then it shuts off and reboots the htc screen. i tried installing the back up, re installing the latest venom rom and even trying to put on a entire new rom but nothing has worked(it wont even let me install a new rom it errors out when i try) i doubt you will even get this but its my last effort Ive spent the entire day and all night looking for some way to fix this but i have yet to find anything. please if anyone one has any know how about this i could really used the help. i rooted my att htc one xl(evita) about 7 months ago using the method from onexroot.com and have never had an issue with this phone till now.
when i try to install a new rom via twerp it said install failed, im really stuck with this and could use some help thanks in advance.
just incase its not clear the phone is rooted running a custom rom(team venom) and im using twerp as my recovery program
evita pvt ship s-on rl
hboot-1.14.0002
radio-0.19as.32.09.11_2
opendep-v29.1.0.45.0622
emcc-boot
not sure if that helps at all
dtk0kai said:
Hey Guys,
This is my first post, so excuse me if I sound like I don't know what I'm talking about.
a few days ago i tried to connect to my wifi at home and it was not picking it up although i was inside my own house. so i thought i should restart my phone. well after trying to restart it it got stuck in a boot loop. it would load the htc screen then start loading the venom logo then it shuts off and reboots the htc screen. i tried installing the back up, re installing the latest venom rom and even trying to put on a entire new rom but nothing has worked(it wont even let me install a new rom it errors out when i try) i doubt you will even get this but its my last effort Ive spent the entire day and all night looking for some way to fix this but i have yet to find anything. please if anyone one has any know how about this i could really used the help. i rooted my att htc one xl(evita) about 7 months ago using the method from onexroot.com and have never had an issue with this phone till now.
when i try to install a new rom via twerp it said install failed, im really stuck with this and could use some help thanks in advance.
just incase its not clear the phone is rooted running a custom rom(team venom) and im using twerp as my recovery program
evita pvt ship s-on rl
hboot-1.14.0002
radio-0.19as.32.09.11_2
opendep-v29.1.0.45.0622
Click to expand...
Click to collapse
flash twrp 2.6 advanced wipe everything except sd card, reflash.
also since youre s-on you have to extract the boot.img from the rom zip and flash it with fastboot after flashing most roms. should not be the case with viper but i would do it anyway if vier doesn't boot after the above steps.
fastboot flash boot boot.img
reply
exad said:
flash twrp 2.6 advanced wipe everything except sd card, reflash.
Click to expand...
Click to collapse
this is going to sound bad but how do i do that again? i really dont remember how to flash twerp
dtk0kai said:
this is going to sound bad but how do i do that again? i really dont remember how to flash twerp
Click to expand...
Click to collapse
download: http://goo.im/devs/OpenRecovery/evita/openrecovery-twrp-2.6.0.0-evita.img
Place img in your fastboot folder
put phone in hboot/fastboot mode
open command prompt within fastboot folder (shift right click - open command prompt here)
fastboot flash recovery openrecovery-twrp-2.6.0.0-evita.img
navigate to recovery in hboot menu, select recovery.
exad said:
download: http://goo.im/devs/OpenRecovery/evita/openrecovery-twrp-2.6.0.0-evita.img
Place img in your fastboot folder
put phone in hboot/fastboot mode
open command prompt within fastboot folder (shift right click - open command prompt here)
fastboot flash recovery openrecovery-twrp-2.6.0.0-evita.img
navigate to recovery in hboot menu, select recovery.
Click to expand...
Click to collapse
ok im going to go try that ill post results
exad said:
download: http://goo.im/devs/OpenRecovery/evita/openrecovery-twrp-2.6.0.0-evita.img
Place img in your fastboot folder
put phone in hboot/fastboot mode
open command prompt within fastboot folder (shift right click - open command prompt here)
fastboot flash recovery openrecovery-twrp-2.6.0.0-evita.img
navigate to recovery in hboot menu, select recovery.
Click to expand...
Click to collapse
when you say reflash you mean my rom right?
Yep
Sent from my HTC One XL using xda app-developers app
exad said:
Yep
Sent from my HTC One XL using xda app-developers app
Click to expand...
Click to collapse
when flashing my rom it said error kernal not installed but then it said new rom flashed successfully will that be a problem?(viperxl-3.2.7)
exad said:
Yep
Sent from my HTC One XL using xda app-developers app
Click to expand...
Click to collapse
well so far nothing has changed.
Like Exad said, you're s-on so you need to manually flash the boot.img from the ROM using fastboot.
Sent from my Evita
timmaaa said:
Like Exad said, you're s-on so you need to manually flash the boot.img from the ROM using fastboot.
Sent from my Evita
Click to expand...
Click to collapse
yea i tried that too nothing changed
off to bed still no luck loads part of the viper logo and then resets back to htc screen x.x
dtk0kai said:
yea i tried that too nothing changed
off to bed still no luck loads part of the viper logo and then resets back to htc screen x.x
Click to expand...
Click to collapse
Try running an RUU. This fault (or at least a very similar fault) happened with my fiance's phone and now there's only one ROM that will boot on it (an old build of cm10.1). You may be facing a hardware fault (that's what's wrong my fiance's phone), but I'd suggest running an RUU to see if that helps.
Sent from my Evita
You might brick if you ruu, I would try flashing other roms first. Make sure to check the md5 to make sure that the download isn't corrupt.
But
If you must ruu make sure it isn't 3.18. And you will have to change your cid back and relock.
Fastboot oem writecid CWS__001
To change your cid back.
If you ruu, you cannot ever the the 3.18+ ota until you reroot and achieve s-off
Sent from my HTC One XL using xda app-developers app
exad said:
Nononono he's s-on remember! He might brick of he RUUs
Sent from my HTC One XL using xda app-developers app
Click to expand...
Click to collapse
Oh gosh, my bad, I'm having a weird day today.
Sent from my Evita
Well so long as it's not 3.18 it Should be OK I think?
Sent from my HTC One XL using xda app-developers app
exad said:
Well so long as it's not 3.18 it Should be OK I think?
Sent from my HTC One XL using xda app-developers app
Click to expand...
Click to collapse
so i should just try a diffrent rom? when doing that i should flash the boot img using fastboot then install the rom and then do a cache whipe correct?
Did you Wipe system in advanced Wipe last time before flashing the rom?
For any rom you ever flash always follow the steps I layer out in my earlier post. It will not be different for any rom.
Sent from my HTC One XL using xda app-developers app
exad said:
Did you Wipe system in advanced Wipe last time before flashing the rom?
For any rom you ever flash always follow the steps I layer out in my earlier post. It will not be different for any rom.
Sent from my HTC One XL using xda app-developers app
Click to expand...
Click to collapse
yes i did the entire wipe just like you said then installed the rom like you said and it started up and loaded the venom screen longer but then restarted, im going to try flashing the cm 10 and see if that dose anything
now cm10 is in a boot loop after i tried to flash gapps
Try flashing the 20130304 build from the get.cm/evita page.
Sent from my Evita