Database Info

My flash counter appears to stay at zero

I have flashed and reflashed roms probably over 15 times since i got my phone. I have read that booting in download mode, you can see a small white number that says your flash count. When I go there I see no number anywhere at all. It says my binary is official and system status as modified. I have downloaded triangle away and when I go into that app, it also says my flash counter is 0 and my binary is official. I have the samsung custom unlock picture boot screen. Is this normal or should I have a flash count? If its normal what triggers the flash count? Also just to make sure, if I ever need my phone to be totally stock and remove the boot unlock screen and modified status I just have to follow the guide to return to stock which involves download mode and a windows pc, right? ( Cant remember the name of the windows app you use for that)

sfetaz said:
I have flashed and reflashed roms probably over 15 times since i got my phone. I have read that booting in download mode, you can see a small white number that says your flash count. When I go there I see no number anywhere at all. It says my binary is official and system status as modified. I have downloaded triangle away and when I go into that app, it also says my flash counter is 0 and my binary is official. I have the samsung custom unlock picture boot screen. Is this normal or should I have a flash count? If its normal what triggers the flash count? Also just to make sure, if I ever need my phone to be totally stock and remove the boot unlock screen and modified status I just have to follow the guide to return to stock which involves download mode and a windows pc, right? ( Cant remember the name of the windows app you use for that)
Click to expand...
Click to collapse
the only way the flash counter is tripped if you flash custom software in odin.

Ok thanks for the info. Is there any reason for a non developer to flash custom software in Odin, like some kind of non stock release or tool?

sfetaz said:
Ok thanks for the info. Is there any reason for a non developer to flash custom software in Odin, like some kind of non stock release or tool?
Click to expand...
Click to collapse
We cant until the booloader is unlocked.

I don't know but I really don't mind if my flash counter gets to be 10000. Isn't this just for Samsung to gage how much development is being done? Why else would they care if we flash ROMs?
Sent from my SCH-I535 using xda premium

They also probably use it to see if people have tried to hide rooting the phone if you send it in.
Sent from my SCH-I535

Locked out by Verizon after cm10 flash

thanky you to anyone ahead of time for reading this post. I really could use some help.
I have a Verizon galaxy s3 which I rooted 3 weeks ago when i got it. I know it was rooted as i had super user permissions, and deleted many bloatware apps. I waited until cm10 came out to flash a new rom and after doing so last night my phone now boots up with this message "System software not authorized by verizon wireless has been found on your phone. Please turn off your phone and go to the nearest Verizon Wireless store for help."
So I tried to boot it in to recovery mode but when I did, the same message came up, only this time it said "recovery booting" in small blue writing in the top left corner.
I followed the directions to a T from a page entitled "Jelly Bean for Verizon Galaxy S3: Unofficial CyanogenMod 10 (CM10) Nightlies Available for Flashing!
From what I understand, the bootloader was somehow never unlocked by kexec. because I cant get in to recovery mode, I was wondering if there was a way to disable the bootlock by installing kexec via odin.
Also, whether it was a good idea or not, I re flashed the stock rom via oden last, which was successful but, nothing has changed still the same response all boot ups. Download boot obviously works though as I have been able to mess with it in odin.
any insight on this would be graciously appreciated.

