Related
In the tradition of the firmware threads by @vsriram92 ... here is the full initial update zip.
Honor 6X (US version) model: BLN-L24C567
Firmware: BLN-L24C567B110
Updated Link 2017-09-09 MEGA-FULL-OTA
Rollback Package from Android 7.0 to 6.0: MEGA-ROLLBACK
You can also download both from Huawei at hihonor.com in their support area.
Thanks @adomol, repository updated with appropriate credit.
Is this the Android 7 update from the 6.0.1 ????
No, this is the stock Marshmallow firmware that shipped with the 6X.
Can this be used to downgrade from Nougat to Marshmallow? Or will it brick? Just figured I'd ask before I try, I'm stuck in a bit of a jam right now, and no firmware I've tried will apply successfully (fails at 5%). So I figure that I might have better luck going back to the stock MM that the device came with.
Edit: It looks like the download link is invalid. Any mirrors?
Both links are not working now
PalakMi said:
Both links are not working now
Click to expand...
Click to collapse
Go to officail website http://www.hihonor.com/us/support/index.html
You need to install the rollback package before you install the 6.0 firmware if you are downgrading from 7.0
e20140 said:
Go to officail website http://www.hihonor.com/us/support/index.html
You need to install the rollback package before you install the 6.0 firmware if you are downgrading from 7.0
Click to expand...
Click to collapse
@AnonVendetta
Thanks guys, but I was able to go back to MM yesterday, with the help of private messages from @adomol. It involved using a small rollback package and a large full package. The rollback went fine. I may or may not upgrade back up to Nougat, got some prep work to do and things to test. I've only had this device for a few days so I don't know the ins and outs of upgrading/downgrading firmware on Huawei. I'm more familiar with Samsung and Odin.
AnonVendetta said:
Thanks guys, but I was able to go back to MM yesterday, with the help of private messages from @adomol. It involved using a small rollback package and a large full package. The rollback went fine. I may or may not upgrade back up to Nougat, got some prep work to do and things to test. I've only had this device for a few days so I don't know the ins and outs of upgrading/downgrading firmware on Huawei. I'm more familiar with Samsung and Odin.
Click to expand...
Click to collapse
It is good that you downgraded to MM.
You'll get used to honor devices pretty quickly.
All the best
AnonVendetta said:
Thanks guys, but I was able to go back to MM yesterday, with the help of private messages from @adomol. It involved using a small rollback package and a large full package. The rollback went fine. I may or may not upgrade back up to Nougat, got some prep work to do and things to test. I've only had this device for a few days so I don't know the ins and outs of upgrading/downgrading firmware on Huawei. I'm more familiar with Samsung and Odin.
Click to expand...
Click to collapse
Can you share the links for small package. I will update the thread so that any othwr user facing the same issue can downgrade.
Link for only smaller file is ok but you can share both.
I'm having this same issue. Trying the rollback package now...hoping that works.
I acidentally deleted all files of blnl24, can i fix with this
Does anyone have the OTA firmware for the Honor 6x LN-24? All the links I'm finding online are broken.
Hi,
I have a Moto G5S which i had to replace the screen couple of months ago So i purchased a screen on ebay being advertised as OEM.
Replacing screen went well and all was working fine till phone was updated to Oreo 8.1 (OTA update).
Now touchscreen is not working.
Phone was not rooted and all was original OS.
I have done a bit of reading and not sure i know what to do.
Is it possible to downgrade to Nougat !?? Has anyone else had this issue? what is the solution please?
Thanks
https://forum.xda-developers.com/moto-g5s/help/bricking-phones-replacement-screens-t3859279
This thread has some more info
Hi, can someone please point me in the right direction to get Oreo stock rom please.
If i am not wrong there are nougat
https://forum.xda-developers.com/mo...h-official-firmware-moto-g5s-montana-t3687768
thanks
I think i found it
https://forum.xda-developers.com/moto-g5s/development/rom-android-8-1-0-oreo-stock-firmware-t3845501
foxy6800 said:
I think i found it
https://forum.xda-developers.com/moto-g5s/development/rom-android-8-1-0-oreo-stock-firmware-t3845501
Click to expand...
Click to collapse
https://forum.xda-developers.com/moto-g5s/development/rom-android-8-1-0-oreo-stock-firmware-t3845501
or https://forum.xda-developers.com/moto-g5s/development/firmware-motorola-g5s-t3845848
By the way, don't attempt to flash Nougat firmwares if you've already installed the Oreo OTA update. It'll brick your device. This includes Nougat custom ROMs.
Hello everyone,
I'm getting really frustrated hree as I can't flash any android 10 GSI. I either get bootloop, stuck on samsung logo or stuck on restarting on samsung logo.
Flashing different kernels seem to change the above behavior (instead of bootloop I get samsung logo and vice-versa).
I tried everything:
Doing the no-verity thingie...
Flashing stock files then GSI - nothing.
Flashing soldiers oreo kernel - nothing
Flashing endurance kernel - nothing
I can't find a vendor image that's compatible with any GSI on my phone. I also can't find any kernel that's compatible either.
So please, end my misery... if anyone managed to install android 10 GSI on this TREBLE COMPATIBLE DEVICE, please guide me through or provide any useful file (vendor img/kernel) that I might have been missed.
I wrote this because I couldn't find anything that could help... Thanks in advance!
EDIT:
I solved the problem with the kind help from phhusson and the guidance from Lanreallenjay (thanks, both of you!), so I'm trying to provide the solution for anyone that might be having the same problem as I had. So here it is:
For PIE GSI: use stock kernel/vendor (anything stock), flash the GSI, then flash Magisk -> it should boot fine now (only tested with phhusson's GSI. I had vibrating restart loops before, I wasn't installing magisk, that was my mistake)
For Android 10 GSI: same as above, but install the modded Magisk from phhusson's git (located @ v200 android 10 gsi post) instead of the normal one .
itShouldWork said:
Hello everyone,
I'm getting really frustrated hree as I can't flash any android 10 GSI. I either get bootloop, stuck on samsung logo or stuck on restarting on samsung logo.
Flashing different kernels seem to change the above behavior (instead of bootloop I get samsung logo and vice-versa).
I tried everything:
Doing the no-verity thingie...
Flashing stock files then GSI - nothing.
Flashing soldiers oreo kernel - nothing
Flashing endurance kernel - nothing
I can't find a vendor image that's compatible with any GSI on my phone. I also can't find any kernel that's compatible either.
So please, end my misery... if anyone managed to install android 10 GSI on this TREBLE COMPATIBLE DEVICE, please guide me through or provide any useful file (vendor img/kernel) that I might have been missed.
I wrote this because I couldn't find anything that could help... Thanks in advance!
Click to expand...
Click to collapse
What's your phone's specifications?
Lanreallenjay said:
What's your phone's specifications?
Click to expand...
Click to collapse
Hey, thanks for the interest!
I've got the S9 Exynos variant (SM-G960F, Europe), I unlocked the bootloader several days ago.
It's on android 9 right now, I flashed the stock firmware after I've tried everything to get android 10 treble to work and failed.
Current kernel version: 4.9.59-16947752 (stock)
Build number: PPR1.180610.011.G960FXXS7CSJ3
I can flash any rom available besides GSI (I've used lineage OS 16 for a couple of days).
If you need anything else more specific just ask, I don't really know what exactly can help with this situation.
Cheers!
itShouldWork said:
Hey, thanks for the interest!
I've got the S9 Exynos variant (SM-G960F, Europe), I unlocked the bootloader several days ago.
It's on android 9 right now, I flashed the stock firmware after I've tried everything to get android 10 treble to work and failed.
Current kernel version: 4.9.59-16947752 (stock)
Build number: PPR1.180610.011.G960FXXS7CSJ3
I can flash any rom available besides GSI (I've used lineage OS 16 for a couple of days).
If you need anything else more specific just ask, I don't really know what exactly can help with this situation.
Cheers!
Click to expand...
Click to collapse
Ask for help here
https://t.me/phhtreble/283195 <---
Read before any question ^^^
After flashing G960FXXS7CSJ3 November stock firmware I can no longer flash anything.
(can't mount data partition)
When I try downgrading to G960FXXU5CSF2 June firmware Odin fails and the screen says:
SW REV. CHECK FAIL (BOOTLOADER) DEVICE: 7 BINARY: 5
November G960FXXS7CSJ3 seems to have upgraded the bootloader security, does anyone know a fix?
itShouldWork said:
Hello everyone,
I'm getting really frustrated hree as I can't flash any android 10 GSI. I either get bootloop, stuck on samsung logo or stuck on restarting on samsung logo.
Flashing different kernels seem to change the above behavior (instead of bootloop I get samsung logo and vice-versa).
I tried everything:
Doing the no-verity thingie...
Flashing stock files then GSI - nothing.
Flashing soldiers oreo kernel - nothing
Flashing endurance kernel - nothing
I can't find a vendor image that's compatible with any GSI on my phone. I also can't find any kernel that's compatible either.
So please, end my misery... if anyone managed to install android 10 GSI on this TREBLE COMPATIBLE DEVICE, please guide me through or provide any useful file (vendor img/kernel) that I might have been missed.
I wrote this because I couldn't find anything that could help... Thanks in advance!
EDIT:
I solved the problem with the kind help from phhusson and the guidance from Lanreallenjay (thanks, both of you!), so I'm trying to provide the solution for anyone that might be having the same problem as I had. So here it is:
For PIE GSI: use stock kernel/vendor (anything stock), flash the GSI, then flash Magisk -> it should boot fine now (only tested with phhusson's GSI. I had vibrating restart loops before, I wasn't installing magisk, that was my mistake)
For Android 10 GSI: same as above, but install the modded Magisk from phhusson's git (located @ v200 android 10 gsi post) instead of the normal one .
Click to expand...
Click to collapse
So from stock you flashed AOSP 10 GSI to system partition then phh's magisk (in TWRP) then it works for you?
rupert3k said:
So from stock you flashed AOSP 10 GSI to system partition then phh's magisk (in TWRP) then it works for you?
Click to expand...
Click to collapse
Yep, it does. Buuut the rom is not stable at all, I've got random reboots/ crashes when opening settings and such, not usable at all. I'm on ONE UI 2.0 beta now which is much more stable (daily driver stable actually).
rupert3k said:
After flashing G960FXXS7CSJ3 November stock firmware I can no longer flash anything.
(can't mount data partition)
When I try downgrading to G960FXXU5CSF2 June firmware Odin fails and the screen says:
SW REV. CHECK FAIL (BOOTLOADER) DEVICE: 7 BINARY: 5
November G960FXXS7CSJ3 seems to have upgraded the bootloader security, does anyone know a fix?
Click to expand...
Click to collapse
Have you tried formatting data with TWRP (to the part when it asks you to write "yes") then flash no-verity?
You should at least be able to flash TWRP. If you can't, just download the proper USB drivers for your device, it might be the culprit.
Cheers!
itShouldWork said:
Yep, it does. Buuut the rom is not stable at all, I've got random reboots/ crashes when opening settings and such, not usable at all. I'm on ONE UI 2.0 beta now which is much more stable (daily driver stable actually).
Click to expand...
Click to collapse
Phh just hinted it's likely Pie vendor causing panics:
"First you need to flash stock rom. Then install magisk and then this gsi.
Though please note that on Pie vendor, S9 kernel panics and reboot every few minutes, so it is highly unusable."
itShouldWork said:
Hey, thanks for the interest!
I've got the S9 Exynos variant (SM-G960F, Europe), I unlocked the bootloader several days ago.
It's on android 9 right now, I flashed the stock firmware after I've tried everything to get android 10 treble to work and failed.
Current kernel version: 4.9.59-16947752 (stock)
Build number: PPR1.180610.011.G960FXXS7CSJ3
I can flash any rom available besides GSI (I've used lineage OS 16 for a couple of days).
If you need anything else more specific just ask, I don't really know what exactly can help with this situation.
Cheers!
Click to expand...
Click to collapse
I have tried Android 10 GSI , using latest Q update
ZoiraP said:
I have tried Android 10 GSI , using latest Q update
Click to expand...
Click to collapse
Is it usable? any random reboots/ annoying instability?
itShouldWork said:
Is it usable? any random reboots/ annoying instability?
Click to expand...
Click to collapse
I have tried it partly , nfc isnt working , camera quality is bad , Bluetooth working , audio working , magisk working . I'll use it a bit more and tell you.
ZoiraP said:
I have tried it partly , nfc isnt working , camera quality is bad , Bluetooth working , audio working , magisk working . I'll use it a bit more and tell you.
Click to expand...
Click to collapse
Camera quality might be fixed with Google cam, if you find a good port.
Not to derail the thread but I just noticed after installing Android 10 beta 2 Treble Info now reports my S9 supports Treble A/B, curious no?
rupert3k said:
Not to derail the thread but I just noticed after installing Android 10 beta 2 Treble Info now reports my S9 supports Treble A/B, curious no?
Click to expand...
Click to collapse
Wait what? That's interesting...
Can someone with more experience enlighten us about the differences between the A only and A/B?
A\B
itShouldWork said:
Wait what? That's interesting...
Can someone with more experience enlighten us about the differences between the A only and A/B?
Click to expand...
Click to collapse
No real experience but A\B devices have two slots ie double the partitions (OnePlus has 67) .
This allows updates to be installed while running from slot A while the updated system is copied to B.
Apparently Q requires A\B so now we're on Q may as well try that next time we're curious
Phh just released:
AOSP 10.0 v208
Fix suspend/dt2w for Samsung Q vendor
Fix backlight for Samsung Q vendor
Samsung Q's fine, love gestures but the bloat is killing me.
You can tell Q's going to be so much leaner without bixby & friends.
Glad we installed it to get compatible but I think now we probably stand a better chance with 10 GSI's, hopefully LOS17 & Pixel Experience get updated again soon.
Wondering whether to following the rooting instructions yet?
Phh did say "flash stock rom then magisk and then gsi"
https://forum.xda-developers.com/galaxy-s9/how-to/one-ui-2-beta-rooting-installing-twrp-t4012961
ZoiraP's wondering why we sooo slow lol!
Wow this looks good: https://forum.xda-developers.com/ga...-s9--s9-cross-device-development/rom-t4020939
At this point I have given up on Android Q on this device and I'm having problems to decide which firmware version to downgrade to. I don't need latest bells and whistles, I like my phone plain and simple with no lags/freezes and minimal amount of bugs. I was overall happy sitting on latest Pie update, but Im not sure if performance was better on latest Oreo firmware since it has been such a long time.
What are your takes on this? Should I go for latest Pie or Oreo firmware?
Heatti said:
At this point I have given up on Android Q on this device and I'm having problems to decide which firmware version to downgrade to. I don't need latest bells and whistles, I like my phone plain and simple with no lags/freezes and minimal amount of bugs. I was overall happy sitting on latest Pie update, but Im not sure if performance was better on latest Oreo firmware since it has been such a long time.
What are your takes on this? Should I go for latest Pie or Oreo firmware?
Click to expand...
Click to collapse
If I would go back to 9 (pie) I would try to find the version which still had the dt2w function. There's 2 different display version of mi a2 lite and because of that they figured it's easier just to remove the function and push out 1 update that fits both version rather than working on 2 separate update just for 1 phone model.
andraslate said:
If I would go back to 9 (pie) I would try to find the version which still had the dt2w function. There's 2 different screen version of mi a2 lite and because of that they figured it's easier just to remove the function and push out 1 update that fits both version rather than working on 2 separate update just for 1 phone model.
Click to expand...
Click to collapse
I'm pretty sure my phone has a screen without dt2w function anyway. If dt2w function is on by default, then it should work here on android Q as well unless they disabled it universally? Because here I am, tapping on the screen and its not waking up and never has before either
Thanks for your quick answer. So I should be looking at flashing V10.0.20.0, it seems to be the last Pie firmware looking from here.
Heatti said:
So I should be looking at flashing V10.0.20.0, it seems to be the last Pie firmware looking from here.
Click to expand...
Click to collapse
Yee. That's the last pie update.
Hi all, anybody knows what is the difference between 2061 and 2063, is it worth updating to 2061 when it is 2063
Veseleil said:
Hi all, anybody knows what is the difference between 2061 and 2063, is it worth updating to 2061 when it is 2063
Click to expand...
Click to collapse
UPD. Found that 2063 is 2061EU, updated last, everything perfect
Need more informations about the two
I am in the same situation.
Got my RMX2063 device not long and i purchased the International Version.
Is there a way to check what is flashed at the moment on it? International or EU OS?
Curently it is saying RMX2063_A_35
Is the RMX2061EU better?
Have not found any clear information about the two, so can someone come with some good informations?
I found out that Realme Flash Tool works great to flash stock ROM or downgrade to previous versions. it can flash zip, ozip and gsi file formats for OS.
From little search on web, it seems like each firmware version was made for particular region. This means particular things will work better with firmware made for your particular area. So why to risk spoiling things by installing firmware made for another region?
I am trying to flash EU Firmware https://download.c.realme.com/osupdate/RMX2061EU_11_OTA_0380_all_EIeguy5zqMib.ozip on RMX2061
Currently, my device is RMX2061_11_A.41
Have anyone tried this?
gaduaxe said:
I am trying to flash EU Firmware https://download.c.realme.com/osupdate/RMX2061EU_11_OTA_0380_all_EIeguy5zqMib.ozip on RMX2061
Currently, my device is RMX2061_11_A.41
Have anyone tried this?
Click to expand...
Click to collapse
I have switched around from Indian, Global and EU roms with no problems many times in the past though now I use a CRDroid A12.1 custom rom
Veseleil said:
UPD. Found that 2063 is 2061EU, updated last, everything perfect
Click to expand...
Click to collapse
Hi @Veseleil
Did you flashing RMX2063 Firmware into RMX2061 successfully? Please give me a guidance
Tkx
gaduaxe said:
Hi @Veseleil
Did you flashing RMX2063 Firmware into RMX2061 successfully? Please give me a guidance
Tkx
Click to expand...
Click to collapse
Hi. It's been a long time since I did this.)
But, I remember exactly, that when version RMX2063 was indicated on the phone - I manually updated it with version RMX2061EU - then all following updates were stable over the air.
The update file was taken from this site (https://www.realme.com/eu/support/software-update) of the European region. Unfortunately, as of now, it does not seem to be up to date, but you can still try to install the version from this site, and after installing it, request an update over the air. There is a chance that the OTA update will start working.
If it helps, I saw another site (https://realmefirmware.com/realme-firmware-update/#google_vignette) with different versions, but I didn’t try to figure needed version out. Maybe it could be useful.
Good luck!