[Q] Official CM Installation Method Confusion - Verizon Samsung Galaxy S III

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.

Related

[Q] Screen not working

Hello,
Later, I tried to root my phone with a crappy script.
I didn't worked and I was stuck at the Google screen.
So I tried to flash the boot.img which comes with CyanogenMod but the result was the same.
Then, I tried ti install a Nexus S stock ROM that I found on this forum and now my screen don't work anymore.
I just have some LEDs on at the bottom on the phone.
I still have access to fastboot wia the terminal.
Thank you.
What model phone do you have, and what stock image did you flash?
Sent from my Nexus S using Tapatalk
I have an European Nexus S (SFR Vodafone).
The ROM I tried to flash is named Stock-GRH78-Unsigned and I downloaded it from this forum.
I'll post the link if I manage to find it.
The ROM comes from this thread: http://forum.xda-developers.com/showthread.php?t=1062777
You flashed the samoled version on yours, which is slcd. Different screens, different and incompatible software. I saw your comment in the other thread. What you'll have to do is figure out how to flash the proper i9023 model software. Hopefully someone more familiar with the process can lend a hand.
Sent from my Nexus S using Tapatalk
Yes, would be nice to have something to flash from fastboot.
Flash the rom in my signature via cwm recovery.
Sent from my Nexus S using XDA App
I'd love it was so simple.
Even in recovery, the scree, stay black so I don't know if I'm really in recovery mod.
Do you think I can use this tool ? http://forum.xda-developers.com/showthread.php?t=974621
If not, I'd like to have some screenshots of the ClockWorkMod Recovery 4.0.0.2 so I can use it even if I don't see anything on the screen.
I just discovered I have ADB access so ClockWorkMod seems to be working.
Can I flash your ROM using ADB?
When I try to flash your rom (rentaric) using fastbot, I get the following errors:
archive does not contain 'android-info.txt'
archive does not contain 'android-product.txt'
error: update package has no android-info.txt or android-product.txt
Thanks.
Nope. Flashing via Odin is easiest if display isn't working imho.
Sent from my Nexus S using XDA App
Have you a link to download Odin please?
Thanks.
Make sure you know what you're doing before you start this time. ODIN is a powerful tool..you can find it in the development forum.
Sent from my Nexus S using Tapatalk
I've downloaded ODIN and CyanogenMod but I've never used ODIN before so I don't know how to flash CyanogenMod with it.
OyoKooN said:
Have you a link to download Odin please?
Thanks.
Click to expand...
Click to collapse
www.samfirmware.com
As uansari1 said, Odin is kind of a "last resort" tool for me. It's poweful and gets the job done even w/o a working screen.
Basically what you do is:
download Odin and the files needed for YOUR device
hold vol up and vol down, then plug in the usb cable while still holding both buttons (this starts download mode)
start Odin
there should be a yellow field top left with a port number in it
make sure everything except Auto reboot and F. reset time is UNchecked
extract the zip files you got from samfirmware
apply bootloader to bootloader
apply pda to pda
apply modem to phone
leave csc empty
hit start
wait (2-3mins), phone will reboot during that period, when the yellow field changes color and says "pass" it is done.
Are the files needed in the Drivers column on samfirmware?
If not where do I download them?
Thanks.
OyoKooN said:
Are the files needed in the Drivers column on samfirmware?
If not where do I download them?
Thanks.
Click to expand...
Click to collapse
They have given you enough information. Do some reading. Research what you are about to do so you don't come across problems like what you are dealing with now.
Good luck.
Sent from my PC36100 using XDA Premium App
I found them.
I do not need to use the PIT file?
Nope, just apply Bootloader, PDA and Phone. Remember to double check which settings are checked/unchecked.
Thank you so much rentaric, it did the trick!
OyoKooN said:
Thank you so much rentaric, it did the trick!
Click to expand...
Click to collapse
Nice, good luck in further expeditions

Bricked....Ugh