Lembro said:
thanky you to anyone ahead of time for reading this post. I really could use some help.
I have a Verizon galaxy s3 which I rooted 3 weeks ago when i got it. I know it was rooted as i had super user permissions, and deleted many bloatware apps. I waited until cm10 came out to flash a new rom and after doing so last night my phone now boots up with this message "System software not authorized by verizon wireless has been found on your phone. Please turn off your phone and go to the nearest Verizon Wireless store for help."
So I tried to boot it in to recovery mode but when I did, the same message came up, only this time it said "recovery booting" in small blue writing in the top left corner.
I followed the directions to a T from a page entitled "Jelly Bean for Verizon Galaxy S3: Unofficial CyanogenMod 10 (CM10) Nightlies Available for Flashing!
From what I understand, the bootloader was somehow never unlocked by kexec. because I cant get in to recovery mode, I was wondering if there was a way to disable the bootlock by installing kexec via odin.
Also, whether it was a good idea or not, I re flashed the stock rom via oden last, which was successful but, nothing has changed still the same response all boot ups. Download boot obviously works though as I have been able to mess with it in odin.
any insight on this would be graciously appreciated.
Click to expand...
Click to collapse
Okay, first, If you did follow the directions for that thread, i'm sure it would of worked, I'm pretty sure you are missing something here and i'm pretty sure from reading your post that I think you didn't unlock your bootloader. kexec was a workaround for the locked bootloader, it doesn't unlock it. I would follow droidstyle's guide to unlocking the bootloader, http://forum.xda-developers.com/showpost.php?p=28530409&postcount=2 after you unlocked it, i'm pretty sure you forgot that step. But the issue when flashing back to stock via odin and still showing up its a custom rom, I don't know why that would happen but I suggest reading section 2 of droidstyle's guide on flashing back to stock. http://forum.xda-developers.com/showpost.php?p=28530394&postcount=1
So first, I suggest to return to stock, then root, then unlock bootloader, and then install the rom of your choice, preferably without kexec, if you don't want the triple reboot.

RyanW114 said:
Okay, first, If you did follow the directions for that thread, i'm sure it would of worked, I'm pretty sure you are missing something here and i'm pretty sure from reading your post that I think you didn't unlock your bootloader. kexec was a workaround for the locked bootloader, it doesn't unlock it. I would follow droidstyle's guide to unlocking the bootloader, http://forum.xda-developers.com/showpost.php?p=28530409&postcount=2 after you unlocked it, i'm pretty sure you forgot that step. But the issue when flashing back to stock via odin and still showing up its a custom rom, I don't know why that would happen but I suggest reading section 2 of droidstyle's guide on flashing back to stock. http://forum.xda-developers.com/showpost.php?p=28530394&postcount=1
So first, I suggest to return to stock, then root, then unlock bootloader, and then install the rom of your choice, preferably without kexec, if you don't want the triple reboot.
Click to expand...
Click to collapse
Agreed! Op, do more reading and less flashing before you end up with a 600.00 paperweight!

Like he says above you have not unlocked your bootloader . Restore nandroid or recover to stock. Then unlock your bootloader and try again
Sent from my SCH-I535 using xda premium

Get rid of the Verizon screen of death
I got the same error msg after flashing a nightly of d2hacker's unofficial cm10, after I had flashed a few nightly's before of the same ROM w/ no problems. I had to
1. Flash a stock bloated unrooted ROM via odin (lemme know if you need a link to one)
2.boot into droid recovery and do a factory reset, and wipe the cache partition also.
If you don't do step 2 you end up w/ a permanent verizon 4G LTE rainbow boot screen :silly:
I haven't re-rooted yet but I'll be trying the official cm10 now that it's up.

MDMoore313 said:
I got the same error msg after flashing a nightly of d2hacker's unofficial cm10, after I had flashed a few nightly's before of the same ROM w/ no problems. I had to
1. Flash a stock bloated unrooted ROM via odin (lemme know if you need a link to one)
2.boot into droid recovery and do a factory reset, and wipe the cache partition also.
If you don't do step 2 you end up w/ a permanent verizon 4G LTE rainbow boot screen :silly:
I haven't re-rooted yet but I'll be trying the official cm10 now that it's up.
Click to expand...
Click to collapse
Refer to my last post

droidstyle said:
Refer to my last post
Click to expand...
Click to collapse
Note that even when I flashed back to stock, my initial boot screen still had the unlocked lock, w/ "Custom" under it, suggesting my bootloader is unlocked

