With root coming I'd like to be able to restore from backup when I need to unlock my bootloader and phone gets wiped but it's not backing up. See attachment. I even ran
PHP:
adb shell
bmgr run
bmgr backupnow --all
Anyone else having the same issue?
Related
OK so when I type in adb backup -f C\Backups\gnexbackup.ab -all -nosystem
it looks like it does it's thing and backs up everything, but then when I go to the folder (Backups) I don't see that .ab file... what's up?
I am using takju 4.1.1 unlocked bootloader, but no root
same problem
works, but does not fix broken system apps
start cmd with admin
go to location of adb.exe
C:\>cd C:\adb
check adb
C:\adb>adb devices
List of devices attached
0123456789ABCDEF device
connect only one device!
if "adb devices" returns anything else, something is wrong, try '>adb kill-server' and retry and/or redownload newest adb at thanks Snoop05
C:\adb>adb backup -all
confirm at phone with password, no password leads to failure during restoring process, its a known bug (adb v1.0.32 and below)
file C:\backup.ab will be created
restore with
C:\adb>adb restore backup.ab
confirm at phone with password
wait till done
works for me, all user apps and data are restored, but it did not fix my broken google services and deleted calendar storage (accidents happen )
This function is not reliable. Some apps work, others dont. Only use this if you dont have any other options, e.g. broken phone or some malfunction.
Hi there,
I want to do a full adb backup before I unlock my bootloader and root etc...
My only issue is that it always hangs at a certain point during the backup 'com.android.sharedstoragebackup'...
I was using the command adb backup -apk -shared -all -f C:\backup\backup2012.ab
It kept freezing up so I decided to remove the '-shared' part but when I try to back up it keeps on doing 'com.android.sharedstoragebackup' and freezing...
Has anyone had this issue before?
Thanks,
T-L-H
Did you find a resolution to this? I'm seeing the exact same things (Evo 4G LTE)
just let it run. My .ab file was 12Gb and it 'hung' at com.android.sharedstoragebackup for about 45min. Then it continued
I remember reading that once it hangs, you can stop and remove the shared flag of it to resume. Just do a search, check the HOWTO results, you will find the exact description.
Hello people, I come to ask for help that I need urgently. Well at the beginning of the year install pixel experiencie and I did not backup the efs folder, when I returned to stock I lost it and from there every day I searched for solutions and I am still looking for some. If anyone knows any effective method or not, you can help me. Thanks greetings
(Sorry for the English, I use the google translator)
TioNacho said:
Hello people, I come to ask for help that I need urgently. Well at the beginning of the year install pixel experiencie and I did not backup the efs folder, when I returned to stock I lost it and from there every day I searched for solutions and I am still looking for some. If anyone knows any effective method or not, you can help me. Thanks greetings
(Sorry for the English, I use the google translator)
Click to expand...
Click to collapse
There's a possible fix until the moment you flash persist or restore EFS from another phone to yours.
ONCE AGAIN, DON'T TRY TO FLASH PERSIST OR RESTORE EFS FROM ANOTHER PHONE!!!
Just root your phone using Magisk and execute these commands using adb on your PC/laptop:
Things to note before you start executing commands below:
1. Make sure that USB debugging in your phone is turned on.
2. If everything is set properly and "adb devices" has been executed, u should see popup window about ADB allow on your phone BUT ONLY IN CASE YOU ARE USING ADB ON PC WHICH WASN'T USED FOR ADB YET. Make sure "Always allow from this PC" is checked and click "OK". Re-run command one more time. You should be able to see your device in cmd window now.
3. After "su" command, you have to grant root access to adb shell within 10 seconds.
4. "adb reboot" command will immediately reboot your phone, don't panic.
5. You are doing this at your own risk.
Code:
adb devices
adb shell
su
chown -R rfs:rfs /persist/rfs
chown -R rfs:rfs_shared /persist/hlos_rfs
adb reboot
Commands have been used from this thread: https://forum.xda-developers.com/g5-plus/how-to/fix-persist-resolve-imei0-explanation-t3825147
Good morning!
Look I was able to recover the signal (h +) with that command but not imei. Will not you know other commands that will make him recover or some method? regards
I'm trying to use ADB Backup and Restore, but when I try it I receive " Now unlock your device and confirm the backup operation."...however, nothing shows on the screen. Normally, a confirmation window displays on my phone, but nothing on the firestick.
I've tried single and double quotes, but nothing:
adb backup appname.ab -f com.app.com
adb backup 'appname.ab -f com.app.com'
adb backup "appname.ab -f com.app.com"
I'm trying to backup some app data and add it to another firestick, but running into some trouble. It isn't Kodi, but it is from a sideloaded app if that helps with more information.
Any ideas would be greatly appreciated! Thanks
Well, I have essentially done everything wrong that you can do wrong.
For security considerations, I wanted to disable my baseband modem on my LG G4 H815 (currently having /e/ installed) - see this beautiful post for the instructions.
As I don't have root, I had the genius idea to do it all via the TWRP recovery. Once booted into the recovery, I had to enter my encryption lock, but that didn't work. I had yet another genius idea, thinking that I probably wouldn't have to unlock the encryption, as I only wanted to disable the modem (and didn't care to backup my data). So I entered TWRP leaving the system read-only.
Then I entered the terminal and wanted to disable the relevant services, as described in the post. However, the pm command wasn't available in the TWRP shell, so I had the genius idea to just skip those steps.
I then wanted to override the radio with zeros (as described in the post). However, the exact file from the post didn't exist, so I had the genius idea to overwrite /dev/block/platform/soc.0/f9824900.sdhci/by-name/modem instead. However, I firstly wanted to back it up to my external SD (I assumed that wouldn't be affected by the encryption) and did so with dd. After also having the modem overwritten with 0s (and synced) I rebooted to system, where I got the error that "Settings," stopped working and my phone started rebooting to recovery.
I thought "oh well, I'll just restore the backup modem from the SD", however I had to realize that (probably because I hadn't mounted the SD properly) the file didn't exist on the SD (anymore).
That's the current state. As I don't really want to lose my data (that I didn't backup), I haven't tried re-flashing anything yet (especially as I don't know if this'd help).
Is there any way to recover the "modem" without losing my data? Or, even better, is there a way to continue disabling the modem, with my phone properly booting again?
I really appreciate your help - please let me know if you need further information.
EDIT: It would probably be super helpful (and enough) if someone out there with the H815 could dump the content of their modem dev and share it with me. I don't think (?) that's included in a system image - at least it isn't mounted in system.
EDIT: Let me provide some instructions on how to (presumably) safe my day, if you have an H815 with TWRP recovery and adb on your computer:
Reboot to recovery:
Bash:
adb reboot recovery
In TWRP, mount your Micro SD card or another partition you can read & write to (Mount -> Tick Micro SD card)
Restart adb:
Bash:
adb kill-server
Enter adb shell:
Code:
adb shell
In adb shell, validate that your SD (or other partition) is correctly mounted (you should get the contents of your external SD):
Bash:
ls /external_sd
In adb shell, dump data from modem and exit adb shell:
Bash:
dd if=/dev/block/platform/soc.0/f9824900.sdhci/by-name/modem of=/external_sd/modem.img
sync
exit
Pull dump from device:
Bash:
adb pull /external_sd/modem.img
Upload modem.img from your computer (from the directory you executed above command from) to some cloud
Share a link to the file with me
I'd be very grateful if someone could do this. Please feel free to ask questions about the procedure or to help me in any other way.
Turns out, someone already did upload a modem - it's even linked in the install instructions for /e/. I used this file (flashed via TWRP) and it seems to have fixed my issues.
Of course, now the modem still isn't disabled - so if someone has an idea on how to achieve this without bricking my phone (preferrably also without having to root it), feel free to make me happy.
I now have tried killing the modem with rooting my phone, but it lead to the same error. Before deleting the modem, I ran the following commands in adb shell to mimick the disabled services from the original post as best as possible:
Bash:
su -c "pm disable com.android.cellbroadcastreceiver"
su -c "pm disable com.android.mms"
su -c "pm disable com.android.phone"
su -c "pm disable com.android.providers.telephony"
su -c "pm disable com.android.smspush"
su -c "pm disable com.android.mms.service"
su -c "pm disable foundation.e.message"
su -c "pm disable com.android.server.telecom"
su -c "pm disable com.qualcomm.qcrilmsgtunnel"
su -c "pm disable foundation.e.esmssync"
Do I have to put this in a startup script? And if so, how do I do this?
It does seem as if they stayed deactivated though:
Bash:
$ su -c "pm list packages" -d
package:com.android.providers.telephony
package:com.android.mms.service
package:com.android.terminal
package:foundation.e.message
package:com.qualcomm.qcrilmsgtunnel
package:com.android.cellbroadcastreceiver
package:com.android.server.telecom
package:com.android.smspush
package:foundation.e.esmssync
package:com.android.phone
I'd love to know how I can achieve this.
EDIT: Now my phone reboots as soon as it's disconnected from my computer (and doesn't boot anymore)...