yashsingh1/xdaforums huggingface dataset:
[Verizon Samsung Galaxy S III] SlimSnoopOS:
Either method produces the same result.
[Verizon Samsung Galaxy S III] nojak:
Awesome, thanks!
[Verizon Samsung Galaxy S III] Wildarc:
I just the stock rom back on my phone because i qualify for versions edge program but my flash counter is triggered. I don't have the money at the moment to purchase a reset app. Does anyone know of a way for free to reset the counter?
[Verizon Samsung Galaxy S III] ThePagel:
Its been a long time and I never wanted to use that app but I think the store app is for donation. There should be the "free" link somewhere On the interwebs.
[Verizon Samsung Galaxy S III] Rakunvar:
Hmm, so just kinda breezed through everything without issue, havent installed a Rom in quite awhile. Now that I went with the stock 4.3 so I can do a warranty replacement my download screen seems weird, and I want to make sure I didnt miss something...

Custom Binary is:No

Current Binary: Official

Status: Official

Qualcomm Secureboot: Enable

Now these were new.

Warranty Bit:0

Bootloader RP SWREV: 1

^ Are these two meaning anything in particular? Looking around the forums atm as well, but figured I should ask. I cannot recall my previous versions of anything or I would've posted them Thanks in advance
[Verizon Samsung Galaxy S III] wrigbone:
I'm going to be doing this in the next month or so to sell my phone. Probably when/if they push the Kitkat update. I used Triangle Away and it looks like it worked...

Counter: 0

Binary: Official

Device: SCH-I535

System: Official

However it still says Device status "Modified" under About Phone. Will this change back to default after flashing the stock rooted image?

Also @ SlimSnoopOS "Either method produces the same result." from your reply to the above post asking if he should use the 4.3 stock or an earlier version and OTA up...which is the preferred method, or what would you do? Are the OTAs like installing an upgrade as opposed to a fresh install of the full OS???

Thanks!
[Verizon Samsung Galaxy S III] Aphole:
I keep getting a message that reads SIM CARD PERMANENTLY BLOCKED... a nice user on cyanogenmod told me I have abad ESN...

Now what? wheres a guide to reset esn? and offtopic... can someone spill the beans of one of the roms that leave carrier credentials like Bodafone so I can get Data?

http://xdaforums.com/showthread.php?p=53503862