MDMoore313 said:
Note that even when I flashed back to stock, my initial boot screen still had the unlocked lock, w/ "Custom" under it, suggesting my bootloader is unlocked
Click to expand...
Click to collapse
Incorrect. It actually means the opposite. The only way to tell if your bootloader is unlocked is to flash a custom rom/kernel and boot up. Please people, do some reading before you turn your phone into a paperweight. That unlocked lock/custom means you're running or were running custom software and it's been detected as such. One possible culprit is your "custom" recovery. If your bootloader is unlocked, you will not have that problem.

MDMoore313 said:
Note that even when I flashed back to stock, my initial boot screen still had the unlocked lock, w/ "Custom" under it, suggesting my bootloader is unlocked
Click to expand...
Click to collapse
refer to post #3 and read this link
http://forum.xda-developers.com/showpost.php?p=30479625&postcount=13

Zalithian said:
Incorrect. It actually means the opposite. The only way to tell if your bootloader is unlocked is to flash a custom rom/kernel and boot up. Please people, do some reading before you turn your phone into a paperweight. That unlocked lock/custom means you're running or were running custom software and it's been detected as such. One possible culprit is your "custom" recovery. If your bootloader is unlocked, you will not have that problem.
Click to expand...
Click to collapse
Thanks for clearing that up, Where did you find this info? I'm coming from a Droid incredible, so I never had to worry about such things....
EDIT: I just saw Droidstyle's post @ http://forum.xda-developers.com/showpost.php?p=30479625&postcount=13, makes a little sense, but why all of a sudden Verizon's screen of death is odd, if it was already detecting custom s/w to begin with. I used kexec also as a workaround, but this was back when there was no way to unlock the gs3 bootloader.
Yeah absolutely I follow the steps here http://forum.xda-developers.com/showpost.php?p=28530394&postcount=1

MDMoore313 said:
Thanks for clearing that up, Where did you find this info? I'm coming from a Droid incredible, so I never had to worry about such things....
EDIT: I just saw Droidstyle's post @ http://forum.xda-developers.com/showpost.php?p=30479625&postcount=13, makes a little sense, but why all of a sudden Verizon's screen of death is odd, if it was already detecting custom s/w to begin with. I used kexec also as a workaround, but this was back when there was no way to unlock the gs3 bootloader.
Yeah absolutely I follow the steps here http://forum.xda-developers.com/showpost.php?p=28530394&postcount=1
Click to expand...
Click to collapse
I think it has to do with the "degree" of customization. IE a custom ROM or Kernel will get you the verizon screen of death for sure if you're not unlocked. The custom/unlock icon seems more for minor things like a custom recovery, possibly different firmware or tweaking specific settings.

Zalithian said:
I think it has to do with the "degree" of customization. IE a custom ROM or Kernel will get you the verizon screen of death for sure if you're not unlocked. The custom/unlock icon seems more for minor things like a custom recovery, possibly different firmware or tweaking specific settings.
Click to expand...
Click to collapse
That makes more sense, as the nightlys progress and more modifications are being made, overnight the "switch is flipped" so to speak, and if you're not running a custom rom,

MDMoore313 said:
If you don't do step 2 you end up w/ a permanent verizon 4G LTE rainbow boot screen :silly:
Click to expand...
Click to collapse
Could he Odin back to stock through download mode though? Or will the locked bootloader block download mode and recovery mode too when it detects tampering?

MDMoore313 said:
Thanks for clearing that up, Where did you find this info? I'm coming from a Droid incredible, so I never had to worry about such things....
EDIT: I just saw Droidstyle's post @ http://forum.xda-developers.com/showpost.php?p=30479625&postcount=13, makes a little sense, but why all of a sudden Verizon's screen of death is odd, if it was already detecting custom s/w to begin with. I used kexec also as a workaround, but this was back when there was no way to unlock the gs3 bootloader.
Yeah absolutely I follow the steps here http://forum.xda-developers.com/showpost.php?p=28530394&postcount=1
Click to expand...
Click to collapse
The secure aboot.img only checks 3 of the 5 system images on boot. Since we can flash a custom recovery to the recovery partition, the secure aboot img lets it ride, but knows it there....hence why you see the custom lock screen, but device still boots. Kexec allowed the bootloader aka secure aboot.img to see the stock kernel(boot.img) and pass signature checks, then side loads the custom kernel. Thats why there was 3 reboots...now that the bootloader is unlocked, we ditch kexec because unsecure aboot is unlocked and not checking signatures.
However, if you flash a kernel thats non kexec and the bootloader is locked, you will get the verizon screen of death since the secure aboot.img is checking signatures. So never lock the bootloader unless your on stock rom/kernel or using kexec.

