I'm trying to install 4.2.1 just because the update message is getting annoying. I tried flashing the stock recovery and using rootkeeper to back-up root. Once I temp un-root and hit the install for the OTA, it begins to flash it, gets to 30%, then says error. I hold the power button to reset and I get a stock recovery error screen that says "No command." From here, I tried flashing stock system.img. This wouldn't write properly, so I ended up re-flashing CWM and simply rebooting and it boots back up fine.
How do I install this freaking OTA?
Edit: Can anyone find the .zip for it? Sideloading will probably work, I just can't find it.
Edit 2: Sideloading didn't work for my N4 which I have the zip for, it fails when verifying the system (related to build.prop). Not sure if the same will happen with the N10.
Related
I'm trying to install 4.2.1 just because the update message is getting annoying. I tried flashing the stock recovery and using rootkeeper to back-up root. Once I temp un-root, I go into fastboot, then stock recovery. I try to sideload the 4.2.1 zip with ADB, however it fails when verifying the system (looked to be related to build.prop.) I also flashed the stock boot.img due to using Franco's kernel but it still gives this error.
For some reason I seem to have lost root. I think this may have occured when I updated to 4.2.2, it automatically asked to update OTA. That or this occured from updating SuperSU.
When I try to go into recovery mode I see a android laying down with an exclamation point on his belly. I can't get into TWRP recovery.
SuperSU gives the error "There is no SU binary installed and SuperSU cannot install it"
I tried opening up titanium backup, and it says I have no root.
The fastboot states me phone is unlocked.
I have no issues rerooting, but I'm wondering:
a) Why and how this happened? Was it from the OTA update?
b) How I can prevent this in the future
c) Can I still back things up before rooting?
d) Will I lose everything when trying to root again?
AAhrens said:
For some reason I seem to have lost root. I think this may have occured when I updated to 4.2.2, it automatically asked to update OTA. That or this occured from updating SuperSU.
When I try to go into recovery mode I see a android laying down with an exclamation point on his belly. I can't get into TWRP recovery.
SuperSU gives the error "There is no SU binary installed and SuperSU cannot install it"
I tried opening up titanium backup, and it says I have no root.
The fastboot states me phone is unlocked.
I have no issues rerooting, but I'm wondering:
a) Why and how this happened? Was it from the OTA update?
b) How I can prevent this in the future
c) Can I still back things up before rooting?
d) Will I lose everything when trying to root again?
Click to expand...
Click to collapse
Just reflash the superSU.zip from here http://download.chainfire.eu/315/SuperSU/UPDATE-SuperSU-v1.25.zip in CWM and you should be rooted again. You will not loose any data so no need to backup. Download OTA Rootkeeper from Play to regain root after installing future OTA`s.
I'm not using CWM, I'm using TWRP and I can't seem to boot into it.
AAhrens said:
I'm not using CWM, I'm using TWRP and I can't seem to boot into it.
Click to expand...
Click to collapse
Try cmd and type: adb reboot recovery. If you see the androidian (stock recovery) you have to reflash the TWRP img file in fastboot mode.
Will this reset my phone? Or does only rooting do that?
You will not loose any data.
Sent from my Nexus 4 using xda premium
AAhrens said:
For some reason I seem to have lost root. I think this may have occured when I updated to 4.2.2, it automatically asked to update OTA. That or this occured from updating SuperSU.
When I try to go into recovery mode I see a android laying down with an exclamation point on his belly. I can't get into TWRP recovery.
SuperSU gives the error "There is no SU binary installed and SuperSU cannot install it"
I tried opening up titanium backup, and it says I have no root.
The fastboot states me phone is unlocked.
I have no issues rerooting, but I'm wondering:
a) Why and how this happened? Was it from the OTA update?
b) How I can prevent this in the future
c) Can I still back things up before rooting?
d) Will I lose everything when trying to root again?
Click to expand...
Click to collapse
Let me guess, you used a toolkit to root?
a) You did the full OTA, so you lost your custom recovery.
b) flash images through fastboot and skip the recovery.
c) Only after you flash a custom recovery. If your recovery is sitting in the same folder as fastboot and named "recovery.img, simply cd into the fastboot folder in a command prompt and type
fastboot flash recovery recovery.img
d) Not unless you lock or relock your bootloader.
OP, you need to do some more research and uninstall the toolkit from your computer. You know just enough to cause yourself problems, but not enough to know why they happen or how to fix them.
Yes the OTA update got rid of the files or partition that is created in order for you to have root access. Your custom recovery was also replaced with the stock recovery (android lieing on its back with red triangle).
To prevent you being unrooted in updates you can try using OTA RootKeeper available on Google play but this is not guaranteed to work.
You can use carbon to back up your data as this does not require root access to work.
And no you will not lose your data if you re root again, this is only done when you unlock the bootloader.
Rizy7 said:
Yes the OTA update got rid of the files or partition that is created in order for you to have root access. Your custom recovery was also replaced with the stock recovery (android lieing on its back with red triangle).
To prevent you being unrooted in updates you can try using OTA RootKeeper available on Google play but this is not guaranteed to work.
You can use carbon to back up your data as this does not require root access to work.
And no you will not lose your data if you re root again, this is only done when you unlock the bootloader.
Click to expand...
Click to collapse
Thanks all, was able to get it fixed by re-rooting!
Hi all,
I have put myself/phone in an interesting situation, which I am hoping the community can help me with.
I recently bought an LG G2, dold with stock 4.4.2. I proceeded to root it, and tried installing custom recovery.
I first installed ROM manager, which didnt work.
I then tried flashing twrp through adb using loki, which gave me a 'this is not a loki file' error.
I eventually realized that they had closed the Loki loophole in stock 4.4.2.
At this point, trying to enter recovery wouls give me a 'secure booting failed' error, making me have to reboot the phone again.
I then unrooted my phone, and factory reset it. I realized Clockworkmod recovery (which ROM manager installed) persisted despite the data wipe, so I unchecked that option in ROM manager and wiped it again.
My thinking was that I vould now downgrade to 4.2.2, install custom recovery there, then flash 4.4.2 whitout losing root or recovery.
Problem: I can't do any of this, because I can't reroot my phone with ioroot25. It fails as when it reboots inti recovery it gives me the 'secure booting failed' error.
Thanks for any help. I simply want to root my phone and if possible, have a functional recovery in order for me to flash some mods. At least being able to have it rooted again would be sweet.
Hehh...
Last thing you can do is try to flash with LG Flash Tools Method or LG Support Tool
Flash stock recovery either via fastboot / or dd(on linux). Then you can proceed further.
Or ^ kdz via download mode.
I have a similar problem. I restored the stock recovery via adb using a dd command. Then I unrooted in order to accept the latest OTA. The OTA fails with a "suspected root" error. Download mode still has "ROOTED" in red letters. At this point I gave up on the OTA and wanted to get back to where I was.
IOROOT25 doesn't work because when the phone reboots to recovery mode, I get the broken android with the red triangle but nothing else on the screen at all. There are no options, nothing. Eventually it reboots. I've done a factory reset to no avail. Recovery seems corrupted.
I need instructions for flashing the stock recovery with no root.
I managed to get my recovery rewritten using the LG Mobile Support Tool on a different computer. Then I was able to root again using ioroot25. I'm not sure why I couldn't run on my own laptop, but it's fixed now.
I cannot get root back on 4.4.2 at all on FNB8 (after OTA update)
Tried using Odin 3.07 and 3.09 with CF-Auto-Root-jflte-jfltexx-gti9505
There are no errors, it reboots, goes through the small setup, reboots again yet no root. Also tried installing SuperSU zip through recovery. Still no errors but no super su on phone.
Anyone know where I'm going wrong?
EDIT: Also, just to confirm - I have checked with a root checker - there is no root
i always just use the option in philz recovery to restore root, then either install supersu app through recovery zip or install it form the play store.
it's under philz settings, then restore root
Gloris said:
i always just use the option in philz recovery to restore root, then either install supersu app through recovery zip or install it form the play store.
it's under philz settings, then restore root
Click to expand...
Click to collapse
I have CWM touch, is it OK to just install over it or do I need to remove it first somehow?
just flash the latest philz using odin. whenever you flash a recovery it replaced the whole recovery partition i believe.
Tried rooting with Philz, it went through OK. Booted into OS, downloaded Super SU. Still not root
EDIT: Sorry Gloris, I got philz working, edited just before you made that next reply.
weird, i've never had that so not sure what to suggest. just to be clear, you got to download mode and flashed philz and all went fine in odin?
and just to be sure....try removing battery for 30 seconds, then insert battery and press and hold home key and volume UP while pressing power button (I tend to keep all 3 buttons pressed until i see the "se android is not enforcing" message and it's booting into recovery.
::EDIT::
no problem, did you get root working also? i've attached the zip that i flash after choosing restore root option in philz......i didn't make this zip, so not takign any credit or anything, jsut sharing it because it might be useful.
i generally prefer my device non rooted, but i use this method to quickly restore root to apply any rom changes then full unroot from within super su app. I found it's the easiest way to gain root access (works for me even from a fresh rom install too).
So I rooted, unlock the bootloader, and installed a custom ROM. I used the toolkit to revert back to stock. Tried to get the marshmallow update, and it fails to install. I try to go into recovery and it says no command. Are these related? And what do I need to do to receive the update?
constomy said:
So I rooted, unlock the bootloader, and installed a custom ROM. I used the toolkit to revert back to stock. Tried to get the marshmallow update, and it fails to install. I try to go into recovery and it says no command. Are these related? And what do I need to do to receive the update?
Click to expand...
Click to collapse
You don't see the twrp recovery because you reverted completely back to stock. That is the stock recovery that you are seeing. Be patient and you will get the update or you can flash twrp again and update manually
I already got the update but when installing it stops about half way and gives an error message
I had this issue as well and found no solution other than flashing a pre-rooted 6.0 image.
Even after I went to 5.1 stock the OTA failed with no clear error.
That's the problem with toolkits.