I see that many custom ROMs require flashing boot.img prior/after flashing he ROM itself. I am about to update my HOX's ROM, but before doing it, I've got some questions:
1. Does flashing boot.img have any consequence to handset operation? Is any data being deleted by doing it?
2. Do the two operations (boot.img flashing and ROM flashing) have to be done in sequence, or not? What is I only flash boot.img, and don't proceed with ROM flashing?
3. How do I do (if possible) boot.img backup?
Excuse my ignorance, I don't do this daily, and love My Precious too much to mess with it...
:silly::angel:
[email protected]|-|oR said:
I see that many custom ROMs require flashing boot.img prior/after flashing he ROM itself. I am about to update my HOX's ROM, but before doing it, I've got some questions:
1. Does flashing boot.img have any consequence to handset operation? Is any data being deleted by doing it?
2. Do the two operations (boot.img flashing and ROM flashing) have to be done in sequence, or not? What is I only flash boot.img, and don't proceed with ROM flashing?
3. How do I do (if possible) boot.img backup?
Excuse my ignorance, I don't do this daily, and love My Precious too much to mess with it...
:silly::angel:
Click to expand...
Click to collapse
Every custom Rom has a boot img
Every kernel has a boot img
Failure to flash boot img will cause your phone not to boot
You have to flash the Rom and boot img
Or kernel & its boot img
.... unless you don't want your phone to boot.
Flashing boot images doesn't effect any data.
---
Just make a note of your OS version prior to flashing any roms.
Also, don't flash anything on a battery less than 50% to stay safe.
Sent from my HTC One X using Tapatalk 2
This was fast!
Thanks, mate.
My phone is already rooted and has a custom ROM in it (RENOVATE 3). Since I joined XDA I saw there are many updates to thiss ROM available (I downloaded 5.3.0 the other day).
I was wondering what damage I can make if I do one of the two steps (flash boot.img, but not ROM). But as far as I can see from your explanation - it wouldn't be smart, right?
I guess I'll take some time during the weekend and just do it. :fingers-crossed:
Thanks again!
Cheers!
[email protected]|-|oR said:
I see that many custom ROMs require flashing boot.img prior/after flashing he ROM itself. I am about to update my HOX's ROM, but before doing it, I've got some questions:
1. Does flashing boot.img have any consequence to handset operation? Is any data being deleted by doing it?
2. Do the two operations (boot.img flashing and ROM flashing) have to be done in sequence, or not? What is I only flash boot.img, and don't proceed with ROM flashing?
3. How do I do (if possible) boot.img backup?
Excuse my ignorance, I don't do this daily, and love My Precious too much to mess with it...
:silly::angel:
Click to expand...
Click to collapse
1 boot partition is a separate partition flashable by fastboot only as long as we have s-on. Data partition is not affected.
2 every rom has its own specific boot.img. Flashing the rom and not the boot.img will result in bootloops. Order is not important since they are flashed to different partitions. Just remember to full wipe when switching to different ROMs. Also do a Fastboot erase cache After flashing the boot.img
3 when you do a nandroid backup from recovery, everything including currently running boot.img gets backed up to your sdcard.
Sent from my HTC One X using xda premium
Thank you too, eyosen. :good:
I guess I'll have to bite the bullet and go for it. I hate doing all the home screen and other settings, but I hope it's worth it!
Do you - by any chance - know why mwilky included this new boot.img since version 5 of his ROM? It was not mandatory until this version...
He must have done some changes to the kernel or ramdisk. I use cm10, so have no clue whatsoever about the changes involved. But if his instructions are to flash the new boot.img, you better do it. Just a nandroid backup of your current system before you start.
Sent from my HTC One X using xda premium
ive swapped between many custom/stock kernels without erasing any data (except the cache)
Related
Im using a custom rom and considering to change to a new one. Do I have to do anything special or just flash it like I did for the first time?
You should first back up your current one (search for nandroid back up) and then full wipe/factory reset before flashing your new ROM.
Not doing a full wipe before flashing a new ROM can (most of the times) cause LOTS of trouble. remember to flash the boot.img included in the ROM .zip file if you have S-ON (mostly you do) using cmd (fastboot flash boot boot.img) and then you can flash the ROM normally from recovery
If ROM doesn't work or you didn't like it you can always restore your previous ROM (which you backed up) from recovery but you have to flash that ROM's boot.img so it can boot
I hope I helped.. and sorry if my English is bad..
Please, i know this is nooby and you guys hate these questions, but i have searched, and maybe i typed the wrong thing but i couldn't find anything. Basically i just want to know how to flash another custom rom and kernel on my device. i tried yesterday with a kernel and just got the infinite reset loop again, somehow i fixed it by gettinginto fastboot and reflashing the old kernel but i dont want that happening again. with the roms i heard you can just download the zip to the sd storage and install it via CWM but again, i dont want to take any risks, i did pay $600 for this phone after all. thanks in advance, and sorry for the n00bish questions, i just want to be on the safe side.
also while im here so i dont have to make another topic, i have ARHD 9 installed atm, and it was fine when i first installed it but now the softkeys are always lit up, i cant find an option to turn it off in the Suite tools that came installed with it either.
all custom kernels comes with modules. They are in the zip file.
First you need to flash the kernel through fastboot.
fastboot erase cache
fastboot flash boot boot.img
then go to recovery and flash the zip modules.
Reboot your phone and it should boot up fine.
Don't worry you are not going to brick your phone. Before flashing anything always charge your phone to full.
Flashing rom is simple again. copy the zip in sd card.
copy the boot.img of the rom and put it in fastboot folder.
reboot to bootloader.
again fastboot erase cahce
fastboot flash boot boot.img
reboot to recovery.
wipe data/cache, cache and davik.
install the zip through recovery
Reboot and done
while installing custom kernels you need to flash kernel modules through recovery always.
and read the thread properly what kernels supports what roms.
some roms need repacking, that would be too much to learn at once..
jst do the process step by step and you will be fine.
thanks for the help man, much appreciated
try viperx...it has all the steps there as well
faiz02 said:
while installing custom kernels you need to flash kernel modules through recovery always.
and read the thread properly what kernels supports what roms.
some roms need repacking, that would be too much to learn at once..
jst do the process step by step and you will be fine.
Click to expand...
Click to collapse
If it is mentioned in the thread of the specific rom that repacking a kernel is requried before flashing please tell me if I have got the whole order of things to do wrong, I would really appreciate it.
The specific rom has recommended kernels for trouble free running.
I definitely feel that I have confused myself along the way.
- repack kernel with "Automated Kernel Repack Beta" and download boot-repacked.img to computer
- copy boot-repacked.img to fastboot folder
- fastboot flash boot boot-repacked.img
- fastboot erase cache
- reboot into recovery
- wipe factory data > wipe cache partition > wipe Dalvik cache
- flash kernel.zip for the modules?
- flash rom.zip?
- flash additional gapps.zip (rom specific)
- reboot?
Does this look right to you?
Sorry if this is a troublesome question.
Thank you!
Looks good to me. One thing. Boot your new rom once first before installing Gapps.
Sent from my HTC One X using Tapatalk 2
eyosen said:
Looks good to me. One thing. Boot your new rom once first before installing Gapps.
Sent from my HTC One X using Tapatalk 2
Click to expand...
Click to collapse
Thank you! I will give it go and will thank you again if all of it works out. Is it possible for the old Gapps to conflict with the new ones I will be flashing. Or will the Factory wipe sort that out.
Also another hypothetical case;
Say the Rom Dev have repacked the recommended kernels, can a problem arise by repacking a kernel with the Rom.zip again? Will the subsequent boot-repacked.img have an issue? And if the modules of the kernel are flashed over modules that the Rom.zip might have, will the modules be overwritten without problems?
Thank you and apologies for the convoluted question!
sidsat20 said:
Thank you! I will give it go and will thank you again if all of it works out. Is it possible for the old Gapps to conflict with the new ones I will be flashing. Or will the Factory wipe sort that out.
Also another hypothetical case;
Say the Rom Dev have repacked the recommended kernels, can a problem arise by repacking a kernel with the Rom.zip again? Will the subsequent boot-repacked.img have an issue? And if the modules of the kernel are flashed over modules that the Rom.zip might have, will the modules be overwritten without problems?
Thank you and apologies for the convoluted question!
Click to expand...
Click to collapse
Gapps, there wont be conflicts.
If you already find them repacked by rom dev, it means that they were tested.so are safer to use. So use them.
As for modules, usually yes. Unless they are on different bases such as 2.6.39 and 3.x.x.x. just do a nandroid backup first, and then try. Enough hypothetical.
I am currently running Leedroid and I sometimes switch to Paranoid Android just to see how things are developing there. Great rom but I cant do without sense camera and like the decent weather app with all its animations.
Back to reason, sorry, I cant change my kernel on neither rom. Just gets stuck on boot animation/loop. Knew problem because I used to be able to change kernels but now just cant. Any idea's to why. Much appreciated - I feel handicapped...
Well, did you repack the kernels AND flash modules?
tomascus said:
Well, did you repack the kernels AND flash modules?
Click to expand...
Click to collapse
Cheers for quick response. :good:Yes, as I said I used to be able to try different kernels but just stopped last dozen attempts. Have tried repacking boot image several times, via online repacker but had no joy. Am i doing something wrong.
veroby said:
Cheers for quick response. :good:Yes, as I said I used to be able to try different kernels but just stopped last dozen attempts. Have tried repacking boot image several times, via online repacker but had no joy. Am i doing something wrong.
Click to expand...
Click to collapse
You put the original boot.img in the source img, correct?
Then repacked, flashed the kernel, erased cache and then rebooted to recovery to flash modules?
tomascus said:
You put the original boot.img in the source img, correct?
Then repacked, flashed the kernel, erased cache and then rebooted to recovery to flash modules?
Click to expand...
Click to collapse
Correct. I have tried erasing cache via command line and I have tried erasing cache via cwm as well. Still no joy
Actually because of desperation I have tried everything in different orders as well. Example- flashing boot image before after flashing kernel. Still doesnt boot and eventually after long wait just loops. This problem is with both roms.
Stock kernel works right?
tomascus said:
Stock kernel works right?
Click to expand...
Click to collapse
Yeap, have had to restore to backups everytime. And they function fine but even tho I am a believer in "if it aint broke don't fix it", I cant help but try and fix wat aint broke. If you know what i mean.....
veroby said:
Yeap, have had to restore to backups everytime. And they function fine but even tho I am a believer in "if it aint broke don't fix it", I cant help but try and fix wat aint broke. If you know what i mean.....
Click to expand...
Click to collapse
Maybe a dumb answer, but i had the same problem. Do you flash in the right order? Do you flash your kernel before or after your rom flash? And you're flashing using fastboot?
KaiseRRUby said:
Maybe a dumb answer, but i had the same problem. Do you flash in the right order? Do you flash your kernel before or after your rom flash? And you're flashing using fastboot?
Click to expand...
Click to collapse
No not dumb, i really appreciate attempt in help. As to right order, have tried right order, fastboot flash boot boot.img with repack and original image to kernel but nothing is working. Just will not allow change kernel. Have tried re-flashing boot image after flash kernel as well. Have tried erasing cache partition with wiping dalvik cache together but no go. Have tried erasing nothing but still boot loop. Any ideas:crying:
veroby said:
No not dumb, i really appreciate attempt in help. As to right order, have tried right order, fastboot flash boot boot.img with repack and original image to kernel but nothing is working. Just will not allow change kernel. Have tried re-flashing boot image after flash kernel as well. Have tried erasing cache partition with wiping dalvik cache together but no go. Have tried erasing nothing but still boot loop. Any ideas:crying:
Click to expand...
Click to collapse
So this is your order:
- Backup
- full wipe
- flash rom
- flash kernel
- flash modules
- restart
?
doesn't matter what order you flash the boot.img, as long as you flash the modules after you flash the ROM.
btw, try another ROM.
ARHD 11.1 jellybean smooth and sense camera full package
tomascus said:
doesn't matter what order you flash the boot.img, as long as you flash the modules after you flash the ROM.
btw, try another ROM.
Click to expand...
Click to collapse
Ok here's what I did, full wipe, Flashed knew copy of Leedroid ( i know you said try another rom but hadnt thought it to be necessary because I was having same problem with Leedroid and Paranoid Android jellybean), kinda custom the rom a little with mods and tweaks. Got a bit ahead of myself because I then fastboot faux kernel boot image and flashed the modules. Gutted BOOt-LooPED...:crying:
Have gone back to my backup Leedroid. At least I know its not the full wipe. Any more ideas welcome.
Forgot to mention I did not repack the boot image until after boot loop. Still did not work.
KaiseRRUby said:
So this is your order:
- Backup
- full wipe
- flash rom
- flash kernel
- flash modules
- restart
?
Click to expand...
Click to collapse
Ok here's what I did, full wipe, Flashed knew copy of Leedroid, kinda custom the rom a little with mods and tweaks. Got a bit ahead of myself because I then fastboot faux kernel boot image and flashed the modules. Gutted BOOt-LooPED...
Have gone back to my backup Leedroid. At least I know its not the full wipe. Any more ideas welcome.
Forgot to mention I did not repack the boot image until after boot loop. Still did not work.
veroby said:
Ok here's what I did, full wipe, Flashed knew copy of Leedroid, kinda custom the rom a little with mods and tweaks. Got a bit ahead of myself because I then fastboot faux kernel boot image and flashed the modules. Gutted BOOt-LooPED...
Have gone back to my backup Leedroid. At least I know its not the full wipe. Any more ideas welcome.
Forgot to mention I did not repack the boot image until after boot loop. Still did not work.
Click to expand...
Click to collapse
Well, the best way to do it as far as i know is:
-boot.img flash (the one included in rom)
-wipe
-flash rom
-reboot
-wait for 10 minutes
-rebooten (full reboot again)
-reboot to fastboot
-boot.img flashen (custom kernel)
-modules flashen (custom kernel)
That 's how things work by me, you can try this?
KaiseRRUby said:
Well, the best way to do it as far as i know is:
-boot.img flash (the one included in rom)
-wipe
-flash rom
-reboot
-wait for 10 minutes
-rebooten (full reboot again)
-reboot to fastboot
-boot.img flashen (custom kernel)
-modules flashen (custom kernel)
That 's how things work by me, you can try this?
Click to expand...
Click to collapse
Yeah understand, I used to be able to just fastboot flash kernel boot image, flash kernel modules via cwm and bobs ya uncle. Done. But no more. Guess I'll have to wait until i jump ship and update firmware to 1.28 for JB roms and re-format or something. Cheers anyways..
Extract Rom and grab the boot.img
Make a Full Wipe (Factory Reset,System,Cache,and Davlik Cache)
Install ROM
Fastboot flash boot boot.img
REBOOT
Enjoy!!!
With these instructions *i've never flashed a rom before* I should download the rom, extract the boot.img where I have the fastboot.exe on my computer, do full wipe, put the zip file on my sd card and install in recovery, reboot and go into fastboot mode and flash the image, and then reboot again right? Or am I missing something? Sorry, as I said i've never done this before.
Yeah that's right but flash the kernel (boot.img) first ...because you may get stuck in a bootloop ...so flash kernel first
Ya too bad each step has very specific things you need to do and it takes quite a bit of time sifting through these forums to understand just wtf is going on.
This might help flashing if you've rooted already:
http://www.youtube.com/watch?v=qNR84FST1KQ&feature=plcp
donhashem.dh said:
Yeah that's right but flash the kernel (boot.img) first ...because you may get stuck in a bootloop ...so flash kernel first
Click to expand...
Click to collapse
atonz said:
Ya too bad each step has very specific things you need to do and it takes quite a bit of time sifting through these forums to understand just wtf is going on.
This might help flashing if you've rooted already:
http://www.youtube.com/watch?v=qNR84FST1KQ&feature=plcp
Click to expand...
Click to collapse
Thanks for your help. I actually went ahead and tried mine first, to see because i'm impatient and it worked totally. Thanks everyone!!!
Ok, I'm having issues with this installing ROMs/kernels.
I entered fastboot
I flashed the boot.img for the kernel I want
I toggled to hboot
I went into recovery (twrp 2.2.0)
I did wipe -> Factory Reset, Cache, Dalvik Cache, System
I installed the zip for ROM I want to use [found here]
I flashed the zip for the kernel I want to use (to install the libs) [found here]
wiped dalvik/cache again
reboot system
Now my phone just bootloops. Not sure what I did wrong.
I should mention I did get it to boot once back when I first installed the ROM because I did a normal reboot not a reboot into fastboot (was doing the install the ROM then the boot.img approach at the time) and hadn't installed any boot.img (still had the stock) but ever since I overwrote it all i get is bootloops.
Also, I even tried the same steps using the boot.img included with the ROM as opposed to the other one.
To make things worse, backups are almost useless because with the phone being S-ON even if the boot.img is being backed up, it not getting restored. A point made extremely obvious by the fact that it still bootloops after restoring my backup.
I am currently running the RUU but am hesitant to try and install any ROMs without some idea of what I did wrong.
Any help is appreciated.
-----EDIT------
Ok, I think the problem was the recovery I used. I installed the CDMA TWRP from the OneV tool, and one linked in the cdma development thread and a couple CWM version found there as well. But what seemed to work was getting TWRP straight from the source. After running the RUU I installed version 2.3.1.0 and repeated the steps using the boot.img included in the ROM and it worked. If I'm feeling adventurous later I'll try my luck with the other kernel lol.
Hey guys,
I'm new to the Xperia Arc development and need some help with installing a custom rom. I've done quite a bit of reading but still can't figure out what is wrong and why it's simply not working.
So from what I gathered the steps to ensure a successful flash are:
Firstly flash a stock rom via flashtool ie LT18i_4.1.B.0.587.ftf
flash LT18i_4.1.A.0.562_Kernel > root the device > flash back to LT15a_4.1.B.0.587_Kernel
Then now that the device is rooted, I need to install a recovery such as CWM via RecoverX
So, so far so good as I can access CWM, stock rom works fine as well
So then next step is to unlock the bootloader
pretty sure this worked, as when i tried to unlock it again, it said it failed as it was already unlocked
Now flash a custom kernel, in this case i flashed the 146 FXP CM kernel
This also seemed successful as I was presented with a custom splash screen
So then after custom kernel is installed I enter recovery, wipe the cache and reset factory settings, format the data system and cache as well as wiping the dalvik and battery stats.
After, I installed the custom rom zip file, in this case it was aokp_anzu-ota-eng.kxp_build5 and then google apps and then reboot.
So my problems begin here.
My phone seems to be stuck in the boot process (sometimes), on the "initiating swagger" splash screen and it goes crazy. I've tried flashing this rom with other kernels (fusion 3.9) and sometimes it actually loads up into the rom. But the rom is extremely laggy, applications freeze and close and the wifi never works
So my question is, is there any steps or procedures that I am missing, not doing right or in the correct order?
I don't think it's any hardware issues as wifi works in the stock rom, and it's fairly smooth and fluid.
Also, is there a better way to flash roms so that I don't need to do this entire process of flashing a stock rom, rooting, unlocking bootloader, installing recovery every time I want to flash a new rom? And when I flash a custom kernel first, then flash a custom rom that has a kernel inbuilt (cm10) does the custom rom's kernel replace the one i just flashed, reason for asking is that the instructions say to flash the custom kernels and then the roms, but yeh just hasn't been working for me so not really sure how to do what.
I'd really appreciated any help or insight!
Thanks
http://forum.xda-developers.com/showthread.php?p=18445331#post18445331
XperienceD said:
http://forum.xda-developers.com/showthread.php?p=18445331#post18445331
Click to expand...
Click to collapse
Thanks! I've read your guide (what I based my flashing on) and it seems consistent with what I have done, on the surface of it anyway. If you think I missed or overlooked something, would it be possible to point it out?
If your boot loader is unlocked it's as simple as this...
1. Flash kernel
2. Wipe cache etc
3. Install ROM
...I always reboot before installing anything else as I've found it can break the installation of the ROM.
XperienceD said:
If your boot loader is unlocked it's as simple as this...
1. Flash kernel
2. Wipe cache etc
3. Install ROM
...I always reboot before installing anything else as I've found it can break the installation of the ROM.
Click to expand...
Click to collapse
As ExpirienceD says,just one more thing flash kernel modules if you need to.
So:
1.Flash kernel
2.Full wipe data/cach...etc...
3.Flash ROM
4.Flash kernel modules
Sent from my LT15i using xda premium