Database Info

[Q] Nexus S w/ CM 7.1.0 (no load & no recovery)

Can anyone help me with this Ive got a Nexus S, with the latest stable vers. of Cyanogen (update-cm-7.1.0-NS-signed) and ClockworkMod as the recovery image. Was working great then all of a sudden the phone will not load past the "Google" unlocked padlock image OR go into recovery mode. I can get into the bootloader alright (vol+ key & power button) and it confirms that the phone's still "UNLOCKED". All I get, on the screen, when I try to get into ClockworkMod is "Google" and the unlocked padlock image.
Can't even get into the SD card when I hook the phone up to my PC. Tried flashing CWM says that its sent and written but still wont load.
Any ideas how I can at least get into recovery mode? Once i'm in, in theory (if there's nothing terminal, hardware-wise) I can wipe the phone, mount the sd card, put a fresh vers. of CyanogenMod on it and start again.

Wrong section.

Soooooo moved.
Obligatory YOU MORON BLAH BLAH RABBLE RABBLE!!!!
....
Seriously though, what version of the Nexus S do you have? Just want to rule out any ID10T erros first. Second what CMW did you flash via fastboot? Thridly what was your fastboot command?

ackte11 said:
Can anyone help me with this Ive got a Nexus S, with the latest stable vers. of Cyanogen (update-cm-7.1.0-NS-signed) and ClockworkMod as the recovery image. Was working great then all of a sudden the phone will not load past the "Google" unlocked padlock image OR go into recovery mode. I can get into the bootloader alright (vol+ key & power button) and it confirms that the phone's still "UNLOCKED". All I get, on the screen, when I try to get into ClockworkMod is "Google" and the unlocked padlock image.
Can't even get into the SD card when I hook the phone up to my PC. Tried flashing CWM says that its sent and written but still wont load.
Any ideas how I can at least get into recovery mode? Once i'm in, in theory (if there's nothing terminal, hardware-wise) I can wipe the phone, mount the sd card, put a fresh vers. of CyanogenMod on it and start again.
Click to expand...
Click to collapse
How did you root it?
You just need to use fastboot to flash CWM & a new rom
Example for the rom:
fastboot update ROMFILENAME.ZIP -w
For more info on fastboot
http://wiki.cyanogenmod.com/wiki/Fastboot
Edit: There, got you the Cyanogenmod page. It's a step by step guide. Skip the bootloader unlocking section. Do all the rest.
http://wiki.cyanogenmod.com/wiki/Nexus_S:_Full_Update_Guide

slimdizzy said:
Soooooo moved.
Obligatory YOU MORON BLAH BLAH RABBLE RABBLE!!!!
....
Seriously though, what version of the Nexus S do you have? Just want to rule out any ID10T erros first. Second what CMW did you flash via fastboot? Thridly what was your fastboot command?
Click to expand...
Click to collapse
sorry bout posting in the wrong section. But Ive got the GT-I9020 version, Second I tried to flash versions 3.0.2.4-crespo, 4.0.0.2-crespo, and 5.0.2.0. Nothing responded.
$ fastboot flash recovery recovery-clockwork-4.0.0.2-crespo.img

ackte11 said:
sorry bout posting in the wrong section. But Ive got the GT-I9020 version, Second I tried to flash versions 3.0.2.4-crespo, 4.0.0.2-crespo, and 5.0.2.0. Nothing responded.
$ fastboot flash recovery recovery-clockwork-4.0.0.2-crespo.img
Click to expand...
Click to collapse
Do you have a working adb setup on your computer?
Put your device in fastboot mode ( VOL up + power button)
Make sure it's properly connected and interfacing with adb (you can type "adb devices" and you should see your device in the list)
If you don't see any string of characters after typing adb devices, then you don't have a working adb setup. You need either a standalone adb or the android SDK.

polobunny said:
How did you root it?
You just need to use fastboot to flash CWM & a new rom
Example for the rom:
fastboot update ROMFILENAME.ZIP -w
For more info on fastboot
---wiki.cyanogenmod.com/wiki/Fastboot
Edit: There, got you the Cyanogenmod page. It's a step by step guide. Skip the bootloader unlocking section. Do all the rest ---.cyanogenmod.com/wiki/Nexus_S:_Full_Update_Guide
Click to expand...
Click to collapse
tried that and got these results
$ fastboot update update-cm-7.1.0-NS-signed.zip -w
archive does not contain 'android-info.txt'
archive does not contain 'android-product.txt'
error: update package has no android-info.txt or android-product.txt

I have the android sdk but after "adb devices" its saying command not found

ackte11 said:
I have the android sdk but after "adb devices" its saying command not found
Click to expand...
Click to collapse
on a mac? also what about "fastboot devices"?

Linux Ubuntu 11.04 and Windows 7 "fastboot devices" recognizes it and shows the serial number. adb on windows runs the command but just comes up blank

