i have a htc amaze i unlocked from htcdev, and install recovery, i was trying to get s-off via wire trick and i attempt many times(like 14 )
and then when i try again the phone just die, i have a spare battery`s ( 3) i change batteryes and nothing i pull battery and nothing and even with usb coneccted to computer nothing not even the l.e.d light come on,, its totally dead,, please help me what i can do i search unbricked amaze but no solution :crying::crying::crying:
I was going to say maybe your recovery was shot but if you're swapping new charged batteries and still nothing, possibly a static discharge from the wire trick?
have you tried the RUU exe? to get you back to stock?
pandemoniumsax said:
i have a htc amaze i unlocked from htcdev, and install recovery, i was trying to get s-off via wire trick and i attempt many times(like 14 )
and then when i try again the phone just die, i have a spare battery`s ( 3) i change batteryes and nothing i pull battery and nothing and even with usb coneccted to computer nothing not even the l.e.d light come on,, its totally dead,, please help me what i can do i search unbricked amaze but no solution :crying::crying::crying:
Click to expand...
Click to collapse
With a charged battery hold down the power button and down volume button, see if it boots into bootloader.. if it does, your amaze is far from bricked. I remember the s-off tool getting some sort of a backup file made, some command you can use in the tool that will put it back into the stock boot sequence- I can't find it now, but I know it is there.. try what I suggested above, and look/read all you can on the s-off tool, I definitely remember them having something for that, but I'd like to know you're putting some work into finding the answer rather than having others do it for you..
andy55 said:
I was going to say maybe your recovery was shot but if you're swapping new charged batteries and still nothing, possibly a static discharge from the wire trick?
have you tried the RUU exe? to get you back to stock?
Click to expand...
Click to collapse
thanx for you response,, but yes i did try RUU and no luck,, the phone is completely dead,, no one single light come on :crying:
Silentbtdeadly said:
With a charged battery hold down the power button and down volume button, see if it boots into bootloader.. if it does, your amaze is far from bricked. I remember the s-off tool getting some sort of a backup file made, some command you can use in the tool that will put it back into the stock boot sequence- I can't find it now, but I know it is there.. try what I suggested above, and look/read all you can on the s-off tool, I definitely remember them having something for that, but I'd like to know you're putting some work into finding the answer rather than having others do it for you..
Click to expand...
Click to collapse
thanx so much for reply,, yes i try to boot into bootloader but... nothing i swap batteries fully charged, but it doesn`t do absolutly nothing,, no one single blink on screen or led light, i also put out the battery and conect usb to computer holding power and nothing,plug it to wall charger for around 1 hr then take out battery ,put it back with no luck
Ive never heard of a bricked amaze... but it sounds like you may have one
Sent from my SGH-T999 using xda premium
if it happened during your attempts at the wire trick, then I'll say you shorted something, or hit the wrong terminal, but something hardware related. Still have warranty? Time to play dumb and take it back to the store
SOLVED!!!!
Well thanx you so much for all your reply`s!!! after i did everything in the post and 9 hrs of NO luck,, i decide to open my amaze and with a small flat screwdriver i lift the "INSIDE BATTERY" (a small battery that looks like a clock batt) just a little bit enoguh to sperate it from the board,, leave it like that for around 2 mins and then i put it back in place and yoohhooooooo!!!!!!! it turns on again im able to get into bootloader,,, now to get sim off again,,
P.S:: yes the phone turns completely off with no signals of life when i was doing the wire trick so maybe like andy55 said i touch wrong terminal o something,,, hope this help somebody thanx so much.......:victory::victory::victory:
Thread moved to Q&A section.
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Didn't we go to different schools together?...Coffee Bean!
Sent from my HTC One X, using XDA Premium.
pandemoniumsax said:
Well thanx you so much for all your reply`s!!! after i did everything in the post and 9 hrs of NO luck,, i decide to open my amaze and with a small flat screwdriver i lift the "INSIDE BATTERY" (a small battery that looks like a clock batt) just a little bit enoguh to sperate it from the board,, leave it like that for around 2 mins and then i put it back in place and yoohhooooooo!!!!!!! it turns on again im able to get into bootloader,,, now to get sim off again,,
P.S:: yes the phone turns completely off with no signals of life when i was doing the wire trick so maybe like andy55 said i touch wrong terminal o something,,, hope this help somebody thanx so much.......:victory::victory::victory:
Click to expand...
Click to collapse
The battery you lifted is likely the motherboard battery that keeps the Bootloader's information in memory so removing it is the lowest level reset you can do on a computer/phone. To reset a BIOS password for example this is the way to do it when you don't know the password.
And after that, cool, yet another way to unbrick an Amaze!
Sent from my HTC_Amaze
Related
So I rooted my EVO 3D using the HTC method. Then I installed CWR and SU. Installed Titanium backup and took a couple of backups. Everything was fine. Then I had this bright idea of installing ROM Manager. I run ROM Manager and I see this option for backing up existing ROM. I click on it and it asks me to install a boot loader or something. I install it. Then click backup again. BAM ! Phone reboots and goes blank. Now the red LED is consistently blinking every short while and the phone wont start.
Tried removing the battery and holding power to drain the cap. Then tried holding power. No dice. Tried holding power + Volume - no dice. The phone simply wont boot.
How do I fix it ? Is it bricked for good ? Anyone else have this problem ?
Try unplugging and then turning it on. Shouldn't be bricked either way. Hope this helps.
Try running the HTC method again
Sent from my PG86100 using xda premium
If the suggestions already given do not work try hooking it up to your
PC and seeing if adb works? Them try to boot into fastboot, then fastboot recovery.
If not, try hooking into sync and seeing if you can initiate an Ruu. The Ruu will more than likely not be successful because you are unlocked and would need to lock first, but some communication between your phone and pc is a great sign.
also there is a thread here (I think sticky) that says "think you broke your phone, look here". Check that thread out to see if any suggestions.
Edit: added link
http://forum.xda-developers.com/showthread.php?t=1281729
Sent from my PG86100 using XDA App
To try all of that it needs to power on and the screen needs to show something. It simplywont power on. Red led keeps blinking. Tried charging it, connecting it to my Mac. A DB reboot. A DB reboot recovery. Says device not cnected.
nimkar said:
To try all of that it needs to power on and the screen needs to show something. It simplywont power on. Red led keeps blinking. Tried charging it, connecting it to my Mac. A DB reboot. A DB reboot recovery. Says device not cnected.
Click to expand...
Click to collapse
Well if the red light is blinking I highly doubt it is bricked.
If Adb doesn't work, try running an Ruu through sync. Even if it says there is no device connected to sync, run the Ruu anyhow. I can tell you that I had an issue Once where I hooked it up to sync and it said there was no device connected. I tried to run Ruu anyhow and it initiated. It didn't complete because I was still locked, but at least it was a sign of life. And after it did it's partial run, I was able to but back into hboot.
Try it. You've got nothing to lose. Me though....I'm losing sleep and have to get up early tomorrow so I'm going to bed. I'll subscribe to this thread to try to keep up with it in the morning to see where you are at. Good luck.
oh. And sleep on it too if you find yourself getting frustrated. Sometimes I find that a night to sleep on it really clears my head to and let's me look at it with a fresh perspective the next morning.
Sent from my PG86100 using XDA App
All suggested up is what I'd recommend. I wish you best of luck.
remove power from the thing for 10 minutes - this means take the battery out, do not have it plugged in... then try again... sometimes they freak the f out over nothing...
Wife's stock EVO has done that when an app tried to reboot the thing.
Try typing fastboot oem boot in terminal with your phone connected obvs
Sounds like a dead battery. Try leaving it plugged in overnight or switch out the battery with a good one.
wrong section btw
Sent from my Touchpad using xda premium
thanx all for your responses. I appreciate them all. The only thing I haven't tried from suggestions above is keeping the battery out for extended period of time. Trying that now. Also since I am a complete noob what is ruu and is I avaliabe or Mac.
I had this issue with the 1.0.x versions on twrp
charge the battery externally if you can. then put it back in and try to turn it back on
do you have insurance? if nothing works take it to sprint service and act all dumb
mildlydisturbed said:
remove power from the thing for 10 minutes - this means take the battery out, do not have it plugged in... then try again... sometimes they freak the f out over nothing...
Wife's stock EVO has done that when an app tried to reboot the thing.
Click to expand...
Click to collapse
This was the fix that worked. Removed the battery for 2 hrs. Phone was fine after that. Posting from phone !
I had a the exact same thing happend to mine.
Repeated battery pulls did not help and it would just blink.
Took it to a sprint keosk at a mall and they just pulled the batter and replaced it with another battery and it booted fine, and then they put my battery back in and it was fine after that, although the battery needed to be charged.
Yeah that happened to my og evo I was all flippin out over a dead battery hahaha
Yep, dead battery. Freaked me out the first time this happened also.
Please use the Q&A Forum for questions Thanks
Moving to Q&A
This is not a dead battery issue but more accurately a "You phone thinks the battery is dead when its actually not" issue. I charged the battery for a long time using usb cable and my Mac and then using the stock charger and even that did not help. Repeated battery pulls also did not help. Only when the battery was taken out and left for a extended period was it fixed.
Here is my theory. All EVOs have a powerful capacitor inside them somewhere where they store the "Battery is almost dead" info and this capacitor takes some time to discharge. Every time you pull the battery and put it back in again the capacitor is not fully discharged and retains the "battery is almost dead" flag and never updates it even after repeated charging. The only solution is to pull the battery and leave it out for some time ( I left it out for 2 hours, someone here suggested 15+ minutes is good enough) and let the capacitor fully discharge at which point it will loose its "Battery is almost dead" flag. Then plug in the battery and everything is fine.
This explanation is a complete assumption but it is based on my observations and expriments. I have seen a lot of people post the same problem however no clear solution and tried solution as the one above so I hope this post helps others like me.
nimkar said:
This is not a dead battery issue but more accurately a "You phone thinks the battery is dead when its actually not" issue. I charged the battery for a long time using usb cable and my Mac and then using the stock charger and even that did not help. Repeated battery pulls also did not help. Only when the battery was taken out and left for a extended period was it fixed.
Here is my theory. All EVOs have a powerful capacitor inside them somewhere where they store the "Battery is almost dead" info and this capacitor takes some time to discharge. Every time you pull the battery and put it back in again the capacitor is not fully discharged and retains the "battery is almost dead" flag and never updates it even after repeated charging. The only solution is to pull the battery and leave it out for some time ( I left it out for 2 hours, someone here suggested 15+ minutes is good enough) and let the capacitor fully discharge at which point it will loose its "Battery is almost dead" flag. Then plug in the battery and everything is fine.
This explanation is a complete assumption but it is based on my observations and expriments. I have seen a lot of people post the same problem however no clear solution and tried solution as the one above so I hope this post helps others like me.
Click to expand...
Click to collapse
Glad you got it working.
Sent from my PG86100 using XDA App
So I was updating (well, downgrading firmware from 2.17 to 2.08 really) the firmware on my phone. It went through its thing and said it updated ok and to press power to reboot. I did and the screen went out, didnt come back on. Waited a minute and nothing, usually this works after a second or two so this is very odd. So I removed the battery and put it back and still nothing. I know is is VERY bad idea to remove battery during firmware update, but the update was done and the phone said it was all finished and needed to reboot by this point. Anyway, nothing will get the phone to turn on or show any sign of life. Plugging USB ion does nothing, plugging in to power does nothing. Removing SD card and trying to boot doesnt work, different battery doesnt work. Trying to hold all buttons while booting does nothing, trying to boot to bootloader does nothing, and booting like normal does nothing. Whether I press the power button or hold it for 3 minutes straight. Nothing. Is my phone hard-bricked now and I have to send it to HTC for reprogramming?
EniGmA1987 said:
So I was updating (well, downgrading firmware from 2.17 to 2.08 really) the firmware on my phone. It went through its thing and said it updated ok and to press power to reboot. I did and the screen went out, didnt come back on. Waited a minute and nothing, usually this works after a second or two so this is very odd. So I removed the battery and put it back and still nothing. I know is is VERY bad idea to remove battery during firmware update, but the update was done and the phone said it was all finished and needed to reboot by this point. Anyway, nothing will get the phone to turn on or show any sign of life. Plugging USB ion does nothing, plugging in to power does nothing. Removing SD card and trying to boot doesnt work, different battery doesnt work. Trying to hold all buttons while booting does nothing, trying to boot to bootloader does nothing, and booting like normal does nothing. Whether I press the power button or hold it for 3 minutes straight. Nothing. Is my phone hard-bricked now and I have to send it to HTC for reprogramming?
Click to expand...
Click to collapse
Ya if your hboot 1.5 S-ON you can't downgrade... Pullin the battery probably spanked it... Have you tried a RUU exe for the hell of it?
What hboot were you?
Wow, sorry bout your luck homey.
HBOOT-1.4 S-OFF
Anyone have any ideas?
Also tried plugging it into computer, doesn't register connection at all.
EniGmA1987 said:
HBOOT-1.4 S-OFF
Anyone have any ideas?
Also tried plugging it into computer, doesn't register connection at all.
Click to expand...
Click to collapse
Well I don't see what went wrong you should of been able to downgrade with no problems... The battery pull mighta done it in tho....
EniGmA1987 said:
HBOOT-1.4 S-OFF
Anyone have any ideas?
Also tried plugging it into computer, doesn't register connection at all.
Click to expand...
Click to collapse
Unfortunately sounds like it's all done man. You've confirmed battery is good by trying other ones, so it's got juice. Based on what you've said, it's toast. As far as I know, there is no way to recover an Evo3D when it's the state yours is in. TrevE was working on some download mode stuff, I think trying to jtag it, but never got to a useful point with it. Sorry for your luck.
Edit: And the only thing I can really think of to explain why it happened, is that perhaps your download was corrupted. Flashing a corrupted radio = brick. Did you check the md5sum? Because as long as you're positive that the firmware update was 100% complete before you pulled the battery, it shouldn't have bricked.
Took it in to a repair store, they completely took the phone apart and probed it with all their special tools and all that. Apparently the motherboard is fried. Dont know how that happens with something like this but whatever. Seems almost like dumb luck that it happened at the same time, but most likely it is somehow related.
Looks like I am leaving the EVO 3D family. I will miss all the fun stuff that goes on here and the AnthraX kernels. But I sold my brand new EVO3 D I got as a replacement for enough money to cover the whole ETF from Sprint and the cost of a Galaxy Nexus. So thats where I am moving.
as you read in the topic title. My HTC thunderbolt is dead. nothing. no yellow / green light at all. This has happened before..but a simple battery pull for about 20 minutes and a restart got me going again. Now...it won't work. I'm not a noob where I flashed the wrong radio or something stupid like that. I had fully functioning Thunderbolt with LiquidSmooth ICS JMOD MR2. Before my phone decided to commit permanent suicide, it was rebooting to the boot screen every hour or so to the LiquidSmooth boot animation while I was using PowerAmp. Then I shut if off normally (just like last time..) and now it won't charge turn on, or do ANYTHING. It won't even go to the HTC logo where I can go to clockwork or the hBOOT menu. I'm running out of options. If anyone could give me advice. That would be great, as I cannot afford another one :___;
Thanks for your time = ]
stanleyopar2000 said:
as you read in the topic title. My HTC thunderbolt is dead. nothing. no yellow / green light at all. This has happened before..but a simple battery pull for about 20 minutes and a restart got me going again. Now...it won't work. I'm not a noob where I flashed the wrong radio or something stupid like that. I had fully functioning Thunderbolt with LiquidSmooth ICS JMOD MR2. Before my phone decided to commit permanent suicide, it was rebooting to the boot screen every hour or so to the LiquidSmooth boot animation while I was using PowerAmp. Then I shut if off normally (just like last time..) and now it won't charge turn on, or do ANYTHING. It won't even go to the HTC logo where I can go to clockwork or the hBOOT menu. I'm running out of options. If anyone could give me advice. That would be great, as I cannot afford another one :___;
Thanks for your time = ]
Click to expand...
Click to collapse
Flashing the radio is the only thing u can flash and completely brick your phone with no fix if you flash wrong or the radio is for a different device then I think your just gonna have to move on to a different phone.
Sent from my AOKP HTC Thunderbolt from Tapatalk 2.4
jonah1234 said:
Flashing the radio is the only thing u can flash and completely brick your phone with no fix if you flash wrong or the radio is for a different device then I think your just gonna have to move on to a different phone.
Sent from my AOKP HTC Thunderbolt from Tapatalk 2.4
Click to expand...
Click to collapse
This is exactly what I didn't do. I was just stating that because I bet some users on here flash the wrong radio or unplug it during flashing and cry on here later for a solution. This is what I did not do.
With that said...is there any possible solution for my dilemma?
stanleyopar2000 said:
This is exactly what I didn't do. I was just stating that because I bet some users on here flash the wrong radio or unplug it during flashing and cry on here later for a solution. This is what I did not do.
With that said...is there any possible solution for my dilemma?
Click to expand...
Click to collapse
Try a different battery maybe. It might be dead. Your USB port could have gone bad too.
Sent from my Thunderbolt using Tapatalk 2
Not any solution or consolidation, but my first bolt did the exact same thing after flashing a rom that I won't name here. The issue was most likely mine,but it happened to me and at least one other user as well.
If yours spontaneously croaked, most likely not the same issue, but mine presented exactly what you described.
I had to get a replacement.
Sent from my ADR6400L using xda premium
smtom said:
Not any solution or consolidation, but my first bolt did the exact same thing after flashing a rom that I won't name here. The issue was most likely mine,but it happened to me and at least one other user as well.
If yours spontaneously croaked, most likely not the same issue, but mine presented exactly what you described.
I had to get a replacement.
Sent from my ADR6400L using xda premium
Click to expand...
Click to collapse
I had 4.0 LiquidSmooth ICS JMOD my custom ROM on my phone ever since the rom first came out.and it was perfectly...fine...
and this same problem happened when I had GB ThunderShed CM7..but my gf told me to pull the battery out and leave it out for 20 minutes..then it put it back in. It worked. She did this many times with her Droid 1. Since it was problematic with this issue. (first android phone OF COURSE its going to have problems) Now she's an iPhone user i'm constantly trying to convert back lol
anyway...as stated before..it's now done it again and this time it's totally dead. my phone was trying to tell me something I bet.
How old is your phone?
Nothing to do with radios or ROMs. A bricked phone will still receive a charge. You need to try a different battery ( preferrably 1 that is charged and for the Thunderbolt) once you get it booted into whatever ROM you're using, go to menu, settings, power and make sure that "fastboot" isn't checked. By default fast boot is checked by HTC and by most ROMs. What fastboot does is just put your phone into "hibernate" much like a PC does.
So when you turn your phone off, it appears that its off, but its really just sleeping. If the battery dies and fastboot is checked, the phone is hella confused about its current state. HTC did this by default for a better customer experience, but its kinda dumb and bad in the long run as your phone never gets a freaking break. Lol
Thats why I'm suggesting getting a good battery to boot up to a ROM or whatever, turn off fastboot, properly turn off the phone then charge your battery. It may take up to 10+ min before you to get an orange light that'll flash then eventually go solid. Let it go solid for about 20+ min to be on the safe side, then boot
Good luck man
Sent from my Geeked n Tweaked GS3
Man I bought one off craigslist that did the exact same thing. Had it about a week. Started random reboots so I was restoring a backup. While trying that recovery randomly rebooted a couple times them finally restore finished. It bootlooped so I pulled the battery and that was the last time it did anything. PC won't see it, won't get a charge light. Put a fully charged battery from my other tbolt in it. Still nothing. It literally died in my hands. I guess a hardware failure was the cause. Also picked up the wireless charging battery cover to try my power mat to see if that would at least make the charging light come on ....nope
dopediculous said:
Nothing to do with radios or ROMs. A bricked phone will still receive a charge. You need to try a different battery ( preferrably 1 that is charged and for the Thunderbolt) once you get it booted into whatever ROM you're using, go to menu, settings, power and make sure that "fastboot" isn't checked. By default fast boot is checked by HTC and by most ROMs. What fastboot does is just put your phone into "hibernate" much like a PC does.
So when you turn your phone off, it appears that its off, but its really just sleeping. If the battery dies and fastboot is checked, the phone is hella confused about its current state. HTC did this by default for a better customer experience, but its kinda dumb and bad in the long run as your phone never gets a freaking break. Lol
Thats why I'm suggesting getting a good battery to boot up to a ROM or whatever, turn off fastboot, properly turn off the phone then charge your battery. It may take up to 10+ min before you to get an orange light that'll flash then eventually go solid. Let it go solid for about 20+ min to be on the safe side, then boot
Good luck man
Sent from my Geeked n Tweaked GS3
Click to expand...
Click to collapse
You should try this, heck order a battery and wall charger off of Amazon for about $15.... Put the battery in and use ADB to put your phone into recovery....
Sent from my Inspire 4G using xda app-developers app
playerjunglejosh said:
You should try this, heck order a battery and wall charger off of Amazon for about $15.... Put the battery in and use ADB to put your phone into recovery....
Sent from my Inspire 4G using xda app-developers app
Click to expand...
Click to collapse
Doubt that'll work if its the same as mine. PC and adb won't see it. And I used known good batteries and charger from my other bolt.just gonna hold on to it in case I find one with a busted screen for cheap on craigslist
Well I've searched the net and this has happened to several people that weren't even rooted or on a custom Rom. To me it seems like the motherboard(or the phones equivalent) is fried....that would explain why it happens on many thunderbolts(but it could just be a simple fix that I don't know of)
Sent from my Inspire 4G using xda app-developers app
Lightning Won't Strike Twice Folks
disconnecktie said:
Try a different battery maybe. It might be dead. Your USB port could have gone bad too.
Sent from my Thunderbolt using Tapatalk 2
Click to expand...
Click to collapse
I had 2 differernt batteries one extended...the other the stock small one. both would not charge. and both had decent battery power when I shut it off.
Shadow Death said:
How old is your phone?
Click to expand...
Click to collapse
Got it a month after it came out first 4G LTE phone maaan
dopediculous said:
Nothing to do with radios or ROMs. A bricked phone will still receive a charge. You need to try a different battery ( preferrably 1 that is charged and for the Thunderbolt) once you get it booted into whatever ROM you're using, go to menu, settings, power and make sure that "fastboot" isn't checked. By default fast boot is checked by HTC and by most ROMs. What fastboot does is just put your phone into "hibernate" much like a PC does.
So when you turn your phone off, it appears that its off, but its really just sleeping. If the battery dies and fastboot is checked, the phone is hella confused about its current state. HTC did this by default for a better customer experience, but its kinda dumb and bad in the long run as your phone never gets a freaking break. Lol
Thats why I'm suggesting getting a good battery to boot up to a ROM or whatever, turn off fastboot, properly turn off the phone then charge your battery. It may take up to 10+ min before you to get an orange light that'll flash then eventually go solid. Let it go solid for about 20+ min to be on the safe side, then boot
Good luck man
Sent from my Geeked n Tweaked GS3
Click to expand...
Click to collapse
this phone does not. I had two batteries with a decent charge and they didn't charge on it. The ROM I was using was a AOSP rom. not sense based...so there was no power menu and a fastboot option to uncheck
wampuscat said:
Man I bought one off craigslist that did the exact same thing. Had it about a week. Started random reboots so I was restoring a backup. While trying that recovery randomly rebooted a couple times them finally restore finished. It bootlooped so I pulled the battery and that was the last time it did anything. PC won't see it, won't get a charge light. Put a fully charged battery from my other tbolt in it. Still nothing. It literally died in my hands. I guess a hardware failure was the cause. Also picked up the wireless charging battery cover to try my power mat to see if that would at least make the charging light come on ....nope
Click to expand...
Click to collapse
yep. it did die in my hands. I'm chalking this up to hardware failure as well...
playerjunglejosh said:
You should try this, heck order a battery and wall charger off of Amazon for about $15.... Put the battery in and use ADB to put your phone into recovery....
Sent from my Inspire 4G using xda app-developers app
Click to expand...
Click to collapse
two batteries and they do the same thing..and I cant boot into ADB mode if the damon can't detect the device on.
playerjunglejosh said:
Well I've searched the net and this has happened to several people that weren't even rooted or on a custom Rom. To me it seems like the motherboard(or the phones equivalent) is fried....that would explain why it happens on many thunderbolts(but it could just be a simple fix that I don't know of)
Sent from my Inspire 4G using xda app-developers app
Click to expand...
Click to collapse
Yep. the Motherboard is fried. has to be.
Thank you so much everyone for your advice, concern and help..but nothing can fix or repair hardware failure to this extent
I got a used HTC Rezound. It's amazing...it's everything the T-Bolt should have been
even though I had this problem before and a long term battery pull fixed it...Looks like Lightning Will Not Strike Twice for The Thunderbolt.
Thank you for your concern and support....but it's just as good as a future spare parts phone on craigslist.
This thread can be locked now.
I have no idea what went wrong or where. One day a few apps starting force closing. Then I got weird unlocking problems. Now google play crashed consistently on any search, as well as ****ing settings. I ****ing hate this phone.
-Rooted and unlocked via freegee.
-Installed clockwork over adb(everything was fine at this point)
-Flashed a few different ROMS
-Flashd beanstalk, and then the problems started.
-Can't get ****ing adb to connect no matter what so I can't flash a new recovery
-Considering beating in my phone with a bat.
Anyone have any suggestions for getting recovery working again? Clockworks app doesn't work, similar to what this fellow went through (and apparently solved) http://forum.xda-developers.com/showthread.php?t=2258671&highlight=can+t+boot+recovery
Haven't tried LGNPST because I have no idea what the acronym stands for and no one says what it is.
Refer to tinybin thread in android development
Sent from my Optimus G using Tapatalk 2
drwario said:
Refer to tinybin thread in android development
Sent from my Optimus G using Tapatalk 2
Click to expand...
Click to collapse
I've exhausted everything I could find through the teenybin thread. LGNPST and teenybin gave me back fastboot, but I still have no recovery.
Oh yeah, and a sweet bonus: My phone refuses to go past the boot screen when booting and adb on both my desktops refuses to recognize my device! Anyone want a free phone before I smash it to bits against my face?
Update: For all you poor fools who are following the same path, heres what happened.
Left it plugged in all night and it continued to flash red for a while, and then show a full charge screen, then turn off. Repeated this throughout the whole night.
Come morning I perform a hard battery pull via this thread: http://forum.xda-developers.com/showthread.php?p=45849420#post45849420
I wait a minute with the motherboard connector disengaged. Hold power button for 10 seconds. Plug back in, absolutely no change in my situation. I tried again for about 5 minutes, ditto.
So in conclusion, I broke my phone because I installed a custom rom and LG didn't want me to. I hope whatever team was in charge of developing this phone burns in hell like they so sweetly deserve.
**** you LG. ****. YOU. I want my ****ING money back. You make **** PRODUCTS.
Dude you are aware it's YOUR fault if any thing bad happens when you are playing around with a rooted phone. U installed it and its your own bad....
Sent from my LG-E975 using xda app-developers app
steffenbakke said:
Dude you are aware it's YOUR fault if any thing bad happens when you are playing around with a rooted phone. U installed it and its your own bad....
Sent from my LG-E975 using xda app-developers app
Click to expand...
Click to collapse
Yeah its my fault for installing a custom ROM. You wouldnt be saying this if a desktop or laptop magically stopped working after reinstalling windows or linux. If those were as randomly, stupidly risky, people would be ****ing in arms at microsoft, as they rightfully should be at carriers. Whatever man.
If you can't access recovery or the phone will not boot then adb won't work. You said that you do have the ability to use fastboot though. Have you tried flash twrp from fastboot?
Sent from my LG-E970 using xda app-developers app
Why you install recovery over adb? I mean, when you unlock with freegee it installs the recovery you want (cwm or twrp), so no need for adb.
Have you tried to KDZ a stock rom and do a hard reset?
putsometrebleinit said:
If you can't access recovery or the phone will not boot then adb won't work. You said that you do have the ability to use fastboot though. Have you tried flash twrp from fastboot?
Sent from my LG-E970 using xda app-developers app
Click to expand...
Click to collapse
I tried LGNPSTING a lot of things and now the battery is ****ed. Hard battery disconnect did nothing. It'll flash its light and maybe show the lg logo when plugged in.. but other than that its frustratingly dead.
Just sell the ****ng phone man...
You got frustrated due to a lack of patience. You can flash recoveries via fastboot. If you actually searched well you would have seen that.
Sent from my Optimus G using XDA Premium 4 mobile app
DeathmonkeyGTX said:
You got frustrated due to a lack of patience. You can flash recoveries via fastboot. If you actually searched well you would have seen that.
Sent from my Optimus G using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Doesnt work, and never did. The ****ing phone drivers are so ****ty and proprietary, no computer I used would recognize my phone. I actually managed to flash the stock AT&T rom to my phone through LGNPST, along with a recovery, or so LGNPST said, but of course another problem had to come up. Fantastic ****ing phone here.
swashy said:
Doesnt work, and never did. The ****ing phone drivers are so ****ty and proprietary, no computer I used would recognize my phone. I actually managed to flash the stock AT&T rom to my phone through LGNPST, along with a recovery, or so LGNPST said, but of course another problem had to come up. Fantastic ****ing phone here.
Click to expand...
Click to collapse
Then it sounds likely that you're doing something wrong, have an antivirus conflict, or genuinely do not have access to one well-maintained windows machine.
swashy said:
I tried LGNPSTING a lot of things and now the battery is ****ed. Hard battery disconnect did nothing. It'll flash its light and maybe show the lg logo when plugged in.. but other than that its frustratingly dead.
Click to expand...
Click to collapse
You can melt the software side of these phones so badly and still recover with the Qualcomm tools after the fact, it's not even funny how bad things can go before no return. Flashing a rom didn't do this, period. I want to believe you just suffered from a fluke hardware failure. Even more so it sounds like the USB connector went ape and continued wigging out from there.
The universal drivers also work perfectly. Considering in every way this is the nexus 4 with an SD card slot and a better LTE amplifier, everything you're ranting about is invalid.
The phone is a sanctioned, flash to hell and back model. You need to do some soul searching and find out where YOU went wrong. Or at least get an el cheapo multimeter out and start checking continuity. If it turns out you broke the charging connector or the battery connector off of the board you can STILL be saved. Just put in some effort and try to find the root cause. Screaming and cursing on a random corner of the internet isn't solving your problem
Making up crazed excuses isn't doing any service to you or the other forum users either. Especially the driver ranting. They work flawlessly. Hell even the generic Google provided SDK abd driver works.
If you figure anything out we're here to try and get you back to good.
Sent from my Optimus G using xda app-developers app
-edit- and leave the battery disconnected for awhile. The reason I suggest holding the power button while battery disconnected is in the hope that it will drain any remaining current out of the phone. There's no documentation to say it does or doesn't. So let the thing sit and be absolutely sure it's got a chance to reset. And check the battery voltage to confirm if it's dead or not. Since the contacts will be right there when it's disconnected...
That red light flashing / lg logo when plugged in is exactly where my phone and others was when needing a battery pull. It's fixed every phone I've heard of in that state. Try it again?
The same thing happened to me twice before. Both times I was able to recover my LG you get back into my recovery screen. What works for me is using Lgnpst back to stock jb. Next I flashed both teeny bins. Immediately after flashing the teeny bins, I open my LG up and pulled the battery. I waited about 10 minutes attach the battery back into the LG. Booted to the device and a factory reset my holding the power button in the volume down button. After the the device finished the reset I was good to go and my LG back to normal. This is what works for me give it a try... And good luck.
Sent from my Optimus G using Tapatalk 2
Well, another free day off, guess I'll give it a go again.
The connection of the battery to the mobo is most definitely intact. Pulled the plug to the mobo for ten minutes, plugged back in.
It still just steadily flashes red whenever I charge it. Nothing.
I'll try holding the power button while its disconnected, but I don't have a multimeter to check voltage.
Edit: Something changed. After sitting with the battery disconnected and a rubber band around the power button for 20 minutes, it showed a battery with a charge icon, then nothing. Havent had a screen for awhile. Pressing the power button, nothing. Holding it for awhile gets the full-charge battery, and if I keep holding it, the google symbol, and then nothing. I guess I'll try pulled the battery for 20 minutes again, Maybe it didn't fully discharge?
Edit 2: I've been informed that after a hundred battery pulls, the battery probably has something physically wrong with it. ****ing phenomenal goddamned phone here!! Why do I pay tech companies money for **** again?
swashy said:
Well, another free day off, guess I'll give it a go again.
The connection of the battery to the mobo is most definitely intact. Pulled the plug to the mobo for ten minutes, plugged back in.
It still just steadily flashes red whenever I charge it. Nothing.
I'll try holding the power button while its disconnected, but I don't have a multimeter to check voltage.
Edit: Something changed. After sitting with the battery disconnected and a rubber band around the power button for 20 minutes, it showed a battery with a charge icon, then nothing. Havent had a screen for awhile. Pressing the power button, nothing. Holding it for awhile gets the full-charge battery, and if I keep holding it, the google symbol, and then nothing. I guess I'll try pulled the battery for 20 minutes again, Maybe it didn't fully discharge?
Edit 2: I've been informed that after a hundred battery pulls, the battery probably has something physically wrong with it. ****ing phenomenal goddamned phone here!! Why do I pay tech companies money for **** again?
Click to expand...
Click to collapse
go to a service, ask them if it can be repaired, if they say yes go home and wait for an idea
if they say no dont lose the hope
its a great phone, and as you see you are the only one with this problem
and with that angriness you will do nothing, remember you and only you are the responsable for any damage your phone suffers, not the developer of that rom
hello guyz
Sorry for my bad english .
I''m here cuz my htc one max was out of charge ,
and when i plugged it to charge it won't charge ,
i tried to open it and same
#i tried to open it with recovery mode and smae
#led light not working too
#i tried different chargers with different outlits .
what to do plz ?
Constantly mess with all button combos when its plugged in. Try holding both vol buttons and power for example...
Jiggity Janx said:
Constantly mess with all button combos when its plugged in. Try holding both vol buttons and power for example...
Click to expand...
Click to collapse
i didn't work , same
Same here, vzw Htc One max no charge, no power....
One foggy hungover little extra bad on me. Was firewater s-off with temporary root, twrp 2
6.3 recovery flashed fine but never had SU commands only SH. In a hungover haze I noticed twrp had 2.7 open recovery out and without due thought I downloaded it to update the recovery. I blatantly force flashed the zip from my phone using CWMR. foolish of me straight out, no excuses. Phone rebooted twrp recovery flashed 2.7 zip and then power dropped immediately. Will not power up/charge.
I got the USB/DLOAD message. Been reading every since to self fix . Would appreciate advice on proper path to take. I've been reading on one hand since it was S-Off it possibly blew the LCD and no bueno brick city. Yet I've also seen success with flashing the RUU as a possible. Other option I found so far was run the JTAG method with Ubuntu and/or try shorting the 2/5 pins with 300k resister.
I'm not concerned about warranty, I would really appreciate anyone who has the time to respond and experience with this indescretion. I would prefer not to damage it further with incorrect fixes if possible. I believe i just jacked my boot image and need to use the RUU method unless the LCD was blown from over clocked over voting .
Direction on the correct method if any is appreciated. I'm completely open to answer questions i may not have addressed. Totally thoughtless and my fault yet I'm very clear on what I did to cause it. Many years electronics repair, still medicore Linnux skills so please go easy on me there. I just need the correct path if known. Im a big boy and fully capable of learning it on my own so no need for you to feel you have to list script and hold my hand.... but a good ass chewing is never out of line ") Thanks for any experience you wish to share.
someone help please ?
Phones dead, no led, no charging, no button combo brings it back. Everything worked great, plugged it in Friday night like always, wake up Saturday to find it was off while on the charger. The cable and charger that it came with, and girlfriends DNA charges on it no problem. Took it to Verizon and they tried a few things, nothing they did helped, like I was surprised. So they are sending me one, but I want to know what happened and how to fix it. This seems to be a common problem, but it seems most people at least get it to power back on at one point.
Exactly what was happen to me some time ago.The only solution i found is to open case and charge the battery about 10 seconds.I advise you to use usb port of your computer to charge it. Btw if you let it drain to zero you will have to do this procedure again