Database Info

UHANS U300 - Development & Support

In order to keep this thread clean, please use this one to discuss about Development, Support or Software Updates.​
ROMs:
To avoid any possible issue, do not forget to backup your NVRAM so that you won't risk to lose your IMEI. How-to: http://www.anythingultimate.in/2015/11/how-to-backup-your-nvram-partition.html
Stock (Android 6.0)
- V3.03: https://mega.nz/#!TYMyTA5Y!humI30xK0HIz1y5WfnALlK72AAiOtb4NiRzn3y2Fgqs
DO NOT USE THE "Format All & Download" OPTION IF YOU CARE ABOUT YOUR IMEI! Choose "Download Only" instead.
Previous Releases:
- Not yet.
Flash Tool
- SP Flash Tool v5.1628 for Windows & Linux: https://mega.nz/#F!dYUm0TbB!SWeMLb5Wu1NbRzTPQ8-s_A​
Recovery:
- TWRP 3.0.3: https://forum.xda-developers.com/showpost.php?p=70546519&postcount=5​
Root:
Rooting Methods (if you are on Stock ROM)
- SuperSU (flashable using TWRP): http://forum.xda-developers.com/apps/supersu​
Extras (Root-Only):
Customization
- Xposed Framework: http://forum.xda-developers.com/showthread.php?t=3034811​
Useful Third-Party Apps:
Battery Life
- Amplify: https://play.google.com/store/apps/details?id=com.ryansteckler.nlpunbounce&hl=en
- Greenify: https://play.google.com/store/apps/details?id=com.oasisfeng.greenify&hl=en​

Thanks Alberto, i managed to build a TWRP and a CTR recovery for U300.
Unfortunately TWRP have no working touch because of a kernel issue, but you can use OTG mouse to work on this... Later i will try with latest 3.03 rom and share with community. Regards

megthebest said:
Thanks Alberto, i managed to build a TWRP and a CTR recovery for U300.
Unfortunately TWRP have no working touch because of a kernel issue, but you can use OTG mouse to work on this... Later i will try with latest 3.03 rom and share with community. Regards
Click to expand...
Click to collapse
For @jemmini : another device with the same touch issue.

