Related
I've read this thread: http://forum.xda-developers.com/showthread.php?t=570452
Actually, I've been using the same setup since the G1, and most recently with my Nexus One. Using those devices, when I start up my VirtualBox session and connect them to the PC, USB debugging mode starts and I can use ADB to connect to the device. As a point of reference, ADB also works from the Windows 7 host environment. What I cannot seem to get working is ADB with my Ubuntu 10.10 guest OS. I'm seeing the following in the dmesg log:
Code:
[ 453.061415] usb 1-1: new high speed USB device using ehci_hcd and address 2
[ 454.132202] usb 1-1: device descriptor read/64, error -32
[ 455.268177] usb 1-1: device descriptor read/64, error -32
[ 456.397201] usb 1-1: new high speed USB device using ehci_hcd and address 3
[ 457.440195] usb 1-1: device descriptor read/64, error -32
[ 458.560189] usb 1-1: device descriptor read/64, error -32
[ 459.684182] usb 1-1: new high speed USB device using ehci_hcd and address 4
[ 459.730509] usb 1-1: device descriptor read/8, error -32
[ 459.874823] usb 1-1: device descriptor read/8, error -32
[ 460.977314] usb 1-1: new high speed USB device using ehci_hcd and address 5
[ 461.042126] usb 1-1: device descriptor read/8, error -32
[ 461.186504] usb 1-1: device descriptor read/8, error -32
[ 461.288285] hub 1-0:1.0: unable to enumerate USB device on port 1
The VirtualBox USB driver looks like it is correctly installed on the host machine. Anyone have any idea?
Chinpokomon said:
I've read this thread: http://forum.xda-developers.com/showthread.php?t=570452
Actually, I've been using the same setup since the G1, and most recently with my Nexus One. Using those devices, when I start up my VirtualBox session and connect them to the PC, USB debugging mode starts and I can use ADB to connect to the device. As a point of reference, ADB also works from the Windows 7 host environment. What I cannot seem to get working is ADB with my Ubuntu 10.10 guest OS. I'm seeing the following in the dmesg log:
Code:
[ 453.061415] usb 1-1: new high speed USB device using ehci_hcd and address 2
[ 454.132202] usb 1-1: device descriptor read/64, error -32
[ 455.268177] usb 1-1: device descriptor read/64, error -32
[ 456.397201] usb 1-1: new high speed USB device using ehci_hcd and address 3
[ 457.440195] usb 1-1: device descriptor read/64, error -32
[ 458.560189] usb 1-1: device descriptor read/64, error -32
[ 459.684182] usb 1-1: new high speed USB device using ehci_hcd and address 4
[ 459.730509] usb 1-1: device descriptor read/8, error -32
[ 459.874823] usb 1-1: device descriptor read/8, error -32
[ 460.977314] usb 1-1: new high speed USB device using ehci_hcd and address 5
[ 461.042126] usb 1-1: device descriptor read/8, error -32
[ 461.186504] usb 1-1: device descriptor read/8, error -32
[ 461.288285] hub 1-0:1.0: unable to enumerate USB device on port 1
The VirtualBox USB driver looks like it is correctly installed on the host machine. Anyone have any idea?
Click to expand...
Click to collapse
may have something to do with the udev adress G1 and N1 where made by HTC using the same UDEV
slowz3r said:
may have something to do with the udev adress G1 and N1 where made by HTC using the same UDEV
Click to expand...
Click to collapse
That was my initial thought as well, but it doesn't look like it's getting that far. I looked and the vendorID already matches what I had in my udev rules. To me, this seems like Virtual Box isn't modeling the Nexus S correctly for some reason.
Chinpokomon said:
That was my initial thought as well, but it doesn't look like it's getting that far. I looked and the vendorID already matches what I had in my udev rules. To me, this seems like Virtual Box isn't modeling the Nexus S correctly for some reason.
Click to expand...
Click to collapse
weird, works perfect using VMware :/
I'm going to have do some serious shuffling. Android requires a 64-bit build environment now, but I use 32-bit Windows to work around driver signing issues. I think my best setup now will be a 64-bit Ubuntu host with a 32-bit Windows 7 guest... That's going to take some work. *sigh*
@Chinpokomon: did you get any solutions to fix this issue? Even i'm hving similar kind of issue. Past 2 days am trying to connect and list my Samsung Captivate Device in Ubuntu, but i failed everytime. Here is my environment
Launching Ubuntu 10.10 (guest OS) from Windows 7 (host OS) using Virtual Box 4.0
In the host OS (Windows 7), i have enabled USB Device Filter for Samsung_Android, and i could see that device in Ubuntu 10.10, but when i use 'lsusb', it doesn't list the samsung device. Any help would be greatly appreciated.
I never have used VBox but if its anything like VMware dont you have to disconnect the device from windows /connect it to VBox
Same here except for the error: -110 instead of -32.
I have three USB filters defined in VBox (product ID 4e20 = fastboot, 4e21 = debug disabled, 4e22 = debug enabled) and corresponding rules defined in /etc/udev/rules.d/51-android.rules
In fastboot mode this works perfectly fine. "fastbood devices" lists the device but when the Nexus S is in normal operation (no matter if debug enabled or disabled), it does not work.
"lsusb" lists the device in fastboot mode but in normal operation it takes a loooooong time and then does not list the Samsung device...
I switched udev to debog logging (/etc/udev/udev.conf -> udev_log="debug") but didn't get any additional logging details in /var/log/udev...
I took the time and recreated the VM using VMware player instead of VirtualBox (after reading the post from slowz3r) and I can confirm exactly the same setup works fine in VMware... It's neither a host nor a Ubuntu setup problem but it seems to be the VirtualBox USB support causing the issue with the NS in debug mode...
Moved to VMWare - works like charm
Hi there,
This is the ONLY thread I have found on the internet where people are actually talking about the same problem I am having. I tried for some days now to get this working, and so far no luck.
I posted a thread over at the VirtualBox forums regarding the issue. Check it out here: (apparently I couldn't post my link as this is my first post, but google "Google Nexus S USB redirection to guest fails" and you'll probably find it). If anyone have any further information on this issue, please post your findings in this thread. I don't like the solution "switch to VMware" though
Thanks in advance!
I try to use the new version of Heimdall but when starting to flash I had the following error:
Code:
Heimdall v1.3.0, Copyright (c) 2010-2011, Benjamin Dobell, Glass Echidna
This software is provided free of charge. Copying and redistribution is
encouraged.
If you appreciate this software and you would like to support future
development please consider donating:
Initialising connection...
Detecting device...
ERROR: Failed to access device. libusb error: -3
Is there anybody that could explain the problem ?
However my SGS-2 is detect in the utilities tab.
Thanks for your answers.
Django313 said:
I try to use the new version of Heimdall but when starting to flash I had the following error:
Code:
Heimdall v1.3.0, Copyright (c) 2010-2011, Benjamin Dobell, Glass Echidna
This software is provided free of charge. Copying and redistribution is
encouraged.
If you appreciate this software and you would like to support future
development please consider donating:
Initialising connection...
Detecting device...
ERROR: Failed to access device. libusb error: -3
Is there anybody that could explain the problem ?
However my SGS-2 is detect in the utilities tab.
Thanks for your answers.
Click to expand...
Click to collapse
Heimdall is flashing software? Why not use Odin?
As far as I understand Heimdall is for use on Galaxy S, not S2.
theo80 said:
Heimdall is flashing software? Why not use Odin?
As far as I understand Heimdall is for use on Galaxy S, not S2.
Click to expand...
Click to collapse
Because Heimdall is stable, reliable, open-source, cross-platform, allows for a large degree of flashing freedom and is guaranteed to be legal. None of these are true for Odin. Although not necessarily overly important Heimdall also flashes substantially faster.
Also as of 1.3.0 Heimdall Frontend now supports Heimdall Firmware Packages, which are by far a superior than attempting to flash several description-less tar archives with Odin.
EDIT: Heimdall works with all Galaxy S devices, except the Droid Charge, which we've had difficulties with. Which is another advantage over Odin; one version of Heimdall works with all devices so there's less confusion about versions.
Django313 said:
I try to use the new version of Heimdall but when starting to flash I had the following error:
Code:
Heimdall v1.3.0, Copyright (c) 2010-2011, Benjamin Dobell, Glass Echidna
This software is provided free of charge. Copying and redistribution is
encouraged.
If you appreciate this software and you would like to support future
development please consider donating:
Initialising connection...
Detecting device...
ERROR: Failed to access device. libusb error: -3
Is there anybody that could explain the problem ?
However my SGS-2 is detect in the utilities tab.
Thanks for your answers.
Click to expand...
Click to collapse
What OS are you running? If it's Windows make sure you follow the README and install the drivers.
@Benjamin Dobell
Yes, I use heimdall 1.3.0 on Kubuntu 11.04.
I read your e-mail and I try to launch Heimdall with sudo and it works !
but it's finished bad, resulting in a "half-bricked" SGS-2.
the flash of the datafs partition, when reaching 100% freeze and heimdall sent the error that it couldn't load datafs. ending the session...
I try twice flashing my phone:
- one with my own built heimdall-firmware-packages
- the other was custom flashing.
both failed.
The third flashing I made with odin in a virtualbox, and succeeded.
here is the results when launching Heimdall in a terminal :
Code:
[email protected]:~$ sudo heimdall-frontend
[sudo] password for didier:
Error: "/var/tmp/kdecache-didier" is owned by uid 1000 instead of uid 0.
QInotifyFileSystemWatcherEngine::addPaths: inotify_add_watch failed: Aucun fichier ou dossier de ce type
QFileSystemWatcher: failed to add paths: /home/didier/.config/ibus/bus
KGlobal::locale::Warning your global KLocale is being recreated with a valid main component instead of a fake component, this usually means you tried to call i18n related functions before your main component was created. You should not do that since it most likely will not work
Error: "/tmp/kde-didier" is owned by uid 1000 instead of uid 0.
Error: "/tmp/ksocket-didier" is owned by uid 1000 instead of uid 0.
kdeinit4: Shutting down running client.
Connecting to deprecated signal QDBusConnectionInterface::serviceOwnerChanged(QString,QString,QString)
Error: "/tmp/ksocket-didier" is owned by uid 1000 instead of uid 0.
Error: "/tmp/kde-didier" is owned by uid 1000 instead of uid 0.
Error: "/var/tmp/kdecache-didier" is owned by uid 1000 instead of uid 0.
kbuildsycoca4 running...
Error: "/var/tmp/kdecache-didier" is owned by uid 1000 instead of uid 0.
Error: "/var/tmp/kdecache-didier" is owned by uid 1000 instead of uid 0.
Error: "/var/tmp/kdecache-didier" is owned by uid 1000 instead of uid 0.
Error: "/tmp/ksocket-didier" is owned by uid 1000 instead of uid 0.
Error: "/var/tmp/kdecache-didier" is owned by uid 1000 instead of uid 0.
[email protected]:~$
Django313 said:
@Benjamin Dobell
Yes, I use heimdall 1.3.0 on Kubuntu 11.04.
I read your e-mail and I try to launch Heimdall with sudo and it works !
but it's finished bad, resulting in a "half-bricked" SGS-2.
the flash of the datafs partition, when reaching 100% freeze and heimdall sent the error that it couldn't load datafs. ending the session...
I try twice flashing my phone:
- one with my own built heimdall-firmware-packages
- the other was custom flashing.
both failed.
Click to expand...
Click to collapse
In regards to sudo permissions being required, I just did a bit of searching and I found some information (although it may have been old) that Kubuntu's udev rules are in a different location to Ubuntu's. I also found separate information indicating that Kubuntu is using an outdated udev rules specification. Either of these two things would cause the -3 permissions error without running Heimdall as a super user.
Do you know exactly what the error was you received from Heimdall when flashing failed? The output from Heimdall Frontend only contains the permissions errors and aren't related to the flashing process. When you use Heimdall Frontend, Heimdall's output is displayed in "Status" section of the "Flash" tab so that it can easily be copy and paste.
By the way if your phone gets stuck in a "half-bricked" state again then it can usually be fixed by going to the "Utilities" tab and running the "Close PC Screen" action. This doesn't repair any corrupted files on device (if there are any). This literally just tells the phone that it should at least try boot up, instead of displaying the phone <--> PC screen.
Help please
trying to run heimdall 1.3.0 on Mac OS 10.5.8, I have qt/xcode installed, still doesn't seem to work. everytime i run frontend and try to detect my device (samsung captivate)or save my .pit file I get "FRONTEND ERROR Heimdall crash"
Any suggestions ?
ERROR: Failed to access device. libusb error: -12
Win7 x64
Installed drivers:
Heimdall v1.3.0, Copyright (c) 2010-2011, Benjamin Dobell, Glass Echidna http://www.glassechidna.com.au
This software is provided free of charge. Copying and redistribution is
encouraged.
If you appreciate this software and you would like to support future
development please consider donating:
http://www.glassechidna.com.au/donate/
Initialising connection...
Detecting device...
Claiming interface...
Setting up interface...
Beginning session...
Handshaking with Loke...
Uploading PITERROR: Failed to send end session packet!
ERROR: Failed to send file part packet!
PIT upload failed!
Ending session...
Odin works, back to odin.
Problem with heimdall on mac 0s 10.5.8
Crappyvate said:
trying to run heimdall 1.3.0 on Mac OS 10.5.8, I have qt/xcode installed, still doesn't seem to work. everytime i run frontend and try to detect my device (samsung captivate)or save my .pit file I get "FRONTEND ERROR Heimdall crash"
Any suggestions ?
Click to expand...
Click to collapse
@benjamin
Problem solved after updating to osx 10.6
there seem to be issues between Heimdall 1.3 on Leopard 10.5 and certain binaries. Heimdall command line does not execute and just crashes.
I'm getting a similar error on Arch Linux running Heimdall v1.3.0 with my Fascinate:
Code:
Initialising connection...
Detecting device...
ERROR: Failed to access device. libusb error: 4
I do have the proper udev rules in place:
Code:
$ lsusb | grep Samsung
Bus 002 Device 068: ID 04e8:6601 Samsung Electronics Co., Ltd Mobile Phone
I couldn't get Heimdall to even detect the device on my MacBook Pro running 10.6.8. I don't have access to a Windows machine to do further testing, and have had a lot of issues trying to update pretty much anything on my phone after I rooted and put a Superclean ROM on a few months ago. Here's my current setup: pastie.org/2358372
Today I tried to flash my SGS-II with heimdall 1.3.0 on Linux Kubuntu 11.04.
I used the latest firmware XXKH3 and it failed as it did with the firmware XXKG6 few weeks ago. Just after it downloaded the file "datafs" it freeze resulting in a half-bricked phone.
Certainly there is a bug in heimdall at this point because all the others files are correctly downloaded.
the question is : why ?
I'm on Mac OsX 10.6.8, and after tried to flash my firmware using the downloaded PIT from my device, Heimdall told me that there were an error with libusb while it was trying to upload the PIT.
My SGS got semi-bricked, and after putting it to download mode again and unchecking Repartition in Heimdall, everything was fine with the flashing.
So, the question is... is there a bug with repartitioning? is it possible to use my device's PIT to repartition?
Need new bootloader for EPIC? How do I tell?
All, I picked up an EPIC from someone and they put DK28 on it which is a bit of a dead end. All searches turned up needing Odin and I don't have a Windows box. I then found Heimdall and then this thread here:
http://forum.xda-developers.com/showthread.php?t=1353310
This all looks promising but then I've read where I need to update the bootloader if I'm using a Mac. My question is, with an EPIC of somewhat unknown past, how do I know if I have the right bootloader on it? DK28 is the leaked Froyo that never got OTA'd. I want to get this EPIC back onto the OTA track so it can get Gingerbread. I've found CWM flashable images but the modem seems to be the biggest struggle. Of course, if Heimdall works, the thread above looks like it will get me all that I want.
So if anyone can help and tell me how to figure out if I've got the right bootloader and won't get the black screen problem, that would be cool.
thanks peterb
Need some help please
My device got messed up and I know nothing about using Linux or fixing partitions with ADB, I have the partition tables I need to fix it but I have no clue and no one in our community knows how to change the "head" sectors from four to ONE. Please this is my partition list from heimdal
Entry Count: 14
Unknown 1: 15718400
Unknown 2: 1
Unknown 3: 0
Unknown 4: 0
Unknown 5: 7703
Unknown 6: 237
Unknown 7: 62704
Unknown 8: 18
--- Entry #0 ---
Unused: No
Chip Identifier: 2 (Unused: %
s
)
Partition Identifier: 1
Partition Flags: 1 (R)
Unknown 1: 0
Partition Block Size: 256
Partition Block Count: 1
Unknown 2: 0
Unknown 3: 0
Partition Name: IBL+PBL
Filename: boot.bin
--- Entry #1 ---
Unused: No
Chip Identifier: 2 (Unused: %
s
)
Partition Identifier: 2
Partition Flags: 1 (R)
Unknown 1: 0
Partition Block Size: 256
Partition Block Count: 1
Unknown 2: 0
Unknown 3: 0
Partition Name: PIT
Filename: YPG70_8G-0304.pit
--- Entry #2 ---
Unused: No
Chip Identifier: 2 (Unused: %
s
)
Partition Identifier: 3
Partition Flags: 1 (R)
Unknown 1: 0
Partition Block Size: 256
Partition Block Count: 5
Unknown 2: 0
Unknown 3: 0
Partition Name: SBL
Filename: Sbl.bin
--- Entry #3 ---
Unused: No
Chip Identifier: 2 (Unused: %
s
)
Partition Identifier: 4
Partition Flags: 1 (R)
Unknown 1: 0
Partition Block Size: 256
Partition Block Count: 5
Unknown 2: 6226025
Unknown 3: 7143533
Partition Name: SBL2
Filename: Sbl.bin
--- Entry #4 ---
Unused: No
Chip Identifier: 2 (Unused: %
s
)
Partition Identifier: 5
Partition Flags: 1 (R)
Unknown 1: 0
Partition Block Size: 256
Partition Block Count: 20
Unknown 2: 0
Unknown 3: 0
Partition Name: PARAM
Filename: param.lfs
--- Entry #5 ---
Unused: No
Chip Identifier: 2 (Unused: %
s
)
Partition Identifier: 6
Partition Flags: 1 (R)
Unknown 1: 0
Partition Block Size: 256
Partition Block Count: 40
Unknown 2: 39021280
Unknown 3: 7143533
Partition Name: EFS
Filename: efs.rfs
--- Entry #6 ---
Unused: No
Chip Identifier: 2 (Unused: %
s
)
Partition Identifier: 7
Partition Flags: 1 (R)
Unknown 1: 0
Partition Block Size: 256
Partition Block Count: 30
Unknown 2: 36662408
Unknown 3: 0
Partition Name: KERNEL
Filename: zImage
--- Entry #7 ---
Unused: No
Chip Identifier: 2 (Unused: %
s
)
Partition Identifier: 8
Partition Flags: 1 (R)
Unknown 1: 0
Partition Block Size: 256
Partition Block Count: 30
Unknown 2: 6684793
Unknown 3: 3014771
Partition Name: RECOVERY
Filename: zImage
--- Entry #8 ---
Unused: No
Chip Identifier: 2 (Unused: %
s
)
Partition Identifier: 9
Partition Flags: 1 (R)
Unknown 1: 0
Partition Block Size: 256
Partition Block Count: 1160
Unknown 2: 0
Unknown 3: 0
Partition Name: FACTORYFS
Filename: factoryfs.rfs
--- Entry #9 ---
Unused: No
Chip Identifier: 2 (Unused: %
s
)
Partition Identifier: 10
Partition Flags: 1 (R)
Unknown 1: 0
Partition Block Size: 256
Partition Block Count: 536
Unknown 2: 6684780
Unknown 3: 115
Partition Name: DBDATAFS
Filename: dbdata.rfs
--- Entry #10 ---
Unused: No
Chip Identifier: 2 (Unused: %
s
)
Partition Identifier: 11
Partition Flags: 1 (R)
Unknown 1: 0
Partition Block Size: 256
Partition Block Count: 256
Unknown 2: 115
Unknown 3: 115
Partition Name: CACHE
Filename: cache.rfs
--- Entry #11 ---
Unused: No
Chip Identifier: 2 (Unused: %
s
)
Partition Identifier: 12
Partition Flags: 1 (R)
Unknown 1: 0
Partition Block Size: 256
Partition Block Count: 7696
Unknown 2: 0
Unknown 3: 0
Partition Name: DATAFS
Filename: datafs.rfs
--- Entry #12 ---
Unused: No
Chip Identifier: 2 (Unused: %
s
)
Partition Identifier: 13
Partition Flags: 1 (R)
Unknown 1: 0
Partition Block Size: 256
Partition Block Count: 20516
Unknown 2: 0
Unknown 3: 0
Partition Name: USERFS
Filename: userfs_8G.rfs
--- Entry #13 ---
Unused: No
Chip Identifier: 2 (Unused: %
s
)
Partition Identifier: 0
Partition Flags: 1 (R)
Unknown 1: 0
Partition Block Size: 0
Partition Block Count: 0
Unknown 2: 0
Unknown 3: 0
Partition Name: GANG
Filename: inand_8G.bin
Ending session...
Rebooting device...
Heyo guys, idk if this can be seen as somehow relate to this topic, cuz its a diff problem with heimdall than originally mentioned in this thread, but my problem is that while trying to flash twrp, my sm-a750fn got half-bricked, and odin didnt want to flash the phones stock ROM, beeing stuck at establishing a connection, so i went and tried to flash it via heimdall-frontend, without sudo cuz else id have issues with the pit not beeing recognised, and everytime i try to flash smth, no matter what .img, be it recovery, boot, misc, etc, heimdall gets stuck at 93% and later gets a fail msg:
"Heimdall v1.4.1
Copyright (c) 2010-2014 Benjamin Dobell, Glass Echidna
Glass Echidna
This software is provided free of charge. Copying and redistribution is
encouraged.
If you appreciate this software and you would like to support future
development please consider donating:
Donate | Glass Echidna
Initialising connection...
Detecting device...
Claiming interface...
Setting up interface...
Initialising protocol...
Protocol initialisation successful.
Beginning session...
Some devices may take up to 2 minutes to respond.
Please be patient!
Session begun.
Downloading device's PIT file...
PIT file download successful.
Uploading BOOT
0%
1%
2%
3%
4%
5%
[...]
80%
81%
82%
83%
84%
85%
86%
87%
88%
89%
90%
91%
92%
93%
ERROR: Failed to confirm end of file transfer sequence!
ERROR: BOOT upload failed!
Ending session...
ERROR: Failed to send end session packet!
Releasing device interface..."
The phone also shows like bout 45% of progress:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
i compiled heimdall fillowing these instructions on FC16:
http://www.sysadminworld.com/2012/compile-and-install-heimdall-on-fedora/
after that heimdall seems to work and detect my device (N7100)
Code:
# /usr/local/bin/heimdall detect
Device detected
but... actually trying to flash recovery.img i get an error the interface can't be claimed:
Code:
/usr/local/bin/heimdall flash --verbose --recovery recovery.img
Heimdall v1.4 RC1
...
Initialising connection...
Detecting device...
length: 18
device class: 2
S/N: 0
VID:PID: 04E8:685D
bcdDevice: 021B
iMan:iProd:iSer: 1:2:0
nb confs: 1
interface[0].altsetting[0]: num endpoints = 1
Class.SubClass.Protocol: 02.02.01
endpoint[0].address: 83
max packet size: 0010
polling interval: 09
interface[1].altsetting[0]: num endpoints = 2
Class.SubClass.Protocol: 0A.00.00
endpoint[0].address: 81
max packet size: 0200
polling interval: 00
endpoint[1].address: 02
max packet size: 0200
polling interval: 00
Claiming interface...
Attempt failed. Detaching driver...
Claiming interface again...
ERROR: Claiming interface failed!
then i also added the device to udev rules but it makes no difference.
then i proceded to install heimdall 1.3.1 FC16 RPM's from:
https://github.com/superweapons/Heimdall-fc/downloads#download_149229]
but still the same problem.
does anyone had anyluck using heimdall on fedora?
if so... how?
strange thing is..
on a different fedora 16 install this does not happen...
but then there is the problem of heimdall claiming it succesfully flashed an img, for example cwm recovery.img and after reboot it is still stock recovery..
I don't have any experience with fedora, but I would guess udev is similar. Perhaps you have something in your udev rules that conflicts with heimdall? I think highest number takes precedant, so grep 04e8 /udev/location/* and see if there are any conflicts. Do you also have a udev folder in /etc/ for user modded rules?
lsusb might offer some insight too.
gee one said:
I don't have any experience with fedora, but I would guess udev is similar. Perhaps you have something in your udev rules that conflicts with heimdall? I think highest number takes precedant, so grep 04e8 /udev/location/* and see if there are any conflicts. Do you also have a udev folder in /etc/ for user modded rules?
lsusb might offer some insight too.
Click to expand...
Click to collapse
i already added a custom rule in /etc/udev/rules.d/51-android.rules but now scanning through the compile output i see that wasn't neccesary since it created rules in lib/udev/rules.d which contain the same rule with the id of the N7100:
Code:
/usr/bin/install -c -m 644 60-heimdall-galaxy-s.rules '/lib/udev/rules.d'
maybe stracing heimdall might clear things up...
will try that later
have compiled a driver for the tablet P3110, but then
ifconfig wlan0 up
<4>[58561.661071] C1 [ ifconfig]
<4>[58561.661102] C1 [ ifconfig] Dongle Host Driver, version 1.15.11
<4>[58561.661132] C1 [ ifconfig] Compiled in drivers/net/wireless/bcmdhd/src on Nov 27 2013 at 18:58:47
<4>[58562.437103] C0 [ ifconfig] dhdsdio_htclk: HT Avail timeout (1000000): clkctl 0x50
<4>[58562.437133] C0 [ ifconfig] dhd_bus_init: clock state is wrong. state = 1
<4>[58562.437255] C0 [ ifconfig] dhd_bus_start failed bus is not ready
What's the problem?
I'm interested in this topic, been wanting to do this with this tablet as well.
Subscribed!
Please make works that driver , monitor mode
Following
Help!!!!
This driver and bin files for CM_10.2 (Galaxy TAB 3110), but when I do:
insmod ./dhd.ko iface_name=wlan0 firmware_path=./bcm4330_sta.bcmon.bin nvram_path=/system/etc/wifi/nvram_net.txt
lsmod
dhd 392776 0 - Live 0x00000000
pvrsrvkm_sgx540_120 385106 60 - Live 0x00000000
ifconfig wlan0 up
error: SIOCSIFFLAGS (Operation not permitted)
Any ideas? So far I've tried hiemdall, Jodin (which is friggen awesome) and towell apk.
Bottum line seems to be that I can't get access to the PIT.
Procedures up to this point: Dowload necesary images. Put phone into usb debug mode. Put phone into download mode and plug in. USB.
Q: Does it matter hat version of USB? I have both types of ports but was using the 3.0 at the time. I'll see if trying it on 2.0 has any effect.
A: It does change things but not for the better. On USB 2.0, the device is not even detected. Interesting.
Idea: The box in question is a custom built water-cooled war machine for gaming. I'll give this a try on my System76 laptop and see if results are different.
Output from hiemdall looks like this:
Code:
[email protected]:~$ sudo heimdall download-pit --output GalaxyNote4.pit --verbose --delay 50000
Heimdall v1.4.0
Copyright (c) 2010-2013, Benjamin Dobell, Glass Echidna
http://www.glassechidna.com.au/
This software is provided free of charge. Copying and redistribution is
encouraged.
If you appreciate this software and you would like to support future
development please consider donating:
http://www.glassechidna.com.au/donate/
Initialising connection...
Detecting device...
Manufacturer: "Sasmsung"
Product: "MSM8960"
length: 18
device class: 2
S/N: 0
VID:PID: 04E8:685D
bcdDevice: 0100
iMan:iProd:iSer: 1:2:0
nb confs: 1
interface[0].altsetting[0]: num endpoints = 1
Class.SubClass.Protocol: 02.02.01
endpoint[0].address: 82
max packet size: 0010
polling interval: 09
interface[1].altsetting[0]: num endpoints = 2
Class.SubClass.Protocol: 0A.00.00
endpoint[0].address: 81
max packet size: 0200
polling interval: 00
endpoint[1].address: 01
max packet size: 0200
polling interval: 00
Claiming interface...
Setting up interface...
Initialising protocol...
WARNING: Control transfer #1 failed. Result: -9
WARNING: Control transfer #2 failed. Result: -9
WARNING: Control transfer #3 failed. Result: -9
WARNING: Control transfer #4 failed. Result: -9
WARNING: Control transfer #5 failed. Result: -9
WARNING: Control transfer #6 failed. Result: -9
ERROR: Failed to receive handshake response. Retrying...
[email protected]:
jcllings said:
Any ideas? So far I've tried hiemdall, Jodin (which is friggen awesome) and towell apk.
Bottum line seems to be that I can't get access to the PIT.
Procedures up to this point: Dowload necesary images. Put phone into usb debug mode. Put phone into download mode and plug in. USB.
Q: Does it matter hat version of USB? I have both types of ports but was using the 3.0 at the time. I'll see if trying it on 2.0 has any effect.
A: It does change things but not for the better. On USB 2.0, the device is not even detected. Interesting.
Idea: The box in question is a custom built water-cooled war machine for gaming. I'll give this a try on my System76 laptop and see if results are different.
Output from hiemdall looks like this:
Code:
[email protected]:~$ sudo heimdall download-pit --output GalaxyNote4.pit --verbose --delay 50000
Heimdall v1.4.0
Copyright (c) 2010-2013, Benjamin Dobell, Glass Echidna
http://www.glassechidna.com.au/
This software is provided free of charge. Copying and redistribution is
encouraged.
If you appreciate this software and you would like to support future
development please consider donating:
http://www.glassechidna.com.au/donate/
Initialising connection...
Detecting device...
Manufacturer: "Sasmsung"
Product: "MSM8960"
length: 18
device class: 2
S/N: 0
VID:PID: 04E8:685D
bcdDevice: 0100
iMan:iProd:iSer: 1:2:0
nb confs: 1
interface[0].altsetting[0]: num endpoints = 1
Class.SubClass.Protocol: 02.02.01
endpoint[0].address: 82
max packet size: 0010
polling interval: 09
interface[1].altsetting[0]: num endpoints = 2
Class.SubClass.Protocol: 0A.00.00
endpoint[0].address: 81
max packet size: 0200
polling interval: 00
endpoint[1].address: 01
max packet size: 0200
polling interval: 00
Claiming interface...
Setting up interface...
Initialising protocol...
WARNING: Control transfer #1 failed. Result: -9
WARNING: Control transfer #2 failed. Result: -9
WARNING: Control transfer #3 failed. Result: -9
WARNING: Control transfer #4 failed. Result: -9
WARNING: Control transfer #5 failed. Result: -9
WARNING: Control transfer #6 failed. Result: -9
ERROR: Failed to receive handshake response. Retrying...
[email protected]:
Click to expand...
Click to collapse
I don't have your device, so I'm not an expert about it.
But I found a guide how to root a similar device (Note 2) ... also for Linux: Galaxy Note 2 Root Tutorials! [Windows/Mac/Linux].
And if you know how to flash something to your device on linux, you can use the easiest rooting method IMO: [SM-N910*] CF-Auto-Root.
If you have further questions about your device, just ask in the T-Mobile Galaxy Note 4 Q&A, Help & Troubleshooting forum.
Thread closed and thank you.