What is the proper way to format a galaxy nexus? I want to clear everything possible and start fresh in an attempt to solve the abysmal write speeds I've been getting recently and I don't want to wind up bricking the thing in the process since I know certain partitions store the boot loader and more.
Other attempts to fix the write speed including fstrim, changing the mount command to enable trimming deleted files automatically, completely filling all free space with zeros then removing it, and none have helped yet. It gets approximately 0.10-0.15KB/s on random write with androbench, 2.0-5.5MB/s for sequencial write. I've never had anything less than 12GB free space, except when I tried filling all the free space
I want to format before reinstalling cyanogenmod and I understand there are risks involved that could brick my device so any instruction for what should and should not be touched would be greatly appreciated.
You need custom recovery installed (twrp or cwm). I have twrp. You need from recovery, for example twrp, wipe cache, dalvik cache, data and system from advanced wipe menu. After that, you should put in queue rom (which you are installing in zip format), then gapps(not all rom's need gapps, read install description for current rom) and custom kernel (not necessarily). After you just swipe on menu to proceed with installation and thats it
marko207 said:
You need custom recovery installed (twrp or cwm). I have twrp. You need from recovery, for example twrp, wipe cache, dalvik cache, data and system from advanced wipe menu. After that, you should put in queue rom (which you are installing in zip format), then gapps(not all rom's need gapps, read install description for current rom) and custom kernel (not necessarily). After you just swipe on menu to proceed with installation and thats it
Click to expand...
Click to collapse
Make sure yu don't wipe "sdcard data" (there's a difference in System Data and SDCard Data). Marco207 mentioned that yu will have to wipe System Data. Rest yu may wipe anything, in fact, everything in case yu want a whole fresh ROM.
I know I saw this process in a recent thread but I've misplaced it. If anyone can point me to it, I would be grateful.
I want to clean flash CM 13 on my OP3.
From what I remember, I'm supposed to store the CM 13 zip file and gapps file in the SD Card folder. Is that truly correct? The OP3 doesn't have an SD Card though I did find a folder.
If I do a factory reset and wipe everything, won't that folder also get wiped? Then how would I install the ROM from the phone?
Sorry, I know this is a straightforward process for many of you, and dirty flashing is easy. But I think a clean flash is better and I'd rather not guess and end up with a bricked phone I have to fuss with.
Again, I know this exact process is in a thread somewhere but I can't find it.
the phone storage is /sdcard/
u can use something like ES File Explorer and create a folder called CM13 or whatever u want
u do have ur bootloader unlocked and twrp installed, correct?
yes u will just the get cm zip file and put it in a folder (ex. /sdcard/CM13/)
i put the gapps in the same folder
create a nandroid backup
wipe/advance wipe - wipe caches/data/system !!!!Do NOT WIPE - INTERNAL STORAGE OR OTG!!!
then flash cm zip and gapps
Hi, thank you. Yes, bootloader unlocked, twrp installed and I've done it in the past on a different phone but couldn't sort out clean flashing from dirty flashing. I've done it correctly in the past, and it's also gone very wrong for me. I think I mistakenly wiped internal storage once and that was a disaster.
Somewhere I've also read about a factory reset through trwp.
I don't need to do that, or wiping caches/data/system is the same thing?
.
digger16309 said:
Hi, thank you. Yes, bootloader unlocked, twrp installed and I've done it in the past on a different phone but couldn't sort out clean flashing from dirty flashing. I've done it correctly in the past, and it's also gone very wrong for me. I think I mistakenly wiped internal storage once and that was a disaster.
Somewhere I've also read about a factory reset through trwp.
I don't need to do that, or wiping caches/data/system is the same thing?
.
Click to expand...
Click to collapse
If you wipe internal storage, you will lose the zips for your ROM and GAPPS. You can connect your device and have it recognized on your PC from within TWRP if you do accidentally wipe your internal storage.
Factory reset doesn't wipe the system partition as that would remove your OS. Most Roms will wipe your system partition before it installs itself so generally you don't have to wipe the system partition manually, but it's good practice.
Clean flash = wipe dalvik, cache, data; then install ROM (which will wipe system before it installs, or manually wipe system before the ROM install for good measure).
Dirty flash = flash ROM, then wipe dalvik and cache. The only time you should do this if the ROM you're looking to flash says it can be done (ie. CM nightlies).
Well simply, can it be done ?
I'm currently running 3.2.8 with root & twrp with partitions encrypted.
I want to upgrade to 4.0.1, convert to F2FS, keep root & twrp and still be encrypted.
I've read that a new version "blu spark" of the recovery has been released, is this the key to what i want to do ?
If you could provide a foolprof how to, this would be amazing.
Vitriol_Drinker said:
Well simply, can it be done ?
I'm currently running 3.2.8 with root & twrp with partitions encrypted.
I want to upgrade to 4.0.1, convert to F2FS, keep root & twrp and still be encrypted.
I've read that a new version "blu spark" of the recovery has been released, is this the key to what i want to do ?
If you could provide a foolprof how to, this would be amazing.
Click to expand...
Click to collapse
It cannot.
The switch to F2FS requires wiping of the data partition including internal storage. You might be able to get around this by staying on ext4 when flashing the update, but the newest recovery by eng.stk won't decrypt ext4 from what I've seen in the forums which means you won't be flashing anything afterwards. Also, root won't be kept because it will overwrite the kernel which you'd have to boot back into TWRP decrypted to flash a fix for and so on. Also, f2fs is showing to be much quicker with UFS storage on the OP3/T so you'd be using a slower file system just because you don't want to lose user data. Get a decent backup app, copy your backups to your PC, wipe and install the new OS CLEANLY, put your backups back on internal storage once you are back logged in again, and restore.
tl;dr no.
AlkaliV2 said:
It cannot.
The switch to F2FS requires wiping of the data partition including internal storage. You might be able to get around this by staying on ext4 when flashing the update, but the newest recovery by eng.stk won't decrypt ext4 from what I've seen in the forums which means you won't be flashing anything afterwards. Also, root won't be kept because it will overwrite the kernel which you'd have to boot back into TWRP decrypted to flash a fix for and so on. Also, f2fs is showing to be much quicker with UFS storage on the OP3/T so you'd be using a slower file system just because you don't want to lose user data. Get a decent backup app, copy your backups to your PC, wipe and install the new OS CLEANLY, put your backups back on internal storage once you are back logged in again, and restore.
tl;dr no.
Click to expand...
Click to collapse
I also want to flash OOS 4.0 based on Nougat, but I want to do a clean flash and change the file system to f2fs (I come from OOS 3.2.7 rooted with official TWRP 3.0.2-1).
So, what I have to do is:
1. make backups of files and apps (I will move files and backup apps with Titanium Backup on my PC or a USB stick) and nandroid backup for evenience (move also it on PC)
2. wipe all (with TWRP or adb?)
3. flash OOS 4.0 Nougat (adb?)
4. flash last stable version of Supersu
5. flash latest TWRP by @eng.stk (with adb?)
Is it correct? The only thing that I can't understand is if I have to use adb or TWRP for flashing, I heard that when you flash the full update the recovery will be replaced with the stock one...
Please help me, I'm looking for trying Nougat
let92 said:
I also want to flash OOS 4.0 based on Nougat, but I want to do a clean flash and change the file system to f2fs (I come from OOS 3.2.7 rooted with official TWRP 3.0.2-1).
So, what I have to do is:
1. make backups of files and apps (I will move files and backup apps with Titanium Backup on my PC or a USB stick) and nandroid backup for evenience (move also it on PC)
2. wipe all (with TWRP or adb?)
3. flash OOS 4.0 Nougat (adb?)
4. flash last stable version of Supersu
5. flash latest TWRP by @eng.stk (with adb?)
Is it correct? The only thing that I can't understand is if I have to use adb or TWRP for flashing, I heard that when you flash the full update the recovery will be replaced with the stock one...
Please help me, I'm looking for trying Nougat
Click to expand...
Click to collapse
Use Titanium backup or any app of you choice, then move the backups and any internal storage files to a PC. Go to TWRP. When you go to the Wipe section, choose "change or repair file system" and convert data to F2FS (will wipe all data and even internal storage). Copy SuperSU 2.79 stable and ROM zips, and this TWRP IMG to phone from a PC, then flash 4.0.1 zip, SuperSU, and TWRP, and reboot to recovery. Make sure you can decrypt data then reboot to system. Then move back your internal storage files and backups.
hiredantispammer said:
Use Titanium backup or any app of you choice, then move the backups and any internal storage files to a PC. Go to TWRP. When you go to the Wipe section, choose "change or repair file system" and convert data to F2FS (will wipe all data and even internal storage). Copy SuperSU 2.79 stable and ROM zips, and this TWRP IMG to phone from a PC, then flash 4.0.1 zip, SuperSU, and TWRP, and reboot to recovery. Make sure you can decrypt data then reboot to system. Then move back your internal storage files and backups.
Click to expand...
Click to collapse
Or... unroot your phone, flash the stock recovery (fastboot mode) and update through the official OTA Then flash the recovery and root your device again :good:
hiredantispammer said:
Use Titanium backup or any app of you choice, then move the backups and any internal storage files to a PC. Go to TWRP. When you go to the Wipe section, choose "change or repair file system" and convert data to F2FS (will wipe all data and even internal storage). Copy SuperSU 2.79 stable and ROM zips, and this TWRP IMG to phone from a PC, then flash 4.0.1 zip, SuperSU, and TWRP, and reboot to recovery. Make sure you can decrypt data then reboot to system. Then move back your internal storage files and backups.
Click to expand...
Click to collapse
All right, I'll try this weekend and will post here the result
Viper The Ripper said:
Or... unroot your phone, flash the stock recovery and update through the official OTA Then flash the recovery and root again :good:
Click to expand...
Click to collapse
In order to unroot the phone what do I have to do? Also re-lock the bootloader?
let92 said:
All right, I'll try this weekend and will post here the result
In order to unroot the phone what do I have to do? Also re-lock the bootloader?
Click to expand...
Click to collapse
Flash stock recovery from OP site and flash rom. Don't relock the bootloader. then flash twrp using fastboot and flash supersu. Will require backing up too tho. I tired the method I gave you and it worked well. F2FS is really worth the effort.
hiredantispammer said:
Flash stock recovery from OP site and flash rom. Don't relock the bootloader. then flash twrp using fastboot and flash supersu. Will require backing up too tho. I tired the method I gave you and it worked well. F2FS is really worth the effort.
Click to expand...
Click to collapse
It seems more simple the @Viper The Ripper's method: in that way I only need to flash the stock recovery, boot the phone (I think the phone will boot on OOS 3.2.7, my actual version), then download OTA (using a VPN to Germany because the update hasn't begun in Italy ), factory reset (will the phone keep Nougat or come back to manufacturer Marshmallow version?), flash recovery by @eng.stk and root phone.
Correct?
AlkaliV2 said:
It cannot.
The switch to F2FS requires wiping of the data partition including internal storage. You might be able to get around this by staying on ext4 when flashing the update, but the newest recovery by eng.stk won't decrypt ext4 from what I've seen in the forums which means you won't be flashing anything afterwards. Also, root won't be kept because it will overwrite the kernel which you'd have to boot back into TWRP decrypted to flash a fix for and so on. Also, f2fs is showing to be much quicker with UFS storage on the OP3/T so you'd be using a slower file system just because you don't want to lose user data. Get a decent backup app, copy your backups to your PC, wipe and install the new OS CLEANLY, put your backups back on internal storage once you are back logged in again, and restore.
tl;dr no.
Click to expand...
Click to collapse
So people with full stock unrooted/without twrp have to lose all data when upgrading ?
Viper The Ripper said:
Or... unroot your phone, flash the stock recovery (fastboot mode) and update through the official OTA Then flash the recovery and root your device again :good:
Click to expand...
Click to collapse
Will this work for me ? Applying the OTA won't relock bootloader will it ?
titanium backup that I took on 3.2.8 isn't restoring on 4.0.1. because F2FS maybe? any solution?
sahed01 said:
titanium backup that I took on 3.2.8 isn't restoring on 4.0.1. because F2FS maybe? any solution?
Click to expand...
Click to collapse
What do you mean? Titanium give you an error when you try to restore some apps? Or you don't find the backups on your phone?
let92 said:
What do you mean? Titanium give you an error when you try to restore some apps? Or you don't find the backups on your phone?
Click to expand...
Click to collapse
.
no nothing like that. it's just when I'm restoring any app, it's like titanium backup freezes. *restoring app* for like hours. but nothing actually happens.
Only suggestion that i will give is what worked for me. So here is what i did and successfully upgraded from 3.2.8 to 4.0.1 OOS without losing data and keeping encryption on ext4 /data.
1. Keep full OTA zip, and SuperSU latest in the folder or Stable, whatever you want, and the latest recovery by eng.stk v11.
2. Remove security from your phone (pin/password/fingerprint), and Go to recovery flash v11 recovery by eng and reboot to recovery.
3. Wipe system, cache, and dalvik.
4. Flash full OTA, flash TWRP recovery img again. If on rebooting, you find stock recovery, just flash v11 from fastboot again.
5. Don't reboot into system, reboot into recovery again, flash SuperSU zip and make sure SuperSU flashes properly. You need to read the installation process and determine that it flashed properly.
6. Reboot to system, you will have all of your data safe and the way it was in MM.
7. Be careful, the moment you assign pin/pattern/fingerprint security to your device, TWRP would ask for a pattern in recovery and it won't decrypt your data. (Works fine if you are on f2fs). If you are like me and don't flash zips that oftenly, it's good to go.
I hope this method helps. Be sure to remove security from phone before flashing and rebooting as recovery won't work if you have security applied. It's a cheap workaround but it works nevertheless.
sahed01 said:
.
no nothing like that. it's just when I'm restoring any app, it's like titanium backup freezes. *restoring app* for like hours. but nothing actually happens.
Click to expand...
Click to collapse
Maybe Titanium wants the storage permission even if it doesn't ask for it
Try to give it, delete app cache and restart the phone.
Then try to restore one app.
let92 said:
All right, I'll try this weekend and will post here the result
In order to unroot the phone what do I have to do? Also re-lock the bootloader?
Click to expand...
Click to collapse
Go to Supersu apk and choose the option in settings to unroot completly your phone
---------- Post added at 10:07 PM ---------- Previous post was at 10:05 PM ----------
Vitriol_Drinker said:
So people with full stock unrooted/without twrp have to lose all data when upgrading ?
Will this work for me ? Applying the OTA won't relock bootloader will it ?
Click to expand...
Click to collapse
If you apply the official OTA you won't lose nothig from your current rom
Yes it'll work and nope, applying the OTA won't relock your bootloader :good:
Vitriol_Drinker said:
So people with full stock unrooted/without twrp have to lose all data when upgrading ?
Click to expand...
Click to collapse
People that want F2FS will lose their data converting their filesystems unless they back it up; no method listed in this thread gets around this. All the options listed keeps the users on ext4 because the official OTA does not convert your /data partition to F2FS as shown in the updater script code below from official 4.0.1 full firmware and update file.
Code:
getprop("ro.display.series") == "OnePlus 3" || abort("E3004: This package is for \"OnePlus 3\" devices; this is a \"" + getprop("ro.display.series") + "\".");
show_progress(0.750000, 0);
ui_print("Patching system image unconditionally...");
block_image_update("/dev/block/bootdevice/by-name/system", package_extract_file("system.transfer.list"), "system.new.dat", "system.patch.dat") ||
abort("E1001: Failed to update system image.");
show_progress(0.050000, 10);
show_progress(0.050000, 5);
package_extract_file("boot.img", "/dev/block/bootdevice/by-name/boot");
show_progress(0.200000, 10);
ui_print("Writing static_nvbk image...");
package_extract_file("RADIO/static_nvbk.bin", "/dev/block/bootdevice/by-name/oem_stanvbk");
# ---- radio update tasks ----
ui_print("Patching firmware images...");
ifelse(msm.boot_update("main"), (
package_extract_file("firmware-update/cmnlib64.mbn", "/dev/block/bootdevice/by-name/cmnlib64");
package_extract_file("firmware-update/cmnlib.mbn", "/dev/block/bootdevice/by-name/cmnlib");
package_extract_file("firmware-update/hyp.mbn", "/dev/block/bootdevice/by-name/hyp");
package_extract_file("firmware-update/pmic.elf", "/dev/block/bootdevice/by-name/pmic");
package_extract_file("firmware-update/tz.mbn", "/dev/block/bootdevice/by-name/tz");
package_extract_file("firmware-update/emmc_appsboot.mbn", "/dev/block/bootdevice/by-name/aboot");
package_extract_file("firmware-update/rpm.mbn", "/dev/block/bootdevice/by-name/rpm");
package_extract_file("firmware-update/devcfg.mbn", "/dev/block/bootdevice/by-name/devcfg");
package_extract_file("firmware-update/xbl.elf", "/dev/block/bootdevice/by-name/xbl");
package_extract_file("firmware-update/keymaster.mbn", "/dev/block/bootdevice/by-name/keymaster");
), "");
ifelse(msm.boot_update("backup"), (
package_extract_file("firmware-update/cmnlib64.mbn", "/dev/block/bootdevice/by-name/cmnlib64bak");
package_extract_file("firmware-update/cmnlib.mbn", "/dev/block/bootdevice/by-name/cmnlibbak");
package_extract_file("firmware-update/hyp.mbn", "/dev/block/bootdevice/by-name/hypbak");
package_extract_file("firmware-update/tz.mbn", "/dev/block/bootdevice/by-name/tzbak");
package_extract_file("firmware-update/emmc_appsboot.mbn", "/dev/block/bootdevice/by-name/abootbak");
package_extract_file("firmware-update/rpm.mbn", "/dev/block/bootdevice/by-name/rpmbak");
package_extract_file("firmware-update/devcfg.mbn", "/dev/block/bootdevice/by-name/devcfgbak");
package_extract_file("firmware-update/xbl.elf", "/dev/block/bootdevice/by-name/xblbak");
package_extract_file("firmware-update/keymaster.mbn", "/dev/block/bootdevice/by-name/keymasterbak");
), "");
msm.boot_update("finalize");
package_extract_file("firmware-update/NON-HLOS.bin", "/dev/block/bootdevice/by-name/modem");
package_extract_file("firmware-update/adspso.bin", "/dev/block/bootdevice/by-name/dsp");
package_extract_file("firmware-update/BTFM.bin", "/dev/block/bootdevice/by-name/bluetooth");
set_progress(1.000000);
You can see that all it does it overwrite the system partition with the new changes, writes the radio file, and flashes the extra firmware to bring you up to speed with nougat. If you want to do this right and be on F2FS you have to do it manually.
Viper The Ripper said:
Go to Supersu apk and choose the option in settings to unroot completly your phone
Click to expand...
Click to collapse
Thank you! I'll try your method so!
hiredantispammer said:
Use Titanium backup or any app of you choice, then move the backups and any internal storage files to a PC. Go to TWRP. When you go to the Wipe section, choose "change or repair file system" and convert data to F2FS (will wipe all data and even internal storage). Copy SuperSU 2.79 stable and ROM zips, and this TWRP IMG to phone from a PC, then flash 4.0.1 zip, SuperSU, and TWRP, and reboot to recovery. Make sure you can decrypt data then reboot to system. Then move back your internal storage files and backups.
Click to expand...
Click to collapse
Sounds like good plan, but I have one question. Do you need to disable security (fingerprint, patern or code) on forehand to make sure the data can be decrypted?
I've managed to do all this and end up wit 4.0.1 with F2FS and no encryption. If I encrypt the phone, it changes the format of the data partition and TWRP won't decrypt it. If I understand this thread, this is to be expected. There is no way to end up with encrypted F2FS that TWRP can decrypt?
Revolised123 said:
Sounds like good plan, but I have one question. Do you need to disable security (fingerprint, patern or code) on forehand to make sure the data can be decrypted?
Click to expand...
Click to collapse
I didn't. Just boot back to recovery after flashing everything. With this TWRP data can be decrypted.
Can I remove encryption after I have flashed a ROM without formatting data. How to permanently decrypt data? After Decryption, can I switch between ROMs without formatting data?
No, for first time decrypt you need to format data, because the complete data partition is encrypted.
So you need to backup everything of phone memory and backup your apps and data with "migrate"
After flashing rom and other zips, you flash "Disable DM Verity Force Encrypt"
Dirty flash without wipes is possible, but you need to flash Gapps (and Magisk) too. Your user apps and data are still present.
Clean flash after this is imho also possible with only wipe data (not format).
After (dirty or clean) flashing rom, gapps, magisk other zips, flash DM verity xxxx again.
Fyi
Dirty flash I have done this way already, but clean flash this way I haven't tried myself, so my advice is to backup your internal memory just in case or wait for a confirmation from someone else.
Elinx said:
No, for first time decrypt you need to format data, because everything is encrypted.
After flashing rom and all other zips you flash "Disable DM Verity Force Encrypt".
Dirty flash without wipes is possible, but you need to flash Gapps (and Magisk) too
imho switch between different rom's is also possible with only wipe data (not format)
After (dirty) flashing (new) rom, gapps, magisk, flash DM verity xxxx again.
Click to expand...
Click to collapse
So, we can't decrypt the data. What happens if we remove screen lock while the data is encrypted? Then how is the data encrypted? (Using some ROM Keys without lock...)
I think it is difficult to backup everything, transfer to external device, format, change ROM, again restore all data.
Also can I enable encryption again while using the ROM without formatting?
devaponnadsm said:
So, we can't decrypt the data. What happens if we remove screen lock while the data is encrypted? Then how is the data encrypted? (Using some ROM Keys without lock...)
I think it is difficult to backup everything, transfer to external device, format, change ROM, again restore all data.
Also can I enable encryption again while using the ROM without formatting?
Click to expand...
Click to collapse
Before I start flashing I always have removed all the locks to prevent such a lock that format data is the only choice. The "how and why" you ask for, I don't know
Backup everything and restore all is very time consuming, user apps and data with migrate isn't that bad.
I don't want to encrypt anymore so never had done this, but I think you don't need to format if you run it from the Android security settings.
you can remove screenlock with the zip i attached
do a full twrp backup, then do all the experiment you ask for to get answers , then restore ...
First of all,
This is just an experiment. Don't try this without backing up your data. I am not responsible for any data loss.
I found a way to switch ROM without fornatting data and also without installing any addon like Disable DM-Verity.
First of all remove the lock screen in your security option. Change to none. Keep everything ready in your storage. Go to TWRP. Wipe System, Vendor, Cache, Dalvik Cache. Go immediately and install ROM and Gapps (Option). Reboot into systen immediately.
After wiping data, make sure that you don't switch off your phone or reboot it again. Boot directly into ROM after flashing. It will not work if you flash Magisk, because the phone reboots automatically during first boot. Flash Magisk only after first boot. It is working for me unless during the first boot, the phone is rebooted twice.
Again,
This is just an experiment. Don't try this without backing up your data. I am not responsible for any data loss.
devaponnadsm said:
First of all,
This is just an experiment. Don't try this without backing up your data. I am not responsible for any data loss.
I found a way to switch ROM without fornatting data and also without installing any addon like Disable DM-Verity.
First of all remove the lock screen in your security option. Change to none. Keep everything ready in your storage. Go to TWRP. Wipe System, Vendor, Cache, Dalvik Cache. Go immediately and install ROM and Gapps (Option). Reboot into systen immediately.
After wiping data, make sure that you don't switch off your phone or reboot it again. Boot directly into ROM after flashing. It will not work if you flash Magisk, because the phone reboots automatically during first boot. Flash Magisk only after first boot. It is working for me unless during the first boot, the phone is rebooted twice.
Again,
This is just an experiment. Don't try this without backing up your data. I am not responsible for any data loss.
Click to expand...
Click to collapse
why you replay to me ?
i'm not the one asking :silly:
Hello guys. Hope u doing well
so i have a problem with decryption on my redmi note 8. and i have already flash into lineageOS and i lost acess to my internal storage even i cant install Gapps and also i can't do the Disable DM Verity Force Encrypt.
Howerver i tried the method
1. reboot the phone and enter recovery mode
2. typing the pin and TWRP trying to decrypte the phone and it's does it well
3. i have a temporary access to the internet storage.
4. i have made a data wipe and reboot to reovery after that i formated data, vender, and all the requied segment but i still cant wipe the internet storage
5. error message. error:1 no access to /data/...
6. i tries to Flash allso the Disable DM Verity Force Encrypt but same error.
7. and when i try to instal/flash LineagOS it pass without any problem
pls any body can help me.
seveneigsh said:
Hello guys. Hope u doing well
so i have a problem with decryption on my redmi note 8. and i have already flash into lineageOS and i lost acess to my internal storage even i cant install Gapps and also i can't do the Disable DM Verity Force Encrypt.
Howerver i tried the method
1. reboot the phone and enter recovery mode
2. typing the pin and TWRP trying to decrypte the phone and it's does it well
3. i have a temporary access to the internet storage.
4. i have made a data wipe and reboot to reovery after that i formated data, vender, and all the requied segment but i still cant wipe the internet storage
5. error message. error:1 no access to /data/...
6. i tries to Flash allso the Disable DM Verity Force Encrypt but same error.
7. and when i try to instal/flash LineagOS it pass without any problem
pls any body can help me.
Click to expand...
Click to collapse
re download DFE and try a clean flash