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. I want my phone fixed without losing any data. Can anyone help?
Reflash your rom or a newer build
Envoyé depuis mon Blade avec Tapatalk
If I do that won't I lose my phones internal memory data for my apps.
Aaqib1 said:
If I do that won't I lose my phones internal memory data for my apps.
Click to expand...
Click to collapse
No, Just flash it by the recovrry. It will rempoace system files, not the data
Envoyé depuis mon Blade avec Tapatalk
I've fixed it. I find that I had build.prop.bak in the system folder and I renamed it to build.prop and it worked. Thanks for your help anyway. This post is closed.
Sent from my Blade using xda app-developers app
Aaqib1 said:
I've fixed it. I find that I had build.prop.bak in the system folder and I renamed it to build.prop and it worked. Thanks for your help anyway. This post is closed.
Sent from my Blade using xda app-developers app
Click to expand...
Click to collapse
How did you access /system if u couldn't boot
I couldn't boot up the phone but I could boot into clockworkmod recovery. I mounted the system and went to adb. I typed 'adb shell' and changed directory to system. Then I did 'ls' and found that there was a backup of the file that I had changed. The backup was called build.prop.bak so using adb shell I typed 'mv build.prop.bak build.prop' which renamed the file to build.prop and then I rebooted and it worked.
Sent from my Blade using xda app-developers app
Related
hi
Ive rooted my nexus s & unlocked the boot-loader
installed superuser
Ive tried installing CWM a couple of times
it installs
but after reboot no recovery or CWM
checked the following posts but no luck
it says install aborted
http://forum.xda-developers.com/showthread.php?t=1317524
http://forum.xda-developers.com/showthread.php?t=1098168
Read : http://forum.xda-developers.com/showthread.php?t=895545
as far as i remember, CWM will be removed each time you restart your phone,unles you have a custom kernel/rom.
but its been long time ago when i did that x3
If stock there is a file that needs to be removed or renamed,
Sent from my Nexus S using XDA Premium App
Try to flash again.... Works for me...
ghost010 said:
Read : http://forum.xda-developers.com/showthread.php?t=895545
as far as i remember, CWM will be removed each time you restart your phone,unles you have a custom kernel/rom.
but its been long time ago when i did that x3
Click to expand...
Click to collapse
No. You merely need to rename / remove the install-recovery.sh script in /etc to prevent the stock recovery from writing at boot.
Sent from my Nexus S using xda premium
krohnjw said:
No. You merely need to rename / remove the install-recovery.sh script in /etc to prevent the stock recovery from writing at boot.
Sent from my Nexus S using xda premium
Click to expand...
Click to collapse
Thanks I to was having the same issue. I assume that to revert you just rename the aformentioned file back to original?
Sent from my A500 using xda premium
spaz2k7 said:
Thanks I to was having the same issue. I assume that to revert you just rename the aformentioned file back to original?
Sent from my A500 using xda premium
Click to expand...
Click to collapse
Yeah, restoring the file will then cause the stock recovery to be written upon reboot (if you want to go back to the stock recovery for some reason).
same but i solved it
clockworkmodrecovery rom manager find and install
open it and touch flash clockworkmod recovery(first item)
select reboot into recovery manual
mount and storage select
mount USB storage
unmount
++++ go back +++++
install from zip sdcard
find
'' super user.zip'' flash
reboot
es file explorer select setting mark root explorer and mount file system after
select phone in file explorer find etc folder select and find ''install-recovery.sh'' file and rename file for example ''install-recovery.sheski'' and
open rom manager again touch flash clockworkmod recovery(first item)
check it...
Ok, never seen this before and suspect SD card corruption.
I did a nandroid backup today before I flashed a custom kernel. Everything went well. Now I am getting low space alerts (got the 8GB model). I want to delete the backup which comes in at 1.8GB. Problem is, the permissions are wacky - the folder perms are rwsrwsr-t (775 with set uid, set gid and sticky).
I can't delete or change permissions with either root explorer or from the shell as root!
Has anyone seen this before, or have a solution ?
timekillerj said:
Ok, never seen this before and suspect SD card corruption.
I did a nandroid backup today before I flashed a custom kernel. Everything went well. Now I am getting low space alerts (got the 8GB model). I want to delete the backup which comes in at 1.8GB. Problem is, the permissions are wacky - the folder perms are rwsrwsr-t (775 with set uid, set gid and sticky).
I can't delete or change permissions with either root explorer or from the shell as root!
Has anyone seen this before, or have a solution ?
Click to expand...
Click to collapse
Same here. No clue how to get rid of it.
This is what I did when I switched from CWM to TWRP
1. Get Root Explorer
2. Navigate to /data/media/clockworkmod/backup
3. Delete whatever backups
4. ?????
5. PROFIT!
Sent from my i777 using xda app-developers app
Its a common issue with some versions of CWM, but Koush has released a (radically) new version
fix is as Wiithepeng said
wiithepeng said:
This is what I did when I switched from CWM to TWRP
1. Get Root Explorer
2. Navigate to /data/media/clockworkmod/backup
3. Delete whatever backups
4. ?????
5. PROFIT!
Sent from my i777 using xda app-developers app
Click to expand...
Click to collapse
"I can't delete or change permissions with either root explorer or from the shell as root!"
If I delete with root explorer I get "delete failed". If I adb shell in and `busybox rm -fR` I get "Operation not permitted"
With those steps?
Sent from my i777 using xda app-developers app
When I tried deleting from /mnt/sdcard or /sdcard or /storage/sdcard0 it would not work until I tried /data/media
Sent from my i777 using xda app-developers app
Phonic posted a script in the "[RECOVERY] r3 (6.0.0.4) - Interim ClockworkMod recovery for Nexus 7" thread in the Android Dev forum,
when executed thru CWM will delete undeleteable backups
didnt use it myself, I used Solid Explorer to delete /data/media/clockworkmod/backup/......
Ok, I rebooted into recovery and was able to delete the files with adb shell.
wiithepeng: Sorry, didn't see the /data/media path at first glance, I was going straight to /sdcard - so it might have worked your way.
Thanks for the help.
No problem. Glad you delete those backups
Sent from my i777 using xda app-developers app
Try THIS. Common problem and fixed in the newest version of the Recovery from that thread AND apparently the newest CWM directly from Koush.
wiithepeng said:
This is what I did when I switched from CWM to TWRP
1. Get Root Explorer
2. Navigate to /data/media/clockworkmod/backup
3. Delete whatever backups
4. ?????
5. PROFIT!
Sent from my i777 using xda app-developers app
Click to expand...
Click to collapse
Thank Bro, this was bugging the crap out of me. I had no idea to navigate through data/media etc. Good fix!
wiithepeng said:
This is what I did when I switched from CWM to TWRP
1. Get Root Explorer
2. Navigate to /data/media/clockworkmod/backup
3. Delete whatever backups
4. ?????
5. PROFIT!
Sent from my i777 using xda app-developers app
Click to expand...
Click to collapse
Thanks! I was about to tear my hair out! I used ES File Explorer though.
wiithepeng said:
This is what I did when I switched from CWM to TWRP
1. Get Root Explorer
2. Navigate to /data/media/clockworkmod/backup
3. Delete whatever backups
4. ?????
5. PROFIT!
Sent from my i777 using xda app-developers app
Click to expand...
Click to collapse
Thanks bro... Root Explorer is premium so even ES File Explorer works as long as you are rooted and grant it SU access, which would be anyway as you have CWM.
Sent from my Nexus 7 using Tapatalk 2
wiithepeng said:
When I tried deleting from /mnt/sdcard or /sdcard or /storage/sdcard0 it would not work until I tried /data/media
Sent from my i777 using xda app-developers app
Click to expand...
Click to collapse
This worked for me :good:
Wahay, Fix ed
I was going to make a zip and flash as i thought all was lost but then I just fixed this via adb using the following commands, I didn't get any errors and it was successful, here is what I did,
# cd /data/media/clockworkmod/
# chmod 777 backup
# cd backup
# rm -rf <backupfilename>
Hope this helps others,
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
I'm trying to install the update. The update said something is changed in the system/bin/app_process. So using root Explorer I saw app_process and app_process.orig.
Thinking the app_process.orig is the unchanged one. I renamed the app_process to app_process.new.
I was trying to rename app_process.orig to app_process but somehow root Explorer can't so I rebooted.
Now its not booting up. Is there a way I can go to the files without booting up and rename the app_process?
Sent from my GT-N7100 using Tapatalk 4
BratPAQ said:
I'm trying to install the update. The update said something is changed in the system/bin/app_process. So using root Explorer I saw app_process and app_process.orig.
Thinking the app_process.orig is the unchanged one. I renamed the app_process to app_process.new.
I was trying to rename app_process.orig to app_process but somehow root Explorer can't so I rebooted.
Now its not booting up. Is there a way I can go to the files without booting up and rename the app_process?
Sent from my GT-N7100 using Tapatalk 4
Click to expand...
Click to collapse
Some custom recoveries (TWRP) will let you browse the files on your device. I know that files can be copied, moved, deleted - I do not know if they can be renamed. My guess is yes, though. If you can boot to recovery go ahead and try that.
If you can't boot to recovery do you at least have ADB access? You can always ADB push the file you want if you do. There are guides out there if you don't know how to do it. I google for a quick refresher every time I have to ADB push a file.
I'm on stock recovery, I can see the device with 'fastboot devices' but 'adb devices' can't see my device? Is this a problem of driver? Or because I haven't checked the developers option? If I can only access the device I can rename back that file.
Sent from my GT-N7100 using Tapatalk 4
Just reinstalled everything from fastboot. Please close this thread.
Sent from my Nexus 7 using Tapatalk
@moonbutt74 i tried using your updater.script it flashed fine. I am no longer stuck at the samsung galaxy tab 4 logo but i am now stuck at the sparkling samsung logo.
Sent from my SAMSUNG-SGH-I337 using XDA Free mobile app
trazfer said:
@moonbutt74 i tried using your updater.script it flashed fine. I am no longer stuck at the samsung galaxy tab 4 logo but i am now stuck at the sparkling samsung logo.
Sent from my SAMSUNG-SGH-I337 using XDA Free mobile app
Click to expand...
Click to collapse
Ahh, okay your boot.img/kernel is skunky, or very likely skunky, see if you can access via adb shell
and if so run mount to see what there/correct/missing/wrong.
m
@trazfer
just a thought, if you removed or altered fusedlocation apk that will cause a hang/loop
also if you modified the system directory structure with additional directories, you need to
account for those additions in the permission settings portion lf the updater-script.
generally the permissions for system directories= 755 libraries,configs,xml's and such= 644 binaries= 755
also try after rom flash to custom restore your stock boot.img from your full stock backup
and see if you boot through. If you still hang then the problem is in system, and likely in any /system/addon.d
scripts [init.d] you may have added/modified.
moonbutt74 said:
Ahh, okay your boot.img/kernel is skunky, or very likely skunky, see if you can access via adb shell
and if so run mount to see what there/correct/missing/wrong.
m
@trazfer
just a thought, if you removed or altered fusedlocation apk that will cause a hang/loop
also if you modified the system directory structure with additional directories, you need to
account for those additions in the permission settings portion lf the updater-script.
generally the permissions for system directories= 755 libraries,configs,xml's and such= 644 binaries= 755
also try after rom flash to custom restore your stock boot.img from your full stock backup
and see if you boot through. If you still hang then the problem is in system, and likely in any /system/addon.d
scripts [init.d] you may have added/modified.
Click to expand...
Click to collapse
Thanks for the reply. I will look in to ot this weekend.
Sent from my SAMSUNG-SGH-I337 using XDA Free mobile app
@moonbutt74 , @trazfer
hi ,
promeo123 present Custom ROM T530NU based on T530NUUEU1ANK1-XAR stock .
Look here http://forum.xda-developers.com/showpost.php?p=58279898&postcount=3