Related
Code:
KRT16S Factory Image available in Downloads section (below)
KRT16S OTA available in Downloads section (below)
As first mentioned by mdamaged in this post KRT16S "KitKat" is rolling out now.
I did not want to hijack that thread, but wanted to have a simple continuously updated first post that summarizes experiences and consolidates resources like OTA URLs, Factory Image flashing, etc.
You will soon be seeing comments from folks about how KRT16S affects the remaining Multi-touch and Random freeze/reboot issues on google product forums:
Google Nexus 7 product forum
KRT16S touchscreen experiences (near the end of thread)
KRT16S touchscreen experiences (2nd thread)
Mixed improvement with WiFi turned on and Bluetooth keyboards
pil-gss wakelock issue appears fixed
If you need to refer to the old KRT16O thread, it is here.
Initial impressions
Problems and/or fixes
Fix for SMS in deb/LTE 4.4 KRT16S available here (thx maconsultant)
Fix for WhatsApp with ART available here (thx MasterJam882)
Fix for BetterBatteryStats - install 1.15 available here
Specific to KRT16S
Audio seems to be improved, immediately noticeable in audio feedback for taps
Touchscreen software same as KRT16O
Bootloader same as KRT16O (4.01)
Kernel same as KRT16O
Recovery same as KRT16O
Changes to nfc (tap&pay?), camera, audio, drm, google backup, TTS (text-to-speech), facelock, webview/chromium, qualcomm sensors
Magnetic smart wake when wifi lost or deep sleeps appears to be fixed
Fix is in 4.01 bootloader - not necessary to flash 4.4 KitKat ROM (thx meekrawb)
Some bluetooth keyboard improvements
GPS/pil-gss wakelock issues appears to be fixed
New touchscreen software.
Mixed results, will likely depend on screen, some fixed, some not, improvement from JSS15R
ghost touches with aligned fingers mostly gone
stuck touches seem to be gone or greatly reduced
may still have missed touches
may still have slight jitters with aligned finger dragging
Does NOT include GEL (Google Experience Launcher)
install extracted N5 GEL and new Google Search if you want the new experience (thx jxr94)
use Nova Launcher if you want transparent status bars
Root can be installed in the same ways as 4.3
If you use NRT (Nexus Root Toolkit) follow this procedure (thx ruggie0)
Logistics (only for people trying to downgrade or mix/match rom/kernels)
You cannot "dirty" flash from 4.4 rom/kernel back to 4.3 rom/kernel, you'll need to wipe data/factory reset
4.3 kernels will not boot 4.4 rom
New FLO-04.01 bootloader.
New boot animation, sounds, icons.
New Easter Egg (thx magnumlove)
settings->about tablet->android version (rapidly tap 4 times)
Tap "K" a few times to make it spin, then see the final prize
New ART (Android Run Time) replacement for Dalvik VM
Discussion here
Enable using settings->developer options->select runtime
Apps should be odexed (stock is odexed)
First boot will take a while (possibly 15+ minutes)
New cloud/network print options
The new tap and pay setting only shows up if you already have NFC enabled. (thx albundy2010)
To get tap and pay working you need to get the N5 version of Wallet (thx ruggie0)
Quick benchmark1, benchmark2 of 4.4 and stock Dalvik (thx Vanillalite)
Quick benchmark1, benchmark2 of 4.4 and ART (thx Vanillalite)
Change summary:
KRT16O(4.4_r1.1)->KRT16S(4.4_r1.2) - AOSP Changelog
Bootloader version: FLO-04.01
Android version: 4.4
Build/ROM version: KRT16S
Kernel version: 3.4.0-gb0eacf3 / Wed Oct 23 17:41:58 PDT 2013
Mini guides:
adb sideload (install OTA using stock recovery, no need to unlock, preserves user data)
flashing factory images (factory image restore, must be unlocked, option to preserve or wipe user data)
restore stock recovery (if you've installed custom recovery and want to go back to stock)
installing OTA-compatible root/SuperSU (will install SuperSU and fix so that it works with OTAs)
entering safe mode, bootloader, stock recovery (button press sequence can be tricky for fallen android)
Universal ADB drivers (use these if you have trouble with adb recognizing device)
Downloads:
KRT16S
KRT16S Factory Image - flo/WiFi (thanks azrash)
KRT16S Factory Image - deb/LTE (thanks azrash)
Source: pure stock
Format: flash in fastboot/bootloader
Guide: flashing factory images
Caveats:
no existing version requirements
requires unlocked bootloader
options to wipe or preserve user data
JSS15R->KRT16S OTA - flo/WiFi (thanks mokomull)
JSS15Q->KRT16S OTA - flo/WiFi (thanks EthanFirst)
JSS15J->KRT16S OTA - flo/WiFi (thanks EthanFirst)
JWR66N->KRT16S OTA - flo/WiFi (thanks TheManii)
KRT16O->KRT16S OTA - flo/WiFi (thanks wilsonlam97)
JLS36I->KRT16S OTA - deb/LTE (thanks scoof2)
JLS36C->KRT16S OTA - deb/LTE (thanks EthanFirst)
JSS15J->KRT16S OTA - deb/LTE (thanks TheManii)
Source: pure stock
Format: flash with stock recovery (adb sideload) or as regular update.zip in TWRP/CWM
Guide: adb sideload
Caveats:
MUST be running respective unmodified stock (JSS15R, KRT16O, JLS36I, etc.)
does NOT require unlocked bootloader
if you are rooted with SuperSU 1.51 or earlier, OTA will fail near the end. See this post for explanation/fix.
if installing via twrp/cwm suggest installing SuperSU update.zip PRIOR to rebooting to preserve root and custom recovery
preserves user data
KRT16S repackaged TWRP/CWM-flashable - flo/WiFi (thanks scrosler)
Source: slightly modified stock
Format: flash as regular update.zip in TWRP/CWM
Caveats:
no existing version requirements
this is stock functionality but not pure stock binaries so might not work with future OTAs
bootloader 4.01 flash is a SEPARATE install (needed for magnetic smart wake fix)
this is pre-rooted with init.d support
odexed and deodexed versions
preserves user data
Stock kernel/recovery (unzip and flash via fastboot/bootloader)
fastboot flash boot boot.img
fastboot flash recovery recovery.img
flo/WiFi
stock JWR66N kernel
stock JSS15J kernel
stock JSS15J recovery
stock JSS15Q kernel
stock JSS15Q recovery
stock JSS15R kernel
stock JSS15R recovery
stock KRT16O kernel
stock KRT16O recovery
stock KRT16S kernel
stock KRT16S recovery
deb/LTE
stock KRT16O kernel
stock KRT16O recovery
stock KRT16S kernel
stock KRT16S recovery
Bootloader - flo/deb (unzip and flash via fastboot/bootloader)
fastboot flash bootloader [filename]
Bootloader v3.14
Bootloader v3.15
Bootloader v4.01
Root/SuperSU
UPDATE-SuperSU-v1.75.zip - install in TWRP or CWM for root (recommended for 4.4)
UPDATE-SuperSU-v1.55.zip - install in TWRP or CWM for root
Custom Recovery (unzip and flash via fastboot/bootloader)
fastboot flash recovery twrp.img
TWRP 2.6.3.1 (recommended for 4.4)
Stock missing/modified KRT16S files
flo/WiFi
update-KRT16S-debuggerd.zip
update-KRT16S-build.prop.zip
update-KRT16S-BasicDreams.zip
Mini guide for flashing stock factory image:
You must have your bootloader unlocked to flash the factory images released so far.
You have the OPTION to wipe your data but it is best to back up anything important AND copy off the phone
Download the factory image from Google's servers:
KRT16S Factory Image - flo/WiFi - https://dl.google.com/dl/android/aosp/razor-krt16s-factory-7235eb0d.tgz
KRT16S Factory Image - deb/LTE - https://dl.google.com/dl/android/aosp/razorg-krt16s-factory-bd6c9241.tgz
Unpack using 7-zip or winrar.
You may need to unpack twice
once to get the .tar file from .tgz
another to get the actual razor-krt16s/razorg-krt16s directory from the .tar
unzip the addon to the appropriate directory
flo/WiFi - razor-krt16s-addon.zip into the razor-krt16s directory (from previous step)
deb/LTE - razorg-krt16s-addon.zip into the razorg-krt16s directory (from previous step)
boot your tablet to the bootloader using Power+VolDown
connect via usb cable to pc
If you have problems with drivers, use the adb_driver.zip from this post or naked drivers from this post
in command prompt in the razor-krt16s/razorg-krt16s directory type EITHER
flash-all
(this WILL perform factory reset and wipe your data, including virtual sdcard, starting completely fresh)
OR
flash-all-nowipe
(this WILL NOT wipe your data, nor your virtual sdcard, allowing you to preserve your setup)
You can ignore the warning about the 3 missing .sig files in the status.
Google didn't sign these factory restore images, which is incidentally why you need to be unlocked to flash.
If you have issues after upgrading, try shutting down the tablet then:
if running custom recovery, boot to recovery, perform wipe cache / dalvik-cache
if that doesn't help or on stock recovery
factory reset (backup your apps and sdcard if needed)
Whenever you preserve your data whether it be factory image or natural OTA, there will always be a small percentage of users who will encounter instability, depending on what apps they are using
So far
Initial impressions
Touchscreen software same as KRT16O
Kernel same as KRT16O
Recovery same as KRT16O
Changes to nfc (tap&pay?), camera, audio, drm, google backup, TTS (text-to-speech), facelock, webview/chromium, qualcomm sensors
Quick boot app force closes for me now. Anyone else?
AeCeEm said:
Quick boot app force closes for me now. Anyone else?
Click to expand...
Click to collapse
Works for me.
Since you probably reinstalled SuperSU, the permissions are probably messed up.
Go to app drawer, tap on SuperSU icon and exit.
Then try QuickBoot again.
If it still doesn't work, uninstall/reinstall QuickBoot.
sfhub said:
WORK IN PROGRESS - Placeholder
Mini guide for flashing stock factory image:
You must have your bootloader unlocked to flash the factory images released so far.
You have the OPTION to wipe your data but it is best to back up anything important AND copy off the phone
Download the factory image from Google's servers:
flo/WiFi
deb/LTE
Unpack using 7-zip or winrar.
You may need to unpack twice
once to get the .tar file from .tgz
another to get the actual razor-krt16s/razorg-krt16s directory from the .tar
unzip the addon to the appropriate directory
flo/WiFi - razor-krt16s-addon.zip into the razor-krt16s directory (from previous step)
deb/LTE - razorg-krt16s-addon.zip into the razorg-krt16s directory (from previous step)
boot your tablet to the bootloader using Power+VolDown
connect via usb cable to pc
If you have problems with drivers, use the adb_driver.zip from this post or naked drivers from this post
in command prompt in the razor-krt16s/razorg-krt16s directory type EITHER
flash-all
(this WILL perform factory reset and wipe your data, including virtual sdcard, starting completely fresh)
OR
flash-all-nowipe
(this WILL NOT wipe your data, nor your virtual sdcard, allowing you to preserve your setup)
You can ignore the warning about the 3 missing .sig files in the status.
Google didn't sign these factory restore images, which is incidentally why you need to be unlocked to flash.
If you have issues after upgrading, the first thing you should try is factory reset (backup your apps and sdcard if needed)
Whenever you preserve your data whether it be factory image or natural OTA, there will always be a small percentage of users who will encounter instability, depending on what apps they are using
Click to expand...
Click to collapse
Excellent guide. I would suggest one change though. Users encountering instability, before jumping straight to a factory reset, should power down their device and let it sit for a couple of minutes. Then reboot into recovery and wipe your cache and dalvik cache.
That move fixes a large proportion of instability issues after a patch or flash
xdhall said:
Excellent guide. I would suggest one change though. Users encountering instability, before jumping straight to a factory reset, should power down their device and let it sit for a couple of minutes. Then reboot into recovery and wipe your cache and dalvik cache.
That move fixes a large proportion of instability issues after a patch or flash
Click to expand...
Click to collapse
Thanks for the feedback, this is what it says now:
If you have issues after upgrading, try shutting down the tablet then:
if running custom recovery, boot to recovery, perform wipe cache / dalvik-cache
if that doesn't help or on stock recovery
factory reset (backup your apps and sdcard if needed)
Whenever you preserve your data whether it be factory image or natural OTA, there will always be a small percentage of users who will encounter instability, depending on what apps they are using
I'm having a problem updating by TWRP my KRT160 stock and rooted N7 with the KRT16s OTA. While flashing the OTA in TWRP, I am getting an error indicating that system/bin/debuggerd has unexpected content. Any advice in solving the problem?
jhom52 said:
I'm having a problem updating by TWRP my KRT160 stock and rooted N7 with the KRT16s OTA. While flashing the OTA in TWRP, I am getting an error indicating that system/bin/debuggerd has unexpected content. Any advice in solving the problem?
Click to expand...
Click to collapse
Are you flashing or sideloading the OTA zip?
Sent from my Nexus 7 using Tapatalk 4
jhom52 said:
I'm having a problem updating by TWRP my KRT160 stock and rooted N7 with the KRT16s OTA. While flashing the OTA in TWRP, I am getting an error indicating that system/bin/debuggerd has unexpected content. Any advice in solving the problem?
Click to expand...
Click to collapse
Added to first post:
Stock missing/modified KRT16S files
flo/WiFi
update-KRT16S-debuggerd.zip
You can either run the update.zip in TWRP/CWM or hand extract the file and place in /system/bin
Don't worry that it is KRT16S version, it will pass the OTA file check and allow the OTA update to complete.
sfhub said:
Added to first post:
Stock missing/modified KRT16S files
flo/WiFi
update-KRT16S-debuggerd.zip
You can either run the update.zip in TWRP/CWM or hand extract the file and place in /system/bin
Don't worry that it is KRT16S version, it will pass the OTA file check and allow the OTA update to complete.
Click to expand...
Click to collapse
Worked!! I can always count on a sfhub posting for the right info. Thanks!!!
Added to first post:
KRT16S repackaged TWRP/CWM-flashable - flo/WiFi (thanks scrosler)
Source: slightly modified stock
Format: flash as regular update.zip in TWRP/CWM
Caveats:
this is stock functionality but not pure stock binaries so won't work with future OTAs
bootloader 4.01 flash is a SEPARATE install (needed for magnetic smart wake fix)
this is pre-rooted with init.d support
odexed and deodexed versions
preserves user data
I updated to this 3.4 mb update, and now lost TWRP and root. When I went into recovery, there was a green fallen android with red exclamation point. And it freezed whole device for like 3min. How do i get recovery back so I can root?
Hello i just saw the update on my tablet (Greece).
Here is the link in case anyone wants to apply the OTA only.
http://android.clients.google.com/p....signed-razor-KRT16S-from-KRT16O.67b84ced.zip
edit: nvm, i didn't see it was posted already.
neo5468 said:
I updated to this 3.4 mb update, and now lost TWRP and root. When I went into recovery, there was a green fallen android with red exclamation point. And it freezed whole device for like 3min. How do i get recovery back so I can root?
Click to expand...
Click to collapse
The android fallen down is stock recovery. You can get the recovery menu by press/hold Power, press/release VolUp, release Power.
To get TWRP back just boot into bootloader (Power+VolDown)
Then in a command prompt type
fastboot flash recovery twrp.img
Has anyone with Deb got the 3.4 MB OTA?
Sent from my Nexus 7 using Tapatalk
Sleepy! said:
Has anyone with Deb got the 3.4 MB OTA?
Click to expand...
Click to collapse
So far, no one has posted receiving any Kit Kat OTAs (KRT16O, KRT16S) for deb.
Just the factory image is available in the first post.
sfhub said:
So far, no one has posted receiving any Kit Kat OTAs (KRT16O, KRT16S) for deb.
Just the factory image is available in the first post.
Click to expand...
Click to collapse
Deb: Forever Alone.
Sent from my Nexus 7 using Tapatalk
neo5468 said:
I updated to this 3.4 mb update, and now lost TWRP and root. When I went into recovery, there was a green fallen android with red exclamation point. And it freezed whole device for like 3min. How do i get recovery back so I can root?
Click to expand...
Click to collapse
Same here. I have TWRP 2630 and SuperSU 1.69 and thought the OTA would work when i received the OTA even prior to checking the forums. I went ahead and apply it and it went well, rebooted back into android and i quickly realised my Root is gone and TWRP custom recovery too.
So just rebooted to bootloader, flash the custom recovery and install supersu again and voila!
No significant observation with this release so far. Guess it's just a minor update
lomonic said:
Same here. I have TWRP 2630 and SuperSU 1.69 and thought the OTA would work when i received the OTA even prior to checking the forums. I went ahead and apply it and it went well, rebooted back into android and i quickly realised my Root is gone and TWRP custom recovery too.
Click to expand...
Click to collapse
Every OTA will behave this way.
If you'd like to simplify the upgrade, don't accept the automatic OTA.
Boot into custom recovery, install the OTA manually, then immediately after that (prior to reboot) install SuperSU.
Upon reboot you'll have root and your custom recovery will be preserved.
Unofficial Kitkat 4.4.4 update for the Moto G
by GPz1100
Purpose: To explore the recently released 4.4.4 update and retain the ability to revert back to Boost firmware. The full firmware update package changes other areas on the device that prevents downgrading. If/when Verizon implements the foreign ESN ban it will no longer be possible to switch the device between PagePlus accounts. At present there is no Android 4.4.4 update specifically for Boost. Flashing 4.4.2 software on device with the 4.4.4 update results in an unstable, nonworking phone. It also remains to be seen if this flash will even be possible after the Boost 4.4.4 update is released.
This archive contains just the system and kernel portions of the firmware. Based on the official 4.4.4 update from Motorola. By only altering these partitions, full downgrade options remain. In testing, all functions of the phone appear to work normally. Flash is retained, full network connectivity remains (including 3g data), camera works, wifi, etc.
Why: Forward thinking. Retaining options. Samsung devices come to mind. After the first OTA on devices such as the VZW S4 (S3 suffered the same fate after later updates) boot loader was entirely locked. No non-stock roms or even stock roms using non-stock kernels.
Precautions: Generate a backup image of your current system before proceeding. Results have been successful dirty flashing (no factory reset). Highly unlikely to brick your phone, but as with all disclaimers, proceed at your own risk.
Requirements: Moto G w/ Permanent flash, TWRP recovery
Installation:
1) Download and extract the entire contents of the archive into the following location on the internal storage
Computer\XT1028\Internal storage\TWRP\BACKUPS\{SERIAL}
The value for {SERIAL} can be obtained from settings|about|status|serial Number. Case does matter for everything. If the folder structure is not maintained, the package will not be visible in step #4.
2) Reboot into recovery
3) Tap on WIPE, ADVANCED WIPE, put a check mark next to Dalvik cache, and cache (1st and 4th entries). Swipe to begin
WARNING, do not check anything else or you will factory reset or possibly erase the internal storage.
4) Tap Home, then Restore, Select KitKat_4.4.4 as the restore package from the list, Swipe to begin
5) Once done, tap Reboot System. First boot will take a few minutes longer.
Enjoy!
Link
{reserved}
Nice work. I'm not sure if I'm ready to try it but sometimes I get bored and will try just about anything.
Which TWRP version was used for your testing? I'm currently using PHILZ (with backup issues) and will need to switch.
Thanks for your hard work.
Rampart, this was generated using twrp 2.6.3.3. I've never used philz's recovery; not sure if it'll read/write twrp images properly.
I've had this running on my test phone for a few days now. Can't say I've seen any issues or other oddities. I'm still not ready to commit to the full blown ota, so this is the next best thing.
Thanks.
IF I do it, I'll switch to TWRP.
I'm waiting on the 4.4.4 because there seems to be some issues. I learned a long time ago (when I worked for IBM), never be 1st on the block to try new software. 4.4.2 works just fine for what I need it for. Great cheap phone and on PagePlus I save a ton of money.
Hi,
I received my dual-sim Huawei Mate 9 Europe version a few weeks back. I selected this as the natural choice after running Samsung Note 3 for several years. There was no other phone that quite fit the bill as this one -
Big screen
Excellent battery
Excellent performance
I am a reasonably advanced user of my android phones - keeping them rooted, unlocked, flashing different roms are just by my alley
However after tinkering around with this new baby, I realized that this is quite different than what I was used to with Note 3.
Never before had I to read so many different forum threads to gain a full understanding of how to do things that I could do very easily with my Note 3 earlier without the need to have an indepth knowledge - just copy the steps and execute was good enough to get what I wanted. i.e.
The bureacratic boot loader unlocking process (never had to deal with this before from Samsung)
Rooting
Flashing custom recovery
Flashing custom rom
Backing up and restoring the different partitions through custom recovery
Flashing stock rom in case things don't work out as expected with the new rom
etc. etc.
I have spent several days reading practically all the forum threads on Mate 9, in order to get a good overview of how to manage this awesome device.
I am usually prone to forgetting things. So I knew after a few weeks, there will be something else that will catch my fancy and whatever I have learnt about Huawei Mate 9 after investing so many days will have gone to waste and I would have to scour the threads again if I need to do something with my Mate 9.
So I started to write down a basic guide in a text file to act as a refresher capsule whenever I decide to open the hood again after a few months
I also wanted to share my summarized learning capsule back to the community, since I have learnt so many from the various threads and the experiences from so many people.
This prompted me to actually create an XDA account (even though I have been a voracious consumer of XDA for several years, but never created an account).
Just one last tip - if you are a new user of Mate 9 trying to understand all the concepts from scratch, then try to read this guide in its entirety. Some concepts are introduced in the beginning, which might be confusing at the start, but you will understand it well after it is covered again towards the later part of the guide. Once you have a good hang of the different concepts involved, then you can jump directly to the specific section for reference.
So enough background to this thread and now out with the content.
--------------------------------------------------------------------------------------------------------------------------------------------------------
Phone Information
--------------------------------------------------------------------------------------------------------------------------------------------------------
The Model number of my phone is MHA-L29. It is a dual sim phone hence L29 at the end.
Single sim version has model number MHA-L09 i.e. L09 at the end.
The firmware version that I am running is : MHA-L29C432B156
Here is the breakup of how to read this number or the naming convention
Naming convention
L29 = Dual sim
C432 = Europe region (there are other regions as well e.g. C636 for Asian and so on)
B156 = version (this is the actual version number of the firmware)
--------------------------------------------------------------------------------------------------------------------------------------------------------
How to best use the phone
--------------------------------------------------------------------------------------------------------------------------------------------------------
For best results in order to get the full power from the hood, you will use the phone with
bootloader is unlocked
phone is rooted
either Custom recovery of TWRP or Stock recovery will be on the phone depending on the situation.
For daily usage, keep stock recovery on your phone since in case of tough situations requiring unbricking etc. stock recovery is the best to have around.
You will also remove the crapware/bloatware. It is difficult to list all the bloatwares, since they differ based on the region.
Factory resets
Reset due to minor issues
In such situations, typically your data partition is messed up but other partition (system) is fine.
If you have software issues due to software which has been additionally installed or phone has become slow etc. then boot to recovery (stock recovery) and do a factory reset. If you are running custom recovery (TWRP), then first you will need to flash the stock recovery. Then do a factory reset through the stock recovery. This action will format the data partition and copy the necessary stuff from the system partition over.
Restart the system.
Reset due to major issues
In such situations, typically your data as well as system partition is messed up. This will typically happen in case you have software issues due to un-installation of core system applications (as a root user) which have resulted in them being removed from the system partition and now you cannot restore them by an ordinary factory reset (since factory reset does not modify/reset the system partition, it only resets the data partition).
This step also requires you to have initially backed-up the system partition using TWRP. If you haven't backed-up the system partition, then you can also extract the system partition by using Huawei Update Extractor tool on the stock firmware of your region and version, which will give you the image file of the system partition that can be used further below.
Steps -
If you are running stock recovery, then first you will need to flash custom recovery (TWRP).
Using TWRP wipe the system partition.
Reboot to recovery.
Format (not wipe) the data partition.
Reboot to recovery.
Wipe the dalvik cache and cache.
Now from the already backed up TWRP partition backups
(a) restore the system partition (or the system partition image file extracted using Huawei Update Extractor)
(b) restore the data partition.
Reboot to recovery.
Wipe the dalvik cache and cache.
Restart the system.
The above should be enough for full reset. An alternative to 7.(b) above is to flash the 2 zip files containing region specific and other related system applications (you might get "error 7", but that is normal).
Upgrades
You can continue to receive over the air (full or incremental) upgrades from huawei even in a rooted and bootloader unlocked phone.
However in order to apply the received updates, you will need stock recovery, as only stock recovery has the capabilities to install the received updates. Thus before applying any update, if you are running custom recovery (TWRP), then first you will need to flash the stock recovery.
Make sure you backup all your private data and do a full installation (instead of incremental). You can select to install the full package by clicking on the 3 dots on top right corner of update screen and selecting to download the full installation package.
After this process, do a full factory reset, so your system is fully reset and updated based on the latest version.
It might happen that after the update, bootloader is locked again and you have lost your root privileges. In that case follow the steps below for unlocking the bootloader and rooting the phone again.
Also after this step, do the below.
Download the new stock firmware from hwmt.ru (as below) and the related 2 zip files zip files containing region specific and other related system applications for the new version and back them up
Make a TWRP backup of all the partitions and and back them up.
This is necessary as you might need them for other activities e.g. flashing stock recovery of the new version, doing full factory resets etc.
--------------------------------------------------------------------------------------------------------------------------------------------------------
General information on Rooting / Bootloader unlocking / Firmware
--------------------------------------------------------------------------------------------------------------------------------------------------------
The device that you get from the factory is bootloader locked with a region specific firmware.
Partitions
The phone has several different partitions (e.g. boot, data, system etc.)
The "BOOT" partition contains the boot image which boots the system and reads from other partitions
The "DATA" partition contains the user private data (e.g. contacts etc.) and is encrypted by the boot partition (Android Nougat feature). When the Android operating system starts, the boot partition decrypts the data partition and then reads it. This is the reason why other "parallel" softwares like TWRP will not be able to read from data partition, since when they read it, then it is already encrypted. Due to this TWRP will be able to backup(clone) all the other partitions except for data partition, as data partition is encrypted on the first boot of a new system. The other way to backup the data partition is to make the backup before you have booted the system (which results in encryption of the partition).
You can do this by the following steps -> "format (not wipe)" the data partition through TWRP + reboot again to TWRP + flashing the 2 zip files containing region specific and other related system applications (you might get "error 7", but that is normal). After this immediately backup the data partition.
The "RECOVERY" partition contains the stock recovery which you can replace with custom recovery TWRP
The "RECOVERY2" partition contains the "Huawei eRecovery mode" and "Huawei updater mode"
Unlocking bootloader
You can unlock the bootloader with the help of unlocking code. You get this from Huawei. Read further below on how to go about it.
Rooting phone
In order to root the phone there are 2 ways
Old method
This requires you to patch your boot partition and replace the stock boot image (which encrypts the data partition), with a custom boot image which does not encrypt the data partition.
After this you format (not wipe) the data partition, so that it is replaced by an unencrypted data partition and then you root the system in which the root exploit is directly injected in the unencrypted data partition.
New method
This does not require you change your boot image. You basically just install the custom recovery TWRP and then root using the PHH super user zip file. Read further below on how to go about it.
Recovery
If you are rooting using the new method, then you will replace the stock recovery with TWRP.
The disadvantage of TWRP recovery is that it is only the Stock Recovery that has the capability to do a proper "Factory Reset" the phone. Basically when you do a factory reset, then you "format (not wipe)" the data partition. But Huawei firmwares, also have some region specific and other related system applications (e.g. themes, camera, system updates etc.), which are also installed on the data partition. The stock recovery recognizes this and does the factory reset carefully (either by removing everything except for necessary system applications OR by doing a complete format (not wipe) of data partition but then re-applying the necessary system applications). TWRP also can do a "factory reset", but TWRP will simply format the data partition dumbly and not take care of re-installing the necessary system applications on the data partition. If you happen to do a "factory reset" or format "data" partition through TWRP, then you will need to manually flash the zip files containing region specific and other related system applications. You can get those zip files (e.g. update_data_public.zip & update_hw_eu.zip) through the same routine for downloading stock firmware detailed below. When installing these zip files through TWRP, you might get "error 7", but that is normal and you can ignore it.
Stock recovery is also useful for managing OTA updates. Typically when you download firmware updates, then they boot to stock recovery for further processing.
Hence even if you have installed TWRP, you will need to flash stock recovery for factory resets or handling new firmware updates.
Thus as mentioned before, for regular daily usage, keep stock recovery on your phone.
In order to get the stock recovery image, you can extract the stock recovery image file by downloading the "update.zip" of the target firmware and extract the "UPDATE.APP" file and then running the "Huawei Update Extractor" tool on it. Commands to flash the obtained stock recovery image file are similar to the command to flash TWRP recovery below.
Note, when you run the "Huawei Update Extractor" on UPDATE.APP file, then you will see RECOVERY.img, as well RECOVERY2.img
RECOVERY refers to the stock recovery and RECOVERY2 refers to huawei eRecovery mode & huawei updater mode.
Stock firmware
Huawei has region based firmwares e.g. in my case, the region is europe (C432)
There are stock firmwares of each region. However except for 2 regions (C636 and AL00), all other stock firmwares cannot be directly flashed. This is by design from Huawei. Even though the stock firmwares are easily available for all regions, but it is only for these 2 regions that firmwares have the PACKAGE_TYPE token set to OFFLINE_UPDATE. The PACKAGE_TYPE tokens for other region's stock firmwares are set to ONLINE_UPDATE, which makes it not possible to flash those through Huawei Updater.
Thus if you are majorly messed up or bricked, then the only way out is to rebrand your phone to a C636 (i.e. changing the OEMINFO partition from C432 (europe) to C636) and then flash that stock firmware for C636.
https://forum.xda-developers.com/mate-9/how-to/guide-rebrand-chinese-al00-mate9-to-t3554656
https://funkyhuawei.club/rebranding
In order to flash the C636 stock firmware, download the "update.zip" of the target firmware and extract the "UPDATE.APP" file into the "dload" folder created at the root of an external SD card and then starting the phone in a "Huawei Updater mode".
In order to get back to your region (C432), you will then have to use tools like "Firmware Finder" (FF), which spoof Huawei servers through DNS and network and make it possible for the updater to download and flash their stock firmwares thinking it is downloading it online from the huawei servers. You might not be able to update to the latest firmware using FF (since Huawei doesn't authenticate for latest versions sometimes), but you can try to update to an older version first and once that is sorted out, then you can update directly within system update settings to move to the latest update.
As a short-cut and if situation permits, you can also use FF, to directly flash your own region's firmware, without needing to go through the C636 route first.
However if that doesn't work, then flashing the C636 as described above is the only way out.
Also the eRecovery mode or recovery through hisuite only works if you are on a C636 region firmware.
Some useful links -
https://forum.xda-developers.com/mate-9/how-to/guide-rebrand-chinese-al00-mate9-to-t3554656
https://forum.xda-developers.com/mate-9/development/oeminfo-library-t3555353
https://funkyhuawei.club/rebranding
https://forum.xda-developers.com/mate-9/how-to/guide-rebrand-chinese-al00-mate9-to-t3554656/page5
https://forum.xda-developers.com/ma...urb175v1-0-t3575146/post71812906#post71812906
https://forum.xda-developers.com/showpost.php?p=71804525&postcount=393
https://forum.xda-developers.com/ma...lost-ideas-t3561569/post71208272#post71208272
https://forum.xda-developers.com/mate-9/how-to/guide-installing-b138-using-firmware-t3557089
--------------------------------------------------------------------------------------------------------------------------------------------------------
FRP Lock (Factory Reset Protection)
--------------------------------------------------------------------------------------------------------------------------------------------------------
Sometimes during normal usage of the phone, if the phone detects some security anomaly, it would engage the FRP lock .
It has also been found that the phone enters FRP lock mode also when you do a "Reset to default" in the developer mode. So try to avoid doing that.
Basically what happens when you reset the developer mode is that the "OEM Unlock" setting goes back to disabled, and typically when OEM Unlock is disabled, then FRP lock is enabled. However if the bootloader is unlocked, then you will find that it is not possible to change the "OEM Unlock" setting in developer mode, because if bootloader is unlocked then this setting is greyed out and not possible to change.
In short ->
Bootloader is Locked -> "OEM Unlock" setting is greyed out
"OEM Unlock" is enabled -> FRP Lock is Unlocked
"OEM Unlock" is disabled -> FRP Lock is Locked
FRP lock is to prevent mis-use of the phone in case of theft. Since it requires you to enter your google sign-on information again after doing a factory reset before you can use the phone..
FRP lock disables entering any fastboot command, which is a big issue since it means you cannot do anything in bootloader mode i.e. no flashing another recovery, no lock/unlock OEM etc.
In order to check if your phone is FRP locked or not, enter the bootloader mode. Over there it will be mentioned "FRP Lock" or "FRP Unlock", the former indicating that the phone is FRP locked.
In such scenarios, the only way out of the FRP lock mode is to flash the stock firmware again (which means your phone will be restored to totally factory condition i.e. bootloader will be locked, phone will be unrooted).
At the point when the phone enters FRP Lock, if you happen to have stock recovery, then you have a better situation as compared to if you have custom recovery (TWRP).
This is because if you have stock recovery, then you can simply use FF to flash your region's stock firmware. However if you have TWRP, then you have to flash the C636 version (asian) using Huawei Updater mode and then move on to your region's stock firmware.
--------------------------------------------------------------------------------------------------------------------------------------------------------
Using Firmware Finder (FF)
--------------------------------------------------------------------------------------------------------------------------------------------------------
Firmware Finder basically spoofs the Huawei servers by using a local proxy server leading the phone to thinking that there is a firmware update available, and thus allowing you to flash the firmware you wish (with some restrictions of course).
Using Firmware Finder requires you to have stock recovery.
If you are trying to install European regional firmware from scratch, then start by installing version B138 through FF and then move to higher versions using normal system update (or if you are not getting prompted for a normal system update automatically, then of course update through FF.)
For getting the full version of B156 (2.2 GB) through FF, at the time of writing this it was not yet authenticated by Huawei, so if you try to download it you will get authentication error after the download is completed and being verified. Thus, you will instead need to download a partial update of 409 MB through FF (if you are moving from B138 to B156). If you are moving from B126 to B156 then you will need to download the partial update of 473 MB through FF. This will allow you to have B156 on your phone.
The limitation of FF is that it only allows you to install firmwares which are authenticated(approved) by Huawei. Thus in order to install the latest and greatest, you might not be able to use FF. In such cases you can use paid services such as FunkyHuawei which allows you to install even non authenticated(approved) latest and greatest Huawei firmwares.
Though personally, I feel that it is for a good reason that Huawei does not authenticate the latest and greatest since they are beta versions and it is not that big an issue to not have them on the phone.
FF has 2 APKs for the phone - one is the actual application and the second one is a proxy server. The usage is simple - you find the firmware to install using the main application and then send the selected firmware over to download through the proxy server application on the phone. You will also need to change your Wifi settings to add a local proxy server (localhost:8080) before trying to check through system update on availability of new firmware.
FF firmware download on the phone has 3 phases.
Phase 1
The first phase requires you to modify the wifi network config to have localhost and 8080 as proxy to go through the FF Proxy application, which will spoof the Huawei servers and allow the handshake to happen to download the right firmware.
Phase 2
Once the download has started, then move on to the second phase, in which you pause the download, and then once again modify the wifi network config to remove the proxy configuration and then resume the download. This will allow you to download the update at full speed without any proxy intervention
Phase 3
The third phase starts at the last phase of the download in which you pause the download at last remaining 1%. After that you turn off wifi and start mobile data and resume the download from there. This is good because after the download is complete, the firmware will be verified and a last authentication handshake will be done to huawei server, and this doesn't need to be spoofed or be through wifi. Instead it is better that it should be originating through your mobile network.
i.e. a spoofed connection is only required in the first phase of the download
After updating from FF, you will need to do a factory reset of the phone. Then proceed with normal installation, bootloader unlocking, custom recovery installation, rooting. If necessary also flash the 2 zip files containing region specific and other related system applications. After this revert back to stock recovery and do a factory reset again. After this the phone is fully clean and ready to use.
--------------------------------------------------------------------------------------------------------------------------------------------------------
How to download stock firmware
--------------------------------------------------------------------------------------------------------------------------------------------------------
Go to this site (replace the MHA-L29C432 part of the string at the end with the model number of your own Mate 9 device)
http://hwmt.ru/oth/HWFF/info/view.php?find_model=MHA-L29C432
In the "Тип" column, you should only filter by FULL (no OTA, as that update is only eligible for usage by a paid service called funkyhuawei)
Check that the link in the "Список изменений" column is almost the same as "Файл обновления" column. Only difference should be the last part which should be changelog.xml in former and update.zip in the latter.
Now using the link, change the last part of the link to filelist.xml
This will give the xml path with the details of the files as part of that version.
Example
Code:
<vendorInfo logfile="changelog.xml" name="common" package="update.zip" subpath=""/>
<vendorInfo logfile="" name="public" package="update_data_public.zip" subpath="public"/>
<vendorInfo logfile="" name="hw/eu" package="update_hw_eu.zip" subpath="hw/eu"/>
Now change the url to download the above 3 zip files using the subpath i.e
Code:
$URL/update.zip
$URL/public/update_data_public.zip
$URL/hw/eu/update_hw_eu.zip
--------------------------------------------------------------------------------------------------------------------------------------------------------
Information on entering the various modes on the phone
--------------------------------------------------------------------------------------------------------------------------------------------------------
Engineer mode
In a powered ON phone
enter the following on the dialler
*#*#2846579#*#*
Huawei Updater mode
In a powered OFF phone
hold volume up + volume down + power for a long time (around 10 seconds)
Recovery mode
In a powered OFF phone
hold volume up + power
In a powered ON phone
enter the following through the command line on computer
adb reboot recovery
Huawei eRecovery mode
In a powered OFF phone
power on the phone through the power button
at the prompt that "Your device has been unlocked and cannot be trusted", it will tell you to press the power up button for 3 seconds to enter the eRecovery mode
Download mode / Fastboot mode / Bootloader mode
In a powered OFF phone
keep the volume button pressed down
connect the USB cable to the computer and the phone
In a powered ON phone
enter the following through the command line on computer
adb reboot bootloader
--------------------------------------------------------------------------------------------------------------------------------------------------------
Information on using adb or fastboot commands on your phone
--------------------------------------------------------------------------------------------------------------------------------------------------------
Make sure that "Minimal ADB and Fastboot" program is installed on your computer
Make sure USB debugging is enabled in phone settings
Make sure all reasonable permissions have been allowed as per the developer options
Make sure that hisuite is installed (which will ensure that USB drivers are installed)
--------------------------------------------------------------------------------------------------------------------------------------------------------
Information on unlocking the bootloader
--------------------------------------------------------------------------------------------------------------------------------------------------------
Steps to obtain unlock code
Entry page for unlocking bootloader is
http://emui.huawei.com/en/
Then click on Download. And then click on "Unlock bootloader"
OR
Visit this page
https://emui.huawei.com/en/plugin/unlock/detail
Enter the required details on the form
Steps to unlock the bootloader
Make sure that USB Debugging is enabled on the phone and the phone has been verified to connect to the computer and phone has permanently accepted the RSA id and connected in debug mode.
Also make sure that "Enable OEM Unlock" has been enabled in the developer options.
Put the phone in "Download mode / Fastboot mode / Bootloader mode"
Enter the following commands
fastboot oem unlock $CODE
fastboot reboot
In the above command, replace $CODE with the actual code received from Huawei
--------------------------------------------------------------------------------------------------------------------------------------------------------
Information on installing custom recovery (TWRP)
--------------------------------------------------------------------------------------------------------------------------------------------------------
Copy the "twrp-3.0.2-2-hi3660.img" file to the "Minimal ADB and Fastboot" directory
Put the phone in "Download mode / Fastboot mode / Bootloader mode"
Enter the following commands
fastboot flash recovery twrp-3.0.2-2-hi3660.img
fastboot reboot
--------------------------------------------------------------------------------------------------------------------------------------------------------
Information on rooting the phone
--------------------------------------------------------------------------------------------------------------------------------------------------------
Make sure that the version of TWRP installed is twrp-3.0.2-2-hi3660
Copy superuser-r275.zip into an external SD card
Boot into TWRP recovery mode and install the above zip file
Restart the phone in normal mode and install the "Superuser_2.0_Beta_9.apk" application
--------------------------------------------------------------------------------------------------------------------------------------------------------
Attachments referred in the guide
--------------------------------------------------------------------------------------------------------------------------------------------------------
https://drive.google.com/drive/folders/0B4pklpmVwGHqOWs3SlpWOEdUcUk
Top work ???
Good job...:good::good::good::good::good::good::good:
Nice. Thanks.
Good summary.
Add the supersu SuperSU-v2.79-MATE9-init.d_support.zip.
This is the method to get busybox and viper4android installed, for they use fix paths of supersu.
My device: Mate 9 supersu b156 Mediapad X2 GEM 701->703 B212 KangVIP (AJ mod)
Hi saurabhg9, I just starting reading you incredible Mate 9 summary guide and had to stop only to say that I simple love the way you explain everything, so simple, so clear, so useful... Thanks a lot for you to share your refreshing capsules, they are just the medicine my Mate 9 and I needed! :good::good::good:
Going back to continue the treatment!
Edit to ask for a little help... Recently I installed the L09C432B181 using Funky services and used it rooted by THIS method and all was going fine. Then I decided to give a try to RomAur but went back to stock restoring system and data. All well apart from root, so I rerooted flashing the 3 zips again but no way to get proper root back. It works but doesn't ask permission any more, the log is empty and it ask for binaries update in each boot. My main reason for root is to control the phone with gestures but only one of the commands of GMD app works.
I tried your 2.-Reset due to major issues using the twrp backup system and data without any result. Tried also the root superuser-r275.zip from the last section with no success either.
Tried as a last option spend another Funky credit in the B182 but always get the same "getting package info failed" error, what should be happening?
Any idea? Maybe extract a clean system and flashing it by adb (edit: tried but get "target reported max download size 471859200 bytes" error)?
Thanks again!
Thanks Peppus!
Sounds like you might need a clean start for your phone and do a "full reset".
In order to do that, I suggest doing a clean stock install of C432B138 using FF and then update to B156.
After that you could unlock the bootloader and root. This will atleast give you a clean base to start with for further experimenting depending on where you would like to go from there.
Epic work, but there are too many things which are absent and can cause mess up knowledge.
No info about MHA-AL00
No info how hard to unlock bootloader on MHA-AL00
No info what is difference between simple root and root with additional functional like dm-verity...
And more, and more....
P.s. I don't want to blame, cause I know that it is too hard to gather information from thousands threads.
5[Strogino] said:
Epic work, but there are too many things which are absent and can cause mess up knowledge.
No info about MHA-AL00
No info how hard to unlock bootloader on MHA-AL00
No info what is difference between simple root and root with additional functional like dm-verity...
And more, and more....
P.s. I don't want to blame, cause I know that it is too hard to gather information from thousands threads.
Click to expand...
Click to collapse
Thanks for the feedback!
I really wish there was a "wiki" functionality at XDA, so guides such as these could be developed with the joint knowledge of its members.
Unfortunately, that is also reflecting above, where most of the content is based on my own personal experience and what I have learnt in past few days based from various threads. and what works for me.
If you could provide me the specific text to be updated above (in regards to the things that you mentioned above), I would gladly add it
I am sure lot of others, including me would benefit from such.
Cheers!
Saurabh
saurabhg9 said:
Thanks Peppus!
Sounds like you might need a clean start for your phone and do a "full reset".
In order to do that, I suggest doing a clean stock install of C432B138 using FF and then update to B156.
After that you could unlock the bootloader and root. This will atleast give you a clean base to start with for further experimenting depending on where you would like to go from there.
Click to expand...
Click to collapse
Hi, that is what Audioralf recommended me and I was trying to avoid but I think it is the only option I have now. Thanks for your interest :good:
Peppus said:
Hi, that is what Audioralf recommended me and I was trying to avoid but I think it is the only option I have now. Thanks for your interest :good:
Click to expand...
Click to collapse
Yes - clean scratch install is good!
I do mine at far lesser problems than yours
saurabhg9 said:
Yes - clean scratch install is good!
I do mine at far lesser problems than yours
Click to expand...
Click to collapse
By the way, does anybody know which is the latest build installed in a L09C432? by Firmware Finder? Thanks!
My good guess would be for b138, since the version numbers for L29 and L09 are quite similar at least for the c432 region.
Try doing a FF install for L09C432B138. Then partial update using FF to 156, if you are not prompted by system update automatically
Hi,
Just updated the guide with some new information relating to -
* FRP Lock
* Using Firmware Finder
Also updated various miscellaneous parts of the guide with additional information and clarification.
hi
this guide is just awesome
top work
for the mate 9 beginners now all is crystal clear
thx for the guide and explenation
greetz benji
Benji1983 said:
hi
this guide is just awesome
top work
for the mate 9 beginners now all is crystal clear
thx for the guide and explenation
greetz benji
Click to expand...
Click to collapse
Thanks!
Glad you found it useful.
Hi,
Thx for your awesome collection of how-to's and how everything works!!!!
Tried to start with all the stuff like you did, but some things were/are too strange for me, so i decided to wait until i found an "encyclopedia" like this :good:
Saved a lot of time i guess
So again thx for your great work. Appreciate that
saurabhg9 said:
...In order to get back to your region (C432), you will then have to use tools like "Firmware Finder" (FF), which spoof Huawei servers through DNS and network and make it possible for the updater to download and flash their stock firmwares thinking it is downloading it online from the huawei servers. You might not be able to update to the latest firmware using FF (since Huawei doesn't authenticate for latest versions sometimes), but you can try to update to an older version first and once that is sorted out, then you can update directly within system update settings to move to the latest update...
Click to expand...
Click to collapse
Hi saurabhg9, do you mean that you can rebrand to another region using Firmware Finder? I thought that you only can install the same region roms by it.
Thanks for the update!
Cheers!
Yes.
There are 2 steps to rebranding.
First step is to ensure that your oeminfo files match that of the targeted region. This can be easily done through twrp.
Second step is to flash that regions firmware using FF.
As mentioned in my guide, you might not be able to flash the bleeding edge versions (you need paid services i..e. funky for that). But if you keep things simple and reasonable then you can get the huawei approved ones of most of the regions (e.g. B156 through FF has been verified personally by me for Europe. I haven't tried higher versions since even this version is fairly new and good)
Also I have read that to flash C636, you do not even need to flash the oeminfo of that region (asia).
Haven't verified this personally but have read some guys do it successfully while they were trying to revive their messed up Europe (C432) phones and they had just placed the C636 UPDATE.APP in dload folder and installed it using the Huawei Updater Mode (3 button method)
OK Please note (4-25-17) this message is a work in progress, as I slowly restore my system.
This is a listing and hopefully helpful listing of what I did (right and wrong)
in upgrading my Systemless-rooted (suuser) phone from 6.01 to 7.00 (nougat)
# 1. it did not work, and I went back to 6.01 successfully using the twrp recovery
I have previously used Bender's guid (here) to get the system-less root on 6.01.
essentailly, here's the best plan. Use the Minimal ADB and Fastboot package (MADB &F) (here)
(Explanation: the MADB&FB package will allow you do do LOTS of stuff related to updating your phone, with very little grief.)
it also includes the ability to automatically "push" a package over your usb connection if the ZIP file doesnt load right. **THIS will come in handy later!
Once MADB&F is installed, make note of your directory, and then make sure you start your dos window (for pc users) as an administrator!
BTW, if I HADN'T made the "TWRP backup" of my system, I'd be Sh*t out of luck right now...", because I screwed up the 7.0 upgrade.
the technical problem was that I had no data, no modem, no way of getting data/voice in/out.
SIMPLY using the TWRP restore fixed me!!!
(so far, we have MADB&FB, downloaded and bender's (chainfire) rootless guide.
Next you want to download the current firmware image for your phone. This will be a lifesaver, I promise!
3) Download a TWRP image (this will MAGICALLY load on your pc when you tell it you need help! Look HERE
(Athene is the Motorola Codename for the motoG4+)
3) copy the athene TWRP image into your madb&FB directory to make it easy to load
4) next, (you still haven't touched your phone yet, you realize: (skipping some basics here, you can search here on XDA to find more info)
a) plug your phone into your pc
b) make sure you are a developer
c) make sure your phone shows you are connected to your pc for file transfers, NOT for charging
5) in your MADB&FB directory, (aka a dos/(admin) window) type the following:
all commands at this point will take place in whatever directory you installed Minimal ADB & Fast boot (MADB&FB)
Connect your phone to your PC and open MADB&FB, check the connection with:
adb devices
return should include your "serial-no" and "device".
6) next, on pc, tell the system to reboot your phone to the bootloader!
Reboot into bootloader with:
adb reboot-bootloader
and check again with:
fastboot devices
7) Next you are going to download TWRP to your phone (not permanently, just for a bit!)
fastboot. flash recovery twrp-3.0.2-0-athene.img
Now you have TWRP (Team Windows RECOVERY PROJECT) loaded.
SO.. THIS is where you create a backup of your current stuff using the backup options.
NEXT:
take the suUser2.78 (stateless rooting), and once your backup is done, install it from TWRP
Then (I was) back to 6.01 rooted.
NEXT: 7.0 and then rooting... (will update tomorrow)
did a successful upgrade to 7.0,
then unsuccessfully tried to sideload supersu2.78, which bricked loader
then downgraded again to 6.01 (and rooted again, ok)
will continue tomorrow.
need working phone for now..
cheers to all, and to all, a happy spelunking!
You can't root factory Nougat as is, it is well encrypted.
You need to replace first the kernel with the ElementalX one, or you will end up with bootloops.
Only after that you can do SuperSU, but only with the latest beta.
A few pointers from your story:
1)As you've found out the hard way, you won't be able to update to Nougat if you have root and/or TWRP, because the update requires a stock system - stock recovery, system and no modifications (bootloader status doesn't matter). In other words, you'll need to unroot and restore your stock recovery - might be easier to reflash the stock system, probably the quickest way to flash a stock ROM (and update to Nougat) is to use the fastboot ROM. https://forum.xda-developers.com/moto-g4-plus/how-to/moto-g4-plus-xt1640-43-athene-npj25-93-t3549369 Of course, this will remove root and TWRP, as well as potentially wipe your data, so back up accordingly. This should flash the NPJ25.93-14 build on your device, which appears to be the latest global build.
1a)Also, if you flash Nougat this way, your bootloader and GPT partitions will be updated, so if you wish to downgrade to Marshmallow at any point, when flashing do not flash these partitions from the Marshmallow ROM. Fastboot should stop you, but a brick may occur if these get flashed.
1b) You may find in the Guides section TWRP backups of Nougat builds, I don't recommend using these to update your system with. Granted, they have most of the Nougat system in a TWRP backup, but some crucial firmware (e.g. the baseband) is not included, and may cause you issues if your device is not formally flashed to Nougat.
2) As SoNic67 has already mentioned, the stock kernel security will cause your device to bootloop should you choose to try to root following the Marshmallow method. If you wish to use SuperSU, follow this guide: https://forum.xda-developers.com/mo...de-root-moto-g4-plus-supersu-android-t3587918 You may wish to use a more up to date TWRP than the official 3.0.2 (I recommend shrep's TWRP 3.0.3 n4 here:https://forum.xda-developers.com/mo...covery-twrp-3-0-2-r3-moto-g4-g4-plus-t3494337) Whatever you do, ensure you flash first the ElementalX kernel before you flash the SuperSU v2.79 SR3 beta (https://forum.xda-developers.com/apps/supersu/2014-09-02-supersu-v2-05-t2868133), or apply the systemless fix with earlier SuperSU versions as directed in the aforementioned rooting with SuperSU guide. Else you'll be having bootloops or your device will not boot whatsoever. Here's my steps in successfully rooting Nougat: https://forum.xda-developers.com/showpost.php?p=71817346&postcount=225. Good luck either way.
echo92 said:
A few pointers from your story:
[...]
1b) You may find in the Guides section TWRP backups of Nougat builds, I don't recommend using these to update your system with. Granted, they have most of the Nougat system in a TWRP backup, but some crucial firmware (e.g. the baseband) is not included, and may cause you issues if your device is not formally flashed to Nougat.
[...]
Click to expand...
Click to collapse
After updating my US retail xt1644 to nougat, by restoring totally-stock marshmallow then taking the OTA, I wiped data and made a *complete* TWRP backup using @Shreps' unofficial 3.1 TWRP build (https://moto.shreps.fr/Moto G4 (athene)/recovery/twrp-3.1.0-athene_shreps.img).
This version of TWRP allows backup/restore of the full set of firmware partitions including baseband, DSP, etc.
In other words, I believe the TWRP backup folder in the following .zip file provides a one-stop path to the latest xt1644 USRET firmware by doing a restore from TWRP 3.1.0.
https://drive.google.com/file/d/0B4XobQzgZVHyRTlmSDMtYkdZeUU/view?usp=drivesdk
My only uncertainly is if the ota process modified the partition table in a way that might make this backup image incompatible with the xt1644 still in the marshmallow state.
I've often wondered if I (or a more skilled enthusiast) couldn't build a TWRP-flashable .zip that would setup the partition table, update the baseband, etc. This is what I've grown used to from devs on other phones I've had, but perhaps there's something about the way moto does things that makes this problematic.
Sent from my Moto G4 Plus using Tapatalk
bmeek said:
After updating my US retail xt1644 to nougat, by restoring totally-stock marshmallow then taking the OTA, I wiped data and made a *complete* TWRP backup using @Shrep's unofficial 3.1 TWRP build (https://moto.shreps.fr/Moto G4 (athene)/recovery/twrp-3.1.0-athene_shreps.img).
This version of TWRP allows backup/restore of the full set of firmware partitions including baseband, DSP, etc.
In other words, I believe the TWRP backup folder in the following .zip file provides a one-stop path to the latest xt1644 USRET firmware by doing a restore from TWRP 3.1.0.
https://drive.google.com/file/d/0B4XobQzgZVHyRTlmSDMtYkdZeUU/view?usp=drivesdk
My only uncertainly is if the ota process modified the partition table in a way that might make this backup image incompatible with the xt1644 still in the marshmallow state.
I've often wondered if I (or a more skilled enthusiast) couldn't build a TWRP-flashable .zip that would setup the partition table, update the baseband, etc. This is what I've grown used to from devs on other phones I've had, but perhaps there's something about the way moto does things that makes this problematic.
Sent from my Moto G4 Plus using Tapatalk
Click to expand...
Click to collapse
Nice one, hopefully that'll help more XT 1644 users I'm still not sure if TWRP can backup/flash the baseband by itself, but I don't have a XT 1644 to test. I imagine your backup will need a clean flash (wipe data/cache/Dalvik) to work?
The OTA process does update the partition table, but as far as I know, that should not prevent you from flashing back to Marshmallow/Nougat as you wish, so long as you did not try to downgrade the GPT/bootloader.
There was an effort to create TWRP flashables of the stock ROMs a little while ago (you can see the thread here: https://forum.xda-developers.com/moto-g4/development/fxz-athene-twrp-flashable-fastboots-t3562147) which if I understood it created flashable radios and ROMs from the firmware files we have. We can't touch the GPT/bootloader since, as I recall, you need a signed stock firmware to do so (and besides, downgrading GPT might be asking for a brick). I recall some users mention they were able to run Nougat TWRP flashes on the MM bootloader/GPT without issue.
There were issues with simply flashing the Nougat 93-14 radio baseband files for some US users, losing LTE in the process and appears the only resolution was to flash the stock ROM - I don't know what the cause was (perhaps no/incorrect CDMA support in the radio files?). Your TWRP flash is from a US based phone so may have better luck in that department, and will likely behave on your device since that OTA has updated all the firmware on your device that TWRP isn't able to touch. I still am not sure if we can use this TWRP backup to update on a MM device without issue, but only one way to find out...
I was updating my system security patch from official moto but after restarting it started twrp and asked me if i want to flash that update file, after swiping it opened Twrp homepage(i was unable to restart from its reboot option but i went to the bootloader and started cell (Working correctly currently))
Two Options
1. I should lock the bootloader
2. Leave it as it is.
If option 1. lock my bootloader on stock Android Nougat 7.0 on Moto G4 plus Athene XT1643. As i have stock android and precious data so i only want to lock bootloader Without wiping my system Data (I can wipe if no other way is available).
For option 2. Keep it as it is.
Please suggest me what to do and how?
And tell me about official Oreo or Custom Oreo(best option)
Sorry for my bad English and errors(If any).
Thanks in advance
@cooldude1598 official update can not be flashed through TWRP, you need to have stock recovery and unmodified system/kernel/etc as well.
If you have played with stock ROM (flashed custom kernel/ rooting / installing and flashing other stuff ), it will fail through stock recovery too, for that you need to download appropriate stock ROM according to your current version of stock ROM, and it will erase everything (includes apps and app data, photos, videos and anything on internal storage)
you said, you have system data ?
What is that?
If it is photos, videos, or personal data then move it to external sd card or PC, apps and app-data can be backup through titanium backup, and also move it to safe place.
If not this, then tell us what system data?
Fro another question about LOCKING, it is not necessary to re-lock bootloader, you can go with unlocked bootloader, don't lock again, once you flash stock ROM through fastboot, you can update to any security updates without fail.
English is weak here too, hope you got it what i said.