Hello everyone!
I may be in deep trouble. Over the past few months, my phone has been in (self-hands) service.
I have bought a Sony Xperia Z1 C6903 used with a faulty battery and faulty audio jack port.
I have ordered a new battery and new audio jack port for my phone from eBay. I feel it is worth noting that all my orders below are from eBay. Roughly 2 weeks after I have ordered the presumed "original" parts for my phone, some one in my family has 'unknowingly' stepped on to the charge cable while the phone was charging thus resulting the phone's screen to be cracked half-way.
After that rather pleasant aftermath, I placed an order for a new 'OEM' screen digitizer along with new adhesive tapes for the phone.
After receiving my items, I proceeded to apply and replace. During the old screen tear down, I have managed to tear the loudspeaker flex ribbon. After that stressful moment, I ordered an 'original' Power On/Off-Volume-Camera flex ribbon. After that, I have replaced the ribbon and applied the adhesive tapes on the phone panels.
Before the whole part replacing, my phone was running on the DstrikerZ1Kai ROM (Version SP002X) because I was unable to unlock its boot-loader. it also had the dual recovery system installed on it.
After all that nightmare, I wanted to revert the phone back to stock ROM because of the following issues:
1. The phone stopped recognizing my USB sticks. Tried all the USB-Stock mount-etc apps on play and the net. Could not get it running.
2. It was starting to get hard to charge the phone. Now I have read about these types of problems. It is said that it is related to the ROM. May be also related to the USB problems I had.
3. I wanted to flash the Kryptonian v5 Final ROM.
Now comes my current big problem.
I was using the Xperia Companion tool to revert back to stock. Everything went fine up to the point where it told me to put the phone to flash mode.
I proceeded to try to put the phone into flash mode, however, as I immediately realized, the Volume Down button did not work at all. I then quickly thought it was a software issue and not a hardware problem. I put the phone to TWRP recovery using the inbuilt dual recovery app (forgot it's precise name), and put the DstrikerZ1Kai ROM to stock, as if I have just flashed it. Of course, I have made a backup before that in case something went awry. But during the re-flash, I have received an error. I don't remember what the error was unfortunately. After that, I accidentally rebooted the phone and now all I receive is the Sony Logo.
I wanted to use the Flash Tool to re-flash an FTP, however, I can not enter Flash Mode since my Volume Down isn't working. I can enter Fast-boot Mode, but then that is it. If I use the Fastboot menu options in Flash Tool, I can get some device info, but then, that is it. I can't use the ADB option, because it says "Device must be in ADB Mode". If I put the phone on charger, I get a red light at the top.
During the phone repair, I have reinstalled my PC to Win 7 Ultimate 64-bit. I don't know if I have the correct drivers installed, to be honest.
Please help me everyone. I am totally stuck here and don't know how to proceed forward. Should I take the phone apart again and try to press the Volume Down manually and not with the buttons itself? Should I buy a new Flex ribbon.
Dujo13309 said:
Hello everyone!
I may be in deep trouble. Over the past few months, my phone has been in (self-hands) service.
I have bought a Sony Xperia Z1 C6903 used with a faulty battery and faulty audio jack port.
I have ordered a new battery and new audio jack port for my phone from eBay. I feel it is worth noting that all my orders below are from eBay. Roughly 2 weeks after I have ordered the presumed "original" parts for my phone, some one in my family has 'unknowingly' stepped on to the charge cable while the phone was charging thus resulting the phone's screen to be cracked half-way.
After that rather pleasant aftermath, I placed an order for a new 'OEM' screen digitizer along with new adhesive tapes for the phone.
After receiving my items, I proceeded to apply and replace. During the old screen tear down, I have managed to tear the loudspeaker flex ribbon. After that stressful moment, I ordered an 'original' Power On/Off-Volume-Camera flex ribbon. After that, I have replaced the ribbon and applied the adhesive tapes on the phone panels.
Before the whole part replacing, my phone was running on the DstrikerZ1Kai ROM (Version SP002X) because I was unable to unlock its boot-loader. it also had the dual recovery system installed on it.
After all that nightmare, I wanted to revert the phone back to stock ROM because of the following issues:
1. The phone stopped recognizing my USB sticks. Tried all the USB-Stock mount-etc apps on play and the net. Could not get it running.
2. It was starting to get hard to charge the phone. Now I have read about these types of problems. It is said that it is related to the ROM. May be also related to the USB problems I had.
3. I wanted to flash the Kryptonian v5 Final ROM.
Now comes my current big problem.
I was using the Xperia Companion tool to revert back to stock. Everything went fine up to the point where it told me to put the phone to flash mode.
I proceeded to try to put the phone into flash mode, however, as I immediately realized, the Volume Down button did not work at all. I then quickly thought it was a software issue and not a hardware problem. I put the phone to TWRP recovery using the inbuilt dual recovery app (forgot it's precise name), and put the DstrikerZ1Kai ROM to stock, as if I have just flashed it. Of course, I have made a backup before that in case something went awry. But during the re-flash, I have received an error. I don't remember what the error was unfortunately. After that, I accidentally rebooted the phone and now all I receive is the Sony Logo.
I wanted to use the Flash Tool to re-flash an FTP, however, I can not enter Flash Mode since my Volume Down isn't working. I can enter Fast-boot Mode, but then that is it. If I use the Fastboot menu options in Flash Tool, I can get some device info, but then, that is it. I can't use the ADB option, because it says "Device must be in ADB Mode". If I put the phone on charger, I get a red light at the top.
During the phone repair, I have reinstalled my PC to Win 7 Ultimate 64-bit. I don't know if I have the correct drivers installed, to be honest.
Please help me everyone. I am totally stuck here and don't know how to proceed forward. Should I take the phone apart again and try to press the Volume Down manually and not with the buttons itself? Should I buy a new Flex ribbon.
Click to expand...
Click to collapse
You might want to buy another phone. Most after-market flex ribbons are defective: the phone either won't boot or screen wouldn't work, or various buttons wouldn't work.
You can try to buy a defective phone very cheap: it could even be sim locked, as all you need is the middle frame with all ribbons intact. Then you can transfer your current motherboard and all other electronic parts to the new frame. Keep in mind that there is a risk you can damage your screen while doing that... . Those are your options.
Related
Tried connecting my kaiser to 2 different pc's and it won't get detected. The device will charge but activesync won't pick it up. Also its not listed in device manager! I tried disabling/renabling advanced network functionality as well has soft reset the device several times. I'm on the verge of hard reseting BUT when i put my device in bootloader mode it only says serial.. will not say USB as its supposed to
any help would be appreciated.. i'm on death v4 rom btw.
thanks in advance!
fone_fanatic said:
The device will charge but activesync won't pick it up.
Click to expand...
Click to collapse
Can you get an activesync connection via Bluetooth? When you inspect the extUSB connection can you see anything which looks wrong (such as a wire sticking out/in more than the others? What happened preceding this problem?
If you hard reset the device I don't see the relevance of the bootloader. It'll just restore the original image from where it's tucked away in the devices ROM. If it was working fine straight after you installed the ROM thats on it now and doesn't work after a hard restore then that points towards a hardware failure. If you have to go down the path of restoring to a different (original) ROM for returning purposes, there are ways of doing this with a microSD card - although I've not tried. I think the wiki would help there.
bluetooth activesync is working, i did a hard reset and nothing. Flashed to romeos via microsd and now its acting all strange.
After it completed the flash from microsd, i soft reset the device and it rebooted backinto bootloader.. i removed the microsd and soft reset several times and it kept going to bootloader. I attempted to hard reset as well and same thing, would go to bootloader. Removed the battery for a couple minutes and still same thing. Plugged it into USB with it off and it turn on by itself and go straight to bootloader. Unplugged the USB cable, took out the battery and put it back in, then plug the USB cable back in and this time the orange light came on as if charging and it finally booted up. The above has happened to me previously on my hermes but that was when the battery was extremely low, my battery level is currently at 97%!
now its booted into the freshly flashed rom and still same thing... charging but not being recognized by the PC... i've checked the usb port on the device and everything looks fine.
I'm lost at what to do now....
This might be a stupid reply but I had the same problem. My cable was busted so you could try another cable.
I am in the same situation here
Tried it with 3 different PCs with 3 different cables.
It's charging, Active sync pickes it up and trying to connect but fails to connect.
The only think I can come up with, I used new charger in the car. May be it killed the port
Is there any way to find out for sure?
i tried 2 cables with 2 different pcs... its only charging it and the computer won't detect the device at all. Nothing under usb in device manager.. even in bootloader, it only says serial not usb. I've downgraded to a shipped AT&T rom and Radio through the storage card but i still need to downgrade the SPL before i attempt to get a warranty exchange. IS that possible to do with through microsd yet?
I'm having the same issue. The usb port charges the phone fine with the USB cable, but teh computer does not detect the device. I also tried the headphones and they work fine as well. Help!
Update: I just tried a different usb cable, and now the computer recognizes the device, but as an unknown device.!!!!!
fone_fanatic said:
bluetooth activesync is working, i did a hard reset and nothing. Flashed to romeos via microsd and now its acting all strange.
After it completed the flash from microsd, i soft reset the device and it rebooted backinto bootloader.. i removed the microsd and soft reset several times and it kept going to bootloader. I attempted to hard reset as well and same thing, would go to bootloader. Removed the battery for a couple minutes and still same thing. Plugged it into USB with it off and it turn on by itself and go straight to bootloader. Unplugged the USB cable, took out the battery and put it back in, then plug the USB cable back in and this time the orange light came on as if charging and it finally booted up. The above has happened to me previously on my hermes but that was when the battery was extremely low, my battery level is currently at 97%!
now its booted into the freshly flashed rom and still same thing... charging but not being recognized by the PC... i've checked the usb port on the device and everything looks fine.
I'm lost at what to do now....
Click to expand...
Click to collapse
Have you tried these steps?
http://www.microsoft.com/windowsmobile/en-us/help/synchronize/activesync-usb.mspx
ajay6780 said:
Have you tried these steps?
http://www.microsoft.com/windowsmobile/en-us/help/synchronize/activesync-usb.mspx
Click to expand...
Click to collapse
Thanks for that suggestion but still no dice
The computer isn't detecting the device at all! Usually when a usb device is plugged in you can go to device manager and look under USB and see it there, but its not showing up. I've scanned for hardware changes several times and nothing.
I've now tried on 3 different computers (2 pc's and 1 mac) with 2 different USB-MiniUSB cables and nothing!!
i guess i'll just go to the at&t device support center tomorrow and hope they'll replace it on the spot and notice that i've changed the SPL...
can i ask for the people that are having this problem to do the following.
With your device unplugged from the PC open device manager. (Right click My Computer -> Properties -> Hardware (3rd tab) -> Device manager) Then expand the last tab (Universal Serial Bus Controller) and plug in your device.. if it doesn't show up then click actions -> scan for hardware changes..
I just want to make sure if your computer is detecting your device or not..
just an update with my situation. i went into the att device service center today and told them my problem... the guy behind the counter had no clue what he was doing. he just looked at it like a monkey for minutes then swapped it out for a new one. no questions asked even though it was hard spl'd, cid unlocked, and sim unlocked.
but now this device's vibration is really weak and i lost my invsishield protection on the front (kept the battery cover and my ppctechs scren protector)
Busted? or just won't work
Hi all,
I have been coming to these forums for a little while and only posted a couple of times. I felt this was important. I was having the same problem. Tried the cables, resets, ROM changes the works. I have had my at&t tilt htc 8925 for 36 days when I reported the problem to them. But it actually started about 10 days before. At&t tech support was very rude and accusatory when it came to them "helping" me. I, like probably all owners of a phone like this treat it like gold. It is very important to me. So when I contacted tech support and was told it was probably abuse or I had "buyers remorse" (I don't want to return the phone I just want it fixed!?)
The best they can do and they do not budge on this is for me to return the phone for an exchange. BUT, and this is a BIG AT&T but, the phone they exchange it with is refurbished. Something someone has returned. I do not want a phone that has been returned. I want mine fixed. "This is my phone, there are many like it but this one is mine" Know what I mean? When I bought the phone the guarantee was "we'll just replace it with a new phone" and I like 1000's of others did not ask if that "new phone" was refurbished. It is. Now advocates will tell you as they did me, refurbished is actually BETTER than new. Huh? Then why aren't all phones sold refurbished ones? And if they are so great, take mine back, give me one of those "crappy" new phones and give mine to someone who wants a sweet refurb. I am outraged by the whole mess.
I have searched forums and complaint sites. The bad usb port problem is NOT an isolated incident. There are a lot of people with the same "it charges but won't sync" problem. This is a known problem they refuse to address. Their stand, send in for refurb.
Personally I would like to see a recall fix class action against at&t. It can be fixed but they just don't want too. I thought I would be relatively safe buying for a huge company. They spend millions on advertising to simply leave their customers twisting in the wind after 30 days. Very bad business.
That's the rant. So I decided that if the warranty was useless anyway I'd take a shot at it myself before sending out for repair myself. There is a place in California PPC Tech http://www.pocketpctechs.com/main.asp?area=home that will fix the usb for $79 and ship it back to you in a few days. They seem to be reputable and a lot of people are opting to fix this problem themselves.
How did I fix mine? by altering the mini usb end of the sync cable. I tried other cables and connectors but I think it has something to do with the contact points. The only way mine would work was if I plugged it in, wiggled it slowly and with a little bit of pressure at times, around until the screen brightens. That means it has made a connection, then don't move. Hold very still. It took both my hands. Wait for what seems like 2 mins and it would start to sync. Based on this. my repair (before I send it to California for repair, which I may end up doing anyway) is make sure the plug on the phone is straight and not damaged. If you can get the phone to sync this way you may be able to crimp the mini end of the usb very very slightly to make the connection you are manually doing by wiggling it around. It took a lot of small tweaking but it now syncs about 29 out of 30 times. That's about as good as it gets.
So good luck to us all. If you can't get it to work yourself send it out west to PPC Tech. In this economy the phone companies like at&t better start getting their customer service back on track before they have no customers to service, It has happened to the biggest before. Wake up AT&T! The days of the business model of massive turnover and new signups is coming to an end as people tighten their belts. Treating current and future users poorly is a sure fire way to put yourself out of business.
here is my gift to you all..
http://forum.xda-developers.com/showthread.php?t=362679
read this post and check EVERY SINGLE LINK in the first post...i had this issue and i ended bending my usb plug every which way until finally i broke the plastic seperator off and in turn smashing the second pin from the left on the top off (the one in charge of activesync) over and over until it broke...i didnt really care i could still flash by sd but then i smashed the + power pin and so i was on the phone with att for many many hours explaining to them that its a known issue to users but not to the company and they finally sent me a replacement..i should have just searched my butt off before trying to deal with a problem/fox it myself (yes i dissasembled it and soldered the pin back on and it broke off multiple times causing me to dissasemble it many many times and smashing it again and i ended up getting alcohol on the water damage void pad which i replaced) learn from me...if you ever have ANY problems that are significant..dont try fixing JUST GET A REPLACEMENT...who cares if its a refurb..if the refurb sucks then send it back until they send you a new kit...after 5 returns you get a new kit soo just keep sendin back them refurbs until your happy
oh and to make it easy on yourself because if you tell att you have a usb problem its NOT covered under warranty and will take you many many hours like me to convince them otherwise (which someone eventually will understand because certain people ARE familiar with this problem at ATT it just depends who you get and how many times youve been elevated in support)..what you need to do is IF YOU CAN return your spl back to stock (if you manage to get a long enough connection with activesync) but if not dont worry too much att doesnt really check spl just that you have the shipped rom on there so load the shipped rom (found on here) on your sd and flash back and just make up some excuse that it isnt working right and youl get a replacement or if you can get the spl revrted jus throw your device in bootloader by a failed flash (pull the usb out during flash) and say its stuck in the funny colored screen lol
jaysjob, i've been dealing with ppctechs for a long time (probably since '03-'04) they're very reputable and highly recommended. They actually got the contract to be the authorized repair center for I-Mate about a year ago.
But why would you pay $79 for something where u can get a complete replacement? Yah it might be a refurb but my device that i turned in was all scratched up from drops.. the images on the start, ie, and messaging buttons by the d-pad had scratched off.. and now the device i got looks brand new (i actually think it is a new one but i never asked if it was a refurb or not)
pazookie, what your saying is true.. always take advantage of the warranty if you have it. If you dont and you want to repair it yourself, know what your doing! I'm very handy and have done many lcd replacements and other various repairs on cellphones (nokias, HTCs, sony ericsson, samsung, motorola, u name it!)
My little brother has the n82 and he bought the black case, I told him to wait for me and i'd help him do it but he got impatient and he thought it was gonna be a simple swap. He ended up breaking his LCD doing it which set him back $80!
anyways i'm happy now with a new device but i'm gonna go back tomorrow and get it replaced again because the vibrate is extremely weak!
fone_fanatic said:
jaysjob, i've been dealing with ppctechs for a long time (probably since '03-'04) they're very reputable and highly recommended. They actually got the contract to be the authorized repair center for I-Mate about a year ago.
But why would you pay $79 for something where u can get a complete replacement? Yah it might be a refurb but my device that i turned in was all scratched up from drops.. the images on the start, ie, and messaging buttons by the d-pad had scratched off.. and now the device i got looks brand new (i actually think it is a new one but i never asked if it was a refurb or not)
pazookie, what your saying is true.. always take advantage of the warranty if you have it. If you dont and you want to repair it yourself, know what your doing! I'm very handy and have done many lcd replacements and other various repairs on cellphones (Niki's, HTCs, sony ericsson, samsung, motorola, u name it!)
My little brother has the n82 and he bought the black case, I told him to wait for me and i'd help him do it but he got impatient and he thought it was gonna be a simple swap. He ended up breaking his LCD doing it which set him back $80!
anyways i'm happy now with a new device but i'm gonna go back tomorrow and get it replaced again because the vibrate is extremely weak!
Click to expand...
Click to collapse
Hi fone
Thanks for the reply.
Yes, I agree with you. If the phone has something else that is messed up like you were saying a scratched screen or buttons. It's just that I am as careful as I can be to keep the phone in nice condition just to send it back for maybe one that someone didn't take the same care of.
Mine works good now. I think it has something to do with when I crimped the cable end. It make a tighter fit. I think that may be the key to mine and others problems. For sure it is becoming more and more clear that there is a design flaw whether att wants to acknowledge it or not.
Thanks for your input about PPC too. If I do end up having to fix it that's probably the way I'll go if that is still the only thing wrong. Otherwise it's in for the warranty as you suggested. I KNOW I'm not that smart.
Im having this same issue and it is definately not a cable problem.
tayloryork said:
Im having this same issue and it is definately not a cable problem.
Click to expand...
Click to collapse
if u think its a hardware problem then take it to a service center. The guys there just follow step by step guides on how to diagnose phone issues. For me he saw a crack in the usb jack on my device and just replaced it. If you send it in to HTC i think theres a higher risk of them figuring outu the device is hard spl'd and wont honor your warranty.
tayloryork said:
Im having this same issue and it is definately not a cable problem.
Click to expand...
Click to collapse
taylor, I'm not saying it is a cable problem. I am saying it is a hardware port problem. I "fixed" mine, probably temporarily, by crimping my usb cord so that it holds more firmly in the port. I did say if you have the same problem and you use the same test I did ie: move it slightly, Gently, not like others I have heard stories of where they ram it from side to side until it snaps off, that you might be able to do what I did. I thought others with the same problem might be able to use this workaround until at&t figures out it is not an isolated incident with thousands of people having the same problem thats all. Hope this helps.
jj
I had a similar problem. Phone would charge fine, but windows didnt even recognise anything was plugged in. Interestingly the bootloader changed to USB when the cable was connected, and Serial when unplugged.
As it turns out (thanks Flying Kiwi for suggesting the obvious I had overlooked) the middle top pin was recessed too much into the plastic guide, so I stabbed it a bit with a scapel and all is well.
So it seems that the Serial/USB section of the bootloader cant even be trusted.
Hi all,
having only had my phone for around 2 weeks tonight the inner screen of my phone has decided to crack whilst sat on the side doing nothing (Yes, I know, likely story but in my case it is true). Luckily Orange have been very good and are sending out a replacement handset tomorrow as it is still under warranty.
All good I thought, but I am now worried that I have to also send the handset back. It is currently running Darkys firmware and wondered if this is likely to be an issue. Also, the phone is configured for my work email and would like to remove this info before hand.
Any suggestions on how I quicky (and without a screen) return a phone to stock would be very much appreciated!
Cheers,
Michael
It is currently running Darkys firmware and wondered if this is likely to be an issue
YES its broken the warranty depends upon how close they inspect the phone etc .
Post on a similar topic within the last two months re no screen
Normal method of returning to stock is .
http://forum.xda-developers.com/showthread.php?t=818556
jje
Pull the Battery and reinsert it.
Get into the Download Mode.
Flash it with a Custom Kernel.
Unplug the USB during the Flashing Procedure
You will end up with a bricked phone which will force Orange to reinstall the firmware.
And as JJEgan said, it all depends upon how they inspect the phone. If they agree for a replacement, then its well and good. Orelse, you can try my method
by your post I gather you don't see anything on the screen. If this is true, why worry. Orange techs will not be able to see what firmware you are running if the screen does not work.
They are not going to install a new screen to see what stuff you have on your phone.
I bought my phone off of the online classifieds, so I thought there was no warranty.
I was having a problem with the USB port not working properly as I got some mushroom soup (Don't ask) in the port. I figured since I do not have any warranty I will take the phone apart and see what I can do. I cut the top of the metal shield off with a Dremel tool and cleaned the USB port out really well. It did work after this, but about two weeks later my internal SC card died.
I brought the phone into Samsung service center and to my disbelief, they replaced the phone, no questions asked. I guess they didn't even open the phone.
I wouldn't worry.
Ian
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
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
Model Name: ROG 3 trncent edition( ZS661KS)
Firmware Version:WW-17.0823.2012.131
Rooted or not: yes ( was trying to root)
Frequency of Occurrence: Got<HARDBRICKED>
APP Name & APP Version (If your issue relates to the app): no app used.(magisk or anything else)
In addition to information above, please also provide as much details as you can, e.g., using scenario, what troubleshooting you've already done, screenshot, etc.
========================================
My rog phone 3 (tencent), which i brought about 6 months ago. I never had any issues like this.
The other day i opened my camera and suddenly the front camera was not working. I restarted the phone, did factory reset, cleared camera data, but nothing solved the issue. I thought i have to upgrade the firmware. So i downloaded the new firmware (2012.143) and connected the usb c cable with my laptop ( lenovo ideapad 320) , but it did not recognize. i tried both ports. I never had this problem before. I unlocked the bootloader, i thought it might help. I also turned on the developer option and selected FTP protocol and USB debugging. But it still didn't connect. while i was trying to enter bootloader recovery mode I accidently put the phone on EDL mode and now its bricked . The indicator light is flashing when i connect to the pc but the PC isn't recognizing the port ( i downloaded the qualcomm EDL driver on my laptop also, but the port option is not showing at all). Is it hardware problem, But the phone was charging just fine.
please suggest some help
Sounds like a hardware malfunction or damage to something on the board (burnt out microchip or resistor something along those lines) something a cell phone or repair shop could have fixed but.. it sounds like you bricked it in combination with the other issue which your best bet now is a new rog phone and sell your current one for parts or repair.. just because the cost to repair it would probably be more than what it is worth as it would require professional repair.
darkensx said:
Sounds like a hardware malfunction or damage to something on the board (burnt out microchip or resistor something along those lines) something a cell phone or repair shop could have fixed but.. it sounds like you bricked it in combination with the other issue which your best bet now is a new rog phone and sell your current one for parts or repair.. just because the cost to repair it would probably be more than what it is worth as it would require professional repair.
Click to expand...
Click to collapse
Bro my phone turned on, and it functioned normally, i didn't brick it, it was probably battery dead, i charged it for hours and it turned on.. But how do you fix a power IC that supply power from the battery . Is it the one in the (picture) , Because sometimes when it charge it gives only the green light and black screen.
Iam having an issue on debug. My bottom side is ok on getting debugged.. but my side port tends only to go in charging state.. mine not rooted or anything. Im just trying to downgrade firmware. any advise?
Firdhaus81 said:
Iam having an issue on debug. My bottom side is ok on getting debugged.. but my side port tends only to go in charging state.. mine not rooted or anything. Im just trying to downgrade firmware. any advise?
Click to expand...
Click to collapse
Try different cable. Been there seen it before