[SOLVED] Unlocked BL, Updated 4.4.2 via OTA, Unable to Root - Moto X Q&A

Ok, i am in the soak test for ATT Kitkat 4.4.2 (XT1058). I reverted back to stock, and took the OTA update.
I have an unlocked bootloader, so i mfastboot flashed TWRP recovery 2.6.3.1 with success
i've tried unofficial TWRP 2.7.0.0, and philz_recovery w/ no luck
I flashed supersu (via zip) v 1.89 and v 1.93, recovery reported success
Reboot, Supersu is not in my app drawer. I installed Supersu via playstore with success, installed "binary" with reported success.
Tried Superuser from Clockword Mod, no luck
Supersu crashed upon launching Titanium Backup w/ TB hanging.
It appears Supersu is not installed correctly.
What am i missing? Installing Supersu should be the easiest thing on an unlocked bootloader.

cpetersen2791 said:
Ok, i am in the soak test for ATT Kitkat 4.4.2 (XT1058). I reverted back to stock, and took the OTA update.
I have an unlocked bootloader, so i mfastboot flashed TWRP recovery 2.6.3.1 with success
i've tried unofficial TWRP 2.7.0.0, and philz_recovery w/ no luck
I flashed supersu (via zip) v 1.89 and v 1.93, recovery reported success
Reboot, Supersu is not in my app drawer. I installed Supersu via playstore with success, installed "binary" with reported success.
Tried Superuser from Clockword Mod, no luck
Supersu crashed upon launching Titanium Backup w/ TB hanging.
It appears Supersu is not installed correctly.
What am i missing? Installing Supersu should be the easiest thing on an unlocked bootloader.
Click to expand...
Click to collapse
Hey, I just rooted a 4.4 the other day. I doubt it is much different. I flashed Official TWRP, made a backup, went to reboot system. TWRP then prompted me to root, I said yes, then installed SuperSu from play store

asuhoops8628 said:
Hey, I just rooted a 4.4 the other day. I doubt it is much different. I flashed Official TWRP, made a backup, went to reboot system. TWRP then prompted me to root, I said yes, then installed SuperSu from play store
Click to expand...
Click to collapse
just rebooted into TWRP, was not prompted to root.

Follow this -> http://forum.xda-developers.com/moto-x/moto-x-qa/instructions-unlocking-rooting-dev-ed-t2649738 it works and has the latest versions you need.

asuhoops8628 said:
Hey, I just rooted a 4.4 the other day. I doubt it is much different. I flashed Official TWRP, made a backup, went to reboot system. TWRP then prompted me to root, I said yes, then installed SuperSu from play store
Click to expand...
Click to collapse
KidJoe said:
Follow this -> http://forum.xda-developers.com/moto-x/moto-x-qa/instructions-unlocking-rooting-dev-ed-t2649738 it works and has the latest versions you need.
Click to expand...
Click to collapse
Followed them, still nothing. Basic Root Checker confirms no root. I used Terminal Emulator, and tried the su command, and it hangs up. Does SuperSU need an update??
Confirmed via ES File Explorer that Superuser.apk is in the /system/app folder.
Any other suggestions?

cpetersen2791 said:
Followed them, still nothing. Basic Root Checker confirms no root. I used Terminal Emulator, and tried the su command, and it hangs up. Does SuperSU need an update??
Confirmed via ES File Explorer that Superuser.apk is in the /system/app folder.
Any other suggestions?
Click to expand...
Click to collapse
would a factory reset help!

That thread has the exact versions of TWRP and SuperSU that I used to root, and countless others have rooted theirs on 4.4.2 as well using that process.
So I'm not sure what to say other than make sure you are using those versions from that thread (down load them again if you have to). And go into SuperSU, under settings, make sure default access is set to PROMPT, and remove anything that might be listed under Apps, reboot the phone, and try the root checker or other app that needs root again.
Another option is to un-install SuperSU via android's App Manager, reboot into TWRP, and try installing SuperSU again

