Problems to install SuperSU - Amazon Fire Phone

Hey xda,
i have some huge problems to install SuperSU.
My original goal was to install xposed and if i'm correct, i need super su for it.
To give you some basic informations.
I have an Firephone with 4.6.6.1 on it and tried the following thing:
http://forum.xda-developers.com/fire-phone/general/root-fire-phone-supersu-t3105546
http://forum.xda-developers.com/fire-phone/help/fire-phone-supersu-xposed-framework-t3392804
http://www.w0lfdroid.com/2015/05/How-to-Remove-Replace-KingUser-KingRoot-with-SuperSU.html
At point 1, i failed at Step 7.
For Point 2, Super SuMe starts but this was all, no progress.
Point 3 installed SuperSu but it won't work at all.
So i'm little bit depressed and have no idea what to do now.
I would like to keep stock firmware, but would have no problems to flash TWRP or anything like this and flash SuperSU, if It's possible.
Maybe some of you have an idea or the same problems with a solution.
GadH
Rathi1985

Related

[Q] Hot to root, install recovery and ROM on a SM-T805? Confusing info out there!

Hi there,
I have a SM-T805 from a few months, and I grew tired of its lags and sloppiness. I've tried to read many threads to find the most simple way too root, install TWRP and a ROM, but most of the threads are old and quite confusing.
So... could someone please tell me, step by step and with the proper links, how to ROOT and install TWRP in the easiest and most safe way?
Thanks a lot!
davidrf said:
Hi there,
I have a SM-T805 from a few months, and I grew tired of its lags and sloppiness. I've tried to read many threads to find the most simple way too root, install TWRP and a ROM, but most of the threads are old and quite confusing.
So... could someone please tell me, step by step and with the proper links, how to ROOT and install TWRP in the easiest and most safe way?
Thanks a lot!
Click to expand...
Click to collapse
You don't need to ROOT 'AND' install TWRP.
Just install TWRP and it will root for you.
You can use the version below if you wish which I built, I have updated the Super su root files and fixed an issue with the wrong reboot option showing - BOOTLOADER instead of DOWNLOAD mode.
Just install via ODIN then boot into TWRP, select reboot from within TWRP and it will ask if you wish to root your device. After that your device will be rooted with the latest updated root.
unofficial-twrp-2.8.5.0-chagall
Did it and installed Iron Rom. Thanks a lot
I have one problem... after I installed TWRP and rooted, with ANY rom I install, included the original one, I get the "no connection" error with every single app from google. In other words, I can't use the tablet. It's like Google knows the tablet is rooted and blocks it. How can I solve this?
Try resigning into your Google account. If that doesn't work clear cache and data for Google play services.
Sent from my SM-T805 using XDA Free mobile app
I found out that when I'm rooted, Android automatically sets my wifi connection behind a non-existent proxy. This happens in EVERY ROM I install, from the original one to Cyanogen. I just have to disable that proxy and everything works. WTF.

[Q] SCH-I435 (Verizon) Anyway to get custom recovery?

