Please help - My Excalibur won't boot up. - HTC Excalibur

Dash Bricked Need Help!!!
I tried using a the google mail java app on my tmobile dash. It froze up on me, and when i turned it back on it just stays at the "tmobile" splash screen. I have tried using the soft key and power button reset but it doesnt work. What's weird is that it wont power down unless I take the battery out. It powers on, shows the tmobile splash screen, then freezes. Is there any other way to reset it or is it totally bricked? I bought it new off craiglslist so tmobile wont replace it for me cause I'm using it unlocked on cingular.

The power key reset should work. Could you be doing it wrong?

I was facing the same problem but after doing hard reset (Power Off, Press 2 soft key, Press Power On Key for 2 seconds then release soft key) worked fine. Seems timing is very important, try and try.

Help, i think i bricked my phone!
I was installing the WM6 Update released on this website, everything was going fine when i saw that my lil' cousin' disconnected my phone while i moved away from the PC (he pulled the phone altogether).
Now my phone is stuck in the bootloader mode screen (tricolor, blue green/red i think). It detects USB (it says USB on the bottom of the screen whenever i connect it). Is there a fix for it for the DASH? I read the wiki about a fix for a similar problem for the Hermes, but that didnt work for mine.
Can anybody help me please?!
Mine's a T-Mobile Dash with the stock rom from T-Mobile.

remove and reinsert the battery

if that does not work paperweight thats how i ruined my cingular 2125

Oh god, all this brickage makes me too scared to update. Can anyone direct me to where I can find how to backup my current setup so that I could reload it if something went wrong or I didnt like the Beta WM6?

MrLuna said:
I was installing the WM6 Update released on this website, everything was going fine when i saw that my lil' cousin' disconnected my phone while i moved away from the PC (he pulled the phone altogether).
Now my phone is stuck in the bootloader mode screen (tricolor, blue green/red i think). It detects USB (it says USB on the bottom of the screen whenever i connect it). Is there a fix for it for the DASH? I read the wiki about a fix for a similar problem for the Hermes, but that didnt work for mine.
Can anybody help me please?!
Mine's a T-Mobile Dash with the stock rom from T-Mobile.
Click to expand...
Click to collapse
Just try the flash again and it should start working. I had my computer bluescreen while I was flashing an SDA and got to the tricolor screen. It flashed fine after trying again. If its not detecting right. Pop out the battery on the phone and restart your computer and attempt the flash again. Shouldn't be a problem. Definitely scary though. I don't think you can brick these unless you mess up the bootloader perhaps...

ANyone know How do I manually put my Dash in Bootloader mode?

deemota said:
ANyone know How do I manually put my Dash in Bootloader mode?
Click to expand...
Click to collapse
power off, hold the camera key beside Space Tab for about 3 sec, and then press power key while still pressing the cam key.

You are a GOD. Thanks.

you have no idea why it gives you warnings not to run any programs or disconnect while the ruu is updating you think they just give you warning messages because the htc techs have nothing better to do????????

Blackforge said:
Just try the flash again and it should start working. I had my computer bluescreen while I was flashing an SDA and got to the tricolor screen. It flashed fine after trying again. If its not detecting right. Pop out the battery on the phone and restart your computer and attempt the flash again. Shouldn't be a problem. Definitely scary though. I don't think you can brick these unless you mess up the bootloader perhaps...
Click to expand...
Click to collapse
Well, tried that, but the computer doesnt detect the phone, meaning it wont connect to ActiveSync. Since it won't connect to activesync the program wont install it on the phone since it can't find it.
Good thing i have insurance. Bad thing i'm trying again as soon as i get the replacement
Are there any alternatives though? Maybe i can fix it before i send this one back.

restart your computer again..

This is from HTC Q&A
Q: I use RUU to update and failed, and my device always boots in three-color mode and cannot enter CE OS anymore, what should I do now?
A: If the update process has failed, you will see that your device will always boot in three-color mode. It's normal and can be recovered. Please follow the instructions below to reset your device and to establish a connection with the computer.
1. Disconnect your Mobile Device from the USB cradle/cable.
2. Reset your Mobile Device.
3. Reconnect your Mobile Device to the USB cradle/cable.
4. Check that the communication cradle/cable is connected properly.
5. Return to the ROM Update Utility.
Note: You should ignore the ActiveSync connection.

WM6: Endless Bootup Loop
A few days before the official TMobile WM6 update came out I download the widely posted leaked version. The Dash started acting up during bootup one day, so I reflashed with the TMobile WM6. Now the same thing just started, and the device can't be used.
When powered on it does the quick vibrate, TMobile screen, Windows Mobile Screen, TMobile screen again, with power up 'jingle', then it just shuts off and starts the bootup sequence again. Endlessly.
Have tried removing the battery, etc. Has anyone else run into this? Any ideas of a keypress combo or something I can press during bootup that might jump-start it??? Thanks!

