How To Guide How To: Unlock Bootloader - Samsung Galaxy A12

How To Unlock Bootloader Galaxy A12.
Code:
*** Disclaimer
I am not responsible for any damage you made to your device
You have been warned
- Go to Settings -> About phone and find your build number.
- Tap on your build number 6 times until you see “You’re now a developer”.
- Go in Developer options > enable OEM unlocking.
- Shut Down your Phone
- Hold Vol + & Vol - and Connect the USB-C Cable
- Device will boot in DOWNLOAD MODE.
- Long press volume UP to unlock the bootloader.
( This will wipe your data and automatically reboot your device! )
- After Reboot the Bootloader is unlocked.

I have done exactly this and the Samsung A12 is now in a boot loop. I have already tried the following:
- Press the power button for a long time.
- Press vol-down+power and if it is turned off only power (https://www.naldotech.com/how-to-fix-bricked-samsung-galaxy-a12-stuck-in-bootloop/)
- Vol-down + vol-up and connect C-USB
- Some variations on this.
UPDATE:
When I tried Vol-down + vol-up and connect C-USB again, it worked and I unlocked the bootloader.

jkaltes said:
I have done exactly this and the Samsung A12 is now in a boot loop. I have already tried the following:
- Press the power button for a long time.
- Press vol-down+power and if it boots only power
- Vol-down + vol-up and connect C-USB
- Some variations on this.
Click to expand...
Click to collapse
Vol-down + vol-up and connect C-USB. You can boot to download mode by this way

It’s how easy Samsung devices are OEM unlocked
1. Tap Build number 7 to 10 times ... You’re now a developer
2. Take software updates
3. Developer settings
4. Allowance of OEM unlocking
5. Start Heimdall (Odin) on desktop to tether your A12 thru USB-C
6. <Vol+> + <Vol-> to reboot to Download mode
7. Long press <Vol+> to unlock bootloader

<Vol+> + <Vol-> + connect C-USB to reboot to Download mode

Hi, I'm new to all this and hopefully I'm just missing something obvious. When I put my A12 into Download Mode, I have no option for a volume-up long-press, as seen in attached photo. I have an A125U model if that information is at all relevant. Developer mode is on, and OEM unlocking is enabled. Not sure where to go from here, any insight would be greatly appreciated!
{
"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"
}

Will this method work on an A12 from ATT that's SIM-locked?

..

crungtrusse said:
Hi, I'm new to all this and hopefully I'm just missing something obvious. When I put my A12 into Download Mode, I have no option for a volume-up long-press, as seen in attached photo. I have an A125U model if that information is at all relevant. Developer mode is on, and OEM unlocking is enabled. Not sure where to go from here, any insight would be greatly appreciated!View attachment 5320891
Click to expand...
Click to collapse
I have the exact same problem.
OEM unlock is toggled ON in developer options.
I cannot get VolUP_VolDOWN + USB to computer to produce download mode so I can unlock my bootloader. All I get is the charging battery %.
Is there any solution to this?

bouyakasha said:
I have the exact same problem.
OEM unlock is toggled ON in developer options.
I cannot get VolUP_VolDOWN + USB to computer to produce download mode so I can unlock my bootloader. All I get is the charging battery %.
Is there any solution to this
Click to expand...
Click to collapse
Same issue tmoble is trying to tell me it automatically unlocked my boot when I Sim unlocked which I'm sure is not true it didn't wipe my data for one

Has anyone tried to use fastboot and use the commands?

Also afterwards, has anyone been able to fastboot boot <kernel_initd.img> to bootstrap over USB from PC?
rob420p said:
Has anyone tried to use fastboot and use the commands?
Click to expand...
Click to collapse

xdabookam said:
Also afterwards, has anyone been able to fastboot boot <kernel_initd.img> to bootstrap over USB from PC?
Click to expand...
Click to collapse
Exactly what I ment

rob420p said:
Has anyone tried to use fastboot and use the commands?
Click to expand...
Click to collapse
I did it just got stuck saying "entering fastboot mode..." In red at top of screen
I also had the same problem as crungtrusse but when i did vol up i got a download screen that i let sit for 15 min and nothing happened
crungtrusse said:
Hi, I'm new to all this and hopefully I'm just missing something obvious. When I put my A12 into Download Mode, I have no option for a volume-up long-press, as seen in attached photo. I have an A125U model if that information is at all relevant. Developer mode is on, and OEM unlocking is enabled. Not sure where to go from here, any insight would be greatly appreciated!View attachment 5320891
Click to expand...
Click to collapse

Goldensnipes said:
I did it just got stuck saying "entering fastboot mode..." In red at top of screen
I also had the same problem as crungtrusse but when i did vol up i got a download screen that i let sit for 15 min and nothing happened
Click to expand...
Click to collapse
You always get "entering fastboot mode..." when you see that screen you are in fastboot.

LAST_krypton said:
You always get "entering fastboot mode..." when you see that screen you are in fastboot.
Click to expand...
Click to collapse
I get no response from phone at that point it dosnt even say its connected to pc

Goldensnipes said:
I get no response from phone at that point it dosnt even say its connected to pc
Click to expand...
Click to collapse
Does that happend when in fastboot? If yes install the adb interface drivers and bootloader iterface drivers.

Looking for deblooted custom rom hmu gala12

TexasAtom said:
Looking for deblooted custom rom hmu gala12
Click to expand...
Click to collapse
Nims? Maybe or do you have the files I can work with that will work too

I am also looking for mcdvoice the same. Have you got any?

Related

[SOLVED] Really "bricked" Nexus S after bad update

So official ics update! i was happy! I restored a 2.3.6 backup with cwm and applyed the official zip. But on reboot.. nothing, zero splashscreens, not even google logo. Now if i press power button the screen turn on but it keeps blank and there are no vibrations.. if i release power button then the screen turns off..
Is my nexus s (i9023) in a known state?
Plz help me!
Edit: after some plug/unplug/push/detach ecc i got this nexus s connected to my pc: windows 7 says: "samsung sec s5pc110 test b/d"
i'm googling..
SOLVED!
Big huge thanks to Adam!
Follow his tips here http://forum.xda-developers.com/showpost.php?p=20382688&postcount=16
I had to use a standard linux box, ubuntu virtualizend on vmware fusion didn't work.
With Adam tool you can get both download and recovery mode depending on what hardkey you press (both vol or only vol up) during resurrection.
You are in download mode if search and home softkeys are on
You are in recovery mode if back and menu softkeys are on
You can try the way of recovery mode (with fastboot), for me (i9023) fastboot did not recognize the device.
Download mode solution
After resurrection you'll get a nice download mode (search and home button on and others off, not viceversa).
Now run a virtualized windows (or restart your pc if you have dualboot) and use odin to restore your device (bootloader radio system) to a stock rom like 2.3.3.
Why a virutalized windows or dual boot? Cause if you unplug the device you lose download mode.
Quick how to for odin:
You need samsung drivers installed
Files for european i9023 nexus s: http://www.multiupload.com/A6OP3TFN0I
Googling it seems that they are good also for i9020 amoled nexus s (i'm not responsable about that!)
I used odin v 1.83 (only this version worked for me) on windows. Order of files in odin:
- Bootloader > Bootloader_I9023XXKA3.tar.md5
- PDA > PDA_SOJU_GRI54_TMO_EUR_MR1_SIGNED.tar.md5
- PHONE > MODEM_I9023XXKB3_REV_00_CL912571_SIGNED.tar.md5
- CSC > DGS_I9023_EUR.tar
This doesn't solve all problems: at this step i can turn my device on only using a usb powered cable. You need to apply cwm and restore your backup.
So:
Enter recovery mode: plug usb cable (battery appears now!) push vol up and power on.
Apply cwm as usual:
fastboot flash recovery recovery-clockwork.img
Click to expand...
Click to collapse
and enter recovery mode using device interface.
Restore your backup and reboot. Wait for a long boot (need caching all your apps) and it's done!
cyberalex88 said:
So official ics update! i was happy! I restored a 2.3.6 backup with cwm and applyed the official zip. But on reboot.. nothing, zero splashscreens, not even google logo. Now if i press power button the screen turn on but it keeps blank and there are no vibrations.. if i release power button then the screen turns off..
Is my nexus s (i9023) in a known state?
Plz help me!
Click to expand...
Click to collapse
Can you boot into bootloader mode (hold down power + vol-up)?
jvanlew said:
Can you boot into bootloader mode (hold down power + vol-up)?
Click to expand...
Click to collapse
No i can't, screen turns on and off at the pressure of the power button but no way to enter bootloader or recovery mode..
Hey, same thing with me.
When I plug it into the computer, it comes up as SEC S5PC110 Test B/D.
fastboot can't see it, so i can't fastboot it into bootloader. Any help?
narcosis219 said:
Hey, same thing with me.
When I plug it into the computer, it comes up as SEC S5PC110 Test B/D.
fastboot can't see it, so i can't fastboot it into bootloader. Any help?
Click to expand...
Click to collapse
you also got this after ics official update?
try to pull the battery and power up again
cyberalex88 said:
you also got this after ics official update?
Click to expand...
Click to collapse
I downloaded it manually and upgraded.
Battery pull does nothing.
maybe this http://forum.xda-developers.com/showthread.php?t=1257434 could help us! i sent a pm to Adam, we'll see..
I got nexus firmware running on a captivate.. might just work on a nexus too
http://forum.xda-developers.com/showthread.php?t=1247962
I would like a nexus to work with. If someone wants to send me a device, I can locate UnBrickable mod and update my resurrector
The upgrade is only for T-Mobile Nexus S (I-9020T), nither I-9020A nor I-9023!
can you upgrade if you're running 2.3.6 I9020XXKF1
it is a tmo version
Same here. Installed from 2.3.6 and now it won't turn on.
Someone send me a device. Send me a pm. I have a recovery option and I can make your device UnBrickable.
AdamOutler said:
Someone send me a device. Send me a pm. I have a recovery option and I can make your device UnBrickable.
Click to expand...
Click to collapse
Yeap, bricked ones should do nicely.
He's a beast over at the Captivate forum guys.
AdamOutler said:
Someone send me a device. Send me a pm. I have a recovery option and I can make your device UnBrickable.
Click to expand...
Click to collapse
is it possible to post the recovery file here ?
Ibn Saeed said:
is it possible to post the recovery file here ?
Click to expand...
Click to collapse
I already did.. I sent the link.
However, I just finished rewriting the UnBrickable Resurrector for this device.
YOU MUST BE RUNNING A DEBIAN BASED LINUX.
Instructions:
Verify you are running the latest version of Java http://java.com/en/download/installed.jsp
Download UnBrickable Resurrector Revision 37
Right click the app and run with Java
Select "S5PC110 (Nexus S)" From the drop-down list in the app.
Plug in your device
Click resurrect.
Use fastboot to reload software
Let me know if it works
This worked on my Captivate which was in the same mode.
https://plus.google.com/u/0/104711040110222472212/posts/1WhTCszaL3M
{
"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"
}
I forgot to mention that you must hold the fastboot key combo
AdamOutler said:
I forgot to mention that you must hold the fastboot key combo
Click to expand...
Click to collapse
So can you provide which DEBIAN Version you use? I encountered the same issue with others.
I think I can install the linux on my laptop and have a try.
yqowen said:
So can you provide which DEBIAN Version you use? I encountered the same issue with others.
I think I can install the linux on my laptop and have a try.
Click to expand...
Click to collapse
I did!
Holy crap people. I don't post this **** for my health. Read my post above and stop sending me PMs.
Managed to get my Nexus S bricked a few hours ago with the ICS update, been spending hours trying to get it working again.
The resurrector has managed to get my device up and running to the Google logo and the padlock screen, now I just need to fix the rest!

[Help Wanted] [Bricked] Accidentally Flashed Factory Image for Pixel 4a (5G)

I mistakenly downloaded and attempted to flash the latest factory image for a Pixel 4 (5G) to my Pixel 4a.
My phone is now stuck on a black screen and I'm unable to boot into the bootloader so that I can flash the correct factory image.
I've tried all sorts of combinations of holding power + volume keys, but nothing seems to work.
The device does some to be on in some fashion as when I plug it into my computer windows alerts me that it's setting up a USB device.
{
"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"
}
Running adb devices and fastboot devices yields no results.
As such the flash-all script included with the factory image doesn't do anything.
I also tried using the "Android Flash Tool" https://flash.android.com/welcome provided by Google, but this also doesn't detect my device.
Are there any other steps I can take to unbrick my phone or is an RMA the only option.
Thanks
I think you're SOL. I did the same thing with my phone and had to send it back to google for a refurb.
AugusDogus said:
I mistakenly downloaded and attempted to flash the latest factory image for a Pixel 4 (5G) to my Pixel 4a.
My phone is now stuck on a black screen and I'm unable to boot into the bootloader so that I can flash the correct factory image.
I've tried all sorts of combinations of holding power + volume keys, but nothing seems to work.
The device does some to be on in some fashion as when I plug it into my computer windows alerts me that it's setting up a USB device.
View attachment 5150333
Running adb devices and fastboot devices yields no results.
As such the flash-all script included with the factory image doesn't do anything.
I also tried using the "Android Flash Tool" https://flash.android.com/welcome provided by Google, but this also doesn't detect my device.
Are there any other steps I can take to unbrick my phone or is an RMA the only option.
Thanks
Click to expand...
Click to collapse
Haha I did the same, don't worry .
I got out of this mess using Android flash tool,
When u plug in the phone hold the volume down button down .....
It might take a while, but it WILL detect the device.
When u pick the rom to flash , in the option to edit make sure to click on wipe , and force partitions.
Good luck
adb and fastboot drivers you must install . Unpack adb and fastboot files to installer , and after unpack tools you can run flashing . Other way don't exist.
AugusDogus said:
I mistakenly downloaded and attempted to flash the latest factory image for a Pixel 4 (5G) to my Pixel 4a.
My phone is now stuck on a black screen and I'm unable to boot into the bootloader so that I can flash the correct factory image.
I've tried all sorts of combinations of holding power + volume keys, but nothing seems to work.
The device does some to be on in some fashion as when I plug it into my computer windows alerts me that it's setting up a USB device.
View attachment 5150333
Running adb devices and fastboot devices yields no results.
As such the flash-all script included with the factory image doesn't do anything.
I also tried using the "Android Flash Tool" https://flash.android.com/welcome provided by Google, but this also doesn't detect my device.
Are there any other steps I can take to unbrick my phone or is an RMA the only option.
Thanks
Click to expand...
Click to collapse
Did you manage to fix this?
I flashing a 4a image to my 4a device and still got the black screen
greeneyez15o said:
Haha I did the same, don't worry .
I got out of this mess using Android flash tool,
When u plug in the phone hold the volume down button down .....
It might take a while, but it WILL detect the device.
When u pick the rom to flash , in the option to edit make sure to click on wipe , and force partitions.
Good luck
Click to expand...
Click to collapse
Are you supposed to have the phone on or off when you plug in the phone with Vol down button down?
But my phone has black screen... how do I tell if the phone is on or off.
Hold power button & volume down at the same time for fastboot screen.
crackerjack1957 said:
Hold power button & volume down at the same time for fastboot screen.
Click to expand...
Click to collapse
Tried that for over 60 seconds. doesn't work.
Problem is like OP the wrong factory image is flashed on the pixel 4a.
The screen just stays blank
greeneyez15o said:
Haha I did the same, don't worry .
I got out of this mess using Android flash tool,
When u plug in the phone hold the volume down button down .....
It might take a while, but it WILL detect the device.
When u pick the rom to flash , in the option to edit make sure to click on wipe , and force partitions.
Good luck
Click to expand...
Click to collapse
Hello,
Not working, the phone in QDL mode, and google flash web tool never detect the phone.
Is there anything to do, or I just through the phone away?
I have goohle 4a flash image 4a 5g.
Phone Going to EDL mode.
I Need mbn loder

How To Guide Install Stock ROM - Xiaoxin Pad Pro 2021 [TB-J716F]

How to install Stock ROM - Xiaoxin Pad Pro 2021 [TB-J716F]​
I tried installing a GSI-ROM on this tablet, which basically worked except for three/four bugs I coulnd't solve.
So I tried to restore the Stock ROM in the meantime and will share my experience.
Your data will be deleted, try it at your own risk.
Requirements:
Download Stock-ROM and unpack it
Download and install QFIL-Tool + Driver
PC with ADB-Tool
Installation:
Boot tablet in EDL-Mode, there are two ways (in EDL-Mode screen always remains off):
If tablet is fully booted: use adb command "adb reboot edl"
If tablet is off or can't be booted: press the volume up button and hold, plug the usb cable into the tablet and PC and wait a few seconds
Now this should appear in your device manager:
{
"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"
}
Start the QFIL-Programm, it should detect the port with the same name.
Go to "Configuration" -> "FireHose Configuration". At device type select "ufs" and tick "Reset After Download" then press ok:
Back in the main window select "Programmer Path" and browse to the ROM-Folder, select the file "prog_firehose_ddr.elf".
Select "Content XML" and browse to the ROM-Folder, select the file "contents.xml"
Click "Download Content" and wait, may take a few minutes
After its done, this status message should a appear and the tablet should reboot.
Done, Stock-ROM should boot now.
Thanks. And relock bootloader and Widevine L1?
Widevine is L3, probably because the bootloader is unlocked.
I haven't tried relocking the bootloader but according to the chinese ZUI website it's not possible to relock.
But you can try it and share you experience, try it with "fastboot oem lock" or "fastboot flashing lock".
HI, How could i use adb since my tab doesnt boot up? It is stucked at bootloop since I receive it from the store
Is your bootloader locked or unlocked? Did you already try to Wipe data/factory reset?
You could try this: https://forum.xda-developers.com/t/guide-how-to-reboot-to-edl-from-fastboot.3394292/
Tropaion said:
Is your bootloader locked or unlocked? Did you already try to Wipe data/factory reset?
You could try this: https://forum.xda-developers.com/t/guide-how-to-reboot-to-edl-from-fastboot.3394292/
Click to expand...
Click to collapse
It is unlocked but it doesnt even star at all.. only bootloop, i can't put it on bootloader mode or fastboot.. nothing
I can only think of one thing you can try to enter edl mode, which I recently read in an chinese forum.
1. turn off tablet
2 open qfil software
3. hold volume up button
4. plug in usb cable and connect tablet with your pc while holding the button pressed
5. let lose of volume up button
6. wait for about 2 sec., tablet should be in edl mode. qfil software should detect the tablet.
Tropaion said:
I can only think of one thing you can try to enter edl mode, which I recently read in an chinese forum.
1. turn off tablet
2 open qfil software
3. hold volume up button
4. plug in usb cable and connect tablet with your pc while holding the button pressed
5. let lose of volume up button
6. wait for about 2 sec., tablet should be in edl mode. qfil software should detect the tablet.
Click to expand...
Click to collapse
Didnt worked for me either I'll keep trying before return it to the seller..
did you try to relock bootloader then flash stock rom again ? will this method can bring back L1 DRM ?
luizkun said:
did you try to relock bootloader then flash stock rom again ? will this method can bring back L1 DRM ?
Click to expand...
Click to collapse
Didn't tried because my pc even recognize the tablet..
Somehow i managed to get QFIL to recognize the tablet but I'm getting this error..
ThiagoArecippo said:
Somehow i managed to get QFIL to recognize the tablet but I'm getting this error..
Click to expand...
Click to collapse
Which?
Tropaion said:
Which?
Click to expand...
Click to collapse
Hahaha was the sahara fail but I couldn't attach the image I couldn't managed to flash the rom and decided to return it to the seller.. I'm deciding if I get the chinese or global rom. I want widevine L1
Hi @Tropaion , I tried your steps but now the tablet it's stuck in boot. It keeps showing the boot animation, than after a while it stops and the screen turn off. Than nothing. I can still access recovery mode but I can't do anything from there, please help me.
@Cris74m What did the qfil status log say?
Tropaion said:
@Cris74m What did the qfil status log say?
Click to expand...
Click to collapse
it showed the same thing that you posted above (https://forum.xda-developers.com/attachments/qfil_2-png.5434149/), with the download succeed and everything.
Now I am only able to get the computer to recognize the device as this:
@Cris74m Does the non-animated or animated lenovo logo show up?
You can try to go to recovery and do an factory reset/wipe data.
Your device is TB-J716F not TB-J706F?
Tropaion said:
@Cris74m Does the non-animated or animated lenovo logo show up?
You can try to go to recovery and do an factory reset/wipe data
Click to expand...
Click to collapse
As the usual boot. It shows the Lenovo logo with the "powered by android" thing, than it shows the animated logo and after a while it gets stuck and than turn off the screen.
Already tried factory reset but nothing changed.
Somehow I was able to get the laptop to recognize the device and doing a new install using the firhose_lite version; now the device booted correctly, unfortunately it has no google services
@Cris74m How did you manage to get it to recognize it? Change driver?
Just download Google Play Store and install it manually.
BTW did buy your tablet with global ROM and wanted to go back to chinese?

Question Recovery mode OneUI 5

Hi. I try to boot the device to recovery mode but unable to enter recovery mode I'm sure I did the right way as per YouTube a description but still unable. did Samsung change the way to enter recovery mode?
It would be better if you mentioned what exactly you did rather than say you did it correctly. I hope you might knowing, now a days you needs to keep device connected to PC while reboot to recovery.
Power off device , then connect USB C cable to device. I connect my SanDisk SSD to the other end off the cable. It should work also with USB C stick.
Push volume up and power button and hold them till your device boots in recovery mode.
If you connect your device to a laptop ,it may start charging, making it more difficult to enter recovery mode.
brouwerchris said:
If you connect your device to a laptop ,it may start charging, making it more difficult to enter recovery mode.
Click to expand...
Click to collapse
In this case, don't power off but connect device to PC and reboot device (force reboot (keep holdingvol down +power) if you are in bootloop ) as soon screen goes blank, hold power + vol up and you will be in twrp
Go into Magisk.
{
"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"
}
dr.ketan said:
In this case, don't power off but connect device to PC and reboot device (force reboot (keep holdingvol down +power) if you are in bootloop ) as soon screen goes blank, hold power + vol up and you will be in twrp
Click to expand...
Click to collapse
I did the steps that you mentioned but unable to into recovery mode
pjaysnowden said:
Go into Magisk.View attachment 5750621
Click to expand...
Click to collapse
Thanks for response. I am not in root
DinarQ8 said:
I did the steps that you mentioned but unable to into recovery mode
Click to expand...
Click to collapse
Keep holding both button power + Vol up (it seems you holding only Vol up)
dr.ketan said:
Keep holding both button power + Vol up (it seems you holding only Vol up
Click to expand...
Click to collapse
Did i have do something in Developer Mode?
DinarQ8 said:
Did i have do something in Developer Mode?
Click to expand...
Click to collapse
For unlock bootloader - Yes, for reboot to recovery - No
For Unlock bootloader read Magisk Documentation for mor details
try ADB
DinarQ8 said:
Hi. I try to boot the device to recovery mode but unable to enter recovery mode I'm sure I did the right way as per YouTube a description but still unable. did Samsung change the way to enter recovery mode?
Click to expand...
Click to collapse
Still the same, simple operation on my SM-S980U1(Android12): turn off the phone, hold both vol+ and power until you see displayed 'Samsung' - let the power button go and after a few seconds(keep pressing vol+) you should see the recovery mode screen right away.
The problem was from the USB cable after changing the cable the device can boot normally to Recovery
Thanks for all I appreciate your responses
DinarQ8 said:
Thanks for response. I am not in root
Click to expand...
Click to collapse
Install Magisk anyway. You don't need to root. The options in my post will appear anyway.
dr.ketan said:
It would be better if you mentioned what exactly you did rather than say you did it correctly. I hope you might knowing, now a days you needs to keep device connected to PC while reboot to recovery.
Click to expand...
Click to collapse
My S22 Ultra (still on Android 12) does not require a USB cable to enter recovery. Just hold down volume up and power when turning on the phone.
celticchrys said:
My S22 Ultra (still on Android 12) does not require a USB cable to enter recovery. Just hold down volume up and power when turning on the phone.
Click to expand...
Click to collapse
I never heard it since A12 except, If you flash recovery/CSC OR If you select to reboot to recovery from adb/magisk/TWRP then it auto rboot to TWRP without connecting to PC
In rest of normal condition it does.
dr.ketan said:
I never heard it since A12 except, If you flash recovery/CSC OR If you select to reboot to recovery from adb/magisk/TWRP then it auto rboot to TWRP without connecting to PC
In rest of normal condition it does.
Click to expand...
Click to collapse
Perhaps it is only for people who have TWRP then? OR only Exynos? I have unrooted Snapdragon, and no USB cable is needed to get into recovery.
celticchrys said:
Perhaps it is only for people who have TWRP then? OR only Exynos? I have unrooted Snapdragon, and no USB cable is needed to get into recovery.
Click to expand...
Click to collapse
I don't think so
Which version you have?
Try rebooting to recovery from device booted on system just with combo key and check
dr.ketan said:
I don't think so
Which version you have?
Try rebooting to recovery from device booted on system just with combo key and check
Click to expand...
Click to collapse
I have a factory unlocked S 22 Ultra, model SM-908U1.
Did it yesterday with only using the volume UP button and the power button, in order to clear system cache. Did it again just now. Worked fine, just as it did on Note 10+ and on Note 8, etc.
Turn off phone.
Hold down volume UP button, then hold down power button at the same time.
When "Galaxy" appears (after Samsung), let go of power, but keep holding down volume UP.
After a few more seconds, recovery menu appears.
Phone is stock, purchased a this week. On October 1, 2022 Security patch.
May be it's only on "U" version

Custom binary (recovery) blocked by OEM

I wanted to install twrp on samsung a30s, after activating the OEM and usb debugging, I installed odin and twrp.tar for the A30s but it gives me an error which is present in the image I have attached.
{
"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"
}
gerryscottiano said:
I wanted to install twrp on samsung a30s, after activating the OEM and usb debugging, I installed odin and twrp.tar for the A30s but it gives me an error which is present in the image I have attached.View attachment 5931147
Click to expand...
Click to collapse
Enabling the OEM Unlocking toggle does NOT unlock the bootloader. It simply functions as a "safety" that allows you to, but you still have to unlock the bootloader through download mode.
If you reboot to download mode, do you see "OEM LOCK: ON"? This means the bootloader is still locked.
gerryscottiano said:
I wanted to install twrp on samsung a30s, after activating the OEM and usb debugging, I installed odin and twrp.tar for the A30s but it gives me an error which is present in the image I have attached.View attachment 5931147
Click to expand...
Click to collapse
V0latyle said:
Enabling the OEM Unlocking toggle does NOT unlock the bootloader. It simply functions as a "safety" that allows you to, but you still have to unlock the bootloader through download mode.
If you reboot to download mode, do you see "OEM LOCK: ON"? This means the bootloader is still locked.
Click to expand...
Click to collapse
no, I don't get oem lockn, if you want I'll send you a video of when it starts up
gerryscottiano said:
no, I don't get oem lockn, if you want I'll send you a video of when it starts up
Click to expand...
Click to collapse
A picture of the download mode screen would be fine.
V0latyle said:
A picture of the download mode screen would be fine.
Click to expand...
Click to collapse

			
				
Can you attach a picture? I can't see the text in the upper left
V0latyle said:
Can you attach a picture? I can't see the text in the upper left
Click to expand...
Click to collapse
Hmm, Samsung apparently has changed things with their newer devices
Boot into recovery, then select Reboot to bootloader and post the screen you see
V0latyle said:
Hmm, Samsung apparently has changed things with their newer devices
Boot into recovery, then select Reboot to bootloader and post the screen you see
Click to expand...
Click to collapse
In the screen I sent you I did the procedure you wrote
V0latyle said:
Hmm, Samsung apparently has changed things with their newer devices
Boot into recovery, then select Reboot to bootloader and post the screen you see
Click to expand...
Click to collapse
Yep. See OEM LOCK: ON? That means your bootloader is locked.
If you're ready to unlock your bootloader, follow these instructions. This will wipe your device.
Power device off completely and disconnect any cables
Have a USB cable plugged into your computer, do not plug it into your phone yet
Hold both Volume + and - buttons, do NOT press Power, and plug in the USB cable.
Device should start with this screen:
Let go of the Volume buttons, then hold Volume Up to select Device Unlock Mode.
The next screen will prompt you to confirm you want to unlock the bootloader. Press Volume Up to select Yes. Your device will restart and wipe all user data.
You aren't quite done yet. Allow the device to boot into the Android setup wizard. Skip through the wizard but make sure you connect to WiFi.
Once setup is complete, open Settings and enable Developer Options. Check to see if the OEM Unlocking toggle is visible.
If the toggle is visible and grayed out, you are clear to install custom firmware.
If the toggle is NOT visible, VaultKeeper is not yet disabled. Manually check for a firmware update in System settings, then check again to see if the OEM Unlocking toggle is visible.
Once OEM Unlocking is visible again, you may reboot to download mode and flash custom images. This will trip the Warranty Void counter, THIS IS PERMANENT.
V0latyle said:
Yep. See OEM LOCK: ON? That means your bootloader is locked.
If you're ready to unlock your bootloader, follow these instructions. This will wipe your device.
Power device off completely and disconnect any cables
Have a USB cable plugged into your computer, do not plug it into your phone yet
Hold both Volume + and - buttons, do NOT press Power, and plug in the USB cable.
Device should start with this screen:
View attachment 5932117
Let go of the Volume buttons, then hold Volume Up to select Device Unlock Mode.
The next screen will prompt you to confirm you want to unlock the bootloader. Press Volume Up to select Yes. Your device will restart and wipe all user data.
You aren't quite done yet. Allow the device to boot into the Android setup wizard. Skip through the wizard but make sure you connect to WiFi.
Once setup is complete, open Settings and enable Developer Options. Check to see if the OEM Unlocking toggle is visible.
If the toggle is visible and grayed out, you are clear to install custom firmware.
If the toggle is NOT visible, VaultKeeper is not yet disabled. Manually check for a firmware update in System settings, then check again to see if the OEM Unlocking toggle is visible.
Once OEM Unlocking is visible again, you may reboot to download mode and flash custom images. This will trip the Warranty Void counter, THIS IS
Click to expand...
Click to collapse
thank you so much for your support, everything worked out. I will thank you forever.
gerryscottiano said:
thank you so much for your support, everything worked out. I will thank you forever.
Click to expand...
Click to collapse
Glad to hear it. Good luck!
V0latyle said:
Glad to hear it. Good luck!
Click to expand...
Click to collapse
hi! I tried to flash the twrp but it gives me an error that is present in the image. Would you know how to fix it?
gerryscottiano said:
hi! I tried to flash the twrp but it gives me an error that is present in the image. Would you know how to fix it?
Click to expand...
Click to collapse
Unfortunately no. Ask for help in the TWRP thread.

Categories

Resources