My Phone (Cubot Power, Android 8.1) always shows a red text in the top right corner of the screen saying "Not Veify".
It shows this message since I reinstalled my stock rom with the SP Flash tool.
If anyone knows a way to get rid of this message let me know.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Di you fix this?
Hi. Did you found solution for this problem? I have this same in cubot nova.
It's an interesting problem.
The most interesting part is that when you click few times on this "not verify", but only while you are configurating phone after fabric settings-phone is connecting with internet and downloading qr codes scaner, like this verification is about scanning code.
"Not Verify" Message
Hello Sir,
i've found a solution to your problem:
so Here's the step you should follow...
Step1 : install gravity box, that depends on your android version [Pie, Oreo, Marshmallow, Kitkat etc.]
Step2: install "Xposed installer" & enable gravity box in modules then reboot your phone.
Warning: this will brick your phone if you don't root your phone them properly ( you can use "Root Checker").
Step3: after you reboot your phone, open gravity box and then go to "Advance Tuning" & enable "Master Switch" then reboot your phone again.
Step4: Open gravity box again, Go to: "Advance tuning", "Frame work" and find "Config_add_tee_watermark_state"
press the "Override" option and then check the "Overridden value" that will turn the watermark off ("Not Verify") to False
Step5: Reboot your phone again....
"Congratulations, your phone is now working as normal"
Btw Here's a full proof: [/URL]https://drive.google.com/open?id=19MXFuMAxQQTv_aU5ua33SMdauy7akGmn[/URL]
Streetfixers
The watermark option isnt showing up help pls
Drahthase said:
The watermark option isnt showing up help pls
Click to expand...
Click to collapse
try here: https://forum.xda-developers.com/android/help/cubot-quest-rid-off-annoying-red-t4130933
streetfixers said:
"Not Verify" Message
Hello Sir,
i've found a solution to your problem:
so Here's the step you should follow...
Step1 : install gravity box, that depends on your android version [Pie, Oreo, Marshmallow, Kitkat etc.]
Step2: install "Xposed installer" & enable gravity box in modules then reboot your phone.
Warning: this will brick your phone if you don't root your phone them properly ( you can use "Root Checker").
Step3: after you reboot your phone, open gravity box and then go to "Advance Tuning" & enable "Master Switch" then reboot your phone again.
Step4: Open gravity box again, Go to: "Advance tuning", "Frame work" and find "Config_add_tee_watermark_state"
press the "Override" option and then check the "Overridden value" that will turn the watermark off ("Not Verify") to False
Step5: Reboot your phone again....
"Congratulations, your phone is now working as normal"
Btw Here's a full proof: [/URL]https://drive.google.com/open?id=19MXFuMAxQQTv_aU5ua33SMdauy7akGmn[/URL]
Click to expand...
Click to collapse
--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
I tried to uninstall the Xposed installer and it came back the "Not Verify" and I installed it back and it's good to go again. Thanks anyway.
P3X3 said:
My Phone (Cubot Power, Android 8.1) always shows a red text in the top right corner of the screen saying "Not Verify".
It shows this message since I reinstalled my stock rom with the SP Flash tool.
If anyone knows a way to get rid of this message let me know.
Click to expand...
Click to collapse
Got solved this after experiencing with my Cherry Mobile Flare S7 just this February 2021.
Assuming you have all this:
Firmware
SP Flash
HxD (HexEditor)
Step #1. Get the system.img from the firmware, make your backup first.
Step #2. Load it to HxD
Step #3. Press A to highlight All then Control F to Find, [check ] Case sensitive, Search direction (All), Type "Not Verify"
Step #4. Click Search All
Step #5. Edit like on the next pictures
Step #6. Save
Step #7. Replace your original file with one you modified
Step #8. Load it up with your SP Flash
Step #9. Uncheck all except the system.img.
Step #10. Flash and Done
Hey folks, none of the above worked for me on blackview BV8800, however, since my device was rooted with magiks with zygisk support. I was able to use this module https://github.com/Magisk-Modules-Repo/MagiskHidePropsConf, as it gives the ability to change props.
After enabling it in magisk, and rebooting. I fired up termux, in it, I entered su, to become superuser, and then used its own command: props as such:
Code:
props ro.mtk_tee_check_support 0
It asked me when I would like that to be applied, I said option 4, at both boot stages. And then rebooted and now it's gone!
rimkashox said:
Hey folks, none of the above worked for me on blackview BV8800, however, since my device was rooted with magiks with zygisk support. I was able to use this module https://github.com/Magisk-Modules-Repo/MagiskHidePropsConf, as it gives the ability to change props.
After enabling it in magisk, and rebooting. I fired up termux, in it, I entered su, to become superuser, and then used its own command: props as such:
Code:
props ro.mtk_tee_check_support 0
It asked me when I would like that to be applied, I said option 4, at both boot stages. And then rebooted and now it's gone!
Click to expand...
Click to collapse
great it works perfectly ... thanks bro
rimkashox said:
Hey folks, none of the above worked for me on blackview BV8800, however, since my device was rooted with magiks with zygisk support. I was able to use this module https://github.com/Magisk-Modules-Repo/MagiskHidePropsConf, as it gives the ability to change props.
After enabling it in magisk, and rebooting. I fired up termux, in it, I entered su, to become superuser, and then used its own command: props as such:
Code:
props ro.mtk_tee_check_support 0
It asked me when I would like that to be applied, I said option 4, at both boot stages. And then rebooted and now it's gone!
Click to expand...
Click to collapse
did you have same method for the orange state message appear on boot ? thanks
Related
How to use GeoWhere to control your location in Pokémon go with an analogue stick (joystick) on android.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
PLEASE NOTE: FOR LOLIPOP 5.0.1 YOU WILL NEED TO FLASH A DEODEXED ROM IN ORDER TO USE EXPOSED FRAMEWORK, PLEASE SEE BOTTOM FOR INSTRUCTIONS.
I DO NOT TAKE RESPONSIBILITY FOR LOSS OF WARRANTY OR DAMAGE TO ANY DEVICES AS A RESULT OF FOLLOWING THIS TUTORIAL.
QUICK GUIDE (For experienced users)
1. Root Your Device
2. Install Exposed Framework for your device
a. http://forum.xda-developers.com/xposed/unofficial-xposed-samsung-lollipop-t3180960 (For Samsung devices)
3. Install “Hide My Location” http://dl-xda.xposed.info/modules/com.github.marlowww.hidemocklocation_v4_d70206.apk
4. Activate “Hide My Location” module in “Exposed Installer”
5. Reboot and black list “Pokemon Go”
6. Install GeoWhere and start playing
a. https://play.google.com/store/apps/details?id=za.co.epicdev.geowhere
7. Remember to allow “Draw over other apps” for devices with lollipop and above
8. Enable “allow mock locations” in developer options
INDEPTH GUIDE (Need help Rooting Device)1. Download Odin 3.09 and a “Recover Image” (SOME DEVICES MIGHT NOT SUPPORT ODIN, READ TWRP INSTALL INSTRUCTIONS)
2. Find the correct recovery for your device (device model) https://twrp.me/Devices/
3. Put device into download mode (on Samsung devices you will hold VOLUME-DOWN + HOME + POWER BUTTON). You can google “how to put device model into recovery mode” for your device
4. Unzip Odin and double click the Odin3 v3.09.exe to start Odin and you should see a screen like below.
5. Connect your device to the PC and let Odin detect it. Once Odin detects the device the section that says ID:COM will light up blue
6. Click the AP button and then choose the recovery image file that you downloaded. It will have an extension of .img.tar
7. Once the file is loaded, click start
If you get a message saying that the install failed because of FRP lock then enable Allow OEM unlock in developer settings
8. Most devices will reinstate the original recovery on start up so as soon as the device reboots press VOLUME-UP + HOME + POWER to boot into the recovery (some devices may vary - check for your device)
9. (OPTIONAL BUT SUGGESTED) Once you have successfully booted into the recovery, I suggest you perform a backup of your device by touching backups and sliding the bar across to start the process. (If you are unsure, google “team win backing up device”)
If your device gets stuck in a boot loop boot back into TWRP and install SuperSu as instructed bellow and it will fix it self
10. Reboot your device
11. You will now need to root your device. You can google the best method for your specific device, this method will work on most devices including Marshmallow devices.
12. Download “SuperSu” from http://forum.xda-developers.com/apps/supersu/2014-09-02-supersu-v2-05-t2868133 and copy the file to your device
13. Shut your device down and boot back into the recovery again with VOLUME-UP + HOME + POWER or whichever method is supported for your device.
14. Touch install and then look for the file you just copied and select it. Swipe to start installation
15. Clear “Dalvik Cache” and then reboot your device
16. Download Xposed framework for your device (check if your device is 64bit or not)
i. Marshmallow (Samsung devices Note4) ARM https://www.androidfilehost.com/?fid=24572330218881465
ii. Marshmallow (Samsung ARM64bit devices Note 5, Galaxy s7) https://www.androidfilehost.com/?fid=24572330218881466
iii. Lolopop 5.1 https://www.androidfilehost.com/?fid=24566454284190899
iv. KitKat only requires the framework manager apk and doesn’t need flashing http://dl-xda.xposed.info/modules/de.robv.android.xposed.installer_v33_36570c.apk
17 Only if you are above kitkat 4.4: Copy the downloaded file to your device and install it with the recovery the same way you did with the SuperSu file. ( For kitkat 4.4 install the Xposed Insataller in let it install for you by opening the app)
18. Clear “Dalvik Cache” and then reboot your device
19. Download the following app to your device http://forum.xda-developers.com/attachment.php?attachmentid=3383776&d=1435601440
20. Install the app
21. Download “Hide mock Location” http://dl-xda.xposed.info/modules/com.github.marlowww.hidemocklocation_v4_d70206.apk
22. Install “Hide Mock Location”
23. Open Xposed Installer and select modules.
24. Enable “Hide Mock Location”
25. Reboot device
26. Open Hide Mock Location app and blacklist Pokemon Go
27. Now you can install GeoWhere and start using the app to spoof your location in Pokemon Go https://play.google.com/store/apps/details?id=za.co.epicdev.geowhere
aa. Remember to allow “Draw over other apps” for devices with lollipop and above
bb. Enable “allow mock locations” in developer options
For Lolipop 5.0.1 Users
You will need to flash a Deodexed rom in order to use Exposed Framework. You need to find a Deodexed or custom rom for your specific device. XDA (http://forum.xda-developers.com/) is a good place to look. For my galaxy S4 I used a cyanogenmod Custom rom which worked fine but some people might not want a custom rom and therefore require a Deodexed rom.
For those of you who want to install cyanogenmod on a galaxy s4 i9500. Use the following link and then flash the file using the recovery method described above https://download.cyanogenmod.org/get/jenkins/169278/cm-12.1-20160710-NIGHTLY-i9500-recovery.img
You can then flash the required Exposed framework for your device for SDK 22
http://dl-xda.xposed.info/framework/sdk22/
Thanks, I followed the steps and it works really well
Great App!
Thanks, I got it to work. It was tricky with my Huawei because I couldn't get Odin to work on it.
Why does "Allow mock locations" option uncheck as soon as I leave the Developer Optio
Why does "Allow mock locations" option uncheck as soon as I leave the Developer Option tab?
Hi, this happens if you have hide mock location set to whitelist mode and have not specified the correct application to whitelist. Rather use black list mode and only check Pokemon go as shown in the screen shot. Also check to see if the hide mock location module has an update.
Rural areas
This app works really well for people in rural areas that would like to play Pokemon Go. I did have a slight problem when trying to root my mobile but it all worked out in the end. :good: Thank you! I recommend this app. Just follow the instructions carefully.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Tutorials and the tools are not my work, so I don't take any credit. However, the tutorial is come from China. I combine my experience and translate them as much as I can to english.
Instructions:
First, download the root files (at the bottom of this post) accroding to your tablet model (at the back of your tablet) and install the driver in the computer.
Please install in the following order:
1) iSocUSB-Driver-Setup-1.2.0.exe
2) IntelAndroidDrvSetup1.5.0.exe
3) PhoneFlashTool_5.3.4.0_win32.exe
Pay attention to the following points
a) you must install those driver in the above order
b) Don't change the install location of those driver
c) Close your antivirus software to avoid unknow problem
Then, go to Settings>Developer Options>USB Debugging. Enable OEM Unlock and enable USB Debugging Mode
Now, connect your X80 Plus to the computer,
Open a Command Prompt window in "Root X80 Plus H6C3" folder (To open a Command Prompt window in any folder, hold down the shift key and right-click on the folder) and enter the following command
Code:
adb reboot bootloader
Press Enter
Wait for the device to enter fastboot mode
Code:
fastboot oem unlock
Press Enter to unlock the oem and enter the following command
Code:
fastboot flash boot boot.img
Press enter to flash the kernal, then enter the following command
Code:
fastboot reboot
This command will restart your tablet.
It is normal that tablet reboot 3 to 4 times automatically, just wait for it. (turn on the tablet yourself if the tablet do not reboot automatically)
After your device is on, check that Wifi and bluetooth works or not. (Wifi and Bluetooth may not works with the replaced kernal, just perform a factory reset)
If everything is ok, enter the following command
Code:
root.bat
Wait for the Command Prompt until it stuck at this command, "adb shell su --daemon"
Now, disconnect the tablet and reboot it manuly
After the device was booted up, Supersu already become a part of system app.
Open Supersu now, it will notify that the SU binary needs to be updated. You must need to install the binary once, but you will fail at 100%(unless there is a miracle, and your tablet is root successfully, congratulations)
Close Supersu and reconnect the tablet, enter the following command again.
Code:
root.bat
Now the command prompt should run all of the command smoothly and Supersu should have no message about the SU binary update !!
Therefore, if your Supersu shows nothing (works properly), your tablet is rooted, thats amazing.
If Supersu keep notifing, please enter the following command again and wait for it to boot up automatically until Supersu have no message about the binary update.
Code:
root.bat
Note that this root method are not stable yet
Known issues:
1) Old version of Titanium Backup was unable to execute the SU command
2) LBE are not 100% compatible with this root
Post reply if you have any requires or problem.
Stock Rom for X80 Plus just in case you need them, and the instruction will be translated later
H6C3 and H5C5
Root files: H6C3 and H5C5
Sorry for my bad english
Hi and thanks for sharing.
Is there a custom recovery to install?
I would like to install xposed framework, but don't know how to install the zip file...
Thanks
thanks and your thread on teclast's forum where the link was crash, please repair.
Thanks a lot
Can someone confim that this method works?
Jeconxis said:
thanks and your thread on teclast's forum where the link was crash, please repair.
Click to expand...
Click to collapse
You can try to flash xposed using flashify!
woody4165 said:
Hi and thanks for sharing.
Is there a custom recovery to install?
I would like to install xposed framework, but don't know how to install the zip file...
Thanks
Click to expand...
Click to collapse
Working hard on it now
hahaha1111 said:
Working hard on it now
Click to expand...
Click to collapse
looking forward to this!
Thaaanks a lot @hahaha1111 !!! I tried that on my all new H6C4 received this morning with your H6C3 files and anything is working perfectly !!! Many thanks again !!!
BTW: Any way to update SuperSU binary then?
I tried your method on my H5C6 and it worked beautifully. Thank you!
where can I use the file?
I download the file named X80 plus-win10_20160108.7z from the link. what is this, and where can I use it?
hahaha1111 said:
Working hard on it now
Click to expand...
Click to collapse
Hi @hahaha1111
any news on custom recovery?
I would like to install xposed framework, but cannot be done without custom recovery, is it correct?
Thanks
woody4165 said:
Hi @hahaha1111
any news on custom recovery?
I would like to install xposed framework, but cannot be done without custom recovery, is it correct?
Thanks
Click to expand...
Click to collapse
Hiatus
H6C4
Great! It works perfectly on H6C4.
Thanks!
Regards
RoroTiti said:
Thaaanks a lot @hahaha1111 !!! I tried that on my all new H6C4 received this morning with your H6C3 files and anything is working perfectly !!! Many thanks again !!!
BTW: Any way to update SuperSU binary then?
Click to expand...
Click to collapse
It's updated from play market with no problem.
May be it is my particular problem ( kernel 3.14.37 firmware assembly ver 3.03.20161109) but.....
WARNING TO H6C4 OWNERS! SD Card becomes unusable with this rooting files. Any SD Card after rooting recognized as 0,9 Mb size and you can't access files on it. You can't use SD Card reader too.
Please report if you do not encounter this issue.
Hi.
I'm stuck on "adb push SUfiles/Superuser.apk /data/superuser" command in root.bat
I've done all the previous steps without problems.
Before executing root.bat I have set again Usb Debug and OEM Unlock, is it correct?
Sometimes I get stuck on "adb remount"
What can I check?
Thanks
Woody
Starmobile Up Prime
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
SOME INFO:
MT6737/M (they seem to be the same thing)
Antutu Score: 30052 [source]
As of Jan 6 2018, latest official firmware is v13 06292017.
A. Root
Disclaimer: YOU ARE DOING THIS AT YOUR OWN RISK. I will not assume any responsibility for your own actions on your phone. Follow the instructions carefully, and ask questions if you're unsure.
Tested way: Magisk Manager patched boot method
Other option: SRS Root reports to root the v12 firmware, though I didn't use this method so I don't know if it works.
Magisk Manager Patched Boot Method
1. Unlock your bootloader (Note: this will factory reset your phone and you will lose all your personal data) To do this:
Enable bootloader unlock inside developer options, accessed by pressing build number 7 times in settings. Thanks @Nao Tomori !
Install adb and fastboot on a computer (Search it, it's available)
Reboot to fastboot mode (Switch off phone, press power and volume up simultaneously. Choose fastboot mode from the menu that appears)
Connect to computer by USB Cable provided
Open a command prompt or terminal and check if fastboot detects your device by typing
Code:
fastboot devices
A device number should appear. If nothing appears, it's a most likely driver problem. Click this button to know more.
Linux doesn't need drivers so try using fastboot in linux. If you really want to do it in windows, try PDANET drivers while connected in fastboot mode. No guarantees. I'm using a linux machine to specifically avoid this hassle
We're now gonna unlock your bootloader. Type
Code:
fastboot oem unlock
and confirm unlock by clicking volume up on your phone.
Reboot and go through all the necessary set-up.2. Download Magisk Manager from here and install the APK.
Make sure you download the latest apk version provided.
Note it says that Magisk itself is not yet installed.
We've only installed the helper app.
3. Flash Patched Boot Image
At this point you have two options: extract and patch your own boot image, or just use my patched boot image. I will assume you pick the second but this REQUIRES that you are on the same v13 06292017 official firmware. PM me if you want to do the first one. Download my patched boot image.
Download
Move the file to a known location that's easy to type (home directory or C Drive)
Reboot to fastboot mode, same as before
Flash with fastboot then reboot
Code:
fastboot flash boot /path/to/patched_boot.img
Code:
fastboot reboot
CONGRATS! Magisk should now be installed and along with it, Magisk's Superuser
Press thanks if it helped you! And/or leave feedback if it worked for you, and if your setup differed from mine. Thanks
MODS
B. Mods
1. Xposed Framework (systemless)
Install Xposed framework from within Magisk. Install API24.
Then reboot. This first boot takes really long. I pulled out my battery once, then the next time it successfully booted after a while.
Install topjohnwu's Xposed apk from his systemless Xposed thread.
It will tell you that Xposed is installed but not active yet.
Reboot one last time
2. Dolby Atmos (systemless)
Install from within Magisk. Confirmed working!
RECOVERY
Reserved
If you get fail operation
If you get
Code:
FAILED (remote:
Unlock operation is not allowed
)
Just go to Developer Settings > OEM Unlocking and enable it.
I used PDAnet for Windows and it worked
Nao Tomori said:
If you get
Code:
FAILED (remote:
Unlock operation is not allowed
)
Just go to Developer Settings > OEM Unlocking and enable it.
I used PDAnet for Windows and it worked
Click to expand...
Click to collapse
Oh yes, I forgot about that! Thanks. Will add and credit you
hi there bro. i just want to know, is there a custom rom that we can use for this phone? i have the same exact phone but i cannot find any articles about any other custom roms that has been used on this phone. hoping to hear from you. thanks.
And another thing, can we use TWRP for this phone?
Hello. Is there anyone here who has a clean stock rom for Starmobile UP Prime? The phone keeps popping up ads and redirecting to chrome/google play. Contact names sometimes disappear too. I ran the malwarebytes app and it said that "Settings" app is the malware. I downloaded and flashed another rom before (I forgot from what website), but same experience. Hoping for helpful response.
This is tutorial how to install XPOSED on POCO F1 MIUI global 10 and 11
This is a guide for experienced users ONLY!.
These are the steps for a phone that has already been rooted .
This is new full working Xposed method tested by me.
Download all files from the attachment and copy it to your phone.
Delete all previous old xposed modules
1. Open Magisk application on your phone
2. Go to Modules, and press +
3. Install first magisk-riru-core v18, after installation of the module press close. Then press + again and install magisk-EdXposed-SandHook-v0.4.1.2_beta-release, press close again and reboot your phone.
4. Install EdXposedInstaller_v2.2.4-release normally AND DON'T UPDATE IT. You can update modules but not installer..
5. You can do update via Magisk Manager.
Open Xposed app, and you should see this on your screen:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Another must have tool is Magisk Manager for Recovery made by VR25.
How to use MM (magisk manager) for recovery in TWRP.
1. Download file form provided link and put it on your phone memory.
2. Enter to recovery mode , go to Install and flash the file mm20190404.zip and do not reboot, just go back to main menu.
3. Go to Advanced, then open terminal
4. Write mm and pres enter
5. Pres l to get list of installed modules
6. You can disable or remove modules form here.
You must repeat all these steps every time you want to start MM
It will look like this:
If someone have trouble with SafetyNet check, just add Google play services to Black list in EdXposed.
1. Enable Black/White list in EdXp Settings
2. Add Google services to black list
3. You will pass SafeyNet Check
You can update to MIUI Global 11.0.5. Everything works fine. Just follow my update steps.
1. Open Magisk
2.Go to uninstall than choose RESTORE IMAGES
3. Reboot phone
4. Go to settings/about phone/system update
5. Download update and install it.
6. After update, go to fastboot, pwr+volume down
7. Connect your phone to PC, open cmd or power shell with admin privileges and go to platform tools folder , then type like first time fastboot flash recovery twrp-3.2.3.0-beryllium.img, then fastboot boot twrp-3.2.3.0-beryllium.img ( change the name of image file if it is different on you PC)
8. Flash Magisk again
9. Reboot
10. All should be like before update
Wrong place to post. You should move to the themes and mods section. But GJ.
Thread updated.
Sent from my POCO F1 using Tapatalk
Will this pass safetynet in magisk?
what xposed-mods do you use?
ctsuresh said:
Will this pass safetynet in magisk?
Click to expand...
Click to collapse
Edit: Safetynet is passing, so there is no issue using this xposed.
MechaNarutoSucks said:
Wrong place to post. You should move to the themes and mods section. But GJ.
Click to expand...
Click to collapse
It's a guide. Technically, it is a mod but the post shows guide and installation.
ctsuresh said:
Edit: Safetynet is passing, so there is no issue using this xposed.
Click to expand...
Click to collapse
OMG! Xposed + Safetynet? I'll try today
I'm really excited
if i use it on lineage do i need to turn off modules before OTA update to prevent bootloop or its fine ?
In order to apply OTAs, you have to open Magisk Manager go to Uninstall \Restore Images. Don't reboot or you will have Magisk uninstalled. This will restore your boot and back to 100% untouched stock images in order to pass pre-OTA block verifications.
Cara... Você salvou a minha vida... Obrigado !!
You is the best....
Working like a charm on Poco F1 running stable 10.3.4.0. Thanks!
Edit: sometimes when I turn on the phone, it go into bootloop. I need to restart manually one or more times to start correctly. I have updated to riru core and edxposed lastest versions.
Edit 2: looks like to be related to minminGuard module. After uninstall it, everything is working as expected.
Yes.You must be careful when you choose a modul. You have update for minminguard.
Sent from my POCO F1 using Tapatalk
bixirulo said:
Working like a charm on Poco F1 running stable 10.3.4.0. Thanks!
Edit: sometimes when I turn on the phone, it go into bootloop. I need to restart manually one or more times to start correctly. I have updated to riru core and edxposed lastest versions.
Edit 2: looks like to be related to minminGuard module. After uninstall it, everything is working as expected.
Click to expand...
Click to collapse
I tested new 2.0.9 version and everything works good. No bootloop. But i found that minminGuatd is not very effective in removing ads. I recomand that you use lucky patcher instead. Inapp purchase option.
But something is buggy with this modul...avoid it.
Sent from my POCO F1 using Tapatalk
@delevic Have you tried "customiuizer" module? Also stuck at boot screen randomly...
Which edxposed version you use ?
Just tested customiuizer. No bootloops no bugs. Write me all your installed versions from magisk riru edxposed ...
Sent from my POCO F1 using Tapatalk
Thanks for sharing.i am use 9.3.21 eu beta weekly and working well.no bootloop everything is okey now
I am testing now magisk-EdXposed-SandHook-v0.4.2.3_alpha-release.zip So far so good
4. Install EdXposedInstaller_v2.2.4-release normally.
Click to expand...
Click to collapse
what is meant by "normally"?
Just install apk fille like all other app. Find apk fille and press enter
Sent from my POCO F1 using Tapatalk
Morning all... after spending almost a whole day to solve a very annoying issue to my Cubot Quest smartphone I decided to write here a short procedure hoping to save headaches in future
When flashing from SP_Flash_Tool can happen that after formatting all partitions and installing/upgrading a new firmware both IMEI are lost and when you reboot the device you have a very annoying red watermark that sounds: not verify
so the only way to get rid off that red line/watermark is to reflash imei + correspondant google key
ATTENTION: this method works and was tested only for Cubot Quest
so let's hope to save someone from future headache:
0. turn off device and do NOT plug
1. download (and unzip) latest stock firmware/rom from cubot website: https://www.cubot.net/platform/Support/detail/id/129/cid/16.html
2. download (and unzip) latest SN Write Tool: https://androidmtk.com/download-sn-write-tool (look at the bottom of the page)
3. launch SN_Writer.exe (from SN Write Tool decompressed folder)
4. go to "Key Files" in the program menu >> Attestation Key >> Attestation Key & browse in the decompressed ROM folder looking for file: a798_cq_8123c_62_p0_0_100000_S1220.bin >> OK
5. go to "system config" , ensure that on left is checked just "IMEI" and at the bottom "Dual IMEI" (do NOT check other options)
6. at the bottom in Database section check "Load Modem DB from DUT"
7. always at the bottom in AP_DB look for file in the ROM folder: APDB_MT6765_S01__W1925 (pay attention do NOT choose APDB_MT6765_S01__W1925_ENUM)
8. save
9. click Start & give correct/correspondant IMEI1 and IMEI2 (they are printed in the device's box, but if you have lost the box I think could work also a fake imei)
10. plug the device and flashing will start in few seconds, wait and if all goes as should be a green pass warning should appear in the program
11. turn on the device and the red watermark should be vanished
anyway with correspondant/correct files the same procedure should work for almost all Cubot devices with the same issue, both files (point 4 & 7) are in the rom folder
ps: do not "play" with SN Write Tool... you can brick the device
Regards,
Davide
suiller said:
Morning all... after spending almost a whole day to solve a very annoying issue to my Cubot Quest smartphone I decided to write here a short procedure hoping to save headaches in future
When flashing from SP_Flash_Tool can happen that after formatting all partitions and installing/upgrading a new firmware both IMEI are lost and when you reboot the device you have a very annoying red watermark that sounds: not verify
so the only way to get rid off that red line/watermark is to reflash imei + correspondant google key
ATTENTION: this method works and was tested only for Cubot Quest
so let's hope to save someone from future headache:
0. turn off device and do NOT plug
1. download (and unzip) latest stock firmware/rom from cubot website: https://www.cubot.net/platform/Support/detail/id/129/cid/16.html
2. download (and unzip) latest SN Write Tool: https://androidmtk.com/download-sn-write-tool (look at the bottom of the page)
3. launch SN_Writer.exe (from SN Write Tool decompressed folder)
4. go to "Key Files" in the program menu >> Attestation Key >> Attestation Key & browse in the decompressed ROM folder looking for file: a798_cq_8123c_62_p0_0_100000_S1220.bin >> OK
5. go to "system config" , ensure that on left is checked just "IMEI" and at the bottom "Dual IMEI" (do NOT check other options)
6. at the bottom in Database section check "Load Modem DB from DUT"
7. always at the bottom in AP_DB look for file in the ROM folder: APDB_MT6765_S01__W1925 (pay attention do NOT choose APDB_MT6765_S01__W1925_ENUM)
8. save
9. click Start & give correct/correspondant IMEI1 and IMEI2 (they are printed in the device's box, but if you have lost the box I think could work also a fake imei)
10. plug the device and flashing will start in few seconds, wait and if all goes as should be a green pass warning should appear in the program
11. turn on the device and the red watermark should be vanished
anyway with correspondant/correct files the same procedure should work for almost all Cubot devices with the same issue, both files (point 4 & 7) are in the rom folder
ps: do not "play" with SN Write Tool... you can brick the device
Regards,
Davide
Click to expand...
Click to collapse
Hello,
I have the not write Googlekey/not write TEE watermark on top of the screen, the device is a Blackview Max 1. It happened after unbricking it , flashed the stock rom with flashtool.
What's the bin file I should look for?
I saw a method replacing systemui apk in priv-app folder but it corrupts my system ui, no nav bar and no top pulldown notification bar. So I don't know what to do, I have even rooted it patching the boot file.
Let me know for more advice, I will try your posted method. Thanks
Morphine1 said:
What's the bin file I should look for?
Click to expand...
Click to collapse
honestly I dunno...
but you don't have many .bin files and the dimension isn't big... about 10k, should be easy to identify it
Hey,
Thanks for the help, I have a Cubot QUEST too, I followed your steps and recovered my IMEI from the box however i still have the red NOT VERIFY text, the IMEI is recovered so im not sure what is left to do.
Any suggestion?
tragidyx said:
Hey,
Thanks for the help, I have a Cubot QUEST too, I followed your steps and recovered my IMEI from the box however i still have the red NOT VERIFY text, the IMEI is recovered so im not sure what is left to do.
Any suggestion?
Click to expand...
Click to collapse
What's your Serial Number like?
Morphine1 said:
What's your Serial Number like?
Click to expand...
Click to collapse
It's messed up like Abcde1234
same here still have the watermark cubot quest
im joining you with my dogee s88 pro
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Hi!
It works for the Ulefone Armor X6.
Although I had to flash the Stock-ROM V1 before I succeeded.
After that I managed to get rid of the message.
This method helped me. I can recommend for everyone, if you have root accces of course.
Sadly, what you described here are not worked for me, because every time when I did that, it failed. But it's a good try.
Here's another possible fix if you have magisk with zygisk support! It has to do with dynamically turning the ro.mtk_tee_check_support build prop to 0. More here https://forum.xda-developers.com/t/not-verify.3870242/post-87713751.
Same like my doogee android, after flash, i just want red mark on top screen gone, but i like dont have imei because this phone from another country if i have imei this phone not work