Code:
#include <std_disclaimer.h>
/*
* Your warranty is now void.
*
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this patch
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you.
*/
INFO:
This is a patch and SaR kernel made for @prashantp01's Vendor Dumpster V1.1.
SaR (System as Root) means the system partition is mounted as the root filesystem.
This allows our phone to boot System-as-Root (also labelled as A/B) GSIs which are the only type of GSIs still supported officially by Google.
There are two types of boot images I'm providing:
Android 9 style ramdiskless SaR
Android 10 style 2-stage init SaR
In general, you should use the Android 9 version for Android 9 based GSIs, and use whichever you want for Android 10 or newer.
The kernel is a modified version of @prashantp01's Quantum Kernel v4.0.
Source code for it is available here: github.com/VDavid003/universal7885_SaR
If you are used to using PHH-Magisk, now you don't have to: you can use normal Magisk on A/B GSIs.
NOTE:The patch and kernel are currently not tested on A530W and A730F. Please tell me if it works or not!
BUGS:
-Basically every bug that is present in the original Vendor Dumpster V1.1
-Secure lock screen can't be set (no pattern/pin/password unlock)
-Seems like Android 11 Developer Preview 2 and later does not currently work. DP1 works fine tho, you can download it here.
INSTALL INSTRUCTIONS:
Follow the instructions to install Vendor Dumpster V1.1.
Flash the SaR Patcher zip from TWRP(this will still let you boot non-SaR GSIs, but it will make the vendor compatible with SaR GSI)
Install a SaR boot.img (P or Q) for your model. (TWRP -> Install -> Install Image -> Select your boot.img -> Select Boot from the list -> Swipe to flash)
Flash an A/B or SaR GSI as you would do normally.
DOWNLOADS:
The root folder contains the vendor patcher zip, and the boot.img folder contains boot.imgs
Naming scheme for them: boot_[MODEL]_[P/Q].img
DOWNLOAD HERE
SPECIAL THANKS:
@prashantp01 for his vendor and kernel. Go support him!
Everyone involved in his vendor/kernel.
CHANGELOG
1.0:
-Initial release with some stuff accidentally left out
1.1:
-Fixed RIL (temporary fix currently), and enabled the media codec fix I forgot to enable in 1.0
TESTING WITH AB GSI ROMs
It works on the SM-A730F when flashing the android 10 boot image with an AB android 10 GSI but mobile services doesn't work, unfortunately and also it messed up the system time a bit but everything else works
Kaduah13 said:
It works on the SM-A730F when flashing the android 10 boot image with an AB android 10 GSI but mobile services doesn't work, unfortunately and also it messed up the system time a bit but everything else works
Click to expand...
Click to collapse
Mobile services should work now with 1.1, but what do you mean by messing up the system time?
VDavid003 said:
Mobile services should work now with 1.1, but what do you mean by messing up the system time?
Click to expand...
Click to collapse
I use GMT but it often switches to EAT even though I set it back to GMT
after every reboot I made.
VDavid003 said:
Mobile services should work now with 1.1, but what do you mean by messing up the system time?
Click to expand...
Click to collapse
The version 1.1 works but for mobile services, only one SIM slot works.
Hi! Android 10 QQ2A.200405.005 descendant x samsung a8+ not working fingerprint. Thanks !
OEM unlocked in developer option but RMM state paranormal in Download Mode
3 weeks ago i accidentally installed a ROM, without installing RMM patch in TWRP mode.
Phone bricked, then i installed pie room with Odin.
what I saw in developer option after installing new pie room, there was OEM unlock option, but even after enabling it, i was getting as below :
KG state checking
RMM state paranormal
FRP lock off
oem lock off
i waited for a week then KG state gone only RMM state left, what is saw was:
RMM state paranormal
FRP lock off
oem lock off
i waited one more week after 168 hours , RMM state is still there even after OEM unlocked in development option.
Please help me i can not downgrade too because is have boot-loader U7 .
Help me to downgrade or help me to install twrp.
one thing i want to add is, when i turned on oem unlock option, i see this in download mode:
RMM state paranormal
FRP lock off
oem lock off
when i turned off oem unlock option, i see this in download mode:
RMM state paranormal
FRP lock off
oem lock on
---------- Post added at 02:31 PM ---------- Previous post was at 02:30 PM ----------
OEM unlocked in developer option but RMM state paranormal in Download Mode
OEM unlocked in developer option but RMM state paranormal in Download Mode
3 weeks ago i accidentally installed a ROM, without installing RMM patch in TWRP mode.
Phone bricked, then i installed pie room with Odin.
what I saw in developer option after installing new pie room, there was OEM unlock option, but even after enabling it, i was getting as below :
KG state checking
RMM state paranormal
FRP lock off
oem lock off
i waited for a week then KG state gone only RMM state left, what is saw was:
RMM state paranormal
FRP lock off
oem lock off
i waited one more week after 168 hours , RMM state is still there even after OEM unlocked in development option.
Please help me i can not downgrade too because is have boot-loader U7 .
Help me to downgrade or help me to install twrp.
one thing i want to add is, when i turned on oem unlock option, i see this in download mode:
RMM state paranormal
FRP lock off
oem lock off
when i turned off oem unlock option, i see this in download mode:
RMM state paranormal
FRP lock off
oem lock on
Related
I rooted my s7, latest version of 8.0 United Kingdom (g930fxxu4esae build r16nw.g930fxxs5esf6). I used TWRP and magisk.
All was well until I rebooted, then got the dreaded "custom binary blocked by frp lock". I was able to take the stock rom and install the AP file, and now it's working again except that of course root is gone. I suspect that if I attempt to root again, I will run into the same error on a reboot.
I've done some googling but haven't found anything really reliable sounding about getting around this problem.
EDIT: UPDATE: I've flashed the latest version of BTU on phones 1 and 2. I've successfully rooted phone 1 and it seems to be sticking. Phone 2 I'm still working on, it doesn't have to be rooted though as it's more of a backup for gaming. Thanks again to everyone in this thread for all the good advice and info.
You are going to have to re flash you current firmware unrooted and before you root, enable OEM unlocking in developer options AFTER setting up your google account(you have to use the same google account as you did before), unfortunately there is no way of force enabling OEM unlock with a flashable zip on the s7, well least to my knowledge. FRP lock is googles factory reset protection, which stops people from factory resetting a phone and then just use their google account instead of the one they don't know the password too, and it stops custom binaries like trwp from booting and even a stock binary that has been rooted from booting because it thinks you could be trying to bypass FRP.
Enabling OEM unlocking with disable FRP lock on the device, allowing you to use custom binary and boot normally without the checks.
Viper4060 said:
You are going to have to re flash you current firmware unrooted and before you root, enable OEM unlocking in developer options AFTER setting up your google account(you have to use the same google account as you did before), unfortunately there is no way of force enabling OEM unlock with a flashable zip on the s7, well least to my knowledge. FRP lock is googles factory reset protection, which stops people from factory resetting a phone and then just use their google account instead of the one they don't know the password too, and it stops custom binaries like trwp from booting and even a stock binary that has been rooted from booting because it thinks you could be trying to bypass FRP.
Enabling OEM unlocking with disable FRP lock on the device, allowing you to use custom binary and boot normally without the checks.
Click to expand...
Click to collapse
Correct basically turn FRP lock off it's a pain in the ass.
Also @kettir this is the final release of BTU not the one you have in your post 》》https://www.sammobile.com/samsung/galaxy-s7/firmware/SM-G930F/BTU/download/G930FXXU5ESD2/270504
cooltt said:
Correct basically turn FRP lock off it's a pain in the ass.
Also @kettir this is the final release of BTU not the one you have in your post 》》https://www.sammobile.com/samsung/galaxy-s7/firmware/SM-G930F/BTU/download/G930FXXU5ESD2/270504
Click to expand...
Click to collapse
Thanks for more great advice and info. It appears that now the requirements are:
Download the latest BTU as per your note because I like it better
Flash it to attain a "stock" system.
Go through the minimum setup after reboot and get developer options.
Set up google account
Enable OEM unlocking (and USB debugging of course)
flash TWRP
go into recovery immediately
Use TWRP to flash magisk
go back into download mode immediately
flash only the AP from the stock firmware
And this might, possibly, achieve root with magisk, while keeping the stock bootloader. That is, if I understand what TWRP and magisk are actually doing to the system. I.e., TWRP replaces the system part that handles recovery, while magisk roots the phone without changing the system, so that TWRP is the problem for FRP.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Orange Fox custom recovery
Code:
[
/*
* Your warranty is now void.
*
* We're not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this recovery
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at us for messing up your device, we will laugh at you.
*
*/
What is Orange Fox?
This custom recovery is based off TWRP, but has added features and different styling.
For more information visit the official wiki - HERE
Features
* Updated with latest TWRP commits
* Built-in support for installing Magisk
* White Flashlight
* Password pretext your recovery
* Better language support
* Optimized versions of community scripts
* Fox theme engine:
- choice of theme (black, dark, etc)
- choice of color scheme
- choice of splash screen
* Alternative lockscreen
Credits
* @BlackMesa123 - for Official TWRP
* The OrangeFox Team - for your hard work
* Thanks to the main contributor @Mijotchi - Without him this would not have been possible
* All our testers - for your patience and help
Downloads
Sourceforge: jackpot2lte
Installation
1. Download the OrangeFox zip to your device
2. Reboot to your existing OrangeFox (or other custom TWRP-based) Recovery
3. Install the OrangeFox zip as a normal zip installer
4. The device will automatically reboot into OrangeFox recovery after installation (allow this to happen)
5. Enjoy!
FAQ and Guides: https://wiki.orangefox.tech/en/guides
XDA:DevDB Information
OrangeFox Recovery Project [R11.0], Tool/Utility for the Samsung Galaxy A8+ (2018)
Contributors
prashantp01, Mijotchi
OFRP Code: https://gitlab.com/OrangeFox
Kernel Code: https://github.com/prashantpaddune/universal7885
Device Tree: https://github.com/YuMi-Project/android_device_samsung_jackpot2lte
Version Information
Status: Stable
Current Stable Version: R11.0
Created 2020-08-21
Last Updated 2020-08-21
reserved
reserved 2
Helloooo, im here again to say:
Thx sir lmfao xd, nice work of u dt too
Thanks!
It's beautiful.
Tested working.
Anyone tried resizing partitions?
hackuletz16 said:
It's beautiful.
Tested working.
Anyone tried resizing partitions?
Click to expand...
Click to collapse
it shoud work
USB OTG cannot be detected.
other than that everything works fine.
OEM unlocked in developer option but RMM state paranormal in Download Mode
3 weeks ago i accidentally installed a ROM, without installing RMM patch in TWRP mode.
Phone bricked, then i installed pie room with Odin.
what I saw in developer option after installing new pie room, there was OEM unlock option, but even after enabling it, i was getting as below :
KG state checking
RMM state paranormal
FRP lock off
oem lock off
i waited for a week then KG state gone only RMM state left, what is saw was:
RMM state paranormal
FRP lock off
oem lock off
i waited one more week after 168 hours , RMM state is still there even after OEM unlocked in development option.
Please help me i can not downgrade too because is have boot-loader U7 .
Help me to downgrade or help me to install twrp.
one thing i want to add is, when i turned on oem unlock option, i see this in download mode:
RMM state paranormal
FRP lock off
oem lock off
when i turned off oem unlock option, i see this in download mode:
RMM state paranormal
FRP lock off
oem lock on
---------- Post added at 02:31 PM ---------- Previous post was at 02:30 PM ----------
OEM unlocked in developer option but RMM state paranormal in Download Mode
3 weeks ago i accidentally installed a ROM, without installing RMM patch in TWRP mode.
Phone bricked, then i installed pie room with Odin.
what I saw in developer option after installing new pie room, there was OEM unlock option, but even after enabling it, i was getting as below :
KG state checking
RMM state paranormal
FRP lock off
oem lock off
i waited for a week then KG state gone only RMM state left, what is saw was:
RMM state paranormal
FRP lock off
oem lock off
i waited one more week after 168 hours , RMM state is still there even after OEM unlocked in development option.
Please help me i can not downgrade too because is have boot-loader U7 .
Help me to downgrade or help me to install twrp.
one thing i want to add is, when i turned on oem unlock option, i see this in download mode:
RMM state paranormal
FRP lock off
oem lock off
when i turned off oem unlock option, i see this in download mode:
RMM state paranormal
FRP lock off
oem lock on
Hi, the download link doesn't work for me, is it still available?
Auramass said:
Hi, the download link doesn't work for me, is it still available?
Click to expand...
Click to collapse
Nope
Please fix the link
Is it possible to lock the bootloader with TWRP and a custom ROM installed and still use the device? Can I still flash ROMs in TWRP without hard/soft bricking my POCO?
Ungeskriptet said:
Is it possible to lock the bootloader with TWRP and a custom ROM installed and still us the device? Can I still flash ROMs in TWRP without hard/soft bricking my POCO?
Click to expand...
Click to collapse
Short Answer: No it's not feasible to do that, reason behind that is AVB 2.0 (Android Verified Boot). It checkes for a pre-existing hash of all paritions signed by the OEM key (in this case Xiaomi), If there are conflicts found and Bootloader is in Locked state, The result would be a Fatal Error and would skip booting The OS to go to repair mode (aka EDL mode), which you can access in Xiaomi devices only if you have a verified EDL account.
Besides, even if you modify the Bootloader Binery or signed the twrp.img with the oem key (which you don't have access to), you wouldn't be able to flash anything anyway, since the device would consider any modifications after that a fatal error as well and won't boot.
Long Answer: read up on the follwing topics:
1- Android verified boot https://android.googlesource.com/platform/external/avb/+/master/README.md
2- FROST attack on unlocked bootloader (The reason android implemented avb) https://www.cs1.tf.fau.de/research/system-security-group/frost/
This patched boot image will allow you to root galaxy a125m(latin america variant) running andorid 11 security patch level 1 october 2021 fimware A125MUBU1BUJ5
Keep in mind that
This rooted boot.img will wipe all data(THIS IS NOT COUNTING THE MANDATORY WIPE WHEN UNLOCKING BOOTLOADER)
Backup anything you need before flash
To root:
Boot on download mode
Make sure frp lock and oem lock are off
If frp is on remove google accounts and lock screen secruity,if oem is on unlock bootloader
Make sure kg state is either checking or that the line is missing
If kg is prenormal insert a valid sim card,connect to wifi,log on to a vaild samsung account ,check for updates and wait 60 seconds for oem unlock to activate
You can also google oem unlock missing samsung
Then flash image in ap
Device will bootloop a few tines and show recovery choose factory data reset and wait after you finish setup activate oem unblock and gain access to home screen install this apk then agree to do additional setup and reboot
I'm Trying to Root my Galaxy A51 using magisk & this is first time i'm trying to root phone. i followed this guide https://forum.xda-developers.com/t/...flash-official-firmware-binary-3-may.4053065/
when i tried to flash AP file of magisk, i'm getting error "Only Official release binaries are allowed to be flashed (VBMETA)"
i tried to flash stock VBMETA but it doesn't Root the Phone.
i tried to flash twrp recovery but still getting same error message "Only Official release binaries are allowed to be flashed".
is there any way to solve this problem & root my phone ??
Did you read this thread?
[SOLVED]Stuck on Only official released binaries are allowed to be flashed(vbmeta)
Hi! I was following the root guide [RECOVERY][UNOFFICIAL][ROOT] TWRP for Galaxy A70 and it seems that I forgot to check that the OEM unlock was still enabled after flashing vbmeta.tar and flashing TWRP v3.3.1-5, now my phone is stuck in a screen...
forum.xda-developers.com
ze7zez said:
Did you read this thread?
[SOLVED]Stuck on Only official released binaries are allowed to be flashed(vbmeta)
Hi! I was following the root guide [RECOVERY][UNOFFICIAL][ROOT] TWRP for Galaxy A70 and it seems that I forgot to check that the OEM unlock was still enabled after flashing vbmeta.tar and flashing TWRP v3.3.1-5, now my phone is stuck in a screen...
forum.xda-developers.com
Click to expand...
Click to collapse
yes, i tried & didn't work.
i doubt that the recent Samsung update has something to do with it. maybe Samsung has forcefully locked bootloader so that no one else can flash custom os.
I Found the solution. KG STATE was Prenormal in bootloader.
Solution is simple,
- turn on wifi/internet
- enable developer option
- open developer option Settings>Developer Options
- check if "OEM Unlocking" is disabled or not. if disabled then it's OK & ready to flash