U300 CTR and TWRP recoveries:
https://mega.nz/#!iUdTUb7D!PNZQSPwS3psOWxzBa79AB1qbJ2Si7Qh3aQTUwVmEsww
Download and Install correctly Mediatek Preloader drivers before using Flashtool
( Take care on Windows 8.1/10 drivers, you need to disable driver signature before install
https://www.youtube.com/watch?v=50pD0mONm44
http://laurentiumihet.ro/technology...-for-32-64-bit-drivers-installation-tutorial/
https://thebroodle.com/microsoft/windows/install-mediatek-mt65xx-usb-vcom-drivers-windows-8-8-1/
Pre Requisite: Unpack all files in a directory on desktop;
- Rename U300 Carliv CTR.img into Recovery.img (if you wanto to flash CTR recovery)
- Rename U300TWRP 3.02 No Touch.img into Recovery.img (if you wanto to flash TWRP recovery, but remember that you need OTG Mouse to use this recovery)
1- With flashtool load MT6750_Android_Scatter.txt
2- Select download and connect smartphone to pc (smartphone must be powered off)… in few seconds will start the process and the new CTR/TWRP will be flashed
P.S after flashing, enter immediately in CTR/TWRP at boot using POWER and VOL + keys at the same time until Logo; it will appear a text menu with 3 options, choose Recovery (first row) with vol- and wait the loading of Custom Recovery.
Please NOTE that CTR recovery could access internal memory that is named ExtraSD (so in install menu, choose zip from ExtraSD).
Move in CTR Recovery with Vol+ and Vol - and confirm with Power key.
Credits: [MENTION]carliv[/MENTION], @jemmini

TWRP 3.0.3 for UHANS U300
TWRP 3.0.3 for UHANS U300
Based on Android 6.0 firmware ver.DK9FA2FWTAG.HSA.UHANS.HB.F.SA.0105.V3.03 / Thu Jan 5 20:12:17 CST 2017
WARNING!! Strictly follow these installation instruction!
Install:
1. Flash the recovery.img using SP FlashTool
2. Enter into TWRP and Install the patch "SuperSU 2.79"
3. Reboot to the system

Thanks for sharing

Main Thread (with reviews and so on) has been replaced: https://forum.xda-developers.com/ge...ans-u300-information-reviews-5-5-fhd-t3555430

thanks

System.IMG Repack
In order to customized my UHANS U300, I already unpack and repack my System.IMG with various software, tools, script, Cygwin, android kitchen, Assayed Kitchen and also through Linux Mint and Lubuntu... but my phone stuck during boot. (Only display boot image from logo.bin). I believe my repack System.IMG's size was correct but the phone still stuck, and checksum failed. (I disable checksum by change switch from "1" to "0".
Can anybody help me, how to get rid of these?
Thanks in advance guys.

I bought it off ebay cheap (for £35) even though it's almost £200 on gearbest etc. I don't think people would want to clone this phone but wondered how it could be that cheap. My kernel version: 3.18.22 is this the latest update for the phone? I did a factory reset since when I got it it was already set up (even though sold as new) I could see an after-image of the Chinese seller so wanted to be safe rather than sorry. Hope someone can help in getting the most out of this phone/remove bloatware etc and how to check everything's ok?
Also any way to upgrade Android?

Cubot Cheetah 2 Nougat Challenges

I have a Cubot Cheetah 2 with Nougat (7.0) [build CUBOT_6143C_CHEETAH_2_V15_20170623].
I have managed to unlock the bootloader (and confirmed it is unlocked) and was hoping to use the following
"Fastboot boot TWRP.img"
to open and use TWRP to take a pre-root copy of my phone without flashing and then proceed to flash TWRP and then Root it.
I have tried several copies of TWRP 3.0 (supposedly for a Cubot Cheetah 2) extracting image files from the zip or rar files and running Fastboot as above. In all cases I get the following message;
downloading 'boot.img'...
OKAY [ 0.931s]
booting...
FAILED (remote: invalid kernel address: not lie in memory)
finished. total time: 0.947s
Understandably the time taken varies a little each time but I'm unable to understand why files intended for the Cheetah 2 do not work. If this will not work using the Fastboot boot option, I suspect it will not work with flash option.
Can anyone help me please.
Thanks.

TWRP and Rooting a Cubot Cheetah 2 (Nougat)
Android_Dog_Walker said:
I have a Cubot Cheetah 2 with Nougat (7.0) [build CUBOT_6143C_CHEETAH_2_V15_20170623].
I have managed to unlock the bootloader (and confirmed it is unlocked) and was hoping to use the following
"Fastboot boot TWRP.img"
to open and use TWRP to take a pre-root copy of my phone without flashing and then proceed to flash TWRP and then Root it.
I have tried several copies of TWRP 3.0 (supposedly for a Cubot Cheetah 2) extracting image files from the zip or rar files and running Fastboot as above. In all cases I get the following message;
downloading 'boot.img'...
OKAY [ 0.931s]
booting...
FAILED (remote: invalid kernel address: not lie in memory)
finished. total time: 0.947s
Understandably the time taken varies a little each time but I'm unable to understand why files intended for the Cheetah 2 do not work. If this will not work using the Fastboot boot option, I suspect it will not work with flash option.
Can anyone help me please.
Thanks.
Click to expand...
Click to collapse
I have done a lot of searching and found the following;
a) Fastboot boot recovery.img does not work on this phone, There may be some Kernel options required to be passed but I cannot find them,
b) Flashing MDSTWRP_3.0.2-7ES_Cubot_Cheetah2 from Needrom, flashes ok by either using "SP Flash tool" or "Fastboot flash recovery recovery image", but when you start the phone or reboot using "Fastboot reboot" and enter recovery, the stock rom has overwritten it. I have tried multiple flashes and erasing the partition first with no success.
The above appear to mean that I cannot use TWRP (or other Custom recovery) and so cannot install the SuperSu.zip. I have raised this on Needrom with TWRP creator who cannot offer a solution.
Before I try using an app, I'd like to ask if anyone has a solution to stop recovery being overwritten. (I have been unable to find a pre rooted image or an image containing TWRP).
Thanks
Solution Found.....The file available from NeedROM will not work with Nougat on a Cheetah 2.
rebuilt MDSTWRP_3.0.2-7ES_Cubot_Cheetah2 using Carliv Image Kitchen and the Nougat stock rom Recovery and.... the Fastboot boot recovery.img works. I will confirm if the flashing option works during the next couple of days, but this helps understanding of why earlier attempts failed.
The Cubot Cheetah 2 gives no error messages if you are trying to start an incompatible recovery file, it just overwrites recovery with stock recovery and opens that.
This thread can now be closed
I confirm that my modified version works (flash or boot). I do not know how to modify the version info yet, so I cannot publish it.

