Database Info

Recovery Help

I have clockworkmod and I updated the recovery to 3.0.0.8. When I boot into recovery and try to install EC10 comavolt and it won't let me. I also tried to install other recovery's via Rom Manager but it says download failed.

ddb1984 said:
I have clockworkmod and I updated the recovery to 3.0.0.8. When I boot into recovery and try to install EC10 comavolt and it won't let me. I also tried to install other recovery's via Rom Manager but it says download failed.
Click to expand...
Click to collapse
Rom manager is not compatible with our phones. You will likely need to revert back to an older version of cwm.
Sent from my SCH-I500 using XDA App

akellar said:
Rom manager is not compatible with our phones. You will likely need to revert back to an older version of cwm.
Sent from my SCH-I500 using XDA App
Click to expand...
Click to collapse
Ohhhhhhh OK well how would I go about reverting back and I am looking for the info while Im sending this

ddb1984 said:
Ohhhhhhh OK well how would I go about reverting back and I am looking for the info while Im sending this
Click to expand...
Click to collapse
I too would also like to know where I can get this older version of cwm.

http://forum.androidcentral.com/ver...roms-w-root-clockwork-updated-3-25-a-389.html
There should be a link to a cwm.tar file (not the exact name) on this page. Flash it via odin and there you go.
Sent from my SCH-I500 using XDA App

emarohl said:
http://forum.androidcentral.com/ver...roms-w-root-clockwork-updated-3-25-a-389.html
There should be a link to a cwm.tar file (not the exact name) on this page. Flash it via odin and there you go.
Sent from my SCH-I500 using XDA App
Click to expand...
Click to collapse
Thats my problem I cant use my USB right now and I can only zip at the moment but barely can do that do to the Recovery messing up

