Related
Hi,
Can anyone please upload the boot.img file for the latest ics tiamat kernel (140312) for us HTCDEV unlocked users?
Thanx...
MG81 said:
Hi,
Can anyone please upload the boot.img file for the latest ics tiamat kernel (140312) for us HTCDEV unlocked users?
Thanx...
Click to expand...
Click to collapse
Can't you fetch it from official tiamat site?
Swyped from my Desire S using Tapatalk 2 beta 5
Nope... Need the boot.img in order to flash it manually via fastboot...
Sent from my Desire S using Tapatalk
Extract it from the kernel ZIP you're downloading from Tiamat site. As simple as that.
Jack_R1 said:
Extract it from the kernel ZIP you're downloading from Tiamat site. As simple as that.
Click to expand...
Click to collapse
Cayniarb doesn't put a boot.img in his ZIP, it's split into parts, so it's a bit more complicated than that.
Oh damn. Went downloading, checked. Here's the procedure:
Get into recovery.
Connect with USB to PC.
Flash the kernel in recovery (I know it won't flash, but you don't need it to).
Execute the following command on your PC:
adb pull /tmp/newboot.img
Click to expand...
Click to collapse
Congratulations, you have your new boot.img. Reboot to fastboot and flash it.
Thanks mate!
Sent from my Desire S using Tapatalk
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?
Whats this problem with the boot.img?
So to flash a rom, I need to flash the boot.img using the boot installer tool, then I put the rom on my SD card and flash it?
Do I also have to flash the boot.img to restore my phone from a previous recovery? I heard this somewhere and was a bit confused,
Just download a ROM from the phone itself. Use flash image GUI. Using flashgui app, Navigate to ROM you downloaded, click. It'll automatically flash kernel. Immediately after boot into recovery, flash entire ROM, then flash gapps if necessary... Profit
Sent from my One X using Tapatalk 2
CollegeProfesor said:
Whats this problem with the boot.img?
So to flash a rom, I need to flash the boot.img using the boot installer tool, then I put the rom on my SD card and flash it?
Do I also have to flash the boot.img to restore my phone from a previous recovery? I heard this somewhere and was a bit confused,
Click to expand...
Click to collapse
There are a couple of roms that are hboot 1.14 friendly right? Doesn't viper have the ability to flash the kernel upon install?
Sent from my HTC One XL using xda app-developers app
I'm not really into sense ROMs, but I know viperxl and cleanrom 5.1 you can flash ROM in recovery.. they're definitely good to have on your SD card as a safety net in case something goes crazy and there's no way to fast boot...
Sent from my One X using Tapatalk 2
Hello, I was trying to flash slim bean to my phone, and when trying to wipe Davik, I wiped the os for the system without a backup. I can now only get to the htc quietly brilliant page. Please help me.
U should be able to boot from what I know.. from the powered off screen... Go to bootloader if. U can
Sent from my HTC One X using xda app-developers app
He won't boot if he wiped the OS.
Just go into recovery, mount usb storage, copy a ROM from pc, flash it.
Sent from my Evita
timmaaa said:
He won't boot if he wiped the OS.
Just go into recovery, mount usb storage, copy a ROM from pc, flash it.
Sent from my Evita
Click to expand...
Click to collapse
Okay, so if I re-lock the bootloader, will I be able to go back to a stock rom, if I use an RUU for my phone? Or should I leave it unlocked and try to flash. S is on by the way.
Thenerdy0ne said:
Okay, so if I re-lock the bootloader, will I be able to go back to a stock rom, if I use an RUU for my phone? Or should I leave it unlocked and try to flash. S is on by the way.
Click to expand...
Click to collapse
I'd leave it unlocked. Boot into recovery, use adb push to copy a rom and flash away.
I'd leave it unlocked. You don't need to use adb push. Just mount usb in recovery and copy ROM across. Then flash the ROM.
Sent from my Evita
fleabeard said:
I'd leave it unlocked. Boot into recovery, use adb push to copy a rom and flash away.
Click to expand...
Click to collapse
Ok, so do you know the script to push from adb? and what dp you think would be the best rom to flash in this case for ease.
Thenerdy0ne said:
Ok, so do you know the script to push from adb? and what dp you think would be the best rom to flash in this case for ease.
Click to expand...
Click to collapse
If you're already S-OFF, easiest would be to RUU and never root your phone again.
exad said:
If you're already S-OFF, easiest would be to RUU and never root your phone again.
Click to expand...
Click to collapse
The thing is I have S-on currently.
Thenerdy0ne said:
The thing is I have S-on currently.
Click to expand...
Click to collapse
What Hboot version?
It should say in bootloader.
exad said:
What Hboot version?
It should say in bootloader.
Click to expand...
Click to collapse
It's 2.14
Maybe you should just relock the bootloader and run the RUU.
Sent from my Evita
timmaaa said:
Maybe you should just relock the bootloader and run the RUU.
Sent from my Evita
Click to expand...
Click to collapse
That might brick him.
Best to just flash CleanRom or stock.
Yeah I guess there have been a couple cases.
Sent from my Evita
sdeUple Ganga
exad said:
That might brick him.
Best to just flash CleanRom or stock.
Click to expand...
Click to collapse
Ok, so I should flash clean rom. Any recommended way to do that? go through Adb? And how would I push the boot img with ADB
Thenerdy0ne said:
Ok, so I should flash clean rom. Any recommended way to do that? go through Adb? And how would I push the boot img with ADB
Click to expand...
Click to collapse
What is with you and ADB? With no OS, you can't use ADB.
Extract the boot.img from the rom zip file and put it in your fastboot folder
Mount USB through recovery, copy the rom zip file to your SDcard
wipe cache, dalvik, system
flash rom
reboot to your bootloader/fastboot
plug in your phone
fastboot flash boot boot.img
fastboot reboot
Should boot and work fine.
exad said:
What is with you and ADB? With no OS, you can't use ADB.
Extract the boot.img from the rom zip file and put it in your fastboot folder
Mount USB through recovery, copy the rom zip file to your SDcard
wipe cache, dalvik, system
flash rom
reboot to your bootloader/fastboot
plug in your phone
fastboot flash boot boot.img
fastboot reboot
Should boot and work fine.
Click to expand...
Click to collapse
Ok, I flashed the rom, and now I can't touch the screen and have it respond. It's strange because the touch screen will work in Recovery.
Which ROM did you end up flashing?
Sent from my Evita
timmaaa said:
Which ROM did you end up flashing?
Sent from my Evita
Click to expand...
Click to collapse
I flashed cyanogenmod 10.1
Is it common to have the touch screen problems after flashing it?
Which version of cm10.1? The other builds aren't compatible with the latest touchscreen firmware. You can either downgrade your ts firmware, or flash the latest cm build.
Sent from my Evita
---------- Post added at 12:26 PM ---------- Previous post was at 12:24 PM ----------
You probably should have stuck to Cleanrom. All of this stuff is super basic and you're still managing to get it wrong.
Sent from my Evita
Hello guys,
I've been looking around for CM11 for my HTC One X+.
Now I've found the original CM11 on their website for HOX+, but there is one little question I got about this.
http://download.cyanogenmod.org/?device=enrc2b
That's the link where I've found it by the way.
There is no boot.img download, how safe is it to just install the ROM? In my opinion it isn't.
So let me know what you guys think.
Sent from my HOX+
NiZii. said:
Hello guys,
I've been looking around for CM11 for my HTC One X+.
Now I've found the original CM11 on their website for HOX+, but there is one little question I got about this.
http://download.cyanogenmod.org/?device=enrc2b
That's the link where I've found it by the way.
There is no boot.img download, how safe is it to just install the ROM? In my opinion it isn't.
So let me know what you guys think.
Sent from my HOX+
Click to expand...
Click to collapse
Its on the official website, and It should work. Make a backup though.
The boot.img download isn't there because the boot.img is probably inside the .zip.
So open the zip and you'll have your boot.img.
Sent from my Nexus 5 using Tapatalk
krishneelg3 said:
Its on the official website, and It should work. Make a backup though.
The boot.img download isn't there because the boot.img is probably inside the .zip.
So open the zip and you'll have your boot.img.
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
Yeah, already found it.
Thanks though.
One small question, if I'm going to put the .zip file on my SD card I can just leave the boot.img in the .zip right?
Sent from my HOX+
NiZii. said:
Yeah, already found it.
Thanks though.
One small question, if I'm going to put the .zip file on my SD card I can just leave the boot.img in the .zip right?
Sent from my HOX+
Click to expand...
Click to collapse
Well is your device s-off or s-on?
Sent from my Nexus 5 using Tapatalk
krishneelg3 said:
Well is your device s-off or s-on?
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
S-On, after hours of searching how to put S-Off I gave that up. Since I can't find it for my HTC One X+.
Sent from my HOX+
NiZii. said:
S-On, after hours of searching how to put S-Off I gave that up. Since I can't find it for my HTC One X+.
Sent from my HOX+
Click to expand...
Click to collapse
Oh okay, you will need to flash the boot.img alone then as flashing the ROM zip won't just work. So boot into bootloader, and flash the new boot.img you had extracted from the .zip
Once yo uhave flashed the .img boot into recovery mode and perform a gull wipe, including cache. Once done simply flash the zip and reboot.
First reboot takes a bit so be patient. I also recommend you getting a band backup in case.
Sent from my Nexus 5 using Tapatalk
krishneelg3 said:
Oh okay, you will need to flash the boot.img alone then as flashing the ROM zip won't just work. So boot into bootloader, and flash the new boot.img you had extracted from the .zip
Once yo uhave flashed the .img boot into recovery mode and perform a gull wipe, including cache. Once done simply flash the zip and reboot.
First reboot takes a bit so be patient. I also recommend you getting a band backup in case.
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
Ye I know it takes a lot of time since I've been flashing a ROM once before, but I can just leave the file in the .zip when flashing it in recovery?
Sent from my HOX+
NiZii. said:
Ye I know it takes a lot of time since I've been flashing a ROM once before, but I can just leave the file in the .zip when flashing it in recovery?
Sent from my HOX+
Click to expand...
Click to collapse
Yeah I suppose you can. Nothing will happen.
Sent from my Nexus 5 using Tapatalk
krishneelg3 said:
Yeah I suppose you can. Nothing will happen.
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
Okay thanks.
Sent from my HOX+
NiZii. said:
Okay thanks.
Sent from my HOX+
Click to expand...
Click to collapse
No worries.
All the best.
Sent from my Nexus 5 using Tapatalk
If you're coming from a Sense ROM you can't just flash the zip without flashing the boot.img. It wouldn't even boot. And sometimes it boots but without mobile signal or WiFi signal.
So just place the zip on your sdcard, take the boot.img out of the zip on your computer.. Then boot into bootloader and connect it to the computer using USB then type
"fastboot flash boot boot.img"
Then "fastboot erase cache"
(you must have fastboot installed and configured on your computer)
Then boot into recovery and flash the zip file and gapps. Oh don't forget a wipe is mandatory if you're coming from sense ROM. But if you're coming from an AOSP ROM it's recommended but you can go without wiping. I flashed cyanogen over paranoid android without wiping data and had no issues at all. But I wiped the system partition.
And you cannot S-OFF an HTC One X+.. If it's S-ON then it stays that way. Only a few amount of people have S-OFF on their HOX+.
Oh and I don't think TWRP recovery is compatible with CM11 on HOX+.. So I recommend you flash philz recovery. Flash it by using the fastboot command "fastboot flash recovery recovery.img"
(recovery.img should be replaced with the name of the recovery you downloaded)
It doesn't take a lot of time. I change ROMs almost every week.
Please press the thanks button if I helped!
Sent from my One X+ using XDA Premium 4 mobile app
backb0ne5p1d0r said:
If you're coming from a Sense ROM you can't just flash the zip without flashing the boot.img. It wouldn't even boot. And sometimes it boots but without mobile signal or WiFi signal.
So just place the zip on your sdcard, take the boot.img out of the zip on your computer.. Then boot into bootloader and connect it to the computer using USB then type
"fastboot flash boot boot.img"
Then "fastboot erase cache"
(you must have fastboot installed and configured on your computer)
Then boot into recovery and flash the zip file and gapps. Oh don't forget a wipe is mandatory if you're coming from sense ROM. But if you're coming from an AOSP ROM it's recommended but you can go without wiping. I flashed cyanogen over paranoid android without wiping data and had no issues at all. But I wiped the system partition.
And you cannot S-OFF an HTC One X+.. If it's S-ON then it stays that way. Only a few amount of people have S-OFF on their HOX+.
Oh and I don't think TWRP recovery is compatible with CM11 on HOX+.. So I recommend you flash philz recovery. Flash it by using the fastboot command "fastboot flash recovery recovery.img"
(recovery.img should be replaced with the name of the recovery you downloaded)
It doesn't take a lot of time. I change ROMs almost every week.
Please press the thanks button if I helped!
Sent from my One X+ using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Hey i have htc one m7_ul and when ever i tried to flash cyanogenmod i ended up with so error like some binary problem do you know the fix for it???
Aisfkhan said:
Hey i have htc one m7_ul and when ever i tried to flash cyanogenmod i ended up with so error like some binary problem do you know the fix for it???
Click to expand...
Click to collapse
Whats the error exactly ? and where did you get the error ?
backb0ne5p1d0r said:
Whats the error exactly ? and where did you get the error ?
Click to expand...
Click to collapse
Its in twrp 2.6.3.3 and about some extracting binary failed error but now solved i flashed the boot.img file from cm11.zip file then flashed from philz recovery and everything goes fine