Hi i have a 16gb wi-fi model and recently updated the build to Android 4.2.
On purchasing this originally i rooted and unlocked it so i could use stickmount for USB storage etc. but after updating it this app was only working occasionally so i downloaded root checker pro and it said my device wasn`t properly rooted so i attempted to re-root but since then i have had this problem.
I installed wugfresh version 1.6.0 and flash stocked/unrooted in softbrick/bootloop to see if this helped which it done but on start up i had the same problem with pausing at the X screen after the google and unlocked padlock screen.
The only thing i can do is get the tablet into recovery mode but have tried factory resetting this way but no joy there either.
My PC also wont recognise the device now and theres a problem with not recognising adb mode?
Lastly once i unplugged the device from the usb otg lead it turned off and wont come back on so i think the battery might now be faulty/broken.
If anyone can offer some advice for a fix this would be greatly appreciated but i`m not your average tech head so a simplified answer would also be appreciated.
Thanks
Related
I have done searching with my crappy searching skills and cannot find anything that has helped yet so here is my problem.
I have my buddy's phone that was rooted but never given cwm and so is running the stock rom. The phone itself will not go into debug mode when I plug it into a computer. I have reset the phone through recovery and in the os but neither have fixed the problem. Is there an update zip i can flash to fix this? Or what do I do?
I'm running Win 7 32 and have the samsung drivers installed.
Figured it out, the phone has a bad connector.
Hi guys,
I have a massive problem.
I recently updated to 4.3 rooted etc, after a few days of not using my nexus 7 on the pc I wanted to flash a new rom.
Now my N7 is only shown as an "Unknown Device" in my Device Manager.
I tried to deinstall Drivers, install, everything, I tried every possibilty in Wug's toolkit, nothing worked. I also tried it on another Notebook where i have never connected any mobile device, same message and i'm not able to install the drivers.
I also tried several ports and cables(the original one included)
Here is the message:http://i.imgur.com/tgxOeZQ.jpg
Translation: The optimal driver software for your device is already installed.
After this I flashed back to 4.2.2 (downloaded the rom on my N7) while performing a normal factory reset, I can't wipe everything because then I am not able to flash anything.
So after flashing to 4.2.2 my N7 was shown as a portable device in my device-manager. I then turned on USB-Debugging to stock+unroot, it was then shown again as a Unknown device, in both modes, USB-Debugging turned Off and On.
So now my question, is there a solution to this? I searched for possibilites to get back to stock without USB but most of them were a bit sketchy or had dead links. Please help me (sorry for my bad english)
Edit:
I just the cable of my old Motorola Defy, and it randomly connects and disconnects(still shown as unknown), so basically I think it is possible that my USB plug is broken(it takes about 6 hours to load the battery which I think might be as well a reason for a broken USB plug).
But to send it back to Google I need to Stock Unroot first so here my problem is again!
greetings
I have tried many options. My Nexus died shortly after a KitKat update, but it may have been frazzled by a faulty car charger.
Cannot access recovery mode.
Cannot get PC to see ADB device
Would replacing the USB board help?
Out of warranty so willing to try almost anything.
Search for naked drivers and install them, then remove previous drivers from device manager and update.
And please provide as much info as possible about your setup before asking a question.
Sent from my Nexus 7 using xda app-developers app
xateeq said:
Search for naked drivers and install them, then remove previous drivers from device manager and update.
And please provide as much info as possible about your setup before asking a question.
Sent from my Nexus 7 using xda app-developers app
Click to expand...
Click to collapse
Hi, I was only ever stock. Unrooted, but had USB debugging.
I sideloaded KitKat when it came out and installed the Google Experience launcher. Received an OTA a day later that was only 1-2Mb.
The sideloading worked perfectly using the adb sideload kitkat.zip.
The evening after the OTA and the unit died. It is possible that it was a car charger, but I think highly unlikely as it never affected a Kindle or Xperia Z. But now I cannot get the PC to even see that the device is connected and neither can I get Recovery Mode to fully start. I select Recovery Mode and all I see is the Google logo. I have tried all sorts of button presses to get the android on its back with the red triangle. I may have missed something obvious so any suggestions would be a help.
Connect to wall charger if u cant get it to charge then it is ok,
try changing ur data cable that ur using to connect it to pc.
if ur tablet was not connected to charger when it dies then it is not the carger. OTA usually mess things up on modified/ rooted devices.
Hi, Thanks for the response.
I've tried all my cables. I can get the unit to charge no problem. It is just that I cannot get it to recover itself.
Powering on freezes on the Google logo and the CPU overheats like a really good overheating thing.
I go into the bootloader and if it doesn't freeze I can select all the various top level options. I have tried selecting Recovery mode and I cannot get that to work either. If I select Recovery mode and hit the power button it once again freezes on the Google logo. I have tried holding the volume up and pressing the power, but nothing happens. The only option I have is to power off again.
I had hoped that the nexus Root toolkit would help, but as it is never seen or recognized by the laptop I think I am totally screwed. I am thinking that my best hope is to sell it for spares. Unless there is a way of resetting the machine without a computer or being able to access recovery mode. I haven't seen anything like this.
I have been searching for hours/days, can not find a solution. I recently unrooted my Nexus 7, 2012 WIFI to download and try the new stock Lollipop 5.0 . I found out the the 5.0 was too buggy and kept freezing up my Nexus. I decided to revert back to 4.4 using the nexus toolkit (as I have many times in the past) and in the process lost my recovery option while in bootloader mode (was on a friends pc and had loose USB cable). Because I can not access the system to enable USB debugging. I am now on my own PC using a good USB cable I cant get ADB to recognize the Nexus. I have tried many drivers. I am thinking this is considered a hard brick scenario. When I do a reboot in bootloader mode, I get gray screen. When I try using recovery, I get dead droid with upside down triangle. Any help would be appreciated. I am not a rookie at this but also not a pro so I need help.
Remember, I do not have USB debugging enabled, nor can I boot up to access dev options. I can go into bootloader and adb modes but can not get adb or nexus toolkit to recognize. Thanks
Anyone?
Hi!
My Nexus Player was rooted, but this was messed up by a recent OTA update (not the current 7.1.1, but the last one before that I guess), after which I factory reset it. I don't really remember if I tried connecting it to my PC then or do something else. A while later I tried rerooting with Nexus Root Toolkit, but there were some issues with the ADB drivers I think, it didn't maintain a connection with the computer during fastboot. It also kept resetting the USB default to charging (I chose MTP, but it just kept switching back by itself). So I took a break for a while and now it won't connect to my computer at all except for a brief moment while booting. All during this I've tried different cables and actually two more computers, but the issue persists. The bootloader is still unlocked and factory resets don't help. Does anyone have any idea how to solve this?
Best regards,
Mikk
re enable debugging? The flip back to Charging from MTP is by design I think...as is the inability to shut off auto update. Google trying to save us from ourselves. Have you flashed twrp? I found the only way to see the player on the desktop was when booted in twrp. Otherwise, like you , it appeared the player wasn't connected. I do believe I was still connected as a fastboot device though.
I haven't bothered to re root as my SD card is supported and kodi installed from the play store removing any need to sideload or file explorer my way to install apps. I have found the 7.1.1. update to be solid/stable with no issues.