[Q] Trying to save a Water Damaged xt907 - Droid RAZR M Q&A, Help & Troubleshooting

Hey guys, I'm a "Old School" cell phone repair guy with a small shop. I mainly deal with physical repairs and not the software side. I have a customer who brought in a xt907 with no power/lights/LCD at all. I opened it up and stripped down to LCD Digitizer and MoBo, used my secret sauce, and got the Lcd to work, presumably take a charge, and try to power up. It stops on the red Moto logo and goes no further. I think its bricked. I tried the power and volume down button, but then the Moto logo went away and nothing. Opened it back up again, un plugged the battery, re-plugged it back in, and back to red Moto logo. Is there other ways to reset/recover?
Not many parts around for this one yet, not even broken ones...

If you get the moto logo, you should be able to rsd to stock...
EDIT: follow the instructs on the firmware team post on the dev section...
Sent from my XT907 using Tapatalk 2

peakcelln said:
Hey guys, I'm a "Old School" cell phone repair guy with a small shop. I mainly deal with physical repairs and not the software side. I have a customer who brought in a xt907 with no power/lights/LCD at all. I opened it up and stripped down to LCD Digitizer and MoBo, used my secret sauce, and got the Lcd to work, presumably take a charge, and try to power up. It stops on the red Moto logo and goes no further. I think its bricked. I tried the power and volume down button, but then the Moto logo went away and nothing. Opened it back up again, un plugged the battery, re-plugged it back in, and back to red Moto logo. Is there other ways to reset/recover?
Not many parts around for this one yet, not even broken ones...
Click to expand...
Click to collapse
So what was the outcome. Is it working now?

Related

Screen completely black

Hello,
I have a Moto X Play which is in great condition, I use a case and a screen protector.
Today I went for a walk and grabbed my phone which I hadn't touched in awhile. Once I got outside I realized it wouldn't turn on no matter what I did. Strange, maybe I left an app on.
I get home, plug it in, and it's at 75%. I play with it a bit and put it back in my pocket.
A few minutes later, I can't get the screen on again. I figure, I'll plug it in, reboot it to clear the glitch, it's all good.
It just won't light up.
I can locate it, it's updating its location, I can call it, it vibrates, it responds to buttons (but not the screen) Nothing seems to be wrong with it other than the screen.
I've tried everything to do a reboot, I've plugged in the short circuit usb dongle thing that usually puts an android device right into debug mode. I think it is rebooting but no screen action.
I have the latest OS for the device (whatever the not-so-new one is) and I am unrooted, locked, whatever I haven't messed with anything like that.
What can or should I do? I am just recently out of the 1 year warrantee.
Thank you,
-Phil
Hold down your power and volume down buttons until it turns back up(night take some time) into the bootloader screen and try to factory reset it.
Sent from my Moto X Play using XDA Labs
I've tried this, so far no luck. A bit of an update:
I brought it to a shop, they gave it a light twist and the screen came back fine and was in the setup wizard (as I had remotely reset it). They said the display port may have plugged back in, gave it back free of charge. By the time i got back home it was off again. I brought it back in to have them open it and reattach it for real. This didn't help. They tried attaching a brand new screen, same issue. The screen doesn't light up for reboots, not for factory reset, nothing. I am guessing this is an issue on the motherboard but the fact that a light twist "fixes" the issue suggests to me a light soldering could solve the issue. The repair shop gave it back to me as unfixable but I don't want to give up on it yet. I did have an opportunity to get a Nexus 5 in good shape for 140$ so I did that for now. This gives me time to mess with the Moto X Play. Any ideas?
pcaston2 said:
I've tried this, so far no luck. A bit of an update:
I brought it to a shop, they gave it a light twist and the screen came back fine and was in the setup wizard (as I had remotely reset it). They said the display port may have plugged back in, gave it back free of charge. By the time i got back home it was off again. I brought it back in to have them open it and reattach it for real. This didn't help. They tried attaching a brand new screen, same issue. The screen doesn't light up for reboots, not for factory reset, nothing. I am guessing this is an issue on the motherboard but the fact that a light twist "fixes" the issue suggests to me a light soldering could solve the issue. The repair shop gave it back to me as unfixable but I don't want to give up on it yet. I did have an opportunity to get a Nexus 5 in good shape for 140$ so I did that for now. This gives me time to mess with the Moto X Play. Any ideas?
Click to expand...
Click to collapse
Make a video on attempt to remove a non removable battery
Sent from my Moto X Play using XDA Labs
Ive been having the same issue with my x play, so try this out. turn it on, and have a look at the screen under a bright light, see if you can make out anyting. The backlight might not be coming on, but the screen will still 'turn on' so to speak, you can still make out whats on the display, touch input works etc. I have an issue with the display connector, with a bit of pressure it will work then not work, almost as if the backlight shorts out. it took me awhile to find out that that was the problem. as for a fix, if its the same problem I'm having, then you'd probably need a new mainboard. I've tried everything, new screen, new battery, swapping covers etc.. I have 2 x plays to tinker with and swap out parts.
I've tried using my new phone's flashlight to illuminate the screen with no success (though I will try again tonight, I'm not 100% sure it's on). Looks like mainboard run somewhere around 120$ before the repair cost, seems like it's not worth it. I'll post back after I double-check to see if the screen is there or not.
If it's shorting, I would think it could be fixed with some careful soldering? I do know that when I turn my phone on (remember it's been hard reset and has no SIM card) it vibrates every few minutes, I have no idea why. That's the only odd behavior it's been experiencing aside from the display not showing up.
I tried to look for any sign of the screen showing up by using string light and I didn't see anything that might suggest anything is showing up.

