Having trouble getting Heimdall to work on OSX - Verizon Samsung Galaxy S III

So I've been using an HTC MyTouch 4G for the past few years and had the rooting/flashing process down with that phone, but I recently switched to the Verizon variant of the Samasung Galasy S III and have run into an issue trying to root and flash an aftermarket rom to this device.
As per the CM Wiki for my device, I need to install and use Heimdall to downgrade the bootloader. I'm not new to using the terminal, so I figured this wouldn't be a difficult step, however I can't get Heimdall to work even after many attempts to download just the binary from the CM wiki, download the entire package including the frontend directly from the website Heimdall is hosted on, and even after compiling directly from source.
After trying to install it many different times/ways, I'm running into the same error every single time. After opening the terminal and trying to execute any command pertaining to Heimdall (Heimdall help, Heimdall detect, etc.) I get a response of "Illegal Instruction." I cannot get it to do ANYTHING other than to respond with "Illegal Instruction."
It's driving me mad because all I need Heimdall for at this point is to downgrade the bootloader.
I know I must be making some very minute error, but I can't figure it out.
Just a bit more information: I'm running OSX 10.6 so the current Heimdall Frontend is not compatable, so I have to use the Terminal (which I'd rather do anyways because I have more control that way.)
Any help or isight would be appreciated.
Thanks!

Just use the casual script instead of trying to downgrade
Sent from my SCH-I535 using Tapatalk 4 Beta
If I've helped, please hit the thanks button

tylerlawhon said:
Just use the casual script instead of trying to downgrade
Sent from my SCH-I535 using Tapatalk 4 Beta
If I've helped, please hit the thanks button
Click to expand...
Click to collapse
Casual script? Mind elaborating or guiding me in the right direction?

checkthisSH said:
Casual script? Mind elaborating or guiding me in the right direction?
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2332825
You shouldn't need to do anything with the bootloader, use this to load a custom recovery, then flash the cm10 image for the Verizon sgs3.
Sent from my SCH-I535 using Tapatalk 2

BadUsername said:
http://forum.xda-developers.com/showthread.php?t=2332825
You shouldn't need to do anything with the bootloader, use this to load a custom recovery, then flash the cm10 image for the Verizon sgs3.
Sent from my SCH-I535 using Tapatalk 2
Click to expand...
Click to collapse
Thanks for getting back to me so quickly.
According to the CM Wiki and a couple of other sources I can't think of at the moment, if I'm coming from stock/no root, I would need to load an older bootloader before flashing recovery and ultimately flashing CM10.
The Samsung root process is a bit different from some of the other phones I have worked with. Would you mind explaining to me why I wouldn't need to load an older bootloader?
Edit: After taking a look into the thread you provided for me I may have answered my own question. Loading the older bootloader is probably essential to getting the exploit to work with Heimdall, right? But not with the Casual exploit?

checkthisSH said:
Thanks for getting back to me so quickly.
According to the CM Wiki and a couple of other sources I can't think of at the moment, if I'm coming from stock/no root, I would need to load an older bootloader before flashing recovery and ultimately flashing CM10.
This process is a bit different from some of the other phones I have worked with. Would you mind explaining to me why I wouldn't need to load an older bootloader?
Click to expand...
Click to collapse
I've never seen those instructions before, but i would try posting this In the cm10 question and answer thread.
That could also be old instructions, find the cm10 development thread and see what the latest instructions are for installation.
I've never used heimdall and couldn't give you instructions how to use it, using odin to flash those would be significantly easier if you can get access to a window computer.
Either way, that process won't achieve root anyway. You're better off running casual first to get a custom recovery and root access, then run that process later if needed.
Sent from my SCH-I535 using Tapatalk 2

BadUsername said:
I've never seen those instructions before, but i would try posting this In the cm10 question and answer thread.
That could also be old instructions, find the cm10 development thread and see what the latest instructions are for installation.
I've never used heimdall and couldn't give you instructions how to use it, using odin to flash those would be significantly easier if you can get access to a window computer.
Either way, that process won't achieve root anyway. You're better off running casual first to get a custom recovery and root access, then run that process later if needed.
Sent from my SCH-I535 using Tapatalk 2
Click to expand...
Click to collapse
In theory, and please correct me if I'm wrong, but it looks like I should be able to use Casual up until I need to flash CM10. Which is as simple as throwing the .zip file onto my SD card and installing from recovery. That way I probably won't even have to touch Heimdall.
The only thing that concerns me is that following the CM wiki instructions has you flash an older kernel as well. Again, this appears to me like it could only be required to load the customer recovery using Heimdall, but I'm not entirely sure.
I'll have to look around for the CM10 dev thread around here because the one on the CM forum is a ghost town.
Thanks again for all of your help!

