Database Info

Rooting- error: cannot load "flashboot flash recovery r1-modaco-reco... .img"

Rooting- error: cannot load "flashboot flash recovery r1-modaco-reco... .img"
I'm rooting my HTC One S the first time. And I was stupid and thought that HTC One X Clockworkmod flash would work.
Now I know how flashing and clockworkmod installing works but before that I accidentally flashed the One X command: "fastboot flash recovery recovery-clockwork-touch-5.8.2.7-endeavoru.img" and now when I go to recovery it gives me a red text and nothing works.
I searched everywhere for a guide to remove it and did not found. So I thought I could flash it over with an One S flash, but then when I entered the command: "fastboot flash recovery r1-modaco-recovery-clockwork-touch-ville.img" It gave me this: "error: cannot load 'recovery r1-modaco-recovery-clockwork-touch-ville.img'. My phone is connected perfectly, when I type 'fastboot devices' it shows me my phone is there.
So I think this is not a big problem for developers. Can anyone tell me what to flash or do to get rid of the One X recovery? Otherwise I just have to live with a phone with unlocked Bootloader and no access to root

Do you have the IMG I the directory from which you are running fast boot?

edscholl said:
Do you have the IMG I the directory from which you are running fast boot?
Click to expand...
Click to collapse
Ofcourse

rixrasta said:
Ofcourse
Click to expand...
Click to collapse
mabey I should just do a factory reset :/

Why don't you dl goo manager from market, open it and open menu and tap on Install OpenScriptRecovery and let it install twrp--although, I guess if you aren't rooted yet that won't work
Did you try fastbooting the cwmr from here--
http://www.clockworkmod.com/rommanager
Did you check the md5 on the modaco recovery before flashing
At the red text did you try hitting vol+ or vol- not sure which one takes you to stock recovery. What does red text say--
Did you hard reboot with holding down vol- and power at same time then release pwr after screen goes off and continue to hold vol-
Not sure what is wrong, just giving some ideas--

rugmankc said:
Why don't you dl goo manager from market, open it and open menu and tap on Install OpenScriptRecovery and let it install twrp--although, I guess if you aren't rooted yet that won't work
Did you try fastbooting the cwmr from here--
Did you check the md5 on the modaco recovery before flashing
At the red text did you try hitting vol+ or vol- not sure which one takes you to stock recovery. What does red text say--
Did you hard reboot with holding down vol- and power at same time then release pwr after screen goes off and continue to hold vol-
Not sure what is wrong, just giving some ideas--
Click to expand...
Click to collapse
Tyvm for your reply,
the cwmr for HTC One S does not exist any more on the page you gave me. There's only a blank page if you click on it
yes I did hard reboot and the red text says: This build is for development purposes only do not distribute outside HTC without HTC's written permission. Failure to comply my lead to legal action.
I tried the superboot from this site: htt p://w ww.m odaco.co m/to pic/352493-how-to-root-your-htc-one-s-for-windows-mac-and-linux/
This just brought up the recovery message again...
Then I tried flashing these files:h ttp://ww w.m odaco.c om/topic/353006-interim-clockworkmod-touch-recovery-for-the-htc-one-s-stock-download/
no help.
Any other ideas I should try?
However the flashing went through this time and there were no error, but the recovery is still f**ked.

rixrasta said:
Tyvm for your reply,
the cwmr for HTC One S does not exist any more on the page you gave me. There's only a blank page if you click on it
yes I did hard reboot and the red text says: This build is for development purposes only do not distribute outside HTC without HTC's written permission. Failure to comply my lead to legal action.
I tried the superboot from this site: htt p://w ww.m odaco.co m/to pic/352493-how-to-root-your-htc-one-s-for-windows-mac-and-linux/
This just brought up the recovery message again...
Then I tried flashing these files:h ttp://ww w.m odaco.c om/topic/353006-interim-clockworkmod-touch-recovery-for-the-htc-one-s-stock-download/
no help.
Any other ideas I should try?
However the flashing went through this time and there were no error, but the recovery is still f**ked.
Click to expand...
Click to collapse
Try this twrp .img
http://teamw.in/project/twrp2/100
The red text will stay till you relock, I believe, or flash stock recovery--