Hello everyone, please be patient with me as I am relatively new to modifying phones. However, I have spent a good portion of the past 1-2 weeks looking into this problem on XDA + google, and I am at the end of my rope.
Here is my problem (I'm sure you already know):
I have no current solution to installing a custom recovery on my phone. I really just want custom recovery to restore FULL backups via Nandroid or equivalent.
Here are my questions:
1) In download mode, Odin has no problem flashing an official image/firmware (tar.md5) to the phone. Is it possible to create my own image of my phone into one file and flash it via Odin to my phone when I would like to restore? I have a feeling that something in the phone checks the hash of the image (I'm sure that I'm not saying it right), and that, considering my image would be twice the size of the official, there would be no way to make my image pass using collisions or what not. However, this would probably be my first choice after safestrap (assuming that won't work), so let me know.
2) I have read that certain people with phones similar to mine (not my variant though) have successfully "swapped" the external and internal SD cards. If I remember correctly they just change a couple lines in void.fstab. If this could actually be done, I could easily restore a backup to the now external internal SD, then change the settings to reswap on reboot. I feel like this is too good to be true though, as I have not seen this as a solution to my specific problem online. Is this actually a suitable option?
3) Currently my phone model is not an officially recognized device which Safestrap will work on. However, I have read that it is possible to do on my model using the Safestrap version which corresponds to a close variant of my phone. Can this be done? Please let me know if you have any information on this.
4) I guess this would be the last resort. I'm pretty good at taking things apart, but even better I can put those things back together Is the internal "SD" really just an SD card deep inside the phone? Would it be possible to replace that card for the purpose of backing up?
Here are my phone specs:
-Samsung Galaxy S4 Mini (SCH-I435)
-The carrier is Verizon Wireless
-Android Version 4.4.2 (kitkat)
-Baseband Version I435VRUBOC1
-Kernel Version 3.4.0 [email protected] #1 Fri May 23 2014
-Build Number KOT49H.I435VRUBOC1
-Hardware Version I435.05
-Configuration version B13.SAM.SCHI435.0
-Needless to say, phone is rooted and has busybox + etc correctly installed.
Any help will be greatly, GREATLY appreciated -- even if that help is telling me that it isn't possible. I can't seem to give up on this.
Thanks,
Kurt
Help
Does anyone have any advice on this? I would REALLY appreciate it. Thanks again.
-Kurt
I'm also interested on this. Thanks for your efforts
Nope no recovery because the Verizon minis bootloader is locked. It can be rooted with kingroot i think its called and then switched to SuperSU by replacing it.(I used super sume pro to get rid of kr) ****!!After root install a application like "disable application [root]" and disabe all Knox applications and any unused apps.(look for a list of recommended apps to disable)
Kannz2 said:
Nope no recovery because the Verizon minis bootloader is locked. It can be rooted with kingroot i think its called and then switched to SuperSU by replacing it.(I used super sume pro to get rid of kr) ****!!After root install a application like "disable application [root]" and disabe all Knox applications and any unused apps.(look for a list of recommended apps to disable)
Click to expand...
Click to collapse
How did you switch it over to SuperSU? I tried, but when it tried updating the root binaries it couldn't continue because of KNOX, so I was stuck with Kingoroot's.
I used this method to replace KINGROOT NewKingrootV4.50_C120_B220_xda_release_2015_07_22_105243 with supersu. most other versions i tried didnt want to cooperate and would make me lose root after one reboot. also i bought the pro version of supersume pro its 4$ off google play.
Kannz2 said:
I used this method to replace KINGROOT NewKingrootV4.50_C120_B220_xda_release_2015_07_22_105243 with supersu. most other versions i tried didnt want to cooperate and would make me lose root after one reboot. also i bought the pro version of supersume pro its 4$ off google play.
Click to expand...
Click to collapse
I tried it with the free version they linked to and it de-rooted it, so maybe I'll try later when I have enough Opinion Rewards credit to get the pro version. That or it doesn't work on this phone with Kingoroot. (The Google Play description says it should do Kingoroot though.)
Did you download the correct version? The one off the kingroot site doesn't work for me. It just deroots. I still have root on both of my s4mini Verizon phones. Try this link to get a working one.HERE scroll down a bit and the different versions are there. Try each one starting with 4.5. Also remember to restart after you root with kingroot and install super sume after the restart.
I just had to re-image my phone, so I did it according to your directions. (Though with the free version still of super sume) and it worked, although it won't update to the newest root binaries. It fails when I try. Did you have this issue? Other than that, SuperSU works.
I updated using "normal" and it worked fine for me. Glad su works at least. also for one phone I did a full unroot factory reset and then I reflashed a tar with Odin. Did the normal root with kingroot 4.5. Restarted tried a few root things like no frills cpu thing then installed super sume pro. Did stage 1. An 2 then supersu started up automatically it asks to update (I think net connection is needed) *do update "normal" because there isnt any recovery. Uninstalled kingroot like supersume says. Did a few root things then restarted. (Checked for superuser after reboot and it stayed)

[Q] Fire Phone: SuperSU-me, Xposed Framework and other Issues

