Hi folks,
I recently upgraded my TWRP from 3.0 (alka I think) to TWRP 3.0.2-2 and since then I get these error messages.
It occurs when I create a backup.
Any idea what's the cause of this?
Have you tried ZCX?
Change the recovery to zcx and try!
gozzaa said:
Hi folks,
I recently upgraded my TWRP from 3.0 (alka I think) to TWRP 3.0.2-2 and since then I get these error messages.
It occurs when I create a backup.
Any idea what's the cause of this?
Click to expand...
Click to collapse
Do a complete wipe, it was fixed for me.
Related
I use the last official ROM and I've installed TWRP recovery + Gapps.
After I've installed google calendar and when I've started the program I get EVER a message that say: "unfortunately, calendar has stopped".
Any solution for solve this?
Thank you in advance.
cron0s879D said:
I use the last official ROM and I've installed TWRP recovery + Gapps.
After I've installed google calendar and when I've started the program I get EVER a message that say: "unfortunately, calendar has stopped".
Any solution for solve this?
Thank you in advance.
Click to expand...
Click to collapse
Hello,
I read someone had same problem, cleared the cache for the app and installed the app again.
How did You install the TWRP ?
I am about to install recovery CWM or TWRP on A820 with stock rom, what is easiest ?
1rnst said:
Hello,
I read someone had same problem, cleared the cache for the app and installed the app again.
Click to expand...
Click to collapse
Thank you. I try this but don't work.
I find this rom that solve this problem (I install the last version):
http://www.needrom.com/mobile/lenovo-a820-12/
1rnst said:
How did You install the TWRP ?
I am about to install recovery CWM or TWRP on A820 with stock rom, what is easiest ?
Click to expand...
Click to collapse
It's the same. I test 2 programs. TWRP is with windows and CWM is with cmd (only text). TWRP in version 2.4 have a bug and I get an error when I make a backup so I prefer CWM until anyone cook the TWRP 2.5 for own A820.
you visit this russian forum for get CWM or TWRP, the russian forum is a best forum for this phone that I know if you are not xina-speaker
http://lenovo-forums.ru/forum/157-lenovo-ideaphone-a820/
use google translator if you are not russian
Hello. So I was on AllianceROM build 25 on 4.3 until today. I decided to go try out the 4.4.4 LiquidSmooth ROM, so I flashed the ND7 modem and the rom. Things were alright, but after I installed GApps, I got force closes over and over to where it was unusable. So I booted back into recovery and now TWRP fails every time at "restoring system" from my backup .
I believe I backed up my working ROM with TWRP 2.5.0.1, I flashed LS ROM with CWM to see if it would help with force closing. It didn't so I reflashed TWRP 2.5.0.1 as recovery and tried restoring it from there, and haven't had any luck.
Anyone have any pointers? Suggestions? Have you had a similar situation?
falkon114 said:
Hello. So I was on AllianceROM build 25 on 4.3 until today. I decided to go try out the 4.4.4 LiquidSmooth ROM, so I flashed the ND7 modem and the rom. Things were alright, but after I installed GApps, I got force closes over and over to where it was unusable. So I booted back into recovery and now TWRP fails every time at "restoring system" from my backup .
I believe I backed up my working ROM with TWRP 2.5.0.1, I flashed LS ROM with CWM to see if it would help with force closing. It didn't so I reflashed TWRP 2.5.0.1 as recovery and tried restoring it from there, and haven't had any luck.
Anyone have any pointers? Suggestions? Have you had a similar situation?
Click to expand...
Click to collapse
Not sure if the recovery version has anything to do with it but twrp 2.5.0.1 is old. Current version is 2.7.2.1.
BluGuy said:
Not sure if the recovery version has anything to do with it but twrp 2.5.0.1 is old. Current version is 2.7.2.1.
Click to expand...
Click to collapse
Only reason I'm on a deprecated version is because, in the past, I've made a backup and tried restoring it on a newer version of TWRP and it failed and failed for days, then I reverted to the version I did the backup on and it worked. The issue here could be that I don't know specifically that 2.5.0.1 was the TWRP i was using before... I could try an updated one though. Is it ok to just flash a newer version of TWRP through TWRP itself?
falkon114 said:
Only reason I'm on a deprecated version is because, in the past, I've made a backup and tried restoring it on a newer version of TWRP and it failed and failed for days, then I reverted to the version I did the backup on and it worked. The issue here could be that I don't know specifically that 2.5.0.1 was the TWRP i was using before... I could try an updated one though. Is it ok to just flash a newer version of TWRP through TWRP itself?
Click to expand...
Click to collapse
Yes, you can flash twrp with twrp. As about the rest, like I said I was just making a guess. It could just also be that the backup was bad. I have had that happen once or twice.
BluGuy said:
Yes, you can flash twrp with twrp. As about the rest, like I said I was just making a guess. It could just also be that the backup was bad. I have had that happen once or twice.
Click to expand...
Click to collapse
Flashing it with the newest TWRP fixed everything.. We're good.
Thank you!
falkon114 said:
Flashing it with the newest TWRP fixed everything.. We're good.
Thank you!
Click to expand...
Click to collapse
Glad to hear.
hi i wanted to flash a new rom for my parents and tried zombi-x i followed all the steps and now i can't mount any partitions with twrp 2.7.1.0. the same problem persists with cwm so i don't know what to do because i never had the problem before.
Try reflashing the recovery using adb commands again.. As I have had that problem with the twrp before on a upgrade.
fruity_senpai said:
hi i wanted to flash a new rom for my parents and tried zombi-x i followed all the steps and now i can't mount any partitions with twrp 2.7.1.0. the same problem persists with cwm so i don't know what to do because i never had the problem before.
Click to expand...
Click to collapse
Shoot me a email if you would like to explore your issue more ...
[email protected]
Thx Josh
I reflashed the original bootloader and started from scrap and now it's working like a charm. Damn i rarely use my parents tablet so i was shocked when I broke it xd
fruity_senpai said:
I reflashed the original bootloader and started from scrap and now it's working like a charm. Damn i rarely use my parents tablet so i was shocked when I broke it xd
Click to expand...
Click to collapse
Can you explain how to re flash the original boot loader? I'm in the same scenario where I can't install a rom because it's unable to mount system data.
i would also be interested in detailed information
Hello, i just installed an TWRP 3.0.0.0 Zip file and after that i rebooted the recovery and it keeps bootlooping, is there any ways to fix it? My current android version is MinimalOS 5.1.1.
Thanks.
Zelion said:
Hello, i just installed an TWRP 3.0.0.0 Zip file and after that i rebooted the recovery and it keeps bootlooping, is there any ways to fix it? My current android version is MinimalOS 5.1.1.
Thanks.
Click to expand...
Click to collapse
What else did you do, did you flash anything else or wiped anything?
TWRP won't work on a non-isorec compatible rom, but it shouldn't bootloop either, explain in details.
I am running LineageOS 15.0 and with TWRP Recovery 3.2.0.0, I did a full system backup with the new updated recovery a couple days ago and the backup finished without any error. It's weekend, I think I have a little time to play around, so today I tested to run a full system restore with my backup but the TWRP Recovery restore process just failed (keep on running without progress and didn't give any error message). Eventually, I have to fastboot and flash back old TWRP Recovery 3.1.1.0, with this old recovery, the restore process went by smoothly, so I concluded that there is nothing wrong with my previous backup but rather a problem of the new TWRP Recovery 3.2.0.0 or the new recovery conflicts with Oreo. So if you are running TWRP Recovery 3.2.0.0, i think you would better double check to confirm your full system backup is good to go.
Restoring backups from TWRP 3.1.0.0 fails with the new TWRP 3.2.0.0
I faced a similar issue today. After I updated my recovery to the latest TWRP 3.2.0.0, I tried to restore my stock rom
that was backed up using the previous version of TWRP 3.1.0.0. However, the restore was not successful. The screen
was stuck after the initial message of partition update and MTP enabled. Then, nothing happened. Even after waiting for close to 10 minutes, there was no progress. So, I guessed there was some issue. I powered off the phone and the used the short-cut keys to boot into the boot loader mode to boot my phone normally. I tried one more time and it failed.
Then, I had to flash to the old TWRP recovery 3.1.0.0 and tried the restore. It went of smoothly without any issues.
So, obviously there is an issue with the latest version of TWRP recovery 3.2.0.0 that fails to restore ROM backups created using the earlier version. I hope this issue goes to the notice of TWRP developers and they provide a fix soon.
P.S. I have also taken a nandroid backup of my phone with the new TWRP 3.2.0.0 which took unusually long time to complete, but finally it showed successful and I am yet to try using it for a restore. At this point, I am not sure if it will work alright. Fingers crossed.
Confirmed. Had the same problem. Unable to restore backup. Successful after rollback.
And what if you make a backup in 3.2.0.0 and restore it in 3.2.0.0 and in 3.1.1.0?
FPSUsername said:
And what if you make a backup in 3.2.0.0 and restore it in 3.2.0.0 and in 3.1.1.0?
Click to expand...
Click to collapse
With recovery 3.1.1.0, you can restore backup no matter it is backup with 3.1.10 or 3.2.0.0, with recovery 3.2.0.0, you just can't restore any backup.
I also faced the backup restore issue through 3.2.0.0. Back to 3.1.1.0.
As the issue is present for everyone, developers at TWRP should provide a quick fix patch or recall this version and release the next stable version with the fix. Also, make a mention of this issue at their download location and provide possible workarounds for the time being.
---------- Post added at 08:08 PM ---------- Previous post was at 08:00 PM ----------
As the issue is present for everyone, developers at TWRP should provide a quick fix patch or recall this version and release the next stable version with the fix. Also, make a mention of this issue at their download location and provide possible workarounds for the time being.
TWRP Recovery has been updated to 3.2.1.0 and the not able to restore problem should have been fixed.
acwcanada said:
TWRP Recovery has been updated to 3.2.1.0 and the not able to restore problem should have been fixed.
Click to expand...
Click to collapse
Just checking, has any one tested it with the new version of TWRP (3.2.1.0) to confirm if the restore / backup are working fine without any issues?
AndroMani said:
Just checking, has any one tested it with the new version of TWRP (3.2.1.0) to confirm if the restore / backup are working fine without any issues?
Click to expand...
Click to collapse
I can confirm that there are no problems with restore/backup in 3.2.1.0