Database Info

XT 1643 Downgrade Nougat To Marshmallow (100% Future OTA not Brick Your Device)

First Make Your Nougat System ,Boot Partition Backup By TWRP.Load TWRP By fastboot boot twrp.img..Dont Flash TWRP recovery.Just Boot it From Fast Boot..My case TWRP recover file name is : twrp.img
1) Download Moto driver and adb and fastboot from above and install it on your PC.
2) Now Download the correct last Updated firmware for your device from above and extract it to the ADB installation directory.
3) Now go to adb and fastboot installation directory and open the command window there by pressing and hold the ‘shift’ key and right-clicked anywhere in that folder.
4) Now Reboot your phone into Bootloader mode by turning it off and press and hold ‘Power + Volume Down‘.
5) Now flash system partition and boot image only by issue the below commands one by one. (If you are using mfastboot then type ‘mfastboot‘ instead of ‘fastboot‘)
fastboot flash boot boot.img
fastboot flash system system.img_sparsechunk.0
fastboot flash system system.img_sparsechunk.1
fastboot flash system system.img_sparsechunk.2
fastboot flash system system.img_sparsechunk.3
fastboot flash system system.img_sparsechunk.4
fastboot flash system system.img_sparsechunk.5
fastboot flash system system.img_sparsechunk.6
fastboot flash system system.img_sparsechunk.7
fastboot erase userdata
fastboot reboot
7) Done! Above steps will Downgrade Moto G4 Plus from Android Nougat to Marshmallow.
You Can able Receive future OTA update without any problem

prakash27091987 said:
First Make Your Nougat System ,Boot Partition Backup By TWRP.Load TWRP By fastboot boot twrp.img..Dont Flash TWRP recovery.Just Boot it From Fast Boot..My case TWRP recover file name is : twrp.img
1) Download Moto driver and adb and fastboot from above and install it on your PC.
2) Now Download the correct last Updated firmware for your device from above and extract it to the ADB installation directory.
3) Now go to adb and fastboot installation directory and open the command window there by pressing and hold the ‘shift’ key and right-clicked anywhere in that folder.
4) Now Reboot your phone into Bootloader mode by turning it off and press and hold ‘Power + Volume Down‘.
5) Now flash system partition and boot image only by issue the below commands one by one. (If you are using mfastboot then type ‘mfastboot‘ instead of ‘fastboot‘)
fastboot flash boot boot.img
fastboot flash system system.img_sparsechunk.0
fastboot flash system system.img_sparsechunk.1
fastboot flash system system.img_sparsechunk.2
fastboot flash system system.img_sparsechunk.3
fastboot flash system system.img_sparsechunk.4
fastboot flash system system.img_sparsechunk.5
fastboot flash system system.img_sparsechunk.6
fastboot flash system system.img_sparsechunk.7
fastboot erase userdata
fastboot reboot
7) Done! Above steps will Downgrade Moto G4 Plus from Android Nougat to Marshmallow.
You Can able Receive future OTA update without any problem
Click to expand...
Click to collapse
Downgrading only boot and system caused messed up fingerprint. Used all commands except bootloader provided in other thread for downgrade and now everything's good.

I see that the bootloader is not being downgraded. Doesn't that mean OTAs might still brick your device?

Bootloader was not upgraded in N. And you won't be able to downgrade your bootloader once updated.
Update : Seems I am wrong about bootloader. rpm and sbl1 have been upgraded. Those are bootloader files.
http://cloud.tapatalk.com/s/581069a8d254a/Screenshot_20161026-135945.png?
Sent from my Moto G4 Plus using Tapatalk

this is not working means fingerprint problem comes

Silesh.Nair said:
Bootloader was not upgraded in N. And you won't be able to downgrade your bootloader once updated.
Update : Seems I am wrong about bootloader. rpm and sbl1 have been upgraded. Those are bootloader files.
http://cloud.tapatalk.com/s/581069a8d254a/Screenshot_20161026-135945.png?
Sent from my Moto G4 Plus using Tapatalk
Click to expand...
Click to collapse
So are you saying that the bootloader was updated and if we do the OTA we might brick our phone?

