How to enable adb after wiping system and installing new kernel? - android

I have a Nexus 4. I accidently wiped system and tried to restore it unsuccessfully.
I did have adb before I wiped the system. Now I can only get into recovery mode. When I use Nexus root toolkit it recognizes the device only in bootloader but it can't recognize it as adb device. I thought maybe now that Android is not installed USB, debugging is disabled as default.
Do I have a way to enable it or do you have any other solution? I can't use the device. Do I have any other way to install Android without adb?

adb isn't required (adb is only one of the ways to do it. As long as you still have access to recovery mode, you're golden).
Just get the zipped image you want to install (a modded one, or the official one). You should be able to get the official one from google since it's a Nexus 4. Do not unzip it.
Connect your phone to your computer as a usb drive. Copy the zip file to the root of your internal sdcard on your phone.
Reboot your phone into recovery mode. Then navigate the menu on the phone with the sound rocker and the power key to tell it where to find the new location of the new image.
Then reboot normally. I'm writing this from memory. If you want more specific instructions, I can provide them if you want.

Related

ADB - Empty list of devices when running 'adb devices' command

I've a Honor 10 View Lite with a broken screen (it's not usable) and I would try to recover data from it.
Following some tutorials it seems possibile to do that with ADB and the phone in recovery mode (holding power button + volume up).
I've installed ADB drivers through UniversalAdbDriver.msi and Fastboot version 1.4.3 Portable on Windows 10.
Being the screen black it's difficult to understand if the phone reboot in custom recovery mode or in normal mode, but when I open shell on the same folder of Fastboot and type 'adb devices' no device is found. I've also tried connecting another phone in recovery mode (Huawei Mate 10 Pro perfectly working) but the problem is still the same, no device found.
What can be the problem? Some wrong or missing installations?
I also have to specify that both the phones have USB debugging disabled and I hope this is not a problem because in the broken phone it's impossible to find a way to enable it. That's also the reason why I'm trying to recover data through ADB and not through programs like FoneLab and so on that required USB debugging enabled.
I will also accept advices on solutions different from ADB to recover data in these conditions, if they exists.
Thank you
I don't think adb will work for this unless usb debugging is enabled. At least, the device might show up in "adb devices" list, but it would show up as "unauthorized" and you wouldn't be able to pull data off it.
What kind of data are you trying to retrieve? Don't suppose you have cloud backup?
If it's just the screen that's broken maybe you can find a way to mirror the screen onto an external display somehow.

Install application update without uninstalling it

So I have a parasite application installed on the phone that blocks the device from booting to bootloader and bunch of other stuff. It is also set as a device administartor thus it can't be uninstalled (deactivate administartor rights is also impossible). So to fix this problem I decompiled the APK of this app and changed the code so I can deactivate the admin rights. Unfortunately recompiled APK can not be installed over the existing application.
Adb error:
INSTALL_FAILED_UPDATE_INCOMPATIBLE
So is there a way to force install the app without uninstalling it? Or if my approach is wrong can you advice me on how to get rid of this annoying app.
Unfortunately recompiled APK can not be installed over the existing application.
No, because you have no access to former key that was used to sign the installed the parasite APK package.
If your device is rooted then you can try to boot to recovery like TWRP and carefully mess with system partition removing/editing files to prevent this particular app from starting (should suffice to simply remove its folder).
it blocks the device from booting to bootloader
How it does so? Most devices offer certain key combination (i.e. hold volume up + power) to boot in other modes, so unless you got it on very low level you can try that way.
So to fix this problem I decompiled the APK
If possible, I'd first backup my data (if there's any you want to backup) and simply factory reset the device. May save you some time.
EDIT
Idk how exactly it blocks the bootloader but it does (holding power, home, volume down just restarts the device)
You can always try to reboot to recovery/bootloader using adb:
adb reboot [bootloader|recovery]
- reboots the device, optionally into the bootloader or recovery program.

Generic USB Mass Media Drivers getting in the way of drivers for ADB

