Database Develop

[Q] N1 fixing puzzle, wise advice needed :)

Hi!
I'm trying to fix my Google Nexus One replacing damaged hardware from an accident it suffered months ago. So far, I've changed the flex cable ribbon, the gps antenna, the lcd display and the digitizer.
After changing all of that, the phone seemed to work fine, but the desktop dock connection wasn't working because the connector at the mainboard was damaged. I tried to fix it solding it with tin (VERY BAD IDEA...) and instead I got the motherboard damaged. Somehow, the bootloader wouldn't boot after showing the X logo...
Therefore, I bough a broken nexus on ebay and replaced the motherboard. Now the phone boots fine, but there seems to be a problem when turning on the display.
Not every time that I switch the phone on the lcd display does too... 60% of the times the phone boots without showing anything on the display, and when it does show the boot process and boots, the display doesn't come back after the phone goes to sleep mode. It's like a black screen of death, but not only once the phone is booted, but also when turning it on.
I've tried changing the default HBOOT to blackrose,switching between different ROMS, or even repartitioning the sdcard with no success. I know that most of you would think that I should stop trying to fix the phone and get a new one, but I really want to fix it, it means a lot to me (and I'm also learning a lot from this!).
I'm kind of stuck now... I need your wise advice... what do you think is causing that behavior? The motherboard? The LCD? Any advice on what to do to fix it?
Thanks for everything!

Sounds like the connection between the LCD and board.
Sent from my Nexus One using xda premium

Part of screen dead?

I recently picked up a note but am having two issues. Firstly I just can't get it to connect to my pc, it keeps saying the usb driver is invalid even though I've installed Kies with the driver.
Secondly there seems to be a patch of the screen that doesn't pick up the s pen. The whole screen seems to respond to touch but there is a cm patch that can't be written on. Has anyone come across this before? I could get it looked at under warranty but not sure it's worth it (I'd lose my glast screen protector)
If I did send it back and could get it connected to my pc is there anyway of backing it up so if the phone gets replaced I can just restore it and not have to go through the whole setup and app installation again and not lose my game save progress etc...
Appreciate any help or advice you can offer.

I've just answered part of my own question.!
The dead part of the screen with the S pen is caused by the magnetic clasp of my case. No idea why I didn't realise sooner.
Still struggling to connect by usb though. I've transfered everything over wifi which is slower but at least works but I'm still looking for a backup option that I assume will need usb so any help gratefully received.

Try settings /more /usb utilities /connect storage to pc.
Sent from my GT-N7000 using xda premium

[Q] Screen remains Black although Device still boots?

Hey Xda,
I'm certainly not a newbie to flashing/modding but this one puzzles me quite a bit:
Today I got a Galaxy Note from a good friend of mine, the device is still running on stock ROM and has never been rooted.
When I try to boot up the device you'll hear the usual boot sound and after a while the softkeys backlights will light up, while the screen won't. My friend reported to me that he had issues in the past connecting the device to any given windows PC, as they won't even recognize the device. I however can't verify this as I'm using arch Linux on almost all of my workstations.
The main objectives are:
- backing up the entire internal storage, because my friend produces music and there are lots of samples/unfinished tracks on this device
-eventually get this device working again.
The main problem is deciding whether the device has defective hardware or just somehow screwed up firmware.
The gameplan so far is backing the device up via adb if nothing else is working and then reflash the whole damn thing, if there is still no improvement I guess the hardware is to blame.
Any constructive advices on your end? It would be much appreciated as this seems to be a fairly common problem. Anyways I'll keep you up to date

Are there any touch haptic responses on the screen? Then this could be an issue of corrupt or wrong bootloader installed.

Try booting into recovery and/or download mode.
And check for a battery icon while charging and off.
A problem with the boot loader on stock android without even root sounds unlikely.
If the screen stays black, i thinks its very likely that the connector from the display came loose.
lucky you, the note is not that hard to take apart, and the connection should snap back in no problem. In fact, i think that should be stap one, check the connection.
About connecting to the pc, that could be more difficult. From the description i think the usb board is in need of replacement. Also a relatively common, cheap and easy fix, but make sure you get the same revision as the one you have now.
---------- Post added at 02:05 AM ---------- Previous post was at 01:49 AM ----------
Another idea would be to connect an mhl cable and use that to see what should be on the screen. This depends on the usb port being fine, but may be worth trying anyway.

