Tried flashing the latest Magisk update in fastboot (v20) with the latest Android 10 update, and my phone went into bootloop, so I reflashed the factory boot.img and got stuck loading on the G splash screen for 16 hours until I shut it off. I booted TWRP to backup the /data partition before reflashing to factory and starting fresh, but it won't mount (shows 0mb) and doesn't prompt for any decryption passwords. Won't boot OS even with dirty flash and OTAs. I need to backup the data partition because I have a lot of important user data on it. Any advice on getting TWRP to decrypt the data (had fingerprint set up with PIN as unlock)?
Seeing as how it's 4 days after your post, I'm going to guess you've already learned that you're pretty much FUBARed. I had the same thing happen last month. Unfortunately, the only way out is through, and in this case that means going through the process of a full wipe and the subsequent hours/days of installing all your user apps and setting everything up from scratch.
This is because of a incompatibility in recent builds of TWRP with Pixel2 images past April that makes it impossible to decrypt the data partition. The only workaround is to wipe the entire device, install the Pixel2 factory image from April, flash TWRP, boot the device and setup your password/pin, boot into TWRP and decrypt the device one time, and then flash the latest Pixel2 factory image and TWRP/Magisk like normal. Outside of that, the only other option is to remove your password/pin every time you need to access recovery.
As for the exact details of how or why this is an issue, I can't say, as I don't have the technical know how to parse a lot of what I've read about the problem, only just enough to understand what the problem is and how to get around it.
Related
Got my brand new U11+ today, applied november patch update, but now even with latest TWRP the phone keeps encrypting data. Any tip?
Sadly it looks like this device forum is poorly attended. Just so few U11+ out there? Really a shame
Please have a test and give me a feedback
https://www118.zippyshare.com/v/hUetNmUq/file.html
Please help me, somehow your version encrypted my phone.... What is password?
Thank you so much!
Just to give you feedback, here is what I did (and what happened):
- Reverted back to stock with RUU
- Applied OTA, security patch 2018 11 01
- Flashed according twrp
At first boot encryption occurred again and in security options I could read 'phone encrypted'; still I could enter recovery and normally see data. No request to decrypt, data perfectly accessible and I've been able to flash magisk from internal storage. This was all I needed. Yet, out of curiosity, I tried to wipe data to decrypt the phone. TWRP read something like 'unable to wipe data, you should reboot recovery to access data again'. And then data were gone. No mount, no access.
Once selected reboot to recovery, the phone rebooted system instead. This time there has been no encrypting message, but the phone was wiped. And again, reading in security options, it was encrypted. Going back to recovery I had exactly the same situation as before wiping data: I could see them and normally flash zip.
Even with this weird behaviour, so far I'm satisfied with the result, so again thank you very much!
Glower said:
Thank you so much!
Just to give you feedback, here is what I did (and what happened):
- Reverted back to stock with RUU
- Applied OTA, security patch 2018 11 01
- Flashed according twrp
At first boot encryption occurred again and in security options I could read 'phone encrypted'; still I could enter recovery and normally see data. No request to decrypt, data perfectly accessible and I've been able to flash magisk from internal storage. This was all I needed. Yet, out of curiosity, I tried to wipe data to decrypt the phone. TWRP read something like 'unable to wipe data, you should reboot recovery to access data again'. And then data were gone. No mount, no access.
Once selected reboot to recovery, the phone rebooted system instead. This time there has been no encrypting message, but the phone was wiped. And again, reading in security options, it was encrypted. Going back to recovery I had exactly the same situation as before wiping data: I could see them and normally flash zip.
Even with this weird behaviour, so far I'm satisfied with the result, so again thank you very much!
Click to expand...
Click to collapse
Okay, seems it works in a right way, I will post it to U11+ TWRP released page.
sabpprook said:
Okay, seems it works in a right way, I will post it to U11+ TWRP released page.
Click to expand...
Click to collapse
How can I get my phone decrypted? Why was it encrypted?
drtopjoe said:
How can I get my phone decrypted? Why was it encrypted?
Click to expand...
Click to collapse
You must flash the TWRP recovery which security level is the same as your current android system, otherwise you will get phone encrypted after reboot to android system or TWRP's data decrypting do not work.
sabpprook said:
You must flash the TWRP recovery which security level is the same as your current android system, otherwise you will get phone encrypted after reboot to android system or TWRP's data decrypting do not work.
Click to expand...
Click to collapse
TWRP says decrypted successfull with default password. In twrp I can see all my apps, but when reboot I cannot see.
Ehat version of twrp Shoul I use? Or which security patch should I flash?
So I did what I thought was a routine thing, trying to restore system, boot, and data like I have on many phones before only to ended up in a bootloop or bootloader only not even able to boot a TWRP from fastboot.
After several hours of trying just about everything I finally faced the fact that I was not going to be able to restore any NANDROID backup I had do to A/B, encryption or the latest Android security patch?
However, you can get you phone running again quite easily with this thread: https://forum.xda-developers.com/oneplus-6/how-to/rom-stock-fastboot-roms-oneplus-6-t3796665 and using the flash-all option from a WIndows 10 VM (I am a Mac/Linux guy, but this does work from a Windows VM and is quick).
Before I re-installed anything I wanted to just verify that I could do a simple NANDROID backup of an empty phone with twrp / blu_spark and I can't under any case. Here's what I tried (with latest stock TWRP and latest Blu_Spark TWRP):
1) simple restore of data, system, boot -- > boots only to fastboot, need to recover with thread above
2) Recover with thread above, re-root (Magisk 18.1) and reinstall TWRP, boot ROM, then try restoring just data -- > same as #1
3) Recover using thread above, re-install TWRP, restore NANDROID, and re-run Magisk (suggest by a few) --> same as #1
My device is encrypted, and I could turn off encryption, but that is somewhat scary on a daily driver.
So has anyone successfully restored a NANDROID on a 9.0.4 rooted phone with the latest Android security patch and if so, what's the trick?
Thanks,
MW
MetroWestMA said:
So I did what I thought was a routine thing, trying to restore system, boot, and data like I have on many phones before only to ended up in a bootloop or bootloader only not even able to boot a TWRP from fastboot.
After several hours of trying just about everything I finally faced the fact that I was not going to be able to restore any NANDROID backup I had do to A/B, encryption or the latest Android security patch?
However, you can get you phone running again quite easily with this thread: https://forum.xda-developers.com/oneplus-6/how-to/rom-stock-fastboot-roms-oneplus-6-t3796665 and using the flash-all option from a WIndows 10 VM (I am a Mac/Linux guy, but this does work from a Windows VM and is quick).
Before I re-installed anything I wanted to just verify that I could do a simple NANDROID backup of an empty phone with twrp / blu_spark and I can't under any case. Here's what I tried (with latest stock TWRP and latest Blu_Spark TWRP):
1) simple restore of data, system, boot -- > boots only to fastboot, need to recover with thread above
2) Recover with thread above, re-root (Magisk 18.1) and reinstall TWRP, boot ROM, then try restoring just data -- > same as #1
3) Recover using thread above, re-install TWRP, restore NANDROID, and re-run Magisk (suggest by a few) --> same as #1
My device is encrypted, and I could turn off encryption, but that is somewhat scary on a daily driver.
So has anyone successfully restored a NANDROID on a 9.0.4 rooted phone with the latest Android security patch and if so, what's the trick?
Thanks,
MW
Click to expand...
Click to collapse
apparently is not matter of factly, i do nandroids and have restored from them various times with only 2-3 settings that i had to reset my way thereafter, hence it's apparently worth to retry, it works.
sometimes it helps to know that things are possible to put some more effort into something, knowing it can be worth it in case of success.
perhaps some remarks:
if your' phone is "empty" as you stated i recommend to first install factory image / stock rom latest OOS, i.e. 9.0.4
make nandroids of each partiton speparately and also restore them separately while don't nandroid the images, and cerrtainly don't restore those, only common partitions like system, boot, vendor, data.
system and vendor are present as normal partition as well as image partition, don't touch the later in any way.
all this only works if you restore on a phone that was bootable before you restore, for restoring to empty phones there are other procedures via fastboot commands and or stock rom via stock recovery if it's on device, else ADB comes in handy.
last but not least if you restore you have to restore everything, not only one partition especially not only system partition, won't work well or not at all depending.
1. Modem if corrupted, else not needed
2. EFS if corrupted, else not needed
3. Vendor start here if the previous rom was running well and make sure it's not been altered or you have to correct vendor backup in case you have more than one
4. System
5. Boot
6. Data
good luck
magnamentis said:
apparently is not matter of factly, i do nandroids and have restored from them various times with only 2-3 settings that i had to reset my way thereafter, hence it's apparently worth to retry, it works.
sometimes it helps to know that things are possible to put some more effort into something, knowing it can be worth it in case of success.
good luck
Click to expand...
Click to collapse
OK -- do tell, what settings did you use? And you have done this on OOS 9.0.4 with encryption, or did you disable decryption?
I'll happily delete or edit the post...it seems many are having problems with few solutions starting with 9.0.4...
Thanks,
MW
MetroWestMA said:
OK -- do tell, what settings did you use? And you have done this on OOS 9.0.4 with encryption, or did you disable decryption?
I'll happily delete or edit the post...it seems many are having problems with few solutions starting with 9.0.4...
Thanks,
MW
Click to expand...
Click to collapse
the last restore i did on 9.0.3, since then i gave up on custom roms since OOS rooted + a few useful apps make OOS close to perfect for me
i'd not delete the thread, many reported issues with nandroids because the normal procedure to take one single backup and restore from twrp to an empty device does not work, one always need to first flash stock OOS to a clean slate before installing anything else or restoring anything.
and backups should be in increments not one single backup like it was possible on single slot devices.
restoring one single partition usuelly ends up in a mess except boot partition, boot, efs and modem can be restored as standalone restores without issues in most cases while flashing a kernel + magisk is still easier and safer than restoring a boot partition.
as to setttings i dunno what you mean, exactly and as to encryption, my device is and has bee encrypted at all times.
it's most important to use twrp- recovery by blue_spark, official standard recovery has issues ( at least always had as long as i tried using it) especially with verification in TWRP on encrypted devices. there is a risk to end up encrypted without any way to boot back into system or into twrp menu, hence use blue_spark's and all is well, user error exempt of course
Since reinstalling everything is going to take forever (at least another 4 hours)...I am going to disable encryption and do some more testing. I am now more certain than ever, no-one has successfully restored a NANDROID on an encrypted OOS 9.0.4 phone ever.
I am going to disable Force Encryption and AVB 2.0/dm-verity and try my restore again -- maybe then I can use one of my NANDROIDS. But doing this on an encrypted phone seems impossible. I guess if you use a screen PIN you files are still vulnerable to someone that knows bootloader and / or recovery, but I'll have to live with that.... Not being able to NANDRIOD restore is a killer...
I know is an old discussion but I believe we still have this issue. I have a 6T, oos10.3.6 and neve succeeded to restore a nandroid backup. Does anyone found a working solution?
Thanks
Hi Folks, I updated the OS, got everything up andrunning, setup a pin & fingerprint, my settings in Elementalx were lost so I made the mistake the backup kernel was the settings and it a big mistake.
Long story short I am only able to boot to Blu_Spark v9.86 to see all my files and data names encrypted. Ugh.
And I cannot boot into the os. What are my options? Heh? If any?
https://youtu.be/X7yDPszoQ5s
---------- Post added at 10:16 AM ---------- Previous post was at 10:13 AM ----------
Also this.....https://************/how-to-fix-twrp-unable-to-mount-storage-internal-storage-0mb/
georgiapi said:
Hi Folks, I updated the OS, got everything up andrunning, setup a pin & fingerprint, my settings in Elementalx were lost so I made the mistake the backup kernel was the settings and it a big mistake.
Long story short I am only able to boot to Blu_Spark v9.86 to see all my files and data names encrypted. Ugh.
And I cannot boot into the os. What are my options? Heh? If any?
Click to expand...
Click to collapse
First i suggest you to update TWRP, reboot to bootloader and boot with blue spark v9.101, you would be able to put your pin and decrypt data, if so, flash the blue spark v9.101 to make it persistent, then reboot to recovery.
Now if everything is gone fine, you can access your storage by putting your correct pin in TWRP and from there i think you can try first to flash oos twice (with TWRP everytime) and see if system will boot-up, if not you need to wipe Data/cache/dalvik (factory reset). Do not flash anything else till system is working and booted
Thank you. Before I begin,
I am new to the term "make it persistent"? I hope you hang with me here....
To clarify, it was late and I was fatigued so I may have left out important details. FYI I run rooted stock roms.
After my fiasco I somehow managed to get booted to TWRP with access to my nandroids, both of which were made or ROMS with no pin or fingerprint. This is left over from the days it was suggested to not make nands of protected roms. Unprotect first.
So I choose restore one and TWRP asks for my pin (before I did the elementalx kernel restore I set a pin) which I entered and now I can only boot to TWRP but all the file names and such are encrypted.
I can also tell you my Slot B is trashed. I had to fastboot set_active _a to get off of it.
Thanks,
Would this be as simple and deleting .key files? I can see them in TWRP /file manager/Data/. I do not see a system file-folder.
Ok first off Everytime you flash the any rom the twrp will be overwrited by stock recovery, this is because with A/B partitioning system there's no more recovery partition and recovery it self is integrated in boot partition so for make it persistent you need to reflash twrp Everytime you flash a rom.
For this I've suggested you to update twrp via fastboot method.
And you can change slot A/B from Twrp too
Now you're problem is encrypted data so you MUST try to update TWRP first, then try what I've already explain before and let me know if it works
OK guys, I bit the bullet and did a full wipe factory reset. I deserve it. You guys are not only off the hook but great. I decided not to burden here over my blunder. I have a data backup about a month old so.........
I just got a used Pixel off Ebay, and had an adventure unlocking the bootloader (f-ing Verizon), but finally got that done. I was expecting the usual easy time of installing TWRP, performing a complete wipe, and LineageOS 16 after that. Instead, I spent the next three hours making no progress at all.
First I used fastboot to boot TWRP.
Next, I used the TWRP installer zip to install TWRP to "both slots". WTF are the slots?
Then I got LineageOS 16 installed and started up. It was really buggy. I figured I had a bad flash, so I thought a wipe and reinstall would be good.
When I rebooted into recovery, it wasn't TWRP, it was Lineage Recovery. WTF is Lineage Recovery? I never installed that.
From here onward, the only way I could get into TWRP was to use fastboot. If I boot into recovery, I get this Lineage Recovery garbage.
I've wiped the phone multiple times, but it fails to wipe /system and /vendor because they are "unavailable or busy".
I can't install another ROM, and it continues to boot into Lineage Recovery.
Obviously, I'm not understanding how "slots" A and B work.
Can anyone explain the partition scheme on this thing to me, please?
The lineage recovery now installs as standard on official builds wether you like it or not, see their wiki for details, helps with the a/b seamless updates. There is a dedicated thread for sailfish/marlin lineageOS16, might pay to ask in there for details on removing the lineage recovery.
Also this should explain the slot thing a bit better
https://www.xda-developers.com/how-...ess-updates-affect-custom-development-on-xda/
Thanks. The installation instructions in the LineageOS changeLog make it clear that the behavior I was seeing was the new normal.
https://www.lineageos.org/Changelog-19/
I've decided to accept it, even if I don't like it.
Mattzees said:
I just got a used Pixel off Ebay, and had an adventure unlocking the bootloader (f-ing Verizon), but finally got that done. I was expecting the usual easy time of installing TWRP, performing a complete wipe, and LineageOS 16 after that. Instead, I spent the next three hours making no progress at all.
First I used fastboot to boot TWRP.
Next, I used the TWRP installer zip to install TWRP to "both slots". WTF are the slots?
Then I got LineageOS 16 installed and started up. It was really buggy. I figured I had a bad flash, so I thought a wipe and reinstall would be good.
When I rebooted into recovery, it wasn't TWRP, it was Lineage Recovery. WTF is Lineage Recovery? I never installed that.
From here onward, the only way I could get into TWRP was to use fastboot. If I boot into recovery, I get this Lineage Recovery garbage.
I've wiped the phone multiple times, but it fails to wipe /system and /vendor because they are "unavailable or busy".
I can't install another ROM, and it continues to boot into Lineage Recovery.
Obviously, I'm not understanding how "slots" A and B work.
Can anyone explain the partition scheme on this thing to me, please?
Click to expand...
Click to collapse
@Mattzees was you Oem unlocking in developer options greyed out ?(connect to the internet or contact your carrier). if so is there any solution or its a waste of time
Hi,
So it seems when i restore data via TWRP it triggers the protection which encrypts the whole sdcard, can this be avoided?
Here are the steps i did:
Full wipe
fastboot boot twrp (Nebrassy)
sideload stock 11.1.1
sideload magdisk
Finished setting up the device
Then booted twrp again
Did full backup
And then it never boot again to system... no idea why could be the twrp.
Now i'm stuck with this backup, every time i restore it, the entire sdcard gets encrypted.
I've tried flashing both stock boot and patched boot but it didn't help
Any ideas or should i do it all again and lose twrp, seems to be very buggy at v11.1.1
I managed to solve this issue myself.
Encryption is forced by default since android v10 i think so that means when you try to flash any data it has to be either the same type or it would encrypt the whole internal storage, i.e. you can backup just fine but if you restore and reboot the phone will tamper with all the data making it unreadable.
You need to disable encryption first then flash the data and then it works fine, unless you disabled it to begin with of course.
Another key point here is that when the phone encrypts the entire storage you won't be able to flash anything else until you completely erase everything.
Wasted hours on this on OP6 and OOS 11.1.1 + Unofficial Twrp,
Here is a short summary of the main points:
Full backup from TWRP works fine but copy it elsewhere or you might lose it when restoring
If you booted into encryption i used to flash lineageos recovery then boot into it and do a full wipe, then flash twrp back. i don't think it works from that twrp version
If you want to disable encryption or restore backups use this one (only one that worked) https://forum.xda-developers.com/t/...ncrypt-disk-quota-disabler-11-2-2020.3817389/
If you want OOS v11.1.1 + TWRP + Root + Backups do it in the following order: Unlock Bootloader, Boot TWRP, Install TWRP permanently, Flash Magdisk, Flash DFE
Not sure it's important but lineageos has a script for A\B slot phones like OP6 to sync slots, should be used at least once after flashing V11 just in case to avoid possible problems https://wiki.lineageos.org/devices/enchilada/install
I'm also adding stock and patched boot images in case someone needs them.