Can't use USB right now...? I think you might be confusing transferring files to the USB card while the phone is booted, with flashing a TAR file via Odin.
Remember--when you're flashing via Odin, your battery is pulled, the phone is off, and then--while you do plug in your USB cable--it's only receiving power through that USB connection.
Use BDE's "How to customize.." guide here, and go directly to step 2. If you don't already have it, grab the "Red" Recovery from this thread (also linked to in BDE's guide); grab the TAR file listed there. Then go back to the guide and follow the instructions for Step 2.
That should get your recovery back to Red recovery, and I think from there I'd make sure everything else is working and the phone boots before doing anything else. Once it's up and running, then maybe give the kernel another shot.
EDIT: Thought of what else you might mean; if you're unable to get Odin to recognize when your phone is plugged in, hit up the Samsung website to get the Samsung USB drivers. Then, when you hold the volume down key as described in the guide, you should see one cell of Odin turn yellow, which tells you your phone has been recognized. Assuming you have a Windows PC, at least.

ChromWolf said:
Can't use USB right now...? I think you might be confusing transferring files to the USB card while the phone is booted, with flashing a TAR file via Odin.
Remember--when you're flashing via Odin, your battery is pulled, the phone is off, and then--while you do plug in your USB cable--it's only receiving power through that USB connection.
Use BDE's "How to customize.." guide here, and go directly to step 2. If you don't already have it, grab the "Red" Recovery from this thread (also linked to in BDE's guide); grab the TAR file listed there. Then go back to the guide and follow the instructions for Step 2.
That should get your recovery back to Red recovery, and I think from there I'd make sure everything else is working and the phone boots before doing anything else. Once it's up and running, then maybe give the kernel another shot.
EDIT: Thought of what else you might mean; if you're unable to get Odin to recognize when your phone is plugged in, hit up the Samsung website to get the Samsung USB drivers. Then, when you hold the volume down key as described in the guide, you should see one cell of Odin turn yellow, which tells you your phone has been recognized. Assuming you have a Windows PC, at least.
Click to expand...
Click to collapse
Yea I even put in another post about my USB issues and can't seem to find a solution. I may just purchase another phone. My girls works perfect and no connection problems but I may of damaged it or something but it only charges doesn't work other wise. ADB, USB file transfer, nothing.

ChromDog's post was a mess. I'm ignoring it.
So you're saying you can't even get the phone to work in Download mode? Will the phone actually boot up into Download mode?

add144 said:
ChromDog's post was a mess. I'm ignoring it.
So you're saying you can't even get the phone to work in Download mode? Will the phone actually boot up into Download mode?
Click to expand...
Click to collapse
Yea I get the yellow screen with the android saying downloading. I have tried 3 cables and 5 diff computers. I even went to cellular south and got a new cable. When I figured it was my phone was when my girls phone worked with the same equipment. Also sometimes when I plug it up to the PC doing download mode it will say USB Not Recognized and I have the drivers installed I even tried to select the specific driver but didnt know which one to do out the that folder of many LOL

Have you tried opening ODIN in Download Mode anyway just to see if it'll recognize the phone?

add144 said:
ChromDog's post was a mess. I'm ignoring it.
Click to expand...
Click to collapse
Rare is the occasion that wiser words than these have been uttered. XD
While I was getting pretty wordy with my answer, Add's more or less on the same track as me: Even with the USB not working when the phone's booted normally, does Odin recognize it even so, or is Odin what you've been trying and not getting to work?

ddb1984 said:
Yea I get the yellow screen with the android saying downloading. I have tried 3 cables and 5 diff computers. I even went to cellular south and got a new cable. When I figured it was my phone was when my girls phone worked with the same equipment. Also sometimes when I plug it up to the PC doing download mode it will say USB Not Recognized and I have the drivers installed I even tried to select the specific driver but didnt know which one to do out the that folder of many LOL
Click to expand...
Click to collapse
The different computers you tried wouldn't really matter unless each one had the Samsung USB driver installed. Also, does your girlfriend have the same model phone as you? If not, it's not necessarily a fair test.
It does sound like you've tried using Odin, and it just hasn't worked (based on the bolded part). So, try this:
http://www.samsung.com/us/support/downloads/SCH-I500RKAXAR
Go to the above link. Underneath where it says "Download Center for SCH-I500RKAXAR", look for "Manuals | Software". Software should be a blue link; click on that.
You should see a list of four items you can download. Look all the way to the right, under the "File" column; there should be four little icons. Click on the first of the four, and Agree to their user agreement. Save the file somewhere easy to remember, and run that file. I'd suggest doing this on any home computer you might connect your Showcase to.
Then, try putting the phone in Download mode and connecting to Odin once again.
Does it work after that?

I dont know how or why but I was able to get odin to work on a XP machine and I flashed the odin files for pick and pack and the odin files for cwm recovery all and was able to get both the recovery and 2.2 but I have more problems LOL. My internal memory is 0. I factory wiped and wiped cache via red recovery but to no avail. Still getting 0

If you can get into your phone and do stuff in Android, I'd run a Titanium Backup of your apps and stuff. If not, you may be SOL.
I'd start by just finding a stock ROM for 2.1 or 2.2.1 and Odin'ing that over to the phone. Start completely clean, no custom ROMs. Then load up CWM Red again.

ChromWolf said:
If you can get into your phone and do stuff in Android, I'd run a Titanium Backup of your apps and stuff. If not, you may be SOL.
I'd start by just finding a stock ROM for 2.1 or 2.2.1 and Odin'ing that over to the phone. Start completely clean, no custom ROMs. Then load up CWM Red again.
Click to expand...
Click to collapse
I have been looking for 2.1 Stock Rom for CS but I have not been able to. I have my apps backed up but unfortunately I can't install them in this Rom yet but I will keep trying to get it.

Ouchie! I just had a look throughout the Mes Dev thread, and the one post I saw for EB11 for Showcase had the link removed. Couldn't find any other reference for an actual stock 2.1 or 2.2.1 specifically for the showcase; the guys *may* tell you the Mesmerize ones work for Showcase, but DO NOT use them until one of them says so. I would guess not, but don't know for sure.
I'd see about hitting the IRC channel and asking for a clean stock ROM from there, and/or maybe getting some "in-person" advice that way. ...or hope Phidelt82 or Elijahblake come across this thread to get it to you/help you out otherwise. XD

LOL IKR but I have already asked them for a Stock 2.1 Rom for CS and I was pointed to someone but they haven't responded to me so idk. And thanks for some of the info and I am happy I was able to get the files b4 he removed his comments. I had them already saved on the computer.

ddb1984 said:
LOL IKR but I have already asked them for a Stock 2.1 Rom for CS and I was pointed to someone but they haven't responded to me so idk. And thanks for some of the info and I am happy I was able to get the files b4 he removed his comments. I had them already saved on the computer.
Click to expand...
Click to collapse
Some individuals were trying to put together a 2.1 stock image but weren't able to get one working, the one they have is stock 2.2 and that is the only pure stock ROM they have, but there is no reason to go back to 2.1 unless you planned on using it and staying with it, so a clean flash to 2.2 should fix any issues you may be experiencing.

bdemartino said:
Some individuals were trying to put together a 2.1 stock image but weren't able to get one working, the one they have is stock 2.2 and that is the only pure stock ROM they have, but there is no reason to go back to 2.1 unless you planned on using it and staying with it, so a clean flash to 2.2 should fix any issues you may be experiencing.
Click to expand...
Click to collapse
I am with Cellular South and I don't believe there is a stock for us just yet. I was also able to put the SDcard in a card reader and put Superclean 2.9.2 on it for Showcase. Pray I get internal storage and my phone works.
YES!!!!!!!! Internal Storage w/ Superclean and a working recovery. Well I have more issues to attend to but that's wonderful to me.

[HOW-TO]Fix your phone

Initially, this post was meant to fix people's phones after a bad restore from CWM, but now I'm changing it to be more general and pretty much be a guide for how to fix your phone from nearly any problem. The original reason for this post is this error:
Code:
-- bootmode=7 from cmdline...
-- Movi_check Start..!!
checksum confirmation need_checksum[0]
Not need checksum confirmation
--Movi_check already executed!!...
--movi_checking done!...
# MANUAL MODE #
It was caused by a problem with /data and this guide helped fix that. Now that several other things have come along (leaks, voodoo, etc.) people are having a host of random errors show up with their phones. This guide will hopefully get you back to a working phone regardless of what is wrong with it. Take note though, that following this guide will delete all data not on the sdcard. So, with that being said, here is how you can fix your phone.
1. Download one of the packages below as well as the PIT file.
2. Open up Odin, click PDA, and select the package you downloaded
3. Click on PIT and select the PIT file that you downloaded.
4. Get your phone into Download mode.
4a. Pull out the battery, hold down on Vol Down, and plug in the USB Cable while still holding the button.
4b. After you are in Download Mode, put the battery back into your phone. This increases the reliability of flashing with Odin
5. Make sure your phone is recognized in Odin
6. Check the box for Re-partition (Odin will fail if you check this and don't use the PIT file) and un-check the boxes for Auto-Reset and F. Reset Time.
7. Press "Start" and flash the package.
8. After it is finished flashing, take the battery out, unplug the USB cable, put the battery back in, and start up what should now be a working phone.
Download descriptions. There are 3 files linked to below. The first is the PIT file, and required for this. The PIT file is the partition information table. It tells your phone where different packages go on the phone, as well as how big partitions are on the phone. Without this information, Odin cannot properly re-partition your device. The next two files are more or less the same and you will only need one of the two, not both (unless you want them just for fun). There is ED1, which is what the phone initially shipped with, and ED2, the update that was released just after the phone was. The ED1 package may be a little bit smaller for those that are concerned about download size as it is compressed. However, you will need 7-zip or similar to extract it after downloading. Also note that this cannot be done with Heimdall as Heimdall does not have the ability to re-partition your phone, thus, you need a Windows computer to be able to follow this procedure.
All packages are available here.

Sweet, as always thanks for the work/effort on this stuff. At least now we don't have to be AS concerned atm if a restore was done in CWR and someone hoses there device.

this work for anyone?

Updated this with what I believe to be the proper steps. I was in and out at work while papi was fixing his phone, and lost track of the exact files used, but some combination of the above Odin packages and the PIT should get you back to a working phone if you are having a problem.

Good sh|t man ... phone was bound to have growing pains.

papi92 said:
this work for anyone?
Click to expand...
Click to collapse
Unfortunately, I am trying to fix this very problem right now.
I was able to get rid of the error message with your method and I can now get into CWM again.. which is progress. I used the smaller file as it looks like the bigger one was corrupt for me (may just have been a bad dl on my end). I'm re downloading the full file now.
Anyway, I used odin. Selected the charge.pit and repartitioned. I allowed that to finish. I then restarted and flashed the smaller .md5 file. I then was able to reboot into CWM.. which is where I am now as the system just boot loops on the Samsung logo ATM.
Any words of wisdom to get me out of the boot loop would be great.. I'll check back later - hopefully with news that I fixed my phone.

trebores1 said:
Unfortunately, I am trying to fix this very problem right now.
I was able to get rid of the error message with your method and I can now get into CWM again.. which is progress. I used the smaller file as it looks like the bigger one was corrupt for me (may just have been a bad dl on my end). I'm re downloading the full file now.
Anyway, I used odin. Selected the charge.pit and repartitioned. I allowed that to finish. I then restarted and flashed the smaller .md5 file. I then was able to reboot into CWM.. which is where I am now as the system just boot loops on the Samsung logo ATM.
Any words of wisdom to get me out of the boot loop would be great.. I'll check back later - hopefully with news that I fixed my phone.
Click to expand...
Click to collapse
Can you flash anything in CWM? Or how about odin the Ed1 rooted package.?

hoppermi said:
Can you flash anything in CWM? Or how about odin the Ed1 rooted package.?
Click to expand...
Click to collapse
I'm going to try that next.. it's downloading now (slowly). It may just be me, but I can't get the full ED1_CWM_Fix.tar.md5 to flash at all. I have now downloaded it from multishare direct and rapidshare and both fail the same way (Write operation failed).

hoppermi said:
Can you flash anything in CWM? Or how about odin the Ed1 rooted package.?
Click to expand...
Click to collapse
And, yes - I was able to previously flash the ed2-debloat rom from CWM, but it wouldn't boot up... I may try that again while I'm waiting for the stock-ED1 root to finish downloading.

trebores1 said:
I'm going to try that next.. it's downloading now (slowly). It may just be me, but I can't get the full ED1_CWM_Fix.tar.md5 to flash at all. I have now downloaded it from multishare direct and rapidshare and both fail the same way (Write operation failed).
Click to expand...
Click to collapse
Pretty sure that papi flashed this http://forum.xda-developers.com/showthread.php?t=1085190 one the error message was gone, and he was good to go.

Hey after you flash the smaller package given by imnuts07 I flashed stock ed1 rooted thru odin and it worked.
Sent from my SCH-I510 using XDA Premium App

papi92 said:
Hey after you flash the smaller package given by imnuts07 I flashed stock ed1 rooted thru odin and it worked.
Sent from my SCH-I510 using XDA Premium App
Click to expand...
Click to collapse
Yeah, that worked. It got rid of the error and I can now boot into stock recovery.. but I'm stuck in a droid eyeball bootloop now. Not sure what else to do. I factory reset everything. I think it's time to just return to the VZW store.

Don't return it. You got that far it can be restored. Try flashing altered beast thru odin o
Sent from my SCH-I510 using XDA Premium App

Also start up took about 10 minutes for me and make sure your phone still isn't on ext 4.
Sent from my SCH-I510 using XDA Premium App

Same here. Flashing altered beast fixed the problem and let me cwm flash debloatedv4. (4.1 seems really buggy)
Sent from my SCH-I510 using Tapatalk

papi92 said:
Also start up took about 10 minutes for me and make sure your phone still isn't on ext 4.
Sent from my SCH-I510 using XDA Premium App
Click to expand...
Click to collapse
I think I turned off ext4. In cwm I disabled the voodoo lagfix and the voice said that it was disabled. How else would I tell if it's off?
I tried your other suggestions too. Flashed altered beast, ed1 rooted, no luck getting past the bootup loop.
When you restored via Odin using the almost-everything.tar.md5, were you able to reboot and use your phone? I can't get that far. If I reboot it just hangs on the samsung logo. After that, I can flash altered beast or ed1-rooted and I get to the droid bootloop.
Trust me, I don't want to return it.. I'm sure there's a fix here somewhere.

You need to wipe data. You have too. And yes I got stuck at Samsung logo after. I had to flash stock ed1 rooted then wipe data
Sent from my SCH-I510 using XDA Premium App

trebores1 said:
I think I turned off ext4. In cwm I disabled the voodoo lagfix and the voice said that it was disabled. How else would I tell if it's off?
I tried your other suggestions too. Flashed altered beast, ed1 rooted, no luck getting past the bootup loop.
When you restored via Odin using the almost-everything.tar.md5, were you able to reboot and use your phone? I can't get that far. If I reboot it just hangs on the samsung logo. After that, I can flash altered beast or ed1-rooted and I get to the droid bootloop.
Trust me, I don't want to return it.. I'm sure there's a fix here somewhere.
Click to expand...
Click to collapse
To find out if lagfix is disabled run mount from a root terminal app, or adb shell mount if you're hooked up to your computer. If anything shows up as ext4, lagfix is still enabled. If it is all rfs/vfat/not ext4 then you're ok.

Progress has been made! I followed steps 1-8 on imnuts guide. On step 8, nothing happens(as it should). Rebooted into download mode, flashed almost-everything, rebooted, system hangs on samsung logo. Rebooted into download mode, flashed ed1-rooted. Rebooted, system boots into phone!
Now I get an error that my sim card is not supported or readable.. but at least I got back into the phone..

trebores1 said:
Progress has been made! I followed steps 1-8 on imnuts guide. On step 8, nothing happens(as it should). Rebooted into download mode, flashed almost-everything, rebooted, system hangs on samsung logo. Rebooted into download mode, flashed ed1-rooted. Rebooted, system boots into phone!
Now I get an error that my sim card is not supported or readable.. but at least I got back into the phone..
Click to expand...
Click to collapse
Did you activate another phone? I know someone w/ a TB who reactivated his Fascinate then wanted to switch back and his sim wouldn't work. Had to get a new one.
Sent from my SCH-I510 using Tapatalk

[Q] Having trouble with Odin 1.85

Recently rooted my droid charge using voodoo lagfix kernel with odin 1.85. Everything went fine until I tried to put files on my SD card. So I found the forum that had the fix. Wasn't able to put fix file on the SD no matter what I did. So I just said forget it and I went ahead and flash my phone back to the stock ROM using Odin 1.85. Now every time I go to flash it odin says it fails. Now I've flash my phone to factory before and it worked perfect. Also I put gingerbread on it and that worked. Now I can't do it anymore. It just keeps failing.
Any suggestion?
Thanks,
Brian
EDIT: Not just odin 1.85 Any version I use doesn't work.

bvsbutthd101 said:
Recently rooted my droid charge using voodoo lagfix kernel with odin 1.85. Everything went fine until I tried to put files on my SD card. So I found the forum that had the fix. Wasn't able to put fix file on the SD no matter what I did. So I just said forget it and I went ahead and flash my phone back to the stock ROM using Odin 1.85. Now every time I go to flash it odin says it fails. Now I've flash my phone to factory before and it worked perfect. Also I put gingerbread on it and that worked. Now I can't do it anymore. It just keeps failing.
Any suggestion?
Thanks,
Brian
EDIT: Not just odin 1.85 Any version I use doesn't work.
Click to expand...
Click to collapse
what are the steps you're using in odin? put the battery back in to flash stuff (if you don't already have it in) if it keeps failing... also what are you trying to flash and where are you trying to end up rom/kernel wise?

I just want to put the stock ROM back on. Right now I have my phone booted up but I dont have service. I have 4G but no calling services. But the weird thing is that when I just ran odin it said it failed but I just shut my phone off and it booted up.

bvsbutthd101 said:
I just want to put the stock ROM back on. Right now I have my phone booted up but I dont have service. I have 4G but no calling services. But the weird thing is that when I just ran odin it said it failed but I just shut my phone off and it booted up.
Click to expand...
Click to collapse
Yeah if an odin flash fails and you unplug it and boot it up it will start the last rom you were running. You can still get it into download mode for odin right? Strange that its not flashing right... Try using a different USB port on your pc (as well as plug in your pc for good measure), disable any antivirus software you may have or run Odin as administrator, then put the battery back in for odin as always only use PDA and/or PIT sections

tried all my usb ports, but yeah getting into download mode works fine. But I just got back from verizon. There sending me a new phone.

bvsbutthd101 said:
tried all my usb ports, but yeah getting into download mode works fine. But I just got back from verizon. There sending me a new phone.
Click to expand...
Click to collapse
I probably would've tried a little more to fix it, its extremely hard to brick this phone or make it so you can't recover or get back to stock... anyways thats good, hope its easier to odin with the new one

yeah, i think ill wait for them to come out with a kernel that doesn't make it so your SD card stops working when you root the phone. Right now my phone is working fine except the fact that I can't make phones calls.

bvsbutthd101 said:
yeah, i think ill wait for them to come out with a kernel that doesn't make it so your SD card stops working when you root the phone. Right now my phone is working fine except the fact that I can't make phones calls.
Click to expand...
Click to collapse
hmm that's weird, something may have gone wrong internally that has to do with the radio or making calls... though if it's not gonna do what a phone does and make calls then yeah I'd get a new one too

anoninja118 said:
hmm that's weird, something may have gone wrong internally that has to do with the radio or making calls... though if it's not gonna do what a phone does and make calls then yeah I'd get a new one too
Click to expand...
Click to collapse
Exactly, pretty important part if I do say so myself. I'm happy though. They didn't give any problem. I didn't even ask to get a new phone. They just told me that we'll just send one out to you.

Soooo I did something stoopid

I flashed the 0817_charge_recovery.tar.md5. I didnt see that it worked and then went back into download, thru Odin, tried to flish cwm_Recovery4008.tar. Got a fail and now when i try to turn on it just shows an icon of a phone with a yellow triangle exclamation point between that and a computer icon. it still goes into download mode with volume down and usb connection but it wont flash the default VZW rom back.
Suggestions?

Battery in or out?

battery in = (phone) ... ! ... (cpu)
battery out = can still go into download mode

Did you come from another rom? I think if you want to flash back to stock from another rom via odin you need to also flash the pit file. At least thats what I had to do.
Sent from my SCH-I510 using XDA App

No i had reverted back to the stock (pentafive ee4 full factor tar).

Have you tried everything from imnuts Fix your Phone thread?
http://forum.xda-developers.com/showthread.php?t=1111486

Ya i got a fail for that as well on Odin. Also tried the Samsung PST and it said error download there as well

DRO1DZ1LLA said:
Ya i got a fail for that as well on Odin. Also tried the Samsung PST and it said error download there as well
Click to expand...
Click to collapse
Are you keeping the battery out during the entire process? You're using the PIT too with the Re-partition box checked (unchecked Auto Restart and F. Time)?

I left the battery in cause in step 4b he says to but anyways it worked. the first time i tried i was using the ed2 file cause for some reason the ed1 link wasnt loading. then i realized i had that file already from somewhere else and used that and it went through

DRO1DZ1LLA said:
I left the battery in cause in step 4b he says to but anyways it worked. the first time i tried i was using the ed2 file cause for some reason the ed1 link wasnt loading. then i realized i had that file already from somewhere else and used that and it went through
Click to expand...
Click to collapse
Nice, bro! Glad to hear you're back up!

thanks for all the help tho! so should i not try to re-root/rom/kernel this ***** or what?

DRO1DZ1LLA said:
thanks for all the help tho! so should i not try to re-root/rom/kernel this ***** or what?
Click to expand...
Click to collapse
Right now, your best bet is to apply whatever system updates there are. If your phone doesn't get you up to EE4 on its own, then you should follow imnuts' instructions here: http://rootzwiki.com/topic/10202-how-to-prepare-for-the-gb-ota/
At some point today, someone will be able to confirm whether the update.zip (leaked) is truly 100% identical to the update.zip that Verizon is pushing out for EP4. If it is, then we'll be safe update to EP4 ahead of the OTA, root, restore any backups, and apply working EP4 themes. I'm anxiously awaiting the ability to depoop my phone--rolled back to stock EE4 last night and have hated my phone ever since!

Haha same. I returned initially for the same reason and then was so sick of it i pushed ahead and messed it up. Still haven't gotten the update tho

Happened to me once. Used stock ee4 odin with the charge .Pit file imnuts posted and it brought me back to stock
Sent from my SCH-I510 using Tapatalk

[Q] Stuck on SGSIII Bootscreen

Before you post, "BLAKDSKF READ OTHER FORUMS BLUSDFLU!!!!!!!111!!!", please, PLEASE, read the whole post. I am not illiterate or a fool. I've spent the last few days researching similar posts, both on xda and other sites, and as far as I've found, this is the only post of this kind on the Verizon SGSIII forums, though there are some that are somewhat similar in the other SGSIII forums (though I think the root of the problem is different). If you can prove me wrong, please redirect.
The Long Story:
ok. SO. I was trying to root my SGSIII, unlock the bootloader, and install CM10. Simple enough, right? Not so. I got through the rooting tutorial at Link 1 relatively smoothly. For the record, I did the composite root and bootloader combo, and I installed CWM Touch Recovery, as per the guide. I also restored the Jellybean Bootchain. I think it was at this point I downloaded Titanium Backup (because forethought is not my forte) and backed up all my apps. I also made a backup with CWM Recovery, but there were errors. I forget the reason, but it aborted backup. I then tried to make a backup onto my external sd card, and some other errors popped up. Mainly that it couldn't find /android.secure (something along those lines) or /sd-ext (might have been something else. I'm going off memory) and skipped them. It still made the backup, so my illiterate, foolish self decided to roll with it and go ahead.
I then went ahead to Link 2, and with it being 2 AM, I stupidly decided to screw trying to figure out how to use Heimdall 1.4rc1 and continue to use ODIN for flashing. After all what's the difference, I thought. One flashing program is the same as another. I flashed the first two files. Well, in truth, I'm not sure if I flashed the first file. Since I just made a single folder for all the SGSIII Verizon flashing stuff, I had two files with similar names at the time. One from Link 1 and one from Link 2. The only difference was one was a boot chain, the other was a boot loader. Also, one ended with .md5 while the other ended with .tar. Sadly I tiredly picked one and flashed it. I think it was the .md5 one, but I'm not sure. Around this point, my micro sd card reader broke, so I decided to just use my other phone (Motorola Photon 4g running Joker's CM9) as a reader of sorts. I swapped them, used my phone to put the zip from Link 2 on it, and swapped them back. I say this because I'm not sure if that is what broke my md5sums or not (more on that in a sec).
Well, surprise, surprise, my phone got stuck on the animated, colorful "4G LTE" boot screen, except it was fully black, though the noise was playing. I think to myself, "No biggie. I'll just restore my previous backup," so I go back to restore it when I get the error 'md5sum mismatch'. I look up the problem, and after extensive, 3AM research (read: clicked the first link on google and blindly followed), I went with one guys advice, which was to create a blank nandroid.md5 file to force the restore. I figured, "Hey. This is pretty risky. I think I'll just restore the bootloader instead of the whole restore." Or at least that's what was going through my head as I went through with restoring the whole backup. Lo and behold, /system was corrupted, I assume, and it aborted restoring it. I reboot my phone only to find out that my phone gets stuck on the SGSIII boot logo. This is where I am now. I would go through with flashing a stock rom onto it to undo everything I've done, but ODIN won't recognize my phone anymore. I can still get into Download and Recovery Mode. All my backups are useless at the moment.
In Short:
I tried to root, unlock the bootloader, and flash CM10 on it
I messed up and ended up restoring a broken backup, md5sums be screwed.
Now ODIN won't recognize my phone and it's stuck at the SGSIII boot screen.
Is there any way to fix this or at least return it back to stock so I can start again?
If there's any other information you need, just ask. I'd be happy to give it. :laugh: This is my first post on these forums, so I'm not sure what information is standard. If you have any idea of what it might be, please drop a comment or something rather than just leaving. I'd like to know that people are actually reading this post.
And on an unrelated note, every time I try to flash with Heimdall, I get an error about there not being a certain .dll file, even though I downloaded the package from Link 2. Am I doing something wrong?
EDIT: I've already tried factory resetting and wiping the cache/dalvik cache. Most of my info is backed up anyway.
Links:
Link 1: http://forum.xda-developers.com/showthread.php?t=2046439
Link 2: http://wiki.cyanogenmod.org/w/Install_CM_for_d2vzw

