Database Info

CWM: A thread of its own

OK, it goes without saying that to do rooting and flashing you need to have at least a basic understanding of the English language, a decent IQ and the ability to follow basic instructions.
However, with the CWM mod that's out there for this phone, there are dangers in trying to use for anything other than flashing. IMO, the problem is that those discussions are getting buried in long threads that were originally meant for other Subjects. I feel that CWM needs to have a thread of its on to benefit EVERYONE, especially the newbies. So I am starting it off with this simple instruction:
DO NOT TRY TO USE A ROM MANAGER AT THIS TIME! THE DEVS WILL LET YOU KNOW WHEN YOU CAN USE IT
ALSO; DO NOT USE CWM TO RESTORE AT THIS TIME YOU WILL BE BRICKED
#2 IF YOU WANT TO GET INTO CWM FROM START-UP TO FLASH A ROM - HOLD DOWN THE VOL UP BUTTON + HOME BUTTON + POWER BUTTON, WHEN YOU SEE THE SAMSUNG LOGO, RELEASE THE POWER BUTTON.
TO END THE CONSTANT QUESTIONS ABOUT THE "GO BACK" MENU OPTION: SCROLL COMPLETELY THROUGH ALL MENU OPTIONS TWICE, THE GO BACK OPEN WILL THEN APPEAR
I ask the devs to post info. here even if it has been posted in one of the threads.
Forum Management FTW!

If one of the devs could throw up the file to flash CWM and the instructions, that might be helfpful as well.

Restoring currently has a bug that bootloops a device.
It should be noted that currently there is no go back option either. To enable this scroll through the menu 3x and select an option, go back will now appear.

boostedjti said:
Restoring currently has a bug that bootloops a device.
It should be noted that currently there is no go back option either. To enable this scroll through the menu 3x and select an option, go back will now appear.
Click to expand...
Click to collapse
So nandroids are not working, Sorry I dont have my Charge yet so I am only trying to get cleaification?

kejar31 said:
So nandroids are not working, Sorry I dont have my Charge yet so I am only trying to get cleaification?
Click to expand...
Click to collapse
AfaIk thats correct. No one has reported a successful restore. People who have tried end up in stock recovery loop. Hopefully someone will come up with a solution for these folks soon.

hoppermi said:
AfaIk thats correct. No one has reported a successful restore. People who have tried end up in stock recovery loop. Hopefully someone will come up with a solution for these folks soon.
Click to expand...
Click to collapse
Huh?? So if you try a recovery it bricks your phone???? or are you still able to get into recovery and reinstall a ROM?
If your are unable to get into recovery can you at least restore and Odin?

kejar31 said:
Huh?? So if you try a recovery it bricks your phone???? or are you still able to get into recovery and reinstall a ROM?
If your are unable to get into recovery can you at least restore and Odin?
Click to expand...
Click to collapse
Not sure an odin restore is helping people.
I have a theory on a way to fix a stock recovery bootloop but that would require a bootlooped device which I'm not willing to do...

boostedjti said:
Restoring currently has a bug that bootloops a device.
It should be noted that currently there is no go back option either. To enable this scroll through the menu 3x and select an option, go back will now appear.
Click to expand...
Click to collapse
I have found pressing the vol up and vol down at the same time enables the "go back" option. It will state that it is enabled.
It will pop up when you select another option first.
Sent from my voodoo Droid Charge ED2

On the Fascinate when you flashed CWM, Stock recovery would come up the first boot, then you would flash an update.zip that took you to CWM and you could flash a compatible kernel and you were on your way no more stock recovery. I don't know if something like this could work to get ppl unlooped or not, just throwing it out there.
And ShotgunSam you might as well add don't restore w/ CWM in your big red warning.

boostedjti said:
Not sure an odin restore is helping people.
I have a theory on a way to fix a stock recovery bootloop but that would require a bootlooped device which I'm not willing to do...
Click to expand...
Click to collapse
Well, I'm already stuck there, if your idea isn't too complex, I can try it out

I have one that was bricked for this reason. If anyone has any ideas I will test them out. I am good with adb shell and have been trying to figure out how to change the bootmode=7 which I think is the sdcard to 6 which I think is the nand. Can't find where the file is in the system because I can't boot. Or a signed update zip that boots Android of the sdcard like the hd2 might work.

stranula said:
Well, I'm already stuck there, if your idea isn't too complex, I can try it out
Click to expand...
Click to collapse
Go to the epic 4g forums and in development you'll find a thread that contains an update.zip that will use cwm 3.0.2.x. adb push that update to your sd card or just transfer it. Flash jts cwm compatible kernel through odin then try applying the update.zip.
Just a theory. If cwm boots, you can then flash a rom and that may work.
hoppermi said:
On the Fascinate when you flashed CWM, Stock recovery would come up the first boot, then you would flash an update.zip that took you to CWM and you could flash a compatible kernel and you were on your way no more stock recovery. I don't know if something like this could work to get ppl unlooped or not, just throwing it out there.
Click to expand...
Click to collapse
That was something I mentioned on irc the other day lol great minds think alike.

