Hi,
I have a Pixel 3xl rooted and running with Havoc Rom.
if I want to switch from a custom rom to another custom rom, how can I do that?
Do I have to install stock rom and erase data before the new custom rom or can I just install the new custom rom above to previous one?
Thank you.
oceliome said:
Hi,
I have a Pixel 3xl rooted and running with Havoc Rom.
if I want to switch from a custom rom to another custom rom, how can I do that?
Do I have to install stock rom and erase data before the new custom rom or can I just install the new custom rom above to previous one?
Thank you.
Click to expand...
Click to collapse
Install stock factory image to both slots with -w intact in the flash-all batch, and then start with the instructions of the ROM you want to install.
sliding_billy said:
Install stock factory image to both slots with -w intact in the flash-all batch, and then start with the instructions of the ROM you want to install.
Click to expand...
Click to collapse
I would personally back up anything I wanted then flash the new rom boot.img and try to dirty flash it. If it got messed up then I would do as above. I am still crazy though and 9/10 you need a wipe when switching.
wangdaning said:
I would personally back up anything I wanted then flash the new rom boot.img and try to dirty flash it. If it got messed up then I would do as above. I am still crazy though and 9/10 you need a wipe when switching.
Click to expand...
Click to collapse
I get it. I hate clean flashing more than anything, but pretty much no custom ROMs allow for dirty installs except for over the same ROM these days. Even over the same doesn't always work well especially if the build was dirty. Not worth the extra effort trying to figure out and fix what broke on a cross-rom dirty flash, IMO.
sliding_billy said:
I get it. I hate clean flashing more than anything, but pretty much no custom ROMs allow for dirty installs except for over the same ROM these days. Even over the same doesn't always work well especially if the build was dirty. Not worth the extra effort trying to figure out and fix what broke on a cross-rom dirty flash, IMO.
Click to expand...
Click to collapse
True, but lots of people have extra time nowadays. I would say just always make sure you back up somehow before any switch. Be ready to wipe your device clean.
Thank you for your replys.
I'm not an english speaking personn, so if i understand:
The normal way to switch two customs roms is to "transit" by the stock rom and clear all data and then install rhe new custom rom.
The other way, would be dirty flash the new custom rom above the previous custom rom (with loss data possible so a bachup is needed).
Related
I've never used an AOSP ROM before, but now I am currently on AOKP. When I want to update to a newer version, do I still need to flash gapps after flashing the update? I assume I have to reflash the kernel as well if I use one different than the one included with the ROM?
You need to flash GApps straight away after if you are wiping your device. You also need to reflash the kernel of choice after. Good luck.
jd1001 said:
You need to flash GApps straight away after if you are wiping your device. You also need to reflash the kernel of choice after. Good luck.
Click to expand...
Click to collapse
Only wiping I would do would be cache and dalvik since I am merely upgrading the ROM version, eg nightly 19 to nightly 20. Would that still involve flashing gapps?
edgeicator said:
Only wiping I would do would be cache and dalvik since I am merely upgrading the ROM version, eg nightly 19 to nightly 20. Would that still involve flashing gapps?
Click to expand...
Click to collapse
Yes
10char.
You shouldn't have to reflash GAPPS if you are just updating..
2 separate answers. Anyone else want to chime in?
You have to ref lash the kernel because flashing a rom flashes the from kernel. I've never had to flash gapps on any device if going from an old build of a rom to a new one unless specifically stated.
Sent from my Galaxy Nexus using xda premium
edgeicator said:
2 separate answers. Anyone else want to chime in?
Click to expand...
Click to collapse
Just think about it. It depends on how you flash and if you flash an update.zip if that zip wipes existing data or just adds to it.
For a sure answer you would need to say what method is used and how the update edify script in the zip looks like.
Now for someone how knows the rom you're talking about in detail and what files are provided there might be a clearer answer, but not every poster does know such details^^
The answer is no, if you just update a rom without wipe, you dont need to flash gapps. This type of rom update keeps all your data in tact anyway so of course no need to flash extra.
I have received a replacement GS3 2 days ago. I rooted the phone no problems and it came with MK3 already on it. But no matter what rom I flash, they all cause a lot of random reboots and lockups. TW and CM based roms ive tried with the same results. I do multiple wipes before installing any rom so I know that cant be the problem. It got so annoying that i just flashed the stock tar in odin even though i hate not being rooted. Can anyone shed some light on this?
cbond007 said:
I have received a replacement GS3 2 days ago. I rooted the phone no problems and it came with MK3 already on it. But no matter what rom I flash, they all cause a lot of random reboots and lockups. TW and CM based roms ive tried with the same results. I do multiple wipes before installing any rom so I know that cant be the problem. It got so annoying that i just flashed the stock tar in odin even though i hate not being rooted. Can anyone shed some light on this?
Click to expand...
Click to collapse
Are you flashing 4.3 TW ROMs? Do you format system before flashing the ROMs (if they do not say that they do it for you)?
Yes, I'm flashing 4.3 roms. I do wipe the system, I don't know if that is the same as formatting the system though(?)
kennyglass123 said:
Are you flashing 4.3 TW ROMs? Do you format system before flashing the ROMs (if they do not say that they do it for you)?
Click to expand...
Click to collapse
cbond007 said:
Yes, I'm flashing 4.3 roms. I do wipe the system, I don't know if that is the same as formatting the system though(?)
Click to expand...
Click to collapse
In CWM the option is format /system. Is wipe system an option in TWRP? And when you flashed the ROMs and the FCs show up, have you tried a factory data reset to clear all data?
Yes, in TWRP in the wipe options, (wipe system) is an option. I haven't gotten any FC's on the 4.3 roms i were flashing. Moar's rom is the main one i used after i got the replacement. Wicked's rom in recovery when I tried to flash would always say unable to mount \system. I can flash CM 11 nightlies fine, but they just have too many random reboots for my liking. I havent tried to factory reset after flashing a rom yet though.
kennyglass123 said:
In CWM the option is format /system. Is wipe system an option in TWRP? And when you flashed the ROMs and the FCs show up, have you tried a factory data reset to clear all data?
Click to expand...
Click to collapse
cbond007 said:
Yes, in TWRP in the wipe options, (wipe system) is an option. I haven't gotten any FC's on the 4.3 roms i were flashing. Moar's rom is the main one i used after i got the replacement. Wicked's rom in recovery when I tried to flash would always say unable to mount \system. I can flash CM 11 nightlies fine, but they just have too many random reboots for my liking. I havent tried to factory reset after flashing a rom yet though.
Click to expand...
Click to collapse
The thing is with Knox in the bootloader you are stuck with and the warranty bit in the secondary bootloader you need to stick with 4.3 and above ROMs as they include compatible kernels. Your options are more limited now than they were. If the Wicked ROM is 4.3 you might try flashing with CWM.
Cool. I will try it with CWM. This sucks because my replacement phone came with Knox already on it. I just wish CM 11 roms werent so buggy on my phone so I could stick with that. Thanks for all your help.
kennyglass123 said:
The thing is with Knox in the bootloader you are stuck with and the warranty bit in the secondary bootloader you need to stick with 4.3 and above ROMs as they include compatible kernels. Your options are more limited now than they were. If the Wicked ROM is 4.3 you might try flashing with CWM.
Click to expand...
Click to collapse
cbond007 said:
Cool. I will try it with CWM. This sucks because my replacement phone came with Knox already on it. I just wish CM 11 roms werent so buggy on my phone so I could stick with that. Thanks for all your help.
Click to expand...
Click to collapse
I would also suggest trying Philz Touch recovery instead of CWM or TWRP.
http://forum.xda-developers.com/showthread.php?t=2446393
---------- Post added at 10:36 AM ---------- Previous post was at 10:25 AM ----------
If you do decide to try Philz (highly recommended!), the option for wiping prior to a ROM install is under Wipe Data/Factory Reset and then choose "Clean to Install New ROM" this will take care of everything you need to start properly. CM11 has run flawlessly for me since its release in early December, but I also am Knox-free. I don't believe that should make a difference though, sounds more like you are not getting a good install, as @kennyglass123 is suggesting. Additionally, some users find that you need to let the ROM "settle in" before doing anything. This means flash just the ROM, and once it boots up don't do anything-no WiFi setup, no fiddling around with apps, nothing for a few minutes. Then, boot back into recovery, flash GApps, boot back into system, and let it sit for a few minutes more. Then, go ahead and setup WiFi connection, Google account, etc.
I've been reading a lot about multiple slots and such and am confused but would like to flash resurrection remix ROM. Currently I am only unlocked. I should flash TWRP using the script, then flash su, then I can have at the ROM but just need to make sure to flash TWRP after the ROM.
Question is do I need to worry about the slots? Or will simple flashing work?
Your best bet is to follow the dev flashing instructions because they're all a bit different depending on which rom you choose. Some ROMs don't include gapps and require switching slots to flash them separately.
Sent from my Pixel XL using Tapatalk
gmac1990 said:
I've been reading a lot about multiple slots and such and am confused but would like to flash resurrection remix ROM. Currently I am only unlocked. I should flash TWRP using the script, then flash su, then I can have at the ROM but just need to make sure to flash TWRP after the ROM.
Question is do I need to worry about the slots? Or will simple flashing work?
Click to expand...
Click to collapse
Not on rr. You can just flash it and not worry, I would make sure your on latest Google firmware first so your vendor image matches up, and it's just a good idea.
I have recently been trying to flash the RR ROM with no luck. I've tried being on 3 different Stock versions and each time it just boots forever when I try booting into RR. I don't know if this is a slot issue or not, but it definitely seems like there are some niche concerns when flashing things to a Pixel, since I never had these frustrations with a Nexus device.
McSnuffles said:
I have recently been trying to flash the RR ROM with no luck. I've tried being on 3 different Stock versions and each time it just boots forever when I try booting into RR. I don't know if this is a slot issue or not, but it definitely seems like there are some niche concerns when flashing things to a Pixel, since I never had these frustrations with a Nexus device.
Click to expand...
Click to collapse
List the steps your using, are you doing a full wipe beforehand
Sorry - slipped my mind.
I've done it a few ways but yes each time I wipe dalvik/cache and do a factory wipe before attempting to flash anything.
And are you using the correct TWRP version?
Sent from my Pixel XL using Tapatalk
Hello my fellow 5t owners.
Now I'm no noob when it comes to Android, but I have a small question to ask everyone, to guage what people do, and how they do it.
I'm assuming we are all rooted so can not take OTA updates.
The question is this:
When a new update comes out, do u dirty flash on top of ur original firmware, or do u do a full wipe and a clean flash?
If ur dirty, like me, then we all know how to do that.
If u clean flash every update, what steps do u take to back up everything on ur device before u wipe? Do u just use TiBu for apps and data or do u take any other additional steps?
I like forward to reading it replies
its usually ok to dirty flash an update providing its based on the same rom source (oos or aosp), i would wipe cache after tho.
I only ever dirty flash from the same OS, I tend to stick to OOS so it's kinda easy and everything stays the same, I just have to go into TiBu, back up newer versions and then debloat everything I usually get rid of, lol.
Sent from my OnePlus5T using XDA Labs
I usually flash AOSP ROMs and clean flash whenever the developer recommends it. I'll also clean flash even if it's safe to dirty flash, but only when I have free time. The way I backup and restore is:
Apps, call logs and sms with TiBackup
Bluetooth and WiFi with Pairs
Create a backup within Nova for my homescreen setup
I go through my ROM settings again manually though
rickysidhu_ said:
I usually flash AOSP ROMs and clean flash whenever the developer recommends it. I'll also clean flash even if it's safe to dirty flash, but only when I have free time. The way I backup and restore is:
Apps, call logs and sms with TiBackup
Bluetooth and WiFi with Pairs
Create a backup within Nova for my homescreen setup
I go through my ROM settings again manually though
Click to expand...
Click to collapse
That's great info thanx.
I used to be a flashaholic when I was running a custom ROM, mainly used OmniROM on my Galaxy S3, but now OOS is actually a really good close to stock ROM so I am happy with it. I like the closest to stock Android I can get, just using Evie Launcher instead of OnePlus Launcher.
Sent from my OnePlus5T using XDA Labs
Adam3Sixty said:
Hello my fellow 5t owners.
Now I'm no noob when it comes to Android, but I have a small question to ask everyone, to guage what people do, and how they do it.
I'm assuming we are all rooted so can not take OTA updates.
The question is this:
When a new update comes out, do u dirty flash on top of ur original firmware, or do u do a full wipe and a clean flash?
If ur dirty, like me, then we all know how to do that.
If u clean flash every update, what steps do u take to back up everything on ur device before u wipe? Do u just use TiBu for apps and data or do u take any other additional steps?
I like forward to reading it replies
Click to expand...
Click to collapse
TiBu is more than enough i think.
Also, im having trouble dirty flashing the new oreo update on my 5t. Idk where im going wrong.
what i did :
flash the full sized update on top of OOS 4.7.6
flash magisk
reboot to recovery
reboot to system
after i do this the device doesnt boot and i can see a static led light on and thats it.
---------- Post added at 12:05 PM ---------- Previous post was at 12:03 PM ----------
Adam3Sixty said:
That's great info thanx.
I used to be a flashaholic when I was running a custom ROM, mainly used OmniROM on my Galaxy S3, but now OOS is actually a really good close to stock ROM so I am happy with it. I like the closest to stock Android I can get, just using Evie Launcher instead of OnePlus Launcher.
Sent from my OnePlus5T using XDA Labs
Click to expand...
Click to collapse
i totally agree. OOS is really good
Try to reflash the rom, do not flash magisk but reboot system. Then you can reinstall TWRP and flash magisk.
pargas said:
Try to reflash the rom, do not flash magisk but reboot system. Then you can reinstall TWRP and flash magisk.
Click to expand...
Click to collapse
Okay I'll try that. Thanks!
worked. thanks!
darkishrex said:
TiBu is more than enough i think.
Also, im having trouble dirty flashing the new oreo update on my 5t. Idk where im going wrong.
what i did :
flash the full sized update on top of OOS 4.7.6
flash magisk
reboot to recovery
reboot to system
Click to expand...
Click to collapse
pargas said:
Try to reflash the rom, do not flash magisk but reboot system. Then you can reinstall TWRP and flash magisk.
Click to expand...
Click to collapse
darkishrex said:
worked. thanks!
Click to expand...
Click to collapse
and now I know exactly what I'll be doing on Sunday morning
Should have a Boeffla Kernel beta to try as well!!
Sent from my OnePlus5T using XDA Labs
So after almost a whole day of blood, sweat and tears, I am FINALLY on OOS 5.0.2!! And what a nightmare it was
I ended up having to totally wipe everything, after trying to restore my back up and getting the "ENCRYPTION FAILED" ur device is now borked message.
STILL haven't got everything sorted, and kicking myself that I didn't flash 5.0.3 seeing as it's out in the wild, but never mind, I am now on Oreo and it's working almost perfectly, with Magisk and Systemless Xposed.
Sent from my OnePlus 5T using XDA Labs
i wonder how to remove custom rom? i already wipe the data , dalvik/cache & internal storage, i dont get any error but when i try to boot the custom rom still there
Ignus01 said:
i wonder how to remove custom rom? i already wipe the data , dalvik/cache & internal storage, i dont get any error but when i try to boot the custom rom still there
Click to expand...
Click to collapse
Oh boy you've got it all wrong.
When a custom rom is installed, it replaces the stock one. So, to get back to stock rom, you need to install it in order to replace the custom one.
DaReDeViL said:
Oh boy you've got it all wrong.
When a custom rom is installed, it replaces the stock one. So, to get back to stock rom, you need to install it in order to replace the custom one.
Click to expand...
Click to collapse
ohh i see i thought the old one is deleting then installing a new one haha sorry
DaReDeViL said:
Oh boy you've got it all wrong.
When a custom rom is installed, it replaces the stock one. So, to get back to stock rom, you need to install it in order to replace the custom one.
Click to expand...
Click to collapse
then i have a question why sometimes it show NO OS INSTALLED? if it is not removed?
Ignus01 said:
then i have a question why sometimes it show NO OS INSTALLED? if it is not removed?
Click to expand...
Click to collapse
It is a possible case. If you wipe the current rom and don't install another one, you'd have nothing to boot into. On my Galaxy it boots to download mode, idk what it does on xiaomi devices
SmartphoneOwner said:
It is a possible case. If you wipe the current rom and don't install another one, you'd have nothing to boot into. On my Galaxy it boots to download mode, idk what it does on xiaomi devices
Click to expand...
Click to collapse
Fast boot in xiaomi