Hey All,
I posted this over on r/nexus5 as well, but figured id see if anyone here had any ideas as well.
I replaced my screen/frame earlier today and started having some trouble, figured I'd see if anyone else has had a similar experience and can give some advice.
I replaced my screen about a year ago, and all was well until a month ago. Dropped it again and cracked the screen, so I ordered another. Decided to spice things up and get a red frame as well, so this afternoon I took it apart. Tore it all down, and moved all the parts over to the new frame, everything went over nice and easy, and I got it all about together and booted it up. I see the Google logo with the unlock symbol, hangs out for about 15 seconds, and then reboots. Will do this for a bit until I power it down.
I read some other threads with some similar symptoms. A few people suggested the power button was being held down and causing the reboot, but that isnt the case here. I can get into the boot loader/fastboot screen, and can see it over adb. Soemone else suggested it was the long wide noddle cable not properly connected, so I've reseated that about a dozen times with no luck. I have checked all of my connections over a handful of times, but still the same deal.
So since my pc can see it in fastboot, I ran the nexus toolkit and did the force flash. Files transferred over and were written successfully, and as far as NRTK was concerned, it all went well. so it tells me the phone to reboot, and of course its the same 15seconds of google logo, rinse/repeat.
So I am thinking maybe my motherboard got damaged somehow during the transition? I just cant find any signs of damage, and I was pretty careful during the transfer. This was a replacement from China, but I figured since it shows the google logo and boot loader, the screen is indeed working... could it be the screen/digitizer preventing it from fully booting? I think its odd that root toolkit could still see the device, send data to it, and write it successfully.
Any thoughts would be much appreciated.
Actually now that I think about it, I will throw the guts back into the old frame in the morning to confirm if it is the new screen causing the problem or not.
So it turns out it was the chinese knock off screen that was the problem. put the guts back into my old phone, and all was well. Going to return it and get a new screen on the way.
Related
Hi all,
I am at my wits end on this problem if anyone can offer any adivice it would be greatly appreciated. So let me give a recap of what has occured thus far. The water damage tag for some reason turn pink thus i am unable to get warranty exchange. I am pretty certain that the phone has never been expose to any water of anything of that sort, but i do live in houston, tx so might be humidity or what not that cause the tag to turn. Anyways.
1. This all started after i flashed RRE 5.2 RC3. Initially after a successful flash everything seem normal and fine. Then next morning i woke up to a frozen screen with many verticial lines running up and down the screen was almost unreadable. Initially i thought it was a bad flash or just random lock up. I did a hard reset and tried to enter the bootloader. Black screen, it does seem like the backlight is coming up but nothing on the screen. I can hear the phone power on and boot successfully into windows. Activesync connects i can browse the contents of the phone.
2. After flashing to stock att rom and stock htc roms same symptoms. So at this point i am thinking crap bad LCD screen. so I ordered both the digitizer and lcd screen for good measure. I replaced them hoping that a bad LCD was all. replaced both screens and i powered on the phone. same problem. black screen. The phone still powers on and boots into windows. Activesync still connects and i cna still reflash the phone.
3. I work extensively and do both desktop pc and notebook repair. I am not new to dealing with small electronic repairs. but at this juncture i am unable to identify the cause of hte malfunction. i am hoping maybe some of the gurus here might be able to shine some light on the subject.
Thanks in advance for any help.
I would have followed the same approach; your description makes it sound like it might be some kind of backlighting issue at first read. I'm inclined to think it might be a cold connection (bad connector) on the main board.
Silly question, what happens if you power up the phone with the keyboard exposed?
*EDIT* Not sure if you have been here yet: http://www.mikechannon.net/
Cheers,
i just tried to power up the phone with keyboard exposed. Powers up the same as with the keyboard hidden. Still boots up fine but black screen. I already have the service manuel dowloaded. i have checked around with several repair places both local and on the web. Seems like no one has any parts for the att fuze/touch pro gsm except for the lcd and digitizer and a speaker.
its quite possible that it is a main board but as the same time it might be something as simple as a ribbon cable. i have contacted htc about doing a possible repair and they want wayyyy too much for just a main board repair almost $400 USD.
Anyone have a bricked/ non working touch pro they would like to sell ? =P
fkoong said:
its quite possible that it is a main board but as the same time it might be something as simple as a ribbon cable.
Click to expand...
Click to collapse
Could be a bad ribbon cable ... and firmly pressing around the front/back of the unit shows no change?
pressing the phone front and back show no changes to display. in a very dark room I can see that there is light emitting from the display but its just the screen is not displaying anything visable. this occured both before and after i changed out the screens. I'll do another visual inspection of all the boards to see if there is any bad resistors burnt out circuits etc.. but i didn't notice anything mentionable during my first 2 inspections. Maybe 3rd time is the charm.
Thanks for all the feedback thus far Hilaireg it is quite appreciated. All this venting has at least made me feel 1000% better than after i replaced my lcd and still same problem at least i don't feel like a complete idiot!
Sorry I couldn't be of much help ... you've done all the steps a seasoned hardware person would do.
Do post back to let other folks know if you get it back up and running.
Cheers,
you have a pm fkoong.
I have possibly the same problem. Phone got wet, dried it out for 2 days (in a container of rice). Phone worked but had "water marks" on screen that disappeared after two days and everything was fine for about 2 weeks. Then one day (happened to be humid misting rain eve in Charleston) the screen is blank (hint of backlight only). A soft reset and it seems OK for about 1hr, then blank again. The hard resest screen displayed OK (readbale text etc), but didnt work. But as I write this, I retry to document it results correctly and the NATF ROM is reloading and the screen works! We will see how long!!
Well.. not that long, the end of the ROM load and it went blank again, seems like a video driver problem. The Press VoluP to boot does show some red artifact.
Trying hard reset again (No SIM no uSD)
The NATF v4.4 loads and gives me the Tap screen, Align Screen, stylus, loads customization, opera, tf3d, then loads a bunch of files under ...... and then the screen goes blank again, seem like what happened last time, so Ill try loading a fresh ROM copy... later
Ive gotten it maybe 5 times since I bought it, although the latest updates have been stable. I still got it a few days ago though. Basically if I have the dock, and close the lid and say rotate the whole device or just move it a certain directions, it will make the screen stop displaying when trying to open it again. The lid opens, you hear a noise like it unlocks, but the screen is black. I try unlocking and locking, undocking, but its still black unless I reset the device via power. Anyone having this issue? It's not a serious one yet, but id like to know why it happens in the first place.
I have similar experience without dock.
I put it in carrying bag and drive to subway, when I take it out and the screen is blank and I can reboot it by power button. It happened 3-4 times under same situation.
I updated to 3.2 and problem didn't come back so far.
Hello,
I have searched the threads but cannot find a situation similar to mine so am posting, but apologise in advance if this has been solved before. It's a bit of a long story. About a year ago I was foolish enough to have stood on my TF300T, cracking the screen. The tablet was still working, but it would not register touch. I put it to one side and left the battery to drain. For various reasons I have just got around to replacing the screen.
I found a screen and digitiser of the correct version for my UK TF300T (version G01) and I'd thought the replacement went without any problems, although I was slightly unsure of one digitiser connection. On pressing the power button (I had pre-charged the battery) the screen came to life just as I'd left it as if coming out of sleep rather than being off for a year. It was short lived though and soon the tablet went to black and would not turn on. I thought maybe it was the digitiser connection so went back in to re-fit it. It was only then that I noticed the power switch on the logic board itself under the plastic shell. I hadn't switched it to off before (duh) so did so then, refitted the digitiser cable much more securely,switched the power back on and tried to boot, but nothing happened at all, apart from the power LED flashing orange. After some experimenting (trying to charge the tablet again etc) I found I could only boot by charging the dock and plugging the tab in the dock, but the tablet would only get as far the ASUS screen (not the 3D one, just the flat lettering), with the 'device is unlocked' message in the top left corner and stops there. I can turn it off, but can't boot into recovery at all. And that's where I am now.
Things I have tried - a different logic board from a TF300T's scrounged from eBay which also had a cracked screen (this, weirdly, seemed to have the same problem as mine), swapping various parts out from some other TF300T's (without logic boards) from eBay and contacting the device through Sandix's ADB GUI (after downloading and extracting the SDK), which registered no device.
My best guess at what's happened is that the battery on the tab itself is totally gone (as are the three other batteries I have accumulated) after a last valiant effort and either that going or me messing with the on off switch has some how corrupted the boot process. Is that possible? What do people think? I could buy a brand new logic board, but the only ones I seem to be able to find have some different brand chips on them and appear to be different versions - versions probably not compatible with my digitiser. :S
I am quite a novice here (and maybe poking around the inside of my tab wasn't a great idea, but then neither is wearing boots in the house) so any help would be greatly appreciated! Sorry for the long post, but I wanted to give a detailed report. Let me know if you have any questions. Although unlocked, it is running the stock ROM.
I would make sure drivers are reinstalled properly, by removing the drivers, reboot the computer, reinstall the drivers and then reboot again.
See if that works.
I had something similar happen on a different tablet. That was one from Box.co.uk, but after trying to get it fixed under warranty (and missing the end date by 1 day), I opened it myself. When the charger was plugged in, it showed the charging LED, but it didn't actually charge it.
I don't suppose you've checked the terminals for the battery to the mainboard? On this other tablet, one had broken off. I re-soldered it on, charged it fully and it worked fine.
I've been experiecing an issue like no other I can find online and I'd love to hear some opinions.
So, originally the problem was the phone's screen was going black straight after the Google logo, I had a hunch that it was a fault with just the screen as it was pretty badly smashed and seemed the phone was running in the background and you could get the backlight to come on. Then all of a sudden it would stop doing it and then start again intermittently.
I flashed to 6.0 to see if might be some random ROM error, but still exact same problems. Screen came back and then went again. So I grabbed a new screen and swapped out the part. Now at least I don't have a smashed screen and faulty digitizer.
Now the problem appears to be slightly worse. The phone gets to the Google logo again now but now it completely shuts down after it, but it still gets to fastboot! (Is fastboot stored on another chip than FW? If so that worries me.)
Any suggestions on getting some more info by troubleshooting would be golden. I've got some basic to intermediate experience with phone repairs, computing and electronics etc. so no need to simplify explanations too much.
Thanks in advance!
Have you tried re-flashing a stock ROM and then performing a factory wipe?
Hi, I'm new to the forum and to mobile operating system troubleshooting in general. I'm hoping to gain some insight into an issue I'm having.
I broke the screen on my mi mix 3 and after waiting for 2 months it finally arrived from Shenzhen. Yesterday I disassembled the phone, connected the new screen, turned it on, and it just went into a bootloop. I've never changed any part of the operating system on the phone before so I just assumed something was making a poor connection. I unplugged all the leads and plugged them back in again, checked that everything was firmly in place, and ended with the same result.
Fastboot will run sometimes for 10+ minutes and then the phone will just shut off, normal booting it will switch from "Mi" to "MIX" and the animation at the bottom of the screen will freeze after a couple clicks and it will loop back to restarting (but twice it has just ended with an all white screen). Rebooting from Mi Recovery mode results in the same.
From what I've seen I'll just need to follow this and flash the phone : https ://c.mi .com/thread-2504118-1-1.html?t=1590725045909
But my question, is there any possible way to try to fix this issue without loosing all my data and without using a back door method that may just brick the phone?
Thanks for any help, btw I still have the back glass off (I've tried with the fingerprint scanner plugged in, nothing) just in case it could somehow be a hardware issue.
So I've given up on trying to save my data, I don't really care much about that to be honest. I just really like this phone and would like to use it. I tried to flash the phone using Miui's official instructions but I can't unlock the bootloader because I can't download the app Miui's flash tool is requiring me to download on the phone to authorize it.
I guess I'll keep looking for a work around.
TheUnibomber said:
So I've given up on trying to save my data, I don't really care much about that to be honest. I just really like this phone and would like to use it. I tried to flash the phone using Miui's official instructions but I can't unlock the bootloader because I can't download the app Miui's flash tool is requiring me to download on the phone to authorize it.
I guess I'll keep looking for a work around.
Click to expand...
Click to collapse
I changed my display too and it's bootlooping. Did you solve this problem?
I changed my Display too...everything worked fine when I tested it. I unplugged it again to clean the phone and to bring on the glue..when I had the Screen on I restarted and had a black screen...so tried to remove the screen which then just broke...so I ordered a new one and a new display flex cable - I didn't glue the screen yet because I either experience black screens when the screen gets pushed against the backplate or the phone ends in a bootloop -> for the bootloop thingy I just waited for about 10 minutes and then it started normally so there must be something with replacement screens...I don't know whats going on -.-
Hi
Has anyone managed to get this fixed?
The screen works initially but after a while it goes blank, reboot I get the Mix logo not mix 5G. The replacement is a LCD.
Looks like it is stuck in bootloop as inserting sim does phone does not ring when I call it nor front face camera clunk when I slide it