Question Poco x3 Pro stuck in Poco Logo after unlocking bootloader - Xiaomi Poco X3 Pro

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.

Related

[Q] Stock OPO soft bricked after turning off at night.

Okay, here's the deal... I have an OPO (not mine) that is completely stock running, I would presume 5.0.2. I'm not exactly sure which build. But I was told that she turned the phone off at night and charged it. Turned it on in the morning and it got stuck on the cyanogen logo. No boot loops, no getting past that. Just sitting there. The device is stock, bootloader locked, no root. I also highly doubt that ADB debugging was turned on while it was working...
I'm trying to wipe it bring it back to stock, but I'm not having any success. I've gone in to Cyanogen recovery and wipe/factory reset, wipe cache, wipe media. Reboot, still stuck. When I click apply update in recovery, it gives me a bunch of errors saying so and so directory isn't found. So that leaves to me to believe that something went bad.
I just tried to fastboot oem unlock, said it finished in a few seconds. Then I tried to fastboot the factory image files and after the first one (modem), it gave me an error saying the bootloader is locked.
I'm out of ideas and the unbrick a hard bricked OPO thread said it wouldn't work, so I haven't tried it. Any advice on where to look would be much appreciated.
Anybody?
{
"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 get this when I hit Apply Update and then use storage as option.
moobieboobie said:
Anybody?
I get this when I hit Apply Update and then use storage as option.
Click to expand...
Click to collapse
Flash The whole Rom with fastboot to fix The Problem ....make a backup of your internal sdcard....
jamal2367 said:
Flash The whole Rom with fastboot to fix The Problem ....make a backup of your internal sdcard....
Click to expand...
Click to collapse
That's the problem. I can't because the bootloader is locked. When I try to unlock it, it runs the command. Then when I try to fastboot flash, it tells me the bootloader is locked. I have my own OPO that I have unlocked and rooted, so knowing how to unlock isn't an issue either.
moobieboobie said:
That's the problem. I can't because the bootloader is locked. When I try to unlock it, it runs the command. Then when I try to fastboot flash, it tells me the bootloader is locked. I have my own OPO that I have unlocked and rooted, so knowing how to unlock isn't an issue either.
Click to expand...
Click to collapse
Run CMD as Admin ...have you install the right driver for your phone and install the ADB drivers correctly? ...
jamal2367 said:
Run CMD as Admin ...have you install the right driver for your phone and install the ADB drivers correctly? ...
Click to expand...
Click to collapse
Yes, all updated drivers. Drivers are not the issue since I can execute commands while in fastboot. The issue is not having an unlocked bootloader, so I can't flash anything and it won't unlock bootloader.
moobieboobie said:
Yes, all updated drivers. Drivers are not the issue since I can execute commands while in fastboot. The issue is not having an unlocked bootloader, so I can't flash anything and it won't unlock bootloader.
Click to expand...
Click to collapse
Ps did phone was encrypt?
geowolf1000 said:
Ps did phone was encrypt?
Click to expand...
Click to collapse
No, phone was not encrypted and ColorOS unbrick didn't work. It recognizes the phone, I hit start and it does it's thing. After first green bar, it boot loops instead of flashing all the files. Ran as admin and all the drivers are good.
moobieboobie said:
No, phone was not encrypted and ColorOS unbrick didn't work. It recognizes the phone, I hit start and it does it's thing. After first green bar, it boot loops instead of flashing all the files. Ran as admin and all the drivers are good.
Click to expand...
Click to collapse
hit install from recovery
Choose file to update
Search files
Do you see your partition?
System exist?
What system do you have color or cyanogen?
Data?
Sd?
geowolf1000 said:
hit install from recovery
Choose file to update
Search files
Do you see your partition?
System exist?
What system do you have color or cyanogen?
Data?
Sd?
Click to expand...
Click to collapse
See post above with picture. It was running stock Cyanogen OS 12, not modded or anything. When I hit Apply Update and Choose from internal storage, I get the error in above picture.
moobieboobie said:
See post above with picture. It was running stock Cyanogen OS 12, not modded or anything. When I hit Apply Update and Choose from internal storage, I get the error in above picture.
Click to expand...
Click to collapse
But you have adb
Sideload full rom included recovery
From adb
geowolf1000 said:
But you have adb
Sideload full rom included recovery
From adb
Click to expand...
Click to collapse
If by sideload, you mean copy the rom to device and then load..I can not access device storage. ADB sideload rom through command line gives me the same errors you see in the above picture.
moobieboobie said:
If by sideload, you mean copy the rom to device and then load..I can not access device storage. ADB sideload rom through command line gives me the same errors you see in the above picture.
Click to expand...
Click to collapse
F**ing recovery
With adb you can navigate to system and change built.prompt and enable debugg mode
All the other method i know need root so dd (replace)recovery from adb
geowolf1000 said:
F**ing recovery
With adb you can navigate to system and change built.prompt and enable debugg mode
All the other method i know need root so dd (replace)recovery from adb
Click to expand...
Click to collapse
Can you give instructions on how to? I'm not too familiar with adb, but can follow steps.
moobieboobie said:
Can you give instructions on how to? I'm not too familiar with adb, but can follow steps.
Click to expand...
Click to collapse
Even this suggest need root.
All need root.... To system...
moobieboobie said:
Can you give instructions on how to? I'm not too familiar with adb, but can follow steps.
Click to expand...
Click to collapse
Another trick for installation is
Code:
fastboot boot <path/name of the recovery twrp img>
It will boot your phone into recovery once from the recovery image
stored in your PC temporarily
then you can flash the zip either by sideload or
Check this
geowolf1000 said:
Another trick for installation is
Code:
fastboot boot <path/name of the recovery twrp img>
It will boot your phone into recovery once from the recovery image
stored in your PC temporarily
then you can flash the zip either by sideload or
Check this
Click to expand...
Click to collapse
cannot fastboot boot recovery, tells me bootloader is locked and fails. the link requires unlocking bootloader, which is not working for me.
moobieboobie said:
cannot fastboot boot recovery, tells me bootloader is locked and fails. the link requires unlocking bootloader, which is not working for me.
Click to expand...
Click to collapse
Haz a parametre here
There is a way to flash an unlocked bootloader if you can't fastboot oem unlock.
As you already tried the color.zip method you should already have most of the needed files.
Download the attachment and unzip it into color folder replacing the files emmc_appsboot.mbn and rawprogram0_64.xml (backup the originals first).
-power off the OPO
-hold VolUp and plug into PC
-on PC open device manager, OPO should be in QDloader 9008
-keep an eye on device manager and start msm8974downloadtool from color.zip
-when in device manager the QDloader 9008 disconnects press stop in msm8974downloadtool
-OPO should now be Qualcomm Diagnostics 9006 in device manager
-download MiFlash from here http://www.androidbrick.com/ultimate-qualcomm-snapdragon-unbrick-guide-snapdragons-are-unbrickable/ and set it up like on the pictures on that website
-click refresh. now it should show you OPO on the respective COM port. click flash
-when successfull finished unplug and press and hold power for 30 seconds
-now start into fastboot with power + VolUp and there is your unlocked bootloader
-now you can flash cos with fastboot
The rawprogram0_64xml is edited so that it only writes partition table and flashes sbl1, dbi, rpm, tz, recovery and emmc_appsboot.
This worked for me when i couldn't flash with msm8974downloadtool, it always flashed modem, started with flashing system and then began from the start again.
tropenfrucht said:
There is a way to flash an unlocked bootloader if you can't fastboot oem unlock.
As you already tried the color.zip method you should already have most of the needed files.
Download the attachment and unzip it into color folder replacing the files emmc_appsboot.mbn and rawprogram0_64.xml (backup the originals first).
-power off the OPO
-hold VolUp and plug into PC
-on PC open device manager, OPO should be in QDloader 9008
-keep an eye on device manager and start msm8974downloadtool from color.zip
-when in device manager the QDloader 9008 disconnects press stop in msm8974downloadtool
-OPO should now be Qualcomm Diagnostics 9006 in device manager
-download MiFlash from here http://www.androidbrick.com/ultimate-qualcomm-snapdragon-unbrick-guide-snapdragons-are-unbrickable/ and set it up like on the pictures on that website
-click refresh. now it should show you OPO on the respective COM port. click flash
-when successfull finished unplug and press and hold power for 30 seconds
-now start into fastboot with power + VolUp and there is your unlocked bootloader
-now you can flash cos with fastboot
The rawprogram0_64xml is edited so that it only writes partition table and flashes sbl1, dbi, rpm, tz, recovery and emmc_appsboot.
This worked for me when i couldn't flash with msm8974downloadtool, it always flashed modem, started with flashing system and then began from the start again.
Click to expand...
Click to collapse
gave it a shot a few minutes ago.. As soon as 9008 dc fom device manager, i hit stop. the phone turns off or reboots (the screen goes blank)... I hear the connection, but no 9006.

MOtO G 2015-Internal Storage[0 mb]-Bootloader [Preflash-VALID. Fail] [No Stock FLash]

MOTO G-2015 TURBO EDITION
Hey Guys , I would like to explain what has happened with me from past 3 days !!!!!
My sim slot got broken accidentally , Got it repaired from the Local repair shop - Suddenly after some time when i restarted my phone - there was an error saying - CID READ FAILURE , FASTBOOT MODE THROUGH CHARGER [PHONE DID'NT TURN ON UNTIL CHARGER CONNECTED ] . SO i thought that it was a soft brick due to some reason .
I went to flash it with stock firmware because iT was in fastboot mode [TWRP WASNT OPENING ], so i got the error in the first flash command to flash gpt.bin , was Error flashing -bootloader access denied -<remote failure> .
So i was shocked , I wasn't able to do anything , i have Unbricked many devices but this one sucked me , WENT TO THAT SHOP BACK AND HE REPIARED IT ,THERE WAS A BATTERY CONNECTION FAULT HE SAID and he knew it.
Then everything went good , but i wanted to flash 7.1 due to some reason , so i again tried the fastboot commands and then when i flashed the twrp using fastboot ,it did flahsed but it didnt open , then i kingrooted my phone and flahsed twrp using flashify and it worked , i was able to open twrp then , so i went to flash the 7.1 AOSP AVAILABLE FOR MERLIN.
I wanted to do a clean flash so i advanced wiped everything -INTERNAL STORAGE TOO [LUCKY ME - I COPIED THE FULL TWRP BACKUP TO MY PC]
- suddenly when i started flahsing the aosp.zip file it gave me error --"zip file curropt -error installing ,updating partition details " thats all , so i thought maybe its true so i tried 7.1 with benstalk ,ressurection remix and then i realized that every rom on twrp flash was giving me the same error ,[DEFINATLY MY ZIP WERE NOT CURROPTED] .
SO i thouht of a advanced wipe again using THE R-MF SETTINGS IN TWRP [DONT KNOW IF IT WAS R-MF] , THIS time i did it and bad luck -suddenly my internal storage was showing [0MB ] - I WAS CRYING , i checked on net but there was post like [ MAYBE YoUR HANDSET IS GONE FOREVER ] my phone is only 8 months old.
I tried switching it off , reflashing ,restarting , reflashing via fastboot ,Nothing worked .
EVERYTHING GAVE ME AN ERROR -ERROR MOUNTING CACHE /SYSTEM /DATA/ -NO SUCH PARTITONS FOUND.
i cried and was just rechecking eveything in twrp and i went to advanced wipe -selected to repair internal storage system , and when i went back i saw it was showing 12 GB again ,but the thing was i wasnt able to flash any of roms- so i copied the nandroid backup back to twrp folder and i restored it -I WAS SO HAPPY IT WORKED THIS TIME .
BUT After such a mishap , i feel like something is wrong with my phone -ITS LAGGY AND SOMEWHAT SLOW NOW , EVEN IN FASTBOOT MODE SCREENS WERE MINGLING UP/
SO I WANNA ASK IF SOMETHING LIKE THIS EVER HAPPENED TO ANYONE ? AND WHAT WAS THAT 0 MB ERROR?
Possibly the partition table of internal storage partition got corrupted, showing 0MB.
Broadcasted from Zeta Reticuli
Gravemind2015 said:
Possibly the partition table of internal storage partition got corrupted, showing 0MB.
Broadcasted from Zeta Reticuli
Click to expand...
Click to collapse
SO is there a way to Fix It? Because it may happen again and yeah ,what about the zip file curropt error in Twrp? One more thing , now whenever i am rebooting ,it always get me into the fastboot mode ,and then i have to select start to get into system+ half blackscreen of fastboot and the warning sign of bootloader is shown-PIC BUG type of thing until the system is rebooted.
[email protected] said:
SO is there a way to Fix It? Because it may happen again and yeah ,what about the zip file curropt error in Twrp? One more thing , now whenever i am rebooting ,it always get me into the fastboot mode ,and then i have to select start to get into system+ half blackscreen of fastboot and the warning sign of bootloader is shown-PIC BUG type of thing until the system is rebooted.
Click to expand...
Click to collapse
Dunno about the corrupted .zip error, maybe try fastboot booting into twrp and try from there?
And the phone restarting into bootloader mode indicates incomplete flashing of stock through fastboot. Try the command-
Code:
fastboot oem fb_mode_clear
You can try fastboot flashing the stock firmware again, I don't have any other ideas.
Broadcasted from Zeta Reticuli
Gravemind2015 said:
Dunno about the corrupted .zip error, maybe try fastboot booting into twrp and try from there?
And the phone restarting into bootloader mode indicates incomplete flashing of stock through fastboot. Try the command-
You can try fastboot flashing the stock firmware again, I don't have any other ideas.
Broadcasted from Zeta Reticuli
Click to expand...
Click to collapse
Anyways I still get the same fastboot error of permission denied while flashing via fastboot ,my bootloader is unlocked tho
{
"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"
}
FASTBOOT status shows : 3 , can someone help please ? I really wanna flash 14.1, i must tell you that i was able to flash gpt.bin in start while got the cid read failure , ONLY GPT.BIN nothing else after that , not even gpt itself, So i think i have damaged the partition table badly?
Can you mount all partitions in TWRP?
Remember that TWRP can access about 6-8 of the 27 partitions on this device... seriously, take a working device and open a terminal, do a "cat /proc/partitions" and you will be amazed at what you see. If those other 20 or so partitions are messed up it's probably hardbricked. If TWRP can't mount system, boot, data, etc... you can try to reformat them (Wipes - Advanced - Change Partition Type and format as ext4 for most partitions).
Not to be a downer, but this is often a brick scenario. :/
acejavelin said:
Can you mount all partitions in TWRP?
Remember that TWRP can access about 6-8 of the 27 partitions on this device... seriously, take a working device and open a terminal, do a "cat /proc/partitions" and you will be amazed at what you see. If those other 20 or so partitions are messed up it's probably hardbricked. If TWRP can't mount system, boot, data, etc... you can try to reformat them (Wipes - Advanced - Change Partition Type and format as ext4 for most partitions).
Not to be a downer, but this is often a brick scenario. :/
Click to expand...
Click to collapse
Damn hardbirck ,no I wasnt able to to do that earlier in twrp , and I will check if I can now ,I feel a bit awkward as my phone can never be usable anymore
[email protected] said:
Damn hardbirck ,no I wasnt able to to do that earlier in twrp , and I will check if I can now ,I feel a bit awkward as my phone can never be usable anymore
Click to expand...
Click to collapse
You can always try a Moto service center, although the repair may not be free.
acejavelin said:
You can always try a Moto service center, although the repair may not be free.
Click to expand...
Click to collapse
My phone is 8 month old , and my pop will screw me up and wont let me pay for that , anyways trying that thing now.
So the thing is recovery aint opening , its ****ed up very well, it get stucked on the white and black screen as on pic above , and the fastboot screen is so buggy and so laggy , cant say anything over it ,+ it took me 3 minutes to boot back into system ,heart nearly failed.
acejavelin said:
Can you mount all partitions in TWRP?
Remember that TWRP can access about 6-8 of the 27 partitions on this device... seriously, take a working device and open a terminal, do a "cat /proc/partitions" and you will be amazed at what you see. If those other 20 or so partitions are messed up it's probably hardbricked. If TWRP can't mount system, boot, data, etc... you can try to reformat them (Wipes - Advanced - Change Partition Type and format as ext4 for most partitions).
Not to be a downer, but this is often a brick scenario. :/
Click to expand...
Click to collapse
should i stop and use my system as it is? i will start back over once i am eligible to buy a new phone , or is there a way we can revive back the moto g 3 from q 800 bootloader mode? like in yureka we used memory card to boot into fastboot? something like that.
[email protected] said:
should i stop and use my system as it is? i will start back over once i am eligible to buy a new phone , or is there a way we can revive back the moto g 3 from q 800 bootloader mode? like in yureka we used memory card to boot into fastboot? something like that.
Click to expand...
Click to collapse
QCOM HS-USB QDloader mode? Nope, if you are at that point and that is all you can access, it is hard bricked... There have been a few users working on getting this working but all attempts have been unsuccessful so far since we cannot get a full system dump of ALL partitions (some appear to not be readable by any means we know of).
Are you unable to start fastboot with POWER+VOL DN anymore?
acejavelin said:
QCOM HS-USB QDloader mode? Nope, if you are at that point and that is all you can access, it is hard bricked... There have been a few users working on getting this working but all attempts have been unsuccessful so far since we cannot get a full system dump of ALL partitions (some appear to not be readable by any means we know of).
Are you unable to start fastboot with POWER+VOL DN anymore?
Click to expand...
Click to collapse
NO NO , i can access fastboot but my optimisim says the next time its gonna brick , it will be QCOM HS -USB Qdloader mode, fastboot for name , no commands works from there anymore . Service centre people will probably say for motherboard replacement of what that cannot be solved from xda LOL.
[email protected] said:
NO NO , i can access fastboot but my optimisim says the next time its gonna brick , it will be QCOM HS -USB Qdloader mode, fastboot for name , no commands works from there anymore lol.
Click to expand...
Click to collapse
Touch base with @IkkyShad he has been working on this, but the last I heard he has not been successful. His story is similar to yours, although the device is is a little different, XT1543 I think.
acejavelin said:
Touch base with @IkkyShad he has been working on this, but the last I heard he has not been successful. His story is similar to yours, although the device is is a little different, XT1543 I think.
Click to expand...
Click to collapse
Any -Anything left as for now? or i should carry on happily with stock 6.0.1 instead of having a dead phone, there is a official security update available but it fails to update from there too , i hope a developer comes up soon with a repair for moto g 3 too in that mode.
[email protected] said:
Any -Anything left as for now? or i should carry on happily with stock 6.0.1 instead of having a dead phone, there is a official security update available but it fails to update from there too , i hope a developer comes up soon with a repair for moto g 3 too in that mode.
Click to expand...
Click to collapse
Wait... Your phone is bootable and usable?
acejavelin said:
Wait... Your phone is bootable and usable?
Click to expand...
Click to collapse
It is !! Except that i cannot change anything in it now ,its laggy tho, i think i got very lucky restoring the twrp backup.
[email protected] said:
It is !! Except that i cannot change anything in it now ,its laggy tho.
Click to expand...
Click to collapse
Better not to mess with it as long as it works, especially if you are not in a situation to repair incase of complete brick Just avoid modding and updates.
Broadcasted from Zeta Reticuli

[Recovery] TWRP 3.2.1-0 for GPD XD Plus / XD+ Handheld MT8176

Update: Thread outdated. A new and working version of TWRP was posted in another Forum. Thanks.
{
"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 get this
PS: On instructions for second method you may want to mention you have to rename twrp image to recovery.img
My device is now stuck in the fastboot menu. It says I can navigate the menu using volume up and down but pressing either of those doesn't do anything and I can't seem to power off the device by holding the power button. Any suggestions on how to fix this?
laod said:
My device is now stuck in the fastboot menu. It says I can navigate the menu using volume up and down but pressing either of those doesn't do anything and I can't seem to power off the device by holding the power button. Any suggestions on how to fix this?
Click to expand...
Click to collapse
Some people have reported that touch isn't working and partitions aren't mounting properly. I tried to fix most issues and uploaded a new version. I do not own this device personally - so i can not test the fixes. Please give me feedback for the updated version.
I just got my GPD XD+ today, thanks for the TWRP build but on mine, even with the current build (2018/04/01), I can't perform any actions. Touch still seems not to work for me. I can't get past TWRP asking me "Keep System Read-only?" Let alone see if partitions are loading correctly.
Everything is in portrait mode which is awkward for this device. What about landscape? Shouldn't it be 1280x720 rather than 720x1280?
**Update**
It would appear that my touch controls are inverted... so the fix for others, seems to have inverted my own.
**Update 2***
Well... after realizing the touchscreen was reversed for me, I was able to slide the "Swipe to allow modifications" slider but after that, I chose to reboot out of recovery since the likelyhood of me hitting something by mistake with the controls reversed was high. Being very careful, I was able to tell it to reboot to system and now the system hangs at the GPD logo.. which no longer animates... I can no longer boot into anything but recovery and fastboot.
Any theories as to what has happened? Does anyone have a Clean Stock ROM of the plus model so I can start over using adb?
**Update 3**
PsyOps pointed me towards some stock images at "forum.gpd.hk/t3-the-latest-firmware-of-gpd-game-console" and I'm back in business. Had to flash more than just recovery and boot.. had to flash system as well for some reason.
Goayandi said:
Some people have reported that touch isn't working and partitions aren't mounting properly. I tried to fix most issues and uploaded a new version. I do not own this device personally - so i can not test the fixes. Please give me feedback for the updated version.
Click to expand...
Click to collapse
I have the same situation here.
It happened after unlocked the bootloader, so it's nothing to do with the recovery.
The adb commend return the error: device '(null)' not found.
I can't check the "recovery" box. It doesn't do anything. And the first methode doesn"t work
EDIT : nevermind, I did it but same problem as Busted77
laod said:
My device is now stuck in the fastboot menu. It says I can navigate the menu using volume up and down but pressing either of those doesn't do anything and I can't seem to power off the device by holding the power button. Any suggestions on how to fix this?
Click to expand...
Click to collapse
Same thing here. Now waiting for the battery to empty. What happens after that? Will it work fine and the bootloader be unlocked?
vanzan said:
Same thing here. Now waiting for the battery to empty. What happens after that? Will it work fine and the bootloader be unlocked?
Click to expand...
Click to collapse
I was being dinner and used adb commands instead of fast boot. If you have your device plugged into a computer with fastboot setup you can run "fastboot reboot" and everything should work.
vanzan said:
Same thing here. Now waiting for the battery to empty. What happens after that? Will it work fine and the bootloader be unlocked?
Click to expand...
Click to collapse
Wait for the battery runs out, then recharge, it works fine and the bootloader is unlocked, the first boot will take longer and a few reboot.
And I find that any time you issue fastboot command from you pc, the xd plus will stuck and you have to wait the battery runs out.
I installed the Magisk use fastboot method, stuck again, and need to wait for the battery runs out, recharged, and evertyhing ok then.
There's another root method on Chinese forum (flash supersu pack by recovery), since I rooted by installin Magisk, I didn't try that.
---------- Post added at 11:46 ---------- Previous post was at 11:45 ----------
laod said:
I was being dinner and used adb commands instead of fast boot. If you have your device plugged into a computer with fastboot setup you can run "fastboot reboot" and everything should work.
Click to expand...
Click to collapse
No, when I stuck in the fastboot menu, the adb command return error that no device can find, I have to unplug battery or wait for the battery runs out.
"fastboot reboot" worked perfectly for me!
Fastboot stuck
Same problem here.
I installed the drivers but got the error.
Now my device is in fastboot mode but fastboot reboot etc. don't work.. And I just can't turn it off..
Im really sad.
Windows 10 x64
So.. At least I could fix the problem, I installed the Drivers (had do disable driver signature) and installed your TWRP Mod successfully but the Screen is mirrored! U can use it but its very tricky.. I could open "Install" But if I open it, twrp could not load any data it called "0MB Space" and yeah after reboot, my GPD XD Plus DON'T start..
LeraxGER said:
So.. At least I could fix the problem, I installed the Drivers (had do disable driver signature) and installed your TWRP Mod successfully but the Screen is mirrored! U can use it but its very tricky.. I could open "Install" But if I open it, twrp could not load any data it called "0MB Space" and yeah after reboot, my GPD XD Plus DON'T start..
Click to expand...
Click to collapse
I had the same issue, could use it inverted and mirrored but after running it and not doing anything with it, I could no longer boot into system... Only into recovery. If I tried to boot into system, the boot animation would never animate and the system would hang.
See PsyOps' reply to my question of where to find a stock rom. You can either use the provided tool or you can use adb commands to reflash your system partition... At least for me I had to flash system... Flashing boot and recovery (removing TWRP) didn't work alone...
reddit.com/r/gpdxd/comments/8a50vq/gpd_xd_plus_stock_rom_available/
Busted77 said:
I had the same issue, could use it inverted and mirrored but after running it and not doing anything with it, I could no longer boot into system... Only into recovery. If I tried to boot into system, the boot animation would never animate and the system would hang.
See PsyOps' reply to my question of where to find a stock rom. You can either use the provided tool or you can use adb commands to reflash your system partition... At least for me I had to flash system... Flashing boot and recovery (removing TWRP) didn't work alone...
reddit.com/r/gpdxd/comments/8a50vq/gpd_xd_plus_stock_rom_available/
Click to expand...
Click to collapse
Thanks for the advice, I spoke with him too and he already gave me the guide how to boot into Recovery Mode and then fastboot (Hold VOL+ & On Off Untill Menu apperas, then boot into recovery, then if the android guy appears press On/Off and THEN VOL+, so you're in the normal recovery mode for all the other poor user's )
And I flashed system.img, boot and stock recovery and then it booted up..
The only thing is, that I think that the SD card won't mount correctly anytime and if I plug it to the PC, I dont see the SD card and big files (like the StockROM Update 1.10 abort before its finished).
Greetings
Contact me in discord.
Could you please close the thread and delte the download link? Not even once your TWRP worked, please don't share the file anymore. Other user's will brick their device too.
Hello how to fix a black screen caused by overheating device?i dont know how to use the stock recovery i have thr gpd boot logo but after a black screen and blue led thanks

TWRP wont allow file transfer in USB via pc

NEED HELP
1. I wiped my system .. no system to load into
2. MIFLASH giving antirollback check error for all Fastboot roms
3. TWRP wont allow me to flash roms and there are no roms copied in the phone. getting error while copying files to the phone via TWRP
any solution ..
other than removing antirollback check in the roms .. ?
1. Is your bootlader CURRENTLY unlocked?
2. Which TWRP did you use?
3. Did you format all data using TWRP (enter yes to confirm) AND reboot TWRP before trying to copy rom to phone?
Sent from my Mi 10 Pro using Tapatalk
ted presley said:
1. Is your bootlader CURRENTLY unlocked?
2. Which TWRP did you use?
3. Did you format all data using TWRP (enter yes to confirm) AND reboot TWRP before trying to copy rom to phone?
Sent from my Mi 10 Pro using Tapatalk
Click to expand...
Click to collapse
bootload is unlocked
I figured it out loaded mi recovery wiped data and entered the system ..
I want to go to flash eu rom
do i dirty flash or do i clean flash the rom
stuck up on that part
TED can u help plz ..
I have used twrp-cmi-3.3.1-1
twrp-umi-3.3.1-2
what twrp are u using and i havent installed twrp
i am just booting TWRP
could you please tell me steps to 20.4.27
It seems you still on stock mi flash recovery, if your bootloader currently still unlocked.
You have to:
1. Go to fastboot
2. Flash TWRP again
3. Without restaring the device, reboot TWRP by using button combination: power off the device, press and hold volume down button until you see twrp screen
4. Format all data using twrp (option enter yes to confirm)
5. Reboot recovery using option reboot in TWRP recovery
6. Plug in pc to copy rom and flash.
Sent from my Mi 10 Pro using Tapatalk
ted presley said:
It seems you still on stock mi flash recovery, if your bootloader currently still unlocked.
You have to:
1. Go to fastboot
2. Flash TWRP again
3. Without restaring the device, reboot TWRP by using button combination: power off the device, press and hold volume down button until you see twrp screen
4. Format all data using twrp (option enter yes to confirm)
5. Reboot recovery using option reboot in TWRP recovery
6. Plug in pc to copy rom and flash.
Sent from my Mi 10 Pro using Tapatalk
Click to expand...
Click to collapse
twrp gives error saying
failed to mount /system_root permission denied
failed to mount /vendor permission denied
is it necessary the twrp should be installed
is it possible to just boot twrp while loading zips ..
thanks
sanish4u said:
twrp gives error saying
failed to mount /system_root permission denied
failed to mount /vendor permission denied
is it necessary the twrp should be installed
is it possible to just boot twrp while loading zips ..
thanks
Click to expand...
Click to collapse
problems just increasing now ..
the phone wont boot to twrp it will just go to fastboot
twrp wont load through volume down and power button
Seems like you lost TWRP
Reinstall twrp
Code:
Fastboot flash recovery twrp.img (use your filename)
Fastboot reboot recovery
Then when your in click the top right icon which says wipe. Here click on the right button I forget what it says I think it says wipe data. Next screen will ask you to type out the word "yes" you have to do this. You will lose all your data on the phone.
Now provided you have the drivers correctly installed you should see your phone as accessible from your computer. Paste your rom into the drive from your computer to the phone drive.
Once completed, go back to your phone you should be on the main menu click on top right it should say install. I believe you'll be in root directory you have to navigate to sdcard. Look for sdcard folder.
You should see the Rom you copied over, install it. It should take 5 to 10 minutes. Once complete reboot to system. First but will take some time maybe 5 to 10 minutes let it do it's thing.
Your done. If you want magisk, there are lots of guides here to do that as well
IronSingh said:
Seems like you lost TWRP
Reinstall twrp
Code:
Fastboot flash recovery twrp.img (use your filename)
Fastboot reboot recovery
Then when your in click the top right icon which says wipe. Here click on the right button I forget what it says I think it says wipe data. Next screen will ask you to type out the word "yes" you have to do this. You will lose all your data on the phone.
Now provided you have the drivers correctly installed you should see your phone as accessible from your computer. Paste your rom into the drive from your computer to the phone drive.
Once completed, go back to your phone you should be on the main menu click on top right it should say install. I believe you'll be in root directory you have to navigate to sdcard. Look for sdcard folder.
You should see the Rom you copied over, install it. It should take 5 to 10 minutes. Once complete reboot to system. First but will take some time maybe 5 to 10 minutes let it do it's thing.
Your done. If you want magisk, there are lots of guides here to do that as well
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"
}
It just wont let me wipe data says permission denied image attached
and wont let me copy rom as it is connected it MTP mode
sanish4u said:
It just wont let me wipe data says permission denied image attached
and wont let me copy rom as it is connected it MTP mode
Click to expand...
Click to collapse
Mtp is ok no issues. Photo is broken can't see what you posted. Try wipe on the left button. Don't wipe system. Did you have a pin code setup for your phone to get in the phone are you entering this pin code when twrp starts? You should enter this pin/password
IronSingh said:
Mtp is ok no issues. Photo is broken can't see what you posted. Try wipe on the left button. Don't wipe system. Did you have a pin code setup for your phone to get in the phone are you entering this pin code when twrp starts? You should enter this pin/password
Click to expand...
Click to collapse
It wont boot twrp or install twrp ..
twrp wont load whatsoever now ..
my only option is only mflash tool ..
is there any Fastboot rom which wont cause anti rollback error check
If anyone finds any solution will be greatly appreciated ..
Thanks
I'm doubt that you have unlocked Bootloader, that's really a big problem here...
If your bootloader is unlocked, our mentioned steps should work fine.
Did you really unlock bootloader? And didn't locked it again accidentally while using miflash?
Sent from my Mi 10 Pro using Tapatalk
The way you describe your problem it seems you had twrp and you booted into it.
Can you tell me what happens when you run
Fastboot flash recovery twrp.img (use your filename)
IronSingh said:
The way you describe your problem it seems you had twrp and you booted into it.
Can you tell me what happens when you run
Fastboot flash recovery twrp.img (use your filename)
Click to expand...
Click to collapse
1. I have bootloader unlocked via miunlock
2. I had booted into TWRP .. it failed to wipe data many times..
3. I installed TWRP and now it does not allow me to do anything ..
4. Wont go to TWRP wont go to Mi recovery and will just go to fastboot
5. MiFlash wont flash as it has anti rollback check error tried all fastboot roms EU and CN
6. Trying to recover it via MIUI recovery loader but it wont download from servers either ..
<img src="https://i.ibb.co/KNjRdNL/twrp.jpg" alt="twrp" border="0">
https://ibb.co/KNjRdNL this was the error message while wiping data
sanish4u said:
1. I have bootloader unlocked via miunlock
2. I had booted into TWRP .. it failed to wipe data many times..
3. I installed TWRP and now it does not allow me to do anything ..
4. Wont go to TWRP wont go to Mi recovery and will just go to fastboot
5. MiFlash wont flash as it has anti rollback check error tried all fastboot roms EU and CN
6. Trying to recover it via MIUI recovery loader but it wont download from servers either ..
https://ibb.co/KNjRdNL this was the error message while wiping data
Click to expand...
Click to collapse
Try another TWRP
Sent from my Mi 10 Pro using Tapatalk
ted presley said:
Try another TWRP
https://1drv.ms/u/s!Amo9DwwPZk-vg9gNxQ-IcpcHDWTI7A
Sent from my Mi 10 Pro using Tapatalk
Click to expand...
Click to collapse
Thanks ted it did solve the problem
thanks for all the support
ted presley said:
Try another TWRP
Sent from my Mi 10 Pro using Tapatalk
Click to expand...
Click to collapse
I installed miui 12 with the twrp provided. it booted into the system.
I want to install gapps so it try to go back to twrp by using vloume down and power the phone goes to fastboot.
Volume up and power will load xiaomi recovery v3.0
Volume up and down with power will load MIUI rom recovery
What is going wrong why am i not able to load TWRP now ..
sanish4u said:
I installed miui 12 with the twrp provided. it booted into the system.
I want to install gapps so it try to go back to twrp by using vloume down and power the phone goes to fastboot.
Volume up and power will load xiaomi recovery v3.0
Volume up and down with power will load MIUI rom recovery
What is going wrong why am i not able to load TWRP now ..
Click to expand...
Click to collapse
Unless you use custom MIUI rom, stock MIUI always overwrite TWRP.
BTW, if you flash official China Dev rom, no need to flash GAPPs, just install additional play store apk (plus additional latest play service framework if needed) from apkmirror, all other necessary things installed by Xiaomi already.
Sent from my Mi 10 Pro using Tapatalk
ted presley said:
Try another TWRP
Sent from my Mi 10 Pro using Tapatalk
Click to expand...
Click to collapse
thank you brother <3

OnePlus 8t KB2001 stuck in a loop

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.

Categories

Resources