Ok so I've been rooted and unlocked for a while now, but stayed with the stock rom as when I tried out Synergy Nightlies it gave me some errors. So I went to try out CleanRom 2.1, people liked it and I didn't notice any flashing errors. So I flashed it through CWM 6.0.1 and it gave me the yellow exclamation mark saying I had unauthorized data on my phone. So I followed the sticky on how to unbrick my phone using the 2 boot loaders and the root66 stock image. My issue is that when running the root66 stock image through Odin it fails at _XmitData_Read, which seems to be somewhere in system.img.ext4. I've tried rebooting the computer, the phone, Odin, it just doesn't work. So when I reboot my phone after the failure I get Odin auto loading saying:
Odin Mode
Product Name: SCH-I535
Custom Binary Download: No
Current Binary: Samsung Official
System Status: Official
Qualcomm Secureboot: Enable
Then an image of a phone, 2 dots, a yellow exclamation, 2 dots and a computer are shown with the message "Firmware upgrade encountered an issue. Please select recovery mode in Kies and try again.
Anyone able to help me?
can you still get to odin mode? also if you have kies installed on the computer erase it.
kidhudi said:
can you still get to odin mode? also if you have kies installed on the computer erase it.
Click to expand...
Click to collapse
Kies isn't installed on the computer and yes I am still able to get into Odin Mode.
I'm under the impression that "unauthorized software" message comes from the locked bootloader (if I'm wrong about that someone plese correct me.)
Sounds like you're functional enough to be able to Odin back to stock and go from there - that's what I'd try. See the stickied thread in the Q&A forum.
I would run the FULL VRALF stock image through ODIN to return to stock. That is always the safest way out of a sticky situation.
Thanks guys, according to another post the version of EZ-Unlock I used most likely gave a false report and never actually unlocked my phone. The problem with going back to stock, which if what I'm trying to do, is that it fails.
Could be an USB issue - an intermittent connection would be most likely to cause problems while sending the system partition since that's the biggest. I've had problems using adb from time to time if I plug into one of the front-panel ports on my PC but no trouble with one on the back.
Maybe try switching ports or try a different cable ...
Actually what usb plug are you using on your computer? You should be using one in the back of your computer by the power supply. Seen the front jacks not work correctly for large transfers. Finally, try another usb cable.
Sent from my SCH-I535 using xda app-developers app
Strange.... i was able to flash syergy on thefirst try. Never used odin during the whole process....
If youre rooted you need to make sure you have a custom recovery in place like cwm or twrp. Make sure you make a nand-backup.
I used casual to flash unsecure bootloader, with that and recovery in place you should be able to flash roms without any hitches....
I could never find a comprehensive guide on using odin so i never got around to testing it
kintwofan said:
Actually what usb plug are you using on your computer? You should be using one in the back of your computer by the power supply. Seen the front jacks not work correctly for large transfers. Finally, try another usb cable.
Sent from my SCH-I535 using xda app-developers app
Click to expand...
Click to collapse
So far I've tried 3 different USB cables and both a desktop, both front and back ports and a laptop, each one fails on the write of XmitData under system.img.ext4
I had a custom recovery installed and Odin is only being used to get me back to a stock rom, otherwise I did all my flashing under CWM 6.0.1 or twrp. I think the whole fake unlocked bootloader just hard bricked the software.
EDIT: Come to think of it I remember waking up to my phone in download mode. I think Verizon tried to install the update to my phone while I was sleeping. Granted it failed at the end, but I'm wondering if that did something to brick me now.
If you can get in download mode it can be saved. I woud re download the stock firmware or the 66, but personally i would go bone stock. You may just have a bad download.
Sent from my SCH-I535 using xda app-developers app
kintwofan said:
If you can get in download mode it can be saved. I woud re download the stock firmware or the 66, but personally i would go bone stock. You may just have a bad download.
Sent from my SCH-I535 using xda app-developers app
Click to expand...
Click to collapse
Yea, I'm currently downloading at the speed of slug the newest update from the forums, will probably just redownload at home, since it's going to take over an hour >.<
EDIT:
Does anyone have a link for an older EZ-Unlocker, that is known to work, so that I don't get this problem yet again.
FIXED!
Ok, so using the newest stock rom from the dev forum worked. Can someone please give me a link to an old EZ-Unlocker so I can flash without worrying about another massive brick in my palm. I'm guessing that running the original root66 stock rom through dropbox somehow corrupted it.
LlirasChosen said:
Ok, so using the newest stock rom from the dev forum worked. Can someone please give me a link to an old EZ-Unlocker so I can flash without worrying about another massive brick in my palm. I'm guessing that running the original root66 stock rom through dropbox somehow corrupted it.
Click to expand...
Click to collapse
I personally suggest not using the app if you already had trouble. Just root your phone using the Debug Root method in Development, download the aboot.img from Adam Outlers thread HERE to your phone, and run the commands at the very bottom in Terminal Emulater app (from the market).
That way you know for sure your bootloader is unlocked. This is what I have done and never had an issue.
Edit: Glad you got your issue resolved!

