Hi,
I made a backup using TWRP a couple of weeks ago of my custom ROM.
I attempted to restore this backup using TWRP Recovery today and after it restores and reboots, it always gets stuck on download mode. Prior to restoring, the system was working fine, with the Magisk image file (that comes with the custom rom) installed in the boot partition. I have also attempted to flash this file after restoring, no luck.
Any help is appreciated and please let me know what details I'm missing that can help with this issue.
I know there is an update available for TWRP (3.4.0), wondering if that would fix the issue.
Device: Galaxy S10+ Exynos (G975F)
Custom Rom: Lineage OS 17.1 with open_gapps-arm64 super
TWRP Version: 3.3.1-104_ianmacd
Magisk: 20.4
Update:
Solution: Restore backup without any image backup
Thanks to @[email protected],
found on this https://forum.xda-developers.com/ga...pdate-2020-t4067765/post82393905#post82393905
Help
I'm in the same trouble
Related
Hello out there,
my problem is a bit annoying. Everything is fine if I use my OP3T with Oxygen (4.0.3) and TWRP (3.0.3-1). But I want to use LineageOS with TWRP and cant, because my TWRP isnt working after flashing lineage.
"Normal"-Setup:
- TWRP 3.0.3-1
- Oxygen 4.0.2 or 4.0.3 (doesn't matter)
- supersu 2.79
- Encrypted Device
"Lineage"-Setup:
- TWRP 3.0.3-1
- lineageOS (lineage-14.1-20170214-nightly-oneplus3-signed.zip OR lineage-14.1-20170208-nightly-oneplus3-signed.zip - tried both, doesnt matter)
- supersu 2.79
- openGApps for 7.1 nano
- Encrypted Device
My Problem is, that I can boot up lineage and use it, but if I reboot into my TWRP to flash something or make some Backups, it asks for my encryption-passphrase, it says it is okay and boots into the twrp main-windows. After that I can't touch anything (stuck in mainmenu) and after a few seconds it results into a black screen (plus white LED) and I am forced to reboot the device. After that reboot I have to reconfigure lineage (seems to loose data).
Does anyone have an idea how to fix this annoying "bug"?
Thank you very much!
Atomique
EDIT: I found that Thread after searching for a issue like that in the lineageOS official Thread - I will try this and report! - Thank you! https://forum.xda-developers.com/on.../recovery-official-twrp-oneplus-3-3t-t3543391
I had the exact same problem when I hab LineageOS installed! It would always lose all its data. After flashing and reflashing a hundred times, I ended up reverting my OP3T back to stock using a OnePlus forum guide (I'm a new user, so I can't post the link). I am now back to OOS 4.0.3 but can't even get SuperSU to work. Whenever I flash it (with or without the dm-verity fix) the phone is stuck booting forever.
I found the post you linked to aswell but haven't tried flashing LineageOS using the new TWRP. But I can tell that the new version doesn't help rooting OOS...
Did you have any luck flashing LineageOS by now?
Edit: With the newest Lineage Version I always get an error when trying to flash it. Do you have the same problem? The nightly from two weeks ago seems to work better.
Use latest TWRP 3.0.4.1
nitinvaid said:
Use latest TWRP 3.0.4.1
Click to expand...
Click to collapse
That's what I'm doing... Could the dm-verity be a problem? There are two versions, one with opt and one with force in the name.
Thank you for your replies! The link (TWRP 3.0.4-1) worked like a charme!
@Tafelbomber: I would recommend you to start from scratch. But please be warned: you will loose your data! Make a backup first!
1. Delete everything with fastboot -w
2. Flash the recovery noted in my first post with fastboot flash recovery <twrp-filename.img>
3. Optional: Restart into the TWRP and flash the OOS 4.0.3 to make sure that you have a clean OS installed befor flashing lineage
4. Flash lineage OS + additional ZIPs (like supersu, betterbatterystats, Gapps etc)
5. Clean Dalvik and Cache!
6. Reboot and have fun. --> Sometimes you get problems with the encryption chain (Red Error --> in my case the fastboot -w did it for me)
Good luck - I will close this thread - thanks again for your help!
Atomique
EDIT: I want to close this thread, but I don't know how.
I have a oneplus 3t and am on OOS 4.0.3 and decided to upgrade to OOS 5.0. I downloaded the ROM, took a backup and then clean wiped my phone. Then I tried installing the ROM but it failed. So I decided to restore my backup from USB OTG. While restore failed and it showed error 255 while restoring data, so I wiped again and then restored everything except data. The phone rebooted and everything is fine except the phone is not detecting my sim card. I have tried restoring again and rebooting but it didn't work. I am using twrp 3.1.1
Please give a solution or tell me which ROM version to flash to solve this problem.
Just follow this guide to get back to factory default. And then try OTA update with the default recovery instead of TWRP.
https://www.google.se/amp/s/forum.x...ck-unbrick-tutorial-oneplus-3t-t3515306/page1
You need a special TWRP in order to upgrade to Android Oreo. Just google for Oneplus3 Oreo TWRP and theres a OnePlus-Forum Thread where you can download the TWRP that is needed for the Oreo Upgrade. Your Backup should work without Problems after you installed Oreo
just install bluSpark TWRP v8.61 from
https://forum.xda-developers.com/devdb/project/dl/?id=27655
and download official 5.0.1 ROM zip file from oneplus official site.
then you can proceed. You can use Magisk 15.3 after ROM installation for root access.
Make sure to reboot TWRP once after wiping everything from TWRP otherwise you may lose TWRP where stock recovery may take place.
I was running Sultan's latest version of CM which was discontinued somtime last year. So, I decided I should upgrade to the latest Sultan Lineage OS version. I updated TWRP to the most current version, took a Backup of the system using the new TWRP (so I could restore back to a working phone). I also downloaded the Sultan version of Lineage OS (and this is where my mistakes began). I accidentally downloaded the incorrect version for the OnePlus 1 and not for the OnePlus 3T. I should have done this from a computer and not from the browser on my phone to prevent this mistake.
So, in TWRP, I cleared cached and the system partition, then tried to install the Sultan Lineage OS. TWRP correctly told me that it was the wrong version for my phone. Okay, no problem. Then, my fallback also failed. I tried to restore the image that I had backed up of my working phone and the image loads properly. However, when the phone is rebooted, it is stuck in a bootloop. I can get into TWRP and the bootloader, but that's all I can do.
What are my options now?
(1) Can I use adb fastboot to copy over the correct version of Sultan's Lineage and go to that?
(2) Why is my recovery image not working?
I essentially have a phone that seems to be bricked. I hope that this is not the case. Any help is greatly appreciated.
weaponG said:
I was running Sultan's latest version of CM which was discontinued somtime last year. So, I decided I should upgrade to the latest Sultan Lineage OS version. I updated TWRP to the most current version, took a Backup of the system using the new TWRP (so I could restore back to a working phone). I also downloaded the Sultan version of Lineage OS (and this is where my mistakes began). I accidentally downloaded the incorrect version for the OnePlus 1 and not for the OnePlus 3T. I should have done this from a computer and not from the browser on my phone to prevent this mistake.
So, in TWRP, I cleared cached and the system partition, then tried to install the Sultan Lineage OS. TWRP correctly told me that it was the wrong version for my phone. Okay, no problem. Then, my fallback also failed. I tried to restore the image that I had backed up of my working phone and the image loads properly. However, when the phone is rebooted, it is stuck in a bootloop. I can get into TWRP and the bootloader, but that's all I can do.
What are my options now?
(1) Can I use adb fastboot to copy over the correct version of Sultan's Lineage and go to that?
(2) Why is my recovery image not working?
I essentially have a phone that seems to be bricked. I hope that this is not the case. Any help is greatly appreciated.
Click to expand...
Click to collapse
1. You can either sideload the correct version in TWRP and ADB. Or fopy the file to your internal storage using TWRP and ADB or by enabling MTP in TWRP (under Mount menu) and then flash it. Don't forget to do a factory reset in TWRP as you're changing ROMs.
2. What partitions were included in your backup?
If boot, data, and system were included then I have no idea why restoring it didn't work.
And, when you say "most current version of TWRP" do you mean version 3.2.1-0 from https://dl.twrp.me/oneplus3/ or something else?
Sent from my OnePlus3T using XDA Labs
BillGoss said:
1. You can either sideload the correct version in TWRP and ADB. Or fopy the file to your internal storage using TWRP and ADB or by enabling MTP in TWRP (under Mount menu) and then flash it. Don't forget to do a factory reset in TWRP as you're changing ROMs.
2. What partitions were included in your backup?
If boot, data, and system were included then I have no idea why restoring it didn't work.
And, when you say "most current version of TWRP" do you mean version 3.2.1-0 from https://dl.twrp.me/oneplus3/ or something else?
Sent from my OnePlus3T using XDA Labs
Click to expand...
Click to collapse
(1) I was successfully able to download the proper Sultan Lineage OS version for OnePlus 3T. I have copied that and the latest firmware sited in this link:
https://forum.xda-developers.com/on...t/op3-op3t-unofficial-lineageos-14-1-t3588696
(2) The following partitions were included: Boot, Data (excl. storage), Recovery, System, System Image, EFS. It is unknown as to why recovery failed.
(3) The version is Team Win Recovery Project (TWRP) 3.2.1-0
weaponG said:
(1) I was successfully able to download the proper Sultan Lineage OS version for OnePlus 3T. I have copied that and the latest firmware sited in this link:
https://forum.xda-developers.com/on...t/op3-op3t-unofficial-lineageos-14-1-t3588696
(2) The following partitions were included: Boot, Data (excl. storage), Recovery, System, System Image, EFS. It is unknown as to why recovery failed.
(3) The version is Team Win Recovery Project (TWRP) 3.2.1-0
Click to expand...
Click to collapse
Oh wow. I had to apply the Firmware Update, and now I am running Sultan's Lineage. This is truly exciting. The animated splash/intro screen is still occurring on the phone. This should be great. Thanks so much for your kind assistance.
I was running a custom ROM (Skydragon) earlier. I simply booted into TWRP, did the basic wipe then flashed the official zip file. Then after booting, its stuck on the boot animation for more than 20 minutes now. Any ideas how to resolve this?
I too faced the same issue. formating the data partition and flashing community beta build booted successfully for me. before you do this, completely back your phone contents to pc
You must flash with TWRP 3.2.3.0 or older!
i had the same issue. formated data had 3.3.0 twrp but still bootloop so i used unbrick tool to put my phone back to stock and then updated to last build though stock recovery and then unlocked bootloader, installed twrp, magisk and done.
After installing at least one Magisk module the phone bootloops every 2nd reboot and it is consistent. Flashing a no-verity zip gives a few more reboots before bootlooping but the issue is quite annoying because I need to restore a backup from TWRP every time a bootloop occurs, so I have to reinstall everything again.
Maybe returning to full stock firmware (I have the original boot image, but not the original recovery) can help, but the lolinet mirrors do not have the latest firmware available.
Apparently, wiping data after restoring backup helped a lot, phone has survived 5 reboots so far with 2 Magisk modules flashed
Nevermind, latest reboot was a bootloop, but I think the culprit here is the Magisk Manager for Recovery Mode, I will restore backup again and see if that module is the cause of it
If it helps, TWRP showed an error before cleaning caché:
"E:Error creating fstab"