Related
I don't know why I saw everywhere that, to update from 10.0.3.0 Global Stable to Beta 8.10.25, you could only do with unlocked BL (even using XiaoMiTool it says that).
This is because I can say that I was able to do the update, not via OTA (it fails with an error message explained below) or via EDL, but via other method with a locked BL, no root and no custom recovery. To clarify, I'm using a Global Version of the Mi 8, with the Chinese Version i'ts probably not possible but I'm not sure since I did not test it, but from what I read it's not safe.
So here's what I did:
I used Xiaomi ADB: ht tp://ww w.xiaomit ool.co m/adb (just aggregate to make a link, I can't post links yet), and just install and follow the steps on the site and you are good to go
In the process, the first time it logged an error on the console that already happened when I tried to update via OTA updater (something like "Your android version is different from the current one and bla bla bla...") but right in the next attempt was successfull (the attempts are done automatically). Also, nothing was erased during the process, all data was kept which is nice
Link for the ROM: htt p://bigo ta.d.miui.co m/8.10.25/miui_M I8Global_8.10.25_f598e a6e8b_9.0.zip (no spaces ofc)
dugapila said:
i don't know why i saw everywhere that, to update from 10.0.3.0 global stable to beta 8.10.25, you could only do with unlocked bl (even using xiaomitool it says that).
This is because i can say that i was able to do the update, not via ota (it fails with an error message explained below) or via edl, but via other method with a locked bl, no root and no custom recovery. To clarify, i'm using a global version of the mi 8, with the chinese version i'ts probably not possible but i'm not sure since i did not test it, but from what i read it's not safe.
So here's what i did:
I used xiaomi adb: Ht tp://ww w.xiaomit ool.co m/adb (just aggregate to make a link, i can't post links yet), and just install and follow the steps on the site and you are good to go
in the process, the first time it logged an error on the console that already happened when i tried to update via ota updater (something like "your android version is different from the current one and bla bla bla...") but right in the next attempt was successfull (the attempts are done automatically). Also, nothing was erased during the process, all data was kept which is nice
Click to expand...
Click to collapse
although you have successfully do it., it was still a very risky move. If you brick the phone with bootloader locked, it will be very troublesome procedure afterwards. I do not encourage people to risk their phone. Just unlock your phone bootloader first. A month wait worth more then bricking your phone with locked bootloader>
AzleeKarliff said:
although you have successfully do it., it was still a very risky move. If you brick the phone with bootloader locked, it will be very troublesome procedure afterwards. I do not encourage people to risk their phone. Just unlock your phone bootloader first. A month wait worth more then bricking your phone with locked bootloader>
Click to expand...
Click to collapse
I don't know why it's risky. As long as i have global version and flash an official mi ROM (with version equal or greater than what I have, even if it's beta version) I think I'm fine, why do you think it's risky?
dugapila said:
I don't know why it's risky. As long as i have global version and flash an official mi ROM (with version equal or greater than what I have, even if it's beta version) I think I'm fine, why do you think it's risky?
Click to expand...
Click to collapse
If you bricked your phone with Locked BL , you may not be able to revive it thru flashing since it may not allow flashing other firmware or recovery like TWRP. Also, ARB may brick your phone if you flashed old version.
Tried. Didn't work for me
engineer000 said:
If you bricked your phone with Locked BL , you may not be able to revive it thru flashing since it may not allow flashing other firmware or recovery like TWRP. Also, ARB may brick your phone if you flashed old version.
Click to expand...
Click to collapse
I flashed to a newer version ofc (even so because it's from Android 8.1 to 9) and you are always allowed to flash and official ROM, even if everything goes wrong, flash back to the Global stable. The tool also notifies and doesn't proceed to flash the ROM if all attempts are tried and unsuccessful.
With things like custom recoveries is where you brick your phones, cause people either don't download and official ROM or something goes wrong and with unlocked BL you're getting screwed...
Also to wait like 25 more days to unlock BL I was like damn it let's try this method and voilá
ricpicpr said:
Tried. Didn't work for me
Click to expand...
Click to collapse
What version are you on? And are you global or chinese version?
Exactly the same of you. From Global 10.0.3 to Developer 8.10.25. My Mi 8 is official global version with locked bootloader (for now, i have to wait the last 10 days)
ricpicpr said:
Exactly the same of you. From Global 10.0.3 to Developer 8.10.25. My Mi 8 is official global version with locked bootloader (for now, i have to wait the last 10 days)
Click to expand...
Click to collapse
I have 30 days to wait because I already unlocked one device on my account. And same as you I can't flash by this method.
8.11.1 beta full ROM update
This was officially suspended for our device, but I'll post it anyway for those that want it.
http://bigota.d.miui.com/8.11.1/miui_MI8Global_8.11.1_ed2903c393_9.0.zip
Flash at your own risk...
dugapila said:
I flashed to a newer version ofc (even so because it's from Android 8.1 to 9) and you are always allowed to flash and official ROM, even if everything goes wrong, flash back to the Global stable. The tool also notifies and doesn't proceed to flash the ROM if all attempts are tried and unsuccessful.
With things like custom recoveries is where you brick your phones, cause people either don't download and official ROM or something goes wrong and with unlocked BL you're getting screwed...
Also to wait like 25 more days to unlock BL I was like damn it let's try this method and voilá
Click to expand...
Click to collapse
if camera is better in 8.10.25 than the stable, I may try this. can you confirm if camera is better or not? Thanks
engineer000 said:
if camera is better in 8.10.25 than the stable, I may try this. can you confirm if camera is better or not? Thanks
Click to expand...
Click to collapse
I don't know. Maybe on the front camera it's better stabilized for photos but other than that I don't notice anything special. I use the Google Camera anyways (link for that: https://www.celsoazevedo.com/files/android/google-camera/f/MGC_6.1.009_MI8_V1a.apk), it's much better, even more for low-light situations (although the latest version still has some bugs and missing some features that I hope will be addressed in the future)
ricpicpr said:
Exactly the same of you. From Global 10.0.3 to Developer 8.10.25. My Mi 8 is official global version with locked bootloader (for now, i have to wait the last 10 days)
Click to expand...
Click to collapse
I don't know then. Maybe if you try one more time. I don't think it will brick anyways because if the process fails, then the command line of the tool will say it can't do it and will not flash, at least afaic.
I will wait for a new ota then will immediately flash the beta?
Before start i'd like to tell you about my adveture with my phone
I had a Huawei mate 10 ( ALP-L29 c185) installed 8.0.0.139, rooted with magisk and TWRP (By Pretoriano80) as recovery so yesterday i suddenly think that "i shuld try android 9" (i don't know why?) . I searched here and internet so finally i decided to update by "hurupdater" method. I downloaded stock firmware by "Firmware Finder for Huawei" app (9.0.0.177) and hurupdater 0.4 also twrp_bla_alp_0.7.img for twrp recovery. I put them in same folder on sdcard. Renamed recovery.img to keep recovery as twrp. Lastly i restarted recovery and installed hurupdater.zip.
DANG!!! My phone is bricked....... It gave a lot of errors during installation and when i try to reboot it was bootlooping, cant load recovery interface (twrp or stock). I could enter e-recovery but gives "getting package info failed" error. So ended up with bricked phone in my hands. I tried many ways including hisuite but nada....
Then i remembered "Funky Huawei", bought 1 credit and followed instructions. After long hellish hours (firmware downloading takes long) i have my phone back working with stock 8.0.0.140 rom, stock recovery even relocked bootloader also my whole data was intact. My curosity cost me 20 $ and hours. This morning i realised there is system update 9.0.0.159
So my questions o this point
1)What should i do now? Update to android pie (with stcock recovery of course)? Is it worth trying or just install twrp and root my current rom and go on my way for a while longer ? (till a more stable pie relase)
2) For the future, what was wrong in my update process. I'd never want to make same mistake again..
Thanks...
draqkin said:
Before start i'd like to tell you about my adveture with my phone
I had a Huawei mate 10 ( ALP-L29 c185) installed 8.0.0.139, rooted with magisk and TWRP (By Pretoriano80) as recovery so yesterday i suddenly think that "i shuld try android 9" (i don't know why?) . I searched here and internet so finally i decided to update by "hurupdater" method. I downloaded stock firmware by "Firmware Finder for Huawei" app (9.0.0.177) and hurupdater 0.4 also twrp_bla_alp_0.7.img for twrp recovery. I put them in same folder on sdcard. Renamed recovery.img to keep recovery as twrp. Lastly i restarted recovery and installed hurupdater.zip.
DANG!!! My phone is bricked....... It gave a lot of errors during installation and when i try to reboot it was bootlooping, cant load recovery interface (twrp or stock). I could enter e-recovery but gives "getting package info failed" error. So ended up with bricked phone in my hands. I tried many ways including hisuite but nada....
Then i remembered "Funky Huawei", bought 1 credit and followed instructions. After long hellish hours (firmware downloading takes long) i have my phone back working with stock 8.0.0.140 rom, stock recovery even relocked bootloader also my whole data was intact. My curosity cost me 20 $ and hours. This morning i realised there is system update 9.0.0.159
So my questions o this point
1)What should i do now? Update to android pie (with stcock recovery of course)? Is it worth trying or just install twrp and root my current rom and go on my way for a while longer ? (till a more stable pie relase)
2) For the future, what was wrong in my update process. I'd never want to make same mistake again..
Thanks...
Click to expand...
Click to collapse
I have exactly same phone (c185) never tried unlocking bootloader but I updated to emui 9 159 there are some buggy things like when you want to use third party lunchers You can't use gesture navigation and it has so many bugs so not using gesture is better
there are again some problems with third party launchers (im using nova) like sometimes when you go to "resents" its totally blank and you have to force stop "huawei home" to make it right
there are some good changes in camera like new 960 fps slow motion (but there is a huge crop in 240fps 720p and 960fps 720p I can't remember that 240fps had that crop or not) Turning off master ai and some new scene detection but it's slower than last one
there is a new performance mode that i love using it (it feels like a real flagship however it's not because of stupid SOC)
there is a new AI api that android 8 didn't have so most of apps wasn't able to use NPU
in emui 8 there is a little bit better battery
I love changes to my phone so I preferred buggy new firmware to old ones there are so many good little changes in interface (like when you take a picture you can go to gallery then scan it for QR code)
There is a way better Mira cast functionality (and new desktop mode in it)
hi touch, hi vision
These were all expensives I had with emui 9 that I can think of
How did you update @arianamirgholami ?
Meanwhile, I have the same phone but am still on Android Oreo......I have the ALP-L29 8.0.0.141(C185) model. I'm reading more and more about others with this model that have gotten the Android Pie upgrade over the last two months but the upgrade is still not available to me. Makes no sense...I have a stock rom on the phone, I am NOT rooted and my bootloader is locked. Neither hisuite, hicare, system update, nor firmware finder methods gets me anywhere. They all say that I'm on the most recent firmware.... 8.0.0.141(C185). Go figure....
curgervending said:
Meanwhile, I have the same phone but am still on Android Oreo......I have the ALP-L29 8.0.0.141(C185) model. I'm reading more and more about others with this model that have gotten the Android Pie upgrade over the last two months but the upgrade is still not available to me. Makes no sense...I have a stock rom on the phone, I am NOT rooted and my bootloader is locked. Neither hisuite, hicare, system update, nor firmware finder methods gets me anywhere. They all say that I'm on the most recent firmware.... 8.0.0.141(C185). Go figure....
Click to expand...
Click to collapse
Same here, although my brother and I have the same device (ALP-L29C185) and we're on the same career, he got the pie update like a month ago and nothing for me yet. I think it's a matter of time until our imeis turns.
MasterThiefGarrett said:
How did you update @arianamirgholami ?
Click to expand...
Click to collapse
I used Erecovery of firmware finder
curgervending said:
Meanwhile, I have the same phone but am still on Android Oreo......I have the ALP-L29 8.0.0.141(C185) model. I'm reading more and more about others with this model that have gotten the Android Pie upgrade over the last two months but the upgrade is still not available to me. Makes no sense...I have a stock rom on the phone, I am NOT rooted and my bootloader is locked. Neither hisuite, hicare, system update, nor firmware finder methods gets me anywhere. They all say that I'm on the most recent firmware.... 8.0.0.141(C185). Go figure....
Click to expand...
Click to collapse
Yes I saw many people on internet facing same issue, What I assume is that when you purchased the phone it came with 8.0.0.141, that's why its not getting the Pie. Because the phones which were using 8.0.0.140 already got the Pie instead of 8.0.0.141. So one thing you can try is to go back to 8.0.0.140 and then update the phone. I did the same, Installed 8.0.0.140 using HiSuite and then update to Pie.
Fazee99 said:
Yes I saw many people on internet facing same issue, What I assume is that when you purchased the phone it came with 8.0.0.141, that's why its not getting the Pie. Because the phones which were using 8.0.0.140 already got the Pie instead of 8.0.0.141. So one thing you can try is to go back to 8.0.0.140 and then update the phone. I did the same, Installed 8.0.0.140 using HiSuite and then update to Pie.
Click to expand...
Click to collapse
I finally got the OTA update from EMUI 8 to EMUI 9
curgervending said:
I finally got the OTA update from EMUI 8 to EMUI 9
Click to expand...
Click to collapse
Thats great. Means you got more luck. Mine is still on 9.0.0.159 and no update. Please also confirm one thing. What is android security patch in this version?
Finally grab the update today morning...
Another update today. Woww
Hi everyone,
When EMUI 9 was first released on Firmware Finder, I've updated my phone with HuRupdate, since then, my phone model has changed from STF-L09C432 to
STF-LGRP2-OVS, since then, I'm stuck with the build 9.0.1.157, even though I've tried many time to flash another update or go back to EMUI 8 but I never managed to do it. I've tried with official recoveries, dload folder and it always failed, I've also tried flashing with TWRP, ADB, HWOTA or even MultiTool 8, but it never changed. Last time I tried flashing Kernel I've got an error saying that the file doesn't match the size or the path of the Partition. Have I done something wrong? Will I ever be Able to go back to EMUI 8? And If I ever manage to do it, Will I be able to receive official updates? I've seen that EMUI 9.1 was released as I saw a Honor 9 Lite with it and I want to upgrade to it as soon as possible
I'd be thankful if anyone can answer one of these questions!
I have Honor 9 STF-Al 10, with the System Emui 9.0.1.179
Due to some bugs, i intend to downgrade to Oreo.
it is said the phone will be hard brick by the method of HuRupdater.
the only way to downgrade to Oreo from Emui9 is Hisuite.
I heard about the HiSuite method, but when I go in the update menu it only tells me that i'm using the latest official version (which is wrong), and it doesn't show me any "switch to other version" button to downgrade the phone
Realiitysme said:
I heard about the HiSuite method, but when I go in the update menu it only tells me that i'm using the latest official version (which is wrong), and it doesn't show me any "switch to other version" button to downgrade the phone
Click to expand...
Click to collapse
should use the proper Hisuite version on PC （mine is 9.0.2.301）
there is an option to switch to Oreo
I'm using the same one, is it written somewhere which version is the right one or do I have to try and retry each version?
Realiitysme said:
I'm using the same one, is it written somewhere which version is the right one or do I have to try and retry each version?
Click to expand...
Click to collapse
you mean that your Hisuite is 9.0.2.301,
but still no option to switch to older Emui?
Exactly!
Not sure about If I should edit or double post but I thought that it also might be because my phone is Unlocked?
Wow I got exactly the same issue! Also STF-LGRP2-OVS but 162. No chance to downgrade!
I would be also fine with flashing a "normal" L09C432 version of EMUI but don't know how to..
Maybe if someone can post a TWRP Backup of EMUI 8.0 with no user data it could work since we can still have access to TWRP
Realiitysme said:
Maybe if someone can post a TWRP Backup of EMUI 8.0 with no user data it could work since we can still have access to TWRP
Click to expand...
Click to collapse
Firstly I'm gonna try to go back to a normal version, not this OVS crap. Maybe if you go to a normal STF-L09 Rom, Hisuite is offering you a rollback?
I don't even know how to do that to be honest. Shouldn't it be possible just with fastboot and a FF rom?
tesacrap said:
Firstly I'm gonna try to go back to a normal version, not this OVS crap. Maybe if you go to a normal STF-L09 Rom, Hisuite is offering you a rollback?
I don't even know how to do that to be honest. Shouldn't it be possible just with fastboot and a FF rom?
Click to expand...
Click to collapse
I've tried but didn't manage to do it, all I got was a bootloop but if you want to try it then go on, I've seen some EMUI 8 roms for STF-L09C432 here
Realiitysme said:
I've tried but didn't manage to do it, all I got was a bootloop but if you want to try it then go on, I've seen some EMUI 8 roms for STF-L09C432 here
Click to expand...
Click to collapse
You tried to flash the EMUI 8 rom directly, right? I would firstly flash a "regular" (no OVS) EMUI 9 Rom and then try to roll back with HiSuite. I'm probably gonna end up with flashing the regular EMUI 9, lock the Bootloader and sell that crappy phone to get a flashfriendly Xiaomi
tesacrap said:
You tried to flash the EMUI 8 rom directly, right? I would firstly flash a "regular" (no OVS) EMUI 9 Rom and then try to roll back with HiSuite. I'm probably gonna end up with flashing the regular EMUI 9, lock the Bootloader and sell that crappy phone to get a flashfriendly Xiaomi
Click to expand...
Click to collapse
Yup, you can still try to do it this way, if it works then tell me how you've done so I can do it
Careful
Realiitysme said:
Hi everyone,
When EMUI 9 was first released on Firmware Finder, I've updated my phone with HuRupdate, since then, my phone model has changed from STF-L09C432 to
STF-LGRP2-OVS, since then, I'm stuck with the build 9.0.1.157, even though I've tried many time to flash another update or go back to EMUI 8 but I never managed to do it. I've tried with official recoveries, dload folder and it always failed, I've also tried flashing with TWRP, ADB, HWOTA or even MultiTool 8, but it never changed. Last time I tried flashing Kernel I've got an error saying that the file doesn't match the size or the path of the Partition. Have I done something wrong? Will I ever be Able to go back to EMUI 8? And If I ever manage to do it, Will I be able to receive official updates? I've seen that EMUI 9.1 was released as I saw a Honor 9 Lite with it and I want to upgrade to it as soon as possible
I'd be thankful if anyone can answer one of these questions!
Click to expand...
Click to collapse
Be super careful downgrading to oreo because android P has rollback protection. I would recommend contacting HiCare and asking them to put you on EMUI 9.1. Although it's not a downgrade you might recieve and upgrade via OTA
Robert314 said:
Be super careful downgrading to oreo because android P has rollback protection. I would recommend contacting HiCare and asking them to put you on EMUI 9.1. Although it's not a downgrade you might recieve and upgrade via OTA
Click to expand...
Click to collapse
I was planning to roll back and the get the updates the official way but if I can have EMUI 9.1 and also have the official updates like that then it's okay too, but should I contact HiCare or Honor directly
It's been a while , I've contacted honor for my problem, they told me that they were going to send my request to a higher cell or something like that, it's been nearly one month and still no answer from them :/
Realiitysme said:
It's been a while , I've contacted honor for my problem, they told me that they were going to send my request to a higher cell or something like that, it's been nearly one month and still no answer from them :/
Click to expand...
Click to collapse
Try again with a correct dload package.
oslo83 said:
Try again with a correct dload package.
Click to expand...
Click to collapse
And how do I know if my dload package is correct?
Realiitysme said:
And how do I know if my dload package is correct?
Click to expand...
Click to collapse
use a dload meant for C432 with a build version superior of the one you actually are.
Try https://androidhost.ru/TTy
use a working SD or usb-otg ExFAT formated
(test for error with h2testw windows app or with f3 osx/linux)
use stock recovery
boot dload mode
Hello everyone!
I spent the last few days trying to flash a stock emui 9 or 9.1 version to my Mate20Pro (C432) because my carrier notified me, that the emui 10 update is officially available.
I was finally able to go to version . 347 by following this guide: click
A few hours later I was offered the emui 10 update and it installed well.
The exact build nr is now: 10.0.0.154(C432E7R1P5patch01)
Only thing left: Root access.
And here's where the problems start:
The Bootloader was relocked somewhere down the road (the update to .347 probably). Now, I've had this issue before, jumping back and forth between ROMs, but was always able to re-unlock my bootloader with my code I got from funkyhuawei (back in the days).
Now when I try to unlock it now, following this procedure:
- turn usb debugging on
- confirm to always trust my computer
- open console - adb devices: I see my device.
- adb reboot bootloader: reboots the phone gracefully
- reached fastboot mode - bootloader lock confirmed. frp locked: no
- in terminal: fastboot devices: check
- fastboot oem unlock xxxxx
--> here i get following output:
Failed. Invalid command.
Has anyone also had this issue? is this some kind of security mechanism (did they change the unlock code?) Or did they chamge the fastboot command set?
What I've checked so far:
- usb drivers are installed (reinstalled them even)
- hisuite is installed (also tried it with uninstalling first)
- terminal is running as admin
- tried different usb cables
- googling
I would really appreciate all thoughts, ideas or experiences with this issue.
Thanks in advance!
On EMUI10 (at least early builds), it's normal behavior.
It's seem that oem unlock's fastboot command was made invalid or was modified...
It's told rolling back to emui9 B346 or B347 will open bootloader back or at least will enable back fastboot and old oem unlock commands.
Does magisk creator @topjohnwu achieved something related to emui10 ?
c4ph4lor said:
Hello everyone!
I spent the last few days trying to flash a stock emui 9 or 9.1 version to my Mate20Pro (C432) because my carrier notified me, that the emui 10 update is officially available.
I was finally able to go to version . 347 by following this guide: click
A few hours later I was offered the emui 10 update and it installed well.
The exact build nr is now: 10.0.0.154(C432E7R1P5patch01)
Only thing left: Root access.
And here's where the problems start:
The Bootloader was relocked somewhere down the road (the update to .347 probably). Now, I've had this issue before, jumping back and forth between ROMs, but was always able to re-unlock my bootloader with my code I got from funkyhuawei (back in the days).
Now when I try to unlock it now, following this procedure:
- turn usb debugging on
- confirm to always trust my computer
- open console - adb devices: I see my device.
- adb reboot bootloader: reboots the phone gracefully
- reached fastboot mode - bootloader lock confirmed. frp locked: no
- in terminal: fastboot devices: check
- fastboot oem unlock xxxxx
--> here i get following output:
Failed. Invalid command.
Has anyone also had this issue? is this some kind of security mechanism (did they change the unlock code?) Or did they chamge the fastboot command set?
What I've checked so far:
- usb drivers are installed (reinstalled them even)
- hisuite is installed (also tried it with uninstalling first)
- terminal is running as admin
- tried different usb cables
- googling
I would really appreciate all thoughts, ideas or experiences with this issue.
Thanks in advance!
Click to expand...
Click to collapse
Were you able to unlock bootloader or downgrade to 9.1 with locked bootloader or fix this issue by any means?
You can rollback to 9.1 using stock hisuite.
If rollback prompt is not shown, you can trigger it with 'Hisuite launcher' from Magnot.
oslo83 said:
You can rollback to 9.1 using stock hisuite.
If rollback prompt is not shown, you can trigger it with 'Hisuite launcher' from Magnot.
Click to expand...
Click to collapse
I tired stock hisuite, but it says does not support.
sharath91221 said:
I tired stock hisuite, but it says does not support.
Click to expand...
Click to collapse
Rollback link is shown from Hisuite 's update option, not from Hisuite' s recovery option.
thank you for the heads up about rooting and emui 10, i have been tempted to try it for myself but had to much to do at home and at work, but i will wait a bit more.
also: dload version will always lock the bootloader
I was able to install CUST and PRELOAD for lya-l09 emui 10 using dload method and it fixed the issue. Thank you.
Check oem option in developer settings.It must be enabled
farizazizov said:
Check oem option in developer settings.It must be enabled
Click to expand...
Click to collapse
thanks yes the obvious-not the issue though (same issue on mate 20 x evr-l29) cannot unlock bootloader (same failed command issue) after emui 10 upgrade (went through an update as well)
---------- Post added at 09:09 PM ---------- Previous post was at 09:09 PM ----------
sharath91221 said:
I was able to install CUST and PRELOAD for lya-l09 emui 10 using dload method and it fixed the issue. Thank you.
Click to expand...
Click to collapse
could you elaborate please? (explain in detail) thanks
mac231us said:
thanks yes the obvious-not the issue though (same issue on mate 20 x evr-l29) cannot unlock bootloader (same failed command issue) after emui 10 upgrade (went through an update as well)
---------- Post added at 09:09 PM ---------- Previous post was at 09:09 PM ----------
could you elaborate please? (explain in detail) thanks
Click to expand...
Click to collapse
I have funkyhuawei account but still that was unable fix the issue. So what i did was:
I choose 365 ver in funkyhuawei website and tried flashing it using modded hisuite. When it downloaded the firmware i replaced the 365 firmware files like CUST AND PRELOAD with EMUI 10 version, it failed at the beginning. I keep on retrying multiple times and final it flashed CUST and PRELOAD and my system booted with EMUI 10 .
sharath91221 said:
I have funkyhuawei account but still that was unable fix the issue. So what i did was:
I choose 365 ver in funkyhuawei website and tried flashing it using modded hisuite. When it downloaded the firmware i replaced the 365 firmware files like CUST AND PRELOAD with EMUI 10 version, it failed at the beginning. I keep on retrying multiple times and final it flashed CUST and PRELOAD and my system booted with EMUI 10 .
Click to expand...
Click to collapse
Do you have the link or if you could upload please the modded hisuite? Appreciate it.
EDIT
So in the dload folder, you used the main update zip from the 9.1 (365) and the custom and preload zips from emui 10? Thanks. (asking also since you say you booted in emui 10 even though from what you have described you seem to have had the main update zip in 9.1...or was it the other way around?)
(I tried-though on mate 20x and the software installation failed-restart-so is that what you tried many times? (in the erecovery update through card/otg option?)
Highly appreciate your clarification here (might just help me get out of this emui10 mess)
mac231us said:
Do you have the link or if you could upload please the modded hisuite? Appreciate it.
EDIT
So in the dload folder, you used the main update zip from the 9.1 (365) and the custom and preload zips from emui 10? Thanks. (asking also since you say you booted in emui 10 even though from what you have described you seem to have had the main update zip in 9.1...or was it the other way around?)
(I tried-though on mate 20x and the software installation failed-restart-so is that what you tried many times? (in the erecovery update through card/otg option?)
Highly appreciate your clarification here (might just help me get out of this emui10 mess)
Click to expand...
Click to collapse
Modded hisuite only work, if you have funkyhuawei account and required credits for that account.
Yes, thats correct i used main update.zip is from 9.1 and custom and preload are from emui 10.
Currently your mobile already have emui 10(update.zip). But when mobile boots it goes through custom and preload and then it loads Operating System(emui 10).
In order to fix it . You need to load custom and preload for supporting emui 10.
If you have a regular hisuite, try erecovery mode.
Hisuite will download a package(update.zip, custom.zip and preload.zip) in documents folders if you are using Windows system. Once it downloads them, it will unzip those files and then it starts flashing customs, preload and then update(in this order). You need to figure out a way, to replace custom and preload folder with emui 10 files before Hisuite start flashing them.
so, since bootloader unlock is not longer possible with emui 10 i will give the phone to one of my kids so it will be a youtube interface, myself ordered a s20+ and hopefully samsung will treat me right.
Hi guys,
I been trying some GSI roms lately and unfortunately I can't get the fingerprint to work on any of them... if any of you guys can source me the fingerprint line value inside BUILD.PROP would be a good help for me but the thing is I don't have much hope that it will work so I want to downgrade to 9.0 and then to 8.0. Via HiSuite the 'older version' doesn't show up, via dload the 'software failed' pops up... but via HRupdater in TWRP I have one update.zip that might lock the bootloader, it can really lock my bootloader?
bejarj said:
Hi guys,
I been trying some GSI roms lately and unfortunately I can't get the fingerprint to work on any of them... if any of you guys can source me the fingerprint line value inside BUILD.PROP would be a good help for me but the thing is I don't have much hope that it will work so I want to downgrade to 9.0 and then to 8.0. Via HiSuite the 'older version' doesn't show up, via dload the 'software failed' pops up... but via HRupdater in TWRP I have one update.zip that might lock the bootloader, it can really lock my bootloader?
Click to expand...
Click to collapse
Not real is now(((
Downgrading risks bricking especially with what Huawei have done basically ensuring EMUI 9 to EMUI 8 is a bricked device