[Q] Problem with Heimdall - General Questions and Answers
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"
}
Related
EE4 Radio/Baseband
Has anybody got just the EE4 Baseband/Radio Update? I have searched to no end, and can't find it. Thanks!
Question. Post in general Sent from my SCH-I510 using XDA Premium App
AFAIK, There is no modem file you can flash. You have to apply the OTA update to get it. There is currently no way to pull the modem off the phone, and what is in the OTA is not a complete modem file and cannot be flashed in odin.
Check out this thread: http://forum.xda-developers.com/showthread.php?p=14644392 If the guy's PIT reading is correct, we should be able to pull an EE4 radio for you that could be flashed with Odin. I'd be happy to pull and post, but I think there's a large risk of losing radio function for an unknown time if the concept is wrong, since there's nothing out there to correct it with. The risk of flashing with Odin would be entirely on you. Hope that's more helpful than not.
distortedloop said: Check out this thread: http://forum.xda-developers.com/showthread.php?p=14644392 If the guy's PIT reading is correct, we should be able to pull an EE4 radio for you that could be flashed with Odin. I'd be happy to pull and post, but I think there's a large risk of losing radio function for an unknown time if the concept is wrong, since there's nothing out there to correct it with. The risk of flashing with Odin would be entirely on you. Hope that's more helpful than not. Click to expand... Click to collapse It helps, thanks! I'd forgotten how hard Samsung's were to flash radio's, it's so much easier with HTC phones! If you or anybody ends up being able to do it, that'd be awesome! I assume I can't just flash the EE4 update over Gummy's 1.5 ROM to get the new radio, or can I?
danalo1979 said: Question. Post in general Sent from my SCH-I510 using XDA Premium App Click to expand... Click to collapse Too late, it's already here If the mods want to move it, they can, no worries!
californiarailroader said: It helps, thanks! I'd forgotten how hard Samsung's were to flash radio's, it's so much easier with HTC phones! If you or anybody ends up being able to do it, that'd be awesome! I assume I can't just flash the EE4 update over Gummy's 1.5 ROM to get the new radio, or can I? Click to expand... Click to collapse Actually, it's not any harder on Sammies, in my opinion, it's just we don't have a released radio to flash. Odin or fastboot flash, not too much difference, other than the hassles of getting Odin to work if you're on a Mac. In theory, you could modify the update file to just patch the radio and not do the rest. Also, since it's a patch, you have to have on the phone what it expects to be patching or you'd end up with a big mess if you bypassed that safety check in the updater-script. The problem is that stock recovery won't run it once you mod it because it won't pass the signature (we have the 3e recovery, the old v2 didn't check) check. I think I read somewhere that CWR wouldn't run it either. It's a hassle, but the best thing right now would be backup with Titanium, flash stock ED2, then apply the EE4 update, then flash your Gummy, restore your backup.
distortedloop said: Actually, it's not any harder on Sammies, in my opinion, it's just we don't have a released radio to flash. Odin or fastboot flash, not too much difference, other than the hassles of getting Odin to work if you're on a Mac. In theory, you could modify the update file to just patch the radio and not do the rest. Also, since it's a patch, you have to have on the phone what it expects to be patching or you'd end up with a big mess if you bypassed that safety check in the updater-script. The problem is that stock recovery won't run it once you mod it because it won't pass the signature (we have the 3e recovery, the old v2 didn't check) check. I think I read somewhere that CWR wouldn't run it either. It's a hassle, but the best thing right now would be backup with Titanium, flash stock ED2, then apply the EE4 update, then flash your Gummy, restore your backup. Click to expand... Click to collapse Thanks, I think that's probably the best way too, either that or wait for the radio, which might take a while.
http://forum.xda-developers.com/showthread.php?t=1108885&highlight=stock+ed2 Is that the right ED2 to flash?
distortedloop said: Check out this thread: http://forum.xda-developers.com/showthread.php?p=14644392 If the guy's PIT reading is correct, we should be able to pull an EE4 radio for you that could be flashed with Odin. I'd be happy to pull and post, but I think there's a large risk of losing radio function for an unknown time if the concept is wrong, since there's nothing out there to correct it with. The risk of flashing with Odin would be entirely on you. Hope that's more helpful than not. Click to expand... Click to collapse Btw i had pulled the pit info by using hiemdall print-pit. I've got the full pit on my laptop. But am mobile atm. Sent from my SCH-I510 using XDA Premium App
Okay, I disabled the lagfix, then flashed stock ED2, but when I try to download the EE4 update it keeps failing, is Samsung having problems or did I do something wrong?
Nevermind, all fixed
c0ns0le said: Btw i had pulled the pit info by using hiemdall print-pit. I've got the full pit on my laptop. But am mobile atm. Sent from my SCH-I510 using XDA Premium App Click to expand... Click to collapse Pulling the PIT is one of the few things I can do reliable with Heimdall. I still have a copy in my terminal buffer from while I was trying to upgrade to EE4 from stock ED1. Problem is I haven't bothered to try to figure out how to translate it into a dd command. Could probably figure it out, some of it's very obvious, but any info on the translation would be appreciated: Code: MBP1:~ dave$ heimdall print-pit Heimdall v1.0.2b, Copyright (c) 2010-2011, Benjamin Dobell, Glass Echidna http://www.glassechidna.com.au Claiming interface... Success Setting up interface... Success Beginning session... Handshaking with Loke... Success Downloading device's PIT file... PIT file download sucessful Entry Count: 14 Unknown 1: 16898048 Unknown 2: 1 Unknown 3: 0 Unknown 4: 0 Unknown 5: 7703 Unknown 6: 255 Unknown 7: 62464 Unknown 8: 22 --- Entry #0 --- Unused: No Partition Type: 0 (RFS) Partition Identifier: 0 Partition Flags: 0 (R) Unknown 2: 0 Partition Block Size: 256 Partition Block Count: 1 Unknown 3: 6684783 Unknown 4: 2097268 Partition Name: IBL+PBL Filename: boot.bin --- Entry #1 --- Unused: No Partition Type: 0 (RFS) Partition Identifier: 1 Partition Flags: 0 (R) Unknown 2: 0 Partition Block Size: 256 Partition Block Count: 1 Unknown 3: 0 Unknown 4: 0 Partition Name: PIT Filename: --- Entry #2 --- Unused: No Partition Type: 0 (RFS) Partition Identifier: 20 Partition Flags: 2 (R/W) Unknown 2: 0 Partition Block Size: 256 Partition Block Count: 40 Unknown 3: 0 Unknown 4: 0 Partition Name: EFS Filename: efs.rfs --- Entry #3 --- Unused: No Partition Type: 0 (RFS) Partition Identifier: 13 Partition Flags: 1 (R) Unknown 2: 0 Partition Block Size: 256 Partition Block Count: 12 Unknown 3: 0 Unknown 4: 0 Partition Name: EFS2 Filename: nvblock.bin --- Entry #4 --- Unused: No Partition Type: 0 (RFS) Partition Identifier: 3 Partition Flags: 0 (R) Unknown 2: 0 Partition Block Size: 256 Partition Block Count: 5 Unknown 3: 0 Unknown 4: 0 Partition Name: SBL Filename: sbl.bin --- Entry #5 --- Unused: No Partition Type: 0 (RFS) Partition Identifier: 4 Partition Flags: 0 (R) Unknown 2: 0 Partition Block Size: 256 Partition Block Count: 5 Unknown 3: 0 Unknown 4: 0 Partition Name: SBL2 Filename: sbl.bin --- Entry #6 --- Unused: No Partition Type: 0 (RFS) Partition Identifier: 21 Partition Flags: 2 (R/W) Unknown 2: 0 Partition Block Size: 256 Partition Block Count: 20 Unknown 3: 0 Unknown 4: 0 Partition Name: PARAM Filename: param.lfs --- Entry #7 --- Unused: No Partition Type: 0 (RFS) Partition Identifier: 6 Partition Flags: 0 (R) Unknown 2: 0 Partition Block Size: 256 Partition Block Count: 30 Unknown 3: 0 Unknown 4: 0 Partition Name: KERNEL Filename: zImage --- Entry #8 --- Unused: No Partition Type: 0 (RFS) Partition Identifier: 7 Partition Flags: 0 (R) Unknown 2: 0 Partition Block Size: 256 Partition Block Count: 30 Unknown 3: 0 Unknown 4: 0 Partition Name: RECOVERY Filename: recovery.bin --- Entry #9 --- Unused: No Partition Type: 0 (RFS) Partition Identifier: 22 Partition Flags: 2 (R/W) Unknown 2: 0 Partition Block Size: 256 Partition Block Count: 1380 Unknown 3: 0 Unknown 4: 0 Partition Name: FACTORYFS Filename: factoryfs.rfs --- Entry #10 --- Unused: No Partition Type: 0 (RFS) Partition Identifier: 23 Partition Flags: 2 (R/W) Unknown 2: 0 Partition Block Size: 256 Partition Block Count: 430 Unknown 3: 0 Unknown 4: 0 Partition Name: DBDATAFS Filename: dbdata.rfs --- Entry #11 --- Unused: No Partition Type: 0 (RFS) Partition Identifier: 11 Partition Flags: 0 (R) Unknown 2: 0 Partition Block Size: 256 Partition Block Count: 48 Unknown 3: 0 Unknown 4: 0 Partition Name: LTEMODEM Filename: lte_modem.bin --- Entry #12 --- Unused: No Partition Type: 0 (RFS) Partition Identifier: 12 Partition Flags: 0 (R) Unknown 2: 0 Partition Block Size: 256 Partition Block Count: 2 Unknown 3: 0 Unknown 4: 0 Partition Name: CPMODEM Filename: cp_modem.bin --- Entry #13 --- Unused: No Partition Type: 2 (EXT4) Partition Identifier: 0 Partition Flags: 1 (R) Unknown 2: 0 Partition Block Size: 0 Partition Block Count: 0 Unknown 3: 7602273 Unknown 4: 7274601 Partition Name: MOVINAND Filename: movinand.bin Ending session... Rebooting device...
[Q] heimdall 1.4 on fedora problems
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
[Q] No MBR found after flashing image files into a board
I have a Samsung development board. After flash ICS images files into internal storage, at first time it can boot to android animation but failed to go to launcher; when i boot it again, it report 'NO MBR is found at SD/MMC', and can not be flashed. I use MMC command to create the partition and flash it, same error occurs. u-boot log is: reading kernel device 0 Start 6144, Count 10240 mmc read 0 0x40008000 6144 10240 MMC read: dev # 0, block # 6144, count 10240 ... there are pending interrupts 0x00000008 error during transfer: 0x00008024 mmc read failed -1 blocks read: ERROR completed reading ramdisk device 0 Start 16384, Count 10240 mmc read 0 0x41000000 16384 10240 MMC read: dev # 0, block # 16384, count 10240 ... there are pending interrupts 0x00000008 [ERROR] response timeout error : 00002104 cmd 18 mmc read failed -19 blocks read: ERROR completed
[Completed] [Q] How to root T-Mo Galaxy Note 4 from Linux (Ubuntu/Debian)?
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.
generating empty userdata.img
I am trying to generate an empty userdata.img file. I just want to get rid of user generated data, so kind of format phone by using heimdall and as I understand this is the simplest way to achieve it. I understand that I can do this other ways as well, but I want to use heimdall for this operation. So I am creating empty userdata image with make_ext4fs like this: "make_ext4fs -l 200M -s userdata.img empty" and it works fine, but the size is something I don't understand. As I use -s parameter, it should be a sparse image which should resize as it gets full, isn't it? But as I flash this file, I can see data directory is just 200 megs in size. If I generate the image with -l 1G, then data partition is 1 gigabyte in the device. Then, do I understand that sparse option incorrectly or does it only work with emulator? Do I have to generate the image to match exactly the size that device specs says or is there some size I should use? If I do print-pit with heimdall, for userdata it doesn't specify partition block count, but just says block size/offset, so I expect this is the place where the partition begins in the filesystem: Code: --- Entry #21 --- Binary Type: 0 (AP) Device Type: 2 (MMC) Identifier: 21 Attributes: 5 (Read/Write) Update Attributes: 5 (FOTA) Partition Block Size/Offset: 6659072 Partition Block Count: 0 File Offset (Obsolete): 0 File Size (Obsolete): 0 Partition Name: userdata Flash Filename: userdata.img FOTA Filename: remained How do I know what is the size of the image I should generate? Is there any way to get this info straight from odin mode with heimdall? I have read quite a lot of different forums and here and there I can see that some peoples are able to find empty userdata images, but I haven't seen those in any of the samsung firmware packages I have checked.