Database Info

[Q] Can't boot into recovery on HTC One X

I've installed TripNRaver's AOKP ROM on my One X and now I can't boot into recovery.
I've unlocked the bootloader
ADB seems to work fine but when I try adb reboot recovery it says device not found
I can connect my phone to my laptop and transfer files on to it
I've managed to get CWM on it by downloading the APK and transferring it to my phone
I can boot into bootloader but when I select Recovery it just boots into TripNDroid's ROM
I have downloaded the RUU and try to run it off my friend's PC (i'm on osx) but that couldn't seem to locate my phone either
When my phone is plugged in fastbood does change to fastboot USB
Any ideas?

It sounds like you have "fastboot" checked somewhere in settings. Not the fastboot you use to flash, but the one that makes the phone boot up quickly.

I don't think so. I can't even find that in settings. I think that's a Sense thing not an aokp thing. I've discovered that I need to lock the bootloader to run ruu so i've done that. I'll borrow my friend's pc again and try that again. If that fails... any other ideas?

under options/power there's a checkbox which enables fastboot, what lowandbehold mentioned. disable this and you should be able to boot with power+volumedown to fastboot and from there to recovery.

I'm pretty sure that's a Sense thing you know. It's not on here.

get in the bootloader, fastboot erase cache, problem solved...

I did this before and it didn't work. I tried it again just now and somehow it worked. I have no idea why or how but it did. So thank you!

Won't go into recovery
First post on here, so be gentle!
Rooted One X that I'm trying to install the ARHD on using the instructions here: http://forum.xda-developers.com/showthread.php?t=1562603
Before I tried this, I had root access and Clockwork Recovery installed. All working fine.
So, read the instructions on the thread, but have only got as far as flashing the boot.img - which gave me the OKAY! to tell me it was successful and the cache erase OKAY as well.
So all I need to do is the superwipe and then flash the ARHD ROM from recovery.
That is the problem - I now can't access recovery. Fastboot isn't enabled, I've tried using vol-down/power, QuickBoot app and select 'recovery', etc., but each time it tries to go to recovery I see an Android character with his stomach internals on show for a split second, and then the phone just reboots normally. I've tried erasing the cache again from bootloader, but after that it still won't go into recovery.
Am I missing something simple here, or can anyone suggest what I need to do?

JC12345 said:
First post on here, so be gentle!
Rooted One X that I'm trying to install the ARHD on using the instructions here: http://forum.xda-developers.com/showthread.php?t=1562603
Before I tried this, I had root access and Clockwork Recovery installed. All working fine.
So, read the instructions on the thread, but have only got as far as flashing the boot.img - which gave me the OKAY! to tell me it was successful and the cache erase OKAY as well.
So all I need to do is the superwipe and then flash the ARHD ROM from recovery.
That is the problem - I now can't access recovery. Fastboot isn't enabled, I've tried using vol-down/power, QuickBoot app and select 'recovery', etc., but each time it tries to go to recovery I see an Android character with his stomach internals on show for a split second, and then the phone just reboots normally. I've tried erasing the cache again from bootloader, but after that it still won't go into recovery.
Am I missing something simple here, or can anyone suggest what I need to do?
Click to expand...
Click to collapse
Have the same problem.
what can we do?

[Q] Phone won't boot to system or recovery

So I tried to flash Magnolia X 1.0 coming from MIUI. After I wiped from MIUI and tried to install Magnolia I got an error. No big deal right? So I figured I would reboot recovery ( clockwork mod ) and try again, if it didn't work I could restore MIUI. When I hit reboot recovery I got stuck in a bootloop, from white htc screen to off. It just looks like it is trying to get to recovery but it is not loading it for some reason. So I decided to boot it into hboot and reflash the recovery, or possibly flash twrp. Now my problem is that the computer is not recognizing the phone, so none of my fastboot or adb commands do anything I just get <waiting for device>. Any ideas?

So right after I made the post I was able to get the drivers to reinstall and was able to re flash the recovery. Tried both CWM and TWRP and neither will boot. With TWRP I can get to the recovery splash screen but then it just goes black. Downloading the RUU now and I am going to try to flash that through the bootloader. Other than that I have no othe ideas...anyone else have any?

