Hey, I really need some desperate help.
So I have a Canadian Note 2, SGH-I317.
It has no SIM card inside it, and it is just connected to wifi.
I have flashed 2 Custom ROMS before on this phone.
The first one, was a 4.4.2 Homemade t0lte ROM.
It worked fine for about a week, but then I started to have this big problem.
After I plugged in my friends charger at her house, (a Samsung Note tablet charger) then this problem started shortly after I left her house:
When I leave the phone alone, it will go to sleep automatically like every other phone. Then, when I press any button which wakes the phone, the touch screen is unresponsive, and the phone since no input is coming in, goes back to sleep and doesn't turn on again until after a while, where it will boot back on itself and start working until randomly out of chance (chance meaning atleast once every 1 - 4 hours) it will do the same thing again. It's getting really annoying and starting to be destructive, as it stops important conversations and other stuff.
I initially thought it was the homemade ROM.
So, I changed the ROM. Now I'm using a better one, and it's called W03 Slim v9 t0lte, and it's 4.4.2 and works good.
I was not seeing any problems up until a few hours after the install of the new ROM, and the problem which I thought had been removed was still persistent. Now, its even more often than the old homemade ROM. Just before posting this, it has happened twice in the matter of 1 hour, and it's just getting on my final nerve.
I'm not sure if this is a key factor, but after it goes to sleep, I still see the visible white pixels of the 4.4.2 shutoff effect.
My final thoughts are that it might be the battery, but I have no idea how to get a replacement for that, and how much they cost.
Obviously I can't send it in because the warranty was voided when I flashed the custom ROM.
I really need a solution, and ultimately I could wipe everything and go back to the stock ROM, but that, in my scenario would be a last case scenario.
Thanks, Delbert.
NOTE: Just found out that when I turn it on, and the touch screen is unresponsive, the S pen works with the phone, and the back and menu button doesn't work. But, all physical buttons do. The physical home button works, but all the rest except the S pen works. So I can navigate the phone unless it goes into sleep mode, in that case no matter what I press, nothing will make it come up unless it reboots.
AgentTran said:
Hey, I really need some desperate help.
So I have a Canadian Note 2, SGH-I317.
It has no SIM card inside it, and it is just connected to wifi.
I have flashed 2 Custom ROMS before on this phone.
The first one, was a 4.4.2 Homemade t0lte ROM.
It worked fine for about a week, but then I started to have this big problem.
After I plugged in my friends charger at her house, (a Samsung Note tablet charger) then this problem started shortly after I left her house:
When I leave the phone alone, it will go to sleep automatically like every other phone. Then, when I press any button which wakes the phone, the touch screen is unresponsive, and the phone since no input is coming in, goes back to sleep and doesn't turn on again until after a while, where it will boot back on itself and start working until randomly out of chance (chance meaning atleast once every 1 - 4 hours) it will do the same thing again. It's getting really annoying and starting to be destructive, as it stops important conversations and other stuff.
I initially thought it was the homemade ROM.
So, I changed the ROM. Now I'm using a better one, and it's called W03 Slim v9 t0lte, and it's 4.4.2 and works good.
I was not seeing any problems up until a few hours after the install of the new ROM, and the problem which I thought had been removed was still persistent. Now, its even more often than the old homemade ROM. Just before posting this, it has happened twice in the matter of 1 hour, and it's just getting on my final nerve.
I'm not sure if this is a key factor, but after it goes to sleep, I still see the visible white pixels of the 4.4.2 shutoff effect.
My final thoughts are that it might be the battery, but I have no idea how to get a replacement for that, and how much they cost.
Obviously I can't send it in because the warranty was voided when I flashed the custom ROM.
I really need a solution, and ultimately I could wipe everything and go back to the stock ROM, but that, in my scenario would be a last case scenario.
Thanks, Delbert.
NOTE: Just found out that when I turn it on, and the touch screen is unresponsive, the S pen works with the phone, and the back and menu button doesn't work. But, all physical buttons do. The physical home button works, but all the rest except the S pen works. So I can navigate the phone unless it goes into sleep mode, in that case no matter what I press, nothing will make it come up unless it reboots.
Click to expand...
Click to collapse
your friend's charger could've damaged your phone
i've had a charger that made my touchscreen unresponsive while plugged in... thankfully it didn't do any noticeable permanent damage
all USB chargers are not created equally:
http://www.righto.com/2012/10/a-dozen-usb-chargers-in-lab-apple-is.html
ShadowVlican said:
your friend's charger could've damaged your phone
i've had a charger that made my touchscreen unresponsive while plugged in... thankfully it didn't do any noticeable permanent damage
all USB chargers are not created equally:
Click to expand...
Click to collapse
Thank you for your reply, but if the charger did do damage to my phone, how would it and how does the touchscreen still work with the S pen?
Is there any way to fix this, and if not what do I do?
I have an HTC One X I could use as a backup, but I would like to install a 4.4.2 ROM on it, and with what I've found out I have to root it, which requires a recovery, which recovers an unlock or S-OFF, and when trying to do that, the phone won't connect via USB to my computer. I am frustrated but at the same time sad.
Should I just factory reset my whole phone and erase everything?
Related
Weird, huh? I thought this was an interesting issue and that maybe some of you more experienced pda tweakers with some electronics background might have an idea what's going on.
I recently got a "backup" Excalibur on ebay from a girl who said it was "broken". Nonetheless, I figured it was a good deal for parts considering I won it for only $10.50.
When the phone arrived I was surprised to see it looked to be in fairly pristine condition all around (better cosmetically than my own anyway). So I popped in a freshly charged battery and pushed the power button. Nothing. I pushed and prodded for different lengths of time for a while and it actually did manage to power up one time to my surprise (the battery power did show as being fully charged). Thinking this was odd I turned it off again and tried to repeat it again with no luck. After a while I gave up and decided to try with the charging cable attached.
Viola! Started right up no problems. After unplugging from the charger the phone worked flawlessly and it holds a charge just as long as my main phone (I usually have about half to 2/3rds charge left on my OEM battery at the end of the day). The phone charges with no problems as well.
Anyway, I've gone ahead and wiped out the T-Mobile ROM and installed the HTC English-Spanish 6.0 ROM just like my other phone (love this ROM - it's a later build and slimmed down compared to the last T-Mobile .8 Rom plus it's faster, supports HCSD, Voice tags, advanced JOGGR etc.. ) and it works beautifully with this strange exception.... I always need to plug it in if I need to turn it on after a complete shutdown. If the device "soft-resets" via a program such as spb backup it will start up fine without needing to plug it in, however if for whatever reason you power it off via Quick list or long press of the power button, you will need to plug it in to get it to restart. I've had it for about a week and it's a real gem and workhorse aside from that one issue.
Does anyone have any idea what could be the cause of this? I can't complain since I bought the phone for just $10.51 (with free shipping! but it's driving me nuts just thinking about what could be the cause. I've scoured the web looking for similar cases but I haven't found anything similar to this.
Is it possible that the phone is supposed to hold a "power up reserve charge" in a capacitor/diode to give it the "umph" to turn on and maybe my diode is bad or damaged? <--- please keep in mind that that sentence came from a guy who knows nothing about electronics but remembers his dad telling him not to touch that broken TV set on his work bench because "it holds a mean charge even though it's been unplugged for a couple hours"... so be kind
Any thoughts or ideas would be greatly appreciated! Thanks guys
Interesting development...
I've managed a workaround for the problem so I can do a cold start.
1. Remove the Battery
2. Hold in the power button
3. Snap in the battery while holding the power button
4. Release the power button 2 seconds after the battery is popped in.
Works every time.
Still, I'd love to hear some advice from someone who's a bit more electrically inclined.
Now onto my new problem...........
I've suddenly lost the ability to active sync on this phone and it all started right after I entered the network SIM UNLOCK CODE.
I've done several total resets and even put in old spb backups and a backup from my other Dash running the same rom which activesyncs with no issues. I've uninstalled and reinstalled ActiveSync. Still, this phone no longer connects, while the other does. The one variable I have is that the issue began right after I got my unlock code and SIM unolocked the phone.
I'm fearing that the issue is this...
My other phone was network unlocked while running the T-Mobile stock ROM. I then upgraded to the HTC ROM later with no negative affects. THIS phone was network unlocked AFTER I'd run the HTCunlock program to install the HTC branded Spanish-English 6.0 ROM. I'm wondering if the process of network unlocking doesn't play nice with a ROM designed for a different device ID?
Anyone have any clues what could be going on and whether there's anything I can do to get Activesync back to working on this dash? I really enjoyed using this phone to test out new ROMS and apps before putting them on my everyday phone.
Thanks
GReetings,
So I have searched for a lot of forums to see if there is an answer to this.
So the story goes. I got myself a new phone and put the TP2 in a drawer. After moving, I have a reason to pull it out and get it ready to be used again. However, it wont turn on.
So I figure the battery went dead. I plug it into the charger, the LED lights up, and got to wait a few minutes. After a minute or so, the white HTC screen suddenly comes on the screen, it vibrates one quick, and shuts off again.
I cant power it up, I can get it to boot loader. Really not sure what the problem is here.
Any ideas suggestions would be welcome as I want to put this one back to stock so I can send it to my step-kid for use.
Try charging it for a few hours, while it is closed. If the phone regularly reboots and then switches off, leave it that way.
The idea is to charge the battery enough, so as the phone boots.
had the same prob the other day
what helped here was:
remove the battery and let it out of the phone for a couple of hours (i did it at night). had the battery removed for about 8 hours. put it back in and it worked for me again.
give it a try and let me know!
Ok will try that tonight when I'm heading for bed. Ill leave it to charge while I'm at work because I get tired of hbearing it vibrate every 20 seconds while its charging
kilmarac said:
Ok will try that tonight when I'm heading for bed. Ill leave it to charge while I'm at work because I get tired of hbearing it vibrate every 20 seconds while its charging
Click to expand...
Click to collapse
Did you get it to work? I'm having the same problem. I posted in another thread that had the same problem as you.
Maybe HTC really is pushing an auto kill program.
Sent from my PG86100 using Tapatalk
Unfortunately, it didnt work. I think the phone was probably dropped one too many times and is broken. I cant get it to boot, cant even get into the bootloader. So I have no idea.
Steefje said:
had the same prob the other day
what helped here was:
remove the battery and let it out of the phone for a couple of hours (i did it at night). had the battery removed for about 8 hours. put it back in and it worked for me again.
give it a try and let me know!
Click to expand...
Click to collapse
I also had the same problem I took out the battery and blew on it to get it to cool down and had it sit out of the phone for 10-15mins then put it in the phone and plugged into charger and left it for 30mins then hit the power button.
This reboot cycle happens when my phone dies in android and it works every time for me.
Hope that helps
for future reference, the phone died with a Sim card in it, revived when a Sim card was replaced.
Sent from my cm_tenderloin using Tapatalk
yesterday I had the same problem, boot loader doesn't work. But.... I charged my battery, replaced it, pushed Vol. down + EndCall btn. + Power btn and inserted battery. As a result my boot loader is working now. But after running task 29 and flashing custom firmware my phone doesn't came back alive. I'm looking for solution now. Did anybody have the same problem?
When I'm flashing original firmware the process stops on checking my phone.
Please, give me advice how to solve my problem. Thx.
RHOD*** 32M SS-BC
SPL-0.88.000
MircoP(LED) Wrong Plat(0x0)
MicroP(KEY) Wrong Plat(0x0)
Turbo HW/Turbo SW
TP MFG DATA
501,526 793,854
810,209 211,200
211,855 Calibrated
First off it looks like you are not Hard SPLed so custom ROMs will be a problem for you. Second you have a major error with your keyboard and touch screen. I have a TP2 that took a dip into some water that has the same error - MircoP(LED) Wrong Plat(0x0) and MicroP(KEY) Wrong Plat(0x0). When I first got the phone it would not turn on but would make a noise that sounded like it was crying. I got another TP2 that works fine and swapped the top halfs of the phones because the new one looked like a dog chewed on it. It still worked but in real bad shape. The touch screen that got wet works fine so it is on the TP2 that I use all the time. The wet TP2 will now start up but the keyboard, all of the front buttons but the end key, and touch screen don't work. The touch screen will only register getting touch in one spot. So if you have a software keyboard up only the t will be hit. I Hard SPLed it, ran task 29, and installed a custom rom on it. I have to use My Mobiler to do anything with it. It also will take a battery that has a full charge and drain it to about 50% in about 20 minutes and then claim the battery is dead even on a charger. Something to play with.
With the error you have unless you got it wet you might have a bad flex cable. I would try to fix the error first before trying to change roms.
Thank you for answer.
My phone was HardSPLed and flashed by custom firmware and works fine for half a year. The reason for my situation was broken charger... I think that problem in hardware when I put it on charge, my phone lightly flashed by orange lamp and became can't turn on
You are told that it is looks like it doesn't hacked because I tried to roll it back to original.
Are you sure the phone did not get wet? Everything you describe makes it sound like the phone took a dip. If not, try plugging it into a computer and see if it will charge and turn on.
I resolved my problem krekol, you are right at 100%!!! I took my phone from work-shop and they told me that some water get there, or it was just condensate. As a result oxidation around microphone and some connections.
Now, my phone works fine on WM 6.1 (they flashed it) and somewhy I can't flash Jackos S3 JackFULL 1.7.0. and Rhodium-HardSPL_V2_00R3 too
maybe it is effects of oxidation.... I'm trying flash from my flash-card.
AlexeYM007 said:
I resolved my problem krekol, you are right at 100%!!! I took my phone from work-shop and they told me that some water get there, or it was just condensate. As a result oxidation around microphone and some connections.
Now, my phone works fine on WM 6.1 (they flashed it) and somewhy I can't flash Jackos S3 JackFULL 1.7.0. and Rhodium-HardSPL_V2_00R3 too
maybe it is effects of oxidation.... I'm trying flash from my flash-card.
Click to expand...
Click to collapse
You can only HSPL once. If they (or you) relocked the device, you won't be able to unlock it again unless you can get Olipro/cmonex to take pity on you.
Glad I could help. Here is a small warning. Once a phone gets wet it's days are numbered. You might have a week, a month, or a year but the phone will die. I would plan ahead for the phone to die and keep an real close eye on it.
Sent from my HTC Touch Pro 2 running FRX07.1 using the XDA mobile application powered by Tapatalk
AlexeYM007 said:
I resolved my problem krekol, you are right at 100%!!! I took my phone from work-shop and they told me that some water get there, or it was just condensate. As a result oxidation around microphone and some connections.
Now, my phone works fine on WM 6.1 (they flashed it) and somewhy I can't flash Jackos S3 JackFULL 1.7.0. and Rhodium-HardSPL_V2_00R3 too
maybe it is effects of oxidation.... I'm trying flash from my flash-card.
Click to expand...
Click to collapse
If you need to HardSPL a second time, PM me.
So I'm watching tv, and I plug in my phone to charge it a bit because the GPS had gotten stuck on this morning and I burned my battery down to 40%. All of a sudden I hear it buzzing over and over again...like a reboot loop.
So I pull it out of the charger, pull the battery and let it try to boot. Gives the samsung screen for a moment, then flickers, and again to the reboot loop. Holding down power for 10 sec makes it do the same thing, I can't force it into recovery or DL mode without it bootlooping either! At one point I was able to get to the download mode screen, but just 3 seconds and the screen goes black, and back to bootlooping.
I literally did nothing to it. Only thing I did different today was the GPS got stuck (which it has done before), I rebooted the phone, then when it booted again I went ahead and just shut off the GPS. But this was like 20 minutes before this started happening.
So what can I do? Right now its plugged into my computer charging while off, seems to be the only thing it can do without bootlooping.
Running CM9.1 Nightly 9/3 with included kernel and LC8 radio (I think)
zander21510 said:
So I'm watching tv, and I plug in my phone to charge it a bit because the GPS had gotten stuck on this morning and I burned my battery down to 40%. All of a sudden I hear it buzzing over and over again...like a reboot loop.
So I pull it out of the charger, pull the battery and let it try to boot. Gives the samsung screen for a moment, then flickers, and again to the reboot loop. Holding down power for 10 sec makes it do the same thing, I can't force it into recovery or DL mode without it bootlooping either! At one point I was able to get to the download mode screen, but just 3 seconds and the screen goes black, and back to bootlooping.
I literally did nothing to it. Only thing I did different today was the GPS got stuck (which it has done before), I rebooted the phone, then when it booted again I went ahead and just shut off the GPS. But this was like 20 minutes before this started happening.
So what can I do? Right now its plugged into my computer charging while off, seems to be the only thing it can do without bootlooping.
Running CM9.1 Nightly 9/3 with included kernel and LC8 radio (I think)
Click to expand...
Click to collapse
My first guess is your battery is shot. i was gonna recommend the power button failure but if its staying off it might not be that. but id let it charge fully then try to boot up.
Thanks, oddly after a bit of messing around finally got it to boot up. Immediately backed up in CWM....seems to be acting OK now. Idk what happened...
i'll guess, the USB connector got short-circuited when you plugged in, and it caused a cascade failure that fried the SD card or something else inside the phone
there was a factory defect back then with the old SGS 1 (i9000m) model, they fixed that after the 3rd batch, everyone with an old phone from 1st and 2nd release batches, were able to exchange i for a new one.
however in your case, that's not a factory defect, but you plugged it wrong (my guess)
because it has happened to me before when i plugged it in, but the battery was still not charging even after several minutes, yet the phone was getting really really hot
then i unplug, and plug it back in and got the sound feedback "tuu tuud" and then it was actually charging after a few minutes
the first time around even though the charging icon changed, there was no feed back sound, and that was the key, it was not plugged in properly.
so after that time, i always made sure to verify to make sure the phone was plugged in properly and not just relay on he visual icon.
check back after a few minutes, to make sure the phone doesn't get very hot, and it actually increased 1%
It happened again today! After a full charge overnight and no problems for the day up to a little while ago, I opened my email app, it froze, then proceeded to start boot looping. I'm in class so I don't have my computer to try to bring it out of it...so yeah that sucks...
I do remember when I got it to charge yesterday it showed it was charging for 20-30 minutes, but after I "revived" it, I found it hadn't charged at all.
I have been using a Nokia USB cable to charge my phone since I got it, because it was longer than the cheapie Samsung cable that came with it...but it hasn't ever caused problems before. And it charged just fine last night.
How long is the warranty on these things thru tmobile? I may just swap it out while I still can.
Also on an unrelated note, I upgraded to the LG3 radio because I was meaning to anyways...
I pulled it out of it again! This time I held the power button while putting the battery in, when it vibrated I let go, it vibrated again, showed the Samsung logo, and then booted like normal
May I ask what rom are you currently on?
datrapstar said:
May I ask what rom are you currently on?
Click to expand...
Click to collapse
CM9.1 nightly 9/3 with included kernel
It did it a third time during class while it was in my pocket, the power button trick didn't work this time, I had to pull the battery after the samsung logo, plugging it back in to get it to boot...but...
near the end of the CM9 boot animation, when it vibrates and the auto brightness kicks in, it started it again! I have yet to revive it...
This is a bit upsetting because I had just got CM9 the way I liked it and I don't exactly have the time right now to mess with warranty and a new phone...I would like to fix it.
There are about 20 different threads on here on how to revert to stock...let me as a last ditch try to revert to stock and see if it keeps doing it...unless somebody has any ideas...
I was working in recovery mode, i super-wiped my phone to see if installing a ROM from scratch would help, and my phone even does it in recovery mode. Warranty time.
So whats the fastest way to restore to stock? Who knows how long I will have after reviving it before it breaks again.
zander21510 said:
I was working in recovery mode, i super-wiped my phone to see if installing a ROM from scratch would help, and my phone even does it in recovery mode. Warranty time.
So whats the fastest way to restore to stock? Who knows how long I will have after reviving it before it breaks again.
Click to expand...
Click to collapse
Here you go!!
http://forum.xda-developers.com/showthread.php?p=30832325
Sent from JMT Goodness
Well, finished playing stupid for T-Mobile, in two weeks I will have my replacement T989. Now all that's left is returning this thing to stock before it starts acting up again.
And my temporary replacement phone?
HTC Dream, aka the G1, the first Android phone! Lol what a difference...GB feels like a dinosaur...
http://forum.xda-developers.com/showthread.php?t=1513359
[HOWTO]Restore to Stock/Recover from a Bad Flash. Could try the last 3 pages on this thread. That will help you go back to stock without an issue. Hell might make you wanna keep your phone if you can get it to work again.. good luck
Sent from my SGH-T989 using xda app-developers app
datrapstar said:
http://forum.xda-developers.com/showthread.php?t=1513359
[HOWTO]Restore to Stock/Recover from a Bad Flash. Could try the last 3 pages on this thread. That will help you go back to stock without an issue. Hell might make you wanna keep your phone if you can get it to work again.. good luck
Sent from my SGH-T989 using xda app-developers app
Click to expand...
Click to collapse
Thanks! got it all done, back to ugly, ugly stock lol...and just when I thought maybe I would have to brick it myself it did the reboot thing again...so pulled the battery and there it sits factory reset.
I recently had a buddy get a screen replace from a place in the mall. The phone display and everything works, but one problem after all of that. It will not stay on and keeps bootlooping ect.... I did a factory reset and still no luck another weird thing is, when it is plugged in the battery will go from 80% down to barely nothing then quickly charges back up. The phone somewhat seems to stay on when it is plugged in. The phone started having these problems when the screen was replaced. Im confused. please help! Thanks!
sure its simple
pdubzzle83 said:
I recently had a buddy get a screen replace from a place in the mall. The phone display and everything works, but one problem after all of that. It will not stay on and keeps bootlooping ect.... I did a factory reset and still no luck another weird thing is, when it is plugged in the battery will go from 80% down to barely nothing then quickly charges back up. The phone somewhat seems to stay on when it is plugged in. The phone started having these problems when the screen was replaced. Im confused. please help! Thanks!
Click to expand...
Click to collapse
First thing first do a hard factory reset with the volume down and power button, not work then flash with lg flash tool the model numbers kdz all downloads and guides are posted. let it fully boot power down then fully charge, power up and down several times so the data files understand the new digitizer and resets all problems. Still dont work find screen replacement video via youtube once there whatch how to disassemble cause I am pretty sure it is one of the data cables or connections that is loose but you can never know with software and those are easier to do and less chance of permanent damage.
Or you can mail it to me and I fix her right up lol
I have a N5X, unrooted, bootloader locked, 7.1.2 stock. It happened twice in the last week, the phone used to work perfectly before that. I just pick it up as usual but it doesn't turn on anymore, I tried multiple times to boot it normally or in bootloader mode but nothing happened; then the next morning I plug it into the wall the led flashes red and it reboots normally. I thought it could only happen once but it happened again yesterday night and as usual this morning it booted up. Does anybody know what the problem may be caused by? What can I do? The phone still has warranty and if no solution is found I'll send it back to Google. Sorry for my english.
I have had the exact same problem, mine only occurs when the phone is ran down to 0% and powered off. I never let that happen but I have a 3 year old son who repeatedly does it, and every time i hold my breath, praying it will come back on. Well i am holding my breath and praying once again this morning,hoping it will power back on. Do you think it could be some kind of "protected mode"to keep the battery or something else from overheating or whatever?
alezmoroni said:
I have a N5X, unrooted, bootloader locked, 7.1.2 stock. It happened twice in the last week, the phone used to work perfectly before that. I just pick it up as usual but it doesn't turn on anymore, I tried multiple times to boot it normally or in bootloader mode but nothing happened; then the next morning I plug it into the wall the led flashes red and it reboots normally. I thought it could only happen once but it happened again yesterday night and as usual this morning it booted up. Does anybody know what the problem may be caused by? What can I do? The phone still has warranty and if no solution is found I'll send it back to Google. Sorry for my english.
Click to expand...
Click to collapse
If you need the phone and are confident, try unlocking the bootloader, reflashing stock factory image and relocking the bootloader again. You will lose all the data, though.
If you can live without a phone for a while, just send it to Google/LG. Nothing else one can do imho.
When my phone was in the last steps of dying (eventual bootloop), I could disconnect the battery and it'd get farther through the boot cycle, or even once booted. Basically, after it wouldn't react to any buttons or combos, I would disconnected and reconnected the battery. Then I could give things another shot. So I'd start it, it'd make it to the colored circles, or I could boot to the recovery menu, and try some things, but at some point it would go black. Then it would not react to anything unless I disconnected the battery. Then it would react to the buttons again and eventually one of the steps would make it go black. And then take a disconnect to get another try.
It sounds like your phone may be close to dying.
By the way, I only opened it up since I was past the warranty expiration date, and LG extending the warranty to about 18 months wasn't a known thing at the time. It is actually easy to get everything apart, but hard not to make dings in the plastic cover even using plastic tools.
I would say, back up everything you can from it and expect it is going to get worse. Redoing the OS didn't save mine.