KidJoe said:
Another option is to un-install SuperSU via android's App Manager, reboot into TWRP, and try installing SuperSU again
Click to expand...
Click to collapse
That did it, apparently i have 2 versions installed, and uninstalled one of them, then it fired right up. Thanks for the tip!

Related

[How to] Install SuperSU successfully on 4.3 without loosing root

Hello guys,
I want to share a pain reliever for many trying to upgrade Superuser with SuperSU without loosing root and successfully installing it's binary.
First you need a recovery for your Atrix HD which I recommend CWM Touch or a working up to date CWM recovery for other devices.
Download SuperSU-v1.43.zip file
Go to recovery and flash SuperSU-v1.43.zip
Go to any app that require root access to make sure is working. Once you see the prompt and hit ok or accepted it, go to Play Store and update SuperSU.
Once done, open it and when it ask you to install tje binary Normal install or by Recovery choose recovery and it should reboot to it. It will flash the binary (dont freak out if all you see is the loading bar)
Once flashed is done it will reboot the phone normally.
Confirm if SuperSU is working by opening back again SuperSU app and if you see everything as it should then job is accomplished and followed to the T.
Eventhough Superuser works great right now, SuperSU is few step ahead.

[Q] GPE 4.3 lost root and can't get it back [SOLVED]

