Bootloader relock after Bootloader was unlocked? & Boot Warning Screen Removal?

Bootloader relock after Bootloader was unlocked? & Boot Warning Screen Removal? - Samsung Galaxy S10 Questions & Answers

Hi Guys,
So i rooted my S10 and got TWRP installed.
But for me it is still unclear, what to do about the first message, that appears when you restart your phone.
Here:
{
"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"
}
Any Way to remove that?
And also I hear from people they somehow relock their bootloader again.
Didn't understand this step for now or what the use of this was? Maybe someone explain please, so it is clear for everyone.
But when I try this > Start Phone in Recovery > Hold Volume Up to Device Lock Option > Lock the Bootloader & Factory Reset >
it just brings me here and after that it does nothing!
Here - see top left.
it says:
>
VBMETA: Error verifiing vbmeta Image: OK_NOT_SIGNED (3)
CUSTOM VBMETA
VBMETA: No sign Info
VBMETA ,
<
Question 1: Is there a Way to remove the Startscreen Warning?
Question 2: What is the use of relocking the bootloader and how is it properly possible?
Hope this Thread brings some clear view on this.

||||| said:
Hi Guys,
So i rooted my S10 and got TWRP installed.
But for me it is still unclear, what to do about the first message, that appears when you restart your phone.
Here:
Any Way to remove that?
And also I hear from people they somehow relock their bootloader again.
Didn't understand this step for now or what the use of this was? Maybe someone explain please, so it is clear for everyone.
But when I try this > Start Phone in Recovery > Hold Volume Up to Device Lock Option > Lock the Bootloader & Factory Reset >
it just brings me here and after that it does nothing!
Here - see top left.
it says:
>
VBMETA: Error verifiing vbmeta Image: OK_NOT_SIGNED (3)
CUSTOM VBMETA
VBMETA: No sign Info
VBMETA ,
<
Question 1: Is there a Way to remove the Startscreen Warning?
Question 2: What is the use of relocking the bootloader and how is it properly possible?
Hope this Thread brings some clear view on this.
Click to expand...
Click to collapse
This Download screen is waiting for you to connect to your computer and fire up Odin and flash stock firmware.
See my post here:
https://forum.xda-developers.com/ga...bootloader-t3927663/post79698366#post79698366

robbo1947 said:
This Download screen is waiting for you to connect to your computer and fire up Odin and flash stock firmware.
See my post here:
https://forum.xda-developers.com/ga...bootloader-t3927663/post79698366#post79698366
Click to expand...
Click to collapse
Thanks your post was very useful!
After I flashed stock firmware again - do I still have TWRP then?
Scenario 1. Your phone is rooted with Magisk.
Go into Developers options and check OEM options, the switch must be ON (to the right). If it isn't turn it ON.
Turn off your phone. Press and hold the Bixby and Volume-down button, then connect with USB to your computer. (The cable shouldn't be connected until after you press the buttons).
Within seconds of USB connection the Download screen will appear. You will see 3 optiions, choose and Long press volume up and hold button until you see the 2 options at bottom of screen. Choose and hold volume up until screen goes off. Then the S10 logo screen will briefly apppear, before it flicks back to the Download screen with the words 'VBMETA: Error verifying vbmeta image etc' at the top, as the image below.
This is all good so far. Leave the phone exactly as it is with this screen showing and make sure the phone is still connected to the computer.
On your computer, fire up Odin3_v3.13.1, you can leave the Reboot option in Odin ticked. Locate your firmware on your computer and put the 4 file parts (BL, AP. CP and CSC) into Odin.
Let Odin finish.
The phone will reboot ready for setup.
The Unlocked bootloader warning screen will be gone.
Click to expand...
Click to collapse
But why should we relock the bootloader in the first place?
Only so we don't have the bootscreen-warning anymore?
Or does it have some other purpose as well?
And I see what I was stuck at, I didn't flashed the stock firmware, but tried to flash the patched stock rom again.
Because the bootloader was locked, It stuck at the flashing process everytime. So thats basically why this thread was created to bring some clarity about this.

||||| said:
Thanks your post was very useful!
After I flashed stock firmware again - do I still have TWRP then?
But why should we relock the bootloader in the first place?
Only so we don't have the bootscreen-warning anymore?
Or does it have some other purpose as well?
And I see what I was stuck at, I didn't flashed the stock firmware, but tried to flash the patched stock rom again.
Because the bootloader was locked, It stuck at the flashing process everytime. So thats basically why this thread was created to bring some clarity about this.
Click to expand...
Click to collapse
To remove the warning screen and be rooted flash Soldier's Splash Screen Changer.

ExtremeGrief said:
To remove the warning screen and be rooted flash Soldier's Splash Screen Changer.
Click to expand...
Click to collapse
Great Tip! Thanks
Soldier's Splash Screen Changer

re-lock Samsung S20 OEM after flashing
For those who may still be interested in knowing the EASY way of doing this:
This is what i did for the S20 (snapdragon)
After flashing stock firmware, the bootloader (OEM) stays unlocked, meaning that things like GooglePay and some bank apps wont work. The way to fix this is by re-locking the oem after you have flashed your new stock rom. Here are the steps to do that (since it took me a while to figure out and there is hardly any info online) - bear in mind this works if you have NOT tripped Knox and its using a stock rom and do these steps at your own risk - always have a backup just in case:
How to re-lock bootloader (for S20):
1. Turn off your device.
2. Press Volume down + volume up and insert usb cable to your phone to start the download mode
3. Read the text below on the Download Mode screen
to block or unblock the Bootloader.
4.- Long press the vol (+) button to enter unlock mode.
LOCK BOOTLOADER SCREEN:
5. Read the 2 options available, one will say to lock the lock the bootloader, the other to lock. Press the relevant volume button (was down on mine) until the phone restarts (this will erase your data and restart automatically).
6. Go into developer mode and then uncheck the unlocked oem option, restart your phone.
That's it! Now you have a device with an OEM locked, so everything will work as expected, again, as long as its a stock rom and you have NOT tripped Knox by root etc.

Hello,
Can you tell me how did you escape the downloading window (after you tried to re-lock the bootloader). Mine seems to have stuck and I tried to long press Vol Down and Power button, but the phone reboots and comes to this screen again.
I also tried to flash a few rom, but everytime it was blocked by OEM lock. I am not sure what was the CSC of the phone (as I bought it from someone who is now not in my contact). Is there any way I can find the stock rom with limited information?
My phone is Samsung SM-G977B (5G). I just know that it is a european version.
Any ideas?

masrhad said:
Hello,
Can you tell me how did you escape the downloading window (after you tried to re-lock the bootloader). Mine seems to have stuck and I tried to long press Vol Down and Power button, but the phone reboots and comes to this screen again.
I also tried to flash a few rom, but everytime it was blocked by OEM lock. I am not sure what was the CSC of the phone (as I bought it from someone who is now not in my contact). Is there any way I can find the stock rom with limited information?
My phone is Samsung SM-G977B (5G). I just know that it is a european version.
Any ideas?
Click to expand...
Click to collapse
See my post here:
https://forum.xda-developers.com/ga...bootloader-t3927663/post79698366#post79698366

Related

unlock the bootloader (Unofficial free way)

While searching for a way to unlock the bootloader i found a way
Hello. Instructions for unlocking the bootloader.
-------------- Responsibility for your bricks I do not take over. Everyone does at their own peril and risk .--------------
Downloa ( Google)
1) Install the driver for the phone (in the header);
2) Install a special driver, find it in the Unlock_BootLoader \ Driver for Winwos \ DriverSetup.exe folder;
3) It is necessary to unwind the phone, remove the cover;
4) It is necessary to disconnect the battery;
5) It is necessary to close the contacts (Photo);
6) Connect the phone to the PC;
7) Open the program Unlock_BootLoader.exe, there is a menu at the top, the item: "Operations> Settings> You need to select the Unlock_BootLoader.xml file"
8) After selecting the Unlock_BootLoader.xml file, click "Operations" again and click Start. Or press the green play button.
9) Done. Now you have TWRP_Mod installed in the Recovery section.
Additionally
The method works both with a locked bootloader and an unlocked bootloader. The only difference is that how to use this program at the moment when the bootloader is unlocked, then you do not need to disassemble the phone and put it into TEST POINT mode.
If the bootloader loader, then the program flashes TWRP_Mod.img to the Recovery section. After flashing, the phone will automatically reboot and the bootloader will remain locked. But TWRP_Mod.img will work. If you need a full unlocking of the bootloader, then you need to prepare several other files. There was no time for that. I made the method only for flashing custom recovery.
In the video, my bootloader is unlocked. I had a chance to block the bootloader and delete all data, so I made a video with the unlocked bootloader.
With a locked bootloader, exactly the same thing, the only difference is that you will need to switch the phone to TEST POINT modeYoutube video
All thanks Goes for SergeySan27 for his work...
this made for 4pda and i am just sharing his work

