Related
I live in VietNam, i use a HTC ONE AT&T, I have to unlock Sim to use in VietNam.
Before, i unlocked bootloader and flash a rom cook.
Today, i want update Lastest Firmware of Android 4.4 ( I using a version Firmware of Android 4.3 )
I flash Stock Recovery of ATT, locked bootloader, Run RUU RUU_M7_UL_JB43_SENSE50_MR_Cingular_US_3.17.502.3_Radio_4A.19.3263.13_10.38j.1157.04_release_334235_signed_2
After, i go to Setting > ATT software update > check for Update, but it say : "no update is available for your device at this time. your device will automatically check for an update within the next 48 hours"
Everyone please say to me how to update lastest firmware but not S-Off (my device S-ON).
Send to me a file or link to download lastest Firmware.
i download darkboot_att_4.18.502.7.zip from a Post's member, but when i flash firmware : fastboot flash zip darkboot_att_4.18.502.7.zip
Ít say: Fail
Thanks you !
I have searched everywhere but I didn't find a reply to my question.
A couple of days ago I have updated my phone LLD-L31 to the version 8.0.0.132 through Firmware Finder (it worked for me with proxy method) then I decided to revert back to the previous version 8.0.0.131. So I started reading guides to install a firmware on Huawei/Honor devices, I have downloaded the FullOTA package version 8.0.0.131 with Firmware Finder, placed it in the folder dload on my SDcard and started the intstallation in the project menu (accessible digiting *#*#2846579#*#* in the dialer), it started but suddenly it ended with a message "installation failed".
So my question is: how can i revert to the previous version of the software (or to the out of the box firmware installed on my device)?
karmakey said:
I have searched everywhere but I didn't find a reply to my question.
A couple of days ago I have updated my phone LLD-L31 to the version 8.0.0.132 through Firmware Finder (it worked for me with proxy method) then I decided to revert back to the previous version 8.0.0.131. So I started reading guides to install a firmware on Huawei/Honor devices, I have downloaded the FullOTA package version 8.0.0.131 with Firmware Finder, placed it in the folder dload on my SDcard and started the intstallation in the project menu (accessible digiting *#*#2846579#*#* in the dialer), it started but suddenly it ended with a message "installation failed".
So my question is: how can i revert to the previous version of the software (or to the out of the box firmware installed on my device)?
Click to expand...
Click to collapse
You should have an option to downgrade in the about section/ the update menu of your phone if you did it right.
Otherwise you may need to use the HuRupdater Method.
Fredin_ said:
You should have an option to downgrade in the about section/ the update menu of your phone if you did it right.
Otherwise you may need to use the HuRupdater Method.
Click to expand...
Click to collapse
Thanks for your reply!
I don't have this option, but if I remember well I hadn't it also in the previous version of the firmware.
So i can't install a previous version of the firmware simply downloading it an putting into dload folder of the SDcard?
karmakey said:
Thanks for your reply!
I don't have this option, but if I remember well I hadn't it also in the previous version of the firmware.
So i can't install a previous version of the firmware simply downloading it an putting into dload folder of the SDcard?
Click to expand...
Click to collapse
Can you please specify why do you want to roll back?
Because most people just wanna upgrade to a newer version.Newwr versions will have better stability so it's recommended to keep the latest version unless you have some bugs.
I honestly don't know why the dload method doesn't work, seems that it doesn't work for most people.
I think you'll be able to roll back using HuRupdater. But that'll mean you'll have to unlock bootloader and flash twrp first. Then you can go all stock from there.
Here's a guide to the HuRupdater from @zxz0O0
https://www.google.co.in/amp/s/foru...lash-official-firmware-recovery-t3769279/amp/
Fredin_ said:
Can you please specify why do you want to roll back?
Because most people just wanna upgrade to a newer version.Newwr versions will have better stability so it's recommended to keep the latest version unless you have some bugs.
I honestly don't know why the dload method doesn't work, seems that it doesn't work for most people.
I think you'll be able to roll back using HuRupdater. But that'll mean you'll have to unlock bootloader and flash twrp first. Then you can go all stock from there.
Here's a guide to the HuRupdater from @zxz0O0
https://www.google.co.in/amp/s/foru...lash-official-firmware-recovery-t3769279/amp/
Click to expand...
Click to collapse
After installing the version 132 I asked the technical support through HiCare and they told me that installing firmware with Firmware Finder could void warranty so I decided to revert to the previous firmware and wait for regular OTA by Huawei.
karmakey said:
After installing the version 132 I asked the technical support through HiCare and they told me that installing firmware with Firmware Finder could void warranty so I decided to revert to the previous firmware and wait for regular OTA by Huawei.
Click to expand...
Click to collapse
I'm not sure but I think you are on the latest build for your varient now so you won't be getting any updates untill a next build comes in.
I don't think you'll be able to roll back without the firmwares from firmware finder as you don't have an option to roll back.
The best option now would be to just wait for the next official build(might come soon as a small ota which has security patches) and then check if you are facing any issues installing which you won't as you are not rooted and dosent have an unlocked bootloader. So don't worry ?
Fredin_ said:
I'm not sure but I think you are on the latest build for your varient now so you won't be getting any updates untill a next build comes in.
I don't think you'll be able to roll back without the firmwares from firmware finder as you don't have an option to roll back.
The best option now would be to just wait for the next official build(might come soon as a small ota which has security patches) and then check if you are facing any issues installing which you won't as you are not rooted and dosent have an unlocked bootloader. So don't worry
Click to expand...
Click to collapse
Version 8.0.0.133 with July security patch just arrived and installed through official OTA!
karmakey said:
Version 8.0.0.133 with July security patch just arrived and installed through official OTA!
Click to expand...
Click to collapse
Good to hear you are up and running fine ?
Want to downgrade my honor 9 lite
After some update the theme engine crashed. Themes can no longer change the notiifcation bar icons and shortcuts icons.
Downgrading version Problem
I used firmware finder and dns method to downgrade my honor 9 lite and while i register update on firware finder and opens hisuite for update it is saying u r on already the latest version
Plz help me with downgrading my version 9 to 8
Hi
I'm unable to change the firmware on my BLA-L29 C432 B142 May security patch (rebranded from C636 about 6 months ago).
Checking OTA just says 'no updates available' and if I try to update via FunkyHuawei using eRecovery it downloads but after 'verifying' it moves on to 'recovery system running' and then errors with the message 'recovery failed' when it gets to 1%.
I've tried quite a few things to try and get something to move on, but it seems like I'm stuck on an old version of firmware and no way to change it. I need a new plan.
I've tried (with lots of factory resets and wiping cache inbetween):
- OTA updates - always says no update available.
- Via FunkyHuawei:
- Reflash same firmware (eRecovery fails during 'recovery system running')
- Reflash newer or older firmare in same region (eRecovery fails during 'recovery system running')
- Change region, reflash newer or older firmware in same region (eRecovery fails during 'recovery system running')
- Use unbrick tool to flash same or different firmware in both same and different regions (unbrick tool completes but firmware version always stays the same in about phone, the android security patch date changes though, but eRecovery won't let me reflash anything afterwards as eRecovery fails during 'recovery system running')
- The last OTA update I got was C432 .137. When everyone else was getting .145 OTA I got Firmware Finder to move me from .137 to .142.
Has anyone got any ideas on what to do next? I don't want to be stuck on the same firmware version and security patch forever.
Other than the FunkyHuawei rebrand about 6 months ago from C636 to C432, the phone is standard (no attempt to unlock bootloader, root).
I was thinking of:
- Unlock bootloader using DC unlocker (from what I've read this might still work as I'm on B142 which has a May security patch)
- Flash TWRP
- Flash a custom ROM
- Try and restore back to stock
- Possibly rebrand back to factory original C636 as there seem to be a few threads about rebranded phones not getting updates promptly, but I can't see anyone else who is getting eRecovery failing no matter what they do and no way to change firmware. I have already tried rebranding back to C636 via FH, but can't, as eRecovery fails at the same point when trying to flash the C636 firmware.
Funky should always work to update, check that DNS is correct when you enter that test site.
- Unlock bootloader using DC unlocker (from what I've read this might still work as I'm on B142 which has a May security patch)
Click to expand...
Click to collapse
This will work. I have downgraded and tested it
You could do this:
Get unlock code
Unlock bootloader
Flash TWRP (https://forum.xda-developers.com/mate-10/development/huawei-mate-10-pro-twrp-3-2-1-0-t3769904)
Download firmware update.zip, public and hw zip from http://pro-teammt.ru/firmware-database/
Update to the version you want using HuRUpdater (https://forum.xda-developers.com/honor-9/development/tool-flash-official-firmware-recovery-t3769279).
You will stay bootloader unlocked now though, but the rest is stock.
ante0 said:
Funky should always work to update, check that DNS is correct when you enter that test site.
Click to expand...
Click to collapse
The DNS is fine and I can load the test sites, eRecovery gets info and downloads the firmware labelled "FunkyHuawei" and the size is around 3GB. After taking a few minutes to download, the eRecovery moved on to 'verifying package', that completes, it moves on to 'recovery system running' and after it gets to 1% it says 'recovery failed'.
ante0 said:
This will work. I have downgraded and tested it
You could do this:
Get unlock code
Unlock bootloader
Flash TWRP (https://forum.xda-developers.com/mate-10/development/huawei-mate-10-pro-twrp-3-2-1-0-t3769904)
Download firmware update.zip, public and hw zip from http://pro-teammt.ru/firmware-database/
Update to the version you want using HuRUpdater (https://forum.xda-developers.com/honor-9/development/tool-flash-official-firmware-recovery-t3769279).
You will stay bootloader unlocked now though, but the rest is stock.
Click to expand...
Click to collapse
I will try this, anything to get me out of the hole I seem to be stuck in as all methods I've tried so far rely on eRecovery. Thankyou for all of the links.
When using HuRUpdater does it have to be in the same region, or can I rebrand at the same time?
Thasscas44 said:
The DNS is fine and I can load the test sites, eRecovery gets info and downloads the firmware labelled "FunkyHuawei" and the size is around 3GB. After taking a few minutes to download, the eRecovery moved on to 'verifying package', that completes, it moves on to 'recovery system running' and after it gets to 1% it says 'recovery failed'.
I will try this, anything to get me out of the hole I seem to be stuck in as all methods I've tried so far rely on eRecovery. Thankyou for all of the links.
When using HuRUpdater does it have to be in the same region, or can I rebrand at the same time?
Click to expand...
Click to collapse
HuRUpdater can only handle same region updates as far as I know.
You can use HWOTA to rebrand, but mankindtw (original author) has since edited the thread as he thought his tool bricked devices. But it was firmware that caused it.
And I can't remember the exact steps... You have to flash twice though, first to rebrand (example C636) and then to update to the same rebranded (C636) firmware.
https://mega.nz/#!oeATEQQb!qiP3mYlQQgZYlaS3dbY_QCwNJ-urTKyLQ2zKOA9KP8g
You could use FHRebrand tool, but it will change your bootloader unlock code so you'd have to use HCU client (DC-unlocker) twice to get it.
Also, before flashing anything, check xloader with this tool: https://forum.xda-developers.com/mate-10/how-to/beware-bla-l29c432b147-t3817241
For now, stay on XLOADER 01 firmware. We don't know if Huawei will change to 02. Going from 02 to 01 will end in a hard brick.
B142 is 01 so you're safe now
Thanks to your advice, I have a plan now. And good to know about the xloader stuff, that could have ruined my day.
I'm going to:
1. Get bootloader code [update: done using dc-unlocker, confirmed working on C432 .142]
2. Flash TWRP
3. Put same region and slightly downgraded version of firmware on to a USB and flash with HuRUpdater (assuming it needs to be put on a USB OTG stick as the M10Pro doesn't have an SD card). I intend to use the downgraded version so I can see the version successfully change in "about phone"
4. Rebrand using FH tool (if there's less chance of bricking than HWOTA) and keeping an older firmware
5. Hopefully it works, and [after getting the bootloader code again from dc-unlocker in case I need it in future] I will be able to update via OTA to latest official firmware
Hopefully starting again completely will overwrite whatever it is that's getting me stuck.
Thanks to @ante0 I got out of the hole I was in.
From what I've tested, there seems to be an inability to update OTA from a rebranded BLA-L29 432 running 137 or 142.
Here's what I did.
1. Unlocked bootloader, flashed twrp, flashed downgraded 137 version of C432 with hrupdater. Success. No offer of an OTA update though so still stuck on old version.
2. Ran FH rebrand tool to change region to the factory original C636. eRecovery failed at the same stage as before. Fail.
3. Kept region as C636, unlocked bootloader and flashed twrp again. Flashed April version of C636 firmware using hrupdater, twice. Success.
4. Immediately on boot up phone offered to update OTA to the latest version of C636 firmware. Success.
It seems that the phone wouldn't offer an update OTA if on rebranded C432 and running 137 or later, but did offer OTA when it was back on C636. I live in Europe, but will keep the 636 region if it means I get OTA, else I can't pass the phone on.
Now to relock the bootloader so banking apps work. Plan to use the fastboot relock command followed by dc unlocker relock tool. Hoping not to brick at the last stage!
Hi Guys,
I making this thread/guide because there is no where else an guide how to relock the bootloader.
In this example I'm having an unlocked bootloader sitting on firmware .238, what I want is to relock my bootloader is by doing an DOWNGRADE and not by an UPGRADE, yes it can be done also by an upgrade but that's not my point/guide.
Also by doing this you can reset the OTA / testing of your device.. For example if you sitting on the beta release of the firmware on the Mate 20 pro, with this method you can fully go back on the mainroad of the normal update progress through OTA.
By this method once you on a lower firmware you should get notified that there is an update for your current device through OTA.
Example; sitting on .238 (received from OTA) downgrading to .210 by dload, go to settings - software update - viola you get the new update of .238 on your phone.
This method will only discuss through the method of dload.
Requirements;
- Phone sitting on any firmware; In this example my phone sitting on 9.0.0.238 firmware
- ONLY works with an Service Firmware such as 9.0.0.210 firmware, this is necessary to be download from;
https://androidhost.ru/Uqv
- Having an OTG usb stick minimum 8GB
Steps;
1. Download the firmware from Androidhost.ru to download an Service Firmware for your device. Sitting on .238, so lets download the full version .210 (3.6GB)
https://androidhost.ru/Uqv
2. Unzip the downloaded.
3. Put the whole: 'dload' directory on the OTG usb-stick;
dload\
├─update_sd_base.zip
├─update_sd_cust_LYA-L29_hw_eu.zip
├─update_sd_preload_LYA-L29_hw_eu_R1.zip
4. Update / execute the update;
There are 2 ways to execute the software update is by doing the enter *#*#2846579#*#* -, and the ProjectMenu page will be displayed. Go to 4. Software Upgrade > 1. Memory card Upgrade> OK.
OR
Power off the phone, insert OTG disk, and press the VOLUME UP ,VOLUME DOWN key, and the POWER key at the same time. The phone enters the automatic upgrade mode, and the upgrade is started.
Give it time and voila, your are successfully downgraded and Safetynet gives all green passed.
CAUTION; USE ONLY AN SERVICE FIRMWARE, do not try any other firmware's.
Thanks me later.
Reserved.
Reserved.
Verstuurd vanaf mijn LYA-L29 met Tapatalk
I don't get it, why service firmware?
What stops from simply relocking in bootloader using same code that was used for unlock?
dimon222 said:
I don't get it, why service firmware?
What stops from simply relocking in bootloader using same code that was used for unlock?
Click to expand...
Click to collapse
An service firmware allows you to downgrade. It contains 3 package instead of 1.
Is causing the phone to get bricked by relocking the bootloader through the adb while being on the same firmware.
Verstuurd vanaf mijn LYA-L29 met Tapatalk
I was on 9.0.0.210 for months and stuck there. It depends on your region code whether it will work. On my region code it did not work and I could not do anything except load another dload version that was not compatible with my region. When 9.1 came out, Huawei manually flashed mine to a certified version for my region and I am back on track now. No more flashing for me.
About a year ago, I downloaded firmware for N960F from updato and downgraded from Pie to Oreo using Odin and it went all so well.
This time around I'm trying to downgrade from Android 10 to the exact same firmware version I used back then, just downloaded from updato yesterday.
Thing is, is doesn't seem to want to flash.. When I use the csc file Odin gets stuck at the recovery.img step. If I use the home_csc file, flashing starts, but is frozen at the start of the system step and nothing happens.
What is going wrong and what can I do?
mhamdyl08 said:
About a year ago, I downloaded firmware for N960F from updato and downgraded from Pie to Oreo using Odin and it went all so well.
This time around I'm trying to downgrade from Android 10 to the exact same firmware version I used back then, just downloaded from updato yesterday.
Thing is, is doesn't seem to want to flash.. When I use the csc file Odin gets stuck at the recovery.img step. If I use the home_csc file, flashing starts, but is frozen at the start of the system step and nothing happens.
What is going wrong and what can I do?
Click to expand...
Click to collapse
You can downgrade to pie android 9.0 but not oreo since you jumped to android 10
Android 10 and android 9 pie is on bootloader 3 and oreo is on bootloader 2 & 1 so impossible to downgrade you Cannot go back to oreo.
Odin will fail to flash.
Trex888 said:
You can downgrade to pie android 9.0 but not oreo since you jumped to android 10
Android 10 and pie is on bootloader 3 and oreo is on bootloader 2 & 1 so impossible to downgrade you Cannot go back to oreo.
Odin will fail to flash.
Click to expand...
Click to collapse
As I previously mentioned, last year I managed to downgrade from Pie to Oreo. Anyway, I just downloaded Pie firmware and tried flashing it and it does exactly like I said above, using each csc file, freezes at its respective step.
What could be the problem? Odin?
mhamdyl08 said:
As I previously mentioned, last year I managed to downgrade from Pie to Oreo. Anyway, I just downloaded Pie firmware and tried flashing it and it does exactly like I said above, using each csc file, freezes at its respective step.
What could be the problem? Odin?
Click to expand...
Click to collapse
As previously mentioned you can downgrade, but only to an earlier version of Android if the bootloader version is the same as the one you're currently on.
So Oreo came with bootloader 1 and later versions had bootloader 2
Pie came with bootloader 2, 3 and last version had bootloader 4
Android 10 comes with bootloader version 4
So from Android 10 you may download to later version of Pie with bootloader 4 only.
mhamdyl08 said:
As I previously mentioned, last year I managed to downgrade from Pie to Oreo. Anyway, I just downloaded Pie firmware and tried flashing it and it does exactly like I said above, using each csc file, freezes at its respective step.
What could be the problem? Odin?
Click to expand...
Click to collapse
Try factory reset first from recovery before flashing
.use latest version of odin
Try reboot your pc and different usb cable.
I recommend you to use patched odin from link below
https://forum.xda-developers.com/attachment.php?attachmentid=4899843
Also regarding csc the firmware comes with 2 csc files so Don't use "HOME_CSC_OMC" file
just use " CSC_"OMC
paul_59 said:
As previously mentioned you can downgrade, but only to an earlier version of Android if the bootloader version is the same as the one you're currently on.
So Oreo came with bootloader 1 and later versions had bootloader 2
Pie came with bootloader 2, 3 and last version had bootloader 4
Android 10 comes with bootloader version 4
So from Android 10 you may download to later version of Pie with bootloader 4 only.
Click to expand...
Click to collapse
OK! can I downgrade the bootloader? i. e. from version 4 to 1?
Trex888 said:
Try factory reset first from recovery before flashing
.use latest version of odin
Try reboot your pc and different usb cable.
I recommend you to use patched odin from link below
https://forum.xda-developers.com/attachment.php?attachmentid=4899843
Also regarding csc the firmware comes with 2 csc files so Don't use "HOME_CSC_OMC" file
just use " CSC_"OMC
Click to expand...
Click to collapse
what if I lost my recovery after flashing an old one? always I got download mode instead of recovery