I am not sure. Guys who got the soak test notification also have their bootloaders upgraded. They were officially handed out the soak test builds by lenovo. So they will have the same issues as those who flashed it manually, if at all there are issues.
I am not sure how this is gonna play out. If someone who is running the 139-63 build who has not upgraded to the N build can pull out the two files, we could compare them.
My point is that users who officially got the soak test builds via OTA and users who flashed them manually have the phone in the same state as of now. So if the guy who flashed it manually is gonna have issues when official N drops, then the same issue will be faced by the guys who got it via OTA.
Sent from my Moto G4 Plus using Tapatalk

Silesh.Nair said:
I am not sure. Guys who got the soak test notification also have their bootloaders upgraded. They were officially handed out the soak test builds by lenovo. So they will have the same issues as those who flashed it manually, if at all there are issues.
I am not sure how this is gonna play out. If someone who is running the 139-63 build who has not upgraded to the N build can pull out the two files, we could compare them.
My point is that users who officially got the soak test builds via OTA and users who flashed them manually have the phone in the same state as of now. So if the guy who flashed it manually is gonna have issues when official N drops, then the same issue will be faced by the guys who got it via OTA.
Sent from my Moto G4 Plus using Tapatalk
Click to expand...
Click to collapse
The point about bricks is regarding downgrade. In previous phones, downgrading from L to K, but keeping the L bootloader and then getting official L OTA would brick phone. Motorola has never supported downgrade on any phone. So if you downgrade, and later take OTA you could brick. Especially if running M with N bootloader.
The whole title of this thread is wrong - no way can anyone 100% guarantee no future brick.

Silesh.Nair said:
My point is that users who officially got the soak test builds via OTA and users who flashed them manually have the phone in the same state as of now. So if the guy who flashed it manually is gonna have issues when official N drops, then the same issue will be faced by the guys who got it via OTA.
Sent from my Moto G4 Plus using Tapatalk
Click to expand...
Click to collapse
Taking OTA to official N from soak test N is not an issue, the issue arises when someone took the N soak test, downgrade to M, OTA to official N.
tl;dr if i'm not wrong:
M -> Official N = No brick
M -> Soak test N -> Official N = No brick
Soak test N -> Downgrade to M -> OTA to official N = Brick

When you downgrade from N to M, you are only changing the system/modem/oem partitons.
Official OTA will probably upgrade bootloader/system/modem/oem/gpt/tz partitions. There is a catch here. People for whom the soak test was released are on a different bootloader than the general public which means they can't patch the bootloader or check for a specific one. They just have to upgrade it without any checks.
My question is how you will brick the device when you won't be able to downgrade the bootloader?
But as someone said, nothing in life is certain.
Sent from my Moto G4 Plus using Tapatalk

Silesh.Nair said:
When you downgrade from N to M, you are only changing the system/modem/oem partitons.
Official OTA will probably upgrade bootloader/system/modem/oem/gpt/tz partitions. There is a catch here. People for whom the soak test was released are on a different bootloader than the general public which means they can't patch the bootloader or check for a specific one. They just have to upgrade it without any checks.
My question is how you will brick the device when you won't be able to downgrade the bootloader?
But as someone said, nothing in life is certain.
Sent from my Moto G4 Plus using Tapatalk
Click to expand...
Click to collapse
You can say what you want but go read the G And X2 communities. EVERY user that updated to M then rolled back to L and later took an OTA back to M bricked. The OTA doesn't take into a count that the bootloader was a newer version - I don't remember the mechanics, but the OTA expected a different version of the bootloader.
Search XDA or the Internet for "Blank flash files" . The problem is downgrade related. If you take any upgrade, be prepared to stay on it. Do NOT downgrade.

Well, it may be true. I don't just blindly flash files on my device. I go thru the zip file to see what files are patched to make sure that I don't get into trouble. That need not be the case with all users.
Let's wait for the official OTA to be released and then we'll see how it goes.
Sent from my Moto G4 Plus using Tapatalk