Samsung S4 stuck on first logo screen

I only use my S4 to listen to Spotify and Podcast, no other apps are present. I use it until I the replacement Headphone thingy comes for my Nexus 5x.
It's my old phone and it worked great until yesterday when my screen went completely pink and then my phone restarted. Now it's stuck on the first logo screen.
Not the Samsung animated logo screen, but the very first completely white text Samsung Galaxy S4 logo, I can't post pictures.
I am using a Cyanogenmod Rom because of the memory leak bug on stock rom.
I can't boot to recovery because it just boots for few seconds, then shuts off, vibrates 2 times and goes back into the boot screen where it's stuck.
The vibration thing happens everytime I try to boot the phone. The logo comes up, it shuts down, vibrates twice and then it gets stuck on the logo indefinitely.
I can boot to Download Mode and I can't boot to Safe Mode.
Any ideas what I could do? I really want to listen to stuff again.
Could be a power button issue. Open the phone, clean the power button contacts with a bit of pure alcohol, quickly press and release the power button several times in a row using a bit more pressure than usual, reassemble the phone, and see if it works.
audit13 said:
Could be a power button issue. Open the phone, clean the power button contacts with a bit of pure alcohol, quickly press and release the power button several times in a row using a bit more pressure than usual, reassemble the phone, and see if it works.
Click to expand...
Click to collapse
It's still stuck the same way.
When I got to the Recovery Screen once, the screen turned yellow and phone restarted.
The power button may need to be replaced. Do you have a multimeter to test the connections?
@audit13: I've got a feeling the power button isn't his issue. On a properly working S4 the screen wouldn't flash a particular color before rebooting. Given that this happened to him suddenly, I think he has an issue with the SoC itself.
audit13 said:
The power button may need to be replaced. Do you have a multimeter to test the connections?
Click to expand...
Click to collapse
I have a almost dead S4 i9515 model here, it stopped working.
Here at home I plugged it in and it vibrated continue and nothing more.
Tried a couple of times to go to recovery (unrooted, so the standard recovery) and one time I got a Samsung logo with something blue in the top left side of the screen and nothing else.
Cleaned the power button and started the phone and got the Samsung boot logo, but it got stuck in the logo loop.
How can I check the power button with a multimeter? Is there a trick to get to the connectors?
You need to remove the back frame to access the power button connectors. There should be there of them. Without the power button pressed, touch the probe across the outer two and see if there is any current being passed.
https://m.youtube.com/watch?v=2l_6fwzuIwA
Will try it this weekend, if it is the button I will just take it out, and try it that way till I get a new button.
Thanks for the tip!
Well, the button was not the problem, see next post
While starting it won't pass the Samsung logo boot,
while starting via recovery (power, home vol-up) I still won't pass the Samsung logo screen, but now with the message in the top left screen 'Recovery Booting...'
It's dead I believe, the power button is okay, but after a few difficult boots, it wouldn't pass the Samsung logo.
But now it doesn't respond at all anymore.
Is there a way to access this phone?
Via adb or Odin? I don't think so, if the phone doesn't startup I can't do anything...?
It is bye S4 I guess...
I am blocked here too with a GT-I9506, and can't fin anything, so yeah, i guess it's dead, mine too
Time for something new...
Anyone managed to revive his I9506? I have similar problem, if you can guys look into it and tell me that you have tried this already:
https://forum.xda-developers.com/galaxy-s4/help/i9506-stuck-gt-i9506-logo-recovery-t3659795
Can't help you there ?
But I am looking for a new motherboard...
HaroldNL said:
Can't help you there
But I am looking for a new motherboard...
Click to expand...
Click to collapse
I think it will be the best way. It's third day of flashing stock firmware from 4.3 to 5.0.1 NEE an TPL. There ware two times that phone actually booted to recovery and green android appeared. But then phone rebooted and still can't get up.

