Related
Still says 2017-08-01 security patch, but now with Blueborne and Krack patched as well.
https://www.verizonwireless.com/support/galaxy-s5-update/
Stock No-Wipe Firmware:
*This will remove Developer Status/Lock your Bootloader*
G900VVRU2DQL1_G900VVZW2DQL1_G900VVRU2DQL1_HOME.tar .md5.zip
Developer Bootloader Friendly/No Aboot No-Wipe Firmware:
G900VVRU2DQL1_G900VVZW2DQL1_G900VVRU2DQL1_HOME_No_ Aboot.tar.md5.zip
I also received the software update notification. Now hoping someone will be able to make the bootloader friendly/no aboot version to flash...
stormified said:
I also received the software update notification. Now hoping someone will be able to make the bootloader friendly/no aboot version to flash...
Click to expand...
Click to collapse
Been a while since I've been to this section of the forums but I'm already uploading a Dev Friendly version and the untouched one right now.
EDIT:
@Silent Patriot
Feel free to add this to the OP.
Stock No-Wipe Firmware:
*This will remove Developer Status/Lock your Bootloader*
G900VVRU2DQL1_G900VVZW2DQL1_G900VVRU2DQL1_HOME.tar.md5.zip
Developer Bootloader Friendly/No Aboot No-Wipe Firmware:
G900VVRU2DQL1_G900VVZW2DQL1_G900VVRU2DQL1_HOME_No_Aboot.tar.md5.zip
Dudash said:
Been a while since I've been to this section of the forums but I'm already uploading a Dev Friendly version and the untouched one right now.
EDIT:
@Silent Patriot
Feel free to add this to the OP.
Stock No-Wipe Firmware:
*This will remove Developer Status/Lock your Bootloader*
G900VVRU2DQL1_G900VVZW2DQL1_G900VVRU2DQL1_HOME.tar.md5.zip
Developer Bootloader Friendly/No Aboot No-Wipe Firmware:
G900VVRU2DQL1_G900VVZW2DQL1_G900VVRU2DQL1_HOME_No_Aboot.tar.md5.zip
Click to expand...
Click to collapse
Hi, I am running the Resurrection Remix Final N ROM on my g900v and I have this bootloader (g900vvrs2dqb2). I looked it up and saw that it was from February 2017.
I would like to update my modem and boot so I am ready for Oreo but I'm not sure best way to go about it,(Odin)?
I know this information is available on XDA and probably in this forum, but I am paranoid because I had a hell of a time unlocking the bootloader because I was fallowing old directions.
I would be very grateful to anyone willing to point me towards simple, but accurate directions.
Thanks in advance, and apologize for my ignorance!
Sent from my kltevzw using XDA Labs
Awesome! Thanks very much. I'm gonna give this a shot like the previous install/upgrade some time Friday afternoon PDT.
Jeebus I need sleep....
Can I flash this over LOS in TWRP to return to stock or do I have to use Odin?
Once flashed will the bootloader remain unlocked to allow me to reinstall LOS?
I got a new screen installed and it appears there may be an issue with how the digitizer interfaces with the software/kernal and going back to stock should update the software to allow the screen to function normally then allowing me to reflash LOS.
Hey Everyone,
Thanks for all your great work on the Galaxy S5. This thing is still kicking! I know I'm way behind on what's been going on. I'm still back on the TowelRoot days. The time has come to finally update my phone because some of the apps won't work anymore. I'm not into ROMs and stuff, I just want the latest firmware without all the bloatware. I had originally gone the TowelRoot method because people were having such a hard time with battery life (me included) with Lollipop. I was fortunate enough to get TowelRoot before updating to the newer version of Lollipop and went back to KitKat and I've been there ever since.
I'm currently on G900VVZW1ANCG (Kitkat 4.4.2) with root access and superuser. I have a CID 15 emmc which is a good thing from all the research I've been doing on XDA.
That's where I get stuck and confused with the newer stuff that's going on. Do I even need to unlock the bootloader?
In the end, I don't mind wiping the entire phone, I just want to get to the latest Marshmallow (which this thread seems to have) without all the bloatware or the ability to delete all the bloatware.
nickbike1 said:
Hey Everyone, Thanks for all your great work on the Galaxy S5. This thing is still kicking! I know I'm way behind on what's been going on. I'm still back on the TowelRoot days...
Click to expand...
Click to collapse
Welcome back!
You had asked some questions that is actually 2 separate ones upon themselves and I'll, hopefully, try to answer them...
Question 1: Should you unlock the bootloader?
Answer 1: The only need for anyone to require this is if they want to perform something outside the scope of just Rooting a device.
What I mean is... for example, if an individual would like to install a Custom Recovery and/or Firmware then you will need to unlock the bootloader.
Question 2: You would, ultimately, like to just debloat the Firmware?
Answer 2: Debloating Stock Firmware only requires root and not an unlocked bootloader.
The proper rooting of a device just means that you will be able to modify areas of the root directory that's restricted for devices without root and Debloating falls into this category.
Just an FYI regarding the following 2:
1) The 2 differences between the CID11 & CID15...
GS5 with CID11 = Toshiba EMMC
GS5 with CID15 = Samsung EMMC
2) There are a handful of Custom Firmwares that are based upon the stock Firmware that is already Debloated. Some of them only requires a Rooted device and Some requires an unlocked bootloader and recommends a Custom Recovery like TWRP.
This is just a brief summary to help you further but, I would recommend that you take note of/highlight the following 2threads that would be a bit more helpful depending on what your looking to do.
https://forum.xda-developers.com/showthread.php?t=2700073
https://forum.xda-developers.com/showthread.php?t=3561529
Good Luck!
~~~~~~~~~~~~~~~
I DO NOT provide support via PM unless asked/requested by myself. PLEASE keep it in the threads where everyone can share.
From this post here, I think the way to get this done for an unlocked bootloader is:
- flash the HOME_No version using Odin 3.12 AP option
- flash TWRP via Odin AP
- reinstall Magisk from TWRP and Magisk Manager.
1) Will that work?
2) What’s the most reliable tool for creating a backup—a) in case I screw up, AND b) in case everything goes well, so I can restore my apps and data into the new clean phone, preferably without screwing up the new clean phone?
I have a G900V.05 on QB2, rooted and unlocked bootloader and custom recovery, that I got to using this method by jrkruse and a false start via another method. So I’ve got Titanium Backup, TWRP, and FlashFire all in play. I'll probably shoot out backups from all of them, not sure which one restores best or if FlashFire survives the update.
Full System Backup method needed!
BigBird9906 said:
From this post here, I think the way to get this done for an unlocked bootloader is:
- flash the HOME_No version using Odin 3.12 AP option
- flash TWRP via Odin AP
- reinstall Magisk from TWRP and Magisk Manager.
1) Will that work?
2) What’s the most reliable tool for creating a backup—a) in case I screw up, AND b) in case everything goes well, so I can restore my apps and data into the new clean phone, preferably without screwing up the new clean phone?
I have a G900V.05 on QB2, rooted and unlocked bootloader and custom recovery, that I got to using this method by jrkruse and a false start via another method. So I’ve got Titanium Backup, TWRP, and FlashFire all in play. I'll probably shoot out backups from all of them, not sure which one restores best or if FlashFire survives the update.
Click to expand...
Click to collapse
1) -Yes, I just tried it, and it works perfectly! The only correction - you have to unzip
G900VVRU2DQL1_G900VVZW2DQL1_G900VVRU2DQL1_HOME_No_Aboot.tar.md5.zip file and flash md5 file with Odin (Odin won't work with that zip file).
2) -I have exactly the same question to fellow members - what is the current most simple and reliable method of full system backup (like ghost image for PC)? I want to try Lineage, but I already spent many hours on system customization (applications, app settings, accounts with login names/passwords, etc.). I really need some fast method to revert phone back to QL1 with all my current setup. I will flash again System and TWRP from Odin, and Magisk from TWRP. How can I then restore my full setup with one click? I used to use 'Titanium Backup' in the past, but that is not an option anymore. It freezes every time when I try to restore 'All apps with system data'
Thank you for reading that and for any possible advices.
So, if I have an unlocked bootloader, will it stay unlocked if I flash the boot from the "Developer Bootloader Friendly/No Aboot No-Wipe Firmware" version? Will it upgrade the baseband to the latest version as well?
Nerva said:
So, if I have an unlocked bootloader, will it stay unlocked if I flash the boot from the "Developer Bootloader Friendly/No Aboot No-Wipe Firmware" version? Will it upgrade the baseband to the latest version as well?
Click to expand...
Click to collapse
If your looking for the Baseband Modem Firmware, the following link has them all for the G900V and won't affect what you have (i use them on my Unlocked G900V to update the Modem Baseband Firmware and I've got TWRP and LineageOS).
[BASEBAND-FIRMWARE-MODEMS]Verizon Samsung Galaxy S5 {SM-G900V/KLTEVZW}[ODIN] by Ibuprophen
Good Luck!
~~~~~~~~~~~~~~~
I DO NOT provide support via PM unless asked/requested by myself. PLEASE keep it in the threads where everyone can share.
Thanks. Are the baseband modem firmware also included in the QL1 "Developer Bootloader Friendly/No Aboot No-Wipe Firmware"? I've been told I should upgrade both my modem and bootloader, but I don't want to re-lock my unlocked bootloader.
WTF?? I was running TWRP 3.2.1.0 and crDroid 7.1.2, and I used Odin to flash the "Developer Bootloader Friendly/No Aboot No-Wipe Firmware" and checked the BL and CP options, which I thought should update just the bootloader and modem, and now it boots up with the Samsung logo and then the Verizon logo, and then just sits there. I tried to go to recovery so I could restore a backup, but it looks like the stock recovery. What did I do wrong and how do I fix it??
Since crDroid 7.1.2 is older than the bootloader, I'm wondering if that's the issue. I do have crDroid 8.1 on the microSD card. I also have TWRP 3.2.1.0 on the microSD card. So I'm wondering if I can use the stock recovery to flash TWRP. I haven't played around with custom ROM's in four years, but prior to that I did it all the time, so apparently I now remember just enough to be dangerous...
@Nerva, I apologize for the delay but, I'm curious to know where, why and what gave you the impression that you were/was required, on your your working device, to update your devices bootloader???
I'm just perplexed about this...
~~~~~~~~~~~~~~~
I DO NOT provide support via PM unless asked/requested by myself. PLEASE keep it in the threads where everyone can share.
I went back and tried to find where I read it, and at the very least it was in this post:
godofsalt said:
Yep all true. .... But....
Once he sends you the info (model numbers and such) might want to also double check that he is on the latest firmware, for his devise. Important!
All reads good. If it's rather, "New" then, I would keep it as well.
Click to expand...
Click to collapse
I think I saw it someplace else as well, but I haven't stumbled across it -- I was posting a lot of questions in a lot of threads as well as PMing people.
Nerva said:
I went back and tried to find where I read it, and at the very least it was in this...
Click to expand...
Click to collapse
Your situation prompted me to confirm what I knew and others that you can see on the recent posts on the following thread...
https://forum.xda-developers.com/showthread.php?t=2259645
... I just wanted to state that if your devices bootloader was already unlocked and the device wasn't bricked (or similar) then you should not need to update the bootloader or it'll lock it up again and, potentially, can even cause FRP issues as well. Luckily your FRP didn't trip and the device was able to be unlocked again.
I have the same device that was unlocked a long time ago and never ever needed its bootloader updated.
Your question regarding the Baseband Modem Updates...
Those are the Modem files extracted from the stock Firmware and only updates the devices Modem. That controls the WiFi, Carrier Data, etc...
This is similar to updating the Drivers for something specific on a PC (like the PC LAN, WiFi, Video Card, etc... ).
When you had flashed what you did on your device, you basically flashed an optimized version of the Stock Firmware. This is why you saw the Samsung Boot Screen.
I hope that I had explained this okay via text...
~~~~~~~~~~~~~~~
I DO NOT provide support via PM unless asked/requested by myself. PLEASE keep it in the threads where everyone can share.
I'm curious, if the bootloader version has so little importance for us custom-ROM users, why does Samsung/Verizon update their bootloader versions -- to what purpose?
It looks like this website will generate a cf-auto-root package for QL1:
https://desktop.firmware.mobi/device:840/firmware:14884
I'm wondering if I flash that with Odin, would it upgrade my current unlocked QB2 to an unlocked QL1?
Nerva said:
I'm curious, if the bootloader version has so little importance for us custom-ROM users, why does Samsung/Verizon update their bootloader versions -- to what purpose?...
Click to expand...
Click to collapse
I'm not stating that Bootloaders doesn't get updated upon themselves but, they specifically seldom require it.
One way to look at it is that the function of the bootloader is allot like the BIOS of a PC. They both handle the boot process and seldomly require to be updated specifically.
When a new Stock Firmware version is released, the bootloader is only updated accordingly to reflect the updates of the firmware. This reflection is to protect the device from being updated to an incompatible firmware version.
In short, when the bootloader is unlocked, the bootloader still protects the device from an incompatible firmware from being installed but, it being unlocked just bypasses the "Samsung Stock firmware only" restriction.
TWRP is just the conduit between the Firmware and the bootloader that just handles the communication between the bootloader and the Firmware.
.
I'm wondering if I flash that with Odin, would it upgrade my current unlocked QB2 to an unlocked QL1?
Click to expand...
Click to collapse
If you flash the firmware, your just going to relock your bootloader and be back to stock.
To get the QL1, just flash the Baseband Modem Update from the following link and you'll be good to go and you'll see this in your device info.
[BASEBAND-FIRMWARE-MODEMS]Verizon Samsung Galaxy S5 {SM-G900V/KLTEVZW}[ODIN] by Ibuprophen
Have I clarified this okay?
~~~~~~~~~~~~~~~
I DO NOT provide support via PM unless asked/requested by myself. PLEASE keep it in the threads where everyone can share.
Hi
Please can someone help. I have just got a Samsung galaxy s7 and was trying to get back some pictures I accidentally deleted using a program called Dr Fone. I followed the instructions and didn't realise I was possibly rooting my phone
The phone is on Status custom and I just want to restore it to how it was originally. I have reset to factory settings but this hasn't corrected it. I am constantly getting a security notice about unauthorised actions
I am not very technical so if anyone could help please give the exact links for where I can download a program to repair this - I have read about a program called Odin but not sure exactly where or how to find this. Does this need to be installed on a computer or phone?
Some more information on the phone is that it's a UK phone. Firmware CSC code is BTU if that helps. It's an S7 SM-G930F
As I said I am not very technical so please can anyone help and if possible provide a step by step guide for what to do that would be amazing
Thank you, David
Odin is a desktop application, it is uses to flash firmware onto your phone. By flashing stock firmware you'd get your device back to stock (excluding KNOX and FRP)
Here's a detailed guide on what Odin is and how to use it https://updato.com/how-to/how-to-install-an-official-samsung-stock-firmware-using-odin
You can use that site to get the firmware for your device by region and carrier.
Ok great thanks
Please can you tell.me what excluding KNOX and FRP means?
I will give this a go. Have started the download for step 3. This download seems to be taking a couple of hours. Do you know roughly how long it takes to put everything on the phone once the download if complete?
I may have to leave the actual installation until tomorrow if it takes a long time.
Thanks again for all you help
KNOX is a way for Samsung to check if you have altered the firmware. Flashing custom firmware and/or rooting trips the KNOX counter, and will void warranty and disable some Samsung apps.
FRP is factory reset protection, if prevents someone from being able to steal your phone and get access by factory resetting. Even after a factory reset, FRP is intact and will require the original google account to do the device setup. So make sure you know your credentials, or delink your account before flashing.
Both are part of the firmware that can't be modified or reverted.
Updato can be quite slow to download, sammobile.com is another site but also slow in my experience. The flashing process takes about 15 minutes on your PC, but the phone can sit on the Samsung splash screen for 15 or so minutes as well.
Beanvee7 said:
KNOX is a way for Samsung to check if you have altered the firmware. Flashing custom firmware and/or rooting trips the KNOX counter, and will void warranty and disable some Samsung apps.
FRP is factory reset protection, if prevents someone from being able to steal your phone and get access by factory resetting. Even after a factory reset, FRP is intact and will require the original google account to do the device setup. So make sure you know your credentials, or delink your account before flashing.
Both are part of the firmware that can't be modified or reverted.
Updato can be quite slow to download, sammobile.com is another site but also slow in my experience. The flashing process takes about 15 minutes on your PC, but the phone can sit on the Samsung splash screen for 15 or so minutes as well.
Click to expand...
Click to collapse
Great thanks for all your help so far. I have completed the ODIN update and got the green pass. The phone is trying to boot up and is saying it is encrypted for security and asking for a password. When I put what I thought was the password in it doesnt seem to accept it, is there any way around this?
I read on another message to try the password default_password but this hasnt worked
I have realised that when I flashed the AP download to the phone that there were 4 other files that were downloaded after I unzipped it. Do I put these into ODIN too?
Thanks again
Davifgmmm678 said:
Great thanks for all your help so far. I have completed the ODIN update and got the green pass. The phone is trying to boot up and is saying it is encrypted for security and asking for a password. When I put what I thought was the password in it doesnt seem to accept it, is there any way around this?
I read on another message to try the password default_password but this hasnt worked
I have realised that when I flashed the AP download to the phone that there were 4 other files that were downloaded after I unzipped it. Do I put these into ODIN too?
Thanks again
Click to expand...
Click to collapse
There are 5 files. You have to flash 4 BL, AP, CP, CSC (not home-csc !) Keep in mind if you previously had firmware from January 2018 and up you can only flash equal or newer firmware.
Domino5 said:
There are 5 files. You have to flash 4 BL, AP, CP, CSC (not home-csc !) Keep in mind if you previously had firmware from January 2018 and up you can only flash equal or newer firmware.
Click to expand...
Click to collapse
ah great thanks, I think that was the mistake I made. I have an S7 and originally downloaded version 7.0 am now downloading version 6.0.1 which I think is correct for an S7?
Davifgmmm678 said:
ah great thanks, I think that was the mistake I made. I have an S7 and originally downloaded version 7.0 am now downloading version 6.0.1 which I think is correct for an S7?
Click to expand...
Click to collapse
6.0.1 is old Android Marshmallow better do not downgrade. There is latest 7.0 Nougat for GB BTU https://updato.com/firmware-archive-select-model?record=CE58E60E0EEF11E89F15FA163EE8F90B
Domino5 said:
6.0.1 is old Android Marshmallow better do not downgrade. There is latest 7.0 Nougat for GB BTU https://updato.com/firmware-archive-select-model?record=CE58E60E0EEF11E89F15FA163EE8F90B
Click to expand...
Click to collapse
thanks thats the one I downloaded earlier - will try again with all 4 BL, AP, CP, CSC on ODIN
Thanks so much for continuing to reply - I know I'm useless but im worried I cant use my new phone again!
Hi guys, i have a galaxy s7 of a customer that doesn't absolutely remember email and password for his google account connected to the phone(and so it's OEM Locked).
i tried to follow many guides on the forum but this happened:
i can't root the phone (because the FRP is locking the Flash),
nor install 6.0.1 (because of the error "sw rev check fail device 2 binary 1")
i can't use bluetooth method to skip setup guide (it was fixed in 6.0.1)
i can't use RealTerm because it can't make me save the number to proceed the guide(also fixed in 6.0.1)
what can i do? how do i bypass the FRP? or how do I downgrade to 6.0.1?
Downgrading can be a problem caused by the bootloader, make sure you try to flash a stock ROM with the same version bootloader as shown with this number
G930FXXU2ERD5
The customer would have had to enter a secondary / recovery email while making that Google account, tell them to check their other email addresses for confirmation emails around the time they set up the phone, then they can find the email address of the google account and reset the password to that email address
You have to downgrade to 6.0 and then there are plenty of ways to unlock.
Download 6.0 and latest firmware.
In Odin
1st and 3rd field from old firmware
2nd and 4th field from new firmware
If You need guide how to unlock from 6.0 let me know
LaHunnid said:
You have to downgrade to 6.0 and then there are plenty of ways to unlock.
Download 6.0 and latest firmware.
In Odin
1st and 3rd field from old firmware
2nd and 4th field from new firmware
If You need guide how to unlock from 6.0 let me know
Click to expand...
Click to collapse
1st and 3rd field in ODIN is Bootloader & Modem
If you flash new firmware to 2nd and 4th you'll end up with new firmware flashed with old bootloader and it won't boot most likely / brick
*Detection* said:
1st and 3rd field in ODIN is Bootloader & Modem
If you flash new firmware to 2nd and 4th you'll end up with new firmware flashed with old bootloader and it won't boot most likely / brick
Click to expand...
Click to collapse
I did that and it didn't brick
LaHunnid said:
I did that and it didn't brick
Click to expand...
Click to collapse
AP is the system / OS, you're telling OP to flash a new version of Android (AP) with an old bootloader, in order to downgrade to 6.0.1, your method would not downgrade anything other than bootloader & modem and old bootloader with new OS will almost certainly brick
To downgrade you need to flash old bootloader (BL) & old Android 6.0.1 (AP), and probably old modem (CP), CSC is the only thing left
And as already stated, downgrading the BL is the problem that prevents most people from downgrading in the first place
check out my tutorial https://forum.xda-developers.com/galaxy-s7/how-to/g930f-frp-unlock-helps-99-g930f-t3791424
Massive thanks
S6unbricker said:
check out my tutorial https://forum.xda-developers.com/galaxy-s7/how-to/g930f-frp-unlock-helps-99-g930f-t3791424
Click to expand...
Click to collapse
I've been absolutely stuck for days trying to sort out the bloody FRP lock on an S7 (SM-G930F) that had been gifted to my wife by my father-in-law where he hadn't removed the accounts before passing it over.
My wife then did an update that the phone requested when it started up and that went wrong at which point I get involved and factory reset it...oh BIG mistake... and that's where my problems started made worse by the fact my father-in-law couldn't remember which account he had setup on the phone....or even the password to possible accounts!! I consider myself to be well versed in all things tech but I had absolutely no idea FRP existed and was absolutely baffled when i saw the message on the screen after flashing the stock firmware (G930FXXU2DRB6) that was on there according to the recovery mode. I've been trying so many different things over the past week all current methods failed...then I came across this one...which had seemed to be blocked by admins but I was able to click on the link in the 2nd post and grab the password from the readme in the first, which i must admit made it a bit dubious and not sure why @S6unbricker felt the need to do that but there's no issues it doesn't go to a stupid survey site or anything it just goes to a text file on mega which has one line and that's the password!
I followed the method to the letter and, to my surprise and joy, it's actually worked a treat...the S7 is no longer a paper weight!!!
Massive thanks to @S6unbricker :good: ...any chance of re-posting but without the password on the file or putting the password in the post?
Frp doesn't block eng bootloader...after u flash eng boot u can simply use Abd command to remove. Or the longer method flash factory binaries. Enable oem unlock (most important part). Then flash stock rom make sure to remove userdata.img ....on a side note wondering if adding the Samsung retail app and activating it, then using the login data to remove the app via factory data reset might work.
deshaney said:
Frp doesn't block eng bootloader...after u flash eng boot u can simply use Abd command to remove. Or the longer method flash factory binaries. Enable oem unlock (most important part). Then flash stock rom make sure to remove userdata.img ....on a side note wondering if adding the Samsung retail app and activating it, then using the login data to remove the app via factory data reset might work.
Click to expand...
Click to collapse
From my experience the combination roms (which I presume you are referring to when you say eng bootloader) didn't solve my issue. Yes I could get them on the phone and boot into them, change the settings or use adb but obviously I don't want the factory binary to stay on there so as soon as I flashed it back to the current firmware, back to square one!
Most poeple advised to use HOME CSC instead of CSC when flashing from combination rom back to stock but I couldn't get odin to flash with HOME CSC.
No I'm referring to the boot.img file. Combination ROMs don't enable su access via she'll.
Samsung s7
Ok I know this is an old Post but I'm brand new to Odin and all the unlock lingo.. can anyone explain to me how to downgrade to bypass the frp on my Galaxy I just bought , I'm very tech savvy just need a walkthrough any help would be greatly appreciated
Hello,
Like many users on this forum, I updated my brand new S8+ to Pie/OneUI and I hate it.
However, i've been digging on the forum for quite a while and I can't find a clear answer.
Would flashing the official Oreo ROM via ODIN void my warranty?
And where can I find the official ROM for my particular version of the phone?
--EDIT-- I found it on updato, thanks to a thread i missed
Any help would be greatly appreciated
SIHS said:
Hello,
Like many users on this forum, I updated my brand new S8+ to Pie/OneUI and I hate it.
However, i've been digging on the forum for quite a while and I can't find a clear answer.
Would flashing the official Oreo ROM via ODIN void my warranty?
And where can I find the official ROM for my particular version of the phone?
--EDIT-- I found it on updato, thanks to a thread i missed
Any help would be greatly appreciated
Click to expand...
Click to collapse
No it won't void your warranty/Trip Knox.
You can download firmware from either sammobil.com or updato.com these are the two i generally use. ( I see you've found it )
If you do downgrade remember to disable software updates so that you don't go back to pie again.
spawnlives said:
No it won't void your warranty/Trip Knox.
You can download firmware from either sammobil.com or updato.com these are the two i generally use. ( I see you've found it )
If you do downgrade remember to disable software updates so that you don't go back to pie again.
Click to expand...
Click to collapse
I read that there's a way to downgrade like it's an update and keep all data and apps installed (via the HOME file on ODIN), is it real?
SIHS said:
I read that there's a way to downgrade like it's an update and keep all data and apps installed (via the HOME file on ODIN), is it real?
Click to expand...
Click to collapse
Firstly before doing anything I recommend doing a backup first. I don't have a preferred method but you could use cloud based service (Google/Samsung) or something like samsung's smartswitch.
You will need to unzip the firmware that you downloaded. In it will be 5 files which will have to be place in the correct sections of Odin.
There will be 2 CSC files:
CSC - clean install will wipe apps and data ( same as a factory reset )
Home_CSC - dirty install will keep your apps and data.
If downgrading you will need the same or higher bootloader version. The BL number is the 5th number from the right of the firmware name you download.
Hi XDA, first time poster and I could not find a similar thread with the answers I was looking for, if that thread exists I apologize!
So basically I started a job in a retail phone shop a few months back. We have a drawer in store that has a bunch of old demo units in there that, once they have been removed from display, just sit there unused. There is phones in there from almost 10 years ago. They are never given back or requested back, nor are they logged in any way.
Well I noticed there was an almost perfect condition S21+ in there so I asked my manager if we could use it as a sales incentive and he replied saying the phones are useless because of the software on them. I said I was pretty sure you could remove the retail software and use it as a normal phone and he said if I can do that and get it working, I can take the phone for myself.
Well, I took it home and did some digging / experimenting. The phone has a proper IMEI already, you can put a SIM into the phone and it registers to the network. The problem is, the phone has security restrictions on data sharing and it does not have the playstore on it and there is no factory data reset option in the settings, nor in recovery mode.
I have tried flashing a stock firmware on using Odin which I thought worked, however when the phone restarts and you go through set up, Samsung Knox pops up and installs settings which forces the phone to set up in retail mode again with the same restrictions as previous (no play store, factory reset etc).
Any idea how to get around this issue? I would have thought flashing stock software would be the obvious work around but something on the phone forces it to install on retail mode every time.
Any advice on this is much appreciated.
Frostyb said:
Hi XDA, first time poster and I could not find a similar thread with the answers I was looking for, if that thread exists I apologize!
So basically I started a job in a retail phone shop a few months back. We have a drawer in store that has a bunch of old demo units in there that, once they have been removed from display, just sit there unused. There is phones in there from almost 10 years ago. They are never given back or requested back, nor are they logged in any way.
Well I noticed there was an almost perfect condition S21+ in there so I asked my manager if we could use it as a sales incentive and he replied saying the phones are useless because of the software on them. I said I was pretty sure you could remove the retail software and use it as a normal phone and he said if I can do that and get it working, I can take the phone for myself.
Well, I took it home and did some digging / experimenting. The phone has a proper IMEI already, you can put a SIM into the phone and it registers to the network. The problem is, the phone has security restrictions on data sharing and it does not have the playstore on it and there is no factory data reset option in the settings, nor in recovery mode.
I have tried flashing a stock firmware on using Odin which I thought worked, however when the phone restarts and you go through set up, Samsung Knox pops up and installs settings which forces the phone to set up in retail mode again with the same restrictions as previous (no play store, factory reset etc).
Any idea how to get around this issue? I would have thought flashing stock software would be the obvious work around but something on the phone forces it to install on retail mode every time.
Any advice on this is much appreciated.
Click to expand...
Click to collapse
Have you tried following the steps in a video such as this?
DO THIS COMPLETELY AT YOUR OWN RISK! I AM NOT RESPONSIBLE IF ANYTHING GOES WRONG, INCLUDING BUT NOT LIMITED TO BRICKING YOUR DEVICE, GETTING A VIRUS OR STARTING A LITERAL WAR.
Everything i was able find on the subject was kind of sketchy-looking (probably because doing this without permission would probably be illegal) so I included a warning.
BloodyFruitDestroyer said:
Have you tried following the steps in a video such as this?
DO THIS COMPLETELY AT YOUR OWN RISK! I AM NOT RESPONSIBLE IF ANYTHING GOES WRONG, INCLUDING BUT NOT LIMITED TO BRICKING YOUR DEVICE, GETTING A VIRUS OR STARTING A LITERAL WAR.
Everything i was able find on the subject was kind of sketchy-looking (probably because doing this without permission would probably be illegal) so I included a warning.
Click to expand...
Click to collapse
Thanks for the reply!
So I also came across this same video on the subject last night, it seems to be a workaround for bypassing Knox but I couldnt find any further info on what kind of state that leaves the phone in after, if it can still get official updates and such or if it triggered to eFuse that causes you to lose access to Samsung Pay and other official apps.
I'm aware this is at my own risk, the phone will sit in a drawer if I cant figure it out any way so no harm no foul as far as I can see. I've thought about rooting the device (I know this will trigger the eFuse) but I cant find any info on if that would get around the specific issue I'm having of Knox forcing the phone to install in retail settings or not so do not want to go down that road just yet.
Frostyb said:
Thanks for the reply!
So I also came across this same video on the subject last night, it seems to be a workaround for bypassing Knox but I couldnt find any further info on what kind of state that leaves the phone in after, if it can still get official updates and such or if it triggered to eFuse that causes you to lose access to Samsung Pay and other official apps.
I'm aware this is at my own risk, the phone will sit in a drawer if I cant figure it out any way so no harm no foul as far as I can see. I've thought about rooting the device (I know this will trigger the eFuse) but I cant find any info on if that would get around the specific issue I'm having of Knox forcing the phone to install in retail settings or not so do not want to go down that road just yet.
Click to expand...
Click to collapse
I'd say that the Knox workaround would probably (do not quote me on that) leave you with un-tripped Knox (=e-fuse intact) if it even still is. Even if Knox would be tripped, you would still most likely be able to get software updates. But because you said that you have already used Odin successfully on the device, that would lead me to believe that OEM unlocking might already be on in which case there probably isn't any more to lose by rooting the device. On a rooted device there are instructions o WikiHow on how to remove the Knox , but I haven't personally tested them. If I were you, I'd check with a Knox warranty checker app or through recovery mode, etc
whether the e-fuse is already triggered before continuing with anything.
And if I confused you, feel free to ask anything!
With the root approach you would also have to worry about passing Safety Net, but that'll only be relevant if you decide to go with that path.
BloodyFruitDestroyer said:
I'd say that the Knox workaround would probably (do not quote me on that) leave you with un-tripped Knox (=e-fuse intact) if it even still is. Even if Knox would be tripped, you would still most likely be able to get software updates. But because you said that you have already used Odin successfully on the device, that would lead me to believe that OEM unlocking might already be on in which case there probably isn't any more to lose by rooting the device. On a rooted device there are instructions o WikiHow on how to remove the Knox , but I haven't personally tested them. If I were you, I'd check with a Knox warranty checker app whether the e-fuse is already triggered before continuing with anything.
And if I confused you, feel free to ask anything!
Click to expand...
Click to collapse
Interesting, I may give the workaround a shot when I get home later then.
So I have used Odin but it was with official firmware obtained through Frija and, according to reading, that does NOT trip the eFuse. I did turn on OHD in dev options but from what I can tell, the fuse is only tripped when you load an unofficial image onto the device which I havent done yet. I can check when I get home by booting into recovery mode and checking the warranty line AFAIK it will say either 1 or 0 indicating if it's been tripped or not.
So my issue with rooting is I dont know if I root, will the phone still install in the retail setup that it does currently. I know I can run apps or code to remove Knox once rooted, but I dont know if then just reinstall firmware and it will be back to default like I want, or if I'll then need to figure out how to get the playstore loaded, if the security issues persist etc. Also as far as I can tell to root, I need to install Magisk on the device first to alter one of the image files, then move that file back to the PC to flash with Odin, and I'm not sure I can do that with the retail settings enabled.
Frostyb said:
Interesting, I may give the workaround a shot when I get home later then.
So I have used Odin but it was with official firmware obtained through Frija and, according to reading, that does NOT trip the eFuse. I did turn on OHD in dev options but from what I can tell, the fuse is only tripped when you load an unofficial image onto the device which I havent done yet. I can check when I get home by booting into recovery mode and checking the warranty line AFAIK it will say either 1 or 0 indicating if it's been tripped or not.
So my issue with rooting is I dont know if I root, will the phone still install in the retail setup that it does currently. I know I can run apps or code to remove Knox once rooted, but I dont know if then just reinstall firmware and it will be back to default like I want, or if I'll then need to figure out how to get the playstore loaded, if the security issues persist etc. Also as far as I can tell to root, I need to install Magisk on the device first to alter one of the image files, then move that file back to the PC to flash with Odin, and I'm not sure I can do that with the retail settings enabled.
Click to expand...
Click to collapse
I am interested in how this develops. Please keep me updated with the warranty byte status and whether the workaround is successful!
BloodyFruitDestroyer said:
I am interested in how this develops. Please keep me updated with the warranty byte status and whether the workaround is successful!
Click to expand...
Click to collapse
So quick update on this: none of the workaround videos on youtube seem to be capable of doing anything. They all rely on being able to connect to Wifi then get around the device before Knox settings apply, however on my build as SOON as you connect to wifi, it immediately starts applying knox settings and cannot be skipped.
I am wondering if this is because the version of software I flashed on using Odin was the most recent firmware, being android 12, and most of these workarounds are for android 11? Is it safe to locate the original firmware for the S21+ somewhere and flash that on to the device instead do you think?
Also the eFuse is still currently in tact.
Frostyb said:
So quick update on this: none of the workaround videos on youtube seem to be capable of doing anything. They all rely on being able to connect to Wifi then get around the device before Knox settings apply, however on my build as SOON as you connect to wifi, it immediately starts applying knox settings and cannot be skipped.
I am wondering if this is because the version of software I flashed on using Odin was the most recent firmware, being android 12, and most of these workarounds are for android 11? Is it safe to locate the original firmware for the S21+ somewhere and flash that on to the device instead do you think?
Also the eFuse is still currently in tact.
Click to expand...
Click to collapse
You could flash an older Android version, but if and only if it has the same bootloader version as the current one, otherwise it won't work and might even brick your device. I am unsure though if the downgrade would help but if the bootloader versions match, you can try!
On SamMobile.com you can see older versions of firmware. Just check the bootloader version before flashing!
BloodyFruitDestroyer said:
You could flash an older Android version, but if and only if it has the same bootloader version as the current one, otherwise it won't work and might even brick your device. I am unsure though if the downgrade would help but if the bootloader versions match, you can try!
On SamMobile.com you can see older versions of firmware. Just check the bootloader version before flashing!
Click to expand...
Click to collapse
So this may seem like a dumb question but how do I check to make sure the bootloader version matches?
Frostyb said:
So this may seem like a dumb question but how do I check to make sure the bootloader version matches?
Click to expand...
Click to collapse
It's most likely as simple as comparing the bootloader filenames between the Odin flashable files for the old and new software. I could verify whether that's the case if you send the filenames for both bootloader files here. (The file that goes into the BL slot in Odin)
BloodyFruitDestroyer said:
It's most likely as simple as comparing the bootloader filenames between the Odin flashable files for the old and new software. I could verify whether that's the case if you send the filenames for both bootloader files here. (The file that goes into the BL slot in Odin)
Click to expand...
Click to collapse
So the first image is of the current firmware that successfully flashed to my device via Odin.
The second is firmware from August 2021 that is on a build of Android 11. You can also see by the file modification dates.
What were your exact model and region again? Probably won't matter, please wait a minute
BloodyFruitDestroyer said:
What were your exact model and region again?
Click to expand...
Click to collapse
BloodyFruitDestroyer said:
What were your exact model and region again? Probably won't matter, please wait a minute
Click to expand...
Click to collapse
SM-G996B
Region is Ireland (CSC is MET)
Yeah, it seems like the current bootloader is version 4 while the Android 11 one is version 3 so these versions seem, unfortunately, incompatible.
Frostyb said:
SM-G996B
Region is Ireland (CSC is MET)
Click to expand...
Click to collapse
Hi there, I can help you out! I have some experience with Samsung.
So first off, I take it this is an Exynos model? Snapdragons require the use of a paid service to get an unlock.
It seems you've flashed stock firmware before but it didn't work out due to Knox. Did you flash all the files including the CSC (wipe all data) file? Also, you could try flashing TWRP and that would trip Knox, at which point Knox is disabled due to detecting system modifications or it will try to rollback your modifications.
So the only thing I personally can think of to get rid of the problem is going the TWRP route, but this will trip the Knox warranty byte to 0x1, so think about it. There might be someone more experienced than me that might be able to help without tripping Knox, but this is right now the only thing I can personally suggest to fix the problem.
Edit: It seems like someone more experienced appeared while I was writing this! Sweet!
BloodyFruitDestroyer said:
So the only thing I personally can think of to get rid of the problem is going the TWRP route, but this will trip the Knox warranty byte to 0x1, so think about it. There might be someone more experienced than me that might be able to help without tripping Knox, but this is right now the only thing I can personally suggest to fix the problem.
Frostyb said:
SM-G996B
Region is Ireland (CSC is MET)
Click to expand...
Click to collapse
Click to expand...
Click to collapse
Are you able to enable developer options? If so, you might be able to use ADB commands to disable the Retail Mode app. I doubt they're enabled though.
BloodyFruitDestroyer said:
Yeah, it seems like the current bootloader is version 4 while the Android 11 one is version 3 so these versions seem, unfortunately, incompatible.
Click to expand...
Click to collapse
Dammit, so it seems I'm stuck on Android 12 and there is no way to get back to a previous version then I take it?
Frostyb said:
Dammit, so it seems I'm stuck on Android 12 and there is no way to get back to a previous version then I take it?
Click to expand...
Click to collapse
With official firmware, I'd be pretty certain that you can't. By the way, please look at the latest messages as there is someone else with fresh ideas here, too.