Related
****************************************************************************
FIXED IT MYSELF! PLEASE CLOSE THIS THREAD! THANKS AND SORRY FOR THE INCONVENIANCE!!
****************************************************************************
Hey guys...pretty big noob here,
I have a Samsung Galaxy S i1900 and wanted to get Cyanogen on there,
I had a custom rom(don't remember which one) with Gingerbread installed for quite some time, but i wanted something new.
I followed the instructions from the cyanogenWiki and wanted to install
the ClockMod Recovery.
\\instructions below
Power off the Samsung Galaxy S and connect the microUSB to the computer but not the Samsung Galaxy S.
Boot the Samsung Galaxy S into download mode by holding down Home & Volume Down while connecting the microUSB to it.
Untar hardcore's kernel into the Heimdall directory.
On the computer, open terminal and run the following command from the Heimdall directory:
heimdall flash --kernel zImage
\\I followed all the instructions above and get the following error
Initialising connection...
Detecting device...
Claiming interface...
Setting up interface...
Checking if protocol is initialised...
Protocol is not initialised...
Initialising protocol...
Handshaking with Loke...
ERROR: Failed to open file "zImage"
\\Then trying to run again:
Initialising connection...
Detecting device...
Claiming interface...
Setting up interface...
Checking if protocol is initialised...
Protocol is initialised.
ERROR: Failed to open file "ZImage"
-------------------------------------
If i reboot without download moade i'm stuck in cell to computer mode and odin doesn't seem to detect anything (tried with 1.7 and 1.85)
Any idea how/if I can fix this??
Thanks
****************************************************************************
FIXED IT MYSELF! PLEASE CLOSE THIS THREAD! THANKS AND SORRY FOR THE INCONVENIANCE!!
Now with what you running your cell?
Sent from my GT-I9000 using xda premium
I find it less disturbing to use heimdall-frontend while im on linux.
If you dont have it installed i would recommend you to use that if you are not to familiar with flashing.
Can you still get you'r phone in download mode?
if so you might have to grab a stock firmware and flash back to stock before re-trying (that is if you cant boot/read data from the partitions)
you can grab a binary file installer from heimdalls website and launch it by typing heimdall-frontend in a terminal window.
Hope this help you!
Edit: you can grab a stock rom from http://samfirmware.com
Edit 2: h***, you have allready fixed it, good for you!
Sent from my GT-I9000 using Tapatalk
That's the solution when I had this problem I solved in this way try it will fix
Sent from my GT-I9000 using xda premium
Hi All --
Bought my touchpad from the last Ebay firesale (REFURB units). As such, my device is out of warranty with HP.
Device has been running very well with moboot/daily ICS flash/WebOS until a couple weeks ago when I left the tablet sitting for probably the better part of a week without being plugged in to the charger.
Presently, my touchpad does not power on at all with any charger I try and it is 100% unresponsive to every combination of press/hold buttons during attempted power on. I purchased a replacement battery with no change, I charged both of my batteries with an external power supply (at proper voltage/currents) and no response from touchpad.
when I connect touchpad to computer and boot it with PWR+volume down, it is detected as QDLoader. I found the Qualcomm drivers and have them installed. Touchpad is repeatably detected in Loader/download mode with PWR+Volume down.
I found QPST -- a software utility package from Qualcomm used to work with several devices, including the touchpad. QPST's "SOFTWARE DOWNLOAD" module detects the touchpad as a device in download state. The software gives me the option to backup/restore the device and it looks as though it would perhaps be able to bring my touchpad back to life.
I know I'm not the only one with this problem -- i've read hundreds of threads about touchpads "stuck" in Loader/Download mode. If I had a Qualcomm-formatted dump, I'd try restoring it to my device and properly document how to recover from brick to functional (if it works..)
Is there any way someone with a working touchpad would consider booting your TP into QDLoader mode (power + volume down) and doing the dumps with the "Software Download" module from QPST? There is a "backup" tab that creates a QCN file that it looks like I can restore to my touchpad and bring it back to life.
Anyone tried this already? If not -- would someone be onboard to help?
I downloaded the most recent build of QPST i could find from this thread on PPCGeeks and it recognizes my touchpad:
(UGH - newly registered here...not enough posts to submit external links. PM me for the URL to this)
This is a direct link to the QPST version i'm using:
(UGH - PM me for the URL to this)
Here's a link to the QDLoader drivers (64 bit) and I know the 32 bit versions are running around...i can find them if you'd like to help me but can't locate the right drivers.
(newly registered here...not enough posts to submit external links. PM me for the URL to this)
To summarize what I'm asking and be 100% clear, here's the drill
1) backup with rom-manager/clockworkmod or whatever
2) wipe data/cache
3) boot touchpad in Loader mode (pwr+volume down)
4) connect touchpad to computer, run SOFTWARE DOWNLOAD module of QPST -- click backup tab -- do the backup, send the backup file my way or post on forum.
5) back into clockworkmod -- restore the backup from step 1.
This would give me a clean qualcomm-formatted backup that would contain zero of your personal data or account data. You could restore right back to your functional ROM with no mess and no fuss.
Final note -- if someone has already tried this and succeeded (or failed) please let me know!
Thanks guys!
I'd be willing to do this for you, absolutely. Toss me a PM with the links, and I'll get on it today or tonight.
PM Sent! Many thanks!
Give me a couple days to get my computer back up and running and I'll get this for you. Sorry I haven't replied, but I've had some serious technological issues of late.
Not sure if this is going to work.
Got my hands on another touchpad and booted it into loader mode to try this --- when i went to do the download, QPST said the device was in "download" mode rather than "diagnostics" mode and wouldn't pull the image.
My touchpad might be dead and out for the count. Frustrating.
I'm wondering if a USB Jig would work with getting the TP to pop into download mode. If that's what you're trying to achieve here..
Like with Samsung Devices...
http://forum.xda-developers.com/showthread.php?t=1522478
I bought a professionally made jig for $5 to bring my Samsung Captivate back to from the dead.
If not I apologize for the intrusion..
=o)
Hmm -- well it's for sure worth a shot, i had seen some other people referencing a "jig" for unbricking. time to dig in and test one.
Other thing I've seen is that there are threads about jtag points on the touchpad....but i haven't seen anything about jtag software. Might have to dig that up too.
Any and all ideas are welcome
tekrhino said:
I'm wondering if a USB Jig would work with getting the TP to pop into download mode. If that's what you're trying to achieve here..
Like with Samsung Devices...
http://forum.xda-developers.com/showthread.php?t=1522478
I bought a professionally made jig for $5 to bring my Samsung Captivate back to from the dead.
If not I apologize for the intrusion..
=o)
Click to expand...
Click to collapse
Matt, any more development on this?
I have the exact same problem. Had given up on the software front and have just taken the battery out to attempt a manual recharge on an external charger however from your experience of buying a new battery it sounds like that isn't the problem.
Would be awesome if we could restore with the qualcomm software. My touchpad is bricked so probably not much help but if you want me to help test anything I will gladly as the touchpad is in the bin if I can't fix it.
have any of you guys even tried novacom to rebuild?
thats the most critical tool for repairing/diagnosing/repartitioning the TP...QPST is fine and well/necessary, but thats just a driver for the TP to communicate with the PC when in diag/DL mode
post or PM and ill help if possible, similar problems happened to me twice (1-black screen, "no charge, 2-boot loop with no DL mode) and ive recovered each time
Solidus, thanks for the offer of help.
When I connect my touchpad to the PC novacom does not recognise that a device is connected. When I press the volume button the PC now brings up found new device but it is only the QDLoader and again no webos device detected by novacom.
I'm not really sure what steps I need to take to get novacom to interface with the dead TP.
Just to recount the TP is completely dead. Have tried every method of charging including a touchstone and 4 different usb chargers and the PC. Have tried all possible button combinations to no avail.
Had a similar dead TP problem before but managed to bring it back on the the 'Power + 10x Home Button' fix.
Similar problem, need help
So, I seem to have a similar problem with the whole Touchpad issue. I've tried connecting to the wall charger and leaving it for some time, but to no avail. Connecting to my computer and using the Power+Home+Up volume button combination places the device as a "Palm" device in my device manager, but any attempt to use WebOS doctor or anything of the sort says there is nothing connected. I've tried updating the drivers, but my computer doesn't let me update them. When using the Power+Home+Down volume button combination, the Touchpad boots as as a "Qualcomm HS-USB QDLoader 9008" device which loading through QPST yields no results either. I'm not sure what other approach to go to, and any other help would be greatly appreciated.
you're in better shape than me if yours shows up as "palm" -- you should be able to get WebOS Dr. to find it and play nice.
I've made no progress to date.
Hi mattvirus,
I have a similar issue with my touchpad and would like to help. I have Windows XP, so I need the 32-bit version of the qualcomm drivers, but can't locate them. The 64-bit versions are easy to find, but I don't have a 64-bit os on any of my machines yet. If you can direct me where to find them as well as the other software you mentioned in previous posts (and couldn't post the links), I can get started. I have access to a working touchpad as well as my possibly bricked one and I'm convinced its not the battery, but a boot issue. After charging, I've been able to bring up the question mark battery logo, which appears to be full brightness, and it stayed on for 4 and a half hours. I can get into palm mode (which is not palm novacom) with pwr+volup+home and into qhsusb_dload mode with pwr+voldn+home.
Thanks
I'll do some digging to see if I can find the 32bit drivers for you. I've all but given up on my touchpad at this point
Hi,
I've got a Pre3 stuck in QDL (Qualcomm Download Mode) probably due to a BootLoader corruption.
The CPU of the Pre3 is the same in the TouchPad (in fact not really but both use the same CPU TYPE) MSM7x30 so we are in the same boat !
After a lot research i found that it can be one of the BootLoader parts that can be the cause of the loop in QDL.
I found the files needed in the webosdoctor jar for my phone : partition.mbn, dbl.mbn, amss.mbn and osbl.mbn.
In QPST you need a BootLoader for the MSM7x30 (this one to be able to flash the files) the Pre3/TouchPad are an eMMC device so it must be called EMPRG7x30.HEX
(E for Emergency when device is in QDL, M for MMC, PRG is common and our CPU TYPE is 7x30)
I found that file (MPRG7x30.HEX is the same file as EMPRG7x30.HEX) on the web in a firmware package for another phone ... but ... in QPST i probably doing something wrong it give me an error :
QPST 2.7-366 Software Download
1. In Software Download tab if choose my EMPRG7x30.HEX
2. In Multi-image tab i choose the folder with my *.mbn files, i select Sec Boot 2.0 as Boot System, i check Use Emerg. Host D/L
3. I press start ... and QPST answer Could not open flash programming file
Update 11 sept 2012
Log files are friends, it gave what was behind the error : QPST's looking for a bootloader in the same folder as the mbn files and it must be EMMCBLD.HEX or eEMMCBLD.HEX (if Use Emerg. Host D/L is checked).
So i rename MPRG7x30.hex to EMMCBLD.HEX and try again ... it doesn't works but go furtherer !
2012/09/11 19:07:41.300 StartSB2Download
2012/09/11 19:07:41.305 Begin SB2.0 Software Download
2012/09/11 19:07:41.305 Skip Reset: 0
2012/09/11 19:07:41.305 Lock phone
2012/09/11 19:07:41.307 Examine phone mode
2012/09/11 19:07:41.307 Get partition file name
2012/09/11 19:07:41.307 Partition file (and path for flash programmer): C:\Users\thierry\Desktop\Partage\Pre3\partition.mbn
2012/09/11 19:07:41.307 Flash Programmer file: C:\Users\thierry\Desktop\Partage\Pre3\EMMCBLD.HEX
2012/09/11 19:07:41.308 Examine phone mode
2012/09/11 19:07:41.308 Prepare to load the flash programmer
2012/09/11 19:07:41.343 Initialize the downloader
2012/09/11 19:07:41.343 Ping the downloader
2012/09/11 19:07:41.343 Sending Ping Request
2012/09/11 19:07:41.344 Response: 0x2 : Ticks: 0
2012/09/11 19:07:41.344 Wait For Download Response Succeeded.
2012/09/11 19:07:41.344 Get downloader parameters
2012/09/11 19:07:41.345 Sending Flash Programmer Parameter Request
2012/09/11 19:07:41.346 Wait For Parameter Response Succeeded.
2012/09/11 19:07:41.346 Load the flash programmer
2012/09/11 19:07:41.346 Search RAM image for erase pattern
2012/09/11 19:07:41.346 Skipped search - base address equals start address
2012/09/11 19:07:41.346 Using 32-bit write
2012/09/11 19:07:41.346 Sent Write: Address: 0x80000000 Size: 0x100
2012/09/11 19:07:41.353 Response: 0x2 : Ticks: 0
2012/09/11 19:07:41.353 Wait For Download Response Succeeded.
2012/09/11 19:07:41.353 Sent Write: Address: 0x80000100 Size: 0x100
2012/09/11 19:07:41.359 Response: 0x2 : Ticks: 0
2012/09/11 19:07:41.359 Wait For Download Response Succeeded.
...
2012/09/11 19:07:45.512 Sent Write: Address: 0x80024600 Size: 0x8C
2012/09/11 19:07:45.518 Response: 0x2 : Ticks: 0
2012/09/11 19:07:45.518 Wait For Download Response Succeeded.
2012/09/11 19:07:45.519 Sending Go Command 0x80000000
2012/09/11 19:07:45.521 Response: 0x2 : Ticks: 0
2012/09/11 19:07:45.521 Wait For Download Response Succeeded.
2012/09/11 19:07:45.521 Finish switching to streaming download mode
2012/09/11 19:07:45.521 SynchronizeConnection starting...
2012/09/11 19:07:45.521 Sending Hello to flash programmer...
2012/09/11 19:07:48.521 Timeout
2012/09/11 19:07:48.521 Sending Hello to flash programmer...
2012/09/11 19:07:51.521 Timeout
2012/09/11 19:07:51.521 Sending Hello to flash programmer...
2012/09/11 19:07:54.521 Timeout
2012/09/11 19:07:54.521 Sending Hello to flash programmer...
2012/09/11 19:07:57.521 Timeout
2012/09/11 19:07:57.521 Sending Hello to flash programmer...
2012/09/11 19:08:00.522 Timeout
2012/09/11 19:08:00.522 Sending Hello to flash programmer...
2012/09/11 19:08:03.522 Timeout
2012/09/11 19:08:03.522 Sending Hello to flash programmer...
2012/09/11 19:08:06.522 Timeout
2012/09/11 19:08:06.522 Sending Hello to flash programmer...
2012/09/11 19:08:07.511 Disabling automatic polling.
2012/09/11 19:08:07.561 Try Hello with polling disabled...
2012/09/11 19:08:07.567 Try Hello with polling disabled...
2012/09/11 19:08:07.573 Try Hello with polling disabled...
2012/09/11 19:08:07.579 SynchronizeConnection succeeded.
2012/09/11 19:08:07.580 Sending Hello Packet
2012/09/11 19:08:07.587 Version info = 3 2
2012/09/11 19:08:07.587 Block size = 400
2012/09/11 19:08:07.587 Flash base = 0
2012/09/11 19:08:07.587 Device Name=eMMC:
2012/09/11 19:08:07.587 Flash ID size= 4
2012/09/11 19:08:07.587 Sectors = 128
2012/09/11 19:08:07.587 Feature mask = 0x09
2012/09/11 19:08:07.587 Sending Close 0
2012/09/11 19:08:07.588 Cannot close when not previously opened
#2012/09/11 19:08:07.589 ARMPRG error: 15, text: Cannot close when not previously opened
2012/09/11 19:08:07.589 CloseDownloader error
2012/09/11 19:08:07.591 Sending Security Mode 0
2012/09/11 19:08:07.593 Decoding partition file
2012/09/11 19:08:07.595 Sending partition file
2012/09/11 19:08:07.595 Sending Partition Table
2012/09/11 19:08:07.799 DBL image: C:\Users\thierry\Desktop\Partage\Pre3\dbl.mbn
2012/09/11 19:08:07.800 Opening DBL file
2012/09/11 19:08:07.801 Sending MI Open mode 15 size 0
2012/09/11 19:08:07.803 No partition table received before open multi
ï2012/09/11 19:08:07.805 ARMPRG error: 15, text: No partition table received before open multi
2012/09/11 19:08:09.060 Download end, status 103, error 783
2012/09/11 19:08:09.060 Exit SB 2.0 download with status 0x00000000
Click to expand...
Click to collapse
In fact the log is right we must send a partition table, partition.mbn contains the MBR only, but how ?
mattvirus said:
I'll do some digging to see if I can find the 32bit drivers for you. I've all but given up on my touchpad at this point
Click to expand...
Click to collapse
If you've not yet given up... I have a working TP and a non-working TP that is in QDL mode. I have the 32-bit drivers installed, and should be able to do what is required. If you're still looking for a solution, please advise. I'm less familiar with the overall problem than you are, but may be in a better position to resolve. I believe I can take the appropriate image, possibly from a totally factory-defaulted TP, if needed.
Still out there?
rippleatwpi said:
If you've not yet given up... I have a working TP and a non-working TP that is in QDL mode. I have the 32-bit drivers installed, and should be able to do what is required. If you're still looking for a solution, please advise. I'm less familiar with the overall problem than you are, but may be in a better position to resolve. I believe I can take the appropriate image, possibly from a totally factory-defaulted TP, if needed.
Still out there?
Click to expand...
Click to collapse
I'm also working on this issue, but w/ Galaxy S3. I have a working stock, and one bricked into QDLoad download mode.
http://forum.xda-developers.com/showthread.php?t=1914359
Check this thread for some good work in progress.
Any luck in fixing your TP?
mexigga said:
Any luck in fixing your TP?
Click to expand...
Click to collapse
Not yet but looks like Darkspr1te is on it with some help with remolten on the forums
http://rootzwiki.com/topic/25858-touchpad-backup-with-qpst-need-this-for-unbricking/page__st__180
http://forum.xda-developers.com/showthread.php?p=34161100&posted=1#post34161100
There is hope for the bricks yet
No matter what downloaded package I tried to open with heimdall to install on my Captivate (i896), heimdall gave me the error:
Tar header contained and invalid file size
I installed ClockworkMod, and rooted the phone, had an issue and installed the stock Rogers (Canada) firmware. Since then, heimdall isn't detecting my phone at all.
$ heimdall detect
Failed to detect compatible download-mode device.
I'm willing to work with any of the heimdall developers to resolve these two issues, or does anyone have any ideas on how to resolve?
Thanks in advance!
acanuck said:
No matter what downloaded package I tried to open with heimdall to install on my Captivate (i896), heimdall gave me the error:
Tar header contained and invalid file size
I installed ClockworkMod, and rooted the phone, had an issue and installed the stock Rogers (Canada) firmware. Since then, heimdall isn't detecting my phone at all.
$ heimdall detect
Failed to detect compatible download-mode device.
I'm willing to work with any of the heimdall developers to resolve these two issues, or does anyone have any ideas on how to resolve?
Thanks in advance!
Click to expand...
Click to collapse
Firstly, please before you do anything else make sure you're using Heimdall 1.3.1 instead of 1.3.2. 1.3.2 introduced issues for some previously well-supported devices. The issues introduced shouldn't hard-brick any devices, but it can cause flashes to fail, and that can be a daunting experience.
The error you've received seems to indicate that the type of file you're trying to flash is not a Heimdall Firmware Package. Chances are the file you have is an archive that when extracted contains 3 other archives for use with Odin. Heimdall Firmware Packages are much simpler than this but unfortunately haven't been heavily adopted by the community just yet.
Nonetheless, Heimdall is extremely flexible. If you wish to flash the files you've downloaded please refer to the README included in the Heimdall DMG (also available here). In particular please refer to the section on performing a Custom Firmware Flash.
However, before you do all that you're going to need to ensure your device is being detected. Aside from the obvious "make sure you're in download mode" there are several reasons why you device may not be detected in OS X. They are as follows:
1. Permissions/ownership are set incorrectly for the codeless kext used by Heimdall. Open a terminal and run the following in order to ensure this is not the problem:
Code:
sudo chown -R root:wheel /System/Library/Extensions/heimdall.kext/
sudo chmod 755 /System/Library/Extensions/heimdall.kext/
sudo chmod 0644 /System/Library/Extensions/heimdall.kext/Contents/Info.plist
After doing this you will need to reboot your machine.
2. There are other kexts on your system interfering with Heimdall's codeless kext. Typically this would occur if you've tried to install Kies for Mac as Samsung's kernel extensions are given higher priority. If the Samsung's kext does exist it can be removed using the following command:
Code:
sudo rm -rf /System/Library/Extensions/ssuddrv.kext/
Again, after running this command you will be required to reboot your machine.
3. Your running an old faulty bootloader...
This is a much more serious problem. Samsung originally released several devices with a secondary bootloader that included a faulty implementation of the USB protocol. Unfortunately this means OS X will be totally unable to recognise your device. As such you will have to flash your phone using either Windows or Linux. However, once you flash a working secondary bootloader onto your device you will be able to use OS X for any other flashing later on.
Once you've completed 1 and 2 from above you'll be able to ask Heimdall to detect your device again. If it doesn't work this time around chances are you're running a faulty secondary bootloader.
$ heimdall version
v1.3.2
I did have the ssuddrv.kext/, which once I deleted and rebooted also asked me about tethering upon USB connect. Also, the heimdall Info.plist from was 755 permissions for some reason. This is all resolved now.
adb is showing the device, but heimdall is still not.
I was able to flash new kernels using heimdall flash on the command line a few days ago, until I went back to a stock image. My issue is, without being able to flash the ClockworkMod recovery kernel now, using heimdall, I'm not sure how to move forward. Perhaps I can can install a zImage with adb or something else? There doesn't appear (from reading the forums) to be FASTBOOT on the Captivate.
There must be a way I can boot another zImage using osx as I've done before?
I am trying to restore my Kindle HD to version 7.2.3 using Windows XP and when executing the fastboot command to flash the system.img I get the following error:
Code:
C:\temp\KFHD_SRT_v1.2.3>fastboot -i 0x1940 flash system system.img
load_file: could not allocate 929038336 bytes
error: cannot load 'system.img'
The system.img file is in the same directory as the fastboot.exe.
I get my Kindle into fastboot mode using a factory cable and to verify fastboot I get the product and it returnsTATE-PVT-08. I have checked the max-download-size and I get
Code:
max-download-size: 1006632960
finished. total time: 0.000s
i have tried flashing with both the factory cable and the regular USB cable and I keep getting the same error. Any thoughts on what the error means?
rjgonzalez73 said:
I am trying to restore my Kindle HD to version 7.2.3 using Windows XP and when executing the fastboot command to flash the system.img I get the following error:
Code:
C:\temp\KFHD_SRT_v1.2.3>fastboot -i 0x1940 flash system system.img
load_file: could not allocate 929038336 bytes
error: cannot load 'system.img'
The system.img file is in the same directory as the fastboot.exe.
I get my Kindle into fastboot mode using a factory cable and to verify fastboot I get the product and it returnsTATE-PVT-08. I have checked the max-download-size and I get
Code:
max-download-size: 1006632960
finished. total time: 0.000s
i have tried flashing with both the factory cable and the regular USB cable and I keep getting the same error. Any thoughts on what the error means?
Click to expand...
Click to collapse
There was another user a while back with the same problem, but I could never figure out why. Your system image is obviously smaller than the max-download size, so it doesn't make much sense to me.
From my perspective, if you can't get it to work, I would think you can (theoretically) boot into TWRP using the method found by Powerpoint45 and that would give you access to the adb shell so you can 'dd' the system image in place. I don't have an HD so I can't confirm that it will work, but I can't see any reason why it wouldn't.
That being said, I suggest you don't even attempt it unless you know exactly what you are doing.
"That's a special kind of stupid. The kind that makes me laugh."
soupmagnet said:
There was another user a while back with the same problem, but I could never figure out why. Your system image is obviously smaller than the max-download size, so it doesn't make much sense to me.
From my perspective, if you can't get it to work, I would think you can (theoretically) boot into TWRP using the method found by Powerpoint45 and that would give you access to the adb shell so you can 'dd' the system image in place. I don't have an HD so I can't confirm that it will work, but I can't see any reason why it wouldn't.
That being said, I suggest you don't even attempt it unless you know exactly what you are doing.
"That's a special kind of stupid. The kind that makes me laugh."
Click to expand...
Click to collapse
I noticed there was an error in the command I copied and pasted. The 0x1940 should be 0x1949, however I still get the same error message. I am of the opinion it is an issue with the computer I am using. I will try with a computer with Windows 7 and see if I have better results.
UPDATE: It was an issue with my XP machine. I was able to flash the system.img using a Windows 7 machine and was able to downgrade to version 7.2.1.
rjgonzalez73 said:
I noticed there was an error in the command I copied and pasted. The 0x1940 should be 0x1949, however I still get the same error message. I am of the opinion it is an issue with the computer I am using. I will try with a computer with Windows 7 and see if I have better results.
UPDATE: It was an issue with my XP machine. I was able to flash the system.img using a Windows 7 machine and was able to downgrade to version 7.2.1.
Click to expand...
Click to collapse
Sorry to revive this thread, but I'm having the same issue and I'm a little desperate.
I'm running a Vista, as are all the computers in my household.
Caveat: I tested this how-to with Ubuntu 14.04 and a Lenovo pc, I obviously don't know if it'll work for different linux versions, computers, note 4 phones. Just take everything as it is and please don't blame me if your phone gets bricked. Heimdall is as risky as Odin and you can void your warranty or even hard brick your phone if you don't know how to use it. I am a beginner myself with this software and don't ask me how to use it, just because I still have to learn most commands
Edit 1/12/16: I tested this software and I successfully flashed a TWRP recovery and eventually rooted my phone.
Most credit goes to Fattire and to the people at Github who are still mantaining and forking this software.(see why below).
I am a linux only user and I've been such for the latest 10 months at least. and, while I was previously a guy who played a lot with his own gadgets, the absolute lack of spare time and the lack of windows and Odin as well has prevented me from rooting and modding my last device.
As most of you should know, Heimdall is something like an open source versione of Odin, which works for Windows, Linux and Mac too. Anyway, Heimdall is this thing https://github.com/Benjamin-Dobell/Heimdall
Most threads here are very old and not very useful in order to get a fully functional Heimdall for Note 4 smartphones. I thought myself it was outdated and no more useful.
Yesterday I saw a post of @fattire http://forum.xda-developers.com/not...3-0-910f-g-t3243386/post64090942#post64090942 that linked to another post of his that linked to a thread of Github.
Well, I had some free time and it took not more than an hour to get everything working.
As Fattire himself wrote in the thread I linked, it is slightly technical, but it's not that difficult (I am a hobbyst, I am a lawyer and not a professional developer, and, as I said above, it took me less than a hour for everything to work).
So I want to share a simple how-to. It'll be not very well written since I have no spare time for now, but I hope it can be useful just the same.
First of all, the version of Heimdall that you can install this way
sudo apt-get install heimdall-flash
does not work
You need to clone the Github repo by SaburoJiro
Well, first of all, you've got to
sudo apt-get install git
then you have got to clone the repo but, unless you have already got a Github account or you want to join to it, you cannot type
git clone [email protected]/SaburoJiro/Heimdall.git
since you'll get a warning about your public key not beeing accepted
on the other side, you just have to use https instead of the previuos command this way (while being sure you are in your own user home directory)
git clone https://github.com/SaburoJiro/Heimdall.git
then it will took some time, also depending on the speed of your data connection and, after that time delay, you should have got the sources in /Heimdall
In any case, if the the path should be different, please look yourself for the directory where the sources are.
So, still as sudo su, type
cd Heimdall/libpit
Now you have got to compile the sources. If you have already compiled other biniaries, you should already have got the build essentials, if you have not compiled anything yet, you have very likely to
sudo apt-get install build-essential cmake zlib1g-dev qt5-default libusb-1.0-0-dev libgl1-mesa-glx libgl1-mesa-dev
then you just have got to type (see also here https://wiki.cyanogenmod.org/w/Install_and_compile_Heimdall)
cmake -DCMAKE_BUILD_TYPE=Release ..
make
sudo cp bin/* /usr/local/bin
Now you should have a working heimdall!
To check if it works, just put your phone in download mode, connect it to your computer via usb, and type
heimdall print-pit
that's what you should get
Copyright (c) 2010-2014 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...
Attempt failed. Detaching driver...
Claiming interface again...
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.
etc.
and finally
Ending session...
Rebooting device...
Releasing device interface...
Re-attaching kernel driver...
Well, now it works and I should be able to flash a recovery or a kernel without any hassle but for now I've got to work, so I cannot go any further
Just a little update, though not many users seem to be interested: I flawlessly flashed a twrp recovery without using the frontend (i.e. by using the terminal) and everything went fine. Later on I rooted the phone by flashing from the recovery both the kernel and supersu 2.50.
This thing is reliable and much faster than Odin, especially if you give up to the Gui.
It is a very good choice for Linux users.
You just have to download the right recovery.img, open the terminal of your pc as
sudo su
connect your phone in download mode and type
heimdall flash --RECOVERY recovery.img
and that's all, your phone will reboot and the recovery will be ok.
No warranty void until you actually use the recovery, as usual. If you flash anything, knox will be triggered.
I flashed supersu 2.52 and one of the kernel Senforcing compiled by Phil379, BTW
Update booloader and modem
I have just downloaded modem and bootloader from Kyuby rom http://forum.xda-developers.com/note-4/snapdragon-dev/kyubi-rom-port-n5-n910f-coj3-v5-t3254964
Updating modem and bootloader is very easy, you just have to remove the .md5 extension an decompress the 2 tar files. My suggestion is to put all the files into a single folder (in my case I put them into Scaricati, which stands for Downloads in italian).
After that, you have just got to type
sudo su
and move to the folder where the files are stored, then type the command shown below, which flashes both the modem and the bl files. Very easy, 30 seconds at most
[email protected]:/home/luca/Scaricati/bootloader# heimdall flash --APNHLOS NON-HLOS.bin --MODEM modem.bin --ABOOT aboot.mbn --RPM rpm.mbn --SBL1 sbl1.mbn --DBI sdi.mbn --TZ tz.mbn
Heimdall v1.4.1
Copyright (c) 2010-2014 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...
Attempt failed. Detaching driver...
Claiming interface again...
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 APNHLOS
100%
APNHLOS upload successful
Uploading MODEM
100%
MODEM upload successful
Uploading ABOOT
100%
ABOOT upload successful
Uploading RPM
100%
RPM upload successful
Uploading SBL1
100%
SBL1 upload successful
Uploading DBI
100%
DBI upload successful
Uploading TZ
100%
TZ upload successful
Ending session...
Rebooting device...
Releasing device interface...
Re-attaching kernel driver...
Video please
pedodroid said:
Video please
Click to expand...
Click to collapse
Well, I have no camera, apart from a couple of smartphones and I can't ask my wife to help me, she would say I am a nerd lol!
Do you want a video of the part where I compile the sources or about the flashing of modem and bootloader? Regarding the first one, maybe i could record the screen of my pc and share such video....
lucaoldb said:
Well, I have no camera, apart from a couple of smartphones and I can't ask my wife to help me, she would say I am a nerd lol!
Do you want a video of the part where I compile the sources or about the flashing of modem and bootloader? Regarding the first one, maybe i could record the screen of my pc and share such video....
Click to expand...
Click to collapse
WE ARE ALL NERDS!!!!!!! EMBRACE NERDOM!!!!
On topic you could use a screen recording app to get a video of what's going on on your phones screen then upload to youtube.
Yes, lol
But, when I use Heimdall, my phone is in download mode and there is nothing to be shown and there is no app that can record its screen. Anyway, during the week end, I will look for a way to make this how to as clear as possible and maybe I will share a little video. I was also thinking of making a deb package since Heimdall is an open source software and sharing a package should not break any rule, but I haven't made any deb package since the times of Nokia n900 (i.e. early 2011) and I need to brush up my skills
Thanks for taking the time to test this out.
One less reason to have a Windows partition.
Sent from my SM-N910F using Tapatalk
Thanks for this thread, been a Linux convert for about a year myself. Had to use my old windows machine for odin until now
Sent from my SM-N920C using Tapatalk
This all sounds interesting, i will try it.
Sorry for not sharing any video, but last week end I was very busy for work and I'd got some troubles with my pc due to a bad update of the javaws platform that I must rely on (the so called PCT: telematic trial... Garbage! Each update a bug, especially for poor linux users lol).
Anyway, I have checked and tried myself my own tutorial and found a little mistake: it's not Saburo Jiro's andoid.git, but Heimdall.git
Sorry for the mistake, but I had written this little guide very fast
The other steps do work.
Double post
@lucaoldb
Thank you,
Wow, I can't believe I've never seen this post. Ive searched for a verified working heimdall for the note 4, on and off for a year. Ive been trying to get rid of windows for over a year. Every search I've always done always showed unsuccessful results. And i never wanted to attempt it without knowing it could work. Don't want to brick my device.
So your saying, if i compile heimdall from source that it'll work. Can you or anyone please confirm this? And does it work for complete tar?
Thank you much!
You are welcome
It worked one year ago and I still have a working heimdall in my pc. In the meanwhile, the version you can install via apt-get could have been updated.... I would try this route first.
Regarding the full tar, you just have to extract the single files so as I wrote in the OP.
So, today 24th of September, Linux says:
remote: Repository not found.
fatal: repository 'https://github.com/SaburoJiro/Heimdall.git/' not found
Do you have the old repository or is there another way to compile the repository to flash the Note 4 with Heimdall?
So i found that you copied the old repository, can you change the old repository from SaburoJiro to https://github.com/fat-tire/Heimdall?
Heimdall is a very interesting choice, specially for linux users (like me) who don't have access to a windows computer or Odin itself. I've compiled the Command line version and saved it somewhere, so I can use it in every distro I got. It works very well and doesn't need any dependecies (except for libusb which comes with almost every distro).
It's just a bit more complicated when you have to flash a stock ROM that comes with many files at once and you have to know every single partition to flash. The command for it gets big and with a lot of parameters (I am not complaining about that) which makes complicated for most of common users.
Just yesterday I have flashed a stock ROM on my Grand Prime, that was complicated to figure out which file fitted on each partition. Even though it was hard, I still managed to get my phone working again.