Develop Bugs

[Q] BEST method for restoring FULL FACTORY STOCK?

I attempted to restore my fiance's S3 to full factory stock about a month ago now, after I received a prompt for the ~82MB OTA update, and she didn't... She was tired of me taking her phone and keeping it out of her hot little hands whilst I made nandroids and flashed the latest updates to BlazerROM, and she didn't have a problem with stock ROM, so I figured I'd put it back for her.
Well, I did, and I KNOW I left CWRecovery in, and not sure if I left root or not, but she STILL has not received the OTA update which still bugs me... So I need to know what is the BEST method for FULL STOCK RECOVERY? I don't want her missing out when the Jelly Bean official drops, and I may flash mine back when it hits just to test it out...
I found this: http://forum.xda-developers.com/showthread.php?t=1935973
Which directed me to QBKing's site, but also warned that the video was now somewhat dated...
Am I assume that by saving her text messages and contacts, and flashing the ODIN .tar listed on this page: http://forum.xda-developers.com/showthread.php?t=1919919 and just letting her re-install her apps, is an effective way to return to FULL and UNMODIFIED stock? Should I run Triangle-Away before proceeding? Will this return the device status to Unmodified (or whatever it says) as opposed to "Custom" in the Status page, as it currently shows for her, in case of warranty needs?
Sorry to be "That Guy", but some of the other topics where a bit vague and lacked details, so I figure if we can get something Semi-Detailed and answering most of the big/general questions, perhaps this could serve as a Go-To thread for others who wish to do this...

http://forum.xda-developers.com/showthread.php?t=1904099
Thread youve mentioned above also works fine. If using odin method, run triangle away beforehand. Neither method will wipe data. Depending on the rom you're coming from, it may not be necessary. If you flash without wiping and the rom fails to boot(hangs on glowing samsung logo), go back to recovery and factory reset. Itll boot right up