Any idea on when you might be able to post some info on the modified build? Or even some instructions for us to try and follow your lead?

I would be happy to share my version but I am concerned that it is a ported version based on the current version in Needrom created by MDSdev and the opening screens reflect that ROM build info. If someone would advise me what the rules are regarding this I am happy to change it and then publish.
Alternatively I could finish writing out the process (already started) I went through so that I have a record and others can use it to port their own version, but each version created will also reflect MDSdev's original configuration information and this does not sit well as they did the hard bit of configuring TWRP to work with Cubot Cheetah 2 hardware and earlier Android (6.0/6.1). All I have done is get it working on a Nougat(7.0) version of the Cheetah 2. Advice from an expert in these matters would be helpful.

Gotcha, hopefully someone will
chime in, I would hope given the nature of xda, as long as those who input are acknowledged and recognised all should be well....

Cubot Cheetah 2 Android 7 Root by EpicFail2017
Hi Guys i have a Cubot Cheetah 2 Android 7.
Sorry my english sucks realy!
I found only a soulution to Root it with Magisk 14.2 beta!
1 First Step Download only PC Flash Files V14 170719 and unpack it !
http://forum.cubot.net/viewtopic.php?f=21&t=1475
The ROM this FilePC Flash Files V14 170719
https://mega.nz/#F!YIt2UKLL!E2PGw3IJ_KeCuVwXhstdFw
------------------------------------------------------------------------------------------------------------
2 Step Download and Install last version!
http://spflashtools.com/windows/sp-flash-tool-v5-1728
------------------------------------------------------------------------------------------------------------
3. Step
Download Magisk v14.2 Beta and Magisk Manager Version: v5.3.0, pu it on your SDCard!
Latest Stable Magisk Version: v14.2
Latest Magisk Manager Version: v5.3.5
https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445
----------------------------------------------------------------------------------------------------------------------------
4 Step
Download and unzip my Patched boot.img ,then Replace the boot.img in Folder from Step 1 !
https://mega.nz/fm/Q6YV3QrZ
http://www117.zippyshare.com/v/EiwE8p57/file.html
----------------------------------------------------------------------------------------------------------------------------
5 Step
Flash with SpFlash the Rom from Step 1 in Format +Download Mode.
Make a backup first from all your Stuff and Apps!
---------------------------------------------------------------------------------------------------------
6 Step
Start Android and make dev option enabel. Usb debug etc!
Install Latest Magisk Manager Version: v5.3.5 from SdCard!
Start and make under Options update beta kanal!
Install Magisk 14.2 Beta and rebot your Phone!
Wolla you have Root this ***** !
---------------------------------------------------------------
7 Step
Download Maui META ver 9.1724.0.00 to fix The Invalid Imei Problem after flashing!
For me this step was need after flashing root+room!
https://www.needrom.com/download/mauimeta-version-9-1724/
Mfg
EpicFail2017

Any idea why the IMEI might get lost? I'm aware that that can happen in mediatek stuff with custom, but is this due to a binary check of boot.img or one of the other ROMS? Or is it the spflash util acting up because of boot.img?
I've two of these phones at the min, one of them already has some issues so don't want to play with that one as of yet - power on issues and fingerprint sensor seems to act up - anyone else?
I'm already on nougat, and your procedure is exactly the same as I was thinking (already patched boot.img using magisk 14.0 but maybe I need use the beta as you did). I didn't get to the flashing of boot.img as I'm more comfortable doing flashing the partition straight from PC (adb/fastboot etc). I'm guessing mediatek can only be flashed safely with sptool? Do we need to reflash ALL partitions as IF we can, flashing boot.img to an upgraded phone should work without loss of data/imei? maybe?
What is the 'R' near the signal in your screenshots?

I'll answer my own questions with a way to root The Cubot Cheetah 2 (Nougat) in just a few minutes ..
I was already on the same version of nougat as the download before I started.
1. Download the ROM shown above and extract, grab the SPFlash too and the drivers. Ensure unknown sources is ticked, unlock bootloader - I also disabled pin security etc (dunno if this was needed).
* Note, install the drivers with the phone NOT connected via USB.
2. Transfer the boot.img to your phone and run it through Magisk (I used the beta 14.2 as documented above and manager 5.35), patch the image file (boot.img)
3. Move the patched boot.img from the magisk folder back to the computer.
4. Run the SPFlash tool load the scatter file, select DOWNLOAD and untick everything asides from boot.img
5. With phone switched off, connect it via USB
Flash
Wait until complete
Reboot
Rooted
No loss of IMEI or data.