original ignored thread ^ :(
[Verizon Samsung Galaxy S III] nickjensz:
I'm currently on a rooted AOSP 4.4 Rom, but would like to get back to stock 4.4.2 . Does any know of the easiest way to get back to stock 4.4.2?
[Verizon Samsung Galaxy S III] rhcreed:
Looking to upgrade my phone.. Using cm11.. Rooted and unlocked.. Do they really check the phones they take back for upgrades?
[Verizon Samsung Galaxy S III] MisfitsTimmy:
I'm on Hyperdrive ROM that is 4.1.2. I want to get back to total stock. Can I just install a stock ROM using Odin, or do I need to do something else. I want to be able to get OTA's again.
[Verizon Samsung Galaxy S III] ShapesBlue:
Yes you could indeed go back to stock. You would have to unroot to take the OTAs, I'll be honest though I highly advise against it as your limited to only a few roms and you'll permanently lock your bootloader

Sent from my Nexus 5
[Verizon Samsung Galaxy S III] ChiefIlliniwek5:
Does this method still apply for people on running CM11 based on the 4.4.2 bootloader? Could I just flash the stock 4.4.2 image via odin and everything will go back to stock?
[Verizon Samsung Galaxy S III] ShapesBlue:
Per the thread title it's from 2012 so I'm leaning highly towards no this will not work for the newest firmware

Sent from my Nexus 5
[Verizon Samsung Galaxy S III] sam008:
Guys

To use my phone on pageplus, Ihe phone had to be forced to 3g. Does this process basically undo that as well?

Thanks
[Verizon Samsung Galaxy S III] Joshatdot:
I want to Odin factory full wipe my SCH-i535. It came with 4.4.2 NE1. I found a FW from Samsung-Updates [VZW-I535VRUDNE1-20140626142723.zip], but the links were not working. I googled the filename and found it. But Samsung-Updates does not have MD5/SHA1 hash checksums, so I don't know if what I downloaded is 100% legit.

I also found one here on XDA [ALL_VZW_I535VRUDNE1_I535VZWDNE1_1542239_REV09_user_low_ship.tar.md5.7z], I don't remember what post/thread it was on, but it also doesn't have a hash checksum.
[Verizon Samsung Galaxy S III] fr8cture:
Quick question if you have a backup of your stock rom cant you go back to that recovery and then use ez unlock to lock your bootloader?
[Verizon Samsung Galaxy S III] fr8cture:
can someone please answer?
[Verizon Samsung Galaxy S III] Brian Gove:
I'm not sure what you're getting at. You have a nandroid of your stock ROM and you want to know if EZ Unlock can unlock or re-lock the bootloader? You have to have your phone be rooted to use EZ-Unlock so if you're nandroid is 100% stock(without root) then you can't do that.
[Verizon Samsung Galaxy S III] fr8cture:
Well its a backup with root but if i restore to that then lock the bootloader wouldn't that remove root?
[Verizon Samsung Galaxy S III] Brian Gove:
nope. Root and unlocking the bootloader have nothing to do with each other except the fact you need root in order unlock the bootloader.
[Verizon Samsung Galaxy S III] fr8cture:
Alright thanks, got my everything back to factory so i can upgrade to a 32gb Gs3
[Verizon Samsung Galaxy S III] TehPersian:
Thank you for this post. Nice to know it's here if I need it :D
[Verizon Samsung Galaxy S III] techgov8:
I dont understand what your trying to ask

Tap'n
[Verizon Samsung Galaxy S III] Brian Gove:
Updated/corrected the OP. It seems flashing the regular stock image via Odin doesn't re-lock the bootloader. You do have to do it manually.
[Verizon Samsung Galaxy S III] fr8cture:
Yeah I used ez unlock then flashed
[Verizon Samsung Galaxy S III] shojus:
GREAT.... I just returned a refurb S3 to verizon cause I read that the odin package relocks the bootloader and now I don't know what they are going to say....? I followed the guide to a T but I did not relock using the playstore app cause I thought the odin method re-locked it.... :(

How will they be able to tell if it's unlocked cause I never had any indication on my boot up screen showing that it was unlocked like some have...? I just went into stock recovery as explained and reset settings and rebooted... I am def paranoid now... Verizon can def be dicks about it and say they are going to charge me for the phone... Hopefully I get lucky...
[Verizon Samsung Galaxy S III] Brian Gove:
If it was a refurb just play stupid and say the owner before must have done it. Act like you have no idea what a boot loader is.

The way to tell without examining the boot image is just the first Samsung splash screen goes by in a split second instead of two or three seconds. That's how I figured it out cuz I went to return mine yesterday and noticed that.
[Verizon Samsung Galaxy S III] techgov8:
If its unlocked it goes quick and if its locked it take a few seconds, right?

Tap'n
[Verizon Samsung Galaxy S III] shojus:
Well that is weird cause I am in the process of returning my 3rd F'in S3 because their refurbs are JUNK and the one I returned a few days ago was not re-locked and the one I am about to return is fully re-locked using the "updated" updated method.... :) But the Samsung splash scteen still only stays on for a couple seconds and I KNOW I relocked it before flashing the images through Odin...? Weird... Hope it all works out! :fingers-crossed::fingers-crossed: Thanks for the quick response!

I definitely would like to know how I can "examine" the boot image myself just to be on the safe side...?
[Verizon Samsung Galaxy S III] Brian Gove:
Correct.

@shojus: When it is unlocked it literally just flashes on and off the screen before going to the boot animation. When locked you can see it for a couple/three or so seconds before the boot animation.
[Verizon Samsung Galaxy S III] techgov8:
So what does the custom mean then? I've seen people saying they were stock getting this

Tap'n
[Verizon Samsung Galaxy S III] Brian Gove:
I haven't gotten a solid answer one way or another. I had thought the custom came from flashing a custom recovery but others have said they got it when running stock. Then again some peoples definition of stock is different. You can be stock rooted with a custom recovery but still call yourself stock in the ROM sense.
[Verizon Samsung Galaxy S III] techgov8:
That's what I am stock rooted with cwm and stock rom and I have the custom. On my other s3 I would get the custom then after a few reboots it wouldn't be there and then sometimes it would pop up again. It was weird

Tap'n
[Verizon Samsung Galaxy S III] droidstyle:
if you odin the stock kernel, then the stock rom, the bootloader is locked...i have performed this method a few times.

---------- Post added at 01:31 AM ---------- Previous post was at 01:29 AM ----------

my device had the custom unlock screen bone stock, no mods. thats how i know section 6 of my guide locks bootloader because the custom unlock screen comes back, which actually means the bl is locked.

---------- Post added at 01:36 AM ---------- Previous post was at 01:31 AM ----------

did u odin the stock kernel first?
[Verizon Samsung Galaxy S III] Brian Gove:
It doesn't lock it. The tell tale sign is the fact that the Samsung splash screen goes by in a split second before going to the 'Samsung galaxy Siii' screen. I did it myself following this exact guide and it didn't work until I re locked the boot loader
[Verizon Samsung Galaxy S III] droidstyle:
did you flash the stock kernel first? like i said, every time i went back to stock using my method, the normal splash screen returned.
[Verizon Samsung Galaxy S III] techgov8:
I thought it wet back too but I had to flash to stock. Reroot then use ez-unlock to lock the bootloader then reflash stock rom. If you relocl the bootloader before you unroot and flash stock you should be all good

Tap'n
[Verizon Samsung Galaxy S III] droidstyle:
why not just lock bootloader with app then flash back to stock...long as the device does not reboot then it shouldnt be a issue. when i get time im going to investigate this.
[Verizon Samsung Galaxy S III] shojus:
Yes I did Odin the stock Kernel first and then Odined the stock rom and then rebooted into stock recovery and did a factory reset...? It sounds like I am Okay...? But people hear are telling conflicting info so I don't know what to believe is the 100% correct method to "strip her down" ;)

---------- Post added at 01:46 PM ---------- Previous post was at 01:43 PM ----------

That's exactly what I did this time around but have yet to send this one back....Still seeing the Samsung logo for a tad bit too long as far as I'm concerned... In fact, My fully rooted and unlocked phone displays the image quicker...?

---------- Post added at 01:48 PM ---------- Previous post was at 01:46 PM ----------

GREAT!! Thank you!!

EDIT: From my findings the Samsung boot logo that flashes across the screen REAL quick when first powered on ,if it's not unlocked, is false because I have a fully unlocked and rooted (with custom recovery & rom) and it is doing what a bone stock Galaxy S3 would do but if I flash back using the method on this thread it stays on a bit longer even though I did it two different ways...? This one has me MEGA stumped!?? Crazy Crazy....
[Verizon Samsung Galaxy S III] Breezer23:
Have any of you returned your phone for the IMEI issue? I reset mine finally, apparently the backup I had made in QPST had failed because it wasn't working. I'm now always in roaming, which is ridiculous. If you have returned it for that reason, what was your excuse?
[Verizon Samsung Galaxy S III] techgov8:
You should be alright then
[Verizon Samsung Galaxy S III] shojus:
I have NEVER lost my IMEI and I have flashed the hell out of these phones... I do ALWAYS keep a backup though with a few different methods just to be on the safe side. Here is my story... I bought a BRAND NEW 16gb S3 at a Verizon dealer (off contract to keep my Unlimited data) and everything was golden for the first two weeks and then I could not connect to gps and had random reboots when it was completely stock(non-rooted)... The dealer would not let me exchange so I had to go the Verizon route which I have already received two defective units from them(with scratches) and I bought NEW so I do not want scratches and the home button would stick as well.... So I am getting pretty fed up with the refurbs they are sending me that are scratched and defective so idk what my next step is here but just a lil paranoid about them charging me for modifications to the phones... Since no one REALLY knows the 100% answer I am just playing the waiting game but I LOVE the phone just had some bad luck so far... :(

"SHOULD", is the key word here.... Once there is a 100% PROVEN method than we just don't know...? Cause like I said, the S3 I have now with the sticking home button is fully rooted with custom recovery and rom w/ overclocked kernel and unlocked and it shows NO signs of it being unlocked and the Samsung boot logo goes just as quick as a NEW out of the box phone does. Answer that one...? Just trying different methods myself to try and determine what is actually going on here... Thanks for everybody's input though!! :good:
[Verizon Samsung Galaxy S III] droidstyle:
ok guys been flashing with odin and its a fact that odin does not relock the bootloader...how I did it the last time is besides me?? I just tried three times and the bootloader is unlocked.

However this did work:

open up the ez-unlock app relocked bootloader

power off and boot into odin mode

flash stock rom via PDA in odin

profit! you are now ready to return the device

I verified this by locking bootloader via the ez app and rebooted...Instantly got the triangle of death. To get out of it I just flashed the stock kernel via odin, then rebooted. Device had the Long samsung splash screen and then triple booted back into android. I then unlocked bootloader flashed latest imo lean kernel and went right back where I started. I apologize for the initial misinformation folks!!! For some reason I thought that I had the bootloader locked after a previous odin session. The good thing is I highly doubt verizon will check for a insecure aboot.img for those who returned it unlocked.
[Verizon Samsung Galaxy S III] Brian Gove:
OK I wasn't sure if locking it while on a ROM that requires it to be unlocked would f things up or not. It is fine as long as you don't let the ROM boot up again?
[Verizon Samsung Galaxy S III] droidstyle:
yes and even if you try to boot you will get the verizon triangle of death..which is no big deal as flashing the stock kernel or stock rom will bring it right back to life.
[Verizon Samsung Galaxy S III] annoyingduck:
Droidstyle, any chance of getting you to repost a new thread without all the clutter on your revised method, step by step? Would be helpful for alot of people. This thread may still confuse people that haven't fully followed it.
[Verizon Samsung Galaxy S III] Brian Gove:
I'll be updating the op when I get to a computer. Its Friday night and I'm out so I can't do it right now. The op is correct anyways, it just has one/two more step(s) than is necessary.
[Verizon Samsung Galaxy S III] droidstyle:
basically all you do is lock bootloader with app then follow section 6 of my guide...i updated that section and im sure brian will update his op.
[Verizon Samsung Galaxy S III] Brian Gove:
OP is updated. thank you for taking the plunge and testing out the re-locking while on a ROM... I was too scared to f up my phone lol.
[Verizon Samsung Galaxy S III] droidstyle:
no problem. i felt that i owed it to you guys for spreading the misinformation in the first place...:o
[Verizon Samsung Galaxy S III] Brian Gove:
lol, it comes with the territory... We all are kinda making the "new frontier" here. It's all a learn as you go, I have used Odin to go back to root66 quite a few times and thought the bootloader was re-locked so I unlocked it each time.... I just wasn't paying attention too much.

Like I said, the only way I figured out Odin didn't re-lock the bootloader was when I went to return my phone to Verizon myself. That's when I payed attention to every detail. Like microscopically lol...
[Verizon Samsung Galaxy S III] shojus:
Thanks guys for all of your help and troubleshooting.... I know this is a NEW thing so I can't and would never blame anyone for misguiding me as I am the one who CHOSE to take the risks... But I am glad that there is now a PROVEN method to get this done! :highfive: :good:
[Verizon Samsung Galaxy S III] FMinMI:
Odin vs CWM?

Hi,

I just read all the postings and am somewhat confused. I just bought a used Siii and the person rooted and unlocked it (I can run programs that require superuser access, like Titanium Pro). It also has CWM installed (6.0.0.6). It appears to have the stock VZN ROM (IMM76D.I535VRALG7).

If I follow the steps listed at the start of this thread, will that also remove CWM? Or is CWM an alternative for Odin? I don't seem to under the difference between the two.

What I want to do is restore my phone to out-of-the-box stock in the event I need to return it to VZN and to also be able to get OTA downloads when JB is released.

Thanks, and sorry if I missed something -- lots of threads to read and I am buggie-eyed....

Frank

Michigan
[Verizon Samsung Galaxy S III] techgov8:
If you use odin to go back to stock firmware in the op that will work fine. CWM is a backup tool that replaces your stock recovery image. Once you go back to stock this will be changed back to stock as well. Once you do all this you'll be able to take OTA updates but if you plan on rooting to use programs like titanium backup then its not a good idea to take OTA updates anyways.

Tap'n
[Verizon Samsung Galaxy S III] FMinMI:
Hi Tap'n, and thanks for the reply. And OK on just having to run Odin -- I will find it online and see if there is a readme file for how to use. I assume it is relatively easy? I am coming from a Galaxy Nexus and we had a real neat program (Wug's Nexus Root Toolkit) which made the entire process click and go from stock to unlocked and back again. It was pretty slick; a no brainer...

I realize that once I go back to stock 'n lock that I will not be able to use such programs as TB Pro. But I am sure that once the official JB is released, it will only be a short time before someone figures out a way to root and unlock it, and at that time I will follow the procedure to get my superuser programs to work again. However I am not going to do that UNTIL VZN starts pushing out JB or if I have a mechanical issue with my new phone. I just want to be ready.

Cheers,

Frank

Michigan
[Verizon Samsung Galaxy S III] techgov8:
Read the guide and it will tell you exactly how to use odin. Its very simple. Just put your phone into download mode then open odin plug your phone into the computer and open up pda and flash away. Make sure to download ez-unlock before you flash back and lock your bootloader. Flashing back to stock does NOT lock your bootloader so you'll want to do that so you'll be able to take the OTA update

Tap'n
[Verizon Samsung Galaxy S III] FMinMI:
Hey Tap'n,

Thanks. I found and watched a few videos to see what I should see, but that just added to my question pool. If I may:

1) Even though it appears I am running the stock ROM, I should download a known unrooted 'original' for ODIN (I found HOME_I535VRALF2_I535VZWALF2_618049_REV09_user_low_ship.tar via the link), correct?

