I almost resorted to unlocking the bootloader of my Huawei Mate 9
So my friend and I swapped phone. I gave him my Huawei P9 and he gave me his Mate 9. The unit's stuck on EMUI 5 / Android 7. I know that later updates have been around for quite some time now. First, I tried searching for updates through the system updater-- didn't work. I flashed firmware through "dload method" which also failed miserably. Then I read that you can "force" an update thru TWRP. As a preparation, I downloaded HiSuite to backup some data on my PC. I sh*t you not, the app immediately detected an update. The app allowed me to update the phone (a series of updates though) to the latest version. So if you're facing the same predicament, try this out.
Download HiSuite for PC, install, connect your Huawei phone, and the application will then guide you on how to set things up. On successful connection, an option (HiSuite on PC) may detect an update for your phone. The app will download the update and install it on your phone. You may choose not to update too.
Tried same. Nadda. Still stuck on Android 7 and Emu 5
Related
Hello,
Please, i need help. I have problem with my honor 8.
Ill start from begining.
My original fw was frd-l02c432. (Im from eu, czech rep.) But since i wanted oreo update, ive done something wrong. Ive downloaded new update, and ended up with nrd90 test keys. After little play, ive manage to downgrade to frd-l02 c675. Just was unable to upgrade. ive download new sw via FF, install, and now im stuck again on test keys. I cant install twrp. Because, when i unlock bootloader, the oem option will grey out, and cant switch on. Cant install FF, because i have no keyboard. (Also update option is missing in settings) Erecovery is not working - cant find package. And when i download recovery package for c675b130 (or c432) and update via dload, it stuck in 5%- failed.
Is there some way to resurect him back to land of living ? or his only way to live is service center. I know, its almost sure, but i want to try fix it myself. And leave the service as a last resort.
Emui 5.0
Android 7.0
Thanks and have a nice rest of the weekend.
Andy.
EDIT: ok ive solved it (i think ) ive flashed twrp to boot instead of recovery. So phone did not start, but i was able to enter twrp. Then rebranded phone to frd L09 (my region with 432) via TWRP. Instal B380 via FF (with unlocked bootloader and twrp). then reflash TWRP back to normal recovery (because when the phone showed me new update, I was unable to install. ive downloaded the update, then hit install. Phone restarted to twrp and it showed me "error 7" when installing. So Ive uninstaled twrp. then download again. Phone restarted and update installed just fine). i just need to download the "latest package" via update from system everytime, so it will take time Maybe it will help someone. see ya
My phone is running android 10 v2.5, i was updated from v.1.8
I want to return android 9, if i flashed to EDL 1.6 backup then all sensors down.
A also tried rollback SD Card option (on this page https://www.ztedevices.com/de/supports/a2020g-proopen-market/), starts update normally but after a little progress update failed. I think my phone never been updated to v1.9, because didnt find it. I searched the internet and forum, is there 1.9 version package i didn't find. How i return to android 9 with sensors working, anyone help.
I figured out the problem, i always tried update process (to downgrade from 2.5 to 1.9) in recovery, but i learned that this is wrong. Downgrade process have to run inside phone system updates. To fix sensor problem on my phone, i followed this steps;
1) First lock bootloader again via fastboot "fastboot flashing lock" command (i think this is only works android 9, my sensors still down)
2) Update to Android 10 via SD card method (my sensors working again)
3) Downloaded the rollback package (2.5 to 1.9 or what you want) and unzip it to root directory in SD card as update.zip,
4) Go to Settings -> System -> System Update, then you will now see the downgrade option, then start the process,
After this steps my phone starts on android 9 and all sensors (brighness, proximity etc) working again.
@erturkmen is your phone A2020G or A2020U (US Version)? I am looking for rollback package for A2020U but could not find it anywhere on zte site.
ccraze said:
@erturkmen is your phone A2020G or A2020U (US Version)? I am looking for rollback package for A2020U but could not find it anywhere on zte site.
Click to expand...
Click to collapse
Hi there, my phone A2020G, i download Roms from this page,
Axon 10 Pro(Open market) – ZTE Deutschland
To install GSM I downgraded my P40 lite from Emui 10.0.1.236 all way down to Emui 10.0.1.108 using Firmware Finder, Hisuite proxy and Hisuite Itself.
Now after installing google, I want to update the phone to 10.0.1.236 again, but it says that the older version is the newest in the updates menu. I tried to reinstall Hisuite, tried to update with the Hisuite proxy and Firmware Finder and with builtin updater in the phone. But still... I can't update my system.
If someone knows some way to reactivate the updates on the phone please reply to this thread
Hi.
Was in the same situation. Tried multiple old firmwares with hisuite proxy, and they downloaded and worked just fine, but couldn't upgrade from them.
Finally found a suggestion on a German forum that worked.
Using the OTG software install method, download a firmware from easy-firmware(dot)com and install that. Be very careful what software you donwnload as you could brick your device.
This worked for me, installed version 144 for my P40 Pro Plus, got immediately a software update notification to 156. Delayed that, done the GMS install, restarted, updated to 156, and then, because I was in thebeta, updated to EMUI 11. All good.
Please be aware that the site is requiring money for the downloads, and that I am in no way affliated with them. It's your own decision what to do
santiagobbboff said:
To install GSM I downgraded my P40 lite from Emui 10.0.1.236 all way down to Emui 10.0.1.108 using Firmware Finder, Hisuite proxy and Hisuite Itself.
Now after installing google, I want to update the phone to 10.0.1.236 again, but it says that the older version is the newest in the updates menu. I tried to reinstall Hisuite, tried to update with the Hisuite proxy and Firmware Finder and with builtin updater in the phone. But still... I can't update my system.
If someone knows some way to reactivate the updates on the phone please reply to this thread
Click to expand...
Click to collapse
Did you ever figure it out? My p40 lite is doing the same thing on 10.0.1.108 as well
OTG install a complete firmware. There is no other way.
Working perfectly ever since I wrote the previous post, upgraded from the Emui11 beta to the final without issues.
costindaemon said:
OTG install a complete firmware. There is no other way.
Working perfectly ever since I wrote the previous post, upgraded from the Emui11 beta to the final without issues.
Click to expand...
Click to collapse
Will this remove the Googlefier install ?
Yeah, you have to completely reset and erase the phone, flash the oldest firmware you can find through OTG, then after booting stop the automatic updates from settings.
Then apply Googlefier and after everything is working fine, only then update.
I had a hard time finding the firmware files for OTG, maybe you're luckier.
So basically, I have 10.0.1.108 installed currently with Googlefier installed.. I'm not able to update the emui via hisuite/proxy, fails the install. So then I need to do OTG install of a fullota emui and then reinstall Googlefier? I guess anything newer than .108 should be ok?
Yes, but be careful, try picking an older software, or you won't be able to use Googlefier. It fails with the latest updates, so your best bet is install it on an older one and then update.
A reinstall of your version 108 or something a bit newer should work.
Ok so i downgraded my huawei p40 from emui 12 to emui 10, but the problem is that i downgraded to emui 10.1.0.182, and, well i lost usb connection and fast charging, i tried updating via ota, but it says im up to date, i used erecovery, but it gives me the error retrieving package info, i tried dload with otg, but when i go to update in recovery it stays there for a while and then gives me the error ´´this update does not exist´´, so i dont know what else to do.
Edit: I used a transcend card instead of the one i was using and it now worked, i believe SanDisk cards also work; then i eventually got the OTAs, also when u get an OTA, you need to restart the phone in order to get the next one.
Hi all,
I have a weird issue - I have updated my OnePlus 9 EU last year over Oxygen Updater, but managed to install India-only update on EU phone and now in settings it shows 2113_11_C.60.
After scouring internet I found that C.60 was India only update.
Now, I haven't received a single auto update since May 2022.
I have tried downloading incrimental updates to C.62 both for 2113 and 2111, but neither local upgrade nor special oneplus app was not able to update.
Also tried full install of C.62, no success.
Even tried full upgrade to latest EU build LE2113_11_F.75 - same result..
The local upgrade through settings constantly shows "verification failed" no matter what file I choose.
OP's System Update app would fail after showing system updating for a minute, with 0% progress.
As I understand, I somehow managed to install Indian version of incrimental update on EU phone, but now I am stuck on it.
What are other reinstall options on OnePlus 9?
Can I somehow force install if I connect over PC?
Many thanks for the help!
EDIT:
Forgot to attach screenshots...
Index of /list/Unbrick_Tools
Find the one compatible for your device whatever stock would be and run the msm recovery tool. This will get you back where you need to be to be able to update to latest software.
Otherwise you can try editing the file payload_properties.txt inside the update zip and changing oplus_update_engine_verify_disable to 1. This way your phone should skip the verification process entirely. Keep in mind that this could still result into bricking your phone because of this unintended update path but since the alternative would be using MSM tool why not trying anyway.