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

Help please.

Long time android user and "moder" here. Never owned an HTC device other than the ONE which I didn't have long. I just acquired this phone from some guy at my job who tried to mod it and he has it rooted with CM10 (which is ICS right? because it's ICS on it don't remember if it was 10 or not). I've downloaded, many, many roms over the past few days from JB to KK and tried to flash them and I successfully flash them in CWM but it just stays on the white HTC screen, and doesn't boot up. Any idea why this is happening?

C-4Nati said:
Long time android user and "moder" here. Never owned an HTC device other than the ONE which I didn't have long. I just acquired this phone from some guy at my job who tried to mod it and he has it rooted with CM10 (which is ICS right? because it's ICS on it don't remember if it was 10 or not). I've downloaded, many, many roms over the past few days from JB to KK and tried to flash them and I successfully flash them in CWM but it just stays on the white HTC screen, and doesn't boot up. Any idea why this is happening?
Click to expand...
Click to collapse
if you are on S-ON flash 4ext recovery
format all partitions except sdcard from 4ext
enable smartflash from 4ext
flash the rom
done

@C-4Nati also..if your bootloader is still s-on state (and stil using cwm recovery)..did you already flashing a boot.img from the rom that you had already installed..?
if not yet..you can try flashing it through fastboot.. "fastboot flash boot boot.img"

JJeamy said:
@C-4Nati also..if your bootloader is still s-on state (and stil using cwm recovery)..did you already flashing a boot.img from the rom that you had already installed..?
if not yet..you can try flashing it through fastboot.. "fastboot flash boot boot.img"
Click to expand...
Click to collapse
No he didn't flash a boot.IMG and its s on. No idea to do what you said :/ any guides you could link to

C-4Nati said:
No he didn't flash a boot.IMG and its s on. No idea to do what you said :/ any guides you could link to
Click to expand...
Click to collapse
If we know ur bootloader details then would make things easier, (turn off phone then press volume down + power) anyway, both these links will get u to where u want to be
http://forum.xda-developers.com/showthread.php?t=1864053
Or here. http://forum.xda-developers.com/showthread.php?t=1631861
Also as @rzr86 said, flash latest 4ext recovery (added below)

jmcclue said:
If we know ur bootloader details then would make things easier, (turn off phone then press volume down + power) anyway, both these links will get u to where u want to be
http://forum.xda-developers.com/showthread.php?t=1864053
Or here. http://forum.xda-developers.com/showthread.php?t=1631861
Also as @rzr86 said, flash latest 4ext recovery (added below)
Click to expand...
Click to collapse
This is it.
{
"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"
}

C-4Nati said:
This is it.
Click to expand...
Click to collapse
ok, have u fastboot setup on ur pc?

jmcclue said:
ok, have u fastboot setup on ur pc?
Click to expand...
Click to collapse
I'm not sure so I'm assuming that means no lol.

C-4Nati said:
I'm not sure so I'm assuming that means no lol.
Click to expand...
Click to collapse
click the first link i posted n set it up

jmcclue said:
click the first link i posted n set it up
Click to expand...
Click to collapse
I installed the sdk and fastboot and everything, and when I enter the fastboot oem token indentifier command all the command prompt says is waiting on device. I've double checked all instructions and it just keeps saying waiting on device.
Edit- I tried to flash the 4ext in cwm and it said installation aborted everytime.

C-4Nati said:
I installed the sdk and fastboot and everything, and when I enter the fastboot oem token indentifier command all the command prompt says is waiting on device. I've double checked all instructions and it just keeps saying waiting on device.
Edit- I tried to flash the 4ext in cwm and it said installation aborted everytime.
Click to expand...
Click to collapse
you are already unlocked your bootloader..so you don't need get identifier token again to unlock your bootloader..
1. first way..like what rzr86 and jmcclue said above..because you're still s-on but already had unlocked bootloader..they've suggest you to installing 4ext recovery for the next future you can easily installing of custom rom...because 4ext recovery is already option "SmartFlash" that fuction can installing custom rom with automatically supported also installing a boot.img from the rom itself under s-on devices like yours..
to installing that 4ext recovery...you can download recovery.zip from here.., then extracted that recovery.zip file to get recovery.img file...then copied recovery.img file to your sdk / adb folder (that are a same place as your adb.exe and fastboot.exe), after that...you can boot your phone to bootloader mode..then select "FASTBOOT" from there, then plug your phone to pc..until indicator in the phone has "FASTBOOT-USB", after that you can open cmd from your adb folder (just press and hold shift + right click on empty space from that folder and select "Open command window here") ...then typing command "fastboot devices" ..see if the output has detect your phone serial number.. if so...then continued typing "fastboot flash recovery recovery.img" then "fastboot reboot-bootloader" done..now you can tested it go to your 4ext recovery..and now you can enabled it "SmartFlash" from tools option before you installing any custom rom from 4ext recovery...
2. second way...if you don't want change you cwm recovery..you can fix your booting stuck by just flashing a boot.img extracted from the rom.zip itself with manual flashing from fastboot..
to do that...firstly just copied rom.zip that you wanna installing to another folder..then extracting / unzipping that file...then copied boot.img to your adb / sdk (same place as your adb.exe and fastboot.exe) folder..then after you've already installing that custom rom from cwm..you must reboot your phone to bootloader again (don't booting the rom first), then select FASTBOOT from there..then plug your phone to pc until indicator in your phone has FASTBOOT-USB..then open cmd from your adb / sdk folder..then typing command "fastboot flash boot boot.img" then "fastboot reboot" done...now you can see that the phone can booting of the rom normally or not..
hope this help..

JJeamy said:
you are already unlocked your bootloader..so you don't need get identifier token again to unlock your bootloader..
1. first way..like what rzr86 and jmcclue said above..because you're still s-on but already had unlocked bootloader..they've suggest you to installing 4ext recovery for the next future you can easily installing of custom rom...because 4ext recovery is already option "SmartFlash" that fuction can installing custom rom with automatically supported also installing a boot.img from the rom itself under s-on devices like yours..
to installing that 4ext recovery...you can download recovery.zip from here.., then extracted that recovery.zip file to get recovery.img file...then copied recovery.img file to your sdk / adb folder (that are a same place as your adb.exe and fastboot.exe), after that...you can boot your phone to bootloader mode..then select "FASTBOOT" from there, then plug your phone to pc..until indicator in the phone has "FASTBOOT-USB", after that you can open cmd from your adb folder (just press and hold shift + right click on empty space from that folder and select "Open command window here") ...then typing command "fastboot devices" ..see if the output has detect your phone serial number.. if so...then continued typing "fastboot flash recovery recovery.img" then "fastboot reboot-bootloader" done..now you can tested it go to your 4ext recovery..and now you can enabled it "SmartFlash" from tools option before you installing any custom rom from 4ext recovery...
2. second way...if you don't want change you cwm recovery..you can fix your booting stuck by just flashing a boot.img extracted from the rom.zip itself with manual flashing from fastboot..
to do that...firstly just copied rom.zip that you wanna installing to another folder..then extracting / unzipping that file...then copied boot.img to your adb / sdk (same place as your adb.exe and fastboot.exe) folder..then after you've already installing that custom rom from cwm..you must reboot your phone to bootloader again (don't booting the rom first), then select FASTBOOT from there..then plug your phone to pc until indicator in your phone has FASTBOOT-USB..then open cmd from your adb / sdk folder..then typing command "fastboot flash boot boot.img" then "fastboot reboot" done...now you can see that the phone can booting of the rom normally or not..
hope this help..
Click to expand...
Click to collapse
Hey, I really really appreciate you trying to help. Both those directions are clear and I know I could easily do either but the only problem is for some reason my computer doesn't recognize the phone and when in fastboot mode it never says fastboot-usb and cmd always says waiting on device. I know usb debugging is enabled but I'm on an aosp rom so I didn't have the option to uncheck fastboot under power, is that the problem maybe? I have android SDK installed and the app "htc sync" so I'm not sure why it doesn't recognize the phone.
edit -it did end up saying "fastboot usb" but in cmd it still said waiting on device and when I typed fastboot devices no serial number came up.

C-4Nati said:
Hey, I really really appreciate you trying to help. Both those directions are clear and I know I could easily do either but the only problem is for some reason my computer doesn't recognize the phone and when in fastboot mode it never says fastboot-usb and cmd always says waiting on device. I know usb debugging is enabled but I'm on an aosp rom so I didn't have the option to uncheck fastboot under power, is that the problem maybe? I have android SDK installed and the app "htc sync" so I'm not sure why it doesn't recognize the phone.
Click to expand...
Click to collapse
what OS you have on your computer?

Mile_zdr said:
what OS you have on your computer?
Click to expand...
Click to collapse
Let me edit my previous post, as in the bootloader it did end up saying "fastboot usb" but in cmd it still said waiting on device and when I typed fastboot devices no serial number came up. I have windows 8.1

C-4Nati said:
Let me edit my previous post, as in the bootloader it did end up saying "fastboot usb" but in cmd it still said waiting on device and when I typed fastboot devices no serial number came up. I have windows 8.1
Click to expand...
Click to collapse
Could this have something to do with it? For some reason the device is recognized if I go into device and printers but it's not listed under the "this PC" area like all my other devices go to. It also wont let me browse the phones internal storage for some reason. http://i.imgur.com/FnhjwYa.png
edit - this is what it says while I'm in fastboot mode and plug the phone in.

C-4Nati said:
Could this have something to do with it? For some reason the device is recognized if I go into device and printers but it's not listed under the "this PC" area like all my other devices go to. It also wont let me browse the phones internal storage for some reason. http://i.imgur.com/FnhjwYa.png
edit - this is what it says while I'm in fastboot mode and plug the phone in.
Click to expand...
Click to collapse
i lot of people have problems with fasboot and win 8.1 i don't know does have solution, but try with win 7 if you have another computer

Mile_zdr said:
i lot of people have problems with fasboot and win 8.1 i don't know does have solution, but try with win 7 if you have another computer
Click to expand...
Click to collapse
I used my windows 7 pc and everything worked. You guys are all AWESOME! and I appreciate all the help. Now I'm having problems with getting signal lol -.- I purchased an unlock code from a website and when I put my t mobile sim it and the phone boots it says enter code and I do and it says network unlock successful but I won't get signal at all. I've rebooted and entered code again and taken sim out and put back in to no avail lol. This phone just won't be easy lol.

C-4Nati said:
I used my windows 7 pc and everything worked. You guys are all AWESOME! and I appreciate all the help. Now I'm having problems with getting signal lol -.- I purchased an unlock code from a website and when I put my t mobile sim it and the phone boots it says enter code and I do and it says network unlock successful but I won't get signal at all. I've rebooted and entered code again and taken sim out and put back in to no avail lol. This phone just won't be easy lol.
Click to expand...
Click to collapse
dial *#*#4636#*#* than go to phone information and set the network to WCDMA prefered see if it work

Mile_zdr said:
dial *#*#4636#*#* than go to phone information and set the network to WCDMA prefered see if it work
Click to expand...
Click to collapse
I did that an it didn't do anything. This is originally a T-Mobile phone but a local company called Cincinnati Bell (which is also a GSM/sim card using company) buys units to resell and locks them on their service. I have T-Mobile and paid for the unlock code so I could use T-Mobile on it but so far it's not working (though it says network unlock successful).

C-4Nati said:
I did that an it didn't do anything. This is originally a T-Mobile phone but a local company called Cincinnati Bell (which is also a GSM/sim card using company) buys units to resell and locks them on their service. I have T-Mobile and paid for the unlock code so I could use T-Mobile on it but so far it's not working (though it says network unlock successful).
Click to expand...
Click to collapse
?
I don't know what to tell you... :/ do you have another sim card from other carrier just to see everything work's okey?

Messed up big time?

Hi,
I am really not into flashing and stuff like this, but some weeks ago I successfully rooted my device and installed a custom bootloader (teamwin). Today I wanted to do a clean wipe to install cm11s on my N5. So I launched into recovery, selected "wipe" and unfortunatly I selected "advanced wipe" also. I checked everything and started the wipe process. Dont ask me why I did this, I wasnt thinking obviously. When I boot my device now, only the white Google font is visible and underneath there is a locker. I can start recovery but since I wiped everything I can not install the stock rom again. Also my PC doesnt recognize the N5 as a "harddrive" so I can not move the stock .zip to the device. The device manager is displaying it as ACER DEVICE, and under portable devices it is displayed as Nexus 5 with a yellow exclamation mark. Any tipps how I can get a rom on this device again?

Simple mate...
Download cm rom zip
Reboot into recovery
Mount ur storage
Put cm rom zip somewhere
Install that rom zip via recovery(twrp is recovery not the boot loader )
Flash gapps (optional if u want google services n apps) (u can do this later also)
Reboot

forstyy said:
Hi,
I am really not into flashing and stuff like this, but some weeks ago I successfully rooted my device and installed a custom bootloader (teamwin). Today I wanted to do a clean wipe to install cm11s on my N5. So I launched into recovery, selected "wipe" and unfortunatly I selected "advanced wipe" also. I checked everything and started the wipe process. Dont ask me why I did this, I wasnt thinking obviously. When I boot my device now, only the white Google font is visible and underneath there is a locker. I can start recovery but since I wiped everything I can not install the stock rom again. Also my PC doesnt recognize the N5 as a "harddrive" so I can not move the stock .zip to the device. The device manager is displaying it as ACER DEVICE, and under portable devices it is displayed as Nexus 5 with a yellow exclamation mark. Any tipps how I can get a rom on this device again?
Click to expand...
Click to collapse
First of app, TWRP is a custom recovery, not a custom bootloader.
Either ADB push a rom zip to your device while it's in recovery and flash it, or flash the factory images while in the bootloader. Links to guides for both of those are available in the first link of my signature.

Lethargy said:
First of app, TWRP is a custom recovery, not a custom bootloader.
Either ADB push a rom zip to your device while it's in recovery and flash it, or flash the factory images while in the bootloader. Links to guides for both of those are available in the first link of my signature.
Click to expand...
Click to collapse
Dont knw exactly but is mount storage an option in adb??? I jst suggested it lol

doctor_droid said:
Dont knw exactly but is mount storage an option in adb??? I jst suggested it lol
Click to expand...
Click to collapse
What do you mean lol?

Lethargy said:
What do you mean lol?
Click to expand...
Click to collapse
Like cwm has an option to mount storage...
Similarly does twrp has same option too?

doctor_droid said:
Like cwm has an option to mount storage...
Similarly does twrp has same option too?
Click to expand...
Click to collapse
As in browse files on a PC or what?

Lethargy said:
First of app, TWRP is a custom recovery, not a custom bootloader.
Either ADB push a rom zip to your device while it's in recovery and flash it, or flash the factory images while in the bootloader. Links to guides for both of those are available in the first link of my signature.
Click to expand...
Click to collapse
Yea sorry, I dont know what I am talking about exactly, just know the terms
So I adb pushed the image-hammerhead-ktu84p.zip to my device to /sdcard. When I want to install it from recovery and select the zip, it just says FAILED

forstyy said:
Yea sorry, I dont know what I am talking about exactly, just know the terms
So I adb pushed the image-hammerhead-ktu84p.zip to my device to /sdcard. When I want to install it from recovery and select the zip, it just says FAILED
Click to expand...
Click to collapse
You don't flash that in recovery lol!
Run this so it flashes and wipes everything:
{
"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"
}

Lethargy said:
You don't flash that in recovery lol!
Run this so it flashes and wipes everything:
Click to expand...
Click to collapse
huh, ok. this guide: http://forum.xda-developers.com/showthread.php?t=1667929 suggested to install it from there
When these are all done, from Recovery's main screen, select "Install ZIP from SD Card" and then "Choose file from SD Card" and select the ROM.zip file you just pushed from your computer to the SD Card. If you do not see the file, go back to Mounts and Storage and toggle them to say "Mount /sdcard/" and "Mount /system/" and then go back and try to fine the ROM.zip file. If you still do not see it, it was not pushed correctly...go back and ensure you were letter for letter with the name and the file path.
Click to expand...
Click to collapse

forstyy said:
huh, ok. this guide: http://forum.xda-developers.com/showthread.php?t=1667929 suggested to install it from there
Click to expand...
Click to collapse
Just push a cm rom made for ur hammerhead...

forstyy said:
huh, ok. this guide: http://forum.xda-developers.com/showthread.php?t=1667929 suggested to install it from there
Click to expand...
Click to collapse
image-hammerhead-ktu84p.zip isn't a flashable ROM zip, it's just a compressed archive of boot.img, cache.img, recovery.img, system.img and userdata.img
What the flash-all script does is:
1. fastboot flash bootloader bootloader-hammerhead-hhz11k.img
2. reboots bootloader
3. fastboot flash radio radio-hammerhead-m8974a-2.0.50.1.16.img
4. reboots bootloader again
5. fastboot -w update image-hammerhead-ktu84p.zip (-w = wipe, then "update image-hammerhead-ktu84p.zip" just flashes all the .img files in the zip, same as individually flashing each with fastboot)

Lethargy said:
image-hammerhead-ktu84p.zip isn't a flashable ROM zip, it's just a compressed archive of boot.img, cache.img, recovery.img, system.img and userdata.img
What the flash-all script does is:
1. fastboot flash bootloader bootloader-hammerhead-hhz11k.img
2. reboots bootloader
3. fastboot flash radio radio-hammerhead-m8974a-2.0.50.1.16.img
4. reboots bootloader again
5. fastboot -w update image-hammerhead-ktu84p.zip (-w = wipe, then "update image-hammerhead-ktu84p.zip" just flashes all the .img files in the zip, same as individually flashing each with fastboot)
Click to expand...
Click to collapse
Ok, thanks it worked. I am back online on stock again. When I start with fastboot (hope it is the right term ) with volume down+power, it says my phone is unlocked still. When I want to enter recovery mode I only see the android picture with a red triangle (looks like something bad). Does this mean I have to root+install a custom recovery again?

forstyy said:
Ok, thanks it worked. I am back online on stock again. When I start with fastboot (hope it is the right term ) with volume down+power, it says my phone is unlocked still. When I want to enter recovery mode I only see the android picture with a red triangle (looks like something bad). Does this mean I have to root+install a custom recovery again?
Click to expand...
Click to collapse
Its the bootloader fastboot is what's used in the bootloader. And yeah, flash a custom recovery then you're good to go!

forstyy said:
Ok, thanks it worked. I am back online on stock again. When I start with fastboot (hope it is the right term ) with volume down+power, it says my phone is unlocked still. When I want to enter recovery mode I only see the android picture with a red triangle (looks like something bad). Does this mean I have to root+install a custom recovery again?
Click to expand...
Click to collapse
Welcome to flashing world...now since u know how to revive ur phone... U will definately mess up it again...

doctor_droid said:
Like cwm has an option to mount storage...
Similarly does twrp has same option too?
Click to expand...
Click to collapse
Mount storage only works on a non-fuse /sdcard. Meaning either:
- device has removable sdcard
- device is not using fuse for internal storage.
Nexus 5 meets neither.
Sent from my Nexus 5 using Tapatalk

Lethargy said:
First of app, TWRP is a custom recovery, not a custom bootloader.
Either ADB push a rom zip to your device while it's in recovery and flash it, or flash the factory images while in the bootloader. Links to guides for both of those are available in the first link of my signature.
Click to expand...
Click to collapse
My thoughts exactly
sent from my thumbs

Same here I've messed my n5 up about 5 times these Google images come In handy

Thank you guys for your help, all is working again. Was a bit scary since this was the first time I did this.:fingers-crossed:

forstyy said:
Thank you guys for your help, all is working again. Was a bit scary since this was the first time I did this.:fingers-crossed:
Click to expand...
Click to collapse
The N5 is basically the best contemporary phone to soft brick or break. The support and tools available are great.

[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.

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?