Database Develop

[RECOVERY] Boot Menu Manager[APP]

ALL OF THIS WORK IS DONE BY whirleyes! PLEASE CREDIT HIM AND NOT I. LINK OF HIS THREAD IS BELOW!
http://forum.xda-developers.com/showthread.php?t=2005187
Same exact thing , compatible with the Droid 4 and tested out on my Droid 4 and works fine. All I did was uninstall safestrap and simply install this app from playstore
Playstore link: https://play.google.com/store/apps/details?id=com.projectlense.bootmenu.manager&hl=en
As usual I'm not responsible nor the developer of the app is responsible for any damaged to your device.
What is Boot Menu Manager?
Well boot menu manager is practically a custom recovery (not going over the system recovery) that launches a screen at each boot asking for rom you want to boot. There are 6 slots and you can edit the system slot, although please remember when entering the recovery, do switch to rom slot 1 if you don't want to mess with system, if you don't you'll edit your stock system.
As this recovery is discontinued, it does support 4.3 and other Roms. I haven't go to mess around with all the apps but it works just fine. Sometimes by entering the recovery there is a slight delay. The Recovery seems to optimize kexec better and handle Roms a bit better, but that's just in my experience.
ALL OF THIS WORK IS DONE BY whirleyes! PLEASE CREDIT HIM AND NOT I. LINK OF HIS THREAD IS AT TOP OF THREAD!

Sorry to dig up old threads, but Safestrap will not work for me. My phone gets stuck at a certain point in the install (60/100) and then just hangs.
I was told that this might be an alternative method to get a Custom ROM on my Droid 4.
Is there a version out there of BMM that I can use?

@joefuf Yep, but
Do you have root?
Fervi

ferviverus said:
@joefuf Yep, but
Do you have root?
Fervi
Click to expand...
Click to collapse
Yeah, I do. I found BMM 0.3.4 and installed that. I managed to get a good updater-script to allow my ROM to be flashed onto my Motorola Droid 4 in System 1.
Is there another version I should be using? It was tough to find v0.3.4.
Unfortunately, I am still experiencing a lot of lagging and slow response from my ROM. Is this common with BMM? Is there anything I can do to optimize the ROM? Should I install my ROM somewhere other than System 1?

@joefuf
Eee, System 1 is on top-right?
If it is top-left, you probably delete stock rom (if u install CM or other ROM)
Fervi

ferviverus said:
Eee, System 1 is on top-right?
If it is top-left, you probably delete stock rom (if u install CM or other ROM)
Fervi
Click to expand...
Click to collapse
System 1 is top-left. I know that I deleted the Stock ROM. It's running fine and reboots into System 1 fine. The ROM just runs very slow. Do you know how to fix it?
Is there a better version of BMM than 0.3.4?

@joefuf
Well, BMM is unsupported (dead)
Technically special version of safestrap or BMM is to install system on "hidden Droid partitions", and u have 2 systems
Probably it's bugged rom, because CM works really fast
Fervi

Downgrade back to 5.0.1 from 6.0/7.0 for full root.

