Hey guys, this is my first post on this forum. There are threads similar to this, but none that match my issues exactly, so get off me!
Anyway, I've had the Atrix HD for about a year now. About a month ago, it was lagging really badly (ended up being my own fault) so i smacked it and shattered the digitizer. I fixed it myself, obviously voiding the warranty. I did everything right, except the pre-bent cable on the new digitizer didn't quite sit right, so it may be folded in there now that it's all back together. All I know is, it has been working fine.
The other day, however, it started registering taps that weren't there, along with just plain ignoring my touch commands. It does this about 85% of the time now, so you can understand why I'm a little flustered. I'm thinking that it could be the digitizer, but I doubt it because it seems to be a software issue.
During my troubleshooting session, I came across another problem. I can't install the latest software update. Tried a soft data reset, nothing. When I went to try a hard data reset, I was unable to navigate through the fastboot menu, and it said "Device is LOCKED. Status code: 0" and below it said "connect usb data cable". I assume this is because I have the device rooted, but when I tried to flash the stock firmware back onto it, I ran into the issue of having to select a fastboot mode, which, as I said, I am unable to do. It's a real thorn in the side too, since it's already on the mode that I need. I simply can't select it.
I would really prefer not to take it to AT&T if I can avoid it, all attempts at helping will be greatly appreciated.
That screen is the fastboot screen.
What ROM was on your phone? If it was JB and you're trying to flash an ICS ROM, it will not work without an unlocked bootloader.
Since you have not warranty on your phone, I suggest you use Myth Tools to unlock the bootloader first. Then use Myth Tools to flash a stock ATT ROM.
audit13 said:
That screen is the fastboot screen.
What ROM was on your phone? If it was JB and you're trying to flash an ICS ROM, it will not work without an unlocked bootloader.
Since you have not warranty on your phone, I suggest you use Myth Tools to unlock the bootloader first. Then use Myth Tools to flash a stock ATT ROM.
Click to expand...
Click to collapse
I appreciate the advice as far as Myth Tools, but what are you talking about when you say "that screen is the fastboot screen"? I didn't ask about the fastboot screen, in fact, I mentioned it specifically several times. I know what the fastboot screen is. The problem is I cannot use it. I can get to the screen (everyone keeps saying you have to press both volume button plus the power button, but you actually only use the volume down button and the power button) but that is it. I cannot use the volume buttons to navigate, nor can I select the mode that is on the screen by default when you go to the fastboot screen. Btw, I'm not sure if it's Jelly Bean or not, but it's 4.1.1.
Okay, so you can get into fastboot, right? The fastboot screen is what you need to flash a ROM. You don't need access to the buttons to flash a ROM on the fastboot screen from what I recall. I used fast boot commands.
If you do not have an unlocked bootloader, I don't think you can downgrade the ROM.
Is this the screen you see or something like it: https://motorola-global-eng.custhelp.com/rnt/rnw/img/enduser/spdrmain22.png ?
Mr Gingernezz said:
Hey guys, this is my first post on this forum. There are threads similar to this, but none that match my issues exactly, so get off me!
Anyway, I've had the Atrix HD for about a year now. About a month ago, it was lagging really badly (ended up being my own fault) so i smacked it and shattered the digitizer. I fixed it myself, obviously voiding the warranty. I did everything right, except the pre-bent cable on the new digitizer didn't quite sit right, so it may be folded in there now that it's all back together. All I know is, it has been working fine.
The other day, however, it started registering taps that weren't there, along with just plain ignoring my touch commands. It does this about 85% of the time now, so you can understand why I'm a little flustered. I'm thinking that it could be the digitizer, but I doubt it because it seems to be a software issue.
During my troubleshooting session, I came across another problem. I can't install the latest software update. Tried a soft data reset, nothing. When I went to try a hard data reset, I was unable to navigate through the fastboot menu, and it said "Device is LOCKED. Status code: 0" and below it said "connect usb data cable". I assume this is because I have the device rooted, but when I tried to flash the stock firmware back onto it, I ran into the issue of having to select a fastboot mode, which, as I said, I am unable to do. It's a real thorn in the side too, since it's already on the mode that I need. I simply can't select it.
I would really prefer not to take it to AT&T if I can avoid it, all attempts at helping will be greatly appreciated.
Click to expand...
Click to collapse
You need to flash a the stock AT&T 4.1.1 fastboot with RSD. Open up the fastboot's xml file and remove all the lines with oem in it. Search around for "modified fastboot xml"...I've come across no less than 20 in the past few months alone. I'd be more helpful, but I'm calling it a night.
If you bought a cheap digitizer, that could be the problem. Phantom touches and being unable to access the top 10% of the screen were the biggest complaints I saw with cheapos.
skeevydude said:
You need to flash a the stock AT&T 4.1.1 fastboot with RSD. Open up the fastboot's xml file and remove all the lines with oem in it. Search around for "modified fastboot xml"...I've come across no less than 20 in the past few months alone. I'd be more helpful, but I'm calling it a night.
If you bought a cheap digitizer, that could be the problem. Phantom touches and being unable to access the top 10% of the screen were the biggest complaints I saw with cheapos.
Click to expand...
Click to collapse
Maaaaaan. If it's the digitizer, I'm gonna be pissed. Fixing it was a pain in the ass. Plus I've done all this screwing around with my firmware for nothing, if that's the case. I'll try what you suggested and get back to you. I appreciate the help.
Mr Gingernezz said:
Maaaaaan. If it's the digitizer, I'm gonna be pissed. Fixing it was a pain in the ass. Plus I've done all this screwing around with my firmware for nothing, if that's the case. I'll try what you suggested and get back to you. I appreciate the help.
Click to expand...
Click to collapse
It's only 22 pain in the ass tiny screws, blow drying off some glue, the feeling like you're gonna snap the motherboard removing the adhesive and lcd screen....why wouldn't you want to do that again?
I'm thinking that when you tweaked your ribbon cable you might have messed something up. Those cables are real sensitive to odd bends.
With my old AHD, my headphone jack quit working. I flashed multiple roms, stock firmwares, and nothing helped. Eventually I found the app SoundAbout and I was able to at least use my phone with headphones. My problem was the sensor that detects the jack being plugged in was out, and sadly, my replacement AHD has a buggy headphone jack sensor...only works half the time, so I still use SoundAbout
skeevydude said:
It's only 22 pain in the ass tiny screws, blow drying off some glue, the feeling like you're gonna snap the motherboard removing the adhesive and lcd screen....why wouldn't you want to do that again?
I'm thinking that when you tweaked your ribbon cable you might have messed something up. Those cables are real sensitive to odd bends.
With my old AHD, my headphone jack quit working. I flashed multiple roms, stock firmwares, and nothing helped. Eventually I found the app SoundAbout and I was able to at least use my phone with headphones. My problem was the sensor that detects the jack being plugged in was out, and sadly, my replacement AHD has a buggy headphone jack sensor...only works half the time, so I still use SoundAbout
Click to expand...
Click to collapse
Lol! I think it'd be easier now, though. Still not crazy about doing that nonsense again.
So, ya know how the ribbon cable is shaped to come down the center of the lcd back, and then turn over to the port? Well, when I went to plug it in, it was about half a centimeter above the port. I kinda just made it work, and it bent weird at the elbow.
..............................l l l l l
..............................l l l l l
..............................l l l l l
..............................l l l l l <---Cable
..............................l l l l l
..............................l l l l l
..............................l l l l l
..............................l l l l l
..............................l l l l l
..............................l l l l l
............................./ / / / /
____________ _ _ / / / / /
_ -- _--_-_-_---_--_-_/ / / / <------Where it went weird on me
---l _--_--_--_--_-_--/ / /
l
l <--- Port
---l
Pardon the poor representation
Hey, I apologize for the poor response time. I have been letting a friend use my laptop, so my internet access is limited.
As I don't have my own laptop at the moment, I can't make any software modifications. I have instead been using this time to try to notice patterns in the phone's faults. I have noticed that, when in the upright position, the area of the screen where the letter "d" is on my keyboard is a trouble area. The d button works 1 out of 10 times. I opened one of those simple touch tester apps (just shows visual feedback of the touches) and realized that it wasn't registering touches in that same area. I'm now almost certain that it is the digitizer. Think I should just get one comin in the mail A.S.A.P.?
Related
PLZ help im freaking out. i accidentally booted into the blue light mode, but when i pulled the battery and rebooted the backlight wouldnt work. i could see everything and even navigate my phone but only under a light. the backlight just wont turn on during boot and changing the setting doesnt help.
i dont get it the thing was working 10 minutes ago and now i cant use it what should i do? i love this phone but i cant afford a new one. is there a way to tell it to turn on during boot in the console?
ok new update the backlight works if i have the keyboard open. i know 100% its software and not the screen. something when wrong with the boot prosses or something.
i think the trackball boot (bluelight boot) must have options but wont display on the screen maybe. like a bios menu. this is very infuriating
Why don't you restore a recent backup?
i have even went as far as downgrading with the .nbh file. and re installing the bootloader (Just the original, didnt want a brick).
Definitely NOT a software problem.
This is a HARDWARE problem -- hence the fact that it works when the keyboard is open.
When you pulled the battery, you might have twisted/pulled something.
*** I would check the ribbon cable connecting the display to the main body!!!
Bluelight mode (where you end up by booting with the trackball pushed in), is just a serial console allowing interfacing with the radio firmware. Unless you actually had a serial cable connected and punched in some commands (which happen to be security locked, therefore wouldn't work for you anyways), bluelight mode wouldn't be able to do this.
lbcoder said:
Definitely NOT a software problem.
This is a HARDWARE problem -- hence the fact that it works when the keyboard is open.
When you pulled the battery, you might have twisted/pulled something.
*** I would check the ribbon cable connecting the display to the main body!!!
Bluelight mode (where you end up by booting with the trackball pushed in), is just a serial console allowing interfacing with the radio firmware. Unless you actually had a serial cable connected and punched in some commands (which happen to be security locked, therefore wouldn't work for you anyways), bluelight mode wouldn't be able to do this.
Click to expand...
Click to collapse
if that were the case than wouldnt it flicker if i flex the screen/hinge ? ill try anything at this point cuz im outa warranty and have no money . im going to the store later trying to update to official 1.6 so i can convince them its software related and they may replace it for me.
oh forgot to mention that if i close it and open it the light stays off untill i hit end and unlock with menu again. im not to sure if that helps.
OK OK OK you are right. i just half closed it and the light stayed on untill it compleatly closed (so the screen flipped, i thought that is what triggered it) and then i got it to stay on completely closed and then the problem flipped to it wouldnt come on while open and now back to the way it was. so im going to go buy a T5 screw driver today and clean the contacts of the ribon cable and reinsert it (i have had experience with that just need to know what ribon. a pic would be nice)
projectzro said:
OK OK OK you are right. i just half closed it and the light stayed on untill it compleatly closed (so the screen flipped, i thought that is what triggered it) and then i got it to stay on completely closed and then the problem flipped to it wouldnt come on while open and now back to the way it was. so im going to go buy a T5 screw driver today and clean the contacts of the ribon cable and reinsert it (i have had experience with that just need to know what ribon. a pic would be nice)
Click to expand...
Click to collapse
There is only one ribbon running to the screen. Try THAT one.
lbcoder said:
There is only one ribbon running to the screen. Try THAT one.
Click to expand...
Click to collapse
LOL lbcoder - always practical.
lbcoder said:
There is only one ribbon running to the screen. Try THAT one.
Click to expand...
Click to collapse
lol ok didn't know that a lot of the devices I have taken apart have had 2 one for the desplay and one for the backlight. Getting a T5 screw driver in half an hour. Will post results later. Hopefully this works, therr area few more ppl with the same problem.
projectzro said:
lol ok didn't know that a lot of the devices I have taken apart have had 2 one for the desplay and one for the backlight. Getting a T5 screw driver in half an hour. Will post results later. Hopefully this works, therr area few more ppl with the same problem.
Click to expand...
Click to collapse
There are two wires going to the screen.. sounds like the "top" one is loose... The jtag photos will give you an idea (it's the two com ports next to the jtag test points)
These are usually taped down very well..
Also you need both a T5 and T6.. the "Security" (has black void sticker) screw is larger than the others.. and a small flat head screwdriver to unclip the cover..
If all else fails: replacement screens seem much cheaper than the phone on ebay.
ezterry said:
There are two wires going to the screen.. sounds like the "top" one is loose... The jtag photos will give you an idea (it's the two com ports next to the jtag test points)
These are usually taped down very well..
Also you need both a T5 and T6.. the "Security" (has black void sticker) screw is larger than the others.. and a small flat head screwdriver to unclip the cover..
If all else fails: replacement screens seem much cheaper than the phone on ebay.
Click to expand...
Click to collapse
ok got it apart 3 times and no luck its prolly the ribbon cable. im going to test that soon. i have a donor phone comming soon from a friend who dropped it in water, the ribbon cable should be fine to use. if that doesnt work im thinking maybe it is software. either way if i cant get it fixed by next month im spending $410 on a new mytouch 3G brand new from the store and getting insurance XP
So its been about a year and half since I received this phone for my birthday, and from this moment on, I am 90% sure that these companies design these phones to fall apart after a while so you buy a new one.
Please to not be intimidated by the length of the problems, I really doent want to waste a $600 nice phone. Please help.....
List of problems:
So on one random day, while I was using my phone with EnergyROM sense 6.1 (Not even 6.5 (Windows 6.5.5)) the phone stopped rotating when I flipped the keyboard, as in the screen will not rotate when I try to use the keyboard. The touch screen also becomes uncalibrated, and even when I recalibrate it, it still acts very funky (have to click lower than button or higher, depending on its mood). I did absolutely nothing different with my phone that day, but I did not call my phone dead right away, so I decided to update the ROM with the latest sense 6.5 ROM to see if the OS is corrupt or over-cached. This did not fix the problem.
Also, another very weird thing is the phone's screen will illuminate (I guess backlight), but no picture will show when turned on after sleep mode, and I have to click the top button again to sleep and awake it to get a picture. When flipped, the screen doesn't even fully illuminate, and literally dies down to a black screen (half of the pixels are bright, and then it just fails).
Any help would be very appreciated. What I am thinking of is wiping the phone 100%, and not even leaving a rom on it. I heard there is a command that deletes the junk off your phone from a previous ROM to your updated ROM is clutter free. Any other suggestions?
Edit: I hard reset my phone, and nothing is fixed; I still cannot flip screen into landscape mode.
The "command" you are talking about is called "task 29", look for it in the ROM section.
It sounds like hardware problems, i've had mine for about 1 year and a half as well and no problems besides a couple of scratches.
The flex cable connecting LCD and board might be out of order.... I had the same issue.
palmwangja said:
The flex cable connecting LCD and board might be out of order.... I had the same issue.
Click to expand...
Click to collapse
Yeah I heard about that problem. I will first task 29 it, but are there any guides to take apart and fix the flex cable, or even just unplugging it and plugging it back in?
Also, what did you do with your broken phone? Did you buy a new one or get it fixed?
Thanks for the feed back both of you.
my X1 also aged same as yours and it still runs flawlessly now. so it might depends on how you used and keep it
as for the "wiping off the phone" its called task 29, and is encouraged to do before you flash a new ROM, have you did it before flashing energyROM?
rhadrio said:
my X1 also aged same as yours and it still runs flawlessly now. so it might depends on how you used and keep it
as for the "wiping off the phone" its called task 29, and is encouraged to do before you flash a new ROM, have you did it before flashing energyROM?
Click to expand...
Click to collapse
No, but I just did now, but it seems to be a hardware problem because nothing seems to be working properly still. This is some serious BS because I am very over protected with this phone, just to prevent stuff like this to happen. I have never dropped it ONCE, and it seemed to just wear out by itself. The lenses covering the camera is cracked also, and the screen is all screwed up, and I didnt do absolutely nothing abusive to it, I am 110% sure of this.
Any suggestions on how to fix hardware/ ribbon connected to the screen problem?
Order a new cable and replace it.
If you search on Youtube for the video on how to disassemble x1 there is a complete guide that shows you. Its pretty easy and all you need to do is, take the flex cable out and carefully plug it back in. Then carefully put your X1 back together and hopefully you issue will be fixed. If it still persist, then try and get the flex cable changed.
So my phone was fine about 2 hours ago, then I took a call an hour ago and since the call ended my touchscreen has been going crazy. It's rapidly clicking the top and the side of the screen. I now have a completely new lockscreen with new widgets and a brand new layout with tons of app shortcuts haha. It even managed to change things I didn't know how to change!
My phone is completely unusable. The clicks happen so fast that if I do manage to unlock it, every app I own starts opening.
Anyhow, I looked around and all I found was a grounding related screen issue on other phones like the nexus4 and lg g2. Since the XZ is sealed thats not really an easy test!
Can I get some suggestions?
Tried so far:
Cleaned screen
Power Cycle
Factory reset
Flashed stock FTF
I'm assuming my next step would be to try replacing parts, but I have no clue which parts I'm looking at. I have a c6602 model XZ
Worst part, I have a phone interview first thing in the morning and this is my only phone
TL;DR
Screen spamming pressing @ top center and mid left, factory reset had no effect.
PS: Phone is not mistreated and hasn't been dropped.
next step is to flash a tft file,if that didnt work i guess your screen is screwed,btw my friend has a x2 and its kinda a problem with that phone
demon2112 said:
next step is to flash a tft file,if that didnt work i guess your screen is screwed,btw my friend has a x2 and its kinda a problem with that phone
Click to expand...
Click to collapse
I reflashed the rom via sony's updater. It's still broken. I couldn't get adb connections to work because they required verifying the connection. I'm assuming the sony tools ignore this step.
http://www.amazon.com/Sony-Xperia-L...HGU8/ref=sr_1_1?ie=UTF8&qid=1416822526&sr=8-1
I think this is the piece to replace, can anyone confirm?
edit:
looked at the replacement process, looks like a full lcd+digitizer is a better idea as the screen is gonna break if I separate them. always something. anyone know a good quality replacement?
touchscreen no longer responds at all, spamming touches have stopped.
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
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.