I was able to install the correct Android drivers on my Windows system so that it synced up with adb and the Android SDK and I was able to run and debug programs on it through Eclipse and Android Studio. It was going fine for a week or so but today my device will only be recognized as a "USB Mass Media Storage" device and will not be recognized by adb. (I'm sure something was changed, but I have no idea what.)
-Whenever I try to reinstall the drivers that were working before I get "The best driver software for your device is already installed." Whenever I uninstall the driver, the computer immediately reinstalls the Mass Media Storage drivers before I have any time to react even though I have disabled automatic driver updating (or at least the option in System menu). By choosing the "Let me pick from a list of drivers" option and browsing to the driver's .inf it will let me install it as either an ADB Interface or a Composite ADB Interface, but though it claims to install successfully, nothing works; ADB never finds a device, the device never says that anything is asking for debug permision (like it did before). And considering that before both interfaces were shown in the Device Manager, I'm confident the driver isn't being installed correctly.
I feel as though there is a corrupt driver or registry that I need to delete but I have no idea how I'd locate it.
I've tried revoking USB debuggin authorization, then wiping the cache partition in my device, then restoring it to factory settings to no effect.
Yes, the USB debugging option has been on the whole time.
Apparently even though the developer options were still visible, I had somehow ceased being a developer on my phone. The solution was to reinstate developer mode by tapping the build number 7 times.

Backup android to ubuntu from recovery mode

I have - stupidly enough - updated my android phone to the newest 5.0 Lollipop. The update went bad and many hours later the phone is still unresponsive. I can only enter in a recovery mode. I have seen in forums that many other users had the same problem and it turns out that the only way out is factory reset of the phone. This means total loss of phone data. As I have no backups (as far as I am concerned) I was wondering if there is a simple way to transfer the data from phone to computer (Ubuntu) while phone being in recovery mode.
This is what I tried already:
started the phone in recovery mode
selected the 'apply update from ADB' (as this is apparently the only way computer sees the phone through $ adb devices)
I type
$ adb devices
List of devices attached
02452a1acc14c9d4 sideload
and then
$ adb backup -apk -shared -all
adb: unable to connect for backup
My phone was not rooted, but I am pretty sure the USB debugging was activated. Any ideas? Is it possible at all to backup phone in recovery mode?
Thanks in advance.
Helps to know what phone you have. You could look for the key sequence needed to boot into recovery mode. I'd look into flashing Clockwork Mod recovery which can mount the phone over USB while in recovery. There you could copy a new ROM zip to flash over the messed up Lollipop rom.
All you have to do is format /system and install a known working ROM. Also, Clockwork mod recovery can make a nandroid backup which can be looked at using Titanium Backup so you can extract your data that way.

How to make sumsung galaxy tab 3 device rooted

I want to make my sumsung galaxy tab rooted. But I have no idea how to do it? I have google so much but don't get any perfect solution or answer.
Please help me how can crack this problem.
Thanks in advance !
. Before You Begin
1. This will void the warranty of your device. However, you can reinstate the warranty by unrooting your device if there’s any unrooting procedure available.
This procedure only works on Windows based PCs.
II. Downloading Required Files
1. Download Odin and save it to your Desktop.
Odin
Download CWM Recovery and save it to your Desktop.
CWM Recovery (It’s attached in the first post)
Download Universal Root ZIP and save it to your Desktop.
Universal Root ZIP (It’s attached in the first post)
III. Flashing a Custom Recovery on the Samsung Galaxy Tab 3 7.0 (Sprint)
1. Extract files from both Odin and CWM Recovery by right-clicking on each of them and selecting Extract here.
Double-click on Odin executable and it should launch.
Click on PDA and choose the CWM Recovery that you just extracted to your Desktop.
Make sure Repartition is unchecked in the Odin.
Uncheck the Auto Reboot option as well.
Turn OFF your device.
Turn it back on by holding down Volume DOWN+Home+Power buttons together.
Press Volume UP and you should be in Download mode.
Plug in your device to your PC using the USB cable.
Hit Start in the Odin and it’ll start flashing the recovery on your device.
Once done, reboot your device.
You’re done!
IV. Rooting the Samsung Galaxy Tab 3 7.0 (Sprint)
1. Connect your device to your PC via USB cable.
Copy the Universal Root ZIP from your Desktop over to the root of your SD card.
Once it’s been copied, disconnect your device from your PC.
Turn OFF your device.
Turn it back on by holding down Volume UP+Home+Power buttons together.
When the Samsung logo appears, release the Power button but keep holding the other two.
You should now be in Recovery mode.
Select install zip from sdcard followed by choose zip from sdcard.
Choose the Universal Root ZIP to be flashed on your device.
It should start flashing the ZIP on your device.
Once it’s done, reboot your device.
You’re now rooted!
All set! Now, you can head to our How to Flash a Custom ROM procedure for the Samsung Galaxy Tab 3 7.0 (Sprint) to open up a whole new world of customizations for your Android device!
By the way, don’t be scared, you can always put your device back to stock by heading to our Rooting How To’s section, finding your device, and doing the How to Unroot listed for it there.

Categories

Resources