2) Do I have to worry about downloading a PIT file? I was not clear on where to find it and one of the videos said it was needed in ODIN to make sure the ROM gets installed properly.

All the other stuff seems straight forward (run ez-unlock, check count/run triangle away if needed, flash stock, wipe...). And this will get rid of all files / programs, including CWM.

Thanks again.

Frank

Michigan
[Verizon Samsung Galaxy S III] techgov8:
1. Yes you will go to that version and then once you get that build flashed to you phone then your phone should most likely find the update to the current G7 build once its up and running. If not just go to settings> about device> software update.

2. I didn't download a PIT file just ODIN and I've flashed a few times with no problem.

And yea just the few other things you said you understand and you'll be all good to go.

Tap'n
[Verizon Samsung Galaxy S III] Brian Gove:
You realize that it's probably going to be the new year before we see Jelly Bean on our devices correct? Verizon is ALWAYS the latecomer as far as OTA pushes like that. Personally I would take the time to play with a few of the ROMs that are already out there and get comfortable to screwing with the phone.

And FYI, tech covered it but, make sure that EVERY time you use Odin for whatever to have the PDA option ticked and load the files through that option. NEVER use any of the other parts.
[Verizon Samsung Galaxy S III] FMinMI:
I am going to think positive about VZNs JB's release date and hope that it will be here within a month but if not, I might just do that. Really, I am not that disappointed in what I have now. I did have JB on my Nexus for a few weeks and indeed it was better than ICS but the only really major feature was the ability to ask it questions - something that the Siii already has via Samsung's interface. A lot of the crap that most people hate I have edited out (e.g. the WIFI pop up, removing the startup and shutdown music, etc) or froze (with TB Pro) so I am now getting good battery life and minimal annoyances.

