FORUMS

CloudPlayer: DIY HiFi Music Streaming Solution

In our Helpful Guide to Music Streaming Services, we mentioned several different services … more

Optimize Battery Life with This Useful App

Battery life is an important aspect of your smartphone, especially if you use it for more … more

The OnePlus 2 & The Year of Smartphone Compromises

We are very close to entering the last third of 2015, and we have now seen many of … more

OnePlus 2 Teardown, Major Android Vulnerability – XDA TV

The OnePlus 2 has been officially released. That and much more news is … more

[Q] Can't Get Rid Of Custom System Status

58 posts
Thanks Meter: 6
 
By GoremanX, Member on 28th March 2014, 05:54 AM
Post Reply Subscribe to Thread Email Thread
I rooted once upon a time using Kingo Root. Worked fine, love being rooted, been doing it for years. But as everyone knows, the GPS signal is really crap on these phones. Mine keeps cutting out randomly.

Lo and behold! KitKat is now available! And among the changes AT&T is bragging about is improved GPS performance. As much as I enjoy being rooted, I need a working GPS a lot more. So I tried installing the OTA update... but it failed. I assume because the device status is listed as "Custom".

So I used Triangle Away, did a full unroot using SuperSU, rebooted... and it still says "Custom". There didn't used to be an open padlock during boot while I was rooted, but now there is, along with the word "Custom". Check the Odin mode, and sure enough it says the system status is "Custom". However Knox flag is still 0x0, and it states I'm running the Samsung Official binary. I've never flashed a ROM on this phone, all I did was root it.

Re-rooted, installed Triangle Away again. It states my system status is "Official" and the flash counter is at 0. However whenever I check the Device status in settings, it always says "Custom". There doesn't appear to be any way to get it back to "Official". Sometimes I can get it to say "Official" for a single boot, but then it always reverts back to "Custom" within a couple minutes whether the phone is rooted or not.

What am I doing wrong?
 
 
28th March 2014, 06:12 AM |#2  
Senior Member
Flag San Francisco
Thanks Meter: 25
 
More
After unroot, you need to do a factory reset, then boot into your recovery, wipe cache, reboot your phone few times the pad lock and custom logo should go away. I am not sure about the "Device status in settings" showing custom, mine always shows official.
28th March 2014, 07:02 AM |#3  
Senior Member
Thanks Meter: 18
 
More
Quote:
Originally Posted by GoremanX

I rooted once upon a time using Kingo Root. Worked fine, love being rooted, been doing it for years. But as everyone knows, the GPS signal is really crap on these phones. Mine keeps cutting out randomly.

Lo and behold! KitKat is now available! And among the changes AT&T is bragging about is improved GPS performance. As much as I enjoy being rooted, I need a working GPS a lot more. So I tried installing the OTA update... but it failed. I assume because the device status is listed as "Custom".

So I used Triangle Away, did a full unroot using SuperSU, rebooted... and it still says "Custom". There didn't used to be an open padlock during boot while I was rooted, but now there is, along with the word "Custom". Check the Odin mode, and sure enough it says the system status is "Custom". However Knox flag is still 0x0, and it states I'm running the Samsung Official binary. I've never flashed a ROM on this phone, all I did was root it.

Re-rooted, installed Triangle Away again. It states my system status is "Official" and the flash counter is at 0. However whenever I check the Device status in settings, it always says "Custom". There doesn't appear to be any way to get it back to "Official". Sometimes I can get it to say "Official" for a single boot, but then it always reverts back to "Custom" within a couple minutes whether the phone is rooted or not.

What am I doing wrong?

Did you delete system (AT&T) apps?
28th March 2014, 02:29 PM |#4  
OP Member
Thanks Meter: 6
 
More
Quote:
Originally Posted by coolmingli

After unroot, you need to do a factory reset, then boot into your recovery, wipe cache, reboot your phone few times the pad lock and custom logo should go away. I am not sure about the "Device status in settings" showing custom, mine always shows official.

Yep, I did all of that. Exact procedure:

- Reset flash counter using triangle away
- full unroot using SuperSU
- reboot immediately into Odin mode (system status says "Official")
- reboot immediately into recovery, do a factory reset
- reboot immediately into Odin mode (system status still says "Official")
- reboot immediately into recovery, do ANOTHER factory reset (because I'm anal that way)
- reboot immediately into Odin mode, (system status STILL says "Official")
- reboot normally, go through normal first-time setup, go into settings, check Device status... it says "Custom"
- reboot into Odin mode, system status now says "Custom"
- reboot normally, stupid open padlock is there again with the word "Custom"
- countless reboots later, it still says "Custom"

Quote:
Originally Posted by serpent2005

Did you delete system (AT&T) apps?

Nope, none. They're all still there. Like I said, I'm still running the bone stock image, never flashed a ROM, and I never edited the image. I only use root for things like GMD S-pen control, Titanium Backup, and FS Trim.

What's really annoying is that damn open padlock is never there while the system really IS modified, it only shows up when I unroot and everything is back to stock. I call it irony.

Would region lock be affecting this? I disabled the region lock many moons ago using RegionLock Away. Does that survive after a factory reset, and would it cause my device status to show up as Custom?
Last edited by GoremanX; 28th March 2014 at 03:00 PM.
28th March 2014, 04:56 PM |#5  
OP Member
Thanks Meter: 6
 
More
Nope, restoring the region lock did not fix the problem. It continues to revert to "Custom" Device status no matter what I try. This is infuriating.
28th March 2014, 05:05 PM |#6  
the2rrell's Avatar
Senior Member
Thanks Meter: 616
 
More
Quote:
Originally Posted by GoremanX

Nope, restoring the region lock did not fix the problem. It continues to revert to "Custom" Device status no matter what I try. This is infuriating.

This is what you need to do

http://forum.xda-developers.com/show....php?t=2559715

it fully returns your phone to stock. and you can get your OTAs again at that point.
28th March 2014, 05:07 PM |#7  
OP Member
Thanks Meter: 6
 
More
Quote:
Originally Posted by the2rrell

This is what you need to do

http://forum.xda-developers.com/show....php?t=2559715

it fully returns your phone to stock. and you can get your OTAs again at that point.

I tried that too. Didn't work. Still says "Custom". However, part of those instructions failed for me, the Heimdall image upload did not work at all. Never could figure out why.
28th March 2014, 05:09 PM |#8  
the2rrell's Avatar
Senior Member
Thanks Meter: 616
 
More
Quote:
Originally Posted by GoremanX

I tried that too. Didn't work. Still says "Custom". However, part of those instructions failed for me, the Heimdall image upload did not work at all. Never could figure out why.

they work, it maybe your PC, i know Heimdall can be a bugger at times. It DOES work though. have you tried another PC if that is an option.
28th March 2014, 06:46 PM |#9  
OP Member
Thanks Meter: 6
 
More
Quote:
Originally Posted by the2rrell

they work, it maybe your PC, i know Heimdall can be a bugger at times. It DOES work though. have you tried another PC if that is an option.

I just tried it from my laptop, same result. The MI9_fix.img.ext4 file refuses to upload to my device. The instructions state it should fail at 95%, but it always fails immediately. I tried downloading the file multiple times from different mirrors to make sure I wasn't getting a bad one. The result is always:

Uploading SYSTEM
0%
ERROR: Failed to send file part packet!
ERROR: SYSTEM upload failed!
28th March 2014, 06:58 PM |#10  
the2rrell's Avatar
Senior Member
Thanks Meter: 616
 
More
Quote:
Originally Posted by GoremanX

I just tried it from my laptop, same result. The MI9_fix.img.ext4 file refuses to upload to my device. The instructions state it should fail at 95%, but it always fails immediately. I tried downloading the file multiple times from different mirrors to make sure I wasn't getting a bad one. The result is always:

Uploading SYSTEM
0%
ERROR: Failed to send file part packet!
ERROR: SYSTEM upload failed!


you have all the drivers and everything loaded up?

thats odd.
28th March 2014, 06:59 PM |#11  
OP Member
Thanks Meter: 6
 
More
Yep, everything called for in the instructions. I get the same result every time.

Did I mention how infuriating this is?

Read More
Post Reply Subscribe to Thread
Previous Thread Next Thread
Thread Tools Search this Thread
Search this Thread:

Advanced Search
Display Modes