hi, i'm trying to downgrade my htcdesire so i can root it.(is it necesarry to downgrade for rooting?)
but it doesnt work for me:
- i format my sd in my phone (fat32)
- i set my phone on "usb debugging"
- connect my phone+sd
- i set my phone on "diskdrive"
- i run goldcardtool as admin.
- i press "get cid (mmc1 & mmc0) "
- this error:
Executing adb shell cat /sys/class/mmc_host/mmc0/mmc0:*/cid
Reading adb output
------------------------
* daemon not running. starting it now *
* daemon started successfully *
------------------------
Could not locate CID in output
-----------------------------------
what did i wrong?
i've tryd it with 2 sd cards.
in what mode did i have to set my phone? (wen usb debugging on & phone connected to pc)
-charge only
- diskdrive
-htc sync
- usb tethering
Ermmm... this is the HTC Legend forum, please post your question on the designated sections.
Sent from my Legend using xda premium
but i have a htc legend? or is this problem not "legend-related"?
You are asking about an HTC Desire in your OP. This is the Legend forum.
Has anyone managed to connect their S2 using MTP when running Ubuntu? Obviously I know that it's a very simple tast to just connect via mass storage instead, but I'm interested to know.
I think that Samsung have some weird implementation of MTP because I was able to connect and copy files when I was running CM9 but not on stock ICS. I always get the error message:
Unable to mount SAMSUNG_Android
Error initialising camera: -60: Could not lock the device
Though it does mount and I can see the root of both SDCards, all the folders are empty and I can't copy any files to the cards from the computer as I get a error message reading:
There was an error copying the file into gphoto2://[usb:001,010]/store_00020002.
The same happens whether I try to use MTP or PTP.
I think the problem lies in that libmtp-1.1.3 contains fixes for the S2 but that version isn't included with 11.10 or 12.04
hint
did you find out,
i got mine working by doing below guide,
think the issue is we have our phones in USB Debugging Mode
ubuntuforums.org/archive/index.php/t-1806119.html
Steps:
1. Go to: Settings ➔ Wireless and network ➔ USB utilities.
2. Connect your phone to your PC using a USB cable.
3. Tap Connect storage to PC.
4. Scroll down from the phone notification bar. Click USB Mass Storage and tap "Connect storage from PC". The android robot will turn from green to orange. (Important step!)
5. From your PC, open the folder to view your files.
6. Copy files between your PC and the memory card.
alpike said:
did you find out,
i got mine working by doing below guide,
think the issue is we have our phones in USB Debugging Mode
ubuntuforums.org/archive/index.php/t-1806119.html
Steps:
1. Go to: Settings ➔ Wireless and network ➔ USB utilities.
2. Connect your phone to your PC using a USB cable.
3. Tap Connect storage to PC.
4. Scroll down from the phone notification bar. Click USB Mass Storage and tap "Connect storage from PC". The android robot will turn from green to orange. (Important step!)
5. From your PC, open the folder to view your files.
6. Copy files between your PC and the memory card.
Click to expand...
Click to collapse
That's connecting via USB mass storage, not mtp. But thanks for trying.
Sent from my GT-I9100 using XDA
Very easy
Code:
cd ~
sudo apt-get install mtpfs
sudo mkdir /mtp
sudo chmod 775 /mtp
sudo mtpfs -o allow_other /mtp
For dismount
Code:
sudo umount mtpfs
You need to have your device rules ( Check how to install adb if you dont )
what I have found out that mtpfs is unable to preserve timestamps of the files at least on my install.
gphoto2 backend worked fine on CM9 now wile testing CM10 its a bit buggy, I can get the list of files but I am unable to read or rename them.
Most likelly it will improve as development of CM10 progresses rapidly.
Mounting my Galaxy S3 when connected via USB to my Ubuntu computer
D4rKn3sSyS said:
Very easy
Code:
cd ~
sudo apt-get install mtpfs
sudo mkdir /mtp
sudo chmod 775 /mtp
sudo mtpfs -o allow_other /mtp
For dismount
Code:
sudo umount mtpfs
You need to have your device rules ( Check how to install adb if you dont )
Click to expand...
Click to collapse
I went through the steps above, except the last: How do I install adb? (device rules ?).
While my phone is so connected, the command:
cd /mtp
produces the result
bash: cd: /mtp: Transport endpoint is not connected
Help greatly appreciated.
Thank you,
-- Saul
slubkin said:
I went through the steps above, except the last: How do I install adb? (device rules ?).
While my phone is so connected, the command:
cd /mtp
produces the result
bash: cd: /mtp: Transport endpoint is not connected
Help greatly appreciated.
Thank you,
-- Saul
Click to expand...
Click to collapse
Ubuntu 13.04 is a drastic improvement for MTP support. I have not got around to trying my S II but I successfully managed a family friends Galaxy TAB 2 with MTP with zero manual modifications to Ubuntu. Everything worked perfect plug and play out of the box.
I have also tried old versions to know how bad they were compared to 13.04.
No luck with S2 and Ubuntu 13.04
I'm on Android 4.1.2 and trying to connect via USB to Ubuntu 13.04. Error I get is that my device is not an MTP device, which it's not as its using USB
Issue is that I don't see the mounted android partitions. To make this worse, it works every now and then. Following is the syslog and the outpu of lsusb
-----------------------------------------------------------------------------------------------------------------------------------------------------------------
Aug 26 23:04:00 ml kernel: [134718.425536] usb 1-5: new high-speed USB device number 11 using ehci-pci
Aug 26 23:04:00 ml kernel: [134718.558636] usb 1-5: New USB device found, idVendor=04e8, idProduct=685b
Aug 26 23:04:00 ml kernel: [134718.558647] usb 1-5: New USB device strings: Mfr=2, Product=3, SerialNumber=4
Aug 26 23:04:00 ml kernel: [134718.558655] usb 1-5: Product: SAMSUNG_Android
Aug 26 23:04:00 ml kernel: [134718.558661] usb 1-5: Manufacturer: SAMSUNG
Aug 26 23:04:00 ml kernel: [134718.558666] usb 1-5: SerialNumber: 001964815b817e
Aug 26 23:04:05 ml kernel: [134723.546077] usb 1-5: can't set config #1, error -110
Aug 26 23:04:05 ml mtp-probe: checking bus 1, device 11: "/sys/devices/pci0000:00/0000:00:12.2/usb1/1-5"
Aug 26 23:04:05 ml mtp-probe: bus: 1, device: 11 was not an MTP device
[email protected]:~$ lsusb
Bus 001 Device 011: ID 04e8:685b Samsung Electronics Co., Ltd GT-I9100 Phone [Galaxy S II] (mass storage mode)
Bus 003 Device 002: ID 046d:c52e Logitech, Inc.
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
After connecting the phone via usb cable, "adb devices" command lists :
$ adb devices
List of devices attached
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
FA3BSWG00401 offline
1) First time it asked whether to trust this computer and I checked 'always trust this computer'. Is there a way to untrust a specific computer / make it ask again ?
2) plugging the cable to my older SGS3 works fine :
$ adb devices
List of devices attached
4df1d4650790afdf device
Has anybody encountered this before ?
Additional info :
$ adb version
Android Debug Bridge version 1.0.32
Revision 57224c5cff69-android
I'm using Linux Mint 17.2, NuSense 6 (Lolipop)
Intro-
This is the stock kernel for the T-Mobile SM-P607T Samsung Note 10.1 (2014 Edition) with the following additional features:
Multiple flavors for SELinux preference
CIFS kernel support
NFS kernel support
Force Fast Charge support
Download Options-
Enforcing ONLY - http://files.zpivot.com/sm-p607t/p607t-zstock-kernel-enforcing-only-1.2.37.tar.md5
SELinux stock behavior, always enforcing
Permissive OPTIONAL - http://files.zpivot.com/sm-p607t/p607t-zstock-kernel-permissive-optional-1.2.37.tar.md5
SELinux mode can be change with setenforce command
Permissive ONLY - http://files.zpivot.com/sm-p607t/p607t-zstock-kernel-permissive-only-1.2.37.tar.md5
SELinux always permissive
Install-
Reboot into download mode
Open ODIN
Add the kernel file downloaded from link above to AP section
Click start!
How to mount cifs/smb shares-
REQUIREMENTS:
root
busybox
ability to read and follow directions
custom kernel with cifs support (ie the kernel above)
INSTRUCTIONS:
Open a terminal emulator or adb shell
Code:
su
Code:
mkdir /mnt/shares/*share_name*
Code:
busybox mount -t cifs -o username=guest,unc=\\\\*server_ip*\\*share_name*,ip=*server_ip* *server_ip*/*share_name* /mnt/shares/*share_name*
NOTES:
Make sure you replace *server_ip* in the instructions above with the ip address of your server, and *share_name* with the name of your shared folder.
You must mount your shares outside of /storage and /mnt/sdcard for all applications to have access. I have provided a public tmpfs for creating mount points at /mnt/shares.
---Your samba share will now be accessible by all programs/apps under the /mnt/shares directory on root.
How to use Force Fast Charge-
DISPLAY FORCE FAST CHARGE INFO:
Open a terminal emulator or adb shell
Code:
cat /sys/kernel/fast_charge/info
ENABLE FORCE FAST CHARGE MODE:
Open a terminal emulator or adb shell
Code:
su
Code:
echo 1 > /sys/kernel/fast_charge/force_fast_charge
SET CUSTOM FORCE FAST CHARGE LEVELS:
Open a terminal emulator or adb shell
Code:
su
Code:
echo 2 > /sys/kernel/fast_charge/force_fast_charge
Code:
echo 1000 > /sys/kernel/fast_charge/usb_charge_level
Code:
echo 2100 > /sys/kernel/fast_charge/ac_charge_level
NOTES:
Force Fast Charge will be disabled by default
When setting custom levels for usb and ac force fast charge, use one of the available values listed when using the display info command above (in the examples I used the max values)
Additional info:
Code:
/*
* Forced Fast Charge - SysFS interface :
* --------------------------------------
*
* /sys/kernel/fast_charge/force_fast_charge (rw)
*
* 0 - disabled (default)
* 1 - substitute AC to USB
* 2 - use custom mA configured through sysfs interface (see below)
*
* /sys/kernel/fast_charge/ac_charge_level (rw)
*
* rate at which to charge when on AC (1.0A/h to 2.1A/h)
*
* /sys/kernel/fast_charge/usb_charge_level (r/w)
*
* rate at which to charge when on USB (0.460A/h to 1.0A/h)
*
* /sys/kernel/fast_charge/wireless_charge_level (r/w)
*
* rate at which to charge when on WIRELESS (0.650A/h to 1.2A/h)
*
* /sys/kernel/fast_charge/failsafe (rw)
*
* 0 - disabled - allow anything up to 2.1A/h to be used as AC / USB custom current
* 1 - enabled - behaviour as described above (default)
*
* /sys/kernel/fast_charge/ac_levels (ro)
*
* display available levels for AC (for failsafe enabled mode)
*
* /sys/kernel/fast_charge/usb_levels (ro)
*
* display available levels for USB (for failsafe enabled mode)
*
* /sys/kernel/fast_charge/wireless_levels (ro)
*
* display available levels for WIRELESS (for failsafe enabled mode)
*
* /sys/kernel/fast_charge/version (ro)
*
* display fast charge version information
*
* /sys/kernel/fast_charge/info (ro)
*
* display complete fast charge configuration in human readable format
*
*/
Changelog
v1.0 - Initial release
v1.1 - Added Enforcing only version (build 21)
v1.2 - Added Force Fast Charge support (build 37)
Thanks/Credits-
mkasick - CIFS/NFS empty mount patch - http://forum.xda-developers.com/showthread.php?t=2106480
blue cat - permissive only patch - http://forum.xda-developers.com/galaxy-note-10-2014/development/kernel-stock-selinux-permissive-kernel-t3232814
chad0989 - force fast charge initial work - http://forum.xda-developers.com/galaxy-nexus/verizon-develop/kernel-patch-devs-force-ac-fast-charging-t1524020
faux123 - force fast charge extensions
yank555-lu - force fast charge note 3 port
Just a question - do you know how to add charging at different voltages? It drives me crazy that our tab can only charge at 1.8V, no more, no less.
Sent from my LG-H818 using Tapatalk
itsita said:
Just a question - do you know how to add charging at different voltages? It drives me crazy that our tab can only charge at 1.8V, no more, no less.
Sent from my LG-H818 using Tapatalk
Click to expand...
Click to collapse
I do not know how to adjust the voltage used for charging. Although you did give me an idea to implement the force fast charging kernel mod. I am currently building a test release with the added patches... let the experiments begin!!!
Updated OP
Okay, I have updated the OP and added a new version with the force fast charge mod in place. I have only done minor testing to make sure the code was functional. I would suggest that you perform your own testing as your mileage may vary depending on the charging equipment you are using.
oneleft.ak said:
Okay, I have updated the OP and added a new version with the force fast charge mod in place. I have only done minor testing to make sure the code was functional. I would suggest that you perform your own testing as your mileage may vary depending on the charging equipment you are using.
Click to expand...
Click to collapse
Thanks! Ill test and post results
Sent from my SM-P605 using Tapatalk
I am getting "md5 error! invalid binary " while adding the kernel file through odin..
plz guide
i have 607T with 5.1.1
tabi304 said:
I am getting "md5 error! invalid binary " while adding the kernel file through odin..
plz guide
i have 607T with 5.1.1
Click to expand...
Click to collapse
This will happen when you change the filename before attempting to flash or if the download completed with errors. Make sure you are trying to flash the file from one of the download links in the OP.
oneleft.ak said:
This will happen when you change the filename before attempting to flash or if the download completed with errors. Make sure you are trying to flash the file from one of the download links in the OP.
Click to expand...
Click to collapse
hmm i'm getting the invalid binary message as well,
tried different odins and different files (didn't change the name or anything..)
I also tried different odin versions but no success
File server error
tabi304 said:
I also tried different odin versions but no success
Click to expand...
Click to collapse
I see what you mean, it appears my file server is altering the file size upon upload.... I am looking into it right now- Will update this thread once it has been corrected.
UPDATE:
Okay, turns out it was the ftp program(FileZilla) I was using to upload the files to my file server. The files have been restored correctly and I have personally tested all three of the links by downloading from my file server and flashing in ODIN.
Thanks for the heads up guys and please let me know if you run into any further issues--
itsita said:
hmm i'm getting the invalid binary message as well,
tried different odins and different files (didn't change the name or anything..)
Click to expand...
Click to collapse
Maybe now you can finally get the chance to test the force fast charge options!!!
Is this kernel valid for P605 too? Surely not, but just asking....
How do you root the P607T? Also, whats the difference (in laymens terms) between the 3 versions?
Worked well thank you
Set my levels to this - hopefully it speeds up the charge a little
Fast charge mode : 2 - Use custom mA on AC and USB
Custom AC level : 2100mA/h
Custom USB level : 1000mA/h
Custom Wireless level : 650mA/h
Failsafe mode : 1 - Failsafe active (default)
Valid AC levels : 1000 1100 1200 1300 1400 1500 1600 1700 1800 1900 2000 2100
Valid USB levels : 460 500 600 700 800 900 1000
Valid Wireless levels : 650 800 900 1000 1100 1200
I flashed the kernel from here, and followed the steps, when i go to check /sys/kernel/fast_charge/info to see if it worked, all i get is permission denied.
no matter what kernel ive used in the past on this tablet ive gotten "permission denied" like trying to set up linux deploy or linux on android. I am rooted, I am using a Permissive kernel, Busy Box installed. So what gives?
Can this be used in P605 ? TY !!
Istarth said:
Can this be used in P605 ? TY !!
Click to expand...
Click to collapse
Yes. It was also the kernel inside Pyrana v27.
zombie thread warning*
So as i understand it, you can use kernels for older roms on newer releases right?
So for example, im trying out an unofficial lineage os rom, and it does not have fast charge support baked in, nothing through kernel auditor or 3c toolbox that can be changed. Could I flash this kernel and add support to the rom that way? The dinosaur charging speeds on this thing is really inconvenient if I ever forget to charge it overnight.
Please, links down.