ackte11 said:
Linux Ubuntu 11.04 and Windows 7 "fastboot devices" recognizes it and shows the serial number. adb on windows runs the command but just comes up blank
Click to expand...
Click to collapse
Alright. Try to flash CWM recovery first, as stated in the Cyanogenmod guide. Then once that's done, boot back into CWM and flash CM7.

Did that and it says that everything goes through, move down to recovery and it just loops the "google" padlock screen

ackte11 said:
Did that and it says that everything goes through, move down to recovery and it just loops the "google" padlock screen
Click to expand...
Click to collapse
Ah okay, maybe a corrupted boot.img
Download the full 2.3.6 rom for your model
i9020a
i9020t/i9023
You can get the model in fastboot mode at the top if you're unsure of which you own.
Extract the ZIP contents and grab hold of boot.img. Flash this boot.img using fastboot
Example: fastboot flash boot boot.img
Once that is done, reboot to fastboot and flash CWM. Then from CWM flash superuser and whichever ROM you want.

polobunny said:
Ah okay, maybe a corrupted boot.img
Download the full 2.3.6 rom for your model
i9020a
i9020t/i9023
You can get the model in fastboot mode at the top if you're unsure of which you own.
Extract the ZIP contents and grab hold of boot.img. Flash this boot.img using fastboot
Example: fastboot flash boot boot.img
Once that is done, reboot to fastboot and flash CWM. Then from CWM flash superuser and whichever ROM you want.
Click to expand...
Click to collapse
Nothings working. flashed the boot then CWM still cant get into recovery. Just right back to the "google" page

I am not sure if this works on the nexus s but give it a try.
Instead of flashing the recovery try and boot it. Change the command to fastboot boot recovery .....instead of flash.

albundy2010 said:
I am not sure if this works on the nexus s but give it a try.
Instead of flashing the recovery try and boot it. Change the command to fastboot boot recovery .....instead of flash.
Click to expand...
Click to collapse
still no go.

i am having the exact same problem, my computer can see my phone, but nothing is working. anyone have any input??? it seems like i can not write to certain parts of the sd card, it says, FAILED (remote: Write Fail)
trying to run an update. see how the image says it was copied over correctly? ive also tried ereasing it as well..
{
"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"
}
No boot or recovery img

This post specifically helped me.
http://forum.xda-developers.com/showpost.php?p=19531979&postcount=30
just rename the file "install-recovery.sh" which is in the /etc folder. You can only access it with a root file manager (rootexplorer $4 on the market)
make sure your new file is not ending with .sh
It appears that this file keeps writing stock recovery to your phone. Once you erase it, flash CWM recovery and then flash your rom. Hope it helps.

Nice catch. Didn't even think about it getting rewritten every boot.
Sent from my Nexus S using xda premium

Android 10 update TWRP not booting

Fastboot Stuck as saying booting with logo. Any Solution?
Sent from my GM1911 using Tapatalk

Were you updating to android 10 from 9 or from 10 beta? is it the 2 white dots spinning around the red dot?

I have a problem, I updated from 9 to 10 and lost root and twrp. Is there any possibility for the author: to root and have twrp again? I tried the fastboot version of the twrp installation. img in cmd and kind of says ok, but the phone is on the fastboot logo and nothing happens ?

equlizer said:
Were you updating to android 10 from 9 or from 10 beta? is it the 2 white dots spinning around the red dot?
Click to expand...
Click to collapse
From 9
Sent from my GM1911 using Tapatalk

Jarek84 said:
I have a problem, I updated from 9 to 10 and lost root and twrp. Is there any possibility for the author: to root and have twrp again? I tried the fastboot version of the twrp installation. img in cmd and kind of says ok, but the phone is on the fastboot logo and nothing happens [emoji29]
Click to expand...
Click to collapse
I got a solution
Twrp 3.3.1.65
Sent from my GM1911 using Tapatalk

Jarek84 said:
Is there any possibility for the author: to root and have twrp again? I tried the fastboot version of the twrp installation. img in cmd and kind of says ok, but the phone is on the fastboot logo and nothing happens
Click to expand...
Click to collapse
You can not flash TWRP in fastboot on this device. And that never worked for this device. I know it worked on lots of previous Android devices (standard method to install TWRP). But you should wipe from your mind that notion that it works on the 7 Pro.
The process for Android 9 was to boot TWRP (very different from flash TWRP). But fastboot boot command doesn't work on the Android 10 update. This is similar to the situation when the 7 Pro was first released, and OnePlus fixed the fastboot boot command a bit later.
Current root method, is to flash a patched boot image. But lots of folks seem to be having trouble rooting the new Android 10 stable (even using the proper method). Flashing the stock boot.img is another option (to get the phone working, but no root).

First fastboot stucked
Second no partition found
{
"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 GM1911 using Tapatalk

You are not supposed to "flash" twrp through windows. Once you "boot" with windows, you install twrp through twrp.

redpoint73 said:
You can not flash TWRP in fastboot on this device. And that never worked for this device. I know it worked on lots of previous Android devices (standard method to install TWRP). But you should wipe from your mind that notion that it works on the 7 Pro.
The process for Android 9 was to boot TWRP (very different from flash TWRP). But fastboot boot command doesn't work on the Android 10 update. This is similar to the situation when the 7 Pro was first released, and OnePlus fixed the fastboot boot command a bit later.
Current root method, is to flash a patched boot image. But lots of folks seem to be having trouble rooting the new Android 10 stable (even using the proper method). Flashing the stock boot.img is another option (to get the phone working, but no root).
Click to expand...
Click to collapse
False, it was possible on android 9 to flash twrp on this device. It worked perfectly. With android 10 that's not possible unfortunately unless you have it already installed on android pie and you are upgrading. Use the unofficial twrp latest build and flash it after you flash the android 10 update in twrp and you are golden.

Hello All,
I decided to hop back in and root my device. I'm running into the same issue as OP. I try to boot into TWRP and i just get a "fastboot mode" screen. Can anyone clarify if this is doable as of now? and how?
Sorry, I havent rooted a phone in 7+ years.

links2586 said:
Hello All,
I decided to hop back in and root my device. I'm running into the same issue as OP. I try to boot into TWRP and i just get a "fastboot mode" screen. Can anyone clarify if this is doable as of now? and how?
Sorry, I havent rooted a phone in 7+ years.
Click to expand...
Click to collapse
Look here. https://forum.xda-developers.com/oneplus-7-pro/how-to/android-q-4th-developer-preview-t3953997

hallo dare said:
Look here. https://forum.xda-developers.com/oneplus-7-pro/how-to/android-q-4th-developer-preview-t3953997
Click to expand...
Click to collapse
That doesn't seem to work for me since I can't see my case, which is the same as @Jarek84
Only the stock boot.img boots for me. magisk_patched.img puts me in a bootloop and I'm stuck at the fastboot logo whenever I try to fastboot boot twrp.img (neither official nor the .65 one here, the modified one).
Any help would be appreciated to get root and twrp back.
Thanks!

hallo dare said:
False, it was possible on android 9 to flash twrp on this device. It worked perfectly. With android 10 that's not possible unfortunately unless you have it already installed on android pie and you are upgrading. Use the unofficial twrp latest build and flash it after you flash the android 10 update in twrp and you are golden.
Click to expand...
Click to collapse
Can you cite anyone who flashed twrp from fastboot in op7p.
---------- Post added at 06:12 PM ---------- Previous post was at 06:09 PM ----------
whisky_ said:
That doesn't seem to work for me since I can't see my case, which is the same as @Jarek84
Only the stock boot.img boots for me. magisk_patched.img puts me in a bootloop and I'm stuck at the fastboot logo whenever I try to fastboot boot twrp.img (neither official nor the .65 one here, the modified one).
Any help would be appreciated to get root and twrp back.
Thanks!
Click to expand...
Click to collapse
. Have you tried patching your own boot.img instead of flashing the one provided on the guide?

Everyone who has ever flashed twrp. But if you want evidence,
https://forum.xda-developers.com/showpost.php?p=79677185&postcount=1

hallo dare said:
Everyone who has ever flashed twrp. But if you want evidence,
https://forum.xda-developers.com/showpost.php?p=79677185&postcount=1
Click to expand...
Click to collapse
If you read a little more carefully you will see that the thread you're linking to says exactly what redpoint73 wrote. I.e. in order to flash TWRP one must first fastboot boot the TWRP-image, and then flash the TWRP-zip from within TWRP.
No one said it's not possible to flash TWRP. What was said was that it's not possible to do it from fastboot.
Cheers.

branko.s67 said:
If you read a little more carefully you will see that the thread you're linking to says exactly what redpoint73 wrote. I.e. in order to flash TWRP one must first fastboot boot the TWRP-image, and then flash the TWRP-zip from within TWRP.
No one said it's not possible to flash TWRP. What was said was that it's not possible to do it from fastboot.
Cheers.
Click to expand...
Click to collapse
Obviously you cannot flash from fastboot, but what I'm referencing to is that it was said "twrp cannot be flashed from fastboot" , but that it can be achieved by the method i pointed out to get to recovery to flash. It's not just a case of saying it cannot be flashed and covered the method in one sweeping statement. There is a method, but as we all know, this is not possible currently with Android 10

hallo dare said:
Obviously you cannot flash from fastboot, but what I'm referencing to is that it was said "twrp cannot be flashed from fastboot" , but that it can be achieved by the method i pointed out to get to recovery to flash.
Click to expand...
Click to collapse
Once you have booted recovery, you are no longer in fastboot.
Just try a fastboot command while in TWRP, and see how that works for you.

redpoint73 said:
Once you have booted recovery, you are no longer in fastboot. Duh!!!!
Click to expand...
Click to collapse
Hold on a sec. If you are going to act in a childish manner how are we to discuss this properly.
To even get to twrp you have to use the .img file in fastboot. So "fastboot flash recovery filename.img"
So you are flashing in fastboot to get to twrp recovery.
Your comment said that you couldn't flash twrp via fastboot and never could with this phone. That's half correct. What I'm saying is you can flash the .img file to access twrp before flashing the zip file on Android pie. Unfortunately that's not the case with Android 10.

hallo dare said:
To even get to twrp you have to use the .img file in fastboot. So "fastboot flash recovery filename.img"
So you are flashing in fastboot to get to twrp recovery.
Click to expand...
Click to collapse
Wrong. Your command is incorrect.
The correct command is: fastboot boot twrp.img
Once you are booted to TWRP, you can than flash TWRP installer zip (not the TWRP img).
Just look at the post you quoted above in response #14.
This phone does not even have a recovery partition. Recovery resides on boot.img for this device due to A/B partition scheme.
My original statements hold as correct.

redpoint73 said:
Wrong. Your command is incorrect.
The correct command is: fastboot boot twrp.img
Just look at the post you quoted above in response #14.
This phone does not have a recovery partition. Recovery resides on boot.img for this device.
My original statements hold as correct.
Click to expand...
Click to collapse
O my God, that recognised contributor tag is going to your head.
The command with "boot" boots into TWRP recovery. The command with "flash", flashes the .img file in fastboot mode on Android pie.

Realme x50 Pro Fastboot Mode Lock Help ?

can someone help me phone is stuck in fastboot mode i can't enter recovery mode i can't flash file
{
"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"
}

can someone help me phone is stuck in fastboot mode i can't enter recovery mode i can't flash file

smhzhl said:
can someone help me phone is stuck in fastboot mode i can't enter recovery mode i can't flash file
Click to expand...
Click to collapse
Me too, i have updated to Android 11_ UI 2.0 via VPN fake IP Guangdong, after that I install TWRP and my phone is stuck in fastboot mode i can't enter recovery mode i can't flash file, plz help me! Thanks all so much!

Once you update to android 11 you cant flash recovery through fast boot with that old twrp.img file. Only way is to stay in android 10. Dont try to flash android 10 ozip file through color os recovery if you are in android 11. I got bootloop and couldn't recover.
Or you can flash an old .ofp file from realme flash tool to android 10 (which wipes everything) and use fastboot to flash twrp recovery.

With Android 11 A/B partitioning became mandatory (Google). Installing TWRP became risky for that reason. This "issue" exists for more than 1 year on OnePlus phones for example.

Extract this https://mirrors.lolinet.com/firmware/gsi/Pixel/Pixel-AB-11-20200909-ErfanGSI.img-0125.7z and fastboot flash the extracted .img into system.

Do you know if it's possible to install Magisk on a A/B Android 11 Realme device ? Personally the modified boot way doesn't work, it doesn't boot on my x50 pro :/

Check with treble checker app from playstore. If seamless updates are available then you have A/B partitions. And basically if you have that there wont be actual "recovery" partition. So you cannot use the flash recovery command in fastboot. For that you have to flash that recovery in boot partition like "fastboot flash boot "recovery".img"
I dont know much about it and i am still on android 10. I am not a developer so correct me if i am wrong.

Tried what jjgvv said but I got this:
fastboot flash system Pixel-AB-11-20200909-ErfanGSI.img
Sending sparse 'system' 1/4 (786428 KB) OKAY [ 18.067s]
Writing 'system' FAILED (remote: 'Partition not found')
fastboot: error: Command failed
What shoud I do?

My phone is RMX2071 Chinese model
Where can I find the OFP for the RMX071 Chinese phone?
Thanks guys

Touche said:
Tried what jjgvv said but I got this:
fastboot flash system Pixel-AB-11-20200909-ErfanGSI.img
Sending sparse 'system' 1/4 (786428 KB) OKAY [ 18.067s]
Writing 'system' FAILED (remote: 'Partition not found')
fastboot: error: Command failed
What shoud I do?
Click to expand...
Click to collapse
Is your phone booting after that?
You can try flashing the old twrp in place of boot as recovery partition is not there. This will eventually flash onto A/B partition for temporary twrp.

Lamhehe said:
Me too, i have updated to Android 11_ UI 2.0 via VPN fake IP Guangdong, after that I install TWRP and my phone is stuck in fastboot mode i can't enter recovery mode i can't flash file, plz help me! Thanks all so much!
Click to expand...
Click to collapse
same happend to me

jhosharath said:
Is your phone booting after that?
You can try flashing the old twrp in place of boot as recovery partition is not there. This will eventually flash onto A/B partition for temporary twrp.
Click to expand...
Click to collapse
Hi mate,
My phone is not booting it is stuck in the bootloader like the photo in the post.
I tried to flask the old TWRP in boot partition too but it is still not booting or entering the recovery..
I think my only option is flash an OFP file, but I can't find it for RMX2071 Chinese phone.
Help! Hahaha

Touche said:
Hi mate,
My phone is not booting it is stuck in the bootloader like the photo in the post.
I tried to flask the old TWRP in boot partition too but it is still not booting or entering the recovery..
I think my only option is flash an OFP file, but I can't find it for RMX2071 Chinese phone.
Help! Hahaha
Click to expand...
Click to collapse
Bad luck bro. RMX 2071 doesnt have an official ofp file i think. You can try entering edl mode and flash the firmware from that.
You can get the firmware from officialrom.com site. Instructions are given there.
Try to enter edl from fastboot by typing fasboot reboot edl or fastboot oem edl command. If not try the button combination given there.
Or you can go to realme service center and they will do it for free if under warranty.

jhosharath said:
Bad luck bro. RMX 2071 doesnt have an official ofp file i think. You can try entering edl mode and flash the firmware from that.
You can get the firmware from officialrom.com site. Instructions are given there.
Try to enter edl from fastboot by typing fasboot reboot edl or fastboot oem edl command. If not try the button combination given there.
Or you can go to realme service center and they will do it for free if under warranty.
Click to expand...
Click to collapse
Bro! I spent all day yesterday trying to understand why it is not flashing. I still don't know.
I do not think RMX2071 has A/B partition. Tried to use fastboot "fastboot --set-active=a" returns no partition found.
I found an OFP file from "https://www.officialroms.com/realme-x50-pro-flash-file/" .
I tried to use the Realme flasher with this OFP but I'm getting " Invalid sparse file format at header magi" when it starts to flash the super.img. It finishes flash everything but It still doesn't boot. It goes back to the Bootloader/fastboot.
I tried using the MSM Download Tool but all the files I found are compacted and has password.
I found another OFP file but it is inside a compacted file from GSMMafia and I do not want to pay to get a password. It's not about the money but principles. hehehe.
No way to get to EDL mode. it says no partition found too.
Any Ideas?
Thanks for the help!

Bro i think its better to take to service center and get it flashed for free if under warranty or they may charge a little if out of warranty period. I dont have much idea about these realme stuffs. Even i had a similar problem but my fastboot/bootloader wont stay and keeps restarting for every 30 secs for which i couldnt do anything. So i took to service center and they did it in 4 hours. They flashed firmware using edl mode. Thereafter i never upgraded to android 11. Sorry couldnt help you much. Good luck

Touche said:
Bro! I spent all day yesterday trying to understand why it is not flashing. I still don't know.
I do not think RMX2071 has A/B partition. Tried to use fastboot "fastboot --set-active=a" returns no partition found.
I found an OFP file from "https://www.officialroms.com/realme-x50-pro-flash-file/" .
I tried to use the Realme flasher with this OFP but I'm getting " Invalid sparse file format at header magi" when it starts to flash the super.img. It finishes flash everything but It still doesn't boot. It goes back to the Bootloader/fastboot.
I tried using the MSM Download Tool but all the files I found are compacted and has password.
I found another OFP file but it is inside a compacted file from GSMMafia and I do not want to pay to get a password. It's not about the money but principles. hehehe.
No way to get to EDL mode. it says no partition found too.
Any Ideas?
Thanks for the help!
Click to expand...
Click to collapse
did you find any solution? im in the same boat like you

afgboy said:
did you find any solution? im in the same boat like you
Click to expand...
Click to collapse
Not yet bro. I still have some thing to try.
I'll let you know if I find a solution.
Please let me know if you find before me

Touche said:
Not yet bro. I still have some thing to try.
I'll let you know if I find a solution.
Please let me know if you find before me
Click to expand...
Click to collapse
sure the same goes for you bro

Touche said:
Not yet bro. I still have some thing to try.
I'll let you know if I find a solution.
Please let me know if you find before me
Click to expand...
Click to collapse
And me too cuz I have an Oppo 10x zoom having same problem unlocked bootloader, stuck in Fastboot mode

ONEPLUS 8T - only fastboot - no edl, msm sees nothing!? [SOLVED]

[SOLVED] Please read through, hopefully this helps someone!​
Ive tried numerous threads and followed the steps always end up with some sort of error.
Device manager shows:
Kedacom USB Device>Android Bootloader Interface
errors:
fastboot: error: Failed to boot into userspace fastboot; one or more components might be unbootable.
fastboot: error: Could not check if partition xbl has slot all
fastboot: error: Could not check if partition xbl_config has slot all
and continues with this error for what ever its trying to flash "has slot all"
flashing logical patitions error:
no such partition or partition not found
I keep researching and every video that shows what to do or posts, i can only get so far before my results dont match and there is no option or description for what to do if getting an error.
edit: adb devices shows nothing, but fastboot devices shows serial.
TIA

I think you have the wrong drivers, try these and check in windows update if your Qualcomm drivers are up to date in the optional updates. Also if fastboot is working and the bootloader is unlocked, you can download the latest full oos 12 and flash it all.

LaviLev said:
Ive tried numerous threads and followed the steps always end up with some sort of error.
Device manager shows:
Kedacom USB Device>Android Bootloader Interface
errors:
fastboot: error: Failed to boot into userspace fastboot; one or more components might be unbootable.
fastboot: error: Could not check if partition xbl has slot all
fastboot: error: Could not check if partition xbl_config has slot all
and continues with this error for what ever its trying to flash "has slot all"
flashing logical patitions error:
no such partition or partition not found
I keep researching and every video that shows what to do or posts, i can only get so far before my results dont match and there is no option or description for what to do if getting an error.
edit: adb devices shows nothing, but fastboot devices shows serial.
TIA
Click to expand...
Click to collapse
If you need the latest oos I can link it here.

Nimiskiv said:
If you need the latest oos I can link it here.
Click to expand...
Click to collapse
Please do! currently DLing the drivers posted Thank you!

https://android.googleapis.com/packages/ota-api/package/435fc808f603bbc8a63ce30fd944676a65a61d6f.zip
LaviLev said:
Please do! currently DLing the drivers posted Thank you!
Click to expand...
Click to collapse

Oh but be careful that's for kebab 2005
Here's the repo
[OnePlus 8T][ROM][OTA][Oxygen OS] Repo of Oxygen OS Builds
Added 11.0.5.6 KB05AA full zip from support website to OP
forum.xda-developers.com

Nimiskiv said:
Oh but be careful that's for kebab 2005
Here's the repo
[OnePlus 8T][ROM][OTA][Oxygen OS] Repo of Oxygen OS Builds
Added 11.0.5.6 KB05AA full zip from support website to OP
forum.xda-developers.com
Click to expand...
Click to collapse
Anything with "kebab" in the beginning is OOS 12

Nimiskiv said:
https://android.googleapis.com/packages/ota-api/package/435fc808f603bbc8a63ce30fd944676a65a61d6f.zip
Click to expand...
Click to collapse
ok ty, looks like is c11 the first android 12 update for the OP8T, downloading now. Hopefully i can get it to flash.

LaviLev said:
ok ty, looks like is c11 the first android 12 update for the OP8T, downloading now. Hopefully i can get it to flash.
Click to expand...
Click to collapse
Use the MSM tool first

Nimiskiv said:
Use the MSM tool first
Click to expand...
Click to collapse

can not get phone to edl stuck in fastboot only. tried all the commands and physical button configs and still only get fastboot. Any workarounds?

I downloaded Fastboot Enhance, which allowed me to flash a bin file, but the phone still wont boot. I had to check ignore unknown partitions for it to flash. Now i can access fastbootd and when choose boot to recovery it loads what looks to a limited recovery similiar to fastbootd.
Any advice?
{
"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"
}

LaviLev said:
I downloaded Fastboot Enhance, which allowed me to flash a bin file, but the phone still wont boot. I had to check ignore unknown partitions for it to flash. Now i can access fastbootd and when choose boot to recovery it loads what looks to a limited recovery similiar to fastbootd.
Any advice?
View attachment 5683905
Click to expand...
Click to collapse
That's a stock OOS recovery you're seeing.

BillGoss said:
That's a stock OOS recovery you're seeing.
Click to expand...
Click to collapse
Any advice or known methods to get me running from here?

LaviLev said:
Any advice or known methods to get me running from here?
Click to expand...
Click to collapse
Run the MSM tool in edl, since now it should work fine. Also did the drivers work? If not you need to uninstall them in windows device manager, then reinstall them

LaviLev said:
Any advice or known methods to get me running from here?
Click to expand...
Click to collapse
Well, you've never said in your initial post what it was that you were trying to do.
Now that you are in the stock recovery you can select Advanced> reboot fastboot.
This will put you into fastbootd mode where you can do things like flash partitions and, more importantly, flash the logical partitions.
But, if you don't know how to do this and get out of whatever mess you're in , then use MSM Tool to reset your phone.

BillGoss said:
Well, you've never said in your initial post what it was that you were trying to do.
Now that you are in the stock recovery you can select Advanced> reboot fastboot.
This will put you into fastbootd mode where you can do things like flash partitions and, more importantly, flash the logical partitions.
But, if you don't know how to do this and get out of whatever mess you're in , then use MSM Tool to reset your phone.
Click to expand...
Click to collapse
I just reread my initial post, damn I started typing mid thought.. my bad!
I tried msmtool, but it doesn't load up a com port. All the listed methods with holding both vol buttons after already hitting start then plugging in did not work as I don't think it sees it at all.
Haven't found a thread with fastboot instructions that didn't require something I couldn't get to, to restore the phone. other methods fail writing to numerous areas when flashing.

trying this...
[GUIDE] Unbrick or restore to OOS using only fastboot
This guide will only work up to OOS 11. This guide is for users that can't or just don't want to download MsmDownloadTool. Linux users especially, since the tool is not available for linux. All you need is a recent version of android tools with...
forum.xda-developers.com

LaviLev said:
trying this...
[GUIDE] Unbrick or restore to OOS using only fastboot
This guide will only work up to OOS 11. This guide is for users that can't or just don't want to download MsmDownloadTool. Linux users especially, since the tool is not available for linux. All you need is a recent version of android tools with...
forum.xda-developers.com
Click to expand...
Click to collapse
OK was able to execute the first 4 fastboot commands, the it hung on the first flash --slot=all
In the end i just boot the phone in fasbootd using fastboot enhance and then using the flash bin file option in FE to flash the OOS 12 FILE @Nimiskiv shared.
Final boots into OOS, hope all works I will be testing to see for a day or two before i switch back from the 6, also before all this the 8T went a12_c11 to a12_c33
right now update for c20 came up!?
Any additional insight or final thoughts appreciated. Thanks again all!

LaviLev said:
OK was able to execute the first 4 fastboot commands, the it hung on the first flash --slot=all
In the end i just boot the phone in fasbootd using fastboot enhance and then using the flash bin file option in FE to flash the OOS 12 FILE @Nimiskiv shared.
Final boots into OOS, hope all works I will be testing to see for a day or two before i switch back from the 6, also before all this the 8T went a12_c11 to a12_c33
right now update for c20 came up!?
Any additional insight or final thoughts appreciated. Thanks again all!
Click to expand...
Click to collapse
check if EDL is working now, its very important for edl to work, because if something happens in the future, you need edl to reset.

Please Help Me. Xiaomi 12x. Bricked Phone after trying to root. Stuck in fastboot bootloop.

Hello.
I've followed instructions as in this thread https://forum.xda-developers.com/t/root-psyche-root-xiaomi-12x-with-magisk.4455293/
only 1 thing I did wrong is downloading 13.02 boot.img file instead of 13.04 boot.img which wasn't available at that time.
After I flashed phone was stuck in Recovery mode bootloop, then for some reason it just got stuck in normal bootloop.
after that I downloaded 13.04 boot.img which was for my version, patched it on another phone in magisk, repeated instructions and now it's stuck in fastboot bootloop.
I also want to mention that I don't have external SD card so I was using boot.img directly from my pc.
Please help me.
There was solution to use Mi Phone Assistant but program doesn't detect my phone.
Edit: I'm green in these kind of termins so want to mention that it doesn't constant rebooting, just everytime I try to boot it goes into fastboot.

If phone is ADB enabled try this
1. Connect Windows desktop computer with phone via USB cable what came with phone
2. In Windows Command prompt run command sequence
Code:
adb devices
adb reboot
to exit phone into NORMAL boot ( i.e. system mode -> ANDROID OS)

xXx yYy said:
If phone is ADB enabled try this
1. Connect Windows desktop computer with phone via USB cable what came with phone
2. In Windows Command prompt run command sequence
Code:
adb devices
adb reboot
to exit phone into NORMAL boot ( i.e. system mode -> ANDROID OS)
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"
}
When in fastboot adb devices didn't find any devices
this screenshot is after I entered in recovery mode but you see it yourself...

Looks like USB Debugging isn't got successfully enabled on phone.

xXx yYy said:
Looks like USB Debugging isn't got successfully enabled on phone.
Click to expand...
Click to collapse
Does it mean that phone is forever bricked? Can you throw me some words of hope please.

it is not forever bricked. you just messed up with the boot image. try the troubleshooting steps from the link you ve posted with a different cable. or a different usb. or a different pc. the app should detect the phone at some point.

Fytdyh said:
it is not forever bricked. you just messed up with the boot image. try the troubleshooting steps from the link you ve posted with a different cable. or a different usb. or a different pc. the app should detect the phone at some point.
Click to expand...
Click to collapse
Thank you for advice, I will try.

Fytdyh said:
it is not forever bricked. you just messed up with the boot image. try the troubleshooting steps from the link you ve posted with a different cable. or a different usb. or a different pc. the app should detect the phone at some point.
Click to expand...
Click to collapse
Tried on different PC, didn't work. I doubt it's USB cable because it's original and I unlocked bootloader with it before. I'm desperate...
Edit: I think it's because of software that my phone doesn't get detected, https://prnt.sc/G232WPcRRqC1 mi unlock tool does detect it although only in fastboot mode, not recovery.
edit2: mi pc suite detects my phone in Fastboot mode but writes this... https://prnt.sc/4dB06CtvIfhz

can you enter in recovery mode ? when you enter in recovery mode, what options do you have ?

kiknalex said:
Tried on different PC, didn't work. I doubt it's USB cable because it's original and I unlocked bootloader with it before. I'm desperate...
Edit: I think it's because of software that my phone doesn't get detected, https://prnt.sc/uwS8qnna60rX mi unlock tool does detect it...
Click to expand...
Click to collapse
Hey, just download the Fastboot ROM for your device, extract the boot.img from there and place it in the platform-tools folder.
Then open CMD inside the platform-tools folder and execute the below command to flash the stock boot.img file [assuming you are in the Fastboot Mode]:
Code:
fastboot flash boot boot.img
You may then boot to the OS via the below command
Code:
fastboot reboot

Sidenote: To avoid such scenarios in the near future, please refrain from directly flashing the boot.img. Rather first temporary boot via
Code:
fastboot boot magisk_patched_boot.img
And then use the Direct Install feature of Magisk for permanent root

Fytdyh said:
can you enter in recovery mode ? when you enter in recovery mode, what options do you have ?
Click to expand...
Click to collapse
https://prnt.sc/Oyjs9lxGVFX8 It's same as in this picture, not my phone tho. I didn't try erase data because I think it will disable USB debugging and I chose to wait for answers on forums.

binary**# said:
Sidenote: To avoid such scenarios in the near future, please refrain from directly flashing the boot.img. Rather first temporary boot via
Code:
fastboot boot magisk_patched_boot.img
And then use the Direct Install feature of Magisk for permanent root
Click to expand...
Click to collapse
Hey, thanks for help, I want to clarify 2 things:
1.
Hey, just download the Fastboot ROM for your device, extract the boot.img from there and place it in the platform-tools folder.
Then open CMD inside the platform-tools folder and execute the below command to flash the stock boot.img file [assuming you are in the Fastboot Mode]:
Do I do it with stock boot.img or I should patch it?
2. Isn't that the same as instructions I linked in thread post?

kiknalex said:
Hey, thanks for help, I want to clarify 2 things:
1.
Hey, just download the Fastboot ROM for your device, extract the boot.img from there and place it in the platform-tools folder.
Then open CMD inside the platform-tools folder and execute the below command to flash the stock boot.img file [assuming you are in the Fastboot Mode]:
Do I do it with stock boot.img or I should patch it?
2. Isn't that the same as instructions I linked in thread post?
Click to expand...
Click to collapse
flash the stock image first. after you get a fully fuctional phone attempt the rooting guide. as in, booting the phone as normal, be relieved that you did not hard brick it. then try again, and follow every step of the way.

Fytdyh said:
flash the stock image first. after you get a fully fuctional phone attempt the rooting guide. as in, booting the phone as normal, be relieved that you did not hard brick it. then try again, and follow every step of the way.
Click to expand...
Click to collapse
I just did it and situation is same, it enters bootloops in fastboot... I just remembered one thing and don't know how important it is but maybe makes a difference.
If I recall correctly, when I first flashed patched.img, the installation process wrote sending boot_b but after that it always said sending boot_a
like in this screenshot https://prnt.sc/t931it_cCodT .
Maybe it is root of problems?
I also want to mention a little detail that I rememeber.
When I was checking MIUI updates on site, the release was Stable BETA but only recovery was available, although now fastboot is available too, it's just Stable - without Beta, Perhaps my ROM was Stable Beta and not stable? It's 13.04 GLOBAL.

well, it does have importance. newer devices have 2 partition for booting. while older have only 1.
try this
fastboot flash boot_a boot.img
fastboot flash boot_b boot.img
fastboot reboot

kiknalex said:
Hey, thanks for help, I want to clarify 2 things:
1.
Hey, just download the Fastboot ROM for your device, extract the boot.img from there and place it in the platform-tools folder.
Then open CMD inside the platform-tools folder and execute the below command to flash the stock boot.img file [assuming you are in the Fastboot Mode]:
Do I do it with stock boot.img or I should patch it?
2. Isn't that the same as instructions I linked in thread post?
Click to expand...
Click to collapse
Oh, I forgot to mention that you should only download the same version of Fastboot ROM that was installed on your device. And then flash the stock boot.img from that ROM to both slots using the commands given by @Fytdyh

Fytdyh said:
well, it does have importance. newer devices have 2 partition for booting. while older have only 1.
try this
fastboot flash boot_a boot.img
fastboot flash boot_b boot.img
fastboot reboot
Click to expand...
Click to collapse
Tried still same... maybe it's something with vbmeta.img?

or if your inactive partition is still non-corrupted [fingers crossed] then you could try booting it via that slot. For that, change the active partition via
Code:
fastboot set_active other
and then
Code:
fastboot reboot

binary**# said:
Oh, I forgot to mention that you should only download the same version of Fastboot ROM that was installed on your device. And then flash the stock boot.img from that ROM to both slots using the commands given by @Fytdyh
Click to expand...
Click to collapse
I downloaded same. :|.
I don't mind using another ROM if it will fix my issues, is it even possible to install from situation like this?