checkthisSH said:
In theory, and please correct me if I'm wrong, but it looks like I should be able to use Casual up until I need to flash CM10. Which is as simple as throwing the .zip file onto my SD card and installing from recovery. That way I probably won't even have to touch Heimdall.
The only thing that concerns me is that following the CM wiki instructions has you flash an older kernel as well. Again, this appears to me like it could only be required to load the customer recovery using Heimdall, but I'm not entirely sure.
I'll have to look around for the CM10 dev thread around here because the one on the CM forum is a ghost town.
Thanks again for all of your help!
Click to expand...
Click to collapse
That's exactly what I'm saying. However, the whole thing is confusing to me also. It seems weird that you'd need an older bootloader in order to run the rom.
Just make a backup before you flash in recovery, then if it won't run at least you have a way to get a working phone.
The kernel should have nothing to do with anything, as soon as you flash cm10 it'll get overwritten with the cm10 stock kernel.
Also make sure that the bootloader is unlocked before you flash, or you'd have to odin back to stock.
Sent from my SCH-I535 using Tapatalk 2

BadUsername said:
That's exactly what I'm saying. However, the whole thing is confusing to me also. It seems weird that you'd need an older bootloader in order to run the rom.
Just make a backup before you flash in recovery, then if it won't run at least you have a way to get a working phone.
The kernel should have nothing to do with anything, as soon as you flash cm10 it'll get overwritten with the cm10 stock kernel.
Sent from my SCH-I535 using Tapatalk 2
Click to expand...
Click to collapse
I'm assuming it has something to do with using Heimdall, and if that's the case, I don't know why anyone would ever want to use that method when it is clearly more difficult. Maybe someone else can weigh in on the topic.
Thanks again for the solid advice. I'll take the Casual route and see where it takes me.

BadUsername said:
That's exactly what I'm saying. However, the whole thing is confusing to me also. It seems weird that you'd need an older bootloader in order to run the rom.
Sent from my SCH-I535 using Tapatalk 2
Click to expand...
Click to collapse
FYI, every rooted and unlocked Verizon GSIII is using a pre-release unlocked bootloader so you're using an older bootloader already.
Sent from my SCH-I535 using Tapatalk 4 Beta

SlimSnoopOS said:
FYI, every rooted and unlocked Verizon GSIII is using a pre-release unlocked bootloader so you're using an older bootloader already.
Sent from my SCH-I535 using Tapatalk 4 Beta
Click to expand...
Click to collapse
You mean once you unlock the phone with an old aboot file right? The newer phones would have a newer bootloader until you change it.
The instructions are really confusing because they're instructing to downgrade the bootloader to inject an aboot file and custom recovery. I still think that entire step is unnecessary.
Sent from my SCH-I535 using Tapatalk 2

Related

CWM to root? Or root to CWM?

