If I do a factory reset from the menu in settings will that replace my build.prop file or will it remain the same In case your wondering I was editing what I thought was my build.prop but it was my backup.
Maybe we should start a library of stock files for occasions like this. I'm sure a generic build.prop will work fine to get it back to A100.
wildrat58 said:
If I do a factory reset from the menu in settings will that replace my build.prop file or will it remain the same In case your wondering I was editing what I thought was my build.prop but it was my backup.
Maybe we should start a library of stock files for occasions like this. I'm sure a generic build.prop will work fine to get it back to A100.
Click to expand...
Click to collapse
All that does is delete /data, /system remains the same, so no, it won't touch your build.prop. A nandroid restore or flash over will replace it.
Edit: wrong wording, it doesn't delete /data, just what's in it, the partition remains there. Not sure if it formats or just deletes the files there.
Tapatalked from my A100 - Flex Reaper RF1.
Okay thanks. I did find an old.build prop and it did not help. Thanks again
Related
So, I was planning on editing my system files to remap home to camera and turn off the capacitive buttons. I just wanted to know if a full wipe or format system will reset the keys back to normal. If not, do I have to manually edit the keys back to rest them
Lolanerd said:
So, I was planning on editing my system files to remap home to camera and turn off the capacitive buttons. I just wanted to know if a full wipe or format system will reset the keys back to normal. If not, do I have to manually edit the keys back to rest them
Click to expand...
Click to collapse
Back up the file you have to edit on the sd card. Put it back to undo your changes. Could always reflash Ur rom or restore a nandroid as well
billard412 said:
Back up the file you have to edit on the sd card. Put it back to undo your changes. Could always reflash Ur rom or restore a nandroid as well
Click to expand...
Click to collapse
Cool thanks, so flashing a ROM resets the files?
Ya cuz flashing a Rom replaces the whole system
I was wondering whether anyone has experienced the following:
I was on Team Sonic-Free GS3 v.3.0.0. Everything was setup the way i wanted it. I booted into Recovery and created a Restore point.
Right after, I did the following:
- Wipe Data/Factory Reset
- Wipe Cache partition
- Wipe Dalvik Cache
- Format /System
- Format /Data
- Format /Cache
I installed the latest Nightly from Cyanogenmod 10 (12.26). Initially I used an older version of gapps-jb but immediately flashed the correct one. Everything went fine. The system loaded and nothing seemed wrong. After some messing around I noticed it was a big sluggish on my phone. So I decided to restore the phone back to its original setting.
When I went to backup/restore and hit the Restore option, it told me that I had no recovery points! :crying::crying: At this point I started freaking out.
I tried to see if I could flash from the SDCard and I noticed one thing. This was in order to get to the main folder of the SDCard i needed to enter a folder named "0". All the files were there including my CMW recover file. Although it was on the card the recovery option was unable to see it.
After this I decided to do the following. I clean swiped again and installed the Free GS3 version i had on the SDCard already. I booted into the system and saw that the folder "0" was there but also in the main directory there were still folders. In the main portion of the card i loaded my copy of the recovery.
I went back into recovery and and tried again. The restore file was there! :good::good: I was able to recovery my original setup. Unfortunately, all of my pictures and music were still located within the newly created "0" folder. I just copied those back.
Can anyone explain why this happened? I'm very curious!
I do apologize if this has been answered before. I have done a search and have only found scenarios for the SDcard is not seen as mounted. (also dont know if the icons mean anything for the post)
*Update - Folder "0" cannot be deleted. Root explorer says "failed" and Windows Explorer says "Cannot delete 0: THe storage is write-protected". Any ideas on this also?
solidhound said:
I was wondering whether anyone has experienced the following:
I was on Team Sonic-Free GS3 v.3.0.0. Everything was setup the way i wanted it. I booted into Recovery and created a Restore point.
Right after, I did the following:
- Wipe Data/Factory Reset
- Wipe Cache partition
- Wipe Dalvik Cache
- Format /System
- Format /Data
- Format /Cache
I installed the latest Nightly from Cyanogenmod 10 (12.26). Initially I used an older version of gapps-jb but immediately flashed the correct one. Everything went fine. The system loaded and nothing seemed wrong. After some messing around I noticed it was a big sluggish on my phone. So I decided to restore the phone back to its original setting.
When I went to backup/restore and hit the Restore option, it told me that I had no recovery points! :crying::crying: At this point I started freaking out.
I tried to see if I could flash from the SDCard and I noticed one thing. This was in order to get to the main folder of the SDCard i needed to enter a folder named "0". All the files were there including my CMW recover file. Although it was on the card the recovery option was unable to see it.
After this I decided to do the following. I clean swiped again and installed the Free GS3 version i had on the SDCard already. I booted into the system and saw that the folder "0" was there but also in the main directory there were still folders. In the main portion of the card i loaded my copy of the recovery.
I went back into recovery and and tried again. The restore file was there! :good::good: I was able to recovery my original setup. Unfortunately, all of my pictures and music were still located within the newly created "0" folder. I just copied those back.
Can anyone explain why this happened? I'm very curious!
I do apologize if this has been answered before. I have done a search and have only found scenarios for the SDcard is not seen as mounted. (also dont know if the icons mean anything for the post)
*Update - Folder "0" cannot be deleted. Root explorer says "failed" and Windows Explorer says "Cannot delete 0: THe storage is write-protected". Any ideas on this also?
Click to expand...
Click to collapse
Was it registering a different recovery version when you flashed CM10 from the FreeGS? If so that would be why it didn't register the backup that you made. (I had this issue or similar to on my Touch) flashed a different rom that used CVM 5.something.. and original was a newer version. Caused me some issues. As for the folder being write protected. Try using root explorer, mount as R/W and then try to delete from there. Just ensure you have everything out of it you want tho.
milky1112 said:
Was it registering a different recovery version when you flashed CM10 from the FreeGS? If so that would be why it didn't register the backup that you made. (I had this issue or similar to on my Touch) flashed a different rom that used CVM 5.something.. and original was a newer version. Caused me some issues. As for the folder being write protected. Try using root explorer, mount as R/W and then try to delete from there. Just ensure you have everything out of it you want tho.
Click to expand...
Click to collapse
hey milky1112.
Thanks for reading and providing your input!
I actually used the sames recovery when creating and trying to restore. That's the odd part. I did recently flash the newer version within the old recovery. Do you think that may have been it? Although the new one was used to create a nandroid and restore it.
I just tried deleting using Root Explorer and the same result. It's not a big deal since its only 69mb but it's quite annoying knowing I can't.
thanks again!
solidhound said:
hey milky1112.
Thanks for reading and providing your input!
I actually used the sames recovery when creating and trying to restore. That's the odd part. I did recently flash the newer version within the old recovery. Do you think that may have been it? Although the new one was used to create a nandroid and restore it.
I just tried deleting using Root Explorer and the same result. It's not a big deal since its only 69mb but it's quite annoying knowing I can't.
thanks again!
Click to expand...
Click to collapse
That is very possible, still odd that it will not let you delete even with R/W permissions set. But as long as everything is working.. Then i wouldn't fuss too much
The new rom you installed is on 4.2 not 4.1 which is probably what you had originally. The new 4.2 releases by Google move everything into the O folder its part of the new Android set up to dual boot devices. If the recovery is not set up to correct for this your phone will not recognize where the files have been moved to. In my understanding only TWRP is corrected to do this, we'll at least in the Gnex it is. Anyone on Cwm has had issues with this. The fix is to copy and paste your files back into its original location. You can not delete O folder it is an essential part now of your system and it's where it will reference everything from and originals must remain.
Transmitted with a portable device using Xparent Blue Tapatalk 2
edfunkycold said:
The new rom you installed is on 4.2 not 4.1 which is probably what you had originally. The new 4.2 releases by Google move everything into the O folder its part of the new Android set up to dual boot devices. If the recovery is not set up to correct for this your phone will not recognize where the files have been moved to. In my understanding only TWRP is corrected to do this, we'll at least in the Gnex it is. Anyone on Cwm has had issues with this. The fix is to copy and paste your files back into its original location. You can not delete O folder it is an essential part now of your system and it's where it will reference everything from and originals must remain.
Transmitted with a portable device using Xparent Blue Tapatalk 2
Click to expand...
Click to collapse
Thanks for clarification Ed. I've been on TPR for a while so haven't flashed any 4.2 roms.
edfunkycold said:
The new rom you installed is on 4.2 not 4.1 which is probably what you had originally. The new 4.2 releases by Google move everything into the O folder its part of the new Android set up to dual boot devices. If the recovery is not set up to correct for this your phone will not recognize where the files have been moved to. In my understanding only TWRP is corrected to do this, we'll at least in the Gnex it is. Anyone on Cwm has had issues with this. The fix is to copy and paste your files back into its original location. You can not delete O folder it is an essential part now of your system and it's where it will reference everything from and originals must remain.
Transmitted with a portable device using Xparent Blue Tapatalk 2
Click to expand...
Click to collapse
hey edfunkycold,
thanks a ton for the response and clarification! i was thinking about swapping recoveries but i already reverted back to the original nandroid image i had at that point.
and you are correct. i was on 4.1 and not 4.2. i didn't know such changes were made but its great to see dual boot is coming up.
i will make sure to THANK both responses once i reach 10 posts. i'm trying hard to participate in these forums but haven't had time until recently.
Hello,
for some reason in TWRP I can't fix permissions. When I have it create a backup it fails at the point where it tries to create a folder. In the file manager I can't even rename a folder.
I'm running a CyanogenMod monthly from about 3-4 months ago, and have the latest TWRP version.
kadajawi said:
Hello,
for some reason in TWRP I can't fix permissions. When I have it create a backup it fails at the point where it tries to create a folder. In the file manager I can't even rename a folder.
I'm running a CyanogenMod monthly from about 3-4 months ago, and have the latest TWRP version.
Click to expand...
Click to collapse
Sounds strange, assuming everything else works fine. Not sure, but try updating the ROM?
latenightchameleon said:
Sounds strange, assuming everything else works fine. Not sure, but try updating the ROM?
Click to expand...
Click to collapse
Yeah, but I'd like to do a backup before I update the ROM.
I wonder if your /sdcard got write protection somehow...I thought I saw @osm0sis had a flashable zip for fixing that...apologies if I'm mistaken and sorry I'm not certain where to find this zip
Could be. But why would it only apply in TWRP? When the phone has booted everything works fine. Only in recovery do I run into problems (which makes me scared of flashing a newer ROM too...).
It should make a difference booted as well, so that's odd.
Easiest thing: Try my sdcard fix permissions zip. Might work anyway. http://v.ht/osm0
More annoying: adb pull everything (my adbsync sdcard Backup might make that easy for you), format data, push it all back then run my sdcard fix permissions zip.
do you use encryption?
osm0sis said:
It should make a difference booted as well, so that's odd.
Easiest thing: Try my sdcard fix permissions zip. Might work anyway. http://v.ht/osm0
More annoying: adb pull everything (my adbsync sdcard Backup might make that easy for you), format data, push it all back then run my sdcard fix permissions zip.
Click to expand...
Click to collapse
I couldn't flash the zip. It failed.
No encryption.
wow. My phone is trying to screw me. Again and again and again. I've tried wiping the sdcard, didn't work. Had to factory reset it. Now that part was ok. Used TitaniumBackup to restore my phone. Reboot... and it was stuck at the boot screen.
Had to factory reset again, this time only let TitaniumBackup install my apps and their settings. Have to set up the system itself again.
Since I am using a VPN I need to lock the screen with a PIN (I hate that, but oh well... Android forces me). After I have set up the VPN, everything was working fine, at some point my phone crashed. And after it started again, I could not enter the PIN code anymore. I was locked out of my phone. The phone still displayed that I pressed a number, but no number did appear. Aaaand factory reset, AGAIN!
Really? What the hell is wrong? I'm worried it might be a hardware problem. The USB port is not working properly anymore, most of the time, and I'm afraid the built in memory is gone. Oh how I hate that. My HTC had the SD card die, but replacing it fixed it. I have a LG with fixed built in storage, where the memory died. Since I was overseas for a couple of months, and LG refuses to fix phones outside of the country it was bought, I had a brick for a few months. And now it seems to have hit my Galaxy Nexus. Yay. Who thought fixed built in storage was a good idea?
Hi,
I am running Carbon Mod Nightly Rom, I was looking at the Volume Blaster Mod (http://forum.xda-developers.com/showthread.php?t=2563209) to raise the volume up on the external speaker. I edited the file system/etc/snd_soc_msm/snd_soc_msm_2x. Somehow I screwed the file up after editing. After I edited it and rebooted, it gets stuck at the Carbon Logo and doesn't go any further :crying:. I have a nandroid backup, but I didnt backup until after I edited the file (before reboot). So I'm wondering can I or how do I replace the edited file (snd_soc_msm_2x) with the original file. I have the original file on the SD card in the phone. I went into the TWRP Recovery and into file manager, but I could not locate the location of the edited file from within there (system/etc/snd_soc_msm/snd_soc_msm_2x). Can someone please help me restore this one file so that my phone will boot up or tell me how would be the best way of getting my phone up and working again ASAP. Oh, I have tried exploring the backup created with Nandroid Backup Manager, well I found the file thats corrupted and opened it with File manager, select all- then delete, then pasted the contents from the working file, and then try to save, and I get an error "Operation Failed". So any help would be greatly appreciated.!!
Thanks in Advance
If you cant see files in /system, you just need to mount it first. Otherwise, just dirty flash the same rom.
DocHoliday77 said:
If you cant see files in /system, you just need to mount it first. Otherwise, just dirty flash the same rom.
Click to expand...
Click to collapse
Dirty Flash? I'm new to all this, so I need some help with the slang. I can explore the contents of the Nandroid backup, are there anyway possible to delete a file in the Nandroid backup and replace it with another file?? If I can do that, then I can replace the corrupted file and then restore from backup. I just dont want to reflash the clean ROM and then have to manually restore all my apps, sms and photos...
If I flash the backup Rom that has the corruted file, and before reboot, can I use the file manager to pull the clean file from the external card and replace the one that corrupted in the root folder. If I can do this, then it should boot normally. Otherwise if I boot with the corrupted file it gets hung after it processes all the apps. (Gets hung on Starting Apps).
I figured it out!!! What I did was I went into recovery, and selected the recovery nandroid backup file that was corrupted. Instead of restoring all the available options, I unchecked System. So it restored everything but the system data. The system data already installed was from the newly installed rom that was working, so by leaving the system unchecked it didnt install the corrupted system from backup! I hope I explained this where you can understand it.
Thanks for all the help DocHoliday77!! I'm just glad that worked and I dont have to manually install everything back over!!
:victory:
So after tinkering around with the AFTV (mounting external usb as internal, etc) , i decided to start fresh. I did a factory reset, but noticed that there's stuff that's still around. for example, I noticed there's an /emulated/legacy folder with some old stuff like my XBMC folders even though after the factory reset I installed SPMC. Also when I installed the ikonoTV app again, it already had the XBMC icon switched in still. Is it correct that the factory reset just wipes a certain portion and leaves others (the "SDcard" portion of the AFTV)? If so, how do i fully go fresh start with everything wiped?
Thanks
Boot into clockwork recovery, wipe /data and /system and reflash the pre rooted software version you want. It will even make you watch the welcome video again. Make sure you have updates blocked on router because com.Amazon.dcp will not be disabled until you disable it again.
Thanks! I guess I need to wipe /system as well then.
Router is blocking the updates so should be good.
barrist said:
Thanks! I guess I need to wipe /system as well then.
Router is blocking the updates so should be good.
Click to expand...
Click to collapse
Factory reset will not FORMAT /data, but just delete everything but /data/media, which is /sdcard. There is a separate option for wiping /data & /data/media. If you wipe /system you must be extra careful you NEVER attempt to reboot before reflashing something onto it.
Do you think it's useful to wipe the system or should wiping data media be enough for a fresh start ?
Sent from my iPhone using Tapatalk
barrist said:
Do you think it's useful to wipe the system or should wiping data media be enough for a fresh start ?
Sent from my iPhone using Tapatalk
Click to expand...
Click to collapse
As long as you didn't change /system, there is no point in touching it. But like I said, if you do, make absolute sure to reflash something.
I got a bit of a problem here.
I extracted two .obb folders with FolderMount to my usb drive and then set my aftv (running your pre-rooted 51.1.4.0_514006420) back to factory settings + did wipe cache, data and dalvik in recovery.
all runs fine except I can not enter the usb drive.
stickmount shows it is mounting "sdcard/usbStorage/sda1" but I can not access it, neither in ESFile explorer nor FolderMount.
sdcard/usbStorage/sda1 is showing the two empty .obb folders and I can not change them.
I just reinstalled 51.1.4.0_514006420 from recovery but saw there is a lot of junk left + the same problem with the usb drive.
how can I safely wipe to a totally clean 51.1.4.0_514006420 ?
best
rbox said:
As long as you didn't change /system, there is no point in touching it. But like I said, if you do, make absolute sure to reflash something.
Click to expand...
Click to collapse
Hi, sorry to jump on this discussion but I think I may well of done this exact process and rebooted before reflashing.
My fire tv will now only boot to the White Amazon logo and won't revert to factory restore at all using the alt-print screen-I method. All I can manage is constant reboots.
Any ideas?
Does this mean I have in fact bricked my fire to and there's no way back for me?
Paul