Sorry its long but i want all the info out there might help with a answer. Last night I went step by step install cm10 nightly. Did the cwm update through rom manager as instruction said to cwm 6.0.2.3 (non touch) did a nandroid of my stock rooted setup. Then did all the wipes and clears all of them. Installed cm 10 let it boot then installed gapps let it boot and settle. I liked it but seamed like something was not right speed wise. Quadrent showed it had dropped to around 3500 where I was getting around 5600 on stock rooted. Went to nandroid back and it could not find back up. Nothing at all showed on internal card through cwm. But when hooked to pc everything was there. So I copied the backup to pc and to ext. Sd card. Cwm found the backup on ext.but said missing something so didnt work. So I nandroid the cm10 I was running checked restore and it worked to nandroid cm10. So I hooked to computer went to backup file and replaced the files with files from my stock rooted I had saved to pc. Cwm restored it perfect back to stock rooted after doing that. Now before I check out other roms could something be wrong with my cwm causing the nandroid problem and also why such low scores on cm 10?
Sent from my SAMSUNG-SGH-I747 using xda premium
kleigh774 said:
Sorry its long but i want all the info out there might help with a answer. Last night I went step by step install cm10 nightly. Did the cwm update through rom manager as instruction said to cwm 6.0.2.3 (non touch) did a nandroid of my stock rooted setup. Then did all the wipes and clears all of them. Installed cm 10 let it boot then installed gapps let it boot and settle. I liked it but seamed like something was not right speed wise. Quadrent showed it had dropped to around 3500 where I was getting around 5600 on stock rooted. Went to nandroid back and it could not find back up. Nothing at all showed on internal card through cwm. But when hooked to pc everything was there. So I copied the backup to pc and to ext. Sd card. Cwm found the backup on ext.but said missing something so didnt work. So I nandroid the cm10 I was running checked restore and it worked to nandroid cm10. So I hooked to computer went to backup file and replaced the files with files from my stock rooted I had saved to pc. Cwm restored it perfect back to stock rooted after doing that. Now before I check out other roms could something be wrong with my cwm causing the nandroid problem and also why such low scores on cm 10?
Sent from my SAMSUNG-SGH-I747 using xda premium
Click to expand...
Click to collapse
Quadrant score means absolutely nothing, don't base yourself on them.
You can change your kernel settings (governor, scheduler) to get a better performance if the current one don't work well with your phone.
I'm not sure why your nandroid wasn't working but I expect it's cause it was made without the cwm recovery.
kleigh774 said:
Sorry its long but i want all the info out there might help with a answer. Last night I went step by step install cm10 nightly. Did the cwm update through rom manager as instruction said to cwm 6.0.2.3 (non touch) did a nandroid of my stock rooted setup. Then did all the wipes and clears all of them. Installed cm 10 let it boot then installed gapps let it boot and settle. I liked it but seamed like something was not right speed wise. Quadrent showed it had dropped to around 3500 where I was getting around 5600 on stock rooted. Went to nandroid back and it could not find back up. Nothing at all showed on internal card through cwm. But when hooked to pc everything was there. So I copied the backup to pc and to ext. Sd card. Cwm found the backup on ext.but said missing something so didnt work. So I nandroid the cm10 I was running checked restore and it worked to nandroid cm10. So I hooked to computer went to backup file and replaced the files with files from my stock rooted I had saved to pc. Cwm restored it perfect back to stock rooted after doing that. Now before I check out other roms could something be wrong with my cwm causing the nandroid problem and also why such low scores on cm 10?
Sent from my SAMSUNG-SGH-I747 using xda premium
Click to expand...
Click to collapse
as has been said, quadrant is a joke. if you have an sd card, next time you make a backup in recovery, select "backup to external sd". that will save your nandroid to a location that will remain untouched during your wipes.
Re: Cwm troubles and cm10 question
BWolf56 said:
Quadrant score means absolutely nothing, don't base yourself on them.
You can change your kernel settings (governor, scheduler) to get a better performance if the current one don't work well with your phone.
I'm not sure why your nandroid wasn't working but I expect it's cause it was made without the cwm recovery.
Click to expand...
Click to collapse
My nandroid was made with cwm the same one I used to flash cm10.
Sent from my SAMSUNG-SGH-I747 using xda premium
Use TWRP ? I prefer how it stores nandroids....although I had the same issue as you with TWRP where it was there when I explored with PC but TWRP could find it. I had to move folder around in windows and put them back into the correct folders. Then created a nandroid on ext card and only moved it when I needed to flash it.
Re: Cwm troubles and cm10 question
hednik said:
Use TWRP ? I prefer how it stores nandroids....although I had the same issue as you with TWRP where it was there when I explored with PC but TWRP could find it. I had to move folder around in windows and put them back into the correct folders. Then created a nandroid on ext card and only moved it when I needed to flash it.
Click to expand...
Click to collapse
Speaking of twrp when I go to rom manager and click recovery where you update cwm under installed recoverys it list I have cwm and twrp installed how is that?
Sent from my SAMSUNG-SGH-I747 using xda premium
Re: Cwm troubles and cm10 question
Sent from my SAMSUNG-SGH-I747 using xda premium
kleigh774 said:
Speaking of twrp when I go to rom manager and click recovery where you update cwm under installed recoverys it list I have cwm and twrp installed how is that?
Sent from my SAMSUNG-SGH-I747 using xda premium
Click to expand...
Click to collapse
You can only have one recovery installed as it saves it as recovery.img. If you install a new one the old one is written over. This has always been my experience. You can install the new recovery in Goo Manager like you do with CWM in Rom Manager.
Related
Hi, I searched and I'm sure it's already been answered but I can't seem to find my exact answer. Here's the question:
I have a rooted galaxy s3 that has a cracked screen, I got a replacement galaxy s3 that I am going to root soon...
What I need to do is make an exact copy of my rom on my cracked phone and then install it on the new phone. I want to keep all my settings, contacts, wallpaper, programs etc... exactly the same.
What is the easiest way to do this?
My recovery is CWM 5.5.. Thanks in advance.
Make a nandroid backup of the broken phone. Copy it to a pc. As long as the new device is the same you can just copy the backup to the new phone and flash using the same recovery you used on the broken phone
evoer said:
Make a nandroid backup of the broken phone. Copy it to a pc. As long as the new device is the same you can just copy the backup to the new phone and flash using the same recovery you used on the broken phone
Click to expand...
Click to collapse
Thank you so much for the fast reply, I went to rom manager and it had me update to ClockworkMod Recovery v6.0.1.2 I am looking for how to make a nandroid but all I see is "backup" after performing backup, I can't seem to find the new rom. no files seem big enough to have the entire rom in them. Where would I find said backup?
ericmcintire said:
Thank you so much for the fast reply, I went to rom manager and it had me update to ClockworkMod Recovery v6.0.1.2 I am looking for how to make a nandroid but all I see is "backup" after performing backup, I can't seem to find the new rom. no files seem big enough to have the entire rom in them. Where would I find said backup?
Click to expand...
Click to collapse
Scroll to the bottom of ROM Manager and choose to install an earlier version of CWM. Choose 5.5 (or whatever version you used on the current phone) flash that and it should recognize the backup you created on the first phone.
Neil Fruit said:
Scroll to the bottom of ROM Manager and choose to install an earlier version of CWM. Choose 5.5 (or whatever version you used on the current phone) flash that and it should recognize the backup you created on the first phone.
Click to expand...
Click to collapse
I meant I updated on the old cracked phone... is "backup to SD card" going to work? So, boot to the new CMW, "backup to sd", put SD card in new phone, boot to CMW, and restore from backup and I'll have exact carbon copy of old phone? Thanks again.
yeah, put the earlier version of CWM on the cracked phone and do a nandroid to the SD card. Install the same version of CWM on the new phone, put in the SD card with the nandroid from the cracked phone into the new phone, boot into recovery with the older version of CWM installed and restore the nandroid from the cracked phone. You should then be good to go.
Team Win Recovery for the win!
Sent from my SPH-L710 using xda app-developers app
I flashed PARANOIDANDROID 2.99 BETA3 from stock DLK4, 4.1.1. It worked but I was ready to revert back to the stock using the nandroid I made before flashing and realized that I did a factory reset when flashing pdroid and lost my nandroid backups. Fortunately I have older Nandroids from 12.12 on my pc. I placed it into the clockworkmod directory, sdcard\clockworkmod\backups, as I normally would but when I reboot into recovery I don't see the nandroid that I placed there. What do I do from here? I tried to do a factory reset from kies of DLK4 but afterwards I get stuck on the "Samsung" loading screen.
Any help would be appreciated. I spent the last 4 hours going through treads as I normally do when having problems but I created my first thread because I screwed up beyond what I can repair myself
edit: while in recovery, I made a backup of pdroid2.99 to see where it saved. When I opened the directly using my pc, I couldn't find that backup I just made. I put the nandroid onto my external sd card and that I could see it in recovery but I get the following error "Error while restoring /system!"
michaeln91 said:
I flashed PARANOIDANDROID 2.99 BETA3 from stock DLK4, 4.1.1. It worked but I was ready to revert back to the stock using the nandroid I made before flashing and realized that I did a factory reset when flashing pdroid and lost my nandroid backups. Fortunately I have older Nandroids from 12.12 on my pc. I placed it into the clockworkmod directory, sdcard\clockworkmod\backups, as I normally would but when I reboot into recovery I don't see the nandroid that I placed there. What do I do from here? I tried to do a factory reset from kies of DLK4 but afterwards I get stuck on the "Samsung" loading screen.
Any help would be appreciated. I spent the last 4 hours going through treads as I normally do when having problems but I created my first thread because I screwed up beyond what I can repair myself
edit: while in recovery, I made a backup of pdroid2.99 to see where it saved. When I opened the directly using my pc, I couldn't find that backup I just made. I put the nandroid onto my external sd card and that I could see it in recovery but I get the following error "Error while restoring /system!"
Click to expand...
Click to collapse
You flashed a 4.2 ROM with an out of date recovery by the sound of it. 4.2 modifies the directory structure of you're phone which is unsupported in old recoveries. I run TWRP myself and I just moved my backups to my new root folder which can be found in: /storage/emulated/0
CWM stores recoveries in blobs and I'm unsure if this method will work for you. Your only option if that doesn't work is to ODIN back to stock. Once you've performed an ODIN back, go into your recovery and factory reset, wipe cache and wipe dalvik.
Then update your recovery for future flashes. I recommend TWRP. Overall an easier recovery.
Sent from my SGH-I747 using xda app-developers app
I successfully flashed back to stock 4.1.1 using ODIN using the rom I got from samsung-updates. I've lost IMEI so I have to inject l that back later on. I'm using CWM 6.0.1.2 and when in recovery when I try to restore my backup and get to "error while restoring /system!"
I've been trying to find other threads, tried what they suggested but no luck
edit: I've found TWRP v2.3.3.1 and but I don't see /storage/emulated/0 instead I put my backup in /storagr/TWRP/BACKUPS/911de9 and tried to restore but it fails
What I did was make a nandroid on the ROM you have and just copy and paste the old one into the new directory and you can flash that old nandroid. Worked perfect for me
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
hednik said:
What I did was make a nandroid on the ROM you have and just copy and paste the old one into the new directory and you can flash that old nandroid. Worked perfect for me
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
Click to expand...
Click to collapse
This is what I typically do but now I get "error while restoring /system!" when restoring any of my old nandroid backups!
Why I like twrp. Maybe most of it is just a placebo but it seems more stable and easier to navigate
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
OK, so I'm used to phones with external SD cards where backing up was very easy. With the GN its a pain in the ass. After flashing a rom and factory resetting it, CWM can not find my back ups. I can see them with root explorer on the "sdcard" but CWM doesn't. I tried dragging them to /data/media/, but cwm doesn't see them.
I saved the back up to my pc before resetting as well. Where can I put it so CWM sees it?
I have the same problem with Titanium Back up. I backed up all apps and data, but after the wipe they were gone. I saved the back up on my PC but now I don't see a titanium backup folder to drag them too.
I realize this question has been asked before but all my research points me to dead ends.
Any help would be appreciated.
edit: was able to to drag an old backup to CWM, tried to restore and it failed. Phone is now stuck at Google logo :/. Factory resetting it again did not help.
update your CWM.
Zepius said:
update your CWM.
Click to expand...
Click to collapse
It doesn't matter, I flashed back to stock and rerooted. How can I avoid this in the future. It seems that if I wipe data I lose my back ups. How can I save my back ups in the future?
Zepius said:
update your CWM.
Click to expand...
Click to collapse
.....
If you just put your backup in data/media/ then CWM might not see it. Mine are in data/media/clockworkmod/backup/
This is why I use TWRP now.
I've had a bad CWM backup/restore operation fail. I think the dev of CWM is losing the ball and TWRP is starting to become the better recovery solution now.
deleted
akira02rex said:
This is why I use TWRP now.
I've had a bad CWM backup/restore operation fail. I think the dev of CWM is losing the ball and TWRP is starting to become the better recovery solution now.
Click to expand...
Click to collapse
I've never once had any errors or failed operations or issues of any kind since using CWM Recovery. Even with my old phone (which was not technically CWM, but based on it). Its hard for me to blame CWM and say that those issues are NOT user error.
If you go from a 4.1.X ROM to a 4.2.X ROM then you will have this problem because it changes the file structure that android uses. Same would occur on TWR. You just need to move the files to the correct location after the fact.
Sent from my Galaxy Nexus using xda app-developers app
pyroemaniac said:
If you go from a 4.1.X ROM to a 4.2.X ROM then you will have this problem because it changes the file structure that android uses. Same would occur on TWR. You just need to move the files to the correct location after the fact.
Sent from my Galaxy Nexus using xda app-developers app
Click to expand...
Click to collapse
Problem is that I tried moving the backup from the old location to the new. When I tried to restore, it failed and never was able to boot past the google logo. I had to unroot and flash back to stock. A great feature that I wish CWM had would be to direct it to where we keep the backup and just restore from there. Since the change from 4.1 to 4.2 I have read many people having similar issues.
Do you have cwm making a md5 for your backup? If not hat is the only time I've had trouble restoring. I've switched from 4.2 to 4.1 and vice versa multiple times without problems.
Also are you using cwm touch or non touch?
Sent from my Galaxy Nexus using xda app-developers app
Also, like others have said, make sure you are using the latest CWM. You can easily get it by downloading ROM manager and selecting "Flash ClockworkMod Recovery". It will also tell you what version you have and what version is the latest.
Thanks for the help. I'm also having problems with titanium back up. I copied the backup folder before the wipe, I dragged the files back to the titanium back up folder but TB doesn't recognize the back ups.
spillner said:
Thanks for the help. I'm also having problems with titanium back up. I copied the backup folder before the wipe, I dragged the files back to the titanium back up folder but TB doesn't recognize the back ups.
Click to expand...
Click to collapse
In Titanium Backup, select menu then preferences. Scroll down and select backup folder location. Tap the "detect" button then whole device. It should find it.
Also I'd grab a cheap otg adapter... And a 32gig min flash drive to backup to. I have mine run overnight (otg w/charging port) it's basically like having external just deciding when you need it
Sent from my Galaxy Nexus using Tapatalk 2
pyroemaniac said:
If you go from a 4.1.X ROM to a 4.2.X ROM then you will have this problem because it changes the file structure that android uses. Same would occur on TWR. You just need to move the files to the correct location after the fact.
Sent from my Galaxy Nexus using xda app-developers app
Click to expand...
Click to collapse
an up to date version of CWM or TWRP will 'move' (actually rename with the new path) your file system for you so you don't have to do it manually - that's why peeps keep on telling you to update your recovery...
help!
spillner said:
Problem is that I tried moving the backup from the old location to the new. When I tried to restore, it failed and never was able to boot past the google logo. I had to unroot and flash back to stock. A great feature that I wish CWM had would be to direct it to where we keep the backup and just restore from there. Since the change from 4.1 to 4.2 I have read many people having similar issues.
Click to expand...
Click to collapse
I have the same exact problem. When I try to move the backup to the main sdcard directory (a 3 gig file) it fails halfway through. No matter if I use adb push or windows/mtp to copy/paste the file.
Any ideas? Please help, I just want to restore my old rom with all my data. I dont care about 4.2 if I dont have my data.
EDIT:
I FIXED IT! This is how I did it. I had backed up my SD card (including clockwork backups) to my computer using adb pull. So I used clockworkmod recovery to format the SD card and /data/media. Then I started up the phone. I used windows to copy the backups to the phone. Now when I went to clockwork and tried to use the restore backup, it worked correctly. I'm now back to my old phone
I have a solution
spillner said:
OK, so I'm used to phones with external SD cards where backing up was very easy. With the GN its a pain in the ass. After flashing a rom and factory resetting it, CWM can not find my back ups. I can see them with root explorer on the "sdcard" but CWM doesn't. I tried dragging them to /data/media/, but cwm doesn't see them.
I saved the back up to my pc before resetting as well. Where can I put it so CWM sees it?
I have the same problem with Titanium Back up. I backed up all apps and data, but after the wipe they were gone. I saved the back up on my PC but now I don't see a titanium backup folder to drag them too.
I realize this question has been asked before but all my research points me to dead ends.
Any help would be appreciated.
edit: was able to to drag an old backup to CWM, tried to restore and it failed. Phone is now stuck at Google logo :/. Factory resetting it again did not help.
Click to expand...
Click to collapse
I was able to solve this problem. Check my post (above this) and the edit! Goodluck!
Reviving this thread
I am reviving this thread because I would like to know if there is any way to preserve CWM backups and Titanium Backup files when wiping data for a new ROM install.
Is it possible to create a symlink using terminal and link to a static directory which could be protected from wiping data? This is granted the shell permits symlinks.
Thoughts?
I'm a bit confused. I backed up my CM10.0 ROM today using Rom manager. It saved to my ext sd/clockworkmod/backup. Attempting to install CM10.2, kept boot looping after install (darkside wipe, flash Rom, clear dalvik), read a few posts saying upgrade recovery and re flash should fix. Ended up flashing to twrp 2.6.3.1, re flashed cm10.2 and same boot loop. Regardless, I wanted to restore from my back up, but twrp wouldn't locate the restore (which I assume is because it was saved to cwm folder and twrp would look in twrp/backups. So I just re flashed cm10.0 and figured I would use ROM manager to restore from back up. The back up is in sdcard1/clockworkmod/backup and ROM Manager says no backups found. I copied it to the internal sdcard0/clockworkmod/backup folder, still says no backups found. I then copied it to the twrp/backups folder thinking maybe because ROM Manager recognizes I am using twrp that it might be looking there for my back up. So I have a back up, it's there, I just can't get it to show up in ROM Manager or in twrp recovery... I find it frustrating that I can't manually browse to it's location from either, given I know exactly where it is. Where does ROM Manager look for backups so I can move it there? Thanks in advance
Sent from my SAMSUNG-SGH-T989 using xda app-developers app
You can't restore an entire rom image with rom manager. Just apps and data. As far as I remember ...unless rom manager has changed.
The only way to backup and restore entire images is through twrp and cwm. One or the other.
You probably need to flash from scratch now.
Sent from my Moto X cellular telephone...
kj2112 said:
You can't restore an entire rom image with rom manager. Just apps and data. As far as I remember ...unless rom manager has changed.
The only way to backup and restore entire images is through twrp and cwm. One or the other.
You probably need to flash from scratch now.
Sent from my Moto X cellular telephone...
Click to expand...
Click to collapse
The only option is to "back up current ROM". And even if it does just back up apps and data, that's all I need. Obviously if you have ROM Manager running you're running a ROM. The problem is, whether it backed up the ROM, or just the apps and data, the back up it made does not show up in ROM Manager, but is definitely in the backup folder, viewable through any file manager
Sent from my SAMSUNG-SGH-T989 using xda app-developers app
Nandroid backups and titanium backup are what most use. Always seen mixed reviews about rom manager.
Sent from my Moto X cellular telephone...
Hey everyone, I've recently backed up my stock rooted 4.4.2 TW rom (OTA) so I could flash a custom rom to check out some of the other KitKat development going on.
After fullfilling my curiosity, I wanted to restore my most recent TWRP backup, but after going through all the motions, TWRP says "restore successful in 536 seconds" which seems a little fast for a TW backup/restore. I restart the system, and my phone was stuck on the Galaxy S4 flash screen. Desperate, I then rebooted into TWRP to do a factory reset, but after trying to boot into the system after that, same results.
I have a feeling this is because I have the recent NB4 bootloader (Knox is tripped) and my backups are stored on my external SDcard.
If anyone knows any fixes for this issue, I would appreciate any input. I did search the web for any threads with anyone who is experiencing the same issue as me, but I don't think anyone was dumb enough to download the OTA, then root their phone.
I am also willing to reflash the stock firmware (4.4.2 OTA) from SamMobile website via mobile Odin. However, I'm not sure if this is a risky method to get back to stock 4.4.2.
Thanks in advance.
Sent from my Nexus 7 using XDA Premium 4 mobile app
I would also like to mention that I have two backups, one was April 1st, and the other one was April 3rd. They both are backups of the same stock ROM, and they both won't restore in TWRP.
In ES File explorer, I can see that both backups are taking up about 4 GBs of storage, so I know the data is there.
Thanks again...
Just had the same problem with mine
paulrileysullivan said:
I would also like to mention that I have two backups, one was April 1st, and the other one was April 3rd. They both are backups of the same stock ROM, and they both won't restore in TWRP.
In ES File explorer, I can see that both backups are taking up about 4 GBs of storage, so I know the data is there.
Thanks again...
Click to expand...
Click to collapse
Just had the same problem with mine, There was something wrong with the TWRP 2.7.0.0 recovery. I could not flash any back-up I previously made, or get it to install any zip files either.
How I got around it...go to TWRP website and get the latest Odin flashable version 2.7.0.1 (Tar file) and flash it that way. From there I was able to get into recovery and my previous back-ups flashed properly.
Best of luck to you, TWRP recovery updates can be hit or miss at times (various versions). This is not the first time I have had issues from trying to update TWRP (especially when doing it VIA goo-manager... updating by Odin seems to be the better option from my experiences)
crockashat said:
Just had the same problem with mine, There was something wrong with the TWRP 2.7.0.0 recovery. I could not flash any back-up I previously made, or get it to install any zip files either.
How I got around it...go to TWRP website and get the latest Odin flashable version 2.7.0.1 (Tar file) and flash it that way. From there I was able to get into recovery and my previous back-ups flashed properly.
Best of luck to you, TWRP recovery updates can be hit or miss at times (various versions). This is not the first time I have had issues from trying to update TWRP (especially when doing it VIA goo-manager... updating by Odin seems to be the better option from my experiences)
Click to expand...
Click to collapse
I tried 2.7.0.1 and 2.7.0.0 and they both aren't working. I used the latest version to do the backups, but it just won't restore! Its terrible. Do you think Knox has anything to do with this issue?
Sent from my Nexus 7 using XDA Premium 4 mobile app
paulrileysullivan said:
I tried 2.7.0.1 and 2.7.0.0 and they both aren't working. I used the latest version to do the backups, but it just won't restore! Its terrible. Do you think Knox has anything to do with this issue?
Sent from my Nexus 7 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Try TWRP 2.6.3.0 or try Philz Touch CWM. Id say one will work
pahick said:
Try TWRP 2.6.3.0 or try Philz Touch CWM. Id say one will work
Click to expand...
Click to collapse
Will Philz Touch CWM be able to restore a TWRP backup? I just tried TWRP 2.6.3.0, and it still didn't work.
If I were you I would try 2.6.3.1, if that doesn't work, try 2.5.0.2. For future backups, (not sure if you do this or if others do this, but I do) restore the backup you just made, so you can be 100% sure it restores correctly.
I also had problems just like that and I would point you here to see the discussion and solution.
http://forum.xda-developers.com/showthread.php?t=2691336
Same issue here note 3 sprint tried every single twrp for 4.4.2 and neither one restores but when i back it up to internal it works ,im thinking it has something to do with sd card read on twrp side
---------- Post added at 06:35 AM ---------- Previous post was at 06:32 AM ----------
I just got my 64 gig sd card i doubt it can be card its brand new and also when i dload stuff it goes on my sd card and if i leave the file there for more than 10 min it goes bad . Like zip files wont open or flash and when i download it to internal it works fine.