OK before anyone blasts me yes I have researched for two days now and feel like I have been run in circles. I have searched XDA and Google to no avail and no I'm not a noob. I myself have a galaxy s2 skyrocket but recently got my wife the infuse and I'm starting to think that was a mistake. OK this is what I've found...
I type in Google how to install CWM recovery on the infuse and every thing I find says it must be rooted first.
Running Android 2.3.6 update thru Samsung kies....
So I type in how to root the infuse and what I find is if you want to root without flashing a new kernal you must have CWM to install a zip file from the SD.
Seems like one big circle. To root my skyrocket was easy as flashing a recovery image in Odin of CWM recovery and opening a super user zip file to root. 5 minutes easy as 1.2.3.
So my questions are..
1. Can I flash a recovery image tar of CWM to the infuse using Odin?
2. If so where can I download the tar file. I already have Odin 1.85 installed on my PC so I don't need that unless the tar comes in a one click.
3. If I can't how can I root and install CWM without flashing a custom kernel?
Please don't give links to nothing heimdel. The last time I used heimdel was with my captivate and I spent 3 days unbricking it.
4. Will the Motorola exploit added in super one click work with Samsung or harm the phone in anyway?
Thanks ahead of time for the help...
Sent from my SAMSUNG-SGH-I727 using xda premium
garydv2002 said:
OK before anyone blasts me yes I have researched for two days now and feel like I have been run in circles. I have searched XDA and Google to no avail and no I'm not a noob. I myself have a galaxy s2 skyrocket but recently got my wife the infuse and I'm starting to think that was a mistake. OK this is what I've found...
I type in Google how to install CWM recovery on the infuse and every thing I find says it must be rooted first.
Running Android 2.3.6 update thru Samsung kies....
So I type in how to root the infuse and what I find is if you want to root without flashing a new kernal you must have CWM to install a zip file from the SD.
Seems like one big circle. To root my skyrocket was easy as flashing a recovery image in Odin of CWM recovery and opening a super user zip file to root. 5 minutes easy as 1.2.3.
So my questions are..
1. Can I flash a recovery image tar of CWM to the infuse using Odin?
2. If so where can I download the tar file. I already have Odin 1.85 installed on my PC so I don't need that unless the tar comes in a one click.
3. If I can't how can I root and install CWM without flashing a custom kernel?
Please don't give links to nothing heimdel. The last time I used heimdel was with my captivate and I spent 3 days unbricking it.
4. Will the Motorola exploit added in super one click work with Samsung or harm the phone in anyway?
Thanks ahead of time for the help...
Sent from my SAMSUNG-SGH-I727 using xda premium
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=1613523
But is flashing a new kernel the only option for rooting? If it were my phone I would flash away cause I'm a flashaholic but she don't want to lose all her info and have to restore it all. The only reason she wants root is to freeze those very annoying att bloatware apps that aggravate everyone by running all the time and slowing everything down...
Sent from my SAMSUNG-SGH-I727 using xda premium
garydv2002 said:
But is flashing a new kernel the only option for rooting? If it were my phone I would flash away cause I'm a flashaholic but she don't want to lose all her info and have to restore it all. The only reason she wants root is to freeze those very annoying att bloatware apps that aggravate everyone by running all the time and slowing everything down...
Sent from my SAMSUNG-SGH-I727 using xda premium
Click to expand...
Click to collapse
Check with jscott. He may know for certain.
Flashing kernel does not alter data.
I made several root via heimdall versions.
Instead of heimdall, basically, if you can Odin an insecure kernel, boot into cwm recovery, you can flash my cwm root package.
It also remove all bloats. Check my uclb3 root thread especially post #2
And as far as I know, on the infuse uclb3, you can't root without an insecure kernel flash in download mode.
Well it may cost a phone of I may soft brick it a few times but I'm gonna put my programming skills to the test and see if I cant come up with a one click root to 1. Make life easier for everyone and 2. To make it simple for the noobs to figure out. I'll let you know if my java VB and other languages I know can come up with something. It may take me a while and a lot of lost sleep hair pulling cursing and crying but I'm gonna give it my best effort.. wish me luck cause I'm gonna need it...
Sent from my SAMSUNG-SGH-I727 using xda premium
For now, the normal exploits used for a one click root option don't work on the stock UCLB3 Gingerbread kernel. As qkster has mentioned, you need an insecure kernel to root UCLB3. Also, there isn't an easy way yet to change the stock recovery to CWM without using a custom kernel zImage that includes it. Check out this HOW-TO that I wrote up for an explanation of what it takes to root UCLB3 Gingerbread. This explains how to temporarily use a custom kernel to achieve root, and also explains how to go back to the stock kernel. None of this removes existing data on the phone.:
http://forum.xda-developers.com/showthread.php?t=1603220
If you don't want to do all of the work required to root UCLB3 on your phone, then you can use qkster's Heimdall one-click packages or my Odin packages that he showed you earlier.
you can root the infuse with super one click... easiest way to just root it, and also might i add, the infuse is very difficult to hard brick, soft bricks are easy to fix, with odin or hiemdall but i haven't yet heard or seen a case where the infuse is actually hard bricked, now installing cwm is easy as well, just youtube it, very simple and that there should get you on your way to flashing
deathblade said:
you can root the infuse with super one click... easiest way to just root it
Click to expand...
Click to collapse
Assuming that you are talking about going back to stock Froyo to root with SuperOneClick? As of yet, you can't reliably use SuperOneClick on the latest Gingerbread release. Sounds like the OP wants to directly root UCLB3 Gingerbread.
garydv2002 said:
Well it may cost a phone of I may soft brick it a few times but I'm gonna put my programming skills to the test and see if I cant come up with a one click root to 1. Make life easier for everyone and 2. To make it simple for the noobs to figure out. I'll let you know if my java VB and other languages I know can come up with something. It may take me a while and a lot of lost sleep hair pulling cursing and crying but I'm gonna give it my best effort.. wish me luck cause I'm gonna need it...
Sent from my SAMSUNG-SGH-I727 using xda premium
Click to expand...
Click to collapse
Now, you're talking.
Good luck.
You will need to look at some kernel work.
You may also need to look at the pit files in the unbrick package.
If you can, also look at boot sequences of the galaxy device. Adam Outler did some neat stuff with the galaxy devices.

[Q] Where to Access Hasoon2000 S-Off Tool?

