Well, I wrote a very thorough post explaining my situation, and when I tried to post it I was informed I was trying to register for my forum account instead. *facepalm* So with that thirty minutes wasted, let's try this again.
I have a Kindle Fire HDX 7. Software 4.5.2. I rooted it with an exploit, deleted some Metrics system files, and then after rebooting came up to a broken "desktop." The main Favorites window flashes from white to gray at me, there are no icons in it. I can't run any apps. I can get to the Settings menu, enable ADB, MTP, etc., but I can't turn on Wi-Fi or do updates. I did a Factory Reset, but that just erased all my content. If I reboot from this situation, I get stuck at the orange animated logo screen forever. If I hold the Volume + button and choose Factory Default from there, I can get back to the flashing Favorites desktop window, but still can't do anything just as before.
I have installed the Android SDK for Windows, installed the adb_usb.ini files, and the device is not recognized by Windows at all. It charges, but that's it. I tried using Ubuntu and SoupKit. They also don't see the Kindle as being there. No matter how many times I reboot the Kindle, all the SoupKit commands just hang at "Waiting for Device".
I made a Factory Cable. When I plug it in, the Kindle doesn't turn on. Holding down the power button does nothing. If I plug back in a regular USB, it turns right on. If I plug the Factory Cable in at the Flashing favorites screen, I hear the "plugged in" chime and the charging icon appears on the battery, but nothing else happens. If I try to reboot from there, with the Factory Cable still in, it shuts down but won't restart. I am open to the possibility I messed up the cable, but continuity seems good with my meter from both ends of the cable and from the solder joints to the micro-USB end, etc.
Has anyone seen the flashing desktop behavior? What should I be doing to try to get my Kindle recognized, so I can push the stock firmware back to it to fix this? Any help would be greatly appreciated. I made a foolish mistake and I can't seem to correct it myself, so I'm hoping someone else out there has the answer I'm overlooking. Thank you for your time.
Make sure you have the Kindle Fire ADB drivers installed.
EncryptedCurse said:
Make sure you have the (link text clipped due to restrictions on <10 posters) installed.
Click to expand...
Click to collapse
I had already installed the Google USB driver using the SDK Manager, and also modified adb_usb.ini and so forth, to no effect. I tried the instructions at the above link, though, since that Add-On site was something new. It appears some things have changed since that article was written, though, since the only thing available from the Add-On site from Amazon now is just the Kindle USB driver. I installed it, but Windows still doesn't recognize the Kindle. I rebooted the computer and the Kindle just to be sure.
To be clear, when I say it doesn't recognize it, I mean it doesn't even appear in Device Manager as an unknown device. No matter which computer, USB port, or cable I use, Windows 7 and Ubuntu simply do not see a device as there. The Kindle chimes and shows the charging icon, but Windows doesn't see anything as being plugged in.
From what I'm reading, it appears the factory cable I made is useless with the Fire HDX line.
I notice that the SuperSU app is still installed for what it's worth. I can't run anything, so it's kind of hopeless. I can't seem to find the original exploit that I used, but I basically just tapped a button that said "Gimme Root" and then I had super user access. Dangerous, dangerous super user access.
I'm not opposed to opening the Kindle up and tinkering with things, if there's any chance that will help correct this problem.
Valence1981 said:
I made a Factory Cable. When I plug it in, the Kindle doesn't turn on. Holding down the power button does nothing. If I plug back in a regular USB, it turns right on. If I plug the Factory Cable in at the Flashing favorites screen, I hear the "plugged in" chime and the charging icon appears on the battery, but nothing else happens. If I try to reboot from there, with the Factory Cable still in, it shuts down but won't restart. I am open to the possibility I messed up the cable, but continuity seems good with my meter from both ends of the cable and from the solder joints to the micro-USB end, etc.
Click to expand...
Click to collapse
"Factory cables" (sometimes called fastboot cable) are useless on all HDX models. Stick with a standard, high quality USB cable. I realize this seems counter intuitive but Amazon has done their best to make the latest generation of devices inaccessible to those looking to leverage the hardware or simply recover and non-functioning device.
Your issue with 'seeing the device' is likely due to Windows drivers. If the suggestion from @EncryptedCurse doesn't work suggest deleting all related entries from device manager when the device is tethered, reboot and then reconnect. Windows should install the correct drivers assuming you downloaded the Kindle specific ones in advance. There are shortcuts to this procedure (eg: a reboot really isn't necessary) if you know your way around Windows.
Davey126 said:
"Factory cables" (sometimes called fastboot cable) are useless on all HDX models. Stick with a standard, high quality USB cable. I realize this seems counter intuitive but Amazon has done their best to make the latest generation of devices inaccessible to those looking to leverage the hardware or simply recover and non-functioning device.
Your issue with 'seeing the device' is likely due to Windows drivers. If the suggestion from @EncryptedCurse doesn't work suggest deleting all related entries from device manager when the device is tethered, reboot and then reconnect. Windows should install the correct drivers assuming you downloaded the Kindle specific ones in advance. There are shortcuts to this procedure (eg: a reboot really isn't necessary) if you know your way around Windows.
Click to expand...
Click to collapse
I plugged the Kindle in (I'm at the Settings menu on it, since staying at the launcher/home/favorites screen just threatens to give me epilepsy with its constant flashing), I removed all the USB host controllers and root hubs, then scanned for hardware changes to reinstall them. The Kindle is not found, as a recognized device or an unknown one. As I said, when I boot from a thumb drive into Ubuntu, it doesn't find it either. When I run adb devices, it says no device is found. I have heard of people getting it to take ADB commands anyway, despite the not found error, by just repeatedly rebooting the Kindle, but it hasn't worked for me.
Valence1981 said:
I plugged the Kindle in (I'm at the Settings menu on it, since staying at the launcher/home/favorites screen just threatens to give me epilepsy with its constant flashing), I removed all the USB host controllers and root hubs, then scanned for hardware changes to reinstall them. The Kindle is not found, as a recognized device or an unknown one. As I said, when I boot from a thumb drive into Ubuntu, it doesn't find it either. When I run adb devices, it says no device is found. I have heard of people getting it to take ADB commands anyway, despite the not found error, by just repeatedly rebooting the Kindle, but it hasn't worked for me.
Click to expand...
Click to collapse
My bad - I overlooked some key details in your original post even though clearly stated. If you are not seeing the the device from any host (and you have certainly done the things I would have suggested) there is little you can do to recover via standard methods. A couple longshot suggestions:
- change cables. I know you tried a homebuilt cable but grab a couple standard cables just to rule out a bad wire; crappy usb cables are more common than people think
- check for a bent/missing pin in the micro-usb port; possible you aren't making a data connection (for others benefit, data and charge use different pins)
I realize both the above are highly unlikely given the sequence of events that lead up to your current problem. Running out of ideas ...
I doubt this will help, but one long shot on Windows is try to use the HDX toolkit to install the adv drivers. It won't do anything else with this build, but if this is a driver issue, it could possibly fix it. Also, if you can try revoking adb permissions if you can get to that window and try a different usb port.
These are all last ditch efforts though.
I tried the HDXToolkit driver install. It seemed promising, but it still doesn't see the Kindle. Checking the connector to see if the data pins were damaged was a good idea, but unfortunately they look unmangled. I am using a regular USB cable at this point, by the way.
I can't disable ADB mode on the Kindle itself. I can go to the Developer menu and try to disable it, but it just kicks me back to Settings and the option stays set to On when I go back to it. I can switch between MTP and CTP for whatever that's worth.
I appreciate the optimism. I'm quite upset with myself for doing this to my Kindle, as I really was getting a lot of use out of it. I can't help but be a little mad at Amazon, too, for making it so hard to fix this.
Oh, I was also going to mention that when I go to the stock recovery window with the option between reboot and factory restore, at the bottom under the Kindle logo it says "No Command" not sure what the significance is of that. I've seen where some people get a lot of error messages in that area.
Valence1981 said:
I tried the HDXToolkit driver install. It seemed promising, but it still doesn't see the Kindle. Checking the connector to see if the data pins were damaged was a good idea, but unfortunately they look unmangled. I am using a regular USB cable at this point, by the way.
I can't disable ADB mode on the Kindle itself. I can go to the Developer menu and try to disable it, but it just kicks me back to Settings and the option stays set to On when I go back to it. I can switch between MTP and CTP for whatever that's worth.
I appreciate the optimism. I'm quite upset with myself for doing this to my Kindle, as I really was getting a lot of use out of it. I can't help but be a little mad at Amazon, too, for making it so hard to fix this.
Oh, I was also going to mention that when I go to the stock recovery window with the option between reboot and factory restore, at the bottom under the Kindle logo it says "No Command" not sure what the significance is of that. I've seen where some people get a lot of error messages in that area.
Click to expand...
Click to collapse
Some very left-field ideas:
- try enabling bluetooth. Obviously if you can get that working there is a way to move files to/from device which might provide additional repair/recovery options.
- there is a rumor that long pressing power (40+ sec) performs some type of 'hard reset' on the device. Never see it work but worth a try.
If the device is still within warranty reach out to Amazon. They are pretty good about providing replacements (say it died during an update) although it will likely be a refurb. Who knows, might get one with a low enough fimware level to unlock. That opens a entirely new set of options.
It would appear that the HDX can't use Bluetooth for file transfers, only for connecting peripherals like keyboards and speakers. I'm going to try it anyway.
I have done the long power button hold down, but it doesn't seem to do anything.
I believe I should be in warranty. I got my Kindle for Christmas, so it's only about 6 months old. I'd rather not have to lie to customer service, though. So I'm still prodding at this trying to find a solution. If I could just get WiFi to work, so I could download a firmware update, I think that might help, but of course everytime I put in my network information and tell it to save it, it kicks me back to the Settings window and I get no connection.
The 40 second Hard Reset never worked in my case, although My Kindle didn't even boot up after my stupidity.
Valence1981 said:
It would appear that the HDX can't use Bluetooth for file transfers, only for connecting peripherals like keyboards and speakers. I'm going to try it anyway.
I have done the long power button hold down, but it doesn't seem to do anything.
I believe I should be in warranty. I got my Kindle for Christmas, so it's only about 6 months old. I'd rather not have to lie to customer service, though. So I'm still prodding at this trying to find a solution. If I could just get WiFi to work, so I could download a firmware update, I think that might help, but of course everytime I put in my network information and tell it to save it, it kicks me back to the Settings window and I get no connection.
Click to expand...
Click to collapse
Understand the ethical concern. Stating it died during an update is technically correct provided you don't indicate who was doing the updating. If asked if the device is rooted then you should come clean (which could impact Amazon's decision whether to replace). I have a great relationship with Amazon and believe honesty will ultimately get you further than deception.
So it doesn't appear there is anything else I can do about this. The Kindle isn't recognized by any computer I have, using Windows XP or 7, or using Ubuntu. I read that XP might be able to see it if I disabled ADB, but it's permanently turned on and if I try to turn it off it kicks me back to the Settings menu without actually changing the setting. Since no computer can see it, I don't think there is anything I can do to recover it. Unless someone figures out a way to flash the ROM by taking the thing apart and doing it manually, which I don't think is going to happen anytime soon. I can't believe I ruined my Kindle. Looks like all that's left is contacting support and seeing if they'll help me with a replacement.
Actually, one other thing. If I have to send the old one back, won't they notice that SuperSU is installed and realize what I did?
Valence1981 said:
So it doesn't appear there is anything else I can do about this. The Kindle isn't recognized by any computer I have, using Windows XP or 7, or using Ubuntu. I read that XP might be able to see it if I disabled ADB, but it's permanently turned on and if I try to turn it off it kicks me back to the Settings menu without actually changing the setting. Since no computer can see it, I don't think there is anything I can do to recover it. Unless someone figures out a way to flash the ROM by taking the thing apart and doing it manually, which I don't think is going to happen anytime soon. I can't believe I ruined my Kindle. Looks like all that's left is contacting support and seeing if they'll help me with a replacement.
Actually, one other thing. If I have to send the old one back, won't they notice that SuperSU is installed and realize what I did?
Click to expand...
Click to collapse
Sorry for your troubles. Amazon is pretty easy going - at least in my region. If the device is in warranty and you simply describe the symptoms without going into too much detail you should get a replacement. I don't believe they inspect devices beyond looking for obvious physical damage. The device will likely get 'reprogrammed' and be sold as a refurb. It makes little economic sense to have a tech inspect returned devices unless they are looking for something specific or a pattern of failures. Good luck.
Any have file APQ8074.hex and 8074_msimage.mbn for unbrick QHUSB?
I have my USB Config set to MTP and USB Debugging ON under Developer Options. However, whenever I connect a USB device, it always resets itself to Charge only and I have to switch it back to File or Photo transfer in order to connect to PC, AA, etc.
Any ideas on how to make the USB setting 'stick' with what I set in DO?
Is there an ADB command? Other setting I should be looking for? Any help is appreciated.
bilottag said:
I have my USB Config set to MTP and USB Debugging ON under Developer Options. However, whenever I connect a USB device, it always resets itself to Charge only and I have to switch it back to File or Photo transfer in order to connect to PC, AA, etc.
Any ideas on how to make the USB setting 'stick' with what I set in DO?
Is there an ADB command? Other setting I should be looking for? Any help is appreciated.
Click to expand...
Click to collapse
Strange, I *know* that mine 'used to' stay at whatever setting it was left at before. I just tried it now, and it still stays on whatever it was last set to, BUT... It automatically toggles the 'allow debugging over USB' to OFF every time I plug my phone into my computer. Now I know it didn't do this before, I wonder if it has something to do with 'always trust this connection' being set? Also, it really seems like this stuff is behaving just a wee bit different since I unlocked my bootloader. Hmm, could it be they have set a flag where USB debugging always turns off when the device is connected to something, IF the bootloader is unlocked?
bilottag said:
I have my USB Config set to MTP and USB Debugging ON under Developer Options. However, whenever I connect a USB device, it always resets itself to Charge only and I have to switch it back to File or Photo transfer in order to connect to PC, AA, etc.
Any ideas on how to make the USB setting 'stick' with what I set in DO?
Is there an ADB command? Other setting I should be looking for? Any help is appreciated.
Click to expand...
Click to collapse
I can confirm that this happens on mine too, really annoying, but I think this is not something a lot of people are facing, as there are literally NO other references to this that I can find. The reason why I think this is a very specific issue is that I recently got a Mate 20 X, which is essentially the same phone, and noticed that when I plug in the USB to a PC, I get a dialog pop up at the bottom of the screen asking if I want to transfer photos, files or to charge only. I NEVER saw this on the Mate 20 Pro, but that might be because I messed something up. I did do a lot of fiddling over ADB when the phone was new (mostly disabling apps) and giving permissions to apps like lightning launcher and System UI tuner and I'm wondering if this what has caused the issue.
Obviously even before I did this, I necessarily must have connected to the thing via USB, but strangely, I don't remember seeing this dialog... Having to go into developer mode to change this setting can't be how it's set up normally, as then basically no-one will be able to get connected via MTP (I suspect everyone on XDA knows about this setting, but suspect none of the average Joes even knows the option exists).
So the question is, what did we do wrong and how do we get this diaglog back because I have found that Developer mode is not accessible for other Users set up on the phone so I can't access the phone at all via USB now when the other user is using it...
I'm hoping we can work together to find out what we did wrong!
PS: I find like kaibosh99 that the USB debugging also toggles back to off. I am not rooted or bootloader unlocked
After a lot of faffing and looking into it some more, I don't get the pop-up dialog but have discovered that it is in the notification menu where it shows
USB icon . Charging via USB
Expanding that notification and tapping on it, gives the option to choose file transfer and a load of other stuff. It's a pity that a pop-up dialog doesn't open like on the Mate 20 X, you can see what I mean here
https://uk.community.huawei.com/mat...tried-usb-debugging-and-all-that-already-6786
Much easier than having to go into the notification menu!
Thread Closed Per OP Request
I'm helping a friend who needs backup of her broken phone for an upcoming court case.
I need to extract all photos (camera, snapchat etc) and text messages (sms/mms).
The phone seems to be working other than the screen and touch controls.
Replacing/repairing the screen isn't an option as we both have minimal funds, and my friend has a new phone already)
i have "access" to the phone, but neither USB Debughing nor MTP is enabled so i cannot access any files.
I'm able to unlock it with a keyboard connected (i hear the little unlock click after entering the pin, and the "turn off screen" click when i press the power button.) But i have to navigate blindly, and any guide i find seems arbitrary how to get to settings, it says to press win+n (same as pulling down the quick settings menu from home) and press tab an arbitrary number of times to get to the settings gear in the corner. i tried doing this on my own working note 10 plus with the external keyboard, but i see it scrolls through every notification, so unless you know the number of notifications, hitting the gear is just pure luck.
I have also tried hooking up a usb-c to hdmi dongle (which works and starts dex on my n10+) but it says no signal on the A80, so external monitor seems out of the question.
Is there a consistent way to enter settings, or any way to enable the following settings:
* enable voice assistant (accessibility settings so i can hear where i am and navigate using voice/sound)
* enable USB MTP (or similar so i atleast can access files from a computer)
* enable USB debugging (to use ADB to screenmirror and/or etc)
* alternatively clear notifications so entering settings should become consistant with number of keypresses
I have tried some apps like dr fone but it doesnt support backup from this model, and any other settings wants to wipe the phone.
I have tried holding both volume buttons to enable google voice assist, but also unsure if this ever worked
The phone is not on wifi and i am not 100% sure if wifi is enabled at the moment, nor if it has the current wifi password my friend uses, but i can try do do things from there if internet access will help.
I dont think google now nor bixby (if this phone has that) is enabled as i dont get any reply or voice ding while pressing the win key (home button normally on working android)
I think i can enter recovery and download modes, i got COM5 on odin, but I'm unsure if i ever get into recovery menu.. but even then, is there any custom recovery firmware that will enable usb mtp access at all for this device?
Also, I'm not able to have a computer connected at the same time as a keyboard as I'm using a wired keyboard with OTG adapter.
Tl;dr:
Have:
* A80 with broken unresponsive screen.
* Have access blindly through otg keyboard
Need:
* Need to enable mtp and/or usb debug (alt. Voice assist)
* Need consistent way to access settings
Both MUST be done using only wired otg keyboard.
Tried:
* Hdmi out (no signal)
* computer recovery software (no dice)
* having computer and keyboard connected simultaneously (keyboard works, pc doesnt recognize, could be dongle)
Hope someone can help me (us) fast.
Could anyone with an A80 and external keyboard please try this to enter settings from keyboard only:
0) [ESC] & ([WIN]+[Enter] to make sure to be on home
1) [WIN]+[Q] "quicklaunch buttons" pulldown menu appears
2) [TAB] (no change)
3) [Down arrow] (magnifying glass gets highlighted)
4) [Right arrow] X2 (gear is highlighted)
5) [Enter] should now be in settings
If this works, could you please count how many times you press down and enter to enter accessability settings and enable talkback, which should make navigating to usb settings etc much easier
Mods: please delete thi post.. its a A8 2018 mot A80, sorry about that
Greetings fellow techno-wizards! Got a big problem that I'm hoping you can help me with.
Long story short, my trusty Pixel 2 had one too many drops, now the screen won't turn on and won't respond to touch. The logic board is operating, and I haven't rebooted since then, so I can unlock with the fingerprint sensor.
I plan on getting an Pixel 5 when it releases, and have an LTE Tablet to limp along until then.
My biggest problem is authenticators on my phone that I may or maynot have the backup QR code for, as well as many other things I'd like to get off the phone before I retire it.
I have the following things at my disposal:
Pixel 2, with USB Debugging turned on, and recently trusted the PC. No screen, no touchscreen.
WearOS watch paired to phone (can get notifications and texts)
Bluetooth Mouse
Wired mouse with USB to USB C adapter
Chromecast
Win PC with Scrcpy installed, already tried to use it to show the screen on the PC, I'm guessing its been too long and I have to press a notification to trust the PC.
The Goal:
To cast the screen to a chromecast and pair a bluetooth mouse, and/or get Scrcpy working by accepting the dialog that I can't see. This would allow me to use the migrate tool to the new phone I will eventually get.
I tried long ago to use a USB C to HDMI adapter, that doesn't work. Google wants you to use a Chromecast for such things (Thanks a ton Google )
The thing I need to figure out next is how to use ADB to force the phone to start casting to a Chromecast, or to remotely accept the dialog. The wired mouse with adapter should work to control the phone instead of the touchscreen, but without any video out, I'm clicking blindly. The microphones are working, but I've never tried to command the assistant to start casting before.
Can anyone suggest the next step I should try?
Just had a thought, there are accessibility features for blind people that would let them use the screen without seeing it. Is there any ADB command to enable these features? If I plug in a keyboard, is there a keystroke combination to turn them on?
TheGeek007 said:
Just had a thought, there are accessibility features for blind people that would let them use the screen without seeing it. Is there any ADB command to enable these features? If I plug in a keyboard, is there a keystroke combination to turn them on?
Click to expand...
Click to collapse
Since you say ADB is enabled on the phone you should be able to pull out by means of ADB-driver the data in mind to your Windows computer.