Database Users

[OFFICIAL] Japanese SGS III (SC-03E) Rooting, ROMs, Kernels & Guides

DISCLAIMER: You will be flashing your phone at your own risk. You are solely responsible for anything you do to your phone, so make sure you are well informed and well prepared before deciding to flash or install anything on your device.
The purpose of this thread is to provide a 'reference site' for anything related to ROMs and kernels, be it original stock, modified stock or custom images for the Samsung Galaxy S III Japanese versions, starting with model SC-03E.
All comments and feedback are welcome and appreciated.
Reminders:
After flashing a new ROM image, it is highly recommended to perform a cache wipe and factory reset. Please avoid posting about problems repeatedly which can be easily solved by this procedure.
If you find that someone has been helpful in assisting you, then please do not shy away from hitting the THANKS button below their post; this is the preferred action instead of creating a new post just to show your gratitude
BEFORE ASKING HOW TO DO SOMETHING, READ THIS GUIDE
Some questions are being asked over and over again in this thread without bothering to read through it or looking for the answer here in the OP. Especially for the 'lazy' ones among us, we'll attempt to make a new and fresh, additional, reference pointer right here at the top of the very first post. Please consider taking a look at @lparryU's guide BEFORE posting your next question.
"How-to: Root, Unlock, Enable Osaifu Keitai/Felica, CWM, cook & flash custom ROM for SC-03E"
PIT File
Use this PIT file when flashing with Odin, and ONLY if you have scr*wed up your default partitioning scheme due to specifying an incorrect one during a previous flash. Normally there is NO NEED to specify a PIT file when flashing with Odin!
m3.pit (SC-03E)
Factory Firmware (stock)
samsung-updates.com and www.sammobile.com host some of the stock images.
Due to hotfile.com's demise, and my limited storage and bandwidth resources in my mediafire subscription, stock images will be available on demand only. Sorry for the inconvenience.
Pre Rooted stock ROMs
(Flashing the following ROM components will trigger the custom binary counter)
All the rooters contain a sample debloat script as well. it is located in the file /preload/Proxyme/debloat.sample. If your /sdcard already has an older debloat script in /sdcard/Proxyme/debloat.sh, it will not be overwritten by the rooter (in case you made changes to it for an older rom). So to be sure of using the most recent script for the targeted version of the firmware check the version in the /preload/Proxyme location. As a reminder, you can execute the debloat script (or any other one) from within Proxyme WITHOUT enabling SU, because it will always run in an environment with elevated privileges.
Jelly Bean 4.3
SC03EOMUBNH2 (Proxyme) (Build Date 2014-08-19)
This zip archive contains an Odin flashable file. It is not the complete stock image, so you MUST have OMUBNH2 already running on your phone or you will need to download it from the above reference sites, which carry complete stock firmware images, and flash it before continuing with this file. Instructions are included.
mediafire
uploaded.net
torrent, mirror2
(Flashing these ROMs will NOT trigger the custom binary counter)
Jelly Bean 4.3
XXUENE4 GT-I9305 Based (Proxyme) (Build Date 2014-05-16)
This image will clear data/cache implicitly upon initial boot, so backup your stuff before flashing
This one includes the Samsung Chinese IME with support for full screen handwriting and the QUERTY layout with extra row of numerical keys at the top
torrent, mirror1, mirror2
mega.co.nz
uploaded.net
SC03EOMUBND2 (Proxyme) (Build Date 2014-04-02)
This image will not clear data, but please consider wiping data/cache manually before posting about issues not related to Proxyme
mega.co.nz
torrent, mirror1, mirror2
(Unpack the .tar.md5 file from any one of the following (multipart) zip archive and flash with Odin)
SC03EOMUBND2_PROXYME20140419.z01
SC03EOMUBND2_PROXYME20140419.zip
Jelly Bean 4.1.2
MI4 GT-I9305(TGY) Based (Build Date 2013-09-26)
Rooting instructions are displayed in RootInfo app
Wipe Data/Cache if you are experiencing problems.
Display Languages: English(UK/US), Chinese(Trad/Simpl) and Korean
Input: Samsung Chinese IME (English/Chinese-TW/Chinese-HK/Chinese/Korean), Standard Samsung IME (en_GB;en_US;az;ca;cs;da;de;et;es;eu;el;fr;gl;ka;hr;it;is;kk;lv;lt;hu;nb;nl;pl;pt;ru;ro;fi;sr;sk;sl;sv;tr;uk;ko;hy;bg;zh_CN)
mediafire (unpack tar.md5 file from this multipart zip archive and flash with Odin)
MR8 GT-I9305(TNL) Based (Build Date 2013-09-26)
Rooting instructions are displayed in RootInfo app
Wipe Data/Cache if you are experiencing problems.
Display Languages: (en_GB;en_US;en_AU;en_IE;en_NZ;en_ZA;ko_KR;de_AT;de_CH;de_DE;fr_FR;fr_CH;bg_BG;cs_CZ;da_DK;el_GR;es_ES;et_EE;fi_FI;ga_IE;hr_HR;hu_HU;is_IS;it_IT;lt_LT;lv_LV;mk_MK;nb_NO;nl_NL;nl_BE;pl_PL;pt_PT;ro_RO;sr_RS;sv_SE;tr_TR;ca_ES;eu_ES;gl_ES;kk_KZ;ru_RU;sk_SK; sl_SI; uk_UA; uz_UZ; az_AZ; hy_AM; ka_GE; es_US; pt_BR; ar_AE;zh_CN;zh_TW;ja_JP)
Input: Samsung Chinese IME (English/Chinese-TW/Chinese-HK/Chinese/Korean), Standard Samsung IME (en_GB;en_US;az;ca;cs;da;de;et;es;eu;el;fr;gl;ka;hr;it;is;kk;lv;lt;hu;nb;nl;pl;pt;ru;ro;fi;sr;sk;sl;sv;tr;uk;ko;hy;bg)
mediafire (unpack tar.md5 file from this multipart zip archive and flash with Odin)
MG3 GT-I9305(SFR) Based (Build Date 2013-07-31)
To toggle root/unroot, boot the phone and then press VolumeUp/VolumeDown/Power simultaneously for a brief moment.
This toggle only works if you enable Settings->Developer Options->USB Debugging
Data and cache are wiped, so backup your data prior to flashing with Odin.
Display Languages: (en_GB;en_US;en_AU;en_IE;en_NZ;en_ZA;ko_KR;de_AT;de_CH;de_DE;fr_FR;fr_CH;bg_BG;cs_CZ;da_DK;el_GR;es_ES;et_EE;fi_FI;ga_IE;hr_HR;hu_HU;is_IS;it_IT;lt_LT;lv_LV;mk_MK;nb_NO;nl_NL;nl_BE;pl_PL;pt_PT;ro_RO;sr_RS;sv_SE;tr_TR;ca_ES;eu_ES;gl_ES;kk_KZ;ru_RU;sk_SK; sl_SI; uk_UA; uz_UZ;az_AZ; hy_AM; ka_GE;es_US; pt_BR; ar_AE)
Input: Samsung Chinese IME (English/Chinese-TW/Chinese-HK/Chinese/Korean), Standard Samsung IME (en_GB;en_US;az;ca;cs;da;de;et;es;eu;el;fr;gl;ka;hr;it;is;kk;lv;lt;hu;nb;nl;pl;pt;ru;ro;fi;sr;sk;sl;sv;tr;uk;ko;hy;bg)
mediafire (unpack tar.md5 file from this multipart zip archive and flash with Odin)
Jelly Bean 4.1.1
SC03EOMAMJ4 ( 2013-10-18 )
Depending on what's running on your phone currently, you may have to consider performing a manual factory reset and wipe the cache and data partitions.
Rooting Instructions:
Default state is - not rooted - Proxyme has been included in this rom,
Proxyme offers live su binary control, and without the need to 'root' the phone, you have...
- SSH server with virtually unlimited user accounts, configurable with specific UID, GID, home directory and shell,
- execution of scripts with elevated privileges (sample debloating script included),
- tag along scripts for root ON and root OFF actions,
- busybox switch
(Unpack the .tar.md5 file from any one of the following zip archive and flash with Odin)
torrent - full stock root ready (Proxyme)
Uploaded.net - full stock root ready (Proxyme)
MF1 (Build Date 2013-06-10)
To toggle root/unroot, boot the phone and then press VolumeUp/VolumeDown/Power simultaneously for a brief moment.
This toggle only works if you enable Settings->Developer Options->USB Debugging
mediafire (unpack tar.md5 file from this multi-part zip archive and flash with Odin)
MC3 (Build Date 2013-03-18)
Courtesy aki0306...
http://forum.xda-developers.com/showpost.php?p=38739961&postcount=8
MB1 (Build Date 2013-02-08)
To toggle root/unroot, boot the phone and then press VolumeUp/VolumeDown/Power simultaneously for a brief moment.
This toggle only works if you enable Settings->Developer Options->USB Debugging
Chainfire's SuperSU has been included for your convenience.
hotfile - link dead (unpack tar.md5 file from this zip archive and flash with Odin)
.
Courtesy aki0306...
http://forum.xda-developers.com/showpost.php?p=38739961&postcount=8
MA6 (Build Date 2013-01-24)
Courtesy aki0306...
http://forum.xda-developers.com/showpost.php?p=38739961&postcount=8
Custom ROMs
(Flashing these ROMs COULD (and usually will) trigger the custom counter)
Probam Rom
Go to this post... and this post... Courtesy @sasbudi
Slimbean 4.3 NTT Docomo SC-03E
Go to this post... Courtesy @majidkhan
Carbon 4.2.2 for NTT Docomo SC-03E
http://forum.xda-developers.com/showpost.php?p=45164630&postcount=550 Courtesy @majidkhan
PACman (Paranoid AOKP CyanogenMod) 4.2.2
http://forum.xda-developers.com/showpost.php?p=43996579&postcount=489 Courtesy @Edgrr000
CyanogenMod
Instructions for flashing CM10.1 Courtesy @lparryU
Getting CM10 to work on SC-03E with Osaifu-keitai... Courtesy @FlyingFlipFlop and @lparryU
http://forum.xda-developers.com/showpost.php?p=42076531&postcount=313
http://forum.xda-developers.com/showpost.php?p=42076531&postcount=302
http://forum.xda-developers.com/showpost.php?p=42094976&postcount=303
rXTREME.v10.0
Link to post Courtesy @Edgrr000
KBC Developers github wiki
Contains everything everyone in here needs, Samsung custom kernel, with visible hidden partition for using triangle away on stock rooted,
and having all Japanese things working too. And the cm10.1 links. Its in Japanese but easily translated. (courtesy of @Robobob1221)
https://github.com/kbc-developers/release/wiki
Paranoid Android (GT-I9305)
Link to post Courtesy @Edgrr000
Misc
How to Convert ROMs for the SC-03E By @DroidZombie
Japanized Rom Tool By @LeathSeraph
http://lt.imobile.com.cn/forum.php?mod=viewthread&tid=10282917
Hints & Tips
Follow this trail...

