Related
I've gotten no help at all with this. Very unlike this forum. My phone is a kltevew, which is straight talks version of a g900v. I need help, there are lots of great looking Roms that require you to have mm firmware I'd like to try!
Not sure why I'm getting g no responses on this. Surely someone must know something... The only response I got was not only not helpful but jerky and obnoxious. Doesn't anyone know how to upgrade the firmware on my phone? (And no, google has no answers for me on this.. I look everyday)
ddjr said:
Not sure why I'm getting g no responses on this. Surely someone must know something... The only response I got was not only not helpful but jerky and obnoxious. Doesn't anyone know how to upgrade the firmware on my phone? (And no, google has no answers for me on this.. I look everyday)
Click to expand...
Click to collapse
Download it with samfirm http://forum.xda-developers.com/galaxy-tab-s/general/tool-samfirm-samsung-firmware-t2988647 (Model= SM-G900V Region= VZW) or from sammobile http://www.sammobile.com/firmwares/database/SM-G900V/ , do you know how to flash firmware with odin?
I do. Thanks so much for responding. Every time I try with Odin, a few different releases, it always gives me the error message fail. Can it be done with flashfire?
What stands in the log of odin when the flash completes?
Ill have to do it again to see... Be back in a bit!
I think it says FAIL! modem but I'll have to run it again... Brb
Last night I used flash fire to install firmware. That didn't get past the red Verizon logo, so I put twrp on it with Odin. Twrp showed it as dpd1, but it just wouldn't boot. So I wiped it once and flashed a ROM that requires mm firmware. Same thing, justbootloop. So I put stock back on it, then mokee 6.0.1. which works, I'm just not on mm firmware and all the great new roms are still unavailable to me.
ddjr said:
Last night I used flash fire to install firmware. That didn't get past the red Verizon logo, so I put twrp on it with Odin. Twrp showed it as dpd1, but it just wouldn't boot. So I wiped it once and flashed a ROM that requires mm firmware. Same thing, justbootloop. So I put stock back on it, then mokee 6.0.1. which works, I'm just not on mm firmware and all the great new roms are still unavailable to me.
Click to expand...
Click to collapse
Have you enabled the option to flash bootloader on flashfire setting?
What? No, I haven't... but do do right now. Thanks for the tip! Actually, where would I find it?
So would I do it in this order? Flash the dpd1 bootloader, then modem, them rom, then jrkruse patch? All in flash fire?
ddjr said:
So would I do it in this order? Flash the dpd1 bootloader, then modem, them rom, then jrkruse patch? All in flash fire?
Click to expand...
Click to collapse
It's in setting of flashfire...but only do it if odin doesn't work because do it from flashfire is more riskiy...
1)do a backup
2)check the bootloader flash option
3)install the firmware with all the wipe except internal storage(it mean that flashfire delete /data excluding /data/media/0 (sdcard) but include it in your backup copy because you never know )
4)wait till reboot skip setup wizard "spamming" the next button then install the rom with flashfire or twrp
On the flashfire site i found this:
Flash bootloaders
"This setting controls if FlashFire will attempt to flash bootloader partitions. By default, bootloader partitions are only read and never written. Even when enabled, flashing bootloader partitions may not succeed - many devices have protections in place against the bootloaders being overwritten.
Please note that flashing bootloaders is extremely dangerous. Any bug, error, or failure may result in an unrecoverable hard-brick. Do not use this feature unless you know exactly what you are doing.
Due to the danger of this feature, it is automatically turned off every time FlashFire starts. You have to manually re-enable it every time you want to use it.
If you must flash bootloaders, it is advised to use a bootloader-based flashing tool such as fastboot or ODIN to do it, as these are the safest methods. OTAs may also update bootloaders, and though slightly less safe than fastboot/ODIN, it is still much safer than having FlashFire flash bootloader partitions directly."
So i suggest to try to flash the firmware directly from odin first
No dice... still doesn't boot up past the red Verizon logo
ddjr said:
No dice... still doesn't boot up past the red Verizon logo
Click to expand...
Click to collapse
did you install the firmware in the "AP" box on odin? (after you factory reset your phone)
I did. At this point guess I'm lucky I haven't bricked my phone. Ive tried every possible combination, nothing works!
ddjr said:
I did. At this point guess I'm lucky I haven't bricked my phone. Ive tried every possible combination, nothing works!
Click to expand...
Click to collapse
Redownload the firmware extract it again,factory reset your phone,and try to install the firmware,maybe it's a bad download
Should I be flashing a kernel too? Will it even start/boot without the right kernel?
find out if you phone is refurbished. to install stock ROM you would need the main board and boot to be the same model.
if it's not, then you just need to install bootloader/modem without full ROM. look around in xda for bootloader/modem.
I just upgraded to the latest G935FXXU1BPH6 using Odin (v3.12.3). With past firmware releases, I was able to load TWRP twrp-3.0.2-2-hero2lte.img.tar using Odin and then proceed to root the phone.
However, with BPH6, TWRP refuses to boot. I try the volume-up+home+power sequence but TWRP recovery never starts. The phone just sits there on the boot screen.
I'm able to recover by re-flashing the BPH6 firmware but this leaves me thinking that the bootloader has changed in BPH6 and twrp 3.0.2-2 is no longer compatible.
1) Anyone else having this issue?
2) Any solutions or workarounds?
3) Do people think it would be safe to dowgrade the bootloader or entire firmware? I'm willing to try it but I'm a little concerned about bricking the phone.
kociubin said:
I just upgraded to the latest G935FXXU1BPH6 using Odin (v3.12.3). With past firmware releases, I was able to load TWRP twrp-3.0.2-2-hero2lte.img.tar using Odin and then proceed to root the phone.
However, with BPH6, TWRP refuses to boot. I try the volume-up+home+power sequence but TWRP recovery never starts. The phone just sits there on the boot screen.
I'm able to recover by re-flashing the BPH6 firmware but this leaves me thinking that the bootloader has changed in BPH6 and twrp 3.0.2-2 is no longer compatible.
1) Anyone else having this issue?
2) Any solutions or workarounds?
3) Do people think it would be safe to dowgrade the bootloader or entire firmware? I'm willing to try it but I'm a little concerned about bricking the phone.
Click to expand...
Click to collapse
In Odin flash an older firmware then reroot and wait for a root update from Chainfire and the TWRP team
I know a couple people that have done that.
"And on that bombshell!"
Sent from my Echoe powered AEL Driven G935F
When I first upgraded to the new firmware, I found the same thing that you did - I wanted to be able to flash custom roms and didn't know when or if TWRP and ROOT was going to be possible with this new firmware - so I used odin and reflashed July's Firmware and I was able to do so without any Issues - so then I decided to try to upgrade the AP/CSC/CP files from the latest update and replaced the bootloader with the bootloader from july's update and it worked.
Good luck - frankly I am Concerned. It appears that the latest bootloader from Samsung is LOCKED - I only hope someone is able to get root and twrp working - and I hope this is not an indication of future issues for rooting samsung phones....
mocsab said:
Good luck - frankly I am Concerned. It appears that the latest bootloader from Samsung is LOCKED - I only hope someone is able to get root and twrp working - and I hope this is not indication of future issues for rooting samsung phones....
Click to expand...
Click to collapse
No it isn't. Korean models had already been incompatible with official TWRP since firmware APG7 and I confirmed it working again when I replaced the kernel inside TWRP with one built from the latest source released by Samsung. So, someone needs to build a new TWRP recovery with BPH6 kernel source and everything will become fine again.
I didnt know that but it is very good news as far as I am concerned.
I have alwasy been fearful that Samsung was going to eventually lock down their international phones like they did to the US Variants - and when this originally happened to me, I started thinking that maybe my worst fears had come true. Thanks for the information....
I have the same question，but i soved it，i Flash the old BL and TWRP can working
BL version ：BL_G935FXXU1APGH_CL8252943_QB10274482_REV00_user
Xlim said:
I have the same question，but i soved it，i Flash the old BL and TWRP can working
BL version ：BL_G935FXXU1APGH_CL8252943_QB10274482_REV00_user
Click to expand...
Click to collapse
pls send related boot loader download link
same iussue .. some news??
by the way to use root now i put the old firmwere
FARSHOOD said:
pls send related boot loader download link
Click to expand...
Click to collapse
https://www.androidfilehost.com/?fid=24671318762848807
When flashing bootloader in Odin there is an options tab, there are checkboxes - Auto Reboot which is checked - Re-Partiion which is unchecked - and - F.Reset Time which is checked, I flashed new bootlaoder and modem and now my phone will not restart no matter the key combination I press. So Are those checkboxes suppose to be checked off or unchecked
Hi everyone,
I am running stock G920FXXU4DPIL (6.0.1) and I want to go back to stock G920FXXU3COI9 (5.1.1).
When I try to flash G920FXXU3COI9 with Odin, it fails at sboot.bin with error "sw rev check fail device 4 binary 3", which is quite normal because Samsung prevents flashing older bootloader over newer bootloader.
So I extracted the content of the stock firmware, removed sboot.bin, cm.bin, modem.bin and repacked a new .tar using android unified toolkit.
Then I flashed the resulting file with Odin.
Flashing worked but now I am stuck at Samsung logo. I cannot enter recovery either.
Only way to soft unbrick the phone is flash stock G920FXXU4DPIL again.
Why ??
I also want to go back to 5.1.1 as I don't like MM and N is also not too stable. so I have struggled alot tried 15 different firmwares from all regions but no luck all of them fails at sboot.bin device 5 binary 4 at last I flashed lollipop based zips and they also stuck at bootlogo. There is a combination firmware 5.1.1 with engineered bootloader which allow you to downgrade but fingerprint sensor don't work .
qasim799 said:
I also want to go back to 5.1.1 as I don't like MM and N is also not too stable. so I have struggled alot tried 15 different firmwares from all regions but no luck all of them fails at sboot.bin device 5 binary 4 at last I flashed lollipop based zips and they also stuck at bootlogo. There is a combination firmware 5.1.1 with engineered bootloader which allow you to downgrade but fingerprint sensor don't work .
Click to expand...
Click to collapse
So do you know where I can find SM-G920F engineering bootloader?
I have searched hundreds of pages and it's nowhere to be found :'(
Thanks!
qasim799 said:
I also want to go back to 5.1.1 as I don't like MM and N is also not too stable. so I have struggled alot tried 15 different firmwares from all regions but no luck all of them fails at sboot.bin device 5 binary 4 at last I flashed lollipop based zips and they also stuck at bootlogo. There is a combination firmware 5.1.1 with engineered bootloader which allow you to downgrade but fingerprint sensor don't work .
Click to expand...
Click to collapse
How do you mean not too stable? It works perfectly! I installed CYV version, not a single glitch since install. Everything works like a charm and battery is muvh better than on MM. Plus it has some pretty awesome options.
OK i managed to find a combination firmware:
COMBINATION_OXA_FA50_G920FXXU4APF1_OXA4APF1_CL6658768_QB10183466_REV02
However there is a pit file inside. Does this mean I have to repartition the device?
Seems tricky since I want to be able to flash a stock firmware afterwards.
Can I extract and flash only sboot.bin from combination firmware?
From my understanding, once I have the engineering bootloader, it will let me flash an older one...
couitchy said:
OK i managed to find a combination firmware:
COMBINATION_OXA_FA50_G920FXXU4APF1_OXA4APF1_CL6658768_QB10183466_REV02
However there is a pit file inside. Does this mean I have to repartition the device?
Seems tricky since I want to be able to flash a stock firmware afterwards.
Can I extract and flash only sboot.bin from combination firmware?
From my understanding, once I have the engineering bootloader, it will let me flash an older one...
Click to expand...
Click to collapse
there is no problem with it. You can go back to any MM or N firmware.
---------- Post added at 01:06 PM ---------- Previous post was at 01:04 PM ----------
ilDuceo said:
How do you mean not too stable? It works perfectly! I installed CYV version, not a single glitch since install. Everything works like a charm and battery is muvh better than on MM. Plus it has some pretty awesome options.
Click to expand...
Click to collapse
Maybe I"m fed up from N grace ux as before N was released i was using note 7 grace ux port. Lollipop is so responsive if you used it then you can feel that is pretty obvious.
It worked!
I flashed COMBINATION_OXA_FA50_G920FXXU4APF1_OXA4APF1_CL6658 768_QB10183466_REV02 to get the engineering bootloader rev4.
Then I tried to flash G920FXXU3COI9_G920FOXA3COJ1_G920FXXU3COI9_HOME but it failed at sboot.bin device 4 binary 3 which prooves that even engineering bootloader prevents downgrade.
Then I tried to flash G920FXXU3COI9_G920FOXA3COJ1_G920FXXU3COI9_HOME without sboot.bin, cm.bin and modem.bin => it worked (not stuck at Samsung logo anymore).
My fingerprint scanner is not working but baseband is here (IMEI ok).
So I have kind of a "hybrid Lollipop" G920FXXU3COI9_G920FXXU4BPF1 but that's ok for what I wanted to do
EDIT: CF-Auto-Root-zeroflte-zerofltexx-smg920f doesn't seem to work when using engineering bootloader => I guess I'll have to find a new way to root the phone :-S
so any good way to do it ? because nougat is bad
Finally I got it rooted using TWRP and flashing SuperSU
So, to sum up, here is what I did to downgrade from stock G920FXXU4DPIL (6.0.1) to stock G920FXXU3COI9 (5.1.1):
(my guess is it will also work with Nougat)
1. Find combination firmware with engineering bootloader matching your current bootloader revision (mine was 4) - unfortunately this step may not be free
2. Find stock firmware you want to downgrade to (even if it is packed with an older sboot.bin bootloader)
3. Extract stock firmware, remove sboot.bin, cm.bin and modem.bin
4. Repack stock firmware to tar (with android unified toolkit for example) without the 3 .bin files
5. Flash combination firmware with Odin
6. Let it boot once and then go back to Odin
7. Flash repacked stock firmware with Odin
Additional steps to get root:
8. Download SuperSU (flashable zip)
9. Download TWRP
10. Flash TWRP with Odin
11. Enter recovery (TWRP) and flash SuperSU
Voilà !
Does it work with G925F (edge) too? Because I really want to downgrade to 5.1.1 as well because it was the best version for the Galaxy S6 and S6 edge in my opinion.. Battery life was VERY good, design was pretty amazing... and Samsung is blocking the downgrade (which is very STUPID!)
Okay I downgraded my S6 edge sucessfully to 5.1.1!
I missed that old UI soo mucchh thanks for your guidance
halloo7 said:
Does it work with G925F (edge) too? Because I really want to downgrade to 5.1.1 as well because it was the best version for the Galaxy S6 and S6 edge in my opinion.. Battery life was VERY good, design was pretty amazing... and Samsung is blocking the downgrade (which is very STUPID!)
Click to expand...
Click to collapse
Actually there is a reason Samsung doesn't want you to downgrade bootloader: I noticed that every bootloader update usually comes with modem/baseband update, which implies some modifications in the /efs partition as well. An older bootloader would then be unable to read new /efs partition, resulting in a null IMEI. That is why the correct way to downgrade is to flash the old system files but keeping current modem/baseband.
The real stupid thing here is that the stock MM bootloader prevents stock LP image to boot. Fortunately the engineering bootloader can bypass this
halloo7 said:
Okay I downgraded my S6 edge sucessfully to 5.1.1!
I missed that old UI soo mucchh thanks for your guidance
Click to expand...
Click to collapse
Cool !
:good:
Sometimes I get a Kernel Problem. The phone crashes randomly after the downgrade. How to fix this?
the only thing i want now is a way to make fingerprint sensor work. If anybody know something about it please reply.
qasim799 said:
the only thing i want now is a way to make fingerprint sensor work. If anybody know something about it please reply.
Click to expand...
Click to collapse
I think fingerprint sensor is somehow related to something inside cm.bin (cryptography management). As long as we don't get cm.bin matching both bootloader version and system image version at the same time, I don't see a way to make it work :crying:
couitchy said:
I think fingerprint sensor is somehow related to something inside cm.bin (cryptography management). As long as we don't get cm.bin matching both bootloader version and system image version at the same time, I don't see a way to make it work :crying:
Click to expand...
Click to collapse
i flashed latest cm.bin from nougat it boots up but fingerprint sensor is still not working and with engineering bootloader, the rom crashes at certain apps and get really snapier when unlocking phone with pin or pattern. So i am back to nougat i gave up downgrading almost downloaded whole sammobile 5.1.1 firmwares non of them is having a B:5 K:2 S:2 bootloader I was expecting such rom because on Verizon S6 , there is a 5.1.1 firmware that successfully allows to get down with same latest sboot.bin and i still believe there is a firmware like that for our model too but it is really hard to find it.
couitchy said:
Finally I got it rooted using TWRP and flashing SuperSU
So, to sum up, here is what I did to downgrade from stock G920FXXU4DPIL (6.0.1) to stock G920FXXU3COI9 (5.1.1):
(my guess is it will also work with Nougat)
1. Find combination firmware with engineering bootloader matching your current bootloader revision (mine was 4) - unfortunately this step may not be free
2. Find stock firmware you want to downgrade to (even if it is packed with an older sboot.bin bootloader)
3. Extract stock firmware, remove sboot.bin, cm.bin and modem.bin
4. Repack stock firmware to tar (with android unified toolkit for example) without the 3 .bin files
5. Flash combination firmware with Odin
6. Let it boot once and then go back to Odin
7. Flash repacked stock firmware with Odin
Additional steps to get root:
8. Download SuperSU (flashable zip)
9. Download TWRP
10. Flash TWRP with Odin
11. Enter recovery (TWRP) and flash SuperSU
Voilà !
Click to expand...
Click to collapse
I've tried flashing the firmware without the binfiles but It just gets stuck on file analysis.
Hi,
I want to downgrade my SM-A310F to earlier Android versions, but Odin blocks this with the Error: "SW REV. CHECK FAIL. DEVICE: 3. BINARY: 2."
So apparently I can only install firmware files which come with the same Bootloader I'm currently on (so 3) and not earlier versions. For me it's Android 7 and the latest update of 6.0.1 which where made for this bootloader. But I want to downgrade to earlier versions of Android (please don't ask why, I know that these don't have the latest security patches etc. pp.).
So my first idea was I should downgrade the bootloader first so it matches the firmware I want to install. I extracted the recovery.img out of the firmware file, packed it in a .tar file and flashed it successfully through Odin. But unfortunately I get the same error in Odin like above when trying to flash the firmware again, so the bootloader maybe didn't downgrade?!
What can I do to downgrade my bootloader?
I want to install a stock Android ROM, so Custom ROMs are not an option. I heard I can install a Custom Bootloader, like TWRP, which allows installing every firmware?!
But does that trip my KNOX counter? My KNOX is still 0, so if there's an option to downgrade to earlier ROMs without tripping KNOX I'd be glad to hear it.
So I found the answer myself.
Apparently it is not possible to simply downgrade the Bootloader. I didn't fully dig into this, but to simply flash some image with Odin won't do the trick at least.
What works however is to downgrade to an older firmware with an older bootloader even if one keeps the newer bootloader on his device.
So what's the trick? One downloads the firmware file (.tar) which one wants to downgrade to and opens it with an archiver application (7zip). One extracts all the files to a folder and repacks them again in a .tar file but leaving every file out which ends on .bin (e.g. sboot.bin etc.). This .tar file can be flashed like any other firmware file via Odin and it should run through it without any problems.
I can not confirm that the downgrade works for every firmware version, but at least I could downgrade from Android 7 Nougat to 6.0.1 Marshmellow while the first one comes with the SW Rev 3 bootloader and the latter with SW Rev 2 bootloader. Again, I don't know how far into the past this works, e.g. if you can downgrade from 7 to 5.1.1 with this method.
Another option is always a Custom ROM (like this one for 5.1.1 for example) which doesn't check the Bootloader version.
I don't know if this method trips KNOX since I had tripped it already before figuring this out (very well could be, since you're not flashing a signed firmware file anymore...).
mcpossity said:
So I found the answer myself.
Apparently it is not possible to simply downgrade the Bootloader. I didn't fully dig into this, but to simply flash some image with Odin won't do the trick at least.
What works however is to downgrade to an older firmware with an older bootloader even if one keeps the newer bootloader on his device.
So what's the trick? One downloads the firmware file (.tar) which one wants to downgrade to and opens it with an archiver application (7zip). One extracts all the files to a folder and repacks them again in a .tar file but leaving every file out which ends on .bin (e.g. sboot.bin etc.). This .tar file can be flashed like any other firmware file via Odin and it should run through it without any problems.
I can not confirm that the downgrade works for every firmware version, but at least I could downgrade from Android 7 Nougat to 6.0.1 Marshmellow while the first one comes with the SW Rev 3 bootloader and the latter with SW Rev 2 bootloader. Again, I don't know how far into the past this works, e.g. if you can downgrade from 7 to 5.1.1 with this method.
Another option is always a Custom ROM (like this one for 5.1.1 for example) which doesn't check the Bootloader version.
I don't know if this method trips KNOX since I had tripped it already before figuring this out (very well could be, since you're not flashing a signed firmware file anymore...).
Click to expand...
Click to collapse
https://forum.xda-developers.com/samsung-a-series/general/rom-t3614602
So I found the answer myself.
Apparently it is not possible to simply downgrade the Bootloader. I didn't fully dig into this, but to simply flash some image with Odin won't do the trick at least.
What works however is to downgrade to an older firmware with an older bootloader even if one keeps the newer bootloader on his device.
So what's the trick?
mcpossity said:
One downloads the firmware file (.tar) which one wants to downgrade to and opens it with an archiver application (7zip). One extracts all the files to a folder and repacks them again in a .tar file but leaving every file out which ends on .bin (e.g. sboot.bin etc.). This .tar file can be flashed like any other firmware file via Odin and it should run through it without any problems.
Click to expand...
Click to collapse
Hi there mcpossity.
Can you please be more specific on this trick part? Please share the steps you followed.
Regards
With a S7 Edge
Hello,
My phone has updated on the last version of Android 8.0.0 Oreo (01.12.2020), with the last version of Bootloader (7th). I want to downgrade my device to Android 6.0.1, but all version for this OS have BLv1, so I am in the same situation than you (but one gen. later). Can I downgrade my phone, with the same methode ? If so, can you explain this in detail or give me a custom OS ? Thanks in advance.
I tried with this methode and this doesn't work : Odin has shut down when I have started the process. What was wrong ?
Downgrade using old versions of LineageOS?
Hi, I've got the same problem: I installed LineageOS 17.1 (Andoroid 10) which upgraded my Bootloader to 5. Now I need to go back to stock ROM but cannot do so because the error says: "SW REV. CHECK FAIL (BOOTLOADER) DEVICE: 5, BINARY 1.
Is it possible to install an early Lineage OS that downgrades the Bootloader and then install stock ROM? Where would I find the BL version of LineageOS?
Thanks
PS: In my case Galaxy S8
galaxynoobie said:
Hi, I've got the same problem: I installed LineageOS 17.1 (Andoroid 10) which upgraded my Bootloader to 5. Now I need to go back to stock ROM but cannot do so because the error says: "SW REV. CHECK FAIL (BOOTLOADER) DEVICE: 5, BINARY 1.
Is it possible to install an early Lineage OS that downgrades the Bootloader and then install stock ROM? Where would I find the BL version of LineageOS?
Thanks
PS: In my case Galaxy S8
Click to expand...
Click to collapse
story is not completely same but my device is note 9 exynos and i did march patch BL is 5 and android 10 & 9 is sucks so need 8.1 but can't go back need serious help
Hey I'm Sam said:
story is not completely same but my device is note 9 exynos and i did march patch BL is 5 and android 10 & 9 is sucks so need 8.1 but can't go back need serious help
Click to expand...
Click to collapse
have you ever rosolved this ?
i have s9 note, want disperatly to downgrade to oreo for call recording. I feel cheated from samsung, what a waste of money....
Nemonavicusrino said:
have you ever rosolved this ?
i have s9 note, want disperatly to downgrade to oreo for call recording. I feel cheated from samsung, what a waste of money....
Click to expand...
Click to collapse
in the same boat as you, cube acr does record but the recording quality is very poor and the recording does not work when you are using Bluetooth headphones
Need help with recording
bilaliz said:
in the same boat as you, cube acr does record but the recording quality is very poor and the recording does not work when you are using Bluetooth headphones
Click to expand...
Click to collapse
Find something here, but i am not sure what i need, seem promising. I feel so cheated by this companies that put this restrictions on OUR HARDWARE. I do not understand, why something i pay today, dont work as espected tomorow, for SECURITY REASON. I want to asume risk and i do not know who is the owner. Me or samsung or google ?
https://forum.xda-developers.com/galaxy-note-9/help/enabling-native-call-recorder-csc-t3962224/page2
Espect day when phones is replaced by personal computer model. I want this OS on this hardware, with this app for calling and ...voila. I am at rage now : a 1000+ euro hardware canot record WHAT I SPEAK AND WHAT IS SPEAKED TO ME? if i put call on speaker and 10 person hear what is the diference...
Please help !
GuestD1009 said:
So I found the answer myself.
Apparently it is not possible to simply downgrade the Bootloader. I didn't fully dig into this, but to simply flash some image with Odin won't do the trick at least.
What works however is to downgrade to an older firmware with an older bootloader even if one keeps the newer bootloader on his device.
So what's the trick? One downloads the firmware file (.tar) which one wants to downgrade to and opens it with an archiver application (7zip). One extracts all the files to a folder and repacks them again in a .tar file but leaving every file out which ends on .bin (e.g. sboot.bin etc.). This .tar file can be flashed like any other firmware file via Odin and it should run through it without any problems.
I can not confirm that the downgrade works for every firmware version, but at least I could downgrade from Android 7 Nougat to 6.0.1 Marshmellow while the first one comes with the SW Rev 3 bootloader and the latter with SW Rev 2 bootloader. Again, I don't know how far into the past this works, e.g. if you can downgrade from 7 to 5.1.1 with this method.
Another option is always a Custom ROM (like this one for 5.1.1 for example) which doesn't check the Bootloader version.
I don't know if this method trips KNOX since I had tripped it already before figuring this out (very well could be, since you're not flashing a signed firmware file anymore...).
Click to expand...
Click to collapse
you sure this method works? i want to downgrade from 9 to 8. I am desperate now. But i don't know if it'll work. I've read thousands of words and all say it won't work.
S10 downgrade bootloader
I'm also in the same boat, Galaxy S10 (Exynos). Android 10 doesn't support PPTP VPN hotspot, and now my bootloader has been upgraded to U4. So yeah..
this seems helpful. are there anyone tried this on a s10 exynos?
ya not alone with an Samsung.....i'm on Sony Xperia 1 and after the update to Android 10 i have couple issuse with Soft restart out of nowhere everyday ones or more
dowangrade to Pie wasn't the problem but with Pie i went into an Gyroscope error....display isn't turning anymore i tried everything to get the sensor working but nothing helped
after updating to Android 10 Sensor running well
PlayJ004 said:
With a S7 Edge
Hello,
My phone has updated on the last version of Android 8.0.0 Oreo (01.12.2020), with the last version of Bootloader (7th). I want to downgrade my device to Android 6.0.1, but all version for this OS have BLv1, so I am in the same situation than you (but one gen. later). Can I downgrade my phone, with the same methode ? If so, can you explain this in detail or give me a custom OS ? Thanks in advance.
I tried with this methode and this doesn't work : Odin has shut down when I have started the process. What was wrong ?
Click to expand...
Click to collapse
same here
Me now with sm-p615 (tablet)
GuestD1009 said:
So I found the answer myself.
Apparently it is not possible to simply downgrade the Bootloader. I didn't fully dig into this, but to simply flash some image with Odin won't do the trick at least.
What works however is to downgrade to an older firmware with an older bootloader even if one keeps the newer bootloader on his device.
So what's the trick? One downloads the firmware file (.tar) which one wants to downgrade to and opens it with an archiver application (7zip). One extracts all the files to a folder and repacks them again in a .tar file but leaving every file out which ends on .bin (e.g. sboot.bin etc.). This .tar file can be flashed like any other firmware file via Odin and it should run through it without any problems.
I can not confirm that the downgrade works for every firmware version, but at least I could downgrade from Android 7 Nougat to 6.0.1 Marshmellow while the first one comes with the SW Rev 3 bootloader and the latter with SW Rev 2 bootloader. Again, I don't know how far into the past this works, e.g. if you can downgrade from 7 to 5.1.1 with this method.
Another option is always a Custom ROM (like this one for 5.1.1 for example) which doesn't check the Bootloader version.
I don't know if this method trips KNOX since I had tripped it already before figuring this out (very well could be, since you're not flashing a signed firmware file anymore...).
Click to expand...
Click to collapse
How on earth did you do that??
Which archive are you talking about when you say you unpack all the files and repack them without every .bin file?
I'm guessing the BL archive because that's the only one with a lot .bin files in it.
So I tried the BL_xxxx.tar.md archive and repacked it. But Odin would always get stuck at "file analysis..."
Also did you flash the modified BL first and then the AP, CP and CSC or did you flash it all at once?
I've got the same problem here. I want to downgrade my Galaxy S7 from Android 8.0 to Androud 7.0 but am unable to do so, to the point where I'm considering buying a completely new device just to have Android 7.0 again.
There is a way but...only Samsung's engineer are able to hack / trick this.
It is require special file to flashing in device then Sofware protection will be removed
Ask an Samsung Mobile Engineer if you have relatives.
Hi,
I rooted my S8 (SM-G950U1, carrier unlocked) recently using SamPWND method.
By doing so my phone's baseband version was changed from the original G950U1UEU1AQH3 to G950USQU1AQDE from SamPWND.
Is there a way to flash the original baseband somehow? I have the original firmware files I downloaded from SamMobile.com
The other baseband version seems to be compatible with my phone since I can make calls and receive messages.
Should I even bother restoring the original baseband firmware?
I flashed the original CSC G950U1UEU1AQH3_G950U1OYM1AQH3_XAA using Comsey Odin (the original Odin was throwing "FAIL! Model dismatch fail" error).
That didn't update the baseband back to stock version though.
I can probably use something like "Partitions backup" app from Google store to restore a partition, but I don't know which partition that is and where to get the original baseband partition image for G950U1UEU1AQH3.
Thank you!
BigBucha said:
Hi,
I rooted my S8 (SM-G950U1, carrier unlocked) recently using SamPWND method.
By doing so my phone's baseband version was changed from the original G950U1UEU1AQH3 to G950USQU1AQDE from SamPWND.
Is there a way to flash the original baseband somehow? I have the original firmware files I downloaded from SamMobile.com
The other baseband version seems to be compatible with my phone since I can make calls and receive messages.
Should I even bother restoring the original baseband firmware?
I flashed the original CSC G950U1UEU1AQH3_G950U1OYM1AQH3_XAA using Comsey Odin (the original Odin was throwing "FAIL! Model dismatch fail" error).
That didn't update the baseband back to stock version though.
I can probably use something like "Partitions backup" app from Google store to restore a partition, but I don't know which partition that is and where to get the original baseband partition image for G950U1UEU1AQH3.
Thank you!
Click to expand...
Click to collapse
I used the Sampwnd method. The first time I flashed with stock. I then did the samPWND. I didn't have any issues doing it in this order.
I saved the samPWND files and somehow went back in to get them and half somehow was deleted. If there is anyway to send me a link via drive or anything like that it would ve greatly appreciated.
Hello,
I used files from this youtube video to root my S8.
Please check the description for that video for the links.
eyelost said:
I used the Sampwnd method. The first time I flashed with stock. I then did the samPWND. I didn't have any issues doing it in this order.
I saved the samPWND files and somehow went back in to get them and half somehow was deleted. If there is anyway to send me a link via drive or anything like that it would ve greatly appreciated.
Click to expand...
Click to collapse
BigBucha said:
Hello,
I used files from this youtube video to root my S8.
Please check the description for that video for the links.
Click to expand...
Click to collapse
This will not work on modern bootloaders. Sampwnd is for version one only. See the PartCyborgRom thread for a modern (and mucb simpler) method, no stock necessary
Just flash CP in Odin, that's what I used to do in the BLV1 version so I'm sure it works the same
adj998 said:
Just flash CP in Odin, that's what I used to do in the BLV1 version so I'm sure it works the same
Click to expand...
Click to collapse
Thank you, guys!
I think I am good for now, the phone is rooted, working perfectly and I am not planning to update it any time soon, unless somebody finds a way to remove the charging to 80% restriction in this engineering kernel