Pardon for the long post but my Nexus One has been out of comission for a few days now so I'll list everything I've tried to make it work in an attempt someone might be able to help me!
Okay, here goes.
A couple days ago I removed the battery on my phone to install an invisible shield. Prior to that I had owned the Nexus One brand new for about a week, had it rooted first thing with the HTC Desire ROM...it was running perfectly
After the installation of the shield was complete I reinserted the battery and hit the power button. The phone booted straight to the bootloader (aka white Robots on Skateboards screen). Funny thing, I was unable to navigate the bootloader (vol up/down) without fiddling with the trackball first by pressing it a couple times) Anyway if I would reboot the phone via bootloader it would return...power off the phone it wouldn't power off just reboot to bootloader.
In this mode I could still use fastboot perfectly and I could enter the restore screen. At this point I kept attempting a reboot and it actually went through at one point and did a full boot to the OS...when I powered down and booted up again however, it was back to the same issue.
On the modaco forum they suggested I flash an alpha2boot.img as the boot image replacement for r21 desire rom as a fix, I tried this method with no success. Since, I've factory reset the phone several times replacing it with various ROMs (currently running stock) none of it fixed the problem.
I also found a way to brute force the phone into safe mode via the fastboot command in prompt: fastboot-windows reboot Using this command the phone successfully reboots, albeit into SAFE MODE. In safe mode the phone works perfectly in every way. I'm just limited in that I can't install any applications and I can't reboot properly (without a computer and command prompt).
I was doing some research on the forums and read the problem could be with the trackball. It would make sense that the phone could only boot to bootloader if the phone had the key press for the trackball triggered somehow. That said, the trackball functions perfectly when operating the phone in safe mode so I doubt this is the issue.
Another idea is that the phone is stuck in some state in the SPL or bootloader...I was wondering if there was anyway to reflash the SPL or bootloader to see if I could resolve the issue that way. (how I would do this, I have no idea)
Any help, suggestions, or advice is very appreciated. As I already unlocked my phone I have a feeling I am out of luck for warranty though I would pay for HTC to repair it if they could. I would prefer to fix it in the software however and not send it in.
Reflash the stock ROM and see if that helps.
mortzz said:
Reflash the stock ROM and see if that helps.
Click to expand...
Click to collapse
He said he's running stock rom...
@ OP, if everything was absolutely perfect before putting the shield on, and everything to crap immediately after finishing the shield, then obviously something went wrong during the install.
The obvious yet unfortunate conclusion is that some solution got inside or something, most likely inside the trackball. =\
Detail exactly what you did when you installed the invisible shield.
Did you get you phone wet at all?
Got the front of the phone a little wet and I'm guessing some did get in the trackball. That said, I do invisi shields every day for my job and never had an issue with any phone...wouldn't it be ironic that mine was the one that got screwed up.
I think it's interesting to note that the trackball still works perfectly when the phone is running in safe mode, no double clicks or anything like that...possibly a sensor was tripped?
Got the front of the phone a little wet and I'm guessing some did get in the trackball. That said, I do invisi shields every day for my job and never had an issue with any phone...wouldn't it be ironic that mine was the one that got screwed up.
I think it's interesting to note that the trackball still works perfectly when the phone is running in safe mode, no double clicks or anything like that...possibly a sensor was tripped?
So I called it quits on fixing this phone and I'm sending it out to HTC does anyone know how I go about getting restore back to factory settings?
Well you can't relock the bootloader, but if you can use fastboot when your phone's on the booatloader, you can use that to wipe the phone.
Oh wow, sorry to hear it.
If your phone will not boot without the help of fastboot, I wouldn't worry to much about what state Android is in (factory, or custom rom). HTC will attempt to boot the phone, toss it in a bin, and then send you a replacement.
Or that is my assumption anyways. A friend had a similar issue; he unlocked his phone and decided after flashing the Desire rom, that he wanted to stay stock with what came on his Nexus for a while. After flashing the stock images back, his phone looped into bootloader. Off to HTC it went and within a week he had a new phone.
Best of luck!
Sorry to post in such an old thread, but I'm having the exact same issue. Even the part with the invisible shield. Didnt install it myself, the idiot at best buy used too much of the liquid I guess. Did you send yours in or what? I managed to get the phone to work for about a month then it started acting up again today. Wont boot into anything other than safe mode, or fastboot. When it boots into safe mdoe, the phone turns off within a few seconds then goes straight to the boot animation. Would love to get this issue settled, really annoying
i am having same problem. fasboot doesnt even find my phone. i got into safe mode but when i turned it off and back on it went back to fastboot
Same
I am getting the same problem! this really sucks. I think the phone might have gotten a little bit wet, just a few drops of water, and that may have caused this. Should I just call HTC and send it in?
btw, the phone was working fine, even with the very little moisture that was wiped from it. But, I took out the battery when I got home, and this happened.
so is this because on invisibleshield? cuz i just ordered mine today!!
I think its from a little bit of moisture getting into the trackball. I've been doing many "tests" trying to figure out the problem, and my almost final conclusion is the trackball not working good. Most of the time I try to start-up the phone i get into safemode, and once I have gotten into the normal way of things, but the trackball wasn't working well. I think I might have to cal htc, and that sucks because I am going out of the country in 4 days... I won't be able to take my nexus if I can't come up with a way to fix it myself.
I DID IT!
Well, I think I did.
My theory that moisture was the cause of this bootloader stuckness is quite correct. I took a towel, and rubbed the trackball to it for a good 5-10 min, then I did it for another 5-10 min wiping while pressing down on the trackball. I'm very sure that there was some moisture extracted from the device. The trackball is working now. I now do not have to call HTC or send it in.
I kept on booting into fastboot and then recovery, being unable to press buttons, but then I rebooted again into safe mode, where the trackball wasn't working either. I kept moving around the trackball, and then I figured it out, because I felt a slight bit of moisture. Now, it boots up normally, I can access the recovery, and all selection is working.
But, I have a bad feeling that this problem will come back to haunt me. It's good for now though.
Phone is working great as usual.
Can confirm the same issue.
Drop of water on the trackball.
Rebooted into an unresponsive fastboot.
Fastboot reboot command from the computer got me into safemode.
Rolling the trackball while pressed fixed it, the phone boots properly now.
Related
Any help would be greatly appreciated.
I have a launch day Nexus One running CM5.0.5.3, the OC/UV kernel, and the EPE54B radio.
It has all been running great until today. I took it out of my pocket and it was warm (not hot) to the touch. I noticed the screen was blank but the buttons along the bottom were illuminated. I tried resetting it (power+volume down+trackball) and that didn't do anything, so I pulled the battery. When I rebooted it, it seemed to take a longer than usual time at the initial boot screen, and then went to the animated screen. It stayed on the animated screen for quite a while and then froze. It's stuck on the X mid-formation.
I then booted into the bootloader (which reacts like normal) and went into recovery. I re-flashed CM5.0.5.3, no effect. I wiped cache and system and re-flashed. Nothing. I did it again, and it finally booted up but I could only select things with the scrollball. The volume rocker worked fine, but the touchscreen is completely non responsive.
If I let it sit at the boot screen for a while it will go black eventually and time out.
I'm at a loss. I'm in the process of downloading a stock ROM and am going to flash it next. Anyone have any suggestions? My bootloader is (obviously) unlocked, so I'm worried about warranty work
Update: Just got it to boot (with the stock ROM) and I've got a warning screen saying:
Sorry!
Process system is not
responding.
[Force close] [Wait]
Any ideas?
Reflash CM 5.0.5.3 and then post back
Ok, re-downloading now.
Just flash in recovery?
Flashed in recovery (after wiping)
The phone stays on the stationary initial boot screen (four bars) for about a minute and a half and then goes to the animated cyan X. It stays there booting for probably two minutes before stopping mid-animation. If you let it sit there for a while the screen will time-out, which you can bring back with the power button. Sometimes when you hit the volume rocker you can hear the beep beep but nothing shows on the screen.
What the hell is wrong with my phone?
After an obscenely long time I got it to boot up.
Touchscreen is not responding, trackball is not responding, I have a question mark on the battery indicator, and no service.
I can't unlock the screen because of the non-functioning touchscreen. Live wallpaper is running great, it makes the sound when USB debugging is connected, it just won't react to any input.
I can, however, establish an ADB connection. It shows up on the device list and a remount succeeded.
Would reflashing the radio be of any benefit?
Dang the touch screen is unresponsive? I'm not an expert, but i'll try to give you some ideas.
I had some trouble once and I used settings-privacy then erased everything from within the OS. Then I reported to the screen just before going into recover and hit clear storage. Then went into recovery and wiped everything that I could. After that, flash the Rom that you want.
I've done a full wipe to no avail.
I'd bite the bullet and call htc, don't mention that you have rooted, it may be a hardware thing.
Scaaaary!! But hey, it happens. I would also try wiping for EXT on the SD card if you have been using apps2sd.....May not hurt, mights well try everything.....
Wiped everything, reflashed radio, flashed to stock. Nothing. This is exactly what I was worried about when I unlocked it.
Oh, well.
liam.lah said:
I'd bite the bullet and call htc, don't mention that you have rooted, it may be a hardware thing.
Click to expand...
Click to collapse
Yeah, I'll do that tomorrow. I guess I'll flash everything back to shipping and hope they don't notice.
mortzz said:
Wiped everything, reflashed radio, flashed to stock. Nothing. This is exactly what I was worried about when I unlocked it.
Oh, well.
Yeah, I'll do that tomorrow. I guess I'll flash everything back to shipping and hope they don't notice.
Click to expand...
Click to collapse
Many people have posted that they got a replacement even with an unlocked bootloader. One guy I heard said they charged him $55.
Either way, you can probably get a replacement.
I may have bricked my phone while flashing with odin to stock froyo 2.2 rom. The download mode works but i cannot get into recovery mode it just flashes at the logo screen gt-i9000m over and over and over again.
Is there a way past this or do i have to send this phone in for repair?
I have stock everything.
My phone battery died and I have spare batteries and changed it to a fully charged one. It booted up and said that a bunch of apps have to be FORCE closed... so I rebooted it.
Now it's doing the same thing yours is... the logo screen flashes over and over.
I pulled the battery to hard boot it. Then without turning it on I plugged it in to charge... so it tries to go to the charging battery icon and then flashes the logo screen over and over again.
This is my second phone... first one kept eating battery life and got real real hot.
omg stoopid samsung. I can get into download mode just fine, when i reflash it just stuck at the boot logo. Are you able to send yours away for repairs? i have mine unlocked but i also got warranty from where i bought it at wireless wave. i rather not send it in though...
I couldn't get into any menu's... sent the piece of **** away for repairs. I almost threw it at the wall behind the clerk at the bell store.
same boat here, i woke up this morning to find a bunch of forced closed messages. so i hit okay, my phone was all screwy so i turned it off, pulled out the battery, put it back in and started the phone and ta-da the galaxy S TEXT (not logo) kept...well it looks like it would boot over and over again just to the title screen, shut off and boot again. If i do the 3 button press to get to download mode i see that screen and i cant do anything else, actually i dont know what to do there.
I bought this thing in august so i am good for warranty, oh i haven't once rooted or lagfixed or anything, i just unlocked it, and with rogers instead of bell, but yeah i called bell and they refuse to help. The guy was not cool with me unlocking the phone, says i might not be covered under warranty anymore.
Next week i am going to take it to the bell repair center in person, see what they say.
Not sure what to do now. EFF!
Last samsung phone ever. the LG optimus 2X looks pretty awesome.
I'm having the same issue, my phones all stock.
When I got my phone this morning is was turned off, I plugged it in, powered it up, saw the Samsung logo and intro play and I walked away. When I came back I tired using my phone but only the lights, on the buttons, turn on but the screen and the rest of the phone doesn't respond. The lights will stay on forever.
If you can get into download mode, have you tried flashing it with some other Rom? Like DocX custom rom?
Sent from my GT-I9000 using XDA App
Try booting into recovery mode (vol-up, home and power). Do you get an error message under the menu? If so, report it here or do a search on that specific error. It appears that some errors are easily recoverable from via flashing while others are not.
gtg2 - Try booting into recovery mode (vol-up, home and power). Do you get an error message under the menu? If so, report it here or do a search on that specific error. It appears that some errors are easily recoverable from via flashing while others are not.
The flash will go through completely and pass, as soon as it reboots to the Gt-i9000m logo it will just loop continuously. even when you hold down vol-up, home and power, it just doesn't recongize those buttons but will recongize vol down, home, power what gives?
Valinorian - If you can get into download mode, have you tried flashing it with some other Rom? Like DocX custom rom?
Yeah tried darkys 5.6 rom, does the same thing shows gt-i9000m logo then loops it self
dtran00 - that sucks man, but bell offers unlock codes so i dont' see how that can void your warrenty when you have to pay $70 for the unlock codes no?
Spudsicles - hopefully i won't have any troubles but i might end up throwing it at them lol
Seriously this is a good phone but the problems omgosh.
regarding everyone with the boot loop errors, Sounds like you have got the corrupted internal memory. This is a common problem everyone has been having including me. You will have to send the phone off at bell. I'm still waiting for mine to come back to me, sent it off Dec 1, although some people are reporting repair times within 5 business days.
To the best of my knowledge, that does NOT necessarily indicate flawed internal memory. I've experienced a few errors myself - one was a real SDCard issue which required repair while the others I was able to recover from.
Have you tried reflashing firmwares via Odin with the repartition option checked?
Have you tried booting into recovery using ADB? I'm not an ADB pro myself but do know it's possible. You'll have to google for instructions.
Hello,
I have recently got my hands on old G1; got it as "bricked" - no matter what i did, it just wouldnt turn on. I could, however, get into bootloader (or whatever is that tri-colored screen called). Using goldcard, i was able to flash RC29 DREAMIMG, which would however result in same error (phone stuck at g1 logo).
Finaly got it "working" by flashing package from stem 3 of this guide; which enabled fastboot. Using fastboot i than flashed hboot and radio from this thread and RA recovery. Using recovery, i finally flashed (tried more, same problem on all of them) this rom ("FroyoByLaszlo Port" one).
Now to the problem; sometimes, phone just wont boot, or access the recovery. I am able to enter bootloader screen every time, even if it wont boot. Sometimes it boots straigt away, sometimes it enters some kind of bootloop (and might actually boot after several [g1 logo -> some time -> reboot] cycles. Also, what i noticed, is that phone sometimes has problems with waking up - buttons would light up and screen stays black. If i open keyboard, screen goes on, but digitezer wont react (trackball works).
Have to say I am not quite sure what might be wrong (one suspect MIGHT be battery, which seems to be quite weak). I will gladly accept any new idea.
Doubtful its the battery but it sure sounds like hardware, maybe a bad chip with some corrupt partitions. Flashing a new bootloader should take care of this but being you have done so.... maybe bad blocks in the chip?
What is you current bootloader and radio? Write down all from that screen
Sent from my HTC Vision using xda premium
DREAM PVT 32B SHIP S-ON
HBOOT-1.33.0013d (DREA11000)
CPLD-4
RADIO-2.22.27.08
Oct 21 2009,22:33:27
Than theres just fastboot and action selection stuff.
Edit: also, i have opened it up (everything except lcd part, which i might check later) to check for any loose cables (what i noticed, is that if i give the phone few harder knocks, it usualy boots - however i am still not sure if this isnt just an coincidence) and oxidation; everything seemed clean & in great condition (ie, no oxidation).
A strange one you have here, the intermediate problems always trouble me the most. Its possible you have a sometimes sticky camera button that keeps you from booting properly without banging it around...
Sent from my HTC Vision using xda premium
I will give these buttons a go later (will open it up once more, might check the lcd part as well), however they dont feel like they are geting "stuck" - and both of them works well for selecting actions in bootloader.
Also, would that explain the "wake up" bug? Just happened.
edit: However i think i may confirm the "bang a phone" theory. Just refused to boot, gave it bang right into the butons and there it boots.
Gentle Bang for The Win!
demkantor said:
A strange one you have here, the intermediate problems always trouble me the most. Its possible you have a sometimes sticky camera button that keeps you from booting properly without banging it around...
Sent from my HTC Vision using xda premium
Click to expand...
Click to collapse
I recently pulled out my HTC G1 which has been out of commission for some time; it's long since had some battery issues - doesn't hold a charge (well, it does now, but not for long..), and I look forward to rooting it this weekend as it's far past warranty and I'm no longer w/ T-Mobile. Long story short, I forgot the screen unlock code and couldn't log in using a Google account (btw - still haven't found a way around this one yet). I used the pinhole reset and I'm pretty sure it got stuck as my phone wouldn't boot, take charge or anything. Was fairly convinced it was bricked - until I came across this post (many thanks) and gently whacked my G1 against the wooden coffee table and pressed over ALL the buttons on the unit to be sure nothing was stuck. During the process - there was light (literally)! Sure enough - I put power back to the unit, and it's taking a charge again. So today I being the journey to root, and wanted to throw this out there for anyone else stuck before boot with an apparently bricked phone. This is the first Android smartphone they made and certainly has it's share of bugs - sticky keys, etc. Give it a good whackin' and try again, hope this works for others as well!
~Sockum
Hi there... new to the forum, but long-time reader, especially over the past two days since I dropped my AT&T HTC M7 (flashed to GPE) on cement and it pretty much died.
I'm out of ideas and could use some help. After the drop, it was stuck in a boot loop, but I was able to get to hboot with volume down. From there, I can access fastboot, but recovery or factory reset options just trigger the boot loop again. During the loop, it shows the Google logo (or HTC logo when flashed to stock) for 15-20 seconds and then reboots. Physical damage to the phone is not too substantial, and I have unfortunately extensive experience opening it up from repeated attempts to fix the purple tint issue with bad modules from eBay, so I checked inside and everything is intact.
Over the past two days I've flashed RUUs and recoveries like crazy, downgraded and upgraded hboot, changed CID, etc. I can oem lock and unlock... fastboot kicks out an error when I do it, but the status in hboot is changed when I reboot into the bootloader. Flashing ROMs and recoveries works like a charm, so does erasing cache. What I mean is that the process works exactly like before in fastboot, and I can see the splash screen logo change, so I know it's taken effect, but NOTHING gets past the boot loop. I am thinking the drop resulted in a corrupt partition, but since I can't get into recovery I haven't been able to find any way to do anything about that. If it was physically broken, it just doesn't seem like I would be able to do everything I can. I initially thought maybe it was a busted/stuck power switch, but that works perfectly navigating hboot menus and nothing ever auto-selects or anything like that, which I would expect.
Aside from the fact that I really like this phone, and that I really don't want to have to pay to replace it, I feel attached to it since I've dismantled it successfully to repair more than once and flashed ROMs many times in the past without issues. I've just run out of ideas, and of course I can't go on much longer without a phone.
Does anyone have any experience with this or hunches I can try out?
placebored said:
Hi there... new to the forum, but long-time reader, especially over the past two days since I dropped my AT&T HTC M7 (flashed to GPE) on cement and it pretty much died.
I'm out of ideas and could use some help. After the drop, it was stuck in a boot loop, but I was able to get to hboot with volume down. From there, I can access fastboot, but recovery or factory reset options just trigger the boot loop again. During the loop, it shows the Google logo (or HTC logo when flashed to stock) for 15-20 seconds and then reboots. Physical damage to the phone is not too substantial, and I have unfortunately extensive experience opening it up from repeated attempts to fix the purple tint issue with bad modules from eBay, so I checked inside and everything is intact.
Over the past two days I've flashed RUUs and recoveries like crazy, downgraded and upgraded hboot, changed CID, etc. I can oem lock and unlock... fastboot kicks out an error when I do it, but the status in hboot is changed when I reboot into the bootloader. Flashing ROMs and recoveries works like a charm, so does erasing cache. What I mean is that the process works exactly like before in fastboot, and I can see the splash screen logo change, so I know it's taken effect, but NOTHING gets past the boot loop. I am thinking the drop resulted in a corrupt partition, but since I can't get into recovery I haven't been able to find any way to do anything about that. If it was physically broken, it just doesn't seem like I would be able to do everything I can. I initially thought maybe it was a busted/stuck power switch, but that works perfectly navigating hboot menus and nothing ever auto-selects or anything like that, which I would expect.
Aside from the fact that I really like this phone, and that I really don't want to have to pay to replace it, I feel attached to it since I've dismantled it successfully to repair more than once and flashed ROMs many times in the past without issues. I've just run out of ideas, and of course I can't go on much longer without a phone.
Does anyone have any experience with this or hunches I can try out?
Click to expand...
Click to collapse
yeah try a new motherboard yours is broken, really it's hardware damage no amount of flashing will fix it
clsA said:
yeah try a new motherboard yours is broken, really it's hardware damage no amount of flashing will fix it
Click to expand...
Click to collapse
Thanks clsA. I'm surprised by that since in my experience a broken motherboard results in a much more substantial and obvious failure, but I guess the point is moot if I can't get into recovery to try anything else.
There isn't much of a market for new motherboards, and my experience with eBay sellers for oem components on this device makes me think trying to replace it there would be a fool's errand. I guess I could buy a used M7, but on the other hand the damn thing has basically been nothing but problems. The defective camera turned to garbage in under a year and one drop killed it? Unless anyone has another suggestion, I guess it's time to cut my losses on this thing. I may feel a sentimental attachment because I've nursed it along so much, but damn... a phone is a phone and this one has been a LOT more problematic than any other one I've had.
Gotta thank you again clsA! Your words of doom made me feel that extra bit wreckless, so I decided if the phone was cooked anyway I might as well tear it down and try whatever I could... firmly reseating cables and squeezing heatsinks, etc. Low and behold, I reassembled and the problem is fixed! I'm not sure what the exact issue was, and I won't be surprised if it comes back at some point down the line, but I'm back up and running tonight and that's a hell of a lot more of a victory than I was expecting.
So... it wasn't a motherboard issue, but it was hardware related.
I should have posted on here when this first happened. I love xda!
placebored said:
Gotta thank you again clsA! Your words of doom made me feel that extra bit wreckless, so I decided if the phone was cooked anyway I might as well tear it down and try whatever I could... firmly reseating cables and squeezing heatsinks, etc. Low and behold, I reassembled and the problem is fixed! I'm not sure what the exact issue was, and I won't be surprised if it comes back at some point down the line, but I'm back up and running tonight and that's a hell of a lot more of a victory than I was expecting.
So... it wasn't a motherboard issue, but it was hardware related.
I should have posted on here when this first happened. I love xda!
Click to expand...
Click to collapse
That's great, I'm glad you were able to fix it
I'll try to make this short.....
I am using N910T3. Phone was charging in car while using (stop by roadside). Out of sudden it shutdown and went into reboot loop and the phone is extremely hot. I took the battery out for soft reset and try to turn on again. Phone will freeze at different screen (Lock Screen, Home Page, Samsung Logo, Powered by Android) and give two separate vibration before reboot.
I thought it is battery problem so I bought a new battery to try, but still the same problem. So I went on to backup all file before I perform hard reset. While doing that, I find out the phone can be use for longer before reboot if it was stay off for a long time. So I have this crazy idea: put it in a fridge. Surprisingly it works! The phone will not reboot anymore and I can manage to backup all file before doing anything else. Also, the phone will not charge if you plug in right after a few reboot.
Then, along with the fridge method, I perform factory reset through normal android setting. Now it will just stuck at powered by android screen while in reboot loop. I then try to flash with Odin, multiple times. Flash by Odin is complete, phone restart, then it freeze and reboot, at different screen (Installing system update, Erasing, powered by android).
Out of frustration I try with the fridge method to flash, and IT WORKS AGAIN!!!. The phone can now boot to welcome screen where you first setup your phone. However, it will then freeze again and reboot while doing so.
There was only this one time, where I left the phone off for a day after flash with a previous stock ROM, turn it on and skip as much setup as I can, finally reach the homepage screen, then will stay on without any reboot issue. I thought I finally fix it. I then power off the phone, put in my Sim Card and SD Card, power it on, then again, reboot issue appear.
I tried flash with latest stock ROM, previous stock ROM (one updates away), flash any stock ROM with pit file. I sometimes will get error code on device after flash (can't remember the exact error). I also cannot boot into recovery mode without flashing a twrp. Sometimes if success, I will get straight to Lock Screen without going through the phone welcome setup process. But again, none of these I tried can solve the reboot loop.
I may went too far and mix up all steps to the phone. Does anyone have any idea how to fix this? Or is my phone, as I believe, has a faulty motherboard that cause the reboot loop? Thanks in advance for reading through my problem!
Hello there, I had a Tmo Note 4 which I loved it until the end, it's a hardware problem and there is no fix for it unless you replace the board, by the time you buy the board and what you need to pay for labor you're going to expend a few hundred dollars, I also tried the freezer method but it finally the phone gave up, it does not turn on anymore. That was my experience. Good luck bud.
oscarmaldonado said:
Hello there, I had a Tmo Note 4 which I loved it until the end, it's a hardware problem and there is no fix for it unless you replace the board, by the time you buy the board and what you need to pay for labor you're going to expend a few hundred dollars, I also tried the freezer method but it finally the phone gave up, it does not turn on anymore. That was my experience. Good luck bud.
Click to expand...
Click to collapse
Seems like that's the case I guess.....But if anyone has any suggestion please do tell so I can give it a shot.
jackgan said:
Seems like that's the case I guess.....But if anyone has any suggestion please do tell so I can give it a shot.
Click to expand...
Click to collapse
Try a firmware flash before newsest. Then take the ota
anyone know if a 910t3 mother board will fit in a 910t frame? Asking cuz I wanna switch them out.