Related
https://download.mokeedev.com/?device=zoom
Does someone try this rom? If u ever on this rom, can u give a feedback about the rom..? I would like to know your opinion..
X10MINISTER said:
Does someone try this rom? If u ever on this rom, can u give a feedback about the rom..? I would like to know your opinion..
Click to expand...
Click to collapse
Rom works but it wasn't maintained. No new bug correction from february.
stuccamelo said:
Rom works but it wasn't maintained. No new bug correction from february.
Click to expand...
Click to collapse
Thanks for sharing ur opinion/experiences on this rom.. Im running on latest build of this mokee rom, i think it is suitable for daily driver..but I got some problem with hotspot(maybe it is because of mod that i've installed).. Maybe u got some solution on this
X10MINISTER said:
Thanks for sharing ur opinion/experiences on this rom.. Im running on latest build of this mokee rom, i think it is suitable for daily driver..but I got some problem with hotspot(maybe it is because of mod that i've installed).. Maybe u got some solution on this
Click to expand...
Click to collapse
Sorry no solution I have big problem with gmaps doesn't recalculate path after initial path and play store give "not compatible device" error in some apps.
Good thing battery drain is very very good
stuccamelo said:
Sorry no solution I have big problem with gmaps doesn't recalculate path after initial path and play store give "not compatible device" error in some apps.
Good thing battery drain is very very good
Click to expand...
Click to collapse
So, it mean that u also facing the hotspot problem.?
Can u change/install fonts in mokee roms? Cause I have an issue with changing font style using iFont apps..its say installed but after reboot font style doesnt change. Any solution?
linux shall eternally bloat all search engines with expired ?=
as it is stated in the title: the internet is full of long expired conversations about issues which are gone, along with hardware.
back in the beginning i recall only one distro Dev, SimplyMepis, who always, promptly warned, that most if not all information online about Linux is outdated or incorrect.
now on mokee, has anyone tested mokee naugat on vibe shot as recent as September/October 2017? The reason I ask is because there are no reviews or any useful feedback on mokee download/changelog page. I used it in August and each time the phone disconnect from WiFi it would reboot with an ugly, annoying double beep.
Apart from this issue everything would work pefectly well, including both sim loaded.
Thanks for taking time to respond.
Dr Tungsten said:
as it is stated in the title: the internet is full of long expired conversations about issues which are gone, along with hardware.
back in the beginning i recall only one distro Dev, SimplyMepis, who always, promptly warned, that most if not all information online about Linux is outdated or incorrect.
now on mokee, has anyone tested mokee naugat on vibe shot as recent as September/October 2017? The reason I ask is because there are no reviews or any useful feedback on mokee download/changelog page. I used it in August and each time the phone disconnect from WiFi it would reboot with an ugly, annoying double beep.
Apart from this issue everything would work pefectly well, including both sim loaded.
Thanks for taking time to respond.
Click to expand...
Click to collapse
There are a lot of recent updates for this rom. I flashed the most recent (2017-11-21 date). I didn't make a lot of testing but the problem you refered has been solved and the performance and stability seems good.
The only issue I noticed so far is that the phone does not start automatically from the shutdown state when an alarm is set.
@piccolo2k2 Was your device flagged as certified? When I flushed the rom I wasn't able to pass the SafetyNet test and I would appear as uncertified in play store, meaning I couldn't download most apps like Messenger or Facebook. I installed a third party app store which worked fine, but YouTube wouldn't play any video, because it couldn't load any ads... I even tried Magisk with no luck..
GeorgeTsak said:
@piccolo2k2 Was your device flagged as certified? When I flushed the rom I wasn't able to pass the SafetyNet test and I would appear as uncertified in play store, meaning I couldn't download most apps like Messenger or Facebook. I installed a third party app store which worked fine, but YouTube wouldn't play any video, because it couldn't load any ads... I even tried Magisk with no luck..
Click to expand...
Click to collapse
This is not my main phone right now so I spend very limited time using or testing it but you are right, I have just checked that with this ROM the device is unable to pass the SafeNet test so far. On the other hand I have not problems at all playing videos with youtube app or rooting the device. I'm using supersu v2.82 and TRWP-3.0.2-0 for lenovo 6.0 by wzsx150 (didn't try Magisk)
has anyone managed to install this ROM?
i tried to install it but failed.
I unlocked the bootloader using the method described here, and installed TWRP recovery as described here
when i try to install it - the flashing is stopped by a long vibration and the device went off, i tried to debug the flashing process, it seems that the step of mounting "\system" fails, i tried to replace the mount/unmount calls from updater_script with respective run_program(busybox) commands, but had no success with that. when i'm using the TWRP build in funcitonlity to wipe the system partition, TWRP claims the operation was successful, but checking the system partition details shows that the partition still contains data.
ohh, and also - the device model seems strange, the script checked that the model is zoom_tdd (or something like that) but the device (the bootloader?) return Z90a40... (i also updated the script to check for Z90a40)
the current state is that the device won't boot, but i can get into recovery.
Anyone have an idea how to proceed?
Thanks.
mrtowel said:
i tried to install it but failed.
I unlocked the bootloader using the method described here, and installed TWRP recovery as described here
when i try to install it - the flashing is stopped by a long vibration and the device went off, i tried to debug the flashing process, it seems that the step of mounting "\system" fails, i tried to replace the mount/unmount calls from updater_script with respective run_program(busybox) commands, but had no success with that. when i'm using the TWRP build in funcitonlity to wipe the system partition, TWRP claims the operation was successful, but checking the system partition details shows that the partition still contains data.
ohh, and also - the device model seems strange, the script checked that the model is zoom_tdd (or something like that) but the device (the bootloader?) return Z90a40... (i also updated the script to check for Z90a40)
the current state is that the device won't boot, but i can get into recovery.
Anyone have an idea how to proceed?
Thanks.
Click to expand...
Click to collapse
I think you need a different TWRP version. Try this one:
https://drive.google.com/file/d/0B1Sms71Oe6FIQnl4STlhSk96b0E/view?usp=sharing
Help me!
I'm new to these things. Installing roms and ****s. Can someone help me with the step by step procedure of installing this room on my Lenovo vibe shot. Thanks in advance.
The same probvlem with TWRP
piccolo2k2 said:
I think you need a different TWRP version. Try this one:
Click to expand...
Click to collapse
I have exactly the same problem.
Did you resolved it? Tried also mentioned "Twrp by rahul.rar", but the same problem - unable to mount /system partition.
Thanks for reply,
st
bug fix?
does anybody tested it?
is it still any bug on release version MK71.2-zoom-180914-RELEASE?
hhaekal said:
does anybody tested it?
is it still any bug on release version MK71.2-zoom-180914-RELEASE?
Click to expand...
Click to collapse
Im using it right now.. Im still have the problem with:
-hotspot tethering,bluetooth tethering
-usb mtp
-suddenly shutdown when on wifi
Have someone had the problem with delay in receiving whatsapp messages?
Hello,
has anyone tested the MK71.2-zoom-181107-RELEASE version? Is the bug with the WiFi still there?
Alex_135 said:
Hello,
has anyone tested the MK71.2-zoom-181107-RELEASE version? Is the bug with the WiFi still there?
Click to expand...
Click to collapse
Hi,
I'm using the release and there is no bug with WIFI.
Linaxx said:
Hi,
I'm using the release and there is no bug with WIFI.
Click to expand...
Click to collapse
How about wifi tethering problem? Does it remain error when wifi tethering are enabled?
Fingerprint Scanner Null after Pie ROM Flash - Custom ROM won't fix. Stock Only
Ok, the story.... Moto G5+ retail, running 8.1 Oreo, Bootloader Unlocked, rooted using Magisk 16.7 and was able to backup my Stock Oreo ROM once rooted, or I'd be dead in the water.
So wanting to stay ahead, I tried my hand at RR v7's Pie version, which, after some troubleshooting, was able to install successfully; but I don't much care for the google bar and other hard-coded "pure android" features. Same thing with Pixel Exp. Not to mention that Pie disallows call recording among a few other things Google decided to stifle its customers with. Deal breaker. So - moving on...or back for that matter.
I proceeded to download RRv6, which is btw running nicely on a 2nd G5+, same GApps, installs perfect except - FingerPrint Reader is not acknowledged. Period. No Security settings, No RR Config to access it, Nada. No matter what ROM I flash outside of the StockROM I backed up, it won't recognize the fp reader upon boot up. Whether I clear Dalvik/Cache, All DATA, do a full Wipe, DATA WIPE, REPAIR, FORMAT, nothing allows me to install RR v6.0 or any other flavor, Oreo or Pie, even while trying a dirty flash over Stock Oreo on this Moto G5+. Tried with several SD Cards, downloading fresh zip files from RR. I even went so far as to image the working G5+, then copy into the 2nd G5's SN folder, and do a restore, just loops - even after repairing the partition. I managed to work around that, Restored the image, but still no FP recognized by the initial Google startup/setup. It's almost as if the phone's been "firmwared" or "tagged".
Any ideas what could be lingering from Android Pie that would survive a F2FS/exT Format? Because something updated some kind of firmware on the phone during a Pie ROM flash, that now won't let me go back to anything below Pie, with a working fingerprint reader. The only difference between the G5 that works and this one is the working one has never seen Android 9. And it's staying that way til we come up with a way to hack the google crap.
Any help would be - awesome to say the least.
Thanks for looking.
Hello,
The issue with fingerprint is that after flashing stock Oreo ROM it replaces some files related to fingerprint sensor.
Hence all the newer custom ROM builds use the Oreo firmware related files. Hence it worked on the Pie ROM.
RR v6 would be still using the old nougat firmware hence you need to flash a file for it work. Which will replace the fingerprint related files for Nougat Stock firmware:
https://androidfilehost.com/?fid=1322778262904029634
In case you want to revert the changes and use Pie ROMs:
https://androidfilehost.com/?fid=1322778262904029635
sharan.nyn said:
Hello,
The issue with fingerprint is that after flashing stock Oreo ROM it replaces some files related to fingerprint sensor.
Hence all the newer custom ROM builds use the Oreo firmware related files. Hence it worked on the Pie ROM.
RR v6 would be still using the old nougat firmware hence you need to flash a file for it work. Which will replace the fingerprint related files for Nougat Stock firmware:
https://androidfilehost.com/?fid=1322778262904029634
In case you want to revert the changes and use Pie ROMs:
https://androidfilehost.com/?fid=1322778262904029635
Click to expand...
Click to collapse
That would make sense if PHONE1 manifested the same thing. But I went from StockOreo to RRv6-Oreo w/out losing anything and having to flash any FP Firmware. I used the RRv6 Official from 18-0911. Which is what's been leading me to believe there's something awry with this 2nd G5. I wonder is it possible PHONE2 has some slight firmware variance that is simply ignoring during the RR flash? Anyway, I'll give this a shot. this is TWRP flash, not fastboot, yes? Just being clear as I'm not proficient at this just yet.
Thanks Sharan!
DJScribe said:
That would make sense if PHONE1 manifested the same thing. But I went from StockOreo to RRv6-Oreo w/out losing anything and having to flash any FP Firmware. I used the RRv6 Official from 18-0911. Which is what's been leading me to believe there's something awry with this 2nd G5. I wonder is it possible PHONE2 has some slight firmware variance that is simply ignoring during the RR flash? Anyway, I'll give this a shot. this is TWRP flash, not fastboot, yes? Just being clear as I'm not proficient at this just yet.
Thanks Sharan!
Click to expand...
Click to collapse
Yeah, give it a try. And yes it's to be flashed via TWRP.
[SOLVED]
sharan.nyn said:
Yeah, give it a try. And yes it's to be flashed via TWRP.
Click to expand...
Click to collapse
Sweet! I had to reflash from scratch as for some reason it wouldn't let me update the ROM already running. But once I re-flashed RRv6-8.1, then flashed FP, it's now back. You rock Sharyn - nice work!
Now if only we found a way to cleanup that Pie - hate the perpetual time stamp, search bar and inability to record voice. Which is why I'm staying on Oreo til further notice. I know it was Google who took it away on v9.
Thanks again Shar!
:good::victory:
DJScribe said:
Sweet! I had to reflash from scratch as for some reason it wouldn't let me update the ROM already running. But once I re-flashed RRv6-8.1, then flashed FP, it's now back. You rock Sharyn - nice work!
Now if only we found a way to cleanup that Pie - hate the perpetual time stamp, search bar and inability to record voice. Which is why I'm staying on Oreo til further notice. I know it was Google who took it away on v9.
Thanks again Shar!
:good::victory:
Click to expand...
Click to collapse
Crap - so turns out this solution was short-lived. FingerPrint Scanner is back to inactive and FPzip isn't fixing it. Only StockOreo brings it back. Tried a plethora of ROMs from Nougat to Oreo, nothing but Pie and stock Oreo. Symptoms say it's the ROM, but a ROM that is currently working on the 1st G5 won't work either. Still looking for solutions, anyone...
Note: Make sure your phone is decrypted and do not turn on the secure boot feature where you need to put in your pattern to boot system!
So as I'm currently without a PC and can't restore the stock images I wanted to share the best method for using Android 10 I've found.
Get the latest phh gsi image v210 is what I used.
Get the latest Lineage OS GSI 17.1 image.
Get the Trinity v2 kernel (beta is what I used).
Get the latest Android 10 pico or nano gapps from opengapps. (I used nano)
Boot to recovery and factory reset.
Install phh gsi IMG to system. When finished don't reboot. (I do this to keep security patches as up to date as possible)
Install LineageOS IMG (DIRTY FLASH).
Install Trinity Kernel to Boot
Reboot system
(Optional once you fully boot you can reboot recovery and flash the f2fs zip from Arter Kernel then reboot recovery and wipe data. When you reboot system you may freeze during setup just reboot by holding the power in until the phone restarts. It will finish setup this time.)
Reboot recovery and flash gapps. If you get error 70 resize the system partition. It will work after resizing once or twice.
When it boots you can do your traditional setup.
Reboot recovery and Install Magisk v20.3.zip
Reboot system and Install Magisk Modules Busybox for Android NDK and Magisk Hide Props Config.
Install terminal app of choice following Reboot
Type su in terminal and hit enter
Type props in terminal and hit enter
Change the fingerprint to Razer Android v9 and Reboot following the prompts.
Congratulations you now have LineageOS Android 10 and are passing safetynet.
Notes:
You can Install v4a if you want.
I highly suggest installing the l'speed module from Magisk as it stabilizes the freezing/kernel.
You can also Install EdXposed and the beta for GravityBox Q ... Still passing safetynet.
Logo++ will fix your Razer logo on the rear of device.
Bluetooth works fine as does everything I've tested.
Downloads needed:
Latest phh GSI for AOSP Android 10
Latest LineageOS 17.x GSI Image
Trinity Kernel (v2)
Magisk v20.3
Pico or Nano GAPPS from OpenGapps
Optional:
V4A (requires the Magisk Module Audio Modification Library)
EdXposed Riru - Core (Magisk Module)
EdXposed - Sandhook Beta / Canary (Installed from manager)
EdXposed - Latest Manager (do not use Taichi)
GravityBoxQ Beta (gives you a lot of customization like the battery icon in statusbar)
Logo+
LSpeed Module for Magisk (lspeed-master.zip)
F2FS_FSTAB.zip from ArterKernel Thread
***Note*** this isn't flawless but when using the LSpeed Magisk Module it's very close**"
**"" LineageOS Freezes every now and then where the AOSP GSI doesn't but I can't get the AOSP to pass safetynet***
Screenshots
Note I changed the font to Comfortaa via Magisk Font Changer Module
SafetyNet
Magisk modules I personally use. Ignore older versions of the same module.
Change the fingerprint to Razer Android v9 and Reboot following the prompts.
Click to expand...
Click to collapse
Will game booster work in cortex app?
I'm on T-mobile, and with every 10 Gsi I've tried, I've installed the required ims.apk. Unfortunately, I can only send sms, not recieve. Do you not have this problem?
Can you receive text messages through LTE? I can't seem to get it to work on T-mobile.
Reznor7 said:
I'm on T-mobile, and with every 10 Gsi I've tried, I've installed the required ims.apk. Unfortunately, I can only send sms, not recieve. Do you not have this problem?
Click to expand...
Click to collapse
Try moving the ims.apk to /vendor/overlay and see if that works.
Generic123. said:
Can you receive text messages through LTE? I can't seem to get it to work on T-mobile.
Click to expand...
Click to collapse
Generic123. said:
Try moving the ims.apk to /vendor/overlay and see if that works.
Click to expand...
Click to collapse
I've re-imaged my phone too many times already, losing countless hours going back to stock when the GSI doesn't work. I'll let someone else give it a shot.
Reznor7 said:
I'm on T-mobile, and with every 10 Gsi I've tried, I've installed the required ims.apk. Unfortunately, I can only send sms, not recieve. Do you not have this problem?
Click to expand...
Click to collapse
Reznor7 said:
I've re-imaged my phone too many times already, losing countless hours going back to stock when the GSI doesn't work. I'll let someone else give it a shot.
Click to expand...
Click to collapse
No doubt I'm through with flashing back to stock countless times.....so over it
Wish I had more time and knew more about Android to bake us up a solid AOSP ROM for this phone. Great hardware to work with here and like I've said before I can't believe there is not one Dev in this community to pick this phone up as cheap as it is and get something going
JDBarlow said:
No doubt I'm through with flashing back to stock countless times.....so over it
Wish I had more time and knew more about Android to bake us up a solid AOSP ROM for this phone. Great hardware to work with here and like I've said before I can't believe there is not one Dev in this community to pick this phone up as cheap as it is and get something going
Click to expand...
Click to collapse
I feel like it's the nature of ROM developers sticking to the devices they have. They are currently developing for other phones, and don't want to have to move/develop for a new phone, nor do they have the time to develop for another phone. To be fair, we are not completely in the dark; f(x)THaxxorX seems to be working on patched versions of popular GSIs that are more suited for the hardware of the RP2:
f(x)THaxxorX said:
What my real plan is to make patch into the GSI Sources before Building it.. Those patches include voLTE fix and other features. Integrate APTX coming from Razer GSI system.img.. and many more..
Click to expand...
Click to collapse
Generic123. said:
I feel like it's the nature of ROM developers sticking to the devices they have. They are currently developing for other phones, and don't want to have to move/develop for a new phone, nor do they have the time to develop for another phone. To be fair, we are not completely in the dark; f(x)THaxxorX seems to be working on a patched version of popular GSIs that are more suited for the hardware of the RP2:
Click to expand...
Click to collapse
Oh nice!
I'll try to contain myself and be a little more patient
So true, I can just imagine the time spent to be a developer for so many devices that are out there!
Happy Valentine's Day
Ugh. I don't know why I keep trying. SMS doesn't work over LTE on TMobile using this method either. OP, your profile says you're on TMobile. Have you solved this problem somehow?
Reznor7 said:
Ugh. I don't know why I keep trying. SMS doesn't work over LTE on TMobile using this method either. OP, your profile says you're on TMobile. Have you solved this problem somehow?
Click to expand...
Click to collapse
Are you still trying to use a Q GSI? If you are willing to go back to a Pie-based GSI, installing ims.apk and moving the apk to "/vendor/overlay/" works every time for me.
Generic123. said:
Are you still trying to use a Q GSI? If you are willing to go back to a Pie-based GSI, installing ims.apk and moving the apk to "/vendor/overlay/" works every time for me.
Click to expand...
Click to collapse
From my experience, Pie ROMs have issues with the fingerprint scanner reliability, and media in a lot of games seems to have buffering issues as it frequently cuts out.
Reznor7 said:
From my experience, Pie ROMs have issues with the fingerprint scanner reliability, and media in a lot of games seems to have buffering issues as it frequently cuts out.
Click to expand...
Click to collapse
I have the same problems on ArrowOS(the fingerprint sensor problem is pretty rare. The speaker issue is really annoying, but it only happens at low volumes), but I guess it depends on how much you're willing to take. If you want to keep to use Q GSIs, our best option is just to wait for patched GSIs by f(x)THaxxorX that might be coming out at some point(Soon™).
Reznor7 said:
From my experience, Pie ROMs have issues with the fingerprint scanner reliability, and media in a lot of games seems to have buffering issues as it frequently cuts out.
Click to expand...
Click to collapse
I think the speaker itself might have issues as I even had this issue with Android 9 GSIs, from what I remember. At first I suspected buffer-related issues but after some testing it doesn't seem to be the only issue. Setting the media volume to at least 50% would allow most of the audio to get out of the speaker, but at max volume the speaker can be really loud (to the point that I feel the speaker could be potentially damaged) so I usually set it to at most 80% when I need to place the phone a bit far from where I am.
Also, I haven't gotten aptX working on Android 10 GSIs due to a strange null pointer dereference bug which would crash the entire Bluetooth stack. Only SBC works as intended. As I noticed that the author of gjf_bt Magisk module (which adds aptX libraries as well as SBC tweaks) recently blacklisted Android 10 and onwards, I think the issue might have more to do with the Android 10 system itself.
Hey! Can anyone confirm if LDAC is working on this? I have never rooted a phone before just doing it to enable LDAC. Also, does this OS support setting for Refresh rate?
I love Lineage OS 17, but I noticed that I don't receive text messages anymore. I could receive text messages when I first flashed it, and after a couple of hours, I could not. Then, I could send messages and I could send and receive calls. I could use data. I could not receive text messages. Is there a fix for this problem? I tried using Lineage 16, but I still could not receive text messages. I am back to stock, for the moment. Does anyone know how to fix this? I'm using AT&T service.
Lorelily said:
I love Lineage OS 17, but I noticed that I don't receive text messages anymore. I could receive text messages when I first flashed it, and after a couple of hours, I could not. Then, I could send messages and I could send and receive calls. I could use data. I could not receive text messages. Is there a fix for this problem? I tried using Lineage 16, but I still could not receive text messages. I am back to stock, for the moment. Does anyone know how to fix this? I'm using AT&T service.
Click to expand...
Click to collapse
It's a known issue, and unfortunately there is no reliable fix yet.
Hi,
who has experienced the same loss of HDR/HD streaming support with update 10.5.5/10.5.6 (Bootloader wasn't unlocked)?
Anyone got a solution to get back Widevine L1?
As far as we found out in the Oneplus forum all model and firmware variants are effected.
I sent logs to Oneplus through the community app but the answers were more or less prepared and only telling me that they research on this issue. Someone got the info from German support that it will be fixed through OTA, but I don't think this will be possible and most likely we have to go for RMA.
To find out about DRM/Widevine level you can use DRM Info app or Netflix in the player properties.
Best regards,
Bernd
This happened to me as well. Noticed the other day on 10.5.8 that Netflix wasn't in HD anymore. Did not unlock bootloader, just did OTA's through the system, no Oxygen Updater .
I tried unlocking and then re locking the bootloader but this did not fix the issue, I still have L3.
Really hoping I don't have to RMA for this.
Okay I was thinking about doing the same, but obviously it didn't fix it for you so I skip it...
Coming from Oneplus 5 with it's DRM drama this really annoys me.
See this post in OnePlus forum:
https://forums.oneplus.com/threads/...int-registration-error.1218379/#post-21604919
As far as I understood, flashing or in our case updating causes the persistent partition (which is encrypted with the first registered fingerprint) to get unreadable, if you removed the first fingerprint data (which I did when I registered my fingerprints freshly, after applying a screen protector) - but I could be also wrong as I used Google Translate read the original post. Maybe someone who is deeper in the rabbit hole can confirm this theory, cause it would be great to know at least where the issue comes from and if a RMA is required or a solution can be achieved via OTA.
Bernd
So removing FP data corrupts the persist partition, correct?
Of that so;
Removing FP breaks FP
Cross flashing breaks FP
Magisk Canary breaks FP
Relocking breaks FP
I did send my phone for RMA after having it for only two days. So I've been reading up on this issue and for now I have this.
Backup your persist partition
Root only with Stable Magisk 20.4
Make your own patched image
Don't relock your bootloader
Altho I can't seem to find how to backup that partition without unlocking the bootloader
I wouldn't had unlocked my bootloader if I knew it's causing so many issues. Honestly I need root just for vanced yt... So it's not worth the troubles I had ?
Balthazard said:
So removing FP data corrupts the persist partition, correct?
Click to expand...
Click to collapse
possible, as said I'm neither that far in the android rabbit hole nor is my Chinese that good but it's possible that FP is the bad guy in this game.
Not possible to backup with ADB or Fastboot?
But as far as I've read through this thread https://forum.xda-developers.com/showpost.php?p=80139723&postcount=26 even a backup/restore doesn't help. For the moment I hope for a workaround the DRM sh*t by OnePlus - I mean who the hell would use an Android Phone for content piracy...
Bootloader still locked on INAA 10.5.8, Im on L1. I had installed and uninstalled fp, now its back in, no changes
Patching your own is the smart move inho
bigjailerman said:
I had installed and uninstalled fp, now its back in, no changes
Patching your own is the smart move inho
Click to expand...
Click to collapse
Didn't touch my bootloader so far. Original FP was with 10.5.4 and deleted/readded with 10.5.6.
Did you mean by re-adding them with 10.5.8 was bringing L1 back? What should be patched?
Although my setup isn't the same as everyone else here, (bl unlocked, rooted & custom kernel. Also on beta 11). Noticed that Netflix had dropped to L3 in the playback settings section. Cleared storage on the app from settings & used magiskhide on Netflix. Seemed to put the app back on L1.
Hi everyone,
I've got a TB-X704L (a Lenovo Tab 4 10 Plus).
I managed to get it, some time ago (about Jan), to root it and (with a lot of help from people on here) get Magisk running, installing Android 9.
There, sadly the good news ended. As of about March (so around 10 weeks after I got it going), Magisk stopped passing Safetynet attenstation.
It passed basic integrity, failing ctSProfile.
I've hung on, hoping for an update that might fix it, but no, as of September we're still on 23.0 (23000) and still failing, which wipes out the reason for the tablet!
So what I'd like help with is;
- Is there a simple way to fix this Safetynet issue?
- If not, what's the best plan; to go back to stock or install a new rom?
- Any good guides on either from where I am?
I'm no noob, but the investment of time on this so far has been pretty huge!
Help much appreciated.
Thanks all,
Any help?
Any ideas how to get back to stock? or If I would sort my magisk problem by installing a different os?