My phone is a lg volt 4g, i need update the Android version. But it dong go by OTA because of the root. The supersu dont work... Problems with the binary system.
Related
Has anyone on DBT CSC used the OTA rootkeeper in CF's SuperSU comin from LB1-LC1?
success?
I I have mobile odin pro, so could just use that, but the SuperSU OTA rootkeeper interests me, would be cool if it works.
either way I'll make the jump to LC1 shortly.
Just flashed the open Germany (DBT) update by mobile odin, the usual method, don't want to take chances of loosing root!
I'd still be interested to know if it works though.
Side note: the update didn't wipe my phone, I'd heard it was a wipe upgrade, but seems to have been non wipe for me.
Some how my phone threw a fit and refused to update via FOTA and kies just said "this phone is not supported" so used mobil odin aswell.
No one with SuperSU pro that can post fota survival or not?
I think before updating to OTA(with SuperSU support), replacement of CF root n CWM with stock kernel should work.
i m eager to test it too, but india have no recent update.
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...
Has anyone found a way to root? With no more download mode we can't even downgrade... No root methods work eg: towel,stump,vroot,io etc...
If anyone does find a way to root please update here!
Someone posted in another thread that they gained root on the D95920s with stumproot. I was going to flash back to stock at some point today to take the upgrades and test it out. Will update my findings later.
Yes! Root!
I just got done testing. I installed the latest update which broke root. I used STUMP to root. It worked! Verified with root checker before and after running STUMP.
Do any of you have the OTA update file?
Stump says already rooted
mattwheat said:
Someone posted in another thread that they gained root on the D95920s with stumproot. I was going to flash back to stock at some point today to take the upgrades and test it out. Will update my findings later.
Click to expand...
Click to collapse
Any luck? I try stump root and it says device us already rooted. I guess I should have used lg flash tool first to completely restore, and then maybe stump root would've worked? I think it is kinda dumb that stump root refuses to even try to root your device if it has been rooted before but lost root due to ota. If only it had a message like "it appears your device is already rooted, would you like to reroot anyway?" Or something like that. Anyways I'm getting by okay without root, so its no big deal if I am stuck, but if there is a way to make stump root work that would be cool.
@steven_computer_guy. Did u try going to playstore and download/install SuperSU apk and then recheck if your rooted or not?
Yup. SuperSU says "there is no supersu binary installed, and SuperSU cannot install it. This is a problem"
Try factory reset via button combo and try towel or stump root?
I got this phone today and it did an OTA update. I'm now on 5.1.1. Is it possible to root this phone? I'm don't think Kingroot will work and not sure I want to use it anyway.
c-dude said:
I got this phone today and it did an OTA update. I'm now on 5.1.1. Is it possible to root this phone? I'm don't think Kingroot will work and not sure I want to use it anyway.
Click to expand...
Click to collapse
If you root you won't be able to install updates anymore
You can root with Droid tool or King root 4.0
If you know how to, do a 100% backup with SP Flash tool
Before you try anything.
Thanks. I read on the Kingroot thread that its not working on 5.1.1. I'm a superuser kinda guy anyway, and not sure I want to use Kingroot. I'll google Droid tool to see how it works.
c-dude said:
Thanks. I read on the Kingroot thread that its not working on 5.1.1. I'm a superuser kinda guy anyway, and not sure I want to use Kingroot. I'll google Droid tool to see how it works.
Click to expand...
Click to collapse
I can confirm kingroot works.
infinix hot 2 5.1.1
I have the same problem with the same device and king root keeps failing any idea what I'm doing wrong? I've tried the OTA and pc versions.
The update with the November security patch can't be rooted for now. I have tried all rooting softwares I know of (apks & PC) and none worked. perhaps a little more patience?
if you wish to root,
flash twrp
flash superuser zip
I'm presently rooted on 11-03 build
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.