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.
Related
I always have used clockwork mod to flash roms and backup and restore my roms so I have a fair amount of backups and my stock rooted back up also is on clockwork mod. I wanted to see if i liked TWRP recovery so I flashed it and used it a little bit made one back up of king kang rom and then went back to clockwork mod. After I did that I tried to use clockwork again and all of my backups which I had made will not restore. Some of them have the message "md5 mismatch" others say "error restoring system" and other say "error restoring data". before this happened i had never had a single problem restoring any of my backups and I have at least 10 backups of mostly different roms which I have restored successfully before. I'm just trying to find out if there's a solution to my problem to get my backups to restore again. Appreciate any and all advice or suggestions.
I know if you rename the backups that will cause the md5 error. Maybe you should try deleting the twrp backup and any files or folders that go with twrp. Not sure if this will do the trick but its worth a shot. Hope you figure it out good luck.
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
Hi --
Nexus 5 on Sprint.
I'm running into a boot loop issue when trying to restore a Nandroid Backup built on a fresh N5 about an hour after a clean install.
Details are:
I just this week updated from Stock KK (4.4.4 I think) to Stock LP (5.0.1) -- I've been waiting because of needing/wanting XPosed framework....
After unrooting and returning to stock recovery on KK 4.4.4,
I did the LP OTA followed by a Full Erase after the OTA to start fresh. (Note: I have subsequently experienced the same exact problem after installing the LP using the flash-all.bat from the Nexus 5 image extracted to the SDK/platform-tools folder.)
After completing the login and google's restore process perfectly... All things LP appear to be working well and my phone is set up the way I want. So...
I then installed CWM recovery 6.0.4.5 using fastboot.
I then used the CWM recovery to root with SuperSU v2.40
I then used CWM recovery to make a Nandroid backup... (after completing a rooted power up and returning to the recovery)
Long story short (kind of), within the first several hours I messed something up (install of Nine email app AFTER the Nandroid didn't work and was leading to android.process.acore stopping issues. Nine has since told me that the app is not compatible with my company's MDM security solution Maas36). So , I wanted to return to the Nandroid point in time and just put my company exchange email into GMAIL - Acore issues continued after removing Nine.-- but were NOT happening at the time point where I created the backup. So I booted into CWM Recovery and selected to restore and picked the backup I had made of the fresh device.
Restore via CWM recovery proceeds fine and completes. However, it goes into the flying circles boot loop (I tried leaving it go for upwards of 2.5 hours at the longest time
I can easily recover from this with a flash-all.bat in fastboot
I have done this numerous times today and it is completely repeatable. Same thing happens each time.
I have definitely restored from Nandroid previously using this process on KK. But so far no Nandroid restore possible for me on LP. To be clear, the LP install works fine, but just can't be recovered from the Nandroid backup. I guess I'm OK with that, but I'd rather not fly without a backup safety net.
Hopefully that's enough detail for someone to comment. If I've missed any helpful details, let me know.
So, have I done anything wrong? The only thing I can think of at this second is possibly needing to unroot before attempting the restore? Is that it? I don't think I've done that before.
Thanks in advance for any help that anyone can provide.
greenawayj
One quick addition. I figured someone would suggest using TWRP instead of CWM, so I'm going through that process now. I'll update the post if I find different results. I'm also making my TWRP first backup pre-root just in case that matters...
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