Hi, i have new honor 9, as i open the phone , it is upgrade to B183 Version.
i need to automatic call recorder and i have found a zip.file to flash whit twrp. So i want install twrp and root...
The first time i download TWRP 3.1.1-1 and Supersu 2,82, i install all whit my zip file per automatic call recorder...
all is ok, twrp, i have root and call recorder working,,, but...
I lose navigation buttons and Camera Flash.
for navigation buttons isnt a problem... i can use only Home button ( i had a Meizu phone before but...
I need camera flash ! it have to work.
so....
for have again all working , i used the Rebrand Guide of HWOTA, whit B120 all work again.
cannot have more OTA upgraded but i think because i just had download them whit my imei.... ok i will wait new update for verifyng it.
I can use Finder Firmware Huawey for have manual upgrade.
Now i'm again in b183.
how can I do now for have a valid twrp or valid method for root phone? Because i read that same people have them..... but i think have reroll to b120 almost 50 time whithout always same results....
oh oh, i see now that i have wrong section. moderator can you move?
SOLVED!
After many time i can have all working now:
Starting to B183 firmware whit button and flash not working:
Step 1) Rollback on B120, downgrading by flashing with hwota scripts, this post . option are 2 (directory upgrade) and 1 (same brand). with this you will have working buttons
Step 2) Update to B183 (FF full-ota files timestamped 2017.12.28)
Step 3) Unlock the bootloader.
Step 4) Install the TWRP-3.1.1.1_120_130_170.img from this thread.
Step 5) Install Supersu SR5
WARNING: you have to be carefull when go in TWRP recovery: do not modify system data at twrp's boot, then rebooted choosing not to install twrp at twrp's exit prompt. ( dont'know if it is important... but so it work
so you will have a b183 firmware whit all working: root, button and flash.
please, reply if this work for you.
Add more infos about FF .
In updater system , no update available after roolback to B120.
Need to use Firmware Finder Huawei on Playstore.
1-Choose the desired full version
2-Check Firmware access for be sure not make mistakes.
3-Get an update throught DNs , register update and change Dns .
4- Come back to updater and check update .
angelobiz said:
Step 2) Update to B183 (FF full-ota files timestamped 2017.12.28)
Click to expand...
Click to collapse
In this step, did you do it with the HWOTA tool or with fully stock B120 inside the system?
Zuzler said:
In this step, did you do it with the HWOTA tool or with fully stock B120 inside the system?
Click to expand...
Click to collapse
While on stock B120 use the android application Huawei Firmware Finder to upgrade:
https://forum.xda-developers.com/tools/general/huawei-firmware-finder-team-mt-t3469146/amp/
But you could try to test to use HWOTA to upgrade from b120 to b183 and then report here?
I already tried upgrading to B182/183 with HWOTA. I was on B120 and did a B182 and B183 upgrade. I was left with no capacitive keys and no flash. Camera was working however.
Just right now downloading B183 on top of a new locked B120 with the Firmware Finder, will report back.
However, it's very inconvenient to update the system this way if you have an unlocked bootloader and are rooted. I mean, downgrade to B120, twice within HWOTA, upgrade within the system and then AGAIN re-unlock the bootloader which results in a factory reset - come on...
Does it also work with Magisk or only with SuperSu?
SuperSu already is nice, but the additional benefits like would be nice to have, especially passing SafetyNet.
Anyone still with missing navigation buttons? I might have a solution that does not require flashing firmware or doing factory reset
zxz0O0 said:
Anyone still with missing navigation buttons? I might have a solution that does not require flashing firmware or doing factory reset
Click to expand...
Click to collapse
Mind telling us?
For me everything worked fine by downgrading to B120 and then updating B183 through the OS.
Zuzler said:
Mind telling us?
For me everything worked fine by downgrading to B120 and then updating B183 through the OS.
Click to expand...
Click to collapse
Seems the problem is that the touch_key firmware is not flashed properly. I modified the TWRP recovery to include the firmware. After I rebooted once into the custom TWRP the buttons worked again.
zxz0O0 said:
Seems the problem is that the touch_key firmware is not flashed properly. I modified the TWRP recovery to include the firmware. After I rebooted once into the custom TWRP the buttons worked again.
Click to expand...
Click to collapse
Good. This might be a breakthrough. Could you please share a step by step guide what to do? Thanks.
zxz0O0 said:
Seems the problem is that the touch_key firmware is not flashed properly. I modified the TWRP recovery to include the firmware. After I rebooted once into the custom TWRP the buttons worked again.
Click to expand...
Click to collapse
good, can you share your modified TWRP recovery???
the solution not work if you do different. you have to downgrade to B120 to HWOTA whit file of its post. After have to upgrade to B183 whit FFH whit locked bootloader
ang stock recovery, after install twrp and supersu.
i dont know why, but so it work.
angelobiz said:
good, can you share your modified TWRP recovery???
the solution not work if you do different. you have to downgrade to B120 to HWOTA whit file of its post. After have to upgrade to B183 whit FFH whit locked bootloader
ang stock recovery, after install twrp and supersu.
i dont know why, but so it work.
Click to expand...
Click to collapse
It would be a good thing.
Edit : As we are all trying to make your device 100% functional with root.
Here is a link for a Su Emui , not testes yet. Work on the mosty Huawei devices
https://forum.xda-developers.com/p9/development/root-supersu-2-81-emui-5-t3612258
http://www.mediafire.com/file/pn2pv1rqih1ug81/SuperSU-v2.82-EMUI5-SELPermissive[1].zip
https://androidfilehost.com/?fid=673956719939815322
I had used this version and it work
https://forum.xda-developers.com/apps/supersu/2014-09-02-supersu-v2-05-t2868133
zxz0O0 said:
Seems the problem is that the touch_key firmware is not flashed properly. I modified the TWRP recovery to include the firmware. After I rebooted once into the custom TWRP the buttons worked again.
Click to expand...
Click to collapse
Can you provide details?
I wonder if we can pull the touch_key firmware from a working B120 firmware and flash over a later version?
angelobiz said:
I had used this version and it work
https://forum.xda-developers.com/apps/supersu/2014-09-02-supersu-v2-05-t2868133
Click to expand...
Click to collapse
Now i'm ok .
I used the good twrp and sideloaded Supersu.sr3 .
All buttons and flashlight work nice
zxz0O0 said:
Seems the problem is that the touch_key firmware is not flashed properly. I modified the TWRP recovery to include the firmware. After I rebooted once into the custom TWRP the buttons worked again.
Click to expand...
Click to collapse
So did your twrp fix touch_key once broken?
zxz0O0 said:
Seems the problem is that the touch_key firmware is not flashed properly. I modified the TWRP recovery to include the firmware. After I rebooted once into the custom TWRP the buttons worked again.
Click to expand...
Click to collapse
Can you please share your modified TWRP recovery, so we can test on our phones?
This issue is driving me crazy.
Thanks :good:
Related
Hi.
The last couple days, I unlocked my bootloader to install the phh-treble rom and experiment with this phone but the *unlocked bootloader* message every time that I power up my phone, is very annoying.
So I ask if anyone knows which firmware to install to my phone so I can lock the bl and receive otas as normal
Thanks
t-shock said:
Hi.
The last couple days, I unlocked my bootloader to install the phh-treble rom and experiment with this phone but the *unlocked bootloader* message every time that I power up my phone, is very annoying.
So I ask if anyone knows which firmware to install to my phone so I can lock the bl and receive otas as normal
Thanks
Click to expand...
Click to collapse
It's just a guess, but i think that you should flash an original "system. img" with fastboot and then reset you device.
You can use Huawei Unpacker to get your system.img from a FullOTA firmware (you can download it with Firmware Finder).
Pretoriano80 said:
It's just a guess, but i think that you should flash an original "system. img" with fastboot and then reset you device.
You can use Huawei Unpacker to get your system.img from a FullOTA firmware (you can download it with Firmware Finder).
Click to expand...
Click to collapse
Thanks for that
But having used this guide ( https://forum.xda-developers.com/mate-10/how-to/guide-mate-10-flash-oreo-update-package-t3716814 ) I guess it changes more that the system
t-shock said:
Thanks for that
But having used this guide ( https://forum.xda-developers.com/mate-10/how-to/guide-mate-10-flash-oreo-update-package-t3716814 ) I guess it changes more that the system
Click to expand...
Click to collapse
When you go to recovery now, is it Huawei recovery or some aosp recovery?
If Huawei you should be able to use that same guide to go back to stock. You just need to download the Firmware your phone came with (Ex. L29 C432), then update using the guide. Or you could rebrand and install fw.
ante0 said:
When you go to recovery now, is it Huawei recovery or some aosp recovery?
If Huawei you should be able to use that same guide to go back to stock. You just need to download the Firmware your phone came with (Ex. L29 C432), then update using the guide. Or you could rebrand and install fw.
Click to expand...
Click to collapse
It is the Huawei recovery but the weird thing is that it flashes another recovery and kernel before at the fastboot mode.
Anyhow, I just wonder, if I go back to the 127 (following the method above) which is verified thru IMEI, will I be able to get OTAs?
Or
Which is the correct method of restoring the full stock rom in order to have OTAs and lock the BL
t-shock said:
It is the Huawei recovery but the weird thing is that it flashes another recovery and kernel before at the fastboot mode.
Anyhow, I just wonder, if I go back to the 127 (following the method above) which is verified thru IMEI, will I be able to get OTAs?
Or
Which is the correct method of restoring the full stock rom in order to have OTAs and lock the BL
Click to expand...
Click to collapse
Yes, you will get OTA.
If you install a full firmware everything will be replaced (though you can keep bootloader unlocked, but you're asked when you run repack so select yes ("Lock bootloader?").
The "correct" ways would be: HWOTA8, Dload (if available for your firmware), FunkyHuawei (paid).
ante0 said:
Yes, you will get OTA.
If you install a full firmware everything will be replaced (though you can keep bootloader unlocked, but you're asked when you run repack so select yes ("Lock bootloader?").
The "correct" ways would be: HWOTA8, Dload (if available for your firmware), FunkyHuawei (paid).
Click to expand...
Click to collapse
Thanks a lot
Just one last question, if I only have unlocked bootloader and no root , will AI "brake"?
Thanks
t-shock said:
Thanks a lot
Just one last question, if I only have unlocked bootloader and no root , will AI "brake"?
Thanks
Click to expand...
Click to collapse
It shouldn't. And it works again with root. Apparently something broke in SEPolicy, but mankindtw fixed it in his pre-rooted ramdisk. Though, we can install Magisk "normally" now (as a package through recovery) so it shouldn't be a problem anyway SuperSU should install in a similar way too, if one would take the time to make it. I prefer Magisk though
So I was on honor 9 stf-l09c432b182 with openkirins twrp and had sideloaded Supersu and everything was working fine.
My plan was to uninstall root, flash stock recovery and upgrade to B183.
So I uninstalled supersu, flashed the recovery.img and recovery2.img in fastboot.
Then I tried to install B183 with the system updater of emui. Failed in the middle of the process.
So then I tried to manually flash system.img, cust.img, recovery.img, recovery2.img, boot.img(basically everything that doesn't give the error: remote command not allowed)
from B183 and when I rebooted i had a really weird version number( similar to this: https://forum.xda-developers.com/honor-9/help/strange-version-t3699280).
Now heres the part where I probably bricked some stuff: I was really concerned and tried to flash my old B180 firmware and then my device is stuck at the screen: Your device can't be trusted...
(http://s1.postimg.org/yilteiv0f/bab3a651_1dcc_4073_88ec_8172118b7227.jpg)
Your device is booting now.
I tried to relock and unlock the bootloader, but does not work.
Tried: fastboot oem lock, fastboot oem relock, fastboot flashing lock
Now current status:
I can boot into bootloader via volume down+ plug in.
Oem and frp are unlocked.
I can hold down volume up and go into erecovery but trying to install something from there didn't work.
I can charge my phone.
Something similar happened to this guy here: https://forum.xda-developers.com/honor-8/help/stuck-device-booting-t3650016 but he was lucky to find someone who repaired it for him.
I would thank you all soo much if you could help me, or just give me a tip what I can do.
Thanks for all replies
You should try to full restore to service repair stock working firmware with sdcard :
https://forum.xda-developers.com/honor-9/development/firmware-huawei-honor-9-stf-l09-stock-t3696892
Alternatively, you could try to downgrade to stock firmware without rebrandind (no sdcard needed) :
https://forum.xda-developers.com/honor-9/how-to/guide-honor-9-t3653719
I think that Rebrand method is the best way for this situation.
Dload with B130 dont help , its happen to me.
If boot after Rebrand method , let it restart several times.
Erecovery will appear then made wipe data/ factory reset.
If dont work again , Erecovery , wipe cache partition.
We can not rollback and upgrade as we want with Huawei..
All done step by step . But work for B120.
k1ks said:
I think that Rebrand method is the best way for this situation.
Dload with B130 dont help , its happen to me.
If boot after Rebrand method , let it restart several times.
Erecovery will appear then made wipe data/ factory reset.
If dont work again , Erecovery , wipe cache partition.
We can not rollback and upgrade as we want with Huawei..
All done step by step . But work for B120.
Click to expand...
Click to collapse
Which version should I use for rebrand ? B120 ?
If yes, I cant find any download links for B120 zips.
Thanks for your reply.
https://yadi.sk/d/Y2yuM--73Lb9Kk
This link
k1ks said:
https://yadi.sk/d/Y2yuM--73Lb9Kk
This link
Click to expand...
Click to collapse
Ok thank you so much my phone is now working again on B120, what a trip!
Lukalion said:
Ok thank you so much my phone is now working again on B120, what a trip!
Click to expand...
Click to collapse
Youre welcome , , a little spicy huawei.
I had the same mishap.
I think we have to wait for a possible fix of the twrp , nothing is stable at the moment.
Too much random behavior.
Lukalion said:
Ok thank you so much my phone is now working again on B120, what a trip!
Click to expand...
Click to collapse
So which file you used for that? I downloaded all three files from that yandex link. What to do now? I tried many different things up to now and everytime the update failed via that installer at 5%.
Freakeee93 said:
So which file you used for that? I downloaded all three files from that yandex link. What to do now? I tried many different things up to now and everytime the update failed via that installer at 5%.
Click to expand...
Click to collapse
These B120 are unaproved, so to install them you need a no-check recovery.
Follow this guide while skipping step 7 :
https://forum.xda-developers.com/honor-9/how-to/guide-honor-9-t3653719
oslo83 said:
These B120 are unaproved, so to install them you need a no-check recovery.
Follow this guide while skipping step 7 :
https://forum.xda-developers.com/honor-9/how-to/guide-honor-9-t3653719
Click to expand...
Click to collapse
But that HWOTA.zip is not available anymore. So I did't knew what to do.
Edit: Found it... It's edited from the mod. Am trying if the download is ready.
It works again!!!! Great and thank you for your help!:good::good::good:
Hi guys,
Probably been discussed before, but I couldn't find all the answers I need.
I have honor 9 STF-L09, version STF-L09C432B100.
The phone bootloader is unlocked, rooted and have TWRP recovery.
Sorry for the muiltiple questions.....
I want to update it to the latest stock ROM (I have no problem wiping the memory).
I thought about using HuRUpdater tool, is that the best method?
I couldn't find a 'Global' ROM version, which should I choose?
Will I have to do incremental update with this tool?
Do I must change the recovery to this one? is there a better version? Do I need the capacitive touch fix (I didn't have any problem with capacitive touch).
Any help is appreciated.
Thank you
They 're no public nougat proper recovery working with HuRUpdater. The one you linked is for oreo.
So i guess you'll have to :
- flash back STF-L09C432B100 stock recovery
- then update tje normal way to oreo via OTA
- if not getting OTA, you could force it with android apps 'Firmware Finder' to update to STF-L09C432B183. Then you should finally got the normal OTA update to STF-L09C432B364.
This process should not mess with your flashlight or caoacitives buttons.
oslo83 said:
They 're no public nougat proper recovery working with HuRUpdater. The one you linked is for oreo.
So i guess you'll have to :
- flash back STF-L09C432B100 stock recovery
- then update tje normal way to oreo via OTA .
.
Click to expand...
Click to collapse
I am already on B100 and its recovery.
Since I'm rotted with TWRP I can't get OTAs (I do but it doesn't work)
What is "tje"?
oslo83 said:
- if not getting OTA, you could force it with android apps 'Firmware Finder' to update to STF-L09C432B183. Then you should finally got the normal OTA update to STF-L09C432B364.
.
Click to expand...
Click to collapse
Can you please elaborate, I have no idea what you're talking about and how do I force OTA?
Thanks
I think "tje" is just "the" . I think you have to start with clean device : stock rom ( in this case stock recovery too : flash back STF-L09C432B100 stock recovery ) and update with Firmware Finder, to 183 first, 364 after.
ADD : for me, just my way, don't hurt me if I'm wrong : ) I open FF, select correct rom , hit button " get an update trough dns " " auto", go to parametre / update , system find the update, go back to FF, close it, update still DL, sometimes , when finish , update can't start, so I reboot my device, return to parametre / update and it's ok.
Clonimus said:
I am already on B100 and its recovery.
Since I'm rotted with TWRP I can't get OTAs (I do but it doesn't work)
Click to expand...
Click to collapse
twrp is a custom recovery and you need to have a stock recovery for OTA update to work.
So : 'flash back STF-L09C432B100 STOCK recovery'
You could get it by using windows app 'Huawei Update Extractor' on the file 'Update.app' included inside the firmware file 'update.zip' 's STF-L09C432B100.
Don't mind your root access: you'll loose it during the update.
Clonimus said:
What is "tje"?
Click to expand...
Click to collapse
just a typo in place of 'the' ; like your 'rotted' in place of 'rooted'
Clonimus said:
Can you please elaborate, I have no idea what you're talking about and how do I force OTA?
Thanks
Click to expand...
Click to collapse
Because you state that you're getting the OTA notifications : You won't have to FORCE them. So don't bother.
oslo83 said:
twrp is a custom recovery and you need to have a stock recovery for OTA update to work.
So : 'flash back STF-L09C432B100 STOCK recovery'
You could get it by using windows app 'Huawei Update Extractor' on the file 'Update.app' included inside the firmware file 'update.zip' 's STF-L09C432B100.
Don't mind your root access: you'll loose it during the update.
just a typo in place of 'the' ; like your 'rotted' in place of 'rooted'
Because you state that you're getting the OTA notifications : You won't have to FORCE them. So don't bother.
Click to expand...
Click to collapse
So you're saying I need to extract the stock recovery and flash it using fastboot. /then I will update normaly via OT to the latest version.
Then I need to re-root and reinstall the custom recovery.
Did I understand you correctly?
Where can I find the STF-L09C432B100 firmware?
Many thanks
Yes.
Yes.
Yes. https://yadi.sk/d/Y2yuM--73Lb9Kk/update.zip
It's C432B120 but its stock recovery is the same as B100.
Thank you all.
I flashed the stock recovery and managed to OTA update all the way to the most recent version.
Now I need to find which custom recovery is appropriate for new version
@Clonimus :
https://forum.xda-developers.com/showpost.php?p=75680308
oslo83 said:
@Clonimus :
https://forum.xda-developers.com/showpost.php?p=75680308
Click to expand...
Click to collapse
Thanks. I did that, it works
I already asked in the post you linked. bit do you knwo what's the difference between "fastboot flash recovery" and "fastboot flash recovery_ramdisk"?
I did as instructed in the OP ("fastboot flash recovery_ramdisk"), but I can't load TWRP from power off using power button + down button.
TWRP does load when using "adb reboot recovery_ramdisk". Is that the reason?
Clonimus said:
but I can't load TWRP from power off using power button + down button.
Click to expand...
Click to collapse
wrong keys combo for recovery mode on huawei/honor phones :
From power off, using power button + up button will give you recovery mode.
oslo83 said:
wrong keys combo for recovery mode on huawei/honor phones :
From power off, using power button + up button will give you recovery mode.
Click to expand...
Click to collapse
LOL, my bad. Thanks
Hey everyone,
last month I unlocked and rooted my phone, then used this tool to put on the newest firmware (at the time 366). Now, I'd like to update to the newest firmware (368). Is there anything special I need to do or can I just dirty flash it per see? Do I use the FullOTA-MF files or the OTA-MF files?
Thanks in advance for your help.
Hi all.
Honor 9 with unlocked bootloader and FRP. I'm on 8.0.0.366, rooted via Magisk's modded ramdisk and stock recovery.
AFAIK Otas should not work anymore.
According to Huawei Firmware Finder, OTA update to .368 is available and approved for my IMEI.
I tried to upgrade putting main update.app file (from the full-ota-mf) in SDCARD\dload and booting in software update mode. Process fails with software update error at 5%.
Same with 367.
Furthermore there are multiple update.app in the downloadable files, how to flash all updates?
Is there a way to manually upgrade the phone without factory resetting it?
I would avoid installing a custom recovery, maybe in beta.
I'm also comfortable with bare fastboot, could I flash all needed images just skipping data?
Thanks
I had the same problem with update.
I used this tutorial https://forum.xda-developers.com/honor-9/how-to/how-to-root-honor-9-stf-l09c432b360a-t3778110 and flashed newest official ROM and Proto 8 kernel and it's awesome.
You can backup your data with hisuite and recover after fleshing. Worked for me very well.
procent said:
I had the same problem with update.
I used this tutorial https://forum.xda-developers.com/honor-9/how-to/how-to-root-honor-9-stf-l09c432b360a-t3778110 and flashed newest official ROM and Proto 8 kernel and it's awesome.
You can backup your data with hisuite and recover after fleshing. Worked for me very well.
Click to expand...
Click to collapse
Yep, I did the same. Got from b360 to b369 without factory reset. No issues.
1. TWRP 2. HuRUpdater with b369 from Firmware Finder 3. Magisk 4. Proto8 kernel+Split injector
All flashed from TWRP. TWRP flashed from fastboot. The same TWRP was renamed and put in the HuRUpdater folder.
sinraal said:
Yep, I did the same. Got from b360 to b369 without factory reset. No issues.
1. TWRP 2. HuRUpdater with b369 from Firmware Finder 3. Magisk 4. Proto8 kernel+Split injector
All flashed from TWRP. TWRP flashed from fastboot. The same TWRP was renamed and put in the HuRUpdater folder.
Click to expand...
Click to collapse
Just a bit curious....what is "split injector"??
Also HiSuite has option to upgrade and it worked for me.
badadam said:
Just a bit curious....what is "split injector"??
Click to expand...
Click to collapse
My bad, it is Spectrum injector and it is explained in the proto8 kernel thread.
sinraal said:
My bad, it is Spectrum injector and it is explained in the proto8 kernel thread.
Click to expand...
Click to collapse
Aha! OK, thanks for the reply
buteo said:
Hi all.
Honor 9 with unlocked bootloader and FRP. I'm on 8.0.0.366, rooted via Magisk's modded ramdisk and stock recovery.
AFAIK Otas should not work anymore.
Click to expand...
Click to collapse
OTA still should work with stock recovery, don't matter magisk
buteo said:
According to Huawei Firmware Finder, OTA update to .368 is available and approved for my IMEI.
I tried to upgrade putting main update.app file (from the full-ota-mf) in SDCARD\dload and booting in software update mode. Process fails with software update error at 5%.
Same with 367.
Furthermore there are multiple update.app in the downloadable files, how to flash all updates?
Click to expand...
Click to collapse
SDCARD\dload won't work with update.app from Full-ota-mf ; maybe the full-ota-mf-pv but it's not sure. I believe it only work in firmware mode (dload) with 'service repair firmware'.
buteo said:
Is there a way to manually upgrade the phone without factory resetting it?
Click to expand...
Click to collapse
normal ota(IF WORKING) or 'HuRUpdater + twrp'
hello, my miA3 was in V10.3.17.0.PFQEUXM, and i had some troubles with it after trying to root with magisk because of a wrong boot.img, and i lost wifi.
since I couldn't find a V10.3.17.0.boot.img to flash and get back wifi, i try to find some escape plan and finally i succeed to install twrp and then official V11.0.8.0 , but i would like to go back to V10.3.15.0 and root it ( or 10.3.17.0 if someone have the good boot.img ), is it possible?
Just download fastboot rom and you are good to go
arjo656 said:
hello, my miA3 was in V10.3.17.0.PFQEUXM, and i had some troubles with it after trying to root with magisk because of a wrong boot.img, and i lost wifi.
since I couldn't find a V10.3.17.0.boot.img to flash and get back wifi, i try to find some escape plan and finally i succeed to install twrp and then official V11.0.8.0 , but i would like to go back to V10.3.15.0 and root it ( or 10.3.17.0 if someone have the good boot.img ), is it possible?
Click to expand...
Click to collapse
If you want to keep your sensors and DRM working, follow this guide:
https://forum.xda-developers.com/showpost.php?p=82110807&postcount=224
amnher said:
Just download fastboot rom and you are good to go
Click to expand...
Click to collapse
ok,do you have a link with DL and tuto step by step?
_mysiak_ said:
If you want to keep your sensors and DRM working, follow this guide:
https://forum.xda-developers.com/showpost.php?p=82110807&postcount=224
Click to expand...
Click to collapse
thanks (again ) mysiak, the steps are clear but there is no link for dl any of the rom he's talking
edit : i downloaded a rom 10.3.15.0 here https://forum.xda-developers.com/mi-a3/how-to/rom-xiaomi-mi-a3-laurelsprout-t3962489, but when i double click on flash_all.bat nothing happends
arjo656 said:
thanks (again ) mysiak, the steps are clear but there is no link for dl any of the rom he's talking
edit : i downloaded a rom 10.3.15.0 here https://forum.xda-developers.com/mi-a3/how-to/rom-xiaomi-mi-a3-laurelsprout-t3962489, but when i double click on flash_all.bat nothing happends
Click to expand...
Click to collapse
Run the script from terminal window, it will show you an error message why it fails.
arjo656 said:
hello, my miA3 was in V10.3.17.0.PFQEUXM, and i had some troubles with it after trying to root with magisk because of a wrong boot.img, and i lost wifi.
since I couldn't find a V10.3.17.0.boot.img to flash and get back wifi, i try to find some escape plan and finally i succeed to install twrp and then official V11.0.8.0 , but i would like to go back to V10.3.15.0 and root it ( or 10.3.17.0 if someone have the good boot.img ), is it possible?
Click to expand...
Click to collapse
Guys, I did the update for android 10 in the second wave.
after trying to return to android 9 my device got stuck resetting the "android one" home screen, as there was no solution i put the "pixel" rom for mi a3.
Today as a test again I tried to flash the rom stock 9 and everything went back to normal as it was before, with everything working.
I believe that after installing "PIXEL" something made it back to normal.
alexjmachado said:
Guys, I did the update for android 10 in the second wave.
after trying to return to android 9 my device got stuck resetting the "android one" home screen, as there was no solution i put the "pixel" rom for mi a3.
Today as a test again I tried to flash the rom stock 9 and everything went back to normal as it was before, with everything working.
I believe that after installing "PIXEL" something made it back to normal.
Click to expand...
Click to collapse
yes , that's what sapper morton explained in a other post:
" I received Android 10 as an OTA 29th February, and a couple of days later I updated to v11.0.8.0 (locked bootloader); but I didn't enjoy it overall, so I did install Magisk, after a couple of days, I downgraded to Pie (March firmware); I lost my sensors, did try a couple of things, none of them solved the issue.
I knew from the beginning I could have flashed persist.img, but then again, I would've lost my DRM Keys (Widevine), thus I updated to Android 10 Stock (recovery firmware) to regain my sensors.
After a little search I read that downgrading from a custom Android 10 ROM (PX in my case) solves the issue on Pie, I tried and the sensors started working again on Android 9 Stock, without losing Widevine L1, since persist partition was intact. "
So my steps to solve the issue was as it follows:
1• Flashed Android 10 Stock (sensors working) [Recovery]
2• Flashed Android 9 Stock (sensors not working) [Fastboot]
3• Flashed Android 10 custom (sensors working) [Recovery]
4• Flashed Android 9 (sensors working) [Fastboot]
hello all
is there any download link to "3• Flashed Android 10 custom (sensors working) [Recovery]" or do you recommend a specific custom rom ?
I want to do the downgrade right