[Q] Unauthorized software message ONLY when booting into recovery

This is my first post ever here so I'm sorry if I'm breaking some rule (read the forum rules so I don't think I am) or if it's in the wrong subforum (although this does seem like a help & troubleshooting topic to me).
A little backstory is probably necessary.
I rooted my s3 (latest OTA update) via CASUAL (thread: http://forum.xda-developers.com/showthread.php?t=2332825) and it seemed like it worked for the most part, although it didn't boot into twrp like it should have and instead booted into normal recovery. I just assumed that it was because something went wrong with the recovery installation so I just thought "ok whatever."
Root access was there, and I assumed the bootloader was unlocked since I read several places that when it's unlocked, the initial samsung boot logo appears for about a second as opposed to several seconds when it's locked. So I just assumed all i needed was to reinstall a custom recovery and I was golden.
Installed ROM Manager, flashed CWM through the app, and rebooted the phone, and as it was booting into recovery I was greeted with the infamous "NO CUSTOM SOFTWARE ALLOWED PLEASE ALERT PAPA VERIZON IMMEDIATELY" warning.
I was about to flash back to stock through odin (which i regretted since I've had bad experiences in the past using it) when I figured out I could get the device to boot normally by clicking cancel in the download mode confirmation window. I guess it kept trying to reboot to recovery after every unsuccessful boot, which made it seem like it was softbricked to me.
Phone is operating normally now, and it should after another reboot as long as it doesn't try to go into recovery again (though I'm kind of afraid to even do that).
Is there any way without Odin I can fix my recovery and/or bootloader? I'm not sure what the problem is here and I don't think this sort of thing is a common searchable issue. Google/XDA search didn't bring up anything that sounded like someone had 100% the same problem I do.
Also on a semi-related note, does EZ-Unlock still work with this latest OTA? And if my bootloader is potentially unlocked already, would unlocking it again through EZ-Unlock break something?
Sleix said:
This is my first post ever here so I'm sorry if I'm breaking some rule (read the forum rules so I don't think I am) or if it's in the wrong subforum (although this does seem like a help & troubleshooting topic to me).
A little backstory is probably necessary.
I rooted my s3 (latest OTA update) via CASUAL (thread: http://forum.xda-developers.com/showthread.php?t=2332825) and it seemed like it worked for the most part, although it didn't boot into twrp like it should have and instead booted into normal recovery. I just assumed that it was because something went wrong with the recovery installation so I just thought "ok whatever."
Root access was there, and I assumed the bootloader was unlocked since I read several places that when it's unlocked, the initial samsung boot logo appears for about a second as opposed to several seconds when it's locked. So I just assumed all i needed was to reinstall a custom recovery and I was golden.
Installed ROM Manager, flashed CWM through the app, and rebooted the phone, and as it was booting into recovery I was greeted with the infamous "NO CUSTOM SOFTWARE ALLOWED PLEASE ALERT PAPA VERIZON IMMEDIATELY" warning.
I was about to flash back to stock through odin (which i regretted since I've had bad experiences in the past using it) when I figured out I could get the device to boot normally by clicking cancel in the download mode confirmation window, rebooting the phone normally. I guess it kept trying to reboot to recovery after every unsuccessful boot, which made it seem like it was softbricked to me.
Phone is operating normally now, and it should after another reboot as long as it doesn't try to go into recovery again (though I'm kind of afraid to even do that).
Is there any way without Odin I can fix my recovery and/or bootloader? I'm not sure what the problem is here and I don't think this sort of thing is a common searchable issue. Google/XDA search didn't bring up anything that sounded like someone had 100% the same problem I do.
Also on a semi-related note, does EZ-Unlock still work with this latest OTA? And if my bootloader is potentially unlocked already, would unlocking it again through EZ-Unlock break something?
Click to expand...
Click to collapse
That is really weird...
I was reading it and was going to suggest easy unlock v1.2,you will not break anything using that app.
If that still doesn't work, try to flash TWRP through goo manager and see if it somehow fixes your recovery issue.
It sounds to me that your Bootloader is unlocked though... But give it a shot.
Sent from my SCH-I535 using Tapatalk 2
BadUsername said:
That is really weird...
I was reading it and was going to suggest easy unlock v1.2,you will not break anything using that app.
If that still doesn't work, try to flash TWRP through goo manager and see if it somehow fixes your recovery issue.
It sounds to me that your Bootloader is unlocked though... But give it a shot.
Sent from my SCH-I535 using Tapatalk 2
Click to expand...
Click to collapse
Thanks for the quick response.
That was going to be what I tried first, that's why I asked about it.
I'll wait for a little more input before trying it though if it's really that weird of an issue.
Sleix said:
Thanks for the quick response.
That was going to be what I tried first, that's why I asked about it.
I'll wait for a little more input before trying it though if it's really that weird of an issue.
Click to expand...
Click to collapse
It's just strange that you only get that message with recovery mode, it normally will not do that.
At the very worst, an odin back to stock is pretty easy. Just follow the same process, but use ez recovery instead of rom manager. It was made specifically for our phone, and never gives me any issues when installing recoveries.
I still think if you use ez unlock it'll probably fix the issue completely. Let me know if you figure it out. Good luck.
Sent from my SCH-I535 using Tapatalk 2
BadUsername said:
It's just strange that you only get that message with recovery mode, it normally will not do that.
At the very worst, an odin back to stock is pretty easy. Just follow the same process, but use ez recovery instead of rom manager. It was made specifically for our phone, and never gives me any issues when installing recoveries.
I still think if you use ez unlock it'll probably fix the issue completely. Let me know if you figure it out. Good luck.
Sent from my SCH-I535 using Tapatalk 2
Click to expand...
Click to collapse
Thanks. Used ez unlock to unlock the bootloader. It was previously labeled as "Unknown".
Downloading ez recovery right now. Do you think I need to reinstall my recovery just to make sure?
Sleix said:
Thanks. Used ez unlock to unlock the bootloader. It was previously labeled as "Unknown".
Downloading ez recovery right now. Do you think I need to reinstall my recovery just to make sure?
Click to expand...
Click to collapse
No, but it wouldn't hurt.
Use 1.2 of ez unlock, versions 1.3 and 1.4 will give an unknown message. There have also been lots of reports saying that version 1.4 did not unlock their bootloader.
These are the most recent recoveries, download and flash in the ez recovery app if you need to.
http://forum.xda-developers.com/showthread.php?t=2096735
Sent from my SCH-I535 using Tapatalk 2
BadUsername said:
No, but it wouldn't hurt.
Use 1.2, versions 1.3 and 1.4 will give an unknown message. There have also been lots of reports saying that version 1.4 did not unlock their bootloader.
Sent from my SCH-I535 using Tapatalk 2
Click to expand...
Click to collapse
Reflashed CMW (I used the version provided by ez recovery, please let me know if that's a problem) just in case and it worked like a charm. Thanks!
Also I did use version 1.2. I actually had it sitting on my phone's home screen before I made this thread.
It still showed up as "Unknown". Maybe that indicated the problem?
Regardless, this problem seems to have been fixed. Now it's time to do some research on verizon s3 roms.
Also another semi-unrelated note, it seems I tripped a flash counter somewhere along the line.
Is Triangle Away one of those apps that is just "open and press a button"? I've been kind of wary of using it since it has that huge warning in app's description.
Sleix said:
Reflashed CMW (I used the version provided by ez recovery, please let me know if that's a problem) just in case and it worked like a charm. Thanks!
Also I did use version 1.2. I actually had it sitting on my phone's home screen before I made this thread.
It still showed up as "Unknown". Maybe that indicated the problem?
Regardless, this problem seems to have been fixed. Now it's time to do some research on verizon s3 roms.
Also another semi-unrelated note, it seems I tripped a flash counter somewhere along the line.
Is Triangle Away one of those apps that is just "open and press a button"? I've been kind of wary of using it since it has that huge warning in app's description.
Click to expand...
Click to collapse
Glad to hear it's working! Strange issue but looks like you ironed it out.
Triangle away is the app you would use. You tripped it using the rooting method injecting your recovery through odin, it's a big warning because it messes with your boot partition. If it fails and borks your boot partition, then you'd have to jtag your phone to fix it.
I personally wouldn't use it unless I was turning in my phone for service or replacement. But the app has great reviews and not many reports of bricks.
Before flashing anything, use a newer recovery image. The one provided by ez recovery is from last year, the newer versions are better written to prevent possible errors that come up with jellybean.
Sent from my SCH-I535 using Tapatalk 2
BadUsername said:
Glad to hear it's working! Strange issue but looks like you ironed it out.
Triangle away is the app you would use. You tripped it using the rooting method injecting your recovery through odin, it's a big warning because it messes with your boot partition. If it fails and borks your boot partition, then you'd have to jtag your phone to fix it.
I personally wouldn't use it unless I was turning in my phone for service or replacement. But the app has great reviews and not many reports of bricks.
Sent from my SCH-I535 using Tapatalk 2
Click to expand...
Click to collapse
I'll keep that in mind, thanks again!
Any roms you'd recommend?
Sleix said:
I'll keep that in mind, thanks again!
Any roms you'd recommend?
Click to expand...
Click to collapse
Read through the op's and decide based on what you're looking for.
Mostly stock, very stable:
Clean rom, bonestock, darthstalker x1.
More modified stocks, more buggy but can run very well:
Hyperdrive, axis, goodness, moar
AOSP isn't my cup of tea, but they are fast and lag free.
Make sure you update your recovery image first, I edited my last post but think you missed it.
Sent from my SCH-I535 using Tapatalk 2
BadUsername said:
Read through the op's and decide based on what you're looking for.
Mostly stock, very stable:
Clean rom, bonestock, darthstalker x1.
More modified stocks, more buggy but can run very well:
Hyperdrive, axis, goodness, moar
AOSP isn't my cup of tea, but they are fast and lag free.
Make sure you update your recovery image first, I edited my last post but think you missed it.
Sent from my SCH-I535 using Tapatalk 2
Click to expand...
Click to collapse
Will do. Thanks for pointing that edit out.

Having trouble getting Heimdall to work on OSX

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

[Q] Bad Recovery flash? (SOLVED)

I've done some searching, finding similar things that have happened to others here, but nothing that specifically fits what I'm experiencing...
I'm hoping someone has a step-by-step that I can do to get this phone rooted properly... First, I've been on XDA for a while, Droid Eris and HTC Incredible 2, but this is the first Samsung phone I've owned... A few days ago, I tried the Casual Root method and went ahead and rooted, unlocked the bootloader (unsecure ABOOT) and loaded CWM touch as my recovery. All looked fine, but when I went in to recovery to try and backup the stock rom, it threw a ton of Not able to write/Cannot Mount errors... My phone came with the MF1 4.1.2 already running.
Since, I've tried EZ-Unlock 1.2 to check and unlock the bootloader (which it showed as "Unknown" until I clicked unlock) and I've tried installing different recoveries through EZ Recovery (TWRP 2.2.2, CWM variants, etc...). Still, no joy in getting this to work properly.
The last attempt kept the phone in Download mode until I rebooted using the Power, Vol. Down, Menu to bypass it (Not detecting ANY recovery now!?). I'm still able to get back to the original Rom (which is rooted now), but I'm concerned with bricking if I keep trying this.
So, I'm thinking now of just doing an Odin back to stock and reflashing all the original firmware so I can start over with Casual. Was wondering if anyone had any other input which might get the R/W issue fixed so I don't have to go through all the Odin stuff? Compared to HTC phones, this is quite different with Root/Flashing, so I'm a little confused with the whole process of things right now... Any help would really be appreciated! I'm looking forward to deving at some point, once I'm comfortable with the process...
Thanks,
Rich
Anyone?
Sent from my SCH-I535 using xda premium
Never mind...
Macrodroid said:
I've done some searching, finding similar things that have happened to others here, but nothing that specifically fits what I'm experiencing...
I'm hoping someone has a step-by-step that I can do to get this phone rooted properly... First, I've been on XDA for a while, Droid Eris and HTC Incredible 2, but this is the first Samsung phone I've owned... A few days ago, I tried the Casual Root method and went ahead and rooted, unlocked the bootloader (unsecure ABOOT) and loaded CWM touch as my recovery. All looked fine, but when I went in to recovery to try and backup the stock rom, it threw a ton of Not able to write/Cannot Mount errors... My phone came with the MF1 4.1.2 already running.
Since, I've tried EZ-Unlock 1.2 to check and unlock the bootloader (which it showed as "Unknown" until I clicked unlock) and I've tried installing different recoveries through EZ Recovery (TWRP 2.2.2, CWM variants, etc...). Still, no joy in getting this to work properly.
The last attempt kept the phone in Download mode until I rebooted using the Power, Vol. Down, Menu to bypass it (Not detecting ANY recovery now!?). I'm still able to get back to the original Rom (which is rooted now), but I'm concerned with bricking if I keep trying this.
So, I'm thinking now of just doing an Odin back to stock and reflashing all the original firmware so I can start over with Casual. Was wondering if anyone had any other input which might get the R/W issue fixed so I don't have to go through all the Odin stuff? Compared to HTC phones, this is quite different with Root/Flashing, so I'm a little confused with the whole process of things right now... Any help would really be appreciated! I'm looking forward to deving at some point, once I'm comfortable with the process...
Thanks,
Rich
Click to expand...
Click to collapse
If you were able to root your phone successfully, then what I would recommend what to do is download whatever image you want (for me, I downloaded twrp 2.6.3.0) and then flash it through flashify (free in play store).
If you want to get it an easier way, then use goomanager and then install open recovery script (you'll see it when you press menu). It should install the recovery automatically.
If you want clockworkmod touch, then if you want an image, use flashify to flash it. Doing either of the options will give you a working recovery.
david_hume said:
If you were able to root your phone successfully, then what I would recommend what to do is download whatever image you want (for me, I downloaded twrp 2.6.3.0) and then flash it through flashify (free in play store).
If you want to get it an easier way, then use goomanager and then install open recovery script (you'll see it when you press menu). It should install the recovery automatically.
If you want clockworkmod touch, then if you want an image, use flashify to flash it. Doing either of the options will give you a working recovery.
Click to expand...
Click to collapse
Ok, I've gotvtwrp 2.6.3.0 loaded, works... But, I cannot mount anything, backup totally fails. Any ideas? Twrp also asks for a password for some reason...
Btw, nice to see a familiar face on here! How's life treating you these days?
Sent from my SCH-I535 using xda premium
Try this. But download and use the correct and updated cwm recovery from somewhere else.
http://bestandroidtricks.com/how-to...covery-on-the-samsung-galaxy-s3-all-versions/
Sent from my SCH-I535 using xda app-developers app
stolo said:
Try this. But download and use the correct and updated cwm recovery from somewhere else.
http://bestandroidtricks.com/how-to...covery-on-the-samsung-galaxy-s3-all-versions/
Sent from my SCH-I535 using xda app-developers app
Click to expand...
Click to collapse
Thanks! After going through Rom Manager and letting it update CWR on it's own, I finally got everything working now! Backup of the Stock Rom is done finally and I can start flashing some Rom's to get comfortable with things... Hopefully, I can start putting out some Rom's for this device soon!! Thanks for all the help, I really appreciate it!
I have been using kitkang cm11, so far really excited and loving 4.4. I have been updating daily.
Sent from my SCH-I535 using xda app-developers app
stolo said:
I have been using kitkang cm11, so far really excited and loving 4.4. I have been updating daily.
Sent from my SCH-I535 using xda app-developers app
Click to expand...
Click to collapse
Got wicked loaded up! So far, so good. I might try pulling a repo on cm11 sometime soon...
Sent from my SCH-I535 using xda premium

Categories

Resources