Related
Anyone able to assist. I have searched the forum.
After my compact froze I did a soft reset only to see it hang on the T-Mobile splash screen (white background, pink dots). The ROM details do not even appear in the bottom right hand corner.
I have upgraded my ROM with Hard-SPL, a Radio ROM and Dutty's 1.8 ROM but that was weeks ago.
Not even a Hard-Reset sorts it out.
Cannot see how the new ROM would be causing the problem as it has worked for a few weeks.
Luckily followed all the instructions and have 1.40 Olinex Hard-SPL on the phone. Just need to wait for home so I can plug it into my laptop. What I do from that point on will be the subject of a further search of this board later.
Any assistance?
Since you already have Hard-SPL, try first flashing a stock ROM.
See here for available ROM's: http://wiki.xda-developers.com/index.php?pagename=Diamond_Upgrades
Let us know what the results are...
Thanks for the reply.
Unfortunately I cannot get my Compact to sync with my PC in order to add a stock ROM. As I am frozen on the T-Mobile screen the Mobile Device Center does not connect to the Compacy.
Are there any work arounds?
Oh well back it goes to T-Mobile with the hope that they do not identify that the ROM has changed.
Happened to me before as well.
Start your Phone in bootloader mode. Means you hold down the Volume down button while soft resetting. Then you get to the red, green, blue, white screen. In the bottom it says "serial". once you connect to the PC it switches to "usb" and now you can flash ANY ROM you like. I replaced mine with the same ROM I had before....
Don't know what happened to cause this problem. But I got it solved that way.
Let me know if this worked....
Cheers for the reply Staty.
I was able to get the USB connection to work but after reloading the ROM the phone has gone off and stayed off. Can't get any splash screen now.
But you were able to completely reflash the ROM?
Or did it stop along the way?
Did not stop along the way. Went to 100% and was met by the finished screen on the PC. However the Compact does not turn in now.
So you try to turn it on but nothing happens?
Did you try hooking the phone to the loading cable and then turn it on? Maybe a problem with the bettery?
Besides that I got no idea right now.
Which ROM did you reflash? The same you used before?
Hi,
You must download full rom (with radio etc.), the best original. Doesn't matter which one. And hard reset after that.
staty said:
So you try to turn it on but nothing happens?
Did you try hooking the phone to the loading cable and then turn it on? Maybe a problem with the bettery?
Besides that I got no idea right now.
Which ROM did you reflash? The same you used before?
Click to expand...
Click to collapse
Tried hooking it up to the loading cable, the charger and still no luck.
Have no idea why it will not start-up. Do not even get the white circular light when plugged into the charger.
PanNet said:
Hi,
You must download full rom (with radio etc.), the best original. Doesn't matter which one. And hard reset after that.
Click to expand...
Click to collapse
Yep done all that. Compact still dead. Changed ROM about 3 weeks ago, no problems just stopped working altogether. Was able to connect it to the PC to update ROM again but now nothing.
Not sure how having Hard-SPL on the phone is gonna help when the thing wont turn on.
waynespa said:
Anyone able to assist. I have searched the forum.
After my compact froze I did a soft reset only to see it hang on the T-Mobile splash screen (white background, pink dots). The ROM details do not even appear in the bottom right hand corner.
I have upgraded my ROM with Hard-SPL, a Radio ROM and Dutty's 1.8 ROM but that was weeks ago.
Not even a Hard-Reset sorts it out.
Cannot see how the new ROM would be causing the problem as it has worked for a few weeks.
Luckily followed all the instructions and have 1.40 Olinex Hard-SPL on the phone. Just need to wait for home so I can plug it into my laptop. What I do from that point on will be the subject of a further search of this board later.
Any assistance?
Click to expand...
Click to collapse
Here wot fella.... Yesterday i called t-mobile cause my mda was running kinda hot for some reason, With no effort the lady said it shouldn't be getting that hot (like she could feel the heat over the phone lol) "i'm going to send you a replacement for tomorrow morning" Today, So me thinking a refurbished phone and no screen protector, i asked if they could send me a screen protector, No she said, i'm sending you a brand new phone "in the box" so all the bits will be there.......
Brilliant i get a new mobile..... Here is the best bit....
UPS turns up this morning with a brand new phone.. the guy asks me for the old phone ONLY, didn't take back old batt, headset...etc put it in a bag and away he went......
So i get a brand new phone (BOXED) and get to keep all the old accessories.
So the moral of the story is..... RMA your mobile, tell t-mobile its over heating and pray too god you get the same woman on the phone that i did...!
P.s..... Out of curiosity, Which cooked rom was you using...!
fyew-jit-tiv said:
P.s..... Out of curiosity, Which cooked rom was you using...!
Click to expand...
Click to collapse
I used Dutty's 1.8, but It is not a problem with the ROM, I'm sure of that.
fyew-jit-tiv said:
Here wot fella.... Yesterday i called t-mobile cause my mda was running kinda hot for some reason, With no effort the lady said it shouldn't be getting that hot (like she could feel the heat over the phone lol) "i'm going to send you a replacement for tomorrow morning" Today, So me thinking a refurbished phone and no screen protector, i asked if they could send me a screen protector, No she said, i'm sending you a brand new phone "in the box" so all the bits will be there.......
Brilliant i get a new mobile..... Here is the best bit....
UPS turns up this morning with a brand new phone.. the guy asks me for the old phone ONLY, didn't take back old batt, headset...etc put it in a bag and away he went......
So i get a brand new phone (BOXED) and get to keep all the old accessories.
So the moral of the story is..... RMA your mobile, tell t-mobile its over heating and pray too god you get the same woman on the phone that i did...!
Click to expand...
Click to collapse
Mine has been extremely hot for the last few days. I'm gonna phone them now.
waynespa said:
Yep done all that. Compact still dead. Changed ROM about 3 weeks ago, no problems just stopped working altogether. Was able to connect it to the PC to update ROM again but now nothing.
Not sure how having Hard-SPL on the phone is gonna help when the thing wont turn on.
Click to expand...
Click to collapse
Thats really wiered. Looks like there is more broken than the ROM. Did you try taking out the battery and keeping it out for a little time.
Try to turn on the phone without the battery in it - so all the power in the condensers etc. will be gone.
Keep the battery separated from the phone for a couple hours and then try it again.
I was having the trouble back then, that the more often I tried to turn the phone on while it was broken it turned off itself even quicker. after I left it without touching it an hour it took longer to turn off itself again.
P.P.S and remember so say its the bottom part off the phone or they may try palm you off with its "the battery"...!
fyew-jit-tiv said:
P.P.S and remember so say its the bottom part off the phone or they may try palm you off with its "the battery"...!
Click to expand...
Click to collapse
Called them and put on my nicest charm with a young lady. She actually read out a T-Mobile notice release that said there was a known fault with the phones over-heating during charge and large downloads. It said that customers should be told that it is safe and a software update coming out soon would sort it out.
I told here the phone no longer worked and she said that they would replace but I should keep all accesories and the battery. I said that as it doesn't turn on it could be the battery and she agreed to a FULL replacement.
They are sending it to my work on Monday and will take the old one away.
Thanks for the advice, was really worried they would want it back for testing BEFORE sending out a new one and they may find my Custom ROM
All good though. Thanks again.
staty said:
Thats really wiered. Looks like there is more broken than the ROM. Did you try taking out the battery and keeping it out for a little time.
Try to turn on the phone without the battery in it - so all the power in the condensers etc. will be gone.
Keep the battery separated from the phone for a couple hours and then try it again.
I was having the trouble back then, that the more often I tried to turn the phone on while it was broken it turned off itself even quicker. after I left it without touching it an hour it took longer to turn off itself again.
Click to expand...
Click to collapse
I left the battery overnight but still no luck.
I am pretty certain it'saphone fault now and absolutely nothing to do with ROM's. T-Mobile are now thankfully taking it back.
Cheers
So I flashed the cm7 alpha that came out last night this morning. I wasn't getting calls so i turned it off and tried to reboot it into recovery. The phone never got into recovery (I told it to reboot into recovery from clockwork mod), and now it isnt powering on, at all. I've tried every key combination, recovery, download mode, letting it charge for HOURS, and still nothing.
If anyone has any ideas, please let me know. I'm trying to gather the files I need to see if odin will recognize it and possibly be able to restore it to stock. If I can't get it to work by tomorrow, I'm just going to go to the T-Mobile store.
aaronpaws said:
So I flashed the cm7 alpha that came out last night this morning. I wasn't getting calls so i turned it off and tried to reboot it into recovery. The phone never got into recovery (I told it to reboot into recovery from clockwork mod), and now it isnt powering on, at all. I've tried every key combination, recovery, download mode, letting it charge for HOURS, and still nothing.
If anyone has any ideas, please let me know. I'm trying to gather the files I need to see if odin will recognize it and possibly be able to restore it to stock. If I can't get it to work by tomorrow, I'm just going to go to the T-Mobile store.
Click to expand...
Click to collapse
Would it be possible that you tried so many combinations that the phone's battery has died? Have you tried plugging it in and seeing what happens?
charged for four hours and nothing.
Took it to a tmobile store and they're doing a warranty exchange since they couldn't get it to do anything either, even with a different battery.
Kind of curious as to what'll happen when I send it back since it has cyanogen mod 7 on it and its rooted. Then again, the phone won't boot, go into download mode, or recovery.
edit: I'm thinking the phone won't charge because of the custom kernel in cm7. Don't know how I would flash a kernel if I couldn't get it to boot though.
Dam,, too late
But for reference try!
Take the battery out and let it sit for a few min the put it back in and see if it boots.
If it still will not boot
Take the battery back out
Plug in the USB cable connected to the computer
Hold down the volume up and down then
Put the battery back in.
You should get the option: Volume UP / Volume Down for Reboot
Hit Volume UP and go get some Odin love!
I still have the phone, I'm gonna try this now. Will update with results.
aaronpaws said:
I still have the phone, I'm gonna try this now. Will update with results.
Click to expand...
Click to collapse
Cool man, keep us updated.
Well, I tried both suggestions to no avail. Anyone else have any ideas?
aaronpaws said:
Well, I tried both suggestions to no avail. Anyone else have any ideas?
Click to expand...
Click to collapse
I did not see you mention it, but did you try the "10 second" power button hold? You know it works when the phone vibrates 3 times. Simply hold the power button until it vibrates. It takes about 7-10 seconds (although when you think your phone is bricked, it feels like it is taking 5 minutes). If it vibrates, you are in the clear. You can usually get to recovery or odin from there. Try doing this on battery only first.
no cigar with the hold for ten seconds method on the power button.
aaronpaws said:
no cigar with the hold for ten seconds method on the power button.
Click to expand...
Click to collapse
It is really, REALLY difficult to brick a phone unless you are changing the radio (for example, flashing a wrong or corrupted radio). A kernel can hose your phone, but not brick it as you don't need a kernel to access recovery. A bad recovery could also brick your phone, but then you have download mode (Odin) to access that bypasses recovery. In other words, there are layers of protection or access points. We have not flashed any new radios for our phones yet, so you know that is not the problem. Having said all that, that does not mean you are not bricked.
To be clear on your position, you are getting no power response at all? Again, try this:
Unplug your phone;
take battery out (wait about a minute before replacing battery);
replace battery;
"10 second" hold until phone vibrates 3 times (or vibrates at all for that matter);
If you see no sign of life, then try the above process with phone plugged in (try plugged into computer and wall socket separately). Odin recognizes when you are plugged into computer and the boot process goes differently.
As for Odin bootup:
Load Odin;
Plug in your USB to computer;
try the volume/power boot up;
if that fails, try the "10 second" hold boot up with Odin running on your system and phone plugged in.
Outside of that, I can not think of any other way to get you to recovery or Odin.
I have flashed my android phones probably 150+ times in the last 2 and a half years and never made a brick. I thought I had, but was always able to get to recovery or bootloader (think Odin for HTC), and recover the phone. The only times I ever saw anyone truly brick the phone was when flashing the wrong or bad radio for their phone (radio is your 4G / cell receiver). So, walk through your processes to recover your phone in a methodical way and if that all fails, then return it. If you can't get it to go trying all these techniques, then T-mobile probably won't be able to as well and see that you rooted it.
Hope this helps.
Slightly off topic but if you send in a rooted phone for warranty (not insurance, warranty) they will charge you a full repair fee.
Sent from the Galaxy, 2 stars to the left.
What happens when you pull your battery, put it back in and attempt to turn your phone on?
Sent from my SGH-T989 using Tapatalk
@PorchSong, I've tried everything you said to no avail. I know its extremely hard to brick an android phone. Having had over 10 devices in the past year, all running custom roms, I've never bricked one either. This is why I find this so unbelievable, I usually don't make posts on XDA, not for lack of caring about the subject matter, but rather because I'd rather learn about it on my own to further my understanding on it.
Again, this is as bricked as I've ever seen something. The phone simply is unresponsive to every method I've tried.
@btyork, how would they know if the phone doesn't boot into recovery, download mode, or into regular android? I'm not saying that they couldn't. I'm just saying, what precautions could I take against them finding out. Trust me, if i could find a way to, I'd restore it to stock before I sent it back to them. (I still have the phone and will until december 6th, when they send me my new one, so we have a little bit of time to work on this)
@ mikeyinid, Nothing at all. Nothing in this thread has made the phone give even the slightest response.
The last thing I did was try to boot into clockwork mod, rather than boot with the key combination like I normally do, i did it directly from rom manager. Except, it never booted into recovery, so I pulled the battery and tried to start it again, from there it hasn't booted, or charged. I could've sworn the phone had at least a 30 percent charge when I was doing all this as well. Not the best for restoring from a backup in clockwork mod but I was in a bind as I was about to leave somewhere for roughly two hours and needed a functioning phone (cm7 did not let me make or receive calls, for whatever reason).
Are you seeing anything on the screen?
Sent from my SGH-T989 using XDA App
aaronpaws said:
@PorchSong, I've tried everything you said to no avail. I know its extremely hard to brick an android phone. Having had over 10 devices in the past year, all running custom roms, I've never bricked one either. This is why I find this so unbelievable, I usually don't make posts on XDA, not for lack of caring about the subject matter, but rather because I'd rather learn about it on my own to further my understanding on it.
Again, this is as bricked as I've ever seen something. The phone simply is unresponsive to every method I've tried.
@btyork, how would they know if the phone doesn't boot into recovery, download mode, or into regular android? I'm not saying that they couldn't. I'm just saying, what precautions could I take against them finding out. Trust me, if i could find a way to, I'd restore it to stock before I sent it back to them. (I still have the phone and will until december 6th, when they send me my new one, so we have a little bit of time to work on this)
@ mikeyinid, Nothing at all. Nothing in this thread has made the phone give even the slightest response.
The last thing I did was try to boot into clockwork mod, rather than boot with the key combination like I normally do, i did it directly from rom manager. Except, it never booted into recovery, so I pulled the battery and tried to start it again, from there it hasn't booted, or charged. I could've sworn the phone had at least a 30 percent charge when I was doing all this as well. Not the best for restoring from a backup in clockwork mod but I was in a bind as I was about to leave somewhere for roughly two hours and needed a functioning phone (cm7 did not let me make or receive calls, for whatever reason).
Click to expand...
Click to collapse
Are you sure you flashed cm7 for our phone? Sounds like a boot.img flashed to the wrong partition. I only know that because I bricked my first gs2 using the wrong mount point to flash a kernel. If it doesn't do anything at all, jig might work but idk. I just got a new one
Sent from my SGH-T989 using Tapatalk
Typically with Samsung phones, if you can get ANYTHING at all to show on the screen it is not bricked.
Do you have a G+ account? If I can see what is going on while I walk you through it it would be easier. Could possibly hold an open hangout so others can join in and help or just for informational purposes.
I have had soft bricks on my behold 2, vibrant and SGS2, over 100 times all together. Sometimes it takes a little fiddling, my SGS2 seemed a little more difficult only because of the relative simplicity of it compared to the others.
---------- Post added at 02:18 PM ---------- Previous post was at 02:15 PM ----------
mikeyinid said:
Are you sure you flashed cm7 for our phone? Sounds like a boot.img flashed to the wrong partition. I only know that because I bricked my first gs2 using the wrong mount point to flash a kernel. If it doesn't do anything at all, jig might work but idk. I just got a new one
Sent from my SGH-T989 using Tapatalk
Click to expand...
Click to collapse
Well i think he said it did boot initially, so I doubt that is the problem.
---------- Post added at 02:19 PM ---------- Previous post was at 02:18 PM ----------
btyork said:
Slightly off topic but if you send in a rooted phone for warranty (not insurance, warranty) they will charge you a full repair fee.
Sent from the Galaxy, 2 stars to the left.
Click to expand...
Click to collapse
That depends if they can tell or not.
Okay, well I'm going to try and fix it in Odin one more time tomorrow on my friends computer (I use a mac), so I'll report back on what happens. I'm thinking I didn't put it into download mode the right way when I tried it the other night. I remember having to do it for rooting the phone, but hadn't done it since, and since this is my first samsung phone other than the nexus s, I wasn't all that familiar with it. The google + idea might be a good one. I'm not sure how to go about setting that up, but I should be at my friends around like 12est tomorrow, so if anyone wants to set something up we can do that, or I can just report back. Either way, I'll come back to this thread and give a conclusion on what's happened.
aaronpaws said:
Okay, well I'm going to try and fix it in Odin one more time tomorrow on my friends computer (I use a mac), so I'll report back on what happens. I'm thinking I didn't put it into download mode the right way when I tried it the other night. I remember having to do it for rooting the phone, but hadn't done it since, and since this is my first samsung phone other than the nexus s, I wasn't all that familiar with it. The google + idea might be a good one. I'm not sure how to go about setting that up, but I should be at my friends around like 12est tomorrow, so if anyone wants to set something up we can do that, or I can just report back. Either way, I'll come back to this thread and give a conclusion on what's happened.
Click to expand...
Click to collapse
Let me know, G+ is easy. Im out of class at 2est.
Just FYI. I ran into this exact same issue. After charging my phone all night and using it for about 5 minutes, I set it down then picked it up like 30 minutes later and received absolutely no responsiveness from the phone. It wouldn't even recognize the charger when I plugged it in.
I tried all the battery tricks, and reset tricks and nothing worked. So I took it into the T-Mobile store, assuming it was bricked, in an attempt to get it replaced. He simply plugged the phone into the stock charger that came with the phone and it indicated that the battery was just completely dead and needed a charge.
It turns out that the phone really didn't get a full charge after being plugged in all night to my GF's MT4G charger. Apparently this phone is picky about what charger is used. I'm sure you've already attempted this, but just make sure to plug it into the stock charger to see if you can at least get the charging battery image to pop up.
more like it wasn't plugged in properly to begin with
because that happened to me, even though it said "charging"... it was stuck at 43% for like 4+ hours, so i figured something must be wrong
and indeed it was, so i unplugged it, and plugged it back in, then voila! now it starts to charge as it was supposed to.
the phone is not picky by any means, i've used my old BB charges with it, the other HTC charger, the other samsung USB, the generic cheap chargers i get from Deal Extreme, etc
they all charges the phone just fine and fast
you do have to be careful when you plug it in, and make sure it's really charging
sn0warmy said:
Just FYI. I ran into this exact same issue. After charging my phone all night and using it for about 5 minutes, I set it down then picked it up like 30 minutes later and received absolutely no responsiveness from the phone. It wouldn't even recognize the charger when I plugged it in.
I tried all the battery tricks, and reset tricks and nothing worked. So I took it into the T-Mobile store, assuming it was bricked, in an attempt to get it replaced. He simply plugged the phone into the stock charger that came with the phone and it indicated that the battery was just completely dead and needed a charge.
It turns out that the phone really didn't get a full charge after being plugged in all night to my GF's MT4G charger. Apparently this phone is picky about what charger is used. I'm sure you've already attempted this, but just make sure to plug it into the stock charger to see if you can at least get the charging battery image to pop up.
Click to expand...
Click to collapse
Got a new rom yesterday. Was working fine, phone was charging fine. Today After using the phone for about 10 hours it just died. I didn't do anything new such as download any new apks or flash any thing. But it just died. When I hold power it can go to the samsung screen and just die, when I hold power vol down and home it goes to the download screen for like 5 sec and dies, when I go to cwm it dies in a short time as well.
Now I have it wall charging and I'm getting no LED light, so I'm worried!!!
Any recommendations?
ihugyou said:
Got a new rom yesterday. Was working fine, phone was charging fine. Today After using the phone for about 10 hours it just died. I didn't do anything new such as download any new apks or flash any thing. But it just died. When I hold power it can go to the samsung screen and just die, when I hold power vol down and home it goes to the download screen for like 5 sec and dies, when I go to cwm it dies in a short time as well.
Now I have it wall charging and I'm getting no LED light, so I'm worried!!!
Any recommendations?
Click to expand...
Click to collapse
Depending on what rom. Some don't play well with the led. Also you have to make sure it's checked in the settings.
Have you tried turning it on while it's charging?
Sent from a planet far far away.
Speedin07si said:
Depending on what rom. Some don't play well with the led. Also you have to make sure it's checked in the settings.
Have you tried turning it on while it's charging?
Sent from a planet far far away.
Click to expand...
Click to collapse
Some times it turns on while charging, but will just turn back off.
I'm using This Rom
Edit* the led normally turns on while charging...im not that much of a newb, i'm just thinking I might have bricked my phone.. It's strange that it happened a whole day after I flashed the rom though..
ihugyou said:
Some times it turns on while charging, but will just turn back off.
I'm using This Rom
Edit* the led normally turns on while charging...im not that much of a newb, i'm just thinking I might have bricked my phone.. It's strange that it happened a whole day after I flashed the rom though..
Click to expand...
Click to collapse
If it's turning on its not bricked at all. It's a charging issue, take the back cover off make sure the battery is making good contact with its connection points. Close it back up and plug it in and let it charge for 30 tp 40 minutes check if it comes on. Sometimes when the battery dies completely it takes some time to get some charge into it. The booting up process uses a ton of power, once on make sure you leave it plugged in and charge fully.
Transmitted with a portable device using Xparent Blue Tapatalk 2
Ok because the one time it actually came on it said it was at 70%, which I'm assuming is totally incorrect. So I will now plug it into the wall and let it charge for quite a while, I jsut think it's weird that the light never comes on (which it normally does).....
thanks for the tips dudes!
I had the same issue as you, the phone will turn on and then most of the time it will turn off during the boot process. If I turn it on in Download or Recovery mode it'll stay on for a couple seconds and then turn off. At best, it'll turn on, get to the home screen and then after a couple seconds of usage it'll turn right back off. Also, did you notice that before the phone turned off it would lock itself and unlock itself possibly showing the power menu to like reboot or turn off and such? That made me think it might've been the power button but I'm not positive.
I could not get a fix for this at all, I attempted everything I could think of. I ran the phone in safe mode, it still did it. I ran a different rom, still had the issue. Ran stock rooted, same problem. Ran stock non-rooted, problem still there. In fact, I talked to Samsung yesterday and I sent it in for the warranty as I didn't have carrier insurance. One thing happened was that while I was in stock rooted, I decided to underclock the phone to see if anything would occur and I noticed something interesting. The phone still had the problem but it would stay on for longer periods of time. This made me think maybe the phone was overheating or the CPU was shutting itself off for some reason. As far as I know from my testing I can say that the problem was hardware related. I should also note that this thing happened to me once a couple months ago but I flashed the stock tar through Odin and the problem disappeared for a short while but it came back and continually did so.
Oh, I also figured out how to get it on for a short period of time. To get it to work temporarily, first make sure the phone is charged a good amount. Plug it in for a couple hours. Next, take the battery out of the phone for a couple hours and remove the phone from the charger, the longer you keep the battery out the better. Now, put the battery back in, and attempt to turn on the phone, if it doesn't work try again a couple times. The phone should eventually turn on and stay on for a short period of time (anywhere between 1 or 2 min and 30 minutes). From here just back up anything you need to and if you are rooted and want to turn it in for warranty or whatnot you'll need to clear the evidence that the phone was rooted.
First off, if you are rooted you'll want to clear your flash counter. Download the Triangle Away apk and put it in the microSD so you can access it easily when the phone turns on. Follow the instructions on how to turn the phone on from above. After it turns on, quickly Run Triangle away and click on the option that says something along the lines of "reset flash counter". Once that is done, turn off the phone and take out the battery so that you can turn it on for the next step.
Next, you will need to download Odin (I believe it is Windows only, if you don't have Windows I'm not sure what you can do as I haven't had to unroot on anything other than my PC) and the stock tar file so that you can return the phone to complete stock. Once you have done this, run Odin and click on the PDA tab and browse for the stock tar. Let Odin do it's thing and once you see it's ready to flash the file, put the battery back in and turn the phone back on in download mode. Plug the phone in and let it sit there for a couple seconds to make sure it won't turn off during the flashing process. If it does turn off try again. When you can get it to stay on for over 30 seconds click on the Start in Odin and start the flash. If it stays on for a while but turns off while flashing, the boot will be corrupt and you will have to try again til you can get it to stay on long enough. Note that if the boot is corrupt you won't be able to turn the phone on to anything other than Download mode and possibly recovery. Once you complete the flashing process the phone should auto-boot and it SHOULD work. That means that the phone should turn on with no problems but it may or may not turn itself off. If it doesn't turn itself off go ahead and use it for a while, but if your situation is like mine the problem will come back eventually. But at least now you can turn it in to Samsung for warranty or whatnot.
And if worst comes to worst you can completely f up the phone while it's flashing in Odin, have a corrupt boot img and then call in saying it doesn't work.
Of course all of this is only if you're having a similar problem to me. Like I said, I sent it in yesterday so I'll post updates as I get them. Hopefully they'll fix it for me!
Nice write-up :good:
@OP If you can't get the unroot process to work (like the guy above me said) just flash a rom made for the international S3, thats a sure-fire way to brick you phone
Sent from my PG06100
CNexus said:
Nice write-up :good:
@OP If you can't get the unroot process to work (like the guy above me said) just flash a rom made for the international S3, thats a sure-fire way to brick you phone
Sent from my PG06100
Click to expand...
Click to collapse
It was quite a nice wall of text. And oh yes, bricking your phone is a great idea! Say it was an OTA or something haha
Ok so SG3 should have a warranty even though I don't have carrier insurance?
And did you try replacing the battery?
ihugyou said:
Ok so SG3 should have a warranty even though I don't have carrier insurance?
And did you try replacing the battery?
Click to expand...
Click to collapse
Correct, there is a 1 year warranty on the phone and 6 months on the battery and charger. And yes I switched with another OEM battery and the issue persisted. However, the S3 I switched the batteries with continued to work so I believe it is the phone itself and not the battery or charger. It might be the connector points but my phone did strange things before turning off. It may be a combination of many things as well.
porshce2 said:
Correct, there is a 1 year warranty on the phone and 6 months on the battery and charger. And yes I switched with another OEM battery and the issue persisted. However, the S3 I switched the batteries with continued to work so I believe it is the phone itself and not the battery or charger. It might be the connector points but my phone did strange things before turning off. It may be a combination of many things as well.
Click to expand...
Click to collapse
Where exactly did you take your phone to return it? The samsung people are giving me a hard time it seems.
ihugyou said:
Where exactly did you take your phone to return it? The samsung people are giving me a hard time it seems.
Click to expand...
Click to collapse
I requested a Repair Service. You can contact them at 1-888-987-4357 and request the service there. They'll send you a UPS label and give you an RMA number. I tried to do it through the site but it didn't work so your best bet is to call them there. It's very simple to do it if your phone is already registered. Otherwise you'll have to give them the HEX number I believe. It's under your battery so just have that ready.
porshce2 said:
I requested a Repair Service. You can contact them at 1-888-987-4357 and request the service there. They'll send you a UPS label and give you an RMA number. I tried to do it through the site but it didn't work so your best bet is to call them there. It's very simple to do it if your phone is already registered. Otherwise you'll have to give them the HEX number I believe. It's under your battery so just have that ready.
Click to expand...
Click to collapse
Ok currently i have my phone running amazingly, re rooted, and installed moar morphology, I'm gonna give this some time and see what happens.. if it dies again i'm bricking it for good and returning it.
I really appreciate your help!
ihugyou said:
Ok currently i have my phone running amazingly, re rooted, and installed moar morphology, I'm gonna give this some time and see what happens.. if it dies again i'm bricking it for good and returning it.
I really appreciate your help!
Click to expand...
Click to collapse
Well if it does happen again, don't brick it unless you can't get it to turn on for long enough to flash stock. Hopefully it'll still be under warranty if it does happen again. And no problem! Good luck!:good:
porshce2 said:
Well if it does happen again, don't brick it unless you can't get it to turn on for long enough to flash stock. Hopefully it'll still be under warranty if it does happen again. And no problem! Good luck!:good:
Click to expand...
Click to collapse
This phone is giving me some epic ****in stress, can't load a rom, can revert to stock, but how boring is that... i've tried flashing at least 3 roms so far, this is taking forever, it just sits at the samsung galaxy screen now or reboots to recovery lol wtf ****ing phone
ihugyou said:
This phone is giving me some epic ****in stress, can't load a rom, can revert to stock, but how boring is that... i've tried flashing at least 3 roms so far, this is taking forever, it just sits at the samsung galaxy screen now or reboots to recovery lol wtf ****ing phone
Click to expand...
Click to collapse
If think you need to take a deep breath and relax. Try doing some more reading, it sounds like your missing a step somewhere. There's something which may be insignificant but your missing it.
Transmitted with a portable device using Xparent Blue Tapatalk 2
Hey Guys, long time reader never posted. I think i may have hard bricked my brand new 5X. I am not new to flashing ROMs I have had great sucess with my old Nexus5 for year (now I have to revert to that phone for now)
I was running Cyanogenmod then decided to try Catalysm. All was wokring fine and then i decide to just reflash to stock. I downloaded the correct factory image went into terminal like usual (linux) executed sudo ./flash-all in the correct folder and it went through the process in about a second then the phone turned off and my terminal screen said waiting for device. After waiting a while i tried turning the phone on got nothing. unplugged the phone tried volume down and power all the regular stuff to make the phone turn on. Plugging it into the charger shows nothing and I cant get into the bootloader.
I have never had an issue like this before I cant figure out flashing stock image would brick my phone? Am i totally screwed with warannty?
Thanks for any help gusy.
Maybe a to simple question.
How long was it ago? Maybe it's stick stuck in the loop with the screen off and maybe you have to wait it out.
If the phone dropped dead they can't even get into it to void your warranty, which I doubt they would do anyway. Let the phone sit for a little bit with it plugged in just so you can relax for a few minutes. Just hold the power button until it turns on. If it won't turn on at all then contact Google for a replacement device.
brick
bobby janow said:
If the phone dropped dead they can't even get into it to void your warranty, which I doubt they would do anyway. Let the phone sit for a little bit with it plugged in just so you can relax for a few minutes. Just hold the power button until it turns on. If it won't turn on at all then contact Google for a replacement device.
Click to expand...
Click to collapse
This just happened about an hour or so ago. Well i was thinking the same thing with the phone looping and no screen but it doesnt feel warm like its on. Also adb devices doesnt list it as on although i would imagine boot looping it would not see the device. Ive tried letting it charge for about a half hour with no luck. should I try letting it sit over night on the charger or off the charger in case its looping and i need it to die eventually?
I just reflashed the stock firmware on my old nexus 5 with no issues, its working fine i did that to make sure it wasnt an error i made.
Interesting, did you check the md5?,
I've never had success with flashall.bat it never worked, I end up extracting the archive and read the commands in flashall.bat and do it manually, worked for me,
When connected to pc does the pc drivers come up and disconnect due to device unplugged?( not sure if it displays on linux
republicano said:
Interesting, did you check the md5?,
I've never had success with flashall.bat it never worked, I end up extracting the archive and read the commands in flashall.bat and do it manually, worked for me,
When connected to pc does the pc drivers come up and disconnect due to device unplugged?,
Click to expand...
Click to collapse
I just figured out what happened. I flashed the nexus 5 flash-all rather then the nexus 5x (wow really dumb mistake). I found the hammerhead folder in the nexus5x folder i flashed from.
Now what?
If you can't get the phone to turn on you're out of luck.
Hey had something simmilar that my phone blank and unresponsive. No turning off. But maybe battery gone empty? try to leave phone longer under changer like for 1-2h or so. ANd the red led should be on showing phone battery gone full empty.
thanks for the help
Czepek said:
Hey had something simmilar that my phone blank and unresponsive. No turning off. But maybe battery gone empty? try to leave phone longer under changer like for 1-2h or so. ANd the red led should be on showing phone battery gone full empty.
Click to expand...
Click to collapse
Yea I am going to leave it for a day to make sure if its boot looping it will shutdown, then I am going to charge it for a day and try to turn it on see where i end up.
kmsgli said:
Yea I am going to leave it for a day to make sure if its boot looping it will shutdown, then I am going to charge it for a day and try to turn it on see where i end up.
Click to expand...
Click to collapse
Also, holding the power button for a few minutes to see if it eventually boots
You need to read the flashall.bat and see what the first commands were, as I think the bootloader maybe the first
Sorry but I doubt it will come back to life, if it bricked at fastboot flash bootloader, then reboot and failed to turn on to flash the rest,
It may need jtag service or you need to find something similar to this post below
forum.xda-developers.com/lg-g2/general/file-unbrick-qualcomm-9006-qhsusb-t3056800
lsusb
republicano said:
You need to read the flashall.bat and see what the first commands were, as I think the bootloader maybe the first
Sorry but I doubt it will come back to life, if it bricked at fastboot flash bootloader, then reboot and failed to turn on to flash the rest,
It may need jtag service or you need to find something similar to this post below
forum.xda-developers.com/lg-g2/general/file-unbrick-qualcomm-9006-qhsusb-t3056800
Click to expand...
Click to collapse
So with my phone plugged into my latop (linux) i run lsub with it plugged in and with it not plugged in and the differnce is this;
Bus 002 Device 031: ID 05c6:9008 Qualcomm, Inc. Gobi Wireless Modem (QDL mode)
my compuer is recognizing the device somehow but its the wrong name?
kmsgli said:
So with my phone plugged into my latop (linux) i run lsub with it plugged in and with it not plugged in and the differnce is this;
Bus 002 Device 031: ID 05c6:9008 Qualcomm, Inc. Gobi Wireless Modem (QDL mode)
my compuer is recognizing the device somehow but its the wrong name?
Click to expand...
Click to collapse
Sounds about right, that thread is for lg g2 and was just for display purpose, I not 100% sure if you can go through lg process on lg nexus,
Since the phone is also new I have not found any information on emmc fix.
You will have to go here and see if you can get help, but I think it will be some time till its released/leaked, you may have to pay to get it serviced.sorry about your Christmas present
forum.gsmhosting.com/vbb/f606/
Call Google and get it replaced. They are very good about that stuff.
kmsgli said:
I just figured out what happened. I flashed the nexus 5 flash-all rather then the nexus 5x (wow really dumb mistake). I found the hammerhead folder in the nexus5x folder i flashed from.
Now what?
Click to expand...
Click to collapse
Let Google know what happened, they're usually pretty good with that stuff and will probably let you RMA it. Google generally expects people to root their device, even though damaging the device while doing so is not technically covered under warranty they will probably help you out.
If 1 rep says no, call back and try another one. You can find countless examples online of people in your situation who Google helped out. Good luck!
Thanks guys
Thanks for all the help guys, I really apprecaite it, this site is really a great site full of people who want to help. ( im used to car forums where people call you an idiot any chance they get).
Ill post back if google did in fact help me out I will just wait for monday as I want to make sure if the phone is on for some reason with a weird screenless boot loop it has time to die and I can make sure I cant get it to boot myself.
Great news!! LG has repaired my phone and said they sent it back to me today. I have not confirmed it to be working as its in the mail but was told the phone has been repaired. So all you guys that do this while still under factory warranty can have your phone repaired by LG direct. Don't bother with google they can't repair it.
kmsgli said:
Great news!! LG has repaired my phone and said they sent it back to me today. I have not confirmed it to be working as its in the mail but was told the phone has been repaired. So all you guys that do this while still under factory warranty can have your phone repaired by LG direct. Don't bother with google they can't repair it.
Click to expand...
Click to collapse
So I guess that means it was so damaged even LG's equipment couldn't read any software/firmware details from the phone. Lucky for you. Just curious, what excuse did you give LG to make them think it wasn't caused by a software modification?
That's just it I was 100% honest and told them I accidentally flashed the nexus 5 image rather then the 5x image and bootloader was first on the flashall script. The girl who took the initial call didn't understand what I was saying so she typed exactly what I told her in the notes. I have to assume LG has a facotry cable that can flash the correct bootloader in seconds and the phone is back to new again.
really happy with LG service!!!!!
If I posted this in the incorrect place or there is something related to my issue, I apologize in advance.
I've been searching here and all over the internet and no progress yet so I decided to make a new account here just to see if anyone can help me because I'm out of ideas right now.
This morning my Nexus 5x (Non-rooted Nougat) woke me up like every morning, after dismissing the alarm I left it on my bed and when I came back to grab it later I noticed it shut off.
Here are the facts and what I have tried so far:
- Battery level was almost full
- I tried to turn it on but nothing happened, not even the Google logo
- Connected it to power and no icons or any response at all
- Left it connected for like an hour and tried to get it into recovery mode
- I was able to get into fastboot mode a few times but after electing "start" or "recovery mode" the Google logo comes up and then shuts off again right after.
- Tried getting into recovery mode after leaving it charging for a while again but I couldn't even get into fastboot this time, no signs of life at all.
- Disconnected the battery for a few minutes and tried to get into fastboot mode again, this time it worked but same thing happened. (Google logo then shuts off)
- Tried connecting it to my PC but doesn't show up on Linux nor Windows, on Windows it makes the sound like I connected a peripheral but that's pretty much it.
- I have USB debugging enable but never accessed my stuff through usb connection because I have had this issue before where it is connected but it won't show up or it shows up but won't let me access the files even though the phone is unlocked.
At this point it just won't do anything and I ran out of ideas. I just want to at least recover some pictures and information I have in it that isn't backed up, if anyone can help me I would greatly appreciate it.
Thanks in advance
It sounds like you might have encountered the hardware bootloop issue. This is theorized to be caused by bad solder for the eMMC chip or bad eMMC chip. This was an acknowledge problem on a related model LG phone, but hasn't been acknowledged for N5x.
If you are under warranty, you should start the replacement process before it runs out.
If you want to try something that sounds crazy but has worked for some people, put the phone in the freezer for 15 minutes then see if it boots. If it does, quickly back up as much data as you can, then wipe the phone in preparation to RMA exchange.
Just boot to bootloader (fastboot) then unlock it and flash a factory image... u can find many guides to this operation on the XDA
sfhub said:
It sounds like you might have encountered the hardware bootloop issue. This is theorized to be caused by bad solder for the eMMC chip or bad eMMC chip. This was an acknowledge problem on a related model LG phone, but hasn't been acknowledged for N5x.
If you are under warranty, you should start the replacement process before it runs out.
If you want to try something that sounds crazy but has worked for some people, put the phone in the freezer for 15 minutes then see if it boots. If it does, quickly back up as much data as you can, then wipe the phone in preparation to RMA exchange.
Click to expand...
Click to collapse
At this point, I'm willing to try anything. Thanks
driss.sadok said:
Just boot to bootloader (fastboot) then unlock it and flash a factory image... u can find many guides to this operation on the XDA
Click to expand...
Click to collapse
If it's a hardware issue like sfhub suggested, I don't think this will fix it.
PennyScissors said:
If it's a hardware issue like sfhub suggested, I don't think this will fix it.
Click to expand...
Click to collapse
Same here... cannot enter recovery mode, so flashed new rom stock rom.
The flashing was fine but it didn't help.
guys if u can get to the bootloader, sure it can be fixed.. everything is possible with the fastboot, u can fix any issue. if it's a hardware issue the bootloader wouldn't work as well.
Re Nexus 5X won't turn on - I've had same issue
PennyScissors said:
This morning my Nexus 5x (Non-rooted Nougat) woke me up like every morning, after dismissing the alarm I left it on my bed and when I came back to grab it later I noticed it shut off.
Here are the facts and what I have tried so far:
- Battery level was almost full
- I tried to turn it on but nothing happened, not even the Google logo
- Connected it to power and no icons or any response at all
- Left it connected for like an hour and tried to get it into recovery mode
- I was able to get into fastboot mode a few times but after electing "start" or "recovery mode" the Google logo comes up and then shuts off again right after.
- Tried getting into recovery mode after leaving it charging for a while again but I couldn't even get into fastboot this time, no signs of life at all.
- Disconnected the battery for a few minutes and tried to get into fastboot mode again, this time it worked but same thing happened. (Google logo then shuts off)
- Tried connecting it to my PC but doesn't show up on Linux nor Windows, on Windows it makes the sound like I connected a peripheral but that's pretty much it.
- I have USB debugging enable but never accessed my stuff through usb connection because I have had this issue before where it is connected but it won't show up or it shows up but won't let me access the files even though the phone is unlocked.
At this point it just won't do anything and I ran out of ideas...
Click to expand...
Click to collapse
I've had the same problem with my 5X, except my alarm didn't even go off! I woke up 15 minutes late to see the boot screen "enter your pattern to start Android". I entered my pattern and it looked like it was going to boot up but when I went back to it it was blank. Tried again, got to the Google loading dots and it switched off again and I haven't been able to power it up since. No bootloader, nothing. Tried all the troubleshooting steps on the Nexus Google Support pages (I did post a link but because I'm new it won't show, so just Google "Nexus Support") and nothing worked. I also knew the battery was fully charged because it had been on charge overnight and when I did get to the 'enter your pattern' screen, the battery icon in the notification bar was full.
I requested a call back from Google and nothing happened so I tried the chat and they said it sounded like a hardware issue and are sending me a replacement device within the next 3-5 working days. Good that they're replacing it. Bad that it happened on a device less than a year old and they only offered £10 Play Store credit by way of compensation, when I've had to spend £15+ on a PAYG sim card to use in my old phone in the meantime because the nano sim in my 5X was too small and I've spent over an hour and half this afternoon wasting my time with troubleshooting and waiting for a call back... Not really the customer service I expected from Google for what appears to be a hardware issue. If you bought the phone from Google, my advice would be to get in touch with Google Support and they should replace it under warranty.
danielledowns01 said:
I've had the same problem with my 5X, except my alarm didn't even go off! I woke up 15 minutes late to see the boot screen "enter your pattern to start Android". I entered my pattern and it looked like it was going to boot up but when I went back to it it was blank. Tried again, got to the Google loading dots and it switched off again and I haven't been able to power it up since. No bootloader, nothing. Tried all the troubleshooting steps on the Nexus Google Support pages (I did post a link but because I'm new it won't show, so just Google "Nexus Support") and nothing worked. I also knew the battery was fully charged because it had been on charge overnight and when I did get to the 'enter your pattern' screen, the battery icon in the notification bar was full.
I requested a call back from Google and nothing happened so I tried the chat and they said it sounded like a hardware issue and are sending me a replacement device within the next 3-5 working days. Good that they're replacing it. Bad that it happened on a device less than a year old and they only offered £10 Play Store credit by way of compensation, when I've had to spend £15+ on a PAYG sim card to use in my old phone in the meantime because the nano sim in my 5X was too small and I've spent over an hour and half this afternoon wasting my time with troubleshooting and waiting for a call back... Not really the customer service I expected from Google for what appears to be a hardware issue. If you bought the phone from Google, my advice would be to get in touch with Google Support and they should replace it under warranty.
Click to expand...
Click to collapse
I contacted Google and they didn't help me at all because my warranty expired last month, they literally just told me to put in a repair request at the LG repair webpage....this sucks
My experience exactly...
My wife's Nexus 5 exhibited the exact same symptoms this morning. It's been running perfectly for 20 months and today it died, and we're unable to even get into the bootloader screen or power on the phone.
Taking your advice, we put it in the freezer for 15 minutes and were able to perform a factory reset wiping all data from the phone. We are going to take advantage of Google's Christmas 2017 promotion and return the Nexus 5X and buy a Moto 4X. They require you perform a factory reset before returning the phone in order to receive a credit for the returned Nexus 5. Thank you so much for the help!
Dennis
sfhub said:
It sounds like you might have encountered the hardware bootloop issue. This is theorized to be caused by bad solder for the eMMC chip or bad eMMC chip. This was an acknowledge problem on a related model LG phone, but hasn't been acknowledged for N5x.
If you are under warranty, you should start the replacement process before it runs out.
If you want to try something that sounds crazy but has worked for some people, put the phone in the freezer for 15 minutes then see if it boots. If it does, quickly back up as much data as you can, then wipe the phone in preparation to RMA exchange.
Click to expand...
Click to collapse
https://forum.xda-developers.com/nexus-5x/help/help-nexus-5x-lg-off-to-t3729739
I've just posted this thread overlooking yours. I think this is becoming another common issue. Has the freezer trick worked with anybody else?
I am having the same issue described here. My Nexus 5x went into a Bootloop about one month ago, but I was able to get it working again by going into Recovery Mode. About 4 days ago it went into a constant Bootloop, just showing the Google screen, and I couldnt get back in to recovery mode. I ordered a new phone on Tuesday (Pixel 2) and as long as I am able to do a factory reset I should get a $150 credit when I send this phone back. So, in desperation, I took a chance on the 15 minute freezer trick, and it worked! I was able to get into recovery mode (power + volume down, select Recovery Mode, little dude on his back came up, pushed power + volume up once) and cleared the cache and applied the factory reset. Ridiculous that this phone only lasted 18 months, but if I get the $150 credit I will be happy.
Same problem here -- just froze for a few seconds, powered off, and won't turn back on. Not a boot loop issue as there is no response at all from any buttons. Swapping the mainboard from a working phone powered up without a problem, but obviously that's the other phone's emmc.
I tried the freezer thing and it sort of worked- LCD powered on for a couple seconds, but then shut back off again and even that only happened once. That's progress over the usual absolutely no response though... Anyone have insight into why the temperature would matter? something is overheating that this gives a bit of wiggle room since it starts much colder than usual? maybe a more complex analog electronic situation?
I would happily pull the flash chip off and put it in a emmc reader, but I think I'm out of luck because from what I've read the dm-crypt key is generated from some data stored in in the processor's trust zone thing. I know the "password" but if that's only part of what makes the key and the rest isn't on the flash chip I suppose there's no point in going that route.
I don't care about the hardware surviving; mostly just looking to recover my data. Anyone have suggestions? Hardware debugging direction? I'm willing to buy some electronics test equipment (within reason of course; not picking up a 10000USD rework station for some old photos and contact list...)
d_ckhole said:
Same problem here -- just froze for a few seconds, powered off, and won't turn back on. Not a boot loop issue as there is no response at all from any buttons. Swapping the mainboard from a working phone powered up without a problem, but obviously that's the other phone's emmc.
I tried the freezer thing and it sort of worked- LCD powered on for a couple seconds, but then shut back off again and even that only happened once. That's progress over the usual absolutely no response though... Anyone have insight into why the temperature would matter? something is overheating that this gives a bit of wiggle room since it starts much colder than usual? maybe a more complex analog electronic situation?
I would happily pull the flash chip off and put it in a emmc reader, but I think I'm out of luck because from what I've read the dm-crypt key is generated from some data stored in in the processor's trust zone thing. I know the "password" but if that's only part of what makes the key and the rest isn't on the flash chip I suppose there's no point in going that route.
I don't care about the hardware surviving; mostly just looking to recover my data. Anyone have suggestions? Hardware debugging direction? I'm willing to buy some electronics test equipment (within reason of course; not picking up a 10000USD rework station for some old photos and contact list...)
Click to expand...
Click to collapse
The only way to connect that buddy to PC is to get SoC (CPU) working, so theoretically you can go towards reballing the chip. But I guess it's not an easy thing for such a little chip. Also u will need kinda plate for balls, i think there are no common ones, so u can make it yourself if have a technical education.
Another way is to connect memory right to PC without a phone but with some connector. IDK if there are any available, but this looks much more simple. I actually got the same happened, and tried to heat the plate, but with particular success.
IMHO
orcgoblinsupply said:
Another way is to connect memory right to PC without a phone but with some connector. IDK if there are any available, but this looks much more simple. I actually got the same happened, and tried to heat the plate, but with particular success.
IMHO
Click to expand...
Click to collapse
Here's the reader
https://www.amazon.com/ALLSOCKET-eMMC169-Programmer-Kingston-Interface/dp/B06Y55DKND/
But I assume the problem is I will not be able to generate the encryption key because part of it is in the processor.
If someone has tried this and it definitely works, I'll give it a go. Just don't want to buy the emmc reader and heat gun this chip off if it's certainly a waste of time.
d_ckhole said:
Here's the reader
https://www.amazon.com/ALLSOCKET-eMMC169-Programmer-Kingston-Interface/dp/B06Y55DKND/
But I assume the problem is I will not be able to generate the encryption key because part of it is in the processor.
If someone has tried this and it definitely works, I'll give it a go. Just don't want to buy the emmc reader and heat gun this chip off if it's certainly a waste of time.
Click to expand...
Click to collapse
I've seen a post of a guy who sent his motherboard to china and got reballed it and gained 4gb of ram. Can be wrong, but it was around $50 and a month of time.
---------- Post added at 04:46 PM ---------- Previous post was at 04:40 PM ----------
Actually found the post itself: https://4pda.ru/forum/index.php?showtopic=722679&st=3440#entry68093395 (it's in russian, so u're welcome at translate.google.com) In short - a guy fount a Chinese service and men in the middle who could resend his motherboard to china, it cost him $100