Hi,
I just got a fire phone and I'm facing multiple issues. It updated to 4.6.6.1 once i started it. Now I want it to act like a normal android phone so I installed google now launcher.
Next thing i wanted to do is to customize the laucher. So I did research how to root it. Did it with kingroot and afterwards followed various instructions to change to superSu. Non of them worked. Neither via adb nor SuperSU me nor the terminal version. only rooted when on kingsroot. SuperSU binaries also would never succesfuly update. Anyways.
So after I got the root, I wanted to install Xposed Framework to finally customize the launcher. Now xposed is saying, that it is not (yet) compatible wit the ANdorid SDK Version 19 or my Prozessor architecture. (armeabi-v7a)
I'm running the phone on german language. Don't know what to do anymore with both. SUpersu and Xposed. Appreciate any help.
So you already bought Super-Sume-Pro? Good, because removing / replacing Kingroot was possible even with the (early) free version of Super-Sume (9.1.6).
Download this old version* of Kinguser.
Yes, like always, it's classified as a virus / exploit / PUP, because it uses very aggressive methods of achieving root.
"But Bingo, this is only Kinguser, I need Kingroot."
No you don't. I used this combo many times, it always worked, from the latest version down to Fire OS 4.6.1 when I first tried it.
Uninstall your current version of Kingroot / Kinguser and remove the leftover folders from the internal storage.
Install the old version (disable auto update within in the app, it can be quite annoying), let it "achieve" root, disable WiFi if you want.
Run Super-Sume. It will have no problem replacing Kinguser with 2 steps.
Download this compatible version of the Xposed Installer.
Install framework, etc. You know the drill.
For BusyBox, I'd recommend either Stericson's version or Meefik's.
I tested one of my devices with 4.6.6.1 and the above mentioned customizations (mainly to enjoy microG on Fire OS ^^), so I can say it definitely works.
* Had to use OCH, because the "good guys" like Dropbox and Google Drive won't allow hosting / linking this file, since it's a bad azz virüs.
I always found W0lfdroid's script to be quite effective and efficient in removing Kingroot:
http://www.w0lfdroid.com/2015/05/How-to-Remove-Replace-KingUser-KingRoot-with-SuperSU.html
Plonko said:
I always found W0lfdroid's script to be quite effective and efficient in removing Kingroot.
Click to expand...
Click to collapse
Ugh, so many letters, I'm so confused, please... no more, let's stay with "dumb it down". This saves time so I can roll around in my own feces. :victory:
Plonko said:
I always found W0lfdroid's script to be quite effective and efficient in removing Kingroot:
http://www.w0lfdroid.com/2015/05/How-to-Remove-Replace-KingUser-KingRoot-with-SuperSU.html
Click to expand...
Click to collapse
W0lfdorid was one of the versions i tried. no success. I can start the script but then it says failure and every single steps fails. I finally made it to the supersu installed, but it wont update the binaries. installation always failed
coolni said:
W0lfdorid was one of the versions i tried. no success. I can start the script but then it says failure and every single steps fails. I finally made it to the supersu installed, but it wont update the binaries. installation always failed
Click to expand...
Click to collapse
Hmmmm...I don't know what to say. I just used it today after returning a phone to stock Fire OS for my niece. The only thing I can think of is I'm using an earlier version of Kingroot? I'm using KingRoot-4.1.0.524.apk if that matters. I can try to PM it to you, but I'm not sure it will work because, as Bingo mentioned, it is seen as a virus by most servers.
Yup, I also used the oldest version I had on my PC, this way I can avoid the cat and mouse game between Kingroot and Super-Sume ^^ ... well, for the Fire Phone and some "older" KitKat devices that is.
But since 'coolni' popped his Fire Phone cherry just recently, he naturally went for a current version of Kingroot and he's also on the latest Fire OS release; thought process = better bring the big guns so that root is guaranteed.
Bingo Bronson said:
Yup, I also used the oldest version I had on my PC, this way I can avoid the cat and mouse game between Kingroot and Super-Sume ^^ ... well, for the Fire Phone and some "older" KitKat devices that is.
But since 'coolni' popped his Fire Phone cherry just recently, he naturally went for a current version of Kingroot and he's also on the latest Fire OS release; thought process = better bring the big guns so that root is guaranteed.
Click to expand...
Click to collapse
can anybody help to root 4.6.6.1 ?
Kingroot 4.0.0.233 from zip file did not work on my phone with 4.6.6.1.
Having problems on custom recovery
Hello sir I am using amazon 4.6.6.1 almost 1 year ago I have backed up my custom recovery from flashify and deleted accidentally now I need that but can't do anything I have tried most things to get back but can't and also can't root my phone with king root I am installing it but it's saying that app not installed any solution please my email is [email protected]

Oukitel K10000 Pro Rooting + Magisk Manager problem

Hey guys. Im new to this whole android rooting world, so i have a problem.
I rooted a phone with instructions i got from needrom.com.
I tried to flash it first with flash tool, but it always stops to an error.
Don't really know what im doing wrong.
So, anyway. I got now twrp installed, phone is rooted and magisk manager installed partly.
Reason i wanted to root this, is to spoof at pokemon go, so my disabled daughter can enjoy the game too, as my son and i am already.
But, as you know pokemon go wont work with rooted device straight, so i wanted to install magisk manager to hide root from pokemon go.
But phone wont flash to magisk manager version 14. It gets error too. With its own installer, and through twrp recovery mode too.
I was able to flash version 12.5 with no problems at all. But then i tried 13.5, and it gets the same error too.
Now i dont know what do i do. I can't make pokemon go to work at all on that device anymore. I tried to unroot from SuperSU, but then pokemon go said that:
This device OS or software is not compatible with Pokemon GO.
So i restored a backup with twrp. Its now rooted again.
I would like to get the Magisk manager to work properly of course. Please help me guys.

Unable to root - not sure why

For some reason I am having a heck of a time getting root to work on this tablet, I can't even figure out what I am doing wrong. I followed the steps here: http://www.**********.com/root-galaxy-note-10-1-sm-p600-and-install-twrp-on-it/ and everything completes as expected. But, when I install a root checker , it reports the device is not rooted. Super SU gets installed, but if I try to open it I just get a message "SuperSU isn't responding" and it never starts.
I am running this ROM https://forum.xda-developers.com/ga...-resurrection-remix-5-8-3-lt03lte-14-t3621927 but want to get root access. I have TWRP installed, but again, no matter what I try, root does not seem to take.
Any idea why? I am sure I am just missing something stupid somewhere, but cannot figure out what exactly
Thanks.
Edit - OK, managed to instead install Magisk via TWRP and all good now.

Categories

Resources