Got it...had to relock bootloader and run ruu then extract the stock recovery and flash it. Rebooted into recovery let it sit, then it rebooted back to the bootloader. Re-unlocked bootloader then flashed TWRP and it worked fine. Back up and running again.

Really frustrated, phone keeps booting to recovery after failing to boot to rom

Hi all, I've been trying for the past 8 hours(you can imagine how frustrated i am right now) to install HatkaXL(http://forum.xda-developers.com/showthread.php?t=2075783) for so long now and I have literally no idea where to go. I was only just trying to switch from cleanrom to Hatka. And I've ended up with absolutely no progress since 8 hours have passed. Actually, i've probably lost progress because i accidentally wiped my data without backing up. Here's what i've done so far:
i'm under AT&T, hboot-1.14, any other info i'll be glad to share. it's rooted and currently unlocked of course.
1. Used fastboot flash boot boot.img to no avail
2. Re-locked bootloader, ran an RUU(i made sure it was compatible), unlocked it and tried to flash HatkaXL froma fresh start
3. Wiped data, cache, etc. then flashed the rom(which still didnt work)
4. flashed TWRP, rebooted, went into TWRP, wiped data, cache, etc. and then flashed HatkaXL
What the problem is that my one x won't go past the HTC screen with all that red developmental font. It'll boot and then go to the screen, stay there for about 10 seconds and then turn off. Then it'll start up again 10 seconds later to boot back to TWRP.
At one point, i encountered a boot loop where it actually went past the red developmental font screen and to the HTCtm Beats Audio and then it just restarted from there. However, now that issue disappeared and it's just booting to recovery after shutting down.
Now that's where I was thinking that maybe since it's booting directly to TWRP that would mean that I would have to go into cmd and 'fastboot flash boot boot.img' right? I did exactly that, one, twice, three times, even with fastboot erase cache.
i can't even remeber everything i did because i'm so tired since i've been up through the night reading throug threads, trying to fix this damn thing.
I would really really appreciate it if anyone could help me out here because i've never been this lost when it came to technology lol.

It sounds like you were on the right track, I am lost why it failed for you?
Can you install cleanrom again? eg is it just HatkaXl that is not working? Perhaps your download is bad or the ROM is simply broken and you need to report it to the dev?
When you were flashing the boot.img did it say success? Did you triple check you are extracting the correct boot.img to the correct folder?
Just to be clear to install ROM's I often do:
1)wipe data and system
2)install ROM
3)fastboot flash boot boot.img

twistedddx said:
It sounds like you were on the right track, I am lost why it failed for you?
Can you install cleanrom again? eg is it just HatkaXl that is not working? Perhaps your download is bad or the ROM is simply broken and you need to report it to the dev?
When you were flashing the boot.img did it say success? Did you triple check you are extracting the correct boot.img to the correct folder?
Just to be clear to install ROM's I often do:
1)wipe data and system
2)install ROM
3)fastboot flash boot boot.img
Click to expand...
Click to collapse
Thanks for the response. Yep, every time i flash the boot.img, it's always a success. i also mae sure it's the correct one.
sending 'boot' (6156 KB)...
OKAY [ 0.933s]
writing 'boot'...
OKAY [ 1.475s]
finished. total time: 2.413s
Click to expand...
Click to collapse
I just tried to install cleanrom 5.1 again and it's not working either. Actually, it's stuck at the red developmental font screen this time so atleast it's not immediately rebooting to go to TWRP.
UPDATE: It's working! CleanROM! Thank you so much man! I'll be back to ask you another question. Gotta go real quick.

Correct me if I'm wrong but clean Rom 5.1 flashes the boot img for you I didn't see you flashing the boot.img the other times successfully so yes it won't get past that HTC screen

