Develop Bugs

[Q] Help with ROOT and SGS3 Toolkit 7.0

Hey guys, longtime lurker, new poster. Lots of help from reading this board. I bought my SGS3 in August last year, and rooted it with the "no trip the counter" style root. I forget which one it was exactly. I didn't install Clockwork Mod or TWRP.
Fast forward to today, and I am trying to play around with my phone. So, I decide to look in the "About device/ status/ device status/" and it is listed as modified. This means it will not update to Jelly Bean. OH NOES! So thats why it didn't OTA update!
So, I download SGS3 toolbox and proceed to putter.
I decide that I will unroot the phone first and see what that does for me.
So, I go into SGS3 toolkit using the following options:
do not update, I pick my model (41. Android 4.04 [Build IMM76D ALG1]) and it goes to the main menu.
I pick option 2. Root/unroot device and read all the options. I pick Number 7 (unroot, etc.). This is where it goes sideways (I think). I read the prompt, and decide to tell it I do not have a custom recovery flashed.
I pick option 2 TWRP and it goes into download mode. ODIN opens. I pick the correct file (I read everything, as usual) and flash my phone. So far so Good.
SGS3toolkit asks me to pick a flash choice. I pick 2 (sideload root file). I press the any key
**************
I just noticed I have a driver issue. Will reboot pc and continue this in a few minutes. If you are reading this, check back soon. I'll keep you posted. GRRRR...
***************
OK, this is a tricky one. The drivers install fine, and the phone gets recognized. SGS3 Toolkit 7 recognizes the phone and it has the serial number. However, when in TWRP, it is supposed to install another driver of some sort, but on my PC, I look in "Devices and Printers" and look around, it lists my SGS3 as this:
{
"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"
}
Any suggestions? Uninstalling and reinstalling the Samsung USB drivers, running Ccleaner, and rebooting and reinstalling hasn't helped. What next, scrub the registry?
Thanks!

When you uninstalled the drivers, did you: uninstall, reboot pc, disconnect from Internet, connect s3 and install?
I believe you were rooted initially? I would have simply made a nandroid, wiped and flashed the latest stock firmware via odin

