Database Develop

System wipe

Hey. What are the advantages/disadvantages of wiping system when installing new ROM? For example Xiaomi.eu rom instructions says you should not wipe system or phone can be bricked. But there are many tutorials that say to wipe also system when installing new ROM.
I've had cm 13, cm 14.1 and different versions of Xiaomi.eu but I've never wiped system - just cache, dalvik and data. I wonder if this causes some problems on my mi 5.

Full wipe of your Mi 5 storage does NOT cause problems to your phone of any sort. In fact, it is good to perform a full wipe of your phone when you are upgrading from one android version or another, for example cm13 to cm14.1! Full wiping completely removes all junk on your phone as it literally removes everything. One thing to not however, is that you will need to reflash your recovery and your preferred ROM after performing a full wipe. If you are just thinking of flashing between different builds of the same ROM such as between CM14.1 nightly builds, only a dirty flash is needed (Clearing cache/dalvik). Hope this clear things up for you!

achickennugget said:
Full wipe of your Mi 5 storage does NOT cause problems to your phone of any sort. In fact, it is good to perform a full wipe of your phone when you are upgrading from one android version or another, for example cm13 to cm14.1! Full wiping completely removes all junk on your phone as it literally removes everything. One thing to not however, is that you will need to reflash your recovery and your preferred ROM after performing a full wipe. If you are just thinking of flashing between different builds of the same ROM such as between CM14.1 nightly builds, only a dirty flash is needed (Clearing cache/dalvik). Hope this clear things up for you!
Click to expand...
Click to collapse
I understand. Just thinking the term "full wipe". Somewhere that is data/dalvik/cache wipe, somewhere data/dalvik/cache/system wipe. I always do clean flash when i change between roms and clear cache/dalvik/data. But I'm just unsure about wiping system partitition. At least with xiaomi.eu rom you should NOT wipe system, just data/cache/dalvik.
Some AOSP roms are advicing wiping also system partitition.