SC-03E Hints & Tips
Hints & Tips
Guides.. with several links and specifically for unlocking your phone with the proper ROM (has the LK5 modem which is the go to for unlocking and working with other carriers), and instructions to do just about everything you need to get done with this phone
How to Convert ROMs for the SC-03E (By @DroidZombie)
Instructions for flashing CyanogenMod ROMs (By @lparryU)
Unlocking
Unlocking Guide - Courtesy of XDA member @majin
Yet Another Unlocking Guide
Custom Binary Counter
.Reset Guide .By @majin
Tethering
Tethering Guide By @majin
How to change Tethering preset APN By @majin
Change Roaming Status
Reference post By @majin
Proxyme Rooting
Proxyme Guide
Fixing Lost IMEI
How to repair your SC-03E's IMEI number and restore its network connection
Miscellaneous
SC-03E Dial Pad Codes

SC-03E Docomo S3 LTE - Just Another Unlocking Guide
This (sim) unlocking guide has been primarily inspired by the very comprehensive guide initially written and posted by @majin in his post.
WARNING: This unlock procedure will automatically wipe the phone's cache and data partitions, effectively performing a factory reset; you are strongly advised to backup your data prior to executing this guide.
Prerequisites:
Windows PC running Odin3 in an administrator account (tested with Odin3 v3.07)
USB cable to connect phone to PC (preferably original cable for reliability)
Internet access to download firmware image(s)
Google account to access Play Store
The following list outlines the required steps in order to successfully unlock your SC-03E:
If you have data on the phone, which is of any importance to you, then I highly recommend that you make appropriate backups first
If present, remove the sim card and sdcard (there's no need to have a Docomo sim card for this procedure to work)
Download this stock firmware image, which is based on MB1 and includes the appropriate modem component to assist in wiping the NV stored network locking data structures. In addition, this firmware image is root-ready; meaning that you can toggle root mode by pressing VolumeUp/VolumeDown/Power button combination briefly to switch modes.
Initiate Odin Download mode on the SC-03E (Turn the phone off, then simultaneously press VolumeDown/Home/Power buttons until the Download Mode splash screen appears and requires you to press VolumeUp to continue or VolumeDown to cancel if you find yourself suddenly struck by an overwhelming feeling of stage-fright)
Unpack the SC03EOMAMB1_LK5MDM.tar.md5 firmware image from the above-mentioned/downloaded zip archive and flash the file with Odin3 (specify the image file in Odin's PDA section)
As soon as Odin completes the flashing process, it will instruct the phone to reset; be patient while the phone starts up, because it will require more time to setup and configure itself after a factory reset.
If you have reached this step, then we're assuming the phone has booted successfully and you are presented with the configuration wizard. You need to at least enter your Google account credentials in order to access the Play Store.
Install the (free) ServiceMode Shortcut app (author: KABASOFT) from the Play Store.
Another (paid) option is the ShowServiceMode For Galaxy LTE app (author: Jaken's Laboratory).
Start the service mode app and tap the ServiceMode option, which will in turn fire up the ServiceMode main menu
Select [1]UMTS->[1]DEBUG SCREEN->[8]PHONE CONTROL->[6]NETWORK LOCK->[3]PERSO SHA256 OFF
Now use the phone's android menu soft button to select Back in the popup menu to return to the NETWORK LOCK menu
Tap [4]NW LOCK NV DATA INITIALLIZ and wait for about a minute before returning to the NETWORK LOCK menu; when you tap this option again, it should state PERSO_NV_INIT is SUCCESSFUL
You may now power off the phone to insert a sim card from your favorite telco operator and restart the phone
From this point onward, it is possible to flash any other firmware image without affecting the unlocked state
Enjoy!

SC-03E Dial Pad Codes
This list is most probably not complete. Please post or send a PM if you know about codes not listed here, your input will be highly appreciated!
*#0*# ........................... Hardware Testing
*#06# .......................... Show IMEI number
*#0011# ....................... GSM Status Information
*#0228# ....................... Battery Status
*#0782# ....................... RTCTimeRead (Show Time)
*#1111# ....................... ServiceMode - READ FTA SW VERSION
*#1234# ....................... Show Software Version
*#2222# ....................... ServiceMode - READ FTA HW VERSION
*#2663# ....................... Touch Screen/Key Firmware Update
*#7284# ....................... PhoneUtil - UART & USB Configuration
*#7353# ....................... Quick Test
*#7594# ....................... Factory Mode - Shutdown Configuration
*#9090# ....................... ServiceMode - DIAG CONFIG
*#9900# ....................... SysDump
*#34971539# ................ Camera Firmware Check

IMEI Repair Procedure
How to repair your SC-03E's IMEI number and restore its network connection.
Keywords: IMEI: null/null Unknown + Baseband: Unknown + no connection with QPST + no IMEI backup + phone signal lost
Disclaimer
This procedure is intended to be applied in a last resort scenario only. You must check thoroughly what the actual cause is for your phone having lost its imei number. It may very well be merely due to an incompatibility issue between the baseband code and the efs version, and thus easily fixed by flashing a proper modem component. Writing to partitions in your phone's internal storage device, re-partitioning it, flashing with the Odin tool or operating the QPST Qualcomm engineering tool carries many risks, which include hard-bricking the phone. You are solely responsible for anything you do to your phone and by carrying out the steps detailed in this procedure, you are agreeing to accept all responsibility for any and all outcome of the procedure, even if you end up with an expensive door-stop.
Try This First
Before panicking and diving into this procedure to perform all of its steps, note that your specific problem/case might not require such an extensive procedure. There could very well be a much simpler solution for your case, so I strongly advise you to put some effort into diagnosing your problem properly (best as you can given the resources you have at your disposal) BEFORE continuing.
I will be adding topics to this section based on the feedback we get, which will hopefully help everyone to improve diagnostics and find out if there are quicker/better way to solve any specific case.
BASEBAND UNKNOWN (Courtesy of @majin)
About the devices with "BASEBAND UNKNOWN" not recognized by QSPT, for first users should try with one of these:
1) enter *#9090# and check if "[2] DM/DUN over HSIC (*)" is selected, then to try to use QSPT to fix/restore the IMEI/EFS-folder, (if users have some old working backup too).
3) Try to use EFS Professional Suite to restore the right permissions on the NV files.
4) Use "Qualcomm NV Tools" (included in "EFS Professional Suite") to write directly their IMEI and to do some other test.
If they can't anything of that, then they really need to make all the "Chinese steps".
Click to expand...
Click to collapse
Introduction
This procedure is based on the following two posts, which are identical content-wise, and may be from the same individual. Credit goes to user xt890612 of forum site bbs.shendu.com and user softbank_1001 of forum site bbs.91dongji.com. Special thanks to xda member @majin for the find/input/feedback and having tested the procedure on his SC-03E.
- bbs.91dongji.com
- bbs.shendu.com
The issues we will attempt to resolve are:
IMEI corrupt or 0
Baseband Unknown status
QPST does not recognize the phone
What to Expect
If the procedure has been followed correctly and applied successfully, then take note of the following points.
IMEI restored
Network connection restored
Device serial number not the same as your original one (we will try to resolve this in the future)
No SIM network lock (Do not apply this procedure if you only want to SIM unlock a device with no issues)
You should be feeling happy, so please lookup the sources mentioned above and thank them
Preparations & Prerequisites
You will need the following tools and files, so please check each item in the list below and make sure you have them ready before commencing with the first step of the procedure.
An SC-03E which can at the very least boot into Odin Download Mode (soft-bricked). If the bootloader is corrupt, you will need some kind of JTAG service to revive the phone, because this procedure will not help your case.
Windows PC
Odin v3 (preferably Odin3 v3.09 or v3.07) - Google is your best friend
Google QPST.2.7.378.zip and download this Qualcomm engineering tool. Install it on the PC.
ADB tool/program. ADB, Android Debug Bridge, is included with Google’s Android SDK.
Hex editor. Google 'Hex editor' and download your preferred or favourite variant. Try HexEdit.exe.
Download SC-03E_IMEI-REPAIR.ZIP (mirror, torrent) and unpack the files in this archive to a work directory
Download one of the pre-rooted or root ready rom images, which are still functional/bootable on your phone, from the OP/reference post (this item is only required if your phone does not boot into Android at all, even after resetting it, and is not rooted)
Step 1 - Flash a Bootable Rooted ROM Image
If your phone currently has firmware, which boots properly and can give you root access, then skip this step. If not, then use Odin to flash the rooted image you have downloaded earlier. Consider resetting the phone afterwards by entering recovery mode to clear data and cache.
Step 2 - Enable USB Debugging
Enable USB debugging by setting the checkmark in the following option in settings:
Settings->Developer options->USB Debugging
Step 3 - Connect the Phone
If necessary, wait for all PC drivers to install and initialize.
Step 4 - Prepare Phone Internal Storage
Copy all 15 mmcblk* files, which were unpacked from the SC-03E_IMEI-REPAIR.ZIP zip archive earlier, to the phone's internal sd card after connecting it to the PC. The files must be located in the root of folder /sdcard.
It is important that you consider verifying data integrity of the mmcblk* files you have copied to the phone. Root Browser is recommended and can assist in this process. The following list consists of the MD5 checksums generated for the files in the SC-03E_IMEI-REPAIR.ZIP zip archive.
b5cfa9d6c8febd618f91ac2843d50a1c *mmcblk0p1
30fd6dfc09a70c8bcf345dc8c9e2781a *mmcblk0p10
c71fb4dfba643299159b97c6065fdb54 *mmcblk0p11
95557d70252c9b0af3f95a2244cd93ab *mmcblk0p12
e35b35efb73dd8320bdae08ec463372c *mmcblk0p13
31bc9037b092df1abbcf7550938d553d *mmcblk0p14
96995b58d4cbf6aaa9041b4f00c7f6ae *mmcblk0p15
b5cfa9d6c8febd618f91ac2843d50a1c *mmcblk0p2
dbad1316e91f5dcf0b89ad3e456f3bf8 *mmcblk0p3
713a67b9605c02f6cdd0346dfa1cab1e *mmcblk0p4
130715b90924c2394e1acd758059dd90 *mmcblk0p5
4029a1de061c375547aa3096a14562dc *mmcblk0p6
67bb0d7fbec2e250c5e2bd75dd9816f3 *mmcblk0p7
9e4a4230f51545ffd352cb7988f4bc9f *mmcblk0p8
edc27dbf0cc8b29df3ba31e21b552a98 *mmcblk0p9
4459508535b3c064f6afc6d1c6119b9e *sc03e.qcn
Step 5 - ADB
Now open a cmd window and start the ADB tool by typing the following command at the cmd prompt, followed by the enter key. In many cases, you will first have to cd (change directory) to the directory where the adb.exe program is located (hint, if you've installed the Android SDK, look for the location where it was installed and search its subdirectories for adb.exe):
>adb shell
If the shell in the adb session starts successfully, the following prompt is presented:
[email protected]:/ $
Type su followed by the enter key to get root access. If the $ sign in the prompt does not change in a # sign, then you have no access to root and you should revert back to step 1 to make sure you have a rooted firmware image on the phone.
[email protected]:/ $su <enter>
[email protected]:/ #
Step 6 - Restore Partitions
This step must be taken with great caution. You will be directly writing to partitions in the internal storage device and a mistake can end in disaster. Copy the following lines, each terminated by the enter key to initiate the command. Note that the lines with mmcblk0p10 to p14 can take a long (5 minutes or more) time to complete, so be patient.
dd if=/sdcard/mmcblk0p1 of=/dev/block/mmcblk0p1 <enter>
dd if=/sdcard/mmcblk0p2 of=/dev/block/mmcblk0p2 <enter>
dd if=/sdcard/mmcblk0p3 of=/dev/block/mmcblk0p3 <enter>
dd if=/sdcard/mmcblk0p4 of=/dev/block/mmcblk0p4 <enter>
dd if=/sdcard/mmcblk0p5 of=/dev/block/mmcblk0p5 <enter>
dd if=/sdcard/mmcblk0p6 of=/dev/block/mmcblk0p6 <enter>
dd if=/sdcard/mmcblk0p7 of=/dev/block/mmcblk0p7 <enter>
dd if=/sdcard/mmcblk0p8 of=/dev/block/mmcblk0p8 <enter>
dd if=/sdcard/mmcblk0p9 of=/dev/block/mmcblk0p9 <enter>
dd if=/sdcard/mmcblk0p10 of=/dev/block/mmcblk0p10 <enter>
dd if=/sdcard/mmcblk0p11 of=/dev/block/mmcblk0p11 <enter>
dd if=/sdcard/mmcblk0p12 of=/dev/block/mmcblk0p12 <enter>
dd if=/sdcard/mmcblk0p13 of=/dev/block/mmcblk0p13 <enter>
dd if=/sdcard/mmcblk0p14 of=/dev/block/mmcblk0p14 <enter>
dd if=/sdcard/mmcblk0p15 of=/dev/block/mmcblk0p15 <enter>
Close the cmd window and restart the phone. If the phone does not boot into Android (could be bootlooping due to incompatible data elements), then perform a reset in recovery mode by wiping data and cache.
At this point you should confirm that the baseband has been restored in settings.
Step 7 - Restoring IMEI
Get ready to make changes to the sc03e.qcn file, which was unpacked from the
SC-03E_IMEI-REPAIR.ZIP zip archive earlier, using the hex editor.
Load the sc03e.qcn file in a hex editor and search for the following hexadecimal byte value sequence:
08 0A 21 43 65 87 09 21 43
The file contains two instances of the sequence as is shown above. Both sequences must be changed to your IMEI number and the way it is done is outlined below.
Note that when searching for the above sequence, in most hex editors you are supposed to also specify the search type, whether it be a text search or byte (binary search. You want the latter type.
Start with looking up your device's IMEI number. It is printed on the label in the battery compartment and on a label or sticker on the original box, if you still have it. The IMEI number consists of 15 digits, so please write it on a sheet of paper in order to help you visually 'construct' a hexadecimal sequence, which in turn can be used to update both instances of the abovementioned sequence in the file. This sequence has three fixed nibble values, which must remain unchanged in the final sequence. The following sample shows x's in the sequence which represent the part to be initialised to your IMEI number. The fixed (constant) parts are the 08 and the A in xA.
08 xA xx xx xx xx xx xx xx
In order to correctly fit your 15 digit IMEI number into the sequence, use the following guide to construct it. Here, we use the dummy IMEI number 012345678901234 for reference only.
...0..12.34.56.78.90.12.34 (IMEI number to convert)
08.0A.21.43.65.87.09.21.43 (byte sequence to be constructed)
As you can see, the first digit of the IMEI number is paired with the A of the second byte in the sequence; it is placed left of the A, thus becoming the most significant nibble of the byte. The remaining digits are paired to form 7 groups in order, where each pair's digits are swapped as is shown above.
When you have finished changing the two instances of the search sequence to reflect your IMEI number, save the sc03e.qcn file, exit from the hex editor and move on to the next step.
Step 8 - Restore Configuration From QCN File
Enter the following string in the stock phone dialpad:
*#7284#
{
"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"
}
Immediately after entering the trailing # sign, as is shown in the above image, the service mode screen shown in the next image will appear.
Tap on the Qualcomm USB Settings button to display the list of USB options you can choose from. This is shown in the next image.
Select the RNDIS + DM + MODEM option followed by tapping the OK button to return to the previous screen. Now use the back button to return to the dialpad.
Next, enter the following string in the stock phone dialpad to enter the DIAG CONFIG service mode screen:
*#9090#
Immediately after entering the trailing # sign, as is shown in the above image, the service mode screen shown in the next image will appear.
Select the [2]DM/DUN over HSIC (*) option. Note that the phone will immediately reboot as soon as you tap on this option in order for it to take effect.
Let's start the QPST Configuration program in Windows and select the Ports tab to add the new port, which has been assigned to the phone's USB communication protocol. Make sure to select the port with label USB/QC Diagnostic before clicking on the OK button.
If the port has been correctly initialised and selected, SURF9615 (0) should be displayed in the Phone column of the Ports tab, as is shown in the image below.
Finally, select the Start Clients menu and navigate to the QPST Software Download item to start its corresponding program.
In the QPST Software Download program, select the Restore tab and then specify the path to the qcn file which you have edited earlier. Hit the Start button to start uploading the new configuration file to the phone. After the upload is done, reboot the phone and check the IMEI number to verify everything went ok.
Finalizing
Enter the following string in the stock phone dialpad:
*#7284#
The service mode screen appears, so again, tap on the Qualcomm USB Settings button to display the list of USB options you can choose from. To restore the default USB settings, select the RNDIS + DM + MODEM option followed by tapping the OK button to return to the previous screen. Now use the back button to return to the dialpad, or hit the home button to continue using the phone normally.
That's it...enjoy your phone!
Notes & Feedback
Serial Number (Courtesy of @majin)
About the wrong Serial Number, [between step 6 and 7] if users have still on board the Chinese Rooted ROM (or if they flashed any other correct Rooted ROM), they can easily edit the file "\efs\FactoryApp\serial_no" by the phone itself (status is 1000:0000 rwxr--r-- 744)
Then they can flash any other favorite ROM [anyway, to make all easier, I suggest some 4.1 ROM, same as the Chinese one.]
Click to expand...
Click to collapse

hey i cant posting outside url
error message
"To prevent spam on the XDA forums, ALL new users prevented from posting outside links in their messages. After approximately 10 posts, you will be able to post outside links. Thank you for understanding!"

aki0306 said:
hey i cant posting outside url
error message
"To prevent spam on the XDA forums, ALL new users prevented from posting outside links in their messages. After approximately 10 posts, you will be able to post outside links. Thank you for understanding!"
Click to expand...
Click to collapse
8 more posts to go and you're in. Why don't you head over to this thread and see if you can contribute or give feedback to any of the queries from other members. Once you get into a dialog or discussion, you'll hit that magic 10 easy.
Your message to davidcsv was also relayed to that thread, and it would help to introduce yourself to the group and gain some 'trust' wrt your firmware images.

---------- Post added 5th March 2013 at 12:46 AM ---------- Previous post was 4th March 2013 at 11:58 PM ----------
MB1 Root Rom JB4.1.1
MA6 Root Rom JB4.1.1
MC3 Root Rom Android File Host JB4.1.1
★MC3 Rom no need rename but need flash stock MC3 Rom before flash root Rom
how to flash
flash from odin
1.flash stock rom
ex if u wanna flash MB1 root, u have to flash MB1 stock Rom before flash Root Rom
2.into recovery, wipe/factory reset
3.unzip Root Rom and rename file
★you guys have to rename file when unzip root Rom★
ex SC03E-ROOTED-system_MB1.tar.md5
　　　　　　　　　　　　　↓
　　SC03E-ROOTED-system.tar.md5
4.Flash Root Rom from odin
5.boot
6.installe Supersu or Superuser on play store
cation MB1 & MA6 Root Rom is "same name of file"
thx for kbc-developers
hv fun guys!!!!
---------- Post added at 12:51 AM ---------- Previous post was at 12:46 AM ----------
Custom Rom Link
jump to china forum
this Rom on MA6 Rom

damn.. didn't know this thread existed.
I will link this to the first post in my thread and have it closed.
if you could close my thread so all the talk can go here, it would be much more beneficial/easy to keep track of things.
---------- Post added at 02:01 PM ---------- Previous post was at 01:46 PM ----------
I can confirm that the root method worked for MB1...
LETS GET THE PARTY STARTED! Seriously, I am having a drink afterwork!

lol,trying with my phone.
update result soon.
my phone is rooted now.
but still waiting for custom one that removed needless app.
"Get PIT for mapping" <-------is this dangerous?

Thank you aki0306..
Already rooted my phone..
Is there any ways to install cwm on sc03e?

skylinerxz said:
Thank you aki0306..
Already rooted my phone..
Is there any ways to install cwm on sc03e?
Click to expand...
Click to collapse
I was just going to ask this...

didoka_702 said:
lol,trying with my phone.
update result soon.
my phone is rooted now.
but still waiting for custom one that removed needless app.
"Get PIT for mapping" <-------is this dangerous?
Click to expand...
Click to collapse
Get PIT for mapping is harmless, because the flashing process with Odin is just getting the current partitioning configuration as is stored in the phone. Just stay away from the PIT options in Odin (PC).
Why don't you just remove unwanted system apps with Titanium Backup?

skylinerxz said:
Thank you aki0306..
Already rooted my phone..
Is there any ways to install cwm on sc03e?
Click to expand...
Click to collapse
Do you mean one of the CWM recovery flavors or the Android builds (like for example CM 10.x)?

davidcsv said:
Do you mean one of the CWM recovery flavors or the Android builds (like for example CM 10.x)?
Click to expand...
Click to collapse
i would like CM10.x ! + CWM recovery flavors!
you got a lab rat available for this!

davidcsv said:
Get PIT for mapping is harmless, because the flashing process with Odin is just getting the current partitioning configuration as is stored in the phone. Just stay away from the PIT options in Odin (PC).
Why don't you just remove unwanted system apps with Titanium Backup?
Click to expand...
Click to collapse
sorry.already did that with tianium backup but still not edit my post.

IparryU said:
i would like CM10.x ! + CWM recovery flavors!
you got a lab rat available for this!
Click to expand...
Click to collapse
Who wants to try CWM Touch recovery? It is embedded in the latest upload of the MB1 stock root ready firmware image. The links are available in the original post in the pre-rooted stock ROMs section.
The procedure is as usual, flash with Odin (PC). Then, when your phone has booted into Samsung's stock Android, at any moment press VolumeUp/VolumeDown/Power at the same time and only briefly. This should root the phone (install su binary) and install the CWM Touch recovery... I say 'should' because I have only been able to test this procedure on my Korean version of the S3; in this case, CWM's recovery has been adapted for the SC-03E. There's no visual or audio confirmation when you've pressed those three buttons, so check with your favorite root-requiring app or with the included SuperSU app.
IF rooting works with this image, then the difference with the one presented by aki0306/kbc-developers is that theirs will always root the phone during startup; meaning you have the convenience of always starting up in a rooted environment. This mechanism will only root it when you need it (three button press detailed above); I'm still assuming that when you reboot, each time su (root) is removed by Docomo's security measures in the boot environment... if you want no root then reboot. As soon as someone can confirm whether this new mechanism works, I can turn it into a toggle kind of switch, so you can root and unroot without having to restart the phone.

davidcsv said:
Who wants to try CWM Touch recovery? It is embedded in the latest upload of the MB1 stock root ready firmware image. The links are available in the original post in the pre-rooted stock ROMs section.
The procedure is as usual, flash with Odin (PC). Then, when your phone has booted into Samsung's stock Android, at any moment press VolumeUp/VolumeDown/Power at the same time and only briefly. This should root the phone (install su binary) and install the CWM Touch recovery... I say 'should' because I have only been able to test this procedure on my Korean version of the S3; in this case, CWM's recovery has been adapted for the SC-03E. There's no visual or audio confirmation when you've pressed those three buttons, so check with your favorite root-requiring app or with the included SuperSU app.
IF rooting works with this image, then the difference with the one presented by aki0306/kbc-developers is that theirs will always root the phone during startup; meaning you have the convenience of always starting up in a rooted environment. This mechanism will only root it when you need it (three button press detailed above); I'm still assuming that when you reboot, each time su (root) is removed by Docomo's security measures in the boot environment... if you want no root then reboot. As soon as someone can confirm whether this new mechanism works, I can turn it into a toggle kind of switch, so you can root and unroot without having to restart the phone.
Click to expand...
Click to collapse
just finish custom my phone today @@
ill try this one tomorrow
and i have already backed up my phone with
+back all user data and app with titanium back up
+back up efs folder using root explorer
+back up QCN file using EFS pro by this thread
any process i need to do after this?

didoka_702 said:
just finish custom my phone today @@
ill try this one tomorrow
and i have already backed up my phone with
+back all user data and app with titanium back up
+back up efs folder using root explorer
+back up QCN file using EFS pro by this thread
any process i need to do after this?
Click to expand...
Click to collapse
That should cover it
I use Whatsapp, so I always make a seperate backup of its database folder as well (folder /mnt/sdcard/WhatsApp)... it contains the message history and all the media that's been sent over.

so i test this one recently and here is MY result (i usually hold up down volume first and then press power button)
+first time:check with Supersu.it said cannot install SuperSU cause of SU binary is not installed.
+restart and try again,this time i installed Titanium back up.and its said that the phone isnt rooted
+restart and try again,no worked
+and at the 5th 6th time everytime i try to press volume up down power to install Su binary,the phone restart.
//so its my result.anyone esle?
//and couldnt get to recovery mode :| now i back to aki rom till the new one came out.

Root+Xposed+Busybox for Bootloader Locked Moto X ATT/VZW

Only fresh flashed bootloader locked XT1058 AT&T - ROM LPAS23.12-21.7-1, and XT1060 VZW - ROM LPAS23.12-39.7-1 are supported!
See archive content for instructions. Time to install ~20 min. If you experience problems after Android boot, like not working buttons or quick settings, wipe cache + data partitions. Don't update SuperSU (disable auto updates), it won't work. Later I'll post complete debloated ROMs with fresh SuperSU version, and simplify instructions. Be informed also, that this method doesn't give you read-write rights like unlocked bootloader. You may read and write having root-rights, but only till a restart or shutdown occurs, and every change will be undo by the Qualcomm protection (like HTC' s=on).
At the moment patch includes:
SuperSU 2.65 Free
Xposed Framework v86 (installer, modules)
Busybox 1.25.0.YDS, path /system/xbin/busybox
Download
P.S. Install only on indicated above ROM versions, and it's obvious that you must have enough theory knowledge and practical experience to make use of 9008 patch, so I'm not responsible for any consequences, etc. Greets go to: CrashXXL (method inventor), Sabissimo (our former OP), and serg_gangubas (ROM guru).
==============================================================================================
31.07.2017 - Full ROM Patch for Bootloader Locked Moto X ATT/VZW/etc
Based on the same principle, and not depend on system partition content, so it suits any bootloader locked Moto X Gen1 ATT/VZW (possibly any model, besides 1049 RepW / 1055 US Cell), but takes about 4 hours to be done - prepare for that, 100% battery level only!
This full ROM patch includes:
SuperSU 2.82 Free
Xposed Framework v87 (installer, modules)
Busybox 1.26.2, path /system/xbin/busybox
ViperFX 2.5.0.5 - sorry needs polishing, removed now (
Gallery and Camera not depend on Moto services
Gboard instead AOSP Keyboard. If it eats too much RAM, see Simple Keyboard
GAPPSes updated. Use command like adb shell pm uninstall --user 0 com.blahblah.blah to block any unwanted app or service
ES File Explorer Free Edition (a clone, you can disable and install yours )
"Jedy" gesture
AdBlock support (effect lasts till the 1st reboot yet, I'll think about make it constant). Please, choose /data/hosts instead of /system/etc/hosts
ROM debloated, but not deodexed.
Download
Instruction
Be careful, phone will be WIPED then flashed in 9008 "brick" mode (CrashXXL idea). Before you start install Moto drivers, latest RSD Lite, and fully charge the battery.
1) Download and unpack zip on С: (or any), open Python27, launch RUN_path.bat (needs to be launched only single time), install driver QHSUSB_driver.exe, and launch file _Moto.X.BootLocked.*.exe (where * - is desired ROM).
2) Go into fastboot mode, execute RUN_blbroke.bat. Screen gets black, Device Manager in Windows finds "QHSUSB_DLOAD", and installs it as "Qualcomm HS-USB QDLoader 9008 (COM*)". If it doesn't install, google for Windows driver digital signature disable.
3) Now launch RUN_root.bat, and see that patching process took start.
4) A small patch *SPEAKERS.BOOST.exe (if exists) boosts both speakers' volume.
P.S. Please, don't flash anything extra into the phone. In case of trouble, all you need is inside this folder. Just make it work.
To make "Battery OK" in fastboot use fastboot_cyclecharge.bat
Completely drained out battery causing "USB input device" needs disassembly of the phone to charge externally.
In case Titanium Backup shows error "Batch backup interrupted: insufficient free storage space", delete default backup folder, and make a new:
Titanium Backup > Menu > Preferences > Backup folder location > Storage Provider > DocumentProvider storage > Show Internal Storage > Internal Storage > Select Internal Storage > Create the folder > Use the current folder. Done!
Notes for myself: Viper, force wipe, readme.txt, volume patch, Adblock, advanced debloat

Debloated, rooted, lightweight ROM - soon! )
PUBLISHED. Sorry, took long time.

