Rooted my phone with with RDLV before the OTA, never froze anything in TiBu, but disabled.
Installed Wanam and such and made some changes to I am assuming build.prop (notification bar, notification prompts, etc.).
Did the OTA, lost root but not all my mods (including ad blocking as well), but now I show as "custom."
Refuse to risk Kingo to re-root and repair status. Sorry China.
Can I factory reset with MJ5 to get back to full stock without soft brick or must I re-root and undo my changes?
Yeah i just did the factory wipe in recovery and it's clean and still rooted.
[email protected] said:
Yeah i just did the factory wipe in recovery and it's clean and still rooted.
Click to expand...
Click to collapse
Yeah, I lost root, but the "custom" status has me concerned, especially in light of all the recent lockdowns that I won't be able to get 4.4 without fixing the "custom" status.
I just want to be sure doing a factory reset will clean up my mess without softbricking.
I would be sure to do it from the recovery partition not from inside the phone. As far as root it might clean that up as well I remember I was not rooted after ota however after reset I was again.
Sent from my SAMSUNG-SM-N900A using xda app-developers app
[email protected] said:
I would be sure to do it from the recovery partition not from inside the phone. As far as root it might clean that up as well I remember I was not rooted after ota however after reset I was again.
Sent from my SAMSUNG-SM-N900A using xda app-developers app
Click to expand...
Click to collapse
So I did this today, which un-did all of my customizations except two.
1. SuperSu is still installed left over from RDLV I guess.
2. The boot up AT&T sound is still gone after I made that particular mod.
Unfortunately, I'm still showing a "custom" status in settings as well. I can't think of any way to undo this without rooting again (with Kingo?) until we get an Odin-able MJ5.
Is this a correct assumption?
Related
I did OTA Rootkeeper when I upgraded to JB, where I was successful at getting root. I installed Safe Strap, I then lost root when I tried to install SuperSU (failed update of binaries). Root checker app tells me I do not have root. So my stock ROM has no root, but when I load up Safe Strap, I am able to go to the previous ROM that I had prior to upgrading to JB (ROM Slot 3). When I load up that ROM I do have root. My question is, how to I go about getting my Stock ROM rooted?
I'm in the EXACT same position. I had root after accepting the OTA update using OTA Rootkeeper. After a day or so I decided to do a factory reset because things were acting a little funny. After the reset I lost root. I tried the ADB method on the stock ROM. I was able to get root access in ADB, but got some errors while trying to push the files. Now I can't get root access in ADB anymore on the stock ROM. I never reinstalled SafeStrap after the reset and didn't uninstall the recovery. I can boot into SS and switch ROMs normally. I have LiquidSmooth on slot 3, fully rooted. Any idea how to fix the stock ROM?
Sent from my XT875 using Tapatalk 2
I can't think of a easy solution . Something similar happened to me...in the end I ended up re-rooting with Linux moto share 2 exploit I think it is and starting over. After a certain point you gotta ask how much is it worth fooling around with forever?
Sent from my XT875 using xda premium
Recently wanted to update to kitkat after i rooted my phone and got frustated with it so I unrooted it and noticed the custom padlock logo was still on. after further review I see it was left with the device status set to custom as per normal when you root your phone. i did some digging and heard a lot of people stating some times if you used a 64 gig sd card it can trigger the custom status, well i use one and have since it was rooted and sadly enough after rooting and unrooting both with the sd card in and out it stays locked at the custom status. i really want to update the phone to kitkat from 4.3 because rooting really doesnt do it for me anymore. but i can not for the life of my figure out how to get it to switch back to official. i know if you used xposed module you can fake it to official. but when i upgrade to kitkat i will lose root permission and this is where my problems arise.
1. If i go ahead and update using xposed to fake my offical status will knox be triggered?
2. When i upgrade and lose root will the device automatically switch to back to official after upgrading or will i be stuck with the custom status and not be able to get anymore updates?
3. Is there any proven method to actually switch back to official permanately and not fake it like with xposed?
cynicalsinner91 said:
Recently wanted to update to kitkat after i rooted my phone and got frustated with it so I unrooted it and noticed the custom padlock logo was still on. after further review I see it was left with the device status set to custom as per normal when you root your phone. i did some digging and heard a lot of people stating some times if you used a 64 gig sd card it can trigger the custom status, well i use one and have since it was rooted and sadly enough after rooting and unrooting both with the sd card in and out it stays locked at the custom status. i really want to update the phone to kitkat from 4.3 because rooting really doesnt do it for me anymore. but i can not for the life of my figure out how to get it to switch back to official. i know if you used xposed module you can fake it to official. but when i upgrade to kitkat i will lose root permission and this is where my problems arise.
1. If i go ahead and update using xposed to fake my offical status will knox be triggered?
2. When i upgrade and lose root will the device automatically switch to back to official after upgrading or will i be stuck with the custom status and not be able to get anymore updates?
3. Is there any proven method to actually switch back to official permanately and not fake it like with xposed?
Click to expand...
Click to collapse
Use triangle away.
you will need root.
graydiggy said:
Use triangle away.
you will need root.
Click to expand...
Click to collapse
Can you give me a bit more detail then rhat? I downloaded it and I am currently rooted
cynicalsinner91 said:
Can you give me a bit more detail then rhat? I downloaded it and I am currently rooted
Click to expand...
Click to collapse
i had that problem i had to do a factory reset to get it to go away
I used Kingo to root. Decided to return to stock. After several manual reboots FINALLY removed "Custom" unlock and FINALLY RETURNED TO "Official".
Sent from my SAMSUNG-SM-N900A using xda app-developers app
jerrycoffman45 said:
i had that problem i had to do a factory reset to get it to go away
Click to expand...
Click to collapse
Sadly I have many times and it still persist. This is exactly what has happened since I got my phone a few months back. Bought it from at&t > rooted it > uprooted it because j couldn't figure out safe strap or how to install toms > rerooted it and tried again > successfully that time > got bored and wanted return to stock and upgrade > custom status issue now
There isn't much else to explain. You install triangle away, open the app and click reset flash counter.
Sent from my SM-N9005A using XDA Premium 4 mobile app
graydiggy said:
There isn't much else to explain. You install triangle away, open the app and click reset flash counter.
Sent from my SM-N9005A using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Oh wasn't sure if that was it or not my count is still set to 0 so I was thinking there was something else to it
Nope. It resets the flash counter and should reset the custom splash screen and custom status in settings.
I have never had issues with it.
Sent from my SM-N9005A using XDA Premium 4 mobile app
graydiggy said:
Nope. It resets the flash counter and should reset the custom splash screen and custom status in settings.
I have never had issues with it.
Sent from my SM-N9005A using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Custom is gone away from the boot logo and in download it reads as official however under settings it still says custom. If I were to just go ahead with the update even though under settings it says custom would it fail and trip knox? Or would everything get reset to official stock?
It will not trip knox.
If you have never done the "revert to MJ5" thread it should be fine.
Sent from my SM-N9005A using XDA Premium 4 mobile app
---------- Post added at 08:10 PM ---------- Previous post was at 08:10 PM ----------
Everything would go back to official
Sent from my SM-N9005A using XDA Premium 4 mobile app
Did you delete system apps while you were rooted (maybe via TitaniumBackup)? I'm in the same boat: TriangleAway made the padlock go away but the "Custom" status is still in device settings. I think it's because the system partition is no longer stock because I deleted some AT&T bloat. I have NB4 and can't update to KitKat (probably because it detects this custom status) and I can't downgrade to MI9 because bootloaders for NB4 and MI9 are not compatible. Looks like I'm stuck until I can use Odin with official KitKat.
My employer uses an enterprise email application (Good) that scans the device for root etc.
I restored my device to an old old backup that I made when I first got the device, but for some reason superuser.apk is still lingering around in my system folder.
I can confirm that the device is no longer rooted as superSU fails to find a binary, and my carrier OTA updates have been coming through fine.
However, that pesky superuser apk is sticking around, and I'm convinced that it is the reason my device is failing the compliance test with the software.
Any suggestions on how I can remove the superuser apk from the system directory? Preferably without blowing up my current android install?
I've dug high and low with no luck, and i'm hboot 1.57, so going S-Off and using an RUU to isn't an option.
SD360 said:
My employer uses an enterprise email application (Good) that scans the device for root etc.
I restored my device to an old old backup that I made when I first got the device, but for some reason superuser.apk is still lingering around in my system folder.
I can confirm that the device is no longer rooted as superSU fails to find a binary, and my carrier OTA updates have been coming through fine.
However, that pesky superuser apk is sticking around, and I'm convinced that it is the reason my device is failing the compliance test with the software.
Any suggestions on how I can remove the superuser apk from the system directory? Preferably without blowing up my current android install?
I've dug high and low with no luck, and i'm hboot 1.57, so going S-Off and using an RUU to isn't an option.
Click to expand...
Click to collapse
install superSU from the market .. then in superSU settings theirs cleanup / Full Unroot
clsA said:
install superSU from the market .. then in superSU settings theirs cleanup / Full Unroot
Click to expand...
Click to collapse
I actually still have SuperSU installed. The problem is that I no longer have a superuser binary, so supersu won't run. Just gives me the usual "There is no SU binary installed, and SuperSU cannot install it. This is a problem." error.
I'm starting to suspect that I might need to re-unlock and re-root just to do the cleanup and re-lock, which is frustrating. Was hoping to be able to avoid those big steps.
SD360 said:
I actually still have SuperSU installed. The problem is that I no longer have a superuser binary, so supersu won't run. Just gives me the usual "There is no SU binary installed, and SuperSU cannot install it. This is a problem." error.
I'm starting to suspect that I might need to re-unlock and re-root just to do the cleanup and re-lock, which is frustrating. Was hoping to be able to avoid those big steps.
Click to expand...
Click to collapse
yeah i know what you mean their
SD360 said:
I'm starting to suspect that I might need to re-unlock and re-root just to do the cleanup and re-lock, which is frustrating. Was hoping to be able to avoid those big steps.
Click to expand...
Click to collapse
(unless you are s-off), re-unlock -> yes, then just use a custom recovery.... custom recovery has root access to all your filesystem, there's no real need to "re-root" a full ROM.
you can accomplish pretty much anything in custom recovery
nkk71 said:
(unless you are s-off), re-unlock -> yes, then just use a custom recovery.... custom recovery has root access to all your filesystem, there's no real need to "re-root" a full ROM.
you can accomplish pretty much anything in custom recovery
Click to expand...
Click to collapse
Appreciated. I'll give it a shot. I just really want to avoid anything that's going to break my ability to get OTA updates again. It was a massive pain to get back to that point before.
I'll just be sure to dump my stock recovery before I do it.
SD360 said:
Appreciated. I'll give it a shot. I just really want to avoid anything that's going to break my ability to get OTA updates again. It was a massive pain to get back to that point before.
I'll just be sure to dump my stock recovery before I do it.
Click to expand...
Click to collapse
it's not as hard as you make it seem... their is a Guru Reset for nearly every version / brand phone and their really easy to use to get back to stock for OTA updates.
Returning to total stock, lock not relocked can be a bit more of a PITA but still doable as long as you s-off
clsA said:
it's not as hard as you make it seem... their is a Guru Reset for nearly every version / brand phone and their really easy to use to get back to stock for OTA updates.
Returning to total stock, lock not relocked can be a bit more of a PITA but still doable as long as you s-off
Click to expand...
Click to collapse
Not really worried about the locked/relocked flag. I don't think that's a check that good does. Pretty sure it just looks for certain files and conditions.
Unfrotunately there is no recent guru reset for my carrier (Rogers), and my device is trapped in S-On as my hboot is super new.
I was able to get twrp up and running, and manually removed all traces of root. Now just hoping I can get my stock recovery back. Hopefully will get me back into the game.
Hello, I just today found out about the update to the Lollipop 5.0. I checked and attempted the download. It got all the way to the restart and install and then it stopped and instantly booted back up. It came up with the notification "Update Interrupted" or something very similar. I tried again after resetting the phone back to factory mode. It did the same thing. I have seen people have the problem of not enough storage but i had plenty. Especially after the factory reset. I know that this is an over wifi update and i am trying to understand why my phone isn't accepting it or why it isn't working. Thank you for any help you can offer.
Alan1727 said:
Hello, I just today found out about the update to the Lollipop 5.0. I checked and attempted the download. It got all the way to the restart and install and then it stopped and instantly booted back up. It came up with the notification "Update Interrupted" or something very similar. I tried again after resetting the phone back to factory mode. It did the same thing. I have seen people have the problem of not enough storage but i had plenty. Especially after the factory reset. I know that this is an over wifi update and i am trying to understand why my phone isn't accepting it or why it isn't working. Thank you for any help you can offer.
Click to expand...
Click to collapse
If you have rooted or modified the system apps in any way then the update is going to fail. You have 2 options:
You can wipe your phone and start with a clean stock ROM; or
You can follow the guide to retain root on OC6. You don't have to be rooted for this method, but this method will allow you to update if you've modified your system.
Devo7v said:
If you have rooted or modified the system apps in any way then the update is going to fail. You have 2 options:
You can wipe your phone and start with a clean stock ROM; or
You can follow the guide to retain root on OC6. You don't have to be rooted for this method, but this method will allow you to update if you've modified your system.
Click to expand...
Click to collapse
My system has been rooted before but it no longer has root access.
When you say wipe and start with a fresh rom, isnt that also the same as resetting the device?
Alan1727 said:
My system has been rooted before but it no longer has root access.
When you say wipe and start with a fresh rom, isnt that also the same as resetting the device?
Click to expand...
Click to collapse
To explain a bit further, the way the update works is there's a program built into the OTA. This program checks the signature of all the system files on your phone against a database included in the OTA. If all the signatures match then the update will proceed, but if even 1 of the signatures doesn't match then the update will fail as you have experienced.
When you root your phone you are exploiting a weakness in some aspect of android that allows you to modify system files. Once you modify system files by rooting you change their signature. Even if you unroot, it is impossible to change the signatures back to what they originally were. This is the reason that even if you unroot the update will fail.
By resetting the device you are essentially deleting all the user apps and settings, the system files go virtually unchanged. So if you unroot, your signatures still don't match and when you factory reset the device the system files don't get touched so the signatures still won't match. The only thing you can do to get the signatures to match is to flash the NE3 full Odin package. This will completely wipe out our phone and install everything (the bootloaders, modems, system files, etc.) from scratch.
So like I said you have 2 options:
Follow the guide I linked to above; or
Flash the NE3 Odin package and take the OTA.
Either way you have to use Odin at some point.
I just got my N6 a few days ago, and JUST got everything all set up how I like. I went to go root it, and the method mentioned in the "All-In-One" stickied thread requires you to unlock the bootloader, which says it will factory reset the device.
I don't want to factory reset at this point, I just want to root it. I've never had to wipe a phone or unlock a bootloader to root a phone before, so this is new to me.
Thanks
arcooke said:
I just got my N6 a few days ago, and JUST got everything all set up how I like. I went to go root it, and the method mentioned in the "All-In-One" stickied thread requires you to unlock the bootloader, which says it will factory reset the device.
I don't want to factory reset at this point, I just want to root it. I've never had to wipe a phone or unlock a bootloader to root a phone before, so this is new to me.
Thanks
Click to expand...
Click to collapse
There is a way, I believe, by running TWRP on your PC and flashing SuperSU from your PC. However, it's not a recommended method as you will have no way of backing up. Also, if you get caught in a bootloop, you won't be able to recover without a custom recovery.
arcooke said:
I just got my N6 a few days ago, and JUST got everything all set up how I like. I went to go root it, and the method mentioned in the "All-In-One" stickied thread requires you to unlock the bootloader, which says it will factory reset the device.
I don't want to factory reset at this point, I just want to root it. I've never had to wipe a phone or unlock a bootloader to root a phone before, so this is new to me.
Thanks
Click to expand...
Click to collapse
and you don't have to "hack" a nexus as well, as google provided an easy way to unlock your bootloader and to obtain root. if you just got your nexus a few days ago, just unlock the bootloader and root it. loosing a few days of information is more than worth it for root. don't waste your time worrying over a few days of data.
Can be done but not recommended.
adb backup/restore can save a little bit of information for you, but I wouldn't go in expecting it to save everything
Sent from my Nexus 6
What did you set up? You can back up your messages, and your apps will re-download. Your photos are already syncing to Google. If it's not rooted, I can't imagine you've done that much customization.
Lesson learned: unlock should ALWAYS be the very first step you do on a new phone.
arcooke said:
I just got my N6 a few days ago, and JUST got everything all set up how I like. I went to go root it, and the method mentioned in the "All-In-One" stickied thread requires you to unlock the bootloader, which says it will factory reset the device.
I don't want to factory reset at this point, I just want to root it. I've never had to wipe a phone or unlock a bootloader to root a phone before, so this is new to me.
Thanks
Click to expand...
Click to collapse
if you download kingroot from the internet and install it onto your phone through unknown sources. it says your not supported but just click start root anyway. and hey presto your rooted. ive done this on my nexus 6 and its worked and hasnt knackered the phone and i know a couple of other people whove done the same
the only thing i havnet worked out how to do is take the king userr off. once your finished rooting, in order to sustain root that app becomes a permanent addittion to the phone. ive deleted it before and lost root. but just reinstall and follow the steps again and you gain root again
to check root download root checker form the app market
danr93 said:
if you download kingroot from the internet and install it onto your phone through unknown sources. it says your not supported but just click start root anyway. and hey presto your rooted. ive done this on my nexus 6 and its worked and hasnt knackered the phone and i know a couple of other people whove done the same
the only thing i havnet worked out how to do is take the king userr off. once your finished rooting, in order to sustain root that app becomes a permanent addittion to the phone. ive deleted it before and lost root. but just reinstall and follow the steps again and you gain root again
to check root download root checker form the app market
Click to expand...
Click to collapse
Yes we're aware but we do recommend against these one-click methods usually. Rooted users cannot accept OTA updates, so the only way to update is with an unlocked bootloader unless you're going to have a custom recovery (also highly recommended) so you can flash flashable zips.
Also you MUST go into settings and enable the "Allow OEM unlock" in developer options, because If you break your OS with root, which is easily done - you're going to become stuck as you can't unlock the bootloader. Not too bad if you have TWRP recovery installed, but then that becomes a single point of failure.
danarama said:
Yes we're aware but we do recommend against these one-click methods usually. Rooted users cannot accept OTA updates, so the only way to update is with an unlocked bootloader unless you're going to have a custom recovery (also highly recommended) so you can flash flashable zips.
Also you MUST go into settings and enable the "Allow OEM unlock" in developer options, because If you break your OS with root, which is easily done - you're going to become stuck as you can't unlock the bootloader. Not too bad if you have TWRP recovery installed, but then that becomes a single point of failure.
Click to expand...
Click to collapse
ok thats fair enough i didnt realise it was so risky. i downloaded twrp straight after this method worked for me and got everything backed up
danr93 said:
ok thats fair enough i didnt realise it was so risky. i downloaded twrp straight after this method worked for me and got everything backed up
Click to expand...
Click to collapse
Good stuff. Once rooted, Flashify is a great tool to flash TWRP. With the nexus 5, you could unlock the bootloader with an app that didnt wipe everything, which was great, but Nexus 6 doesn't allow that, but always do go to settings > developer options > OEM Unlock (Set to enable). Without this set, you cannot unlock the bootloader from fastboot. Also, side note, developer options doesn't show up until you go into Settings > About phone then tap "Build number" several times to make the option visible. Think its 7 times.
It's interesting saying that you need kingroot to remain on the device. Thats a bit of a pain. Does it install SuperSU or not? If not, might be interesting to see what happens if you install the SuperSU app from Play - whether it allows it to be removed then.
My preferred method however is definitely unlock the BL, fastboot flash TWRP, From TWRP flash SuperSU zip (or rooted ROM).
For the record, I did end up factory resetting to do it the right way.
Is this easy to unroot if a new OTA update comes out?
arcooke said:
For the record, I did end up factory resetting to do it the right way.
Is this easy to unroot if a new OTA update comes out?
Click to expand...
Click to collapse
Yes and no. To "unroot" you have to fastboot flash system.img and boot.img, which if the factory image is available for the version your OTA will raise you to, you're done. If there is no factory image for that new version, you must flash the system and boot(and recovery) of the expected version, then OTA. Note, recovery version isn't checked. Only system and boot. Just that recovery must be stock for OTA to flash.
To be honest, easiest way is to wait for a rooted flashable zip to be made available and flash via recovery
danarama said:
Yes and no. To "unroot" you have to fastboot flash system.img and boot.img, which if the factory image is available for the version your OTA will raise you to, you're done. If there is no factory image for that new version, you must flash the system and boot(and recovery) of the expected version, then OTA. Note, recovery version isn't checked. Only system and boot. Just that recovery must be stock for OTA to flash.
To be honest, easiest way is to wait for a rooted flashable zip to be made available and flash via recovery
Click to expand...
Click to collapse
Geez. I thought the "pure google experience" would be much less of a headache. lol. Rooting/updating/etc was so much easier on my old Verizon phones.. one-click-root, one-click-unroot, easy updates, never had to factory reset or flash roms to do anything.
I only rooted for AdAway, starting to wonder if that was a good idea or not.
arcooke said:
Geez. I thought the "pure google experience" would be much less of a headache. lol. Rooting/updating/etc was so much easier on my old Verizon phones.. one-click-root, one-click-unroot, easy updates, never had to factory reset or flash roms to do anything.
I only rooted for AdAway, starting to wonder if that was a good idea or not.
Click to expand...
Click to collapse
That's lollipop for you. It changed everything.
It's still really simple.
Good to know. Thanks for the info!