I missed my android phone with Google apps Rom Toolbox Pro. I set the screen density from 306 to 106. My phone is Samsung I9300. It's MTK processor phone . Now I can't open the launcher after the screen lock. When I swipe the phone to left or to right, it says "Touchwiz is not responding" . It keeps prompting that message over and over again. I already set the phone to its factory reset using android recovery, so theres no way that I can connect my phone to my pc because the usb debugging is already turned off due to factory reset. If i could just enable the phone usb debugging, that will lessen the problem. Please help me. There is also another solution using the notepad, and if i could browse the build.prop file inside the system folder, I can edit the screen density back to 306. But as I said, usb debugging is turned off.Anyone out there who knows the solution to this, please help me.
Related
I was using Gingerbread 2.3.4 and enter the Software Update option on the Settings Menu.
There was a Software Update available and started downloading, then it began to install, until it was finished. After rebooting itself, the initial "Samsung Galaxy SII GT-I9100" screen appears (since is rooted, appears with the Warning signal also) and it won't go beyond that screen.
I tried Recovery Mode, Wipe cache, Wipe Data/Factory Settings, etc, and it won't go further.
I download Heimdall, detects the device, but when it tries to connect, it says that there was an error "Claiming Interface Failed!". I search for an error like this one, and turns out the USB Debugging has to be ON in order to access the device when connected to the USB port.
Since I cannot get by the initial screen, I cannot set ON the USB Debugging option.
Is there a way to enable this from a Terminal or Command window? I am using Mac OS X.
Any help? I searched the website without any luck.
Thanks a lot!
I returned my phone to stock, forgetting I uninstalled the phones launcher.
The phone is an AT&T MB511 Motorola Flipout.
I want to install the ADW launcher, but theres no way for me to get to the setting menu, to enable USB debugging, to install the launcher.
I've seen posts that have instructions on how to get into safe mode on some phones. I'm not sure if my phone has that function.
BTW the capacitive buttons and the keyboard do nothing.
a_rocklobster said:
I returned my phone to stock, forgetting I uninstalled the phones launcher.
The phone is an AT&T MB511 Motorola Flipout.
I want to install the ADW launcher, but theres no way for me to get to the setting menu, to enable USB debugging, to install the launcher.
I've seen posts that have instructions on how to get into safe mode on some phones. I'm not sure if my phone has that function.
BTW the capacitive buttons and the keyboard do nothing.
Click to expand...
Click to collapse
try if you are able to get to the USB debugging settings via pressing the menu button at your homescreen.
otherwise you can try to start the adbd in the recovery mode.
this might work but i heard from people who disabled usb debugging and crashed theyr system
afterwards they wanted to flash it back via adb but adb didnt recognize the phone cus usb debugging was turned of
Hi there,
I have a samsung galaxy s3 i9300 with broken display and I need to run a software to recover deleted files on the memory of the phone. This software requires to doo usb debugging to the phone in order to do its job. I was already able to enable it changing buold.prop using adb in recovery mode. Now the phone waits for the user to touch the "ok" button in order to allow the pc, unfurtunately my display is broken so I can't do it. Do you have any idea on how to let the phone accept adb/usb debugging connections from my pc, or to completely disable the confirmation box and accept the requests automatically?
Does your touch screen still register touch? If so, I'd try borrowing same model of phone from a friend, connecting it to computer to see where exactly is the OK button, then try to tap same location on the broken screen of your phone>
Device: Samsung Galaxy Tab 4 8.0 (SM-T330NU, Region XAC)
Odin version: 3.09
Root file: CF-Auto-Root-milletwifiue-milletwifiue-smt330nu.tar.md5
First, I did a factory reset from Settings>General>Backup and reset>Factory data reset. Before this, I had developer mode enabled and the "allow USB debugging" option checked, but I forgot to redo these steps after factory resetting.
Then I proceeded to root it and everything went as normal, I've been using it for a few days now and I actually only just realized that I had forgotten to enable USB debugging mode before rooting. So now I go to the settings of my already-rooted tablet, developer mode is of course disabled so I enable it, I see that the USB debugging checkbox is unticked so I tick that.
How come the rooting didn't go horribly wrong and brick my tablet as it seems to have for most other people?
So far I've been removing bloatware, using screen mirroring, browsing, managing files, using SuperUser, installing and using a bunch of apps from the Play store, and everything works perfectly. But I'm thinking about re-rooting with all the proper steps; I've never made this mistake before and if I leave it as it is, what kind of problems might I run into later?
(Sorry about the double post! I couldn't figure out how to change forums or delete my original one.)
Usb debugging does need to be enabled if you're using odin to flash something in download mode
Sent from my SM-N920G using Tapatalk
I have a Verizon SCH-I435 gx4 mini and I forgot my pin. Android device manager can't help me put it into lost mode and over ride screen lock. The interesting part is when I boot into recovery and go to factory data restore as a last option it says it's in display mode (MTM). The phone boots into Odin mode just fine. On all my phone I always turn on USB debugging which I believe if you have a pc you need to enable to use Odin correct me if I'm wrong. So if there's a way to keep my files safe and use my phone again it would be appreciated.
pk198 said:
I have a Verizon SCH-I435 gx4 mini and I forgot my pin. Android device manager can't help me put it into lost mode and over ride screen lock. The interesting part is when I boot into recovery and go to factory data restore as a last option it says it's in display mode (MTM). The phone boots into Odin mode just fine. On all my phone I always turn on USB debugging which I believe if you have a pc you need to enable to use Odin correct me if I'm wrong. So if there's a way to keep my files safe and use my phone again it would be appreciated.
Click to expand...
Click to collapse
Let's make Points
1-Odin Doesn't require any USB-Authentication such as Debugging Enabled
2-Only adb Requires Debugging
3-Great Thing you enabled it.
Now you can Apply two ways.
One you can boot into recovery and go into adb.Now on PC install adb and connect it to your phone(Go read a Tuto or watch a Video on how to do it)Now remove the locksettings.db file from /data partition(Use google to find the exact location)
Or you can pull the locksetting.db copy to your PC and crack the code using hashcat.But I recommend the first one.Next Time be cautious and if you don't know how to delete files using adb go read how to.
Sent from my Pixel 3 XL using Tapatalk