Database Info

[Q] S4 , cant access my recovery or boot normally!

i cannot boot phone into recovery nor can i boot phone normally... I had just installed Viper one S rom on my phone and rebooted into recovery because my wifi wasnt working , so i was just going to revert back to an old rom. After clicking reboot to recovery from Viper rom the screen just went white . I had to power it down manually, after powering it up it would stop at htc screen with the red development lines... tried to go into recovery and it will come up for a second then disapear then phone reboots.... any ideas? oh I also had installed Latest radio in CWM after installing rom.. I hear its buggy in CWM...

I had the same problem. Did you flash the boot.IMG in recovery or fastboot? If you flashed in recovery and its not supported by your hboot version. That could be the issue. Try re flashing the boot.IMG using fastboot. If you still cannot get it to work. I would try reinstalling a custom recovery manually and restarting the Rom flashing process. There are forums all over the place to help with that. Try twrp. Ps this is all assuming you are able to get into your boot loader.
Sent from my HTC One S using xda app-developers app

Problem fixed. Don't ask me how lol. All I did was relock boot loader and flash stock ROM. Stock ROM would not load so I just decided to unlocked boot loader and phone rebooted fine. Recover works to.. crazy.
Sent from my HTC One S using xda premium

That happened to me when I didn't fast boot flash the boot.IMG file, but only the latest Viper has given me grief with that.
Sent from my HTC One S using xda app-developers app

MrPickleFicker said:
That happened to me when I didn't fast boot flash the boot.IMG file, but only the latest Viper has given me grief with that.
Sent from my HTC One S using xda app-developers app
Click to expand...
Click to collapse
Good to know so I won't make the same mistake twice.
Sent from my HTC One S using xda premium

Jb 4.2.x roms

I read on flip board that cm 10.1 is official for our phone and I I want to flash it and I did but the after I flash it and flash the boot.IMG it get stuck on the HTC logo and I see that the soft key button turn on and have vibration when I touch them can anyone help .
Sent from my HTC One S using xda premium

Do you have an S4 or S3 phone
Did you check md5 for good/bad download
Did you wipe all including System 2x in recovery
Which recovery are you using

I have s4 and I didn't check the md5 cause all 4.2 ROMs have the same problem for me,i have twrp
Sent from my HTC One S using xda premium

which version twrp. some of the later 2.3's had issues
otherwise if you are wiping all and fastbooting boot, not sure
fastboot boot after rom and fastboot erase cache before booting onto rom

rugmankc said:
which version twrp. some of the later 2.3's had issues
otherwise if you are wiping all and fastbooting boot, not sure
fastboot boot after rom and fastboot erase cache before booting onto rom
Click to expand...
Click to collapse
I have v 2.3.3.0 for twrp I'll update it and try what you said and report back here if it works
Sent from my HTC One S using xda premium

i had 2.3.3.0 and it was not one of the bad ones

Still doesn't work and I tried force md5 sum check on twrp and it failed could that be the problem
Sent from my HTC One S using xda premium

brandontamas said:
Still doesn't work and I tried force md5 sum check on twrp and it failed could that be the problem
Sent from my HTC One S using xda premium
Click to expand...
Click to collapse
I'd reccomend clockworkmod over twrp, had more bootloops with twrp in the past.
Also, good alternative rom is dark jelly cm10.1 with android 4.2.1 stable and reliable, using it a pretty long time.
Easy install via an automatic installer program called aroma installer, no need to flash boot.img here
http://forum.xda-developers.com/showthread.php?t=2051865
Sent from my One S using xda app-developers app

yes, ck your md5's. i use es explorer and it is easy
as john said you can try another rom, but still ck md5 and wipe system as part of your wipes
if you flash a rom with aroma, don't wipe in recovery and aroma. only one. i prefer recovery
as for cwm or twrp. everyone has their favorite. it is my understanding though cwm hasn't kept pace on updates with later version roms afaik
hope you get it--

Problems After S-Off

I have an AT&T One XL and have had problems recently. I unlocked my bootloader last year on the 2.20 firmware, which is how the phone came. I was able to flash ROMs no problem. About 3 weeks ago I decided to go S-Off with the whole thing. The S-Off was successful, I immediately flashed a new splashscreen and it is confirmed in bootloader that I am S-off. Last week I tried to flash the stable CM10 build, but it was unsuccessful. I found that the only ROMs I am able to flash are Sense ROMs 4.1.1 and above, or AOSP ROMs that are 4.2.x or above. I am on hboot 1.14 and I am very confused as to why I cannot flash properly. I am on TWRP 2.4.1.0, but have used various recoveries trying to solve the problem. I have also RUU'd trying to fix the problem, but to no avail. Any help would be much appreciated!