What happens when you plug your phone into your PC? Have you tried deleting the drivers then reinstalling them either from Samsung or from the Kies program? You really have to try to mess up this phone and it seems like you definitely tried very hard in this regard.
Edit: Idk anything about Heimdall, I use Odin only so I can't help you there.

SlimSnoopOS said:
What happens when you plug your phone into your PC? Have you tried deleting the drivers then reinstalling them either from Samsung or from the Kies program? You really have to try to mess up this phone and it seems like you definitely tried very hard in this regard.
Edit: Idk anything about Heimdall, I use Odin only so I can't help you there.
Click to expand...
Click to collapse
I hadn't noticed before, but my phone doesn't even show a charge screen when plugged in, but that might just be the settings on the phone pre-root. I'm not sure because I left the phone on to see if it was just a time thing. The phone died and I have to recharge it.
After goofing around with the phone while on the charger for a while, I can get a charge screen to show up for a second. The standard "battery with a loading circle" type symbol for this type of error.
I just reinstalled the drivers. I'll let the phone charge for about 10 minutes or so, then test the phone.

dudeman9199 said:
I hadn't noticed before, but my phone doesn't even show a charge screen when plugged in, but that might just be the settings on the phone pre-root. I'm not sure because I left the phone on to see if it was just a time thing. The phone died and I have to recharge it.
After goofing around with the phone while on the charger for a while, I can get a charge screen to show up for a second. The standard "battery with a loading circle" type symbol for this type of error.
I just reinstalled the drivers. I'll let the phone charge for about 10 minutes or so, then test the phone.
Click to expand...
Click to collapse
Well if it died you should leave it on the charger longer than ten minutes if it is charging. If Odin recognizes it, your first step would be to try flashing a stock image.

