I decided to change my dpi on my tablet to see if I could install an app that I needed from the market. Well I screwed up. I bumped it to 240 dpi and now I can't unlock my tablet when I cut the screen on because the unlock button that you slide to is off the screen. I can cut the camera on, but I have no home or back button because they are off the screen as well. I can't do anything. I need some help here. I have the build.prop file, but when I try to push it, it doesn't find my device. I have usb debugging on. Please help me before my wife kills me lol.
Wipe your tablet ,thing its fastest way.but you loose your apps and other stuff.
Wysyłane z mojego ASUS Transformer Pad TF300T za pomocą Tapatalk 2
I didn't think wiping would restore the build.prop file.
If the restore doesn't work, then you may have to flash the stock firmware to your tablet. Have you tried accessing it with adb?
I reset and it is still the same. Everytime I try to access through adb, it doesn't find my device. All the drivers are installed. If I could get adb to recognize my device, then I could push the build.prop file and everything would be fine. I'm really stuck here.
Best solution would be getting adb working correctly and pushing the stock build.prop
Do you have any idea why the adb might not be recognizing my device? I wouldn't need to have the bootloader unlocked for adb would I?
I ensure I have right drivers in a folder and not to always use installers, attach device then (on windows) use system/hardware manager and remove the device it is showing as, close device manager, detach device, re-attach the device when asked to install drivers select manually this will then install ALL the drivers required (I found genuine installer didn't install correctly or was fixed so not for users use only programs use) it should pick up your device on at least i'd guess x2 USB ports.
No bootloader etc needs adb to work to unlock it via USB
Rooted Xakep E320/C6 EUU Hacked Update
Try forcefully restarting the tablet. Hold the top power switch and the volume-down until it shuts off. Restarting often helps me with any problems I'm having. It may help your computer recognize the tablet if you keep it attached. And maybe restart your computer, windows is notorious for stuff like that.
Thanks all for the replies. Here's what's going on. I've reinstalled the drivers and the computer recognizes the device now. You can see from the attached image. Am I doing something wrong in my push command that is keeping the pc from pushing the file?
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
How about trying https://play.google.com/store/apps/details?id=lv.n3o.lcddensity&feature=search_result or any other similar app from the Play Store?
superuser has quit responding anytime that I try to run one of these apps. I can't allow permission so the app won't work. This really sucks. I wish I could just figure out why I can't push the file through adb.
UPDATE:
I fooled around and managed to navigate to the play store without unlocking the screen. Upon doing this, I got into superuser and then allowed the lcd changer app to run. Then I ran the app and it rebooted my tablet and it's back to normal. Thanks for all the tips guys. I am no longer in the dog house.
jbrowning37 said:
UPDATE:
I fooled around and managed to navigate to the play store without unlocking the screen.
Click to expand...
Click to collapse
Just out of curiosity: How did you manage to do that? Is it possible to control the device like that from ADB?
No, even with the screen locked I could pull down the notification bar. When it said "installing adobe flash player" I clicked it and the market opened. I would have been screwed had I not been able to do that.
You shouldn't run the "adb shell" command and then "adb push ....", you should push the file without you go into shell.
Not sure if that was really causing your issue or not, but it could be.
Related
Guys I'm at my wits end. I'm about to give up. I'm trying to get adb working on the nook here on my work computer. I can't for the life of me get it to work. I had no problem on my laptop, but then again I think I caught it before windows installed anything.
I've been using "usbdeview" to uninstall rogue drivers, trying to reel in the problem. However every time I go into device manager, it try's to install "Android ADB interface" which I think means its assigning the wrong driver to it. It should be "Android Composite ADB Interface", no? I know thats what it is on my laptop.
Anybody have any last ditch efforts? I should note that adb works perfectly fine on my Aria on this same machine. I love ADB, hate the setup though.
*****EDIT: Working on different usb port*********
You aren't alone, m8.
I used to have no problem with ADB over USB. But after re-formatting my laptop, I just couldn't get it to work, no matter what I did. I gave up
I'd tried wireless ADB, everybody said it's so easy, me? Couldn't ever get it to work. Gave it also.
At least, for now, I wouldn't think I need it.
I'm now convinced its not driver related. There is something holding my computer back from talking to it. But I'm 99% the right drivers are installed. Mounting disks works fine and it identifies like my android phone does, ADB just won't talk to it.
Try unchecking and rechecking Debugging mode...
Tried that many times. Just for fun I ran the easy adb executable on another machine here, THEN plugged in my nook to it. ADB worked perfect. I'm frustrated, but I really want to figure this thing out. (btw, it identifies with the exact same drivers on both machines)
EDIT: Don't know why or how, but for some reason switching usb ports (which I swear I've done before) worked!!!!!!! It now recognizes and can push/pull/install over adb (usb).
WWW.Ubuntu.com
Enough said.
Love me some Ubuntu, but CMD prompt > Terminal every time.
If you don't mind, can you provide the link to where you downloaded the driver?
Thanks
I used the "combo" pack which installed the drivers and a stripped version of ADB to C: (redundant since I already had ADB installed).
http://forum.xda-developers.com/showthread.php?t=910008
Thanks audio,
I'll give it another try.
DISCONNECT YOUR COMPUTER FROM ANY NETWORK TO AVOID WINDOWS UPDATE GOING ONLINE AND INSTALLING INCORRECT DRIVERS
Make sure you're Nook is identifying like this when its plugged in via device manager. If you're unsure how to get here; WINDOWS KEY + R, type without quotes "devmgmt.msc", hit ENTER.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Note: You're drive letter's under 'Portable Devices' may vary from mine, that's fine. Just make sure they are there.
DISCONNECT YOUR COMPUTER FROM ANY NETWORK TO AVOID WINDOWS UPDATE GOING ONLINE AND INSTALLING INCORRECT DRIVERS
I got all those except the Disk drive list above.
I'll give a try and see what happens.
We may need to uninstall some old drivers before we can get it to install the right ones. You on gtalk or msn? I'll help you troubleshoot it the best I can.
Works like charm.
LOL , without this thread, I would (actually I did) abandon installing ADB over USB.
Thanks audio for providing the correct link.
Gotta love this forum.
So I had the magical luck of having my S4 fall out of my pocket while closing my car door, shattered to pieces, no touch response from the glass.
The problem is, I had the device locked with a pattern & pin, so I can't just plug in and backup all my photos and stuff that were saved with local device storage. I also can't get adb to connect to the device (with developer options enabled), I always get a "device offline" error (I've updated ADB to the current 4.2.2 version, but I cant whitelist it because I can't allow it from the phone without touch)
Now, I still have root, and I was able to blindly install CWM (the OUDHS-Recovery-jfltespr-1.0.3.3.tar) version with Odin. I'm assuming it went well because I heard the sprint chime on restart.
WHAT I NEED: Is someone to either give me some screenshots (or number of button presses) to enable internal storage to be accessible by usb in cwm (also how to get into it too). I figure if I'm able to use volume presses and the home button I can get to my internal files. Other than this option I'm at a loss before I return it. If anyone can help I would be so damn grateful.
I'll draw you a picture too.
EDIT 1: I have a picture of the main CWM screen from a youtube video here:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Now all i need is the mount and storage menu
So nobody can help? I didn't think a cwm menu was that hard to come by with an S4.
alexcu said:
So nobody can help? I didn't think a cwm menu was that hard to come by with an S4.
Click to expand...
Click to collapse
Were you able to connect with adb before? Was usb debugging checked in settings before the drop?
If you could get adb to connect, you could use a program like android screencast to view your phones screen on your computer.
fgr said:
Were you able to connect with adb before? Was usb debugging checked in settings before the drop?
If you could get adb to connect, you could use a program like android screencast to view your phones screen on your computer.
Click to expand...
Click to collapse
That was my first move actually.
Problem is, even though debugging was enabled, I can't whitelist my PC from my phone. This is a new 4.2.2 feature to prevent data theft ironically.
All of these options will just return an "adb: device offline" error when it's connected. Trust me, I wish it was that easy.
You can't connect while in recovery either?
It would be kind of a pain, but you could pull multiple files that way.
Look HERE
Hello
Sorry if this was a very noob topic
I done lots of flashing new ROM or back in stock process but i almost gave up this time
My phone status are
No OS
TWRP installed
Can boot to recovery
PC can't recognize the phone
Typing ADB devices shows empty list
Typing Fastboot devices also shows empty lines
30% battery left
I recently try to install the Lollipop version for my phone but it turns out that the zip are behaving like OTA (yep the title of the zips are OTA)
What i mean is it returned my recovery to stock
Without thinking much further i did 'fastboot flash recovery TWRP2810.img' thing (Yes i rename recovery image that way so it will be more convenience for me) and wipe all partition in the phone through the TWRP without problems
One thing i forgot is to "refresh" all ADB and Fastboot driver for my phone on the PC
Now my phone states are "No OS" and "PC doesn't recognize my phone" wether in ADB (obvious cause i can't boot with no OS so no USB debugging for me) and Fastboot (Enter Bootloader is OK, enter TWRP is OK too)
I already try the WUG step for installing the needed driver but no success since my PC can't recognize my phone
Try on 4 PC at my office and all of them are ignoring my phone
What should i do now, please, any help will be appreciated since its already the time i ussualy already at home
Thank You Very VERY MUCH for any help I can get.
unsungkhan said:
Okay, here's what you do.
Download the ADB drivers first, from here [URL="link"]http://developer.android.com/sdk/win-usb.html
Click to expand...
Click to collapse
unsungkhan said:
Extract the zip.
Once you're done extracting, boot your phone into bootloader mode, plug in USB, should show up as an unrecognized device.
Device manager from control panel, select device, properties, driver, update device driver, browse my computer, let me pick, all devices, have disk, navigate to where you extracted zip, select inf file, adb interface.
Should work.
Click to expand...
Click to collapse
[/URL]
Thank you Sir
I managed to fresh install my XP and continue with your instructions
I don't know why but it gave me this
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I already try other driver but still a no go?
Do you happen to know other way around for tricking this Sir?
Please lock this unuseful thread
Before locking the thread, can you repeat all the steps and try with ADB Composite Device instead of ADB Interface?
Also, did you try changing USB ports, sometimes these things get a little troublesome because of faulty USB ports.
Last but not the least, you could also try a change of cables.
unsungkhan said:
Before locking the thread, can you repeat all the steps and try with ADB Composite Device instead of ADB Interface?
Also, did you try changing USB ports, sometimes these things get a little troublesome because of faulty USB ports.
Last but not the least, you could also try a change of cables.
Click to expand...
Click to collapse
#late_post
i've been able to resurrect my phone finally
after those steps i found Universal Naked Driver and it works
Thank You very MUCH Sir :laugh:
Hello.
I've repaired a nexus 4 screen and digitizer but I got it back because my friend can't recover access from a forgotten pattern lock.
He is running stock android 5 lollipop and he doesn't get the email recovery option when he inputs wrong pattern. I've searched even in google support but I didn't find a solution to recover his photos.
My main concern is to recover files and photos!!! There isn't a reason to suggest a factory reset....
--Phone Status---
Boot loader seems unlocked "Locked state is marked as unlocked in bootloder in red letters" while secure boot is enabled in green letters
USB debugging seems OFF: There is no android device listed in device manager. I only get a music player in disk drives which is empty.
adb devices command in bootloader recognises it
When entering to recovery I get the message "no command" along with the icon of an android under repair.
No dropbox no google+ photos backup
---What I've tried---
UPDATE: Managed to flash TWRP 2.7.1.0 I can see the files but since usb flash drive doesn't work I can't copy the files...
Android Device manager: Returns error that the phone is already locked and there is no need to apply new password.
Tried about 30 wrong patterns and it didn't came up the google mail recovery option.
Tried during a phone call to see the files but I only managed to turn on WiFi.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
When you say the USB flash drive doesn't work, do you mean the USB port in the phone?
MTP doesn't always work in TWRP, meaning it won't show up as a normal usb drive on a pc. ADB will still work though, you have to set up ADB on your computer, boot into twrp on the phone and use 'adb pull' to copy the files to the computer. On windows you will need to download adb and the drivers, I use http://www.koushikdutta.com/post/universal-adb-driver
I'm trying to install the drivers for adb but I cannot find the right one.
Edit: Also it cannot be detected from boot loader now. I'll try in a pc that already has been connected and worked.
I have adb and fastboot installed already and worked with this and my own phones.
Edit: It seems to be a lost cause the phone fell down many times. Don't bother maybe I'll solder a usb port first... if it is possible with my less than basic equipment.
There are many methods on the following page,
http://forum.xda-developers.com/showthread.php?t=2620456
The way I did it was an alternative version of method 5 while in twrp.
Method 5 - alternatively, Mount system in twrp and delete the file /data/system/gesture.key
If it asks for a pattern on boot just try any random pattern it should let you in. I did this when a version before lollipop was installed but there is no reason it shouldn't work on lollipop as the same file is saved in the same location, just checked.
Using adb
adb shell rm /data/system/gesture.key
Click to expand...
Click to collapse
Hello all,
I recently started to get lots of popads on my device, so I ran my usual scan with Malwarebytes and it came up with KingRoot being heavily infected with malware. I cant uninstall, since its what i used to root and its also a system app. Any help?
loganwaffle8 said:
Hello all,
I recently started to get lots of popads on my device, so I ran my usual scan with Malwarebytes and it came up with KingRoot being heavily infected with malware. I cant uninstall, since its what i used to root and its also a system app. Any help?
Click to expand...
Click to collapse
see rootjunky's supersume video
https://www.youtube.com/watch?v=3O3DcpeS_Ic
or manually install supersu with a terminal emulator
http://www.w0lfdroid.com/2015/05/How-to-Remove-Replace-KingUser-KingRoot-with-SuperSU.html
Ill try the rootjunky method in a few hours, I tried the terminal emulator installed and it just forceclosed all apps and rebooted.
Sent from my KFTBWI using XDA Labs
So I got a bit impatient, and decided to retry the w0lfdroid method. The same thing happened from last time (apps wouldnt open) and so I decided to reboot.
As the device began to shutdown, SuperSU appeared for a few seconds, then my device switched off. I believe I have bricked my device as it has been stuck on the 'fire' logo for the past 10 minutes. Congrats to me ._.
I tried to install adb and its drivers, however drivers wouldnt install saying 'windows couldnt find any driver software for you device' when i point it to the drivers. Any idea why?
loganwaffle8 said:
I tried to install adb and its drivers, however drivers wouldnt install saying 'windows couldnt find any driver software for you device' when i point it to the drivers. Any idea why?
Click to expand...
Click to collapse
Download kindle_fire_usb_driver.zip from Amazon site
Connecting Your Fire Tablet for Testing or XDA
extract files
run KindleDrivers.exe
Then manually select drivers
Open device manager Settings>Devices>Device Manager
Connect Kindle Fire
Enable USB debugging
(If Kindle is not listed as Android>Android Composite ADB interface)
select Other Devices>Fire
Right Click>Update Driver Software
Browse my computer for Driver Software
Let me pick from a list of drivers on my computer
select Android or Android Phone (or ADB Interface or Android Device)
Select Android Composite ADB interface for Stock rom or recovery/adb sideload
Select Android ADB interface for Fastboot mode
or Android Composite ADB interface
next
you may have to reboot pc
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Sent from my KFFOWI using XDA Labs
Thanks
Have I done it right? I hope I've done everything. Also when I open ADB a load of text flashes down the cmd box for about a second then it closes. Ran as administrator and everything. Hoping I can get this fixed by the weekend...
Ok, I think I got it.
Doing adb devices gives me G000HH0454340LB9, I beleive this is the correct device?
Anyways, plan is:
Boot into recovery on device and select apply update from adb
Get the 5.1.1 update (firmware it originally had) and place it in the folder adb installed in.
Do adb sideload (file name)
Wait (maybe grab a cup of coffee?)
Hopefully success, back to stock firmware!
Afterwards ill root with kingroot and then remove using rootjunky supertool.
Ok, this is getting kinda annoying.
Placed the update-kindle-32.5.4.1_user_541112720 .bin file in the same folder I have adb installed.
Booted devices into recovery mode, selected apply update from adb
Open adb, do adb sideload update-kindle-32.5.4.1_user_541112720
Get error message 'cannot read update-kindle-32.5.4.1_user_541112720'
Have ALL correct drivers and stuff installed @sd_shadow
Can anyone help? I really need this fixing...
loganwaffle8 said:
Can anyone help? I really need this fixing...
Click to expand...
Click to collapse
try downloading the firmware again, or try a different version like 5.1.2
which version is on it now?
Sent from my KFFOWI using XDA Labs
The version on my device before it was bricked is 5.1.1. I'm staying on that version since its the easiest to root.