Database Users

best mod for elocity A7

My tablet was runnin dexter mod 1.4 with all the patches, buy always had problems with the sd card and the usb thumb and I also had problems running some applications. Right now my A7 is running [mod] update04-19 patched market + google apps and my tablet is working almost perfect. I think this mod is better that dexter mode.
I hope everybody use this mode in their tablets.
Thanks Bestialbub for your great job.

i jus got my elocity a7
i tried to mod mine with the dexter mod 1.41 and mines wont work,
1st- i download the file didn't unzip it then i sent it to the SD card and rename it "update.zip".
2nd- i did the factory wipe/reset then i select to wipe all data
3rd- i select update.zip but i notice an message saying( E. can't read from SD card). i dont know if that is apart of the mod or what.
4th- when it is finish then i select reboot option and when it is done rebooting i get nothing new. can you help me out are do you know something that i might be doing wrong. i also did do the 1.42 patch aswell didn't work. are is there another mod that you can tell me how to get it.

hasn't been tested for application on dexter's rom, though i don't know of reason they shouldn't work. gapps can be flakey like that; actually, the files are all stock as they come from cyanogen, minus my patched market, which doesn't have any reason not to work on dexter's rom and has nothing to to with the installation of the rest of google applications, including the calendar and text messaging services; i introduced no signature issues else it wouldn't install on stock firmware.
what i can suggest, is that if you're doing this under wiped conditions; is that you need to do a "factory reset" in recovery AFTER applying my gapps update.
if you don't do the factory reset, there will be settings put in place by the provision.apk in dexter's rom (not sure if this has changed in 1.42) that may conflict with the setup of google-apps. it didn't w/ the gapps in v1 i ported from dexters rom in previous tests, but i was going for a vanilla install w/out mixed signatures/versions/dates. provision.apk is generally suggested to be removed when google-apps is intended to be installed, and it is by my installer, but not the changes done in the data folders, which is why the wipe is suggested. i think its role is replaced by the googlepartnersetup.apk, but i could be wrong.
theres also some build prop differences; some unnecessary (gsm provider info), some improved (fingerprint for added apps in addition to patched market and added permissions), and the same ones necessary for apps like skype to run.
sorry if that was too much info. i do that.
EDIT: i reviewed my original post, its step *2B*. i did update it to underline it, and provide explanation for its probable necessity.

bestialbub said:
provision.apk is generally suggested to be removed when google-apps is intended to be installed, and it is by my installer, but not the changes done in the data folders, which is why the wipe is suggested. i think its role is replaced by the googlepartnersetup.apk, but i could be wrong.
Click to expand...
Click to collapse
SetupWizard.apk replaces "provision.apk".
bestialbub said:
theres also some build prop differences; some unnecessary (gsm provider info), some improved (fingerprint for added apps in addition to patched market and added permissions), and the same ones necessary for apps like skype to run.
Click to expand...
Click to collapse
Audio fix, which enhances EQUlizer and probably a 10% audio increase, and rotation support for games is another one..
the gsm props were actually very much needed, as Google for a period enabled provider checking, so if no gsm provider was there, you could not activate a google account, so instead of ppl getting lost without MarketEnabler on a clean device, i included it for safety reasons so next time, we're prepared for such checks.. so it all serves a purpose, if you like to know more, XDA has excellent information on those topics.

SetupWizard.apk replaces "provision.apk".
Click to expand...
Click to collapse
thanks for the tip. i did concede i could be wrong, and you're right, i could find that small detail that setupwizard is known to replace functions for provision.apk. the same posts i'm finding on xda and cyanogenmod don't say anything about googlepartnersetup, however, yet its provided with gapps packages..
i also learn from demonstrated and practiced examples..
demonstrated examples i learned from, including your 1.2 rom shows your remove provision.apk and provide googlepartnersetup.apk, then reverse the decision in 1.4, i ASSUME based on signiture issues you had stated (i generally don't have those as i know i can re-use existing containers without having signature issues).
i also learned/ported from various sdk's, including google's sdk for gapp imports, and neither is required, but what is provided is sdksetup.apk.. me seeing a relation from sdksetup for an sdk/emu android device kinda indicates one might want googlepartnersetup as a counterpart on a physical device. (your 1.4 example does prove that doesn't have to be true).. but the google sdk shows that i don't need setupwizard.apk for google services either.
thought i'd relate, since most the general posted information i've seen on xda and cyanogenmod seem like vague gueses at best. though i suspect the people posting this information aren't necessarily the devs working closely with the files. just hobbists and modders making educated guesses like me.
Audio fix, which enhances EQUlizer and probably a 10% audio increase, and rotation support for games is another one..
the gsm props were actually very much needed, as Google for a period enabled provider checking, so if no gsm provider was there, you could not activate a google account, so instead of ppl getting lost without MarketEnabler on a clean device, i included it for safety reasons so next time, we're prepared for such checks.. so it all serves a purpose, if you like to know more, XDA has excellent information on those topics.
Click to expand...
Click to collapse
i was refering to MY gsm provided build prop information, i wasn't ragging on your build prop or rom addons. i followed suit to the gtab tnt modrom and added DIFFERENT gsm provider information than yourself (service provider id, not google client information). but it made no difference in gapps present demonstrated performance as this information DOES NOT (the stuff i provided/borrowed from tntlite) get passed into the android system or database files, as no service provider id is listed when opening marketaccess.apk, as it does on a phone device that does genuinely have this information.
i do concede to the thread discussion, tho, DEXTERS ROM IS THE BEST AND ONLY FULL ROM MOD FOR THE A7 TABLET!!!
my gapps mod is only intended to provide google applications ommitted by the manufacture. nothing more.
thanks for the indirect market patching instructions!

thanks am going to retry and see what happends

bestialbub said:
but it made no difference in gapps present demonstrated performance as this information DOES NOT (the stuff i provided/borrowed from tntlite) get passed into the android system or database files, as no service provider id is listed when opening marketaccess.apk, as it does on a phone device that does genuinely have this information.
Click to expand...
Click to collapse
Had the same issues, so i found the trick to be adding it in the boot.img using the default.prop, and it is added during bootup.. but now we're OT! so let's leave it at that.

a7 installation problem
these are the exat message i got (E:can't open/usb/update.zip)
(E:Can't mount USB:update.zip)
then underneath that it say (Finding update package)
then it say (Wait for 5 second)
(Installation time out)
(installation aborted)
(Formatting MISC)
these are all the thing it say during installation

these are the exat message i got was (E:can't open/usb/update.zip)
(E:Can't mount USB:update.zip)
then underneath that it say (Finding update package)
then it say (Wait for 5 second)
(Installation time out)
(installation aborted)
(Formatting MISC)
these are all the thing it say during installation

why post the same thing every 10 minutes?

.............................

demamalu said:
My tablet was runnin dexter mod 1.4 with all the patches, buy always had problems with the sd card and the usb thumb and I also had problems running some applications. Right now my A7 is running [mod] update04-19 patched market + google apps and my tablet is working almost perfect. I think this mod is better that dexter mode.
I hope everybody use this mode in their tablets.
Thanks Bestialbub for your great job.
Click to expand...
Click to collapse
That is not a mod it's the factory firmware with a patch to get market, I don't see in what way it is better than Dexter mod.

kevinppk said:
these are the exat message i got was (E:can't open/usb/update.zip)
(E:Can't mount USB:update.zip)
then underneath that it say (Finding update package)
then it say (Wait for 5 second)
(Installation time out)
(installation aborted)
(Formatting MISC)
these are all the thing it say during installation
Click to expand...
Click to collapse
When this happen I remove the .zip from file name or just rename the file but most time removing. .zip does the job...

FM Radio for R1_HD

Thanks to the release of other roms for the R1_HD it was proven that the hardware does work as an FM radio.
The spec sheet did say it had the feature.
To anyone interested in adding the radio. Attached is a flashable recovery zip that will enable it for you.
ATTENTION:!!!! For the radio to function, the kernel needed to be made "permissive"
This was line in logcat that pointed me to permissive.
Code:
W android.fmradio: type=1400 audit(0.0:641230): avc: denied { read write } for name="fm" dev="tmpfs" ino=9679 scontext=u:r:untrusted_app:s0:c512,c768 tcontext=u:object_r:fm_device:s0 tclass=chr_file permissive=0
So this update will re-flash your boot.img , And because the newest supersu has been systemless it modified your boot.img. This means after flashing this you will need to reinstall supersu.
This obviously only will work if you're rooted and have custom recovery.
Note,.1
the changed boot loader may cause the stock messenger app to force close. Other sms, and txt apps seem to be fine.
Note. 2
Just noticed amazon music and amazon video did not work after installing this. Reflashing the stock boot image allpws them to work again bit kill the radio.
Will update the zip if i find another way to allow permisive and have amazon apps still work
Boot.img seems to effect too much for my likeing. Found new (old) way to switch to permissive. .
New method for installing does not change boot.img
mode changer app is old and as of now it has hard coded root, looking for the binary in /system/xbin. This new fm_Radio_WITHOUT_boot.zip also has the fix for this root problem.
Need to install this SELinux Mode changer app
http://forum.xda-developers.com/showthread.php?t=2524485
http://forum.xda-developers.com/devdb/project/?id=1561#downloads

Awesome.
Works well from what I tried. Thanks for sharing!

Anybody know if this will KO safetynet? I already change to permissive and back, as well as tried just copying the system files, so that doesn't ko it. However, not sure what else is done.
Guess I could back up and try. If nobody knows I guess I will, but thought I would ask first.

This worked great, thank you. I'm running vampirefo's safe v6.6. Flashed your FM zip in TWRP, rebooted and it worked.

Just curious what method you chose for using permissive? I guess I've seen: kernel hack (vamp's kernel) echo script|command run w/ root, boot param. Also any ideas where the radio fails due to non-permissive mode.
How does the radio actually work btw, I know about the headphone jack requirement, but is there a specific app that uses that feature?
e/ Just a theory, I can test when I get home to build it
Code:
diff --git a/drivers/misc/mediatek/selinux_warning/selinux_warning.c b/drivers/misc/mediatek/selinux_warning/selinux_warning.c
index b8bbadb..3c70b40 100644
--- a/drivers/misc/mediatek/selinux_warning/selinux_warning.c
+++ b/drivers/misc/mediatek/selinux_warning/selinux_warning.c
@@ -52,7 +52,7 @@ const char *aee_filter_list[AEE_FILTER_NUM] = {
"u:r:ppp:s0",
/* "u:r:platform_app:s0", */
"u:r:racoon:s0",
-/* "u:r:radio:s0", */
+ "u:r:radio:s0",
"u:r:recovery:s0",
"u:r:rild:s0",
"u:r:runas:s0",

Thank you so much! Switching the FM radio to speaker is nice and loud. Wish it was this loud for my calls.
Installed fm_Radio.zip and UPDATE-SuperSU-v2.78-20160905010000.zip via TWRP on my 16/2GB on Stock Rom v12 and no issues with amazon video or stock messenger app. Will try on my 8/1GB this weekend.
EDIT
DARN! Tried to use my GPS (Waze) and screen won't rotate. Anyone one else having this issue after applying the FM radio?

mumbel said:
How does the radio actually work btw, I know about the headphone jack requirement, but is there a specific app that uses that feature?
Click to expand...
Click to collapse
If you are asking does it use a special radio app, yeah, it appears so. There is an app added to priv-app called FM-Radio in the zip. It might work with others, but I don't know. Only none specific radio app I know of (that works on many different radios) is SpiritFM, which doesn't work. Too bad, I like it.
As for SafetyNet, seems it passes it, at least for now. They are constantly making it harder to pass, so who knows what the future holds. Even just removing wirelessupdate now causes a soft fail/almost fail/whatever, blue in safetynet helper, had to restore /system from a backup.
Also, I had to switch to lopestom's recovery in order to install, as Vamp's sets the phones name as P6601, which isn't allowed by the zip.

Rotation fix
FerociousAndroid said:
Thank you so much! Switching the FM radio to speaker is nice and loud. Wish it was this loud for my calls.
Installed fm_Radio.zip and UPDATE-SuperSU-v2.78-20160905010000.zip via TWRP on my 16/2GB on Stock Rom v12 and no issues with amazon video or stock messenger app. Will try on my 8/1GB this weekend.
EDIT
DARN! Tried to use my GPS (Waze) and screen won't rotate. Anyone one else having this issue after applying the FM radio?
Click to expand...
Click to collapse
It can be fixed by http://forum.xda-developers.com/r1-hd/development/custom-rom-r1hd-zen-ui-t3473593/page5 #44

mumbel said:
Just curious what method you chose for using permissive? I guess I've seen: kernel hack (vamp's kernel) echo script|command run w/ root, boot param. Also any ideas where the radio fails due to non-permissive mode.
How does the radio actually work btw, I know about the headphone jack requirement, but is there a specific app that uses that feature?
e/ Just a theory, I can test when I get home to build it
Code:
diff --git a/drivers/misc/mediatek/selinux_warning/selinux_warning.c b/drivers/misc/mediatek/selinux_warning/selinux_warning.c
index b8bbadb..3c70b40 100644
--- a/drivers/misc/mediatek/selinux_warning/selinux_warning.c
+++ b/drivers/misc/mediatek/selinux_warning/selinux_warning.c
@@ -52,7 +52,7 @@ const char *aee_filter_list[AEE_FILTER_NUM] = {
"u:r:ppp:s0",
/* "u:r:platform_app:s0", */
"u:r:racoon:s0",
-/* "u:r:radio:s0", */
+ "u:r:radio:s0",
"u:r:recovery:s0",
"u:r:rild:s0",
"u:r:runas:s0",
Click to expand...
Click to collapse
I did not make the change to be permissive. I just used the boot.img from zenrom.
But now I have decided to suggest using the selinux mode changer app instead of changing the boot.img

theredbaron1834 said:
If you are asking does it use a special radio app, yeah, it appears so. There is an app added to priv-app called FM-Radio in the zip. It might work with others, but I don't know. Only none specific radio app I know of (that works on many different radios) is SpiritFM, which doesn't work. Too bad, I like it.
As for SafetyNet, seems it passes it, at least for now. They are constantly making it harder to pass, so who knows what the future holds. Even just removing wirelessupdate now causes a soft fail/almost fail/whatever, blue in safetynet helper, had to restore /system from a backup.
Also, I had to switch to lopestom's recovery in order to install, as Vamp's sets the phones name as P6601, which isn't allowed by the zip.
Click to expand...
Click to collapse
i can add that assert. But it is not the recovery that sets it it is the build prop on phone.

FerociousAndroid said:
Thank you so much! Switching the FM radio to speaker is nice and loud. Wish it was this loud for my calls.
Installed fm_Radio.zip and UPDATE-SuperSU-v2.78-20160905010000.zip via TWRP on my 16/2GB on Stock Rom v12 and no issues with amazon video or stock messenger app. Will try on my 8/1GB this weekend.
EDIT
DARN! Tried to use my GPS (Waze) and screen won't rotate. Anyone one else having this issue after applying the FM radio?
Click to expand...
Click to collapse
Please restore to your previous boot.img, reflash supersu and use the mode changer app to make it permissive. Will need to run the new install zip so that root will work with mode changer.

mrmazak said:
i can add that assert. But it is not the recovery that sets it it is the build prop on phone.
Click to expand...
Click to collapse
Yeah, not sure what's up with it. Just know that vampire's twrp had the name p6601 and the other one worked.

Why do we have to have root if we have TWRP? Or do we not really need it?

voluptuary said:
Why do we have to have root if we have TWRP? Or do we not really need it?
Click to expand...
Click to collapse
because the selinux mode changer app needs root. and for radio to work it needs selinux set to permissive.

Rotation Fix!
Wow, that worked on stock v12 (8GB/1GB and 16GB/2GB models)!!!! Thank you so much!!!
bjbjs said:
It can be fixed by http://forum.xda-developers.com/r1-hd/development/custom-rom-r1hd-zen-ui-t3473593/page5 #44
Click to expand...
Click to collapse
LOL... Was linked to an old post of mine that I never followed up.

mrmazak said:
because the selinux mode changer app needs root. and for radio to work it needs selinux set to permissive.
Click to expand...
Click to collapse
For what it's worth I pulled SelinuxModeChanger from FDroid and it requested root at /su/xbin just fine. No need for the files in your zip (I removed xbin from yours) I'm using v12 stock on an Amazon Blu R1 HD.

parkerlreed said:
For what it's worth I pulled SelinuxModeChanger from FDroid and it requested root at /su/xbin just fine. No need for the files in your zip (I removed xbin from yours) I'm using v12 stock on an Amazon Blu R1 HD.
Click to expand...
Click to collapse
Thanks. Good to know. I was just trying to stay with the version from tje developers thread.

Just installed SELinux Mode changer app downloaded from f-droid.org and flashed the fm radio zip file wow working like a charm!
Great job, dude!

I assume this uses the standard method of using the earphones as an antenna? Or will the radio work without earphones plugged in?

ase1590 said:
I assume this uses the standard method of using the earphones as an antenna? Or will the radio work without earphones plugged in?
Click to expand...
Click to collapse
Yep the standard headphone antenna

Possible fix for touch screen issue. ( updated )

Hello all.. so i started working again on hacks for android. I literally stopped it when i sold my sony xperia z5 premium and bought some samsung device.( It is literally no pleasure to work with all those s6 edge, s7 edge and note 5.. sorry samsung.. but your software is nothing but a nightmare for guys like me) .
I was desperate to buy a pixel 2 xl , waited so long to arrive at markets near me.. and when it arrived.. i grabbed one soon.. its a joy to hold this device.. well .. every happiness comes with some sorrows..
As soon as i got my pixel 2 xl, i unlocked the bootloader and rooted it in just 2 hours after i got it.. so.. even though this device is an awesome gadget to play with.. it have its own drawbacks at several things..
1) of course the infamous display issues.. ( lol.. those haters may wont even know what OLED( or pOLED) display does..
2) crackling of speakers ... Well i am not worried.. i know its something to do with the software.. and google or even we xda geniuses will fix it soon.. ( btw.. i am looking into some solutions)
3) touch screen sensitivity... Ya.. you heard it right.. this pannel have some touch issues.. may be most of you or some of you have noticed it now.. if you dont.. try a glass screen protector..
So while i was not able to fix the speaker issue by now ( my device is just 4 days old.. and i noticed it yesterday only, as i haven't even started using it with a sim card yet) , i possibly have a solution for touch sensitivity .. i just found it 10 minutes before creating this post. ( Thanks to some old knowledge for some sony hacks back in those days) ..
Way too boring talks?? Sorry.. i am basically a story teller type guy.. ok. No more stories.. lets get it done.
1) go to your favorite root file manager ..
2) go to - system / vendor/ usr / idc .
3) you will see a file named touchscreen.idc
4) open it with any text editor and remove all values from it and add these lines ( or replace with the attached file)
device.internal = 1
touch.deviceType = touchScreen
touch.orientationAware = 1
touch.filter.level = 0
touch.size.calibration = diameter
touch.size.scale = 5
touch.size.bias = 5
touch.size.isSummed = 0
touch.gestureMode = pointer
touch.pressure.calibration = physical
touch.pressure.scale = 0.00000125
touch.distance.calibration = none
touch.distance.scale = 0
touch.gestureMode = spots
MultitouchSettleInterval = 0.1ms
MultitouchMinDistance = 0.5 px
TapInterval = 0.5 ms
TapSlop = 0.5 px
touch.orientation.calibration = none
touch.coverage.calibration = box
5) save the file with its previous permissions ( i use filemanager named xplore, which automatically saves it with previous permissions)
6) reboot your device.. and enjoy your super responsive touch screen..
Guys.. please let me know your experience.. for further goods and bads..
Thank you..
Oh.. btw.. i have a bonus knowledge to share too..
If you find your colour calibration ( or colourfulness!! ) Of your device is low even after googles " saturated mode" , you can adjust it in build.prop file.
1) go to - system / vendor
2) open build.prop file in your fave text editor.
3) find this line - " persist.sys.sf.color_saturation=1.1 "
4) change the value to " persist.sys.sf.color_saturation=1.5 " or so..
5) you can go all the way upto "persist.sys.sf.color_saturation=2" but not more..
6) save file with its previous permissions
7) reboot and enjoy you " Samsung'ish " display..
Nb:-
dont burn ur eyes with all those alien looking colours with value of 2.. just keep it under 1.5 or so... Guys.. keep it as pixel, why go for that samsung colours
Wishes..
All praise Lord Dinkan..