xBeerdroiDx said:
When you uninstalled the drivers, did you: uninstall, reboot pc, disconnect from Internet, connect s3 and install?
I believe you were rooted initially? I would have simply made a nandroid, wiped and flashed the latest stock firmware via odin
Click to expand...
Click to collapse
I did all of the above except disconnect from the internet. Just to be clear, the phone is still completely functional (i guess I didn't explicitly state that). Why would a live internet connection impact this?
Also, what driver is messing up in my photo? Is it a special driver of some sort?

jeraldjunkmail said:
I did all of the above except disconnect from the internet. Just to be clear, the phone is still completely functional (i guess I didn't explicitly state that). Why would a live internet connection impact this?
Also, what driver is messing up in my photo? Is it a special driver of some sort?
Click to expand...
Click to collapse
Search for samsung drivers on this forum and download them. When you install a new device, it looks online for the drivers. You don't want those.
I figured the phone was working, I just would have used odin to flash the latest firmware, wiped and been done. Would have saved doing all those steps

xBeerdroiDx said:
Search for samsung drivers on this forum and download them. When you install a new device, it looks online for the drivers. You don't want those.
I figured the phone was working, I just would have used odin to flash the latest firmware, wiped and been done. Would have saved doing all those steps
Click to expand...
Click to collapse
So, no luck on the going offline and redoing the drivers. I am pretty thorough about how I do it too. Any ideas? Specifically, does anyone know what is going on the picture I posted?

jeraldjunkmail said:
So, no luck on the going offline and redoing the drivers. I am pretty thorough about how I do it too. Any ideas? Specifically, does anyone know what is going on the picture I posted?
Click to expand...
Click to collapse
Bump... Anyone? I suspect it is because I am using windows 8, but not sure. I'd have to load up a copy of XP somewhere..

I have similar issues. Windows8 doesn'tplay nice. Ive reloaded drivers run compatible mode. Odin kies etc phone will not connect properly to pc with 8.
Sent from my SAMSUNG-SGH-I747 using xda app-developers app

SOLVED!!! Windows 8x64 and ADB Sideload driver on SGS3
scramble88 said:
I have similar issues. Windows8 doesn'tplay nice. Ive reloaded drivers run compatible mode. Odin kies etc phone will not connect properly to pc with 8.
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
Click to expand...
Click to collapse
Need 10 posts to post an url that solves this!!! Sorry for spamming the forum, will keep it in this thread!

jeraldjunkmail said:
Need 10 posts to post an url that solves this!!! Sorry for spamming the forum, will keep it in this thread!
Click to expand...
Click to collapse
Blah Blah Blah

jeraldjunkmail said:
Blah Blah Blah
Click to expand...
Click to collapse
Blah Blah Blah!

jeraldjunkmail said:
Blah Blah Blah!
Click to expand...
Click to collapse
Furthermore, Blah Blah Blah!

jeraldjunkmail said:
Furthermore, Blah Blah Blah!
Click to expand...
Click to collapse
To which, I would reply, Blah Blah Blah. Really, I have a fix for this problem...

jeraldjunkmail said:
To which, I would reply, Blah Blah Blah. Really, I have a fix for this problem...
Click to expand...
Click to collapse
But FIRST, blah blah blah!

SOLVED!!! Windows 8x64 and ADB Sideload driver on SGS3
OK, I solved it. EXTREMELY OBSCURE. Credit goes here:
http://blog.dantup.com/2012/10/fixing-adb-device-not-found-with-nexus-7-in-recovery-mode
In order to save you the hassle, because I changed a couple other tiny things, here are the files.
https://docs.google.com/file/d/0B22uHLqOAaf9Yk8xaERzZklITjA/edit?usp=sharing
You will need to reboot your computer into PC Settings, General, Advanced Startup and choose Install drivers in unprotected mode (because this is a hacked driver). Than go to where you put this file (usually in C:\Program Files\SAMSUNG\USB Drivers\25_escape), right click it and select install. I have confirmed that this works on my SGH-I747 ATT phone.
I am by no means a programmer, but am alright with Windows stuff. This is my fix for this problem. Enjoy!

A lot of work just to get stock version of JB. ODIN and MrRobinson method would have worked and had you running in under half an hour...that includes downloading files if you have a decently fast internet connection.
With mobile ODIN no drivers required.
Sent from my SAMSUNG-SGH-I747 using xda app-developers app

aybarrap1 said:
A lot of work just to get stock version of JB. ODIN and MrRobinson method would have worked and had you running in under half an hour...that includes downloading files if you have a decently fast internet connection.
With mobile ODIN no drivers required.
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
Click to expand...
Click to collapse
Perhaps, but this works, and having working drivers for th SGS3 on Win8 is a bit of an issue some have had, so I fixed it. With Google, they will hopefully find this thread and the file and have to do much less than me.

Tutorial: How to use KIES Emergency Firmware Recovery (EFR)

Edit Nov 28 2013: GN3 Owners PLEASE READ!
As of the new update the ATT Galaxy note 3(possibly all carriers) IS NOT compatable with KIES EFR!
This includes KIES 2.XX and KIES 3! What does this mean?
If you took the MJ5 update you will no longer be able to use the KIES Emergency Firmware Updater.
Please complain to Samsung, locking the bootloader is one thing but no EFR??
Would you get on ship with no life boats or life preservers??
Seriously uncool of Samsung to do this.
-end of edit
/rant
So its come to my attention a lot of new guys are getting stuck soft brick, bootloop, borked recovery etc.
So .... I made this tutorial for everyone.
Please: dont flame or post useless comments.
Its great for you Odin is easy, but I made this for people who want a hassle free easy way to recover their phone.
This is also imo the fastest and easiest way back to true stock w/o a "modified"
Some people have reported a flash count of 1 but idk I always went back to 0.
If you are new, have no rooting, rom flashing or w/e experience, imo you should NOT be using odin until you have completely read up on it. I mean hey some of you super geniuses have no probs but when I see posters who have no clue about usb drivers or even how to use kies, im confused why you would want to venture to odin? 500 $ is a very expensive brick.
Ok so unsure about odin or just new and now you just borked your brand new phone?
First things first:
Can you get into dl mode.
Dont worry about recovery mode because it doesnt matter for this. This works with corrupted recovery as well.
For now lets just say download mode is achieved one way only:
Press : vol down power and home key all at the same time. Release quickly when you see the screen come up. Takes practice some times.
:thumbup: This method will remove "modified" status from your phone! :thumbup:
:beer:
Ok ready? You want step by step you got it.
If this doesnt work you are doing it wrong, so try again. Even with Odin you may have to try several times, its the nature of android.
If you can get into DL mode you CAN 100% recover your device.
If it doesnt work or you get an error, you are doing this wrong. I am pretty sure this is for ALL Samsung phones but I can only confirm this for my gs3 and note2.
Keep in mind: I corrupted my recovery on my gs3 several times and this still worked. I will assume the same for my note 2.
Download kies from samsung.com
Follow the prompts but no need to install the stupid codecs.
When you are done, (dont forget hit "yes" to dl current usb drivers)
ON your computer "run as administrator" the kies icon.
make sure you are connected to the internet.
Kies will automatically check for updates and proper usb drivers.
No need to install "myfree codecs" hit no on that.
every thing else hit yes
Step one:
Run kies as administrator as I said And do all the usb updates, kies updates
but leave the codec thing alone.
Step by step instructions just follow the pics in order:
1.Kies opens asks about update
{
"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"
}
2.
3.Dont worry about this
4. Now in top left corner hit "tools" tab. Ignore everything else
5. After clicking tools tab click the emergency fimrware recover choice as described below
6. For now ignore this button. YOu might need it later but ignore it for now
7.
8.Well last step. Hit emergency recovery ( the "ok" button wont be there )
this will probably take 20 to 30 min total. The EFR will let you know if its succesfull or fail.
IF it fails try using the method I said to ignore. Its the same thing just an extra step of in putting your phones exact model number.
Heres some xtra links: (Thanks to Bajanman for finding these btw!)
http://www.sammobile.com/firmwares/1/
http://www.sammobile.com/kies/
http://m.samsung.com/us/support/

Nice help guide for noobs.
Good guide freak :thumbup:
Might want to go back and check some of your words tho. Lot of them misspelled... lol
Side note: All my years with Sammy I've never used Kies with any of my phone's!!
Sent from my SAMSUNG-SGH-I317 using Xparent SkyBlue Tapatalk 2

yeah yeah yeah

Nice tut freakboy i just hope I dont need to use it someday I subscribed anyways who know flashing games always full of surprises.
Sent from my SAMSUNG-SGH-I317 using xda premium

Please HELP
i have an at&t galaxy note 2 was rooted got OTA update now no signal and when i go to mobile networks (under settings) it says insert sim card so i am trying to do it your way and i have updated everything (drivers and kies) and when i try to connect to kies it says my device isn't supported by kies and there is no phone model in the white box to use the "emergency recovery using recovery code" is there a place to get this code?
Please help

Well first off there shouldnt be a need to use the kies efr with just an ota.
You can select your phone model manually.
Can I ask...did you install a recovery and make a bu after you rooted ?
im not familiar with these newer ota probs, I remember on my dx ota was no biggie due to rootkeeper. Its strange that a stock rooted phone gets borked with an ota.
Can you get into recovery?
Can you get into dl mode?
Im subscribed to this thread so ill try n help out
Edit: are you using this method because you are unfamiliar with odin?

i did install CWM recovery
i don't remember making a back up but i am sure i did
i can NOT get to recovery
i can get to dl mode
i am familiar with odin but i am on my work computer as i don't have internet at home at the moment so i cant run searches as it trips the big brother software here and i would get in trouble the phone seems to work fine other then it doesn't recognize the sim card and no recovery mode
but if i could find a stock rom i could just flash with odin

That may also be your problem.
Are you running kies as admin?
Sorry if these sound like stupid questions.
But 8f you dont have admin privies kies may not work.
Regardless there is a drop down for you to manually choose your phone.
You do have usb debugging?
A corrupted recovery should not affect your ability to use kies.
Your jobs software could be blocking it.

Also you do realise you cannot take ota with custom recovery?
Thats why your phone is borked.

i do realize it now lol but i didnt even think about it when it happened
yes running kies as admin
no to usb debugging don't event remember how to get to usb debugging but if it is in settings under mobile networks i cant get there it just says insert sim card

Justvto be sure this is an sgh-i317 correct?
Try doing the upgrade first that may give you the code.
First make sure you have usb debugging
Home>Settings> developers options> make sure usb debugging is checked.
Also since it sounds like your recovery is corrupted do not do a factory reset.

Ok so try this:
Make sure you have latest drivers from samsung for YOUR device.
Make sure kies is the latest version.
Make sure antivirus is off orvput kies in the whitelist/allowed.
Turning off is better.
Go to dl mode on phone .
Sincevkies is already running go to thetop menu :
tools> emergency firmware recovery
You should get a drop down list of devices. If this is an att phone and not another carrier model ported to att, you should choose sgh-i317 (att galaxy note 2). You shouldnt need a number thats only if you try to upgrade and it fails ( as I mentioned you may want to try upgrade first to trick the que to give you a number)
Post back.

+1
Sent from my SGH-I317M using xda premium

freakboy13 said:
Ok so try this:
Make sure you have latest drivers from samsung for YOUR device.
Make sure kies is the latest version.
Make sure antivirus is off orvput kies in the whitelist/allowed.
Turning off is better.
Go to dl mode on phone .
Sincevkies is already running go to thetop menu :
tools> emergency firmware recovery
You should get a drop down list of devices. If this is an att phone and not another carrier model ported to att, you should choose sgh-i317 (att galaxy note 2). You shouldnt need a number thats only if you try to upgrade and it fails ( as I mentioned you may want to try upgrade first to trick the que to give you a number)
Post back.
Click to expand...
Click to collapse
thanks so much for all your help there is no drop down box on my version of kies however i found stock firmware some where else and it is working now again thanks so much

mrnewspaper said:
thanks so much for all your help there is no drop down box on my version of kies however i found stock firmware some where else and it is working now again thanks so much
Click to expand...
Click to collapse
Nice job! Isnt it great figuring things out yourself?
Love hearing happy endings!
Now... go into recovery and :
Make a backup/boot img .
:thumbup:

Hello,
I am trying to fix my Korean Note 1. It is not being listed in the list of devices. I have it in D/L mode but it isn't listed. Can I use the code and, if so, what is the right code?

activepassive said:
Hello,
I am trying to fix my Korean Note 1. It is not being listed in the list of devices. I have it in D/L mode but it isn't listed. Can I use the code and, if so, what is the right code?
Click to expand...
Click to collapse
Hmmm not that familiar with note 1 or international version but ill assume its the same?
If you are not listed in the database you may want to try using odin.
The code needs to be generated by kies.
Is kies recognizing your phone?
I may be mistakwn but isnt their a kies for your country or some thing like that?
Have you submited this question in your forum?
Edit: I found this I hope it helps you!
http://forum.xda-developers.com/showthread.php?t=1740367
sent from my T.A.R.T.I.S
(Time And Relative Tarts In Space)

so this will restore my phone to stock and will instal stock recovery and reset my flash counter and modified status? no need for tiangle away and unroot??

i tried doing exactly what was in the OP and it's now stuck at 0% at restoring. It's given me an error message a few times before and i tried again but it still stays at 0%. I tried doing it with the button you said not to click and running as admin.
Now i've got two problems, one is the phone not getting out of this mode and 2 is it not even giving me an error message meaning i can't try again since it's still busy restoring.
What can i do now? Should i just pull the plug out of it and try again? Will this not break anything?
What should i do now OP?
further info:
model: galaxy S3 GT-19300
i've had it rooted using CF-root and i did a firmware update to trigger emergency recovery mode.
I got into emergency recovery mode on purpose but expected to get out of it...
---------- Post added at 08:03 PM ---------- Previous post was at 07:10 PM ----------
Hooray! it's now actually installing it and i didn't mistake it for downloading this time. I switched USB ports and now it works apparently.
Also something people that do this in the future should know: if you unplug the cable, it just gives you the error message saying that it couldn't find it which shouldn't cause any trouble. BUT only do this once it is stuck at 0%.

Possibly stupid question..
Having rooted the Note 2 att with mr skips toolbox, I then noticed a few days later the modified status.. So due to concern for warranty being voided, I'd like to return to stock: ( Heres the stupid question part).. I did install stock recovery via same toolbox, But How do I tell if it is stock vs twrp? I dont see where/how to check if it succeeded. Next- Why wont factory reset work to clear the flash counter, modified status to normal with full wipe? and as much as I admire mr Cortex method to full wipe ( 10 min process..) is that repetitive process of wiping, triangle away,unroot, reroot etc..necessary? I had a rooted samsung epic 4g touch before this note 2 and All I did to return phone to stock firmware for trade in was factory reset! yes- it was Not jellybean, was Gingerbread android.
Perhaps someone or some devs can explain this bit of mystery to me, and perhaps others... who are in search of a more direct and straightforward reset without complicating the steps. I will probably reroot and run a custom rom after warranty runs out.. but for now..stock again.

[Q] How To Root Samsung Galaxy SPH-D700 Epic 4G Using A Macbook Pro OS 10.8.4

Hey everybody,
I've researched this topic for days and I'm not coming up with any good solutions here.
Essentially, I am trying to figure out what the best firmware as of current date that runs really well on the Samsung Galaxy SPH-D700 Epic 4G.
I'm on 2.3.6 currently and from what I know the latest firmware for Android is 4.3 Jellybean. Is Jellybean available for the SPH-D700? If so, does it run well? If not, what's the next best alternative?
How do I root this phone using a Macbook Pro? I've read about "Wine", "Wine Bottler", "Heimleter" ( I don't think that's how it's spelled but I'm sure some of you know what I am talking about )
From what I have read, Wine doesn't seem like it's going to be very effective. Heim is more of a manual root which I could do but there isn't really a straight forward set of directions. The directions I've found have been written by many different sources and neither of them are the same.
If anybody has suggestions, I would greatly appreciate some. This will be the officially the 2nd phone I've ever rooted, the first being an HTC Hero and my 2nd droid phone ever owned.

DarkXShadowX21 said:
Hey everybody,
I've researched this topic for days and I'm not coming up with any good solutions here.
Essentially, I am trying to figure out what the best firmware as of current date that runs really well on the Samsung Galaxy SPH-D700 Epic 4G.
I'm on 2.3.6 currently and from what I know the latest firmware for Android is 4.3 Jellybean. Is Jellybean available for the SPH-D700? If so, does it run well? If not, what's the next best alternative?
How do I root this phone using a Macbook Pro? I've read about "Wine", "Wine Bottler", "Heimleter" ( I don't think that's how it's spelled but I'm sure some of you know what I am talking about )
From what I have read, Wine doesn't seem like it's going to be very effective. Heim is more of a manual root which I could do but there isn't really a straight forward set of directions. The directions I've found have been written by many different sources and neither of them are the same.
If anybody has suggestions, I would greatly appreciate some. This will be the officially the 2nd phone I've ever rooted, the first being an HTC Hero and my 2nd droid phone ever owned.
Click to expand...
Click to collapse
v4.3 isn't released yet, that I'm aware of, but v4.2.2 is released and stable (mostly).
For most yes it does run well, but for me JB roms and my list of apps installed leaves ~3-9MB of RAM remaining. So that causes crazy lag and is incredibly annoying. You basically have to try it out yourself with your apps and decide if it'll work for your needs.
You can use Odin (in Windows via bootcamp), or Heimdall (in Linux and possible OSX).

nikon120 said:
v4.3 isn't released yet, that I'm aware of, but v4.2.2 is released and stable (mostly).
For most yes it does run well, but for me JB roms and my list of apps installed leaves ~3-9MB of RAM remaining. So that causes crazy lag and is incredibly annoying. You basically have to try it out yourself with your apps and decide if it'll work for your needs.
You can use Odin (in Windows via bootcamp), or Heimdall (in Linux and possible OSX).
Click to expand...
Click to collapse
I don't have a Windows via bootcamp. I deleted that from my Mac last year. Is 4.2.2 available for the Epic 4G?
Do you have any good sources for how to root the Epic 4G from 2.3.6 to 4.2.2? It's been quite a long time since I've rooted. Thanks.
I would like to get my phone to be all set up with this.
http://forum.xda-developers.com/showthread.php?t=2131117

Well rooting or flashing a custom rooted rom is easy, if you can use Odin in Windows. I'm not familiar with Heimdall enough to give you a tutorial.
I posted this in a thread halfway down page 1 of Q/A:
nikon120 said:
TWRP: Flashes through CWM; OR you can pull the recovery.bin file from the zip file and flash that in Odin.
Root:
Power down device
Open keyboard, press and hold both the 1 key and power button. This places the phone into download mode.
Plug the device into your computer, and most likely drivers will install. Allow that to finish before proceeding.
Within Odin, wait until you see COM and a port number appear. That means your phone is recognized.
Next, uncheck all boxes on the left side, including auto-reboot.
Place the victory_8G_100528.pit file in the PIT box. Place CWM v5.0.2.7 .bin/.tar/.md5 file in the PDA box.
Click start and will complete relatively quickly.
Disconnect the phone from USB and pull the battery out.
Replace battery.
Press and hold Vol down, Camera and Power buttons until the capacitative lights light up, then release. This will place you in recovery mode.
From there you will boot into CWM, where you can flash whatever you want (custom rom or a compatible kernel for FC09 & SuperSU) off the SD card. So place those files prior to doing all the above.
Keep in mind, that if you want to remain on stock FC09, but rooted, you will need to flash a custom kernel. The stock kernel will replace CWM with stock recovery every time. That is why in the list above you must disable auto-reboot and battery pull.
All files are in my devhost, in my signature. If not, then they expired and I can reupload them if notified.
Click to expand...
Click to collapse
Just flash Avatar rom from your SD card when booted into CWM v5.0.2.7. Typically when coming from stock, you will be rebooted into a newer version of CWM that is MTD compatible and have to go through the same flashing steps as you just performed to flash Avatar. If you are still on the same CWM version (5.0.2.7), then you need to manually flash either TWRP (2.6.0.0 is current) or CWM (6.0.3.2 is current) before attempting to flash Avatar again.

Unfortuantely, Odin doesn't work for mac. Wine/Wine Bottler is extremely unpredictable. All I need is a way to root my Sph-D700 using the latest version of Mac OS without Windows via dualboot.
Heimdall seems to be the best solution but to be honest, I don't quite understand the procedure. I tried to do it earlier and I didn't have any luck. Since I'm posting this from my phone currently, I'll post the sources I tried in a bit when I jump back on the computer.
Here are the sources I have been trying to use:
http://wiki.cyanogenmod.org/w/Install_CM_for_epicmtd
http://www.glassechidna.com.au/products/heimdall/
http://www.youtube.com/watch?feature=player_embedded&v=1ILk3Dlo9Gg
Here are the steps I've tried taking.
1st Step: I download DRockStar's ClockworkMod Recovery
{
"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"
}
2nd Step:
I download Heimdall Suite 1.4RC1 Command-line Binary:
Place the libusb-1.0.0.dylib library from the zip inside /opt/local/lib on the machine.
I don't know where this folder is on my Mac. I've searched for it and it doesn't exist and it also doesn't specify where I should create it if necessary.
Building From Source: The source code for the Heimdall Suite is available on Github. For more details about how to compile the Heimdall Suite, please refer to the README provided on Github or refer to the instructions to Install and compile Heimdall.
I don't quite understand how to do this earlier. I'm pretty familiar with xCode since I am being taught how to use it from my University. Even with that being said, I'm still not understanding exactly how to build it from the source. I read through the read me and it seems a bit more advanced than what I know how to do. Even with following instructions, it's very confusing to follow.
Booting the phone into download mode is a given to me.
This doesn't relate to me since I am using a Mac.
Number 4: Place DRockStar's ClockworkMod Recovery file into the Heimdall directory.
I'm not sure exactly what this is asking to be honest.
Putting phone into download mode....
Here's what I type into Terminal. I've tried with and without Sudo and I always get the same error.
Also, Heimdall version 1.40 doesn't even recognize my device.
I also tried selecting the Avatar zip from the sd card from going into "Apply update from sdcard" and I got the following error.
This is where I am basically stuck at. I'm not sure what else to do honestly.

DarkXShadowX21 said:
This is the tar file I downloaded:
Zedomax Epic Touch Kernal v3.
Click to expand...
Click to collapse
Don't use that file. It's for the D710, aka Epic Touch.
Sent from my Nexus 7 using Tapatalk 2

nikon120 said:
Don't use that file. It's for the D710, aka Epic Touch.
Sent from my Nexus 7 using Tapatalk 2
Click to expand...
Click to collapse
Which file should I be using? I updated my last post with a bunch on information by the way.

To anyone else following this, I have responded on the Github issue:
https://github.com/Benjamin-Dobell/Heimdall/issues/149

DarkXShadowX21 said:
Hey everybody,
I've researched this topic for days and I'm not coming up with any good solutions here.
Essentially, I am trying to figure out what the best firmware as of current date that runs really well on the Samsung Galaxy SPH-D700 Epic 4G.
I'm on 2.3.6 currently and from what I know the latest firmware for Android is 4.3 Jellybean. Is Jellybean available for the SPH-D700? If so, does it run well? If not, what's the next best alternative?
How do I root this phone using a Macbook Pro? I've read about "Wine", "Wine Bottler", "Heimleter" ( I don't think that's how it's spelled but I'm sure some of you know what I am talking about )
From what I have read, Wine doesn't seem like it's going to be very effective. Heim is more of a manual root which I could do but there isn't really a straight forward set of directions. The directions I've found have been written by many different sources and neither of them are the same.
If anybody has suggestions, I would greatly appreciate some. This will be the officially the 2nd phone I've ever rooted, the first being an HTC Hero and my 2nd droid phone ever owned.
Click to expand...
Click to collapse
Have you tried using heimdall and the instructions found here?

Odin PIT file

Any chance anyone can Dropbox me a link to the latest pit file? Much appreciated.

An extremely simple Google search finds this.
http://forum.xda-developers.com/showthread.php?t=1848266
At least take the time to look stuff up before you create yet another thread.

** Update: sorry, I was in the wrong tab, thought this was my thread. I need the same file here, and have tried what you suggested already. http://forum.xda-developers.com/showthread.php?p=48257903&posted=1#post48257903
CNexus said:
At least take the time to look stuff up
Click to expand...
Click to collapse
I spent a few days going through all threads - this one included.
The PIT he listed fails when flashing through Odin - tried with 1.85 and "v3" which seem to be the two most used on the forums.
I tried both the file listed here http://invisiblek.chickenkiller.com/pits/ and the one attached as "out.pit" in the thread directly.
With Odin3, it doesn't fail - it just hangs indefinitely on "Initialization".

OK……Thanks All.…
Sent from my Nexus 7 using xda app-developers app

CorporalMaxSterling said:
** Update: sorry, I was in the wrong tab, thought this was my thread. I need the same file here, and have tried what you suggested already. http://forum.xda-developers.com/showthread.php?p=48257903&posted=1#post48257903
I spent a few days going through all threads - this one included.
The PIT he listed fails when flashing through Odin - tried with 1.85 and "v3" which seem to be the two most used on the forums.
I tried both the file listed here http://invisiblek.chickenkiller.com/pits/ and the one attached as "out.pit" in the thread directly.
With Odin3, it doesn't fail - it just hangs indefinitely on "Initialization".
Click to expand...
Click to collapse
what do you need . i have 16gb sprint pitt.

kaos420 said:
what do you need . i have 16gb sprint pitt.
Click to expand...
Click to collapse
Awesome! Yeah I think the PIT file should do it.
I tried flashing another one through Odin that claimed to be 16GB Sprint as well, but it just said write error and failed.
If this doesn't work, I'm not sure what else I can do.
Please post the file and I'll try it out, thanks!

CorporalMaxSterling said:
Awesome! Yeah I think the PIT file should do it.
I tried flashing another one through Odin that claimed to be 16GB Sprint as well, but it just said write error and failed.
If this doesn't work, I'm not sure what else I can do.
Please post the file and I'll try it out, thanks!
Click to expand...
Click to collapse
http://www.androidfilehost.com/?fid=23252070760972325
i have uses it both on mine and my wifes without a single issue. should work for you.
use this odin http://www.androidfilehost.com/?fid=23252070760972329

kaos420 said:
http://www.androidfilehost.com/?fid=23252070760972325
i have uses it both on mine and my wifes without a single issue. should work for you.
use this odin http://www.androidfilehost.com/?fid=23252070760972329
Click to expand...
Click to collapse
OK now I'm really confused. It didn't take it the first few tries, but rebooting both computer and phone a couple times got it to flash the PIT file successfully.
{
"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"
}
So then I closed Odin, disconnected & restarted the phone...
Got back into download mode, re-opened Odin, re-connected USB (to a powered port).
Chose the usual CF auto root I've used a bunch of times (actually the same file I had on the computer from the first time I rooted)...
Missing PIT info again.

Why does it say epic 4G. This is for s3.and why are you using cf auto root? Just push a recovery with odin. Then flash rom from recovery.
Sent from my SPH-L710 using Tapatalk

dude 1. your odin says epic 4g
2 that file your using says 720 not 710. is it even for the s3.

kaos420 said:
dude 1. your odin says epic 4g
2 that file your using says 720 not 710. is it even for the s3.
Click to expand...
Click to collapse
I know it's been a few hours. But you are 100% correct, the file he is using is definitely for the GS4. SPH-L720.
GS4 Stock Rooted MJA 4.3,Philz Touch CWM,HotSpot Mod,Transparent Weather Widget...

Something is screwy here.

metalfan78 said:
Something is screwy here.
Click to expand...
Click to collapse
yup. id hate to see someone brick cause of user error. we did what we could. if he doesn't sound back then i guess he realizes he messed up. or is a troll.

Yep, I concur

kaos420 said:
dude 1. your odin says epic 4g
2 that file your using says 720 not 710. is it even for the s3.
Click to expand...
Click to collapse
dude, odin says whatever you want it to - it's just a crap ini file with a title field:
and you're right about it being an L-720 (Galaxy S4) file - but actually it was just mislabeled and I didn't bother fixing it. the other copies I downloaded of CF's auto root didn't work either.
I do have the stock recovery, and tried flashing that, but it didn't work either.
It just doesn't want to write the PIT partition for some reason.

CorporalMaxSterling said:
OK now I'm really confused. It didn't take it the first few tries, but rebooting both computer and phone a couple times got it to flash the PIT file successfully.
So then I closed Odin, disconnected & restarted the phone...
Got back into download mode, re-opened Odin, re-connected USB (to a powered port).
Chose the usual CF auto root I've used a bunch of times (actually the same file I had on the computer from the first time I rooted)...
Missing PIT info again.
Click to expand...
Click to collapse
what i did was first flash pit. selected repartition. didnt reboot phone. i exited odin then restarted odin. selected pit file again. then as well selected tar flashed with both selected went fine. but im also on odin 3.07 maybe try the newer odin its in the files i linked.

Just use the .PIT at same Time with PDA to Full Fix!
kaos420 said:
what i did was first flash pit. selected repartition. didnt reboot phone. i exited odin then restarted odin. selected pit file again. then as well selected tar flashed with both selected went fine. but im also on odin 3.07 maybe try the newer odin its in the files i linked.
Click to expand...
Click to collapse
Just use the .PIT at same Time with PDA to Full Fix! I don't know why you want to repartition and then try to fix. Just do all the job in a single step. Odin knows how to manage all files in a single shot. You literally can full brick a phone if you create partition without any data FYI! I tested this with a phone I know I can recover using JTAG and in some models if you write .PIT alone even without reboot you loose recovery.img & Download Mode and then gave error on second attempt to write PDA so you can kill the unit because you can lost recovery and download access remaking partition alone without any data on PDA which have recovery & download modes disable writing .PIT alone.

Hi all,
Sorry to wake the dead for this, but I'm looking for a 32 gb pit file. The links that I found for them are dead (i.e Invisiblek's site)
Thanks!

Zin0 said:
Hi all,
Sorry to wake the dead for this, but I'm looking for a 32 gb pit file. The links that I found for them are dead (i.e Invisiblek's site)
Thanks!
Click to expand...
Click to collapse
Sorry but I think the S3 is so obsolete at this point, these files are all going to result in dead links. I never did get my 16GB back to health... such a shame.
Good luck!