Deleted

Jesus. All of these people who don't read up on things before they flash something astounds me.

Lol, the exact same thing happen to me as Op, I was unlock (ezrecovery app) and rooted(casual-revision131) but when I flash unofficial CM10 KANG I was lock out by Verizon message.Thanks to DroidStyle awesome GUIDE i just Odin back to stock along with kernel.Thank you to all the cool people here at xda who help and evolve Android:thumbup:
Ezrecovery app must not have work properly even tho it said unlock, so I use Adam casual R131 flash Unsecure Aboot too.
Sent from my SCH-I535 using xda premium

EvoSideHustlAZ said:
Lol, the exact same thing happen to me as Op, I was unlock (ezrecovery app) and rooted(casual-revision131) but when I flash unofficial CM10 KANG I was lock out by Verizon message.Thanks to DroidStyle awesome GUIDE i just Odin back to stock along with kernel.Thank you to all the cool people here at xda who help and evolve Android:thumbup:
Ezrecovery app must not have work properly even tho it said unlock, so I use Adam casual R131 flash Unsecure Aboot too.
Sent from my SCH-I535 using xda premium
Click to expand...
Click to collapse
ezrecovery to unlock? What?

MDMoore313 said:
Note that even when I flashed back to stock, my initial boot screen still had the unlocked lock, w/ "Custom" under it, suggesting my bootloader is unlocked
Click to expand...
Click to collapse
No, that just means that it normally has detected some changed files. If you WERE unlocked you would never see that icon.
TAPPED in on my (now unlocked bootloader) Verizon S3

strung said:
Could he Odin back to stock through download mode though? Or will the locked bootloader block download mode and recovery mode too when it detects tampering?
Click to expand...
Click to collapse
Well, step 1 is going Odin back to stock, but if a cache wipe and factory reset aren't done (like in Droidstyle's guide), then it will never completely boot, at least that's what I experienced after my phone sat at that screen for 10+ minutes. It doesn't run the user setup again.

[Q] Yellow triangle of death?

Got the yellow triangle with " unauthorized software found on your device. Return to authorized Verizon dealer." I was trying to return this to stock and the directions on Odin said the bootloader had to be locked. I took the EZunlock and locked it back then all hell broke loose. Any ideas?

ergon said:
Got the yellow triangle with " unauthorized software found on your device. Return to authorized Verizon dealer." I was trying to return this to stock and the directions on Odin said the bootloader had to be locked. I took the EZunlock and locked it back then all hell broke loose. Any ideas?
Click to expand...
Click to collapse
where did u read the bootloader had to be locked? all u need to do is odin back to stock, root, unlock bootloader.

All you need to do is download Odin, and and whatever tar file you want, boot phone into download (volume down, home, power), select yes when it asks are you sure, open Odin, select the tar file and start. Easy schmeasy
Sent from my SCH-I535 using xda app-developers app

ergon said:
Got the yellow triangle with " unauthorized software found on your device. Return to authorized Verizon dealer." I was trying to return this to stock and the directions on Odin said the bootloader had to be locked. I took the EZunlock and locked it back then all hell broke loose. Any ideas?
Click to expand...
Click to collapse
You rebooted your phone after locking the bootloader. You shouldn't have done that. Your issue isn't unfixable tho, not by any means. IIRC VRALF2 I'm pretty sure is the only stock image that doesn't re-lock the bootloader(I haven't tested all of them). If you choose VRALG1 that will re-lock the bootloader for you when you flash it, it did for me the other day when I started over.
Just boot into download mode and flash the G1 thru Odin then do a factory wipe and you should be fine. I'm 99% sure you didn't trip the flash counter doing this, someone else chime in on this please?
And make sure you use PDA mode when you use Odin and don't unplug your phone from it until it says finished(even if it says removed, let it continue rebooting and doing its thing before unplugging. The Start and Cancel buttons should 'come back to life' when it's ok)

