I possess a Huawei Y6 SCL-L01C55B130, and I encountered a lot of problems in rooting it.
First, I unlocked the bootloader, then flashed TWRP 2.8.7.0 with Minimal ADB and Fastboot. Result: the recovery is messily responsive with touch! Is there any NORMALLY FUNCTIONING recovery for this device (as in, not requiring me to use a hammer and nail to get the touch to work)?
Then, I tried to flash SU: another disaster. It asked apps for "superuser permissions", but rootchecker told me the phone WASN'T rooted. I had to uninstall SuperSU, because I couldn't ask it to unroot nor use the flashable "UnSu" package (I had flashed SU multiple times trying to make it work). Is there any way to remove any and all traces of its passage?
Then, again, I tried King Root: after some attempts, it worked, but then I discovered how much of a nuisance that tool is, because of all the "spyware" stuff it brings with it. I eventually decided to unroot and uninstall the tool, but, again, can I remove the traces it left in my system (if there are any)?
Eventually, I used magisk 12.0, and it works like a charm for rooting.
Other issues emerged though: I had finally rooted and debloated my phone, but I can't apparently play "nintendo games" because of Safetynet. Is there a way to circumvent it (as in, hiding the open bootloader and root)? Are the SU and KingRoot traces going to be an issue?
If I need to flash a new custom rom (the stock and/or nobrand apparently DON'T EXIST on the internet)to obtain the safetynet workaround and have a clean system, so be it, but which bugs do they have with my specific device? The situation is very confusing because of the existence of SO MANY variations of Huawei Y6.
Thanks for reading all this mess, and for the help!
Related
I have tried to UNROOT my Verizon Note 3 (SM-N900V) 4.3/MJE using Kingo, but Kingo shows that I am NOT rooted and doesn’t provide the “Unroot” option as it should. I used Kingo to root my phone, and I haven’t installed any custom ROMs or recoveries other than upgrading to SuperSU Pro and installing Xposed Installer.
I’ve watched dozens of videos on unrooting, but little without Kingo. Unfortunately at the end of these videos, they all show that the Knox warranty being voided (0 x 1) and some can’t remove the Custom Padlock screen. Just wondering if anyone has successfully unrooted and not having the Custom Padlock screen or Knox tripped.
Any help would be greatly appreciated!
Also, sorry if I didn’t post this right as this is my very first post or thread.
Easy Solution to Kingo Unrooting Found
I contacted Kingo about a week ago and gave them a decent donation along with my question. Unfortunately I never got any response back whatsoever. I’m thinking that they are really busy. So, I went ahead and took the leap and did the work successfully myself.
1. I uninstalled Xposed Installer through its own uninstaller. Then I removed it along with Titanium Backup, and the Pro version through CleanMaster with no problems.
2. I was able to uninstall SuperSU through it’s own “Uninstall” feature, then rebooted.
3. The first thing I noticed was the “Custom” and Padlock logo still on my screen at bootup, but the great thing was that I booted up without any problems.
4. I had discovered that the SuperSu Pro apk was still present through the phone’s Application Manager and was able to uninstall it from there.
5. Finally and fearfully, I rebooted one more time.
Everything booted normally again, and this time, the “Custom” logo and padlock were finally gone! I checked the Knox counter and both flags showed 0 x 0. Kingo had a problem with their servers in early February and I tried to root about 15 times over a period of about ten days or so. Suddenly one evening, I was able to successfully root within 3 or 4 minutes, and it really was a one click ordeal. Just be aware that you may not be able to unroot with their program. Don’t fear. Unrooting manually the way I did reveals absolutely no traces of a previous root or that the phone had been tampered with. I’m not sure that anyone who has flashed a custom ROM or recovery would have the same results though, so proceed with caution.
Hi all. I'm into my umpteenth reinstall through Odin. As I'm trying to troubleshoot why my tablet independently reboots. This is my thread in the specific forum.
http://http://forum.xda-developers.com/galaxy-note-pro-12/help/sm-p905v-root-issue-t2842651
Right now I have a bare stock reinstall. I upgraded the Verizon OTA package and I have installed towelroot v.3. My system is stable.
As soon as I install Supersu my system will begin into the slide of reboots. This is confirmed by me because I have gotten to this point before.
My question is if there is something I can run or should run, to log what process is causing my instability?
I have gone past this point recently where I installed all non root requiring programs. The tablet will be perfectly stable. Then install tr v.3. and I will still be fine. Once I install Supersu the problem starts. I have repeated this process and tried different Supersu programs and still the same problem.
Again, when I install Supersu "first thing" after a (reinstall and tr v.3) the problem starts. That pretty much tells me the problem is with either Supersu or towelroots handling of supersu.
Any ideas or suggestions? Any help would be greatly appreciated. Support for this device is limited and I'm thinking I may need to take things out onto my own.
Solution is not to abide by the Knox warning when installing Supersu and allow Supersu to "fix it". I haven't had a hot boot since.
Sent from my SM-P905V using Tapatalk
I was trying to root my OPO by flashing SuperSU Beta_V2.52 but after each flash my OPO goes into a boot loop, flashed several builds of SuperSU (inc; beta's) and all of them result in a bootloop. To be on the safe side i did fresh installs of CM13 via bootloader, no result.
Pulling my hair what the solution will be. Dev's from "Cyanogenmod-team" are aware of this problem but find its not there problem to solve...:
It needs to be said that this issue with SU is something that is outside the scope of official support. We neither recommend or support SuperSU installs, as it opens the device up security wise in ways that most users (not all, some do the homework to understand what's going on) either ignore or are ignorant of. So if there's a bootloop happening, you are going to need to diagnose it on your own, or with others help here. You can also check XDA as well.
sandeman11 said:
I was trying to root my OPO by flashing SuperSU Beta_V2.52 but after each flash my OPO goes into a boot loop, flashed several builds of SuperSU (inc; beta's) and all of them result in a bootloop. To be on the safe side i did fresh installs of CM13 via bootloader, no result.
Pulling my hair what the solution will be. Dev's from "Cyanogenmod-team" are aware of this problem but find its not there problem to solve...:
It needs to be said that this issue with SU is something that is outside the scope of official support. We neither recommend or support SuperSU installs, as it opens the device up security wise in ways that most users (not all, some do the homework to understand what's going on) either ignore or are ignorant of. So if there's a bootloop happening, you are going to need to diagnose it on your own, or with others help here. You can also check XDA as well.
Click to expand...
Click to collapse
Did you try SuperSU V2.76?
[CENTER[/CENTER]
sandeman11 said:
I was trying to root my OPO by flashing SuperSU Beta_V2.52 but after each flash my OPO goes into a boot loop, flashed several builds of SuperSU (inc; beta's) and all of them result in a bootloop. To be on the safe side i did fresh installs of CM13 via bootloader, no result.
Pulling my hair what the solution will be. Dev's from "Cyanogenmod-team" are aware of this problem but find its not there problem to solve...:
It needs to be said that this issue with SU is something that is outside the scope of official support. We neither recommend or support SuperSU installs, as it opens the device up security wise in ways that most users (not all, some do the homework to understand what's going on) either ignore or are ignorant of. So if there's a bootloop happening, you are going to need to diagnose it on your own, or with others help here. You can also check XDA as well.
Click to expand...
Click to collapse
Happened to me couple of times while switching from cm12.1 to cm13. Turns out marshmallow doesn't really support superSU v2.52. Try v2.76 instead. Worked like a charm for me
P.S.:update your TWRP to version 3.0.
I've basically been trying to root this phone for over a week now - first of all I had problems with the ADB drivers and such, but now I can actually flash stuff onto the phone.
I then also managed to flash SuperSU and XPosed and now herein lies the problem. I want to play PokémonGO.
Now, after doing a lot of reading up on the subject, it seems P-GO now uses Google's SafetyNet API in order to block Root, Xposed, etc users from playing the game.
So, I did a complete reset and tried flashing a different rom. I used the ''Stock Android 6.0 ROM'' from this thread: https://forum.xda-developers.com/android/general/leagoo-shark-1-development-support-t3415599
HOWEVER, flashing that ROM seems to wipe the recovery partition (even if you untick recovery in sp flash tool) and you end up with some chinese 4G logo banner, before it boots into the OS.
So, back to square 1. I found and re-flashed the stock Leagoo OS ROM and then tried using Magisk (because supposedly Magisk can hide itself and allow me to play P-GO).
No digs...
So, after many hours of flashing many different ROMs, performing countless resets and wipes on my phone, I think I may have found the issue.
After reading through the support forum of Magisk, it was recommended trying to go back to 0 (un-rooting, re-wiping partitions, re-flashing stock rom, etc) and seeing if my phone would then pass SafetyNet Check - It doesn't.
Purely stock ROM, does not pass SafetyNET, which I reckon is because the phone's bootloader is unlocked from the get-go.
Now, weirdly, the stock rom CAN play PokémonGo without a hitch, but installing root then mucks it up.
Seeing as Leagoo isn't exactly a common brand, I cannot install LineageOS with it's custom kernel which hides the bootloader settings....
what can I do if I want to have a rooted phone, but also want to play PokemonGo?
I’ve recently been trying to root my Samsung SM-J710FN. I managed to find a sequence of actions that consistently produces a rooted phone. I found TWRP 3.0.2 (I know that later versions exist, but this is the latest I could find for this model) and flashed it using Odin. I then use it to wipe the data partition (because, apparently, TWRP doesn’t work well with encryption). I use adb push to copy SuperSU 2.79 (downloaded from here) and no-verity-opt-encrypt-6.0 (in accordance with instructions in this thread, downloaded from here) to /data, then I install both of them using TWRP and reboot.
While the phone does appear rooted, it does end up having some serious problems. Here are some that I managed to find:
The camera doesn’t work. When I try to start the Camera app, it just crashes after a few moments.
The flashlight doesn’t work. When I try to turn it on using the button in the quick settings panel at the top, I get a message saying that the Camera app is using the flashlight (and the flashlight doesn’t turn on, obviously).
The phone does not automatically change orientation as I rotate it (in apps that are supposed to support it, such as Google Chrome), even though the appropriate settings are enabled.
The brightness controls do not affect the screen’s brightness in any way.
(I also can’t manage to re-encrypt the phone after rooting it, but that’s probably better left for a different thread.)
Has anyone else encountered similar problems? What can I do to solve them?
Have you tried to reflash stock ROM again?
I have. In fact, I did so many times before I figured out the exact steps to successfully root the phone (and then a number of times more while troubleshooting these issues). Everything works fine after restoring (unrooted) stock firmware, but stops working again after rooting.
I finally figured it out. Looks like I should have used a different SuperSU version. I repeated the process using SuperSU v2.82 SR5 and the problems stopped.
(I’m still trying to get the phone to be both rooted and encrypted, but that’s a separate story…)
EDIT: I gave up on SuperSU and used Magisk instead. It’s much easier and seems to work perfectly even with encryption!
Can you give me link to download a Android system and Magisk. Which one you used. I have the same problem :c
Here’s Magisk: https://forum.xda-developers.com/apps/magisk
As for “Android system”, do you mean stock firmware? In that case, I’m really sorry but I haven’t really kept a link to the place I downloaded it from Besides, you need stock firmware that matches your specific phone (based on the part of the world where you bought the phone, I think? I’m not quite sure), which may not be the same as mine.
I've already done it, I downloaded all the necessary files from sammobile.com
But thank you for your willingness to help
voidphantom said:
I have. In fact, I did so many times before I figured out the exact steps to successfully root the phone (and then a number of times more while troubleshooting these issues). Everything works fine after restoring (unrooted) stock firmware, but stops working again after rooting.
Click to expand...
Click to collapse
Can you give me the link of the Stock ROM?
When twrp install j7 max then phone go to bootloop problem please tell me how I fix this problem
dealiyo said:
Can you give me the link of the Stock ROM?
Click to expand...
Click to collapse
As I said before, unfortunately, I have not kept a link to the stock firmware. Further, judging by your other posts, you don’t seem to have a device of the same model as mine (I have SM-J710FN, you said you have SM-J710GN), which means my stock firmware isn’t going to be useful to you anyway.