Related
Guys I REALLY NEED your HELP.
Here's What I did..
1. Installed CWM on my NOKIA X
2.Got into Recovery mode(It's Cool actually)
3.Thought of installing minirom kitkat on it..(I had already copied it to my removable sd card.)
4.Went through all the menus,,, did nothing,,, and somewhere I saw advanced,, got into it (I didn't know what I was thinking) I cleared every option that it had including cache, memory,sd card, emmc and also some boot related stuff..
5.All of a sudden I couldn't move the options so I just removed the battery and tried to power it on....(**** Happens)-Phone is not powering on.... no boot no light just A DEAD PHONE.
plz gus I Really NEED HELP. How Can I Solve this Problem.........................................................................................Plz plz plz plz.......:crying::crying::crying::crying::crying::crying::crying::crying::crying::crying::crying:
I think this is hard brick.(very hard to fix) are you able to open factory mod now? if no then wait for developers to help you to fix hard brick. or if your device showing on pc then you can flash stock rom...
•axe• said:
I think this is hard brick.(very hard to fix) are you able to open factory mod now? if no then wait for developers to help you to fix hard brick. or if your device showing on pc then you can flash stock rom...
Click to expand...
Click to collapse
no my phone's not powering up and i'm not able to open factory mode....... Plz help
Aztile said:
no my phone's not powering up and i'm not able to open factory mode....... Plz help
Click to expand...
Click to collapse
download and open ADB driver installer
is your device showing here? or download and open adb shell and type adb devices
is your device listed here?
if yes then download stock rom for nokia x
and flash is with any flash tool (like odin)
(make sure you have installed your phone to the same pc before means you have drivers)
if your device not showing then contact nokia care (dont tell them your story otherwise your warrenty will over tell them only that your mobile is not turning on )
•axe• said:
download and open ADB driver installer
is your device showing here? or download and open adb shell and type adb devices
is your device listed here?
if yes then download stock rom for nokia x
and flash is with any flash tool (like odin)
(make sure you have installed your phone to the same pc before means you have drivers)
if your device not showing then contact nokia care (dont tell them your story otherwise your warrenty will over tell them only that your mobile is not turning on )
Click to expand...
Click to collapse
Sorry buddy...... Tried it... but no use
All we can do is to refer you to a service center. Sorry.
Moderators, please verify my account. I am sick of the five-minute post wait.
Sent from my XT1022 using the XDA Premium 4 app.
Try this..power the phone off, wait 5 mins, then press and hold power for 60 seconds, and check if you see any signs of the phone coming back to life. If not, then the next option is the service center
that too is not working.................Is there no one inthis whole XDA Universe who can help me..... come on guys there must be someone................:crying::crying::crying:
tech_master said:
Moderators, please verify my account. I am sick of the five-minute post wait.
Click to expand...
Click to collapse
The five-minute post limit is lifted once you have reached 10 posts. The moderators have nothing to do with it, as the process is automated to lift the wait after you post 10 times.
The reason for this wait is to keep new users from rapidly posting uselessly just to achieve 10 posts.
Dude This is crazy
thenookieforlife3 said:
The five-minute post limit is lifted once you have reached 10 posts. The moderators have nothing to do with it, as the process is automated to lift the wait after you post 10 times.
The reason for this wait is to keep new users from rapidly posting uselessly just to achieve 10 posts.
May I have a post thank for helping?
Click to expand...
Click to collapse
Dude this is really crazy....... I thought it was someone trying to help me there and now this............................................ AAAhhhhhhh:crying::crying::crying:
Aztile said:
Dude this is really crazy....... I thought it was someone trying to help me there and now this............................................ AAAhhhhhhh:crying::crying::crying:
Click to expand...
Click to collapse
Oops, sorry to get your hopes up.
I do actually have a few things to say about the real problem here:
1. Are you sure that your device is charged up? If not, make sure to plug it in to charge.
2. If charging isn't the problem, I'm going to give it a safe bet that your device is bricked. Like, turned into nothing more than a brick. (That's what "bricked" actually means ) If the device doesn't respond to the power button (which your posts have led me to believe), then there is no way to revive your device.
aah come on
thenookieforlife3 said:
Oops, sorry to get your hopes up.
I do actually have a few things to say about the real problem here:
1. Are you sure that your device is charged up? If not, make sure to plug it in to charge.
2. If charging isn't the problem, I'm going to give it a safe bet that your device is bricked. Like, turned into nothing more than a brick. (That's what "bricked" actually means ) If the device doesn't respond to the power button (which your posts have led me to believe), then there is no way to revive your device.
Post thank for the real answer?
Click to expand...
Click to collapse
Jesus!!!! Did you just say "NO WAY" come on buddy don't do this to me..................................................... It's like i'm half dead...... there must be some way to unbrick it.........................Come on PLZ plz plz:crying::crying::crying::crying::crying::crying::crying:
aah come on
thenookieforlife3 said:
Oops, sorry to get your hopes up.
I do actually have a few things to say about the real problem here:
1. Are you sure that your device is charged up? If not, make sure to plug it in to charge.
2. If charging isn't the problem, I'm going to give it a safe bet that your device is bricked. Like, turned into nothing more than a brick. (That's what "bricked" actually means ) If the device doesn't respond to the power button (which your posts have led me to believe), then there is no way to revive your device.
Post thank for the real answer?
Click to expand...
Click to collapse
Jesus!!!! Did you just say "NO WAY" come on buddy don't do this to me..................................................... It's like i'm half dead...... there must be some way to unbrick it.........................Come on PLZ plz plz:crying::crying::crying::crying::crying::crying::crying:
Aztile said:
Jesus!!!! Did you just say "NO WAY" come on buddy don't do this to me..................................................... It's like i'm half dead...... there must be some way to unbrick it.........................Come on PLZ plz plz:crying::crying::crying::crying::crying::crying::crying:
Click to expand...
Click to collapse
You said you've cleared eMMC and also some boot related stuff.
Well, messing with your eMMC and boot partition isn't a good idea, if you wiped your entire eMMC partition it means you've also wiped bootloader stuff...
I'm sorry but looks like your phone is totally bricked....
First of all stop shouting...!
Are you sure you choose "advaneced menu" and not "mount and storage" ....?
Also me too I think your device is bricked...
If you can't recognise it from fastboot and adb and you can boot to bootloader and recovery mode it is bricked...
root-expert said:
First of all stop shouting...!
Are you sure you choose "advaneced menu" and not "mount and storage" ....?
Also me too I think your device is bricked...
If you can't recognise it from fastboot and adb and you can boot to bootloader and recovery mode it is bricked...
Click to expand...
Click to collapse
Ooops Sorry.....
Ok I understood..... IT'S BRICKED..........
Well then how to unbrick it
Aztile said:
Ooops Sorry.....
Ok I understood..... IT'S BRICKED..........
Well then how to unbrick it
Click to expand...
Click to collapse
If your phone won't turn on at all, it's totally bricked. Only a motherboard replacement will fix it...
As you know your phone has hard bricked buddy
then you should also know you cant fix it
try odin and flash bootloader (if u can without open download mode)
or Nokia care is the best way...
Well, it happened
I was sitting on a bench and somehow my phone found a way to slide between my fingers and crash. (I must note that it dropped on the bench, which was like 10 cm max fall).
Anyway, I came home, plugged it into my computer and miraculously the phone works even though the screen is all crashed/pixelated/non-responsive.
Is there a way to control my phone with my computer? Like viewing everything on the computer itself?
There are some programs that I need to backup my files there in order to use them on my other phone.
Thanks!
Hi
Thanks for writing to us at XDA Assist. Here is a thread which will be very helpful to you:
[Tool][Windows] Control a device with a broken screen
Good luck!
timmaaa said:
Hi
Thanks for writing to us at XDA Assist. Here is a thread which will be very helpful to you:
[Tool][Windows] Control a device with a broken screen
Good luck!
Click to expand...
Click to collapse
Already tried it.
I can't see if I got into the recovery mode and cmd does not recognize what "adb shell" is.
Even if I somehow reach it (and I'm not sure if I really did) then on windows it gives me an error qhsusb_bulk (driver not found).
Airbender123 said:
Already tried it.
I can't see if I got into the recovery mode and cmd does not recognize what "adb shell" is.
Even if I somehow reach it (and I'm not sure if I really did) then on windows it gives me an error qhsusb_bulk (driver not found).
Click to expand...
Click to collapse
If you're seeing qhsusb_bulk in Windows there's more wrong with the phone than just the screen unfortunately. I think we're going to have to move your thread into the Nexus section so the Nexus experts can lend a hand. Please standby while we have your thread moved.
Good luck!
Transmitted via Bacon
I finally managed to get into recovery mode. It seems like the "qhsusb_bulk" error is gone.
I tried using the adb shell but it doesn't recognize my phone even though device manager sees it perfectly fine.
Any help?
Maybe there is a chance that USB debugging is enabled so I just waste my time, how can I check?
Airbender123 said:
I finally managed to get into recovery mode. It seems like the "qhsusb_bulk" error is gone.
I tried using the adb shell but it doesn't recognize my phone even though device manager sees it perfectly fine.
Any help?
Maybe there is a chance that USB debugging is enabled so I just waste my time, how can I check?
Click to expand...
Click to collapse
Does the "adb devices" command return your serial number?
Transmitted via Bacon
timmaaa said:
Does the "adb devices" command return your serial number?
Transmitted via Bacon
Click to expand...
Click to collapse
Nope, that's the problem I'm facing currently.
It just gives me an error "device not found".
There could be many reasons for that. Unfortunately I'm not terribly experienced with this phone so we'll need to wait for one of the Nexus experts to come and lend a hand.
Airbender123 said:
Nope, that's the problem I'm facing currently.
It just gives me an error "device not found".
Click to expand...
Click to collapse
Please Google "15 second adb installer". Use that to install adb drivers. Then open a command prompt. Make sure you navigate to where adb gets installed (usually in program files) then adb device
Edit: To check Developer Settings go to Settings then About phone. Tap your build number 7 times. This will enable developer options in settings. Turn on developer mode there.
Sandman-007 said:
Edit: To check Developer Settings go to Settings then About phone. Tap your build number 7 times. This will enable developer options in settings. Turn on developer mode there.
Click to expand...
Click to collapse
Ummm that's kind of hard to do with a shattered display.
OP Just follow sandmans advice to get the drivers right and you'll be able to follow the tools instructions you're trying to use to enable USB debugging. If you just want your data off you could also just use:
Code:
adb pull /sdcard
Is your Bootloader unlocked?
If USB debugging is not enabled in Android and you can not enable it in android due to unreadable screen,
Your only option is to ADB shell from custom recovery such as TWRP.
You can only boot into custom recovery if your bootloader is already UNLOCKED.
theesotericone said:
Ummm that's kind of hard to do with a shattered display.
Click to expand...
Click to collapse
Not really. There are some tools out there that let you view and control your screen on a PC.
Sandman-007 said:
Not really. There are some tools out there that let you view and control your screen on a PC.
Click to expand...
Click to collapse
Yes there are. The OP is trying to use one of them. He has a broken screen and is unable to use the screen on the device. He does not have USB Debug enabled. To use the program to mirror screen you need USB Debug enabled. See the catch-22 there? His only hope is to enable it via recovery and ADB. But as @joegestes points out if he's not already unlocked he needs to unlock for that. Unlocking wipes the phone. Another catch-22.
This thread is still alive?
So I've tried absolutely everything, new drivers, flash batch all newest firmware.. different computers, restarting computer..
whatever I do I cannot manage to get any computer to detect my Nexus 5 via adb or mounted storage.. the only thing that is detected is fastboot..?
any ideas??
Maybe it's a driver problem on your system. Did you try another computer?
What does device manager show? An unknown device connected? An acer device connected?
Sent via tapatalk from my cataclysm'd Lollipooop Nexus 5
Ben36 said:
What does device manager show? An unknown device connected? An acer device connected?
Sent via tapatalk from my cataclysm'd Lollipooop Nexus 5
Click to expand...
Click to collapse
nothing, nothing detected at all. but the USB port on the phone works fine because fastboot is working fine..
any idea's anybody? I've tired several computer with different windows versions.
This phone is absolutely undetectable by USB/ADB. It charges perfectly fine and fastboot works flawlessly...
You have an issue with the Nexus 5's driver and your adb driver, but not your fastboot driver.
Try uninstalling/reinstalling the drivers and use the 15-second adb/driver installer, if that doesn't work then try the universal naked driver.
Elluel said:
You have an issue with the Nexus 5's driver and your adb driver, but not your fastboot driver.
Try uninstalling/reinstalling the drivers and use the 15-second adb/driver installer, if that doesn't work then try the universal naked driver.
Click to expand...
Click to collapse
tried both, this phone isn't detected by any computer at all when it's switched on, zero. It doesn't show up as android, or acer or anything, there is no driver able to be installed because the phone isn't even detected by the computer unless I put it in fastboot mode.
omg, first the first time it just got magically detected in TWRP as ADB composite device. This is completely un-explainable, it's been days this was achievable..
restarted phone, impossible to detect again....
THE_KINGDOM said:
tried both, this phone isn't detected by any computer at all when it's switched on, zero. It doesn't show up as android, or acer or anything, there is no driver able to be installed because the phone isn't even detected by the computer unless I put it in fastboot mode.
Click to expand...
Click to collapse
You can still install/uninstall a driver if the device is not plugged in/detected as unknown device.
Have you tried manually reinstalling the driver?
Elluel said:
You can still install/uninstall a driver if the device is not plugged in/detected as unknown device.
Have you tried manually reinstalling the driver?
Click to expand...
Click to collapse
it's not detected at all thats what I'm trying to explain, it's not an unknown device, it's never detected at all
THE_KINGDOM said:
it's not detected at all thats what I'm trying to explain, it's not an unknown device, it's never detected at all
Click to expand...
Click to collapse
If you are certain it is an issue with the device and not your drivers, try booting up a Linux distro (Ubuntu will do) in a VM or directly off a USB stick, as it requires no driver installation in Linux to access the internal storage via USB.
Elluel said:
If you are certain it is an issue with the device and not your drivers, try booting up a Linux distro (Ubuntu will do) in a VM or directly off a USB stick, as it requires no driver installation in Linux to access the internal storage via USB.
Click to expand...
Click to collapse
it's strange because for the first time a few moments ago i was able to see the device in adb mode via TWRP, as soon as I restarted the phone it's impossible again, I've tried 20+ times since then.
only thing i can get repeatedly with no issues at all is the bootloader interface/fastboot
tried with linux, ubuntu. no connection.. But I already knew it wasn't drivers.. device isn't detected at all.. it's not like it's allocating the wrong drivers.. it's not even registering a usb device was connected to the PC unless in bootloader/fastboot.
Sounds like an issue with your usb cable or the phone side adapter. Have you tried ADB through a wireless connection?
[RANT ON]
I have already addressed your issue in this thread http://forum.xda-developers.com/google-nexus-5/help/diagnosing-usb-driver-adb-issues-windows-t2514396/post59570828#post59570828 and yet without so much as even a single reply or simple thank you for taking my time and telling you in detail how it is, you found it necessary to create a new thread? Are you hoping for a magic bullet?
What's even worse in my world. You offered not a single thank you to anyone here in this tread that completely wasted their valuable time trying to help you after you already have your answers.
I realize I am relatively new member here at XDA. But I've been lurking here for over 5 years. Forgive me but this guy is why I have been reluctant to join and help until recently. He is the reason I will not waste much more of my time attempting to help others. [RANT OFF]
I will try to calm now.
Thanks for listening and I don't care if you are offended.
THE_KINGDOM said:
my situation is quite different from yours. There is no ability to "adb reboot" my device because the device is completely undetectable by USB.
I've now only managed to see the device twice in adb mode and that was completely random while in TWRP recovery, and I didn't need to turn on ADB sideload to make it visible either.. other than these two times I've tried well over 100-150 times, this phone is absolutely undetectable by USB/Computer unless in the bootloader.
Click to expand...
Click to collapse
joegestes said:
If you are able to detect the device in bootloader "fastboot devices" but still can't ABD devices in android with USB debug enabled or in recovery and/or you experience intermittent ABD detection. After looking through OP and post #322 you are absolutely certain that it is not a driver issue, you are likely looking at a hardware failure of the charging port.
https://www.youtube.com/watch?v=qqCEXEmcj4Y
If it were me, I'd replace the port and re-attempt ADB devices.
Click to expand...
Click to collapse
joegestes said:
Also be sure to try a new high quality USB data cable. (not a cheep charging cable)
Click to expand...
Click to collapse
joegestes said:
[RANT ON]
I have already addressed your issue in this thread http://forum.xda-developers.com/goo...es-windows-t2514396/post59570828#post59570828 and yet without so much as even a single reply or simple thank you for taking my time and telling you in detail how it is, you found it necessary to create a new thread? Are you hoping for a magic bullet?
What's even worse in my world. You offered not a single thank you to anyone here in this tread that completely wasted their valuable time trying to help you after you already have your answers.
I realize I am relatively new member here at XDA. But I've been lurking here for over 5 years. Forgive me but this guy is why I have been reluctant to join and help until recently. He is the reason I will not waste much more of my time attempting to help others. [RANT OFF]
I will try to calm now.
Thanks for listening and I don't care if you are offended.
Click to expand...
Click to collapse
Wow man you need to cut the estrogen pills out. This is borderline extremely weird...
You gave me one potential plausible scenario and this thread was created days before my activity on that other thread. And my first comment u quoted was a reply to somebody else lolol...
Also, I have no charging issues whatsoever with this phone... therefore charging port may not be an issue at all. But at this point I don't deny that chances are it's an extremely rare hardware issue, rare.. Hence why I'm trying to explore potential software issues/fixes before hand.
And actually I'm very generous with the "thank you" I dish out to users on XDA, unfortunately I most people seem to think its a driver issue because thats the common issue.. But im trying to relay to people that my phone is not detected at all, zero recognition of a USB attached device. EXCEPT when in fastboot.. Which makes no sense... If it was a broken port then why does fastboot work????
THE_KINGDOM said:
If it was a broken port then why does fastboot work????
Click to expand...
Click to collapse
Because it could be a single broken connector in the port, it could be a bad internal connector, it could be a motherboard issue, etc.
THE_KINGDOM said:
Wow man you need to cut the estrogen pills out. This is borderline extremely weird...
Click to expand...
Click to collapse
Resorting to childish insults when you are called out is weird for a Man and IMO cowardly.
It is also why you should consider taking you own sage advice.
THE_KINGDOM said:
You gave me one potential plausible scenario
Click to expand...
Click to collapse
Actually, I gave you virtually all plausible scenarios.
THE_KINGDOM said:
this thread was created days before my activity on that other thread.
Click to expand...
Click to collapse
Correct. You did not create a new thread afterwards. You first created a new thread and then posted the same issue in a separate thread.
My mistake.
But still you are here, after you already have your answers, never bothering to thank anyone.
THE_KINGDOM said:
I don't deny that chances are it's an extremely rare hardware issue
Click to expand...
Click to collapse
Good, but IMO, it's not that rare on N5.
THE_KINGDOM said:
And actually I'm very generous with the "thank you" I dish out.
Click to expand...
Click to collapse
I,ll give you the same answer I give most people I encounter who are likely in denial.
Your Right! :good:
I haven't seen this mentioned, just making sure you have turned on usb debugging in the developer options otherwise adb won't work.
Sent from my Nexus 5 using Tapatalk
Hi. This is probably the simplest thing ever but...
I can easily get into download mode. I want to get into recovery though and got there only once and can't get back. If that can't be answered, then how can I use adb on my smt700 with usb debugging disabled? It's glitching out and will not let me into any kind of settings page. That includes wifi connection. Help!!
Photon156 said:
Hi. This is probably the simplest thing ever but...
I can easily get into download mode. I want to get into recovery though and got there only once and can't get back. If that can't be answered, then how can I use adb on my smt700 with usb debugging disabled? It's glitching out and will not let me into any kind of settings page. That includes wifi connection. Help!!
Click to expand...
Click to collapse
see your other thread, http://forum.xda-developers.com/showpost.php?p=60979457&postcount=2
This thread will be closed.
On a business trip in Dubai, the phone suddenly turns it off.
Now I am posting in the airport.
No response, cant turn on. tried whatever I can do.
can charge, but no flash sign.
connected to my laptop, no response
adb check ending up no devices.
Please someone help me figure this out.
Damn google, I have no backup phone, and use the phone to take pictures.
Will never use google phone again,
Are you able to boot into bootloader? Did you previously have USB debugging turned on?
can't boot into bootloader? and USB debugging enabled.
post-mortem said:
Are you able to boot into bootloader? Did you previously have USB debugging turned on?
Click to expand...
Click to collapse
Does fastboot devices find anything?
I don't think so. I tried adb devices, find nothing.
confirmed with a local engineer. the so called storage chip on the mainboard was broken. will try to find someone to replace it, then come here to update.
Damn google.
post-mortem said:
Does fastboot devices find anything?
Click to expand...
Click to collapse
bush911 said:
Damn google.
Click to expand...
Click to collapse
I guess you should blame HTC.