[Q] Rooting with Linux (No ODIN/Windows is Not an Option) - Sprint Samsung Galaxy S III

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

Related

[Heimdall One-click] FI27

This is Stock ROOTED deoxed FI27 OTA with agat recovery heimdall one click
Wanna learn more about Heimdall ?
http://www.glassechidna.com.au/products/heimdall/
Wanna learn about how to make your own one-click packages?
http://forum.xda-developers.com/showthread.php?t=1348392
Want AIO tutorial? Ask...
Credit goes toooo crawrj,Agat63,Adamoutler, and Benjamin Dobell, Chris41g,Sextape and anyone else who claims it lol or i forgot
I didnt do anything except know how to read and use a mouse so donate to the people i mentioned and not me . all credit goes to them for the respective files
Heimdall is cross platform compatible and open source this means it works on
LInux/Mac/WIndows
it is superior to ODIN
To run in linux open a Terminal where you downloaded the file and type
java -jar fi27rr.jar (or what ever you named the file)
mac and windows you just double click it
plug in your phone put in Download mode ( from it being off press and hold power+down) till splash or adb reboot download in console while on with adb on.
Caution this wipes data like Odin would and is safe to flash
DOWNLOAD Link:
fi27rr.jar - 352.40 MB
Enjoy!
Got a stupid triangle ? use triangle away. Id make a one click but the author asks to not redistribute. but it comes with a apk version and a tar version. Depending on what chainfire says ill make the next versions with it built in. Anyway heres the link:
http://forum.xda-developers.com/showthread.php?t=1494114
dos
ahhh mod please move this my bad its 6 in teh am here
Thanks again
i guess people should realise how handy these are gonna prove !!!
Thanks! I've been running linux and waitting for oneclicks!
Glad I can be of service if anyone wants anything else made in this manner lmk
As always, thank you for thee hard work.
Sent from my SPH-D710 using xda premium
I'm looking for known good firmware to use in heimdall for the Samsung Galaxy S II Epic 4G Touch by Sprint. It's a CDMA phone and finding firmware compatible with Heimdall is proving near impossible. I am studying my pit file to see if there is a way I can change my build files to output my binary image in the proper tar format for the d710. It's going to be a rather large undertaking, but if I am right, anyone would be able to provide me a pit file and if I'm correct, it would literally modify the manifest for android source, repo init for the flavor the user is looking for and build the heimdall image instead of the standard recovery image... It seems it would be easier though to take the standard flash image and strip from it the necessary stuff and repack it... Has anyone done this?
This is amazing have been waiting for this for a while as a mac user and it works well just tested. I hated switching to crappy windows to use odin thanks again 8D
slackguru said:
I'm looking for known good firmware to use in heimdall for the Samsung Galaxy S II Epic 4G Touch by Sprint. It's a CDMA phone and finding firmware compatible with Heimdall is proving near impossible. I am studying my pit file to see if there is a way I can change my build files to output my binary image in the proper tar format for the d710. It's going to be a rather large undertaking, but if I am right, anyone would be able to provide me a pit file and if I'm correct, it would literally modify the manifest for android source, repo init for the flavor the user is looking for and build the heimdall image instead of the standard recovery image... It seems it would be easier though to take the standard flash image and strip from it the necessary stuff and repack it... Has anyone done this?
Click to expand...
Click to collapse
thats pretty much what this is i think?
this is a known good firmware im kind of missing your point would you like just a tar package of the firm for just regular heimdall instead of a one click i can package that for you if you like... that is actually a feature of heimdall.. and you can download the pit from your current device as well to use for flashing open it and edit anyway you like. if you decompress the jar i provided you can pull the pit from it also.
you might need to elaborate a bit and ill see if I can help you.
manup456 said:
This is amazing have been waiting for this for a while as a mac user and it works well just tested. I hated switching to crappy windows to use odin thanks again 8D
Click to expand...
Click to collapse
yess meee toooo thats actually my reason for making this
@Dreamlogix
This plus the el29 is all wee need and continuing from here is great.
Quick question is there a way to this without messing with the flash count I have triangle away just would like to know also a data wipe version would be good just thinking also this should be a sticky for sure.
manup456 said:
@Dreamlogix
This plus the el29 is all wee need and continuing from here is great.
Quick question is there a way to this without messing with the flash count I have triangle away just would like to know also a data wipe version would be good just thinking also this should be a sticky for sure.
Click to expand...
Click to collapse
Hm i thought i enabled data wipe.. ill have to re-do it and ill post two versions (sticky on my second contribution? ) that would be amazing If a mod wants to sticky ill maintain it im pretty sure you just have to message them.
to get rid of the triangle i use triangle away here is the link it will reset your flash counter and get rid of the triangle redistribution is not allowed per order of the maker
i messaged chainfire to see if he will allow me to make a one click triangle away heimdall package for convince i can send you that one click privately but i cant post it. id like to integrate it for the later ones.
http://forum.xda-developers.com/showthread.php?t=1494114
but good point ill add that link to the op
thanks for being supportive i knew SOMEBODY could use it.
quick question did you test my el29 everything work out?
@ Dreamlogix
Yeah bro plz do send me that, and yeah i use triangle away just a one click all good it's always a plus. I appreciate this a lot.
manup456 said:
@ Dreamlogix
Yeah bro plz do send me that, and yeah i use triangle away just a one click all good it's always a plus. I appreciate this a lot.
Click to expand...
Click to collapse
cool should be in your pm do you currently got a yellow triangle? id like you to test it out and report back
upon investigation it seems to only remove the triangle image and not reset the flash counter. I inquired in CF' thread im pretty sure ill be able to come up with a package if he allows me
Dreamlogix said:
thats pretty much what this is i think?
this is a known good firmware im kind of missing your point would you like just a tar package of the firm for just regular heimdall instead of a one click i can package that for you if you like... that is actually a feature of heimdall.. and you can download the pit from your current device as well to use for flashing open it and edit anyway you like. if you decompress the jar i provided you can pull the pit from it also.
you might need to elaborate a bit and ill see if I can help you.
Click to expand...
Click to collapse
Great! That was what I meant to say. I am looking for the firmware files. I'm not interested in a one click although I may end up using it one day. I am in learning mode and you might as well say I am from Missouri... So as I said before, I am actually looking for known good "firmware" and it's great news that I can simply extract it from the jar. That sounds pretty straight forward. Does the jar include images, bins, lfs img and all that? I've been doing some study and there are 15 partitions on the SPH-D710, 7 of which are in use during runtime, 2 of which are in use at recovery and I still haven't figured out how to tell whats going on in the download state. No offense intended, but I am really more interested in learning to fish rather than eat from your catch if you know what I mean.
I found a description of what is called EMMC booting where after mapping out the layout of the partitions you build an x-loader appended with RAW eMMC headers, u-boot build system initramfs structure, the kernel's zImage except they called it uImage I guess for the u-boot system and the rest including system.img, userdata.img and cache.img. These instructions are fairly precise but they aren't written for our device even though our device does contain the hardware they refer to, the am37xevm. That's where they stop though. They don't get into the GANG partition, BOOT, EFS, SBL1 and 2 which I believe are the bootloader combined in one logical partition across 2 logical devices. Then there's the hidden partition which is looking for the hidden.img when performing a complete flash.
I am only wanting to be this thorough because I want to learn all I can and I believe that if I could make the serial interface active during boot up I could load this type of OS, external to the phone and make all of the partitions simultaneously available to manipulate. This would solve a lot of people's problems with the triangle and counter. Hell, I believe that with a large enough space your preexisting ROM could be completely backed up prior to flashing and then nothing would be stopping a completely new partition layout.
Just food for thought and I will grab that jar and see what I can't squeeze out of it. Thanks for letting me know. I didn't realize you left the jar open.
Dreamlogix said:
Hm i thought i enabled data wipe.. ill have to re-do it and ill post two versions (sticky on my second contribution? ) that would be amazing If a mod wants to sticky ill maintain it im pretty sure you just have to message them.
to get rid of the triangle i use triangle away here is the link it will reset your flash counter and get rid of the triangle redistribution is not allowed per order of the maker
i messaged chainfire to see if he will allow me to make a one click triangle away heimdall package for convince i can send you that one click privately but i cant post it. id like to integrate it for the later ones.
http://forum.xda-developers.com/showthread.php?t=1494114
but good point ill add that link to the op
thanks for being supportive i knew SOMEBODY could use it.
quick question did you test my el29 everything work out?
Click to expand...
Click to collapse
When I saw this post I said Amen! Dreamlogix, you can include me in that tar ball for the reset counter too!
Totally embarrassed ... RTFF
Dreamlogix said:
This is Stock ROOTED deoxed FI27 OTA with agat recovery heimdall one click
Wanna learn more about Heimdall ?
http://www.glassechidna.com.au/products/heimdall/
Wanna learn about how to make your own one-click packages?
http://forum.xda-developers.com/showthread.php?t=1348392
Want AIO tutorial? Ask...
Credit goes toooo crawrj,Agat63,Adamoutler, and Benjamin Dobell, Chris41g,Sextape and anyone else who claims it lol or i forgot
I didnt do anything except know how to read and use a mouse so donate to the people i mentioned and not me . all credit goes to them for the respective files
Heimdall is cross platform compatible and open source this means it works on
LInux/Mac/WIndows
it is superior to ODIN
Click to expand...
Click to collapse
with the exception of the triggering of the counter
To run in linux open a Terminal where you downloaded the file and type
java -jar fi27rr.jar (or what ever you named the file)
mac and windows you just double click it
plug in your phone put in Download mode ( from it being off press and hold power+down) till splash or adb reboot download in console while on with adb on.
Caution this wipes data like Odin would and is safe to flash
DOWNLOAD Link:
fi27rr.jar - 352.40 MB
Enjoy!
Got a stupid triangle ? use triangle away. Id make a one click but the author asks to not redistribute. but it comes with a apk version and a tar version. Depending on what chainfire says ill make the next versions with it built in. Anyway heres the link:
http://forum.xda-developers.com/showthread.php?t=1494114
Click to expand...
Click to collapse
If the execution of the jar causes a yellow triangle you should build in the functionality of wiping the triangle and counter automatically whether or not Chainfire likes that it's there. If the fix is open source and not given to you by Chainfire what harm can it do, I know Chainfire is selling the Triangle Away app, to make a flash that does not cause the triangle? Isn't that what a flash is supposed to do? Go on the phone without incident? I was thinking to ask for your guidance with this project to further it. I made a "jig" that actually has an SD card recepticle wired to it and I thought that maybe I could get the entire flash to boot "outside" the device so the spanning eMMC parttions could be rendered harmless. We could then at that point extract necessary proprietary code from the phone to integrate into the flash as it builds out on the phone on the fly. I appreciate the respect you gave to Chainfire though in not releasing the code you have to repair the triangle... I know if I look long enough and hard enough I will find it soon too, but it would be nice if both you and Chainfire shared without $ 2.00.
I really am eating my words here. Thanks and heavy shout outs to Chainfire for including TriangleAway-v2.10.apk on another post. I do still think that if the Heimdall Oneclick is known to cause the counter that some obscure coding in it to remove it would be prudent.
Then also, since I haven't done so yet, GREAT JOB on the Oneclick to Dreamlogix. The best idea I've had all day. I much prefer to use the opensource flash utility to ODIN. Thanks for both of your very hard work. It is appreciated.
My bad you cannot extract it out of the jar and Odin triggers the triangle also I and in not allowed to repackage chain fires code solo I can't make that for you guys sorry
Also do you want 100% stock with no root and stock recovery and to answer your question we do not have a gang or efs ( because its a cdma device) but we do have sbl1 and boot no sbl2 and yes they are part of the bootloaders efs is part of where the serial and some modem stuff is stored on gsm phones i believe.
sorry for the poor english been a long night lol
edit update if anyone boot loops at the 4g logo YOU ARE NOT BRICKED dont panic use a oem cable.
FAIL!
Alright, I attempted to flash, my already rooted SPH-D710 by executing sudo java -jar fi27rr.jar and this is what is happening:
First the GUI reports differently than the cli behind the scenes. Here is the out put from the Oneclick screen;
Operating System: Debian Based i686
Found Heimdall Version: Heimdall version is out of date.
Connect your device in Download Mode to procede.
Device Connected. Awaiting package preparation.
FI27+agat kernel+recovery FI27 is ready for your device.
Repartition was requested but bootloaders are not to be flashed.
Omiting Bootloaders.
KERNEL RECOVERY MODEM FACTORYFS HIDDEN
Heimdall v1.4 RC1
Copyright (c) 2010-2012, 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...
Checking if protocol is initialised...
Protocol is not initialised.
Initialising protocol...
Protocol initialisation successful.
Beginning session...
Session begun.
Downloading device's PIT file...
PIT file download successful.
Ending session...
Rebooting device...
Releasing device interface...
Re-attaching kernel driver...
Click to expand...
Click to collapse
Immediately following my device reboots. I suspect there is something wrong with the recovery partition itself. I am also experience an error when entering the download recovery that further indicates issues with the recovery partition. The recovery.do file has some specific commands referencing the CSC that can not complete because /system/etc/csc does not exist... another strange note, the GUI thinks PIT failed but the command line says otherwise and even stranger the GUI also says other wise:
View attachment 1415566
Meanwhile, back at Gotham, the CLI is sitting and waiting for the GUI to complete it's job which never happens and this is the output within the CLI:
sudo java -jar fi27rr.jar
[sudo] password for jeffrey:
Operating System: Debian Based i686
Found Heimdall Version:
Connect your device in Download Mode to procede.
Device Connected. Awaiting package preparation.
Total PITEntry Count: 15
Pit Complete.
Partition Targeted:1-BOOT
Partition Targeted:2-SBL1
Partition Targeted:10-FACTORYFS
Partition Targeted:13-HIDDEN
Partition Targeted:9-MODEM
Partition Targeted:6-KERNEL
Partition Targeted:5-PARAM
Partition Targeted:7-RECOVERY
FI27+agat kernel+recovery FI27 is ready for your device.
Total PITEntry Count: 15
Pit Complete.
Partition Targeted:1-BOOT
Partition Targeted:2-SBL1
Partition Targeted:10-FACTORYFS
Partition Targeted:13-HIDDEN
Partition Targeted:9-MODEM
Partition Targeted:6-KERNEL
Partition Targeted:5-PARAM
Partition Targeted:7-RECOVERY
[heimdall, flash, --pit, /tmp/rootHeimdallOneClick2ACBA745/pit.pit, --6, /tmp/rootHeimdallOneClick2ACBA745/zImage, --7, /tmp/rootHeimdallOneClick2ACBA745/recovery.bin, --9, /tmp/rootHeimdallOneClick2ACBA745/modem.bin, --10, /tmp/rootHeimdallOneClick2ACBA745/factoryfs.img, --13, /tmp/rootHeimdallOneClick2ACBA745/hidden.img]
<<<<<<<<<<< this is where the cursor hangs
Click to expand...
Click to collapse
This is the contents of /tmp/rootHeimdallOneClick2ACBA745/ :
drwxr-xr-x 3 root root 4096 Oct 19 14:56 .
drwxrwxrwt 21 root root 12288 Oct 19 17:17 ..
-rw-r--r-- 1 root root 131072 Oct 19 14:54 boot.bin
-rw-r--r-- 1 root root 486481476 Oct 19 14:56 factoryfs.img
-rw-r--r-- 1 root root 878 Oct 19 14:56 firmware.xml
-rwxr--r-- 1 root root 42268 Oct 19 14:55 heimdall_i386.deb
-rw-r--r-- 1 root root 8626468 Oct 19 14:56 hidden.img
-rw-r--r-- 1 root root 9111 Oct 19 14:57 log.txt
-rw-r--r-- 1 root root 15466656 Oct 19 14:56 modem.bin
-rw-r--r-- 1 root root 1060864 Oct 19 14:56 param.lfs
-rw-r--r-- 1 root root 4096 Oct 19 14:56 pit.pit
-rw-r--r-- 1 root root 8387840 Oct 19 14:56 recovery.bin
drwxr-xr-x 2 root root 4096 Oct 19 14:55 ROMPACKAGE
-rw-r--r-- 1 root root 1310720 Oct 19 14:54 Sbl.bin
-rw-r--r-- 1 root root 7476524 Oct 19 14:56 zImage
Click to expand...
Click to collapse
... and the ROMPACKAGE directory is empty. Now, I opted NOT to install the 1.31 Heimdall because I have a newer version. I am currently running 1.4-RC1 compiled from source out at BatMan's website (Benjamin Dobell - https://github.com/Benjamin-Dobell/Heimdall). The phone didn't act like this before I completed my first flash. I played around with the cli and the frontend with the pit file and the likes. It was nice I could load my own pit file and it recognized my device without restarting it. Then comes my first flash... it was StockCWM-EL26.zip that I extracted to a folder and simply flashed Kernel using zImage. The flash took, sort of, CWM showed up but none of my partitions could be recognized, at least none that counted. I couldn't mount internal or external storage... all the system partitions were fine. I downloaded that REPACK from chris41g's repo and that was why I was surprised it didn't work and suspect hardware issues. During this flash this is the PIT i used sph-d710.pit, if you even need it.
My next plan is to see if I can attempt repair of the troubled partitions. I hear that /dev/zero is going to be my friend for a bit, but I'm not looking forward to it. Worse comes to worse I'll be reactivating my crespo4g for a bit. It's been running CM10 reliably for a long while now. I'd be glad to part with contact info if you felt like brainstorming. My gmail should be on my profile page because of jabber... The phone is still working well so feel free to GTalk me if you want. I only hope I'm not truly as incompetent as this post makes me sound.
Fight the good fight, keep the faith!
Slackguru