This is 100% not working. Pls dont waste your effort

Wow

Specific what version of Pie do you have on Honor Play?

can u also tell if we have a method by which we can unlock our bootloader. If its possible using this technique then we can have development for our device. More people will be available to use the roms.

Excuse me, sir. Where is the TEST POINT?

Up for this...

Up for this...

Cor-L29 firmware 9.0.0.184 Not working....

PM me plz, need you to change my configue xml

Test Point or EDL Mode requires physically opening the phone
nuteyha said:
Up for this...
Click to expand...
Click to collapse
I know lot of people already know but for everyone else's clarification Test Point or EDL Mode requires physically opening the phone and shorting 2 electric points together something like the following video.
https://www.youtube.com/watch?v=W8salW6m-z8
I do not know exactly where those 2 point are on honor play.
But one good thing is opening honor play is comparatively easy as it does not require heating the screen with some heatgun. There are 2 special screws and then the screen is clasped.

Cor-L29 firmware 9.0.0.184 (SP53C636) Not working....

Tried on Huawei P20 EML-L29
Hello,
I have tried this method on my Huawei P20 EML-L29.
{
"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"
}
the IDT started to flash the image and I got the successful PASS green message in the end.
The bootloader is temporary unlocked in testpoint mode
however, even if I have kept the VOL UP button pressed and removed the usb cable to reboot directly in the recovery mode (to prevent the overwrite with the default eRecovery) it still brings me to the default eRecovery menu.
I have even tried to flash TWRP manually in fastboot (using the tespoint mode to temporary unlock the bootloader) and I got the img file sent and written.
However, it still brings me to the default eRecovery.
Do I do something wrong or miss something? becase flashing of any image is successful but I can't get anything changed on the phone (just getting OKAY or success messages on the pc)

For everyone here trying by opening up the phone, make sure you DON'T touch any other 2 points or your motherboard will short-circuit and become unusable.

sorinbotirla said:
Hello,
I have tried this method on my Huawei P20 EML-L29.
the IDT started to flash the image and I got the successful PASS green message in the end.
The bootloader is temporary unlocked in testpoint mode
however, even if I have kept the VOL UP button pressed and removed the usb cable to reboot directly in the recovery mode (to prevent the overwrite with the default eRecovery) it still brings me to the default eRecovery menu.
I have even tried to flash TWRP manually in fastboot (using the tespoint mode to temporary unlock the bootloader) and I got the img file sent and written.
However, it still brings me to the default eRecovery.
Do I do something wrong or miss something? becase flashing of any image is successful but I can't get anything changed on the phone (just getting OKAY or success messages on the pc)
Click to expand...
Click to collapse
Did you try going to recovery through command line?
Code:
fastboot reboot recovery
(or reboot-recovery)
Sent from my COR-L29 using Tapatalk

Why would people have to take this tedious route to unlock their Huawei or Honor smartphones? Huawei as a company should listen and release bootloader to those who wish to unlock their system. They can put in place an agreement to be accepted by those who want to unlock their phones and expected no warranty after doing so. This is very simple to do.

Can someone confirm test point connectors on the play please?
Doesn't look too difficult imho.

https://4pda.ru/forum/index.php?showtopic=932709
Original thread ?