I've spent hours searching for how to S-Off my device. I've been running CM 9 and then 10, but it seems like my problem with 10.1 is S-on.
Most searches come to someone recommending Hasoon2000s S-Off tool, and linking to the original thread at: http://forum.xda-developers.com/showthread.php?t=1696373&highlight=s+off
The problem is that the link in that original thread to download the S-Off Tool is no longer there. I've looked through Hasoon2000s other downloads, and while there is the all-in-one toolkit 2.0, there doesn't seem to be a way to do S-Off in that kit.
I'll probably settle for JuopunutBear's solution, but since everywhere I go people are swearing by Hasoon2000s, (and I used the all-in-one toolkit with great success), does anyone have any new direction to track down a downloadable version of the S-Off tool, or a way to access it, or is JuopunutBear's all that is left for some reason? I haven't found any posts saying why Hasoon2000's has been pulled?
Thanks!
If I were you I would stay away from toolkits altogether. Not because they are bad, only because you learn absolutely nothing from using them and usually come bomb the threads when **** hits the fan.
The wire trick is a fun little task to handle though so everything should be okay that way.
Sent from my Nexus 4 using Tapatalk 2
Toolkit
ArachnydZ28 said:
I've spent hours searching for how to S-Off my device. I've been running CM 9 and then 10, but it seems like my problem with 10.1 is S-on.
Most searches come to someone recommending Hasoon2000s S-Off tool, and linking to the original thread at: http://forum.xda-developers.com/showthread.php?t=1696373&highlight=s+off
The problem is that the link in that original thread to download the S-Off Tool is no longer there. I've looked through Hasoon2000s other downloads, and while there is the all-in-one toolkit 2.0, there doesn't seem to be a way to do S-Off in that kit.
I'll probably settle for JuopunutBear's solution, but since everywhere I go people are swearing by Hasoon2000s, (and I used the all-in-one toolkit with great success), does anyone have any new direction to track down a downloadable version of the S-Off tool, or a way to access it, or is JuopunutBear's all that is left for some reason? I haven't found any posts saying why Hasoon2000's has been pulled?
Thanks!
Click to expand...
Click to collapse
His toolkit is still there, just browse around a bit... or go here... http://d-h.st/users/hasoon2000/?fld_id=2818#files
acwest said:
His toolkit is still there, just browse around a bit... or go here...
Click to expand...
Click to collapse
Thanks for your help I appreciate it- That was the same place linked to above.
Thats his toolkit 2.0 which I used to unlock my phone, but it doesn't give the phone S-Off (or atleast I couldnt find a way to do it in the toolkit)
His S-Off toolkit can't be found anymore on the otherhand, and I've searched in depth. I've been trying for at least 6-8 hours to get S-Off. Now I have a semi-bricked phone. Every path I go down is a dead end and its driving me nuts!
I was going to try the wire trick, but it requires stock rom. I had backed up the stock rom but it won't load. I downloaded 2 PD15IMG.zip files but neither of them will load, recovery says "Bad" when I try to run the .zip files. Did a little research. I think I need to do it via fastboot for the PD15IMG.zip files. Trying to figure that out now. Warnings seem pretty dire about trying to do it on a non-stock rom
This is getting above my head but I'm working my best to figure it out. Worst comes to worse I'll just have to order a new phone! I hate to be the novice that ends up being a PITA, as I've dealt with them plenty on the car forums I'm active on. I'd like to apologize up front for being "that guy".
Whats your situation now, do you have a recovery? What does it all say on your bootloader screen? Write that all down here
Sent from my Nexus 7 using xda premium
demkantor said:
Whats your situation now, do you have a recovery? What does it all say on your bootloader screen? Write that all down here
Sent from my Nexus 7 using xda premium
Click to expand...
Click to collapse
unlocked
Doubleshot PVT Ship S-On RL
Hboot- 1.45.0013
Microp-0353
eMMC-Boot
Nov 21 2011, 20:20:47
I do have recovery and hboot. Stock backup won't load though even though the file is there in recovery.
Thanks!
And what if you were to try and flash another rom, like miktouch, through recovery?
Sent from my MyTouch 4G Slide using xda premium
demkantor said:
And what if you were to try and flash another rom, like miktouch, through recovery?
Sent from my MyTouch 4G Slide using xda premium
Click to expand...
Click to collapse
I was able to reflash a version of CM10 I was using for a while and that works, but I can't find a stock one that will work. I've tried multiple, and they all give me "bad" error and don't finish the install.
I was going to try a different version of CM10, 10.1, or go to a stable release of 9. If none of those worked, I'd be happier with stock. None of the ones I've tried will work, but I'm assuming thats because I'm S-On, but since I can't find hasoon2000s S-Off tool everyone was raving about, and the wire trick requires stock ROM based on what the directions say, I find myself in a pickle.
The CM10 version I have can't do some basic things I need for work- like sync with my bluetooth in the car or not randomly freeze up during the day without me knowing it sending all my calls to voicemail. I tried versions of the others that other people are using (like silverL's 10.1 and the CM-listed stable CM9) and neither would load.
Do I have a different issue? AKA are other people with S-On able to load those Roms? I can try miktouch too.
---
Also trying to load via fastboot and I'm getting this error:
"Whoops: didn't find expected signature
read_central_directory_entry_failed
error: failed to access zipdata in [Whole bunch of non-english characters taking up a few lines]"
----
Update: Just to clarify, when I try to install a stock rom it gives me "Can't open [filename] (bad)
However, when I try to install the CM's, it installs fine and says "Install from sdcard complete" they just won't load when I restart my phone, except for the original version of CM10. (for example, in all the 10.1s I've tried I get "Unfortunately, the process com.android.phone has stopped" but the intro page will load. I figured that came down to an S-On issue when I tried to troubleshoot.
Any rom that is based off stock (like miktouch) should work to do the wire trick. I would check md5sums of the roms that won't flash to make sure they aren't corrupt at all. Also some say the latest twrp (and maybe other recoveries) won't flash some roms, so may need to change that as well
Sent from my MyTouch 4G Slide using xda premium
demkantor said:
Any rom that is based off stock (like miktouch) should work to do the wire trick. I would check md5sums of the roms that won't flash to make sure they aren't corrupt at all. Also some say the latest twrp (and maybe other recoveries) won't flash some roms, so may need to change that as well
Sent from my MyTouch 4G Slide using xda premium
Click to expand...
Click to collapse
Great, thanks!
I'll give miktouch a shot to see if I can use it for the wire trick. I'll let you know if it works.
ArachnydZ28 said:
Great, thanks!
I'll give miktouch a shot to see if I can use it for the wire trick. I'll let you know if it works.
Click to expand...
Click to collapse
negative.
miktouch would go through the install process, and end at the Tmobile mytouch 4g slide screen forever. I know on one install it took a long time to "load" the first time so I left it on this screen for about 15 minutes to no avail. Let me know if there is any chance of it taking longer than that. Reinstalls were the same story.
I got CM9.1 to install by installing it twice on top of itself (not sure why that fixes it) but it was a tiny bit buggy.
Is there any chance this could be bootloader related or recovery related? I can try to reload those too. grrr...
Its possible but if your bootloader can boot up one ROM it should be able to boot another. For this phone the only reason I have seen to change bootloaders is to unlock all the fastboot options. Flashing a new bootloader would reformat your partitions which may be the cause of your issue. Make sure you do a full wipe from recovery or fastboot -w or use a superwipe script, hell I tend to do all three between flashes but I'm kinda ocd when it comes to this, I hate debugging issues caused by residual effect from old data left after a dirty flash
But it may be worth it to flash a new recovery, not sure what you are using now but sometimes one will work when another doesn't, this would probably be my next step
Sent from my Nexus 7 using xda premium
demkantor said:
Its possible but if your bootloader can boot up one ROM it should be able to boot another. For this phone the only reason I have seen to change bootloaders is to unlock all the fastboot options. Flashing a new bootloader would reformat your partitions which may be the cause of your issue. Make sure you do a full wipe from recovery or fastboot -w or use a superwipe script, hell I tend to do all three between flashes but I'm kinda ocd when it comes to this, I hate debugging issues caused by residual effect from old data left after a dirty flash
But it may be worth it to flash a new recovery, not sure what you are using now but sometimes one will work when another doesn't, this would probably be my next step
Sent from my Nexus 7 using xda premium
Click to expand...
Click to collapse
I'm running CWM 5.5.0.4
I'll try to reload it or another version (I'm seeing some issues people have with 5504)
Thanks!
ArachnydZ28 said:
I'm running CWM 5.5.0.4
I'll try to reload it or another version (I'm seeing some issues people have with 5504)
Thanks!
Click to expand...
Click to collapse
You should try CWM 5.0.2.7. Also, since you are S-On you should extract the boot.img from Miktouch and flash it from fastboot, separately from the ROM. Since you have been on an ICS/Jellybean rom, I have to believe your original boot.img was replaced at some point. This is the only way to get back the Gingerbread boot.img. I am not savvy enough to know if this file is the bootloader or the kernel, but this process should get you back to stock-enough to do the wire trick.
Sent from my SGH-T699 using xda app-developers app
It's the kernel.....the boot.img file, I mean. The bootloader is that mostly white screen you see with "Hboot" at the top that will have "S-On" or "S-Off" after the word Radio. Good response.:good:
ArachnydZ28 said:
Thanks for your help I appreciate it- That was the same place linked to above.
Thats his toolkit 2.0 which I used to unlock my phone, but it doesn't give the phone S-Off (or atleast I couldnt find a way to do it in the toolkit)
His S-Off toolkit can't be found anymore on the otherhand, and I've searched in depth. I've been trying for at least 6-8 hours to get S-Off. Now I have a semi-bricked phone. Every path I go down is a dead end and its driving me nuts!
I was going to try the wire trick, but it requires stock rom. I had backed up the stock rom but it won't load. I downloaded 2 PD15IMG.zip files but neither of them will load, recovery says "Bad" when I try to run the .zip files. Did a little research. I think I need to do it via fastboot for the PD15IMG.zip files. Trying to figure that out now. Warnings seem pretty dire about trying to do it on a non-stock rom
This is getting above my head but I'm working my best to figure it out. Worst comes to worse I'll just have to order a new phone! I hate to be the novice that ends up being a PITA, as I've dealt with them plenty on the car forums I'm active on. I'd like to apologize up front for being "that guy".
Click to expand...
Click to collapse
Load the pd15img.zip on your sd card and boot to your bootloader. It should detect the file on your card and ask if you want to flash it. Just follow the directiins it gives you
Edit: actually should be pd59img not 15
Sent from my SGH-T889 using Tapatalk 2