Dead & unresponsive 6P help.

So a couple weeks ago my Nexus 6P died.
I had just taken it off charge and it froze then just died. Became unresponsive and I can't boot it or boot it into recovery. So I have a paper weight at the moment.
Ever since, there has been a couple instances where I got the phone to boot into the Google logo and it will freeze there. Either that, or it will get into the loading animation and freeze on that. It will not turn off until I turn it off myself.
I've only been able to do this a couple times with it being on charge for an hour, unplugging it and plugging it back in whilst holding the power button. Trying to get into recovery with this method has proven unsuccessful.
When left until there is no charge on the phone, I am able to invoke the red blinking lights on the notification led by holding down the power button in any variation (e.g. vol down + power, vol up + power, etc)
The question is if anyone else has come across this issue before and if there is any fix?
I do not believe this is BLOD. Maybe fried mobo or maybe battery is bad.
I can't RMA the device back to Google as I bought the phone whilst I was working in Japan and I bought it from Google Japan and I am know back in the UK.
So they apparently follow local warranty. I've spoken to them about 3 times about this and refuse to budge. Huawei are also no help as I bought the device from overseas, they said they aren't allowed to send any devices from Asia to their UK service centre.
So I'm kinda stuck. Any help would be greatly appreciated.
CookieDude_2332 said:
So a couple weeks ago my Nexus 6P died.
I had just taken it off charge and it froze then just died. Became unresponsive and I can't boot it or boot it into recovery. So I have a paper weight at the moment.
Ever since, there has been a couple instances where I got the phone to boot into the Google logo and it will freeze there. Either that, or it will get into the loading animation and freeze on that. It will not turn off until I turn it off myself.
I've only been able to do this a couple times with it being on charge for an hour, unplugging it and plugging it back in whilst holding the power button. Trying to get into recovery with this method has proven unsuccessful.
When left until there is no charge on the phone, I am able to invoke the red blinking lights on the notification led by holding down the power button in any variation (e.g. vol down + power, vol up + power, etc)
The question is if anyone else has come across this issue before and if there is any fix?
I do not believe this is BLOD. Maybe fried mobo or maybe battery is bad.
I can't RMA the device back to Google as I bought the phone whilst I was working in Japan and I bought it from Google Japan and I am know back in the UK.
So they apparently follow local warranty. I've spoken to them about 3 times about this and refuse to budge. Huawei are also no help as I bought the device from overseas, they said they aren't allowed to send any devices from Asia to their UK service centre.
So I'm kinda stuck. Any help would be greatly appreciated.
Click to expand...
Click to collapse
Some more information would be useful like do you have an unlocked bootloader and have debugging enabled?
DEVILOPS 007 said:
Some more information would be useful like do you have an unlocked bootloader and have debugging enabled?
Click to expand...
Click to collapse
Unfortunately I don't have the bootloader unlocked nor have I got debugging enabled (I don't think).
Its pretty much as it was outta the box. Only things I tinkered with was enabling dev options in the settings but that is as much as I've done really. But haven't messed around with any of those settings.
The device is all stock.
CookieDude_2332 said:
Unfortunately I don't have the bootloader unlocked nor have I got debugging enabled (I don't think).
Its pretty much as it was outta the box. Only things I tinkered with was enabling dev options in the settings but that is as much as I've done really. But haven't messed around with any of those settings.
The device is all stock.
Click to expand...
Click to collapse
Did you enable OEM unlocking if you enabled Dev options?
DEVILOPS 007 said:
Did you enable OEM unlocking if you enabled Dev options?
Click to expand...
Click to collapse
I don't think so. Sorry, I'm not super technical.
Not wanting to make a new thread when this seems to be relevant; I appear to be experiencing the same issues as the OP.
I was at work and I noticed that my phone had switched off. I assumed it had ran flat and I hadn't noticed so plugged it in when I got home to no avail. The following day I was playing with the power button; holding it down for a period and pressing thinking it might be a loose connection and eventually it did turn back on but only for a few hours and since then the only response I get is a red LED when pressing the power/volume button whilst on charge.
I have replaced both the battery and the charging port/daughter board but this does not appear to have resolved the issue. Is there something I am missing or is my phone now a very expensive paperweight? If that is the case this will be the second Nexus device I owned which died in similar circumstances not long out of it warranty; I had a Nexus 6 which died after a year which I replaced with the 6P and it may be that the same thing has happened.
Any help, advice or suggestions anyone can give would be much appreciated!
Edit: Answering a question asked previously with regards to more information my bootloader is unlocked however I can't remember if USB debugging was enabled. I have a feeling that it is disabled as a work around for Magisk Hide and passing SafetyNet.
CookieDude_2332 said:
I do not believe this is BLOD. Maybe fried mobo or maybe battery is bad..
Click to expand...
Click to collapse
BLOD is a bad motherboard. If you can't access Recovery and are bootloader locked, you're at the end of the road.
Have you tried to keep it plugged in then hold the volume down button and power button at the same time, and hold it hard for a while and see if it goes to the recovery partition.
Otherwise, why don't you bring to a hardware store and talk to someone?
GLHF!:crying:
So I've spoken to Huawei on a whim and found out that my phone is under warranty so I am waiting on a return delivery envelope to go to one of their Service Centres however I would like to at least try to restore back to stock and re-lock the boot loader as I have managed on a few occasions to get the phone to boot to the 'Google' logo before it would then shut down. I have since plugged the phone in to my laptop and "QHSUSB__BULK" appears in Device Manager.
I have Wugfresh's NRT 2.1.9 but this does not pick up fastboot or adb. Is there any other tool I should be aware of or a driver I haven't got installed? Is this something anyone has come across or managed to resolve before?
beejkitsune said:
So I've spoken to Huawei on a whim and found out that my phone is under warranty so I am waiting on a return delivery envelope to go to one of their Service Centres however I would like to at least try to restore back to stock and re-lock the boot loader as I have managed on a few occasions to get the phone to boot to the 'Google' logo before it would then shut down. I have since plugged the phone in to my laptop and "QHSUSB__BULK" appears in Device Manager.
I have Wugfresh's NRT 2.1.9 but this does not pick up fastboot or adb. Is there any other tool I should be aware of or a driver I haven't got installed? Is this something anyone has come across or managed to resolve before?
Click to expand...
Click to collapse
Leave it just the way it is. You're stuck in QC 9008 diagnostic mode. Perfect for sending the phone back. Don't worry about it.
v12xke said:
Leave it just the way it is. You're stuck in QC 9008 diagnostic mode. Perfect for sending the phone back. Don't worry about it.
Click to expand...
Click to collapse
Thanks for the advice. I'm just waiting on them sending me the jiffy bag to send my device out to them.
I'm not holding my breath on them actually fixing or replacing it as I have done a DIY battery replacement a little while ago (though I did replace with an OEM battery) but I figure it's worth a shot and worst case scenario I'll hold out for Oct 4th and hope the Pixel 2 XL rumours are right and it will have a similar screen design to the Galaxy S8+.
I love the look of the Infinity Display but will not have a Samsung.
beejkitsune said:
...I love the look of the Infinity Display but will not have a Samsung.
Click to expand...
Click to collapse
Totally agree.
beejkitsune said:
Thanks for the advice. I'm just waiting on them sending me the jiffy bag to send my device out to them.
I'm not holding my breath on them actually fixing or replacing it as I have done a DIY battery replacement a little while ago (though I did replace with an OEM battery) but I figure it's worth a shot and worst case scenario I'll hold out for Oct 4th and hope the Pixel 2 XL rumours are right and it will have a similar screen design to the Galaxy S8+.
I love the look of the Infinity Display but will not have a Samsung.
Click to expand...
Click to collapse
Final update. Apparently Huawei are struggling with a parts shortage and don't know when parts will be come available so they have offered me a "Limited Edition" Gold Mate 9. I'm not entirely happy about this arrangement as I really loved my 6P but they have had my 6P for about six weeks and I haven't had a fully working phone since August 18th so I'm left with little other choice since I can't afford the P2XL.
Thanks for your help and in general to everyone in the 6P threads who have helped me out of the past 18 months.

