Hey! long story short. My phone wont boot slot B (witch is the location my primary Os is installed.) it reboots itself immediately after booting and switches back to slot A where it starts to load H2 OS, but in the end it stucks at loading screen forever.
Full details here:
It started when i decided to update the OS to android 10. So first i wanted to update the TWRP (3.2.3-1 is the older one, and i needed to install: 3.3.1-2).
I downloaded the latest update, backed up the recovery (all of it, just in case).
Then, keep in mind, i by mistake installed the same installer as i already had! I by mistake installed the same 3.2.3-1 version, from an installer i had earlier when i rooted the phone in the past.
In theory, nothing could go wrong. But there you have it, it stuck on TWRP. i just could not boot to system.
so i decided to restore from TWRP backup. Now the problem only worsened!
First, not just that the system doesn't loads (apparently, it is installed in slot B), it is forcing to load to slot A, every time i boot the phone. And it loads H2 OS, well not really loads, because it is loading for 20 minutes now and nothing happens.
Second, slot A is "only for reading" and everything is encrypted, so i can pretty much can't do a thing there, including restoring from backup again.
Third, every time i try to switch to slot B, in the recovery it switches, but as soon as i reboot (doesn't matter if i reboot to recovery, fastboot or system) the phone just restarts immediately after boot, apparently switches back to slot A in background, and tries to load H2 OS again. an i know that because i try to go into recovery after that and i see it is in slot A once again.
Click to expand...
Click to collapse
please help me with it!:crying:
Thanks!
The issue might be that official TWRP does not support Android 10 yet. You probably needed unofficial mauronofrio twrp. However, I am not sure if there is a clean way out of this situation. Maybe if you flash the right twrp it will just boot?
What do you mean "everything is encrypted and I cannot do much there"? Data is encrypted with your password, isn't it?
[email protected] said:
The issue might be that official TWRP does not support Android 10 yet. You probably needed unofficial mauronofrio twrp. However, I am not sure if there is a clean way out of this situation. Maybe if you flash the right twrp it will just boot?
What do you mean "everything is encrypted and I cannot do much there"? Data is encrypted with your password, isn't it?
Click to expand...
Click to collapse
how to properly flash the twrp?
and for your question.
the thing is, it doesn't gives me a password. it automatically gets into here:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
fenixsword said:
how to properly flash the twrp?
and for your question.
the thing is, it doesn't gives me a password. it automatically gets into here:
Click to expand...
Click to collapse
If you click "Read Only" doesn't it ask you the password then? I swear I have done this today when recovering from a poor magisk module...
I am actually not sure if you want to keep it read only or not, but I think no matter which option you select it promts you for a password
EDIT: Sorry, got distracted by the picture and missed the question. I looked at some threads and the process of upgrading seems to be potentially complicated if you have Magisk. Read more here. And maybe here.
Maybe if you boot into bootloader, run "fastboot set_active a" and then "fastboot flash boot_a <recovery_filename>.img" and everything will just work. Maybe it won't. Replace "a" with "b" in both commands if you are trying to boot into b.
TWRP 3.3.1-17 Q Unofficial by mauronofrio
[email protected] said:
If you click "Read Only" doesn't it ask you the password then? I swear I have done this today when recovering from a poor magisk module...
I am actually not sure if you want to keep it read only or not, but I think no matter which option you select it promts you for a password
Click to expand...
Click to collapse
and yet again, it doesn't asks for pasword, and wvwry folder i look to restore, looks like this:
meaning it is encrypted.
is there a way to reinstall TWRP from PC using command prompt, using adb or something like that?
fenixsword said:
and yet again, it doesn't asks for pasword, and wvwry folder i look to restore, looks like this:
meaning it is encrypted.
is there a way to reinstall TWRP from PC using command prompt, using adb or something like that?
Click to expand...
Click to collapse
Hm, interesting.
IF YOUR DATA IS ON THE LINE, DO NOT LISTEN TO ME. I do not know how twrp backup/restore works. Maybe wait for someone more knowledgeable to come in if you are worried about the data. But if you are sure that everything is safe on your pc somewhere, feel free.
Yes, please see my edit. You can do it through fastboot. You can use the respective section here for inspiration.
Did you had the password block on phone?
Just answer me, do u know the decrypt data? Its the password which u use to unlock phone
whatsinside said:
Did you had the password block on phone?
Just answer me, do u know the decrypt data? Its the password which u use to unlock phone
Click to expand...
Click to collapse
i'll answer detailed.. At start, while TWRP was working and it could launch slot B (it's where my OS initially was installed), it asked me for the phones password.
After backing up TWRP and trying to update it, it failed to launch OS, so i tried to restore from backup.
After restoring, it just couldn't start slot B at all (OS nor recovery) and it switched to slot A.
in slot A though, it didn't asks me for password, and encrypted data right away.
Now at the moment,after trying to flash TWRP to both slots, slot A don't launch recovery, the phone seems like it's connected to PC and works but screen is black, and the problem with slot B stays the same (switches right away to slot A)
you really can help with that? :silly:
fenixsword said:
i'll answer detailed.. At start, while TWRP was working and it could launch slot B (it's where my OS initially was installed), it asked me for the phones password.
After backing up TWRP and trying to update it, it failed to launch OS, so i tried to restore from backup.
After restoring, it just couldn't start slot B at all (OS nor recovery) and it switched to slot A.
in slot A though, it didn't asks me for password, and encrypted data right away.
Now at the moment,after trying to flash TWRP to both slots, slot A don't launch recovery, the phone seems like it's connected to PC and works but screen is black, and the problem with slot B stays the same (switches right away to slot A)
you really can help with that? :silly:
Click to expand...
Click to collapse
Restore from twrp is broken. Everything on slot b is gone but your data is there. You must install the same oos version you had on slot b to fix slot b. Then you boot into and do first time setup. Reboot to twrp and restore data only.
Try to enter settings and terminal, and type "decrypt [password]" or "twrp decrypt [password]
MrSteelX said:
Restore from twrp is broken. Everything on slot b is gone but your data is there. You must install the same oos version you had on slot b to fix slot b. Then you boot into and do first time setup. Reboot to twrp and restore data only.
Click to expand...
Click to collapse
ok.. i get what i need to do.. is there a guide on how to do so properly, so i wont mess up things even more? lol
The easy way would be if you have otg cable to jump drive with stock oos, twrp, and root. If not, then adb in twrp is your friend.
MrSteelX said:
The easy way would be if you have otg cable to jump drive with stock oos, twrp, and root. If not, then adb in twrp is your friend.
Click to expand...
Click to collapse
so i do have OTG cable. But i need a more vivid explanation on how to install stock os on it. or how to use adb in TWRP, if TWRP doesn't load on any slot.
The pictures look like you still have twrp. From twrp, you install stock rom twrp. Reboot recovery. Root and boot into system. The jump drive is because it will not be encrypted in twrp.
MrSteelX said:
The pictures look like you still have twrp. From twrp, you install stock rom twrp. Reboot recovery. Root and boot into system. The jump drive is because it will not be encrypted in twrp.
Click to expand...
Click to collapse
that's the problem though.. TWRP is gone, that's what i tried to tell you
first i need a way to flash recovery, then to do what you are suggesting.
You put phone in fastboot mode. The fastboot boot twrp.Img
https://forum.xda-developers.com/oneplus-6/how-to/rom-stock-fastboot-roms-oneplus-6-t3796665 should help
MrSteelX said:
You put phone in fastboot mode. The fastboot boot twrp.Img
https://forum.xda-developers.com/oneplus-6/how-to/rom-stock-fastboot-roms-oneplus-6-t3796665 should help
Click to expand...
Click to collapse
ok, i'll try it and update with the results, Thanks!
do you think i will be able to recover all the data from the phone?
fenixsword said:
ok, i'll try it and update with the results, Thanks!
do you think i will be able to recover all the data from the phone?
Click to expand...
Click to collapse
maybe?
Related
DO NOT FORMAT YOUR MICRO SDCARD INSIDE TWRP RECOWERY
WARNING: If you want tho use /data and internal sdcard first have to format data in stock recovery This will wipe your internal storage, and factory reset your phone!
encryption is not supported yet
To flash this img to your phone use fastboot
Code:
fastboot flash recovery twrp-x.x.x-x-h840.img
+new test build with encryption support
source code https://github.com/synescu/twrp_lg_h840
1.Unlocking the bootloader.
1.1Get the latest drivers: ( http://tool.lime.gdms.lge.com/dn/downloader.dev?fileKey=UW00120120425 )
1.2Get ADB fastboot. If you hate installing huge files for just a few commands, you have 3 options:
-MINIMAL ADB and fastboot: (https://forum.xda-developers.com/showthread.php?t=2317790 )
-15 seconds ADB Installer v1.4.3: (https://forum.xda-developers.com/showthread.php?t=2588979 )
-SDK Platform-Tools coming directly from google: (https://developer.android.com/studio/releases/platform-tools.html )
I personally went with the “15 seconds ADB Installer v1.4.3”, because it installs also a Google driver, which might, or might have not helped out in the process to follow.
1.3Follow the instructions at the official LG unlocking page ( https://developer.lge.com/resource/mobile/RetrieveBootloader.dev ), just keep in mind that after step 1.2 you have adb ready to go @ your main drive C:\adb. You go to that folder shift + right click and open a command prompt at that location, the rest is trivial.
2.Updating to the latest official stock android.
2.1Get the latest kdz from: (https://lg-firmwares.com/lg-h840-firmwares/ ). As far as I know you can go for any of those firmwares, but it is advisable to use one from your region (Europe, South America, Middle East). As mentioned above my LG G5 H840 is the newest European model, totally unbranded. So I took the 20c for Spain. This is as high as you can get at present moment.
2.2 Flash with LGUP 1.14 and UPPERCUT 1.0.0, both available at: (http://downloads.codefi.re/autoprime/LG/LG_G5 )
2.3 Reboot and do a quick setup. I recommend to have your sim card, SD card out at this moment, do not connect to wireless networks, all of this you will have plenty of time to do later, besides whatever you set at this point will be lost in the next step.
3.Get TWRP and root
3.1TWRP. As a courtesy of synescu, we have 2 versions: a regular one and such with encryption support. It took me long to realize that only the one with encryption would work on a latest H840 installed with v20c. So I guess if you have an old phone and possibly firmware 10a/b/c/d, than you can try “twrp3.1.1-0-h840.img”, otherwise go straight to “twrp_encryption-h840.img”. If you use the one without encryption support you will find no way to root the phone, because it can not see the SD card, or any USB flash attached and also if you connect the phone to a PC with MTP mode, or any other mode you won’t be able to browse both (internal and external) memories on that phone.
3.1.1Put on a SD card following files: 1) latest stable SuperSU 2.79 2) no-verity-opt-encrypt.zip from here (https://build.nethunter.com/android-tools/no-verity-opt-encrypt/no-verity-opt-encrypt-5.1.zip ) and just in case although not mandatory “twrp_encryption-h840.img”.
3.1.2Put in the C:\adb folder the “twrp_encryption-h840.img” and the stock recovery from here (https://forum.xda-developers.com/attachment.php?attachmentid=4149809&d=1494791791 ). The stock recovery is necessary in case you make a mistake and have to do a factory reset.
3.1.3Turn off the phone.
3.1.4Boot into stock recovery (holding volume down + power, at LG logo releasing power shortly and than pushing power again).
As a side note here, after I unlocked the bootloader I’ve got that annoying message on start-up that the phone is untrusted. With G4 H815 it was a small message in the upper corner, this time around it is a huge message in the middle of the screen. LG, for the love of god! After all the playing, I have now also a message screen, which I call “Options Menu”, it shows right after the nagging untrusted message. Although esthetically ugly, I have an easy way to go to recovery and fastboot in each and every regular power on, or restart. As said the Options Menu is showing up for 5 sec after the untrusted nagger. If you click the volume up, or down you get to the options (Power off, Restart, Recovery, Fastboot ), otherwise after 5 sec the phone would boot normally. I don’t know if this is the expected behavior of the phone, or did I trigger it somehow, but now I don’t have to use the combo buttons for anything.
Back from the side note. The new stock recovery is a white screen with 2 options for No and Yes. Go for YES and than YES again, after both YES the phone will be factory reset and will reboot. Do not allow it to boot though, because the userdata will be encrypted at this point and you will have to repeat the reset again. Use the combo buttons for recovery, which will bring you to the “Options Menu”, or Volume up and plug in the phone into the PC. Yet again there is hardly any time so maybe plugin in won’t be fast enough, so just keep pressed the combo buttons, also change with volume up and power, or remove the battery and start again. In any event do not let it boot until it brings you to the “Options Menu”
3.1.5In the Options Menu pick fastboot and plug the phone to the PC
3.1.6Open command prompt in adb and flash TWRP ( fastboot flash recovery twrp_encryption-h840.img ) you might be ok also to do factory reset from adb with this command (fastboot –w ), but unfortunately I forgot already if I did it, when it finally worked for me
3.1.7Disconnect from the PC and pull the battery out, or just keep the buttons combo pressed. It is possible that you see the old stock recovery (white screen YES/NO), which might have stayed somehow in memory. Do not perform further resets, just keep pressing the button combo and it will reboot eventually to the Options Menu.
3.1.8There you go 3 times volume down and power to pick recovery. Follows a reboot of the bootloader, nagging screens, but eventually it loads TWRP.
3.2Root.
3.2.1For some reason even after the factory reset, the data partition keeps an encrypted flag. So you can not write to it. Stock recovery should have reset it to non-encrypted, but it does not do it correctly, I guess. Therefore you go to Wipe, pick only the Data check box and go to change format in the bottom. Change the format to FAT and than back to EXT4
3.2.2Go to the SD card and flash no-verity-opt-encrypt.zip and SuperSu. Yes I know, that SuperSu is supposed to install also no-verity, but I like to flash both just in case.
3.2.3Do NOT wipe anything in TWRP at this point. Reboot only!!!!! Once the phone has booted in v20c you can go back to TWRP, Wipe and make all the backups you like
Thanks to @svetloslav for this complex post
Thanks a lot.
Can't wait to flash!!
YESS finally we have root on the SE thank you very much man
Hi all. When I try to flash recovery, fastboot give me that message:
target reported max download size of 536870912 bytes
sending 'recovery' (15089 KB)...
OKAY [ 0.490s]
writing 'recovery'...
FAILED (remote: image is not a boot image)
Any suggestion? Thanks
Solved: I had not extracted the .img from the .tar archive
synescu said:
For now external sd card is mounted as internal. De only way you can flash something for now When I would have more time I will try to fix this and upload the source to github. I rooted the phone and installed the supersu and no verity zip
source code https://github.com/synescu/twrp_lg_h840
Click to expand...
Click to collapse
Thanks a lot!
just a few information...
Is this build on android 6, 7 or 7.1 three?
Is encryption supported?
bob8x said:
Thanks a lot!
just a few information...
Is this build on android 6, 7 or 7.1 three?
Is encryption supported?
Click to expand...
Click to collapse
I'm booting this vith android 7.0
6.0 must boot just fine. didn't tried encryption but I'm pretty sure that doesn't work
Build compiled from Omni 6.0 sources
Sent from my LG-H840 using Tapatalk
Thank you very much for your precious time my friend. Good work
Can't flash magisk through twrp.
Can't mount data through twrp. It is greyed out. Can't select
Have you fix the ptoblem with external sd?
Wire1122 said:
Can't flash magisk through twrp.
Can't mount data through twrp. It is greyed out. Can't select
Have you fix the ptoblem with external sd?
Click to expand...
Click to collapse
Yes internal storage it's properly mounted now
Sent from my LG-H840 using Tapatalk
Anyone can confirm if encryption works?
Sent from my LG-H840 using Tapatalk
synescu said:
Anyone can confirm if encryption works?
Click to expand...
Click to collapse
I have flash it succesffully. But how can I yest if it works?
I can't backup my data partition with twrp. Whats wrong?
Sent from my LG-H840 using XDA Labs
Wire1122 said:
I can't backup my data partition with twrp. Whats wrong?
Sent from my LG-H840 using XDA Labs
Click to expand...
Click to collapse
{
"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"
}
Sent from my LG-H840 using Tapatalk
Can't backup data. :crying: unable to mount data ecc
Sent from my LG-H840 using XDA Labs
Wire1122 said:
Can't backup data. :crying: unable to mount data ecc
Sent from my LG-H840 using XDA Labs
Click to expand...
Click to collapse
In Order to use data first you have to factory reset your phone using the stock recovery
Sent from my LG-H840 using Tapatalk
How? Stock recovery? Where is it? I'm noob and rooted with supersu
My log
Wire1122 said:
My log
Click to expand...
Click to collapse
stock h840-recovery.img
I have flashed stock recovery but not have twrp anymore... What must do i do?
Sent from my LG-H840 using XDA Labs
Wire1122 said:
I have flashed stock recovery but not have twrp anymore... What must do i do?
Sent from my LG-H840 using XDA Labs
Click to expand...
Click to collapse
Why would you think that you would keep TWRP after flashing stock recovery? Also, why would you flash stock recovery after flashing TWRP and SuperSU? You either have TWRP or stock recovery, not both. Also, don't ever recommend flashing stock recovery after modifying system in any way unless you reflash whole stock system as stock. Anyways, all you need to do to get TWRP back is use the :
fastboot flash recovery TWRP.img
Hey guys, I'm in trouble. Need urgent help.
I was trying to install OOS & xXx rom from a clean install. But after flashing OOS & TWRP, probably I boot into wrong Slot. So now I'm stuck with Fastboot mode, cannot even go to Recovery. Can anyone help me out here so that I don't have to format the phone & re-unlock again?
TIA
nipun1110 said:
Hey guys, I'm in trouble. Need urgent help.
I was trying to install OOS & xXx rom from a clean install. But after flashing OOS & TWRP, probably I boot into wrong Slot. So now I'm stuck with Fastboot mode, cannot even go to Recovery. Can anyone help me out here so that I don't have to format the phone & re-unlock again?
TIA
Click to expand...
Click to collapse
If wrong slot is the only thing you messed up,
hook the phone in fastboot mode to PC and use the adb command (assuming you have appropriate drivers/adb already installed on your pc):
fastboot --set-active=_a
Change the slot from a to b if slot a does not get you to recovery. This command simply make either slot a or b active so you can boot into the correct slot.
Make sure you copy the command exactly as it's posted
Good luck!
Gr8man001 said:
If wrong slot is the only thing you messed up,
hook the phone in fastboot mode to PC and use the adb command (assuming you have appropriate drivers/adb already installed on your pc):
fastboot --set-active=_a
Change the slot from a to b if slot a does not get you to recovery. This command simply make either slot a or b active so you can boot into the correct slot.
Make sure you copy the command exactly as it's posted
Good luck!
Click to expand...
Click to collapse
Hello, thanks a lot for your prompt response. But it is showing this error.
{
"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"
}
nipun1110 said:
Hello, thanks a lot for your prompt response. But it is showing this error.
Click to expand...
Click to collapse
How current are your fastboot (and adb) executables? From the command line, try entering:
Code:
adb version
I'm getting Android Debug Bridge version 1.0.40. If you're seeing something older than that, try a more recent version of adb and fastboot.
maigre said:
How current are your fastboot (and adb) executables? From the command line, try entering:
Code:
adb version
I'm getting Android Debug Bridge version 1.0.40. If you're seeing something older than that, try a more recent version of adb and fastboot.
Click to expand...
Click to collapse
Finally I got the solution. Thanks man. that command prompt u sent me was a little incorrect. There will be no "_" before "a". Thanks a lot for your help. Highly grateful.
nipun1110 said:
Finally I got the solution. Thanks man. that command prompt u sent me was a little incorrect. There will be no "_" before "a". Thanks a lot for your help. Highly grateful.
Click to expand...
Click to collapse
That wasn't me. It was Gr8man001 that gave you the advice that worked.
nipun1110 said:
Finally I got the solution. Thanks man. that command prompt u sent me was a little incorrect. There will be no "_" before "a". Thanks a lot for your help. Highly grateful.
Click to expand...
Click to collapse
maigre said:
That wasn't me. It was Gr8man001 that gave you the advice that worked.
Click to expand...
Click to collapse
true command : '''' fastboot --set-active=a '''' is it?
For me not work... please help.
https://i.hizliresim.com/pbOkpJ.png
Same thing here. In addition, I am unable to find a newer version of adb. Mine is 1.0.32.
I bricked my phone trying to update twrp. It will reboot to fastboot but not to system. A reboot to system has a dark screen and a small blue light in the notch. I'm thinking (and hoping) that changing the active slot will get it going again. I updated to Experience when the phone was new and want to go Pie, so the original should be in the other slot.
Any help will be appreciated.
zulu657 said:
Same thing here. In addition, I am unable to find a newer version of adb. Mine is 1.0.32.
I bricked my phone trying to update twrp. It will reboot to fastboot but not to system. A reboot to system has a dark screen and a small blue light in the notch. I'm thinking (and hoping) that changing the active slot will get it going again. I updated to Experience when the phone was new and want to go Pie, so the original should be in the other slot.
Any help will be appreciated.
Click to expand...
Click to collapse
Try the msm recovery tool, just Google how to unbrick OnePlus 6, it'll wipe your phone and install OOS 5.x.x but it will help you for sure
szybki_ben said:
Try the msm recovery tool, just Google how to unbrick OnePlus 6, it'll wipe your phone and install OOS 5.x.x but it will help you for sure
Click to expand...
Click to collapse
I looked at that one first, but would much rather swap the partitions and see if that will save it before trying the full wipe. Also looked at the Qualcomm drivers and can't seem to get that to work either. I am more used to working on a chromebook and going back to Windoze has been a challenge.
zulu657 said:
I looked at that one first, but would much rather swap the partitions and see if that will save it before trying the full wipe. Also looked at the Qualcomm drivers and can't seem to get that to work either. I am more used to working on a chromebook and going back to Windoze has been a challenge.
Click to expand...
Click to collapse
I don't think that you have to install Qualcomm drivers, I didn't install them and it still worked
szybki_ben said:
I don't think that you have to install Qualcomm drivers, I didn't install them and it still worked
Click to expand...
Click to collapse
The drivers were for another unbrick solution, I believe. I've looked at so many it's now hard to keep them separate. My original quest was to make another slot active. Another member tried the fastboot text and it didn't work -- same for me. A few posts later said to check the adb version. Mine is 1.0.32 and apparently there is now 1.0.40. I cannot find that one. The fastboot text was: fastboot --set-active=a. Didn't work for me either. Said unknown command.
I can boot into twrp but it is stuck on the opening screen.. Possible I can fastboot a new twrp and save it that way.
zulu657 said:
The drivers were for another unbrick solution, I believe. I've looked at so many it's now hard to keep them separate. My original quest was to make another slot active. Another member tried the fastboot text and it didn't work -- same for me. A few posts later said to check the adb version. Mine is 1.0.32 and apparently there is now 1.0.40. I cannot find that one. The fastboot text was: fastboot --set-active=a. Didn't work for me either. Said unknown command.
I can boot into twrp but it is stuck on the opening screen.. Possible I can fastboot a new twrp and save it that way.
Click to expand...
Click to collapse
If you can boot into recovery then booting a fresh img is a good idea, good luck!
szybki_ben said:
If you can boot into recovery then booting a fresh img is a good idea, good luck!
Click to expand...
Click to collapse
Just tried that one -- No Cigar!!! I followed the instructions for installing recovery on a new install. It said to use the text: fastboot boot recoveryimgrecovery.img I had renamed the Blu-spark img to recovery.img. The result was: no file or directory with this name. I was in the folder with adb, fastboot, recovery.img and all the rest of the files for OP6.
There used to be a way to install twrp with adb if I recall, but I can't find it. I know it was for an earlier phone. I have had OnePlus phones from the first one.
Very frustrating!!! I hate to wipe the phone because this should be a simple thing. Of course those are the ones that really get you....
Hmmmm, evidently the command fastboot set active=a is not a command in adb v1.0.32. When I tried it, I got a list of the commands and that one isn't in it.
Trying to find a later version of adb without success.
There has to be a way to change the active partition without formatting the phone. The phone had the original OS and I upgraded to Experience when I got it and have been using it ever since. Experience should be on another partition, so if I can change partitions, I should be on the original OS.
Would that not be correct???
Global/US OnePlus 9 Unbricking Guide
Tested and used on a LE2115 variant device.
YOU SHOULDN'T USE THIS GUIDE UNLESS YOU ARE ABSOLUTELY SURE YOUR PHONE IS BRICKED. PLEASE TRY POWER COMBOS FIRST! THERE ARE NO GUARANTEES, AND THIS SHOULD BE A LAST DITCH ATTEMPT BEFORE SENDING IT TO ONEPLUS (THEY WILL FIX IT FOR YOU, UNLOCKED BOOTLOADER OR NOT)
Step 1: Boot your device into EDL mode. (If it's not already), then plug it in.
If it isn't, and you're in fastboot, you can boot into it via fastboot oem edl (correct me if I'm wrong here)
Step 2: Download the MSM tool.
The proper MSM tool can be found here.
I'd recommend using Internet Download Manager to speed it up.
Unzip it using something like 7-zip into the root folder of any drive (the root folder meaning the topmost, any subdirectories may have issues).
Some AVs may flag MSM, so please make an exception (it's safe, you can ask basically anyone)
Step 3: Install the right drivers. (If they aren't installed)
The proper drivers can be found here.
Use the readme.txt file in the driver zip, it'll explain how to do everything.
Step 4: Run the "MsmDownloadTool V4.0.exe"
Set the dropdown to "Others" and click next.
{
"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"
}
Check the "Use Lite Firehose" box, and uncheck the "Sha256 check" box.
Click on "Start" once your phone is detected.
Step 5: Let it run for around 300-350 seconds (that's how long it took mine). Once it says "Completed" (if it errors, see below), congrats! You've unbricked your OnePlus 9!
Errors
If an error occurs, don't worry! See here for the potential errors and how to solve them.
Sahara Communication Failed
When this happens, try using a different cable (one included in box is best), and try a different port. If both fail, try on another computer.
Device not match image!
Okay, this one WILL take much longer than the previous one, but this is still fixable.
Download this MSM tool instead following the same guidelines as above. (I am aware it is the wrong version, however this is the only working fix to the extent of my knowledge.)
Close the old one.
Flash using the above guidelines aswell.
Once finished (you have to wait the 300 seconds), hope that it works lol.
If it does, it'll reboot into OxygenOS. Go through setup as normal (the cursed camera cutout is also normal), finish it, and then you will have to:
Set up Magisk (too many guides for it, not going to explain it here.
Flash magisk by booting into TWRP using fastboot (fastboot boot twrp-3.6.0_11-0-lemonadep.img) (install menu, then find magisk's file), then copy TWRP's image to the device and install the ramdisk via the image (should be in advanced).
Install this app.
When setting up, grant it root access, and make sure to select the Stable (Full) channel, and set your device to OnePlus 9. (NOT THE INDIA VERSION, NO MATTER WHAT IT SAYS.
Go into settings, and enable Advanced Mode (this is req'd)
Go to the main page, and click download update.
When it finishes, let it do automatic install (UNCHECK ALL BOXES OR IT WILL ERROR!)
Congrats! You fixed it!
If it doesn't work, you may have to send it off to OnePlus. They will still do repairs even on unlocked bootloaders assuming that you're in warranty.
Nice guide ! Just one question, the TWRP link is for OnePlus 9 pro, it is normal?
Other point, to be complete, you should specify how to boot in EDL mode and add fastboot commands for every operations, like flashing twrp
akboy7015 said:
Nice guide ! Just one question, the TWRP link is for OnePlus 9 pro, it is normal?
Other point, to be complete, you should specify how to boot in EDL mode and add fastboot commands for every operations, like flashing twrp
Click to expand...
Click to collapse
Yup, it's normal. I use that specific TWRP on my LE2115. I'll make the edits right away! Thanks for the suggestion!
I have a CN variant of OnePlus 9 (LE2110) running the Global version of Oxygen OS 11.2.10.10LE25AA.
I installed the latest TWRP (3.6.0_11-0-lemonade) from the TWRP website and then I rooted the phone via TWRP with Magisk v23 and everything was fine.
Today I installed a new version of the launcher which was probably buggy, and it made the phone act funny even when I rebooted the device, so I booted the phone into TWRP recovery and dirty flashed the ROM and then reflashed Magisk for root. This is how I used to do it with my 5T.
Obviously, I have done sth wrong, and now the phone boots only in fastboot mode. When I try to boot into recovery, TWRP loads with the lockscreen but it doesn’t work, you cannot do anything, whatever you press it doesn’t react.
To my understanding, I have soft-bricked the phone and need to follow your guide to unbrick it?
panoramixmeister said:
I have a CN variant of OnePlus 9 (LE2110) running the Global version of Oxygen OS 11.2.10.10LE25AA.
I installed the latest TWRP (3.6.0_11-0-lemonade) from the TWRP website and then I rooted the phone via TWRP with Magisk v23 and everything was fine.
Today I installed a new version of the launcher which was probably buggy, and it made the phone act funny even when I rebooted the device, so I booted the phone into TWRP recovery and dirty flashed the ROM and then reflashed Magisk for root. This is how I used to do it with my 5T.
Obviously, I have done sth wrong, and now the phone boots only in fastboot mode. When I try to boot into recovery, TWRP loads with the lockscreen but it doesn’t work, you cannot do anything, whatever you press it doesn’t react.
To my understanding, I have soft-bricked the phone and need to follow your guide to unbrick it?
Click to expand...
Click to collapse
This guide is for phones stuck in edl mode. This won't work on CN phones to the extent of my knowledge. If you can get into fastboot, you can try and recover via a tool. I'm not sure why twrp is doing that, but can you try booting the twrp image instead of booting the flashed one? Sorry about the late response, by the way
@winterfoxx,
thanks for this very useful guide, a curiosity, when you use the zip file linked from "OnePlus_9_Pro_India_OxygenOS_11.2.4.4", you flash the file inside the zip, "lemonadep_22_I.07_210412" which is for the Pro model? right? thanks
winterfoxx said:
This guide is for phones stuck in edl mode. This won't work on CN phones to the extent of my knowledge. If you can get into fastboot, you can try and recover via a tool. I'm not sure why twrp is doing that, but can you try booting the twrp image instead of booting the flashed one? Sorry about the late response, by the way
Click to expand...
Click to collapse
It worked perfectly for the CN variant (LE2110) that I have. The CN variant is running the Global version of OxygenOs (AA) so the only difference was that I had all three options checked (Sha256 check, Auto reboot and Use Lite Firehose).
The first few times I got the Sahara Communication Failed message but I followed your suggestion and changed USB port and cable and it worked flawlessly.
Thank you for the very helpful guide!
I managed to do as described step by step in the guide, after the flash of the original rom via "oxygen updater" but on restart there is actually the stock rom but the touch remains blocked, I also tried to do a factory reset but nothing changes, my phone gets stuck on the first screen and the touch does not respond, any advice? Thank you
iaio72 said:
I managed to do as described step by step in the guide, after the flash of the original rom via "oxygen updater" but on restart there is actually the stock rom but the touch remains blocked, I also tried to do a factory reset but nothing changes, my phone gets stuck on the first screen and the touch does not respond, any advice? Thank you
Click to expand...
Click to collapse
So sad , I am in the same situation!
Did you figured it out ??
from oxygen updater, I also tried to flesh the Open beta 1, but same result, the touchscreen does not respond, strange but with the rom for the pro version the touchscreen works fine, I'm looking for a way to solve but still nothing new....
iaio72 said:
I managed to do as described step by step in the guide, after the flash of the original rom via "oxygen updater" but on restart there is actually the stock rom but the touch remains blocked, I also tried to do a factory reset but nothing changes, my phone gets stuck on the first screen and the touch does not respond, any advice? Thank you
Click to expand...
Click to collapse
i had to do this with the latest a12 update broke the screen like your saying and this is the steps i had to take to fix it
Device not match image!
Okay, this one WILL take much longer than the previous one, but this is still fixable.
Download this MSM tool instead following the same guidelines as above. (I am aware it is the wrong version, however this is the only working fix to the extent of my knowledge.)
Close the old one.
Flash using the above guidelines aswell.
Once finished (you have to wait the 300 seconds), hope that it works lol.
If it does, it'll reboot into OxygenOS. Go through setup as normal (the cursed camera cutout is also normal), finish it, and then you will have to:
Set up Magisk (too many guides for it, not going to explain it here.
Boot into TWRP using fastboot (fastboot boot twrp-3.6.0_11-0-lemonadep.img
Flash 11.2.10.10 ota zip in twrp via adb sideload and reboot and you will have working screen and everything else.
at this point do not update to A12 update aka the c36 ota in settings or you will face the same issue and have to redo this process
Congrats! You fixed it!
panoramixmeister said:
It worked perfectly for the CN variant (LE2110) that I have. The CN variant is running the Global version of OxygenOs (AA) so the only difference was that I had all three options checked (Sha256 check, Auto reboot and Use Lite Firehose).
The first few times I got the Sahara Communication Failed message but I followed your suggestion and changed USB port and cable and it worked flawlessly.
Thank you for the very helpful guide!
Click to expand...
Click to collapse
Congrats! I'm glad I was able to help
iaio72 said:
I managed to do as described step by step in the guide, after the flash of the original rom via "oxygen updater" but on restart there is actually the stock rom but the touch remains blocked, I also tried to do a factory reset but nothing changes, my phone gets stuck on the first screen and the touch does not respond, any advice? Thank you
Click to expand...
Click to collapse
Erm, try factory resetting it in twrp
winterfoxx said:
Erm, try factory resetting it in twrp
Click to expand...
Click to collapse
even with twrp flashed the device is frozen in recovery same as on the main screen even for me i had todo it the way i listed above to be able to even do anything on the phone and it was the only way for it to work correctly for me
the one downside to this method that ive found is i am still unable to flash stock OP9 msm even after fixing i still get the device not match image error even after using the param from my stock msm backup files and flashing it directly to my device.
i verified before i even had this issue that my device was in fact a le2115 and backed up all partitions using msm.
i figured out the best way to flash stock global to device and not have a frozen screen if you update to a12
i can verify that you can shorten this down by a few steps also and it will still work .
At step 4 just flash global msm with step 2 options unchecked and device set as o2 and start
Although i would advise against taking the a12 update for multiple reasons
papad13 said:
So sad , I am in the same situation!
Did you figured it out ??
Click to expand...
Click to collapse
now i try to: at the step where you installed twrp, now i try to flash (adb sideload...) indian fw to downgrade from openbeta, stay tuned!!
allenjthomsen said:
i figured out the best way to flash stock global to device and not have a frozen screen if you update to a12
i can verify that you can shorten this down by a few steps also and it will still work .
At step 4 just flash global msm with step 2 options unchecked and device set as o2 and start
Although i would advise against taking the a12 update for multiple reasons
Click to expand...
Click to collapse
"a12" you talked aboit open beta? or we have official oxygen android 12? thx
iaio72 said:
now i try to: at the step where you installed twrp, now i try to flash (adb sideload...) indian fw to downgrade from openbeta, stay tuned!!
Click to expand...
Click to collapse
Can you help finding the “param bin file global”
Please ?
I shifted from apple to android recently and I decided to root my device OnePlus 8t KB2001 (I believe I have Android 12) as I wanted to install kali on it. Therefore I decided to follow instructions on this website. I did not type the steps because I did not want to lose out on any key details.
I performed all the steps till here:
I did not perform step 6, instead, I performed step 7 as I wanted to install TWRP Recovery on my phone permanently.
{
"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"
}
According to the instructions I was supposed to boot my device to TWRP. Since I am currently booted to Fastboot, I used the Volume Keys to bring up the Recovery option and hit the Power key to confirm the decision.
As per the instruction as soon as my OnePlus boots to TWRP, it will ask to decrypt data. I was supposed to simply enter my phone’s password/PIN to proceed ahead but this never happened. Instead, I am stuck in a situation where I am seeing the following screen:
I searched every single option and there's no Online Update (keep data) option. I am stuck in this loop for hours. Even the option of formatting data doesn't remove this RECOVERY.
I don't know if this information would help but I can enter the Fastboot Mode by tapping on "Advanced" and selecting "Reboot to fastboot mode".
It would be really helpful if someone can tell me a fix to this problem as I really don't want to throw this phone away as I just got it today.
You probably flashed a version of TWRP made for Android 11 while having Android 12. You can try flashing a compatible version (unofficial) which you can find here.
I have not had the exact problem you describe but I don't think you'll end up discarding your phone. Just plan to read a lot on the forums, try a lot of things and potentially spend several days working through the problem. Bookmark the useful instructions you find so you can return to re-read and make notes as you go along. Start with booting a different version of TWRP and see what happens. The images you posted are of the stock recovery, not TWRP recovery. Make sure the TWRP.img you are trying to boot resides in the folder that your command prompt is pointing to.
TheNewHEROBRINE said:
You probably flashed a version of TWRP made for Android 11 while having Android 12. You can try flashing a compatible version (unofficial) which you can find here.
Click to expand...
Click to collapse
Thank you for this link. I followed these steps and I am out of the continuous recovery loop. My phone now directly boots to Team Win Recovery Project. Although I have a feeling my phone no longer has any oxygen OS. I tried rebooting into System but I am taken back to the TWRP screen. Any idea what is happening?
FakeGemstone said:
I have not had the exact problem you describe but I don't think you'll end up discarding your phone. Just plan to read a lot on the forums, try a lot of things and potentially spend several days working through the problem. Bookmark the useful instructions you find so you can return to re-read and make notes as you go along. Start with booting a different version of TWRP and see what happens. The images you posted are of the stock recovery, not TWRP recovery. Make sure the TWRP.img you are trying to boot resides in the folder that your command prompt is pointing to.
Click to expand...
Click to collapse
Thank you, this really gives me hope that my money will not go to waste. Now I am just in the process of trying to find a solution where I can my make phone the way it was which is without having any TWRP
kooluser said:
Thank you for this link. I followed these steps and I am out of the continuous recovery loop. My phone now directly boots to Team Win Recovery Project. Although I have a feeling my phone no longer has any oxygen OS. I tried rebooting into System but I am taken back to the TWRP screen. Any idea what is happening?
Click to expand...
Click to collapse
I think I know what happened:
The OnePlus 8T is a device which uses a technology called Virtual A/B. In practice, it has two slots for the operating system called 'a' and 'b' of which only one is active at a time. When you do an OTA upgrade the upgrade gets installed to the inactive slot and then the phone is asked to switch slot on the next boot. If the phone can't boot after this slot switch, it will switch back to the previous slot to prevent bricking itself. So what I think it happened when you flashed the wrong TWRP is that the phone tried to boot into recovery from your current slot but failed because of incompatibility. Then, it switched the active slot to the inactive slot where you probability have another version of OxygenOS that can't boot (probably because it's older than your current one). After some attempts, the phone goes into recovery but this time it loads the stock one because it has switched slot and the recovery is subject to this Virtual A/B mechanism too.
If this is what happened you can do as follows:
- reboot into fastboot
- switch the active slot by doing
Code:
fastboot --set-active=other
- flash the correct TWRP you downloaded before on this slot by doing
Code:
fastboot flash recovery <recovery file name>.img
After doing this you should be able to boot both into the system and into TWRP.
TheNewHEROBRINE said:
I think I know what happened:
The OnePlus 8T is a device which uses a technology called Virtual A/B. In practice, it has two slots for the operating system called 'a' and 'b' of which only one is active at a time. When you do an OTA upgrade the upgrade gets installed to the inactive slot and then the phone is asked to switch slot on the next boot. If the phone can't boot after this slot switch, it will switch back to the previous slot to prevent bricking itself. So what I think it happened when you flashed the wrong TWRP is that the phone tried to boot into recovery from your current slot but failed because of incompatibility. Then, it switched the active slot to the inactive slot where you probability have another version of OxygenOS that can't boot (probably because it's older than your current one). After some attempts, the phone goes into recovery but this time it loads the stock one because it has switched slot and the recovery is subject to this Virtual A/B mechanisms too.
If this is what happened you can do as follows:
- reboot into fastboot
- switch the active slot by doing
Code:
fastboot --set-active=other
- flash the correct TWRP you downloaded before on this slot by doing
Code:
fastboot flash recovery <recovery file name>.img
After doing this you should be able to boot both into the system and into TWRP.
Click to expand...
Click to collapse
THANK YOU SO MUCH!!! THIS SOLUTION SOLVED MY PROBLEM!
I can't express how happy I am right now!! I really thought I lost my phone forever. My phone has now successfully booted up and I can now actually use this device
kooluser said:
THANK YOU SO MUCH!!! THIS SOLUTION SOLVED MY PROBLEM!
I can't express how happy I am right now!! I really thought I lost my phone forever. My phone has now successfully booted up and I can now actually use this device
Click to expand...
Click to collapse
I'm happy for you too
TheNewHEROBRINE said:
I'm happy for you too
Click to expand...
Click to collapse
I just have one more question, so now if I have to boot into TWRP what steps should I follow? As I still have to download Magisk on my phone to properly root it
Did you flash TWRP after switching slot? If so you should be able to boot into it by holding power and volume down while turning the phone on.
Yes I flashed the TWRP as you specified below
Code:
fastboot flash recovery <recovery file name>.img
and once I press the power and the lower volume button I am taken into fastboot option. Once I am there which option should I select? Start, recovery or something else?
kooluser said:
Yes I flashed the TWRP as you specified below
Code:
fastboot flash recovery <recovery file name>.img
and once I press the power and the lower volume button I am taken into fastboot option. Once I am there which option should I select? Start, recovery or something else?
Click to expand...
Click to collapse
To root your phone you can follow this guide: https://forum.xda-developers.com/t/...national-kb2000-kb2001-kb2003-kb2005.4178675/
You actually don't strictly need TWRP to root. I suggest that you always try to follow guides that are on XDA rather than searching for random websites with Google.
TheNewHEROBRINE said:
To root your phone you can follow this guide: https://forum.xda-developers.com/t/...national-kb2000-kb2001-kb2003-kb2005.4178675/
You actually don't strictly need TWRP to root. I suggest that you always try to follow guides that are on XDA rather than searching for random websites with Google.
Click to expand...
Click to collapse
Thank you for the link. To perform this step do I need to do anything special right now? As I believe TWRP is still on my phone
kooluser said:
Thank you for the link. To perform this step do I need to do anything special right now? As I believe TWRP is still on my phone
Click to expand...
Click to collapse
It's not a problem to have TWRP installed.
TheNewHEROBRINE said:
It's not a problem to have TWRP installed.
Click to expand...
Click to collapse
Thank you so much for helping me and solving all my queries
kooluser said:
I just have one more question, so now if I have to boot into TWRP what steps should I follow? As I still have to download Magisk on my phone to properly root it
Click to expand...
Click to collapse
You can install magisk from TWRP recovery.
Changing slots is also possible there.
So, there was a year that I initiated the bootloader unlocking process (Yeah I waited 1 year instead of 168 hours xD). After I unlocked it, the phone wouldn't boot anymore. It get stuck on the poco logo with the Unlocked icon above. It boots then ramps up the brightness and stays on Poco. I can boot to fastboot. I tried miflashing the fastboot ROM multiple times (tried both EU and Global) and still the same issue. I tried installing Arrow recovery but whenever I boot to recovery and try to sideload arrow os, it doesn't even start and gives me cannot mount /cache. I also tried TWRP but it gives me cannot mount /systemroot whatever. What can I do?
doomalikaw99 said:
So, there was a year that I initiated the bootloader unlocking process (Yeah I waited 1 year instead of 168 hours xD). After I unlocked it, the phone wouldn't boot anymore. It get stuck on the poco logo with the Unlocked icon above. It boots then ramps up the brightness and stays on Poco. I can boot to fastboot. I tried miflashing the fastboot ROM multiple times (tried both EU and Global) and still the same issue. I tried installing Arrow recovery but whenever I boot to recovery and try to sideload arrow os, it doesn't even start and gives me cannot mount /cache. I also tried TWRP but it gives me cannot mount /systemroot whatever. What can I do?
Click to expand...
Click to collapse
Maybe a stupid question, but did you try to wipe caches?
And if you used the MiFlash tool, did you select the clear_all.bat-File?
SmartJuwel said:
Maybe a stupid question, but did you try to wipe caches?
And if you used the MiFlash tool, did you select the clear_all.bat-File?
Click to expand...
Click to collapse
When I was on TWRP I tried wiping caches but it didn't work, couldn't mount. Can I wipe it from Fastboot? and yes I used the Clean All option (flash_all.bat).
EDIT: just did 'fastboot erase cache'. What now? Seems it's still stuck on POCO.
doomalikaw99 said:
When I was on TWRP I tried wiping caches but it didn't work, couldn't mount. Can I wipe it from Fastboot? and yes I used the Clean All with option (flash_all.bat).
Click to expand...
Click to collapse
And the flashing didn't fail? IMHO Flash_all.bat also flashes the cache partition...
SmartJuwel said:
And the flashing didn't fail? IMHO Flash_all.bat also flashes the cache partition...
Click to expand...
Click to collapse
I think so? It successfully flashes everything and then reboots. MiFlash says error: Could not catch checkpoint. But I think that's normal?
doomalikaw99 said:
I think so? It successfully flashes everything and then reboots. MiFlash says error: Could not catch checkpoint. But I think that's normal?
Click to expand...
Click to collapse
First, check your model is Poco X3 Pro.
There is another similar phone that is without "Pro".
Did you "format data" or "wipe cache/Dalvik" ?
https://forum.xda-developers.com/t/4288121/post-85137963
Another option: find Xiaomi/Redmi/Poco repair center or support center and ask them if they can help you flash official MIUI back into your phone.
pl1992aw said:
First, check your model is Poco X3 Pro.
There is another similar phone that is without "Pro".
Did you "format data" or "wipe cache/Dalvik" ?
https://forum.xda-developers.com/t/4288121/post-85137963
Another option: find Xiaomi/Redmi/Poco repair center or support center and ask them if they can help you flash official MIUI back into your phone.
Click to expand...
Click to collapse
Checked again, the miui rom is the pro version (vayu). After I miflash I should format data or what? This is so weird!! Why would the phone brick like that? Is it because I initiated the unlocking a year ago in MIUI 12 and now I unlocked it with MIUI 13 ??
doomalikaw99 said:
Checked again, the miui rom is the pro version (vayu). After I miflash I should format data or what? This is so weird!! Why would the phone brick like that? Is it because I initiated the unlocking a year ago in MIUI 12 and now I unlocked it with MIUI 13 ??
Click to expand...
Click to collapse
I mean check your phone if it is Pro version or not.
If you can still access fastboot, it's most likely a soft brick. It can probably be saved as long as the hardware is still normal.
It shouldn't matter as long as you had applied for unlocking. Unlock bootloader most likely only need some key from server to decrypt the bootloader.
I had seen some users saying phone randomly reboot on it's own and had stuck in rebooting for a few times, then it boot normally again.
Also try reboot PC, and reboot your phone to fastboot mode manually (press power button+Vol - ), then flash again.
You can try flash MIUI 12 with "clean all". Just don't lock the bootloader.
Here's a picture step-by-step tutorial to flash a ROM:
https://forum.xda-developers.com/t/4288121/post-85137963
Format data is done in TWRP, but with the official fastboot ROM "clean all" option, data should had already formatted.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I don't know what happen cause I never encounter such issue, and I have 3 Poco X3 Pro.
Anyway, remember Xiaomi center is always a place to go.
pl1992aw said:
I mean check your phone if it is Pro version or not.
If you can still access fastboot, it's most likely a soft brick. It can probably be saved as long as the hardware is still normal.
It shouldn't matter as long as you had applied for unlocking. Unlock bootloader most likely only need some key from server to decrypt the bootloader.
I had seen some users saying phone randomly reboot on it's own and had stuck in rebooting for a few times, then it boot normally again.
Also try reboot PC, and reboot your phone to fastboot mode manually (press power button+Vol - ), then flash again.
You can try flash MIUI 12 with "clean all". Just don't lock the bootloader.
Here's a picture step-by-step tutorial to flash a ROM:
https://forum.xda-developers.com/t/4288121/post-85137963
Format data is done in TWRP, but with the official fastboot ROM "clean all" option, data should had already formatted.
I don't know what happen cause I never encounter such issue, and I have 3 Poco X3 Pro.
Anyway, remember Xiaomi center is always a place to go.
Click to expand...
Click to collapse
Mine doesn't reboot man. It stays at the POCO logo. If I want to get to TWRP, I have to "Fastboot flash recovery twrp.img then fastboot boot twrp.img" multiple times for it to actually boot to twrp. And if I try to format data I get multiple errors: " Failed to mount /system_root (Block Device Required) Failed to mount /data ..........."
doomalikaw99 said:
Mine doesn't reboot man. It stays at the POCO logo. If I want to get to TWRP, I have to "Fastboot flash recovery twrp.img then fastboot boot twrp.img" multiple times for it to actually boot to twrp. And if I try to format data I get multiple errors: " Failed to mount /system_root (Block Device Required) Failed to mount /data ..........."
Click to expand...
Click to collapse
Press and hold both "volume up" and "power" together, until it goes into fastboot.
It will first turn off, then boot the poco logo, and then into fastboot mode.
Then plug phone to PC.
On PC, extract the fastboot ROM tgz into a folder with short name (like "rom"), and put the "rom" folder into C:\
Then go inside the "rom" folder, look for the file "flash_all.bat" and run it.
Make sure NOT the one with lock.
The error in TWRP is possibly bug, similar to this:
https://forum.xda-developers.com/t/...-only-rw-remount-failed.4482065/post-87312725
I just read again your first post
doomalikaw99 said:
It get stuck on the poco logo with the Unlocked icon above. It boots then ramps up the brightness and stays on Poco.
Click to expand...
Click to collapse
This means the phone is booting correctly, it is just doing initialization, like the first time you got your phone.
This step will take quite some time to initialize, give it 30 minutes, or up to 1 hour max.
Keep the usb cable connected to PC to keep the battery up.
pl1992aw said:
Press and hold both "volume up" and "power" together, until it goes into fastboot.
It will first turn off, then boot the poco logo, and then into fastboot mode.
Then plug phone to PC.
On PC, extract the fastboot ROM tgz into a folder with short name (like "rom"), and put the "rom" folder into C:\
Then go inside the "rom" folder, look for the file "flash_all.bat" and run it.
Make sure NOT the one with lock.
The error in TWRP is possibly bug, similar to this:
https://forum.xda-developers.com/t/...-only-rw-remount-failed.4482065/post-87312725
I just read again your first post
This means the phone is booting correctly, it is just doing initialization, like the first time you got your phone.
This step will take quite some time to initialize, give it 30 minutes, or up to 1 hour max.
Keep the usb cable connected to PC to keep the battery up.
Click to expand...
Click to collapse
It's been a rough 2 weeks. Thank you for telling me about that last bit, it gave me hope for trying more. I booted into twrp twice to bypass the "Block device Required" thing but then I tried sideloading Arrow OS but it didn't work as usual saying this " assert failed: update_dynamic_partitions (package_extract_file("dynamic_partitions_op_list"))". But after googling, I randomly stumbled upon comment saying that I should make sure that /system and /vendor are unmounted! For me it became a habit to boot into recovery and mount everything to check if recovery is working properly without the Block Device errors!!!I unmouned everything except the defaults (data and something else), I sideloaded Arrow OS 13 (copying from pc wasn't working for some reason), I formatted the data, rebooted but it kept getting me into fastboot for some reason but I rebooted a couple of times and SUDDENLY IT WORKS WTF!!! Maybe you were right, I should've waited for an hour after miflashing the original ROM. God I feel dumb. Thank you anyways and thank you everyone.
Now, I want to root lol...
Ok so, after my first reboot the phone got stuck in the POCO logo again and after a few reboots it doesn't turn on anymore but connects as device "Qualcomm HS-USB QDLoader 9008" into my pc, I guess the phone bricked?
Before I unlock the bootloader, it would sometimes reboot and get stuck in the POCO logo but then turns on after a while. I guess the problem was hardware related after all. I don't have the indian variant, I don't know if this is common or not.