It's good to see some responses. I seemed to struggle with TWRP and rooting for a while and now several options are apparently available. My personal opinion (I would say this wouldn't I!) is that if I can get advice on publishing/sharing the working version of TWRP on Cubot Cheetah 2, it is really simple to root the device by flashing TWRP, copy latest version of Supers.zip onto to SD card, open phone in recovery (Which is now TWRP), set English as default language (a one time action), install the Supers.zip. Job done, rooted with the best SuperSu facilities and an industry recognised backup facilities.
Unfortunately I have not yet had any advice on how to version the Nougat version from anyone on XDA yet and I am looking at trying to get MDSdev (the Cheetah 2 Marshmallow TWRP developer) to adopt the Nougat version.

That was my worry, not sure of compatibility of TWRP or boot time stuff on the mediatek devices. Rooting is now very very simple with the previous instructions, I was thinking flashfire or flashify or similar to push recovery onto the recovery partition but it's making sure TWRP is aware of the partitions. 10 years ago I'd have had a good look through the sourcecode for any possible problems but simply don't have the time these days :/
Love the phone but was put off using it as my primary phone due to lack of root. Okay I had to install stuff on the computer to flash this, but it's turned out it's very very easy and seems very safe too!

You may like to note that MDSdev have now published a new version of TWRP that works on Nougat (this is also a later version of TWRP).
https://www.needrom.com/download/twrp-3-1-1-1-mdsdev/

Android_Dog_Walker said:
You may like to note that MDSdev have now published a new version of TWRP that works on Nougat (this is also a later version of TWRP).
https://www.needrom.com/download/twrp-3-1-1-1-mdsdev/
Click to expand...
Click to collapse
EpicFail2017 said:
Hi Guys i have a Cubot Cheetah 2 Android 7.
Sorry my english sucks realy!
I found only a soulution to Root it with Magisk 14.2 beta!
1 First Step Download only PC Flash Files V14 170719 and unpack it !
http://forum.cubot.net/viewtopic.php?f=21&t=1475
The ROM this FilePC Flash Files V14 170719
https://mega.nz/#F!YIt2UKLL!E2PGw3IJ_KeCuVwXhstdFw
------------------------------------------------------------------------------------------------------------
2 Step Download and Install last version!
http://spflashtools.com/windows/sp-flash-tool-v5-1728
------------------------------------------------------------------------------------------------------------
3. Step
Download Magisk v14.2 Beta and Magisk Manager Version: v5.3.0, pu it on your SDCard!
Latest Stable Magisk Version: v14.2
Latest Magisk Manager Version: v5.3.5
https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445
----------------------------------------------------------------------------------------------------------------------------
4 Step
Download and unzip my Patched boot.img ,then Replace the boot.img in Folder from Step 1 !
https://mega.nz/fm/Q6YV3QrZ
http://www117.zippyshare.com/v/EiwE8p57/file.html
----------------------------------------------------------------------------------------------------------------------------
5 Step
Flash with SpFlash the Rom from Step 1 in Format +Download Mode.
Make a backup first from all your Stuff and Apps!
---------------------------------------------------------------------------------------------------------
6 Step
Start Android and make dev option enabel. Usb debug etc!
Install Latest Magisk Manager Version: v5.3.5 from SdCard!
Start and make under Options update beta kanal!
Install Magisk 14.2 Beta and rebot your Phone!
Wolla you have Root this ***** !
---------------------------------------------------------------
7 Step
Download Maui META ver 9.1724.0.00 to fix The Invalid Imei Problem after flashing!
For me this step was need after flashing root+room!
https://www.needrom.com/download/mauimeta-version-9-1724/
Mfg
EpicFail2017
Click to expand...
Click to collapse
Anyone uploading a mirror of nougat TWRP, please.
Also i´m kind of shy flashing the recovery with patched boot.img, any experience?
Someone with nougat and superSU here? Magisk seems to have some errors with some xposed moduls duo lag of "su-root-floder"
Do you password protect your recovery?

