galaxy note 20 SM-N981B downgrade firmeware from 13 to 11 - Samsung Galaxy Note 20 Questions & Answers

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.

Related

"Error: UEGetPhoneInfoFailure UE_2003" when trying to update to 6.0.1

Hi,
I just bought a sony xperia Z5compact from another guy that barely used it. He gave it to me with apparently, a stock ROM. But I dont know if the other guy did anything on the phone like rooting, unlocking, whatever.
But now I want to update from 6.0 to 6.0.1 and I cant do it. Neither in the phone, nor with the computer coz I get this error:
error: UEGetPhoneInfoFailure
UE_2003".
I checked more, and the phone has TWRP recovery and an Androdplus kernel. So it has been modified, but I dont know how to check the status of the bootloader or if it rooted.
I want to update the phone to 6.0.1. and I would like to have a stock rom and a locked bootloader. (because I read that custom rom and unlocking bootloader affect to the function of the camera).
How can I do it?
I am getting different information over the forum and the internet, and I am getting a bit lost...
the security thing from service info, stays like this
{
"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"
}
Click to expand...
Click to collapse
Hi, i've got the same issue,
did you find any solution to update the phone ?
Thanks !

Replacement M9 Phone should I try and update or root first

My original M9 battery is not holding a charge after about 3 years of faithful service. I was able to pickup a new M9 and would like to root it. It is a AT&T phone and my current provider is AT&T.
How should I go about rooting this phone should I put it on my AT&T account and then root after it gets an update or should I try and root it first ?
I am happy with stock but I do like Viper Rom (but worried that there might not be much more development in terms of custom roms for the M9)
Thanks for any help or guides you can point me to
{
"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"
}
Unlocked bootloader and have been doing OTA updates but cant see to update past Android 6.0 3.38.502.12
just tried to do a RUU_HIMA_UL_N70_SENSE80_ATT_MR_Cingular_US_4.27.502.7 update but it did not work, OTA updates keeps saying nothing to update please try again later (tried trick to set date forward but still nothing is found)
Any help would be great
Found that I might have to run RUU_HIMA_UL_M60_SENSE70_ATT_MR_Cingular_US_3.38.502.17.exe
But as the bootloader is unlocked it wont allow me to run it as it fails with a 155 error.
Trying
fastboot oem lock
and appears to run with out error but on reboot bootloader is still unlocked
ANY Help would be great about now

ATT unlocked and its current state of SW

Hello. I have an unlocked ATT version of S9 plus.
I flashed unlocked firmware to it but after reading so many pie thread, I'm beginning to question if I flashed the phone correctly.
Its been receiving OTA update regularly and its on ARL1.
I THINK I read somewhere in XDA that if you are on truly unlocked firmware, phone must read xaa/xaa/xaa. However, mine shows xaa/xaa/att? (currently on mintsim service which uses tmobile network I believe)
Can someone tell me if I did anything wrong as I have limited knowledge of android phones and I would like to correct it before pie update.
Thanks in advance.
You should be all good. The last one is showing the original software provider version that never changes from flashing carrier firmwares or unlocked firmwares. Basically it shows what the phone was born as I guess is a way you could look at it.
Bought mine directly from Samsung and mine also says that.
{
"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"
}
Sent from my SM-G965U1 using Tapatalk

Question: Safe to downgrade firmware ELS-N39 C636?

Hi, has anyone with ELS-N39 C636 managed to downgrade firmware successfully to prepare for sideload GMS?
The reason I'm asking is because my phone just got into a situation where it reboots every 20 secs. So, I've sent it to service center and they mentioned i will have to get motherboard replacement.
Few question from me
In what scenario will cause that to happen? Wrong firmware flashed?
Which way is more safe to downgrade? Hisuite proxy or OTG?
Seems like Hisuite don't check against current version?
OTG does check and will stop updating if some versions not matching?
I know i could have just flash back the correct firmware, but I've tried using Hisuite which wont happen due to constant rebooting. Also OTG mentioned my version don't match. So any better solution if this happens again? Any alternative firmware tools that is working?
I hope someone who knows the ins and outs of android could shed some light.
I've try to read up as much as I could but those mentioned are some concerns that I still have before retrying to downgrade again.
Thanks!
Here's my software version info
{
"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"
}

S9 Plus Rollover to Android 9

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"
}

Categories

Resources