Database Info

[GUIDE][ROOT] O+ 8.31z MT6572

This thread shall strive to be an all-in-one thread for the phone O+ 8.31z. And to be noob friendly as well. As of now, I have only very limited knowledge so I'll be adding stuff as I go.
Phone Specs:
CPU: MT6572 1GHz Dual-Core
Architecture: ARM Cortex-A7
Clock Speed: 598 MHz - 1.00 GHz-----
GPU Vendor: ARM
GPU Renderer: Mali-400 MP
UBIFS File system
Android: 4.2.2
Kernel Architecture: armv7I
Default Governor: Hotplug
Screen Res: 320x480
Density: 160dpi
RAM: 219MB
Internal Storage: 0.16GB
Sensors: Proximity, Light, 3-axis.
Click to expand...
Click to collapse
For drivers, connect your phone to windows PC, download PDANET (search for it on google) and let it install drivers for your phone.
Preface: TOOLS and THREADS TO BE USED
1. MTK Droid Root and Tools by xda senior member rua1. Press thanks in his thread! Compatible with Windows and Linux(with wine).
2. SP Flash Tool Credits to Khonshu of china.phonearena. I downloaded v3.1344. Here's an xda thread on what you can do with it: Click Me! Troubleshooting SP flash tools: .Click here!
3. Pdanet for Windows drivers
Chapter 1.0.0: HOW TO ENABLE PHONE MODES
Steps:
1.1.0 For MTP mode
1.2.0 For ADB mode
1. Go to Settings>About Phone
2. Click Build number about 6 times, quickly. Developer Options should now appear.
3. Go back to settings then click Developer Options. Here you find so many things you thought didnt exist
4. For now, we only check USB debugging. When a pop-up appears, just click "ok". Done!
1.3.0How to enter recovery mode: (Credits to phcorner.com O+8.52 thread)
Method 1:
1. Remove battery and reinsert.
2. Press Volume Up and power key simultaneously.
3. A blank screen with an android lying down and a red exclamation triangle should appear now.
4. Press Power button once, and the menu will appear.
5. To navigate, Power: Show/Hide options. Vol UP: Confirm. Vol Down: Scroll.
6. When done, reboot system to exit.
Method 2: When you're on a PC,
1. Connect Phone in USB debugging mode.
2. Open cmd (or terminal then change directory to your adb folder) and
Code:
adb reboot recovery
1.4.0 For Phone test mode
1. Press Volume Down and Power simultaneously.
2. Choose among the options.
3. When done, remove battery to exit.
(It seems like reinserting the battery and doing VolDown+Home combo does not do anything else)
1.5.0 For fastboot (aka bootloader) mode
Requirements: Since you want to use fastboot, then you must be on an adb configured computer
1. Open cmd (or terminal then change directory to your adb folder)
2.
Code:
adb reboot bootloader
3. Wait for the phone. Done!
Chapter 2.0.0: ROOTING
Why root?
There are many methods to rooting. I will list what I know might work. I'm 99.9% sure the first one works (given you are not stuck in a bootloop.)
2.1.0 Shuame ROOT GeniusDownload​Info: This is a one-click PC application. I have used this in Windows 7 32-bit and in lubuntu 13.10 and it works. If your phone is not an MT6572 I'd still recommend that you try this as it can root almost anything! It installs Kinguser as the superuser app.
2.1.1 Requirements for Windows PC: A Windows PC, a USB cable, your phone, and a fully downloaded shuame root genius. No drivers needed as shuame root genius already installs them for you.
2.1.2 Requirements For Linux PC users: A linux PC, a USB cable, your phone, a fully downloaded shuame root genius, WINE, and adb (I might be wrong here, but get this: Since drivers are not really used, we need our phone to be given adb permissions by linux, or else shuame will not be able to recognize your phone. So you will probably need to have adb installed first, just to be sure.)
For info on how to do that, check here: Click Me!
Also, shuame root genius does not display well under wine in my case, but the buttons were clickable anyway so it still works. From here, it's pretty much the same procedures.
2.1.3 Steps:
I made a visual guide here:
​
And in text, here:
1. Connect your phone to PC using the USB cable and go to MTP mode. See Chapter 1.1.0 for help
4. Enable USB debugging. See Chapter 1.2.0 for help.
5. Open Shuame Root Genius. It will connect to your phone automatically and install drivers for about 3-5 minutes. (No more driver installation on linux PCs)
6. Click "Root it". You should now see your device as rooted. And if you click back, you can unroot. Done!​
2.2.0ErootDownload/help thread​Info: Another tool by Chinese developers. I tried it on my lubuntu 13.10 WINE and it worked flawlessly! I'm pretty sure it'll work on a Windows PC as well. It installs superuser by clockworkmod.
2.2.1 Requirements: See 2.1.1 and 2.1.2.
2.2.2 Steps:
Visual guide
Textual guide here:
1. Connect your phone to PC using the USB cable and go to MTP mode. See Chapter 1.1.0 for help
4. Enable USB debugging. See Chapter 1.2.0 for help.
5. Open eroot. It will connect to your phone automatically.
6. Click the root button. It's the only button anyway. When you have rooted successfully, you can click the 解除 button to unroot if you wish. Done!​
2.3.0 MTK Droid root and tools
Connect Phone in ADB and MTP mode.Download/Help thread can be found in Preface​Run MTK Droid Tools. Wait for it to recognize and establish a connection with your phone. This should appear after a minute:
Take note that a blue rectangle on the lower left means you're still not rooted. Press ROOT.
Wait for about three to five minutes. In my case, MTK Droid tools crashed So I didn't see a superuser app.
But I downloaded root checker and sure enough, my phone was rooted. Only the superuser app was missing.
I also opened MTK Droid tools again and saw a green rectangle (which means I am rooted :victory: )
So now, technically, you are rooted. But we still need a superuser app, so I downloaded a superuser app that I liked and updated the binary. I downloaded SuperSU by chainfire from the play store. Done!
or, you could try the superuser button in the root, backup, recovery tab. I didn't try it though
2.4.0 Other stuff you might wanna try or know about if none of these methods worked for you, here: http://forum.xda-developers.com/showthread.php?t=2523814

Chapter 3.0.0: RECOVERY STUFF
3.2.0 How to backup stock recovery
3.3.0 What is clockworkmod recovery?
3.4.0 What is carliv touch recovery?
UPDATE: I think O+ 8.31z was primarily sold for the Philippine Market; as such, I may be in competition with more Philippine based forums such as symbianize and gsmworldfive. Therefore, I think it would be best that I leave the two 8.31z links here and discontinue any plans on improving this thread. Here they are:
http://www.symbianize.com/showthread.php?t=1094034&page=10
^this link contains a SPFT flashable pre-rooted clean stock rom.
http://www.gsmworldfive.com/forum/showthread.php?t=37787
^this link uses the SPFT method too, but the rom here has much more root apps installed already, like swapper, greenify, auto ram cleaner etc. (Oh, stock keyboard was also taken out).
Both confirmed working to bring back a bootlooped 8.31z. I prefer the first one though
Until next time! My dad plans to sell this phone soon so I guess I won't be learning how to make custom roms anytime soon yet... Hope you guys are doing well
Click to expand...
Click to collapse
UPDATE: Since my dad hasn't sold it yet, I'm playing with it again. There is a Filipino facebook group that is dedicated for 8.31z users. I think they have custom roms ported there.
Click to expand...
Click to collapse
Chapter 4.0.0: ADD INIT.D SUPPORT TO STOCK ROM
Check here! http://forum.xda-developers.com/showthread.php?t=1933849
I haven't personally tried any one yet. You are always proceeding at your own risk

