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)
Related
[Q] Root "disabled" itself!? (Rooted phone that is no longer allowing root access)
Anyone here with this phone (or any) - that is rooted - have it just seemingly act as if it is no longer rooted? or unjustly denying root access for no apparent reason....
Have been rooted since purchase and have never seen or had any issue with this..have flashed custom recovery and rom's hundreds of times...no problems...currently using Task's latest KK 4.4.4 rom and had no issues from beginning...
It comes with SuperUser...i do usually install SuperSU instead but hadn't tried yet...it was fine and apps that needed root appeared ok..even SuperUser has three or four listed apps in the "allow" section...but all of a sudden I can't seem to give root access to anything else now..
First noticed the other day when trying to sideload an apk..couldn't...tried to do it manually by just copying it to system/apps folder and that's when the first message came up saying "it appears your device may not be rooted"...quite odd I thought.. i then tried to install SuperSU and it when SuperUser popped up to give it allowable root access it would only timeout and say denied...i then tried a bunch of other apps that require root and they would all just get denied by SuperUser...
Anyone seen this before or know what causes this and/or how to fix?
THanks for any help or suggestions
ps.. i'm no noob and have been doing this a long time and have rooted/modded dozens of phones, hundreds of times...but this issue is a new one for me.. IF i have to completely wipe and even go back to stock image and then start over to re-root and re-mod... I will and can do so easily..but that would be last resort if necessary...thanks!
In SuperSU, try the clean-up for reinstallation option.
DocHoliday77 said:
In SuperSU, try the clean-up for reinstallation option.
Click to expand...
Click to collapse
when launching SuperSU it needs root access to begin with and SuperUser wont allow..this clean up for reinstall is still doable?
Get the recovery flashable SuperSU then. It'll get rid of the other one in the process. You can get it from my sig, but it'll need to be updated after.
Hi, I'm super new to this I have no clue what I'm doing, but I did manage to follow the instructions of http://forum.xda-developers.com/gala...-t800-t3079488 and get my t800 rooted.
Until problem occurs, at http://techbeasts.com/2015/05/01/roo...-lollipop-502/ step 9 "Once it has booted up, check out the SuperSu application in the app drawer. If it asks you to update SU binary, update it." When I open supersu app it only ask me to follow someone on google+ but didn't mention anything about update, couldn't find an update option anywhere in the app either.
I ignored this potential problem and then downloaded rootvalidator, everything was green only busy box was yellow and SELinux was blue saying something enforcing, I don't have a screenshot but these 2 were the only one that's not green. I installed busybox free and got busybox in rootvalidator green (from yellow). Not sure if the enforcing part was an issue so I left it like that.
So I use this guide to root t800 is to use xmod, and XMOD actually have their own tutorial on how to root and install and get it to work etc. just didn't have one for this model. I think I made a huge mistake of following their guide after this one, and got mislead not knowing wtf is going on..
I installed xmod and found out it isn't working, I installed kingroot from within xmod app and when I opened kingroot it shows my tab is already rooted. So I was sure it's not a rooting problem, I then found out xmod isn't working because SE is enforcing and I followed the video guide (from xmod faq) on how to make xmod work on enforcing device. I downloaded Link2SD and clear data+ unistalled xmod. But I also clear and unistalled kingroot (and kinguser i think?) and another app that came along with kingroot when i got it (It was in chinese)...
After this I lost root access and when I check rootvalidator it show my device is not rooted anymore. When {I click on supersu it asks me to update normal or from twrp/cwm...
Everything seem to be a mess so I'd like some advice is it better for me just to restore everything back to factory settings and root the device again? Sorry for this long and noob post I'd really appreciate if someone can help me out. Thank you so much!
Edit: Hey Ashyx thanks for replying so fast, I can't reply due to not enough post.
Just to make sure, I just need to go back to download mode and use cf-autoroot-twrp-t800 with odin to root it again. (then it reboots)
After it reboot, turn off and go back to download mode again and install the tar you provided with odin similar to rooting it? Is there any specific options I need to tick or untick in odin?
Thanks again!!
Just reroot that's all you need do.
The same way you did it the first time.
For permissive mode. You need a kernel that allows it.
I have built a stock kernel that will allow you to set permissive mode:
https://www.androidfilehost.com/?fid=24052804347765648
Install with odin.
I'm brand new to this website, and have only signed up because I cannot find a solution for this problem. I have always used the forum to get answers, but never though to join! My Galaxy Tab S 8.4 4G T705Y was put through the CF-Auto-Root method, and no a glitch at all. Very smooth. By the way I checked the ChainFire website to make sure I was using the latest. When my device started up I noticed, as I have done before with my Nexus phones, that SuperSU has been added. Good Sign!
But when I open SuperSU I was prompted to update the Binary. Then I pressed 'continue', used the 'normal' method, and waited. It then asked me if I would like to Disable Knox. Yes I would! FAILED TO DISABLE KNOX. Shut down SuperSU. Unhappy Face. As you can see at this point, I am not very up to speed with my rooting knowledge.
So then I decided to select the 'never' option to updating SuperSU, and still it failed to update the binary, I'd say due to Knox stopping it from gaining access.
So my pickle is this: I can't update SuperSU because Knox will not allow me to use SuperSU. I cannot simply hit yes to disabling Knox in SuperSU, as that didn't work for me. I also tried finding something called Knox on my tablet and it seems to be very elusive. I tried updating SuperSU on Play Store also, but to no avail!
I am also unable to use any third party app to do so as I need to grant them access in SuperSU before they can begin! And around I go...
There is a guide here http://forum.xda-developers.com/showthread.php?t=2540761 but it's not for my device so I'm a bit hesitant to start trying random things, as my device is working great atm!
Any info or help would be greatly appreciated!
Look in the android development section for my updated builds of cf_autoroot and flash that.
If you still get issues flash supersu v2.49 with twrp.
ashyx said:
Look in the android development section for my updated builds of cf_autoroot and flash that.
If you still get issues flash supersu v2.49 with twrp.
Click to expand...
Click to collapse
That seemed to at least do something, now it's saying there is no SU Binary installed. So I googled how to do that, then saw you needed TWRP to do so. And in order to get that, I needed the SDK and JDK, so I got them, but then in then couldn't find any of the right files in the SDK folder when trying to install through command prompt. There is a cool program called TWRP Manager that claims to do it, but you need root access. Lets not go there. So method 2: you needed to use a program like GooManager. But even then root access seems to be the order of the day. Ive tried Terminal Emulator and Package disabler also.
clint.fish said:
That seemed to at least do something, now it's saying there is no SU Binary installed. So I googled how to do that, then saw you needed TWRP to do so. And in order to get that, I needed the SDK and JDK, so I got them, but then in then couldn't find any of the right files in the SDK folder when trying to install through command prompt. There is a cool program called TWRP Manager that claims to do it, but you need root access. Lets not go there. So method 2: you needed to use a program like GooManager. But even then root access seems to be the order of the day. Ive tried Terminal Emulator and Package disabler also.
Click to expand...
Click to collapse
UPDATE: So now I have managed to try and install the version of superSU that you have released in the dev thread, using TWRP. seemed to work fine, but i still got the same binary missing error.
clint.fish said:
That seemed to at least do something, now it's saying there is no SU Binary installed. So I googled how to do that, then saw you needed TWRP to do so. And in order to get that, I needed the SDK and JDK, so I got them, but then in then couldn't find any of the right files in the SDK folder when trying to install through command prompt. There is a cool program called TWRP Manager that claims to do it, but you need root access. Lets not go there. So method 2: you needed to use a program like GooManager. But even then root access seems to be the order of the day. Ive tried Terminal Emulator and Package disabler also.
Click to expand...
Click to collapse
Whoah way way way over complicating things. You just install twrp with odin and that's it.
Then you flash this with twrp http://download.chainfire.eu/743/SuperSU/BETA-SuperSU-v2.52.zip
ashyx said:
Whoah way way way over complicating things. You just install twrp with odin and that's it.
Then you flash this with twrp
Click to expand...
Click to collapse
So this is what I do.
Power off device.
Restart in Download Mode.
Use Odin to install the cf-autoroot-twrp-t705.tar from the development section.
When device restarts I put supersu version 2.52 (beta) on the devices memory, then turn off device.
Restart in TWRP Recovery mode, hit install, choose the zip file, install, reboot device.
When device reboots, open superuser and get this message: "There is no SU binary installed, and SuperSU cannot install it. This is a problem! If you just upgraded to Android 4.3, you need to manually re-root - consult the relevant forums for your device".
I swear i'm not blonde. :good:
Something is blocking supersu from installing. Which firmware build is this device running and is reactivation lock disabled?
ashyx said:
Something is blocking supersu from installing. Which firmware build is this device running and is reactivation lock disabled?
Click to expand...
Click to collapse
**Googles how to check firmware version** Build Number KOT49H.T705YDOU1ANG1
**Googles how to bypass reactivation lock...** hmm seems hard. And I cant see it as an option in my security menu.
clint.fish said:
**Googles how to check firmware version** Build Number KOT49H.T705YDOU1ANG1
**Googles how to bypass reactivation lock...** hmm seems hard. And I cant see it as an option in my security menu.
Click to expand...
Click to collapse
UPDATE: So I went into my Samsung account and Performed a factory reset. Only had the device a few days so no biggy. Then as it reset i chose not to put in and Samsung details and skip all the options i could, assuming this would help. Flashed cf autoroot with odin, then updated supersu through twrp... still nothing
clint.fish said:
**Googles how to check firmware version** Build Number KOT49H.T705YDOU1ANG1
**Googles how to bypass reactivation lock...** hmm seems hard. And I cant see it as an option in my security menu.
Click to expand...
Click to collapse
UPDATE: SUCCESS! I used the latest version of Kingroot available on this forum. From looking around, you are a very patient person ashyx. Thanks for all your help!
clint.fish said:
UPDATE: SUCCESS! I used the latest version of Kingroot available on this forum. From looking around, you are a very patient person ashyx. Thanks for all your help!
Click to expand...
Click to collapse
This doesn't make sense. Something is amiss if you can't root with cf_autoroot or twrp. You are the only one as far as I'm aware that has experienced this.
Reactivation lock is under 'Find my phone' in security settings.
clint.fish said:
I'm brand new to this website, and have only signed up because I cannot find a solution for this problem. I have always used the forum to get answers, but never though to join! My Galaxy Tab S 8.4 4G T705Y was put through the CF-Auto-Root method, and no a glitch at all. Very smooth. By the way I checked the ChainFire website to make sure I was using the latest. When my device started up I noticed, as I have done before with my Nexus phones, that SuperSU has been added. Good Sign!
But when I open SuperSU I was prompted to update the Binary. Then I pressed 'continue', used the 'normal' method, and waited. It then asked me if I would like to Disable Knox. Yes I would! FAILED TO DISABLE KNOX. Shut down SuperSU. Unhappy Face. As you can see at this point, I am not very up to speed with my rooting knowledge.
So then I decided to select the 'never' option to updating SuperSU, and still it failed to update the binary, I'd say due to Knox stopping it from gaining access.
So my pickle is this: I can't update SuperSU because Knox will not allow me to use SuperSU. I cannot simply hit yes to disabling Knox in SuperSU, as that didn't work for me. I also tried finding something called Knox on my tablet and it seems to be very elusive. I tried updating SuperSU on Play Store also, but to no avail!
I am also unable to use any third party app to do so as I need to grant them access in SuperSU before they can begin! And around I go...
There is a guide here http://forum.xda-developers.com/showthread.php?t=2540761 but it's not for my device so I'm a bit hesitant to start trying random things, as my device is working great atm!
Any info or help would be greatly appreciated!
Click to expand...
Click to collapse
Chimed in with some feedback but noticed your problem solved after I replied. Unable to delete. Glad to see you're good to go though.
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]
Suddenly I get a warning telling me to uninstall king root 4.9.6. I've been running same fulmics 6 for months and I just discovered the warning sign today.
What is this? Is there any potential danger to keeping king root? If I uninstall king root I will loose root privileges, yes?
joppy said:
Suddenly I get a warning telling me to uninstall king root 4.9.6. I've been running same fulmics 6 for months and I just discovered the warning sign today.
What is this? Is there any potential danger to keeping king root? If I uninstall king root I will loose root privileges, yes?
Click to expand...
Click to collapse
Fulmics has SuperSu installed as System application,there was no need to install KingRoot..
Also if you have two Root apps (same like SuperSu),then your phone isn't going to have a good time..
So delete KingRoot and stay with SuperSu.
Greetings.
Thx. I used king root to first get root access so I could install fulmics. Iirc I found the king root from a post here on the forum, so I assumed it was safe.
I disabled king root.btw it is fulmics 6.1 I got. It seems all things good now. I feel a little paranoid, as I discovered king root is from China ?
I wonder if I should do complete install from scratch or am I safe as long as king root is not longer active?
joppy said:
Thx. I used king root to first get root access so I could install fulmics. Iirc I found the king root from a post here on the forum, so I assumed it was safe.
I disabled king root.btw it is fulmics 6.1 I got. It seems all things good now. I feel a little paranoid, as I discovered king root is from China ?
I wonder if I should do complete install from scratch or am I safe as long as king root is not longer active?
Click to expand...
Click to collapse
The best choice is to uninstall it.Because it has setted it's self as a system application.
But also i think it has an option (in-app) "Uninstall".
In addition if Kingroot is unable to uninstall by using the inapp option then try installing an app from Play store called " System app remover" and delete it from there.
If nothing works then doing a clean re-installation of the ROM would be a great option.
A Tip:Never install an other Root application while you have SuperSU.
Let's take Kingroot for an example, when you have SuperSU and install Kingroot then automatically Kingroot detects that you have an other root application and it set's it's self as system app.
System app remover did the trick. Removed the King Root app. Result is o/c that adaway is no longer working. So I get to play around with SuperSU now. As I am new to SuperSU I am not sure how to get the correct settings. Should I make SuperSU a system app? Or set permanent full root?
Btw, I never had any problems running King Root. It was even a very nice way to charge the phone because King Root made charging go faster.
I've been thinking about the warning sign I got, and could it possible be a generic warning because King Root had root access? Meaning I would get the same warning with other apps with root access?
It seems strange that King Root that is mentioned som many times here on XDA should be crapware. Surely some smart people would have noticed and made posts about it? I am thinking maybe I panic'd and removed King Root prematurely?
Darn it. SuperSU won't run or allow me to set root access to apps. So no TWRP does not work, adaway does not work, root checker confirms I don't have root anymore and to make things worse, SuperSU says I need to upgrade, so I downloaded the latest version as a zip file to install from TWRP but guess what, no more root access. I will try to boot manually into TWRP and install SuperSU. Hopefully that will work.
And reading SuperSU thread it clearly says I must have ROOT prioer to install SuperSU.
Is there are fulmics setting somewhere I have overlooked? Can I set root from within fulmics tweaks?
Well I didn't get the SuperSU working, then I discovered that there was a newer version of KingRoot, v5.0. So for the ease of it I just installed KingRoot v5.0. As of right now, I don't have any warning signs saying Kingroot is bad news.
So unless it is a known fact that kingroot is infected by crap/malware/spyware/whatever I think I just stick to that one for now. I am used to it, I know how to work it and google didn't find any indications kingroot has been compromised . I saw a few posts about earlier version sending IMEI to china, but it seems that was v3xx. v4x and5x seems to be ok.
If this is stupid behavior and I should remove king root let me know and pls add some links or something to back it. I would hate to give a compromised app gateway into my phone but at the same time I think I was in panic mode earlier today and that my reaction was uncalled for.
joppy said:
Well I didn't get the SuperSU working, then I discovered that there was a newer version of KingRoot, v5.0. So for the ease of it I just installed KingRoot v5.0. As of right now, I don't have any warning signs saying Kingroot is bad news.
So unless it is a known fact that kingroot is infected by crap/malware/spyware/whatever I think I just stick to that one for now. I am used to it, I know how to work it and google didn't find any indications kingroot has been compromised . I saw a few posts about earlier version sending IMEI to china, but it seems that was v3xx. v4x and5x seems to be ok.
If this is stupid behavior and I should remove king root let me know and pls add some links or something to back it. I would hate to give a compromised app gateway into my phone but at the same time I think I was in panic mode earlier today and that my reaction was uncalled for.
Click to expand...
Click to collapse
Then if you are used to Kingroot just uninstall SuperSu(Install the system app remover from Play store ((the first app that appears)).
Because as i mentioned before if you have two Root applications your phone isn't going to have a good time.
(That may be the problem your phone went to Panic Mode)
If you have Kernel Panic mode problems (after unstalling SuperSU) a clean reinstall of the latest version of Fulmics ROM would be great..
PS:I don't know if Kingroot has any type of virus but I'll check if it has anything malicious.
As i checked you said that you lost root access and you took it back with Kingroot right?
Sotiris02 said:
Then if you are used to Kingroot just uninstall SuperSu(Install the system app remover from Play store ((the first app that appears)).
Because as i mentioned before if you have two Root applications your phone isn't going to have a good time.
(That may be the problem your phone went to Panic Mode)
If you have Kernel Panic mode problems (after unstalling SuperSU) a clean reinstall of the latest version of Fulmics ROM would be great..
PS:I don't know if Kingroot has any type of virus but I'll check if it has anything malicious.
As i checked you said that you lost root access and you took it back with Kingroot right?
Click to expand...
Click to collapse
Seems I am good after all. Turned out I messed up the fulmics 6.1 badly when trying to get adaway for youtube to work. So now I got fulmics 6.5. Yeah I know it is not the latest but I had slow internet connection and 6.5 was already downloaded but not yet installed so I just picked that and did a swipe, and twrp install of fulmics 6.5.
I did however install king root 5.01 again to get an easy way of getting everything else important installed that requires root.
If I don't see more warnings I think I will be fine. If I do I will take the plunge for superSU and read up on that before making the switch.
If I see those warning signs again I will try not to panic and try to keep calm