Related
This package includes:
Repartitioning: Repartition to stock JFD
Reloading: IBL/PBL, PARAM, SBL, SBL2, Kernel, Recovery, FactoryFS and DBData
formatting:Cache
This package does not wipe:
Data(where your apps are stored)
Modem (Your carrier specific communications Operating System)
SDCard (where your pictures are stored)
EFS(Where your serial number and carrier information is stored)
Instructions:
Get the latest version of java here: http://java.com/en/download/installed.jsp
Put your Gtab into "Download Mode"
Run the program once, and if it does not work, then check the "Flash Bootloaders" checkbox and flash again
{
"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"
}
Your device will end up as it came from the factory with UVJFD
Download:
Download JQ1 Heimdall One-Click
http://files.teamkomin.com/GalaxyTabP1000/GalaxyTabP1000-JQ1-One-Click.jar
This package is intended for:
Linux 32
Linux 64
OS-X Leopard
OS-X Snow Leopard
OS-X Lion
Windows XP
Windows Vista
Windows 7
Note: In-App links do not work. No other problems are known at this time.
Hello,
program always returns me:
Initialising connection...
Detecting device...
ERROR: Failed to access device. libusb error: -12
pubi said:
Hello,
program always returns me:
Initialising connection...
Detecting device...
ERROR: Failed to access device. libusb error: -12
Click to expand...
Click to collapse
Is your device in download mode?
Did you install the open source drivers included with the package? Try menu help>install heimdall. Perform the steps as prompted.
yes, i'm in dwl mode and i had reinstall drivers and heimdall. but when i click on Flash, same window again. I have installed boca latest, is maybe that a problem? Because i have noticed that Odin also won't connect in dwl mode anymore. I don't understand...
pubi said:
yes, i'm in dwl mode and i had reinstall drivers and heimdall. but when i click on Flash, same window again. I have installed boca latest, is maybe that a problem? Because i have noticed that Odin also won't connect in dwl mode anymore. I don't understand...
Click to expand...
Click to collapse
I don't know what Boca latest is.
Just use zadig and select show all devices from the menu. Then reinstall the driver. What OS are you using?
i'm using win7.
i already reinstall drivers, several times.
boca = other room
i can confirm, that problem is in one-click app, because i have installed everything on the other computer and i get the same error.
Your app always want to install drivers again in never-ending loop... can you fix that? do i send you some log or maybe some other info?
I should say that i have no problems with drivers here, i didn't need to re-stock but i wanted give it a try.
So, as i said i can install drivers but i've got a problem with pit file:
Code:
GalaxyTab Stock P1000 XXJQ1 XXJPZ is ready for your device.
Operating System: Windows
Found Heimdall Version: v1.3.1
Device not connected.
Ready for flash.Repartition was requested but bootloaders are not to be flashed.
Omiting Bootloaders.
KERNEL RECOVERY FACTORYFS CACHE
Heimdall v1.3.1, 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...
ERROR: Drivers Not Found
Installing driversRepartition was requested but bootloaders are not to be flashed.
Omiting Bootloaders.
KERNEL RECOVERY FACTORYFS CACHE
Heimdall v1.3.1, 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...
Checking if protocol is initialised...
Protocol is not initialised.
Initialising protocol...
Handshaking with Loke...
Beginning session...
Session begun with device of type: 0
Downloading device's PIT file...
PIT file download sucessful
Local and device PIT files don't match and repartition wasn't specified!
Ending session...
Rebooting device...
Device not connected.
Nice work Adam.
Samsung Drivers is what i've used.
should I continue if it failed to install drivers?
It can't install the drivers (message below) so I took q pics to prove it in attachments...
edit: edited/resized pics, strange xda forum limitation
Operating System: Windows
Found Heimdall Version: v1.3.1
Device Connected. Awaiting package preparation.
GalaxyTab Stock P1000 XXJQ1 XXJPZ is ready for your device.
Repartition was requested but bootloaders are not to be flashed.
Omiting Bootloaders.
KERNEL RECOVERY FACTORYFS CACHE
Heimdall v1.3.1, 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...
ERROR: Drivers Not Found
Installing drivers
Click to expand...
Click to collapse
should I continue with flashing (and ticking the bootloaders box)?
Stock Gingerbread 2.3.3 UK 3G Galaxy Tab:
PDA: JP9
PHONE: JPZ
CSC: KP1
pit problems?
I am on win7 x64. I did a next step a bit more succesfuly after installing (different) 'heimdall' drivers.
1. downloaded/installed (unpacked) latest Heimdall 1.3.1
2. put the Galaxy Tab to download mode
3. installed zadig.exe drivers found in the Heimdall's drivers directory, followed instructions in readme.txt to accept not-signed-prompts
4. tried to flash it, it moved with it (no longer window to install drivers) - thought it was not succesful (maybe because of pit) with this message:
GalaxyTab Stock P1000 XXJQ1 XXJPZ is ready for your device.
Operating System: Windows
Found Heimdall Version: v1.3.1
Ready for flash.Repartition was requested but bootloaders are not to be flashed.
Omiting Bootloaders.
KERNEL RECOVERY FACTORYFS CACHE
Heimdall v1.3.1, 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...
Checking if protocol is initialised...
Protocol is not initialised.
Initialising protocol...
Handshaking with Loke...
Beginning session...
Session begun with device of type: 0
Downloading device's PIT file...
PIT file download sucessful
Local and device PIT files don't match and repartition wasn't specified!
Ending session...
Rebooting device...
Device not connected.
Click to expand...
Click to collapse
European (UK) 3G Galaxy Tab:
PDA: JP9
PHONE: JPZ
CSC: KP1
5. Galaxy Tab rebooted to normal mode.
6. I've entered Download Mode once again.
now I'm able (entering 2nd time to download mode) to tick 'flash bootloaders' checkbox (probably because 1st try was unsuccesful it is now enabled for checking).
7. should I tick it and Flash it once more? - quite a risky message follows, and I don't want it to eat my dogs...
Heimdall uses open source libusb drivers. They must be installed. Odin drivers are closed source and property. The heimdall drivers will only work on the USB port which you install them on. The rest will be Odin
If you flash bootloaders it is at your own risk. This package is the safest way to flash. It won't flash a bootloader unless it also repartitions, flashes PBL,SBL, And PARAMS. There are several safety mechanisims built in as well. A bad bootloader flash is how you brick your tab. Just make sure you have a good cable. I don't want my software package to be responsible for any bricks. I've implemented several safeties on top of heimdall's built-in safety mechanisims.
should I disconnect/reboot manually?
AdamOutler said:
If you flash bootloaders it is at your own risk. This package is the safest way to flash. It won't flash a bootloader unless it also repartitions, flashes PBL,SBL, And PARAMS. There are several safety mechanisims built in as well. A bad bootloader flash is how you brick your tab. Just make sure you have a good cable. I don't want my software package to be responsible for any bricks. I've implemented several safeties on top of heimdall's built-in safety mechanisims.
Click to expand...
Click to collapse
I gave it a 2nd try with checkbox 'flash bootloaders' enabled, it looks like it finished. But my tab is still in download mode (didn't reboot to normal mode) and console says it is disconnected - yet picture (in one-click-program-interface) is green-connected (right-down corner). Nothing seems to be happening now.
I guess I'm going to disconnect it and reboot?
Ready for flash.IBL+PBL SBL SBL2 PARAM KERNEL RECOVERY FACTORYFS CACHE
Heimdall v1.3.1, 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...
Checking if protocol is initialised...
Protocol is not initialised.
Initialising protocol...
Handshaking with Loke...
Beginning session...
Session begun with device of type: 0
Uploading PIT
PIT upload successful
Uploading KERNEL
KERNEL upload successful
Uploading RECOVERY
RECOVERY upload successful
Uploading FACTORYFS
FACTORYFS upload successful
Uploading CACHE
CACHE upload successful
Uploading IBL+PBL
IBL+PBL upload successful
Uploading SBL
SBL upload successful
Uploading SBL2
SBL2 upload successful
Uploading PARAM
PARAM upload successful
Ending session...
Rebooting device...
Device not connected.
Ready for flash.
Click to expand...
Click to collapse
---------- Post added at 12:21 PM ---------- Previous post was at 11:54 AM ----------
SUCCESSFUL
I've disconnected galaxy tab & rebooted it - and was able to boot to normal mode. I have JQ1 firmware now (with many locales) which is a requirement for my next step (install CyanogenMod 7.1).
Thank you very much Adam for a great work and support.
I've released information on creating your own Heimdall one-Click here: [Release] Heimdall One-Click - ROM Packaging and Distribution System
does this include hidden.rfs?
one quick question: does this package include hidden.rfs?
If I install chainfire's package with odin it will fails at Hidden.rfs.
If I remove Hidden.rfs from the package odin will return success, but Tab would hung at logo during boot.
One-Click-xxJQ1 also would work return success with the same booting problem.
I am trying to identify the problem by reducing variables, can you confirm that One-Click-xxJQ1 does not flash hidden.rfs?
thanks
Adam
Any chance of the md5sum value for the file linked in the first post please.
I'm getting a magic number error when trying to execute it and want to check the file as I'm downloading it again.
I'm using Ubuntu 64bit
Galaxy Tab P1000 JQ1 One Click jar
AdamOutler said:
I don't know what Boca latest is.
Just use zadig and select show all devices from the menu. Then reinstall the driver. What OS are you using?
Click to expand...
Click to collapse
Hello.
I have problem with these links.
I need file Galaxy Tab P1000- JQ1 -One-Click jar
I can't create this file in one click package but is error " firmware xml missing from package"
I want to do unbrick my samsung P1000.
Somebody have actually Galaxy Tab P1000- JQ1 -One-Click jar ??
Help me please
Thanks
I'm looking to root my Sprint SGS3 using a Linux machine.
Note: I do not own nor do have access to a Windows machine so don't even suggest I use ODIN in a Windows virtual machine or otherwise.
I've done plenty of searching on this and other forums over the last month but most of what I find suggest using ODIN, however, this is not an option for the above started reason. In addition, the shear number of search results is making it difficult to find the needle in the haystack.
Also, I read the posts in the Sprint SGS3 XDA forums that mention Heimdall but they don't actually explain how to root the Sprint SGS3. All the Heimdall threads I've found only describe what it is capable of. Even Glass Echidna's site only describes what it is capable of but not the steps required to root a phone.
I've also found the post with links to the Heimdall Flasher or other toolkits that either mention basic steps but don't explain what each step does or the toolkit is a Windows executable.
I tried to flash twrp recovery with Heimdall and it appeared to work, however, it tripped the flash counter and either didn't actually flash or it was overwritten because I booted into recovery and still had the stock recovery.
The "[HOWTO][ROOT] Forget about Odin and Heimdall also does not increase counter" post doesn't work anymore. Any attempt to perform an operation on "/data/local/" now fails with "permission denied" thereby thwarting any attempt to root the devices with this method.
Why can't I just root my Sprint SGS3 with adb and fastboot. I was able to root my Motorola XOOM with adb and fastboot so why can't I on a SGS3?
So, with all that said, what I'm looking for is written instructions on flashing in Linux without using a toolkit that does everything for me. I want to actually understand what is going on. Also, I'd prefer not to sit through watching several youtube videos.
Have you seen this thread? I haven't tried it, so I can't vouch for it in any way, but it is stock, rooted lj7 using heimdall. I used heimdall a lot on my captivate and it was a rock solid program, much better than odin in my opinion.
Anyway, It's an old thread, not sure how much support you'll get. Good luck!
http://forum.xda-developers.com/showthread.php?p=34631785
Sent from my SPH-L710 using xda app-developers app
laihafloyd said:
Have you seen this thread? ...
Click to expand...
Click to collapse
Yup, saw it and tried it. Doesn't work running as a normal user.
The package from the post is able to detect when my phone is placed in download mode, however, after clicking the "flash" button, it hangs at 'Detecting device...' I can't remember if I tried running the package as root but it shouldn't be required. When I tried flashing twrp with heimdall before finding the thread you mention, I didn't have to run as root.
Besides, the download in the thread falls into the category of a toolkit and hides everything behind the curtain, which means I'll never understand what is going on.
Thanks anyway.
Edit:
OK, there is a button in the toolkit to show details of the flashing process and, when viewing it, I saw 'Detecting device...ERROR: Failed to access device. libusb error: -3'. So in my case it does need to be run as root because I do not have the udev rules that set the permissions properly for the device file.
Alas, it still fails as root with:
Checking if protocol is initialised...
Protocol is not initialised.
Initialising protocol...
Re-attaching kernel driver...ERROR: Failed to initialise protocol!
Click to expand...
Click to collapse
Edit Again:
OK, I let the toolkit download and install heimdall (version 1.3.1) with the previous run.
However, I ran the toolkit again but instead of letting it download and install heimdall I had it run heimdall 1.4 RC1 that I downloaded and compiled from source prior to this post.
With this run, the toolkit is actually uploading to my phone now.
Looks like I might be able to root my phone with this toolkit but it still doesn't help me understand how to root a SGS3 step-by-step.
Update:
It worked.
For those who are worried about what they should see inside the main toolkit window while flashing, here is the output of my run:
Operating System: Debian Based x86_64
Found Heimdall Version: Heimdall version is out of date.
Connect your device in Download Mode to procede.
Device Connected. Awaiting package preparation.
Stock Rooted+recovery! L710VPBLJ7 is ready for your device.
Repartition was requested but bootloaders are not to be flashed.
MODEM SBL1 SBL2 SBL3 ABOOT RPM BOOT TZ SYSTEM PERSIST CACHE RECOVERY
Heimdall v1.4 RC1
Copyright (c) 2010-2012, Benjamin Dobell, Glass Echidna
[SNIP - cannot post links]
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:
[SNIP - cannot post links]
Initialising connection...
Detecting device...
Claiming interface...
Attempt failed. Detaching driver...
Claiming interface again...
Setting up interface...
Checking if protocol is initialised...
Protocol is not initialised.
Initialising protocol...
Protocol initialisation successful.
Beginning session...
Session begun.
In certain situations this device may take up to 2 minutes to respond.
Please be patient!
Downloading device's PIT file...
PIT file download successful.
Uploading MODEM
MODEM upload successful
Uploading SYSTEM
SYSTEM upload successful
Uploading PERSIST
PERSIST upload successful
Uploading CACHE
CACHE upload successful
Uploading RECOVERY
RECOVERY upload successful
Uploading SBL1
SBL1 upload successful
Uploading SBL2
SBL2 upload successful
Uploading SBL3
SBL3 upload successful
Uploading ABOOT
ABOOT upload successful
Uploading RPM
RPM upload successful
Uploading BOOT
BOOT upload successful
Uploading TZ
TZ upload successful
Ending session...
Rebooting device...
Releasing device interface...
Re-attaching kernel driver...
Click to expand...
Click to collapse
In regards to the rooting of my phone on the page [GUIDE][ROOT][Mac][Linux]Epic 4G Touch Root on Mac or Linux using Heimdall!....
I get this....
Casper Downloads # heimdall flash --kernel zImage
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...
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.
ERROR: Partition "kernel" does not exist in the specified PIT.
Ending session...
Rebooting device...
Releasing device interface...
Re-attaching kernel driver...
Help anyone please!
PC Odin a rooted stock ROM, there are instructions how to do it on Linux and Mac in the Stock ROM Repository in the stickies section of E4GT Android Development.
Team Rejectz
Thanks . I'll look into it.
Take it to the house said:
In regards to the rooting of my phone on the page [GUIDE][ROOT][Mac][Linux]Epic 4G Touch Root on Mac or Linux using Heimdall!....
I get this....
# heimdall flash --kernel zImage
...
ERROR: Partition "kernel" does not exist in the specified PIT.
Click to expand...
Click to collapse
This means your phone does not have a partition named "kernel". As of Heimdall 1.4.0 you need to specify exact partition names (because every device uses different names). The README (https://raw.github.com/Benjamin-Dobell/Heimdall/master/Linux/README) has detailed instructions.
Thanks bro
I got it rooted through another thread. I believe it was Rwilco12.
I so wanted to get this rooted as I am running linux and had to virtual into a windows to do it the other way.
Regarless I learned a lot and had a fun time figuring it out.
Again thank you
Usual disclaimers this will void your warranty and may brick your phone,
This is not an all inclusive guide, just how I was able to install TWRP and root my Note 3 using a Mac Pro with OSX Mavericks. If you can't find the needed files you probably shouldn't be trying this.
I tried several things to Install TWRP - Kies, ADB, Fastboot, Odin for Mac, Odin for Windows running under Virtual Box. None of these worked.
What finally worked was using: The CLI version of Heimdall v1.4.0. From terminal with openrecovery-twrp-2.6.3.1-hltetmo.img in your current directory the command to flash is:
heimdall flash --RECOVERY openrecovery-twrp-2.6.3.1-hltetmo.img
Notes: kies must be uninstalled or you will get: libusbx: error [darwin_claim_interface] USBInterfaceOpen: another process has device opened for exclusive access
ERROR: Claiming interface failed!
RECOVERY must be all CAPS or flash will fail.
Phone must be in Odin mode from powered off VOL_DOWN--HOME--POWER
Once TWRP is installed I was able to download: UPDATE-SuperSU-v1.65.zip and install it from TWRP in Recovery mode, This final step leaves you with ROOT on your phone.
Wish I saw this earlier! Borrowed a friend's laptop just root the Note.
Good to know Heimdall 1.4 is working on it. I was hesitant to try it until it was confirmed working.
this worked perfectly ! Thanks !
Trying to Root Note 3 using this method but getting error message. I've uninstalled KIES from computer and I don't see it on the phone. Any help?
mrmarshall428 said:
Trying to Root Note 3 using this method but getting error message. I've uninstalled KIES from computer and I don't see it on the phone. Any help?
Click to expand...
Click to collapse
When you uninstalled Kies did you use the uninstall program or did you just delete it from the applications folder? I used the uninstall program I got on the KiesMac_3.0_Setup.dmg
What is the exact error you are getting?
mlpmail said:
When you uninstalled Kies did you use the uninstall program or did you just delete it from the applications folder? I used the uninstall program I got on the KiesMac_3.0_Setup.dmg
What is the exact error you are getting?
Click to expand...
Click to collapse
Uninstalled it from Computer
busbx: error [darwin_claim_interface] USBInterfaceOpen: another process has device opened for exclusive access
ERROR: Claiming interface failed!
Actually i deleted it from Applications putting it in trash then erase, thinking that would remove it all
---------- Post added at 03:10 AM ---------- Previous post was at 02:44 AM ----------
mrmarshall428 said:
Uninstalled it from Computer
busbx: error [darwin_claim_interface] USBInterfaceOpen: another process has device opened for exclusive access
ERROR: Claiming interface failed!
Actually i deleted it from Applications putting it in trash then erase, thinking that would remove it all
Click to expand...
Click to collapse
Edit: I figured it out. Thanks
mrmarshall428 said:
Uninstalled it from Computer
busbx: error [darwin_claim_interface] USBInterfaceOpen: another process has device opened for exclusive access
ERROR: Claiming interface failed!
Click to expand...
Click to collapse
Do you have any other program running that might be grabbing the phones usb connection? Parallels, virtualbox, fastboot, abd are a few things I can think of,
Try exiting any of these programs
If you have run adb since computer was rebooted try :
adb kill-server
I hope this helps, I can't think of anything else to try.
Knox
Only have a macbook as well wanting to know if this root method will mess with knox? I have read several articles about some root methods messing with the phone after rooting. can anyone confirm this?
khrizg35 said:
Only have a macbook as well wanting to know if this root method will mess with knox? I have read several articles about some root methods messing with the phone after rooting. can anyone confirm this?
Click to expand...
Click to collapse
This will trigger the knox flag disabling the knox features. There is now another way to get root that does not change the recovery partition or trip the knox flag, I have not looked into doing it, as I have already tripped my knox flag and as far as I can tell it cannot be undone.
mlpmail said:
This will trigger the knox flag disabling the knox features. There is now another way to get root that does not change the recovery partition or trip the knox flag, I have not looked into doing it, as I have already tripped my knox flag and as far as I can tell it cannot be undone.
Click to expand...
Click to collapse
So by tripping Knox we wouldn't be able to do a warranty exchange or phone cloak through t-mobile? Sorry for all the questions just wanna make sure I do this right and appreciate the help
khrizg35 said:
So by tripping Knox we wouldn't be able to do a warranty exchange or phone cloak through t-mobile? Sorry for all the questions just wanna make sure I do this right and appreciate the help
Click to expand...
Click to collapse
On another thread a user said he saw a note getting returned at tmo and they checked the system status in settings and in download mode. I'm gonna wait to flash anything until there is a way to get 100% back to stock.
mlpmail said:
Usual disclaimers this will void your warranty and may brick your phone,
This is not an all inclusive guide, just how I was able to install TWRP and root my Note 3 using a Mac Pro with OSX Mavericks. If you can't find the needed files you probably shouldn't be trying this.
I tried several things to Install TWRP - Kies, ADB, Fastboot, Odin for Mac, Odin for Windows running under Virtual Box. None of these worked.
What finally worked was using: The CLI version of Heimdall v1.4.0. From terminal with openrecovery-twrp-2.6.3.1-hltetmo.img in your current directory the command to flash is:
heimdall flash --RECOVERY openrecovery-twrp-2.6.3.1-hltetmo.img
Notes: kies must be uninstalled or you will get: libusbx: error [darwin_claim_interface] USBInterfaceOpen: another process has device opened for exclusive access
ERROR: Claiming interface failed!
RECOVERY must be all CAPS or flash will fail.
Phone must be in Odin mode from powered off VOL_DOWN--HOME--POWER
Once TWRP is installed I was able to download: UPDATE-SuperSU-v1.65.zip and install it from TWRP in Recovery mode, This final step leaves you with ROOT on your phone.
Click to expand...
Click to collapse
OH MY GOD!
i was a right panic attack because i couldnt do anything! followed your directions and BAM worked. Thank you so much! you got a paypal i can donate to?
mlpmail said:
Usual disclaimers this will void your warranty and may brick your phone,
This is not an all inclusive guide, just how I was able to install TWRP and root my Note 3 using a Mac Pro with OSX Mavericks. If you can't find the needed files you probably shouldn't be trying this.
I tried several things to Install TWRP - Kies, ADB, Fastboot, Odin for Mac, Odin for Windows running under Virtual Box. None of these worked.
What finally worked was using: The CLI version of Heimdall v1.4.0. From terminal with openrecovery-twrp-2.6.3.1-hltetmo.img in your current directory the command to flash is:
heimdall flash --RECOVERY openrecovery-twrp-2.6.3.1-hltetmo.img
Notes: kies must be uninstalled or you will get: libusbx: error [darwin_claim_interface] USBInterfaceOpen: another process has device opened for exclusive access
ERROR: Claiming interface failed!
RECOVERY must be all CAPS or flash will fail.
Phone must be in Odin mode from powered off VOL_DOWN--HOME--POWER
Once TWRP is installed I was able to download: UPDATE-SuperSU-v1.65.zip and install it from TWRP in Recovery mode, This final step leaves you with ROOT on your phone.
Click to expand...
Click to collapse
Would anyone be so kind as to walk me through this step-by-step or point me to a link that does the same? Please please please!
gilsmithii said:
Would anyone be so kind as to walk me through this step-by-step or point me to a link that does the same? Please please please!
Click to expand...
Click to collapse
Yes, I would like more help as well!!!
Worked for me too!
Worked for me too after UNINSTALLING Kies.
I deleted kies first and it returned "libusbx: error [darwin_claim_interface] USBInterfaceOpen: another process has device opened for exclusive access"
Then I downloaded kies again. When it starts it offers you to uninstall.
After uninstalling everything started working.
It is qon macbook pro.
Thank you!
Please help! I'm getting this:
"heimdall flash --RECOVERY /Users/Lauren/Downloads/recovery-clockwork-6.0.4.6-hltexx.img --no-reboot
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...
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...
ERROR: Failed to send request to end PIT file transfer!
ERROR: Failed to download PIT file!
Ending session...
ERROR: Failed to send end session packet!
Releasing device interface...
Does it matter if the Note 3 had the latest Lollipop based download from Samsung on it?
tmorterlaing said:
Please help! I'm getting this:
"heimdall flash --RECOVERY /Users/Lauren/Downloads/recovery-clockwork-6.0.4.6-hltexx.img --no-reboot
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...
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...
ERROR: Failed to send request to end PIT file transfer!
ERROR: Failed to download PIT file!
Ending session...
ERROR: Failed to send end session packet!
Releasing device interface...
Does it matter if the Note 3 had the latest Lollipop based download from Samsung on it?
Click to expand...
Click to collapse
So picked up the phone this week and it I took the Ota by mistake. I have osx and mac only. I've tried mutiple versions of heindall only to get a similar error. I've tried multiple things found online and some xda. I simply cannot download the pit. Anyone have the pit for lollipop and any ideas on how to properly get heindall (latest mac version to play nicely)
Sent from my SM-N900T using XDA Free mobile app
I've been attempting to install LineageOS onto my (Exynos) Galaxy S7 for a while now with absolutely no luck. I followed the LineageOS guide for my phone (can't link things yet, sorry) step by step, and have consistently not been able to get past this command:
Code:
heimdall flash --RECOVERY twrp-x.x.x-x-herolte.img --no-reboot
On my phone, it displays what looks to be the very start of a white progress bar at the bottom. It never goes past this. The command exits saying the following:
Code:
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 RECOVERY
100%
RECOVERY upload successful
Ending session...
ERROR: Failed to receive session end confirmation!
Releasing device interface...
From what I've read online, Heimdall not working is a fairly common problem all-around. Something called Odin was rumored to work. The problem is, it was a Windows app, and I don't have any access to a Windows computer. I attempted to use it with WINE, but it wouldn't recognize my phone at all (and I had the right drivers, too).
Things I have tried:
* Running the heimdall command as sudo
* Checking my file integrity - I checked every file's MD5 / SHA256 hashes
* lsusb says that my phone is there and in download mode
* Bootloader's unlocked, USB debugging enabled
* Neither fastboot nor ADB recognize my device in download mode
I'm running Manjaro, but have access to a Mac if needed. Thanks for any help.
EDIT: Some people have said that Heimdall is always problematic with Samsungs and recommended using Odin.
Heimdall is outdated. There is a newer version for self compilers in github I think.
The version in Debian repo failed with my S5 at pit file downloading.
kurtn said:
Heimdall is outdated. There is a newer version for self compilers in github I think.
The version in Debian repo failed with my S5 at pit file downloading.
Click to expand...
Click to collapse
Do you have a link? I couldn't find it.
kyiami said:
Do you have a link? I couldn't find it.
Click to expand...
Click to collapse
https://gitlab.com/BenjaminDobell/Heimdall
The path of lest resistance
kyiami said:
I've been attempting to install LineageOS onto my (Exynos) Galaxy S7 for a while now with absolutely no luck. I followed the LineageOS guide for my phone (can't link things yet, sorry) step by step, and have consistently not been able to get past this command:
Code:
heimdall flash --RECOVERY twrp-x.x.x-x-herolte.img --no-reboot
On my phone, it displays what looks to be the very start of a white progress bar at the bottom. It never goes past this. The command exits saying the following:
Code:
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 RECOVERY
100%
RECOVERY upload successful
Ending session...
ERROR: Failed to receive session end confirmation!
Releasing device interface...
From what I've read online, Heimdall not working is a fairly common problem all-around. Something called Odin was rumored to work. The problem is, it was a Windows app, and I don't have any access to a Windows computer. I attempted to use it with WINE, but it wouldn't recognize my phone at all (and I had the right drivers, too).
Things I have tried:
* Running the heimdall command as sudo
* Checking my file integrity - I checked every file's MD5 / SHA256 hashes
* lsusb says that my phone is there and in download mode
* Bootloader's unlocked, USB debugging enabled
* Neither fastboot nor ADB recognize my device in download mode
I'm running Manjaro, but have access to a Mac if needed. Thanks for any help.
EDIT: Some people have said that Heimdall is always problematic with Samsungs and recommended using Odin.
Click to expand...
Click to collapse
I am going to risk making the assumption that you know SOMEONE (anyone) with a Windows PC who can grant you access to it for the not more than the (hard to believe more than) ten to fifteen minutes it will take you to install Odin on it, flash the blasted thing, and be done with it. I realize you need to set foot into the territory of the evil Windows empire to do this, but Odin and the rest of the Ancient Norse Gods shall forgive you, I promise. It is so preposterously easy to do this with Odin that even a simple mind like mine can grasp it easily and do it without problems. At least I had none, and hopefully you shall have a similar experience (but as with all things out here, no guarantees). If it fails, it suggests a hardware problem to me, because this is about as straightforward as it gets. Just DO remember to turn OFF the automatic reboot in Odin because I believe THAT is what will trip KNOX on the device on the way out. Of course, with a rooted device running LOS, tripping KNOX is a somewhat less important consideration. GOOD LUCK
nezlek said:
I am going to risk making the assumption that you know SOMEONE (anyone) with a Windows PC who can grant you access to it for the not more than the (hard to believe more than) ten to fifteen minutes it will take you to install Odin on it, flash the blasted thing, and be done with it. I realize you need to set foot into the territory of the evil Windows empire to do this, but Odin and the rest of the Ancient Norse Gods shall forgive you, I promise. It is so preposterously easy to do this with Odin that even a simple mind like mine can grasp it easily and do it without problems. At least I had none, and hopefully you shall have a similar experience (but as with all things out here, no guarantees). If it fails, it suggests a hardware problem to me, because this is about as straightforward as it gets. Just DO remember to turn OFF the automatic reboot in Odin because I believe THAT is what will trip KNOX on the device on the way out. Of course, with a rooted device running LOS, tripping KNOX is a somewhat less important consideration. GOOD LUCK
Click to expand...
Click to collapse
Yeah, I've found a bunch of stuff saying that Heimdall just doesn't work on Samsung phones. It's just a hassle to get access to a Windows computer, and neither WINE nor gnome-boxes work (WINE doesn't have access to USB ports). I'll try that.
I had same problem on my N910C. Try this, i installed with this way.