[GUIDE]How to be rooted, retain zero custom binary download count and official status

Search This thread

mossy1963

Senior Member
Nov 28, 2010
514
143
Cardiff
How to Guide: flash any rom you want, be rooted, retain zero custom binary download count, official/normal status and save your warranty – busting the myth

Testimony that this works! > http://xdaforums.com/showpost.php?p=33260545&postcount=29

There is a lot of misinformation floating around these forums saying things like “if you root your phone your phone status will change from official (download mode) to custom and normal to modified (phone settings, status) and the only way to regain official / normal is to flash stock rom –WRONG.

I’m here to tell you that I’m running unbranded DLJ4 rooted with zero flash count and official status (normal – not modified in phone settings, status). It just takes a bit of fiddling about – but not a lot and it does involve a reset so a backup is required – use titanium because a nandroid restore will over flash your good work, obviously.

The only possible reason to flash stock FW after the process is if you want its original state to return to Samsung under warranty or upgrade OTA or via Kies - it is not necessary to flash stock to get official status.

First of all this is not all my work and I’m not claiming the credit, but I did not find the solution on XDA, hence my post here. Any credits go to Jayce Ooi’s paradise web site (JayceOoi.com – google it). I have edited it a bit to relect my own experience.

Prerequisites: Triangle Away, Mobile Odin (doesn’t increase flash count like PC version), Rooted Rom of your choice, cwm recovery.

Step by Step Guide – follow to the letter, especially the remove battery bits

Steps 1....11 basically preamble to check status

1.Power off Samsung Galaxy S3.
2.Press and hold down Volume Down + Home + Power buttons at the same time to enter download mode.
3.Press Volume Up button when warning prompt.
4.Odin download mode will be loaded.
5.Note your custom binary download counter number and system status.
6.Long press Power button to restart Samsung Galaxy S3.
7.Remove back cover after Android OS loaded.
8.Go to Settings.
9.Select About device.
10.Select Status ~ show status of battery, network, and other information.
11.Device status should be Modified.

The business starts here...

12.Launch Triangle Away.
13.Grant it root access when prompted.
14.Download latest update when prompted.
15.Double check counter number at Current status is the same as Odin Download Mode.
16.Select Reset flash counter if everything is correct.
17.Follow Triangle Away instructions then.
18.Note – It will boot into Triangle Away boot mode.
19.IMPORTANT – Pull out battery immediately after rebooting starts.
20.Replace battery.
21.Power off Samsung Galaxy S3.
22.Press and hold Volume Up + Home + Power buttons at the same time to enter recovery mode.
23.Release all buttons when you see SGS3 Logo.
24.ClockworkMod Recovery will be loaded.
25.Go to wipe data/factory reset with Volume Up / Down buttons.
26.Select it with Power (or Home) button.
27.Then select Yes — delete all user data.
28.Select wipe cache partition.
29.Then select Yes — Wipe cache.
30.After wiping data and cache, pull out battery.
31.Put battery and back cover back.
32.Press and hold down Volume Down + Home + Power buttons at the same time to enter download mode again.
33.Press Volume Up button when warning prompt.
34.In Odin download mode Custom binary download should be “No”, current binary to Samsung “Official”.
35.Long press power key to reboot phone
36.Go to settings, about device, status, device status will read “Normal”.

OK, now you have a rooted rom of your choice with zero flash count and official status.

From here you have choices, either:
•Do nothing – happily use your “clean” rooted phone as it is
•flash other roms of your choice, stock or custom, using mobile Odin without changing flash counter or status, or
•Flash a stock rom with mobile odin, again retaining zero flash count and normal status from which you can perform OTA updates or Kies updates, return phone to Samsung under wararanty if necessary, whatever.

Like I said above, I couldn’t find comprehensive and correct instructions elsewhere on XDA – apologies if I’m wrong. However there is a lot of BS flying around which I couldn’t ignore hence this guide.

I’ll repeat, main credit goes to Jayce Ooi, but happy if I’ve helped - hopefully you'll appreciate this guide.
 
