I have purchased G6 and flashed TWRP and custom ROM but have a problem. When i wipe data partition and flash a custom ROM can not to write in data partition and must to wipe again...after that the same story. There is some problem in TWRP i think or some security reason for that. Dm-veryty flash does not work.
Related
Title says it all!
I know that this should be done trough TWRP recovery but, what i need?
Backups?
Kernel with F2FS support?
ROM with F2FS support?
SuperSU can cause any problems?
Thanks in the advance for your time!
UP!
No one interested?
Ok this how i do it. It works out well for me but some get asked for an encryption pw.
Go into twrp recovery that supports f2fs
Wipe everything, format normally
Flash rom compatible with f2fs
Flash GApps
Flash kernel compatible with f2fs
Flash SuperSU
Wipe cache/dalvic
Boot into android startup screen
Reboot into recovery
Make a nandroid backup
Trasnfer nandroid backup to pc
Wipe/format again normally
Select data, then change file system, then change data to f2fs
Transfer nandroid backup back to phone
Restore nandroid backup
factory reset wipe
Reboot
Profit.
Hi,
I have a rooted OP5 with 4.5.13.
I tried to install the flashable zip (from here) via TWRP without wipe, but ended up in a bootloop.
I've restored to the nandroid backup, wiped data, and tried again. This time the OP5 managed to boot only to recovery.
I've verified the md5 of the file I've used.
Do you know why this is happening? Do you know how I can upgrade to 4.5.14?
Thanks.
Did you download the full ROM or just the update?
I tried both. I didn't succeeded to install the update (as it is not intended for rooted devices).
The full rom is what caused the bootloop.
If you are doing a dirty flash you wipe cache and system. If you are doing a clean flash you wipe cache, system and data. It doesn't sound like you wiped the correct partitions when doing your flash. You also need to flash Magisk or SU after the ROM flash and before booting up or you will lose TWRP and root. If your phone is decrypted for some reason you also need to flash a no verify zip or your phone will boot loop because OOS is made for encrypted phones.
Hello everyone.
Usually I just format things through TWRP and flash a new ROM, but I found the following in a Nexus 6 thread:
As to what I usually do for a really clean install (likely overkill):
Reboot to Bootloader
Wipe everything (fastboot erase all)
Do flash-base.sh from latest factory image (this reflashes modem partitions; this is required after erase all)
Boot to Recovery
Wipe everything from TWRP
Reboot to Recovery
Wipe everything again from TWRP (old habit from when the first wipe didn't actually get rid of everything on older devices)
fstrim Data, Cache, System, and Firmware partitions
Reboot to Recovery
ROM
GApps (I don't use GApps, but if I did, this is when they are to be flashed)
Reboot to Recovery
Wipe everything except System from TWRP
Format Data and Cache to F2FS
fstrim Data and Cache partitions
Reboot to Recovery
Kernel
Magisk
Reboot to System
Do set-up and copy files over to device
Reboot to Recovery
Wipe Dalvik Cache (I guess the button in TWRP would work; I do rm -Rf /data/dalvik-cache)
Use filesystem tools to check and repair partitions (e2fsck for ext4 being System and Firmware partitions, and fsck.f2fs for F2FS being Data and Cache partitions)
fstrim Data, Cache, System, and Firmware partitions
Reboot to System
Click to expand...
Click to collapse
Is there anything similar for Moto G5 Plus? I would really like to make a deep cleanup in my phone before flashing a new ROM.
Thanks in advance.
vitorsubs said:
Hello everyone.
Usually I just format things through TWRP and flash a new ROM, but I found the following in a Nexus 6 thread:
Is there anything similar for Moto G5 Plus? I would really like to make a deep cleanup in my phone before flashing a new ROM.
Thanks in advance.
Click to expand...
Click to collapse
Except part 1: flash-base.sh from latest factory image (we have no factory image) you can do everything on the Moto G5+ too.
The question is if that is really needed.
Wiping twice with TWRP isn't necessary anymore but you can do it if you want.
fstrim isn't really needed imo, but you can do it from terminal if you want.
And checking the partitions for errors may be a good thing but if the partitions are faulty you would recognise it when you try to flash anything. But this is a thing you can do too if you want to.
You can find the exact usage of the commands for fstrim and e2fsck and fsck.f2fs by googling for it.
If I want to be sure that everything is cleaned up I wipe all partitions except external SD with TWRP, reformat data (you'll have to do that as the F2FS formatted data partition is encrypted) and flash my usual stuff like ROM, gapps, kernel, magisk etc.
Sent from my Moto G5 Plus using XDA Labs
So I've seen with installing custom ROMs that there are steps that basically say, "Do not wipe system" in TWRP. I have noticed in doing things the dumb way that I can wipe every partition but the only way it becomes unrecoverable is if system is wiped, this is even if I install a custom ROM in its place. Can someone help me understand what has changed with A/B partition or OnePlus security settings where OOS system partition must be intact to allow one to run a custom ROM?
The reason I ask is that unless it is a byte for byte overwrite then we leave OOS files on parts of the custom ROM storage partition and if it is bit for bit write why would erasing the partition matter?
What seems more important for custom ROM is to not wipe data before rebooting in TWRP to flash magisk. So a clean flash is now flashing the ROM, flashing TWRP then reboot in TWRP and then only wiping data and art. Then flashing magisk. This is important to keep decryption working. That means not using factory reset feature either, always wiping with manually selected partitions.
Anyway wiping system is useless as the flashing script wipes it anyway.
Hey everybody.
I have a problem on the phone and i have been trying to fix it for about 2 days.But no luck.
I had been using MIUI for about 1 year, then i wanted to flash a custom rom.The recovery is orangefox R11.1.On the recovery i wipe cache, dalvik, data and system and i try to flash Pixel experience 9.Also i tried to flash lineageos 16.But the same problem occurs.Just after the flash i clean dalvik and cache.And just for the first boot it says the data is encrypting.I can not escape from it.When i restart it asks for a pin and as you know there is no pin i added, so i can not put it.Then to decrypt the data i have to wipe data again.Then if i flash theese roms the same problem again.
Also i, just after the flashing, before rebooting the phone, tried to delete some lock files on /data/system folder.But unless i reboot there is not a system folder in data.And if i try to reboot it encrypts the folder again.
Is there any fix for that?I am expecting your ideas or helps.Thank you.
Does the rom boot?
Try formatting (not wiping) the data partition. Obviously you'll lose all the data but I think it's the only way. When you change rom on rn7 you have to format data.
darhma said:
Does the rom boot?
Try formatting (not wiping) the data partition. Obviously you'll lose all the data but I think it's the only way. When you change rom on rn7 you have to format data.
Click to expand...
Click to collapse
Thank you very much.I fixed the problem and wanted to share it here to help the others who face the same problem.
-First of all i upgraded the latest version of orange fox.
-I formatted data partition completely.Then i wiped Data, Dalvik, Cache, System.
-I flashed Pixel Experience 9 rom.But an important thing is before i flash the rom i enter options > OTA & ROM settings.And ticked "Disable Forced Encryption".
-Then i flashed the rom and on the line it says "disabling forced encryption".And it worked.Now i use the rom without any problem.