Has anyone with bricked phones tried to reach out to Koush?
Sent from my ADR6400L using Tapatalk

kejar31 said:
Has anyone with bricked phones tried to reach out to Koush?
Click to expand...
Click to collapse
Koush has been worse than useless for the Galaxy S.

Well he does have the Charge listed as a supported device on his website.. if its bricking he might help.. so if my phone were bricked I would at least try and start with him
Sent from my ADR6400L using Tapatalk

I tweeted at him and said the problem. No response yet. Ill keep posted. Everyone should tell him
Sent from my SCH-I510 using XDA Premium App

Koush is looking into it.
Sent from my SCH-I510 using XDA Premium App

Thanks OP for this tread. I agree 100%.
1) I think some "bootloopers" have had success entering download mode when their SD card was pulled.
2) Have any brickers/bootloopers tried the JIG method to force download mode?
Google JIG:
http://forum.xda-developers.com/showthread.php?t=819551
http://www.youtube.com/watch?v=iSaeaAcJHqw
http://www.youtube.com/watch?v=GjDkShT-65Y
http://samsungjigs.blogspot.com/
http://shop.ebay.com/skisky1/m.html
3) Also, I *think* someone who had bootloops was able to clear his data/cache folder somehow/someway. And I *think* he was either able to stop the bootloops or at least get into download mode. But maybe I am thinking of something else here.

Would empty cache/dbdata/movinand.bin files be helpful for Odin? We could rip them out of one of the Fascinate Odin packages to be included with a "Restore to stock" Odin package. Based on the error I've seen of someone that tried to restore, it looks like /data is getting FUBARd and that's causing the problem, but it's not something I want to personally test since my phone is working.

Anyone having issues after a restore, please see if you have adb shell access. If so, please grab a logcat and post it here.
Sent from my SCH-I500 using XDA App

[Q] Noob needs a little help

Ok so I just got me a New samsung showcase. It came with 2.2 installed build number sch-i500.ee25. Ok so i find out about rooting and all this so i start researching all about it. Here is where i am. I rooted with SuperOneClick. Worked fine. I installed ROM manager to get the clockworkmod but it did not work so I used Odin to install clockworkmod. That worked fine. So at this point I decided i need to backup the stock ROM. I try this using ROM manager but no go. it reboots into clockworkmod and gives me the sd card not mounted stuff. So I read and read and read but i can't seam to find a solution to this problem. I know there other people that have had this problem. I have read through the step by step guides and i really see nothing on this. Anyone have any type of solution.

Running on stock 2.2 rom manager doesnt work. You will need to go into cwm by turning off phone, holding power,vol up and down at same time. after samsung blinks 2nd time let go of buttons and you will boot into recovery.

Thank you. I thought I tried that before but I guess i did something wrong. Worked that time. Now if my memory is correct from reading that will not back up two things. The kernel and something else. How do I back up the kernel? Or am I just not thinking correctly cause I have not had enough sleep.

Samsung Galaxy S with Cellular South
I had to have Kies Mini open and running on my computer to root my phone

First, Welcome!
Second, Download and familiarize yourself with a program called Odin. This phone is hard to brick. From nearly every situation you can flash back to stock with Odin.
Third, Showcase files are not common. Send me a PM and ill give you my email address. I can better help over email.

studdyhalllooser said:
This phone is hard to brick. From nearly every situation you can flash back to stock with Odin.
Click to expand...
Click to collapse
Not true; that's what we call a false sense of security.

add144 said:
Not true; that's what we call a false sense of security.
Click to expand...
Click to collapse
that is true. ive seen phones get restored that have been flashed with roms for other phones and wont even get past the samsung logo. he said nearly, I'm sure you can come up with some weird far out situation but don't try and scare the newbies off this early.
Sent from my MIUI SCH-i500

sageDieu said:
don't try and scare the newbies off this early.
Click to expand...
Click to collapse
What will scare newbies off is when they start flashing crazy **** for another phone in the Phone box in ODIN or something and can't fix it by just ODIN'ing like you guys are suggesting.

add144 said:
What will scare newbies off is when they start flashing crazy **** for another phone in the Phone box in ODIN or something and can't fix it by just ODIN'ing like you guys are suggesting.
Click to expand...
Click to collapse
It's ok he's the only one still here so he'll have to help them.
Sent from my SCH-I500 using XDA App