I have now tried the Magisk and TWRP routes to achieve rooting. My preference is the TWRP route because it has the fewest steps and works!.
An point worth noting is that if you are a new user on needrom, you need to register using Chrome, Firefox or other non Microsoft browser. Once registered Microsoft Edge works. I don't know why the registration with Edge fails but It is annoying when you complete the process and do not get the registration e-mail. Without registering you cannot get the TWRP download referenced above.

Hi,
Everything seems fine except if i make a wipe of dalvik cache every app stop working. The only solution is to wipe data or flash rom again with flashtool.
any can fix it on TWRP 3.1.1.1 ?

EpicFail i´m not sure, maybe security related issue. Instead of flashing rom i prefer restore backup^^
Still did not find a public nougat TWRP download
Both old 6.0 twrp freeze if timer is set and screen is going to turn off. Isn´t an issue anymore?
Today i hardly crashed system, it was in relation to magisk modul (busybox) update issue https://forum.xda-developers.com/apps/magisk/module-canstantly-module-updated-reboot-t3696943
EDIT: switched to supersu, busybox now working
Yesterday xposed appsops was getting a fix it is still unoffical
https://forum.xda-developers.com/xposed/modules/xposed-appopsxposed-appops-4-3-t2564865/page89
Edit:
updated to magisks unoffical xposed framework 3.1.4

[twrp_3.1.0]_m10_mt6572_ext4_emmc_chinaphone

******TWRP 3.1.0 FOR M10 CHINAPHONE******
---------------------------------------------------------------------------
DISCLAIMER : this is an unnoficial build created by myself Tested and confirmed working
NOT WORKING : MTP
THIS IS FOR EXT4 ONLY IF YOU NEED UBIFS OR YAFFS2 RECOVERY COMMENT HERE I WILL BUILD YOU ONE AGAIN EXT4 ONLY...
_______________________________________________
NOTICE : take a firmware backup before flashing
Anything to your device though this recovery is
Confirmed working you should always back your original firmware up, This recovery does NOT come with a Scatter.file included to stop bricking with incompatible device partitions
--------------------------------------------------------------------------
1. Unzip the recovery from the .zip.
2. Open SP Flash tool.
3.set your DA AGENT to all in one MTK DA.
4.load your scatter.file into the Flash tool.
5.wait for your scatter to load your files.
6.unselect all files for flash but recovery.
7.load twrp_3.1 into recovery slot.
7.1 flash my patched boot.img below also.
8.MAKE SURE DOWNLOAD ONLY is set DO NOT use format all + download.
9. Click start button
10. Connect to pc with usb cord.
12. wait for flash to complete.
13. Unplug & take out & insert your battery.
14. Hold power & volume up until the first screen appears and release, TWRP will now load.
15. Swipe to allow modifications.
Thats it Happy Flashing dont forget the thanks button & enjoy
---------------------------------------------------------------------------
If you need help please dont be afraid to ask here im here to help, if it does not boot on your device your board is different in which case you will need to attach your boot.img & recovery.img in a post so i can download and create a compatible twrp for your device.
_____________________________________________
LINKS :
TWRP 3.1.0
https://drive.google.com/file/d/1yhFWmbTUQLFvJCGZnUX20oF-f6TTEBaX/view?usp=drivesdk
Patched Boot.img : will be up later
Removed the following.
*SB.CHK
*Encrypted footers on userdata from :
*fstab
*fstab.fat
* fstab.fat.nand,
*adjusted kernel slightly this will not affect the operation of the system or operation of it.

[GUIDE][20-MAY-2019]HOW TO FLASH Z010D ROMs on Z010DD (8.1 and 9.0 ROMs).