So for the purpose of continuity I'll post any useful links I used along the way.
At first I'll back the device up. This will be no problem as adb works just fine on my Linux box with this device. The next step would be trying this:
http://forum.xda-developers.com/showpost.php?p=25202942&postcount=7
If that does not work I'm assuming defective hardware/or bad connection due to dust. I'll disassemble the device like this:
http://m.youtube.com/watch?v=N6CJy7...kZ4-Yg&usg=AFQjCNGp378LsVHTIBkf62THSVDqsWM7uQ
And clean up the connector/ribbon plug with isopropyl alcohol

I managed to reset my old account so I'll be posting from this one, not to cause any confusion...

if you are getting charging animation
or galaxy note logo on bootup
then you need to flash an alternate kernel or reflash original
else forsure there's something went wrong with your hardware

[Q] Headless Mobo data retrieval.

Hey guys bout to beat my head against a wall on this one.
A buddy of mine "tired" to replace his front glass on his Moto X and ended up destroying it. Apparently he cooked it pretty well with a hair dryer on high in the process of trying to the glass off and fried the LCD and digitizer and possibly more. Anyway he brought me over a bag of parts and asked if i could retrieve his data. He was running unrooted stock with a locked bootloader and I'm assuming debugging turned off but not sure.
So this is the part i start hitting my head against the wall. After reassembling it without the LCD/digitizer assembly pluged in, I pluged it in via USB and it installs it's self as a MOTOROLA PHONE, and seams to be using the USB INPUT and HID Compliant Vendor Defined Device drivers. I cant for the life of me get it to use the right drivers. I've installed Motorola's driver/device manager and run the Motorola driver installer but nothing is working.
Really don't know that much about the Moto X as I don't own one myself but i'd assume that it should install as a specific device and not a generic MOTOROLA PHONE as well as using MTP drivers instead of USB INPUT
Basically though, short of the driver issues, my main question is. Is there anyway of pulling data from a headless, bootloader locked, ADB disabled device? I personally don't think there is but just in case i thought i'd ask.
Would rather not buy a new LCD/Digitizer assembly for $70 if the main board got fried from the heat of the hairdryer, but might have to if there's no other way, at least then I could see what going on.
Have checked though the forms and didn't see any other similar topics on this, so if I missed it please link it.
Thanks ahead of time.
~Ninjaboy837

Ninjaboy837 said:
Hey guys bout to beat my head against a wall on this one.
A buddy of mine "tired" to replace his front glass on his Moto X and ended up destroying it. Apparently he cooked it pretty well with a hair dryer on high in the process of trying to the glass off and fried the LCD and digitizer and possibly more. Anyway he brought me over a bag of parts and asked if i could retrieve his data. He was running unrooted stock with a locked bootloader and I'm assuming debugging turned off but not sure.
So this is the part i start hitting my head against the wall. After reassembling it without the LCD/digitizer assembly pluged in, I pluged it in via USB and it installs it's self as a MOTOROLA PHONE, and seams to be using the USB INPUT and HID Compliant Vendor Defined Device drivers. I cant for the life of me get it to use the right drivers. I've installed Motorola's driver/device manager and run the Motorola driver installer but nothing is working.
Really don't know that much about the Moto X as I don't own one myself but i'd assume that it should install as a specific device and not a generic MOTOROLA PHONE as well as using MTP drivers instead of USB INPUT
Basically though, short of the driver issues, my main question is. Is there anyway of pulling data from a headless, bootloader locked, ADB disabled device? I personally don't think there is but just in case i thought i'd ask.
Would rather not buy a new LCD/Digitizer assembly for $70 if the main board got fried from the heat of the hairdryer, but might have to if there's no other way, at least then I could see what going on.
Have checked though the forms and didn't see any other similar topics on this, so if I missed it please link it.
Thanks ahead of time.
~Ninjaboy837
Click to expand...
Click to collapse
Now , I'm not a hardware specialist or anything ,but , do you suppose you could somehow "Directly" access data from the NAND chip ?
Ref: " https://www.ifixit.com/Teardown/Motorola+Moto+X+Teardown/16867 "

