Develop Bugs

Remove files from system

I'm trying to remove some preinstalled apps from /system/app folder. My phone is rooted.
When I'm trying this over adb it says that I only have Read permissions. What am I doing wrong?

Put the phone into recovery mode then do the adb commands.
You only have read access while booted. R/W access while in recovery.

Mh I tried this but I couldn't even open the shell, said something.sh is missing.
You mean the normal recovery and not Clockworkmod or something, right?

You have to put it in the custom recovery. Clockworkmod or whichever one you use.

Ah okay, thank you, I will try that.
Though I need to use the normal recovery.

I tried it with clockwork now. It works but when I do "cd system" and do "ls" it's empty...so I can't see any app-folder?!
Edit: Oh I forgot - do I need to mount system first using the partitions menu?!

Eggcake said:
I tried it with clockwork now. It works but when I do "cd system" and do "ls" it's empty...so I can't see any app-folder?!
Edit: Oh I forgot - do I need to mount system first using the partitions menu?!
Click to expand...
Click to collapse
Code:
mount /system
At the adb shell.

Oy, thanks now I finally got it
Remove worked, pull didn't (or it took >5min for a simple apk file and I aborted it too early).

Phone wont install my backups.......HELP!!!!!

I was running Jelly bean for 2 weeks now and no problems and I hooked the phone up to my charger and it just started to bootload itself over and over and so I just tried to install my backup and start over but it says error while restoring data on all my backups. I need help on whether or not I am screwed or If I can connect my phone to my computer someway and use clockwork and maybe do something that way. I am able to get to clockwork rec and I believe that my files have been erased some how some way and cant connect to my computer to just start over unless one of you guys can really help me out. If I can get step by step help I will def buy someone a beer or two or three. Thanks

If you have a rom zip on your sdcard just boot into recovery, wipe and flash a new rom. If you don't then go into recovery, mount sdcard to your computer and move a zip onto your sd and then flash.
Sent from my Galaxy Nexus using Tapatalk 2

eqjunkie829 said:
If you have a rom zip on your sdcard just boot into recovery, wipe and flash a new rom. If you don't then go into recovery, mount sdcard to your computer and move a zip onto your sd and then flash.
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
I dont have a rom zip on my phone my dumbass deleted it 3 days ago. this sounds stupid but I go to recovery5.8.0.2 and how do I mount the sd card to my mac? if that helps....

Try this.
http://forum.xda-developers.com/showthread.php?t=1667929

genethebean33 said:
I dont have a rom zip on my phone my dumbass deleted it 3 days ago. this sounds stupid but I go to recovery5.8.0.2 and how do I mount the sd card to my mac? if that helps....
Click to expand...
Click to collapse
Connect your phone to your computer, boot into CWM recovery, and use ADB to push a ROM.zip, GAPPS, and whatever else you need to flash to your phone. You can then do a data wipe in CWM and flash the ROM.
If you don't know how to use ADB, download the package I've attached to this post. Unzip it to your home directory and drop any files you need to push into that file as well. Open up Terminal, type "cd" (no quotes) and drag that unzipped Mac_ADB_Fastboot folder into the terminal and hit return. It'll take you to that directory.
First, make sure the computer recognized the device by typing:
Code:
./adb devices
and hitting return.
If it detects, then type this into the Terminal, of course substituting any file you need (GAPPS, etc.) where "ROM.zip" is:
Code:
./adb push ROM.zip /sdcard/

cattom2000 said:
Try this.
http://forum.xda-developers.com/showthread.php?t=1667929
Click to expand...
Click to collapse
is there a mac version?

genethebean33 said:
is there a mac version?
Click to expand...
Click to collapse
Read my post.

genethebean33 said:
is there a mac version?
Click to expand...
Click to collapse
adb is a platform tool in android sdk, and can use on mac surely.
you can get one sent by martonikaj.
firstly you have to try to mount your sdcard in the cwm recovery. if it done, you can use adb push send file to sdcard.