CorporalMaxSterling said:
Sorry but I think the S3 is so obsolete at this point, these files are all going to result in dead links. I never did get my 16GB back to health... such a shame.
Good luck!
Click to expand...
Click to collapse
Great news, I was given a link to working 16 GB and 32 GB pit files! Here you go! I hope you get your s3 back to health!

Cannot do anything with Galaxy S3

I cannot root it, I cannot install any recovery besides the stock one that comes with it, I cannot get it to connect to the computer as mass storage, only as a media device.
Im thinking I just blew $215 on a paperweight.
I CANNOT EVEN INSTALL TITANIUM BACKUP TO GET RID OF THE FREAKING ATT CRAP!
What have I did wrong?
I have CWM v5.5.0.3!
Ive tried countless number of rooting programs including some poplular ones:
1. Casual - http://forum.xda-developers.com/showthread.php?t=2189536
2. Kingo Android ROOT - http://www.kingoapp.com/android-root.htm
3. Towelroot - https://towelroot.com/
4. CF Root (Flashed SU but does not work) - http://download.chainfire.eu/269/CF-Root/CF-Auto-Root/CF-Auto-Root-d2can-d2vl-sghi747m.zip
CF Root flashed Superuser but it says unfortunately Superuser has stopped.
Im about to take this back to the store I got it from....

