After installation custom rom (and then stock again) root installer cannot uninstall application (uninstall failed). Phone is root, and there is no other problem with root access. Btw, after that message from root uninstaller application dissapear, but it's still there when I looking in settings>apps>all (but i cannot open it, and it is not the same icon). When I reboot phone app disapeared from settings>apps>all too.
I tried several root uninstaller application!
This is not was happened when I was root official stock rom for first time...
Does anybody know about that problem?
Thx!
Here is how to root the new BLU Life One, there are probably many ways to do it but this was the best way that I could find.
Note that I tried to root with framaroot, towelroot, and iroot and their apps have failed.
Try this of your own free will, I am not responsible for anything happening to your device (it worked for me so it should work for you).
What you will need:
kingoroot, supersu, busybox, root checker, and titanium backup.
First things first,
Go into settings and check the box next to "Unknown sources".
Next open up the internet tab and search for Kingoroot (kingorootapp dot com)
Click the download button for android (not the windows one)
When it finishes downloading, click in the drop down menu and install the apk.
Open the kingo root app, and click root circle.
After the app is finished rooting your device, you can download Root checker in the play store to ensure that your device is indeed rooted.
Now, I personally don't like kingo root, so the next steps are optional.
In the play store download three apps, SuperSU ( i use chainfire), busybox, and titanium backup (i suggest buying the paid version, it is well worth the money).
Next open up SuperSU (KingoUser should ask to grant SuperSU root access, allow it), and install the SU binary. Do not reboot system.
Next open titanium backup, click the middle tab, then scroll down until you see SuperSU. Long press, and then press install to system apps. (you can do this manually by using ES file explorer and copying the SuperSU.apk file [may need to download it from the internet] in to the/system/app folder.
Now restart your device.
When the device boots back up, check and make sure that your device is still rooted by using root checker again.
If it is still rooted, open SuperSU and make sure you dont have to install the binarys again (you shouldnt have to).
Next uninstall the kingo root app (it will not let you uninstall the kingouser app, for this you must use titanium backup)
Now go into your system, applications and then disable kingouser app.
After doing so, check and see if your device is still rooted (it should be)
If it is still rooted, proceed to use titanium backup to uninstall kingouser app.
Lastly install busy box. If you get an error saying "unable to install choose another location" simply click on where it says "/system/xbin" and change it to "system/bin".
And there you should have a freshly rooted device with no kingoroot. Not saying Kingoroot is bad, i just have always used SuperSU
Credits:
To the developers of kingoroot, supersu, busybox, root checker, and titanium backup!
ikpb said:
Here is how to root the new BLU Life One, there are probably many ways to do it but this was the best way that I could find.
Note that I tried to root with framaroot, towelroot, and iroot and their apps have failed.
Try this of your own free will, I am not responsible for anything happening to your device (it worked for me so it should work for you).
What you will need:
kingoroot, supersu, busybox, root checker, and titanium backup.
First things first,
Go into settings and check the box next to "Unknown sources".
Next open up the internet tab and search for Kingoroot (kingorootapp dot com)
Click the download button for android (not the windows one)
When it finishes downloading, click in the drop down menu and install the apk.
Open the kingo root app, and click root circle.
After the app is finished rooting your device, you can download Root checker in the play store to ensure that your device is indeed rooted.
Now, I personally don't like kingo root, so the next steps are optional.
In the play store download three apps, SuperSU ( i use chainfire), busybox, and titanium backup (i suggest buying the paid version, it is well worth the money).
Next open up SuperSU (KingoUser should ask to grant SuperSU root access, allow it), and install the SU binary. Do not reboot system.
Next open titanium backup, click the middle tab, then scroll down until you see SuperSU. Long press, and then press install to system apps. (you can do this manually by using ES file explorer and copying the SuperSU.apk file [may need to download it from the internet] in to the/system/app folder.
Now restart your device.
When the device boots back up, check and make sure that your device is still rooted by using root checker again.
If it is still rooted, open SuperSU and make sure you dont have to install the binarys again (you shouldnt have to).
Next uninstall the kingo root app (it will not let you uninstall the kingouser app, for this you must use titanium backup)
Now go into your system, applications and then disable kingouser app.
After doing so, check and see if your device is still rooted (it should be)
If it is still rooted, proceed to use titanium backup to uninstall kingouser app.
Lastly install busy box. If you get an error saying "unable to install choose another location" simply click on where it says "/system/xbin" and change it to "system/bin".
And there you should have a freshly rooted device with no kingoroot. Not saying Kingoroot is bad, i just have always used SuperSU
Credits:
To the developers of kingoroot, supersu, busybox, root checker, and titanium backup!
Click to expand...
Click to collapse
Hi, thanks for this info, works for me. You should publish this info in the official Blu Life One thread. Thanks again for this.
if someone here has a working blu life one 2015, could you do a rom dump. a bunch of us have soft bricked phones and can't get them working. Blu doesn't have the stock rom available
Hey thanks for this guide! I have one problem I'm hoping you could shed some light on. I've followed your steps and when I try to update the SU binaries it fails every time. The kingroot worked and the kingroot su asked if I wanted SuperSu to have root access and I selected yes. Each time it fails to update it suggest I reboot and try again, but I haven't yet.
Thanks again
Robert
Dear forum
This dang SCH-i435 Verizon s4 was rooted by that kingroot apk, then I saw mentions of software sources and concerns. I down loaded , instantly rooted my phone some apps like apps to SD and other would work. But it seemed like kingroot was protecting
The root mod and wouldn't all supersu or any rom installer to install. What the S--t is this kingroot. I found a couple links using terminal to have su open on screen and then type ( sd /sdcard/mrw/root.sh) worked it deactivated king root and installed that supersu.
Search your favorite search engine for ( replace Kingroot with Supersu apk) I was a little chicken at first but it went and rooted the phone.
I unistalled kingroot and all
Addition software be sure to look for kingroot in you software there maybe numerous references in different apps???like it
Added shortcut references to root too root cleaner bricked my phone until I rebooted phone. Be sure your backups and clouds are free of this kingroot apk. I am becoming nervous about this free app being available.
Doug
If you don't know what the app "PhotoTAN Raiffeisen Schweiz" than this is probably not interesting for you.
I'm just writing this to confirm that the aforementioned app can be run on rooted devices. First I tried several of the root hiding apps in the market, but for all I tried, the app still detected root and deleted the credentials.
The next thing I tried was suhide which left my Tab S2 (T810, 6.0.1, rooted) in a boot loop.
I ended up trying Xposed with RootCloak (Xposed Guide for S7: http://forum.xda-developers.com/ver...-to-notes-root-install-xposed-unroot-t3411039). Installing Xposed using FlashFire didn't work for me, so I copied the zip to the external sd and installed using TWRP. In Xposed I installed RootCloak and added the app to the apps root should be hidden from.
After a restart, I can now use the app without an issue and I can also backup/restore the credentials using TitaniumBackup.
I hope, this helps someone and I hope the devs of the app don't read this and fix the app.
Using Titanium Backup I also detached the app from the market, so I'll not get automatic updates.
I was able to use Kingoroot for PC to root my Fire HD 10. Updated to the newest Firmware. It would say it was rooted. But, Trying to give permissions and checking with root checker was not successful and said there was no root. I installed SuperSU apk it says the binary is occupied. So I Uninstalled the superuser apk. that was installed by Kingoroot and tried to change the build prop with a root browser text editor and it was successful so apparently it roots but superuser is not working to grant or deny permissions. It automatically grants permissions does not even open up superuser so its kinda dangerous but it is rooted and working. My experience is that kingoroot superuser must be Uninstalled for root to work. I used twrp manager to backup my recovery img., and boot img. I am going to try to build a recovery for it but I'm not In a hurry plus I'm not sure if it will flash afterwards anyways but if you want root, Kingoroot for pc and Uninstalled the kingoroot superuser apk it installs and you will have it
Installed magisk manager installed zip direct (recommended) it bricked the fire. And then I adb sideloaded the update and now I'm back in business reasonably easy to do but I do not recommend magisk at this time .
Going to try xposed next
Couldn't get it to install says it's arm device tries to install and says it's an arm64 device. Plus has to be flashed in recovery and one hasn't been built yet
You can't manage Kingoroot su binary using SuperSU.
If you not install SuperSU su binary, SuperSU apk does not working.
Try this method to install SuperSU su binary.
https://forum.xda-developers.com/showpost.php?p=75242414&postcount=99
erono said:
You can't manage Kingoroot su binary using SuperSU.
If you not install SuperSU su binary, SuperSU apk does not working.
Try this method to install SuperSU su binary.
https://forum.xda-developers.com/showpost.php?p=75242414&postcount=99
Click to expand...
Click to collapse
I installed supersu to find out if it was rooted since the root checker said it was not. the binary error was a confirmation that it was in fact rooted and it doesn't matter what superuser is used it will not allow pop up or apps to draw over other apps so when it's rooted with kingoroot it automatically grants root without a confirmation,as long as the kingoroot super user app is not installed and if SuperSU is kept installed default permission has to be set to grant for root to work. I in fact installed the SuperSU binary through an older version of the apk and it installed but still has no control over denying or granting permissions. Thanks for the advice though. I appreciate your willingness to help me
Joker1716 said:
I was able to use Kingoroot for PC to root my Fire HD 10. Updated to the newest Firmware. It would say it was rooted. But, Trying to give permissions and checking with root checker was not successful and said there was no root. I installed SuperSU apk it says the binary is occupied. So I Uninstalled the superuser apk. that was installed by Kingoroot and tried to change the build prop with a root browser text editor and it was successful so apparently it roots but superuser is not working to grant or deny permissions. It automatically grants permissions does not even open up superuser so its kinda dangerous but it is rooted and working. My experience is that superuser must be Uninstalled for root to work. I used twrp manager to backup my recovery img., and boot img. I am going to try to build a recovery for it but I'm not In a hurry plus I'm not sure if it will flash afterwards anyways but if you want root, Kingoroot for pc and Uninstalled the superuser apk it installs and you will have it
Installed magisk manager installed zip direct (recommended) it bricked the fire. And then I adb sideloaded the update and now I'm back in business reasonably easy to do but I do not recommend magisk at this time .
Going to try xposed next
Click to expand...
Click to collapse
Not trying to insult your intelligence or anything here, but you said newest firmware? Newest Fire firmware? Newest firmware isn't rootable from my understanding.
What firmware were you on when you started the root process?
Also, are you making sure that the Kingoroot "install our extra junk" box isn't checked (not sure that would prevent root success)?
It wouldn't open superuser. superuser should be set to "grant" because of how the Fire works, which it sounds like you are aware of based on your last post. I wouldn't say it's dangerous, per se.
I've followed this guide nearly a dozen times now and I've not run into the issue(s) you're having.
smam1338 said:
Not trying to insult your intelligence or anything here, but you said newest firmware? Newest Fire firmware? Newest firmware isn't rootable from my understanding.
What firmware were you on when you started the root process?
Also, are you making sure that the Kingoroot "install our extra junk" box isn't checked (not sure that would prevent root success)?
It wouldn't open superuser. superuser should be set to "grant" because of how the Fire works, which it sounds like you are aware of based on your last post. I wouldn't say it's dangerous, per se.
I've followed this guide nearly a dozen times now and I've not run into the issue(s) you're having.
Click to expand...
Click to collapse
Prompt dialog not working in amazon fire devices.
erono said:
Prompt dialog not working in amazon fire devices.
Click to expand...
Click to collapse
Set prompt to grant and fixed.
yes. mind doesnt pop up supersu granting notification too
my fire hd 10 is on 5.6.1.0
someone told me it's amazon's own security measure
stevenchun said:
yes. mind doesnt pop up supersu granting notification too
my fire hd 10 is on 5.6.1.0
someone told me it's amazon's own security measure
Click to expand...
Click to collapse
One can try this improvement :
SuperSU access workaround for Fire devices
https://forum.xda-developers.com/hd8-hd10/general/supersu-access-workaround-fire-devices-t3738269