Coming from the SGH-i777, there is a One-Click Odin Unroot/Return to Stock that does not trigger the flash counter. The comments in this thread state that the the SGH-i727 method WILL trigger the flash counter. And according to this thread, I have no way of resetting the counter.
I want to have the option for warranty service down the road, but it looks like if I'm currently rooted there is no way to return to stock without triggering the flash counter and voiding the warranty. In the first thread I linked there is a comment asking why the process to flash CWM through Odin does not trigger the flash counter, but the Stock recovery method does - there is no answer.
The primary question is still, how do I return the phone to its original factory state, from root+CWM, without triggering the flash counter? Any help, comments, thread pointing, education would be greatly appreciated.
Related
Ive been reading up on the current root methods and all of the subsequent issues that comes along with each method and need some clarification. The desired result that im looking for is to have root with cwm recovery, to not trip the counter, and not have any boot issues, partition corruption issues, nandroid backup issues, or anything else...Whats the correct procedures should i take?
cavsoldier19d said:
Ive been reading up on the current root methods and all of the subsequent issues that comes along with each method and need some clarification. The desired result that im looking for is to have root with cwm recovery, to not trip the counter, and not have any boot issues, partition corruption issues, nandroid backup issues, or anything else..
Click to expand...
Click to collapse
From all the threads, there is no such method... The root-injected method is reported to cause severe problems, the CWM method increases the counter. But CWM never caused any problems here, neither with the original firmware not after updating with Kies to LH2.
BUT: TriangleAway is available which sucessfully reset the counter on my N8000 to zero. Just strictly follow the instructions.
The counter thing is pretty much unavoidable if you want to play it safe (ie, not turning your note 10.1 into a paper weight). It's Samsung trying to catch people on warranty claims, but as already noted there are ways to reset it. Not sure about the Note 10.1, but I know the GS3 still reads MODIFIED (on the stock rom) even after using TriangleAway. Only way to get rid of that is to return it to a stock rom.
If you want root access though there's not much choice. Use method 2. I personally wouldn't trust any other method. Odin and CWM are your friends!
I've rooted my tablet and the superSU won't update can anyone help!?
Sent from my GT-P5113 using xda app-developers app
Will I lose my warranty, if i install this JB (http://forum.xda-developers.com/showthread.php?t=2007402&page=8&nocache=1) to my p3110?
for example, if something will be bad, and i will want to take it for warranty with that rom, everything will be ok?
sorry, if i do some mistakes - my english is not very good.
If you're French and install through official channels (i.e. via Kies) then I imagine your warranty will remain intact.
If you're not French and/or you install via Odin then you will probably lose your warranty.
For what it is worth I'm not French, but I installed the new 4.1.1 firmware via Mobile Odin and I'm perfectly happy with it. Yes, I've probably lost my warranty, but that doesn't bother me too much.
If you need the warranty you flash the firmware of the site were you live and then you send the tab to sat.
Yes, if you need to send to repair. My P3110 is still under warranty, the original stock rom is 4.0.4. Nowadays I am using offical stock 4.1.1 french version and if need use the warranty I will have to reflash it back. Also, I have to zero count the firmware counter with "triangle away", until now I have flashed a lot with no problems at all, using a lot of cm10 flavors. You just need to learn what to know and avoid mess up everything.
Good luck!
The danger with the flashing back approach is that you assume you will always be able to access your device to flash back to stock and reset counter prior to return.
However, if your warranty repair is needed because the thing has broken then you may well not be able to flash it back to stock...because it is broken.
Flashing by unofficial means is always a risk, but if you know what you're doing then the risk is reduced (but not entirely eliminated).
Hi I'm gonna root my phone using a file which can do it with stock recovery i just wanted to ask does it void my warranty?
How the company can understand that my warranty void?
does flashing a stock rom void my warranty?
how about insurance?
thanks in advance
warranty void
Any rooting will void warranty.
Samsung would know it if you do send it in rooted for claims purposes.
However root can be undone. Just flash stock rom will unroot your device.
Suggest you read, read and read for more info....
Good luck and happy rooting... :good:
I know how to unroot with adb or terminal, ... I just wanted to make sure how exactly the Samsung company will find out my warranty is voided?
also I read somewhere about this that Samsung has a file every rom that flashed will add a number in this file so the Samsung will find out if you flash a rom or not, in that case if I even flash a stock rom it will void my warranty! if not then nothing will do as i can flash my rom (as I have already a backup) anytime! Right?
I know the perception out there is that rooting will void your warranty but this is not necessarily the case. You can always flash back to stock. Rooting can't damage the hardware so if they try not to fix/replace failed hardware because of rooting you could probably due them. Most rooting/firmware changes don't touch the download mode stop you should always be able to flash to stock.
Sent from my GT-P6800 using xda app-developers app
sijav said:
I know how to unroot with adb or terminal, ... I just wanted to make sure how exactly the Samsung company will find out my warranty is voided?
also I read somewhere about this that Samsung has a file every rom that flashed will add a number in this file so the Samsung will find out if you flash a rom or not, in that case if I even flash a stock rom it will void my warranty! if not then nothing will do as i can flash my rom (as I have already a backup) anytime! Right?
Click to expand...
Click to collapse
Okay... let me try to explain further to your question...
Firstly... I dont know how exactly Samsung will now if you are rooted or not... They must have some software or hardware to check that. I know that there is an app to check wether you are rooted or not. Maybe they use that app...
Secondly... my guess is you are referring to the flashing counter... Normally when rooted, this will be bypassed, so you can flash and reflash any rom you like, any number of times you like. (Actually, I've not seen this counter in my P6800... I might be wrong, but in SGS3 yes, I've seen it)
Hope this clarify further...
I see a lot of similar questions, but am getting yes and no answers.
Background+Rant: after spending yesterday bashing my head against knox, i managed to get my new sm-g900p from oem 5.0 back to stock 4.4.2, towel-rooted successfully (keeping 0x0). Good, but not enough. without a real recovery to make a backup, samsung is actually putting me at more risk than ever at turning my phone into a brick (security my ***). plus the slow/ugly stock rom hurts my head after seeing what Android should be. They act like making a rewarding process dangerous is going to stop this entire community! Anyway enough ranting from a non-dev.
what i need to know is since i have NOT sent knox into lockdown mode(0x1), can i get knox out of the Bootloader? from what i understand, you can disable the knox apps using superSU, titanium, or a command prompt, but this will not effect the flash counter (not eliminating the risk of permanent 0x1). we flash bootloaders all the time with our recoveries, firmwares, and roms. If knox has not activated (ie blocking root, apps, etc) how is this bootloader different?
http://www.s4miniarchive.com/2013/12/how-to-remove-knox-bootloader-from-new.html seems hopeful as it involves extracting the firmware to linux, removing the knox code, repacking and reflashing. sounds like something even i could do, but would feel more comfortable downloading from a real developer.
Hopes and thoughts to go along with my disappointment and concerns?
3rdsurfer said:
I see a lot of similar questions, but am getting yes and no answers.
Background+Rant: after spending yesterday bashing my head against knox, i managed to get my new sm-g900p from oem 5.0 back to stock 4.4.2, towel-rooted successfully (keeping 0x0). Good, but not enough. without a real recovery to make a backup, samsung is actually putting me at more risk than ever at turning my phone into a brick (security my ***). plus the slow/ugly stock rom hurts my head after seeing what Android should be. They act like making a rewarding process dangerous is going to stop this entire community! Anyway enough ranting from a non-dev.
what i need to know is since i have NOT sent knox into lockdown mode(0x1), can i get knox out of the Bootloader? from what i understand, you can disable the knox apps using superSU, titanium, or a command prompt, but this will not effect the flash counter (not eliminating the risk of permanent 0x1). we flash bootloaders all the time with our recoveries, firmwares, and roms. If knox has not activated (ie blocking root, apps, etc) how is this bootloader different?
http://www.s4miniarchive.com/2013/12/how-to-remove-knox-bootloader-from-new.html seems hopeful as it involves extracting the firmware to linux, removing the knox code, repacking and reflashing. sounds like something even i could do, but would feel more comfortable downloading from a real developer.
Hopes and thoughts to go along with my disappointment and concerns?
Click to expand...
Click to collapse
I did a little reading on the xda thread that links to but other than it being done just because it can, I don't see the real usefulness in the exercise of removing knox from a stock bootloader.
As you already pointed out, getting anywhere with a stock rom is pretty much pointless without two things:
1. Root
2. Custom Recovery
First of all, lets face it, there is only so much you can do with a stock odexed rom. Secondly, I personally dont understand the need to keep the knox bit untripped. Even if you remove knox from the bootloader, once custom recovery is installed, I'm pretty sure you're going to trip the bit anyway.
He even states so in the thread here:
http://forum.xda-developers.com/showpost.php?p=51828541&postcount=102
---------- Post added at 02:25 PM ---------- Previous post was at 02:17 PM ----------
And FYI, no one to my knowledge has ever hard bricked a Sprint Galaxy S5 phone. The only real issue at the moment is once you flash the OD3 Lollipop firmware or newer (currently OF6 I think) or take the OTA update, flashing any firmware older than OD3 is blocked.
Hi guys! with all due respect my question might be dumb but here it goes, after flashing custom recovery TWRP on my S7 the phone seems to stop working like google playstore keep on hanging along with touchwiz blank page nothing on the main screen. To fix this I have to flash back to stock rom from Odin with the correct updated firmware and Odin3 v3.12.3. All this happens after I wanted to sell my phone to a new buyer, he installed knox and failed so insisted to return the phone back to me. After I got it decided to root the phone again then that happen and my knox counter trip is 0x030? Does this means anything? Because before it was 0x1 ?
one more question can I rooted with Magisk and Super Su both is available on my S7? Maybe its a dumb question too to cheers
hmm nobody gonna give me a few tips on how to solve this?
The Knox flag is still void. Mine is the same. Seems indicate different levels of tripped, or maybe changes depending on if a full custom ROM is installed. SuperSU and magisk do work, and work best when flashed through TWRP. It's tricky to get root to work with encryption though, so most people just disable encryption and format data.