Hi,
I've got a xoom eu, the tablet was flashed for long time with different rom (CM, EOS9), I was using TWRP.
Some days ago I've installed TWRP bigpart and latest Omnirom, everything was working fine.
Before the procedure I've made a nandroid backup of the CM 11 and TWRP that was running before the new installation.
After some days of playing I've decided that I prefer the old CM, after taking a second nandroid backup, containing Omnirom, I've tryed to restore the first backup....
A this point everything is screwed up, no recovery, no boot.
I've restored with RSD the original stock HC rom, this works well, after I reinstalled TWRP bigpart but if I try to restore one of the 2 nandroid backup the process failed.
It seems something got messed up in the partitioning scheme.
So what I can do to restore "original" partitioning scheme? At this point I can continue to use the partitioning modified by the bigpart procedure.
Thanks for the help.
diphe
Related
Hello,
Im using the TeamRogue's recovery (1.3.0) and I made a backup using this, before trying out a rom.
Now i wanted to go back to my backup, so i restored it, however it is stuck at the asus eee pad screen (boot screen).
I've seen more people with this problem and some say wiping the cache after the restore fixes it. Or when using the Super Wipe script, reboot after wipe and then restore.
Now after a lot of tries and wipes i finally got it booting fine.
However, me as stupid as I am, I tried another rom, so now I got the same problem, however only this time i can't get it to work.
Any help appreciated!
Kind regards,
ps. sorry for the grammar mistakes
What ROM were you on when you made a backup and what ROM did you try out?
If you went to an ICS base ROM and went back to a HC base ROM, you must get a HC kernel back, you can achieved this by flashing the HC ROM after your backup is done restoring.
I was on ICS and i flashed a ICS rom.
I also know about the kernel thing, ive flashed to my 3.2 backup to with no problem.
It just hangs on boot, has to be with \boot partition
Saw a few reports of this in the Team Rouge thread.
Same way to fix, nandroid restore and once it's done. immediate flash the ROM the backup is based upon. (No wipe if you want to save your data).
I had this happened to me going once going to an older ICS backup.
So.. to make this clear, i made a backup of the stock ICS.
So, i have to restore my backup and then flash a stock ICS rom or will EOS or some kind work to?
pretty much it is because eos is asop and stock is stock and some things that are different between the two are not restored when you restore a nandroid
Hi Folks, I hope this is posted in the right forum and sorry if I've missed seeing something similar already here.
I have a rooted Verizon GSIII on which I have been flashing custom ROMs and restoring nandroid backups without any problems for a while now (most recently I've been on Paranoid Android). Today I decided to try out Carbon ROM. I generated a nandroid backup using TWRP, then downloaded the ROM (the most recent nightly) and Gapps zip files using GooManager and flashed these after doing a factory reset. After rebooting the phone it seemed to start up OK... but it got as far as trying to find the network, which it unable to do. After selecting the skip option I then tried to sign in to my WiFi, but the keyboard didn't show up for me to type in the password. So I figured I'd cut my losses and just reboot into recovery and restore my PA backup. I was able to reboot into recovery and restore the backup but the PA backup pretty much did the same thing the carbon ROM did... just looped trying to find the network.
So... I'm not sure what went wrong or what to do next. Any suggestions???
I am able to boot the phone into recovery, but I'm afraid to start messing around too much without help as I'm no expert!
I do have the most recent nandroid backup and several earlier ones that did restore OK on my computer. Is there a way to flash any of these to the phone or to go back to stock?
Any help would be greatly appreciated.
Cheers.
Wipe catche dalvik factory reset then flash fresh batch of rom and gaaps if that works well getting tru start up then flash ur backup thats what i did.. If that dnt work then u gotta go tru odin back to stock
Hi guys,
after many atempts to find solutions and several hours without success I hope someone here can help me.
My configuration:
Phone: Nexus 4 16GB
ROM: Resurrection Remix LP v5.3.9
Kernel: 3.4.106-unleashed-101u+
Recovery: CWM 6.0.4.7 touch
This combination really works well. But when I boot into recovery, making a nandroid backup and afterwards restore it, I get a bootloop with the boot animation from the rom. The backup itself has around 2GB. Both, backup and restore processes are confirmed by cwm without errors.
I already tried to clean cache and dalvik cache before I made the backup, but restoring also doesn't work. A dirty flash of the ROM after cwm restoring (as a read in another thread) didn't work.
Is it possible that my cwm doesn't backup the preload partition (mentioned here)? Can the kernel or the ROM be the reason? Any other hints or a guesses?
You can update your CWM recovery or try other, like TWRP.
With TWRP you can change what partitions you want to backup
Sorry bad english
Upgrade of CWM is not possible, as 6.0.4.7 is already the latest version.
In the meanwhile I did some further tests: CWM 6.0.4.7 without touch is not working, too: The N4 gets stuck to the rom boot animation.
TWRP backs the same partitions up as CWM does, but works! I'm happy to be able to make and restore nandroid backups.
Still I'm wondering why nandroid backups using my former favorite recovery CWM don't work
Hey there guys, im having trouble restoring my Rom backups through twrp recovery since im on cm 12.1 i had done nandroid backups of my stock and cm12 Roms. The other day i tried going back to previous rom but when i go to twrp/ restore option...there is nothing even though i have the backup folders in my external sd. I tried moving the folders to internal storage also to check if it shows in twrp but nothing there....what do i do, help me cuz this is essential for changing Roms and stuff.
Well I think I got the reason behind it. When the system partition is wiped, the backup that is created before the system being wiped is not read. I tried it my self, I flashed cm 12.1 doing it fail proof method (wiping cache/dalvik/data and SYSTEM partitions)and before flashing the ROM I did a nandroid back up which when I went in the restore option in twrp was there before flashing the ROM . once I flashed the ROM, after everything gets booted and all I go to twrp, even though I have the backup folders I just doesn't show in twrp restore. That's what I've figured. Is this really the reason or there's something else being it.....?
Sent from my SM-N9005 using XDA Free mobile app
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!