Ok I got my phone new in July and fully converted it to the google play edition successfully. I rooted it as well and had no problems. Eventually the OTA for 4.3 came out and I lost root. I successfully got it back using superuser (clockworkmod version). After that the JWR66Y update came out in august or september. I didn't lose root on that OTA. Now my problem:
Last night I wanted to switch from superuser to supersu. I installed supersu from the play store. Supersu said it needed to update supersu so I let it. It failed. I then downloaded the latest clockwork recovery (6.0.43), flashed it and then tried to install UPDATE-SuperSU1.6.5.zip. No errors of any kind came up. I then rebooted the phone and I had no root. No superuser app and no supersu app. Running su from android terminal emulator causes the shell to hang.
I then booted back in to recovery and connected my phone to my mac. Ran adb shell and cleaned out all of the su crap. /system/xbin/su /system/bin/su /system/app/superuser.apk /system/app/supersu* /data/app/eu.blahblah.supersu.apk /system/xbin/daemonsu
After I did that I wanted to see if TWRP would work better. I flashed that (latest one from their site) and then tried to install the supersu zip again. Same thing as before with CWM.
Booted back in to recovery once again and manually deleted all of the su crap. I then tried to flash the zip flashable version of superuser (clockworkmod's). After I installed the zip then rebooted I got a message saying su needs to update. I try to update it and it fails.
So I really need to get root back. I don't care if its superuser or supersu or something else. Someone please help me with this. I'm completely stumped on the issue.
Thank you
Edit: missed deleting 3 files from /system/etc.
.has_su_daemon
.installed_su_daemon
instal-recovery.sh
Once I deleted those and reinstalled superuser.zip everything works now.

Problem with gaining SU access

Last week I rooted my phone at htcdev.com, installed CWM touch custom recovery, then flashed Android_Revolution_HD_Root_and_BusyBox.zip. When I ran SuperSU, I got the message "There is no SU binary installed, and SuperSU cannot install it. This is a problem." I have not try to flash a new ROM yet.
BTW, Fastboot is showing TAMPERED and UNLOCKED.
Was there something I missed?
Thank you for the help.
saint168 said:
Last week I rooted my phone at htcdev.com, installed CWM touch custom recovery, then flashed Android_Revolution_HD_Root_and_BusyBox.zip. When I ran SuperSU, I got the message "There is no SU binary installed, and SuperSU cannot install it. This is a problem." I have not try to flash a new ROM yet.
BTW, Fastboot is showing TAMPERED and UNLOCKED.
Was there something I missed?
Thank you for the help.
Click to expand...
Click to collapse
Download this and flash it in recovery the same as a rom
http://download.chainfire.eu/396/SuperSU
saint168 said:
Last week I rooted my phone at htcdev.com, installed CWM touch custom recovery, then flashed Android_Revolution_HD_Root_and_BusyBox.zip. When I ran SuperSU, I got the message "There is no SU binary installed, and SuperSU cannot install it. This is a problem."
Click to expand...
Click to collapse
This is a common problem. Reflashing SuperSU in recovery almost always resolves it. I keep the most recent recovery-flashable version of SuperSU on my phone for this very reason.
Also, ARHD and CWM don't always play well together. You should switch to TWRP if you're staying on that rom.
That worked, thank you.

Can't root LG-H811 20p because supersu soft bricks phone

So I connected my LG-H811 running stock ROM 20p to my PC successfully and ran adb and fastboot to transfer twrp and supersu over to the phone internal drive. So far so good. I couldn't get twrp to flash properly, so I simply did a temporary boot and got twrp to run without flashing it as a recovery. Then I used twrp to flash supersu (SuperSU-v1.94.zip). The problem is that when I try to reboot, it says the superSU binary is not installed. So I tried newer versions of supersu (SuperSU-v2.76-20160630161323.zip and SuperSU-v2.48.zip). Each time with these newer versions it soft bricked the phone again and required a full stock ROM restore. Specifically, it hangs either on the black LG screen or the white T-mobile screen, while the blue LED flashes on and off every few seconds. To unbrick it each time, I did a restore with stock ROM H811V20p_00_0913.kdz with LGUP. That got it working again with stock ROM, but no root. There must be a way to get superSU to install on 20p (and even get the twrp recovery to flash). I unlocked the bootloader, and it seems to load, so apparently that's not the issue. Thanks.
theprof7 said:
So I connected my LG-H811 running stock ROM 20p to my PC successfully and ran adb and fastboot to transfer twrp and supersu over to the phone internal drive. So far so good. I couldn't get twrp to flash properly, so I simply did a temporary boot and got twrp to run without flashing it as a recovery. Then I used twrp to flash supersu (SuperSU-v1.94.zip). The problem is that when I try to reboot, it says the superSU binary is not installed. So I tried newer versions of supersu (SuperSU-v2.76-20160630161323.zip and SuperSU-v2.48.zip). Each time with these newer versions it soft bricked the phone again and required a full stock ROM restore. Specifically, it hangs either on the black LG screen or the white T-mobile screen, while the blue LED flashes on and off every few seconds. To unbrick it each time, I did a restore with stock ROM H811V20p_00_0913.kdz with LGUP. That got it working again with stock ROM, but no root. There must be a way to get superSU to install on 20p (and even get the twrp recovery to flash). I unlocked the bootloader, and it seems to load, so apparently that's not the issue. Thanks.
Click to expand...
Click to collapse
have twrp .img in sd card and install click on image tab.. then select recovery and flash it.
once it flashes i just flash superSU and get root.
raptorddd said:
have twrp .img in sd card and install click on image tab.. then select recovery and flash it.
once it flashes i just flash superSU and get root.
Click to expand...
Click to collapse
Thanks raptorddd, but that's exactly the problem. I did flash superSU using twrp, and it seemed to install fine. I expected that I would simply get root as you say, but that's not what happened. The first time with SuperSU v1.94 newly installed, the phone rebooted normally, and the superSU app showed up, but it didn't work because it said there was no binary installed. The newer versions of superSU simply soft-bricked the phone. So I need a way to get superSU to work and not soft-brick the phone. Is there a preferred version of superSU for LG-H811 ROM 20p, or some obscure setting that makes it work?
theprof7 said:
Thanks raptorddd, but that's exactly the problem. I did flash superSU using twrp, and it seemed to install fine. I expected that I would simply get root as you say, but that's not what happened. The first time with SuperSU v1.94 newly installed, the phone rebooted normally, and the superSU app showed up, but it didn't work because it said there was no binary installed. The newer versions of superSU simply soft-bricked the phone. So I need a way to get superSU to work and not soft-brick the phone. Is there a preferred version of superSU for LG-H811 ROM 20p, or some obscure setting that makes it work?
Click to expand...
Click to collapse
did you open the app and clicked on update binaries.? if it asks to.?
here mine try this. then update from PS.
https://drive.google.com/file/d/0B90RfjoH13UEbDFBSG5XWVA0ME0/view?usp=sharing
raptorddd said:
did you open the app and clicked on update binaries.? if it asks to.?
here mine try this. then update from PS.
Thanks -- that's the the exact same version of superSU I used earlier (I even ran a diff, and the files are identical). After I flashed this version of superSU on the p20 stock ROM with twrp, it soft-bricked my phone. By that I mean it got to the boot page, and the blue LED pulsed on and off every few seconds, and it never got beyond that. When I flashed superSU v1.94, at least it booted afterward, but when I opened the superSU app, it didn't even give me the option to update binaries -- it just said the binary isn't installed, and so superSU can't run, it exited.
Maybe I'll try flashing an earlier stock ROM and see if that allows superSU to flash and run properly -- not sure which ones are compatible given the anti-rollback versioning.
Click to expand...
Click to collapse
theprof7 said:
raptorddd said:
did you open the app and clicked on update binaries.? if it asks to.?
here mine try this. then update from PS.
Thanks -- that's the the exact same version of superSU I used earlier (I even ran a diff, and the files are identical). After I flashed this version of superSU on the p20 stock ROM with twrp, it soft-bricked my phone. By that I mean it got to the boot page, and the blue LED pulsed on and off every few seconds, and it never got beyond that. When I flashed superSU v1.94, at least it booted afterward, but when I opened the superSU app, it didn't even give me the option to update binaries -- it just said the binary isn't installed, and so superSU can't run, it exited.
Maybe I'll try flashing an earlier stock ROM and see if that allows superSU to flash and run properly -- not sure which ones are compatible given the anti-rollback versioning.
Click to expand...
Click to collapse
try a custom kernel it has superSU installed.. i say imperium kernel.
try first the custom kernel.. if not you can only downgrade to 20o. no lower or youll hard brick phone.
Click to expand...
Click to collapse
OK so I finally got root. The key was to copy over this file to the phone's internal memory:
Imperium_Kernel_G4_H811_v4.8a.zip
Then:
adb reboot bootloader
fastboot boot twrp-3.0.2-0-h811.img
Then in TWRP, flash the imperium kernel. After that everything worked with root, though I still can’t get the twrp recovery to flash properly. Having root is good enough for now though.
EDIT: just now got TWRP to flash using flashify, so everything works. On to unlocking...
can you please share what guide you used to unlock and root this phone? I'm having issues on finding it, im on the newest update
theprof7 said:
OK so I finally got root. The key was to copy over this file to the phone's internal memory:
Imperium_Kernel_G4_H811_v4.8a.zip
Then:
adb reboot bootloader
fastboot boot twrp-3.0.2-0-h811.img
Then in TWRP, flash the imperium kernel. After that everything worked with root, though I still can’t get the twrp recovery to flash properly. Having root is good enough for now though.
EDIT: just now got TWRP to flash using flashify, so everything works. On to unlocking...
Click to expand...
Click to collapse
Please, can you share what guide you used to unlock and root this phone (20p)? Can not find any complex info anywhere.
Thank you.
theprof7 said:
OK so I finally got root. The key was to copy over this file to the phone's internal memory:
Imperium_Kernel_G4_H811_v4.8a.zip
Then:
adb reboot bootloader
fastboot boot twrp-3.0.2-0-h811.img
Then in TWRP, flash the imperium kernel. After that everything worked with root, though I still can’t get the twrp recovery to flash properly. Having root is good enough for now though.
EDIT: just now got TWRP to flash using flashify, so everything works. On to unlocking...
Click to expand...
Click to collapse
May I ask where you downloaded the Imperium_Kernel_G4_H811_v4.8a.zip
Did "fastboot boot twrp-3.0.2-0-h811.img" work?
What version of SuperSu did you install? I am planning on using "SR1-SuperSU-v2.78-SR1-20160915123031.zip"
king200 said:
May I ask where you downloaded the Imperium_Kernel_G4_H811_v4.8a.zip
Did "fastboot boot twrp-3.0.2-0-h811.img" work?
What version of SuperSu did you install? I am planning on using "SR1-SuperSU-v2.78-SR1-20160915123031.zip"
Click to expand...
Click to collapse
You can get the latest Imperium kernel (5.0 currently) from: http://forum.xda-developers.com/g4/orig-development/kernel-imperium-kernel-g4-v1-0-t3282915
Yes, fastboot boot from the twrp image was kind of a hack, but it worked. As for SuperSU, I tried v1.94 and SuperSU-v2.76-20160630161323.zip. Both soft-bricked the phone. Maybe the newest SuperSU will work, but I wouldn't count on it given that several previous versions didn't.
theprof7 said:
OK so I finally got root. The key was to copy over this file to the phone's internal memory:
Imperium_Kernel_G4_H811_v4.8a.zip
Then:
adb reboot bootloader
fastboot boot twrp-3.0.2-0-h811.img
Then in TWRP, flash the imperium kernel. After that everything worked with root, though I still can’t get the twrp recovery to flash properly. Having root is good enough for now though.
EDIT: just now got TWRP to flash using flashify, so everything works. On to unlocking...
Click to expand...
Click to collapse
I need to flash twrp and root from 20p also. One question to clarify exactly what you did,
Did you originally try flashing TWRP from TWRP? You said you flashed root from TWRP but I want to verify if you tried flashing TWRP from TWRP like:
> adb reboot bootloader
> fastboot boot twrp-3.0.2-0-h811.img
then in TWRP:
> install click on image tab.. then select twrp-3.0.2-0-h811.img recovery and flash it.
> reboot recovery (should reboot to TWRP you just flashed)
Just to be totally clear doing > fastboot boot twrp-3.0.2-0-h811.img leaves your stock recovery intact and just loads TWRP temporarily.
Or did you actually flash TWRP from TWRP and it didn't flash properly?
Thanks!
emailej said:
Just to be totally clear doing > fastboot boot twrp-3.0.2-0-h811.img leaves your stock recovery intact and just loads TWRP temporarily.
Or did you actually flash TWRP from TWRP and it didn't flash properly?
Thanks!
Click to expand...
Click to collapse
Yes, just loads TWRP temporarily. Later I installed some apps that flashed the recovery successfully, either rashr or flashify (I don't remember which)
I hope you have all the files and pc is reading your phone in adb.
Keep the downloaded twrp file in your adb folder with dwonloaded name (Ex:1234twrp.img)
Copy the file and keep in phone internal storage with names recovery.img
adb reboot bootloader (wait for phone to boot in bootloader ofcourse)
fastboot boot 1234twrp.img (whatever your twrp img file name would be)
Now you are in twrp recovery page in the phone.
Tap Install > Images (bottom right) > select recovery.img >
Now you are in next screen where options to slect recovery or boot
Tap recovery and swipe you will see [image flash complete]
Now twrp is permeant. You can restart in recovery without PC. (Tested)
I have flashed more than 6 methods to install supersu. Keep trying and reply.

SuperSU not installing

i have a nexus 5x that i want to root running on stock firmware unlocked.
when i try flashing the superSU installer zip in twrp it says
Code:
done
but when i reboot, there is no supersu app and root checker says my phone is not rooted.
any help? thanks
I'm sure that there's a whole bunch of output above that "done". Post a recovery log from the flash instead, it'll be so much more useful...

Categories

Resources