{
"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?
Related
When I installed Froyo on my N1, I found that streaming quality over Pandora suffered tremendously; low-quality was unbearable, and high-quality sounded worse than low-quality normally does. The change to StageFright from OpenCore is to blame here, while it improves HTTP streaming, it's AAC decoder doesn't decode LC-AAC streams properly.
To disable it temporarily, use
Code:
adb setprop media.stagefright.enable-player false
and restart any applications actively playing anything. To disable it permanently, pull build.prop from /system and change the value there. When you restart, it should be disabled; use adb getprop to verify.
Of course, the phone needs to be rooted for this to happen, as r/w access to /system is required.
THANK YOU!!!
I was so completely frustrated by this, as my phone is my primary source of music in my car via Rhapsody, that i had just rolled back to 2.1 yesterday.
I just verified your 'fix' and my sound is now perfect again!
Side note to everyone out there, setprop is a shell command, so you actual command to set the property is:
adb shell setprop media.stagefright.enable-player false
But there's no reason you shouldn't change the property in your build.prop file if you listen to streaming music regularly.
Again, THANK YOU for this fix!!
One other side note: this change also appears to fix the bluetooth "skipping" issue that appeared in 2.2 as well.
HUGE difference for the better
Thank you
cnunez1987 said:
When I installed Froyo on my N1, I found that streaming quality over Pandora suffered tremendously; low-quality was unbearable, and high-quality sounded worse than low-quality normally does. The change to StageFright from OpenCore is to blame here, while it improves HTTP streaming, it's AAC decoder doesn't decode LC-AAC streams properly.
To disable it temporarily, use
Code:
adb setprop media.stagefright.enable-player false
and restart any applications actively playing anything. To disable it permanently, pull build.prop from /system and change the value there. When you restart, it should be disabled; use adb getprop to verify.
Of course, the phone needs to be rooted for this to happen, as r/w access to /system is required.
Click to expand...
Click to collapse
Thanks for the info man
Just curious though, does anyone know the cause of why this is? Maybe a different decoder would have more success?
Thanks, sounds much better.
Now I have to remember to change my build.prop nearly everyday when I flash a new rom.
I'm rooted and pulled the build.prop file, but what program do I need to open the build.prop file and edit it?
PeRRiiN said:
I'm rooted and pulled the build.prop file, but what program do I need to open the build.prop file and edit it?
Click to expand...
Click to collapse
any text editor, notepad included, will work
Manacit said:
any text editor, notepad included, will work
Click to expand...
Click to collapse
Thank you, I'll try it out.
Thanks so much for the fix. Now I can listen to my tunes without some of the lyrics sounding like a Chimpmunks sing-a-long!
Thanks for this! Having some trouble pulling it off though I'm new to android.
I have root/unlocked, and have successfully used the adb pull command to pull the build.prop file. I've got the file edited, but cannot seem to get it to push back to the device.
Here is my problem if anyone would be willing to point me to the correct method.
{
"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"
}
venelar said:
Thanks for this! Having some trouble pulling it off though I'm new to android.
I have root/unlocked, and have successfully used the adb pull command to pull the build.prop file. I've got the file edited, but cannot seem to get it to push back to the device.
Click to expand...
Click to collapse
I believe you have to type this command before you push it
adb remount
I used pandora all day today, and I never heard anything wrong with it. :S
I can confirm that this works! Thanks!
I think it would be a good idea to include these instructions in the OP for those who don't know the commands.
Here's what I did. For those following these steps, the file locations on your computer may be slightly different.
On Windows:
1. Open Command Prompt
2. Type cd [location of tools folder in android sdk] Example cd C:\Documents and Settings\Administrator\My Documents\Nexus One\android-sdk-windows\tools
3. Type adb pull /system/build.prop c:\build.prop [This will place build.prop in your C Drive]
4. Using any text editor, open the file, make the necessary changes, then save.
5. Type adb remount
6. Type adb push c:\build.prop /system/build.prop
7. Type adb reboot
8. To verify that it is disabled, type adb shell getprop
After a few scrolls, you will see the following:
[media.stagefright.enable-player]: [false]
This means that everything was done correctly.
I'm pretty n00bish at this stuff. If something doesn't look right, let me know.
Thanks again for the fix!
venelar said:
Thanks for this! Having some trouble pulling it off though I'm new to android.
I have root/unlocked, and have successfully used the adb pull command to pull the build.prop file. I've got the file edited, but cannot seem to get it to push back to the device.
Here is my problem if anyone would be willing to point me to the correct method.
Click to expand...
Click to collapse
Which ROM are you using? And which boot image are you using. Just root access is not enough. The ro.secure value in default.prop should be set to 0 (zero) to allow remount with read-write permissions. Check the value of ro.secure in /default.prop. If it is 1 (one), you need to flash a new boot.img which has the value set as 0 (zero)
stealthopts17 said:
I can confirm that this works! Thanks!
I think it would be a good idea to include these instructions in the OP for those who don't know the commands.
Here's what I did. For those following these steps, the file locations on your computer may be slightly different.
On Windows:
1. Open Command Prompt
2. Type cd [location of tools folder in android sdk] Example cd C:\Documents and Settings\Administrator\My Documents\Nexus One\android-sdk-windows\tools
3. Type adb pull /system/build.prop c:\build.prop [This will place build.prop in your C Drive]
4. Using any text editor, open the file, make the necessary changes, then save.
5. Type adb remount
6. Type adb push c:\build.prop /system/build.prop
7. Type adb reboot
8. To verify that it is disabled, type adb shell getprop
After a few scrolls, you will see the following:
[media.stagefright.enable-player]: [false]
This means that everything was done correctly.
I'm pretty n00bish at this stuff. If something doesn't look right, let me know.
Thanks again for the fix!
Click to expand...
Click to collapse
awesome! although i have to say i don't really see (hear) a difference using pandora on cm6rc2
mixer5911 said:
awesome! although i have to say i don't really see (hear) a difference using pandora on cm6rc2
Click to expand...
Click to collapse
i've tried every froyo rom available, and sound quality in my car was horrible on all of them. this fix definitely makes listening to pandora enjoyable again.
thanks. completely stopped using pandora because it started to sound like I was trapped in tin can; and too lazy to swap out files constantly
Super gratefull for this! Worked like a charm.
Sent from my PC36100 using XDA App
Thanks so much.
Sounds so much better now.
What real life consequences does making this change this have? The OP mentions HTTP streaming, can you elaborate?
Thanks!
Noob question: canine just access the build.prop file with root explorer and edit it that way?
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....
Hi all,
There have been a couple of threads regarding ad-hoc not working for the NT but I decided to make a new one so it would be easily searchable. Please find below the fix for adhoc wifi. This fix should work for any OMAP4 device that uses version 0.6.10 of wpa_supplicant. The patch for this came from the following link (the diff file). I just applied it and recompiled for our device.
http://forum.xda-developers.com/showpost.php?p=7711198&postcount=6
Download the files attached below.
Turn off wifi.
To apply the fix do the following with adb (you will need root) or just use root explorer. Be sure to do a backup first (included in the adb script below).
Code:
$ adb pull /system/bin/wpa_supplicant wpa_supplicant.bak
$ adb shell
$ su
# mount -o remount,rw /dev/block/mmcblk0p5 /system
# chmod 777 /system/bin/wpa_supplicant
# exit
$ exit
$ adb push wpa_supplicant.omap4.adhocfix /system/bin/wpa_supplicant
$ adb shell
$ su
# chown root /system/bin/wpa_supplicant
# chmod 755 /system/bin/wpa_supplicant
# mount -o remount,ro /dev/block/mmcblk0p5 /system
# exit
$ exit
Turn wifi back on. You should be good to go.
I'm very happy to say that my wife will be driving everywhere now as I will be even more inseparable from this lovely little device from now on now that those of us with old tethers are MOBILE!
One thing I noticed using this patch. After installing it the first time you reboot you may need to go into the wireless settings and forget your networks to be able to reconnect.
worked perfectly thank you!
Sent from my BNTV250 using Tapatalk
Glad to hear it. I have been running it for about 2 days between AP and adhoc and haven't had problems yet.
zambien said:
Hi all,
There have been a couple of threads regarding ad-hoc not working for the NT but I decided to make a new one so it would be easily searchable. Please find below the fix for adhoc wifi. This fix should work for any OMAP4 device that uses version 0.6.10 of wpa_supplicant. The patch for this came from the following link (the diff file). I just applied it and recompiled for our device.
http://forum.xda-developers.com/showpost.php?p=7711198&postcount=6
Download the files attached below.
Turn off wifi.
To apply the fix do the following with adb (you will need root) or just use root explorer. Be sure to do a backup first (included in the adb script below).
Code:
$ adb pull /system/bin/wpa_supplicant wpa_supplicant.bak
$ adb shell
$ su
# mount -o remount,rw /dev/block/mmcblk0p5 /system
# chmod 777 /system/bin/wpa_supplicant
# exit
$ exit
$ adb push wpa_supplicant.omap4.adhocfix /system/bin/wpa_supplicant
$ adb shell
$ su
# chown root /system/bin/wpa_supplicant
# chmod 755 /system/bin/wpa_supplicant
# mount -o remount,ro /dev/block/mmcblk0p5 /system
# exit
$ exit
Turn wifi back on. You should be good to go.
I'm very happy to say that my wife will be driving everywhere now as I will be even more inseparable from this lovely little device from now on now that those of us with old tethers are MOBILE!
One thing I noticed using this patch. After installing it the first time you reboot you may need to go into the wireless settings and forget your networks to be able to reconnect.
Click to expand...
Click to collapse
Using ADB is problem on my machine. How do I do this through root explorer? I assume its much more than save a backup of a file and renaming the new?
Could I open terminal emulator on tablet and do this?
Also, after downloading the files, where would I save them to on my tablet?
Thanks
qngds said:
Using ADB is problem on my machine. How do I do this through root explorer? I assume its much more than save a backup of a file and renaming the new?
Could I open terminal emulator on tablet and do this?
Also, after downloading the files, where would I save them to on my tablet?
Thanks
Click to expand...
Click to collapse
It's pretty easy with root explorer.
1. Turn off wifi.
2. Open root explorer. Navigate to /system/bin.
3. Copy wpa_supplicant
4. Put is somewhere as a backup. Remember where you put it.
5. Get the wpa_supplicant from the zip file above. Unzip it and rename it to wpa_supplicant.
6. Take your new wpa_supplicant from your computer and put it on your nook via usb.
7 With Root Explorer copy the new wpa_supplicant and navigate to /system/bin
8. change to read write.
9. Paste wpa_supplicant into the directory /system/bin which you should be in.
10. Change owner to root.
11. Change permissions to:
read write execute
read execute
read execute
12. Turn wifi back on and test. You may find that you need to reboot your nook if it doesn't work at first.
To restore use the same steps starting at step 6 but with your backup.
whoops, double post
Thanks so much! I figured up til item 10, but it didnt occur to me to change permissions.
Thanks!! works perfectly to tether on my Iphone.
zambien said:
It's pretty easy with root explorer.
1. Turn off wifi.
2. Open root explorer. Navigate to /system/bin.
3. Copy wpa_supplicant
4. Put is somewhere as a backup. Remember where you put it.
5. Get the wpa_supplicant from the zip file above. Unzip it and rename it to wpa_supplicant.
6. Take your new wpa_supplicant from your computer and put it on your nook via usb.
7 With Root Explorer copy the new wpa_supplicant and navigate to /system/bin
8. change to read write.
9. Paste wpa_supplicant into the directory /system/bin which you should be in.
10. Change owner to root.
11. Change permissions to:
read write execute
read execute
read execute
12. Turn wifi back on and test. You may find that you need to reboot your nook if it doesn't work at first.
To restore use the same steps starting at step 6 but with your backup.
Click to expand...
Click to collapse
Thank you for the step by step for us novices.
As a side note, I used ES File Explorer, which shows up on the Android Marketplace on the nook (at least when rooted) to make the switch. I thought I'd add how to do this using this free app.
When using ES File Explorer. I already downloaded and unzipped the new wba supplicant file, and placed in a folder I could access on the device. I also made a copy of the original wba and placed it in an "original wba file" folder:
1. Open ES File Explorer
2. Select "Settings" at the bottom
3. Scroll down to "Home Directory" and change it to "/" (without the quotation marks)
4. Scroll down to "Root settings" and check both "Root Explorer" AND "Mount File System"
5. Backout of settings and try to navigate to "system" and "bin" (if you don't see it try restarting the ES File Explorer program)
From here ES File Explorer can change root files and permissions.
Now you can follow steps 1-9 listed above by zambien. Then...
Once you have replaced the original wpa_supplicant file with the new one under /system/ bin (don't forget the renaming; I used the "copy to" option) you have to:
1. Navigate back to /system/bin and find the new wpa_supplicant file
2. Long press the wpa_supplicant file and scroll down the pop-up menu to "Properties" (should be the last option)
3. Check the following boxes:
-User; read, write, execute
-Group; read, execute
-Other; read execute
I was able to connect to my HD2 through WiFi Tether (came with AmeriCanAndroid) over ad hoc, and confirmed internet access. I did not have to restart the device, but you might have to. I was able to switch between my house WiFi router, and the cell phone WiFi Tether without any issues.
**Update: Issue with reboot. After reboot it keeps trying to connect with adhoc network even though adhoc network it is off (phone off; shows full bars on NT). NT says my home network is out of range. At this point I:
1. Click on ad hoc network and select "Forget"
2. Wait for my home network to show up (sometimes I click on my home network and it shows up as connecting in background; don't know if it matters and just needs time to scan)
It is currently working except for this bug and seems to keep working after sleep. I think it is only a reboot issue. I will keep this configuration for a few days and see if the reboot issue changes.
**Update 2: It seems like the issue is more about waiting a few seconds for the nook to find the networks after sleep and after boots. With the original WiFi file, it was ready right away. Otherwise, works great!
Flawless first time. No need to reboot. Thanks for everything! This plus my galaxy nexus makes for an awesome combination!!!
Worked perfectly first time. Wifi hangs once in a while and I havev to turn it off and back on to kick it back in, but not really a big deal. I rooted my OG droid justs to get wifi to my nook. I love it.
Hi, I have installed this with my rooted NT 1.4.1. It appears to be working perfectly but if I switch WIFI off and power off my NT, it will reboot itself at the Nook screen and I have to force a factory reset to make it work.
@zambien Would you please look into this?
Thanks dude now I can fully use the wifi tether of my phone
Sent from my BNTV250 using xda premium
Change Owner Question...
When I go to change Owner to Root, there's another box below entitled 'Group' which is now showing sd card - I am still having trouble with the Nook recognizing the wifi from my droid x2 - is this something that should be changed to 'Root' as well?
Thank you!
Its because of this site and all the people on here that share their wealth of knowledge that I get to enjoy an optimal electronic experience and I greatly appreciate it! Thanks!
wpstewartjr0421 said:
When I go to change Owner to Root, there's another box below entitled 'Group' which is now showing sd card - I am still having trouble with the Nook recognizing the wifi from my droid x2 - is this something that should be changed to 'Root' as well?
Click to expand...
Click to collapse
where do we go to change the owner? I can change the permissions but no idea where to go to change the owner. Wondering if this is what is keeping me form getting this to work off of my X2 running CM7
rbellis said:
where do we go to change the owner? I can change the permissions but no idea where to go to change the owner. Wondering if this is what is keeping me form getting this to work off of my X2 running CM7
Click to expand...
Click to collapse
{
"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"
}
~ Veronica
lavero.burgos said:
~ Veronica
Click to expand...
Click to collapse
thank you but that really doesn't tell me anything. I changed the permissions but I still don't know how to change the owner to root. The 3 options below the permissions...what are those?
rbellis said:
thank you but that really doesn't tell me anything. I changed the permissions but I still don't know how to change the owner to root. The 3 options below the permissions...what are those?
Click to expand...
Click to collapse
To change owner simply long press the file a window will pop up scroll down(like when you go to change permissions) in the list and you will see change owner, another window will show now next to Owner pick 0 - root from the list. If you can't see change owner option then you need a recent version of root explorer.
~ Veronica
That did it! Went off w/o a hitch. I used a combination of root explorer and es file explorer. Es file ex to do the unzipping and copying, root ex to change owner and permissions. 1 reboot later and I'm sending this thx thru my phones tether! Thx a mil, guys!
The purpose of this thread is to make u familiar with the ADB (Android Debug Bridge)
It is a tool that lets u communicate with ur android device that is connected to ur pc.
In the first tutorial we shall learn some basics of adb and then advance to use pro commands in further tutorials.
Requirements
1. Adb link - http://dl.google.com/android/adt/adt-bundle-windows-x86-20130219.zip
2. Windows based pc ( yes we will use windows and not linux as i dun want to communicate anything that i havent tried by myself )
1. Download and extract the zip ADB in any drive , lets say C:
2. Go to C:/adb/sdk/platform-tools and u will something like
View attachment 1937059
{
"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"
}
3. Now press shift key + right click on mouse/keypad
http://forum.xda-developers.com/attachment.php?attachmentid=1936847&stc=1&d=1367732560
select open command window here
then type adb start-server
in order to ensure ur device is connected and recognized by adb , type adb devices , u will get something like this
View attachment 1940190
Now once your adb is setup up, lets play.....
GETTING LOGCAT THROUGH ADB
Easiest of all
just type
adb logcat
u will see entire log ur phone,
use ctrl+c to skip it
To get logcat in a file
type
adb logcat > logcat.txt
u will see a file logcat which will save ur phone's realtime process log.
TO GET A BUGREPORT
type adb bugreport
bt bt bt.. this will show info that wont b readable ..
so type
adb bugreport>result.txt
http://forum.xda-developers.com/attachment.php?attachmentid=1936973&d=1367737608
USING ADB WITH SUPERUSER PERMISSIONS
for this , u must be rooted
command
adb root
if it is success it will show something like
http://forum.xda-developers.com/attachment.php?attachmentid=1937056&stc=1&d=1367740210
INSTALLING AN APP VIA ADB
to install any app, make sure there is no space in the name of the apk...
and u should know its location,
command that u use is adb install
i have installed a game papertoss via this command, if u get success u will get something like this
View attachment 1936893
View attachment 1940189
COPYING A FILE VIA ADB
this is pretty easy
command u use is
adb pull
i have given a example by pulling the framework-res.apk from system/framework folder
View attachment 1940191
the file that u pull, u will see it in the platform -tools folder
PUSHING A FILE INTO YOUR PHONE
very similar to pull, bt this copies file from ur pc to ur android .
command u use is
adb push
For eg,
i have pushed the papertoss.apk file from C:\sanket\apps to sdcard/nimbuzz folder through the command
adb push C:\SANKET\apps\papertoss.apk /sdcard/nimbuzz
if u get success u will see something like this
http://forum.xda-developers.com/attachment.php?attachmentid=1937039&stc=1&d=1367739756
this command is very powerful and u can shift an entire video or movie folder via a single command anywhere on ur android
more commands added
thanks to @Guich
Code:
adb remount
This command remount the /system partition in read/write
Code:
adb usb
Restarts the adbd daemon listening on USB
Code:
adb shell
Run remote shell interactively
The command set shall b updated within few days.
Feel free to drop ur comments, corrections, commands.
All commands have been verified by me..
once i learn more, i will share more.
criticism is welcomed if its healthy
Thread material is not copied and will never be.
Thread will be updated with newer and complex commands soon with pics.
For developers, this is just a piece of cake which they can do with their eyes closed
i have made this specially for beginners ( like me )
PS - make sure the path name has no spaces
Also take care of the upper and lower case letters
Thanks @hiratafabio
op modified
new commands added
Reserved just in case
drsanket_xperia_u said:
Reserved just in case
Click to expand...
Click to collapse
Nice tut doctor g...
Sent from my MT27i using xda app-developers app
thanx a lot for this, keep it up&going !
For windows fan qtadb is much better I prefer Linux but used qtadb :beer:
Sent from my Xperia P using Tapatalk 2
Thanks mate
Sent from my LT22i using xda app-developers app
Thanks Bro, Great Tuto !!!:victory:
There are a lot of command
However, nothing
Interesting
Just what i was looking for! Thank you mate, great work!
Great tuto, well explained
Nice done, good explained
..::[ Pandemic ]...:: Face The Insanity With My Xperia P
.....:::: Jelly Bean Moonbreakers Member 4 Ever ::::....
Good and simple tutorial, thanks!
I have a question, though. Today I pushed a file from my PC to my device and it went OK, but when I tried to push another, all I got was the adb command list, as if I typed 'adb help'. I killed adb server, restarted it, no luck. Restarted the phone, no luck either. Tried 'adb device' to see if listed the device and it did, do it was connected.
What can it be?
hiratafabio said:
Good and simple tutorial, thanks!
I have a question, though. Today I pushed a file from my PC to my device and it went OK, but when I tried to push another, all I got was the adb command list, as if I typed 'adb help'. I killed adb server, restarted it, no luck. Restarted the phone, no luck either. Tried 'adb device' to see if listed the device and it did, do it was connected.
What can it be?
Click to expand...
Click to collapse
Try
Adb start-server
Adb remount
Sent from my ST25i using Tapatalk 2
drsanket_xperia_u said:
Try
Adb start-server
Adb remount
Sent from my ST25i using Tapatalk 2
Click to expand...
Click to collapse
Will try, thanks!
Edit: No luck, when giving 'adb remount', system says 'Operation not permitted'
hiratafabio said:
Will try, thanks!
Edit: No luck, when giving 'adb remount', system says 'Operation not permitted'
Click to expand...
Click to collapse
Okay when u open cmd
Make sure u run it as administrator
Secondly
Try adb root
Which rom are u using???
Edit _ just saw ur signature
drsanket_xperia_u said:
Okay when u open cmd
Make sure u run it as administrator
Secondly
Try adb root
Which rom are u using???
Edit _ just saw ur signature
Click to expand...
Click to collapse
My user has administrator rights, so I guess it's OK, right?
Funny thing is that works for only one push, if I try another, it doesn't work.
adb root gives 'adbd cannot run in production builds' error.
I guess I figured it out: filenames can't have spaces, is this correct? I tried pushing files that have spaces and it didn't work. When I renamed them, it worked like a charm. First I thought the problem was the path, that adb couldn't push files that were two or more levels inside folders, but some I was able to push, others I wasn't, but I also figured out that the path can't have spaces on it.
So that's it, no spaces in both path and filenames do the trick. I think it's a good tip to have in the OP, so people get aware of it if they face a problem just like I did.
Thanks again!
Lol buddy yes files names cant have spaces and also u need to take care of upper n lower case
Edit _ I will add this to op @hiratafabio.. Thanks
Awaiting part 2
Free to choose....
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.