Hi. My screen is dead on my phone. I need to somehow disable the alarm.
I cannot seem to find where the alarm data is stored.
I then tried to delete the apk.
I got an ADB by booting into TWRP. Then used ADB SHELL. I attempted to cd into System/App as follows
cd system/app
/sbin/sh: cd: can't cd to system/app
I figured I had a root permission error, so I tried "su" but it couldn't find the command which is odd because I have SuperSu.
I can't navigate the TWRP menus due to my broken screen and don't know what to do.
Ratiocination said:
Hi. My screen is dead on my phone. I need to somehow disable the alarm.
I cannot seem to find where the alarm data is stored.
I then tried to delete the apk.
I got an ADB by booting into TWRP. Then used ADB SHELL. I attempted to cd into System/App as follows
cd system/app
/sbin/sh: cd: can't cd to system/app
I figured I had a root permission error, so I tried "su" but it couldn't find the command which is odd because I have SuperSu.
I can't navigate the TWRP menus due to my broken screen and don't know what to do.
Click to expand...
Click to collapse
you can wipe data.... and to do so you can use a openrecovery script
make a file named openrecoveryscript and push it in /cache/recovery/
in the file put the folowing command
wipe data
and then reboot into recovery and it will execute by itself.
by wiping data the phone will reset to factory/rom defaults. you will loose installed data. everything on "sdcard" will stay in place
darkobas said:
you can wipe data.... and to do so you can use a openrecovery script
make a file named openrecoveryscript and push it in /cache/recovery/
in the file put the folowing command
wipe data
and then reboot into recovery and it will execute by itself.
by wiping data the phone will reset to factory/rom defaults. you will loose installed data. everything on "sdcard" will stay in place
Click to expand...
Click to collapse
I considered wiping it, but wanted to avoid that so I can determine who attempts to call/text me before I can get a replacement.
darkobas said:
you can wipe data.... and to do so you can use a openrecovery script
make a file named openrecoveryscript and push it in /cache/recovery/
in the file put the folowing command
wipe data
and then reboot into recovery and it will execute by itself.
by wiping data the phone will reset to factory/rom defaults. you will loose installed data. everything on "sdcard" will stay in place
Click to expand...
Click to collapse
Get an mhl cable and plug it in to a tv or monitor. It mirrors the display so you can navigate it as usual, unless the digitizer AND the panel are both dead...
Sent from my LG-D803 using xda premium
dirt_squirrel said:
Get an mhl cable and plug it in to a tv or monitor. It mirrors the display so you can navigate it as usual, unless the digitizer AND the panel are both dead...
Sent from my LG-D803 using xda premium
Click to expand...
Click to collapse
I should have clarified. The display works as in it can display an image. It just does not recognize my touch other than in a very small area.
If you have root access with adb...
Run adb root
Then adb shell
Cd to /system/media/alarms and delete all the sounds.
Or search for clock in /data/data
Sent from my LG-D802 using Tapatalk
Related
Hi, i need a fix for this and fast !!! I've tried all that is listed on xda about this issue, but to no avail. Anyway, i forgot my pattern and went to the forgot pattern menu. My wifi was off, so i figured it would give a prompt of some kind to turn on the wifi and then log on to my google account. But nooooo, google supposes that everyone's wifi is on all the time. Please help, what do i do ? I rebooted to recovery, i made a nandroid and currently i am adb pulling the twrp folder from my N7. I would have just factory reseted it, no probs, but i remembered i have some EXTREMELY important works in colornote that i can't afford to lose. Please help, what do i do ?????
Looks like you answered your own question. Unless your Android isn't encrypted, just boot into TWRP and backup your data using adb:
adb pull /data/data C:\backup
Click to expand...
Click to collapse
The main thing you will have to concern about is restoring those data and make it readable by the app. There are several ways, but you can either:
adb push C:\backup\colornotes /data/data/colornotes
Click to expand...
Click to collapse
Don't forget some devices you need to give it write permission first: adb remount rw, though should not be needed with TWRP. Or just copy the folder back using a rooted file manager.
Then go into adb shell and fix permission of the files so the app can get access to them:
adb shell
su - (again shouldn't be needed wile in TWRP)
chmod -R 644 /data/data/colornotes (or 777 for full access)
Click to expand...
Click to collapse
Tips while in adb shell:
Check permissions of files by typing: ls -la
Check what partition is mounted and whether you have write privilege to it by typing: cat /etc/fstab
Also, if you use a custom rom like CyanogenMod or AOKP, there is an option to enable all widgets on the lockscreen. Just put the Power Control widget on the lockscreen, then you can toggle WiFi on and off. (Can't remember if this is also possible with stock.)
Have fun.
OR have a look here.
Looks like either of the two methods suggested would be feasible with only a recovery running, but the 2nd one is easiest (as a custom recovery wouldn't necessarily provide a statically-linked sqlite3 utility).
if it works it doesn't require any wiping.
BTW guess how I found this.... wait for it .... wait for it.... wait for it.... I used google search.
Hi, i forgot to mention that i made the twrp backup while i was locked out and whenever i try to restore from the backup after a factory reset, it goes back to square one... And when i did a full wipe and hoped to use titanium backup to extract stuff from the nandroid, it just gives me and empty list, but the backup is there, all 5gb of it
iAndroidOS said:
Hi, i forgot to mention that i made the twrp backup while i was locked out and whenever i try to restore from the backup after a factory reset, it goes back to square one...
Click to expand...
Click to collapse
Well, that is to be expected, is it not? You are restoring exactly what is already there - effectively a no-op.
OK, I just booted into TWRP (2.4.1.0) and confirmed that the (equivalent of the) following disabled my pattern lock on the next boot:
cd /data/system
mkdir foo
mv locksettings.* foo
mv gesture.key foo
I did all of the above (the 'cd' command is implicit) using TWRPs touch interface - didn't even need adb.
ymmv as I am using jdq39/4.2.2 and my tablet was not in a "locked-out" state, but its an easy thing to try.
I sadly dropped my nexus 4 on hard tiles yesterday face down and the whole front cracked everywhere! The phone still turns on, I can copy internal storage off fine, but since the touchscreen doesn't work anymore I'm having trouble with getting system data off e.g. sms.
I've managed to get non touch CWM installed, made a nandroid, but now I can't copy the damn thing off! ADB gives me unauthorised for every command, and obviously I can't use the phone to authorise my PC. Am I now essentially screwed? Been googling for ages and can't find a way round the fact I can't use ADB or force my phone to authorise my PC without using the screen.
Any other ideas would be massively appreciated. The phone is rooted, CM10.2, and luckily usb debugging is enabled.
Cheers!!
You said you can copy internal storage right? so why not pull the nandroid from /clockworkmod/backup?
Sent from my Nexus 4 using Tapatalk 4
I do not use CWM, but I do use TWRP and it allow me to access to the /data and /sdcard partition just fine, /system is off limit though. I don't know where your nandroid is backed up in, but I assume its in /sdcard.
Try this: Flash TWRP in fastboot mode, then press the volume button either up or down twice, then press Power to access the recovery. Then on the main menu of TWRP, you can do adb commands right away.
I can then simply back up my whole /sdcard partition by: adb pull /sdcard/ C:\backup
Or backup the all the apps data: adb pull /data/data/ C:\backup
Thank you both for the advice. I've tried using adb in recovery, but it says: remote object '/sdcard' is not a file or directory.
If I type adb devices, I get my phone ID along with 'recovery' next to as expected.
Any ideas?
Thanks.
EDIT: Ignore this, just added a / after /sdcard and now its pulling ok. Thanks so much!
I was typing this up before I read your edit:
If you don't know where certain files are, you can type "adb shell" to enter the phone itself, there you can look at the phone directory structure and find where your files are located.
Use the cd and ls commands to navigate in the phone: http://afrodita.rcub.bg.ac.rs/~ivica/nlm/part1/cd_ls.html
Once you're done, type "exit" to get out of adb shell. Then you can use the "adb pull" command to copy the files.
Hi !
I have a problem, my phone (nexus with cyanogenmod10.2) switch off when he have finished to boot, as if there was very low power battery.
So i want to reset all but i need a solution to save all my datas, on "sdcard" and in "system" memory
i read that i can using the cmd : adb pull "device files directory" "PC files directory"
but i don't know how to use it... i'm french and its hard to translate all...
so if there is a French who can explain me its perfect !
if the explanations are clear in english its perfect too
To use any of these command you need to install adb on your computer. Here is a guide: http://www.redmondpie.com/how-to-set-up-android-adb-and-fastboot-on-windows-tutorial/
After that you open a command prompt window (windows key + r, type in "cmd", press enter). Then you put the phone into custom recovery and use the command "adb pull /sdcard/".
I've done these steps
But my problem is how to write, i need the "trame"(in french).
to be in recovery mode, i just have to boot in fastboot and select recovery mode and press power and next step is to sent my commands right?
the bg gg said:
I've done these steps
But my problem is how to write, i need the "trame"(in french).
to be in recovery mode, i just have to boot in fastboot and select recovery mode and press power and next step is to sent my commands right?
Click to expand...
Click to collapse
Correct.
Chromium_ said:
Correct.
Click to expand...
Click to collapse
Ok, but, i'm in the correct directory to use adb i write : adb pull /sdcard/ E:\Nexus4SDcard\ and nothing happens, as if i made a mistake... and i need to save all, sd card + system, so how can i do? what is the directory?
Someone can help me? 3 days without phone its hard :/
the bg gg said:
Ok, but, i'm in the correct directory to use adb i write : adb pull /sdcard/ E:\Nexus4SDcard\ and nothing happens, as if i made a mistake... and i need to save all, sd card + system, so how can i do? what is the directory?
Click to expand...
Click to collapse
If you looked at that other guide and have added adb to the environment variables
In your command prompt, do the following
E:
cd Nexus4SDcard
adb pull /sdcard
It should now being transferring
Sent from my Nexus 4 using xda app-developers app
finally i didn't write any directory for destination and it works fine but in this directory : C:\Program Files (x86)\Android\android-sdk\platform-tools, but its not a problem, using command prompt : "adb pull /"
how can i save and restore all my sms messages?
If the database is still intact it is located at /data/data/com.android.providers.telephony/databases/mmssms.db
You grab it the same way you tried to pull.
In recovery
adb shell mount /data
adb pull /data/data/com.android.providers.telephony/databases/mmssms.db
Sent from my Nexus 4 using xda app-developers app
i have an error :/
"C:\Program Files (x86)\Android\android-sdk\platform-tools>adb shell mount /data
mount: mounting /dev/block/platform/msm_sdcc.1/by-name/userdata on /data failed:
Device or resource busy"
and when i'm in the recovery mode i can't unmount /data
Sounds a little extreme... chances are, there's a better method.
If you have CM10.2, then no doubt you have a custom recovery already. I'm going to assume that this is not an actual battery issue. Is it crashing and rebooting or flat out turning off? I can't remember if CWM shows battery percentage, but TWRP does. What does it show?
What are you trying to back up? Just your /sdcard? Or your /data as well?
What happened to make it seemingly turn off once it's booted? Did you flash a new nightly?
You could always backup /data in your custom recovery as well and then do the wipe that doesn't erase the "sdcard" and then pick apart your backup later...
I'm trying to recover some lost pictures from cache. I can't root because my bootloader is still locked, and unlocking it will wipe the very data I'm trying to recover... Is there any way for me to get read-only access to my cache, without first wiping the phone?
What exactly will adb backup/restore keep? Will it save my cache? I've heard people say it stores literally *everything* and others say it won't back up the cache and some other system files?
The djrbliss motochopper toolkit http://forum.xda-developers.com/showthread.php?t=2233852 would be absolutely perfect, except that I'm running 4.3, and I don't know of any way to downgrade without wiping the phone... One Click Root also would be perfect, except they don't support the Nexus 4...
Is there any way I can root access, or at least read/pull these files, without wiping the device?
I've been searching frantically for days now, I'd pay good money to have those pictures back If I can get these pictures off, you can bet I'm rooting immediately!
Nexus 4, running 4.3 build JWR66Y all stock
If all you want to do is be able to access files on your cache partition, you could try using "adb pull /cache/".
I dont think that needs root, but i could be wrong. Nonetheless, its worth a shot. Setup adb , open command prompt, and run:
Code:
cd Desktop
mkdir cache
cd cache
adb pull /cache/
Chromium_ said:
If all you want to do is be able to access files on your cache partition, you could try using "adb pull /cache/".
I dont think that needs root, but i could be wrong. Nonetheless, its worth a shot. Setup adb, open command prompt, and run:
Code:
cd Desktop
mkdir cache
cd cache
adb pull /cache/
Click to expand...
Click to collapse
It does appear to need root - it just leaves the destination file empty? Likewise I can't access /cache/ it through FTPDroid or Total Commander, says I don't have permission
bken said:
It does appear to need root - it just leaves the destination file empty? Likewise I can't access /cache/ it through FTPDroid or Total Commander, says I don't have permission
Click to expand...
Click to collapse
I guess you need root as I just tried adb pull too and it's not working, opening the folder in adb shell is not working either so I guess you have no luck
What you could try is copying the partition using dd but I'm not sure what's the name of the partition (which block) etc ... But that *could* work. EDIT: Not working either, you still get permission denied, sorry
Sent from my Nexus 4 running Android 4.3
mihahn said:
I guess you need root as I just tried adb pull too and it's not working, opening the folder in adb shell is not working either so I guess you have no luck
What you could try is copying the partition using dd but I'm not sure what's the name of the partition (which block) etc ... But that *could* work. EDIT: Not working either, you still get permission denied, sorry
Sent from my Nexus 4 running Android 4.3
Click to expand...
Click to collapse
Thank you for trying. adb backup gave me access to all my app files, but didn't grab cache.
Here's a thought: through the backup I have an extracted .ab file with all the data for the app that wrote this data into cache. Is there a way I could replace the .apk with something that could copy this program's cache data to /sdcard, and then "restore" with this modified .apk? Would the new .apk retain the permissions of the old, and let me copy this data? Or, alternately, could I modify the .apk to allow debug mode so I can open the cache as that app in console, and adb pull then?
My next best option I can think of, is to go ahead and unlock the bootloader, let the phone reset, and then immediately root and perform data recovery, and hope I don't overwrite everything in the meantime. I'm not sure yet which USB Mass Storage methods (if any) will let me use a standard file recovery program to scan the drive. This is also my last resort, as if it screws up I'm toast.
Forensics lab got back to me, said they could "probably" do it but it'd cost me $1200 I would happily pay 120 but 1200 is absurd. Wonder what their method is to extract data...
OK I think I'm almost there!! I retrieved the .apk through my Holo Backup full system backup and decompressed it using Droid Explorer. Decompiled with apktools, changed my manifest file, and then recompiled into apk. Now I'm trying to get my new AndroidManifest.xml and resources.arsc into my .apk without mucking up the certificate... It sounds like people have had success taking the changed files out of the newly compiled apk and stuffing them into the old apk real quick without it changing the certificates, but I don't seem to be having the same luck? I'm getting this error which isn't a "no certificates error" but isn't success either. Only thing I changed was debug = "false" to "true"
Code:
c:\>adb install -r -d d:\com.xxxxx.xxxxx.apk
2490 KB/s (15989341 bytes in 6.269s)
pkg: /data/local/tmp/com.xxxxx.xxxxx.apk
Failure [INSTALL_PARSE_FAILED_UNEXPECTED_EXCEPTION]
The apk I'm starting from installed fine, and I know because it reverted me to a previous version because the marketplace had just updated me over the weekend. This zip trick has also apparently worked for a few people, any suggestions other than keep trying other computers and programs?
http://www.galaxynexusforum.com/for...562-how-decompile-compile-using-apktools.html
http://forum.xda-developers.com/showthread.php?t=1658121
I'm not trying to reverse engineer this app for any evil, I only want my lost data that I only don't have because I failed to root when I should have and as soon as I have that, I'm reverting the app back to the official version. :angel:
I'm trying to delete the audio conf file in system/vendor/etc but it won't let me. I'm rooted and running Pure Nexus.
Also when I go into the recovery and try to use the file manager it doesn't show me any files in that folder even though there are files in there.
I just updated the Rom the other day. What could have gone wrong?
Sent from my Nexus 7 using Tapatalk
you need to mount the system partition as writable first. Issue from the dos command prompt:
adb root
adb remount
and then try again and it should work.
*EDIT* that's from within the normal system. You're also asking about recovery. In that case you need to mount /system first. Click on the 'mount' button inside TWRP and select system and vendor. Then you should be able to delete the file too (make sure you didnt select 'mount system partition read-only'). So that's a solution if you don't have adb installed.
gekkehenkie11 said:
you need to mount the system partition as writable first. Issue from the dos command prompt:
adb root
adb remount
and then try again and it should work.
*EDIT* that's from within the normal system. You're also asking about recovery. In that case you need to mount /system first. Click on the 'mount' button inside TWRP and select system and vendor. Then you should be able to delete the file too (make sure you didnt select 'mount system partition read-only'). So that's a solution if you don't have adb installed.
Click to expand...
Click to collapse
The worked when I did it in the recovery. Thanks so much
Sent from my Nexus 6P using Tapatalk