Related
Hello,
i have bought a new Xiaomi Mi A2 and thought it would be a really nice idea to flash magisk on it. First everything was alright. I unlocked my bootloader in fastboot with "fastboot oem unlock" and flashed twrp on the b partition. Unfortunately my device broke (don't know why... maybe the unofficial twrp with some bugs or...). So now i have a really big problem, because my twrp recovery is missing as well as the stock recovery. When i try to switch on the mobile i am stuck in bootloop (with the mi logo). Not even the bootloader warning is shown.
Fastboot mode is working but not really nice. Not even the mitu appears, no the display is black (or doesn't show anything.. The device's display is on).
My Mi A2 is recognized by the computer so I considered to flash the stock rom with fastboot.
I thought it would work, but in the mi flash programm i got the erorr: flash devcfg_a error.
Now i can't switch my mobile off, because when I'm holding the power button, it restarts and restarts and restarts...
I know i am stupid and maybe have done something wrong, but i would be soooo happy to get some help
Thank you so much!
Fastboot flashing unlock_critical
(It will wipe /data)
then flash with mi flash
But before doing that, try just flashing stock boot
Fastboot flash boot_a boot.img
Or boot_b if that's your active slot
Nebrassy said:
Fastboot flashing unlock_critical
(It will wipe /data)
then flash with mi flash
But before doing that, try just flashing stock boot
Fastboot flash boot_a boot.img
Or boot_b if that's your active slot
Click to expand...
Click to collapse
Thank you very much for your answer.
Unfortunately i have wiped everything in twrp before (when it worked) so there's nothing stored on the device.
When i type in critical unlock only a big list of commands appears which can be used.... ?
MardukPVP said:
Thank you very much for your answer.
Unfortunately i have wiped everything in twrp before (when it worked) so there's nothing stored on the device.
When i type in critical unlock only a big list of commands appears which can be used.... ?
Click to expand...
Click to collapse
what's the exact command you used?
Nebrassy said:
what's the exact command you used?
Click to expand...
Click to collapse
In minimal ADB and Fastboot I used: fastboot flashing unlock_critical
{
"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"
}
MardukPVP said:
In minimal ADB and Fastboot I used: fastboot flashing unlock_critical
Click to expand...
Click to collapse
Don't use minimal adb, use this https://developer.android.com/studio/releases/platform-tools
Okay, i've got no words. You saved my life. It worked. Thank you sooo much !!!
Not receiving updates
I need help i recently flashed fastboot rom on mi A2 Oct patch firmware.I can't receive any Ota Updates,How to get in phone on original state? With working online updates in settings PLEASE HELP!!:crying::crying:
jdivya524 said:
I need help i recently flashed fastboot rom on mi A2 Oct patch firmware.I can't receive any Ota Updates,How to get in phone on original state? With working online updates in settings PLEASE HELP!!:crying::crying:
Click to expand...
Click to collapse
So you have flashed this rom https://en.miui.com/download-353.html ?
Nebrassy said:
Fastboot flashing unlock_critical
(It will wipe /data)
then flash with mi flash
But before doing that, try just flashing stock boot
Fastboot flash boot_a boot.img
I promised I would create an account here just to thank you if your method worked!
After doing something dumb (I typed some wrong commands I think) my A2 got into the infinite reboot, never got out of the android logo, I tried everything and literally thought I lost my phone for good ;n;
I downloaded "jasmine_global_images_V10.0.2.0.PDIMIFJ_20181206.0000.00_9.0_02b8deeb6d.tar" and flashed that on miflash and watched my phone come back from the dead like frankestein or something. He's doing great and is in top shape, thanks to your advice! THANK YOU VERY MUCH! Hope you have a wonderful 2019!
Click to expand...
Click to collapse
MardukPVP said:
Okay, i've got no words. You saved my life. It worked. Thank you sooo much !!!
Click to expand...
Click to collapse
Hey Did Your smartphone works fine I mean did you get every Updates from Stock
error
Nebrassy said:
Fastboot flashing unlock_critical
(It will wipe /data)
then flash with mi flash
But before doing that, try just flashing stock boot
Fastboot flash boot_a boot.img
Or boot_b if that's your active slot
Click to expand...
Click to collapse
When i try it shows the error remote error flashing partition , how to solve that help please my email is [email protected] , replay there if possible thank you
[email protected] said:
When i try it shows the error remote error flashing partition , how to solve that help please my email is [email protected] , replay there if possible thank you
Click to expand...
Click to collapse
Try flashing through edl mode
I think I bricked my mi a2 please help me.
MardukPVP said:
Thank you very much for your answer.
Unfortunately i have wiped everything in twrp before (when it worked) so there's nothing stored on the device.
When i type in critical unlock only a big list of commands appears which can be used....
Click to expand...
Click to collapse
I have a mi a2 and it's stuck on Android logo screen. It has an unlocked bootloader and maybe it's rooted too. While I thought I rooted it.. It went into bootlooping.. Only fastboot and android logo can be accessed. I tried flashing it with stock rom but mi flash tool goes like 3500+ sec. Please tell how to fix this.
same issu
okay i hav the same problem, can't fix it
whenever i try to use any command in cmd during the device is in fastboot mode, my phone screen go to the black, and it says in a liitle, "press any key to shutdown"
is there any solution? it will me life saving.
anikapproe said:
...whenever i try to use any command in cmd during the device is in fastboot mode, my phone screen go to the black, and it says in a liitle, "press any key to shutdown" is there any solution?
Click to expand...
Click to collapse
I have the same issue in PC I'm writing this from (in USB3.1 Gen2 and Gen 1 ports, and even in USB 2.0 ports), but have no problems in 2 other PCs I currently have access to.
For non-universal solution with my current PC please see more info in my answer in neighbouring thread: https://forum.xda-developers.com/showpost.php?p=81693759&postcount=28.
Hello, my phone is stuck in Fastboot mode (rebooting does not work, it will always boot into fastboot mode) so I just followed this guide to flash a new ROM: https://c.mi.com/oc/miuidownload/detail?guide=2
But I am wondering, why the installation is still going on after over 10min. - What is wrong?
{
"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"
}
After trying it again:
It is just stuck forever and I do not know why, I do not get out of fast boot mode and I really do not know what to do now.
Like doesn't the "status" say something what is wrong here? I cannot identefy it, but has anyone enough experience with it and maybe experienced my issue already?
Try flash non-official rom via recovery (twrp). After successful flash, launch system. Then, try flash latest stable via fastboot (do not use FLASH-AND-LOCK, use it only after successfully flashing like flash, check if everything is ok and then flash it again and lock).
I cannot enter recovery, I am stuck in a Fast boot loop. The phone won't let me get into recovery mode.
So flash TWRP in fastboot mode.
And you could try to flash another ROM because "echo Missmatching image and device"
The name of your directory path should not include any space. Replace the spaces with underscores, dashes or just remove them.
From your screenshot, you selected clean all and lock. Try unlocking the bootloader again.
Sent from my MI 9 using Tapatalk
Thanks, but the thing is I fixed all those things already as my last picture shows: https://img.xda-cdn.com/5kNbM-6ZvzA8Jvc_Fc-qUwGIG-Q=/https://i.imgur.com/ZOhtier.png
@Tomcar do you mean 'fastboot flash recovery name.img' ? That does not work, it still boots me into fastboot mode everytime I try to get into recovery mode.
Shure, because you are locked again
I fixed the problem. I just downloaded a newer version of Mi Flash and now I have the newest version installed. So the plan is to install a new custom rom now.
Why is wipe system not recommended to do?
And do I have to "wipe internal storage"?
I really do not understand.. Now as I sad above I have the newest version installed and the phone is unlocked too!
When I go into fastboot mode and do "fastboot flash recovery twrp.img" it works, but when I boot into recovery mode with volume UP and power button the old recovery is still there.
What am I missing out here?
hallohallo222 said:
I really do not understand.. Now as I sad above I have the newest version installed and the phone is unlocked too!
When I go into fastboot mode and do "fastboot flash recovery twrp.img" it works, but when I boot into recovery mode with volume UP and power button the old recovery is still there.
What am I missing out here?
Click to expand...
Click to collapse
Try after "fastboot flash recovery twrp.img"
"fastboot boot recovery twrp.img"
Once you do this, the recovery should stay permanently there.
Dont know why, but this was working for me.
(I hate this phone, too many strange things with it)
On my Mi 9, what I did to make TWRP stick was to press vol up + power right after flashing the recovery, to boot into TWRP.
Sent from my MI 9 using Tapatalk
sangbuana said:
On my Mi 9, what I did to make TWRP stick was to press vol up + power right after flashing the recovery, to boot into TWRP.
Sent from my MI 9 using Tapatalk
Click to expand...
Click to collapse
You my friend are a genius, thanks for the help. That worked!
abocksberger said:
Try after "fastboot flash recovery twrp.img"
"fastboot boot recovery twrp.img"
Once you do this, the recovery should stay permanently there.
Dont know why, but this was working for me.
(I hate this phone, too many strange things with it)
Click to expand...
Click to collapse
Thanks, this did not work somehow the boot command did not get recognized: "C:\Mini ADB and Fastboot>fastboot boot recovery twrp.img
fastboot: error: cannot load 'recovery': No such file or directory"
I was facing the same issue. I stopped the flashing. Copied manually the recovery.img file that came with the flash tool, and flashed the original recovery manually, cause i had it on a customer recovery. Then i tried again, it showed a more meaningful error, basically the path of the folder we're flashing can't have spaces. moved the folder under C: and tried again.. all worked!!
As the title suggests, I decided to flash Lineage OS onto my old Huawei P9 phone. I unlocked the bootloader, which was a mess but I did indeed achieve that goal.
However, things screeched into a halt as I found out that my specific model of P9 does not support SU or rooting. So the only way I can install TWRP is by running the
Code:
adb reboot bootloader
flashboot flash recovery_ramdisk twrp.img
Things got kinda weird when I tried to boot into recovery mode. I've tried all the ways, from using all kinds of key combinations to googling software solutions, sadly all my efforts were in vain. However, I can now boot into recovery mode consistently with the classic "volume + and power button" key combo. The problem I run into is that everytime I boot into it, I get the error 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"
}
What can I do? all the other solutions on Google say that I need to root to use the software solutions so I'm stuck in this weird circular logic loop. So any suggestions?
Running EMUI 8.0.0.552(C01)
Model EVA-TL00
Cpu: Hisilicon Kirin 955
Kernel version 4.4.23
Catnip202X said:
As the title suggests, I decided to flash Lineage OS onto my old Huawei P9 phone. I unlocked the bootloader, which was a mess but I did indeed achieve that goal.
However, things screeched into a halt as I found out that my specific model of P9 does not support SU or rooting. So the only way I can install TWRP is by running the
Code:
adb reboot bootloader
flashboot flash recovery_ramdisk twrp.img
Things got kinda weird when I tried to boot into recovery mode. I've tried all the ways, from using all kinds of key combinations to googling software solutions, sadly all my efforts were in vain. However, I can now boot into recovery mode consistently with the classic "volume + and power button" key combo. The problem I run into is that everytime I boot into it, I get the error screenView attachment 5281583
What can I do? all the other solutions on Google say that I need to root to use the software solutions so I'm stuck in this weird circular logic loop. So any suggestions?
Running EMUI 8.0.0.552(C01)
Model EVA-TL00
Cpu: Hisilicon Kirin 955
Kernel version 4.4.23
Click to expand...
Click to collapse
TWRP must be flashed with the command:
fastboot flash recovery_ramdisk ...
After flashing, first thing must be rebooting to TWRP by key conbo - it's always that same trick for Huawei phones
And btw, better ask inside the P9 LOS thread, to get attention and help
zgfg said:
TWRP must be flashed with the command:
fastboot flash recovery ...
After flashing, first thing must be rebooting to TWRP by key conbo - it's always that same trick for Huawei phones
And btw, better ask inside the P9 LOS thread, to get attention and help
Click to expand...
Click to collapse
I've tried
Code:
fastboot flash recovery twrp.img
This doesn't work as I've learned that the correct partition name is recovery_ramdisk. Flashing the recovery gives the error.
Catnip202X said:
I've tried
Code:
fastboot flash recovery twrp.img
This doesn't work as I've learned that the correct partition name is recovery_ramdisk. Flashing the recovery gives the error.
Click to expand...
Click to collapse
Yes, sorry, you are right, typo.
But I wanted to point that you must use fastboot flash command (not FLASHBOOT or whatever you used in your post #1)
And that you MUST reboot to TWRP as the first thing after flashing it - otherwise (as you claimed), stock recovery will overwrite the TWRP you flashed
Hence, prepare you fingers for the key-combo, type fastboot reboot, disconnect USB and make sure you properly keep pressing Vol+ until it boots to TWRP. Then you can safely reboot to the system
But also READ the P9 LOS thread - it clearly describes that LOS must bi flashed from fastboot, not from TWRP and it actually asks users not to use TWRP
See here and better ask there to get the answers directly from developer:
[ROM][Treble][microG]LineageOS 16.0 for HUAWEI P9
This thread is dedicated to provide Lineage-OS 16.0 builds with microG included for the HUAWEI P9 with current security patches. It is a treble build, therefore it could also work on other devices, but I haven't tested. And yes, the camera...
forum.xda-developers.com
zgfg said:
And that you MUST reboot to TWRP as the first thing after flashing it - otherwise (as you claimed), stock recovery will overwrite the TWRP you flashed
Hence, prepare you fingers for the key-combo, type fastboot reboot, disconnect USB and make sure you properly keep pressing Vol+ until it boots to TWRP. Then you can safely reboot to the system
Click to expand...
Click to collapse
I have indeed tried this route, but as I have stated before, trying to boot into recovery mode right after flashing TWRP and pressing key combo still boots me into the error screen where it says that I need to update something. On the bottom of the screen will also show errors such as Function11 not found and error 2 no image etc. I’ll try to replicate it and send you a picture of the error screen when I get home from work tonight.
Hello,
it's been about two years since I installed CalyxOs on my A2 and I don't want to do anything stupid.
I would like to ask you for your advice to go back to the original AndroidOne ROM and then test other ROMs like /e/ OS or GrapheneOS for example.
I'm on linux, a Manjaro, and no worries with the terminal unless you have an application at hand.
Knowing that the current ROM is a CalyxOs under Android 11, I share with you the data in my possession.
Thanks in advance
{
"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"
}
Well, if you are running with locked bootloader, you have to unlock it again through fastboot.
Toggle oem unlock in the developer options and then fastboot oem unlock.
Then you can boot twrp or Lineage recovery, fastboot flash boot <recovery_filename>.img to wipe your device for each slot.
I personally moved away from CalyxOS too and went back to LineageOS 18.1.
I also updated the firmware to the latest release firmware_jasmine_sprout_V11.0.28.0 cause that version of CalyxOS uses a old firmware that allowed to lock the bootloader, use twrp to flash the update package firmware and then move back to the recovery you want.
About the OS I see you like /e/ is available, for Graphene they support only pixels so you are out of luck I guess.
Hello,
So according to you, being on android 11 I can reinstall directly from a recovery such as lineage-18.1-20220507-nightly-jasmine_sprout-signed.zip
Apart from the firmware, no other manipulations or downgrade is necessary?
Hi @Reynald0,
I haven't been back for a while and I'm still using my xiaomi A2 under CalyxOs.
I have a problem, my A2 is no longer recognized in USB, whether under Linux, Windows, having tried many different cables. Reset, etc...
The A2 loads 4 seconds then disconnects, but it is not discovered by the PC.
So I am with an A2 under CalyxOs, without TWRP installed, without possibility to connect it to a PC.
Will one of you be able to help me to put it back to its original stock state?
romhtk said:
Hi @Reynald0,
I haven't been back for a while and I'm still using my xiaomi A2 under CalyxOs.
I have a problem, my A2 is no longer recognized in USB, whether under Linux, Windows, having tried many different cables. Reset, etc...
The A2 loads 4 seconds then disconnects, but it is not discovered by the PC.
So I am with an A2 under CalyxOs, without TWRP installed, without possibility to connect it to a PC.
Will one of you be able to help me to put it back to its original stock state?
Click to expand...
Click to collapse
Well, you need fastboot to perform a lot of operations.
Those 4 seconds make me think of Magisk, or in general that indicates a boot problem, red color indicator.
You can forget TWRP from now on with LineageOS 18.1 and LineageOS 20 we use Lineage recovery.
If you are sure your device isn't detected using fastboot devices when you are into fastboot mode then there is not much we can do, if you used Magisk you will have to deal with changing slots and temporary flash the recovery as a boot image.
I don't recall exactly, but the first thing is to unlock the bootloader again, then upgrade the firmware cause CalyxOS used an old one, and then you should be good.
If you plan to use Magisk and Lineage recovery the most important things you will have to deal are:
Switching between slots,
fastboot --set-active=a , set the a slot as active
fastboot --set-active=b , set the b slot as active
fastboot flash boot boot.img && fastboot reboot , where boot.img is the Lineage recovery
Reynald0 said:
Well, you need fastboot to perform a lot of operations.
Those 4 seconds make me think of Magisk, or in general that indicates a boot problem, red color indicator.
You can forget TWRP from now on with LineageOS 18.1 and LineageOS 20 we use Lineage recovery.
If you are sure your device isn't detected using fastboot devices when you are into fastboot mode then there is not much we can do, if you used Magisk you will have to deal with changing slots and temporary flash the recovery as a boot image.
I don't recall exactly, but the first thing is to unlock the bootloader again, then upgrade the firmware cause CalyxOS used an old one, and then you should be good.
If you plan to use Magisk and Lineage recovery the most important things you will have to deal are:
Switching between slots,
fastboot --set-active=a , set the a slot as active
fastboot --set-active=b , set the b slot as active
fastboot flash boot boot.img && fastboot reboot , where boot.img is the Lineage recovery
Click to expand...
Click to collapse
Thank you very much for your answer.
I think I misspoke, if I understood your message correctly. The phone starts up correctly, CalyxOs works perfectly well, but I can't charge it, nor access the files by connecting it to a pc. Magisk is not installed
I just rebooted in fastboot mode and with an I just rebooted in fastboot mode and with an
Code:
adb devices
, the tel is not detected.
Can you tell me what is DSU?
romhtk said:
I just rebooted in fastboot mode and with an I just rebooted in fastboot mode and with an
Code:
adb devices
, the tel is not detected.
Can you tell me what is DSU?
Click to expand...
Click to collapse
Sorry, I have no experience with GSIs, so I can't help you with them right now.
I will try them in the future if there are no alternatives ^o^
I went to a computer specialist, tested new cables, etc... nothing to do.
adb/fastboot via wifi ?
How complicated is it?
Reynald0 said:
Sorry, I have no experience with GSIs, so I can't help you with them right now.
I will try them in the future if there are no alternatives ^o^
Click to expand...
Click to collapse
HELP!
I installed platform-tools_r33.0.2-windows and UniversalAdbDriverSetup, now i'm trying to flash TWRP on the XA2 Phone by using this cmd command:
adb devices
- daemon not running, starting now at xxx
adb flash recovery twrp.img
- waiting for any device
What am i doing wrong?? Please help!!
{
"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"
}
Boot phone in fastboot mode
Execute "fastboot flash recovery twrp.img"
LR7875 said:
Boot phone in fastboot mode
Execute "fastboot flash recovery twrp.img"
Click to expand...
Click to collapse
How? Im pressing volume up and then connecting the phone to the pc, then i see a blue light. Is this fastboot mode? Thats what im already doing for 3 hours...
Yeah just did it again... volumeup+connect phone to pc, blue light appears on phone (fastboot mode i asume).
on pc in cmd i type adb devices, it starts the daemon.
then i type "fasboot flash recovery twrp.img"
result in cmd: "waiting for any device"
Wtf?
I swear this is so cancer can't handle this ****, the F is wrong with sony? This phone is buggy AF im trying to insall TWRP for like 4 hours now, this is a ****ing joke. What a waste of time.
Try the 15 seconds adb and fastboot driver if you haven't already
LR7875 said:
Try the 15 seconds adb and fastboot driver if you haven't already
Click to expand...
Click to collapse
This? https://forum.xda-developers.com/t/...vers-15-seconds-adb-installer-v1-4-3.2588979/
I doubt it will be any different from the platformtools adb? How could this help?
LR7875 said:
Try the 15 seconds adb and fastboot driver if you haven't already
Click to expand...
Click to collapse
You mean minimal adb ? or can you provide a link?
Connect the phone in fastboot mode (LED = blue) and open the device manager. Do you see the phone under "Other Devices" or "Android" with an exclamation mark? Then you need an ADB/bootloader interface driver. Get this for example:
https://developer.sony.com/file/download/xperia-xz2-driver/
(Yes, XZ2! There is no official XA2 driver)
Unzip it somewhere and force install the driver:
Right click on the device manager entry from above, "Update driver", "Browse my computer...", "Let me pick...", "List/show all...", "Have disk...", browse to the folder from above, open the selected .inf file and install.
Fastboot should work now. At least that's how I got it to work on a new PC.
BTW, just use "fastboot devices" to check whether it works. If your device doesn't appear, you don't need to try other fastboot commands - it won't work.
I have this problem, when installing twrp to my Sony Xperia XA2 (H3123), I am trying to install several versions of Twrp, for example: twrp-3.2.2-0-pioneer.img, twrp-3.7.0_9-0 -pioneer.img, my Sony is on Android 9
Carljaynp03 said:
I have this problem, when installing twrp to my Sony Xperia XA2 (H3123), I am trying to install several versions of Twrp, for example: twrp-3.2.2-0-pioneer.img, twrp-3.7.0_9-0 -pioneer.img, my Sony is on Android 9
Click to expand...
Click to collapse
Did you unlock the bootloader ?
Carljaynp03 said:
View attachment 5734133
Click to expand...
Click to collapse
I agree with faraway, if i remember correctly when i had this issue i didn't unlock the bootloader.
I typed a specific number in the phone dial app and it said that the bootloader is unlocked, however there is another step you need to take that i had overlooked, you need a bootloader unlock code.
The code is free, not like with chinese spyware huawai they want your money for the code...
Unlock Bootloader - Open Devices - Sony Developer World
developer.sony.com
https://developer.sony.com/develop/open-devices/get-started/unlock-bootloader/how-to-unlock-bootloader/#tutorial-step-4
and use one of these commands in cmd/adb
fastboot flashing unlock
fastboot oem unlock
Carljaynp03 said:
View attachment 5734133
Click to expand...
Click to collapse
What is your end goal? To flash a custom ROM like LineageOS? Then you can temporarily flash a recovery image to the boot partition:
fastboot flash boot <recovery_filename>.img
You don't really need TWRP for this, just use the latest official LOS Recovery:
https://download.lineageos.org/pioneer
Also see: https://wiki.lineageos.org/devices/pioneer/install
Or do you want to "permanently" install TWRP on an existing system? Then you need to directly boot into TWRP and install it from its GUI:
fastboot boot <twrp_filename>.img
See: https://twrp.me/sony/sonyxperiaxa2.html
I haven't tried the latter on the XA2 yet though and don't know how permanent that installation really is. It maybe gone after an OTA update.
irgendwer2 said:
What is your end goal? To flash a custom ROM like LineageOS? Then you can temporarily flash a recovery image to the boot partition:
fastboot flash boot <recovery_filename>.img
You don't really need TWRP for this, just use the latest official LOS Recovery:
https://download.lineageos.org/pioneer
Also see: https://wiki.lineageos.org/devices/pioneer/install
Or do you want to "permanently" install TWRP on an existing system? Then you need to directly boot into TWRP and install it from its GUI:
fastboot boot <twrp_filename>.img
See: https://twrp.me/sony/sonyxperiaxa2.html
I haven't tried the latter on the XA2 yet though and don't know how permanent that installation really is. It maybe gone after an OTA update.
Click to expand...
Click to collapse
Booting a temprary image did not work when i tried it, most likely because the bootloader wasn't unlock.
Privacydroid said:
Booting a temprary image did not work when i tried it, most likely because the bootloader wasn't unlock.
Click to expand...
Click to collapse
Independent from the bootloader status: you can't flash an image directly to the recovery partition on the XA2/Pioneer (like he tried, see screenshot) because such a dedicated partition doesn't exist on this and other A/B devices. Instead the recovery is built into the boot image.
That's why you have to use fastboot flash boot instead of recovery.
irgendwer2 said:
Independent from the bootloader status: you can't flash an image directly to the recovery partition on the XA2/Pioneer (like he tried, see screenshot) because such a dedicated partition doesn't exist on this and other A/B devices. Instead the recovery is built into the boot image.
That's why you have to use fastboot flash boot instead of recovery.
Click to expand...
Click to collapse
follow the next steps you mentioned use: fastboot flash boot recovery from LineageOS, and my phone went into a constant boot shutdown and restart, then this message appeared
and the bootloader is open
Shutdown the phone after flashing the recovery image (it doesn't seem like you did that). Then hold Volume Down + Power to boot into recovery.
irgendwer2 said:
Independent from the bootloader status: you can't flash an image directly to the recovery partition on the XA2/Pioneer (like he tried, see screenshot) because such a dedicated partition doesn't exist on this and other A/B devices. Instead the recovery is built into the boot image.
That's why you have to use fastboot flash boot instead of recovery.
Click to expand...
Click to collapse
I get that the recovery is only for a temporary boot, when i tried it, it didn't work but i can't remember what the error was.