I am having an issue with TWRP TWRP 3.3.1-18 at the moment and wonder what I am doing wrong. I backed up my Oneplus 6 in February then the phone offered my a system updat at the weekend which I accepted. I later went to use Titanium backup then realised I had lost roots rights due to the update so I reflashed (TWRP if I remember) and Magisk, however the phone got stuck in the bootloop where 2 white dots were spinning around a red circle. After searching and trying one thing after another I resolved it by using the msm download tool. So thats the first issue and i dont know what caused it. Onto the TWRP issue. After the phone was recovered and all the updates to Android 10 was accepted and bootloader unlocked, TWRP and Magisk 20.5 flashed, I restored my February backup which is possibly Android 9. When I rebooted I was then in a fastboot loop. I again restored using the MSM tool and tried again, the same happened. The next time I first backed up the new Android 10 system after the update then tried to restore the February backup one last time (cleared the dalvik and factory reset) but had the same issue so after restoring one more time I instead tried to restore the new nandroid backup and have the same issues. Can anyone suggest why this is happening with my TWRP backups?
Related
First off I am on mdk and rooted and up until today have been running hd 10.2. I had been having some weird things happen with twrp 2502 so I went into goo and tried to update to the newest version of twrp. it downloaded and went through with everything and I rebooted into recovery. once I got into recovery it was showing I was still on 2502, but it was asking for a password which I had never seen before. I backed out and tried to boot into my rom again and it got stuck on the samsung custom screen. pulled the battery a few times and still kept getting stuck. went back into recovery and tried to restore a known good backup that I had restored before, but it keeps failing. I had rls12 on my phone so I tried installing it dirty since I cant wipe anything due to the whole password thing in twrp which said it was succesful but still gets stuck on the samsung custom screen. it sits there for about 10 seconds and loops. I tried about 10 more times to get my backup restored and it finally finished and booted into the rom. I left it this way for an hour or so and did some stuff with my phone, tried to update twrp again which did the same thing again and still shows 2502. after the reboot I am back to the same problem of not being able to do anything in twrp except restore or dirty flash, I cant get the usb to mount in twrp so I cant try putting another rom on the phone unless I go and buy a micro sd adapter.
I am in the process of downloading a stock mdk rom to try and flash in odin, but is there anything I can try before I go through with this, or is it pretty much my only option.
after some more research I think I figured out what caused all this. I wiped the data partition with the old version of twrp which screwed it up pretty bad. Apparently the older versions of twrp were known to have this problem. I kept trying to restore, but trying to restore kept failing on the data partition. After about 25 attempts of trying to restore just the data partition I was able to get it to work finally, and then I restored the the others and got it to boot back into the rom. like an idiot I rebooted the phone back into recovery after it finished and had the same problem again. another couple hours wasted trying to restore the data partition and it worked again and this time i was able to get twrp to update and then went back to recovery and formated the data partition again and it seems to have fixed the problem. Now to figure out why hd rls 12 wont install.
I seem to have shot myself in the foot recently. I've been on CM 13 for nearly a year now and I wanted to try out LineageOS for the hell of it since I am planning to get a new phone and I wanted to put LineageOS on that as well. So I downloaded an unofficial build of LineageOS for the G850W and followed some basic instructions: backup with TWRP, wipe with TWRP, and flash both the ROM and OpenGApps with TWRP. All three of these went well and I was able to install LineageOS. Now the problem: I tried restoring my backup (a CM 13 based backup) thinking I could restore some things from that backup and when I went to restart the CM boot screen popped up and I immediately knew I must have messed up. Checking my backup it contained boot, cache, system, EFS, modem, and a couple other folders/partitions that I can't remember off the top of my head. I then simply tried to redo everything again: backup, wipe, flash. While I am able to backup, wipe, and flash, and I am able to proceed past my device's boot screen, the Lineage OS boot screen seems to either be stuck or it is taking a long time. I've waited for 30 minutes with no change and I am sure that shouldn't be the case at all. Stock ROM was the same way, sitting on the Samsung logo with the sparkles forever. I managed to reinstall CM 13 but it's a very buggy install as sometimes it restarts randomly and goes through the "preparing applications" thing upon restart. Furthermore data doesn't seem to work and IMEI info is not found and sometimes in the stock recovery mode it shows that the EFS partition could not be found. Same thing happens when I poke around in ADB, I do not see any EFS partition when I type in the mount command. Clearly I've really messed things up. So would there be some way to fix things considering I do have a backup of things before I messed things up? How would I use my backup to fix everything? Would there be other tools I should be trying? Any help would be appreciated.
Flash original firmware
echo124 said:
Flash original firmware
Click to expand...
Click to collapse
I did: "Stock ROM was the same way, sitting on the Samsung logo with the sparkles forever".
Erase everything on your phone (aftet backup) and flash stock again.
echo124 said:
Erase everything on your phone (aftet backup) and flash stock again.
Click to expand...
Click to collapse
I've done that as well already, still the same issue.
:fingers-crossed:Flash stock, flash same version twrp used to backup, flash same version of cm 13 used on backup, try restore.
I'll try and keep this short and to the point, any other info you require to help me out i'll add.
My Z5c is running 32.4.A.1.54, unlocked bootloader and rooted using rootkernel which adds TWRP.
Straight after rooting and after initial setup of the phone I started TWRP and created a backup, all available partitions were selected and the back completed. I then copied it to my PC.
Anyway, no the problem. I was messing with the phone and then after every boot of the phone i kept getting some app crashes. No problem i thought i'll just restore my backup in TWRP. I selected to restore the system and data partion ONLY, then wiped cache & dalvik and rebooted.
It didn't reboot, just the sony logo then a loop back to the sony logo and then into TWRP again. What did I do wrong?
So i decided to restore all partitions except the TA one and that resulted in the same problem. So recover i just flashed stock with flashtool and all is well.
My question is regarding TWRP and restoring a backup. Which partitions do you have to restore? All of them? What is safe to omit when doing a restore?
andybog said:
I'll try and keep this short and to the point, any other info you require to help me out i'll add.
My Z5c is running 32.4.A.1.54, unlocked bootloader and rooted using rootkernel which adds TWRP.
Straight after rooting and after initial setup of the phone I started TWRP and created a backup, all available partitions were selected and the back completed. I then copied it to my PC.
Anyway, no the problem. I was messing with the phone and then after every boot of the phone i kept getting some app crashes. No problem i thought i'll just restore my backup in TWRP. I selected to restore the system and data partion ONLY, then wiped cache & dalvik and rebooted.
It didn't reboot, just the sony logo then a loop back to the sony logo and then into TWRP again. What did I do wrong?
So i decided to restore all partitions except the TA one and that resulted in the same problem. So recover i just flashed stock with flashtool and all is well.
My question is regarding TWRP and restoring a backup. Which partitions do you have to restore? All of them? What is safe to omit when doing a restore?
Click to expand...
Click to collapse
The old TWRP in rootkernel had a backup problem if i remember correctly. Use a newer TWRP.
Thanks, i'll use 'your' TWRP from here.
after a successfull backup of a custom rom via twrp when i am trying to resore from the backup and after full restoring when it finally boots up it is stuck in the bootlogo and a force reboot wont solve the problem i think its a decreption issue might be although i may be wrong,any one knows how to deal with that?is twrp supports backup restore for poco f1????there is also an another issue rebooting into twrp freeze twrp a couple of minutes and then its working!any one knows how to deal with that too?
So, I can't restore my backup due to the error above. When I restore my backup, I get that error and a reboot loops me straight back into TWRP. You can read all that stuff below if you need the backstory.
(I had Lineage OS 18.1 installed and wanted to restore a backup from two weeks ago. So, I booted into TWRP, did a normal factory reset and restored the Backup of Lineage. However, it put out an error regarding something in root (structure needs cleaning). I tried rebooting into system, but it ended in fastboot mode. So I googled it and one thread said you can solve that by formatting system. "System" is backed up anyway, so I thought there was no harm, wiped it and restored the same backup once again. No error this time.
However, when I rebooted into system, the unlock pattern didn't work any more, even though I never changed it and always use the same one. I had to reboot into recovery, and now the TWRP unlock pattern didn't work either. Had to skip it and did another reset.
Now, every time I restore a backup (and those backups contain basically every partition available) it works, but when I reboot into system it just stops at the boot logo, then reboots into recovery. Basically a boot loop plus. Tried a fresh flash, same loop.
Also, all of my pictures and downloaded files are gone, because it's encrypted. I had to wipe data, which led to the whole encryption issue going away, however, I'm still stuck in that loop.
Does anyone know how to solve this cluster****? How do I get it to boot into system?
Edit: Managed to flash LIneage new after wiping data and system and it actually boots, hallelujah, but when I flash the back up I'm still at square one with the same fail and it fails to boot. )