Related
Hello,
I have a htc desire s (s-on, 2.10.401.8_Radio_20.4801.30. 0822U_3822.10.08.04 installed).
When I start the phone with fastboot enabled, the widgets occasionally close and load again.
So everything start normal, but sometimes the widgets close in less than a second after startup and load again.
This only happens since 2.10.401.8 is installed.
I think that it's htc sense that crashes, but I'm not certain.
Already tried a factory reset, but same result.
Does Anyone have an idea what wrong and/or a solution?
After further testing I guess fast boot isn't working correctly anymore even after factory reset.
Is this a hardware problem or is there a way to test if it is a hardware problem?
Now it start to take a lot of time to startup and shutdown.
I also can't get in recovery: "E:Can't mount /cache/recovery/command"
From what I've seen on here, this sounds like what used to be called "the dreaded eMCC chip" problem, but is actually the "cache" partition being corrupted.
From what I've read, you may just about get away with it. Have a look at the following threads;-
http://forum.xda-developers.com/showthread.php?t=1177299
http://forum.xda-developers.com/showthread.php?t=1314629
Thanks, I feared that it was the emmc problem.
I have never pulled out the battery.
I will look into the threads, but I don't know if there is much I can do being s-on.
Update:
I had to send the device to HTC and they replaced the mainboard.
Everything is working good again.
Hi.
Once I tried to install RUU on S-offed rooted phone. Instalation stopped and didn't continue. I had the same problem with partitions
I also can't get in recovery: "E:Can't mount /cache/recovery/command"
Click to expand...
Click to collapse
What helped is to format cache partition in recovery. After that I could bring back my previous rom. In the end I didn't try to install RUU anymore.
I hope it will help.
---
Sorry, I didn't see your last post
i brought the phone at launch, its a T-Mobile version Super AMOLED I9020, im in india though, using indian sim.
the phone was previously rooted, then unrooted, then rooted, then unrooted again. then filnally i was using unrooted nexus s, but with unlocked bootloader and stock recovery.
4-5 months after this, the phone started stucking on google logo.
it used to stuck at google logo at times but a quick battery pull would fix it, one day it didnt. since then it always stuck at the google logo on boot and never turned on, except some 1 out of 1 million times after connecting to computer.
i tired to format the whole phone using stock recovery, it was successful and the phone turned on, but next time when it switched off, same problem again but this time even formatting wont work, the formatting from stock recovery would just display an error that it failed to find a file and formatting aborted.
i tried everything, hundreds of stuff from google and XDA but nothing seems to be working.
today i managed to flash CWR to it. i tired to then erase sdcard but it says failed to mount /sdcard . i also tried other things like update from sd card(i have a ICS update.zip file in the memory) but still it said failed to mount sdcard, tried to wipe-> 'error mounting sdcard'
and now i dont know what ive done but when i boot the phone(normally) it doesnt even display the google logo, it enters bootloader by itself and says 'fastboot mode - no boot or recovery img'
bootloader is still unlocked, CWR is still there and accessible.
i took it to samsung service centre too, they said they will have to replace the motherboard(quoting me 400$ for it lol)
this is my last try really, ive been trying to fix this thing from ages!
is there anything that can be done?
going to sell it if i still cant fix it
I'm in about the same spot. If you have a Linux box available, you might try Adam Outler's "Unbrickable Resurrector." (http://forum.xda-developers.com/showthread.php?t=1397393) It's supposed to be a last gasp kind of thing before you give up. However... I ran it and it crashes -- not the phone, the software itself. Sigh.
I got here by making a backup, then unintentionally erasing everything on the phone, including the backup, the boot image, and the recovery image (the backup, presumably). That's what the message "no boot or recovery img" seems to be saying. Fastboot doesn't work either.
So here's my last gasp before I take it in for repair: apparently you can buy or build a micro-USB connector called a "USB jig" -- it's just a connector with a resistor connecting a pin that's usually not connected. This is supposed to put the phone into download mode, where you can copy a recovery image to the phone. Then you can use CWM to install a new image.
-Rod
It sounds like your mem is shot.
Sent from my Nexus S
I've had a similar problem to this and to solve it I just locked the boot loader and then unlocked it again and everything was back to normal for me. You could try that and see if it works
Sent from my Nexus S using Tapatalk
sell faulty nexus phone
HI
I am intrested in buying a faulty nexus s phone . If in case this is of no use to you then I am ready to buy this.
contact me at 7838448028
Regards
Amit
amity_coolin said:
HI
I am intrested in buying a faulty nexus s phone . If in case this is of no use to you then I am ready to buy this.
contact me at 7838448028
Regards
Amit
Click to expand...
Click to collapse
R u still interested in a faulty Nexus S?
Hi.
My solution may sound a bit strange but me too have the same problem.
Just heat the phone a bit and see if it boots.
Heat it from a hot air source such as laptop heatsink area.
Just get the cell phone warm and it may boit up.
I know it may sound strange but it has worked for me everytime.
Regards
Sent from my xperia TX via xda premium
Ok guys, new to the forums but this problem has had me fully occupied for the last 6 hours and I feel like I have tried everything. I had cm9 alpha 12, and went to flash TrickDroid v5.0, something happened and I'm currently stuck in some wierd bootloop/soft brick. I had access to CWM but my SD card wouldn't mount and my adb push attempts didn't do anything, for reasons I don't know why. My phone would start up into the wierd trickdroid bootup and last for like 30 minutes. I tried the solution of another thread on how to fix a bootloop/ softbrick, but now I dont have any CWM access and I can only access the bootloader or the endless bootup screen. I tried using the all in one tool to flash the CWM again but it just restarts it and puts it back into the bootup, and when i restart to go to bootloader to acess the recovery, it goes back to bootup. Every solution I try makes my problem worse, and to top it off I cant turn my phone off and keep it off because it will just start back up. Thanks.
Edit: Problem fixed. Downloaded the original all in 1 tool for htc one s, plugged phone into comp went to fastboot and with the tool flashed the phones stock recovery. I reset to factory defaults and cleared storage with it from the bootloader. After that, I flashed clockwork mod recovery again and my SD card was able to be mounted and accepted files from my adb push, and I reflashed cyanogenmod. Wuzzah!
milesmarrero said:
Ok guys, new to the forums but this problem has had me fully occupied for the last 6 hours and I feel like I have tried everything. I had cm9 alpha 12, and went to flash TrickDroid v5.0, something happened and I'm currently stuck in some wierd bootloop/soft brick. I had access to CWM but my SD card wouldn't mount and my adb push attempts didn't do anything, for reasons I don't know why. My phone would start up into the wierd trickdroid bootup and last for like 30 minutes. I tried the solution of another thread on how to fix a bootloop/ softbrick, but now I dont have any CWM access and I can only access the bootloader or the endless bootup screen. I tried using the all in one tool to flash the CWM again but it just restarts it and puts it back into the bootup, and when i restart to go to bootloader to acess the recovery, it goes back to bootup. Every solution I try makes my problem worse, and to top it off I cant turn my phone off and keep it off because it will just start back up. Thanks.
Click to expand...
Click to collapse
lol, meant to "quote" not "thanks".
Can you fastboot a new recovery?
Did you do a full wipe coming from CM9 to TrickDroid
Well I can't access the phone from usb on my computer (still takes charge though), so I don't think I can flash a recovery thru fastboot (I'm not too experienced though). From cm9, I wiped all and flashed trickdroid + tweak set, then it just stat their at home screen. CMW being lost occurred later.
Im in the same situation rght now. I have trickdroid and I went into my tweaks to set them back to their original setup...so removing all of the options I chose before when I used the tweaks for the first time. When I rebooted my phone it just hangs on the HTC screen. I can get into recovery and I tried reinstalling trickdroid but its still getting stuck. Not sure what to do at this point. I don't think I can put a recovery file on this since I can't connect it to my computer.
Hopefully someone can help us.
But the thing is I can't access recovery. I try to flash it again with the all in 1 tool and it won't work. It says it went through, but accessing it doesn't work.
If its recognised by USB when plugged in computer just run an ruu that's my solution all The time lol
Sent from my HTC One S using xda premium
Ok i somehow managed to get TWR on my phone, but still unable to mount the SD. How do I run the RUU? I downloaded it, but the instructions are flawed I think
Connect with USB to.computer go into faatboot USB then run ruu on pc
Sent from my HTC One S using xda premium
Well I thought the RUU was going to work, but it just stops at the HTC and gives me an error saying I can't. What now?
Ok currently, I relocked my bootloader in an attempt to do the RUU, but I get a 155 Unknown Error up doing such, using the TMOUS 1.53 ruu... other places I have seen say something about returning to the stock img etc, but I'm quite stuck. Any advice appreciated
htc one s stuck in bootloop almost unresponsive
hey guys, got a brain teaser for you.
i have a tmobile htc one s, unlocked, rooted using all in one htc tool, been at it for two days now. im stuck on the boot screen showing its unlocked, i used to be able to get into the boot loader screen but now it seems ive dead ended. ill hold any combination of power and vol up/down, the keys flash for 10 sec and the screen flashes once, i let go and it reboots, keeps that htc screen, after 20-30 sec goes black. my pc doings like it detects a device but i cant locate it. ive used adb and the htc all in one unlock tool trying to get any kind of os to launch.
Shortly before this i was able to go into the boot loader, clear and master reset the files and cache, and search for the rom zip, thus never allowing me to flash. on a journey to place this in the phone through various combinations of the all in one, adb push, and everything else i found on youtube, countless forum posts, i seem to be in a deeper hole now.
I ultimately want to end with a cm10 nightly on my tmo htc one s. I have never done this to a phone without a sd card. i come to this community humbly seeking any and all advice. thank you.
Hi everyone,
I am trying to help a buddy out and getting his phone working. The phone is not rooted in any way shape or form.
Here are my issues
The phone will not boot into the stock rom. I can get it into the bootloader. Which I went to htcdev. To unlock the bootloader. Followed the steps and was able to get the phone screen to show unlock bootloader. But when I hit yes it reboots and stays on the white htc screen. Then it will keep rebooting. When I go back into bootloader. It still shows the bootloader as being locked? Any suggestions. I haven't flashed anything in about 3 years. But only Samsung things.
This is my set up
Your best bet is to try latest RUU: http://www.htc.com/us/support/htc-one-sv-boost/news/
I tryed that as well. Thinking it is kinda like Odin for samsungs. But as soon as it try to reboot into bootloader. It stays on the white htc screen
The RUU was running completely through and it still not booting?
I will take a picture of the screen. It does not go all the way through. Also I tryed the Ota. Zip. And changed it to PL80IMG and placed it in my SD card. It looked as if it went through and it told me to reboot. But still nothing.
This is what's happening.
Forget the OTA. It won't solve anything for you.
I also think, your bootloader must be locked to run the RUU.
And i think it is your only chance to get the phone back running, because there is no stock rom or backup for boost (as far as i know).
I am OK with rooting it. But in order for me to do it I have to get the bootloader to unlock which I can't seem to do. It does all the motions to unlock. Until the phone reboots
What i have found in this few minutes, Error 171 should be a driver issue.
So, you should make sure that the correct drivers are running (HTC Sync). Maybe another PC could be also a good try.
And you can't root a phone which is not booting into OS. You need a OS.
Is there different drivers I could try besides tc sync. I have tried both computers that I have one has windows 8. The other has windows vista.both have htc sync on them. Also tried a different cable.
If I type in cmd fast boot devices it shows my device being connected. The error shows up while it is waiting for the boot loader to reconnect
Latest should be this.
I will give it a try thank you for helping me. I'm banging my head against the wall for 2 days trying to figure out why nothing is working on this.
Its really kinda strange, that bootloader should belocked again after reboot.
But your focus must be the RUU.
old.splatterhand said:
Its really kinda strange, that bootloader should belocked again after reboot.
But your focus must be the RUU.
Click to expand...
Click to collapse
Yea, my main goal is to get it to boot up. I was hoping it was an easy fix. Like with the Samsung epic I had. Just slap it in with odin and boom. after I couldn't get the RUU to work I figured I would try to root it. but since I can't even get the bootloader to unlock. I am stuck and that's the biggest reason I posted. normally I wouldn't I try to read other post and/or youtube it to find someone with a similar problem.
Quick question. When I go into the RUU can/should be in fastboot?
Yes, you should be in fastboot (USB) mode.
Ok so I downloaded the drivers you recommend. It was different then the ones I had. I also downloaded the RUU from the htc site as well just in case. Will try when I get back home. Thanks again.
So here is what I have. I downloaded driver v4.11.0.001. And installed. Downloaded ruu k2_cl_jb_45_s_sprint_wwe_boost_3.05.653.4......
I went into cmd and type fastboot devices. My device showed up. Ran the ruu. Samething happened. The ruu stops because when the phone reboots. It doesn't reboot to the bootloader.
Also I tried in cmd to get the phone to reboot to bootloader with no luck. Is there any thing else I can try?
I'm stuck in Bootloader/hboot. When I try to get into recovery it reboots back into hboot. I reinstalled a RUU of the latest 4.4.4 and I have reinstalled the recovery a couple of times. I am not getting an error when installing TWRP or the RUU.
The thing that's weird is that when its rebooting the HTC white screen does NOT have the red warning writing on the bottom.
Hboot states all the usual: Software status modified, S-Off, hboot 3.19, Radio 1.09.20.0926
I'm really at a loss. Please Help :crying:
mentallo said:
I'm stuck in Bootloader/hboot. When I try to get into recovery it reboots back into hboot. I reinstalled a RUU of the latest 4.4.4 and I have reinstalled the recovery a couple of times. I am not getting an error when installing TWRP or the RUU.
The thing that's weird is that when its rebooting the HTC white screen does NOT have the red warning writing on the bottom.
Hboot states all the usual: Software status modified, S-Off, hboot 3.19, Radio 1.09.20.0926
I'm really at a loss. Please Help :crying:
Click to expand...
Click to collapse
You sure the ruu completed?
When I "fastboot oem rebootRUU" in cmd it reboots but goes back into the Bootloader and doesn't go into the Black screen/Transfer screen.
The way I did the RUU was by placing it on the sdcard. It finished installing.
BTW is it normal that it says "Software Status: Modified"? I see some Screenshots from people where it doesn say that.
(The weird thing about all this is that the phone was working fine up until it started doing this. I was running Viper with the occasional Black Screen issue that plagues the rom right now.)
mentallo said:
When I "fastboot oem rebootRUU" in cmd it reboots but goes back into the Bootloader and doesn't go into the Black screen/Transfer screen.
The way I did the RUU was by placing it on the sdcard. It finished installing.
BTW is it normal that it says "Software Status: Modified"? I see some Screenshots from people where it doesn say that.
(The weird thing about all this is that the phone was working fine up until it started doing this. I was running Viper with the occasional Black Screen issue that plagues the rom right now.)
Click to expand...
Click to collapse
Does your phone work at this point?
Nope, I am searching for the answer but I am coming up empty. I'm at a loss. Could it be that the internal memory is fried or something? But in that case I wouldn't be able to install the RUU right?
same thing happened to me yesterday. I tried for hours yesterday and today doing anything to get Some sort of response out of it, as all that it would do is boot into hboot. I could use fastboot commands but I was never able to flash anything, usually said not allowed... I was on Digital High 5.0.1 from like 12/11 or something like that. So strange. Everything was running so smoothly, then it's like it just imploded. I'd be interested if you find a solution, but I ended up ordering a replacement phone from Verizon. Looks like I'm starting over...
Apparently the internal flash memory. {emmc} just died and nothing can be flashed to it. Phone is dead. There is nothing you can do to fix it.
thanks for the update. I was holding on to my broken phone before returning it to vzw in hopes that I could restore it; I guess I'll send it back today.
lazyboy0172 said:
thanks for the update. I was holding on to my broken phone before returning it to vzw in hopes that I could restore it; I guess I'll send it back today.
Click to expand...
Click to collapse
What commands did you run on it after it broke?
dottat, you helped with it remember? lol
mentallo said:
dottat, you helped with it remember? lol
Click to expand...
Click to collapse
Across four devices and a couple carriers I start to lose my marbles some. Or perhaps lollipops