martonikaj said:
Connect your phone to your computer, boot into CWM recovery, and use ADB to push a ROM.zip, GAPPS, and whatever else you need to flash to your phone. You can then do a data wipe in CWM and flash the ROM.
If you don't know how to use ADB, download the package I've attached to this post. Unzip it to your home directory and drop any files you need to push into that file as well. Open up Terminal, type "cd" (no quotes) and drag that unzipped Mac_ADB_Fastboot folder into the terminal and hit return. It'll take you to that directory.
First, make sure the computer recognized the device by typing:
Code:
./adb devices
and hitting return.
If it detects, then type this into the Terminal, of course substituting any file you need (GAPPS, etc.) where "ROM.zip" is:
Code:
./adb push ROM.zip /sdcard/
Click to expand...
Click to collapse
I tried what you did and when I try to detect the device it says no such file or directory. is there anything I am doing wrong? when I go to mounts and storage i mount the system and data and nothing happens.

man now I cant mount my sd card........... I am so screwed!!! do i need a new phone now?

genethebean33 said:
man now I cant mount my sd card........... I am so screwed!!! do i need a new phone now?
Click to expand...
Click to collapse
You could always just find someone with a PC that will let you use it for 15 minutes, download the rom, move to your phone, boot into recovery, flash and enjoy. I always have 2 or 3 rom zips on my phone just for that reason.
Sent from my Suxen Yxalag using Xparent SkyBlue Tapatalk 2

yeh I cant even mount my sd card now. just a quick question? do I just sell my phone or is there anything I can do?

genethebean33 said:
yeh I cant even mount my sd card now. just a quick question? do I just sell my phone or is there anything I can do?
Click to expand...
Click to collapse
Maybe this help.
http://forum.xda-developers.com/showpost.php?p=26088161&postcount=5
http://forum.xda-developers.com/showpost.php?p=25850720&postcount=8

[Q] Flash system over cmd

I just erased everything on my sdcard (emulated) and the system. The only things left are recovery and bootloader. I read about sideload but it doesn't work for me, because my adb doesn't act out the command (My adb version is 1.0.29). So how could I transfer the rom onto my not existing sdcard? (If I do adb push all it says is: "E: /sdcard/ : is a directory")
Please help me as quick as possible. Thanks!

Try pushing it to
adb push c:/rom_name.zip /data/media
Click to expand...
Click to collapse

acreatorius said:
I just erased everything on my sdcard (emulated) and the system. The only things left are recovery and bootloader. I read about sideload but it doesn't work for me, because my adb doesn't act out the command (My adb version is 1.0.29). So how could I transfer the rom onto my not existing sdcard? (If I do adb push all it says is: "E: /sdcard/ : is a directory")
Please help me as quick as possible. Thanks!
Click to expand...
Click to collapse
I managed it by downloading the factoryimage from google and flashing userdata.img, but thanks for the quick reply

[Q] Stuck on Google Boot screen, Can still access CWM. How to proceed?

Okay so my father was about to flash to my rom. We Wiped data, cache, delvik, and installed rom. Said it worked and rebooted the phone. Phone tossed us into the CWM again and we tried flashing again and it gives us error #7. Soooo, We did NOT make a backup and every time we try to reflash the rom it gives us error 7. We can't get the Phone to be detected by the computer so we can at least grab his data. The thing here is we can't afford to lose the data on the phone (I know, should have made a backup). Any advice on how to proceed would help significantly. I've never seen this kind of issue in my years of rooting android phones. It just sits at the Google screen and doesn't go anywhere.
Phone is Verizon Galaxy nexus running (was) MIUI
Update: Tried flashing back his previous rom (MIUI) and I'm getting the error 7 again. Even though that past rom worked perfectly. This is all very frustrating.

What data do you want to keep? Internal storage won't be wiped when flashing ROMs, and as for app data, contacts, SMS, etc, as long as you can enter CWM, you can pull them out of the phone with "adb pull".
Sent from Samsung Galaxy Nexus @ CM11

AndyYan said:
What data do you want to keep? Internal storage won't be wiped when flashing ROMs, and as for app data, contacts, SMS, etc, as long as you can enter CWM, you can pull them out of the phone with "adb pull".
Sent from Samsung Galaxy Nexus @ CM11
Click to expand...
Click to collapse
Well the problem is I don't have the Nexus adb installed onto the PC, so I can't connect to the nexus through USB. Can I install adb and everything without being in the rom? also I'm trying to get the Titanium backup folder and the photos.

