Database Info

twrp suddenly not booting

i was craving some aosp so I wiped then flashed aokp. Want to switch back now, so I rebooted to recovery but twrp splashscreen shows for 2 seconds, then screen goes black. then the phone reboots into normal os. i tried reinstalling twrp via goomanager to no avail. will flashing the img make any difference? any one else have this issue?

ok i tried flashing the twrp img and still no go. gonna try ruu'ing now unless someone jumps in with a solution.

Are you rooted and bootloader unlocked?
Sent from my HTC One X using xda premium

yes... i've been around here for ages. just this problem is very weird. tried erasing recovery via fastboot and says fastboot remote not allowed FAILED. gonna ruu now.

if ruu dosent work try relocking bootloader by using the "fastboot oem lock" command i believe and then ruu
Sent from my HTC One X using xda premium

DJ-midnite said:
if ruu dosent work try relocking bootloader by using the "fastboot oem lock" command i believe and then ruu
Sent from my HTC One X using xda premium
Click to expand...
Click to collapse
lol thats what I just said but thanks anyway

k ruu'ed and all is back to normal. interestingly, no data was wiped when i relocked bootloader and flashed ruu.

and remember try wiping/factory reset when flashing aokp on twrp, and youre welcome
Sent from my HTC One X using xda premium

i done it again... help?

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.

S-off before at&t update

Is there an easier way of rooting after running ruu 3.18 update if I was already s-off?
Sent from my HTC One X using xda premium

If your bootloader is unlocked just flash twrp 2.3.3.1 or under. Then you can flash su or wipe everything and flash a ROM.
Sent from my One X using xda app-developers app

exad said:
If your bootloader is unlocked just flash twrp 2.3.3.1 or under. Then you can flash su or wipe everything and flash a ROM.
Sent from my One X using xda app-developers app
Click to expand...
Click to collapse
I've unlocked bootloader and installed twrp also flashed su and tried to flash CM10. I wiped cashe and and then installed CM10.1 and now it freezes on "HTC quitly briliant" screen and some warning notes under it.. what to do?
Is it necessary tu S-off?

Wipe everything not just cache. Then fastboot flash boot boot.IMG right before or after flashing the ROM. The boot.img should be extracted from the ROM you're flashing.
Sent from my One X using xda app-developers app

exad said:
Wipe everything not just cache. Then fastboot flash boot boot.IMG right before or after flashing the ROM. The boot.img should be extracted from the ROM you're flashing.
Sent from my One X using xda app-developers app
Click to expand...
Click to collapse
Is it necessary to S-off?

Only if you wish to ruu without bricking after supercid
Sent from my Sony Tablet S using xda app-developers app

Wouldn't the ruu lock the bootloader tho?
Nevermind it worked!
Sent from my HTC One X using xda app-developers app

mircony said:
Wouldn't the ruu lock the bootloader tho?
Click to expand...
Click to collapse
No. RUU doesn't "lock" anything. If S-on, you typically need to relock the bootloader to run an RUU (but as mentioned, running the 3.18 RUU with S-on and SuperCID will brick the device).
But with S-off, it doesn't matter if bootloader is locked or not.

HTC One X AT&T

Just bought a used One x At&t..I want to Root it but i dont know if its bootloader is locked or unlocked.It has got the Stock Rom & Stock recovery.
It says S-off in the bootloader menu..I want to Root it..Should i just go & Flash Custom recovery then go for the Rooting?

Well if you flash recovery and the bootloader is locked it will fail so there's not really any harm in trying.
Though it says In the bootloader if it's locked unlocked or relocked
Sent from my HTC One X using xda app-developers app

Bootloader is locked..Guess i have to unlock it first :crying:

Plug it in, fire up cmd prompt and type adb getvar cid
If it comes back as 11111111 simply unlock with htc dev, its super simple.
Then fastboot recovery.
You can always try the fastboot cmd
Fastboot oem unlock
Can't remember if that works or not lol. Probably not though just a thought since its already s-off
Since it is s-off you will ALWAYS be able to root very easily. :thumbup:
Sent from my HTC One X using Tapatalk 2

Sak3ater said:
Bootloader is locked..Guess i have to unlock it first :crying:
Click to expand...
Click to collapse
What's it matter if your phone has a tampered and unlocked tag?
Sent from my HTC One XL using xda app-developers app

[Q] Post root unable to access phone through ADB

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?