I was playing around with some ROMs yesterday, since i was not happy with CM11 anymore. after installing a couple of different ROMs i decided to stick with slimkat. so i made a nandriod of slimkat and tried to go back to CM11 to get my apps all figured out for the switch. This is where the trouble started. when trying to restore CM11 I would get to "writing data" and at some point (always a different percentage) the phone would crash and reboot and get stuck in a boot loop. it would then do the same thing when trying to restore the slim ROM, always crashing before the restore finished. I always wiped data/sys/cache, i tried to fix permissions, install different version of twrp (2.6.x.x vs 2.8.6.0). I've since restored the phone back to factory and installed twrp again. I'm at my wits end as to what the problem could be. one thing that's odd is I get a splash screen before the twrp splash which still shows the little cyanogenmod guy at the bottom, even though there should be no remnants of CM on my s3 at this point.
I have slimkat installed at the moment and it's running fine. i'd still like to boot back into my old CM11. if i can't it's no tragic loss.
I will be travelling and i wont have access to odin for a little while, so i'm less inclined to go breaking things till i get back home. I thought maybe someone here has run into this or knows how to fix this.
Thanks for the help
Dom
wascalwabbit said:
I was playing around with some ROMs yesterday, since i was not happy with CM11 anymore. after installing a couple of different ROMs i decided to stick with slimkat. so i made a nandriod of slimkat and tried to go back to CM11 to get my apps all figured out for the switch. This is where the trouble started. when trying to restore CM11 I would get to "writing data" and at some point (always a different percentage) the phone would crash and reboot and get stuck in a boot loop. it would then do the same thing when trying to restore the slim ROM, always crashing before the restore finished. I always wiped data/sys/cache, i tried to fix permissions, install different version of twrp (2.6.x.x vs 2.8.6.0). I've since restored the phone back to factory and installed twrp again. I'm at my wits end as to what the problem could be. one thing that's odd is I get a splash screen before the twrp splash which still shows the little cyanogenmod guy at the bottom, even though there should be no remnants of CM on my s3 at this point.
I have slimkat installed at the moment and it's running fine. i'd still like to boot back into my old CM11. if i can't it's no tragic loss.
Click to expand...
Click to collapse
Was the original CM11 nandroid made with the same recovery make and version which would not install it? I am pretty sure TWRP will not install a CWM or Philz nandroid. I don't know if there are issues installing a 2.6.x.x TWRP nandroid with the 2.8.x.x version of TWRP.
Thanks for you're reply. The backup was made with twrp, I'm not sure which version it was, so I downgraded to see if it would help, then I installed the latest version again. There was no difference in the results no matter the twpr version. Twrp nandroids are in fact incompatible with CWM, not sure about philz
wascalwabbit said:
Thanks for you're reply. The backup was made with twrp, I'm not sure which version it was, so I downgraded to see if it would help, then I installed the latest version again. There was no difference in the results no matter the twpr version. Twrp nandroids are in fact incompatible with CWM, not sure about philz
Click to expand...
Click to collapse
Since Philz was originally based on CWM I wouldn't expect it to work with TWRP nandroids either.
Have you tried installing only specific partitions of the nandroid, such as the /data/data partition where the user installed apps are stored. As opposed to restoring the entire nandroid. I have heard mention of this, but in your case it may be problematic since your nandroid is of CM11 and the ROM you are running is SlimKat.
Oh that's a great idea, thanks, that may work. I i'll just flash CM and then restore data. I'm literally heading into the jungle right now, so in not sure if I'll be able to try this out for few days, but I will as soon as I get a chance.
Thanks for tour help
Related
So got my G2 today, rooted, installed Hboot, started up the phone, logged into all my accounts, got stuff how I wanted. Made a backup via Clockwork.
Then I tried out CM7 Nightlies, decided its pretty good but I wanted to go back to my backup. Loaded into Clockwork hit recover, picked my backup. The phone then just sits on the HTC screen. Never going to the G2 screen or getting back into the OS. I can't get a logcat from it either to see if it is crashing. I can get back into recovery, and flash another rom, but why isn't my backup of my original image working? There are no errors when restoring, I've tried a few times.
crater said:
So got my G2 today, rooted, installed Hboot, started up the phone, logged into all my accounts, got stuff how I wanted. Made a backup via Clockwork.
Then I tried out CM7 Nightlies, decided its pretty good but I wanted to go back to my backup. Loaded into Clockwork hit recover, picked my backup. The phone then just sits on the HTC screen. Never going to the G2 screen or getting back into the OS. I can't get a logcat from it either to see if it is crashing. I can get back into recovery, and flash another rom, but why isn't my backup of my original image working? There are no errors when restoring, I've tried a few times.
Click to expand...
Click to collapse
If you are using CM7, does this mean you upgraded to one of the CWM3 recoveries? Not sure if this has changed, but backups made with the older CWM2 recoveries are not compatible with CWM3. You will need to reflash back to the older recovery before restoring your backup (pretty sure there are lots of warnings about this in the CWM3/CM7 threads, so you should probably check those out to see if this is no longer the case).
I used CWM3 to make the backup, i assumed that would work to restore it.
EDIT: Okay. so CWM3 can't handle ANY Froyo, regardless of if the backup was made with it. Misunderstood that part. Flashed to CWM32 and it worked. Thanks.
I have a Samsung Galaxy Note 2(AT&T). I have it rooted w/CWM recovery. I recently flashed Jedi X12 rom to it following the directions to the tee. It installed perfectly and all was going well. I then tried run TiBu to put all apps with data back and system files. This cause several issues most of which were pop up boxes telling me various processes were failing. Tried to run the backup again and the problems persisted. So I restore to my CWM .zip image from before the whole process and it all is fine and where it should be. I then went back through the Jedi X install process and when it is all wiped, flashed, clear chached, it just hangs on the first black and white Samsung Galaxy Note 2 page. I let it sit for an hour hoping it would eventually boot, but no luck. So i restored to backup zip(CWM) again and the phone is fine. I repeated this process half a dozen times trying clearing different things, but nothing has gotten the rom to boot. It says all went fine in install.
*It worked the first time, got messed up by a TiBu, and hasnt worked since
*tried reflashing and restoring several time
*re-dl'ed the rom zip again and copied to phone incase file was corrupt
*In between every restore and rom flash I
-Wipe data ( factory data reset)
-Wipe system (Format system (in mounts/storage) if on CWM)
-Flash ROM
-Wipe cache/Dalvik
-Boot system and DO NOT TOUCH FOR 10 MIN
-After the 10 min, reboot phone
*All restoring/flashing was done through the CWM recovery.
I assume I have to clear/wipe/format/flash some other location to fix this. But Im going nuts trying to figure out where. Any help would be much appreciated. Thanks for your time.
Use Odin to get back to stock/unbrick. and NEVER restore system data using Titanium Backup
mrevankyle said:
Use Odin to get back to stock/unbrick. and NEVER restore system data using Titanium Backup
Click to expand...
Click to collapse
Thanks. I'm going to try app2zip the next time i get it to work. The phone works fine after i do a restore in clockwork mod, but I should still flash back to stock in odin again,, and start over? The recovery doesnt do that for me? Sorry if these are dumb questions, just getting into the android stuff, but have years exp. modding iphones.
if the phone is working fine, then no, you dont have to go back to stock; just NEVER EVER restore system files in TB, and you will be fine
Also, if you are going to be flashing alot of roms, you might want to switch to TWRP recovery, insted of CWM, as most folks have far fewer problems flashing when TWRP is their recovery..
wase4711 said:
if the phone is working fine, then no, you dont have to go back to stock; just NEVER EVER restore system files in TB, and you will be fine
Also, if you are going to be flashing alot of roms, you might want to switch to TWRP recovery, insted of CWM, as most folks have far fewer problems flashing when TWRP is their recovery..
Click to expand...
Click to collapse
Thanks all good info. Definitely learned the hard way about TB. Ill check TWPP out.
wase4711 said:
if the phone is working fine, then no, you dont have to go back to stock; just NEVER EVER restore system files in TB, and you will be fine
Also, if you are going to be flashing alot of roms, you might want to switch to TWRP recovery, insted of CWM, as most folks have far fewer problems flashing when TWRP is their recovery..
Click to expand...
Click to collapse
+1 on this...
I do a complete backup in TWRP...data and all saved to my external SD before doing any changes to my phone...and have not had 1 issue restoring it completely. FWIW...I make a complete back up every week regardless..then delete the previous one..and have everything available to me when it is restored all apps & data....TWRP makes it very easy to do this..and you can name & date your backups any way you choose to..I've found doing it any other way..causes more headaches than needed..and in less than 5 minutes I can be back up and running with all my apps & data with no problems in case I downloaded something that was causing an issue or changed something that caused issues. It's no different than using any desktop computer...you just need to get in the habit of doing it on a regular basis.
Mac
The other day I was restoring a backup in TWRP 2.6.0 on my Sprint Galaxy S3. The ROM I was on was AOSP based and the one I was restoring was AOSP based. During the restore, the phone rebooted during the data restore and then started a boot loop on the device, where it appeared I was starting TWRP again, only to have the device reboot at the TWRP splash screen.
I eventually finagled the device into getting TWRP to load by starting DL mode and then booting into recovery where I proceeded to do a full wipe and install a ROM from fresh. Anyone know why this would occur? It was very scary to think I was about to brick my device over something as simple as restoring what was a successful backup. I have not tried to restore any backups since out of fear of this issue occurring again. I also read on the TWRP page about a defect of reboot during restores if not enough data is available, but I have plenty of storage room available on my internal (26.26) and external (29.93) SD cards.
Not much help here, and at the risk of sounding like a Negative Nelly, I gave up on image-based backups several devices ago. The only device that I could get reliable nandroids was my HTC EVO 4G running AmonRA recovery. Since then, I've owned/rooted 4 or 5 other Android devices, and every single one of them have been completely unreliable with nandroid restores to the point that I just gave up, use Titanium Backup, and then just flash the ROM again. That's been with CWM and TWRP, all versions (and I've probably tried them all) on all of my devices.
I would love it if someone could enlighten the both of us on how to be successful with nandroid backups/restores. Again, sorry I'm not of much help, but consider me a confirmation of what you're encountering (a "yeah, what he said").
dante32278 said:
The other day I was restoring a backup in TWRP 2.6.0 on my Sprint Galaxy S3. The ROM I was on was AOSP based and the one I was restoring was AOSP based. During the restore, the phone rebooted during the data restore and then started a boot loop on the device, where it appeared I was starting TWRP again, only to have the device reboot at the TWRP splash screen.
I eventually finagled the device into getting TWRP to load by starting DL mode and then booting into recovery where I proceeded to do a full wipe and install a ROM from fresh. Anyone know why this would occur? It was very scary to think I was about to brick my device over something as simple as restoring what was a successful backup. I have not tried to restore any backups since out of fear of this issue occurring again. I also read on the TWRP page about a defect of reboot during restores if not enough data is available, but I have plenty of storage room available on my internal (26.26) and external (29.93) SD cards.
Click to expand...
Click to collapse
What I have found out the hard way is that every device is different. Some prefer CWM Recovery, some TWRP Recovery. If TWRP is not working for you, try CWM. A stable Custom Recovery is a must have.
TEAM MiK
MikROMs Since 3/13/11
So, I've been using TWRP since I purchased this device. I did a TWRP backup today as usual since I wanted to flash back to TouchWiz to update my PRL. I did so, then went to restore my backup. Only part of the backup restored. Now, no matter what I do in TWRP, I get the same error:
E error opening 'data/data/com.newegg.app/share (there's more text here but it's truncated by the recovery)
E error: Not a directory
This happens when I try to wipe (any option), flash a ROM, create a backup, restore a backup, etc. I've updated from TWRP 2.5 to 2.6.3, still to no avail. I don't believe it's a recovery issue. Recoveries don't just stop working, especially after using Odin to write a new recovery partition.
My ROM is screwed up. It boots, but no apps open. The hardware keys don't work (except home).
Any ideas or suggestions? I don't really want to switch to CWM but will if absolutely necessary.
Thanks!
I would suggest doing an ODIN back to Stock. Make sure everything is working correctly. Then Root the Device again.
I did something similar. I used a flash to stock and reset counter .zip that worked. It still threw that newegg error, but once I rebooted, reinstalled twrp, rooted, flashed Slim 4.3 Stable 2 and did another nandroid, the weird error is now gone. So glad I didn't ruin my phone! Thanks!
Your welcome. Happy you got the issue resolved .
TEAM MiK
MikROMs Since 3/13/11
[SOLVED]
Hello guys, hope that someone could help me.
I had a 4.4.2 rom (note4neo 2.0) and i wanted to try 5.1.1 so first of all i mad a full Nandroid Backup through TWRP and also a titanium bkp. Later on i installed lollipop original rom through ODIN and everything was ok. I then followed a guide from Noble Rom for rooting and installing TWRP. Everything went ok, but i had problems with some rooting app (like titanium) and so i decided to revert back to 4.4.2.
At first I rebooted into recovery, made a full wipe (even system) then restored previously backup. Seemed to be ok, but then when rebooted it stucks on boot logo (i left booting for 28 minutes, so....).
Then i tried to wipe cache, dalvik and data and reboot again: no changes.
I then decided to reflash previously twrp (the one that i used for bkp). Flashes went ok, but i have "recovery is not seandroid enforcing" message on the top (even with the lollipop twrp: maybe is this the key of my problem?!?).
Restoring backup from older twrp didn't work as well...
Of course i can enter both Download and Recovery mode.
Now i flashed back the original 5.1.1 through ODIN in order to go back to original lollipop and see what u guys can tell me to do to restore backup i made..
Thank you very much for your help
I was thinking that maybe i should flash a stock 4.4.2 before restore the backup...
Now i'm downloading it and see what happens...tell me if i may be right
Yes you should first restore a 4.4.2 firmware before flashing TWRP and then you'll be able to restore your backup
lennon123 said:
Yes you should first restore a 4.4.2 firmware before flashing TWRP and then you'll be able to restore your backup
Click to expand...
Click to collapse
Update: Flashed 4.4.2, all ok. Then rooted, twrp and all ok again
After i restored Backup and stuck on boot.
Then i made again all the steps: STOCK, ROOT, TWRP, then Base version of the Rom and all ok.
At this point i was thinking it was done and restoring would have been just fine...unfortunatley it doesn't. Stuck on boot again.
So i reflashed the Base version of the mod rom and: it started with my restored app Btw i'm encountering problems like no home button, no volume icon, no settings shortcut. Now i made a cache and dalvik wipe but problems still remain..
Any idea?
After some attempts to solve those problems i stucked again on boot..
So now my plan is to: Flash STOCK rom, Root, Twrp, Base mod rom (everything always ok so far) and then restore JUST DATA from backup... Not touching system and boot should let the rom works just fine...at least i hope so :'D
Ok, as i was expecting the problem is solved. I did not restored System and Boot and all apps works just fine. Even though i miss some settings i made now i'm happy to be 90% back to origin ^^
Well alright, your solution will probably help other people in your situation. I presume your porblem is solved, if so you can add [SOLVED] in your first post in the title.
lennon123 said:
Well alright, your solution will probably help other people in your situation. I presume your porblem is solved, if so you can add [SOLVED] in your first post in the title.
Click to expand...
Click to collapse
Yes, it's solved I'll mod the title