Related
Are they going to fix the bug anytime soon? trying to fix my battery and all methods consist of charging it off..
Sent from my DesireT4G, thanks to a Gr8 gorilla!
Honestly I've had fine luck with simply wiping battery stats when phone is fully charged, rebooting, removing from charger and going on with my life. Never found the need to "recalibrate" beyond what I just said.
Try it.
Thanks I just found that if you turn fastboot on that is a way to work around the cw bug.
Sent from my DesireT4G, thanks to a Gr8 gorilla!
Jaskwith said:
Thanks I just found that if you turn fastboot on that is a way to work around the cw bug.
Sent from my DesireT4G, thanks to a Gr8 gorilla!
Click to expand...
Click to collapse
What do you mean? Fastboot, plug in, then power down and it stays off while charging?
Phateless said:
What do you mean? Fastboot, plug in, then power down and it stays off while charging?
Click to expand...
Click to collapse
Correct.
Sent from my DesireT4G, thanks to a Gr8 gorilla!
Jaskwith said:
Correct.
Sent from my DesireT4G, thanks to a Gr8 gorilla!
Click to expand...
Click to collapse
No ****, will try that tonight.
Yes there is another thread I mentioned this fix. It works.
Sent from my HTC Glacier using XDA App
jjlean said:
Yes there is another thread I mentioned this fix. It works.
Sent from my HTC Glacier using XDA App
Click to expand...
Click to collapse
Didn't work for me. Did you mean fastboot or hboot?
Phateless said:
Didn't work for me. Did you mean fastboot or hboot?
Click to expand...
Click to collapse
Seems fastboot needs to be on, and phone plugged before powering off. This worked for me
esincho said:
Seems fastboot needs to be on, and phone plugged before powering off. This worked for me
Click to expand...
Click to collapse
This works because with fastboot turned on, your phone doesn't completely shut off. It goes into hibernation mode without clearing memory. It's more of an illusion of a fix than anything.
Swyped on my rooted MyTouch4G
esincho said:
Seems fastboot needs to be on, and phone plugged before powering off. This worked for me
Click to expand...
Click to collapse
Fastboot in MENU --> SETTINGS --> APPLICATIONS in stock rom?
XfooYen said:
This works because with fastboot turned on, your phone doesn't completely shut off. It goes into hibernation mode without clearing memory. It's more of an illusion of a fix than anything.
Swyped on my rooted MyTouch4G
Click to expand...
Click to collapse
This is true...
You also need to change your Connect to PC option from "Disk Drive" to "Charge only" and your phone won't turn on into Recovery Mode with it "Off" and plugged into the wall charger... Last night, I had the phone turn itself on in Recovery Mode, after I had completely turned it off, until I rebooted and changed the Connect to PC option and tried the recharging procedure that way again... Then it charged with the phone off, the way it should.
Not working for me, phone still turns on in recovery menu. Any other ideas ?
henryblank said:
Not working for me, phone still turns on in recovery menu. Any other ideas ?
Click to expand...
Click to collapse
If you're on the stock ROM enable fast boot in MENU, SETTINGS, APPLICATIONS.
I'm on Evil Z ROM, FASTBOOT doesn't work ... still powers up in Recovery.
henryblank said:
I'm on Evil Z ROM, FASTBOOT doesn't work ... still powers up in Recovery.
Click to expand...
Click to collapse
Hate to day this bro, but known bug. Deal with it. :-\
I don't know if the phone is bricked, i sure hope not.
I had cm7 final running just fine. I was installing a kernel from clockwork recovery, and i followed the instructions. It installed, i told it to reboot the phone, it came to the cm7 blue booting screen. it kept repeating that for over 20 minutes. at that point i pulled the battery and replaced it. then i think it was stuck at the tmobile splash screen for a while. i was able to reboot and get to recovery mode again, i wiped cache and tried to install the kernel again, this time got an error. now it went to tmo splash screen and froze there for a while. after another battery pull, nothing will display on the screen and i cannot access recovery mode (i try by holding volume down, then holding power button). the ONLY thing that does happen is that the lcd backlight will stay on until i pull the battery. i plugged into pc without the battery, lcd lights up, but its not recognized by windows or adb.
I'd be grateful for any possible help or ideas, thanks in advance.
Could you give more info on Rom recovery kernel you were attempting etc?
Sent from my HTC Glaciee using XDA Premium App
Jay10826 said:
I don't know if the phone is bricked, i sure hope not.
I had cm7 final running just fine. I was installing a kernel from clockwork recovery, and i followed the instructions. It installed, i told it to reboot the phone, it came to the cm7 blue booting screen. it kept repeating that for over 20 minutes. at that point i pulled the battery and replaced it. then i think it was stuck at the tmobile splash screen for a while. i was able to reboot and get to recovery mode again, i wiped cache and tried to install the kernel again, this time got an error. now it went to tmo splash screen and froze there for a while. after another battery pull, nothing will display on the screen and i cannot access recovery mode (i try by holding volume down, then holding power button). the ONLY thing that does happen is that the lcd backlight will stay on until i pull the battery. i plugged into pc without the battery, lcd lights up, but its not recognized by windows or adb.
I'd be grateful for any possible help or ideas, thanks in advance.
Click to expand...
Click to collapse
Um sorry to say but your screwed. Sounds like a true brick to me
Sent from my HTC Glacier using XDA Premium App
Can you boot into the bootloader? Which one is installed? How can we help if we have no idea what's installed on your phone? There could be hope if you can boot into the bootloader and have the engineering SPL installed.
Also, what kernel were you trying to install?
TeeJay3800 said:
Can you boot into the bootloader? Which one is installed? How can we help if we have no idea what's installed on your phone? There could be hope if you can boot into the bootloader and have the engineering SPL installed.
Also, what kernel were you trying to install?
Click to expand...
Click to collapse
He already stated that he could not boot into h boot
Sent from my HTC Glacier using XDA Premium App
mark manning said:
He already stated that he could not boot into h boot
Click to expand...
Click to collapse
He did? I only saw that he could not boot into recovery. I was thinking if his recovery is screwed up, he could still use fastboot to flash a new recovery and then be able to wipe and start over. If he can't get into the bootloader or recovery, then yeah, it's the dreaded B word.
I'd really like to know what kernel he was trying to flash.
TeeJay3800 said:
I'd really like to know what kernel he was trying to flash.
Click to expand...
Click to collapse
Me too......
TeeJay3800 said:
I'd really like to know what kernel he was trying to flash.
Click to expand...
Click to collapse
First thing I asked.. still no reply kinda sucks when they can't help by responding so we can help them..
Sent from my HTC Glaciee using XDA Premium App
I was flashing the #107 kernel from this thread:
[Kernel]Gingerbread[2.6.32.36]MaxOC~1.84GHz,Smartass/UV/BFS/BFQ/SLQB-Faux123[Apr-10]
http://forum.xda-developers.com/showthread.php?t=957267
I'm not sure if there's a different procedure to get into hboot as opposed to recovery. I've only had the mytouch 4g for about a week (always had Nexus one before). After pulling and replacing the battery, i hold volume down, then hold power button. Is that how to get into recovery and/or hboot, or is there another procedure I can try?
I used the visionary app to obtain root, install rom manager, then installed clockword mod recovery and cm7 through that. Working fine for a few days until i decided to flash the kernel to get better battery life....
Jay10826 said:
I was flashing the #107 kernel from this thread:
[Kernel]Gingerbread[2.6.32.36]MaxOC~1.84GHz,Smartass/UV/BFS/BFQ/SLQB-Faux123[Apr-10]
http://forum.xda-developers.com/showthread.php?t=957267
I'm not sure if there's a different procedure to get into hboot as opposed to recovery. I've only had the mytouch 4g for about a week (always had Nexus one before). After pulling and replacing the battery, i hold volume down, then hold power button. Is that how to get into recovery and/or hboot, or is there another procedure I can try?
I used the visionary app to obtain root, install rom manager, then installed clockword mod recovery and cm7 through that. Working fine for a few days until i decided to flash the kernel to get better battery life....
Click to expand...
Click to collapse
Unfortunatly its the same procedure, hold volume down and power on. So if when u do that nothing happens and adb doesn't work your phone is done.
Sent from my HTC Glacier using XDA Premium App
A little more info, maybe good news...i've been trying to get it to do anything for the last few hours. i had the battery out for a while. When i would plug it into AC charger or my pc with no battery, nothing would happen. however now i put in the battery, plugged it into the pc, and NOW the orange charging light is on like its charging...i haven't tried to turn it on or anything yet though.
Jay10826 said:
A little more info, maybe good news...i've been trying to get it to do anything for the last few hours. i had the battery out for a while. When i would plug it into AC charger or my pc with no battery, nothing would happen. however now i put in the battery, plugged it into the pc, and NOW the orange charging light is on like its charging...i haven't tried to turn it on or anything yet though.
Click to expand...
Click to collapse
I'm not sure what the exact status of your phone is, but usually flashing a kernel does not brick the phone. If anything the ROM won't run right or there will be other problems, but never do they prevent the phone from booting into recovery (the recovery partition uses a completely different kernel). When you try turning it on again, don't bother trying to let it boot normally. Hold down power and volume down and see if you can get into recovery. Then run all three wipe options and flash a new ROM.
Jay10826 said:
A little more info, maybe good news...i've been trying to get it to do anything for the last few hours. i had the battery out for a while. When i would plug it into AC charger or my pc with no battery, nothing would happen. however now i put in the battery, plugged it into the pc, and NOW the orange charging light is on like its charging...i haven't tried to turn it on or anything yet though.
Click to expand...
Click to collapse
It's happened to me before where I thought I had completely bricked the phone. It crashed in CM7 RC2 when I tried to mess with the DSP settings. After that, I went through the same situation as you. I got tired of it, left it charging overnight while it was stuck on the splash screen. The next morning, it was on like nothing happened. I'm thinking it just needed to sort itself out. Not really a fix or suggestion, but at least an indication that there is hope.
Nah, its dead man. Not on its entirety but virtually. I know that JTAG could be an option albeit, im not sure.
I can assure you though that there must be something extra u must have missed that caused this, did you play with radio's or SPL's? Cause that is how i bricked a magic lol
blah
mine bricked on restoring. got to the point of not responding to anything - power button and even charge indicator no longer worked.
sorry to hear OP. it's bricked.
Jay10826 said:
I was flashing the #107 kernel from this thread:
[Kernel]Gingerbread[2.6.32.36]MaxOC~1.84GHz,Smartass/UV/BFS/BFQ/SLQB-Faux123[Apr-10]
http://forum.xda-developers.com/showthread.php?t=957267
I'm not sure if there's a different procedure to get into hboot as opposed to recovery. I've only had the mytouch 4g for about a week (always had Nexus one before). After pulling and replacing the battery, i hold volume down, then hold power button. Is that how to get into recovery and/or hboot, or is there another procedure I can try?
I used the visionary app to obtain root, install rom manager, then installed clockword mod recovery and cm7 through that. Working fine for a few days until i decided to flash the kernel to get better battery life....
Click to expand...
Click to collapse
By saying that you used the visionary app to obtain root, is that all you did? Then installed rom manager and etc etc etc? Did you go through the full root method to get S=OFF as well?
Well previous to using visionary...i was trying another method to root using the terminal, but it wasn't working, so then i found visionary and used that. I never interacted with the phone using adb, if it matters. If i never really had s=off, could this be why this whole thing happened?
Jay10826 said:
If i never really had s=off, could this be why this whole thing happened?
Click to expand...
Click to collapse
Yes it probably is
Sent from my HTC Glaciee using XDA Premium App
Jay10826 said:
Well previous to using visionary...i was trying another method to root using the terminal, but it wasn't working, so then i found visionary and used that. I never interacted with the phone using adb, if it matters. If i never really had s=off, could this be why this whole thing happened?
Click to expand...
Click to collapse
Not really, if you were able to run a custom ROM with no problems before then you were rooted properly. Somwhere after you must have gone wrong, not sure where
blah
Hey guys, I know this is the 1000th time you've seen this thread. However, I might be a little different.
I've read all the red blinking threads before posting this one.
ROM: CM10 Stable Snapshot
Kernel: Franco r53
Okay, yesterday as I was downloading and I opened a game, my phone screen just turned off completely. I'm assuming it was due to overheating as the phone was getting pretty hot.
So I assumed it died, no big deal. I tried to boot up using power button, no luck.
Then I panicked and started searching XDA for all these red blinking LED of doom threads.
I managed to get the phone to boot up to the Google screen by having it on a wall charger + hold the power button for 10 seconds. But then it just shuts down. I managed to make it stick with bootloader, but only on the wall charger, which isn't much help. On a USB connection with my computer, I'm not able to even open boot loader as it would just open and turn off the phone within a few seconds.
Threw it on the charger over night, no luck.
This morning, nothing has changed.
So what's weird about my situation is, I can get it into fast boot, but only when it's on a wall charger, nothing else. And getting it to Google logo for a few seconds.
Edit: I can't RMA, because when it boots to Google logo, it says bootloader is unlocked (the little icon). And I also bought the phone off Swappa, so it's not attached to my account (is it even possible to claim warranty?)
Interesting this sounds like a hardware problem all right. Simply because you said it works on the mains charger which has an output of 1.2a were as the USB to PC chargers phone at rate of 400ma. I would try getting a replacement if you can. Also are you able to boot into recovery through boot loader if so you could try wiping everything or restoring from back up.
Okay, something weird. I tried a different method of getting into fastboot, and it worked (connected to PC).
Hold volume - (DOWN) by itself WHILE plugging in the USB cable. And now I'm in fastboot. Now I'm just trying to find a way to erase cache via toolkit x)
Edit: Weird, toolkit picks up the ADB device but manual adb doesn't using adb devices command.
I've read another user who fixed this by removing the back, then disconnecting and reconnecting the battery connector. Sorry I can't find the post but I'm sure it was in one of the I bricked my phone threads.
Yeah, I saw that, too. But I don't have the equipments for it, unfortunately
ADB won't recognize my nexus 4.
Toolkit will (so I know that toolkit is installed properly). I tried opening a command prompt through toolkit and I couldn't run anything.
Any suggestions?
draikz said:
ADB won't recognize my nexus 4.
Toolkit will (so I know that toolkit is installed properly). I tried opening a command prompt through toolkit and I couldn't run anything.
Any suggestions?
Click to expand...
Click to collapse
Adb won't work from bootloader, you should have fastboot access though
I'm in fastboot now.
I cannot get into recovery =[ When I select recovery, it would just turn off the phone and the blinking lights begins again.
Try charging overnight with other charger, not stock
Sent from my Nexus 4 using xda premium
Just tried with a nonstock charger. It blinked red. Then the battery charging screen popped up (first time ever). And now it's dead blinking red again.
Hopefully I'll see results overnight.
draikz said:
Just tried with a nonstock charger. It blinked red. Then the battery charging screen popped up (first time ever). And now it's dead blinking red again.
Hopefully I'll see results overnight.
Click to expand...
Click to collapse
That's a good sign! Sounds like it was in some serious deep hibernation! The fact that the battery icon popped up shows u didn't brick it or anything, its just really really dead! However when I had my problem, I had just a red light on all the time, it never blinked
Sent from my Google Nexus 4
Mine is constantly blinking. :'(
And it's probably not dead because I did manage to get it into fastboot. And I got adb to pick up using fast boot.
Every after reflashing recovery, I can't get into anything other than fastboot. When I try to select "Recovery" from the fastboot menu, it just turns off and continues to blink ;[
if you can get it into fastboot while plugged in your pc, scroll down in fastboot to the "power off" option. leave it there to charge up for a bit. you can check if its charging by using adb
Code:
adb shell cat /sys/class/power_supply/battery/capacity
hopefully it comes back to life after you charge it a bit. After it charges I would flash stock images just to be safe.
rayford85 said:
if you can get it into fastboot while plugged in your pc, scroll down in fastboot to the "power off" option. leave it there to charge up for a bit. you can check if its charging by using adb
Code:
adb shell cat /sys/class/power_supply/battery/capacity
hopefully it comes back to life after you charge it a bit. After it charges I would flash stock images just to be safe.
Click to expand...
Click to collapse
Okay, trying that now. It's been on the charger all night.
How does one ADB with the phone "powered off"?
So if the phone died because of heat, didn't it throttle properly? How is this possible?
Why don't you reflash stock images through fast boot? I don't understand why the need to be in recovery?
Sent from my Nexus 4 using Tapatalk 2
Lownita said:
So if the phone died because of heat, didn't it throttle properly? How is this possible?
Click to expand...
Click to collapse
I'm not really sure. I'm just assuming that it died from heat.
joshnichols189 said:
Why don't you reflash stock images through fast boot? I don't understand why the need to be in recovery?
Sent from my Nexus 4 using Tapatalk 2
Click to expand...
Click to collapse
I thought I had to factory reset it first inorder to flash factory image? (Coming from CM and Franco) At least that's how I always done it or it'd get stuck in a boot loop on my old phone.
But it is my last resort as well, because I have some precious data on this phone x)
Oh and Google pulled factory images, do you knows know where I can get a copy of one?
draikz said:
I'm not really sure. I'm just assuming that it died from heat.
I thought I had to factory reset it first inorder to flash factory image? (Coming from CM and Franco) At least that's how I always done it or it'd get stuck in a boot loop on my old phone.
But it is my last resort as well, because I have some precious data on this phone x)
Oh and Google pulled factory images, do you knows know where I can get a copy of one?
Click to expand...
Click to collapse
Mskip tool kit has images. There might be a thread in general section with them
Sent from my Nexus 4 using xda premium
rayford85 said:
Mskip tool kit has images. There might be a thread in general section with them
Sent from my Nexus 4 using xda premium
Click to expand...
Click to collapse
I've not flashed stock before for this phone. And I'm afraid it might be different.
So question noob question.... Do I flash the booterloader and radios too? I've read that it's pretty dangerous to flash those.
I'm following this guide: http://forum.xda-developers.com/showthread.php?t=2010312
Any instructions I should do differently?
EDIT: I just flashed stock, nothing happened. Still could only get to fastboot. I am now losing hope.
draikz said:
I've not flashed stock before for this phone. And I'm afraid it might be different.
So question noob question.... Do I flash the booterloader and radios too? I've read that it's pretty dangerous to flash those.
I'm following this guide: http://forum.xda-developers.com/showthread.php?t=2010312
Any instructions I should do differently?
EDIT: I just flashed stock, nothing happened. Still could only get to fastboot. I am now losing hope.
Click to expand...
Click to collapse
IF ur going to rma it don't forget to lock the bootloader :angel:
I flashed PA, GAPPS and then DER kernel; wiped cache and dalvik and rebooted. It booted fine and I restored all my settings. I ran a benchmark and in the middle of it, it cut off and wouldn't turn back on. I plugged it in to the stock charger and I got the charging indicator. Then after playing with the volume and power buttons I got it into download mode. I then moved to the computer to use the toolkit and reflash the stock rom and when I plugged it into the computer the charging indicator would not come on, went back to the stock charger and now the charging indicator wont come on. Now it won't do anything, no download mode, no bootloader, nothing.
Any suggestions?
I found one other thread where someone had the same problem and he ended up just RMA'ing.
TYIA
Leave it charging undisturbed for the night, try again tomorrow. It'll boot up again most likely.
Careful with the benchmarking. Which I'm sure you don't need advise for anymore I bet..
Let it sit over night on the charger, still nothing.
Sent from my Nexus 7 using Tapatalk 2
any solution please? i have same problem. only download mode and nothing
PeITeeR said:
any solution please? i have same problem. only download mode and nothing
Click to expand...
Click to collapse
When you plug in the phone do you get the red notification light? Have you tried letting the phone charge for several hours while off or opening the phone and disconnecting/reconnecting the battery?
Sent from my Nexus 4 using xda premium
You need to get out of download mode. Honestly I mash force rebooting the N4 and plug it in and out of the charge until something works, and every time without fail it works lol
Sent from my Nexusâ´
Try This...
PeITeeR said:
any solution please? i have same problem. only download mode and nothing
Click to expand...
Click to collapse
When in download mode press the down and up volume rocker and power button. Try this for some time and it must reboot into bootloader(android with open chest).
(try it when connected to computer too)
If you get it to bootloader you can restore it!!
1. Flash factory image . all info here detailed :::http://forum.xda-developers.com/showthread.php?t=2010312
2. If u cant do it yourself download mskip's toolkit and install drivers. Select option to restore to factory image and it must get you back to stock rom unrooted with only bootloader unlocked.
mskip's toolkit:::http://forum.xda-developers.com/showthread.php?t=1995688
Recovered mine..
ALL THE BEST..:good::good::good::good::good:
So, here's my situation, my phone suddenly turned off last night while installing a game, when i tried to power it up, it "blinking" on the boot logo, it keeps turned on and off, so i reckon its battery has run out, so i charge it, then it works, it can boot to system, after it shows around 80% i unplugged the charger but the phone then suddenly turned off and again, blinking on the boot logo.. so i charge it again just to see it boot to system and shows 80% battery.. i tried to charge it to 100%, but at 100%, the phone suddenly died, again..
at first i thought it might be a battery problem, or power circuit thingy, but here's the catch, it can hold for 30 mins + on bootloader mode..
can someone tell me what is wrong with my phone?
EDIT: flashed stock ROM and Recovery, still no use
EDIT2: Did the QPST as suggested as Rwepradeep, still blinking on lenovo logo
EDIT3: Solved! Battery was the actual problem
chlova said:
So, here's my situation, my phone suddenly turned off last night while installing a game, when i tried to power it up, it "blinking" on the boot logo, it keeps turned on and off, so i reckon its battery has run out, so i charge it, then it works, it can boot to system, after it shows around 80% i unplugged the charger but the phone then suddenly turned off and again, blinking on the boot logo.. so i charge it again just to see it boot to system and shows 80% battery.. i tried to charge it to 100%, but at 100%, the phone suddenly died, again..
at first i thought it might be a battery problem, or power circuit thingy, but here's the catch, it can hold for 30 mins + on bootloader mode..
can someone tell me what is wrong with my phone?
Click to expand...
Click to collapse
Flash Stock ROM or any Other ROM and report back
Rub My Donger :'v said:
Flash Stock ROM or any Other ROM and report back
Click to expand...
Click to collapse
downloading the stock ROM atm, will report once it's done
Rub My Donger :'v said:
Flash Stock ROM or any Other ROM and report back
Click to expand...
Click to collapse
flashed Stock ROM, still happening
chlova said:
flashed Stock ROM, still happening
Click to expand...
Click to collapse
in what way u are flashing the stock rom??
try flashing with QPST if u had pc..
then ur phone will start like a factory product..
if u have pc search in YouTube for qpst method..
that method can solve
Rwepradeep said:
in what way u are flashing the stock rom??
try flashing with QPST if u had pc..
then ur phone will start like a factory product..
if u have pc search in YouTube for qpst method..
that method can solve
Click to expand...
Click to collapse
okay so i did the qpst thing, it can hold on at download mode until it finished, then after that the phone reboots, and it happened again...
i don't get this phone, it works well on bootloader and download mode, but not so long at recovery.. not to mention i can't even boot into system (can't even past the boot logo lol)
Okay so, i took it to Lenovo Service Center, they told me something wrong with the battery, apparently it hold up on bootloader because the bootloader mode didn't took so much power, so even a broken battery should hold up a little.. Changed the battery, now it works well, thanks for all the help..