Tell us your phone's specifics (firmware, modem, bootloader, is it AT&T or some other carrier). Does the phone work OK otherwise?
Do you have a ROM you want to try?

How are you flashing the recovery? Do you have Knox on your phone?

Model Number: Samsung-SGH-I747
OKAstro said:
Tell us your phone's specifics (firmware, modem, bootloader, is it AT&T or some other carrier). Does the phone work OK otherwise?
Do you have a ROM you want to try?
Click to expand...
Click to collapse
Its an [email protected] Phone with a new [email protected] sim card in it. The phone works on stock stuff. It will boot up just fine with CWM installed but I cannot actually go into CWM. It just gives me a black screen.
Android Version: 4.4.2
Baseband Version: I747UCUFNE4
Kernel Version
3.4.0-1514807
[email protected] #1
Mon May 19 21:00:05 KST 2014
Build number: KOT49H.I747UCUFNE4
SE for Android Status:
Enforcing
SEPF_SAMSUNG-SGH-I747_4.4.2_0016
Mon May 19 20:59:50 2014
It doesn't matter if I got a ROM or not. I cannot install a custom recovery.
audit13 said:
How are you flashing the recovery? Do you have Knox on your phone?
Click to expand...
Click to collapse
I am flashing Recovery thru Odin. Ive even tried different versions of Odin from 1.7 to 3.09. I prefer to use Odin 1.85.
And I have no clue what knox is or even if its installed.

