Related
This is regarding a recently bought tablet Note 8. The current usage of /system partition is at above 75%. I have been trying to wipe/delete all system data in an attempt to have a 'fresh' OS once I install new stock ROM. In CWM recovery, I have even tried to format system partition (in addition to normal data reset, cache wipe and delvek cache wipe).
I installed the new stock ROM 4.4.2 in Download mode. Afterwards I checked and my system partition was still above 75% full. I do understand that system partition is normally read only. I am trying to work out if there is there any way where I can flash the stock ROM whilst completely removing the current system files.
Please offer any guidance or advice regarding this matter. Thanks!
Possible? Yes. Necessary? No.
The installation script for a ROM will almost always format the system partition before setting it up with the new ROM files, unless the developer is doing some special testing and you would know if that is the case.
ramjet73
Yes I think most custom ROMs would wipe system partition too. Though I want to install the stock ROM of Android 4.4.2. I have flashed the ROM about four times now, everytime trying different settings such as wipe/format system drive.
But I always end up with /system drive same size as before.
Thanks for the reply ramjet73.
S2 user said:
Yes I think most custom ROMs would wipe system partition too. Though I want to install the stock ROM of Android 4.4.2. I have flashed the ROM about four times now, everytime trying different settings such as wipe/format system drive.
But I always end up with /system drive same size as before.
Thanks for the reply ramjet73.
Click to expand...
Click to collapse
Depending on how you flash the stock ROM, Odin will flash a .img file to the system partition and completely replace its contents or an updater-script in a stock ROM zip file will format it and then copy all the included /system files to the empty partition.
In either case you cannot control what goes into the initial configuration of the system partition, only delete things that you don't need after it is flashed, unless you flash from a stock ROM zip file and delete items from that before you flash it.
There are scripting tools that can help with ROM "slimming" but I don't know if any are available for the Note 8.0 or not.
ramjet73
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.
Hello
This is a TWRP recovery for Motorola Moto G5 Cedric for arm64 ROMS, with encryption support, backup support for persist and efs partitions and possibility to flash/backup logo boot image.
I need review and test, especially for the storage decryption and/with LineageOS fingers-crossed. I was able to test it on my device (XT1676 3Go).
It is my first ROM so it is possible that there are bugs.
- Be carefull, there are problems with the backup system :
Just wish to come here and tell you guys to AVOID using this recovery, it seems to have a serious bug.
I just backed up my entire data partition (and enable digest verification) and restored the partition afterwards and the phone didn't boot.
Then I tried restoring it with verification enabled and the hashes didn't match.
In other words, for some reason, the generated backup was corrupt.
- freeZbies
Click to expand...
Click to collapse
Changelog
TWRP 3.2.3-2
add sdcardfs
add FB2PNG for screenshot
fix brightness path and define it at 160
fix time zone error
fix incorrect lun path for USB
You can download it here :
TWRP 3.2.3-2 (md5: 0dbd3846593ae907d3391596876c1f35)
TWRP 3.2.3-1 (md5: 404b54d27653b5a1ec5b59023f53d3cb)
TWRP 3.2.3-0
Sources :
https://github.com/Akipe/twrp_android_device_motorola_cedric
https://github.com/Akipe/twrp_android_device_motorola_msm8937-common
Manifest :
https://github.com/Akipe/android_development_manifest
Would it be possible for you to compile a version capable of backing up all partition, including persist and efs? see here: https://forum.xda-developers.com/showpost.php?p=78695191&postcount=95
Guttergorm said:
Would it be possible for you to compile a version capable of backing up all partition, including persist and efs? see here: https://forum.xda-developers.com/showpost.php?p=78695191&postcount=95
Click to expand...
Click to collapse
Hi!
Sorry for the delay, I added the functions you wanted. Can you try and tell me if everything is ok?
Hi,
tested your recovery image with my installed LOS 15.1. (32bit) Device: XT1676 16GB P5
- storage decryption: OK
- backup support for persist and efs partitions and possibility to flash/backup logo boot image: OK
nice work, thx for you effort
mikefive said:
Hi,
tested your recovery image with my installed LOS 15.1. (32bit) Device: XT1676 16GB P5
- storage decryption: OK
- backup support for persist and efs partitions and possibility to flash/backup logo boot image: OK
nice work, thx for you effort
Click to expand...
Click to collapse
Thx for testing :good:
Akipe can u help us to build treble rom for cedric???
Works nicely, thanks.
I just tested it and it decrypts my internal storage normally.
Just wish to come here and tell you guys to AVOID using this recovery, it seems to have a serious bug.
I just backed up my entire data partition (and enable digest verification) and restored the partition afterwards and the phone didn't boot.
Then I tried restoring it with verification enabled and the hashes didn't match.
In other words, for some reason, the generated backup was corrupt.
Of course I could make another test but it'll take just a long time to backup everything again, so if anyone wants to test it, feel free, but beware, you could have a hell of a headache finding out the backups you made were useless.
freeZbies said:
Just wish to come here and tell you guys to AVOID using this recovery, it seems to have a serious bug.
I just backed up my entire data partition (and enable digest verification) and restored the partition afterwards and the phone didn't boot.
Then I tried restoring it with verification enabled and the hashes didn't match.
In other words, for some reason, the generated backup was corrupt.
Of course I could make another test but it'll take just a long time to backup everything again, so if anyone wants to test it, feel free, but beware, you could have a hell of a headache finding out the backups you made were useless.
Click to expand...
Click to collapse
Hello ! Thank you for your test and sorry for your backup
I will test the backup system and add a warning
freeZbies said:
Just wish to come here and tell you guys to AVOID using this recovery, it seems to have a serious bug.
I just backed up my entire data partition (and enable digest verification) and restored the partition afterwards and the phone didn't boot.
Then I tried restoring it with verification enabled and the hashes didn't match.
In other words, for some reason, the generated backup was corrupt.
Of course I could make another test but it'll take just a long time to backup everything again, so if anyone wants to test it, feel free, but beware, you could have a hell of a headache finding out the backups you made were useless.
Click to expand...
Click to collapse
I have backup up data partition from my TWRP, reboot one time to recovery, restore the data backup with digest verification, and reboot to LineageOS, with no problem (my rom is LineageOS 16.0 without encryption.)
I think there may be 2 errors (maybe more) :
1) There is a problem with data restore when encryption is enable. I can not test this scenario for now, but i will do it as soon as i can
2) Was your backup stored on your SD card? if so, it is possible that the sd card may be damaged, because it is too old or of poor quality (more info here : https://photo.stackexchange.com/questions/40489/what-causes-an-sd-card-to-go-corrupt )
if you have other information or other ideas, do not hesitate to share it!
if people want to participate, try to save the data partition and restore it, especially with the encrypted partition :good::good:
be careful, make a backup of your data before test
Akipe said:
I have backup up data partition from my TWRP, reboot one time to recovery, restore the data backup with digest verification, and reboot to LineageOS, with no problem (my rom is LineageOS 16.0 without encryption.)
I think there may be 2 errors (maybe more) :
1) There is a problem with data restore when encryption is enable. I can not test this scenario for now, but i will do it as soon as i can
2) Was your backup stored on your SD card? if so, it is possible that the sd card may be damaged, because it is too old or of poor quality (more info here : https://photo.stackexchange.com/questions/40489/what-causes-an-sd-card-to-go-corrupt )
if you have other information or other ideas, do not hesitate to share it!
if people want to participate, try to save the data partition and restore it, especially with the encrypted partition :good::good:
be careful, make a backup of your data before test
Click to expand...
Click to collapse
I agree it may be any of the 2 problems.
My data partition was indeed encrypted, and yes, my SD card is not what I would call genuine, though I think that's not the case since the card is relatively new and I never had any problem related to data corruption.
Anyways, thanks for your effort.
freeZbies said:
I agree it may be any of the 2 problems.
My data partition was indeed encrypted, and yes, my SD card is not what I would call genuine, though I think that's not the case since the card is relatively new and I never had any problem related to data corruption.
Anyways, thanks for your effort.
Click to expand...
Click to collapse
I have test backup the data partition with encryption on LineageOS 16 (arm64), backup and restore work without issue
What ROM did you use when you made the backup, and with what arch (arm or arm64) ?
Akipe said:
I have test backup the data partition with encryption on LineageOS 16 (arm64), backup and restore work without issue
What ROM did you use when you made the backup, and with what arch (arm or arm64) ?
Click to expand...
Click to collapse
I was on stock oreo, so its arm, not arm64
freeZbies said:
I was on stock oreo, so its arm, not arm64
Click to expand...
Click to collapse
Oh ok, there are chances that's why the backup did not work .
This recovery is mainly intended for arm64 rom !
Just wanted to say that everything worked well for me in backing up and restoring the OmniROM, on both decrypted and encrypted phone.
Thanks @Akipe for the great job
Can you update it to latest TWRP?
Sent from my cedric using XDA Labs
forgot password to decrypt??
hi,
first, sorry if this is the wrong place to post this. right now, when i install the 64 bit twrp i am asked for a password to decrypt my data. i have tried some passwords i think i would have used, but those don't work and i get a message also saying that the default password didn't work - i haven't typed a default password, though, so i assume there is a default one that twrp tries automatically. in the past, i did try a rom requiring 64 bit twrp and i am guessing i set a password other then the default to encrypt/decrypt, but i went back to stock without issues so have not thought about the password and cannot remember what i would have used. i wanted to try dotos on my phone, which i assume requires 64 twrp because i got error 255 when i tried to flash without twrp64. so i installed twrp64 but cannot get any further. so here are my questions:
is there any way to decrypt the data if i forgot my password?
if not, can i format the data while encrypted to install the new rom? if i can do that, what should i back up? i have pictures and other necessary files backed up, so i am not worried about completely wiping the phone to start over. however, should i back anything else up before formatting? do i need to worry about losing imei or losing any partitions that would make phone inoperable or not have any signal? should i back up with twrp64 or the non-64 bit twrp currently installed? any help or point in the right direction is greatly appreciated.
tia,
nurvus
nurvus said:
hi,
first, sorry if this is the wrong place to post this. right now, when i install the 64 bit twrp i am asked for a password to decrypt my data. i have tried some passwords i think i would have used, but those don't work and i get a message also saying that the default password didn't work - i haven't typed a default password, though, so i assume there is a default one that twrp tries automatically. in the past, i did try a rom requiring 64 bit twrp and i am guessing i set a password other then the default to encrypt/decrypt, but i went back to stock without issues so have not thought about the password and cannot remember what i would have used. i wanted to try dotos on my phone, which i assume requires 64 twrp because i got error 255 when i tried to flash without twrp64. so i installed twrp64 but cannot get any further. so here are my questions:
is there any way to decrypt the data if i forgot my password?
if not, can i format the data while encrypted to install the new rom? if i can do that, what should i back up? i have pictures and other necessary files backed up, so i am not worried about completely wiping the phone to start over. however, should i back anything else up before formatting? do i need to worry about losing imei or losing any partitions that would make phone inoperable or not have any signal? should i back up with twrp64 or the non-64 bit twrp currently installed? any help or point in the right direction is greatly appreciated.
tia,
nurvus
Click to expand...
Click to collapse
You need to format data
Push back button when it asks for decrypt
Goto wipe and select the option on the right to format data
This will erase everything on internal storage so copy any files you want to keep to pc first (pictures music etc)
Once formatted data restart back to recovery to check encryption has been removed and data partition is mountable
TWRP backups do not save personal files (pictures music etc) They only backup data and system files (and other named partitions)
Once you have flashed a new rom you can encrypt again if you want to via the security settings menu in phone settings
TheFixItMan said:
You need to format data
Push back button when it asks for decrypt
Goto wipe and select the option on the right to format data
This will erase everything on internal storage so copy any files you want to keep to pc first (pictures music etc)
Once formatted data restart back to recovery to check encryption has been removed and data partition is mountable
TWRP backups do not save personal files (pictures music etc) They only backup data and system files (and other named partitions)
Once you have flashed a new rom you can encrypt again if you want to via the security settings menu in phone settings
Click to expand...
Click to collapse
thanks for the quick response! and just for clarification and for me to be sure, should i back up any partitions before formatting? right now i have 32 (or non64 i guess) bit twrp installed, stock rom and bootloader unlocked. do i need to take any precautions with data/imei/signal before reinstalling twrp64, formatting data, and installing a new rom? if it matters any i have the international version of the moto g5. thanks again!!
nurvus
nurvus said:
thanks for the quick response! and just for clarification and for me to be sure, should i back up any partitions before formatting? right now i have 32 (or non64 i guess) bit twrp installed, stock rom and bootloader unlocked. do i need to take any precautions with data/imei/signal before reinstalling twrp64, formatting data, and installing a new rom? if it matters any i have the international version of the moto g5. thanks again!!
nurvus
Click to expand...
Click to collapse
Backup efs if you want to preserve your current emei state or need to restore it in future
EDIT 3-11-2019: Know that RSDlite-ing a stock ROM will give you an encrypted system.
EDIT Never mind - I solved it though I don't know how - it kept telling me that it couldn't mount Data. Took 2 RSDlite's of 8.0.0 and a few fastboots of 3.2.3 . at one point I tried a adv wipe of everything except internal and SDcard, and LO it formatted the Data . So then I could just nandroid restore my previous one (Alberto 9 64bit)
I'd love to know how to avoid it, though.
was on alberto 9
1.82 bootloader
did full clean wipe and installed this
https://forum.xda-developers.com/moto-z-play/development/rom-aosip-9-0-beta-t3859578
on first boot it asked for password which of course I didn't have.
back to twrp but when I try anything it says busy.
RSD lite rafikowy's 8.0.0, but it auto encrypts on first boot.
Help!
Thanks!
I tried about "ten times" with rafikowsky rom, I did all tricks mentioned in xda and it encrypts each time I boot it. No way to get rid of encryption
hamudistan said:
I tried about "ten times" with rafikowsky rom, I did all tricks mentioned in xda and it encrypts each time I boot it. No way to get rid of encryption
Click to expand...
Click to collapse
yeah.
each time I rsd'ed 8.0.0, I then flashed twrp 3.2.3 (twice) and booted to twrp and tried to format Data. The problem I kept having was that Data wouldn't show as mounted. Then at some point in there I clicked on mount (data was checked), backed out,
clicked on wipe, advanced and checked dalvik/art,data,system, and slid the slider and NOW it wiped AND formatted. Don't know why.
You have to format Data (in TWRP) to get rid of encryption.
Then I just restored a nandroid that I took before I started playing yesterday and voila, back where I was.
Yeah I know.I somehow managed to mount and format data and when I boot to system afterwards - it starts encrypting again.
hamudistan said:
Yeah I know.I somehow managed to mount and format data and when I boot to system afterwards - it starts encrypting again.
Click to expand...
Click to collapse
Now THAT's interesting.
In my case I
rsdlite'ed 8.0.0
flash twrp from laptop(I do it twice in a row)
boot to twrp
managed to format data somehow,
immediately nandroided a non encrypted rom (alberto's aosp 9 64bit)
and haven't been bothered by it again.
I gotta say, this makes me more than a bit afraid to go flashing 9 stuffs other than what I've been flashing. even flashing Alberto's 32 bit scares me as this came out of the blue.
At least in worst case I can always go back to 8.0.0 and let that update as much as it can and just run that. I was hoping for a security current updated ROM which was why I was going with Alberto's 64 bit - which is no more.
Before I did any of this I went to twrp and backed up and then plugged to computer and copied internal and SDcard to my computer since I knew I would lose internal (that's where my TBPro bakup is!!!!) and wasn't sure about SDcard.
read this one - to format DATA change to ext4 and then back to f2fs.
https://forum.xda-developers.com/moto-z-play/help/twrp-3-2-3-wipe-format-data-break-phone-t3892745
new guide:
https://forum.xda-developers.com/editpost.php?do=editpost&p=79070724
for folks who read that last post and link, I just completely re-wrote it.
RSDlite-ing a stock rom will give you an encrypted phone.
Hello,
this is somewhat similar to this thread, but there are no answers and I have a bit of a different problem at the moment.
I've been using official LOS 17.1 for some time on my Note 8T, but it started to get slow, so I decided to upgrade my android version and test the latest features. I downloaded xiaomi firmware and A13 ROM, flashed them, made a full wipe and... here is where my problems started. Please don't school me here - I'm pretty sure that I messed up, I'm just looking for possible solutions.
What happened?
My phone had an encrypted data partition and as I read later, it was pretty normal that A12 installation messed it. The recovery (regardless of the version) has stopped prompting me to give the encryption password, instead it was mounting the internal drive encrypted. I tried to downgrade android version to 10 (both LOS and MIUI), but I had bootloop bringing me back to recovery. I tried decrypting it via ADB, but it didn't work. Since I need my phone, I made a backup of the whole internal storage with ADB and I have it in .img form on my hard drive. Since I've never encountered any problems like this, I wasn't prepared for losing all of my data, especially pictures and Signal archive, so I'm wondering - what can I do to try to get my data back, giving I have the full memory dump and I know the password used for en/decrypting it?
Thanks in advance, I spent hours looking for an answer, but I don't feel like getting close to the solution.
reip said:
Hello,
this is somewhat similar to this thread, but there are no answers and I have a bit of a different problem at the moment.
I've been using official LOS 17.1 for some time on my Note 8T, but it started to get slow, so I decided to upgrade my
Click to expand...
Click to collapse
Encryption is effective if you protect your phone with a password or schema etc on the lock screen.
You cannot restore data from an AOSP rom to a MIUI rom and vice versa.
The backup will only work with the same rom as the backup.
So if i have a filesystem that was encrypted on lineage os 17.1, i should make a clean install of it and then try to push the whole .img backup through adb?
reip said:
So if i have a filesystem that was encrypted on lineage os 17.1, i should make a clean install of it and then try to push the whole .img backup through adb?
Click to expand...
Click to collapse
Same rom, same password, not 100% guaranteed that it works.
reip said:
.
Click to expand...
Click to collapse
Since you have a backup try flashing DFE
let me know if it work
loopypalm said:
Since you have a backup try flashing DFE
let me know if it work
Click to expand...
Click to collapse
the problem is i pulled the whole mmcblk0 dump with adb, which gives me more than twenty partitions in the .img file (I can easily say which one is the /sdcard one because of the size) and I am not sure if pushing the whole image with incorrect rom won't bring me to the exact state i was in before. Is there a way to push a particular partition from a .img file or should i try to push everything and flash dfe, as you're saying?
reip said:
the problem is i pulled the whole mmcblk0 dump with adb, which gives me more than twenty partitions in the .img file (I can easily say which one is the /sdcard one because of the size) and I am not sure if pushing the whole image with incorrect rom won't bring me to the exact state i was in before. Is there a way to push a particular partition from a .img file or should i try to push everything and flash dfe, as you're saying?
Click to expand...
Click to collapse
if the partitions inside are .IMG file you can restore with orangefox
pick the img and set the target to restore
restore just data 1st then DFE then wipe cache+dalvik then reboot and pray
loopypalm said:
if the partitions inside are .IMG file you can restore with orangefox
pick the img and set the target to restore
restore just data 1st then DFE then wipe cache+dalvik then reboot and pray
Click to expand...
Click to collapse
This sounds like a plan, but to which partition should I flash it? I don't see 'data' option there.
+ just to make sure, do I have to reflash and set up the exact rom and password I was on when I had the encryption working before I start the operation you're suggesting?
reip said:
This sounds like a plan, but to which partition should I flash it? I don't see 'data' option there.
+ just to make sure, do I have to reflash and set up the exact rom and password I was on when I had the encryption working before I start the operation you're suggesting?
Click to expand...
Click to collapse
aah, i forgot it don't have data as target
but there must be a way using ADB
-if you are going to restore the whole backup = no need to recreate the same conditions you did before
-if you are going to restore just the userdata backup = recreate the same conditions
in both cases format DATA is important (format nt wipe then reboot to recovery)
loopypalm said:
aah, i forgot it don't have data as target
but there must be a way using ADB
-if you are going to restore the whole backup = no need to recreate the same conditions you did before
-if you are going to restore just the userdata backup = recreate the same conditions
in both cases format DATA is important (format nt wipe then reboot to recovery)
Click to expand...
Click to collapse
so format data, restore, flash DFE, reboot?
reip said:
so format data, restore, flash DFE, reboot?
Click to expand...
Click to collapse
yes