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
Related
********Please Mods remove thread if possible!! New Tatuyama fix (ext4) has been incorporated into SuperRooter by DesignGears ********
LINK: http://forum.xda-developers.com/showthread.php?t=751934
DISCLAIMER
DO IT ON YOUR OWN RISK.
ME OR ANYONE ELSE ON THIS FORUM IS NOT RESPONSIBLE FOR BRICKED/DEAD DEVICES AND/OR DEAD SD CARDS.
YOU SHOULD UNDERSTAND EVERY STEP IN THIS HOW-TO BEFORE ATTEMPTING TO FOLLOW.
**********EDIT LOG*******************
8/10/2010: Added Startup Issue Reversion
8/11/2010: Added Alternate Manual Method that might work better than AUTO
8/11/2010: Added Possible Method of Backing EXT2 Partition
Here everyone... I have been trying lag fixes all over the place and I always seem to have issues partitioning the external sd for the apps... so after so many attempts, this was BY FAR the best lag fix out there.... It doesn't rely on the externalsd for functionality.
Easy and nothing special needed.
The steps below are pretty good, but I did things a little different.
Copied the update.zip to my external sdcard.
Then used Root Explorer to copy the update.zip to my internal sd card.
(******Here is the updated filed: http://forum.xda-developers.com/attachment.php?attachmentid=376882&d=1281390347******)
Then I used ROM Manager (Reboot into Recovery) to boot into the Linux Loader
Then I said update using update.zip (not install update.zip)
Then Reboot
For some reason it didn't install busybox 1.17.1 so install it manually
(located: http://forum.xda-developers.com/showpost.php?p=7574130&postcount=229)
Make sure after you install busybox.apk that you go into busybox and check to MAKE SURE you are running 1.17.1 ONLY. You might have an older version or newer version but it must be 1.17.1; if different just click install.
After that follow the MCR Scripts below. (Took about 6 minutes to do everything)
*** If MCR Scripts DOES NOT show up, its probably because you don't have the non market install hack on your phone. In the update.zip you can find the apk and install via ADB, but I didn't do it this way. ******
(Original Thread! Alternate method on OP in link below! Some people say it worked better for them.)
http://forum.xda-developers.com/showpost.php?p=7587405&postcount=417
@Tayutama
I ran the Tayutama update.zip using the up+power+menu button method, it installed in seconds and I restarted the phone. I ran the benchmark but still got 8xx scores. I'm an Noob, so needed more thorough instructions. These are now given below. NOTE: THIS METHOD IS MUCH MORE NOOB FRIENDLY AND DOES NOT REQUIRE A PC OR USB DEBUGGING MODE.
EDIT I had realised I needed to launch the newly installed MCR app after restart and choose a lagfix file to run. I ran the file and 'all complete'. This worked a treat. Ran Quadrant and now have a top score of 2114 running on JM2. System is much snappier. This mod of RyanZA fix by Tayutama is the most noob friendly also. Full instructions as follows:
EDIT Requirements: Make sure your phone has 'superuser' app installed by checking your app list. If it isn't installed, you can use a newer beta version of Tayutama's update.zip
available at; http://forum.xda-developers.com/atta...4&d=1281437129
Full instructions:
1. The update.zip installs all the files needed. It is attached here; http://forum.xda-developers.com/atta...2&d=1281390347
2. Place it on your internal sdcard
3. Turn off your phone.
4. Hold down Up+powerbutton+Menubutton for a couple of seconds until u see the galaxy logo .
5. Use the up and down buttons to get to update.zip.
6. Press menu button on update.zip to select it
7. It installs root, correct busybox (1.17.1) as well as all the scripts needed for the fix and the 'MCR Scripts' app to run the scripts. (NOTE: This version does not install superuser.app which is needed, although the beta update.zip does, so read 'requirements' above if needed)
8. After install, the phone restarts.
9. Go to the newly installed 'MCR Scripts' application from the app list, open it and choose from 3 scripts. For example, Lagfix10024 is the 1gb ex2 version.
10. The script should run and take a few minutes.
11. You should see an 'all complete' prompt, and this means you can close the application.
12. Run quadrant to test if the fix was applied.
Originally Posted by Tayutama
Don't know if you mind me posting this here RyanZA, but i made a update.zip out of your script. NOTE THIS ONLY WORKS ON 2.1
What this update.zip file does is that it copies a few files to your internal sdcard and installs ASE which can be used to run .sh files without the need to use a terminal.
There are 3 scripts included:
LagFix1024.sh - Makes a 1GB file on /data
LagFix512.sh - Makes a 512MB file on /data
RemoveFix.sh - Removes the lagfix
This also includes BusyBox 1.17.1 so no need to install that first.
Testet this on JM1
Click to expand...
Click to collapse
********Alternate Method that might even work better!! ****************
All the files are located in the update.zip file that you need to download.
1. Connect phone to PC, make sure adb can see it:
adb devices
2. adb kill-server
3. adb push createlagfix.txt /sdcard/createlagfix.sh
4. adb push playlogos1 /sdcard/playlogos1
5. adb push userinit.sh /sdcard/userinit.sh
6. adb shell su -c "/system/bin/sh /sdcard/createlagfix.sh"
7. adb kill-server
8. adb reboot
************ Reverting back if there are boot up and black screen issues ****************
If you have black screen and doesn't boot into the desktop, this is the fix to return back to normal state:
To fix that problem:
1. Boot into Recovery Mode (Vol Up + Vol Down + Power) Let go of Power after you see AT&T.
2. Delete User Cache
3. Delete All User Data
4. Then see if your phone boots up
5. If your phone does boot up then navigate to Settings -> Security -> Factory Reset
6. After factory reset your phone should be useable again.
DO NOT INSTALL THIS UPDATE IF YOU DO NOT KNOW WHAT YOU ARE DOING.
**********Possible method of Backing up Your EXT2 Partition **********
BTW I would also perform a NANDROID Backup as well which can be done by using ROM Manager to boot into the Android Loader....
Nandroid does NOT back up the apps off your SD card.
AppsToSD (I'm speaking re MoDaCo's rom here) uses the ext2 partition on your SD card for the /data/app and /data/app-private folders, where your actual downloaded application files are kept. Nandroid does NOT back this up, and simply mounting your SD card and copying the files off also does not back this up.
The only way to back up these critical folders is to directly copy them to somewhere else. You can use command line or Droid Explorer.
If you want to use command line, do this from an ADB shell or terminal:
mkdir /sdcard/backup/
mkdir /sdcard/backup/app
mkdir /sdcard/backup/app-private
cp -r /data/app/* /sdcard/backup/app/
cp -r /data/app-private/* /sdcard/backup/app-private/
This will create two folders on your SD card: app and app-private, both in a folder called Backup. It will then copy the entire contents of your /data/app and /data/app-private folders to your SD card.
After you do this, back up the entire contents of your SD card as normal.
To restore the files after replacing/partitioning your SD card, head to this thread:
http://forum.xda-developers.com/showthread.php?t=585349
Click to expand...
Click to collapse
Quadrant score was 917 and was on stock roms.....
Now Quad score is 2193 and still on stock roms.....
Tested on 2.1 Update 1 Captivate
Baseband: I897UCJF6
slider2828 said:
Quadrant score was 917 and was on stock roms.....
Now Quad score is 2193 and still on stock roms.....
Tested on 2.1 Update 1 Captivate
Baseband: I897UCJF6
Click to expand...
Click to collapse
Does it show strong real world improvements?
good job explaining nothing. troll harder
So....
This is a ""one step"" that isn't one step... ?.. ?
Oh, and for anyone wondering....
This appears to be the ext2 fix.
This IS the same fix from the otger thread, just packaged in update.zip format. Id be a bit more cautious using this one as it hasnt had as much testing among the I9000 crowd much less Captivate users.
Zilch25 said:
This IS the same fix from the otger thread, just packaged in update.zip format. Id be a bit more cautious using this one as it hasnt had as much testing among the I9000 crowd much less Captivate users.
Click to expand...
Click to collapse
Thanks for confirming this. I am seeing strong real world improvements, too. Dolphin Browser HD is very snappy and everything seems a lot faster (I am on stock captivate, btw, couldn't get this to work on I9000 for some reason).
Only thing is you should back up frequently because it can be corrupted a lot more easily since it is on ext2.
hm... i applied the update in clockwork mod recovery, i have super user and the correct busybox version installed and rebooted the system. i went to the app list and could not find the "MCR SCRIPT" you mentioned i should be seeing... am i doing something wrong?
THat is weird I saw mine in the apps list.... its just called MCR with a green dog bowl and light bulb....
Woops sorry for the truncation in the quote.... I have attached the update.zip file that you need to download.... The update.zip file you used is probably a ROM Manager Update.zip, so just rename it and copy the new update.zip file to the internal sd....
Sorry.....
solufein said:
good job explaining nothing. troll harder
Click to expand...
Click to collapse
What the hell does that mean.... You saying it doesn't work? Why not try it and it is an EXT2 fix.
max_warheads said:
So....
This is a ""one step"" that isn't one step... ?.. ?
Oh, and for anyone wondering....
This appears to be the ext2 fix.
Click to expand...
Click to collapse
This isn't one step because I don't have the USB cable with me. I just had a USB adapter for the microsd and I can't boot into the linux loader correctly without the cable, so I used ROM Manager. It would have been easier if I did.
Zilch25 said:
This IS the same fix from the otger thread, just packaged in update.zip format. Id be a bit more cautious using this one as it hasnt had as much testing among the I9000 crowd much less Captivate users.
Click to expand...
Click to collapse
Yup it is but on the internal card. Are you sure its the same? Look at the OG thread, a LOT of people have tried it with great success....
darth_vato said:
Thanks for confirming this. I am seeing strong real world improvements, too. Dolphin Browser HD is very snappy and everything seems a lot faster (I am on stock captivate, btw, couldn't get this to work on I9000 for some reason).
Only thing is you should back up frequently because it can be corrupted a lot more easily since it is on ext2.
Click to expand...
Click to collapse
How do you back it up?
i updated the zip and rebooted used busy box and i dont have that MCR app
Bionicboto said:
i updated the zip and rebooted used busy box and i dont have that MCR app
Click to expand...
Click to collapse
Same instructions before, did you download the update.zip? I just added that instruction. Can you try again after that?
slider2828 said:
THat is weird I saw mine in the apps list.... its just called MCR with a green dog bowl and light bulb....
Woops sorry for the truncation in the quote.... I have attached the update.zip file that you need to download.... The update.zip file you used is probably a ROM Manager Update.zip, so just rename it and copy the new update.zip file to the internal sd....
Sorry.....
Click to expand...
Click to collapse
when you say put the update.zip into the phone... do i put it in the internal sd card root? or do i put it in the ROM MANAGER folder? when i choose apply update, it only gives me one option to update from: /sdcard/update.zip. i choose that it installs properly and i reboot. i still don't the app, lol.
i also have removed the the recovery-update.zip or renamed it and tried to reboot into recovery mode via ROM MANAGER but it doesn't let me do it because it can't find the zip. then i tried to put the update into the the ROM MANAGER folder and it says it can't the find update.
its still the same cant find the app i reboot to recovery apply sd card update.zip go to yes and it says installed reboot and its not there
arsinic said:
when you say put the update.zip into the phone... do i put it in the internal sd card root? or do i put it in the ROM MANAGER folder? when i choose apply update, it only gives me one option to update from: /sdcard/update.zip. i choose that it installs properly and i reboot. i still don't the app, lol.
i also have removed the the recovery-update.zip or renamed it and tried to reboot into recovery mode via ROM MANAGER but it doesn't let me do it because it can't find the zip. then i tried to put the update into the the ROM MANAGER folder and it says it can't the find update.
Click to expand...
Click to collapse
Sorry for the bad reply.
Rename the update.zip that is already on the internal sd cards root because that is ROM Managers using ROOT Explorer
Then copy the update.zip that you downloaded to the external SD card.
Then copy update.zip from the external sd card to the internal sd cards root.
Then use ROM Manager to reboot into the linux loader.
Hope that helps?
-Ken
slider2828 said:
Sorry for the bad reply.
The update.zip that you use download, copy it the the internal sd card's root... (Basically where ROM Manager update.zip was. Like you did Rename the update.zip that is already there, because that is ROM Managers).
Hope that helps?
Click to expand...
Click to collapse
hm... the only update.zip i have is in the Recovery Mod folder named: recovery-update.zip. the only update.zip i have in the sdcard root is the update.zip i downloaded from the your url and have been applying that as the update. i seem to be having the same problem as Bionicboto.
should i have the rom manager's update.zip in there also or it doesn't matter? and i also have no external sd card. is that something i need in order to get this update working properly?
Did you ever perform a backup with the ROM Manager? That usually creates a update.zip.....
Basically when I log into root explorer and click on SDCARD.... you should see the update.zip in that folder along with Android folder, busybox folder, clockworkmod folder, DCIM folder, downloads folder, etc etc....
slider2828 said:
Did you ever perform a backup with the ROM Manager? That usually creates a update.zip.....
Click to expand...
Click to collapse
i preformed a backup right before i did all this. i did notice the update.zip in there. i took it out and put in the update.zip you uploaded. do i need both in there?
thanks for the quick replies btw.
Nope... Try this... with ROM Manager,
Choose Flash ClockWorkMod Recovery and that will recreate the boot files for ROM Manager.... and also backup your current ROM again.
Then try the steps again.
OMG Dude I noticed you in oakland, I am in hayward/san leandro.... We can try after I get off work which is in 30 minutes. and then take 30 minutes to get back to SL....
You wanna meet at the starbux on marina?
Flashed and installed perfectly. Bumped my quadrant up to 2117. Good post, thanks.
I've been running cm7 nightlies and now stable 7.0 for some time now. I have the new radio, ladios' kernel, and the sdcard read fix flashed.
I installed super manager and successfully deleted some of the stock cm7 media off my phone last week. Today, I came across the new GPS.conf files and wanted to try them.
Super manager couldn't switch the system to r/w despite saying "ok"
When I try to delete or write in the system with EStrongs file explorer, ghost commander, or android mate, they all give strange errors. The deleted files disappear but reappear after reboot. If I try to paste a file in system/etc I only get an error.
Superuser is successfully allowing permissions. I have the latest busybox. I have r/w enabled in each file manager.
I even tried an adb push test which first said "system is r/o only". The next try was "successful" but didn't do anything.
I'm still new with adb so I probably did something wrong. I typed in that r/w command, mount now shows: /dev/block/mtdblock3 on /system type yaffs2 (rw,relatime)
I can't figure out what changed and what I need to do to get r/w permissions. My only theory is that i had uninstalled and reinstalled super manager earlier and that somehow messed with my permissions.
You cannot permanently modify the system partition while the phone is booted into Android. The only way is to use adb while the phone is in recovery mode. Any changes you make while the phone is booted will be lost after a reboot.
Go check on those media files you thought you deleted. I bet you'll find they are still there.
Yes that worked. Thank you.
I thought I had read somewhere that you had to be booted to adb push.
I also thought that root managers advertising r/w capability would make permanent changes.
Next question:
Can I add and remove files from the cm7 zip before flashing it? Do I have to rezip it in any special or can windows 7 manage it fine?
EDIT: Ok I guess i need to sign it... lets see...
jamus28 said:
Yes that worked. Thank you.
I thought I had read somewhere that you had to be booted to adb push.
I also thought that root managers advertising r/w capability would make permanent changes.
Next question:
Can I add and remove files from the cm7 zip before flashing it? Do I have to rezip it in any special or can windows 7 manage it fine?
EDIT: Ok I guess i need to sign it... lets see...
Click to expand...
Click to collapse
You don't need to sign them on the aria
Sent from my Liberty using XDA App
jamus28 said:
Yes that worked. Thank you.
I thought I had read somewhere that you had to be booted to adb push.
I also thought that root managers advertising r/w capability would make permanent changes.
Click to expand...
Click to collapse
Those programs will work on some phones but not the Aria.
Next question:
Can I add and remove files from the cm7 zip before flashing it? Do I have to rezip it in any special or can windows 7 manage it fine?
EDIT: Ok I guess i need to sign it... lets see...
Click to expand...
Click to collapse
It really is as simple as adding or removing a few files from the zip file if you want to modify it.
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!
Trying to restore a NAND in CWM but it says "couldn't find directory, no files found" when I click "restore"
So i did a backup, and it shows up when I then hit "restore" in sdcard/clockworkmod/backup (listed at top of recovery screen) but when I boot and look on my sdcard, it shows the old backups I made in the folder listed, not the one I just made. I can't find the one I just made, even though if I reboot into recovery, it still shows it (the latest) and only it.
Any idea where the newest one is, and why I cant restore the older ones?
Are you running CWM 6.0.1.9?
Also, take a look at http://forum.xda-developers.com/showthread.php?t=1991657.
I am running v6.0.1.9 and the link you posted seems to say that this should be an issue resolved with this version. Though it did tell where to find the new backup.
It lists some adb commands to move the old backups to the new directory, can I just do that in rootexplorer with copy/paste?
TheAtheistReverend said:
I am running v6.0.1.9 and the link you posted seems to say that this should be an issue resolved with this version. Though it did tell where to find the new backup.
It lists some adb commands to move the old backups to the new directory, can I just do that in rootexplorer with copy/paste?
Click to expand...
Click to collapse
I don't see why you couldn't move the files with rootexplorer. Give it a try!
They moved fine
They are seen by recovery, and now I just switched to TeamWin recovery. We'll see if that sees them too.
Are we confident that wiping doesn't clear this location? I'm a little worried that a factory reset or something might wipe the data folder
TheAtheistReverend said:
They moved fine
They are seen by recovery, and now I just switched to TeamWin recovery. We'll see if that sees them too.
Are we confident that wiping doesn't clear this location? I'm a little worried that a factory reset or something might wipe the data folder
Click to expand...
Click to collapse
Please read the following
http://forum.xda-developers.com/showthread.php?p=34794673
If you are worried about losing the backups, copy them to your pc or onto OTG storage. I use cwm and my backups are now in /data/media/clockwork. If you activate multi-user, I think they go to /data/media/0/clockwork, but I can't test. Not sure about the TW recovery.
scott_doyland said:
Please read the following
http://forum.xda-developers.com/showthread.php?p=34794673
Click to expand...
Click to collapse
Confusing But the info is there. I don't like how complicated it ahs gotten to wipe, restore, recover, and flash. It used to be so simple...:silly:
In CWM it says the file location for the backups is /sdcard/clockworkmod/backup
When I go through AirDroid, Root Browser, Solid Explorer, etc. that directory is NEVER found. Where are these backups saved and how can I find them (and ultimately copy them to my PC). I've never had a problem in the past with my S2 doing this. What am I missing? Thanks.
Nosferatu. said:
In CWM it says the file location for the backups is /sdcard/clockworkmod/backup
When I go through AirDroid, Root Browser, Solid Explorer, etc. that directory is NEVER found. Where are these backups saved and how can I find them (and ultimately copy them to my PC). I've never had a problem in the past with my S2 doing this. What am I missing? Thanks.
Click to expand...
Click to collapse
have these file explorers been updated for the fs change in 4.2? root explorer shows correctly. try /data/media/0/clockworkmod/ or /data/media/clockworkmod/
simms22 said:
have these file explorers been updated for the fs change in 4.2? root explorer shows correctly. try /data/media/0/clockworkmod/ or /data/media/clockworkmod/
Click to expand...
Click to collapse
found it in data/media/clockworkmod thanks dude
So why does it do this?
Secondly, how can I get windows to fully see the entire device. MTP is limited in what you can see and also is rather slow in file transfers. Thanks a million dude!
Nosferatu. said:
found it in data/media/clockworkmod thanks dude
So why does it do this?
Secondly, how can I get windows to fully see the entire device. MTP is limited in what you can see and also is rather slow in file transfers. Thanks a million dude!
Click to expand...
Click to collapse
4.2 added multiple users per device. the main user is user 0. if you add more users to your device they become /data/media/1 and /data/media/2...
simms22 said:
4.2 added multiple users per device. the main user is user 0. if you add more users to your device they become /data/media/1 and /data/media/2...
Click to expand...
Click to collapse
okay. Well now CWM won't let me look through the entire device to flash a new update/rom etc. It just locks me into that data/media folder and my root browser or solid explorer won't let me write to that directory. I'm hating this device more and more....
Nosferatu. said:
okay. Well now CWM won't let me look through the entire device to flash a new update/rom etc. It just locks me into that data/media folder and my root browser or solid explorer won't let me write to that directory. I'm hating this device more and more....
Click to expand...
Click to collapse
you should use twrp recovery. it has more functuallity and just works right. easiest way is to download the goo manager app(free)press the menu button, press install open recovery script, press yes
simms22 said:
you should use twrp recovery. it has more functuallity and just works right. easiest way is to download the goo manager app(free)press the menu button, press install open recovery script, press yes
Click to expand...
Click to collapse
okay I'll look into it. On my Android phones I've always used CWM. Guess it's not as good on tablets...
Hate to ask so many noob questions (I'm pretty good when it comes to my phone) but how to I remove CWM and install TWRP?
Nosferatu. said:
okay I'll look into it. On my Android phones I've always used CWM. Guess it's not as good on tablets...
Hate to ask so many noob questions (I'm pretty good when it comes to my phone) but how to I remove CWM and install TWRP?
Click to expand...
Click to collapse
just install it the way i wrote above, or you can flash it via fastboot.
okay I'll do that later. Do I have to remove CWM or will they co-exist?
Nosferatu. said:
okay I'll do that later. Do I have to remove CWM or will they co-exist?
Click to expand...
Click to collapse
they will coexist, but twrp wont restore a cwm backup. id suggest you make a fresh backup if you go to twrp.