HI, I have an S3 9300 which was damaged by water. I finally managed to revive it by using Isopropyl Alcohol and cleaning it. The piece worked perfectly fine except for the display screen which kept blurring out. Unfortunately, the S3 display gave up and i cannot see anything or even use the touch. I tried opening the display to clean out any moisture, but again unfortunately even after carefully removing the display it wont work. Now the S3 is working with no display or Touch. repairing it here in India is costing me more than a second hand unit available. so i decided to not repair it. But since the motherboard and the rest are working fine, i thought i could use it for something else like a security IP camera.
Now i have a problem, the USB debugging was not enabled before the display konked off. the S3 is not rooted either. Can anyone help me how can i get the USB debugging enabled somehow so i can operate the phone from the desktop PC using MyPhoneExplorer. this way i can install apps, use the phone for SMS, calls and use the camera too.
I just need the USB debugging on so i can do the needful.
Anybody has any ideas? how can you help me here?
i have tried putting it in download mode and flashing a rooted stock firmware. this will at least have USB debugging on by default (i think).
Please help. what can i do?
If anyone has a working display with a busted motherboard, can i buy it? how much? i live in mumbai - India
Please reply in the thread or PM me
Thanks guys.
try connecting s3 to tv via hdmi and goto settings>developer option>enabled usb debugging ?
MoonBlade said:
try connecting s3 to tv via hdmi and goto settings>developer option>enabled usb debugging ?
Click to expand...
Click to collapse
would have tried it. but the digitizer does not work either. cannot use the display or touch. secondly i dont have the MHL HDMI connector too.
francisdsa said:
would have tried it. but the digitizer does not work either. cannot use the display or touch. secondly i dont have the MHL HDMI connector too.
Click to expand...
Click to collapse
looks like you are in a bit of a trouble.. i would have suggested flashing any other rom with usb debugging already enabled like cm10.1 . but with screen not working accessing recovery to flash rom will be tricky.
MoonBlade said:
looks like you are in a bit of a trouble.. i would have suggested flashing any other rom with usb debugging already enabled like cm10.1 . but with screen not working accessing recovery to flash rom will be tricky.
Click to expand...
Click to collapse
Ha ha ha. Actually the issue is that USB debugging is not enabled. that is the reason i am jumping around trying stuff. in fact i am on ODIN FU##ng around and now the device just wont go off the download mode. still fooling around.
i think i may brick the phone... anyways, the piece was a lab rat for me...
can i salvage anything from it? can i use the camera elsewhere? anything???
do let me know
francisdsa said:
Ha ha ha. Actually the issue is that USB debugging is not enabled. that is the reason i am jumping around trying stuff. in fact i am on ODIN FU##ng around and now the device just wont go off the download mode. still fooling around.
i think i may brick the phone... anyways, the piece was a lab rat for me...
can i salvage anything from it? can i use the camera elsewhere? anything???
do let me know
Click to expand...
Click to collapse
i heard somewhere that you can use usb keyboard with your s3. but then i am not sure whether u need usb debugging to be ON for this to work. if its not needed then i think you can use the keyboard to navigate to settings to enable usb debugging.
i have never tried this though try searching a bit in google. might find a solution.
http://forum.xda-developers.com/showthread.php?t=1749902
You cannot use input device and video output simultaneously. This means you cannot change any settings. Only bet is to try to find an adaptor that allows MHL and usb simultaneously.
Sent from my GT-I9300 using Tapatalk 4
rootSU said:
You cannot use input device and video output simultaneously. This means you cannot change any settings. Only bet is to try to find an adaptor that allows MHL and usb simultaneously.
Sent from my GT-I9300 using Tapatalk 4
Click to expand...
Click to collapse
You are right.
Well, please let me know if there is any other method to control the phone from the PC and enable the USB debugging settings.......I would be delighted and thankful
any ADB command mode to start USB vai command prompt
francisdsa said:
You are right.
Well, please let me know if there is any other method to control the phone from the PC and enable the USB debugging settings.......I would be delighted and thankful
Click to expand...
Click to collapse
There's no other method.
Heres a thread about MHL and OTG : http://forum.xda-developers.com/showthread.php?t=1741583
rootSU said:
There's no other method.
Heres a thread about MHL and OTG : http://forum.xda-developers.com/showthread.php?t=1741583
Click to expand...
Click to collapse
Need to know something.
What if i flash a pre-rooted ROM from ODIN? USB debugging should be enabled on it by default.
but will i get a rooted custom ROM in odin flashable format?
will i be able to flash the ROM if the device is not rooted and USB debugging disabled?
have never tried this method and hence asking a nooby question
Please help
francisdsa said:
Need to know something.
What if i flash a pre-rooted ROM from ODIN? USB debugging should be enabled on it by default.
but will i get a rooted custom ROM in odin flashable format?
will i be able to flash the ROM if the device is not rooted and USB debugging disabled?
have never tried this method and hence asking a nooby question
Please help
Click to expand...
Click to collapse
i was just googling around . i found something interesting. i think you can enable usb debugging via adb in CWM if u have proper knowledge of adb commnads. just do a search for enabling usb debugging by changing value of a property in the settings.db file located in data/data/com.android.providers.settings/databases/settings.db
rootSU said:
There's no other method.
Heres a thread about MHL and OTG : http://forum.xda-developers.com/showthread.php?t=1741583
Click to expand...
Click to collapse
MoonBlade said:
i was just googling around . i found something interesting. i think you can enable usb debugging via adb in CWM if u have proper knowledge of adb commnads. just do a search for enabling usb debugging by changing value of a property in the settings.db file located in data/data/com.android.providers.settings/databases/settings.db
Click to expand...
Click to collapse
Thanks dude, but the issue is i dont have root or CWM installed. With no display this is will be even painful as i will blindly be shooting around and possibly brick the device.
i have spoken to a few friends if they can arrange an S3 and maybe with the USB keyboard over OTG i can enable the developer settings. Secondly have also spoken around with a few service centers and mobile repair shops if they can temporarily swap a working display from a repair piece and enable the mode for me. no one has a piece at present. fingers crossed...
by the way, you are from india.. Where are you from? which city? I am from Mumbai
francisdsa said:
Thanks dude, but the issue is i dont have root or CWM installed. With no display this is will be even painful as i will blindly be shooting around and possibly brick the device.
i have spoken to a few friends if they can arrange an S3 and maybe with the USB keyboard over OTG i can enable the developer settings. Secondly have also spoken around with a few service centers and mobile repair shops if they can temporarily swap a working display from a repair piece and enable the mode for me. no one has a piece at present. fingers crossed...
by the way, you are from india.. Where are you from? which city? I am from Mumbai
Click to expand...
Click to collapse
Flashing CWM is easy. You just need to be in download mode which is easy enough to bet into blind.
ADB is done from a computer. If the settings.db has the answer, all you do is adb pull it, make the change and adb push it. Seems simple enough to me.
rootSU said:
Flashing CWM is easy. You just need to be in download mode which is easy enough to bet into blind.
ADB is done from a computer. If the settings.db has the answer, all you do is adb pull it, make the change and adb push it. Seems simple enough to me.
Click to expand...
Click to collapse
could try that. but i read elsewhere that the settings change will not affect ti as the boot.img file also needs to be stripped and modified to work with it.
francisdsa said:
could try that. but i read elsewhere that the settings change will not affect ti as the boot.img file also needs to be stripped and modified to work with it.
Click to expand...
Click to collapse
Can't you just flash a supported custom kernel then? That's all boot image is. A kernel available in .tar? Siyah 1.9.1 tar flashed from Odin.
Then boot into recovery:
Code:
adb shell
mount system
sqlite3 /data/data/com.android.providers.settings/databases/settings.db
SELECT * FROM global;
update global set value=1 where name='adb_enabled';
SELECT * FROM global;
CTRL + C
adb shell
mount system
echo "persist.service.adb.enable=1" >> /system/build.prop
This should work. Yes, adb_enabled is the value set as 0 or 1 when turning usb debugging on or off, I tested it all
Note SELECT * FROM global; shows all the values in the global table which is where adb_enabled is. It should say 0. Then you run the update command and then SELECT again to witness the change. I noticed that this did not persist after booting into android, which is why we need to put persist in the build prop. Hope this helps.
rootSU said:
Can't you just flash a supported custom kernel then? That's all boot image is. A kernel available in .tar? Siyah 1.9.1 tar flashed from Odin.
Then boot into recovery:
Code:
adb shell
mount system
sqlite3 /data/data/com.android.providers.settings/databases/settings.db
SELECT * FROM global;
update global set value=1 where name='adb_enabled';
SELECT * FROM global;
CTRL + C
adb shell
mount system
echo "persist.service.adb.enable=1" >> /system/build.prop
This should work. Yes, adb_enabled is the value set as 0 or 1 when turning usb debugging on or off, I tested it all
Note SELECT * FROM global; shows all the values in the global table which is where adb_enabled is. It should say 0. Then you run the update command and then SELECT again to witness the change. I noticed that this did not persist after booting into android, which is why we need to put persist in the build prop. Hope this helps.
Click to expand...
Click to collapse
Huh. That's seeming a bit tough fer me especially after I left linux almost 10 years ago. But am eager to try it out. Will try so and check. yhanks fot the great info. Will revert
francisdsa said:
Huh. That's seeming a bit tough fer me especially after I left linux almost 10 years ago. But am eager to try it out. Will try so and check. yhanks fot the great info. Will revert
Click to expand...
Click to collapse
You can literally copy and paste that (line by line) into windows cmd prompt, once you have adb.exe dropped in c:\windows\system32
But yeah let me know please. I did test successfully so works for me
rootSU said:
You can literally copy and paste that (line by line) into windows cmd prompt, once you have adb.exe dropped in c:\windows\system32
But yeah let me know please. I did test successfully so works for me
Click to expand...
Click to collapse
Yea yea. Surely. I shall try tomorrow itself.
francisdsa said:
Yea yea. Surely. I shall try tomorrow itself.
Click to expand...
Click to collapse
Did not work. Flashes the Siyah kernel via odin, the phone went into a boot loop.
went into recovery mode
started ADB
here is the output
====================
C:\>adb devices
List of devices attached
4df7dfa9572f3051 recovery
C:\>adb shell
[email protected]:/ $ mount system
mount system
Usage: mount [-r] [-w] [-o options] [-t type] device directory
1|[email protected]:/ $
=============================
here are the mount paths
================
C:\>adb shell
[email protected]:/ $ mount
mount
rootfs / rootfs rw 0 0
tmpfs /dev tmpfs rw,nosuid,relatime,mode=755 0 0
devpts /dev/pts devpts rw,relatime,mode=600 0 0
proc /proc proc rw,relatime 0 0
sysfs /sys sysfs rw,relatime 0 0
/dev/block/mmcblk0p9 /system ext4 rw,nodev,noatime,nodiratime,barrier=1,data=ord
ered 0 0
[email protected]:/ $
=========================
Am stuck please help
Related
Hi i was just looking for some quick clarification if anyone is willing.
Boot into Clockwork Recovery. -DONE
Navigate to "mounts and storage". -DONE
Select "mount USB storage". -DONE
Copy /usr/src/tegratab/boot-custom-kernel.zip to the mounted filesystem. -HOW?
I tried adb push /usr/src/tegratab/boot-custom-kernel.zip /sdcard I dont believe it worked since nothing actually happened. I didnt even get my command line back. Im just waiting though, its been about 10 minutes though, I really dont think anything is happening. Actually it just finished, and now my tab is locked up. After I fix this I hope someone will be able to tell me how to properly install this. Also when I go into the android system then turn on usb storage device and try and drag and drop it says its going to take 3 hours?
I cant seem to figure out how to copy my file to "the mounted filesystem" I dont get a filesystem that I can drag and drop my zip into, I dont see or know of a command to do it through the terminal. So how can I accomplish this?
Thanks!
DKS1282 said:
Hi i was just looking for some quick clarification if anyone is willing.
Boot into Clockwork Recovery. -DONE
Navigate to "mounts and storage". -DONE
Select "mount USB storage". -DONE
Copy /usr/src/tegratab/boot-custom-kernel.zip to the mounted filesystem. -HOW?
Click to expand...
Click to collapse
Need details--
Whose kernel is this? Is it for the gTab? Where was it compiled from (source)? Is it stable? Has it been tested? Why is the guy telling you to copy the zip file onto the internal SD via ClockworkMod when you can do it more easily by other means? Can I have a look at the contents of the zip file?
really? in order to install it you have to know all that? The zip file is over 1.5 gigs.. How do you propose I get it to you?
DKS1282 said:
really? in order to install it you have to know all that? The zip file is over 1.5 gigs.. How do you propose I get it to you?
Click to expand...
Click to collapse
This kernel better be able to sing and dance for you if it's that big. What the hell is in there? I want to see what's in there now.
DKS1282 said:
really? in order to install it you have to know all that? The zip file is over 1.5 gigs.. How do you propose I get it to you?
Click to expand...
Click to collapse
This is why I asked you for the details. A compiled kernel for the gTab, along with the most useful modules, plus the installer program, is about 3MB, max.
The complete Linux kernel source, uncompressed, is around 450MB. Compressed, it is ~100MB. A compressed 1.5GB file would therefore contain a heck of a lot more than just the kernel sources. What were you expecting to happen here? Ram a boat-load of source into the tablet and it should automatically compile and install everything for you?
Actually no... I followed a link and followed directions and I actually thought I was doing well till I saw the size of the file... Im actually going to work on recompiling the kernel again. It was a version of pershoots but I think the tutorial I was working off of is incorrect as are most of them on the net. Im learning but sadly not at the pace I would like, Im new to linux and android. Thank you all for the help so far. I'll post what ive done here in a lil bit and I was wondering if I would be able to get advice on how to install it... Ill even link the tutorial I follow. Here it is http://forum.xda-developers.com/showthread.php?t=916198
Now that Ive gone over it again its an issue in the zipping... For some reason my 28.7M file zips to 1.6gb WTF? Here is the command I used
From inside the file where the contents is to be zipped zip -r /usr/src/tegratab/boot-custom-kernel *
Yes evey time I zip it it comes out to 1.6 gigs. The system file is is pretty small but after its been ziped it actually takes most of the 1.6gb... Could I possible send the meta file, kernel file, and system file? Or maybe someone could tell me how to correctly do this? Ive followed the directions in that link and thought I was getting a legit output but I guess that im not even close.
GOOD NEWS EVERYBODY! I can save you 15% on car insurance...
Actually I was able to figure out what has happened... There were some symlinks that didnt get removed so it grabbed everything in that link and zipped it as well... after I fixed the issue it zipped correctly and I was even able to get it to install... Sadly the prolific driver for the 2303 is still not included even though it shows on the kernel menuconfig as being included, I guess Im going to try again and make it modular and see if I can get the driver file to install that way.. Ill let you know how it goes and also upload and link it if I can get it to work in case someone else wants to grab it and build off it. Im also planning on helping out the forums a little bit...
Thank you again.
DKS1282 said:
Sadly the prolific driver for the 2303 is still not included even though it shows on the kernel menuconfig as being included...
Click to expand...
Click to collapse
Attach the .config (kernel configuration file) so I can look at it.
Does running dmesg on the new kernel show the driver loading/initializing?
Are the /dev/ttyUSB* device files present? Are the permissions for those serial devices correct? I'm not sure what they ought to be, but try making them read+write for all--at least while you are testing things: chmod 666 /dev/ttyUSB* as root.
Here is actually the zipped kernel file. When it compiles it does show the drivers being installed, I just cant get the device to recognize the Prolific cable. Ive tried including them, Ive tried modular, im not sure how to make it work, or if there is something im missing entirely. Thanks again.
http://www.mediafire.com/?nil9bh3spu6sp78
DKS1282 said:
Here is actually the zipped kernel file.
Click to expand...
Click to collapse
The binary is no use to me--I don't have your hardware. The .config file is what I need.
When it compiles it does show the drivers being installed, I just cant get the device to recognize the Prolific cable.
Click to expand...
Click to collapse
The real test is the dmesg output, not whether the driver is being compiled in.
However, I think your problem is that you've compiled the wrong driver. What you need is the driver for "Prolific PL-2301/2302 based cables" which is included by enabling:
config USB_NET_PLUSB
which depends on
config USB_USBNET and
config EXPERIMENTAL
The module will be called plusb.ko, I think.
Sorry for being really uneducated on this. But I can not find any of thoes that you listed in the kernel. Also I cant even find the config file. I know where im targeting it from command line but if I try to move it it says file not found, and if I try and go there visually the file isnt there.
Id love to be able to upload what you want to see, and Id love to be able to add in the items you just suggested. But alas. neither seems possible.
Its honestly odd to me.. Ive been reading a couple different posts on the net that say you install this driver for the Prolific 2303. But not the PL2303.... So why is it included when it doesn't do what its supposed to do? Ive tried a lot of different methods and none of them work. It sucks cause I see people using it. Maybe Its not the kernel and its the android OS? I really have 0 clue at this point and about to just give my resignation at my employment.
The .config file will be present in the kernel's main directory (/usr/src/tegratab/gtab-2632/.config) if you have already built a kernel.
It looks like there are 2 drivers for Prolific hardware in the source tree. One is for host-to-host cables with Prolific chips (which is not enabled by default, and which, I think, is what you want), and the other for a Prolific USB serial port adapter (which is already enabled by default).
To build the module for the first, do a make menuconfig, then select:
Device Drivers > Network device support > USB Network Adapters > Prolific PL-2301/2302 based cables
However, you should verify what you have before you build the module. Do a "lsusb" then check the USB device IDs against the USB ID database in /var/lib/usbutils/usb.ids on a regular Linux machine.
Hints:
0. See pershoot's hints to another user here and further along in the same thread.
1. Make sure that you have downloaded the correct pershoot kernel: froyo or gingerbread.
2. You don't need to include all the modules in your kernel zip file. Just overwrite the kernel proper (zImage), the wireless driver (bcm4329.ko) and then add only the prolific driver module. Otherwise you're just wasting space on the /system partition.
3. Sign the zip file after creating it.
Thank you so much for the attempt.
But my .config file is not located where you have directed me. I checked there before, I could send you a screen shot showing you this.
Thank you for showing me where the driver for the cables where, I would not have checked network adapters looking for USB.... Alas, this has not solved my problem. The cable is still undetected by the OS. Although almost EVERY other usb is detected.
Im really not sure why this wont work. It installs 100% fine I have 0 issues on this, but the Prolific 2303 usb to serial cable will not show up in log cat or anything.. Although when i adb shell and do lsusb I see it and it has a device ID and everything.
Thank you again for the help..
DKS1282 said:
But my .config file is not located where you have directed me.
Click to expand...
Click to collapse
It is created in the kernel's top-level directory (ie. the same directory as the file REPORTING-BUGS) after you do "make menuconfig".
If you still can't find it, do,
find /some/path/ -name .config
after you've finished "make menuconfig". Replace /some/path/ with your kernel source dir (or / to search everything that is mounted).
Alas, this has not solved my problem. The cable is still undetected by the OS. Although almost EVERY other usb is detected.
Click to expand...
Click to collapse
If the driver is built as a module then the kernel will recognize it only after you have loaded the module. Load the correct module first, either plusb.ko or pl2303.ko, depending on your hardware, then check for detection/initialization messages from the module by issuing a "dmesg" command immediately after the "insmod /some/path/driver.ko" command.
Im really not sure why this wont work. It installs 100% fine I have 0 issues on this, but the Prolific 2303 usb to serial cable will not show up in log cat or anything.. Although when i adb shell and do lsusb I see it and it has a device ID and everything.
Click to expand...
Click to collapse
Still lacking details:
1. Did you download the correct kernel--Froyo/GB?
2. Are you sure you're running the new kernel after flashing the zip file?
3. Did you insmod the correct module?
4. What is the USB device ID shown?
5. Did you run dmesg--not logcat--after you insmod'ed the correct module? Can I see that dmesg output?
I can not find a .config file anywhere on this computer. it just does not exist.
Yes I am using a gingerbread version.
Insmod does not install anything for me. Although I installed the modules before even packaging the kernel. Ive verified this by checking in the the correct driver files once installed.
I dont remember the device Id exactly but its something similar to 067b:2303
I didnt run dmesg, honestly, this is way beyond me. I have absolutely no clue what im doing at all... I wasnt even hired for this job.. I was supposed to create an app that will use this specific cable on this specific device, although they did not give me the device able to use the cable... So now I have to figure out how to do this, and im just going to resign and tell them im not a hacker im a developer. Thank you very much for your effort but I am turning in my resignation here now at the end of the day. Thank you again and I'll give you thanks.
You had asked a while back if dev/ttyUSBx has shown, and I did get that to show last night. its dev/ttyUSB0 Ive tried to use a usb to serial api but the app couldn't open the serial port... Im guessing because android does not support that (since they dont really support anything) I personally dont even understand why these things sell... Its a giant useless phone that can not make phone calls. Im in the wrong business I need to sell useless products to consumers.
DKS1282 said:
I can not find a .config file anywhere on this computer. it just does not exist.
Click to expand...
Click to collapse
You a) didn't search correctly, b) haven't built the kernel yet, or, c) done a "make mrproper" and cleaned up.
Yes I am using a gingerbread version.
Click to expand...
Click to collapse
Which ROM?
I dont remember the device Id exactly but its something similar to 067b:2303
Click to expand...
Click to collapse
You cannot be vague about this. Run a Terminal emulator on the gTablet (download one from Market if needed), then type in the command in bold:
Code:
$ [B]lsusb[/B]
Send me the output of lsusb.
I didnt run dmesg,...Thank you very much for your effort but I am turning in my resignation here now at the end of the day.
Click to expand...
Click to collapse
Steady on, mate--we'll get you sorted: Just send me the lsusb output and I'll build a kernel for you--if the current kernel sources include the driver code.
You had asked a while back if dev/ttyUSBx has shown, and I did get that to show last night. its dev/ttyUSB0 Ive tried to use a usb to serial api but the app couldn't open the serial port...
Click to expand...
Click to collapse
Does the app have permissions to read/write the device? Use the chmod command I gave in an earlier post to give permissions.
Next: once the actual hardware is connected to the Prolific cable, is data appearing on /dev/ttyUSB0? Run,
Code:
$ [B]hexdump -C /dev/ttyUSB0[/B]
to see if any data appears.
But, this depends on the device. Some devices need to be triggered, either electrically or by sending commands to the port, before they will send anything back. Other devices will spit data out as soon as power is applied to them.
Which kind is yours?
lsusb returns 067b:2303
My device needs to have data sent to it in order for it to start spitting out data. Otherwise there is nothing happening. It requires a 16bit hex "Start Command". So of course $ hexdump -C /dev/ttyUSB0 returns nothing.
I have the kernel I built here, as well as the gingerbread 2.3.4 rom i am using, and Ive also included the Gaps I needed to install into 2.3.4 to activate the USB feature. (why isnt that feature standard since its really the only difference for 2.3.3 and 2.3.4?
http://www.mediafire.com/?1phzkmvhtr0li
Thank you again.
Honestly you know what would fix all of this... Being able to install windows 7 on this tablet. I know the viewsonic view pad has a dual boot android / windows 7 how cool is that?
DKS1282 said:
lsusb returns 067b:2303
My device needs to have data sent to it in order for it to start spitting out data. Otherwise there is nothing happening. It requires a 16bit hex "Start Command". So of course $ hexdump -C /dev/ttyUSB0 returns nothing.
Click to expand...
Click to collapse
That's assuming that /dev/ttyUSB0 is the correct port, which may not be the case.
Right after the tablet has booted, load both the Prolific kernel modules (or only plusb.ko, if the other is built into the kernel--you still haven't sent me your .config file), attach the Prolific cable to the tablet, then attach the actual device to the cable, then run a
Code:
$ [B]dmesg > /mnt/sdcard/dmesg.txt[/B]
command. Attach the dmesg.txt so I can look at it.
Couldnt do it. Lost the job. Thanks anyway.
Here is a small script that toggle force usb charging option from pershoot kernel :
Code:
#!/system/bin/sh
export STATE=`cat /sys/class/power_supply/battery/force_usb_charging`
if [ $STATE == 0 ]
then echo 1 > /sys/class/power_supply/battery/force_usb_charging
echo "Enable USB Charging"
else echo 0 > /sys/class/power_supply/battery/force_usb_charging
echo "Disable USB Charging"
fi
It needs root permission and a suitable kernel such as pershoot's.
PS: first step in the XDA community
It will be nice if you could explain how to use this script (one of the several ways).
Sorry to forgot the documentation part, here it is :
It can be used with any terminal apps with root access, just copy the content into a file (toggle_usb.sh for instance) and launch it in root terminal with :
Code:
sh toggle_usb.sh
A more user friendly way is to use Script Manager with SMWidget to add it on your homescreen. I use it this way so I could disable charging when the tab is plugged only for a file transfert.
Will this work on other devices? Like say the acer a100 or acer a500. Considering getting one of those but don't like that neither will charge usb.
If this only works for galaxy tab, how come? Just curious why force usb works on galaxy tab and not other devices.
It might work on other devices if the charging chipp support it and if the kernel has driver for. For the Galaxy Tab,The stock kernel and many others shipped with custom rom don't allow usb charging.
If supported by your hardware the script should work, it only use standard script and kernel related configuration.
EDIT:
The Acer a100 et a500 have a dedicated charger wich deliver 12V which is far more than a USB port can deliver (5V), I seriously doubt they put a dc-dc converter to connect the usbport to the charging chip.
Envoyé depuis mon GT-P7500 avec Tapatalk
Widget Apps
Hello,
I've tried to make it more user friendly, so I created a small widget apps using my previous script. It's my first real apps for Android, it still has some flaws.
Known Issues :
when adding the widget the file is at unknown state, need to hit the refresh button
Design is perfectible especially icons...
I would like to thanks the authors of the android-widget-development-tutorials availlable on google code.
not on tab 3
ebolalex said:
Here is a small script that toggle force usb charging option from pershoot kernel :
Code:
#!/system/bin/sh
export STATE=`cat /sys/class/power_supply/battery/force_usb_charging`
if [ $STATE == 0 ]
then echo 1 > /sys/class/power_supply/battery/force_usb_charging
echo "Enable USB Charging"
else echo 0 > /sys/class/power_supply/battery/force_usb_charging
echo "Disable USB Charging"
fi
It needs root permission and a suitable kernel such as pershoot's.
PS: first step in the
Well so far as I can see the folder called battery here apears as a file that is un openable to root explorer, the terminal will go in but there is no editing allowance as the files are locked, command chmod return a bad mode eror, since force_usb_charging does not exist I thought np ill creat on... long story short I made a file by that name in storage then used cp to copy that file to the destination mentioned (after chmod the sys class power_supply to write for all, ) battery would not as I mention take such command. All in all I still have not created the file force_usb_charging with a 1 as cat. So question........ how can I create the file in the directory. I am rooted, all my work in terminal has been su, I see the # show me as rooted, and I can alter the permissions. (Ps sorry dude with svsfsswitch.apk did absolutly nothing as the file did not exist, nor did the script above) is the smt 210r that different from othet machines? Lol retorical q, sorry . Tyvm for the help in advance. With time ill learn this linux /android stuff out.... summery how to creat a file in the sys/class/power_supply/battery called force_usb_charging containing the number 1.....
Click to expand...
Click to collapse
grummbunger said:
ebolalex said:
Here is a small script that toggle force usb charging option from pershoot kernel :
Code:
#!/system/bin/sh
export STATE=`cat /sys/class/power_supply/battery/force_usb_charging`
if [ $STATE == 0 ]
then echo 1 > /sys/class/power_supply/battery/force_usb_charging
echo "Enable USB Charging"
else echo 0 > /sys/class/power_supply/battery/force_usb_charging
echo "Disable USB Charging"
fi
It needs root permission and a suitable kernel such as pershoot's.
PS: first step in the
Well so far as I can see the folder called battery here apears as a file that is un openable to root explorer, the terminal will go in but there is no editing allowance as the files are locked, command chmod return a bad mode eror, since force_usb_charging does not exist I thought np ill creat on... long story short I made a file by that name in storage then used cp to copy that file to the destination mentioned (after chmod the sys class power_supply to write for all, ) battery would not as I mention take such command. All in all I still have not created the file force_usb_charging with a 1 as cat. So question........ how can I create the file in the directory. I am rooted, all my work in terminal has been su, I see the # show me as rooted, and I can alter the permissions. (Ps sorry dude with svsfsswitch.apk did absolutly nothing as the file did not exist, nor did the script above) is the smt 210r that different from othet machines? Lol retorical q, sorry . Tyvm for the help in advance. With time ill learn this linux /android stuff out.... summery how to creat a file in the sys/class/power_supply/battery called force_usb_charging containing the number 1.....
Click to expand...
Click to collapse
Hi grummbunger,
The /sys folder is a special filesystem handled by the linux kernel itself (by the means of its drivers), it provide information and control on peripheral. So If you do not have a specific fil in your /sys you could not create it. My Script was intended to work with Pershoot kernel, if you do not use it, the driver may not be loaded or might use a different file.
I would asked you which ROM and Kernel you are using to test it, but unfortunately i don't have access to a galaxy tab anymore...
Could you post me the list of file availlable in your battery folder ?
Welcome in the community, I hope you'll find the way to hack into your device to suit your needs
Click to expand...
Click to collapse
samsung usb charge enabling
ebolalex said:
grummbunger said:
Hi grummbunger,
The /sys folder is a special filesystem handled by the linux kernel itself (by the means of its drivers), it provide information and control on peripheral. So If you do not have a specific fil in your /sys you could not create it. My Script was intended to work with Pershoot kernel, if you do not use it, the driver may not be loaded or might use a different file.
I would asked you which ROM and Kernel you are using to test it, but unfortunately i don't have access to a galaxy tab anymore...
Could you post me the list of file availlable in your battery folder ?
Welcome in the community, I hope you'll find the way to hack into your device to suit your needs
Click to expand...
Click to collapse
android version 4.1.2 (could not find a pershoot rom to run on a 7 inch samsung tab3, and before flashing at all i wanna make sure that the setting can't be applied without flashing as that is really a last resort.) but i am totally ok with flashing if it is nessesary. i have rockettab ready to go, but have no idea if that would help at all with this situation.
kernel 3.4.5-1304745-user
found that the link "battery" goes to sys/devices/platform/sec-battery/power_supply/battery there are many files there that report status of power and such i found, some of the files names are like:
batt_charging_source batt_lp_charging Charge_now charge_type soip_activated soip_level status talk_gsm wc_enable wc_status. etc...
tyvm for your interest in helping my problem!
Click to expand...
Click to collapse
grummbunger said:
ebolalex said:
android version 4.1.2 (could not find a pershoot rom to run on a 7 inch samsung tab3, and before flashing at all i wanna make sure that the setting can't be applied without flashing as that is really a last resort.) but i am totally ok with flashing if it is nessesary. i have rockettab ready to go, but have no idea if that would help at all with this situation.
kernel 3.4.5-1304745-user
found that the link "battery" goes to sys/devices/platform/sec-battery/power_supply/battery there are many files there that report status of power and such i found, some of the files names are like:
batt_charging_source batt_lp_charging Charge_now charge_type soip_activated soip_level status talk_gsm wc_enable wc_status. etc...
tyvm for your interest in helping my problem!
Click to expand...
Click to collapse
In fact the kernel you need to install must support charging from any sources. It should be specified in the kernel feature list. Stock kernel won't let you do this or it would work out of the box.
Be aware that your Usb port must provide enough power to charge your device.
You're welcome.
Click to expand...
Click to collapse
ebolalex said:
grummbunger said:
In fact the kernel you need to install must support charging from any sources. It should be specified in the kernel feature list. Stock kernel won't let you do this or it would work out of the box.
Be aware that your Usb port must provide enough power to charge your device.
You're welcome.
Click to expand...
Click to collapse
Well it is a dell usb with power share at 1.2 a a wall charger is 2, the battery is 4000ma, I digress though I have in fact found the battery lasts for well over the time I need so I am all good. Thanks again for the responce!
Click to expand...
Click to collapse
If your kernel supports init.d scripts you can save script to /system/etc/init.d and it will be automatically launched on device boot. You have to delete extension from script name and prefix is number from 00 to 99
Hi,
Any way to get this working on kitkat rom (carbon kk)?
Phone is photon q, in the original sprint rom burried under hidden menu's the is a app to do it, so it must be possible in some way....any ideas?
Thanks!
Hi guys, I have the Rock Jaw Vi phone which by all sense and purpose seems to be a clone of the HTC One. It's Quad Core with 2 mega pixel camera on the front and 8 mega pixel on the back. The case and all outward appearances are that of the HTC, the phone info screen displays the following ...
Model Number = RJViJGTL32SM
Andoid version 4.2.1
Baseband version = moly.wr8.w1248.md.wg.mp.v6.p8,2013/08/12 15:55
Kernel version 3.4.5 [email protected] #1 Mon Aug 19 16:54:14 CST 2013
Build Number = 0502H026_20130819
I can get into the boot options screen by doing the On/Volume Down press but the menu's are all in Chinese and just seem to go through self diagnostics and tests. I can drag n drop file from Mac OSx but none of the apps I have found so far will communicate with the phone via USB. I am trying to get root so i can do a full back-up and then to try and put HTC Android 4.3 on it.
Do you guys have any idea on how I can achieve this or to get the phone to display it's boot options in English ?
I am pretty much clueless and stuck, any advice, tips, hacks etc would be really appreciated
I did follow a link at one stage on the web that went to SRSroot but their tool was windows only
Hmmm More messing with the phone has revealed power on with volume up depressed gets me to some very small text menu with the options;
Boot Normal
Fastboot
Boot(UART)
Boot UART is all the test screens that I was getting in Chinese but now they are touch screen buttons and labeled in english ao that's good to know.
Using fastboot-mac from HTCRootOne tries to talk to it but comes back with error: could not clear input pipe; result -536854449, is this something that's platform specific, ie it's not a true HTC so the version of fastboot-mac is no good and needing a non specific version ?
Ok that error is generated to the oem get_identifier_token...
If i do a fastboot-mac devices i get the reply "mt6589_phone_720pv2 fastboot" ...
I'm getting there slowly
Done some more digging with the phone attached to the Mac here and checking my systems profile I see that the phone is listed under usb connections as seen in the screen grab, still referring the as a HTC. Getting a new usb cable delivered to see if the phones usb cable provided is for charging only. If anyone here has any other suggestions I would be all ears or eyes as the case might be
Done more grubbing around and have found it to be a HDC One, HTC One clone .... Now to go see if any are rooted on here
Can anyone help me
Well i am pretty much stuck here so if anyone is reading this and wants to offer some help and advice I could do with it
I have looked around on the phone and can't see any bin or system folders even with show hidden i can't find them.
adb wont give me a remote shell, it complains that there is no bin/bash
when i try and do an adb backup i get 0 byte files grrrrr!!
I still need to find a way of getting root
This phone is a tricky beast for a learner - lol
Install some file explorer that allows you to browse from the top folder (/). I'm pretty sure you'll find at least /system there.
gbl08ma said:
Install some file explorer that allows you to browse from the top folder (/). I'm pretty sure you'll find at least /system there.
Click to expand...
Click to collapse
Thanks Gbl08ma - I have have it opened in Mac osx finder with show all files hidden or otherwise - The phone shows as two "No Name" devices and get mounted immediately on connection ....
I used sideload to push a package file over using adb and then went back to use Finder, and I can't see the file anywhere - hidden partition perhaps ? Can you do that with Android ?
Even the Android SDK file transfer app wont see the phone when it's connected, I am all very confused - lol
Thanks for the reply - Wonder if i can use disk utility to so some probing and at least get an ISO image file incase I goof things real bad - lol
TpwUK
tpwuk01 said:
Thanks Gbl08ma - I have have it opened in Mac osx finder with show all files hidden or otherwise - The phone shows as two "No Name" devices and get mounted immediately on connection ....
I used sideload to push a package file over using adb and then went back to use Finder, and I can't see the file anywhere - hidden partition perhaps ? Can you do that with Android ?
Even the Android SDK file transfer app wont see the phone when it's connected, I am all very confused - lol
Thanks for the reply - Wonder if i can use disk utility to so some probing and at least get an ISO image file incase I goof things real bad - lol
TpwUK
Click to expand...
Click to collapse
/ does not get mounted over USB so you won't see /bin, /system, /data or anything other than the SD card and the internal FAT32 "user" partition when entering USB transfer mode.
You must do it on the device. And for adb to work, USB debugging must be enabled in the settings.
gbl08ma said:
/ does not get mounted over USB so you won't see /bin, /system, /data or anything other than the SD card and the internal FAT32 "user" partition when entering USB transfer mode.
You must do it on the device. And for adb to work, USB debugging must be enabled in the settings.
Click to expand...
Click to collapse
I already had the phone in usb debug mode. Had to set the phone to use usb as MTP and not mass storage device connection type. Now it allows me to get in to the blighter with adb, fastboot still errors with pipes. That method allows me to get adb shell running and i can get android file transfer .... back to the reading part again
Thanks for the information gbl08ma - if i can find a way to back-up the rom i will share it somewhere
Hmm yummy - lots of interesting things in there .... Forgive my ignorance again please, but if i can create an update.zip file from the shell on the device that compresses all files from \ and all subdirs would that be the same thing as a safe ROM backup ? i wanna be safe before i attempt to root the phone as someone on here has a lower spec version of this phone and says it's a partial brick now.
TpwUK
Rooted
This phone is easily rooted with the motochopper
http://forum.xda-developers.com/showthread.php?p=40747604
Now should I push my luck further and go for the ROM - lol
TpwUK
I believe i own the same mobile
@tpwuk01
I also asked the same here; http://forum.xda-developers.com/showthread.php?t=2180425&page=92
but i was only able to root using frama root app, and it worked like a charm, but thats the only thing i could achieve, dont know but it seems theres no official thread of developement going on for any cloned device, mine runs the MOLY.WR8.W1248.MD.WG.MP.V6.P8 2013/08/12 15:55 Baseband.
After root i just installed some root apps, ads blockers, cant get any recovery to work, (Playing safe actually not to brick this now, since no support yet) but would have appreciated trying out kitkat on it, using antutu to view up specs, its impressive, i got to find out our 13MP camera at the back can do a great job than it currently is we only need to figure out how to change the image compression, the one i stumbled upon online was the blast, the 13MP was great also the flash light was tweaked to be 50X its current brightness, our 1GB application space was increased to 3.5GB, GPS and the rest was also modded to work really great.
Would like to hear any new updates you stumble upon bro.
Still a nice and featured packed device.
Long story short... I have a non-rooted SGH-M919 (Samsung Galaxy S4) with a completely broken screen. USB to PC transfer doesn't work, it's set to charge only, Kies doesn't see it...etc.
I have found that it's still on my wifi and on my google play account so I can install apps from the website. Does anybody know any apps I can install that will instantly let me access my files (and transfer them) without needing to do anything on the phone's side? Remote access would be great but I'd settle for file sharing even if only on the local network.
Any other ideas would be great! I need to recover pictures and contacts that aren't on google, or the SD card. New phone doesn't take the SIM.
You're probably not going to like this answer, but I recommend you simply have the screen fixed. If MTP isn't enabled and you can't enable it, and it's not rooted... There's just not much you can do.
NetworkAuditor said:
You're probably not going to like this answer, but I recommend you simply have the screen fixed. If MTP isn't enabled and you can't enable it, and it's not rooted... There's just not much you can do.
Click to expand...
Click to collapse
That's not too helpful... I found a (paid) app that attempts to recover files from the phone's download mode, which I think I could get to. There's gotta be other (free) options out there if download mode has access to files. Also as I said, I'm sure there's some app out there that shares files on the local network. I just need a name if anybody has one.
Thanks for answering still... but I know there's options.
UnknownCloakedMan said:
That's not too helpful... I found a (paid) app that attempts to recover files from the phone's download mode, which I think I could get to. There's gotta be other (free) options out there if download mode has access to files. Also as I said, I'm sure there's some app out there that shares files on the local network. I just need a name if anybody has one.
Thanks for answering still... but I know there's options.
Click to expand...
Click to collapse
Oh! Well if you can get to recovery, you may be able to pull the files off the device or back it up entirely.
Search "adb from recovery" and see if that gets you anywhere. If you *can* use adb, you might be able use adb's "backup" command to back up whatever you have on there.
NetworkAuditor said:
Oh! Well if you can get to recovery, you may be able to pull the files off the device or back it up entirely.
Search "adb from recovery" and see if that gets you anywhere. If you *can* use adb, you might be able use adb's "backup" command to back up whatever you have on there.
Click to expand...
Click to collapse
No custom recovery and no root access so I don't think adb will work for me... will it? I've confirmed USB debugging is off.
UnknownCloakedMan said:
No custom recovery and no root access so I don't think adb will work for me... will it? I've confirmed USB debugging is off.
Click to expand...
Click to collapse
Well, I've never used adb from recovery before, but a quick search makes me think it could be possible. If you're desperate to recover the data, I' m assuming anything is worth a try.
Now most of the time, stock recovery doesn't have adb access, but if you can manage to unlock your phone, you would be able to install CWM recovery and boot to it.
However, this is unlikely, as IMO, the SGS4 is one of the most painful phones to try to unlock, especially when you don't have access to the screen.
soo.. I am trying adb right now. I did...
adb shell
cd /sdcard/DCIM/Camera
ls
and all my pictures are listed! I tried doing a pull at that point and it says device not found... which it clearly is since it's reading the info. Any idea what my next step is? mounting or something? I feel like I'm so close!
EDIT:
BOOM! got it! I read one post online that said "stay out of shell for pull" I reopened my adb window and just did "adb pull /sdcard/DCIM/Camera" and all is recovered now. Thanks and I hope this post helps somebody in the future!
UnknownCloakedMan said:
soo.. I am trying adb right now. I did...
adb shell
cd /sdcard/DCIM/Camera
ls
and all my pictures are listed! I tried doing a pull at that point and it says device not found... which it clearly is since it's reading the info. Any idea what my next step is? mounting or something? I feel like I'm so close!
EDIT:
BOOM! got it! I read one post online that said "stay out of shell for pull" I reopened my adb window and just did "adb pull /sdcard/DCIM/Camera" and all is recovered now. Thanks and I hope this post helps somebody in the future!
Click to expand...
Click to collapse
Glad you got everything resolved! Now for my own curiosity, how did you manage to get adb working?
NetworkAuditor said:
Glad you got everything resolved! Now for my own curiosity, how did you manage to get adb working?
Click to expand...
Click to collapse
Nothing special at all. It only required:
> Phone in download mode, wired to PC with USB cable
> ADB installed on PC
> Samsung USB Drivers
> Open adb command prompt, and run the pull command (after finding the exact directory using adb shell)
So i got the new G8X and have been trying desperatey to just access the system files to remove some bloatware.
Problem is it only gives me access from \User\0 and on. I tried to delete them through adb on windows but everytime i try and run adb shell the phone automatically disconnects.
I know i have all the updated drivers cause it recognizes the phone through windows and adb when i type adb devices
but as soon as i execute adb shell it disconnects. Does anyone have a solution for this?
Any sort of feedback would be greatly appreciated. i Have a 30 day return policy in effect if i cant gain access to any of that i plan on returning the phone.
Thanks for reading
Edit: Im dumb switching ports and usb cable resolved issue.
If anyone hears anything about root access please advise. Thanks all
I have had my phone on ADB and sending and reading data from it two nights in a row, I have not seen this problem at all. I can run adb shell no problem. Sorry! I know it's a stupid suggestion, but can you try a different USB cable/port on your PC?
SirataXero said:
I have had my phone on ADB and sending and reading data from it two nights in a row, I have not seen this problem at all. I can run adb shell no problem. Sorry! I know it's a stupid suggestion, but can you try a different USB cable/port on your PC?
Click to expand...
Click to collapse
Its not dumb, i appreciate the input i hve not tried a diff port or cable. I'm going to do that right now.
What provider are you using?
abraham3991 said:
Its not dumb, i appreciate the input i hve not tried a diff port or cable. I'm going to do that right now.
What provider are you using?
Click to expand...
Click to collapse
The problem might be that if you run from power shell command, first type cmd and press enter.
abraham3991 said:
Its not dumb, i appreciate the input i hve not tried a diff port or cable. I'm going to do that right now.
What provider are you using?
Click to expand...
Click to collapse
I bought unlocked but i'm using it with T-Mobile and its getting WiFi calling and HD Voice and everything. Works really well and am getting good service/signal with it on T-Mobile.
Yeah, as suggested, I also used it in CMD and not in powershell…
SirataXero said:
I bought unlocked but i'm using it with T-Mobile and its getting WiFi calling and HD Voice and everything. Works really well and am getting good service/signal with it on T-Mobile.
Yeah, as suggested, I also used it in CMD and not in powershell…
Click to expand...
Click to collapse
As simple as your suggestion was it lets me command it through cmd now., switching the cable worked.
Still through the phone itself i cant access system directories. and its not like i cant change things it just flat out wont let me view them at all.
The end goal is to get root/custom recoveries so i can install magisk and xposed, if you hear anything let me know.And thanks again!
abraham3991 said:
As simple as your suggestion was it lets me command it through cmd now., switching the cable worked.
Still through the phone itself i cant access system directories. and its not like i cant change things it just flat out wont let me view them at all.
The end goal is to get root/custom recoveries so i can install magisk and xposed, if you hear anything let me know.And thanks again!
Click to expand...
Click to collapse
No problem! Glad that worked.
I can view system directories, and I read them as well. However, I definitely can't change anything and don't have write access either.
Will be open to suggestions/attempts in the future!
SirataXero said:
No problem! Glad that worked.
I can view system directories, and I read them as well. However, I definitely can't change anything and don't have write access either.
Will be open to suggestions/attempts in the future!
Click to expand...
Click to collapse
Sorry or the constant questions I downloaded a file explorer and im able to see more than before but i still have some files telling me i lack access.
What file explorer are you using?
abraham3991 said:
Sorry or the constant questions I downloaded a file explorer and im able to see more than before but i still have some files telling me i lack access.
What file explorer are you using?
Click to expand...
Click to collapse
I use Solid Explorer. So, some of the files you can physically see in the explorer, but if you try to open it, the text is garbled. It was only after I started doing adb pull that I could actually see/read the files themselves.