[Q] Cyanogenmod 10 on boost mobile

So I decided to take the plunge and flash CM10 to my epic 4g flashed to boost mobile. The phone and text seem to work, besides having bad reception, but is there a way to get the data working using diag rx with CM10? I vaguely remember reading somewhere that this was not possible on CM10 and I've been trying to set the mms url using *#*#3282#*#* but it won't let me into the edit menu, I get a MODEM ERROR, "modem exception occurs". So is it possible for a noob to get CM10 working on boost or should I stop wasting my time and flash back to stock, or another ROM (recommendations appreciated). Thanks,
Questions go in Q&A
Thread moved
Sent from my SPH-L710 using xda premium
odin back to stock
So I attempted to odin back to stock fc09 but it hung up about 80% through with a green screen. I went to reboot into download mode again and now it won't show the battery at 0% when you plug in the cable and it doesn't let me access download mode unless I hold 1 and power with a fresh battery and no cable installed. This would be fine but now the computer only recognizes the device as an unknown device and odin won't detect it.
Does anyone know how to get windows to recognize the epic without booting into download mode with just the cable plugged in?
Heimdall (no front end) in ubuntu will write a recovery mode but I can't get it to boot into recovery. Here is the code
Code:
[email protected]:~/Downloads$ heimdall flash --recovery recovery.bin
Heimdall v1.3.1, 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...
Claiming interface...
Attempt failed. Detaching driver...
Claiming interface again...
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
Uploading RECOVERY
100%
RECOVERY upload successful
Ending session...
Rebooting device...
Re-attaching kernel driver...
OK so Heimdall saved the day with the stock FC09 and odin 1.8.5 pit file. Boots up like normal. I just need to find a good ROM that works well with Boost / diag rx and is rooted because I hate sprint's bloatware. Hope this helps someone else.
Code:
[email protected]:~/Downloads/SPH-D700-FC09-8Gb-REL$ heimdall flash --factoryfs factoryfs.rfs --cache cache.rfs --param param.lfs --kernel zImage --modem modem.bin --pit victory_8G_100528.pit
Heimdall v1.3.1, 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...
Claiming interface...
Attempt failed. Detaching driver...
Claiming interface again...
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
Uploading KERNEL
100%
KERNEL upload successful
Uploading MODEM
100%
MODEM upload successful
Uploading FACTORYFS
100%
FACTORYFS upload successful
Uploading CACHE
100%
CACHE upload successful
Uploading PARAM
100%
PARAM upload successful
Ending session...
Rebooting device...
Re-attaching kernel driver...
Note - I have the stock cable, this is probably why Odin failed. Heimdall stalled repeatedly but always picked back up after a minute or two.
OK so I got almost everything sorted out, except data still.
I want to run CM10 for my daily driver, but with boost every time you activate a different phone and then reactivate your donor phone the HA and AAA passwords change. So I want to either
1. Figure out how to edit the HA and AAA passwords for profiles 0 and 1 on CM10 and/or using QPST. I haven't been able to find any information on this so I'm not sure it's possible.
or
2. Set up dual boot with stock FC09 and CM10 so I can frequently update PRL's and HA / AAA passwords.
OR, last resort,
3. Flash the stock ROM using heimdall, edit passwords, then flash back to CM10. I don't want to have to do this all the time but I'm not sure if options 1 or 2 will work. If someone has done either of the first two options successfully please point me in the right direction. Thanks,
Tobey
Inert_Production said:
OK so I got almost everything sorted out, except data still.
I want to run CM10 for my daily driver, but with boost every time you activate a different phone and then reactivate your donor phone the HA and AAA passwords change. So I want to either
1. Figure out how to edit the HA and AAA passwords for profiles 0 and 1 on CM10 and/or using QPST. I haven't been able to find any information on this so I'm not sure it's possible.
or
2. Set up dual boot with stock FC09 and CM10 so I can frequently update PRL's and HA / AAA passwords.
OR, last resort,
3. Flash the stock ROM using heimdall, edit passwords, then flash back to CM10. I don't want to have to do this all the time but I'm not sure if options 1 or 2 will work. If someone has done either of the first two options successfully please point me in the right direction. Thanks,
Tobey
Click to expand...
Click to collapse
Download the stock boot from sdcard by wtogami then program to your preferences and reboot. then profit????
phonehunter59 said:
Download the stock boot from sdcard by wtogami then program to your preferences and reboot. then profit????
Click to expand...
Click to collapse
I found this, I'm going to give it a try.
http://epiccm.blogspot.com/2012/01/boot-el30-stock-from-sdcard.html?m=1
That's what I meant lol
Sent from my SPH-D700 using Tapatalk 2
phonehunter59 said:
That's what I meant lol
Sent from my SPH-D700 using Tapatalk 2
Click to expand...
Click to collapse
I'm thinking it will allow me to write with QPST to the internal radio settings while leaving the ROM on the phone intact. It's somewhat like a live cd for a computer. Haven't tried it yet but looks promising. Right now I'm on 1x data, talk and text after flashing to the people's rom, editing the QPST settings and then re flashing to CM10. I didn't update the 1192 files or anything, just the HA and AAA passwords. I'll do a complete update with the SD card boot once I have time, and see if I can get the 3g working.
Inert_Production said:
I'm thinking it will allow me to write with QPST to the internal radio settings while leaving the ROM on the phone intact. It's somewhat like a live cd for a computer. Haven't tried it yet but looks promising. Right now I'm on 1x data, talk and text after flashing to the people's rom, editing the QPST settings and then re flashing to CM10. I didn't update the 1192 files or anything, just the HA and AAA passwords. I'll do a complete update with the SD card boot once I have time, and see if I can get the 3g working.
Click to expand...
Click to collapse
That should work, i did that for my friend who was on cm9 at the time
Sent from my SPH-D700 using Tapatalk 2

