Downgrade from lollipop b312 to kitkat b143 - Ascend Mate 7 Q&A, Help & Troubleshooting

As the title, anyone know how? I tried the transitional b300 but failed. Tq in advanced

I just did mine couple of days ago. Rollback to b300 worked without any issues. Then trying to install b141 I couldn't get it working( 3 button method wasn't getting to installation screen, it was rebooting device after huawei logo). So I tried few times with SD card taken out, worked after 3rd time(you have to push the card in just when the huawei logo is going off).
Not sure why you cannot install transition pack, what phone have you got? Is your recovery stock? Phone rooted and unlocked?

muzammil84 said:
I just did mine couple of days ago. Rollback to b300 worked without any issues. Then trying to install b141 I couldn't get it working( 3 button method wasn't getting to installation screen, it was rebooting device after huawei logo). So I tried few times with SD card taken out, worked after 3rd time(you have to push the card in just when the huawei logo is going off).
Not sure why you cannot install transition pack, what phone have you got? Is your recovery stock? Phone rooted and unlocked?
Click to expand...
Click to collapse
Where can I find b300?
Sent from my HUAWEI MT7-TL10 using Tapatalk

muzammil84 said:
I just did mine couple of days ago. Rollback to b300 worked without any issues. Then trying to install b141 I couldn't get it working( 3 button method wasn't getting to installation screen, it was rebooting device after huawei logo). So I tried few times with SD card taken out, worked after 3rd time(you have to push the card in just when the huawei logo is going off).
Not sure why you cannot install transition pack, what phone have you got? Is your recovery stock? Phone rooted and unlocked?
Click to expand...
Click to collapse
R u malaysia? Btw.. Can i hv the b300 link

It always stuck at 19%

Dekdek1 said:
R u malaysia? Btw.. Can i hv the b300 link
Click to expand...
Click to collapse
No man UK.
http://www.carbontesla.com/2015/07/how-to-downgrade-ascend-mate-7-to-kitkat-firmware/

why u all downgrading .. u love so much lolipop all sudden dont like it ?

because it's a performance step back, phone is almost non usable on lollipop.

if you have L09, from B300 you can flash B137Sp03, then you can flash any kitkat you want

I just want to go back to kitkat lollipop is boring , i stuck on 19% on rolling back of MT7-tl10

muzammil84 said:
because it's a performance step back, phone is almost non usable on lollipop.
Click to expand...
Click to collapse
Update to 317 it is really cool..

XDADEVX said:
Update to 317 it is really cool..
Click to expand...
Click to collapse
yeah, done it few days ago, big improvement over b308 and b312.

Anybody else here stuck on B300 transition? I can't seem to flash back to B137 or B145...keep getting stuck at 19% and menu says failed. I was at B327 5.1.1, flashed B300 and now I'm stuck.
Any ideas? Please help.

jfer671 said:
Anybody else here stuck on B300 transition? I can't seem to flash back to B137 or B145...keep getting stuck at 19% and menu says failed. I was at B327 5.1.1, flashed B300 and now I'm stuck.
Any ideas? Please help.
Click to expand...
Click to collapse
Have you tried flashing KitKat B119?
For the model TL10, here is the link: http://consumer.huawei.com/en/support/downloads/detail/index.htm?id=32364
Let me know if it works or not.

kingrk said:
Have you tried flashing KitKat B119?
For the model TL10, here is the link: http://consumer.huawei.com/en/support/downloads/detail/index.htm?id=32364
Let me know if it works or not.
Click to expand...
Click to collapse
I'm MT7-L09...tried the lowest firmware 127 up to 148, no luck.

jfer671 said:
I'm MT7-L09...tried the lowest firmware 127 up to 148, no luck.
Click to expand...
Click to collapse
Can you try this?
Upgrade to firmware B308 by downloading from here for L09 -> http://www.carbontesla.com/2015/06/download-ascend-mate-7-b308-lollipop-ota-zip-emui-3-1/
Then follow this guide:
http://www.carbontesla.com/2015/07/how-to-downgrade-ascend-mate-7-to-kitkat-firmware/
Best

Ok, problem solved. Before being stuck, I was on 145, then >148...wanted 145 back, and flashed 300. Somehow was able to then upgrade to 324 and >327. Camera is really slow on 5.1.1 and somehow doesn't take full pics (leaves gallery with multiple "no image") files.
Flashed 300 again and became stuck for the past two weeks. Re-flashing and factory resetting failed as well. Read somewhere on the forum to not factory reset on 5.1.1, after the fact, and thought I'd been soft-bricked.
**Update: finally was able to unlock boot-loader; and via adb/fastboot, re-flashed 300>324>327.
Thinking of going back 145 if I can't find solution for LP root.
Thanks for all the input tho, helped in organizing my thoughts on what went wrong.

How did you flash using fastboot. Can you write the procedure please. Did you use a custom recovery or directly flash using fastboot?
Sent from my HUAWEI MT7-TL10 using Tapatalk

