Soft Bricked my HTC One SV, managed to get the Stock Recovery working again, but refuses to boot even after a Factory Reset.
Gets stuck at HTC Quietly Briliant screen.
Any ideas on how to fix?
Running Android 4.2.2 (well, was) Unlocked but S-On
it seems my System dir got wiped.....no idea how this happened...does anyone have a NANDROID 4.2.2 backup k2_plc_cl?
You have tried to run this RUU?
downloading now, I also thought of something else, it could be I'm not using the correct boot.img, would you happen to have a copy of 4.2.2 boot.img?
Also, the device doesn't boot, sticks at HTC screen, will I still be able to use this?
@ARitualSacrifice
Preparing to run the RUU:
To run the RUU, here's what you will need to do:
-- Make sure phone is charged to at least 100% (but if not, then at least 60% or more)
-- Place phone in fastboot mode(select fastboot from hboot menu), plug in via usb.
-- Open a command prompt window, change to android directory (wherever you set this up for adb/fastboot) and enter the following commands (one at a time):
--
Code:
fastboot devices
--
Code:
fastboot oem lock
-- This will lock your bootloader and allow you to run the RUU. The phone will try and reboot, or it will give you a security warning, and lock you into bootloader. Don't worry, this is normal.
Running the RUU
-- Make sure the HTC drivers you downloaded earlier are installed and working. Do this by connecting your phone to your computer. If your computer detects it, your drivers are working. I recommend staying in fastboot usb mode after entering the commands above, the RUU.exe will detect that and be able to work from fastboot.
-- Run the RUU.exe (that you downloaded earlier) on the PC as administrator. It takes a few minutes to boot up, so don't be alarmed if it doesn't appear immediately.
-- Follow the prompts. It should ask you to ensure your phone is plugged into the computer and that ADB debugging is turned on. As long as you left it plugged in from earlier you are fine.
--The RUU should recognize the phone and start running. Be patient, do not unplug the phone under any circumstances!!
-- When it finishes, it will reboot, you will be stock again.
Sent from my C525c using Tapatalk
HAH! Worked like a charm, holding onto this
Thanks greatly for the help.
My final question, has there been an S-Off method made for hBoot 2.21 yet?
www.rumrunner.us
I assume (since the one sv isn't listed) I use the "universal" version?
Yes.
Says it requires an unsecure kernel...best/suggested one for my version?
ARitualSacrifice said:
Says it requires an unsecure kernel...best/suggested one for my version?
Click to expand...
Click to collapse
did you run it and it said that?
upload your stock boot.img, I'll unpack/repack it unsecure
What's the command for that again? Sorry, conning off Samsung development, starting on my HTC, bit rusty on these.
Sent from my HTC One SV using xda app-developers app
ARitualSacrifice said:
What's the command for that again? Sorry, conning off Samsung development, starting on my HTC, bit rusty on these.
Sent from my HTC One SV using xda app-developers app
Click to expand...
Click to collapse
https://www.dropbox.com/s/y1pi0q1m0xwz23e/insecure_boot.img
Download and flash it using fastboot.
Code:
fastboot flash boot insecure_boot.img
Sent from my C525c using Tapatalk
this is for Android 4.2.2? last time I flashed a boot.img, is why I made this post lol
ARitualSacrifice said:
this is for Android 4.2.2? last time I flashed a boot.img, is why I made this post lol
Click to expand...
Click to collapse
Yes, it is for 4.2.2 k2_plc_cl. Otherwise, I wouldn't have sent you the download link lol.
Sent from my C525c using Tapatalk
Thanks for the help, device is back up and running smooth, with s-off. Can't seem to find a working root method for 4.2.2 yet, angain, thanks for the help.
Sent from my HTC One SV using xda app-developers app
ARitualSacrifice said:
Thanks for the help, device is back up and running smooth, with s-off. Can't seem to find a working root method for 4.2.2 yet, angain, thanks for the help.
Sent from my HTC One SV using xda app-developers app
Click to expand...
Click to collapse
Flash this zip using either twrp or cwm
https://db.tt/xL563K7X
Sent from my C525c using Tapatalk
---------- Post added at 03:40 PM ---------- Previous post was at 03:34 PM ----------
It will root your device and place the root app in to ./system/apps
Comes with the su binary for /etc and /xbin
Binary for /xbin is then symlinked.
Download a root checker from the play store for confirmation or run a app that requires root. Either one will give confirmation
Sent from my C525c using Tapatalk
---------- Post added at 03:41 PM ---------- Previous post was at 03:40 PM ----------
Afterwards, just update the supersu app in the play store and you will be good to go.
Sent from my C525c using Tapatalk
About CWM, is there one that works with hboot 2.21?
Sent from my HTC One SV using xda app-developers app
ARitualSacrifice said:
About CWM, is there one that works with hboot 2.21?
Sent from my HTC One SV using xda app-developers app
Click to expand...
Click to collapse
Not that I am aware of. I recommend TWRP.
Sent from my C525c using Tapatalk
Lol, your public links have been temporarily disabled..
Sent from my HTC One SV using xda app-developers app
Related
I've sent my DS off for warranty, and it was returned with the new ics update installed on it. I immediately found out that the method i used to downgrade it from hboot 2.00 to 0.98(zergRUsh/tacoroot) wasn't working anymore. Are there any alternatives to unlocking the bootloader with htcdev, rooting and then going thru the whole downgrading procedures? Are there any other temproot exploits or are them under development?
Try this
http://forum.xda-developers.com/showthread.php?t=1443636&highlight=down+grading+hboot
or
http://forum.xda-developers.com/showthread.php?t=1318919&highlight=down+grading+hboot
Have tried both, but one needs tacoroot (not working on ics) and the other needs to be htcdev unlocked. Any other alternatives?
Sent from my HTC Desire S using xda app-developers app
I don't think there are any alternatives for hboot 2.02.xxx.
Sent from my HTC Desire S using xda app-developers app
teadrinker said:
I don't think there are any alternatives for hboot 2.02.xxx.
Sent from my HTC Desire S using xda app-developers app
Click to expand...
Click to collapse
Ok thx im going to root with htcdev and then downgrade for true s off.
Sent from my HTC Desire S using xda app-developers app
Trouble getting htc dev unlocked
I've submitted the unlocking request on htcdev, and was sent the unlock_code.bin file. The trouble is I can't get it flashed thru fastboot.
I type
fastboot flash unlocktoken Unlock_code.bin
and it stucks on sending 'unlocktoken'. The bootloader does something, as to reboot it I have to close the command prompt, reopen it and type fastboot reboot-bootloader and it rebbots just fine.
I tried several times, but without luck. What can I do?
Anyone?
totalnoob34 said:
I've submitted the unlocking request on htcdev, and was sent the unlock_code.bin file. The trouble is I can't get it flashed thru fastboot.
I type
fastboot flash unlocktoken Unlock_code.bin
and it stucks on sending 'unlocktoken'. The bootloader does something, as to reboot it I have to close the command prompt, reopen it and type fastboot reboot-bootloader and it rebbots just fine.
I tried several times, but without luck. What can I do?
Click to expand...
Click to collapse
Have you installed the latest HTC-USB drivers on your PC?
---------- Post added at 10:43 AM ---------- Previous post was at 10:18 AM ----------
have you tried this one?
http://forum.xda-developers.com/showthread.php?t=1318919
HypnoCondor said:
Have you installed the latest HTC-USB drivers on your PC?
---------- Post added at 10:43 AM ---------- Previous post was at 10:18 AM ----------
have you tried this one?
http://forum.xda-developers.com/showthread.php?t=1318919
Click to expand...
Click to collapse
Thx was the guide i am fpllowing, but i cant get my bootloader unlocked
I have successfully downgraded my iphone once, and cpmmands work. Should i update them?
Sent from my HTC Desire S using xda app-developers app
what have your iphone to do with a desire s?
HypnoCondor said:
what have your iphone to do with a desire s?
Click to expand...
Click to collapse
Sorry, typo
Sent from my HTC Desire S using xda app-developers app
Maybe you can try to flash a eng hboot from your SD card on your phone.
You also need a resent version of busybox
Shut down your phone and pull the battery and wait 5 minuter before you put
your battery back. In the mean time install the lastest HTC-USB drivers on you computer.
Start your device in bootloader mode and plug it in to your computer.
You now got bootloader-usb. Now flash your Unlock_code.bin.
"fastboot flash unlocktoken Unlock_code.bin"
Boot your phone in recovery
Make a nandroid backup of your ROM, reboot your phone
To make a backup of the hboot by entering this:
1) open terminal on your phone
2) su
3) dd if=/dev/block/mmcblk0p18 of=/sdcard/backup.img
download a eng hboot.img and copy it to the SDcard/
1) open terminal on your phone
2) su
3) dd if=/sdcard/hboot.img of=/dev/block/mmcblk0p18
4) close the therminal
reboot in bootloader an see witch version of bootloader you got
If it has workt go to recovery and do a factory resset, reset dalvik and install a new rom and reboot
It works for me because my phone has revolutionary root but you can give it a try because I have not
found anyone has done this with HTC-dev, I also got no experience with HTC-dev.
Good luck ( I'm not responsible for any damage on your device )
HypnoCondor said:
Maybe you can try to flash a eng hboot from your SD card on your phone.
You also need a resent version of busybox
Shut down your phone and pull the battery and wait 5 minuter before you put
your battery back. In the mean time install the lastest HTC-USB drivers on you computer.
Start your device in bootloader mode and plug it in to your computer.
You now got bootloader-usb. Now flash your Unlock_code.bin.
"fastboot flash unlocktoken Unlock_code.bin"
Boot your phone in recovery
Make a nandroid backup of your ROM, reboot your phone
To make a backup of the hboot by entering this:
1) open terminal on your phone
2) su
3) dd if=/dev/block/mmcblk0p18 of=/sdcard/backup.img
download a eng hboot.img and copy it to the SDcard/
1) open terminal on your phone
2) su
3) dd if=/sdcard/hboot.img of=/dev/block/mmcblk0p18
4) close the therminal
reboot in bootloader an see witch version of bootloader you got
If it has workt go to recovery and do a factory resset, reset dalvik and install a new rom and reboot
It works for me because my phone has revolutionary root but you can give it a try because I have not
found anyone has done this with HTC-dev, I also got no experience with HTC-dev.
Good luck ( I'm not responsible for any damage on your device )
Click to expand...
Click to collapse
Thx man, which hboot version should i flash?
Sent from my HTC Desire S using xda app-developers app
totalnoob34 said:
Thx man, which hboot version should i flash?
Click to expand...
Click to collapse
How about looking in the Index Thread?
I only found the 0.98 hboot, can i flash it over the 2.02 one?
Sent from my HTC Desire S using xda app-developers app
totalnoob34 said:
I only found the 0.98 hboot, can i flash it over the 2.02 one?
Click to expand...
Click to collapse
From that page I gave you the link to there should be all the information you need to read and understand what/how to do and why.
Don't expect people to spoon-feed you the answers as you need to learn or you will simply screw your phone up and then start blaming everyone else on XDA for it.
SimonTS said:
From that page I gave you the link to there should be all the information you need to read and understand what/how to do and why.
Don't expect people to spoon-feed you the answers as you need to learn or you will simply screw your phone up and then start blaming everyone else on XDA for it.
Click to expand...
Click to collapse
I dont wanna be spoon-fed, I only ask what I don't understand, and was unable to find anywhere.
Can somebody answer me please?
Sent from my HTC Desire S using xda app-developers app
totalnoob34 said:
I dont wanna be spoon-fed, I only ask what I don't understand, and was unable to find anywhere.
Can somebody answer me please?
Sent from my HTC Desire S using xda app-developers app
Click to expand...
Click to collapse
You have to browse all threads to find which way to Root or S-OFF your DS, that's what I've done before deciding to S-OFF my DS.
Sent from my Desire S
miwanr said:
You have to browse all threads to find which way to Root or S-OFF your DS, that's what I've done before deciding to S-OFF my DS.
Sent from my Desire S
Click to expand...
Click to collapse
You dont understand bro. I know what s off is, and how to achieve it. I have done it several times on different devices. I am totally aware of the risk of bricking my device.
I just need a bit of clarification about flashing the hboot. Which one can I flash over the 2.02?
Sent from my HTC Desire S using xda app-developers app
totalnoob34 said:
You dont understand bro. I know what s off is, and how to achieve it. I have done it several times on different devices. I am totally aware of the risk of bricking my device.
I just need a bit of clarification about flashing the hboot. Which one can I flash over the 2.02?
Sent from my HTC Desire S using xda app-developers app
Click to expand...
Click to collapse
Please open this thread http://forum.xda-developers.com/showthread.php?t=1938615
My DS was from hboot 2.02 by latest ICS RUU by hTC. In above link is what I've done to get S-OFF. Hope it may help
Sent from my Desire S
I got the official 4.0.4 on my one s (s3) but the problem is I my phone is rooted and the bootloader unlocked. Unfortunately when I go to install the update it goes into TWRP and nothing can be done from there. Tried installing the ROM from TWRP and unfortunately that does not work. Can anyone pls help me out with this?
Thanks in advance
Relock bootloader, run ruu, then try
Sent from my HTC VLE_U using xda app-developers app
You must lock your bootloader first.
To do that, go in the bootloader menu, select fastboot and from the command prompt run
"fastboot oem lock".
After that finishes, just run the RUU.
After that, download the update and install. If you are from Romania please PM me in case you need further explaining.
You can find the RUU here:
http://forum.xda-developers.com/showthread.php?p=23542379
Good luck!
Sent from my HTC One S using xda app-developers app
saculetz said:
You must lock your bootloader first.
To do that, go in the bootloader menu, select fastboot and from the command prompt run
"fastboot oem lock".
After that finishes, just run the RUU.
After that, download the update and install. If you are from Romania please PM me in case you need further explaining.
You can find the RUU here:
http://forum.xda-developers.com/showthread.php?p=23542379
Good luck!
Sent from my HTC One S using xda app-developers app
Click to expand...
Click to collapse
From Malta mate
saculetz said:
You must lock your bootloader first.
To do that, go in the bootloader menu, select fastboot and from the command prompt run
"fastboot oem lock".
After that finishes, just run the RUU.
After that, download the update and install. If you are from Romania please PM me in case you need further explaining.
You can find the RUU here:
http://forum.xda-developers.com/showthread.php?p=23542379
Good luck!
Sent from my HTC One S using xda app-developers app
Click to expand...
Click to collapse
Re-locked bootloader and ran update. Phone rebooted and went to the bootloader menu.. No update :/
Din you run the RUU first?
I erased system and everything after having some issues. Then I ran the ruu from the computer. After that I installed the update. First time it only wiped everything. Second time I downloaded the update it worked
Sent from my HTC One S using xda app-developers app
saculetz said:
Din you run the RUU first?
I erased system and everything after having some issues. Then I ran the ruu from the computer. After that I installed the update. First time it only wiped everything. Second time I downloaded the update it worked
Sent from my HTC One S using xda app-developers app
Click to expand...
Click to collapse
When I open the RUU on my PC it comes up as a rar file.
On my pc it came up as a setup installer. Try downloading it again and find a setup exe file
I will upload it on dropbox when I get home and send the link to it if you want...
Sent from my HTC One S using xda app-developers app
saculetz said:
On my pc it came up as a setup installer. Try downloading it again and find a setup exe file
I will upload it on dropbox when I get home and send the link to it if you want...
Sent from my HTC One S using xda app-developers app
Click to expand...
Click to collapse
That would be fantastic . As long as it is the ruu for the s3 version
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
okay so this time around i made sure my htc one x was S-Off and i didnt do anything wrong. i installed a rom that themes sense 5 and what not... anyways the install failed and when i went to go boot up it didnt go further than the htc splash screen... i can get to bootloader but i cannot load recovery, it opens and then 3 seconds later it closes and then im back at splash screen... any ideas on how to fix?
Redownload twrp, check md5
fastboot flash recovery recoveryfilename.img
Fastboot erase cache
Fastboot reboot-bootloader
select recovery
If that doesnt work, since youre s-off, just ruu.
Sent from my Sony Tablet S using xda app-developers app
exad said:
Redownload twrp, check md5
fastboot flash recovery recoveryfilename.img
Fastboot erase cache
Fastboot reboot-bootloader
select recovery
If that doesnt work, since youre s-off, just ruu.
Sent from my Sony Tablet S using xda app-developers app
Click to expand...
Click to collapse
thank you Exad. im just going to run ruu. but since im ruu i should be fine?
exad said:
Redownload twrp, check md5
fastboot flash recovery recoveryfilename.img
Fastboot erase cache
Fastboot reboot-bootloader
select recovery
If that doesnt work, since youre s-off, just ruu.
Sent from my Sony Tablet S using xda app-developers app
Click to expand...
Click to collapse
THANK YOU MAN i did what you said. now i just gotta flash my back up. i really wish i coudl delete this post now :/
Yeah Ive RUUed at least ten times with my bootloader unlocked and cid as 11111111
Sent from my Sony Tablet S using xda app-developers app
As long as you aren't taking an ota supercid won't hurt you
Sent from my Nexus 4
Megadoug13 said:
THANK YOU MAN i did what you said. now i just gotta flash my back up. i really wish i coudl delete this post now :/
Click to expand...
Click to collapse
**** happens. I embarrass myself on here all the time. Glad its working again.
Sent from my Sony Tablet S using xda app-developers app
---------- Post added at 08:36 PM ---------- Previous post was at 08:35 PM ----------
mirGantrophy said:
As long as you aren't taking an ota supercid won't hurt you
Sent from my Nexus 4
Click to expand...
Click to collapse
It bricked my telus phone when I ruud with supercid. No ota.
Sent from my Sony Tablet S using xda app-developers app
exad said:
**** happens. I embarrass myself on here all the time. Glad its working again.
Sent from my Sony Tablet S using xda app-developers app
---------- Post added at 08:36 PM ---------- Previous post was at 08:35 PM ----------
It bricked my telus phone when I ruud with supercid. No ota.
Sent from my Sony Tablet S using xda app-developers app
Click to expand...
Click to collapse
I'm glad my phone is working too, am I looking forward to sense 5 roma coming out soon. I really want blinkfeed lol
Sent from my HTC One X using xda app-developers app
exad said:
**** happens. I embarrass myself on here all the time. Glad its working again.
Sent from my Sony Tablet S using xda app-developers app
---------- Post added at 08:36 PM ---------- Previous post was at 08:35 PM ----------
It bricked my telus phone when I ruud with supercid. No ota.
Sent from my Sony Tablet S using xda app-developers app
Click to expand...
Click to collapse
I've done it many times :\
Sent from my Nexus 4
Megadoug13 said:
I'm glad my phone is working too, am I looking forward to sense 5 roma coming out soon. I really want blinkfeed lol
Sent from my HTC One X using xda app-developers app
Click to expand...
Click to collapse
Sense 5 is already out. Look in the "getting port to boot" thread.
Sent from Xparent Red using my Venomized Evita
mirGantrophy said:
As long as you aren't taking an ota supercid won't hurt you
Click to expand...
Click to collapse
Its been well documented here (happened to more than a few folks):
3.18 RUU + SuperCID + S-On = brick
redpoint73 said:
Its been well documented here (happened to more than a few folks):
3.18 RUU + SuperCID + S-On = brick
Click to expand...
Click to collapse
Doesn't seem to be limited to 3.18 RUU as the RUU I used was for an older software ver. since telus never released a 3.17 ruu.
exad said:
Doesn't seem to be limited to 3.18 RUU as the RUU I used was for an older software ver. since telus never released a 3.17 ruu.
Click to expand...
Click to collapse
Yeah, I saw you commented on the Telus RUU in a previous reply earlier on this thread. I hadn't heard of RUUs for other carrier (aside from 3.18 from AT&T) bricking due to SuperCID and S-on, so I was just commenting on what I knew.
redpoint73 said:
Its been well documented here (happened to more than a few folks):
3.18 RUU + SuperCID + S-On = brick
Click to expand...
Click to collapse
I have only done an ruu with supercid and s-on with 1.44, 1.73, 1.85 and 2.20, I guess at&t put in some extra security measures. I never bricked on those. But my phone did catch on fire fwiw
Sent from my Nexus 4
mirGantrophy said:
I have only done an ruu with supercid and s-on with 1.44, 1.73, 1.85 and 2.20, I guess at&t put in some extra security measures. I never bricked on those. But my phone did catch on fire fwiw
Click to expand...
Click to collapse
Yup, on older firmwares it was fine to RUU with SuperCID and S-on. But not so on 3.18. Nobody here really knows why 3.18 bricks the phone under these conditions, but it does.
redpoint73 said:
Yup, on older firmwares it was fine to RUU with SuperCID and S-on. But not so on 3.18. Nobody here really knows why 3.18 bricks the phone under these conditions, but it does.
Click to expand...
Click to collapse
I have a feeling it has to do with the write protection that gets implemented.
any jellybean update for evita with supercid + s-on will brick
exad said:
Redownload twrp, check md5
fastboot flash recovery recoveryfilename.img
Fastboot erase cache
Fastboot reboot-bootloader
select recovery
If that doesnt work, since youre s-off, just ruu.
Sent from my Sony Tablet S using xda app-developers app
Click to expand...
Click to collapse
Wow I did the same thing thank you.
redpoint73 said:
Its been well documented here (happened to more than a few folks):
3.18 RUU + SuperCID + S-On = brick
Click to expand...
Click to collapse
That being said.... I believe I was the first to experience it lol
Sent from my HTC One XL using xda app-developers app
i've stuck with cwm since release since i havent had any of the same twrp woes. even with twrp 2.3.3.1 i still had problems with getting into recovery from bootloader, which is a pain when you are bootlooping. usually if you manually get into bootloader without the phone plugged into pc then once in bootloader you plug your phone into pc you have a better chance of getting it to load on the first try, same goes for getting unlock token to take.
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?