How I rooted my Note 3 (t-mobile) using a MAC

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

Fear I May Have Bricked Device

I recently bought a new Samsung Galaxy Tab Pro 8.4 tablet, and not being satisfied that it's only running Android 4.4.2, I attempted to take care of that myself.
I believe I may have written over the OS with the recovery while using some bargain basement recovery flashing program instead of doing it by hand and using Heimdall.
Here's what I'm currently experiencing
-Whenever I try to boot into the device, I get stuck, indefinitely on the Samsung Galaxy Tab Pro loading screen.
-I have tried to utilize the recovery to try to restore to factory settings, to no avail.
-I have tried to flash a new recovery to the device using Heimdall with the following results
sudo heimdall flash --RECOVERY recovery.img --no-reboot
Heimdall v1.4.0
Copyright (c) 2010-2013, 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...
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...
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...
Re-attaching kernel driver...
-------
I am not sure what to do to currently fix the issue, I think if i re-write the entire partitions with a brand new ROM it could fix the problem entirely....however I'm not entirely sure how to go about that.
It appears that my pc and tablet are not wanting to communicate on this front at all. As all communications between the two inevitably ends in failure in download mode.
If anyone has any advice or suggestions I would be most appreciative
I also haad the idea of trying to adb flash the files over, but with the way Samsung's seem to be set up, I do not believe that is a viable option
I'd use Odin and download the ROM from Sammobile.com
Sent from my SAMSUNG-SM-G900A using XDA Premium HD app

I'm having problems installing LineageOS using Heimdall on my Galaxy S7

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.

Categories

Resources