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

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

Moto G XT1033 Soft Bricked, Cannot Boot To TWRP or CWM

no custom recovery loading
I am currently using moto G first generation xt1033 indian dual sim version.
I have soft bricked my phone.
WHAT I HAVE: I have access to fastboot
My bootloader is unlocked
Access to stock recovery
PROBLEM: I have tried to flash twrp , cwm and philz recovery but every time i boot into recovery mode stock recovery loads.
I cannot access USB Debugging mode since the phone is soft bricked.
I have also tried to flash stock firmware no change seen.
I would be glad if you all can help me.
@ravibhat i have read your thread and my starting problem was same as yours @lost101 please help me as well.Thank You

Ok.Post pics,videos so that we know it's the same problem.
Go to a service centre when you can and share what they've told.

did u use these steps ?
fastboot erase recovery
fastboot flash recovery ur_recover_zip_name.zip
try different versions of recovery, i suggest u use CWM V6.0.4.7
If that works, use the adb sideload feature to flash the ROM

thank you for the reply
@ankur.walia
i tried the erase recovery command this was the output
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
and when i tried to lock bootloader this was the ouput

mrawal031 said:
@ankur.walia
i did not try the erase recovery command but i tried to flash it directly.
ill try this and revert i hope it wouldn't pose a problem if i directly flash the .img file
Click to expand...
Click to collapse
yes, and try the version i mentioned because i was also facing the problem like u and only this specific versions worked for me

still no change
@ankur.walia @ravibhat
i tried the command you told me to. There is no change im unable to boot in flash recovery also now xD.
i also went to the service centre they said there is nothing they can do for this phone as the only thing they know is to flash the stock firmware.

mrawal031 said:
@ankur.walia @ravibhat
i tried the command you told me to. There is no change im unable to boot in flash recovery also now xD.
i also went to the service centre they said there is nothing they can do for this phone as the only thing they know is to flash the stock firmware.
Click to expand...
Click to collapse
are u not able to go in fastboot mode now?
if u are, then ls try different versions of the recoveries...
and yes...what actually is happening? are u able to see the boot logo? its stuck in bootlogo screen?..or is it struck in recovery's logo screen?
are it is not even booting itself?

ankur.walia said:
are u not able to go in fastboot mode now?
if u are, then ls try different versions of the recoveries...
and yes...what actually is happening? are u able to see the boot logo? its stuck in bootlogo screen?..or is it struck in recovery's logo screen?
are it is not even booting itself?
Click to expand...
Click to collapse
I can go to the bootloader after entering stock recovery no combination of keys can display the option.
my phone starts normally shows logo and all booting animation but after that it gets stuck on a blank screen showing nothing and no touch response. I have tried aprox 4-5 variants of custom recoveries but i can flash none of them even after trying your command and getting success written on screen.

mrawal031 said:
I can go to the bootloader after entering stock recovery no combination of keys can display the option.
my phone starts normally shows logo and all booting animation but after that it gets stuck on a blank screen showing nothing and no touch response. I have tried aprox 4-5 variants of custom recoveries but i can flash none of them even after trying your command and getting success written on screen.
Click to expand...
Click to collapse
well if u got the successful execution of recovery flashing then it should go to recovery mode, try holding powe and volume down together for quite some time (5-6 seconds by the clock) and then release it

ankur.walia said:
well if u got the successful execution of recovery flashing then it should go to recovery mode, try holding powe and volume down together for quite some time (5-6 seconds by the clock) and then release it
Click to expand...
Click to collapse
https://drive.google.com/file/d/0B6y6POATHFhrLVhpUThNVUc1VXc/view?usp=sharing
you can see the condition even after flashing the custom recovery i get booted into stock recovery

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!

[solved + how i solved it] the current image(boot/recovery) have been destroyed

so, i was trying to install twrp, but i made a stupid mistake, instead of fastboot flash recovery i did fastboot flash boot, now it tells me: "the current image(boot/recovery) have been destroyed", when i go into bootloader, and attack the cable (both before and after) restarts itself.
things I tried: flash the original boot (it gave "FAILED (Write to device failed (no link))", obviously before the bootloader happened) change usb cable, flash the stock rom (obviously before the bootloader happened)), redownload adb /fastboot drivers, phone drivers, and google drivers. this is all i remember trying to do, i'm desperate, could someone help me please?

update: now i can use bootloader

update: I fixed it, in case this situation happened to you, I solved it like this: I had a windows update, while it was doing it, I connected the phone to the pc, in the end it no longer rebooted by itself (the phone) , then do fastboot flash boot (original boot), if it doesn't work, reboot the bootloader , from the bootloader, if it doesn't work, do the same thing downloading the drivers again, then do fastboot flash boot (original boot.img), if you want to download costum recovery, do fastboot flash recovery (costum recovery.img). I fixed it like this, now I have a costum recovery, costum rom and root!

Hello friend, I have a question. I closed the bootloader and when I closed it, the recovery image was destroyed.
Now I can't enter my cell phone and it stays in an infinite boot
any solution with locked bootloader

Angel1104 said:
Hello friend, I have a question. I closed the bootloader and when I closed it, the recovery image was destroyed.
Now I can't enter my cell phone and it stays in an infinite boot
any solution with locked bootloader
Click to expand...
Click to collapse
try going into the bootloader and re-unlocking 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"
}
That happened to me when I wanted to block the boot, so I think the boot was blocked and only stayed in the realme recovery like the following photo

Angel1104 said:
View attachment 5798249That happened to me when I wanted to block the boot, so I think the boot was blocked and only stayed in the realme recovery like the following photo
Click to expand...
Click to collapse
I don't understand if the recovery works or not, it's a bootloop with locked bootloader and you can go into recovery or locked bootloader without accessing recovery? you are confusing me, however, if you have access to recovery download the stock rom from the recovery, if not, try to unlock the bootloader again by doing fastboot flashing unlock, then flash the stock recovery and then download the stock rom from the recovery

And how do you enter that mode without the application?

enter bootloader and do fastboot reboot recovery, in bootloader you can't perform flashing actions and many other things (bootloader locked) but some things, like reboot should work

in case you get the same error for the recovery you have to unlock the bootloader again

Can I send you a private message?

yes

Did you solve it? I'm facing the same issue.

Gamer_Mida said:
update: I fixed it, in case this situation happened to you, I solved it like this: I had a windows update, while it was doing it, I connected the phone to the pc, in the end it no longer rebooted by itself (the phone) , then do fastboot flash boot (original boot), if it doesn't work, reboot the bootloader , from the bootloader, if it doesn't work, do the same thing downloading the drivers again, then do fastboot flash boot (original boot.img), if you want to download costum recovery, do fastboot flash recovery (costum recovery.img). I fixed it like this, now I have a costum recovery, costum rom and root!
Click to expand...
Click to collapse
I am having trouble understanding what you did exactly. I am getting this same error with a Xiaomi Mi 8 Lite.
Edit: got it working by disconnecting all usb ports and trying another port.

Angel1104 said:
Hello friend, I have a question. I closed the bootloader and when I closed it, the recovery image was destroyed.
Now I can't enter my cell phone and it stays in an infinite boot
any solution with locked bootloader
Click to expand...
Click to collapse
same as me i dont know what to do