Have you tried this thread?
http://forum.xda-developers.com/showthread.php?t=2789917

OKAstro said:
Have you tried this thread?
http://forum.xda-developers.com/showthread.php?t=2789917
Click to expand...
Click to collapse
Im not able to flash a working custom recovery.

mrnapolean1 said:
Im not able to flash a working custom recovery.
Click to expand...
Click to collapse
Well - maybe try flashing the stock 4.42 ROM again through Odin and then if that sticks, try the steps in the thread I linked
Good luck

OKAstro said:
Well - maybe try flashing the stock 4.42 ROM again through Odin and then if that sticks, try the steps in the thread I linked
Good luck
Click to expand...
Click to collapse
I had booted into download mode being about to flash CWM to my phone via Odin (Again) and I noticed this:
{
"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"
}
(If you cannot see it it says):
Factory Mode
Product Name: SGH-I727
Current Binary: Custom
System Status: Custom
Qualcomm Secureboot: Enable
Warranty Bit 1
Bootloader AP Swrev: 3
Is this bad?
Am I still able to root?
Am I able to install custom Recovery?
Am I able to install ROMS like CM 11?

mrnapolean1 said:
I had booted into download mode being about to flash CWM to my phone via Odin (Again) and I noticed this:
(If you cannot see it it says):
Factory Mode
Product Name: SGH-I727
Current Binary: Custom
System Status: Custom
Qualcomm Secureboot: Enable
Warranty Bit 1
Bootloader AP Swrev: 3
Is this bad?
Am I still able to root?
Am I able to install custom Recovery?
Am I able to install ROMS like CM 11?
Click to expand...
Click to collapse
The fact that you can get to download mode is good. But sorry, what this means is out of my league. Try PM'ing "DocHoliday77". He seems to be a great resource for all things SGS3. He's in numerous threads in the Development forum
EDIT: I booted into download and mine says the exact same thing

