Related
I really don't understand this phone. I've been on a quest of 2 weeks to be rooted and on official status, finally i gave up everything because i was not able to have both. Finally i flashed factory rom through odin, formated a couple of time the phone, and i got back official status. I much rather gave up a few rooting benefits then OTAs, at least until they fix the phone's problems.
Well, this morning, i wake up, and that DAMN custom status is back....WHY????????? I'm not rooted, i'm 100% stock, i checked with rootchecker and my phone doesnt have root....then why does that damn status keep coming back??? There is obviously something else that triggers it......man i'm so deperate! Please help!
polish_pat said:
I really don't understand this phone. I've been on a quest of 2 weeks to be rooted and on official status, finally i gave up everything because i was not able to have both. Finally i flashed factory rom through odin, formated a couple of time the phone, and i got back official status. I much rather gave up a few rooting benefits then OTAs, at least until they fix the phone's problems.
Well, this morning, i wake up, and that DAMN custom status is back....WHY????????? I'm not rooted, i'm 100% stock, i checked with rootchecker and my phone doesnt have root....then why does that damn status keep coming back??? There is obviously something else that triggers it......man i'm so deperate! Please help!
Click to expand...
Click to collapse
It's really not as big of a deal as you are making it. The way I see it you have 2 choices.
1. Exchange the phone for another (that might do the same thing)
2. Ignore it.
Just like every other Galaxy phone out there (you remember the skyrockets, right?) not all of them react the same way. Some get custom, some do not. Others switch back and forth.
I've noticed you have made many posts about this same thing. If someone hasn't provided a concrete answer that has worked for you by now it just doesn't exist yet. No matter how frustrated you are over it, making new posts about it are not going to change anything.
Its up to you if you keep wanting to post about it (I'm not complaining about it), I just don't think it's going to get you any more information at this point than what already has been said. Maybe I am wrong and someone will tell you exactly what to do to make it "official", but I haven't seen anything yet.
Good luck and try not to let it get to you so much.
euhhh no, they are not about the same thing, one was about retaining officiel while rooted, and now that i've given up on that, i still have a custom status, the reson why i dont report there is becuase poeple have seen the thread and will not go back, so in order to attract new poster i create a new thread. And no, i dont want to ignore anything because i want OTAs. If you have a problem with that, dont answer
You need to re-root (motochopper method) and then using a file browser such as "root explorer" go to:
/System/Xbin
Once you have navigated to the above path, delete these two files:
"su" and " busybox"
Once you've deleted the two files, uninstall SuperSU and reboot your phone twice.
You'll notice that after the second reboot the "custom" will revert back to "official"
Sent from my SGH-I337M using Tapatalk 2
peoples_flip said:
You need to re-root (motochopper method) and then using a file browser such as "root explorer" go to:
/System/Xbin
Once you have navigated to the above path, delete these two files:
"su" and " busybox"
Once you've deleted the two files, uninstall SuperSU and reboot your phone twice.
You'll notice that after the second reboot the "custom" will revert back to "official"
Sent from my SGH-I337M using Tapatalk 2
Click to expand...
Click to collapse
correct me if i'm wrong but these 2 files, should not even exist if you install a firmware thru odin and format the phone a few times...
I went through what you have, I completed a full stock restore via Odin and these two files I mentioned were still there. Use a file explorer and go to the path I suggested and you'll see them there
Sent from my SGH-I337M using Tapatalk 2
polish_pat said:
correct me if i'm wrong but these 2 files, should not even exist if you install a firmware thru odin and format the phone a few times...
Click to expand...
Click to collapse
I don't believe the current Odin contains a pit...or whatever it is that formats the phone...
So all Odin is going to do is reinstall everything...so replace missing or corrupted files - it will not delete your new files
Formating from the phone itself won't delete everything...its just going to delete your apps, app data, and cache
Therefore doing multiple factory resets and odins likely will not remove all traces of root...someone correct me if I'm wrong but that's what I believe is the case...
Sent from my HTC PH39100 using Tapatalk 2
Is there a reason why it showing custom is a bad thing?
Sent from my SAMSUNG-SGH-I337 using xda premium
XGhozt said:
Is there a reason why it showing custom is a bad thing?
Sent from my SAMSUNG-SGH-I337 using xda premium
Click to expand...
Click to collapse
AT&T software update push or download will not work for your phone if it is showing custom. People like to be getting these stock updates as soon as they are published by the provider, not when some good heart packages a new ROM using them.
polish_pat said:
correct me if i'm wrong but these 2 files, should not even exist if you install a firmware thru odin and format the phone a few times...
Click to expand...
Click to collapse
Good info here, I did this procedure as you described, and yes, official is showing, but you can NOT delete su, it will unroot. I just renamed the 2 files, and root was gone. renamed su back, re-installed su superuser, and reboot, root is back with official status.
Thanks.
TheAxman said:
Good info here, I did this procedure as you described, and yes, official is showing, but you can NOT delete su, it will unroot. I just renamed the 2 files, and root was gone. renamed su back, re-installed su superuser, and reboot, root is back with official status.
Click to expand...
Click to collapse
I tried this procedure and still have custom after 2 reboots. I renamed su and busybox then verified root was gone. Then renamed su back. I guess the part I was confused at was reinstall super user. Do I uninstall then re-install from play store?
Thank you.
EDIT: Followed my thought of uninstalling and re-installing through play store and still get custom.
CAG-man said:
I tried this procedure and still have custom after 2 reboots. I renamed su and busybox then verified root was gone. Then renamed su back. I guess the part I was confused at was reinstall super user. Do I uninstall then re-install from play store?
Thank you.
EDIT: Followed my thought of uninstalling and re-installing through play store and still get custom.
Click to expand...
Click to collapse
Same here
CAG-man said:
I tried this procedure and still have custom after 2 reboots. I renamed su and busybox then verified root was gone. Then renamed su back. I guess the part I was confused at was reinstall super user. Do I uninstall then re-install from play store?
Thank you.
EDIT: Followed my thought of uninstalling and re-installing through play store and still get custom.
Click to expand...
Click to collapse
Correct. the one from the playstore updates the binaries. then uninstall.
---------- Post added at 07:11 PM ---------- Previous post was at 07:10 PM ----------
XGhozt said:
Is there a reason why it showing custom is a bad thing?
Sent from my SAMSUNG-SGH-I337 using xda premium
Click to expand...
Click to collapse
Good answer, why does it matter if it says custom? whats the big deal here. If you are wanting the update, why not just wait until a dev does what they need to do to it, and flash it later. I updated 1 time in a year on my GS3, and never did it again. When a new rom is developed, it usually is a base from the update...so....
Had a posting. Could not delete
Sent from my SAMSUNG-SGH-I337 using xda app-developers app
Did some digging in the forums and I am rooted with OFFICIAL.
This is how to do it. Taken from this thread.
http://forum.xda-developers.com/showthread.php?t=2252248&page=42
Mr. Q said:
Well, you do not have to install the ZIP, but instead, do the following:
- Install SuperSU from the market
- Grant SuperSU root access
- When asked to update su-binary, please do
- Remove SuperUser from your device
- Reboot (I read two reboots are needed to make the icon disappear again.)
Click to expand...
Click to collapse
My process completely.
Remove Busybox from system/xbin (or your busybox backup)
Install SuperSU by Chainfire from playstore.
Open SuperSU and Grant SU root
Update the binary
Say yes to try to remove other root apps. This will remove superuser.
reboot
reboot
On second reboot you will notice the Galaxy S4 logo returns and Official Status has returned.
If it has not returned then some other issue is causing the custom status.
CAG-man said:
Did some digging in the forums and I am rooted with OFFICIAL.
This is how to do it. Taken from this thread.
http://forum.xda-developers.com/showthread.php?t=2252248&page=42
My process completely.
Remove Busybox from system/xbin (or your busybox backup)
Install SuperSU by Chainfire from playstore.
Open SuperSU and Grant SU root
Update the binary
Say yes to try to remove other root apps. This will remove superuser.
reboot
reboot
On second reboot you will notice the Galaxy S4 logo returns and Official Status has returned.
If it has not returned then some other issue is causing the custom status.
Click to expand...
Click to collapse
I was able to get official and root, the problem is it comes back after 2-3 days, please report back on sturday and tell me if its still official, also this logo you are talking about, i never see it because im in canada and my bootloader is unlocked already
EDIT: Ok, so once i was rooted and installed SuperSU and got superuser out, i deleted busybox, i then rebooted ONCE and got official just like that. I also took out SD card because i know this screwed me up last time. I'm happy because i'm rooted and official, but i'm not convinced this will last very long because it has never lasted more than 2 days. I will report back in a few days. Thanks Cagman, you've been very helpful and what you told me to do did the best results for me, i just hope they last
so far so good!!!:fingers-crossed:
polish_pat said:
so far so good!!!:fingers-crossed:
Click to expand...
Click to collapse
Try rebooting a few more times.
For about a week i was getting the custom status every 2nd or 3rd reboot, and then eventually it just went away...
joeybear23 said:
Try rebooting a few more times.
For about a week i was getting the custom status every 2nd or 3rd reboot, and then eventually it just went away...
Click to expand...
Click to collapse
Hahaha, i did it!! earlier this afternoon i sort of challenged my phone by rebooting it constantly, ive rebboted probbaly 20-30 times and its still official, i guess deleting busybox sealed the deal!!
Polish_pat I am glad I was able to help. You are welcome. Congratulations.
Sent from my SAMSUNG-SGH-I337 using xda app-developers app
Ok so my SGH-I337 S4 is rooted using Motochopper and is still stock ROM, just rooted. I did it so I could make Google Wallet work on AT&T, which was successful. Now AT&T has an OTA update that I want. So I will have to unroot. I already have the stock ROM download that I can flash via Odin to unroot. But what will happen to the apps I have installed that require root, like Titanium Backup, ROM manager, etc. Will they automatically be removed or just stop working? Also, has anyone had any experience with the Universal Unroot app? That would sure be easier. But my main question remains: what does Unrooting do to apps that are installed that require root privileges?
Sent from my SGH-I337 using Tapatalk 4
When you user Odin you'll have to do a factory reset or you'll get into a boot loop. So by by apps. Your tibu backup file will still be there, but just in case copy it to your pc before hand. The apps that require root will not work until you re-root.
Hi highly recommend you don't get the ota. Even though it's root able it's very dangerous to do so.
What I will say, if you want the update is to go here http://forum.xda-developers.com/showthread.php?p=43963746 and you will have the benefit of the OTA and not lose the root and custom recovery, and all the app will work! You will not upgrade the bootloader. Once you updated the bootloader is not coming back!
Sent from my SAMSUNG-SGH-I337 using xda app-developers app
I don't understand why you get a boot loop. I once soft bricked a phone and used Odin to flash a md5.tar of a stock ROM. The phone rebooted and I saw my wallpaper and all my apps and data intact. I have seen threads on Unrooting that describe using Odin that way. They all said that doing a factory reset afterword is if you want to delete all your apps and data like if you sell your phone or just want it as it was out of the box
Sent from my SGH-I337 using Tapatalk 4
feetr2c said:
I don't understand why you get a boot loop. I once soft bricked a phone and used Odin to flash a md5.tar of a stock ROM. The phone rebooted and I saw my wallpaper and all my apps and data intact. I have seen threads on Unrooting that describe using Odin that way. They all said that doing a factory reset afterword is if you want to delete all your apps and data like if you sell your phone or just want it as it was out of the box
Sent from my SGH-I337 using Tapatalk 4
Click to expand...
Click to collapse
what device were you using?
That was my S3
Sent from my SGH-I337 using Tapatalk 4
feetr2c said:
That was my S3
Sent from my SGH-I337 using Tapatalk 4
Click to expand...
Click to collapse
thats interesting. were you on stock when you soft bricked it?
many, many...many users commonly have to wipe data/factory reset after flashing stock via odin. sometimes they can get away with just a cache wipe. not often, though.
I had used (can't remember his name) Galaxy S3 Toolkit to root the phone. Interestingly, Root Checker said I was rooted, but Titanium Backup wouldn't install... It said I needed root access... Hmmm.... Later when I went to unroot using the same S3 Toolkit, I did something wrong. The phone would boot but stick at tiny little letters in the upper left of the screen that I *think* said recover. I messaged the developer of the Toolkit and he sent me a link to download the original AT&T stock ROM. He told me how to use Odin and check the PDA box. I did it and it fixed my phone.
Sent from my SGH-I337 using Tapatalk 4
I had rooted my S3 using the Galaxy S3 Toolkit by (can't remember his name). Interestingly enough, Root Checker said I was rooted but yet Titanium Backup wouldn't install... Said it needed root access... Hmmm.... When I tried to unroot using the Toolkit, I did something wrong and the phone rebooted with little Teeny letters in the upper left corner of the screen that I *think* said recover. I messaged the developer of the Toolkit and he sent me a link to the AT&T stock ROM. He told me how to use Odin and check the PDA box. I did and it fixed my phone
Sent from my SGH-I337 using Tapatalk 4
thats why i asked if you were still on stock when you used odin. most users are not, which is ultimately what requires them to factory reset in recovery.
I wonder if universal unroot is trustworthy
Sent from my SGH-I337 using Tapatalk 4
All that would happen to your rooted apps is they wouldn't have root privileges anymore, which means they ultimately won't work as expected. I would recommend uninstalling them before you update. You may also be able to do a full unroot via SuperSU or one of the other superuser apps.
NOTE: Your phone may not update even after unrooting. You may have to do a factory reset first. I don't know why, I'm not a developer. I'm just speaking out of my own experience from the past.
Has anyone tried this method? SuperSU has a full unroot option in its settings. I have read many posts saying it is impossible to unroot at this time.
I did a little searching around and didn't find much. Just suggestions to try it and no one ever reported back if it works or doesn't.
I personally don't have the OTA and have a custom ROM, but i would like to know any confirmation of it working or not working by anyone that has tried it.
Sent from my SAMSUNG-SGH-I337 using XDA Premium 4 mobile app
I did the ota to mf3 and successfully rooted it I then realized that I had like 6gbs missing so in an effort to restore I went into the SU settings and chose the remove root option and it seemed to work I checked with root checker and I no longer had root access I still was unable to restore it just bumps me into Odin mode and I have to boot power+home+volume- then cancel to reboot my phone into working order
But as far as I can tell I have no root
Since I can't restore and try and clear up my missing storage I wanted to take it in and try and get a new one under warranty but I'm afraid to use triangle away so I'm just gonna wait it out until we get a mf3 restore firmware for Odin since my phone works fine for now
Sent from my SAMSUNG-SGH-I337 using xda premium
So that is 1 confirmation for an unroot. Basically hit unroot, it sends the phone to bootloop. Remove battery, put it back, then boot to download mode with power+volume down, then hit volume down again to cancel and reboot to a fully functional phone with no root. If that doesn't work, use power+home+volume down. Anyone else?
Btw,
Don't use triangle away. It flashes a temporary recovery to reset the binary. It will brick you or just fail.
Sent from my SAMSUNG-SGH-I337 using XDA Premium 4 mobile app
graydiggy said:
Has anyone tried this method? SuperSU has a full unroot option in its settings.
Click to expand...
Click to collapse
I fully un-rooted using the method in my post here - http://forum.xda-developers.com/showthread.php?p=44495559 . For me, it just threw the custom-lock icon boot up screen and showed "Custom" status in the "About Phone" menu when using the SuperSU's un-root method.
The problem was busy box. The MF3 root scripts install Busybox files into the /xbin directory, but SuperSU's "full unroot" doesn't touch Busybox's files. Not even any Busybox apps can remove those files.
So delete the busybox files first, then unroot. That is 2 confirmed unroots.
Sent from my SAMSUNG-SGH-I337 using XDA Premium 4 mobile app
ou812bkewl said:
I fully un-rooted using the method in my post here - http://forum.xda-developers.com/showthread.php?p=44495559 . For me, it just threw the custom-lock icon boot up screen and showed "Custom" status in the "About Phone" menu when using the SuperSU's un-root method.
The problem was busy box. The MF3 root scripts install Busybox files into the /xbin directory, but SuperSU's "full unroot" doesn't touch Busybox's files. Not even any Busybox apps can remove those files.
Click to expand...
Click to collapse
graydiggy said:
So delete the busybox files first, then unroot. That is 2 confirmed unroots.
Sent from my SAMSUNG-SGH-I337 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
This method also worked for me as well. Had no problems following the steps.
3 confirmed
Sent from my SAMSUNG-SGH-I337 using XDA Premium 4 mobile app
graydiggy said:
3 confirmed
Sent from my SAMSUNG-SGH-I337 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Good info to know. Thanks graydiggy
I am going to change this to a how to thread later today. Anyone else try it?
Sent from my SAMSUNG-SGH-I337 using XDA Premium 4 mobile app
this may be a stupid question, but if you went through the trouble of rooting after the mf3 update.. why would you want to unroot?
Warranty replacement in case of a hardware issue, testing purposes, also, some people only want a temp root to remove bloat. After that, they don't want root anymore.
Sent from my SAMSUNG-SGH-I337 using XDA Premium 4 mobile app
So to summarize the steps from what I've read on rooting & unrooting MF3:
Root:
Use this guide by jortex: http://forum.xda-developers.com/showthread.php?t=2387577&highlight=mf3
Unroot: http://forum.xda-developers.com/showpost.php?p=44495559&postcount=39
1. Re-root again using the same method you did before for MF3, then:
--a) Reboot, update SuperSU app and it's binary
--b) Reboot again, verify device status is back to"Official"
--c) Reboot again, verifying that, this time, the boot screen is back to normal again
2. Download a file manager app in the Play Store called "Total Commander" and enable "Root functions everywhere" in its settings.
3. Navigate to a folder called "/system/xbin"
4. Delete ONLY files in that folder with the word "busybox" within its filename or symlink path. You should end up with three files left. I did. Two of them are SuperSU related. DO NOT DELETE ANY OF THEM!
5.Open SuperSU and, in its settings, select the "Full un-root" option. Once SuperSU closes, reboot.
Click to expand...
Click to collapse
Follow step 1 if not rooted or messed up somewhere during unrooting process.
Just double checking step 2: We can use es file explorer with root explorer option as well correct?
Also I noticed superSU got updated today:
http://forum.xda-developers.com/showthread.php?t=1538053
05.09.2013 - v1.60
- Added SELinux+Enforcing compatibility (for new SGS4 ROMs)
- Fixed (newest) CWM versions asking you question that break root if answered wrongly
- Fixed issue with the TWRP/CWM binary installer
- Fixed 4.3 OTA survival looping
Click to expand...
Click to collapse
Does the new update have something to do with our mf3 baseband like SELinux?
haremmon said:
So to summarize the steps from what I've read on rooting & unrooting MF3:
Root:
Use this guide by jortex: http://forum.xda-developers.com/showthread.php?t=2387577&highlight=mf3
Unroot: http://forum.xda-developers.com/showpost.php?p=44495559&postcount=39
Follow step 1 if not rooted or messed up somewhere during unrooting process.
Just double checking step 2: We can use es file explorer with root explorer option as well correct?
Also I noticed superSU got updated today:
http://forum.xda-developers.com/showthread.php?t=1538053
Does the new update have something to do with our mf3 baseband like SELinux?
Click to expand...
Click to collapse
This worked for me! But I skipped all the steps in the beginning. They sounded useless to me. Rerouting to unroot? Hah
I deleted all busybox files and was left with 3 files then went to SuperSU and did the full unroot and restart.
I check with root checker and installed SuperSU as well. Root checker said I have no root and SuperSU fails. Status is official.
Going to restart a few times to be sure.
Sent from my SAMSUNG-SGH-I337 using xda app-developers app
WezzleD said:
This worked for me! But I skipped all the steps in the beginning. They sounded useless to me. Rerouting to unroot? Hah
I deleted all busybox files and was left with 3 files then went to SuperSU and did the full unroot and restart.
I check with root checker and installed SuperSU as well. Root checker said I have no root and SuperSU fails. Status is official.
Going to restart a few times to be sure.
Sent from my SAMSUNG-SGH-I337 using xda app-developers app
Click to expand...
Click to collapse
Nice! Thank you. Looks like 4 confirmed. Also, was SuperSU on v1.60?
haremmon said:
Nice! Thank you. Looks like 4 confirmed. Also, was SuperSU on v1.60?
Click to expand...
Click to collapse
I'm actually not sure. Didn't look at version numbers.
Sent from my SAMSUNG-SGH-I337 using xda app-developers app
4 confirmed. Let's get 5 and I will post a how to.
Sent from my SAMSUNG-SGH-I337 using XDA Premium 4 mobile app
ou812bkewl said:
I fully un-rooted using the method in my post here - http://forum.xda-developers.com/showthread.php?p=44495559 . For me, it just threw the custom-lock icon boot up screen and showed "Custom" status in the "About Phone" menu when using the SuperSU's un-root method.
The problem was busy box. The MF3 root scripts install Busybox files into the /xbin directory, but SuperSU's "full unroot" doesn't touch Busybox's files. Not even any Busybox apps can remove those files.
Click to expand...
Click to collapse
That method worked for me also. I'm so glad it was discovered. Successfully unrooted.
Sent from my SAMSUNG-SGH-I337 using Tapatalk 4
5!
Sent from my SAMSUNG-SGH-I337 using XDA Premium 4 mobile app
graydiggy said:
5!
Sent from my SAMSUNG-SGH-I337 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
I was able to unlock as well. However my phone stopped showing the custom unlocked symbol at bootup a few days ago (before doing this) and I am at a loss as to why. So I am not sure I can count as a real confirmation.
I did your unroot process, root checker confirms I no longer have root and the unlock symbol has not come back.
Stay tuned guys. Getting everything ready to quickly make a more organized how to.
Being horribly sick is not helping
Sent from my SAMSUNG-SGH-I337 using XDA Premium 4 mobile app
So, it looks like Samsung put in a lovely system patch under the guise of "Software update" and I am now curious to see what another attempt at rooting might do to the knox 0x0 which is still show as such.
When attempting to see if an update is available, I now get a reply saying that My system is "modified" and that update is unavailable.
Running N900W8 on telus (Canada) likely will have to wait and see which one I would be willing to risk getting bricked... cf auto root which Would trigger Knox or waiting for an updated csc for the "Vega" method... which might have been patched
There is a software update avail on rogers...i turned my auto update off..i rarely take updates after what happened with the s4...sammy is trying to screw us usually..no thanks
Sent from my SM-N900W8 using xda premium
I need root access, so,
more research to be done.
??
Your system is modified because it detected a SuperSU binary inside your device. This does not affect KNOX as it affects every single Android device with 4.0 and above. Check Settings -> General -> About Device -> Status-> Device Status
You can obviously change it back to Official using Wanam Xposed, but no matter what, since you have root, you will have that there.
Sent from my SM-N900W8 using Tapatalk
nicholaschum said:
Your system is modified because it detected a SuperSU binary inside your device. This does not affect KNOX as it affects every single Android device with 4.0 and above. Check Settings -> General -> About Device -> Status-> Device Status
You can obviously change it back to Official using Wanam Xposed, but no matter what, since you have root, you will have that there.
Sent from my SM-N900W8 using Tapatalk
Click to expand...
Click to collapse
What if we uninstall supersu? Would we back to stock then? I used non knox tripping root.
dipole said:
What if we uninstall supersu? Would we back to stock then? I used non knox tripping root.
Click to expand...
Click to collapse
Just flash back stock then you can guarantee that it would say Official again. If you want to uninstall root all together without tripping KNOX then just boot it up in Download mode, flash your devices' stock ROM. I doubt you can just uninstall the root and reset your system counter just like that....don't take my word on this, but it could just be checking if there is root access, if there is then it would say custom. Revoking the root checker from settings could be what wanam did.
Sent from my SM-N900W8 using Tapatalk
nicholaschum said:
Your system is modified because it detected a SuperSU binary inside your device. This does not affect KNOX as it affects every single Android device with 4.0 and above. Check Settings -> General -> About Device -> Status-> Device Status
You can obviously change it back to Official using Wanam Xposed, but no matter what, since you have root, you will have that there.
Sent from my SM-N900W8 using Tapatalk
Click to expand...
Click to collapse
I've re-enabled official status from within wanams but to no avail... uninstalled it.. cleared cache and Data, reinstalled it and still no go.?
I did get root back by copying back Rot Vega folders to the system folder but so far, only recognized as a Custom system.
Pow35 said:
I've re-enabled official status from within wanams but to no avail... uninstalled it.. cleared cache and Data, reinstalled it and still no go.?
I did get root back by copying back Rot Vega folders to the system folder but so far, only recognized as a Custom system.
Click to expand...
Click to collapse
You installed the latest version of Xposed Framework, and then enabled Wanam Xposed within Xposed Framework's Module tab?
Yes, at that point you cannot revert back to official status
Sent from my Nexus 10 using xda app-developers app
:highfive:......
so is there any update to this? I am in the same situation... admittedly, I used the cf root method without reading into all the warnings first
I have a Samsung galaxy s4 running 4.2.2 AT&T, Recently I used triangle away and SuperSu to get rid of root and to get the official device status. I went into Odin and it said failure and I noticed that it said custom in the device status. So then I went to motorchopper how I rooted in the first place and did that and it also said "rooting... Failure" so now the questions is how do I get root access back so I can unroot it and then flash the official 4.2.2 and then get 4.4.2?
Flashing 4.2.2 in Odin will remove root. Why do you want to go to 4.4.2? You will no longer be able to use twrp or cwm if you do.
Sent from my Nexus 5 using XDA Free mobile app
Oh I didn't know that well thanks for the info, I'll stay on 4.2.2 then. Now my problem if when I goto motorchopper after it installs the SuperSu it waits and then fails. From what I read that means I'm still technically rooted but idk. Also idk if the status has anything to do with it but it still says custom instead of offical
OhDreamsNo said:
Oh I didn't know that well thanks for the info, I'll stay on 4.2.2 then. Now my problem if when I goto motorchopper after it installs the SuperSu it waits and then fails. From what I read that means I'm still technically rooted but idk. Also idk if the status has anything to do with it but it still says custom instead of offical
Click to expand...
Click to collapse
I don't know what the current status of your device is or what you're ultimately trying to achieve. But I would recommend you stay on 4.2.2, mdl, firmware and flash a 4.4.2 custom rom.
Sent from my Nexus 5 using XDA Free mobile app
Well OK here is what I want to do now, I want to re-root my 4.2.2. Thought when I use the moterchopper method it says failure right after it installs SuperSU for you. Now I'm stuck and don't really know what to do! I would love to know some way to fix this
OhDreamsNo said:
Well OK here is what I want to do now, I want to re-root my 4.2.2. Thought when I use the moterchopper method it says failure right after it installs SuperSU for you. Now I'm stuck and don't really know what to do! I would love to know some way to fix this
Click to expand...
Click to collapse
Does the device boot and can you check if you still have a custom recovery and whether you're rooted or not
Sent from my Nexus 5 using XDA Free mobile app
jd1639 said:
Does the device boot and can you check if you still have a custom recovery and whether you're rooted or not
Sent from my Nexus 5 using XDA Free mobile app
Click to expand...
Click to collapse
The device does boot, root checker says I have not root, and I believe I don't have a custom. Recovery b/c when I do power/down volume it bring me to download mode and power/up brings me into the regular recovery menu
OhDreamsNo said:
The device does boot, root checker says I have not root, and I believe I don't have a custom. Recovery b/c when I do power/down volume it bring me to download mode and power/up brings me into the regular recovery menu
Click to expand...
Click to collapse
I think at this point I'd flash the stock 4.2.2 firmware from sammobile.com in Odin and start over. But watch out for the device wanting to update itself after the Odin flash. If it does you'll lose the ability to use twrp or cwm. To avoid it, root with motorchopper, but on a custom recovery and flash a custom Rom. There also three files you can freeze our delay on the device that neuteres the updates. I only remember one of them, FWUpgrade
Sent from my Nexus 5 using XDA Free mobile app