I am on OOS12 rooted with twrp. I elected to do the OTA update method where you disable magisk modules, go into magisk and uninstall images, install the update, and then restore images and reboot. I have no idea why, but now my phone is in Qualcomm Crashdump mode. I have a lot of valuable things on my internal storage that I need to save or backup somehow.
Now, I can fastboot boot twrp.img and have that work, but in order to decrypt my userdata, it's asking for a pin, and I don't believe my pin is working. I'm wondering if this issue also affects what the pin code would be.
Is there any way at all to retrieve my data? Never would I expect an OTA to cause this and hence, there was no need to backup anything beforehand. Also, isn't the other a/b partition supposed to be available as a failsafe? My other partition should be just fine, although I have a feeling that assumption is because I don't understand the full gravity of this Qualcomm Crashdump mode.
bulletbling said:
As stated, there will be a reward for someone who has a solution that works.
I am on OOS12 rooted with twrp. I elected to do the OTA update method where you disable magisk modules, go into magisk and uninstall images, install the update, and then restore images and reboot. I have no idea why, but now my phone is in Qualcomm Crashdump mode. I have a lot of valuable things on my internal storage that I need to save or backup somehow.
Now, I can fastboot boot twrp.img and have that work, but in order to decrypt my userdata, it's asking for a pin, and I don't believe my pin is working. I'm wondering if this issue also affects what the pin code would be.
Is there any way at all to retrieve my data? Never would I expect an OTA to cause this and hence, there was no need to backup anything beforehand. Also, isn't the other a/b partition supposed to be available as a failsafe? My other partition should be just fine, although I have a feeling that assumption is because I don't understand the full gravity of this Qualcomm Crashdump mode.
Click to expand...
Click to collapse
As a follow-up, I am wondering if the latest twrp-3.7.0_11-0 I am temporarily booting is not allowing my pin to work correctly because it doesn't support decryption / breaks my pin for OOS 12.1 C.69, which is what the OTA wanted to update to.
---UPDATE---
I downloaded the latest Stock Firmware and extracted the payload.bin and manually flashed everything from this thread below.
Restore OnePlus 9 to Stock via Fastboot Commands
This guide assumes you have the SDK Platform Tools installed and working, along with USB drivers for your device (if needed), and have your full update zip which you've already extracted the payload.bin from, and then dumped the images using...
forum.xda-developers.com
And now...instead of it going to the Qualcomm crashdump, it goes right to fastboot. I don't know if this is progress, but at least with boot slot b it's currently on, there is no more crashdump occurring. The problem now is that it still wont boot with a fresh manual install of all stock images in the payload.bin. I'm wondering if this is related to my internal storage, but that wouldn't make any sense. TWRP is still telling me my pin is incorrect, even though it's correct.
---UPDATE 2---
I had tried everything I could think of and ended up resorting to the MSM tool. I don't have any recent backups but have some things saved. It appears that no one responded meaning this is likely impossible, short of a forensics lab that can crack encryption like this.
Related
Dear XDA, I could really use your help.
I have a stock LG Nexus 5x (bullhead/7.1.1) which recently started to fail to boot properly as it never loads past the coloured animations on startup and often stops. This sounds like it may be the boot-loop problem.
I have not rooted the phone, unlocked the boot-loader or flashed any recoveries. I have not enabled USB debugging and can't now because it won't boot.
I am looking at my options to recover the data from this phone.
I can get to the fastboot screen (where the fastboot command line tools see the device, but adb does not). I can proceed to the recovery screen and have tried clearing the cache with no luck.
I am considering trying:
Booting a fastboot recovery image
(eg fastboot boot recovery TWRP.img)
Applying a rescue OTA image
Will these methods void the phones warranty?
Will these methods even work (given the bootloader is locked)?
Can the images be recovery images like TWRP or does it have to be some stock/non-custom image?
Does the rescue OTA require adb/usb-debugging to be operational?
Will the data on the phone still be intact using these methods?
As I am cautiously working may way through this to firstly recover my data, secondly recover my phone., any advice would be greatly appreciated.
Sorry to hear that! I'm assuming your files weren't backed up to Google drive.
I don't know a way to recover your data! If you flash a OTA image, it might help fix your phone boot up problem and it will preserve your phone data.
This sucks because the phone is encrypted by default (did you use to enter a password in the middle of phone booting up and the it would continue booting after your password was accepted? If yes, encryption is on). So flashing TWRP won't mean you can see your data.
And it also has USB debugging disabled by default, which means you probably can't mount the internal memory through ADB.
So I would flash a full OTA image before anything else and keep my fingers crossed. Don't flash a full factory image because it will wipe the data and continue!!!
https://developers.google.com/android/ota
Sent from my Nexus 5X using XDA-Developers Legacy app
Commodore 64 said:
Sorry to hear that! I'm assuming your files weren't backed up to Google drive.
I don't know a way to recover your data! If you flash a OTA image, it might help fix your phone boot up problem and it will preserve your phone data.
This sucks because the phone is encrypted by default (did you use to enter a password in the middle of phone booting up and the it would continue booting after your password was accepted? If yes, encryption is on). So flashing TWRP won't mean you can see your data.
And it also has USB debugging disabled by default, which means you probably can't mount the internal memory through ADB.
So I would flash a full OTA image before anything else and keep my fingers crossed. Don't flash a full factory image because it will wipe the data and continue!!!
Click to expand...
Click to collapse
Unfortunately I had not set-up any syncing/backup process on the phone. In the future I will.
Although I don't recall what encryption settings were originally configured, I didn't have to enter a password in the middle of boot, and was only prompted to swipe in. So I think it wasn't encrypted.
So I attempted to sideload an OTA image via:
adb sideload bullhead-ota-n4f26i-06953aec.zip
then rebooted, however the phone still does not successfully boot any further. I must have really broken this one!
Are there any data recovery methods if a factory reset is applied? if I take it in to a repair agent under-warranty, do they typically wipe your data anyway?
Also, do I need to remove this OTA image if I am to return it for repair under warranty?
In a futile/desperate attempt to try to further recover my data, I have attempted to load my Nexus 5X into the stock recovery mode, then experimented with adb when using the 'apply update from adb' option. This exposed a subset of adb commands which appeared to work (eg adb devices, adb sideload etc). I was hoping to be able to run adb shell or adb pull remote local and recover some data... however I only encountered errors.
./adb shell
error: closed
./adb pull /storage/emulated/ /backup
adb: error: connect failed: closed
I assume this is expected (due to the stock recovery adb limitations, but thought it was worth a shot). I am considering exploring the fastboot options (eg fastboot boot recovery recovery.img) I suspect these are also likely to fail/wipe data. Has anyone got any suggestions/ideas or am I just wasting my time?
This just happened to me yesterday, and I got the single file I needed off the phone today. I fought with the thing for hours yesterday. First you have to clear the cache and sideload a new bullhead zip file (as documented elsewhere). That isn't all, though. After several tries, I noticed that I got farther along in the boot if I let the phone sit for a while. So, on the theory that there's a loose solder connection somewhere and/or heat buildup, I put the phone in the freezer for a few hours (not my idea; found it on reddit). This worked, but only if I also tapped the back of the phone with my knuckle before booting. As I said, success today and I'm all smiles. I hope this helps someone else.
The phone, by the way, is bricked as far as I can tell. And my backups are going to be a lot more comprehensive from here on.
Hello
About securing your device after having an unlocked bootloader. Using TWRP you can easily delete whatever lockscreen is installed by removing a few files from /data/system, the gatekeeper files and the three locksettings files.
You might as well not have a lockscreen at all if a potential phone thief has any idea what he's doing. How would you secure your device?
Encryption isn't possible on Lineage 14, and 15 still has too many bugs for me to consider using it. The only other option is staying stock and having a massively outdated Android security patch.
Are there any other security options I'm missing?
a tiny ant said:
Hello
About securing your device after having an unlocked bootloader. Using TWRP you can easily delete whatever lockscreen is installed by removing a few files from /data/system, the gatekeeper files and the three locksettings files.
You might as well not have a lockscreen at all if a potential phone thief has any idea what he's doing. How would you secure your device?
Encryption isn't possible on Lineage 14, and 15 still has too many bugs for me to consider using it. The only other option is staying stock and having a massively outdated Android security patch.
Are there any other security options I'm missing?
Click to expand...
Click to collapse
Install a stock recovery to avoid the easy deletion of files in TWRP.
But...as long as you have a LP or MM bootloader stack you can still boot a TWRP image by fastboot boot when having physical access. To avoid this you need the bootloader stack for N which is available only for h815 devices and denies fastboot boot commands. While fastboot flash is still available for flashing TWRP...
Another option:
Install any ROM which has working encryption. Encrypt the device.
Flash the ROM of your choice over it. The issue we had in 14.1 was about enabling(!) encryption. The decrypt of a previous one worked fine. Just ensure that you do not use format data as that would remove encryption.
Even when you have encrypted your device your bootloader unlock will let a door open which can allow the modification of system files (which never gets encrypted). Means: I can place a malware in system, you will boot next time android and activate my malware after you have entered your pass for the decrypt.
So all the above can make things harder for an attacker while not impossible to break.
TLDR;
Once unlocked there is always a way to allow access. The warnings of the vendors are there for a reason
Sent from my LG-H815 using XDA Labs
steadfasterX said:
Install a stock recovery to avoid the easy deletion of files in TWRP.
But...as long as you have a LP or MM bootloader stack you can still boot a TWRP image by fastboot boot when having physical access. To avoid this you need the bootloader stack for N which is available only for h815 devices and denies fastboot boot commands. While fastboot flash is still available for flashing TWRP...
Another option:
Install any ROM which has working encryption. Encrypt the device.
Flash the ROM of your choice over it. The issue we had in 14.1 was about enabling(!) encryption. The decrypt of a previous one worked fine. Just ensure that you do not use format data as that would remove encryption.
Even when you have encrypted your device your bootloader unlock will let a door open which can allow the modification of system files (which never gets encrypted). Means: I can place a malware in system, you will boot next time android and activate my malware after you have entered your pass for the decrypt.
So all the above can make things harder for an attacker while not impossible to break.
TLDR;
Once unlocked there is always a way to allow access. The warnings of the vendors are there for a reason
Sent from my LG-H815 using XDA Labs
Click to expand...
Click to collapse
Thanks! Very informative post. I think the risks of having an unlocked bootloader are acceptable if the phones' data can be encrypted.
I have tried encrypting on stock Nougat and then flashing LineageOS over it, however it resulted in the LineageOS installation not recognizing my pattern and refusing to boot past the boot prompt. Maybe deleting the keyguard files right after flashing? I will try this later.
So the next step was disabling the pattern altogether and then trying to use TWRP again, but then it asks for a password, which technically shouldn't exist since there isn't any lock on the screen.
**Well I've actually figured this one out, apparently Android defaults to "default_password". It almost seems too silly to be true but it has to be something I guess. Will try flashing LOS later over an encrypted storage.
steadfasterX said:
Another option:
Install any ROM which has working encryption. Encrypt the device.
Flash the ROM of your choice over it. The issue we had in 14.1 was about enabling(!) encryption. The decrypt of a previous one worked fine. Just ensure that you do not use format data as that would remove encryption.
Click to expand...
Click to collapse
I've actually tried this, encrypting from stock Nougat and flashing Lineage over it, except then Lineage refuses to boot, asking for a password instead. "default_password" doesn't work even though no actual password is set.
It seems to be dependant on what setting it was on stock nougat, as it could also ask for a pattern which then won't be accepted.
I also cannot find any lockscreen or keyguard related files in /data/system after flashing stock Nougat. Are there any other options I could try? The device is decrypted in TWRP before rebooting, but afterwards the encryption activates making it no longer possible to enter the system.
Another bit of a strange/interesting thing. The only way out was to format data, thus removing encryption. I then restore a TWRP backup where encryption was enabled, deleted the lockscreen files and upon booting the device appeared to be fully encrypted again. Is this a bug or something?
Hello,
I have a Mi Max 3 6GB/128GB which I got from the UK which arrived unlocked and with Global Stable ROM installed which actually updated to V10.3.3.0.PEDMIXM by OTA - I tested.
fastboot getvar anti shows failed, so I assume no Anti Rollback Protection, which I thought a little strange, it being MIUI 10 with (after OTA) June 2019 security patch.
I spent the last couple weeks setting up the phone to my liking (I have 300 apps installed) and finally finished yesterday.
Then I wanted to uninstall some Google/Facebook/Xiaomi bloatware using the excellent "Xiaomi ADB/Fastboot Tools".
I was pretty careful in my opinion to only remove the safe ones (the tool claims to only show you the safe ones) like Music, Video, MiPay, MiCloud, MiForum, MiSIM and all Facebook in the ADB section of the tool.
The I switched in fastboot and thought it would be a good idea to wipe Cache (nothing else).
Upon restart the Mi Max 3 first shows the black boot screen with unlock written at the bottom, then changes to the normal boot boot screen with MIU and the points at the bottom showing that it is busy booting. It stayed there for a while and I thought maybe it was rebuilding the cache and it took that long, but after 30 min still no luck.
Then I fired up the "Xiaomi ADB/Fastboot Tools" on my PC again and it told me the phone was in ADB mode, I could reboot into system mode, where the same thing happened - no progress in booting.
I cannot turn off my phone either, but I can switch from sastem boot (which gets stuck) into fastboot mode via ADB.
Would someone know what's wrong and what I can do to get my phone out of that bootloop while hopefully maintaining all my data and setups, on which I worked for weeks?
Thank you so much for your help!
P.S .: In case it could help: I could read out the phone properties of the Mi Max using the "Xiaomi ADB / Fastboot Tools" while it was softbricked, meaning the ro. init. persist. sys. and dalvik. values of the smartphone. I am happy to post them here, if requested.
Hi,
Do you have an SD card? If so, remove it, because as you cleared the cache, I think it might be a problem with encryption (lost reference).
In your case, I believe a reset will work again, but you will lose application configuration data. Via ADB you can backup files only.
If you do not have unlock bootloader, be very careful as you will not be able to flash TWRP or others.
Good luck!
Thanks, the phone came from the vendor with Global Stable ROM and unlocked. It may be an unofficial unlock, though I was able to install OTAs.
I don't have SDCard.
How can I do ADB backup?
I was able to flash official TWRP just a few minutes but it couldn't access data, maybe because it is encrypted. Now I think I will try and install latest Orange Fox r10 stable, which I think should be able to handle decryption, so that maybe I will be able to get at my date.
Any other advice?
Hi,
Now that you have TWRP, clear cache / dalvik from TWRP and try starting again, maybe start system.
About copy via adb follows a link below:
https://www.lifewire.com/use-minimal-adb-and-fastboot-4582201
in step 2
"
The command to move files from your computer to your phone is adb push.
To move files from your phone to your computer the command is adb pull.
"
Through TWRP you may also be able to back up. Go to (mount partitions) and select all partitions.
Make sure the TWRP MTP option is on, it will allow the device to be mounted via usb on your computer.
I use TWRP I use nijel8, it works very well.
https://forum.xda-developers.com/mi-max-3/development/recovery-twrp-3-2-3-1-nitrogen-t3866084
If you can't launch system, you will have to reinstall the Rom.
Good luck!
PS.
More help for adb.
https://forum.xda-developers.com/android/help/adb-fastboot-commands-bootloader-kernel-t3597181
Thanks for your advice!
I first used the official TWRP and I was able to flash it and start it.
But then the wipe of cache and dalvik failed.
And I could not mount data etc..
When I tried to repair the file system with TWRP I got error 255 - unable to repair data from fsck.f2fs.
Then I saw in your signature that you use nijel8's TWRP and I read that thread, and I started to understand, that my TWRP errors most likely originate from TWRP not being able to decrypt my partitions.
However, towards the end of the thread it seemed that nijel8 stopped working on that project and then Xiaomi once again changed the encryption in MIUI 10/Pie and so it was recommended first to use an obscure Chinese TWRP and then to move on to Orange Fox Recovery Project, which supposedly can handle the decryption better. So that's what I got and I am just about to install it and see if I can rescue or even repair anything.
If you have any other tips for me, I would be very grateful.
You have explored the possibilities well, at the moment I dont have more options regarding current system recovery / backup.
The encryption error resolves you by formatting the user partition by TWRP, in the option to format f2fs plus the installation of a custom Rom or Xiaomi.eu.
Look for tutorials and other reviews before testing these procedures.
Remember that there is a big achance of your ARB model as well.
Good luck.
PS. You can try dirty flash. Find an recovery Rom same version, and flash via TWRP.
Hello, I haveNokia 6.1 (2018) and I have just got it into a strange state. It happened during custom rom install, or to be more precise during the set-up (probably). I have finished setting up the Omni ROM from this thread (https://forum.xda-developers.com/nokia-6-2018/development/rom-omnirom-t3945850) and wanted to install magisk to have root.
After downloading the .zip file, I rebooted into TWRP (through the fastboot mode and using the "fastboot boot image.img" command) and TWRP asked for a password to decrypt the storage. I tried password that I am pretty sure is correct, but the TWRP insisted it is incorect. I tried several variations to it in case I made a misclick during a setup but no luck. I wiped everything (system, cache, data, sd) and through a fastboot mode I uploaded stock boot, vendor and system to both slots.
After the reboot, I am stuck on the password (system PIN, to be precise - not the SIM PIN, that is OK) screen. When I enter an incorrect PIN, it will say that the PIN is incorrect, but when I enter the correct one, screen just goes black for a while and I am back at the screen to enter the PIN.
Is there a way to get out of this mess? I am able to get into fastboot mode and boot recovery.
Any help would be much appreciated.
More details about the process as I forgot to include. TWRP used was 3.2.3 from this thread (https://forum.xda-developers.com/no...recovery-twrp-3-2-3-0-touch-recovery-t3825545). Stock FW (Nov 2019 version) used was from this thread (https://forum.xda-developers.com/no...de-how-to-make-backups-restore-stock-t3889815)
Before the OMNI ROM install I have tried stock system with custom vendor (version 2.2 from the thread linked in the OMNI ROM thread) which could also contribute to the failure, but the phone did not even boot (it got stuck on the "android one" logo). I hoped that I could at least get the ability to convert SD to internal storage, as that feature is disabled on stock, but with custom vendor it works (tested on the OMNI rom, which I managed to install correctly before)
I have also found here an OST tool, which could potentially help with the situation (I am not sure) but I am missing the original firmware files to use with this tool.
The problem must be with the internal storage encryption, which got messed up in the process (I am not still sure, what went wrong). Am I correct that now I would need to find the original loadout (is there something as RUU available fror this model?) and basically revert everything including the bootloader unlock and start from the begining? Could someone here point me in the right direction how to fix this issue?
If the only way is to pay someone to fix this issue, I will gladly provide any reasonable amount if it will resolve my problem.
So all I had to do was boot into TWRP and do a factory reset from there. How stupid of me that I did not try this.
Dear XDA-Developers, after installing August 2020 update for my Pixel 2 XL and possibly applying incorrect Magisk bootloader version, my phone doesn't boot anymore and is constantly stuck in bootscreen animation.
What I have tried so far to no result:
- Re-flashing both May 2020 (previous working version) and August 2020 without -w flag to preserve my data that I would ideally like to recover.
- Side-loading May 2020 and August 2020 OTA versions through TWRP
- Creating and booting from Magisk-core only image as per guide called "How to Create & Boot from a Magisk Core-Only Image to Fix a Bootloop Without Custom Recovery" (since I cannot post links in here).
While unpacking and repacking Magisk-core image I noticed that "BOARD_OS_PATCH_LEVEL 2020-05" indicating that I might have had the wrong version applied to it.
So looks like my only hope is finding magisk_patched.img file for August 2020 Pixel 2 XL (image-taimen-qq3a.200805.001) and trying to patch it to disable Magisk upon startup. Would anybody be so kind to post one here?
I have also tried to make data backup using TWRP, but it fails mounting /data partition and shows that it's 0 Mb.
Any other ideas to how to save the phone without wiping all the data would be greatly appreciated.
Thank you all very much for whatever suggestions you might have to help me!
hencrow said:
So looks like my only hope is finding magisk_patched.img file for August 2020 Pixel 2 XL (image-taimen-qq3a.200805.001) and trying to patch it to disable Magisk upon startup. Would anybody be so kind to post one here?
Click to expand...
Click to collapse
Magisk doesn't touch the bootloader, only modifying the boot image. Given your description of the issue, I don't believe Magisk to be the culprit here. Based upon personal experience, flashing a stock image using flash-all.bat, whether the -w flag is present or absent, totally removes Magisk as the stock boot image overwrites the modified version created by Magisk.
It's clear though that you have an issue, but how much of it is brought about by misconceptions and incorrect knowledge is unknown and at this point irrelevant. So what do you do now? Try backing up your data using the instructions here. But be prepared for the very real possibility that you have already lost all your data, and only a stock ROM install with the -w flag present will restore the device to working order.
Strephon Alkhalikoi said:
So what do you do now? Try backing up your data using the instructions URL. But be prepared for the very real possibility that you have already lost all your data, and only a stock ROM install with the -w flag present will restore the device to working order.
Click to expand...
Click to collapse
Thanks for getting back. I'm a little confused how can adb backup can work though if the only thing I can boot into is TWRP and even it fails to decrypt /data partition (it just shows "Could not mount /data and unable to find crypto footer" upon startup).
And with my very limited Android debugging experience wondering if things are really that hopeless that it's not possible to simply copy and decrypt user data partition or there aren't even any logs from failed Android boot attempts that can be looked at to at least diagnose the issue.
hencrow said:
Thanks for getting back. I'm a little confused how can adb backup can work though if the only thing I can boot into is TWRP and even it fails to decrypt /data partition (it just shows "Could not mount /data and unable to find crypto footer" upon startup).
And with my very limited Android debugging experience wondering if things are really that hopeless that it's not possible to simply copy and decrypt user data partition or there aren't even any logs from failed Android boot attempts that can be looked at to at least diagnose the issue.
Click to expand...
Click to collapse
It may not work, and in fact it probably won't, especially if TWRP can't mount the data partition. That's why I said you should be prepared for the very real possibility that you have lost all your data. As for getting logs to diagnose the issue, the only certain way to get a catlog is to record the logcat from the device on your PC as you boot it, via USB Debugging. Something that likely will not be of much help now, given what you have tried doing to resolve the issue.
At this point, in your position I would simply cut my losses and install a factory image and let it wipe the data. Once you are back up and running, you want to get into the habit of backing up app data. There are many apps that can do this, but regardless of the app used, backing up the app data to internal storage or to a location like Mega or Dropbox will make life easier if you ever encounter this again.
An update if anybody is wondering what happened - flashing Android 11 Beta 3 brought the phone back to life with all the data intact. All versions of Android 10 haven't even reached the booting stage where adbd was started and showed no logs.