Kindle Fire 5th Gen cyangenmod superuser conflicting with supersu - Android Q&A, Help & Troubleshooting

I just purchased an Amazon Kindle Fire 5th Gen. Since I have the Jem and Tate version running cyangenmod I decided to install it on the 5th gen as well. Since the boot loader is locked I flashed with chain fire's flashfire.apk. Also the cyangenmod I flashed is not the official version but it is stable. So I ordered the command via flasfire to wipe followed by install rom finishing with install gaps pico version. So when the kindle rebooted it booted into cyangemod no problem but I quickly noticed I had no google play. So I went into flashfire again but when i did it gave me an error alerting me that either I was not rooted or was not using supers or cm su set to permissive. When I go into developer options I can see my SElinux is set to permissive and did enable root access for adb and apps. But when I checked root checker I was not rooted. So I installed Kingroot and gain root again but when I tried installing supersu it could not update binaries. I think its an conflict with cm su because it does sometime say it detected another su and tried uninstalling it but couldn't. Also I tried flashing su through fast boot but I can not get into TWRP temporally to do so. I keep getting...
$ sudo fastboot -i 0x1bbb boot TWRP_Fire_2.8.7.0_adb.img
Password:
downloading 'boot.img'...
OKAY [ 0.258s]
booting...
FAILED (remote: unknown command)
finished. total time: 0.260s
I tried this on boot my pc and mac to no avail. I stuck at this point I tried disabling the CM root but I get nowhere. I have no recovery image since my boot loader is locked so I can't ref lash. Flashfire won't work because I need su and CM root is conflicting with the install? Adb is working and fast boot seem too because i rebooted the device and it shows under fast boot.

Designassist said:
I just purchased an Amazon Kindle Fire 5th Gen. Since I have the Jem and Tate version running cyangenmod I decided to install it on the 5th gen as well. Since the boot loader is locked I flashed with chain fire's flashfire.apk. Also the cyangenmod I flashed is not the official version but it is stable. So I ordered the command via flasfire to wipe followed by install rom finishing with install gaps pico version. So when the kindle rebooted it booted into cyangemod no problem but I quickly noticed I had no google play. So I went into flashfire again but when i did it gave me an error alerting me that either I was not rooted or was not using supers or cm su set to permissive. When I go into developer options I can see my SElinux is set to permissive and did enable root access for adb and apps. But when I checked root checker I was not rooted. So I installed Kingroot and gain root again but when I tried installing supersu it could not update binaries. I think its an conflict with cm su because it does sometime say it detected another su and tried uninstalling it but couldn't. Also I tried flashing su through fast boot but I can not get into TWRP temporally to do so. I keep getting...
$ sudo fastboot -i 0x1bbb boot TWRP_Fire_2.8.7.0_adb.img
Password:
downloading 'boot.img'...
OKAY [ 0.258s]
booting...
FAILED (remote: unknown command)
finished. total time: 0.260s
I tried this on boot my pc and mac to no avail. I stuck at this point I tried disabling the CM root but I get nowhere. I have no recovery image since my boot loader is locked so I can't ref lash. Flashfire won't work because I need su and CM root is conflicting with the install? Adb is working and fast boot seem too because i rebooted the device and it shows under fast boot.
Click to expand...
Click to collapse
Well I fixed my own problem...well immediate problem. I tried several times to install supersu finally got it working. So flash fire works again. I realized the gapp zip was for 6.0 and I'm running lollipop 5.1. So i downloaded gapp from opengapps 5.1 mini and installed its working now. But I realized I have no recovery it got wiped while flashing with flash fire. Hope someone figures how to fix that issue.

Related

SGP561 - Help installing recovery to root

