I made a full backup via TWRP before testing out OOS13, and when did a wipe, and a full restore I got a Qualcomm modem boot error "Crashdump Mode".
I flashed a clean signed flashable zip od OOS11 11.0.12.12 and tried again and again. I have been 12h of trying so Im lost.
Long story short:
If I have a full twrp backup, how can I restore it and not get a Qualcomm modem boot error?
walthroughs of restoring are old and dont have the "super" restore option I includes more than just system.
Im at a loss.
Update: I got rid of the Qualcomm modem boot error "Crashdump Mode".
My problem is that if I restore the DATA partition, with or without other partitions, the phone boots, with logo, but the screen turns black and when holding power and/or volume I get a prompt that "com.android.phone" is crashing.
So in short, any solution for this? I thought a complete Nandroid backup would exclude these things.
It's normal to get the black screen and phone crash message after restoring data in TWRP. Just reboot the phone again and it should then come up cleanly.
Read the OP of the TWRP thread. It tells you to do this.
BillGoss said:
It's normal to get the black screen and phone crash message after restoring data in TWRP. Just reboot the phone again and it should then come up cleanly.
Read the OP of the TWRP thread. It tells you to do this.
Click to expand...
Click to collapse
This is probably the link to the thread, and thanks, it was eye opening, disable password before restoring the data partition and removing the sim card might been what causes the com.android.phone to crash and the display to be blank other than the crash pop-up.
You'll find similar requirements for TWRP 12 when restoring a backup (look in the TWRP 12 thread in the same forum).
Related
Edit: Since I am the impatient guy of course I still meddled with the backup after posting this thread. By chance I found a solution that finally worked for me. Latest Oxygen Os 9.0.2 stable without root.
Note that I will list every step even it may be that it hasn't contributed anything to the solution:
1. From fastboot I booted into latest blu_sparc TWRP.
2. I plugged the phone into USB and copied all files from my backup into the usual TWRP folder.
3. I flashed only DATA, nothing else.
4. From TWRP I rebooted directly into bootloader/fastboot.
5. Then I ram the flash-all-partitions.bat from Mauronofrio provided by this thread https://forum.xda-developers.com/oneplus-6/how-to/rom-stock-fastboot-roms-oneplus-6-t3796665 .
6. Crucial step: At the beginning, it asks "Wipe all data?". SELECT NO. It will start "restoring" all other partitions.
7. Reboot the phone and it should work as you left it before creating the backup.
Note that this method worked the restoration of backup data from the same OS and same version. Feel free to try it out on other system images. It's ugly and inconvenient, but it seems to work.
Hey guys,
is there a fail safe way to restore data from a clean twrp backup without soft bricks or PIN error?
I tried to restore a very recent TWRP backup but had serious trouble. At first, it rebooted just fine but upon trying to unlock the device with 4-digit pin it suddenly told me that my usual pin isn't working.
Then I tried deleting the lockscreen.db and other related files. Rebooted and got into the OS, but it got stuck at "starting up device".
The I did a complete wipe without internal storage and tried it again. Then it wouldn't even boot and I had to use the flash-all.bat to flash all partitions "manually" to get it working again.
Now I am afraid of using Oneplus 6 if it's impossible to make a seamless backup/recovery. Is there a guide on how to do this?
Thank you in advance!
This is a known issue though. If you want to make a usable backup in TWRP: Remove the PIN (screen lock), do the backup, and then activate the screen lock again.
efex said:
This is a known issue though. If you want to make a usable backup in TWRP: Remove the PIN (screen lock), do the backup, and then activate the screen lock again.
Click to expand...
Click to collapse
I remember having read a thread with this hint too and disabled my security pin in a temporary working OS. Then I did the flashing stuff and I just noticed that my now working restored phone doesn't have a pin anymore. So basically removing this pin on a data backup will make things go smooth? I will keep this in mind, thank you
Hey,
Quick rundown: Stuck in a bootloop to some sort of empty bootloader screen which has the readout:
"Start/Restart Bootloader/Recovery Mode/Power Off"
"Press volume key to select, and press power key to select"[Regarding above options]
"FastBoot Mode
PRODUCT_NAME - sdm845
VARIANT - SDM UFS
BOOTLOADER VERSION -
BASEBAND VERSION -
SERIAL NUMBER - [Gonna leave this out for now]
SECURE BOOT - yes
DEVICE STATE - unlocked" [this line is in red]
Every choice besides Power Off returns me to the same window. What can I do to recover from this?
Background:
So I was trying to update my OP6 to the current OxygenOS while keeping my root using TWRP and Magisk, which I've done in the past without any issue(i.e. go in recovery flash OS, flash current TWRP, reboot back to recovery, flash current Magisk as I understand it). However this time I was running into an issue flashing the Oxygen update getting an error that said it "failed to map file" for the zip. My first instinct was to update TWRP to see if the newest version didn't run into this issue so I flashed that followed by the current Magisk(no reboot in between). After booting back to standard operations everything seemed fine. I went back into recovery and tried the OS update again, but hit the same issue.
I couldn't find anything specific to OP6 with this issue, but similar questions with other devices suggested clearing the dalvik cache, which I tried to no useful effect. Then I came across this thread (forums.oneplus.com/threads/oxygen-os3-i-have-a-problem-please-help.440587/page-2 too new to hyperlink) and did what I think really messed me up which was boldly follow this guy's advice to do an advanced wipe of everything but internal storage(I also left USB storage intact) from TWRP. This failed to fix the issue with the file mapping error when I subsequently tried to flash the update, though I was able to flash TWRP and Magisk successfully again before rebooting and ending up in this loop.
Any assistance in fixing this or general tips on how to not be foolish when messing around with this stuff is greatly appreciated.
Update:
So I followed the advice gleaned from the resourceful person here(https://forum.xda-developers.com/oneplus-6t/help/bootloader-baseband-versions-blank-t3927565) to try working with the device from my computer with fastboot. At first it would recognize the device as "Android" but be unable to find a driver for it and adb/fastboot both failed to recognize it as a device. After installing MiniTool(more as a way to backup what was on the SD card) the proper device driver also got installed and I was able to access it with fastboot; I ran into similar issues as the linked thread above, solved it by switching to b(still failed) then back to a.
Currently I've got it booted into TWRP and I'm working on getting the current Oxygen .zip copied onto the phone storage but the transfer keeps failing after moving a negligible amount.
Update 2:
Via TWRP was able to sideload the current up-to-date standard OS onto it, however my Google backup seems to have decided to disappear on me and the only OP backup I have is ages old. Anyone have recommendations on data recovery tools?
next time just dont change the build.prop file.
serious, it just breaks the system.
heppened to me too.
NickTheHuy said:
next time just dont change the build.prop file.
serious, it just breaks the system.
heppened to me too.
Click to expand...
Click to collapse
Good to know, thanks for the info!
I assume that happened when I messed around with advanced wipe, do you know which of the folders I selected that would have been under? And just for future awareness, would that have not occurred had I just used TWRP's standard wipe instead?
You can run a program that will install 9.0.6 from scratch, running a batch file...
Save my life before yesterday....
Your device is bricked
If able to access the TWRP recovery then boot into twrp and try to get all the data stored in your computer.
Then use the Qualcomm flash tool to completely recover from your hard bricked OP6.
from here https://forum.xda-developers.com/oneplus-6/how-to/op6-collection-unbrick-tools-t3914109
Then its easy, again unlock boot-loader flash TWRP and magisk.
Spent about 1 entire day now and I think am in worse shape than when started.
Rooted with Magisk went from 10.3.3 to 10.3.4, and the phone was working, but didn't have TWRP recovery.
So, putting that back on is when the trouble started. Got TWRP on, and all the phone would do was boot to recovery.
Have since tried lots of things, and learned, apparently a TWRP backup is of no use whatsoever - can't restore the phone from the backup. (Restore "restores" but it doesn't boot.)
As I tried different things (flashing the full 10.3.3 and/or 10.3.4 OTA), at one point I got the phone back booted, but wifi wouldn't turn on and the cell signal didn't work - and now, I'm at a point where with TWRP in either slot A or slot B, cannot mount Data partition.
Really stuck now - don't know what to do.
I have TWRP backup of 10.3.3 before I did the upgrade - but doesn't seem like it can be restored, and now I don't know if there's anything I can do to mount Data partition again?
What can I do?
Do I have to basically factory reset the phone? Any suggestions?
TIA!
relaxable said:
Spent about 1 entire day now and I think am in worse shape than when started.
Rooted with Magisk went from 10.3.3 to 10.3.4, and the phone was working, but didn't have TWRP recovery.
So, putting that back on is when the trouble started. Got TWRP on, and all the phone would do was boot to recovery.
Have since tried lots of things, and learned, apparently a TWRP backup is of no use whatsoever - can't restore the phone from the backup. (Restore "restores" but it doesn't boot.)
As I tried different things (flashing the full 10.3.3 and/or 10.3.4 OTA), at one point I got the phone back booted, but wifi wouldn't turn on and the cell signal didn't work - and now, I'm at a point where with TWRP in either slot A or slot B, cannot mount Data partition.
Really stuck now - don't know what to do.
I have TWRP backup of 10.3.3 before I did the upgrade - but doesn't seem like it can be restored, and now I don't know if there's anything I can do to mount Data partition again?
What can I do?
Do I have to basically factory reset the phone? Any suggestions?
TIA!
Click to expand...
Click to collapse
If you still have the cellular and wifi problem then you are not alone. Simply flashing android 9 image via edl mode and installing update to android 10 locally fixed for me. As you boot to 9 don't turn on wifi or cellular just download the update packages via pc, copy to internal storage then local update via system updates. Once you are on android 10 then install TWRP and root. TWRP backup only work if your data partition is decrypted.
relaxable said:
Spent about 1 entire day now and I think am in worse shape than when started.
Rooted with Magisk went from 10.3.3 to 10.3.4, and the phone was working, but didn't have TWRP recovery.
So, putting that back on is when the trouble started. Got TWRP on, and all the phone would do was boot to recovery.
Have since tried lots of things, and learned, apparently a TWRP backup is of no use whatsoever - can't restore the phone from the backup. (Restore "restores" but it doesn't boot.)
As I tried different things (flashing the full 10.3.3 and/or 10.3.4 OTA), at one point I got the phone back booted, but wifi wouldn't turn on and the cell signal didn't work - and now, I'm at a point where with TWRP in either slot A or slot B, cannot mount Data partition.
Really stuck now - don't know what to do.
I have TWRP backup of 10.3.3 before I did the upgrade - but doesn't seem like it can be restored, and now I don't know if there's anything I can do to mount Data partition again?
What can I do?
Do I have to basically factory reset the phone? Any suggestions?
TIA!
Click to expand...
Click to collapse
Hi,
Just a suggestion, was in this predicament before and the the thing that save me was my OTG USB stick with a USB C adapter, moved the latest rom(full rom 2.4gig) to it with TWRP installer , wiped( factory reset in twrp and installed the full update followed by TWRP installer. Reboot into recovery and did the same steps,
Reboot system,
Could never get MSM to work always param preload nonsense.... LOL.
relaxable said:
Spent about 1 entire day now and I think am in worse shape than when started.
Rooted with Magisk went from 10.3.3 to 10.3.4, and the phone was working, but didn't have TWRP recovery.
So, putting that back on is when the trouble started. Got TWRP on, and all the phone would do was boot to recovery.
Have since tried lots of things, and learned, apparently a TWRP backup is of no use whatsoever - can't restore the phone from the backup. (Restore "restores" but it doesn't boot.)
As I tried different things (flashing the full 10.3.3 and/or 10.3.4 OTA), at one point I got the phone back booted, but wifi wouldn't turn on and the cell signal didn't work - and now, I'm at a point where with TWRP in either slot A or slot B, cannot mount Data partition.
Really stuck now - don't know what to do.
I have TWRP backup of 10.3.3 before I did the upgrade - but doesn't seem like it can be restored, and now I don't know if there's anything I can do to mount Data partition again?
What can I do?
Do I have to basically factory reset the phone? Any suggestions?
TIA!
Click to expand...
Click to collapse
I'm not sure what you did.
How I normally upgrade is:
1. Local install
2. Install Magisk after OTA option
3. Reboot
4. Local install again, the other slot
5. TWRP zip install from Magic (do not reboot)
6. YOU ARE NOW UNROOTED.
7. Use Magisk Manager to do direct install (do not reboot)
8. Use Magisk Manager to do OTA install
9. Now reboot.
You have same firmware, TWRP and root on both slots.
If you can flash the stock boot image from 10.3.4 you can recover.
Thanks for all the replies.
I wish I could have done what Tech_Head wrote, but it wasn't happening for me.
I couldn't flash using OTG either as I couldn't mount USB with TWRP.
In the end, I was able to get back to life using the Fastboot flash method from This Thread, but, also not without complication
Hi there, Thaught, I was on the save side for 2 years, having my TWRP, made a backup after every change on the 12+, now I had to recover it...
Steady installed TWRP 3.3.1.0 on 1.68.401.6 does a restore without errors, restart ends with bootloop.
So I flashed new with 1.53.401.5, tried to fastboot boot twrp.3.2.3.3 and restore my backup -> bootloop
Flashed 1.53.401.5 again, made a backup of that fresh system with booted TWRP, to test that restore, brings the same bootloop.
Have to say, the twrp versions are the right ones for the used SW versions. Decryption is working.
Where is the blind spot in my brain??
Please delete my ask here, I'll try my luck in TWRP thread. Still my problem.
Hello,
I'm stuck on TWRP, no way to load Android.
TWRP wasn't reading the partition so I tried to repair, pass to EXT2 and back to EXT4.
All got stuck on TWRP, I could only go to fastboot, at boot it goes back to TWRP automatically. The message on TWRP console is :
"Android Rescue Party trigger! Possible solutions?
Either :
1) Wipe caches, and/or
2) Format data, and/or
3) Clean - Flash your ROM
The reported problem is:
"init_user0_failed"
Unable to decrypt FBE device."
TWRP version 3.6.2_12-MI10Ultra_v3.7_A12
First ROM present on device: xiaomi.eu_multi_MI10Ultra_22.6.15_v13-12-fastboot.zip
Second time I tried to flash with fastboot and XiaomiFlash the same ROM, successfully installed, but I was still stuck in the loop.
Third time I flashed xiaomi.eu_multi_MI10Ultra_22.6.29_v13-12.zip with TWRP, successfully, but I'm still stuck on the same loop, Android won't load.
Please I need help, I use the phone for work and actually I've been without for a whole day.
How can i fix TWRP possibly without lose all my apps and data?
sergio-bodyweb said:
Hello,
I'm stuck on TWRP, no way to load Android.
TWRP wasn't reading the partition so I tried to repair, pass to EXT2 and back to EXT4.
All got stuck on TWRP, I could only go to fastboot, at boot it goes back to TWRP automatically. The message on TWRP console is :
"Android Rescue Party trigger! Possible solutions?
Either :
1) Wipe caches, and/or
2) Format data, and/or
3) Clean - Flash your ROM
The reported problem is:
"init_user0_failed"
Unable to decrypt FBE device."
TWRP version 3.6.2_12-MI10Ultra_v3.7_A12
First ROM present on device: xiaomi.eu_multi_MI10Ultra_22.6.15_v13-12-fastboot.zip
Second time I tried to flash with fastboot and XiaomiFlash the same ROM, successfully installed, but I was still stuck in the loop.
Third time I flashed xiaomi.eu_multi_MI10Ultra_22.6.29_v13-12.zip with TWRP, successfully, but I'm still stuck on the same loop, Android won't load.
Please I need help, I use the phone for work and actually I've been without for a whole day.
How can i fix TWRP possibly without lose all my apps and data?
Click to expand...
Click to collapse
Afternoon matey, not to sure if this is helpful or not, may not be even specific to your device, but the error is the same error, so may shine a little light on the error.
Unable to decrypt FBE device
Plz anybody help this out... I unlocked bootloader, then immediately flashed Pitchblack recovery, then booted into recovery. Initially console shows decrypted FBE device with default password. But Encryption status : Encryped So I went into wipe...
forum.xda-developers.com
plegdroid said:
Afternoon matey, not to sure if this is helpful or not, may not be even specific to your device, but the error is the same error, so may shine a little light on the error.
Unable to decrypt FBE device
Plz anybody help this out... I unlocked bootloader, then immediately flashed Pitchblack recovery, then booted into recovery. Initially console shows decrypted FBE device with default password. But Encryption status : Encryped So I went into wipe...
forum.xda-developers.com
Click to expand...
Click to collapse
Forgot to add, would recommend reading the whole thread, you can then judge what actually works or not before trying
plegdroid said:
Forgot to add, would recommend reading the whole thread, you can then judge what actually works or not before trying
Click to expand...
Click to collapse
Of course, thx.