Database Develop

[GUIDE] Unbrick your device or recover from bootloop

Assalamu alaikum people,
Those on the telegram group know that I bugged you a lot about needing data partition. Because of my experience with unbricking and recovering the device, I can tell you a sureshot method that works to restore the device. Do not use this method if your device already works. There seems to be a lot of files inside the data partition which are necessary for the stock ROM to work. This method asks you to wipe data partition and so system update will not work. This should be a last resort. .
Many people seem to have come to the situation where they are in fastboot, and it says frp locked, so they cannot flash new twrp. And the system seems to be in bootloop and it does not work. What to do from there?
1. Download this file ->https://www.androidfilehost.com/?fid=673956719939832337.
2. In your SDCard, create a folder called TWRP and inside it, create a folder called BACKUPS (all in capitals). Inside this, create a folder called 7xtwrpbackup (small letters) and paste the contents of the zip that you have downloaded into this.
3. Boot to twrp in your device and go to restore. There you should see a folder 7xtwrpbackup. If you select it, you will get a checkbox below with recovery_ramdisk like this
{
"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"
}
4. Select Yes and after restore complete, go back and select reboot and reboot to recovery.
5. Now, the new twrp will boot. In the new twrp, I want you to first go to wipe -> advanced wipe -> select dalvik/art cache, cache, data, internal storage and system.
6. Come back once again and select wipe, and this time, select format data. It will ask you to type yes. After that is done, come back once again.
7. Now select install and in that, install the openkirin RR image from telegram group or here -> https://forum.xda-developers.com/honor-view-10/development/rom-t3753555 (This step is optional because openkirin RR has a greater chance of booting than stock ROM. You can skip this step and directly boot stock)
8. Your system must boot now. If it boots, then all partitions are good. You can boot stock.
9. You can now can download stock from my post here and repeat from step 5-> https://forum.xda-developers.com/9-lite/development/stock-img-unlock-indian-version-t3767569
If this does not work, then look at the second method in the next post

Second method
If your first method does not work, then you can try this second method. Make sure you have enough data left in your internet connection (1.8 GB ish) before starting the process. Please note that this method will lock your bootloader, install stock recovery, flash the stock system and boot your phone. Of course, even if it relocks the bootloader, you can still unlock it using your code.
1. Download the zip
https://www.androidfilehost.com/?fid=746010030569970895
2. Extract it into sdcard directly (i.e. extract it to the root folder of your sdcard)
3. Make sure you have enough battery left (atleast 15%). Power off your phone. Now, press and hold vol up + Vol down + power buttons until the honor logo comes. Then, you can release all the keys. The system will go into emui recovery and restore your phone.
You will have stock phone at the end of the process.
Note:-If you still have bootloop at Honor logo, then power off the phone. Hold vol up + power button until the honor logo comes. It will boot into stock recovery. From there, you can do a factory reset and erase cache partition. Then the phone will definitely boot up.

Bricked my device Twrp doesn't work
Hello, I have bricked my honor 9 lite AL10(Indian Version). I have formatted my vender directory through Twrp by mistake now my device shows erecovery and reboots. Fastboot is working fine and FRP and Devices both shows unlocked means I can flash through fastboot. I don't want to lose my internal memory data.
Help me to unbrick my device !! :crying:

Oushal kDee said:
Hello, I have bricked my honor 9 lite AL10(Indian Version). I have formatted my vender directory through Twrp by mistake now my device shows erecovery and reboots. Fastboot is working fine and FRP and Devices both shows unlocked means I can flash through fastboot. I don't want to lose my internal memory data.
Help me to unbrick my device !! :crying:
Click to expand...
Click to collapse
Download vendor partition from here https://forum.xda-developers.com/9-lite/development/stock-img-unlock-indian-version-t3767569

Hello i am siddharth, i have relocked my oem by fastboot oem relock -------- after that yes/no option came i click on yes. It starts factory formatting after completion of formatting when the phone starts its showing your device has failed verification and got stuck in it. When i press reboot option it will directly comes to erecovery mode wher the option came to download new recovery when i connect my phone with wifi it starts searching for some time after that system update failed.
When i starts mobile directly to fastboot mode by pressing volume down button and power button the white screen with android comes appear i.e fastboot mode screen. In that screen in green colour i found that
Phone Relock
FRP lock
When ever i m trying to find the device in fastboot mode by typing fastboot devices my device showing there but no other command is working such as fastboot oem unlock -------, fastboot flash system system.img, all the time it comes Failed.
I have downloaded many UPDATE.APP and tried to load that by dload method but every time after 5% it come Failed to install.
I have downloaded UPDATE.APP form ur given link also. This is only the image in which my phone comes upto 23% install after dat failed.
Nothing working for me. Kindly help me.
Mail me if there is any solution @
[email protected]