billard412 said:
http://forum.xda-developers.com/showthread.php?t=1904099
Thread youve mentioned above also works fine. If using odin method, run triangle away beforehand. Neither method will wipe data. Depending on the rom you're coming from, it may not be necessary. If you flash without wiping and the rom fails to boot(hangs on glowing samsung logo), go back to recovery and factory reset. Itll boot right up
Click to expand...
Click to collapse
i cant thumbs-up you hard enough.... thanks for that awesome pile of resources
JUST TO CLARIFY!
On your thread you updated just this morning with the flash-counter reset included, just run in CWR, and all is good, if not, then factory reset, and all is good? Or factory reset, reflash, all is good?
EDIT: FLashed
In download mode;
ODIN MODE
PRODUCT NAME: SPH-L710
CUSTOM BINARY DOWNLOAD: NO
CURRENT BINARY: Samsung Official
SYSTEM STATUS: Custom
QUALCOMM SECUREBOOT: ENABLE (not sure what that one is haven't done more than root with oden and flash)
System status troubles me... ODEN flash, or let it full reboot? I went into download to check before first initial boot after flash. will allow full boot and see what happens...
EDIT 2: Well, android system status shows Normal... Girl woke up and took her phone back, so will check oden later.

Yup the one updated today is just that. Flash and reboot. Youll be 100% stock
The system status in odin will probably fix itself after booting. If not a factory reset should do it

billard412 said:
Yup the one updated today is just that. Flash and reboot. Youll be 100% stock
The system status in odin will probably fix itself after booting. If not a factory reset should do it
Click to expand...
Click to collapse
Seems to have worked. I wish I had money to donate to your wonderful work. Hopefully she'll be receiving prompts for OTA updates for JellyBean shortly... Thanks for also having it up to date. At least I gather it DOES include the ~82MB update she's been missing... Keep up the wonderful work friend!

Glad to hear it. Much appriciated. Now if only the damn thing would be stickied...XD

billard412 said:
Yup the one updated today is just that. Flash and reboot. Youll be 100% stock
The system status in odin will probably fix itself after booting. If not a factory reset should do it
Click to expand...
Click to collapse
billard412 said:
Glad to hear it. Much appriciated. Now if only the damn thing would be stickied...XD
Click to expand...
Click to collapse
Whoever I need to tell, I support sticky'ing the thread.

How to restore device status to "official" Android 4.3

WARNING! THIS WILL ERASE EVERYTHING ON YOUR PHONE!
You also must NOT have any custom recovery or kernel installed as this method requires stock recovery. All bloatware removed prior to unrooting will still be removed! You will have to reinstall the bloatware that was removed and be 100% bone stock in order to get any OTA updates!
I am not liable if you do something wrong and you brick, nor will I be held accountable for any damage done, warranty being voided, ninja zombie aliens taking over, bigfoot, your neighbors lawn catching fire, etc.
Hi everyone, last week I got a brand new At&t Galaxy S3 sgh-i747. I rooted it using towel root and did not do anything else except remove some Google app bloatware (play magazines and play books).
My device status was changed from "official" to "custom" meaning no OTA updates. Here is how I fixed that:
If you installed SuperSU from play store, open it and select the "full unroot" option from the settings menu. It might hang, if so reboot and try again. It should complete the unroot after rebooting.
Next power off and boot into stock recovery (Google can help you with getting into recovery if you don't know how). Once you boot into recovery, select wipe cache, then select factory data reset. Recovery may give an error upon exiting with Andy the Android slumped over on his back, this is okay. Reboot and the phone will hang at the AT&T logo for a few minutes. Once booted up, your device status should say official and be unrooted back to 100% stock. You can now get OTA updates!
No ODIN needed! I just happen to try this and it worked. Not sure if it works on 4.4 or not, but it should. It should also work on the Galaxy S4, but has not been tested or confirmed.

How do you boot into Stock Recovery on a SGH-I747M ?

Nick9drs said:
How do you boot into Stock Recovery on a SGH-I747M ?
Click to expand...
Click to collapse
http://forum.xda-developers.com/wiki/Samsung_Galaxy_S_III/SGH-I747#Recovery_Mode

can't update to 4.4.2 OTA

Hello, my phone recently notified me that a 4.4.2 android OTA update is available (i have a AT&T SGH-i747) however once it reboots, it will get to about 29% complete, then i get the "Update failed" message, and it reboots back into android (4.3) and i was wondering how i could get it to work?
(i'm using stock rom, i've NEVER flashed anything on it before, only thing i've done is root it to use titanium backup, however i used the saferoot thing so as to not flip the knox security stuff)

You need to unroot.

audit13 said:
You need to unroot.
Click to expand...
Click to collapse
do i have to do something special to do that? or can i just click the "Full unroot" button in the SuperSU settings tab to unroot my phone

You also need stock recovery and, preferably, all of the ATT apps on your phone. I have read that removing too many ATT apps will prevent the OTA update from completing.
I have never tried removing root that way so I cannot comment.
You should also make note of the fact that it is possible to have something go wrong during the OTA process which may result in the loss of your data. I recommend at least backing everything up to your external SD card and removing the SD card during the OTA update process.

like i said, i only rooted to use titanium backup to restore a backup for a game save, that's all i've ever done (so if that undid stock recovery, or removed AT&T apps without me telling it to, then how would i fix that)

In that case, just unroot and then run the OTA update. Titanium backup would not alter the recovery or remove apps.

well, i have 5 hours to wait before doing so, after unrooting (using the saferoot unroot.bat file, then using supersu's unroot after that to finish the process as the saferoot program said to do) i went to click check for updates, and instead got "Your device is running the latest version" and "you may check again in 5 Hours 0 Minuties" which i'm assuming is because it failed last night when i tried to update it?

So everything is completely stock? Does it say custom on the download screen or anywhere in the About section of the phone.

audit13 said:
So everything is completely stock? Does it say custom on the download screen or anywhere in the About section of the phone.
Click to expand...
Click to collapse
nope, doesn't say custom anywhere on the about phone screen, will check the download mode now

logoster said:
nope, doesn't say custom anywhere on the about phone screen, will check the download mode now
Click to expand...
Click to collapse
sorry for double post, just checked download mode, says i'm completely stock and official
also thought i'd mention that the check again later timer is going down, it's at 4 hrs and 3 minutes

You could also try booting into recovery and wiping cache and Dalvik. Don't wipe data.

nope, still has a timer, but it's fine as it is going down, i have about 2hrs and 47 Mins left according to it

Sorry for double post again, but timer finished, and update worked flawlessly, so unrooting did work, thanks
Sent from my SAMSUNG-SGH-I747 using XDA Free mobile app

[Q] Unroot

Its been a while since ive been on XDA so dont kill me lol.
I have a Galaxy Tab S 10.5 SM-T800 that i rooted back in december. Well i have had horrible battery issues all along and now its cutting off without notice. I have tried to take the batter out and what not but nothing is working.
SOOOOO...I am going to send it back to Sammy to have them fix it. My question is what is the best method to unroot this thing? i currently and rooted stock lollipop with TWRP recovery. Im guessing i need to be unrooted and back to stock recovery before i send it. Any suggestions?

cwhitney24 said:
Its been a while since ive been on XDA so dont kill me lol.
I have a Galaxy Tab S 10.5 SM-T800 that i rooted back in december. Well i have had horrible battery issues all along and now its cutting off without notice. I have tried to take the batter out and what not but nothing is working.
SOOOOO...I am going to send it back to Sammy to have them fix it. My question is what is the best method to unroot this thing? i currently and rooted stock lollipop with TWRP recovery. Im guessing i need to be unrooted and back to stock recovery before i send it. Any suggestions?
Click to expand...
Click to collapse
Flash official cf-autroot then open the supersu app and select Full unroot from settings. Done.

1. Back up any data from internal storage
2. Device settings > security > re-activation lock > disabled
3. Boot into TWRP recovery and format :
a) system
b) data
c) cache
d) dalvik-cache (advanced)
e) factory-reset for good measure
4. Re-boot directly into DOWNLOAD MODE from recovery menu
5. Flash official firmware package with Odin
All partitions will be clean and fully stock. Knox warranty void 0x1