Take out the microSD card and the unit should boot properly. Mine was fixed with a new SIM card, but a new device may also be needed.

Wound up doing a hard reset. I had tried taking out the microSD card, then it would just hang on the TMobile screen. I also tried rebooting without the SIM card in, then it would do the loop thing. I'm thinking it must be related to software loading during the boot, and the only program I have on the microSD card that loads during bootup is FizzWeather.
rabilancia said:
Take out the microSD card and the unit should boot properly. Mine was fixed with a new SIM card, but a new device may also be needed.
Click to expand...
Click to collapse

I think this may at times be related to an auto-install file being present.
If you hold down the "end" key during boot-up it seems to prevent the cycling.

Thanks, will keep that in mind if it happens again. By 'end' key, do you mean the red phone icon key that you hang up on a call with?
robertgbl said:
I think this may at times be related to an auto-install file being present.
If you hold down the "end" key during boot-up it seems to prevent the cycling.
Click to expand...
Click to collapse

Related

From download mode to dead ?

Hi,
yesterday i got my sgs and first i wanted to update it to JM5.
Because 3 of my friends have the same phone i know what to do.
First i tried to get into download mode but it doesn´t work.
I found here in the forum (thread 749470) "Australia Optus Galaxy S no download mode!" that i´m not the only one with this problem.
Someone told me to use "adb reboot download" to enter download mode - and this worked fine. The working android appeared on the screen.
Odin now found the phone and i tried to flash but it always ended with "file analysis....". So I found help in this forum - restart pc, start odin as admin, use another firmware, try other usb port - nothing happened - last thing: remove the battery for 30sec and try again.
NOW: SGS alway shows the same pic: a phone + ! + PC - but PC can´t find phone, phone can´t be switched off - nothing!
What can I do now except taking the phone back to my dealer?
I appended a pic from my display.
Thanks for your help!
HolyFreak
if you can not get into download mode, then there is no way to fix it
you'll have to send it back to the store, to have it repaired
hmm, you can press at least the power button for 7-10 seconds, then the phone reboots, mybe you are able to go into download or recovery mode, with those button combinations.
but isn't that icon his screen shows, meant to connect the phone to pc and start kies so kies can fix it? (at least i read sth like that on forum) but if this all doesn'T work i don't know
You can always switch the phone off, pull the battery out. ( Avoid doing so when flashing though. )
http://forum.xda-developers.com/showthread.php?t=725858
saldawop said:
http://forum.xda-developers.com/showthread.php?t=725858
Click to expand...
Click to collapse
This guide is really not all that useful.
Take out the battery, and reboot by first pressing voldown+home and then power and wait until you see the yellow download screen.
I'd recommend not doing anything with a phone that you can't get into download mode from a cold start with. Too much can go wrong. Leave it on stock.
I remember seeing that screen when I thought I had bricked my phone, I think I managed to pull back by removing the battery and trying again.
waspbr said:
I remember seeing that screen when I thought I had bricked my phone, I think I managed to pull back by removing the battery and trying again.
Click to expand...
Click to collapse
that is only because your 3 button combination was working
in his case, his 3 buttons are not working
there is a batch of samsung phones that came from factory with the 3 button combo disabled
Having the same issue. Think the stores will replace it under warranty like this?

ATT TILT 2 owned since released stuck in Boot Screen

I have a Stock TILT 2 (TP 2) never flashed running basic programs Mobile Shell never had any issues with it, haven't installed new software in a few weeks , but I soft resetted it this morning and it keeps getting stuck in the boot screen. when first turned on it will run through boot screen then load screen for a millisecond then back to boot screen and never advances again , I've tried battery out sim card out Sd card out everything, even tried hard reset , but wont allow me to hard reset with front buttons and power, is there another way to hard reset , is it possible my phone just bricked for no reason ? thanks for any help ?
have you tried to do a hard reset via the pc? the original rom is on the htc website so you can try useing the exe file there. there is also an updated rom you can try to flash there. hope that helps
You might try sending it to the bootloader screen and reflashing. I don't know if it will work, but I thought it might be worth the effort.
I did notice that HTC removed the original shipped ROM for the Tilt2. I'm sure it is floating around here somewhere. If not, I have it and can send it to you when I get home.
Thanks I have original rom and just released wont work.
dod you see anythign on teh screen? if you do, then hard reset may fix it.
Power off your phone (or take teh battery out). Then press and hold teh call and hang up button while press teh power button. it will enter the hard reset mode. (remember hard reset will erase all the info on the phone and rever tot the stock setting).
jcterry said:
I did notice that HTC removed the original shipped ROM for the Tilt2.
Click to expand...
Click to collapse
wow, thank god i dl'd it when i dl'd the updated rom... and they still have the image of the old rom right beside it... lol
as for op, you can try to enter the bootloader with the following steps
Remove the back cover from the phone.
Hold the Volume Down button.
Use the stylus to press the reset hole.
Or if the device was powered off, press the power button whilst holding down the Volume Down button.
and try to flash from there
hope that helps again