i have tried first method it failed and says 'no partition selected for restore'
and their is no option to select partition what should i do plz help

None of the method worked for me my device still bootloops no matter what system.img or rom zip file i flash. The emui recovery method didn't work for me as it loaded up to 5% and then failed instantly. Please help me unbrick my 9 lite bro. Could you provide me the boot.img? i think my phone got bricked because i tried to i install magisk on treble rom (i guess?). But anyway PLEASE HELP ME (

Try extracting kernel.img from an update and flash that. It fixed it for me.

hi twrp is bootlooping as well
cant access
---------- Post added at 07:15 PM ---------- Previous post was at 06:52 PM ----------
hey i used the twrp from the link made a backup restored it now a get bootloop cant get into twrp it goes in ti it then it fcs then am back to bootloader unlocked warning

hi anyone got custom.img and userdata.img from this LLDL31C432B130 800130 a need to restore my device

Same Problem
[email protected] said:
i have tried first method it failed and says 'no partition selected for restore'
and their is no option to select partition what should i do plz help
Click to expand...
Click to collapse
Even I'm facing the same problem, if anyone has solution plz help.
---------- Post added at 10:15 AM ---------- Previous post was at 10:10 AM ----------
[email protected] said:
i have tried first method it failed and says 'no partition selected for restore'
and their is no option to select partition what should i do plz help
Click to expand...
Click to collapse
Even I'm facing the same problem.

mine goes to 5% doesnt do anything and then it fails

aveemashfaq said:
If your first method does not work, then you can try this second method. Make sure you have enough data left in your internet connection (1.8 GB ish) before starting the process. Please note that this method will lock your bootloader, install stock recovery, flash the stock system and boot your phone. Of course, even if it relocks the bootloader, you can still unlock it using your code.
1. Download the zip
https://www.androidfilehost.com/?fid=746010030569970895
2. Extract it into sdcard directly (i.e. extract it to the root folder of your sdcard)
3. Make sure you have enough battery left (atleast 15%). Power off your phone. Now, press and hold vol up + Vol down + power buttons until the honor logo comes. Then, you can release all the keys. The system will go into emui recovery and restore your phone.
You will have stock phone at the end of the process.
Note:-If you still have bootloop at Honor logo, then power off the phone. Hold vol up + power button until the honor logo comes. It will boot into stock recovery. From there, you can do a factory reset and erase cache partition. Then the phone will definitely boot up.
Click to expand...
Click to collapse
But this is for L31
---------- Post added at 08:06 AM ---------- Previous post was at 08:05 AM ----------
My phone's frp and bootloader locked,and phone is booting to erecovery,what to do

need help with LLD-AL10C675 indian version
I have flashed a cutom treble rom phh-treble to be specific,used it for couple of days and then tried instaling the magisk from magiskmanager and after its done when i reboot it shows error mode with message Func no:10(boot img ) and func no:2 , i can boot into fastboot mode both frp and phone unlocked ,can some please help me to get back my phone into a usable condition thank you

sunny_deed said:
I have flashed a cutom treble rom phh-treble to be specific,used it for couple of days and then tried instaling the magisk from magiskmanager and after its done when i reboot it shows error mode with message Func no:10(boot img ) and func no:2 , i can boot into fastboot mode both frp and phone unlocked ,can some please help me to get back my phone into a usable condition thank you
Click to expand...
Click to collapse
To help you a full firmware is required and that's not available for (India c675) yet!
Before any modification to system you should have a full firmware in hand.

BS4388 said:
To help you a full firmware is required and that's not available for (India c675) yet!
Before any modification to system you should have a full firmware in hand.
Click to expand...
Click to collapse
yea that was a pretty big mistake i made without looking for it, i have been told by someone that we can pull out all the require d imgs from a phone in good working condition, i asked in the hopes that someone would be generous enough to do that for me , thank you ,and also does anyone have any idea about when the full firmware will be released

sunny_deed said:
yea that was a pretty big mistake i made without looking for it, i have been told by someone that we can pull out all the require d imgs from a phone in good working condition, i asked in the hopes that someone would be generous enough to do that for me , thank you ,and also does anyone have any idea about when the full firmware will be released
Click to expand...
Click to collapse
What's wrong with the version (675) from here :-
https://www.mobileheadlines.net/download-huawei-honor-9-lite-firmware-files/

