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?
Related
tl;dr - TWRP touch screen won't work after installing custom ROM, much hassle to unbrick, looking for a "bumped" (still not actually sure what that term means) or otherwise modified version of TWRP that won't go haywire when installing a custom ROM.
tl;dr 2 - Also interested in the LATEST "stock-based" ROM recommendations anyone may have... G3 backports or whatever. She needs her Camera to work well but older 4.4.x and 5.0.x OS is missing a lot of new functionality and compatibility with new apps.
I'll just start out by saying that I've figured out just about every way to brick and subsequently un-brick this device that is feasibly possible, and am considering starting a thread specific to those various methods... but that's not what this is for.
This is an issue I've encountered a few times now, definitely on my girlfriend's T-Mobile LG G2 D801 with Lollipop (30B and now again on D801 30C), and iirc, also on KitKat.
I'll explain what I can remember, most of this has been done in the middle of the night after many frustrating hours of attempting various methods... I have to say, this phone has been much more difficult to mod compared to my previous experiences with Samsung and Nexus devices.
I had gotten this device all the way through to CM12 or 13 a year or so ago but recent issues made us decide to attempt to revert back to a Stock-based ROM.
Steps:
1. Root (ioroot / Autorec, can't remember which or for what reason, I have multiple versions of each)
2. Install TWRP Custom Recovery (most recently and successfully using a modified version of the "30B Freedom Tool", although I haven't tried that on 30C - yet.
3. Transfer custom ROM & Kernel to SDCard.
4. Boot into TWRP and install custom ROM & Kernel - most recently GoogleEdition 1.5 and then DorimanX 12.0 Kernel
5. Clear Cache / DALVIK Cache.
6. Reboot device. This is where the trouble begins...
Results: Won't boot into OS at all, instead I end up at the text-based "fastboot" screen, which after multiple tries I can eventually get back into TWRP or into Download Mode.
Once in TWRP after installing custom ROM, the bottom ~1" of the screen won't respond and all other touches aren't accurate... playing with it, I can usually eventually get into some of the TWRP screens, but for most purposes it's about useless.
I managed to restore a backup of the original 30B system image via command line over MTP using ADP TWRP commands, but that bricked the phone in an entirely separate manner where I couldn't access Recovery anymore and the system wouldn't boot at all... I ended up using the LG Update tool to get it up to 30C, and was surprised to find that it still had the restored backup data (apps, pictures, settings, etc), and the phone is now working again, albeit back to stock recovery.
Now, as I mentioned, this isn't the first time I've run into this "phantom touch" issue in TWRP on this device, although the circumstances seem to be a little backwards this time vs when I was taking the device over to CM12/13. I think I remember something about a "bumped" or otherwise modified version of TWRP being out there, but I can't find it now or put my finger on what the changes were.
Has anyone else run into this? I am hoping I've just overlooked something, but days of digging through threads hasn't turned up much.
/edit/ To give you an idea, attached is the folder I've got files stored in... with tons more in Archive and Stock-Based... I've used them ALL at some point. I'd like to get enough info in here to write a Step by Step guide for new owners who are picking these devices up on the cheap, and would appreciate if anyone wants to help out with this!
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!
Hi Everyone,
Honor View 10 is going to be launched soon in my country (this end of month). I have considered it as my next phone upgrade. Before, I have looked upon N*k** 8, but that subforum is dead already (no UBL, no root, nothing to see). I am currently waiting for X***mi RN5P which still have no news about the official launch here (probably another 3 months). But they decided to do some twist, by disabling the UBL ability for the phones they launched officially here. Kinda ironic.
To make sure I can live with the phone as it, I have to confirm several things first :
1. Does the phone has native VoLTE that works out of box without installing any additional app? I read from several thread here, it has support Dual VoLTE, but still doubt. I have checked some other phone who said they support VoLTE but in reality doesn't work. My main carrier used to be CDMA carrier, which has completely moved to 4G (only). So we can only call/sms thru VoLTE. If someone can post the screenshot of the VoLTE call setting, or "Enhanced HD" setting or similar, it will be a great confirmation. (I don't need the video call, only voice call/sms).
2. I am using Automagic (tasker alternative). I am quite active in that forum for several months. From there, I read a lot of incompatibility or something won't work, mostly from Huawei Devices. It seem the aggressive battery saving from the ROM has been disrupting Automagic from running properly. Is there anyone here who use Automagic/Tasker or similar automation app and found problem specific for Huawei devices, specificly for this View 10? (using stock ROM). I mean something like wifi scanning or location which work in Phone A or Phone B using the same android oreo 8.0; but doesn't work in View 10. If only minor problem, I can accept it.
3. Is there anyone having problem with the UBL process? X***mi just pull it tricks by kinda banning all user from my country to unlock the Bootloader. (error 86023:hardwareID) I am afraid of the same, as I need root. But I don't need to change the ROM.
Best case
If all the problems are solved and I have bought the device; I am going to root and install TWRP as usual. But I will stay on Stock ROM, most custom ROM still have problem with VoLTE. I might use LineAge or AOSP-ish ROM if there is any and has solved most bug. This is the step that I am going to do after I bought the phone.
1. Unlock the bootloader. https://forum.xda-developers.com/honor-view-10/how-to/honor-view-10-bootloader-unlock-t3749426 Result : Bootloader Unlocked
2. Install Magisk (latest is 16.2) via fastboot https://forum.xda-developers.com/ho...agisk-root-honor-view-10-mate-10-pro-t3749280 Result : Root achieved, Magisk Installed
3. Then proceed on to backup the original recovery https://forum.xda-developers.com/showpost.php?p=75630973&postcount=3 Result : Original recovery backed up. I am thinking to do additional backup by using partition backups, but don't know if it works.
4. Flash Official TWRP https://forum.xda-developers.com/ho...recovery-twrp-3-2-1-0-touch-recovery-t3752397 Result : recovery changed to TWRP.
5. Backup all available partition. Result : all partition backed up, except /data. Since FBE still won't work
After the ritual, the phone will be rooted, Magisk installed, TWRP, and have full backup of all backup-able partition from TWRP and the original recovery. Xposed still won't work, so need to find alternative in Xposed. I mostly use Gravity box and App Settings Modules. Maybe there are alternatives available in Magisk. (haven't research much about it). To backup app's data, the only choice is Titanium Backup then, since /data partition can't be backed up in TWRP. We don't have stock firmware yet available, so need to be careful with the modification.
Do I miss something in my steps above?
Thanks for the answer in advance. And sorry for the long post.
Regards,
Desmanto
Hello there.
I'm using tulip for few months now. One of first things that I've done, have been unlocking device, rooting it and put stock rom with root access on it. So far, so good. I did not encounter any serious glitches etc, but now I would like to finally upgrade miui to 11 (currently having 10.3).
And there's my problem. I would love to dodge making clean installation (wipe data etc) and I do not wish to risk to bootlooping my phone. I've read on some threads (older ones, but still) that you cannot simply install ota update in system, because due to changed recovery (I do have TWRP instead of fabric one) you will cause bootloop. I've tried alternative method of installing zip BY twrp, but program says, that it encounter a problem called "package expects build fingerprint (...) of tulip 0/PKQ1.180904.001/V10.3.2.0.PEKMIXM or PKQ1.180804.001/V11.0.2.0; this device has omni_tulip/tulip:8.1.0/OPM8.181105.002/1", and then sait, that in had error 7.
Is it simply wrong rom being installed and I have to choose something that is being named the same way and supports ota, or is there a way to go more swiftly through this process? If so and I should pick rom with ota - what to choose? I like deep level customisation, but compatibility with google store, being able to use store, payments and paid apps, instead of "opening them" by some lucky patchers kind of apps.
OR MAYBE I just need to change recovery from TWRP to something different - like PBRP f.e.? Just like this thread says - https://forum.xda-developers.com/re...how-to-setup-official-miui-breeaking-t3893703
Just a quick update - changing twrp to pbrp does not change anything in upgrade process - still get the same error, now just without telling me, which version do I have.
Also, what's interesting, apparently twrp said to me that I do have android 8.1, but "about phone" in system says, that its android 9 (9PKQ1.180904.001 to be exact).
That's werid, because everywhere I check, phone says "android 9" as a version of it.
Have you tried wiping system and installing?
Nitin Rai said:
Have you tried wiping system and installing?
Click to expand...
Click to collapse
Not yet. I've found method of flashing via PBRB with usage of downloaded file and one option check, but I'm not gonna try it, unless I do a backup of my apps. If that won't work, I'll perform a clean instalation and choose rom that supports ota.
well, I've tried to do this with the method, that I've described before, but this did not ended successfully. I'll look for rom with ota update possibility and then install it most likely. Apps had backup, so I lost almost nothing.
It worked. I had to download bigger patch (1.7 GB, instead of circa 700 MB, that I've tried before), I also had to use method described here -> https://c.mi.com/thread-1782169-1-1.html (pitch black recovery, instead of twrp + one tweak in options). Start after flash was very long (it took like 10 minutes or so), but it booted successfully in the end. Not sure which rom I do have after all, but as far as I remember it was so close to stock, as possible (with only few extra options and tweaks). So yea, it just works.
I have a regular OnePlus 7 PRO (GM1913)
My bootloader is unlocked and I am rooted with Magisk on Android 10, with Oxygen 10.3.4 Stock.
something got funky with switching between apps and keyboard gets stuck sometimes and camera crashes, could be Nova launcher, could be Swiftkey, idk really
but I guess its time for a refresh to see if that fixes the problem (which I believe it will).
My Questions are:
1: How would I go on about flashing a custom ROM / latest Stock (recommendations welcome) without wiping data and keeping everything intact?
2: do I need a PC for that or can I do it "Over the air"? (sorry not fluent in this stuff since a long time)
Thank you!
Well, I'm not an expert but I've done that for the same reason as yours; ended up with the stock OxygenOS. Actually it started with stock OTA updater, ended with a brick(then unbrick)...
I've tried several custom roms, but
stock camera app is irreplaceable (Custom OS got more options, but Android 10+ is difficult to tinker with)
Even the most popular custom OS's may crash with an upgrade (especially if you tinker with your system). So whatever is wrong with it now, may got worse, or better.. Or it may get worse later(or not, who knows).
OTA doesn't do downgrades and check the signature of the package, so if something goes wrong or if you want oos back, you may need to use EDL with MSM Tools(Which, unfortunately requires a PC)
Thats why your safest bet is to:
Backup everything you can't afford to lose, then prepare an unbrick tool image if you can. You can backup without pc, but using edl or fastboot requires PC or other android device as a host device.
By the way, It's not that fun after a hundreds of reboot and flashes, so I use Linux now