This guide is specifically aimed for Z010DD users who want to flash custom ROMs:​If you want to stay on stock and only wanna flash TWRP and root the Stock ROM, please skip this thread and refer to @jide1 's guide here instead: https://forum.xda-developers.com/as...ot-asus-zenfone-max-zc550kl-qualcomm-t3652518​
Things to be noted beforehand:
1. Make sure you are on the latest/final stock rom/firmware
2. Need Unlocked bootloader (Linked below, install the apk and follow the steps)
3. Take backup of all of your data from the internal storage. (To avoid depression if accidentally wiped your precious data)
4. Minimal ADB and Fastboot (Thread Linked below, Download from there and follow on-screen steps).
Steps:
A. To flash TWRP:
1. Once you have unlocked the bootloader, download 'minimal adb and fastboot zip' and PBRP zip(extract img from it).
2. Boot into fastboot by switching off the device, then POWER + VOLUME 'UP'. (You'll enter CSC ode screen, which is fastboot so don't worry)
3. Place the recovery image into the fastboot folder and open a command window there.
4. Connect your device, then type 'fastboot devices' and Enter, just to verify if your device is shown.
5. type: fastboot flash recovery recoveryname.img
THE NEXT STEP IS IMPORTANT, Pay Attention.
6. Now REBOOT Directly to twrp by holding POWER + VOLUME 'DOWN'. Don't boot into system else stock recovery will get restored.
B. Preparing for Flashing ROMs:
Once you have booted to twrp successfully, you will need to 'format' all the partitions, which includes:
System, Data, Cache, Dalvik/ART Cache, & Internal Storage.
HERE YOU WILL LOSE ALL OF YOUR DATA, YOU HAVE BEEN WARNED ALREADY SO, yeah.
Click to expand...
Click to collapse
1. In TWRP, go to WIPE -> ADVANCED WIPE;
2. Select the above listed partitions and then SWIPE TO WIPE.
Note: You will notice a partition called 'ASDF' ,wipe/skip, doesn't matter.
3. Come back to home, go to REBOOT -> RECOVERY
C. Flashing ROMs:
1. Download the ROM, Patch, and Kernel zip (Linked Below).
2. Flash them in the mentioned order.
3. Flash Opengapps (if needed) (Nano Gapps recomended).
4. Reboot.
(NOTE: FOR MAGISK, FLASH IT 'AFTER FIRST BOOT ONLY', AND IF FLASHING ZIP NOT WORKING, THEN see POST #3)
Bugs and Notes:
1. Notification LED doesn't BLINK when a notification arrives, it stays on (colors are correct though).
2. VoLTE is broken on pie roms (ignore the volte logo), stick to Oreo if you want VoLTE. (LTE data works fine).
3. Reboot Sometimes get stuck in black screen, its RANDOM, LONG Press the power button for 15 secs instead if that happens.
4. If any ROM contains 'Always On' functionality, disable it as the feature doesn't work properly. (Ambient display has no issues)
Links: Refer POST #2 .
Credits:
@SakilMondal for roms.
@YaAlex for kernel and patch for Z010DD.
Myself for testing.
Created 2019-04-22
Last Updated 2019-05-20

Links:
ROMs: https://sourceforge.net/projects/zenfone-max-updates/files/Z010D/ (Please flash the latest ones only, don't use old ones)
Patch (link updated): https://anonymousfiles.io/3WLplRtD/
Kernel (link updated + new kernel update): https://anonymousfiles.io/m4oKP6wL/
TWRP Recovery (Image file, Flash via fastboot): https://drive.google.com/file/d/1txHT0vRNo0gTMkD0Sb5kpuQQT0dAiphH/view
ASUS Official Bootloader Unlock Tool for 8939 Devices: http://dlcdnet.asus.com/pub/ASUS/Ze...513.74708998.1502054577-2083321676.1502054577
Minimal ADB and Fastboot: https://forum.xda-developers.com/showthread.php?t=2317790

Troubleshooting:
Instructions for Magisk:
1. Extract boot image from the rom zip
2. Go to Magisk Manager app
3. Tap 'Install' next to 'Magisk is not installed' line.
4. Tap 'Select and patch a file'
5. Navigate to the extracted boot image. It will now create a new boot image and save it in mentioned location.
6. Reboot to recovery, Flash the Boot image + KERNEL zip.
7. Reboot to system.
To fix CTS Mismatch in Magisk:
Open /system/build.prop, replace the line 'ro.build.fingerprint=' with:
Code:
ro.build.fingerprint=asus/WW_Phone/ASUS_Z010_2:6.0.1/MMB29P/13.8.26.80-20161230:user/release-keys
Open /system/vendor/build.prop , replace the line 'ro.vendor.build.fingerprint=' with:
Code:
ro.vendor.build.fingerprint=asus/WW_Phone/ASUS_Z010_2:6.0.1/MMB29P/13.8.26.80-20161230:user/release-keys

Patch is required for sd410 devices??

koushik99 said:
Patch is required for sd410 devices??
Click to expand...
Click to collapse
Nope, patch is only for DD.

Guide has been updated. Please check.

unable to flash GAPPS
Hai , i got a problem , phone shutdowns after flashing GAPPS (opengapps) , i tried Many RAMS(DOT OS, lineage-16.0-20190514-Z010D, BootleggersROM-Pie4Z010D.4.1-Stable-Unshishufied-20190421-170442 ,RR-P-v7.0.2-20190505-Z010D-Unofficial ) , without GAPPS Flashing it is , ROM working good , please let us know how to fl

I cant turn off the phone with pie,
i need to go in recovery first to power off otherwise after a while it turns back on
is it a known bug?

PRASAD.ASRS said:
Hai , i got a problem , phone shutdowns after flashing GAPPS (opengapps) , i tried Many RAMS(DOT OS, lineage-16.0-20190514-Z010D, BootleggersROM-Pie4Z010D.4.1-Stable-Unshishufied-20190421-170442 ,RR-P-v7.0.2-20190505-Z010D-Unofficial ) , without GAPPS Flashing it is , ROM working good , please let us know how to fl
Click to expand...
Click to collapse
Looks like you're using aroma gapps..
Use micro gapps or below. Here everything works fine.

ihatebarrels said:
I cant turn off the phone with pie,
i need to go in recovery first to power off otherwise after a while it turns back on
is it a known bug?
Click to expand...
Click to collapse
In both oreo and pie, for both z010d and dd, reboot and shutdown is an issue
It doesn't happen everytime, its random, and no fix is found yet.

Is it working on asus zenfone max 2016 sd 615?

Can anyone give me the updated link for the dd-fix-r5.zip and GUNMetal-R3.zip files

james_imch said:
Can anyone give me the updated link for the dd-fix-r5.zip and GUNMetal-R3.zip files
Click to expand...
Click to collapse
I just saw that the link was no longer working (would have been better if you pointed out that first instead)
Anyways,
Link is updated, check again (kernel is updated,patch remains the same).

Kaustav365 said:
Is it working on asus zenfone max 2016 sd 615?
Click to expand...
Click to collapse
Hope you have read the OP properly
This thread is only for sd615/Z010DD/MSM8939, and its clearly mentioned.

TechNova said:
I just saw that the link was no longer working (would have been better if you pointed out that first instead)
Anyways,
Link is updated, check again (kernel is updated,patch remains the same).
Click to expand...
Click to collapse
PBRP Recovery (flashable zip) link is also not working. Please update it.

james_imch said:
PBRP Recovery (flashable zip) link is also not working. Please update it.
Click to expand...
Click to collapse
Done,
Removed pbrp and now Twrp link posted.

TechNova said:
Looks like you're using aroma gapps..
Use micro gapps or below. Here everything works fine.
Click to expand...
Click to collapse
Hey! I am also facing the same issue. I tried the nano version of Gapps on my Asus Zenfone Max Z010D and my phone is still crashing it keeps restarting and then automatically turns off. Is there any issue to fix this?

unable to flash roms it shows up no digest found or invalid zip or update error 7
please help how do i find correct rom for sd615 8939

Eric0000 said:
unable to flash roms it shows up no digest found or invalid zip or update error 7
please help how do i find correct rom for sd615 8939
Click to expand...
Click to collapse
I too facing same problem

Unlocking the apk no longer works

[ROOT] Galaxy J810x Methods Magisk And Twrp

[ROOT] Galaxy J810x Methods Magisk And Twrp
[ROOT Normaly]
1. Download Stock ROM 9.x or upgrade normaly
2. Start your ROM enter configuration, developer options and set Unlock by OEM
3. Download Odin 3.14 and drivers
4. Download Magisk and TWRP 3.3.0 and no-verity-opt-encrypt-6.1.zip
5. Install drivers for J7
6. Copy Magisk and no-verity-opt-encrypt-6.1.zip to SD Card
7. Enter in Stock Recovery and Factory reset
[Download MODE]
8. After this enter in download mode imediatly or your system encrypt
9. no start your stock rom or your system encrypt
10. Open Odin 3.14 flash Stock Bootloader and Modem Only If necessary
11. Flash TWRP with Odin or upgrade via img
12. Reboot imediatly in Recovery
13. Flash Magisk 20
14. Flash no-verity-opt-encrypt-6.1.zip
15. iNTALL your prefered Custom ROM
16. Install Magisk Manager 7.5
17. Press Thanks please
18. in this moment install Havoc or Lineage 17.1
[mAgisk mEthod]
You will need the stock Rom files from Sammobile for your phone model(BL, AP, CP, HOME CSC) and Odin on your PC.
1. Install Magisk manager on your phone.
2 Copy the AP file on your Download folder of your phone.
3 Open Magisk and tap Install Magisk then Select and patch a file. Go on Download folder and select the AP file to patch. After is done it will create a file in your Download folder named magisk_patched.tar. Copy this file back on your PC.
4 Run Odin and put your phone on Download mode. To get in Download mode shut your phone off, Hold pressed VOLUME UP + POWER, select Reboot to bootloader.
5 In Odin select BL, CP and Home_CSC from your stock ROM folder. In AP select the magisk_patched.tar file. Go on Optons and uncheck Auto Reboot. Hit START and let him finish. IMPORTANT, READ FIRST : After is done you have to restart the phone by pressing VOLUME DOWN + POWER and when the screen is black immediately press VOLUME UP + POWER. Dont let go until you are in Recovery mode, even if restarts.
5 select Wipe data/ factory reset and then Reboot system now. Might take a while to boot.
6 Set up your phone and install Magisk Manager again. It will ask you to complete the rooting will need to install few more files. Press OK.
WELL DONE. You have root now.
[RECOVERY][UNOFFICIAL]TWRP 3.3.1-0 Galaxy J8 J810M/F/FN/G/DS
https://forum.xda-developers.com/an...overy-twrp-3-3-1-0-galaxy-j8-j810m-f-t3962423
[Magisk 20.4] Primary option
https://github.com/topjohnwu/Magisk/releases/download/v20.4/Magisk-v20.4.zip
[Manager 7.5.2]
https://www.apkmirror.com/apk/topjohnwu/magisk-manager/magisk-manager-7-5-2-1e2de1bb-release/
[no-verity-opt-encrypt-6.1.zip]
https://build.nethunter.com/android-tools/no-verity-opt-encrypt/
[Official]
Magisk Official Post
https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445
[RMM State Fix] Miracle box
https://forum.xda-developers.com/ga...-rmm-fix-oreo-8-1-oem-unlock-fix-dez-t3877764
The Secret Of My Seccess is Jesus​

Since you mentioned custom ROMs in the first guide, have you found any that are compatible with the J8? If so, could you link them?
Edit: Found a port of LineageOS 16 (Android 9.0) by the developer Bad Guy. However I couldn't get TWRP to flash it as it always resulted in error 7, despite modifying the file to remove the assert section. The no-verity-opt-encrypt-6.1.zip would not flash either due to error 1.

Someonerandom said:
Since you mentioned custom ROMs in the first guide, have you found any that are compatible with the J8? If so, could you link them?
Edit: Found a port of LineageOS 16 (Android 9.0) by the developer Bad Guy. However I couldn't get TWRP to flash it as it always resulted in error 7, despite modifying the file to remove the assert section. The no-verity-opt-encrypt-6.1.zip would not flash either due to error 1.
Click to expand...
Click to collapse
Hello my friend
technically j8 has a native treble and means that any treble ROM can be installed on the j8 with a custom kernel
If You have time test this ROM
https://forum.xda-developers.com/ga...om-crdroid-6-3-android-q-10-0-galaxy-t4048917
You need Kernel Android 10
Remember backup your files
Unlock oem and USB debugg

hacker812c said:
Hello my friend
technically j8 has a native treble and means that any treble ROM can be installed on the j8 with a custom kernel
If You have time test this ROM
https://forum.xda-developers.com/ga...om-crdroid-6-3-android-q-10-0-galaxy-t4048917
You need Kernel Android 10
Remember backup your files
Unlock oem and USB debugg
Click to expand...
Click to collapse
I have taken a look at your ROM, however I don't think it would work.
The ROM is ARM64, and the Galaxy J8 is an ARM device with a 64-bit binder. This means that the ROM needs to have that architecture to work.
It also requires Spaget X which is built for Exynos, and the J8 is a Snapdragon device.
And on another note, do you happen to know the fix for error 1 on the disable forced encryption zip?

Someonerandom said:
I have taken a look at your ROM, however I don't think it would work.
The ROM is ARM64, and the Galaxy J8 is an ARM device with a 64-bit binder. This means that the ROM needs to have that architecture to work.
It also requires Spaget X which is built for Exynos, and the J8 is a Snapdragon device.
And on another note, do you happen to know the fix for error 1 on the disable forced encryption zip?
Click to expand...
Click to collapse
Yes
If j8 use custom kernel 10
You install any release treble
I have release arm and arm64

Can i do that with android 8?

J810F android 8 or 10 working ???