Hi 2 all!
Before somebody claims - I read and searched the threads but I was not able to flash a new rom.
My envoirment:
Win 7 X86
HTC Desire (rooted)
8 GB Memory Card (I copied the new rom in the root directory and named it update.zip)
I tried rom manager (the non-paid version):
I don't know which menu (after my device rebooted) should I take?
applying sdcard update.zip?? (I selected this, bus no new rom..)
I also tried the fake flash method:
Error Message: signature verification failed.
Now, please can anyone tell me how to flash to a new rom?
br,
Chris
Edit: Solved: The zip file was corrupt
Is your handset branded? What rom are you trying to flash. Have you rooted your device? Because it needs to be rooted to flash 99% of the roms available here.
..no, its not branded; its also rooted.
So what rom are you trying to flash? You should be able to flash one if your handset is rooted.
If you use fake flash don't rename it but put it on your sd card root. Then in the menu go to flash zip from sd then choose the rom. Just before you flash make sure to select wipe data, cache etc.
why did u rename the rom?...once in the custom recovery it should not matter what the rom is called...from the menu u just select flash zip from SD then select the rom from the list
Dwayne01 said:
why did u rename the rom?...once in the custom recovery it should not matter what the rom is called...from the menu u just select flash zip from SD then select the rom from the list
Click to expand...
Click to collapse
...somewhere I read to rename the rom the update.zip.
Now I am following this link: http://theunlockr.com/2010/06/07/how-to-load-a-custom-rom-on-the-htc-desire/
I am trying the rom: http://forum.xda-developers.com/showthread.php?t=705606
Will whipe date/whipe cache clear my memory card?
Will any other action clear my memory card?
br,
Chris
Ok so that rom should be fine. Do not rename it.
Wiping cache/data etc will only wipe data form the handset. All your memory card will be still intact. Only repartitioning the card will wipe it so back up any data first if you ever plan on doing that.
If the error is signature verification failed, re-sign the ROM.
http://forum.xda-developers.com/showthread.php?t=682972
Here is friends Deodex Stock 10.5.A.0.230 To Bootloads Locked or Unlocked has CMW, with corrections Lags Settings Scrolling with Super mod for installing APKs Modification or third-party themes!
Installation Method!
1º Download and copy the zip file to the internal memory
2º Turn off your device, go into recovery mode!
3º Flash Zip
4º Wipe Dalvik Cache and Cache
5º After Installation do the Root
(Download in Google Driver)
- To Root Method !
- Download lastest SuperSu to sdcard
- flash SuperSU .zip file in Recovery
- Restart and enjoy kk Rom without lags And Root .
Credits :
And Especially @Serar By the mod and corrections
@RyokoN for the amazing tool Kamome
Sorry my Bad English !! I br o/
If I helped you thank !!
Awesome!!!
Thank you!!
Could you do this for C6502 user also? Btw, great work...
Ammo90 said:
Could you do this for C6502 user also? Btw, great work...
Click to expand...
Click to collapse
Also works in 6502 !
could installation and root be performed in one after another operation, or installation first and after first reboot to return to recovery and do rooting?
why installation file should be put into internal storage not to SD?
thx
rfg13 said:
could installation and root be performed in one after another operation, or installation first and after first reboot to return to recovery and do rooting?
why installation file should be put into internal storage not to SD?
thx
Click to expand...
Click to collapse
It can be done one after the other , Put in into Internal Storage or Sd !!
xtremepredador said:
It can be done one after the other , Put in into Internal Storage or Sd !!
Click to expand...
Click to collapse
thanks.
In what folder I could add my apps, like titanium, file manager etc, to install it at the same time (system\app or system\priv-app)?
rfg13 said:
thanks.
In what folder I could add my apps, like titanium, file manager etc, to install it at the same time (system\app or system\priv-app)?
Click to expand...
Click to collapse
In System\priv-app !!
I've been searching for this but i'm limited to 8 thanks per day.
This post is to remind me to do it tommorow
TWRP
Can I flash with TWRP? thanks
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.
I am on lineage-14.1-20180110-nightly-hammerhead
Obviously using Nexus 5 with latest FrancoKernal & Rooted with LineageOS SU - Add on
Also Latest TWRP 3.2.1
It Passes SafeyNET.
SO
My questions are :
1> Will The Automatic Updater Delete the Data (Photos, Music, etc ) ?
2> Will It change the settings ( App defaults, Ringtones, Notification settings, etc ) ? Using Google Apps n Services.
3> Will it remove Root ?
4> Will it remove the custom Kernal ( Franco in this case ) ?
5> Will it affect the SafetyNet Status of my device ?
Please don't suggest me to try n find out for myself.
Setting up the phone from scratch is what i am actively trying to Avoid. It works perfectly as of now.
Thanks in Advance for any helpful Info.
As far I know:
0. The LOS Updater downloads just the new build and boots into your recovery where you have to flash it. (not like the stock OTA updates)
1. No. (Except the Developer says you have to wipe data obviously.)
The new build should be installed in the system partition. Your "private data" (or internal SD) are located at data/media..
2.+3. Not necessary, but its recommended (I do it every time). here more
4. I don't use a custom kernel, so I don*t know for sure, but acording to this question you have to flash the kernel again.
If you want to test a new build, just do a full backup in your recovery. Assuming that u'r using TWRP us should know that a full backup in TWRP doesn't included your internal SD! Backup it separately! here more
If you wipe your data partition your "private data" (or internal SD) should be wiped too.
A factory reset excludes this!
Hoping that i dont made any mistakes :laugh:
chrisrevoltes said:
As far I know:
0. The LOS Updater downloads just the new build and boots into your recovery where you have to flash it. (not like the stock OTA updates)
1. No. (Except the Developer says you have to wipe data obviously.)
The new build should be installed in the system partition. Your "private data" (or internal SD) are located at data/media..
2.+3. Not necessary, but its recommended (I do it every time). here more
4. I don't use a custom kernel, so I don*t know for sure, but acording to this question you have to flash the kernel again.
If you want to test a new build, just do a full backup in your recovery. Assuming that u'r using TWRP us should know that a full backup in TWRP doesn't included your internal SD! Backup it separately! here more
If you wipe your data partition your "private data" (or internal SD) should be wiped too.
A factory reset excludes this!
Hoping that i dont made any mistakes :laugh:
Click to expand...
Click to collapse
Thanks for the info
mrinal46 said:
Thanks for the info
Click to expand...
Click to collapse
0 my devices perform automatic updates in twrp.
2 your settings survive. Installed gapps survive. No need to update in twrp they are self updating
3 addonsu survives.
5 yes, in cases magisk or SuperSU get removed by the update.
Hi,
I was following this guide to finally update my redmi note 8 to MIUI global 11.0.12.00 (I don't remeber which version exactly I had before). I flashed the zip with TWRP and everything went fine, but I cannot boot now, I always go into TWRP when rebooting.
What could be causing this? I was rooted before, through magisk, and I did not reflash it. Would that help?
Any help appreciated
Edit: I installed magisk through TWRP, which was successful but I still wasn't able to boot. I then reflashed the OTA update and immediately installed magisk, which also did not work.
I read that flashing the stock recovery might help, but I don't know what to try next
Edit: I extracted boot.img from the OTA zip and ran fastboot boot boot.img, still got sent to TWRP
Edit: I flashed the stock recovery, now instead of booting into TWRP I boot into the MIUI recovery, which I suppose makes sense. I really wish there's something I can do without wiping my data.
I've reflashed twrp for now, and I'm gonna sleep for today. Hopefully I have some replies by the morning. Next I'm planning to flash the latest rom directly from en.miui.com (11.0.11.0)
Thanks
Also, in case I have to do a factory reset, which partitions can I then restore with TWRP (If I back them up now)? Most of all I really want to keep my app data. Am I forgetting anything else that's important?
try this...
1.flash dtbo.img
2.flash dm-verity
I hope it works
oindividuo said:
Hi
Click to expand...
Click to collapse
if you were decrypted you have to flash DFE again (Disable_Dm-Verity_ForceEncrypt_03.04.2020)
if not backup your data partition and reset sys config by deleting (data/system + data/user_de/0/com.android.settings + com.androidsystemui + cache + dalvik)
if it still dosn't work make a copy of the folder (data/data/your app name) wipe data and restore the data of your app after instaling it and hope it will work
Baim alif said:
try this...
1.flash dtbo.img
2.flash dm-verity
I hope it works
Click to expand...
Click to collapse
Just to clarify, dtbo.img is the one inside the OTA zip and dm-verity can be the Disable_Dm-Verity-09.02.2018.zip file found here? https://miui.blog/any-devices/dm-verity-opt-encrypt-force-encryption-disabler-xiaomi/
loopypalm said:
if you were decrypted you have to flash DFE again (Disable_Dm-Verity_ForceEncrypt_03.04.2020)
if not backup your data partition and reset sys config by deleting (data/system + data/user_de/0/com.android.settings + com.androidsystemui + cache + dalvik)
if it still dosn't work make a copy of the folder (data/data/your app name) wipe data and restore the data of your app after instaling it and hope it will work
Click to expand...
Click to collapse
I'm not sure if I was decrypted, I never flashed DFE before. So I should try the second set of instructions, right?
Also, I meant the data from all my apps, but hopefully I can just copy the full /data/data folder and restore it the same way
Baim alif said:
[Deprecated] Universal DM-Verity, ForceEncrypt, Disk Quota Disabler [11/2/2020]
Hi all! For the past couple of months, I've been looking into making a more universal solution to disable dm-verity and forceencrypt. Needing to take different zips, modify them for different devices, and then cross your fingers when you switch...
forum.xda-developers.com
Click to expand...
Click to collapse
use this bro
oindividuo said:
I'm not sure if I was decrypted, I never flashed DFE before. So I should try the second set of instructions, right?
Also, I meant the data from all my apps, but hopefully I can just copy the full /data/data folder and restore it the same way
Click to expand...
Click to collapse
if you never flashed dfe before don't do it
you will have to format data (not wipe) and it will erase also internal storage
follow the 2nd set ...
make a bkp of 'data' partition (you can use 7zip to explore it) and restore app data but that's not garanteed
Baim alif said:
use this bro
Click to expand...
Click to collapse
So first I flash dtbo with fastboot (fastboot flash dtbo dtbo.img?), then boot into twrp, then flash dm-verity?
Thank you
good luck bro
Baim alif said:
good luck bro
Click to expand...
Click to collapse
Now I'm not being redirected to TWRP, but I'm in a bootloop :/
loopypalm said:
if you never flashed dfe before don't do it
you will have to format data (not wipe) and it will erase also internal storage
follow the 2nd set ...
make a bkp of 'data' partition (you can use 7zip to explore it) and restore app data but that's not garanteed
Click to expand...
Click to collapse
Alright I can boot now, I'm restoring the automatic backup from google drive, though I don't think it contains app data, right? Anyway, this is much more than I was expecting this morning. I will make a new full twrp backup when it finishes and then attempt to restore the old /data/data backup and hope for the best. I still need magisk too, but that's honestly not a priority rn
Thank you very much for your guidance
oindividuo said:
Alright I can boot now, I'm restoring the automatic backup from google drive, though I don't think it contains app data, right? Anyway, this is much more than I was expecting this morning. I will make a new full twrp backup when it finishes and then attempt to restore the old /data/data backup and hope for the best. I still need magisk too, but that's honestly not a priority rn
Thank you very much for your guidance
Click to expand...
Click to collapse
you can't browse data folder without root
you can do it with the recovery file manager but it will take too much time
orangefox file manager is better if you don't want root ...