Last edited:

sorg

Senior Member
Sep 5, 2006
1,058
1,136
台灣
For me, it looks like:
- syscope process doesn't check ROM with every boot, but only after some event happened. This looks weird, because it looks that syscope always scan background processes at every boot and changes status to "Modified" if it finds any non-white listed root process, su binary or adb in root mode.
- you clear somehow trigger to let syscope thinks it still on the same already checked ROM.

This instruction looks too obfuscated. I believe steps count can be reduced significantly.

I'm not going to repeat this whole sequence because i have too much apps preinstalled and my ROM is heavily modified, so there is no way syscope will like it :) :)

I think, system state will change to modified if you will start to use more applications requiring root access. Just by some strange bug in syscope, exactly in your case and set of apps your ROM still not triggered "modified" flag.
 

mnitstanley

Senior Member
Oct 24, 2012
103
16
Thanks for the good will and instructions. However, I will request you to post a video to avoid any gap between what we read and what you meant. Also, "TO SEE IS TO BELIEVE" :thumbup:

Sent from my GT-I9300
 

mossy1963

Senior Member
Nov 28, 2010
514
143
Cardiff
@sort
There are not that many steps. It's actually quite straight forward, I've simply tried to break it down and make it as simple as I can for people less experienced who really want to do ota upgrades as well as the more experienced.

Sent from my GT-I9300 using xda app-developers app
 

mossy1963

Senior Member
Nov 28, 2010
514
143
Cardiff
Thanks for the good will and instructions. However, I will request you to post a video to avoid any gap between what we read and what you meant. Also, "TO SEE IS TO BELIEVE" :thumbup:

Sent from my GT-I9300

There is a video in jayce ooi's web page.
Actually...in this case, doing its believing. Suck it and see.

To be honest I really don't care whether people do. I just couldn't sit here any longer and ignore the incorrect advice when my own research and experimentation has proved something different.

This SHOULD be a great help to people. I'm in work at the moment (unlike some of the serial posters round here apparently) so I won't be able to respond to every question very quickly. This is a developer community, I'd expect people to try for themselves. But check my profile...I wouldn't make something like this up.
Best of luck to anyone who has a go...it's not that tricky.

Sent from my GT-I9300 using xda app-developers app
 

slaphead20

Senior Member
Feb 13, 2011
11,309
4,718
Out there somewhere
interesting, I genuinely would give this a try if I needed it, but I don't! But it is a question that I've asked myself a few times.

On another note, it's easy to judge "serial posters".......but maybe check their profile before doing so ;)
 

mossy1963

Senior Member
Nov 28, 2010
514
143
Cardiff
interesting, I genuinely would give this a try if I needed it, but I don't! But it is a question that I've asked myself a few times.

On another note, it's easy to judge "serial posters".......but maybe check their profile before doing so ;)

Haha...agreed. That is very naughty of me (slaps back of hand)

Sent from my GT-I9300 using xda app-developers app
 
  • Like
Reactions: slaphead20

JJEgan

Senior Member
Oct 24, 2010
30,509
5,923
Samsung Galaxy Note 3
Some cereal posters earn good money sitting in front of a computer .


Of course if Samsung service centres actually follow the instructions from Samsung in regard to rooted phones and actually look for rooted applications warranty will be invalid anyway . However not many of them actually bother to check to deep in that regards .

Samsung Notice GSM 10-71 Abnormal System Change Warranty Guide .


jje
 

carrd

Senior Member
Oct 10, 2012
249
50
Has anyone tried to see if the SKY GO app in the uk works after this? I am sure I read somewhere that the app checks the modified atatus so if this method allows you to keep root but with a device status of Normal. This should work right?
 

mossy1963

Senior Member
Nov 28, 2010
514
143
Cardiff
Has anyone tried to see if the SKY GO app in the uk works after this? I am sure I read somewhere that the app checks the modified atatus so if this method allows you to keep root but with a device status of Normal. This should work right?

Sky go does not work on jellybean yet.it says so quite clearly on play market if you want to check it out.

