Database Info

Clockworkmod backup question

Is there a way to verify a backup worked? This morning I was trying to restore a backup and it said the md5sum didn't match. I hadn't done anything different than I ever do. I Just ran the backup in recovery yesterday and tried to restore it today. Thankfully I had an additional backup from the day before that did work but it kind of made me nervous since it really seems you cannot be sure they worked.
I am hoping maybe there is a way I can check the md5sum of a backup somehow but I am really not sure how to go about doing that.

You can try THIS to verify your md5sum. Not sure if it will work, never had the cause to check the md5sum of a backup. Another option would be to switch Recovery to TWRP. Much more stable on the Shift than CWM. Also a lot more options overall .
EDIT:
For a more detailed explanation of CWM you can check out THIS GUIDE

I had the md5 thing happen about a week ago. Since then I've been making 2 backups. Still room for error, but I little less likely. Also started making them in recovery instead of rom manager then rename later.
Sent from my PG06100 using xda premium

jsp254 said:
I had the md5 thing happen about a week ago. Since then I've been making 2 backups. Still room for error, but I little less likely. Also started making them in recovery instead of rom manager then rename later.
Sent from my PG06100 using xda premium
Click to expand...
Click to collapse
Your posts jogged my memory. I THINK when my problem happened I may have actually chosen to do a backup through rom manager but didn't really think anything of it since it boots the phone into recovery anyway. Usually I boot myself into recovery and do the backups myself but I think that time I may not have. I probably will not do that again.

Stopped using RomManager a while back. Used it only for renaming Backups when I used CWM. But have sinced switched to TWRP. Like it much better, and more options. If you want to rename a Backup. Just connect the device as a Disk Drive to your PC. Explore to the TWRP Backup folder, and rename that way.

[Q] Atrix 2 - Wont load and tried everything!

