Ok so here is my problem. I broke my screen before i had usb debugging enabled, ADB, root, CWM or TWRP recovery or anything like that. I need to be able to access my phone, not just the data. I know there is software that can extract the data, but i want to be able to control my phone with my computer. I have heard that in order to do this i should "contact a kernel developer to automatically enable it in the default.prop and sideload the kernel in recovery!....i enabled adb via the default.prop and compiled the kernel and flashed in recovery(sideload). now i have full control over the device.". Can anyone do this? I am kinda desperate.
Related
Alright here is my situation. I ran the latest OTA update on the stock rom and the phone started going into
a boot loop. My problem is that I havent performed a recent backup and need to access some files on the
phone. Developer mode is enabled, however I disabled USB debugging prior to running the update. When my
phone reboots, I remove the battery and restart the phone but every once in a while my phone successfully
loads and I am able to punch in my pin to unlock the phone. However, a few seconds later the phone reboots.
I tried to access the phone using ADB but because I dont have USB debugging enabled I dont see any devices
when I run the "adb devices" command. I also tried to acquire a smartphone image using encase forensic, but
yet again, because USB debuggin is not enabled, I am not able to pull data.
I am able to go into recovery mode and I tried to wipe my cache partition, but that did not help.
My questions are:
1. Is there a way for me to access my data files while the phone is stuck in a boot loop and USB debugging is
disabled?
2. Is it possible for me to download the latest update, copy it over to my sdcard and rerun the update from
my sdcard from recovery mode? Could this possibly solve my problem?
3. In a worst case scenario, if I do a factory wipe/reset, will this solve my problem and what is the
likelyhood of recovering my files from the data partition?
Any tips, tricks, advice is greatly appreciated.
tparnet said:
Alright here is my situation. I ran the latest OTA update on the stock rom and the phone started going into
a boot loop. My problem is that I havent performed a recent backup and need to access some files on the
phone. Developer mode is enabled, however I disabled USB debugging prior to running the update. When my
phone reboots, I remove the battery and restart the phone but every once in a while my phone successfully
loads and I am able to punch in my pin to unlock the phone. However, a few seconds later the phone reboots.
I tried to access the phone using ADB but because I dont have USB debugging enabled I dont see any devices
when I run the "adb devices" command. I also tried to acquire a smartphone image using encase forensic, but
yet again, because USB debuggin is not enabled, I am not able to pull data.
I am able to go into recovery mode and I tried to wipe my cache partition, but that did not help.
My questions are:
1. Is there a way for me to access my data files while the phone is stuck in a boot loop and USB debugging is
disabled?
2. Is it possible for me to download the latest update, copy it over to my sdcard and rerun the update from
my sdcard from recovery mode? Could this possibly solve my problem?
3. In a worst case scenario, if I do a factory wipe/reset, will this solve my problem and what is the
likelyhood of recovering my files from the data partition?
Any tips, tricks, advice is greatly appreciated.
Click to expand...
Click to collapse
Boot phone into recovery mode. You can access phone now and make backup or download need files to PC.
svs57 said:
Boot phone into recovery mode. You can access phone now and make backup or download need files to PC.
Click to expand...
Click to collapse
Thanks svs57 for the quick reply.
Would you mind elaborating a bit more? I am an IT guy but by no means a developer. When I boot into recovery is the phone supposed to show up in My Computer via MTP or PTP? The phone is not showing up as a device. Or am I supposed to use adb commands to pull the files down?
When I go into recovery and run the "adb devices" command now I get what appears to be a serial number followed by the word "unauthorized". I rebooted and went into recovery mode again this time tried "apply update from ADB". When I try using either the adb push or adb pull I get "error: closed"
Thanks again for the help.
You have to use latest version of adb. Then you can login to phone via adb and find file you want to backup. Then use "adb pull" to get file to PC.
If you have custom recovery you also can make backup you data using recovery.
Also you can flash the same ROM you have without wipe data.
Hi there.
I have a Nexus 4 with a failed root through Nexus 4 Root toolkit.
The toolkit unlocked the bootloader with no problems but it failed at applying SuperSU-v1.45.zip through ADB through CWM
I am pretty certain that this process failed because I did not Enable USB debugging before starting.
So, I think the question I want to ask is: Is it possible to Enable USB debugging so I can apply perform adb sideload SuperSU-v1.45.zip
Do I have any other options? At present the device won't boot into Android OS. The states I currently have are either
1. fast boot mode
and then Recovery Mode -> CWM
2. Just a black screen, the Google logo, and an unlocked padlock
Any pointers would be greatly appreciated
Thanks!
jon.
Why CWM? TWRP is a lot better.
And Android USB debugging has no job in recovery so it isn't necessary if you're sideloading
Oh, and a few extra bits of info:
* I am on a mac
* I am pretty sure it's the adb ruining the party because when I do this:
(null) latform-tools jonwhittlestone$ adb devices
List of devices attached
(null) latform-tools jonwhittlestone$
Ahh thanks Lawstorant. Maybe my question isn't warranted then, or I'm barking up the wrong tree with ADB/USB debugging. Needless to say, I didn't enable it and surely this is not going to stop me rooting?
How can I get replace CWM with TWRP bearing in mind I can't get into the OS anymore - I'm a total Android root newbie as of this morning?
jonwhittlestone said:
Ahh thanks Lawstorant. Maybe my question isn't warranted then, or I'm barking up the wrong tree with ADB/USB debugging. Needless to say, I didn't enable it and surely this is not going to stop me rooting?
How can I get replace CWM with TWRP bearing in mind I can't get into the OS anymore - I'm a total Android root newbie as of this morning?
Click to expand...
Click to collapse
You shouldnt have used a toolkit.
Anyways, i think that you are misunderstanding this. You DO NOT need usb debugging enabled for adb to work while in a custom recovery. Adb works by default in a custom recovery.
I would suggest pushing a rom onto your phone (download a rom on your mac, put the phone into cwm, and run "adb push rom.zip /sdcard/").
After that go back to the phone and choose: wipe data/factory reset, wipe cache partiiton, advanced> wipe dalvik cache. Then go to install zip from sdcard and install the rom that you just pushed.
*Download the newest TWRP .img file from TWRP website
*Rename it to recovery.img to get rid of that long name
*Go into bootloader but don't choose anything (fastboot mode)
*In ADB type: fastboot flash recovery file_location/recovery.img
Sideloading in TWRP is in Advanced menu
consonant edbreach
Chromium_ said:
You shouldnt have used a toolkit.
Click to expand...
Click to collapse
Thanks Chroumium_, the procedure is becoming clearer. I should have known better to use a toolkit for sure.
I had actually followed Lawstorant's advice and put on twsrp, nevertheless - when I try to push a zip with adb, I get the following
(null)latform-tools jonwhittlestone$ adb push cm-10.2-20130815-rootandboot-mako.zip /sdcard/
error: device not found
Is this because I don't have the correct Nexus 4 drivers? The way I've always handled File transfers is with Android File Transfer so presumably I have go the correct drivers.
I am guessing if I had removable media, I could have put the zip on that...
jonwhittlestone said:
Thanks Chroumium_, the procedure is becoming clearer. I should have known better to use a toolkit for sure.
I had actually followed Lawstorant's advice and put on twsrp, nevertheless - when I try to push a zip with adb, I get the following
(null)latform-tools jonwhittlestone$ adb push cm-10.2-20130815-rootandboot-mako.zip /sdcard/
error: device not found
Is this because I don't have the correct Nexus 4 drivers? The way I've always handled File transfers is with Android File Transfer so presumably I have go the correct drivers.
I am guessing if I had removable media, I could have put the zip on that...
Click to expand...
Click to collapse
Im pretty sure that mac doesnt require any drivers to be installed. Try running these commands first:
Code:
adb kill server
adb start server
Also make sure that your adb is up to date (using the sdk manager). If its still not working try other usb ports or cables if you have any.
At this point adb is the only way to move the zip onto the phone, since the nexus 4 doesnt not support usb mass storage.
Chromium_ said:
Im pretty sure that mac doesnt require any drivers to be installed. Try running these commands first:
Code:
adb kill server
adb start server
Also make sure that your adb is up to date (using the sdk manager). If its still not working try other usb ports or cables if you have any.
At this point adb is the only way to move the zip onto the phone, since the nexus 4 doesnt not support usb mass storage.
Click to expand...
Click to collapse
Thanks to both - I've now solved and rooted
I reflashed with the stock google image
Followed androidpolice.com/2013/07/24/how-to-flash-your-nexus-4-to-android-4-3-jwr66v-and-root-it-right-now/
And - got the official TRSW from Gooapps on the Market
Flashed the SU update using the shell script - all details in the link above.
current supersu is 1.65
Can i enable usb debugging via locked phone [pin screen lock]
ok so i have a phone its an lg k5 or in mexico lg q6 a friend has asked me to unlock it with out doing any kind of hard reset or format so he he can access the pictures and other things on the phone since it belongs to his brother who passed away. anyways does anybody know of any way i can enable usb debugging so i can reset the lock screen via ADB ?? or maybe some other way?
Hi Folks:
i have read many threads on this problem and how to resolve it but bear with me as I am a newbie.
I have a nexus 4 with bootloader unlocked and USB Debugging disabled. I am looking for some step by step advice on how I would be able to enable usb debugging so that i could access my phone remotely to reset the lock pattern and backup my information. I have adb running on a windows PC and I know how to access stock recovery mode. I have only been able to connect to my device via adb when accessing the ADB sideload function in the recovery console. I have seen that you can sideload a kernel with usb debugging enabled but I have no clue on how to achieve this. i also need to make sure that whatever I do the data will not be affected. Any assistance would be very helpful. Thanks in advance.
Phranqy
Not sure if this would work but you could boot into download mode, flash a custom recovery, boot into custom recovery, and mount the partitions to copy the data to your computer.
Edit: if the digitizer failed, I don't think my method will work unless it is just in the ROM that the digitizer doesn't work.
I figured it makes sense to break this out into it's own thread. Dealing with a dead screen/digitizer situation. Phone is rooted with safetrap, usb debugging is enabled but unauthorized. I'm not able to boot into recovery (no screen, not sure whats happening), closest thing I get to is booting into sideload mode and adb recognizes my phone.
Not sure if that means anything, is it possible to write some script, that executes pushing the new key, zip it and sideload it via adb? Will it autorun somehow?
Device - OnePlus 5 (64GB), TWRP 3.3.1-0-20190713-codeworkx
Yesterday, while trying to reset my phone I accidentally wiped the system partition. I am able to boot the device into fastboot mode and TWRP (doesn't ask for any password), however the phone is going undetected on my Mac.
I tried ADB side loading using terminal, following error comes -
Device (Null) not found.
Tried to connect thru OTG, even that is going unnoticed. I just want to copy the ROM file to phone, in order to restore it to stock condition.
Any help would be appreciated...
Was your device encrypted and you had a password? Otherwise it's normal that it doesn't ask for a password.
First off, I don't know how proficient you are.
I assume
- You're in TWRP
- Your phone is connected to your Mac and charges
- You're using a cable that can transfer data, eg. the Dash Charge cable
In TWRP, go to mount. You can either have MTP or adb enabled, not both at once AFAIK (MTP disabled = adb enabled). You probably have it disabled. You can either get the zip to the phone by MTP or via adb push. I think it happened once that I had to switch MTP off and on again.
If you try to use a USB stick, you have to mount it. You can do that under mount too. I'm currently not sure where it will be mounted though. (I don't know what formats are supported, but Fat32 should do the job).
I assume you tried sideload correctly, but just to make sure you did it right, you have to go to Advanced -> Sideload and enable it, THEN use the command 'adb sideload ....
If nothing of the above works, I only assume there's something wrong with the recovery. Try another version, official, codeworkx (he posted a thread), or blu_spark (latest version is on GitHub).
You can modify the system partition without needing to decrypt, doesn't matter.