I got a replacement Tab from sony and I'm having trouble rooting it with the updated firmware. Seems the only real way to do it is to have a custom recovery installed, however I am having trouble with that. When I try installing a recovery through fastboot flash command I get an error FAILED: Remote: Command not Allowed.
The installer version of XZDual just hangs at install.
Has anyone else on Verizon tab found any other ways of rooting after the latest update?
Varekai said:
I got a replacement Tab from sony and I'm having trouble rooting it with the updated firmware. Seems the only real way to do it is to have a custom recovery installed, however I am having trouble with that. When I try installing a recovery through fastboot flash command I get an error FAILED: Remote: Command not Allowed.
The installer version of XZDual just hangs at install.
Has anyone else on Verizon tab found any other ways of rooting after the latest update?
Click to expand...
Click to collapse
You have to downgrade firmware off 4.4.4 and root,
Got it working. I didn't know I had to have the unknown sources checked. Also I didn't realize I was plugged into a 3.0 port in the back of my PC, so that didn't help. Thanks for the help.
I have a Verizon Z2 LTE SGP561 with the latest update of 4.4.4 and i managed successfully to Root it with the latest KingRoot apk.
It was very easy - just download the KingRoot apk to your device , run it from the device and it will do the work.
After it will complete you will have KingRoot user which is the superuser app for permission, no need to install SuperUser of SuperSU.
I checked with root-checker to verify and indeed it was rooted.
even though the bootloader is locked you are rooted.
I managed to remove all Verizon bloatware apps.
You can find the latest KingRoot apk in the following link:
http://downloadandroidapkget.blogspot.co.il/2015/05/download-kingroot-apk-latest-version.html
Varekai said:
I got a replacement Tab from sony and I'm having trouble rooting it with the updated firmware. Seems the only real way to do it is to have a custom recovery installed, however I am having trouble with that. When I try installing a recovery through fastboot flash command I get an error FAILED: Remote: Command not Allowed.
The installer version of XZDual just hangs at install.
Has anyone else on Verizon tab found any other ways of rooting after the latest update?
Click to expand...
Click to collapse
Thanks, I'll try this if I get another replacement device. This one has a dead pixel in it.

Bootloop after every root attempt.

So as written in the title, i've tried flashing different Supersu versions. I also tried doing so on official oxygen os, cyanogenmod 13 and now currently using paranoid CM, it would get stuck in a boot loop everytime i tried to flash supersu. Any help there ? I'm sure i haven't got root access already !
gabytzu339 said:
So as written in the title, i've tried flashing different Supersu versions. I also tried doing so on official oxygen os, cyanogenmod 13 and now currently using paranoid CM, it would get stuck in a boot loop everytime i tried to flash supersu. Any help there ? I'm sure i haven't got root access already !
Click to expand...
Click to collapse
What version you using? You want 2.65 or higher .
Try the latest beta SuperSU and you will have no problem at all!
Thank you very much guys ! I've initially tried to flash 2.52, 2.56 and 2.65, none of them worked, it went well with 2.72 or w/e is that last one .
Try to change that supersu zip file and try other versions
If you haven't unlocked the bootloader then it won't boot into a modified system. To unlock the bootloader you need to reflash the stock recovery from here: https://s3.amazonaws.com/oxygenos.oneplus.net/OPX_recovery.img. Once flashed, boot into OxygenOS, go to settings, go to About Phone, tap on "build number" until it says that you're a developer. Back to settings, go to Developer, and turn on OEM unlock. Now boot into Fastboot, and on the computer you used to flash TWRP in the first place, use the command "fastboot oem unlock". Then you can flash TWRP and use whatever rom you like or flash SuperSU on OOS.

Bricked HDX 7, safestrap 4.01 (TWRP v2.7.1.0)

Just got my new to me hdx 7 in the mail, decided to root and install nougat..
Downgraded to 4.5.2 and installed root via kingroot.
Was having problems unlocking the bootloader so I found a method to install cm11 withoutunlockijg bootloader. I got safestrap installed, and installed lineage 14 instead of cm11, and then got stuck in recovery loop, tried factory reset (mistake), and all the unbrick utilities I could find... im so frustrated with this can anyone help please?
updates
adb devices shows
+
D0FBA0A034540445 recovery
keep getting su not found so im assuming the root is no longer good.. please anyone??
SOLVED
Ok I was able to fix this with searching and trial and error, it took me about 5 hours total but all i did was adb push 4.5.5.1 stock rom and it works now.. making backups for now on!!!! thanks anyway !

rooted OPX and now phone no longer has root but, has su and locks up

is there anyway to re root it without having to factory reset? i still have twrp / fastboot installed
okay i update super su binaries with fastboot i think it's is a problem with root/super su not loading first when booting up. all the apps and stuff try to load first before super su and root and don't see root/su and get all crashy and hangy.
flash magisk for root

My RMX1851 stuck on logo boot screen after flashing SUPERSU

I successfully flashed TWRP 3.4.0.0 and flashed patched image using magisk, the phone was successfully rooted and I used it as well.
I downloaded SUPER SU apk but showed up "SU binary occupied" so I downloaded an older version that asked me to flash it using either TWRP or without TWRP, firstly I chose without but it failed, so when I chose with TWRP the phone rebooted and still stuck on realme logo!
Tried many solutions but failed, so I hope anybody could help me.
NOTE: realme logo stays for about 70 seconds then it turns into FastBoot mode automatically.
*Tried this one
https://forum.xda-developers.com/2015-moto-g/help/problem-boot-flashing-supersu-t3507127
But in vain

Categories

Resources