You have Knox on your phone. You tripped the knox counter and changed the warranty bit to 1 which means the warranty on your phone has been voided.
When flashing a custom recovery phone in Odin, do not check auto reboot. When you see the word reset appear in the status window, remove the usb cable, pull the battery, and use the button combo to boot inter recovery.

audit13 said:
You have Knox on your phone. You tripped the knox counter and changed the warranty bit to 1 which means the warranty on your phone has been voided.
When flashing a custom recovery phone in Odin, do not check auto reboot. When you see the word reset appear in the status window, remove the usb cable, pull the battery, and use the button combo to boot inter recovery.
Click to expand...
Click to collapse
No still nothing.
It vibrates when you first start it up and then the Samsung logo comes up with Recovery is starting in blue at the top for about a second and then goes to a black screen and nothing never happens afterwards.
What is Knox by the way? Is this keeping my phone from being rooted?

Figured id post here now rather than having two threads going for the same problem.
The more this goes on though, the more i am suspecting some sort of hardware problem.
I want to suggest using the PIT file to repartition the device, but theres no firmware to use along side it. Theres a program here on xda called PIT Magic i think. I dont know much about it, but maybe it could help you to somehow repartition....?
As for knox, there is tons of info out there on it already,so i wont get into it here. It wont block you from rooting, but it can deny root access when an app requests it.

