So, I'm not new to custom ROMs and I have been a Nexus user for years, but the new dual partition system has me a bit confused and I'm trying to sort of stick to guides to avoid breaking anything.
In all of the Pixel XL specific guides I've read about flashing custom ROMs it says to first wipe the device with TWRP (except internal storage obviously), but wouldn't wiping system wipe it on the active slot and the ROM is going to flashed on the opposite slot, so do I need to switch slots within TWRP, wipe, switch back to the other slot and then flash the ROM?
admiralspeedy said:
So, I'm not new to custom ROMs and I have been a Nexus user for years, but the new dual partition system has me a bit confused, so I'm trying to sort of stick to guides to avoid breaking anything.
In all of the Pixel XL specific guides I've read about flashing custom ROMs, it says to first wipe the device with TWRP (except internal storage obviously), but wouldn't wiping system wipe it on the active slot, but the ROM is going to flashed on the opposite slot, so do I need to switch slots within TWRP, wipe, switch back to the other slot and then flash the ROM?
Click to expand...
Click to collapse
Yes when you wipe from TWRP it wipes what you are currently on. I never wipe system always just been doing factory reset from TWRP and haven't had a problem yet. Last time I wipe system it went okay I just had a heck of a time getting back to the bootloader. I know for the factory reset it wipes data on both slot so maybe the same thing for system
When you boot to twrp the current slot system is wiped.
So if you are on slaot A and wipe for a clean install you have to reboot to the other non active slot. I always hold down vol - so I get right back to bootloader. Than reboot to twrp. Now install rom and twrp and reboot again while holding vol -. Back to twrp and install vendor. Than install gapps if necessary and reboot to system. Once in system reboot into twrp and install su.
mikaole said:
When you boot to twrp the current slot system is wiped.
So if you are on slaot A and wipe for a clean install you have to reboot to the other non active slot. I always hold down vol - so I get right back to bootloader. Than reboot to twrp. Now install rom and twrp and reboot again while holding vol -. Back to twrp and install vendor. Than install gapps if necessary and reboot to system. Once in system reboot into twrp and install su.
Click to expand...
Click to collapse
So after you wipe the system and do a factory reset you boot to the other slot then reboot to recovery and that doesn't ever put you in a loop. I know for a fact the factory reset wipes​ the data and both slots. I quit doing system wipes because I always keep everything on one slot and every time I tried to reboot to recovery or bootloader it would put me into a loop after a system wipe
Never once in a reboot. That's why I hold vol- before I reboot to another slot. Always right away to bootloader. And from there back to twrp.
I had problems multiple times when I didn't wipe system.
BTW if I want to flash dirty I'll do nearly the same.
In TWRP reboot to the non active slot and than install rom twrp and so on.
I really don't know if that's all necessary but never had a problem doing so.
Same thing with flashing factory. I always flash it to both slots.
mikaole said:
Never once in a reboot. That's why I hold vol- before I reboot to another slot. Always right away to bootloader. And from there back to twrp.
I had problems multiple times when I didn't wipe system.
BTW if I want to flash dirty I'll do nearly the same.
In TWRP reboot to the non active slot and than install rom twrp and so on.
I really don't know if that's all necessary but never had a problem doing so.
Same thing with flashing factory. I always flash it to both slots.
Click to expand...
Click to collapse
I'll give it a shot again I was just curious if there was something that I was doing different. someone else was telling me whenever you install a ROM it wipe system anyway for you so you don't even really have to do it maybe next time I'll try it again
Thanks
mikaole said:
When you boot to twrp the current slot system is wiped.
So if you are on slaot A and wipe for a clean install you have to reboot to the other non active slot. I always hold down vol - so I get right back to bootloader. Than reboot to twrp. Now install rom and twrp and reboot again while holding vol -. Back to twrp and install vendor. Than install gapps if necessary and reboot to system. Once in system reboot into twrp and install su.
Click to expand...
Click to collapse
Could you not just change the active slot in TWRP and wipe? Or just change the active slot in TWRP, then tap "Reboot bootloader" and then go back into the recovery if it needs to be restarted for the slot change to take effect?
mac796 said:
So after you wipe the system and do a factory reset you boot to the other slot then reboot to recovery and that doesn't ever put you in a loop. I know for a fact the factory reset wipes​ the data and both slots. I quit doing system wipes because I always keep everything on one slot and every time I tried to reboot to recovery or bootloader it would put me into a loop after a system wipe
Click to expand...
Click to collapse
How do you know that factory reset does both? It doesn't tell you any info when you do it and I'm not convinced it does both at all.
I never tested that.
Don't have time to do so, but will at weekend.
This would make things way easier. Thx for that hint.
Will try with 2 different roms to see if that works.
admiralspeedy said:
How do you know that factory reset does both? It doesn't tell you any info when you do it and I'm not convinced it does both at all.
Click to expand...
Click to collapse
Because when I was running dual slots if I did a wipe on one slot. If I booted to other I had to re setup. They share same data partition so it makes sense
You can also tell when you do it it takes a few seconds if you switch slots and do factory reset again it's already done
mac796 said:
Because when I was running dual slots if I did a wipe on one slot. If I booted to other I had to re setup. They share same data partition so it makes sense
You can also tell when you do it it takes a few seconds if you switch slots and do factory reset again it's already done
Click to expand...
Click to collapse
I'm talking about the system partition, not data. Data is shared between both slots, so obviously wiping it on one is all that is needed.
admiralspeedy said:
I'm talking about the system partition, not data. Data is shared between both slots, so obviously wiping it on one is all that is needed.
Click to expand...
Click to collapse
I said factory reset did both slots I never said system did that's why I asked the other member about it but I've been testing ROMs I have flashed just about every one of them some of them several times and I haven't had to do a system wipe at all so I don't really think it's needed. Only ever caused me problems for me. But obviously I was doing something wrong that's why I asked
mac796 said:
I said factory reset did both slots I never said system did that's why I asked the other member about it but I've been testing ROMs I have flashed just about every one of them some of them several times and I haven't had to do a system wipe at all so I don't really think it's needed. Only ever caused me problems for me. But obviously I was doing something wrong that's why I asked
Click to expand...
Click to collapse
I started this thread by asking about the system partition, so I kind of assumed you were also referring to the system partition.
admiralspeedy said:
I started this thread by asking about the system partition, so I kind of assumed you were also referring to the system partition.
Click to expand...
Click to collapse
Was referring to them both. I don't think it's needed
Related
So I wanted to go to Lollipop and I happened to flash the twrp recovery for new layout(as i was getting boot loop when flashing the rom with cwm recovery)
The things i tried until now.
1. Installed twrp and formatted it to get the new layout. Wiped everything, system, cache, data, dalvik cache
2. It was supporting MTP so i transferred the roms to the device being in recovery. Installed CM 12 + gapps for lollipop.
3. Rebooted to bootloader again. flashed boot.img, and did fastboot erase cache.
4. Rebooted again and stuck at CM boot logo.
I wiped the cache, dalvik cache(actually did a factory reset in the twrp recovery) and tried installing Resurrection Remix. Again flashed the relevant boot.img too. But the same result..
Did i destroy my phone?
anoopknayak said:
So I wanted to go to Lollipop and I happened to flash the twrp recovery for new layout(as i was getting boot loop when flashing the rom with cwm recovery)
The things i tried until now.
1. Installed twrp and formatted it to get the new layout. Wiped everything, system, cache, data, dalvik cache
2. It was supporting MTP so i transferred the roms to the device being in recovery. Installed CM 12 + gapps for lollipop.
3. Rebooted to bootloader again. flashed boot.img, and did fastboot erase cache.
4. Rebooted again and stuck at CM boot logo.
I wiped the cache, dalvik cache(actually did a factory reset in the twrp recovery) and tried installing Resurrection Remix. Again flashed the relevant boot.img too. But the same result..
Did i destroy my phone?
Click to expand...
Click to collapse
can you enter in recovery ?
wipe dalik,chace,chace,data then go to,mount select system,chace,data,2gb extra data ,and disabel mtp
if your phone dot show up just leave it on select partions to mount ,unplug cable then plug it back,go to device manager btw and see will it show there
dado323 said:
can you enter in recovery ?
wipe dalik,chace,chace,data then go to,mount select system,chace,data,2gb extra data ,and disabel mtp
if your phone dot show up just leave it on select partions to mount ,unplug cable then plug it back,go to device manager btw and see will it show there
Click to expand...
Click to collapse
Yes I can enter recovery. But again I just cant get any lollipop ROM's working. I dont know whether i have to restore to kitkat(i really dont want too..
I dont get it.. Wipe dalvik cache, cache, data and then disable mtp and then enable mtp.. I mean at the end what does this do?
And in the meanwhile did you mean HTC Sync Manager for device manager. FYI I use a mac(if this helps to get into the problem). And i had flashed kitkat roms from the same without a hiccup but lollipop is failing
anoopknayak said:
Yes I can enter recovery. But again I just cant get any lollipop ROM's working. I dont know whether i have to restore to kitkat(i really dont want too..
I dont get it.. Wipe dalvik cache, cache, data and then disable mtp and then enable mtp.. I mean at the end what does this do?
And in the meanwhile did you mean HTC Sync Manager for device manager. FYI I use a mac(if this helps to get into the problem). And i had flashed kitkat roms from the same without a hiccup but lollipop is failing
Click to expand...
Click to collapse
its hard to explain with recovery you can mount ur sdcard and put another room and install ,the easy way its to start from the begin and install clear CM12 and you will get out from bootloop that help me i was in bootloop like 3920489208420984920 times hahaha
anoopknayak
Have you solve the bootloop issue? I am having the same problem on my International One X
thanks
Probably both of you encountered the same problem as me.
If you are S-on, you have to flash rom and kernel separately. Also, if you try to revert any changes with twrp you have to flash kernel you were using during creation of backup, and then restore backup.
In other words: your current kernel is incompatible with rom.
Mwys
Yes i am S-ON. Can you tell me what the steps are to flash the kernel? I do not have a backup.
What is did was flash New Layout TWRP, did a complete wipe, then copied the ROM and G-Apps zips to the phone, installed them and then flashed boot.img.
Thanks for the help
Yup I also tried the same. but no luck. I tried to revert back to kitkat(by installing cwm, format the storage, sideloaded the ROM and gapps, flashed the boot.img) and still again in bootloop.
Sorry for the delay. I was a lot too busy with work.
Hi! I went into the latest TWRP recovery with unlocked bootloader, and I wiped system, cache, dalvik and data. Then I flashed the proper vendor image, the ROM zip, Gapps and then Elemental X kernel. However, when I reboot, it just boots me into TWRP recovery. I have tried wiping dalvik cache and cache. I then tried restoring a nandroid, but it just got stuck on the Google screen. Didn't even get to the colored dots screen. I ended up flashing factory image, but I would like to get my Nandroids working and this ROM. Please help! Thanks
I'm no expert but I think it might be happening because of encryption. Did you disable encryption before doing all this stuff?
Aman301582 said:
I'm no expert but I think it might be happening because of encryption. Did you disable encryption before doing all this stuff?
Click to expand...
Click to collapse
Encryption in stock Android? As far as I know, I can't turn it off. It says that the device is encrypted in settings. I think nougat forces encryption.
Unless maybe there's a patched kernel that can do that?
NateDev473 said:
Encryption in stock Android? As far as I know, I can't turn it off. It says that the device is encrypted in settings. I think nougat forces encryption.
Unless maybe there's a patched kernel that can do that?
Click to expand...
Click to collapse
I dont think is your problem , im encrypted and never have issues with twrp! Never!! What version of twrp you running? Theres an unofficial kicking around that is much better than official! Maybe you got a bad download! I would redownload all, find and download unofficial twrp 3.0.2.3 I believe. Let your phone boot before you flash custom kernel, thats always worked great for me. The latest official twrps 3022 and 3021 both have nandroid restore issues as well efs restore issues that could ruin your day
Format data and system (format, not wipe) and try installing it again. Should work
OK, thanks
neth15 said:
Format data and system (format, not wipe) and try installing it again. Should work
Click to expand...
Click to collapse
Only data and system? Not cache and dalvik like the purenexus install guide says?
NateDev473 said:
Only data and system? Not cache and dalvik like the purenexus install guide says?
Click to expand...
Click to collapse
Ofc wipe all partitions, but these two also format.
neth15 said:
Ofc wipe all partitions, but these two also format.
Click to expand...
Click to collapse
What's the difference between wipe and format? On TWRP there is only WIPE for all partitions, but a format data button.
NateDev473 said:
What's the difference between wipe and format?
Click to expand...
Click to collapse
Wipe just deletes all data on the partition. Format makes the partition again, therefore it removes encryption, repairs potential problems etc. Format data has dedicated button in TWRP, for formatting System go to Advanced Wipe, check system, tap on Partition details, check EXT4 and perform format.
neth15 said:
Wipe just deletes all data on the partition. Format makes the partition again, therefore it removes encryption, repairs potential problems etc. Format data has dedicated button in TWRP, for formatting System go to Advanced Wipe, check system, tap on Partition details, check EXT4 and perform format.
Click to expand...
Click to collapse
There is no Partition details button. Just fix partition or something like that.
NateDev473 said:
There is no Partition details button. Just fix partition or something like that.
Click to expand...
Click to collapse
Repair or Change filesystem? Yeah, it should be that.
neth15 said:
Repair or Change filesystem? Yeah, it should be that.
Click to expand...
Click to collapse
OK, I will do that. Thanks Just to clarify, I format data and system, and wipe cache and dalvik?
A Thought
Dunno if this will help, but whenever I flash a ROM/kernel combo, I always flash the ROM/gapps, boot up with whatever kernel is included in ROM to make sure it boots properly, and then after successful boot flash EX kernel through TWRP.
OK, so I formatted DATA and SYSTEM, and I wiped CACHE and DALVIK. I then flashed the proper vendor image, pushing it to the device with adb push, and then adb sideload for the pure nexus ROM. It's currently installing. Then, I will adb sideload the gapps ZIP file. Then I'll reboot and see if it worked
EDIT: It just said "No OS installed"
EDIT 2: Just flashed the ROM again, and it is showing the boot animation. This time I did not do Gapps. I also wiped and formatted everything again. Hope all goes well.
EDIT 3: The ROM booted fine. Glad all is working now
NateDev473 said:
OK, so I formatted DATA and SYSTEM, and I wiped CACHE and DALVIK. I then flashed the proper vendor image, pushing it to the device with adb push, and then adb sideload for the pure nexus ROM. It's currently installing. Then, I will adb sideload the gapps ZIP file. Then I'll reboot and see if it worked
EDIT: It just said "No OS installed"
EDIT 2: Just flashed the ROM again, and it is showing the boot animation. This time I did not do Gapps. I also wiped and formatted everything again. Hope all goes well.
EDIT 3: The ROM booted fine. Glad all is working now
Click to expand...
Click to collapse
Good job You're welcome
neth15 said:
Good job You're welcome
Click to expand...
Click to collapse
So I had flashed the ROM with no Google Apps or anything, just the ROM. But when I add a Google Account, I can't because it says Google Play Services has stopped. I just noticed that the build number is one of a Nexus 6P, and the vendor image is different, the one I manually flashed.
Hey,
So im currently on holiday and dont get back home until the 13th aug.
I was on my phone last night until i ran out of battery and the phone inevitably died. I charge it this morning and the phone is stuck on the boot animation and has a slowly flashing blue led. I do get past the lg bootloader unlocked screen too and the android boot animation runs fine, just never completes. My phone is running bootloader unlocked, twrp recovery and the imperium rom. My model is h815 and s/n is 512 prefix. The battery was running pretty bad so it might be that. Either way it is stuck in bootloop and i am not sure how to approach it. I also have some internal storage that would need backing up if possible.
Cheers for any help
That's a common issue with Imperium ROM, check post #3341 in this thread for example. Just do a clean flash and your system is back again, but sadly you will lose the apps and settings.
MattheewHun said:
That's a common issue with Imperium ROM, check post #3341 in this thread for example. Just do a clean flash and your system is back again, but sadly you will lose the apps and settings.
Click to expand...
Click to collapse
Thats interesting, never thought of that. I should be able to backup any files etc from the internal storage using adb right?
Simply dont wipe internal storage, only wipe data, cache, dalvik and system. THe files on your Internal storages not gonna' deleted, just reinstall the apps you had.
MattheewHun said:
That's a common issue with Imperium ROM, check post #3341 in this thread for example. Just do a clean flash and your system is back again, but sadly you will lose the apps and settings.
Click to expand...
Click to collapse
MattheewHun said:
Simply dont wipe internal storage, only wipe data, cache, dalvik and system. THe files on your Internal storages not gonna' deleted, just reinstall the apps you had.
Click to expand...
Click to collapse
Another problem is that i cant boot into twrp recovery using the buttons. It brings me to the stock recovery asking to factory reset. I guess i could just wait until im home and use adb to boot into the twrp recovery.
jet399 said:
Another problem is that i cant boot into twrp recovery using the buttons. It brings me to the stock recovery asking to factory reset. I guess i could just wait until im home and use adb to boot into the twrp recovery.
Click to expand...
Click to collapse
Yep. That's what it looks like for me too. When you select factory reset, the phone actually restarts into TWRP.
Make sure you actually do have TWRP installed otherwise it will wipe your phone.
You have a custom ROM installed so I assume competence, but there's always a chance
If you think I'm pulling a prank, here's some validation:
https://forum.xda-developers.com/tmobile-g4/help/booting-twrp-manually-t3371237
htr5 said:
Yep. That's what it looks like for me too. When you select factory reset, the phone actually restarts into TWRP.
Make sure you actually do have TWRP installed otherwise it will wipe your phone.
You have a custom ROM installed so I assume competence, but there's always a chance
If you think I'm pulling a prank, here's some validation:
https://forum.xda-developers.com/tmobile-g4/help/booting-twrp-manually-t3371237
Click to expand...
Click to collapse
Yeah i saw that post and was reluctant to do so as im on my holiday. Dont want to lose my pics either, even when im very sure twrp is installed correctly as i use the quick boot app to go into recovery quite often.
Hi!! I flashed twrp as soon as I got the device and as a redmi note 3 user I don't know anything about vendor so I wiped it and even flashed 3 OTA updates of RR will I face any problems in future?if yes are there any solution?
Ps- now the device is running fine no probs at all
**Thanks for tuning in this question is answered**
Yep. Now you can't mount data, vendor and probably can't flash any other roms.
Happens to my other devices.
beeduq said:
Yep. Now you can't mount data, vendor and probably can't flash any other roms.
Happens to my other devices.
Click to expand...
Click to collapse
False. Please don't spread misinformation.
RR overwrites the vendor partition anyway, so @sreek995 will have no problems. If you eventually want to flash GSIs just flash this first.
Oh, then I might used bad recoveries. Happens to my two of smartphones and a tablet.
Every time, I wiped the vendor, I can't re-mount it after rebooting the recovery, even after wipe it and installing a rom seems works fine, but rebooting to recovery, "can't mount vendor" error pops up. Now I always stay away from clicking vendor when wiping the device.
JoseRebelo said:
False. Please don't spread misinformation.
RR overwrites the vendor partition anyway, so @sreek995 will have no problems. If you eventually want to flash GSIs just flash this first.
Click to expand...
Click to collapse
thank you sir!!
beeduq said:
Oh, then I might used bad recoveries. Happens to my two of smartphones and a tablet.
Every time, I wiped the vendor, I can't re-mount it after rebooting the recovery, even after wipe it and installing a rom seems works fine, but rebooting to recovery, "can't mount vendor" error pops up. Now I always stay away from clicking vendor when wiping the device.
Click to expand...
Click to collapse
This is actually my first phone with a vendor partition, but that is weird. Bad TWRPs are probably doing something terribly wrong, that shouldn't happen. But you should still be able to flash the vendor partition.
Sorry if my message came out a bit too harsh.
JoseRebelo said:
This is actually my first phone with a vendor partition, but that is weird. Bad TWRPs are probably doing something terribly wrong, that shouldn't happen. But you should still be able to flash the vendor partition.
Sorry if my message came out a bit too harsh.
Click to expand...
Click to collapse
Me and vendors were not in good terms, I guess. ?
beeduq said:
Oh, then I might used bad recoveries. Happens to my two of smartphones and a tablet.
Every time, I wiped the vendor, I can't re-mount it after rebooting the recovery, even after wipe it and installing a rom seems works fine, but rebooting to recovery, "can't mount vendor" error pops up. Now I always stay away from clicking vendor when wiping the device.
Click to expand...
Click to collapse
I think after formating data ,you might mount it again.
Dush4711 said:
I think after formating data ,you might mount it again.
Click to expand...
Click to collapse
Nope, it's gone and never mounted again. Even format, repair or change the storage type cannot re-mount the vendor.
The only way, I can get it to work is by flashing original recovery using computer and let it format it. After that, using computer flash twrp.
But I never unlocked bootloader in this device (note5), so I don't know about it's recovery. Xiaomi's can be very tricky or very easy. My wifes phone (Mi 5X) came with unoriginal rom, and I brick it when trying to install twrp, but by open the device and doing something inside of it, I manage to restore it to original and flash twrp.
beeduq said:
Oh, then I might used bad recoveries. Happens to my two of smartphones and a tablet.
Every time, I wiped the vendor, I can't re-mount it after rebooting the recovery, even after wipe it and installing a rom seems works fine, but rebooting to recovery, "can't mount vendor" error pops up. Now I always stay away from clicking vendor when wiping the device.
Click to expand...
Click to collapse
it happened on my samsung j6 plus (SM_J610F) and i can not even flash it with original rom (in download mode it said sw rev check failed fused 4 binary 1) and t can not do any thing. twrp said /vendor has no data in it (0MB) and vendor img has (477MB). do you have any idea i can resurect my phone from dead.
tumo07 said:
it happened on my samsung j6 plus (SM_J610F) and i can not even flash it with original rom (in download mode it said sw rev check failed fused 4 binary 1) and t can not do any thing. twrp said /vendor has no data in it (0MB) and vendor img has (477MB). do you have any idea i can resurect my phone from dead.
Click to expand...
Click to collapse
Use PIT file for your model (don't use other or you'll brick the phone) in Odin.
Good luck.
Sent from my SM-A300FU using XDA Labs
;-;
you dont wipe vendor partition and reboot. If you wipe vendor, wipe system partition too reinstall the rom and everything runs fine. If you wipe vendor and dont flash rom, sure you'll get into trouble(Not that trouble actually,just cant boot into your rom).
Prathamesh 27 said:
you dont wipe vendor partition and reboot. If you wipe vendor, wipe system partition too reinstall the rom and everything runs fine. If you wipe vendor and dont flash rom, sure you'll get into trouble(Not that trouble actually,just cant boot into your rom).
Click to expand...
Click to collapse
yep, vendor is essential to runs the system
What's the proper way to dirty flash? I used to be able to dirty flash on my OnePlus One by just flashing the ROM and Gapps and it'll boot right away. But with the 5T, half the time this method doesn't work anymore and I get stuck on the splash screen. I don't use passwords or pins so there should be no encryption, but even when I flash no-verity.zip, my phone still gets stuck on the splash screen.
geokilla said:
What's the proper way to dirty flash? I used to be able to dirty flash on my OnePlus One by just flashing the ROM and Gapps and it'll boot right away. But with the 5T, half the time this method doesn't work anymore and I get stuck on the splash screen. I don't use passwords or pins so there should be no encryption, but even when I flash no-verity.zip, my phone still gets stuck on the splash screen.
Click to expand...
Click to collapse
wipe dalvik art cache, cache and system
I do that just like with all my other phones, but it just hangs on the splash screen. Dirty flashing used to be so simple but now even clean flash doesn't work 100%.
geokilla said:
I do that just like with all my other phones, but it just hangs on the splash screen. Dirty flashing used to be so simple but now even clean flash doesn't work 100%.
Click to expand...
Click to collapse
Don't wipe Dalvik / ART cache, you will have problems. Factory Reset will I usually make it boot again. If you do a clean flash boot once before installing things like Magisk.
Wipe cache, Flash ROM, Gapps, Kernel if you run a custom ROM.
Make sure you are not using the official TWRP, either codeworkx or blu_spark (eng.stk). Having. a password or pin is NOT a problem.
OhioYJ said:
Don't wipe Dalvik / ART cache, you will have problems. Factory Reset will I usually make it boot again. If you do a clean flash boot once before installing things like Magisk.
Wipe cache, Flash ROM, Gapps, Kernel if you run a custom ROM.
Make sure you are not using the official TWRP, either codeworkx or blu_spark (eng.stk). Having. a password or pin is NOT a problem.
Click to expand...
Click to collapse
Factory Reset and even wipe data doesn't boot. Only way I got it to boot was to wipe internal storage. It would however flash stock OxygenOS fine though. It's just every time I tried to dirty flash or even clean flash Havoc OS without wiping internal storage I'd get issues it seems.
geokilla said:
Factory Reset and even wipe data doesn't boot. Only way I got it to boot was to wipe internal storage. It would however flash stock OxygenOS fine though. It's just every time I tried to dirty flash or even clean flash Havoc OS without wiping internal storage I'd get issues it seems.
Click to expand...
Click to collapse
I would ask in the Havoc OS thread then. That would seem out of the ordinary. For Lineage most people dirty flash every week. I clean flash every so often, but I basically never clean flash my wife or sons phone, no issues. So these issue might be isolated to the ROM you are trying to run.
Not to mention wiping internal storage all the time would be very annoying...
OhioYJ said:
I would ask in the Havoc OS thread then. That would seem out of the ordinary. For Lineage most people dirty flash every week. I clean flash every so often, but I basically never clean flash my wife or sons phone, no issues. So these issue might be isolated to the ROM you are trying to run.
Not to mention wiping internal storage all the time would be very annoying...
Click to expand...
Click to collapse
I've asked in the Havoc OS thread but the instructions to clean and dirty flash are the same as when I first played with custom ROMs back in the Samsung Galaxy S days. Wipe system, wipe data, wipe the two caches, etc etc.
If you're using a Substratum theme, make sure to disable all overlays before flashing.
Sorry for digging this post, but with android 10 there is no way to decrypt the data partition.
So how do you dirty flash android 10 "properly" ?