You say that but the fact that you said it means I'm not the only one.

Ooooohhhh someone's getting technicallllllllll

add144 said:
Ooooohhhh someone's getting technicallllllllll
Click to expand...
Click to collapse
dang right
Sent from my MIUI SCH-i500

Same phone
I have the exact same phone as you. I just rooted my phone for the first time yesterday and I am having trouble installing CWM. Can you explain to me how you used Odin to flash CWM. And after you flash CWM, is it possible to revert back to stock recovery? If so how?

How to Unroot/Return Stock

So just like that gentlemen, my SGT 7 Plus seems to be giving me trouble. It randomly shut off today and then wouldn't boot up again until I tried about 7 or 8 times. The tablet itself is great and I had no complaints with the build quality. I'm guessing it's just a lemon; will get it replaced.
Just wondering if I can ask if there's some way to unroot the device. I'm guessing I can just replace the stock recovery by using the back-up that was made during the CWM flash.

I think you could also just do a restore via kies.
Sent from my GT-P6210 using Tapatalk

Thanks! I'll just wait for some more suggestions before I go ahead. I've never used KIES before to be honest. All my previous devices have been HTC. I bought a Galaxy S II and never looked back.
How exactly do you restore via KIES? Is there something I should know about at the risk of soft-bricking it?

somebody9 said:
So just like that gentlemen, my SGT 7 Plus seems to be giving me trouble. It randomly shut off today and then wouldn't boot up again until I tried about 7 or 8 times. The tablet itself is great and I had no complaints with the build quality. I'm guessing it's just a lemon; will get it replaced.
Just wondering if I can ask if there's some way to unroot the device. I'm guessing I can just replace the stock recovery by using the back-up that was made during the CWM flash.
Click to expand...
Click to collapse
use odin3 to restore one of the stock images that are posted in the development section. there are instructions there. I've done it at least 10 times - works fine

Thanks! Gary suggested I do the same. Good to know it works.

is there any visual mark like yellow or blue triangle on the boot screen (like other samsung device do) on GT7+ that saying our device has been flashed?
I heard samsung has a flash counter, and Im afraid if I flash even if it's stock firmware (if the counter truly exist and visually appear) the warranty will be void...

Could somebody confirm this? I'd like to avoid complications with returning the device..

somebody9 said:
Could somebody confirm this? I'd like to avoid complications with returning the device..
Click to expand...
Click to collapse
Why would there be complications? Its the stock rom, any flashing is STILL the stock rom. if you boot up odin it will say no to custom binary download and also samsung official. You should be good.

otamctech said:
use odin3 to restore one of the stock images that are posted in the development section. there are instructions there. I've done it at least 10 times - works fine
Why would there be complications? Its the stock rom, any flashing is STILL the stock rom. if you boot up odin it will say no to custom binary download and also samsung official. You should be good.
Click to expand...
Click to collapse
so if I flash stock fw there would be no flag/counter and I would be good?
how about you bro?, is there any visible mark on boot after u flash stock firmware?

dewadewi said:
so if I flash stock fw there would be no flag/counter and I would be good?
how about you bro?, is there any visible mark on boot after u flash stock firmware?
Click to expand...
Click to collapse
Nothing that I can see, but I am no expert. I don't know what would be indicated when and if we get custom roms, but the stock ROM flashing does not appear to be flagging anything. Just as a fair business practice I don't see Samsung denying service/warranty for loading the firmware THEY provide. Custom, yes. Stock, no.

Galaxy Mini Disaster!!

Hi All,
Iv had a disaster with me 3 month old Galaxy Mini, I got the latest Android magazine which talked about installing custom ROM's so I downloaded ROM Manager which the recommended, and tried to perform a ROM Backup firstly it asked for my phone model which it didn't say anything about, anyway I accidently hit the wrong phone model, it then asked for a backup name which, I OK'd it, the phone should reboot into recovery mode and perform the backup, mine shutdown and now I cant turn it on. It was plugged in when I did all this, and I left it plugged in when it shutdown. I dont even get the charging icon when its off.
have I bricked my phone?
PLEASE HELP?

Oh boy, looks like you got a problem...
You'll get more help here: http://forum.xda-developers.com/forumdisplay.php?f=1311
In all probability, you will have to go to samsung service centre, and they will replace the processor...

