Related
Hi A7 users,
Let's start this off be saying, bare with me English is not my primary language.....
OK now, the reason for this Thread is to find a definite solution for current users and future users who have run into boot issues cuz they were trying to :
A- Go back to Un-rooted and lock bootloader state.
B- Started Playing with root tools and make a huge mistake
C- Started playing with twrp not knowing what they were doing
D- All the above + started flashing images files and got worts.
E- Any other type of situation.
I Know we make mistakes and we learn from them and well here today we are going to try or rather say Find a permanent /define solution to all this issues with your help, so PLEASE ONLY POST IF YOU HAVE RUN INTO ANY OF THIS ISSUES AND HOW YOU GOT INTO THE ENCHILADA ( MESS ) .
If you have the solution to your previous boot problems send me a PM and I'll keep this Thread updated for everyone to see with your solution and of course credit to the user/s.
NOTE : Please mention which Axon 7 you are using e.g. :
- A2017 (Chinese Variant)
- A2017U (USA Variant)
-A2017G (UK/Europe/International Variant)
reserve 1
reserve 2
reserve 3
reserve solution 4
reserve solution 5
Anyone this issues please post you issue, how to got into the problem, device model and if you got it fix let us know.
https://www.youtube.com/shared?ci=05LD4Ja-h3k
You'd think with all the other posts about problems there'd be something here by now.
Always thank those who are helpful...and just ignore those who aren't.
Mine happened when I wiped Internal storage from twrp. This caused the phone to only see 4gb of internal storage. Came to xda and it was suggested to flash back original boot.img. once that was done 4gb issue was fixed and the radio was gone.
I did indeed try every solution offered (thanks again for all the effort, DrakenFX and others). But, I've come to the conclusion that this is not going to get fixed until XTE releases US images. For other people's sake I hope I am wrong, but I myself decided to proceed with the exchange where I bought it, as I was right at the end of my 14 days (newegg doesn't seem to give the 30 days that xte does). I may be out of an Axon 7 for a while, so for now I am on my amazon ads, Blu R1 HD (with ads defeated
Is there a guide to go back to stock for the A2017G?
i'm on B02 with root and the bootloader still locked.
Like to go back to stock now that ZTE is working on an update to give the A2017G an unlocked bootloader.
Hi all,
I am currently experiencing a bootloop on my Chinese Axon 7. Some of you regulars may have seen me asking in other threads because I've tried to fix it myself, but I've kind of run out of options. Sincerely hoping one of you can help me out!!! I'll buy the winner a beer or 2, haha!
Back story:
Was on B07 with root (tenfar's tool) with locked bootloader and had some issues with the ROM. Like vibrating when I opened the camera and battery drops. So I decided to upgrade to B09. Placed the OTA on SD card and went to: Settings -> update. Worked fine. So I connected it to my PC and made a dump (tenfar's dump tool) of my recovery and boot and stored them. Then I ran the Tenfar's tool, the B09 version and it went like the last one. But when I booted I didn't have wifi, and other issues came up. So I thought: did I make a mistake? So I read it again, checked the COM port again... all checked out. And used Tenfar's tool again. After that it didn't even boot anymore! It plays the nice boot animation and then gets stuck on the end screen with all the pictures.
So after that I restored my dumped recovery.img and boot.img. This is when I knew something was wrong: it still didn't boot! I reset data/cache in the stock recovery: no boot. Still stuck at the end of the boot animation.
What I've tried:
- Flashing the stock B09 update.zip with TWRP.
- Flashing the stock B09 update.zip without updater-script 'assert' and 'get-prop' line. TWRP says 'update.zip is corrupt'. Doesn't install.
- The I put it on SD card and internal memory and tried updating it with stock recovery: 'sorry you cant sdcard upgrade'. That's all it says.
- ADB sideload stock recovery: 'cannot load update.zip'.
I tried different ADB versions, Windows and Mac, different drivers... I tried formatting SD card as FAT32.. Tried different SD card.. Doesn't make a difference.
TWRP log says it can't pass the Zip verification when I try that. If I turn that off it says re.product.name is wrong. But I checked build.prop and updater-script. It's the same! But somehow TWRP comes up with a different one. Also tried removing getprop and assert lines from updater-script. But then it says: ZIP file is corrupt.
TWRP log after trying original, stock B09 flash:
http://pastebin.com/cJivE2TK
Build.prop: moved from /system with TWRP:
http://pastebin.com/b6rryc2n
Build.prop: ro.product.name=P996A03
Updater-script:
Code:
getprop("ro.product.device") == "ailsa_ii" || abort("This package is for \"ailsa_ii\" devices; this is a \"" + getprop("ro.product.device") + "\".");
assert(getprop("ro.product.name") == "P996A03");
But TWRP log: ro.product.name=cm_ailsa_ii
So, yeah, I've been trying on and off for the past couple of days in between work and travelling. Got a back-up phone so it's not that bad. But I really like this phone! It's just been such a pain in the ass the past few days...
I tried researching online and reading all the XDA posts. It is my fault this has happened and feel such a newb for not being able to fix it myself
Many thanks in advance!
aPexalpha said:
Hi all,
I am currently experiencing a bootloop on my Chinese Axon 7. Some of you regulars may have seen me asking in other threads because I've tried to fix it myself, but I've kind of run out of options. Sincerely hoping one of you can help me out!!! I'll buy the winner a beer or 2, haha!
Back story:
Was on B07 with root (tenfar's tool) with locked bootloader and had some issues with the ROM. Like vibrating when I opened the camera and battery drops. So I decided to upgrade to B09. Placed the OTA on SD card and went to: Settings -> update. Worked fine. So I connected it to my PC and made a dump (tenfar's dump tool) of my recovery and boot and stored them. Then I ran the Tenfar's tool, the B09 version and it went like the last one. But when I booted I didn't have wifi, and other issues came up. So I thought: did I make a mistake? So I read it again, checked the COM port again... all checked out. And used Tenfar's tool again. After that it didn't even boot anymore! It plays the nice boot animation and then gets stuck on the end screen with all the pictures.
So after that I restored my dumped recovery.img and boot.img. This is when I knew something was wrong: it still didn't boot! I reset data/cache in the stock recovery: no boot. Still stuck at the end of the boot animation.
What I've tried:
- Flashing the stock B09 update.zip with TWRP.
- Flashing the stock B09 update.zip without updater-script 'assert' and 'get-prop' line. TWRP says 'update.zip is corrupt'. Doesn't install.
- The I put it on SD card and internal memory and tried updating it with stock recovery: 'sorry you cant sdcard upgrade'. That's all it says.
- ADB sideload stock recovery: 'cannot load update.zip'.
I tried different ADB versions, Windows and Mac, different drivers... I tried formatting SD card as FAT32.. Tried different SD card.. Doesn't make a difference.
TWRP log says it can't pass the Zip verification when I try that. If I turn that off it says re.product.name is wrong. But I checked build.prop and updater-script. It's the same! But somehow TWRP comes up with a different one. Also tried removing getprop and assert lines from updater-script. But then it says: ZIP file is corrupt.
TWRP log after trying original, stock B09 flash:
http://pastebin.com/cJivE2TK
Build.prop: moved from /system with TWRP:
http://pastebin.com/b6rryc2n
Build.prop: ro.product.name=P996A03
Updater-script:
Code:
getprop("ro.product.device") == "ailsa_ii" || abort("This package is for \"ailsa_ii\" devices; this is a \"" + getprop("ro.product.device") + "\".");
assert(getprop("ro.product.name") == "P996A03");
But TWRP log: ro.product.name=cm_ailsa_ii
So, yeah, I've been trying on and off for the past couple of days in between work and travelling. Got a back-up phone so it's not that bad. But I really like this phone! It's just been such a pain in the ass the past few days...
I tried researching online and reading all the XDA posts. It is my fault this has happened and feel such a newb for not being able to fix it myself
Many thanks in advance!
Click to expand...
Click to collapse
PM I'll help you create a flashable zip base on B10 (Full update release), just make sure to have the following apps:
- 7Zip
- Notepad++
I am was rooting my axon a2017 on b10 chinnese version without any backup after rooting got password screen after boot then i was do factory reset and format data and all looking good but after that i saw that i dont have google play app so i installed macro gapps 6.0 after flashing phone stuck on axon screen (after zte logo) for long time i been wait up to 30 minutes and nothing was done..also i have the message on twrp about the modification(dont understand why i have this message all the time) i saw in xda forum that need to install supersu so i search on internet and was flash super su 2.65 and then when i am was boot device go to zte logo screen and then turning off when i connect the device as mtp device named as a2017u (whats worng with it??? I was flashed b10 root boot.img)
I regret about this root and want to back all to stock without any problems need help from someone
I need stock b10 boot.img if someone can upload
Many thanks!
---------- Post added at 04:23 AM ---------- Previous post was at 04:11 AM ----------
DrakenFX said:
PM I'll help you create a flashable zip base on B10 (Full update release), just make sure to have the following apps:
- 7Zip
- Notepad++
Click to expand...
Click to collapse
Its will help me too i think
Dear All,
ZTE Axon 7 A2017 (Chinese version) Stuck on Bootloader mode.
Device after power on will Stuck on ZTE logo even power button press longer also will Off and came back to square one and the only way to power off is via selection on bootloader page via volume button which consists of Recovery mode, Power Off, Bootloader and some other mode which I can't recall.
History of this issue. Please bear with long story.
Manage to install MM ROM with B13 via sd card installation via update software in phone setting. follow by Unlocked bootloader and Install TWRP 3.1.1.0 then try few different ROM until one day when I use Xiaomi flashtool my PC crash half way through during flashing resulting in device with Pure Chinese ROM and TWRP also got corrupted, when I said corrupted because I install TWRP 3.1.1.0 but when I go to Recovery mode it shows TWRP 3.0 something. with this corrupted TWRP when I try to install ROM it will show loading but end result is NIL meaning same ROM nothing change.
Until this stage I never did a TWRP backup because all this while the ROM is Not my type of ROM from this junction when I boot back to TWRP and I did Advance Wipe most of it except external sd card thinking that I may be able to install fresh TWRP but my Recovery TWRP is residing in phone storage resulting in No more TWRP recovery software. next thing I did was I connect phone to PC and ran adb fastboot tool to detect device and managed to detect device in recovery mode and I make decision to Locked back the bootloader and did just that and Locked bootloader is Succes and it also Erased everything during the process.
To cut short the story after Locked back bootloader only Bootloader mode is accessible and when I connect to PC and enable Recovery mode (Black screen) and EDL mode (Black screen) from Windows PC Device Manager COM port able to see Qualcomm 9008 for this 2 mode.
I must admit after few days of trying to resolve this Stuck Bootloader issue I almost give up.
Then I remember this Woodo magic by jcadduno which recommends XM flashtool version 2016.08.30.0 but unable to flash after trying few version Xiaomi flashtool and the very latest and I mean from Xiaomi Flashtool webpage http://xiaomiflashtool.com/
version 20170425 that break the ice and finally able to load A2017U ROM because this US ROM my phone No Network detected.
From here onwards I unlocked bootloader and install back TWRP (Installation of TWRP via Axon7toolkit) because of Network issue since I got TWRP I install back A2017 ROM but still Not satisfied because Chinese ROM certain Apps having issue because of Google services and I chance upon this Conversion A2017 to A2017U ROM (Hybrid ROM caused ROM is US and Modem from Chinese Modem)
that I'm stay put right now and my phone now is A2017U model.
I hope this experience can help others with similar Stuck bootloader and those who wish to convert A2017 to A2017U ROM.
below is the link that I described Woodo magic.
https://forum.xda-developers.com/axon-7/development/edl-emergency-dl-mode-twrp-unlock-t3553514
Straight forward Axon7toolkit, please don't use Chrome browser cause Chrome will Automatically Delete it after complete download for my case I used Microsoft Edge.
https://forum.xda-developers.com/axon-7/development/tool-axon7toolkit-t3573108
below is the link to Hybrid ROM for A2017U
https://androidfilehost.com/?fid=457095661767154458 by Michael Warner After flash install No verity patch for the bootloader.
Cheers.
I am stuck in a position where I can restore my nandroid backups but get Error 7
when trying to reinstall any Rom on a2017u I was able to fix the unlocked bootloop
by the EDL method. The Rom's are the same as the backups. I think I tried to role back to B29 Causing the bootloop) and have had problems ever since.
Should I try flashing A2017Uv1.1.0B32_Bootstack_by_DrakenFX since the Rooms are all B32?
The B15 and B19 Nandroid's still Restore fine.
Hello all,
i don't get onto forums very often but i thought this was a nice one to add to. i've rooted a few motorolas, a few ztes, a cat; i've also bricked those ztes, cat & a few samsungs. i'm dealing with two Axon7U's; one is factory MM-b29, the other is N-b35.
while screwing around with TWRP, i bricked the b35 (the b29 has been bricked for a month at this time) after i had it almost perfected. by perfected i mean a custom recovery & root user access fully acquired. with DrakenFX's {YOURS; thanks so much. i'm learning to get along with linux} extensive files created to save people from themselves i was able to unbrick the b35. albeit its CELLULAR DATA became unhinged; that's something i could've lived with except it was a loaner and had NO CAMERA! it's camera (along with the ability to push both volume buttons at once for say EDL mode...) was damaged having been beaten across a steering wheel several times. so with my newfound unbricking superpowers i decided to take another crack at the b29. managed to get it unbricked but couldn't get it setup with both TWRP & SuperSU without losing one, the other or, both. at times it didn't even boot up. i was doing pretty much everything cited above for reasons 'why'. best way to learn is by trial & error (if one can afford it).
the b29 is rooted right at this moment; i'm working on it as soon as i leave this posting. i used Axon7_EDL_Tool. i used Axon7root. i used MiFlash. i used Fastboot. I used ADB App Controller software too. back & forth i fought for three days mostly due to downloading glitches and i prevailed. i manipulated a stock OTA full system update.zip by happenstance and it Auto_Updated over itself. in other words it already had the same ROM installed. i don't know what it tested to realize it needed to update to what it already had. it didn't have CELLULAR DATA either. just like the b35, it broke somehow while flashing TWRP or SuperSU. funny thing is it still wanted to update that same ROM after it did. while perusing the system update setting(s) i noticed it had downloaded N-b15 and it wanted to update b29 AGAIN! i opted for the Nougat update. it did alright and appears to have fixed it's CELLULAR DATA too. i haven't looked at it since but i'm confident i can gain root user access with a minimal amount of effort.
The main problem i've had with dealing with bricked devices is the age of the file downloads. most of them are simply GONE!, expired links and whatnot. if i'd had a clear path say from a custom recovery and rooted boot image of my factory version or the path that leads to it, i'd have been fixed up long ago. i've found partial 'paths' if you will that almost get me there but no quite all the way. flashing images & zips through fastboot are different from their counterparts entered through TWRP or Emergency Download Mode which of course are both different too. three different ways to get into one's phone makes it almost impossible to keep them perfected.
i'm not sure i did what i'm supposed to regarding this thread. Thank you DrakenFX for your time & knowledge; you've saved my old Axon7!
Hello all update;
b35 Nougat phone is retired. b29 managed to update itself to b35 7.1.1. however, its CELLULAR DATA is still broken. i haven't managed to figure out how or where it's broken so i cannot fix it.
what i'm trying to do now is flash Magisk instead of SuperSU and using a TWRP version 3.0.3-1. heck i've used all of TWRP's versions in my efforts to reacquire CELLULAR DATA.
crazy part is the phone knows its CELLULAR DATA carrier and freely displays all of its hookup info. this is very frustrating.
So I followed a tutorial online to install Android Nougat 7.0 on my Huawei P9 lite. Once I was in TWRP I realised I was supposed to install two update files from two different .zip files. Trouble is I only had the one update on my phone at the time. I didn't want to exit TWRP at that stage because I already installed one of the update files.
When I booted my phone after the update, it all seemed to be working with 7.0 installed. Then I noticed my internet data wasn't working outside of wifi, and my bluetooth isn't turning on. The rest seems to be running fine other than those two things.
I rely a lot on bluetooth and internet on the go. I need it back, does anyone know what I could do, outside of factory reset?
Thanks
factory reset wouldn't help, you need to reflash update.zip and data_full.zip AT SAME TIME without rebooting
Coolyou said:
factory reset wouldn't help, you need to reflash update.zip and data_full.zip AT SAME TIME without rebooting
Click to expand...
Click to collapse
Okay, I realised that just now. Trouble is I am having trouble booting into TWRP now. I just get "your device has been unlocked and can't be trusted." with an orange web link.
For some reason my phone says in the settings that I'm still on android 4.3 although the ui and functionality is 7.0. Also, the EMUI is 2.0. I don't know how I got TWRP working before but I think there's a conflict due to it half being 7.0 so recover won't boot. I have tried loads of tutorials online but none of the rocovery.img or twrp.img files are working.
have the exact same problem, on android 4.3 and stuck.
from what i understand to dload a working stock rom, you need to have the correct oem info that matches the recovery stock rom. i cant flash any OEMinfo as i cant get root from revolution recovery.
no access to Data partition either.
no other recovery's to install as its the only one for nougat.
So i need help for this issue too.
jackvdbuk said:
have the exact same problem, on android 4.3 and stuck.
from what i understand to dload a working stock rom, you need to have the correct oem info that matches the recovery stock rom. i cant flash any OEMinfo as i cant get root from revolution recovery.
no access to Data partition either.
no other recovery's to install as its the only one for nougat.
So i need help for this issue too.
Click to expand...
Click to collapse
I fixed it! It was more simple than I realised. I used the dload folder method; Placing the update.app into a folder called 'dload' on an sdcard. Then holding power, both volume buttons to initiate the update.
Thanks for your help guys!!
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)
Hi
I got my self in quite a pickle here..
so advice or help is very welcomed.
I own a Huawei P10 lite,
with a software version WAS-LX1AC900B049
First off I unlocked the phone, then flashed TWRP recovery, and thus far everything was ok
I wanted to install Lineage 14.1 OS, and I failed because my version of the phone is not supported..
but during attempt installation of Lineage OS , I deleted data, system, dalvik, and cashe..
I did not make a backup!!! (major mistake, I know..)
so effectively I deleted my OS :-/ ..
but it isn’t over jet..
because I could not find a stock rom, namely WAS-LX1AC900B049 version
I thought of debranding my phone to Orange, namely WAS-LX1AC109B110 because stock roms for Orange are available on the net.
so.. using TWRP I replaced oeminfo file..
(this time making a backup of oeminfo)
but once I downloaded Orange stock rom, put it on the
sdcard in /dload folder and entered download mode on the phone, nothing happened, update failed
but.. also changing oeminfo resets the system so I guess that turned off USB debugging..
so now the TWRP is not available because of the system reset, and in the fastboot and rescue mode , adb program from Windows, does not detect device..
so..
it seems I have 3 options..
1. somehow install Orange stock rom
2. make fastboot and rescue mode to work properly so I can reinstall TWRP and go further from there
3. find original stock rom WAS-LX1AC900B049, may be it will work
by the way erecovery does not work, it conects to the wifi, starts serching, and then fails
Help please..
I unbricked the phone
for anyone interested I used adb to unlock the phone in fastboot and rescue mode..
the phone was showing me a message that it was unlocked but it was not
once unlocked previously installed TWRP booted immediately, so from there I installed Lineage 14.1 by HassanMirza01 and it works great
Happy that you fixed your problem but how did adb detected your device as you mentioned it didn't at the first place?
Planning on going back to stock and I think the same trouble would happen for me too.
oH MY GOD!
ultragorki said:
Hi
I got my self in quite a pickle here..
so advice or help is very welcomed.
I own a Huawei P10 lite,
with a software version WAS-LX1AC900B049
First off I unlocked the phone, then flashed TWRP recovery, and thus far everything was ok
I wanted to install Lineage 14.1 OS, and I failed because my version of the phone is not supported..
but during attempt installation of Lineage OS , I deleted data, system, dalvik, and cashe..
I did not make a backup!!! (major mistake, I know..)
so effectively I deleted my OS :-/ ..
but it isn’t over jet..
because I could not find a stock rom, namely WAS-LX1AC900B049 version
I thought of debranding my phone to Orange, namely WAS-LX1AC109B110 because stock roms for Orange are available on the net.
so.. using TWRP I replaced oeminfo file..
(this time making a backup of oeminfo)
but once I downloaded Orange stock rom, put it on the
sdcard in /dload folder and entered download mode on the phone, nothing happened, update failed
but.. also changing oeminfo resets the system so I guess that turned off USB debugging..
so now the TWRP is not available because of the system reset, and in the fastboot and rescue mode , adb program from Windows, does not detect device..
so..
it seems I have 3 options..
1. somehow install Orange stock rom
2. make fastboot and rescue mode to work properly so I can reinstall TWRP and go further from there
3. find original stock rom WAS-LX1AC900B049, may be it will work
by the way erecovery does not work, it conects to the wifi, starts serching, and then fails
Help please..
Click to expand...
Click to collapse
YOU DID AS EXACTELLY AS ME ...HAHAHAHAHAHAHAH and now im still tryiong to find it solutution ...have you found some?
Hello,
In a late-night act of utter stupidity, when over-tired, I re-flashed the boot recovery with TWRP and bricked my M3. It obviously can't now enter boot recovery.
I've used TWRP and successfully re-flashed custom roms on my original Mate, and changed regions. (Not in any way an expert, I know how to follow instructions.)
I was trying to convert my Chinese (I was living there) ROM to UK. It's tricky nowadays.
This was a stupid error when tired. Any way back?
I read somewhere that people with the right hardware can do it, but finding someone. I'm in Leeds, UK.
The pad does (did) what I need, and I'm not in a position to buy a new one. If it's dead, it's dead; and I can move on.
Cheers in advance for any input.
SOLVED
See my last post on this thread.
After using Multi Tool V8 to enquire into the machine I switched off and rebooted.
It came back with a "Wipe cache" and "Reset to factory settings" Huawei screen, so I did both and - It booted!
It had spectacularly failed to do anything but boot-loop since coming out of a very dead battery yesterday.
1) Boot recovery, OTA recovery, and dload recovery from SD were all unavailable after the original overwriting of the bootloader.
2) After being dead for months, all recovery options booted from power button plus vol- Vol+ and Vol+/- - but still bootlooping.
Then, suddenly it booted into wipe cache/factory reset screen.
Android 7, EMUI 5.1.3
I have no idea why.
Now fully working. (Including restarting)
I fell in a similar situation after having flashed a magisk module .. unfortunately my nandroid backup didn't restore my devices, but I was able to enter in twrp recovery.. so,..
if you can boot in twrp recovery, not all hopes are lost..
first of all, you must download a stock firmware for your device (i suggest to download trough huawei firmware finder: https://forum.xda-developers.com/tools/general/huawei-firmware-finder-team-mt-t3469146/amp/)
You must download a fullota version of stock firmware
then, you can flash this firmware (3 zip files) trough hurupdater via twrp recovery: https://forum.xda-developers.com/ho...lash-official-firmware-recovery-t3769279/amp/
in order to not overwrite twrp recovery, put the twrp.img file in the same folder and rename it to recovery.img
you can find more info in this topic (follow the instructions, in particular those on how to use hurupdater): https://forum.xda-developers.com/me...ting-btv-dl09-to-unapproved-firmware-t3817541
in order to find a firmware suitable to your device, try to find info on it: you have a mediapad m3 European? American? asian? just wifi or also 4G-LTE (whit a sim and phone functions)? lite or normal version? 10 inches or 8.4?
everyone of these devices have different codenames and suitable firmwares
I found exact firmware for my devices with the procedure described here:
https://forum.xda-developers.com/showpost.php?p=77241673&postcount=3
.. but, if you flashed a wrong firmware, i really don't know if it might help you..
anyway, i wish the info above could help you.
qllkevuoi said:
I fell in a similar situation after having flashed a magisk module .. unfortunately my nandroid backup didn't restore my devices, but I was able to enter in twrp recovery.. so,..
if you can boot in twrp recovery, not all hopes are lost..
first of all, you must download a stock firmware for your device (i suggest to download trough huawei firmware finder: https://forum.xda-developers.com/tools/general/huawei-firmware-finder-team-mt-t3469146/amp/)
You must download a fullota version of stock firmware
then, you can flash this firmware (3 zip files) trough hurupdater via twrp recovery: https://forum.xda-developers.com/ho...lash-official-firmware-recovery-t3769279/amp/
in order to not overwrite twrp recovery, put the twrp.img file in the same folder and rename it to recovery.img
you can find more info in this topic (follow the instructions, in particular those on how to use hurupdater): https://forum.xda-developers.com/me...ting-btv-dl09-to-unapproved-firmware-t3817541
in order to find a firmware suitable to your device, try to find info on it: you have a mediapad m3 European? American? asian? just wifi or also 4G-LTE (whit a sim and phone functions)? lite or normal version? 10 inches or 8.4?
everyone of these devices have different codenames and suitable firmwares
I found exact firmware for my devices with the procedure described here:
https://forum.xda-developers.com/showpost.php?p=77241673&postcount=3
.. but, if you flashed a wrong firmware, i really don't know if it might help you..
anyway, i wish the info above could help you.
Click to expand...
Click to collapse
Thanks for the reply, and sorry for the delay. New child has somewhat taken over our lives!
I'll take a look at the tablet again when I have time, probably next month.
Update - Bootloader working after battery drain: Now what?
[Edit] Post redundant as it started working - see OP.
NwotNot said:
Thanks for the reply, and sorry for the delay. New child has somewhat taken over our lives!
I'll take a look at the tablet again when I have time, probably next month.
Click to expand...
Click to collapse
Well...
After being without power for so long I turned the tablet on and it booted!
However, it then went into OTA and updated - rebooted - and locked the damned bootloader.
1) It's showing as rooted.
2) Boot loader is locked.
3) Fastboot & rescue mode comes up.
4) Recovery (OTA) still comes up but "Fails" this time.
I don't recall how I unlocked it last time. I don't ever rememebr an unlock code.
Status:
Fastboot reports it exists.
ADB reports "Null" not found. (ADB drivers installed).
Firmware version: CPN-AL00C233B078
Device name: CPN-AL00
Serial Number: Showing
IMEI: Showing
Bootloader state: LOCK
I have an old TWRP backup - don't know how to use it.
Solutions?
a) Any kind devs prepared to work with me and find the boot unlocker code for this 5-year old tablet?
b) Any other solutions now we know what's what?
I'm self employed without income in this pandemic and can't really afford to buy a new tablet. If I have to, it won't be Huawei.
(There's a T3 10.6" at £89, but I'm not biting - I need to sort out a budget tablet with at least the oomph of the M3.)
Any help much appreciated. :good:
David.