ok guys ive just done some testing and ive found that whilst on official android 6.0 my bootloader version was (moto-msm8952-b0.0e) (sha-4986429) with the date 2016-04-13
then after upgrading to 7.0 soak test the bootloader version changed to (moto-msm8952-b1.00) with the date 2016-06-24
so after i then did the downgrade back to 6.0 marshamallow and the bootloader version downgraded back to its original (moto-msm8952-b0.0e) (sha-4986429) with the date 2016-04-13 so moral of the story is the bootloader does infact downgrade too and doesnt stay with the new android 7.0 bootloader like many seem to claim on this thread if u guys want to try this for yourself run this command to get your bootloader versions before update and after u updateto 7.0 & then 1 last time when u downgrade to 6.0 u will need to run the below command via adb fastboot
fastboot getvar version-bootloader

The problem with X2 and G was a mismatch between partition table version and bootloader. If you can't downgrade gpt.bin, then you may be facing a brick with OTA. Keep in mind that this is just one possible path to brickdom. The Motorola update assumes certain things, and we don't know what may change in the future. I think there is a reason that Moto says they don't support downgrades: they are not going to check for modifications and any mismatch may cause problems.
If you downgrade, then don't take an OTA, it is that simple.
http://forum.xda-developers.com/moto-x-2014/general/warning-downgrade-bootloader-partition-t3105147

chromedome00 said:
The problem with X2 and G was a mismatch between partition table version and bootloader. If you can't downgrade gpt.bin, then you may be facing a brick with OTA. Keep in mind that this is just one possible path to brickdom. The Motorola update assumes certain things, and we don't know what may change in the future. I think there is a reason that Moto says they don't support downgrades: they are not going to check for modifications and any mismatch may cause problems.
If you downgrade, then don't take an OTA, it is that simple.
http://forum.xda-developers.com/moto-x-2014/general/warning-downgrade-bootloader-partition-t3105147
Click to expand...
Click to collapse
soo we cant take ota but we can install it manually that doesnt effect i think

does downgrading work if my device is brick??
does downgrading work if my device is brick??

sucssecfully downgraded from marshmallow after brick in nougat .........tons of thank
my device was brick while trying rooting in nougat with superuser su but stuck in bootloop..........
so i directly tried to install cm 14.1 but failed..
not able to reinstall nougat ota update also......
finally downgraded to marshmallow .......... but i guess fingerprint is not working.....

drdhaval1987 said:
my device was brick while trying rooting in nougat with superuser su but stuck in bootloop..........
so i directly tried to install cm 14.1 but failed..
not able to reinstall nougat ota update also......
finally downgraded to marshmallow .......... but i guess fingerprint is not working.....
Click to expand...
Click to collapse
dOWNGRADE process please

kemesh said:
dOWNGRADE process please
Click to expand...
Click to collapse
its already mentioned in this thread....simply follow the steps........

When I am trying to install the Nougat OTA zip file from within the stock recovery, it is giving me the following errors:
Code:
Verifying current system. . .
Mount count = 9
Last mount path = /system
Last mount time = 1479061757 -> Sun Nov 13 18:29:17 2016
Device was remounted R/W 9 times
Last remount happened on Sun Nov 13 18:29:17 2016
E1004: system partition fails to recover
E: unknown command [log]
E: unknown command [log]
E: Error in /sideload/package.zip
(Status 7)
Installation aborted.
How do I go about fixing this? I have followed your guide on how to downgrade and downgraded my XT1643 to -63 baseband.
Help please!

Recevied an update with rooted phone, is it safe to update ?

I'm currently on NXT-29C185B190 and I received update with NXT-29C185B1200, my phone is unlocked and rooted, I have flash fire installed and it recognized that update was downloaded.
My question is flash fire have big red huawei device warning, saying Huawei device is very easy to hard brick (also my mate 8 is my first locked bootloader phone) so is it safe to use flash fire ? or install update throught huawei system without losing root ?