nuteyha said:
Cor-L29 firmware 9.0.0.184 (SP53C636) Not working....
Click to expand...
Click to collapse
Did you try this then and didn't work??

Does/can this work with Honor View 10?

I tried it with EML-L29C432, program showed me OK, but I still have stock recovery... Any idea?

[RECOVERY] TWRP 3.3.1 Lenovo Z6 Pro

DISCLAIMER
As usual, you do anything described in this post at your own risk. No one but you is responsible for any data loss, bricking or damage of your device.
INSTALLATION:
Pre-Requirements
ADB means Android Debug Bridge, and it is software that you should always do have installed on your PC.
Pre-Requisite 1
Make sure that you have the drivers for your phone installed on your PC.
If not, you can download and install them from here
Pre-Requisite 2
You must also install: Minimal ADB & Fastboot, you can download the software
from here
Pre-Requisite 3
Your device needs this with unlocked bootloader
Pre-Requisite 4
Make sure you have enabled 'USB Debugging' and OEM Unlocking on your device
Settings -> Advanced settings -> Developer Options
PAY ATTENTION: If you do not see the Developer Options menu you need to do this:
Settings -> Device Info -> tap 6 or 7 times on the 'ZUI version' entry
A pop-up should appear, telling you 'now you are a developer'
And now, how to install:
1.Reboot phone to Fastboot mode (via adb -type adb reboot bootloader)
2.Download patched vbmeta and TWRP recovery
3.Extract it to folder with minimal adb and fastboot
4.Open cmd in this folder and type fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
5.Then type fastboot reboot bootloader
6.Type fastboot flash recovery twrp_3.3.1_decrypt_works_by_alexeei.img
7.Press volume - and select Reboot recovery, then press power button
8.Enjoy
What worked:
All functions (may be if not, please say). Also TWRP now see exFAT microsd.
Thanks wzsx150 for it's TWRP for Lenovo Z5 Pro GT, some decrypt stuff taken from it.

This is f*cking awesome. Thank you for your efforts. Will install asap and bring some feedback.

Is it working ? Any custom roms then ?

Please provide custom ROM the official ROM is no less than terrible and bad.

Finally compiled TWRP with decryption support, added in first post

hammad5507 said:
Please provide custom ROM the official ROM is no less than terrible and bad.
Click to expand...
Click to collapse
There are some "globalised" china roms which are doing a decent job (with notifications sound fixed, chinese bloatware removed and google services installed), I recommend the one made by Francko76.
Also you can try all the treble stuff out there. I only tried two GSIs so far and I went back to Francko´s build.
Anyway I´m like you looking forward z6 pro dedicated custom roms.

descarao81 said:
I recommend the one made by Francko76.
Click to expand...
Click to collapse
Can you share a link to the Roms you mentioned ?
thanks

descarao81 said:
There are some "globalised" china roms which are doing a decent job (with notifications sound fixed, chinese bloatware removed and google services installed), I recommend the one made by Francko76.
Also you can try all the treble stuff out there. I only tried two GSIs so far and I went back to Francko´s build.
Anyway I´m like you looking forward z6 pro dedicated custom roms.
Click to expand...
Click to collapse
benjieb said:
Can you share a link to the Roms you mentioned ?
thanks
Click to expand...
Click to collapse
what rom is Francko´s build? if you have a link, can you share it please?

Sorry to ask, is this vbmeta patched only for this device or can i installed in others device ?

Please share the links
Please share links for the Franko's build.
and also is there any custom pie rom available??
Pls share if any.. I am very unsatisfied with the global rom. Pls help.

@alexei sir, can you make custom kernel or give way to our devices gets exfat support ?

this is twrp for Lenovo Z6 (not pro) ?

geepnozeex said:
this is twrp for Lenovo Z6 (not pro) ?
Click to expand...
Click to collapse
No this is Twrp for Z6 Pro ( L78051 )

Very tempted to get this phone... has anyone try with phh’s GSI? Does under screen scanner works?

alexeei said:
DISCLAIMER
As usual, you do anything described in this post at your own risk. No one but you is responsible for any data loss, bricking or damage of your device.
INSTALLATION:
Pre-Requirements
ADB means Android Debug Bridge, and it is software that you should always do have installed on your PC.
Pre-Requisite 1
Make sure that you have the drivers for your phone installed on your PC.
If not, you can download and install them from here
Pre-Requisite 2
You must also install: Minimal ADB & Fastboot, you can download the software
from here
Pre-Requisite 3
Your device needs this with unlocked bootloader
Pre-Requisite 4
Make sure you have enabled 'USB Debugging' and OEM Unlocking on your device
Settings -> Advanced settings -> Developer Options
PAY ATTENTION: If you do not see the Developer Options menu you need to do this:
Settings -> Device Info -> tap 6 or 7 times on the 'ZUI version' entry
A pop-up should appear, telling you 'now you are a developer'
And now, how to install:
1.Reboot phone to Fastboot mode (via adb -type adb reboot bootloader)
2.Download patched vbmeta and TWRP recovery
3.Extract it to folder with minimal adb and fastboot
4.Open cmd in this folder and type fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
5.Then type fastboot reboot bootloader
6.Type fastboot flash recovery twrp_3.3.1_decrypt_works_by_alexeei.img
7.Press volume - and select Reboot recovery, then press power button
8.Enjoy
What worked:
All functions (may be if not, please say). Also TWRP now see exFAT microsd.
Thanks wzsx150 for it's TWRP for Lenovo Z5 Pro GT, some decrypt stuff taken from it.
Click to expand...
Click to collapse
At step 4 I'm getting "fastboot: unknown option -- disable-verity"
Any idea?
Thanks

threeeye said:
At step 4 I'm getting "fastboot: unknown option -- disable-verity"
Any idea?
Thanks
Click to expand...
Click to collapse
NVM, just updated the adb tools and now everything is good