If you can get into recovery, that means you can use adb. Just install the driver (if you are on Windows) and adb should work.

tonychau77 said:
If you can get into recovery, that means you can use adb. Just install the driver (if you are on Windows) and adb should work.
Click to expand...
Click to collapse
What's the command for pulling pictures and Titanium backup?

Hitmanthe3rd said:
What's the command for pulling pictures and Titanium backup?
Click to expand...
Click to collapse
adb pull [remote file] [local file]
You can pull the whole folder from your phone. The folder of Titanium Backup should be /sdcard/TitaniumBackup or something similar. For photos it is in /sdcard/DCIM

tonychau77 said:
adb pull [remote file] [local file]
You can pull the whole folder from your phone. The folder of Titanium Backup should be /sdcard/TitaniumBackup or something similar. For photos it is in /sdcard/DCIM
Click to expand...
Click to collapse
I tried to install ADB for Nexus and it failed and I ran into many roadblocks. Can you link me a W8 64bit guide I can follow?

Hitmanthe3rd said:
I tried to install ADB for Nexus and it failed and I ran into many roadblocks. Can you link me a W8 64bit guide I can follow?
Click to expand...
Click to collapse
I don't know much about those drivers because I use Ubuntu (just for my phone). But you can refer to this thread.
http://forum.xda-developers.com/showthread.php?t=1583801

tonychau77 said:
I don't know much about those drivers because I use Ubuntu (just for my phone). But you can refer to this thread.
http://forum.xda-developers.com/showthread.php?t=1583801
Click to expand...
Click to collapse
I got ADB installed but cannot get the pull command to work. It's adb /pull and it's in a 0 folder and then Titanium backup and in the Tina user folder . What would be the command?

Hitmanthe3rd said:
I got ADB installed but cannot get the pull command to work. It's adb /pull and it's in a 0 folder and then Titanium backup and in the Tina user folder . What would be the command?
Click to expand...
Click to collapse
"adb pull /storage/emulated/0/YOUR-DIRECTORY/YOUR-FILE C:\" or something like that.
Sent from Google Nexus 4 @ CM11

Question Help with bootloop after editing settings file

Hey folks,
Last night I was editing a file located under "data/system/users/0/settings_ssaid.xml" and upon rebooting my phone, it's been stuck in a boot loop. I have an original copy saved in a different folder, but unable to access anything to replace it.
Is there any specific fastboot command I can run to swap the files (adb push, pull etc)? Only boot slot A is giving me an issue, and I was reading flashing system.img would be able to help, but I don't wanna do anything I'm unsure will wipe any of my data where I'd have to start over unless I've recovered some of that data first.
If I do have to flash any stock images, pls post the instructions for clarity.
Thanks in advance.

Assuming adb can actually access your device, while it's stuck in a boot loop (test this by running 'adb devices' and see if you receive a response)
You can run the following command to list all the files in your specific folder.
adb shell ls FILEPATH
Every file in your specific folder will be listed. You can then do the following to pull/push your file
adb pull FILEPATH
adb push FILENAME FILEPATH
Of course you need to place the file that you want to push in your ADB folder.
Mind though, that simply replacing your edited file with the backup might not solve your bootloop.
You can always look up available commands here
adb shell ls - Android ADB Shell Commands Manual

Morgrain said:
Assuming adb can actually access your device, while it's stuck in a boot loop (test this by running 'adb devices' and see if you receive a response)
Click to expand...
Click to collapse
Yes, I can access adb and my device while it's booting up, but once it reboots I lose connection. Unless I can interrupt the process I'd have to be very quick in my typing to copy files lol.
Even with the few seconds I have to type some commands to access the directory of the file I edited, I do get a permission denied error.
Would swapping to Slot B during boot allow me into the system, or even flashing the system.img file?