MegaMedo said:
I received update with NXT-29C185B1200
Click to expand...
Click to collapse
Is this an EMUI update through the standard update menu in settings - updater?
The version seems a bit odd to me, the last update for C185 was B320, I wouldn't expect an official update to jump as high as that. Mind uploading a screenshot?
Anyway, as for actually updating, as long as you are running stock recovery (not TWRP) then it shouldn't be an issue. Just know that you WILL lose root after updating. And I'd strongly suggest making a data backup before the update.

MuPp3t33r said:
Is this an EMUI update through the standard update menu in settings - updater?
The version seems a bit odd to me, the last update for C185 was B320, I wouldn't expect an official update to jump as high as that. Mind uploading a screenshot?
Anyway, as for actually updating, as long as you are running stock recovery (not TWRP) then it shouldn't be an issue. Just know that you WILL lose root after updating. And I'd strongly suggest making a data backup before the update.
Click to expand...
Click to collapse
Thanks for the help, I tried to user flash fire to keep my root but it failed to update, now I really think rooting huawei phone is more trouble than it worth as for what you said is version is typo
I'm currently on B190 and I got update to B200.
and yes the update is standard update from system updater
I have twrp installed so that means I can't update at all ?

Plz i want to know how to return to the normal situation after root and unlock bootloader in order to receibe update without problem

Prof1977 said:
Plz i want to know how to return to the normal situation after root and unlock bootloader in order to receibe update without problem
Click to expand...
Click to collapse
Well if you unlocked bootlader and rooted, it safe to say that you have TWRP installed, fire up SRKToolHuawei choose (2)install recovery then install stock recovery after that it reboots and then update using system updater from huawei.
PS: You will lose your root access and new to install TWRP then root again.

MegaMedo said:
Well if you unlocked bootlader and rooted, it safe to say that you have TWRP installed, fire up SRKToolHuawei choose (2)install recovery then install stock recovery after that it reboots and then update using system updater from huawei.
PS: You will lose your root access and new to install TWRP then root again.
Click to expand...
Click to collapse
Thinks a lot were can fond recovery?sorry

Prof1977 said:
Thinks a lot were can fond recovery?sorry
Click to expand...
Click to collapse
download SRKToolHuawei-Lod-Chong-V2.0-20161002 or whatever version you used to unlock bootloader and choose option 2 (Install recevory) and that it.

Thinks very much

Rooted Honor 8 Nougat and EMUI 5 OTA Update Prerequisites

I currently have a rooted Honor 8 FRD-L04 with TWRP installed, and I'm just wondering how I should prepare for the Nougat Update. I heard that I need to revert to Stock Recovery, and I'm wondering if Huawei's own erecovery can do that. Also, will using erecovery or the normal .img method wipe my phone data? I have unrooted using SuperSU or XDA (I don't remember which one). Is there anything else I should know about? Thanks!

MCWarriorz said:
I currently have a rooted Honor 8 FRD-L04 with TWRP installed, and I'm just wondering how I should prepare for the Nougat Update. I heard that I need to revert to Stock Recovery, and I'm wondering if Huawei's own erecovery can do that. Also, will using erecovery or the normal .img method wipe my phone data? I have unrooted using SuperSU or XDA (I don't remember which one). Is there anything else I should know about? Thanks!
Click to expand...
Click to collapse
u unrooted using supersu? Omg. Lol

Tmobilefan906 said:
u unrooted using supersu? Omg. Lol
Click to expand...
Click to collapse
What? SuperSU has a inbuilt unroot feature... Why not using it?

MCWarriorz said:
I currently have a rooted Honor 8 FRD-L04 with TWRP installed, and I'm just wondering how I should prepare for the Nougat Update. I heard that I need to revert to Stock Recovery, and I'm wondering if Huawei's own erecovery can do that. Also, will using erecovery or the normal .img method wipe my phone data? I have unrooted using SuperSU or XDA (I don't remember which one). Is there anything else I should know about? Thanks!
Click to expand...
Click to collapse
Tmobilefan906 said:
u unrooted using supersu? Omg. Lol
Click to expand...
Click to collapse
AnDrOiiiD_YT said:
What? SuperSU has a inbuilt unroot feature... Why not using it?
Click to expand...
Click to collapse
The only problem with unrooting with SuperSU is it will most likely Fail.
This is because SuperSU actually patches the boot.img when you flash it in TWRP and this can't be undone
to fully unroot this phone you'll need to fastboot flash boot.img and stock recovery.img
I find it easier to just use Huawei Backup and dload flash back to B162
and then restore my backup
If your already on the Nougat beta you'll need to do 2 flashes
first flash is the rollback and the second flash will return you too b162

