I did a factory reset. It was stuck in "Erasing" for an hour.
1. Restart -> Booted back to Erase mode
2. Bootloader -> Recovery mode -> Booted back to Erase mode
3. Bootloader -> Start -> Booted back to Erase mode
4. USB connection -> no device recognized
5. ???
6. Profit!
Anyone has an idea what to try? Android 6.0. Unlocked, Rooted on Kitkat but didnt modify anything after the update. Bootloader HHZ12k, rev_11
P.S.
Im serious about 5. and 6. Verizon gave me 300 USD for trading in the formerly working phone.
I don't know about the Verizon version of the phone but if it is like the gsm version, you could unlock the bootloader and flash a stock rom.
Need help please
the device was initially on nougat 7.1.1, i activated oem unlock and flashed oreo 8.0 then flashed pie 9.0 then downgrade back to oreo
now nothing pass by odin, i cannot flash twrp to root or any other stock firmwar
oem unlock is missing from dev option menu
more than 7 days of continuous uptime and still no oem unlock option visible
tried days and time trick >> same issue
device : Sm-a530f/ds
firmare : Stock oreo
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
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