And OK on the PDA check. By default is that selected? Or does ODIN warn you if you pick something else? I would hope the programmer would do that if it is critical...

Thanks.

Frank

Michigan
[Verizon Samsung Galaxy S III] Brian Gove:
By default no option is checked and there's no warning or anything. Odin is used for a lot of other devices, its not a GS3 specific program.
[Verizon Samsung Galaxy S III] FMinMI:
OK. Thanks again.
[Verizon Samsung Galaxy S III] javier21:
thanks..
[Verizon Samsung Galaxy S III] dangerousx:
deneme

deneme
[Verizon Samsung Galaxy S III] Brian Gove:
What does that mean in English. Cuz I googled it and could only come up with two possible answers. One is "test" and the other is "*****". And I hope you're not saying ***** lol.
[Verizon Samsung Galaxy S III] cwalter9:
Worked like a champ!

My power button fell off my phone in my pocket. Not sure how but had to return me phone to the store and followed your steps to get back to stock. Worked great.
[Verizon Samsung Galaxy S III] devanb:
Thanks and a question

Just wanted to say thanks. It's my first post so I don't have a thanks button yet.

Also, when reading the posts, there is an abbreviation I'm not familiar with: "op" It's too short a term to do a search on it. What does it mean?

Thanks again,

Devan
[Verizon Samsung Galaxy S III] Brian Gove:
It refers to either the original post or poster of the thread depending on the context it's used in.
[Verizon Samsung Galaxy S III] droidstyle:
click on the gs3 guide link in my sig and refer to section 8 Android Glossary. Op stands for original post(er).
[Verizon Samsung Galaxy S III] kevinchen1102:
A big big thank you.this really helps.
[Verizon Samsung Galaxy S III] makavelli302:
I think my phones completely bricked I just flashed to omega jb v 27.2 without doing the prerequisite flash prior...any suggestions?
[Verizon Samsung Galaxy S III] Brian Gove:
I think you may have the wrong variant here. Are you on Verizon??? If so you shouldn't have flashed Omega because there is no Omega for Verizon and that will brick your phone, possibly permanently.
[Verizon Samsung Galaxy S III] thrgk:
OK so I'm on a ROM and want to get the ota g7 update. Do I just relock. Then boot into download mode start down and flash the stock image with root. Or do I need without root to get the ota g7 update?