clsA said:
The only problem with unrooting with SuperSU is it will most likely Fail.
This is because SuperSU actually patches the boot.img when you flash it in TWRP and this can't be undone
to fully unroot this phone you'll need to fastboot flash boot.img and stock recovery.img
I find it easier to just use Huawei Backup and dload flash back to B162
and then restore my backup
If your already on the Nougat beta you'll need to do 2 flashes
first flash is the rollback and the second flash will return you too b162
Click to expand...
Click to collapse
Yes I know but he said that he successfully unrooted it with SuperSU, so no problem there...

I unrooted and went back to stock recovery simply by doing a FULL OTA update. It completely blew away TWRP and rooted ROM when I did it.

L14 B360 to B385 OTA with unlocked bootloader?

I've got my FRD-L14 (64GB US honor 8) running stable with B360 firmware (released 02-13-17) bootloader unlocked, SU flashed via TWRP.
I wanted to try the latest B385 OTA firmware flash so I used fastboot to flash my current stock B360 System.img, boot.img, and recovery.img to be sure I am running all stock boot/system files before flashing the B360 OTA.
I rebooted from fastboot successfully and continued with the OTA interface to install latest system update, it rebooted into Huawei recovery interface, verifying, installing, and then fails to verify and install.
Do I really have to lock the bootloader and wipe the entire phone in order to install latest OTA and then re-unlock bootloader, reflash twrp, and restore data ?
Thanks !

Well, that wasn't hard.
I used the "download latest full package" in the top-right menu of the OTA updates screen. This successfully installed B385 OTA update package for me without failure, while bootloader unlocked. Imagine that. I hope this helps someone else! Now, to figure out how to use magisk rather than supersu....

[remove, accidental doublepost]

I have the FRD-L04 32GB US model and im wondering why I havent had the update yet
I did revert to stock boot loader and unrooted im on 360 at the moment but no updates.

crowruin said:
I have the FRD-L04 32GB US model and im wondering why I havent had the update yet
I did revert to stock boot loader and unrooted im on 360 at the moment but no updates.
Click to expand...
Click to collapse
I just got the new update

mine26135 said:
I just got the new update
Click to expand...
Click to collapse
same here hahaha updating now.

Reisntalling B385 stock rom to my FRD-L04

Hi guys,
I am currently trying to figure out how to reinstall a clean version of the B385 for my FRD-L04. I have downloaded these two files from the Nougat Update for FRD-L04 Honor 8 (USA):
Full ROM – http://update.hicloud.com:8180/TDS/data/files/p3/s15/G1585/g104/v83098/f1/full/update.zip
Data File – http://update.hicloud.com:8180/TDS/...FRD-L04_hw_usa/update_full_FRD-L04_hw_usa.zip
I have tried to flash them both from TWRP, but I always get the error: Updater process ended error 7
Can anyone please guide me through the process and let me know what I'm doing wrong?
I have look for a guide or post where this is detailed, but without luck. Can anyone link me to a guide on how to reinstall the stock firmware in my Honor 8 FRD-L04?
Thanks! :good:

The best way (if you don't want to unlock bootloader) is to flash a downgrade package first, then dload the Marshmallow update and finally your preferred Nougat update though Firmware Finder.

hackslash said:
The best way (if you don't want to unlock bootloader) is to flash a downgrade package first, then dload the Marshmallow update and finally your preferred Nougat update though Firmware Finder.
Click to expand...
Click to collapse
Thanks for the response. In my case, my phone is rooted, so I don't mind unlocking the bootloader. Would you please elaborate on how to do it that way?
Sent from my FRD-L04 using Tapatalk

juanboja said:
Thanks for the response. In my case, my phone is rooted, so I don't mind unlocking the bootloader. Would you please elaborate on how to do it that way?
Click to expand...
Click to collapse
Unlock your bootloader and follow this guide:https://forum.xda-developers.com/honor-8/how-to/guide-flashing-unapproved-firmwares-t3668306/
Choose the B385 firmware or any newer firmware available for your region.

So I decided to finally reinstall the stock firmware in my Honor 8 FRD-L04 in B389, and this is where the nightmare began.
- I made a full backup with TWRP just in case and I decided I wanted to start from the earliest firmware possible available.
- I started unrooting my phone using the UnSU zip by Osmosis.
- Then I flash via bootloader the recovery and boot image of the firmware B360.
- I flashed the rollback package from the Huawei official site with the B122 firmware also available at the same place. I saved the rollback package in my root directory in the dload folder, and loaded it with the 3-button method. After this I wasn't able to boot my phone normally, I was stuck in a boot loop. I still continue with the next firmware, the B122, and it was successfully loaded (this also relocked my bootloader).
- It is important to say I clear many times the cache and wipe/erase data through stock recovery options, and also tried to erecover but I wans't able to connect to the WiFi. I guess something was missing (at this point I was already going crazy).
- I was still stucked at a boot loop after loading the B122, so I decided to unlock my bootloader and flash the twrp 3.1.1-1-frd.img
- From there I tried to wipe data and cache and system and everything, but I wasn't able because an error saying unable to mount always appeared.
- After rebooting, since I already had unlocked the bootloader, the initial message prompting: "press power to continue, press for 3 seconds for erecovery, etc..." appeared.
- I enter the erecovery options with the hope it will do something... and it did!!! I could connect this time through WiFi and the system asked to update the firmware and many other things it said at that moment. This was the first time I felt relieved through the night.
- The phone updated perfectly, it started at the firmware B122 and I kept updating it until I reached the B389.
- I unlocked the bootloader again and rooted the phone. And everything is running smooth as silk!
I know this is a very long story, but I just want to get it out there in case anyone is facing the same problem I just passed. Hope this helps someone and brings peace to them! =) Good luck!

I believe B385 is not functional with TWRP. Flash B360 and reboot to recovery. This should go to stock recovery, where you will have to do a factory reset. I got EMUI working, but it refuses to update to any newer version (it does show B380 but doesn't update). Also there should be updates after making that update. The updates did work for other people, so you may be able to have it working.

juanboja said:
Hi guys,
I am currently trying to figure out how to reinstall a clean version of the B385 for my FRD-L04. I have downloaded these two files from the Nougat Update for FRD-L04 Honor 8 (USA):
Full ROM – http://update.hicloud.com:8180/TDS/data/files/p3/s15/G1585/g104/v83098/f1/full/update.zip
Data File – http://update.hicloud.com:8180/TDS/...FRD-L04_hw_usa/update_full_FRD-L04_hw_usa.zip
I have tried to flash them both from TWRP, but I always get the error: Updater process ended error 7
Can anyone please guide me through the process and let me know what I'm doing wrong?
I have look for a guide or post where this is detailed, but without luck. Can anyone link me to a guide on how to reinstall the stock firmware in my Honor 8 FRD-L04?
Thanks! :good:
Click to expand...
Click to collapse
Try flash B360 then OTA to 388 or 391 (If 391 singed).

blackbuffalo said:
Try flash B360 then OTA to 388 or 391 (If 391 singed).
Click to expand...
Click to collapse
Thanks for the replies, any link to where I can find the B360?
Sent from my FRD-L04 using Tapatalk

juanboja said:
Thanks for the replies, any link to where I can find the B360?
Sent from my FRD-L04 using Tapatalk
Click to expand...
Click to collapse
http://pro-teammt.ru/firmware-database/?firmware_model=FRD-L04&firmware_page=0

blackbuffalo said:
http://pro-teammt.ru/firmware-database/?firmware_model=FRD-L04&firmware_page=0
Click to expand...
Click to collapse
Thank you very much for this info!
Sent from my FRD-L04 using Tapatalk