Restore stock bootloader?
Hello, I recently went through the whole process of unlocking bootloader, installing TWRP recovery and flashing ROM, and I am at version 11.0.350 ST ROW currently.
The ROM works fine, but now at every boot I am greeted by the "The boot loader is unlocked and software integrity cannot be guaranteed. <snip> Press power button to pause boot/continue" notice.
According to google, it's apparently a result of the bootloader unlocking process.
I tried to lock the bootloader again using "fastboot flashing lock", but then the phone stopped booting normally. It got stuck at the boot logo (which I believe means bricked?).
It wouldn't work until I unlocked bootloader and reflash the ROM.
So what I want to ask is, is it possible at this time to restore the bootloader to stock to avoid that "boot loader unlocked" notice and possibly become eligible for warranty again?

kagoromo said:
Hello, I recently went through the whole process of unlocking bootloader, installing TWRP recovery and flashing ROM, and I am at version 11.0.350 ST ROW currently.
The ROM works fine, but now at every boot I am greeted by the "The boot loader is unlocked and software integrity cannot be guaranteed. <snip> Press power button to pause boot/continue" notice.
According to google, it's apparently a result of the bootloader unlocking process.
I tried to lock the bootloader again using "fastboot flashing lock", but then the phone stopped booting normally. It got stuck at the boot logo (which I believe means bricked?).
It wouldn't work until I unlocked bootloader and reflash the ROM.
So what I want to ask is, is it possible at this time to restore the bootloader to stock to avoid that "boot loader unlocked" notice and possibly become eligible for warranty again?
Click to expand...
Click to collapse
Share screenshot, I think this normal boot step when BL is unlocked on lenovo / Zuk phones.

benjieb said:
Share screenshot, I think this normal boot step when BL is unlocked on lenovo / Zuk phones.
Click to expand...
Click to collapse
Here is the "The boot loader is unlocked..." screen:
{
"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"
}
And here's the boot loader:

kagoromo said:
Hello, I recently went through the whole process of unlocking bootloader, installing TWRP recovery and flashing ROM, and I am at version 11.0.350 ST ROW currently.
The ROM works fine, but now at every boot I am greeted by the "The boot loader is unlocked and software integrity cannot be guaranteed. <snip> Press power button to pause boot/continue" notice.
According to google, it's apparently a result of the bootloader unlocking process.
I tried to lock the bootloader again using "fastboot flashing lock", but then the phone stopped booting normally. It got stuck at the boot logo (which I believe means bricked?).
It wouldn't work until I unlocked bootloader and reflash the ROM.
So what I want to ask is, is it possible at this time to restore the bootloader to stock to avoid that "boot loader unlocked" notice and possibly become eligible for warranty again?
Click to expand...
Click to collapse
Do you try flash qfil rom after lock bootloader?

Mi A2 - Failed to boot - after system update

Hello everyone, yesterday morning, Sunday 12/15/19, the system message "restart the device to make the system update effective".
So I do as I have always been.
The phone, an Mi A2, goes into bootloop and then a white screen appears on a black background with the title:
"<!> Failed to boot"
"Press the Volume keys to select then the Power button to continue.
RETRY
POWER OFF "
Choosing "RETRY" verifies bootloop 3 or 4 times and then the recovery mode screen appears which says:
"Can't Load Android system. Your data may be corrupted. You should get the message you need to perform at factory data reset and erase all user data stored on this device."
It gives me the choice between:
-Try again
-Factory data reset
Choosing "Try again" returns the same routine as when "RETRY" is selected In the previous black background screen, bootloop and then the black background white screen described at the beginning.
I MUST ACCESS AND SAVE THE VERY IMPORTANT CONTENT. :crying:
I have all the photos and videos of my newborn daughter. I usually backup but this inconvenience suddenly caught me.
I surfed and I saw that many people found this problem after an update .. but I never found any solutions. I called the Xiaomi center in Novara indicated by the site but they told me that they only serve as a collection center to send to the assistance in the company Xiaomi, saying that the assistance resets the phone to restore its functioning and does not save the data. I tried to start the fastboot, the device is recognized by the PC and shows the locked bootloader. The program MiFlash asks me to start to install a set of drivers and then immediately generate an unhandled exception and crash.
Attached the images.
Can you help me? I do not know what to do..
{
"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"
}

You should try to use adb in recovery, if it works, you could digit "adb pull /sdcard".

Continue rebooting with external power on. Android One with A/B slots is supposed to reboot into previously (before OTA) active slot.

Aerobatic said:
Continue rebooting with external power on. Android One with A/B slots is supposed to reboot into previously (before OTA) active slot.
Click to expand...
Click to collapse
Thank you, can you explain me better what I should try to do?

HTCDevil said:
You should try to use adb in recovery, if it works, you could digit "adb pull /sdcard".
Click to expand...
Click to collapse
Is there any guide to do that?

pedrix82 said:
Is there any guide to do that?
Click to expand...
Click to collapse
I don't think so, when you are in recovery you should try to verify if your device is connected with "adb devices" and then you should use the command "adb pull /sdcard". But it usually works with custom recoveries, and if you have prevently enabled usb debugging.

pedrix82 said:
Thank you, can you explain me better what I should try to do?
Click to expand...
Click to collapse
First you can try to search this forum and read dozens of discussions of the same issue. Meanwhile you can plug in power adapter and reboot several times with pauses, probably sometimes switching to stock recovery and to fastboot mode, and then leave phone powered for a night.

HTCDevil said:
I don't think so, when you are in recovery you should try to verify if your device is connected with "adb devices" and then you should use the command "adb pull /sdcard". But it usually works with custom recoveries, and if you have prevently enabled usb debugging.
Click to expand...
Click to collapse
Thanks....I will try, I don't remember if I enabled the usb debugging mode, for sure I saw with fastboot that I have the bootloader Locked.

nothing to do...i tried ADB mode, but it is not enabled, only fastboot mode where i can do nothing because the bootloader is locked.
I also tried to install the Xiaomi tool, but it doesnt recognize the device.
i dont know what to do....

Did you try the factory data reset?

1N4148 said:
Did you try the factory data reset?
Click to expand...
Click to collapse
Hello...ehm...not, the aim is to recover all the data, photos and documents that are stored inside...

Same thing happened to me. You should manually switch the active partition in fastboot.

Zedsdeadbaby said:
Same thing happened to me. You should manually switch the active partition in fastboot.
Click to expand...
Click to collapse
Hi, I already tried to do what you suggest, but it is not possible with the bootloader Locked.
Anyway, can you tell me what I have to do to change the active partition? Maybe I don't do it as I should....

