Related
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?
Yesterday afternoon, I took it upon myself to attempt a Kindle Fire root, which seemed to be successful. I had followed the instructions and I had even installed TWRP (At least, I think I did). I think was asked to reboot, and I did. Unfortunately, I am now met with a brick. All that is showing right now everytime I turn on the device is the "Kindle fire" logo all in white letters with the screen's brightness down. It does not go any further than that at all. I had tried to remedy the situation by using Unbrick tools, but anytime I clicked on "Stuck on Logo", I got the "error: device not found" message. I even tried to do the standard "Hold power button for 20 seconds", but that didn't work either.
All the rooting and TWRP flashing/installation was done with a regular Amazon USB cable. I didn't have a fastboot cable, so I made do with a regular one. Now it seems as though I might need to purchase one from Amazon. Although I had read somewhere online that someone was able to use an Xbox One Play and Charge Cable claiming that it works the same as a fastboot cable (can anyone confirm this, by the way?). Hopefully, my Kindle Fire HD can be saved with or without a fastboot cable.
No amount of Googling has gotten me very far at all. I would include a screenshot of what my Kindle Fire looks like when turned on, but I cannot due to being a new user. I may, however, be able to send a PM if requested.
Forgot to add. The model of my Kindle is the Kindle Fire HD 7 3rd Generation
UPDATE: Apparently, my computer can still kind of detect it. Whenever I have the device plugged into my computer and press the power button and volume down, I get a USB connection sound with a message "the last USB device you connected to the computer malfunctioned and Windows does not recognize it"
EDIT2: I think this might be in the wrong section.
Really? No help on this issue at all? That's sad, man.
Did you try to boot to the recovery?
If you can turn it off do so. Wait a few seconds and then press power and volume + button at the same time until it boots.
Does it boot to the recovery screen?
xSentinel said:
Did you try to boot to the recovery?
If you can turn it off do so. Wait a few seconds and then press power and volume + button at the same time until it boots.
Does it boot to the recovery screen?
Click to expand...
Click to collapse
Yes I have tried that, but that did not boot to recovery at all. The Kindle Fire is still stuck at the white Kindle Fire logo and won't go any further at all. It even shuts off probably because I am holding the power button.
I am running Windows 10 if that helps.
Windows 10 should not matter for this particular thing because I am talking about not being connected to your PC. If you are connected to the PC while doing this that could interfere with the process I would imagine, so do this while not connected.
I read in another post where a guy had similar freeze and had to press power first for a second then vol + and hold it for a long time. Eventually it came up.
Mine never had a white fire logo. Mine starts with a white amazon logo followed by colored/flashing fire logo. From what I have read if you can make it to the colored fire logo you can save it. If you are stuck at the white amazon logo then it's worse.
But I have never read of a white fire logo. Mine is a 6 (4th gen) which could be the difference.
When mine screwed up I was stuck at colored fire logo (past white amazon logo). It took numerous resets but eventually I got back in.
Neither pressing and holding volume + or - seemed to help at all. Volume - seems to do at least something as the computer detects it for a split second. I'm not really sure what that is, though.
Even when not connected, I'm getting nowhere with this.
Okay, so further progress has been made, I think. I had left the Kindle off and held the Volume - button, then connected it to the computer. Lo and behold, I hear a USB Device connected sound with no error message in sight. I have no idea where to go from there.
EDIT: Saw error message. I spoke too soon.
DragonfireEX402 said:
Okay, so further progress has been made, I think. I had left the Kindle off and held the Volume - button, then connected it to the computer. Lo and behold, I hear a USB Device connected sound with no error message in sight. I have no idea where to go from there.
EDIT: Saw error message. I spoke too soon.
Click to expand...
Click to collapse
Sorry to say, you used a root guide for the 2014 Fire HD 6/7 on your 2013 Kindle Fire. Try posting here: http://forum.xda-developers.com/kin...p/help-thread-question-noob-friendly-t3206681 or (more people) at KFSOWI Modding on G+
DoLooper said:
Sorry to say, you used a root guide for the 2014 Fire HD 6/7 on your 2013 Kindle Fire. Try posting here: http://forum.xda-developers.com/kin...p/help-thread-question-noob-friendly-t3206681 or (more people) at KFSOWI Modding on G+
Click to expand...
Click to collapse
Actually, I didn't use a root guide for the 2014 Fire HD on my 2013 Kindle Fire. I actually followed a guide on a different website which I cannot find record of because Google Chrome's browsing history has a way of messing up.
Thanks for the link, by the way. Really helps.
Regrettably I can't help you. I have a 2014 HD 6, so I have no familiarity with your device. And on mine all I have done is rooted it and disabled practically all the Amazon stuff to try to make it the most android like that I could possibly get without bricking it.
I have not installed a different launcher.
I have not installed a custom ROM.
I have not installed TWRP (yet)
I have not install gapps (or any Google stuff at all)
I have not installed TWRP because, to me at least, the instructions posted here are very difficult to follow. After reading them numerous times I still don't get it. I'm not sure what to download, from where, what to run or how.
Also I don't know what value having TWRP would be for me because I have no desire to install gapps or any Google stuff. So, at this point at least, I have not had any need for TWRP yet. Other than installing Google stuff I have not needed TWRP.
I have not install gapps because I am trying to make this thing light and android like. It seems to me that taking off a ton of Amazon stuff just to replace it with a ton of Google stuff defeats my personal purpose with this tablet. I have all the apps I need or use downloaded directly from their sources so I don't need Google Play.
xSentinel said:
Regrettably I can't help you. I have a 2014 HD 6, so I have no familiarity with your device. And on mine all I have done is rooted it and disabled practically all the Amazon stuff to try to make it the most android like that I could possibly get without bricking it.
I have not installed a different launcher.
I have not installed a custom ROM.
I have not installed TWRP (yet)
I have not install gapps (or any Google stuff at all)
I have not installed TWRP because, to me at least, the instructions posted here are very difficult to follow. After reading them numerous times I still don't get it. I'm not sure what to download, from where, what to run or how.
Also I don't know what value having TWRP would be for me because I have no desire to install gapps or any Google stuff. So, at this point at least, I have not had any need for TWRP yet. Other than installing Google stuff I have not needed TWRP.
I have not install gapps because I am trying to make this thing light and android like. It seems to me that taking off a ton of Amazon stuff just to replace it with a ton of Google stuff defeats my personal purpose with this tablet. I have all the apps I need or use downloaded directly from their sources so I don't need Google Play.
Click to expand...
Click to collapse
The thread I've started is not in the appropriate section anyway, so don't feel any regret.
xSentinel said:
Windows 10 should not matter for this particular thing because I am talking about not being connected to your PC. If you are connected to the PC while doing this that could interfere with the process I would imagine, so do this while not connected.
I read in another post where a guy had similar freeze and had to press power first for a second then vol + and hold it for a long time. Eventually it came up.
Mine never had a white fire logo. Mine starts with a white amazon logo followed by colored/flashing fire logo. From what I have read if you can make it to the colored fire logo you can save it. If you are stuck at the white amazon logo then it's worse.
But I have never read of a white fire logo. Mine is a 6 (4th gen) which could be the difference.
When mine screwed up I was stuck at colored fire logo (past white amazon logo). It took numerous resets but eventually I got back in.
Click to expand...
Click to collapse
@xSentinel
how did you get it working again. currently I am stuck at the flashing fire logo and goes no where else. any help is appreciated.
Sorry for the delay.
Honestly I don't know exactly what specific thing I did, as I was panicking at the time and tried everything. First off I booted to the recovery screen. I tried clearing the cache partition and then rebooting. That did not appear to fix it as it still hung at the fire logo.
Next I tried every other option in the recovery list one by one except for reset and return to factory defaults. I did not want to do that yet and lose all I had gained so far.
Eventually I just set it down on the fire logo and walked away, figuring I needed a break and time to clear my head and contemplate my next move. Probably I also took some time to post in here and see if anyone had an answer. By the time I came back I saw it had booted up correctly and was working fine. So it is possible that all it needed was an inordinate amount of time to boot.
So sadly I can't say with any specificity what actual thing I did that did it or if it just fixed itself when I left it alone for a long time. I wish I could be more help.
Hello to all genius mind.
I am writing here, to find a solution for my problem. I will start from beginning, to be as clear as possible.
This summer, during my vacation time, while diving, I found SG J5 in the bottom of the lake (sorry for the person who lost it like that...). Since I never had android smartphone in my hands before, I was wondering, can this device still work, since I have no idea how long it was under water and what can I learn from this process.
After opening it up, cleaning with 96% alcohol and drying it, devices finally showed some signs of life. Actually, almost everything was working, amazing...
Once I got this device running, I started to deal with software. Following some tutorials online, I was on the process to bypass RFP, but could not finish it, since I had other important matter to attend to. After I was back, and turned device on, for some reason, it booted into safe mode. I have been tried again SideSync method, but it was not working, since device did not reacted, after I plugged in to PC. Computer can recognize device and I can even browser the files in it. Weird thing is, that lower volume button stopped responding (I had theory that it could be jammed, once I removed it and cleaned contact, no changes was in the system, still in safe mode, so its not jammed button...), it was working before and all other buttons are working fine. Because of that, I cannot load recovery mode.
OTG method also did not worked, since nothing happen when I plunged usb into phone (safe mode block all external apps). I have tried to flash new ROM, with a help of "Samsung 300K Tool" I can launch download mode, but new ROM did not gave any result either, and RFP blocks all custom ROM's, that could modify system.
ADB do not find the device, since USB Debugging is probably off, and I don't know a way how to activate it from PC. The trick to disconnect WiFi, when it checks info for google account, did not worked either, since its not possible to select a text for sharing it.
After trying all the methods that I could find, I hit the brick wall. Phone works fine, but its completely locked. I am thinking, that new Samsung protection system is designed like this, to force phone in to safe mode after one hard reset and lock all posiblities to byass RFP, not sure though, it could be hardware problem to, but no idea where...
Does anyone here could help me out with this case
THANKS!
Best regards to all,
HG
Hello everyone,
I've been a reader for a while, purely out of interest. I've never really dabbled with customizing android. In that regard I am a noob... I recently acquired a Medion X6001 that I was planning to build into my car as informant/navigation. Phone root successful, developer options active, debugging and oem options active. Automate programmed to all the standards I was happy with., worked great. All that was left to do to was get the thing to boot on charge. The "fastboot oem off-mode-charge 0" command was unsuccessful so I resorted to trying to find the system file responsible for battery icon on charge with power off.
That's where I went wrong. This phone has two icons; first a battery with a bolt, then switches to another with blue fluid and battery percentage. I found the blue fluid battery icon - 'system/bin/kpoc_charger', unfortunately I needed the killswitch battery icon. So I made another guess and renamed - 'system/bin/lmkd'. This was the file directly before ...kpoc and my daft logic lead me to believe that that might have been the right file. Obviously, it wasn't.
So the problem? The phone won't boot. Not really... At first, it was entirely stuck in bootloop. So, the good sheep I am, I factory reset the phone through recovery. The phone still went into bootloop for a few minutes, but came out of it to an applet saying 'optimizing apps'. Took 10 minutes to optimize and then went through to another applet saying something along the lines of "system process not found, do you want to wait?". Behind this applet I could tantalizingly see the startup screen of a freshly reset android.... It gave the option to wait or push ok, neither of which were actually active to touch. If I held the power button it would give me the option to shutdown, reboot or screenshot, also none of which where actually active to touch.
So after more googling, I wiped the cache through recovery. Everything stayed the same; bootloops for a few minutes then applets. Only now everything is in Chinese kanji... which is why I can't reiterate verbatim what the applets originally said...
After around 12 hours of tirelessly searching the web I've tried everything I've found but every time I get through a door there's another one closed. I can't install twrp or clockwork, I can't flash the rom, the phone won't let me unlock the bootloader in fastboot. Went I type the command it asks if I want to unlock it: volume up yes, volume down no. But fails: "remote access denied"
Since the factory reset, I don't have access through adb anymore. If I let the phone boot I can see it connect to the computer, but only as mtp. The file is entirely empty. I have no access to usb debugging. And to remotely access that, I need to be able to unlock the bootloader.
I can't get around the blocks and everything that is advised to get around bootloops and flash through fastboot are seemingly impossible because I no longer have proper access. But I can't get into the phone to get access...
And to make matters worse, just now as I type this.... I can't get into fastboot anymore. I think the phone battery is dead, but apparently doesn't accept a charge. When I plug it in the battery symbol appears, the dark red led lights up indicating very low battery. Very shortly after that the led turns off, which is not how it was before I buggered everything. Battery icon stays on, but when I push the necessary buttons to get into recovery, everything goes blank and the phone does nothing. When released, battery icon comes back and red led for a few seconds. Repeat. Phone has been plugged in all night....
I'm nearly bald from pulling my hair out. I hope there's someone out there that can give me a hand. I have a hard time believing I bricked the phone just by changing a bin file name.
Thanks in advance!
fastboot
I have access to fastboot again. Plugged the phone into a different cable, is now charging. I can see the battery % through recovery.
Back in business....sort of.
Any idea's welcome.
bump
Anyone?
Well I found the ultimate cure: buy a new one.
I will however keep fumbling around with the other one and hopefully as my knowledge increases I'll have a break through.
** This post should be in the "Help & Troubleshooting" section of the Nexus Player - ooops. **
My Nexus Player started hanging up at the 4 balls bounce routine last week. After trying a factory reset, the only thing that I've been able to do to get back to Android boot with TV interface is the OTA restore from the latest version 8.0.
This however doesn't stick, as if the device powers off, powering up, the problem returns.
I had the hdmi output connected to a switch that allows the monitor to be shared with a laptop. If the NP device goes to sleep, the switch automatically opens up the feed from the laptop (dual monitor). If I switch back, the wake up mode becomes the 4 balls again.
Someone pointed to the Oreo upgrade as being problematic. Do these symptoms sound like software or hardware?
I did connect the unit without the switch directly to the monitor and got slightly different results. Now the unit tells me that I need to run system restore which formats /data and another partition then partially loads get the Android screen and starts over. Tried to restore from OTA again and it won't pair with the controller saying "Can't play this video" .
Got it running again, let it run overnight with a channel selection and by morning it had died.
Tried loading a different OTA Ver.8 and it is too smart for that. I am reading though from several sites that I'm not the only one with a partial brick since the update to Ver. 8. - Unfortunately, that was "supposed" to be the last update, yet there appears to have been a "zero day" failure built into it.
OK Google (seems as if Asus isn't responsible) the ball is in your court, yet it's going to be difficult to patch when the device is partially bricked.
ggregor said:
My Nexus Player started hanging up at the 4 balls bounce routine last week. After trying a factory reset, the only thing that I've been able to do to get back to Android boot with TV interface is the OTA restore from the latest version 8.0.
This however doesn't stick, as if the device powers off, powering up, the problem returns.
I had the hdmi output connected to a switch that allows the monitor to be shared with a laptop. If the NP device goes to sleep, the switch automatically opens up the feed from the laptop (dual monitor). If I switch back, the wake up mode becomes the 4 balls again.
Someone pointed to the Oreo upgrade as being problematic. Do these symptoms sound like software or hardware?
I did connect the unit without the switch directly to the monitor and got slightly different results. Now the unit tells me that I need to run system restore which formats /data and another partition then partially loads get the Android screen and starts over. Tried to restore from OTA again and it won't pair with the controller saying "Can't play this video" .
Got it running again, let it run overnight with a channel selection and by morning it had died.
Tried loading a different OTA Ver.8 and it is too smart for that. I am reading though from several sites that I'm not the only one with a partial brick since the update to Ver. 8. - Unfortunately, that was "supposed" to be the last update, yet there appears to have been a "zero day" failure built into it.
OK Google (seems as if Asus isn't responsible) the ball is in your court, yet it's going to be difficult to patch when the device is partially bricked.
Click to expand...
Click to collapse
There are a couple threads on this already. Mine is bricked too at the moment.
https://forum.xda-developers.com/nexus-player/help/stuck-google-screen-t3044191
https://forum.xda-developers.com/nexus-player/help/nexus-player-suddenly-dead-t3814519