Related
Hi,
I've just joined after getting linked to this site. Seems like a huge site with plenty of info but unfortunately after a few searches I haven't been able to figure out my problem.
I recently followed a guide on here for replacing the digitizer on my xperia x10 and I followed it to the letter. After re-assembling the phone it refuses to switch on and there is no response when I connect the charger.
A little history.....
The problem started when I dropped the phone in water. I know I have been told that it would never be right again etc etc but I did everything I could to dry the phone and for a couple of months after the incident the phone would switch on and display perfectly and the buttons would work fine also. The only problem was that the touch wouldn't work rendering the phone useless as I couldn't even unlock the screen.
Anyway, every now and again I would switch the phone on again to cHeck if it had made a miraculous recovery but no joy. After asking some questions I decided to replace the screen/digitizer. I remember the last time I tried switching the phone on a few days before taking it apart it wouldn't switch on. It simply gave out a few flashes from the LED. I put this down to the battery being dead and carried on replacing the digitizer.
The only response I get from the phone now is when the charger is connected to my laptop and I remove the battery, the LED gives out a red flash every 2-3 seconds. Although this doesn't happen all the time. Most of the time I get nothing at all. I must add that I did charge the phone at least once or twice successfully after the water incedent so something else must be causing this.
I have heard of issue with these phones not charging but I don't see why this would happen to mine if it wasn't even being used. The phone was only a month or two old when damaged.
Sorry for the long winded introduction and if anyone has any ideas I would greatly appreciate hearing them.
Thanks,
Gav.
anyone had any similar problems to this before?
I know this is an old thread, BUT my X10 won't switch on either now :/ not dropped it ever and ive never got it wet, i turned it off due to it being laggy and unresponsive and now it won't turn on :/ no ROM's not rooted just stock anyone have a fix ? and no i have tried putting it in the computer for the SEUS to fix it but nothing unresponsive
Guys I owned a Galaxy SIII white GT-19300... had it for 3-4 months, bought it brand new. used really carefully, only had one or two falls that's it.
Finally it decided to crap all of a sudden like it had a silent heart attack, just a couple of hours ago. It wasn't charging or was in process of updating or anything. Just that I was sitting and having a sms conversation where in the middle it just won't budge at all. It just went completely pulseless.
These are the symptoms:
-No display
-Won't power up by any means
-No charging light
-No sign of booting up
What I tried:
-Hard reset
-Remove SIM and SD card, still no activity
-Swapped battery of working S3
What should be the next step?. Thankfully warranty period hasn't elapsed yet.
How should I approach now?. Will the warranty company replace the set or more likely create some unsolvable obstacles, like them assuming fall or label the phone rooted etc?
Thanks for your time
saadxe said:
Guys I owned a Galaxy SIII white GT-19300... had it for 3-4 months, bought it brand new. used really carefully, only had one or two falls that's it.
Finally it decided to crap all of a sudden like it had a silent heart attack, just a couple of hours ago. It wasn't charging or was in process of updating or anything. Just that I was sitting and having a sms conversation where in the middle it just won't budge at all. It just went completely pulseless.
These are the symptoms:
-No display
-Won't power up by any means
-No charging light
-No sign of booting up
What I tried:
-Hard reset
-Remove SIM and SD card, still no activity
-Swapped battery of working S3
What should be the next step?. Thankfully warranty period hasn't elapsed yet.
How should I approach now?. Will the warranty company replace the set or more likely create some unsolvable obstacles, like them assuming fall or label the phone rooted etc?
Thanks for your time
Click to expand...
Click to collapse
Warrant may be void if its rooted or custom rom or modified status or rom counter above zero .
No way to reset those on a non booting phone .
Dropped damage incurred again who knows until they take the phone apart .
jje
JJEgan said:
Warrant may be void if its rooted or custom rom or modified status or rom counter above zero .
No way to reset those on a non booting phone .
Click to expand...
Click to collapse
If the phone's truly hard-bricked, there's no way the service center would be able to discern that. Dead is dead.
Agreed, if the phone is truly dead no one in the sammy repair could able to detect that.
Sent from my GT-I9300
I'm sorry but I have to disagree, just because the power port has died, by no means means the memory/storage, or anything else for that matter really is down.. (not that it'll come up, just making a point)
it sounds like you really did everything right to troubleshoot it huh.. well let me just throw a few things out, you probably didnt, but hopefully did overlook..
the cord you're trying to charge it with, could it be not working/charging it?
have you tried another cord, or maybe even a USB cord? was it plugged in when it died? some low quality/defective cords can have some weird effects on phones, like less responsive digitizers, or even short out a phone
did you have any custom CPU settings? over/under clock/volt? had you played with you min/max CPU settings?
it doesn't turn on, did you determin this by seeing no display? seeing if there's any hapticfeedback, or even calling it from another phone and seeing if it rings on the callers side.
I know it seems silly but I'm just throwing out things from personal expirence ..
so now your phone really is dead, well having it under warrenty is great. having worked at an AT&T corporate retailer, I can tell you what happens on our side when you bring in a damaged phone.. well try it ourselves, well ask what happened, if you don't know well ask things like, 'did you drop it', 'or it was in contact with water'. (were actually required to ask, since these things aren't covered under warranty. which let me say, is so broken that we push the extended warranty on you, because it covers basically nothing.. we have a quota that says we need to sell X amount of a list of product/services each month.. but I digress).. anyway, once you tell us it just died out of nowhere we take your phone, put it in an envelope and ship it back to the manufacturer. in the mean time well offer you a loaner phone if you need one (just whatever we have on hand at the time, usually phones we get from trade-ins) (you keep your battery and sim) , and we put a 50 dollar hold on your card (yes on a creditcard, not your account) until your phone comes back in and we get our loaner phone. they'll send you a phone back to us, not yours, usually a refurbished version, then we call you and let you know your phones ready.
NEVER have I ever seen or heard anything ever of checking for root. most of our reps don't even know what that is.. once we submit a replacement form, the new phone is on transit to our shop usually by the next day (meaning they send out the replacement before they get the one we sent).
my advice is once you're sure the phone is dead, take it in to your retailer, tell them it died out of nowhere while you were texting, and it won't turn back on. you don't need to go into anymore detail than that..
clearly I have a problem with rambling this morning haha so ill stop talking there. if you have anymore questions tho, ill be happy to answer. goodluck!
Sent from my GT-I9300 using xda app-developers app
soraxd said:
I'm sorry but I have to disagree, just because the power port has died, by no means means the memory/storage, or anything else for that matter really is down.. (not that it'll come up, just making a point)
it sounds like you really did everything right to troubleshoot it huh.. well let me just throw a few things out, you probably didnt, but hopefully did overlook..
the cord you're trying to charge it with, could it be not working/charging it?
have you tried another cord, or maybe even a USB cord? was it plugged in when it died? some low quality/defective cords can have some weird effects on phones, like less responsive digitizers, or even short out a phone
Click to expand...
Click to collapse
Didn't mention it. I underwent much thoroughly then what I typed.. Yup tried 3 different cables, couple of chargers, usb cable.
And no it really wasn't plugged in. I really was expecting a sms at that time, when it took too long, I took it out from the pocket and voila DEAD!
soraxd said:
did you have any custom CPU settings? over/under clock/volt? had you played with you min/max CPU settings?
Click to expand...
Click to collapse
No didn't.. was too scared to try that!
soraxd said:
it doesn't turn on, did you determin this by seeing no display? seeing if there's any hapticfeedback, or even calling it from another phone and seeing if it rings on the callers side.
Click to expand...
Click to collapse
Tried everything you mentioned and even more then that!
yup lifeless like a brick.
** By the way an incidental finding found before claiming warranty. While having the battery in the phone. It was still warm. Removed it. Became cooler, upon reinstall, it became warm again. What gives??!
It's more like a phone in coma!
soraxd said:
I know it seems silly but I'm just throwing out things from personal expirence ..
so now your phone really is dead, well having it under warrenty is great. having worked at an AT&T corporate retailer, I can tell you what happens on our side when you bring in a damaged phone.. well try it ourselves, well ask what happened, if you don't know well ask things like, 'did you drop it', 'or it was in contact with water'. (were actually required to ask, since these things aren't covered under warranty. which let me say, is so broken that we push the extended warranty on you, because it covers basically nothing.. we have a quota that says we need to sell X amount of a list of product/services each month.. but I digress).. anyway, once you tell us it just died out of nowhere we take your phone, put it in an envelope and ship it back to the manufacturer. in the mean time well offer you a loaner phone if you need one (just whatever we have on hand at the time, usually phones we get from trade-ins) (you keep your battery and sim) , and we put a 50 dollar hold on your card (yes on a creditcard, not your account) until your phone comes back in and we get our loaner phone. they'll send you a phone back to us, not yours, usually a refurbished version, then we call you and let you know your phones ready.
NEVER have I ever seen or heard anything ever of checking for root. most of our reps don't even know what that is.. once we submit a replacement form, the new phone is on transit to our shop usually by the next day (meaning they send out the replacement before they get the one we sent).
my advice is once you're sure the phone is dead, take it in to your retailer, tell them it died out of nowhere while you were texting, and it won't turn back on. you don't need to go into anymore detail than that..
clearly I have a problem with rambling this morning haha so ill stop talking there. if you have anymore questions tho, ill be happy to answer. goodluck!
Sent from my GT-I9300 using xda app-developers app
Click to expand...
Click to collapse
Thanks for the detailed reply man, really appreciated. Especially since I was already trying to read the minds of these warranty dealers!
So just a while ago I gave it in for warranty. I was adamant of it going dead while I was doing an sms (although true!).. just said no to whatever cause they tried to find (wasn't any, honest!). They were pressing me though for the graze it got (a month ago).. I said 90% of the phones are scratched, and how many do die? He went okay we'll see then, 'yeah you are right we buy that, most that gets damaged from a fall is a phone with shattered screen!"'. Next question, the tricky one!. Did you modify/update software?
I was like, I keep my phones as stock and was totally acting alien to terms like 'rooting' 'firmware' 'kernel' etc (not being honest, but i'm sure that's not the cause)
He was like okay hand it over, we'll do the rest!
Hopefully they don't ever get to revive the mobo or i'm screwed for real!
my phone just died after flashing morfic A10 kernel. i am running stock rooted rom and the best part my sgs 3 was bought 11/18/12 from target, cant go to download mode, cant go to recovery i even tried adb recovery and download mode hoping to turn on nada, charge for an hour no led flashing. my sgs3 totally dead. called target and they said just bring it and they will replace it with new one if the phone wont turn on. is that mean i will be okay even my phone is rooted?
UPDATE:
Thank God.. got my SIII fixed in warranty, now it's back to life!
Just had a motherboard replacement, no further details given.
Hence kind of proven!:
if the phone is truly dead no one in the sammy repair could able to detect that.
Click to expand...
Click to collapse
Hi everybody,
Since this morning, my Huawei Honor U8860 on Gingerbread (stock ROM) keeps showing me the Power Off menu that is usually obtained when one presses the Power button for 1-2secs. After putting the haptic option on, I can say that it pops up every second almost, as this mode makes the phone vibrate when it appears.
I'd like to know what to do to solve this problem, because it prevents me from doing anything with my phone.
Here is what I did so far :
- After a while, I figured that if I pressed continuously the Power button, the menu stops poping up, so it's like the button is working reverse if I'm not wrong...
- Inspired from 'droidforums.net/forum/droid-2-general-discussions/88196-disable-power-options-while-locked.html' I tried then to deactivate this button. So after I rooted my phone, I installed a file browser/editor and modified the following files :
- /system/usr/keylayout/qwerty.kl
- 'key 116 POWER' changed from 'WAKE' to ' ', then to 'NONE', did nothing, then to 'WAKE_DROPPED' , stopped the popup for 10mins, then not anymore- did the same with surf_keypad.kl and touchscreen-keypad.kl with the 'key 87 POWER' as I didn't know if it was useful or not, so just in case.
- Installed 'Button Remapper' to see if it could help, but when I change the POWER button to WAKE_DROPPED or NONE, it doesn't do anything...
So if anybody has an idea to either deactivate the Power Off menu, or maybe deactivating completely the Power button as I tried (I would prefer the first solution, but it could work), you're welcome!
Thank you in advance for any piece of advice.
P.S. : The only reason I could find for this sudden change in behavior is that yesterday night I biked under a hailstorm, so maybe it got humid. But the problem appeared only this morning as I used my phone fine last night...besides the hail didn't really soak like rain, and my phone worked under rain many times before, so I'm really not sure...
So I let my phone on the whole night and it's still doing it, and I'd like to mention that as the Power Off menu continuously pops up, the screen is always on, which kills the battery.
So even though I found a temporary solution by pressing continuously the Power button to make the phone work properly, it's not gonna be a viable solution as the battery is probably not gonna last more than 8-9h...
So if someone has a solution, you're welcome ^^
Up!
I still didn't find any solution to my problem, if anyone has a solution, he's welcome
Hey
I've just started to have to same problem, with my Huawei Honor. a long time ago someone spilled some beer over my phone, and it went crazy for a long time, but then it started to act normal again, and i thought the trouble was over. But now i have the exact same problem, it's like my power button is stuck, i think that we need to change the power button itself or clean it. But so far i haven't succeeded..
And here is a fun fact for you, if you switch to Airplane mode (no antenna signal) or just remove the simcard, you wont have any trouble with the phone at all! Well except that fact that you can't call or receive calls..
Have you done anything after your last post?
Best regards
Alcohol + Glassbrush FTW
Duuude! I solved it!
First i took the motherboard apart and soaked/bath it in alcohol 93 % for about 30 minutes and then dry it the night over.
This morning i brushed the motherboard with a glassbrush (That's what is called in Denmark, it's a fine brush made of tiny glass straws), And voila the phone is now working without a complaint!
I'm not allowed to attach a link to my post so do a googlesearch for: "glasbørste" and look at picture no. 6
I had the same problem as you, a few days after the rain episode everything was fine again, and since then, it happened two times, for like two days where the problem appears again, but then it just goes away.
I don't think I am ready to soak my MB in alcohol and brush it after, so I'll just bear with it ^^
But thanks for the info, and maybe it can help some other people (even though I'd wait a month or two to see if it doesn't do it again after your bath, but let's keep our fingers crossed)
I'm also hitting the same issue for past one month. So not able to use the phone at all. Recently went out of warranty.
Any other solutions?
maniabbas said:
I'm also hitting the same issue for past one month. So not able to use the phone at all. Recently went out of warranty.
Any other solutions?
Click to expand...
Click to collapse
I had the same problem and i managed to work it out. Firstly i dissembled the phone so i had the motherboard by itself, search on youtube for guide. Then i dipped the motherboard in 93% alcohol, for about 30 minutes, removed it and lot it dry the night over. I then brushed all the exposed metal areas with a glassfiber brush (especially on the backside where it connects with the screen). After that the phone has been working perfectly!
I'm not allowed to attach a link to my post so do a googlesearch for: "glasbørste" and look at picture no. 6
It's a bit complicated but i managed to do it and i'm not the biggest handyman or phone geek, so it's possible. And the phone is just about useless if you do nothing, so you might just as well give it a try.
If it's too much work for you, you can hold the power button when you want to use the phone, this stops the button error..
Best of luck, let me know how you're doing
penpex said:
I had the same problem as you, a few days after the rain episode everything was fine again, and since then, it happened two times, for like two days where the problem appears again, but then it just goes away.
I don't think I am ready to soak my MB in alcohol and brush it after, so I'll just bear with it ^^
But thanks for the info, and maybe it can help some other people (even though I'd wait a month or two to see if it doesn't do it again after your bath, but let's keep our fingers crossed)
Click to expand...
Click to collapse
Same thing happened to me... when water went inside my phone... the POWER MENU was appearing continuously .. when i went to service center they said.. MOTHERBOARD needs to replaced... and the price quoted was equivalent to new device...:crying::crying:
After going thu this youtube video i finally managed to un-assemble my phone fully .. and used HAIR DRYER to for about 4-5 mins...
And than phone started working normally...
Hope it helps some else with the same issue:good::good::good:
Hi guys! I'm new around here, I've been lurking the forums for the past year or 2.
I originally had a i9000. Had it rooted, flashed & running 4.2.2 Hellybean, it was a dream, easiest android phone i've ever dealt with.
Today, I bring you a device that is so mind boggling and mysterious, it's ridiculous. Before you ask, yes I've searched and searched countless hours on end & sleepless nights. Trying to work out how to PERMANENTLY fix this device.
Straight up, I'm going to tell you what I've done, what I've tried, where the phone came from, model of the phone & all the useless stuff.
OKAY. Go.
I got the Samsung Galaxy S2 (i9100T) off a friend recently, about a month or two back. He didn't have a back cover for it, and the camera was all smashed up (back camera). It was running on 4.1.2 Vodaphone Stock DVLSH. It had a few issues when the phone got to me.
I wasn't sure if the phones battery was depleted, but I had to muck around with the phone for a couple of hours just to get the damned thing to turn on.
When I had got the phone to turn on, I kept getting "Warning! Battery Disconnected!" messages, this was frustrating. I eventually let the phone fully charged before I mucked around with it and ignored the warning.
When it was fully charged, I went straight to rooting it. I first rooted it by flashing CF-Root and then flashed a custom rom. (Xylon AOKP. 4.2.2)
From here on, the phone started to randomly restart, drop signal, lose battery after random restarts, get semi boot loops.
So I flashed a different stock (XWPL8) and got rid of the Samsung Galaxy SII i9100T boot logo and it was changed to Samsung Galaxy SII i9100.
After this, I then again rooted the phone but this time a different method and used Siyah kernel and flashed Carbon rom 4.2.2.
I still encountered the same problem as Xylon 4.2.2.
So I kept reverting back to stock, re-rooting & trying again.
I've tried countless methods.
POSSIBLE HARDBRICK RECOVERY DON'T TAKE MY WORD THOUGH: I've even managed to HardBrick the device (yes I mean hardbrick, i didn't even JTAG to bring it back... I flashed Dorimax Kernel at some point and it hardbricked it to all ****.) I spent a few days trying to unbrick it when finally I just plugged it into the charged and forced it to internally turn on (i believe) and let the battery deplete (the phone was hot even when i unplugged it. So I let the battery drain.) Yes I even battery pulled and tried to reboot it to see if I could boot recovery or download or the rom even before I tried any of this! (absolutely nothing.)
I took out my SIM card after a full day of letting it drain (just to be sure) plugged it in, took out the battery while the charger was plugged in, put the battery back in, unplugged the charger while holding power, and plugged it back in and I got the charging logo booted into download mode after 80% charge and flashed stock again.
Now the problem(s) with the phone:
SEMI-BOOTLOOPS: Every time i've rooted the phone and even flashed different roms just to make sure, it does a "semi boot-loop" I've searched everywhere for people with the same problem but found nothing on it.
What it does, is it turns on (boots the samsung logo.) turns off, turns back on, turns off, turns back on etc and then after about 2-8 times of doing is usually it boots to the ROM and the phone works for awhile.
RANDOM REBOOTS: I don't get these much anymore since I found a solution where someone had just folded up a receipt and pushed the battery up against the prongs because it had about .5mm movement off the prongs. This fixed most of the random reboots and don't see many anymore.
SLEEP OF DEATH!?!?!? OR JUST A BLACK SCREEN THAT DOESN'T TURN BACK ON!?: This one I'm not 100% sure what it is, I read it's the S.O.D (Sleep of Death). Which is common on 4.0.4 and was apparently fixed in later Android versions. But sometimes, when I lock my phone, or my phone goes to sleep, the screen stays black even after I press the home button or the power button, at first I thought just restart it by battery pull or holding down power like everyone says, yeah it works, my phone boots up and does a semi-bootloop and goes back on eventually, but one day I left it on in the mysterious S.O.D. and waited 5-10 mins pressed the power button and it unlocked... This one really has me baffled and it does it a LOT.
REALLY BRIGHT SCREEN AFTER REBOOT SOMETIMES!: Okay, so sometimes when the phone finally turns on, the screen is really bright, like the brightness is still on half, but it's a lot more noticeable on how much brighter it is, it's nearly like a white.
It's really really BRIGHT. Phone shouldn't be able to look/get that bright. After a reboot though it goes away and goes back to normal but this leads me to believe something to do with the battery just a hunch.
RANDOM FREEZES!??!?: Sometimes the phone will just randomly freeze, I can be doing something and it'll just freeze, it won't turn off, I still get picture on the screen but it's frozen and I can't do anything until I either battery pull or reboot it by holding down the power button.
Before anyone asks, yes, I Factory Reset from recovery, Wipe Cache & Dalvik Cache before, I flash a new rom etc.
- My GApps matches with my Android versions each time.
- The ROMs I have flashed are compatible with my phone.
- And I've made sure everything I have done is completely compatible with my phone and android version.
What I think!:
SEMI BOOT-LOOPS:
This one, I don't think much of, it's got me baffled. It could be something to do with the Boot-Loader, could be something to do with a bad flash (but I've even tried double flashing a single rom.)
the eMMC could be damaged in a certain way that it causes these self proclaimed "semi boot-loops"
RANDOM REBOOTS:
This one, I've pretty much fixed with the help of lurking the internet over and over for hours, so this indicates a battery problem, will be replacing it this week. (Yes I'm aware that this battery problem could be causing everything else to play up and that it could all be due to the battery but can we leave the battery out of this just for now so I have more options on how to fix it.)
SLEEP OF DEATH!?!?!? OR JUST A BLACK SCREEN THAT DOESN'T TURN BACK ON!?:
I believe that this could be due to either a high load on the CPU (maybe not so much high but a really low load that it goes into a state of nothing for awhile.) It drops into a mode where it's turned off (something bigger than deep-idle.)
REALLY BRIGHT SCREEN AFTER REBOOT SOMETIMES!:
I haven't changed voltages or messed with any voltages on my phone, but I believe that it does indeed have something to do with the CPU & GPU voltages or even the BATTERY Voltages either undervolting or being to high.
RANDOM FREEZES!??!?:
I think this one is something to do with my phone not liking the voltages stock set to it.
I read that somewhere Freezing the System Alarm Clock can fix the random reboots, so I've done that and also pushed the battery up with a bit of receipt so it touches the prongs completely.
Anyway, right now, the phone is on Stock Kernel with CWM Recovery6, with PacMan's 4.3.1 Nightly release on XWLP8 Baseband and it still does this all.
I know i'm asking for a lot of help and I'm probably going to get yelled at by Devs or forum mods or some body because I've done something wrong.
But if it doesn't belong here, move it please.
IT TRULY IS A PHONE FROM HELL.
-Thanks, Just another man who wants to fix silly problems for fun.
Youve said "dont mention get a new battery".What if that is the problem.
Maybe the phone has water damage, or it needs that hawkerpaulls scripts run.
Youve just got to try free stuff, then maybe splash a bit of cash I.e battery.
Nothing software/firmware-side is fixing this. Phone has major hardware issues going on. I wouldn't bother beyond trying the 'free stuff' TheUnderling mentioned.
erm - I'm agreeing with you on this 'phone from hell!' also agree with @theunderling and @MistahBungle - it doesn't sound like its worth fixing if the free stuff doesn't work - sounds like it would probably be cheaper to buy a second hand s2! Don't think dori kernel had anything to do with your 'hard brick' - I've been running dori for some time including the experimental builds, dori tests everything himself as do his team of testers - the 'd team' and I have never known him to release anything that even soft bricks let alone hard bricks.
Good luck :cyclops:
Hey guys thanks for the speedy replies! I love waking up to instant replies!
theunderling said:
Youve said "dont mention get a new battery".What if that is the problem.
Maybe the phone has water damage, or it needs that hawkerpaulls scripts run.
Youve just got to try free stuff, then maybe splash a bit of cash I.e battery.
Click to expand...
Click to collapse
Sorry, I was half asleep when writing all this! I am getting a new battery this week! But I wanted to have a go at trouble shooting it but crossing out the battery from the list of problems seeing as it's being replaced this week @theunderling
MistahBungle said:
Nothing software/firmware-side is fixing this. Phone has major hardware issues going on. I wouldn't bother beyond trying the 'free stuff' TheUnderling mentioned.
Click to expand...
Click to collapse
It may sound like it @MistahBungle but I have faith and I come down to being very patient with technology even when I do reach ticking time bomb mode. I believe I can fix it if I just get the right help !
If the new battery doesn't do anything, It might be the logic board and i'll just go buy a new one.
Jimsilver73 said:
erm - I'm agreeing with you on this 'phone from hell!' also agree with @theunderling and @MistahBungle - it doesn't sound like its worth fixing if the free stuff doesn't work - sounds like it would probably be cheaper to buy a second hand s2! Don't think dori kernel had anything to do with your 'hard brick' - I've been running dori for some time including the experimental builds, dori tests everything himself as do his team of testers - the 'd team' and I have never known him to release anything that even soft bricks let alone hard bricks.
Good luck :cyclops:
Click to expand...
Click to collapse
@Jimsilver73 It really is!
I'm not the most wealthy person or have money to just throw at things like new phones etc etc. I'd love to see what I can do on my side and try and trouble shoot every problem for even the simpilest of DIY Solutions. I get a kick out of mucking with phones and computers.
Your probably right, but I was thinking that does Dori kernel keep stock voltages or does it change the voltages at all? Because it just managed to Hardbrick its self a few hours after flashing it which was odd, which led me to suspect that my phone didn't like the Dori Kernel & Carbon Rom Combination!
@theunderling I will try that Hawkers script by the way!
Is this the one? http://forum.xda-developers.com/showthread.php?t=2100558
Phone having no back cover and camera smashed suggests that there is a physical damage to the phone, i wouldn't even try battery to this one, it may just kill the new battery if there is some kind of water damage, tho you seem like having fun trying to repair it Yes, that's hawkers script, use it and couple of ROMs, (ICS,GB etc) to see if there is a software problem. If you can dissamble it, you can check if there are some contact problems between pieces.
Hi @Dakura thanks for the reply!
The camera isn't smashed completely, but at fist I thought that the camera would be screwing up the phone in someway.
I know for sure as well that there is no water damage, and the phone was just sitting around he lost the back cover randomly after he had bought an iPhone 4S.
I can disassemble it, I just need to find my little screw driver I use for stand-off changing on PC cases.
I read somewhere that the proximity sensor has a bit to do with things, so seeing as the back cover isn't on, that maybe dust got into it while it was in his draw and that's the reason for screen-offs? because the phone is still responsive. I can receive calls & text messages just the screen is black and doesn't come back on.
The warning in 4.0.4 "Warning! Battery Disconnected!" leads me to think that in versions above 4.0.4 (4.1.2 for example) don't have warnings and the phone just turns off.
**major update**
@Dakura @theunderling @Jimsilver73 @MistahBungle
Hey guys, so I've just taken the back CASING not the cover. Off the phone.
I've been looking for breaks in solder points on the Logic Board and around it.
- The Camera ISN'T smashed it was the lens on the case..
- Looks a tad dusty.
- Semi Boot-Loops have disappeared! booted the phone with the case off and the semi boot loops are gone tried booting multiple times each time with success!
- No breaks on the logic board from what I can see as far!
- For some reason the Camera app would not connect to the Camera. "Can't connect to Camera!" maybe the camera flex cable isn't in properly.
- First boot with case off, battery gave false reading of -1021032418914 (something along those lines). That's usually caused by a lose battery correct me if I'm wrong?
- Everything seemed a lot more responsive and working.
Hmmm.
So removing the screws and taking the back casing off made the Semi Boot-Loops go away.
Maybe a part of the back casing was pushing on the Logic board and shorting it out?
Maybe the screws torque where messing with it (e.g. on a HDD with computers the simpliest change in toque on the screws in the HDD can screw the HDD.)
But the torque of the screws where very loose.
Any ideas are much appreciated!!
Yep, probably a short-circuit or dust problem or displacement somewhere around there. What you said proves that somehow the phone was physically damaged. You may need to actually disassemble all the pieces, inspect them and put them all back together, and it still may not work, for now, try cleaning the dust and tighten the screws, fasten the board.
@Dakura thanks for the help today Dakura!
Finally got around to putting everything back together after an evaluation, made the flex-cables all snug and tightened up the screws a lot!
The phone appears to be working now.
at 100% it even vibrates now when i tap things it never used to.
I couldn't quite locate the problem, but I have a feeling that one of the flex cables could have come loose but only just enough to generate fluctuation of power between full and under to keep the phone on.
Hopefully the phone stays stable!
@theunderling thanks for recommending me HawkerPauls Nuke script, I'll be using that every time I re-rom my phone from now on!
Will update the thread on a possible fix for anyone else with this problem.
It's always good to run through every possibility and solution to fix problems before going out and blowing money.
Hi, I have a problem with my T399n.
My phone doesn't turn on, I installed CM12 and it was good, then I flashed the stock ROM from metro again, everything was good about a month, one day I made a call, whatsapp, text and then I put it in my pocket, then when I pulled it out like 10 minutes later and it was rebooting, I didn't pay attention to this because sometimes my phone reboots itself, later It was power off. I pulled the battery, reinserted it and nothing, connected usb cable, nothing, tried to charge it and nothing, Its like my phone died. Looking for a fix, there is the usb jig that work with others galaxy's.
So I just want to know if I'm fried or if there's a last hope to revive this phone with the usb jig
Thanks!
Something similar to this happened to me, would love to know the answer...
just today...
just today, not 2 hours ago at most I was playing around with my galaxy light, deciced to root and mod it.. first step was to, ofc flash a custom recovery... well like most things I pursue I ended up fighting the damn thing for HOURS!! could not get it to register on my computer for the life of me.. now I'm far from a dev and probably one of the least experienced on/around here but something so trivial as lack of drivers, udev, faulty port/cords isn't my forte.. so eventually I whipped out my handy dandy usb jig and .... nothing... *head scratch* hmmm.... now its got my attention... so I get out the multimeter usb data/charging cable and it does show signs of life, easily registering 5.1v / 0.4 mah ... now I'm getting anxious.... so its time for the next test... usb-otg connected to dbl usb-type-A converter to connect to the pooter (it never works but I wish it would ) and nothing there... so otg to my main mobile, reverse it... hmmm seems this lil guy is taking in charge and no data xfer of any kind... since id already rotated various cables I turned my attention to the charging port.. under 6x magnification and too many lumens light I could hardly see any problems but persisted with the 99% isopropyl anyhow... end result "wtf is wrong with this garbage....?) and just as I went to throw it at the wall I spotted my personal "boneyard" where all of my former problematic/faulty devices end up and just in sight was another tmobile galaxy light, broken lcd but logic board intact.. so a quick flip of the wrist and a smack on the back and the 2 became one... fired her up, plugged it in and BAM.. instantly detected... and for some reason I cant quite seem to put my finger on, I had the urge to power it back off and insert my usb jig one final time to see if it infact would work with the galaxy light.... *device in left hand... jib in the right.... bead of sweat steadily sliding down my ruffled brow... time seemed to all but come to a screeching halt as the two came closer until the moment of trust had arrived... the initial contact, the penetration (lol) .. the pause... BOOM factory mode*
so, now that u read that half illiterate rambling from a barely educated redneck shut-in to determine if the usb jig works with galaxy light or not .. the answer is yes... it does unless its a piece of crap like one of the 2 I own is...
KatharsisSoul said:
Hi, I have a problem with my T399n.
My phone doesn't turn on, I installed CM12 and it was good, then I flashed the stock ROM from metro again, everything was good about a month, one day I made a call, whatsapp, text and then I put it in my pocket, then when I pulled it out like 10 minutes later and it was rebooting, I didn't pay attention to this because sometimes my phone reboots itself, later It was power off. I pulled the battery, reinserted it and nothing, connected usb cable, nothing, tried to charge it and nothing, Its like my phone died. Looking for a fix, there is the usb jig that work with others galaxy's.
So I just want to know if I'm fried or if there's a last hope to revive this phone with the usb jig
Thanks!
Click to expand...
Click to collapse
It does in fact work. If asking about the USB mount, from my knowledge you would've had to already installed them by turning the function on like I did in the first screen shot.
If you need them I can link them to my drive or mega. Whichever is best. Think I have drop box still too.
And yes. I have bricked this phone I'm using now for a solid 3 days when I first started with it. However cm12 has bugs, after the second time it rebooted and bricked on me I went back to Tigerlily I even had no SIM error but somehow fixed that when flashed back to stock. Cm12 caused me to flash back to stock about 3 times a day. Too much headache. Guess thats why we are not supposed to do this to our primary phones. on tigerlily ive Had a little trouble keeping super su in his place too, Got home last night and POOF, just gone for no known reason. finally got him to stick by installing him into the system with lucky patcher. Flashify, flashfire, and even rom installer all failed to keep him there. . I have also stripped down almost every file just for fun to see what other fine items I could damage, Finally found where they hide the dialer codes for the phone. They are not in any files that i have spent the last for years looking in. The codes are inside of the APK. The last place I decided to look. Everything I know is self taught and just recently started working with apps for windows 10 and merging android files into windows apps.
Now , I'm actually quite impressed with it's capabilities .
Really what's helped me dial everything in was the helped of an app called Mixplorer with all the ad-on's all of which are free.
Good luck with your brick. Myself, I have 3 other phones I'm currently working on unbricking. One of which is a hard bricked LG motion. Flashed th err wrong firmware to it a year ago. Just this week got the cup to recognize it. the code to get into the first service menu pictured here on the bottom left is *#0808#
Really what's helped me dial everything in was the helped of an app called Mixplorer with all the ad-on's all of which are free.
Good luck with your brick. Myself, I have 3 other phones I'm currently working on unbricking. One of which is a hard bricked LG motion. Flashed th err wrong firmware to it a year ago. Just this week got the cup to recognize it.
when youre ready to really see whats going on you can dial *#9900# for all the System Dump features.