Database Users

[HELP] I need to restore build.prop

Hello XDA-Developers. I am using the a rooted Orange San Francisco (ZTE BLADE) running CM 7.1 Stable. I was reading a guide on how to edit the build.prop file in the /system/ directory in order to get access to some previously incompatible apps:
howtogeek.com/116456/how-to-install-incompatible-android-apps-from-google-play
I tried it and changed the two lines to 'samsung' and 'Nexus S'. When I rebooted my device later it only showed the green android boot logo and did not proceed booting any further. Its still stuck like that. I have got a copy of the original build.prop file locally on my c:\ drive. I read that you can sort this problem out by using adb. I have got adb set up and now I don't know what to do next and have tried pushing the backup to the device but it says no space left on device. I want my phone fixed without losing any data. Can anyone help?

Why did u create another thread?

Because unfortunately I got myself stuck in the same situation again but this time without the build.prop.bak. I have the original stored locally on my c:\ drive but when i try to push it to my phone through adb it says 'no space left on device'. Can you help? and how do I delete the previous thread?

Why you dont use the other tread? And there is a way to recover back your phone in the other thread...
And y u no do backup with your recovery ???
Envoyé depuis mon Blade avec Tapatalk

Your right from now on im going to backup ervery week. My last backup is from all the in june last year. I didn't want to restore that one cos i'd lose all my game progress and my new apps. When i push the file through adb it says no space left on device. Any ideas what i could do. or any way to get that file to the system directory?