This might be the source the OP was referring to:
http://forum.xda-developers.com/showthread.php?t=1867253&highlight=odin+to+stock
Although it clearly says to NOT reboot after re-locking your bootloader, it does say that the first step is to lock it before flashing to stock via Odin. Further down in the thread he says he'll remove it from the guide, but I don't think flashing stock via Odin locks the BL so if youre trying to return it to Verizon I would lock it first.

nghtrain88 said:
This might be the source the OP was referring to:
http://forum.xda-developers.com/showthread.php?t=1867253&highlight=odin+to+stock
Although it clearly says to NOT reboot after re-locking your bootloader, it does say that the first step is to lock it before flashing to stock via Odin. Further down in the thread he says he'll remove it from the guide, but I don't think flashing stock via Odin locks the BL so if youre trying to return it to Verizon I would lock it first.
Click to expand...
Click to collapse
Certain stock images do. I've had g1 lock and I've read that he will to.
Don't get me wrong, locking it yourself prior to flashing thru Odin is a good thing to do just to make sure. It's easier than having to re-root just to lock it then flash all over again.

Brian Gove said:
Certain stock images do. I've had g1 lock and I've read that he will to.
Don't get me wrong, locking it yourself prior to flashing thru Odin is a good thing to do just to make sure. It's easier than having to re-root just to lock it then flash all over again.
Click to expand...
Click to collapse
the only stock rom i have found that locks the bootloader is vralhd... are you sure g1 locked your bootloader because i thought we had this conversation already lol? unless your returning the device, why would you even want to lock it back up?

droidstyle said:
the only stock rom i have found that locks the bootloader is vralhd... are you sure g1 locked your bootloader because i thought we had this conversation already lol? unless your returning the device, why would you even want to lock it back up?
Click to expand...
Click to collapse
Yeah, I meant HD, not HE.
We did, but that was when I flashed F2. F2 doesn't lock it, but a week or so ago I had to flash back to stock to start over, used G1 and it re-locked my bootloader on me.
One of these days when I'm bored I'll sit down and try them all just to double check too.

cvbcbcmv said:
Don't over think it. This is simply happening because the bootloader is locked and your trying to run a custom rom. Just restore to stock and you're fine.
Sent from my SCH-I535 using Tapatalk 2
Click to expand...
Click to collapse
I am having the same issue but when I go to restore back to stock Odin says it has completed 100% but when the phone reboots I get the triangle again. Please help.

i get this very same problem with with yellow triangle when i try to flash a rom it happend to me 2 times so i had to odin back any ideas why it happens when i try to flash a rom

Bootloader is locked
Sent from my SCH-I535 using xda app-developers app

Verizon note 2 will not go into download just yellow triangle
Okay bye hope someone can help me I rooted my galaxy note 2 by Verizon with framaroot and didn't realize the boot loader was locked and try to download ROM manager and it locked my phone up all I got was a yellow triangle said that they did not recognize a program then I did Adam's way of returning to stock with casual will not read it so then I found the root66_vzw..... same as stock but rooted and unlock boot loader and I flashed it and the pit file that went with it using Odin. It said pass when everything was done it upload bar on the phone I seen it on the screen and when it went to reset then it come back to the same Verizon yellow triangle and now I can't get it to going to download mode or do anything at all except for when I plug in the cable to my computer the yellow triangle come on. Can someone help?? Please I really we'd love to have my phone back! I would appreciate it very much thank you sincerely