Will Samsung still take it back after you trip Knox? Curious as to how this turns out for you as I am having the exact same issues with mine lately. Let us know what happens.

Not "rooted" still shows Custom, fixing others "resets"

I have a tmo s4 (m919) that had been previously rooted (by someone else). Root check says it's not "rooted" but it still says Custom in status. It's running 4.4.2 and won't update because of this. When I try to wipe the cache it gives me an error. The binary counter may have not been reset when the previous owners "factory reset" it. I only know all this garbage because i did a little research and learned a little lesson in what to look for next time. ..ugh. Sooooo....I'm looking to return it to stock/warrantable condition and be able to update. I have never messed with any rooting before but am willing to learn. The reason for the post is that the method for fixing this may be different than the general guides. Thank you for your time, it is most appreciated!

The Glue said:
I have a tmo s4 (m919) that had been previously rooted (by someone else). Root check says it's not "rooted" but it still says Custom in status. It's running 4.4.2 and won't update because of this. When I try to wipe the cache it gives me an error. The binary counter may have not been reset when the previous owners "factory reset" it. I only know all this garbage because i did a little research and learned a little lesson in what to look for next time. ..ugh. Sooooo....I'm looking to return it to stock/warrantable condition and be able to update. I have never messed with any rooting before but am willing to learn. The reason for the post is that the method for fixing this may be different than the general guides. Thank you for your time, it is most appreciated!
Click to expand...
Click to collapse
Triangle away by chainfire

Can i use triangle even if the unit has been reset already to "stock" and not running whatever it was running?

Have you tried to factory reset? Warranty is gone already you can't fix it. What I would do is download the latest firmware, flash it with Odin or update with samsung smart switch, then factory reset. After that it should be back to official status
Sent from my SM-G920T using Tapatalk

We did a factory reset when we got it. My understanding is that Triangle Away solves the modification counter, but needs to be done before unrooting it. I had no knowledge of this issue at the time so I am wondering if it would need to be rerooted to use the TA before using Odin to reflash it to stock.

The Glue said:
We did a factory reset when we got it. My understanding is that Triangle Away solves the modification counter, but needs to be done before unrooting it. I had no knowledge of this issue at the time so I am wondering if it would need to be rerooted to use the TA before using Odin to reflash it to stock.
Click to expand...
Click to collapse
I've never had to use triangle away. Probably the user before you modified something and didn't change it back, that's why it still shows modified. Reason why I suggested to flash stock firmware then factory reset. But yeah if you want you have to use triangle away when you have root access
Sent from my SM-G920T using Tapatalk

The Glue said:
We did a factory reset when we got it. My understanding is that Triangle Away solves the modification counter, but needs to be done before unrooting it. I had no knowledge of this issue at the time so I am wondering if it would need to be rerooted to use the TA before using Odin to reflash it to stock.
Click to expand...
Click to collapse
I agree with @serio22, Odin stock, then reset. Triangle was just a bit quicker way then DL firmwares, losing data/apps etc.

OK, what I'm understanding is:
- Warrantable condition is lost even with the modification counter being reset. Obvious reason I'm guessing, but why?
- Downloading current firmware, installing with Odin/Smart Switch, and then factory resetting will reset the mod counter without using Triangle. I don't care about app loss since the user (my teen boy's first phone) hasn't used it yet or even knows of its existence (better be good, ya never know what Santa's got up his sleeve that you'll never see otherwise) so nothing to lose.
Sound about right?

The Glue said:
OK, what I'm understanding is:
- Warrantable condition is lost even with the modification counter being reset. Obvious reason I'm guessing, but why?
- Downloading current firmware, installing with Odin/Smart Switch, and then factory resetting will reset the mod counter without using Triangle. I don't care about app loss since the user (my teen boy's first phone) hasn't used it yet or even knows of its existence (better be good, ya never know what Santa's got up his sleeve that you'll never see otherwise) so nothing to lose.
Sound about right?
Click to expand...
Click to collapse
Yes. Just Odin stock and reset. Check your Knox status in your bootloader just to be sure its been voided or not. Power off and then hold power and vol down buttons to get into bootloader. Look for Knox 0x0 or if void, 0x1.