E6683 (dual)
Stock Malaysia ROM (MM 305)
Rooted with rooted stock kernel
TWRP is 3.0.2.0
I've had this setup for months working nicely.
I did a full TWRP backup, tried N, didn't like it (for now) and so did a restore from the backup. Following a restore, it is stuck in Recovery! As in, when I reboot System, it just bounces back to Recovery.
I could try putting stock MM back on and then restoring, but before I do, are there any quicker tricks to getting the TWRP backup working again?
TIA
m
You should have switched back to MM before restoring your backup.
There are no other way around you have to switch back to THE SAME VERSION OF MM you were using during the backup.
Don't try this in the future you could brick your phone
Baradoura said:
You should have switched back to MM before restoring your backup.
There are no other way around you have to switch back to THE SAME VERSION OF MM you were using during the backup.
Don't try this in the future you could brick your phone
Click to expand...
Click to collapse
Interesting... thank you. I would estimate I've done a TWRP restore across all phones perhaps 500 times. At a guess, I'd estimate 80% between the same version, so maybe 100 between versions. On this particular phone, this may be the first time I've tried it - I forget, I do so many. So, I'm intrigued: why? Or to put it another way: do you know what it is that TWRP fails to back up successfully or indeed restore successfully that causes this problem in the first place?
EDIT: I restored the MM stock rom (re rooted) and restored the TWRP backup and it worked fine - i'm back on MM.
Related
ok so i had a backup that i used for twrp for rasbean jelly, which i used succesfully to restore my data many times before....so after i decided to try and restore my backup after i was done messing with miui...it restored as usual....but when i rebooted system it jumped me straight to bootloader...after flashing roms and then restoring and turning the phone on and of numerous times, it still shot me to bootloader so i thought i might have corrupted the backup somehow...so i get everything setup again and forget about the issue....i try backing my rom up again....and as i try to restore it it does its usual thing....once it finished restoring i reboot the phone and it shoots me right back to bootloader? what is going on or why is it doing this? never happened prior to these two incidents? and im using the latest twrp from goo.manager app....someone please help?
I have root, s-off, using TWRP recovery. I backed up everything on my external SD card with TWRP, ran (what I think is) RUU to get a clean install and was able to update to 4.4.3. After update, I put TWRP back on, and restored all my apps, still have s-off and root. A couple of things didn't restore (like Tasker), but I chalked that up to them probably being on the internal storage and then erased.
Everything else seemed to be working fine, but my WiFi will not turn on, and the default Sense camera opens to a completely black screen.
Any suggestions?
Thanks,
Ian
istrasci said:
I have root, s-off, using TWRP recovery. I backed up everything on my external SD card with TWRP, ran (what I think is) RUU to get a clean install and was able to update to 4.4.3. After update, I put TWRP back on, and restored all my apps, still have s-off and root. A couple of things didn't restore (like Tasker), but I chalked that up to them probably being on the internal storage and then erased.
Everything else seemed to be working fine, but my WiFi will not turn on, and the default Sense camera opens to a completely black screen.
Any suggestions?
Thanks,
Ian
Click to expand...
Click to collapse
To be correct, you are running a 4.4.3 ROM with 4.4.3 firmware right? Also when you try to enable wifi from the status bar does it simply endlessly show its trying to turn it on?
Perhaps a viable option would be to try a factory reset via TWRP, I sometimes encounter issues when doing that after a firmware update. Actually my 4.4.3 was so messed up because of restoring apps that I was forced to go back to my 4.4.2 ROM. Soo as I said, since you have a backup I'd just at least give factory reset a try and if it doesn't fix it then you can restore your backup again.
Try another kernel, I had the same issues
Enviado desde mi unknown mediante Tapatalk
bighleo114312 said:
Try another kernel, I had the same issues
Enviado desde mi unknown mediante Tapatalk
Click to expand...
Click to collapse
I'm kinda new to all this flashing/recovery stuff. How exactly do I use another kernel?
istrasci said:
I have root, s-off, using TWRP recovery. I backed up everything on my external SD card with TWRP, ran (what I think is) RUU to get a clean install and was able to update to 4.4.3. After update, I put TWRP back on, and restored all my apps, still have s-off and root. A couple of things didn't restore (like Tasker), but I chalked that up to them probably being on the internal storage and then erased.
Everything else seemed to be working fine, but my WiFi will not turn on, and the default Sense camera opens to a completely black screen.
Any suggestions?
Thanks,
Ian
Click to expand...
Click to collapse
How did you restore your apps?
jsaxon2 said:
How did you restore your apps?
Click to expand...
Click to collapse
Through TWRP. I put it back on after the update and restored the apps and data (not the system) from the backup I'd made previously.
You could try and flash the stock rom from http://forum.xda-developers.com/showthread.php?t=2874699 through twrp and see if it works for you. Don't wipe anything, just try flashing on top of what you have. Might work.
jsaxon2 said:
You could try and flash the stock rom from http://forum.xda-developers.com/showthread.php?t=2874699 through twrp and see if it works for you. Don't wipe anything, just try flashing on top of what you have. Might work.
Click to expand...
Click to collapse
Do I do that through TWRP or through the bootloader?. Sorry, again I'm still new at this.
istrasci said:
Do I do that through TWRP or through the bootloader?. Sorry, again I'm still new at this.
Click to expand...
Click to collapse
Your posts didn't really make clear what exactly you did: From which rom you took the TWRP nandroid, which rom you restored it back to, what you mean by "you think you ran a RUU", what exactly from the nandroid you restored in TWRP....
Did you restore all of /data? If you did, you restored way more than just your apps and may have compatability issues.
Restoring /data IMHO is not a good idea after doing a firmware upgrade and flashing a corresponding rom.
A better strategy would be to backup just your apps and their data in TiBu and only restore those after you flashed the new firmware and the new rom.
Here's what I would do:
Factory reset in TWRP
Reflash the rom
Reinstall your apps (this time from scratch, next time you'll have a TiBu backup).
Hi --
Nexus 5 on Sprint.
I'm running into a boot loop issue when trying to restore a Nandroid Backup built on a fresh N5 about an hour after a clean install.
Details are:
I just this week updated from Stock KK (4.4.4 I think) to Stock LP (5.0.1) -- I've been waiting because of needing/wanting XPosed framework....
After unrooting and returning to stock recovery on KK 4.4.4,
I did the LP OTA followed by a Full Erase after the OTA to start fresh. (Note: I have subsequently experienced the same exact problem after installing the LP using the flash-all.bat from the Nexus 5 image extracted to the SDK/platform-tools folder.)
After completing the login and google's restore process perfectly... All things LP appear to be working well and my phone is set up the way I want. So...
I then installed CWM recovery 6.0.4.5 using fastboot.
I then used the CWM recovery to root with SuperSU v2.40
I then used CWM recovery to make a Nandroid backup... (after completing a rooted power up and returning to the recovery)
Long story short (kind of), within the first several hours I messed something up (install of Nine email app AFTER the Nandroid didn't work and was leading to android.process.acore stopping issues. Nine has since told me that the app is not compatible with my company's MDM security solution Maas36). So , I wanted to return to the Nandroid point in time and just put my company exchange email into GMAIL - Acore issues continued after removing Nine.-- but were NOT happening at the time point where I created the backup. So I booted into CWM Recovery and selected to restore and picked the backup I had made of the fresh device.
Restore via CWM recovery proceeds fine and completes. However, it goes into the flying circles boot loop (I tried leaving it go for upwards of 2.5 hours at the longest time
I can easily recover from this with a flash-all.bat in fastboot
I have done this numerous times today and it is completely repeatable. Same thing happens each time.
I have definitely restored from Nandroid previously using this process on KK. But so far no Nandroid restore possible for me on LP. To be clear, the LP install works fine, but just can't be recovered from the Nandroid backup. I guess I'm OK with that, but I'd rather not fly without a backup safety net.
Hopefully that's enough detail for someone to comment. If I've missed any helpful details, let me know.
So, have I done anything wrong? The only thing I can think of at this second is possibly needing to unroot before attempting the restore? Is that it? I don't think I've done that before.
Thanks in advance for any help that anyone can provide.
greenawayj
One quick addition. I figured someone would suggest using TWRP instead of CWM, so I'm going through that process now. I'll update the post if I find different results. I'm also making my TWRP first backup pre-root just in case that matters...
Hello!
I am sorry if this is the incorrect place to post, but I have a very annoying issue with my OnePlus One!
A few days ago I took the OTA update from Android 4.4.4 all the way to 5.1.1. However, there are quite a few bugs with this version, and the "Material UI" is seriously getting on my nerves so I would like to revert back to my previous version. This should be doable because I performed a Nandroid backup with TWRP before updating the phone. My backup is saved on a USB stick which I connect to the phone via a USB OTG cable, which is perfectly mountable in the Recovery.
My phone is rooted and WAS running TWRP Recovery before I upgraded to Lollipop, this replaced TWRP with Cyanogens stock. When I re-rooted my phone I had to reinstall a custom recovery. For some reason, ADB installing TWRP was just not working (No errors, it just didnt install no matter what) so I opted to try a CWM recovery which did the trick.
Now my issue is that my recovery is unable to mount /sdcard which prevents it from performing backups or restores.
I could really use some help here.
Did you update your backup (TWRP?) as well? What version of it are you on?
JeffDC said:
Did you update your backup (TWRP?) as well? What version of it are you on?
Click to expand...
Click to collapse
I am not sure what you mean by updating the backup. The backup is backed up and left in the state it was when I took it, that is to say Android 4.4.4 and the version of TWRP (The date I installed TWRP the first time) is mid February 2015.
The phones recovery right now is PhilzRecovery which as far as I understand is CWM. Latest version.
Try installing twrp from the CWM recovery.. And before restoring the phone from nandroid try installing the clean stock rom at 4.4.4 and then do the nandroid restore.
Sent from OPO using Tapatalk
Press on thanks if I helped you
ashuthosh.heda said:
Try installing twrp from the CWM recovery.. And before restoring the phone from nandroid try installing the clean stock rom at 4.4.4 and then do the nandroid restore.
Sent from OPO using Tapatalk
Press on thanks if I helped you
Click to expand...
Click to collapse
And to do this, I would just drop the .img for TWRP into my phones storage and chose it from inside the recovery? Would this really work? It might be my inexperience, but it sounds somewhat risky.
NodCom said:
And to do this, I would just drop the .img for TWRP into my phones storage and chose it from inside the recovery? Would this really work? It might be my inexperience, but it sounds somewhat risky.
Click to expand...
Click to collapse
Don't know if CWM recovery supports installing img. Twrp supports img flashing. Check the features of CWM recovery and proceed.
Sent from my A0001 using Tapatalk
ashuthosh.heda said:
Don't know if CWM recovery supports installing img. Twrp supports img flashing. Check the features of CWM recovery and proceed.
Sent from my A0001 using Tapatalk
Click to expand...
Click to collapse
Well... I am not sure how I just managed this, but I was tinkering about inside my TWRP application and tried the "Install TWRP recovery" setting a second time (I tried it before making this thread, the first time it failed), it actually was successful because it booted into TWRP. From here I selected the TWRP-backup I kept and it installed it successfully (With one note, that it during the installation said something among the lines of "Restoring backup without deleting /data/media" or something like that. The phone rebooted itself after it finished updating, and the old Cyanogen/OPO bootanimation plays. But at login (My device is encrypted since long) it tells me my password is incorrect?!
How could this to happen? I've only ever used a single password (numbers only) for my phone encryption. This is very odd.
NodCom said:
Well... I am not sure how I just managed this, but I was tinkering about inside my TWRP application and tried the "Install TWRP recovery" setting a second time (I tried it before making this thread, the first time it failed), it actually was successful because it booted into TWRP. From here I selected the TWRP-backup I kept and it installed it successfully (With one note, that it during the installation said something among the lines of "Restoring backup without deleting /data/media" or something like that. The phone rebooted itself after it finished updating, and the old Cyanogen/OPO bootanimation plays. But at login (My device is encrypted since long) it tells me my password is incorrect?!
How could this to happen? I've only ever used a single password (numbers only) for my phone encryption. This is very odd.
Click to expand...
Click to collapse
I guess it's a side effect of restoring up a backup of 4.4.4 on lollipop. Try factory reset from twrp and then flash the backup. I would still suggest to first install the stock firmware of 4.4.4 and flash it and then do a restore of 4.4.4.
Sent from OPO using Tapatalk
Currently on Resurrection Remix
Thank me if I helped you.
Also make sure you are using the most recent version of TWRP, as it provides better 'outs' and reliability for newer OP OS versions.
I've been trying to weasel my way into a stable marshmallow rom, or even stock updated ota. So earlier today I did a backup with twrp before I tried to flash (clean wipe first of course) cm13. I tried to restore the backup, after it was successfully completed and the restoration process only took 47 seconds.. obviously something went wrong with it. So I took out the battery, rebooted it and tried to restore it again to find the backup was gone. Same directory though I also checked the external sd. I mean thats not even a big deal bc I have another backup, but does anyone know why a backup would just disappear?
Thanks and happy flashing!