worknman69 said:
Okay bye hope someone can help me I rooted my galaxy note 2 by Verizon with framaroot and didn't realize the boot loader was locked and try to download ROM manager and it locked my phone up all I got was a yellow triangle said that they did not recognize a program then I did Adam's way of returning to stock with casual will not read it so then I found the root66_vzw..... same as stock but rooted and unlock boot loader and I flashed it and the pit file that went with it using Odin. It said pass when everything was done it upload bar on the phone I seen it on the screen and when it went to reset then it come back to the same Verizon yellow triangle and now I can't get it to going to download mode or do anything at all except for when I plug in the cable to my computer the yellow triangle come on. Can someone help?? Please I really we'd love to have my phone back! I would appreciate it very much thank you sincerely
Click to expand...
Click to collapse
We don't have a Note 2 go to the Note 2 forums to get help.

[Q] I can only boot to Odin

Okay - I pulled a real stupid move today and need some help.. I'm somewhat of a flashing noob.
I installed AOKP 4.2 the other day and was having issues, so I decided to try a Synergy Rom. I use Clockword Mod Recovery to do this. When going in to flash Synergy I noticed the recovery wasn't accessing the SD like it usually does. It was giving me some error code about not being able to read external SD (I dont even have one in the phone I only use internal storage). So eventually I found the synergy file on the internal storage and flashed it. So I flashed it and was having all sorts of issues like no data, FC's etc and went back into recovery to flash my backup of the AOKP 4.2 ROM.
Here's my stupid part - I was in a rush at work this morning and wiped data / cache and got side tracked. Came back and thought I had flashed the new rom and hit restart phone in the recovery. So now I have nothing installed on the phone and the only thing I can get it to do is boot into the Download screen in Odin.
If this helps, the screen in Odin says:
Odin Mode
Product Name: SCH-I535
Custom Binary Download: Yes (2 counts)
Current Binary: Custom
System Status: Official
Qualcomm Secureboot: Enable
I have downloaded Odin to my computer and plugged it and tried to flash this .tar file and get a new recovery this way: http://forum.xda-developers.com/showthread.php?t=1695238 and had no luck as it errors out in Odin. When I connect the phone to Odin I get 0:[COM5] with a yellow colored background towards the top. I still tried to follow the above link's steps and it just errors out.
I'm at wits end and have no idea what to do now. If anyone has any idea, I would REALLY appreciate help. I have been searching for hours and haven't come up with anything that can really replicate my complete issue. I can chat via Gchat if thats easier or whatever, I just really need to get this fixed!
Thanks

Why are you trying to flash something intended for the international GSIII on your Verizon GSIII?
Had to state that cuz it is a terrible way to go about fixing your phone. Flash the rooted VRBKL3 tar in mrRobinson's thread in the Verizon GSIII dev section and then unlock your bootloader using EZ Unlock v1.2. If you didn't successfully flash anything for the i93000 then you should be fine in a few mins.
Edit: that thread you linked to even says what models it works for in the third line of the OP! lol

SlimSnoopOS said:
Why are you trying to flash something intended for the international GSIII on your Verizon GSIII?
Had to state that cuz it is a terrible way to go about fixing your phone. Flash the rooted VRBKL3 tar in mrRobinson's thread in the Verizon GSIII dev section and then unlock your bootloader using EZ Unlock v1.2. If you didn't successfully flash anything for the i93000 then you should be fine in a few mins.
Edit: that thread you linked to even says what models it works for in the third line of the OP! lol
Click to expand...
Click to collapse
Good call - god I'm an idiot....
So when you say flash the file you listed above, I assume your talking about through Odin since I cannot access recovery.
And no, nothing successfully flashed from the i9300 link.

Steve182 said:
Good call - god I'm an idiot....
So when you say flash the file you listed above, I assume your talking about through Odin since I cannot access recovery.
And no, nothing successfully flashed from the i9300 link.
Click to expand...
Click to collapse
Yes sir, flash it via Odin. There are two rooted tars per image: wipe and no wipe. It's all detailed in mrRobinson's thread. You're in an easily recoverable situation. Just make sure to unlock your bootloader using EZ Unlock v1.2 and install a custom recovery if need be.