Sparkrite said:
What's wrong with the version (675) from here :-
https://www.mobileheadlines.net/download-huawei-honor-9-lite-firmware-files/
Click to expand...
Click to collapse
there is no Fullota version in there

sunny_deed said:
there is no Fullota version in there
Click to expand...
Click to collapse
Go:
https://forum.xda-developers.com/9-lite/development/stock-rom-indian-firmware-c675-t3813875

sunny_deed said:
there is no Fullota version in there
Click to expand...
Click to collapse
My bad, I was only trying to help.............
Anyway you have it now (post above) thanks to @BS4388 and @VigneshS007 .

Maze Alpha X Bootloop Problem [SOLVED]

Hello everybody please help me. I tried to Root my phone I unlocked the phone while getting help from “dreambo” then I unlocked the phone and download twrp recovery then when I tried to start phone it only showed me recovery menu sistem was not opening then tried to chech “dreambo” again then i saw a picture (picture 1) there I wrote “fastboot flash recovery boot.alpha.x.img” instead of “fastboot flash boot boot.alpha.x.img” and now phones recovery didnt open and become bootloop it shows logo then turn off (video 1) then i cant able to to put phone into “bootloader mode” . I know this phone doesn’t have stock rom how can i fix this phone ?
dreambo Thread: Root and TWRP 3.2.1 for Maze Alpha X 6/64
(picture 1)
{
"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"
}
(video 1)​
video link: https://youtu.be/QYMCOQiExMg
Originally Posted
dreambo said:
I am almost sure that you have flashed the recovery image in the boot partition !
You have do that fastboot flash boot recovery.img instead of fastboot flash recovery recovery.img
To have your phone working, just flash the attached boot.img : fastboot flash boot boot.alpha.x.img
Click to expand...
Click to collapse
Edit: Way to solve Problem:
Stive very thanks to my friend after a long time I fixed the phone. In order to do UNBRICK phone download this from link and than put phone into charge than connect phone to computer with usb and open "Flash tool" program than add “MT6757_Android_scatterr.txt” file than put it “Frimware Upgrade” than download and wait until it finished.
Stive87 said:
Unbrick Maze Alpha X 6/64GB only phone is black screen and phone is total brick (format all partition).
https://drive.google.com/file/d/12t3MHsAWBlXyKm_ktJt9GKqZ9sOrFRVi/view
Rom is no official :
System : official rom for Maze Alpha B6/64GB . (! no update after - OTA !!),
boot, logo and recovery is normal (copy from original my phone).
Good luck.
Sorry for bad english, my french ^^
Click to expand...
Click to collapse
Stive87 said:
https://drive.google.com/file/d/12t3MHsAWBlXyKm_ktJt9GKqZ9sOrFRVi/view?usp=drivesdk
full rom V03 6/64GB Rom Ofifcial Stock
https://drive.google.com/file/d/1WjXKj8abnghy_OjfUW5TYkAppjWg0amH/view?usp=sharing
Click to expand...
Click to collapse
Thanks to everyone who helped!!

help please

rafaello21 said:
help please
Click to expand...
Click to collapse
Became interested in this phone since I found a 6/128 model for 160$. If fastboot is failing (maybe because of the different partition size?) I'd go with SPFlashTool: if I remember well phone only need to be swithed off when you start downloading the image, therefore it goes well with bootloping if you choose the right moment

matteo.de-leo said:
Became interested in this phone since I found a 6/128 model for 160$. If fastboot is failing (maybe because of the different partition size?) I'd go with SPFlashTool: if I remember well phone only need to be swithed off when you start downloading the image, therefore it goes well with bootloping if you choose the right moment
Click to expand...
Click to collapse
I bought it 170$ when it was on discount no matter what i do “bootloader mode” not works because of the error that i did and no one helps

rafaello21 said:
I bought it 170$ when it was on discount no matter what i do “bootloader mode” not works because of the error that i did and no one helps
Click to expand...
Click to collapse
That's exactly what I'm saying: SPFlashTool doesn't require your phone to be in fastboot mode, only to be switched of when you plug it in. I had the same problem with an Archos Sense 55S after treying to root it. I wasn't able to enter neither fastboot or recovery mode, therefore I flashed the stock rom with SPFT

matteo.de-leo said:
That's exactly what I'm saying: SPFlashTool doesn't require your phone to be in fastboot mode, only to be switched of when you plug it in. I had the same problem with an Archos Sense 55S after treying to root it. I wasn't able to enter neither fastboot or recovery mode, therefore I flashed the stock rom with SPFT
Click to expand...
Click to collapse
I would do it if i have Stock rom ? i am very disappointed because of bought this phone how is it possible that phone doesnt have stock rom is there any possibility to fix this without stock rom?