Twrp 2.4 has issues with wiping properly. Have you tried a different version or wiping with adb in fastboot?
Sent from my HTC One X using xda premium

From what I understand twrp 2.4.1 should be working but I would flash 2.3.x just in case, then do fastboot erase cache. Then wipe cache, dalvik, system, factory reset.
If you RUUd and are s-off why are you still on 1.14? You may as well go up to 2.14 then downgrade touchscreen to use AOSP. Super easy.
Since S-OFF is just a security flag, I am 100% sure it's not the cause of your issue.
Sent from my One X using xda app-developers app

exad said:
From what I understand twrp 2.4.1 should be working but I would flash 2.3.x just in case, then do fastboot erase cache. Then wipe cache, dalvik, system, factory reset.
If you RUUd and are s-off why are you still on 1.14? You may as well go up to 2.14 then downgrade touchscreen to use AOSP. Super easy.
Since S-OFF is just a security flag, I am 100% sure it's not the cause of your issue.
Sent from my One X using xda app-developers app
Click to expand...
Click to collapse
I haven't wiped in fastboot because I thought that's what wiping in recovery was for, I really appreciate all of the input and I will be trying both of these things as soon as I'm done with dinner. Man's gotta eat, ya know :laugh:

Lol. Yep.
Sent from my HTC One X using xda premium

Only fastboot erase cache! The rest of the wiping is done in recovery!
Sent from my One X using xda app-developers app

exad said:
Only fastboot erase cache! The rest of the wiping is done in recovery!
Sent from my One X using xda app-developers app
Click to expand...
Click to collapse
As a question, what is the difference between wiping cache in recovery and the fastboot command?

Downgrade twrp to 2.3.3.1
Sent from the HOXL dimension of S-OFF

The fastboot command wipes a cache related to the recovery. Wiping cache in recovery wipes a cache relating to the rom.
Sent from my One X using xda app-developers app

exad said:
The fastboot command wipes a cache related to the recovery. Wiping cache in recovery wipes a cache relating to the rom.
Sent from my One X using xda app-developers app
Click to expand...
Click to collapse
So I wiped cache via fastboot, and flashed the ROM like i normally would (wipe everything in recovery), but nothing has changed. I still get hung up on the splashscreen when trying to boot the new ROM. ViperXL boots fine when I restore my NANDroid backup, though.

Did you try flashing the boot.img after? You're still on hboot 1.14 afterall. I haven't seen first hand if you can skip flashing the boot.img with s-off, in your case, it seems not.
Sent from my One X using xda app-developers app

exad said:
Did you try flashing the boot.img after? You're still on hboot 1.14 afterall. I haven't seen first hand if you can skip flashing the boot.img with s-off, in your case, it seems not.
Sent from my One X using xda app-developers app
Click to expand...
Click to collapse
Even without flashing the boot.img, it should go past the splashscreen to the boot animation, am I wrong?

You are wrong. It may depending on the kernel previously installed
Sent from my One X using xda app-developers app

exad said:
You are wrong. It may depending on the kernel previously installed
Sent from my One X using xda app-developers app
Click to expand...
Click to collapse
Sorry to sound like a complete noob, I've been rooting ect for 2.5 years and never seen this problem. Could you please explain a bit more what you mean by the previous post. Are you saying it's the kernel or the boot.img not being installed correctly?

WeiblezWobble said:
Sorry to sound like a complete noob, I've been rooting ect for 2.5 years and never seen this problem. Could you please explain a bit more what you mean by the previous post. Are you saying it's the kernel or the boot.img not being installed correctly?
Click to expand...
Click to collapse
flashing the boot.img is flashing the kernel. you don't sound like a complete noob so don't worry.

I'm going to try again right now to flash the boot.img and then the ROM like normal, reporting back in 15 mins

WeiblezWobble said:
I'm going to try again right now to flash the boot.img and then the ROM like normal, reporting back in 15 mins
Click to expand...
Click to collapse
wipe everything first of course. cache dalvik system and factory reset. i dont mean to treat you like a noob but its better to be extra specific than not specific enough

exad said:
wipe everything first of course. cache dalvik system and factory reset. i dont mean to treat you like a noob but its better to be extra specific than not specific enough
Click to expand...
Click to collapse
Alright, tried it all exactly how you said and it had the same response, got stuck on splashscreen. I am completely puzzled

WeiblezWobble said:
Alright, tried it all exactly how you said and it had the same response, got stuck on splashscreen. I am completely puzzled
Click to expand...
Click to collapse
alright so just to be sure. first off youre on twrp 2.3.x right?
you wipe cache, dalvik, system and factory reset right?
then you flash the rom and the boot.img right? (doesnt matter what order these are flashed)
and still bootlooping?