RetroTech07 said:
Yes, I can access adb and my device while it's booting up, but once it reboots I lose connection. Unless I can interrupt the process I'd have to be very quick in my typing to copy files lol.
Even with the few seconds I have to type some commands to access the directory of the file I edited, I do get a permission denied error.
Would swapping to Slot B during boot allow me into the system, or even flashing the system.img file?
Click to expand...
Click to collapse
No because your file is on /data.
The issue is that you can't push your file to /scard since (I guess) you can't even get beyond to the point where /sdcard is mounted.
So copying it from /sdcard will likely be too late in the boot process.
Pushing directly into /data does not work either as you would have to be root. In the old days you could run and in root mode but I'm not sure that is still possible.
Factory reset will work.
On devices with separate recovery partition it would be possible to change recovery to allow adb access to /data so then push old file via recovery... But I would not know how to do that on Pixel as recovery is s part of the boot partition.

So effectively, it's likely you're only solution is to do a full firmware flash along with wipe.

I would first try a full flash removing the -w to avoid the wipe. It may work.

TonikJDK said:
I would first try a full flash adding the -w to avoid the wipe. It may work.
Click to expand...
Click to collapse
Probably a typo, but I think you meant you need to "remove" the -w to avoid a wipe.

Lughnasadh said:
Probably a typo, but I think you meant you need to "remove" the -w to avoid a wipe.
Click to expand...
Click to collapse
Thank you! My post is fixed.

TonikJDK said:
I would first try a full flash removing the -w to avoid the wipe. It may work.
Click to expand...
Click to collapse
Ok, I'm rooted so to be sure I don't mess anything up, lol can you list the steps just as a precaution?
Obviously I'd be in fastboot / recovery mode, then perform a flash-all but remove the -w so as to not erase my data?
Once the system boots, all of my texts and setup should remain as is, or do I have to go and recover it?
Would I be able to install the OS again on the inactive slot to recover data, or does that not work that way?

RetroTech07 said:
Would I be able to install the OS again on the inactive slot to recover data, or does that not work that way?
Click to expand...
Click to collapse
Nope ... there is only 1 data partition, so even when you flash the OS to the inactive slot, it would still use the same data partition. Moreover, it is then likely to upgrade/convert some files on /data which might result in not being able to go to the previous version in the old slot.

RetroTech07 said:
Ok, I'm rooted so to be sure I don't mess anything up, lol can you list the steps just as a precaution?
Click to expand...
Click to collapse
See https://forum.xda-developers.com/t/...thout-wiping-data-and-retaining-root.4356065/

so, unfortunately doing a full flash without wiping data didn't work. I'm almost inclined to believe that if TWRP was available for the P6/P, that I could go and push the file I had saved back into the directory of where it was and save myself from this mess.
I'm kicking myself because I'm usually backing up my data before I modify any system files, but this one time I hadn't done so and I had Google's backup turned off at the time, so I'm gonna have to lose some text messages over the last few days with some folks I enjoy speaking to. I do have some saved from late last week, but nothing from the weekend up until now.

As you said you can access ADB while booting, why not push/remove/replace the file while booting, even if this takes multiple boots to perform all commands, it should work assuming you can also use SU, if you can't, none of the below will work.
Code:
adb push <backup file location> /sdcard
adb shell
su
rm data/system/users/0/settings_ssaid.xml
cp /sdcard/settings_ssaid.xml /data/system/users/0/
chmod 600 data/system/users/0/settings_ssaid.xml
I don't know why it's affecting your boot though, there's a .fallback file that the system should fall back to when the system notes that this file is corrupt.
If the above doesn't work, and you could try:
Code:
adb shell
su
rm data/system/users/0/settings_ssaid.xml
cp /data/system/users/0/settings_ssaid.xml.fallback /data/system/users/0/settings_ssaid.xml
If that doesn't work, try:
Code:
adb shell
su
rm data/system/users/0/settings_ssaid.xml
And reboot, but again, I don't know why you're bootlooping from this, that file shouldn't be integral to booting.
Also, if you need to back up your data, why not just boot to boot_b, if it's not causing you issues? You really shouldn't have to reset your device to fix one problem - you could do a /data & /sdcard pull while booted to boot_b, or just run something like Titanium & SMS backup/restore.