rafaello21 said:
I would do it if i have Stock rom i am very disappointed because of bought this phone how is it possible that phone doesnt have stock rom is there any possibility to fix this without stock rom?
Click to expand...
Click to collapse
Which model are you using, the 6/64 or the 6/128?
For the former you can use a TWRP Backup done by @dreambo in order to restore at least the boot and and recovery partition
https://forum.xda-developers.com/maze-alpha/development/recovery-twrp-3-2-1-maze-alpha-x-t3740575
while for the latter a link in this post (https://forum.xda-developers.com/maze-alpha/development/original-rom-t3720714) is given ( eventually as soon as my phone arrives I can dump the image):
Option 1) https://drive.google.com/drive/folde...ZyDQFgygsdkei2
Option 2) http://bit.ly/2GKcmYe

matteo.de-leo said:
Which model are you using, the 6/64 or the 6/128?
For the former you can use a TWRP Backup done by @dreambo in order to restore at least the boot and and recovery partition
https://forum.xda-developers.com/maze-alpha/development/recovery-twrp-3-2-1-maze-alpha-x-t3740575
while for the latter a link in this post (https://forum.xda-developers.com/maze-alpha/development/original-rom-t3720714) is given ( eventually as soon as my phone arrives I can dump the image):
Option 1) https://drive.google.com/drive/folde...ZyDQFgygsdkei2
Option 2) http://bit.ly/2GKcmYe
Click to expand...
Click to collapse
Hi, can i use this to restore my phone? And do you know how? I did a search in the web but didn't fin any solution.

ttl1982 said:
Hi, can i use this to restore my phone? And do you know how? I did a search in the web but didn't fin any solution.
Click to expand...
Click to collapse
Hi ttl1982, before giving an answer I should know what are we talking about. Is it the same phone? And which version? What is the current situation (bootlooping into TWRP, bootlooping into Android)? Even assuming we're still talking about the Maze Alpha X, there are still too much variables!

matteo.de-leo said:
Which model are you using, the 6/64 or the 6/128?
For the former you can use a TWRP Backup done by @dreambo in order to restore at least the boot and and recovery partition
https://forum.xda-developers.com/maze-alpha/development/recovery-twrp-3-2-1-maze-alpha-x-t3740575
while for the latter a link in this post (https://forum.xda-developers.com/maze-alpha/development/original-rom-t3720714) is given ( eventually as soon as my phone arrives I can dump the image):
Option 1) https://drive.google.com/drive/folde...ZyDQFgygsdkei2
Option 2) http://bit.ly/2GKcmYe
Click to expand...
Click to collapse
I have Maze Alpha X 6/64 model. If “bootloader mode” doesnt open how can i install ‘twrp’ ? About Thread article i read everything but my only problem is my phone dont open “bootloader mode”. And only solution is stock rom i think than you need SPFlashTool to install it. Maybe you know better than me how can i install “twrp” without opening “bootloader mode” ? I wrote above why this happened.
I click Power and Vol+ buttons as i show in the video phone turn of but doesn’t open “bootloader mode”