exad said:
alright so just to be sure. first off youre on twrp 2.3.x right?
you wipe cache, dalvik, system and factory reset right?
then you flash the rom and the boot.img right? (doesnt matter what order these are flashed)
and still bootlooping?
Click to expand...
Click to collapse
Exactly, but just to be 100% clear, I am getting stuck at the splashscreen, and it just sits there infinitely.

[Q] Need help recovery only working

I have a HTC Inspire 4G, I got the bootloader unlocked and had it rooted. I had CWM Recovery on it that was like version 5.8 the one before that. I tried flashing a jellybean firmware, the phone never went by past the HTC white screen. I tried updating the recovery and it still didn't work. Right now my phone can only boot into hboot and that's still unlocked, but fastboot commands won't work, I can only flash new recoveries, but no ROMs actually get flashed. I tried using the PDimg thing for HBOOT to get back into full stock, I followed all the rules about going to ext3 (can't remember off the top of my head). It won't see the image, I've tried everything out there. ADB won't see the device unless in recovery mode, fastboot won't work, except to flash new recoveries.
Any possible ideas?

After flashing a ROM you need to fastboot flash thr ROM zip's boot.img.

Even if it doesn't boot into the ROM? It should work?
Sent from my Nexus 4 using xda app-developers app

No. I missed that. Can you fastboot flash a recovery? If not, you can try running a RUU.

Yeah I am able to flash a recovery via fast boot, but to actually do any other commands via fast boot it won't recognize anything. HBOOT won't see any .zips, tried everything.
Sent from my Nexus 4 using xda app-developers app

I don't understand. Where are these zips? Computer or phone?

Phone. The .zips are like the pd98img things. Those don't read on my phone from HBOOT
Sent from my Nexus 4 using xda app-developers app

Wait, if you have a working recovery, just flash a ROM (not PD98IMG) zip from the recovery (not fastboot). Download a custom ROM, full wipe in recovery, and flash in recovery.

Tried that. It seriously just sits there till the battery dies trying to turn on, doesn't pass the HTC white screen.
Sent from my Nexus 4 using xda app-developers app

And then extract the boot.img from the ROM zip and fastboot flash boot boot.img.

I love you haha
Sent from my Nexus 4 using xda app-developers app

[Q] Fresh Start

Hi all, I just wanted to start by saying that xda is the shizz and has helped me through thick n thin. Anywho, I have a custom Rom and am trying to go to a different Rom. ViperX to be specific. I've tried before, but with little success. Extracted boot.img, fastboot flash boot boot.img in the command, put the Rom on my sd and installed via TWRP. Problem is, is that it never boots, only the HTC boot screen with the red writing. Anyone have any suggestions on what I need to do? I'm still S-on, but from what I understand, that doesn't matter if you fastboot the boot.img via command prompt. I also have Hboot 1.14.
Thanks.

Chuckles850 said:
Hi all, I just wanted to start by saying that xda is the shizz and has helped me through thick n thin. Anywho, I have a custom Rom and am trying to go to a different Rom. ViperX to be specific. I've tried before, but with little success. Extracted boot.img, fastboot flash boot boot.img in the command, put the Rom on my sd and installed via TWRP. Problem is, is that it never boots, only the HTC boot screen with the red writing. Anyone have any suggestions on what I need to do? I'm still S-on, but from what I understand, that doesn't matter if you fastboot the boot.img via command prompt. I also have Hboot 1.14.
Thanks.
Click to expand...
Click to collapse
Because you are S-ON with hboot 1.14 you ALWAYS ALWAYS ALWAYS need to fastboot flash boot boot.img from the rom you are flashing.
That being said, Sounds like you are on TWRP 2.4.x please confirm.
If so, fastboot flash twrp 2.3.x.x
then fastboot erase cache
then wipe cache, dalvik, system, factory reset
Install rom and fastboot flash boot boot.img
Keep me posted.

exad said:
Because you are S-ON with hboot 1.14 you ALWAYS ALWAYS ALWAYS need to fastboot flash boot boot.img from the rom you are flashing.
That being said, Sounds like you are on TWRP 2.4.x please confirm.
If so, fastboot flash twrp 2.3.x.x
then fastboot erase cache
then wipe cache, dalvik, system, factory reset
Install rom and fastboot flash boot boot.img
Keep me posted.
Click to expand...
Click to collapse
Will do thank you
Sent from my HTC One XL using xda app-developers app

exad said:
Because you are S-ON with hboot 1.14 you ALWAYS ALWAYS ALWAYS need to fastboot flash boot boot.img from the rom you are flashing.
That being said, Sounds like you are on TWRP 2.4.x please confirm.
If so, fastboot flash twrp 2.3.x.x
then fastboot erase cache
then wipe cache, dalvik, system, factory reset
Install rom and fastboot flash boot boot.img
Keep me posted.
Click to expand...
Click to collapse
Apparently there's a TWRP 2.4.4 out, would it hurt me to flash the latest version?
Sent from my HTC One XL using xda app-developers app

