Just got my S3 from ATT last week which came with ICS. ATT won't OTA upgrade to JB, so I am stuck with Kies. Problem is that Kies crashes every time I try and upgrade the phone. Can I flash teh stock rom using ODIN and is this wise? (will it increase the flash counter?)
-J
miatawnt2b said:
Can I flash teh stock rom using ODIN
Click to expand...
Click to collapse
Yes; see here for the completely stock images.
miatawnt2b said:
is this wise? (will it increase the flash counter?)
Click to expand...
Click to collapse
I do not believe the flash counter will be tripped if you are using a stock image (even a rooted stock image).
smelenchuk said:
Yes; see here for the completely stock images.
I do not believe the flash counter will be tripped if you are using a stock image (even a rooted stock image).
Click to expand...
Click to collapse
You are correct, sir. Flashing official stock, or even properly root injected stock packages, will not increase your flash counter.
If you can reset your flash counter, why would it matter?
Just to say you have never did it
Related
Ok im confused heck about this flashing stuff. I have a S2 I rooted, and flashed... using zerg oneclick.. didnt flash my counter.... and I flashed tons of times
How come on this phone It will ding my flash counter? Isn't there some way to not ? Also I read a thread
http://forum.xda-developers.com/showpost.php?p=35165945&postcount=1610
I just need to understand..
So what trips the flash counter? Every fash trips the counter?
I need my warrenty so I need make sure whatever I do I don't flash the counter... beside that thread about are there any other roms that won't tip my counter? BTW im on ICS still im about get JB but im holding off to see if being on ICS means I can flash with out tripping my counter someone explain this in noobie for me
Hate to tell you, but you are in the Att Galaxy S3 forum.
xxsicknessxx said:
Ok im confused heck about this flashing stuff. I have a S2 I rooted, and flashed... using zerg oneclick.. didnt flash my counter.... and I flashed tons of times
How come on this phone It will ding my flash counter? Isn't there some way to not ? Also I read a thread
http://forum.xda-developers.com/showpost.php?p=35165945&postcount=1610
I just need to understand
Click to expand...
Click to collapse
I have NEVER used 1-touch. Follow the instructions you found in the link you provided, and you'll be just fine.
Edit: as long as you're on the ATT GSIII
Sent from my SGH-I747 using xda app-developers app
I have a s2 rooted but I own a S3
Look im on ICS right now from the store (just got my phone) I want to root it and install a custom rom.... now my question is
Because I don't have JB yet I won't flash my counter right? Question is I can easly choose to flash stock firm ware again later on and reinstall the offical JB rom right? The one from the KIES and samsung,..
So once again... Im on ICS offical.... I want a custom ICS rom.... im ok ? no flash counter? I choose to go back to stock and go forward with JB im still ok no flash counter?
Alright.... but if I flash a JB ROM It will flash right? and it keeps flashing the counter every time I flash
Im a bad type try answer my question if you can please.
I am a person who may need his warrenty some day
xxsicknessxx said:
Because I don't have JB yet I won't flash my counter right?
Click to expand...
Click to collapse
You will trip the flash counter if you use Odin to flash something other than a stock (untouched or properly rooted) image.
xxsicknessxx said:
Question is I can easly choose to flash stock firm ware again later on and reinstall the offical JB rom right? The one from the KIES and samsung,..
Click to expand...
Click to collapse
Yes - see here for completely stock images you can use for that, or here for pre-rooted stock images.
xxsicknessxx said:
So once again... Im on ICS offical.... I want a custom ICS rom.... im ok ? no flash counter? I choose to go back to stock and go forward with JB im still ok no flash counter?
Click to expand...
Click to collapse
Well, to reach the point of having a custom ROM image without having tripped the flash counter, you'll need to go through the root process listed in the second of those links I indicated above so that you can install a custom recovery through which you can install those ROM images.
xxsicknessxx said:
Alright.... but if I flash a JB ROM It will flash right? and it keeps flashing the counter every time I flash
Click to expand...
Click to collapse
Just remember - if you're using Odin and you don't want to trip the flash counter, don't flash anything other than stock images. You should be okay then.
Also, keep in mind there is an app called Triangle Away which works for the GS3. Triangle Away can completely reset the flash counter.
http://www.xda-developers.com/android/triangleaway-reset-flash-counter-tool/
I recently rooted my S3 and am running frostys basic jelly bean Rom. I've installed CWM and checked my flash counter and its at 0 and I want to keep it that way. So do I need to go back to stock jelly bean through Odin then flash the new Rom that I want to try?
Sent from my SGH-T999 using xda premium
RnRexpress3423 said:
I recently rooted my S3 and am running frostys basic jelly bean Rom. I've installed CWM and checked my flash counter and its at 0 and I want to keep it that way. So do I need to go back to stock jelly bean through Odin then flash the new Rom that I want to try?
Sent from my SGH-T999 using xda premium
Click to expand...
Click to collapse
After the 4.1 update samsung updated their bootloader. I completely wiped my phone and it still is tripping the flash counter ever time you boot to recovery. Even after wiping everything. Even if you flashed stock ICS, after you flash your Recovery of choice through Odin you are going to trip the counter.
I am in the process of writing a guide to get back to Complete stock with a zero flash counter.
The point is, you are going to trip your counter. Dont panic, it is 100 percent resetable.
elesbb said:
After the 4.1 update samsung updated their bootloader. I completely wiped my phone and it still is tripping the flash counter ever time you boot to recovery. Even after wiping everything. Even if you flashed stock ICS, after you flash your Recovery of choice through Odin you are going to trip the counter.
I am in the process of writing a guide to get back to Complete stock with a zero flash counter.
The point is, you are going to trip your counter. Dont panic, it is 100 percent resetable.
Click to expand...
Click to collapse
I downloaded Rom Manager off the play store and flashed the recovery through Rom Manager and I've gone into recovery countless times and my flash counter still says zero. I just got the phone Friday and it came pre-loaded with JB. You said you trip the counter every time you enter recovery? Weird!
Edit - I followed the guide from this thread http://forum.xda-developers.com/showthread.php?p=33115777 but I installed the ICS version first then flashed to frostys all while not tripping the counter.
Sent from my SGH-T999 using xda premium
RnRexpress3423 said:
I downloaded Rom Manager off the play store and flashed the recovery through Rom Manager and I've gone into recovery countless times and my flash counter still says zero. I just got the phone Friday and it came pre-loaded with JB. You said you trip the counter every time you enter recovery? Weird!
Edit - I followed the guide from this thread http://forum.xda-developers.com/showthread.php?p=33115777 but I installed the ICS version first then flashed to frostys all while not tripping the counter.
Sent from my SGH-T999 using xda premium
Click to expand...
Click to collapse
I think that is the only wildcard. I flashed my recovery from Odin on my computer. Reset it via Triangle Away, booted back to recovery, and it tripped it. I remember reading that if you use Rom Manager then it doesnt. Im not sure why or why not but yes if you Odin recovery then you trip flash counter with each boot to recovery.
I have done much testing/goofing around. And no matter what scenario you are in, it is always able to flash back to stock 4.1.1 with a zero flash counter.
elesbb said:
I think that is the only wildcard. I flashed my recovery from Odin on my computer. Reset it via Triangle Away, booted back to recovery, and it tripped it. I remember reading that if you use Rom Manager then it doesnt. Im not sure why or why not but yes if you Odin recovery then you trip flash counter with each boot to recovery.
I have done much testing/goofing around. And no matter what scenario you are in, it is always able to flash back to stock 4.1.1 with a zero flash counter.
Click to expand...
Click to collapse
So then since I've gotten the wildcard does that mean I'm free to flash whatever rom I'd like without ever tripping the counter?
Sent from my SGH-T999 using xda premium
I rooted my phone without stripping the flash counter and recovery by goomanager and i checked and it was still 0.
We after i have only flash roms and newest twrp updates from goomanager. today I was trying to boot to recovery and messed up and booted to download mode. So since I was already there I went to check my flash encounter and it was set to 1. Witch it made me wonder how it got there if I havent used odin, only to root without stripping the flash encounter.
So by flashing roms etc via recovery can stripped the counter?
Not that it bothers me but just a thought
On the later stock firmwares, the bootloader was changed so that your counter will always show 1 if you are using a custom recovery.
TriangleAway will clear it, but as soon as you reboot, it will be back.
No worries.
Aerowinder said:
On the later stock firmwares, the bootloader was changed so that your counter will always show 1 if you are using a custom recovery.
TriangleAway will clear it, but as soon as you reboot, it will be back.
No worries.
Click to expand...
Click to collapse
So as long i have a custom recovery it will be 1 even after TriangleAway reset and reboot. With stock recovery it will stay at 0 right?
I know that to be the case with UVDLJC. Unsure of when that started though.
Flash counter is irrelevant.
re: flash counter
gypsy214 said:
So as long i have a custom recovery it will be 1 even after TriangleAway reset and reboot. With stock recovery it will stay at 0 right?
Click to expand...
Click to collapse
If you ever want the counter to remain a "0" just odin flash a Tmobile Jellybean v4.1.1 stock or a stock-rooted rom.
After doing that use the triangleAway and the flash counter will remain at 0 unless
you flash a custom rom which is not based on a Tmobile T999 Jellybean v4.1.1 rom.
If you want the stock-rooted Tmobile Jellybean v4.1.1 rom here is the link: http://www.androidfilehost.com/?fid=9390169635556426451
Flashing CWM or TWRP recovery has no effect on the flash counter, it will not change it one way or another.
Rooting has no effect on the flash counter either.
Misterjunky said:
If you ever want the counter to remain a "0" just odin flash a Tmobile Jellybean v4.1.1 stock or a stock-rooted rom.
After doing that use the triangleAway and the flash counter will remain at 0 unless
you flash a custom rom which is not based on a Tmobile T999 Jellybean v4.1.1 rom.
If you want the stock-rooted Tmobile Jellybean v4.1.1 rom here is the link: http://www.androidfilehost.com/?fid=9390169635556426451
Flashing CWM or TWRP recovery has no effect on the flash counter, it will not change it one way or another.
Rooting has no effect on the flash counter either.
Click to expand...
Click to collapse
This is incorrect.. Check your resources bro..
Sent from my Nexus 4 using xda premium
LuigiBull23 said:
This is incorrect.. Check your resources bro..
Sent from my Nexus 4 using xda premium
Click to expand...
Click to collapse
Indeed it is. I think I understand what he meant (not what he said). But it's still incorrect. What I said is tested and researched by me personally.
So I recently used CF Autoroot to root my T-Mobile GS3 SGH-T999 and I heard that if you try to downgrade to android versions before 4.3 your phone will be hard bricked. So with my knox counter tripped I was wondering can I flash a rom that is on 4.2.2 I want to flash the MIUI rom. Thanks in advance.
You can flash any custom Rom via Custom Recovery. Nothing bad will happen as they have only Rom and Kernel.
However just never flash Pre-4.3 Samsung firmwares via Odin. Those contain the older bootloader. If you tried to flash older bootloader, you get hardbrick.
Perseus71 said:
You can flash any custom Rom via Custom Recovery. Nothing bad will happen as they have only Rom and Kernel.
However just never flash Pre-4.3 Samsung firmwares via Odin. Those contain the older bootloader. If you tried to flash older bootloader, you get hardbrick.
Click to expand...
Click to collapse
Thanks for the answer been wanting to try MIUI for so long was scared of hard brick
Quxus said:
So I recently used CF Autoroot to root my T-Mobile GS3 SGH-T999 and I heard that if you try to downgrade to android versions before 4.3 your phone will be hard bricked. So with my knox counter tripped I was wondering can I flash a rom that is on 4.2.2 I want to flash the MIUI rom. Thanks in advance.
Click to expand...
Click to collapse
I know to get rid of the trip count I used triangle away. I installed, opened the app, followed the set up, reboot and count was back to zero.
I have S4 with MDL bootloader, was running GE based roms...and now want to restore it to STOCK and upgrade to latest firmware. Giving it away to my father so want to make completely stock with ability to receive OTAs .
Last night flashed via Oden stock 4.2.2 (MDL) rom, modem, and restored counter to (0). Tried to upgrade from the phone to the latest firmware, but getting the error (Processing Failed). Installed Kies 2.x.x and it would not recognized the device. Please Help to install latest stock 4.4.4 rom with (0) counter
Is the error when it tries to update or when checking for updates?
when checking for updates from the phone it self, but Kies also fails to connect to the phone.
You may want to try again later. Also does your computer recognize it at all?
serio22 said:
You may want to try again later. Also does your computer recognize it at all?
Click to expand...
Click to collapse
Yes, I've installed sam. drivers ... Odin, MTP and PTP works fine... Bootloader shows Samsung Rom, (0) counter...
T1001 said:
Yes, I've installed sam. drivers ... Odin, MTP and PTP works fine... Bootloader shows Samsung Rom, (0) counter...
Click to expand...
Click to collapse
what baseband are you on?
serio22 said:
what baseband are you on?
Click to expand...
Click to collapse
MDL baseband
T1001 said:
MDL baseband
Click to expand...
Click to collapse
Hmm well not sure what the problem is then. Try to update to 4.3 via odin and then give the ota a try and see it'll work
serio22 said:
Hmm well not sure what the problem is then. Try to update to 4.3 via odin and then give the ota a try and see it'll work
Click to expand...
Click to collapse
What about bootloader? and setting the counter to 0? 4.3 will flash new bootloader with KNOX and then I'll never be able to restore to 100% stock, or I'm wrong?!
For your phone to be stock right now it would have to be on NK2 firmware. Nothing wrong with that.
Knox only matters for the first 12 months, after that it's your phone not Samsung's.
Pp.
T1001 said:
What about bootloader? and setting the counter to 0? 4.3 will flash new bootloader with KNOX and then I'll never be able to restore to 100% stock, or I'm wrong?!
Click to expand...
Click to collapse
As long as you don't root it or modify it in anyway, you'll always be 100 percent stock
PanchoPlanet said:
For your phone to be stock right now it would have to be on NK2 firmware. Nothing wrong with that.
Knox only matters for the first 12 months, after that it's your phone not Samsung's.
Pp.
Click to expand...
Click to collapse
If I flash latest firmware via Odin, will it get OTAs in the future?
Not if your rooted /custom recovery and debloated, as you remove all the T-Mobile and Samsung bloat you will not get any ota updates, ( I haven't in16 months ) . I run stock /debloated /rooted.
You can run stock rooted or find a stable custom rom to use.
Pp.
Fixed it.
Re flashed the firmware via Odin again, cleared cache and data before first boot and thats fixed it!