Hello there today my phone stop working all i did was remove the battery and remove the sim card to put a new one in. When i put it back on and turn on the phone, the phone vibrates for three times and the charging led starts blinking ,also the screen is black. I cant even get into bootloader mode anyone knows a fix. I was running Ossymod MIUI and have an engineer boot loader.
Did i mention that this happened because i pull the battery out while phone was on this could be what f*ck it up.
Problem
Phones off --> Hit the on button---> Three Vibrates with black Screen ----> Orange LED Blinking.
Things i tried
Try to get into Fast boot but i only get a black screen with a Green Led while connected to the pc, Device manager detects my mytouch as a "Qualcomm CDMA Technologies MSM".
i thought i posted this on Q&A can some move this to Q&a Section
Me the issue I may br - able to help or post it here mine does that
Sent from my HTC Glacier using XDA Premium App
Does it turn on atall ??
Sent from my HTC Glacier using XDA Premium App
pbedard said:
Me the issue I may br - able to help or post it here mine does that
Sent from my HTC Glacier using XDA Premium App
Click to expand...
Click to collapse
Huh?
Sent from my demonSPEED Glacier using XDA Premium App
thederekjay said:
Huh?
Sent from my demonSPEED Glacier using XDA Premium App
Click to expand...
Click to collapse
At least he tried? To the OP, sounds to me like your battery was probably almost dead before you took it out. Try charging it before you try turning it on again...
battery had 50 percent im trying to get it on fastboot by holding the power and volume down while connected to the pc but all i get is a black screen and in my pc it shows "Qualcomm CDMA Technologies MSM" could this have been cause ,by pulling the battery while the phone was on.
jeff7790 said:
battery had 50 percent im trying to get it on fastboot by holding the power and volume down while connected to the pc but all i get is a black screen and im my pc it shows "Qualcomm CDMA Technologies MSM" could this have been cause ,by pulling the battery while the phone was on.
Click to expand...
Click to collapse
I dnt believe that pullin the battery while the phone is on would cause that issue,ive dropped my phone numerous times while it was on,while playin a game or by just gettin out my car while listenin to music & not once had that issue...
Mytouch 4g-white
Permrooted s-off
Root Method-gfree
CWR-3.0.2.4
Rom-Royalginger v2.1
Kernel-Ckisgen~smartass~v1.2
I cannot figure out how you got to this point, but I think you have a bad radio.
That Qualcomm MSM device is something that I think happens only with the engineering bootloader installed. I believe it could provide a way to access the radio directly, but I have never seen any info on how to do that.
I mistakenly flashed the wrong data to the radio partition while I was trying to reset to factory and since I had the engineering bootloader, I got the same results as you. As a result, mine was effectively bricked and I had to return it to T-mobile like that. This was a couple of months ago and I have not heard anything about it.
G8351427 said:
I cannot figure out how you got to this point, but I think you have a bad radio.
That Qualcomm MSM device is something that I think happens only with the engineering bootloader installed. I believe it could provide a way to access the radio directly, but I have never seen any info on how to do that.
I mistakenly flashed the wrong data to the radio partition while I was trying to reset to factory and since I had the engineering bootloader, I got the same results as you. As a result, mine was effectively bricked and I had to return it to T-mobile like that. This was a couple of months ago and I have not heard anything about it.
Click to expand...
Click to collapse
Ever since I've had this phone i never try to flash radios or beta test radios i always kept it stock . The only thing i flash were Roms and yes i have a engineering bootloader.
I am not saying you did any of those things, I am only telling you how I got to that point and that once there, I had zero luck in recovering.
This happened to me before. I had a full charge and turned off the phone, pulled out the battery, and put it back in. Tried turning it on, it wouldn't. Plugged it in the charger, had the blinking light. I simply googled "amber blinking led mytouch 4g" or something like that. It happens when the phone thinks the battery is really low. So just leave it off, plug in your charger and wait.
ill try that
I am pretty sure that if the radio is bad it will not charge. So if you can charge, then you do not have a bad radio.
I found this thread for the same issue on an HD2. They say a JTAG is required to fix a bad flash on an HD2; may be the same on a Glacier, I don't know.
I am fairly certain that this Qualcomm MSM is the radio itself and if you had the right drivers you could send it commands, though flashing the emmc may not be possible from there.
the device does charge no blinking at all so it might not be a radio ,funny thing this happened without me flashing anything.
Edit: i though it was charging but then 5 minutes later i see a green LED on ,i think the phone turn on while it was charging not sure.
Edit2: Yeah its not charging i plug the phone then it just turns on to a black screen
Thanks for the Help
Can we remove this thread or post it where it is supposed to be? Thanks!
Sent from my HTC Glacier using XDA App
bretjrodgers said:
Can we remove this thread or post it where it is supposed to be? Thanks!
Sent from my HTC Glacier using XDA App
Click to expand...
Click to collapse
dude read the second post i told them to move it ,you dont have to say it twice
i had this happen to me once when i first got this phone. pulled the battery and it started right up. now sure what the cause was tho?
Have u tried takin out the battery,sim card & sd card,leave it out for about 10 min or so & then put everythin bck on & try of it starts that way,a friend of mine called me earlier & sd his phone just shut dwn & wouldnt start & thats what he did & it wrked... He sd he thinks the phone was thinkin the battery was dead & thats what fixed it? Just a thought : )
Mytouch 4g-white
Permrooted s-off
Root Method-gfree
CWR-3.0.2.4
Rom-Royalginger v2.1
Kernel-Ckisgen~smartass~v1.2
bretjrodgers said:
Can we remove this thread or post it where it is supposed to be? Thanks!
Sent from my HTC Glacier using XDA App
Click to expand...
Click to collapse
the above quote is very helpful towards the topic this is why xda is failing as a community based forum
Related
i have to have the worst luck in the world..
got my nexus one today. condition is MINT. seller also included the receipt from HTC proving that it got replaced.
popped in my sim, everything worked fine. turned it off to swap batteries and thats when the hell started.
im not able to get past the nexus logo. NOTHING. it would turn on, than go to the screen, vibrate, than repeat multiple times. phone has never been rooted.
i did EVERYTHING. i did the volume down plus power and than i cleared wiped the memory, same result.
than i tried downloading 2.2.1, renaming it to update.zip, put it on my zip, but that doesnt work. the phone can't tell theres a update.
like **** man. i than went here
http://forum.xda-developers.com/wiki/index.php?title=Nexus_One/Guides_&_Tutorials
read that i needed FRG33 and rename it to PASSIMG.ZIP. when the phone turns on, it gives me the message if i want to update, i get excited. i click yes, everything says ok, than i reboot and bam, still endless reboot. tried to do the passimg again but this time i get a fail on radio V2 or something like that.
WTF is going on. i didnt do anything. ANYBODY HELP?
maybe the battery you swapped in is bad?
same result with both batteries :/
i hate my effing luck.
Make sure your batteries are fully charged, seriously.
great, now when i click recovery, it doesnt even go to the android guy with the exclamation mark, it just gets stuck at the logo. all im able to do is get to hboot. WTF.
i mean the battery has half a charge. just checked with my desire. i even tried with it plugged in in the wall. nothing.
my aim is screwupboy444. your welcome to help me there or even laugh at me for being a bone head and getting in this situation.
Do you have a different SD card you can use?
Sent from my Nexus One using XDA App
yeah, i was using both the desire 8gb and the nexus one 4gb. both were reading fine in the desire. i read that if it gets to the nexus one logo then my phone isn't bricked, but im starting to think otherwise. nothing works.
ive been searching for the past hour half. everyone seemed to have fixed there by doing the passimg method or wiping data. but unfortunately none of that is working. i tried placing the froyo "update.zip" and running it but when i clicked recovery, it went into the boot cycle again.
http://forum.xda-developers.com/showthread.php?t=614850
thinking about doing that but i have a feeling it doesnt apply to me. that and i don't understand any of the process. i dont think my phone will even be read by my comp.
did the passimg for the third time. went past the logo and actually to the set up screen. than it rebooted again. and now its stuck on the nexus one logo again.
could it actually be that? i left the battery charging in the desire for about 40 minutes, than took it out and put it in the nexus one and actually got to the set up screen for the first time.
but my question is, if thats the solution, does that mean my phone is gonna trip out everytime its less than 60 percent battery power?
this is what i get when i put the 2.2.1 update on my sd card and go into recovery mode
Uploaded with ImageShack.us
most of the threads where people got this fixed required them unlocking the bootloader and doing something. im the second owner of the phone but would like to avoid rooting but if its required in this situation, i will. i just need a dummies guide to do it..
No, there's threads for recalibrating the battery, if needed.
Keep it fully charged, and see if it will run for a reasonable period... That way, we can see if it really is the battery...
Sent from my Nexus One using XDA App
Don't worry about the exclamation and Android for now, and see if the phone will boot and run with a fully charged battery...
Sent from my Nexus One using XDA App
frick, i know thats what i should do. it just blows that i got this today and theres already a chance that its trashed...
danger-rat said:
Don't worry about the exclamation and Android for now, and see if the phone will boot and run with a fully charged battery...
Sent from my Nexus One using XDA App
Click to expand...
Click to collapse
thanks for all the help man. you dont think i need to unlock the bootloader right...? im just more curious on why the desire can work with either party no matter the charge. damn.
Wait until your battery is about 75% or more would be better, then try the passimg again...
Sent from my Nexus One using XDA App
not sure if its good news or not but (i apologize for my lack of patient before hand haha), i took out the battery the desire was charging again and put it in the nexus one. it got to the set up screen all three times before it resets again. i tried plugging it in the wall charger but it still resets at that area.
edit:
the battery level was at 74% when i tried it.
75% is not a hard number, and I'd let it charge as much as possible. I'd also quit switching batteries, and just stick with one until you isolate the problem...
Sent from my Nexus One using XDA App
danger-rat said:
75% is not a hard number, and I'd let it charge as much as possible. I'd also quit switching batteries, and just stick with one until you isolate the problem...
Sent from my Nexus One using XDA App
Click to expand...
Click to collapse
oh iam. im charging the nexus one battery in the desire because once i turn on the nexus one, it gets frozen there, and than i cant turn it off.
Before anyone asks why I'm not posting in the development area, I don't have permission cause I don't have ten posts. Anyway, I rooted my myTouch 4G about two months ago and started with CwM recovery 2.5.1.3 and Ice Glacier 1.1.4. Just about a week ago every time I plugged my phone into a computer then unplugged it, it would reboot itself and never get past the white mytouch screen. What it does is go to the screen for a few seconds, then turns black and starts over.
To get it to work, I have to remove the battery and turn it on again. Even that doesn't fix it 100% of the time. I wiped my phone this morning and flashed cyanogen mod 7 rc2 as well as updated the recovery to 3.0.0.5. But it's still doing it?
What do I do? I'm about to throw this thing down the street...
Q&A may have been a better spot to post this.
So everytime you unplug the phone from a computer the phone wants to reboot?
Have you tried using different cables?
and does your phone do this while you are are using a plug in the wall charger?
No, it is not the cable. I've used many different ones and they do the same thing. And no, using a wall charger doesn't affect it whatsoever. It only happens when I plug it into a computer. It also bootloops simply if I turn off/on the phone or reboot it by holding the power button.
Anyone know what's wrong?
FiddleGoose said:
Anyone know what's wrong?
Click to expand...
Click to collapse
If it were my phone i would check a different computer. If it still happens i would flash the PD15IMG and restore everything to stock. If it still happens i would exchange the handset.
to me honestly it sounds like a malfunction in the PC drivers since it's doing it when you unplug the phone. but then if it's doing it away from the PC it may be the phone itself. It might just be a defective phone.
Any computer does it, even the Xbox 360 and ps3, since plugging the phone into them enables disk mounting. I'm going to try formatting my SD card, I hope its not my handset.
I don't think the sdcard will do anything if it happens when you try to power off or reboot the phone. I would try the PD15 image, that way you have a common point of reference. If it happens after that, you know its hardware.
This sounds like hardware to me.
option94 said:
This sounds like hardware to me.
Click to expand...
Click to collapse
What about bad recovery? Maybe installing incorrectly or somethin.
Sent from my glacier using XDA Premium App
Nicgraner said:
What about bad recovery? Maybe installing incorrectly or somethin.
Sent from my glacier using XDA Premium App
Click to expand...
Click to collapse
Doubtful. Phone resetting when being removed from a power source screams hardware fault to me. Of course I could be wrong. Im not perfect or all knowing. Just sounds like hardware.
option94 said:
Doubtful. Phone resetting when being removed from a power source screams hardware fault to me. Of course I could be wrong. Im not perfect or all knowing. Just sounds like hardware.
Click to expand...
Click to collapse
Well you are indeed a forum ninja lol and you know worlds more than I do.
Sent from my glacier using XDA Premium App
Thank you everyone for all your input. I will troubleshoot the situation!
This is a warning to everyone who is running VisionKernel v1.2 by ACS.
I highly recommend you rollback to v1.1 immediately. Several people have wound up with bricked phones using this new kernel version (completely unrelated to overclocking). It appears the source may be RAM corruption due to the UV added in this new release. I am unfortunate enough to be one of the people with a bricked phone, if anyone knows a way to come back from this problem please post here. My screen is cracked and being that sprint changed the cracked screen policy BACK I can't get my phone replaced .
NOTE: It appears that MANY users are suffering from this issue and haven't realized it yet (because they haven't yet shut their phone down). If you reboot to flash another kernel, please know you may suffer from this problem so do so at your own risk. This is extremely unfortunate as this means there's no way to prevent the problem from getting worse.
ok..hmmm..so I saw this thread and decided to power off my phone and go back to genocide since visionkernal has been acting weird here and there anyways..so i power off my phone and now it doesn't turn on lol
DO NOT PANIC AND POWER OFF/REBOOT THE PHONE OR YOU MIGHT BRICK!!! WAIT TILL A SAFE METHOD TO TURN YOUR PHONE OFF IS CONFIRMED!!!
If YOU ALREADY BRICKED, POST IN HERE:
http://forum.xda-developers.com/showthread.php?t=1043240
--
SO FAR THE FOLLOWING METHODS WERE CONFIRMED TO BRICK:
Power down/Reboot via menu
Battery pull
BRICK DOES NOT HAPPEN FOR EVERYONE, AND MAY HAPPEN AFTER TIME BUT IF IT DOES HAPPEN TO YOU ITS A PERMA BRICK
I work for sprint, If you don't have insurance and the screen is cracked take it to a tech center and they will fix it for $35. If it is a larger crack than 2 inches they might give you some hassle just haggle with them or go to a different store cause my store does it no problem
Sent from my harmonious Bonsai 4.0.1 tree
trobertson said:
This is a warning to everyone who is running VisionKernel v1.2 by ACS.
I highly recommend you rollback to v1.1 immediately. Several people have wound up with bricked phones using this new kernel version (completely unrelated to overclocking). It appears the source may be RAM corruption due to the UV added in this new release. I am unfortunate enough to be one of the people with a bricked phone, if anyone knows a way to come back from this problem please post here. My screen is cracked and being that sprint changed the cracked screen policy BACK I can't get my phone replaced .
Click to expand...
Click to collapse
If this **** happened to me id be highly pissed...literally...did you have any symptoms before this happened?
Sent from my SPH-D700 using XDA Premium App
Custodian said:
If this **** happened to me id be highly pissed...literally...did you have any symptoms before this happened?
Sent from my SPH-D700 using XDA Premium App
Click to expand...
Click to collapse
For me what I noticed was phone randomly shut off at night even though it was stable all day long...
The battery was good...like lost 3-5% in 7 hours of idling and stuff..then when I turned it on after it crashed it instantly lost 50% battery.
You can't get your phone replaced for problems unrelated to cracked screens???
I was actually hoping to brick my phone some day
Dude, WTF!
My phone has acs rom 1.1 and visionkernel 1.2. It started hanging on me so I held down the power button and pressed reboot. Now it wont turn on, and it won't charge either! WTF I AM SO ANGRY RIGHT NOW. IT WAS JUST FINE.
Finally I'm not alone.. I had this issue as well and fixed it by pulling my sd card and battery out a few times and then pressing the power button. After I finally got the phone back on I had to odin back to eclair. Hope this helps...
Note: I also formatted my sdcard. Because just pulling the battery didn't work. So I suspect something on the sdcard was making the phone not turn on..
Hmm..,maybe powering off is the cause of the issue..hmm..I think its safer maybe to crash the phone rather then turning it off/rebooting it then reflash another kernal..
I had an issue flashing 1.2 also. Got stuck at a boot loop after first installing, had to do a battery pull that corrupted everything. None of my back up works so I had to start fresh with eb13 then flash the ec05 modem and then flash my backup after all of that. Glad I had a back up but still a bit of run around having to odin first.
I flashed another kernel and the same thing still happend to me -- phone would shutdown and not power on. Odin back to eclair and formatting the sdcard was the only thing that fixed it for me atleast.
cerchiara said:
I flashed another kernel and the same thing still happend to me -- phone would shutdown and not power on. Odin back to eclair and formatting the sdcard was the only thing that fixed it for me atleast.
Click to expand...
Click to collapse
which kernel? also I tried with taking out the sd card altogether and putting in a new one..didn't work....
it has been working fine for me and I only used Voltage and overclocked only to 1300. What applications are you guys using to set your speeds/governor?
Isnt this two kernals in two weeks causing perm bricks? Isnt that kinda rare? Is the EPIC that much of a pain does or does this happen much on other platforms? BTW this is NOT any kind of complaint against our devs they are busting their ass's for some free coffee/beer money just seems odd to have some really bad failures that are not from people being tards flashing
To those others that may be affected by this problem, is your phone charging? Does the red light come on when you plug your phone in?
quik99 said:
Isnt this two kernals in two weeks causing perm bricks? Isnt that kinda rare? Is the EPIC that much of a pain does or does this happen much on other platforms? BTW this is NOT any kind of complaint against our devs they are busting their ass's for some free coffee/beer money just seems odd to have some really bad failures that are not from people being tards flashing
Click to expand...
Click to collapse
Well bricks happen..its nothing new..mostly when experimenting with things...
What other kernel was causing perma bricks?
fhurricane said:
To those others that may be affected by this problem, is your phone charging? Does the red light come on when you plug your phone in?
Click to expand...
Click to collapse
nope, my phone didnt charge, tried it already
I think I just joined
I think I've just joined the brick club. Running SRF & vision 1.2 kernel. Turned my phone off today, won't turn on.
Light does not turn on when plugged in, tried two different full batteries, can't even turn it on to get to recovery or download mode.
hussmanne said:
I think I've just joined the brick club. Running SRF & vision 1.2 kernel. Turned my phone off today, won't turn on.
Click to expand...
Click to collapse
you did "power off" or "reboot" via menu right?
if so can op update the OP telling people NOT to power off their phones! cause thsi thread make get more people to brick their phones as is...it made me break mine lol
I think I chose power off from menu, I remember the phone vibrating faster than usual before turning off. Twas its last breathe.
I got the phone just 3 days ago from an insurance claim, had no problems with it other than the power button is a pain sometimes.
I rooted the phone yesterday with visionary at first, then gfree after i got the s-off, and I have the CWM 5.8 touch recovery. I then flashed Virtuous Unity 2.39 and the Darkside v12 kernel, as well as all sorts of different radio's. I then fell asleep after installing those, and before setting up the ROM, and i left it charging on my computer overnight.
I woke up about 5 hours later, and the phone was at 4% battery life. I dont know what happened. i can get it to about 2% charge and then it stops and dies out. i did notice that the clock on the status bar froze at one point and said 11:40 when it was really 12:27. the clock widget on the main screen was correct the whole time.
I am able to get into recovery, I am able to get into fastboot, I am able to get into the ROM...
I have switched out the radio to different one than the one last night, and i have switched the kernel to "CollectiveACE-BFS-v0.1.5" and that doesnt solve the issue. I have also cleared the battery stats, even though i didn't want to since it was at such a low level of power...none of these things helped.
I have also noticed that after the phone shuts off, when i power it back on, it goes into recovery. I am unsure why, but when I tell it to reboot from recovery, it goes right back to recovery, and i have to pull my battery to get it to go to the OS.
Any idea's? and I am sorry if this is confusing...
Try flashing a new ROM. But before you do, flash Mike1986's superwipe script from here: http://dl.dropbox.com/u/61962340/Android_Revolution_HD_Super_Wipe.zip , just to make sure everything is fully clean . Then flash your ROM of choice. Also, never flash radios for the heck of it. They can easily brick your device. Be careful, and report back
RUMyBruncle said:
I got the phone just 3 days ago from an insurance claim, had no problems with it other than the power button is a pain sometimes.
I rooted the phone yesterday with visionary at first, then gfree after i got the s-off, and I have the CWM 5.8 touch recovery. I then flashed Virtuous Unity 2.39 and the Darkside v12 kernel, as well as all sorts of different radio's. I then fell asleep after installing those, and before setting up the ROM, and i left it charging on my computer overnight.
I woke up about 5 hours later, and the phone was at 4% battery life. I dont know what happened. i can get it to about 2% charge and then it stops and dies out. i did notice that the clock on the status bar froze at one point and said 11:40 when it was really 12:27. the clock widget on the main screen was correct the whole time.
I am able to get into recovery, I am able to get into fastboot, I am able to get into the ROM...
I have switched out the radio to different one than the one last night, and i have switched the kernel to "CollectiveACE-BFS-v0.1.5" and that doesnt solve the issue. I have also cleared the battery stats, even though i didn't want to since it was at such a low level of power...none of these things helped.
I have also noticed that after the phone shuts off, when i power it back on, it goes into recovery. I am unsure why, but when I tell it to reboot from recovery, it goes right back to recovery, and i have to pull my battery to get it to go to the OS.
Any idea's? and I am sorry if this is confusing...
Click to expand...
Click to collapse
Stop flashing aosp kernels on your SENSE rom... Try darkside sense v7 or one of the unity kernels and all should be fine.
Sent from my HTC Glacier using xda premium
I have installed Icecreaminsanity 7.1 AOKP fixed or whatever the name of it is. I did not know the kernels were different depending on AOSP and Sense. If i have ICS on it now, which kernel should I use since there are no ICS kernels for the glacier?
I dont know if the charging issue is fixed yet, because i just did the superwipe and put on the ICS ROM. I will post if it is fixed or not, but my hopes are low
edit: Sorry, it is IceColdInsomnia 7.1.AOKP-test.
WOW i love this ROM...but i digress...its still too early to tell if it's going to fix the charging issue. I did notice that when the screen was on and i was going through the launcher, it didnt interrupt me telling me my battery was only at 3%...maybe that's a good sign.
No, it didnt fix the issue. While leaving the screen off and plugged into the wall, the charge dropped to 2%, and now it's blinking between the green and orange LED's...what do I do now??? Any recommended kernels for this rom? would an AOSP kernel be better than a Sense kernel for this new ROM?
Edit: I am already using the kernel mentioned by the OP in the thread for that ROM...the Collectives ACE kernel.
Get an external battery charger or find a friend with a glacier or t-bolt and charge the battery. Flash PD15IMG.zip and start over. If it still doesn't charge tell them they sent you a busted device, raise some hell, and see what you can get.
Sent from my HTC Glacier using XDA
i think that may be my only option. I appreciate your guys' help. it was really nice to see people giving actual advice with links instead of just telling me im in idiot and telling me to search for it.
Haha, well some of us are trying. Also, you didn't post in the dev section, so that's an automatic plus.
Don't forget to get S-On if you have to send it back.
estallings15 said:
Haha, well some of us are trying. Also, you didn't post in the dev section, so that's an automatic plus.
Don't forget to get S-On if you have to send it back.
Click to expand...
Click to collapse
Haha yeah, props to OP!
i'm no noob to this forum or to rooting...but i am to the MT4G...lol it's a completely different beast than the MT3G i came from. Thanks again, and i guess a mod can close this thread out...
In the middle of using my mt4g, it just froze. I waited 10 minutes but never got the not responding message. So I pulled the battery, and all it did was sit at the white mt4g screen until the battery died. While the battery charged, I looked here for a solution. I found this thread http://forum.xda-developers.com/showthread.php?t=1844910, and since it seemed to describe my situation, I followed it. So I put the pd15img.zip on the microsd card and the boatloader said update succesfully applied. I hit restart and it turned off but didnt come back on. And it hasn't Im pretty sure that mean my phone is gone, but does anyone know of any black magic that may bring it back from the grave? I really like this phone. I've taken really good care of this phone and it is in such good physical shape.
Ideas?
shiboby said:
In the middle of using my mt4g, it just froze. I waited 10 minutes but never got the not responding message. So I pulled the battery, and all it did was sit at the white mt4g screen until the battery died. While the battery charged, I looked here for a solution. I found this thread http://forum.xda-developers.com/showthread.php?t=1844910, and since it seemed to describe my situation, I followed it. So I put the pd15img.zip on the microsd card and the boatloader said update succesfully applied. I hit restart and it turned off but didnt come back on. And it hasn't Im pretty sure that mean my phone is gone, but does anyone know of any black magic that may bring it back from the grave? I really like this phone. I've taken really good care of this phone and it is in such good physical shape.
Ideas?
Click to expand...
Click to collapse
Sounds like she gave up the ghost, buddy. Sorry.
Sent from my HTC Glacier using xda app-developers app
shiboby said:
In the middle of using my mt4g, it just froze. I waited 10 minutes but never got the not responding message. So I pulled the battery, and all it did was sit at the white mt4g screen until the battery died. While the battery charged, I looked here for a solution. I found this thread http://forum.xda-developers.com/showthread.php?t=1844910, and since it seemed to describe my situation, I followed it. So I put the pd15img.zip on the microsd card and the boatloader said update succesfully applied. I hit restart and it turned off but didnt come back on. And it hasn't Im pretty sure that mean my phone is gone, but does anyone know of any black magic that may bring it back from the grave? I really like this phone. I've taken really good care of this phone and it is in such good physical shape.
Ideas?
Click to expand...
Click to collapse
Was it the bad eMMC chip?
I don't know. How do i tell
Sent from my GT-I9100 using xda app-developers app
I think you need your phone booting at least to know which emmc you have.
http://forum.xda-developers.com/showthread.php?t=1388962
check your eMMC chip through THIS GUIDE HERE
THAT METHOD REQUIRES ROOT ACCESS, WHICH YOU PROBABLY DON'T HAVE (unless the first thing you did was root, but that's not always the smartest idea)
so, here's the method that you can use to check your chip WITHOUT ROOT ACCESS
1) download the free terminal emulator app in the android market
2) open it up, and you should see a command line
3) type this command EXACTLY:
Code:
cat /sys/class/block/mmcblk0/device/name
if your device comes out with SEM04G, then GREAT! YOU CAN NOW SAFELY ROOT YOUR DEVICE AND FLASH TO YOUR HEARTS CONTENT IF YOU CHOOSE TO.
if your device came out with M4G2DE, then you're a little unlucky. you may, of course still choose to root if you want to, but BE WARNED: YOU ARE AT A RISK OF ENDING UP WITH A BRICKED DEVICE.
It was previously rooted and I used several different roms. But I can't get it to turn on to try what you posted.
Sent from my GT-I9100 using xda app-developers app