Sent from my GT-I9300 using xda app-developers app
 

mossy1963

Senior Member
Nov 28, 2010
514
143
Cardiff
@jj. :) I was being cheeky regarding serial posters, apologies if I offended anyone.

It's a given that anyone who uses this method and flashes a stock for return to Samsung will not have any tell-tale apps

Ps. "Cereal posters" conjures up all kinds of wonderful images :)

Sent from my GT-I9300 using xda app-developers app
 
Last edited:

slaphead20

Senior Member
Feb 13, 2011
11,309
4,718
Out there somewhere
@jj. :) I was being cheeky regarding serial posters, apologies if I offended anyone.

It's a given that anyone who uses this method and flashes a stock for return to Samsung will not have any tell-tale apps

Ps. "Cereal posters" conjures up all kinds of wonderful images :)

Sent from my GT-I9300 using xda app-developers app

The secrets out... jjegan.... international man of mystery is, in fact, a coco-pop! :D
 

carrd

Senior Member
Oct 10, 2012
249
50
I have spent my lunch time researching this and from what I can gather even if this works there is a background service that runs periodically that checks if device has been modified and set status to modified. so even if this process does work it will revert back to modified at some point.

Does anyone know more about his backgorund service? If so could it be disabled?
 

slaphead20

Senior Member
Feb 13, 2011
11,309
4,718
Out there somewhere
I have spent my lunch time researching this and from what I can gather even if this works there is a background service that runs periodically that checks if device has been modified and set status to modified. so even if this process does work it will revert back to modified at some point.

Does anyone know more about his backgorund service? If so could it be disabled?

I think it is syscope, earlier someone mentioned it, apparently it scans at boot, wether this is true or not, I have no idea
 
  • Like
Reactions: carrd

mossy1963

Senior Member
Nov 28, 2010
514
143
Cardiff
I have spent my lunch time researching this and from what I can gather even if this works there is a background service that runs periodically that checks if device has been modified and set status to modified. so even if this process does work it will revert back to modified at some point.

Does anyone know more about his backgorund service? If so could it be disabled?

The difference is I have done it...still unmodified and have been for days...another urban myth?

Sent from my GT-I9300 using xda app-developers app
 

