[G935F] ENG sboot and eng boot - Samsung Galaxy S7 Edge Guides, News, & Discussion

Hello, so I got an eng sboot from here: https://boxwares.net/bd72f04e285c7819ed1f1fc4678e9c4f/G935FXXU5ASD2_ENG_sboot_BoxWares.tar.md5 and eng boot from here: https://boxwares.net/def022c0c13989fa68278d4ae3f226e2/G935FXXU5ASD2_ENG_boot_BoxWares.tar.md5 haven't rooted my device yet cause I always use Samsung Pay. Anyone tried it? What does it do? Does it allow flashing twrp without tripping Knox? I'm currently on March 1, 2019 security patch with build no. G935FXXS4ESCC

pascua28 said:
Hello, so I got an eng sboot from here: https://boxwares.net/bd72f04e285c7819ed1f1fc4678e9c4f/G935FXXU5ASD2_ENG_sboot_BoxWares.tar.md5 and eng boot from here: https://boxwares.net/def022c0c13989fa68278d4ae3f226e2/G935FXXU5ASD2_ENG_boot_BoxWares.tar.md5 haven't rooted my device yet cause I always use Samsung Pay. Anyone tried it? What does it do? Does it allow flashing twrp without tripping Knox? I'm currently on March 1, 2019 security patch with build no. G935FXXS4ESCC
Click to expand...
Click to collapse
Par my knowledge, its just the combination rom, you can't use combination rom bootloader/kernel + normal rom as it never works.
Theoretically it is possible, as snapdragon variants were rooted using engineering boot/kernel as it had no option for oem unlock. But they have had many bugs and problems, I don't know which method is currently used for rooting snapdragon variants.
But no I have not seen or known any exynos user successfully using eng boot and then able to root without tripping knox or even booting phone using it..
Sent from my S7 Edge using XDA Labs

Related

New Update - QI2

