Hello, my device is currently running LeeDroid's ROM and I was looking to test out other ROMs for fun. One example is TrickDroid. I noticed that each thread provides a boot.img to be flashed in fastboot. Must I do that before flashing each ROM and after backing up and wiping? Thank you!
If both ROMs are on the same base then no, you shouldnt have to flash each time..
Newer bases require newer boot.imgs,
The worst thing that could happen is the ROM wont boot, To fix that, Just flash the boot.img
I would love to thank you but I reached my max Thanks for today. I will come back tomorrow
If you get a bootlop, you should erase the cache or just flash the boot.img as said above
Related
Hello everyone!
I recently tried to test AOKP and MIUI roms, so i installed them and flashed the boot.img. After I did so, I wanted to go back with a nandroid backup, but the ROM didn't started. Since i read in the MUIU thread that you have to flash the boot.img to start this rom correctly, I flashed the boot.img of the Noble ROM (which I'm using currently), but it didn't help. Even reflashing Noble ROM did not work. So now i have to use AOKP to run the phone, but I want back to Noble Sense 4.
Is there someone who can help me with this?
Thank you in advance
Holger
Sorry for my bad English but I'm no native speaker
Fullwipe, then flash your ROM
Thank you for your advice,
but this didn't work. The ROM gets stuck at the boot animation.
Logcat outputs always the same sequence...
I don't know what to do.
Is there any other method?
But you wiped in recovery right? (data,system,cache)
Data, System, Chache, Dalvik cache, even battery stats.
AOKP starts properly...
Download my Sense 4.0 ROM and flash the boot.img that's inside then boot into recovery do a full wipe then flash my ROM.
Yeah what he said ^^^
you have to use the boot.img for which ever ROM you want to flash.. E.G - You cant flash boot.img from a ROM based on 1.70/8 RUU if the ROM you want is based on a 1.53 RUU..... or vice versa, you catch my drift.
Did this already as mentioned in the first post ... Didn't work. Cannot start Noble ROM, but AOKP
You got bootloader unlocked ?
perhaps you should ask in the AOKP ROM thread...
or the long way is to run RUU and start from the start
azzledazzle said:
Yeah what he said ^^^
you have to use the boot.img for which ever ROM you want to flash.. E.G - You cant flash boot.img from a ROM based on 1.70/8 RUU if the ROM you want is based on a 1.53 RUU..... or vice versa, you catch my drift.
Click to expand...
Click to collapse
I catch your drift homie.
Ha! It worked after the third try Finally, my nandroid backup boots correctly ^^ thank you for all the help
I have a quick question. I wanted to install a certain ROM and was required to use their Boot File. I installed it and I then installed the ROM. All is great, however I was wanting to return to Stock and flashed the Stock Boot.img. My question is, what if I want to now stay with the custom ROM. Whats the harm? On top of that, how can I verify that the Boot was flashed?
Thank you
Boot.img contains the kernel and some other stuff to help the phone boot.
The worse that could happen is the phone wont boot. To fix this just flash the correct boot.img
If you want to stay on a custom ROM, Just reflash the boot.img and then the ROM. you can swap back and forth from stock to custom as many times as you want. Just make sure you have the right boot.img(s) in case it fails to boot.
Great. I askked because I flashed a custom boot.IMG and then a custom rom. Then went back to stock Rom without flashing a new boot and it worked fine. Is therw a way to see what boot.IMG is currently flashed.
Sent from my HTC VLE_U using xda premium
I intend to flash a custom ROM on my One S. I've noticed all roms require flashing boot.img
I did some searching on what boot.img is and found that it has the kernel and booting instructions.. Now, if I flash a new boot.img and some time in the future wanted to restore the stock rom, how do I restore the original one?
I have my nandroid and apps backup. Is that sufficient?
Pheroh said:
I intend to flash a custom ROM on my One S. I've noticed all roms require flashing boot.img
I did some searching on what boot.img is and found that it has the kernel and booting instructions.. Now, if I flash a new boot.img and some time in the future wanted to restore the stock rom, how do I restore the original one?
I have my nandroid and apps backup. Is that sufficient?
Click to expand...
Click to collapse
Restoring the Nandroid will restore the boot image, it is backed up during the Nandroid
If you use TWRP as your recovery, you won't need to flash boot image separate. TWRP bypasses the HTC restriction, allowing the boot image to be flashed with the rom.
If you want a copy of the stock boot.img, I know LeeDroid's Supreme ROM has it linked in the thread there. If you dig that thread out, you can download it and keep a copy of it.
Or run ruu if u want to go back to stock completely
Sent from my HTC One S using xda premium
Thanks all..
I should start my journey then
Good Luck and enjoy
Do as it seems you have done--read OP pages and beginning and ending pages of threads and include System wipes when wiping before flashing--
An update..
As I begun testing various roms.. I found out that neither TWRP nor CWM could manage to flash the boot.img from a nandroid.. I had to flash it via fastboot EVERY time.. TWRP took around 5 min just to flash the boot image and although it reported success, it didn't work! I got stuck at boot animation after flashing my stock nandroid until I flashed a stock boot.img..
No big deal, but just a note for those adventurers..
Flashing With RUU
I'm really new to Android. I've rooted my phone and installed something called TWRP. So will installing a RUU restore the original Boot Image and the Bootloader ? Please repli. Soon Thanks in advance.
AW: [Q] Restoring stock boot.img
The RUU will install stock recovery, stock boot.img and stock rom to your phone. You will lose root, custom recovery and your custom rom.
You have to relock your bootloader for running a RUU.
Sent from my HTC One S using xda app-developers app
Hey Guys,
I´m new to HOS custom mods and so I have a question.
Yesterday I successfully installed Trickdroid 9.1 which is JB and would like to try Vipermod which is ICS.
I would do it like this: Go to recovery, clear cache,dalvik,system and simply install the rom.
To switch back to Trickdroid, I have to flash the stock 9.0 Trickdroid rom and then restore my backup.
Is this procedure right?
Thanks alot for all your work, I really like this site!
Sounds about right... Except I dont think you need to flash trickdroid before restoring your backup.
Ive been switching between viper and Dark Jelly a few times by only restoring the backups (+fastboot flash the boot.img's)
Thanks!
I´ll give it a try this afternoon
gerryfresh said:
Thanks!
I´ll give it a try this afternoon
Click to expand...
Click to collapse
Just make sure to fastboot the boot.img from the Viper ROM (ie extract the boot.img from the Viper ROM and then fastboot flash boot boot.img)
The kernels for JB and ICS are not the same. you would need to flash the rom and fastboot the boot.img unless you are on a low hboot (ie ver 1.06, 1.09)
Viper provides a flash-script in their thread, so all you need to do (for viper) is extract it and doubleclick flash-boot-windows.bat
Hint: That also works with other boot.img's. Simply replace the boot.img with any other boot.img
Thanks for the replies! Flashing the boot.img with commandline is no problem!
Both work great, but I think I´ll stay with Trickdroid until ViperOneS 2 is released
Anyway thanks for the infos!
I am about to flash my nexus 5 device.
I was wondering.. if i unlock the bootloader and install a custom recovery plus create a backup.. that means ill have basicly a backup on my phone of a factory ROM and kernel right ?
So If i play around with custom roms and Kernels does that mean if I want to go back to stock kernel or/and ROM I can just recover my backup files from ,for example, CWM ?
And also if anyone here knows... how big difference can a kernel for battery life extension make ?
Then..
If I want to flash both.. Custom ROM and Kernel.. Rom comes first ? And if after that .. lets say I have flashed Cyanogenmod , and I have decided to change ROMs , Do I have to flash factory ROM ? Or I can just factory reset and Flash ir over the Cyanogenmod ?
For example.. for elementalX kernel I read this line... "You should only flash ElementalX over the kernel that came with your ROM!!!" I assume that means I do flash the ROM first... and what if I want to change Kernels later on? I re-flash the factory kernel ? And how do I do that?
For now that would be it
Thanks
Yes, installing a custom recovery (I recommend TWRP) allows you to create a backup of the existing ROM for restoration at a later point in time if you don't like the phone's existing ROM. Restoring TWRP backups have always worked except for me except in a couple of situations where I could not boot the restored ROM without first doing a factory wipe of the data and cache partitions.
I can't comment on custom kernels except to say that everyone uses their phone in different ways and getting the best battery life and performance may require a lot of tweaking. You could just try different kernels to see which one suits your needs.
You can restore the ROM's original kernel by extracting the kernel from the original ROM and flashing it. Alternatively, you could dirty flash the over the existing ROM. For example, if you are running CM12.1 2015-12-30 with a custom kernel and you want to go back to CM12.1 2015-12-30 without the custom kernel, you could just re-flash the entire CM12.1 2015-12-30 ROM again.
audit13 said:
Yes, installing a custom recovery (I recommend TWRP) allows you to create a backup of the existing ROM for restoration at a later point in time if you don't like the phone's existing ROM. Restoring TWRP backups have always worked except for me except in a couple of situations where I could not boot the restored ROM without first doing a factory wipe of the data and cache partitions.
I can't comment on custom kernels except to say that everyone uses their phone in different ways and getting the best battery life and performance may require a lot of tweaking. You could just try different kernels to see which one suits your needs.
You can restore the ROM's original kernel by extracting the kernel from the original ROM and flashing it. Alternatively, you could dirty flash the over the existing ROM. For example, if you are running CM12.1 2015-12-30 with a custom kernel and you want to go back to CM12.1 2015-12-30 without the custom kernel, you could just re-flash the entire CM12.1 2015-12-30 ROM again.
Click to expand...
Click to collapse
Thanks!
What advantages does TWRP has over CWM ? And also does it recover other files as well or just the system ones ?
And I guess its safer to just extract the original ROMs kernel.. Just how do i do that ?
TWRP is well supported and features a simple touch interface. TWRP will recover the system and data files.
Not necessarily safer to flash just the kernel rather than the entire ROM. It also saves time and effort because, if the kernel is not extracted and compiled for flashing in recovery, it could cause the phone to bootloop.
I've never extracted the kernel myself but this may help: https://www.youtube.com/watch?v=rLhprnOF6-U
audit13 said:
TWRP is well supported and features a simple touch interface. TWRP will recover the system and data files.
Not necessarily safer to flash just the kernel rather than the entire ROM. It also saves time and effort because, if the kernel is not extracted and compiled for flashing in recovery, it could cause the phone to bootloop.
I've never extracted the kernel myself but this may help:
Click to expand...
Click to collapse
Thanks!
So.. If, lets say, I flash cyanogenmod. Then Flash custom kernel. In order to change other kernel which is also custom , I should first flash the factory ROM which will have kernel on it ? And then reflash the ROM and then flash the new kernel ?
Im sorry , I also read a lot about this and somewhere on the way got really confused , haha.
Let's assume you flash CM version 1 and then you flash custom kernel "Kernel A". If you want to try another custom kernel named "Kernel B", you could just flash "Kernel B" over "Kernel A". If the developer of "Kernel B" cays it must be flashed over CM's original kernal, you could still flash "Kernel B" over "Kernel A" and hope it works. If it doesn't work, you could dirty flash CM version 1 over the existing ROM, then flash "Kernel B".
audit13 said:
Let's assume you flash CM version 1 and then you flash custom kernel "Kernel A". If you want to try another custom kernel named "Kernel B", you could just flash "Kernel B" over "Kernel A". If the developer of "Kernel B" cays it must be flashed over CM's original kernal, you could still flash "Kernel B" over "Kernel A" and hope it works. If it doesn't work, you could dirty flash CM version 1 over the existing ROM, then flash "Kernel B".
Click to expand...
Click to collapse
Thank you. Made things much clearer. Dirty flash means just flashing over the existing custom ROM and Kernel right?
And also.. What about if i have CM and Kernel B ... But i want to go change to ParanoidAndroid and still keep the Kernel B? This ROM would remove the Kernel and I would have to re flash ir right?
And also if I am just switching around ROMs only.. I can just flash them one over another? Perhaps a factory reset is healthy in between though.
Dirty flash means flashing over the existing ROM without wiping the system in recovery.
Flashing any ROM over an existing ROM will replace the system and kernel. If you want to change ROMs altogether, you'd flash PA and then flash Kernel B.
When changing ROMs, I always recommend a full wipe (i.e. system, data, cache).
audit13 said:
Dirty flash means flashing over the existing ROM without wiping the system in recovery.
Flashing any ROM over an existing ROM will replace the system and kernel. If you want to change ROMs altogether, you'd flash PA and then flash Kernel B.
When changing ROMs, I always recommend a full wipe (i.e. system, data, cache).
Click to expand...
Click to collapse
Alright. And just one last thing that I got a bit confused of..
When I root and install a custom ROM, I am not going to receive OTAs. If I just flash the newest custom ROM does that work as an update? Or the newest ROM can ble flashed over the newest android? If so... How do I exactly get the newest updates manually? I have to flash to factory ROM and then somehow flash the update? By far thats how I understood it.
rihz said:
Alright. And just one last thing that I got a bit confused of..
When I root and install a custom ROM, I am not going to receive OTAs. If I just flash the newest custom ROM does that work as an update? Or the newest ROM can ble flashed over the newest android? If so... How do I exactly get the newest updates manually? I have to flash to factory ROM and then somehow flash the update? By far thats how I understood it.
Click to expand...
Click to collapse
Depends on which rom, but updates to custom roms generally can just be flashed over. Not sure of the MM jump, but from KK to LP, it worked fine so far. Whatever you do read the instructions of the rom and kernel builders. You get lucky sometimes and can dirty flash things that should not be dirty flashed, but if there are issues, there are instructions on the rom or kernel page how to start again.
If you are factory modified and want a factory image you need to flash in fastboot. If on a custom rom, well, like I said follow their advice. Make sure to backup with recovery and save on computer before doing anything.
wangdaning said:
Depends on which rom, but updates to custom roms generally can just be flashed over. Not sure of the MM jump, but from KK to LP, it worked fine so far. Whatever you do read the instructions of the rom and kernel builders. You get lucky sometimes and can dirty flash things that should not be dirty flashed, but if there are issues, there are instructions on the rom or kernel page how to start again.
If you are factory modified and want a factory image you need to flash in fastboot. If on a custom rom, well, like I said follow their advice. Make sure to backup with recovery and save on computer before doing anything.
Click to expand...
Click to collapse
Okay, thanks!
And Happy New year to you all!