This is my first post so please bear with me. I searched and searched and tried everything and havent been able to do this.
After rooting atrix 2, went to delete some bloatware...think i accidentally deleted something crucial (as most noobs do I am sure ). Now the phone will not boot fully - it gets stuck at the moto emblem in a kind of boot loop. Just going to give you info about what I have done so far:
Once i boot after a hard reset- in recovery mode tried to install stock rom. Did not work. This is because it said E:Signature did not get verified. ALSO pls note that I do not have cwm or any other custom boot program - so I am unable to see any uncheck the e signature option. I tried to find any rom which might have a signature so i can get that and then put the stock on subsequently - no good so far - of the mere 2-3 roms I found all showed the same problem with E-signature.
I tried to see if I could install cwm. I installed sdk tools on my computer - however I dont know how to install cwm without phone being fully on. Nor can I find a file for the Atrix 2 to do it. The ones I found were the bootstrap ones in .apk files which i dont know how to install on bootlooping phone.
Spoke to some android pros - tried the suggestions above they gave me and nothing so far. I think it was android phone portal that I accidentally removed...
Also note that I am in India and my stock rom is the India version NOT the AT&T/Verizon.
Im a bit scared to use the RSDLite application as I am not proficient with the workings of that software and I dont want to cause any more damage.
Is there any rom for atrix 2 that has a valid E:Signature? Is there any way to bypass this on stock bootloader. I repeat I do NOT have clockwork..Only options are to Reboot, Install package from SD, Format and Clear Cache.
PLEASE HELP...as a last draw will take to the service center...this phone is only 1 month old so I dont want to risk losing warranty (

Have you tried flashing an FXZ as in this post:
http://forum.xda-developers.com/showthread.php?t=1396650
Sorry just re-read your post see you are in India and not on AT&T version.

Your best chance is to use RSD Lite to flash the stock Indian ROM. Here is the whole list of known fxz's for the A2. The Indian Retail ROM is "5.5.1-EDEM-27-SEARET."
When you first try to flash, it might error out depending on if you are on the latest update for your firmware. If so, just post the screenshot of the error it gives.

Do you think maybe i can flash it to this at&t firmware and then install cwm and then restore to india stock flash as with cwm i would be able to bypass signature authentication?
Please let me know.
Thanks.

dheerb said:
Do you think maybe i can flash it to this at&t firmware and then install cwm and then restore to india stock flash as with cwm i would be able to bypass signature authentication?
Please let me know.
Thanks.
Click to expand...
Click to collapse
Yes, you can do it that way, but it is rather indirect way of doing it. The easiest thing to do is flash the Indian firmware with RSD Lite.

yes i tried that but for some reason rsd lite does not detect my device (yes i have downloaded all relevant drivers).
And now whats worse :
I used moto-fastboot to flash the system files and i got the dreaded low battery fail. As expected this has caused Flash Mode (S) Flash Failure - is this mean its beyond repair by me? If there is a way please let me know.
As of now i have connected it to the wall charger hoping that by tomorrow morning I should have battery for me to try again (I tried again after a half hr or so of battery charging and it didnt work - gave the same error)...
Worst case Ill take it to the service center - would they be able to repair it does anyone think? Is this something they will do? (I understand warranty might be void)...
Please tell me I'm fretting big time...I cant afford a new phone

Oh and I tried with the Indian rom too but didnt work again coz rsdlite didnt register my phone connected despite drivers being installed.
Tutorial videos were hard to find but atrix 4g and original atrix show the boot mode as RSD protocol boot mode....this is not to be found on my atrix 2 boot mode - only thing is AP Fastboot - maybe its the same I do not know...
Also another question - will my phone battery charge when phone is connected to wall charger while the persistent flash failure Fastboot is showing on screen...
If all fails I really hope the service center can repair this...this is possible right?

http://forum.xda-developers.com/showthread.php?t=892026
this should work I've used it a couple times now
Sent from my MB865 using xda premium

chrisn91 said:
http://forum.xda-developers.com/showthread.php?t=892026
this should work I've used it a couple times now
Sent from my MB865 using xda premium
Click to expand...
Click to collapse
^^ this is your best bet at a fix. Once your battery is high enough, RSD Lite should detect your phone (I'm assuming that that's why it doesn't show up in RSD but it does in fastboot).

alright seems a bit mechanical...probably a last resort...
are you saying the battery will not charge when connected to the wall charger though?
Also if i do it the way the thread says...how long do i keep it connected?
thanks!

dheerb said:
alright seems a bit mechanical...probably a last resort...
are you saying the battery will not charge when connected to the wall charger though?
Also if i do it the way the thread says...how long do i keep it connected?
thanks!
Click to expand...
Click to collapse
I've done it a couple times I usual wait like 10 mins before starting the rsdlite but leave the micro usb and mcgyver method plugged in. As also read so where on here that the batter will charge in recovery mode as well. Never tried that
Sent from my MB865 using xda premium

PHEW
hey guys thanks so much for all your support and help! Ive just managed to get it back up and running...guess the wall charger did charge it just enough (literally just - started with 8% battery )
now will start restoring things one by one... (and happy to do it too after this ordeal)
One last question - is it worth me rooting again? Before this crisis everything was fine after i attained successful root...problem came after i deleted bloatware where I think I stuffed up by deleting phoneportal...
Thanks again...happy days again!

If yo u do root heres a link that coukd help u out http://forum.xda-developers.com/showthread.php?t=1330235
[Reference] List of things that are safe to freeze
Sent from my MB865 using xda premium

dheerb said:
...One last question - is it worth me rooting again? Before this crisis everything was fine after i attained successful root...problem came after i deleted bloatware where I think I stuffed up by deleting phoneportal...
Thanks again...happy days again!
Click to expand...
Click to collapse
Its always best to freeze unwanted apps, rather than deleting. Also, if you re-root, there's several roms that are de-bloated already.
Sent from my MB865 using xda premium

Apex_Strider said:
Its always best to freeze unwanted apps, rather than deleting. Also, if you re-root, there's several roms that are de-bloated already.
Sent from my MB865 using xda premium
Click to expand...
Click to collapse
I agree with apex, just because you can delete it, doesn't mean you should. Be VERY careful when. Deleting system apps. When in doubt, freeze it out!
Sent from my MB865 using xda premium

Fall of Enosis said:
I agree with apex, just because you can delete it, doesn't mean you should. Be VERY careful when. Deleting system apps. When in doubt, freeze it out!
Sent from my MB865 using xda premium
Click to expand...
Click to collapse
IMHO, Titanium Backup is a must have for all rooted users. https://play.google.com/store/apps/details?id=com.keramidas.TitaniumBackup
Sent from my MB865 using xda premium

Apex_Strider said:
IMHO, Titanium Backup is a must have for all rooted users. https://play.google.com/store/apps/details?id=com.keramidas.TitaniumBackup
Sent from my MB865 using xda premium
Click to expand...
Click to collapse
Be vary wary of TIB....
It is best to just freeze anything with something like eazy freezy in market, and backup everything with CWM.
TIB was great, maybe 3 years ago before CWM was the thing. It has not innovated and the things it does can break things a lot... I bought it a long time ago, and I have not liked using it in over 2.5 years now. I stopped loading it last year, when it would give erreranous errors about incorrect permissions, and fail to restore things correctly, and using it to remove and "freeze: things tends to cause more FCs than I care to count.....
There are several on the Atrix2 forum that have seen these same issues, and have even been soft bricked by TIB.

jimbridgman said:
Be vary wary of TIB....
It is best to just freeze anything with something like eazy freezy in market, and backup everything with CWM.
TIB was great, maybe 3 years ago before CWM was the thing. It has not innovated and the things it does can break things a lot... I bought it a long time ago, and I have not liked using it in over 2.5 years now. I stopped loading it last year, when it would give erreranous errors about incorrect permissions, and fail to restore things correctly, and using it to remove and "freeze: things tends to cause more FCs than I care to count.....
There are several on the Atrix2 forum that have seen these same issues, and have even been soft bricked by TIB.
Click to expand...
Click to collapse
I didn't realize there was such issues with TB... I haven't really used it for freezing, but new it held that option to do so. I've used to backup apps so as to not have to re-download my apps each time after flashing new roms. Is there something better for this purpose?
CWM backs up everything, like rom and apps and so forth, right? What about just backing up apps only?
Sent from my MB865 using xda premium

Apex_Strider said:
I didn't realize there was such issues with TB... I haven't really used it for freezing, but new it held that option to do so. I've used to backup apps so as to not have to re-download my apps each time after flashing new roms. Is there something better for this purpose?
CWM backs up everything, like rom and apps and so forth, right? What about just backing up apps only?
Sent from my MB865 using xda premium
Click to expand...
Click to collapse
Backing up and restoring apps can be risky when flashing ROMs. You are best to use the option with the market/play to backup what apps you have installed, then when you install a new ROM, and sign into the market/play, it should download and install all the apps you had before. I have had the best success with this.

jimbridgman said:
Be vary wary of TIB....
It is best to just freeze anything with something like eazy freezy in market, and backup everything with CWM.
TIB was great, maybe 3 years ago before CWM was the thing. It has not innovated and the things it does can break things a lot... I bought it a long time ago, and I have not liked using it in over 2.5 years now. I stopped loading it last year, when it would give erreranous errors about incorrect permissions, and fail to restore things correctly, and using it to remove and "freeze: things tends to cause more FCs than I care to count.....
There are several on the Atrix2 forum that have seen these same issues, and have even been soft bricked by TIB.
Click to expand...
Click to collapse
REALLY? Man, i'm kinda with apex on this one. I have never had any issues with TIB.
Guess the primary reason I like it over the store restore is that it restores all apps. Even the ones not on the store. IE: Cheesecake. It also restores all system settings like text messages, settings, stored passwords. wifi/bluetooth settings. Everything.
However, I trust your wisdom Jim. I will be wary of its usage in the future. Just saying I haven't ran into it... Yet.
Sent from my MB865 using xda premium

Getting an S3 next week, how important is it to backup your IMEI?

I see some topics about it. I plan to unlock and root as soon as I get the phone.
Just how important is it to backup this, and anything else I should backup too?

its pretty important.. nothing can go wrong by backing it up. once you root it back it up just in case so your new phone wont be a $600 paperweight!
When you install CWM do a nandroid backup of stock

THE SKATER DUDE said:
its pretty important.. nothing can go wrong by backing it up. once you root it back it up just in case so your new phone wont be a $600 paperweight!
When you install CWM do a nandroid backup of stock
Click to expand...
Click to collapse
That's good to hear. I figured I'd make stock backup too. Having stock rooted won't mess it up I'd presume? Is there an app that does it too?

I have flashed all the roms available, including CM10 and had no trouble with IMEI. Always good to backup though. There's a fairly simple process in the CM10 OP.

joaquinla1 said:
I have flashed all the roms available, including CM10 and had no trouble with IMEI. Always good to backup though. There's a fairly simple process in the CM10 OP.
Click to expand...
Click to collapse
It's built in I assume?

Recon0212 said:
That's good to hear. I figured I'd make stock backup too. Having stock rooted won't mess it up I'd presume? Is there an app that does it too?
Click to expand...
Click to collapse
once rooted and you have installed clockwork mod recovery or TWRP you can make a back up of your whole phone..this will not mess up anything. You can get these two recoveries by using the ez recovery app on google play....... To make a backup in the recovery it will say backup and restore as one of the main options

THE SKATER DUDE said:
once rooted and you have installed clockwork mod recovery or TWRP you can make a back up of your whole phone..this will not mess up anything. You can get these two recoveries by using the ez recovery app on google play
Click to expand...
Click to collapse
Sorry I don't think I was clear, I know about ROMs cause I do it on my Incredible. What I meant was backing up my IMEI

Recon0212 said:
Sorry I don't think I was clear, I know about ROMs cause I do it on my Incredible. What I meant was backing up my IMEI
Click to expand...
Click to collapse
O my bad you have to be rooted in order to run the operation through a terminal emulator app

If you poke around in development there's one for Mac/Ubuntu (I think Ubuntu anyway) that does root and clockwork recovery from your computer, and that's what I use because it's pretty quick and easy.
If it can ever be important you should make a backup of it though. Since fixing things is always a process, having comprehensive resources for it can trim a lot of time.

Using QPST it only took me like 5 minutes to back mine up. Really simple. Then I put a copy of the file on my HD, on my phone's SD card and one on my Google drive. Now I'm sure I can't lose it. LoL they are small files too. Under 500kb
--Sent from GlaDos baked potato

I’d like to look further into it.

I lost my IMEI and other connection data with a bad flash of a CM10 nightly. I had to do a lot of stuff, including manually typing in my IMEI using QPST and then returning my phone to the Verizon store for them to do some factory-reset style stuff to it before I got connectivity again. (Even though I was bone-stock with a re-locked bootloader they still knew I had rooted and messed with the kernel and other stuff, btw). And its not completely correct, even though I am in my home service area I constantly have the flashing grey triangle that says I am doing international roaming. Pretty weird. So long story short, backup IMEI and everything else BEFORE FLASHING ANYTHING.

Legato Bluesummers said:
Using QPST it only took me like 5 minutes to back mine up. Really simple. Then I put a copy of the file on my HD, on my phone's SD card and one on my Google drive. Now I'm sure I can't lose it. LoL they are small files too. Under 500kb
--Sent from GlaDos baked potato
Click to expand...
Click to collapse
That's good, I'll probably put it on my Skydrive then too.
Is there a high chance of losing it on flashing though? I just plan to flash CM10 really.

Recon0212 said:
That's good, I'll probably put it on my Skydrive then too.
Is there a high chance of losing it on flashing though? I just plan to flash CM10 really.
Click to expand...
Click to collapse
Yes, there's always a chance you'll loose it. Better to be safe, than sorry. It only takes a couple of minutes to backup and it may save you the hassle of an exchange.

I backed up the IMEI using this method ( QPST) http://rootzwiki.com/topic/32397-tutorial-imei-backup-nv-with-qpst-us-variants/ It doesn't say should i reset the modems to mtp-adb?
it doesn't say and i would have posted it there but the guy at the end of the thread seems like he is all pissy if you ask any questions. thanks guys

Check out this thread. http://forum.xda-developers.com/showthread.php?t=1852255
Flash the file in the OP in cwm recovery for an easy backup. NOTE: Your bootloader must be unlocked for it to work.
Sent from my SCH-I535 using xda app-developers app

thanks bro i did that one first but they say do all of them just in case. so i did .

CWM backups show wrong date

Does anyone know why? Its done this since I first rooted and did my first back up.
Sent from my SCH-I535 using xda app-developers app

same here. i think thats just how CWM works.

ddurandSGS3 said:
same here. i think thats just how CWM works.
Click to expand...
Click to collapse
Hmmm. Its only ever done it on my s III. Never did it on my og evo or HTC sensation. Maybe its the version of cwm. Is there an updated one? I have version 6.0.1.2 I know there's a touch version but I heard it was buggy.
Sent from my SCH-I535 using xda app-developers app

There is a bug in the RTC software for this phone. Until that but gets fixed (would have to be by Samsung or VZW) this isnt going to change.

Yeah it sucks but just rename your backups after they are done
Hit me up on Gtalk if u need help @musclehead84

musclehead84 said:
Yeah it sucks but just rename your backups after they are done
Hit me up on Gtalk if u need help @musclehead84
Click to expand...
Click to collapse
I believe if you rename the backup then you will have to remake the MD5 for that backup, which isnt really a big deal. Just wanted to toss that out there.

apacseven said:
I believe if you rename the backup then you will have to remake the MD5 for that backup, which isnt really a big deal. Just wanted to toss that out there.
Click to expand...
Click to collapse
i keep 2 renamed nandroids that i restore regularly and run them without any issues.

apacseven said:
I believe if you rename the backup then you will have to remake the MD5 for that backup, which isnt really a big deal. Just wanted to toss that out there.
Click to expand...
Click to collapse
U can rename them as long as u don't use special characters.
Sent from my SCH-I535 using xda premium

Install rom manager from the market and flash the latest recovery through that. Walla, they're back to normal. Only fixable by Samsung or vzw? Wtf do people get this stuff? This question gets asked every other day and there are STILL people who think its some unsolvable bug.

Imatoasta said:
Install rom manager from the market and flash the latest recovery through that. Walla, they're back to normal. Only fixable by Samsung or vzw? Wtf do people get this stuff? This question gets asked every other day and there are STILL people who think its some unsolvable bug.
Click to expand...
Click to collapse
That's the first I've heard this. I have the latest cwm touch and wrong dates show. Actually I keep seeing people use RM and the recovery isn't flashing right.
Sent from my S3 running Eclipse 2.1

same me
Same me as well,:crying:

I thought that was normal since those numbers are no where near a type of date, I just rename it once booted into ROM.
Sent from my SCH-I535 using XDA Premium App

i suffering same issue too

Imatoasta said:
Install rom manager from the market and flash the latest recovery through that. Walla, they're back to normal. Only fixable by Samsung or vzw? Wtf do people get this stuff? This question gets asked every other day and there are STILL people who think its some unsolvable bug.
Click to expand...
Click to collapse
This is not true. I dl'd my CWM thru RM and my dates are still wrong. Where do u get this stuff?

Imatoasta said:
Install rom manager from the market and flash the latest recovery through that. Walla, they're back to normal. Only fixable by Samsung or vzw? Wtf do people get this stuff? This question gets asked every other day and there are STILL people who think its some unsolvable bug.
Click to expand...
Click to collapse
That's incorrect. The date issue is still there regardless of how it's flashed in. Some people have reported issues with restoring after renaming. Consensus seams to be if you keep the default cwm assigned name and add your own to the end of it without any spaces, any reported issues dissappear.
Boom! Jellybomb biatch!

annoying for sure. I just rename the moment I am done and booted back up.

TWRP date is also wrong but you can rename them anything you want at time backup. :laugh:

The guy meant backup FROM RM, it allows you to rename the backup file before it gets created, then reboots into recovery and creates the backup.
please try to search for your problem before posting... I'm typically the last to complain about that, but geez us...

Seirÿu said:
The guy meant backup FROM RM, it allows you to rename the backup file before it gets created, then reboots into recovery and creates the backup.
please try to search for your problem before posting... I'm typically the last to complain about that, but geez us...
Click to expand...
Click to collapse
TWRP does everything rom manager does except download roms which have been seen to cause bricks. Backups are named before creation also but already booted into recovery. One stop shop. Easier wipe.

prdog1 said:
TWRP does everything rom manager does except download roms which have been seen to cause bricks. Backups are named before creation also but already booted into recovery. One stop shop. Easier wipe.
Click to expand...
Click to collapse
I got to jump on that one of these days to see what all the fuss is about, I'm just loving cwm touch too much! I assume when changing, your existing nandroids will become useless, so would make sense to copy onto your cpu incase they are needed down the road...?
Boom! Jellybomb biatch!

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