I lost root after a normal reboot. Super SU sais there is no SU binary installed and it cannot install it.
So I've tried several times to CF autoroot again, but nothing changes.
Does anyone know what may be going on?
Edit: Realized I shared no info about what's running: Stock rom (920G, MM) and was CF autorooted.
I'm guessing the rom is replacing my recovery on boot, could this be it?
This just happened to me as well on my G920T running MM. I wonder if some sort of update was pushed out that makes CF auto root no longer work.
Edit: It looks like a new SEAndroid policy was pushed out that makes CF Auto Root no longer work (see this thread).
If you see "SE for Android Status: Enforcing, SEPF_SECMOBILE_6.0.1_0011" under your device status, that would explain it.
Related
Hello everyone.
I got a little problem with my phone, since i want to root it, i checked out which build I had installed on my phone, here's the results:
i.imgur.com/1sOmg7i.png
As you can see, my build is an AMG3/AMF3, and i couldn't find any guide for rooting with that build installed.
What should i do?
Thank you in advance,
Amaryl.
Hi there,
Firstly, I am new to all this too, so take my advice, or leave it, with that in mind!!
I have recently rooted mine from the AMG3 build with mskip's toolkit. I took the plunge and took his advice on choosing the closest available build. I donated so as to be sure I had his latest update of the toolkit. I am not near my pc, but it was the selection which included the AMD3 build (the most recent, ie bottom in the section for the model with NFC, as that is themodel I have). I had one root through odin which failed to give superSU any binaries or permissions at all, so then completely reinstalled the toolkit on my pc (possibly unnecessary) and then reflashed twrp recovery, but chose the cwm version of superuser and ot worked perfectly! As far as I can tell, my phone works exactly as it did before, but now with root access.
If you look in this section of the forum, I posted a q this morning which gives a couple more details about the process I went through re 1st failed attempt which I won't retype here, but I can confirm I have full rooted functionality with the toolkit over the AMG3 build on the N model of the mini, with twrp and superuser!
Btw I say a failed attempt, but my phone worked fine, I just got an error message at the end of the toolkit installing busybox, so booted the phone and superSU just said "there are no binaries I stalled, this is a problem!". So I assume I wouldn't have been able to exploit the root, but at no point did It stop the phone working as a phone.
As I say, I am faaaar from an expert, but that's my experience.
Hi there,
Just got a new S5 mini (SM-G800F) today. I've updated to latest Android version (4.4.2). I did not install any custom ROM. Build ID was KOT49H.G800FFXXU1ANJ1.
I've then rooted the phone successfully with CF-Auto-Root (http://autoroot.chainfire.eu/) and Odin. The closest file I found was KOT49H.G800FXXU1ANH2. ANJ1 to ANH2 looks like a "downgrade"... perhaps this is the issue? But read on..
I then started to install corporate access (Exchange account). Our corporation wants to have the device encrypted so I started to do that.
What basically happens is that the encryption droid symbol shows on the screen for about 20 minutes and after that the device reboots.
Yet, no encryption has happened! (is the anywhere a logfile I can look at for more info?)
I have a Samsung Galaxy S3 with 4.1.2, stock ROM as well and rooted with CF-Auto-Root. On that device the encryption process was more verbose and worked fine (although slowed down the phone considerably during normal usage).
So, does rooting the S5 mini with Autoroot break the encryption process? How can I encrypt the phone? Do I have to go back to pure unrooted stock, encrypt first and root later?
Thanks for any insights.
Dan
I still do not know why encryption would not work, but I found a workaround:
I reset the phone to the latest stock firmware with the help of Kies 3. I got G800FFXXU1ANG7. Obviously I lost all data, but that is ok since its a brand new phone.
Started the phone and configured WLAN to accept and install pending OTA upgrade. Just to get to the very latest release at the moment (G800FFXXU1ANJ2).
Encrypted device. I installed the corporate access tools which required the encryption...
Then I installed latest TWRP for my device with ODIN.
Last step was to install SuperSu with TWRP, using the zip file from chainfire.
Some remarks:
- I am not sure why encryption fails while the phone is rooted. Perhaps someone could explain to me?
- If I use CF-Autoroot after encryption of the device, the phone would go into a boot loop, i.e. not asking for the decrypt password and fall back to the boot logo. I thought that encryption would only touch /data. Most likely there is something that initiates decryption during boot, which is replaced by the CF-Autoroot image.
- OTA updates are not possible anymore after installing TWRP recovery (the phone complains that there are changes to the stock ROM). However, if I re-flashed with a stock recovery, OTA was not complaining anymore. If an update would actually work, I have not checked.
- If SuperSu is already installed however, even TWRP re-flashing with stock recovery would not make OTA work again. I would assume that the OTA update routine checks several components to decide if there is stock installed. Temporarily disabling SuperSu did not work, un-rooting through the SuperSu menu left me with SuperSu hanging for an hour until I switched the phone off. I also tried the OTA survival mode (I have SuperSU Pro) and it does not work either (in that try I left out step 2 above).
So for now I have a rooted S5 mini on Android 4.4.2 with encryption and I am happy. I did live without OTA with my S3 (which still is on 4.1.2) since I rooted it and frankly, I did not really miss 4.3...
Regards
Dan
If you change some files (like Recoery or rooting) OTA won't work anymore on any Samsung Rom...only pure Stock!
User_99 said:
If you change some files (like Recoery or rooting) OTA won't work anymore on any Samsung Rom...only pure Stock!
Click to expand...
Click to collapse
Thanks. That is what I thought.
1 - Encryption fails if the phone (S5 mini, 4.4.2) is rooted. Why? However, encrypting a rooted S3 (4.1.2 stock) did work fine. Was there anything changed with the newer Android versions?
2 - Do we know what the OTA process is checking to decide if it can go ahead or stall? SuperSu's OTA survival surely knows a bit more on that.. but unfortunately it still won't work..
Mahesh Senghani here please help me. Long time trying but not properly Root Access not properly configured or was not granted. Please sir how to fix this problem deeply request to you please solution easiest explain to me
Mahesh Senghani
Please help me you send Email [email protected]
How to fix this problem
grokit said:
Thanks. That is what I thought.
1 - Encryption fails if the phone (S5 mini, 4.4.2) is rooted. Why? However, encrypting a rooted S3 (4.1.2 stock) did work fine. Was there anything changed with the newer Android versions?
2 - ..
Click to expand...
Click to collapse
Hey, please read about KNOX, hope you may get your answer...
I'm a bit slow to realize this, but after updating to T mobile's latest 20b firmware (lollipop 5.0x), it lost root. I then tried to root it, using the three methods mentioned here: http://forum.xda-developers.com/showthread.php?t=2732311.
Towelroot clearly doesn't work anymore. The zip file in the above thread couldn't be flashed since there's no recovery operation possible (just showing an android with ! in a triangle sign). I also tried the purpledrake, but the script doesn't run when the phone is connected with all drives installed and adb devices showing the phone. I then tried to get fastboot mode back (to install twrp/cwm recovery to flash the zip file) by following http://forum.xda-developers.com/lg-l90/general/guide-fastboot-l90-d415-t2827825 which I have done successfully before, but then couldn't do it because it requires root (doh!).
So it seems that I just lost my ability to root, unless I downgrade to a stock kitkat (10e?) from tmobile, and then towelroot/etc. assume those work.
Anyone with experience on the stock 20b firmware? Can you root it and how? I'd love to use the beautiful 12.1 Cyanogen that's available here, but the camera doesn't work right on mine. Thus stock 5.0 seems to be the best option. Many thanks.
I got a bit further on the purpledrake method, in that I had to do a clean restart on the phone and connect to usb before the script will recognize. However, it ends up giving a really quick error message after trying a temp root: "your phone is not running a compatible software version. No vulnerable mode detected. Rebooting phone."
Anyway, many thanks to @brossovitch I followed http://highonandroid.com/android-smartphones/how-to-root-lg-g-flex-2-g2-g3-on-lollipop/ and it works like a charm. I can't seem to delete this very short thread so I thought I'd wrap it up with a solution. If it seems a bit useless please remove the thread (or tell me how to do it since I can't find the "easy button"). Thanks.
OK I got the notification to update today it's MMB29S, I am on K. I am rooted but stock, unlocked using systemless root for root. I've always been rooted and expected it to fail and have to install manually but this time because I'm not rooted like the old way. So i downloaded and went to install to my surprise dead Android with the triangle didn't show but it went to custom recovery screen twrp. I just hit restart because I've never not had a fail and never seen it do this before. Well when it restarted I was not updated and still on K. I also for the life of me can't get it to redo the ota. Tried to clear system service in apps and recheck but nothing.
So my question is since I'm new to systemless root what should I have done when it went to custom recovery? So that way if I can get it to pop up again I can be updated. Thank you in advance for any help and it would be awesome if possible to update this way without having to manually do it.
My best guess, based on what Chainfire replied to me when I asked about OTA, is that because you're somehow rooted the OTA will refuse to install. He said that using the "unroot" function in v2.63 (and I suppose in subsequent versions) he was able to apply the OTA and then just had to re-root.
As to the OTA, I read in the long-distant past that once it's been provided to your device you sort of go to the back of the queue, and even pressing the "check for system update" button has no effect. One day your turn will come again. When it happens, before you press the "install now" button, use the unroot function, reboot, and give it another go.
And I would really appreciate it if you could report back on the success or failure, just so we all know - thanks...
And before I close... your alternative is just to download the full ROM from Google, unzip everything in sight (including the zip within the zip), copy system.img to a convenient folder, and use Fastboot to flash system. After that you'll need to re-root (simple flash) and when you reboot everything will be as it was, apart from the version and security update date. I did it myself to MMB29S a week or so ago.
But my lawyer advises me to advise you to take a full backup first and store it off your device before you do anything to your device - just in case, you know?
I will definitely reply if I get the update again in a few days. If it doesn't I'll probably do it manually. I was just really surprised I hadn't gotten the error, just so used to it. Thank you for the info though.
Correct me if I'm wrong, but to install an OTA don't you need to be completely stock, including recovery?
If I'm not mistaken but since 4.3 (I'm probably wrong) if your rooted (before systemless root) when you try to the ota you will always get the dead Android because rooting changes the system files causing the update when it does is checks to think your system is corrupt.
Also it was really bad when people tried going from 5.x.x to 6.x even doing it manually some of us got bootlooped or when starting the phone up after updating manually saying system is corrupt but still starting up fine. Leaving like me having to completely clear out everything and installing the factory image just to not be corrupt and able to use Android pay.
Systemless root though I've not had a single problem and still able to use AP. And is also the first time in years I've gotten as far as I did with the OTA.
Rbh50815 said:
OK I got the notification to update today it's MMB29S, I am on K. I am rooted but stock, unlocked using systemless root for root. I've always been rooted and expected it to fail and have to install manually but this time because I'm not rooted like the old way. So i downloaded and went to install to my surprise dead Android with the triangle didn't show but it went to custom recovery screen twrp. I just hit restart because I've never not had a fail and never seen it do this before. Well when it restarted I was not updated and still on K. I also for the life of me can't get it to redo the ota. Tried to clear system service in apps and recheck but nothing.
So my question is since I'm new to systemless root what should I have done when it went to custom recovery? So that way if I can get it to pop up again I can be updated. Thank you in advance for any help and it would be awesome if possible to update this way without having to manually do it.
Click to expand...
Click to collapse
These small ota's can be done with boot modifications because they don't include any boot.img changes and if they do then they just blanket overwrite what's already there. The only part that is checked is /system. However TWRP won't ever install an ota update for compatibility reasons. Even if you reflash the stock recovery then you'll fail the ota because when you installed TWRP it protected itself (by modifying /system) from being overwritten by the stock recovery which is what unmodded stock android will always do on boot by default. And there are 2 things the ota verification looks for when updating: 1. It looks for whether /system has been ever mounted as Read/Write. 2. It hash checks the /system, if it finds any mismatch it fails. As for the update not showing up again, the ota checker hides the update after a failure to stop from flooding the download server. If you want to extract the update zip you can look in /cache for the zip. But since you don't have an unmodded /system you might as well just download the newest factory image and manually flash the system.img
You can use Wug NRT, unroot with MMB29S provided in the NRT , then root.
Hello everyone!
So I rooted my Note 3 back when I first got it and I've been loving it. Well, about a month ago I noticed that an application that I wrote (restarts my phone automatically under certain conditions) would not work correctly, as though its Superuser permissions were revoked, but the SU app said everything was fine. Fast forward to a few days later and I try to access the root of my phone using ES File Explorer and discovered that I had lost root. I tried Kingo Root and Towelroot and they both failed, so I'm stumped as to why I lost root and why I cannot seem to get it back. I know I could go about wiping the phone but that would remove everything on my phone except for my applications and those are the least of my worries.
Any ideas? I appreciate any and all help!
Android Version: 4.4.2
Baseband Version: N900AUCUCMLG
Kernel Version: 3.4.0-257432
Build Number: UrDroid KOT49H.N900AUCUCMLG
Not sure if any of this information makes a difference but it's worth posting just in case.
To anyone who may come across this and is having the same issue, I was able to resolve mine, and hopefully the steps that I took (listed below) will be of some kind of assistance to another.
I still had Safestrap installed, so I was able to install a ZIP version through it, and I rebooted after it was done. I let the phone load back up fully before going back into Safestrap to wipe the Dalvik/Cache, attempt to Fix the Permissions (which failed), and then renamed the data/data/eu.chainfire.supersu folder to eu.chainfire.supersuh (as I thought that maybe the old folder was causing conflicts). After booting back into Android I had root again! I cannot delete the eu.chainfire.supersuh hence why I renamed it, but I've got root back on my phone so I'm satisfied.
I will add that all of these steps may not have been necessary but I do not know what step made it work, this is just what I did to solve my problem.