Related
hello. i used LCD density monitor to try to fix the market after switching the DPI settings, and my device is unusable. as sooon as i boot, everything force closes, nothing runs. ADB cannot connect to the device. it says theres no device connected.
i used toolkit to reflash stock rom, but i cant reset to factrory, so it keeps booting into this terrible set up with nothing working. stock recovery is just the android with the open chest and eclamation.
going through the toolkit, i cannot get the ADB drivers to install and correctly see my tablet.
can anyone offer some help?
much appreciated!
Not sure if this will work for you but when ADB couldn't see my N7, it was because it was in MTP mode.
Settings > Storage > Menu (top right) > USB computer connection > select Camera (PTP)
If that works, you can push all the stock images and recovery via fastboot.
managed to finally get adb to work, flashed stock, and starting over wiuth a restore, but theres no MTP drivers installed. anyone have any idea how to install them or where to get them?
joshtb86 said:
managed to finally get adb to work, flashed stock, and starting over wiuth a restore, but theres no MTP drivers installed. anyone have any idea how to install them or where to get them?
Click to expand...
Click to collapse
Can you roll us a little how you managed to revive your device?
Sent from my Galaxy Nexus using xda premium
kind3rgarten said:
Can you roll us a little how you managed to revive your device?
Sent from my Galaxy Nexus using xda premium
Click to expand...
Click to collapse
to get ADB to work, i went through the manual driver install several times before i got it to work. i had the USB plugged into a usb 3.0 port, and for some reason, ADB does not recognize through 3.0 ports. plugged into a 2.0 port and had no problem getting ADB to finally recognize it.
I flashed stock, but rebooted to the same problem. i managed to get into the menu and factory reset. after factory resetting, it was fine.
no more LCD density until they fix that.
Make sure you have android SDK installed.
Sent from my Nexus 7 using Tapatalk 2
joshtb86 said:
to get ADB to work, i went through the manual driver install several times before i got it to work. i had the USB plugged into a usb 3.0 port, and for some reason, ADB does not recognize through 3.0 ports. plugged into a 2.0 port and had no problem getting ADB to finally recognize it.
I flashed stock, but rebooted to the same problem. i managed to get into the menu and factory reset. after factory resetting, it was fine.
no more LCD density until they fix that.
Click to expand...
Click to collapse
The easiest way to change your DPI is to either download ROM Toolbox or edit it yourself. ROM Toolbox is good for whole slew of things, not just DPI modding. I would recommend it for anyone with a rooted Android Device.
And thanks for telling us that information, nice to know that ADB doesn't support USB 3.0. :/
Sent from my Nexus 7 using xda premium
I have no idea what i did, but my Nexus 7 formatted every file on there, there's not even a rom it can boot into....I can boot into recovery, but I have no idea how I can bring a file and load a rom on Nexus 7 because I can only get to three things..bootloader, recovery and google (unlocked) that's stuck there because of no rom.
using nexus 7 toolkit...but i'm probably doing something wrong...getting device not found.
can someone give me a noob guide on what i can try to fix this
Use the flash back to stock option with device will not boot checked on wugfresh toolkit
Sent from my Nexus 7 using xda app-developers app
the computer is not picking up the nexus 7...it makes a sound when i connect or disconnect the USB, but it doesn't show up on the computer.
really need help...i'm sure this can be fixed since i can boot into recovery or boot loader...
djricekcn said:
the computer is not picking up the nexus 7...it makes a sound when i connect or disconnect the USB, but it doesn't show up on the computer.
really need help...i'm sure this can be fixed since i can boot into recovery or boot loader...
Click to expand...
Click to collapse
Did you try installing the driver package that comes with Wugs?
Its sounds like it isnt finding the drivers to me.Are you using a custom recovery or the stock?
Try using Odin and see if it recognizes it.
Kodiack99 said:
Did you try installing the driver package that comes with Wugs?
Its sounds like it isnt finding the drivers to me.Are you using a custom recovery or the stock?
Try using Odin and see if it recognizes it.
Click to expand...
Click to collapse
i thought odin is for samsung devices...where do i download one that works with N7?
I'm trying to install drivers, but it's not doing anything but opening up pictures with how to install in Wugs.
using wugs, it does pick up as grooper under device manager, but doesn't show on the MY COMPUTER section
not sure what you mean by recover or stock, but i can get into Clockword Mod Recover 6.0.1.0...does that help?
**tried odin 3.7 but it isn't doing anything
LOL sorry I got a few devices and 2 out of 3 are samsung.
Maybe try to install the drivers in the toolkit here http://forum.xda-developers.com/showthread.php?t=1809195 ,if you can get a image on there you should be able to flash it with Clockwork if you select install from zip.
I dont suppose you made a backup with Clockwork?
If you can get adb working you can easily flash it back to stock by following this http://forum.xda-developers.com/showthread.php?t=1907796
how do i do this when i can't boot into android
Driver Installation
This seems to be the most confusing part for many people. Be patient and thoroughly read all the instructions.
Enable usb debugging on your device (found under Settings > Developer Options)
NOTE: Since Android 4.2 the Developer Options are hidden by default.
To enable them, go to Settings > About Phone, and tap on build number around seven times. A small dialog will appear letting you know "You are now a developer!"
Install the abd driver - detailed instructions for installing or upgrading and existing driver on your version of Windows can be found at http://developer.android.com/tools/extras/oem-usb.html
Once the driver is installed open a command prompt and change directories to <your sdk directory>\platform-tools (see #2). From the command prompt run "adb devices". This will list any adb-capable devices that are connected to the computer by their serial number assuming your drivers are installed correctly. Recap:
Code:
can't figure it out....
"devices not found"
djricekcn said:
can't figure it out....
"devices not found"
Click to expand...
Click to collapse
Did you install the drivers from the nexus toolkit?
And maybe try a reboot of your pc,and try unplugging usb and replugging while in fast boot.
Also check in CWM and see if a backup has every been made even if its old, its better than where you are now.
there's no backup of anything on the nexus...everything got wiped somehow. nexus 7 toolkit keep tellingthe resource loader cache doesn't have loader mUI entry" whichs tells me it's ok..
adb: unable to connect backup
unplug / reboot / different ports...basic pc stuff already done
Maybe try using a different cable,Other than that maybe try a different pc and see if it loads a default driver to at least give you access to put a zip file on it to flash,could be your driver is corrupt on that pc never heard of it installing a nexus as grooper.
Besides that I'm at a loss.
Best of luck,hopefully you get it figured out.
so...i've tried the following already just to make it clear...
i already tried all the basic pc things
-switch usb ports
-reboot pc
-use usb2
-use usb3 ports
-use a different computer (one 8, one XP)....both...i don't really know what to do cause instructions seems to be mostly in 7 and/or just not working on 8
-rebooted asus n7
if someone can give me step by step, noob guide...instead of saying try thing / that, it may help me.
djricekcn said:
there's no backup of anything on the nexus...everything got wiped somehow. nexus 7 toolkit keep tellingthe resource loader cache doesn't have loader mUI entry" whichs tells me it's ok..
adb: unable to connect backup
unplug / reboot / different ports...basic pc stuff already done
Click to expand...
Click to collapse
A lot of people who think every thing got stopped find their files under /storage/emulated/0
Sent from my Nexus 7
Clean ROM 2.5 - leanKernel 0.7
Try this to get adb working it was a fix for this guy. If adb works you can flash stock images.
http://forum.xda-developers.com/showpost.php?p=30230955&postcount=8
If you're using one of the toolkits you should be able to push an image to it.
Sent from my HTC Desire S using xda app-developers app
Kearkan said:
If you're using one of the toolkits you should be able to push an image to it.
Sent from my HTC Desire S using xda app-developers app
Click to expand...
Click to collapse
which is what I'm having trouble with...it's not picking up....
and can't find media player 13....only find some sort of pack..tried it...not working becuase it's not applicable with W8 even though i downloaded the W8 version..arg.
http://windows.microsoft.com/en-US/windows/download-windows-media-player
Included in Windows 8 and Windows 8 Pro, but doesn't include DVD playback. Go to the DVD playback for Windows page to find out how to add DVD playback to Windows 8. To get Windows Media Player 12 for Windows 8 N and KN editions, download the Media Feature Pack.
Click to expand...
Click to collapse
I had exactly the same problem. I was able to restore mine to stock 4.2 without ever having the Nexus 7 show up under my computer. My understanding is that it isn't supposed to show up there unless it is booted into android, but I could be wrong. Anyways, just try downloading the stock N7 firmware and installing with the Unroot and restore stock option in the Wugfresh Toolkit, and if you want root and custom recovery back, simply use the option to reroot and follow the instructions. That's what I did and it worked like a charm.
Sent from my Nexus 7 using xda premium
was able to get it working with a MAC, can't adb push on the computer i have at home...not recognizing it even after drivers installed...well it recognizes but adb doesn't.
Finally, i have solved it !!! A couple of days ago, i forgot my pattern and clicked on forgot pattern, but i didn't get a prompt to turn on wifi. So basically, i was stuck, unless i wanted to do a factory reset and lose all of my data. Here's my unique solution to this problem, :
First of all, you need to be rooted and to have usb debugging ON. Otherwise, it won't work.
Second, you need to install wug's nexus toolkit, because it gives you an option to boot with a modified boot.img which has root privileges, go to advanced, you'll see it (if you know of any other way to boot up such an image, use it, because when you get locked out with the ,,forgot pattern'', your root won't work, that's why you need this boot image).
Here's what i did:
First, i booted the modified boot image and by using either adb or the toolkit, i pulled /data/data and /data/app to my pc.
Second, I made a full wipe and set up my N7 as usual. At this point, you need a good root file explorer in order to get to the /data folder. I installed colornote (from the app backup i made, because i wan't sure that there was a new version and,if there was, it could be a possible failure, because i wasn't sure how it would behave with the last version's data) and rebooted (in order for colornote to get into the dalvik cache).
Third, i opened up colornote's folder in /data/data and just replaced the databases folder with the one from my backup and i went to /data/dalvik-cache and deleted the corresponding color note dalvik file. Afterwards, i just rebooted and voila, all my stuff that i had written in color note was staring at me.
Now, i want to mention that i've only tried this with colornote (as it was my foremost priority to get to the essays that were stored there) and i've tried this on only 4.1.2. I can't guarantee that it will work on other apps or that you won't get damage to your precious Nexus 7, so please, proceed with caution, and don't blame me if something unexpected comes up. Good luck !!!
P.S. If you get more than one device or emulator, it's because you have bluestacks, disable or uninstall it, and you're good to go !!!
Did you try any of the suggestions offered to you in the other thread you started on this topic?
They seem like way less effort and some of them don't involve any wiping.
BTW when you do an adb pull you lose all file ownership and mode information; it is important to restore those correctly.
iAndroidOS said:
Second, you need to install wug's nexus toolkit, because it gives you an option to boot with a modified boot.img which has root privileges, go to advanced, you'll see it (if you know of any other way to boot up such an image, use it, because when you get locked out with the ,,forgot pattern'', your root won't work, that's why you need this boot image).
Click to expand...
Click to collapse
You can do whatever you want with the custom recovery - it is unaffected by the lock condition. You are complicating things by using a toolkit.
good luck
If you have USB debugging enabled you can just use adb to delete the pattern file and then unlock the tab.
Sent from my GT-I9000 using xda premium
NIMBAH said:
If you have USB debugging enabled you can just use adb to delete the pattern file and then unlock the tab.
Sent from my GT-I9000 using xda premium
Click to expand...
Click to collapse
I tried that and it didn't work
bftb0 said:
Did you try any of the suggestions offered to you in the other thread you started on this topic?
They seem like way less effort and some of them don't involve any wiping.
BTW when you do an adb pull you lose all file ownership and mode information; it is important to restore those correctly.
You can do whatever you want with the custom recovery - it is unaffected by the lock condition. You are complicating things by using a toolkit.
good luck
Click to expand...
Click to collapse
Thank you for reminding me, it is imperative to restore the permissions
iAndroidOS said:
I tried that and it didn't work
Click to expand...
Click to collapse
Weird I've done it a few times and its always worked. How did you do it ?
Sent from my GT-I9000 using xda premium
NIMBAH said:
Weird I've done it a few times and its always worked. How did you do it ?
Sent from my GT-I9000 using xda premium
Click to expand...
Click to collapse
I dunno, i went into adb and used the adb shell rm /data/system/gesture.key
command and as soon as it finished, i unplugged my N7 and rebooted it, and the login prompt was still there.
My nexus 7 has a serious bootloop problem.
i have been researching threads on fixing it and watched many a video and nothing seems to work.
when i boot up i will get google logo and nothing after that.
i have gone into the bootloader and gone into recovery mode and done a factory reset multiple times with no results.
connected to computer and run both NRT and nexus toolkit and tried multiple options.
flashing a new rom wont work because wont boot up and let me turn on usb debugging.
my last cahnce would be to try to get it replaced but it was a gift so do they fix those?
please help i think im going crazy!
What did you do to erase your ROM?
Your rom has been erased, as your device has no system to boot into. Your must have formatted your system. Just flash a rom and you should be fine. If needs be push the zip to your device through adb if you don't have a rom stored in your device, or if the current one is corrupted (which may be why it's not booting), and always check your md5.
All you need to do is flash the factory images through fastboot, or a custom ROM through recovery. There is nothing stopping you from taking either of those actions.
thankyou
i think the problem is actually my computer so i will try it on another one. thanks for the help this is all new to me
Username invalid said:
What did you do to erase your ROM?
Click to expand...
Click to collapse
i just did the factory reset from the recovery bootloader then it just bootlooped forever...
annoyingduck said:
Your rom has been erased, as your device has no system to boot into. Your must have formatted your system. Just flash a rom and you should be fine. If needs be push the zip to your device through adb if you don't have a rom stored in your device, or if the current one is corrupted (which may be why it's not booting), and always check your md5.
Click to expand...
Click to collapse
i tried to push files with nexus root toolkit but i cant without powering on and allowing usb debbugging, is there anything i am missing? or is there another way to do it?
asaman96 said:
i tried to push files with nexus root toolkit but i cant without powering on and allowing usb debbugging, is there anything i am missing? or is there another way to do it?
Click to expand...
Click to collapse
Yes and USB debugging is not needed.
asaman96 said:
i tried to push files with nexus root toolkit but i cant without powering on and allowing usb debbugging, is there anything i am missing? or is there another way to do it?
Click to expand...
Click to collapse
You can adb push files while in recovery. You need to choose the option in recovery first though.
Sent from my Nexus 4 using xda premium
So I managed to break the digitiser on my Nexus 4 last weekend. I have most things off it anyway but there are a couple of apps I need to run to get the data I need. I would like to be able to use android screencast to run the couple of apps or use it to set up my bluetooth mouse so I can use that as the screen itself still views fine. However, I need to enable USB Debugging in regular operation.
My phone is rooted, has CWM as the recovery and I have the ADB platform tools downloaded to my mac. This for a Nexus 7 is the closest I have come to an answer of how to do it. However, I can't find these files so I guess they are somewhere else to change these settings?
Any help would be much appreciated, thanks!
If you have cwm, not into recovery and use adb to pull files you want off your device
Sent from my Nexus 5 using XDA Free mobile app
jd1639 said:
If you have cwm, not into recovery and use adb to pull files you want off your device
Sent from my Nexus 5 using XDA Free mobile app
Click to expand...
Click to collapse
I can't seem to find build.prop to be able to edit it. I can find default.prop but when I do adb pull /system/build.prop it doesn't work just says 'does not exist'.
mike_dangerous said:
I can't seem to find build.prop to be able to edit it. I can find default.prop but when I do adb pull /system/build.prop it doesn't work just says 'does not exist'.
Click to expand...
Click to collapse
In your recovery, I use twrp, mount system. It should work then.
Sent from my Nexus 5 using XDA Free mobile app
Works! Brilliant thanks! Hopefully the rest of this works!
So I have managed to Brick my phone into a boot loop of the cyanogenmod startup symbol. What can I do now?
Can someone confirm what the file permissions should be for settings.db and build.prop?
mike_dangerous said:
So I have managed to Brick my phone into a boot loop of the cyanogenmod startup symbol. What can I do now?
Can someone confirm what the file permissions should be for settings.db and build.prop?
Click to expand...
Click to collapse
Permissions should be rw-r-r. There's always the factory image to flash. You're not bricked!
Sent from my Nexus 5 using XDA Free mobile app
jd1639 said:
Permissions should be rw-r-r. There's always the factory image to flash. You're not bricked!
Sent from my Nexus 5 using XDA Free mobile app
Click to expand...
Click to collapse
OK so I'm stuck how do I flash a factory image then? And I can't wipe my data or else the exercise is moot. Is there a way I can flash an image with the USB Debugging I require enabled? That would make my life much much simpler!
mike_dangerous said:
OK so I'm stuck how do I flash a factory image then? And I can't wipe my data or else the exercise is moot. Is there a way I can flash an image with the USB Debugging I require enabled? That would make my life much much simpler!
Click to expand...
Click to collapse
This going to get some what experimental but it won't wipe your date. I assume your bootloader is unlocked Just flashing the factory image will wipe your data but.... Download the factory image and extract it using winrar or 7-zip. Inside is a zip file, extract that too. You should find a system.img file in there. Flash that in fastboot
fastboot flash system system.img
Hopefully that'll get you past the boot loop
Edit, I'd forgotten that I made this. It'll get you up and running too. http://forum.xda-developers.com/showthread.php?p=533289
Sent from my Nexus 5 using XDA Free mobile app
jd1639 said:
This going to get some what experimental but it won't wipe your date. I assume your bootloader is unlocked Just flashing the factory image will wipe your data but.... Download the factory image and extract it using winrar or 7-zip. Inside is a zip file, extract that too. You should find a system.img file in there. Flash that in fastboot
fastboot flash system system.img
Hopefully that'll get you past the boot loop
Edit, I'd forgotten that I made this. It'll get you up and running too. http://forum.xda-developers.com/showthread.php?p=533289
Sent from my Nexus 5 using XDA Free mobile app
Click to expand...
Click to collapse
Your link doesnt seem to work?
mike_dangerous said:
Your link doesnt seem to work?
Click to expand...
Click to collapse
Try this
http://forum.xda-developers.com/showthread.php?p=53766885
Sent from my Nexus 5 using XDA Free mobile app
jd1639 said:
Try this
http://forum.xda-developers.com/showthread.php?p=53766885
Sent from my Nexus 5 using XDA Free mobile app
Click to expand...
Click to collapse
Thanks a lot, I have now successfully unbricked my phone, enabled usb debugging and through a series of key strokes turned on bluetooth and connected my mouse. However, somewhere in the process I appear to have lost all my app data which was the points of trying to get in there in the first place. What could have done this? All my data e.g. photos is there but my SMS are gone!
mike_dangerous said:
Thanks a lot, I have now successfully unbricked my phone, enabled usb debugging and through a series of key strokes turned on bluetooth and connected my mouse. However, somewhere in the process I appear to have lost all my app data which was the points of trying to get in there in the first place. What could have done this? All my data e.g. photos is there but my SMS are gone!
Click to expand...
Click to collapse
You most likely wiped the data partition while trying to fix the bootloop.
Would the data partition not be where everything else is stored?
Try this
http://forum.xda-developers.com/showthread.php?p=53766885
Sent from my Nexus 5 using XDA Free mobile app
Click to expand...
Click to collapse
Is this image modified so that USB debugging is ENabled?
Background: I'm in the same situation as OP. Broken screen/digitizer, USB debugging is DISabled, unlocked, rooted, CWM recovery. I need to ENable USB debugging, otherwise I just keep getting told "error: device offline".
theman5511 said:
Is this image modified so that USB debugging is ENabled?
Background: I'm in the same situation as OP. Broken screen/digitizer, USB debugging is DISabled, unlocked, rooted, CWM recovery. I need to ENable USB debugging, otherwise I just keep getting told "error: device offline".
Click to expand...
Click to collapse
If you boot into recovery and then type adb devices is it still offline? It shouldn't be. You can recovery data while in recovery if that's what you're trying to do
Sent from my SAMSUNG-SGH-I957 using XDA Free mobile app
Yes, when I attempt to run adb while in recovery I still get told that the device is offline.
Not sure what the best solution is. I was thinking about trying to flash a modified factory image that is already set up to have USB Debugging Enabled because I can probably flash that without wiping data. However, I don't know if such images exist or, if necessary, how to make my own.
Clearly the OP got around it but I can't seem to be able to and I'm not sure what to do.
theman5511 said:
Yes, when I attempt to run adb while in recovery I still get told that the device is offline.
Not sure what the best solution is. I was thinking about trying to flash a modified factory image that is already set up to have USB Debugging Enabled because I can probably flash that without wiping data. However, I don't know if such images exist or, if necessary, how to make my own.
Clearly the OP got around it but I can't seem to be able to and I'm not sure what to do.
Click to expand...
Click to collapse
I would start by flashing a twrp recovery in your current cwm recovery. I.know you don't need usb debugging checked in trwp.
Sent from my Nexus 5 using XDA Free mobile app
jd1639 said:
I would start by flashing a twrp recovery in your current cwm recovery. I.know you don't need usb debugging checked in trwp.
Sent from my Nexus 5 using XDA Free mobile app
Click to expand...
Click to collapse
Well I'll start there and keep you posted. Thanks!
I was able to get TWRP running as my recovery. When I run adb, my device appears as "recovery", however, I'm not able to access the "build.prop" file to edit it so I can ENable USB Debugging. I think this is because I'm not able to remount "system" as read/write. Not sure what my issue is, but when I run adb root, it claims to be already in root, however when I run su in adb shell, it claims it can't find su. Any ideas?