[Q] What is a BootChain

I've spent an hour searching for something to explain what bootchains are. I want to understand how they allow the S3 to be rooted and why you need to put them back when you're done. But I'd settle just for a simple what are they.
TommyTFC said:
I've spent an hour searching for something to explain what bootchains are. I want to understand how they allow the S3 to be rooted and why you need to put them back when you're done. But I'd settle just for a simple what are they.
Click to expand...
Click to collapse
A bootchain is the process your phone takes in order to boot. Flashing a specific bootchain is the bootchain available at the time when it was released.
It specifically tells the phone to boot through a series of steps in order to make sure the phone is running correct files. If any part of the chain is broken, the phone won't be able to boot up.
An example which we bypass on our specific phone is the aboot step in the bootchain. To unlock the phone, we simply flash a modified aboot file that makes the phone think it's running the correct rom and kernel. Aboot is only one part of the bootchain.
Hope that makes sense.
Sent from my SCH-I535 using Tapatalk 2
So the files in the tar are programs and they each execute in turn?
The rooting instructions say it doesn't matter if you put the original back. Know why?
Sent from my SCH-I535 using xda app-developers app
TommyTFC said:
So the files in the tar are programs and they each execute in turn?
The rooting instructions say it doesn't matter if you put the original back. Know why?
Sent from my SCH-I535 using xda app-developers app
Click to expand...
Click to collapse
Basically you got it. That's exactly what's in the tar file.
I'm not really sure how exactly the new rooting process works the way it does, but I know it has something to do with breaking the chain and allowing it to inject a superuser app and recovery. The original bootchain blocks this process and doesn't allow superuser permission. ICS allowed this, which is why it was easier to root it. JB blocks this method, which is why a modified bootchain is needed.
I'm only assuming, but restoring to the original bootchain is simply recommended because it's what should be on the phone. If there's something wrong with the modified bootchain then it may break your booting checkpoints. You're probably safe not restoring it, but you can be sure you're safe if you do restore it.
Sent from my SCH-I535 using Tapatalk 2
Yea you should restore the original bootchains. You want to be original.
Did a search, and this was the best thread I could find.
I'm looking to root, and know that I need to download the correct bootchain.
Question: How do I determine which one that is?
I'm running the (new, awful) version of 4.1.2 that just updated my Verizon Galaxy S3. Currently, I'm stock... but not for long.
Thanks for the assistance.
ccstra54 said:
Did a search, and this was the best thread I could find.
I'm looking to root, and know that I need to download the correct bootchain.
Question: How do I determine which one that is?
I'm running the (new, awful) version of 4.1.2 that just updated my Verizon Galaxy S3. Currently, I'm stock... but not for long.
Thanks for the assistance.
Click to expand...
Click to collapse
You can get everything you need from the S3 link in my signature. Instructions are there also.
If anyone is more curious about this, you should google "2nd-init" or "milestone bootchain" theres a couple good blogs/posts discussing how they got past the locked boot loader on the Motorola Droid/ milestone.