SlimSnoopOS said:
Well if it died you should leave it on the charger longer than ten minutes if it is charging. If Odin recognizes it, your first step would be to try flashing a stock image.
Click to expand...
Click to collapse
Thanks. It would seem that it now recognizes the phone, from what I can tell. As soon as I get a stock rom, I'll flash it and post an update.

dudeman9199 said:
Thanks. It would seem that it now recognizes the phone, from what I can tell. As soon as I get a stock rom, I'll flash it and post an update.
Click to expand...
Click to collapse
Great! Use Droidstyle's guide or MrRobinson's thread for the proper images. Should be a good starting point.
Sent from my SCH-I535 using xda app-developers app

I just wanted to add that THIS is how you do a first post or any help needed post! Great details and is obvious you researchedyour problem as well.
The errors in cwm are actually normal. I think the corrupt backups are unrelated.
Sent from my SCH-I605 (AKA NOTE 2)

SlimSnoopOS said:
Great! Use Droidstyle's guide or MrRobinson's thread for the proper images. Should be a good starting point.
Sent from my SCH-I535 using xda app-developers app
Click to expand...
Click to collapse
Thanks. I've finally booted up into the setup wizard. I guess from here on I can re-root, unlock the bootloader, and *hopefully* get a working backup and eventually flash CM10.
I guess this means Problem Solved? Again, Thanks.
kintwofan said:
I just wanted to add that THIS is how you do a first post or any help needed post! Great details and is obvious you researchedyour problem as well.
The errors in cwm are actually normal. I think the corrupt backups are unrelated.
Sent from my SCH-I605 (AKA NOTE 2)
Click to expand...
Click to collapse
Thanks. I'm just gonna assume that the problems stemmed from swapping the sd card and leave it at that.

dudeman9199 said:
Thanks. I've finally booted up into the setup wizard. I guess from here on I can re-root, unlock the bootloader, and *hopefully* get a working backup and eventually flash CM10.
I guess this means Problem Solved? Again, Thanks.
Thanks. I'm just gonna assume that the problems stemmed from swapping the sd card and leave it at that.
Click to expand...
Click to collapse
Perfect! Which thread did you end up using btw?
Sent from my SCH-I535 using xda app-developers app

SlimSnoopOS said:
Perfect! Which thread did you end up using btw?
Sent from my SCH-I535 using xda app-developers app
Click to expand...
Click to collapse
I used droidstyle's thread for getting the stock rom.