My 15 Y-O was using my old MT3GS while waiting on parts for her iPhone 3G. Once the parts came in and her phone was back working, she turned off the MT3GS. Two days later she dropped her phone and broke her digitizer. She went back to the MT3GS but it wouldn't start. Her sim card is good, she's now using our phone of last resort, an old Samsung feature phone.
When I opened the back to pull the battery I found the sim card tray unlocked. I fixed the sim tray, pulled the battery, waited a few minutes and put the battery back. On startup it vibrated once, but nothing else happened. I assumed the battery was drained, so I stuck in on the charger overnight. When I woke up, the battery light was green indicating a full charge, but it still does the one vibrate and then a whole lot of nothing.
Any ideas or suggestions?
Is the phone stock or rooted?
Sent from my T-Mobile myTouch 3G Slide using xda app-developers app
It's stock, but I picked it up from eBay and I've replaced all of the external hardware. (Digitizer and outer shell)
I did pull the sticker off the original shell and move it to the new shell, but it's obvious to see.
A few questions, are you running the froyo update? Do you have the sdk installed? Are you willing to root/unlock the phone?
If the answer to all these questions is yes then you can try to root/unlock the phone, install a custom recovery, do the nessasary wipes and reinstall your rom or even a custom rom of your choice. I'm not sure if its a hardware issue. Doing the above doesn't work then I would say it is a hardware issue.
Sent from my T-Mobile myTouch 3G Slide using xda app-developers app
Dvarl said:
A few questions, are you running the froyo update? Do you have the sdk installed? Are you willing to root/unlock the phone?
Click to expand...
Click to collapse
I'm running 2.2 (but not the updated release in the past week). I should, I've rooted and installed a custom ROM on my MT4GS. And I'm more than willing to root / unlock this phone.
Dvarl said:
If the answer to all these questions is yes then you can try to root/unlock the phone, install a custom recovery, do the nessasary wipes and reinstall your rom or even a custom rom of your choice. I'm not sure if its a hardware issue. Doing the above doesn't work then I would say it is a hardware issue.
Click to expand...
Click to collapse
Any suggestions on where to start?
I assume your on the 1.05 hboot? Check your hboot if it is you will need to unlock through htcdev.com. follow the instructions, and root that way. There is another thread on the forums that discuss this method. I did s-off early on so I won't be of much help with the official method.
http://forum.xda-developers.com/showthread.php?t=1500700
Sent from my T-Mobile myTouch 3G Slide using xda app-developers app
Dvarl said:
I assume your on the 1.05 hboot? Check your hboot if it is you will need to unlock through htcdev.com. follow the instructions, and root that way. There is another thread on the forums that discuss this method. I did s-off early on so I won't be of much help with the official method.
http://forum.xda-developers.com/showthread.php?t=1500700
Sent from my T-Mobile myTouch 3G Slide using xda app-developers app
Click to expand...
Click to collapse
I can't check my hboot, since the phone won't start.
Also Windows sees an empty removable disk.
ABD and FASTBOOT command shows no devices connected.
If adb and fastboot won't read the phone then I'm at a loss. Sorry I wish I could be more helpful.
Sent from my T-Mobile myTouch 3G Slide using xda app-developers app
---------- Post added at 02:42 PM ---------- Previous post was at 02:30 PM ----------
The same thing happens if you hold vol down + power? Just a single vibrate and a blank screen?
Sent from my T-Mobile myTouch 3G Slide using xda app-developers app
---------- Post added at 03:15 PM ---------- Previous post was at 02:42 PM ----------
I did some checking around and other people have had this problem too. Sounds like it is one of two things. A: it is a hardware issue. B: your yaffs partition got corrupted somehow. Neither of those can be fixed here. The phone would need to be serviced, but I would get a second opinion, I don't know all there is to know about the phone and I'm not a dev. You could try taking the phone in and have it looked at. The best of luck.
Sent from my T-Mobile myTouch 3G Slide using xda app-developers app
So what happens when you hit power is a single vibrate and then nothing. The phone won't change, won't turn on and then won't do anything until you pull the battery.
Dvarl said:
The same thing happens if you hold vol down + power? Just a single vibrate and a blank screen?
Click to expand...
Click to collapse
Interestingly enough, vol down and power does absolutely nothing. No vibrate, nothing. But after giving up, you can hit power to get the one vibrate....
---------- Post added at 02:25 PM ---------- Previous post was at 02:08 PM ----------
So I did a bit of thinking about this and wondered if the problem might be the LCD.
I pulled the battery
I hit vol down + power
I hit vol down again
I hit power
When I plugged it in via USB my PC recognized it and I was able to get the following from ADB.exe.
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
List of devices attached
HT06WPS10312 offline​
So now I'm fairly well convinced that the phone may be ok and it's just the LCD that's dead. But I need some assistance with validating the phone is ok before I consider spending $20 - $30 for a replacement LCD.
I had a similiar problem that turn out to be a bad battery. Wouldnt hold a charge and wouldn't boot. Is this the oem battery?
Sent from my openAOS Build of Android 2.3 (cyanogenmod edition) using xda app-developers app
Related
I was flashing jackos s3 radio after the phone finished installing the update it will not start at all any fix for this previously it was stuck at htc screen did the task 29 and flashed the jackos rom will stay stuck at htc screen thanks
Is your device GSM or CDMA?
is gsm tried everything I could think of, I hope you have a suggestion the only thing that I found is the last resource is that riff jtag box ($150 plus shipping) but I don't have it, and I don't think is worth it for one phone.
Try...
Try flashing stock rom....i think hold volume down and press power button..go to bootload screen/ three color screen..
.then insert cable and flash stock rom
that is the biggest problem I don't get a bootloader screen or any screen any longer it seems like the the cellphone is dead, it tried holding the reset button with battery and without and it makes no difference, it just died after flashing the radio and I don't get a screen anymore I tried a different battery I have a separate charger, and it doesn't work either...
Not enough information to work with really, could you say more about the steps you took in this flash. There is a lot of help here on XDA but only IF enough is known. What you describe is not a common failure. Somethings been left out.
Just have to wonder if you were stock rom prior to the flash, were you unlocked, did the device operate properly before ANY flash was attempted ect....Not knowing were you started and the steps taken make it difficult, xda folks love fixing these things TELL US MORE !!!
PS I'm only here once or twice a month but really have gotten nothing less than the best help here when asked for with better information.
Let me see this telephone is not mine is from a friend that gave to me to fix it, the phone it was unlocked and on the bootloader screen it said security disabled I think something like that,
what it was wrong is that it was stuck on the htc white background
everytime you turn the phone on, I read some threads on how to repair this and found out how to get to the bootloader screen,
then I flashed, Rhodium-HardSPL_V2_00R3_185HSPL it completed and then rebooted, I flashed then Jackos S3 JackFULL 1.4.0, it completed 100% but I got the same error, I read on some thread that you somebody fixed that error by using task 29 so I flashed task 29 and then I flashed the same rom, it was stuck on the same htc screen so I checked on the rom folder there was another file recommended radio Radio_Rhodium_4.49.25.91 I flashed that file to see if it fixed the problem, but after it finished the phone turn itself off and did not start again,
then I checked the battery it had charge,
I tried a different battery nothing,
if I remove the battery slowly I see the red low battery light on for an instant
so the phone is getting power,
I pressed the power button and down button nothing
just the power button nothing,
tried holding the reset button nothing,
it is in a brick state,
is there any hardware mod for this phone,
I fixed a samsung captivate with a tool you created using a micro usb head some resistor in order to put it in a state called download mode,
the only thing I found on how to revive this is this box http://www.gsmserver.com/shop/gsm/riff_box_jtag.php the problem I don't have the money for it...
is that enough information? and of course the rom I use it was a gsm rom
I wonder if a hard reset would snap it into doing something...remove the battery, wait a couple of minutes, put the battery back in.. hold the talk and end buttons down and press the power button...I'm really not sure as I have not experienced this, but...I don't think anything would be a waste of time at this point
---------- Post added at 12:16 PM ---------- Previous post was at 11:52 AM ----------
oops...oh yeah...if the device does power on and you get a screen press the volume up next and see what if anything happens
that is right I have to try everything, but it didn't work but thanks anyway any suggestions I am still open to try everything...
I know you say the phone is GSM but...could you please tell us which, if any, carrier information the phone was designed for, and which rhodium version it is by looking at the sticker under the battery?
Ive been looking for a while into a solution for your symptoms and what Ive found thus far indicates a wrong radio was installed...CDMA radio to GSM device, or vice versa....there are people on this site who know everything, I am not one of them, but...it might be the case where you use MTTY...a low level type of command you can send to the phone via usb from your PC...I'm still looking...perhaps try looking too and cut the time in half lol...the low level commands can get to the device without it being in bootload screen...I think...as I said, I'm still looking for solutions
---------- Post added at 09:46 PM ---------- Previous post was at 09:10 PM ----------
read up on this...
http://forum.xda-developers.com/showthread.php?t=371154
and there's an example here
http://www.youtube.com/watch?v=4fQE0P3diKg
I'm not saying this will work and certainly dont try anything without reading up on the process in the first link
---------- Post added at 10:07 PM ---------- Previous post was at 09:46 PM ----------
I've been reading the thread of the link I posted, it's not relative to the Rhodium specifically, but still good reading until some Rhodium specific links can be found
Ok, so today I was simply trying to backup my phone and it started to give errors and did not save the backup. Since that point it will not go past the HTC white screen. I have tried to restore the different backups and even to install new different ROM. None of this is working so I decided after reading multiple post to just go to recovery and use the PG32IMG file but now it has been updating for 30 min but not progressed. What have I done and how do I fix this?
Update: Now that I have waited for the phone to reboot, the battery has died and it will not charge. Now after I plug it in, the light does not come on showing it is charging. Looks like it might be an insurance claim unless anyone has any ideas.
Flightmed said:
Ok, so today I was simply trying to backup my phone and it started to give errors and did not save the backup. Since that point it will not go past the HTC white screen. I have tried to restore the different backups and even to install new different ROM. None of this is working so I decided after reading multiple post to just go to recovery and use the PG32IMG file but now it has been updating for 30 min but not progressed. What have I done and how do I fix this?
Update: Now that I have waited for the phone to reboot, the battery has died and it will not charge. Now after I plug it in, the light does not come on showing it is charging. Looks like it might be an insurance claim unless anyone has any ideas.[/QUOTE
I'm experiencing the same problem... hope someone can help us out... this leads me to believe that its a bad ruu download....
Sent from my Galaxy Nexus using xda app-developers app
Click to expand...
Click to collapse
It's a known issue with the micro-usb port & its easier to probably do the insurance claim.
Sent from my Incredible 2 using xda app-developers app
if u let the battery die all the way to the point it shut off and u cant turn back on and it wont charge, it very well may an issue with the custom Recovery..
u can find much info on this prob in the rezound forums i know they found a fix, this pertained to the CWM recoveries on rezound so search for that, sorry i would but short on time.
---------- Post added at 02:22 PM ---------- Previous post was at 02:21 PM ----------
Flightmed said:
Ok, so today I was simply trying to backup my phone and it started to give errors and did not save the backup. Since that point it will not go past the HTC white screen. I have tried to restore the different backups and even to install new different ROM. None of this is working so I decided after reading multiple post to just go to recovery and use the PG32IMG file but now it has been updating for 30 min but not progressed. What have I done and how do I fix this?
Update: Now that I have waited for the phone to reboot, the battery has died and it will not charge. Now after I plug it in, the light does not come on showing it is charging. Looks like it might be an insurance claim unless anyone has any ideas.
Click to expand...
Click to collapse
ours is a diff number PG32IMG = inc2 we are Pxxximg.zip
Update: Well I called Verizon and explained the problem to them and they have sent me another phone under warranty. I received the phone charged the battery and put it back in the old phone and it will still not turn on.
So the other day if fell/dropped my phone in a puddle and before I could pull the battery the power button shorted. It's all dried out now and as good as it can be, for a while everything was working fine but then the battery died and now, seeing as the power button doesn't work at all, I have no way of charging it. Is there any way to boot without the power button? It's just stock and I've tried a bunch of battery pulls, unplugging/replugging the charger, all this janky stuff that I read about here and elsewhere, but none of them work. I know that the best thing is to go to the store, and I will eventually, but I'd like a work around for the time being. I saw someone mention that it can be turned on by a key combo on the keyboard, anyone know what that is?
There's some apps in the play store that will turn on the the phone without the power button, but they're buggy.
Search power on.
Some require root but most don't. It uses the proximity sensor If I remember correctly.
Sent from my SPH-D710 using xda app-developers app
But I have no way of booting to download any apps.
Did you have usb debugging enabled? You can reboot it using adb I'm pretty sure
sent from MY BAD A$$ ET4G
---------- Post added at 06:16 PM ---------- Previous post was at 06:10 PM ----------
www.xda-developers.com/android/lets-talk-about-adb/
sent from MY BAD A$$ ET4G
I did not.
Something tells me you are on the wrong device thread... What keyboard combo are you talking about? We don't have e a keyboard on this device.
Sent from my SPH-D710 using xda app-developers app
Hi all,
Installed snd Bootloader as described (don't have link at hand sorry)...all seemed well. Got a screen with Fastboot Logo and used pr to reboot, again as prescribed. Kindle turned off and its two days now and it STILL refuses to boot up AT ALL.
Tried the various methods of holding on button for 30 secs etc etc...all to no avail. Not recognised by PC (unsurprisingly).....so,
...am I now the proud owner of a rather expensive paperweight?
No warranty I hasten to add!
So you didn't tell us too much. Does it do anything at all. If it displays anything then you probably can fix it.
Sent from my KFJWA using xda app-developers app
---------- Post added at 09:36 PM ---------- Previous post was at 09:32 PM ----------
http://forum.xda-developers.com/showthread.php?t=2011126
Check out this thread. It has helped me recover.
Sent from my KFJWA using xda app-developers app
...nothing much to add. Its like a piece of wood. Displays nothing. No change when plugged in, PC doesn't see it either of course. Can't use any of the Android First Aide apps either, as its no turning on at all...
myotai said:
...nothing much to add. Its like a piece of wood. Displays nothing. No change when plugged in, PC doesn't see it either of course. Can't use any of the Android First Aide apps either, as its no turning on at all...
Click to expand...
Click to collapse
Unfortunately, My Kindle have the same problem as yours. My device now refuses to repones at all to whatever measures I take. Searching for useful help......
Hey guys, I'm new to XDA so please forgive the noob post, I'm just trying to get my phone working again. I broke the screen and now the bottom half of my phone is unresponsive (capacitive keys don't work). I'm rooted with TWRP installed, stock 4.1.2. Everything was fine until my friend thought it would be funny to put a lockscreen on my phone. I am unable to rotate my lockscreen to 270 degrees (how i've been managing to use my device with the help of gravity box on screen navigation keys) and am now permanently locked out of my decice. I can't input the correct pin that he told me (6735) or even incorrectly five times to reset via google account because the "ok" button is located on the part of the screen that I can't click. I thought that hopefully I had left USB debugging on so that I could send an ADB command to unlock my phone but it won't even recognize my device when it's plugged in, meaning I must have unchecked USB debugging. On top of that, my phone is in charge only mode, with the option to switch to USB mass storage stuck behind the lock screen. So my problem is that I want to go into twrp recovery, created a nandroid backup then factory reset my device. But of course, TWRP doesn't rotate either. I can click most of the buttons, including Backup, wipe, etc, but can't actually execute any action because the "swipe to ..." is located on the bottom of the screen - where I can't click. I was wondering if anyone could somehow flip the TWRP program upside down so that I could use it.
I just realized that I don't know how I would get the new version of recovery on my device anyway, because I can't even connect my phone to the computer for it to recognize as mass storage... any suggestions, help, advice, anything! would be very very appreciated. Thanks.
PS - This is MY phone, not stolen, not picked up anywhere, I know my google account info, I know the phone number, I know most everything about it so if you need some sort of verification that it's mine, let me know. I would just like to be able to use my phone again. Thanks
Your friend is a jerk. I'd punch him in the face.
Can you access the side load option in twrp?
oohaylima said:
Your friend is a jerk. I'd punch him in the face.
Can you access the side load option in twrp?
Click to expand...
Click to collapse
I can get to the "swipe to start sideload" screen but can't swipe because it's below the crack... :/
Could I just get a new digitizer, would that fix it?
Would be easier to get digitizer+LCD already put together. I screwed up a new screen on my evo because the LCD didn't get heated up enough to separate the glue. I do have the official service manual for the phone so if u want I can send u what it says to do to separate the LCD and digitizer if u don't want to pay the extra
Sent from my iPad using Tapatalk HD
---------- Post added at 07:03 PM ---------- Previous post was at 07:03 PM ----------
But yes a new digitizer would fix it
Sent from my iPad using Tapatalk HD
AFschizoid said:
Would be easier to get digitizer+LCD already put together. I screwed up a new screen on my evo because the LCD didn't get heated up enough to separate the glue. I do have the official service manual for the phone so if u want I can send u what it says to do to separate the LCD and digitizer if u don't want to pay the extra
Sent from my iPad using Tapatalk HD
---------- Post added at 07:03 PM ---------- Previous post was at 07:03 PM ----------
But yes a new digitizer would fix it
Sent from my iPad using Tapatalk HD
Click to expand...
Click to collapse
Any idea where I'd find it already put together?
I'll do some quick hunting, see if I can't find it
Sent from my LG-LS970 using Tapatalk
---------- Post added at 12:28 AM ---------- Previous post was at 12:17 AM ----------
http://www.ebay.com/itm/LCD-Display...34037?var=590205692373&_trksid=p2054897.l5658
Or can select different parts on that listing, for example. Just search google for touch digitizer LCD assembly ls970, that's what I did. There are other cheaper ones but that one is just plug it in, screw it back together and go, so...
Sent from my iPad using Tapatalk HD
Hmm.....try fastboot, then load clockwork non-touch version through adb and see if that works.
oohaylima said:
Hmm.....try fastboot, then load clockwork non-touch version through adb and see if that works.
Click to expand...
Click to collapse
I can't load anything through ADB because my phone won't connect to the computer - USB debugging is turned off. If I could use ADB I would just use an unlock command to remove the pin.
Thanks though.
UnluckyTech said:
I can't load anything through ADB because my phone won't connect to the computer - USB debugging is turned off. If I could use ADB I would just use an unlock command to remove the pin.
Thanks though.
Click to expand...
Click to collapse
That doesn't matter in fastboot. As long as you have the drivers for the o/s to read the device adb will pick it up. In windows 8 you have to install modified drivers for it to read it.