[Q] Want to root, have some questions first.

Hello everyone, so I have a couple questions for you guys in regards to rooting my S3. Back in November when I got the phone, I had rooted it and unlocked it using Odin and the EZ-Unlock app off of the play store. Not long after that, i returned back to stock, and here we are 6/7 months later and I am wanting to re-root, but I have discovered that the way to go about this has since changed.
I have looked at this guide http://forum.xda-developers.com/showthread.php?t=2046439 and looked at these videos http://forum.xda-developers.com/showthread.php?t=2295146 but am still a little iffy about jumping right into this since the methods involved are different than the last time I did it. One thing I noticed on the guide that I linked is that they do not have the bootchain for the version on my phone (VRBMF1).
Basically so this thread does not turn into a short story, I am just going to ask if the steps I lay out is the correct way to go about this. I am strictly wanting to root and unlock so that I can flash to a custom ROM, mainly CM10.
1. install samsung drivers
2. download Odin
3. download the "both root and unlocked bootloader"
4. download VRALEC bootchain
5. download either CWM or TWRP
6. and for this step, should I just flash to either VRBMB1 or VRBMD3, or should I just skip this step since it is optional and go straight to flashing a custom ROM?
In addition to this, I have heard things mentioned about backing up the IMEI, and I see them saying you can do it in a Terminal Emulator (the su and reboot nvbackup commands) . Is this something that has to be done after root and unlock?
I would love to get back to rooted and running custom ROMS again, so any help you can provide would be greatly appreciated.
Bump.
Flash the VRBMD3 bootchain and backup your IMEI after rooting and unlocking the bootloader but before flashing a custom ROM.
Thanks for your reply. Is there any benefit to flashing the md3 bootchain if I am just going to be flashing to a custom ROM?
Sent from my SCH-I535 using Tapatalk 2
The boot chain makes a great stable platform before you go off on a custom. That way you can boot and make sure the root has taken
Sent from my SCH-I535
Lord_Tardis said:
The boot chain makes a great stable platform before you go off on a custom. That way you can boot and make sure the root has taken
Sent from my SCH-I535
Click to expand...
Click to collapse
Thanks for your reply. I am happy to report that I listened and flashed the VRBMD3 bootchain and am successfully unlocked and rooted and am running a custom ROM. I did not know that the bootchain would have an effect after I had flashed a custom ROM, so I am glad that I did that. Thanks for your replies everyone. One question though. Since my baseband version is VRBMF1, is there any downside to flashing the VRBMD3 bootchain or does it really matter?
Atwooooood said:
Thanks for your reply. I am happy to report that I listened and flashed the VRBMD3 bootchain and am successfully unlocked and rooted and am running a custom ROM. I did not know that the bootchain would have an effect after I had flashed a custom ROM, so I am glad that I did that. Thanks for your replies everyone. One question though. Since my baseband version is VRBMF1, is there any downside to flashing the VRBMD3 bootchain or does it really matter?
Click to expand...
Click to collapse
The mf1 is the most current radio data. I do not believe there is harm in flashing to an older one. The best bet is to find the one that gives you the best signal strength.
Sent from my SCH-I535
If I wanted to test a couple bootchains as far as signal strength goes , am I able to flash to a different one after I've already flashed a custom ROM or are there more steps involved?
Sent from my SCH-I535 using Tapatalk 2
Correct me if I'm wrong. But bootchains do not affect signal. Only modems/basebands. You can go download any which one as long as kids meant for your model/carrier.
Sent from my SCH-I535 using Tapatalk 4
Sandman-007 said:
Correct me if I'm wrong. But bootchains do not affect signal. Only modems/basebands. You can go download any which one as long as kids meant for your model/carrier.
Sent from my SCH-I535 using Tapatalk 4
Click to expand...
Click to collapse
You, sir, are correct.
Sent from my SCH-I535 using xda app-developers app
Thanks for clarifying guys. Appreciate your alls help.
Sent from my SCH-I535 using Tapatalk 2

