Related
I've read numerous places that when I root my 4.1.1 i747 and install custom recovery, I will increase the flash counter no matter how I load the custom recovery. What I haven't read anywhere is whether or not Triangle Away will work to reset flash counter to 0. Anyone have any success using it?
I'll be loading stock rooted using Odin. Then I'll load custom recovery through ROM Manager since it doesn't really matter how I do it. Then I plan to use Triangle Away to get back to 0, hopefully. Then I can flash ROM's in my custom recovery without ever tripping the counter, right?
Successes using Triangle Away, or any other feedback or recommendations are appreciated!
robbieas said:
I've read numerous places that when I root my 4.1.1 i747 and install custom recovery, I will increase the flash counter no matter how I load the custom recovery. What I haven't read anywhere is whether or not Triangle Away will work to reset flash counter to 0. Anyone have any success using it?
I'll be loading stock rooted using Odin. Then I'll load custom recovery through ROM Manager since it doesn't really matter how I do it. Then I plan to use Triangle Away to get back to 0, hopefully. Then I can flash ROM's in my custom recovery without ever tripping the counter, right?
Successes using Triangle Away, or any other feedback or recommendations are appreciated!
Click to expand...
Click to collapse
Yes, I successfully did this yesterday, so flash away.
robbieas said:
I've read numerous places that when I root my 4.1.1 i747 and install custom recovery, I will increase the flash counter no matter how I load the custom recovery. What I haven't read anywhere is whether or not Triangle Away will work to reset flash counter to 0. Anyone have any success using it?
I'll be loading stock rooted using Odin. Then I'll load custom recovery through ROM Manager since it doesn't really matter how I do it. Then I plan to use Triangle Away to get back to 0, hopefully. Then I can flash ROM's in my custom recovery without ever tripping the counter, right?
Successes using Triangle Away, or any other feedback or recommendations are appreciated!
Click to expand...
Click to collapse
Triangle away works with 4.1.1 as long as you don't reboot otherwise it will keep the counter at 1 all the time. What you want to do is flash stock ics and go from there. Then you can flash whatever you want without worrying about the counter
Read this its all about triangle away
http://forum.xda-developers.com/showthread.php?t=2010157
Sent from my SGH-I747M using xda premium
There is no reason to over complicate things. I was on stock 4.1.1. I loaded the rooted 4.1.1 image using Odin, then used ROM manager to install CWM. Then used Triangle Away to reset counter to zero.
Boom, done.
Do you need to use triangle away when you first root your phone? Or can you just use it when you need to return the phone back to stock? I want to root and if I need to return my phone for warranty I want to be able to put the phone back to stock with 0 flash counter.
later not needed right away
hold on but.....
dpshptl said:
Do you need to use triangle away when you first root your phone? Or can you just use it when you need to return the phone back to stock? I want to root and if I need to return my phone for warranty I want to be able to put the phone back to stock with 0 flash counter.
Click to expand...
Click to collapse
U can just hold on on if u need to return it for service, u don't have to use it rite now since u most likely will be flashing roms and u will be triggering ur counter everytime u flash or root ur device.
ONE THING TO KNOW ABOUT TRIANGLE AWAY, IS THAT AS FAR AS I KNOW ( I DON'T KNOW ANYONE THAT HAS TRIANGLE AWAY WORKING AFTER THE 1ST JB UPDATE ) TRIANGLE AWAY WON'T WORK ON OUR DEVICES PAST JB, SO IF U NEED TO RESET YOU COUNTER U NEED TO ODIN BACK TO ICS STOCK ROOTED AND THEN USE TRIANGLE AWAY.
sorry about the caps, just tryin to make my point clear, if anyone has triangle away working on JB please feel free to post about it.:laugh:
Mr_Jay_jay said:
U can just hold on on if u need to return it for service, u don't have to use it rite now since u most likely will be flashing roms and u will be triggering ur counter everytime u flash or root ur device.
ONE THING TO KNOW ABOUT TRIANGLE AWAY, IS THAT AS FAR AS I KNOW ( I DON'T KNOW ANYONE THAT HAS TRIANGLE AWAY WORKING AFTER THE 1ST JB UPDATE ) TRIANGLE AWAY WON'T WORK ON OUR DEVICES PAST JB, SO IF U NEED TO RESET YOU COUNTER U NEED TO ODIN BACK TO ICS STOCK ROOTED AND THEN USE TRIANGLE AWAY.
sorry about the caps, just tryin to make my point clear, if anyone has triangle away working on JB please feel free to post about it.:laugh:
Click to expand...
Click to collapse
This is not even close to the truth.
Aerowinder said:
This is not even close to the truth.
Click to expand...
Click to collapse
and u say this because? I mean I'm just talking on my experience with triangle away and JB It didn't work, I would use it and it would reset but once I restarted the counter would go back to "1" and honestly I'm not the only one, so please if u know the rite answer please explain, just calling me a liar is not helping anyone at all.
Mr_Jay_jay said:
and u say this because? I mean I'm just talking on my experience with triangle away and JB It didn't work, I would use it and it would reset but once I restarted the counter would go back to "1" and honestly I'm not the only one, so please if u know the rite answer please explain, just calling me a liar is not helping anyone at all.
Click to expand...
Click to collapse
I'm not calling you a liar. I simply stated that your post was not factually accurate. TriangleAway does indeed work as intended on even the new MD5.
Using a custom recovery will cause your flash counter to trip on newer JB builds. This may be what you meant, but the issue is not related to TA. It's a bootloader "feature". You can witness this yourself by resetting the flash counter, then rebooting into download mode. Count will be 0.
Aerowinder said:
I'm not calling you a liar. I simply stated that your post was not factually accurate. TriangleAway does indeed work as intended on even the new MD5.
Using a custom recovery will cause your flash counter to trip on newer JB builds. This may be what you meant, but the issue is not related to TA. It's a bootloader "feature". You can witness this yourself by resetting the flash counter, then rebooting into download mode. Count will be 0.
Click to expand...
Click to collapse
So what u're saying is that my custom recovery is to blamed? I can say that statement is partially true. Wait.. u think I havent tried to reset my counter while on JB before?? I'm telling it didn't work why don't you go head and try to reset your counter and show that it did work.
check it out.
http://www.youtube.com/watch?v=LxpL46-Zd0A&feature=youtu.be
Mr_Jay_jay said:
So what u're saying is that my custom recovery is to blamed? I can say that statement is partially true. Wait.. u think I havent tried to reset my counter while on JB before?? I'm telling it didn't work why don't you go head and try to reset your counter and show that it did work.
check it out.
http://www.youtube.com/watch?v=LxpL46-Zd0A&feature=youtu.be
Click to expand...
Click to collapse
He's correct. Having a custom recovery will always trip the flash counter to 1 after every subsequent reboot. If you use Ta and reboot, you'll see 0. But the next time you reboot and don't use Ta you will see 1. It doesn't matter what ROM you run or how you've rooted in the end, the custom binary (TWRP / CWM) will Always trip the counter.
That being said if you don't want to continously trip the counter you're going to need to go back to stock recovery.
Sent from my SGH-T999 using Tapatalk 2
TheLastSidekick said:
He's correct. Having a custom recovery will always trip the flash counter to 1 after every subsequent reboot. If you use Ta and reboot, you'll see 0. But the next time you reboot and don't use Ta you will see 1. It doesn't matter what ROM you run or how you've rooted in the end, the custom binary (TWRP / CWM) will Always trip the counter.
That being said if you don't want to continously trip the counter you're going to need to go back to stock recovery.
Sent from my SGH-T999 using Tapatalk 2
Click to expand...
Click to collapse
I do Agree with his statment, however while I was on any ICS rom even with custom recovery, TA would work even after a reboot, so my counter would stay at "0" it wasnt after I upgraded to JB when the TA would reset after reboot. I will upload a video of doing TA on ICS and everything just to prove I'm not just arguing just because. but it will have to wait til l8er tonite.
Mr_Jay_jay said:
I do Agree with his statment, however while I was on any ICS rom even with custom recovery, TA would work even after a reboot, so my counter would stay at "0" it wasnt after I upgraded to JB when the TA would reset after reboot. I will upload a video of doing TA on ICS and everything just to prove I'm not just arguing just because. but it will have to wait til l8er tonite.
Click to expand...
Click to collapse
There is no need for a video. I understand what you are saying, and I'm telling you, it's because of the bootloader. Not TriangleAway.
I am on 4.1.1 and TA 2.90 works FINE, the Counter shows "0" after a bunch of reboots, and "Allow tracker to run" is checked...
The ONLY time the counter trips is when/if I boot into the recovery or downloader modes.
I guess some structure of the setup makes a difference. I am using Root66 SGHT999 Build JR003L.T999UVDLJA with a T999UVDMD5 Baseband
bobolinko said:
I am on 4.1.1 and TA 2.90 works FINE, the Counter shows "0" after a bunch of reboots, and "Allow tracker to run" is checked...
The ONLY time the counter trips is when/if I boot into the recovery or downloader modes.
I guess some structure of the setup makes a difference. I am using Root66 SGHT999 Build JR003L.T999UVDLJA with a T999UVDMD5 Baseband
Click to expand...
Click to collapse
kool. maybe that's a good workaround. thanks. but in my case still won't work.. but then again i'm 4.1.2. thanks!
Mr_Jay_jay said:
U can just hold on on if u need to return it for service, u don't have to use it rite now since u most likely will be flashing roms and u will be triggering ur counter everytime u flash or root ur device.
ONE THING TO KNOW ABOUT TRIANGLE AWAY, IS THAT AS FAR AS I KNOW ( I DON'T KNOW ANYONE THAT HAS TRIANGLE AWAY WORKING AFTER THE 1ST JB UPDATE ) TRIANGLE AWAY WON'T WORK ON OUR DEVICES PAST JB, SO IF U NEED TO RESET YOU COUNTER U NEED TO ODIN BACK TO ICS STOCK ROOTED AND THEN USE TRIANGLE AWAY.
sorry about the caps, just tryin to make my point clear, if anyone has triangle away working on JB please feel free to post about it.:laugh:
Click to expand...
Click to collapse
You can avoid using Odin and flash old firmware (excluding system / kernel) directly via heimdall or dd (which can be nicely bundled into an update.zip), avoiding the whole mess of needing Odin/Windows and having to backup+restore your system.
I think I'll make an update.zip just to flash the oldest firmware onto our phones -- I just made one that flashes the latest UVDMD5 firmware. The ROM shouldn't make a difference as far as trying to clear the flash counter really, it's the firmware that would be blocking that.
Also, flashing ROMs through CWM Recovery (and probably other custom ones) avoids tripping the flash counter. If you can root your ROM and dd the recovery directly to your eMMC, it avoids tripping the flash counter. Then you can use CWM Recovery to flash things without tripping the counter as well.
Remember, these are just computers with Linux + kernel modifications + custom Java VM running on them, essentially. It's good to become comfortable with UNIX commands like dd.
mnasledov said:
Also, flashing ROMs through CWM Recovery (and probably other custom ones) avoids tripping the flash counter. If you can root your ROM and dd the recovery directly to your eMMC, it avoids tripping the flash counter. Then you can use CWM Recovery to flash things without tripping the counter as well.
Remember, these are just computers with Linux + kernel modifications + custom Java VM running on them, essentially. It's good to become comfortable with UNIX commands like dd.
Click to expand...
Click to collapse
I think you might be a tad off on this ......
just booting into recovery when you use anything other than a stock recovery will trip the flash counter. the ONLY way that counter won't trip is when you use a stock recovery. At least that's been the case with all of the doings on my rooted gs3 and Note 10.1
bobolinko said:
I think you might be a tad off on this ......
just booting into recovery when you use anything other than a stock recovery will trip the flash counter. the ONLY way that counter won't trip is when you use a stock recovery. At least that's been the case with all of the doings on my rooted gs3 and Note 10.1
Click to expand...
Click to collapse
Really? I mean I'm no authority on this, so I could be wrong but I based this off my findings last night. I was in Download mode quite a few times and got to see my Flash Counter which was at 3. I've gone into recovery dozens if not hundreds of times by now on this device as well as flashed dozens and dozens of things ...
Even if it was just an 8-bit counter that overflowed, I'd need to have flashed over 256 things which I don't think I've reached yet and it would be totally silly if Samsung made the counter so easy to defeat that an 8-bit numeric overflow would bring it back to 0.
Can anyone else chime/weigh in? I'm curious now. I heard that using dd is supposed to avoid the flash counter. As a software engineer, I'd think there has to be some hook to trip that counter and that hook would belong to whatever firmware is on the phone for flashing (i.e. the stock recovery) and that if any other software gains control of the phone, all bets are off.
bobolinko said:
I think you might be a tad off on this ......
just booting into recovery when you use anything other than a stock recovery will trip the flash counter. the ONLY way that counter won't trip is when you use a stock recovery. At least that's been the case with all of the doings on my rooted gs3 and Note 10.1
Click to expand...
Click to collapse
I don't know who told you all of that or where you read it but you are wrong.
The only things that trip the flash counter is when you flash a custom rom or a custom kernel.
Simply booting into stock or custom recovery will not trip the flash counter at all.
Think about it, that's why it's called a FLASH counter, it counts the number of rom and kernel flashes. LOL
Misterjunky said:
I don't know who told you all of that or where you read it but you are wrong.
The only things that trip the flash counter is when you flash a custom rom or a custom kernel.
Simply booting into stock or custom recovery will not trip the flash counter at all.
Think about it, that's why it's called a FLASH counter, it counts the number of rom and kernel flashes. LOL
Click to expand...
Click to collapse
It trips whenever I boot into TWRP though. Maybe some phones are different?
Sent from my SGH-T999 using Tapatalk 2
re: unlocked?
TheLastSidekick said:
It trips whenever I boot into TWRP though. Maybe some phones are different?
Sent from my SGH-T999 using Tapatalk 2
Click to expand...
Click to collapse
Perhaps since I have an unlocked phone it might make a difference?
I have a Galaxy S3 AT&T I747 Unlocked phone and am using it with Tmobile service.
That makes sense actually lol as it says I have an SGH-T999 and mine isn't unlocked. Probably the model of the phone acts slightly differently with Ta and recoveries.
Sent from my SGH-T999 using Tapatalk 2
In my case My counter won't move from "1" no matter what I do, Restart to download or Recovery ( TWRP), or flash a new rom which I do alot, only way it goes from 1 to "2" is when I do something to my phone and I need to odin back to stock and re root(which I did for research) ... it's then it gets trigger again.
I've read a little bit about Knox in the last few months, but wanted to make sure I've got everything right, especially since things have probably changed since the early days of Knox.
Here's my situation: I'm running a TMO Galaxy S3 w/ stock recovery. I was using mrRobinson's T999UVDMD5 and foolishly did the TMO update to T999UVUEMJC.
(I thought I'd be able to retain root, but ended up losing root, getting Knox, and a bootloader that won't let me roll back. )
Now my phone locks up during boot. If I'm lucky, it'll boot but locks up nearly immediately after boot.
And this is with stock everything. I've had the phone a year and a half, so it's out of warranty.
So what's Sammy's stance on their update breaking phones out of warranty?
Do they cover that? Can I get a TMO store to put DMD5 back on?
I'm thinking of using the root66 EMJC img. I'm pretty confident that it won't brick the phone, since it'll be the same bootloader I'm currently running.
And I'm not too worried if it trips the Flash Counter (flag, really) since I should be able to clear it.
But what about the Knox counter? Will that get tripped? mrRobinson's post leads me to think that it will.
Any other root options I should consider? (Above all else, I'd like to be able to restore back to stock if I need to.)
I kinda like the stock ROM (save for some bloatware) and TouchWiz doesn't bother me.
If it's out of warranty, it shouldn't matter if you trip the Knox counter, Should it? Some say as long as you don't install a custom recovery that if you do the root 66 method just for root that Knox doesn't trip. But I can never get anyone to confirm that.
Sent from my SGH-T999L using xda app-developers app
masondoctorjt said:
If it's out of warranty, it shouldn't matter if you trip the Knox counter, Should it? Some say as long as you don't install a custom recovery that if you do the root 66 method just for root that Knox doesn't trip. But I can never get anyone to confirm that.
Sent from my SGH-T999L using xda app-developers app
Click to expand...
Click to collapse
Thanks masondoctorjt! That's one of my questions. (albeit, a lesser one)
If TMO/Sammy's update f'd up my phone will they cover it if it's out of warranty? especially when it was fine before?
(It's also a work phone, so I'd like to be able to return it like I got it, if need be.)
It's that confirmation I'm looking for here.
This Knox thread seems to state that as long as a Knox-enabled bootloader is used, the counter won't trip. But it also says flashing Knox-enabled fw via Odin trips the Knox counter too. (which I don't fully believe) Hence my confusion. A lot of contradictory info.
Add to that the loose usage of 'flash counter' to refer to both the triangle/flash counter/flag and the Knox counter/flag and you can see why my head is spinning!
It was tricky for me to see the Knox Counter info for my phone. Recovery and Bootloader mode didn't pop up the screen.
But when I used adb to enter bootloader, I saw the counter info.
So did you root it, and if so, did the trip the knox counter?
Sent from my GT-N8013 using xda app-developers app
No, not yet. I was hoping to hear back from someone who's tried this.
I didn't want to be the first guinea pig.
I'll probably take my phone down to the T-Mobile store this weekend and give them an earful to see if they can roll me back w/o tripping Knox flag and report back.
PhilipJFry said:
No, not yet. I was hoping to hear back from someone who's tried this.
I didn't want to be the first guinea pig.
I'll probably take my phone down to the T-Mobile store this weekend and give them an earful to see if they can roll me back w/o tripping Knox flag and report back.
Click to expand...
Click to collapse
I would be like to hear how you did after going to T-mobile. Thanks.
patcal said:
I would be like to hear how you did after going to T-mobile. Thanks.
Click to expand...
Click to collapse
I honestly don't expect a whole lot from them really. But it's an avenue I have to try.
I'm ultimately going to root this anyway. If TMO can successfully roll me back to T999UVDMD5 completely, I'll just root that and stick till the dust has settled somewhat on Knox.
For Rooting after getting that 4.3 update, the process is pretty simple really. Since you have 4.3, you flash Root66 Via Odin. Or you could flash a custom Recovery via Odin and then flash SuperSU zip via Recovery.
It is my understanding that either one will not trip the Knox Counter. If you wish you can follow this guide.
NOTE - Do not Try to flash Older Root66 versions. You can only flash UVUEMJC version. If you flash any other version even accidentally then you will get expensive paperweight.
patcal said:
I would be like to hear how you did after going to T-mobile. Thanks.
Click to expand...
Click to collapse
It was ultimately unproductive.
I went in and explained the situation (w/ less detail) and asked them to roll me back to UVDMD5.
They said Samsung doesn't let them roll back, so he then proceeded to recover my phone.
He booted into recovery and wiped cache. When that proved unsuccessful, he wiped data. (nothing I couldn't have done)
Wiping data ultimately made the phone usable again. He then proceeded to enter some short codes to bind me to the network quicker.
(all he mentioned was #NUM#)
So I'm back to stock (more or less ). Not sure when I'll root now.
Perseus71 said:
For Rooting after getting that 4.3 update, the process is pretty simple really. Since you have 4.3, you flash Root66 Via Odin. Or you could flash a custom Recovery via Odin and then flash SuperSU zip via Recovery.
It is my understanding that either one will not trip the Knox Counter. If you wish you can follow this guide.
NOTE - Do not Try to flash Older Root66 versions. You can only flash UVUEMJC version. If you flash any other version even accidentally then you will get expensive paperweight.
Click to expand...
Click to collapse
From what I've read, the custom recovery should trip Knox. Have you tried this yourself?
I'm fairly confident if I merely flash root66 that it won't trip Knox. But I'd like better than a 51% confidence interval, that's all.
(Again, it's a work phone and I'd like to return it as I got it.)
It will trip that previous counter bit. Don't think it will trip the Knox counter.
No I do not have the Knox Counter.
PhilipJFry said:
It was ultimately unproductive.
I went in and explained the situation (w/ less detail) and asked them to roll me back to UVDMD5.
They said Samsung doesn't let them roll back, so he then proceeded to recover my phone.
He booted into recovery and wiped cache. When that proved unsuccessful, he wiped data. (nothing I couldn't have done)
Wiping data ultimately made the phone usable again. He then proceeded to enter some short codes to bind me to the network quicker.
(all he mentioned was #NUM#)
So I'm back to stock (more or less ). Not sure when I'll root now.
From what I've read, the custom recovery should trip Knox. Have you tried this yourself?
I'm fairly confident if I merely flash root66 that it won't trip Knox. But I'd like better than a 51% confidence interval, that's all.
(Again, it's a work phone and I'd like to return it as I got it.)
Click to expand...
Click to collapse
I believe I tripped the Knox counter when I flashed CWM recovery after I flashed stock 4.3 from Docs signature. Phone works great but no warranty on a 6 month old phone.
Pat
patcal said:
I believe I tripped the Knox counter when I flashed CWM recovery after I flashed stock 4.3 from Docs signature. Phone works great but no warranty on a 6 month old phone.
Pat
Click to expand...
Click to collapse
Was that the Flash Counter or Knox Counter?
Perseus71 said:
Was that the Flash Counter or Knox Counter?
Click to expand...
Click to collapse
Well I reset the flash counter with Triangle away. The Knox counter was not tripped until I flashed the recovery.
Pat
patcal said:
I believe I tripped the Knox counter when I flashed CWM recovery after I flashed stock 4.3 from Docs signature. Phone works great but no warranty on a 6 month old phone.
Pat
Click to expand...
Click to collapse
Pat,
So just to get this straight, you flashed the stock TMO update, so you were not rooted?
Or did you do a root-injected variant of the stock?
Either way, I'm surprised you tripped the (triangle) flash counter.
But I'm more worried about the Knox counter; not worried about the other since there is Triangle Away.
patcal said:
Well I reset the flash counter with Triangle away. The Knox counter was not tripped until I flashed the recovery.
Pat
Click to expand...
Click to collapse
Thanks for letting me know.
PhilipJFry said:
Pat,
So just to get this straight, you flashed the stock TMO update, so you were not rooted?
Or did you do a root-injected variant of the stock?
Either way, I'm surprised you tripped the (triangle) flash counter.
But I'm more worried about the Knox counter; not worried about the other since there is Triangle Away.
Click to expand...
Click to collapse
I flashed T999LUVUBMK4 from Docs signature. I am not exactly sure when the flash counter tripped. I do know that the Knox bit was tripped by my flashing the recovery.
Edit: Don't remember how I got root. Sorry.
Edit2: T999L_4.3_UVUBMK4_deodexed_KnoxFREE.zip is the file I flashed.
patcal said:
I flashed T999LUVUBMK4 from Docs signature. I am not exactly sure when the flash counter tripped. I do know that the Knox bit was tripped by my flashing the recovery.
Edit: Don't remember how I got root. Sorry.
Edit2: T999L_4.3_UVUBMK4_deodexed_KnoxFREE.zip is the file I flashed.
Click to expand...
Click to collapse
The Flash Counter (Triangle away kind) will trip due to the running tracer (read Sysscope) in that Rom. I'd not worry about it as Triangle away will take care of it. Yes it trips due to custom Recovery and Root.
Perseus71 said:
The Flash Counter (Triangle away kind) will trip due to the running tracer (read Sysscope) in that Rom. I'd not worry about it as Triangle away will take care of it. Yes it trips due to custom Recovery and Root.
Click to expand...
Click to collapse
Thanks for that Perseus71. Didn't know about Sysscope before, but sounds interesting. I figured root66 removed it, since mrRobinson claims that it doesn't trip the normal flash counter. And this matches my experience w/ his previous root66.
patcal said:
I flashed T999LUVUBMK4 from Docs signature. I am not exactly sure when the flash counter tripped. I do know that the Knox bit was tripped by my flashing the recovery.
Edit: Don't remember how I got root. Sorry.
Edit2: T999L_4.3_UVUBMK4_deodexed_KnoxFREE.zip is the file I flashed.
Click to expand...
Click to collapse
So it sounds like you were able to flash a rooted ROM and not affect Knox, as long as you leave the stock recovery.
That was my plan anyway. I'll probably look into this later this week.
PhilipJFry said:
Thanks for that Perseus71. Didn't know about Sysscope before, but sounds interesting. I figured root66 removed it, since mrRobinson claims that it doesn't trip the normal flash counter. And this matches my experience w/ his previous root66.
So it sounds like you were able to flash a rooted ROM and not affect Knox, as long as you leave the stock recovery.
That was my plan anyway. I'll probably look into this later this week.
Click to expand...
Click to collapse
Yep. Let us know how it goes.
FYI, the Knox counter gets tripped.
I flashed the root66 T999UVUEMJC via Odin. That's it.
Oh, and the flash counter does not get set.
Tried reverting my T999L back to stock last week and used the root66 firmware (4.3 of course) and was able to get my phone back in working condition, unfortunately the warranty bit is now tripped and I can no longer flash things inside of Odin (haven't tried mobile, probably the same outcome).
With the JUMP program through Tmo changing now and the warranty bit tripped, what are my odds of being able to trade it in without any questions?
Also, how would I go about going back to stock with Odin no longer working?
***I currently have the stock setup through root66, with TWRP recovery installed if that gives anymore info to make things easier***
Just because Knox bit is tripped, should not make Odin stop working. What is the issue with Odin ?
So long the phone's working, hopefully Jump will accept it. Not sure just guessing.
Perseus71 said:
Just because Knox bit is tripped, should not make Odin stop working. What is the issue with Odin ?
So long the phone's working, hopefully Jump will accept it. Not sure just guessing.
Click to expand...
Click to collapse
I'll have to check back tomorrow and get back to you, it might have just been the recovery I was trying to flash. Ended up dd'n that.
Sent from my SGH-T999L using Tapatalk
My warranty bit has been tripped and I can still use ODIN no problem
I'm running the T999L Root66 4.3 ROM on my phone and am planning on trading it in on Friday (hopefully) and want to 100% factory reset it. I've already grabbed the 4.3 stock odin file from doc's thread and I read through the thread, but couldn't find this answer.
Once I run the odin file and reboot it, none of my data should be there from before right? Or do I need to then hit the factory reset from inside the ROM? Will I need to run triangle reset after running odin? Everything looks OK currently inside the app.
Thanks again for everything!
Sent from my SGH-T999L using Tapatalk
thetolsonator said:
I'm running the T999L Root66 4.3 ROM on my phone and am planning on trading it in on Friday (hopefully) and want to 100% factory reset it. I've already grabbed the 4.3 stock odin file from doc's thread and I read through the thread, but couldn't find this answer.
Once I run the odin file and reboot it, none of my data should be there from before right? Or do I need to then hit the factory reset from inside the ROM? Will I need to run triangle reset after running odin? Everything looks OK currently inside the app.
Thanks again for everything!
Click to expand...
Click to collapse
You will have to go to Stock Recovery after flashing 4.3 Stock. Hit Factory Reset there and you are good to go.
Perseus71 said:
You will have to go to Stock Recovery after flashing 4.3 Stock. Hit Factory Reset there and you are good to go.
Click to expand...
Click to collapse
If I understand the packing of the files, that is included. Giving it a shot now
Hi, sorry for these noob questions.
I have to send my device back for warranty and I just learned about the flash counter. So used triangle away to set the number back to zero but my phone's device status still says "custom." I read somewhere that a factory reset would be able to change that back to normal. I will try that soon, but I haven't unrooted yet. I was going to flash a stock rom (also read that that would change device status back to "normal") after changing the flash counter number, but wouldn't that change it to 1? How do I unroot without triggering the flash counter? Thanks in advance!
What bootloader are you on?
serio22 said:
What bootloader are you on?
Click to expand...
Click to collapse
how do I check that?
Also, I tried flashing stock firmware with Odin before, but nothing happened except I lost root. And I forgot about the flash counter, so I rooted again and used Triangle Away. What do I do from here? I just went into download mode again, and binary status says "custom" instead of samsung official, even though I just used triangle away.
Can you post a picture of your download screen? Reason I ask is if you got knox bootloader your knox counter is most likely tripped and you can't reset it.. and to get official status you need to be completely stock, the system will check on every boot so no matter how many times you reset it, it will detect custom. You need to run triangle away, reboot straight to download mode and flash back to stock, after that reboot straight into recovery and do a factory reset. Those are the steps if I'm not mistaken
serio22 said:
Can you post a picture of your download screen? Reason I ask is if you got knox bootloader your knox counter is most likely tripped and you can't reset it.. and to get official status you need to be completely stock, the system will check on every boot so no matter how many times you reset it, it will detect custom. You need to run triangle away, reboot straight to download mode and flash back to stock, after that reboot straight into recovery and do a factory reset. Those are the steps if I'm not mistaken
Click to expand...
Click to collapse
do you mean a picture of my download mode screen? basically, this is what it says (I guess typing it out is better, since the words are very small anyways)
Odin Mode
product name: SGH-M919
current binary: custom
system status: custom
CSB-OEM_Config_LSB: 0x30
Write protection: enable
and then there's the big green android, and "downloading.. do not turn off target" under it.
I don't think I have the knox bootloader, because I never upgraded to 4.3. I was always using 4.2.2 android before I flashed a custom rom, and I also don't have the two knox lines showing up. I'm guessing I'm fine as long as I can revert back to original stock and get my phone to stop showing "custom"
I first flashed the stock rom with Odin, then I used triangle away, and then I factory reset it, which is why I don't understand why it still says "custom" in download mode, because I should be on the stock rom already. If I boot into download mode immediately after I use triangle away, it shows "official samsung," but if I try again later, it reverts back to "custom."
If I follow the steps you mentioned, would flashing the stock rom cause the flash counter to go to 1?
No it will not because it is official and unrooted.. was it rooted or did you have custom recovery? Just do it the way I posted and see if that works
serio22 said:
No it will not because it is official and unrooted.. was it rooted or did you have custom recovery? Just do it the way I posted and see if that works
Click to expand...
Click to collapse
your method worked! my phone's device status now says "official" and it no longer says custom when I boot into download mode. So, as long as my phone says those things and I reset the flash counter following your steps, I'll be fine right? Thank you so much!!
Yes.. no problem!
serio22 said:
Yes.. no problem!
Click to expand...
Click to collapse
sorry, I have one more question. you said to boot straight into download mode after using triangle away, so I pressed the top volume button to reboot normally, but then I immediately pulled out the battery, and then booted into download mode. The phone never had a chance to reboot, so there isn't a problem with what I did right?
I did the same thing after flashing. I just pulled out the battery, and then booted into recovery mode.
Thanks again!
Yeah that's not problem, that's actually what you want, to not give the system a chance to boot at all
serio22 said:
Yeah that's not problem, that's actually what you want, to not give the system a chance to boot at all
Click to expand...
Click to collapse
okay, again, thanks a lot!!
lalachata0 said:
okay, again, thanks a lot!!
Click to expand...
Click to collapse
I am trying to do something similar. I want to reset counter but it does not stick. ie when I use triangle away then reboot it still shows the count as 10.
Is there any way to get a stock kernel?
I am running stock rom that is rooted but kernel does not appear to be stock.
Right now I am looking for zip flashable NB4 kernel??
Looked for hours and cant find.
Or also would like any hints on how to get triangle reset to stick.
Thanks
shortbus1234 said:
I am trying to do something similar. I want to reset counter but it does not stick. ie when I use triangle away then reboot it still shows the count as 10.
Is there any way to get a stock kernel?
I am running stock rom that is rooted but kernel does not appear to be stock.
Right now I am looking for zip flashable NB4 kernel??
Looked for hours and cant find.
Or also would like any hints on how to get triangle reset to stick.
Thanks
Click to expand...
Click to collapse
I'm pretty sure you need to be on the stock kernal and recovery in order for triangle away to work. Maybe you should try flashing the stock rom, reroot and then use triangle away? that's what I did, because I wasn't using the stock samsung firmware
I flashed stock Firmware. It took 2 times with ODIN. The first flash added knox then I had to flash a second time to reinstall everything else. I now have a Knox 0x0 rooted phone. I was curious so I used towelroot and rooted the phone. Still 0x0 and root was succesful. I installed triangle away and it showed the counter was at 0.
Just unrooted and I will take back to tmobile to replace under warranty.
What they don't know will not hurt them.
It would encourage everyone wishing to have root to look into and support towelroot. It works great!!!!
Knox will still be tripped 0x1 if you flash custom ROM......but IMO it is worth it