Not sure if anyone care or still want to go back to 5.0.1.
It is possible if you download COMBINATION_VZW_FA50_G925VVRU4AOJ1 (Google it yourself its free out there.)
After flashing combination file you can root it with kingroot then replace it with superuser ( https://forum.xda-developers.com/a310/general/how-to-remove-replace-kingroot-kinguser-t3308989 ), then you can use flashfire to flash 5.0.1 rom.
You will need to keep the sboot/bootloader from combination file i order to boot with 5.0.1 kernel.
Anyone know if theres good rom that will still work with this method? I tied some stock root rom ( https://forum.xda-developers.com/ve...ment/rom-stock-rooted-g925v-vru1aoc3-t3115121 ), it seems to be missing some file after flashing. It boots up gets signal, but it is buggy. If anyone know if bugs from flashing this way cannot be fixed then let me know so I can stop trying .

I flashed the COMBINATION_VZW_FA50_G925VVRU4AOJ1 tar file but how do it install apks so i can use kingroot. unless you have forum to share with me

I haven't used the XDA forums in over a year. I don't know if I have the courage to downgrade from 7.0 to 5.X

Snowby123 said:
I haven't used the XDA forums in over a year. I don't know if I have the courage to downgrade from 7.0 to 5.X
Click to expand...
Click to collapse
Something similar for me honestly. I just downloaded the firmware stated, did the steps and it seems to have worked fine. Even with root, I honestly liked 7.0 on this device. Dang locked BL. :/

3Cubed27 said:
I flashed the COMBINATION_VZW_FA50_G925VVRU4AOJ1 tar file but how do it install apks so i can use kingroot. unless you have forum to share with me
Click to expand...
Click to collapse
You can install apks using ADB -- I think you can get it from Android Studio or try https://www.xda-developers.com/install-adb-windows-macos-linux/
Once you have ADB installed, just connect your S6 to your PC, open terminal, and run "adb devices" to confirm your phone is visable
Then to install an apk, have it downloaded on your PC and run
"adb install {path/to/apk}"
Example:
adb install Downloads/NewKingrootV5.3.7_C197_B451_xda_release_2018_06_19_20180620193529_242043.apk

I don't really think there was a 5.0.1 ROM designed for the Revision 4 bootloader outside of the Combination Firmware. I think this may be a reason.

Delgoth said:
I don't really think there was a 5.0.1 ROM designed for the Revision 4 bootloader outside of the Combination Firmware. I think this may be a reason.
Click to expand...
Click to collapse
I know this is old. But I come from a s8. So we should be able to even though rev4 bootloader flash any 5 System IMG. The bootloader from the fa50 combination should suffice to boot any lolipop system since they are not incremented

TheMadScientist said:
I know this is old. But I come from a s8. So we should be able to even though rev4 bootloader flash any 5 System IMG. The bootloader from the fa50 combination should suffice to boot any lolipop system since they are not incremented
Click to expand...
Click to collapse
Correct, you just need the bootloader and kernel capable of booting the system up. This is how I was able to use any of the LP AP Build/System on my rev 3 Note5.
All the LP builds were rev 2. But I had a LP bootloader and kernel. Realistically someone should try, but you might need to root the combo firmware first and use flash fire/flashify/safestrap to flash the system image. Because ODIN might not let you.

Delgoth said:
Correct, you just need the bootloader and kernel capable of booting the system up. This is how I was able to use any of the LP AP Build/System on my rev 3 Note5.
All the LP builds were rev 2. But I had a LP bootloader and kernel. Realistically someone should try, but you might need to root the combo firmware first and use flash fire/flashify/safestrap to flash the system image. Because ODIN might not let you.
Click to expand...
Click to collapse
Yea Odin pushing the rooted firmware with combo boot was patched on s8 about the same time. But now where using edl to push a rooted combination file with su flash fire and safestrap.
My s8 is running a bit 5 nougat combo which that bootloader is reserved for Oreo and pie. But I'm running a rooted system IMG I made up from a equivalent rev2 nougat system and runs fine other than 80% charge limmit on the newer combos. Even my j3 limmits to 80 on combo. But I found a hack to charge to 100% I got posted in the s8 threads. I'm gonna try this over the next few days. If there's a eng bootloader with permissive kernel nougat should be able to be rooted too.

TheMadScientist said:
Yea Odin pushing the rooted firmware with combo boot was patched on s8 about the same time. But now where using edl to push a rooted combination file with su flash fire and safestrap.
My s8 is running a bit 5 nougat combo which that bootloader is reserved for Oreo and pie. But I'm running a rooted system IMG I made up from a equivalent rev2 nougat system and runs fine other than 80% charge limmit on the newer combos. Even my j3 limmits to 80 on combo. But I found a hack to charge to 100% I got posted in the s8 threads. I'm gonna try this over the next few days. If there's a eng bootloader with permissive kernel nougat should be able to be rooted too.
Click to expand...
Click to collapse
The question is, what did you do to.modify your stock rom to be able to boot on the combo bootloader? I'm still a little lost on that.

Delgoth said:
The question is, what did you do to.modify your stock rom to be able to boot on the combo bootloader? I'm still a little lost on that.
Click to expand...
Click to collapse
I didn't on the j3.

TheMadScientist said:
I didn't on the j3.
Click to expand...
Click to collapse
Maybe not on the j3 haha.

Delgoth said:
Maybe not on the j3 haha.
Click to expand...
Click to collapse
Wrong device ****. I got so many phones lying around. I haven't really messed with the s6 much. I got a few other on the front burner

TheMadScientist said:
Yea Odin pushing the rooted firmware with combo boot was patched on s8 about the same time. But now where using edl to push a rooted combination file with su flash fire and safestrap.
My s8 is running a bit 5 nougat combo which that bootloader is reserved for Oreo and pie. But I'm running a rooted system IMG I made up from a equivalent rev2 nougat system and runs fine other than 80% charge limmit on the newer combos. Even my j3 limmits to 80 on combo. But I found a hack to charge to 100% I got posted in the s8 threads. I'm gonna try this over the next few days. If there's a eng bootloader with permissive kernel nougat should be able to be rooted too.
Click to expand...
Click to collapse
This is what I was asking about though. I still can't get anyone to explain how to make the stock ROMs work on the newer more locked devices. It's like a big secret or something. But it is possible on the S6, Note5, and S8. Probably the S7 too.
But 5.0.1, 5.1.1, and 7.0 are built a lot differently and I imagine the method is different.
TheMadScientist said:
Wrong device ****. I got so many phones lying around. I haven't really messed with the s6 much. I got a few other on the front burner
Click to expand...
Click to collapse
Before the S9 Line most everything has been built pretty similarly.

Magisk and Bootloader

Hi,
I am very new to this android world so my queries might feel stupid. Actually i m here after 3 years and that is very long period in this world. I know about rooting(super Su), bootloader and recovery (stock,CM and TWRP) . Recently read about Magisk and got some queries. Hope you will help me out. These are not device specific but need to learn.
What i read/study i found these readings...
1. Magisk roots device systemlessly (does not touch system partition) so one can get OTA updates easily.
2.To install and run Magisk one needs to unlock the bootloader .
3.(Device Specific) My redmi MI Flash tool says,If you unlock the bootloader , you wont get OTA updates.
4.I have previously rooted my galaxy Y and uninstalled system apps. If i delete sys apps from magisk,still can we say that we are not touching system.
So all statements are true? or some? or none ?
Here my device is redmi 3s (6.0.1- MIUI 9.6.1.0 Global Stable).All these queries are just in relation to OTA system updates. Nothing related to warranty.
Thanking You

Yes.
Yes.
Don't know about Xiaomi, but I've never had issues with OTA on a device with an unlocked bootloader (I've mainly used different Google and Oneplus devices). Someone with a Xiaomi is gonna have to chime in on this one.
As long as you use Magisk's debloating feature of replacing files or directories with empty ones, you're good. The actual /system partition won't be touched. Use a module like the Debloater module by @veez21, or make a debloater module yourself.

Didgeridoohan said:
Don't know about Xiaomi, but I've never had issues with OTA on a device with an unlocked bootloader (I've mainly used different Google and Oneplus devices). Someone with a Xiaomi is gonna have to chime in on this one.
Click to expand...
Click to collapse
Ahh, Thank You.
You get OTA system updates for your STOCK ROM ?

inwell said:
Ahh, Thank You.
You get OTA system updates for your STOCK ROM ?
Click to expand...
Click to collapse
Yes. But, having both Magisk and a custom recovery (an OTA won't install with a modified boot image and a custom recovery installed) I always find it easier to download the update and flash it manually. But, like I said, I have no idea if this is true for Xiaomi.

1. Ok. i also heared that when you update your device,you lose root...not true ? Or you need to root again ?
2.In normal stock device,we get update notification and we downlaod then restart (as per convenience)device to update.
If i remove some system apps from my rooted device and unroot the device,manage to get stock recovery back ,will the OTA update system treat my device as Stock-untouched? And install updates just as stock device will do ?
3. Is boot.img and bootloader are same things? Coz i read that for re locking boot loader you need to flash boot.img from stock software. (But Some procedures just use fastboot and relock oem command-they wont use boot.img,dont know why )
I read that unrooting,restoring stock recovery and locking bootloader again is more difficult/complicated than the rooting procedure
Some one should come up with solution just like Windows Restore .If you want to go back to everything STOCK,just use that feature same as done to Restore Windows in its previous state.

Any update that also updates the boot image (which means pretty much all) will remove root. But, that's just a simple case of reflashing Magisk right after applying the update.
If you've touched /system in any way, removing system apps or even just mounting the /system partition read-write, an OTA will fail. To be able update with an OTA your /system and /vendor partitions need to be untouched and you need to have the stock boot image and stock recovery installed. If your device doesn't conform to this the OTA will fail.
Boot image and bootloader are not the same thing. That you can read up on all over the internet, so I won't go into details. If you have done any kind of modifications on your device, I suggest you leave your bootloader unlocked. It's to easy to mess things up otherwise.
Going back to full stock is usually just a matter of flashing a full factory image/firmware package/stock ROM. Quite easy... Of course, some manufacturers make it harder than others.

Didgeridoohan said:
Boot image and bootloader are not the same thing. That you can read up on all over the internet, so I won't go into details. If you have done any kind of modifications on your device, I suggest you leave your bootloader unlocked. It's to easy to mess things up otherwise.
Click to expand...
Click to collapse
Ok. As you say the two are different , but can you explain in simple words (terms) that how they both are related/linked/connected? Coz as i read some forums/posts i get to read
1. To relock/lock bootloader you need to flash boot.img which suggests these (terms) are linked/connected.
2. but same time some forums/post suggest no img file flashing but just a fastboot command(s) to relock bootloader. In this case it seems they are not linked/connected.
And if the above 2 statements are true and device specific then how the bootloader and boot image are linked and not linked in diff devices? what changes are made so that in some cases these are linked and in some not
Sorry for asking too much. But you were really very kind to help me out.Thank you once again

I'm not 100% accurate (and someone will hopefully come I'm and correct me if needed), but basically the bootloader checks that everything is alright and then starts up your device. After that the boot image (ramdisk and kernel) takes over. Ramdisk basically makes sure all the partitions are mounted, and the kernel is exactly what it sounds like. The core of the OS, making sure that everything is working as it should.
This is of course a huge over-simplification, so if you want more you'll have to search around (and there are tons of resources around the web).
The main reason I can think of right at the moment for wanting to flash a boot image before locking the bootloader is that it's generally a good idea to have your device fully stock and functional before doing so. After you've locked the bootloader there might not be any going back if things start acting up and you could end up with a nice paperweight.
Questions are good. That's how you learn. I do believe that you'd be much better of searching around the internet for your answers. They've been put out there many, many times.

Ok.Thank you very much.I will learn more ...

General [IMG] Boot + magisk patched boot images

Hi, I have decided to gather boot images and magisk patched images to one thread for now. I will try to edit this thread to be up-to-date. You can let me know what could you want next or if anything is wrong etc.
Stock boot.img files (direct links): ​
EU NE2213_11_A.12​
Stock boot.img - link
EU NE2213_11_A.10​
Stock boot.img - link
​Magisk patched boot.img are here a file that can be downloaded (I am using magisk canary usually, but in Magisk, you can change the channel from the canary to stable etc.) - names as the versions come. ​
Below this there are those magisk patched files which you just flash (or boot and then flash directly from the Magisk app) via fastboot ​

Reserved

Don't you need to patch vendor_boot.img as well like OnePlus 9 pro ?

HessNL said:
Don't you need to patch vendor_boot.img as well like OnePlus 9 pro ?
Click to expand...
Click to collapse
Apparently not. I have patched that stock boot via magisk, then via fastboot boot <patchedimage.img> booted (and also tested if it actually boots) and when it booted, via magisk app I did "Direct install (recommended)", rebooted and done.

Oh okay you had a temporary boot we that's good to know well it works that's the most important thing ain't it

Noob question I been on locked bootloader for years so haven't been in the root scene, but I have US model NE2215 I'm guessing I need to wait for the firmware to be available to get the boot img? Did I just got my phone too early? Already oem unlocked now just waiting for twrp and root info. I always wanted a OnePlus phone because the community is big, but doesn't seem like much people upgraded from 9 pro.

HessNL said:
Oh okay you had a temporary boot we that's good to know well it works that's the most important thing ain't it
Click to expand...
Click to collapse
Yes, because this is probably and currently the most secure option to root it as we haven't got twrp available yet.
BuBbLeFIZzY said:
Noob question I been on locked bootloader for years so haven't been in the root scene, but I have US model NE2215 I'm guessing I need to wait for the firmware to be available to get the boot img? Did I just got my phone too early? Already oem unlocked now just waiting for twrp and root info. I always wanted a OnePlus phone because the community is big, but doesn't seem like much people upgraded from 9 pro.
Click to expand...
Click to collapse
That's not that you have it early. The phone itself is early in spite of rooting and doing things like rooting, custom recoveries, ROMs etc. I currently can't find boot img for your model, but once I do, I will post it here for you with patched one.

Thank you kouzelnik3 for this thread !
I was going to dl original firmware and patch it myself but found your thread in time with all ready to flash
Rooted OP10 pro done, now i can't wait to see some TWRP and roms in the future

fozzy056 said:
Thank you kouzelnik3 for this thread !
I was going to dl original firmware and patch it myself but found your thread in time with all ready to flash
Rooted OP10 pro done, now i can't wait to see some TWRP and roms in the future
Click to expand...
Click to collapse
You're really welcome, I wanted to unite those currently quite hard rooting stuff!
And yes, I can't wait to see twrp too!

Is there a known stock boot.img of the NE2215_11_A.10? I assume I shouldn't use the 2213_11_A.10.

GeekMcLeod said:
Is there a known stock boot.img of the NE2215_11_A.10? I assume I shouldn't use the 2213_11_A.10.
Click to expand...
Click to collapse
Not yet unfortunately. Or I don't know about it yet. :/

kouzelnik3 said:
Not yet unfortunately. Or I don't know about it yet. :/
Click to expand...
Click to collapse
Yeah.. I googled a lot last night once I got my phone trying to find it to root it. I need me that extra bit of customization.
Is there a way I can get it from my phone?

what am i doing wrong here rooted for 7+ years and some reason can't get this working.
Just moved over from ColorOS to Oxygen - when i try to flash the boot.img (patched one) all i get is this

Johnstan725 said:
what am i doing wrong here rooted for 7+ years and some reason can't get this working.
Just moved over from ColorOS to Oxygen - when i try to flash the boot.img (patched one) all i get is this
Click to expand...
Click to collapse
Ignore me but for anyone else that tries looks like i had to reboot bootloader and flash the img via bootloader...
thought it's normally flashed via fastboot?! weird phone

Johnstan725 said:
Ignore me but for anyone else that tries looks like i had to reboot bootloader and flash the img via bootloader...
thought it's normally flashed via fastboot?! weird phone
Click to expand...
Click to collapse
You should wipe the phone and start all over or else you won't be able to take ota updates. Never flash the patched boot image since you bypass the magisk backup feature. You have to wait for the full update package to update if you flash the boot. Ppl have previously had update issues after flashing.

g96818 said:
You should wipe the phone and start all over or else you won't be able to take ota updates. Never flash the patched boot image since you bypass the magisk backup feature. You have to wait for the full update package to update if you flash the boot. Ppl have previously had update issues after flashing.
Click to expand...
Click to collapse
Wiped the phone already, what difference would it make if i remove root or flash stock boot then flash ota and reflash boot?

Johnstan725 said:
Wiped the phone already, what difference would it make if i remove root or flash stock boot then flash ota and reflash boot?
Click to expand...
Click to collapse
Not sure what else magisk does during the backup process, but doing what you’re describing didn’t work for users on 8T and they usually ended up soft bricking. Everyone who flashed it vice installing from magisk app had to wait for op to post the full rom or for someone to post a repacked fastboot rom to update.
You do what you need to do, I’m just giving you some experience and recommendations since you just wiped and flashed the boot.

g96818 said:
Not sure what else magisk does during the backup process, but doing what you’re describing didn’t work for users on 8T and they usually ended up soft bricking. Everyone who flashed it vice installing from magisk app had to wait for op to post the full rom or for someone to post a repacked fastboot rom to update.
You do what you need to do, I’m just giving you some experience and recommendations since you just wiped and flashed the boot.
Click to expand...
Click to collapse
Interesting.
I moved over from ColorOS to oxygen OS, wiped the device then just booted a patched boot img, and installed direct.
I assume I flash ota and go onto magisk and do inactive slot? Where does the issue lie what method should I have gone down?

Johnstan725 said:
Interesting.
I moved over from ColorOS to oxygen OS, wiped the device then just booted a patched boot img, and installed direct.
I assume I flash ota and go onto magisk and do inactive slot? Where does the issue lie what method should I have gone down?
Click to expand...
Click to collapse
Hmmm. Well you should be fine if you patched the boot and let magisk do the install. I only suggested wiping since you said you flashed the img from the bootloader.
You might run into the same problem I have with the 9RT. I too upgraded from color to oos and couldn’t update at all, even though I rooted from the magisk app. I had to wait for someone to make a fastboot rom. I had no problems updating color following my method, but not oos after switching. Hopefully that’s not the case for you.

Good source for firmwares?

I'm looking for a good source of firmwares, i know the famous sites but some firmwares doesn't seem to be listed. I know in the time os Samsung KIES there were tools which communicated directly with samsung.
For example these firmware builds for the SM-G975Ux aren't listed on most firmware sites but have the December secutiry update with binary/bootloader version 8: G975USQS8IVL1 and G975USQS8IVL2

All the big sites have ROMs for that phone (same one I have). There is no "Ux" model... it's *U or *U1, with the latter being unlocked. IF you search for U1 ROMs you have many selections, but most get the XAA version which will usually change carriers automatically based on the SIM card.
The latest BL=8 version I see there is https://www.sammobile.com/samsung/g...M-G975U1/XAA/download/G975U1UEU8IWB6/1741280/ which is the February 2023 security update. I believe this is the last one we are getting (but I could be mistaken as there may be 1 more security patch, I don't remember).

There's U U1 0 W F N .... I'm looking for the oldest firmware with binary version 8, but it seems the sites don't show all firmwares available.... i'm looking for the oldest firmware with U8 bootloader (or any compatible bootloader with binary 8 version), i could have a look at all sites and try my luck... but they don't seem to have all data. but like i said i prefer some original source xml files... i saw some url's to original samsung servers but can't find them anymore.
There is already a firmware available with the march update.... but you have to be lucky to find them... i'm looking for original sources. like update.zip's and such
Found the first one....
https://fota-cloud-dn.ospserver.net/firmware/TMB/SM-G975U/version.xml

I'd recommend around sammobile and samfw. These are the two sources I use the most

hey!
after I wanted to update my g973f from "G973FXXUGHVK1" to "G973FXXSGHWC2" (I tried odin 3.13 and odin 3.14) and an error occurred, I can't install anything anymore... recovery and download mode work, and I can also flash the original firmware, but the device no longer boots into the system! even custom roms don't want to boot anymore
Can anybody help me further?

Ben1987 said:
hey!
after I wanted to update my g973f from "G973FXXUGHVK1" to "G973FXXSGHWC2" (I tried odin 3.13 and odin 3.14) and an error occurred, I can't install anything anymore... recovery and download mode work, and I can also flash the original firmware, but the device no longer boots into the system! even custom roms don't want to boot anymore
Can anybody help me further?
Click to expand...
Click to collapse
Do you mind explaining a bit more? Do you mean like that it boots you into recovery only or?

WooBLOATERRRR said:
Do you mind explaining a bit more? Do you mean like that it boots you into recovery only or?
Click to expand...
Click to collapse
if i flash a new rom (whether original or custom rom) nothing happens after the reboot... download mode works too, flashing twrp works too! however, the system boot does not work via twrp either... not even a bootloop, the cell phone does not react at all! the task combination for

Right now I don't even care if I get the original firmware or a custom rom running... I hope I didn't brick it (((

My old device was a G930F, its unbreakable make sure you flash the right rom and wipe data and dalvik cache after flashing.... THis ons is locked so it doesn't have fastboot. My G-930F came with fastboot enabled so you can always fastboot a recovery.img. like TWRP
Did you try to download TWRP from twrp.me and "fastboot boot twrp-3.7.0_9-0-herolte.img" ? it should boot to twrp in fastboot mode (hold volume down + home + power).

Ben1987 said:
if i flash a new rom (whether original or custom rom) nothing happens after the reboot... download mode works too, flashing twrp works too! however, the system boot does not work via twrp either... not even a bootloop, the cell phone does not react at all! the task combination for
Click to expand...
Click to collapse
1. is your KG status is broken?
2. Is your bootloader unlocked?

You know how to flash lineageos through twrp right? and how to use odin?
Maybe flash lineageos to see if everything works.... and then revert to original software. Be sure to wipe cache/dalvik and userdata

DaanNL said:
There's U U1 0 W F N .... I'm looking for the oldest firmware with binary version 8, but it seems the sites don't show all firmwares available.... i'm looking for the oldest firmware with U8 bootloader (or any compatible bootloader with binary 8 version), i could have a look at all sites and try my luck... but they don't seem to have all data. but like i said i prefer some original source xml files... i saw some url's to original samsung servers but can't find them anymore.
There is already a firmware available with the march update.... but you have to be lucky to find them... i'm looking for original sources. like update.zip's and such
Found the first one....
https://fota-cloud-dn.ospserver.net/firmware/TMB/SM-G975U/version.xml
Click to expand...
Click to collapse
Yes, I know there are many other variant firmwares out there, but for a U phone (snapdragon) there is really only U and U1... the rest are incompatible.
There is no "older" firmware with binary 8, because the firmwares are packaged with the proper/compatible binary already. Basically, the "binary" is the bootloader version. On Snapdragon phones, you must have the proper BL/binary to flash, as you already know. You can't interchange the binary/BL with the ROM and security updates because they are not made that way.
The update.zip you're looking for are updates sent by Samsung directly, and they can update the ROM (and Binary) from one stock version to another... but, again, they will update both the binary/BL as well as the ROM, so they can't be broken up to only do one or the other.
It sounds like you're trying to get to an older ROM version (for whatever reason) with an older security patch level as well? Basically, this cannot be done on Snapdragon phones. Once you're on an updated binary/BL, you're stuck there (at least today you are).

WooBLOATERRRR said:
I solved the problem! I had unlocked the bootloader, but I also had to deactivate verity via CMD with twrp+adb "adb disable-verity"
ok i've solved the problem now, but does anyone know why i couldn't even start the original stock roms? Actually, the stock ROM should set everything to factory settings...
Click to expand...
Click to collapse

WooBLOATERRRR said:
1. is your KG status is broken?
2. Is your bootloader unlocked?
Click to expand...
Click to collapse
Thank you for helping so quickly with ideas... I would not have expected such quick help with such an old model, even samsung customer service didn't want to help me yesterday

Ben1987 said:
Thank you for helping so quickly with ideas... I would not have expected such quick help with such an old model, even samsung customer service didn't want to help me yesterday
Click to expand...
Click to collapse
Samsung/apple support in a nutshell

schwinn8 said:
Yes, I know there are many other variant firmwares out there, but for a U phone (snapdragon) there is really only U and U1... the rest are incompatible.
There is no "older" firmware with binary 8, because the firmwares are packaged with the proper/compatible binary already. Basically, the "binary" is the bootloader version. On Snapdragon phones, you must have the proper BL/binary to flash, as you already know. You can't interchange the binary/BL with the ROM and security updates because they are not made that way.
The update.zip you're looking for are updates sent by Samsung directly, and they can update the ROM (and Binary) from one stock version to another... but, again, they will update both the binary/BL as well as the ROM, so they can't be broken up to only do one or the other.
It sounds like you're trying to get to an older ROM version (for whatever reason) with an older security patch level as well? Basically, this cannot be done on Snapdragon phones. Once you're on an updated binary/BL, you're stuck there (at least today you are).
Click to expand...
Click to collapse
I've tried different firmwares, its all about snapdragon. You can also flash SM-G975W parts and other snapdragon variants.... there's a lot of variants out there.
I first upgraded and then downgraded to the parts i wanted and am on a rom now with security patch level December 2022, as long as the binary version is the same there's no problem. I've got the latest modem installed and the oldest firmare and bootloader for the latest binary version, i can upgrade or downgrade my bootloader. I already asked someone before if this was possible and if he could confirm because before i was only able to flash CSC and AP i think.
If there's no updates comming anymore why not downgrade and wait for a new leak
I'm also sure we can unlock the bootloader, i'm trying to make an lposed module. I've installed lspatch and lposed and they work fine for some modules. The bootloader unlock has several prerequisites (properties and such) if i can make it look for other properties or something like that we might get an unlock option. Also it looks for an encrypted file on EFS, if someone with an unlocked samsung phone could copy that file we would be a lot further.
It's called /efs/sec_efs/sktdm_mem/encmembership.txt and should be an encrypted file, also if anyone knows how to set ro properties without root (like a stub before the preference controller starts) this would be very usefull.