rafaello21 said:
I have Maze Alpha X 6/64 model. If “bootloader mode” doesnt open how can i install ‘twrp’ ? About Thread article i read everything but my only problem is my phone dont open “bootloader mode”. And only solution is stock rom i think than you need SPFlashTool to install it. Maybe you know better than me how can i install “twrp” without opening “bootloader mode” ? I wrote above why this happened.
I click Power and Vol+ buttons as i show in the video phone turn of but doesn’t open “bootloader mode”
Click to expand...
Click to collapse
No, even in the case you just want to boot into TWRP (and be able to use one of the backups provided in that post) you need to access fastboot mode. during bootlooping does your PC find the device with the "adb devices" command (namely, as soon as your phone boots up you'd spam this command via terminal)?

matteo.de-leo said:
Hi ttl1982, before giving an answer I should know what are we talking about. Is it the same phone? And which version? What is the current situation (bootlooping into TWRP, bootlooping into Android)? Even assuming we're still talking about the Maze Alpha X, there are still too much variables!
Click to expand...
Click to collapse
Hi, Thanks for your quick response. I will share some more info like you asked.
- Phone: Maze Alpha X
- Version: 6GB RAM/128GB Storage
- Current situation: It won't start at all (when connected to Windows PC i get the 'USB device not recognized' error, so it does see something)
My idea is the following:
- Install recovery with SPK flashtool
- Restore with backup (i have this from another thread) or the system dump.
The above does not work because i do not have the correct preloader file (so SPK flash tool does recognize the phone?).
ADB is not recognizing the phone, so it can't be done that way (as far as my knowledge goes).
I asked Maze several times to provide me the original rom but i get zero response, no matter on what channel i ask them.

matteo.de-leo said:
No, even in the case you just want to boot into TWRP (and be able to use one of the backups provided in that post) you need to access fastboot mode. during bootlooping does your PC find the device with the "adb devices" command (namely, as soon as your phone boots up you'd spam this command via terminal)?
Click to expand...
Click to collapse
I will try but phone turn off and one very quick. Is 1-2 seconds enough for doing what you are saying ? Twrp flash i have to do ? Is there any phone and have similar problem like this ? Can help with help of Video ? And i will try what you said and back to you thanks

ttl1982 said:
Hi, Thanks for your quick response. I will share some more info like you asked.
- Phone: Maze Alpha X
- Version: 6GB RAM/128GB Storage
- Current situation: It won't start at all (when connected to Windows PC i get the 'USB device not recognized' error, so it does see something)
I got this phone from my nephew. He broke it because he flashed the Maze Alpha (not X) 4GB RAM/64GB storage rom on it because he had TWRP bootloops.
My idea is the following:
- Install recovery with SPK flashtool
- Restore with backup (i have this from another thread) or the system dump.
The above does not work because i do not have the correct preloader file (so SPK flash tool does recognize the phone?).
ADB is not recognizing the phone, so it can't be done that way (as far as my knowledge goes).
I asked Maze several times to provide me the original rom but i get zero response, no matter on what channel i ask them.
Click to expand...
Click to collapse
I also wrote them several times about stock rom but they didn’t answer me i think company only think about money. Do we have to throw our phone to garbage because of one wrong thing ? What should i do ?

ttl1982 said:
My idea is the following:
- Install recovery with SPK flashtool
- Restore with backup (i have this from another thread) or the system dump.
Click to expand...
Click to collapse
Yes I was thinking the same. Eventually you do not need to install the recovery, restoring the bootloader should be enough: if the bootloader is already unlocked you can just boot into TWRP and from there restoring the backup previously copied into a SD card.
The above does not work because i do not have the correct preloader file (so SPK flash tool does recognize the phone?).
Click to expand...
Click to collapse
Why do you say you don't have the right one? Did SPFlashTool return you some error?
I asked Maze several times to provide me the original rom but i get zero response, no matter on what channel i ask them.
Click to expand...
Click to collapse
Well AFAIK Maze is completely done, no surprise if they do not answer. I'm reasonably sure that there's a way to dump these files from a working phone, if I'm right I'll try with mine

matteo.de-leo said:
No, even in the case you just want to boot into TWRP (and be able to use one of the backups provided in that post) you need to access fastboot mode. during bootlooping does your PC find the device with the "adb devices" command (namely, as soon as your phone boots up you'd spam this command via terminal)?
Click to expand...
Click to collapse
I tried when I click Power and Vol+ it does bootloop.But the only way to put phone into “bootloader mode” you need SPFlashTool. I dont know what can i do now. When phone was bootlooping i wrote several times “adb devices” but nothing happened

matteo.de-leo said:
Yes I was thinking the same. Eventually you do not need to install the recovery, restoring the bootloader should be enough: if the bootloader is already unlocked you can just boot into TWRP and from there restoring the backup previously copied into a SD card.
I will try this, maybe that works.
Why do you say you don't have the right one? Did SPFlashTool return you some error?
Yes, it says 'status preloader invalid'
Well AFAIK Maze is completely done, no surprise if they do not answer. I'm reasonably sure that there's a way to dump these files from a working phone, if I'm right I'll try with mine
Click to expand...
Click to collapse
That explains a lot. But it is still not acceptable to answer no one imo
---------- Post added at 10:48 PM ---------- Previous post was at 10:34 PM ----------
matteo.de-leo said:
Yes I was thinking the same. Eventually you do not need to install the recovery, restoring the bootloader should be enough: if the bootloader is already unlocked you can just boot into TWRP and from there restoring the backup previously copied into a SD card.
Why do you say you don't have the right one? Did SPFlashTool return you some error?
Well AFAIK Maze is completely done, no surprise if they do not answer. I'm reasonably sure that there's a way to dump these files from a working phone, if I'm right I'll try with mine
Click to expand...
Click to collapse
ttl1982 said:
That explains a lot. But it is still not acceptable to answer no one imo
Click to expand...
Click to collapse
I now get another error when flashing boot.img:
ERROR: STATUS_BROM_CMD_STARTCMD_FAIL

ttl1982 said:
ERROR: STATUS_BROM_CMD_STARTCMD_FAIL
Click to expand...
Click to collapse
As reported by another user on this website: https://forum.hovatek.com/thread-21351.html
The device attempted to power on before SP flash tool could flash files to it
Click to expand...
Click to collapse
Phone must be plugged (while switched off) to the USB port after having given the Download order to SP
---------- Post added at 09:38 PM ---------- Previous post was at 09:34 PM ----------
By the way, it seems that this very website (in particular here https://forum.hovatek.com/thread-468.html) hosts a guide to dump a Mediatek firmware SPFlashTool compatible, together with the necessary files, but guess what? You need to register in order to download them, something that I'll definitely do if it just lets me

ttl1982 said:
I now get another error when flashing boot.img:
Click to expand...
Click to collapse
Which boot.img you chose ?
matteo.de-leo said:
Phone must be plugged (while switched off) to the USB port after having given the Download order to SP
Click to expand...
Click to collapse
What should i do exactly to use SPFlashTool ? What alternative ? When I connect my phone to pc it turn off turn on then power volume + and - buttons randomly and than turn on turn off stoped now it looks like this in the picture . Than i checked “adb devices” it says “waiting for devices”. The thing that “dreambo” shared “boot.alpha.x.img” and can i adjust this with SPFlashTool and install it ?

rafaello21 said:
Which boot.img you chose ?
What should i do exactly to use SPFlashTool ? What alternative ? When I connect my phone to pc it turn off turn on then power volume + and - buttons randomly and than turn on turn off stoped now it looks like this in the picture . Than i checked “adb devices” it says “waiting for devices”. The thing that “dreambo” shared “boot.alpha.x.img” and can i adjust this with SPFlashTool and install it ?
View attachment 4518023
Click to expand...
Click to collapse
I have used the exact same boot.img as you did.

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!

Installing twrp on Sprint v40 flashed to us pie

Recently downgraded from Verizon 10.0 to us pie in order to root / install custom ROM. I've followed all guides and Its not going good. To start, I've successfully unlocked my bootloader after 2 failed attempts. However, when I try to enter fastboot after installing my default abl_a/b, it just boots normally. To get back into fastboot, I have to load the v35 image first . Even after getting into fastboot, I am still unable to flash twrp. The flash says completed and the phone turns on but boots normally.
Does anyone have a solution for this ? Is this blocked and is there any bypass ?

kris597 said:
Recently downgraded from Verizon 10.0 to us pie in order to root / install custom ROM. I've followed all guides and Its not going good. To start, I've successfully unlocked my bootloader after 2 failed attempts. However, when I try to enter fastboot after installing my default abl_a/b, it just boots normally. To get back into fastboot, I have to load the v35 image first . Even after getting into fastboot, I am still unable to flash twrp. The flash says completed and the phone turns on but boots normally.
Does anyone have a solution for this ? Is this blocked and is there any bypass ?
Click to expand...
Click to collapse
First, the phone doesn't have fastboot, normally. So, after you flash the normal (stock) abl back, you should not be able to get to fastboot, so that's expected.
Second, getting twrp on the device has changed, you don't 'boot it', you need your boot partition with twrp 'injected' into it already (that's the easiest way). Which version of US Open Pie do u have? Can't seem to find a boot partition of it with twrp injected, but that's what u need.
Also, do u know what your current slot is? If u flash something to the other slot, it won't change anything. Use 'fastboot getvar all' and at the bottom of the output it will tell you what current slot is.
cheers

I tried injecting twrp directly into both my boot partitions and it just bootloops. I am also currently on active slot a . Prior to this, I was attempting to flash twrp using Verizon 10.0. However, after following countless guides, I was unsuccessful and tried to do it on this current version
{
"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"
}

kris597 said:
I tried injecting twrp directly into both my boot partitions and it just bootloops. I am also currently on active slot a . Prior to this, I was attempting to flash twrp using Verizon 10.0. However, after following countless guides, I was unsuccessful and tried to do it on this current version View attachment 5453895
Click to expand...
Click to collapse
So, from your previous post this is us Open 20a correct? Even though it says UA, it's actually QA right?
Also, how did u 'try injecting directly to your boot partition'? Did u use twrp? How did u do that?
Remember, once u have twrp in the boot partition, you should be going directly to twrp, not boot the system. Format data, reboot recovery, flash magisk and dm-verity, then boot system (not before).
Have you tried posting in the guide u followed? Usually you'll find answers there most often.
cheers

AsItLies said:
So, from your previous post this is us Open 20a correct? Even though it says UA, it's actually QA right?
Also, how did u 'try injecting directly to your boot partition'? Did u use twrp? How did u do that?
Remember, once u have twrp in the boot partition, you should be going directly to twrp, not boot the system. Format data, reboot recovery, flash magisk and dm-verity, then boot system (not before).
Have you tried posting in the guide u followed? Usually you'll find answers there most often.
cheers
Click to expand...
Click to collapse
I loaded judypn twrp image into boot a/b using qfill. It just boot loops. I have posted in the guide. Unfortunately no luck

kris597 said:
I loaded judypn twrp image into boot a/b using qfill. It just boot loops. I have posted in the guide. Unfortunately no luck
Click to expand...
Click to collapse
That's not the way it works, it's supposed to be 'injected' by twrp itself, in the advanced options of twrp, there's a selection called 'inject twrp', and you give it the name of the twrp image (on the sd card) and it then injects that image into the current boot loader of the device (the actual 64 meg image on the hard drive boot partition of the device).
Post in this thread your current boot image, and the twrp image. If your device is crossflashed by lgup, then both a and b boot images are the same. If your device is booting a carrier image, be sure to pull the boot image from the current boot slot (as boot a and boot b will be different).
I'll inject the twrp image into it for you. Then u use qfil and flash it, boot directly to recovery (now twrp) from qfil (use key combo), and follow what I mentioned in prev post.

AsItLies said:
That's not the way it works, it's supposed to be 'injected' by twrp itself, in the advanced options of twrp, there's a selection called 'inject twrp', and you give it the name of the twrp image (on the sd card) and it then injects that image into the current boot loader of the device (the actual 64 meg image on the hard drive boot partition of the device).
Post in this thread your current boot image, and the twrp image. If your device is crossflashed by lgup, then both a and b boot images are the same. If your device is booting a carrier image, be sure to pull the boot image from the current boot slot (as boot a and boot b will be different).
I'll inject the twrp image into it for you. Then u use qfil and flash it, boot directly to recovery (now twrp) from qfil (use key combo), and follow what I mentioned in prev post.
Click to expand...
Click to collapse
These are all the files i found / used. My device no longer has a carrier image as i crossflashed to global pie.
Im still a little confused. In all the guides i've followed, they've either used fastboot to booth twrp image and then install twrp after or load the twrp image straight into boot a/b.

kris597 said:
These are all the files i found / used. My device no longer has a carrier image as i crossflashed to global pie.
Im still a little confused. In all the guides i've followed, they've either used fastboot to booth twrp image and then install twrp after or load the twrp image straight into boot a/b.
Click to expand...
Click to collapse
I spoke too soon, my current device is LG G8, it has twrp, but unfortunately adb shell doesn't work on this twrp version. So I can't do this anymore.
I would suggest, in the guide you mention, I saw your last post but didn't know how to respond because you didn't say what command u used that resulted in:
downloading 'boot.img'... OKAY [ 2.124s]
booting... FAILED (remote: Failed to load/authenticate boot image: Load Error)
The version of twrp you have won't boot. twrp has to be 'injected' into the boot image, so you'll then have a boot image and twrp (recovery) will be in it.
Post again in that guide, so others can learn from it. But put in the exact command you were using to try to get to twrp, that would help a lot so others know what yer doing.
cheers

I should add, yes, this is confusing, sorry.
the guide you want to follow to get twrp is this one.
The reason(s) yer having trouble booting that version of twrp I believe it's because of 1) the engineering abl is Oreo, it won't boot anything that isn't Oreo based. 2) to be able to boot that version of twrp, follow the guide above and 'nuke laf' (back it up first, in case you need download mode - lgup, again).
so, as mentioned in the guide, in the 'nuke laf' section, you now get to fastboot by using the keys you'd normally use to get to lgup, but now u get a 'watered down' version of fastboot.
Pretty sure u can then use that version of fastboot to boot your version of twrp and then follow the directions in the guide to 'inject' it into ramdisk (the boot partition).
cheers

kris597 said:
These are all the files i found / used. My device no longer has a carrier image as i crossflashed to global pie.
Im still a little confused. In all the guides i've followed, they've either used fastboot to booth twrp image and then install twrp after or load the twrp image straight into boot a/b.
Click to expand...
Click to collapse
Managed to get a version of twrp that does what's needed, installed. The attached is your boot partition with twrp injected. Both a and b images were the same so it will work for both slots.
Flash it with qfil, then use key combo to go directly to recovery. Once in twrp, format data, reboot recovery, flash magisk (if wanted) and dm-verity-force... and you should be all set.
cheers

My phone is now unresponsize and stuck on a black screen. Was i supposed to boot a and b ?
I am unable to enter edl, download mode or any mode. It is completely unresponsize. Is it hard bricked ?
Edit: I was able to enter edl mode and restore my original boot partitions, however, im still stuck on a black screen and can only enter edl
AsItLies said:
Managed to get a version of twrp that does what's needed, installed. The attached is your boot partition with twrp injected. Both a and b images were the same so it will work for both slots.
Flash it with qfil, then use key combo to go directly to recovery. Once in twrp, format data, reboot recovery, flash magisk (if wanted) and dm-verity-force... and you should be all set.
cheers
Click to expand...
Click to collapse

kris597 said:
My phone is now unresponsize and stuck on a black screen. Was i supposed to boot a and b ?
I am unable to enter edl, download mode or any mode. It is completely unresponsize. Is it hard bricked ?
Edit: I was able to enter edl mode and restore my original boot partitions, however, im still stuck on a black screen and can only enter edl
Click to expand...
Click to collapse
wow what in the world did u do? You really need to say specifically the steps you did to get where u are now, I mean, telling me the results and saying 'what do I do' is assuming I expected this to happen?
this is totally unexpected. What, exactly, did u do?

AsItLies said:
wow what in the world did u do? You really need to say specifically the steps you did to get where u are now, I mean, telling me the results and saying 'what do I do' is assuming I expected this to happen?
this is totally unexpected. What, exactly, did u do?
Click to expand...
Click to collapse
I followed the steps correctly i believe. I have experience with rooting and flashing in the past but its entirely different with LG.
The steps i followed:
I entered EDL MODE, i flashed the boot_a_twrp to both my a & B slots and it was successful. After this, i tried to enter recovery mode and was left with a black screen, no vibration, screen or any form of life. Tried booting may times, holding down power + volume down for 4+ minutes but still no hope. I was then able to get back into edl where i flashed my original images back . Unfortunately, it is still not working. Sucks that i will have to buy a new phone now. I guess this is where i stop messing with my phone lol .

kris597 said:
I followed the steps correctly i believe. I have experience with rooting and flashing in the past but its entirely different with LG.
The steps i followed:
I entered EDL MODE, i flashed the boot_a_twrp to both my a & B slots and it was successful. After this, i tried to enter recovery mode and was left with a black screen, no vibration, screen or any form of life. Tried booting may times, holding down power + volume down for 4+ minutes but still no hope. I was then able to get back into edl where i flashed my original images back . Unfortunately, it is still not working. Sucks that i will have to buy a new phone now. I guess this is where i stop messing with my phone lol .
Click to expand...
Click to collapse
Wow, sorry to hear that. From what you're saying it sounds as though you did the right steps. To clarify, to exit edl mode is hold vol minus and power buttons until u hear the windows chime meaning 'disconnect' (usually only about 5 to 10 secs).
It is certain that newer phones are much more complicated, with dual slots and the challenge they present, and it's even worse with LG as they don't allow bl unlock and don't have fastboot, so getting those adds to the complexity.
You say you flashed the image to boot a and b, did u get a message about 'data overflow' by chance? (If so, that would explain the situation, but not how it happened). If an image was flashed to an incorrect partition (not that hard to make that mistake in qfil), and someone 'okays' the 'data overflow' message, it will **overwrite** nearby partition(s), resulting in a brick.
Assuming something like the above happened, there's an option, unfortunately it's a bit complicated also.

AsItLies said:
Wow, sorry to hear that. From what you're saying it sounds as though you did the right steps. To clarify, to exit edl mode is hold vol minus and power buttons until u hear the windows chime meaning 'disconnect' (usually only about 5 to 10 secs).
It is certain that newer phones are much more complicated, with dual slots and the challenge they present, and it's even worse with LG as they don't allow bl unlock and don't have fastboot, so getting those adds to the complexity.
You say you flashed the image to boot a and b, did u get a message about 'data overflow' by chance? (If so, that would explain the situation, but not how it happened). If an image was flashed to an incorrect partition (not that hard to make that mistake in qfil), and someone 'okays' the 'data overflow' message, it will **overwrite** nearby partition(s), resulting in a brick.
Assuming something like the above happened, there's an option, unfortunately it's a bit complicated also.
Click to expand...
Click to collapse
I believe i got a message similar to that
Edit: Cant be bothered to try any new methods. Will get a refurbished lg v60 from amazon. Had the v40 for 2 years. Its time to upgrade
cheers and thankyou for your help

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