The "System" partition is essentially where your OS resides (correct me if I'm wrong!), hence by wiping it, you are essentially removing your OS. Reinstalling the ROM afterwards then ensures that the ROM is in a sense "cleanly" flashed and will not have any unnecessary or corrupt files of sorts. Wiping system partition will NOT cause issues, that I can guarantee you, just that your phone will not have any OS to boot into when you reboot. Which is why I recommend you to have the ROM and recovery zip on your computer to flash it afterwards!

Well it's safe to wipe system partition but I am not sure about xiaomi.eu nougat ROM's the first nougat update bricked many devices, anyways wiping system is safe.

Going back to nougat

So, I have the nexus 6 and one plus 3t...on the 3t, going back to nougat you have to wipe internal storage, do you have to do the same here?

jamescable said:
So, I have the nexus 6 and one plus 3t...on the 3t, going back to nougat you have to wipe internal storage, do you have to do the same here?
Click to expand...
Click to collapse
If you're referring to flashing the factory image, yes I it will automatically wipe internal storage. Alternatively you could just wipe system/data/cache/dalvik and just install a nougat based custom ROM, the most recommended one being the infamous PureNexus. Some people its possible to flash the factory recovery from inside TWRP so give that a look too. :good:

Ta3miyyasandwich said:
If you're referring to flashing the factory image, yes I it will automatically wipe internal storage. Alternatively you could just wipe system/data/cache/dalvik and just install a nougat based custom ROM, the most recommended one being the infamous PureNexus. Some people its possible to flash the factory recovery from inside TWRP so give that a look too. :good:
Click to expand...
Click to collapse
What I am referring to is this, on 3t, if I am on a custom Oreo ROM, and want to go back to custom nougat, if I wipe system, dalvik,data, and cache...install a nougat ROM, it will boot but make me wipe internal memory...

I don't believe there is any reason a custom nougat ROM will trigger a wipe of user data (internal storage). Of course it's always a good idea to back up just in case [emoji6]
I know you're not talking about stock, but the only time user data is wiped automatically is by using the stock install script. The script can be modified to not flash user data. Or better, just manually fastboot flash the stock ROM excluding the user data partition. The -w flag is the wipe command.
"Good judgment comes from experience, and a lot of that comes from bad judgment." - Will Rogers

Returning to stock/xiaomi.eu rom after aosp (after wiping /system)

Hey there,
today I started flashing my mi9tpro.
First I tried xiaomi.eu, but still wasn't happy about the security/junkcleaner integration ...
So I moved on to paranoid quartz 4 for the start. Runs nice and smooth, could settle here.
But I wanted to give ressurection, crdroid, havoc a try too.
Now there is a conflict between the statement of xiaomi.eu:
FORMAT /data partition (NEVER wipe System or Persist!)
Click to expand...
Click to collapse
And e.g. crdroid:
Wipe Data/Cache/System when coming from non-AOSP ROMs
Click to expand...
Click to collapse
Sure, I am coming from a non-AOSP rom, so this is a step I need to do for trying the other roms based on AOSP.
BUT:
If I want to return to Miui, Xiaomi.eu or Paranoid ... will there be troubles about flashing?
Do I need to flash anything, so /system is returned to stock?
I made a full backup booting twrp before flashing anything (even twrp), so if I need a original /system, I should be able to restore this image.
Greetings

houston_ said:
Now there is a conflict between the statement of xiaomi.eu:
And e.g. crdroid:
Sure, I am coming from a non-AOSP rom, so this is a step I need to do for trying the other roms based on AOSP.
BUT:
If I want to return to Miui, Xiaomi.eu or Paranoid ... will there be troubles about flashing?
Do I need to flash anything, so /system is returned to stock?
Click to expand...
Click to collapse
No need to format /System, as it afaik can result in an instant-bootloop to Fastboot, which may then cause you to reflash the whole MIUI Fastboot ROM.
When coming from MIUI to AOSP ROMs, formatting /Data (aka the "Format Data" Option where you have to type "yes") should be enough.
Same process goes when going back to MIUI from AOSP.
Hope it helped!

houston_ said:
Hey there,
today I started flashing my mi9tpro.
First I tried xiaomi.eu, but still wasn't happy about the security/junkcleaner integration ...
So I moved on to paranoid quartz 4 for the start. Runs nice and smooth, could settle here.
......
If I want to return to Miui, Xiaomi.eu or Paranoid ... will there be troubles about flashing?
Do I need to flash anything, so /system is returned to stock?
I made a full backup booting twrp before flashing anything (even twrp), so if I need a original /system, I should be able to restore this image.
Greetings
Click to expand...
Click to collapse
The system partition is home to the OS. Every time you flash a ROM, you replace the system partition. If you want to return to stock, flashing MIUI will restore the stock system partition.
In reality there is no need to wipe the system partition, because flashing a ROM will wipe it automatically anyway, before installing the new ROM.
When flashing new ROMs, doing a factory reset is all that's needed. You should rarely need to enter advanced wipe menu in TWRP.
The only extra step required is when flashing over MIUI (official or custom version). In this case you will also need to format data too.
Follow my guide for flashing
https://forum.xda-developers.com/k20-pro/how-to/simple-guide-flipkart-owners-t4151007/post83329343

Thanks for both of of your answers! So nothing really changed since my HTC10. On my Cubot I used gsi images... Unsuccessfully, but quite easy.
Just wanted to ask before loosing something important

Havoc OS won't install

hey y'all, i hope everyone is okay.
I have (well now it's "i had") Havoc OS installed on my Redmi 8 but i wanted to return to the MIUI. I taught that I could do the installation just like with havocOS, but if it was like that i wouldn't post here. After it "installed" I rebooted it but it was in bootloop and i entered OrangeFox. I then tried to install HavocOS again but it again got in a bootloop. I was thinking that I should wipe something, and I selected Dalvik/ART Cache, Data, Internal Storage, Cache and System. When i got back to the Files section it says "Folder is empty". I taught it was okay and then i tried to copy HavocOS to the Internal Storage but when I entered that folder on my computer there was, and still is, 3 internal storages ("18.1 GB free of 20.4 GB) and one micro sd card folder. I don't know what I did and now whenever i try to copy some file to the Internal Storage it does not show on the OrangeFox. I am scared of restarting the phone so please, if you want to help me don't say i have to restart it unless I really have to.
Thanks!

p_vujic07 said:
hey y'all, i hope everyone is okay.
I have (well now it's "i had") Havoc OS installed on my Redmi 8 but i wanted to return to the MIUI. I taught that I could do the installation just like with havocOS, but if it was like that i wouldn't post here. After it "installed" I rebooted it but it was in bootloop and i entered OrangeFox. I then tried to install HavocOS again but it again got in a bootloop. I was thinking that I should wipe something, and I selected Dalvik/ART Cache, Data, Internal Storage, Cache and System. When i got back to the Files section it says "Folder is empty". I taught it was okay and then i tried to copy HavocOS to the Internal Storage but when I entered that folder on my computer there was, and still is, 3 internal storages ("18.1 GB free of 20.4 GB) and one micro sd card folder. I don't know what I did and now whenever i try to copy some file to the Internal Storage it does not show on the OrangeFox. I am scared of restarting the phone so please, if you want to help me don't say i have to restart it unless I really have to.
Thanks!
Click to expand...
Click to collapse
Oh my God I'm so dead. I just wiped Micro SD card and now it isn't showing as well. I'm just so stupid. When i click reboot to the recovery it says "No OS installed! Are you sure you wish to reboot to the recovery?"

p_vujic07 said:
Oh my God I'm so dead. I just wiped Micro SD card and now it isn't showing as well. I'm just so stupid. When i click reboot to the recovery it says "No OS installed! Are you sure you wish to reboot to the recovery?"
Click to expand...
Click to collapse
I feel so stupid to reply on my posts every 2 minutes but I got the guts and I restarted the phone to the recovery and now it shows everything again. What it doesn't do is installing havoc OS. I installed it again but it booted in to the recovery. I don't know what to do

p_vujic07 said:
I feel so stupid to reply on my posts every 2 minutes but I got the guts and I restarted the phone to the recovery and now it shows everything again. What it doesn't do is installing havoc OS. I installed it again but it booted in to the recovery. I don't know what to do
Click to expand...
Click to collapse
Finally I done it, i formatted the data and then installed Havoc OS. Thanks @p_vujic07 (myself)! You are such a genius!

sorry for the late response, i do tend to watchover here in case someone needs help.
which miui are you flashing? if its xiaomi.eu, that requires stock. since youre using havoc, you deleted most of stock stuff (remember the install steps wiping stuff). also remember to format data (like you did in the last post) to remove most encryption (which also nterferes with recovery).
also which zip did you flash in the last thread? an encryption disabler?
are you still on havoc? does your internal still show as 20GB? 48 (out of 64) is the normal amount in sdcard0 and you should prolly reinstall stock if it isnt correct
upd
for our phone, its possible to install using an otg in case of derps
also for custom roms based on a11, its recd to use the beta 11.1_0

fonzacus said:
sorry for the late response, i do tend to watchover here in case someone needs help.
which miui are you flashing? if its xiaomi.eu, that requires stock. since youre using havoc, you deleted most of stock stuff (remember the install steps wiping stuff). also remember to format data (like you did in the last post) to remove most encryption (which also nterferes with recovery).
also which zip did you flash in the last thread? an encryption disabler?
are you still on havoc? does your internal still show as 20GB? 48 (out of 64) is the normal amount in sdcard0 and you should prolly reinstall stock if it isnt correct
upd
for our phone, its possible to install using an otg in case of derps
also for custom roms based on a11, its recd to use the beta 11.1_0
Click to expand...
Click to collapse
heyy, please sorry for this late answer. i was moving out so i couldn't answer you. it wasn't xiaomi.eu, but it was mi-globe. i tried to install with root (magisk) or wihout it but it wouldn't work. i tried xiaomi.eu, but when i saw that MIUI won't be supported on Redmi 8 i installed havoc again.
the encryption wasn't a problem so i really don't know what was it. maybe i am stupid so i get this now, but do you need to have official MIUI for mi-globe to work? i don't know, and, honestly, i don't want to. i am happy with my havoc, so anyways thank you and sorry for the latest answer you'll ever see!

like i said, most miui roms do require stock stuff (remember the wipes), you could also manually install a miui imgs and (theoretically) install miui roms but yeah i havent tried that.
how much internal storage does it show
are you using orfox 11.1_0 beta
did you flash an encryption disabler

Now it shows 32gb,so it's good
I'll now boot into recovery to see what is the version
I don't think that I used encryption disabled, I just used havoc is zip (also gapps and magisk)

p_vujic07 said:
Now it shows 32gb,so it's good
I'll now boot into recovery to see what is the version
I don't think that I used encryption disabled, I just used havoc is zip (also gapps and magisk)
Click to expand...
Click to collapse
Orange fox is R11.0_2

I installed havoc os only because I can't receive messages, like from what's up. With havoc os it works perfectly fine so I just wanted to install MIUI to see if they fixed the problem in 12.5 (or what was it) version

you should prolly reinstall stock again as sdcard0 should show 48gb (max 64). something messed up your partition. if its a low priority you could let it slide.
miui based roms wont work from most custom roms since they are using different system|vendor imgs.

Oh, you didn't understand. My phone has 32 gb, so it's all good. I don't want to install MIUI now because I don't know if my problem if solved (notifications) and MIUI 13 is going to come out, and Redmi 8 won't support it

ah sorry, i completely forgot about the 3/32 variant (ive only seen the 4/64).
i doubt 11 will even come out as fastboot 12.5.1 is only out for china only, and its been months lol. wouldnt matter to me for tons of reasons

Question My Redmi Note 10 pro not showing System and Vendor

Hi guys i am facing a liitle bit of a problem i unlocked my bootloader and flash some custom roms but after flashing lineage os the battery went down hill and tried to flash other roms to fix the problem also flashed the stock rom no luck.So i was trying to make a clean flash as last possible fix but the system and vendor options in advance wipe are not showing i mounted them but nothing show in advance wipe.I tried to flash different Twrp version old and new and still no luck also tried to flash Orangefox Recovery when i go to mount options and tried to ticked system and vendor it didnt ticked.I remember first time flashing Twrp after i reboot in recovery there was option (read only i guess) and i ignore it and it seems that's it become write only. (i tried to reflash the orangefox recovery and then the twrp to reset it but still no option for read only to untick it).Any idea to fix that issue?!Thanks.

Newbie2022 said:
Hi guys i am facing a liitle bit of a problem i unlocked my bootloader and flash some custom roms but after flashing lineage os the battery went down hill and tried to flash other roms to fix the problem also flashed the stock rom no luck.So i was trying to make a clean flash as last possible fix but the system and vendor options in advance wipe are not showing i mounted them but nothing show in advance wipe.I tried to flash different Twrp version old and new and still no luck also tried to flash Orangefox Recovery when i go to mount options and tried to ticked system and vendor it didnt ticked.I remember first time flashing Twrp after i reboot in recovery there was option (read only i guess) and i ignore it and it seems that's it become write only. (i tried to reflash the orangefox recovery and then the twrp to reset it but still no option for read only to untick it).Any idea to fix that issue?!Thanks.
Click to expand...
Click to collapse
Don't try to format or delete other partitions as data dalvik and cache! Risk of brick! And not necessary!
Only follow exactly step by step the ROM installation instructions
E.g.
👍 [SHARED][ROM] [ANDROID 13] [OSS] PULKITS lineage os 20 19.02.23/ checked by myself
Update on page 14 Update latest los 20 on page 7 I'm on pulkits android 13 for testing. Quiet good! Soon you'll get a beta! Thanks a lot to @Pulkit Agarwal Please donate him, thanks Update see post Post in thread '👍 [SHARED][ROM] [ANDROID...
forum.xda-developers.com

Newbie2022 said:
.... i was trying to make a clean flash as last possible fix but the system and vendor options in advance wipe are not showing i mounted them but nothing show in advance wipe......
Click to expand...
Click to collapse
I'm always surprised if someone want to do these kind of actions to resolve such relative simple problems. While imho nowhere such actions are described by flashing instructions.
"Simple" because the rom itself does work without issues, so the real reason for battery drain must be found, (wakelocks, sensors, updateproblems, running services etc.) which could be very time consuming,
By starting without Gapps to see what happens with battery, you find if the reason is rom or Google.
Other reasons could be VOlte, pocket detection, proximitysensor, hanging updates.
Flashing a new rom does replace the system and vendor partition, so everything what was on it is gone.
The data partitition needs to be formatted, because it is locked by encryption of the old rom.
Startup the new flashed rom after format data partition, does encrypt the new data again.

Laptapper said:
Don't try to format or delete other partitions as data dalvik and cache! Risk of brick! And not necessary!
Only follow exactly step by step the ROM installation instructions
E.g.
👍 [SHARED][ROM] [ANDROID 13] [OSS] PULKITS lineage os 20 19.02.23/ checked by myself
Update on page 14 Update latest los 20 on page 7 I'm on pulkits android 13 for testing. Quiet good! Soon you'll get a beta! Thanks a lot to @Pulkit Agarwal Please donate him, thanks Update see post Post in thread '👍 [SHARED][ROM] [ANDROID...
forum.xda-developers.com
Click to expand...
Click to collapse
Thanks man yes i know the risk but it seems to be the only option i have i tried to dirty flash Roms following instructions, but the battery drain issue persist so i was trying as last resort to clean flash and then stock rom in a hope to resolve the issue. Thank you very much really appreciated

Elinx said:
I'm always surprised if someone want to do these kind of actions to resolve such relative simple problems. While imho nowhere such actions are described by flashing instructions.
"Simple" because the rom itself does work without issues, so the real reason for battery drain must be found, (wakelocks, sensors, updateproblems, running services etc.) which could be very time consuming.
Flashing a new rom does replace the system and vendor partition, so everything what was on it is gone.
The data partitition needs to be formatted, because it is locked by encryption of the old rom.
Startup the new flashed rom after format data partition, does encrypt the new data again.
Click to expand...
Click to collapse
Yeah the issue was after flashing the rom something happened i don't know exactly what it is but the screen battery consumption hit the roof altouth i capped the refresh rate at 60 and use dark mode and brightness to 35 max . Before flashing the rom(lineage) i didnt had this issue with older other roms i flashed before the issue (pixel experience and pixel os)...I dirty flash other roms and even stock rom through Miflash tool but the same issue continued so i was hoping if i can clean flash the stock rom. Thanks alot man.

Newbie2022 said:
... i tried to dirty flash Roms following instructions, but the battery drain issue persist ....
Click to expand...
Click to collapse
"Dirty flash" means system and vendor partition will be replaced with the same files as before, but the data stays untouched. So this will have no impact on solving your problems.
"Clean flash" means the data is gone too for a new rom encryption.
With enabled encryption it is only possible to flash a new rom or stock rom by clean flash.
FYI: I solved huge battery drain what was caused by Pixel spoofing on a non Pixel.
Before I found this I was weeks further.
Only if everyone with the same rom has such drain too, there is something wrong with a rom.
If this is the case i can assure you this will be picked up by the developer of that rom.
If you have the same issue with different roms it could be directed to the hardware of the phone.
With RN10P the proximity sensor has known issues with some devices.

Elinx said:
"Dirty flash" means system and vendor partition will be replaced with the same files as before, but the data stays untouched. So this will have no impact on solving your problems.
"Clean flash" means the data is gone too for a new rom encryption.
With enabled encryption it is only possible to flash a new rom or stock rom by clean flash.
FYI: I solved huge battery drain what was caused by Pixel spoofing on a non Pixel.
Before I found this I was weeks further.
Only if everyone with the same rom has such drain too, there is something wrong with a rom.
If this is the case i can assure you this will be picked up by the developer of that rom.
If you have the same issue with different roms it could be directed to the hardware of the phone.
With RN10P the proximity sensor has known issues with some devices.
Click to expand...
Click to collapse
Ok i will check the spoof issue and try to flash stock rom again via Miflash tool hopefully the issue will be solved. Thanks a lot for the tips and insight