Hey guys, I've been using CW Recovery Version 6.0.1.0 (Installed from Ez Recovery) for about the past week or so, and have started getting errors where CWM can't restore the data, cache, system, or boot from any of my four back ups. (One on stock rooted/unlocked, one on Pac Man, one on Galaxy Mod with stock JB kernal, and the other on Galaxy Mod with the lean kernal.)
After falling victim to the repeating "0" folder, and large file sizes for blobs, I decided I'd give TWRP a try. (Note, at this point, CWM was able to restore all of my backups.) So I flashed TWRP 2.2.0.0 from Ez Recovery, and then re-installed Galaxy Mod, but realized I forgot to back up my apps and data. So, I reflashed CWM and now after having flashed TWRP and reinstalling (I did do all the system/cache wipes and formats) Galaxy Mod, CWM cannot restore any part of any of my backups, and AppExtractor doesn't recognize them, even though they are right there on the SDext.
Anyone happen to have an idea of what's causing these /system/cache/data/boot errors??
If you flashed TWRP and then reinstalled Galaxy Mod but forgot to back up your data the smart thing to do is boot into recovery and back up your data using TWRP. Also you just freaking replace CWM with TWRP so of course it won't restore it as you no longer have that recovery.
I guess I wasn't as clear as I thought. ;o
All my app data, sms, etc. is on my latest CWM backup. And I do know that you can't recover CWM backups, with TWRP, so I did in fact reflash CWM and even though I left all of the backups untouched, not even CWM can restore any of them. So, I can't just backup my data on TWRP if all of it is on a CWM backup. ;o
Sent from my SCH-I535 using xda app-developers app
you can backup your CURRENT data on TWRP. I guess I wasn't clear as I said to backup your current setup. I don't recommend you using ez recovery to flash a custom recovery as it is outdated. All I can say is I didn't have that problem using the current version CWM recovery but did experience them using version 6.0.1.0.
Ahhh, gotcha.
Well, I'll try manually installing 6.0.1.0 (As I know CWM tends to be version specific) and also the latest version, just to see how things go. If it doesn't work, then well, I'll just rebuild everything from scratch. ;P
And thanks for the quick replies.
Sent from my SCH-I535 using xda app-developers app
Related
My recovery wont restore any backups I make. This may be an easy fix and I'm sure I'm asking a stupid question but I can't seem to get it to restore a back up. I get an error when it trys to. I'm on CWM-based Voodoo Lagfix Recovery v5.0.2.7.
what error do you get?
Sent from my SGH-T959V using xda premium
Let me guess... Cant mount system in the restore feature. I use titanium back and just use flashable roms if i need to restore... Dont know any other way around it. Maybe someone else does.
Sent from my SGH-T959V using XDA
5.0.2.7 shouldn't have the issue with being unable to mount /system.
What error or message do you get when you try to restore?
I'm getting the mount/system error. I thought flashing the new cwm recovery and kernel would have gotten rid of that problem. It never did. I still get the same error.
And your trying to restore back ups made with CWM 5. Not CWM 3 right.
if the backup was made with cwm 3.x it won't restore with cwm 5.x and vice versa.
Also, GB roms had issues restoring backups made with cwm 3.x - you had to flash a clean rom, and then do an advanced restore, and restore data only.
I just finished rooting my Verizon GS3 using the Easy root method ( http://www.youtube.com/watch?v=JVRjAiW7HdE&feature=plcp ) and everything went well, Installed Rom Manager, flashed Verizon GS3 CWM Recovery. Booted into Recovery, went to make a backup and it keeps giving me an error "Error while backing up boot image!" I've checked and it seems the the root took just fine, Superuser is working. I just can't make a backup in CWM. Please help
If you're using CWM Touch than that's the cause for not backing up. Use a non-touch CWM, preferably 6.0.1.0 so that you have the ability to use kexec and custom roms later to prevent potential issues later
Sent from my SCH-I535
You Da'man! Thanks so much
No problem, glad to help!
And meant to say custom kernels
Sent from my SCH-I535
What's a non-touch cwm?
Sent from my SCH-I535 using xda premium
when you go into Rom Manager and flash CWM it asked me if I want to purchase the "Touch". I did the first time I and was having an issue making a backup. When you are in CWM you usually have to use your volume up/down to toggle through it. If you add the "tough" you can use the screen and just tough what command you want to do. For some reason it didn't like it and wouldn't let me make a backup. So I flashed CWM again and it let me make the backup.
Helllo everyone, I have problem in restoring nandroid backups generated by CWM 5.0.2.0
When I restore backup, I get boot loops and cleaning up dalvik cache and cache wont help. First i thought it maybe a random error but it has happened even after lot of tries. I dont have a faulty sd card.
The backup i was trying to restore was of oxygen 2.3.2 with a theme installed + some apps
Can anyone suggest a a solution?
If you are getting bootloops then sorry to say the backup is not a healthy one, you need to reflash ROM. I also had problems with themes installed, now I made a backup keeping everything stock with apps.
Oxygen has inbuilt app2sd script. This causes problems many times. I would recommend restoring the system first, boot it up den restore both data and sdext.
sarus_b said:
Helllo everyone, I have problem in restoring nandroid backups generated by CWM 5.0.2.0
When I restore backup, I get boot loops and cleaning up dalvik cache and cache wont help. First i thought it maybe a random error but it has happened even after lot of tries. I dont have a faulty sd card.
The backup i was trying to restore was of oxygen 2.3.2 with a theme installed + some apps
Can anyone suggest a a solution?
Click to expand...
Click to collapse
Switch to twrp or amonra(if I'm not mistaken amonra can restore cwm backups).
Sent from my LG-P500 using xda premium
if Im not mistaken, we can flash a recovery within a recovery right?
sarus_b said:
if Im not mistaken, we can flash a recovery within a recovery right?
Click to expand...
Click to collapse
Yes, just download xxx.zip and flash, no problems, also they are very stable if you are wondering...
Sent from my LG-P500 using xda premium
You could have an error, like bad block, in your internal memory. To rule that out, install some other ROM fresh & see if you get errors.
-- Sent from my TouchPad using Communities
If the backup isn't restoring, then you should try restoring the backup, then reflashing the rom. I would recommend switching to amon ra recovery or twrp since they don't have that problem and imho they're better.
It seems the theme I installed had some problems since they replace system files such as framework-res.apk , settings.apk etc.
I flashed clean oxygen, installed lot of apps, created and restored the backup and it seems to work flawlessly now.
post-mortem said:
You could have an error, like bad block, in your internal memory. To rule that out, install some other ROM fresh & see if you get errors.
-- Sent from my TouchPad using Communities
Click to expand...
Click to collapse
Thats not the case, if it was i would have phone's PCB replaced by now.
bluespoon4 said:
If the backup isn't restoring, then you should try restoring the backup, then reflashing the rom. I would recommend switching to amon ra recovery or twrp since they don't have that problem and imho they're better.
Click to expand...
Click to collapse
This solution may also work i think.
I have Verizons S3. I recently rooted and unlocked the bootloader and have TWRP recovery. I was on 4.1 JB. I made a Nandroid Backup of System and Data. I then flashed the CM10.1 Monthly ROM, and all seemed to be working fine. However, I was having some issues with my app backups and the weird "emulated" directory structure. So I decided to go back to my Nandroid Backup and start over.
I went into TWRP, did a factory reset, cleared System Data, cache/dvalick cache, then I restored the Nandroid Backup (system and data). TWRP said it was successful and asked to reboot. When I did, the Samsung logo flashes, and then the screen stays black. I tried going back into recovery, but it won't let me. I can get to download though.
I think I'm going to have to use Odin to reflash a ROM as I can't get into recovery, right? But I'm also trying to understand what I did wrong. Did I forget a step? Did it have something to do with differences between 4.1 and 4.2? I'm new to this, and have searched the forums but can't find anything that answers my questions specifically. I appreciate the help.
anacree said:
I have Verizons S3. I recently rooted and unlocked the bootloader and have TWRP recovery. I was on 4.1 JB. I made a Nandroid Backup of System and Data. I then flashed the CM10.1 Monthly ROM, and all seemed to be working fine. However, I was having some issues with my app backups and the weird "emulated" directory structure. So I decided to go back to my Nandroid Backup and start over.
I went into TWRP, did a factory reset, cleared System Data, cache/dvalick cache, then I restored the Nandroid Backup (system and data). TWRP said it was successful and asked to reboot. When I did, the Samsung logo flashes, and then the screen stays black. I tried going back into recovery, but it won't let me. I can get to download though.
I think I'm going to have to use Odin to reflash a ROM as I can't get into recovery, right? But I'm also trying to understand what I did wrong. Did I forget a step? Did it have something to do with differences between 4.1 and 4.2? I'm new to this, and have searched the forums but can't find anything that answers my questions specifically. I appreciate the help.
Click to expand...
Click to collapse
You're supposed to backup "boot.img" as well. I'm pretty sure boot.img is the kernel which you failed to backup. The phone won't boot into your nandroid because the kernel wasn't restored as well. In TWRP: system, data, and boot are all supposed to be backed up simultaneously if you want to restore the entire nandroid. Odin flash and make sure to do a proper nandroid with all three that I listed.
Sent from my SCH-I535 using xda app-developers app
SlimSnoopOS said:
You're supposed to backup "boot.img" as well. I'm pretty sure boot.img is the kernel which you failed to backup. The phone won't boot into your nandroid because the kernel wasn't restored as well. In TWRP: system, data, and boot are all supposed to be backed up simultaneously if you want to restore the entire nandroid. Odin flash and make sure to do a proper nandroid with all three that I listed.
Click to expand...
Click to collapse
Ah, perhaps that "boot" checkbox wasn't check. =P So basically the CM10.1 boot.img is still there, but now the wrong ROM is there so it won't boot? Can I just flash the boot.img with Odin now, or will I need to do a full ROM flash?
anacree said:
Ah, perhaps that "boot" checkbox wasn't check. =P So basically the CM10.1 boot.img is still there, but now the wrong ROM is there so it won't boot? Can I just flash the boot.img with Odin now, or will I need to do a full ROM flash?
Click to expand...
Click to collapse
Flash nandroid and then try to flash a kernel. Might work Idk. Worth a shot.
sent telepathically
---------- Post added at 07:14 PM ---------- Previous post was at 07:13 PM ----------
jdub251 said:
Flash nandroid and then try to flash a kernel. Might work Idk. Worth a shot.
sent telepathically
Click to expand...
Click to collapse
Edit. Are you still not able to get into recovery? Sorry missed that in your post.
sent telepathically
jdub251 said:
Are you still not able to get into recovery? Sorry missed that in your post.
Click to expand...
Click to collapse
No, when I do the button combo for recovery, the word "Samsung" flashes, then "Galaxy S3" logo, but after that nothing...just blank screen. I was on stock Verizon s3 before this, so I guess I need to put that kernel back on the phone? Is the kernel the same as the bootloader? Can I use the unlocked bootloader referenced in this post: http://forum.xda-developers.com/showthread.php?t=1974114?
So, I tried using Odin to flash back the stock JB 4.1.1 kernel, which should have matched my Nandroid backup, but then I got an unlocked padlock on my splash screen and then the yellow triangle. blah. so i flashed a stock no wipe rom and that got me back into touchwiz, but I cant get into recovery no matter what i do. And I still have the padlock. I think I may need to do a stock full wipe rom?
anacree said:
So, I tried using Odin to flash back the stock JB 4.1.1 kernel, which should have matched my Nandroid backup, but then I got an unlocked padlock on my splash screen and then the yellow triangle. blah. so i flashed a stock no wipe rom and that got me back into touchwiz, but I cant get into recovery no matter what i do. And I still have the padlock. I think I may need to do a stock full wipe rom?
Click to expand...
Click to collapse
If you flashed a fully stock rom then you need to root, unlock, and install your custom recovery again.
Sent from my SCH-I535 using xda app-developers app
Ok, so I finally got time to try this again after flashing back to (what I thought) was stock Jelly Bean 4.1. I was following the directions here in this thread: http://forum.xda-developers.com/showthread.php?t=2046439
I get the VRALEC bootchain fine, phone reboots and all seems well. I got to flash TWRP 2.4, do a batter pull, and when I try to boot into recovery mode suddenly there is the Samsung splash screen with an unlocked padlock on it. Then the screen goes black and doesn't go into recovery. When I release the buttons, the phone then boots into the OS. I can still get to the download mode, but for some reason I can't get into a custom recovery. Any help on this? Please?
I used this file to wipe my phone back to stock JB: COMBINATION_I535VRBLK3_I535VZWBLK3_381038_REV09_user_low_ship.tar.md5
Thanks for the assistance. =)
Redo step three like the directions state.
Edit : In that thread, some folks even suggest waiting 5-10 mins after its successfully flashed before booting into recovery.
Sent from my SCH-I535 using xda app-developers app
Forgot to followup here, but I got it working. I left my phone plugged in after flashing the recovery for like 15 minutes. I also released the power button on trying to boot into recovery once the Samsung logo appeared. I finally got into recovery and was so happy. Thanks for the help!
Running mastamoon's unofficial CM 10.1. =)
anacree said:
Running mastamoon's unofficial CM 10.1. =)
Click to expand...
Click to collapse
Perfect! Glad you've got it all working properly!
Sent from my SCH-I535 using xda app-developers app
I used a mod ROM but I made a backup before doing that. The problem is that I use now CWM recovery (6.0.1.2) and I cannot restore the stock data. I get "Error while flashing boot image". I do not know what I am doing wrong
I go to restore from internal sdcard --> and I choose the restored backup
I have wiped all the data/cache & dalvik cash available. But still nothing. Does anyone know?
Did you use a different version of CWM recovery when you took the backup? If so it might have a different version of nandroid backup in it and be using a different backup format. If the CWM recovery is different, can't you put the original CWM recovery back on so the backup will restore with it?
Unfortunately I do not remember which recovery version it had but I am almost certain that it was the same version
Sent from my ZTE V970 using xda app-developers app
Cool-J said:
Unfortunately I do not remember which recovery version it had but I am almost certain that it was the same version
Sent from my ZTE V970 using xda app-developers app
Click to expand...
Click to collapse
An easy way to tell is to think about if you ever installed a new recovery. ROMs don't do that for you. ROM Manager has the ability to update your recovery image if you tell it to do so.
Your error is telling you that the recovery you have installed doesn't know how to handle the backed up boot.img. You could removed the boot.img from the backup and try restoring it again. Google it, if you don't know how to do that.
Does the MD5 check pass?
I just installed 4EXT Recovery, and it was able to restore my recent CWM recovery backups where CWM could not (>10,000 files bug). It appears that it doesn't support your device yet, but you never know.
Failing that, perhaps look at other alternatives. Maybe see if TWRP can restore CWM recovery backups, and if it supports your device.
Good luck.