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

Stuck Rooting @ tf300t

hi guys,
i was following this thread guide http://forum.xda-developers.com/showthread.php?t=1668173
and while i'm on step 5, i accidentally pick the wipe data (available options are RCK, Android and Wipe Data)
now, i am stuck in this
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
and totally unable to mount sdcard, emmc. Hopefully my tablet hasn't bricked yet.

johnson234 said:
hi guys,
i was following this thread guide http://forum.xda-developers.com/showthread.php?t=1668173
and while i'm on step 5, i accidentally pick the wipe data (available options are RCK, Android and Wipe Data)
now, i am stuck in this View attachment 2454401 and totally unable to mount sdcard, emmc. Hopefully my tablet hasn't bricked yet.
Click to expand...
Click to collapse
I remember on the old bootloader that ended in and insta-brick, but idk which BL you are on.

cmendonc2 said:
I remember on the old bootloader that ended in and insta-brick, but idk which BL you are on.
Click to expand...
Click to collapse
By BL u mean bootloader? My stock bootloader is 4.2.1 Jelly Bean. I tried to dl the twrp.blob from the twrp website with -4.2 and try to use the terminal emulator thingy but it still boot into CWM based Recovery.
However, I just bought the ROM Toolbox Pro in Google Play and use the 'Flash Recovery' but it search my whole tablet and returns nothing while i have already copy and paste the twrp.blob into the/sdcard/

johnson234 said:
By BL u mean bootloader? My stock bootloader is 4.2.1 Jelly Bean. I tried to dl the twrp.blob from the twrp website with -4.2 and try to use the terminal emulator thingy but it still boot into CWM based Recovery.
However, I just bought the ROM Toolbox Pro in Google Play and use the 'Flash Recovery' but it search my whole tablet and returns nothing while i have already copy and paste the twrp.blob into the/sdcard/
Click to expand...
Click to collapse
Edit: I am a first timer a.k.a. newbie. Sorry for that if i don't understand the short form/ slang u used.

johnson234 said:
By BL u mean bootloader? My stock bootloader is 4.2.1 Jelly Bean. I tried to dl the twrp.blob from the twrp website with -4.2 and try to use the terminal emulator thingy but it still boot into CWM based Recovery.
However, I just bought the ROM Toolbox Pro in Google Play and use the 'Flash Recovery' but it search my whole tablet and returns nothing while i have already copy and paste the twrp.blob into the/sdcard/
Click to expand...
Click to collapse
Wait it boots into android? What exactly are you trying to do? Just install the Superuser binaries for root or get a custom ROM?

cmendonc2 said:
Wait it boots into android? What exactly are you trying to do? Just install the Superuser binaries for root or get a custom ROM?
Click to expand...
Click to collapse
I plan to root it into a custom rom but ended up installing cwm which I later found out to be incompatible with my device. This is because I thought that everyone need to undergo these three process (root>install recovery>install rom) now I'm trying to remove or replace this cwm with a twrp then I can start installing my custom rom. I have already root my tablet with supersu (kingo). Did I do anything wrong on my steps above? If yes, please enlighten me. Thanks
anyway, what's a super user binary?

johnson234 said:
I plan to root it into a custom rom but ended up installing cwm which I later found out to be incompatible with my device. This is because I thought that everyone need to undergo these three process (root>install recovery>install rom) now I'm trying to remove or replace this cwm with a twrp then I can start installing my custom rom. I have already root my tablet with supersu (kingo). Did I do anything wrong on my steps above? If yes, please enlighten me. Thanks
anyway, what's a super user binary?
Click to expand...
Click to collapse
OK download the -42 TWRP recovery for jellybean onto your computer. Use fastboot (http://forum.xda-developers.com/showthread.php?p=42407269) to flash the bootloader to your tablet with:
Code:
fastboot flash recovery TWRP.img -i 0x0b05
Then reboot into Android and reboot again into TWRP to flash a custom ROM.

cmendonc2 said:
OK download the -42 TWRP recovery for jellybean onto your computer. Use fastboot (http://forum.xda-developers.com/showthread.php?p=42407269) to flash the bootloader to your tablet with:
Code:
fastboot flash recovery TWRP.img -i 0x0b05
Then reboot into Android and reboot again into TWRP to flash a custom ROM.
Click to expand...
Click to collapse
Sorry to tell you but everytime i try to fastboot, (tried this even before posting the problem here) i get this error. Waiting for like 10mins, the 'waiting for device' message is still there.
Command I used,
fastboot flash recovery TWRP.img -i 0x0b05
Click to expand...
Click to collapse
After pressing enter, i get this
< waiting for device >
Click to expand...
Click to collapse
Edit; sorry for the screenshot, typed the command wrong but tried it with the correct 1 but the outcome still the same.

I'm thinking that is it usb drivers problem? currently running on Win8 Professional 64bit.

johnson234 said:
I'm thinking that is it usb drivers problem? currently running on Win8 Professional 64bit.
Click to expand...
Click to collapse
Fastboot utility is very sensitive to connection type. It can refuse to work on some laptops and usb ports on front pannel of desktop PC. Also do not use usb hub or tablet dock with fastboot. And if Windows device manager shows tablet as something like "asus bootloader interface" or "asus fastboot interface" (don't remember exact name) is probably shouldn't be a driver issue.

Graiden05 said:
Fastboot utility is very sensitive to connection type. It can refuse to work on some laptops and usb ports on front pannel of desktop PC. Also do not use usb hub or tablet dock with fastboot. And if Windows device manager shows tablet as something like "asus bootloader interface" or "asus fastboot interface" (don't remember exact name) is probably shouldn't be a driver issue.
Click to expand...
Click to collapse
It has these 2 (see attachment) and I even can use ASUS SYNC perfectly. So i guess the usb driver wont be a problem?

johnson234 said:
It has these 2 (see attachment) and I even can use ASUS SYNC perfectly. So i guess the usb driver wont be a problem?
View attachment 2457522
Click to expand...
Click to collapse
Did You know that to use fastboot tablet should be loaded in fastboot mode? If You connect it in fastboot mode and Windows shows no recognised fastboot or bootloader interface You need a proper driver.

So, you suggest that i need to use a different pc to do the fastboot thing? What are the drivers do i need to install? Where can i download it? Maybe my wind8 64bit professional got some flaw/bug. Thanks for helping. Will try it out when i get back home.

cmendonc2 said:
OK download the -42 TWRP recovery for jellybean onto your computer. Use fastboot (http://forum.xda-developers.com/showthread.php?p=42407269) to flash the bootloader to your tablet with:
Code:
fastboot flash recovery TWRP.img -i 0x0b05
Then reboot into Android and reboot again into TWRP to flash a custom ROM.
Click to expand...
Click to collapse
I get something like this. But when i reboot into android and reboot it, i still get boot into CWM recovery. Nothing changed

Update : I try flashing the TWRP recovery again, but now its freezing on the fastboot mode. Probably still installing. Hopefully everything went well and i can successfully install it.

Graiden05 said:
Did You know that to use fastboot tablet should be loaded in fastboot mode? If You connect it in fastboot mode and Windows shows no recognised fastboot or bootloader interface You need a proper driver.
Click to expand...
Click to collapse
After i run this command
fastboot -i 0x0b05 flash recovery TWRP.img
Click to expand...
Click to collapse
it freeze.(I have waiting for 30mins but still nothing significant comes up.)
There is three option to choose from (RCK, Android and WipeData)
Now under the "Device and Printer", there is a fastboot devices (unspecified). But when i see it in properties of this fastboot device, it's manufacturer is still under ClockworkMod. See attachment

Try this guide.

Moto G 3rd gen (XT1540) stuck on bootloader warning screen after SuperSU

I'm trying to root my Moto G 3rd generation. I looked around a bit and started using a guide from a website called "the unlockr" (which I can't link to) and it all seemed to be going well until the very end. I got to Part 5 "Rooting the Motorola Moto G (3rd Gen) Using SuperSU" and everything seemed to be going well, however on reboot it seems to be stuck on the bootloader warning screen. Maybe I'm being impatient but its been sitting there for a while and I fear that I've broken something.
I've read around a bit and a few threads/people in similar situations recommend flashing to a stock rom and starting again but I'm afraid I'll find a way to make things worse.

Did you make a backup before you flashed SuperSU?
Lollipop or marshmallow?
I believe stock marshmallow needs systemless root, google it there is a SuperSU systemless version out there.
If you took a backup first, just restore and try again

hossman said:
Did you make a backup before you flashed SuperSU?
Lollipop or marshmallow?
I believe stock marshmallow needs systemless root, google it there is a SuperSU systemless version out there.
If you took a backup first, just restore and try again
Click to expand...
Click to collapse
No, in my infinite wisdom I didn't take a backup. It seemed so simple before I started I didn't think I'd need it.
I'll look into SuperSU systemless but if I can't get my phone to turn on, how do I load the files to flash it? Can I transfer it using USB debugging or something?

You will most likely need to flash factory image
Check here
http://forum.xda-developers.com/showthread.php?t=3169639
[INDEX][Osprey][Merlin] Moto G Factory Firmware Images
After that you can reflash recovery and make a backup before you start tinkering again.
Follow the directions linked in that thread to the T
---------- Post added at 11:38 AM ---------- Previous post was at 11:20 AM ----------
Before you flash factory image, maybe you could try flashing just stock boot.IMG through fastboot. Or maybe even squid kernel

hossman said:
You will most likely need to flash factory image
Check here
http://forum.xda-developers.com/showthread.php?t=3169639
[INDEX][Osprey][Merlin] Moto G Factory Firmware Images
After that you can reflash recovery and make a backup before you start tinkering again.
Follow the directions linked in that thread to the T
---------- Post added at 11:38 AM ---------- Previous post was at 11:20 AM ----------
Before you flash factory image, maybe you could try flashing just stock boot.IMG through fastboot. Or maybe even squid kernel
Click to expand...
Click to collapse
Finally got around to trying your advice, but I can't get ADB to recognize the phone at all. When I try to get a list of devices this is what I'm greeted with.
Code:
C:\Program Files (x86)\Minimal ADB and Fastboot>adb devices
List of devices attached
This is what my fastboot screen looks like.
{
"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"
}
Phone also shows up in Windows device manager. I dont remember the first line saying "Secure" before. Could that be part of the problem?

RTWinter said:
Finally got around to trying your advice, but I can't get ADB to recognize the phone at all. When I try to get a list of devices this is what I'm greeted with.
This is what my fastboot screen looks like.
Phone also shows up in Windows device manager. I dont remember the first line saying "Secure" before. Could that be part of the problem?
Click to expand...
Click to collapse
Which command did you use? adb devices or fastboot devices?

Henriquefeira said:
Which command did you use? adb devices or fastboot devices?
Click to expand...
Click to collapse
Hah, oh wow. I was using adb devices. Fastboot returns the phone.
One thing I'm not sure of, though, is how to push the recovery image to the phone. Someone online said you can use adb push to do so but will that work with fastboot?

RTWinter said:
Hah, oh wow. I was using adb devices. Fastboot returns the phone.
One thing I'm not sure of, though, is how to push the recovery image to the phone. Someone online said you can use adb push to do so but will that work with fastboot?
Click to expand...
Click to collapse
All info here http://forum.xda-developers.com/2015-moto-g/orig-development/twrp-twrp-moto-g-2015-t3170537

Henriquefeira said:
All info here http://forum.xda-developers.com/2015-moto-g/orig-development/twrp-twrp-moto-g-2015-t3170537
Click to expand...
Click to collapse
I tried the command fastboot flash recovery.img and I have the .img in the correct directory on my computer. However, I get the following output.
Code:
unknown partition 'recovery.img'
error: cannot determine image filename for 'recovery.img'
I tried using fastboot boot to temporarily load the .img but all that does is get me to a screen that says "No Command."
EDIT
Whoops, sorry. Realized I should have been using "fastboot flash recovery recovery.img" instead. Trying that now.

So I've tried this tutorial that hossman linked to but I still get the "No command" error when I try to go into the recovery menu.
Stuck here again, sorry to be a bother but I'm in over my head.

RTWinter said:
I tried the command fastboot flash recovery.img and I have the .img in the correct directory on my computer. However, I get the following output.
I tried using fastboot boot to temporarily load the .img but all that does is get me to a screen that says "No Command."
EDIT
Whoops, sorry. Realized I should have been using "fastboot flash recovery recovery.img" instead. Trying that now.
Click to expand...
Click to collapse
RTWinter said:
So I've tried this tutorial that hossman linked to but I still get the "No command" error when I try to go into the recovery menu.
Stuck here again, sorry to be a bother but I'm in over my head.
Click to expand...
Click to collapse
Download the "twrp-osprey-3.0.2-r1.img" image from the thread link that I gave you and move the image to your ADB and FB folder, after that booted on the bootloader of your phone use this command fastboot flash recovery twrp-osprey-3.0.2-r1.img

Stuck at fastboot (rooted) - Need help please

Hey guys, I'm in trouble. Need urgent help.
I was trying to install OOS & xXx rom from a clean install. But after flashing OOS & TWRP, probably I boot into wrong Slot. So now I'm stuck with Fastboot mode, cannot even go to Recovery. Can anyone help me out here so that I don't have to format the phone & re-unlock again?
TIA

nipun1110 said:
Hey guys, I'm in trouble. Need urgent help.
I was trying to install OOS & xXx rom from a clean install. But after flashing OOS & TWRP, probably I boot into wrong Slot. So now I'm stuck with Fastboot mode, cannot even go to Recovery. Can anyone help me out here so that I don't have to format the phone & re-unlock again?
TIA
Click to expand...
Click to collapse
If wrong slot is the only thing you messed up,
hook the phone in fastboot mode to PC and use the adb command (assuming you have appropriate drivers/adb already installed on your pc):
fastboot --set-active=_a
Change the slot from a to b if slot a does not get you to recovery. This command simply make either slot a or b active so you can boot into the correct slot.
Make sure you copy the command exactly as it's posted
Good luck!

Gr8man001 said:
If wrong slot is the only thing you messed up,
hook the phone in fastboot mode to PC and use the adb command (assuming you have appropriate drivers/adb already installed on your pc):
fastboot --set-active=_a
Change the slot from a to b if slot a does not get you to recovery. This command simply make either slot a or b active so you can boot into the correct slot.
Make sure you copy the command exactly as it's posted
Good luck!
Click to expand...
Click to collapse
Hello, thanks a lot for your prompt response. But it is showing this error.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

nipun1110 said:
Hello, thanks a lot for your prompt response. But it is showing this error.
Click to expand...
Click to collapse
How current are your fastboot (and adb) executables? From the command line, try entering:
Code:
adb version
I'm getting Android Debug Bridge version 1.0.40. If you're seeing something older than that, try a more recent version of adb and fastboot.

maigre said:
How current are your fastboot (and adb) executables? From the command line, try entering:
Code:
adb version
I'm getting Android Debug Bridge version 1.0.40. If you're seeing something older than that, try a more recent version of adb and fastboot.
Click to expand...
Click to collapse
Finally I got the solution. Thanks man. that command prompt u sent me was a little incorrect. There will be no "_" before "a". Thanks a lot for your help. Highly grateful.

nipun1110 said:
Finally I got the solution. Thanks man. that command prompt u sent me was a little incorrect. There will be no "_" before "a". Thanks a lot for your help. Highly grateful.
Click to expand...
Click to collapse
That wasn't me. It was Gr8man001 that gave you the advice that worked.

nipun1110 said:
Finally I got the solution. Thanks man. that command prompt u sent me was a little incorrect. There will be no "_" before "a". Thanks a lot for your help. Highly grateful.
Click to expand...
Click to collapse
maigre said:
That wasn't me. It was Gr8man001 that gave you the advice that worked.
Click to expand...
Click to collapse
true command : '''' fastboot --set-active=a '''' is it?
For me not work... please help.
https://i.hizliresim.com/pbOkpJ.png

Same thing here. In addition, I am unable to find a newer version of adb. Mine is 1.0.32.
I bricked my phone trying to update twrp. It will reboot to fastboot but not to system. A reboot to system has a dark screen and a small blue light in the notch. I'm thinking (and hoping) that changing the active slot will get it going again. I updated to Experience when the phone was new and want to go Pie, so the original should be in the other slot.
Any help will be appreciated.

zulu657 said:
Same thing here. In addition, I am unable to find a newer version of adb. Mine is 1.0.32.
I bricked my phone trying to update twrp. It will reboot to fastboot but not to system. A reboot to system has a dark screen and a small blue light in the notch. I'm thinking (and hoping) that changing the active slot will get it going again. I updated to Experience when the phone was new and want to go Pie, so the original should be in the other slot.
Any help will be appreciated.
Click to expand...
Click to collapse
Try the msm recovery tool, just Google how to unbrick OnePlus 6, it'll wipe your phone and install OOS 5.x.x but it will help you for sure

szybki_ben said:
Try the msm recovery tool, just Google how to unbrick OnePlus 6, it'll wipe your phone and install OOS 5.x.x but it will help you for sure
Click to expand...
Click to collapse
I looked at that one first, but would much rather swap the partitions and see if that will save it before trying the full wipe. Also looked at the Qualcomm drivers and can't seem to get that to work either. I am more used to working on a chromebook and going back to Windoze has been a challenge.

zulu657 said:
I looked at that one first, but would much rather swap the partitions and see if that will save it before trying the full wipe. Also looked at the Qualcomm drivers and can't seem to get that to work either. I am more used to working on a chromebook and going back to Windoze has been a challenge.
Click to expand...
Click to collapse
I don't think that you have to install Qualcomm drivers, I didn't install them and it still worked

szybki_ben said:
I don't think that you have to install Qualcomm drivers, I didn't install them and it still worked
Click to expand...
Click to collapse
The drivers were for another unbrick solution, I believe. I've looked at so many it's now hard to keep them separate. My original quest was to make another slot active. Another member tried the fastboot text and it didn't work -- same for me. A few posts later said to check the adb version. Mine is 1.0.32 and apparently there is now 1.0.40. I cannot find that one. The fastboot text was: fastboot --set-active=a. Didn't work for me either. Said unknown command.
I can boot into twrp but it is stuck on the opening screen.. Possible I can fastboot a new twrp and save it that way.

zulu657 said:
The drivers were for another unbrick solution, I believe. I've looked at so many it's now hard to keep them separate. My original quest was to make another slot active. Another member tried the fastboot text and it didn't work -- same for me. A few posts later said to check the adb version. Mine is 1.0.32 and apparently there is now 1.0.40. I cannot find that one. The fastboot text was: fastboot --set-active=a. Didn't work for me either. Said unknown command.
I can boot into twrp but it is stuck on the opening screen.. Possible I can fastboot a new twrp and save it that way.
Click to expand...
Click to collapse
If you can boot into recovery then booting a fresh img is a good idea, good luck!

szybki_ben said:
If you can boot into recovery then booting a fresh img is a good idea, good luck!
Click to expand...
Click to collapse
Just tried that one -- No Cigar!!! I followed the instructions for installing recovery on a new install. It said to use the text: fastboot boot recoveryimgrecovery.img I had renamed the Blu-spark img to recovery.img. The result was: no file or directory with this name. I was in the folder with adb, fastboot, recovery.img and all the rest of the files for OP6.
There used to be a way to install twrp with adb if I recall, but I can't find it. I know it was for an earlier phone. I have had OnePlus phones from the first one.
Very frustrating!!! I hate to wipe the phone because this should be a simple thing. Of course those are the ones that really get you....

Hmmmm, evidently the command fastboot set active=a is not a command in adb v1.0.32. When I tried it, I got a list of the commands and that one isn't in it.
Trying to find a later version of adb without success.
There has to be a way to change the active partition without formatting the phone. The phone had the original OS and I upgraded to Experience when I got it and have been using it ever since. Experience should be on another partition, so if I can change partitions, I should be on the original OS.
Would that not be correct???

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?