[SOLVED] Hello,
This is the first time for me posting in a forum asking for help about an android device so go easy. I have rooted my Nexus 4 running Android 4.3 and installed TWRP 2.6.0.0 on it. That was the first time I rooted an android. I used Titanium Backup (Pro) to backup all of my user apps + system data. Then I transferred the backup to my PC. Then I created a nandroid backup using TWRP. Then I cleared the cache, dalvik cache, and factory reset the phone using TWRP. Then I installed Cyanogenmod 10.1.2 mako, which is marked as stable, along with the Gapps found on Goo.im. It worked successfully and I set up my brand new ROM. Then when I restore using TiBU, it restores successfully until it gets to about 70% where it begins telling me that "There was a problem parsing the package" or "x App not Installed". TiBu then instructed me to reboot in order for system data to take effect after the restore, and I follow that order. Finally, my phone gets stuck in the boot animation of Cyanogenmod. I've gone in to recovery and did the entire process of flashing the CM ROM again and the same thing happened to me again. So I just restored my nandroid backup and now am on the stock ROM again. I've tried to look online but could not find any solution or reason. Remember that this was my first rooted Android device and I am not a pro at this stuff. I'm not asking for how to get out of the boot animation (I already know that), just why this problem is occuring and some possible solutions. Thank you.
I think the reason might be that you are not supposed to restore apps when changing from one ROM to another. I read that somewhere online. Is that true and do you think that that could possibly be the case? I went from stock ROM to CM.
[SOLVED] i have found the solution. it was that i tried to restore system data which caused the problem. everything is great now!
Related
What it says on the tin. I backed up using ROM Manager to launch the backup. I was upgrading to the CM11m6 from CM10.2 but that led to a failed boot followed by boot into recovery so I decided to restore. Restoring has left just CM`s built-in apps, a few gapps and one paid app. I thought nandroid backups were like imaging a computer and you got everything back? I stupidly didn't make backups with TitaniumBackup thinking it was unnecessary.
So, any ways for me to get all my apps back?
Update for googlers: I used Nandroid Manager to restore the missing apps from the backup. Hope that helps someone else with this situation!
I discovered a new issue while I continued to use CM 10.2.1--some apps updated and then it went into a bootloop again. Luckily I had am so I restored it and restored the missing apps again. I suspect it's either Gmail, Google Text-to-Speech, Google+ or Android Terminal Emulator. Google didn't reveal anybody else having this problem yet with the latest updates, so I must have some very unique issue.
As for updating to CM11, I'm gonna try creating another image (which'll hopefully restore all apps!) after it gets stable and trying updating to CM M5 instead of M6 which seems to have caused a bootloop for at least one person, too. I can't post outside links yet, so that person's report can be found by googling this phrase including quotation marks: "Update From 10.2.1 Stable To 11 M6 Causes Boot Loop".
Another update for googlers: The problem of apps-not-restoring seems to have been caused by version 2.6.0.0 of TWRP. I tried updating to 2.6.3.1 using both GooManager and TWRP Manager but it didn't stick. Used Nexus Root Toolkit to upgrade TWRP to 2.7.0.0, though. Restoring the image with that restored all the apps as far as I can figure out. Yay! Now I don't have to wait 3-4 hours for the app restore process to finish on top of the nandroid restore.
Hello,
I'm running TWRP v2.8.4.0 on a G900T. Before testing out my first custom rom after rooting the device I made a full backup through TWRP. I was having some difficulties with the ROM I chose and decided to restore my backup so I could use my phone still while figuring things out. Unfortunately, after restoring the backup file through TWRP and rebooting I am receiving crash report after crash report of a long list of apps.
I tried searching the forums but no such luck with the wording that I've used for a fix.
I've tried disabling MTP and Fixing Permissions (without the "SELinux contexts" option) after doing another factory reset (Wiping Data, Cache, and Dalvik.
If there is anything else that I could try or read up on that would be great. Thank you!
**Update**
The only thing I can think of is something to do with downgrading from Lollipop 5.0 to Stock 4.4.2. I'll update this thread if I end up getting something to work.
I ended up flashing the Alliance Rom to get it back to something very close to stock. Still interested in possible solutions to restoring that original backup though as if I need to send it in for maintenance that's the one that I'll need to use.
Guys,
I have an S5 running Cyanogen Lollipop and Philz Touch 6.26.2 as the recovery. I was experimenting with flashing a new camera .ZIP earlier today but BEFORE doing so I used Philz to create a backup. The flash of the .zip for the camera went wrong and ended up prompting the phone to hang on boot.
I booted into Recovery and restored my backup...restarted the phone and it then booted as normal BUT as soon as Android had booted, it was unusable as I just kept getting the "##### has stopped" error messages, one after the next - the launcher doesn't appear and the phone is completely unusable.
I have tried a 'Factory Reset' and wiping the Dalvik cache, on boot it optimises all apps but then does precisely the same.
Please help as I'm travelling tomorrow and need to sort this tonight!!
Cheers
sergeantash said:
Guys,
I have an S5 running Cyanogen Lollipop and Philz Touch 6.26.2 as the recovery. I was experimenting with flashing a new camera .ZIP earlier today but BEFORE doing so I used Philz to create a backup. The flash of the .zip for the camera went wrong and ended up prompting the phone to hang on boot.
I booted into Recovery and restored my backup...restarted the phone and it then booted as normal BUT as soon as Android had booted, it was unusable as I just kept getting the "##### has stopped" error messages, one after the next - the launcher doesn't appear and the phone is completely unusable.
I have tried a 'Factory Reset' and wiping the Dalvik cache, on boot it optimises all apps but then does precisely the same.
Please help as I'm travelling tomorrow and need to sort this tonight!!
Cheers
Click to expand...
Click to collapse
Backup restore also system apps and sometimes there are problems. I think you must flash the rom without backup.
davyleggend said:
Backup restore also system apps and sometimes there are problems. I think you must flash the rom without backup.
Click to expand...
Click to collapse
Ok, this has given me an idea - I have flashed fresh Cyanogen and now I'm attempting to restore just the 'data' and 'cache' elements of my backup by using the Philz 'Custom Restore' feature...fingers crossed!
So, my idea worked...my phone is now back up and running, what a relief!
Hey,
I've had this problem for ages now, and always gave up on my data, but now I really want to fix this for good.
Yesterday I was ready to update my CM12 nightly to the lastest version (didn't see it was actually CM13), and did a backup in cwm before the update. The backup succeeded, but it gave the message that .android_secure couldn't be found and it didn't back that up. It always gives me this message after a backup and after google searching, it seems to me that it doesn't matter.
After installing the update, I noticed it was CM13, and my gapps wasn't updated to the marshmellow stock, as expected, so errors occured all the time.
I didn't want to upgrade to CM13 just yet, so I decided to restore my backup.
As always, the restore process goes without errors, but upon reboot I'm stuck at the CM logo. I can wait untill the battery is dead or ignites from the heat, but nothing happens. This has also happened to me every time I make a backup. I've watched about every video on youtube on how to do a proper backup and how to restore one, so I'm confident that I did it right.
For some reason, any backup I make, no matter what android version (didn't work with stock kitkat, either, before I switched to CM12) it never works and I'm forced to do a clean install and start over again.
I've tried to do partial restores from the backup file, and if I only restore the data partition (and wipe dalvik) It does boot, but gives me non stop errors that apps are crashing.
I've tried to do a dirty flash to no avail, always endless error messages.
When I do a clean install and check the MK5 of the backup with nandroid manager it gives no errors.
Is there anything wrong with my phone or something? I'm not making backups to be unable to restore them.
Can anyone help me out with this?
(I have a i9505)
Try a different recovery. CWM is outdated. TWRP is nice. Worked for ne every time. There are TWRP flashable zips so you won't have to mess around with Odin.
GDReaper said:
Try a different recovery. CWM is outdated. TWRP is nice. Worked for ne every time. There are TWRP flashable zips so you won't have to mess around with Odin.
Click to expand...
Click to collapse
Won't changing recovery make my old backups useless? I'm all for changing to TWRP, but first I'd love to restore my CWM backup...
Yes it will. Unfortunately I don't know what to suggest. Haven't used CWM since I switched to the S4.
I just got a s5. And I got it succesfully rooted and also got TWRP working on it.
All the data from my previous phone was transfered to the s5.
Now I made some backups with TWRP with the default settings: Partitions boot, system and data.
With the backups in mind I was thinking I could easily restore it to a previous state.
Thinking I backed up all the data and wanted to make it fresh again, I wanted to restore it.
In the menu I chose the restore option with the same settings as the backup: Partitions boot, system and data.
And it gives a message restoring system succesfull.
But when rebooting, it keeps hanging and at the moment of loading the android system every bit of the system keeps 'hanging'
It keeps saying
'Unfortunately touchwiz startup unsuccesfully'
'Unfortunately youtube startup unsuccesfully'
'Unfortunately greenify startup unsuccesfully'
'Unfortunately app whatever startup unsuccesfully'
And so on and so on
Eventually it starts with a black screen with nothing loaded. Complete blackout.
So this backup doesn't work. And I try my second backup.
Unfortunately also the second backup gave these errors.
And also the third backup!
So the backup files seem the right size, it's some gigabytes, and it alway's keeps saying backup/restore succesfully.
But now it fails to restore and boot the backup
The things I tried.
-Trying three different backups
-Wiping cleaning data/dalvik/cache etc etc
-Restoring a part of the backup. First system, then data, then boot, no succes.
So i'm totally lost! Does somebody know how to fix this? Or have some tips to try??
You can't restore system and boot from a different model phone
That would be like trying to flash a ROM for one model phone to another without porting it
If it was an S5 you backed up, was it the exact same model (ie: G900F etc?)
Flash back to stock, then try restoring only DATA
Or use TiBu to restore your apps from the TWRP backup
*Detection* said:
You can't restore system and boot from a different model phone
That would be like trying to flash a ROM for one model phone to another without porting it
If it was an S5 you backed up, was it the exact same model (ie: G900F etc?)
Flash back to stock, then try restoring only DATA
Or use TiBu to restore your apps from the TWRP backup
Click to expand...
Click to collapse
Thanks for the reply! It was a backup and restore on the same phone. So that is why I thought it was supposed to be a easy restore.
But I found the solution hidden somewhere in one message on XDA:
"Originally Posted by Dr. Fed
Would you happen to know why, when restoring a TW 4.4.2 nandroid using TWRP 2.8.1 or 2.8.4, after running an AOSP lollipop ROM like CM12, the TW ROM boots but then the whole system force-closes? Before restoring the nandroid, I advance wipe system, data, cache, and dalvik. Then I restore the nandroid. It boots, but then some daemon crashes. Then all processes and apps. The screen goes black after a few crashes.
So, what I do is pull out the battery, boot into recovery, advance wipe system, data, cache, dalvik, flash a CM11 ROM, reboot. I let CM11 start up, skip the set-up, then I boot back to TWRP (2.8.1 and now 2.8.4), advanced wipe, restore TW nandroid, and now it works just fine.
It seems like TWRP doesn't fully wipe."
Here the steps for if other people will run into the same problem:
Problem: Android 5 is running, with twrp 2.7 performed a back up = Restoring the backup is difficult because it problably doesn't do a clean wipe somehow.
1. I downloaded a cyanogen 11 rom, a Android 4 version.
2. Installed it with TWRP. Somehow it 'wipes' it more efficiently.
3. From cyanogen 11 back to booting TWRP.
4. In TWRP trying the Android 5 restore.
And Amazingly this worked!! = Celebrate!!
chokolademan said:
Thanks for the reply! It was a backup and restore on the same phone.
Click to expand...
Click to collapse
Confused me with this line
chokolademan said:
All the data from my previous phone was transfered to the s5.
Click to expand...
Click to collapse
Good to see you solved it