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.
Related
[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!
Recently installed Hyperdrive Rom on my Verizon Note 3. SM-900V, NC4, running KK 4.4.2 prior to this installation.
Followed instructions re flashing back to NC2, Rom installed, everything is good,
BTW, as a part of the process installed SafeStrap, which provided a nice TWRP related recovery.
Did as suggested, a backup through recovery.
subsequently, made a couple of other changes, making a new backup through recovery each time. At present, there are three recoveries in backup.
Now comes the problem...........Decided to restore a prior backup, as instructed, did the full wipe using SS recovery, selected restore file desired, all went well and rebooted phone, only to have it hang once it reached the Bright Red Verizon screen.
Rebooted to recovery, followed the above procedure two other times on the remaining two backups. Same results.
Have wiped (Factory reset) each time in recovery with no apparent success.
Is this now being caused by the fact that I'm @ NC2, rather than NC4?
Would appreciate any suggestions as how I can get back to being able to restore and use any of the prior backups.
As a temporary measure, I went into recovery and reinstalled the Hyperdrive rom but would like to be able to go back in time if possible, and for no other reason to be able to understand just exactly what is causing this issue. Perhaps others have the same and have resolved in some way. A Google search shows that some are suggesting a return to factory settings, i.e. a full wipe through recovery, however I've done that with no success.
Another question, what happens if I also "wipe" the system files as well as dalvic, cache and data? Have hesitated to do that for fear of the unknown consequences
Bump
Kicking Deuce on the Beast, Note 3
sacgeek said:
Recently installed Hyperdrive Rom on my Verizon Note 3. SM-900V, NC4, running KK 4.4.2 prior to this installation.
Followed instructions re flashing back to NC2, Rom installed, everything is good,
BTW, as a part of the process installed SafeStrap, which provided a nice TWRP related recovery.
Did as suggested, a backup through recovery.
subsequently, made a couple of other changes, making a new backup through recovery each time. At present, there are three recoveries in backup.
Now comes the problem...........Decided to restore a prior backup, as instructed, did the full wipe using SS recovery, selected restore file desired, all went well and rebooted phone, only to have it hang once it reached the Bright Red Verizon screen.
Rebooted to recovery, followed the above procedure two other times on the remaining two backups. Same results.
Have wiped (Factory reset) each time in recovery with no apparent success.
Is this now being caused by the fact that I'm @ NC2, rather than NC4?
Would appreciate any suggestions as how I can get back to being able to restore and use any of the prior backups.
As a temporary measure, I went into recovery and reinstalled the Hyperdrive rom but would like to be able to go back in time if possible, and for no other reason to be able to understand just exactly what is causing this issue. Perhaps others have the same and have resolved in some way. A Google search shows that some are suggesting a return to factory settings, i.e. a full wipe through recovery, however I've done that with no success.
Another question, what happens if I also "wipe" the system files as well as dalvic, cache and data? Have hesitated to do that for fear of the unknown consequences
Click to expand...
Click to collapse
I am essentially having the same problem. I am currently running on Biggins ROM and that had me install a unified verision of the NC2 and NC4 kernels (I came from NC4 prior to flashing). I wanted to go back to stock root and flashed my backup from SS, everything went well so I restarted and just like you the phone just never went passed the Verizon logo screen. So I reinstalled the Biggins ROM and it works fine now but I also want to know what I have to do when I want to install other ROMS or simply go back to stock root.
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.
Update : sorry, I solved it. Not sure what happened but the 4th time trying completed the restore with no change in twrp. Go figure.
I searched for help on this but I'm not finding an answer.
I tried to restore my stock nandroid backup yesterday after being on RR nougat build (great build as well as cm14.1 but I had a few glitches that I want worked out before I make it my main rom). I had previously restored with NO problems at all but when I tried to restore I got through most of the process then was given an "error=255". I don't have a complete log so if that helps to solve this, I will try again and grab it. The only thing that is different other than the new rom is that I updated to twrp 3.0.2-5 from the 3.0.2-4 that I made the backup with. Should I revert back to that twrp then try to restore?
I have a Sprint Note 3 and I am having the dreaded "Unfortunately, the process android.process.media has stopped" problem.
I tried every single fix I found online. Even the stupid ones I knew wouldn't work. I finally caved and did a full wipe. Low and behold, on the very first setup screen the error message immediately popped up.
I am stock (whatever the latest version is) and rooted.
If factory reset doesn't work I don't know what else would work. That's usually the last recourse. Any suggestions? HELP!
Do I maybe need to re-flash the stock rom? If so, can someone please provide a link?
Suggest you ask in the SPRINT forum .
uscpsycho said:
I have a Sprint Note 3 and I am having the dreaded "Unfortunately, the process android.process.media has stopped" problem.
I tried every single fix I found online. Even the stupid ones I new wouldn't work. I finally caved and did a full wipe. Low and behold, on the very first setup screen the error message immediately popped up.
I am stock (whatever the latest version is) and rooted.
If factory reset doesn't work I don't know what else would work. That's usually the last recourse. Any suggestions? HELP!
Do I maybe need to re-flash the stock rom? If so, can someone please provide a link?
Click to expand...
Click to collapse
Yes, you need to re-flash stock ROM (search in updato). I'd also suggest you do a full DATA wipe with TWRP before and THEN flash stock ROM. Make sure you backup everything before anything.
ShaDisNX255 said:
Yes, you need to re-flash stock ROM (search in updato). I'd also suggest you do a full DATA wipe with TWRP before and THEN flash stock ROM. Make sure you backup everything before anything.
Click to expand...
Click to collapse
Holy crap. I downloaded a stock ROM from Updato and my phone isn't bricked but I'm worse off now.
Somehow, nothing at all changed on my phone after I flashed the ROM. All my apps, data, screens, everything is still there. However, I lost root and I lost my custom recovery and I still have the problem I had before.
Two questions:
1) I still have a Nandroid backup of my rooted phone from before I flashed the stock ROM. Can I restore this Nandroid backup with the stock recovery?
2) If not I will install TWRP again. At that point can I just restore the rooted Nandroid and gain root again or do I have to root first and then restore the Nandroid?
What a mess. Why did everything stay the same after flashing the stock ROM? Is updato a legit website?
uscpsycho said:
Holy crap. I downloaded a stock ROM from Updato and my phone isn't bricked but I'm worse off now.
Somehow, nothing at all changed on my phone after I flashed the ROM. All my apps, data, screens, everything is still there. However, I lost root and I lost my custom recovery and I still have the problem I had before.
Two questions:
1) I still have a Nandroid backup of my rooted phone from before I flashed the stock ROM. Can I restore this Nandroid backup with the stock recovery?
2) If not I will install TWRP again. At that point can I just restore the rooted Nandroid and gain root again or do I have to root first and then restore the Nandroid?
What a mess. Why did everything stay the same after flashing the stock ROM? Is updato a legit website?
Click to expand...
Click to collapse
It's a legit website but you need to wipe everything before flashing stock ROM. The order would have been: Boot into TWRP -> Wipe/Factory reset -> Format Data -> Reboot to download mode -> Flash stock
Yes, you will have to re-install TWRP again and restore your nandroid backup.