Top Liked Posts

  • There are no posts matching your filters.
  • 30
    How to Guide: flash any rom you want, be rooted, retain zero custom binary download count, official/normal status and save your warranty – busting the myth

    Testimony that this works! > http://xdaforums.com/showpost.php?p=33260545&postcount=29

    There is a lot of misinformation floating around these forums saying things like “if you root your phone your phone status will change from official (download mode) to custom and normal to modified (phone settings, status) and the only way to regain official / normal is to flash stock rom –WRONG.

    I’m here to tell you that I’m running unbranded DLJ4 rooted with zero flash count and official status (normal – not modified in phone settings, status). It just takes a bit of fiddling about – but not a lot and it does involve a reset so a backup is required – use titanium because a nandroid restore will over flash your good work, obviously.

    The only possible reason to flash stock FW after the process is if you want its original state to return to Samsung under warranty or upgrade OTA or via Kies - it is not necessary to flash stock to get official status.

    First of all this is not all my work and I’m not claiming the credit, but I did not find the solution on XDA, hence my post here. Any credits go to Jayce Ooi’s paradise web site (JayceOoi.com – google it). I have edited it a bit to relect my own experience.

    Prerequisites: Triangle Away, Mobile Odin (doesn’t increase flash count like PC version), Rooted Rom of your choice, cwm recovery.

    Step by Step Guide – follow to the letter, especially the remove battery bits

    Steps 1....11 basically preamble to check status

    1.Power off Samsung Galaxy S3.
    2.Press and hold down Volume Down + Home + Power buttons at the same time to enter download mode.
    3.Press Volume Up button when warning prompt.
    4.Odin download mode will be loaded.
    5.Note your custom binary download counter number and system status.
    6.Long press Power button to restart Samsung Galaxy S3.
    7.Remove back cover after Android OS loaded.
    8.Go to Settings.
    9.Select About device.
    10.Select Status ~ show status of battery, network, and other information.
    11.Device status should be Modified.

    The business starts here...

    12.Launch Triangle Away.
    13.Grant it root access when prompted.
    14.Download latest update when prompted.
    15.Double check counter number at Current status is the same as Odin Download Mode.
    16.Select Reset flash counter if everything is correct.
    17.Follow Triangle Away instructions then.
    18.Note – It will boot into Triangle Away boot mode.
    19.IMPORTANT – Pull out battery immediately after rebooting starts.
    20.Replace battery.
    21.Power off Samsung Galaxy S3.
    22.Press and hold Volume Up + Home + Power buttons at the same time to enter recovery mode.
    23.Release all buttons when you see SGS3 Logo.
    24.ClockworkMod Recovery will be loaded.
    25.Go to wipe data/factory reset with Volume Up / Down buttons.
    26.Select it with Power (or Home) button.
    27.Then select Yes — delete all user data.
    28.Select wipe cache partition.
    29.Then select Yes — Wipe cache.
    30.After wiping data and cache, pull out battery.
    31.Put battery and back cover back.
    32.Press and hold down Volume Down + Home + Power buttons at the same time to enter download mode again.
    33.Press Volume Up button when warning prompt.
    34.In Odin download mode Custom binary download should be “No”, current binary to Samsung “Official”.
    35.Long press power key to reboot phone
    36.Go to settings, about device, status, device status will read “Normal”.

    OK, now you have a rooted rom of your choice with zero flash count and official status.

    From here you have choices, either:
    •Do nothing – happily use your “clean” rooted phone as it is
    •flash other roms of your choice, stock or custom, using mobile Odin without changing flash counter or status, or
    •Flash a stock rom with mobile odin, again retaining zero flash count and normal status from which you can perform OTA updates or Kies updates, return phone to Samsung under wararanty if necessary, whatever.

    Like I said above, I couldn’t find comprehensive and correct instructions elsewhere on XDA – apologies if I’m wrong. However there is a lot of BS flying around which I couldn’t ignore hence this guide.

    I’ll repeat, main credit goes to Jayce Ooi, but happy if I’ve helped - hopefully you'll appreciate this guide.
    2
    For me, it looks like:
    - syscope process doesn't check ROM with every boot, but only after some event happened. This looks weird, because it looks that syscope always scan background processes at every boot and changes status to "Modified" if it finds any non-white listed root process, su binary or adb in root mode.
    - you clear somehow trigger to let syscope thinks it still on the same already checked ROM.

    This instruction looks too obfuscated. I believe steps count can be reduced significantly.

    I'm not going to repeat this whole sequence because i have too much apps preinstalled and my ROM is heavily modified, so there is no way syscope will like it :) :)

    I think, system state will change to modified if you will start to use more applications requiring root access. Just by some strange bug in syscope, exactly in your case and set of apps your ROM still not triggered "modified" flag.
    1
    interesting, I genuinely would give this a try if I needed it, but I don't! But it is a question that I've asked myself a few times.

    On another note, it's easy to judge "serial posters".......but maybe check their profile before doing so ;)

    Haha...agreed. That is very naughty of me (slaps back of hand)

    Sent from my GT-I9300 using xda app-developers app
    1
    I have spent my lunch time researching this and from what I can gather even if this works there is a background service that runs periodically that checks if device has been modified and set status to modified. so even if this process does work it will revert back to modified at some point.

    Does anyone know more about his backgorund service? If so could it be disabled?

    I think it is syscope, earlier someone mentioned it, apparently it scans at boot, wether this is true or not, I have no idea
    1
    A little experiment on custom rooted rom for research purpose only .

    Followed all stages boot to OS reboot device status is normal with factory restored custom rom .

    to recovery and using a Nandroid backup restored Data Only

    Boot up in system status it scans Device Status and shows modified now .

    Remove syscope from custom rom and flash .


    Boot and on status now says modified >> thats with syscope removed .

    jje