twrp recovery is the way to go. Me too I couldn't install the clockwork one!

rugmankc said:
Try this twrp .img
h ttp://team w. in/projec t/twrp 2/100
The red text will stay till you relock, I believe, or flash stock recovery--
Click to expand...
Click to collapse
I flashed the "openrecovery-twrp-2.2.2.0-ville.img". Didnnt change anything :/

sorry to hear that, not sure what else to do, so you still have onex recovery?
even if you run an ruu, i think you still have to flash the stock recovery first. haven't read up on that much, as never needed to run one
Don't know if trying to flash the stock recovery will help. I have the original one at home, but not sure if that is what they still call stock recovery with new ota's having come out

If it cannot load it, you probably spelt the name wrong. rename the image file to recovery.img (make sure it isn't .img.img) and flash that. Make sure the file path is correct! (e.g fastboot flash recovery C:\Users\Me\Desktop\recovery.img)

usaff22 said:
If it cannot load it, you probably spelt the name wrong. rename the image file to recovery.img (make sure it isn't .img.img) and flash that. Make sure the file path is correct! (e.g fastboot flash recovery C:\Users\Me\Desktop\recovery.img)
Click to expand...
Click to collapse
no no, the flashing finished successfully. I entered "fastboot flash recovery openrecovery-twrp-2.2.2.0-ville.img" and then it flashed without problems, but in the phone it didn't change a thing. If I enter recovery then there's the android icon with a white background and under it is the red text.
But keep guessing, maybe I really am doing something stupid wrong
When I go to Fastboot USB mode with my phone then I open the command prompt and firstly type "cd c:\CWM" (the folder where my flashing files are). Then secondly I type "fastboot devices" (just to be shure). And thirdly depending on what I am flashing I type "fastboot flash recovery name.img". I have tried "fastboot flash recovery openrecovery-twrp-2.2.2.0-ville.img", "fastboot flash recovery r2-modaco-recovery-clockwork-touch-ville" and "fastboot flash recovery ville_recovery_signed". Every one of them finishes successfully but doesn't change anything in the phone. I already have recovery-clockwork-touch-5.8.2.4-ville.zip and CWM-SuperSU-v0.96.zip in my phones directory to install root when I get into the recovery. In the C:\CWM folder in my computer are these files:
adb.exe
AdbWinApi.dll
AdbWinUsbApi.dll
fastboot.exe
(these where exctracted from fastboot.zip)
openrecovery-twrp-2.2.2.0-ville.img
r2-modaco-recovery-clockwork-touch-ville.img
ville_recovery_signed.img

the text won't disappear with unlocked bootloader, so that's ok.
Try to boot into bootloader hit fastboot reboot bootloader and then choose recovery. It can take a while to boot into recovery.
Gesendet von meinem HTC One S mit Tapatalk 2

stunner2002 said:
the text won't disappear with unlocked bootloader, so that's ok.
Try to boot into bootloader hit fastboot reboot bootloader and then choose recovery. It can take a while to boot into recovery.
Gesendet von meinem HTC One S mit Tapatalk 2
Click to expand...
Click to collapse
fastboot ->reboot bootloader ->bootloader ->recovery. Absolutely no change, It took half a second to bring up the "HTC quietly brilliant" logo and about two seconds for the red text to appear under it. No buttons work after that and I just have to hold the power button down to shut it down.
And by bootloader is unlocked!

As stunner said above it can take a while to boot into recovery, how long have you waited?
Give it a few minutes... Also you could try flashing stock recovery, it is distributed in the all-in-one tool and also in paulobriens posts about superboot. Then run a RUU.
But my best to would be to try fastboot booting a custom recovery, "fastboot boot cwm.img".

If this is the thing where you go int recovery for a millisecond and then back to the 'red text' screen (you have to watch carefully to notice), you should try erasing your cache in fastboot mode.
fastboot erase cache
Click to expand...
Click to collapse
-Jobo

It's gotten a little confusing and some suggestions are being repeated. I wonder if the android icon you are describing is the stock recovery symbol. At that screen have you tried to press vol+ or maybe volume-. I forget which one takes you to stock recovery. May want to check on that.
Also, have you tried typing "fastboot boot recovery" to go straight to recovery, bypassing htc restrictions
Here is very early stock recovery--not sure if it is still considered "stock" with new versions out now--I did mention that earlier--
https://www.dropbox.com/sh/yhrq0tia8512rj9/go28kc1NeP/ville_recovery_signed.img
I did have issues fastbooting recovery before. You can as mentioned try fastboot erase cache before fastbooting recovery. And change the name of your recovery to just recovery.img before you fastboot.
I assume you have nandroid backup on phone and copies of it and sdcard backup on pc.
I think when I had issues with recovery sticking it was my N1 and I typed "fastboot erase system" first, then fastbooted recovery. Then wiped all and restored nandroid. I am not sure we can do that on the 1s with no s-off. Someone else may know.
Can you access sdcard where you could reformat it fat32 thru a windows formatter program. Of course copy all to pc first. Sometimes sdcard formats help things you wouldn't expect it to.
Some folks have reported formatting works better thru phone on the 1s, maybe because it is an internal card. I did it once and think I had to redo it thru phone. But, if it gets recovery working, no big deal.
All these are suggestions and as the devs say--at your own risk--
I thought you said you said in first post, phone works, just no root capabilty. If that is true it should be fixable--I hope.
---------- Post added at 05:06 PM ---------- Previous post was at 04:32 PM ----------
rixrasta said:
no no, the flashing finished successfully. I entered "fastboot flash recovery openrecovery-twrp-2.2.2.0-ville.img" and then it flashed without problems, but in the phone it didn't change a thing. If I enter recovery then there's the android icon with a white background and under it is the red text.
But keep guessing, maybe I really am doing something stupid wrong
When I go to Fastboot USB mode with my phone then I open the command prompt and firstly type "cd c:\CWM" (the folder where my flashing files are). Then secondly I type "fastboot devices" (just to be shure). And thirdly depending on what I am flashing I type "fastboot flash recovery name.img". I have tried "fastboot flash recovery openrecovery-twrp-2.2.2.0-ville.img", "fastboot flash recovery r2-modaco-recovery-clockwork-touch-ville" and "fastboot flash recovery ville_recovery_signed". Every one of them finishes successfully but doesn't change anything in the phone. I already have recovery-clockwork-touch-5.8.2.4-ville.zip and CWM-SuperSU-v0.96.zip in my phones directory to install root when I get into the recovery. In the C:\CWM folder in my computer are these files:
adb.exe
AdbWinApi.dll
AdbWinUsbApi.dll
fastboot.exe
(these where exctracted from fastboot.zip)
openrecovery-twrp-2.2.2.0-ville.img
r2-modaco-recovery-clockwork-touch-ville.img
ville_recovery_signed.img
Click to expand...
Click to collapse
you should also have adb.exe if you are using adb--

frdd said:
As stunner said above it can take a while to boot into recovery, how long have you waited?
Give it a few minutes... Also you could try flashing stock recovery, it is distributed in the all-in-one tool and also in paulobriens posts about superboot. Then run a RUU.
But my best to would be to try fastboot booting a custom recovery, "fastboot boot cwm.img".
Click to expand...
Click to collapse
Okay I waited for 10 minutes, nothing happens. I've even tried to hold down all the button combinations(with the three buttons) for a few minutes.
I've tried flashing everything and fastboot boot just takes me directly to the recovery with the red text. I flashed both the recoveries in the all-in-one tool.
As I know absolutely nothing about RUU(only what the letters stand for) then I'd rather not do that because I read from some threads that RUU has quite a high chance to mess up your phone. Or if you direct me to a tutorial that u insure me that is 100% good then I could give it a go : D

[
I think I have made ​​the same mistake of flash recovery, but I can not get into cwm recovery, I only appear for 1 second the recovery, then restarts and returns to the operating system. SD card, all changes are discarded when you restart the phone, which is also only if I try to install or remove some utility. Can not install any recovery, even if fastboot works well and looks real mind install the recovery but when I reboot, it returns to its previous behavior, with recovery not working. I tried to install the recovery in every way, from fastboot, from All in one with quickroot, but none of these operations has changed the state of the system.
Unfortunately you can not install a Stock RUU because the bootloader unlocked and the recovery is not the stock, and especially not when there is no tutorial to follow to bring this situation to the ONE S, to its original state
Hopefully someone will be able to find a solution to your and my problem.

One option you guys may need to entertain, if applicable, would be to exchange phones with Carrier. Worth a shot--
I have not heard of this exact issue, but most comments say if you can't boot to recovery you are bricked--
Has anyone tried "fastboot boot recovery" command in terminal window?

[Q] Really Hard Brick.. I think..

HELP TO ALL THE COMMUNITY ASAP!!!
here is the deal, i had the HTC One S Rooted fine, it was working but i tried now to install a custom rom, baked black beans, but now i've downloaded the rom, set it in my HTC, accessed CMW, wiped data, installed from sd, rebooted, went to bootloader, run boot.img on cmd on computer, restarted and now i am getting the HTC Bootloader that states that "This build is for development purporses etc. etc.." now here is the deal guys... i was able to get to bootloader then to recovery, i check the sd files in clockwork recovery and nothing!! all i want now is just stock and try again.. guys.. help???
URGENT!!

therion0 said:
HELP TO ALL THE COMMUNITY ASAP!!!
here is the deal, i had the HTC One S Rooted fine, it was working but i tried now to install a custom rom, baked black beans, but now i've downloaded the rom, set it in my HTC, accessed CMW, wiped data, installed from sd, rebooted, went to bootloader, run boot.img on cmd on computer, restarted and now i am getting the HTC Bootloader that states that "This build is for development purporses etc. etc.." now here is the deal guys... i was able to get to bootloader then to recovery, i check the sd files in clockwork recovery and nothing!! all i want now is just stock and try again.. guys.. help???
URGENT!!
Click to expand...
Click to collapse
CWM cant mount SD you need TWRP for that and a RUU put you back to stock but the bootloader needs relocking. So did you even try booting the rom because the red writing is fine.

you didn't mention it, but you should wipe system and caches as well as data

Not hard brick. you can chose the correct Ruu file and flash it to your phone.... solved your case.

Darknites said:
CWM cant mount SD you need TWRP for that
Click to expand...
Click to collapse
CWM can not mount our sdcard onto your computer over USB.
But it absolutely can mount the sdcard partition onto the root filesystem.
Unless you have the 'unmountable sdcard' problem, for which there is a sticky in Q&A.
My feeling is that the OP didnt mount the sdcard partition. In that case it is normal to see the mount point as an empty folder.
Once it's mounted, you can adb push rom zips to it.

touch of jobo said:
CWM can not mount our sdcard onto your computer over USB.
But it absolutely can mount the sdcard partition onto the root filesystem.
Unless you have the 'unmountable sdcard' problem, for which there is a sticky in Q&A.
My feeling is that the OP didnt mount the sdcard partition. In that case it is normal to see the mount point as an empty folder.
Once it's mounted, you can adb push rom zips to it.
Click to expand...
Click to collapse
Oh right seems a lot work lol, I think I stick to TWRP.

Darknites said:
Oh right seems a lot work lol, I think I stick to TWRP.
Click to expand...
Click to collapse
+1, 2 & 3!
Really don't understand why anyone still uses CWM, I think its just habit with some people.

shadowch31 said:
+1, 2 & 3!
Really don't understand why anyone still uses CWM, I think its just habit with some people.
Click to expand...
Click to collapse
Habit and guides.

I thought I saw a post that mentioned cwm has not kept up to date--not sure
But, I was a slow convert too and very happy with twrp 2.2.2.0

rugmankc said:
I thought I saw a post that mentioned cwm has not kept up to date--not sure
But, I was a slow convert too and very happy with twrp 2.2.2.0
Click to expand...
Click to collapse
I not seen updates but then I not looked and I didn't move over in till it got the usb mount.

when i run the CMD Command prompt adb reboot bootloader I get error: device not found, i was able to flash the boot.img and i got the 2 OKs but i get that error now... what now?

Also, when i go to recovery mode, i don't see any files to install the .zip file of the rom i want to install

therion0 said:
Also, when i go to recovery mode, i don't see any files to install the .zip file of the rom i want to install
Click to expand...
Click to collapse
You lost SD then and best off running a RUU to recover it.

ok i'm lost.. how do i run an RUU to recover it?

therion0 said:
ok i'm lost.. how do i run an RUU to recover it?
Click to expand...
Click to collapse
Download the right RUU for your carrier and location by looking at http://forum.xda-developers.com/showthread.php?t=1543588 and you can get free download at http://www.4shared.com/folder/jKN2qjTl/HTC_Ville_RUU_Collection.html
Then plug in your phone and follow the instructions when you run the RUU .exe file.
AKToronto

but everytime i try to run it, it says it fails because the phone it is not connected to the computer but it is...

did you ever try to boot into the rom after you flashed it and boot image as in just tapping on reboot system
can you plug phone into pc and get indicator at top of screen that says you are connected. then pull down notification bar and select to mount drive
if so, does it show you your sdcard in the windows screen
you do have an S4 device and assume you are hboot .13 or higher
if you can get into os and see sdcard, you can get twrp and flash image gui and flash rom and boot image with it
i am sure you tried these things, just hard to know when reading posts
also, i don't know if you are running your commands correctly based on how i undestand your posts. you can't run adb commands from fastboot, which is what you were in to fastboot boot image. you would want to type fastboot reboot-bootloader
if you are very familiar with adb/fastboot--sorry. if not need to get up to speed on them
if i misread or misunderstood any of this, sorry for butting in--

rugmankc said:
did you ever try to boot into the rom after you flashed it and boot image as in just tapping on reboot system
can you plug phone into pc and get indicator at top of screen that says you are connected. then pull down notification bar and select to mount drive
if so, does it show you your sdcard in the windows screen
you do have an S4 device and assume you are hboot .13 or higher
if you can get into os and see sdcard, you can get twrp and flash image gui and flash rom and boot image with it
i am sure you tried these things, just hard to know when reading posts
also, i don't know if you are running your commands correctly based on how i undestand your posts. you can't run adb commands from fastboot, which is what you were in to fastboot boot image. you would want to type fastboot reboot-bootloader
if you are very familiar with adb/fastboot--sorry. if not need to get up to speed on them
if i misread or misunderstood any of this, sorry for butting in--
Click to expand...
Click to collapse
Ya he messed it up so needs RUU. He has PM me just waiting on a reply.

[Q] Help! My One X is Stuck in Boot Loop

Hey Guys,
This is my first post, so excuse me if I sound like I don't know what I'm talking about.
I was experiencing issues with my ATT HTC One X with CDM 10.1 on it, so I booted into boot loader and tried to boot up a new ROM, but somehow my initial ROM got deleted, I forgot to back up, and now I have no ROM installed and my phone is stuck in a boot loop. I have been messing with this thing and researching for hours trying all kinds of different things to get it working and nothing has seemed to work.
Can someone please help me?

Did you do a factory reset from the bootloader? If so, you've corrupted the internal memory, and will need to format it before you can move another ROM onto it.
Sent from my Evita

timmaaa said:
Did you do a factory reset from the bootloader? If so, you've corrupted the internal memory, and will need to format it before you can move another ROM onto it.
Sent from my Evita
Click to expand...
Click to collapse
Now that I recall, yes I believe that's exactly what I did.
Where I'm at now, I can't get into recovery. The only thing I can do is get into fastboot. Where do I go from here?

Ok. I'm assuming you have a working adb/fastboot environment on your PC. If you can't get into recovery you may as well try flashing it. Get it from here (I recommend version 2.3.3.1):
http://goo.im/devs/OpenRecovery/evita
Once you've downloaded the file, put it into your working adb/fastboot directory (rename it to something simple like twrp.img). Make sure you're booted into bootloader, connect phone to pc, ensure it says "fastboot usb" on your phone screen, open a command prompt within your adb/fastboot directory then issue the following command:
fastboot flash recovery twrp.img
This will flash the recovery, it only takes a few seconds. When it's finished, issue this command:
fastboot erase cache
Once that's done, select recovery on your phone and it should boot into TWRP recovery. Select mount from TWRP menu, mount usb storage, the storage should now show up on your pc, format it to fat32.
Now you can copy ROM from PC to phone, unmount storage, and you should be able to flash a ROM (make sure you do a full wipe first though).
Sent from my Evita

timmaaa said:
Ok. I'm assuming you have a working adb/fastboot environment on your PC. If you can't get into recovery you may as well try flashing it. Get it from here (I recommend version 2.3.3.1):
Once you've downloaded the file, put it into your working adb/fastboot directory (rename it to something simple like twrp.img). Make sure you're booted into bootloader, connect phone to pc, ensure it says "fastboot usb" on your phone screen, open a command prompt within your adb/fastboot directory then issue the following command:
fastboot flash recovery twrp.img
This will flash the recovery, it only takes a few seconds. When it's finished, issue this command:
fastboot erase cache
Once that's done, select recovery on your phone and it should boot into TWRP recovery. Select mount from TWRP menu, mount usb storage, the storage should now show up on your pc, format it to fat32.
Now you can copy ROM from PC to phone, unmount storage, and you should be able to flash a ROM (make sure you do a full wipe first though).
Sent from my Evita
Click to expand...
Click to collapse
I appreciate the info. I think I understand what to do now. My only problem now is that I think my phone died. The red light blinks for a couple minutes, then it turns on and goes to the HTC quietly brilliant screen. If I hold down the power and vol down buttons it will turn off and then if I hold them down again it will go into the bootloader, but then it will shut off after a few seconds. Is it because it's dead and how do I get it charge?

Stop trying to turn it on. If you do that too many times while it has very low charge you can kill the battery to the point where it's not usable at all anymore.
Leave it turned off, plug it into a wall charger overnight and then try again.
Sent from my Evita

timmaaa said:
Stop trying to turn it on. If you do that too many times while it has very low charge you can kill the battery to the point where it's not usable at all anymore.
Leave it turned off, plug it into a wall charger overnight and then try again.
Sent from my Evita
Click to expand...
Click to collapse
I got it back into recovery after running the commands you told me. I then moved my ViperXL 3.2.7 ROM file over to the phone. The install started and then froze one the ViperXL screen and never went any farther. I am back in recovery again, but I don't know what to do again because that ROM failed.

So now I got the ViperXL installer to go all the way through the install and it said it was successful, but now it is doing the boot loop again. It reboots, goes to the HTC screen, turns off, and just keeps repeating itself.

lcderrick said:
So now I got the ViperXL installer to go all the way through the install and it said it was successful, but now it is doing the boot loop again. It reboots, goes to the HTC screen, turns off, and just keeps repeating itself.
Click to expand...
Click to collapse
What hboot? S-on or off??
Sent from my HTC One XL using xda premium

You probably need to flash the boot.img manually.
Sent from my Evita

[Q] - Nexus S 4G Unable to boot past Google logo and CWM can't mount /sdcard

I have a Sprint Nexus S 4G that I keep in Airplane mode most of the time and rarely use (an hour a week at most, usually). I use it so rarely that it shuts off due to low battery a lot.
The last time it shut off, I wasn't able to boot it up when I turned it back on. It got stuck at the Google logo indefinitely with the bottom buttons lit up. I can boot to CWM Recovery (v6.0.1.9) but when I do, I get the log message "Error mounting /sdcard!" or "E:Can't mount /sdcard/" when I try to search for an update.zip on the phone, or try to mount or format /sdcard. I tried using the "adb sideload" command to install a ROM from CWM, which fails with:
E:Error in /tmp/update.zip
(Status 0)
Installation aborted.
Click to expand...
Click to collapse
I also tried using "adb push cm-10.1.2-crespo4g.zip /sdcard/", which does not fail with any errors but still am unable to mount /sdcard/ through CWM so that obviously isn't any help for me.
I can boot into fastboot and tried flashing back to stock with these commands using the image files from this thread.
Code:
fastboot flash boot boot.img
fastboot flash system system.img
fastboot flash recovery recovery.img
fastboot flash userdata userdata.img
fastboot flash radio radio.img
fastboot erase cache
fastboot reboot
When I flashed using the commands above, I got no errors in the terminal but my phone still would not boot past the Google logo. Afterwards I was able to flash CWM Recovery back onto the phone with no problems but CWM still can't see the /sdcard partition.
I also tried all of the suggestions on this thread with no success.
Nexus S stuck on google boot logo
For an even crazier attempt at a solution, I found a person with a similar problem to mine where they ran a hair dryer over the phone for a few minutes to fix it. That didn't help, either.
I think my nexus died
At this point I'm out of ideas and was hoping someone else might know something I could try. I planned on getting a new phone soon anyway but was hoping to be able to use my old phone for a little while until that happens.

You've tried all sorts of things to recover the SD card portion. Which I think is badly corrupted.
I think your internal memory card has died. I suggest going for a new phone.
One last effort will be to install a different recovery and try formatting the SD card from there. Try Philz Touch or TWRP.
Sent from my Nexus S using Tapatalk 4

danherbert said:
I have a Sprint Nexus S 4G that I keep in Airplane mode most of the time and rarely use (an hour a week at most, usually). I use it so rarely that it shuts off due to low battery a lot.
The last time it shut off, I wasn't able to boot it up when I turned it back on. It got stuck at the Google logo indefinitely with the bottom buttons lit up. I can boot to CWM Recovery (v6.0.1.9) but when I do, I get the log message "Error mounting /sdcard!" or "E:Can't mount /sdcard/" when I try to search for an update.zip on the phone, or try to mount or format /sdcard. I tried using the "adb sideload" command to install a ROM from CWM, which fails with:
I also tried using "adb push cm-10.1.2-crespo4g.zip /sdcard/", which does not fail with any errors but still am unable to mount /sdcard/ through CWM so that obviously isn't any help for me.
I can boot into fastboot and tried flashing back to stock with these commands using the image files from this thread.
Code:
fastboot flash boot boot.img
fastboot flash system system.img
fastboot flash recovery recovery.img
fastboot flash userdata userdata.img
fastboot flash radio radio.img
fastboot erase cache
fastboot reboot
When I flashed using the commands above, I got no errors in the terminal but my phone still would not boot past the Google logo. Afterwards I was able to flash CWM Recovery back onto the phone with no problems but CWM still can't see the /sdcard partition.
I also tried all of the suggestions on this thread with no success.
Nexus S stuck on google boot logo
For an even crazier attempt at a solution, I found a person with a similar problem to mine where they ran a hair dryer over the phone for a few minutes to fix it. That didn't help, either.
I think my nexus died
At this point I'm out of ideas and was hoping someone else might know something I could try. I planned on getting a new phone soon anyway but was hoping to be able to use my old phone for a little while until that happens.
Click to expand...
Click to collapse
I am also having the same situation. OP, were you able to resolve this issue?

[Q] Flashed boot.img, did a reboot, but phone keeps restarting after splashscreen

I'm trying to load the CM ROM to my HTC One S device. I was able to unlock and root the device. Next, I flashed the boot.img (fastboot flash boot.img) from the ROM zip file to the device and restarted it (cm-10.1-20130304-EXPERIMENTAL-ville-M2). Now my device just cycles through the HTC splash screen with the red letters "this build is for development purposes only..." -> Android Splash Screen. Phone does not properly boot up. I think I missed a step in the flashing process. Any ideas on how to proceed?

fastboot flash boot boot.img
just in case you typed it the way you wrote in your post.
what recovery are you using? what version?
maybe try twrp 2.3.3
get into bootloader and flash again, go to recovery do a full wipe and install the cm zip again.

tivofool said:
fastboot flash boot boot.img
just in case you typed it the way you wrote in your post.
what recovery are you using? what version?
maybe try twrp 2.3.3
get into bootloader and flash again, go to recovery do a full wipe and install the cm zip again.
Click to expand...
Click to collapse
Sorry, the command I used was "fastboot flash boot boot.img" The CM boot.img definitely got written to the device. I missed the step of copying the ROM to a folder on my device. I wasn't clear on this step since I'm not sure how to view folders on the device. Is there a way to load the ROM from my PC instead of copying the files to the device first?
I'm using TWRP 2.6.0.0. I'm also not clear on the back up portion since there is no SD card on this device. Is it possible to perform a backup? I thought I did one during the initial step, but now that I'm trying to restore, I don't see a backup available.

yes, the "sd card" is there as a partition or whatever. But it works the same way. Backups do work.
So in twrp mount the sd card (usb storage, whatever twrp calls it), then you can transfer the rom to your phone from your computer. Then just wipe your caches and install zip.
You can get into recovery from your bootloader, hold volume down and press power (don't hold)

tivofool said:
yes, the "sd card" is there as a partition or whatever. But it works the same way. Backups do work.
So in twrp mount the sd card (usb storage, whatever twrp calls it), then you can transfer the rom to your phone from your computer. Then just wipe your caches and install zip.
You can get into recovery from your bootloader, hold volume down and press power (don't hold)
Click to expand...
Click to collapse
Thanks for clarifying. I successfully loaded the ROM on my device.

My workflow stopped at the same spot, screen is locked in the HTC logo and the warning about the build being development purpose only, but trying again to get into bootloader and the phone doesn't load it up, it just turns off and nothing else happens

Mhord said:
My workflow stopped at the same spot, screen is locked in the HTC logo and the warning about the build being development purpose only, but trying again to get into bootloader and the phone doesn't load it up, it just turns off and nothing else happens
Click to expand...
Click to collapse
Was your battery too low?
Hopefully you can get into bootloader, that's pretty important to fix anything.
someone could correct me, but can't you hold power down until the buttons flash, then hold both power and volume down button until bootloader starts.

tivofool said:
Was your battery too low?
Hopefully you can get into bootloader, that's pretty important to fix anything.
someone could correct me, but can't you hold power down until the buttons flash, then hold both power and volume down button until bootloader starts.
Click to expand...
Click to collapse
It had like 75% charge. Buttons don't flash like normal... Got to load the bootloader flashed the recovery, reboot, same screen

Mhord said:
It had like 75% charge. Buttons don't flash like normal... Got to load the bootloader flashed the recovery, reboot, same screen
Click to expand...
Click to collapse
So you are trying to get into recovery. When you go into the bootloader, you choose recovery and it doesn't work.
you could go back to bootloader, fastboot usb.
from there open a command terminal on your computer. From your fastboot folder press shift and right mouse click <open command terminal here>
type
fastboot erase cache
then you can press power button to select hboot, then volume down to recovery.
You could try to flash a different recovery if that doesnt work. Make sure you are using the correct recovery for your device. S4 version or the S3 international type devices.

tivofool said:
So you are trying to get into recovery. When you go into the bootloader, you choose recovery and it doesn't work.
you could go back to bootloader, fastboot usb.
from there open a command terminal on your computer. From your fastboot folder press shift and right mouse click <open command terminal here>
type
fastboot erase cache
then you can press power button to select hboot, then volume down to recovery.
You could try to flash a different recovery if that doesnt work. Make sure you are using the correct recovery for your device. S4 version or the S3 international type devices.
Click to expand...
Click to collapse
mmm yeah tried what you said, and still got stuck in "entering recovery".
I used eyeballer recovery which is the one CM recommends on their wiki
EDIT: My HBOOT says VilleC2 in that case S3 recovery would be the correct one?
EDIT: Yep found the correct recovery back in business, many thanks Tivofool