[Q] Help please! 3x vibrate and amber flashing light after removing battery! (brick?)

Hey guys, I'm normally silent in these forums 'cause I've never had a brick, just by reading correctly. This problem I'm having isn't a flashing brick! What happened is the following:
I know that the DHD in combi with my BT car radio is somewhat difficult (because of bad HTC coding). It seems that when I have my facebook friends in my contacts that the DHD starts slowing down and eventually hang when connected to the radio, because my radio tries to get every contact including it's info. Normally I do not sync my FB contacts with my DHD however I must have mistakingly done this.
Today I connected to my car radio and after getting out of the car my DHD showed that it was still connected (a sign that my DHD had the hang problem again). I turned of BT (took a hell of a time) and contiued on. When I came back I tried connecting the DHD again, however when I pushed the BT checkmark in settings it showed BT on, but no BT connection came up. So I went into BT settings only to find that BT wasn't turned on, then in the BT settings I checked turn BT on.
At that moment my DHD hang instantly, no inputs were registered at all. I waited a few minutes but nothing changed (I could still see the screen frozen at turning on BT). So I took out the battery and reinserted it, but when a pushed the power, the phone vibrated thrice and then did not boot, but only showed a flashing amber led.
I have rooted, S-offed and did the whole shebang to flash my DHD once. This was a long time ago and I haven't had any problems, all was OK. So at first I tried to search the forums, what might have happened. No post seems to be the same as my problem, because everyone is having these problems after an incorrect flash (my flash was correct, cause I've been using the ROM for more than 4 months!). Still I tried the solutions given in these posts (enter fastboot and flash again).
But it seems my DHD won't go into fastboot. When I hold VOLdown&power my DHD vibrates 5 times and shows a steady green led. So I thought maybe flashing a new ROM resolves the problem. If I cycle the battery and then connect is to my computer, my DHD goes into Clockwork recovery. From there I flased a new ROM to my DHD (update.zip method), but to no avail. I've factoryresetted, cleared al data, wiped battery stats, all to no avail...
As of this moment I'm at the end of my knowledge, I've done everything I know could have helped, but nothing did. Therefore I'm asking you, the Oracle of XDA (users), please does anyone have any clue what happened to my DHD and if so, how do I resolve the problem!
Thanks in advance for every little motivation/obligation you show be giving me your insights!
Info:
ROM: Android Revolution HD 2.0.9
CWM Recovery: 2.5.1.3
I've allready wiped battery stats as per this topic!
Additional thoughts: Might a hardware fault be the reason? Because it happened after some problems with BT, and also because I'm still able to correctly flash new ROMS with CWM though the problem remains?
Allright, so nobody know an answer I'm guessing... I've started the replacement process with my insurance company. However I'd still would like it if someone would know what the heck I did wrong...
Have you tried flashing a new radio, as that is what controls the hardware?
All a new ROM will do is update the RIL, not the radio.
http://forum.xda-developers.com/showthread.php?t=896597
Sent from my Desire HD using Tapatalk
It does more than likely seem like a hardware fault so it cant really be solved with software changes. Although I still would have tried to flash an RUU which updates basically everything on the phone to bare stock.
Use an RUU via your pc (v2.36 or lower so you can root it again) to restore to an out of the box state.
Allright guys, thanks for your ideas! I'm however experiencing problems trying your idea's. fFashing a radio or flashing a stock rom are not possible, because I need a connection with my computer. This connection is not possible, if I start the phone normally (or with vol down) I get the amber flashing light or the green steady light. Both do not connect to my pc, I get some device "Qualcomm CDMA Technologies MSN" for which windows can't find any drivers. When I let the DHD go into QWM recovery, the RUU won't find the DHD.
So I've tried extracting the RUU rom en putting this on the SDCARD of the DHD, but when I try to install it via CWM Recovery it says that it's an invalid file...
I actually bricked mine on purpose, and the thing that happened when it got bricked was that no lights and no life at all we're visible on the phone...
Atleast you get shakes and lights, thats a good sign!
Sadly i don't know what has to be done to restore it, but maybe Jkoljo does, PM him about your problem, if you get an assistance and some solving, write back here for your solution for others to use in the future!
They hang out in the Android Revolution HD IRC Channel, thats where i would go tbh.. Live support ftw!
Edit: While reading your above statement, it seems your drivers may be faulty in windows, redownload HTC Sync from htc.com, install, reboot, and try again.
The "Qualcomm CDMA ..." notification on the PC is a sign for the Qualcomm service mode. Also the 3 vibrates and the orange light is an indicator for that. You can enter this mode by pressing vol+ and power your device.
Stupid question, but is it possible that your vol+ button is stuck or something like that?
And you said you're able to enter CWM? how? I'm asking because you said you can't enter the bootloader.
I'll do some research when i get home today.
Meanwhile Try if ADB/Fastboot sees your phone
Edit: just checked my theory of the broken vol+ button: i held down my vol + button, took my battery out, reinserted it and powered up my phone. Result: 3 vibrates and a flashing orange light.
Then i did the same, but held down vol - ( vol+ still pressed). Result: your second phenomenon: a few vibrates and the green light stays on.
So I think this proves my theory because this is exactly what you described
I suggest you to play a bit with the vol+ button. Maybe the button will work again then
Sent from my Desire HD using Tapatalk
Well, I'm gonna fire up IRC then and try get some help. It's indeed not bricked as far as I'm guessing cause I do indeed have lights and I'm able to boot into CWM!
Flussen said:
The "Qualcomm CDMA ..." notification on the PC is a sign for the Qualcomm service mode. Also the 3 vibrates and the orange light is an indicator for that. You can enter this mode by pressing vol+ and power your device.
Stupid question, but is it possible that your vol+ button is stuck or something like that?
And you said you're able to enter CWM? how? I'm asking because you said you can't enter the bootloader.
I'll do some research when i get home today.
Meanwhile Try if ADB/Fastboot sees your phone
Sent from my Desire HD using Tapatalk
Click to expand...
Click to collapse
Right I'm guessing this is my problem! Just two days prior to resetting I started having problems with my VOL+ button (wouldn't work, only VOL- worked). So I'm guessing my hardware VOL+ button is broken and stuck to pressed...?
To answer your question about CWM: When I take out the battery so the phone is powered down, then reinsert the battery, connect the phone to the adapter or my computer (without pressing the power button), the phone boots into CWM after about 1 minute!
So after consolidating all the answers I'm guessing this is my problem: Hardware VOL+ is constantly pressed, therefore the phone boots consequently into Qualcomm service mode. Everything seems to be OK (flashing able to CWM), though just this little VOL+ problem puts my phone into an unusable brick...
The problem is that I'm not able to repair this myself (when I would try this, I'm guessing I'll break the seals therefore my insurance won't pay)... Anyone an idea how to circumvent the VOL+ button problem, without opening up my phone?
bdacier said:
Well, I'm gonna fire up IRC then and try get some help. It's indeed not bricked as far as I'm guessing cause I do indeed have lights and I'm able to boot into CWM!
Right I'm guessing this is my problem! Just two days prior to resetting I started having problems with my VOL+ button (wouldn't work, only VOL- worked). So I'm guessing my hardware VOL+ button is broken and stuck to pressed...?
To answer your question about CWM: When I take out the battery so the phone is powered down, then reinsert the battery, connect the phone to the adapter or my computer (without pressing the power button), the phone boots into CWM after about 1 minute!
So after consolidating all the answers I'm guessing this is my problem: Hardware VOL+ is constantly pressed, therefore the phone boots consequently into Qualcomm service mode. Everything seems to be OK (flashing able to CWM), though just this little VOL+ problem puts my phone into an unusable brick...
The problem is that I'm not able to repair this myself (when I would try this, I'm guessing I'll break the seals therefore my insurance won't pay)... Anyone an idea how to circumvent the VOL+ button problem, without opening up my phone?
Click to expand...
Click to collapse
Do you have needles at home? The ones you use when you repair cloth.. Try using one very carefully behind the volume +, you could also take a bit of A4 Paper, cut out some of it and make it fit between the gap of the Volume button, and try getting dirt out of there.
Allright, I've tried cleaning the VOL+ key but it still won't work. As a matter of fact I can feel a little "click" when pressing the VOL+ key, so I'm guessing the mechanical part of the key is working correctly. However when in CWM I can only use the VOL- key to switch thru the options, VOL+ is not registered by the phone. Therefore my assumption is that the there's a problem on the PCB with the VOL+ key, ergo a hardware fault... Insurance has been called and I'm up for a switch, now let's hope the insurance doesn't figure out I've rooted and installed another ROM than stock!
At least I wan't to thank all of you who've tried to help me! My ego has been saved, knowing it's indeed a hardware fault .
Cant you use adb within cwm to adb reboot bootloader?
Sent from my Desire HD using Tapatalk
bdacier said:
Allright, I've tried cleaning the VOL+ key but it still won't work. As a matter of fact I can feel a little "click" when pressing the VOL+ key, so I'm guessing the mechanical part of the key is working correctly. However when in CWM I can only use the VOL- key to switch thru the options, VOL+ is not registered by the phone. Therefore my assumption is that the there's a problem on the PCB with the VOL+ key, ergo a hardware fault... Insurance has been called and I'm up for a switch, now let's hope the insurance doesn't figure out I've rooted and installed another ROM than stock!
At least I wan't to thank all of you who've tried to help me! My ego has been saved, knowing it's indeed a hardware fault .
Click to expand...
Click to collapse
I've got the exact same problem! I don't have insurance on it though. And, im a day late for warranty.
What am i supposed to do? Any suggestions? Will htc deny my request to fix it coz it had a custom firmware?
Any help of any sort is appreciated.
I had exactly the same problem, and I'm sorry to say that I had to have it repaired. My button would also "click", but not register.
Maybe if you are buy a new power button from eBay?
Realising this is an old thread, but still:
I was just experiencing the same problem after I did a reboot to let one of my friends borrow my DHD to turn off the PIN code check on his SIM.
It started with the blinking lights (black screen), then I pulled the battery and found that my DHD was only accessible through ADB in recovery mode.
Did a couple of "ADB reboot" without any success, then tried using "ADB reboot recovery", which seemed to work (still black screen though), and then I did a "ADB reboot".
Back to normal!
hi , i had this issue too , its bcz of the moisture ur cell phone has absorb and as HTC desire HD very sensitive with its volume rocker area , the first thing that will be affected with moisture is ur volumer rocker circuit , try making it dry with a hair dryer blower or place ur phone in a rice sack for a day .
i am sure it will work .

