Base ROM Before Flash? - Tilt, TyTN II, MDA Vario III Windows Mobile ROM De

I was wondering if people flash an original base ROM, such as the stock HTC one or the original At&T one, before flashing each custom ROM.
With my Wizard, it was always advised to flash a stock carrier ROM first to ensure the extended ROM was not corrupted and to avoid battery drain issues.
From what I understand, if you flash an OEM ROM, it does not re-flash your SPL like it did with the Wizard, just the radio and OS - which would mean that a newer radio would needed to be re-flashed, as well (if desired).
Just wanted people's thoughts on this. Does anyone do this, or does everyone just flash over the custom ROMs?
Thanks...

zakhir_n said:
I was wondering if people flash an original base ROM, such as the stock HTC one or the original At&T one, before flashing each custom ROM.
With my Wizard, it was always advised to flash a stock carrier ROM first to ensure the extended ROM was not corrupted and to avoid battery drain issues.
From what I understand, if you flash an OEM ROM, it does not re-flash your SPL like it did with the Wizard, just the radio and OS - which would mean that a newer radio would needed to be re-flashed, as well (if desired).
Just wanted people's thoughts on this. Does anyone do this, or does everyone just flash over the custom ROMs?
Thanks...
Click to expand...
Click to collapse
I just flash whatever new version comes along. I have not had any problems at all.

Related

flash back to stock before flashing new rom

Does it really matter to flash back to stock before i install a new rom. I know that it is recommened but is there really any drawback of just flashing over the current rom?
If you just updating the Custom Rom with a newer version of it don't think there huge deal not going to Stock 1st still might need to Wipe Data and Cache. But if you going to totally new Custom Rom I think I would go to Stock 1st.
rg400smarttowel said:
Does it really matter to flash back to stock before i install a new rom. I know that it is recommened but is there really any drawback of just flashing over the current rom?
Click to expand...
Click to collapse
You know, if the ROM author recommends you flash back to stock then you should probably follow that recommendation...
In my experience, it's just better to flash to stock. The ROM creator might say it's fine to flash over a previous ROM, but it seems like most of the problems people have are caused by flashing over an existing custom ROM and are fixed by flashing back to stock then flashing the new ROM.
Just my 2 cents!
pmd5700 said:
In my experience, it's just better to flash to stock. The ROM creator might say it's fine to flash over a previous ROM, but it seems like most of the problems people have are caused by flashing over an existing custom ROM and are fixed by flashing back to stock then flashing the new ROM.
Just my 2 cents!
Click to expand...
Click to collapse
Yup. It seems very hit or miss when just flashing over a rom so I always flash stock first. Look in any rom thread and you'll see countless posts of people flashing over their existing roms and experiencing force closes and other issues. I even flash stock when upgrading an existing rom. This may be overkill, but I've never had issues doing it this way.
I always do, even if it is just an update to the same ROM. The main reason is that if I end up really liking this new ROM or update, I want to make sure that it is as clean an install as I can do, so I don't have to re-do it later just work clean up a mess.

Will Aces Hack Kit approach to rooting remove the stock radio.

At the end of the "effen manual" in ace's hack kit, it shows you how to reflash the stock radio and rom, probably in case you ever need to send the phone back for insurance purposes. My question is...do I need to reflash the stock radio if I intend to use the stock radio with a custom rom or will the stock radio still be in tact after rooting, downgrading the rom, etc...
In other words, does ace's hack kit affect the stock radio?
Yes. As part of the downgrade step, the radio is also replaced by the one in the downgrade package.
Thank you.
I will reflash the stock radio and then flash a custom rom. It doesn't matter which order I perform those two steps in...or does it?
if your going to flash a custom rom, go ahead and wait to flash the radio, until you flash the custom rom, then you can flash the recommended radio for the rom.
Like said above because sometimes the roms will run just as good with one radio as they do with another. I did though when I used the kit.... can't really go wrong with either one you can always change it later.
Sent from my Inspire 4G using XDA App
The first rom I flashed after I rooted with the Hack-Kit was the rooted stock rom with the OTA update in PD98IMG.zip form (http://forum.xda-developers.com/showthread.php?t=1058042). Because it has the OTAed stock radio with the rooted stock rom in it so everything is done in one step (installed from HBoot). After that you can flash any rom of your choice from recovery and you get to keep the OTAed stock radio.

[Q] State of phone when flash with stock ROM

Just a quick question:
When you flash your phone, with for example a DFT custom ROM, and you want to go back with a stock ROM, will your phone then be as new, as in, SPL and Radio etc...?
kirkwesterbroek said:
When you flash your phone, with for example a DFT custom ROM, and you want to go back with a stock ROM, will your phone then be as new, as in, SPL and Radio etc...?
Click to expand...
Click to collapse
yes, as long as you flash the RUU_Signed.nbh of a stock Shipped ROM specific to your device.

[Q] Regarding flashing boot.img between 2 ROMs.

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

Need a few qiuck tips. Regarding rooting and flashing

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!

Categories

Resources