According to the Verizon Galaxy S5 Update Page:
Android® Security Patch Level: 2017–08-01
The current software update gives you the most up to date Android security patches on your device.
Click to expand...
Click to collapse
This is basically the same thing they are doing with other devices. Since Samsung never released their September Security patch due to them addressing the BlueBorne problem, they have been re-releasing the QH* updates as QI* but they include the BlueBorne patch. For some reason, Verizon didn't include the BlueBorne patch in the changelog like they have been for every other phone.
For example. The Galaxy S6, Galaxy S8, and Galaxy S8+ updates all say
Includes: Blueborne security patch
The current software update gives you the most up to date Android® security patches on your device.
Click to expand...
Click to collapse
Who knows why they chose to include the exact same changelog as the prior update with the same security patch. Whatever. Verizon sucks. We all know it.
Stock No-Wipe Firmware:
*This will remove Developer Status/Lock your Bootloader*
G900VVRU2DQI2_G900VVZW2DQI2_G900VVRU2DQI2_HOME.tar.md5.zip
Developer Bootloader Friendly/No Aboot No-Wipe Firmware:
G900VVRU2DQI2_G900VVZW2DQI2_G900VVRU2DQI2_HOME_No_Aboot.tar.md5.zip
Also, I'm not sure how much longer I'll be doing this though because the screen on my S5 is going bad (flickering and flashing green whenever I bring it out of sleep) so this weekend I'm getting an S8+.
so its safe to say that the new modem ql2 is pretty much the same sa the previous update?
Updated to this build from QH2, flashed in odin, then booted up, reflashed TWRP and SU, froze system updater all good. If you do end up leaving, this will just be another loss for this model as no one else is updating the stock images anymore.
Thank you for your work on this. Does this have root, and if not, do those of us with locked bootloaders have a way to keep root and safestrap?
Tell us how the S8+ goes and if you can unlock the bootloader and root that. Thanks again!
Dudash said:
Stock No-Wipe Firmware:
*This will remove Developer Status/Lock your Bootloader*
G900VVRU2DQI2_G900VVZW2DQI2_G900VVRU2DQI2_HOME.tar.md5.zip
Developer Bootloader Friendly/No Aboot No-Wipe Firmware:
G900VVRU2DQI2_G900VVZW2DQI2_G900VVRU2DQI2_HOME_No_Aboot.tar.md5.zip
Also, I'm not sure how much longer I'll be doing this though because the screen on my S5 is going bad (flickering and flashing green whenever I bring it out of sleep) so this weekend I'm getting an S8+.
Click to expand...
Click to collapse
For the record, this loses root, and loses safestrap. I'm too dumb to know how to root this since I can't get TWRP on this phone, so I'm going to hope the way back to root and safestrap is get back Kitkat and then up to PB1 starting over using these steps.. This will probably be better for someone who knows what they're doing or just wants to upgrade for the security updates and doesn't care about root.
androidman807 said:
Thank you for your work on this. Does this have root, and if not, do those of us with locked bootloaders have a way to keep root and safestrap?
Tell us how the S8+ goes and if you can unlock the bootloader and root that. Thanks again!
Click to expand...
Click to collapse
I have a 15 Emmc chip and unlocked the bootloader via this thread: https://forum.xda-developers.com/ve.../testers-required-easier-root-method-t3561529
I flashed EMMC_15_VZW_QB2_STOCK_MAGISK_ROOT.zip to my phone. I also have TWRP installed.
Now, if I understand all this correctly, I can simply flash your Developler Boatloader friendly version via TWRP? This will upgrade my OS to the latest update? Then flash Magisk to get root back?
This all seems too simple.
You will also have to re-flash TWRP via Odon.
kevin98208 said:
I have a 15 Emmc chip and unlocked the bootloader via this thread: https://forum.xda-developers.com/ve.../testers-required-easier-root-method-t3561529
I flashed EMMC_15_VZW_QB2_STOCK_MAGISK_ROOT.zip to my phone. I also have TWRP installed.
Now, if I understand all this correctly, I can simply flash your Developler Boatloader friendly version via TWRP? This will upgrade my OS to the latest update? Then flash Magisk to get root back?
This all seems too simple.
Click to expand...
Click to collapse
HolyHog said:
You will also have to re-flash TWRP via Odon.
Click to expand...
Click to collapse
I too followed the instructions in the thread above for a CID 15 eMMC.
I was unable to flash the "G900VVRU2DQI2_G900VVZW2DQI2_G900VVRU2DQI2_HOME_No_ Aboot.tar.md5.zip" from the OP using TWRP, but was able to do it no problem using Odin 3.12 (AP option).
After flashing that I then used Odin again (AP option) to flash the latest TWRP (https://dl.twrp.me/klte/twrp-3.1.1-0-klte.img.tar.html). I then did another factory reset on the phone (since I had already just wiped my data following the bootloader instructions) and reinstalled Magisk from TWRP and MagiskManager.
Everything looks great so far. Thanks for this update OP and for those of you providing guidance.
I have G900VVRU2DPD1 with unlocked bootloader and twrp 3.0.0-0.
Can I flash the
Developer Bootloader Friendly/No Aboot No-Wipe Firmware:
G900VVRU2DQI2_G900VVZW2DQI2_G900VVRU2DQI2_HOME_No_ Aboot.tar.md5.zip ?
If yes, after flashing, will my bootloader remain PD1 unlocked? Is it OK to have unlocked PD1 bootloader with DQI2 firmware?
Will the TWRP and root be lost? And how I can get back TWRP? Using ODIN? If root is lost then can not use flashify to flash TWRP.
If using odin to flash TWRP, then I can just flash supersu zip in zip to get root back, right?
Thanks.
I guess this is slightly off topic since it's not about this specific firmware version, but here goes ~
How do you guys go about extracting firmware/modems from stock ROM updates?? It boggles my mind lol. I'm running a OP3T now, but am working on an old device (and I still have my old S5 too). Over the years it appears people are now able to do this process for most devices and make it flashable one way or another.
I wish I understood how this gets done (and possibly figure out how to do it myself). Would love a guide / video / brief explanation with terms I could look up if it's long & involved??
Thanks for the work!
purplepenguin said:
How do you guys go about extracting firmware/modems from stock ROM updates??
Click to expand...
Click to collapse
Stock ROM update is just a tar archive with files inside.
The names of the files are mostly self-explaining.
Use some tool to access the archive, like Total Commander or 7zip archiver.
bbsc said:
Stock ROM update is just a tar archive with files inside.
The names of the files are mostly self-explaining.
Use some tool to access the archive, like Total Commander or 7zip archiver.
Click to expand...
Click to collapse
Hmmm and then to make flashable??
purplepenguin said:
Hmmm and then to make flashable??
Click to expand...
Click to collapse
Just pack what you want into tar archive and it will be flashable.
No need to attach checksum.
But it's possible too.
Say, this tar-file is flashable:
Missing apps
TraderJack said:
and reinstalled Magisk from TWRP and MagiskManager.
Click to expand...
Click to collapse
Can I reuse the same Magisk from the "EMMC_15_VZW_QB2_STOCK_MAGISK_ROOT.zip" file from the other thread on how to unlock bootloader and root, or should I download the latest Magisk and MagiskManager?
Edit 1: Okay, I installed Magisk after updating to the latest QI2 and am rooted. However, I found that I'm missing busybox and safestrap. Do I have to reinstall both of those as well or can I just reinstall busybox?
Also, QI2 lost tether/hotspot capability as it reverted back to asking to purchase the service (I'm also on the old grandfathered unlimited plan)...is there a way to get it back as when on rooted QB2?
Edit 2: Did some more research while hiding at work...so now I know, having TWRP recovery is enough and just need to reinstall busybox.
Now still need to find a way to get hotspot capability back like when on the rooted magisk QB2...
Thanks

Custom ROMs on S8+ Verizon Model

Hi,
I have purchased a Galaxy S8+ Verizon version, I want to know if I could install custom ROMs on it from the stock galaxy s8+ page. I am a little confused about this as I want to try out different ROMs, Also will installing different ROMs unlock the device?
Thanks
LOL. You purchased the wrong device if you wanted custom ROMs. You can only flash stock official ROMs via Odin on the North American Snapdragon S8. There is no unlock for us.
All you can do is root it: https://forum.xda-developers.com/galaxy-s8/development/samsung-galaxy-s8-root-snapdragon-t3659305
Maybe??
https://forum.xda-developers.com/ga...root-partcyborgrom-aqk3-samfail-odin-t3717702
So I understand that the bootloader verification and lock is why we can install TWRP, but I swear on my Razr(XT912) or Bionic or G3 had a locked bootloader but they had a way to boot the ROM after initial boot you would have a way to boot the regular system or boot to custom Rom. Killing me right now what name of it was, is it just that there was an exploit or is the security much stricter
bmxmike said:
So I understand that the bootloader verification and lock is why we can install TWRP, but I swear on my Razr(XT912) or Bionic or G3 had a locked bootloader but they had a way to boot the ROM after initial boot you would have a way to boot the regular system or boot to custom Rom. Killing me right now what name of it was, is it just that there was an exploit or is the security much stricter
Click to expand...
Click to collapse
It was probably exploit like safestrap No exploits have been found obviously for our devices yet

How to Downgrade S7 930U Snapdragon from Nougat 7 to Marshmallow 6?

I prefer the speed and performance of marshmallow on the S7. Where are the correct files I should flash in Odin and which version of Odin should I be using to flash Android 6?
So apparently the camera isn't working after downgrade to 6?
Not something I'm willing to deal with unless the issue has been solved.
You can't downgrade snapdragon S7 models (G930U/T/V/A/P) due to the locked bootloader
Any downgrading would only work on the G930F with OEM unlock
Help root or downgrade or both?
Beanvee7 said:
You can't downgrade snapdragon S7 models (G930U/T/V/A/P) due to the locked bootloader
Any downgrading would only work on the G930F with OEM unlock
Click to expand...
Click to collapse
I have a sm-g930u factory unlocked and Im also trying to get all i need to downgrade from oreo which is havoc on my battery and i dont know if its better to downgrade to laterst nougat or root it and take care of bloatware to help battery drain yet the problem will persist which is that the upgrade is designed for s8 and s9 with octacore processor and the s7 is working harder with a quad core so temp will always be hotter than before and slower than with nougat . Any help with proper step by step in downgrading my factory unlocked phone would be appreciated and any root links as i havent done it in years.
Beanvee7 said:
You can't downgrade snapdragon S7 models (G930U/T/V/A/P) due to the locked bootloader
Any downgrading would only work on the G930F with OEM unlock
Click to expand...
Click to collapse
You can downgrade. You just can't root.
dave678 said:
You can downgrade. You just can't root.
Click to expand...
Click to collapse
thats not true
You can downgrade any version bit loader by flashing the combo firmware and the rooting combo firmware then flash stock nougat system image its basically what the root method is for Rev11/B. If you are just on nougat then you would have to get the combo firmware that matches the bootloader version you have because if you flash my rev11/B root method you are forever stuck on that bootloader and can never use nougat again or have oreo root as there is no eng root boot.img available for oreo root on rev11/B bootloader
jrkruse said:
You can downgrade any version bit loader by flashing the combo firmware and the rooting combo firmware then flash stock nougat system image its basically what the root method is for Rev11/B. If you are just on nougat then you would have to get the combo firmware that matches the bootloader version you have because if you flash my rev11/B root method you are forever stuck on that bootloader and can never use nougat again or have oreo root as there is no eng root boot.img available for oreo root on rev11/B bootloader
Click to expand...
Click to collapse
Oh I meant if you're not rooted.
dave678 said:
Oh I meant if you're not rooted.
Click to expand...
Click to collapse
you can downgrade too marshmallow from any version you have because combo firmware for s7 is marshmallow based and its available for all bootloader versions. You just use the combo bootloaders and boot.img and stock system image then root it
If your still on bit 4 you can just flash stock bit 4 marsmallow and root with marshmallow eng root img

Downgrading G611F to a lower bootloader

Hello, i was trying to downgrade my phone from OneUI (Android 9) to samsung experience (Android 7) on G611F because latest version makes the device too slow for me and also i like samsung experience more than OneUI but seems that even when bootloader is unlocked it can't be downgraded from S3 to U1 and i face sw rev. check fail (bootloader) device 3, binary 1 error.. unfortunately trying to flash without BL gives same error with kernel (boot image).. is there any workaround to get this working? The bootloader already unlocked and i don't bother tripping knox or use custom recovery to flash stock old rom but i don't know if that would work or will give me same error during boot with kernel and other partitions.. also i'm worried about using a custom recovery to flash BL and downgrade bootloader by writting the old one directly to the proper partition with dd in terminal as i don't know if doing this will hard brick the device or not..
Is there any way i can use to downgrade to stock samsung experience rom?..
Thanks!
Same question sir...?

Samsung A11 got android 12 and I want to flash it (help)

So I first bought my Samsung a11 as an android 10 model,
I then flashed it after I bought it with an open-line android 11 version and got twrp and root. This was a year ago I think.
Now they released the final update for this Samsung phone model, and I want to at least get the latest and last version of my phone.
But I kinda forgot how to do the procedures again.
So my question is does flashing the new android version firmware using odin remove TWRP installed on my device?
my phone model is: A115FXXU2BUJ2 (android 11)
the firmware I want to install: A115FXXU3CV13 (android 12)
if so what do I need to do in order to successfully have both the new firmware I want to install and twrp installed on my device? (i kinda know how to root using twrp and magisk so no problems here)
Any help would be much appreciated!
????.?? said:
So I first bought my Samsung a11 as an android 10 model,
I then flashed it after I bought it with an open-line android 11 version and got twrp and root. This was a year ago I think.
Now they released the final update for this Samsung phone model, and I want to at least get the latest and last version of my phone.
But I kinda forgot how to do the procedures again.
So my question is does flashing the new android version firmware using odin remove TWRP installed on my device?
my phone model is: A115FXXU2BUJ2 (android 11)
the firmware I want to install: A115FXXU3CV13 (android 12)
if so what do I need to do in order to successfully have both the new firmware I want to install and twrp installed on my device? (i kinda know how to root using twrp and magisk so no problems here)
Any help would be much appreciated!
Click to expand...
Click to collapse
Yes, flashing the update via Odin will remove TWRP and root, it will also, more than likely, lock your bootloader, then you won't be able to reinstall TWRP or root the device unless you unlock the bootloader, if it can be unlocked.
Droidriven said:
Yes, flashing the update via Odin will remove TWRP and root, it will also, more than likely, lock your bootloader, then you won't be able to reinstall TWRP or root the device unless you unlock the bootloader, if it can be unlocked.
Click to expand...
Click to collapse
My phone's bootloader is already unlocked, after flashing the updated android version firmware will the bootloader become lock again? and how do i avoid rmm and frp lock?(just incase this happens)
????.?? said:
My phone's bootloader is already unlocked, after flashing the updated android version firmware will the bootloader become lock again? and how do i avoid rmm and frp lock?(just incase this happens)
Click to expand...
Click to collapse
If the bootloader in the update is a securely locked bootloader, it will probably have locked bootloader after flashing and might not be able to be unlocked. That was the whole point of me warning you in my last post. Now I've had to post again just to say the same thing that I already said. I guess I was talking to the wind.
There is no way to know what the results will be after updating unless you find someone that has already updated the exact same model number of A11 or bite the bullet and update yours then see what you get.
Droidriven said:
If the bootloader in the update is a securely locked bootloader, it will probably have locked bootloader after flashing and might not be able to be unlocked. That was the whole point of me warning you in my last post. Now I've had to post again just to say the same thing that I already said. I guess I was talking to the wind.
There is no way to know what the results will be after updating unless you find someone that has already updated the exact same model number of A11 or bite the bullet and update yours then see what you get.
Click to expand...
Click to collapse
I see, looks like i need to find someone who have done it and see if it works. I didnt get what you mean about after flashing, it might have a chance to lock the bootloader depends on the update. I think ill just try and see what happens. Thank you.
I dont know guys with that phone but there should be a tool that bypass auth and unlock the bootloader in any case. I ONLY knows MTK devices, not sure about that samsung i use a .Bat file.
????.?? said:
I see, looks like i need to find someone who have done it and see if it works. I didnt get what you mean about after flashing, it might have a chance to lock the bootloader depends on the update. I think ill just try and see what happens. Thank you.
Click to expand...
Click to collapse
No, I said that after the update, it could cause the bootloader to be locked and then may not be unlockable from that point on. It depends on the bootloader in the update. If this happens, you will be unable to install TWRP or root via Magisk. That is why you need to confirm whether or not flashing the update will relock the bootloader during the flashing process and, if it does, whether or not it can be unlocked again after the update.
In other words, look at exactly what you are about to jump into before you make the jump because you might land in the one place that you absolutely do not want to land.

Categories

Resources