This trick should solve your problem:
- Grab the same build of CM you flashed on your phone from http://get.cm/?device=blade&type=stable (I assume you really have 7.1 stable and not 7.2/nightly/RC)
- Put it on your SD-Card with Gapps (upgraded Gapps by targetbsp: http://blade.windows98.co.uk/downloads/gapps-gb-20110828f-signed.zip )
- Do a Nandroid backup just to be safe (if after the whole procedure phone still won't work you can go back to the previous state with this backup)
- Go to Mounts and Storage > Format /system
- Flash without wipe (or ONLY with dalvik cache wipe)
- Reboot and check if the phone works.
Data/Games/Applications are stored on /data while the OS/Rom is stored on /system. If you don't wipe/format /data you won't lose any application, but with a /system format + reflash every file on /system will be recreated (including your broken build.prop).
EDIT: If you're using a APP2SD/Link2SD/Simple2EXT script or anything that moves application to /sd-ext, I think that you have to also reflash / recreate the script, otherwise you won't see any app moved to the sd-card's ext partition.

Thank you so much. It worked. I'm back in. I'm going to backup weekly from now on. Thanks you to:
ctrl+alt+delete, quantumfoam and gokh for contributing and helping me out.

Aaqib1 said:
Thank you so much. It worked. I'm back in. I'm going to backup weekly from now on. Thanks you to:
ctrl+alt+delete, quantumfoam and gokh for contributing and helping me out.
Click to expand...
Click to collapse
Lol, just backup before flashing somerhing or modifing system files
Envoyé depuis mon Blade avec Tapatalk

I was trying to do the same thing for game loft games it wasn't working so i found another site that said to edit the ro fingerprint and directory now I'm stuck with a black home screen and the twlauncher force close loop i can't access anything from my phone if i'm lucky i can bring up task manager but that does nothing i don't have clockwork or any other back up i have tried a hard reset several time and that hasn't worked please help

[Q] Why can I not delete my /sdcard/clockworkmod folder?

So I've installed a custom ClockworkMod recovery and ROM on my Nexus 7 tablet. Life was good. Recently, I was running out of space and decided to delete my CWM backup (after saving it to my computer). And then, I realized I couldn't.
I went into ES File Explorer to try. I couldn't do it there.
I went into the ADB shell as root to try to remove it. No luck again, just the message when I finally DID try to remove one file:
Code:
# rm boot.img
rm failed for boot.img, Operation not permitted
What am I doing wrong?
Edit: This looks like it's ClockWorkMod (5.8.??)'s fault, but besides reading that another backup won't make the current one much larger, I don't actually know how to delete the current one.

Try "rm -rf ddd" (where "ddd" is the directory name) on the directory containing the files.
Sent from my Nexus 7

BillGoss said:
Try "rm -rf ddd" (where "ddd" is the directory name) on the directory containing the files.
Sent from my Nexus 7
Click to expand...
Click to collapse
in the development section there is a cwm flashable.zip that will delete them.. Then upgrade to latest cwm or TWRP.. its a bug from older version of cwm.. its talked about in the dev cwm thread..
good luck..

I did this in a way not mentioned here that still deserves mentioning... First I updated to the latest version of CWM available (via the Nexus 7 Toolkit) and then booted into recovery, opened the backup option, deleted the backup that was there, then cleaned the nandroids.
I could not find the aforementioned flashable zip, and because of the new CWM I had, I wanted to attempt a proper method of removal before running another rm command via the terminal. Therefore I could not verify the other methods mentioned here, my apologies.

erica_renee said:
in the development section there is a cwm flashable.zip that will delete them.. Then upgrade to latest cwm or TWRP.. its a bug from older version of cwm.. its talked about in the dev cwm thread..
good luck..
Click to expand...
Click to collapse
primetechv2 said:
I could not find the aforementioned flashable zip, and because of the new CWM I had, I wanted to attempt a proper method of removal before running another rm command via the terminal. Therefore I could not verify the other methods mentioned here, my apologies.
Click to expand...
Click to collapse
Sorry for re-opening an old thread, but I am having a problem where I have files that I cannot delete from the clockworkmods/blobs folder on my external sd card. So far, I have tried deleting them from a file explorer, deleting them as root from a file explorer, root and non-root deletes from terminal emulator, deleting through windows, adb shell deletes (with system booted).
I also wanted to try adb shell while booted into cwm, but I could not get the adb connection to work from recovery.
I also tried to find the zip file in the developer section and that's the real reason why I revived this thread...Does anyone know where the thread is with the zip file to remove these files?

I think the only way to delete them is through cwm.Boot to recovery and use the menu to delete them.
Sent from my SGH-I927 using xda app-developers app

Kodiack99 said:
I think the only way to delete them is through cwm.Boot to recovery and use the menu to delete them.
Sent from my SGH-I927 using xda app-developers app
Click to expand...
Click to collapse
When I booted to recovery, I am able to delete each of the backups that I created. These all deleted correctly. I then went to Free unused backup files (to delete the files/folders in the blobs folder) and ran that and most of the files are gone. When I boot back into the phone, there are still some files/folders there and they seem to be taking up about 4-5 GB on the card. When I try to delete them through the file manager apps (either as root or not) they will not delete and the manager reports an error (before clicking delete, the manager displays a statistics report that says that the size of the files are over 2TB so obviously something is very messed up about them). I have also tried to delete them through the terminal (again as root and regular user) and they will not delete there either and they totally mess up the terminal window with unprintable characters (the only way to recover is to exit out of the current window and start a new one).
I finally fixed this problem last night by backing up all of my stuff (except the clockworkmod folder) to my computer. I then rebooted into recovery (latest version of CWM non-touch) and formatting the ext SD Card. When I rebooted there were still some folders there (including the clockworkmod folder). I did a format from within the OS and that cleared everything out. I copied all of my stuff back from my computer and I'm now good to go. Not sure how it got messed up to begin with, but the problem is fixed now. I think I'm going to stick with TWRP from now on.

Nexus 7 partition table messed up/ broken?

Flashed a rooted stock Android 4.2 ROM, root appeared to be broken so i figured rather than be late for work i'd flash my nandroid backup i did beforehand. Now recovery can't find the backup location, and under any file explorer it appears as '0' which i have to select first to view the files. Because of this CWM can't see the backup folder. HELP

That's because of the 4.2 multi-user feature, it needs to separate files of multiple users somehow, so it just moves all your files to "0" subdirectory. If you add another users, they will have their own folders.
It should be okay to just move /data/media/0/TWRP to /data/media/TWRP, either via TWRP's file manager or via adb shell while in recovery:
Code:
mv /data/media/0/TWRP /data/media/

Tasssadar said:
That's because of the 4.2 multi-user feature, it needs to separate files of multiple users somehow, so it just moves all your files to "0" subdirectory. If you add another users, they will have their own folders.
It should be okay to just move /data/media/0/TWRP to /data/media/TWRP, either via TWRP's file manager or via adb shell while in recovery:
Code:
mv /data/media/0/TWRP /data/media/
Click to expand...
Click to collapse
Thank you for your help but I'm using clockworkmod recovery. What do i need to change in that command to suit CWM?

Matty Matt said:
Flashed a rooted stock Android 4.2 ROM, root appeared to be broken so i figured rather than be late for work i'd flash my nandroid backup i did beforehand. Now recovery can't find the backup location, and under any file explorer it appears as '0' which i have to select first to view the files. Because of this CWM can't see the backup folder. HELP
Click to expand...
Click to collapse
Haha, I thought I was the only one! I thought I had partitioned my card somehow. I basically did the same thing as you. I also am running CWM. Its making Rom flashing almost impossible for me, I can only select & flash files from the SD "O". All my nandroids are on the regular SD selection. Did you ever find you answer Matt.?
Sent from my Nexus 7 using Tapatalk 2

[Q] Understanding Directories, and Backing Up

I want to make a backup of my Android I9505 by copying all the files to my laptop.
I don't understand the directories
Using ES3 I see
/ Device (Which I guess is root.)
0
extSdCard
I assume that exdSdCard is (as it almost says) the external SD Card.
So what are "/" and
"0"
I guess I should back up all directories. What do you think?

webmanoffesto said:
I want to make a backup of my Android I9505 by copying all the files to my laptop.
I don't understand the directories
Using ES3 I see
/ Device (Which I guess is root.)
0
extSdCard
I assume that exdSdCard is (as it almost says) the external SD Card.
So what are "/" and
"0"
I guess I should back up all directories. What do you think?
Click to expand...
Click to collapse
Hi,
0 is your internalSD ( /storage/ emulated/0/ )
/ is root directory
If you just copy folder like that , yes you will make a copy of the folders and the data inside of them but it will not work to restore your system , for that you will need something like a Nandroid copy or use Titanium Backup to be re install after you restore your rom

webmanoffesto said:
I want to make a backup of my Android I9505 by copying all the files to my laptop.
I don't understand the directories
Using ES3 I see
/ Device (Which I guess is root.)
0
extSdCard
I assume that exdSdCard is (as it almost says) the external SD Card.
So what are "/" and
"0"
I guess I should back up all directories. What do you think?
Click to expand...
Click to collapse
You are WAY overthinking this.
Install custom recovery. Use it to make a Nandroid backup.
That's a single zip file that you can later use to restore everything in exactly the same state as it was the day you made the backup. (Takes all of 5 minutes.)
Then if you want to store that backup zip file on your PC you can easily copy it to the computer and store it there for as long as you need.
Your way of doing this will take a lot longer to copy the files and won't ultimately work to restore the system.

Skipjacks said:
You are WAY overthinking this.
Install custom recovery. Use it to make a Nandroid backup.
That's a single zip file that you can later use to restore everything in exactly the same state as it was the day you made the backup. (Takes all of 5 minutes.)
Then if you want to store that backup zip file on your PC you can easily copy it to the computer and store it there for as long as you need.
Your way of doing this will take a lot longer to copy the files and won't ultimately work to restore the system.
Click to expand...
Click to collapse
Using ROM Manager, I boot to Recovery mode. I only see
- Reboot system now
- apply update from ADB
- Apply update from external storage
- wife data/factory reset
- wipe cache partition
- apply update from cache
No Backup option.

webmanoffesto said:
Using ROM Manager, I boot to Recovery mode. I only see
- Reboot system now
- apply update from ADB
- Apply update from external storage
- wife data/factory reset
- wipe cache partition
- apply update from cache
No Backup option.
Click to expand...
Click to collapse
Hi ,
Then i guess you are 100% stock , no root , no Custom recovery?
if so then you need an app that does not need root to back up your app , Titanium is good but you need at least to be root.

MAX 404 said:
Hi ,
Then i guess you are 100% stock , no root , no Custom recovery?
if so then you need an app that does not need root to back up your app , Titanium is good but you need at least to be root.
Click to expand...
Click to collapse
I have Root and I use Titanium Backup.

webmanoffesto said:
I have Root and I use Titanium Backup.
Click to expand...
Click to collapse
you are root but you do not wish to install a Custom recovery or custom rom , right?
If so use titanium to make a back up of your apps , contacts , settings , email , sms ..etc etc
If you want to make a nandroid you need to install a Custom Recovery

Just install a custom recovery.
It won't affect the operation of the ROM at all if you're completely happy with the stock rom.
Root and Recovery are mutually exclusive things. One has nothing to do with the other. Each exists independently of the other.

Skipjacks said:
Just install a custom recovery.
It won't affect the operation of the ROM at all if you're completely happy with the stock rom.
Root and Recovery are mutually exclusive things. One has nothing to do with the other. Each exists independently of the other.
Click to expand...
Click to collapse
+1

[PSA] lollipop sdcard/TWRP directory permissions problem

I upgraded to motorola's 5.02 lollipop last week. Beautiful - no problems worth mentioning.
Then I wanted to try xposed, so I went into TWRP and made a backup. No problems with xposed. It is working fine.
But, I noticed a disk space inconsistency and a problem with the /sdcard/TWRP directory. Here are the symptoms:
Under settings->storage, it did not show my TWRP backups under "misc", but it counted the space as used in the numeric free space.
I tried to look at /sdcard/TWRP/ in es file explorer, but TWRP showed up as a file and not a directory.
At the command line, I got permission denied when I tried to cd into or ls the /sdcard/TWRP directory.
I could not see the /TWRP directory using my PC via USB/MTP while in android.
I could not delete /sdcard/TWRP within es file explorer or at the command line.
The TWRP directory was available and seemed fine at /data/media/0/TWRP.
Within TWRP recovery (v2.8.5.0), I had no problem viewing or deleting the TWRP directory, but when I made a new backup, the problem came back.
I googled and found a number of people with the same problem. (ie http://forum.xda-developers.com/google-nexus-5/general/sdcard-problems-upgrading-android-t2938749)
This fixes half of the problem. After running this, the TWRP ?file? was a directory again and the space was seen in storage under "misc":
Code:
su
restorecon -FR /data/media/0
But, I still did not access to read TWRP as either root in the terminal or from es file explorer. I noticed the owners were not the same as other directories. This fixed that problem:
Code:
su
chown -R media_rw:media_rw /data/media/0/TWRP
Now, I seem to finally have control over the /sdcard/TWRP directory. Whew!
I did not try a restore, and read where others were having trouble restoring lollipop (bootloops or /data missing) with older versions of TWRP. I would be interested to hear if anyone had successfully restored lollipop /data/ using TWRP.
edit: I was forced to restore system and data.. It worked....

Ctrl-Freak said:
I did not try a restore, and read where others were having trouble restoring lollipop (bootloops or /data missing) with older versions of TWRP. I would be interested to hear if anyone had successfully restored lollipop /data/ using TWRP.
Click to expand...
Click to collapse
About 2 weeks ago I had restored the Motorola 5.0.2 backup posted here on XDA [Link Removed by Mods due to Moto Policies]. I had the SELinux storage access problem. Then I restored the CM12 nandroid i had then.
No problem occurred. All of my data in /data is still intact.

Ctrl-Freak said:
I upgraded to motorola's 5.02 lollipop last week. Beautiful - no problems worth mentioning.
Then I wanted to try xposed, so I went into TWRP and made a backup. No problems with xposed. It is working fine.
But, I noticed a disk space inconsistency and a problem with the /sdcard/TWRP directory. Here are the symptoms:
Under settings->storage, it did not show my TWRP backups under "misc", but it counted the space as used in the numeric free space.
I tried to look at /sdcard/TWRP/ in es file explorer, but TWRP showed up as a file and not a directory.
At the command line, I got permission denied when I tried to cd into or ls the /sdcard/TWRP directory.
I could not see the /TWRP directory using my PC via USB/MTP while in android.
I could not delete /sdcard/TWRP within es file explorer or at the command line.
The TWRP directory was available and seemed fine at /data/media/0/TWRP.
Within TWRP recovery (v2.8.5.0), I had no problem viewing or deleting the TWRP directory, but when I made a new backup, the problem came back.
I googled and found a number of people with the same problem. (ie http://forum.xda-developers.com/google-nexus-5/general/sdcard-problems-upgrading-android-t2938749)
This fixes half of the problem. After running this, the TWRP ?file? was a directory again and the space was seen in storage under "misc":
Code:
su
restorecon -FR /data/media/0
But, I still did not access to read TWRP as either root in the terminal or from es file explorer. I noticed the owners were not the same as other directories. This fixed that problem:
Code:
su
chown -R media_rw:media_rw /data/media/0/TWRP
Now, I seem to finally have control over the /sdcard/TWRP directory. Whew!
I did not try a restore, and read where others were having trouble restoring lollipop (bootloops or /data missing) with older versions of TWRP. I would be interested to hear if anyone had successfully restored lollipop /data/ using TWRP.
edit: I was forced to restore system and data.. It worked....
Click to expand...
Click to collapse
hi, im having the same problem as you. I was on cm12, reverted to 4.4.4 and took the OTA, i then flashed TWRP and did a backup of the stock rom, but I cant see the file on ES Explorer and its taking space like you said. The problem is I didnt understand how you fixed it. Could you explain please? Whats the code you mention on the solution? where do you enter it?
Edit: I managed to flash a backup of the rom i was running prior to KitKat via OTG cable. TWRP recognized the backup when i made a couple of folders: TWRP/BACKUPS/TA000021JN and i flashed. As soon as the phone booted up I was able to see the TWRP folder on ES Explorer again so i think it 's probably fixed?

Cristian314 said:
hi, im having the same problem as you. I was on cm12, reverted to 4.4.4 and took the OTA, i then flashed TWRP and did a backup of the stock rom, but I cant see the file on ES Explorer and its taking space like you said. The problem is I didnt understand how you fixed it. Could you explain please? Whats the code you mention on the solution? where do you enter it?
Click to expand...
Click to collapse
Terminal emulator (app), I just tried it, works [emoji2]
Enviado desde mi XT1058 mediante Tapatalk