few days after got my phone back from warranty,i did all the flashing.
after i updated my CWM to latest version from revolutionary CWM,i wiped cache.
and then I saw the 'cannot mount etc.' message.
I thought i will be safe as long as I didn't pull the battery.
then when I was downloading a game from market,my phone froze.
From my experience,I decided not to pull the battery and I held the volume buttons and power button for seconds instead.
Then,my phone's screen went black,and the phone vibrates for 7 times and refuses to power on anymore.
No abd,no fastboot,no nothing.
I guess i have to send it for warranty again.
What I want to ask is,if my phone has the bad emmc chips,how do I prevent it from having the same problem again?
tcchuin said:
few days after got my phone back from warranty,i did all the flashing.
after i updated my CWM to latest version from revolutionary CWM,i wiped cache.
and then I saw the 'cannot mount etc.' message.
I thought i will be safe as long as I didn't pull the battery.
then when I was downloading a game from market,my phone froze.
From my experience,I decided not to pull the battery and I held the volume buttons and power button for seconds instead.
Then,my phone's screen went black,and the phone vibrates for 7 times and refuses to power on anymore.
No abd,no fastboot,no nothing.
I guess i have to send it for warranty again.
What I want to ask is,if my phone has the bad emmc chips,how do I prevent it from having the same problem again?
Click to expand...
Click to collapse
sounds like another warranty return im afraid! you will just have to hope your replacement has the good chip
Android Flasher doesn't recognize your device either?
http://forum.xda-developers.com/showthread.php?t=794638
Ouch, thats unlucky mate
Sent from my HTC Desire S using xda premium
Related
Hi, i've got a big problem...
After a system crash i pull-out the battery and then pull-in to reset the device.
after that now when i turn on the telephone it remain stucked on the white screen with htc logo. tryed to factory reset but remain stucked after i press on it.
my htc has original rom. no modification. what can i do? i don't really want to spend 3 weeksfor htc assistance.
Thanks
Semi-bricked phone E:Can't mount /cache/recovery/command
[solved]BRICKed: inside eMMC's dead, with E:Can't open /cache/recovery/log
For everyone who Bricked their phone - Help prevent the others
[Guide] How to brick your Desire S
Have i to flash a stock rom? how can i do without remove warranty? in the case it does'nt work i have to take it to htc center
You probobly fried your EMMC chip when you removed your battery.
it would be best to return it in for repair.
I think you may have same problem with me before. No choice but to bring it to repair.
Sent from my HTC Desire S using XDA App
It was s-off before? Can you boot 2 recovery?
It's unlikely your chip is fried. This happened to my phone. You need to get into recovery - restart holding volume down button - and reflash a ROM, any one should do. The phone should reboot from there.
Edit: thus assumes you have a ROM stored on your phone, and you have Clockwork recovery or similar. If not, you can use adb to push a ROM to your card and reflash that. Adb comes with Android Developer Kit. Search!
Peace.
Sent from my HTC Desire S
chris5s said:
It's unlikely your chip is fried. This happened to my phone. You need to get into recovery - restart holding volume down button - and reflash a ROM, any one should do. The phone should reboot from there.
Edit: thus assumes you have a ROM stored on your phone, and you have Clockwork recovery or similar. If not, you can use adb to push a ROM to your card and reflash that. Adb comes with Android Developer Kit. Search!
Peace.
Sent from my HTC Desire S
Click to expand...
Click to collapse
Same problem as topic poster, i,ve been messing a lot with custom roms on win 6.5 phones, but I havn´t done anything fancy on my Desire S , as to rooting or custom roms. (work phone!) Now I´m just curious as how I get a recovery going, when the PC doesent recognice the device when USB connected.
The eng-off file (mine is ON) with the .bat file cant connect to phone, and maybe im better off sending it to repair, but my pride wants me to solve it myself.
-Damn phone just went AWOL last night after an marked Angry Birds update, rebooted it a couple of times, because of a lot of process errors, and then all dead. (white HTC screen on -until morning)
Have the latest FOTA (DK, Nordic)
ROM: SAGA PVT SHIP S-ON RL
Hboot: 0,98.0002
Radio: 3805.06.02.03_M
Are there any ninja tricks or is it just a "bite down", send in?
/Psudo
psudo said:
Same problem as topic poster ....
Are there any ninja tricks or is it just a "bite down", send in?
/Psudo
Click to expand...
Click to collapse
Maybe best sending it in if that's a viable option.
You say it's not rooted? With stock ROM? If there is a ROM on the sdcard that you can boot then try that - power + volume up + volume down will reboot the phone, try pressing volume down as it reboots to get into recovery.
If you can't (by pressing volume down) then power off and restart (holding volume down). I had to do a battery pull to power off - if you do this while the phone is off as it reboots, and leave it out for 30 secs you should avoid any danger of bricking the phone (which has happened with some people when removing battery while phone is in this state).
Good luck!
Peace
chris5s said:
Maybe best sending it in if that's a viable option.
You say it's not rooted? With stock ROM? If there is a ROM on the sdcard that you can boot then try that - power + volume up + volume down will reboot the phone, try pressing volume down as it reboots to get into recovery.
If you can't (by pressing volume down) then power off and restart (holding volume down). I had to do a battery pull to power off - if you do this while the phone is off as it reboots, and leave it out for 30 secs you should avoid any danger of bricking the phone (which has happened with some people when removing battery while phone is in this state).
Good luck!
Peace
Click to expand...
Click to collapse
"ROM on SDcard": what format would that be in? RUU.exe or?
I can get into recovery menu (HBOOT) but chosing recovery option results in "a green recycle icon with an arrow on black background" screen, a few seconds then it virbrates 6-8 times, and then fades to black, so to speak!
Factory reset option: Locks the HBOOT screen and nothing but a battery pull, will change that.
I MAY have pulled the battery and not left it out for the 30 sec bricking danger senario, that I wasn´t aware of, until resently.
So the diag. is that is probably bricked!
Thanks for the reply
/Psudo
Rom on sdcard would have to be *.zip to be flashable. If you're unrooted + stock then you won't have Clockwork recovery or similar.
Tough that factory reset doesn't give any joy. These devices.....
Looking like masonry then, unless someone else can help.
Peace
Sent from my HTC Desire S using xda premium
surprisingly i got the same issue yesterday after i installed proxuser's official htc rom. Everything started fine went through setup so i assume it's not because of the rom because i don't think the phone would've started up in the first place. Anyway i am about to try and install some different roms and have also copied a backup over from my other desire s.
Will let you guys know if it worked.
I just got a Inspire that will vibrate 3 times and then stop and blank screen.
Will not enter boot loader and get detected by usb.
Is this recoverable?
DJ_MiX said:
I just got a Inspire that will vibrate 3 times and then stop and blank screen.
Will not enter boot loader and get detected by usb.
Is this recoverable?
Click to expand...
Click to collapse
what have u done to get in that state?
glevitan said:
what have u done to get in that state?
Click to expand...
Click to collapse
That's the way I got it off ebay. Don't know the history but no water damage.
If I can't access bootloader or detected by computer maybe jtag will fix it? or any tools or methods to revive it?
DJ_MiX said:
That's the way I got it off ebay. Don't know the history but no water damage.
If I can't access bootloader or detected by computer maybe jtag will fix it? or any tools or methods to revive it?
Click to expand...
Click to collapse
Maybe it has a messed bootloader....it get into bootloader but take about 15 to 20 minutes....try that. Pull the battery, put it back and boot in hboot (power + volume down)....and leave it for about 30 minutes....
glevitan said:
Maybe it has a messed bootloader....it get into bootloader but take about 15 to 20 minutes....try that. Pull the battery, put it back and boot in hboot (power + volume down)....and leave it for about 30 minutes....
Click to expand...
Click to collapse
Tried that no luck.. Guess will need Jtaq or it hardware failure.
DJ_MiX said:
Tried that no luck.. Guess will need Jtaq or it hardware failure.
Click to expand...
Click to collapse
Try with a different battery...if that is not working, then it probably is a hardware issue...
DJ_MiX said:
I just got a Inspire that will vibrate 3 times and then stop and blank screen.
Will not enter boot loader and get detected by usb.
Is this recoverable?
Click to expand...
Click to collapse
I had a similar experience when i tried to root my phone, leave the battery out for about a week then put it in and power up to recovery. I was able to unbrick my phone.
Use AAHK....
DJ_MiX said:
I just got a Inspire that will vibrate 3 times and then stop and blank screen.
Will not enter boot loader and get detected by usb.
Is this recoverable?
Click to expand...
Click to collapse
...read the "Effen Manual" carefully about 3 times then use the feature that puts everything back to stock unrooted/stock RUU. Then use AAHK again to root the device and you should be good. I almost bricked my Inspire with HTCDevUnlock, and used AAHK in this way to fix it.
fatboyRICH said:
...read the "Effen Manual" carefully about 3 times then use the feature that puts everything back to stock unrooted/stock RUU. Then use AAHK again to root the device and you should be good. I almost bricked my Inspire with HTCDevUnlock, and used AAHK in this way to fix it.
Click to expand...
Click to collapse
If he is not able to get into fastboot he wont have a chance to get his phone back. Besides, the Hack Kit does not run from fastboot and running a device that is already S-OFF is useless.
Maybe, you should read the effen manual some more...
OK I had this problem. Take the battery out and let the phone sit for about half an hour. Then plug the phone in to a wall charger ( not the computer ) press the volume down button and press the power button until you see the HTC logo. After that keep holding the down button until it enters HBOOT. Use the vloume keys to select the reboot option and boot the phone. It worked for me. Hope it helps.
Sent from my Inspire 4G using xda app-developers app
My phone has done this twice as well. Both times taking the battery out for 30 minutes & then booting into recovery (volume down+power) fixed the problem for me
sorry for rekindling this thread, but im trying one of you guys' solutions as I type this. my girlfriends inspire died about 2 weeks ago. she fully charged it, and ran the battery out completely. havent tried a new battery yet but that will be the next step.
anyway. I havent messed with it for about a week. all it does is vibrate 7 times. No boot, no bootloader, no usb detection, anything. Pulled battery and gonna let sit for an hour before i put the battery back in, and try the bootloader method. I called ATT about it but they wont replace the device or anything. I read online about it being hard bricked, and if thats the case, that means the phone is just an expensive paperweight right? It was completely stock, no rooting or anything. the phone just died and wouldnt turn back on at all, even sitting on the charger over night.
Moved to Q & A section.
Sent from my Galaxy Nexus using Tapatalk 2
I am using a S3 HTC One S with stock 4.0.3 rom, rooted and unlocked bootloader. I was not carrying my charger with me and phone battery is finished to 0 and phone is closed. After I come home, I connect original charger to phone. Indication led is not flashing orange. I wait around half an hour. It does not flash now also. When I press power button around 7-8 seconds touch buttons blink 5-6 times and indication led begins flashing orange for 3-4 seconds and turns off. What should I do ?
Are you using CWM recovery? That's one fault with CWM, it will not charge the phone when off.
I am using TWRP. I entered recovery and reboot device from it. Problem solved but I still dont know problem.
rumnheim said:
I am using TWRP. I entered recovery and reboot device from it. Problem solved but I still dont know problem.
Click to expand...
Click to collapse
That's good to hear.
rumnheim said:
I am using TWRP. I entered recovery and reboot device from it. Problem solved but I still dont know problem.
Click to expand...
Click to collapse
how did you make it work? cuz i have the same problem... and since i cant charge it.. i dont think it has anymore battery left..
how do u go to recovery if you cant even open the damn phone?
Still orange led is not flashing, I kept my phone on charging. I pressed volume down and power buttons. It didnt open in first try. When I finally boot my phone normally it shows battery is 30%.
So while trying to put on a new ROM (I've rommed and done custom recoveries and radios on this phone before) I had TWRP recovery on it and the ROM I was going to wanted CWM on it, so I flashed that and on battery it will show Samsung logo then go into a 2 second vibrate boot loop.
None of the button combos work. I ordered a jig on ebay and it flashes download mode for about a second before it flashes again and goes into the 2 second vibrate mode again. I tried to go from jig to Odin and it saw it for a split second, but disconnected/failed as soon as it started looping.
I read about the power button issue and the behavior matches, but I know I was the one that messed this thing up.
Is the JTag repair service my only option at this point?
I got an S4 so I'm just trying to get this revived to get rid of it so too expensive and I'll just sell it for parts.
thanks in advance for the help!
Jeffro
jeffro7172 said:
I read about the power button issue and the behavior matches
Click to expand...
Click to collapse
Focus on that.
theesotericone said:
Focus on that.
Click to expand...
Click to collapse
The reason I dismissed that was because I actually did it twice.the first time I was able to get into odin.
So of course the next time I did it, I told it to reboot into recovery and that was the last command I gave it. Since recovery is hosed I think that's why it's just looping.
I guess it could be the power button but I think because I hosed recovery, it's just not booting.
This phone has a separate recovery partition. So even if you hosed the recovery it would still boot. Theory here, like I said I've never seen anyone report a recovery bootloop. I think it's just a timing issue. Power button happened to get stuck when you where flashing something. The fact that it won't hold DL mode further leads to the simple solution.
You got a stuck power button.
Isn't the sop for this problem a battery pull? If you take the battery out and put it back in and the phone tries to turn on by itself(lights or vibration) then it's a faulty power button.
jondroid2 said:
Isn't the sop for this problem a battery pull? If you take the battery out and put it back in and the phone tries to turn on by itself(lights or vibration) then it's a faulty power button.
Click to expand...
Click to collapse
makes sense guys, that's what it does. Guess it just so happened to crap out right when I was messing with it. Thank you all, I'll head that route and see if I can get it revived.
It indeed revived with a take apart and some power button fiddling. Thank you all very much!
I'm going to try to keep this as simple as possible as I don't really know what I did wrong or how I ended up where I am now.
I have a Samsung Galaxy 8+ and I decided to root it. I decided to follow this guy's instructions on how to do it: youtube.com/watch?v=eh-I4uxAmUY.
I follow his steps and am bought to the "Unmodified System Partition" menu after having gone through the process of factory resetting, wiping my data and using Odin to flash twrp-3.1.0-r1_dreamlteks.
The problem is that now the touch screen is unresponsive. It does literally nothing.
I am stuck at the screen that says "Keep System Read only?" where I have to "Swipe to Unlock Modifications", but find myself unable to do so because my touch screen doesn't let me swipe!
So now I'm panicking:
Firstly, I can't get the phone to shut down. Holding the power button does nothing, even if I hold it for a full minute.
Secondly, I can't boot the phone into anything except this unresponsive TWRP thing.
Thirdly, my computer no longer recognizes my phone when I try to connect it via USB (might be unrelated?).
How ****ed am I?
Is my phone just bricked now?
Can I save this rooting attempt in any way, or at least revert to the stock?
Will bringing the phone to a retailer help me in any way, or have I already broken the warranty?
Please guys I am desperate for some assistance here.
ViRALiC said:
I'm going to try to keep this as simple as possible as I don't really know what I did wrong or how I ended up where I am now.
I have a Samsung Galaxy 8+ and I decided to root it. I decided to follow this guy's instructions on how to do it: youtube.com/watch?v=eh-I4uxAmUY.
I follow his steps and am bought to the "Unmodified System Partition" menu after having gone through the process of factory resetting, wiping my data and using Odin to flash twrp-3.1.0-r1_dreamlteks.
The problem is that now the touch screen is unresponsive. It does literally nothing.
I am stuck at the screen that says "Keep System Read only?" where I have to "Swipe to Unlock Modifications", but find myself unable to do so because my touch screen doesn't let me swipe!
So now I'm panicking:
Firstly, I can't get the phone to shut down. Holding the power button does nothing, even if I hold it for a full minute.
Secondly, I can't boot the phone into anything except this unresponsive TWRP thing.
Thirdly, my computer no longer recognizes my phone when I try to connect it via USB (might be unrelated?).
How ****ed am I?
Is my phone just bricked now?
Can I save this rooting attempt in any way, or at least revert to the stock?
Will bringing the phone to a retailer help me in any way, or have I already broken the warranty?
Please guys I am desperate for some assistance here.
Click to expand...
Click to collapse
You have voided your warranty so you can't take it down to the shop and get it replaced.
It isn't fully bricked because you can still boot into an "os" that isn't fully functional. It ain't recognised because you have to swipe past this and hop into the ADB sideload interface. Btw, try holding your home button, power button and volume up (or down) and report results.
If I was you, I would wait till the battery drains and shuts off and then let it be off for the rest of the night or something and then try again.
RAZERZDAHACKER said:
You have voided your warranty so you can't take it down to the shop and get it replaced.
It isn't fully bricked because you can still boot into an "os" that isn't fully functional. It ain't recognised because you have to swipe past this and hop into the ADB sideload interface. Btw, try holding your home button, power button and volume up (or down) and report results.
If I was you, I would wait till the battery drains and shuts off and then let it be off for the rest of the night or something and then try again.
Click to expand...
Click to collapse
Alright, I'll give it until it passes out from battery loss and then get back on when things change. Thanks for the reply!