Will the pit wipe it?
Will installing cm 11 using the installer work? Does it work?

Yes, repartitioning will wipe your data.
I dont use CM roms so im not familiar with the installer. Sorry.

DocHoliday77 said:
Yes, repartitioning will wipe your data.
I dont use CM roms so im not familiar with the installer. Sorry.
Click to expand...
Click to collapse
My main thing is I want to root my unrootable SGS3 so I can remove the ATT crap.

Im out of ideas for you...sorry. I kinda think its probably a hardware issue. It sounds like youve done everything you can to get root or recovery. Might be wise to start looking into a motherboard replacement...and keep your backups up to date!

DocHoliday77 said:
Im out of ideas for you...sorry. I kinda think its probably a hardware issue. It sounds like youve done everything you can to get root or recovery. Might be wise to start looking into a motherboard replacement...and keep your backups up to date!
Click to expand...
Click to collapse
I just spent $215 on this. I don't think the place where I bought it from will ever take it back.

I wish i had something better for you to try. Sorry.
If you are willing and able to consider it, i saw several motherboards and devices with broken screens (but otherwise functional) go for less than $65 today. Its the best option i can think of now.

Where at?

Sorry. It was on ebay. They often will go for a bit more than that, but if you are patient you should be able to get one relatively cheap.
Just do not buy any that say no power. Just look at ones that are a good motherboard, or a device with a broken screen where they say it powers on, just with no display. Also make sure the IMEI is clean.
Good luck!