As soon as I can actually get 5.1 flashed I'll try this.
Though I'm afraid I'll have to try to go to stock and use sunshine first, still have a locked BL.
But this is great, I didn't expect root so soon.

DownTheCross said:
As soon as I can actually get 5.1 flashed I'll try this.
Though I'm afraid I'll have to try to go to stock and use sunshine first, still have a locked BL.
But this is great, I didn't expect root so soon.
Click to expand...
Click to collapse
This method is working on locked BL.

DownTheCross said:
As soon as I can actually get 5.1 flashed I'll try this.
Though I'm afraid I'll have to try to go to stock and use sunshine first, still have a locked BL.
But this is great, I didn't expect root so soon.
Click to expand...
Click to collapse
Wait wait... If you can have now possibility to unlock bootloader - go for it immediately! You will have normal FULL root-rights (SuperSU 2.49). Don't install 5.1, if you plan to unlock, because Sunshine app (25$) works only on 4.4.2 Android.
This topic is to help those AT&T users that are boot locked forever (who missed out possibility to unlock on 4.4.2 by proceed to 5.1) to give them READ-ONLY root. Yes, it's limited, but anything at least.

s5610 said:
If you can have now possibility to unlock bootloader...
Click to expand...
Click to collapse
I guess anyone on 4.4.4 today. There is no possibility to use Sunshine anymore.
Anyway spasibo za method