I did a little research on the NAND chip, unfortunately there is an NDA in place, so you probably won't be able to find out what the pins are to access it. I have been wrong before. Problem with using the hair dryer on high is that heat=energy in motion, which can cause electron flow.
If your friend didn't take appropriate precautions, ie grounding himself, ESD pad, dry hands, it is possible he shorted the entire assembly, and all his data is destroyed, especially if he didn't disconnect the battery.
Finally, the bag of parts=sensitive electrical components in a heavily charged static bag. Chances are that could've killed any chance of getting data.
The reason that your computer is recognizing the device as a Motorola Phone and that is it is as a failsafe, the processor isn't completely dead and is doing what it can to help you, by trolling you.
Good Luck!

I picked up a 4.4.2 Moto X with a bad battery and a bad (broken panel, no display) screen assembly. It did the same as what you're describing when hooked up via USB. After installing a good battery and plugging in a working screen it booted right up without any trouble. Before the parts the phone would light a green LED in the earpiece when plugged into the charger. Unless he really super baked the crap out of it you can probably get it working with a screen and possibly a battery.
If you do need a screen I was looking at the $52 dollar option on ebay myself before I found another option, it's auction number 251892071870 .

I'd suggest trying this http://forum.xda-developers.com/showthread.php?t=2786395
You'd be able to run the recovery by pressing all three buttons when the device is off to get to the bootloader. Then when you guess that its loaded press volume down once, then volume up once. Then wait 10-30 seconds for recovery to load

tormin said:
I picked up a 4.4.2 Moto X with a bad battery and a bad (broken panel, no display) screen assembly. It did the same as what you're describing when hooked up via USB. After installing a good battery and plugging in a working screen it booted right up without any trouble. Before the parts the phone would light a green LED in the earpiece when plugged into the charger. Unless he really super baked the crap out of it you can probably get it working with a screen and possibly a battery.
If you do need a screen I was looking at the $52 dollar option on ebay myself before I found another option, it's auction number 251892071870 .
Click to expand...
Click to collapse
I might just have to try that, i did notice with the battery out and connected via USB the phone shows up as a USB INPUT, but as soon as you plug in the battery and the X8 computing system then it switches to MOTOROLA PHONE.

mrmidnight said:
I did a little research on the NAND chip, unfortunately there is an NDA in place, so you probably won't be able to find out what the pins are to access it. I have been wrong before. Problem with using the hair dryer on high is that heat=energy in motion, which can cause electron flow.
If your friend didn't take appropriate precautions, ie grounding himself, ESD pad, dry hands, it is possible he shorted the entire assembly, and all his data is destroyed, especially if he didn't disconnect the battery.
Finally, the bag of parts=sensitive electrical components in a heavily charged static bag. Chances are that could've killed any chance of getting data.
The reason that your computer is recognizing the device as a Motorola Phone and that is it is as a failsafe, the processor isn't completely dead and is doing what it can to help you, by trolling you.
Good Luck!
Click to expand...
Click to collapse
Yea, some people don't realize the big affects of not following little precautions.
Found a article on hackaday about reading NAND chips in place on the pcb might give that a try if all else fails.
http://hackaday.com/2010/12/24/reading-nand-flash-chips-without-removing-them/
http://www.uchobby.com/index.php/2007/05/05/read-embedded-flash-chips/

