Hi was wondering if somebody can help me. I am new to htc devices and am learning loads about how a phone operates ect due to no s off but was wondering.
if I was on htc custom jb rom ie insercoin but wanted to flash another stock based rom ie miui australia or any other stock based do I have to flash the boot image as I assume there using the same kernel. Is this correct and can it be done. Im probaly miles off. Also can a boot image be flashed through terminal emulator on phone
Im prepared to read but couldn't find a explanation so a link would also be appreciated
sent from my highgrade HTC one x
You always have to flash the boot.img from the rom you are about to flash ! Even if its the same, just to avoid any problems !
You can't flash a boot.img inside a running OS. This has to be done with the phone in fastboot usb mode and fastboot commands from pc (cmd prompt)
Hope this helps a bit
Edit : this has some info about flashing ....
http://forum.xda-developers.com/showthread.php?t=1843585
Mr_S said:
Hi was wondering if somebody can help me. I am new to htc devices and am learning loads about how a phone operates ect due to no s off but was wondering.
if I was on htc custom jb rom ie insercoin but wanted to flash another stock based rom ie miui australia or any other stock based do I have to flash the boot image as I assume there using the same kernel. Is this correct and can it be done. Im probaly miles off. Also can a boot image be flashed through terminal emulator on phone
Im prepared to read but couldn't find a explanation so a link would also be appreciated
sent from my highgrade HTC one x
Click to expand...
Click to collapse
The boot.img contains both kernel and ramdisk
The kernel might not change that much between releases but the ramdisk certainly does
You would likely find that if you don't flash the boot.img then you will just get boot loops
And to your second point. Due to the security on newer HTC phones. You cannot flash a boot.img anyway other than in fastboot.
With s-off you could but as of this moment there is no way of achieving s-off
With s-off the boot.img would automatically be flashed when you install the rom in recovery
Sent from my HTC One X using xda app-developers app
Thanks. So when you repack a boot image are you using kernel and rom specific ramdisk
sent from my highgrade HTC one x
Yes.
Repacking is merging a new kernel with the ROMs ramdisk
Sent from my HTC One X using xda app-developers app
Thanks all. Im getting this now and your help was appreciated.
Bloody auto correct
sent from my highgrade HTC one x
Related
Hi.. Big noob here. But after having flashed the latest ARHD, i can see that they recommend to flash boot.img.. Is this the stock bootloader? and why is it a good idea to flash it when my phone seems to work fine?
i've rooted my phone the "fastboot way" from OSX, so what would i write i the terminal to flash this boot.img?
still not able to post in the dev forum, so hope im not way of, posting it here
thanks!
it contain tweaks
The boot.IMG has nothing to do with the bootloader ,it is the kernel and the ramdidsk which developers change to add tweaks and features. This boot image would normally be flashed automatically as you install the rom in recovery but for now the recovery is incapable of flashing this image so we should do it manually
Sent from my HTC One X using XDA
bagofcrap24 said:
The boot.IMG has nothing to do with the bootloader ,it is the kernel and the ramdidsk which developers change to add tweaks and features. This boot image would normally be flashed automatically as you install the rom in recovery but for now the recovery is incapable of flashing this image so we should do it manually
Sent from my HTC One X using XDA
Click to expand...
Click to collapse
How do u flash stock boot.img when returning the handset back to.full stock ROM? Would a cwm restore fix it or would the same problem occur? If so where could the stock boot.img be found to keep as a backup for if fully stock ROM is wanted again?
Sorry for all the questions.
I'm new to the HTC way, had Samsung before and I knew what I was doing lol.
Drew071
Sent from my HTC One X using XDA
drew071 said:
How do u flash stock boot.img when returning the handset back to.full stock ROM? Would a cwm restore fix it or would the same problem occur? If so where could the stock boot.img be found to keep as a backup for if fully stock ROM is wanted again?
Sorry for all the questions.
I'm new to the HTC way, had Samsung before and I knew what I was doing lol.
Drew071
Sent from my HTC One X using XDA
Click to expand...
Click to collapse
flashing the RUU will replace the boot.img
also your backup you made in clockworkmod will have the boot.img in there. it just wont be able to flash it when restoring. so just pull the boot.img from your /sdcard/cwm to your pc then you will have the stock boot.img which if you do restore can be flashed through fastboot
so your 2x options are
1. download the full RUU file for factory reset
2. copy your CWM backup to PC.
do a restore from CWM then goto fastboot and flash the backed up boot.img
bagofcrap24 said:
flashing the RUU will replace the boot.img
also your backup you made in clockworkmod will have the boot.img in there. it just wont be able to flash it when restoring. so just pull the boot.img from your /sdcard/cwm to your pc then you will have the stock boot.img which if you do restore can be flashed through fastboot
so your 2x options are
1. download the full RUU file for factory reset
2. copy your CWM backup to PC.
do a restore from CWM then goto fastboot and flash the backed up boot.img
Click to expand...
Click to collapse
Makes perfect sense. One other quick question. Like with Samsung handsets Odin can be used to flash stock Roms, is there any such software than can do the same for htc devices?
Thanks again
Drew071
Sent from my HTC One X using XDA
drew071 said:
Makes perfect sense. One other quick question. Like with Samsung handsets Odin can be used to flash stock Roms, is there any such software than can do the same for htc devices?
Thanks again
Drew071
Sent from my HTC One X using XDA
Click to expand...
Click to collapse
The RUU is what HTC uses instead of Odin.
joshnichols189 said:
The RUU is what HTC uses instead of Odin.
Click to expand...
Click to collapse
Thanks. I know it noobish but it seems like a new world compared to flashing Samsung. Even rooting was harder lol. I'll get there soon enough. Just got to learn. Thanks for ya help
Drew071
Sent from my HTC One X using XDA
drew071 said:
Thanks. I know it noobish but it seems like a new world compared to flashing Samsung. Even rooting was harder lol. I'll get there soon enough. Just got to learn. Thanks for ya help
Drew071
Sent from my HTC One X using XDA
Click to expand...
Click to collapse
No worries
ok, so as far as i can tell i should boot to fastboot, and in terminal " ./fastboot flash boot boot.img" or something like this? im a bit confused about the guide in the ARHD thread.
http://forum.xda-developers.com/showpost.php?p=25100933&postcount=3741
What's going on with the normal...cwm method that'android has used for the last few years now that ics is out
Do we need a pc now available to actually.flash a Rom every single.time ?
I don't understand what this fastboot.zip is for prior to flashing any normal zipRom in cwm .
I've never had to do this on my galaxy note
Flashed from gb to ics and back
My one x is unlocked and rooted and I have 3 roms I've tried says install complete
But on reboot I'm back.on stock Rom that's factory reset
This is my second post am I missing a step here ? Can anyone answer and explain why all the one.x roms need to flash some fastboot.zip first and is this done through hboot or cwm or on a pc and is it a one time thing
Sent from my HTC One X using xda app-developers app
Until we get s-off we need to flash the boot.img through fastboot because with s-on its not possible through recovery
Sent from my HTC One X using Tapatalk 2
HTC's "unlock" procedure doesn't give you full s-off, it just allows you to write to certain partitions. And while it does allow you to write to the boot partition from fastboot, it doesn't allow you to write there from recovery. Hence when you flash a ROM/backup in recovery, nothing is written to the boot partition, so you have to write the boot.img there yourself using fastboot (from a PC). We're stuck with this until either HTC cave in and give us full access (unlikely) or someone finds an exploit to gain s-off without them.
Ok now I know so for the first time ever now flashing roms requires being infront of a pc the fastboot boot script can only be done on a pc, no script can be done on the go or right from the device...hboot menu,odd Kind of stupid
I've flashed roms with s on
On other HTC devices that gained root and unlock with s on only , but still allowed fully flashing gb roms
Sent from my HTC One X using xda app-developers app
Why can't the boot.IMG be loaded just like you would any other IMG when you boot into hboot it would recognize the new boot IMG ,then from there finish the install in recovery
Why is adb only way to do the fastboot script
People want to flash roms on the go
Reminds me of backtracking the HTC hd2 days
Sent from my HTC One X using xda app-developers app
Isn't this a bug that the guy from modaco was talking to HTC about?
There's also a random guy that posted a google+ conversation in the general section that was saying the next update will make flashing ROMs easier.
Maybe my 2+2 = 5, but this would be nice, it'll just about half the traffic in the ROM threads.
Hey guys...long time subscriber,not your usual poster. Been using mikes ARHD roms since I had my DHD. My One X has a CID not yet available to flash a JB Rom.
I'm still on ARHD 9.7.2 but I have a problem. The phone reboots on a daily basis. Today being the worst...4 times. Happens anytime, could be locked or even trying to dial a call. No idea why,otherwise running perfect. My hBoot is 0.95 - anything to do with it??
Sent from my HTC One X using xda app-developers app
Anybody at all?
Sent from my HTC One X using xda app-developers app
Have you tried flashing the boot.img that comes with the ARHD rom?
You need to download it separately on the first post.
Boot into fastboot mode
Code:
fastboot flash boot boot.img
peedub said:
Have you tried flashing the boot.img that comes with the ARHD rom?
You need to download it separately on the first post.
Boot into fastboot mode
Code:
fastboot flash boot boot.img
Click to expand...
Click to collapse
I was previously running 9.4.1 so i had flashed the boot.img with that but was under the understanding that it was the same boot.img for all 9.x.x ROMs??
Should i just flash it anyway and then flash the ROM again??
I have just updated from hboot 0.95 to 1.36. Now only a hand full of my ROM's boot now. I have tried them all. Only Viper X 2.71, OrDroid 11.2.0 & InsertCoin 15.0.0 boot up. I have read that the boot image needs to be updated to JB, so tied to repack some of my ROM with the TripnDroid Kernel - though, is the boot.img the same as the kernel? If not, I know where I've gone wrong. Does anyone have some real advice on how to remedy the situation or do I have to wait until the Chefs cook up a new boot.img or just d/l later version ROM. No rush really, Viper X has been has been my ROM of choice for 6mths.
There is a modified boot.img that works with the new hboot.
Sent from my EndeavorU using xda app-developers app
But aren't boot,images specific to each ROM?
Random Pinenut Joy said:
But aren't boot,images specific to each ROM?
Click to expand...
Click to collapse
Yes boot img's are specific to reach Rom,they contain the kernel and a ram disk.
If you have been restoring with a nand back up,you restore the boot img of the Rom you backed up,obviously some will work with the new 1.39 some will not,it states in all op pages what the requirements are and what hboot it's required..
Sent from my EndeavorU using xda app-developers app
So repacking the boot.img, as I did at nibble.cc/repack/index.php. Will this work or does the specific boot.img have to be modified to load in the new hboot environment by the original Chefs
Random Pinenut Joy said:
So repacking the boot.img, as I did at nibble.cc/repack/index.php. Will this work or does the specific boot.img have to be modified to load in the new hboot environment by the original Chefs
Click to expand...
Click to collapse
I don't think you need to modify your boot.img or repack it at all.
The tripndroid kernel is only for unsupported hboots, and the new hboot can also run ics or jb ROMs perfectly.
Sent from my faster than SGS3 HOX.
Hi,
Ive done a quick search and cannot find a straight answer, i dont own HTC one x but need to modify a friends phone. as far as im aware they have a custom 4.1 rom and CWM etc.
Do i need to flash boot.img for every rom regardless of what it says on the post? some dont mention it... just want to be sure!
LOGMD said:
Hi,
Ive done a quick search and cannot find a straight answer, i dont own HTC one x but need to modify a friends phone. as far as im aware they have a custom 4.1 rom and CWM etc.
Do i need to flash boot.img for every rom regardless of what it says on the post? some dont mention it... just want to be sure!
Click to expand...
Click to collapse
If the rom uses stock kernel, then no but you may lose ram disk tweaks for that rom.
Sent from my HTC One X using xda app-developers app
Basically, Yes. If you switch over to a different ROM you have to flash the new boot image. Sometimes the boot image is also updated with a new version of a ROM in that case you have to flash the new Boot Image too.
You can install rom without flash boot.img only if you device is S-Off.
If your are S-On, you have to flash boot.img everytime you install a new rom.
I have a Desire S-Off and i can flash which rom i want without flash boot.img.
For my Sensation XE, it's the same.
For my HOX, i have to flash everytime i change my rom.
totofe69 said:
You can install rom without flash boot.img only if you device is S-Off.
If your are S-On, you have to flash boot.img everytime you install a new rom.
I have a Desire S-Off and i can flash which rom i want without flash boot.img.
For my Sensation XE, it's the same.
For my HOX, i have to flash everytime i change my rom.
Click to expand...
Click to collapse
No. No. No.
Some or most kernels and ROM's for the OneX are NOT set up to flash the boot.img in recovery precisely because there is no method to S-Off the phone. Devs have simply stopped implementing the method. I have no idea which ones can and cannot so err on the side NONE can and you cannot go wrong.
Always flash, in fastboot, the given boot.img for every ROM is the general basic rule.
Tigerlight said:
No. No. No.
Some or most kernels and ROM's for the OneX are NOT set up to flash the boot.img in recovery precisely because there is no method to S-Off the phone. Devs have simply stopped implementing the method. I have no idea which ones can and cannot so err on the side NONE can and you cannot go wrong.
Always flash, in fastboot, the given boot.img for every ROM is the general basic rule.
Click to expand...
Click to collapse
If both roms are using stock kernel and on the same base and you don't mind losing the roms ram disk tweaks you really don't need to flash.
Same if you are using a custom kernel.
So long as the kernel/base match you would just need to flash the modules.
Sent from my HTC One X using xda app-developers app
If you use Android 4.2.2 with sense 5, you only flash boot.img one time and flash any rom except Alex-V's rom. Because still now, all sense 5 rom using stock kernek
If you flash cm, you must flash boot.img every time you flash difference rom
if your device already s-off and super-cid you flash rom normal no need flash boot.img except some rom not allow flash boot.img in update-script
Thanks all!
nightstorm8x said:
If you use Android 4.2.2 with sense 5, you only flash boot.img one time and flash any rom except Alex-V's rom. Because still now, all sense 5 rom using stock kernek
If you flash cm, you must flash boot.img every time you flash difference rom
if your device already s-off and super-cid you flash rom normal no need flash boot.img except some rom not allow flash boot.img in update-script
Click to expand...
Click to collapse
Thanks for all the replies guys, given me a better insight to the method i should take with this phone when i get hold of the phone ill analyse the rom currently on there. i think its 4.1 with sense so ill do more homework and figure it out!:cyclops: