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

[Q] All that bootloader jargon.

I was trying to understand what is fastboot. And then I got caught into all that bootloader jargon and couldn't differentiate one from the other. So I have a few questions. If someone could make me understand this stuff...I would be really grateful. Thanx guaranteed
1. What is fastboot? When I run fastboot commands through cmd...I get <waiting for device>.
2. How to get into fastboot mode...should I boot into bootloader? How?....
3. I know how to get into recovery...I'm rooted and have a custom recovery CWM. Is recovery same as bootloader?
4. Then what is download mode....how is it different from bootloader mode or recovery mode?
5. I tried running fastboot commands through cmd by entering recovery and download mode...but got the same message as in point 1. Whats wrong???
Has anybody tried using the fastboot commands on our galaxy r?
Sent from my GT-I9103 using xda premium

The-Droidster said:
I was trying to understand what is fastboot. And then I got caught into all that bootloader jargon and couldn't differentiate one from the other. So I have a few questions. If someone could make me understand this stuff...I would be really grateful. Thanx guaranteed
1. What is fastboot? When I run fastboot commands through cmd...I get <waiting for device>.
2. How to get into fastboot mode...should I boot into bootloader? How?....
3. I know how to get into recovery...I'm rooted and have a custom recovery CWM. Is recovery same as bootloader?
4. Then what is download mode....how is it different from bootloader mode or recovery mode?
5. I tried running fastboot commands through cmd by entering recovery and download mode...but got the same message as in point 1. Whats wrong???
Has anybody tried using the fastboot commands on our galaxy r?
Sent from my GT-I9103 using xda premium
Click to expand...
Click to collapse
1. Samsung phones don't actually have a fastboot
2. We have an unlocked bootloader , such bootloaders don't have fastboot AFAIK
3. Recovery =/= bootloader
4. Download Mode allows stock firmware to be "Downloaded" into your phone through USB
5. Fastboot is non-existent !
"I have to go. It's just....they really need me." - Sora

Fastboot and typical bootloader called "bootloader" exists on HTC devices. It's not the exactly same what recovery is. In order to boot to recovery u must enter the bootloader first there. We don't have something like this on Sammy. (Well, every phone has a bootloader but we don't have something corresponding to HTC-bootloader, which has many functions - you can even flash files through bootloader). Bootloader is simply the very first thing that is loaded when telephone starts. So if you screw bootloader your phone would be stone dead.
Both: Download Mode and Recovery can be categorized as a bootloader here.

m.kochan10 said:
Fastboot and typical bootloader called "bootloader" exists on HTC devices. It's not the exactly same what recovery is. In order to boot to recovery u must enter the bootloader first there. We don't have something like this on Sammy. (Well, every phone has a bootloader but we don't have something corresponding to HTC-bootloader, which has many functions - you can even flash files through bootloader). Bootloader is simply the very first thing that is loaded when telephone starts. So if you screw bootloader your phone would be stone dead.
Both: Download Mode and Recovery can be categorized as a bootloader here.
Click to expand...
Click to collapse
Wow nicely explained:good: But your last statement is a bit confusing....because htc phones can boot into 3 diff modes bootloader, recovery and download....so can recovery and download mode be categorised as bootloader or are they different in some respects?? I mean even our devices must be having the bootloader mode apart from recovery and download mode...only that we are not able to boot into it

HTC phones don't have download mode. It's kinda more complicated there. They don't have Odin-like program. FW is installed through self-extracted program - RUU***.exe, u can flash zips through bootloader but not always, and not all zips, you must create a gold card first, unlock bootloader, and label file to the one specific for device name (for example for HTC LEgend it was LEGEIMG.zip). Othewrise it won't be recognized by bootloader. Fastboot command is very useful if you for example want replace stock recovery with cwm (which is btw impossible with locked bootloader). HTC Bootloader (called even HBOOT) the one you're speaking now is using other words a phone service mode. That's how it looks.
{
"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"
}
AFAIK we don't have such service mode. We don't need it, our bootloader is unlocked. We can enter the recovery, and download mode directly and flash whatever we wish.
Anyway, here you have a good art about htc bootloader:
http://android.appstorm.net/general/opinion/were-htc-right-to-open-up-their-bootloader-policy/

m.kochan10 said:
HTC phones don't have download mode. It's kinda more complicated there. They don't have Odin-like program. FW is installed through self-extracted program - RUU***.exe, u can flash zips through bootloader but not always, and not all zips, you must create a gold card first, unlock bootloader, and label file to the one specific for device name (for example for HTC LEgend it was LEGEIMG.zip). Othewrise it won't be recognized by bootloader. Fastboot command is very useful if you for example want replace stock recovery with cwm (which is btw impossible with locked bootloader). HTC Bootloader (called even HBOOT) the one you're speaking now is using other words a phone service mode. That's how it looks.
AFAIK we don't have such service mode. We don't need it, our bootloader is unlocked. We can enter the recovery, and download mode directly and flash whatever we wish.
Anyway, here you have a good art about htc bootloader:
http://android.appstorm.net/general/opinion/were-htc-right-to-open-up-their-bootloader-policy/
Click to expand...
Click to collapse
This is great info.....This makes me understand a lot of things I was trying to learn over the past 2 days. Below I'm mentioning a few points that I have understood.....Please these are just assumptions of my understanding...I might be wrong....Plz cement my understanding by just saying either true or false....You may correct the wrong assumptions...no force
1. Users with unlocked bootloaders and the ability to boot into the bootloader (HTC) can do without a custom recovery...as they can do all that we do through CWM using the fastboot commands through cmd. (This point is clarified a bit from ur above post. Bootloader/fastboot mode can only replace a few features of CWM not all....CWM gives more advanced features. )
2. Samsung users have unlocked bootloaders but cannot boot into it so cannot use fastboot commands. They need to flash CWM through ODIN by entering download mode.
3. Download mode exclusive to samsung.
4. fastboot commands be used with locked bootloaders.
5. The boot.img is an image of the boot partition and same goes for recovery.img.
6. boot.img contains the kernel and the ramdisk..so the bootloader location first loads this partition into main memory and the kernel then loads the OS and other stuff.
7. HTC devices have access to bootloader (HBOOT) ie they can boot into the bootloader. From there they can use fastboot commands to direct the bootloader to boot into recovery mode....what this does is directs the bootloader to load the recovery partition into memory instead of the boot partition.
8. Samsung users cannot directly address the bootloader as they cannot boot into the bootloader and hence cannot use fastboot commands. The key combinations (Volume up + ok + Power) that sammy users use to get into recovery are directions to the bootloader to load the recovery partition instead of the boot partition.
9. On rooted phones, we can use apps to do the same thing from within the phone ie we are using apps with root access to instruct the bootloader to take us into recovery instead of using key combinations at boot.
10. Even htc users can do so apart from the ability to directly instruct the bootloader by booting into it.
Your help will be greatly appreciated
Note : Samsung here refers to mostly R and S2 as I know that nexus users can boot into the bootloader.

1) I've just used HTC and Samsung. No idea how it looks on SE, Moto or LG
2) No, I just wrote, we don't have it such HTC-type bootloader menu. Lock bootloader means: No custom flashing! unlocked bootloader: flash whatever you wish! It has nothing to do with cwm. CWM was just an example. Forget about it. I am talking about installation via bootloader now (With locked bootloader u won't be even able to install CWM! We have download mode for such installations. And it goes smoothly for us. You can thus easily replace recovery on Sammy but it is God damn hard process on HTC). Fastboot commands are unnecessary for Samsung since we can flash everything we want via Odin.
3) I don't know how it looks on other devices than Sammy and HTC
4) Yes, but I don't know if exclusively. Most of devices have locked bootloaders: Moto, HTC, SE...Don't know about LG. You need a fastboot mode (enabled in bootloader) and use fastboot commands for "heavy-flashing" for example....changing recovery, bootloaders. We can flash bootloaders via Odin but not via CWM, so u cannot really compare CWM to it. On the other hand you cannot do a full wipe in Odin etc.
5) boot.img is always a kernel, it's not a bootloader!!! recovery.img yes it's a recovery image but I've seen it only on SGR, on S2 kernel and recovery are integrated (bootloader is sbl1.img)
6) 7) 8) I am not that theoretical expert, sorry. U must google it. I don't know about booting partitions. But clearly: HBOOT has nothing to do with boot.img (more with sbl1.img). Bootloader is not a kernel partition!
HTC phones have just a different structure of bootloader, they have this (HBOOT) bootloader menu, and one of the options is recovery. (another is: fastboot mode ->fastboot usb, when connected to usb port, and then fastboot commands can be applied) They need fastboot commands for more heavyweight changes/flashing . We don't need it. We have (separately) recovery and download mode for heavy flashing. These are the only modes we can enter with key combos. And that's all we need to be happy!
9) 10) Yes, yes, you and they can do it even via terminal.apk
su -> reboot recovery or reboot download (sammies)
su -> reboot recovery or reboot bootloader (HTC)
Ok hope it helped little bit. It can be some minot shortcomings. I'm sorry but I must say EOT now (call of duties ). I recommend visit some htc, q&a section and read just for fun.

m.kochan10 said:
1) I've just used HTC and Samsung. No idea how it looks on SE, Moto or LG
2) No, I just wrote, we don't have it such HTC-type bootloader menu. Lock bootloader means: No custom flashing! unlocked bootloader: flash whatever you wish! It has nothing to do with cwm. CWM was just an example. Forget about it. I am talking about installation via bootloader now (With locked bootloader u won't be even able to install CWM! We have download mode for such installations. And it goes smoothly for us. You can thus easily replace recovery on Sammy but it is God damn hard process on HTC). Fastboot commands are unnecessary for Samsung since we can flash everything we want via Odin.
3) I don't know how it looks on other devices than Sammy and HTC
4) Yes, but I don't know if exclusively. Most of devices have locked bootloaders: Moto, HTC, SE...Don't know about LG. You need a fastboot mode (enabled in bootloader) and use fastboot commands for "heavy-flashing" for example....changing recovery, bootloaders. We can flash bootloaders via Odin but not via CWM, so u cannot really compare CWM to it. On the other hand you cannot do a full wipe in Odin etc.
5) boot.img is always a kernel, it's not a bootloader!!! recovery.img yes it's a recovery image but I've seen it only on SGR, on S2 kernel and recovery are integrated (bootloader is sbl1.img)
6) 7) 8) I am not that theoretical expert, sorry. U must google it. I don't know about booting partitions. But clearly: HBOOT has nothing to do with boot.img (more with sbl1.img). Bootloader is not a kernel partition!
HTC phones have just a different structure of bootloader, they have this (HBOOT) bootloader menu, and one of the options is recovery. (another is: fastboot mode ->fastboot usb, when connected to usb port, and then fastboot commands can be applied) They need fastboot commands for more heavyweight changes/flashing . We don't need it. We have (separately) recovery and download mode for heavy flashing. These are the only modes we can enter with key combos. And that's all we need to be happy!
9) 10) Yes, yes, you and they can do it even via terminal.apk
su -> reboot recovery or reboot download (sammies)
su -> reboot recovery or reboot bootloader (HTC)
Ok hope it helped little bit. It can be some minot shortcomings. I'm sorry but I must say EOT now (call of duties ). I recommend visit some htc, q&a section and read just for fun.
Click to expand...
Click to collapse
Thanx thanx thanx.......for ur time and patience and for helping me out.:good:

Urgent Help, time constraint - to Stock for return

I've been at this for like 8 hours going in circles. I have about 12 hours to figure this out. I am scheduled to go back to TMO to return this phone. Please help me.
While trying to revert back to stock, upon boot, at first there is a green icon, then it turns red w/ an exclamation point and just hangs there. It seems to have booted into the recovery because where it hangs, if i touch the "home" button, it disappears and shows me the cwm recovery main menu with a few errors relating to unable to mount SD. Its a very gimpy CWM with more than half of the commands/functions missing. (see pics below)
This is what I am currently getting in order....
{
"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"
}
- Boots to image 01
- Then to 02, here its trying to load/mount stuff, notice the SD icon and load bar near the bottom
- In 03 it looks like it ran into an error and hangs there
- Not sure why but I realized it boots straight into recovery. From 03, if i touch the home button I get 04. Notice all the stuff missing from cwm options
- 05 is what my HBoot / Bootloader looks like
-------------------------------
I am able to get back into HBoot / bootloader screen and can confirm that while in that mode the PC does recognize the device. But everything I flash does not work. When I run RUUs they seem to begin a process, but once that is done ( which isnt long), I would reboot but see nothing has changed. I tried to undo that stock recovery to access to NAND backups and start the process again but that Recovery doesn't have options for backups (strange?). Anyways, but can not flash another CWM successfully.
This is what I currently see when flashing a CWM now
c:\android-sdk\tools>fastboot flash recovery recovery-clockwork-touch-5.8.3.1-vi
lle.img
sending 'recovery' (6616 KB)...
OKAY [ 0.969s]
writing 'recovery'...
(bootloader) signature checking...
FAILED (remote: signature verify fail)
finished. total time: 2.210s
c:\android-sdk\tools>fastboot reboot
rebooting...
I am completely out of options now. I looked at all the stickies around here and other places but can not find anything that will work. I did my best to be as thorough as I can. Please let me know if there are more info that would help. Thanks ahead of time.

This is One S development forum. Questions should be posted in questions.
Simple fix. Boot into bootloader and factory reset. Reboot once again into bootloader and format /erase sd card. Remember all this is being done from bootloader and not recovery. Reboot once again into bootloader and connect usb to phone and use fastboot to push cwm or whatever recovery you want to phone. Your sd card should now be mounted.
Not entirely sure about the return to stock, but being able to mount is a huge step in the right direction. Hope this helped
Sent from my HTC One S using xda premium

Chris Boyer said:
This is One S development forum. Questions should be posted in questions.
Simple fix. Boot into bootloader and factory reset. Reboot once again into bootloader and format /erase sd card. Remember all this is being done from bootloader and not recovery. Reboot once again into bootloader and connect usb to phone and use fastboot to push cwm or whatever recovery you want to phone. Your sd card should now be mounted.
Not entirely sure about the return to stock, but being able to mount is a huge step in the right direction. Hope this helped
Sent from my HTC One S using xda premium
Click to expand...
Click to collapse
Sorry if I posted in the wrong place. Usually when I ask a flashing related question there someone tells me it should be asked in Development.
Anyways, I tried that but nothing changed. Sucky thing is that current recovery I am using, I can't even make a backup, restore a backup, or even install a rom from there.

enzyme said:
Sorry if I posted in the wrong place. Usually when I ask a flashing related question there someone tells me it should be asked in Development.
Anyways, I tried that but nothing changed. Sucky thing is that current recovery I am using, I can't even make a backup, restore a backup, or even install a rom from there.
Click to expand...
Click to collapse
First and foremost you need a working recovery with a mounted sd card. Are you able to push anything via fastboot? I found it easiest to use a fastboot script. It dumbs it down to a couple mouse clicks. There is a utility for the one S called all in one. (sorry don't have link) maybe try that to install fresh recovery. One thing for certain, factory reset and then format card has to be done from bootloader mode and then push new recovery.
Sent from my HTC One S using xda premium

These are the steps I took that led me here.....
1. flashed ville_recovery_signed.img via Fastboot from here
2. re-locked the bootloader with in fastboot
3. ran RUU_Ville_U_TMOUS_1.53.531.16_Radio_0.16.31501S.02_10.18.31501S.08L_release_262073_signed from here that was from this thread.

http://forum.xda-developers.com/showthread.php?p=25850720
That should help, iv had that problem before and solved it from the post I just linked
Sent from my HTC One S using XDA Premium HD app

Moved To Q&A​
Do not open question threads in the development section, thats what Q&A is for.​

Chris Boyer said:
First and foremost you need a working recovery with a mounted sd card. Are you able to push anything via fastboot? I found it easiest to use a fastboot script. It dumbs it down to a couple mouse clicks. There is a utility for the one S called all in one. (sorry don't have link) maybe try that to install fresh recovery. One thing for certain, factory reset and then format card has to be done from bootloader mode and then push new recovery.
Sent from my HTC One S using xda premium
Click to expand...
Click to collapse
Yeah i have full control of Fastboot, just not always getting the desired final results. Yes I have the AIO pack and have tried to flash those recoveries w/o results. I mean from the log it looks like that did the trick but nothing changes after reboot, I can't get rid of the current Recovery.

stealthnoodle said:
http://forum.xda-developers.com/showthread.php?p=25850720
That should help, iv had that problem before and solved it from the post I just linked
Sent from my HTC One S using XDA Premium HD app
Click to expand...
Click to collapse
Steath! Now we are getting somewhere!
As I was going through the steps, I got the CWM from the AIO. That was before I had a chance to flash the 2nd time (step3), before I could get to the rest of the steps I allowed the phone to boot normal instead of HBoot, then it reverted back to the other recovery. But as of right now I did flash via AIO, cleared storage, factory defaulted, flashed via AIO again and now I am on step 5.
I am still sitting in the AIO CWM right now. The guide says to flash the UTB rom, which I am unfamiliar with and it appears like a custom rom. So what should I flash and what method should I use? Even though CWM is back I have no means to flash a ROM from there b/c my sd is empty. Should I .....
- flash one of the RUUs via fastboot?
-rename the RUU and push it to the SD via ADB and flash via CWM (like in the guide)?
(not sure if that method works with customRom only or RUUs as well.

enzyme said:
Even though CWM is back I have no means to flash a ROM from there b/c my sd is empty.
Click to expand...
Click to collapse
If you can mount your sdcard partition in recovery, you can then adb push a rom to it and flash it.
On your PC:
adb push yournewrom.zip /sdcard/
Then on your phone, in recovery:
Format system, data, cache
Flash zip from sdcard -> choose zip -> /sdcard/yournewrom.zip
Before you boot into the new rom, flash the boot.img (extract it from the zip) in fastboot.
adb reboot-bootloader
fastboot flash boot boot.img
fastboot reboot

Steath's advice led me to the guide and got me on the right track. Even with detailed instructions, I went in circles for awhile, but in the end I got it. I'm so relieved, its been a stressful 12hrs.
So now I just have one last question. Is it safe to extract boot.img & recovery.img and flash it with fastboot? This might even be a common practice who knows, I'm still very new to much of it.

enzyme said:
Is it safe to extract boot.img & recovery.img and flash it with fastboot? This might even be a common practice...
Click to expand...
Click to collapse
It is safe and common practice (and in many cases required to prevent bootloops) to extract the boot image from the rom you flash, and flash this boot image through fastboot.
Custom roms do not come with their own recovery (only their own boot.img). The only reason to extract a recovery from a RUU or OTA and flash it, is when you need to go back complete stock.
Edit: But if you want to switch to a different custom recovery, then yes, flashing it through recovery is safe and the proper way. (You just don't 'extract' it from anything.)

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

D2303 Bricked. Fastboot works, FlashTool doesn't

I have bricked M2 D2303. I don't know how it was bricked for the first time(it's not mine), but yesterday I temporarily resurected it by flashtool. It booted and worked few minutes on any system(i dont remember what it was) After trying to put customrecovery it started to bootloop.
Now Flashtool doesn't see this device anymore, but fastboot is stil alive. I flashed CM12.1 boot.img - it showed sony logo, android logo and then bootanimation(blue waves). After few more tries of flashing different images it doesn't start to boot, screen remains black. I searched for boot, system and userdata IMG packets, but I've found only this one: http://forum.xda-developers.com/xperia-m2/general/aosp-5-0-2-d2303-progress-t3073842
After flashing nothing happens. Fastboot still works, but flashtool doesn't.
I don't have any idea how to resurect it now...
I've never had any sony android device... My only ones were nexuses and Oneplus One.

Try repairing using Sony PC Companion...This may solve your problem

Than you. I tried to follow this instruction: http://talk.sonymobile.com/t5/Xperi...uctions-using-Pc-Companion-Win-or/td-p/249946
But in my version of app isn't any "repair phone/tablet" button
{
"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"
}

Download the TWRP recovery and OmniROM or any other flashable ROM.
Flash the recovery through fastboot.
Reboot into the recovery, allow /system modification and install the ROM; reboot to system.
Then re-flash stock if needed.

Maybe stupid question. I've already tried to unbrick via recovery yesterday, but I can't boot it. I flashed TWRP by "fastboot flash recovery twrp.img" but i wasn't able to boot. ADB works only on android and there is no fastboot command to boot recovery. I tried some hotkeys like volume up/down, both, but they do nothing.
fastboot boot twrp.img also returns an error.

wefhy said:
Maybe stupid question. I've already tried to unbrick via recovery yesterday, but I can't boot it. I flashed TWRP by "fastboot flash recovery twrp.img" but i wasn't able to boot. ADB works only on android and there is no fastboot command to boot recovery. I tried some hotkeys like volume up/down, both, but they do nothing.
fastboot boot twrp.img also returns an error.
Click to expand...
Click to collapse
If the bootloader is locked you shouldn't be able to flash any .img file. It it isn't unlocked in order to flash a recovery the phone must have a kernel (Sony made them for KK) that supports the recovery in a separate partition. Stock Xperia phones don't. Flashing any random .img file I won't be surprise if the phone gets bricked, it isn't like in many other phones.
Anyway, to fix it you must be able to flash via flash mode. Flashtool when connecting a phone reports in the log which mode is enabled (if the phone gets recognized at all). So you can use it to see if anything is alive. If the flash mode is dead for any reason but fastboot still works you must a kernel for Xperia M2 flashable via fastboot, if any is available. That may reopen the flash mode and from there do a phone repair from PC Companion.
Oh, and as usual if you are in Windows be sure all USB drivers are correctly installed..

wefhy said:
Than you. I tried to follow this instruction: http://talk.sonymobile.com/t5/Xperi...uctions-using-Pc-Companion-Win-or/td-p/249946
But in my version of app isn't any "repair phone/tablet" button
Click to expand...
Click to collapse
To repair your phone by using PC Companion you have to go to Support Zone: 1
Then follow the steps (sorry for the language i can't change it) : 2
3
I hope it will help you

Hope your Xperia will fixed bro,
Keep your spirit

@Miche1asso
Fastboot mode works, I'm able to flash any boot image.
Windows drivers are installed correctly because flashtool repaired this phone few days ago.
Wchich kernel to flash? Recovey-friendly one? It's for 4.4.4, but last installed system was lollipop. I am able to flash system via recovery on bricked sony device? On my Oneplus One it's impossible.
Or rather any original kernel to revive flashtool?
Unfortunately most of download links are dead :/
@tromine It would be better if my PC companion worked the same... Support zone shows nothing.
Edit: I flashed this kernel: http://www.android.gs/install-cwm-recovery-on-sony-xperia-m2-lte/ It's a progress - its shows sony logo again I tried few times to boot into recovery bu every time it stucked on sony logo. I pressed power off button (next to sim/sd) and left it for few minutes on c harger and... It booted into recovery (without any volume hotkey)
It looks like stock recovery on my oneplus or zenfone:
I am able to flash system using it? Only stock one or any?
O rather i should flash any other recovery?
Push zip file via ADB or any other way to tho this?
Or one question for everything: What's the fastest way to flash CM12.1 from there?
Edit: Nearer than farther Now I have CWM v6 on it But it still can't flash any system image
It says installation aborted; error in storage(...).zip; can't partition non mmbcblk device: /devices/msm_sdcc.2/mmc_host

Edit3: I tried 4 roms(stock rooted, CM12, CM11 and one more) and the same error. I have no idea what to do next... cant partition... maybe flashing userdata? It was flashed recently... Anyone knows what can i do?
sorry for doubleposting, i can't delete it.

wefhy said:
Edit3: I tried 4 roms(stock rooted, CM12, CM11 and one more) and the same error. I have no idea what to do next... cant partition... maybe flashing userdata? It was flashed recently... Anyone knows what can i do?
sorry for doubleposting, i can't delete it.
Click to expand...
Click to collapse
Wich flashtool do you use?

wefhy said:
Edit3: I tried 4 roms(stock rooted, CM12, CM11 and one more) and the same error. I have no idea what to do next... cant partition... maybe flashing userdata? It was flashed recently... Anyone knows what can i do?
sorry for doubleposting, i can't delete it.
Click to expand...
Click to collapse
A couple of things: Did you update PC Companion to the last release? It must have the option to repair the phone somewhere. I can't help much on that because I use the OS X version, but the option is there on one of the top menu.
Anyway, since you managed to flash a working kernel (with CWM) the phone isn't bricked. From there (the CWM) I would flash a full custom ROM which includes a kernel with CWM, obviously wiping everything (cache and data). The kernel must belong to the ROM to avoid further troubles. At that point hopefully the flash mode is restored. But even if it isn't from there with the last PC Companion repair the phone.
PS: I realize I messed up a bit writing in English in my previous post. But it seems you've got what I meant anyway.

I use the newest flashtool and PC companion downloaded from sony page. I updated them.
I searched few times, but my pc companioj just hadn't got repair option.
CWM wasn't able to flash anything(alwatys the same error)
Anyway... I installed flashtool on Linux Mint. It detected device immediately. As linux version is hardly outdated, it couldn't flash anything on this device(device list stopped on Xperia T/S - no M/M2) but somehow it unlocked my xperia.
When I next time tried to use flashtool on windows it just detected it and flashed stock.
Now I'm on 5.1.1 and everything works fine Thanks!