Related
Hello all,
I have recently upgraded from my g1 to an HD2. HD2 is a great phone but still miss android . Anyways, today I wanted to get my g1 to work without a sim or data plan and was about to start working on it when my g1 screen dimmed to just the blacklight with a black screen. I turned it off and tried turning it back on but it just comes up with the backlight on a black screen. It does not even get to the G1 screen. I cannot get to recovery mode or any other mode for that matter. I have searched around but not found any real solution to this problem (if there is one). I am thinking my phone is bricked but have heard possibilities using ADB. I have never used ADB before and if anyone knows if this is a possible fix to my problem that would be great. It would be nice to know if it actually could fix my problem before looking into it and learning it all while finding out it has no chance of fixing my problem. I have tried using my sim card and a different sd card so those are not causing the problems.
So the background of what I am running on my g1. Right before I got my HD2 I was using Cyanogen version 4.2.14.1 with and ext 3. I had no problems with it until now. I got my HD2 a week ago and my g1 has been on about twice in that time without a sim card just for comparing purposes to the HD2. Then just today (about 2-3 days since I last turned it on) the screen just went black and I had my problems. I cannot return my phone because it has been over a year and I dont have insurance on the phone so these are not possibilities for me unfortunately. I also don't really want to get parts from other g1's and take apart and put my g1 back together. I am just looking for something with ADB or any other possible solution to the problem (if one exists).
Any help would be greatly appreciated!
I had this happen to me before. Apparently, it was a hardware GPU problem that would cause a boot loop because it couldn't draw anything on the screen. This happened on SuperD, AOSP, Cyanogen, and stock Donut.
If your problem is the same, you should be able to get into recovery, regardless of your ability to see what you're doing. Easy way of telling is to hit Camera+End on boot. If it doesn't vibrate, you're able to flash still. You may be able to get the screen back temporarily by either pulling the battery or letting the battery die and recharging.
Anyways, I ended up flashing the DREAIMG.nbh, and trying to upgrade back to 1.6 to remove traces of hacking. (Be careful if you have DangerSPL, you want to restore the default before flashing DREAIMG.nbh) I eventually got the screen working on 1.6, but it died again, so I sent it in to T-Mobile and got a replacement. I'm now using AOSP with no problems.
One small note, however, I did start having my problems using Cyanogen's mod. May want to bring it up with him?
Sorry if this sounds scatterbrained, it's a bit late and I should be asleep right now.
e:Just realized you said the warranty was void. You may be able to get something out of what I did, though? Good luck, in any case.
Thanks very much for the help even though it was really late. I did understand pretty much everything you said and I tried the camera plus power button and it didn't vibrate so it should mean I probably can flash things still. I have drained the battery and am charging it back up to see if that helped.
I have a friend who knows ADB so I am going to have him look at it to see if we can't get it working through there. Also the G1 screen has been popping up but then fading right when its about to change to the boot animation. So we will see how things go and I'll try a couple different things and report back if anything seems to work or open up more possibilities.
Thanks again for your information.
Ok, so my friend and I were going to flash a rom through fastboot. It was responding and such so we knew we were able to get it in there.
Anyone know what the command to flash a rom in fastboot is and if there are specific instructions to follow?
Any help would be greatly appreciated!
coolookoo said:
Ok, so my friend and I were going to flash a rom through fastboot. It was responding and such so we knew we were able to get it in there.
Anyone know what the command to flash a rom in fastboot is and if there are specific instructions to follow?
Any help would be greatly appreciated!
Click to expand...
Click to collapse
google it. i did and got about 100 links telling me how to do it. "unroot g1 with fastboot."
sorry i have the same problem, but my g1 is not rooted nor has it been flashed before, my friend messed it up somehow? wen i turn it on all there is is a blank highlighted black screen. What do yall suggest i should do
r3s-rt said:
google it. i did and got about 100 links telling me how to do it. "unroot g1 with fastboot."
Click to expand...
Click to collapse
First of all we are not trying to unroot the phone just flash another rom
Secondly we already tried your "fantastic" method of using google before coming to the forums
Ok I think I just bricked my G1
I was following the steps on theunlockr.com and was following the steps to the T like I always do.
The problem incurred after flashing the spl. I flashed the correct radio then ir rebooted and went back into recovery mode. Then I flashed the spl all seemed well home+back and never rebooted. It stayed on a black screen for over 30 mins. So I took out the battery and waited a few mins and put battery back in and same thing. Just a black screen nothing I can do. I have tried holding home+power and camera+power and back+power nothing. I am stuck have looked it up and this is the best forum I have found to post in.
Any input would be great.
thanks
nate
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]
Was updating using Odin when, as my luck always proves out, a circuit breaker tripped and cut power to my PC. The phone seemed to be frozen on the "Download Mode" screen (30+ minutes of zero activity) so I pulled the battery. Upon reinserting the battery I discover that the phone is 100% unresponsive. I've tried every trick google could produce for me with the exception of the "homemade jig" method as it seemed fairly clear that the phone needed some semblance of life for that to be effective.
So, my question is... WTF??? I've soft modded wiis, hard modded xboxes, hacked PSPs flashed hundreds of phones and generally revel in futzing around in this manner of endeavor and have NEVER bricked a device (even after some incredibly stupid mistakes). This just doesn't make sense and I haven't seen sysmptoms such as mine presented in any of my web searches. Any ideas???
I'm not saying your not a modder, but you should know to have a UPS hooked up to your dev box, for me its a laptop, so...
Anyway, try removing the battery for 1m, press power button with batt removed, now start up Odin, plug the phone in (batt removed still) and see if the phone connects. I'm sure someone will pop in here and provide links to several threads that describe different methods to help you fix this, I would but I'm sorta busy...
Help support autism awareness,it only takes 2 seconds to help make a difference...
http://picketfenceblogs.com/vote/3616
Sent from MyEF02 using XDAPA...
Keep the battery out for like a half hour and then try again. That has worked for some people.
Or try the mysterious button that may or may not exist. I know I'd be pushing the heck out of it just in case.
Thank you so much for your quick input... I tried precicely that 3-4 times (google search turned it up) and it was a futile endeavor.
And yes, I am fully aware of all the proper precautions to take, unfortunately I am also fully stupid with frightening regularity (well, maybe just lazy and reckless), I seem to have become a tad cocky as I have never really had to face disaster before today.
It won't happen again!
plug phone into computer without battery. Then hold power and 1 to go into download mode (still no battery)
That there is what I've seen as most effective thing to work on bricked phone's.
cool... I just popped out the battery and will let you know the result in about 40 minutes...
this happened to me recently, i found a post with the solution being to pull the battery out of the phone hold down 1 and the power button at the same time before popping the battery back in and it will send you to the proper screen to odin back to what you need, worked perfect for me
oh crap I editted my previous post. i forgot to mention go into download mode...
It's --
Remove battery and plug into computer. then go into download mode WITHOUT Battery still.
If your not getting any sign of life from ur phone, try this:
http://forum.xda-developers.com/showthread.php?t=1042746
It worked for me.
Krojian said:
If your not getting any sign of life from ur phone, try this:
http://forum.xda-developers.com/showthread.php?t=1042746
It worked for me.
Click to expand...
Click to collapse
there is no hole in the back case of my device. I've had my device powered on and bent the **** out of a paper clip trying to push the 'hidden magic button' to no avail.
YMMV (false hope ??)
Cool, didn't know that little button existed!
I bricked mine the same way a few weeks ago and tried every trick in the book over the course of 2 days. It was truly bricked. I don't have insurance; however, my phone was under warranty. Since I couldn't get the phone to boot or anything I figured there was no real way of telling what went wrong. I sent it in for warranty repair and 10 days later, the phone returned in working order. Work order says they replaced the main board. I marked the phone before returning it so I know its the same phone and it works fine now.
And before anyone says anything, I know, I'm an evil bastard. But I figure it's payback for a samsung flatscreen that died 6 months out of warranty.
I've done this, leaving my battery out for 20 mins or so, and leaving it out while going into download mode worked for me. I don't know why but sometimes I can't even get into download mode with my battery in.
keeepinitgansta said:
Cool, didn't know that little button existed!
Click to expand...
Click to collapse
it doesn't..
to prove this (or dis-prove it).. go into clockwork and make a nandroid backup (you know, just in case)...then boot normally and while you're looking at your home screen, jam a paper clip in there as hard as you can. Your device will do nothing.
daddymikey1975 said:
it doesn't..
to prove this (or dis-prove it).. go into clockwork and make a nandroid backup (you know, just in case)...then boot normally and while you're looking at your home screen, jam a paper clip in there as hard as you can. Your device will do nothing.
Click to expand...
Click to collapse
I hope you guys are messing with him...
hardrock121 said:
I hope you guys are messing with him...
Click to expand...
Click to collapse
No, it's just not proven. Some people swear by it, some say it's a myth and some say it depends on when your phone was made.
Sent from Godot's place.
So basically i Started Installing roms for like 4 months now, i started the rooting process using this guy's "Mackster248" method, witch was the gfree shown here: youtube.com/watch?v=c4B4y0CQUDo[/url]. I never tried anything more complicated than this aside from installing the genius button with required the need to use button shortcut app.
I've tried a few roms like VU 1.29. and a Vdoubleshoot one witch i hated. I loved vu 1.29.0 but i felt something was missing, so i tried the DARKSIDE Runny v2.1.0 first but found out that the voice recognition in the genius did not work, so i updated to 2.2.0. witch did work with the easy genius fix....Sooo I Loved it & decided to stay with it for good regardless of the ffc issue. So after reinstalling all my apps again i noticed that my power button would not lock and turn off the screen, I thought it was the button cause i had a problem with it being hard and sticking, so on the lock screen i "pulled the battery" yes after now reading in some forums I'm seeing that's a Big NO NO!
After trying to power on i get a Black screen of death where the black light turns on when pressing on the home screen only when the charger is plugged in so yes i am aware that I'm bricked but my question is why? This also happened to my friends "UNROOTED" mytouch 4g, when he was downloading something from the market the froze on him so i pulled the battery out and upon rebooting it was stuck on a line of androids. When sent to HTC they said it was the emmc chip.
So a some questions i have are, 1: Do these phone brick regardless of rooted or not? 2nd: Is pulling the battery out really so dangerous? if so what to do in my 2 scenarios? After i realized my phone was bricked i was thinking i should of used clockward mod before turning it off, but would that had made a difference? Ohh well i already know that HTC repairs rooted phones based on whats been posted in these forums so I'm not worried and i have already my shipped my phone...hopefully it wont take too long to replace that eMMc. Thanks for reading me out!
Maybe change the title of your thread... Your phone was bricked because you installed the Rom...
How r people getting the FFC to work with stock camera
wanabdev said:
So basically i Started Installing roms for like 4 months now, i started the rooting process using this guy's "Mackster248" method, witch was the gfree shown here: youtube.com/watch?v=c4B4y0CQUDo[/url]. I never tried anything more complicated than this aside from installing the genius button with required the need to use button shortcut app.
I've tried a few roms like VU 1.29. and a Vdoubleshoot one witch i hated. I loved vu 1.29.0 but i felt something was missing, so i tried the DARKSIDE Runny v2.1.0 first but found out that the voice recognition in the genius did not work, so i updated to 2.2.0. witch did work with the easy genius fix....Sooo I Loved it & decided to stay with it for good regardless of the ffc issue. So after reinstalling all my apps again i noticed that my power button would not lock and turn off the screen, I thought it was the button cause i had a problem with it being hard and sticking, so on the lock screen i "pulled the battery" yes after now reading in some forums I'm seeing that's a Big NO NO!
After trying to power on i get a Black screen of death where the black light turns on when pressing on the home screen only when the charger is plugged in so yes i am aware that I'm bricked but my question is why? This also happened to my friends "UNROOTED" mytouch 4g, when he was downloading something from the market the froze on him so i pulled the battery out and upon rebooting it was stuck on a line of androids. When sent to HTC they said it was the emmc chip.
So a some questions i have are, 1: Do these phone brick regardless of rooted or not? 2nd: Is pulling the battery out really so dangerous? if so what to do in my 2 scenarios? After i realized my phone was bricked i was thinking i should of used clockward mod before turning it off, but would that had made a difference? Ohh well i already know that HTC repairs rooted phones based on whats been posted in these forums so I'm not worried and i have already my shipped my phone...hopefully it wont take too long to replace that eMMc. Thanks for reading me out!
Click to expand...
Click to collapse
1. I have yet to hear of a non-rooted phone bricking because of the bad eMMc chip, only after you root it does the chip start acting funny. could have been a possibility that you had the bad eMMc, did you check to see before taking the plunge and rooting your phone?(guessing not lol )
2. pulling the battery isnt as dangerous as everyone says it is. its only dangerous if you pull it while trying to flash the stock PD15IMG to return to stock, or during the phones booting process where its loading everything up. Ive pulled my battery plenty of times, but never in those situations.
Maybe hope
Out of curiosity are you able to get into the bootloader to run fastboot at all by holding down the power and the down volume on your phone? If so you could probably flash clockworkmod onto your phone again through fastboot and reflash a new rom.
If you're able to do this you could save your phone
macblaxter said:
Out of curiosity are you able to get into the bootloader to run fastboot at all by holding down the power and the down volume on your phone? If so you could probably flash clockworkmod onto your phone again through fastboot and reflash a new rom.
If you're able to do this you could save your phone
Click to expand...
Click to collapse
DING DING DING we have ourselves a winner.
[OP] are you able to get into the bootloader or recovery?
I remember when I first started rooting my phone it would be titles like this that would scare me away form certain roms. Which is a good and bad thing. Although I would generalize the title a little. Like " dam i messed up installing a sense rom" this way it's a little more inviting to open minded people that want to help and less offending to people that put in time for tutorials and development
Sent using XDA App
aznprodgy said:
1. I have yet to hear of a non-rooted phone bricking because of the bad eMMc chip, only after you root it does the chip start acting funny. could have been a possibility that you had the bad eMMc, did you check to see before taking the plunge and rooting your phone?(guessing not lol )
Click to expand...
Click to collapse
Wrong. To hear this (or actually, to see this), you only need to go to the eMMC thread in General section, and look at the poll. You'll see enough failed non-rooted "bad" eMMCs, and you'll also see some "good" eMMC chips fail, even non-rooted. If you were reading the forum for the last 1/2 year, you'd hear more than enough of stock phones dying with failed eMMC. You can just try searching and reading the threads.
Moreover, you're wrong about the dangers of battery pull too. The danger isn't only when you're writing to sensitive partitions. It's a bit complicated, but I'll try to explain:
When the power is turned off, it doesn't go out at once - it takes a bit of time, several microseconds, maybe less, maybe more, depends on the capacitance of the supply path. During that time the electronic circuits still act, but with gradually diminishing voltage.
Circuits are built to function reliably in certain voltage range. The thing is that under that range, they don't stop functioning immediately - there is a range where they still function, but unreliably. Signals can receive erroneous values that aren't determined by the logic.
During that unreliable functionality period, a sequence of signals might happen that will cause overwriting one of the system partitions in the eMMC - since the logic doesn't function reliably, it can happen. If the phone is currently writing to eMMC (which might easily happen - programs read and write data when they run), you only need a couple of bits to fail in the bus address and write protection mechanism. The probability is very low and there are protections against that, but still, they aren't 100%.
If it happens, the phone is dead.
To add to that, there could be physical effects on eMMC chip from uncontrolled voltage drop.
So, this is why there's a recommendation to avoid pulling the battery, and using it only when really necessary.
Jack_R1 said:
Wrong. To hear this (or actually, to see this), you only need to go to the eMMC thread in General section, and look at the poll. You'll see enough failed non-rooted "bad" eMMCs, and you'll also see some "good" eMMC chips fail, even non-rooted. If you were reading the forum for the last 1/2 year, you'd hear more than enough of stock phones dying with failed eMMC. You can just try searching and reading the threads.
Moreover, you're wrong about the dangers of battery pull too. The danger isn't only when you're writing to sensitive partitions. It's a bit complicated, but I'll try to explain:
When the power is turned off, it doesn't go out at once - it takes a bit of time, several microseconds, maybe less, maybe more, depends on the capacitance of the supply path. During that time the electronic circuits still act, but with gradually diminishing voltage.
Circuits are built to function reliably in certain voltage range. The thing is that under that range, they don't stop functioning immediately - there is a range where they still function, but unreliably. Signals can receive erroneous values that aren't determined by the logic.
During that unreliable functionality period, a sequence of signals might happen that will cause overwriting one of the system partitions in the eMMC - since the logic doesn't function reliably, it can happen. If the phone is currently writing to eMMC (which might easily happen - programs read and write data when they run), you only need a couple of bits to fail in the bus address and write protection mechanism. The probability is very low and there are protections against that, but still, they aren't 100%.
If it happens, the phone is dead.
To add to that, there could be physical effects on eMMC chip from uncontrolled voltage drop.
So, this is why there's a recommendation to avoid pulling the battery, and using it only when really necessary.
Click to expand...
Click to collapse
well damn bro, didnt think it was that serious...
Hey Jack_R1 thanks for the input. I always enjoy getting a snapshot of information to clarify how things work.
wanabdev do you know if you're able to get into the boot loader to get access to fastboot? You really may be able to save your phone if you're still able to do this.
Wi-Fi Calling using Darkside Runny 2.2
Does anyone know how I can resolved my wifi calling issue using this ROM? I've tried about 10 ROMS on my MT4G, and found this to be the nicest. But when I'm on wifi, any calls I make or receive, the person on the other end says they can barely hear me. I can hear them just fine, but they can't. This is also true at multiple hotspots, ie. Starbucks, friends home, etc.
When I flash different ROM, this feature works just fine.
Help!
Chicago T said:
Does anyone know how I can resolved my wifi calling issue using this ROM? I've tried about 10 ROMS on my MT4G, and found this to be the nicest. But when I'm on wifi, any calls I make or receive, the person on the other end says they can barely hear me. I can hear them just fine, but they can't. This is also true at multiple hotspots, ie. Starbucks, friends home, etc.
When I flash different ROM, this feature works just fine.
Help!
Click to expand...
Click to collapse
same here, not rooted. any calls I make or receive, the person on the other end says they can barely hear me. I can hear them just fine, but they can't.
Wi-Fi Calling using Darkside Runny 2.2
glacier1122 said:
same here, not rooted. any calls I make or receive, the person on the other end says they can barely hear me. I can hear them just fine, but they can't.
Click to expand...
Click to collapse
Right, soooooo annoying. There's gotta be a fix out there? I like this ROM the best, it has all the little tweaks that make me happy!
Anyone have any ideas?
Flash the newest version.
http://forum.xda-developers.com/showthread.php?t=1283682
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.