I can only speak for BLA-L29C432B197 (Probably B179 too), but I assume this will cover any Pie firmware released in January.
In these releases Huawei disabled custom kernel, so phone won't boot with a custom kernel flashed.
This had me wanting to downgrade to B161 where it does work. So I try with NoCheck, which is fine to update with, Software install failed.
I try with FH (I happened to have a credit left) HiSuite method, Software install failed.
I tried with Dload package, same result.
So I figure I can use Rollback, as it worked fine on Beta to get back to Oreo with it...
It failed after 7% (or so, I didn't actually watch), device reboot to a black screen. Fastboot was working though.
So it most likely only flashed Oreo bootloader, and device was hardbricked. I managed to get it back using test point and IDT, this will void your warranty though.
So, do not downgrade using NoCheck recovery and rollback package, it's not worth the time to get device back.
Edit: Downgrade from Pie B197 to Oreo B157 is fine using NoCheck.
ante0 said:
So, do not downgrade using NoCheck recovery and rollback package, it's not worth the time to get device back.
Click to expand...
Click to collapse
So, there are no options to downgrade from 197? WTF is wrong with Huawei?
ante0 said:
So, do not downgrade using NoCheck recovery and rollback package, it's not worth the time to get device back.
Click to expand...
Click to collapse
And probably will also require spending money on other tools. Backups are also important, so people with rooted devices should use Partitions Backup (by wanam) and backup nvme, oeminfo and modem partitions.
As for downgrading with DLOAD or HiSuite we have no idea if it will work or if it will brick. Original recovery/eRecovery might have a fail safe mechanism.
badmania98 said:
So, there are no options to downgrade from 197? WTF is wrong with Huawei?
Click to expand...
Click to collapse
Dload might work or just refuse to downgrade, but i don't think it will brick.
Pretoriano80 said:
Partitions Backup (by wanam) and backup nvme, oeminfo and modem partitions.
Click to expand...
Click to collapse
Where I can find this app, and what version I have to use?
I installed Partitions Backup & Restore 2.0.1.
LE. Backup Done.
also.it's happened in alp-al00（mate10 china）.
Sent from my HUAWEI ALP-AL00 using XDA Labs
”5. This system version can be rolled back to the official version of EMUI 8.0 in Phone Manager. Rolling back the system version will erase your personal data. For more information, please contact the customer service hotline.” - according to description of v.197 firmware.
Where is this option in the phone menu? It is written in v.179 firmware, also.
badmania98 said:
”5. This system version can be rolled back to the official version of EMUI 8.0 in Phone Manager. Rolling back the system version will erase your personal data. For more information, please contact the customer service hotline.” - according to description of v.197 firmware.
Where is this option in the phone menu? It is written in v.179 firmware, also.
Click to expand...
Click to collapse
There's none! I don't know what they mean with Phone Manager. My guess is that HiSuite = Phone Manager.
zt379 said:
also.it's happened in alp-al00（mate10 china）.
Click to expand...
Click to collapse
When downgrading with No_check recovery?
I asked Huawei centre about downgrade and they told me that is possible in service centre only.
ante0 said:
I can only speak for BLA-L29C432B197 (Probably B179 too), but I assume this will cover any Pie firmware released in January.
In these releases Huawei disabled custom kernel, so phone won't boot with a custom kernel flashed.
This had me wanting to downgrade to B161 where it does work. So I try with NoCheck, which is fine to update with, Software install failed.
I try with FH (I happened to have a credit left) HiSuite method, Software install failed.
I tried with Dload package, same result.
So I figure I can use Rollback, as it worked fine on Beta to get back to Oreo with it...
It failed after 7% (or so, I didn't actually watch), device reboot to a black screen. Fastboot was working though.
So it most likely only flashed Oreo bootloader, and device was hardbricked. I managed to get it back using test point and IDT, this will void your warranty though.
So, do not downgrade using NoCheck recovery and rollback package, it's not worth the time to get device back.
Click to expand...
Click to collapse
Hey there, search on forum a tool for P20 Pro. From 179 i came back on 158 Oreo
Pretoriano80 said:
There's none! I don't know what they mean with Phone Manager. My guess is that HiSuite = Phone Manager.
When downgrading with No_check recovery?
Click to expand...
Click to collapse
perhaps never! and now hope xda developers could handle this bad things
Sent from my HUAWEI ALP-AL00 using XDA Labs
lorenzomeini56 said:
Hey there, search on forum a tool for P20 Pro. From 179 i came back on 158 Oreo
Click to expand...
Click to collapse
Can you put a link to this tool.?
badmania98 said:
Can you put a link to this tool.?
Click to expand...
Click to collapse
https://forum.xda-developers.com/huawei-p20/how-to/guide-how-to-rollback-emui-9-beta-to-t3841687
lorenzomeini56 said:
Hey there, search on forum a tool for P20 Pro. From 179 i came back on 158 Oreo
Click to expand...
Click to collapse
does it works in other kirin970 devices of emui9 to emui8？？
Sent from my HUAWEI ALP-AL00 using XDA Labs
lorenzomeini56 said:
https://forum.xda-developers.com/huawei-p20/how-to/guide-how-to-rollback-emui-9-beta-to-t3841687
Click to expand...
Click to collapse
This tool we already have it. I dont know if ante0 used it this time, but I think he did ( contains nocheck.img).
badmania98 said:
This tool we already have it. I dont know if ante0 used it this time, but I think he did ( contains nocheck.img).
Click to expand...
Click to collapse
Yep. Same NoCheck.img.
Edit: well, unless that nocheck is for p20... That might be why.
I will compare them.
I can confirm that in connecting my ALP-29 to my Windows 10 PC with HiSuite, I get offered the choice to roll back to Oreo. But the small print warns that your device should not be rooted or unlocked. I'm happy with Pie, so I'm not tempted to check whether this works without bricking your device, but just letting folks know about the purported option. Presumably if you try, you should at minimum unroot first......You also will be factory wiped.
ante0 said:
to get back to Oreo .
Click to expand...
Click to collapse
To what version of Oreo did you tried to get back?
badmania98 said:
To what version of Oreo did you tried to get back?
Click to expand...
Click to collapse
B150, the rollback version. I figured that would work as it is a rollback. But I should maybe have gone with B158.
Either way, don't do it with NoCheck for BLA
I'm almost done repairing device!
ante0 said:
B150, the rollback version. I figured that would work as it is a rollback. But I should maybe have gone with B158.
Click to expand...
Click to collapse
B150 was the roll back from Pie Beta. According to FF, I think that B156 and 157 are the roll back from official Pie.
badmania98 said:
B150 was the roll back from Pie Beta. According to FF, I think that B156 and 157 are the roll back from official Pie.
Click to expand...
Click to collapse
B157 should be the roll-back version. But a P20 Pro owner bricked when downgrading with HiSuite, with a completely stock device, so....
Related
Hi,
I've recently debranded my P20 Pro and found that I can no longer use Google Pay. As part of the debranding process, I unlocked the bootloader, rooted the phone, debranded, and then lost root, and noticed that even without root, it wasn't working.
I've rooted the P20 Pro after debranding and SafeNet Check is coming back False for ctsProfile and basicIntegrity, which after reading around, seems to be the issue here. I've tried using Magisk Core Only Mode, I've tried making sure Google Pay is selected in Magisk Hide etc, but still no luck.
Has anyone else managed to get Google Pay working after debranding, or managed to get SafetyNet to come back True after debranding?
Many thanks
Yes, you need to relock the bootloader but will mean you lose root
robot1000 said:
Yes, you need to relock the bootloader but will mean you lose root
Click to expand...
Click to collapse
This is incorrect, man. I have been using Google Pay fully rooted with an unlocked bootloader for over a month with no issues. I suspect it is either because the debranding process has created the issue or something to do with the firmware.
OP, what firmware are you running? If you are on 8.1.0.128a then that is the reason you are failing safetynet.
Downgrade to just 8.1.0.128 and it will function.
I'm unlocked and rooted, Google Pay works just fine.
robot1000 said:
Yes, you need to relock the bootloader but will mean you lose root
Click to expand...
Click to collapse
Thanks for your suggestion. I'll give it a try when i get home this evening.
robot1000 said:
Yes, you need to relock the bootloader but will mean you lose root
Click to expand...
Click to collapse
Shaolin36 said:
This is incorrect, man. I have been using Google Pay fully rooted with an unlocked bootloader for over a month with no issues. I suspect it is either because the debranding process has created the issue or something to do with the firmware.
OP, what firmware are you running? If you are on 8.1.0.128a then that is the reason you are failing safetynet.
Downgrade to just 8.1.0.128 and it will function.
Click to expand...
Click to collapse
Thanks for your reply. I'm on 8.1.0.128. The reason I debranded was to get firmware updates. I was originally stuck on a UK build CLT L29 8.1.0.110, but I'm now on EU build CLT L29 8.1.0.128.
angus_mcfisher said:
Thanks for your reply. I'm on 8.1.0.128. The reason I debranded was to get firmware updates. I was originally stuck on a UK build CLT L29 8.1.0.110, but I'm now on EU build CLT L29 8.1.0.128.
Click to expand...
Click to collapse
No problem. Your build number (in settings) would only show 128 even if on 128a which I suspect that you are infact on (which is the most recent C432 firmware on firmware finder).
Before locking your bootloader (which is unlikely to help, but maybe worth a try if you fail to pass safetynet after at least trying another firmware) you should check firmware finder for 128 (not 128a) and use the HuRUpdater method, and then see if SafetyNet passes.
I had the same issue, basically if your phones bootloader is unlocked but no root and no twrp is installed then all apps will fail the safenet check... No clue why, but i found that out after a few hours of testing and restoring the phone...
Shaolin36 said:
No problem. Your build number (in settings) would only show 128 even if on 128a which I suspect that you are infact on (which is the most recent C432 firmware on firmware finder).
Before locking your bootloader (which is unlikely to help, but maybe worth a try if you fail to pass safetynet after at least trying another firmware) you should check firmware finder for 128 (not 128a) and use the HuRUpdater method, and then see if SafetyNet passes.
Click to expand...
Click to collapse
Thanks again. Can you confirm that it's safe to downgrade the firmware? I' seem to remember reading that it bricks the phone.
auridas330 said:
I had the same issue, basically if your phones bootloader is unlocked but no root and no twrp is installed then all apps will fail the safenet check... No clue why, but i found that out after a few hours of testing and restoring the phone...
Click to expand...
Click to collapse
Thanks for your reply. Can I assume you got Google Pay back to working, after undoing the changes you made in testing, i.e. locking the bootloader, rooting, and installing twrp?
angus_mcfisher said:
Thanks for your reply. Can I assume you got Google Pay back to working, after undoing the changes you made in testing, i.e. locking the bootloader, rooting, and installing twrp?
Click to expand...
Click to collapse
Yup, reflashed with e-recovery back to stock and its all fine
So, if you did something wrong and finished with bricked phone or, just want to perform upgrade from O to O, or N to O, or to back from custom to stock one here it is the link and Manufacturer instruction with dload method.
Its a service rom for EU region C432. Don't use that for other regions it will not work.
My recommendation is to use Force method and only if you had bricked phone. For other situation you can use alternative methods, OTA, HWOta, , Ffinder, etc.
Please, read carefully instruction. Its not so easy and its a different method (files formats) for Emui 5.1 and Emui 8.0.
http://androidhost.ru/3ey
Good luck!
Can I just say a big thank you for this. It restored my hard bricked P10 plus after 2 frantic days of trying. BL and Frp both locked. And you say its complex, but its much much easier than other methods I have been trying. Thanks again. :good:
arsenicas said:
Can I just say a big thank you for this. It restored my hard bricked P10 plus after 2 frantic days of trying. BL and Frp both locked. And you say its complex, but its much much easier than other methods I have been trying. Thanks again. :good:
Click to expand...
Click to collapse
Yes, amazing stuff. Glad that u success unbricked not so cheap model.
Sent from my VKY-L29 using Tapatalk
Hi, the link isn't working.
Best regards
Rb1982 said:
Hi, the link isn't working.
Best regards
Click to expand...
Click to collapse
Androidhost is available at the moment.
Poslato sa WAS-LX1 uz pomoć Tapatoka
You are a life savior, thank you. It worked fine on my rebranded L09 > L29.
rafaila42 said:
You are a life savior, thank you. It worked fine on my rebranded L09 > L29.
Click to expand...
Click to collapse
How?
If not mistaken,
I created a folder on my SD card (by connecting it to my PC card reader),
and placed there the files exported.
Code:
dload
.
├── update_sd.zip
├── VKY-L09_hw_eu
│ └── update_sd_VKY-L09_hw_eu.zip
└── VKY-L29_hw_eu
└── update_sd_VKY-L29_hw_eu.zip
After, I tried several times to boot with the three buttons. V+, V-, POWER, as mentioned in the directions file page 6, to enter the Software Upgrade Mode.
By pressing V- and pluging-in the usb, i was in fastboot mode, so, from console i unlocked my bootloader (several times) because it was getting locked again, example: fastboot oem unlock 1234567890123456
Also, i had to install again twrp: fastboot flash recovery_ramdisk C:/twrp.img.
I was on rebranded stock emui8, then tried to install B201 fromfuture, but probably i had done some thing wrong and i was in a bootloop. Most of the times, i was ending on erecovery screen, unsuccessfully trying to update through ff.
After installation of stock firmware, i had an FRP lock. So i did: fastboot oem relock 1234567890123456, reboot several times and in the end i had it cleared. Maybe I am forgetting something, I wasn't keeping notes.
stock firmware relocking and unlocking again was not helpful. I had to normally update the stock, maybe to 371.
rafaila42 said:
stock firmware relocking and unlocking again was not helpful. I had to normally update the stock, maybe to 371.
Click to expand...
Click to collapse
Could you send us what u want to do? I tried to understand but....
You had emui 8 and wanted to instal patched b201 which is emui 5.....you bricked phone did u?
Poslato sa VKY-L29 uz pomoć Tapatoka
Alexxxx1 said:
You had emui 8 and wanted to instal patched b201 which is emui 5.....you bricked phone did u?
Click to expand...
Click to collapse
Yes, that's exactly what I did.
As mentioned above, I was in a bootloop, but I still had erecovery. I tried to update through ff, but the phone was not finding any FW, maybe I did something wrong. With the files provided by you, I managed to reflash it, following the dload method described in chapter 4, "O-O Upgrade operations" paragraph 2 "Force upgrade". Only problem was, I couldn't start the recovery in "Software Upgrade Mode" (Step 4, page 6). I had to try several times. Once I managed to successfully reflash, I had to do an OTA upgrade (to 371 I think), in order to bypass my "FRP lock" problem.
After this, I managed to install openkirin's "OmniROM Pie Alpha 3".
Hope I was more clear now.
rafaila42 said:
Yes, that's exactly what I did.
As mentioned above, I was in a bootloop, but I still had erecovery. I tried to update through ff, but the phone was not finding any FW, maybe I did something wrong. With the files provided by you, I managed to reflash it, following the dload method described in chapter 4, "O-O Upgrade operations" paragraph 2 "Force upgrade". Only problem was, I couldn't start the recovery in "Software Upgrade Mode" (Step 4, page 6). I had to try several times. Once I managed to successfully reflash, I had to do an OTA upgrade (to 371 I think), in order to bypass my "FRP lock" problem.
After this, I managed to install openkirin's "OmniROM Pie Alpha 3".
Hope I was more clear now.
Click to expand...
Click to collapse
You should use force method upgrade pressing volume up, volume down and power key for N to O, not O to O because u was on 201...but at the end u success upgraded.
Poslato sa VKY-L29 uz pomoć Tapatoka
Given the filesizes
will it work with the SD card formatted in NTFS?
algarues said:
Given the filesizes
will it work with the SD card formatted in NTFS?
Click to expand...
Click to collapse
It should be ok.
But.... Remember. If you have last update from January dont use older service roms because you will brick it permanently. Only use last service rom from androidhost.ru with January security patch.
Huawei implemented antirollback features. So if you try older stock rom to flash on new one it will be trigger to change xloader partition and block fastboot. So, there is no any chance to repair phone.
Sent from my WAS-LX1 using Tapatalk
Alexxxx1 said:
It should be ok.
But.... Remember. If you have last update from January dont use older service roms because you will brick it permanently. Only use last service rom from androidhost.ru with January security patch.
Huawei implemented antirollback features. So if you try older stock rom to flash on new one it will be trigger to change xloader partition and block fastboot. So, there is no any chance to repair phone.
Sent from my WAS-LX1 using Tapatalk
Click to expand...
Click to collapse
Thank you!
I am actually still on Nougat and try to upgrade on Oreo, since FF failed.
I am using VKY-L09C432.
I guess it should be fine....
The security patch is from 2017
algarues said:
Thank you!
I am actually still on Nougat and try to upgrade on Oreo, since FF failed.
I am using VKY-L09C432.
I guess it should be fine....
The security patch is from 2017
Click to expand...
Click to collapse
Yep, but read carefully software upgrade guideline zipped together with dload. You should extract update_sd.zip into update.app and subfolder with file in it.
If you havent rooted phone you can try Hisuite and check update using PC.
Sent from my WAS-LX1 using Tapatalk
Alexxxx1 said:
Yep, but read carefully software upgrade guideline zipped together with dload. You should extract update_sd.zip into update.app and subfolder with file in it.
If you havent rooted phone you can try Hisuite and check update using PC.
Sent from my WAS-LX1 using Tapatalk
Click to expand...
Click to collapse
Thank you!
will follow the instructions
Hisuite does not see updates available, even if setting the FF proxy in settings
mistery
algarues said:
Thank you!
will follow the instructions
Hisuite does not see updates available, even if setting the FF proxy in settings
mistery
Click to expand...
Click to collapse
Did you try erecovery method as new one in FF?
Sent from my WAS-LX1 using Tapatalk
Alexxxx1 said:
Did you try erecovery method as new one in FF?
Sent from my WAS-LX1 using Tapatalk
Click to expand...
Click to collapse
yes, I tried changing the dns on the router, but it failed. I have the suspicion some providers block the traffic from that ip.
But let's give a try to your method.
The phone I have is unrooted and sim unlocked.
However, I bought it second hand.
Anything I should check on it that might be preventing updates?
algarues said:
yes, I tried changing the dns on the router, but it failed. I have the suspicion some providers block the traffic from that ip.
But let's give a try to your method.
The phone I have is unrooted and sim unlocked.
However, I bought it second hand.
Anything I should check on it that might be preventing updates?
Click to expand...
Click to collapse
Maybe to change Sim card from other operator for the moment and check. Could you send me current build no in phone and which region...
Sent from my WAS-LX1 using Tapatalk
Official EMUI 9.0 release for Mate 10 Pro (BLA-L29), European version (c432).
Requirements ;
1) Unlocked Bootloader
2) Root (only if you go from EMUI8.0 - > EMUI 9
3) A PC with working ADB
4) Some residual gray matter ?
Download - > https://androidhost.ru/7K8
Installation :
1) Upgrading from EMUI8.0
* use this tool - > https://mega.nz/#!w0kVRJjQ!MxuNRqUWJ-xM-nj2houAGqgreIodqbrwEIfVZ10CDcc
Run flash.bat and follow the on-screen instructions!
2) Updating from EMUI9 beta
* use this tool - > https://mega.nz/#!B9MnBYqQ!Ie7t_5lNSNlfiJqAY6ui_yV9rWyU3UUig2D5MFkdx68
Run flash.bat and follow the on-screen instructions!
Why we need root for 8.0? The download file says no service? Does everthing work? Thanks
inthedark22 said:
Why we need root for 8.0? The download file says no service? Does everthing work? Thanks
Click to expand...
Click to collapse
For the EMUI 8 to 9 tool you will need root. You can do it from TWRP if you wanted to.
But you will need an unlocked bootloader at least, else you won't be able to install it.
No service = its not a service firmware, as most are on androidhost.ru.
Everything works fine. I just flashed it.
inthedark22 said:
Why we need root for 8.0? The download file says no service? Does everthing work? Thanks
Click to expand...
Click to collapse
It says "no service" because it's not a DLOAD firmware.
Sorry, i'm just asking... From where did you got the rom? I see nothing on FF
Pretoriano80 said:
It says "no service" because it's not a DLOAD firmware.
Click to expand...
Click to collapse
Will There be any problem when updating from emui 8.0 to 9.0 if i have deleted some apps from my system folder beforehand ??
ante0 said:
For the EMUI 8 to 9 tool you will need root. You can do it from TWRP if you wanted to.
But you will need an unlocked bootloader at least, else you won't be able to install it.
No service = its not a service firmware, as most are on androidhost.ru.
Everything works fine. I just flashed it.
Click to expand...
Click to collapse
My bootloader is unlocked but everything is stock. Reboot in bootloader and run flash. Bat wont do the trick?
Sheldd said:
Sorry, i'm just asking... From where did you got the rom? I see nothing on FF
Click to expand...
Click to collapse
Got it from a friend, who got it from another friend which found it on www.
inthedark22 said:
My bootloader is unlocked but everything is stock. Reboot in bootloader and run flash. Bat wont do the trick?
Click to expand...
Click to collapse
It won't with the EMUI8 tool as it is now.
I will edit the EMUI9 tool and upload it, it will only require unlocked bootloader.
Edit: You can just use the EMUI9 tool as is, it's using Oreo TWRP and Oreo NoCheck.
As I am sure that EMUI 9 comes with new bootloader, is it possible to flash it without flashing xloader? As the Custom treble rom I want to use do not work on 9.0 vendor, so I could downgrade back.
Or uses the EMUI9 the 02xloader? If 02 then I can upgrade it to try it out!
Hopefully the update doesnt come x years laters for the ones on the official beta lol, anyway have fun guys
L09 nothing yet
how can i root BLA29 c432 157 versiot firmware?
nagyviktor199017 said:
how can i root BLA29 c432 157 versiot firmware?
Click to expand...
Click to collapse
Unlock phone, flash twrp by pretoriano80, flash Magisk zip in twrp.
Alternatively: unlock phone, patch ramdisk in Magisk Manager, flash patched ramdisk in fastboot.
Would this method work for upgrading BLA-L29c636 b145 to BLA-L29C636E2R1P13B159 (9.0.0.159)
Is there any chance of getting a working TWRP/root on this version?
Great news. I've just installed it without problems. Is there any safe way to unroot and relock bootloader?
thatJasper said:
Is there any chance of getting a working TWRP/root on this version?
Click to expand...
Click to collapse
Apparently the root developers, amongst others John Wu (Magisk), are working to get a simple way to root EMUI 9.0.
The root has already been confirmed to be working on the Huawei Mate 10 Pro and more devices should join the party sooner or later.
Click to expand...
Click to collapse
https://www.theandroidsoul.com/emui-9-0-already-rooted/
the rom is working, but horrible performance. 125 000 points with antutu. fully working but very slow. i back to stock emui 8
Pretoriano80 said:
It says "no service" because it's not a DLOAD firmware.
Click to expand...
Click to collapse
I'm on emui 9 beta and my bootloader and FRP were both unlocked. I removed all the scheme (fingerprint ecc.) ... but when i tred to flash the upgrade with your tool I saw that the FRP got locked. In the Setting options, Developper, (OEM unlock option is not anymore active). How can I restore this options to go on with the upgrade? Thank in advance.
So I tried FunkyHuawei to downgrade from pie beta to official. Now i'm bricked totally. Only getting into fastboot and are not unlocked. My guess is i'm screwed. Can't access Erecovery neither. Stupidity pays it price.
Any ideas at all? Cant really do anything, and the screen is all black too.
superior888 said:
So I tried FunkyHuawei to downgrade from pie beta to official. Now i'm bricked totally. Only getting into fastboot and are not unlocked. My guess is i'm screwed. Can't access Erecovery neither. Stupidity pays it price.
Any ideas at all? Cant really do anything, and the screen is all black too.
Click to expand...
Click to collapse
What model do you have (rebranded or not) , what firmware did you choose on funky site?
If you still can boot into fastboot mode funky should be able to recover it.
forever_lol said:
What model do you have (rebranded or not) , what firmware did you choose on funky site?
If you still can boot into fastboot mode funky should be able to recover it.
Click to expand...
Click to collapse
I have CLT29C432. Tried the downgrade method through hisuite. I'll check with em
superior888 said:
I have CLT29C432. Tried the downgrade method through hisuite. I'll check with em
Click to expand...
Click to collapse
Please specify What firmware you tried to flash
Did you modify your phone somehow? Rebrand/bootloader unlock?
forever_lol said:
Please specify What firmware you tried to flash
Did you modify your phone somehow? Rebrand/bootloader unlock?
Click to expand...
Click to collapse
Downgrade from EMUI9 to EMUI8 CLT-L29 8.1.0.156(C432)
that one. No nothing. it was on the beta program as i bought it.
Tried to install it again but getting fail when installig recovery in Hisuite...
superior8888 said:
Downgrade from EMUI9 to EMUI8 CLT-L29 8.1.0.156(C432)
that one. No nothing. it was on the beta program as i bought it.
Tried to install it again but getting fail when installig recovery in Hisuite...
Click to expand...
Click to collapse
This thing remains mystery to me.
I have literally the same model, and I've downgraded from Pie (both beta and stable 163) using the same method and firmware several times. I've never had any issues. In the changelog for rollback firmware you've chosen you can find:
"1. Please make sure you are currently using the official version of Huawei EMUI, and that no unofficial updates have been installed. Otherwise, there will be risk of an unsuccessful rollback, and an unknown error may occur. 2. Make sure that the current version has not been unlocked or rooted. "
But since you've never fiddled with your handset, never unlocked your bootloader this warning shouldn't apply to you.
Have you tried flashing pie again via OTG?
I would but i cant access recovery. I mean the otg is ready to go..i tried several firmware
from funky with same error when flashing recovery. I usually solve bricks but this got me :-\
How about extracting the erecovery source from the update package and try installing erecovery via fastboot instead of hisuite?
VinCme said:
How about extracting the erecovery source from the update package and try installing erecovery via fastboot instead of hisuite?
Click to expand...
Click to collapse
Wouldnt be possible i guess. As i said bootloader is locked...
Skickat från min G3311 via Tapatalk
Going to send it for repair. Still warranty and they probably never know what happend..so.
superior888 said:
So I tried FunkyHuawei to downgrade from pie beta to official. Now i'm bricked totally. Only getting into fastboot and are not unlocked. My guess is i'm screwed. Can't access Erecovery neither. Stupidity pays it price.
Any ideas at all? Cant really do anything, and the screen is all black too.
Click to expand...
Click to collapse
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.
Comming soon.. maybe this year
il3gal said:
Comming soon.. maybe this year
Click to expand...
Click to collapse
That's old, there's already a B140 build. xD
Pretoriano80 said:
That's old, there's already a B140 build. xD
Click to expand...
Click to collapse
FF is always behind a bit I think, but if it's there it means its coming soon.
Pretoriano80 said:
That's old, there's already a B140 build. xD
Click to expand...
Click to collapse
Looking forward for an update solution from you and ante0.
badmania98 said:
Looking forward for an update solution from you and ante0.
Click to expand...
Click to collapse
All versions of EMUI10 that I've tested so far, force locks bootloader. So don't install if you don't want to get locked. I guess if you have beta access approved you can downgrade back to 9.1 using HiSuite.
I have to downgrade using testpoint
Fastboot will still say you're unlocked but the command fastboot oem lock-state info says it's locked. Downgrading back to 9.1 will give back the unlock status, apparently. I guess they just add something to lock even if you're technically still unlocked. And the command to unlock through fastboot is removed so no way to unlock it again. I hope it's just locking for the beta.
ante0 said:
All versions of EMUI10 that I've tested so far, force locks bootloader. So don't install if you don't want to get locked. I guess if you have beta access approved you can downgrade back to 9.1 using HiSuite.
I have to downgrade using testpoint
Fastboot will still say you're unlocked but the command fastboot oem lock-state info says it's locked. Downgrading back to 9.1 will give back the unlock status, apparently. I guess they just add something to lock even if you're technically still unlocked. And the command to unlock through fastboot is removed so no way to unlock it again. I hope it's just locking for the beta.
Click to expand...
Click to collapse
Maybe it is necessary to downgrade till EMUI 8.0?
I don't have beta access till now. But , as you know, I follow your and Pretoriano80 work very carefully.
badmania98 said:
Looking forward for an update solution from you and ante0.
Click to expand...
Click to collapse
Like @ante0 said in the previous post, we already have the links for the updates, but so far all of them will trigger the bootloader lock, so unless you don't care about it, you should refrain from flashing EMUI10.
If the final release won't change this behavior, then probably Huawei has decided to lock the bootloader for good.
Pretoriano80 said:
Like @ante0 said in the previous post, we already have the links for the updates, but so far all of them will trigger the bootloader lock, so unless you don't care about it, you should refrain from flashing EMUI10.
If the final release won't change this behavior, then probably Huawei has decided to lock the bootloader for good.
Click to expand...
Click to collapse
I prefer to wait. If you 2 will find a good solution to maintain boot-loader unlocked, I will follow it.
badmania98 said:
Maybe it is necessary to downgrade till EMUI 8.0?
I don't have beta access till now. But , as you know, I follow your and Pretoriano80 work very carefully.
Click to expand...
Click to collapse
Downgrade to EMUI 8?
Well, if you do like me you have to as I have to flash board when BL is locked.
If you mean to keep unlock it won't work. Update from Oreo to Q directly will cause problems, it did for me when going Oreo to 9.1 anyway, and system update actually forces you to flash the latest stable 9.0 (9.0.0.197) to update to 9.1.0.300 then to 9.1.0.306.
And it's not like it's using a function to lock BL like they do when you flash a dload firmware. It's probably still unlocked but something changes it to locked. Iirc you could unlock using TP before, but now it refuses as USERLOCK is changed to unlock as well when you use testpoint, so it will just say "Phone is already unlocked", before it only changed FBLOCK to unlock.
But we will see what happens
@ante0 @Pretoriano80 : just in case I would install this beta from FF. What install method I have to use?
badmania98 said:
@[email protected] : just in case I would install this beta from FF. What install method I have to use?
Click to expand...
Click to collapse
Installing with no-check recovery should work just fine, but you should also flash the new CUST and Preload.
If you really want to flash it, i can send you the link with the latest build (B140), but like i said, it will lock your bootloader.
Pretoriano80 said:
Installing with no-check recovery should work just fine, but you should also flash the new CUST and Preload.
If you really want to flash it, i can send you the link with the latest build (B140), but like i said, it will lock your bootloader.
Click to expand...
Click to collapse
Yes, thanks in advance. Also the link for the no-check recovery & tool.
LE. It is from somebody else.
badmania98 said:
Yes, thanks in advance. Also the link for the no-check recovery & tool.
LE. It is from somebody else.
Click to expand...
Click to collapse
It's a BLA-L29 C432 device?
Pretoriano80 said:
It's a BLA-L29 C432 device?
Click to expand...
Click to collapse
Yes.
badmania98 said:
Yes.
Click to expand...
Click to collapse
You can use the 3 files tool (skip the rooting part, of course) from here -> https://forum.xda-developers.com/mate-10/how-to/tool-emui-9-0-to-9-1-upgrade-tool-t3949867 <- and replace the nocheck.img with the one from here (tge no verification version) - > https://forum.xda-developers.com/mate-10/development/recovery-nocheck-pie-t3950037
Make sure that the downloaded firmwares are not corrupt, otherwise the installation may fail, because the no-check recovery will skip the integrity check.
I will send you the update files in PM.
i'd like to have a link for the update files aswell please, on firmware finder PC version there's only 10.0.139
vandal4e said:
i'd like to have a link for the update files aswell please, on firmware finder PC version there's only 10.0.139
Click to expand...
Click to collapse
It doesn't really matter. When you flash it you won't be able to flash any newer ones as you won't be unlocked anymore, and can't unlock again either without downgrading back to 9.1.
I would wait until official to see if forced locking remains or not.