MHA-AL00C00B125 - https://mega.nz/#!1853WCAQ!uuCgvn4a7JXHSmEmlBzdMsOOC9vQFJ3WSuMUQI9NDVM
MHA-AL00C00B115 - https://mega.nz/#!88RmjJjA!gGmuc0gL-_sPHOQ0VAXZgTJ3lXmlRRmBqXIYNEyw9XY
MHA-L29C185B186 - http://androidhost.ru/KR
MHA-L29C636B181 - https://forum.xda-developers.com/mate-9/help/bricked-mate-9-help-t3664727/post73988779
MHA-L29C636B122 -
https://drive.google.com/file/d/0BxUuiDq_FRA_cHlHc3BTWEFOUlU/view?usp=sharing
LON-AL00C00B229 - http://androidhost.ru/KZ
LON-L29C432B225 - http://androidhost.ru/L0
LON-L29C185B225 - http://androidhost.ru/L3
LON-L29C636B225 - http://androidhost.ru/L2
LON-L29C721B186 - http://androidhost.ru/L1
Please, make mirror or copy your region ROM to own archive to avoid situation if main source is not available or deleted.
hw to install
Waleedaligomaa said:
hw to install
Click to expand...
Click to collapse
You extract zip, put contents in external_sd/dload/
then boot using vol up + vol down + power. It's useful if you manage to brick or want to rebrand.
Or want to rollback from Oreo to Nougat.
---------- Post added at 10:54 PM ---------- Previous post was at 10:23 PM ----------
Phew. Thanks to these dload images...
I was going to update to Oreo again to try some stuff to get Magisk running.
I downloaded Oreo Beta from pro-teammt.ru using Linux. Little did I know the update.zip was corrupt (Later I tried downloading multiple times using both browser and wget, different MD5 each time so something is up with my computer).
So I updated like usual using HWOTA. It started installing, I don't know how long it got to, but I was presented with a screen that said PLEASE REDOWNLOAD PACKAGE USING RECOVERY.
So I rebooted. ERROR MODE. Now I'm scared... I googled "Mate 10 release date" just in case, lol.
I rebooted to fastboot mode, thankfully it still worked. I had to unlock bootloader again. Now I tried flashing stock B197 recovery, FAILED: (remote: partition length get error).
I tried the same with boot. Same result.
Then I figured out it probably had the new Oreo partition names for boot and recovery, and thankfully those flashed fine.
So flashed TWRP for Oreo, flashed oeminfo for AL00C00 using dd. Flashed ERECOVERY partitions using dd as well, just in case.
Back to bootloader to unlock again after flashing oeminfo, then flashed back stock recovery_ramdisk.
Then placed dload folder on external sd and booted up using vol up+down+power
Now my Mate 9 is booting up again!
Where L09 ..??
Sent from my MHA-L09 using XDA-Developers Legacy app
ante0 said:
Now my Mate 9 is booting up again!
Click to expand...
Click to collapse
That was some journey to the dark side. Welcome back.
So with this Builds I can rollback from Oreo to naught? But my phone isn't listed... European MHA-L29C432
albertobom said:
So with this Builds I can rollback from Oreo to naught? But my phone isn't listed... European MHA-L29C432
Click to expand...
Click to collapse
You need to rebrand to AL00C00 to rollback.
In other words, flash AL00 oeminfo.bin, use AL00 dload. Then rebrand back to L29C432 using Hwota. It's currently the only free way of rolling back to Nougat.
ante0 said:
You need to rebrand to AL00C00 to rollback.
In other words, flash AL00 oeminfo.bin, use AL00 dload.
Click to expand...
Click to collapse
I've change some things in system. It's there a problem to use dload if I have change system?
Also I've to have dload on external sdcard right?
So the steps are:
Flash oeminfo.bin info
Then use erecovery and dload right
albertobom said:
I've change some things in system. It's there a problem to use dload if I have change system?
Also I've to have dload on external sdcard right?
So the steps are:
Flash oeminfo.bin info
Then use erecovery and dload right
Click to expand...
Click to collapse
It doesn't check system or any other partition so it will install.
Yes, ext sd:/dload/files from AL00C00(B115 is what I used) dload rar.
Extract dload rar, place all files on external SD in dload folder.
Flash AL00C00 oeminfo.bin. use vol up+vol down+power to boot, make sure USB is unplugged else it will stuck on 5%.
After you will have to rebrand back to L29C432 using HWOTA.
ante0 said:
It doesn't check system or any other partition so it will install.
Yes, ext sd:/dload/files from AL00C00(B115 is what I used) dload rar.
Extract dload rar, place all files on external SD in dload folder.
Flash AL00C00 oeminfo.bin. use vol up+vol down+power to boot, make sure USB is unplugged else it will stuck on 5%.
After you will have to rebrand back to L29C432 using HWOTA.
Click to expand...
Click to collapse
Thanks my dear friend I'm at beta oreo and it's running amazing but I think I'll have to go back to N so I can make new updates since Oreo doesn't have patched recovery yet.
---------- Post added at 10:41 PM ---------- Previous post was at 10:05 PM ----------
@ante0 where or how do I flash oeminfo.bin? Via twrp? With a flashable zip?
albertobom said:
So with this Builds I can rollback from Oreo to naught? But my phone isn't listed... European MHA-L29C432
Click to expand...
Click to collapse
Why to rollback?
Enviado desde mi MHA-L29 mediante Tapatalk
jaimeguate said:
Why to rollback?
Enviado desde mi MHA-L29 mediante Tapatalk
Click to expand...
Click to collapse
Nothing special really just want to know if I can go back if I have to. ?
albertobom said:
Thanks my dear friend I'm at beta oreo and it's running amazing but I think I'll have to go back to N so I can make new updates since Oreo doesn't have patched recovery yet.
---------- Post added at 10:41 PM ---------- Previous post was at 10:05 PM ----------
@ante0 where or how do I flash oeminfo.bin? Via twrp? With a flashable zip?
Click to expand...
Click to collapse
Oeminfo in this thread: https://forum.xda-developers.com/mate-9/how-to/guide-rebrand-chinese-al00-mate9-to-t3554656 can be restored as a backup. That's probably the easiest way.
Alternative, copy and flash using dd.
cp /external_sd/MHA-AL00C00. bin /tmp/oeminfo.bin
dd if=/tmp/oeminfo.bin of=/dev/block/sdd5
5[Strogino said:
;74268268]MHA-AL00C00B125 - https://mega.nz/#!1853WCAQ!uuCgvn4a7JXHSmEmlBzdMsOOC9vQFJ3WSuMUQI9NDVM
MHA-AL00C00B115 - https://mega.nz/#!88RmjJjA!gGmuc0gL-_sPHOQ0VAXZgTJ3lXmlRRmBqXIYNEyw9XY
MHA-L29C185B186 - http://androidhost.ru/KR
MHA-L29C636B181 - https://forum.xda-developers.com/mate-9/help/bricked-mate-9-help-t3664727/post73988779
MHA-L29C636B122 -
https://drive.google.com/file/d/0BxUuiDq_FRA_cHlHc3BTWEFOUlU/view?usp=sharing
LON-AL00C00B229 - http://androidhost.ru/KZ
LON-L29C432B225 - http://androidhost.ru/L0
LON-L29C185B225 - http://androidhost.ru/L3
LON-L29C636B225 - http://androidhost.ru/L2
LON-L29C721B186 - http://androidhost.ru/L1
Please, make mirror or copy your region ROM to own archive to avoid situation if main source is not available or deleted.
Click to expand...
Click to collapse
Hi bro can you send me oeminfo of chinese version of p8 lite 2017/honor 8 lite????
I want to rebrand my phone
ante0 said:
You extract zip, put contents in external_sd/dload/
then boot using vol up + vol down + power. It's useful if you manage to brick or want to rebrand.
Or want to rollback from Oreo to Nougat.
---------- Post added at 10:54 PM ---------- Previous post was at 10:23 PM ----------
Phew. Thanks to these dload images...
I was going to update to Oreo again to try some stuff to get Magisk running.
I downloaded Oreo Beta from pro-teammt.ru using Linux. Little did I know the update.zip was corrupt (Later I tried downloading multiple times using both browser and wget, different MD5 each time so something is up with my computer).
So I updated like usual using HWOTA. It started installing, I don't know how long it got to, but I was presented with a screen that said PLEASE REDOWNLOAD PACKAGE USING RECOVERY.
So I rebooted. ERROR MODE. Now I'm scared... I googled "Mate 10 release date" just in case, lol.
I rebooted to fastboot mode, thankfully it still worked. I had to unlock bootloader again. Now I tried flashing stock B197 recovery, FAILED: (remote: partition length get error).
I tried the same with boot. Same result.
Then I figured out it probably had the new Oreo partition names for boot and recovery, and thankfully those flashed fine.
So flashed TWRP for Oreo, flashed oeminfo for AL00C00 using dd. Flashed ERECOVERY partitions using dd as well, just in case.
Back to bootloader to unlock again after flashing oeminfo, then flashed back stock recovery_ramdisk.
Then placed dload folder on external sd and booted up using vol up+down+power
Now my Mate 9 is booting up again!
Click to expand...
Click to collapse
Hi, I'm having a similiar issue. I can't flash any recovery using fastboot (FAILED: (remote: partition length get error). , I'm on emui 5.0.1 android 7.0 (phone works perfectly fine), is possible to flash TWRP recovery using DD? if so, how? it's my first time doing this with a huawei phone and I want to try oreo beta
UPDATE:
Bricked it, can't flash recovery, only fastboot, can't force update neither, any idea?
seniga1 said:
Hi, I'm having a similiar issue. I can't flash any recovery using fastboot (FAILED: (remote: partition length get error). , I'm on emui 5.0.1 android 7.0 (phone works perfectly fine), is possible to flash TWRP recovery using DD? if so, how? it's my first time doing this with a huawei phone and I want to try oreo beta
UPDATE:
Bricked it, can't flash recovery, only fastboot, can't force update neither, any idea?
Click to expand...
Click to collapse
recovery is named recovery_ramdisk on Oreo.
So fastboot flash recovery_ramdisk twrp.img
Make sure you flash twrp from the oreo thread.
If you're on Nougat recovery partition is named recovery, so:
Fastboot flash recovery twrp.img
Twrp is in the regular twrp thread.
You can only use dd in twrp, not using fastboot.
If you tried updating to Oreo I would try both recovery and recovery_ramdisk.
ante0 said:
recovery is named recovery_ramdisk on Oreo.
So fastboot flash recovery_ramdisk twrp.img
Make sure you flash twrp from the oreo thread.
If you're on Nougat recovery partition is named recovery, so:
Fastboot flash recovery twrp.img
Twrp is in the regular twrp thread.
You can only use dd in twrp, not using fastboot.
If you tried updating to Oreo I would try both recovery and recovery_ramdisk.
Click to expand...
Click to collapse
flash recovery_ramdisk twrp.img
That did the trick, really appreciated, you'r my new hero :highfive:
Oreo updates
albertobom said:
Thanks my dear friend I'm at beta oreo and it's running amazing but I think I'll have to go back to N so I can make new updates since Oreo doesn't have patched recovery yet.
---------- Post added at 10:41 PM ---------- Previous post was at 10:05 PM ----------
@ante0 where or how do I flash oeminfo.bin? Via twrp? With a flashable zip?
Click to expand...
Click to collapse
You should be able to get updates if you are on the Oreo beta, update checks for stock recovery and won't update if you are on a custom or patched recovery, system update would just see you as updating from beta to release version, beta and release versions are both official ROMs so I don't think you would have any issues with updating as long as the device brand is the same.
plz help sir
ante0 said:
recovery is named recovery_ramdisk on Oreo.
So fastboot flash recovery_ramdisk twrp.img
Make sure you flash twrp from the oreo thread.
If you're on Nougat recovery partition is named recovery, so:
Fastboot flash recovery twrp.img
Twrp is in the regular twrp thread.
You can only use dd in twrp, not using fastboot.
If you tried updating to Oreo I would try both recovery and recovery_ramdisk.
Click to expand...
Click to collapse
I did what you have described above ... flashed oreo twrp successfully but when tried to boot into TWRP it never boots into TWRP ( only a screen appears having three options : 1. Reboot system now 2. Wipe data/factory reset 3. Wipe cache partition.
I'm neither able to perform wipe data/factory reset nor able to wipe cache( it goes to 40% and gives error)
Struck here for more than 15 days...any help will be highly appreciated.
jaldi said:
I did what you have described above ... flashed oreo twrp successfully but when tried to boot into TWRP it never boots into TWRP ( only a screen appears having three options : 1. Reboot system now 2. Wipe data/factory reset 3. Wipe cache partition.
I'm neither able to perform wipe data/factory reset nor able to wipe cache( it goes to 40% and gives error)
Struck here for more than 15 days...any help will be highly appreciated.
Click to expand...
Click to collapse
You do have Oreo, right?
TWRP should fail to install if you don't have Oreo (unless you're flashing it to recovery and not recovery_ramdisk).
But it sounds to me like it's not installing at all, since you're ending up in stock recovery.
Make sure you use "fastboot flash" , not "fastboot boot"
Related
Anyone know why fingerprint sensor isn't working after i flash recovery of b145?
Same
I bricked my Mate S so extracted the img files from the stock B145 Europe full file, and flashed:
boot
recovery
system
cache
userdata
I have the same problem, fingerprint sensor doent work, there are no options in settings for the fingerprint sensor.
Also im unable to set any security, and also i cant uninstall any apps as the phone reboots everytime i do..
I did root the phone to see what was going on and the keystore is missing along with a whole bunch of errors.
I know it doesnt help, sorry
Arola1982 said:
I bricked my Mate S so extracted the img files from the stock B145 Europe full file, and flashed:
boot
recovery
system
cache
userdata
I have the same problem, fingerprint sensor doent work, there are no options in settings for the fingerprint sensor.
Also im unable to set any security, and also i cant uninstall any apps as the phone reboots everytime i do..
I did root the phone to see what was going on and the keystore is missing along with a whole bunch of errors.
I know it doesnt help, sorry
Click to expand...
Click to collapse
If you are both talking about flashing those files whilst on B303 or B321 it's just not possible at the moment..you'll need to restore a TWRP backup u made whilst on MM Beta to get security options back.
You just can't get back to 5.1.1 from MM Beta at the moment
Okay so ive tried to manually update. Won't work. Should i try to flash the images of b321 mabye?
Basicly stupid me doesn't have backup :/
Sent from my HUAWEI CRR-L09 using XDA-Developers mobile app
The same happened to me - semi-bricked my phone whilst I was on b321; wanted to root it and it didn't work. Now I'm back on b145 because I have no TWRP backup of b321 (stupid me). So, could anyone make a (clean) TWRP backup of CRR-L09C432B321? That would be awesome!
Thanks in advance - fbs
ask to dcunlocker in the support chat...huaweiphonewriterv4.exe to flash recovery update in fastboot mode and then reflash full firmware with same tool..i have save my device.
frisko76 said:
ask to dcunlocker in the support chat...huaweiphonewriterv4.exe to flash recovery update in fastboot mode and then reflash full firmware with same tool..i have save my device.
Click to expand...
Click to collapse
Well, my phone is not bricked. It's just a really dirty version of b145 (security options and automatic screen brightness and stuff like that is not working). But thanks, I will try it
edit: where can I find the support chat? Here on XDA? Sorry for this dumb question :S
edit: where can I find the support chat? Here on XDA? Sorry for this dumb question :S[/QUOTE]
On web site of dcunlocker in the tab contact live chat..describe your problem in the tecnichal support..
---------- Post added at 03:40 PM ---------- Previous post was at 03:34 PM ----------
You not have stock recovery..you have twrp and not is possible flash original firmware....is possible to flash boot.img and recovery.img on the fastboot mode,but if you have frp lock this is not possible...only with tool of dcunlocker is possible to install recovery and boot original..after your install full firmware with same tool..
On web site of dcunlocker in the tab contact live chat..describe your problem in the tecnichal support..
Click to expand...
Click to collapse
Hi Frisko76
I have try to contact support DCunlocker chat , but there is nobody to help me today.
Can you send me a link for download huaweiphonewriterv4.exe?
frisko76 said:
edit: where can I find the support chat? Here on XDA? Sorry for this dumb question :S
On web site of dcunlocker in the tab contact live chat..describe your problem in the tecnichal support..
---------- Post added at 03:40 PM ---------- Previous post was at 03:34 PM ----------
You not have stock recovery..you have twrp and not is possible flash original firmware....is possible to flash boot.img and recovery.img on the fastboot mode,but if you have frp lock this is not possible...only with tool of dcunlocker is possible to install recovery and boot original..after your install full firmware with same tool..
Click to expand...
Click to collapse
Thanks for the input, but I guess this is not my problem. I'm able to flash via fastboot and my FRP is unlocked.
I tried flashing the files from all versions - b145, b303 and b321 (eg. system.img, recovery.img, cush.img and such), but I couldn't get b303 or b321 working again. I end everytime in a boot loop.
Maybe I did something wrong, but that's the reason I restored an old b145 twrp backup.
fbsfelony said:
Thanks for the input, but I guess this is not my problem. I'm able to flash via fastboot and my FRP is unlocked.
I tried flashing the files from all versions - b145, b303 and b321 (eg. system.img, recovery.img, cush.img and such), but I couldn't get b303 or b321 working again. I end everytime in a boot loop.
Maybe I did something wrong, but that's the reason I restored an old b145 twrp backup.
Click to expand...
Click to collapse
Have you tried factory reset then putting a full version of B145 in the /dload/ folder and doing a update through the settings..update..local update
Yes..after you have flashed the file via fastboot write command fastboot reboot..put the full firmware in the folder of dload of internal sd card....press with usb connect of your pc volume up + power and enter in huawei erecovery..press shutdown....disconnect usb...press volume +,volume- and power and release only power after huawei logo..you enter in the upgrade firmware...if flashing block at 90℅ for several minute flashing not is correct..and you need this tool huaweiphonewriterv4 with usb connect to pc for flashing full firmware without error...you have need after flashing via fastboot recovery and boot the wipe data factory reset...try before with wipe data e factory reset in the recovery ..enter in this mode without usb press volume up + power..
---------- Post added at 07:29 AM ---------- Previous post was at 07:23 AM ----------
Check control in device manager of pc..in fastboot mode you have displayed in the samsung android interface driver driver name ADB BOOTLOADER INTERFACE..IS CORRECT DRIVER..in recovery you have driver ANDROID ADB INTERFACE...check the driver correct..is very important for this...not is displayed ANDROID SOONER SINGLE ANDROID INTERFACE..not work correct this driver...check you.
brumgav said:
Have you tried factory reset then putting a full version of B145 in the /dload/ folder and doing a update through the settings..update..local update
Click to expand...
Click to collapse
I tried that, yes. But with no luck; through the settings I can't make a factory reset (it fails after a few seconds), same with the stock recovery. I haven't tried it with TWRP yet, maybe this will work.
And also the method with the dload folder fails - no matter if I do it via the phones settings or when I boot directly into the setup with volume-down and volume-up (where it stops at 90%).
Maybe a full version of b303 or b321 would work, but for now we don't have that yet.
frisko76 said:
Yes..after you have flashed the file via fastboot write command fastboot reboot..put the full firmware in the folder of dload of internal sd card....press with usb connect of your pc volume up + power and enter in huawei erecovery..press shutdown....disconnect usb...press volume +,volume- and power and release only power after huawei logo..you enter in the upgrade firmware...if flashing block at 90℅ for several minute flashing not is correct..and you need this tool huaweiphonewriterv4 with usb connect to pc for flashing full firmware without error...you have need after flashing via fastboot recovery and boot the wipe data factory reset...try before with wipe data e factory reset in the recovery ..enter in this mode without usb press volume up + power..
---------- Post added at 07:29 AM ---------- Previous post was at 07:23 AM ----------
Check control in device manager of pc..in fastboot mode you have displayed in the samsung android interface driver driver name ADB BOOTLOADER INTERFACE..IS CORRECT DRIVER..in recovery you have driver ANDROID ADB INTERFACE...check the driver correct..is very important for this...not is displayed ANDROID SOONER SINGLE ANDROID INTERFACE..not work correct this driver...check you.
Click to expand...
Click to collapse
I guess that's somehow the case - As mentioned above, I already tried to upgrade the firmware with volume-up and volume-down, but it stops at 90%. But I will try it again in the order you said, thanks!
My drivers are all fine, working with them for a while now with a lot of phones and never had problems using fastboot or adb commands (I'm using the ones of the android-sdk) - but you're right, in fastboot it is called "Android Sooner Single ADB Interface". In stock recovery my phone isn't displayed in the device manager of my computer. When I boot up normally with USB-Debugging enabled it is called "Android Adapter ADB Interface".
Honestly I'm a bit concerned about using the said software "huaweiphonewriterv4" - it doesn't seem very
reliable to me
With tool of dcunlocker i have save my device...android sooner single adb interface is not correct driver in fastboot mode...right key mouse in the pc driver device manager,update driver,manually search and toggle compatible driver..list of driver is down of samsung driver..driver correct is adb bootloader interface version with data driver..most recent..accept message of windows driver is not compatible version..install driver..are his the driver correct!!100℅ work...your problem is twrp ..you not have flash right recovery stock..twrp already installed on your device..you must cancel twrp with recovery stock..
---------- Post added at 09:23 AM ---------- Previous post was at 09:14 AM ----------
If twrp start you not have flashedrecovery stock correct....try to flash boot e recovery in fastboot and userdata of the firmware you have in the device before you in bootloop...with correct driver..and after reboot in recovery stock and wipe data factory reset,reboot and try to install firmware in dload..excuse for my english!!
frisko76 said:
With tool of dcunlocker i have save my device...android sooner single adb interface is not correct driver in fastboot mode...right key mouse in the pc driver device manager,update driver,manually search and toggle compatible driver..list of driver is down of samsung driver..driver correct is adb bootloader interface version with data driver..most recent..accept message of windows driver is not compatible version..install driver..are his the driver correct!!100℅ work...your problem is twrp ..you not have flash right recovery stock..twrp already installed on your device..you must cancel twrp with recovery stock..
---------- Post added at 09:23 AM ---------- Previous post was at 09:14 AM ----------
If twrp start you not have flashedrecovery stock correct....try to flash boot e recovery in fastboot and userdata of the firmware you have in the device before you in bootloop...with correct driver..and after reboot in recovery stock and wipe data factory reset,reboot and try to install firmware in dload..excuse for my english!!
Click to expand...
Click to collapse
Ok, I'll try a driver update, thanks
The thing with the recovery - right now I'm on the b145 recovery, but I've tried the b303 and the b321 recovery as well as the TWRP recovery. I just switched between each versions. But I will try the steps you provided, thank you very much!
It's just that I can't make a proper factory reset - it fails after a few seconds, but my phone is then reset. I will try it again with the files (everything I'm able to flash) of the last working firmware - in my case it was b321 before I ****ed up. Again, thanks
You have to access the update menu without a USB cable connected to update via Update file in dload. If you Reboot into Update Mode with a cable connected, your device will go into USB flashmode und will stop at 90%.
Keep pressing vol up + vol down + Power without a cable connected and Release the power button after the Vibration.
frisko76 said:
Yes..after you have flashed the file via fastboot write command fastboot reboot..put the full firmware in the folder of dload of internal sd card....press with usb connect of your pc volume up + power and enter in huawei erecovery..press shutdown....disconnect usb...press volume +,volume- and power and release only power after huawei logo..you enter in the upgrade firmware...if flashing block at 90℅ for several minute flashing not is correct..and you need this tool huaweiphonewriterv4 with usb connect to pc for flashing full firmware without error...you have need after flashing via fastboot recovery and boot the wipe data factory reset...try before with wipe data e factory reset in the recovery ..enter in this mode without usb press volume up + power..
Click to expand...
Click to collapse
If you do it this way, make sure there is no USB Logo in the circle.
yes..is correct..but if you had a b321 before crash you need to download full 321 and extract boot and recovery of 321 with huaweiexctrator tool and flash it in fast boot mode..then upgrade full firmware in recovery..
I have the same issue, i have mate s with tim brand, i change my brand to no brand, i have installed the firmware b114 (first b110) nex b145, and i try to instal mm beta, but installation fail, i try to flash b145 and fingerprint doesn't work. Next i contacted dc forum with live chat, they help me to return at b114, when finished the finger print It has worked well for 15 min and then gave me problems again.
They told me that They do not yet have a solution for people that have upgrate the mate to MM, and must be wait for the official firmware MM for solve that because the beta of MM is not full version
Guys, I did it
I just found a bigger OTA update which allows you to upgrade directly from b145 to b321.
b145 to b321 OTA
I loaded the recovery.img and boot.img of b145 via fastboot on the phone, after that I just put the downloaded zip on my external sd-card in the dload folder, made the update via settings and et voilà, done!
Just quick tested a few things, but everything seems to work.
Defaultuser88 said:
I have the same issue, i have mate s with tim brand, i change my brand to no brand, i have installed the firmware b114 (first b110) nex b145, and i try to instal mm beta, but installation fail, i try to flash b145 and fingerprint doesn't work. Next i contacted dc forum with live chat, they help me to return at b114, when finished the finger print It has worked well for 15 min and then gave me problems again.
They told me that They do not yet have a solution for people that have upgrate the mate to MM, and must be wait for the official firmware MM for solve that because the beta of MM is not full version
Click to expand...
Click to collapse
Maybe you can try to upgrade your phone with the full version of b145, and after that upgrade from b145 to b321.
Thanks everyone!
did you put the complete zip or only update file?
now i'm in b114 but have same feature like multiwindows of next version, i try to flash the full version of 145, first flash recovery and boot but can't install, the phone give me error :/ can't upgrade from b114 to b145
Hello all
I have a problem with my Huawei P9 (Eva L09). During my dload update my smartphone shutdown without any advice. So update process has been completed therefore device does boot and stucked in Huawei logo and jumped to Huawei erecovery. Recocery mode does works but i cannot re flash a new firmware. Fastboot mode works. I re flash system.img boot.img and so on as a thread in this forum says but nothing to do. Device does not work. Hisuite can restote all in fastboot mode but seems that my device is not compatible. It is last version of hisuite. My bootloader and FRP mode locked. Someone can help me?
Thanks in advance
Update: My phone now just only go to fastboot mode and can not boot up to recovery mode now, always boot to logo screenand stuck, please help! Thanks
Flash rom from dload from sd card. After flash when system not start go back to recovery and wipe data and factory reset. Turn on again. When system not work flash again from dload. Use 3 button to turn on phone
<<<by scaniathe>>>
scaniathe said:
Flash rom from dload from sd card. After flash when system not start go back to recovery and wipe data and factory reset. Turn on again. When system not work flash again from dload. Use 3 button to turn on phone
<<<by scaniathe>>>
Click to expand...
Click to collapse
but when I started flash until 5%, it said firmware failed to install and just gave me the option was"reboot system now" and reboot back to erecovery, so annoying.....:crying:
different firmware??
probably wrong type of firmware...
there are several types of firmware for L09 two in particular I messed around... since I was in your shoe too...
one was B136 and the other was i think B165
try installing another firmware
C432b182 latest from huawei.customer.com
<<<by scaniathe>>>
sk0n3 said:
probably wrong type of firmware...
there are several types of firmware for L09 two in particular I messed around... since I was in your shoe too...
one was B136 and the other was i think B165
try installing another firmware
Click to expand...
Click to collapse
which firmware should I flash for the phone? C432B136?
scaniathe said:
C432b182 latest from huawei.customer.com
<<<by scaniathe>>>
Click to expand...
Click to collapse
I tried, but it was still said "install firmware fail".......
scaniathe said:
C432b182 latest from huawei.customer.com
<<<by scaniathe>>>
Click to expand...
Click to collapse
have you tried installing other firmwares?
one thing you might be able to do is...
1 flash twrp
2 wipe cache, data, system
3 reinstall system recovery
4 dload stock firmware
---------- Post added at 08:08 AM ---------- Previous post was at 08:04 AM ----------
sk0n3 said:
have you tried installing other firmwares?
one thing you might be able to do is...
1 flash twrp
2 wipe cache, data, system
3 reinstall system recovery
4 dload stock firmware
Click to expand...
Click to collapse
http://forum.xda-developers.com/p9/how-to/guide-root-huawei-p9-t3367800
/\ /\ /\ /\ /\ /\ /\ /\
this guy works with one click its pretty cool
Stock recovery install automatically with reinstall firmware from dload. Format your all data from twrp and reinstall again
<<<by scaniathe>>>
scaniathe said:
Stock recovery install automatically with reinstall firmware from dload. Format your all data from twrp and reinstall again
<<<by scaniathe>>>
Click to expand...
Click to collapse
when i did mine i downloaded the ROOT-HUAWEI-P9.zip/extract then used part 1 to install twrp from bootloader
then boot to recovery wipe data cache system
go back to the extracted zip file and use part 3 to reinstall stock recovery
then check to see if you have dload folder with UPDATE.APP in your main directory o your sd card
then turn your phone off hold vol up and down and pwr/ after first vibration release pwr button
---------- Post added at 08:31 AM ---------- Previous post was at 08:30 AM ----------
sk0n3 said:
when i did mine i downloaded the ROOT-HUAWEI-P9.zip/extract then used part 1 to install twrp from bootloader
then boot to recovery wipe data cache system
go back to the extracted zip file and use part 3 to reinstall stock recovery
then check to see if you have dload folder with UPDATE.APP in your main directory o your sd card
then turn your phone off hold vol up and down and pwr/ after first vibration release pwr button
Click to expand...
Click to collapse
if the update stops at 5% change firmware to B136 and try
sk0n3 said:
have you tried installing other firmwares?
one thing you might be able to do is...
1 flash twrp
2 wipe cache, data, system
3 reinstall system recovery
4 dload stock firmware
---------- Post added at 08:08 AM ---------- Previous post was at 08:04 AM ----------
http://forum.xda-developers.com/p9/how-to/guide-root-huawei-p9-t3367800
/\ /\ /\ /\ /\ /\ /\ /\
this guy works with one click its pretty cool
Click to expand...
Click to collapse
but my bootloader and FRP are locked now, can use the other methods to fix it? thanks
It's been suggested a couple of times already... Flash C432B136.
Sent from my EVA-L09 using Tapatalk
elspinat said:
It's been suggested a couple of times already... Flash C432B136.
Sent from my EVA-L09 using Tapatalk
Click to expand...
Click to collapse
now I want to turn off my phone, but can't turn it off and always boot to huawei logo screen how can I turn it off, please? thanks:crying:
You must connect to pc install adb and fastboot or srk tool and try fixed from pc
<<<by scaniathe>>>
scaniathe said:
You must connect to pc install adb and fastboot or srk tool and try fixed from pc
<<<by scaniathe>>>
Click to expand...
Click to collapse
I installed already, but the main point is, the bootloader and FRP mode are locked, if I used srk tool that must be unlock bootloader first...I'm so annoying...please help!
You unlock botloader fixed phone and lock again
<<<by scaniathe>>>
FRP mode is factory reset protection you know that right?
benjamen50 said:
FRP mode is factory reset protection you know that right?
Click to expand...
Click to collapse
I think it is....do you know how to fix it?? you can chat with me in PM....Thanks
scaniathe said:
You unlock botloader fixed phone and lock again
<<<by scaniathe>>>
Click to expand...
Click to collapse
the main point is I can boot into bootloader and rescue mode but i can't unlock bootloader....because the device's bootloader looked and also can't not use Hisuite to restore the firmware....so I'm very frustrate now.....:crying:
If I remember correctly even if FRP lock is enabled it should still allow official Huawei Firmware to be flashed onto the phone. It just means that you will need to enter most likely a google username and password (that was used to enable factory reset protection on the device) during the device initial setup wizard screen after the phone boots up for the first time after firmware flash / factory reset.
Though it is weird that you can't do the firmware flash via the system recovery option in hisuite. The device should be able to boot into system recovery mode (fastboot mode) right?
What happens when you try to do it? Does some error message come up?
I update to B132 and I have some bug on this firmware
https://www.youtube.com/watch?v=1yVya1LV5IM
https://www.youtube.com/watch?v=-Mhg3hdcSq0
I want to dowgrade from nem-l21_c432b132 back to stock nem-l21_c432b100
I copy the dload and update.app B100 + *#*#2846579#*#* and press update, but is not working, i get update failed.
How can downgrade the firmware?
You got the update fail cause your version is higher than b100.
I think that if you want to downgrade you will have to download Full B100 not the OTA.
But I recommend if you want to do this use the b130 - I am using it and it is very good.
Do the whole procedurę through turned of phone: then VOL down and up together if I remember correctly.
I have try Full B100 not ota.
Not working.
Maybe some one know how to downgrade with fastboot?
nem-l21_c432b132 to nem-l21_c432b130 is working downgrade.
But i want nem-l21_c432b100
i try flashboot
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash cust cust.img
fastboot flash system system.img
At fastboot flash system system.img i get failed
someone can help me?
@zzhunt This is an experimental method to go back to B100 by using OEMinfo. You do on your own risk! Required unlocked bootloader and installed TWRP (from Meticulus). Before performing make a full backup in TWRP.
1. Download here this package and put together of firmware B100 on the memory card,
2. Run and install in TWRP this package.
3. When finished install it, restart your smartphone to fastboot mode (Reboot>Bootloader)
4. Plug it into your computer and flash original recovery [LINK] a command "fastboot flash recovery recovery.img"
5. When you can flashed, then disconnect and hold power switch. When the informations will disappear from the display, immediately press the buttons Volume up and Volume down,
6. Will start the flashing system and after finishing restart your smartphone
7. Done!
I tested so far only on my device and don't know, what will happen with smartphone a different serial number/IMEI etc., but rather it should go.
@przemas2468 I can not flash twrp.
I get the same error: remote: command not allowed
zzhunt said:
@przemas2468 I can not flash twrp.
I get the same error: remote: command not allowed
Click to expand...
Click to collapse
Reverting back can be done by putting the full update in dload folder in sdcard. I have once got that error that u r talking about after the installing process completed. So i simply rebooted. And i got the stock one. So try this, just reboot and see.
@Shubho20 not working
https://www.youtube.com/watch?v=zLBrrrAJ1WQ&feature=youtu.be
I also go today to huawei service to flash the B100, and they can not flash.
They try but also not working
zzhunt said:
@Shubho20 not working
&feature=youtu.be
I also go today to huawei service to flash the B100, and they can not flash.
They try but also not working
Click to expand...
Click to collapse
What does ur dload folder contain? Only update.app?
yes
Shubho20 said:
What does ur dload folder contain? Only update.app?
Click to expand...
Click to collapse
And does the update process complete and then show that error?
---------- Post added at 03:30 PM ---------- Previous post was at 03:28 PM ----------
zzhunt said:
yes
Click to expand...
Click to collapse
In full stock firmware, after extracting it, there is dload folder. In dload folder there will be 2 folders and update app.
I try B100 firmware bulgaria and greece
On greece is only dload folder and update.app
And in bulgaria is 1 folder hw + update.app
http://postimg.org/image/w6e41dxet/
in hw folder is other folder EU and inside is update_data_hw_eu.app
I try with update.app + this folder.
Not working, at 5% fail install and start normal.
I want to go back to B100 because this updates B130-131-132 is junk for me.
Only problems i have
https://postimg.org/image/tkuz6g901/
https://postimg.org/image/4qbhcdo5t/
Double icons
Keyboard sometime freeze
https://www.youtube.com/watch?v=1yV..._comment_id=z131wfkqszjtzdi3l222x52jtmj0fpc3x
Fingerprint problems
This 3 updates for me is misery, only bugs i have
zzhunt said:
@przemas2468 I can not flash twrp.
I get the same error: remote: command not allowed
Click to expand...
Click to collapse
You have unlocked bootloader? If not, you'll have to unlock - here is a tutorial on how to do it. Then you flash TWRP and perform what I wrote previously.
for me b132 optimized alot battery life and ram usage. also gpu works better.
Hi!
I see the large number of requests concerning the roolback of a custom rom to a official and untouched EMUI 4, i decide to create this thread.
After follow that methode, you able to rest on official EMUI and get the new update automatically on OTA (directly on your phone) OR try to install custom rom with a clear and good base version.
1. You ave access on TWRP?
-If not, pleas unlock your bootloader (again) and flash TWRP recovery for you actual version (marshmallow or nougat).
-perform a full wipe and restore your partitions on "ext4" format, shutdown phone.
2. Get a "oem_info.zip" for your model phone (dont extract the .zip) and push it on your internal or external sd.
-This archive contain cust and oem info for patched your phone at the correct manufacture information.
-I have a link for VNS-L31 (c432, but is not very important) HERE LINK
-If you have other model (VNS-L31) pleas find a correct patch for you (VNS-L21, ...).
3. Find and download a EMUI marshmallow official full-ota update.
-for a VNS-L31 i advice choice a VNS-L31C432B160 full-ota update.
4. Unpack your update archive.
5. Create "dload" folder on your internal or external sd and put it UPDATE.APP
6. Reboot phone on TWRP recovery and flash "oem_info.zip"
7. Use dload methode for update (hold 3 buttons phone and dont release before "dload screen" appears)
8. Unlock your bootloader again (important!) And make a factory reset
9. Your phone reboot (please wait ) and done!
Ok now you are on official version, please update on setting menu >> update and choice, rest on official or flash a custom rom..
P9 lite brick precision:
In my personal experience the "p9 lite" is very easy to flash, mod or other tips and the risk of HARD brick is very very tiny.
If you see this page and your phone bootloop, relax, keep calm at 99,999% you have a little and ridiculous brick
Good luck and flash happy!
hi! i'm on 381, on my phone i have root, twrp and elite kernel...this guide is good for me???why after dload method i have to re-unlock my bootloader??
thank you and sorry for my english XD
macao1989 said:
hi! i'm on 381, on my phone i have root, twrp and elite kernel...this guide is good for me???why after dload method i have to re-unlock my bootloader??
thank you and sorry for my english XD
Click to expand...
Click to collapse
Yes, is good for you.
Not necessary to re-unlock bootloader.
Therand said:
Hi!
I see the large number of requests concerning the roolback of a custom rom to a official and untouched EMUI 4, i decide to create this thread.
After follow that methode, you able to rest on official EMUI and get the new update automatically on OTA (directly on your phone) OR try to install custom rom with a clear and good base version.
1. You ave access on TWRP?
-If not, pleas unlock your bootloader (again) and flash TWRP recovery for you actual version (marshmallow or nougat).
-perform a full wipe and restore your partitions on "ext4" format, shutdown phone.
2. Get a "oem_info.zip" for your model phone (dont extract the .zip) and push it on your internal or external sd.
-This archive contain cust and oem info for patched your phone at the correct manufacture information.
-I have a link for VNS-L31 (c432, but is not very important) HERE LINK
-If you have other model (VNS-L31) pleas find a correct patch for you (VNS-L21, ...).
3. Find and download a EMUI marshmallow official full-ota update.
-for a VNS-L31 i advice choice a VNS-L31C432B160 full-ota update.
4. Unpack your update archive.
5. Create "dload" folder on your internal or external sd and put it UPDATE.APP
6. Reboot phone on TWRP recovery and flash "oem_info.zip"
Click to expand...
Click to collapse
I can do everything up to point 6... won't enter to twrp... stays on Your device is now booting...
Update: I can now reach point 7 but now won't do dload (3 buttons) method... Huawei logo all the time. Can't even turn off the phone
In my other thread you post the same problem but is not entirely the same..
You succeeded to enter on fastboot mode? Flash recovery?
If you follow the steps 1-5 is impossible to fail the 6 point..
You have acces on fastboot mode or not?..
Therand said:
In my other thread you post the same problem but is not entirely the same..
You succeeded to enter on fastboot mode? Flash recovery?
If you follow the steps 1-5 is impossible to fail the 6 point..
You have acces on fastboot mode or not?..
Click to expand...
Click to collapse
I did update the post... 3 hours ago I wasn't able to enter TWRP, some way I did managed, now I can enter fastboot, I did flash custOEM (sorry I don't remember exactly the name but it's the one of your post) .zip file. Now I can't do dload method, stuck on huawei logo. If I try to go to recovery, I got red message "phone fail validation"...
I know, I post on both but I was trying to do everything...
just tried... validation red error message won't let me go to TWRP now...
You have a VNS-L31C432?
Your phone does not enter at dload mode?
Wipe all partitions an retry flash a oeminfo for your model phone (if not C432 you need right oeminfo).
Therand said:
You have a VNS-L31C432?
Your phone does not enter at dload mode?
Wipe all partitions an retry flash a oeminfo for your model phone (if not C432 you need right oeminfo).
Click to expand...
Click to collapse
How can I wipe all partitions if stuck in Huawei logo? Is there a way to do everything from adb command line? (I'm using Mac and cannot use all the tools I've found here XDA neither hiSuite which is basically a backup photo/video only the Mac version).
Thank for helping, really appreciate
To answer your question in the other thread, yes bootloader is unlocked and I am on C432.
What's your rom have before the bootloop?
You have the right version of TWRP for your rom?
If you have a MM version Don't flash a TWRP for N.
Send me a link to TWRP version used (thread forum)
Therand said:
What's your rom have before the bootloop?
You have the right version of TWRP for your rom?
If you have a MM version Don't flash a TWRP for N.
Send me a link to TWRP version used (thread forum)
Click to expand...
Click to collapse
Before the bootloop I was on L31C900 (on the phone) but I did actually flashed C432B160 because I did rollback. TWRP used I've found in the other post where there's a OEMfile to flash (but for this I need to double check because I did look so many pages which I am not 100% sure.
I not have experience on other model that C435.
But i suggest to find a oeminfo for your variant (C900?)
For TWRP you need flash a version for MarshMallow HERE
Flash it and pas return here (fastboot flash return and first enter to new recovery)
Hi, found Windows emulator for MacOs so I extract from update.app boot.img and flash.
I did format all partitions as told using a proper twrp this time.
What's next step, system says NO OS INSTALLED?
islandman75 said:
Hi, found Windows emulator for MacOs so I extract from update.app boot.img and flash.
I did format all partitions as told using a proper twrp this time.
What's next step, system says NO OS INSTALLED?
Click to expand...
Click to collapse
Flash partitions on .img files is not needed.
Just find a corect oeminfo for your model phone.
Flash it on TWRP recovery.
Use dload methode to update on basical version (MarshMallow b160).
After that, unlock bootloader again and make a factory reset.
Switch on your phone (the first boot make long time).
Update on last emui on OTA.
Done!
After that you able to install a custom rom.
Therand said:
Flash partitions on .img files is not needed.
Just find a corect oeminfo for your model phone.
Flash it on TWRP recovery.
Use dload methode to update on basical version (MarshMallow b160).
After that, unlock bootloader again and make a factory reset.
Switch on your phone (the first boot make long time).
Update on last emui on OTA.
Done!
After that you able to install a custom rom.
Click to expand...
Click to collapse
Done!
Thanks again you're saving my life!
IT won't turn off so been always on it won't keep the charge... Writing so because apparently it won't go to download mode (dload) if plugged in. On the other way if I unplugged from power it won't even start. Shall I force to download mode using console ADB or FASTBOOT? I had looked but can't find anything...
islandman75 said:
Done!
Thanks again you're saving my life!
IT won't turn off so been always on it won't keep the charge... Writing so because apparently it won't go to download mode (dload) if plugged in. On the other way if I unplugged from power it won't even start. Shall I force to download mode using console ADB or FASTBOOT? I had looked but can't find anything...
Click to expand...
Click to collapse
I not understand.
You not able to switch on your phone without connected charger?
Therand said:
I not understand.
You not able to switch on your phone without connected charger?
Click to expand...
Click to collapse
Correct. Because I'm not able to switch it off it won't keep the charge. When discharged, the minute I do plug on charge it wakes up... That's the loop...
My main question is: does a command exist to enter download mode using terminal?
islandman75 said:
Correct. Because I'm not able to switch it off it won't keep the charge. When discharged, the minute I do plug on charge it wakes up... That's the loop...
My main question is: does a command exist to enter download mode using terminal?
Click to expand...
Click to collapse
You have a hardware bug?
No abd command to enter dload mode..
Try flash a update.zip with twrp (not guaranted)
After that unlock bootloader again and make factory reset.
Therand said:
You have a hardware bug?
No abd command to enter dload mode..
Try flash a update.zip with twrp (not guaranted)
After that unlock bootloader again and make factory reset.
Click to expand...
Click to collapse
I'll try. Thank you
Hi, I followed this guide to go back to stock from elite rom. I flashed my oeminfo.img on twrp and then went to dload combination. Do I have to unlock the bootloader after the reboot? Thanks!
Hi,
I followed your guide and it works perfectly thanks!
Hi guys, muy English is not so good, but here we go:
I had a problem after rooting my P10, my phone is a VTR-L09c605 and I rebranded it to VTR-L29c432 successfully and after that I updated it to Oreo (b360) using the hwota.bat successfully again.
I flashed twrp for oreo and I installed magisk v16 without problems, it worked so fine until I decided to debloat a bit the phone, I remember that I uninstaled all the Gapps (using a Fx file explorer directly from system partition) and other app that I can't remember, after that I rebooted the phone and was stuck at bootloop, I saw the huawei bootanimation normarly (the bubbles with blue background) and the phone restarted again and again... In that moment I rebooted into twrp and wipe cache partition, I flashed this stock ramdisk https://forum.xda-developers.com/p10-plus/development/magisk-p10-p10plus-t3752482 and no luck (I don't know why I did it).
After that, I tried to flash the full ota using the hwota.bat but i was stuck at "your device has been unlocked and cannot be trusted, the phone is booting now" that message appears always when I tried to enter into twrp or erecovery but now it was stuck in that message and I rebooted it manually into fastboot, maybe the problem was that whem I tried to flash again the oreo full ota, I used the same files (contained in the recovery folder (twrp and recovery nocheck) from nougat.
Please guys, help me, I still can boot into fastboot, but can't boot into twrp(even flashing it via fastboot recovery_ramdisk) or erecovery, maybe the hwota.bat needs to be edited, but I don't know what lines I need to change, if someone knows how to repair the phone, please, help me.
Thanks in advanced
If you deleted some system app or system file by mistake it wont probably boot, try to flash ramdisk, original recovery_ramdisk, original kernel, and original system.img to see if it boots again, I would just try the first ramdisk(to get rid of root) recocery_ramdisk and original kernel.
Sent from my [device_name] using XDA-Developers Legacy app
lil_kujo said:
If you deleted some system app or system file by mistake it wont probably boot, try to flash ramdisk, original recovery_ramdisk, original kernel, and original system.img to see if it boots again, I would just try the first ramdisk(to get rid of root) recocery_ramdisk and original kernel.
Sent from my [device_name] using XDA-Developers Legacy app
Click to expand...
Click to collapse
I flashed some of them using fastboot, I extract them from the update.zip from the oreo's full ota (update.app) and using the huawei extractor, but there's a lot of recovery files, how to know which is the correct?
You just need recovery_ramdis.img it's written wrong in there and also ramdisk.img you also need kernel.img try with those only I have those file on my PC but I'm not home I could upload them and share you the link but it would be later.
Sent from my [device_name] using XDA-Developers Legacy app
lil_kujo said:
You just need recovery_ramdis.img it's written wrong in there and also ramdisk.img you also need kernel.img try with those only I have those file on my PC but I'm not home I could upload them and share you the link but it would be later.
Sent from my [device_name] using XDA-Developers Legacy app
Click to expand...
Click to collapse
No success my friend, I'm still getting the error mode: please update system again, and can't boot into recpvery (I flashed it)
The files that tou have are for oreo? I'm on L29c432b360
I'm a bit desperate, hope it can be fixed :/
Yes I have that same build and model, done worry u had the same issue before and it took me awhile to recover it , for sure it has a fix. Remember i flashed some other file last time but don't remember which since they are in my PC, do you have frp unlocked and phone unlocked ? Do you have access to you unlocked key? I would try to relock now that you are on the stock recovery and try to factory reset once it enters erecovery after it gets lock it performs a factory wipe
Sent from my [device_name] using XDA-Developers Legacy app
---------- Post added at 08:06 PM ---------- Previous post was at 08:05 PM ----------
Also try to press the volume up and down at the same time to enter update mode
Sent from my [device_name] using XDA-Developers Legacy app
---------- Post added at 08:07 PM ---------- Previous post was at 08:06 PM ----------
sfoot13 said:
No success my friend, I'm still getting the error mode: please update system again, and can't boot into recpvery (I flashed it)
The files that tou have are for oreo? I'm on L29c432b360
I'm a bit desperate, hope it can be fixed :/
Click to expand...
Click to collapse
Yes I had a similar issues same thing try to relock it and just make sure to be in stock recovery and ramdisk also and stock kernel. Once you relocked it I should do a factory reset try if that works.
Sent from my [device_name] using XDA-Developers Legacy app
lil_kujo said:
Yes I have that same build and model, done worry u had the same issue before and it took me awhile to recover it , for sure it has a fix. Remember i flashed some other file last time but don't remember which since they are in my PC, do you have frp unlocked and phone unlocked ? Do you have access to you unlocked key? I would try to relock now that you are on the stock recovery and try to factory reset once it enters erecovery after it gets lock it performs a factory wipe
Sent from my [device_name] using XDA-Developers Legacy app
---------- Post added at 08:06 PM ---------- Previous post was at 08:05 PM ----------
Also try to press the volume up and down at the same time to enter update mode
Sent from my [device_name] using XDA-Developers Legacy app
---------- Post added at 08:07 PM ---------- Previous post was at 08:06 PM ----------
Yes I had a similar issues same thing try to relock it and just make sure to be in stock recovery and ramdisk also and stock kernel. Once you relocked it I should do a factory reset try if that works.
Sent from my [device_name] using XDA-Developers Legacy app
Click to expand...
Click to collapse
Yes, I have frp and phone unlocked and I have my unlock key (saved as screenshot and .txt file).
So, if I relock my bootloader, it will do a low level format but actually I can't access to erecovery and update mode, because it fails to enter in that mode and I always get the error mode message.
But, there's a possibility to lock the bootloader and doing that, that action unlocks the access to erecovery? (sounds like a mess )
I'm not at home now, I'll try what you said me, and I'll wait until you can upload the files
Thank you so much for your help, I really appreciate it
Any success? I have the same problem. Im about ready to cough up 20 euros but im hopefully waiting for a solution.
I have same problem... Did you fix your phone? Some metohds for other guys work but not for me
We need a good tuto on that...Im stuck too now after trying some mods in build.prop
whats the adb command to flash erecovery-kernel/ramdisk ect.
---------- Post added at 03:32 PM ---------- Previous post was at 03:16 PM ----------
Cant extract Update.app in huawei update extractor...got error
Recovery_ramdisk.img Invalid header crc - Expected:22935 got 52610
really need help here hehehe
here are the results.. same as other guy,on that 432..
first of all.huawei update extractor wont open the update.pp from the HWOTA_VTRC432B360-Oreo package giving ramdisk error.....
have access to fastboot..
unlocked frp/bootloader
on stock recovery and cant flash any recovery---- twrp..it give some some partition error
successfully flashed :
kernel with erecovery_kernel_a.img
kernel with kernel_a.img
ramdisk with ramdisk_a.img
FAILED to flash:
erecovery_ramdisk_a with fastboot flash ramdisk erecovery_ramdisk_a.img (is it the good command ? )
recovery_ramdisk_a.img with fastboot flash ramdisk and recovery
so,whats next
please
all that cuz of frikkin build.prop MODIF.
i did re lock with low level reset...
i re unlock for another low level reset...
just wont boot anymore
when booting normally it takes me directly to firmware dload screen and fail to dload of course....
virusdunil said:
here are the results.. same as other guy,on that 432..
first of all.huawei update extractor wont open the update.pp from the HWOTA_VTRC432B360-Oreo package giving ramdisk error.....
have access to fastboot..
unlocked frp/bootloader
on stock recovery and cant flash any recovery---- twrp..it give some some partition error
successfully flashed :
kernel with erecovery_kernel_a.img
kernel with kernel_a.img
ramdisk with ramdisk_a.img
FAILED to flash:
erecovery_ramdisk_a with fastboot flash ramdisk erecovery_ramdisk_a.img (is it the good command ? )
recovery_ramdisk_a.img with fastboot flash ramdisk and recovery
so,whats next
please
all that cuz of frikkin build.prop MODIF.
i did re lock with low level reset...
i re unlock for another low level reset...
just wont boot anymore
when booting normally it takes me directly to firmware dload screen and fail to dload of course....
Click to expand...
Click to collapse
Same to me. Also i can flash CUST and some TWRPs but doesnt want to boot in recovery
I have fixed mine this morning by extracting KERNEL.img from update.app
fastboot flash kernel KERNEL.img
my p10 got back to life after trying all flashable things for maybe 6 hours yesterday
:silly:
I was stuck in error mode and managed to get out of it. I reached this gloriously by trying to flash Magisk V15.4 zip and then the oreoupgrade (from Jannomag), which failed..
First I tried the Multi-Tool method. Didn't work for me. Flashing was succesful, but no change in boot status.
So I slept over it and today I tried DC Phoenix. Selected the UPDATE.APP from update.zip and the UPDATE.APP from update_full_hw.zip. I cross my fingers and waited. It took a long time^^ When finished, it didn't reboot automatically. So I removed the cable and shut it down by pressing Power Button for some seconds. It booted then into eRecovery and I was confused.. It tried to download firmware via WiFi etc, but failed then with some ID error or smth, idk. I rebooted ....
aaaaaand voila: Booted without problems, all data still there!! :victory:
I sent it to tech service, tomorrow I'll know if they fixed my phone.
I think that I hard bricked it, because I relocked the bootloader, so the phone stuck at huawei's logo, no fastboot mode, no recovery, nothing, so guys, NEVER RELOCK THE BOOTLOADER if you get an error like that, it's the worst IDEA that you can have.
I'm a bit confused with this phone, looks like the system is very sensitive if you make modifications, like debloating or add or remove some lines in build.prop, things like tha.
Sadly, there's no much development for this phone :/
@Fenryl93 Happy to know that you fixed your phone bro!
@virusdunil you were using Oreo or Nougat? I was on Oreo, so I think that I'll not install Oreo until it becomes official :/
..
sfoot13 said:
@virusdunil you were using Oreo or Nougat? I was on Oreo, so I think that I'll not install Oreo until it becomes official :/
Click to expand...
Click to collapse
I was on nougat....VTR-L09 then rebranded it
Finally, the tech service repaired my phone, they changed the electronic board, well, that's what they wrote in the report.
So, I have my phone back, I'll try to be more careful this time.