DanielF50 said:
As you said you can access ADB while booting, why not push/remove/replace the file while booting, even if this takes multiple boots to perform all commands, it should work assuming you can also use SU, if you can't, none of the below will work.
Code:
adb push <backup file location> /sdcard
adb shell
su
rm data/system/users/0/settings_ssaid.xml
cp /sdcard/settings_ssaid.xml /data/system/users/0/
chmod 600 data/system/users/0/settings_ssaid.xml
I don't know why it's affecting your boot though, there's a .fallback file that the system should fall back to when the system notes that this file is corrupt.
If the above doesn't work, and you could try:
Code:
adb shell
su
rm data/system/users/0/settings_ssaid.xml
cp /data/system/users/0/settings_ssaid.xml.fallback /data/system/users/0/settings_ssaid.xml
If that doesn't work, try:
Code:
adb shell
su
rm data/system/users/0/settings_ssaid.xml
And reboot, but again, I don't know why you're bootlooping from this, that file shouldn't be integral to booting.
Also, if you need to back up your data, why not just boot to boot_b, if it's not causing you issues? You really shouldn't have to reset your device to fix one problem - you could do a /data & /sdcard pull while booted to boot_b, or just run something like Titanium & SMS backup/restore.
Click to expand...
Click to collapse
I appreciate the help but I can't go back as I've already wiped everything minutes before you sent this. If I had the above commands sooner I would have loved to try, although I'm not really sure why this became an issue in the first place. I tried booting to slot B, using both patched and normal boot images but it wasn't working, unless I did something wrong.
All I remember is installing an app to edit UDID for individual apps that I've used in the past, but because it wasn't identifying root properly, to which I'm assuming is an Android 12 issue, I decided to follow instructions for manually editing such IDs in the file I edited in my OP.
After I rebooted, I remember the main system about to start and seeing the Google boot logo with a percentage # go all the way up to 90%, then that's where the boot loop started. My guess at this point is either the app or the file I edited caused an issue, because I did nothing else up until that point. What's odd, is that after I formatted the whole system and rebooted, I saw the same percentage appear on screen after installing the same app to see if that was the issue, but it booted fully just fine.
I was going to just keep fighting this and keep the phone the way it was until I could maybe fix everything, but figured there's nothing I could do at this point since trying a flash of everything failed. I was up until 5am last night and it's almost 4 am with me trying to fix this. I feel defeated and upset because I don't believe I had to wipe this in the first place, and could have likely saved all of my data. I didn't have Google's backup option turned on and hadn't backed up my text messages because I was dumb. I'm more upset with myself than the phone honestly.

RetroTech07 said:
I appreciate the help but I can't go back as I've already wiped everything minutes before you sent this. If I had the above commands sooner I would have loved to try, although I'm not really sure why this became an issue in the first place. I tried booting to slot B, using both patched and normal boot images but it wasn't working, unless I did something wrong.
All I remember is installing an app to edit UDID for individual apps that I've used in the past, but because it wasn't identifying root properly, to which I'm assuming is an Android 12 issue, I decided to follow instructions for manually editing such IDs in the file I edited in my OP.
After I rebooted, I remember the main system about to start and seeing the Google boot logo with a percentage # go all the way up to 90%, then that's where the boot loop started. My guess at this point is either the app or the file I edited caused an issue, because I did nothing else up until that point. What's odd, is that after I formatted the whole system and rebooted, I saw the same percentage appear on screen after installing the same app to see if that was the issue, but it booted fully just fine.
I was going to just keep fighting this and keep the phone the way it was until I could maybe fix everything, but figured there's nothing I could do at this point since trying a flash of everything failed. I was up until 5am last night and it's almost 4 am with me trying to fix this. I feel defeated and upset because I don't believe I had to wipe this in the first place, and could have likely saved all of my data. I didn't have Google's backup option turned on and hadn't backed up my text messages because I was dumb. I'm more upset with myself than the phone honestly.
Click to expand...
Click to collapse
Ah damn, I was too late!
The 90% thing sounds like the November Google Play services updated - mine updated yesterday and I got the same thing when I rebooted, maybe something between the two got corrupt.
Yeah, I get that, I've had more than my fair share of self inflicted (and not so self inflicted) problems that have lost me data but you live and you learn I suppose