Related
Now the thing is when I am at the home screen on my G1 i push "Enter" on the keyboard and then type "telnetd" and then push enter again it doesnt do anything. When I open up telnet client on my PC it wont connect with wifi on.
So I go to Terminal Emulator on G1 and plug in"
cd system
cd bin
telnetd
And then try and connect to telnet on PC and nothing happens.
So I then go to Telnet client on my G1 and go to connect to "localhost:23" and it says "Error while connecting to server: localhost/127.0.0.1:23 - Connection refused" the thing is that my local host for my wifi is not 127.0.0.1:23
And when I "netstat" from inside Terminal Emulator there is no address with port "23"
Any help would be greatly appreciated.
Download the app called Terminal Emulator from the market and use that instead of pterminal.
use the "su" command before trying to start telnetd.
Also make sure your wifi is up before your start telned.
mrboyd said:
Download the app called Terminal Emulator from the market and use that instead of pterminal.
use the "su" command before trying to start telnetd.
Also make sure your wifi is up before your start telned.
Click to expand...
Click to collapse
Thats what I have been using is Terminal Emulator but I dont think I can install Debian through Terminal Emulator. I would rather do it through the PC anyways.
I geta syntax error when using "su" in Term. Emu. because I believe I have installed the "su" mod to always allow.
adb shell
Presuming you're already running the proper modded RC30, you should be able to run 'adb shell' with USB debugging enabled on the phone and it connected to your machine. This should just drop you to a root shell.
SplasPood said:
Presuming you're already running the proper modded RC30, you should be able to run 'adb shell' with USB debugging enabled on the phone and it connected to your machine. This should just drop you to a root shell.
Click to expand...
Click to collapse
adb being a utility included in the android sdk (in tools/)
SplasPood said:
Presuming you're already running the proper modded RC30, you should be able to run 'adb shell' with USB debugging enabled on the phone and it connected to your machine. This should just drop you to a root shell.
Click to expand...
Click to collapse
SplasPood said:
adb being a utility included in the android sdk (in tools/)
Click to expand...
Click to collapse
I got all that but how do I actually use it (adb)? Every time I click on it a command window pops up and then goes away.
Ok I got adb shell to work now thanks guys
Can anyone add the "Usb Mass Storage" to the notification
I don't want to use MTP mode
I need to go to Setting->more->USB.... to change to "Usb Mass Storage" mode.
It's too trouble....
Widgetsoid2.x (google play market) is the way for what you need.
It seems that stock ROM have complete driver (i.e. supporting audio HW decoding as today, only AAC can be hardawrely decoded), hopefully when sources will be available all kind of sound will be hardwarely decoded.
Regarding USB Mass storage, you can use the attached APK (found it in this very thread a hundred pages back). Just launch it and when you tap on the Bugdroid, you can access your SDCards from your phone and computer at the same time. Don't forget to eject them before taping the Bugdroid again 
Sent from my GT-N7000 using xda premium
http://forum.xda-developers.com/showthread.php?p=26169987
Sent from my GT-N7000 using xda premium
aht said:
Can anyone add the "Usb Mass Storage" to the notification
I don't want to use MTP mode
I need to go to Setting->more->USB.... to change to "Usb Mass Storage" mode.
It's too trouble....
Click to expand...
Click to collapse
Or try actived usb mass storage with runing following script on any terminal emulator ( I use rom toolbox)
> su (Superuser will ask for privileges. Say yes). then enter
> setprop persist.sys.usb.config mass_storage,adb then enter (PAY ATTENTION AT COMMAS)
Then restart your device ...
By default (ICS), usb mass storage didn't active as removeable disk on PC.
chantik said:
Or try actived usb mass storage with runing following script on any terminal emulator ( I use rom toolbox)
> su (Superuser will ask for privileges. Say yes). then enter
> setprop persist.sys.usb.config mass_storage,adb then enter (PAY ATTENTION AT COMMAS)
Then restart your device ...
By default (ICS), usb mass storage didn't active as removeable disk on PC.
Click to expand...
Click to collapse
Thank you very much!
i will test it tonight!!
chantik said:
Or try actived usb mass storage with runing following script on any terminal emulator ( I use rom toolbox)
> su (Superuser will ask for privileges. Say yes). then enter
> setprop persist.sys.usb.config mass_storage,adb then enter (PAY ATTENTION AT COMMAS)
Then restart your device ...
By default (ICS), usb mass storage didn't active as removeable disk on PC.
Click to expand...
Click to collapse
Hi, may I ask if I want to stop/delete the script. What can I do?
olmg said:
Hi, may I ask if I want to stop/delete the script. What can I do?
Click to expand...
Click to collapse
find & delete in build.prop > persist.sys.usb.config=mass_storage,adb
chantik said:
find & delete in build.prop > persist.sys.usb.config=mass_storage,adb
Click to expand...
Click to collapse
Will this command work on GB? I want it to mount as a mass storage instead of MTP.
jovan123 said:
Will this command work on GB? I want it to mount as a mass storage instead of MTP.
Click to expand...
Click to collapse
Didn't test on GB ... maybe you can test by yourself.
chantik said:
Or try actived usb mass storage with runing following script on any terminal emulator ( I use rom toolbox)
> su (Superuser will ask for privileges. Say yes). then enter
> setprop persist.sys.usb.config mass_storage,adb then enter (PAY ATTENTION AT COMMAS)
Then restart your device ...
By default (ICS), usb mass storage didn't active as removeable disk on PC.
Click to expand...
Click to collapse
Thank you very much Man!!! This is exactly what I need to achieve!
Works well with my Galaxy Note GT-N7000 Stock ROM. I have Dual Mount SD.. also working well.
Now I can use my new ICS phone like my GB phone...
Thanks alot!!!
But only one imperfection with my Dual Mount SD is that.. I can only mount the internal SD. But when I choose to turn on USB Mass Starage from the pull downn notifications, I have both internal and external SD mounted, like my old GB ROM... no problem at all...
why i can't type anything on terminal emulator,i have android terminal emulator and better terminal emulator.
i want to try tweaking my build.prop but i need to type something first like this link said http://forum.xda-developers.com/showthread.php?t=1588439
any idea? my phone is SGM+ gt-s5570i rooted and using custom rom.
what do you mean by typing not able to write anything or not able to execute any command
can't type anything as in. after i open the terminal emulator and i press any letter it wont show up on the screen.
maybe the background color and text color are same
After launching Terminal Emulator ... Press Menu Key > Toggle Soft Keyboard.
in better terminal it only show > and ] when i tap the center of the screen. i already tried soft keyboard and still the same can't type anything.
it happened to me once too.just installed the latest terminal emulator from google play and it was done
the better terminal is already included on repencis v3.5 advance for sgm+ so i decided to dl the android terminal emulator and i still can't type anything.
Menu>preferences>input method>character based
Sent from Jelly Bean S5570
ok ill try it but not now because i hard bricked my phone T_T
I have your phone with repencis and better termimal emulator works good?
What is this problem
Sent from my galpop + GT-S5570I
Galaxy4Peeps said:
I have your phone with repencis and better termimal emulator works good?
What is this problem
Sent from my galpop + GT-S5570I
Click to expand...
Click to collapse
i already said that i can't type anything except when i tap the center of the screen it type ] or > only.
Logcat. Also try terminal emulator in ROM toolbox.
Sent from my GT-I9300 using xda app-developers app
U wud need these 2 things in order 2 work on terminal emulator
"Hacker's Keyboard IME" n "Busy Box" in order to get the most out of this program
:silly:
ohh i need hacker's keyboard IME. uhm about busy box i think when i root my phone using universal root it already has busy box or when i install repencis v3.5 advance its already has busy box.
mickeyzkun said:
why i can't type anything on terminal emulator,i have android terminal emulator and better terminal emulator.
i want to try tweaking my build.prop but i need to type something first like this link said http://forum.xda-developers.com/showthread.php?t=1588439
any idea? my phone is SGM+ gt-s5570i rooted and using custom rom.
Click to expand...
Click to collapse
change set up input methods from samsung keypad to Swype
Here's the solution
mickeyzkun said:
why i can't type anything on terminal emulator,i have android terminal emulator and better terminal emulator.
i want to try tweaking my build.prop but i need to type something first like this link said http://forum.xda-developers.com/showthread.php?t=1588439
any idea? my phone is SGM+ gt-s5570i rooted and using custom rom.
Click to expand...
Click to collapse
Tap menu, Preferences, then input method. Then choose your choice. Hoped it helped
Hello,
I had the same problems with the official Terminal Emulator app. (on android-x86 v2.2 emulated with VirtualBox 6.1 on Mac Os)
Another terminal emulator app from google play store does not help.
Preferences in VirtualBox about "input method" also does not help.
SOLUTION:
Inside the loaded virtual Android -> Settings -> Language and Keyboard Settings :
Disable - LIME keyboard.
Set language to default - English (US)
Then open "Android keyboard settings" and disable all extra features:
Vibrate on keypress
Sound on keypress
Auto-capitalization
Quick fixes
Show suggestions
Save settings (or just close).
Close the running Terminal Emulator app.
Start the Terminal app again and it works!
You can type everything you need with your normal keyboard.
Also you can pass some long command string from your host machine to virtual Android with a command like this:
VBoxManage controlvm YOUR_VM_NAME keyboardputstring "dir c:\\"
I have found it here:
Input -> Keyboard -> "Paste as text (send characters)" - Page 2 - virtualbox.org
Stanislav
Hey guys,
I'm just trying to port a Rom...
I changed some settings and it installs clearly now, but it has a bootloop...
I'm trying to port the paranoid android rom from HTC One X, I think it's V3.10...
I just googled and searched around and I know that I should get a log via ADB...
The PC finds my device, in device manager it is in "portable devices" as "P880", but doesn't show it in "Computer"... There is just my HDD and my cd burner shown...
I start CMD before debugging phone on PC and type "adb logcat", ADB starts and the message "Waiting for device" appears...
I plug the phone in, boot it and the computer finds the device in device manager... But ADB still "waits for device"... When I open another CMD Window and type "adb devices" it shows a device which is "offline"...
I have installed the latest ADB drivers (needed them for unlocking BL) and LG Software drivers...
Is there any other way to show a log while booting or at least turn the device to "online"?
Thanks in advance!
The phone should be detected as adb device in device manager do you see any driver contains adb in it - you can try droid explorer for log cat but I think it depends on working adb too
Thanks, I will try it later!
do you have adb version 1.0.31? lower versions won't work
also, there's a string in default.prop (in your kernel) with something like "ro.adb.secure=1" --> set it to 0 and re-compile
laufersteppenwolf said:
do you have adb version 1.0.31? lower versions won't work
also, there's a string in default.prop (in your kernel) with something like "ro.adb.secure=1" --> set it to 0 and re-compile
Click to expand...
Click to collapse
Thanks for your reply, I have the newest SDK so I think newest ADB, too, so that's not the problem...
thank you for this hint, I will look into it and will search that string....
I'll report when I find it
Since you have SDK, use ddms.
Tested and.... Nothing -.-
laufersteppenwolf said:
do you have adb version 1.0.31? lower versions won't work
also, there's a string in default.prop (in your kernel) with something like "ro.adb.secure=1" --> set it to 0 and re-compile
Click to expand...
Click to collapse
So, I just checked ADB version: 1.0.31...
I made it to unpack the boot.img (don't ask how ) and changed the "ro.adb.secure=1" to 0 and compiled it...
I just zipped and flashed the rom and connected it to PC and... Goddammit, nothing! Device is still offline... Any other ideas?
Paulo87 said:
Since you have SDK, use ddms.
Click to expand...
Click to collapse
So i just checked ddms... It tells me that it is a old version or sth. like that and I should use "monitor" instead of ddms...
Tried that, but still... Device is offline...
I start freaking out!
BlackDuty said:
So, I just checked ADB version: 1.0.31...
I made it to unpack the boot.img (don't ask how ) and changed the "ro.adb.secure=1" to 0 and compiled it...
I just zipped and flashed the rom and connected it to PC and... Goddammit, nothing! Device is still offline... Any other ideas?
So i just checked ddms... It tells me that it is a old version or sth. like that and I should use "monitor" instead of ddms...
Tried that, but still... Device is offline...
I start freaking out!
Click to expand...
Click to collapse
you can stay with ddms, it's better IMO
now you can try to change "ro.secure=1" to "ro.secure=0", compile and try again now adb should start as soon as possible, even on kernel level
Argghhh
Why didn't you tell it earlier?
Just joking, thank you!
Will try and report...
Another try went wrong...
Okay,
so I recompiled the boot.img with an "ro.security=0" string...
Flashed and restarted, device was found by PC but it's still shown as offline
Tested ADB Logcat DDMS & Moniter, everytime offline...
The device is shown in windows device manager like in attached picture...
Maybe something is wrong there?
.
I tried to reinstall all the drivers, but still nothing new...
I just wanted a f*cking Bootlog, but it looks like I have to write complete android from scratch :laugh:
Maybe you have another idea... *hoping* :silly:
BlackDuty said:
Okay,
so I recompiled the boot.img with an "ro.security=0" string...
Flashed and restarted, device was found by PC but it's still shown as offline
Tested ADB Logcat DDMS & Moniter, everytime offline...
The device is shown in windows device manager like in attached picture...
Maybe something is wrong there?
.
I tried to reinstall all the drivers, but still nothing new...
I just wanted a f*cking Bootlog, but it looks like I have to write complete android from scratch :laugh:
Maybe you have another idea... *hoping* :silly:
Click to expand...
Click to collapse
you don't use linux?! well, try to use a linux OS, and if it doesn't work there, too, do the following:
pull the battery
put it back in and boot the device
i guess it stops somewhere and stays there, right?
pull the battery again
put the battery back in and boot into CWM
now run:
Code:
adb shell
su
cat /proc/last_kmsg >/sdcard/debugging/last_kmsg
ctrl + c
adb pull /sdcard/debugging/last_kmsg C:\debugging\last_kmsg.txt
laufersteppenwolf said:
you don't use linux?! well, try to use a linux OS, and if it doesn't work there, too, do the following:
pull the battery
put it back in and boot the device
i guess it stops somewhere and stays there, right?
pull the battery again
put the battery back in and boot into CWM
now run:
Code:
adb shell
su
cat /proc/last_kmsg >/sdcard/debugging/last_kmsg
ctrl + c
adb pull /sdcard/debugging/last_kmsg C:\debugging\last_kmsg.txt
Click to expand...
Click to collapse
Unfortunatly I can't use linux, just with a terminal over cygwin :|
I will try that method tomorrow, now I have to sleep
Thank you again, you make me feel a little bit smarter then I am atm
Launch SDK Manager and download/install "Google USB Driver"
When the download is complete, follow this tutorial to install the usb driver's. -> Here
Next time you plug your device on boot you will see it as "Android ADB Interface".
Paulo87 said:
Launch SDK Manager and download/install "Google USB Driver"
When the download is complete, follow this tutorial to install the usb driver's. -> Here
Next time you plug your device on boot you will see it as "Android ADB Interface".
Click to expand...
Click to collapse
As you can see in the attached picture in my previous posts, there is already the "ADB Interface" on device manager, or is there any difference between "Android ADB Interface" and "ADB Interface"?
I will try to reinstall it and look into the link to install USB-Drivers you wrote here, later!
Thank you for that many tries to help me! I hope we will find the right way...
Hey, some news:
@Paulo87 : I tried to reinstall the google drivers and use the device as Android ADB Interface and it worked when I am in recovery...
Looked at monitor and ddms, they found a device but there was no "online" or "offline", but a "??"
I flashed the files and rebooted, plugged data cable in and... There is still this MTP-Device shown, no Android ADB Interface...
Tried the same steps there but it told me that in the folder google drivers are no drivers for this MTP device...
I think I will kill me in the next hours
Nah, just joking, but this is really annoying...
@laufersteppenwolf : Tried like you said:
pull battery off -> plug it in -> reboot -> bootloop -> pull battery off -> plug it in -> boot into recovery
plug in usb cable -> type "adb shell" on CMD with admin rights (adb starts server) -> typing "su" (error like /sbin/sh: su not found) -> still trying to pull the kmsg log, but as the SU rights fail, the whole way fails -.-
Any ideas why it is not found?
Thanks...
Try doing what @laufersteppenwolf said without the "su".
Honestly, if nothing work's... Just kill yourself like you said! (Joking)
Don't quit mate, everything has a solution.
Paulo87 said:
Try doing what @laufersteppenwolf said without the "su".
Honestly, if nothing work's... Just kill yourself like you said! (Joking)
Don't quit mate, everything has a solution.
Click to expand...
Click to collapse
I already tried, but it hangs on the last step, it says that "last_kmsg" wasn't find... So if it doesn't exist , it's logical that you can't move it... Something like this
And you really don't want to know how near I am to do that thing what the guy in your picture did... :silly:
Any other suggestions?
BlackDuty said:
@laufersteppenwolf : Tried like you said:
pull battery off -> plug it in -> reboot -> bootloop -> pull battery off -> plug it in -> boot into recovery
plug in usb cable -> type "adb shell" on CMD with admin rights (adb starts server) -> typing "su" (error like /sbin/sh: su not found) -> still trying to pull the kmsg log, but as the SU rights fail, the whole way fails -.-
Any ideas why it is not found?
Thanks...
Click to expand...
Click to collapse
this seems like the rom wasn't flashed?! or the rom has no su binary included...
and when it says, that last_kmsg wouldn't be found, it's most likely that you've got a serious problem with your kernel...
what kernel source are you using?
Honestly, i have no more ideas mate...
Good luck.
Glück
I found something interesting. When i used the OTG checker, i noticed that 3 system files are disabled(they don't have full permissions).
Here's what you have to do(if the FIX button doesn't work)
1.Use a root explorer (Xplore is needed)
2.Find the files with the X from the screenshot
3. Change the permissions and check all the boxes.
4.Reboot and done!
Someone test this and comment if it does or if it doesn't work.
I didn't tried ( i didn't root yet) but i hope it will work
(Tried on my s4 mini and it worked)
Johnny TDN said:
I found something interesting. When i used the OTG checker, i noticed that 3 system files are disabled(they don't have full permissions).
Here's what you have to do(if the FIX button doesn't work)
1.Use a root explorer (Xplore is needed)
2.Find the files with the X from the screenshot
3. Change the permissions and check all the boxes.
4.Reboot and done!
Someone test this and comment if it does or if it doesn't work.
I didn't tried ( i didn't root yet) but i hope it will work
(Tried on my s4 mini and it worked)
Click to expand...
Click to collapse
Hey, just tried. I've fixed permission for android.hardware.usb.host.xml file and now the otg checker give me only green check. Rebooted the phone but when i plug in my usb pen anything happen
Zeph1990 said:
Hey, just tried. I've fixed permission for android.hardware.usb.host.xml file and now the otg checker give me only green check. Rebooted the phone but when i plug in my usb pen anything happen
Click to expand...
Click to collapse
You must do on the all files. Now only android.hardware.usb.host.xml
Zeph1990 said:
Hey, just tried. I've fixed permission for android.hardware.usb.host.xml file and now the otg checker give me only green check. Rebooted the phone but when i plug in my usb pen anything happen
Click to expand...
Click to collapse
Do it for all of the files. Not only on android.hardware.usb.host.xml
doesn't work..
you must make changes to kernel also for otg to work
snapdesign said:
doesn't work..
you must make changes to kernel also for otg to work
Click to expand...
Click to collapse
Did you checked all the boxes on the permissions?
Johnny TDN said:
Did you checked all the boxes on the permissions?
Click to expand...
Click to collapse
what do you see in the photo? also otg needs support from kernel... it doesn't work without it
i make a custom kernel with host permissions but doesn't work anyway...
Possible problem its software and managed vold's...
In the RAMDISK it's pointed correct for USB OTG
/devices/hisi-usb-otg/usb1/* auto auto defaults voldmanaged=usbotg:auto
BadWolfYe said:
i make a custom kernel with host permissions but doesn't work anyway...
Possible problem its software and managed vold's...
In the RAMDISK it's pointed correct for USB OTG
/devices/hisi-usb-otg/usb1/* auto auto defaults voldmanaged=usbotg:auto
Click to expand...
Click to collapse
can you make a kernel with multirom support?
edit: you are the same bad wolf from htcmania?
snapdesign said:
can you make a kernel with multirom support?
edit: you are the same bad wolf from htcmania?
Click to expand...
Click to collapse
Yes the same
And in this moment MultiROM its innecesary (no support for other roms only EMUI...)
BadWolfYe said:
Yes the same
And in this moment MultiROM its innecesary (no support for other roms only EMUI...)
Click to expand...
Click to collapse
well, someone is working on a cm build... when that will boot we should have a kernel with multirom...
i tried on more way too for OTG already,,, added lines too vold.fstab etc etc but it wont support,,,
UPDATE
My phone is rooted and i am testing it. Hope it works on mine. If it doesn't, the post should be removed
Hiya Fellas,
I was messing around with my development build last night and I was able to turn on USB host mode and successfully plug in and use a usb flash drive. Now keep in mind that this was on CM 13 but, this might also work on a rooted stock.
Using adb or terminal app.
1. Look for a path in /sys/devices that ends with hisi_usb (e.g /sys/devices/f4000000.hisi_usb)
2. Now inside that folder there should be a file called plugusb.
3. use this command
echo hoston > /sys/devices/f4000000.hisi_usb/plugusb
Replace "f4000000" with the real value.
Now plug in your device and see if it is recognized!
EDIT: You may need to be root to do this!
ADB: "adb root"
TERMINAL APP: "su"
Meticulus said:
Hiya Fellas,
I was messing around with my development build last night and I was able to turn on USB host mode and successfully plug in and use a usb flash drive. Now keep in mind that this was on CM 13 but, this might also work on a rooted stock.
Using adb or terminal app.
1. Look for a path in /sys/devices that ends with hisi_usb (e.g /sys/devices/f4000000.hisi_usb)
2. Now inside that folder there should be a file called plugusb.
3. use this command
echo hoston > /sys/devices/f4000000.hisi_usb/plugusb
Replace "f4000000" with the real value.
Now plug in your device and see if it is recognized!
EDIT: You may need to be root to do this!
ADB: "adb root"
TERMINAL APP: "su"
Click to expand...
Click to collapse
The value changed... I forgot my USB adapter in the car... will update the in a few minutes... if it works you resolved a big thing in what..2 days from having the device? great dev... thanks!
EDIT: unfortunately it doesn't work on my device... also after reboot the value changed to OFF again... great find although
Meticulus said:
Hiya Fellas,
I was messing around with my development build last night and I was able to turn on USB host mode and successfully plug in and use a usb flash drive. Now keep in mind that this was on CM 13 but, this might also work on a rooted stock.
Using adb or terminal app.
1. Look for a path in /sys/devices that ends with hisi_usb (e.g /sys/devices/f4000000.hisi_usb)
2. Now inside that folder there should be a file called plugusb.
3. use this command
echo hoston > /sys/devices/f4000000.hisi_usb/plugusb
Replace "f4000000" with the real value.
Now plug in your device and see if it is recognized!
EDIT: You may need to be root to do this!
ADB: "adb root"
TERMINAL APP: "su"
Click to expand...
Click to collapse
WORK !!! THANK YOU !
- install from Playstore Universal Init.d
- Open Universal Init.d and activate support
- Create a generic text file Ex. usbotg in /etc/init.d folder with the following content
#!/system/bin/sh
echo hoston > /sys/devices/f4000000.hisi_usb/plugusb
!!!! Replace "f4000000" with the value found in your smartphone (my: ff100000) !!!!
- give to the file 755 permission
- reboot
I used Root Explorer to do all.
Enjoy !
Meticulus said:
Hiya Fellas,
I was messing around with my development build last night and I was able to turn on USB host mode and successfully plug in and use a usb flash drive. Now keep in mind that this was on CM 13 but, this might also work on a rooted stock.
Using adb or terminal app.
1. Look for a path in /sys/devices that ends with hisi_usb (e.g /sys/devices/f4000000.hisi_usb)
2. Now inside that folder there should be a file called plugusb.
3. use this command
echo hoston > /sys/devices/f4000000.hisi_usb/plugusb
Replace "f4000000" with the real value.
Now plug in your device and see if it is recognized!
EDIT: You may need to be root to do this!
ADB: "adb root"
TERMINAL APP: "su"
Click to expand...
Click to collapse
ThankS!!!! It worked but, there are some troubles:
after using that command doesn't work the usb cable phone - PC (need reboot or to write "hostoff" instead of "hoston");
after rebbot need again to rewrite the command.
With universal Init.d it can be a little easy cause you can make 2 file ( 1 for hoston and 1 for hostoff) and just run them from app, so with 2 touch you can enable and disable otg instead of wirting everytime the command using terminal.
Edit: universal init.d doesn't work properly so I used a script runner and just run from it (with root permissions) 1 of 2 script (enable, disable).
Edit2: Look these images to see what I've done(don't need to reboot phone after):
Image 1: http://prnt.sc/ckk9hs
Image 2: http://prnt.sc/ckka26 (used this app: https://play.google.com/store/apps/details?id=com.snclabs.scriptrunner&hl=it)
Don't know if anyone else has this problem but for some weird reason when I try plug in my 8gb or 128gb it won't work but if plug in the 32gb memory stick bam it works fine any one know the reason y?
Sent from my HUAWEI VNS-L31 using XDA-Developers mobile app
Noel.89 said:
Don't know if anyone else has this problem but for some weird reason when I try plug in my 8gb or 128gb it won't work but if plug in the 32gb memory stick bam it works fine any one know the reason y?
Sent from my HUAWEI VNS-L31 using XDA-Developers mobile app
Click to expand...
Click to collapse
I've tried with my 16gb usb pendrive, 500gb external HD, 2TB external HD and it worked fine with all of them...
SevenSlevin said:
I've tried with my 16gb usb pendrive, 500gb external HD, 2TB external HD and it worked fine with all of them...
Click to expand...
Click to collapse
Really how did you get yours to work maybe I'm doing something wrong putting the file in wrong place
Sent from my HUAWEI VNS-L31 using XDA-Developers mobile app