Ahh, if I don't have to be BL unlocked that's great lol.
I haven't read too much into the 5.1 updates or sunshine for that matter.
I've been on krypton 1.4.1 since it was released, and I haven't been able to successfully upgrade to any 5.1 roms yet.

Works great!
Works great for me on Windows 10 RTM 64-bit! Thanks a ton, I was waiting for a post like this.
I only had 3 minor hiccups:
1. RSD Lite gave me an error about "getvar", so I had to go into flashfile.xml in the ROM zip and remove the line that said getvar
2. I had to reboot to disable driver signature enforcement twice for some reason because Windows Update
3. The run-root.bat got stuck on "Executing..." because I installed the wrong driver (the correct file is qcusb.inf when installed from device manager -> browse my computer for driver software -> let me pick from a list -> all devices -> have disk)
Otherwise, everything runs just as well as KitKat, including Xposed.

Hehe got to love step 9

System Write
How can we help in getting the system write to zero using the same method,because I have xt1058 model bootloader unlocked and I provide any file needed to disable the pesky system write...

How can we help in getting the system write to zero using the same method,because I have xt1058 model bootloader unlocked and I provide any file needed to disable the pesky system write...
Click to expand...
Click to collapse
First, never quote op. It takes way to much space and is redundant.
Second, to get write off we would need to some how either start a custom kernel some magical way or disable it via a kernel mod like htc guys did. Another way, which was done before was to burn the efuse but kernel has been patched since then.

Need some help, I did all steps until step 9. I installed the QHSUSB_DLOAD driver manually, and I can see 'Qualcomm HS-USB QDLoader 9008 (COM4)' showed in my Device Manager, but when I run 'RUN_Root.bat', I got this
c:\Python27>python qdloadRoot.py MPRG8960.bin -ptf root/partitions.txt
QDLoad utility version 1.2 (c) VBlack 2014
Found TTY port: com4
Sending MAGIC ...
QCOM fast download protocol targ:
Version: 7
Compatible version 2
Maximum block size 1024 (0x00000400)
Base address of Flash 0x00000000
Flash: eMMC
Window size: 30
Number of sectors: 128
First sector size: 2097152 (0x00200000)
Feature bits: 09
Sending SBL Reset...
Done
c:\Python27>pause
Press any key to continue . . .
Then I tried to run 'RUN_Root.bat' again, then I got
c:\Python27>python qdloadRoot.py MPRG8960.bin -ptf root/partitions.txt
QDLoad utility version 1.2 (c) VBlack 2014
Found TTY port: com4
Requesting Params...
Params:
Version: 8
Min version: 1
Max write size: 1536 (0x00000600)
Model: 144
Device size: Invalid or unrecognized Flash device, or Flash device progr
amming not supported by this implementation
Device type: Intel 28F400BX-TL or Intel 28F400BV-TL
Requesting SoftwareVersion...
Version: PBL_DloadVER2.0
Requesting SerialNumber...
Serial number: 00,00,48,03
Requesting HW Id...
HW Id: 00,00,48,03,e1,10,7e,00
Requesting PublicKey...
PublicKey: 39,c4,ee,3e,b5,be,eb,87,8e,2f,e3,b8,53,4d,14,6f,91,ca,fd,bb,94,2a,0d
,aa,d0,1e,b0,87,62,d4,b9,b8
Uploading file 'MPRG8960.bin' to addr 0x2a000000...
Executing...
Could not find Qualcomm device in Emergency download mode
Done, with errors!!!
c:\Python27>pause
Press any key to continue . . .
any suggestions? Thanks

jahrule said:
First, never quote op. It takes way to much space and is redundant.
Second, to get write off we would need to some how either start a custom kernel some magical way or disable it via a kernel mod like htc guys did. Another way, which was done before was to burn the efuse but kernel has been patched since then.
Click to expand...
Click to collapse
Ill put the files here

Fantastic!!! I was looking this. All the last week I was sleeping about 3 hours per day trying to root my phone.
----
I scream "Victory" before the process finish.
Damn! My phone reboot and stay in the android doll fallen screen.

DejanPet said:
Ill put the files here
Click to expand...
Click to collapse
What to do with these files?

Those files are needed by Jahrule