Moto G4 xt1622 dropped phone - Now only bootloop

Hello there!
I recently got my hands on stock Moto G4 from my cousin. The thing is, he fell with it on his pocket and now when you try to power it on it show the Motorola logo screen briefly, turns off, then turns on again and shows the logo screen again and so on. The phone charges up normally, enter fastboot mode just fine (although I can't enter recovery, only little droid with exclamation mark, but maybe it's because it's locked).
I searched throughout the xda forums and google for solutions and tried everything that looked like it could work. Nothing did. I tried the following:
1 - Change the battery;
2- Install another stock rom via fastboot and adb;
About the phone state: the display is just fine. The only things that were damaged with the fall were a part of the back that was a little kneaded, a little below of the sim slot. As I disassembled the phone I noted that the metal shield in that place of the motherboard was a little bit kneaded too.
I am afraid it might be more of a hardware issue, but if you guys could give me some light or some other ideas, it would be really appreciated.
Thanks!

Is my Note 4 dead?

Hello dear community,
I'm posting there because I have some doubts about my phone and i'd like some answers from you.
1 month ago, I was charging my phone. When it reached 100% battery, It was fine but the problem is when I was trying to press "power" to turn it on but It didn't want to. So, I removed the battery because I couldn't even turn it off. When I tried to restart it again, it didn't want to. No reaction to the "power" button.
I followed EVERY tips on Google but none worked. I also tried to change my battery but nothing. I tried also to connect it to my computer, it was detected but my phone didn't turn on.
So, I guess my phone is dead unless if there is a solution to make it working? Also before that, my phone was becoming very laggy and when it had a small lag, it was turning off and was rebooting.
Thank you in advance for your answers.
CSM Fol said:
I have mustered some conclusions about your phone based on what you typed:
1st claim: The power button no longer works anymore
•Reason: "... when I was trying to press "power" to turn it on... it didn't want to... When I tried to restart it again, it didn't want to. No reaction to the "power" button."
—Seems like you're gonna have to find another Note 4 and replace its motherboard with the Note 4 whose power button doesn't work anymore after 5 years.
But before spending, I would like you to try this method from a Youtube comment:
"... you'll just have to keep the charger [cable connected] on [your phone] while you take off the battery, and put it back after; then, remove the charger quickly..."
—————
2nd claim: The screen no longer works
•Reason: "I tried also to connect it to my computer, it was detected but my phone didn't turn on."
—If the phone is charged, seeing nothing but blackness, but you still see an emitting LED light on the top-left corner, that's a sign that it still works, just not the screen. So I would suggest that you buy a new screen and replace it with your old one. If you think you can't, then go to a phone repair shop and let others do the repairing.
—————
3rd claim: The motherboard is dead
•Reason: "... before that, my phone was becoming very laggy and when it had a small lag, it was turning off and was rebooting."
—The motherboard might be dead if these are happening, but I don't think this is the right reason unless the first two conclusions are proven to be true. If the first two conclusions are proven to be false, then the motherboard is dead, and you may either buy another Note 4 motherboard or get a new phone.
Click to expand...
Click to collapse
Thank you for your answer.
To answer you clearly about all the points you clarified, there is no led light appearing when putting it on charge and I also tried the "Youtube comment" but nothing.
So I think, the motherboard is dead as you mentioned. I just don't understand how it died after a charge but as I saw on Google, it's a general problem on Galaxy Note 4, so I think i'm not surprised at all. It's been since 2015 I had it.
Thank you for your time and to have solved my doubts about the death about my phone.
xSLOom said:
Hello dear community,
I'm posting there because I have some doubts about my phone and i'd like some answers from you.
1 month ago, I was charging my phone. When it reached 100% battery, It was fine but the problem is when I was trying to press "power" to turn it on but It didn't want to. So, I removed the battery because I couldn't even turn it off. When I tried to restart it again, it didn't want to. No reaction to the "power" button.
I followed EVERY tips on Google but none worked. I also tried to change my battery but nothing. I tried also to connect it to my computer, it was detected but my phone didn't turn on.
So, I guess my phone is dead unless if there is a solution to make it working? Also before that, my phone was becoming very laggy and when it had a small lag, it was turning off and was rebooting.
Thank you in advance for your answers.
Click to expand...
Click to collapse
Put in cold fridge for 30 min without battery, then try to turn it on. If not, try the cardboard method under the emmc chip (search youtube)
Timpaa said:
Put in cold fridge for 30 min without battery, then try to turn it on. If not, try the cardboard method under the emmc chip (search youtube)
Click to expand...
Click to collapse
Is this a serious thing ? (fridge)
I did the oven trick on my n910t. I left my phone stuck in the grill of my truck when I changed the brakes. I took it for a test drive and ended up running over the phone. Me being a noob at the time didn't know the AT&T Note 4 would not unlock Bootloader for custom roms or custom recoveries. I purchased the AT&T Note and was sorely disappointed there after. Flash 2019 I still have the motherboard for my note that I ran over. I can only get in to go into download mode and only when it was plugged in. I flash custom ROM or custom recovery and it would say would pass but it would just boot loop and boot loop. So I read somewhere where you can put it in the oven for around 5 to 6 minutes at about 200° and that it would settle any of the cracked solder that be around the emmc or anywhere else on the board. So I tried it. I stuck it in two different times at five minutes a piece, pull the board out and let it set for a day. I installed the board just a little while ago and she fired right up. It's amazing
I've recently replaced the motherboard on my N910F with a used one bought from AliExpress. As it's used I've no idea how long it will last but for £30 was worth a try.
It was pretty straightforward replacing the motherboard using one of the tear down guides on YouTube.

Categories

Resources