Related
Especially for people who rooted their phones recently using X-Factor root exploit
"If you have the newer HBOOT 1.14 (you probably do if coming from stock 2.20), boot.img's will have to be flashed separately via fastboot. Extract the boot.img from you ROM zip of choice and put it in the same directory as fastboot. Reboot your device into boot loader and run "'fastboot flash boot boot.img' (no quotes)
You can then flash the ROM" - thanks to
Guylncognito721
How to flash Custom Recovery and ROM after 2.20 root - http://forum.xda-developers.com/showthread.php?p=33179690
More information
"if you are flashing similar ROMs ( having same kernel ).. there is no need to flash boot.img separately. But say if you wanna switch from sense to aosp you must do that as they have different kernels.
Again if you are just upgrading from older version to newer version of same ROM and if there are no kernel changes no need to flash it" (thanks kancherlapraneeth)
I have seen so many topics in Q&A thread regarding this issue, thought this would help ppl
Butchered my name...
Sent from my One X using xda app-developers app
GuyIncognito721 said:
Butchered my name...
Sent from my One X using xda app-developers app
Click to expand...
Click to collapse
Sorry bro.. Corrected it
If you have flashed viperROM from stock 2.20 do you still have 1.14 boot? Do I still have to flash boot separate?
And would it be worth it to just ruu to 1.85
Sent from my HTC One XL using xda app-developers app
Kole_Ackerson said:
If you have flashed viperROM from stock 2.20 do you still have 1.14 boot? Do I still have to flash boot separate?
And would it be worth it to just ruu to 1.85
Sent from my HTC One XL using xda app-developers app
Click to expand...
Click to collapse
Yes.
Yes.
You can't ruu to 1.85 as downgrading hboot is not possible.
Sent from my One X using xda app-developers app
GuyIncognito721 said:
Yes.
Yes.
You can't ruu to 1.85 as downgrading hboot is not possible.
Sent from my One X using xda app-developers app
Click to expand...
Click to collapse
Oh wait, s-off is needed to downgrade isn't it.. haha blonde moment
Sent from my HTC One XL using xda app-developers app
Bumping this.
WR
Sent from my HTC One X
So what happens if you don't? I did the exploit and then installed Calkulin's ROM and it seems to be going fine without flashing the boot.img. Maybe this is why another ROM I tried didn't work (got stuck on the Paranoid Android screen).
ChummyDays said:
Because it stays on the stock kernel. Paranoidandroid got stuck because it probably can't run on the stock kernel... calkulin's ROM is somewhat close to the stock ROM (4.0.4 and sense)
Sent from my One X using xda app-developers app
Click to expand...
Click to collapse
Aha, good to know. Thanks!
Ok I am getting "sending 'boot' (6156 KB)... FAILED (status read failed (Too many links)) any help?
The_new_user said:
Ok I am getting "sending 'boot' (6156 KB)... FAILED (status read failed (Too many links)) any help?
Click to expand...
Click to collapse
did you type
fastboot flash boot boot.img
absolutelygrim said:
did you type
fastboot flash boot boot.img
Click to expand...
Click to collapse
Yes I am in the correct directory and have my boot.img there I am typing fastboot flash boot boot.img I even tried fastboot erase cache but I am still getting the too many links error.
Going to try rebooting the computer and phone to see what happens I will report back if it fixes it.
Ok a reboot of the phone and comp was no help.
" OK I fixed it. All I did was change usb ports on my computer and it went straight through. " Hope this helps someone else later on.
need help
Can i please get some need some help
I'm currently on paranoid android 2.51 jb ROM. I did the root exploit since I was stuck on 2.20
And before I flashed paranoid android I made a twrp backup of stock sense.
Ok this is what I need help on because I was on 2.20 I had to flash the boot.img along with the custom ROM to get it working, now what I need to know is if I restore my twrp backup do I need to flash the boot.img so I can go back to stock? If so how can I get the boot.img from my backup that I made? I copied backup to my computer to look for the boot.img but there's nothing there
I wanted to post here before I make a new thread
TWRP restore does not boot
I used TWRP 2.3.1 to back up the rooted stock rom on my AT&T One X firmware 2.20. I then proceeded to flash Viper X 2.6.0 but the phone was stuck in boot loop even after I flashed the boot.img in the Viper zip file. I was able to get back into TWRP and run the restore. However, the phone continues to be in a boot loop even after the restore.
Did I miss any steps in the restore process for TWRP?
ViperX isn't for you phone. Your lucky you can get back into twrp. You need to flash your boot.img backup in fastboot.
For people trying to flash the style backup and can't find the boot.img you should be able to fastboot boot.emmc.win just as a normal boot.img.
http://forum.xda-developers.com/showthread.php?p=33743517
Sent from my One X using xda premium
Boot.img and now no image display
hello friends, was trying to root the One X att and for several times but reading the roms were not entered into the system, just by downloading the boot.img boot.img_1.88.707.2 and sent only the boot.img via fastboot, now put the original system goes, but not no picture on display, I can hear the sound of the system by opening and receiving emails but no picture. please help me because I do not know what else to do.
irosemberg said:
hello friends, was trying to root the One X att and for several times but reading the roms were not entered into the system, just by downloading the boot.img boot.img_1.88.707.2 and sent only the boot.img via fastboot, now put the original system goes, but not no picture on display, I can hear the sound of the system by opening and receiving emails but no picture. please help me because I do not know what else to do.
Click to expand...
Click to collapse
Can you give more details on what version are you on (2.20?)and are you able to boot??
Create a separate post in Q&A and many people will respond ,this not appropriate place to ask
Sent from my Nexus 4 using xda premium
I think I know what my problem was. I flashed the rom first THEN the boot.img. Which caused it to get stuck at the boot animation and I would have to go to the boot loader and flash the boo.img.
---------- Post added 12th February 2013 at 12:16 AM ---------- Previous post was 11th February 2013 at 11:40 PM ----------
sschrupp said:
So what happens if you don't? I did the exploit and then installed Calkulin's ROM and it seems to be going fine without flashing the boot.img. Maybe this is why another ROM I tried didn't work (got stuck on the Paranoid Android screen).
Click to expand...
Click to collapse
Ya same issue here too. My mistake was i flashed the boot.img after I flashed the rom. So now I'm rooting and flashing again and see if flashing boot.img the first time works.
I feel so stupid now. I kept doing fastboot boot boot.img. Not fastboot flash boot boot.img. No wonder it always stuck in the boot animation screen all the time. So I flash the boot img then i flash the rom from recovery? What do I wipe in TWRP?
I downloaded rom put it in downloads folder on phone. Then I got into fastboot and flashed boot img and erased cache. Then I did a factory reset and flashed rom. First option is to run boot img, so the first time I tried install I didn't do it using aroma installer went through all the steps. Then I rebooted phone and it was stuck on HTC screen with no boot animation. It was just stuck. Went back to recovery and wiped then installed again this time using option to run boot img. Same thing happened witch was nothing. Any advice for a noob would be appreciated. :good:
HTC ONEX (loving it)
Samsung galaxy S2 (retired)
Did you check the md5 of the zip? Sounds like it might be a bad download
Sent from my VENOMized HoxL
area51avenger said:
Did you check the md5 of the zip? Sounds like it might be a bad download
Sent from my VENOMized HoxL
Click to expand...
Click to collapse
No But i will I have never had that problem before.
Try to flash the rom with either option, the boot into bootloader to fastboot the boot.img.
On my cousins phone it won't take when I fastboot the boot.img first... It works 100% the time when I flash the rom first then do the boot.img... Try it out homie
Sent from my One X using Tapatalk 2
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.
Picked up an inspire 4g off of cl.Paid 20 for it because it had no battery. Put a batter in it and it boots to the htc screen, black screen, then reboots. Volume down was broken but I fixed it and am able to enter hboot. Phone had already been unlocked through htcdev. So I relocked it and ran the newest 3.20 RUU. It completed successfully and rebooted. However, it does the same thing. So I tried to factory reset it through bootloader. Again it just reboots and does the same thing. So I decided to try to htc dev unlock it and flash a custom recovery. Everything went smooth and recovery flashed. But when I select recovery in bootloader it does the same bootloop over again. Again I've tried using the latest RUU to no avail. Ive tried everything I know of to do. I'm out of ideas. It seems like a great phone and I really want to fix this so any help would be greatly appreciated.
If the bootloader is unlocked and you can flash a ROM, fastboot flash the boot.img from the ROM zip and see if it works. Detailed instructions in my signature.
bananagranola said:
If the bootloader is unlocked and you can flash a ROM, fastboot flash the boot.img from the ROM zip and see if it works. Detailed instructions in my signature.
Click to expand...
Click to collapse
Unfortunately I can't enter recovery to flash a rom. It just reboots at the white screen. The only thing I was able to flash was the stock RUU. And it still didn't boot. I've also tried flashing recoveries but that doesn't work either. It flashes successfully but never boots into it.
Sent from my XT897 using xda app-developers app
No one knows what to do? I really want to fix this.
Sent from my XT897 using xda app-developers app
I got a free inspire 4g, well two of them, one neeeds a new screen and this one seems like i just have to reinstall android. Problem is, how do i do this? Uploading pics of the hboot and other pics as well
Does it have a custom recovery installed? If not, install one using fastboot. Then flash ROMs from recovery. Don't forget to flash the boot.img from fastboot afterwards.
bananagranola said:
Does it have a custom recovery installed? If not, install one using fastboot. Then flash ROMs from recovery. Don't forget to flash the boot.img from fastboot afterwards.
Click to expand...
Click to collapse
Not sure, its clockworkmod v5.0.2.0 i have a PD98IMG.zip i downloaded for the stock rom but it says wrong image or bad image. Give me a short walkthrough on what to do if you could, thanks!!
devakaozzy said:
Not sure, its clockworkmod v5.0.2.0 i have a PD98IMG.zip i downloaded for the stock rom but it says wrong image or bad image. Give me a short walkthrough on what to do if you could, thanks!!
Click to expand...
Click to collapse
Not the stock ROM, a custom ROM. Wipe, then flash it from ClockworkMod (which is a custom recovery). Then flash the boot.img from that ROM zip in fastboot.
Ended up switching the screen over to a different inspire that needed a screen.
Sent from my Inspire 4G