Just tried it. Will report. If this fixes the telegram push to talk button, I will be overjoyed!
---------- Post added at 02:43 AM ---------- Previous post was at 02:01 AM ----------
Never mind.. the changes don't stick. I can edit the 2 files mentioned but after a reboot they back to the way they were. Tried multiple root browsers. Always after a reboot, everything is back stock settings. What am I missing?

Holy crap! Nice find my friend. I'll definitely be looking into this. Thanks a bunch! :good::good:

Same here. Didn't survive the reboot.
Sent from my Pixel 2 XL using Tapatalk

crowsnestitsupport said:
Just tried it. Will report. If this fixes the telegram push to talk button, I will be overjoyed!
---------- Post added at 02:43 AM ---------- Previous post was at 02:01 AM ----------
Never mind.. the changes don't stick. I can edit the 2 files mentioned but after a reboot they back to the way they were. Tried multiple root browsers. Always after a reboot, everything is back stock settings. What am I missing?
Click to expand...
Click to collapse
wolfeyes30 said:
Same here. Didn't survive the reboot.
Click to expand...
Click to collapse
That's kinda strange. I edited it with root explorer, rebooted, and the settings stuck! Definitely can tell the difference on my smart keyboard pro :good:

I didn't have general swipe issues, the only thing I had trouble with was swiping up on the lock screen to bring up the pin pad. Usually it took me two or three times before the pin pad would actually come up. In any event, I just tried your touch sensitivity suggestion, except that I just set it to .000125 (because I don't have a glass screen protector on it, and I didn't want it to be too sensitive), and that worked absolutely beautifully. I was just able to pull up the pin pad about 15 times in a row with absolutely no issues. Thank you so much!
If you can fix the crackling speaker sound, you'll be a god in my eyes! In my opinion, that is the only issue I have left with this phone.
I'll hit the thanks button tomorrow, I'm all out of thanks for today.
Sent from my Pixel 2 XL using XDA Labs