[Q] T-Mobile Note 3 stuck in a auto-restarting, recovery bootloop

Hello, I am new to these forums. I mostly registered for this one specific problem.
I'm pretty sure the phone isn't hardbricked, but I tried rooting my T-Mobile Galaxy Note 3 (4G LTE version) with Klingo. After that, it said the root was successful and the phone immediately restarted itself. However, it was then stuck in a bootloop and it just kept restarting itself. The phone turns on, and then the "Samsung Galaxy Note 3" logo appears with "RECOVERY....." in blue in the top left corner, and directly under that it says "Set Warranty Bit: recovery" in yellow. Then after about 3-4 seconds it shuts off, then about 2 seconds later it restarts automatically and just keeps looping like that.
T-Mobile said they would replace the phone, and they'll be sending me a new one as soon as the old one reaches the return center. Obviously I didn't tell them what I actually tried to do. In case they're able to find out what I tried to do and end up sending my old one back, I just wanted to ask this question preemptively so I might have an idea of what to do.
I HAVE TRIED BOOTING INTO RECOVERY MODE AND DOWNLOAD MODE. No button combinations cause anything to happen. The only thing that stopped the auto-restarting and looping was taking the battery out. Upon putting the battery back in, it will stay off until I manually turn the phone on again, where it will then continue to auto-restart and loop itself.
I do not have the phone right now because I sent it to a return center after spending a few hours searching online for answers and talking to T-Mobile on the phone. But if any of you have any ideas it would certainly be a great help if the worst case scenario ends up happening. Thanks for any potential solutions!
JasePK said:
Hello, I am new to these forums. I mostly registered for this one specific problem.
I'm pretty sure the phone isn't hardbricked, but I tried rooting my T-Mobile Galaxy Note 3 (4G LTE version) with Klingo. After that, it said the root was successful and the phone immediately restarted itself. However, it was then stuck in a bootloop and it just kept restarting itself. The phone turns on, and then the "Samsung Galaxy Note 3" logo appears with "RECOVERY....." in blue in the top left corner, and directly under that it says "Set Warranty Bit: recovery" in yellow. Then after about 3-4 seconds it shuts off, then about 2 seconds later it restarts automatically and just keeps looping like that.
T-Mobile said they would replace the phone, and they'll be sending me a new one as soon as the old one reaches the return center. Obviously I didn't tell them what I actually tried to do. In case they're able to find out what I tried to do and end up sending my old one back, I just wanted to ask this question preemptively so I might have an idea of what to do.
I HAVE TRIED BOOTING INTO RECOVERY MODE AND DOWNLOAD MODE. No button combinations cause anything to happen. The only thing that stopped the auto-restarting and looping was taking the battery out. Upon putting the battery back in, it will stay off until I manually turn the phone on again, where it will then continue to auto-restart and loop itself.
I do not have the phone right now because I sent it to a return center after spending a few hours searching online for answers and talking to T-Mobile on the phone. But if any of you have any ideas it would certainly be a great help if the worst case scenario ends up happening. Thanks for any potential solutions!
Click to expand...
Click to collapse
I have no idea what the issue is, but it seems you might not have a recovery installed on the phone. Try this:
Hold power + volume to go into bootloader (I know you said you tried various combinations, but make sure you're doing it correctly.).
Go into fastboot
flash a new recovery image from (TWRP or CWM) (how to: https://sites.google.com/site/tomsgt123//adb-fastboot)
reboot and go into recovery, then use adb sideload to flash a new ROM.
Source: http://www.reddit.com/r/htcone/comments/1rkvy0/help_stuck_in_bootloop_without_access_to_recovery/
I have no idea whether this will work, but it's worth a try. Please don't blame me if your phone gets even more messed up than it already is.
Techngro said:
I have no idea what the issue is, but it seems you might not have a recovery installed on the phone. Try this:
Hold power + volume to go into bootloader (I know you said you tried various combinations, but make sure you're doing it correctly.).
Go into fastboot
flash a new recovery image from -snip-
reboot and go into recovery, then use adb sideload to flash a new ROM.
Source: -snip-
I have no idea whether this will work, but it's worth a try. Please don't blame me if your phone gets even more messed up than it already is.
Click to expand...
Click to collapse
Thank you so much. I will definitely try this. I was also getting replies elsewhere that if I can see the logo, I should be able to get into download mode where I could then flash the stock ROM. Honestly, it does seem like I somehow may not have a recovery installed.
If they send me my old phone back I will definitely give this a try. Thanks a bunch! And don't worry, I won't hold you accountable haha.
JasePK said:
Thank you so much. I will definitely try this. I was also getting replies elsewhere that if I can see the logo, I should be able to get into download mode where I could then flash the stock ROM. Honestly, it does seem like I somehow may not have a recovery installed.
If they send me my old phone back I will definitely give this a try. Thanks a bunch! And don't worry, I won't hold you accountable haha.
Click to expand...
Click to collapse
If the advice above didn´t work (nothing happened when pressing the usual VOL down - home - power etc; this did not work for me), this is how I managed:
I tried booting around 25 times with the power button released at different times. Did not work.
Tried to insert battery when pressing the 3 buttons. Did not work.
I let the battery run completely empty. Started charging the phone and pressing the 3 buttons. Did not work.
I charged the phone full (with booting the whole time....needed to put it somewhere quiet). After estimating it was full, I pulled out the battery, preparing to send it to mobiletechvideos.com (they saved me before). After a few hours I wanted to see the error message so I could inform them. When I inserted the battery, I got the regular download mode! Nowthen, would I dare to boot it since I am not really sure what to flash to my phone?
I rebooted, and now the phone is back to normal. OTOH, I will not try to flash CWM/TWRP again, so goodbye custom roms (Omega )
cdresor said:
If the advice above didn´t work (nothing happened when pressing the usual VOL down - home - power etc; this did not work for me), this is how I managed:
I tried booting around 25 times with the power button released at different times. Did not work.
Tried to insert battery when pressing the 3 buttons. Did not work.
I let the battery run completely empty. Started charging the phone and pressing the 3 buttons. Did not work.
I charged the phone full (with booting the whole time....needed to put it somewhere quiet). After estimating it was full, I pulled out the battery, preparing to send it to mobiletechvideos.com (they saved me before). After a few hours I wanted to see the error message so I could inform them. When I inserted the battery, I got the regular download mode! Nowthen, would I dare to boot it since I am not really sure what to flash to my phone?
I rebooted, and now the phone is back to normal. OTOH, I will not try to flash CWM/TWRP again, so goodbye custom roms (Omega )
Click to expand...
Click to collapse
So basically your problem was fixed by keeping the battery out for an extended period of time? Did you get the same problem as I did, with the phone trying to boot into recovery constantly and failing due to having no recovery image?
I never kept the battery out for more than 2-3 minutes, so that's another option for me to try if they send my old phone back and the first guy's suggestion doesn't work.
JasePK said:
So basically your problem was fixed by keeping the battery out for an extended period of time? Did you get the same problem as I did, with the phone trying to boot into recovery constantly and failing due to having no recovery image?
I never kept the battery out for more than 2-3 minutes, so that's another option for me to try if they send my old phone back and the first guy's suggestion doesn't work.
Click to expand...
Click to collapse
Yes, I had the exact problem. I tried to have the battery out for 10 minutes, and also ran out of battery during a nightly discharge. Still I could not get it to work. The only way was to leave the battery out for several hours. Beats me, but it worked.
Having bricked a device completely before, I am confident that your phone will be able to get fixed. This isn´t even semi-bricked
Good luck - let me know what happened!
cdresor said:
Yes, I had the exact problem. I tried to have the battery out for 10 minutes, and also ran out of battery during a nightly discharge. Still I could not get it to work. The only way was to leave the battery out for several hours. Beats me, but it worked.
Having bricked a device completely before, I am confident that your phone will be able to get fixed. This isn´t even semi-bricked
Good luck - let me know what happened!
Click to expand...
Click to collapse
Thanks so much to both of you. I feel relieved now no matter what happens. Will post the results when I've reached the end of this ordeal!
JasePK said:
Thanks so much to both of you. I feel relieved now no matter what happens. Will post the results when I've reached the end of this ordeal!
Click to expand...
Click to collapse
I tried to flash latest cwm again and got the same loop. I could narrow it down to 30 min without battery :laugh:
cdresor said:
I tried to flash latest cwm again and got the same loop. I could narrow it down to 30 min without battery :laugh:
Click to expand...
Click to collapse
When that happens and you go back to normal, are you able to access recovery mode afterwards if you want to? Or does trying to cause the same loop? Is it wise to re-flash the stock firmware just to be safe?
JasePK said:
When that happens and you go back to normal, are you able to access recovery mode afterwards if you want to? Or does trying to cause the same loop? Is it wise to re-flash the stock firmware just to be safe?
Click to expand...
Click to collapse
I never dared to try. But since I always used Windows under Mac (Parallells) or the fact that I used Windows 7 or 8, I tried to flash CWM on a native Windows XP PC today and it worked. So now I have a custom ROM working which I never thought would happen :laugh:
Sorry I did not try to access recovery before so you would know
Cheers,
cdresor said:
I never dared to try. But since I always used Windows under Mac (Parallells) or the fact that I used Windows 7 or 8, I tried to flash CWM on a native Windows XP PC today and it worked. So now I have a custom ROM working which I never thought would happen :laugh:
Sorry I did not try to access recovery before so you would know
Cheers,
Click to expand...
Click to collapse
No that's alright, I just wanted to know if it was something I should avoid. :laugh: I'll use Odin to flash the official firmware back on regardless.
I had this happen to me, what had occurred was that the efs was corrupt. Here's the fix:
http://forum.xda-developers.com/showthread.php?t=2507403
Now to implement this fix, you must first be able to get into download mode. To do so:
1. Pull the battery
2. Wait 10-20 secs
3. Reinsert battery WHILE holding power button and (volume down + home???, whatever the key combination is)
5. Phone will boot directly to download mode, no logo
6. Flash twrp via odin
7. Phone will reboot into bootloop again
8. Repeat steps 1-4 except this time use the key combination for recovery
9. You must now use adb and push the file I linked to earlier
10. Then without rebooting you must flash it
11. Reboot and problem solved
Fixed issue with continuous recovery boot
So, this issue was somewhat perplexing, and while the information shared was hopefully valuable to some, it took me about 2 minutes to
fix this and get back into download mode.
Take the battery out of the device, then plug the device into USB (If you're having same issue I was device will not show charging or turn on when plugged in.) Then with the device plugged in to usb and the battery out, hold down the Download mode combination Vulume +, Home and Power, then simultaneously slide in the batter, the phone will boot into download mode and you can get back to stock.
Hope this helped! If it did, leave a thanks.
twill1987 said:
So, this issue was somewhat perplexing, and while the information shared was hopefully valuable to some, it took me about 2 minutes to
fix this and get back into download mode.
Take the battery out of the device, then plug the device into USB (If you're having same issue I was device will not show charging or turn on when plugged in.) Then with the device plugged in to usb and the battery out, hold down the Download mode combination Vulume +, Home and Power, then simultaneously slide in the batter, the phone will boot into download mode and you can get back to stock.
Hope this helped! If it did, leave a thanks.
Click to expand...
Click to collapse
This is exactly what I posted above lol
LOL Sorry. When I flash the TWRP file it just rebooted the phone back into the Hyper Drive Rom I'm using, did it do the same for you?
Thanks to everyone who has provided information and tried to help me! Thankfully, T-Mobile simply sent me a new phone. However, I'm definitely going to keep this topic bookmarked for future reference. This seems to be a rather uncommon problem, considering I had to make a topic to find a solution since all of my searches didn't give me any results.
Thanks again to everyone!
twill1987 said:
So, this issue was somewhat perplexing, and while the information shared was hopefully valuable to some, it took me about 2 minutes to
fix this and get back into download mode.
Take the battery out of the device, then plug the device into USB (If you're having same issue I was device will not show charging or turn on when plugged in.) Then with the device plugged in to usb and the battery out, hold down the Download mode combination Vulume +, Home and Power, then simultaneously slide in the batter, the phone will boot into download mode and you can get back to stock.
Hope this helped! If it did, leave a thanks.
Click to expand...
Click to collapse
U r My neww Mirical worker I messed up a Mobile Odin Flash At work today trying to get the newish NE6
couldnt get it to boot into download after the screw up but read this this morning nd after trying everything else it worked perfect
thank you thank you
I'm having the same problem with my TMobile Note3 after using Kingo after upgrading via Kies to the latest Firmware. The only difference is my phone immediately starts rebooting as soon as I put the battery back in. It doesn't appear that any keys stop this and the USB isn't recognized by my computer in time before the reboot cycle starts.
Is there anything else to try other than sending the phone back for warranty replacement?
tim
Yeah Kingo has given me nothing but trouble, I'd steer clear of that software. I'm assuming you have no access to recovery mode? I have had that issue before on an S3 and was able to finally get it into download mode, but the battery being inserted immediately boots the phone up. So what you have to do is 1. Take battery out and unplug usb cable. 2. Plug USB cable in and Hold download mode buttons with BATTERY OUT (vol+, home and power) 3. insert battery simultaneously while holding buttons down, phone will boot up.. After holding down for about 10 seconds phone will manually reboot, 4. When screen shuts off (potentially vibrates) release download mode buttons, then IMMEDIATELY press and hold download mode buttons again (must perform this step FAST, the key is to do it right before the screen turns on if you can.) 5. The manual boot you've performed should allow you to trigger download mode. I was eventually able to get this to work (about 3 tries. ) I believe your download mode is still intact, you just have to use this method to access it. Remember that because your phone atuo boots with battery inserted download mode will only be available by manual reboot not battery insert.
Give thanks if I assisted you.. Your phone isn't a hard brick so Jtag service should be unnecessary at this juncture.
---------- Post added at 05:09 AM ---------- Previous post was at 05:01 AM ----------
Awesome!! Glad I could be of such assistance
---------- Post added at 05:13 AM ---------- Previous post was at 05:09 AM ----------
R187J said:
U r My neww Mirical worker I messed up a Mobile Odin Flash At work today trying to get the newish NE6
couldnt get it to boot into download after the screw up but read this this morning nd after trying everything else it worked perfect
thank you thank you
Click to expand...
Click to collapse
Awesome man!! Glad I could be of assistance!!
Give thanks/thumbs up!
I read on many posts and comments that everyone is able to boot in download mode. My Note 3 just stuck on recovery boot and I can't get it to boot in download mode. I tried all of the suggestions about pressing three buttons, removing battery etc.
Does anyone know solution for when you can't get into download mode?
Thanks

LG G4 bricked - cannot get into recovery or download mode.

Hello everyone, I hope you can help me. My husband tried to downgrade his LG G4 UK model from Marshmallow to Lollipop, using LGUP. The process failed and the phone is now bricked. I switch it on, and the "LG powered by Android" screen comes on, followed by the other LG screen. The phone just sits like that. I have tried to boot to recovery, and boot to download mode; but can do neither. I have also tried connecting to LGUP, LG Bridge, and the LG Mobile Support Tool. None of these can find the phone, as it needs to be switched on to be located by the programs. When I connect the phone to my laptop, I get the "thump" sound that shows the phone is connected to the computer. That is all I can get though. Is there a way out of this, and back to getting the phone working again? I would be grateful for any advice you can offer me to resolve this issue.
I think it's hard bricked. In that case, you can't recover it.
SirDarknight said:
I think it's hard bricked. In that case, you can't recover it.
Click to expand...
Click to collapse
I have now been able to get the phone into download mode. I was hoping that getting into download mode might help LGUP to see the phone, but I can't find a way of doing that.
We're on the same boat.
Did It - Fixed It!
drumbeater79 said:
We're on the same boat.
Click to expand...
Click to collapse
I took a punt, and the punt worked. I disconnected the phone from the computer, and pulled the battery. Then I re-inserted the battery. Next, I tried to get the phone to boot into download mode, by pressing power and volume down; with the phone disconnected from the computer. The phone then brought up a screen, asking if I wanted to do a factory reset. I chose "yes" and it asked me again (presumably in case I had pressed "yes" in error. The phone then powered down, before powering up, and optimising apps. Then it went to the welcome/sign in screen. All the previous apps are lost, but at least the phone is working now. Hubby is chuffed to bits with his "new" phone.
@SirDarknight @drumbeater79
Glad to hear that!
ursulavasey said:
I took a punt, and the punt worked. I disconnected the phone from the computer, and pulled the battery. Then I re-inserted the battery. Next, I tried to get the phone to boot into download mode, by pressing power and volume down; with the phone disconnected from the computer. The phone then brought up a screen, asking if I wanted to do a factory reset. I chose "yes" and it asked me again (presumably in case I had pressed "yes" in error. The phone then powered down, before powering up, and optimising apps. Then it went to the welcome/sign in screen. All the previous apps are lost, but at least the phone is working now. Hubby is chuffed to bits with his "new" phone.
@SirDarknight @drumbeater79
Click to expand...
Click to collapse
It's a hard reset, not download mode. Glad that it worked for you I already tried it several times but I can't get past the screen saying Android starting apps.

Categories

Resources