Tweak for speed, battery life, and other cool/useful stuff.
Chapter 5.0.0: Speed
There are tons of stuff to speed up your phone, and they're not just limited to one specific phone. So bring in the list.
1. Use Greenify (find it in the play store)
Requirements: Root (optional for auto-hibernation. Highly Recommended.), Android 4.0+
You may greenify stuff like Guardian if you are not using it, or maybe the FB app too. Saves some battery and gives a little free ram for better multitasking.
2. Disable fancy window animations and transitions
Go to settings>developer options and disable the three animation options to animation off.
3. Use a cpu controller like No Frills CPU control (find it in the play store)
Controls how fast or slow you want your CPU to go. Default Governor is hotplug.
For a faster phone, set the governor to performance. It sets the CPU to scale to the max that you set. Use when you are playing heavy games.
For a battery saving phone, set the governor to powersave. It sets the CPU to scale to the min that you set. Use when you only plan to use really light apps.
For a balance between performance and battery save, it's probably best to go back to hotplug since it can turn the second core on or off depending on your usage.
4. Tweaks and Scripts
Info: Tweaks refers to build.prop tweaks. Scripts refer to init.d scripts. So this is a two-part thing. Adding build.prop tweaks, and running init.d scripts. Some do this two-part thing simultaneously in one flasher. Others, separate the tweak part from the script part. The reason they do this is because phones running from stock usually do not support init.d scripts, but only build.prop tweaks.
Our 8.31z cannot support init.d (yet) so for now we will only do the tweak part.
1. Tweak part of [ SCRIPT | TWEAK ] ◢ Project Fluid™ ◣ by Spex. [size="+1"]Recommended.[/size]
Please press thanks in his thread! This is not my work.
Project Fluid has a separable tweak part. I didn't apply all as some are optional. So I just applied it and what happened?
Using Antutu X Benchmark
Before Project Fluid Tweak: 7334
After Project Fluid Tweak: [size="+1"]9264!!![/size]​I only selected some of the tweaks (i.e. I didn't use "unlock with volume rocker and other stuff like that) Here's what I added to my build.prop. Feel free to do the same.View attachment 2785183
How to:
1. Open ES explorer (I'm using latest version)
2. Copy the tweaks that you want to add to build prop. Find the tweaks in spex's post or copy my selected tweaks. And thank spex in his thread.
3. Press the menu button on your phone. Click tools. Click on for root explorer and grant root permissions.
4. Click root explorer. Click Mount R/W. Choose R/W for /system and click ok.
5. Navigate to /system and open build.prop with ES note editor. Press the menu button on your phone and click edit.
6. Now paste the tweaks into the build.prop file. Or type them manually
7. Reboot and enjoy!
2. Tweak of Dash-M Script and tweak by myaservip
Please press thanks in his thread! This is not my work.
Dash-M has a tweak part and a script part too. If you want to try Dash-M Tweak, go to his myaservip's thread and download the zip, transfer to the root of your sdcard, go to recovery mode, and flash from there.But personally, Project Fluid's tweaks are more complete. I haven't tried Dash-M script since we haven't added init.d so stay tuned.​3. Script and Tweak of ★ [MOD] ◢ PurePerformances™X ◣ | Golden Edition | Scary performances on Android by Jeeko
Please press thanks in his thread! This is not my work.
This is a single inseparable script and tweak in one so we cannot use it yet. Stay tuned.​[size="+1"]General reminder: Tweaks and scripts are usually not mix-able. So remove one before trying another.[/size]
Chapter 6.0.0: Cool/Useful Stuff
1. Xposed Framework and Modules.
Our device can definitely benefit from Xposed modules! 4.2 is capable of running these.
2. TouchPal Keyboard
A good replacement to stock keyboard. Contains different keyboard layouts and support for tons of languages! And if you have experienced the keyboard not pressing the right button, this might be a better replacement.
3. Moreto come.

Hi there fellow Filipino! Please continue what you're doing. I can help you in some way in installing CWM-esque recovery tool for our phone. As it is a UBIFS-type system, many have said that it's a tricky job. A lot have failed but some did it successfully like me. I followed this tutorial from here
chinaphonearena.com/forum/Thread-CWM-For-All-MTK-Easy-Magic-CWM-MT6575-MT6515-MT6577-MT6517-MT6589-MT6582-MT6592
Sorry I can't post links yet because this is a new account.
So I was able to boot into recovery, but I stopped there until someone successfully restore our phone from a backup (even if it's just stock ROM)
Cheers! You should try it!
PS. I tried your build.prop and benchmarked afterwards, only to get about 7100+. HOW DID YOU GET TO 9K?! Please indicate if you have a lot of apps and is greenify and that cpu tool the only apps you're using for speed?
After sometime though, my phone got slow, so I deleted the added lines in build.prop and speed went back on. What's happening?

Successfully enabled init.d! I used term-init. It was so easy! Just a matter of minutes. Now, to try some scripts...
Edit: Currently backing up using Carliv Touch Recovery, the MTK compatible CWM recovery tool, before going further. Will try restoring it later. If it is a success, then Chapter 3 is done!

zildjosh97 said:
Successfully enabled init.d! I used term-init. It was so easy! Just a matter of minutes. Now, to try some scripts...
Edit: Currently backing up using Carliv Touch Recovery, the MTK compatible CWM recovery tool, before going further. Will try restoring it later. If it is a success, then Chapter 3 is done!
Click to expand...
Click to collapse
Hi! I've been a little busy lately haha. I'll get back to updating this thread in a week or so
Are you new to this stuff? Or have you had previous experience before? Seems like you're going pretty well! I don't know much about this phone of ours yet, maybe you know more than I do
Update: So my O+ phone wasn't sold, and now I plan to use it. Just tested Carliv 2.4 using Yuweng's Auto Magic Installer, and it installed! Restore doesn't work though. And don't advance restore > restore system. You'll get a bootloop haha.

HELP
What is the best CWM or TWRP on my o+8.31z, newbie here. and How? any Help. Thank you for rooting process. as well.

Sory
Sorry if I'm wrong forum, I just want to ask, is there any one can help me to do the rooting of the device Himax H TWO with the following specifications
CPU: MT6735 OCTACORE @ 1.3GHz
GPU: Mali-T720 MP3
Screen : 5.0 inc 720 x 1280 pixels (~294 ppi pixel density)
Android : Marshmellow with lewa os
Karne : 3.18.19
Ram : 2GB
Internal memory : 16GB
I HOPE there that will help me to do the roots and modify twrp for this device
Thankyou fery much

nothing working for MT6572 device (not that O+) for root.. tried all one click or simple root methods nothing working
MTK Droid root and tools waiting for hours and hours and nothing happens it just wont root my mobile idk what to do

P6000 General Thread - Bug fixes, FAQ, general info.

Elephone P6000
Phone reviews by @s7yler
Stock ROM (SPFlash):
from elephone servers
from needrom.com
Custom Recovery --- Touch RecoveryCourtesy of @bigrammy, @carliv and @Santhosh M​Various
Latin Paradise(拉丁乐园)(Elephone) on Baidu
P6000 Folder
OTA Updates - direct from elephone
--- both are 404 now ---
12282014 to 31012015
01092015 to 31012015
Other threads and useful sites:
http://forum.xda-developers.com/android/general/elephone-p6000-mtk6732-64-bit-4g-5-2g-t2957425
SP Flash Thread - P6000
4pda thread - translated top post is fairly concise
Check your Mobile Network/Carrier
Please use the other threads/Q&A and the thanks button - to minimise duplicate posts reporting the same issues.
I'd like this thread to be used mainly for bug fixes, tips and tricks. If someone reports a similar problem/fix/bug click the thanks button if you'd like to agree.

Bugs
Android 5.0 'Official' Release
Update Official (V3.3)
Some modifications: #186
Android 5.0 Beta
12-02-15 ROM available on needrom.com
Hardware buttons don't work
Battery doesn't draw charge
Ril related memory leak
No ADB​
Android 4.4.4 (V8.4)
Notification light - not breathing when charging
OTG only works with self-powered devices
Battery seems to jump from 100% to ~90% Soon after removing from charger
Screen jumps several pixels (30) on slow scrolling. ​Android 4.4.4 (V8.3) bugs not present in V8.4Data encryption results in a stalled boot/softbrick​
FAQ/Fixes
1. Notification light is not working in V8.4 as it was in V8.3
Try Light Manager from the play store or gravity box (xposed module)
2. Does OTG work?
It seems to work only with a powered USB hub - I've only been able to check a powered external hard-drive which wouldn't connect
3. How do you fix the screen jump issue?
There are several options here:
From @the1024 / zOrgent we have two options 1. Using a chinese tool - and 2. Using a .bat
From elephone we have TpUpgrade.apk (appears to only work with V8.4)
From lidmiloff we have P6000 Bugfixer.apk​
4. How do you restore a Stock ROM?
Download a SPFlash ROM from #1; you will need to install MediaTek USB VCOM drivers (if they aren't automatically installed); On the download page select the scatter from the ROM folder; and the page should populate with the various .img's and .bins; if it doesn't then double click on the entry and locate it manually (also useful if you wan to change boot/recovery with SPFlash). Hit download; remove the battery from the phone and connect it to the PC (you can connect the battery again). The connection will be fairly instantaneous (there may be a driver install the first time it's connected); if it doesn't connect then unplug/replug.
More details from @bigrammy found here
5. Battery jump from 100% to 90%.
Haven't really noticed this too much - download an app like Battery Monitor Widget, add widget (Battery monitor widget gauge => Content => Central value => Battery => Battery Current (mA)) which will show you the battery drain/draw and charge until the draw is close to; if not +0mA
6. Is there any touch recovery?
As of now (pre-5.0) there is no touch recovery. The recovery thread on #1 contains various recoveries - most of which boot but none have touch - this seems to be a kernel issue.
Touch recoveries can be found here. These are built for KK.
7. What about Custom ROMs?
Potential Port devices (MT6732/MT6752) and their ROMS
As there are no official sources released; for MT6732 or P6000 then custom ROMs are a no-go for now. Porting ROMs from other devices running on MT6732 (and MT6752); i.e. Ulefone Be Pro for example is theoretically possible but there doesn't appear to be any custom ROMs on these chips that offer anything different than the stock/AOSP(almost) that we have already. As other devices get released possibly running MIUI or ColorOS then Custom ROMs may be possible.
FlymeOS
8. How do you take a screenshot?
Natively pressing Volume down and power together for 1 second will take a screenshot - it may take a while to get used to - if volume mixer appears then they were too slow and need to wait for it to disappear. Over adb/terminal you can make use of screencap and screen record
9. How do you back up EVERYTHING(except preloader)?
In SPFlash Tools => readback from 0x00 to 0x3a3e000000
This is a fairly quick way to make sure you have a copy of all the partitions on the device; it will create a 14GB+ file containing all the partitions. You will need to break this block up (manually for the moment) into it's constituent parts if you want to use it to restore - using a Hex-editor (HxD for example) and a copy of the matching /proc/partinfo file and/or scatter.txt
The essential partitions to backup for a fully running device are - boot, (recovery), system, (cache) and data which can all be backed up using a custom recovery. The one other partition needed is nvram - this can be backed up with SPFlash (look at /proc/partinfo) or with dd commands. The nvram partition will only be needed to be restored if you Format All with SPFlash. If you don't have a backup you can restore/recreate the IMEI files that it contains.
10. How do you backup/restore IMEI?
Several options here:
1. MTKDroid
2. Backup NVFLASH partition via readback in SPFlash Tools (look at the scatter.txt) to restore you need to modify the scatter.txt to give the nvflash a file_name: and change it from is_Download: false to is_Download: true
3. From elephone there's a IMEI coding tool
4. Keep a copy of the /data/nvram folder
5. Create new imei files to add to nvram folder/partition with imei.exe
6. Chamelephon app from the play store
7. MTK Engineering Mode
11. Adb access with 5.0 Beta ROMs
1. Use KingoRoot
2. Add the Mediatek subsystem id (0x0e8d) to adb_usb.ini
12. Any Stock Camera fixes?
For KK-4.4.4 from @z0rgent at 4pda

FAQ/Fixes Continued
Android 5.0 V1; V1.1; V2.2 (V3.2); V3.3 #125 #186These versions seem to have gapps preinstalled and are prerooted - for everything else have a look at the 5.0 Betas section below
5.0 Modifications #186​Android 5.0 Beta1 Beta2 Beta3
To gain adb access
Linux/Windows - need to add the Mediatek subsystem id (0x0e8d) to adb_usb.ini
Linux: ~/.android/adb_usb.ini
Windows: C:/Users/${Username}/.android/adb_usb.ini​KingoRoot It won't root the device however - I believe this is due to it installing a 32bit su binary rather than a 64bit one.
Root
For root install SuperSU v2.11+
Confirmation
Custom Recovery
Recovery from @carliv - from #1; modded to boot on L (basically just the cmdline changed / initrd.gz from stock L recovery replaced with carliv's built CWM).
Carliv Port by hanuma50 on 4pda (hopefully all his work and not partially stolen to take credit)
This recovery seems to only work when the Lollipop Beta ROM is installed.
Gapps
64-bit gapps made for the Nexus 9.
My phone seems to be running a little hot after installing the gapps - but that might just all the cores kicking in.
Mirrored copy of the version I'm using.
(OP's thread has updated them and removed the previous version)
Busybox
64-bit busybox installation
Removing encrypted data (temporarily)
In recovery while in an adb shell: /sbin/make_ext4fs /dev/block/mmcblk0p19
This will allow you to restore backed up data - but it will get re-encrypted on first boot, I'll take a look at removing encryption when I get the chance - should be either secro partition or something in the boot.img​
Android 5.0 Beta Breakdown
Screenshots to come later.
Entering LKVOL UP and POWER (this no longer enters recovery)
From lk menu: entering fastboot mode and normal boot works.
Entering recovery (stock) doesn't work and I can't tell if the other normal boot options do anything different​Charging batteryFlashing a custom recovery should allow you some way to charge the battery​I haven't yet been able to install/boot any recovery. Flashing lk and boot from 4.4.4 (I took them from the 48MB OTA) seems to let you charge when powered off. Confirmed​RIL Memory leakThere seems to be a RIL/Sim related memory leak leading to random reboots - for testing purposes disable the sim card(s) or enter airplane mode
I could be wrong about the RIL and the ROM just needed time to settle; all I can say is I had reboots until I switched to airplane mode​IMEIIMEI was lost but that would be due to formatted flash memory (wiped nvflash partition) - it's a good idea to keep a backup regardless.​Antutu Scores64-bit Antutu Scores are around 28000
32-bit Scores are around 27000
Data-encrypted 4.4.4 Antutu scores are also around 28000​SensorsBacklight, sound ... can't be changed
Brightness can be fixed in MTK Engineering Mode #5​ROM is not rooted; does not have gapps installed and data is encrypted.
TL;DR The issues with the 5.0 Beta ROM, are primarily not ROM related but kernel related, they have bumped the kernel version up to 3.10.61+, and the issues that need correcting are the various kernel modules (power,sensors).
Android L kernel config

Annotated /system/build.prop
Stripped top of build.prop (build properties) due to size
# begin mediatek build properties
ro.mediatek.version.release=ALPS.KK2.MP13.V1.27
ro.mediatek.platform=MT6752
ro.mediatek.chip_ver=S01
ro.mediatek.version.branch=KK2.MP13
ro.mediatek.version.sdk=3
# end mediatek build properties
#
# from out/target/product/k01q_e/obj/CUSTGEN/config/system.prop
#
#
# system.prop for generic sdk
#
rild.libpath=/system/lib/mtk-ril.so
rild.libargs=-d /dev/ttyC0
# MTK, Infinity, 20090720 {
wifi.interface=wlan0
# MTK, Infinity, 20090720 }
# MTK, mtk03034, 20101210 {
ro.mediatek.wlan.wsc=1
# MTK, mtk03034 20101210}
# MTK, mtk03034, 20110318 {
ro.mediatek.wlan.p2p=1
# MTK, mtk03034 20110318}
# MTK, mtk03034, 20101213 {
mediatek.wlan.ctia=0
# MTK, mtk03034 20101213}
#
wifi.tethering.interface=ap0
#
ro.opengles.version=196608
wifi.direct.interface=p2p0
# dalvik.vm.heapgrowthlimit=256m
# dalvik.vm.heapsize=512m
# USB MTP WHQL
ro.sys.usb.mtp.whql.enable=0
# Power off opt in IPO
sys.ipo.pwrdncap=2
# Switching Menu of Mass storage and MTP
ro.sys.usb.storage.type=mtp #### adding ,massstorage to this gives an additional USB option but it apears to still mount as a media device (MTP) adding ,mass_storage will let you mount the microsd card
# USB BICR function
ro.sys.usb.bicr=no #### changing to yes will allow you to mount /system/mobile_toolkit/iAmCdRom.iso to PC via USB ####
# USB Charge only function
ro.sys.usb.charging.only=yes
# audio
ro.camera.sound.forced=0
ro.audio.silent=0
ro.zygote.preload.enable=0
#
# ADDITIONAL_BUILD_PROPERTIES
#
persist.gemini.sim_num=2
ro.gemini.smart_sim_switch=false
ro.gemini.smart_3g_switch=0
ro.gemini.sim_switch_policy=1
ril.specific.sm_cause=0
bgw.current3gband=0
ril.external.md=0
ro.btstack=blueangel
ro.sf.hwrotation=0
ril.current.share_modem=2
curlockscreen=1
ro.mediatek.gemini_support=true
persist.radio.fd.counter=15
persist.radio.fd.off.counter=5
persist.radio.fd.r8.counter=15
persist.radio.fd.off.r8.counter=5
persist.radio.fd.on.only.r8.network=0
drm.service.enabled=true
fmradio.driver.enable=1
ril.first.md=1
ril.flightmode.poweroffMD=1
ril.telephony.mode=0
dalvik.vm.mtk-stack-trace-file=/data/anr/mtk_traces.txt
persist.mtk.anr.mechanism=1
mediatek.wlan.chip=CONSYS_MT6752
mediatek.wlan.module.postfix=_consys_mt6752
ril.radiooff.poweroffMD=0
ro.config.notification_sound=Proxima.ogg
ro.config.alarm_alert=Alarm_Classic.ogg
ro.config.ringtone=Backroad.ogg
persist.mtk.wcn.combo.chipid=-1
ter.service.enable=0
mediatek.extmd.usbport=0
ro.lte.dc.support=0
ril.active.md=0
ro.setupwizard.mode=OPTIONAL
ro.com.google.gmsversion=4.4.4
ro.com.google.clientidbase=alps-k01q_e-{country}
ro.com.google.clientidbase.ms=alps-k01q_e-{country}
ro.com.google.clientidbase.yt=alps-k01q_e-{country}
ro.com.google.clientidbase.am=alps-k01q_e-{country}
ro.com.google.clientidbase.gmm=alps-k01q_e-{country}
wfd.dummy.enable=1
persist.sys.dalvik.vm.lib=libdvm.so #### Charnging this to libart.so appears to have no effect ####
net.bt.name=Android
dalvik.vm.stack-trace-file=/data/anr/traces.txt
# begin fota properties
ro.fota.platform=MTK6732_KK
ro.fota.type=phone
ro.fota.oem=new-bund6732_KK
ro.fota.device=k01q_e
ro.fota.version=eng.jenkins.1422677980
# end fota properties
ro.sf.lcd_density=190
#### Stock value I believe is 320; changing to >190 switches the device to phablet mode; this spoofs the screen size to be 7.73 inches (CPU-Z) enabling tablet apps in the apps store after clearing play store app data ####
qemu.hw.mainkeys=0
#### This enables softkeys ####
Annotated /custom/customprop/custom.prop
ro.product.model=Elephone P6000
ro.product.name=Elephone P6000
ro.product.brand=elephone
ro.product.manufacturer=elephone
ro.bt.name=P6000
ro.wifi.name=P6000
ro.notification.breath=yes #### This seems to not be working with V8.4 ####
ro.build.display.id=ALPS.KK2.MP13.V1.27
ro.internal.build.version=K01Q-E.ELEPHONE.vR83.E4.150109
ro.custom.build.version=Elephone_P6000_V8.4_20150109
ro.fota.device=Elephone_P6000
ro.fota.version=Elephone_P6000_V8.4_20150109202612

MTK Engineering Mode
*#*#3646633#*#* (*#*#ENGMODE#*#*)
What can be done in engineering mode
General non-specific guide
Backlight
Hardware ===> LCM ===> LCM Cycle ===> add a value between 5 and 55 ===> Hit Set.
(On L at least this value will jump to value in the millions/billions; unsure if this has any implications)
Audio
http://forum.xda-developers.com/showthread.php?t=2746861
http://forum.xda-developers.com/showthread.php?t=2248396
GPS
http://www.cnx-software.com/2013/11...ps-lock-on-mediatek-mt65xx-based-smartphones/
Orientation / GSensor
Hardware Testing ===> Sensor ===> Sensor Calibration ===> GSensor Calibration ===> Do Calibration (20% tolerance)
IMEI Restore
Command should be AT +...
Xposed Installer (or WSM Tools)
I've had no problems with any xposed modules.
You will get a warning regarding AliyunOS -
this issue is reported due to the presence of /system/framework/*.jar.jex files.
You can ignore/move/remove these *.jar.jex files without it causing any (noticable) issue.
I haven't decompiled any apps so I don't know if. jex files are used elsewhere within the ROM (in place of .jar),
so can't comment on whether the stock ROM is indeed an Aliyun OS.
I would advise backing them up so that any future OTA can complete 100%.
Any issues identified with xposed modules will be reported here.​

Very Helpful and concise
Nice one bro :good:
Subscribed

Ludmiloff's Screen fix apk version 1.2 final now works with 8.3 also. Just wanted to give you a quick update so you edit your post HypoTurtle

greekfragma said:
Ludmiloff's Screen fix apk version 1.2 final now works with 8.3 also. Just wanted to give you a quick update so you edit your post HypoTurtle
Click to expand...
Click to collapse
Still doesn't work for me on 8.3.

Nice one, i get my phone in a couple of weeks.

Hello
and Thanks for all your work ! :victory:
Can you add how save and restore imei ?

xenonism said:
Still doesn't work for me on 8.3.
Click to expand...
Click to collapse
Sorry to hear that man. Can you give more details? Are the driver version letters shown normal or "?"

greekfragma said:
Sorry to hear that man. Can you give more details? Are the driver version letters shown normal or "?"
Click to expand...
Click to collapse
Well, I tried the first methods which came out and they wouldn't work. Then I upgraded to V8.4, at the same time the Elephone APK came out, so I used it and it set the thresholds to 3 and 4. Then I decided to go back to V8.3 and since then, no method managed to make a persistent change to the values (I tried ludmiloff's works, Elephone's APK modified by me, which worked for others, and the old Russian method). At best, I get the new vaules in the "init config" portion of the configuration, never in the "real config" portion, and they are always gone after a reboot. File permissions of /proc/gt9xx_config are 660, owned by root. The config version letter is currently F and ludmiloff's app reads it correctly.
I guess that's all the info I can share.

xenonism said:
Well, I tried the first methods which came out and they wouldn't work. Then I upgraded to V8.4, at the same time the Elephone APK came out, so I used it and it set the thresholds to 3 and 4. Then I decided to go back to V8.3 and since then, no method managed to make a persistent change to the values (I tried ludmiloff's works, Elephone's APK modified by me, which worked for others, and the old Russian method). At best, I get the new vaules in the "init config" portion of the configuration, never in the "real config" portion, and they are always gone after a reboot. File permissions of /proc/gt9xx_config are 660, owned by root. The config version letter is currently F and ludmiloff's app reads it correctly.
I guess that's all the info I can share.
Click to expand...
Click to collapse
Well, time to get in here, I guess...
@xenonism, the best I could tell you is to start over with clean ROM, preferably the one listed at 4pda.ru thread about elephone P6000 (in the head section) and try again. There must be something messed up in your device. I really believe the config is independent of ROM. The secret is very simple, you must start with new version letter and at offset 184 set correct checksum. How to calculate checksum:
//cal checksum
byte checksum;
for(i=0; i<chip_cfg_len; i++) {
checksum += file_config;
}
file_config[chip_cfg_len] = (~checksum) + 1;
Where chip_cfg_len = 184
Then write the checksum and write 0x01 at offset 185.
I believe you already know where are the theshsold values - at offset 16 and 17.
If you wish, I could send you my hand crafted config, which I was an inspiration for my apk.
Good luck

Err... it looks like I am unable to install a clean ROM, or even to update the existing one. I guess I'll have to sort this issue out before I join back the discusssion.
I have a fully functionalV8.3_20141228 ROM running and carliv's CWM from the 7th of February installed. The phone offers me the OTA update and it downloads a ~23 MB update. When I agree to install it, the phone reboots to CWM and the update fails with the following messages:
E:Invalid command argument
Finding update package...
E:unknown volume for path [/storage/sdcard0/adupsfota/update.zip]
E:Can't mount /storage/sdcard0/adupsfota/update.zip
Installation aborted.
Click to expand...
Click to collapse
If I try to install the same update with ROM Manager, it also fails in CWM with the following message:
-- Installing: [FILENAME SHOWS HERE]
Finding update package...
Opening update package...
Installing update...
Installation aborted.
Click to expand...
Click to collapse
But when I reboot the phone, I get the "Android is upgrading...] Screen, saying it's optimizing 124 apps. I believe no actual update takes place, though.
And here's what I'd consider the relevant portion of the recovery.log file:
Preparing to install ROM...
about to run program [/cache/dowipedalvikcache.sh] with 1 args
mount: mounting /dev/block/platform/mtk-msdc.0/by-name/userdata on /data failed: Device or resource busy
mount: mounting /dev/block/platform/mtk-msdc.0/by-name/cache on /cache failed: Device or resource busy
mount: can't find /sd-ext in /etc/fstab
umount: can't umount /sd-ext: Invalid argument
run_program: child exited with status 1
about to run program [/sbin/chmod] with 3 args
about to run program [/tmp/recovery/11-rommanager.sh] with 2 args
mount: mounting /dev/block/platform/mtk-msdc.0/by-name/system on /system failed: Device or resource busy
about to run program [/sbin/umount] with 2 args
Click to expand...
Click to collapse
If I try to install the full 20150109 ROM with ROM Manager, it also fails in CWM, without displaying any meaningful messages in recovery. I also get the "Android is upgrading screen here".
The errors in recovery.log are the same as above.
I guess I could install the full ROM via SP Flash Tool, right?
Also... I have a couple of questions to ask, can I feel free to do it in this thread? Some might be trivial for most.

ludmiloff said:
Well, time to get in here, I guess...
@xenonism, the best I could tell you is to start over with clean ROM, preferably the one listed at 4pda.ru thread about elephone P6000 (in the head section) and try again.
Click to expand...
Click to collapse
@ludmiloff does your app require busybox to be installed?
Downloading from 4pda.ru is a bit hit and miss for me, any chance someone can post the CWMLollipop.img...
Is there any difference in the 4pda.ru ROMs and the ones on needrom.com?
Also found a fix for the backlight in Android L - in engineering mode - not sure if it will do anything useful in 4.4.4 (lower the minimum brightness?).
MTK Engineering Mode => Hardware => LCM => LCM Cycle => value between 5 and 55.
xenonism said:
Err... it looks like I am unable to install a clean ROM, or even to update the existing one. I guess I'll have to sort this issue out before I join back the discusssion.
Click to expand...
Click to collapse
Feel free to elaborate. Edit your previous post with your current setup / what you've tried - so we can turn it into a troubleshooting post.

HypoTurtle said:
Feel free to elaborate. Edit your previous post with your current setup / what you've tried - so we can turn it into a troubleshooting post.
Click to expand...
Click to collapse
Ok, thanks a lot. I will edit my post right now. The thing is... I haven't used an Android phone in 4 years and I did a lot of my tinkering on my P6000 while working or late at night so.. things got a bit messy.

@HypoTurtle,
My app does not require busybox. It simply run some commands in the shell, though.
In fact It is my first experience with android programming and I just followed some examples found here and there. I also wanted to make a Kotlin based app, but then I decided to continue with plain old java. The app might not a perfect one. Hope it worked for many of elephone owners
---------- Post added at 08:05 AM ---------- Previous post was at 07:41 AM ----------
@xenonism, you should try a clean ROM with sp flash tool. It is a bit tricky, I have tried one from needrom and as the author suggested, I did not check the preloader mark. Then my phone ended totally bricked. The ROM from 4pda worked for me. Today I'm going to reflash it again and investigate why my app does not work on it.

@ludmiloff, I ended up installing 20150109 via SP Flash Tool and then updating via OTA to the latest version. Sure enough, your app worked then. And permissions for gt9xx_config are now 666.
I am not particularly happy with the gravitybox solution for the notification issue, so I'm trying to look into it, but I am not really hopeful to achieve something.

xenonism said:
@ludmiloff, I ended up installing 20150109 via SP Flash Tool and then updating via OTA to the latest version. Sure enough, your app worked then. And permissions for gt9xx_config are now 666.
I am not particularly happy with the gravitybox solution for the notification issue, so I'm trying to look into it, but I am not really hopeful to achieve something.
Click to expand...
Click to collapse
Same I did just few minutes ago. Won't install updates and will try to make my app working on this ROM.
BTW. Russian method write a very different format to file /process/gmnodexxxxxxx where xxxxxxx is build date. I'm pretty sure if I could change the file with correct checksum and version letter it should work too.
Anyway, my intent was to fix the scroll after I applied the elephone apk. For sure the Russian method with correct version letter and checksum would work too and it is still the best flow now for phones with very stock ROM. I already explained how to calculate the checksum.

HypoTurtle said:
@ludmiloff does your app require busybox to be installed?
Downloading from 4pda.ru is a bit hit and miss for me, any chance someone can post the CWMLollipop.img..
Click to expand...
Click to collapse
I cant see any CWMLollipop.img there
They only list two recoverys my P6000CWM3.img with no links or credits of course
and carliv's CWM_Modd_2.img again no links or credits
I will be working on the lollipop soon
I am getting another phone very soon to use for daily life so I can use the P6000 for dev only purposes.

[KERNEL][x52x][OREO/PIE]EffectiveKernel + QS tile mode switch(BATTERY/BALANCE/GAMING)

for LeEco Le 2 x520 / x526 / x527
spandey65 said:
@DoubleHack Hope you had success in battery life for this Phone? Can you please create a thread and list the steps so that others can also benefit from your discoveries ?
Click to expand...
Click to collapse
this is a pre-compiled kernel with an excellent premade configurations and many tweak (install the zip from twrp) + a QS tile apk ( for pie use: RRLeecoPerf-signed.apk) to change between battery / balance / performance (once the apk is installed reboot and add the tile to the quick settings panel). The kernel have all of OverloadKernel and also has cpu and GPU voltage management (for undelvolt and overvolt), slight overclock of GPU freq, many governor and other features like boost on event by sultanxda (with per cpu basis tuning) ... and "simple algorithm addons" for adreno idler and more ...Quick and Fast charge also work. I recommend SmartPack-Kernel Manager or EX kernel manager for tweaking ... flash zip from twrp and install the apk normally.
SOURCE: https://github.com/Anubioz/android_kernel_leeco_msm8976
if you want for change parameters of the preconfigured profiles you have to modify file:
before flash in zip file: init.leeco.rc
after flash in root of your sd: /system/vendor/etc/init/hw/init.target .rc
(in these files you find line "on property:sys.leeco.performace_mode=[[0 for battery or 1 for balance or 2 for performance]] and below this line there are profile settings ; ask in a reply if u need more info) but if you don't know what I'm talking about, leave everything as it is
backup of system and boot partition with twrp is recommended
flash zip in twp > reboot > install the right apk based on your android version (for dub: you must install apk in android...not flash in twrp) > reboot > edit QUick Settings Panel (for dub: click on pen icon in bottom right of QS panel): Add QS tile named "Leeco [...something...]" > click on this QS tile and choose "battery mode" or your prefer mode (Battery/balance/gaming) ... Enjoy!!!
It should work also with android 8 oreo ... but for this you must use RRSwitcher-for-android-8.apk
thks to ANUBIOZ from 4pda.RU
UPDATE: 14/06/2019
if i help you hit thanks button!!!

if someone wants to modify the profiles in /system/vendor/etc/init/hw/init.target .rc ask and I will give them more information.
If someone changes their profiles in /system/vendor/etc/init/hw/init.target .rc and wants to share their configuration, they can post...they will be welcome

X522?
The title of your post says x52x so I would assume it does support x522 but the top of your post doesn't include x522. I have tried installing this on Android Pie x522 but I got error code 1.
Edit: So it looks like the x522 is the same as the x526, the only difference being that the x526 supports a wider range of bands for mobile data. So basically the x522 is the x526 except it was made to be sold in America.
So I'm guessing a quick edit of something in the zip file would let it install on the x522 variant?
Thanks for this kernel by the way, sounds like it would be extremely useful.
Edit 2: NVM what I said above, turns out the compatability error was because my TWRP was too old, simply flashed a newer one and it worked!

Its shows error 1 on installation what to do?
Using pixel experience 9 pie latest build
Twrp custom recovery installed..
Please reply anyone ASAP

kaleemkhan1996 said:
Its shows error 1 on installation what to do?
Using pixel experience 9 pie latest build
Twrp custom recovery installed..
Please reply anyone ASAP
Click to expand...
Click to collapse
Sorry i broke my type-c connector :crying: can't use my leeco anymore :crying: ... Due to this Unfortunately for now i cant no longer develop for this phone.... damn damaged type-c !!! i was forced to find a rapid solution to have a working android phone... Et-voilà...i try experiment to compile and run a kernel and lineage OS 16 build for (my 2012's junky found in the cellar) Samsung galaxy ace 2 (800mb system RAM+ , single cpu dual core 800ghz)and after overclock cpu(from 800 to 1200), gpu, DDR chip(gpu from 480 to 700 mhz
and for DDR... I don't remember... Seem to me a i add 300mhz more tonstandard freq),and after00 many other SoC-pushed-to-die tweak...i can say: IT IT'S ALIVE!!!!! And IT'S WORKS!!!!
..but return to leeco...
Have you installed from twrp or magisk? ( u must installato in twrp) error 1 is an incompatibility error: Twrp recognize that your device is not compatibile ... What version is your leeco?maybe you have a mtk le2 ? This kernel is not compatibile with mediatek soc, compatibile only with qualcoom snapdragon. Can you send me a log of twrp... Also if i don't have a leeco anymore, MAYBE i can recompile a flashable kernel that work for you...if your device is real compatible, maybe i can find error that not permitted to install kernel (without my real leeco device it could be a little more difficult ...damn! Damn! Damn typec)
bit i need more info from you. ( twrp version, code name of your phone, if any of your partition is encrypted and if any of tour partition is formatted in f2fs)

Got it working, thanks!
DoubleHack said:
Sorry i broke my type-c connector :crying: can't use my leeco anymore :crying: ... Due to this Unfortunately for now i cant no longer develop for this phone.... damn damaged type-c !!! i was forced to find a rapid solution to have a working android phone... Et-voilà...i try experiment to compile and run a kernel and lineage OS 16 build for (my 2012's junky found in the cellar) Samsung galaxy ace 2 (800mb system RAM+ , single cpu dual core 800ghz)and after overclock cpu(from 800 to 1200), gpu, DDR chip(gpu from 480 to 700 mhz
and for DDR... I don't remember... Seem to me a i add 300mhz more tonstandard freq),and after00 many other SoC-pushed-to-die tweak...i can say: IT IT'S ALIVE!!!!! And IT'S WORKS!!!!
..but return to leeco...
Have you installed from twrp or magisk? ( u must installato in twrp) error 1 is an incompatibility error: Twrp recognize that your device is not compatibile ... What version is your leeco?maybe you have a mtk le2 ? This kernel is not compatibile with mediatek soc, compatibile only with qualcoom snapdragon. Can you send me a log of twrp... Also if i don't have a leeco anymore, MAYBE i can recompile a flashable kernel that work for you...if your device is real compatible, maybe i can find error that not permitted to install kernel (without my real leeco device it could be a little more difficult ...damn! Damn! Damn typec)
bit i need more info from you. ( twrp version, code name of your phone, if any of your partition is encrypted and if any of tour partition is formatted in f2fs)
Click to expand...
Click to collapse
I already had a TWRP recovery installed but I guess it was too old for this Kernel. Because what I did was flash the latest TWRP available for my S2 and then tried flashing your zip again (because I was going to collect and send logs) and then it worked! FYI this is a Qualcomm Snapdragon S2
Edit: Just wanted to say thank you for making this kernel, it works flawlessly! Tested this with a heavy game and I noticed a dramatic FPS increase when switching from Power Saving Mode to Gaming Mode. Because of your Kernel, this phone is twice as useful for me now, Thanks again. Only thing I miss is quick charge..

QS tile not working but great kernel
The QS tile widget force closed for me everytime on los15.
I then built init.target.rc shell scripts for different performance modes and had a great impact on the battery and efficiency as required, while running them with tasker. Great kernel, good settings. Have attached shell scripts for all 3 performance modes, if anyone else is also struggling with the QS tile widget.

DoubleHack said:
Sorry i broke my type-c connector :crying: can't use my leeco anymore :crying: ... Due to this Unfortunately for now i cant no longer develop for this phone.... damn damaged type-c !!! i was forced to find a rapid solution to have a working android phone... Et-voilà...i try experiment to compile and run a kernel and lineage OS 16 build for (my 2012's junky found in the cellar) Samsung galaxy ace 2 (800mb system RAM+ , single cpu dual core 800ghz)and after overclock cpu(from 800 to 1200), gpu, DDR chip(gpu from 480 to 700 mhz
and for DDR... I don't remember... Seem to me a i add 300mhz more tonstandard freq),and after00 many other SoC-pushed-to-die tweak...i can say: IT IT'S ALIVE!!!!! And IT'S WORKS!!!!
..but return to leeco...
Have you installed from twrp or magisk? ( u must installato in twrp) error 1 is an incompatibility error: Twrp recognize that your device is not compatibile ... What version is your leeco?maybe you have a mtk le2 ? This kernel is not compatibile with mediatek soc, compatibile only with qualcoom snapdragon. Can you send me a log of twrp... Also if i don't have a leeco anymore, MAYBE i can recompile a flashable kernel that work for you...if your device is real compatible, maybe i can find error that not permitted to install kernel (without my real leeco device it could be a little more difficult ...damn! Damn! Damn typec)
bit i need more info from you. ( twrp version, code name of your phone, if any of your partition is encrypted and if any of tour partition is formatted in f2fs)
Click to expand...
Click to collapse
S2 x526 Qualcomm version twrp version 3.1 .2 using pixel experience plus 9 pie

Great Kernel But Fast Charge Not Working.

pls make profile switcher wrk
hello pls pls pls make the profile switcher work , when i try to switch profile from the notification shade it says that the app has stopped. I use lineage os 16 on leeco x526. pls make it work i rly like it

Does this work on android 10

princenna77 said:
Does this work on android 10
Click to expand...
Click to collapse
No , Only Oreo/Pie

scoopspoof said:
QS tile not working but great kernel
The QS tile widget force closed for me everytime on los15.
I then built init.target.rc shell scripts for different performance modes and had a great impact on the battery and efficiency as required, while running them with tasker. Great kernel, good settings. Have attached shell scripts for all 3 performance modes, if anyone else is also struggling with the QS tile widget.
Click to expand...
Click to collapse
Can you share the scripts?

[OVERCLOCK] GPU overclocking | Upgrade your Red Magic 3 to Red Magic 3s | Unleash the Beast

Before do all of this tutorial, Please keep in mind, that if you are dont have basic on Unix System dont do this!!​i am buy this device just for gaming only, and i am buy secondhand on 20 April 2021.
Goals : for overclock and unleash all inside the beast in my new secondhand red magic 3
Note : I am using Macbook to do all of this, and working adb
THIS ACTION WILL IMPACT TO YOUR HARDWARE DEVICE, PLEASE MONITOR YOUR DEVICE TEMPERATURE, AND DO AT YOUR OWN RISK!!!
check adb command with :
Code:
adb devices
Step by Step​1. Flash Global Rom (in my case, is still using global android 9) to China Rom : China Rom
note : using MD5:FB9ABF42A4711962272606E0437AFA12 v5.13
Optional installing GAPPS:​1.1 if you are using same ROM version as mine, install GAPPS with NIKGAPPS and put nikgapps.config to root /
1.2 run command
Code:
adb push nikgapps.config /
adb push NikGapps-core-arm64-11-20201231-signed.zip /
1.3 flash with twrp with install > install zip > pick <nikgapps zip>
2. Installing TWRP // for restoring boot.img if disaster happen : TWRP
3. Installing Magisk // for root access : Magisk, After all you have done with above step, do this :
4. Installing Konabess // set frequency GPU : Konabess APK, wanna some research with Konabess? do fork and star the author on Github: github
${FREQ} = move step by step from 650 to 800, [675, 700, 725, 750, 775, 800]. try this : set 650 restart play genshin/Antutu, monitor your temperature. repeat and repeat. youtube tutorial
Click to expand...
Click to collapse
4.a. open konabess
4.b. pick "EDIT GPU FREQ TABLE", > "ADD NEW" > SET Freq : ${FREQ}Mhz, bus-freq: 11, bus-min: 11, bus-max: 11, need to research more about this
4.c. pick "EDIT GPU VOLT TABLE", > "ADD NEW" > SET Freq : ${FREQ}Mhz, voltage level : NOM_L1, need to research more about this
nb : Please aware of this voltage table, this voltage table is from here, need to re-adjust for our Red Magic 3.
Click to expand...
Click to collapse
{
"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"
}
4.d. and then final "Backup old image" > remember your current path for boot.img, if disaster happen, boot to bootloader > recovery, and install <your backup boot.img> with target "boot" partition.
4.e. pick "REPACK AND FLASH NEW IMAGE"
Note: i am using 700Mhz for gaming daily driver, for PUBG and GENSHIN IMPACT "RATA KANAN"
Click to expand...
Click to collapse
Antutu V9​- stock rom : 510k
- before OC : 528k
- after OC : 588k
Antutu V8​- before OC : 431k
- after OC : 482k
Supporting Apps :​- Kernel auditor // set frequency if not in use
-- my setting for OOM (Out of Memory/Low memory killer is "Aggresive")
Additional Hardware :​- Black Shark fan Pro // tested well on frequency 850Mhz, NOM_L2
CN ROM Version V5.13 Report​
Works :
- shoulder button
- rotation
- no flicker
- many of them is stable
- sensor : Light, Proximity
Not works :
- sensor : Accelerometer, Magnetometer, Compass, Gyro. // was doin all of things "Wipe all on twrp except system"
Click to expand...
Click to collapse

Works with Poco X3 Pro ? Snapdragon 860 is just 855+ ?

astronomy2021 said:
Works with Poco X3 Pro ? Snapdragon 860 is just 855+ ?
Click to expand...
Click to collapse
Idk bro, I don't have poco X3 pro
It's not recommended do that after someone expert doin that.
On poco X3 pro, you just need to remove cpu throttle to improve stability performance if you don't care about heat issue

never00miss said:
Idk bro, I don't have poco X3 pro
It's not recommended do that after someone expert doin that.
On poco X3 pro, you just need to remove cpu throttle to improve stability performance if you don't care about heat issue
Click to expand...
Click to collapse
Thanks for Answer How do you remove it ? Magisk Module or someting else ?

astronomy2021 said:
Thanks for Answer How do you remove it ? Magisk Module or someting else ?
Click to expand...
Click to collapse
yup, you can use magisk module or something, the difference between gaming phone and standard phone is on heat management.
cause on standard android phone that use powerful SOC not designed to minimize heat issue.
so buy gaming phone instead of standard phone cause designed for heat issue. hahaha.

Have you completed further research on the subject?

SilentDevGuy said:
Have you completed further research on the subject?
Click to expand...
Click to collapse
for the deep research, i am not be able to do that cause my work as a programmer and have tight time to do my works.
but i was using 775 mhz for daily use,
and its was stable until this day.
whats the poin you ask that? that i can help you sir? @SilentDevGuy

never00miss said:
for the deep research, i am not be able to do that cause my work as a programmer and have tight time to do my works.
but i was using 775 mhz for daily use,
and its was stable until this day.
whats the poin you ask that? that i can help you sir? @SilentDevGuy
Click to expand...
Click to collapse
Id like to know the temperature effects. Such as how hot it runs on a heavy load for extended period of time and frame rate results

SilentDevGuy said:
Id like to know the temperature effects. Such as how hot it runs on a heavy load for extended period of time and frame rate results
Click to expand...
Click to collapse
750mhz Overclock
PUBG mobile - playing on 3.40 hours result :
- max temp : 78C
- avg temp : 65C
- min temp : 55C
Misc : using external fan

Thank you so much! How does the temperature spread across components? When at 78c is it uncomfy? I am creating a custom rom for red magic and will implement this gpu overclock
never00miss said:
750mhz Overclock
PUBG mobile - playing on 3.40 hours result :
- max temp : 78C
- avg temp : 65C
- min temp : 55C
Misc : using external fans
Click to expand...
Click to collapse

Are these battery temps, cpu temps, or gpu temps? How is your nand temperature? It is suppose to be never go past 50c(internal storage/memory)
never00miss said:
750mhz Overclock
PUBG mobile - playing on 3.40 hours result :
- max temp : 78C
- avg temp : 65C
- min temp : 55C
Misc : using external fan
Click to expand...
Click to collapse

never00miss said:
Before do all of this tutorial, Please keep in mind, that if you are dont have basic on Unix System dont do this!!​i am buy this device just for gaming only, and i am buy secondhand on 20 April 2021.
Goals : for overclock and unleash all inside the beast in my new secondhand red magic 3
Note : I am using Macbook to do all of this, and working adb
THIS ACTION WILL IMPACT TO YOUR HARDWARE DEVICE, PLEASE MONITOR YOUR DEVICE TEMPERATURE, AND DO AT YOUR OWN RISK!!!
check adb command with :
Code:
adb devices
Step by Step​1. Flash Global Rom (in my case, is still using global android 9) to China Rom : China Rom
note : using MD5:FB9ABF42A4711962272606E0437AFA12 v5.13
Optional installing GAPPS:​1.1 if you are using same ROM version as mine, install GAPPS with NIKGAPPS and put nikgapps.config to root /
1.2 run command
Code:
adb push nikgapps.config /
adb push NikGapps-core-arm64-11-20201231-signed.zip /
1.3 flash with twrp with install > install zip > pick <nikgapps zip>
2. Installing TWRP // for restoring boot.img if disaster happen : TWRP
3. Installing Magisk // for root access : Magisk, After all you have done with above step, do this :
4. Installing Konabess // set frequency GPU : Konabess APK, wanna some research with Konabess? do fork and star the author on Github: github
4.a. open konabess
4.b. pick "EDIT GPU FREQ TABLE", > "ADD NEW" > SET Freq : ${FREQ}Mhz, bus-freq: 11, bus-min: 11, bus-max: 11, need to research more about this
4.c. pick "EDIT GPU VOLT TABLE", > "ADD NEW" > SET Freq : ${FREQ}Mhz, voltage level : NOM_L1, need to research more about this
4.d. and then final "Backup old image" > remember your current path for boot.img, if disaster happen, boot to bootloader > recovery, and install <your backup boot.img> with target "boot" partition.
4.e. pick "REPACK AND FLASH NEW IMAGE"
Antutu V9​- stock rom : 510k
- before OC : 528k
- after OC : 588k
Antutu V8​- before OC : 431k
- after OC : 482k
Supporting Apps :​- Kernel auditor // set frequency if not in use
-- my setting for OOM (Out of Memory/Low memory killer is "Aggresive")
Additional Hardware :​- Black Shark fan Pro // tested well on frequency 850Mhz, NOM_L2
CN ROM Version V5.13 Report​
Click to expand...
Click to collapse
so i flashed the latest cn rom and now my gyroscope with other components are not working and then I rolled back to global and it still not working what should I do I am really stuck here please help me it bugges me its been over a week problem after problems accruing I really regret buying this pice of crap

Rebinaziz said:
so i flashed the latest cn rom and now my gyroscope with other components are not working and then I rolled back to global and it still not working what should I do I am really stuck here please help me it bugges me its been over a week problem after problems accruing I really regret buying this pice of crap
Click to expand...
Click to collapse
Its hard to help with so little information and you cant call something a piece of crap because you broke it. What rom are you on right now?

i have same problem, my sensors not working bro, plz.. help

never00miss said:
Before do all of this tutorial, Please keep in mind, that if you are dont have basic on Unix System dont do this!!​i am buy this device just for gaming only, and i am buy secondhand on 20 April 2021.
Goals : for overclock and unleash all inside the beast in my new secondhand red magic 3
Note : I am using Macbook to do all of this, and working adb
THIS ACTION WILL IMPACT TO YOUR HARDWARE DEVICE, PLEASE MONITOR YOUR DEVICE TEMPERATURE, AND DO AT YOUR OWN RISK!!!
check adb command with :
Code:
adb devices
Step by Step​1. Flash Global Rom (in my case, is still using global android 9) to China Rom : China Rom
note : using MD5:FB9ABF42A4711962272606E0437AFA12 v5.13
Optional installing GAPPS:​1.1 if you are using same ROM version as mine, install GAPPS with NIKGAPPS and put nikgapps.config to root /
1.2 run command
Code:
adb push nikgapps.config /
adb push NikGapps-core-arm64-11-20201231-signed.zip /
1.3 flash with twrp with install > install zip > pick <nikgapps zip>
2. Installing TWRP // for restoring boot.img if disaster happen : TWRP
3. Installing Magisk // for root access : Magisk, After all you have done with above step, do this :
4. Installing Konabess // set frequency GPU : Konabess APK, wanna some research with Konabess? do fork and star the author on Github: github
4.a. open konabess
4.b. pick "EDIT GPU FREQ TABLE", > "ADD NEW" > SET Freq : ${FREQ}Mhz, bus-freq: 11, bus-min: 11, bus-max: 11, need to research more about this
4.c. pick "EDIT GPU VOLT TABLE", > "ADD NEW" > SET Freq : ${FREQ}Mhz, voltage level : NOM_L1, need to research more about this
4.d. and then final "Backup old image" > remember your current path for boot.img, if disaster happen, boot to bootloader > recovery, and install <your backup boot.img> with target "boot" partition.
4.e. pick "REPACK AND FLASH NEW IMAGE"
Antutu V9​- stock rom : 510k
- before OC : 528k
- after OC : 588k
Antutu V8​- before OC : 431k
- after OC : 482k
Supporting Apps :​- Kernel auditor // set frequency if not in use
-- my setting for OOM (Out of Memory/Low memory killer is "Aggresive")
Additional Hardware :​- Black Shark fan Pro // tested well on frequency 850Mhz, NOM_L2
CN ROM Version V5.13 Report​
Click to expand...
Click to collapse
bro plz help , my sensores not working ,

SilentDevGuy said:
Its hard to help with so little information and you cant call something a piece of crap because you broke it. What rom are you on right now
Click to expand...
Click to collapse
You are right i was kinda out of my mind but anyways, i flashed it using red magic 3 unbrick tool it flashes the oldest rom which is 1.11 and worked my way to NX629J_ENcommon V1.21 cuz i thought it would fix it but it didn't, and changed a lots of gsi roms and used latest cn rom but that aslo throw me in the hole, and i read some posts here they said that you have ro flash persist.img in twrp (which comes with fastboot rom) and i couldn't find it anywhere and someone said you have to wipe everything and it fixs it but that also didn't work, its been a week and half I've read everything online even other phones having same problem but they alway fix theirs with flashing persist.img and i can't find it in the rom which they provide in their website

SilentDevGuy said:
Are these battery temps, cpu temps, or gpu temps? How is your nand temperature? It is suppose to be never go past 50c(internal storage/memory)
Click to expand...
Click to collapse
CPU temps,
And so far so good.
Rebinaziz said:
so i flashed the latest cn rom and now my gyroscope with other components are not working and then I rolled back to global and it still not working what should I do I am really stuck here please help me it bugges me its been over a week problem after problems accruing I really regret buying this pice of crap
Click to expand...
Click to collapse
1366gh said:
View attachment 5357549i have same problem, my sensors not working bro, plz.. help
Click to expand...
Click to collapse
1366gh said:
bro plz help , my sensores not working ,
Click to expand...
Click to collapse
Rebinaziz said:
You are right i was kinda out of my mind but anyways, i flashed it using red magic 3 unbrick tool it flashes the oldest rom which is 1.11 and worked my way to NX629J_ENcommon V1.21 cuz i thought it would fix it but it didn't, and changed a lots of gsi roms and used latest cn rom but that aslo throw me in the hole, and i read some posts here they said that you have ro flash persist.img in twrp (which comes with fastboot rom) and i couldn't find it anywhere and someone said you have to wipe everything and it fixs it but that also didn't work, its been a week and half I've read everything online even other phones having same problem but they alway fix theirs with flashing persist.img and i can't find it in the rom which they provide in their website
Click to expand...
Click to collapse
Do my thread, I am rollback to v3.xx latest, and do all wipe on all partition.
[Guide][Stable] How to clean Install CN ROM + TWRP + ROOT + GAPPS on our Nubia Red Magic 3
Hello guys, welcome again to my thread this thread will be my tutorial too for reminder how to reinstalling my Nubia Red Magic 3 i will tell you how to do step by step guide how to do clean Install : Requirement : - ADB installed, check with...
forum.xda-developers.com

i m using red magic 3 on android 11 china rom i m used your
Konabess,,,apk
i m expriance many frequencys

[Guide][Stable] How to clean Install CN ROM + TWRP + ROOT + GAPPS on our Nubia Red Magic 3

Hello guys, welcome again to my thread
this thread will be my tutorial too for reminder how to reinstalling my Nubia Red Magic 3
i will tell you how to do step by step guide how to do clean Install :
Requirement :
- ADB installed, check with command
Bash:
adb devices
Download all needed first :
First download ROM here V3.34 : http://romdownload.nubia.com/红魔3/V3.34/NX629J-update.zip
// android 11 is not stable yet, there is a lot of function like gyro and other sensor that not working
After that download TWRP here, https://forum.xda-developers.com/t/...twrp-for-nubia-red-magic-3-3s-stable.3962482/
then download Magisk APK : https://magiskmanager.com/
create a zip file from Magisk.apk -> Magisk.zip, we need both of them
then download NIK GAPPS NikGapps-core-arm64-10-20210424-signed.zip and nikgapps config, https://sourceforge.net/projects/nikgapps/files/
download nik gapps, Releases > 23 April 2021 > NikGapps-full-arm64-10-20210423-signed.zip > https://sourceforge.net/projects/ni...ps-full-arm64-10-20210423-signed.zip/download
download nik gapps config, Relaases > Config > nikgapps.config > https://sourceforge.net/projects/nikgapps/files/Releases/Config/nikgapps-config/
After download, do this carefully step by step :
Bash:
# go to download folder
cd ~/Downloads
# now on android, Settings > About Phone > click Build Number 5 times
# go to developer options with usb debugging enable
# Settings > Advanced Settings > Developers Option > Enable toggle USB Debugging > Enable toggle OEM Unlocking
# push ROM file to adb
adb push NX629J-update.zip /storage/emulated/0/
# after push go to your android,
# go to Settings > System Update > pick "..." 3 dot on top right corner > Local Update
# then install Choose from local and pick NX629J-update.zip
# Install
# now on android, after all ROM installed successful do unlock developer options
# Settings > About Phone > click Build Number 5 times
# go to developer options with usb debugging enable
# Settings > Advanced Settings > Developers Option > Enable toggle USB Debugging > Enable toggle OEM Unlocking
# then reboot to bootloader
adb reboot bootloader
# then do unlock and flash twrp
fastboot devices
fastboot oem nubia_unlock NUBIA_NX629J
fastboot flash recovery twrp-3.3.1-3-NX629J-mauronofrio.img
# and now twrp was installed, reboot with command below
# now we need to clean ROM installing
adb reboot recovery
# now on android, you can see twrp menu
# go to Wipe > Advanced Wipe > check all of thing in there
# check Dalvik/Art Cache
# check Cache
# check System
# check Vendor
# check Data
# check Internal Storage
# and "Swipe to Wipe" dont do reboot here!!! please dont do
# now push ROM zip again in twrp,
adb push NX629J-update.zip /
# if it cannot mount or said read only file system
# this step if error only !!
adb shell
# you will goin to android sh, run command mount
mount -o rw,remount /
exit
# you will goin to your shell again, do push zip again
adb push NX629J-update.zip /
# after your push now you need to enable read access again on /
adb shell
mount -o ro,remount /
exit
# now on twrp, go to Install > go to / directory, just pick "up a level" until its gone,
# and on / folder you will see NX629J-update.zip,
# and do install on NX629J-update.zip > "swipe to install"
# it will fill data on that we are wiping off
# then push Magisk.zip
adb push Magisk.zip /
# now on twrp, go to Install > go to / directory > install Magisk.zip
# then push
adb push NikGapps-core-arm64-10-20210424-signed.zip /
adb push nikgapps.config /
# now on twrp, go to Install > go to / directory > pick NikGapps-core-arm64-10-20210424-signed.zip
# > "swipe to install" > "wipe dalvik cache/cache"
# reboot to system now
adb reboot
# after you see launcher screen, do install Magisk.apk
adb install Magisk.apk
# popup will be shown on screen, and click "OK"
Now you get clean Install CN ROM with all working feature
- Disable cover detection on Screen
Settings > Lockscreen, Launcher and Theme > Toggle disable "pocket mode"
- Disable Recommeded Application
Settings > Lockscreen, Launcher and Theme > Launcher Setting > Toggle disable ["Fancy Icon", "show the first screen negative", "Recommended Applications"]
Done.
If anything mistakes happen let me know ya.
Not Working :
- Google services Push Notif on Lock Screen, bug hunter @Faonee
[Guide][Stable] How to clean Install CN ROM + TWRP + ROOT + GAPPS on our Nubia Red Magic 3
Hello guys, welcome again to my thread this thread will be my tutorial too for reminder how to reinstalling my Nubia Red Magic 3 i will tell you how to do step by step guide how to do clean Install : Requirement : - ADB installed, check with...
forum.xda-developers.com
Credit :
@Secretcow
[Guide] Unlocking Red Magic 3's Bootloader
Requirements: - To Unlock Bootloader On Nubia Red Magic 3 (NX629J), you will need a computer. - Charge the Nubia Red Magic to at least 50%. - You need a USB cable to connect your phone to PC. (Users reported better luck with usb 2.0 port vs usb...
forum.xda-developers.com
[Guide] Flashing TWRP & Granting Root Access (Magisk Systemless) - Red Magic 3
Use this guide to root for now for global rom: https://forum.xda-developers.com/red-magic-3/how-to/red-magic-3-root-guide-t3933148 Requirements: - Unlocked Bootloader On Nubia Red Magic 3 (NX629J)...
forum.xda-developers.com

Well sure I'm goona do this...well I'm waiting for the new update 红魔3/红魔3S Android R V5.14 coming soon.....

NubiaNinja said:
Well sure I'm goona do this...well I'm waiting for the new update 红魔3/红魔3S Android R V5.14 coming soon.....
Click to expand...
Click to collapse
I am not sure v5.14 is already stable yet, cause if we see v3 and v2, there is a lot of changes until it stable.
And there must plenty degraded performance instead of android 10. Cause I got AnTuTu only 450k on Android R on Rom v5.1x

never00miss said:
I am not sure v5.14 is already stable yet, cause if we see v3 and v2, there is a lot of changes until it stable.
And there must plenty degraded performance instead of android 10. Cause I got AnTuTu only 450k on Android R on Rom v5.1x
Click to expand...
Click to collapse
Yes @never00miss you were are saying right I think I'm only one who think observed feel the best update was of CN V3.34 Android 10 OF R3,but mine was something 3.04/3.09/3.11 OF R3S I can't remember ??but sure it was android 10 bruh ur saying right...review I'm playing pubg mobile for almost 12 hrs continuosly on this update V3.34 played till almost next update comes.With 90fps game mode on fan speed normal I remember I don't feel any issue lagging, shuttering or any kind of fps down and sometimes I recording too my gameplays making short clips of engaging on fights..well no problem BUT only problem I face was Render in game heavy for a bit of moment then I decided I have to upgraded to Android 11 I think so game needed but this is the time I upgraded by OTA means phone update push the new one V5.11 which was failed version of Android 11 full of bugs I used for some days then I can't play pubg mobile not running game launcher malfunctioning screen flickers and many bugs nevermind I make my mind to return back to android 10 well I think I have to put the 3.34 zip to internal storage like simple way of reboot to recovery by inbuilt recovery wipe/data/cache boom I started installing zip lol who knows the Android 11 new policy added anti-rollback...system Lol DEVICE BRICKEDDDDDD!This is Nubia fail! At that moment I knew I f_____up!
Wait for 1-2 week dead phone....since whole Chinese community of Nubia Redmagic3/3S Flooded and crying in Chinese forum then the GOD ENTERS THE CHAT "SCARLETT GLASS" POSTED SOMETHING A RECOVERY TOOL Then the issue solved TWRP flashed since then I rooted checking gsi roms and new updates V5.11 Rebrushed and rightnow I'm on V5.13 but truely I'm saying my honestly review I don't like ANDROID 11 I can't play for long periods maximum 3-4hours pubg heating so much lagging and shuttering occurs! Device heat so much exceed sometimes 50 degrees lol I don't want to lost my precious hands I don't have girlfriend yet! Lol..... I'm afraid to play for long time!
GO FOR V3.34 PEOPLES WHO LOOK.....THIS POST WELL people this is the #Antutu Score of my Android 11 CN V5.13 NUBIA REDMAGIC 3S Well this score is due to SD 855+ I think so so...never mind YOU CAN SEE THE DIFFERENCE SCORE OF R3 AND R3S CPU AN D GPU R3 WINS....
R3S Has more scored but R3 have some stability...so V3.34 wins! Even Chinese forum people confirm V3.34 was best!
note: I can't remember which version I was running on android 10 I forgot 3.04/3.09/3.11??
sorry..on my RM3S but android 10

This works on both version of RM3 right?

NubiaNinja said:
Yes @never00miss you were are saying right I think I'm only one who think observed feel the best update was of CN V3.34 Android 10 OF R3,but mine was something 3.04/3.09/3.11 OF R3S I can't remember ??but sure it was android 10 bruh ur saying right...review I'm playing pubg mobile for almost 12 hrs continuosly on this update V3.34 played till almost next update comes.With 90fps game mode on fan speed normal I remember I don't feel any issue lagging, shuttering or any kind of fps down and sometimes I recording too my gameplays making short clips of engaging on fights..well no problem BUT only problem I face was Render in game heavy for a bit of moment then I decided I have to upgraded to Android 11 I think so game needed but this is the time I upgraded by OTA means phone update push the new one V5.11 which was failed version of Android 11 full of bugs I used for some days then I can't play pubg mobile not running game launcher malfunctioning screen flickers and many bugs nevermind I make my mind to return back to android 10 well I think I have to put the 3.34 zip to internal storage like simple way of reboot to recovery by inbuilt recovery wipe/data/cache boom I started installing zip lol who knows the Android 11 new policy added anti-rollback...system Lol DEVICE BRICKEDDDDDD!This is Nubia fail! At that moment I knew I f_____up!
Wait for 1-2 week dead phone....since whole Chinese community of Nubia Redmagic3/3S Flooded and crying in Chinese forum then the GOD ENTERS THE CHAT "SCARLETT GLASS" POSTED SOMETHING A RECOVERY TOOL Then the issue solved TWRP flashed since then I rooted checking gsi roms and new updates V5.11 Rebrushed and rightnow I'm on V5.13 but truely I'm saying my honestly review I don't like ANDROID 11 I can't play for long periods maximum 3-4hours pubg heating so much lagging and shuttering occurs! Device heat so much exceed sometimes 50 degrees lol I don't want to lost my precious hands I don't have girlfriend yet! Lol..... I'm afraid to play for long time!
GO FOR V3.34 PEOPLES WHO LOOK.....THIS POST WELL people this is the #Antutu Score of my Android 11 CN V5.13 NUBIA REDMAGIC 3S Well this score is due to SD 855+ I think so so...never mind YOU CAN SEE THE DIFFERENCE SCORE OF R3 AND R3S CPU AN D GPU R3 WINS....
R3S Has more scored but R3 have some stability...so V3.34 wins! Even Chinese forum people confirm V3.34 was best!
note: I can't remember which version I was running on android 10 I forgot 3.04/3.09/3.11??
sorry..on my RM3S but android 10
Click to expand...
Click to collapse
No, you got it wrong on AnTuTu version, you are run on v9 AnTuTu that on my device it will get score on 588k, on you are on 536k
You can see the results on my thread, in this thread I am using v5.13
[OVERCLOCK] GPU overclocking | Upgrade your Red Magic 3 to Red Magic 3s | Unleash the Beast
Before do all of this tutorial, Please keep in mind, that if you are dont have basic on Unix System dont do this!! i am buy this device just for gaming only, and i am buy secondhand on 20 April 2021. Goals : for overclock and unleash all inside...
forum.xda-developers.com
Faonee said:
This works on both version of RM3 right?
Click to expand...
Click to collapse
Yup, correct, both RM3 and RM3s works very well

never00miss said:
No, you got it wrong on AnTuTu version, you are run on v9 AnTuTu that on my device it will get score on 588k, on you are on 536k
You can see the results on my thread, in this thread I am using v5.13
[OVERCLOCK] GPU overclocking | Upgrade your Red Magic 3 to Red Magic 3s | Unleash the Beast
Before do all of this tutorial, Please keep in mind, that if you are dont have basic on Unix System dont do this!! i am buy this device just for gaming only, and i am buy secondhand on 20 April 2021. Goals : for overclock and unleash all inside...
forum.xda-developers.com
Yup, correct, both RM3 and RM3s works very well
Click to expand...
Click to collapse
never00miss said:
No, you got it wrong on AnTuTu version, you are run on v9 AnTuTu that on my device it will get score on 588k, on you are on 536k
You can see the results on my thread, in this thread I am using v5.13
[OVERCLOCK] GPU overclocking | Upgrade your Red Magic 3 to Red Magic 3s | Unleash the Beast
Before do all of this tutorial, Please keep in mind, that if you are dont have basic on Unix System dont do this!! i am buy this device just for gaming only, and i am buy secondhand on 20 April 2021. Goals : for overclock and unleash all inside...
forum.xda-developers.com
Yup, correct, both RM3 and RM3s works very well
Click to expand...
Click to collapse
Yes, I looked at the thread carefully but you haven't mentioned that we RM3S users can also apply this method...for overclock well I have to try it first...lol I think that thread is only for RM3 users... Sorry. Yeah V9 Antutu was score is damnn soo good.... Lesss goooo.....

NubiaNinja said:
Yes, I looked at the thread carefully but you haven't mentioned that we RM3S users can also apply this method...for overclock well I have to try it first...lol I think that thread is only for RM3 users... Sorry. Yeah V9 Antutu was score is damnn soo good.... Lesss goooo.....
Click to expand...
Click to collapse
Cause konabess process is unpacking binary on boot.img and re-compiling again, and boot.img it's same on all CN ROM that working on both devices RM3 and RM3s

I've installed everything succesfully. Only one thing thats bugging me that app notification doesn't show up on the lockscreen. I've tried disabling and enabling lockscreen notification but still not showing.

Faonee said:
I've installed everything succesfully. Only one thing thats bugging me that app notification doesn't show up on the lockscreen. I've tried disabling and enabling lockscreen notification but still not showing
Click to expand...
Click to collapse
ZTE have their own SDK for showing push notification info on their lock screen, and not all of apps support this lock screen info and integrate ZTE notification SDK.
So this problem depends on developer of apps, or ZTE must develop to allow all notification showing in locks screen and allow Google play services to show notification on lock Screen, * this is impossible yet cause of china vs us regulations for integrating gapps.
You can go on notification, Settings > Notification and status Bar > Notification Management > System, a lot of apps provided by CN ROM is supported by showing notif on lock screen. But in third party apps is not showing advanced feature to show notif on lock screen
*For reminder who's people is installing CN ROM, google services SDK feature like push notification (fcm) Or anything relate will not supported by apps in CN ROM it self. if you wanna working push notification and supported by system apps, you need to install from ZTE appcenter

never00miss said:
ZTE have their own SDK for showing push notification info on their lock screen, and not all of apps support this lock screen info and integrate ZTE notification SDK.
So this problem depends on developer of apps, or ZTE must develop to allow all notification showing in locks screen and allow Google play services to show notification on lock Screen, * this is impossible yet cause of china vs us regulations for integrating gapps.
You can go on notification, Settings > Notification and status Bar > Notification Management > System, a lot of apps provided by CN ROM is supported by showing notif on lock screen. But in third party apps is not showing advanced feature to show notif on lock screen
*For reminder who's people is installing CN ROM, google services SDK feature like push notification (fcm) Or anything relate will not supported by apps in CN ROM it self. if you wanna working push notification and supported by system apps, you need to install from ZTE appcenter
Click to expand...
Click to collapse
Thanks for the reply. Well that sucks. Need to get used to it somehow Haha.

Can you please write a guide to install android 11? I know it got bugs but I want to try it once atleast

souma_rox said:
Can you please write a guide to install android 11? I know it got bugs but I want to try it once atleast
Click to expand...
Click to collapse
Same as this tutorial "maybe", cause a lot of update on ZTE CN ROM flashable via TWRP.
You just need to change from v3.3x zip to v5.1x zip and flash on TWRP.
And what's said by @mauronofrio that TWRP only works again Chinese bootloader, so its "maybe" possible to flash CN ROM via twrp

Adb comand doesn't work for me.

Amuror3z said:
Adb comand doesn't work for me.
Click to expand...
Click to collapse
whut?? you need to make sure your adb installed well bruh.

Can we use the ok google hotword in the CN rom?

souma_rox said:
Can we use the ok google hotword in the CN rom?
Click to expand...
Click to collapse
You need to install full pack of nikgapps to get google assistant

I'm not sure what I'm doing wrong. I got Magisk to work and I have the rom up and running, but google play store doesn't seem to work. Which version exactly do I need to flash?

hidelater said:
I'm not sure what I'm doing wrong. I got Magisk to work and I have the rom up and running, but google play store doesn't seem to work. Which version exactly do I need to flash?
Click to expand...
Click to collapse
NIK GAPPS NikGapps-core-arm64-10-20210424-signed.zip

heya, nice guide.
just wanted to notify you that if you want to install the 3.34 cn rom / global rom from inside twrp, you might get a zip error.
to fix this, simply delete compatibility.zip from inside the NX629J-update.zip
under linux you can do this simply with "zip -d NX629J-update.zip compatibility.zip".
unpacking/repacking the zip is not advised
edit: seems this is only a thing if you try to flash from android 11 (v5.14) to android 10 (v3.34)
oh and the "adb reboot recovery" command (after flashing twrp) wont work since you are in fastboot mode during that step, "fastboot reboot recovery" might work