Related
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
Hi, I've got a little sceary problem with my desire s.
I installed reaper v 1.2 ROM, configured it, everything was ok. But now phone is not responding. Only black screen. I tried vol up/down and power button configuration - nothing happend. I connected phone to the charger and led turned on, I tred the same configuration - nothing happend. I discconnect phone - led is still on and phone is not responding.
I downloaded latest android sdk tools, latest htc drivers, installed, connected phone to computer, run sdk tool and type adb reboot recovery - error device not found.
When I connect phone to computer it found Qualcomm CDMA Technologies MSM, I try to install soft automaticly but comp find nothing.
Wha else I can do? I don't want pull battery. I have never done it.
Help, please.
adix631 said:
Hi, I've got a little sceary problem with my desire s.
I installed reaper v 1.2 ROM, configured it, everything was ok. But now phone is not responding. Only black screen. I tried vol up/down and power button configuration - nothing happend. I connected phone to the charger and led turned on, I tred the same configuration - nothing happend. I discconnect phone - led is still on and phone is not responding.
I downloaded latest android sdk tools, latest htc drivers, installed, connected phone to computer, run sdk tool and type adb reboot recovery - error device not found.
When I connect phone to computer it found Qualcomm CDMA Technologies MSM, I try to install soft automaticly but comp find nothing.
Wha else I can do? I don't want pull battery. I have never done it.
Help, please.
Click to expand...
Click to collapse
Don't panic brother. I've been in a similar situation many times. Whatever you do... DO NOT PULL THE BATTERY till the phone is switched off!!
Just disconnect the phone from the laptop or wall socket (remove the usb cable from the phone) and leave the phone. Don't sit and stare at it, and don't try to reason it into rebooting. Also, stop pestering God...he doesn't do phones. (I think) Just relax, and go watch T.V. or something.
One out of two things may happen :
1. It may reboot on it's own. Has happened to me... Sometimes it happes in 5 mins, sometimes in 20, and sometimes, never.
2. The battery will eventually run out of charge and your phone will switch off by itself. Now remove the battery, reinsert after 2 mins and boot up into recovery. From here, you can restore your previous nandroid backup.
P.S. If you do not have a nandroid backup, just reflash the ROM after a full format ("format all partitions, except sdcard" option in recovery). Note that if you have unlocked using HTC site, this will not work until you manually flash boot.img (you can find it in the ROM (Reaper_v1.2.zip) file) from fastboot.
Let me know what happens.
Now I' still waiting, without phone touching. Led is ON (orange colour). Phone is disconected (and me too ). Battery level was 13% before this insydent.
When LED will turn off (I don't know when) I'll reinsert battery and let you know what's up.
I hope, I did't bricked it...
adix631 said:
Now I' still waiting, without phone touching. Led is ON (orange colour). Phone is disconected (and me too ). Battery level was 13% before this insydent.
When LED will turn off (I don't know when) I'll reinsert battery and let you know what's up.
I hope, I did't bricked it...
Click to expand...
Click to collapse
Don't worry. I am virtually a 100% sure you have NOT bricked it.
Just don't panic and let the phone switch off first.
BTW, you didn't say if you unlocked your bootloader with HTC Dev site or Revolutionary?
Do you have a Nandroid backup of your previous ROM ?
How new are you to all this (flashing etc)?
Is this the first custom ROM you have flashed on this device?
enigmaamit said:
Don't worry. I am virtually a 100% sure you have NOT bricked it.
Just don't panic and let the phone switch off first.
BTW, you didn't say if you unlocked your bootloader with HTC Dev site or Revolutionary?
Do you have a Nandroid backup of your previous ROM ?
How new are you to all this (flashing etc)?
Is this the first custom ROM you have flashed on this device?
Click to expand...
Click to collapse
My phone was s-off by xtc clip (I did't use revolutionary), boot loader was unlocked on HTC Dev site.
I flashed at first CMW recover, than 4EXT Touch recovery and used it.
I tried a lot of roms, virtuous, endymnion, runny. The best for the beast was CM7.1, nightly. I flashed it month ago and updated succefully. Two days ago I decided to try REAPER. I wiped cache and dalvik's, than flashed reaper v 1.1. Today I updated it to 1.2 version (the same way as always) and I had a problem with dialer, so I wiped everything. Format all ex. sd card was done and I flashed reaper 1.2. I confogured it, just I like (set a new gov reaper, freq 118 (I don't remember) low and 1074 high) and thats it. I tried laucher, sms, phone and thats all.
adix631 said:
My phone was s-off by xtc clip (I did't use revolutionary), boot loader was unlocked on HTC Dev site.
I flashed at first CMW recover, than 4EXT Touch recovery and used it.
I tried a lot of roms, virtuous, endymnion, runny. The best for the beast was CM7.1, nightly. I flashed it month ago and updated succefully. Two days ago I decided to try REAPER. I wiped cache and dalvik's, than flashed reaper v 1.1. Today I updated it to 1.2 version (the same way as always) and I had a problem with dialer, so I wiped everything. Format all ex. sd card was done and I flashed reaper 1.2. I confogured it, just I like (set a new gov reaper, freq 118 (I don't remember) low and 1074 high) and thats it. I tried laucher, sms, phone and thats all.
Click to expand...
Click to collapse
Well in that case, don't worry your phone is safe. Just wait for it to switch off. Then after booting into recovery, just restore the last working ROM backup that you have. Don't flash the Reaper 1.2 that you downloaded till you have confirmed that the md5 checksum matches the one posted by Lowveld.
Hmm. Strange.
Phone turned off - LED was off, so I pulled battery, wait 2-5 minutes (without battery) and tried to turn it on. I saw a black screen. I press vol up/down power buttons, phone vibrated 3 times (quick) and I saw a green LED. I tried turn it on (with vol down button and without it) - nothing. I waited a while then a Led turned off.
I pluged device to the charger - orange led started blinking, so I tried to on phone - nothing. I restarted it (3 buttons) - it vibrated 3 times quickly and the same story from my first post.
Phone is unplugged, orange led is on (not blinking) and no react.
Any ideas??
Can you still boot to recovery?
adix631 said:
Hmm. Strange.
Phone turned off - LED was off, so I pulled battery, wait 2-5 minutes (without battery) and tried to turn it on. I saw a black screen. I press vol up/down power buttons, phone vibrated 3 times (quick) and I saw a green LED. I tried turn it on (with vol down button and without it) - nothing. I waited a while then a Led turned off.
I pluged device to the charger - orange led started blinking, so I tried to on phone - nothing. I restarted it (3 buttons) - it vibrated 3 times quickly and the same story from my first post.
Phone is unplugged, orange led is on (not blinking) and no react.
Any ideas??
Click to expand...
Click to collapse
Well, the blinking signifies inadequate charge for a bootup. Wait till the orange LED stopsa blinking and turns on constantly... then boot into bootloader (Voulme up and Power button - don't let go of the volume button even after releasing the power button) - I don't want you to restart by using three button combo...otherwise you'll be back to the same problem, trying to boot into a broken OS... Just disconnect again and wait for it to switch off.... then reinsert battery, connect to charger, then wait for the LED blinking to stop. Have a little patience! and DON"T RESTART with three button combo. Just boot into bootloader with Voulme up + Power key.
You have to follow these instructions carefully, exactly as i have written. Report back what happens.
enigmaamit said:
Well, the blinking signifies inadequate charge for a bootup. Wait till the orange LED stopsa blinking and turns on constantly... then boot into bootloader (Voulme up and Power button - don't let go of the volume button even after releasing the power button) - I don't want you to restart by using three button combo...otherwise you'll be back to the same problem, trying to boot into a broken OS... Just disconnect again and wait for it to switch off.... then reinsert battery, connect to charger, then wait for the LED blinking to stop. Have a little patience! and DON"T RESTART with three button combo. Just boot into bootloader with Voulme up + Power key.
You have to follow these instructions carefully, exactly as i have written. Report back what happens.
Click to expand...
Click to collapse
I did it exactly like you've written. Waited till phone, switch off, connected it and charged till led stopped blinking, disconnect, and try to boot it into recovery (vol up + power). Phone wibrated 3 times (screen did't react) and the same story. Now waiting for discharging and I'll try again.
Anyway thanks for your help and interest.
What else I can do? If the phone is not responding I can send it to warranty service. Meybe they will honour it... If not...ehss very expensive play.
adix631 said:
I did it exactly like you've written. Waited till phone, switch off, connected it and charged till led stopped blinking, disconnect, and try to boot it into recovery (vol up + power). Phone wibrated 3 times (screen did't react) and the same story. Now waiting for discharging and I'll try again.
Anyway thanks for your help and interest.
What else I can do? If the phone is not responding I can send it to warranty service. Meybe they will honour it... If not...ehss very expensive play.
Click to expand...
Click to collapse
Well, it that's not workin, Wait till the phone switches off again. Then configure adb, make sure it detects your device (use the command: adb devices) and then type the following at the cmd prompt :
adb reboot recovery
This should take you to recovery.
Ok, what can I say? Youe last thread worked!! I restared device, connect to computer - it was found as usb disk. In sdk tool divece was also found, this time as my ds Just restarted a recovery. First I saw an error in 4ext recovery, but it started with orange letters. I wiped all, formated all, recover old system, restart phone. And it works! Now I flshesd last jorgens CM7 and starting to config my phone. But a heart attack was close... Thanks man
adix631 said:
Ok, what can I say? Youe last thread worked!! I restared device, connect to computer - it was found as usb disk. In sdk tool divece was also found, this time as my ds Just restarted a recovery. First I saw an error in 4ext recovery, but it started with orange letters. I wiped all, formated all, recover old system, restart phone. And it works! Now I flshesd last jorgens CM7 and starting to config my phone. But a heart attack was close... Thanks man
Click to expand...
Click to collapse
You're welcome brother! And Congratulations!!
I know what you must have gone through till you reclaimed your phone. I remember the first time i was in a situation like yours... had to figure out this discharge the phone, LED blinking etc... thing on my own..., everyone else said battery pull was my only option. But i sitll didn't do it. I had around 60% battery remaining before this happened, so you can only imagine how many sleepless hours i spent waiting for the damn battery to run dry. http://forum.xda-developers.com/showthread.php?t=1271360
The important thing is to resist the temptation of pulling battery. Everything can be salvaged if you don't do that, but once you fry your eMMC, there is nothing anyone can do without physically repairing the phone.
May I suggest you edit the topic your OP and add the word [SOLVED] to the title. This will ensure anyone in trouble can easily locate this thread out of the cacophony on xda!
I am rooted and unlocked. I was running CM10 and tried to flash Lean Kernel on it (I have never tried to flash a different kernel so I have a feeling this is where I went wrong). After flashing the new Kernel, the Samsung Galaxy SIII boot logo would appear, then go away and leave the hardware keys lit up. Now I can't get any activity out of my phone other than when I pull my battery and put it back in. When I put the battery back in the phone vibrates, the red LED comes on, and I get a battery logo with a loading circle then the screen goes black. I have tried booting into download and the bootloader but gotten nothing. I have never been able to boot into bootloader using the power and volume down, I've always had to go to the restart menu. My battery was fairly low (about 10%) when I tried flashing the kernel. Is there any way to fix this?
I have a CWM backup as well as TiBu and Nova Launcher backups. Please help!
chaplngrillsgt said:
I am rooted and unlocked. I was running CM10 and tried to flash Lean Kernel on it (I have never tried to flash a different kernel so I have a feeling this is where I went wrong). After flashing the new Kernel, the Samsung Galaxy SIII boot logo would appear, then go away and leave the hardware keys lit up. Now I can't get any activity out of my phone other than when I pull my battery and put it back in. When I put the battery back in the phone vibrates, the red LED comes on, and I get a battery logo with a loading circle then the screen goes black. I have tried booting into download and the bootloader but gotten nothing. I have never been able to boot into bootloader using the power and volume down, I've always had to go to the restart menu. My battery was fairly low (about 10%) when I tried flashing the kernel. Is there any way to fix this?
I have a CWM backup as well as TiBu and Nova Launcher backups. Please help!
Click to expand...
Click to collapse
To boot into bootloader using the power + volume down + Home button.
Volume Up + Home + PWR = recovery
Volume Down + Home + PWR = download
Push and HOLD each button in the above sequence.
I think Lean Kernel is for ICS/TWiz only.
Get into recovery and restore your backup ...
Sent from my SCH-I535 using xda premium
pdinphx said:
Volume Up + Home + PWR = recovery
Volume Down + Home + PWR = download
I think Lean Kernel is for ICS only.
Get into recovery and restore your backup ...
Sent from my SCH-I535 using xda premium
Click to expand...
Click to collapse
Ok, so I've tried booting into both modes and it's not working. I'm thinking that in the process of my phone not working that the battery died... If the kernel is bad then the phone won't charge, correct? It's been a while since I've had my battery completely dead, is the battery with the loading symbol in it the indication that the battery is dead?
chaplngrillsgt said:
Ok, so I've tried booting into both modes and it's not working. I'm thinking that in the process of my phone not working that the battery died... If the kernel is bad then the phone won't charge, correct? It's been a while since I've had my battery completely dead, is the battery with the loading symbol in it the indication that the battery is dead?
Click to expand...
Click to collapse
Why don't you plug in and let it charge for 3 hrs and try the process again?
buhohitr said:
Why don't you plug in and let it charge for 3 hrs and try the process again?
Click to expand...
Click to collapse
I have it on a charger right now and have had it there for about an hour with no success. I'll let it sit for a while and try the process again in the morning. If this doesn't work, are there other options??
Edit: If I get a new phone, will restoring using the CWM backup restore my app data and such?
chaplngrillsgt said:
I have it on a charger right now and have had it there for about an hour with no success. I'll let it sit for a while and try the process again in the morning. If this doesn't work, are there other options??
Click to expand...
Click to collapse
I would let it charge to full, then pull the battery, let it sit for a few hrs the give it another try. You have to call Verizon service for replacement if you can't get into recovery or download mode, probably the best way.
buhohitr said:
I would let it charge to full, then pull the battery, let it sit for a few hrs the give it another try. You have to call Verizon service for replacement if you can't get into recovery or download mode, probably the best way.
Click to expand...
Click to collapse
Ok, I'll let it charge while I sleep then try in the morning. Luckily I have the Best Buy protection plan so I can get a new (or refurbished) phone for free. Will restoring the CWM backup restore everything (app data, etc)? I'm assuming I'll need to root, unlock, and flash CWM onto the new phone.
Thanks for the help.
good luck
chaplngrillsgt said:
Ok, I'll let it charge while I sleep then try in the morning. Luckily I have the Best Buy protection plan so I can get a new (or refurbished) phone for free. Will restoring the CWM backup restore everything (app data, etc)? I'm assuming I'll need to root, unlock, and flash CWM onto the new phone.
Thanks for the help.
Click to expand...
Click to collapse
wish i can just like you
buhohitr said:
I would let it charge to full, then pull the battery, let it sit for a few hrs the give it another try. You have to call Verizon service for replacement if you can't get into recovery or download mode, probably the best way.
Click to expand...
Click to collapse
Thank you, thank you, thank you! When I woke up this morning I was able to boot into CWM and restore my backup. I apologize for being a bit frantic
Hi, Everytime my phones battery dies, when i plug it back into recharge, it always boots into recovery. I cant get it to reboot normal until it plugged in for about 5-10 minutes. I have to hold the power button for a while and finally it boots back normal. Any idea why It does that? and how to fix? Its a pain if I have to make a call after finding a charger. Any help is appreciated.
sk8er982 said:
Hi, Everytime my phones battery dies, when i plug it back into recharge, it always boots into recovery. I cant get it to reboot normal until it plugged in for about 5-10 minutes. I have to hold the power button for a while and finally it boots back normal. Any idea why It does that? and how to fix? Its a pain if I have to make a call after finding a charger. Any help is appreciated.
Click to expand...
Click to collapse
Let me guess CWM recovery? if so swap to TWRP but you will still need to leave it to charge for 5-10 minutes before it will boot and to add this isnt good to let it run out of power, it has been known to mess up and need to be factory reset to work again.
Ill try it
Darknites said:
Let me guess CWM recovery? if so swap to TWRP but you will still need to leave it to charge for 5-10 minutes before it will boot and to add this isnt good to let it run out of power, it has been known to mess up and need to be factory reset to work again.
Click to expand...
Click to collapse
Yes CWM. Ill try it and report back. Thanks!
I agree with dark. I had this issue with CWM, switched to TWRP and it works perfectly fine.
But, dont let it run out of juice, the odds that it wont boot is quite high. In both my cases I had to reflash boot.img through fastboot before the device started properly.
If you dont have access to a charger, and the device is about to run out of power - shut it down! Dont let it self-die!
it happend to me , i just reboot using the recovery. No need for hard reboot.
Sent from my HTC One S Special Edition using xda app-developers app
Hello Guys,
My OnePlus One screen broke, it was in my drawer for more than 15 days without charge, i connected charger for 1 hour it just went from 1% to 5% but i didnt thought much about it as my priority was to change screen, i bought touch+lcd with frame and replaced it myself, but it wasnt powering up then i tried putting the backpanel on, it then booted up to the home screen, but the battery indicator wasnt moving up i powered off the phone after that it never turned on, i researched a bit and found out the after long period of time if you dont charge your phone might have problem charging and there was one suggestion which i followed and that was charge OPO using usb cable attached to PC, i left it for somewhat 7hours and it powered on i thought it might be the problem of ROM i flashed official H2OS (regret selecting this rom) using TWRP, it was a catastrophe my phone wont Enter Bootloader or Recovery, and wont even boot to system, it seemed i hardbricked my device, i used Oneplus one recovery tool 64GB to bring my device to life but after that no matter what i do my device wont enter to bootloader as the volume up button stopped working too : tried advance reboot, powerup+volumeup, opo toolkit.
Help me, i want to root my device and unlock bootloader once again.
Pra7ul said:
Hello Guys,
My OnePlus One screen broke, it was in my drawer for more than 15 days without charge, i connected charger for 1 hour it just went from 1% to 5% but i didnt thought much about it as my priority was to change screen, i bought touch+lcd with frame and replaced it myself, but it wasnt powering up then i tried putting the backpanel on, it then booted up to the home screen, but the battery indicator wasnt moving up i powered off the phone after that it never turned on, i researched a bit and found out the after long period of time if you dont charge your phone might have problem charging and there was one suggestion which i followed and that was charge OPO using usb cable attached to PC, i left it for somewhat 7hours and it powered on i thought it might be the problem of ROM i flashed official H2OS (regret selecting this rom) using TWRP, it was a catastrophe my phone wont Enter Bootloader or Recovery, and wont even boot to system, it seemed i hardbricked my device, i used Oneplus one recovery tool 64GB to bring my device to life but after that no matter what i do my device wont enter to bootloader as the volume up button stopped working too : tried advance reboot, powerup+volumeup, opo toolkit.
Help me, i want to root my device and unlock bootloader once again.
Click to expand...
Click to collapse
adb reboot bootloader
waterdaan said:
adb reboot bootloader
Click to expand...
Click to collapse
That Just Reboots it to system, i have turned adb on and clicked on trust this connection i have checked adb devices, and it shows attached devices too,
it just wont reboot to bootloader, but i can enter recovery. Help Please.
Pra7ul said:
That Just Reboots it to system, i have turned adb on and clicked on trust this connection i have checked adb devices, and it shows attached devices too,
it just wont reboot to bootloader, but i can enter recovery. Help Please.
Click to expand...
Click to collapse
Is your volume up button actually broken or does it still work and can you boot into something? If it still works (hold on, this idea might be a little crazy xD) you could try completely hard bricking (no joke! you cannot get into Qualcomm download mode with a booting device) and restoring it with the msm8974downloadtool from the oneplus one unbricking guide which should theoretically fix everything that is wrong.
noahvt said:
Is your volume up button actually broken or does it still work and can you boot into something? If it still works (hold on, this idea might be a little crazy xD) you could try completely hard bricking (no joke! you cannot get into Qualcomm download mode with a booting device) and restoring it with the msm8974downloadtool from the oneplus one unbricking guide which should theoretically fix everything that is wrong.
Click to expand...
Click to collapse
Even If my volume button dosent work then why wont it enter bootloader via advance reboot it just restarts to system after selecting reboot to bootloader,so i should hard brick my device once again, P.S. i have done that twice before though.