So while i was at work today, I was just browsing through twitter on my phone and randomly it force closes, so I tried to reopen the app and it forces closes again and im like . So I thinking of just going to the market, uninstall and reinstall, when i opened market it force closed. Basically everything i opened force closed and so i was like ok ill just reboot.
After the phone turned off, it just stayed off, I cant turn it on, it won't charge(well it might but the led is not lighting up), nothing is working. Though when i do plug it into my computer my computer recognizes it but fails to install any drivers.
Any suggestions on what I could do from this point? Thanks in advance.
what rom were you on?
Try taking the battery out for like 10 minutes and put it back in. Never happened to me, but I have read posts where this has worked.
saranhai said:
what rom were you on?
Click to expand...
Click to collapse
Faux's AOSP Rom
lowandbehold said:
Try taking the battery out for like 10 minutes and put it back in. Never happened to me, but I have read posts where this has worked.
Click to expand...
Click to collapse
Ill try it.
what was the root method you used?
also.. if you do.. do you know what your eMMC chip was?
sorry for all the questions
saranhai said:
what was the root method you used?
also.. if you do.. do you know what your eMMC chip was?
sorry for all the questions
Click to expand...
Click to collapse
Tbh i forgot, I had this phone since it first came out, so whatever the first root method was, was the one i used. no idea what the emmc chip is.
Sounds like a failed emmc, if you can get adb to recognize it check it. But random fcs followed by no boot definitely sounds like a failed emmc.
Sent from my HTC Glacier
Nicgraner said:
Sounds like a failed emmc, if you can get adb to recognize it check it. But random fcs followed by no boot definitely sounds like a failed emmc.
Sent from my HTC Glacier
Click to expand...
Click to collapse
how exactly do i check an emmc?
tonyriceroni said:
how exactly do i check an emmc?
Click to expand...
Click to collapse
if you can't go into the OS, then go into recovery,
use adb and type
Code:
adb shell
cat /proc/kmsg | grep mmc0
I wouldn't worry so much about the emmc. I think that's a prob with newer phones(might be wrong on this). None the less this seems to have different symptoms. Your biggest concern is getting into recovery.
Can you boot into the bootloader?
If so do you have the Eng spl?
Use either that or adb to boot in to recovery
Adb reboot recovery
Fastboot reboot recovery
If neither of those work but you can boot into the bootlader try running the PD15IMG.zip
It will reset the phone and you will have to reroot but atleast you have your phone back. Let me know if any of this works please. If not we can go from there
He said his phone won't turn on at all. I don't recall that being a symptom of the failed eMMc chip. Probably a good thing though, will make getting a replacement less of a headache.
lowandbehold said:
He said his phone won't turn on at all. I don't recall that being a symptom of the failed eMMc chip. Probably a good thing though, will make getting a replacement less of a headache.
Click to expand...
Click to collapse
I know I'm hoping he just forgot about hboot
Sent from my HTC Glacier using XDA Premium App
Yeah I can't access recovery at all. I can't get my computer to recognize the phone through adb either. Im just going to call tmobile and see what i can do
So random update, I gave HTC a call and they gave me a RMA # to send to them to check the phone out. So sent it in(bout a week and a half ago) and they told me they would call me after they found out what the problem was and discuss cost of repairs. So today I wake up to find my phone at my door and everything is working again. No idea if they are going to charge me or not but this is how i fixed my problem lol.
I also purchased a SGS4G for the time being and am loving it. Now I don't which phone to keep X.X
If they sent it back without a call then your only out the shipping to them. Done 2 now, both were that way.
tonyriceroni said:
So random update, I gave HTC a call and they gave me a RMA # to send to them to check the phone out. So sent it in(bout a week and a half ago) and they told me they would call me after they found out what the problem was and discuss cost of repairs. So today I wake up to find my phone at my door and everything is working again. No idea if they are going to charge me or not but this is how i fixed my problem lol.
I also purchased a SGS4G for the time being and am loving it. Now I don't which phone to keep X.X
Click to expand...
Click to collapse
Related
so my mytouch 4g wont turn on even with a different battery. i plug it it in and it gives me a flash on th screen but thats it. any suggestion without sending it in
Take it to a tmo store, they'll swap it.
I got it off of Craigslist I think it was previously tampered with
Sent from my HTC Desire using XDA App
so i was in the process of doing a custom splash screen last night. i went through all the instructions on how to push the custom splash through terminal. everything went how the instructions said, but once i reboot it my phone turned off and never came back on. it doesnt power on, boot into recovery, nothing! i put the phone to charge and the red light comes on on the top left but when i take it off the charger it stays on.
i been rooted for about a month now and i was running cm7 build 8 when this happened. i just want to see if anybody has any idea on what going on. i tired everything i can think of. taking out the battery and normally powering on and nothing. taking off the battery and volume down and power to boot into recovery and nothing. taking off the battery, sd card, sim, putting back the battery and doing both normal power on and to boot into recovery and nothing.
First of all you just hijacked the guys old dead thread and second it sound like you just bricked your phone. As there is boot animation and there is slash screen. Seems like you flashed wrong thing. If the screen don't even turn on its dead then.
Sent from my HTC Glacier
Don't flame the poor guy! He's got it bad enough as is! And he didn't flash the "wrong thing" there are several threads on flashing splash screens in this phone's forum. Cut the guy some slack. He knows it may be bricked, he's just hoping it's not. And he was hoping for someone to provide some possible help. Not be be given **** for not opening a new thread.
i thread jacked because the thread was old and didnt want to clutter by starting a new one when im having some what the same problem. but no i pushed the splash image. i had already flashed a boot animation a few day back. i had call of android running on my phone as a boot animation. i just want to know is theres other methods of reaching hboot or recovery.
First of all don't put words in my mouth as my post does not contain any flame, second when I said wrong thing I meant he may not have meet the requirement for the splash image if he did correctly then obviously he would have had it up and running. Best thing for him would be going back to the original thread where he downloaded the image and asking the OP and troubleshoot it but at this point its to late all he can do now is warn others.
But if his phone is not old lol he can social engineer and play the victim card and send it back to HTC but first would be trying TMo saying he didn't get the POST OTA as he had PRE OTA and when he try to install the OTA it went blank and act like he has no idea what is going on, as he simply just want the phone to work or he will cancel service and do acting best of his life.
i already know i probably super bricked it. becuase ive bricked it before but not like this. i was able to fix it very quickly before. its like if the phone just doesnt have a battery. im just going to wait to see if anybody else has any more input. if not ill head to the tmo store see what they can do.
BlackSHELF said:
But if his phone is not old lol he can social engineer and play the victim card and send it back to HTC but first would be trying TMo saying he didn't get the POST OTA as he had PRE OTA and when he try to install the OTA it went blank and act like he has no idea what is going on, as he simply just want the phone to work or he will cancel service and do acting best of his life.
Click to expand...
Click to collapse
I do apologize for using the word flame. It was too strong. But I get fired up when people criticize instead of offering insight. If you had posted the above paragraph first, I wouldn't have had any issues. This is good and viable option. Albeit a last resort, but much better than criticizing for thread jacking. And I am the OP of the thread that he's using and am doing EVERYTHING I can to help him figure out a way to get this resolved.
coupetastic-droid said:
i already know i probably super bricked it. becuase ive bricked it before but not like this. i was able to fix it very quickly before. its like if the phone just doesnt have a battery. im just going to wait to see if anybody else has any more input. if not ill head to the tmo store see what they can do.
Click to expand...
Click to collapse
ok, I just got caught up on your issue. I am going to do a little research and see if I can come up with anything to maybe help. Do you have adb set up? What recovery are you running?
Same thing happened to me, flashed a rom rebooted and the phone never turned on again.
thanx every one for trying to help. i tried everything i can think of and i could not get that phone to power on at all. it was completely dead. so i went to the tmo store by my pad and they gave me a brand new one. now i just need to gain s=off on this one which i cant do for some reason. i dont know why since it was fairly easy to gain s=off on my other mt4g. ill figure out though.
coupetastic-droid said:
thanx every one for trying to help. i tried everything i can think of and i could not get that phone to power on at all. it was completely dead. so i went to the tmo store by my pad and they gave me a brand new one. now i just need to gain s=off on this one which i cant do for some reason. i dont know why since it was fairly easy to gain s=off on my other mt4g. ill figure out though.
Click to expand...
Click to collapse
Don't know if you used this guide yet or not but I will post it anyway http://forum.xda-developers.com/showthread.php?t=858996
toby4059 said:
Don't know if you used this guide yet or not but I will post it anyway http://forum.xda-developers.com/showthread.php?t=858996
Click to expand...
Click to collapse
I aready got s=off but thanx anyways.
Sent from my CM7 Glacier using XDA App
Hi.
I had the same problem on my htc glacier (mytouch 4g) which was turn it on, stuck on the htcwelcome screen, keep loading and then turn off automatically. My phone is rooted and cusome flashed to the new htc 3.0 sense when this happened, i did a back up and restore to the oem mytouch sense and now it is working just perfectly. So if your phone is rooted you might give it a shot and hope it will work again
i had same prob kinda
i flashed a rom was useing it for a week and today i went to use camera and while camera was loaded the screen shut off like not beining used it did the crt thing and all then it wouln't come out of it so i pulled battary after like 5 min of a lighted black screen and went to power phone back on and nothing like no batt.....
anyways what i was geting to is that i called tmoble and they said it sounded like a hardware problem if you can plug it in to wall or car charger and nothing.. when i plug it into a usb on pc i get
hsusbs or something so u all might want to look into that.
i have s mytouch 4g it wont boot
i rooted my mytouch 4g ussing gfree and then i installed sense 3.0 rom and it worked then force closed left me in bootloader then from there flasheed cm7 worked good for 15 days then said force closed again then never turned back on aghain now when i plug it back in it tells me cannot install drivver software and it recognizes it as qhsusb_dload any solutions or its a gonner contact me at [email protected]
Hi again guys. I dont know if i ralle can use the term bricked or not, but i guess so. After a funny day with a couple reboot and new "radio" image my Legend want start anymore. The screen is just black, even if i hold down vol down/up and power. So the big question.... Is this phone bricked? If so, can i fix it?
EDIT: The LED does not even respond when charger is plugged in.
Sorry for the lack of English.
if it is bricked - try this.
I dont even get to fastboot The phone is completely dead/black
Are you S-OFF? I've never known a S-ON Legend be completely bricked like that!
No i'm still S-ON because of the d*** HBOOT 1.01
Only thing i've done so far is root+CM7. And yesterday when i played around with ROM Manager i had to remove the battery upon a crash.
Apparently same problem as here : http://forum.xda-developers.com/showthread.php?t=1096083
This is really weird...
I dont even get to fastboot The phone is completely dead/black
Click to expand...
Click to collapse
I think you are in trouble...
RomManager is maybe the source of your problems, what did you do with ?
Did you have errors during the radio installation process ? and which radio were you flashing ?
Here the story. I rooted my phone and switch to CM7 and notice that my GPS did not work with stock radio verision (dont remember wich) I upgraded to 7.08.35.21 and the GPS finally workt again with some minor interrups. Did some reading and decided to upgrade again to 7.13.35.05.
The installation went well untill the end. A picture was shown, a mailbox lookalike with an arrow pointing at a foolish looking droid dude. The only thing i could do was to remove the battery, after that the phone was dead.
SGT John Doe said:
Here the story. I rooted my phone and switch to CM7 and notice that my GPS did not work with stock radio verision (dont remember wich) I upgraded to 7.08.35.21 and the GPS finally workt again with some minor interrups. Did some reading and decided to upgrade again to 7.13.35.05.
The installation went well untill the end. A picture was shown, a mailbox lookalike with an arrow pointing at a foolish looking droid dude. The only thing i could do was to remove the battery, after that the phone was dead.
Click to expand...
Click to collapse
me too it sucks
Is it still under warranty? (Obviously not as you're rooted, but would it be if you weren't rooted?) If so, try sending it to HTC they might just replace it if they can't see for themselves that you're rooted!
If you says its a firmware update that caused the phone to not turn on they just JTAG it without checking,reflash the latest update (and sadly HBOOT) and send it back
bonesy said:
If you says its a firmware update that caused the phone to not turn on they just JTAG it without checking,reflash the latest update (and sadly HBOOT) and send it back
Click to expand...
Click to collapse
ok but they could ask what update and stuff possibly just thinking i might ring them soon whats the worse thing that could happen if they work it out? Just out of question?
madcat340 said:
ok but they could ask what update and stuff possibly just thinking i might ring them soon whats the worse thing that could happen if they work it out? Just out of question?
Click to expand...
Click to collapse
They will send it back unfixed and say the warranty is void. Even if they know its rooted they might still fix it for you, it depends.
It's my fault that the phone is broken and i'm willing to take that blame A clean conscience makes me sleep better at night
I dont know how it is in the rest of the world, but in my country there is a high fee if they notice that the owner has done something with the firmware etc. Thanks anyway for all the respons and help, and remember guys, stay away from Rom manager
You only have to say that it said update available then when it restarted it did this.. If they say anythign after its been sent then just plead ignorance.Its not like they cant afford to repair one phone
bonesy said:
You only have to say that it said update available then when it restarted it did this.. If they say anythign after its been sent then just plead ignorance.Its not like they cant afford to repair one phone
Click to expand...
Click to collapse
well i'm going to say something like that. Generally because my phone was buggered before then (signal problems and locking into airplane mode) though i'm rooted i still wouldn;t think i'd get away with it
does it matter if the root is S-ON i'm just thinking off my chances
PM sent, I can fix hard bricked Legends with JTAG.
Before I state my problem, I'd like to say how I used my phone. I never rooted it, I never downloaded any apps that I didn't trust and I always kept a good maintenance on my phone. I do have a 16 gb micro sd on the phone, different from what the manufacturer gave which was a 8 gb micro sd.
One day, I woke up and noticed my phones alarm didn't go off, it was just stuck on the bootscreen where it said mytouch 4g. I tried letting the battery drain and recharging it and repeating that a few times and nothing happened. I held my phones volume down and press the power button and pressed recovery and the hard reset option to no avail. I found out I was missing this img.zip file so I formatted my 16gb microsd and put the zip in the root. I pressed the down volume and power again and it begin loading the zip and it asked me to start the update by pressing the up volume, which I did. Now this is what shows up on my phone.
Parsing...[SD ZIP]
[1]BOOTLOADER - FAIL-PU
[2]BOOT - FAIL-PU
[3]RECOVER - FAIL-PU
[4]SYSTEM - FAIL-PU
[5]USERDATA - FAIL-PU
[6]SPLASH1 - FAIL-PU
[7]TP
[8]TP - BYPASSED
[9]RADIO_V2 - UPDATING
[10]RADIO_CUST
At number nine, I'm pretty sure the phone freezes because it's stayed like that for 30 minutes. Is there anything I can do or is my phone done?
I don't know what it could be cause I only used the in market apps and used it for calling, I never rooted it and I always had it protected in my cover.
How many more people will ask this...
Fail-PU = phone dead. Completely dead, no chance of recovery whatsoever.
Seriously Jack? It is his first post and he never rooted his phone. If you do a search for fail PU all you get is returns that deal with rooting and flashing, so I don't know why his question upset you so much.
But yes, your phone is dead.
possible solution
this might work.... since you like your phone unrooted and it is stock.... your local t-mobile store has the update to the mt4g on an sd card.... take it to your local t-mobile store with your phone fully charged.... let them know your situation... let them do the update.... if it does not work.... they should set you up with a warranty replacement with gingerbread... cheers!
I just wanted to thank everyone for their help. I had noticed only one other thread saying just "you're done" about the fail-pu thing when I searched mytouch 4g fail-pu which is why I made a thread about my phone, I wasn't 100% sure if my phone was bricked or not. I'm going to go to tmobile tomorrow and ask them if they can repair it or get it replaced, if not, I'll try contacting HTC (I think that's the company that made the phone) and ask if they can do anything for me. Again, thanks for all the help =].
Your thread, together with another couple of threads, inspired me to make a troubleshooting guide for MT4G.
The guide is in Troubleshooting section in Glacier Wiki, link in my signature.
Question
so what exactly causes this because just had the same problem?
Chuck_McFly said:
so what exactly causes this because just had the same problem?
Click to expand...
Click to collapse
the cause of Fail-PU is because the eMMC chip has died, meaning you cannot write anything to the phone anymore. as of now, there is no way of fixing it. if you know adb and adb can see your device, look up the eMMC serial and it should turn out as M4G2DE.
twitpicdotcom/79n6vs
I got the same thing.
Same problem
I have same problem.
so what is the solution.? is it bricked ?
hey guys what is the real time solution for fail-pu problem on my touch 4g,
"phone is dead is not a solution".
Then we have no solution for you. It's a paperweight. Telling us the phone is dead is not a solution doesn't magically bring it back to life. If the eMMC fails, you have no access to the partitions in which the data resides that makes the phone useful. Sorry.
Sent from my HTC Glacier using xda app-developers app
Upgrade time? Warranty exchange? Or send it in to htc for repair...just make sure they can't tell you are rooted or you will pay more than what is worth
Hi guys,
Tried searching for my problem, but though I found some similar stuff, noone had quite my problem.
I was checking my Nexus S after a trip and it was with the 'emergency only' message. This sometimes happens to me, not sure if it's due to the roaming activation or caused by a bug where the radio subsystem crashes after a long period without network.
Anyway, I proceeded to my common solution: Turn off and reboot.
Except that after the phone was off, it would not turn on.
It doesn't even vibrate. It doesn't show anything when connected to the wall socket or to the computer. It's just completely dead.
Now, I'm not even sure if this is a hardware or software problem. Any idea on how I can debug this?
Here's what I've tried:
1. Take the battery out: no changes (even tried leaving it out overnight).
2. Charge the phone overnight: no change.
Next step: I'll go to a store and try a different battery... meanwhile I'm without my primary phone which sucks... Can anyone help?
Thanks in advance!
Try booting your phone into the bootloader. Hold the power button and volume up button simultaneously.
If it is not the battery, i can see what else you can do, a "dont turn on" phone is a dead end...
Sent from my Nexus S using XDA App
Guess I'm screwed... I had some pics and other data there... anyway I can get it back? i.e. is there a way to remove the internal sd card?
saranyan said:
Try booting your phone into the bootloader. Hold the power button and volume up button simultaneously.
Click to expand...
Click to collapse
Was this tried? Cause if that works there's hope for you yet.
BlackHawkA4 said:
Was this tried? Cause if that works there's hope for you yet.
Click to expand...
Click to collapse
Yup, it was one of the first things I tried. No sign of life... I can't get a single sign that the phone is even being powered. It's like the battery was taken out.
nunocordeiro said:
Yup, it was one of the first things I tried. No sign of life... I can't get a single sign that the phone is even being powered. It's like the battery was taken out.
Click to expand...
Click to collapse
Sounds like something is wrong with the hardware then. Have you brought it the store? Might need to get a new one on warranty.
I have the same issue with my old Blackberry 9000. It worked fine up until I stopped using it. Left it in a drawer for a few months. Went to sell it to Sprint. Wouldn't turn on. No LED, no nothing. Worked fine months before when I was still using it. To this day I have no idea what's wrong with it and it doesn't turn on.
Why not get an external battery charger and charge the battery up and then test it?
All true, and after trying with a new battery I'll have a bit more information.
But what strikes me as odd is that I didn't leave it in a drawer - I didn't even let the battery run down... it was just a damn reboot! I shut it down, and then couldn't power it up again (try and imagine THAT happening to you). It would be odd for the battery to be sucked dry all of a sudden...
I have a feeling that there's something else... maybe while shutting down something burned out in the power circuitry....? =S
No one ever heard of anything like what I'm experiencing? It sucks to be the only one!
Thanks for all the help so far, guys!
If you can get to download mode nothing is lost. Just flash new image via Odin.
Sent from my GT-I9000 using Tapatalk
nunocordeiro said:
All true, and after trying with a new battery I'll have a bit more information.
But what strikes me as odd is that I didn't leave it in a drawer - I didn't even let the battery run down... it was just a damn reboot! I shut it down, and then couldn't power it up again (try and imagine THAT happening to you). It would be odd for the battery to be sucked dry all of a sudden...
I have a feeling that there's something else... maybe while shutting down something burned out in the power circuitry....? =S
No one ever heard of anything like what I'm experiencing? It sucks to be the only one!
Thanks for all the help so far, guys!
Click to expand...
Click to collapse
Never heard of that happening, but it's a possibility... Still, I would first attribute it to a bad battery and try that first
Sent from my Nexus S 4G
With a new battery (that works on another nexus S) still no luck. =(
I still can't find anyone with this problem. I feel like the unluckiest idiot on Earth.
I assume I can't get to download mode since I can't even get the phone to report it is charging (it used to do that even if off). Do you want me to try anything, though? I'm open to suggestions until Monday. Then I'm taking it to Samsung. Hope they can recover my pictures.
BTW, my receipt doesn't have the IMEI and a customer service rep told me I need it on the receipt or they won't give me free support. How can I get it with the phone off?
Regards and thanks to all who responded,
Nuno
nuno, if you cant power on even with a new charged battery, then it's a harware fault and nothing can me done... =o\
but thanks for the advice, i never thought about the data in sd card, i guess i should make some backups! =o)
nun
BTW said:
Look under your battery. IMEI should be printed on the sticker beneath. Good luck!
Click to expand...
Click to collapse
I've got the same problem: dead nexus s after a reboot. It says "no service" emergency call does not work. I tried pretty much everything like switching the battery, recovery mode, plug it in, etc. I even updated its image to the latest I've got access to. No luck. I'm already contacting samsung to get it replaced.
odd things can happen ... it sucks
igorgatis said:
I've got the same problem: dead nexus s after a reboot. It says "no service" emergency call does not work. I tried pretty much everything like switching the battery, recovery mode, plug it in, etc. I even updated its image to the latest I've got access to. No luck. I'm already contacting samsung to get it replaced.
Click to expand...
Click to collapse
Did you try flashing a different rom? Or radio/
I haven't experienced this myself but I'm very interested on what happened. Did you guys flash any custom ROMS? or Radios for that matter?
This looks very similar to what i have. I just got my nexus s GT-i9023, it doesn't boot into fast boot, recovery, download mode or normal. The most activity i have got so fare is when i take the battery out, put it back it, and try turn the phone on it will sometimes flash then do nothing. I have looked every ware. When i use "./platform-tools/adb get-state" it returns "unknown". Any help would be great.
What i think i did was this:
- Unlocked bootloader, this worked
- restart
- installed clockwork mod with fast boot, this worked
- wiped data
- wiped cache (correct me if i spelt that wrong, or anything else)
- flashed cyanogenmod, this got an error but i didn't notice it the first time and i can't remember what it was.
- flashed gapps, this didn't work, when i restarted the phone it said that the installer for gaps had quit.
- restarted
- flashed cyanogenmod again, this is when i noticed the error
- restarted, didn't change anything
- wiped data
- wiped cache
- flashed i9020t recovery, this http://forum.xda-developers.com/showthread.php?t=1061855 i think this is what stuffed it up because my phone is i9023
- wiped data after flashing, thats what it said to do, i thought it was strange but i went along with it.
- wiped cache
- reboot
- now doesnt work.
Take it to the store where you purchased and claim ignorance!
I recently received a used epic 4g when a friend replaced his phone, all was good but then yesterday the phone froze. I took the battery out and powered it back on it then took a long time to boot (2 minutes+) and once it finally did boot it was unusable and very unresponsive. I looked online and got into restore mode and then encountered a problem, my buttons at the bottom don't work therefore I could not hit the home button to select an option.
So I then used Odin to restore it (Used stock stuff). After I restored it it was working fine again. Then today i dropped it 2 feet off my bed and it went back to booting slow and then being unresponsive once booted. I then tried to restore it with Odin again but I made a mistake and didn't put the PDA file in and now my phone seems to be hard bricked (noob move I know).
I am considering sending it in for JTAG but I have some questions. Do you guys think the SLOW booting and unresponsive once booted issues were hardware issues? Will it just do that again eventually after I pay for it to be JTAG fixed? Also do you think they would be able to fix the buttons at the bottom? I would appreciate any advice.
Also please don't kick me when I am down, I know not double checking my Odin stuff was a dumb move, that's not what this thread is about.
So to just be sure, you can't power it on at all? The slow booting seems like a ROM problem. If you can get into Download mode you can fix it. If not, then you are definitely bricked and need to take it in.
If you could though, just reodin the proper files WITHOUT rushing.
I've dropped my phone everyday (I've even found out gorilla glass is ass since it cracked) but its always booted unless I did some dumb **** to it.
Sent from my SPH-D700 using xda premium
A_Flying_Fox said:
So to just be sure, you can't power it on at all? The slow booting seems like a ROM problem. If you can get into Download mode you can fix it. If not, then you are definitely bricked and need to take it in.
If you could though, just reodin the proper files WITHOUT rushing.
I've dropped my phone everyday (I've even found out gorilla glass is ass since it cracked) but its always booted unless I did some dumb **** to it.
Sent from my SPH-D700 using xda premium
Click to expand...
Click to collapse
Thanks for the reply
Correct I can't get it to power on at all. A second opinion on whether or not there was a hardware issue would nice, it just seems odd to me that the exact same thing would happen again a day later. When I bricked it I accidentally only used a pit file. When I did it right the first time I followed a guide and had a pit file and a PDA file, I assume one of those is(or includes) the ROM but I don't really know a lot about this stuff. I am considering just selling this one on ebay as-is if you guys think its a hardware issue and getting a new phone but if not I'll send it to be fixed.
JoeCow said:
Thanks for the reply
Correct I can't get it to power on at all. A second opinion on whether or not there was a hardware issue would nice, it just seems odd to me that the exact same thing would happen again a day later. When I bricked it I only had a pit file. When I did it right the first time I followed a guide and had a pit file and a PDA file, I assume one of those is(or includes) the ROM but I don't really know a lot about this stuff. I am considering just selling this one on ebay as-is if you guys think its a hardware issue and getting a new phone but if not I'll send it to be fixed.
Click to expand...
Click to collapse
try removing the battery. then try to get into download mode with it plugged into the computer only no battery also remove sd card.
tazfanatic said:
try removing the battery. then try to get into download mode with it plugged into the computer only no battery also remove sd card.
Click to expand...
Click to collapse
Thanks!! that did it. I had actually already tried that but tried it again when you suggested it I couldn't get it initially but kept trying and eventually tried unplugging it and plugging it back in while holding one and power the whole time and that got it. So was the slow boot thing happening twice just unlucky or is there something else I need to root or whatever?
JoeCow said:
Thanks!! that did it. I had actually already tried that but tried it again when you suggested it I couldn't get it initially but kept trying and eventually tried unplugging it and plugging it back in while holding one and power the whole time and that got it. So was the slow boot thing happening twice just unlucky or is there something else I need to root or whatever?
Click to expand...
Click to collapse
My guess is the slow booting was data corruption. A clean install should fix that. After Odining in the stock EL30 run it like that for a few days to see how it is working before looking into rooting it and a custom ROM.
Sent from my SPH-D700 using xda premium
kennyglass123 said:
My guess is the slow booting was data corruption. A clean install should fix that. After Odining in the stock EL30 run it like that for a few days to see how it is working before looking into rooting it and a custom ROM.
Sent from my SPH-D700 using xda premium
Click to expand...
Click to collapse
what kenny said
Thanks guys, saved me $50s should i have sent it in. I appreciate it. I watched a few of the videos on rooting it and I saw the recovery program used to root things lets you use the camera button as apposed to the home button for selecting things. Think I should switch to that since my bottom buttons are broken? It looked like I probably wouldn't be able to navigate back in menus after selecting something but that would be better then not being able to select anything.
JoeCow said:
Thanks guys, saved me $50s should i have sent it in. I appreciate it. I watched a few of the videos on rooting it and I saw the recovery program used to root things lets you use the camera button as apposed to the home button for selecting things. Think I should switch to that since my bottom buttons are broken? It looked like I probably wouldn't be able to navigate back in menus after selecting something but that would be better then not being able to select anything.
Click to expand...
Click to collapse
If they are still broken after a fresh Odin then yes the newer CWM will work fine for you. There are widgets somewhere (don't remember) to add those buttions to your screen once you get it working right.
If the buttons really are toasted there are two fairly good onscreen button apps available. One is called Zmooth and the other is called Button Savior.