I recently switched over to team win recovery from cwm. I do like the ui and functionality way better then cwm. The problem I'm having is that I cannot access my back up files from my PC via USB. When I use the file browser that is built into twrp I can see the back up files in the twrp folder. When I plug my tablet into my PC via USB and open the twrp folder it is empty. Also when I open the twrp folder in es file browser it is empty there too. I would like to store the back up on my PC rather then on my tablet. Am I missing something? I was having this same problem with titanium with backed up apps so I upgraded to the paid version and uploaded my back ups to Google drive. After that I looked in the titanium back up folder again on my PC and all the sudden the files were there when before they were not. Its very frustrating. Please help.
Sent from my Nexus 7 using Xparent Green Tapatalk 2
I had this same problem with TWRP when I started using it a couple of days ago. I'm not rooted, just unlocked and using fastboot to load the recovery image temporarily to do backups. And when I went looking for the backup files to move to my computer, I couldn't find them. It turns out to be a permissions issue, with TWRP creating the files/directories owned and visible only to root. Not a problem if backing up to a FAT formatted sdcard, but it is a problem with the Nexus 7 since it honors permissions and ownership of all files on the "sdcard".
Two fixes that I know of, though I have only used one so far:
1) After you do the backup, open up the psuedo terminal in TWRP and manually change the permissions or owner of the files recursively. Just set the starting directory in TWRP to "/sdcard/TWRP" and do "chown -R media_rw.media_rw BACKUPS" to change the owner, or do "chmod -R og+rw BACKUPS" to change the permissions. You really only have to do one of those, and I went with the owner change. I was then able to see the backup when connected to my computer, copy the files off, and then delete them to avoid taking up space on the tablet.
2) Although I haven't tried it yet, supposedly you can backup and restore directly to/from a USB thumb drive connected via OTG cable. This would be the easiest method for me, since I want backup and restore capability but without actually storing anything on the Nexus 7. I'm going to try it with a backup tomorrow, but I read about someone doing just that thing for the same reasons in a comment on reddit.
Hopefully that answers your question and gives you a way around it.
Just wanted to bump and let you know that the permissions issue seems to be properly resolved in the 2.2.1.5 version of TWRP. If you update then you shouldn't have to go through any crap to get at the backups.
Additionally, I tried doing a backup to a USB drive and it worked perfectly, so if you prefer that route it is definitely an option. Just make sure that you have the USB drive connected before you boot into TWRP, otherwise it doesn't notice the drive.
mtrs said:
I had this same problem with TWRP when I started using it a couple of days ago. I'm not rooted, just unlocked and using fastboot to load the recovery image temporarily to do backups. And when I went looking for the backup files to move to my computer, I couldn't find them. It turns out to be a permissions issue, with TWRP creating the files/directories owned and visible only to root. Not a problem if backing up to a FAT formatted sdcard, but it is a problem with the Nexus 7 since it honors permissions and ownership of all files on the "sdcard".
Two fixes that I know of, though I have only used one so far:
1) After you do the backup, open up the psuedo terminal in TWRP and manually change the permissions or owner of the files recursively. Just set the starting directory in TWRP to "/sdcard/TWRP" and do "chown -R media_rw.media_rw BACKUPS" to change the owner, or do "chmod -R og+rw BACKUPS" to change the permissions. You really only have to do one of those, and I went with the owner change. I was then able to see the backup when connected to my computer, copy the files off, and then delete them to avoid taking up space on the tablet.
2) Although I haven't tried it yet, supposedly you can backup and restore directly to/from a USB thumb drive connected via OTG cable. This would be the easiest method for me, since I want backup and restore capability but without actually storing anything on the Nexus 7. I'm going to try it with a backup tomorrow, but I read about someone doing just that thing for the same reasons in a comment on reddit.
Hopefully that answers your question and gives you a way around it.
Click to expand...
Click to collapse
Thank you for the tip. I went everywhere yesterday...
Best buy, radio shack, staples etc looking for an otg cable and had no luck. I'm going to order one online today. I will give the other techniques a try today though. I'm not familiar with pseudo terminal but I'm gonna dig in anyway. That's the best thing about these gadgets for me is hacking in and figuring out. Thanks again for your help!
mtrs said:
Just wanted to bump and let you know that the permissions issue seems to be properly resolved in the 2.2.1.5 version of TWRP. If you update then you shouldn't have to go through any crap to get at the backups.
Additionally, I tried doing a backup to a USB drive and it worked perfectly, so if you prefer that route it is definitely an option. Just make sure that you have the USB drive connected before you boot into TWRP, otherwise it doesn't notice the drive.
Click to expand...
Click to collapse
When I first started out with twrp I flashed 2.2.1.2 via adw. That was before I knew about the goo option in the play store. I've since upgraded to 2.2.1.5 and still having the same issue.
Sent from my Nexus 7 using Xparent Green Tapatalk 2
norcal61 said:
When I first started out with twrp I flashed 2.2.1.2 via adw. That was before I knew about the goo option in the play store. I've since upgraded to 2.2.1.5 and still having the same issue.
Click to expand...
Click to collapse
I think that it only works with newly created files. So your existing backups will still have the wrong permissions, but new ones will be correct.
It's the old permissions on directory structure that will mess you up though. If you delete the "/sdcard/TWRP/BACKUPS" directory through TWRP, you will lose your existing backups, but then the next backup that you do should recreate the full directory path with the correct permissions on all of the files and directories. After that you shouldn't have any trouble accessing the backups. I tested that on mine just to be sure that it worked and it did fine for me.
If you don't want to lose your existing backups then just do the owner/permissions change that I mentioned before and you will have access to the old backups as well as having the new ones created with the correct permissions from the start.
mtrs said:
I think that it only works with newly created files. So your existing backups will still have the wrong permissions, but new ones will be correct.
It's the old permissions on directory structure that will mess you up though. If you delete the "/sdcard/TWRP/BACKUPS" directory through TWRP, you will lose your existing backups, but then the next backup that you do should recreate the full directory path with the correct permissions on all of the files and directories. After that you shouldn't have any trouble accessing the backups. I tested that on mine just to be sure that it worked and it did fine for me.
If you don't want to lose your existing backups then just do the owner/permissions change that I mentioned before and you will have access to the old backups as well as having the new ones created with the correct permissions from the start.
Click to expand...
Click to collapse
Cool, that totally makes sense. Can't believe I didn't try that all ready. I will definitely make a new back up with the latest version of twrp. I'm running the same ROM and kernel as the back up that I currently have stored. Gonna give it a shot right now and let you know how it works.
Sent from my Nexus 7 using Xparent Green Tapatalk 2
mtrs said:
I think that it only works with newly created files. So your existing backups will still have the wrong permissions, but new ones will be correct.
It's the old permissions on directory structure that will mess you up though. If you delete the "/sdcard/TWRP/BACKUPS" directory through TWRP, you will lose your existing backups, but then the next backup that you do should recreate the full directory path with the correct permissions on all of the files and directories. After that you shouldn't have any trouble accessing the backups. I tested that on mine just to be sure that it worked and it did fine for me.
If you don't want to lose your existing backups then just do the owner/permissions change that I mentioned before and you will have access to the old backups as well as having the new ones created with the correct permissions from the start.
Click to expand...
Click to collapse
No luck. That's weird. I deleted the folder SD/twrp/backups containing the back up, did another back up and still not visible on my PC or in es file browser.
norcal61 said:
No luck. That's weird. I deleted the folder SD/twrp/backups containing the back up, did another back up and still not visible on my PC or in es file browser.
Click to expand...
Click to collapse
Hmm, you may have to delete "/sdcard/TWRP" as well, and just let it recreate everything. I might have changed the permissions on it already on mine, which is why it worked for me just deleting BACKUPS. I'll double-check that when I get back home and make sure.
mtrs said:
Hmm, you may have to delete "/sdcard/TWRP" as well, and just let it recreate everything. I might have changed the permissions on it already on mine, which is why it worked for me just deleting BACKUPS. I'll double-check that when I get back home and make sure.
Click to expand...
Click to collapse
It worked! I deleted the twrp folder all together and it worked like a charm. I'm now able to see and move the backups to my PC. Thank you very much for your help. It is greatly appreciated!
Sent from my Nexus 7 using Xparent Green Tapatalk 2
Some path is :
/data/media/TWRP/BACKUPS/
You need copy to /sdcard/TWRP/BACKUPS and connect to pc will see it.
trungdtdev said:
Some path is :
/data/media/TWRP/BACKUPS/
You need copy to /sdcard/TWRP/BACKUPS and connect to pc will see it.
Click to expand...
Click to collapse
I had the same issue and tried searching for "TWRP" to locate every instance of that folder. Turns out that I had previous backups in:
/mnt/shell/emulated/TWRP/BACKUPS/
I am happy to report that I was able to delete several past and hidden backups and recovered over 9gb of space!
Related
So I've installed a custom ClockworkMod recovery and ROM on my Nexus 7 tablet. Life was good. Recently, I was running out of space and decided to delete my CWM backup (after saving it to my computer). And then, I realized I couldn't.
I went into ES File Explorer to try. I couldn't do it there.
I went into the ADB shell as root to try to remove it. No luck again, just the message when I finally DID try to remove one file:
Code:
# rm boot.img
rm failed for boot.img, Operation not permitted
What am I doing wrong?
Edit: This looks like it's ClockWorkMod (5.8.??)'s fault, but besides reading that another backup won't make the current one much larger, I don't actually know how to delete the current one.
Try "rm -rf ddd" (where "ddd" is the directory name) on the directory containing the files.
Sent from my Nexus 7
BillGoss said:
Try "rm -rf ddd" (where "ddd" is the directory name) on the directory containing the files.
Sent from my Nexus 7
Click to expand...
Click to collapse
in the development section there is a cwm flashable.zip that will delete them.. Then upgrade to latest cwm or TWRP.. its a bug from older version of cwm.. its talked about in the dev cwm thread..
good luck..
I did this in a way not mentioned here that still deserves mentioning... First I updated to the latest version of CWM available (via the Nexus 7 Toolkit) and then booted into recovery, opened the backup option, deleted the backup that was there, then cleaned the nandroids.
I could not find the aforementioned flashable zip, and because of the new CWM I had, I wanted to attempt a proper method of removal before running another rm command via the terminal. Therefore I could not verify the other methods mentioned here, my apologies.
erica_renee said:
in the development section there is a cwm flashable.zip that will delete them.. Then upgrade to latest cwm or TWRP.. its a bug from older version of cwm.. its talked about in the dev cwm thread..
good luck..
Click to expand...
Click to collapse
primetechv2 said:
I could not find the aforementioned flashable zip, and because of the new CWM I had, I wanted to attempt a proper method of removal before running another rm command via the terminal. Therefore I could not verify the other methods mentioned here, my apologies.
Click to expand...
Click to collapse
Sorry for re-opening an old thread, but I am having a problem where I have files that I cannot delete from the clockworkmods/blobs folder on my external sd card. So far, I have tried deleting them from a file explorer, deleting them as root from a file explorer, root and non-root deletes from terminal emulator, deleting through windows, adb shell deletes (with system booted).
I also wanted to try adb shell while booted into cwm, but I could not get the adb connection to work from recovery.
I also tried to find the zip file in the developer section and that's the real reason why I revived this thread...Does anyone know where the thread is with the zip file to remove these files?
I think the only way to delete them is through cwm.Boot to recovery and use the menu to delete them.
Sent from my SGH-I927 using xda app-developers app
Kodiack99 said:
I think the only way to delete them is through cwm.Boot to recovery and use the menu to delete them.
Sent from my SGH-I927 using xda app-developers app
Click to expand...
Click to collapse
When I booted to recovery, I am able to delete each of the backups that I created. These all deleted correctly. I then went to Free unused backup files (to delete the files/folders in the blobs folder) and ran that and most of the files are gone. When I boot back into the phone, there are still some files/folders there and they seem to be taking up about 4-5 GB on the card. When I try to delete them through the file manager apps (either as root or not) they will not delete and the manager reports an error (before clicking delete, the manager displays a statistics report that says that the size of the files are over 2TB so obviously something is very messed up about them). I have also tried to delete them through the terminal (again as root and regular user) and they will not delete there either and they totally mess up the terminal window with unprintable characters (the only way to recover is to exit out of the current window and start a new one).
I finally fixed this problem last night by backing up all of my stuff (except the clockworkmod folder) to my computer. I then rebooted into recovery (latest version of CWM non-touch) and formatting the ext SD Card. When I rebooted there were still some folders there (including the clockworkmod folder). I did a format from within the OS and that cleared everything out. I copied all of my stuff back from my computer and I'm now good to go. Not sure how it got messed up to begin with, but the problem is fixed now. I think I'm going to stick with TWRP from now on.
So I would like to transfer my nexus 7 nandroid backups to my PC. Since I only have an 8GB N7, I dont want to waste alot of space with nandroid backups. My question is, when connecting my N7 to my PC via USB cable, which folders do I need to transfer? The reason I'd like to do this is because I need to do a factory restore on my device, but after I get the factory restore done, I want to be able to reflash CWM and then use the files on my computer to restore my N7 (after transferring the files back to my N7 of course) Any help would be much appreciated!
Just cut the clockworkmod folder from the internal storage. Then if you Need to restore just drop it back
Sent from my HTC One X using xda app-developers app
I have had to do this as well. I keep my nandroid and TiBu files on my PC between ROM updates.
bagofcrap24 said:
Just cut the clockworkmod folder from the internal storage. Then if you Need to restore just drop it back
Sent from my HTC One X using xda app-developers app
Click to expand...
Click to collapse
Sorry, but I never thought about this before. If I delete the CWM folder from my tablet, it will remain in my tablet folder on my PC? Then, if I need to do a restore, I can just connect to the PC and add it back to my tablet and restore? Is this correct?
No. Plug your tablet in
Open Nexus 7
Internal storage
Copy the folder clockworkmod to a place on your pc
Once complete delete it from internal storage
If you need to restore
Plug in
Open Nexus 7
Internal storage
Copy clockworkmod folder back from pc to internal storage
Sent from my Nexus 7
I realize this thread is a bit old, but I have been searching and I cant find the answer. My problem is simple. The clockworkmod folder simply does not show up on my PC. The directories that show are the ones for my apps etc, and I can't seem to dig deeper than that. On my Nexus 7 I can browse right to the backups, but I cannot access them from the PC. I have no clue why. I successfully rooted 4.2.2 yesterday and everything else I've done has worked fine, but I can only access the clockworkmod folder from the Nexus 7 itself or from the adb shell on the PC (but I have no idea if I can use the shell to move the backup file to the PC or not).
So in short, I have no idea what to do. I recognize that I am a noob here, but I have done my homework searching for this particular issue and I haven't been able to find anything resembling a solution.
Mjolniir said:
I realize this thread is a bit old, but I have been searching and I cant find the answer. My problem is simple. The clockworkmod folder simply does not show up on my PC. The directories that show are the ones for my apps etc, and I can't seem to dig deeper than that. On my Nexus 7 I can browse right to the backups, but I cannot access them from the PC. I have no clue why. I successfully rooted 4.2.2 yesterday and everything else I've done has worked fine, but I can only access the clockworkmod folder from the Nexus 7 itself or from the adb shell on the PC (but I have no idea if I can use the shell to move the backup file to the PC or not).
So in short, I have no idea what to do. I recognize that I am a noob here, but I have done my homework searching for this particular issue and I haven't been able to find anything resembling a solution.
Click to expand...
Click to collapse
The pathway for nandroid backup is not /storage/emulated/0 or /storage/sdcard0 or /sdcard
It's somewhere else, but I'm not sure exactly where. Download a root file manager like root explorer then search.
Sent from Nexus 7 3G using Tapatalk HD
stfudude said:
The pathway for nandroid backup is not /storage/emulated/0 or /storage/sdcard0 or /sdcard
It's somewhere else, but I'm not sure exactly where. Download a root file manager like root explorer then search.
Sent from Nexus 7 3G using Tapatalk HD
Click to expand...
Click to collapse
Thanks, I have been using the one that comes with ROM Toolbox. The path is data/media/clockworkmod but the problem is I can't access that from the PC. When I try to copy or move the backup file to a directory that I can reach from the PC, It fails. I just get a message saying copy failed or move failed and thats it. That happens with both ES file Explorer and the ROM Toolbox root file explorer. I can see the files just fine and they also appear to have read, write and execute permissions.
Perhaps I am doing something wrong as a user with these apps that I am not being allowed to copy or move these files.
Mjolniir said:
Thanks, I have been using the one that comes with ROM Toolbox. The path is data/media/clockworkmod but the problem is I can't access that from the PC. When I try to copy or move the backup file to a directory that I can reach from the PC, It fails. I just get a message saying copy failed or move failed and thats it. That happens with both ES file Explorer and the ROM Toolbox root file explorer. I can see the files just fine and they also appear to have read, write and execute permissions.
Perhaps I am doing something wrong as a user with these apps that I am not being allowed to copy or move these files.
Click to expand...
Click to collapse
OK, something occurred to me right after writing that reply. I have been trying to copy the whole folder containing the backup files instead of just copying the files themselves. So I went in one level deeper and selected all the individual backup files and was able to copy/paste them into a directory my PC can see and was able to copy them from there onto my PC hard drive. So problem solved I guess.
Difficult to transfer Nandroid to Win8 PC
I have spent the morning trying to find a certain way to transfer my TWRP folders/files to a Windows 8 PC, without luck:
If anyone knows of a simple way to do this please chip in.
Luckily I have an iMac which allows easy transfer from a Nexus device, so I was able to copy TWRP to the iMac and from there to a 32GB Flash drive, then carry that to the Win8 for copying. Not exactly what one would hope for in 2013.. but it works.
I looked at pulling TWRP using WUGfresh and a Nexus Toolkit and think myself lucky not to have ended up with a brick.
Any links to Howto for Windows 8 much appreciated
Mvh
Its as simple as
adb pull /data
Sent from my Galaxy Nexus
Pirateghost said:
Its as simple as
adb pull /data
Sent from my Galaxy Nexus
Click to expand...
Click to collapse
Can't get much simpler than that I guess
Thanks
So it's okay to just copy the backup itself to the computer desktop, then when I need it, transfer it back? I've been just going in to the CWM folder and copying the folder directly to my desktop. So if I need to I can just copy it back provided I put in the same folder?
nicholi2789 said:
So it's okay to just copy the backup itself to the computer desktop, then when I need it, transfer it back? I've been just going in to the CWM folder and copying the folder directly to my desktop. So if I need to I can just copy it back provided I put in the same folder?
Click to expand...
Click to collapse
of course....why would it NOT be ok?
Pirateghost said:
of course....why would it NOT be ok?
Click to expand...
Click to collapse
Well, I just wasn't sure if in the process of being transferred that windows might alter it somehow. I just transferred my Nandroid to my computer, deleted it off my phone, then transferred it back and booted into CWM. I went to restore just to see if it would show up and it did just fine.
I just wasn't 100% sure about it. It just seems too easy... lol. I have Nandroids of quite a few different Rom setups on my computer, I just never had to restore them yet. So hypothetically, if you had the storage space, you could take a Nandroid of every Rom setup you've had and be able to revert to them anytime?
I saw some video guides of people using Adb to transfer to their computers and wondered why they didn't just copy and paste it. I thought there must be a reason. I'm still relatively new to this (only been a few months since my first flash), so I'm still learning.
---------- Post added at 07:41 AM ---------- Previous post was at 07:02 AM ----------
Pirateghost said:
Its as simple as
adb pull /data
Sent from my Galaxy Nexus
Click to expand...
Click to collapse
And what would the advantage of doing it through adb pull command instead of just simply copying it to the desktop? Is it safer or what? That's why I wonder if doing it this way is safe, when everyone else does adb commands...
Sent from my Galaxy S3 on Beans build 15 via tapatalk 2
nicholi2789 said:
Well, I just wasn't sure if in the process of being transferred that windows might alter it somehow. I just transferred my Nandroid to my computer, deleted it off my phone, then transferred it back and booted into CWM. I went to restore just to see if it would show up and it did just fine.
I just wasn't 100% sure about it. It just seems too easy... lol. I have Nandroids of quite a few different Rom setups on my computer, I just never had to restore them yet. So hypothetically, if you had the storage space, you could take a Nandroid of every Rom setup you've had and be able to revert to them anytime?
I saw some video guides of people using Adb to transfer to their computers and wondered why they didn't just copy and paste it. I thought there must be a reason. I'm still relatively new to this (only been a few months since my first flash), so I'm still learning.
---------- Post added at 07:41 AM ---------- Previous post was at 07:02 AM ----------
And what would the advantage of doing it through adb pull command instead of just simply copying it to the desktop? Is it safer or what? That's why I wonder if doing it this way is safe, when everyone else does adb commands...
Sent from my Galaxy S3 on Beans build 15 via tapatalk 2
Click to expand...
Click to collapse
If you are using cwm, the backups are not user accessible and do not show up under /sdcard, and the only way of accessing them is with ROM manager or with a root explorer... Which makes it hard to transfer back and forth from a computer. If you use adb you will be able to pull everything available under /data/media
Sent from my Nexus 7 using Tapatalk HD
That's weird... The backups show up on my computer.... I just plug in and open my phone through my computer, then I go to the CWM folder and drag and drop it to the desktop. Usually takes about ten minutes to transfer because my nandroids are huge (2.2 gb). That easy. I now have transferred it to the computer and then transferred it back to my ext SD card and used it to successfully restore. Did it yesterday.
That's weird. I wonder why it would show up on my computer and not everyone else's?
nicholi2789 said:
That's weird... The backups show up on my computer.... I just plug in and open my phone through my computer, then I go to the CWM folder and drag and drop it to the desktop. Usually takes about ten minutes to transfer because my nandroids are huge (2.2 gb). That easy. I now have transferred it to the computer and then transferred it back to my ext SD card and used it to successfully restore. Did it yesterday.
That's weird. I wonder why it would show up on my computer and not everyone else's?
Click to expand...
Click to collapse
Depends on what version you are on
Sent from my Galaxy Nexus
Pirateghost said:
Depends on what version you are on
Sent from my Galaxy Nexus
Click to expand...
Click to collapse
Well i guess on windows 7/Beams build 15 it's visible.... But even when I still had the stock Jellybean Rom I was able to transfer my backups no problem...
In any event, I should probably get more familiar with adb so i am able to transfer that way or restore if I get bricked somehow... Adb is just so complicated to me though. I've read countless threads and other how tos, but i'm still hesitant to try anything serious. It's friggen intimidating. I have the toolkit installed and the path all set up on my computer and everything, I just haven't done much with it yet.
Sent from my Galaxy S3 on Beans build 15 via tapatalk 2
not your version of windows OR ROM.
are you on 4.2.2 with latest CWM?
I used ROM Manager to 'Backup Current ROM'. It seems like I saved a couple nandroid backups successfully but I can't find where they saved so I can transfer them to my computer. I checked internalstorage/clockworkmod/ but there is no "backup" folder present, only 3 small files called .nomedia, .salted_hash, and .settings.
When I go in ROM Manager and go to "Manager and Restore Backups" I can see three dated backups listed, where are those?
I just want to successfully perform a nandroid backup and move it to my computer. I have tinkered with this device twice and lost data both times because of unsuccessful backups to my computer (totally my fault). Still getting used to Android.
right under the "Backup Current ROM" option in ROM Manager you can see it says mnt/shell/clockwordmod/backup
It's where CWM stores backups, you cannot see the folder from computer. But you can pull it via adb or copy it to sdcard using a root explorer then move to computer
Sent from my Nexus 4 in a Faraday cage
KyraOfFire said:
right under the "Backup Current ROM" option in ROM Manager you can see it says mnt/shell/clockwordmod/backup
It's where CWM stores backups, you cannot see the folder from computer. But you can pull it via adb or copy it to sdcard using a root explorer then move to computer
Sent from my Nexus 4 in a Faraday cage
Click to expand...
Click to collapse
How exactly do I pull via adb?
provided you know how to use adb
adb pull "mnt/shell/emulated/clockwordmod" "C:/CWMbackups"
if you're not familiar with adb, well... go to the general section then read
Sent from my Nexus 4 in a Faraday cage
I'm having the same problem but I'm using TWRP. Is it possible to make TWRP store my backups in /data/media/0/TWRP instead? This is quite a mess to go through just to be able to make a copy of the backup on my PC...
Like the other guy said, just use root Explorer and copy the back ups, then past them in the faux sd card. This is the simplest way to do it. ADB can be challenging for the novice.
[email protected] via Nexus4
Don't know why...but my nandroid backups are in /mnt/shell/emulated/clockworkmod/backup
GretaLewd said:
Don't know why...but my nandroid backups are in /mnt/shell/emulated/clockworkmod/backup
Click to expand...
Click to collapse
Out of interest does anyone know why my backups are put there, I backed up using TWRP and it puts the backups there, but in recovery it looks to the sdcard/twrp folder so doesnt find the backups
same here. i've already browsed everything using file explorer but still cant find my cwm nandroid backup
Hi, i done the adb pull..
Later on if i wish to copy back to phone, do i need
to use adb push ? Thanks.
KyraOfFire said:
right under the "Backup Current ROM" option in ROM Manager you can see it says mnt/shell/clockwordmod/backup
It's where CWM stores backups, you cannot see the folder from computer. But you can pull it via adb or copy it to sdcard using a root explorer then move to computer
Sent from my Nexus 4 in a Faraday cage
Click to expand...
Click to collapse
thanks man
nsg86 said:
Hi, i done the adb pull..
Later on if i wish to copy back to phone, do i need
to use adb push ? Thanks.
Click to expand...
Click to collapse
You should be able to just drag and drop anywhere on the sdcard folder.
On another note why do I have to do an image verification every time I leave a comment?
I apologize for what I hope only 'appears' to be a redundant question.
I created a full system backup from TWRP recovery yesterday, in preparation of flashing another radio (.33). I usually always go right in and move it to dropbox to keep my N4's storage as clean as possible. However, I waited until today, and alas, it's not there. The internal storage on my phone, as Windows reports, has indeed gone down about 2.5GB, which seems accurate from the size TWRP reported the backup would be.
Btw, I've made numerous backups with TWRP. I'm perfectly comfortable with it. I know where they are kept (well, until this one). But there's no 'backup' folder in my TWRP folder.
When I did the backup, it always requires me to use internal storage. I'm assuming it sees the N4's sdcard as internal.
Any idea what I'm missing here?
I opened my N4 in Windows Explorer, highlighted everything in the internal storage folder, and it only added up to 6.4GB. Windows reports that there is only 2GB free of 12.9GB.
wvcadle said:
I apologize for what I hope only 'appears' to be a redundant question.
I created a full system backup from TWRP recovery yesterday, in preparation of flashing another radio (.33). I usually always go right in and move it to dropbox to keep my N4's storage as clean as possible. However, I waited until today, and alas, it's not there. The internal storage on my phone, as Windows reports, has indeed gone down about 2.5GB, which seems accurate from the size TWRP reported the backup would be.
Btw, I've made numerous backups with TWRP. I'm perfectly comfortable with it. I know where they are kept (well, until this one). But there's no 'backup' folder in my TWRP folder.
When I did the backup, it always requires me to use internal storage. I'm assuming it sees the N4's sdcard as internal.
Any idea what I'm missing here?
I opened my N4 in Windows Explorer, highlighted everything in the internal storage folder, and it only added up to 6.4GB. Windows reports that there is only 2GB free of 12.9GB.
Click to expand...
Click to collapse
use a file explorer on your device to make sure that its in the twrp folder, instead of looking using windows. i bet its there and windows is having issues.
I actually have ES File Explorer installed and looked there first. Only after I didn't find it did I look in Windows. Of course if I had tried Windows first, I would have come to the same conclusion.
Ok, I've found the problem. For some reason, it's in /data/media/twrp/backups. Weird, because /data/media is the 'real' location of /sdcard, right? The reference to it isn't showing in /sdcard/twrp..., but it's in the above referenced location.
So, no problem I thought. I'd just cut/paste it into the /sdcard/twrp folder, but can't because it says there's not enough room.
I'm not good at using a command prompt to move the file from it's current location to my computer.
Any suggestions?
wvcadle said:
Ok, I've found the problem. For some reason, it's in /data/media/twrp/backups. Weird, because /data/media is the 'real' location of /sdcard, right? The reference to it isn't showing in /sdcard/twrp..., but it's in the above referenced location.
So, no problem I thought. I'd just cut/paste it into the /sdcard/twrp folder, but can't because it says there's not enough room.
I'm not good at using a command prompt to move the file from it's current location to my computer.
Any suggestions?
Click to expand...
Click to collapse
that makes sense.
cant you upload it to dropbox from /data/media/? i dont really know the command line well, so i cant help you there.
wvcadle said:
Ok, I've found the problem. For some reason, it's in /data/media/twrp/backups. Weird, because /data/media is the 'real' location of /sdcard, right? The reference to it isn't showing in /sdcard/twrp..., but it's in the above referenced location.
So, no problem I thought. I'd just cut/paste it into the /sdcard/twrp folder, but can't because it says there's not enough room.
I'm not good at using a command prompt to move the file from it's current location to my computer.
Any suggestions?
Click to expand...
Click to collapse
Try "cp -r /data/media/twrp/backups/* /sdcard/twrp/"
If it still says not enough room, try "mv -r /data/media/twrp/backups/* /sdcard/twrp"
Otherwise use adb on your computer. "adb pull /data/media/twrp/backups/"
Hello everyone, I recently purchased the Desire 816 for Virgin Mobile, and could not find anything on rooting this device.
So... I figured it out on my own! I decided to write out a tutorial since there isn't anything out there about rooting this phone!
I'm also including a nandroid backup of my stock rooted rom if you don't want to go through all of the steps. You will still need custom recovery.
1. Unlock your bootloader, install custom recovery, and flash superuser. I used v_superuser's guide for this, so thanks to him!
Use his guide to install custom recovery and root: http://forum.xda-developers.com/showthread.php?t=2775801
The custom recovery he links to isn't made for the VM variant of this phone, but it works!
Now you can restore my clean install, rooted nandroid backup (link at end of post) if you don't want to do the following steps and still have full root.
2. Hopefully you were able to successfully install custom recovery and root.
Now this part is a bit tricky. Even with root HTC is stopping us from writing to system. For this we need to apply the wp_mod.ko module.
Download it here: http://forum.xda-developers.com/showthread.php?t=2707378
Copy this file to the root of your internal storage.
Now download Terminal Emulator from play store, run it and enter the following commands (you only need to do this once):
su
insmod /sdcard/wp_mod.ko
Once you do this go into your favorite root explorer and mount as R/W. Copy the wp_mod.ko file to /system/lib/modules
Now go to /system/etc and find install-recovery.sh. Open it with a text editor and add a new line at the end with the following:
insmod /system/lib/modules/wp_mod.ko
Reboot! If all went well the wp_mod module will run at boot every time so you won't have to do it manually each time!
Congratulations, you now have a fully rooted Desire 816!
Download my nandroid backup here (place the contained folder into the CWM backup directory):
https://drive.google.com/uc?id=0B0bhyG2E55hXaWtpeGVQaEpOVzA&export=download
Hope this helped anyone wondering how to root the device!
I just get md5 mismatch error when I try to restore
Never mind found out my phone wasn't downloading the whole back up
jcrt2000 said:
I just get md5 mismatch error when I try to restore
Click to expand...
Click to collapse
I'm not trying to offend with my answer. Just going for the easiest solution first...
Did you unzip the backup nandroid onto your PC? I imagine he zipped the actual Nandroid folder as it would have a date and time as the name.
If you unzip VM_HTC_Desire_816_Rooted_NandroidBackup.zip you SHOULD see a folder with a date and time. That is the actual nandroid that you'd copy to your Clockwordmod backup folder.
sirrx7 said:
I'm not trying to offend with my answer. Just going for the easiest solution first...
Did you unzip the backup nandroid onto your PC? I imagine he zipped the actual Nandroid folder as it would have a date and time as the name.
If you unzip VM_HTC_Desire_816_Rooted_NandroidBackup.zip you SHOULD see a folder with a date and time. That is the actual nandroid that you'd copy to your Clockwordmod backup folder.
Click to expand...
Click to collapse
^ this. And restore that from clockworkmod. I know it should work because I already had someone confirm it working.
Kontrary said:
^ this. And restore that from clockworkmod. I know it should work because I already had someone confirm it working.
Click to expand...
Click to collapse
It does work. I had to download on my pc to get the whole file downloaded.
jcrt2000 said:
It does work. I had to download on my pc to get the whole file downloaded.
Click to expand...
Click to collapse
Oh nice! Glad you got it working.
Kontrary said:
^ this. And restore that from clockworkmod. I know it should work because I already had someone confirm it working.
Click to expand...
Click to collapse
Also...
The act of unlocking the phone clears out your data so you might notice that your flashlight and calculator apps are missing. For some reason HTC didn't make those 2 system apps.
If you'd like them back, here you go.
http://forum.xda-developers.com/showthread.php?t=2699906
sirrx7 said:
Also...
The act of unlocking the phone clears out your data so you might notice that your flashlight and calculator apps are missing. For some reason HTC didn't make those 2 system apps.
If you'd like them back, here you go.
http://forum.xda-developers.com/showthread.php?t=2699906
Click to expand...
Click to collapse
Thank you, I sold the phone but never noticed that.
Thanks for this, I had deleted my stock backup
problems with the mod.ko
everything works until I get to the wp_mod.ko command when using the terminal command. It just says cannot open. I tried countless times but it says the same thing. Is there any other way?
dwest3784 said:
everything works until I get to the wp_mod.ko command when using the terminal command. It just says cannot open. I tried countless times but it says the same thing. Is there any other way?
Click to expand...
Click to collapse
If you're having too much trouble and are about to give up you can always download Kontrary's Nandroid backup. I didn't use it but I did look through it and it looks like he already did the write protect mod in it.
Just unzip it on your PC and put the dated folder in your clockworkmod/backup folder. Boot into CWM recovery and restore from his nandroid.
Out of curiosity... Are you hitting enter after SU and before insmod???
Also...
The command insmod /sdcard/wp_mod.ko is only good if you have wp_mod.ko sitting on the root of the internal sd. If its on your micro sd card you'll obviously have to change the path after insmod or just move it to the internal sd..
thanks
sirrx7 said:
If you're having too much trouble and are about to give up you can always download Kontrary's Nandroid backup. I didn't use it but I did look through it and it looks like he already did the write protect mod in it.
Just unzip it on your PC and put the dated folder in your clockworkmod/backup folder. Boot into CWM recovery and restore from his nandroid.
Out of curiosity... Are you hitting enter after SU and before insmod???
Also...
The command insmod /sdcard/wp_mod.ko is only good if you have wp_mod.ko sitting on the root of the internal sd. If its on your micro sd card you'll obviously have to change the path after insmod or just move it to the internal sd..
Click to expand...
Click to collapse
Thanks I figured it out last night. I put in the internal memory and it worked but thanks for the reply!
dwest3784 said:
Thanks I figured it out last night. I put in the internal memory and it worked but thanks for the reply!
Click to expand...
Click to collapse
Right on. Glad you got it working.
driver issue
ive downloaded and installed and uninstalled and rebooted and done everything i can think to do...ive tried on my PC and on my laptop...ive tried with every usb cable i have...including the one that came with the phone...i can not get windows to recognize my phone...so i cant even unlock the bootloader to begin this process...any suggestions or hints on what i could try?
any help??
dragonclaw88 said:
ive downloaded and installed and uninstalled and rebooted and done everything i can think to do...ive tried on my PC and on my laptop...ive tried with every usb cable i have...including the one that came with the phone...i can not get windows to recognize my phone...so i cant even unlock the bootloader to begin this process...any suggestions or hints on what i could try?
Click to expand...
Click to collapse
i really really need to get this phone rooted any help??
dragonclaw88 said:
i really really need to get this phone rooted any help??
Click to expand...
Click to collapse
Have you plugged it in while in Fastboot? Which OS are you running? I'm on Win 7 x64 and have it set to download drivers from Windows update, I didn't have any problems going that route.
Have you downloaded HTC Sync Manager? It has the drivers required for your PC to recognize your phone.
Kontrary said:
Download my nandroid backup here (place the contained folder into the CWM backup directory):
https://drive.google.com/uc?id=0B0bhyG2E55hXaWtpeGVQaEpOVzA&export=download
Hope this helped anyone wondering how to root the device!
Click to expand...
Click to collapse
I installed your CWM Backup after I couldn't figure out your steps... but now there's an ANNOYING notification that says, "Smith disabled... Click here to open." I open it, and no matter what settings I choose, this notification keeps POPPING UP! Is this your doing, or a known issue with this "Mod." All I wanted to do was uninstall all the Google/VM Bloatware. Now going back to stock might be the only fix... ????
That Smith app is a problem for most recent HTC phones. It has nothing to do with the CWM backup. It happens with the M8 and our 816.
I just long press the notification, click App Info and force close. It's usually good until you reboot your phone.
Either HTC or Sprint is supposed to be looking for a fix but who knows.
https://community.sprint.com/baw/thread/169142?start=0&tstart=0
jayblaze406 said:
I installed your CWM Backup after I couldn't figure out your steps... but now there's an ANNOYING notification that says, "Smith disabled... Click here to open." I open it, and no matter what settings I choose, this notification keeps POPPING UP! Is this your doing, or a known issue with this "Mod." All I wanted to do was uninstall all the Google/VM Bloatware. Now going back to stock might be the only fix... ????
Click to expand...
Click to collapse
I was able to stop this annoyance by simply going to Titanium Backup (root needed) and freezing the process.
I typed in Smith in the search bar of TB and it came back with this process/app called
"Smith 4.21-plat_4.4.2-KOT49H"
I believe it happens to come up when a specific "bloatware" app is unaccessible by the device when removed but I have not singled out which app is it so far.
I backed up the app first then froze it and it stopped the Smith popup error permanently even after reboots and power offs.
(You could possibly delete it but until the stock bloatware app that causes this pinpointed i wouldn't recommend it.)
Tested running everything is good no errors rebooted fine checked bootloader and recovery and both are fine as well.
Sent from my 710C using XDA Free mobile app