Hello, I just rooted my phone and I tried to rollover my S9 plus which is currently on android 10 to android 9 pie. I tried to use Odin but I am still getting a binary error (Rev Check Fail Bootloader Device: 5 Binary: 2) Is there a bypass that I can use? I just really want to get my phone on Android 9. Thanks
yoonicorn said:
Hello, I just rooted my phone and I tried to rollover my S9 plus which is currently on android 10 to android 9 pie. I tried to use Odin but I am still getting a binary error (Rev Check Fail Bootloader Device: 5 Binary: 2) Is there a bypass that I can use? I just really want to get my phone on Android 9. Thanks
Click to expand...
Click to collapse
No bypass
Samsung devices can't be downgraded to previous android versions hence the error.
The significant digit for bootloader version can't higher than the rom build number. It must be the same or lower.
The 5th digit from the end of the number is the significant digit that designates that, is what I've been told here.
In this case it's 2.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Related
Hey there i am using samsung galaxy note 2 model number n 7100 which is running android jellybean version 4.3latest versions, when i tried to install ☆FRAMROOT☆ V 1.8 on my note 2 it did not work the build number of my note 2 is N7100XXUEMKD.
I also tried to ROOT my phone through pc with cf auto root and other options available but it didn't route properly. Super user installed but then the knox on my note 2 shows a security warning and security the policy update message and the super user stopped unfortunately message appears so this also didn't work.
I also installed the "supersu" [v 1.86] app from chainfire, but it shows the following message:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I don't want to root my phone through pc, is there any other version of ☆FRAMROOT☆ available that could work on my note 2 jellybean 4.3.
Please help me guys !!!!
After using the box for almost 2 years without any problem I decided to upgrade to android 7.
I have only linux os at home and I found aml burn tool for it.
I tried quite all version of rom, the official beelink one 708N0, atvxperience, tillaz, magendanz and alvatech.
All of them get stuck on initial logo.
On the first time I was thinking about something wrong with the burning tool even if messages are all ok
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Then I flashed all roms available and always same result (stuck on boot logo) except for the different logo.
I was a little afraid I could have bricked my box so I tried flashing the latest MM stock firmware available 110M0 and finally the box booted normally.
I'm trying to figure out were is the problem:
aml-flash-tool for linux doesn't upgrade kernel? maybe it's too old to handle nougat?
I know that the best and smarter choice is to get access to a windows pc but it's like a challenge make it work on linux
I here have a Honor 20 pro (YAL-L41) in Europe.
The build is 11.0.0.176(C431E4R5P4 with Magic 4.0.0 and security patch level fom september 1, 2021.
Will there be any more updates coming from Huawei/Honor?
I read that the HarmonyOS should be available by now for this device, but maybe only in China.
Any ideas how to keep this device up to day with a current Android version? Any third-party firmware maybe?
But as far as I remember, this would need a bootloader code which Huawei no longer provides.
Thanks for your input.
Rgds
same here, it's been discontinuted update since September! what a joke, i thought they announced honor 20 will get EMUI 12
I read somewhere that Honor phones will get emui 12 in June.
News! Russian Federation Users gets MagicUI 5.2 update
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Anyway to get the update if not in Russia?
I don't know. Maybe change region, maybe hisuite proxy?
can confirm changing region doesn't work. firmware finder doesn't have any Magic UI 5 version, latest ones are Magic UI 4 /EMUI 11 from 2021
Hello everyone, I bought a samsung a52 5g hoping that it would arrive with android 11 instead it was updated to 12. the current build is A528BXXU1BUL7 I can downgrade to android 11. I attach a photo with versions of the 11 which one can I use? thanks for the help
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Any firmware with the same BIT = 1.
ze7zez said:
Any firmware with the same BIT = 1.
Click to expand...
Click to collapse
Thank you very much. you were very kind
Go for Andorid 13 as it is more optimised.
Zdrawko0o said:
Go for Andorid 13 as it is more optimised.
Click to expand...
Click to collapse
I don't think so. Samsung tends to build their systems on top of the first releases of android and it stays that way until the end of the firmware line.
ze7zez said:
I don't think so. Samsung tends to build their systems on top of the first releases of android and it stays that way until the end of the firmware line.
Click to expand...
Click to collapse
I'm using SM-A526B with Android 13.
What to say...
I can see how my midranger is flying (like never before) two updates after One UI 5.0 has been released.
Hi
am traying to downgrade my galaxy note 20 via odin and i cant do it always get an error so can someone now if there any solution to make it work ?? thanks for answers
anatiki12 said:
Hi
am traying to downgrade my galaxy note 20 via odin and i cant do it always get an error so can someone now if there any solution to make it work ?? thanks for answers
Click to expand...
Click to collapse
Your bootloader must be unlocked to downgrade. Be aware that some bootloader versions may incorporate an anti-rollback which will prevent downgrading.
Samsung uses eFuses to prevent downgrading. Speaking from my experience with an SM-N981U1, the fifth digit before the end tells you the amount of eFuses that update will blow. So if you are on a 3 version and you upgrade to a 4 version, it will blow another eFuse. You can only install firmware with the same number or higher. Do note, installing one with a higher number restricts downgrade ability. Here is a screenshot from https://samfw.com with different versions and the Bit/sw rev.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I hope you find this helpful!
Note: Unlocking the bootloader removes these eFuse checks although I'm not sure as to whether it prevents more eFuses from being blown.