I'm trying to do an adb backup, but the behavior I'm seeing makes me thing it's failing. I'm on OAF (Verizon Note 4, LP 5.0.1). When I try, I immediately get a file that varies in size with each attempt.
I suspect this is an issue with ADB though. I can connect over USB, but after ~30 seconds, it disconnects and reconnects then stays connected. If i use tcpip mode, it doesn't have this issue, but ADB Backup doesn't want to work at all over tcpip mode.
Since backup requires me to wake the device to approve the backup, I seem to be stuck, but I'm not positive that's the issue since the backup is creating a file almost instantly and dropping me back to a prompt, long before adb resets.
1) Anyone seen this ADB behavior and know a solution? I've tried various ADB drivers, installed/uninstalled Kies, etc.. All my other devices work fine also. Same behavior on my laptop also. I have disabled knox and OTA packages, but not much else.
2) Does this ADB backup behavior sound appropriate?
3) Should I bother with Helium given these issues?
Bottom line is that my Note 4 is running like lowmemkiller is a mess; I have to close all apps ever few hours to get the phone back to a remotely usable state and I haven't seen that in years. I want a clean app/data backup before I do anything else like factory reset, revert to KK, etc..
To preempt the 7eet "go search" replies, I have spent a few hours working on this myself, but searching threads for "adb", "backup", "disconnect", "reset" and combinations of those don't return very helpful responses
Related
Re-written to be more concise and readable:
Long story short: I installed the program "Permissions Denied" from the market and restricted a few games. When I rebooted something was broken and I can't quite figure out what, but it runs deep through the phone.
The phone isn't bootlooping, but when I starts up it will very often become unresponsive immediately after getting to the lockscreen, my theory is that things are trying to load and crashing in the background. The only fix for this is to wait until it appear to reboot itself; the screen will come back on and show me a quick few cycles of the boot animation, then back to the lockscreen. After this, it asks to re-activate on the network. Whether or not everything works after this point has been highly variable. Currently, my phone is on but has no way of signing into a google account (isn't even an option in the list under settings).
If I try to restore a nandroid, at the very end it spits out "Error while restoring /data!". I've done this with a couple nandroids that I've used fine in the past. Fully wiping from CWM and installing a fresh rom yields similar results.
Basically my thinking at this point is to back up anything I want while I have access to the phone and try to do as full a factory reset as possible. Any ideas? Of note is that I've run the "fix permissions" function both in CWM and ROM Manager, and when I run it in ROM Manager the log shows permissions for a bunch of programs that have been wiped. So I'm guessing that permissions settings persist across wipes, but I don't know what to address that with specifically.
Bump? (rewrote OP to make it less of a train wreck of my late-night detective work)
Edit with maybe-progress: I found and installed an older apk for Permissions Denied and even though this is an older nandroid and everything has been wiped time and again, the permissions for the games I changed are still disabled.
Having trouble getting the program to actually undo anything though, and rebooting the phone is a rather tiresome task with all this going on just to find out nothing changed.
Does anyone know
1)Where permissions live, and if I can reflash whatever that is, as it is clearly corrupt here.
2)Where I can get a copy of the v2.9 apk for this app, as maybe it will be better at restoring what it did than the older version I dug up.
Edit2:I eventually just did a factory reset and it fixed everything. I had also emailed the developer of the app and he got back to me with the following advice:
It sounds like the permissions file is locked, packages.xml. Try opening my app, going into the settings, and make sure that the first option is NOT checked.
Then hit the unlock option to unlock the file.
If that doesn't work, try the following in a terminal...
su
chattr -ia /data/system/packages.xml\
Click to expand...
Click to collapse
Intuitively this sounds like it may have fixed the problem, so I'm posting it here in case anyone ends up with similar problems and finds this thread searching.
Well, I'm in a bit of a predicament.
Last week I installed a custom rom, and almost immediately after, I completely destroyed my phone's LCD and digitizer. Fortunately, the phone still functions fine, but obviously I have no screen and I can do nothing except essentially press the home button. I still hear text message tones, etc, and I can still call the phone, but obviously I can't navigate or do anything as there is no screen.
The problem is, I want to sell the back of the phone as used parts since it functions well, but the phone contains sensitive information (my contacts, SMS, etc) that can not be accessed via Windows Explorer.
I downloaded the SGS3 QCom Toolkit, but it will not recognize the phone, nor will Android Commander, because USB Debugging is disabled.
I'm not interested in retrieving anything in the phone, but I definitely want to delete the SMS, contacts, and Google login info from the phone. If this means restoring factory and loading stock rom that would be great, but I can't seem to do anything without USB debugging enabled, as no software seems to recognize the phone even with all the drivers installed.
Can anyone help? Thanks in advance!
Just sideloaded the Mashmallow update from 5.1.1 to 6.0 (downloaded from Google) and the update seemed to go normally - most things work as normal. But the WiFi wouldn't turn on, and it's mac address reports as 02:00:00:00:00:00. That address I know was an issue in the M Preview as a fake address.
I didn't want to hard reset it but in the end relented and loaded a clean new version of 6.0 from Google. When it restarts the second thing it wants to do, after selecting a language, is start the WiFi so it can log on. Of course WiFI won't start, and I can't "skip" so it's stuck. I tried Bad_Boyz fromXDA, and then going back to 5.1.1, and now forward again to 6.0 - same result. I suspect the WiFi mac address has been cleared. I found a little help that if I shell into the tablet, and write the mac address into /persist/wifi/.macaddr I might move forward. I know how to do this, but I can't shell in with adb. I can talk over USB, and run fastboot. When I connect via USB the Nexus mounts (sort of - the storage folder isn't shown when the tablet is at the "Select WiFi network" stage of setup)
When I run "adb devices" - I can't see any, even though I can "fastboot reboot recovery" and the like. I'm sure bluetooth (mac address) is broken too, but I"ll fix that later.
Does anyone have any idea how I can encourage adb to talk, so that I can "adb shell"?
Safe Mode
Just so you know - I started it in safe mode, which I have done before, but anyway - and the WiFi works. Also, USB debugging is presumably switched to off on a hard reset, and I couldn't log in to enable it without working WiFi. Suddenly my mac address is back. Don't really know if safe mode is the answer but it's worth trying...
To get into Safe Mode - long press on the "Power Off" question when you turn it off - it reboots in safe mode.
Dropped my S3 today, and now the screen doesn't respond to touch. The display also only works partially. This is the excuse I needed to get an S5, but I'd like to pull data off this S3 for the transition. Honestly I'm not even sure there's anything important on there that isn't already backed to the cloud one way or another. But I'd like to poke around to be sure, use Titanium backup for at least a few apps in particular.
So I found this nice utility: http://forum.xda-developers.com/showthread.php?t=2786395 to allow me to control the device and see the screen via adb. Problem is that while USB debugging is enabled, I have to confirm the RSA fingerprint of my PC on the device itself... which I can't do because the digitizer on the phone is broken. Some searching suggests using a USB OTG to connect a mouse to blindly try to hit the RSA confirmation button. Either it doesn't work, or the cable I hacked together didn't cut it. I couldn't get off of the keyguard screen. Ordered a premade OTG adapter, but if that still fails I may have to find another way in.
From what I've read, I can disable the RSA check by setting ro.adb.secure=0 in default.prop, but that file would need to be replaced on the boot ramdisk. Making a custom boot image isn't something I've done. I found this article about it, "HOWTO: Unpack, Edit, and Re-Pack Boot Images". Following that article, should my boot.img come from extracting the L710VPUDNJ2_L710SPRDNJ2_L710VPUDNJ2_HOME.tar.md5 file? And then once I've recompiled boot.img with the modified default.prop, what is the proper method for flashing that boot.img? Do I need to use odin?
The device has stock NJ2+root and Philz Touch recovery. The display and hardware keys work well enough that I can navigate recovery and initiate anything in there, and I can get to an adb shell while the device is booted in recovery.
So two questions...
1) am I on the right track to make and flash a custom boot.img?
2) is this all pointless? would I be better served to simply use recovery to copy down a backup image and extract anything I may need from that? That main data I'm concerned about is keys/etc for 2-factor apps like google authenticator and battle.net.
EDIT: As far as getting in, I couldn't figure out how to make that app work properly for controlling the phone. It could show me the screen, but apparently not send touch input.
BUT, the solution to bypassing secure adb was easy. Since I had a custom recovery and could get adb shell while booted in recovery, I could shell in, mount data, and push my local adbkey.pub to /data/misc/adb/adb_keys. VMLite VNC Server was the easiest way I found to access the system remotely, since I could push the app install from the play store on the web and then use the companion desktop app to launch the server on my phone via adb.
So hello there!
I'm having the following issue and I'm kinda out of ideas.
I was running a (KingRoot) rooted fireOS 4.6.6.1 (420) if I'm not mistaken.
So this is what happened:
Phone was running just fine, but I wanted to get rid of the facebook background services which kept running without the actual app installed. Also a friend proposed to run the 'fstrim' command. So reading through xda I found an app called 3C Toolbox (http://www.3c71.com/android/?q=node/916) which seemed to be safe to use. Installed it and still didn't change a thing except for the three 'fstrim' actions to perform. After that I restarted my phone.
Powered off just fine, but at the start only the 'Amazon' logo comes up and vanishes into a black screen with the backlight still on. Even after waiting several hours nothing changes.
So what did I attempt to get it wirking again?
At first I tried to simply restart it. --> Nothing changed.
Tried to get into recovery and clean the cache. --> Nothing changed except the 'Amazon' being on for a bit longer
Get into ADB and try pull/uninstall... --> Guess due to the locked bootloader I'm not allowed to issue any command other than 'adb sideload [packagename]' for system updates. As for ADB itself I can only get it to recognize on the PC when I get into recovery and choose the 'apply update from ADB' option.
Get into fastboot according to this tutorial (https://forum.xda-developers.com/showthread.php?t=1668159) --> doesn't work.
Get into 'Safe Mode' with this tutorial (https://forum.xda-developers.com/fire-phone/help/how-to-fire-phone-to-boot-safe-mode-t2828240) --> doesn't work either.
So does anybody has another idea I could give a try or should I just abondon all my data and flash a new clean image?
Also I'm not sure if updating from ADB will erase all personal data too. Guess so, but maybe I can get a clearification in here too.