As title suggests I can't copy my nandroid backup folder contents from TWRP to my PC. Seems to be just the large data and system files that are around 1.3 gig each.
in windows 7 it never copied, no error. in windows 8 I receive an 'unspecified error' and it just stops.
I can copy other large files back and forth but just not these from my backup.
Any ideas?
Sent from my HTC One using Tapatalk 2
I have the same problem with my Galaxy Nexus... waiting for a solution .
terega said:
I have the same problem with my Galaxy Nexus... waiting for a solution .
Click to expand...
Click to collapse
Edit - Feature of TWRP 2.6. Encryption and permissions.
Currently only way to backup contents is to change permissions of the Backup folder contents, or boot phone back into recovery and do an an ADB pull.
I did ADB pull and that went fine.
gustav30 said:
Edit - Feature of TWRP 2.6. Encryption and permissions.
Currently only way to backup contents is to change permissions of the Backup folder contents, or boot phone back into recovery and do an an ADB pull.
I did ADB pull and that went fine.
Click to expand...
Click to collapse
Changing permissions didn't work for me at all... however, ADB pull did. Any other ideas to get this working again without having to use ADB pull?
This post in this thread is what worked for me to change permissions. Also more discussion about this in that thread.
http://forum.xda-developers.com/showthread.php?p=43453295
Sent from my HTC One using Tapatalk 4 Beta
gustav30 said:
This post in this thread is what worked for me to change permissions. Also more discussion about this in that thread.
http://forum.xda-developers.com/showthread.php?p=43453295
Sent from my HTC One using Tapatalk 4 Beta
Click to expand...
Click to collapse
Sweet! That worked. Thanks! I was trying 644, not 777.
Sorry to kind of hijack this thread, but I am having issues with trying to copy the backups using ADB. Whenever I am booted into TWRP my computer will not recognize the device as an ADB device. Running Windows 8 with the SDK/Google USB Drivers installed.
Permissions do not change via shell. ADB Pull permission denied. Mounted get "unspecified error". Cannot change permissions with Root Explorer.
I am rooted, ADB working, device connected, TF700t
Any help to backup my backup would be appreciated.
(This is what I did:
C:\Users\Chad\Desktop\Android SDK\sdk\platform-tools>adb shell
[email protected]:/ $ su
su
[email protected]:/ # chmod -R 777 /sdcard/TWRP
chmod -R 777 /sdcard/TWRP
[email protected]:/ # exit
exit
[email protected]:/ $ exit
exit
C:\Users\Chad\Desktop\Android SDK\sdk\platform-tools>adb pull /sdcard/TWRP/BACKU
PS c:/Users/Chad/Desktop
pull: building file list...
pull: /sdcard/TWRP/BACKUPS/015d29955a581616/first071613/recovery.log -> c:/Users
/Chad/Desktop/015d29955a581616/first071613/recovery.log
pull: /sdcard/TWRP/BACKUPS/015d29955a581616/first071613/boot.emmc.win.md5 -> c:/
Users/Chad/Desktop/015d29955a581616/first071613/boot.emmc.win.md5
pull: /sdcard/TWRP/BACKUPS/015d29955a581616/first071613/boot.emmc.win -> c:/User
s/Chad/Desktop/015d29955a581616/first071613/boot.emmc.win
pull: /sdcard/TWRP/BACKUPS/015d29955a581616/first071613/data.ext4.win.md5 -> c:/
Users/Chad/Desktop/015d29955a581616/first071613/data.ext4.win.md5
pull: /sdcard/TWRP/BACKUPS/015d29955a581616/first071613/data.ext4.win -> c:/User
s/Chad/Desktop/015d29955a581616/first071613/data.ext4.win
failed to copy '/sdcard/TWRP/BACKUPS/015d29955a581616/first071613/data.ext4.win'
to 'c:/Users/Chad/Desktop/015d29955a581616/first071613/data.ext4.win': Permissi
on denied
pull: /sdcard/TWRP/BACKUPS/015d29955a581616/first071613/system.ext4.win.md5 -> c
:/Users/Chad/Desktop/015d29955a581616/first071613/system.ext4.win.md5
pull: /sdcard/TWRP/BACKUPS/015d29955a581616/first071613/system.ext4.win -> c:/Us
ers/Chad/Desktop/015d29955a581616/first071613/system.ext4.win
failed to copy '/sdcard/TWRP/BACKUPS/015d29955a581616/first071613/system.ext4.wi
n' to 'c:/Users/Chad/Desktop/015d29955a581616/first071613/system.ext4.win': Perm
ission denied
7 files pulled. 0 files skipped.
2233 KB/s (8538070 bytes in 3.732s)
gustav30 said:
This post in this thread is what worked for me to change permissions. Also more discussion about this in that thread.
http://forum.xda-developers.com/showthread.php?p=43453295
Sent from my HTC One using Tapatalk 4 Beta
Click to expand...
Click to collapse
thanks a million.
sundoulos said:
Permissions do not change via shell. ADB Pull permission denied. Mounted get "unspecified error". Cannot change permissions with Root Explorer.
I am rooted, ADB working, device connected, TF700t
Any help to backup my backup would be appreciated.
Click to expand...
Click to collapse
I had this same problem for a while on my Nexus 4. I found this thread and tried to figure out what I was doing wrong. Turns out the adb pull doesn't work with the device booted up normally, as most adb commands do! Once I went into recovery and used adb there, everything transferred over. Hope it helps.
I want to know I have same problem but I just move the folder and went I try to use I only have the boot backup, that mean I don't have my backup?
Removed.
Hi,
I started having this issue on my Nexus 4 but I can't remember if it was after 4.3 update. I could not copy the large files from the TWRP folder through windows explorer, wifi pro, Nexus Toolkit or any other method with the mobile turned on.
Permissions were already to 777 and still nothing.
For me the pull command with the mobile into recovery mode did the job.
Thanks
orangeyes said:
Hi,
I started having this issue on my Nexus 4 but I can't remember if it was after 4.3 update. I could not copy the large files from the TWRP folder through windows explorer, wifi pro, Nexus Toolkit or any other method with the mobile turned on.
Permissions were already to 777 and still nothing.
For me the pull command with the mobile into recovery mode did the job.
Thanks
Click to expand...
Click to collapse
For me it was TWRP ver. 2.6. that prevented me from a PC transfer. An adb pull resolved the issue. I believe changing permissions has the potential of opening a can of worms later on.
Yes indeed it must be the TWRP update for me as wel that caused the issuel because I updated the TWRP before going into 4.3.
pjc123 said:
For me it was TWRP ver. 2.6. that prevented me from a PC transfer. An adb pull resolved the issue. I believe changing permissions has the potential of opening a can of worms later on.
Click to expand...
Click to collapse
orangeyes said:
Hi,
I started having this issue on my Nexus 4 but I can't remember if it was after 4.3 update. I could not copy the large files from the TWRP folder through windows explorer, wifi pro, Nexus Toolkit or any other method with the mobile turned on.
Permissions were already to 777 and still nothing.
For me the pull command with the mobile into recovery mode did the job.
Thanks
Click to expand...
Click to collapse
Hi,
Could you please explain what an Adb pull is and how I can do it ? I've never done it before and need some help. I use a Rooted Nexus 4 (4.3), with the latest version of TWRP (flashed the recovery only today).
veeravar said:
Hi,
Could you please explain what an Adb pull is and how I can do it ? I've never done it before and need some help. I use a Rooted Nexus 4 (4.3), with the latest version of TWRP (flashed the recovery only today).
Click to expand...
Click to collapse
Hello,
Assuming that you are in the same folder with the adb.exe (can be found in the sdk or standalone online) and have the proper drivers installed:
1) Reboot phone into recovery.
2) COnnect it to your PC. A driver installation will take place if this is the first time.
3) Hold shift in the folder with the adb.exe and select "open command window here"
4) Type
Code:
adb pull /mnt/sdcard/TWRP C:\
You can continue after the C:\ if you want to copy the files elsewhere. Also fi you get error of the type that the target is not found propably your backups are saved in another directory. You can easily get the complete location to them by going into the advanced options of TWRP and the use the file manager to browse to your backups. You will see the target directory on top.
Edit: Sorry I did not include what adb is. here you go http://developer.android.com/tools/help/adb.html
I think that's all :good:
Hi,
Thank you for that tutorial. I tried using the code you mentioned. I need to move the TWRP folder on my sdcard to the platform-tools folder on the D:/ on my pc. I executed the following code (with cmd opened in the platform-tools folder):
adb pull /sdcard/ twrp
Only 24.6mb of files are being pulled into the said folder. Whereas the actual size of the TWRP folder is 1.5gb. The phone is booted into TWRP recovery.
Could you please explain why this is happening? and it would be great if you tell me the code to execute if i want to copy the TWRP folder to a folder called ANDROID in my D drive.
nope not working.....it shows this when i boot my phone into TWRP recovery and did an adb pull
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
zixian96 said:
nope not working.....it shows this when i boot my phone into TWRP recovery and did an adb pull
Click to expand...
Click to collapse
Connected from recovery:
adb pull /sdcard/TWRP/BACKUPS C:\
Then wait for it to finish.
Related
Hello,
i wish to create an update.zip to copy fonts from the zip into the system/fonts/ folder because i delete them and kept one font but it seems android doesn't boot with one font only need other fonts to be there (or atleast matching the names) to be able to boot.
adb push doesn't work giving me permission denied because /system is not mounted R/W (which i do using Super Manager for example)
i read other update.zip files and it seems i need to create CERT.SF and MANIFEST.MF files in META-INF , but it seems there are some SHA1-Digest: below each file (is this a md5checksum?) so i can't just replace file names and apply it
any ideas how can i do it without Wipe data/factory reset ? (and if factory reset is my last option would fonts be returned or factory reset doesn't get fonts back? i feel not)
Thanks
The app below will sign the zip and allow you to flash it. You just need to put the zip inside the folder and call it 'update.zip'
l0st.prophet said:
The app below will sign the zip and allow you to flash it. You just need to put the zip inside the folder and call it 'update.zip'
Click to expand...
Click to collapse
Thank you , any chance there i a Linux version out there? i'm using adb on ubuntu
and for CERT.SF and MANIFEST.MF i just create them manually based on any update.zip file i download earlier?
I'm on windows now and i've signed the file, when i try to apply it from recovery i get
E:signature verification filed
Installation aborted
what i'm missing?
attached my signed update.zip
it seems i had a folder update inside the zip
i have re-created one and signed it and still same error
attached the file
btw as i'm rooted and i used to su from adb shell and terminal emulator earier, any idea why su not working now?
$ su
[1] + Stopped (signal) su
$
[1] Segmentation fault su
$
is it because i'm on the HeRO logo boot screen ? it didnt get in yet?
btw for linux/ubuntu users who want to sign on linux you can use this:
Code:
java -jar signapk.jar testkey.x509.pem testkey.pk8 update.zip update_signed.zip
inside the Auto Sign folder
after signing on linux i get the following:
E: failed to read footer from / sdcard/update.zip (I/O error)
E:signature verification failed.
Installation aborted
First of all, please use the edit button, posting 6 times in a row is very hard to read, and is considered bumping your own thread which is a quick way to lose friends.
Secondly, the autoSign program creates a file called update_signed.zip which is the file you need to flash, the cert and manifest files are created by the process, you don't need to touch them. I have attached a signed version of your zip
I resigned it for you, see attachment. I use "androsign" I found here somewhere on XDA, maybe go look for it. It is a very easy tool edit: Too late
When you are in "adb shell" you should have SU rights already.
Otherwise there is an option in adb to switch to SU rights, just type in "adb help" of a howto.
First of all , sorry for the multiple posts
second i've tried both update-signed.zip and update_signed.zip and both of them gave me the same error
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
*P.S: sorry if i'm not allowed to put an image ill delete it
EDIT:
riemervdzee said:
When you are in "adb shell" you should have SU rights already.
Otherwise there is an option in adb to switch to SU rights, just type in "adb help" of a howto.
Click to expand...
Click to collapse
i tried to the help i didn't find how to set su in the right roots?
Have you flashed an alternative recovery at all? This one looks like the default one.
And look at the first error, it asks for a path in /cache/... Just get amon_ra recovery This way you can select which zip you want to flash (as long as they are in the root of the sd-card).
And from "adb help":
"adb root - restarts the adbd daemon with root permissions".
However seen you still have the original recovery, that probably won't work in recovery.
You said you rooted the device already right? maybe you can move the files with adb then when the ROM is trying to start, and after everything works get a real recovery where you can do something.
riemervdzee said:
Have you flashed an alternative recovery at all? This one looks like the default one.
And look at the first error, it asks for a path in /cache/... Just get amon_ra recovery This way you can select which zip you want to flash (as long as they are in the root of the sd-card).
And from "adb help":
"adb root - restarts the adbd daemon with root permissions".
However seen you still have the original recovery, that probably won't work in recovery.
You said you rooted the device already right? maybe you can move the files with adb then when the ROM is trying to start, and after everything works get a real recovery where you can do something.
Click to expand...
Click to collapse
yeah i tried the adb root already but getting "adbd cannot run as root in production builds"
yes i'm rooted and everything is fine
btw why deleting fonts prevents the phone from booting although there is one font there "not the default one"
what i want is to push the font files into the phone but getting the error i mentioned earlier that its not mounted as as R/W:
[email protected]:~/linux_adb_fastboot/hero_fonts$ for i in `cat list`; do adb push $i /system/fonts/$i ; done
failed to copy 'DroidSerif-Bold.ttf' to '/system/fonts/DroidSerif-Bold.ttf': Read-only file system
failed to copy 'DroidSerif-Regular.ttf' to '/system/fonts/DroidSerif-Regular.ttf': Read-only file system
failed to copy 'DroidSerif-Italic.ttf' to '/system/fonts/DroidSerif-Italic.ttf': Read-only file system
failed to copy 'DroidSansMono.ttf' to '/system/fonts/DroidSansMono.ttf': Read-only file system
failed to copy 'DroidSansFallback.ttf' to '/system/fonts/DroidSansFallback.ttf': Read-only file system
failed to copy 'DroidSerif-BoldItalic.ttf' to '/system/fonts/DroidSerif-BoldItalic.ttf': Read-only file system
failed to copy 'DroidSans-Bold.ttf' to '/system/fonts/DroidSans-Bold.ttf': Read-only file system
failed to copy 'Clockopia.ttf' to '/system/fonts/Clockopia.ttf': Read-only file system
failed to copy 'DroidSans.ttf' to '/system/fonts/DroidSans.ttf': Read-only file system
and yes adb remount doesn't work
[email protected]:~/linux_adb_fastboot/hero_fonts$ adb remount
remount failed: Operation not permitted
You have "rooted" your phone but you can't get adb root? That is contradictory
But since I'm in a good mood. Try to boot up the phone on your ROM, so not in recovery or bootloader. Then try to remount.
If remount is still failing, you don't have root.
Maybe you should also read your stuff a bit in before attempting anything. You are kinda screwing up your phone here.
Yes i'm sure i'm rooted i had universal root which i can root and unroot, and before deleting the fonts i used to do su and get root
also to confirm im rooted i used to use Market Access to access US and other markets to buy (since my country only has free apps not paid yet)
i didn't get the part of botting up the phone using my ROM ?
also a side question when booting the phone normally (i think this is what you meant about booting into the ROM?) and it stays on the HeRO logo as you can see i can access the adb shell etc.. so the phone is actually responding but not booting because of the fonts not there? or something else could be broken ?
Bashar . said:
Yes i'm sure i'm rooted i had universal root which i can root and unroot, and before deleting the fonts i used to do su and get root
also to confirm im rooted i used to use Market Access to access US and other markets to buy (since my country only has free apps not paid yet)
i didn't get the part of botting up the phone using my ROM ?
also a side question when booting the phone normally (i think this is what you meant about booting into the ROM?) and it stays on the HeRO logo as you can see i can access the adb shell etc.. so the phone is actually responding but not booting because of the fonts not there? or something else could be broken ?
Click to expand...
Click to collapse
Read "adb logcat" or in adb shell, use the linux command "dmesg" to see what is wrong.
And yes, with booting your ROM I mean the normal boot process. But probably android won't start as it can't find the fonts (they are essential).
And really... Read your stuff. You deleted fonts but didn't put any new there yet? You are asking for problems, while you ask us to solve it.
Then you come up with the plan to flash the new fonts, but you don't have a customized recovery.
riemervdzee said:
Read "adb logcat" or in adb shell, use the linux command "dmesg" to see what is wrong.
And yes, with booting your ROM I mean the normal boot process. But probably android won't start as it can't find the fonts (they are essential).
And really... Read your stuff. You deleted fonts but didn't put any new there yet? You are asking for problems, while you ask us to solve it.
Then you come up with the plan to flash the new fonts, but you don't have a customized recovery.
Click to expand...
Click to collapse
I did put one font there, but my mistake is not renaming it as the default font names that was there, i thought it would scan the fonts folder and use ANY font listed there
but seems not...
catlog shows im missing the fonts: http://dpaste.org/ADyJ/
dmesg output: http://dpaste.org/8IGw/
i never thought the recover it had won't let met flash the fonts
EDIT: i tried the mv command as linux user but my main problem is that its a read only system
[email protected]:~$ adb shell
$ cd system
$ cd fonts
$ ls
DroidSansArabic.ttf
$ mv
USAGE: mv <source...> <destination>
$ mv DroidSansArabic.ttf DroidSans.ttf
failed on 'DroidSansArabic.ttf' - Read-only file system
$
You can't do "adb remount" when starting normally? You have rooted the ROM, not the recovery (which refuses root access, as it is still the default one).
If everything fails, you can always do a RUU. (google "hero RUU"), this will reset everything as HTC wants it. Then you start from scratch again.
riemervdzee said:
You can't do "adb remount" when starting normally? You have rooted the ROM, not the recovery (which refuses root access, as it is still the default one).
If everything fails, you can always do a RUU. (google "hero RUU"), this will reset everything as HTC wants it. Then you start from scratch again.
Click to expand...
Click to collapse
yeah it seems thats my only option
I was hoping to learn by fixing, i'll flash it tomorrow then
now back to the question, why the update.zip that we were trying to sign is not flashable or signable ? what might be the reason? is it because i didn't root the recovery ?
i tried an stock Hero rom and still gives me invalid signature, i can't apply any rom at all now or what?
03.30.2011 -=*[ working on automation of backup/install of the Boot Animation... ]*=-
!!COMPLETED!! see bottom of OP
i made a few Boot Animations to go with my GingerBlur'd phone if anyone is interested in them. they're nothing fancy, just something different to look at.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
GingerBlur-bootanimation-1.zip
GingerBlur-bootanimation-2.zip
GingerBlur-bootanimation-3.zip
you will need to rename the respective GingerBlur-bootanimation-x.zip to bootanimation.zip.
original design was by ZeliardM for the Eris. i made some changes for GingerBlur.
Installation Instructions:
The script that's run on your phone WILL back up your existing /system/media/bootanimation.zip file ONE time and that's it. As long as the backup (/system/media/bootanimation.zipORG) exists from then on, it will simply overwrite the /system/media/bootanimation.zip file each time you run the install. this script should work for any of the Boot Animations that you get your hands on as long as there is a bootanimation.zip file in the same directory as the batch and script file (explanation(s) below). you can always revert back to your original bootanimation.zip, but you'll need to do so manually using adb to copy the /system/media/bootanimation.zipORG -> /system/media/bootanimation.zip
Download your Boot Animation of choice from the above links
Download the zip file (GB-BootAni.zip) below containing the install .bat and .sh file.
unzip the GB-BootAni.zip file you downloaded (should create you a GB-BootAni directory)
place your downloaded Boot Animation zip file in the above directory and either rename it bootanimation.zip or copy the file to bootanimation.zip
run the GB-BootAni.bat and the rest should take care of itself.
Download GB-BootAni.zip (installation helper for the GingerBlur Boot Animations)
md5sum: f20838c2d293f181f1f2d5650f6e8f83
i welcome any and all feedback...good, bad or indifferent.
Looks good! I'm loving all the boot screen's that have come out so far, great work!
Looks nice, and how would you go about installing this to your phone? Asking b/c I've never done this before.
crea78 said:
Looks nice, and how would you go about installing this to your phone? Asking b/c I've never done this before.
Click to expand...
Click to collapse
i'll try to post a script to facilitate things, but basically:
copy/rename the .zip file to bootanimation.zip
adb push bootanimation.zip /data/local/tmp
adb shell
<the above is done from your windows/linux machine>
<here down is done on your phone>
$ su
# cp /data/local/tmp/bootanimation.zip /system/media
# rm /data/local/tmp/bootanimation.zip (optional)
# reboot
...sit back and watch the magic happen.
itsonlym3 said:
i'll try to post a script to facilitate things, but basically:
copy/rename the .zip file to bootanimation.zip
adb push bootanimation.zip /data/local/tmp
adb shell
<the above is done from your windows/linux machine>
<here down is done on your phone>
$ su
# cp /data/local/tmp/bootanimation.zip /system/media
# rm /data/local/tmp/bootanimation.zip (optional)
# reboot
...sit back and watch the magic happen.
Click to expand...
Click to collapse
Thanks, and a script would be much easier to use
Can I do this on a stock atrix 4g
Always_Jonezen said:
Can I do this on a stock atrix 4g
Click to expand...
Click to collapse
you have to have "root" access in order to write to /system/media/
itsonlym3, I'm trying to do this manually via adb. First, does it matter where we put the bootanimation.zip because when I insert adb push bootanimation.zip /data/local/tmp in the command terminal, I get a "cannot start bootanimation.zip: No such file or directory"
Not sure what I'm doing wrong here...
itsonlym3 said:
you have to have "root" access in order to write to /system/media/
Click to expand...
Click to collapse
that sucks i lost my root with that update to 1.5.7
Always_Jonezen said:
that sucks i lost my root with that update to 1.5.7
Click to expand...
Click to collapse
you know you can get it back, right? you'll have to revert back and what not, but you can still have your update and get your root back.
check out this [SCRIPT] Root for 4.1.57 (RELEASED!) (requires 4.1.26 rooted) thread.
crea78 said:
itsonlym3, I'm trying to do this manually via adb. First, does it matter where we put the bootanimation.zip because when I insert adb push bootanimation.zip /data/local/tmp in the command terminal, I get a "cannot start bootanimation.zip: No such file or directory"
Not sure what I'm doing wrong here...
Click to expand...
Click to collapse
you need to issue the push (adb push) from your Winxx or Linux machine. if you've got adb in your path (which you probably do), then go into the directory where you downloaded the new bootanimation.zip and issue:
adb push bootanimation.zip /data/local/tmp/
that better?
i'm kind of assuming there's a /data/local/tmp. hopefully i'm correct in my assumption....?
sorry, i'm working on a script to automate this, just been busy. :/
also, you should probably back up your existing bootanimation.zip file before overwriting it if you'd like to keep it. PM me and i'll walk you through it if you need help. i'll add manual instructions to the OP once i finish up the automated script.
itsonlym3 said:
you need to issue the push (adb push) from your Winxx or Linux machine. if you've got adb in your path (which you probably do), then go into the directory where you downloaded the new bootanimation.zip and issue:
adb push bootanimation.zip /data/local/tmp/
that better?
i'm kind of assuming there's a /data/local/tmp. hopefully i'm correct in my assumption....?
sorry, i'm working on a script to automate this, just been busy. :/
also, you should probably back up your existing bootanimation.zip file before overwriting it if you'd like to keep it. PM me and i'll walk you through it if you need help. i'll add manual instructions to the OP once i finish up the automated script.
Click to expand...
Click to collapse
That clears things up. I'm patient on you making a script, and good point on making a backup.
added installer and its usage to OP.
itsonlym3 said:
added installer and its usage to OP.
Click to expand...
Click to collapse
Even while using the script, the installer failed because of the data/local/temp not being found. Not sure how to find the path in order to see if bootanimation.zip is located in there.
Edit: when I type in %temp% in the start - search, it pops up my local temp files, but there is nothing in that folder?? I'm using Chrome as a browser if that makes a difference.
crea78 said:
Even while using the script, the installer failed because of the data/local/temp not being found. Not sure how to find the path in order to see if bootanimation.zip is located in there.
Edit: when I type in %temp% in the start - search, it pops up my local temp files, but there is nothing in that folder?? I'm using Chrome as a browser if that makes a difference.
Click to expand...
Click to collapse
/data/local/tmp is a path on your phone.
you should take whichever Boot Animation file you would like to use, copy it to the directory where you unzipped the installer and name it: bootanimation.zip
then while in that directory, you should run GB-BootAni.bat file and it should do the rest for you.
first off, when you get to a command line on your PC and type:
adb devices
does it return return/display something like this:
List of devices attached
TB30607H83 device
Stupid me!! I named the zip as bootanimation.zip so it read "bootanimation.zip.zip" so that is why it never worked. The new bootanimation works perfectly after I figured out my error
Stupid me!! I named the zip as bootanimation.zip so it read "bootanimation.zip.zip" so that is why it never worked. The new bootanimation works perfectly after I figured out my error
Click to expand...
Click to collapse
glad u figured it out and got it installed!
Thanks for the update
Sent from my MB860 using XDA Premium App
where do you put the script folder to run it? im having no luck getting it to take
Spaztazim said:
where do you put the script folder to run it? im having no luck getting it to take
Click to expand...
Click to collapse
you should be able to put it anywhere on your machine, as long as you have adb.exe in your path somewhere. i didn't add it to the zip file, but i suppose i could.
is that what you were asking?
Yep didn't do the adb part, I got creative and made my own animation by combining the peking droid and honeycomb takeover then figured out how to install it manually
Sent from my Atrix 3g
This script will run on Windows, Linux and Mac. No longer do you have to worry about having adb in your path, as i have included the binaries for all the operating systems.
The Linux and Mac script will automatically detect what O/S your using and use the correct binary.
You should be all set right out of the box, as long as you have the adb drivers installed for your device if you are in Windows. Linux/Mac users need not worry about the drivers.
COMING SOON.
overclocking capability and more
For Windows Users:
1. REBOOT YOUR PHONE BEFORE RUNNING
2. Extract the zip.
3. Make sure your drivers are installed.
Youtube Video from a user
http://www.youtube.com/watch?v=ZcWqeYQjjk0
older version of the script but same principal
4. Run Root.bat
5. Select your device
6. Hit #1
7. Profit!!!
Drivers For Windows:
Evo3D 32-bit Windows drivers:
Download HERE
Evo3D 64-bit Windows drivers:
Download HERE X64
For Linux/Mac Users:
1. REBOOT YOUR PHONE BEFORE RUNNING
2. Extract the zip.
3. Enter the directory.
4. Set the script permissions to allow it to execute.
Code:
chmod +x root
5. Plug in your device.
6. Run the script.
Code:
./root
7. Select your device.
8. Select #1
9. Profit!
Notes:
After the script starts all you have to do is choose option #1
The script remounts the file system R/W by itself. The other options are just there for convenience if you were to need to remount for hackery. sorry for the confusion.
All files are included including Fre3vo, su, busybox and superuser.apk
I get absolutely no superuser force closes with this. Titanium backup works perfectly. This is also the newest version of the superuser beta.
I have tested these scripts on my phone 10x each, 20 reboots if your counting If you are having problems REBOOT the phone to wipe all the changes you may have made with other scripts/errors.
Also if you install the Terminal Emulator from the market and type "su" you will get a superuser pop up to allow permissions and you will get a root prompt in the Terminal.
Let me know how it works for you.
Changelog:
v2.5
[Linux/Mac] Auto-detect Os
[Linux/Mac] Linux and Mac binaries now included so no more adb having to be in your PATH
v2.4
[Linux/Mac] Fix stupid error on my part in linux script
v2.3
[Linux/Mac]
[Windows]
Script Tweaks
New sticky temp root method (Installs to /vendor/bin/)
v2.2
[Linux/Mac]
[Windows]
HTC Sensation Support!
v2.1
[Linux/Mac] script tweaks
[Windows] rewrote script & added tools
v2.0
[Linux/Mac] rewrote script & added tools
[Windows] SORRY WINDOWS USERS NEW SCRIPT ISNT DONE FOR WINDOWS YET
v1.1
[Windows] Added Windows .bat
v1.0
[Linux/Mac] Initial Release
[Windows] Release SOON!
Download it here
http://dl.dropbox.com/u/11406774/Jeremy_Fre3vo2.5.zip
------Linux
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
------Windows
Dam sweeeet
Can someone make one for a win XP setup
I plan on making a .bat soon but if someone that knows what they are doing wants to try to convert it over for me ill update the op. I use my only windows computer to watch netflix on my tv. LOL
Pew Pew
I got Linux but how do I run this one tho?
Sent From My "Desperate For Root" 3VO...
You Sir are Amazing. Thank You. (Moves my own script into trash =) )
Eagerly awaiting a .bat file for this.
I *THINK* this should work for Window users... I made it really quick like and haven't even tested it myself..
Put this in the SDK folder "platform-tools" and run it as Admin. Make sure you extract all of the files to the root directory of the platform-tools folder and it should work.
platform-tools > root.bat
platform-tools > bin
platform-tools > apk
That should be your folder structure.
Let me know if it works
I got a mac, but from reading the OP it says I need ADB in my path? Not sure exactly what that means...
Stericson said:
I *THINK* this should work for Window users... I made it really quick like and haven't even tested it myself..
Put this in the SDK folder "platform-tools" and run it as Admin. Make sure you extract all of the files to the root directory of the platform-tools folder and it should work.
platform-tools > root.bat
platform-tools > bin
platform-tools > apk
That should be your folder structure.
Let me know if it works
Click to expand...
Click to collapse
Testing now.. ill edit once it (hopefully) completes
EDIT:
steps one thru 3 work great...
cant seem to 4 to work... any ideas?
**************
Your choices:
**************
(1) Set PATH variable for SDK platform-tools directory
(2) List devices found by adb
(3) Temp Root your Evo3d or Sensation with Fre3vo
(4) Install su, Superuser.apk and busybox
(5) Mount /system as R/W
(6) Mount /system as R/O
(7) Check mount points
(8) ADB Shell
(9) Exit
Type choice number: 4
********** su, Superuser.apk and busybox ***********
---------------------------------------------------------
Mounting /system as R/W
mount: Read-only file system
Done!!
---------------------------------------------------------
Installing su and busybox
failed to copy 'bin/su' to '/system/bin//su': Read-only file system
Unable to chmod /system/bin/su: Read-only file system
link failed File exists
failed to copy 'bin/busybox' to '/system/bin//busybox': Read-only file system
Unable to chmod /system/bin/busybox: Read-only file system
[1] Segmentation fault busybox --instal...
Done!!
---------------------------------------------------------
Installing Superuser
failed to copy 'apk/Superuser.apk' to '/system/app//Superuser.apk': Read-only fi
le system
Done!!
---------------------------------------------------------
Installing user and group
cannot create /system/etc/passwd: read-only file system
cannot create /system/etc/group: read-only file system
Unable to chmod /system/etc/passwd: No such file or directory
Unable to chmod /system/etc/group: No such file or directory
Done!!
---------------------------------------------------------
Complete, Press ENTER to return back to the main menu
Click to expand...
Click to collapse
Not sure what I'm doing wrong, copied all the folder elements into c:/android-sdk-windows/platform-tools, ran root.bat, pressed 3, waited until process finished, then pressed 4, installation says Okay. I see SU.apk installed on my phone but whenver I open up any rooted apps, it says cannot find root.
EDIT: this is through the windows version of the script.
Hmmm... I just tried it and it worked for me first go....using adb shell, do you have root?
Stericson said:
Hmmm... I just tried it and it worked for me first go....using adb shell, do you have root?
Click to expand...
Click to collapse
I'm retrying, let me test again after reboot.
fowenati said:
I got a mac, but from reading the OP it says I need ADB in my path? Not sure exactly what that means...
Click to expand...
Click to collapse
here is the mac binary for adb.
what you have to do is copy it into the /usr/bin/ folder.
Code:
sudo cp adb /usr/bin/
you need to make sure you are in the directory that adb is in when you execute that.
spunks3 said:
Testing now.. ill edit once it (hopefully) completes
EDIT:
steps one thru 3 work great...
cant seem to 4 to work... any ideas?
Click to expand...
Click to collapse
try using step 5 first then step 4?
EDIT: Well you shouldn't have to do that...try running step 3 again and show us the output?
Stericson said:
try using step 5 first then step 4?
EDIT: Well you shouldn't have to do that...try running step 3 again and show us the output?
Click to expand...
Click to collapse
my first time 3 worked okay i believe.
when i adb shell i get #
rebooting and trying again
This is my setup. Fresh reboot, fresh file extraction (directly from your .zip into platform-tools). Failed.
http://i642.photobucket.com/albums/uu150/Deflectant/Cropped.png
This picture is cropped, much easier to read.
EDIT: root.bat is in c:/android-sdk-windows/, I cropped it out of the picture though.
SuperUser keeps crashing for me....that might be the problem...
Thanks J.eremy. You asked to let you know how it went in your OP, so I'm reporting back. It worked excellent and quick, as advertised. Couldn't have been simpler, thanks. I've had it running for about an hour now, and have had no super user FC. How long have you had this lasting so far? Prior to this, I would only be able to go about a half hour or so before i got FC on super user, and would have to start over again. Is something different here? It seems to be sticking far longer...at least so far.
k2buckley said:
Thanks J.eremy. You asked to let you know how it went in your OP, so I'm reporting back. It worked excellent and quick, as advertised. Couldn't have been simpler, thanks. I've had it running for about an hour now, and have had no super user FC. How long have you had this lasting so far? Prior to this, I would only be able to go about a half hour or so before i got FC on SU, and would have to start over again. Is something different here? It seems to be sticking far longer...at least so far.
Click to expand...
Click to collapse
Your welcome
it lasts me until reboot every time normally, im pretty sure the main problem with some other scripts are they are not setting the permissions right and not modifying the passwd and group files correctly.
no f/c on my end either
spunks3 said:
my first time 3 worked okay i believe.
when i adb shell i get #
rebooting and trying again
Click to expand...
Click to collapse
yea Stericson is right, looks like the batch file isn't auto mounting the /system as R/W.
gonna go take a look at it now
Overstew said:
This is my setup. Fresh reboot, fresh file extraction (directly from your .zip into platform-tools). Failed.
http://i642.photobucket.com/albums/uu150/Deflectant/Cropped.png
This picture is cropped, much easier to read.
Click to expand...
Click to collapse
interesting...your picture shows it cannot find /bin/fre3vo
either it cant find the folder, or it cant find the file....
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Everytime after i turn off my wifi connection, i will have this 'dumpstate_sys_WIFI_OFF_20134...error.log.txt' log in my data folder..i wonder why this log appear and how to prevent it from automatically arise?? It can be delete with root explorer but i just wanna know is there any way to ultimately stop this log from happening.tq
Sent from my GT-I9100G
Sent from my GT-I9100G
rascal123 said:
Sent from my GT-I9100G
Click to expand...
Click to collapse
I also got this error file, and today I notice my phone keep hanging when turning on the wifi.
same for me with Stock LB1 rooted
The problem is if we not delete them..they will consume a lot of space..eating our internal memory..
Sent from my GT-I9100G
i am experiencing this too, even up to 1gb space is consumed T_T
it is like some kind of debug function is still enabled in LB1 firmware, maybe the samsung dev forgot to disable it
Sent from my GT-I9100G using Tapatalk
I also got this on superRomv3. when i flashed stock xxla1, the problem disappear...
Is it bcos of rom or kernel?anyone knows??
Sent from my GT-I9100G using Tapatalk 2 Beta-6
fauzi_91 said:
Is it bcos of rom or kernel?anyone knows??
Sent from my GT-I9100G using Tapatalk 2 Beta-6
Click to expand...
Click to collapse
i think it's the base of LB1 Roms ...
I've written this in another thread, so I figure I'll just repost this here for everyone's reference.
There's a workaround for this problem. Just remove the execute permission from /system/bin/dumpstate so the error log is not generated. There's a few ways you can do this:
Using ADB. Just type in the computer command prompt with the phone connected via USB. Of course, you need USB debugging enabled and have the android SDK installed on the computer.
Code:
adb shell chmod a-x /system/bin/dumpstate
Using Terminal Emulator on the phone. Just type the following commands:
Code:
$ su
# chmod a-x /system/bin/dumpstate
Using a root enabled file explorer on the phone such as Root Explorer or ES File Explorer. Browse to /system/bin/, find dumpstate, tap-hold to open the properties and remove all the Execute permissions.
aidfarh said:
I've written this in another thread, so I figure I'll just repost this here for everyone's reference.
There's a workaround for this problem. Just remove the execute permission from /system/bin/dumpstate so the error log is not generated.
Click to expand...
Click to collapse
Thanks a lot! It working perfectly, no more wifi error dump file, some more it seems fix my hanging issue as well, previously I keep facing phone hanging when switching between wifi on and off.
aidfarh said:
I've written this in another thread, so I figure I'll just repost this here for everyone's reference.
There's a workaround for this problem. Just remove the execute permission from /system/bin/dumpstate so the error log is not generated. There's a few ways you can do this:
Using ADB. Just type in the computer command prompt with the phone connected via USB. Of course, you need USB debugging enabled and have the android SDK installed on the computer.
Code:
adb shell chmod a-x /system/bin/dumpstate
Using Terminal Emulator on the phone. Just type the following commands:
Code:
$ su
# chmod a-x /system/bin/dumpstate
Using a root enabled file explorer on the phone such as Root Explorer or ES File Explorer. Browse to /system/bin/, find dumpstate, tap-hold to open the properties and remove all the Execute permissions.
Click to expand...
Click to collapse
thanks so much...it works..
c. Using a root enabled file explorer on the phone such as Root Explorer or ES File Explorer. Browse to /system/bin/, find dumpstate, tap-hold to open the properties and remove all the Execute permissions.
Click to expand...
Click to collapse
Thanks for the workaround..... this one really was eating up space.
help !
aidfarh said:
I've written this in another thread, so I figure I'll just repost this here for everyone's reference.
There's a workaround for this problem. Just remove the execute permission from /system/bin/dumpstate so the error log is not generated. There's a few ways you can do this:
Using ADB. Just type in the computer command prompt with the phone connected via USB. Of course, you need USB debugging enabled and have the android SDK installed on the computer.
Code:
adb shell chmod a-x /system/bin/dumpstate
Using Terminal Emulator on the phone. Just type the following commands:
Code:
$ su
# chmod a-x /system/bin/dumpstate
Using a root enabled file explorer on the phone such as Root Explorer or ES File Explorer. Browse to /system/bin/, find dumpstate, tap-hold to open the properties and remove all the Execute permissions.
Click to expand...
Click to collapse
Thanks for that. But whenever I try method b and c , what I get is that the dumpstate is a read only file, any idea what I should do ?
thanks
System memory continously decreasing
Hi all,
I'm having this same issue of system memory decreasing at a rapid rate. Had to do a factory reset once. Phone is non rooted. Checked the dump state file but it's really small in size. And i can't change executable permissions for that using es explorer without root. Any solution please?
zidhu said:
Thanks for that. But whenever I try method b and c , what I get is that the dumpstate is a read only file, any idea what I should do ?
thanks
Click to expand...
Click to collapse
Root. Sounds like you don't have root. You need root to do the above.
Geekeek said:
Hi all,
I'm having this same issue of system memory decreasing at a rapid rate. Had to do a factory reset once. Phone is non rooted. Checked the dump state file but it's really small in size. And i can't change executable permissions for that using es explorer without root. Any solution please?
Click to expand...
Click to collapse
Same as above. To change permissions on files in the system partition, you need root.
Thanks. What is causing the continual decrease? Can't root at least until the weekend but internal memory will be over in a day by the looks of it. :what:
Sent from my GT-I9100G using XDA
Geekeek said:
Thanks. What is causing the continual decrease? Can't root at least until the weekend but internal memory will be over in a day by the looks of it. :what:
Sent from my GT-I9100G using XDA
Click to expand...
Click to collapse
You said system memory in post 15, and internal memory above in post 17. Which is it?
In any case, I don't know what all you have installed and how you use your phone, so I can only guess what the cause would be.
If you for sure want it to stop, do a factory reset, (but you will lose all apps and user data) and carefully monitor what apps you re-install.
Sorry, it's obviously the system memory I am referring to. Already did a factory reset once and hardly installed anything later on. Still 1 gb used up.
Sent from my GT-I9100G using XDA
Geekeek said:
Sorry, it's obviously the system memory I am referring to. Already did a factory reset once and hardly installed anything later on. Still 1 gb used up.
Sent from my GT-I9100G using XDA
Click to expand...
Click to collapse
Not so obvious, really. Exactly how are you seeing the space remaining? Are you looking at Menu > Storage > Device memory?
Hi,
So I have a bootloader-unlocked and rooted (otherwise stock) AT&T HTC One with the latest TWRP.
When you generate a Nandroid with TWRP it creates ".ext4.win" files. I cannot find any possible way to get these files on to a Mac (iMac w/ OS X 10.8.3 Mountain Lion). I'm guessing it's because of the ".ext4" part -- so they are probably .ext4 Linux-style files that cannot be saved on the Mac's HFS+ file system.
I had hoped that I could just zip up my whole TWRP nandroid backup directory and then transfer the .zip to my Mac. No dice. The zip function of ES File Explorer errors on the ext4.win files. That I find a bit weird since the files are clearly ok on the phone's file system.
Does anyone out there use TWRP and a Mac and have a way of saving their TWRP Nandroids to Mac?
Google's "Android File Transfer" and "adb pull" would work for me on all other kinds of files but not these ".ext4.win" files. Similarly I could not get Bluetooth or Airdroid file transfer to work on those files either.
The only solution I could come up with was to use ES File Explorer to upload the nandroid files to Google Drive. That works but is really slow.
It would be great to save them to my Mac over USB or Wifi.
Any ideas?
thanks,
Matt
p.s.
I suppose this could be an argument to switch to CWM if its nandroid files are Mac-storable. I did find one post on here that seems to indicate this, but I like the touch-GUI of TWRP -- I'd like to continue using it if possible.
ShivaSmith said:
Hi,
So I have a bootloader-unlocked and rooted (otherwise stock) AT&T HTC One with the latest TWRP.
When you generate a Nandroid with TWRP it creates ".ext4.win" files. I cannot find any possible way to get these files on to a Mac (iMac w/ OS X 10.8.3 Mountain Lion). I'm guessing it's because of the ".ext4" part -- so they are probably .ext4 Linux-style files that cannot be saved on the Mac's HFS+ file system.
I had hoped that I could just zip up my whole TWRP nandroid backup directory and then transfer the .zip to my Mac. No dice. The zip function of ES File Explorer errors on the ext4.win files. That I find a bit weird since the files are clearly ok on the phone's file system.
Does anyone out there use TWRP and a Mac and have a way of saving their TWRP Nandroids to Mac?
Google's "Android File Transfer" and "adb pull" would work for me on all other kinds of files but not these ".ext4.win" files. Similarly I could not get Bluetooth or Airdroid file transfer to work on those files either.
The only solution I could come up with was to use ES File Explorer to upload the nandroid files to Google Drive. That works but is really slow.
It would be great to save them to my Mac over USB or Wifi.
Any ideas?
thanks,
Matt
p.s.
I suppose this could be an argument to switch to CWM if its nandroid files are Mac-storable. I did find one post on here that seems to indicate this, but I like the touch-GUI of TWRP -- I'd like to continue using it if possible.
Click to expand...
Click to collapse
This must be something to do with newer TWRP. I mistakenly told you it works fine for me, but in order to try to replicate your problem I made a twrp backup using 2.6.0.1 and like you said I can't copy it to my mac.
I never had issues with this before. I'd say use the older version of twrp if you could find it, but if you're running newer firmware from either the google ediiton conversion or 2.24 then touch won't work in twrp.
It's a shame because I prefer twrp's interface too.
maybe we should alert teamwin about this issue. or whoever built this version of twrp.
---------- Post added at 09:33 AM ---------- Previous post was at 09:28 AM ----------
Here's something odd, I plugged the flashdrive I always use via otg into my mac and am able to copy twrp backups from it to the Mac.
I bet it's an android file transfer problem.
it's an ongoing problem with the new twrp.
so either use OTG or switch to cwm
Hey Gunnyman,
Thanks so much for the independent confirmation of the issue! Much appreciated! Now I know I'm not crazy .
I'd also been speaking with the dev. of AFV (Android File Verifier) because that App also cannot compute .md5 sums on the ext4.win files from the latest TWRP. It appears to be some kind of file permission error:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
But yet I have root, and the files have read permission, so that's very weird. Ok, I just tried a command suggested by the AFV dev., and the output is very interesting:
Code:
$ adb shell ls -a -l /storage/sdcard0/TWRP/BACKUPS/**********/2013-07-18--13-37-53
-rw-rw-r-- root sdcard_rw 16777216 2013-07-18 14:37 boot.emmc.win
-rw-rw-r-- root sdcard_rw 48 2013-07-18 14:37 boot.emmc.win.md5
-rwSrwSr-- root sdcard_rw 55296 2013-07-18 14:37 cache.ext4.win
-rw-rw-r-- root sdcard_rw 49 2013-07-18 14:37 cache.ext4.win.md5
-rwSrwSr-- root sdcard_rw 1349282304 2013-07-18 14:39 data.ext4.win
-rw-rw-r-- root sdcard_rw 48 2013-07-18 14:39 data.ext4.win.md5
-rw-rw-r-- root sdcard_rw 16776192 2013-07-18 14:39 recovery.emmc.win
-rw-rw-r-- root sdcard_rw 52 2013-07-18 14:39 recovery.emmc.win.md5
-rw-rw-r-- root sdcard_rw 287235 2013-07-18 14:41 recovery.log
-rwSrwSr-- root sdcard_rw 1529744384 2013-07-18 14:41 system.ext4.win
-rw-rw-r-- root sdcard_rw 50 2013-07-18 14:41 system.ext4.win.md5
Look at those funky execute permissions... Regarding the "S" --
Wikipedia indicates: "S or T: setuid/setgid or sticky, but not executable".. not sure why that causes issues tho'.
Additionally, although I was able to transfer my first TWRP 2.6.0.1 nandroid backup to Google Drive using ES File Explorer, the 2nd nandroid I made last night would not transfer! It wouldn't work in either ES File Explorer or in the Google Drive App. That makes me wonder about the stability of the files being produced, but yet Ti Backup can open up the nandroids ok, so I don't think the files are corrupted... just seems like a permission issue
I will see if the OTG route will work for me -- that's a great idea which I hadn't tried yet.
Contacting TWRP sounds like a good idea to me, so I sent a message on their site, and pointed them to this thread, but haven't heard back from them yet. If there is any other better way to let them know -- or if we could PM them on XDA, we should. I'm not sure who to contact.
thanks,
Matt
gunnyman said:
it's an ongoing problem with the new twrp.
so either use OTG or switch to cwm
Click to expand...
Click to collapse
Hey Matt!
Thought I'd respond to you over here (I'll ping you on email later, too ).
I did a real quick search for the "S" bit (didn't know too much about it) and found this: http://www.unix.com/tips-tutorials/19060-unix-file-permissions.html:
The passwd file is writable only by root (Remember, root is special. It can write a file that has no write permissions set). The shadow file, which is where passwords are stored, cannot even be read by ordinary users. But joe wants to change his password. He can do that by running /usr/bin/passwd. Notice those r-s permissions. The passwd program has the suid and sgid bits set. This turns the x's into s's. In octal, it would be 6555. The passwd program is owned by root. When joe runs it, it does not run as "joe". Instead, it runs as it owner which is root. So the passwd program can change joe's password for him. The sgid bit works the same way, except it causes the passwd program to run with the group sys instead of joe's group. The suid and sgid do not get their own position in the ls. When the suid bit is set, ls displays a s rather than a x for the owner execute permission. What if the suid bit is set, but the owner execute bit is off? ls will display a capital S in the case. The sgid bit is displayed in a similiar manner, except that it interacts with the group execute permission. (The set uid concept was invented by Dennis Ritchie as he was developing Unix.)
Click to expand...
Click to collapse
I'm guessing that TWRP is setting the suid but not setting (or removing?) the x (execute permission) bit for some reason (pardon me for not being up-to-date on this issue w/TWRP) and this is leading to a read permission error in my AFV app.
Can you use/try another app to read this file (another file manager like ES File Explorer) and see if it can?
The currently available release of my app is not root-enabled (I have a version that I'm still testing), but this particular file should not require root access.
-SA
Hey SA,
Thanks for the "S" bit research info!
Gunnyman found some great info over in an HTC One International thread regarding PC's. This may make things work Mac. I'm about to try some of the chmod ideas from here:
http://forum.xda-developers.com/showthread.php?t=2357819
Matt
scary alien said:
Hey Matt!
Thought I'd respond to you over here (I'll ping you on email later, too ).
I did a real quick search for the "S" bit (didn't know too much about it) and found this: http://www.unix.com/tips-tutorials/19060-unix-file-permissions.html:
I'm guessing that TWRP is setting the suid but not setting (or removing?) the x (execute permission) bit for some reason (pardon me for not being up-to-date on this issue w/TWRP) and this is leading to a read permission error in my AFV app.
Can you use/try another app to read this file (another file manager like ES File Explorer) and see if it can?
The currently available release of my app is not root-enabled (I have a version that I'm still testing), but this particular file should not require root access.
-SA
Click to expand...
Click to collapse
I can confirm that TWRP 2.6.0.1 did actually restore my bootloader-unlocked, rooted (otherwise stock -- 4.2.1) AT&T HTC One properly...
I had just accidentally rebooted into safe mode and then later when I rebooted normally, my live wallpaper was gone (it was reset to the original wallpaper), and so were some home screen folders and icons. It seems like just booting into safe mode one time did that.
I'm still pretty new to Android -- I assumed that booting into safe mode would be like on a PC -- it shouldn't actually change your system. But apparently it did... which is good to know. Luckily I had a recent Nandroid, and the TWRP restore appears to have worked perfectly and my phone is back to exactly how it was... awesome.
So even tho' there are these weird permission things going on, the restore worked fine (as far as I can tell), which is great to know.
=============================================
And even better, the technique from the following post works on Mac's too!! Yay!! --
http://forum.xda-developers.com/showthread.php?p=43453295
Just did this in Terminal on my Mac:
Code:
$ adb shell
[email protected]:/ $ su
[email protected]:/ # chmod -R 777 /data/media/TWRP
[email protected]:/ # exit
[email protected]:/ $ exit
$ adb pull /storage/sdcard0/TWRP/BACKUPS/............/2013-07-18--13-37-53
pull: building file list...
pull: /storage/sdcard0/TWRP/BACKUPS/............/2013-07-18--13-37-53/recovery.log -> ./recovery.log
pull: /storage/sdcard0/TWRP/BACKUPS/............/2013-07-18--13-37-53/system.ext4.win.md5 -> ./system.ext4.win.md5
pull: /storage/sdcard0/TWRP/BACKUPS/............/2013-07-18--13-37-53/system.ext4.win -> ./system.ext4.win
pull: /storage/sdcard0/TWRP/BACKUPS/............/2013-07-18--13-37-53/recovery.emmc.win.md5 -> ./recovery.emmc.win.md5
pull: /storage/sdcard0/TWRP/BACKUPS/............/2013-07-18--13-37-53/recovery.emmc.win -> ./recovery.emmc.win
pull: /storage/sdcard0/TWRP/BACKUPS/............/2013-07-18--13-37-53/data.ext4.win.md5 -> ./data.ext4.win.md5
pull: /storage/sdcard0/TWRP/BACKUPS/............/2013-07-18--13-37-53/data.ext4.win -> ./data.ext4.win
pull: /storage/sdcard0/TWRP/BACKUPS/............/2013-07-18--13-37-53/cache.ext4.win.md5 -> ./cache.ext4.win.md5
pull: /storage/sdcard0/TWRP/BACKUPS/............/2013-07-18--13-37-53/cache.ext4.win -> ./cache.ext4.win
pull: /storage/sdcard0/TWRP/BACKUPS/............/2013-07-18--13-37-53/boot.emmc.win.md5 -> ./boot.emmc.win.md5
pull: /storage/sdcard0/TWRP/BACKUPS/............/2013-07-18--13-37-53/boot.emmc.win -> ./boot.emmc.win
11 files pulled. 0 files skipped.
2825 KB/s (2912922874 bytes in 1006.604s)
Nandroid safely stored off-phone on Mac! Mission accomplished .
Matt
I use Root Explorer to set the permissions to "rw_rw_r__" on all of the files in the backup folder, and then you can copy them off to your PC or Mac without any problems.
guyd said:
I use Root Explorer to set the permissions to "rw_rw_r__" on all of the files in the backup folder, and then you can copy them off to your PC or Mac without any problems.
Click to expand...
Click to collapse
Same issue with the protected backup files here! Unfortunately won't let me edit permissions, assume it's cause I'm running the stock Rom. I'm hesitant to flash a new one until I can copy the backup to my pc, otherwise my stock backup might be gone for good!
I actually prefer Cwm but for some reason can't get to work correctly on my One. Backups are made just fine but my file explorer can't seem to find them, so again can't copy to my pc! (they're definitely there as taking up valuable sdcard space!)
Neil
nstirton said:
Same issue with the protected backup files here! Unfortunately won't let me edit permissions, assume it's cause I'm running the stock Rom. I'm hesitant to flash a new one until I can copy the backup to my pc, otherwise my stock backup might be gone for good!
I actually prefer Cwm but for some reason can't get to work correctly on my One. Backups are made just fine but my file explorer can't seem to find them, so again can't copy to my pc! (they're definitely there as taking up valuable sdcard space!)
Click to expand...
Click to collapse
I was able to edit the permissions of the TWRP backup files on the Stock ROM just fine using Root Explorer!
Make sure you navigate to your backup folder via the /data/media/0 path!
You must have root to do it of course.
guyd said:
I was able to edit the permissions of the TWRP backup files on the Stock ROM just fine using Root Explorer!
Make sure you navigate to your backup folder via the /data/media/0 path!
You must have root to do it of course.
Click to expand...
Click to collapse
Thanks for the reply! Odd, I am rooted (confirmed by root checker from the market) but root explorer is telling me I'm not, and so can't amend the files. Am I missing something? Put me out of my misery!
EDIT: After a reset it appears to have worked! Thank you so much for your help!
TWRP needs to avoid puting the problematic S permission on .win files
gunnyman said:
it's an ongoing problem with the new twrp.
so either use OTG or switch to cwm
Click to expand...
Click to collapse
I'm having the same issues, I use the Rsync app to copy my nandroids to my linux box, but the rwSrwSr-- permissions on the win files result in "permission denied" when the app tries to read them. So I've been using the chmod utility of the TWRP 2.6.6.0 recovery itself to change the permissions to 0664, but it's highly annoying having to remember and do that after every backup.
Does anyone know if the TWRP folks have plans to fix the permissions issue and avoid putting the S bit ?
ShivaSmith said:
Hey Gunnyman,
Thanks so much for the independent confirmation of the issue! Much appreciated! Now I know I'm not crazy .
I'd also been speaking with the dev. of AFV (Android File Verifier) because that App also cannot compute .md5 sums on the ext4.win files from the latest TWRP. It appears to be some kind of file permission error:
. . .
Click to expand...
Click to collapse
I can confirm this. I was using Dropsync to auto-backup my backups. They wouldn't upload; shared the log and sync history with the Dropsync developer. He/she confirmed a permission issue; this was validated by moving the files that wouldn't upload to a different directory, where they started syncing correctly. I tried CWM and no such issue exists (even though it backs them up to data/media). I wish I had saw the quoted post below; sounds like the remedy (thanks guyd). I may try it when I get my patience back. I'm all about automation so I wouldn't want to manually do that every time I made a backup. I could probably get it done automatically with Tasker and some shell commands.
guyd said:
I use Root Explorer to set the permissions to "rw_rw_r__" on all of the files in the backup folder, and then you can copy them off to your PC or Mac without any problems.
Click to expand...
Click to collapse
nstirton said:
Same issue with the protected backup files here! Unfortunately won't let me edit permissions, assume it's cause I'm running the stock Rom. I'm hesitant to flash a new one until I can copy the backup to my pc, otherwise my stock backup might be gone for good!
I actually prefer Cwm but for some reason can't get to work correctly on my One. Backups are made just fine but my file explorer can't seem to find them, so again can't copy to my pc! (they're definitely there as taking up valuable sdcard space!)
Neil
Click to expand...
Click to collapse
As stated, it seems to backup to a different directory. For me, the backup folder defaults to data/media (and not data/media/0).
guyd said:
Make sure you navigate to your backup folder via the /data/media/0 path!
Click to expand...
Click to collapse
Thanks, that was the key for me!
I ran into the same problem, noticed the suid permission, but a chmod 0664 just wouldn't fix it. Turned out I cd'ed into TWRP's backup path via /sdcard/TWRP/... and not /data/media/0.
To summarize: in a terminal window I was able to
Code:
su
chmod -R 0664 /data/media/0/TWRP
(reproduced from memory)
and then adb pull the files via the command prompt from my Nexus 4 (same issue here as on the One) to my PC (same issue here as on a Mac).
Thanks again
Alex
As stated, it seems to backup to a different directory. For me, the backup folder defaults to data/media (and not data/media/0).
Click to expand...
Click to collapse
/data/media = Android 4.1.2
/data/media/0 = Android 4.2.2
If you are running 4.2.2 and TWRP still puts the backup in the wrong path, then delete the ".twrps" file in the twrp folder, and that should take care of it.
guyd said:
/data/media = Android 4.1.2
/data/media/0 = Android 4.2.2
If you are running 4.2.2 and TWRP still puts the backup in the wrong path, then delete the ".twrps" file in the twrp folder, and that should take care of it.
Click to expand...
Click to collapse
I was talking about CWM when I said that. TWRP backed up to the correct location but had the file permission issue.
Simba501 said:
I was talking about CWM when I said that. TWRP backed up to the correct location but had the file permission issue.
Click to expand...
Click to collapse
I wonder when they will fix the permissions issue, anyone know? I'll stay with 2.5.0.0 till then.
sordna said:
I wonder when they will fix the permissions issue, anyone know? I'll stay with 2.5.0.0 till then.
Click to expand...
Click to collapse
Hm. I didn't know it was fine on 2.5.0.0.
Sent from my HTC One
Simba501 said:
Hm. I didn't know it was fine on 2.5.0.0
Click to expand...
Click to collapse
If you have the latest touch pad drivers (2.24.401.1 firmware) you may run into touch problems with that older version of TWRP.
guyd said:
I use Root Explorer to set the permissions to "rw_rw_r__" on all of the files in the backup folder, and then you can copy them off to your PC or Mac without any problems.
Click to expand...
Click to collapse
It works! But do we need to revert the permissions of the files when restoring? Sorry, n00bs here. ;p