@pedrix82: I can only repeat, though you do not read and trust:
- the only (legal*) way to save data in bootloop with locked device is to boot;
- all other options are blocked for a locked Mi A2, - resetting, unlocking, etc. will erase user data; switching Slots and/or loading TWRP need unlocked phone; stock recovery is useless;
- Android One partitions system with A/B Slots was specifically designed to solve problems of failed OTAs, see https://source.android.com/devices/tech/ota/ab and https://android.googlesource.com/pl...ware/+/master/include/hardware/boot_control.h
Which means that: if you have bootloop after OTA on full stock (and have not tampered device yourself), after numerous attempts to boot -> the bootloader MUST detect that active Slot does not have bootable OS and MUST switch to the other Slot.
(non-legal*) - or read memory chip content at low-level and decipher encrypted data.

Aerobatic said:
@pedrix82: I can only repeat, though you do not read and trust:
- the only (legal*) way to save data in bootloop with locked device is to boot;
- all other options are blocked for a locked Mi A2, - resetting, unlocking, etc. will erase user data; switching Slots and/or loading TWRP need unlocked phone; stock recovery is useless;
- Android One partitions system with A/B Slots was specifically designed to solve problems of failed OTAs, see https://source.android.com/devices/tech/ota/ab and https://android.googlesource.com/pl...ware/+/master/include/hardware/boot_control.h
Which means that: if you have bootloop after OTA on full stock (and have not tampered device yourself), after numerous attempts to boot -> the bootloader MUST detect that active Slot does not have bootable OS and MUST switch to the other Slot.
(non-legal*) - or read memory chip content at low-level and decipher encrypted data.
Click to expand...
Click to collapse
Thanks,
It's really long time that I'm rebooting the mobile since it happened...
But cyclically and alternate I got the two image attached to the main post....

try a "fastboot continue" in adb

hello everyone, update.
unfortunately I was unable to recover anything and proceeded with the factory reset.
The phone has reset and everything is working.
So I thought to try to do a file recovery as you do for deleted files.
for the various recovery applications I need to root the device.
For this phone should be really simple but I'm still stuck in.
I followed one guide, then another, and then another .... all with the same procedures.
the result is that twrp recovery, if loaded with Vol + and pwr button hangs on the custom recovery logo.
I can only start the twrp recovery installed in the secondary partition of the phone.
but from this recovery, even if I install Magisk, with a successful results from the recovery, I do not root the device. I verified root with Magisk manager and rootchecker.
Help.... thanks

pedrix82 said:
... So I thought to try to do a file recovery as you do for deleted files.
Click to expand...
Click to collapse
I do no believe you'll be able to undelete files after factory reset.
pedrix82 said:
... for the various recovery applications I need to root the device. ... I followed one guide, then another, and then another .... all with the same procedures.
Click to expand...
Click to collapse
This guide works for everybody, except that
(1) there is obsolete "fastboot oem unlock" command stated which should better be changed to "fastboot flashing unlock", and
(2) guide does not mention that each unlock step is to be approved on phone, and
(3) guide skips step of patching stock boot.img in phone with MagiskManager, - while exactly this step creates archived copy of stock boot image in /data root, thus allowing to restore images (actually restoring stock boot image) before downloading next OTA, and
(4) only 1st variant - that is booting into patched boot image and then making "Direct Install" is safe - it allows to check that patched boot image is suitable for ROM.
pedrix82 said:
...the result is that twrp recovery, if loaded with Vol + and pwr button hangs on the custom recovery logo.
I can only start the twrp recovery installed in the secondary partition of the phone....
Click to expand...
Click to collapse
IMHO that just means that you did not do your homework (I mean you have not read guides and discussions and Google info with links I provided) well enough to understand that with A/B slots partitions structure there is no separate /recovery partition in phone (instead, recovery is embedded into /boot image), and thus we cannot just "flash TWRP" into MiA2.
Instead, TWRP can only be embedded into boot image (patching previously flashed suitable boot image), which is made by installing TWRP.zip in temporarily booted TWRP.img. Thus, if you want to have both root and permanent TWRP (I still do not see why anybody needs permanent TWRP with rooted stock), first get root with patched boot image, and then install TWRP patching this Magisk-patched boot image once more.
And I do think that "TWRP 4pda edition" is working better than so called "official TWRP".

Found the solution,
First u need to get to the recovery menu by pressing vol up + power, tap it multiple times after retry boot...you have to be quick...and eventually will get to the android robot pic with "no command"....keep pressing till you get to the full recovery menu. (this might take multiple tries)
Then go to update using adb. (you need all the files for adb, usb drivers, latest mi a2 update zip, you can find tutorials in youtube/google )
after updating it should boot up fine with all data intact.
If latest update versions dont boot, try repeating will older version.
Make sure you backup everthing afterwards! and enable oem unlocking &usb debugging for potential future issues.
Hope this helps!

Recover your X01AD using EDL mode and QFIL.