Yes. It would hurt anyone with a one xl as 2.4 does not wipe our device properly. I tested 2.4.4 myself.
Sent from my HTC One X using xda app-developers app

ok, well I found another problem you might be able to help me with, but I'll shoot it to you anyway. I just found out my phone was originally a One X when I got it from the ATT store. Now apparently after I flashed the Rom I got (odex-JB-Sense4+.zip), It's saying my phone is an XL. Seems to me I have a whole new set of issues. Did I flash the wrong Rom? I though I did enough research to find a compatible Rom. How do I find out for sure what's going on with my phone and how to fix it properly?

Chuckles850 said:
ok, well I found another problem you might be able to help me with, but I'll shoot it to you anyway. I just found out my phone was originally a One X when I got it from the ATT store. Now apparently after I flashed the Rom I got (odex-JB-Sense4+.zip), It's saying my phone is an XL. Seems to me I have a whole new set of issues. Did I flash the wrong Rom? I though I did enough research to find a compatible Rom. How do I find out for sure what's going on with my phone and how to fix it properly?
Click to expand...
Click to collapse
No problem you have the correct ROM, if you had flashed wrong one it would have not worked correctly. Depending on the ROM sometimes it will show XL instead of X.

One xl is the proper model name, code named Evita, not to be confused with the real HTC One X international quad core version.
So in other words, nothing is wrong. This is normal. If you flashed the wrong rom you would know as you would now have a paperweight
Sent from my HTC One X using xda app-developers app

ok cool, I was kinda confused there for a sec lol. Ok, now for the TWRP. I'm assuming you were referring to 2.3.0.0? just because there is a 2.3.0.0, 2.3.1.0, 2.3.3.0, and a 2.3.3.1. I just want to make sure I have the correct one for Hboot 1.14

Doesn't matter which one. I use 2.3.3.1 myself.
Sent from my HTC One X using xda app-developers app

You have an xl so be sure to download and flash ViperXL and not ViperX. Luckily Viper does a model check before it installs.
Sent from my HTC One X using xda premium

ok, downloading it now. I'll keep you updated.

bkmo said:
You have an xl so be sure to download and flash ViperXL and not ViperX. Luckily Viper does a model check before it installs.
Sent from my HTC One X using xda premium
Click to expand...
Click to collapse
Ah I didn't catch that in the first post! Good eye.

bkmo said:
You have an xl so be sure to download and flash ViperXL and not ViperX. Luckily Viper does a model check before it installs.
Sent from my HTC One X using xda premium
Click to expand...
Click to collapse
ok, I'll keep that in mind. Thank you!!

exad said:
Ah I didn't catch that in the first post! Good eye.
Click to expand...
Click to collapse
it's ok bud, just downloaded and installed TWRP 2.3.3.1 successfully, now i'm downloading ViperXL and hope everything comes out ok

exad said:
Because you are S-ON with hboot 1.14 you ALWAYS ALWAYS ALWAYS need to fastboot flash boot boot.img from the rom you are flashing.
That being said, Sounds like you are on TWRP 2.4.x please confirm.
If so, fastboot flash twrp 2.3.x.x
then fastboot erase cache
then wipe cache, dalvik, system, factory reset
Install rom and fastboot flash boot boot.img
Keep me posted.
Click to expand...
Click to collapse
Should I need to be thinking about Kernels of any sort?

Chuckles850 said:
Should I need to be thinking about Kernels of any sort?
Click to expand...
Click to collapse
Yeah.......give bulletproof 1.1 a shot. Gonna give you better performance and battery, plus a no brainer install and its stable.
Sent from my Transformer TF101 using xda premium

bkmo said:
Yeah.......give bulletproof 1.1 a shot. Gonna give you better performance and battery, plus a no brainer install and its stable.
Sent from my Transformer TF101 using xda premium
Click to expand...
Click to collapse
Ok cool. Any links?
Sent from my HTC One X using xda app-developers app

It's in Android development page. if not the first page then the second.

exad said:
Because you are S-ON with hboot 1.14 you ALWAYS ALWAYS ALWAYS need to fastboot flash boot boot.img from the rom you are flashing.
Click to expand...
Click to collapse
Except for ViperXL (and old builds of CleanROM, which may also happen with future builds if/when scrosler gets AROMA back in there) which is intended to flash the boot.img in AROMA.
Although, it doesn't always work for some folks, so they have had to flash boot.img manually. So yes, if at all in doubt (and you have a boot loop) flash boot.img manually.