Related
{
"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"
}
More information about this device:
DIFFERENT VARIANTS AND VERSIONS OF Honor 3C
There are now five main versions of Honor 3C that i am aware of:
H30-U10 (联通2G), H30-T00 (移动1G), H30-T10 (移动2G), H30-L01 (移动4G) and H30-L02 (联通4G).
Most guides and resources provided on this thread are dedicated to Honor 3C 2G H30-U10 with MT6582 chip.
But guides like SD Upgrade and ROM flashing using SPFT might also applicable to other variants with MT6582.
Just make sure you don't mess up and use only files dedicated to your device, please check, and double check.
Since we will be working with Honor 3C H30-U10, let's discuss some known variants of this version.
International set: Comes with LOCKED bootloader. (Ref. Build number: H30-U10 V100R001C900B1XX)
China set: Comes with UNLOCKED bootloader. (Ref. Build number: H30-U10 V100R001CHNC00B1XX)
Europe set: Comes with LOCKED bootloader. (Ref. Build number: H30-U10 V100R001C432B1XX)
Note: International set sometimes referred to as global, MY (Malaysia) or TW (Taiwan) set.
USEFUL LINKS & RESOURCES
H30-U10 ROM (In UPDATE.APP format)
Official ROM for International Set
* EMUI 2.0 / V100R001C900B110 / JellyBean 4.2.2 (Mirror: UsersFiles, Mega)
* EMUI 2.0 / V100R001C900B115 / JellyBean 4.2.2 (Latest) (Official, Mirror: UsersFiles)
Official ROM for International Set (New Revision/Set)
* EMUI 2.0 / V100R001C900B127 / JellyBean 4.2.2 (Official, Mirror: UsersFiles) (New/diff digitizer)
Official ROM for International Set (Region Based Update)
* EMUI 3.0 / V100R001C900B320 / KitKat 4.4.2 (Optimized for SouthEast Asia countries) (Official, usersfiles)
* EMUI 3.0 / V100R001C900B320 / KitKat 4.4.2 (Same with above, higher zip compression) (Official, usersfiles)
Official ROM for China Set
* EMUI 2.0 / V100R001CHNC00B149 / JellyBean 4.2.2 (稳定版 / Stable Build) (Official)
* EMUI 2.3 / V100R001CHNC00B629 / 4.10.16 / KitKat 4.4.2 (开发版 / Developer Build) (Official)
* EMUI 3.0 / V100R001CHNC00B255SP01 / 4.12.10 / KitKat 4.4.2 (开发版 / Developer Build) (Official)
* EMUI 3.0 / V100R001CHNC00B256SP01 / 4.12.20 / KitKat 4.4.2 (稳定版 / Stable Build) (Official)
* EMUI 3.0 / V100R001CHNC00B261 / 5.02.06 / KitKat 4.4.2 (稳定版 / Stable Build) (Official)
* EMUI 3.0 / V100R001CHNC00B266 / 5.05.08 / KitKat 4.4.2 (稳定版 / Stable Build) (Official, UsersFiles, Mega)
* EMUI 3.0 / V100R001CHNC00B267 / 5.08.12 / KitKat 4.4.2 (稳定版 / Stable Build) (Official, UsersFiles)
* EMUI 3.0 / V100R001CHNC00B268 / 5.10.27 / KitKat 4.4.2 (稳定版 / Stable Build) (Official, UsersFiles)
Official ROM for Europe Set
* EMUI 2.0 / V100R001C432B109 / JellyBean 4.2.2 (Official)
* EMUI 2.0 / V100R001C432B111 / JellyBean 4.2.2 (Official, Mega) (Note: For sets with new/diff digitizer)
* EMUI 3.0 / V100R001C432B306 / JellyBean 4.4.2 (Official, UsersFiles) (Note: Works woth both old/new digitizer)
Unofficial ROM (Leaked & Beta) (Outdated now)
* EMUI 3.0 / V100R001C432B301 / KitKat 4.4.2 (Optimized for EU sets) (SPFT Dump shared by kornis01)
* EMUI 3.0 / V100R001C900B310 / KitKat 4.4.2 (Optimized for Middle East countries) (Official, Mega mirrored by Ax1qwer)
Note:
* For devices that come with B127/B129/B111, use only EMUI 3.0 B3XX releases and NOT the B2XX . (Touch issue)
SP Flash Tool Flashable ROM
Signed Factory Stock ROM for International Set (H30-U10 V100R001C900B108)
Signed Factory Stock ROM for Europe Set (H30-U10 V100R001C432B111)
* To Honor 3C europe set users: ONLY use B111 if your device come with this version, otherwise use B108.
Custom ROM in Zip Format (With Custom Recovery Only)
<Click HERE for tested custom ROM>
* To be updated / contact me if you know any good one or want to add yours to the list.
Flashable Zip (With Custom Recovery Only)
Chainfire SuperSU (For root & Superuser app)
Google Apps for JB 4.2.2 (gapps-jb-20130812-signed.zip)
Google Apps for 4.4+ (Delta GApps)
Google Apps for 5.1+ (TK GApps) (Note: 'pico' or 'nano' version preferred)
Drivers
Handset WinDriver v1.00.00.31 (Drivers for ADB, MTP, USB Mass Storages, etc)
DriverAutoInstaller v1.1236.00 (Drivers for MediaTek USB VCOM)
MediaTek USB VCOM Driver v1.1123.00 (MTK VCOM driver for Win 8.1 x64) (Important: read this)
Programs & Tools
SP Flash Tool v3.1324.0.sn177 (SecBoot)
Hi-Suite - Android Smart Device Manager (Official software by Huawei)
Huawei Update Extractor by @worstenbrood (Tool to work with Huawei update.app)
MTK Droid Root by @rua1 (Multi-function ROM Tool)
Miscellaneous
H30-U10 JB Kernel Source (Kernel 3.4.5)
H30-U10 KK Kernel Source (Kernel 3.4.67)
Online Themes for EMUI 2.0 (Theme preview & downloadable .hwt format)
Online Themes for EMUI 2.3 (Theme preview & downloadable .hwt format)
NOTE: Password to download & extract file, if needed: [email protected]
CREDIT & THANKS
gavrila from 4pda.ru - For sharing unlocked bootloader and provide modem hack tips! Huge thanks!
cvg from LYN - For sharing stock B108 SPFT flashable ROM and other useful resources.
@Dees_Troy - For the greatest TWRP Recovery
@carliv - For his Carliv Touch Recovery and Modified CWM for MTK phones.
@yuweng - For his Easy Magic TWRP Installer for MTK phones.
@worstenbrood - For his Huawei Update Extractor, the best software to work with update.app.
@Whiskey103 - For his screenshot taking tool.
@Chainfire - For his SuperSU.
@TKruzze, @osm0sis - For their TK gapps packages.
@Deltadroid - For his Delta gapps packages.
And many many more who contributed to the projects, thank you all!
DISCLAIMER
All guides and informations shared on this page are purely based on my own personal experiences.
I cannot guarantee that these informations are 100% correct, there is a chance that some of the info is inaccurate/wrong,
but i can assure you all these guides have been personally tested and proven working from my repeated trials and tests.
Though, i cannot promise that these tricks will work on your device, nor won't brick your device, there is always a risk.
I will NOT be responsible for any loss or damage caused, or alleged to have been caused, directly or indirectly,
by the informations or ideas suggested or referenced, including but not limited to links and files provided on this thread.
Please try at your own risk. Your warranty is now void.
I am more than happy to answer any question related to the guides, all others irrelevant question will be ignored.
All private message asking for support will NOT be entertained, i have shared everything i know about the device.
Please note that most guides found on this page were written with Honor 3C H30-U10 (MY) locked set in mind,
Make sure you have read and understand all the steps, and check whether the guide is applicable to your device before applying it.
.
Before We Begin...
BEFORE We Begin, Make Sure You
HAVE Compatible Version of 'Handset Driver' Installed.
* This driver provide access for device services such as ADB, MTP, USB Mass Storages, etc.
* You can get 'Handset WinDriver 1.00.00.31' from HERE. (18.5 MB - Mediafire)
* NOTE: It's recommended that you install the driver as Adminstrator while the phone is connected.
Driver shared courtesy of cvg from LYN
Click to expand...
Click to collapse
HAVE 'MediaTek VCOM Driver' Installed.
* This driver allow SP FlashTool to work with the device running under META/PreLoader mode.
* You can get the driver from HERE. (9.6 MB - Mediafire)
* NOTE: It's recommended that you install the driver as Adminstrator while the phone is connected.
Driver shared courtesy of cvg from LYN
Click to expand...
Click to collapse
HAVE Prepared Memory Card (Micro SD), and...
* Required for storing ROM & updater files, mainly UPDATE.APP and UPDATE.ZIP.
* Need to be FAT32 formatted, has minimum 1.3 GB free space if you plan to use ROM upgrade feature.
* MicroSD class 10 or higher is recommended for faster operation.
Click to expand...
Click to collapse
KNOW How To Transfer Files From Computer to SD Card.
* You can manage files on SD card easily by connecting the phone to PC with USB cable.
* You need to connect the phone as MTP or USB-Storage mode.
Click to expand...
Click to collapse
KNOW How To Enter Device Specific Modes.
NOTE: The device MUST be powered OFF before you can enter below modes:
RECOVERY MODE (METHOD #1)
Press and hold [Power] while holding down [Volume Up/+], release all when REC booted.
RECOVERY MODE (METHOD #2)
Press and hold [Power] until it vibrates, immediately press & hold [Volume Up/+], release all when REC booted.
RECOVERY MODE (METHOD #3)
NOTE: This method only applicable if you have custom recovery installed on the device.
Press and hold [Power] while holding down [Volume Up/+] and [Volume Down/-], release all when REC booted.
RECOVERY MODE (METHOD #4)
NOTE: This method requires you to have adb driver & binary setup and working.
Open Windows Command Prompt and type "adb reboot recovery".
FASTBOOT MODE
Press and hold [Power] while holding down [Volume Down/-], release all when honor logo appears.
* NOT all ROMs support calling fastboot using this method.
SD UPGRADE MODE (METHOD #1)
1) Copy ROM upgrade file 'UPDATE.APP' to '/sdcard/dload/UPDATE.APP'.
2) Press and hold [Power] while holding down [Volume Up/+] and [Volume Down/-], release all when logo appears.
* You need stock recovery for this to work, if you flashed custom recovery this method won't work.
SD UPGRADE MODE (METHOD #2)
1) Copy ROM upgrade file 'UPDATE.APP' to '/sdcard/dload/UPDATE.APP'.
2) Create an empty text file and save it as 'au_temp.cfg', copy the file to '/sdcard/dload/au_temp.cfg'.
3) Start the device normally by pressing [Power] button only.
* NOT all ROMs upgrade can be called using this method, phone will boot normally if this is the case.
* Unlinke method #1 above, this method will work even you are not running stock recovery.
PRELOADER MODE
Simply connect the device to computer with USB cable while the device is powered off.
With Battery: Exit PRELOADER mode after a while and enter battery charging mode if no connection is made.
Without Battery: Keep restarting the phone (and vibrate) until a connection is made, eg: SPFT
* You MUST have MTK PreLoader USB VCOM driver installed for this to work.
* Although both methods would work, entering this mode without battery is preferred.
Click to expand...
Click to collapse
HAVE Downloaded My 'Honor3C' Project Folder With Tools.
* The project folder contains SP Flash Tool and some other tools to work with Honor3C ROMs.
* Download the project folder from HERE. (13.4 MB - Mediafire, password: [email protected])
* EXTRACT the downloaded zip and copy the project folder to root directory of your drive. (C:\, D:\, E:\)
* From now on, remember that this folder is to be called 'Honor3C project dir' in my guides.
Click to expand...
Click to collapse
CREATED Complete Backup (ROM Dump and Personal Files)
The following tools can be used to create full ROM dump of your existing ROM.
1) SP Flash Tool 'ReadBack' feature. (Can be used before first boot)
2) MTK Droid & Tools by rua. (Required a rooted device)
To backup personal files, you can use Hi-Suite. (Official software by Huawei)
Click to expand...
Click to collapse
UNDERSTAND That You May Lose Your Phone Warranty (By Unlocking)
.
ROM Backup using SP Flash Tool 'Readback' feature
IMPORTANT: MAKE SURE YOU HAVE CREATED A FULL ROM BACKUP BEFORE TRYING ANYTHING ELSE!
Backup your current ROM (Create ROM dump with SP FlashTool)
Warning:
* Files produced by this method are unsigned, thus it CANNOT be restored to a device with locked bootloader.
Tips:
* Since the unlocking method for this device has been found, the ROM dump can now be restored easily.
* It's recommended that you dump the ROM right after the phone comes out from the box.
* Only system and device specific data will be dumped, user data will be skipped.
* You can create another dump for userdata only should you think you need it. (For backup purpose only, not recommended for restore)
1) Open SP FlashTool, click [Scatter-loading] and browse to 'Honor3C' project main dir.
2) Select the default 'MT6582_Android_scatter.txt' and click 'Open'.
3) The partitions info should be loaded as shown below.
4) Now switch to [Read back] tab.
5) Clear all existing items in the list and click [ADD] button to create a new read back item.
6) Double click on the newly created item in the list. (Double click anywhere in the highlighted blue area)
7) Browse to 'Honor3C' project dir and select 'ROM_READ' and click 'Open'.
8) Change the output file name to 'ROM_FULL' and then click 'Save' button.
9) Edit the read back settings as following: (Type: Hex, Start Address: 0x0, Length: 0x62380000), then click 'OK'.
10) Double check everything is correct and press 'Read back' button or 'F10' on keyboard.
11) SP FlashTool is waiting for connection, now connect your phone to computer using USB cable, WITHOUT the battery inserted.
12) SPFT has successfully established a connection with the phone, the read back process will begin.
13) Read back in progress, this process could take 30 minutes or more, please be patience...
14) The following GREEN circle will be displayed if the read back succeeded.
15) Double check the output file has been saved successfully in 'ROM_READ' folder.
16) Now DISCONNECT the USB cable from your phone.
Click to expand...
Click to collapse
Process ROM Dump File (Convert Dump File To SPFT Flashable Files)
1) Check and make sure dumped file 'ROM_FULL' exists in 'ROM_READ' folder.
2) Now run 'dumpSplitter.exe' provided in the folder. (Required .NET 2.0+)
3) The program starts and begins splitting the ROM dump into it's individual partition.
4) The processed files will be saved in 'OUTPUT' folder.
4) Inside 'OUTPUT' folder you can find files that can be used to restore your android system.
5) Inside 'NoDL' subfolder you can find files that contain important data such as device IMEIs, vendor/id, etc.
6) Please keep ALL generated files, who knows you might need it someday.
Warning: DO NOT share files under folder 'NoDL' with people you don't know or don't trust.
Click to expand...
Click to collapse
Restoring ROM Dump (Using files generated from SPFT Read back)
Note:
* Make sure you have already processed the ROM dump file, eg: splitted it back to it's individual partition using provided tool.
Warning:
* You cannot and won't be able to restore from this backup unless your bootloader is/has been unlocked.
1) Open SP FlashTool, click [Scatter-loading] and browse to 'Honor3C' project dir, then select folder 'ROM_READ' and click 'Open'.
2) Select folder 'OUTPUT' and click 'Open'.
3) Select 'MT6582_Android_scatter.txt' found in 'OUTPUT' folder and click 'Open'.
4) The partitions info should be loaded as shown below. (If more than 2 items are unchecked, something is not right! Stop now!)
5) Click on the 2nd last item 'CACHE', browse to 'Honor3C' project dir, select folder 'URestore' and click 'Open'.
6) Select the file 'cache.img' and click 'Open'.
7) Now click on the last item 'USRDATA', this time select 'userdata.img' and click 'Open'.
8) Now ALL partition should have it's source defined, make sure the files path are similar to below.
9) Next, press [Firmware Upgrade] button or 'F8' on keyboard.
10) SP FlashTool is waiting for connection, now connect your phone to computer using USB cable, WITHOUT the battery inserted.
11) SPFT has successfully established a connection with the phone, the upgrade process will begin.
12) Upgrade in progress, this may take a few minutes...
13) The following GREEN circle will be displayed if the upgrade succeeded.
14) Now DISCONNECT the USB cable from your phone.
Click to expand...
Click to collapse
Unbrick, Unlocking Bootloader, Restoring Stock & Force Upgrade
Unbrick (Recover from a bootloop caused by installing custom recovery)
Note: This unbrick method will ONLY works if the bootloop was caused by installing custom recovery on device with LOCKED bootloader.
1) Make sure you have downloaded my 'Honor 3C' project folder and contain 'Unbrick' folder under it.
2) Open SP FlashTool, click [Scatter-loading] and browse to 'Unbrick' folder, enter into the dir.
3) Select 'MT6582_Android_scatter.txt' found in 'Unbrick' folder and click 'Open'.
4) The partitions info should be loaded with only 'RECOVERY' partition checked.
5) Now press [Download] button or 'F9' on keyboard to begin the writting procedure.
6) You will receive a warning message that not all images are loaded, click 'Yes' to continue.
7) SP FlashTool is waiting for connection, now connect your phone to computer using USB cable, WITHOUT the battery inserted.
8) SPFT has successfully established a connection with the phone, the writing process will begin.
9) The following GREEN circle will be displayed if the download succeeded.
10) Now DISCONNECT the USB cable from your phone.
11) Re-insert the battery into the phone and press power button, you should be able to boot normally again.
Click to expand...
Click to collapse
Unlocking Bootloader (For International aka MY/TW/Europe set ONLY)
Warning:
* Below steps are ONLY applicable to Honor 3C (H30-U10) that comes with locked bootloader.
* If you unlock the bootloader, you may void the warranty of your device.
Unlocking on this device consist of two parts:
1) Flashing a fully unlocked version of the bootloader.
2) Flashing an unlocked secro. (To work with the unlocked bootloader).
1) Open SP FlashTool, click [Scatter-loading] and browse to 'Honor3C' project dir, then select folder 'Unlock' and click 'Open'.
2) Select 'MT6582_Android_scatter.txt' found in 'Unlock' folder and click 'Open'.
3) The partitions info should be loaded as shown below.
4) Enable 'Write Memory' under [Window] drop down menu.
5) Switch to 'Write Memory' tab and click [Open raw data] button.
6) Browse to 'Honor3C' project dir and select folder 'Unlock' and click 'Open'.
7) Select 'preloader_huawei82_wet_jb5.bin' inside 'Unlock' folder and click 'Open'.
8) Now change Memory Setting to 'EMMC', Begin Address to '0x800' and Container Length to '0x1B0EC' as shown below.
9) Double check everything is correct and press 'Write Memory' button.
10) SP FlashTool is waiting for connection, now connect your phone to computer using USB cable, WITHOUT the battery inserted.
11) SPFT has successfully established a connection with the phone, the writing process will begin.
12) The following GREEN circle will be displayed if the writing succeeded.
13) Now DISCONNECT the USB cable from your phone.
14) Return to 'Download' tab and press [Download] button or 'F9' on keyboard.
15) You will receive a warning message that not all images are loaded, click 'Yes' to continue.
16) SP FlashTool is waiting for connection, now connect your phone to computer using USB cable, WITHOUT the battery inserted.
17) SPFT has successfully established a connection with the phone, the writing process will begin.
18) The following GREEN circle will be displayed if the download succeeded.
19) Now DISCONNECT the USB cable from your phone.
20) Your phone should be unlocked now, you may re-insert battery to boot normally or continue flashing recovery/ROM.
Click to expand...
Click to collapse
Restoring Official Stock ROM using SPFT (+Relocking The Bootloader) (Intl. Set)
Warning:
* This guide is ONLY applicable to Honor 3C (H30-U10) that comes with locked bootloader.
* DO NOT use this package on China set or other variants, YOU HAVE BEEN WARNED!
* Please note that the phone will be formatted prior to the installation, please make any necessary backup.
What's this all about?
* You can follow this guide to revert back to original stock ROM which can receive official local OTA updates from Huawei.
* This guide can also be treated as a Full Reset or Unbrick guide as you can use it to reload your whole system.
* The ROM we will be using is B108 signed ROM, which is believed to be identical to the one used to flash locked version of H30-U10.
Important Note:
* If your device come with B127 or B129, you MUST Force Upgrade to V100R001C900B127 after flashing B108. (To regain touch)
* If you receive error #6010 from SP Flash Tool while flashing, you MUST first do the following:
1) Load scatter file in 'UReflash' folder, make sure only 1 item is checked.
2) Press 'Download' and connect the phone to the computer with USB cable - without battery inserted.
3) Wait until the process complete and after that you may continue with below steps.
To relock the bootloader, you will need SPFT SIGNED ROM:
* For International sets or Europe sets that come with C432B109, use B108 SIGNED ROM. (761 MB)
* For Europe sets that come with C432B111, use B111 SIGNED ROM. (739 MB)
Once you have it, extract the zip content and move the extracted 'ROM_*' folder to 'Honor3C' project dir.
1) Open SP FlashTool, click [Scatter-loading] and browse to 'Honor3C' project main dir.
2) Select the extracted folder 'ROM_H30-U10_V100R001C900B108_SIGNED' and click 'Open'.
3) Select 'MT6582_Android_scatter.txt' found in the signed ROM folder and click 'Open'.
4) The partitions info should be loaded as shown below, make sure ALL items are checked.
5) Press [Firmware Upgrade] button or 'F8' on keyboard.
6) SP FlashTool is waiting for connection, now connect your phone to computer using USB cable, WITHOUT the battery inserted.
7) SPFT has successfully established a connection with the phone, the upgrade process will begin.
8) SP FlashTool will verify the input images and begin writing to the phone EMMC once the verification succeeded.
9) Upgrade in progress, this may take a few minutes...
10) The following GREEN circle will be displayed if the upgrade succeeded.
11) Now DISCONNECT the USB cable from your phone.
12) Re-insert battery to your phone, press [Volume Up] + [Power] button to enter recovery.
13) Perform a 'Factory Reset/Wipe data' before booting from the rom for the first time.
Click to expand...
Click to collapse
Restoring Official Stock ROM (+Relocking The Bootloader) (Europe Set - B109)
Warning:
* This guide is ONLY applicable to Honor 3C (H30-U10) EU set that comes with B109 & locked bootloader.
* DO NOT use this package on China set or other variants, YOU HAVE BEEN WARNED!
* Please note that the phone will be formatted prior to the installation, please make any necessary backup.
What's this all about?
* You can follow this guide to restore EU stock ROM which can receive official local OTA updates from Huawei.
* This guide can also be treated as a Full Reset or Unbrick guide as you can use it to reload your whole system.
* The ROM we will be using is B108+B109, which is believed to be identical to the one used to flash locked version of H30-U10.
Process Summary:
To relock unlocked EU set, we will need to first flash the Intl. B108 ROM as it's the ONLY relocking package we have.
Once we have (re)locked the bootloader, we can use Force Upgrade method to get C432B109 EU ROM restored.
Note: If you did not unlock bootloader but just want to reload B109 (eg: unroot), you can skip step #2.
1) Download stock ROM for your EU set V100R001C432B109 (UPDATE.APP format, 740 MB)
2) Follow the guide "Restoring Official Stock ROM using SPFT (+Relocking The Bootloader) (Intl. Set)"
3) Follow the guide "Force Upgrade / Installing ROM using UPDATE.APP" (Using B109 UPDATE.APP)
4) Boot into stock recovery & perform a Factory Reset before you start using the phone.
Click to expand...
Click to collapse
Restoring Official Stock ROM (+Relocking The Bootloader) (Europe Set - B111)
Warning:
* This guide is ONLY applicable to Honor 3C (H30-U10) EU set that comes with B111 & locked bootloader.
* DO NOT use this package on China set or other variants, YOU HAVE BEEN WARNED!
* Please note that the phone will be formatted prior to the installation, please make any necessary backup.
What's this all about?
* EU set that comes with B111 is believed to have different sensors with set that comes with B109.
* You can follow this guide to restore EU stock ROM which can receive official local OTA updates from Huawei.
* This guide can also be treated as a Full Reset or Unbrick guide as you can use it to reload your whole system.
* The ROM we will be using is B111, which is believed to be identical to the one used to flash locked version of H30-U10.
Process Summary:
To relock unlocked EU set, we will need to flash the B111 signed ROM.
1) Download stock ROM for your EU set V100R001C432B111 (739 MB)
2) Follow the guide "Restoring Official Stock ROM using SPFT (+Relocking The Bootloader) (Intl. Set)"
3) Boot into stock recovery & perform a Factory Reset before you start using the phone.
Click to expand...
Click to collapse
Restoring/Installing EMUI Stock ROM using SPFT (China Set / Unlocked Intl. Set)
Warning:
* DO NOT flash signed B108 on your China/clone set, YOU HAVE BEEN WARNED!
* For Intl. set users, your bootloader MUST be unlocked first before you can flash or use this guide.
* Please note that the phone will be formatted prior to the installation, please make any necessary backup.
What's this all about?
* You can follow this guide to revert back to stock ROM which can receive OTA updates from Huawei/EMUI.
* This guide can also be treated as a Full Reset or Unbrick guide as you can use it to reload your whole system.
* For Intl. set users, you may consider this as flashing unofficial ROM, tho, B11X ROMs are identical to official one.
Important Note:
* If you receive error #6010 while flashing, you MUST first do the following:
1) Load scatter file in 'UReflash' folder, make sure only 1 item is checked.
2) Press 'Download' and connect the phone to the computer with USB cable - without battery inserted.
3) Wait until the process complete and after that you may continue with below steps.
1) Download your desire version of ROM from EMUI.com. (开发版=Dev Build, 稳定版=Stable Build, 下载=Download)
2) Please continue with instructions found on post #7.
Click to expand...
Click to collapse
Restoring Single Partition using SPFT (NVRAM, PRO_INFO, ETC) (Restore IMEIs)
What's this all about?
* You can follow this guide to restore individual/single partition which cannot be restored using standard 'Download' method.
Warning:
* Usually you DO NOT need to use this function, except when you accidently wrote to wrong partition, or ran a Full Format through SPFP.
Tips:
* You will need backup file created by SPFT's Read back function, and processed by dumpSplitter. (You can also use files from MtkDroidTool)
* These special partitions backup files can be found under 'ROM_READ\OUTPUT\NoDL\' folder and start with 'nodl_' prefix.
* For this guide, i will be using NVRAM that stores calibration data, device IMEIs, etc as an example.
* You can also use the same method to restore almost all partition, provided that you know the start address of the target partition.
1) Open SP FlashTool, enable 'Write Memory' under [Window] drop down menu.
2) Switch to 'Write Memory' tab and click [Open raw data] button.
3) Browse to 'Honor3C' project dir and select folder 'ROM_READ' and click 'Open'.
4) Select folder 'OUTPUT' and click 'Open'.
5) Select folder 'NoDL' and click 'Open'.
6) Select the file 'nodl_NVRAM' and click 'Open'.
7) Change Memory Setting to 'EMMC', Begin Address to '0x1800000' and use File Size value as Container Length.
8) Double check everything is entered/selected correctly, then press 'Write Memory'.
9) SP FlashTool is waiting for connection, now connect your phone to computer using USB cable, WITHOUT the battery inserted.
10) SPFT has successfully established a connection with the phone, the writing process will begin.
11) The following GREEN circle will be displayed if the download succeeded.
12) Now DISCONNECT the USB cable from your phone.
Click to expand...
Click to collapse
Force Upgrade / Installing ROM using UPDATE.APP (Method #1)
What's this all about?
* Incase you haven't heard about 'UPDATE.APP', it's one of the format used by Huawei/OEM to pack ROMs & provide updates.
* This method requires a MicroSD with minimum size of 2 GB as the ROM itself could cost 1.2 GB for newer version of android, eg: KitKat.
* Under normal 'Local Upgrade' mode, you are ONLY allowed to upgrade if your current version is listed under the ROM's supported version.
* But with 'Force Upgrade', we can bypass version check and upgrade/downgrade to any supported ROM, as long as it's made for the device.
Warning
* You must be running stock recovery in order for this to work, otherwise use method #2 below to call this function.
* Although it's called 'upgrade', it's not actually an upgrade, it's more like a Full Reset as data partitions will be cleared.
* Make sure the phone is fully charged as the upgrade process is power-intensive and will drain your battery quickly.
1) Download the target ROM file, extract the zip, copy extracted 'dload' folder to SDCard as '/sdcard/dload/UPDATE.APP'.
2) Power off the phone, restart the phone by holding [Volume Up/+] & [Volume Down/-], then press & hold [Power] button.
3) The phone will be booted into recovery and the upgrade process will begin automatically.
* The upgrade process takes around 3-10 minutes depending on your memory card speed.
4) Once the upgrade process completed, a large 'OK' text similar to below will be shown and the phone will reboot by itself.
NOTE: If you are having International (aka MY/TW) set and upgrading to non-official ROM, you might also get the following error.
* The error was caused by missing preset in /cust partition specific for your country/region in non-official ROM, eg: ROMs from emui.com.
* Don't worry as it won't affect the phone basic functionality, just restart the phone manually if you get the error message.
Click to expand...
Click to collapse
Force Upgrade / Installing ROM using UPDATE.APP (Method #2)
What's this all about?
* Similar to method #1 above, this method can also be used to bypass version check when flashing 'UPDATE.APP'.
* Unlike method #1 above, this method calls the target ROM's recovery and enter SD Upgrade with the help of 'au_temp.cfg'.
* This method can be used even you are not using stock recovery, eg: installed a custom recovery.
* However, NOT all target ROM support calling upgrade using this method, if that is the case use method #1 above.
1) Download the target ROM file, extract the zip, copy extracted 'dload' folder to SDCard as '/sdcard/dload/UPDATE.APP'.
2) Create an empty file 'au_temp.cfg' and copy it to '/sdcard/dload/au_temp.cfg' alongside 'UPDATE.APP'.
3) Power off the phone, then start the phone normally by pressing [Power] button only.
4) The phone will be booted into recovery and the upgrade process will begin automatically.
* All remaining steps are similar to method #1 above. (Step 3 onwards)
Click to expand...
Click to collapse
Reverting to / Restoring Stock Recovery
What's this all about?
* Some people prefer custom recovery (eg: TWRP, CWM) over stock recovery because the earlier provides more functionality.
* However, custom recovery does not work well with Huawei specific update files, for eg: EMUI OTA zip and UPDATE.APP.
* Because of this you will need to restore the stock recovery before you perform any EMUI related update.
* Please note that the 'stock recovery' we are talking about is the 'Android system recovery <3e>'.
1) Download recovery flashable stock recovery 'UPDATE-RestoreStockRecovery_*.zip' from HERE.
2) Copy above .zip file to your external sdcard.
3) Boot into your custom recovery, eg: TWRP and flash (Install) the updater zip that you just copied.
4) If the flashing process completed successfuly, you should have the stock recovery restored to phone memory.
5) To confirm, back to [Home], enter '[Reboot/Power]' menu and choose 'Reboot into Recovery'.
Click to expand...
Click to collapse
EXTRA: Tips & Tricks
Format EMMC with SP Flash Tool (Single Partition)
What's this all about?
* This procedure help you to clear the target partition, once executed the target partition will be emptied and zero filled.
* Usually you do not need to run this, except when you messed up starting address when flashing, or facing data overlapping related issue.
* You can get partitions info like starting address and partition size/length by referring to scatter file for the device.
Warning:
* Your device needs to be UNLOCKED in order to perform this action.
For this guide i will be using (formatting) recovery partition as an example.
1) Open SPFT, click [Scatter-loading] and browse to 'Honor3C' project dir, select 'MT6582_Android_scatter.txt' and click 'Open'.
2) The partitions info should be loaded as shown below.
3) Click on 'Format' button.
4) Switch to 'Manual Format', edit 'Begin Address' and 'Format Length' according to scatter file for the device.
5) Check 'Validation' and click 'OK' button.
6) SP FlashTool is waiting for connection, now connect your phone to computer using USB cable, WITHOUT the battery inserted.
7) SPFT has successfully established a connection with the phone, the formatting process will begin.
8) The following GREEN circle will be displayed if the format succeeded.
9) Now DISCONNECT the USB cable from your phone.
Click to expand...
Click to collapse
Format EMMC with SP Flash Tool (Full Format)
What's this all about?
* This procedure helps you to clear internal storage, once executed the whole EMMC except preloader sector will be emptied and zero filled.
* Usually you do not need to run this, except when you messed up starting address when flashing, or would like to start over from zero.
Warning:
* Your device needs to be UNLOCKED in order to perform this action.
* ALL data stored on EMMC, including but not limited to NVRAM (IMEIs), localization data, system files & userdata will be removed.
* Make sure you have created a ROM backup using SPFT Read back, a normal ROM upgrade is NOT enough to bring back your device.
1) Open SPFT, click [Scatter-loading] and browse to 'Honor3C' project dir, select 'MT6582_Android_scatter.txt' and click 'Open'.
2) The partitions info should be loaded as shown below.
3) Click on 'Format' button.
4) Switch to 'Auto Format', check 'Validation' and click 'OK' button.
5) SP FlashTool is waiting for connection, now connect your phone to computer using USB cable, WITHOUT the battery inserted.
6) SPFT has successfully established a connection with the phone, the formatting process will begin.
7) The following GREEN circle will be displayed if the format succeeded.
8) Now DISCONNECT the USB cable from your phone.
Click to expand...
Click to collapse
Factory Reset (Using Stock Recovery)
Factory Reset is recommended after you have just upgraded/installed a ROM, this can be done with both stock & custom recovery.
Everytime you exit from stock recovery, /data/cust will be updated, this could be useful if you have upgraded /cust manually.
1) Power off your phone, boot into recovery using key combinations of [Volume Up] + [Power]
If you are running 4.2.2 JellyBean Stock Recovery (B11X)
2) Use Volume +/- keys to move highlight to 'wipe data/factory reset', then press [Power] button to select.
3) Select 'Yes - delete all user data' and press [Power] button to confirm wiping.
4) The following message will be displayed if format process succeeded.
5) Select 'reboot system now' and press [Power] button to restart the phone.
If you are running 4.4.2 KitKat Stock Recovery (B6XX)
2) Use Volume +/- keys to move highlight to 'wipe data/factory reset', then press [Power] button to select.
3) Select 'Yes - delete all user data' and press [Power] button to confirm wiping.
4) The following message will be displayed if format process succeeded.
5) Select 'reboot system now' and press [Power] button to restart the phone.
6) If you receive the following error message, just repeat step #5 above.
* The above error was due to missing localization data in /cust partition, likely true if using non-official ROM on global set.
Click to expand...
Click to collapse
ALL About Recovery
Custom Recovery: Team Win Recovery Project (TWRP) 2.x
Ported with the help of @yuweng's Easy Magic TWRP Installer, further improved to work better with Honor 3C.
Reminder: Before making any backup with this recovery, remember to change storage location to Micro-SD
Click to expand...
Click to collapse
Custom Recovery: Carliv CWM Based Recovery v6
Ported using files provided by Carliv, please visit Carliv's thread for more information about this recovery.
Click to expand...
Click to collapse
Custom Recovery: Carliv Touch Recovery (CTR) 1.4
Ported using files provided by Carliv, please visit Carliv's thread for more information about this recovery.
Note: Touch buttons are not functioning, use volume & power keys to navigate; This version has no gzip compression support.
Click to expand...
Click to collapse
Running Live Recovery: Use TWRP without flashing the recovery to device
Tips: MicroSD card is needed to run recovery using this method.
1) Download Live TWRP provided on this thread, extract the zip & copy 'dload' folder to to your SDCard.
2) Make sure there are 2 files under the folder /sdcard/dload/, which are: au_temp.cfg & UPDATE.APP.
3) Also copy any UPDATE.ZIP that you want to flash via recovery to SDCard. (Eg: UPDATE-SuperSU-*.zip)
4) Now power off the phone and press power button to restart the phone.
5) Instead of booting normally the phone will be booted into Live TWRP Recovery.
6) Now do whatever you want with the recovery, eg: flash update.zip, backup, restore, etc.
7) When you are done with recovery:
A) If you are using my LiveTWRP 2.8.1.0 & above, skip step 8-13 and jump to step #14.
B) If you are using my LiveTWRP 2.7.1.0 / 2.8.0.0, continue with the following steps.
For LiveTWRP 2.8.0.0 & below, you MUST delete 'au_temp.cfg' in SDCard before restarting the phone.
8) To do so, touch the 'Home' icon to return to main menu, then touch 'Advanced' button.
9) Touch 'File Manager' button.
10) Browse to '/sdcard/dload/', find the file 'au_temp.cfg' and touch on it to bring up the actions menu.
11) Now touch 'Delete' button on the actions menu.
12) Confirm file deletion by swiping the blue icon.
13) Now you can boot normally again, touch 'Home' icon to return to main menu.
14) Touch 'Reboot' button to enter the reboot menu.
15) You can choose to Power off the device or reboot into android system directly, it's up you.
Click to expand...
Click to collapse
Installing Custom Recovery: Flashing custom recovery to device with SPFT
Warning:
* Your bootloader MUST be unlocked before you install custom recovery on your phone, otherwise you will get a bootloop.
Tips:
* If you just want to use custom recovery but do not want to unlock your device, use Live Recovery instead.
1) Download your favorite custom recovery from this thread, eg: TWRP, and extract the zip content to 'Honor 3C' project dir.
2) Open SP FlashTool, click [Scatter-loading] and browse to 'Honor3C' project dir, then select recovery folder and click 'Open'.
3) Select 'MT6582_Android_scatter.txt' found in the recovery folder and click 'Open'.
4) The partitions info should be loaded as shown below, press 'Download' or 'F9' on keyboard.
5) You will receive a warning message that not all images are loaded, press 'Yes' to continue.
6) SP FlashTool is waiting for connection, now connect your phone to computer using USB cable, WITHOUT the battery inserted.
7) SPFT has successfully established a connection with the phone, the download process will begin.
8) Download in progress, this may take a few seconds...
9) The following GREEN circle will be displayed if the download succeeded.
10) Now DISCONNECT the USB cable from your phone.
Click to expand...
Click to collapse
Using Custom Recovery: Root & Install SuperSU with TWRP (Full Root)
Tips:
* You can use Live Recovery if you do not have custom recovery installed. (Works for EMUI 2.0, 2.3 4.9.x & below)
* For Honor 3C europe set of with build number of V100R001C432B1XX, please read this post before you proceed.
1) Download latest SuperSU from Chainfire's thread. (Get 'CWM / TWRP / MobileODIN installable ZIP' version)
2) Copy the downloaded UPDATE-SuperSU-*.zip to root dir of your SDCard as shown below.
3) Next, download 'UPDATE-FullRootHelper*.zip' from this thread and copy to SDCard like you just did.
4) Power off your phone, boot into custom recovery using key combinations of [Volume Up] + [Power]
5) Touch [Install] button.
6) Browse to '/external_sd' and touch on 'UPDATE-SuperSU-*.zip'.
7) Make sure 'Zip file signature verification.' is unchecked, then confirm flashing.
8) If flashing succeeded the word 'Successful' will be displayed.
9) Now repeat step 5-6 and flash 'UPDATE-FullRootHelper*.zip'.
10) Now your phone is fully rooted, touch 'Reboot system' to restart the phone and boot normally.
Click to expand...
Click to collapse
Using Custom Recovery: Apply modem fix after installing non-official ROM
Warning:
* Apply this patch ONLY if your IMEIs are missing and 'No services' after you have just installed a non-official ROM.
* Please make sure you use the correct patch based on your phone variant, eg: Use ModemFix-EU if you have EU set.
Tips:
* MicroSD card is needed. (Although you may store the patch anywhere you can remember, and have write access to)
* Custom recovery is needed to apply this patch. (Live Recovery can be used if you do not have one installed)
1) Download 'UPDATE-ModemFix*.zip' provided on this thread.
2) Copy the patch 'UPDATE-*.ZIP' to the root dir of your SDCard as shown below. (Note: No need to rename)
3) Power off your phone and boot into custom recovery with key combinations of [Volume Up] + [Power] button.
If you are using TWRP recovery:
4) Touch [Install] button on home screen.
5) Use '(Up a level)' whenever needed to navigate back to root '/' directory.
6) Now that you are in '/', find and touch on 'sdcard' to enter the directory.
7) Touch on 'UPDATE.zip' to apply the fix.
8) Make sure 'Zip file signature verification.' is unchecked, then confirm flashing.
9) If flashing succeeded the word 'Successful' will be displayed.
10) Touch on 'Reboot System' to restart the phone.
If you are using CWM based recovery:
4) Use Volume +/- keys to move highlight to 'Install zip' and press [Power] button to select.
5) Select 'Apply /sdcard/update.zip' and press [Power] button to enter.
6) Select 'Yes' and press [Power] button to confirm flashing.
7) If flashing succeeded the following message will be displayed.
8) Use '<< Go Back' to return to main menu, enter 'Power Menu' and power off the phone.
Click to expand...
Click to collapse
Using Custom Recovery: Running Aroma File Manager
Tips:
* Aroma File Manager v1.8 work best with Honor 3C. (Download aromafm-1.80.zip)
* For CWM based recovery that supports calling Aroma FM directly, place the zip at /sdcard/clockworkmod/.aromafm/aromafm.zip
* For TWRP recovery, place the zip in sdcard root /sdcard/aromafm-1.80.zip and use [Install] function to call the app.
Click to expand...
Click to collapse
CHANGELOG
2014/10/06 - TWRP & LiveTWRP updated to v2.8.0.0, which has MTP support.
2014/10/08 - 'PermissionFix' updated to V3 but renamed to 'FullRootHelper' V1 to better reflect it purpose.
2014/11/05 - TWRP & LiveTWRP v2.8 updated to V2, optimized to work better with custom ROMs.
2014/11/14 - Added 'RestoreStockRecovery' zip, for more info please refer to the guide 'Restoring Stock Recovery'.
2014/11/19 - TWRP updated to 2.8.1.0, FullRootHelperV2 released, minor bug fix.
2015/02/17 - Added TWRP 2.8.1.0 optimized for EU set that comes with Build.no C432B111.
2015/04/18 - Updated TWRP 2.8.6.0, FullRootHelperV2d & update-binary. (Important: Read this)
2015/05/14 - Added ModemFix for CN & EU set; FullRootHelper updated to V2e with minor bug fix.
2015/05/15 - Updated TWRP for EU sets, now using B301 kernel which has proper SELinux support.
2015/08/06 - Added kernel (KernelSwapper) & modem (ModemFix) from latest official EU ROM - B306.
IMPORTANT NOTE
- ModemFix has been tested on unofficial EMUI 2.3 only, DO NOT flash it for more than 1 time.
- Please remember to switch your 'Storage:' in TWRP to external memory (MicroSD) before making backup.
- As of TWRP 2.8, external storage (MicroSD) will be mounted at /external_sd in recovery. (was on /sdcard)
- FullRootHelper might cause your next OTA to fail, this is unavoidable if you want full filesystem access on KitKat.
- Live TWRP no longer work with newer versions of EMUI released after October 2014. (4.10.x & above)
- For devices that come with build number B111 or B127, you must use EU version of the TWRP.
WARNING: Please DO NOT hotlink or mirror these files. Thank you for your cooperation.
Amaran: Hotlink/cermin file berikut adalah tidak diizinkan. / 警告: 以下文件不被允许转载, 谢谢合作
EXTRA: Working With UPDATE.APP - Making it flashable for SP Flash Tool
Part #1 - Converting Huawei UPDATE.APP to SP FlashTool Flashable Files
What's this all about?
* OK, now you know you can apply update using 'UPDATE.APP' by placing it in /sdcard/dload/ folder.
* But do you know there is another way to flash the images directly with computer? Yes there is, by using SP FlashTool.
* This can be quite useful (and dangerous too) as you can skip/bypass the version check enforced by Huawei/OEM.
* Other than that, this method can also be used to install non-official ROM, provided that the ROM is compatible with the device.
Warning:
* Make sure you use UPDATE.APP that was built for your device, in this case, Honor 3C (H30-U10)
For this guide, i will be using update package H30-U10_EMUI_2.3_4.7.16.zip Dev KitKat build (860 MB+) as an example.
1) Download 'Huawei Update Extractor' by @worstenbrood HERE, get the non-setup version. (Don't forget to thank him!)
2) Extract the program files to a new folder named 'HuaweiUpdateExtractor' under 'Honor3C' project dir as shown below.
3) Extract the downloaded update package 'H30-U10_EMUI_*.zip', locate the extracted folder 'dload' and open the folder.
4) Inside 'dload' folder you have 'UPDATE.APP', move the file into 'ROM_UPDATE' folder under 'Honor3C' project dir.
5) Now back to 'HuaweiUpdateExtractor' program folder and launch the program.
6) Set Profile to Unknown, click the browse icon, browse to 'ROM_UPDATE' folder, select 'UPDATE.APP' and click 'Open'.
7) The images list should be loaded as shown below.
8) Right click on any item to bring up the action menu, select 'Extract All' and click on it.
9) Browse to 'Honor3C' project folder, select 'ROM_UPDATE' and press 'OK' button.
10) Wait until the extraction complete, this may take a few minutes...
11) Extraction completed, close the extraction dialog and the main program.
12) Open 'ROM_UPDATE' folder and verify that all images were extracted. (Folder size should be doubled now)
13) Click on '_PrepareFiles.exe' provided in the folder. (Required .NET 2.0+)
14) Now the ROM files are ready to be loaded from SP FlashTool.
Click to expand...
Click to collapse
Part #2 - Flashing ROM using Files Exported From UPDATE.APP
Warning:
* Your device MUST be UNLOCKED in order to be able to flash using this unsigned ROM.
* Please note that ALL existing user data on the device will be removed as the partitions get formatted.
Tips:
* Although it's not compulsory but i recommend you to do a factory/data reset through recovery before booting the new rom for the first time.
* For international set users: If you are not flashing official ROM from Huawei, you will need to apply modem fix to regain call functionality.
Once you have prepared all the needed files from previous step, you can flash the ROM back to device.
1) Open SP FlashTool, click on [Scatter-loading] and browse to 'Honor3C' project dir, select 'ROM_UPDATE' folder and click 'Open'.
2) Select 'MT6582_Android_scatter.txt' found in the folder and click 'Open'.
3) The partitions info should be loaded as shown below, ALL items MUST be defined and checked.
4) Now press [Firmware Upgrade] button or 'F8' on keyboard.
5) SP FlashTool is waiting for connection, now connect your phone to computer using USB cable, WITHOUT the battery inserted.
6) SPFT has successfully established a connection with the phone, the upgrade process will begin.
7) SP FlashTool will format the target partitions first before writing to it.
8) Upgrade in progress, this may take a few minutes...
9) The following GREEN circle will be displayed if the upgrade succeeded.
10) Now DISCONNECT the USB cable from your phone.
Recommended extra steps
1) Re-insert battery to your phone, press [Volume Up] + [Power] button to enter recovery.
2) Perform a 'Factory Reset/Wipe data' before booting from the new rom for the first time.
Click to expand...
Click to collapse
EMUI 3.0 Summary & Extras Tips & Tweak
Honor 3C H30-U10 - Upgrading to EMUI 3.0
UPDATE: As of today 2015-07-15, official EMUI 3.0 for all H30-U10 variants are available on huawei/hihonor site.
Please follow the upgrade guide (.doc) provided in the update.zip package to upgrade instead. (SD Force Upgrade)
Important Tips:
* Please restore your stock recovery before performing the upgrade. (Tips: You can also use the recovery in the update package)
* Official EMUI 3.0 upgrade might fails if you have altered your system, in this case please extract & use SPFT to flash instead.
* Some update package might relock your bootloader and causing a bootloop, in this case please unlock your bootloader again to fix.
OLD GUIDES & ADDITIONAL PATCHES (For References ONLY)
* Upgrading to unofficial ROM - B301 EU Beta / B310 (Offcial for Middle East Countries)
* Upgrading to unofficial ROM - B320 (Offcial for South East Asian Countries)
* Standard Procedures for Installing Unofficial ROM (Now outdated)
- THIS GUIDE IS NO LONGER APPLICABLE AS OF NOW (JULY 2015) -
GUIDE: How to upgrade to unofficial KitKat for International set users + Custom ROM preview
Want to try out the latest unofficial EMUI 3.0 KitKat but the above guides are too complicated for you?
No problem! Let me summarize the upgrade process a little bit.
UPDATE: This guide is NOT suitable for devices that come with build number: B127/B129/B111. (Touch issue)
Prerequisites:
* Charge your phone, make some backups, sync your data, prepare a minimum 2 GB memory card.
* Download latest unofficial KitKat ROM in UPDATE.APP format from this page. (Press 'ROM包下载' under '稳定版')
* Download TWRP Live Recovery, gapps-kk-*-signed.zip, UPDATE-SuperSU*.zip & optional UPDATE-*Fix*.zip.
* Extract the downloaded KitKat ROM zip & copy 'dload' folder to memory card as /sdcard/dload/.
* Also copy all others UPDATE*.zip to root dir of memory card, eg: UPDATE*.zip, gapps*.zip
Step by Step:
1) Power off the phone, enter SD Upgrade mode by pressing & holding both Volume+/- & Power keys.
2) Wait until the upgrade process complete and choose 'reboot system now', then proceed to the EMUI setup.
3) Check if your IMEI is available, if IMEI is missing remember to flash 'UPDATE-ModemFix*' later.
4) Connect the phone with USB to PC & replace /sdcard/dload/ folder with the one from Live Recovery.
5) Now reboot the phone normally and you will be booted into Live Recovery automatically.
6) In TWRP, touch [Install] & apply all the UPDATE*.zip. (SuperSU -> Gapps -> FullRootHelper -> * ModemFix)
7) Reboot the device normally, done.
* Optional: ModemFix is ONLY applicable to International/Europe set users, only apply the fix if your IMEI is missing.
Warning:
Above steps can be done WITHOUT unlocking bootloader, HOWEVER, there are some limitations:
* You MUST NOT use 'Local Upgrade' or 'OTA' to perform update afterwards, otherwise a soft-brick *might* occurs.
* In order to be able to update through OTA, you MUST unlock the bootloader, then ALL update method can be used.
* To avoid such problem, it's recommended that you unlock the bootloader first before performing any upgrade.
* However, if you choose to unlock the bootloader, you may void the warranty of your phone, please decide wisely.
* Although reverting to factory ROM is possible, getting IMEIs back working in factory ROM is extremely tricky.
* DO NOT attempt to update to any unofficial ROM (including this one) if warranty is part of your concern.
Side Note:
* It's recommended that you to revert back to official KitKat once it's available. (Check your local huawei site)
P/S: I strongly recommend you to create a Full ROM dump using 'SPFT Readback' before you start flashing to device.
You can also use MTK Droid Root & Tools by rua to dump your current ROM.
Click the following link to visit the <Custom ROM Installation Guide>
Extra Tips & Tweaks: <Build.prop Changer for EMUI>
Extra Tips & Tweaks: <Kernel Swapper for Honor H30-U10>
.
WARNING: TO WHOM IT MAY CONCERN
If warranty is part of your concern, MOST guides provided in this thread are NOT suitable to you,
except the 'unbricking guide' and 'reflashing B108 factory ROM'.
Remember, you have been warned.
----------------------------------------------------------------------------------------------------------------------------------------------------------------
- GUIDELINE WHEN POSTING QUESTION / ASKING FOR HELP IN THIS THREAD -
To better understand the problem, please provide the following info when posting question / asking for help:
Code:
- Phone model:
- Phone Version:
- Initial Build Number:
- Last Build Number:
- Bootloader Status:
- Current Status:
- Problem/Question:
* Phone model: H30-U10 (Just to make sure you are in the right thread)
* Phone Version: International or China set. (Check post #1, if you still have no idea, tell us where you bought/imported from)
* Initial Build Number: The version when you first got the phone. (If you still remember, to help determine your H3C variant)
* Last Build Number: The last version number before having the problem.
* Bootloader Status: Still locked, or already unlocked (China set always unlocked unless you accidently flashed B108)
* Current Status: Bootloop (Logo) or softbrick (Vibrate only).
* Problem/Question: What you did last before the problem, eg, flashing, OTA, installed an app or something else.
-
restore
if i restore from a backup dump firmware which was the official my firmware, will it auto lock the bootloader too?
aminroslan said:
if i restore from a backup dump firmware which was the official my firmware, will it auto lock the bootloader too?
Click to expand...
Click to collapse
Hey, it's nice to see you here, good question you have there!
Well, to answer your question, theoretically yes, but the answer is NO.
Remember that i mentioned in the guide that you CAN'T restore from the SPFT Readback ROM dump if your bootloader is still locked?
The reason behind this is that the SPFT expects you to provide signed images as sources.
Since the dumped images are no longer signed, SPFT will not allow you to flash it, unless the dump was from an unlocked ROM,
Even if you managed to restore the files, you won't be able to boot the device either because the locked BL just won't work with these unsigned images.
BUT, if you are following my guide and use my tool to process the dump file, the output files will be a fully unlocked ROM instead.
The tool will helps you to replace all neccessary files and convert it to a fully unlocked ROM, which you can flash back to device, provided that your BL has been unlocked.
The ONLY known method to relock bootloader is by flashing the B108_Signed images which you can find in OP.
I hope this clarifies some of your doubts, let me know if you have any other question.
imei issue
i already flashed back to official signed firmware, but now my imei are both null. what do you think could be the cause of the problem?
EDIT*
OK i dont know what happened. now i got my IMEI back after flashing back to emui2.3
Big, Big THANKS
I just came upon this thread and I just want to say a big thanks for all that you have done here.
So much information in one spot is just fantastic.
Great Job !!!!
Recovery
Hi
I have a Chinese version of the 3C. I have installed all the different recoveries that you have and the only one I could get to boot was the TWRP.
Thanks for everything here
codelover said:
- Reserved for ROM Development -
Click to expand...
Click to collapse
Hi, i´m a developer for h30-u10 chinese version, I have a rom based at international updates, named ASAP. I´m thinking that I can make it for international users undone the port. There is any other problem with modroms like lost imeis?
Hi
Thanks for the this usefull thread.
I am using international version, can i Install
MIUI Rom in it after unlocking boot loader and flashing Custom Recovery?
And Custom ROMs are available for this cell or not
aminroslan said:
i already flashed back to official signed firmware, but now my imei are both null. what do you think could be the cause of the problem?
EDIT*
OK i dont know what happened. now i got my IMEI back after flashing back to emui2.3
Click to expand...
Click to collapse
If you flashed unofficial EMUI 2.3 KK ROM and applied ModemFix, you will need to flash official ROM (Eg: B115) before returning to the locked ROM.
BobBro said:
Hi
I have a Chinese version of the 3C. I have installed all the different recoveries that you have and the only one I could get to boot was the TWRP.
Click to expand...
Click to collapse
Yea, my CWM ports are based on International 4.2.2 ROM, so they might not be compatible with China set.
Anyway i have ported another one based on Carliv modified CWM, but using files from KK instead, would you mind to help me test it?
Since we have a working TWRP, the CWM based recoveries will be served as alternatives incase someone still prefer the old school style,
but please be reminded that these CWM ports are outdated and might contains bugs.
flufytendo said:
Hi, i´m a developer for h30-u10 chinese version, I have a rom based at international updates, named ASAP.
I´m thinking that I can make it for international users undone the port. There is any other problem with modroms like lost imeis?
Click to expand...
Click to collapse
Hey, nice to see you here! Some of my colleagues already tested your 6pack KK build, and they have good comments about it. :good:
About your question, if international set H3C user flashed emui.com's ROMs, the device will not be able to detect or read the IMEIs,
but the issue can be easily fixed by applying ModemFix provided on this thread. Regarding your ASAP ROM, i am not quite sure,
did you port that using ROM from huaweidevice.com.tw as base? if yes then should be no problem.
Btw, would you mind if i add your ROMs to OP under 'Flashable Custom ROM' section? Nice work btw.
Waqar90 said:
Hi
I am using international version, can i Install MIUI Rom in it after unlocking boot loader and flashing Custom Recovery?
And Custom ROMs are available for this cell or not?
Click to expand...
Click to collapse
Hi, i am not sure if there is any compatible MIUI ROM available for this device, as we just managed to unlock it.
But for custom ROM, yes, there are many ported from China ROM, you can also check out ROMs ported by @flufytendo.
Just another kind reminder, unlocking the device will void the phone warranty, decide wisely, and always make backup, rom dump, etc.
-
codelover said:
If you flashed unofficial EMUI 2.3 KK ROM and applied ModemFix, you will need to flash official ROM (Eg: B115) before returning to the locked ROM.
Yea, my CWM ports are based on International 4.2.2 ROM, so they might not be compatible with China set.
Anyway i have ported another one based on Carliv modified CWM, but using files from KK instead, would you mind to help me test it?
Since we have a working TWRP, the CWM based recoveries will be served as alternatives incase someone still prefer the old school style,
but please be reminded that these CWM ports are outdated and might contains bugs.
Hey, nice to see you here! Some of my colleagues already tested your 6pack KK build, and they have good comments about it. :good:
About your question, if international set H3C user flashed emui.com's ROMs, the device will not be able to detect or read the IMEIs,
but the issue can be easily fixed by applying ModemFix provided on this thread. Regarding your ASAP ROM, i am not quite sure,
did you port that using ROM from huaweidevice.com.tw as base? if yes then should be no problem.
Btw, would you mind if i add your ROMs to OP under 'Flashable Custom ROM' section? Nice work btw.
Hi, i am not sure if there is any compatible MIUI ROM available for this device, as we just managed to unlock it.
But for custom ROM, yes, there are many ported from China ROM, you can also check out ROMs ported by @flufytendo.
Just another kind reminder, unlocking the device will void the phone warranty, decide wisely, and always make backup, rom dump, etc.
-
Click to expand...
Click to collapse
For asap I have to fixing the same for China version (is really a c900b1 rom).
I tried your carliv cwm, carliv touch and twrp. The last only can use internal sd for backup and restore so it's a big problem because whenever you install a zip or restore all backups will be lost.
I'm using just now the carliv cwm at Chinese phone, I'll tell you about it . Edit: doesn´t work for intalling zips
For my roms I'd rather links to movilesdualsim, I'm from the staff so is better for our forum. But in the other hand I will do new tutorials for outdoor phones with your work, so as you wish.
one question, where come from the modem.img for fixing kk roms? from jb updates?
edit: kk carliv doesn´t work either for chinese version
Roms for h30-u10 outdoor and unlock bootloader
[CWM ROM] ASAP.b115.international.edition [JB4.2.2]
Please tell me if is working properly for adding to movilesdualsim and needrom
https://mega.co.nz/#!VQATBLAB!oKpuUmIabKQ1Oa9Rpahop1av3aGZ7HphuPAUE8WyUao
mirror https://drive.google.com/file/d/0B8CMz2uT6wvPODZaU1I2VnIyYlk/edit?usp=sharing
[CWM ROM] 6pack.international.edition [KK4.4.2]
Please tell me if is working properly for adding to movilesdualsim and needrom
link: https://docs.google.com/file/d/0B8CMz2uT6wvPZXBPRTJ0clNPQkE/edit?usp=docslist_api
Paypal donate link
Enviado desde mi H30-U10 mediante Tapatalk
"Yea, my CWM ports are based on International 4.2.2 ROM, so they might not be compatible with China set.
Anyway i have ported another one based on Carliv modified CWM, but using files from KK instead, would you mind to help me test it?
Since we have a working TWRP, the CWM based recoveries will be served as alternatives incase someone still prefer the old school style,
but please be reminded that these CWM ports are outdated and might contains bugs" by codelover
I would be happy to test out Carliv mod CWM.
Two of the custom roms on Needrom ask for CWM to install them with. Both failed the install with TWRP even though I was able to boot into one of them. I will let you know how the new recovery works.
UPDATE: I installed the recovery and I could get it to boot up and work fine. I tried to install 2 custom KK roms from Needrom and the install on both of them failed. When I tried to boot into them I got stuck on the Honor splash screen. I will try some other Chinese custom KK roms later and let you know how it goes.
My phone is a 3C H30-U10 Chinese version
Thanks again
We Were looking For you !!
@codelover ,
This is our thread
http://forum.xda-developers.com/showthread.php?t=2773098
we had begun from the time the International Version was released :laugh::good:
Alas we had been waiting for a Legendary Guide Like you !! .
Thanks for the HARD WORK , We H30 - U10 Owners will be trying out the methods u posted,
Simple Questions for You ? ( These were done by Me before you started this thread !)
Story !!---------------
1) when i flashed 4.7.1 ( i was on KK without Signal /IMEi)
2) Then i Restored the NVRAM Restore from MTK DROID , i was able to get a single IMEI for both Devices ,
i used KK and then recieved Chines OTA Updates , and did an OTA Update to 4.7.16
and that was last time my phone ever booted , next the phone restarted and it only kept vibrating
as the Boot Loader was locked, i couldnt do anything !...... Got my phone replaced by Service Centre
------------
Now the Question,
1) if i unlock the bootloader , would i able to relock it ? ( Very important Question )
2) Can we stay on 4.8.1 and keep updating KK as long as HUAWEI keeps giving new UPDATE.APP????
3) Could we get ever get back to B115 ( Pure Stock aka Virgin HUAWEI International)??
4) Would they be able to find out if the phone is unlocked ?
5) Will we get Android L this Decemeber ???
6) What are the Antutu Scores for the MIUI , other KK Roms ?
7 ) ..........To be Continued , My Boss was standing behind me as i typed the prev Question
PLease answer them !!!!
ANSWER THIS MOST IMPORTANT QUESTION !!
Steps planned for today :
1) Full ROM Backup
2) Unlock bootloader
3) Flash KK 4.8.1 using Forced SD Card Upgrade
4) Do a modem Patch if necessary
5) now incase the International ROM gets Official KK
HOW TO GO BACK WITHOUT LOSING IMEI AND HAVING A RELOCKED BOOTLOADER!!!!
Should i Flash B115 First ( Will it give me IMEI) ???
or after B115 should i Flash B108 ( To Get both IMEI & Locked Bootloader) ????????
PLEASE EXPLAIN THIS CLEARLY
The objective of this post is to explain how to currently install a custom ROM in our device. (for total newbies like me, you can also refer -among others- to my previous post). I give the general procedure which wipes everything in your device, but you can check various precious posts in xda that variate this procedure.
The codename for our device is "pollux_windy", which is the Wifi-only version. The LTE version (I should probably get the LTE!) is "pollux" and I suppose the general procedure (with the corresponding firmwares to your specific device) will work for any Xperia device. You can also get the general idea from this post.
As a general rule of thumb do not forget after/before every firmware flashing to:
Enable developer mode (explained here)
Enable the USB Debugging mode (explained here)
Trust installation from unknown sources (explained here)
Steps.
A. Unlock the bootloader.
You can refer here and then check that it is successfully unlocked with these steps (taken from here ):
Open the Contacts app.
Click the menu button.
Click Settings.
Long press (for about 5 seconds) somewhere in the empty space just above status bar, as indicated by the red frame in the screenshot below, and then release your finger. A button named Enter service code will then appear in the same area (this may take a few tries).
Click Enter service code. A dialler will appear.
Dial *#*#7378423#*#* . Then go to -> "Service Info" -> "Configuration". If there is:
Bootloader unlock allowed - Yes << this means that your Bootloader is Locked
Bootloader Unlocked - Yes << this means that your bootloader is unlocked
B. Flash a firmware in which you will root the device
Download/install FlashTool.
Download and place to the FlashTool's folder "firmwares" the firmware "SGP312_10.5.A.0.230_VMo UK_IE.ftf". More information here . In sort, download and extract http://d-h.st/MrI and http://d-h.st/ULc
Open FlashTool and connect the powered-off device (USB cable) in Flashmode, holding the Volume Down button while you plugin the usb cable. The FlashTool should say that it is connected in Flashmode. Then flash the 10.5.A.0.230 firmware in it.
C. Gain root to the new firmware
Open the device, complete the setup wizard and connect to a wireless network. You do not have to setup the Google Account since you can download every application googling the respective APK files, but Google Play is easier to use.
Get (click λ) the towelroot APK, install it and run it (click "make it rain"). You should have root, which you can check with a Root Cheker like this one.
Download/Install SuperSU APK (this is actively developed, while SuperUser is abandoned at the moment) as described here.
D. Install a Recovery to easily flash new ROMs
NUT has done excellent work with XZDualRecovery.Follow the instructions for installing it in his thread. In short:
Download the installer, run it and follow its instructions.
Select SuperSU and of course grant access to your computer from your tablet (watch the tablet screen).
E. Download a Custom ROM and Google Apps
I had problems with Cyanogenmod (versions 11 and 12) that I cannot explain. I had no GPS and no media sound from the speakers, but I did have "notifications" sound! I could listen to "media" sounds using headphones, though. So I tried the nightly OmniROM which seems very stable and fast at the moment, with no sound problems and also has a working GPS! You can get it directly from their site (the NIGHTLY I downloaded is omni-4.4.4-20150223-pollux_windy-NIGHTLY.zip which runs just fine). Somewhere I read that PacMan ROM - also works perfectly but I have not tested it yet.
I had device recognition problems from the Recoveries ("Status 7 Error") that I think dear NUT will solve promptly. What I did to solve them is
Upack the ROM zip.
Remove the first line (from assert(...); till the column) of META_INF/com/google/android/updater-script and save the file.
repack the ROM to a zip.
Then copy this zip to your external SD card. If you need google apps (you probably do, to use Google Play instead of other applications like Aptoide), you will also need to download and place to your external SD card the corresponding google apps from here - (I found it in this post - which also explains the different gapps versions)
F. Install the Custom ROM
So now that both the ROM and (optionally) gapps are in the device's SD card:
Enter the Recovery while repeatedly pressing Volume Up or Down while the device boots.
Wipe everything (except the external SD card, obviously --- if you delete the zip files by mistake you must begin again from step B. using the FlashTool to flash the *.230* ftf).
Reboot and setup/enjoy your new ROM.
It seemed that with OmniROM I had lost root access so I had to reinstall SuperSU. I did this by downloading the flashable/installable zip - and flashing/installing it through the recovery.
In the end a did a full backup with the TWRP recovery and one with Titanium backup
Magnus_E said:
The objective of this post is to explain how to currently install a custom ROM in our device. (for total newbies like me, you can also refer -among others- to my previous post). I give the general procedure which wipes everything in your device, but you can check various precious posts in xda that variate this procedure.
Click to expand...
Click to collapse
For installing customs (CM/AOSP/GPe based ROM's), you don't need to install .230 firmware, furthermore you don't need root (except for backup TA procedure), furthermore you don't need XZDualRecovery (cause it works only for Stock and Custom STOCK based rom's - see this post).
So you you only need to flash kernel via fastboot, and then enter recovery (integrated in kernel), and install .zip with custom, SuperSU and Gapps from there.
hello i was following this guide but im stuck on status 7 error, i tried deleting assert but the twrp recovery dont get any answer to "getprop ro.product.device" and it just doesnt proceed...
and Rootk1t i cant find any kernels flashable via fastboot or flashtool can you point one to me? all of the kernels i see are in '.zip's .... i want to have android 6.0 so i think i should have black kernel but how?
bluealef said:
hello i was following this guide but im stuck on status 7 error, i tried deleting assert but the twrp recovery dont get any answer to "getprop ro.product.device" and it just doesnt proceed...
and Rootk1t i cant find any kernels flashable via fastboot or flashtool can you point one to me? all of the kernels i see are in '.zip's .... i want to have android 6.0 so i think i should have black kernel but how?
Click to expand...
Click to collapse
.zips are installed through recovery, .ftf through flashtool.
6.0.1 ROM you can find here.
Rooting VK810 official stock release 11A (11A is chosen for two reasons: 1. because it's easiest to root with the Stump app and 2. because on anything newer than 11A, you'd have to manually downgrade the bootloader before being able to install TWRP the first time):
1. On the tablet, download the Stump app from http://forum.xda-developers.com/lg-g3/orig-development/root-stump-root-lg-g3-sprint-verizon-t2850906
Credit and thanks @jcase, IOMonster , @autoprime and @PlayfulGod. Credit and thanks azureflux for the music although personally I turn the volume down all the way.
2. Install the Stump app you downloaded. Android should prompt you that it's an app from an unknown source since you didn't download it from the Play Store. It should direct you to the Security Settings option "Unknown sources" which you should checkmark and then attempt again to install the Stump app.
3. Launch the Stump app.
4. Turn the volume all the way down if you want because the music can be annoying for the duration necessary to root the VK810.
5. Choose "Grind".
6. Choose "Brute Force".
7. On the VK810, it can take up to 20 minutes at which time the Stump app should say to reboot the device to implement the root.
8. Once the device is rebooted, go to the Play Store and install SuperSU from https://play.google.com/store/apps/details?id=eu.chainfire.supersu&hl=en
Alternatively you can download the latest non-beta SuperSU zip from http://download.chainfire.eu/supersu (XDA thread with this link at http://forum.xda-developers.com/showthread.php?t=1538053), extract the zip and install the SuperSU app, or the latest Beta version from a link in @Chainfire 's thread at http://forum.xda-developers.com/apps/supersu/2014-09-02-supersu-v2-05-t2868133.
You'll also need this SuperSU.zip for step 8 of the fourth post "Flash to the latest stock ROM so that you can have it with root".
Credit and much thanks to @Chainfire !!!
9. Launch SuperSU, confirm the prompt to update binaries.
Installing the initial (necessary) TWRP v2.7.0.1 and updating it to the latest TWRP v2.8.7.0:
http://forum.xda-developers.com/showpost.php?p=64577888&postcount=3
Installing the initial (necessary) TWRP v2.7.0.1 and updating it to the latest TWRP v2.8.7.0:
1. On the tablet, download the "VK810_twrp_2.7.0.1.zip" from http://forum.xda-developers.com/showthread.php?t=2726707
Credit and thanks teamwin , @Drgravy , @djrbliss , @Dees_Troy , @id10terror and @traccdma !
The link is in the "DOWNLOAD" section below the "DISCLAIMER" towards the bottom of the first post.
Credit @Drgravy for the original instructions but I prefer to run the commands directly on the device instead of from a PC via USB Cable and ADB.
2. Download TWRP v2.8.7.0 from http://forum.xda-developers.com/lg-g-pad-83/orig-development/recovery-twrp-2-8-7-0-t3150812
Credit and thanks @AndroidUser00110001 !
3. Install "X-plore File Manager" from the Play Store at https://play.google.com/store/apps/details?id=com.lonelycatgames.Xplore&hl=en
Credit and thanks Lonely Cat Games!
4. While you're in the Play Store, install "Terminal Emulator for Android" https://play.google.com/store/apps/details?id=jackpal.androidterm&hl=en
5. Launch X-plore.
6. Enable root mode in X-plore:
6A. Click the three-dot menu button in X-plore's upper right corner.
6B. Choose "Configuration".
6C. In the "Root access" section, click the gray area below it and choose "Superuser + mount writable".
6D. Give X-plore SuperUser permissions by choosing "Grant" in the SuperSU prompt that pops up. It might not open this prompt until a later step when you actually access root.
7. Find the "VK810_twrp_2.7.0.1.zip" file you downloaded in step 1 above. It should be on your internal storage in the Download folder.
8. Click once on the zip file - this will show you the files contained in it.
9. Navigate to the other file manager pane by choosing "SWITCH PANE" in the upper right corner.
10. Choose "Internal storage".
11. Navigate to the original pane by choosing "SWITCH PANE" again.
12. Select all the files inside the zip.
13. Choose the "Copy" icon in the toolbar on the right or left side of the screen. Choose "OK" at the confirmation prompt.
14. Now navigate to root. Give X-plore SuperUser permissions by choosing "Grant" in the SuperSU prompt that pops up.
15. From root, navigate to data/local/tmp.
16. "SWITCH PANE" to where you extracted the files from the zip.
17. Select "loki_flash" and "twrp.lok".
18. Choose the "Copy" icon in the toolbar on the right or left side of the screen. Choose "OK" at the confirmation prompt.
19. Launch "Terminal Emulator" installed in step 4 above.
20. In Terminal Emulator type (make sure no typos, or can copy/paste to be sure):
Code:
su
cd /data/local/tmp
chmod 777 loki_flash
./loki_flash recovery /data/local/tmp/twrp.lok
reboot recovery
Instead of "reboot recovery" you can use an app such as "Quick Reboot" from the Play Store at https://play.google.com/store/apps/details?id=phongit.quickreboot to reboot to recovery.
21. For getting to custom recovery with the tablet off, press and hold the Down Volume button. While continuing to hold the Down Volume button, press and hold the Power Button. The screen should come on in the stock-looking recovery and you can let go of both buttons). "Factory Reset" will no longer perform a Factory Reset. That's what you choose to get into custom recovery.
22. Update to to the latest TWRP v2.8.7.0 that you downloaded in step 2 above by (in TWRP v2.7.0.1) choosing "Install", navigating to where you downloaded the TWRP v2.8.7.0 zip (probably in internal storage in the Download folder), and choosing to flash the zip.
You can put a different custom recovery on the same way.
23. You can reboot into the newer TWRP by choosing the reboot recovery option.
Flash to the latest stock ROM so that you can have it with root:
http://forum.xda-developers.com/showpost.php?p=64601845&postcount=4
Flash to the latest stock ROM so that you can have it with root:
1. Download my ROM from my signature at the bottom of this post. I use ADM "Advanced Download Manager" from the Play Store at https://play.google.com/store/apps/details?id=com.dv.adm&hl=en, especially for downloading larger files like ROMs.
2. Check the MD5 Hash of the ROM zip:
2A. Copy (to the clipboard) the MD5 hash that I have in the filename of the ROM zip you downloaded in step 1 above.
2B. Install @scary alien 's "AFV File Verifier for Android" from the Play Store at https://play.google.com/store/apps/details?id=sa.afvx&hl=en.
2C. Run the AFV app.
2D. Choose "Input checksum for comparison".
2E. Paste the MD5 hash previously copied to the clipboard in step 2A above.
2F. Choose "Select File".
2G. Navigate to where you have the ROM zip.
2H. Long-press on the ROM zip and choose "Calc MD5 Checksum".
2I. When it's done calculating the MD5 hash of the ROM zip, it'll automatically compare it to the MD5 hash you pasted in step 2E above.
If the hashes match, the downloaded ROM zip is non-corrupt. If the hashes don't match, you have to re-download the ROM zip.
3. Optionally download one or more of my debloat zip files in the third post of my ROM thread in my signature below. If you don't flash my "no OTA" debloat zip, then don't take any OTAs you get offered if there are ever any more, or you might get soft bricked, which I won't go into recovering from here.
4. If you didn't already do so in step 8 of the second post "Rooting VK810 official stock release 11A", download the latest non-beta SuperSU zip from http://download.chainfire.eu/supersu (XDA thread with this link at http://forum.xda-developers.com/showthread.php?t=1538053) or the latest Beta version from a link in @Chainfire 's thread at http://forum.xda-developers.com/apps/supersu/2014-09-02-supersu-v2-05-t2868133.
5. Copy/move anything you want to keep from internal storage like the files you downloaded in the previous sections.
6. I strongly suggest wiping everything from TWRP (Data, Cache, System, Dalvik and Internal Storage). Wiping all of these things, especially if you use my debloat zip(s) will clear up garbage/folders that were left behind by previous bloat.
7. Flash my ROM.
8. Flash SuperSU.zip (downloaded in step 4 above). This step is VERY IMPORTANT if you want to get back into custom recovery without having to re-flash a stock ROM and go through the whole process again.
9. Optionally flash one or more of my debloat zip files. If you don't flash my "no OTA" debloat zip, then don't take any OTAs you get offered if there are ever any more, or you might get soft bricked, which I won't go into recovering from here.
Flashing the debloat zip(s) before the first boot of the ROM will give the advantage of never having the data/cache entries or internal storage folders for the debloated apps created, the latter is why I recommend a wipe of internal storage.
In order to get back into TWRP/custom recovery from rooted Lollipop or above ROMs:
http://forum.xda-developers.com/showpost.php?p=64601845&postcount=5
Thanks to @JBurch/cry for the monetary motivation to finally put this all together in one place!
There are THREE variants of the G Pad 8.3: The Verizon VK810.4G which has LTE, and the V500 and V510 WIFI-only models. These instructions are ONLY for the VK810.4G.
Please don't quote the whole OP.
FAQ: If you use files meant for anything else other than the VK810, you'll brick your tablet. This will be exhibited by the tablet showing up in Windows' Device Manager under "Other devices" as "QHSUSB-BULK". You will have to Google for "QHSUSB-BULK" to find out how to fix that. I've read about some having success doing so and others not. I haven't ever had to fix that so I have no personal experience with it and can only lead you to Google about it.
This requires a Windows PC, preferably Windows 7 or newer, to first downgrade your VK810 variant of the G Pad 8.3 to LG build 11A / Jellybean 4.4.2, to make it easiest to root and to put a custom recovery on.
Disclaimer: I am not responsible for whatever you do to your device. This is my preferred method and what I recommend.
Note: These instructions are still working in order to downgrade from official stock release 36B on the VK810 (codename "altev"), Verizon LG G Pad 8.3 LTE, to official stock release 11A in order to make it easiest to both root and install TWRP. You can then install any ROM you like including my newest stock ROM in my signature at the bottom of this post.
Downgrading/resetting to 100% official stock unrooted release 11A (11A is chosen for two reasons: 1. because it's easiest to root with the Stump app and 2. because on anything newer than 11A, you'd have to manually downgrade the bootloader before being able to install TWRP the first time):
1. On a Windows PC, preferably with Windows 7 or higher, download the latest Verizon-LG driver at http://www.lg.com/us/support-mobile/lg-LGVK810 (current version 4.0.3, direct download link if still working http://18d5a.wpc.azureedge.net/8018D5A/tool/dn/downloader.dev?fileKey=UW00520120427).
2. Install the driver.
3. Reboot the PC.
4. While you're continuing to follow the rest of the directions, might as well get the installed driver "loaded":
4A. Put the VK810 in Download mode:
4A1. Preferably using the original USB cable, or alternatively possibly a high-quality cable, connect the one end preferably to a USB 2.0 port on your Windows PC. Note: not all, but most USB 3.0 ports (to avoid for this process under normal circumstances) are blue in color whereas USB 2.0 ports are usually black.
4A2. Turn the VK810 off (within Android, long press the power button and choose "Power off").
4A3. The following is different from other G Pad 8.3 variants:
4A3a. Press and hold the Up Volume button.
4A3b. While continuing to hold it, insert the tablet end of the USB cable.
4A3c. You should feel the tablet vibrate and you can see a very dim, very faint graphic in the very center of the screen that says "Download Mode":
{
"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"
}
Credit and thanks @sevoan for posting the screenshot at http://forum.xda-developers.com/showthread.php?t=2782066
4A3d. Let go of the Up Volume button.
4B. Windows may take up to 10 minutes to finish loading the driver you previously installed. Every time you connect any USB device to a new/different USB port on a PC, Windows will have to take a longer loading the driver process.
5. Download the official stock release 11A KDZ for the VK810: https://www.androidfilehost.com/?fid=23991606952610809 (file name "5. VK81011A_01 - Jellybean 4.2.2.KDZ - MD5 hash inside - recommended for both ease of rooting and one less step to install the initial TWRP v2.7.0.1.7z")
If the previous link doesn't work, you can find it in my signature at the bottom of this post.
6. Download and install the free 7-Zip Windows program from ttp://www.7-zip.org"]http://www.7-zip.org[/URL]. Any version should work although you can only install the 64-bit version on 64-bit versions of Windows.
7. Use 7-Zip to extract the KDZ from the 7-Zip (7z) file downloaded in step 5 above. If you want to extract the 7-Zip on an Android device instead for some reason, use ZArchiver from the Play Store at https://play.google.com/store/apps/details?id=ru.zdevs.zarchiver&hl=en
8. LG Flash Tool 2014:
8A. On the Windows PC, download "LG Flash Tool 2014" from http://forum.xda-developers.com/showthread.php?t=2797190
Credit and thanks @quangnhut123
The MediaFire link is in step "3. Tutorial"
8B. Run "LGFlashTool2014.exe" as Admin: Right-click on "LGFlashTool2014.exe" and choose "Run as administrator". Provide Administrator credentials if necessary. If you get a UAC (User Account Control) prompt, click "Yes".
8C. If the program doesn't run, install the Visual C++ Runtime Library, also available in step "3. Tutorial" at the link in step 8 above, then repeat step 9.
8D. Screenshots also available at the link in step 8.
8E. "Select Type" should already be at the correct default "CDMA". Same for "PhoneMode" is "DIAG" and "Reset time" is "33000".
8F. Click the yellow folder icon to the right of the "Select KDZ file" field and choose the 11A KDZ file extracted from the 7-Zip archive you downloaded in step 5 above.
For reference: "CSE Flash" is what you should normally always use. "CSE Flash" will wipe your user data including your internal storage so be sure to move/copy anything you want to keep that's currently on your internal storage. "Normal Flash" is like a dirty flash. Your device will be restored completely to stock but will keep all of your user data including your internal storage. If you're downgrading stock ROM versions, you can expect "Normal" to result in a device that'll crash. If you do so, you can attempt a "Factory Reset" from the stock recovery (with the device off - long press the power button for 10 or so seconds until the device shuts off - press and hold the Down Volume button. While continuing to hold the Down Volume button, press and hold the Power Button. The screen should come on in the stock recovery and you can let go of both buttons). "Factory Reset" will of course wipe all user data including Internal Storage.
8G. Click "CSE Flash".
8H. On the "Read Phone Information" dialog which appears, do NOT press the "Read Phone Information" button. This has always crashed for me.
8I. Click "Start".
8J. On the next dialog, you can change the Country and Language if you like - either way doesn't make a difference. Click "OK".
VERY IMPORTANT: Once you click "OK", ignore any error dialogs that pop up. I mean every single one. Don't click any buttons in them, just drag them out of your way if necessary. 99.9% of the time, given enough time the device will be flashed successfully anyway. On the VK810, usually within 20 minutes. For comparison, on the VS985 Verizon LG G3, usually within 10 minutes.
Rooting VK810 official stock release 11A (11A is chosen for two reasons: 1. because it's easiest to root with the Stump app and 2. because on anything newer than 11A, you'd have to manually downgrade the bootloader before being able to install TWRP the first time):
http://forum.xda-developers.com/showpost.php?p=64577888&postcount=2
Installing the initial (necessary) TWRP v2.7.0.1 and updating it to the latest TWRP v2.8.7.0:
http://forum.xda-developers.com/showpost.php?p=64577888&postcount=3
Flash to the latest stock ROM so that you can have it with root:
http://forum.xda-developers.com/showpost.php?p=64601845&postcount=4
In order to get back into TWRP/custom recovery from rooted Lollipop or above ROMs:
http://forum.xda-developers.com/showpost.php?p=64601845&postcount=5
General thanks to, for my previous experience:
@AndroidFileHost for the Android File Host website and especially their changes allowing for the reorganization of already uploaded files.
@KyPbP for letting us know it's availability and giving the link to download the VK810 35A_08 KDZ. http://forum.xda-developers.com/showpost.php?p=60851710&postcount=108
@Revoe for letting us know the availability of the VK810 36B_00 OTA. http://forum.xda-developers.com/lg-g-pad-83/general/verizon-lg-g-pad-8-3-vk810-altev-ota-t3182449
@hsbadr for giving me permission to kang his Verizon G3 VS985 JasmineROM 7.0 update script for this use. http://forum.xda-developers.com/showpost.php?p=56005236&postcount=1
@rant for giving a link to the official Verizon PDF detailing 35B. http://forum.xda-developers.com/showpost.php?p=60857092&postcount=1 http://www.verizonwireless.com/dam/support/pdf/system_update/benefits-lg-g-pad-83-5-20-15.pdf
@DeanGibson for giving a link to the official Verizon PDF detailing this release. http://forum.xda-developers.com/showpost.php?p=62413430&postcount=2 http://www.verizonwireless.com/dam/support/pdf/system_update/benefits-lg-gpad-83-8-17-15.pdf
@Chainfire for SuperSU! http://forum.xda-developers.com/showthread.php?t=1538053
@Hnk1 for continued support, advise and ideas, and for experimenting to find out how to root 35A_08 without downgrading.
@xdabbeb for further knowledge about the partitions!
In order to get back into TWRP/custom recovery from rooted Lollipop or above ROMs:
1. Download the corresponding "aboot only" (aboot is the bootloader) found in the same place to download as my ROM zip. Corresponding means if you installed the latest 36B VK810 stock ROM, then download the 36B VK810 aboot zip file.
2. Download the 4.2.2 aboot package from http://forum.xda-developers.com/showpost.php?p=54533937&postcount=2
Credit and thanks @paperWastage !
The download link is about three quarters down in that second post.
3. Move this aboot.4.2.2.img file into the top of the internal storage (meaning, not in a folder).
4. In Terminal Emulator type (make sure no typos, or can copy/paste to be sure):
Code:
su
dd if=/sdcard/aboot.4.2.2.img of=/dev/block/platform/msm_sdcc.1/by-name/aboot
5. You can now reboot into recovery via your preferred method.
6. Once you're finished in TWRP, you need to re-flash the newer aboot zip downloaded in step 1 above. If you forget, the ROM won't boot. You should be able to long-press the power button to force the device off, then use the manual method to get back into TWRP mentioned in step 22 in the previous section above. Re-flash the newer aboot zip, then reboot from TWRP and the ROM will boot.
You can alternatively dirty flash my ROM zip instead of just the aboot. You'd have to re-flash SuperSU.zip and any debloat zips too.
Reserved
Update
Ok, so I installed TWRP and flashed the new version. I then cleaned out my internal memory and loaded several files to the external SD card for the final process. I flashed "ViKtory810ROM_v36B_00+5.0.2+with+36B+aboot+[no+custom+recovery+after]+-+MD5+50fe66dfd0b57a50694accef47263a94" first. Then I flashed "UPDATE-SuperSU-v2.46". Next I flashed "VK810.4G+36B_00+5.0.2+-+no+OTA+-+MD5+b031ab290cde9f6fa0e30db8ef61223a". Then flashed "VK810.4G+36B_00+5.0.2+debloat+-+all+EXCEPT+still+has+OTA+-+MD5+e215ad72cb4fc9d5841217faa5048444". Then I flashed "VK810.4G+36B_00+5.0.2+debloat+-+LG+apps+&+UI+sounds+-+MD5+9a15512ed7754ef7fccf8b017c631199". I flashed them in that order from TWRP v2.8.7.0. After reboot the new ROM loads up and it seems to be working ok except for one issue. I keep getting an error popping up that says "Unfortunately, the process com.android.phone has stopped. Then it shows activation complete and shows my phone number listed under that. After that the pop up appears and say Unfortunetly, the process com.android.phone has stopped. I clear the pop up and it says activating tablet again, then shows the activation complete with my phone number all over again. Then the pop up appears again. This is an endless cycle of happening. I haven't done anything on the tablet as of yet. I want to know what your thinking. Is there something I need to do with one of the settings? I'm also noticing its not connecting to the cell towers. Ok, hope you can help. Thanks again!
JBurch/cry said:
Ok, so I installed TWRP and flashed the new version. I then cleaned out my internal memory and loaded several files to the external SD card for the final process. I flashed "ViKtory810ROM_v36B_00+5.0.2+with+36B+aboot+[no+custom+recovery+after]+-+MD5+50fe66dfd0b57a50694accef47263a94" first. Then I flashed "UPDATE-SuperSU-v2.46". Next I flashed "VK810.4G+36B_00+5.0.2+-+no+OTA+-+MD5+b031ab290cde9f6fa0e30db8ef61223a". Then flashed "VK810.4G+36B_00+5.0.2+debloat+-+all+EXCEPT+still+has+OTA+-+MD5+e215ad72cb4fc9d5841217faa5048444". Then I flashed "VK810.4G+36B_00+5.0.2+debloat+-+LG+apps+&+UI+sounds+-+MD5+9a15512ed7754ef7fccf8b017c631199". I flashed them in that order from TWRP v2.8.7.0. After reboot the new ROM loads up and it seems to be working ok except for one issue. I keep getting an error popping up that says "Unfortunately, the process com.android.phone has stopped. Then it shows activation complete and shows my phone number listed under that. After that the pop up appears and say Unfortunetly, the process com.android.phone has stopped. I clear the pop up and it says activating tablet again, then shows the activation complete with my phone number all over again. Then the pop up appears again. This is an endless cycle of happening. I haven't done anything on the tablet as of yet. I want to know what your thinking. Is there something I need to do with one of the settings? I'm also noticing its not connecting to the cell towers. Ok, hope you can help. Thanks again!
Click to expand...
Click to collapse
You're welcome! Everything debloated in the LG/etc debloat zip is also debloated in the debloat All, FYI.
Sorry you're having trouble. I haven't had that experience at all. Did you wipe Data, Cache and Dalvik too? Sadly, without being able to fully use Android you won't be able to get back into TWRP since you have to temporarily redowngrade the bootloader (aboot.img) to get into it (the last section "In order to get back into TWRP/custom recovery from rooted Lollipop or above ROMs").
I know there's a way in Android to boot in a "safe mode" but I've only done it by accident and can't recall how. I don't know if that would make any difference anyway.
If you can use the hardware keys to get into the stock-looking recovery you could try re-wiping Cache but I wouldn't have much hope of that doing the trick, either.
I hate to say but if none of these things work the only way to get back into TWRP without the use of Android is to use LG Flash Tool 2014 to re-flash the 11A KDZ and start over.
I guess I'm going to have to write the detailed instructions for how to check MD5 hashes and add that into the OP, as that would be something I would ask if was done when anyone has problems after a flash.
@JBurch/cry I wrote up directions for checking MD5 hashes on Android - they're in the section for flashing my ROM. I realized that this won't help you in your current situation unless you take the MicroSD card out and put it in another Android device and check the hash on there.
I'm debating whether I should write up directions for checking MD5 hashes on Windows too.
So uh ya
roirraW "edor" ehT said:
You're welcome! Everything debloated in the LG/etc debloat zip is also debloated in the debloat All, FYI.
Sorry you're having trouble. I haven't had that experience at all. Did you wipe Data, Cache and Dalvik too? Sadly, without being able to fully use Android you won't be able to get back into TWRP since you have to temporarily redowngrade the bootloader (aboot.img) to get into it (the last section "In order to get back into TWRP/custom recovery from rooted Lollipop or above ROMs").
I know there's a way in Android to boot in a "safe mode" but I've only done it by accident and can't recall how. I don't know if that would make any difference anyway.
If you can use the hardware keys to get into the stock-looking recovery you could try re-wiping Cache but I wouldn't have much hope of that doing the trick, either.
I hate to say but if none of these things work the only way to get back into TWRP without the use of Android is to use LG Flash Tool 2014 to re-flash the 11A KDZ and start over.
I guess I'm going to have to write the detailed instructions for how to check MD5 hashes and add that into the OP, as that would be something I would ask if was done when anyone has problems after a flash.
Click to expand...
Click to collapse
So um ya, I failed to do what you stated on task 3 of your Rom installation. You told me to do this before installation:
3. I strongly suggest wiping everything from TWRP (Data, Cache, System, Dalvik and Internal Storage). Obviously, first copy/move anything you want to keep from internal storage like the files you downloaded in the previous sections. Wiping all of these things, especially if you use my debloat zip(s) will clear up garbage/folders that were left behind by previous bloat.
So.... I pulled a stupid.....When reading this I thought you meant to go into my folders "on the tablet" and manually delete the things I put in there. I didn't realise you meant to do it through TWRP before installation lol. So after coming to grips with the idea that I now need to start completely over,,,, I rebuilt the entire thing correctly in 20 minutes. Sad this took me 3 days to learn everything by reading over countless forums. Your help was absolutely necessary to bring it all together. My tablet is fully upgraded and that was the best money I've spent in along time. The next time i get a device, you'll get first crack at helping me. If everything goes well, I'll make sure to double the donation next time. Your experience is valuable and should come at a cost. Thank you and I look forward to talking with you in the future. Take care! Now to get busy using this thing.
JBurch/cry said:
So um ya, I failed to do what you stated on task 3 of your Rom installation. You told me to do this before installation:
3. I strongly suggest wiping everything from TWRP (Data, Cache, System, Dalvik and Internal Storage). Obviously, first copy/move anything you want to keep from internal storage like the files you downloaded in the previous sections. Wiping all of these things, especially if you use my debloat zip(s) will clear up garbage/folders that were left behind by previous bloat.
So.... I pulled a stupid.....When reading this I thought you meant to go into my folders "on the tablet" and manually delete the things I put in there. I didn't realise you meant to do it through TWRP before installation lol. So after coming to grips with the idea that I now need to start completely over,,,, I rebuilt the entire thing correctly in 20 minutes. Sad this took me 3 days to learn everything by reading over countless forums. Your help was absolutely necessary to bring it all together. My tablet is fully upgraded and that was the best money I've spent in along time. The next time i get a device, you'll get first crack at helping me. If everything goes well, I'll make sure to double the donation next time. Your experience is valuable and should come at a cost. Thank you and I look forward to talking with you in the future. Take care! Now to get busy using this thing.
Click to expand...
Click to collapse
Cool! Glad at least it was something simple, even if a little bit painful to fix. You must at least be a fast learner.
Maybe I'll separate that into two steps to distinguish them.
Enjoy! I hope we get 5.1.1 someday because 5.1.1 on the G3 is so much better than 5.0.x was. You're welcome and thank you! I never even took donations until a few months back when one or two people wanted me to.
Most of the time I enjoy just seeing someone successfully do whatever they're trying to do.
Thank you, I felt so much better using this than some sketch chinese program.
FL4NKENSTEIN said:
Thank you, I felt so much better using this than some sketch chinese program.
Click to expand...
Click to collapse
You're welcome! I know what you mean.
Hey. Not sure if I am posting in the correct thread so apologises if warranted.
I recently rooted my vk810 with king root. Seemed to be the only thing to work. Only after I rooted did I realize that king root probably was not the wisest way to go.
So I'm about to attempt to unroot and hopefully get this thing rooted and a decent rom working. I like the tablet but all the verizon crap and associated bloatware are driving me nuts.
A little background, I've used linux distros for a while now, but not comfortable with command line stuff. I'm that copy and paste guy...
Any ideas on where to begin? I see Mr warrior seems to be the guy. Just about all related searches end with a post by him. Kudos for helping everyone he has so far. People like him are the reason why the linux/android world is such a great place!
Thanks in advance!
Soundsofsublime said:
Any ideas on where to begin? I see Mr warrior seems to be the guy. Just about all related searches end with a post by him. Kudos for helping everyone he has so far. People like him are the reason why the linux/android world is such a great place!
Thanks in advance!
Click to expand...
Click to collapse
Just follow all of the directions in the first through fifth posts and they'll get you there. You'll need a Windows PC.
Some people have told about an app called "SuperSU Me" (not by @Chainfire) to replace Kingroot with SuperSU. I have no experience with that or links to it, however.
Thanks and you're welcome!
Lost on step 3.20
i think i messed up somewhere in the "VK810_twrp_2.7.0.1.zip" copy/paste section using X-PLORE. when i type in the "cd /data/local/temp" command in the emulator it
returns "sh: cd: /data/local/temp: no such file or directory". any help would be greatly appreciated.
for the record, this is my first time trying any type of root process.
thanks
***********************
update: i figured it out.
Slingb1ade said:
i think i messed up somewhere in the "VK810_twrp_2.7.0.1.zip" copy/paste section using X-PLORE. when i type in the "cd /data/local/temp" command in the emulator it
returns "sh: cd: /data/local/temp: no such file or directory". any help would be greatly appreciated.
for the record, this is my first time trying any type of root process.
thanks
***********************
update: i figured it out.
Click to expand...
Click to collapse
Thanks for the update. What did you figure out was the trouble? Didn't do the "SU" command first?
How to unlock boot loader anyone suggest me
zaccheo said:
How to unlock boot loader anyone suggest me
Click to expand...
Click to collapse
No one has done it. Someone more knowledgeable than I would have to tackle it.
roirraW "edor" ehT said:
Thanks for the update. What did you figure out was the trouble? Didn't do the "SU" command first?
Click to expand...
Click to collapse
i didn't pay attention to the provided instructions "20. In Terminal Emulator type (make sure no typos, or can copy/paste to be sure)"
i was typing temp, needed to type tmp.
Hello Guys,
At first a little background story:
I bought the Tablet 3 Month ago. I have got the Update to Android 6.0 in January and unfortunately, I applied it.
So If you don't want to apply a custom rom do not update to 6.0, because 5.1.1 is much better.
I am not responsible if anything goes wrong.
Ok, so let's get started:
At first you must install Minimal ADB and Fastboot on your PC/Laptop/Mac.
Windows: https://forum.xda-developers.com/showthread.php?t=2588979
Linux/Mac: http://rootmygalaxy.net/install-adb-and-fastboot-on-mac-or-linux/
Here is the link for all OSs: http://lifehacker.com/the-easiest-way-to-install-androids-adb-and-fastboot-to-1586992378
Before you can Root or flash a Custom Rom you must flash the recovery:
You will need:
-Nvidia Family Drivers(Extract it in a folder of your choice): http://nvidiashieldzone.com/files/shieldtv/shieldfamilydriver.zip not working anymore, official link:
http://developer.download.nvidia.com/mobile/shield/SHIELD_Family_WHQL_USB_driver_201801.zip
-As many of you are experiencing problems with my previously mentioned TWRP 2.8.7.3 version I am replacing the link with the official TWRP Shield Tablet Download Site. Just take the newest stable version: https://dl.twrp.me/shieldtablet/ (Put the file into the ADB+Fastboot Folder)
-TWRP 2.8.7.3 Recovery(Put the file into the ADB+Fastboot Folder): Download URL: https://www.androidfilehost.com/?fid=24269982087009777
Developer Post: http://forum.xda-developers.com/shi...recovery-twrp-2-8-7-0-touch-recovery-t3257172
Install the Drivers
Connect your Tablet to your PC
Windows:
Open your Device Manager
If there Is a device with a yellow ! klick on it and update the Drivers Manually(select the Folder where you extracted the Family Divers)
Linux:
You don't need any drivers
(For every fastboot command in ADB+Fastboot you will need a "sudo" in front of it...)
Mac:
You also don't need any drivers
(For every fastboot command in ADB+Fastboot you will need a "./" in front of it...)
Flash Recovery
1. Open Minimal ADB and Fastboot
2. Type in
Code:
adb devices
if you get a long term of numbers and letters your drivers are correctly installed, If this command does not bring up a device, check your cable connection and/or update your drivers again.
3. Now you must enable developer options on your SHIELD Tablet K1
3.1 Go to your Setting, scroll all the way down and choose Info(or similar)
3.2 Tap seven times on the Build Number
3.3 Now go back and now there is a new menu point Developer Options
3.4 Open them and Enable USB Debugging
4. Now type
Code:
adb reboot bootloader
EDIT: 4.1 To enable the fastboot protocol, you must select "Fastboot mode" on the Tablet. After that type
Code:
fastboot devices
in order to check if fastboot is enabled.
5. Before you can do anything you must unlock the Bootloader
5.1 Type in
Code:
fastboot oem unlock
5.2 Follow the Instructions on the Terminal(On your tablet: press the volume down button and then the power button)
6. Now you are ready to flash the recovery
6.1 Type in
Code:
fastboot flash recovery twrp-x.x.x-x-shieldtablet.img
6.2 Wait until it is finished then navigate with the volume buttons through the Menu on your Tablet and choose the option recovery mod with you power button
7. You are now in a custom Recovery on this point you must decide what you want to do:
-Do you only want to root your Device
-Or do you want to install a custom rom
Custom Rom
If you want to be on the safe side you should consider wiping the /data partition (Troubleshoot section at the end of the Post)
1. You can access your tablet from your PC
2. Now move your Custom rom to your internal or SD Card Storage
2.1 Download your custom rom of your choice.
2.1.1 Cyanogenmod 12.1 (Android 5.1.1) and BlissPop v4.0.3 https://www.androidfilehost.com/?w=files&flid=150249
2.1.2 Cyanogenmod 13.0 (Android 6.0) https://androidfilehost.com/?w=files&flid=27600&sort_by=date&sort_dir=DESC
2.1.3 Nvidia Shield Tablet Resurrection ROM (Android 6.x) https://androidfilehost.com/?w=files&flid=60681&sort_by=date&sort_dir=DESC
2.1.4 BlissPop
2.2 Download Google Apps (Gapps) (ARM Device)
2.2.1 Android 5.1 http://opengapps.org/?api=5.1&variant=stock
2.2.2 Android 6.0 http://opengapps.org/?api=6.0&variant=nano
2.3 Download Nvidia Apps (You still need to install Nvidia Shield HUB from the Play Store)http://forum.xda-developers.com/shield-tablet/development/shield-apps-cyanogenmod-12-t3070116
3. In TWRP click on Backup and Swipe to Back Up
3.1 Now go to Wipe. For a dirty flash you will only need to wipe the Dalvik and Cache for a full wipe select Dalvik, System, Data, Cache
4. After it has finished Click on Install and choose the .zip of your Custom Rom
4.1 To install the Google Apps click on Add More Zips and select the GApps zip
4.2 And again click on Add More Zips and select nvsystemservices.zip
4.3 now you can Swipe to Confirm Flash
Root
Download the Latest Stabel SuperSU file: http://download.chainfire.eu/supersu-stable and copy it to the internal or SD Card Storage
For Android 7.0 (Nougat) the SuperSU r4 2.78 version is confirmed working.
1. Open Minimal ADB and Fastboot
2. Type in
Code:
adb reboot recovery
to enter the recovery mode
3. In TWRP click on Backup and Swipe to Back Up
4. After it has finished Click on Install and choose the UPDATE-SuperSU-v2.65-20151226141550.zip (or similar) and Swipe to Confirm Flash
5. Restart you Tablet and now a new App SuperSU is Installed
Xposed Framework
Download the Xposed Framework Zip file, take the newest version:
(The Shield Quad Core has a 32 bit arm architecture, so you need the framework for arm)
SDK21 for Android 5.0: http://dl-xda.xposed.info/framework/sdk21/arm/
SDK22 for Android 5.1: http://dl-xda.xposed.info/framework/sdk22/arm/
SDK23 for Android 6.0: http://dl-xda.xposed.info/framework/sdk23/arm/
and the apk: https://forum.xda-developers.com/attachment.php?attachmentid=3921508&d=1477916609
and move them to you Tablet.
Developer Thread (for the uninstaller): https://forum.xda-developers.com/showthread.php?t=3034811
Go to Recovery with Root
1. Now that you have root you don't need you PC anymore. Go to the Play store and download Quick Boot
2. Open Quick Boot and klick on Recovery
3. Allow Root rights and the Tablet should boot into recovery
Go to Recovery without Root
1. Shut down your Tablet
2. Press and hold the Vol down button and the Power button until the Bootloader screen appears
3. Navigate with the volume buttons through the Menu on your Tablet and choose the option recovery mod with you power button
Install Xposed Framework
1. In the TWRP Recovery (Optionally you can make a Backup) select Install and choose the xposed-v80-sdk22-arm.zip file
2. When you get an Error let me know
3. Now Restart you Tablet and install the .apk file normally
4. In the App Press Framework and now there should be a green writing saying: Xposed Framework version 80 is active
5. Here is a list of very useful programs for the Xposed Framework: http://forum.xda-developers.com/android/general/best-xposed-modules-android-t3103027
Please Leave a post if you are getting errors or something isn't clearly explained! And if I could help you, consider giving me a Thanks
Troubleshoot
If you are stuck in a Bootloop:
Without data loss(e.g. when you installed Xposed framework zip and its stuck in a bootloop)
1. flash the stock rom boot image BUT ONLY IF YOU DONT USE A CUSTOM ROM (it will probably loose root). go to https://developer.nvidia.com/gameworksdownload#?search=SHIELD Tablet K1&tx=$additional,shield and download the latest NVIDIA SHIELD Tablet K1 Recovery OS Image
2. Unpack the zip file and flash it to your Tablet
Code:
fastboot flash boot boot.img
If something went wrong while flashing a custom rom (after that you will need to flash the custom/stock rom again)
wipe the /data partition. It could be encrypted from the previous rom. Be aware that you need to reinstall the rom, therefore loose all your data. Troubleshot guide by agentbob123
-Toby
Credits:
@xsquid mac support
@agentbob123 suggestion to mention to wipe the /data partition as a solution for being stuck in a bootloop
@champs777 suggested the newest TWRP
@grävling mentioned importance of waiting until the recovery flash is finished
Toby9 said:
Hello Guys,
At first a litte background story:
I bought the Tablet 3 Month ago. I have got the Update to Android 6.0 in January and unfortunately i applied it.
So If you don't want to apply a custom rom do not update to 6.0, because 5.1.1 is much better.
Ok, so let's get started:
I am not responsible if anything goes wrong.
At first you must install Minimal ADB and Fastboot on your PC/Laptop/Mac.
Here is the link for all OSs: http://lifehacker.com/the-easiest-way-to-install-androids-adb-and-fastboot-to-1586992378
Before you can Root or flash a Custom Rom you must flash the recovery:
You will need:
-Nvidia Family Drivers(Extract it in a folder of you choice): http://nvidiashieldzone.com/files/shieldtv/shieldfamilydriver.zip
-TWRP 2.8.7.3 Recovery(Put the file into the ADB+Fastboot Folder):
Download URL: https://www.androidfilehost.com/?fid=24269982087009777
Developer Post: http://forum.xda-developers.com/shi...recovery-twrp-2-8-7-0-touch-recovery-t3257172
Install the Drivers
Connect your Tablet to your PC
Windows:
Open your Device Manager
If there Is a device with a yellow ! klick on it and update the Drivers Manually(select the Folder where you extracted the Family Divers)
Linux:
You dont need any drivers
(For every fastboot command in ADB+Fastboot you will need a sudo in front of it...)
Mac:
2016/02/16 Please leave a post if you how to do this
1. Open Minimal ADB and Fastboot
2. Type in
Code:
adb devices
if you get a long term of numbers and letters your drivers are correctly installen, If this command does not bring up a device, check your cable connection and/or update your drivers again.
3. Now you must enable developer options on your SHIELD Tablet K1
3.1 Go to your Setting, scroll all the way down and choose Info(or similar)
3.2 Tap seven times on the Build Number
3.3 Now go back and now there is a new menu point Developer Options
3.4 Open them and Enable USB Debugging
4. Now type
Code:
adb reboot bootloader
5. Before you can do anyting you must unlock the Bootloader
5.1 Type in
Code:
fastboot oem unlock
5.2 Follow the Instructions on the Terminal(On your tablet: press the volume down button and then the power button)
6. No you are ready to flash the recovery
6.1 Type in
Code:
fastboot flash recovery twrp-2.8.7.3-shieldtablet.img
6.2 Wait until it is finished then move with the volume buttons through the Menu on your Tablet an choose the option recovery mod with you power button
7. You are now in a custom Recovery on this point you must decide what you want to do:
-Do you only want to root your Device
-Or do you want to install a cutom rom
Custom Rom
1. You can access your tablet on your pc
2. Now move your Custom rom to your internal or SD Card Storage
2.1 Download your custom rom of your choice. I decided to use Cyanogenmod 12.1 (Android 5.1.1) http://forum.xda-developers.com/shi...-cyanogenmod-12-shield-tablet-lte-na-t3055043
2.2 Download Google Apps (Gapps) (ARM Device) http://opengapps.org/?api=5.1&variant=stock
2.3 Download Nvidia Apps (You still need to install Nvidia Shield HUB from the Play Store)http://forum.xda-developers.com/shield-tablet/development/shield-apps-cyanogenmod-12-t3070116
3. In TWRP click on Backup and Swipe to Back Up
4. After it has finished Click on Install and choose the .zip of your Custom Rom
4.1 To install the Google Apps click on Add More Zips an select the GApps zip
4.2 And again click on Add More Zips and select nvsystemservices.zip
4.3 now you can Swipe to Confirm Flash
Root
Download the Latest Stabel SuperSU file: http://download.chainfire.eu/supersu-stable and copy it to the internal or SD Card Storage
1. Open Minimal ADB and Fastboot
2. Type in
Code:
adb reboot recovery
to enter the recovery mode
3. In TWRP click on Backup and Swipe to Back Up
4. After it has finished Click on Install and choose the UPDATE-SuperSU-v2.65-20151226141550.zip (or similar) and Swipe to Confirm Flash
5. Restart you Tablet and now a new App SuperSU is Installen
Please Leave a post if you are getting errors or someting isn't clearly explaned!
-Toby
Click to expand...
Click to collapse
My tablet just keeps rebooting to the lock screen whenever I try to go to recovery mode... Somehow twrp doesn't stick... It did when I was on Lollipop. I have already tried to flash the recovery, do a full reboot before trying to get in twrp but without success.
On mac
You dont need any drivers
(For every fastboot command in ADB+Fastboot you will need a ./ in front of it...)
example being ./fastboot oem unlock
xsquid said:
On mac
You dont need any drivers
(For every fastboot command in ADB+Fastboot you will need a ./ in front of it...)
example being ./fastboot oem unlock
Click to expand...
Click to collapse
Thank you I added this in guide
nielsscholte said:
My tablet just keeps rebooting to the lock screen whenever I try to go to recovery mode... Somehow twrp doesn't stick... It did when I was on Lollipop. I have already tried to flash the recovery, do a full reboot before trying to get in twrp but without success.
Click to expand...
Click to collapse
Try other TWRP versions like 2.8.7.0 or 2.8.7.1 i think the 3.0.0.0 is for Andoid 6.0 devices so if you are currently in the newest version of the Android OS try this one out
The 3.0 versionof TWRP was unstabel on my device so you should flash it wipe the storage and flash one of the older ones
nielsscholte said:
My tablet just keeps rebooting to the lock screen whenever I try to go to recovery mode... Somehow twrp doesn't stick... It did when I was on Lollipop. I have already tried to flash the recovery, do a full reboot before trying to get in twrp but without success.
Click to expand...
Click to collapse
3.0.0.0 wasn't out yet when I did mine but it was doing the same thing and this worked perfectly:
fards said:
Try deleting recoveryonboot.p in /system
Click to expand...
Click to collapse
Credit to fards.
xsquid said:
3.0.0.0 wasn't out yet when I did mine but it was doing the same thing and this worked perfectly:
Credit to fards.
Click to expand...
Click to collapse
How can I remove this file without root ?
SonicDBZFan07 said:
How can I remove this file without root ?
Click to expand...
Click to collapse
Try your normal command line for flashing recovery except change flash to boot. It doesn't flash it, just boots to it.
In other words, if you are using:
1. Fastboot Flash recovery recoveryname.img
Do instead:
2. Fastboot boot recovery recoveryname.img
While in recovery (make sure the supersu zip is on the sd card or wherever you normally flash files from first) flash supersu. You should now be rooted but without a recovery.
Go then to delete the file and then reboot, flash the recovery as normal (#1), reboot and then it should be good to go. It was for me.
rooted device no need to unlock bootloader it will unlock for ittself
just go to playstore and dowload twrp manager
choose the name of your device
and choose one of the two versions available
for shield tablet the version 3.0.0.0 doesnt work well it spilts the screen but wthe other version Works great
the link is twrpmanager on play.google
this way you dont need to connect your tablet to your pc
Great work!
Thank you for the awesome guide. Besides deleting the TegraOTA apk, is there any other app/service that I should disable to prevent OTA updates?
Followed the guide after screwing my device up with official firmware. Thanks for nothing Nvidia, why are you offering OTA that cause the device to stop working correctly.
Nothing happened other than appearing to boot itself to the "powered by android" (kernel) screen over and over.
Held down power + volume UP ...
And it factory reset itself.
Somehow.
Did I mention that Nvidia is a terrible company?
Edit: Fixed using TWRP v3.0.0 - this guide should be updated to reflect this particuarly as people who screw their device up after trusting Nvidia OTA MM will be using it.
diji1 said:
Followed the guide after screwing my device up with official firmware. Thanks for nothing Nvidia, why are you offering OTA that cause the device to stop working correctly.
Nothing happened other than appearing to boot itself to the "powered by android" (kernel) screen over and over.
Held down power + volume UP ...
And it factory reset itself.
Somehow.
Did I mention that Nvidia is a terrible company?
Edit: Fixed using TWRP v3.0.0 - this guide should be updated to reflect this particuarly as people who screw their device up after trusting Nvidia OTA MM will be using it.
Click to expand...
Click to collapse
I'm sorry that you had that problem but this guide is a general guide and not an screw nvidia (besides they are awesom giving us a really good tablet for 200 Buck, but jea?) guide. TWRP v3.0.0 has his bugs so generally when you have finished deleting the stock rom you should flash TWRP 2.8.7.3 works the most stabel.
Trafalgar Square said:
Great work!
Click to expand...
Click to collapse
Thanks, i appreciate that
Add TWRP to M image (Shield 1.1)
Folks,
Just received Nvidia Shield K1 and OTA immediately upgraded it to M (Shield 1.1) and I unlocked bootloader no problem. However when I go to flash or temp boot twrp 2.x or 3.x it flashes OK, but when I reboot (either via fastboot or hard off/start to recovery manually) it appears it is overwriting the recovery partition and it just boots normally.
Is there a limitation to flashing twrp bootloader in M, and do I have to downgrade to L to flash recovery partition?
I seem to be happy w/ stock (limited stick time), I just want to root at this point and install my favs. Once I get this running will supersu pro preserve root, or do I need to turn off nvidia OTA process.
Also I see optimization for chrome, does this do anything X1 optimizations)?
Thanks
psychic99 said:
Folks,
Just received Nvidia Shield K1 and OTA immediately upgraded it to M (Shield 1.1) and I unlocked bootloader no problem. However when I go to flash or temp boot twrp 2.x or 3.x it flashes OK, but when I reboot (either via fastboot or hard off/start to recovery manually) it appears it is overwriting the recovery partition and it just boots normally.
Is there a limitation to flashing twrp bootloader in M, and do I have to downgrade to L to flash recovery partition?
I seem to be happy w/ stock (limited stick time), I just want to root at this point and install my favs. Once I get this running will supersu pro preserve root, or do I need to turn off nvidia OTA process.
Also I see optimization for chrome, does this do anything X1 optimizations)?
Thanks
Click to expand...
Click to collapse
After you flash twrp reboot to recovery. I may be wrong, but I think the stock ROM overwrites the custom recovery at reboot. If you reboot to twrp first after flash, twrp will disable this.
Sent from my SHIELD Tablet K1 using Tapatalk
Rooting
Hi everyone,
Yesterday got my new Nvidia Shield Tegra K1 and upon using it I noticed it's a great tablet for it's price range and will do my job easier while flying my Phantom 4. To be honest it's seems very stable and solid but was thinking about rooting it. I have some questions regarding the process wince I haven't rooted anything since my HTC Fire, log time ago that was. What are the benefits of rooting this device ? Will I still be able to update the Shield with its official updates ? Will I be able to roll back to an unrooted tablet should I need too ? I wasn't planning on flashing a custom rom but if I'll do what are the pros and cons of doing so ? I know that maybe searching this forum I would find all the answers needed but since there is so much information and threads I'm lost as from were to start from.
Would be nice to guide me about how to properly root my device with all the necessary links. My tab is running on Android 6.0.
I thank you so much guys for the hard work you all do in providing such information. I know it takes a lot of time and patience.
I just got a Shield K1. I like it a lot but I wanted to root it. Then I saw how confusing it is to distinguish between it and the previous model. My guess is whatever is out there that says Shield Tablet means the old one not the K1. I also updated mine to MM cause I'm using and 128GB micro sd card for internal storage. I guess I'll just have to wait until more support comes out for this tablet such as a stable TWRP 3.0 Recovery and the ability to gain root access and custom ROMs like CM 13.
do you recommed to install all OTAs before install custom recovery and custom roms or is it better to install twrp-2.8.7.1 out of the box and then go for the custom stuff ?
I would install all updates to get the latest bootloader. Do not install twrp 2.8.7.1. Install the official 3.0.x from the official site.
At first I created a guide about rooting stock Marshmellow of Sony Xperia Z5 Premium. After some time I realized that it may be useful to users of virtually any recent Sony phone or tablet, so here is my Sony Cross-Device general rooting thread. I will mostly copy-paste bits from my previous guide, but using renewed screenshots and firmwares'/tools' versions.
Please write back in this thread which model of Sony phone you was able to root with the help of this guide.
This guide does not work for MediaTek devices.
INTRODUCTION
Sony historically provides own versions of Android OS, modified for Sony phones. These firmwares with added Sony apps are known as a stock firmware, contrary to vanilla Android developed by Google.
This guide will lead you through the process of rooting the stock firmware for your particular Sony phone. At the same time, your phone will be supercharged with TWRP recovery image, a useful tool for things such as an installation of system behavior altering apps to a whole device backup including all system partitions.
WHY ROOT?
Sony, just as any other smartphone vendor, ships its devices without the ability to alter inner system workings of Android OS. Technically speaking, default OS only allows use of non-administrator accounts, which have access only to their own user space.
Rooting is a process of allowing access to the administrator account, also known as root. This enables a possibility to alter/remove system parts of the OS: apps, settings, behaviors. For example, with root access you can block ads system-wide, from apps to browsers.
WHAT ARE CAVEATS
During the rooting procedure, the unique DRM keys will be removed from the phone. These keys are used to make some proprietary Sony features work, such as X-Reality for Mobile, camera denoise filter etc.
During the course of this guide a so called DRM fix will be apllied, which effectively emulates DRM keys, so many Sony features remain in working condition, even without actual keys. Some features, such as Widevine, will not work but majority of typical users won't even notice this. I think most of you even don't know what Widevine is.
However, in this guide I will present a way to backup your DRM keys, if you still think you need them. I will not deep dive though, since I never bothered with DRM keys export/import procedure myself and have no experience in doing this.
Some apps will refuse to work on rooted device, Pokemon Go and Android Pay are couple of notorious examples. Research your apps for rooted device compatibility. If you find such app and cannot live without it, don't root your phone.
ACCOLADES
The rooting of Sony stock firmware will not be possible without the work of these brilliant community developers:
@Androxyde — Flashtool
@IgorEisberg — XperiFirm (integrated into Flashtool)
@Dees_Troy et al. — TWRP
@Chainfire — SuperSU
@topjohnwu — Magisk
@tobias.waldvogel — Kernel repack script and DRM fix
@zxz0O0 — iovyroot
@rayman — TA Backup v2
STEPS
The whole process of rooting your stock firmware is divided into the following steps:
Getting your phone recognized by your computer (driver installation).
(optional) Backup your DRM keys.
Unlocking a bootloader.
Flashing stock firmware with Flashtool.
Repacking and flashing a kernel.
Installing SuperSU or Magisk.
(optional) Restore your DRM keys.
Optional tasks.
After the completion of this guide, your phone contents will be completely erased, so you may want to backup all what is important to you to some external locations. External microSD card will not be erased, so you may copy your stuff to it. If you are already use some rooted Android, you may want to use some specialized tools like Titanium Backup or like. TWRP also have a nice backup features, if you have one already installed.
Also, use Sony's own Backup & reset tool from the settings. You may backup your local contacts, messages and much of such stuff directly to your microSD card. After the rooting, same tool may be used to restore some (or all) of these things back.
I usually make a whole backup with TWRP, Titanium Backup for user apps and the Sony's Backup & reset for conversations and call logs.
The guide was developed using Windows 10 Pro 64-bit and Sony Xperia Z5 Premium Dual-SIM E6883 official model for the Russian market.
Let's go.
1. GETTING YOUR PHONE RECOGNIZED BY YOUR COMPUTER (DRIVER INSTALLATION)
During the course of this guide, your phone will comminicate with your computer in Fastboot and Flashmode connection modes. When connected in these modes, for the phone to be properly recognized by a computer, you have to provide special drivers. Thanks to Flashtool creators, it comes bundled with generic drivers compatible with all recent Windows operating systems, so at first you should install Flashtool. You can get installer from the official website.
Next, you should install Fastboot and Flashmode drivers for your phone.
One caveat here however, these drivers are not from a "recognized Windows developer", that is they are not Windows-certified, so to get them installed on Windows 8/10, you should reboot with the disabled driver signature enforcement. Use Google to know how to perform this.
Once booted in the aforementioned mode (or in a regular mode if you are still on Windows 7), proceed to the actual driver installation. The drivers are packed into the Flashtool\drivers\Flashtool-drivers.exe executable, but it didn't work on my system, perhaps because it is 64-bit (but feel free to try it yourself), so I simply unarchived it with 7-Zip (right-clicked it and chose 7-Zip > Extract to "Flashtool-drivers"). I got a Flashtool-drivers folder, which contained all the drivers from the executable.
Once drivers are unpacked, connect your phone in a Fastboot mode. Recent Sony devices can boot in Fastboot just like this: shutdown the phone, press and hold Volume Up rocker button and connect USB cable to the phone while the other end is connected to a running PC. The phone's LED will turn blue shortly. That's it, you are in a Fastboot mode. Open Device Manager (Win + X, Device Manager) and check if there is some unknown device (with the name S1Fastboot or something like this).
Double-click this unknown device in the Device Manager, click Update Driver..., then Browse my computer for driver software, and choose the Flashtool-drivers folder created earlier with 7-Zip (leave Include subfolders checked). Shortly you will get a red warning dialog window, which inform you that this driver doesn't have a proper signature:
{
"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"
}
Very scary. Just proceed with the install despite all the red flags, it's safe.
Once Fastboot driver is installed, plug out the USB cable off the phone and connect it in a FlashMode mode. This is done just like for Fastboot, but in this case you should press and hold Volume Down rocker button during the cable plugging in. The LED in this case will be green and not blue. The procedure to install the driver is exactly the same.
After the successful installation, try to reconnect the phone in these modes again couple more times to make sure all devices get properly recognized by Windows. If all seems good, proceed to the next step.
2. (OPTIONAL) BACKUP YOUR DRM KEYS
I encourage you to skip this step, but if you feel like you should do this anyway, here is some info.
There is a tool called iovyroot, with which you can backup your DRM keys from an unrooted phone, but at the time of the writing it doesn't support latest firmwares. It does support a lot of older firmwares so it may be useful to not upgrade your phone before checking up this tool.
If you're into this backup DRM thing, go to the original thread, download the latest version and check if it is working for you. For now I just skip this step. Basically, you want to download the zip, connect your phone in USB Debugging mode, run the tabackup.bat script and see the output.
Some people suggest to use the newer Universal (Dirtycow-based) TA Backup v2 tool instead of ageing iovyroot to backup you keys. Please check the official thread to get instructions (linked in the previous sentence).
I will not cover DRM keys extraction/restore in details, since I never did it, so I don't want to write about something I haven't myself performed. Please check corresponding threads.
Note that most proprietary Sony features will work even without DRM keys, such as X-Reality for Mobile, camera denoise filter and some others. DRM fix will be covered later in this guide. Some features will not work with DRM fix, Widevine for example. Most users will not even notice these.
3. UNLOCKING A BOOTLOADER
Sony does provide its own guide. It is a plain and simple and — good news! — if you have followed the previous steps, you just got all the prerequisites covered!
4. FLASHING STOCK FIRMWARE WITH FLASHTOOL
Now we will flash the latest available Sony firmware to the phone. In this step it will be untouched vanilla firmware, without root yet.
The Flashtool was installed on the completion of the first step, so let's start it. If you are on 64-bit Windows, start Flashtool64 (there is a shortcut in the Start menu). It does require administrator privileges.
Once you are in Flashtool, at first you need to obtain the most recent official stock firmware from Sony. Press the "XF" icon (the right-most one in the toolbar) to start XperiFirm. This is where it is:
The window will open, choose your phone from the left part of the window, then choose your particular model and after that choose your market and operator from the right part of the window. The entry will become highlighted and shortly there will be some info in the last column (Latest Firmware). This definition will be also in the right-most part of the window just under the phone thumbnail, click on it. Not a brilliant design decision, but that's it. Here is a screenshot for your reference:
If there are multiple firmwares available, pick the more recent (typically the top-most). The new window will pop up, press Download. The stock firmware will be downloaded to your computer and unpacked.
Once the download is completed, close all XperiFirm windows to return to the main Flashtool window. Flashtool will begin a creation of the .ftf file from the downloaded resources which will be used for a (subsequent) flashing. FTF-files are similar to ZIP-files, and may be opened with 7-Zip. For example, I've got E6883_32.3.A.0.376_1299-4828_R3D.ftf after the completion of this procedure. Flashtool places firmwares in the C:\Users\<Your Windows Username>\.flashTool\firmwares.
Now, once the stock firmware is downloaded, packed into .ftf and ready to be installed, let's do this.
Disconnect and switch off the phone for now, physically extract microSD card (if any) and press the left-most button on the Flashtool's toolbar (the "Lightning" one) and choose Flashmode. The Firmware Selector window will appear with a selected default folder and list of all firmware available for a flashing. I've got a single entry, the firmware I just downloaded. Before actual flashing, you can check some checkboxes from the Wipe section, I usually check all to start clean (all the data on the phone is erased). Once again, just to be safe, extract the microSD card from the phone at this moment. It is not needed for a flashing anyway. Here is how the window looked to me:
After all is set up, press Flash. The flashing process is not yet begun, since at first Flashtool just prepares firmware for a flashing.
After a while, a window will appear which will ask you to connect your phone in the Flashmode mode. With your phone off, hold the Volume Down button, connect the USB cable. Once Flashtool detects the phone in the Flashmode mode, it will start the actual flashing automatically. You may release the Volume Down button and go get some snack. The flashing will take some time.
After the completion of the flashing procedure, you'll get a stock Sony firmware installed, and now it is perfect time to proceed to the next step. You may leave your phone off at this moment, but if you are curious, start it up and check if the new Android is actually there. Note however that first start after the firmware installation takes a long time.
5. REPACKING AND FLASHING A KERNEL
Now it is a most interesting part: repacking and flashing a stock kernel. This procedure will allow the actual rooting.
To get the stock firmware rooted, you need a way to install SuperSU or Magisk. These are tools which enable root access to the Android system. To install them, you need TWRP. To run TWRP, you need a kernel, which supports both TWRP and your Android version.
Thankfully you can extract the kernel from the .ftf file, prepared by Flashtool earlier. Then you repack it, integrate TWRP (and DRM fix) into it, and finally flash it to your phone back modified. Sound like a complex task but it's definitely achievable. I did it multiple times mostly without any issues.
At first you should extract the actual kernel from the .ftf file. Reminder: it's in the C:\Users\<Your Windows Username>\.flashTool\firmwares folder and may be titled E6883_32.3.A.0.376_1299-4828_R3D.ftf or something like this. Open it as an archive (right-click on a file, 7-Zip > Open archive) and extract kernel.sin. It's your phone's packed kernel.
If it is packed, obviously you need to unpack it. Thankfully the almighty Flashtool can do this. Open Flashtool, navigate to the Tools > Sin Editor, select a kernel.sin you've just extracted and press Extract data. As a result, you'll get a kernel.elf file in the same directory where your packed kernel is residing. As you may have guessed, kernel.elf is an unpacked kernel. It can be modified, repacked and flashed back to the phone. Let's do this.
You will need a Stock kernel repack script from @tobias.waldvogel. Here is the original thread. Author of the script mentioned, that now it is hosted on GitHub, so let's just grab the latest version from there. Here is the link to the repository. In the upper-right corner there is a Clone or download button you may push it and choose Download ZIP from the menu. The script will be downloaded.
Once the contents of the zip-file with script are extracted to some directory, copy the kernel.elf there and summon command prompt in this directory (right-click in the empty space of this folder in File Explorer with the Shift button pressed and choose Open command window here).
In the command line type the following:
Code:
rootkernel.cmd kernel.elf boot.img
You'll get some questions about adding some features/tools to your kernel, feel free to answer "Yes" (type Y) to all of them. Screenshot for your reference:
If all went smoothly, you'll get a repacked kernel, boot.img in the script folder, supercharged with TWRP and DRM fix, and most importantly, which also supports rooting. Now it is time to flash it to your phone.
ATTENTION! Since the script is mostly unsupported, when new firmware get released, its kernel modules are not getting automagically added to the script package. You will get "Skipping TWRP recovery. No kernel modules for 3.10.84-perf-XXXXXXX available" error due to this. But don't worry, you can extract the required modules yourself from the firmware.
1. Open the FTF-file (firmware you downloaded) with 7-Zip, and extract system.sin file.
2. Open Flashtool, navigate to Tools > Sin Editor, choose this system.sin file, push Extract data. You'll get system.ext4 in the same directory.
3. Use the cool free Ext2Read tool to get into the ext4 filesystem in the system.ext4 (File > Open Image). Linux users can mount this filesystem as usual. Once you get into the filesystem, go to the lib/modules directory and grab the following files from there (Tools > Save):
core_ctl.ko
ecryptfs.ko
kscl.ko
mhl_sii8620_8061_drv.ko
texfat.ko
4. Once you get these files, create the 3.10.84-perf-XXXXXXX folder in the script's Android\twrp_common_kmodules directory. In my case I created 3.10.84-perf-g5e25a09 folder, just as was mentioned in the script's output in the console (when it complained about Skipping TWRP recovery). Copy these 5 files into this newly created folder.
5. Voilà! Re-run the script and see that now TWRP gets properly integrated! Thanks to @sceryavuz for his initial instructions. I just elaborated them a bit.
When all is clear, turn off your phone if it's on and connect it in a Fastboot mode: hold the Volume Up rocker button and connect USB cable. The LED on the phone will turn blue. Release the button.
Flashing images in this mode is typically done with a fastboot.exe from the Android SDK. Android SDK weighs many gigabytes but thankfully you don't need it. Fortunately Flashtool contains fastboot.exe from the SDK. It's in the Flashtool\x10flasher_lib folder. For the brevity of the following steps, I assume you have all necessary files there. To make it true, copy the newly generated boot.img to this folder.
Now Shift-right-click in the empty space of this folder window and choose Open command window here entry from the context menu. Windows console will appear.
At first try this command:
Code:
fastboot.exe devices
If all is good, there will be one device in the output of this command, just like this:
If not, perhaps there is some driver issue, so head back to the step #1 and make sure the drivers are installed correctly.
If your device is shown correctly, let's flash some files to the phone. Execute the following command to flash the modified kernel:
Code:
fastboot.exe flash boot boot.img
The proper output of this command will be like this:
If you get any errors, the first and more likely reason is that you still have a locked bootloader. Head to the step #3 to verify its state and unlock it if necessary.
If there were no errors — congratulations! — you now just flashed a stock kernel supercharged with TWRP recovery and DRM fix. You're almost done! You may plug out the cable from your phone. If you are attentive to the details, you'll notice that now, once your phone is started, its LED turns amber for 2-3 seconds. This is a special signal for those looking to boot into a recovery (TWRP). But you don't have to start your phone yet.
Although @tobias.waldvogel claims his script is able to also integrate SuperSU during the kernel repacking, I didn't managed to get this working, so the SuperSU (or Magisk) installation is a separate step in my guide. The next step.
6. INSTALLING SUPERSU OR MAGISK
Now when you have TWRP in place and latest Android installed, let's install SuperSU to it. SuperSU distributed in a TWRP-friendly .zip archives, so you should copy one to your microSD card. I used version 2.79 from here. Download TWRP / FlashFire installable ZIP, not the APK. At the time of your reading, there probably will be some newer versions available, feel free to install them them instead. Copy the downloaded ZIP-archive to your microSD. Don't bother to unpack the ZIP.
Once SuperSU zip-file is copied to your microSD card, place it into your phone and reboot to recovery (TWRP). To do this restart or power up your phone and look at the LED. Once it lights amber, press Volume Up rocker button and you'll get into recovery — TWRP. In my case it was TWRP v3.0.2-0.
To install SuperSU, press Install, go to the /external_sd and select the .zip (in my case SuperSU-v2.79-201612051815.zip). Swipe right to confirm installation. Once it is installed, press Reboot System button. Phone will reboot twice. Do not interfere with the process during these multiple reboots, the things are getting done, so just wait once Android is started. When it's started, the phone is rooted and functional!
If you would like to install Magisk instead, the instructions are exactly the same. Grab the latest ZIP from the original thread and flash it with TWRP. That's it!
7. (OPTIONAL) RESTORE YOUR DRM KEYS
If you had successfully backed up your DRM keys in step #2, it is now time to restore it back to the device. There is a flash_dk.cmd script shipped with the Root kernel repack script you used in the previous step. flash_dk.cmd can be used to flash the DRM partition back to your phone.
At first prepare the flashable .ftf:
Code:
flash_dk.cmd <ta backup image> dk.ftf
And then flash dk.ftf via Flashtool, just like you flashed the whole firmware in the step #4, but don't wipe anything this time.
8. OPTIONAL STEPS
8.1. Xposed installation
If you use Lollipop and later, you should install Xposed APK from here. At the time of writing there is XposedInstaller_3.0_alpha4.apk installer there.
Once APK is installed, grab the latest .zip from the repository, I've got xposed-v86-sdk23-arm64.zip. Install it in a regular TWRP way covered in step #6.
Once all these steps are done, you should have Xposed Installer app in your phone, and if you open it and check Framework section, if everything is alright, there will be text in green, something like "Xposed framework version 86 is active".
8.2. Resolving Voice Search and random volume up/down issues while using regular headphones
See this thread.
8.3. Disable startup notification if there is a newer firmware available
Some people get annoyed by a persistent notification, which is displayed once the new firmware become available (new Android version from Sony). Rooted users cannot just tap it and update over-the-air, because they need to perform a complex rooting procedure in beforehand (covered in this guide). It is possible to disable this notification. You may get these notifications by email anyway.
The easiest and safest way is to use some autorun manager. I used Autorun Manager Pro and disabled all receivers of system apps com.sonymobile.fota.service, fota update service and Software update. Notification vanished after a restart.
You may even freeze or remove these apps via some app manager like Titanium Backup Pro.
8.4. Disable that damned green LED light while phone is charged and attached to the cable or docked
This is a historic Xperia behavior, not easily fixable without the root. The notorious green LED is on all night no matter which settings you set up. In fact, there is no setting to switch it off.
However, if you are rooted, you can solve this issue easily. One method is to install a free Light Flow - LED Control app. Once it is installed, you need to enable the following settings in the Settings > Device Settings and Root section: Direct mode, Root mode and Run every command as root. Then you can mess around with individual notifications in the Notification settings, but I just cleared all in there and hey! — the annoying green LED is gone!
THAT'S IT
At this point you have a stock Sony Android enhanced with root privileges. SuperSU / Magisk app is also installed, so you are ready to use root right away. SuperSU now can be updated in a regular way via Play Store. Magisk has it's own updating capabilities.
P.S. WHEN NEW FIRMWARE IS AVAILABLE
Once the new firmware is released, you may perform the same procedure for it beginning from the step #4, but if it is a minor upgrade, you may want not to wipe anything during Flashtool flashing this time. If it is a major upgrade, e.g. Marshmallow > Nougat, you probably may want to start with a clean system and wipe all.
Fragmentation said:
Getting your phone recognized by your computer (driver installation).
(optional) Backup your DRM keys.
Unlocking a bootloader.
Flashing stock firmware with Flashtool.
Repacking and flashing a kernel.
Installing SuperSU.
(optional) Restore your DRM keys.
Optional tasks.
Click to expand...
Click to collapse
I'm pretty sure that once you have unlocked the bootloader, the easiest thing at that point is to use fastboot to flash a custom kernel/recovery, then boot to recovery, flash su, then reflash your original kernel. Then you're rooted.
Plus, rooting is easy now even with locked bl, since we have Kingroot, and new Sony bootloader with real recovery.
(However, I can't say for sure on every device... I appreciate you taking the time to post...)
levone1 said:
I'm pretty sure that once you have unlocked the bootloader, the easiest thing at that point is to use fastboot to flash a custom kernel/recovery, then boot to recovery, flash su, then reflash your original kernel. Then you're rooted.
Click to expand...
Click to collapse
Hey. If you'd say this to my mom, I'm sure she'll not understand any of these. And with this guide she at least have some chance of success.
levone1, why at the end would you flash your original kernel again instead of just running your custom kernel that you made like in the guide?
F2a said:
levone1, why at the end would you flash your original kernel again instead of just running your custom kernel that you made like in the guide?
Click to expand...
Click to collapse
If you flash stock-based kernel via boot.IMG in fastboot that will work with your stock ROM, great, keep it. I was just imagining easiest thing to be to flash, for example, CM boot IMG, just to be able to get into recovery to flash su. Usually stock-based kernels are zips, with other things besides just boot IMG. What I've usually done with unlocked BL and stock ROM is use fastboot to flash CM boot and recovery IMG, then go to recovery and flash supersu, then use flashtool to flash kernel only of stock ROM. Once you reboot, rooted, you can do whatever from there.
Which ROM have you flashed to 6883. The Nougat?
levone1 said:
If you flash stock-based kernel via boot.IMG in fastboot that will work with your stock ROM, great, keep it. I was just imagining easiest thing to be to flash, for example, CM boot IMG, just to be able to get into recovery to flash su. Usually stock-based kernels are zips, with other things besides just boot IMG. What I've usually done with unlocked BL and stock ROM is use fastboot to flash CM boot and recovery IMG, then go to recovery and flash supersu, then use flashtool to flash kernel only of stock ROM. Once you reboot, rooted, you can do whatever from there.
Click to expand...
Click to collapse
I am not quite sure what you mean tbh so forgive me if I missunderstand.
stock kernels are not zips they come in .elf hence the use of rootkernel to unpack/repack it to something more manageable. nowadays supersu makes changes to this partition once flashed, so if you flash stock kernel.sin containing kernel.elf again from flashtool changes will be reverted and you loose root.
the easiest way to get into twrp recovery without flashing anything is to just fastboot it.
nigeta_gr said:
Which ROM have you flashed to 6883. The Nougat?
Click to expand...
Click to collapse
Yes, the latest official firmware available for Z5P (E6883) is Nougat (7.0). I flashed it during the assembly of this guide.
I suppose it will work with my E6833 as well.
Fragmentation said:
Yes, the latest official firmware available for Z5P (E6883) is Nougat (7.0). I flashed it during the assembly of this guide.
Click to expand...
Click to collapse
nigeta_gr said:
I suppose it will work with my E6833 as well.
Click to expand...
Click to collapse
I'm sure it will.
Fragmentation said:
At first I created a guide about rooting stock Marshmellow of Sony Xperia Z5 Premium. After some time I realized that it may be useful to users of virtually any recent Sony phone, so here is my Sony Cross-Device general rooting thread. I will mostly copy-paste bits from my previous guide, but using renewed screenshots and firmwares'/tools' versions.
Click to expand...
Click to collapse
Ogromnoye spasibo bratan!
This helped me tremendously, just wanted to say thanks!
FYI, I'm using latest Nougat 333 UK firmware on Xperia X F5121 US version --- so that my fingerprint scanner works. Got stuck in a boot loop after installing TWRP but after reading your thread, I fully understood and fixed the reason why. The root tool from GitHub worked kinda --- meaning I had busybox and others but no su binary I still had to install SuperSU.zip via TWRP to actually have root. You documented a similar experience.
JZ SmartMort said:
Ogromnoye spasibo bratan!
This helped me tremendously, just wanted to say thanks!
FYI, I'm using latest Nougat 333 UK firmware on Xperia X F5121 US version --- so that my fingerprint scanner works. Got stuck in a boot loop after installing TWRP but after reading your thread, I fully understood and fixed the reason why. The root tool from GitHub worked kinda --- meaning I had busybox and others but no su binary I still had to install SuperSU.zip via TWRP to actually have root. You documented a similar experience.
Click to expand...
Click to collapse
You're welcome, zemlyak! Sure, for root you definitely need SuperSU, it just won't work without it this way. It's a shame US versions of Xperias don't have fingerprint scanner activated, but it's cool to hear, that flashing another region firmware helps.
Hi, I followed everything until the part where I need to flash the modified kernel in step 5. There is no error messages. the output is exactly like the screen captures. When I start the phone, I don't see the amber light. I cannot proceed. Where did I go wrong? Appreciate any help available.
Edit: Used a rooted stock kernel from another thread. Seems to work. Still not sure what I missed out though.
viperc said:
Hi, I followed everything until the part where I need to flash the modified kernel in step 5. There is no error messages. the output is exactly like the screen captures. When I start the phone, I don't see the amber light. I cannot proceed. Where did I go wrong? Appreciate any help available.
Edit: Used a rooted stock kernel from another thread. Seems to work. Still not sure what I missed out though.
Click to expand...
Click to collapse
Hey. If the phone don't turn on amber light for a while during the boot up, then TWRP is not there.
If you used the kernel repack script I mentioned in the guide with a very recent Sony's firmware, probably you didn't notice, that TWRP has not been integrated into the kernel due to some error. It is because this script should be frequently updated to work with any newly released firmware, and Tobias, its author, apparently have not time to do this.
However, you can update the script yourself, following this procedure.
viperc said:
Hi, I followed everything until the part where I need to flash the modified kernel in step 5. There is no error messages. the output is exactly like the screen captures. When I start the phone, I don't see the amber light. I cannot proceed. Where did I go wrong? Appreciate any help available.
Edit: Used a rooted stock kernel from another thread. Seems to work. Still not sure what I missed out though.
Click to expand...
Click to collapse
I don't have the amber LED light on boot up on my X Compact but everything works fine. I can't seem to find it but I recall reading somewhere an actual reason why I didn't see it but as far as I know it's not a problem.
Edit: Simple check, reboot and hold volume down. Do you enter TWRP? I do even though I never see the amber led.
F2a said:
I don't have the amber LED light on boot up on my X Compact but everything works fine. I can't seem to find it but I recall reading somewhere an actual reason why I didn't see it but as far as I know it's not a problem.
Edit: Simple check, reboot and hold volume down. Do you enter TWRP? I do even though I never see the amber led.
Click to expand...
Click to collapse
Maybe it wasn't a proper kernel for your rom or device, I also experienced some errors including yours but at last (after 12 try) I found a working kernel for me. I really don't know what the problem is, sometimes it just doesn't work...
Fragmentation said:
Hey. If the phone don't turn on amber light for a while during the boot up, then TWRP is not there.
If you used the kernel repack script I mentioned in the guide with a very recent Sony's firmware, probably you didn't notice, that TWRP has not been integrated into the kernel due to some error. It is because this script should be frequently updated to work with any newly released firmware, and Tobias, its author, apparently have not time to do this.
However, you can update the script yourself, following this procedure.
Click to expand...
Click to collapse
Thanks. I will look into that again when my region's Sony release the latest firmware.
F2a said:
I don't have the amber LED light on boot up on my X Compact but everything works fine. I can't seem to find it but I recall reading somewhere an actual reason why I didn't see it but as far as I know it's not a problem.
Edit: Simple check, reboot and hold volume down. Do you enter TWRP? I do even though I never see the amber led.
Click to expand...
Click to collapse
Interesting, didn't try that lol. I used another pre-rooted sick kernel to flash after my attempt failed. I can see the amber led now with the other kernel.
Tried again after re-downloading the script. It's working now. Thanks.
if not do drm-fix, and flash dk.ftf with old flashtool, the result is" FIDO KEYS NOT PROVISONED PROVISION FAILED"
any way to fix this?
This thread is a complete guide and must be sticked, Thanks :fingers-crossed:
You should add backupTA-V2 for Lollipop devices..
Thread : https://forum.xda-developers.com/crossdevice-dev/sony/universal-dirtycow-based-ta-backup-t3514236
iovyroot method is very old..