kingrk said:
How did you flash using fastboot. Can you write the procedure please. Did you use a custom recovery or directly flash using fastboot?
Sent from my HUAWEI MT7-TL10 using Tapatalk
Click to expand...
Click to collapse
You need to be on correct firmware version (KK or LP) to flash correctly.
-Extract correct firmware using Huawei Update Extractor (127-137SP03), and highlight boot, recovery img
-Power down device and do Volume - and Power with usb plugged (to enter rescue mode)
-Shift + right click inside adb/fastboot folder (to open command prompt)
-Type: adb devices (to make sure it recognizes, you should see your device number)
-Type: fastboot flash boot boot.img (wait a few seconds, success)
-Type: fastboot flash recovery recovery.img (wait few seconds again, success)
-Type: fastboot reboot (your device should reboot and flashed to the firmware you chose.
---------- Post added at 03:38 PM ---------- Previous post was at 03:35 PM ----------
jfer671 said:
You need to be on correct firmware version (KK or LP) to flash correctly.
-Extract correct firmware using Huawei Update Extractor (127-137SP03), and highlight boot, recovery img
-Power down device and do Volume - and Power with usb plugged (to enter rescue mode)
-Shift + right click inside adb/fastboot folder (to open command prompt)
-Type: adb devices (to make sure it recognizes, you should see your device number)
-Type: fastboot flash boot boot.img (wait a few seconds, success)
-Type: fastboot flash recovery recovery.img (wait few seconds again, success)
-Type: fastboot reboot (your device should reboot and flashed to the firmware you chose.
Click to expand...
Click to collapse
Sorry, make sure to put extracted boot/recovery img files into adb/fastboot folder, and then proceed with Shift + right click

Related

Need help. I think its dead.

I have an AL-10 64GB mate 8. I wanted to turn it to the iternational ROM to have google apps. I followed this guide: http://forum.xda-developers.com/mate-8/general/howto-load-international-mate-8-t3293619
Afte flashing with fastboot commands the files my phone doesn't boot up. It shows the warning screen because it is Unlocked but I doesn't boot in menu.
u forgot to flash boot.img, try that through fastboot as well and then try and boot again
jbmc83 said:
u forgot to flash boot.img, try that through fastboot as well and then try and boot again
Click to expand...
Click to collapse
There isn't a boot.img in the thread there. Where do I find it?
So I thought to try myself something... I flashed the oldest boot.img from this thread: http://forum.xda-developers.com/mate-8/orig-development/kernel-insecure-boot-img-t3311306 (B156 FLASHABLE IMG). The only difference now is that it remains stuck at the warning scrren. Previously that screen would dissapear and the phone would be total black.
Also I downloaded the update.app from here: http://forum.xda-developers.com/mate-8/general/nxt-l09-nxt-l29-stock-rom-b133-download-t3311839 of L29. Extracted boot,cache,cust,system,recovery,userdata from that package and flashed all files with fastboot. Everything successful but still stucked at warning screen.
eltarod said:
Also I downloaded the update.app from here: http://forum.xda-developers.com/mate-8/general/nxt-l09-nxt-l29-stock-rom-b133-download-t3311839 of L29. Extracted boot,cache,cust,system,recovery,userdata from that package and flashed all files with fastboot. Everything successful but still stucked at warning screen.
Click to expand...
Click to collapse
try this first
1- go to recovery then factory reset then reboot if not booting so try this method below (use same update.app file)
rowihel2012 said:
Download the update file
Extract
Folder "dload" at the root level of the memory Share (internal or external).
Update.app in the folder "dload" Copy
As Huawei has removed the item "Local Update" from the update program, you must do the following:
Option 1: update via ForceUpdate
Switch off
Simultaneously Power + Volume Down + volume Louder press until the update starts
Click to expand...
Click to collapse
dload doesn't work. I did manage to install TWRP though... Will try to flash a custom ROM
So I managed to make it boot using DarkSilentSC instruction: http://forum.xda-developers.com/mat...ng-to-b321-t3375934/post66776218#post66776218
Only 2 problems left. First the memory shows 4GB rather than 64GB and there is no theme support. Any idaes?
hmmm....try and go to recovery and format the data partition, maybe that helps.... just make sure u dont have any important data on the phone before u do that
Data partition is:
TWRP - wipe - advanced wipe - tick data and slide to start?
Sent from my HUAWEI NXT-L29 using Tapatalk
Nevermind I did it thanks to jbmc83. The solution for anyone that has the same problem is to format data partition. It's in twrp-wipe the right button. Thanks to jbmc83 and to all that helped me!!
Sent from my HUAWEI NXT-L29 using Tapatalk
yep thats correct although i think ull have to type "yes" in order to start it. in any case, just follow the screen instructions! also, be aware that this takes a lot of time, so wait at least half an hour before giving up ^^ let it run its course!
edit: ah ok, i just saw that it worked! glad it did
Huawei mate 8, hard bricked while it's updating. Pho
Huawei mate 8, hard bricked while it's updating custom rom. Phone is not responding at all. No power, black screen, it i put on charging, doesn't feeling like battery charging. Can someone help me out this problem.
Yes, if you can go into bootloader mode, kindly run these commands and report back what are the results.
fastboot oem get-product-model
fastboot getvar vendorcountry
fastboot oem get-build-number
dear phone doesn't respond at all. not connecting to pc. no sign of power.
Syd2Ldh said:
dear phone doesn't respond at all. not connecting to pc. no sign of power.
Click to expand...
Click to collapse
Which rom were you try to flashing which caused this issue?

Honor 8 Bricked

Hello everyone,
I'm actually in front of a big problem. I try this night to upgrade from FRD-L09C432B120 to FRD-L09C432B316. Since I try it, my phone stay on a Warning screen and i can't do anything. (Just try to shut down by a long press on power button and it make a reboot and it's the same for every key combination).
I can't go in Recovery or eRecovery. The only things that works is the fastboot mode. I try to flash the stock firmware after an extract of "UPDATE.APP" but the system image give me an error. I also try to put UPDATE.APP on the SD Card but I can't access to the update mode (by press vol+ , vol- and power button). I think that i've try all the ideas that i've fund on internet !
I've no more ideas. Do you think that is possible to unbrick it ?
Thanks to your help and your reply.
Flo.B said:
Hello everyone,
I'm actually in front of a big problem. I try this night to upgrade from FRD-L09C432B120 to FRD-L09C432B316. Since I try it, my phone stay on a Warning screen and i can't do anything. (Just try to shut down by a long press on power button and it make a reboot and it's the same for every key combination).
I can't go in Recovery or eRecovery. The only things that works is the fastboot mode. I try to flash the stock firmware after an extract of "UPDATE.APP" but the system image give me an error. I also try to put UPDATE.APP on the SD Card but I can't access to the update mode (by press vol+ , vol- and power button). I think that i've try all the ideas that i've fund on internet !
I've no more ideas. Do you think that is possible to unbrick it ?
Thanks to your help and your reply.
Click to expand...
Click to collapse
But please confirm , was the update from b120 to b316 successfull?
Sent from my KIW-L22 using Tapatalk
gopinaidu77 said:
But please confirm , was the update from b120 to b316 successfull?
Click to expand...
Click to collapse
I think it failed because the warning screen showed right?
Sent from my honor 5X using XDA Labs
adriansticoid said:
I think it failed because the warning screen showed right?
Click to expand...
Click to collapse
Right that was what I am also thinking bro.
---------- Post added at 01:35 PM ---------- Previous post was at 01:35 PM ----------
adriansticoid said:
I think it failed because the warning screen showed right?
Sent from my honor 5X using XDA Labs
Click to expand...
Click to collapse
So it's a failure . which mean that it is a semi flashed update . which doesn't installed update.app .
Extract update.app from ota and put it in dload folder .later flash it manually using dload method .
He should follow this way to overcome those reboots
Sent from my KIW-L22 using Tapatalk
---------- Post added at 01:36 PM ---------- Previous post was at 01:35 PM ----------
Flo.B said:
Hello everyone,
I'm actually in front of a big problem. I try this night to upgrade from FRD-L09C432B120 to FRD-L09C432B316. Since I try it, my phone stay on a Warning screen and i can't do anything. (Just try to shut down by a long press on power button and it make a reboot and it's the same for every key combination).
I can't go in Recovery or eRecovery. The only things that works is the fastboot mode. I try to flash the stock firmware after an extract of "UPDATE.APP" but the system image give me an error. I also try to put UPDATE.APP on the SD Card but I can't access to the update mode (by press vol+ , vol- and power button). I think that i've try all the ideas that i've fund on internet !
I've no more ideas. Do you think that is possible to unbrick it ?
Thanks to your help and your reply.
Click to expand...
Click to collapse
Consider reading my above post bro.
Sent from my KIW-L22 using Tapatalk
HONOR 8 Bricked
Hello ,
It happened on my FRD-L04, but I think is the same.
Bootloader is unlocked ?
1. Do you have all drivers installed ? OK
2.Do you have STOCK ROM ? OK. If not, use Huawei Firmare Finder to find suitable ROM. Be aware what you choose !!!
3. Unzipp (WinRar) the ROM.
4.Download and install Huawei Update Extractor. Run Huawei Update Extractor . Choose Update.app from the folder you unzipped the ROM.
5. Select cust.img , boot.img , recovery.img and system.img and extract them on a folder.
6.. Install MultiTool by Team (Multi Tool Team). The instalation will make a folder named UNBRICK.
7. Move the files extracted : cust.img , boot.img , recovery.img and system.img on the folder UNBRICK
8. Run MultiTool . Choose option 6 (unbrick) and after that choose option 2 ( if you already have files on folder UNBRICK)
9. Let the tool finish the job.
NOTE : You must have all drivers installed and the phone in FASTBOOT mode ( turn phone OFF - Press VOL- and insert USB cable simultaneously.)
Good luck !
Hi, thanks everyone for your reply.
Unfortunatly, the dload method seems not work. I think that to run this method, i need to press simultaneously vol+, vol- and the power button to run it, right ?
If it's like that, the method doesn't work anymore.
I will try the process given by technoguy09 and I said to you if it's ok !
So, after many try, every method that i try doesn't work.
Even the Unbrick method doesn't work because the system and cust report an error.
For the cust, i have "partition error" and for the system I have the "sparse flash write failure". Can we correct this error ?
Flo.B said:
So, after many try, every method that i try doesn't work.
Even the Unbrick method doesn't work because the system and cust report an error.
For the cust, i have "partition error" and for the system I have the "sparse flash write failure". Can we correct this error ?
Click to expand...
Click to collapse
Was the bootloader unlocked ?
Do u have twrp installed ?
Sent from my KIW-L22 using Tapatalk
---------- Post added at 03:53 PM ---------- Previous post was at 03:53 PM ----------
Flo.B said:
Hi, thanks everyone for your reply.
Unfortunatly, the dload method seems not work. I think that to run this method, i need to press simultaneously vol+, vol- and the power button to run it, right ?
If it's like that, the method doesn't work anymore.
I will try the process given by technoguy09 and I said to you if it's ok !
Click to expand...
Click to collapse
If u have twrp I will make a flashable zip of stock ROM and cust
Sent from my KIW-L22 using Tapatalk
The bootloader is unlock and TWRP was install but now I can't access it. I try to restore stock recovery and it's the same result.
Flo.B said:
The bootloader is unlock and TWRP was install but now I can't access it. I try to restore stock recovery and it's the same result.
Click to expand...
Click to collapse
Can fastboot detect your phone?
Yes, fastboot is detect, I can launch some command (fastboot devices display my phone, flash etc) everything work but flash recovery didn't change anything and flash system response an error (sparse flash write failure).
Flo.B said:
Yes, fastboot is detect, I can launch some command (fastboot devices display my phone, flash etc) everything work but flash recovery didn't change anything and flash system response an error (sparse flash write failure).
Click to expand...
Click to collapse
From what you said, looks like it is reallt bricked. Service center is your friend.
I think too... I hope that there will be no problem with service center because of the phone is unclocked !
I was never had this kind of problem with my previous android phone. I'm really bad ^^
Thanks for all everybody.
Flo.B said:
So, after many try, every method that i try doesn't work.
Even the Unbrick method doesn't work because the system and cust report an error.
For the cust, i have "partition error" and for the system I have the "sparse flash write failure". Can we correct this error ?
Click to expand...
Click to collapse
Try another ROM.
Flo.B said:
I think too... I hope that there will be no problem with service center because of the phone is unclocked !
I was never had this kind of problem with my previous android phone. I'm really bad ^^
Thanks for all everybody.
Click to expand...
Click to collapse
Goodluck with it buddy.
technoguy09 said:
Try another ROM.
Click to expand...
Click to collapse
I try at least 3 ROM download on different website. I don't think that it can change anything.
I had the same problem.
Dont worry, Honor 8 phones are nearly unbrickable.
Take your B120 ROM extract recovery, cust and boot partitions. (use huawei update extractor)
Flash Them via fastboot (adb) then force the dload method via the 3 buttons combo.
I had all the problems you described and restored my phone as new. (even the "sparse flash write failure" error)
Now i'm on EMUI 5 rooted, no problem
---------- Post added at 06:30 PM ---------- Previous post was at 06:25 PM ----------
Please refer this thread as it might help you.
http://forum.xda-developers.com/mate-8/general/fuss-debrick-restore-mate-8-t3457969
Have a little faith in your Honor
Flo.B said:
I try at least 3 ROM download on different website. I don't think that it can change anything.
Click to expand...
Click to collapse
Did you use Huawei Firmare Finder for your model ?
morpheus302 said:
I had the same problem.
Dont worry, Honor 8 phones are nearly unbrickable.
Take your B120 ROM extract recovery, cust and boot partitions. (use huawei update extractor)
Flash Them via fastboot (adb) then force the dload method via the 3 buttons combo.
I had all the problems you described and restored my phone as new. (even the "sparse flash write failure" error)
Now i'm on EMUI 5 rooted, no problem
---------- Post added at 06:30 PM ---------- Previous post was at 06:25 PM ----------
Please refer this thread as it might help you.
http://forum.xda-developers.com/mate-8/general/fuss-debrick-restore-mate-8-t3457969
Have a little faith in your Honor
Click to expand...
Click to collapse
I have extract all this img but the flash of cust won't work too so, the dload method can't be launch. Now, I send my phone to the service center yesterday. Wait and See ^^
technoguy09 said:
Did you use Huawei Firmare Finder for your model ?
Click to expand...
Click to collapse
Yes, I Download 2 ROM on it but same problem on both.
Flo.B said:
I have extract all this img but the flash of cust won't work too so, the dload method can't be launch. Now, I send my phone to the service center yesterday. Wait and See ^^
Yes, I Download 2 ROM on it but same problem on both.
Click to expand...
Click to collapse
Leave it for service centre people .they will take care
Sent from my KIW-L22 using Tapatalk

L-29C900B*** Problem no C432

Hello XDA-Guys,
i think i might found a Problem - i wanted to flash Nougat (B560)... it didnt worked via TWRP.
So i wanted to go back to stock B152 to upgrade via OTA Update.
And then i relised that my TWRP is backing up everyrom with C900B170! My Huawei Mate8 says its C900B180!
but the most thing that ****s up is that i install C432B152 from here - and when its done im on C900B152...
so orignal it should be C432 since im from Germany but i only get C900 - that sucks because only C432 get Nougat, right?
Or to sort the Topic:
Is the b560 still beta? I got my eyes on a online article that says huawei is rolling out B560!
If someone has some infos for me that would be fine.
The C900/C432 is not a problem for me so no troubleshooting needed - but if it denies me the Nougat Update then i need help ( if its not beta anymore).
Thanks guys
can you fix it? I have the same problem and nothing
senseijulio said:
can you fix it? I have the same problem and nothing
Click to expand...
Click to collapse
since no one is helping here, no i still have the problem.
EGOiST1991 said:
since no one is helping here, no i still have the problem.
Click to expand...
Click to collapse
Root you phone then change ro.build = NextL09C999B100 and oeminfo = C432 by using SRK Tools
Sent from my HUAWEI NXT-L29 using XDA Labs
I allready rooted my PHone then i try the srk-tool thanks a lot.
EGOiST1991 said:
I allready rooted my PHone then i try the srk-tool thanks a lot.
Click to expand...
Click to collapse
Glad you managed to rooted your phone.
Sent from my HUAWEI NXT-L29 using XDA Labs
@EGOiST1991 and @dexz I'm having the same problem. I am on C636B320 but it's shown as C900B320 so when I try to follow the guide to update to C432B560 it fails.
My plan was first to get the phone recognised as C636 and then via the srk tool debrand to C432 and then when in TWRP 3.0.2 emui 4.1 follow the guide to get to C432B560.
Now the problem I am having is that I don't know how to get my phone to go from C900 to C636... I'm the srk tool my phone isn't recognised when the tool runs adb server. I belive that is because it is on C900 to begin with, I have HiSuite installed on the computer (Win 10). The files, oeminfo and custom.bin, for C636 are in the tools folder can't I just manually put them in the correct location?
Edit: I have unlocked bootloader and I'm rooted FYI
Edit2: Gotten the computer to recognise the phone. But when I run the srk tool to flash oeminfo and custom.bin it stops at "waiting for device". If I run adb devices I can see my device number but after it says Offline.
An other problem I have noticed is that TWRP 3.0.2-0-next.img doesn't seem to accept my decrypted/insecure_boot_B320.img which is need to format data before flashing B560. The only TWRP version that accepts/hold the decrypted/insecure boot.img is TWRP_3.0.2-0_BLACK_BLUE_EMUI4.1.img
http://cloud.tapatalk.com/s/589fa1f505b9e/Screenshot_2017-02-12-00-35-19.png
Skickat från min NEXT via Tapatalk
Don't everyone answer all at once lol
@EGOiST1991 how has it gone for you, have you managed to update?
Skickat från min NEXT via Tapatalk
@Leo - SRK tool worked fine fro me (im also c900 and rooted so should be your fault) REMEMBER u need to plug your phone in booted up! NOT in fastboot mode!!!
no i didnt managed it yet. i tryd to go back to stock recovery and then the dload method but it failed. so i guess its bc im c900....
EGOiST1991 said:
@Leo - SRK tool worked fine fro me (im also c900 and rooted so should be your fault) REMEMBER u need to plug your phone in booted up! NOT in fastboot mode!!!
no i didnt managed it yet. i tryd to go back to stock recovery and then the dload method but it failed. so i guess its bc im c900....
Click to expand...
Click to collapse
Yeah I am in boot mode but the srk tool still doesn't find my device or rather running adb devices returns device number with comment Offline. Which is strange because if instead go to fastboot and run fastboot devices I can see my device with no problem, so that to me seem like it's not an USB driver issue.
As soon as I am able to debrand to C432 I will give it a go again. At the moment I'm trying to find a way to manually change. I'm going to post a comment on QA for that.
Skickat från min NEXT via Tapatalk
DUDE ! AGAIN! FOR THE SRK TOOL DONT!!!! GO IN FASTBOOT!
just plug your phone to your computer when its on and ready to use!
SRK will boot your phone in fastboot
EGOiST1991 said:
DUDE ! AGAIN! FOR THE SRK TOOL DONT!!!! GO IN FASTBOOT!
just plug your phone to your computer when its on and ready to use!
SRK will boot your phone in fastboot
Click to expand...
Click to collapse
Dude!!! read my reply again, I'm not in fastboot when running the srk tool or running the adb commands...
Skickat från min NEXT via Tapatalk
Leo_83 said:
Dude!!! read my reply again, I'm not in fastboot when running the srk tool or running the adb commands...
Skickat från min NEXT via Tapatalk
Click to expand...
Click to collapse
DUDE! then im sorry
quick update worked for me with srk tool!
im downloading now b560 via my phone official OTA! wuhu
EGOiST1991 said:
quick update worked for me with srk tool!
im downloading now b560 via my phone official OTA! wuhu
Click to expand...
Click to collapse
I hate you lol [emoji8] I'm going to try one last time otherwise I'm gonna try the custom rom based B386 Twisted Mate 8
Skickat från min NEXT via Tapatalk
maybe i can help you via teamviewer bro?
EGOiST1991 said:
maybe i can help you via teamviewer bro?
Click to expand...
Click to collapse
No I give up! I love this phone but damn it is complicated to flash roms. All other phones are simple.
Today I tried again, this time by manually testing some steps which I don't know if they are correct since no one seems to be able to answer me. Any way which ever twrp I flash that isn't the one I'm using for flashing B320 won't boot or won't wipe data.
First Attempt:
1. Change build.prop (C432)
2. Change oeminfo file (C432)
3. Change custom.bin (C432)
4. Flash insecure_boot_b560.img by @franzyroy
5. Flash twrp-3.0.3_EMUI5.0.img
6. Boot loop booting to TWRP so FAILED
Second Attempt:
1. Flash decrypted insecure_boot_B320.img
2. Flash TWRP_3.0.2-0_BLACK_BLUE_EMUI4.1.img
3. Wipe Data
4. Factory Reset
5. Flash insecure_boot_b560.img
6. Flash twrp-3.0.2-0-next-modaco-rc3-emui41.img as suggested by @franzyroy
6. Boot loop booting to TWRP so FAIL AGAIN.
Third Attempt:
1. Flash decrypted insecure_boot_b560.img
2. Flash TWRP_3.0.2-0_BLACK_BLUE_EMUI4.1.img
3. Try flashing supersu_v2.79_sr2.zip get error about mounting memory
4. Try flashing
update_full_hw_eu.zip get error 7
Fourth Attempt:
1. Flash decrypted insecure_boot_B320.img
2. Flash twrp-3.0.2-0-next.img
3. Successfully booted to TWRP (woho! Maybe just maybe...)
4. Wipe Data failed, can't mount memory *cry*
Fifth Attempt, let's go back:
1. Flash insecure_boot_b180.img
2. Flash TWRP-3.0.2-BLACK-BLUE_EMUI4.0.img
3. Boot loop booting into recovery so FAILED
F*ck it, went back to B320!
I really don't know what I'm doing any more lol. I guess the last thing could do is go completely stock again (unroot and lock bootloader) by dload(?), rebrand from AL10 to L29C432, update via OTA to nougat and then unlock bootloader and root again. I just feel it shouldn't be necessary and secondly I don't know how to go completely stock again [emoji13]
Leo_83 said:
No I give up! I love this phone but damn it is complicated to flash roms. All other phones are simple.
Today I tried again, this time by manually testing some steps which I don't know if they are correct since no one seems to be able to answer me. Any way which ever twrp I flash that isn't the one I'm using for flashing B320 won't boot or won't wipe data.
First Attempt:
1. Change build.prop (C432)
2. Change oeminfo file (C432)
3. Change custom.bin (C432)
4. Flash insecure_boot_b560.img by @franzyroy
5. Flash twrp-3.0.3_EMUI5.0.img
6. Boot loop booting to TWRP so FAILED
Second Attempt:
1. Flash decrypted insecure_boot_B320.img
2. Flash TWRP_3.0.2-0_BLACK_BLUE_EMUI4.1.img
3. Wipe Data
4. Factory Reset
5. Flash insecure_boot_b560.img
6. Flash twrp-3.0.2-0-next-modaco-rc3-emui41.img as suggested by @franzyroy
6. Boot loop booting to TWRP so FAIL AGAIN.
Third Attempt:
1. Flash decrypted insecure_boot_b560.img
2. Flash TWRP_3.0.2-0_BLACK_BLUE_EMUI4.1.img
3. Try flashing supersu_v2.79_sr2.zip get error about mounting memory
4. Try flashing
update_full_hw_eu.zip get error 7
Fourth Attempt:
1. Flash decrypted insecure_boot_B320.img
2. Flash twrp-3.0.2-0-next.img
3. Successfully booted to TWRP (woho! Maybe just maybe...)
4. Wipe Data failed, can't mount memory *cry*
Fifth Attempt, let's go back:
1. Flash insecure_boot_b180.img
2. Flash TWRP-3.0.2-BLACK-BLUE_EMUI4.0.img
3. Boot loop booting into recovery so FAILED
F*ck it, went back to B320!
I really don't know what I'm doing any more lol. I guess the last thing could do is go completely stock again (unroot and lock bootloader) by dload(?), rebrand from AL10 to L29C432, update via OTA to nougat and then unlock bootloader and root again. I just feel it shouldn't be necessary and secondly I don't know how to go completely stock again [emoji13]
Click to expand...
Click to collapse
Okay. I will try to guide you. Let's do it one by one. Bare with me. So are you in C432B320 right now? Are you able to load into the system?
Sent from my HUAWEI NXT-L29 using XDA Labs
Leo_83 said:
No I give up! I love this phone but damn it is complicated to flash roms. All other phones are simple.
Today I tried again, this time by manually testing some steps which I don't know if they are correct since no one seems to be able to answer me. Any way which ever twrp I flash that isn't the one I'm using for flashing B320 won't boot or won't wipe data.
First Attempt:
1. Change build.prop (C432)
2. Change oeminfo file (C432)
3. Change custom.bin (C432)
4. Flash insecure_boot_b560.img by @franzyroy
5. Flash twrp-3.0.3_EMUI5.0.img
6. Boot loop booting to TWRP so FAILED
Second Attempt:
1. Flash decrypted insecure_boot_B320.img
2. Flash TWRP_3.0.2-0_BLACK_BLUE_EMUI4.1.img
3. Wipe Data
4. Factory Reset
5. Flash insecure_boot_b560.img
6. Flash twrp-3.0.2-0-next-modaco-rc3-emui41.img as suggested by @franzyroy
6. Boot loop booting to TWRP so FAIL AGAIN.
Third Attempt:
1. Flash decrypted insecure_boot_b560.img
2. Flash TWRP_3.0.2-0_BLACK_BLUE_EMUI4.1.img
3. Try flashing supersu_v2.79_sr2.zip get error about mounting memory
4. Try flashing
update_full_hw_eu.zip get error 7
Fourth Attempt:
1. Flash decrypted insecure_boot_B320.img
2. Flash twrp-3.0.2-0-next.img
3. Successfully booted to TWRP (woho! Maybe just maybe...)
4. Wipe Data failed, can't mount memory *cry*
Fifth Attempt, let's go back:
1. Flash insecure_boot_b180.img
2. Flash TWRP-3.0.2-BLACK-BLUE_EMUI4.0.img
3. Boot loop booting into recovery so FAILED
F*ck it, went back to B320!
I really don't know what I'm doing any more lol. I guess the last thing could do is go completely stock again (unroot and lock bootloader) by dload(?), rebrand from AL10 to L29C432, update via OTA to nougat and then unlock bootloader and root again. I just feel it shouldn't be necessary and secondly I don't know how to go completely stock again [emoji13]
Click to expand...
Click to collapse
i made it like this:
SRK TOOL C432 cust
then install via TWRP c432b192 (just take the zip and install it with twrp 2.8.)
then let the update magic begin in the c432b192 rom with unlooked bootloader -worked good
maybe that helps you
oh btw now im using the frd-twrp and i CANT backup my rom... any solution for that?

I messed up with Huawei Mate 9. Please Help.

Guys i have a really really big problem with mate 9 (MHA-L29). I broke both twrp and system same time (please don't ask why.)
Now, my phone don't open, just fastboot&rescue mode, useless huawei recovery (which can't format data neither install stock rom). Besides, i can't install stock rom because i tried once, and i downloaded wrong system file, and i can't format the phone now. Because of that, stock rom that i download sd card not working too. Because there is a dload file in phone.
worst of all, i can't install twrp again, because my fastboot screen tell me that: "Phone Unloced" (with red) "FRP Lock" (with green). When i try to install twrp, adb says "Failed, remote command not allowed"
Now, if can install the twrp, all my problems will be solve. There is 1 custom rom (RomAur) and 1 system backup.
How can i install twrp with this situation?
Please someone help me i spend 2 days and still nothing! How can i open this phone? Stock rom, with/without root, custom rom whatever, just tell me how can i open this phone
up
You get that command when trying to flash the wrong recovery partition, was your room nougat or Oreo based?? If nougat it's fastboot flash recovery recovery.img and Oreo fastboot flash recovery_ramdisk recovery.img I think you are trying to flash the wrong partition
shae23 said:
You get that command when trying to flash the wrong recovery partition, was your room nougat or Oreo based?? If nougat it's fastboot flash recovery recovery.img and Oreo fastboot flash recovery_ramdisk recovery.img I think you are trying to flash the wrong partition
Click to expand...
Click to collapse
No, my twrp is not wrong, i installed before, and i used long time, till broken. I installed wrong twrp recovery over correct recovery (i was trying to chance recovery because project treble). Thats why my twrp broken. Now i try to correct one, but adb says "not allowed". My custom rom nougat based.
cannurkars said:
No, my twrp is not wrong, i installed before, and i used long time, till broken. I installed wrong twrp recovery over correct recovery (i was trying to chance recovery because project treble). Thats why my twrp broken. Now i try to correct one, but adb says "not allowed". My custom rom nougat based.
Click to expand...
Click to collapse
With FRP lock you'll have to use DC-Phoenix.
But it costs €19 (For 3 days usage).
Simply put you can bypass FRP with it by force closing DC-Phoenix when it has activated the backdoor, after this you can flash anything from fastboot (until you reboot).
So you could use it to flash back TWRP.
Or you can use it to install stock firmware
ante0 said:
With FRP lock you'll have to use DC-Phoenix.
But it costs €19 (For 3 days usage).
Simply put you can bypass FRP with it by force closing DC-Phoenix when it has activated the backdoor, after this you can flash anything from fastboot (until you reboot).
So you could use it to flash back TWRP.
Or you can use it to install stock firmware
Click to expand...
Click to collapse
I will try it. Thank you very much.
cannurkars said:
Guys i have a really really big problem with mate 9 (MHA-L29). I broke both twrp and system same time (please don't ask why.)
Now, my phone don't open, just fastboot&rescue mode, useless huawei recovery (which can't format data neither install stock rom). Besides, i can't install stock rom because i tried once, and i downloaded wrong system file, and i can't format the phone now. Because of that, stock rom that i download sd card not working too. Because there is a dload file in phone.
worst of all, i can't install twrp again, because my fastboot screen tell me that: "Phone Unloced" (with red) "FRP Lock" (with green). When i try to install twrp, adb says "Failed, remote command not allowed"
Now, if can install the twrp, all my problems will be solve. There is 1 custom rom (RomAur) and 1 system backup.
How can i install twrp with this situation?
Click to expand...
Click to collapse
During startup the menu there is a option to go in Huawei e-recovery, when you are at the start up menu hold volume up for about 5 second.
ConnerZhao929 said:
During startup the menu there is a option to go in Huawei e-recovery, when you are at the start up menu hold volume up for about 5 second.
Click to expand...
Click to collapse
No it wasn't work for me. But thank for your attention. I'm glad to find a good person to help me and my problem solved about 1-2 hour ago.
Special Request
Hey ante . Is it possible to help me ? I rooted my phone 2 days back and messed it up while downloading a framework app which ended me up in a bootloop. I have been reading and following your posts of you helping others. I don't really get the steps what I should follow.
My phone is unlocked. FRP shows Unlock.
Rooted on oreo and I tried e-recovery and fastboot steps you mentioned in other threads using kernel and ramdisk etc. ( After this I have lost access to TWRP and I am simply getting EMUI Screen with options for Factory Data Reset and Wipe Cache Partition. I don't know where it is going to lead me next :-/.
Also downloaded Huawei Extractor and tried to extracted specific files but the firmware file I have doesn't have CUST.img file.
Also the site link you mentioned for download firmware is in some other language and I am unable to search for my firmware.
I also tried the placing update file in the dload on my sd card but fails at 5%. The file was correct and I am sure I did'n download the wrong firmware.
Currently it shows this on the fastboot screen.
Andorid reboot reason
: AP_S_ABNORMAL 32
NA
Just don't know what I should be doing ? PLEASE HELP BRO?
ante0 said:
With FRP lock you'll have to use DC-Phoenix.
But it costs €19 (For 3 days usage).
Simply put you can bypass FRP with it by force closing DC-Phoenix when it has activated the backdoor, after this you can flash anything from fastboot (until you reboot).
So you could use it to flash back TWRP.
Or you can use it to install stock firmware
Click to expand...
Click to collapse
AniMaL92 said:
Hey ante . Is it possible to help me ? I rooted my phone 2 days back and messed it up while downloading a framework app which ended me up in a bootloop. I have been reading and following your posts of you helping others. I don't really get the steps what I should follow.
My phone is unlocked. FRP shows Unlock.
Rooted on oreo and I tried e-recovery and fastboot steps you mentioned in other threads using kernel and ramdisk etc. ( After this I have lost access to TWRP and I am simply getting EMUI Screen with options for Factory Data Reset and Wipe Cache Partition. I don't know where it is going to lead me next :-/.
Also downloaded Huawei Extractor and tried to extracted specific files but the firmware file I have doesn't have CUST.img file.
Also the site link you mentioned for download firmware is in some other language and I am unable to search for my firmware.
I also tried the placing update file in the dload on my sd card but fails at 5%. The file was correct and I am sure I did'n download the wrong firmware.
Currently it shows this on the fastboot screen.
Andorid reboot reason
: AP_S_ABNORMAL 32
NA
Just don't know what I should be doing ? PLEASE HELP BRO?
Click to expand...
Click to collapse
What's your firmware now?
You can get that info in Fastboot using
Code:
fastboot oem get-product-model
fastboot oem get-build-number
Since your recovery and fastboot still functions you probably will only need to use HWOTA to get back to stock.
It can be found here: https://forum.xda-developers.com/mate-9/how-to/guide-mate-9-flash-oreo-update-package-t3699522
But post your cust/build before proceeding.
Also cust.img is found in UPDATE.APP in the hw data zip.
Problem Solved - Somewhat
Hey ante. Thanks for the promt reply. I got it solved by using CHIMERA tool.
Would like to suggest others also stuck with same issue to use CHIMERA.
Note - It is a paid tool and 100% legit and it can help with all problems related to FRP, Bootloader Lock / Unlock & also flashes back to factory firmware.
However what I am facing now I have flashed another version of firmware which isn't my region and some features of my phone like fingerprint scanner and other things are not working but phone is back to live. So Im glad and looking forward to searching for clean Oreo Firmware for my region to flash using CHIMERA Again.
Also, the sick and stupid part of it. I went to the service center and a person non-technical told me straight that you lost your device and it's of no use now. We cannot fix such issues 99% but I'll still ask my team and let you know after 3 days.
Thank God I didn give them and wasted my time and money.
As soon as I returned, I followed up to things and got it done myself. :good:
Anybody can possibly suggest a official firmware Oreo EMUI for Middle East Region!? If not which one can be flashed instead and where to download from?

Was Bricked - CLT-L04 with EMUI 8.1 - the fixed ended up giving me EMUI 9 CLT-L04

Bricked my phone by doing the following:
Honor View 10 ROMs are compatible with P20 Pro, I installed and used them all. Then the other day they made a mod that force the EMUI 9 update so I ran it. The mod ended rebranding my entire phone to Honor View 10 followed by boot loops like crazy. So then I went into twrp and tried to format thinking it would help. It ended up deleting everything including eRecovery. The only this I had access to was fastboot. Yes I brought this on my self lol. I paid a lot for Funky Huawei but nothing worked. I tried every tool they had.
Fix: (Turns out my phone's structure is now EMUI 9\Android 9)
1- Downloaded my phone image (CLT-L04 - EMUI 9 version), extracted the update.app file from it.
2- Used EMUI extractor app to extracted everything from the update.app file (Lots of image files)
3- Noticed userdata.img wasn't in the extracted files so I downloaded multiple images that are similar models to my phone until I found it.
4- Used fastboot command to flash the userdata.img, followed by eRecovery.img, followed by the rest I pulled from that update.app file.
after about three reboots I was back into my phone except I now have EMUI 9.
My case is similar. I downgraded from B195 to rollback B161. Now I am literally doomed. No erecovery, no huawei logo, just plain black fastboot screen. My bootlodaer is unlocked and I'm unable to relock it. Huawei is denying service, is there any way to revive my black dead phone???
twrp.img gets flashed succesfully but doesnt boot into it.
QuazIqbal said:
My case is similar. I downgraded from B195 to rollback B161. Now I am literally doomed. No erecovery, no huawei logo, just plain black fastboot screen. My bootlodaer is unlocked and I'm unable to relock it. Huawei is denying service, is there any way to revive my black dead phone???
twrp.img gets flashed succesfully but doesnt boot into it.
Click to expand...
Click to collapse
Can you try this.
Files that you will be downloading are,
update.zip
update_full_CLT-L29_hw_eu.zip (Or whatever model of phone you have)
Get them here by searching for your model and click filelist
Prep:
a. Rename update_full_CLT-L29_hw_eu.zip to update_all_hw.zip
b. Download this Flash tool and extract in to a folder in your PC
c. Copy update.zip and update_all_hw.zip to ZIPS-HERE folder (you can find this folder where you have extracted Flash tool
How to flash Firmware
1. Double click to run the file cmd-here.exe. It opens command prompt in the same folder where you are.
2. Once command prompt opens, type FLASH.bat and follow steps carefully. Once flashing is complete, it will boot normally.
- if it fails to detect the files try removing the .zip from the names of the files in the ZIPS-HERE folder
This should bring back eRecovery, recovery, system, whatever. Even at the end if it fails the structure should be rebuilt enough for you to recover via HiSuite application. This worked for me.
Vedrick said:
2. Once command prompt opens, type FLASH.bat and follow steps carefully. Once flashing is complete, it will boot normally.
- if it fails to detect the files try removing the .zip from the names of the files in the ZIPS-HERE folder
This should bring back eRecovery, recovery, system, whatever. Even at the end if it fails the structure should be rebuilt enough for you to recover via HiSuite application. This worked for me.
Click to expand...
Click to collapse
Thanks for offering your help. Mine case looks different....
I have tried this, after flashing twrp in the fastboot the device fails to boot into twrp recovery, it's all black, only fastboot is accessible in the black screen.
I experienced the same problem. Bricked my P20 Pro and can only access fastboot (no access to erecovery). Could you tell me which image that you used to flash userdata.img and erecovery.img? I tried several images but none of them contains userdata.img and erecovery.img.
Thanks.
Edit:
Also, aside from userdata.img and erecovery.img, what files did you flash to the phone?
przival said:
I experienced the same problem. Bricked my P20 Pro and can only access fastboot (no access to erecovery). Could you tell me which image that you used to flash userdata.img and erecovery.img? I tried several images but none of them contains userdata.img and erecovery.img.
Thanks.
Edit:
Also, aside from userdata.img and erecovery.img, what files did you flash to the phone?
Click to expand...
Click to collapse
Update : Good news finally. My device is now unbricked by flashing downloaded OTA from Firmware Finder (Oreo B161 simple non-rollback version) using DC phoenix via testpoint mode. P.S. Flashing B195 pie didn't worked earlier.
QuazIqbal said:
Update : Good news finally. My device is now unbricked by flashing downloaded OTA from Firmware Finder (Oreo B161 simple non-rollback version) using DC phoenix via testpoint mode. P.S. Flashing B195 pie didn't worked earlier.
Click to expand...
Click to collapse
Nice one!!
Can I ask that you help me out as I'm in the same situation? I'm scared about removing back cover and loading credit to CD and still not being able to fix it. A step-by-step idiots guide would be greatly appreciated.
How was it removing the back?
Did you need to buy a new back glass case?
Were are the test points and how do you trigger them?
What FW did you use exactly?
Sorry for the questions but I've yet to find anyone who's provided help to sort it.
QuazIqbal said:
Update : Good news finally. My device is now unbricked by flashing downloaded OTA from Firmware Finder (Oreo B161 simple non-rollback version) using DC phoenix via testpoint mode. P.S. Flashing B195 pie didn't worked earlier.
Click to expand...
Click to collapse
can i ask you are your phone relock after update or not ??if yes are you unlock your phone again with same number and in the end can you give us full guide what you done to unbrick your phone
Deano1889 said:
Nice one!!
Can I ask that you help me out as I'm in the same situation? I'm scared about removing back cover and loading credit to CD and still not being able to fix it. A step-by-step idiots guide would be greatly appreciated.
How was it removing the back?
Did you need to buy a new back glass case?
Were are the test points and how do you trigger them?
What FW did you use exactly?
Sorry for the questions but I've yet to find anyone who's provided help to sort it.
Click to expand...
Click to collapse
I will do my best to answer tomorrow, God willing. Please wait
---------- Post added at 09:04 PM ---------- Previous post was at 08:55 PM ----------
black_1986 said:
can i ask you are your phone relock after update or not ??if yes are you unlock your phone again with same number and in the end can you give us full guide what you done to unbrick your phone
Click to expand...
Click to collapse
After this process your bl will be in 'locked' state. If you had my kind of downgrade brick the imeis and serial will number will not be disturbed. You may simply use your old bl code to unlock. However I messed up my oeminfo but due to my own stupidity, I'm looking to restore my imei and will try to unlock again.
If possible, could you share the files you use?

Categories

Resources