IT WILL ERASE ALL DATA ON YOUR PHONEAND KEEP YOUR BOOTLOADER UNLOCKED.YOUR WARRANTY WILL BE VOID AFTER IT.DO IT AT YOUR OWN RISK. DO IT CAREFULLY.(It won't erase your SD card, but I still recommend you remove SD card before it)Please read this thread carefully at least once before you modify your phone.
This thread is in order to give your X01AD a new life when it hard bricked.
First, Prepare the things you need :
-A Computer
Windows (10 is better) Platform. Tell me if you need Linux version.
-QPST
Download the file below. QPST included QFIL.
-Firmware
Download from here(vnrom.net). (find version "15.2016.1902.159" under ZB633KL)
-Unofficial unlock tool (Maybe you need)
Download from here(other thread). (download unlock.zip)
(Perhaps you don't need below stuffs, see note.)
-A flat screwdriver or anything can pry the backcover of your phone.
Download from reality
-A slice of paper
It is for separate battery cable and port.
-A USB Cable that have good quality.
The better the better.
Second, install QPST and Qualcomm USB driver, and then reboot.
Third, launch QFIL, choose "Flat Build",click "Configuration">"FireHose Configuration"
{
"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"
}
and set up like this:
click "OK" after you completed setting,
Next, Click "Browse...", navigate to the folder you unzip the firmware, select 'prog_emmc_firehose_8953_ddr.mbn'.
DON'T SELECT "validated_..." ONE, IT WILL LET FLASH FAIL.
Click "Load XML...", select 'rawprogram_unsparse.xml' in first window, select 'patch0.xml' in second window.
DON'T CLOSE WINDOW!
Fourth, enter EDL mode, try note1 first.
pry the back-cover of your phone.
Be careful, don't hurt your hand or screen, look carefully.
Remove battery cable cover, remove battery cable, put the paper between cable and port.
Next, connect your phone and computer.
Fifth, click "Select Port...", select 'Qualcomm......Port', click "OK".
Your "Download" button should available now. Click it.
And your phone will reboot automatically after flash completed.
Finally, your phone will boot into stock android 8 .
And if you get RED error, reboot into fastboot, run unofficial unlock. It should be resolve after that.
(Real relock bootloader method not found yet , it will get RED state after you lock the bootloader)
Note:
1 If you want enter EDL mode, "maybe" you can press VolUp+VolDown+Powerkey when power is off,
screen will be blank after a few seconds, and screen will not display anything during EDL mode.
Connect phone and computer to see whether QFIL detected device.
Long press Powerkey to exit EDL mode.
2 Serial number(string) will be erase, please follow this thread to recover that.

I tried but after rebooting I'm facing EIO warning after unlocking it did gone but I want to lock the Bootloader

Techgaming432 said:
I tried but after rebooting I'm facing EIO warning after unlocking it did gone but I want to lock the Bootloader
Click to expand...
Click to collapse
Is there blank screen after EIO warning?

dascrystal said:
Is there blank screen after EIO warning?
Click to expand...
Click to collapse
After EIO warning it goes to Asus splash screen then again EIO then again splash it loops
But
If i unlock the bootloader then the EIO state disappears

Techgaming432 said:
After EIO warning it goes to Asus splash screen then again EIO then again splash it loops
But
If i unlock the bootloader then the EIO state disappears
Click to expand...
Click to collapse
Sorry, I still can't find a method that can relock the bootloader,
but I think if anyone have a locked or not unlocked X01AD,
we maybe can pull the file in it (boot, persist, dtbo, etc.), that maybe can help.
By the way, I want to learn how to port or create a device specific rom, if you know any tutorial resource, tell me please.

dascrystal said:
Sorry, I still can't find a method that can relock the bootloader,
but I think if anyone have a locked or not unlocked X01AD,
we maybe can pull the file in it (boot, persist, dtbo, etc.), that maybe can help.
By the way, I want to learn how to port or create a device specific rom, if you know any tutorial resource, tell me please.
Click to expand...
Click to collapse
Join our official TG group so I can explain all these things

Techgaming432 said:
Join our official TG group so I can explain all these things
Click to expand...
Click to collapse
Where is the link?

dascrystal said:
Where is the link?
Click to expand...
Click to collapse
Search our device name in tg
Here I can't send link due to rules of XDA

Techgaming432 said:
Search our device name in tg
Here I can't send link due to rules of XDA
Click to expand...
Click to collapse
Is that ASUS Max M2 | X01AD | OFFICAL ?

Yes
dascrystal said:
Is that ASUS Max M2 | X01AD | OFFICAL ?
Click to expand...
Click to collapse
tag me there my name is @subhendu_mk

When i try to select the Programmer in Firmware folder, there is no file recognized as useful. Its empty from the QFIL point of view

Error Sahara protocol
Main 320: Uploading Image using Sahara protocol failed
Failed to open the device 1 slot 0 partition 0

It's all well explained, but firehose fail is a problem.

(X01AD) Valid Relocker for Bootloader
(X01AD) Valid Relocker for Bootloader
Dear forum users, I am glad to present you several guaranteed ways to lock the bootloader on Asus Zenfone Max M2 (ZB633KL, X01AD). This completely solves the "Red State" problem, allows you to return to stock with a successful SafetyNet...
forum.xda-developers.com
This is the method for "Real relocking", although I haven't tested yet, but someone said it works.

dascrystal said:
IT WILL ERASE ALL DATA ON YOUR PHONEAND KEEP YOUR BOOTLOADER UNLOCKED.YOUR WARRANTY WILL BE VOID AFTER IT.DO IT AT YOUR OWN RISK. DO IT CAREFULLY.(It won't erase your SD card, but I still recommend you remove SD card before it)Please read this thread carefully at least once before you modify your phone.
This thread is in order to give your X01AD a new life when it hard bricked.
First, Prepare the things you need :
-A Computer
Windows (10 is better) Platform. Tell me if you need Linux version.
-QPST
Download the file below. QPST included QFIL.
-Firmware
Download from here(vnrom.net). (find version "15.2016.1902.159" under ZB633KL)
-Unofficial unlock tool (Maybe you need)
Download from here(other thread). (download unlock.zip)
(Perhaps you don't need below stuffs, see note.)
-A flat screwdriver or anything can pry the backcover of your phone.
Download from reality
-A slice of paper
It is for separate battery cable and port.
-A USB Cable that have good quality.
The better the better.
Second, install QPST and Qualcomm USB driver, and then reboot.
Third, launch QFIL, choose "Flat Build",click "Configuration">"FireHose Configuration"
View attachment 5355831
and set up like this:
View attachment 5355701
click "OK" after you completed setting,
Next, Click "Browse...", navigate to the folder you unzip the firmware, select 'prog_emmc_firehose_8953_ddr.mbn'.
View attachment 5355697DON'T SELECT "validated_..." ONE, IT WILL LET FLASH FAIL.
Click "Load XML...", select 'rawprogram_unsparse.xml' in first window, select 'patch0.xml' in second window.View attachment 5355705
DON'T CLOSE WINDOW!
Fourth, enter EDL mode, try note1 first.
pry the back-cover of your phone.
Be careful, don't hurt your hand or screen, look carefully.
Remove battery cable cover, remove battery cable, put the paper between cable and port.
Next, connect your phone and computer.
Fifth, click "Select Port...", select 'Qualcomm......Port', click "OK".
Your "Download" button should available now. Click it.
And your phone will reboot automatically after flash completed.
Finally, your phone will boot into stock android 8 .
And if you get RED error, reboot into fastboot, run unofficial unlock. It should be resolve after that.
(Real relock bootloader method not found yet , it will get RED state after you lock the bootloader)
Note:
1 If you want enter EDL mode, "maybe" you can press VolUp+VolDown+Powerkey when power is off,
screen will be blank after a few seconds, and screen will not display anything during EDL mode.
Connect phone and computer to see whether QFIL detected device.
Long press Powerkey to exit EDL mode.
2 Serial number(string) will be erase, please follow this thread to recover that.
Click to expand...
Click to collapse
Ok. Post rom which works 100%

N3l3 said:
Ok. Post rom which works 100%
Click to expand...
Click to collapse
UnBrick (EDL) - ZQL1830_Factory_201812181515_ChangeFlash.zip

AzimBahar said:
UnBrick (EDL) - ZQL1830_Factory_201812181515_ChangeFlash.zip
Click to expand...
Click to collapse
Post again.

You can get it on ROMDevelopers.
They have huge collection

any one help me am get error cant got to edl mode

Question Custom Binary Blocked by OEM Lock - Edit: it was the bootloader

Today the A33 5G 128GB arrived, to flash twrp on it i had to enable oem unlock and usb debugging first in develeoper options.
To do that i had to complete the setup first, it's sick that the phone did NOT even let me complete the setup without connecting to the internet... this is out of control.
Now, i have oem unlock enabled aswell as usb debugging.
{
"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"
}
Next i connect the phone to PC and booted in download / odin mode.
Then i tried to flash this a33x_experimental_twrp.tar created by Zillion with odin, however as you can see on the next screenshot... the phone says "Custom Binary Blocked by OEM Lock"...
Why does the Phone say Custom Binary Blocked by OEM Lock even when i have it enabled in developer options??!
The Phone-Model is SM-A336B/DSN if that matters? I contacted my service provider from who i bought this phone and they told me that they are selling only this model.
Any help is welcome ...

My last hope is that someone from this forum can help me get twrp and lineage running, otherwise i'll have no choice but to return the phone within 14 days. No way i will use this device with the sick psycho spyware it contains.
PS: My only idea that might be worth a shot is booting twrp from adb terminal on pc, but i'm not sure how that works, how do i flash twrp permanently and how do i flash lineageos from adb, while i might be able to flash lineageos i'm not sure if that would work with the stock recovery..?

You have to unlock your bootloader to be able to flash custom images such as TWRP. When in download mode, hold Volume + until the unlock screen appears. This will wipe data.
After you've unlocked the bootloader, you will need to boot to Android, connect to the Internet, and verify that OEM Unlocking is still visible in Developer Options. If it isn't, Vaultkeeper is not yet disabled and flashing custom images will result in boot failure.

V0latyle said:
You have to unlock your bootloader to be able to flash custom images such as TWRP. When in download mode, hold Volume + until the unlock screen appears. This will wipe data.
After you've unlocked the bootloader, you will need to boot to Android, connect to the Internet, and verify that OEM Unlocking is still visible in Developer Options. If it isn't, Vaultkeeper is not yet disabled and flashing custom images will result in boot failure.
Click to expand...
Click to collapse
Thanks for the info, i tried doing as you told boot in downloadmode and hold volume up untill unlockscreen appears, i'f been holding volume up for over 20 seconds but nothing happens.
Not that i doubt your instructions but are you sure this has to be done in downloadmode and not recovery?
Or do i have to press another button instead? Vol + doesn't seem to do anything.

You can also use Adb ( Adb reboot download)

Privacydroid said:
Thanks for the info, i tried doing as you told boot in downloadmode and hold volume up untill unlockscreen appears, i'f been holding volume up for over 20 seconds but nothing happens.
Not that i doubt your instructions but are you sure this has to be done in downloadmode and not recovery?
Or do i have to press another button instead? Vol + doesn't seem to do anything.
Click to expand...
Click to collapse
Yes, I am sure, bootloader unlock is never done through recovery.
Turn your device off completely with USB disconnected. Leave it off for a minute or so. Then, hold both Volume buttons (DO NOT press Power) and plug in the USB cable from your computer.
This should start the device in Download mode.
Now, hold Volume Up until the bootloader unlock screen appears, which should have an instruction to either press or hold Volume Up to unlock the bootloader.

V0latyle said:
Yes, I am sure, bootloader unlock is never done through recovery.
Turn your device off completely with USB disconnected. Leave it off for a minute or so. Then, hold both Volume buttons (DO NOT press Power) and plug in the USB cable from your computer.
This should start the device in Download mode.
Now, hold Volume Up until the bootloader unlock screen appears, which should have an instruction to either press or hold Volume Up to unlock the bootloader.
Click to expand...
Click to collapse
Thank you Sir. i totally forgot about the bootloader, and i didn't know how it works on the newer models (android 12), thanks to your easy insturctions i was able to unlock the bootloader.

V0latyle said:
You have to unlock your bootloader to be able to flash custom images such as TWRP. When in download mode, hold Volume + until the unlock screen appears. This will wipe data.
After you've unlocked the bootloader, you will need to boot to Android, connect to the Internet, and verify that OEM Unlocking is still visible in Developer Options. If it isn't, Vaultkeeper is not yet disabled and flashing custom images will result in boot failure.
Click to expand...
Click to collapse
I think the bootloader was sucessfully unlocked, just want to mention that after doing that (and the phone was erased) i do not see the oem unlock option under develeoper settings, all other options seem to be listed as normal.
So you are saying i must take care of vaultkeeper before finally flashing lineageos?
How would i handle that?

Privacydroid said:
I think the bootloader was sucessfully unlocked, just want to mention that after doing that (and the phone was erased) i do not see the oem unlock option under develeoper settings, all other options seem to be listed as normal.
So you are saying i must take care of vaultkeeper before finally flashing lineageos?
How would i handle that?
Click to expand...
Click to collapse
See Magisk installation instructions:
Unlocking the bootloader on modern Samsung devices have some caveats. The newly introduced VaultKeeper service will make the bootloader reject any unofficial partitions in some circumstances.
Allow bootloader unlocking in Developer options → OEM unlocking
Reboot to download mode: power off your device and press the download mode key combo for your device
Long press volume up to unlock the bootloader. This will wipe your data and automatically reboot.
Go through the initial setup. Skip through all the steps since data will be wiped again in later steps. Connect the device to Internet during the setup.
Enable developer options, and confirm that the OEM unlocking option exists and is grayed out. This means the VaultKeeper service has unleashed the bootloader.
Your bootloader now accepts unofficial images in download mode
Click to expand...
Click to collapse
If OEM Unlocking is not visible, Vaultkeeper has not unleashed the bootloader yet and you must fix this before proceeding. Look for "KG STATUS" on the screen when your device is in download mode; if this says "PRENORMAL" you cannot flash a custom image. If it says "CHECKING" you should be fine to flash TWRP, and once you flash TWRP, you can install LineageOS.

V0latyle said:
See Magisk installation instructions:
If OEM Unlocking is not visible, Vaultkeeper has not unleashed the bootloader yet and you must fix this before proceeding. Look for "KG STATUS" on the screen when your device is in download mode; if this says "PRENORMAL" you cannot flash a custom image. If it says "CHECKING" you should be fine to flash TWRP, and once you flash TWRP, you can install LineageOS.
Click to expand...
Click to collapse
Well, i tried flashing twrp right now without using magsik, might have been a bad idea.. there's some error now.
Not really a surprise.. i never managed to brick a phone by all the idiotic things i'f done, no clue how to perceed now as the phone keep rebooting to the exact same screen with the exact same error message.
Did i damage the recovery?

You seem softbricked. You can always flash stock recovery. What happens when you try to boot to system? Is it just stuck in Odin mode?

Arealhooman said:
You seem softbricked. You can always flash stock recovery. What happens when you try to boot to system? Is it just stuck in Odin mode?
Click to expand...
Click to collapse
How do i boot to system? Just hold power button? Yes it keeps booting to odin mode, it does not even allow me to shutdown, keep booting to Odin.
Remember when you could simply unplug the battery...
Can i use Frija to download stock recovery or is it only for the "system os"?

Privacydroid said:
How do i boot to system? Just hold power button? Yes it keeps booting to odin mode, it does not even allow me to shutdown, keep booting to Odin.
Remember when you could simply unplug the battery...
Can i use Frija to download stock recovery or is it only for the "system os"?
View attachment 5790277
Click to expand...
Click to collapse
Yes.
Guide to Extract Stock Recovery:
First, download the preferred Samsung stock firmware for your device model.
Extract the firmware zip file on your computer within a folder.
Open the .tar.md5 file using 7Zip. (Download 7Zip)
You will find the ‘recovery.img’ file. This is the stock recovery file for your Samsung device. Select it and hit Extract.
Compress the recovery image file via 7Zip tool in “.tar” format.
Put your Samsung device in Odin Download mode, select ‘AP’ or ‘PDA’ in Odin tool and select the new recovery.tar file, then hit the Start button.
(credit to Getdroidtips)

Btw its in the AP file

Given that TWRP for this device is experimental, this is pretty unsurprising.
Unfortunately without TWRP you won't be able to install LineageOS, unless there's another way I'm not aware of

V0latyle said:
Given that TWRP for this device is experimental, this is pretty unsurprising.
Unfortunately without TWRP you won't be able to install LineageOS, unless there's another way I'm not aware of
Click to expand...
Click to collapse
After re-flashing the stock firmware i checked the KG-STATUS and it says "broken"
Indeed the twrp i tried to flash is experimental and made by @Zillion
Might sound like a stupid question, people like andy yan appear to provide GSI's (generic system images) just curious if the same would be possible with twrp? A generic twrp image that is compatible with any/most devices? Basically, if mr Zillions twrp does not function yet, what other twrp could i try?

Arealhooman said:
Yes.
Guide to Extract Stock Recovery:
First, download the preferred Samsung stock firmware for your device model.
Extract the firmware zip file on your computer within a folder.
Open the .tar.md5 file using 7Zip. (Download 7Zip)
You will find the ‘recovery.img’ file. This is the stock recovery file for your Samsung device. Select it and hit Extract.
Compress the recovery image file via 7Zip tool in “.tar” format.
Put your Samsung device in Odin Download mode, select ‘AP’ or ‘PDA’ in Odin tool and select the new recovery.tar file, then hit the Start button.
(credit to Getdroidtips)
Click to expand...
Click to collapse
Thanks, i managed to re-flash the stock firmware!
I actually didn't want to whole system (the os) the be re-flashed but only the recovery, however when i extract the AP file i do not get any recovery.img file.
`
Edit: i see recovery.img.lz4 (can i use that aswell to re-flash stock recovery, i never saw .lz4 whatever that is.

I tried flashing twrp with odin by placing it in the AP slot, so since that didn't work would it be worth a shot trying to flash it with adb via pc instead? Or is magisk a hard requirement now to bypass Vaultkeeper to be able and flash twrp?

V0latyle said:
Given that TWRP for this device is experimental, this is pretty unsurprising.
Unfortunately without TWRP you won't be able to install LineageOS, unless there's another way I'm not aware of
Click to expand...
Click to collapse
actually theres a way of repacking using lz4 images, but i dont really know how to do it

Privacydroid said:
After re-flashing the stock firmware i checked the KG-STATUS and it says "broken"
View attachment 5790319
Indeed the twrp i tried to flash is experimentla and made by @Zillion
Might sound like a stupid question, people like andy yan appear to provide GSI's (generic system images) just curious if the same would be possible with twrp? A generic twrp image that is compatible with any/most devices? Basically, if mr Zillions twrp does not function yet, what other twrp could i try?
Click to expand...
Click to collapse
Wich device is that
*A33 TWRP was never meant for final users
The latest build was just a testing one

Database Develop

welcome