You are a SAVIOR. Just got it to work, thank you so much.

Steve182 said:
You are a SAVIOR. Just got it to work, thank you so much.
Click to expand...
Click to collapse
My pleasure, I troll the q/a section just to help people!
Sent from my SCH-I535 using xda app-developers app

[Q] Was rooted - took OTA - hanging at white Verizon logo screen

I was rooted and made the mistake of accepting the latest OTA update, which I assume was the new and devious 4.3. The update process seemed to work fine, but on reboot, phone is now freezing at the white Verizon logo screen.
My boot sequence looks like this: "SAMSUNG ([lock pic] Custom)" -> "SAMSUNG GALAXY S III" on black -> Swirly SAMSUNG logo on black -> Verizon animation on white -> HANG at indefinitely repeating few-frame loop animation of shining Verizon logo on white background.
I can get to Download mode - it looks like this:
ODIN MODE
PRODUCT NAME: SCH-I535
CUSTOM BINARY DOWNLOAD: Yes (2 counts)
CURRENT BINARY: Custom
SYSTEM STATUS: Custom
QUALCOMM SECUREBOOT: ENABLE
*NO* mention of Warranty Bit.
Does this mean I am still on 4.1.2 and not dreaded 4.3 Knox? I don't want to screw up and accidentally brick this thing.
Unfortunately I have crappy notes from my original rooting, so I don't know if I had a simple root or custom ROM or custom bootloader or what. I know I have CF-Auto-Root-d2vzw-d2vzw-schi535.tar.md5, VRBMB1_Bootchain.tar.md5, and VRALEC.bootchain.tar.md5 in my work folder, and I was only rooting so I could use SGS3 Easy UMS so I likely did whatever method was needed for that.
How can I get back to functional? Stock or custom, I don't care, but with all the bricking dangers I'm reading about after this new OTA update I just want to proceed extra carefully. Also I'd really like to not have to wipe the phone with a factory reset or anything like that.
Thanks for your help!

scrowdid said:
I was rooted and made the mistake of accepting the latest OTA update, which I assume was the new and devious 4.3. The update process seemed to work fine, but on reboot, phone is now freezing at the white Verizon logo screen.
My boot sequence looks like this: "SAMSUNG ([lock pic] Custom)" -> "SAMSUNG GALAXY S III" on black -> Swirly SAMSUNG logo on black -> Verizon animation on white -> HANG at indefinitely repeating few-frame loop animation of shining Verizon logo on white background.
I can get to Download mode - it looks like this:
ODIN MODE
PRODUCT NAME: SCH-I535
CUSTOM BINARY DOWNLOAD: Yes (2 counts)
CURRENT BINARY: Custom
SYSTEM STATUS: Custom
QUALCOMM SECUREBOOT: ENABLE
*NO* mention of Warranty Bit.
Does this mean I am still on 4.1.2 and not dreaded 4.3 Knox? I don't want to screw up and accidentally brick this thing.
Unfortunately I have crappy notes from my original rooting, so I don't know if I had a simple root or custom ROM or custom bootloader or what. I know I have CF-Auto-Root-d2vzw-d2vzw-schi535.tar.md5, VRBMB1_Bootchain.tar.md5, and VRALEC.bootchain.tar.md5 in my work folder, and I was only rooting so I could use SGS3 Easy UMS so I likely did whatever method was needed for that.
How can I get back to functional? Stock or custom, I don't care, but with all the bricking dangers I'm reading about after this new OTA update I just want to proceed extra carefully. Also I'd really like to not have to wipe the phone with a factory reset or anything like that.
Thanks for your help!
Click to expand...
Click to collapse
You got lucky. For some reason your boot chain didn't flash so it's still unlockable.
You need to flash this file in Odin:
http://www.androidfilehost.com/?fid=23134718111254196
Using section 5 of this guide:
http://forum.xda-developers.com/showthread.php?t=1762709
Then root and unlock with casual:
http://forum.xda-developers.com/showthread.php?t=2332825
Then download ez unlock 1.2 and verify it's unlocked.
Then you're good to go again. Install a custom rom and never accept an Ota again.
As far as wiping your phone goes, you can't really do much about that, this is pretty much a last resort.
Sent from my SCH-I535 using Tapatalk 2

