Hi all,
I have a GN and have an unusual problem :
My GN screen simply stoped to work while using it...
The phone continue to work
He sence my finger
He reboot, I can reboot, reboot after battery unplug in normal mode or bootloader ....
but I have one big question : can I find a solution without changing the screen ... (I can do it myself but a GN screen is 120$...)
And HOW can I enable USB debuging without screnn ... I have to enter password and find usb debuging without screen ... impossible mission)
The only thing I make for now is booting in bootloader and pulled all data and make a backup on the computer
Hey guys. My Wildfire's screen doesn't respond to touch. Also the phone doesn't respond when I use the buttons at the bottom so I can't do anything. I want to try this
http://forum.xda-developers.com/showthread.php?t=1275680
but firstly I would like to recover the data on the phone. Obviously, I need to put the stuff on my computer using USB. But whenever I connect it to the computer, it goes into charge mode and doesn't mount as a disk drive. Is there anyway to get around this, given that the screen isn't responding? I'd mostly like to get the contact details, if possible. Many thanks.
deadman1206 said:
Hey guys. My Wildfire's screen doesn't respond to touch. Also the phone doesn't respond when I use the buttons at the bottom so I can't do anything. I want to try this
http://forum.xda-developers.com/showthread.php?t=1275680
but firstly I would like to recover the data on the phone. Obviously, I need to put the stuff on my computer using USB. But whenever I connect it to the computer, it goes into charge mode and doesn't mount as a disk drive. Is there anyway to get around this, given that the screen isn't responding? I'd mostly like to get the contact details, if possible. Many thanks.
Click to expand...
Click to collapse
are you s-on or s-off? if you have no touch input you are really gonna struggle. especially without root. does the trackball still work and do you have usb debugging on?
heavy_metal_man said:
are you s-on or s-off? if you have no touch input you are really gonna struggle. especially without root. does the trackball still work and do you have usb debugging on?
Click to expand...
Click to collapse
I haven't done any rooting or anything like that (I don't know much about it) so it must be s-on. The phone doesn't seem to respond to the trackball or the volume buttons either. I don't know if I have USB debugging on. I think I do. When I connect it to the computer the phone says "USB debugging connected" but I can't remember if I had it turned on or off in the settings. The computer recognizes it as "Android Phone" but, as I said, the phone is in charge mode and I can't access any of the files.
deadman1206 said:
I haven't done any rooting or anything like that (I don't know much about it) so it must be s-on. The phone doesn't seem to respond to the trackball or the volume buttons either. I don't know if I have USB debugging on. I think I do. When I connect it to the computer the phone says "USB debugging connected" but I can't remember if I had it turned on or off in the settings. The computer recognizes it as "Android Phone" but, as I said, the phone is in charge mode and I can't access any of the files.
Click to expand...
Click to collapse
Hmmm. OK, can you power off the Phone for me and then reboot with volume down held in and power at the same time.
This will take you to a white screen with info like s-off, s-on and hboot and a version number beside it. Can you share with me that Info please.
Then use the volume buttons to navigate the phone to reboot and use power to select. Then once it has rebooted connect it to the PC with the screen unlocked/awake and see if it pops up on the screen with USB debugging connected.
If we can security unlock your phone with revolutionary we will be able to add a custom recovery to your phone and make a full back up of your mobile. If USB debugging is not enabled you are stuck, and cannot retrieve anything from the phone before you ruu unless you are s-off already, (but that is very unlikely).
Your SD card can be removed from the back of your phone and with it all your pictures/music videos ect will be safe but your contacts are on the phone.
If you had the phone linked to your Google account it may be worthwhile logging in on the website and going to the Google dashboard. Find your phone on the list and your contacts "may" be backed up there if you enabled it during your initial phone set up.
Sent from my HTC Sensation using Tapatalk
I have a 2013 Nexus 7 wifi tablet, bootloader locked, with USB debugging disabled. It decided mid-activity that all it would like to do in life is display the "Google" image on the boot up screen.
I can access the bootloader so I tried doing the standard wipe in recovery mode but that did not work.
Investigated Wugfresh's Nexus Root Toolkit. Drivers (Windows 7) are installed but under Step 4 of the Full Driver Configuration guide it is unable to find the device as an ADB device, even though the device does show up on my Device Manager (but only as bootloader interface, not ADB). Tried to use the unlock feature anyway but on the tablet it just gets stuck on the "unlock bootloader" screen after trying to run the unlock tool (choosing "yes" by pressing the up volume button to scroll to the yes option, followed by the power button to select it).
My questions based on this are simple:
1) Can I unlock this device without having USB debugging enabled? If so, how?
2) Can I restore to factory stock settings without having USB debugging enabled (and not using recovery mode on the device itself, as that does not work)? If so, how?
All of the tools I have seen thus far require that USB debugging be enabled on the device. Since I can't actually boot up the device, there is no way to make this happen. I don't really care about any of the data on the device, I just want it to function again to avoid buying a new one.
Stop using a toolkit. Your device will never be recognized by adb when booted into the bootloader.
Unlocking the bootloader is simple if you have the Windows drivers set up correctly. Open command prompt with admin privileges, type 'fastboot oem unlock' and done. This is why I hate toolkits.
nhizzat said:
Stop using a toolkit. Your device will never be recognized by adb when booted into the bootloader.
Unlocking the bootloader is simple if you have the Windows drivers set up correctly. Open command prompt with admin privileges, type 'fastboot oem unlock' and done. This is why I hate toolkits.
Click to expand...
Click to collapse
I believe this also requires that USB Debugging be enabled. I would paste links but the forum prevents me from doing so since I just signed up.
If I am incorrect in thinking that USB Debugging must be enabled for this to work, then please let me know. All I really need is clear instructions on how to hard reset the device without USB debugging enabled. Unlocking just seems to be a prerequisite for that in most of the tutorials I have found so far.
You can flash the device back to stock with wugs without adb. There should be an option you pick under the factory restore button that says "soft bricked" which tells wugs that it needs to go straight fastboot mode instead of trying to restart the tablet with adb.
skrypj said:
You can flash the device back to stock with wugs without adb. There should be an option you pick under the factory restore button that says "soft bricked" which tells wugs that it needs to go straight fastboot mode instead of trying to restart the tablet with adb.
Click to expand...
Click to collapse
Thanks for your reply. I have tried this option without the ADB (but with my computer recognizing the device). Since it did not work I expect the device is well and truly screwed (the recovery mode factory reset also does not work on the tablet itself).
Bugnerd said:
Thanks for your reply. I have tried this option without the ADB (but with my computer recognizing the device). Since it did not work I expect the device is well and truly screwed (the recovery mode factory reset also does not work on the tablet itself).
Click to expand...
Click to collapse
Couple of things:
1. You may also have a driver issue, I was playing with this the other day on both my Nexus 5 and Nexus 7. My nexus 5 worked fine, but later that day when i tried my nexus 7 I had troubles with my PC recognizing the N7 in fastboot mode. It would be fine in ADB and would reboot, but then the computer would freak out when it saw the fastboot device. Sometimes it would kinda work, sometimes the N7 would freeze on the bootloader screen or fail to flash during the process. It even locked my PC at one point. I completely uninstalled(per the Step 1 instructions in Wug's) all Android associated drivers(Samsung, LG, Asus, whatever. Kill them all) on the PC and reinstalled and it solved the issues. It sounds like maybe your PC is failing to flash properly like mine was.
2. Not sure if you tried this yet but; go to Options Menu>Flash Stock Tab>Check "Enable 'Force Flash Mode' . . . " Then try to flash stock + unroot again with the soft-bricked option selected. This basically makes Wug's ignore the check process at the beginning of the flash. I had to do this for both my N5 and N7.
Keep in mind, you will lose EVERYTHING on your N7 if you unroot and flash, including your internal storage.
Yeah, it does not seem to want to do the unroot + flash even with the override of checks. It seems unlocking is really a prerequisite for that tool (according to the text that appears as it proceeds), and unlocking appears to require the USB debugging. If it really can be unlocked without that, then it is not cooperating and just getting stuck on the unlocking screen. I expect it is now a very expensive paperweight.
All of this nonsense just over a year since I bought it, of course.
Try it with another computer, another USB cable...
I'm in the same boat, can't get it to unlock so it's essentially dead now
I've tried original and a G3 usb cord and nothing, front and rear USB ports, just will not unlock, almost to the point of sending it on and paying to get it fixed if possible , will try another computer first
Can you boot manually into fasboot mode and do flashing full stock firmware for ur device..
Bcoz I thinks you don't need usb debugging when on fastboot mode..
if you want to use toolkit, you must setup all driver for ur device first using the toolkit.. but you must do it when ur device is full "working", not when It's just stuck on google image... that's ur main problem now ...
you should try install the driver again on new "fresh" pc ....
Good luck bro... :fingers-crossed:
Did you try to manually unlock it? Boot to the boot loader screen(down volume+power) and the fastboot unlock it using the cmd in windows?
Az-one786 said:
Can you boot manually into fasboot mode and do flashing full stock firmware for ur device..
Bcoz I thinks you don't need usb debugging when on fastboot mode..
if you want to use toolkit, you must setup all driver for ur device first using the toolkit.. but you must do it when ur device is full "working", not when It's just stuck on google image... that's ur main problem now ...
you should try install the driver again on new "fresh" pc ....
Good luck bro... :fingers-crossed:
Click to expand...
Click to collapse
I can boot into fastboot mode but when I then switch to recovery mode manually to reset it does not go to the recovery mode screen (it did at first, but now just gets stuck on the sick robot screen, then on the "Google" loading screen).
I can try the drivers again on another PC, but I have a feeling that won't fix anything.
skrypj said:
Did you try to manually unlock it? Boot to the boot loader screen(down volume+power) and the fastboot unlock it using the cmd in windows?
Click to expand...
Click to collapse
I looked into this a week or so ago and I think I determined that it would also require the USB debugging to be on (at least from the tutorials). Do you have any recommendations of tutorials on this process? Screwing around with this stuff is not really my bag.
Bugnerd said:
I can boot into fastboot mode but when I then switch to recovery mode manually to reset it does not go to the recovery mode screen (it did at first, but now just gets stuck on the sick robot screen, then on the "Google" loading screen).
I can try the drivers again on another PC, but I have a feeling that won't fix anything.
Click to expand...
Click to collapse
Ok.., Your have no choice by now, you'll need to find a working driver for your PC to get recognize your tablet when on fastboot mode..
I've got this issues before when I want to update my tab using toolkit...
My PC can recognized my tab as adb devices, but when it's reboot to check fastboot status it fail to detect my device is on fastboot mode..
But maybe I'm so lucky that day, Moboginie notification has pop-up and it's has searching and found the driver and fix it itself ...
Then i try again and this time it's has no problem at all till now... I still can access my storage using Moboginie but until now window explorer still fail to recognized my N7...
It's so weird isn't it ...
Try Moborobo
Bugnerd said:
I can boot into fastboot mode but when I then switch to recovery mode manually to reset it does not go to the recovery mode screen (it did at first, but now just gets stuck on the sick robot screen, then on the "Google" loading screen).
Click to expand...
Click to collapse
After the recovery screen with "sick" Andy, did it automatically begin to reboot? If not, you know that it's very tricky with the power+vol up button (sometimes I think it's power+both volume buttons that works) to access that screen in recovery (the one past sick Andy). Sometimes I've tried five or six times. I have twrp so I can't check it out right now.
As far as adb/fastboot drivers set up to run any commands, I thought they were required. I'm not certain about USB debugging. It seems you've tried with your device in fastboot and running Cmd (fastboot oem unlock) from your fast boot directory. Do you get a device code when you enter [fastboot devices] while in that directory? If not, your N7 will not accept fastboot commands.
Sent from my Nexus 7 using Tapatalk
hello everyone,
the power button and the volume-down-button have both little or even no more function. I did not turn off the phone for several days now, knowing that I would not be able to turn it on again. I searched the internet for help, enabled usb-debugging and downloaded adb-files. I was able to connect to my phone and did the reboot command to see if it was working. it did.
my question is: once the phone turns off for any reason, will I be able to enter a boot mode (recovery, fastboot, download-mode: whatever they call it, I couldnt tell the difference) that allows me to turn on my phone or do I have to do additional steps..? At one page in this board (http://forum.xda-developers.com/tmobile-lg-g3/general/how-to-boot-lg-g3-fastboot-mode-t3087445) I read that isnt as easy for the lg g3 as it is for other android phones to get into the right boot mode. is that thing necessary or can I use that "download mode" for using adb and starting the phone.
what commands do I have to enter to start my phone once it is in that respective mode?
hope you can help. looking forward to your answers..!
regards
silvan
Hey everyone,
I've got my phone startet now, but I still do need a kind of "backdoor", so I can restart the phone, if the button stops working again or if I loose this small plastic-piece again.
Furthermore it would be really cool if I would not have to dismantle the phone to turn it on
First of all I thought about ADB, but ADB doesn't recognize my device anymore.
I don't know why. My USB-Debugging is (and was) activated, but the PC isn't authorized yet (since it doesn't recognize the ADB it won't ask me for permission).
How can I fix this? I already tried to restart (pc and device), reinstall the drivers and kill/start the sever. Nothing worked.
But I'm also open for new ways.
I thought of some possibilities:
1. Change the "action_on_power_plug_connect": Is there a way to change the action my phone does execute when the power plug is connecting? Right now it's just starting to charge mode.
2. Boot on shedule/remote: Is there any app, which got the power to boot the phone, even if it is completely shut down?
I'm thankful for every single advice you can give me here.
Sincerly,
maj0r_tom
~~~~~~~~~
DEVICE INFO:
~~~~~~~~~
System: ColorOS 2.5.1i (Android Lollipop)
Root: Yes, SuperSU
Recovery: Stock Recovery
Hardware buttons working: None :]
---------------------
OLD POST:
---------------------
Hello everyone,
I've just repaired the broken display of my old Oppo Find 7.
Everything worked fine but one thing: The power button does not respond anymore.
It's a small piece of plastic, held in place by a bridge of metal.
When I press it onto the "sensor", it doesn't seem to recognize it.
Everything else is working perfectly - connecting a power source makes the phone start into loading mode.
Is there any way to start the phone without the physical button?
Maybe something beyond fastboot?
Or do you think that any phone-repair shop could help me there?
Sincerly,
maj0r_tom
Edit: The Volume Buttons do not work, too.
I've tried ADB. I could swear, that USB debugging is enabled (used Titanium Backup, it's asking for it on startup).
But ADB does tell me, that the phone is unauthorized.
Edit 2: Volume buttons repaired.
Edit 3: I got it.
The buttons didn't break - they just lost a small piece - a very ****ing small piece.
I did see it dropping from my Vol+ button and could insert it into the power button.
The phone startet, Debugging was enabled. Do I have to check anything else to activate ADB?
Hello, i don't know if my problem is the same but i have the power button don't work too. For restart my phone, i press VOL- when I charged the phone. He boot in recovery and next i reboot system. If a hardware solution is possible, tell me.
maj0r_tom said:
Hey everyone,
I've got my phone startet now, but I still do need a kind of "backdoor", so I can restart the phone, if the button stops working again or if I loose this small plastic-piece again.
Furthermore it would be really cool if I would not have to dismantle the phone to turn it on
First of all I thought about ADB, but ADB doesn't recognize my device anymore.
I don't know why. My USB-Debugging is (and was) activated, but the PC isn't authorized yet (since it doesn't recognize the ADB it won't ask me for permission).
How can I fix this? I already tried to restart (pc and device), reinstall the drivers and kill/start the sever. Nothing worked.
But I'm also open for new ways.
I thought of some possibilities:
1. Change the "action_on_power_plug_connect": Is there a way to change the action my phone does execute when the power plug is connecting? Right now it's just starting to charge mode.
2. Boot on shedule/remote: Is there any app, which got the power to boot the phone, even if it is completely shut down?
I'm thankful for every single advice you can give me here.
Sincerly,
maj0r_tom
~~~~~~~~~
DEVICE INFO:
~~~~~~~~~
System: ColorOS 2.5.1i (Android Lollipop)
Root: Yes, SuperSU
Recovery: Stock Recovery
Hardware buttons working: None :]
---------------------
OLD POST:
---------------------
Hello everyone,
I've just repaired the broken display of my old Oppo Find 7.
Everything worked fine but one thing: The power button does not respond anymore.
It's a small piece of plastic, held in place by a bridge of metal.
When I press it onto the "sensor", it doesn't seem to recognize it.
Everything else is working perfectly - connecting a power source makes the phone start into loading mode.
Is there any way to start the phone without the physical button?
Maybe something beyond fastboot?
Or do you think that any phone-repair shop could help me there?
Sincerly,
maj0r_tom
Edit: The Volume Buttons do not work, too.
I've tried ADB. I could swear, that USB debugging is enabled (used Titanium Backup, it's asking for it on startup).
But ADB does tell me, that the phone is unauthorized.
Edit 2: Volume buttons repaired.
Edit 3: I got it.
The buttons didn't break - they just lost a small piece - a very ****ing small piece.
I did see it dropping from my Vol+ button and could insert it into the power button.
The phone startet, Debugging was enabled. Do I have to check anything else to activate ADB?
Click to expand...
Click to collapse
Hi, I think that an alarm application in ColorOS was able to start the phone if you had alarm setup.
But I'm sure this only applies to the ColorOS native alarm application, so no third party apps....
tw9 said:
Hi, I think that an alarm application in ColorOS was able to start the phone if you had alarm setup.
But I'm sure this only applies to the ColorOS native alarm application, so no third party apps....
Click to expand...
Click to collapse
I have had same problem. I am not expert at all but can suggest you to check out your phone mother board. Problem might be there. Nothing will work if your phone motherboard is out of function. Thanks