Sabissimo
Hello.
I did everything as instructed, but eventually got the screen "no command".
The only thing I did not flash rom - a month ago updated by an OTA to 5.1, thought it was not necessary.
Factory reset does not help.
Advise something.
In the end, everything worked, thank you))

It works
It works great! Thank you very much! ATT xt1058.

eze_cba17 said:
Damn! My phone reboot and stay in the android doll fallen screen.
Click to expand...
Click to collapse
Follow the OP instruction EXACTLY, no exceptions!
If you got your current 5.1 through AT&T OTA, it's not enough for root patching procedure. A full RSD 5.1 official SBF flash over is required.

Could someone please do a video on this. I'm having a little trouble.

[GUIDE] Updated KIW-L24 UNLOCK/RECOVERY/ROOT

I've noticed since I've followed the thread the days prior to my device arriving many have struggled to follow the current guides available. I am not responsible for your inability to read, bricked, or internally explosions on devices.
Step 1:
Go to your desktop and create a new folder I labeled mine 'KIWISDK' but you can call it whatever you want. This is where you will store all files during this process so you can easily access them.
{
"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"
}
Step 2:
Create and save a blank Wordpad/Word document into the newly created folder on the desktop title it 'bootloadercode'
Step 3:
Assuming you're not android developers or have the massive android SDK on your computers you need to download and install adb and fastboot from here.
Go ahead and put the installer in that folder just for safe keeping, run the exe to natively install adb/fastboot from anywhere on your PC. We will use this a few steps later.
Step 4:
Prior to unlocking your bootloader we have to do a few things first. Go ahead and power on your phone and go through the initial setup process.
You can use the following link (corrected from all the other ones) to create a new Huawei account (click register for free below the login. This website can be found here
Once you've created a user ID you can use this same link to access the bootloader unlock page later.
Step 5:
Once your device is fully initialized go to settings>about phone
click the build number 7 times as shown above. It will display a toast notification that you are now a developer.
press the back button (2) up from the about phone area of the settings you will now see
file:///C:/Users/Jesse/Desktop/developeroptions.png
Be sure that the 'developer options', 'enable OEM unlock' and 'USB debugging' toggles are in the on position.
Step 6:
Open the Huawei website posted in step 4. Login and accept the terms.
On your device go to the dialer and type the following into the keypad:
*#*#1357946#*#* Open the bootloadercode document we created in step 2 and record this number here, leave the word pad open to record the unlock code created on the Huawei website.
With the website open,
Carefully go to About Phone> After you select smart phone and type your model number KIW-L24 into the website open your about Phone>Status enter your Serial number and IMEI number (if your IMEI 1 number doesnt work, try again with your IMEI 2 number. Make sure you have all numbers and letters in this step complete with accuracy. DOUBLE AND TRIPLE CHECK.
Product Identification is the number located on the wordpad/word document copy and past it into this area. Generate the unlock code after typing in the pin.
Copy and paste the generated number onto the wordpad document for future reference and save the wordpad document.
Step 7:
Download TWRP revovery from here
Download the 3.0.2.0 version and save it to your folder you created in step 1
Download SuperSU from here
Save it into the folder on your desktop.
Download opengapps here
Save which ever version you choose to your desktop file (I go with Nano and Micro) Be sure to select the ARM64 and android 6.0 versions.
Also at this time download your favorite custom rom from the ROM/Kernel portion of our website and store it in that file (be sure to check if it needs gapps flashed along with it) if it is a CM based ROM it has to have the gapps either way I always like to keep a gapps zip on my SD card.
Step 8:
Plug your phone into your computer, open your external SD card drag and drop the superSU zip, Open Gapps Zip, and rom if you selected one for future access.
open a command prompt (cmd from Cortana or runcmd in earlier versions of windows.
type the following:
adb reboot bootloader
Your phone should reboot with a white screen, once it has type the following:
fastboot oem unlock 5019482736699543
(these are the numbers the website generated for your specific Identification# copy and paste from the wordpad document 'bootloadercode' It is the 16 digit long code.
Your device will factory reset do not unplug the device until complete.
unplug the device and redo the initial setup. Once complete repeat step 5 to enable USB debugging
Step 9:
Plug the device back into your computer, open the cmd prompt window and type
adb reboot bootloader
FLASHING CUSTOM RECOVERY:
locate the twrp-3.0.2-0-kiwi.img we placed in the folder on your desktop
to ensure you dont misstype anything in the command prompt type:
fastboot flash recovery then drag and drop the twrp-3.0.2-0.img file from the desktop folder to the cmd prompt
It will look something like this:
fastboot flash recovery C:\Users\Name\Desktop\KIWISDK\twrp-3.0.2-0-kiwi.img
**BE SURE THERE IS A SPACE BETWEEN recovery and C:\**
Hit enter.
Once complete type:
fastboot reboot
Step 10:
Let your phone fully reboot, once rebooted Power off your phone.
NANDROID BACKUP - THE MOST IMPORTANT STEP
1) With the phone off hold volume up , the while holding volume up press and hold the power button. You will see the boot logo come up hold for about 2 seconds more and release ( just to ensure )
2)Your phone will boot into TWRP Recovery
3) PRIOR TO FLASHING ANYTHING: Click Backup
Select your External SD card to backup too.
Swipe to backup.
once the STOCK ROM is backed, you can flash the superSU zip from your sd card rooting the stock rom, be sure to wipe cache/dalvik before rebooting.
If you choose to flash a custom rom you placed on your SD card: once stock is backed up:
1. Go to wipe and swipe to wipe stock
2. hit back and go to install
3. select the ROM file you wish to flash
4. select the gapps file
5. you can include SU even if rom is already rooted
wipe cache/dalvik and then reboot. Happy flashing!

will update screenshots and pics soon
this is a holding place

Thanks for this guide. I created an account but for the past 3 days I get the sorry, the server is busy..... Message on every phone and browser I've tried. I tried 3 phones, 7 browsers a windows laptop and an iPad and iPhone they all give me the same silly message after I hit the agree button to the unlock terms and conditions.
What have I done to screw up such an easy process?

954wrecker said:
Thanks for this guide. I created an account but for the past 3 days I get the sorry, the server is busy..... Message on every phone and browser I've tried. I tried 3 phones, 7 browsers a windows laptop and an iPad and iPhone they all give me the same silly message after I hit the agree button to the unlock terms and conditions.
What have I done to screw up such an easy process?
Click to expand...
Click to collapse
Did you try the link I provided?

Wow you are a genius, I wonder why all the others look exactly the same yet only yours works?

954wrecker said:
Wow you are a genius, I wonder why all the others look exactly the same yet only yours works?
Click to expand...
Click to collapse
Was merely trying to delute the guide to a step by step process leaving out no details for people not familiar with root.

954wrecker said:
Wow you are a genius, I wonder why all the others look exactly the same yet only yours works?
Click to expand...
Click to collapse
Did the link work for you? I fixed some link issues in my html link I hope it works as flawlessly for everyone as it did myself.

The page looked the exact same when I agreed to the huge list of terms, but yours took me to the correct place to get the unlock code instead if the servers are busy page. Thanks for the help

Stuck on stock for 3 days really makes the non stock ROMs 10000% smoother! That emui is a trainwreck, it's going to be impossible to go back to that mess.

kobos311 said:
I've noticed since I've followed the thread the days prior to my device arriving many have struggled to follow the current guides available. I am not responsible for your inability to read, bricked, or internally explosions on devices.
Step 1:
Go to your desktop and create a new folder I labeled mine 'KIWISDK' but you can call it whatever you want. This is where you will store all files during this process so you can easily access them.
Step 2:
Create and save a blank Wordpad/Word document into the newly created folder on the desktop title it 'bootloadercode'
Step 3:
Assuming you're not android developers or have the massive android SDK on your computers you need to download and install adb and fastboot from here.
Go ahead and put the installer in that folder just for safe keeping, run the exe to natively install adb/fastboot from anywhere on your PC. We will use this a few steps later.
Step 4:
Prior to unlocking your bootloader we have to do a few things first. Go ahead and power on your phone and go through the initial setup process.
You can use the following link (corrected from all the other ones) to create a new Huawei account (click register for free below the login. This website can be found here
Once you've created a user ID you can use this same link to access the bootloader unlock page later.
Step 5:
Once your device is fully initialized go to settings>about phone
click the build number 7 times as shown above. It will display a toast notification that you are now a developer.
press the back button (2) up from the about phone area of the settings you will now see
file:///C:/Users/Jesse/Desktop/developeroptions.png
Be sure that the 'developer options', 'enable OEM unlock' and 'USB debugging' toggles are in the on position.
Step 6:
Open the Huawei website posted in step 4. Login and accept the terms.
On your device go to the dialer and type the following into the keypad:
*#*#1357946#*#* Open the bootloadercode document we created in step 2 and record this number here, leave the word pad open to record the unlock code created on the Huawei website.
With the website open,
Carefully go to About Phone> After you select smart phone and type your model number KIW-L24 into the website open your about Phone>Status enter your Serial number and IMEI number (if your IMEI 1 number doesnt work, try again with your IMEI 2 number. Make sure you have all numbers and letters in this step complete with accuracy. DOUBLE AND TRIPLE CHECK.
Product Identification is the number located on the wordpad/word document copy and past it into this area. Generate the unlock code after typing in the pin.
Copy and paste the generated number onto the wordpad document for future reference and save the wordpad document.
Step 7:
Download TWRP revovery from here
Download the 3.0.2.0 version and save it to your folder you created in step 1
Download SuperSU from here
Save it into the folder on your desktop.
Download opengapps here
Save which ever version you choose to your desktop file (I go with Nano and Micro) Be sure to select the ARM64 and android 6.0 versions.
Also at this time download your favorite custom rom from the ROM/Kernel portion of our website and store it in that file (be sure to check if it needs gapps flashed along with it) if it is a CM based ROM it has to have the gapps either way I always like to keep a gapps zip on my SD card.
Step 8:
Plug your phone into your computer, open your external SD card drag and drop the superSU zip, Open Gapps Zip, and rom if you selected one for future access.
open a command prompt (cmd from Cortana or runcmd in earlier versions of windows.
type the following:
adb reboot bootloader
Your phone should reboot with a white screen, once it has type the following:
fastboot oem unlock 5019482736699543
(these are the numbers the website generated for your specific Identification# copy and paste from the wordpad document 'bootloadercode' It is the 16 digit long code.
Your device will factory reset do not unplug the device until complete.
unplug the device and redo the initial setup. Once complete repeat step 5 to enable USB debugging
Step 9:
Plug the device back into your computer, open the cmd prompt window and type
adb reboot bootloader
FLASHING CUSTOM RECOVERY:
locate the twrp-3.0.2-0-kiwi.img we placed in the folder on your desktop
to ensure you dont misstype anything in the command prompt type:
fastboot flash recovery then drag and drop the twrp-3.0.2-0.img file from the desktop folder to the cmd prompt
It will look something like this:
fastboot flash recovery C:\Users\Name\Desktop\KIWISDK\twrp-3.0.2-0-kiwi.img
**BE SURE THERE IS A SPACE BETWEEN recovery and C:\**
Hit enter.
Once complete type:
fastboot reboot
Step 10:
Let your phone fully reboot, once rebooted Power off your phone.
NANDROID BACKUP - THE MOST IMPORTANT STEP
1) With the phone off hold volume up , the while holding volume up press and hold the power button. You will see the boot logo come up hold for about 2 seconds more and release ( just to ensure )
2)Your phone will boot into TWRP Recovery
3) PRIOR TO FLASHING ANYTHING: Click Backup
Select your External SD card to backup too.
Swipe to backup.
once the STOCK ROM is backed, you can flash the superSU zip from your sd card rooting the stock rom, be sure to wipe cache/dalvik before rebooting.
If you choose to flash a custom rom you placed on your SD card: once stock is backed up:
1. Go to wipe and swipe to wipe stock
2. hit back and go to install
3. select the ROM file you wish to flash
4. select the gapps file
5. you can include SU even if rom is already rooted
wipe cache/dalvik and then reboot. Happy flashing!
Click to expand...
Click to collapse
My PC finds the adb device before I type "adb reboot bootloader" but once in fastboot, it wont find it. How can I fix that?

It's already been found (on the first part) just type fastboot oem unlock fastboot and adb go hand in hand.
Remember once your bootloader is unlocked you will have to go through the initialization process and toggle developer options on again

AsapJuno said:
My PC finds the adb device before I type "adb reboot bootloader" but once in fastboot, it wont find it. How can I fix that?
Click to expand...
Click to collapse
Please follow the guide as stated.dont deviate thank you.

definitely tried that. Wouldn't be commenting if I didn't. Can you help

Pin Code Telephone # no longer works
I've tried a few days to get the PIN code with * # * # 1357946 # * # * however the number no longer works. Is there a new tele # or an alternate way to unlock the bootloader ?
error msg:
Connection problem or invalid MMI code

Mine worked 2 days ago. So clearly the code works fine check your about phone settings and make sure you have an imei 1 and an imei 2

AsapJuno said:
definitely tried that. Wouldn't be commenting if I didn't. Can you help
Click to expand...
Click to collapse
ASAP Juno, it's already detected your device via adb adb/fastboot are linked just type the commands don't worry about checking fastboot.

any other methods for retrieving the pin code ?
jusdef said:
Pin Code Telephone # no longer works
I've tried a few days to get the PIN code with * # * # 1357946 # * # * however the number no longer works. Is there a new tele # or an alternate way to unlock the bootloader ?
error msg:
Connection problem or invalid MMI cod
Click to expand...
Click to collapse
kobos311 said:
Mine worked 2 days ago. So clearly the code works fine check your about phone settings and make sure you have an imei 1 and an imei 2
Click to expand...
Click to collapse
I have both imei's and actually tried with a two different sim cards...AT&T and Google Fi.
I get the same error message since Saturday night., 7/16/16
Does anyone know of any other methods for retrieving the pin code ?

jusdef said:
I have both imei's and actually tried with a two different sim cards...AT&T and Google Fi.
I get the same error message since Saturday night., 7/16/16
Does anyone know of any other methods for retrieving the pin code ?
Click to expand...
Click to collapse
Let me be more clear, not the ones on the box, you need the digital file backed up via nandroid which originally you said you didn't have? The numbers on the box won't help

So when I install SuperSU, wipe, and reboot... it boots back into twrp

kobos311 said:
Mine worked 2 days ago. So clearly the code works fine check your about phone settings and make sure you have an imei 1 and an imei 2
Click to expand...
Click to collapse
kobos311 said:
Let me be more clear, not the ones on the box, you need the digital file backed up via nandroid which originally you said you didn't have? The numbers on the box won't help
Click to expand...
Click to collapse
Wrong user, I didnt say I did not have imei's and I can't do a Nandroid backup if my phone isnt rooted. I'm trying to unlock my bootloader so I can take the steps to root and install TWRP. Huwai site will not let me submit the request without the pin #.

[ROM] Flyme OS 6 (G) Global Stable for Chinese Pro 6 Plus devices

How To Install Flyme OS 6.1.0.0G Global Stable on Chinese Pro 6 Plus devices
{
"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"
}
This is a Guide to install the Global ROM Flyme OS 6Global on the Meizu Pro 6 Plus Chinese version.
Note: This is also a way to install Any custom ROM made in the future. If someone wanna Customize the ROM( Integrate Xposed and other stuff) feell free to do it.
What does this mean:
Meizu released two versions of the Pro 6 Plus, a chineese version (A) for china and an International version (G) for the devices sold in other countries (International). If you bought your Pro 6 plus from official meizu store on your country, it will come with the G version, but if you bought it from Aliexpress or any other Chinese store, you will buy a Chinese version, some seller may send you the international version if you are lucky but the majoritynot.
Global / International version:
No bloatware, chinese apps..
Multilanguage ( all languages available)
Stock apps optimized for International use (Weather....)
seems to be smoother and faster than the chinese version.
​
Disclaimer
*** As always - Read everything carefully and Flash on our own risk! ***
I can and will not take any responsibility for bricked phones or lost data.​​What do we need:
Rooted Device
FlashFire app from playstore
Flyme 6.1.0.0G _Global_Stable_Pro 6 Plus for Flashfire
​
Instructions:
Its recomnended to back up your data (Titanium backup, your fotos etc)in case of disaster.
Update to a newer version:
Copy the new version to Internal storage
Open Flashfire, click on the + button and choose Flash Zip / OTA
Select the Downloaded ROM from the file explorer and select Mount system read write.
Now you will see a screen with all the actions that will be done, select the action called Reboot and un-thick the option Preserve recovery, leave Normal selected.
Finally click on FLASH and wait until the process ends.
Enjoy...
Note: In case of any problems and you want a clean installation, add the wipe action from the + button before flashing. But it should not be needed.
Note: it seems to be a problem with supersu if you don't wipe data before update. so to avoid problems, you should wipe before flash.
If you want to keep your apps and data, you should make a data (data partition only) backup from flashfire before updating. then wipe and update, follow instructions to root and to have super su. After that you can use flshfire to restore data backup (only data partition) .
also you can use kingroot but its not compatible with flashfire.
If you already updated, you can use titanium backup(give root permision from system root in settings, security root permissions)make a backup of your apps and then follow the guide below How to go back to stock chinese ROM in case of disaster, after that follow the instruction of new installation and when you have the that done, you can rstore your apps with titanium backup.
[/LIST]
​
First Time Installation:
Root:
Go to Meizu page and create and account. Enter a valid email as its needed to activate the account. if you already have an account, just skip this step.
Now go to Settings on your device and Select Meizu account, Log in with your new created account.
Go back and select Fingerprint & security , then select Root permission, scroll down and confirm. The device will reboot. Now its rooted but i recommend installing supersu because the built int root some times has failed for me.
Install SuperSu from playstore, open it and select Update su binary, choose Normal. wait until it finishes and reboot.
Now you have Root
Note: if you dont have Google Playstore, open meizu app store and search for supersu.
Install ROM:
Root your device
Install Flashfire from Playstore
Download This modified Flyme 6.1.0.0G _Global_Stable_Pro 6 Plus for Flashfire
[*]Copy the downloaded ROM to Internal storage
[*]Open Flashfire, give root permissions and click on the + button,
[*]Select Wipe and then ok
[*]Click again on the + button and choose Flash Zip / OTA
[*]Select the Downloaded ROM from the file explorer and select Mount system read write. See these screens for more information:
[*]Now you will see a screen with all the actions that will be done, select the action called Reboot and unthick the option Preserve recovery, leave Normal selected.
[*]Finally click on FLASH and wait until the process ends.
[*]Enjoy...
​
Optional:
You can Install gapps from flashfire along with the rom, just select Flash zip/ota and select Gapps zip, this way it will be installed after rom. Or you can use Google Installer which you can find in meizu appstore after reboot.
Note: For future updates, do not update the device from the Updates app included as it will donload the Gobal version of Flyme but it will fail because your device is still a chinese version.
How to go back to stock chinese ROM in case of disaster:
Download the latest version of chinese Flyme from: [url]http://www.flyme.cn/firmwarelist-101.html#3
​
Turn off the device （hold power button until it turns off.
Hold Volume + button and power button at the same time until the phone vibrates. it will enter recovery mode.
Connect your device to your PC by usb, you will have access to a folder named Recovery. Copy the update.zip to this folder and wait for it to finish.
Go back to the device and select the options Upgrade System and Clear data.
Hit Start and wait until it finishes.
​
Older Versions:
Flyme OS 6.7.4.11_beta_Global_Pro 6 Plus for Flashfire

Thanks for this tutorial! It was very detailed and easy to follow.
In the future when I want to perform an update, do I need to go through FlashFire in order for it to work correctly on a Chinese version of the device? Also, where do you download the "G" versions of the beta firmware? I know their next release is a stable version and I know it comes out after the A version; just wondering where you go to download it. Cheers!

ShaolinMilk said:
Thanks for this tutorial! It was very detailed and easy to follow.
In the future when I want to perform an update, do I need to go through FlashFire in order for it to work correctly on a Chinese version of the device? Also, where do you download the "G" versions of the beta firmware? I know their next release is a stable version and I know it comes out after the A version; just wondering where you go to download it. Cheers!
Click to expand...
Click to collapse
For future update you can download the stable from http://www.flymeos.com/firmwarelist?modelId=46&type=1. Or the betas from flyme forum. You will have to edit the installation script to be able to flash through flashfire and don't get error and avoid firmware problems. Anyway i will upload the future updates modified for flashfire.

bihariel said:
For future update you can download the stable from http://www.flymeos.com/firmwarelist?modelId=46&type=1. Or the betas from flyme forum. You will have to edit the installation script to be able to flash through flashfire and don't get error and avoid firmware problems. Anyway i will upload the future updates modified for flashfire.
Click to expand...
Click to collapse
Thanks!!! I tried looking through the zip file to see what you changed, but didn't know which file to go into. I assume it's not as easy as opening up a file in notepad and changing some data on there.

ShaolinMilk said:
Thanks!!! I tried looking through the zip file to see what you changed, but didn't know which file to go into. I assume it's not as easy as opening up a file in notepad and changing some data on there.
Click to expand...
Click to collapse
Its not hard to do but yes, i you dont know what are you doing is dangerous. Dont worry i will upload future updates.

bihariel said:
Its not hard to do but yes, i you dont know what are you doing is dangerous. Dont worry i will upload future updates.
Click to expand...
Click to collapse
Thanks dude! Looking forward to it.

im surprised at how small the response to this phone is....just stumbled upon it while looking for a new device.
this is rather off-topic but this seems to be the most active thread

thanks for that.
i have question,i can flash the Flyme 5.2.7.0G by this method?

@bihariel Hey I have a question for you. Have you ever experienced a sudden change in battery life out of nowhere? When I first installed this firmware, the battery was perfect. All of a sudden after charging my phone, the battery is draining at an unprecedented rate especially on standby. I charged the phone to 100%, disabled all notification/wifi/cellular network and left it on overnight to activate the battery calibration. The problem still exists however. It's draining about 1% every 2 minutes on standby which is ridiculous.
I'm just wondering if you ever encountered this issue before.
Sent from my PRO 6 Plus using XDA-Developers Legacy app

mr.mgmg said:
thanks for that.
i have question,i can flash the Flyme 5.2.7.0G by this method?
Click to expand...
Click to collapse
You can but you have to modify the script to avoid firmware files and recovery.img to be flashed, which would end in an installation abort,

ShaolinMilk said:
@bihariel Hey I have a question for you. Have you ever experienced a sudden change in battery life out of nowhere? When I first installed this firmware, the battery was perfect. All of a sudden after charging my phone, the battery is draining at an unprecedented rate especially on standby. I charged the phone to 100%, disabled all notification/wifi/cellular network and left it on overnight to activate the battery calibration. The problem still exists however. It's draining about 1% every 2 minutes on standby which is ridiculous.
I'm just wondering if you ever encountered this issue before.
Sent from my PRO 6 Plus using XDA-Developers Legacy app
Click to expand...
Click to collapse
Not really, the battery is surprising me on this ROM. Maybe you sould use a battery monitoring app and see whats draining it. If not, do a factory reset and see if it still prsists.

bihariel said:
You can but you have to modify the script to avoid firmware files and recovery.img to be flashed, which would end in an installation abort,
Click to expand...
Click to collapse
so,how we can do that?
i think the 6.7.4.11_beta_Global no stable yet
u can edit the Flyme 5.2.7.0G?

bihariel said:
How To Install Flyme OS 6.7.4.11 Global on Chinese Pro 6 Plus
This is a Guide to install the Global ROM Flyme OS 6.7.4.11 on the Meizu Pro 6 Plus Chinese version.
Note: This is also a way to install Any custom ROM made in the future. If someone wanna Customize the ROM( Integrate Xposed and other stuff) feell free to do it.
What does this mean:
Meizu released two versions of the Pro 6 Plus, a chineese version (A) for china and an International version (G) for the devices sold in other countries (International). If you bought your Pro 6 plus from official meizu store on your country, it will come with the G version, but if you bought it from Aliexpress or any other Chinese store, you will buy a Chinese version, some seller may send you the international version if you are lucky but the majoritynot.
Global / International version:
No bloatware, chinese apps..
Multilanguage ( all languages available)
Stock apps optimized for International use (Weather....)
seems to be smoother and faster than the chinese version.
​
Disclaimer
*** As always - Read everything carefully and Flash on our own risk! ***
I can and will not take any responsibility for bricked phones or lost data.​​What do we need:
Rooted Device
FlashFire app from playstore
Flyme OS 6.7.4.11_beta_Global_Pro 6 Plus for Flashfire
​
Instructions:
Its recomnended to back up your data (Titanium backup, your fotos etc)in case of disaster.
Root:
Go to Meizu page and create and account. Enter a valid email as its needed to activate the account. if you already have an account, just skip this step.
Now go to Settings on your device and Select Meizu account, Log in with your new created account.
Go back and select Fingerprint & security , then select Root permission, scroll down and confirm. The device will reboot. Now its rooted but i recommend installing supersu because the built int root some times has failed for me.
Install SuperSu from playstore, open it and select Update su binary, choose Normal. wait until it finishes and reboot.
Now you have Root
Note: if you dont have Google Playstore, open meizu app store and search for supersu.
Install ROM:
Root your device
Install Flashfire from Playstore
Download This modified Flyme OS 6.7.4.11_beta_Global_Pro 6 Plus
Copy the downloaded ROM to Internal storage
Open Flashfire, give root permissions and click on the + button,
Select Wipe and then ok
Click again on the + button and choose Flash Zip / OTA
Select the Downloaded ROM from the file explorer and select Mount system read write. See these screens for more information:
Now you will see a screen with all the actions that will be done, select the action called Reboot and unthick the option Preserve recovery, leave Normal selected.
Finally click on FLASH and wait until the process ends.
Enjoy...
​
Optional:
You can Install gapps from flashfire along with the rom, just select Flash zip/ota and select Gapps zip, this way it will be installed after rom. Or you can use Google Installer which you can find in meizu appstore after reboot.
Note: For future updates, do not update the device from the Updates app included as it will donload the Gobal version of Flyme but it will fail because your device is still a chinese version.
How to go back to stock chinese ROM in case of disaster:
Download the latest version of chinese Flyme from: http://www.flyme.cn/firmwarelist-101.html#3
Turn off the device （hold power button until it turns off.
Hold Volume + button and power button at the same time until the phone vibrates. it will enter recovery mode.
Connect your device to your PC by usb, you will have access to a folder named Recovery. Copy the update.zip to this folder and wait for it to finish.
Go back to the device and select the options Upgrade System and Clear data.
Hit Start and wait until it finishes.
​
Click to expand...
Click to collapse
Hello everyone, thanks a lot bihariel for this guide.
I have successfully installed the beta with flashfire and it's all ok!
Some people say flashfy is not a very safe method, what do you think? I'm not an expert.
However, I did not go to the flymex account synchronization, now I've installed the closed beta apps yesterday and it works perfectly well!
We wait for the stable then!
Can you explain how you modified the update for the future? Thanks so much.
Are Alternative Methods to Flashfire? Type ADB?
In Italy a seller on his blog posted this guide, but I could not install it:
"The tutorial for installing firmware G in the Asian Meizu Pro 6 Plus smartphone is really very simple and does not require solid modding basics, you just have to be careful about installing ADB drivers correctly.
Load the battery completely before you begin the procedure and save all your important data
On your PC or on a Cloud as you will need to make the full factory reset.
Prerequisites Preinstalling Firmware G in Meizu Pro 6 Plus:
1-Smartphone fully charged
2-Any antivirus and / or firewalls disabled
3-Driver ADB properly installed, restart your PC after installation!
4-Enabled Root permissions through Flyme account (Fingerprint and Security Menu)
5-USB Debug Mode Enabled in Developer Options (Accessibility Menu)
G Firmware Installation in Meizu Pro 6 Plus:
Decompress the Meizu_Pro6plus_Flyme 5.2.7.0G.zip archive and copy it to the root folder
Of Meizu Pro 6 Plus the file system-i.img
Decompress the archive adb_tool.zip and in the folder obtained we select the file
Cmd.exe to open the command window
Write in the command window:
Adb shell
We give Send and permission to ADB through the pop-up that will appear on the Meizu Pro 6 Plus display
We will read in the shell @ Pro6Plus command window
WARNING: If the pop-up display does not appear, ADB drivers have not been installed correctly!
Write in the command window:
su
We give Send and permission of ADB SHELL root permissions through
The pop-up that will appear on the Meizu Pro 6 Plus display
We will read in the command window the symbol #
WARNING: If the pop-up display does not appear, root permissions are disabled!
Write in the command window:
Dd if = / sdcard / system-i.img of / dev / block / platform / 155a0000.ufs / by-name / system
We give Enter, we will see the cursor blink, we do not touch anything until the flash procedure
The system will not be completed and the screenshot message below will appear
Meizu pro 6 plus 01
Disconnect the usb cable from the Meizu Pro 6 Plus and restart it by holding down the button
Power for a few seconds, the startup process will take a few minutes, do not alarm and we start booting.
When the terminal is started we go in
Settings> About phone> Storage> Factory data reset>
We see Factory reset and Format internal storage>
Select START RESET"
I put into google translate, if you want the original in italian language let me know.

mr.mgmg said:
so,how we can do that?
i think the 6.7.4.11_beta_Global no stable yet
u can edit the Flyme 5.2.7.0G?
Click to expand...
Click to collapse
I read in some chinese forum that we cant downgrade but...
Download the ROM 5.2.7.0G, open the zip and editthis file \META-INF\com\google\android\updater-script
You can use this picture as a guide, delete the red lines:

Tony72 said:
Hello everyone, thanks a lot bihariel for this guide.
I have successfully installed the beta with flashfire and it's all ok!
Some people say flashfy is not a very safe method, what do you think? I'm not an expert.
However, I did not go to the flymex account synchronization, now I've installed the closed beta apps yesterday and it works perfectly well!
We wait for the stable then!
Can you explain how you modified the update for the future? Thanks so much.
Are Alternative Methods to Flashfire? Type ADB?
In Italy a seller on his blog posted this guide, but I could not install it:
"The tutorial for installing firmware G in the Asian Meizu Pro 6 Plus smartphone is really very simple and does not require solid modding basics, you just have to be careful about installing ADB drivers correctly.
Load the battery completely before you begin the procedure and save all your important data
On your PC or on a Cloud as you will need to make the full factory reset.
Prerequisites Preinstalling Firmware G in Meizu Pro 6 Plus:
1-Smartphone fully charged
2-Any antivirus and / or firewalls disabled
3-Driver ADB properly installed, restart your PC after installation!
4-Enabled Root permissions through Flyme account (Fingerprint and Security Menu)
5-USB Debug Mode Enabled in Developer Options (Accessibility Menu)
G Firmware Installation in Meizu Pro 6 Plus:
Decompress the Meizu_Pro6plus_Flyme 5.2.7.0G.zip archive and copy it to the root folder
Of Meizu Pro 6 Plus the file system-i.img
Decompress the archive adb_tool.zip and in the folder obtained we select the file
Cmd.exe to open the command window
Write in the command window:
Adb shell
We give Send and permission to ADB through the pop-up that will appear on the Meizu Pro 6 Plus display
We will read in the shell @ Pro6Plus command window
WARNING: If the pop-up display does not appear, ADB drivers have not been installed correctly!
Write in the command window:
su
We give Send and permission of ADB SHELL root permissions through
The pop-up that will appear on the Meizu Pro 6 Plus display
We will read in the command window the symbol #
WARNING: If the pop-up display does not appear, root permissions are disabled!
Write in the command window:
Dd if = / sdcard / system-i.img of / dev / block / platform / 155a0000.ufs / by-name / system
We give Enter, we will see the cursor blink, we do not touch anything until the flash procedure
The system will not be completed and the screenshot message below will appear
Meizu pro 6 plus 01
Disconnect the usb cable from the Meizu Pro 6 Plus and restart it by holding down the button
Power for a few seconds, the startup process will take a few minutes, do not alarm and we start booting.
When the terminal is started we go in
Settings> About phone> Storage> Factory data reset>
We see Factory reset and Format internal storage>
Select START RESET"
I put into google translate, if you want the original in italian language let me know.
Click to expand...
Click to collapse
I can tell you that for now the safest method is flashfire because it install the ROM in same way that the Recovery does, that is: it wipes the system partition and installs the ROM with correct permissions.
The method you mention is more risky( to get a bootloop) because it overwrites the ROM files directly over the System partition with the OS still running on phone. This drives into a system hang freeze. of course you have to turn it of by holding power button until it restarts. Then you have to go recovery and do a factory reset if you get bootloop.
I tried this method before Flasfire but it gave me bootloop so then i used Flashfire because it do the same job that Recovery does.
About the modifications, its really simple. Just open \META-INF\com\google\androidupdater-script and delete all the lines in red in this picture (these lines check if your phone is Chinese version or global and update the firmware files.)
Also you can delete the files related to those lines just for safety (boot.img, recovery.img, logo.bin, ldfw, bootloader..)

bihariel said:
I can tell you that for now the safest method is flashfire because it install the ROM in same way that the Recovery does, that is: it wipes the system partition and installs the ROM with correct permissions.
The method you mention is more risky( to get a bootloop) because it overwrites the ROM files directly over the System partition with the OS still running on phone. This drives into a system hang freeze. of course you have to turn it of by holding power button until it restarts. Then you have to go recovery and do a factory reset if you get bootloop.
I tried this method before Flasfire but it gave me bootloop so then i used Flashfire because it do the same job that Recovery does.
About the modifications, its really simple. Just open \META-INF\com\google\androidupdater-script and delete all the lines in red in this picture (these lines check if your phone is Chinese version or global and update the firmware files.)
Also you can delete the files related to those lines just for safety (boot.img, recovery.img, logo.bin, ldfw, bootloader..)
Click to expand...
Click to collapse
Thanks a lot!, I'll read all as soon I could

BE Careful
Removed

bihariel said:
I read in some chinese forum that we cant downgrade but...
Download the ROM 5.2.7.0G, open the zip and editthis file \META-INF\com\google\android\updater-script
You can use this picture as a guide, delete the red lines:
Click to expand...
Click to collapse
i flashed the 6.7.4.11 but i have problem when i open the front camrera and close the camrea not open again
now i want back to the 5.2.7.0G but when i want edit the script is Different about your picture.
u can edit the just script and upload and then i will add to zip

mr.mgmg said:
i flashed the 6.7.4.11 but i have problem when i open the front camrera and close the camrea not open again
now i want back to the 5.2.7.0G but when i want edit the script is Different about your picture.
u can edit the just script and upload and then i will add to zip
Click to expand...
Click to collapse
Salam,
The camera bug is weird, i don't have that bug, i open the camera ( front and back) many times and it works perfectly, maybe you changed something in camera setting ( erasing camera app data should help)
Anyway, the script is exactly the same as mine, its just you are using and editor with Arabic orientation.
Just use the app Notepad++( google it) and open it in English lang.
If not, just upload the script for me and i will edit it.

bihariel said:
Salam,
The camera bug is weird, i don't have that bug, i open the camera ( front and back) many times and it works perfectly, maybe you changed something in camera setting ( erasing camera app data should help)
Anyway, the script is exactly the same as mine, its just you are using and editor with Arabic orientation.
Just use the app Notepad++( google it) and open it in English lang.
If not, just upload the script for me and i will edit it.
Click to expand...
Click to collapse
ealaykum alssalam
thanks bro for help
i flashed the rom without change anything in script and its work
u know when the stable rom will out?

[Guide] How to root SM-J730F without TWRP [Android 7.0.0] [Firmware Included]

Note to users: I am NOT RESPONSIBLE for any damage done to your device. I did this on my phone and it worked just fine. Any damages done to the device is your fault. Please make sure to follow the steps carefully.
This is a guide on how to root the Samsung Galaxy J7 SM-J730F without TWRP. I've included a backup stock firmware in case you soft-brick your device.
BACKUP STOCK FIRMWARE FOR SOFT-BRICKED DEVICES:
In case you have soft-bricked your device by doing this tutorial incorrectly, download the stock firmware HERE and follow this guide to re-flash your phone, HERE. Do not attempt to root your device again unless you know what you're doing this time.
I also recommend completely backing up your device after successful root - click here to find out how.
WARNINGS:
1. You will have to WIPE ALL YOUR DATA in order to complete this tutorial.
2. You are at a very high risk of screwing up your device if you proceed ahead with this tutorial. Please make sure you know what you are doing, and that you have knowledge of re-flashing your phone. I am not responsible.
Requirements:
1. A Samsung Galaxy J7 SM-J730F device;
2. PC;
3. An USB cable;
4. Odin v3.12.7 - Download Here;
5. SuperSU .tar file - Download Here;
6. ADB - Download Here.
Instructions:
1. Download Odin on your PC from the link above, and extract everything from the archive to C:\ODIN (create a new folder);
2. Download the SuperSU .tar file from the link above and place it in your C:\ODIN folder. DON'T extract this archive;
3. Download ADB from the link above and extract the contents of the archive to C:\ADB (create a new folder);
4. Make sure USB Debugging AND OEM Unlock are ENABLED in Settings --> Developer Options on your phone. If you don't know how to activate Developer Options, check this out. After you've enabled these, connect your USB cable from your phone to your PC.
Note: If the phone tells you an access request is being received from your PC's fingerprint, accept it.
6. Open ADB on your computer by going to a Command Prompt, and typing cd C:\ADB;
7. Type adb devices to make sure your phone has been detected by ADB, like so:
{
"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"
}
8. In the Command Prompt, type adb reboot recovery and press enter to reboot your phone into Recovery Mode;
9. Once your phone has booted into Recovery Mode, select the Wipe data/factory reset, and then select Yes when it asks for confirmation:
(Note: THIS STEP IS MANDATORY. If you don't wipe your data, the encryption on your phone will remain and you will be unable to root your phone.)
10. After you've wiped your data, BOOT DIRECTLY INTO DOWNLOAD MODE FROM RECOVERY MODE. You can do this by holding down Volume Down + Home Key + Power Button WHILE STILL IN THE RECOVERY MENU.
Important Note: Ideally, you should still be in the recovery menu after doing a factory reset. Then do the instructions above to enter Download Mode. If you reboot AND THEN go to Download Mode, this method won't work, because your encryption will be put in place again and your phone will become unrootable. Please do the above steps with caution.
11. Hold the buttons down. If you did everything correctly, you should see a screen like this pop up:
12. Press the Volume Up button to proceed to the flashing section. You should see this screen:
13. Now, make sure that the USB cable is still connected to your phone. Open ODIN on your PC, and click on the AP button, then select the SuperSU archive that you downloaded. Make sure that your phone is detected, Odin has to say "Added!!" in the log to the right. If it doesn't say that, re-connect your USB cable to your phone, or switch the USB port on your PC. Then press Start to begin flashing SuperSU and rooting your phone:
14. After Odin has finished flashing your phone, it should say PASS! at the top left of the window, under it's name. Your phone will reboot automatically.
15. Once your phone has rebooted, you should be greeted by the usual setup screen that happens when you factory reset your device. Set up the settings as normal, and install SuperSU from the Play Store HERE once the phone is set up. (This is VERY important.)
16. After you've installed SuperSU, download Titanium Backup from the Play Store, and uninstall the system app "Knox" and everything with "Knox" in their name, and also uninstall "Device Security". They could mess with your boot and spam you with "Unauthorized Action" notification. You don't need them anyway -- once you're rooted, those two don't work anymore.
And that's it!
Your phone should be rooted now! I recommend installing Root Checker to see if you have done everything correctly. It should return this result if so:
Thanks for reading my tutorial! I hope it has helped you root your phone. If you did everything correctly, you should be rooted now. If you have soft-bricked your device and your phone is stuck on the Samsung boot logo, please download the included backup firmware and re-flash your phone, and do not attempt to root your phone again.
Hit the "Thanks!" button if my guide helped you!
Please leave any problems you might have in the comments, and don't be immature. I will not help people with a bad attitude. As I said, if you **** up, it's your problem and I am not responsible. But I will still try to help.
-----------------------------------------------------------------
Recommendations (Optional):
I recommend the following root-only apps to enhance your rooted experience.
1. Titanium Backup - Must-have app for rooted users. Useful in debloating your phone, freezing apps (hiding them from app drawer and disabling them - even system apps), backing up apps and more.
2. FlashFire - Useful for completely backing up your phone, flashing your phone with ZIPs, restoring backups and more.
3. Link2SD - Useful for moving apps to the SD card or to the Internal Storage, and more.
4. Greenify - Greenify working in root mode is the best battery saving app there is. It hibernates the apps that you don't use so that you can get the most out of your battery.
5. ES File Manager PRO - The perfect file manager. It lets you back up your apps, has a root explorer function, can let you see hidden files, lets you create shortcuts to any file on your home screen, and much more. There is a free version too, but I strongly recommend the PRO version.
Note: You guys can leave root-only apps in the replies as well, I didn't include a full list of them, obviously, so you guys can help people finding the apps they need to enhance their newly unlocked root experience.
If you want me to send you a list of safe to uninstall system apps, PM me.
Quick extra tip: To disable the ugly white frames for icons in the TouchWiz Home launcher, go to Settings -> Display -> Icon Frames and choose Icons Only.
------------------
Revisions:
- Added extra step about Knox resulting from the feedback of a user.
- Removed system app section. Seems to be giving people boot issues.

good work:good:
i did it and all was good till rebooting.my phone got stuck in the product logo so i had ton get a new software and root again but i'm afraid of rebooting it again.what should i d plz ?
i think the proplem within the device maintenance & security...it says restart to undo the unauthorised actions!!

MEMA1191 said:
good work:good:
i did it and all was good till rebooting.my phone got stuck in the product logo so i had ton get a new software and root again but i'm afraid of rebooting it again.what should i d plz ?
i think the proplem within the device maintenance & security...it says restart to undo the unauthorised actions!!
Click to expand...
Click to collapse
Root again and check every step carefully.
After you've checked everything was done properly, ONLY UNINSTALL KNOX AND DEVICE SECURITY. Don't attempt to uninstall other system applications other than the ones listed in the list.
That's why you're getting "Unauthorized Action" warning. Because Knox is still in effect, and it's detected that you're using a rooted phone. Therefore it warns you. So uninstall it completely, and everything else with "Knox" in its name.
I'm going to add this to the guide so that this doesn't happen again.
NOTE: Also don't worry, once you have completely re-flashed your phone with default stock firmware, it's not rooted anymore and rebooting is safe. Rebooting while rooted is also perfectly safe, if you can do tutorial steps correctly and don't skip over any steps.

I think this guide should be on this forum : https://forum.xda-developers.com/galaxy-j7-2017, but it had very help me, thank you!
After my second reboot (first done after remove the knox things), I'm stuck ont boot screen... I'm not sure, but I think onedrive can't be remove... I will try again

arwandar said:
I think this guide should be on this forum : https://forum.xda-developers.com/galaxy-j7-2017, but it had very help me, thank you!
After my second reboot (first done after remove the knox things), I'm stuck ont boot screen... I'm not sure, but I think onedrive can't be remove... I will try again
Click to expand...
Click to collapse
Don't try to uninstall system apps. I will remove that whole section - seems to be giving people a lot of trouble.

ScarXL said:
Don't try to uninstall system apps. I will remove that whole section - seems to be giving people a lot of trouble.
Click to expand...
Click to collapse
For me, it's the only useful part of the tutos, as I root the phone with trwp... I am tring to remove all systems apps exept onedrive, which always leads me to have issues after reboot.
For now, I've successfully remove
Duo
Excel
Google Play Musique
Google Play Films & séries
Powerpoint
S Health and services
Samsung notes
Skype
Smart Switch
Talkback
Upday
Word
*knox* + device security
EDIT:
Removed too without problems:
*ant* + radio
internet browser
samsung members
voice recorder
maps
my files
choco truc
foundation
roseeukor
samsung push
ScarXL, can you pm me the list you've removed?

arwandar said:
For me, it's the only useful part of the tutos, as I root the phone with trwp... I am tring to remove all systems apps exept onedrive, which always leads me to have issues after reboot.
For now, I've successfully remove
Duo
Excel
Google Play Musique
Google Play Films & séries
Powerpoint
S Health and services
Samsung notes
Skype
Smart Switch
Talkback
Upday
Word
*knox* + device security
Click to expand...
Click to collapse
Well, don't remove OneDrive then. I have no idea what's causing this issue. I uninstalled all those apps in the list on my phone and it works just fine?

this did not work for me. After rooting the device I am stuck with SAMSUNG boot logo. I think I have android 9 might be the issue.
AP: J730FXXS6CTD1
CP: J730FXXS6CTD1
CSC: J730FOXX6CSK6
Model: SM-J730F/DS