It's a nice write up Badusername..:good:
I just want to add that if you want to keep stock rooted, just make sure you disabled OTA. Like Badusername mentioned if you decided to flash custom rom then you don't have to worry about OTA.

If that's everything in download mode, then you are still on 4.1.2. If you want to try retaining your /sdcard data, then you could try Odin flashing the no-wipe VRBMB1 image.
If you would like to start clean and wipe away /sdcard, then Odin flash this VRBMF1 4.1.2 stock image. You would need to root and unlock in both cases. DO NOT accept the 4.3 OTA in either case.
Edit: ninja'd lmao...badly

Thanks! I am operational again with the No-Wipe flash. Whew!
Unfortunately, it looks like I lost all my text messages though. That was one of the main things I had been hoping to preserve, to keep a record of some conversations. Unless there's something I'm missing and they might still be lurking somewhere?
My photos survived and it looks like apart from a few settings it's mostly unwiped. Cool! Glad I didn't ruin it. Now I can try a custom 4.3 or something else if I want, but for now I'm just glad to have it working again.

This happened to me after flashing VZW-I535VRUCML1-20131220083128 instentionally to return back to stock.
after flashing with odin in PDA mode, the samsung 'custom' screen came on then the loop on the white logo.

blueblur said:
This happened to me after flashing VZW-I535VRUCML1-20131220083128 instentionally to return back to stock.
after flashing with odin in PDA mode, the samsung 'custom' screen came on then the loop on the white logo.
Click to expand...
Click to collapse
Did you boot into recovery and do a factory reset?
Sent from my SCH-I535 using Tapatalk 4

SlimSnoopOS said:
Did you boot into recovery and do a factory reset?
Sent from my SCH-I535 using Tapatalk 4
Click to expand...
Click to collapse
When? Before flashing stock? No. After? No, but if I can get into recovery, I will.
edit:::
went into recovery after flashing odin image, that did the trick. thank you.
still showing 'custom' when starting up

blueblur said:
When? Before flashing stock? No. After? No, but if I can get into recovery, I will.
edit:::
went into recovery after flashing odin image, that did the trick. thank you.
still showing 'custom' when starting up
Click to expand...
Click to collapse
No problem. Idk why custom would be there unless you tried flashing something pre-4.3 in Odin beforehand? Odin flashing the VRUCML1 tar would wipe everything else off the phone in terms of rom and root. It doesn't affect anything unless you plan on doing a warranty replacement.

SlimSnoopOS said:
No problem. Idk why custom would be there unless you tried flashing something pre-4.3 in Odin beforehand? Odin flashing the VRUCML1 tar would wipe everything else off the phone in terms of rom and root. It doesn't affect anything unless you plan on doing a warranty replacement.
Click to expand...
Click to collapse
I was trading it in to verizon for the note 3. i'm good to go now. thanks for your help!

scrowdid said:
Thanks! I am operational again with the No-Wipe flash. Whew!
Unfortunately, it looks like I lost all my text messages though. That was one of the main things I had been hoping to preserve, to keep a record of some conversations. Unless there's something I'm missing and they might still be lurking somewhere?
My photos survived and it looks like apart from a few settings it's mostly unwiped. Cool! Glad I didn't ruin it. Now I can try a custom 4.3 or something else if I want, but for now I'm just glad to have it working again.
Click to expand...
Click to collapse
Just a suggestion. I use an app in the play store called sms backup plus. It backs up your texts to your email.
https://play.google.com/store/apps/details?id=com.zegoggles.smssync
Sent from my SCH-I535 using Xparent ICS Tapatalk 2