Hi all,
I'm using Unofficial LineageOS 14.1 with TWRP 3.1.1-0
Every time I try to do nandroid backup via recovery, I get a random reboot. It doesn't happen at a specific backup section.
I then have to boot into recovery and start the backup again and again until it completes it without reboots.
Is it a known issue? Is there a fix?
No it is not a known issue. Use this Twrp instead: https://www.google.co.in/amp/s/foru...elopment/recovery-twrp-3-0-3-k1-t3563692/amp/
Related
Hi.
Today I wanted to upgrade from CM11 to CM12.1, but I had to upgrade the bootloader first. It all worked and I'm now on bootloader version 41.18.
When I flashed the ROM it flashed in 20 seconds from an USB stick. It seemed a little to fast. When I rebooted it worked fine and I was on Android 5.1.1, but after installing SuperSU and rebooting I stuck into a bootloop.
I'm now in a bootloop and when I try to enter the recovery the TWRP splash screen comes up, but then it goes into the bootloop again.
I have the XT1032 and my TWRP version is 2.8.6.0 and I have a TWRP backup from CM11
If someone could push me in the right direction how I can access TWRP then that would be great.
Thanks in advance.
Quick update
The phone now booted into TWRP, but when I do a restore to my backup the phone goes back to the bootloop. The same happens when I try to wipe.
zomgwalrus said:
The phone now booted into TWRP, but when I do a restore to my backup the phone goes back to the bootloop. The same happens when I try to wipe.
Click to expand...
Click to collapse
I have the same issue, cannot get into twrp, how did you managed to boot into TWRP?
i had same issues in my moto g xt1032 i tried below CM12.1 works without issues.
go recovery --- wipe---- format data
and try step install steps like install rom zip & gapps
Ok, first what do you use to flash recovery, can you reflash recovery with the lastest TWRP version (2.8.7.0) and post back the logs here? Then tell me if you can get into recovery
Its common place that twrp cause bootloop with backups.
No problem try to
Install new twrp using fastboot mode it will be work fine
Hello Friends,
I updated Redmi 1s to twrp 3.0.0.0 custom recovery and tried to restore cm13 rom backup and miui 7. Unable to restore both backup via twrp. But installed (flashed) miui 7 global ROM via twrp 3.0.0.0. God grace everything gone well and it's working fine. I rechecked the twrp 3.0 but my Redmi booted into Mi recovery. Since then I tried to install twrp as update. zip through mi recovery, it says unable to update. Tried many times but nothing happens.
Please advise me how to flash which version of twrp and get access to port Roms.
Thanks and regards
TWRP 3.0.0.0
The above thread I asked for a help for my redmi 1s how to flash twrp 3.0 as I tried to flash through mi recovery, updater and fastboot mode. Nothing gone in my way. At lost I succeed by rooting with good and saviour app and flashed twrp 3.0.0.0 via flashify. Now I got the twrp and able to flash. But I have a problem with the twrp 3, when I do backup and restore, it is fine with backup but getting error while restore. Still working out to find solution.
TWRP
I have flashed lower version of twrp 2.8.7.0 instead of 3.0 . Now I am not getting any kind of error message if I do a backup, restore, wipe or install. So if anyone come across such problems do the same.
KrishTKavin said:
I have flashed lower version of twrp 2.8.7.0 instead of 3.0 . Now I am not getting any kind of error message if I do a backup, restore, wipe or install. So if anyone come across such problems do the same.
Click to expand...
Click to collapse
Even I am having the same version but twrp freezes on it's cover page plz help
Droid Turbo (quark) is the device in question...
So over the weekend I attempted to boot into TWRP recovery and TWRP ended up in a bootloop. Never had this happen before (version 3.1.1-0 is installed). Attempted to reinstall version using Flashify, however Flashify hung up and stalled when I'd click on "search for file to flash" or whatever it's called. So I (successfully) flashed TWRP version 3.2.1-0 using the TWRP app, rebooted to recovery, and TWRP still bootlooped (showed that version 3.2.1-0 was installed). Using TWRP app I (successfully) reflashed the 3.1.1-0 version .img file I had saved from the first time I flashed TWRP months ago, rebooted to recovery, and TWRP still bootlooped (showed that version was again 3.1.1-0).
I'm fairly certain that some rogue apps I installed caused the issue. It's the only thing I can think of as to why TWRP is messed up. I've uninstalled the rogue apps with Titanium Backup, TWRP still bootloops.
Any ideas on what I've botched, and how to unbotch it? Phone otherwise works as it should booting up normally, running normally, etc. I'm just at a loss for any future tinkering I want to do since I can't get into TWRP to make or restore backups.
Hello,
I encountered a annoying problem with my oneplus 6 tonight, a device i am fairly new with, previously owning a oneplus 3t.
While restoring a TWRP backup out of lazyness i screwed up something in my device to the point that it was booting in TWRP on the second try (the first was just a bootloop).
I said ok, there's something wrong, lets do that again and booted in TWRP (blu_spark, latest). There, i was not asked about any decryption password and obviously everything was encrypted.
I re-installed everything now using MSM tool and re-rooted but this is a painful process that takes time.
Anyone encountered that?
I am, and was on latest OOS with stock kernel, latest TWRP blu_spark (the stock one gives me QUALCOMM CrashDump when trying to boot from fastboot in it), rooted with magisk (latest 18.1) and using magisk custom rom on top of stock (XXX_nolimits, latest).
Any of you encoutered this issue?
Thanks!
0xPraeT0Rian said:
Hello,
I encountered a annoying problem with my oneplus 6 tonight, a device i am fairly new with, previously owning a oneplus 3t.
While restoring a TWRP backup out of lazyness i screwed up something in my device to the point that it was booting in TWRP on the second try (the first was just a bootloop).
I said ok, there's something wrong, lets do that again and booted in TWRP (blu_spark, latest). There, i was not asked about any decryption password and obviously everything was encrypted.
I re-installed everything now using MSM tool and re-rooted but this is a painful process that takes time.
Anyone encountered that?
I am, and was on latest OOS with stock kernel, latest TWRP blu_spark (the stock one gives me QUALCOMM CrashDump when trying to boot from fastboot in it), rooted with magisk (latest 18.1) and using magisk custom rom on top of stock (XXX_nolimits, latest).
Any of you encoutered this issue?
Thanks!
Click to expand...
Click to collapse
All you need to do is backup data. There are multiple threads explaining nandroid backup and restore. Just install OOS and TWRP, reboot recovery and flash all mods that you use, then restore data only and reboot.
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.