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
Related
guyz TWRP or CWM which is better and why?
i was a huge twrp fan.....but when i tried to flash sense rom by Qube2 i got an error.I used CWM and flashed the same zip successfully.
also which is better with backups?
nexussgeek said:
guyz TWRP or CWM which is better and why?
i was a huge twrp fan.....but when i tried to flash sense rom by Qube2 i got an error.I used CWM and flashed the same zip successfully.
also which is better with backups?
Click to expand...
Click to collapse
the best for me is cwm.. the twrp is little more 'dificult'
I was on CWM until about last week, then I decided to take a look at TWRP again. I never tried CWM 6 so I can't compare TWRP to that, but navigating through TWRP is way quicker. The thing I hate about CWM (hopefully it isn't like this anymore in CWM 6) is confirming a wipe/install/format whatever. It takes ages and is really frustrating. I also disliked the menu layout. Why is wiping dalvik cache in advanced? Nobody knows... In TWRP, the things you need when installing a new ROM or Kernel is right there, when I flashed Air Kernel it even asked me whether I wanted to wipe cache & dalvik cache. Lastly, I prefer GooManager over Rom Manager. Automates the whole flashing process, if it automatically did a titanium backup restore after flashing a new ROM it would be perfect . So far I haven't experienced any bugs in either one, but they both seem to have some.
Hi,
This is my first post on XDA, so please forgive if i miss some of the things !! So i will start with the issue i am facing. I was running Prism Barebone v14.6 on my S4 i9500, i was trying to install the Xposed Framewrok for Lollipop but somehow i missed the part where it said that "Xposed it not yet working for Samsung TW roms and you will end up in bootloop if you flash it".
So as expected i ended up in bootloop, so i tried to restore my Nandroid backup from Philz recovery. Everything went just fine in the recovery but i was again stuck in bootloop and my phone was not proceeding from Samsung logo loading screen. So i flashed the PB rom again and restored my apps and data with Titanium Backup.
Since then i am having strange issue that for some reason i am not able to restore my Nand backups even after creating the fresh nandroid backups. I was creating the Nandroid backup using "Online nandroid backup" tool; so i thought maybe the issue could be with this app(though it worked just fine on my previous rom Omega v27).
So finally i thought of creating the Nandroid backup from PhilZ recovery and the weird thing was nandroid backup creation failed at "/system" saying "Error backing up /system".
So please guys help me understand what exactly went wrong and how can i fix this. I am facing this issue from last 2 days and i have tried everything which could think of, so i need help from you Android Gurus out here !!!
Thanks in advance !!
rbhanot2 said:
Hi,
This is my first post on XDA, so please forgive if i miss some of the things !! So i will start with the issue i am facing. I was running Prism Barebone v14.6 on my S4 i9500, i was trying to install the Xposed Framewrok for Lollipop but somehow i missed the part where it said that "Xposed it not yet working for Samsung TW roms and you will end up in bootloop if you flash it".
So as expected i ended up in bootloop, so i tried to restore my Nandroid backup from Philz recovery. Everything went just fine in the recovery but i was again stuck in bootloop and my phone was not proceeding from Samsung logo loading screen. So i flashed the PB rom again and restored my apps and data with Titanium Backup.
Since then i am having strange issue that for some reason i am not able to restore my Nand backups even after creating the fresh nandroid backups. I was creating the Nandroid backup using "Online nandroid backup" tool; so i thought maybe the issue could be with this app(though it worked just fine on my previous rom Omega v27).
So finally i thought of creating the Nandroid backup from PhilZ recovery and the weird thing was nandroid backup creation failed at "/system" saying "Error backing up /system".
So please guys help me understand what exactly went wrong and how can i fix this. I am facing this issue from last 2 days and i have tried everything which could think of, so i need help from you Android Gurus out here !!!
Thanks in advance !!
Click to expand...
Click to collapse
Have you tried TWRP ? PhilZ development has been stopped, so you should think about switching someday.
I would do it like this:
-Make a nadroid backup with your custom recovery
-Perform a full wipe
-Flash latest stock firmware via ODIN
-Let the system boot up
-Flash custom recovery and check if the error persists
tried TWRP as well however i was still getting the same issue(boot up process getting stuck at samsung logo screen). Will flashing the Stock Firmware reset the recovery also to Stock recovery ?
Can anyone please reply !!
rbhanot2 said:
Can anyone please reply !!
Click to expand...
Click to collapse
Yup, stock firmware will restore everything. Flash it as i linked it earlier. Once done, perform a factory reset in stock recovery before you boot up android.
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
Due to problems with Google Services on my rooted Galaxy S5 (SM-G900F) I opted for a reset from TWRP and it returned to a condition where after some initial screens it was just stuck at "Checking for Updates" so I went back into TWRP and told it to wipe the other partitions. Whoops - now I have no OS (I was sort of assuming that the factory reset OS was somewhere else)
Which is the stock ROM for my Region - UK, unbranded - where do I get it from and how do I load it using Odin and/or TWRP?
TIA
Hello,
Did you make a nandroid backup of your stock ROM or a nandroid backup of a custom ROM if you installed one? If you have a nandroid backup of either of those then you can restore them in TWRP by choosing the restore option and then your nandroid then swipe the slider at the bottom of the screen. If you installed a custom ROM at any time before this and you still have the ROM file then you can reflash the ROM and Gapps.
If you don't have a custom ROM stored anywhere but can still get to recovery, then you can download any of the custom ROMs compatible with your device and a Gapps package that matches it and put them on your extsdcard then boot to recovery and flash the ROM and gapps, do the normal wipes in recovery after flashing, the normal wipes(wipe data/factory reset, wipe cache and wipe dalvik cache), DO NOT CHOOSE THE ADVANCED OPTIONS THAT LET YOU WIPE PARTITIONS.
Check this thread to see if it is your stock firmware, it SHOULD be but double check first, it also has instructions for rooting again and installing recovery.
http://forum.xda-developers.com/galaxy-s5/development/stock-rom-root-recovery-sm-g900f-t2967725
If that doesn't work then go to Sammobile.com and search for your stock firmware by using your device model number.
The firmwares can sometimes be found at samsung-updates.com also.
Find the right firmware for your exact model number and flash through Odin.
For further assistance, post your question in the forum linked below.
http://forum.xda-developers.com/galaxy-s5/help
Good luck.
Droidriven said:
Did you make a nandroid backup of your stock ROM or a nandroid backup of a custom ROM if you installed one?
Click to expand...
Click to collapse
Sadly not - wasn't expecting to need it, thought it would revert to factory default - I have Titanium backup of apps and data.
I am hopefully a few minutes away from downloading the stock ROM and hopefully can reflash that using ODIN.
KD
colehill said:
Sadly not - wasn't expecting to need it, thought it would revert to factory default - I have Titanium backup of apps and data.
I am hopefully a few minutes away from downloading the stock ROM and hopefully can reflash that using ODIN.
KD
Click to expand...
Click to collapse
Making nandroid backups in recovery is the most important and valuable function of custom recovery, flashing ROMs is its' secondary purpose Android is not like PC with a recovery partition that restores a factory IMG, on PC that factory IMG is stored in a recovery partition. The factory reset feature in stock android does not restore an IMG, it deletes all data from the user partition and leaves everything in system partition the way it is, if you delete a system app and then do a factory reset then you will still not have the system app that you deleted. Anything you modify in system remains the way you modified it if you use the factory reset option. You should only use the factory reset in recovery, not the factory reset in system settings when you have a rooted device with custom recovery.
I'm sure that when you found the recovery, the directions had to have mentioned making a nandroid backup of your stock ROM before flashing anything, your present situation is why you do that, so that if anything goes wrong then you can easily restore to the one ROM that you know for sure works with no issues.
Sent from my SCH-I535 using Tapatalk
Droidriven said:
I'm sure that when you found the recovery, the directions had to have mentioned making a nandroid backup of your stock ROM before flashing anything, your present situation is why you do that, so that if anything goes wrong then you can easily restore to the one ROM that you know for sure works with no issues.
Click to expand...
Click to collapse
I installed the TWERP recovery as part of the rooting operation and I didn't pay any attention to the backup option - I thought that's what Titanium did.
I am learning and will make sure that I take a Nandroid backup once I have it back up and running. Life would be so much simpler if only Samsunng didn't stuff their 'phones with bloatware that can't be deleted in stock mode.
KD
colehill said:
I installed the TWERP recovery as part of the rooting operation and I didn't pay any attention to the backup option - I thought that's what Titanium did.
I am learning and will make sure that I take a Nandroid backup once I have it back up and running. Life would be so much simpler if only Samsunng didn't stuff their 'phones with bloatware that can't be deleted in stock mode.
KD
Click to expand...
Click to collapse
Titanium backup can only backup data that you installed or downloaded, it does not backup anything that comes on the phone itself, that is what custom recovery is for.
When following guides to mod your device, read and understand ALL instructions before you even make the first move to touch your device. Get used to being thorough about reading and understanding first or you'll end up in a mess, possibly even hard brick your device, all it takes is one wrong move. Not all mistakes are fixable with android devices.
Sent from my SCH-I535 using Tapatalk
I still have the original ROM. I have rooted it.
Before installing Malaysk's ROM i wish to backup the original
I know i can use Nandroid to backup. BUT should i choose TWRP or clockwordmod Backup?
And does the recovery of the unit support restore from this kind of backups?
Nomader0 said:
I still have the original ROM. I have rooted it.
Before installing Malaysk's ROM i wish to backup the original
I know i can use Nandroid to backup. BUT should i choose TWRP or Cyanogen Backup?
And does the recovery of the unit support restore from this kind of backups?
Click to expand...
Click to collapse
How would you install a custom recovery like TWRP? Is there a specific one to our devices?
That is exactly my question..
while with nandroid backup you can backupe yourn ROM in two formats (TWRP and clockwordmod), my question is how do you restrore from these backup files since we can not install TWRP or clockwordmod..
My qustion is whether the factory recovery can restore from these backups