bugs78 said:
Hi All,
Iv had a disaster with me 3 month old Galaxy Mini, I got the latest Android magazine which talked about installing custom ROM's so I downloaded ROM Manager which the recommended, and tried to perform a ROM Backup firstly it asked for my phone model which it didn't say anything about, anyway I accidently hit the wrong phone model, it then asked for a backup name which, I OK'd it, the phone should reboot into recovery mode and perform the backup, mine shutdown and now I cant turn it on. It was plugged in when I did all this, and I left it plugged in when it shutdown. I dont even get the charging icon when its off.
have I bricked my phone?
PLEASE HELP?
Click to expand...
Click to collapse
A lot of reading is neede when trying to flash custom roms on any phone.
I think you better had done everything by yourself in recovery (step by step), so no mistake can be made that way.
Maybe you can get some help in Galaxy Mini section.
I guess you cant even power it in download mode?

Alpha120 said:
A lot of reading is neede when trying to flash custom roms on any phone.
I think you better had done everything by yourself in recovery (step by step), so no mistake can be made that way.
Maybe you can get some help in Galaxy Mini section.
I guess you cant even power it in download mode?
Click to expand...
Click to collapse
I honestly don't think he was rooted, or had a custom recovery.

You must flash the tass.ops file via odin ( computer program ) and then download and install ( again via odin ) the stock or a custom rom.
WARNING: To successfully unbrick your galaxy mini, you must have the odin for samsung galaxy mini GT-S5570. Odin for other devices will probably destroy your device at all.
If you want links and more instructions, you can sent me a pm.
If I helped you, don't forget to press the Thanks button.
Sent from my GT-S5570 using xda premium

Thanks, so will samsung need to replace the processor as stated earlier, or can this be repaired by a decent phone repair shop?
Sgmaster said:
You must flash the tass.ops file via odin ( computer program ) and then download and install ( again via odin ) the stock or a custom rom.
WARNING: To successfully unbrick your galaxy mini, you must have the odin for samsung galaxy mini GT-S5570. Odin for other devices will probably destroy your device at all.
If you want links and more instructions, you can sent me a pm.
If I helped you, don't forget to press the Thanks button.
Sent from my GT-S5570 using xda premium
Click to expand...
Click to collapse

Have you even read Sgmaster's post??
You need to flash a stock rom using ODIN, no need to take it to any service if it boots into download mode.

Alpha120 said:
Have you even read Sgmaster's post??
You need to flash a stock rom using ODIN, no need to take it to any service if it boots into download mode.
Click to expand...
Click to collapse
Sgmaster said:
You must flash the tass.ops file via odin ( computer program ) and then download and install ( again via odin ) the stock or a custom rom.
Click to expand...
Click to collapse
I don't know how is he going to flash tass.ops with odin, and then separately flash a stock rom...
Last I checked, you couldn't flash an odin partition script by itself, since that script is for odin's use on the phone and not for the phone itself...
Is it different for mini?
Typed using a small touchscreen

I think Sgmaster meant to load .ops file and then, flash the stock rom.
For SGS+ is ariesve.ops, I flashed with odin a few times...

Right this. First load the tass.ops file via odin and then flash a rom throught odin or clockworkmod recovery mode.
If I helped be sure to press THANKS button.
Sent from my GT-S5570 using xda premium.

Always read the threads first if not a vid is even better

*sigh*
This is why articles shouldn't say, "IT'S SO EASY, ANYONE CAN DO IT!"
No, it's not. It's easy to f*ck up and brick your phone is what it is. Don't even bother joining XDA if you don't have the patience to read. Nowadays all we get are people who join after messing up their phones, begging us to perform some over-the-internet sorcery to fix it. We're not magicians. We're people. We don't exist to serve you. We have lives.
This isn't pointed directly at the OP.

Product F(RED) said:
*sigh*
This is why articles shouldn't say, "IT'S SO EASY, ANYONE CAN DO IT!"
No, it's not. It's easy to f*ck up and brick your phone is what it is. Don't even bother joining XDA if you don't have the patience to read. Nowadays all we get are people who join after messing up their phones, begging us to perform some over-the-internet sorcery to fix it. We're not magicians. We're people. We don't exist to serve you. We have lives.
This isn't pointed directly at the OP.
Click to expand...
Click to collapse
Thats why no matter what, Im still on Stock Froyo.

I'm not saying don't root. It's not hard to root, but it is easy to brick your phone. By brick, I mean permanently. As long as you have recovery mode or download mode, you're good. But my point is read, read, read before you even download a ROM.

I did successfully root my fine no problems, and read about ROM's but, think I should have read more before attempting.
I`m guilty of getting misty eyed over the thought of something new and flashy not seen before.
I have been on here a while reading, not posting and i think i`ll check out here before attempting again.
anyway I wimped out and sent it back to Samsung to be repaired under its warranty, I know I could probably fix it with the help of you guys, but if I dont need to have the hassle.
But, if I was to recover myself I know you have said use odin I have downloaded it and had a look. Would I load the software then attempt to turn it on with the Home, down volume, and on buttons it should then boot into recovery mode. Is that correct?
Thanks All for your time

[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.