crowsnestitsupport said:
Just tried it. Will report. If this fixes the telegram push to talk button, I will be overjoyed!
---------- Post added at 02:43 AM ---------- Previous post was at 02:01 AM ----------
Never mind.. the changes don't stick. I can edit the 2 files mentioned but after a reboot they back to the way they were. Tried multiple root browsers. Always after a reboot, everything is back stock settings. What am I missing?
Click to expand...
Click to collapse
wolfeyes30 said:
Same here. Didn't survive the reboot.
Click to expand...
Click to collapse
There is two system folder system and system_root..
Also there is a vendor folder outside system folder..
I dont know the system structure yet ( as i didn't disassemble the factory images yet ) .. so i dont know why this all confusing folder structure..
Btw.. i think you have looked into system_root folder or vendor folder outside system folder..
Make sure u go into system ( not system_root) and find the file..
System - vendor - usr - idc..
Or may be just your filemanager didn't saved the value??

sharkie405 said:
I didn't have general swipe issues, the only thing I had trouble with was swiping up on the lock screen to bring up the pin pad. Usually it took me two or three times before the pin pad would actually come up. In any event, I just tried your touch sensitivity suggestion, except that I just set it to .000125 (because I don't have a glass screen protector on it, and I didn't want it to be too sensitive), and that worked absolutely beautifully. I was just able to pull up the pin pad about 15 times in a row with absolutely no issues. Thank you so much!
If you can fix the crackling speaker sound, you'll be a god in my eyes! In my opinion, that is the only issue I have left with this phone.
I'll hit the thanks button tomorrow, I'm all out of thanks for today.
Click to expand...
Click to collapse
Meh....just make him a special font package bro. That'll be some good thanks for sure! :good:

Root explorer doesn't save the change for some odd reason. I just tried xplore as well with no change. Once I reopen the file the value was back to stock.
Sent from my Pixel 2 XL using Tapatalk

wolfeyes30 said:
Root explorer doesn't save the change for some odd reason. I just tried xplore as well with no change. Once I reopen the file the value us back to stock.
Click to expand...
Click to collapse
I use FX and had no issues.
Sent from my Pixel 2 XL using XDA Labs

Like the OP said. The pic shows the proper path to the file. This is using root explore.

Dtbo image causing this maybe? I'm using the unofficial magisk without patching the dtbo.

crowsnestitsupport said:
Just tried it. Will report. If this fixes the telegram push to talk button, I will be overjoyed!
---------- Post added at 02:43 AM ---------- Previous post was at 02:01 AM ----------
Never mind.. the changes don't stick. I can edit the 2 files mentioned but after a reboot they back to the way they were. Tried multiple root browsers. Always after a reboot, everything is back stock settings. What am I missing?
Click to expand...
Click to collapse
wolfeyes30 said:
Same here. Didn't survive the reboot.
Click to expand...
Click to collapse
Avb 2.0 dm verity has to be patched in the dtbo image in order to edit the vendor partition. The above fix will stick once the dtbo image is patched. Will not stick without the patch.
---------- Post added at 03:04 AM ---------- Previous post was at 03:01 AM ----------
wolfeyes30 said:
Dtbo image causing this maybe? I'm using the unofficial magisk without patching the dtbo.
Click to expand...
Click to collapse
You got it. That's the problem

Golf c said:
Avb 2.0 dm verity has to be patched in the dtbo image in order to edit the vendor partition. The above fix will stick once the dtbo image is patched. Will not stick without the patch.
---------- Post added at 03:04 AM ---------- Previous post was at 03:01 AM ----------
You got it. That's the problem
Click to expand...
Click to collapse
Hey Golfc, you seem to know this magisk stuff pretty well. I'm still using the 14.5 zip, but using the 5.5 app. As you can see by the pic, force encryption and the AVB thingy are checked off. Everything is working fine. Would that change if I flashed the 14.6 version?? Only reason I haven't is I don't want to mess up my V4A. Any insight is greatly appreciated :good:

What's the correct way for me to get onboard with the official magisk with a patched dtbo?
I have twrp installed already and using custom kernel. Uninstall the unofficial magisk from magisk manager then flash stock boot image, flash stock dtbo image, flash custom kernel then flash official magisk?
Thanks
I'm sure I need to reflash twrp.zip somewhere during that process to keep from getting the stock recovery.

Badger50 said:
Hey Golfc, you seem to know this magisk stuff pretty well. I'm still using the 14.5 zip, but using the 5.5 app. As you can see by the pic, force encryption and the AVB thingy are checked off. Everything is working fine. Would that change if I flashed the 14.6 version?? Only reason I haven't is I don't want to mess up my V4A. Any insight is greatly appreciated :good:
Click to expand...
Click to collapse
Are you still getting the internal storage corruption message on boot? Your dtbo image is still patched then. It will not change by updating to 14.6. The only way to change is to fastboot the stock dtbo image and flash 14.6. In your current situation, all you would have to do is flash stock dtbo image and 14.6 Your Viper will still work.

wolfeyes30 said:
Root explorer doesn't save the change for some odd reason. I just tried xplore as well with no change. Once I reopen the file the value was back to stock.
Click to expand...
Click to collapse
I don't know what is the problem with your file manager bro.. i changed and checked it several times.. every single time it is working.. actually i have some more tweaks with touch.. i am experimenting some values.. so i put on each values and checking every single time..

Golf c said:
Are you still getting the internal storage corruption message on boot? Your dtbo image is still patched then. It will not change by updating to 14.6. The only way to change is to fastboot the stock dtbo image and flash 14.6. In your current situation, all you would have to do is flash stock dtbo image and 14.6 Your Viper will still work.
Click to expand...
Click to collapse
Thanks bud. Not sure about the V4A that Zackptg5 helped create. Been reading that magisk 14.6 is causing it not to work. Guess I'll find out. Thanks again :good:

wolfeyes30 said:
What's the correct way for me to get onboard with the official magisk with a patched dtbo?
I have twrp installed already and using custom kernel. Uninstall the unofficial magisk from magisk manager then flash stock boot image, flash stock dtbo image, flash custom kernel then flash official magisk?
Thanks
I'm sure I need to reflash twrp.zip somewhere during that process to keep from getting the stock recovery.
Click to expand...
Click to collapse
1. Fastboot stock dtbo image and stock boot image
2. Reboot Twrp recovery from bootloader screen
2. Flash Twrp, custom kernel and Magisk 14.6 in one session.
No need to uninstall anything. I also assume your custom kernel uses a Ak2 zip for flashing.

But i seriously doubt that the kernal configuration for touch screen calibration and the actual driver values of the touch screen drivers are some how miss matched.. the sensitivity is way too low at extreme bottom corners of the display ( both left and right bottom corners) .. but i have tweaked the values to give much better touch response than original. For now i think we can deal with the problem this way till google or some of us will come out with better solution.

Phone blocked on unlock phase.

Hi,
This last days I have stranges things with my phone, and it is the first time that happened.
When I reboot after install magisk modules or adaway file host, my phone cannot be unlocked.
I type the pin code for unlock my sim card, and after the pin code for unlock the phone.
At this moment I have a black screen and I must retype my code ever and ever.
Nothing to do, just reinstall all the rom. Unable to use a clean backup, this is the same problem.
If anybody knows this issue and can save my life, you're welcome.
Thanks a lot, cordialement

I found the issue.
I can install magisk and reboot normally.
But when I install modules everything is locked.
If anyone have infos?

Lethalben said:
I found the issue.
I can install magisk and reboot normally.
But when I install modules everything is locked.
If anyone have infos?
Click to expand...
Click to collapse
Hello, I am updating my mom's phone and saw your post.
Unfortunately that bug has been around for a few months, I have a quick temporary fix for you but unfortunately the bug will return, if you can live without a screen lock that may be you only solution for now.
Lock Screen ( delete the lock)
Boot to Recovery
Go to Recovery File Manager
Navigate to the /data/system folder
locate and delete the file called : locksettings.db
Now you no longer have a screen lock and you can easily get into the phone.
FYI : If you want the lock again , simply create a new key or pattern
This issue could be anything such as corrupted permissions, It seems that it pops up after installing audio mods and substratum. But I don't think it is caused by either one.
If your phone gets hot while experiencing this issue flash the thermalfix 7 file, located on the thermals thread https://forum.xda-developers.com/showpost.php?p=78717015&postcount=18

This morning I've formated my phone to be sure is not an error from me. I will try your solution if it happens again.
Thanks for your response my friend!

Is it possible f2fs formating data partition is the issue?

Lethalben said:
Is it possible f2fs formating data partition is the issue?
Click to expand...
Click to collapse
It's very likely that this is the origin of the problem. It happens to me too, and have F2FS formated data too.

Forsaken75 said:
It's very likely that this is the origin of the problem. It happens to me too, and have F2FS formated data too.
Click to expand...
Click to collapse
I'm go back to ext4 and everything is OK.
I saw a magisk module who's made for stop this issue.
If there is a magisk module for that I think the problem is f2fs!

Lethalben said:
Is it possible f2fs formating data partition is the issue?
Click to expand...
Click to collapse
I don't think so because I only use Ext4

Well, I think I finally found the true origin of this problem: Magisk Hide interferes with newer Webview implementations, as explained here:
https://www.didgeridoohan.com/magisk/MagiskIssues#
I also found several workarounds:
1) Disable Magisk Hide. I need some banking apps, so for me this is not an option.
2) Use Chrome Beta and select its engine as default Webview in Developer Options. Chrome Beta signature is not buggy, so it works as it should. This is the solution that I've chosen, by the way.
3) Ask our developers @codeworks @mosimchah and the others if they could include this commit that fixes invalid signatures in their future releases:
https://github.com/LineageOS/android_vendor_cm/commit/a3a76f5d1cc233ad8024ffdc74bb3a786e1605c3