[Q] Official CM Installation Method Confusion

Greetings,
My name is Tim and I'm looking for some assistance with getting CM 10.1.3 up and running on my GS3 (d2vzw / SCH-i535). I'm not a complete noob, as I managed to successfully flash CM to my Galaxy Tab 2 10.1, and my Droid X2 after countless hours of reading through XDA forum posts for each of the devices, however...I'm still pretty new to a lot of this stuff as I usually don't mess with it once I get CM up and running, and struggle with command prompts still, so I apologize for any/all idiocy posted herein.
I am using the instructions found on the CM site under the d2vzw device (I'd link you but it doesn't appear as though I'm allowed to), and after reading that I don't need to root my device to install CM, I'd prefer to stick with this method (I'm also uncomfortable using Odin or any other such software, as I've heard bad things and already managed to soft brick my GS3 once with it.)
I've got all the appropriate files listed at the above page, but I'm confused with several aspects of the "official" install instructions, and would like some clarification, if possible. Any assistance would be greatly appreciated.
1) USB drivers: I installed the Samsung drivers, but when I ran heimdall print-pit in CMD, it failed giving me an error 12 (can't remember what, specifically, but apparently it has to do with USB drivers). A bit of Google-ing, and I was able to determine that Samsung drivers = bad. Okay, I can deal with that and have uninstalled them. However, does that mean I need to NOT let Windows 7 Update auto install drivers? Further, do I need to use the zadig app to install drivers before I can use Heimdall appropriately? I ask because after I uninstalled the Samsung drivers and rebooted, I tried to flash but it failed.
2) Wording of CMD commands confuses me. Heimdall flash --ABOOT aboot.mbn - okay, I get that I'm typing "heimdall flash" as the preface, but the actual aboot.mbn file is within a .tar file...so do I just flash to the location of the actual tar file? Or do I extract it with 7zip (as I initially tried) and try to flash to the location of the actual aboot.mbn file? Further, --ABOOT doesn't show up on the list of viable options within CMD, which confuses me (is it part of the command, or is it a place holder for some command I'm not understanding).
3) Same question for the other CMD commands.
I've looked around on XDA, the Heimdall site, and elsewhere for more detailed "official" install guides, but they all seem to either involve Odin or rooting, and as I mentioned I want nothing to do with either of them, if possible.
Thank you kindly for your time.
Sure you can do all that, but there are some easy one click root apps for the gs3. Then install cwm recovery. Then flash CM and GAPPs.
Just search the forum and you should be able to find the thread.
Good luck!!
Sent from my SCH-I535 using xda app-developers app
stolo said:
Sure you can do all that, but there are some easy one click root apps for the gs3. Then install cwm recovery. Then flash CM and GAPPs.
Just search the forum and you should be able to find the thread.
Good luck!!
Sent from my SCH-I535 using xda app-developers app
Click to expand...
Click to collapse
The only "one-click app" I know of is Framaroot which does not work on the VZW varient of the GS3. So what app are u referring to?
Sent from my SCH-I535 using Tapatalk
I was not referring to an apk on the phone, meant pc app.
I have not personally used this, but looks like it will do the trick.
http://forum.xda-developers.com/showthread.php?t=2332825
stolo said:
I was not referring to an apk on the phone, meant pc app.
I have not personally used this, but looks like it will do the trick.
http://forum.xda-developers.com/showthread.php?t=2332825
Click to expand...
Click to collapse
I thought I downloaded that before and it ended up being a jumble of files...but I just downloaded it now and it looks promising. Thanks for the suggestion, I'll give it a try tomorrow!
Swatpro004 said:
I thought I downloaded that before and it ended up being a jumble of files...but I just downloaded it now and it looks promising. Thanks for the suggestion, I'll give it a try tomorrow!
Click to expand...
Click to collapse
If you want just go try out the cyanogenmod installer from the play store. It should root, unlock, and install for you. Just follow the instructions in the app.
Sent from my AOSP on Grouper using Tapatalk HD
Well, I just tried using the "casual" root one-click thing.
I successfully rooted, but it took ~10 minutes on the flashing of aboot. It claimed to be done, but when I tried to flash CWM it rebooted into the "unauthorized software, contact verizon" screen.
Any ideas? This makes me sad. I don't know why this is so much more difficult than my other devices.
-e- I can still get into download mode, but when I try to go into recovery it just loops back to the main samsung screen with the custom icon and then hops into the verizon unauthorized stuff. Also, when I plug it in to charge it just vibrates once every ~5 seconds without doing much else.
Additionally, I still don't know which USB drivers I want for doing all of this. I'm relying on the ones Windows 7 auto-installs currently, if that helps with troubleshooting. Thank you in advance, again.
Swatpro004 said:
Well, I just tried using the "casual" root one-click thing.
I successfully rooted, but it took ~10 minutes on the flashing of aboot. It claimed to be done, but when I tried to flash CWM it rebooted into the "unauthorized software, contact verizon" screen.
Any ideas? This makes me sad. I don't know why this is so much more difficult than my other devices.
-e- I can still get into download mode, but when I try to go into recovery it just loops back to the main samsung screen with the custom icon and then hops into the verizon unauthorized stuff. Also, when I plug it in to charge it just vibrates once every ~5 seconds without doing much else.
Additionally, I still don't know which USB drivers I want for doing all of this. I'm relying on the ones Windows 7 auto-installs currently, if that helps with troubleshooting. Thank you in advance, again.
Click to expand...
Click to collapse
you just didn't unlock your bootloader that's all. Flash stock (or stock recovery) using Odin. Then root using the same method above. When rooted unlock your bootloader using EZunlock1.2. Its an app that runs on your phone. Then flash recovery. Done.
Edit: at this point it may be easier to just flash a prerooted stock ROM using Odin.
Sent from my SCH-I535 using Tapatalk
Sandman-007 said:
you just didn't unlock your bootloader that's all. Flash stock (or stock recovery) using Odin. Then root using the same method above. When rooted unlock your bootloader using EZunlock1.2. Its an app that runs on your phone. Then flash recovery. Done.
Edit: at this point it may be easier to just flash a prerooted stock ROM using Odin.
Sent from my SCH-I535 using Tapatalk
Click to expand...
Click to collapse
Thank you, Sandman. I will try this right now.

Categories

Resources