a box of kittens said:
Correct me if I'm wrong but clean Rom 5.1 flashes the boot img for you I didn't see you flashing the boot.img the other times successfully so yes it won't get past that HTC screen
Click to expand...
Click to collapse
I also noticed this. Op, a few things to remember when flashing boot.img.
The boot.img needs to be extracted from the rom you are flashing.
The phone must be in bootloader, plugged in to pc and in fastboot usb mode. (the phone will say fastboot usb.
The boot.img must be in the folder with the fast boot and adb programs.
I have more than just a feeling you were doing something wrong
Sent from my One X using xda app-developers app

Thanks for the responses guys, you guys are saving me lots of stress and time.
a box of kittens said:
Correct me if I'm wrong but clean Rom 5.1 flashes the boot img for you I didn't see you flashing the boot.img the other times successfully so yes it won't get past that HTC screen
Click to expand...
Click to collapse
You are correct that clean rom 5.1 flashes it for you, which is through its AROMA installer. However, HatkaXL also uses the AROMA installer, and there's a line in the installation screen where it says "flashing boot.img." - both ROMs have that line. Interestingly, it worked when I followed twistedddx's order so I'm going to try that again.
exad said:
I also noticed this. Op, a few things to remember when flashing boot.img.
The boot.img needs to be extracted from the rom you are flashing.
The phone must be in bootloader, plugged in to pc and in fastboot usb mode. (the phone will say fastboot usb.
The boot.img must be in the folder with the fast boot and adb programs.
I have more than just a feeling you were doing something wrong
Sent from my One X using xda app-developers app
Click to expand...
Click to collapse
Yup, I have those in the same folder correctly. I always extract the boot.img from the rom zip into the folder with both fastboot and adb(how else would I able to have fastbooted in the first place?), always made sure the phone was in bootloader, plugged in, and in fastboot usb.
edit: I wiped, then installed hatkaXL, then fastboot flash boot boot.img, and now it starts, it gets past the red developmental screen, INTO the HTC Onetm beats audio screen, turns off and then restarts again through the whole process. it's jst looping now.
edit2: Flashed ViperXL, that's working. I guess HatkaXL just isn't for my phone.. sigh. I hope this thread helps anyone else.

devfrost said:
Thanks for the responses guys, you guys are saving me lots of stress and time.
You are correct that clean rom 5.1 flashes it for you, which is through its AROMA installer. However, HatkaXL also uses the AROMA installer, and there's a line in the installation screen where it says "flashing boot.img." - both ROMs have that line. Interestingly, it worked when I followed twistedddx's order so I'm going to try that again.
Yup, I have those in the same folder correctly. I always extract the boot.img from the rom zip into the folder with both fastboot and adb(how else would I able to have fastbooted in the first place?), always made sure the phone was in bootloader, plugged in, and in fastboot usb.
edit: I wiped, then installed hatkaXL, then fastboot flash boot boot.img, and now it starts, it gets past the red developmental screen, INTO the HTC Onetm beats audio screen, turns off and then restarts again through the whole process. it's jst looping now.
edit2: Flashed ViperXL, that's working. I guess HatkaXL just isn't for my phone.. sigh. I hope this thread helps anyone else.
Click to expand...
Click to collapse
Could be a kernel issue.. Try flashing stock kernel after flashing rom?... That's all I can think of. Also, I don't know if you do but I always wipe cache, dalvik, system, and then factory reset in twrp and I've never had any issues with any roms.
Sent from my One X using xda app-developers app

BRICKED any fix?

so my stupid head downloads a s3 rom for my s4 hard and flashes it...
now its bricked but i can still get into recovery..
is this the end:[

No, wipe everything and reflash the right one. You should use TWRP so...
Depending on your bootloader version don't forget to 'fastboot flash boot boot.img' within fastboot mode. Remember: **** happens...

rootrider said:
No, wipe everything and reflash the right one. You should use TWRP so...
Depending on your bootloader version don't forget to 'fastboot flash boot boot.img' within fastboot mode. Remember: **** happens...
Click to expand...
Click to collapse
hopefully this works :[
i tried stock ruu but it says error the whole time.
im using twrp so ill try flashing a diff rom..

bstylz911 said:
hopefully this works :[
i tried stock ruu but it says error the whole time.
im using twrp so ill try flashing a diff rom..
Click to expand...
Click to collapse
For stock ruu you need to be on stock recovery, your device relocked. You can always do that after you've tried it the easy way. :good:

i completly forgot about the relocking...thank you so much

half brick htc one s s4
Hi, so after upgrading to MIUI.us_ville_v4_2.11.16_Eng_Deo_ZipA_Signed_linds6630 for some reason my htc one s s4 storage usb sotrage stopped working and now even wifi wont work, I've tried wiping installing many times and it didn't help.
So I went and flashed stock recovery and locked bootloader I got the ruu file and now it wont flash as I get signature error so went to check mainver and there is a problem it's all blank. I've tried to use mainver error fix from all in one toolkit ver3.3.1 and no luck as system can't mount sd. when on custom recovery windows couldn't recognize file system so i only had an option to format the storage, I didn't want to do that as miumi starts and I was affraid that this operation will wipe some data and I loose phone completely. So what can I do next, can you help me please?

[Q] help with tampered, locked, ruu, s off etc

I have a one sv which:
is k2 ul
normally boots only to HTC screen (no quietly brilliant) and stays there till the end of times
shows tampered locked, which i now changed unlocked status (htcdev)
s-on
has twrp recovery on, but swipes fail mostly
flashing roms in twrp recovery show success but result is still HTC logo without being quietly brilliant
can not be ruu-ed beucause the ruus i find are i think older than required
hboot 2.21, radio 1.18 version
s-off fails because tho fastboot recognizes phone, adb doesnt in fastboot mode and in bootloader pc thinks it is not attached (tried xp, 7, 8.1 and many different drivers)
i am not sure if usb debugging was on before the phone crashed
so i can't put an older ruu because of s-on, i can't get s-off because rumrunner and moonshine can't work without adb, and basically that is it.
does anyone PLEASE have any idea what to do?
and yes, the warranty is over and the phone has gone to the warranty twice with bootloop before.

After flashing a rom, did you also flash the boot.img of the rom with fastboot cmd?
Thats necessary, because you are S-on.
And what TWRP is installed?

old.splatterhand said:
After flashing a rom, did you also flash the boot.img of the rom with fastboot cmd?
Thats necessary, because you are S-on.
And what TWRP is installed?
Click to expand...
Click to collapse
yes i did.
twrp 2.6.3.2
now i have made such progress that twrp tells me it cannot mount int sd and when booting, phone stays on the htc logo for some seconds and then switches off. i believe i have actually made it worse (didnt think that could happen).
EDIT: so i formatted the storage like this http://forum.xda-developers.com/showthread.php?t=2576897 and it BOOTED
EDIT2: the phone now kind of works IF it boots. half of booting times it just switches off, the other half it switches off and then reboots and works. i think something is still kind of not good but i dont have the b***s atm to poke it more.
thank you all for your potential help.

What rom did you use?
Please also perform a full wipe (without internal/external sd) in recovery under Wipe -> Advanced

old.splatterhand said:
What rom did you use?
Please also perform a full wipe (without internal/external sd) in recovery under Wipe -> Advanced
Click to expand...
Click to collapse
it was this one http://forum.xda-developers.com/showthread.php?t=2512742 which is, as i understand, your work, thank you very much, donations will happen when im a tincy bit richer
and i will wipe some time later when im at home and courageous enough.

You can also try to restore this TWRP backup.

great news! today the phone restarted itself and froze on the logo. i tried to start twrp but it froze on that logo too. tried to do a factory reset, which removed the "tampered" sign until next reboot but that was about it.
now i can't reflash twrp or anything at all, with the error remote: image update error. oh please save me again.

Does not sound good.
You can boot into bootloader? Is it locked or unlocked? Did you reflash the recovery to check if you can boot into it?

looks bad indeed.
i can boot into bootloader, which is unlocked. and please specify what do you mean by reflashing the recovery (pardon my stupid brain)

When in bootloader, connect your phone to fastboot and try to flash recovery again.
If you can't get into recovery, i don't know, if there is much i can do for you

fastboot basically tells me to go f* myself with the error "remote: image update error" what ever I try to flash. right now Im trying to find a way to reflash twrp from ext sd. not doing so great

Well, about your country flag i suggest you speak (or you can at least read) russian language.
Go to 4pda.ru and look for the posts of "MikG". He has made zip files, similar to RUU. They are flashed from bootloader/Ruu mode. Maybe they can bring your phone back to life.
I can't tell you how to use this files, because i don't speak russian.

I'll try, thanks.
edit: and it just refuses to cooperate. it kind of does something in bootloader, but still doesnt boot past htc logo or if i try recovery, it stays on teamwin logo. i dont know if im doing something wrong or what... maybe i'll wait for the 4.2.2 hboot 2.21 radio 1.18 ruu then because i really dont know what else i could do.