Hi all:
Have you managed to solve the screen lock problem? I did not achieve it and I followed all the instructions you mentioned.
A greeting.

txiscoman said:
Hi all:
Have you managed to solve the screen lock problem? I did not achieve it and I followed all the instructions you mentioned.
A greeting.
Click to expand...
Click to collapse
It's some app compatibility issue with Android Pie/Webview for sure. In my case was my banking app, changing to Chrome beta fixed the problem (app still crashes from time to time, but I'm not having the damned screen lock problem anymore)
You can try using Webview component alone from Play Store (I notice that in my case it's working too) or do some research to find out which app is causing the issue and uninstall it (if you can live without it, of course)

Deleted

Going back to stock rom, coming from lineageos 16 ????? Lenovo Tab4 10 Plus TB-X704F

Hey guys,
since I dont get neither Netflix nor Disney+ to work on my TB-X704F after having flashed LOS 16, I want to go back to stock rom. I've already tried to use Lenovo Smart Assistant but the flashing procedure always fails. I also tried QComLoader but also fails at 5%.
Is there a working way on going back to stock rom having TRWP ans LOS 16 installed???
Due to the fact that Netflix and Disney+ arent working (already tried Magisk module to change the tablets' fingerprint), I need to go back to stock rom.
Thanks in advance!!!!

Please use this tool to flash the stock rom: https://qfiltool.com/qfil-tool-v2-0-2-3

need help here. I'm flashed LineageOS previously. Can't install NetFlix hence i want to switch back to stock. I've installed the drivers and QFIL software. however when the device is off, i hold the volume up button then plug in the usb, but the QFIL software still show port not available. I entered the TWRP screen asking me to whether i can choose Boot to FFBM. Restart Bootloader.. etc. what should i choose?

I assume by "magisk module", you mean the termux props method? That's worked for me on several devices.
Also I really don't know how I can help you past that, most stock firmwares aren't designed to be flashed on modified devices. Very few manufacturers even support that (Samsung, LG and OnePlus are falriy major exceptions)
Edit: just realised the age of the thread, apologies.

rhchia said:
need help here. I'm flashed LineageOS previously. Can't install NetFlix hence i want to switch back to stock. I've installed the drivers and QFIL software. however when the device is off, i hold the volume up button then plug in the usb, but the QFIL software still show port not available. I entered the TWRP screen asking me to whether i can choose Boot to FFBM. Restart Bootloader.. etc. what should i choose?
Click to expand...
Click to collapse
I've got the same problem. What did you do in the end?

K14_Deploy said:
I assume by "magisk module", you mean the termux props method? That's worked for me on several devices.
Also I really don't know how I can help you past that, most stock firmwares aren't designed to be flashed on modified devices. Very few manufacturers even support that (Samsung, LG and OnePlus are falriy major exceptions)
Edit: just realised the age of the thread, apologies.
Click to expand...
Click to collapse
What exactly is the termux props method?
Is that to fix Magisk not authenticating? Or to allow the tool QFIL to restore stock?

boomhaueruk said:
What exactly is the termux props method?
Is that to fix Magisk not authenticating? Or to allow the tool QFIL to restore stock?
Click to expand...
Click to collapse
I mean the MagiskHide Props Config, which requires Termux. Basically you install the module, give Termux root and configure props with it. Then you use MagiskHide to hide magisk from them.
On the topic of reverting to stock, it's not possible. Custom firmware is almost always a one way process, and you understand if you do it things like the OP has described can and will happen. People who want things to "just work" use stock firmware, or an Apple device, it was never designed to not need tinkering.

K14_Deploy said:
I mean the MagiskHide Props Config, which requires Termux. Basically you install the module, give Termux root and configure props with it. Then you use MagiskHide to hide magisk from them.
On the topic of reverting to stock, it's not possible. Custom firmware is almost always a one way process, and you understand if you do it things like the OP has described can and will happen. People who want things to "just work" use stock firmware, or an Apple device, it was never designed to not need tinkering.
Click to expand...
Click to collapse
Goodness, I'm not a person who needs a 'just work' situation. It took weeks to get this onto stock and I've spent a long time reading up trying to fix Magisk. Surely there has to be a point when you're actually using the device and not just fixing it!
Basic things like being able to download and use apps...that seems like a reasonable request.
I think there's 'tinkering' and 'it doesn't work!'
Also, I've rolled back to stock roms before on various phones, recovery and so on - not with this tablet admittedly. Surprised it seems such a difficult or - as you say - impossible process. But hey.
That said, I appreciate the help! I really do.
So; I need to find 'Termux'. https://termux.com/
This says I get it from 'F Droid'. But I then found a link on their webpage to this;
https://f-droid.org/repo/com.termux_117.apk
I'm assuming that's the right one.
It looks like a terminal?
Googling for Termux Magiskhide props config got me to this youtube video;
It's in Indonesian, but shows you some steps. Would that be the best place to find instructions?

boomhaueruk said:
Goodness, I'm not a person who needs a 'just work' situation. It took weeks to get this onto stock and I've spent a long time reading up trying to fix Magisk. Surely there has to be a point when you're actually using the device and not just fixing it!
Basic things like being able to download and use apps...that seems like a reasonable request.
I think there's 'tinkering' and 'it doesn't work!'
Also, I've rolled back to stock roms before on various phones, recovery and so on - not with this tablet admittedly. Surprised it seems such a difficult or - as you say - impossible process. But hey.
That said, I appreciate the help! I really do.
So; I need to find 'Termux'. https://termux.com/
This says I get it from 'F Droid'. But I then found a link on their webpage to this;
https://f-droid.org/repo/com.termux_117.apk
I'm assuming that's the right one.
It looks like a terminal?
Googling for Termux Magiskhide props config got me to this youtube video;
It's in Indonesian, but shows you some steps. Would that be the best place to find instructions?
Click to expand...
Click to collapse
Is this going to be a problem?
Magisk is dropping support for hiding root access from apps
Magisk, the popular Android rooting tool, will continue to be developed by topjohnwu, but without its root hiding feature called MagiskHide.
www.xda-developers.com

boomhaueruk said:
Goodness, I'm not a person who needs a 'just work' situation. It took weeks to get this onto stock and I've spent a long time reading up trying to fix Magisk. Surely there has to be a point when you're actually using the device and not just fixing it!
Basic things like being able to download and use apps...that seems like a reasonable request.
I think there's 'tinkering' and 'it doesn't work!'
Also, I've rolled back to stock roms before on various phones, recovery and so on - not with this tablet admittedly. Surprised it seems such a difficult or - as you say - impossible process. But hey.
That said, I appreciate the help! I really do.
So; I need to find 'Termux'. https://termux.com/
This says I get it from 'F Droid'. But I then found a link on their webpage to this;
https://f-droid.org/repo/com.termux_117.apk
I'm assuming that's the right one.
It looks like a terminal?
Googling for Termux Magiskhide props config got me to this youtube video;
It's in Indonesian, but shows you some steps. Would that be the best place to find instructions?
Click to expand...
Click to collapse
You can install Termux from the Play Store if you have GApps. I did and it worked. And yes, it is a terminal. I've just upgraded to 17.1 on this device so I'm going to be doing it again sooner rather than later anyway.

K14_Deploy said:
You can install Termux from the Play Store if you have GApps. I did and it worked. And yes, it is a terminal. I've just upgraded to 17.1 on this device so I'm going to be doing it again sooner rather than later anyway.
Click to expand...
Click to collapse
Thanks.
I guess my other issue is I'm not actually sure what steps I'm supposed to do next.
That youtube video looks really dodgy!
It's nice to find someone else on this device. Mine has sat unused for months, I've decided to finally either get it to work properly or bin it. Todays the day.

boomhaueruk said:
Thanks.
I guess my other issue is I'm not actually sure what steps I'm supposed to do next.
That youtube video looks really dodgy!
Click to expand...
Click to collapse
Ok, so...
Make sure Magisk has "MagiskHide Props Config" and "Busybox For Android NDK" and root fully enabled. Hide must be disabled. If this isn't the case, do so and then reboot.
Open Termux. Type 'su' to give root access. Then type 'props' and follow the menu for your device. Type '1' for 'Edit device fingerprint'. Type 'f' for 'Pick a certified fingerprint'. Type '13' for 'Lenovo'. Type '2' for 'Lenovo Tab 4 8 Plus TB-8704F (8.1.0)'. If you have another device you might be out of luck. Type 'y' for 'yes'. Wait. Type 'y' again to reboot.
Configure MagiskHide to hide these parts of GPS + any other root sensitive apps. The screenshot I have was taken from a OnePlus but it shows the GPS that needs to be hidden. The less you can get away with hiding the better for performance reasons. Also make sure to repackage Magisk as 'Settings' and change the name of the 'TWRP' folder using a root file explorer (for some reason I don't have one) to... I'm partial to 'f**kyougoogle' personally, but anything will do. Reboot again and Disney+ should work just fine. If it doesn't, I can't help you.
I'd recommend moving to 18.1 before doing this, you'll have to start from square 1 but it means you're more up to date and won't have to do it again until someone builds 19.1 for this device. Can confirm, that build works.
This isn't without risk. Some apps specifically wanting android 11 might not work right. But it SHOULD fix root sensitive apps that use Safetynet. I also can't say anything about Widevine compatibility as I don't have Disney+ on this device.
boomhaueruk said:
Thanks.
I guess my other issue is I'm not actually sure what steps I'm supposed to do next.
That youtube video looks really dodgy!
It's nice to find someone else on this device. Mine has sat unused for months, I've decided to finally either get it to work properly or bin it. Todays the day.
Click to expand...
Click to collapse

K14_Deploy said:
Ok, so...
Make sure Magisk has "MagiskHide Props Config" and "Busybox For Android NDK" and root fully enabled. Hide must be disabled. If this isn't the case, do so and then reboot.
Open Termux. Type 'su' to give root access. Then type 'props' and follow the menu for your device. Type '1' for 'Edit device fingerprint'. Type 'f' for 'Pick a certified fingerprint'. Type '13' for 'Lenovo'. Type '2' for 'Lenovo Tab 4 8 Plus TB-8704F (8.1.0)'. If you have another device you might be out of luck. Type 'y' for 'yes'. Wait. Type 'y' again to reboot.
Configure MagiskHide to hide these parts of GPS + any other root sensitive apps. The screenshot I have was taken from a OnePlus but it shows the GPS that needs to be hidden. The less you can get away with hiding the better for performance reasons. Also make sure to repackage Magisk as 'Settings' and change the name of the 'TWRP' folder using a root file explorer (for some reason I don't have one) to... I'm partial to 'f**kyougoogle' personally, but anything will do. Reboot again and Disney+ should work just fine. If it doesn't, I can't help you.
I'd recommend moving to 18.1 before doing this, you'll have to start from square 1 but it means you're more up to date and won't have to do it again until someone builds 19.1 for this device. Can confirm, that build works.
This isn't without risk. Some apps specifically wanting android 11 might not work right. But it SHOULD fix root sensitive apps that use Safetynet. I also can't say anything about Widevine compatibility as I don't have Disney+ on this device.
Click to expand...
Click to collapse
Thanks.
OK. So, I've attached a few pics to show you where I am.
Booted, checked into Magisk for those settings. I can see 'Magiskhide', so I can untick that, but how do I ensure "Magisk has "MagiskHide Props Config" and "Busybox For Android NDK" and root fully enabled"
Root wise, I'm pretty sure it is, but yes, not sure how I double check!

boomhaueruk said:
Thanks.
OK. So, I've attached a few pics to show you where I am.
Booted, checked into Magisk for those settings. I can see 'Magiskhide', so I can untick that, but how do I ensure "Magisk has "MagiskHide Props Config" and "Busybox For Android NDK" and root fully enabled"
Root wise, I'm pretty sure it is, but yes, not sure how I double check!
Click to expand...
Click to collapse
They are Magisk modules, you go to there the puzzle piece is and search for them.

boomhaueruk said:
Thanks.
OK. So, I've attached a few pics to show you where I am.
Booted, checked into Magisk for those settings. I can see 'Magiskhide', so I can untick that, but how do I ensure "Magisk has "MagiskHide Props Config" and "Busybox For Android NDK" and root fully enabled"
Root wise, I'm pretty sure it is, but yes, not sure how I double check!
Click to expand...
Click to collapse
OK, found 'root checker' on the play store. And Termux.
so I have root.

K14_Deploy said:
They are Magisk modules, you go to there the puzzle piece is and search for them.
Click to expand...
Click to collapse
Ah! Got it. Ok, went into Magisk, went to the puzzle piece, found them both and...
Ah, I've just seen you've said "I'd recommend moving to 18.1 before doing this, you'll have to start from square 1 but it means you're more up to date and won't have to do it again until someone builds 19.1 for this device. Can confirm, that build works."
Right. I'd better go and find all the instructions for that. I've forgotten how I got this thing onto custom firmware, but I've got recovery installed.

boomhaueruk said:
Ah! Got it. Ok, went into Magisk, went to the puzzle piece, found them both and...
Ah, I've just seen you've said "I'd recommend moving to 18.1 before doing this, you'll have to start from square 1 but it means you're more up to date and won't have to do it again until someone builds 19.1 for this device. Can confirm, that build works."
Right. I'd better go and find all the instructions for that. I've forgotten how I got this thing onto custom firmware, but I've got recovery installed.
Click to expand...
Click to collapse
Go to the 18.1 thread on this forum and look for the instructions for flashing without being on stock. Also use TWRP 3.4.0.0. You will need a computer, as you have to wipe internal storage and use ADB.

K14_Deploy said:
Go to the 18.1 thread on this forum and look for the instructions for flashing without being on stock. Also use TWRP 3.4.0.0. You will need a computer.
Click to expand...
Click to collapse
I may stay where I am on Android 9. I've just seen it doesn't support sim and I sort of need that.
I can always come back and do that later, right?
I'm a bit worried about bricking it too. I might just get myself onto Android 9 working with the fix for now. It took me so long to get it onto custom rom the first time.

boomhaueruk said:
I may stay where I am on Android 9. I've just seen it doesn't support sim and I sort of need that.
I can always come back and do that later, right?
I'm a bit worried about bricking it too. I might just get myself onto Android 9 working with the fix for now. It took me so long to get it onto custom rom the first time.
Click to expand...
Click to collapse
Yeah of course, but you will have to start over if / when you upgrade

Ah. Hit a snag.
You said "Type '2' for 'Lenovo Tab 4 8 Plus TB-8704F (8.1.0)"
I've got the TB-8704L, the 10 inch.
Let me see if anythings listed.