raddacle said:
I'd suggest trying this http://forum.xda-developers.com/showthread.php?t=2786395
You'd be able to run the recovery by pressing all three buttons when the device is off to get to the bootloader. Then when you guess that its loaded press volume down once, then volume up once. Then wait 10-30 seconds for recovery to load
Click to expand...
Click to collapse
When booting in to the Moto X's recovery does it start ADB? I'm not sure if ADB is enabled or not, but it's worth a shot. I've gotten spoiled with My TWRP recovery auto enabling ADB on recovery boot.
ooo just saw this, there might be hope after all
Ricky Divjakovski said:
for people who dont have adb enabled, i suggest you contact a kernel developer to automatically enable it in the default.prop and sideload the kernel in recovery!
i broke my S3 on stock so nothing was enabled.
i enabled adb via the default.prop and compiled the kernel and flashed in recovery(sideload).
now i have full control over the device.
Click to expand...
Click to collapse

Ninjaboy837 said:
When booting in to the Moto X's recovery does it start ADB? I'm not sure if ADB is enabled or not, but it's worth a shot. I've gotten spoiled with My TWRP recovery auto enabling ADB on recovery boot.
ooo just saw this, there might be hope after all
Click to expand...
Click to collapse
Hmm you know what, you're right. It seems Nexus devices have adb on stock recovery- Moto's don't. Though what you found might be gold, I hope you can bust out a modified kernel- or know someone who does.
EDIT: Though I don't know how you're going to get the Update.zip on the phone to flash it. Worse comes to worse you could plug a mouse into the phone and play a guessing game of what you're clicking on

Dead LCD: How to recover data ?

Hello
My friend has Nexus 6, or should I say had. Unfortunately, he dropped his phone really hard on concrete. LCD is completely dead. He is dumb enough to never make a backup of his photos etc. Is there any way to get his data back ? Phone is pure stock.
Thanks for any help

grzechu51 said:
Hello
My friend has Nexus 6, or should I say had. Unfortunately, he dropped his phone really hard on concrete. LCD is completely dead. He is dumb enough to never make a backup of his photos etc. Is there any way to get his data back ? Phone is pure stock.
Thanks for any help
Click to expand...
Click to collapse
Does he have USB debugging enabled?

grzechu51 said:
Hello
My friend has Nexus 6, or should I say had. Unfortunately, he dropped his phone really hard on concrete. LCD is completely dead. He is dumb enough to never make a backup of his photos etc. Is there any way to get his data back ? Phone is pure stock.
Thanks for any help
Click to expand...
Click to collapse
If the phone turns on and boots just plug it in the PC and you might be able to port them to the PC.
Sent from my Nexus 6 using XDA-Developers mobile app

grzechu51 said:
Hello
My friend has Nexus 6, or should I say had. Unfortunately, he dropped his phone really hard on concrete. LCD is completely dead. He is dumb enough to never make a backup of his photos etc. Is there any way to get his data back ? Phone is pure stock.
Thanks for any help
Click to expand...
Click to collapse
Well a very annoying thing about Marshmallow is that the phone requires you to unlock it and select file share over usb mode otherwise it will only charge off a computer, if he had ADB enabled AND had it used on a computer in the past then you can do an ADB pull, but again on a new computer you'll have to confirm that you trust the computer to get adb to work. And even if he had TWRP recovery installed you'll still need to decrypt the phone using a passcode unless he used a unsecure lockscreen. Also if you have ADB access then you can use a chrome extension called "vysor" which mirrors the phone screen onto your computer to interact with it.
EDIT: just read pure stock...

Debugging is unfortunately off.

Is the actual screen destroyed, or just the digitizer?
If the actual screen is toast along with the digitizer, replacing the screen is the only means of retrieving his data. The good news in that regard is that taking apart the Nexus 6 is actually quite easy, based upon iFixit's teardown of the device.
If only the digitizer is gone, there may be some hope. Grab a USB OTG cable and a PC mouse. Connect the mouse to the OTG cable and plug the OTG cable into the MicroUSB port. Android should then generate a mouse cursor that you can use to maneuver around the device. From there you should be able to enable USB debugging if you want, or simply copy his data to Mega, Mediafire, Dropbox, or Google Drive for later retrieval.

I had the same thing happen to my N6. With nothing to lose, I banged it against my palm and saw the screen flicker. After a few more taps, I got the screen to come back long enough to back up data and get me through till a replacement arrived.