Hello all,
I have a Samsung Galaxy Note i717. I have installed a few ROM's, but recently I installed CM9 unofficial build. After it was installed, I noticed that my build.prop is only like 4 lines long. So I try and add stuff to it (I am rooted, and used RW mode in Root Explorer). I can close the file and save changes successfully, but when I reboot it is back to the way it was with the 4 lines. It is not only that though, any files i add to the "/" get deleted upon reboot.
Things I have tried:
ODIN to stock rom, still did not have a full build.prop
Tried many different ways to change file system (different programs)
Ran fix permissions in CWM and busybox installer script
All with no success. Is there anything else I can try to fix this and be able to edit my "/" and have changes take affect. Or has anyone had this issue before?
Thanks
So no one has any idea what's happening? Is there a way to completely wipe everything and start fresh? Like format the whole internal file system like a brand new phone?
Sent from my SAMSUNG-SGH-I717 using Tapatalk 2
Related
Epic 4G
Rooted my phone last night, everything went well. All I was going to do was make my phone compatible with netflix, so I edited my build.prop to do that. All that process did was make my Swype keyboard stop working.
The first time, I used ES File Manager to copy build.prop out of the system folder, pasted to SD card, edited it, cut it from SD card and I put it back in system, overwriting the build.prop that was in there. No problems. When I attempted to do that again, I got the error "build.prop cannot be moved!" I did the exact same process, only now it wasn't letting me do it.
So I was googling ways to restore build.prop, and someone said to flash a different rom. I attempted to flash Syndicate ROM. I followed all the instructions just as there were at Samsung Epic Hacks.com, and now my phone is frozen at the first screen that happens on boot "Samsung/ww w.samsungmobile.com"
I also attempted to reflash the Froyo update from Sprint, that had no results.
So you flashed a different ROM to the one you already were using without wiping?
If so then it's no wonder your device is now stuck in a boot loop. I would say go into recovery do a full wipe and reflash.
For future reference get Root Explorer and when you use that to modify build.prop it will automatically create a backup. No need to paste it onto SD etc...
Just remember to mount System R/W within the program.
Good Luck!
I was originally rooted by using invisiblek's original "stock" root, which contained some Sprint stuff, so I opted to do a clean start from a stock Verizon rom, but to save time I rooted using the adb script method from GS3DebugFSRoot http://forum.xda-developers.com/showthread.php?t=1792342 instead of Root66, which requires a 1.5 GB image download then must be flashed through Odin.
I did this to avoid some of the strange app behaviors from the rooted "Sprint" rom, but after rooting through adb with an automated script, some root apps don't function properly, even though they're getting root permission.
After doing some research and restoring my sprint NAND backup several times to compare, the main things I noticed are:
1. After rooting through adb, the Superuser.apk app is installed in /data/app (which is a user app location) as opposed to /system/app in the case of the flashable root method.
2. Superuser.apk is called com.noshufou.android.su-1.apk instead
3. Superuser.apk from a flashed rom has these permissions (seen using root-expl)
rwsr-sr-x, but the adb method file xxxxxx.su-1.apk has these permissions rwxrwxr-x
4. The owner of the file is "root" when flashed through Odin, but "system" when rooted with adb.
Otherwise, the su binary itself is ok, it is a newer version and larger in size compared to the flashed versions, but it has the right permissions and is located correctly in /system/xbin.
I tried deleting the xxxxx.su-1.apk in /data/app and copying Superuser.apk to /system/app, to make it a system app, reset permissions and "owner" and "group" to root, but lost root after rebooting, so had to start back from my NAND backup again.
Does anyone know how to make Superuser a system app in the /system/app folder without losing root?
Also, I'm not sure this is the cause, but Titanium Backup has a hard time detecting root every time I start it, and has to be restarted multiple times, which wasn't a problem when flashed root w/ Odin, and most importantly, DroidWall is not blocking ANYTHING, whether it's in whitelist or blacklist mode, which it did when I used Odin to flash a rooted rom. I've tried everything, bu to no availe, can a dev that might have an idea what is going on here, help me with this and point me in the right direction to look for what to fix to get DroidWall to work, and if that is causing these issues, to get Superuser installed in the right folder?
Thank you
Nvm, I can't seem to find it again, I know I saw it somewhere though. If this was the OG Droid or Droid 2 I could tell you how to adb push no problem, but it's my first Samsung device. I don't know if anything is different, and I don't wanna be responsible for a brick :S
So here's the case- I used the zero camera mod, and don't have a recovery backup before that point, although I have made a backup copy of the two files, which the mod replaces. Now I want to restore the original camera app, but I can't.
Here is what I have tried:
Manual replacement with root explorer, after setting the right permissions, and the app just disappeared from drawer. After that, tried wiping cache and dalvik-didn't help.
So next thing-replaced my original files with those from the zerocam zip and flashed them, again with wiping caches and fixing permissions, and again no luck....
Any ideas why the s##t isn't working, like it's supposed to, and how to get back the original camera app? I've done such things thousands of times on other phones, without any problems, and can't figure out what's the problem here....
Sent from my HTC One S using Tapatalk 2
Boot into recovery and replace the files through adb. You cant replace system apps while the system is running, in most cases.
Tried with the file manager of trwp - again, the app just disappeared... Fixing permissions and wiping caches didn't help either...
Sent from my HTC One S using Tapatalk 2
Hey guys,
I've done a little Google-ing but I can't find an answer to this one...
So I rooted my new Nexus yesterday but today I started to create myself some backups of the stock ROM just in-case I ever need or want them.
While I was doing this I went through the following process:
1. Ran Google's Factory Image: https://developers.google.com/android/nexus/images#hammerhead.
2. Installed TWRP through Fastboot.
3. Rebooted my bootloader.
4. Opened TWRP's File Manager.
5. Noticed a weird folder...
So from the steps that I have listed above, I'm pretty sure that It's safe to say that the only data/software that is held on my device's storage at the particular point in time is Google's (excluding TWRP), correct?
So back to this weird folder... I noticed a folder in the following directory "/" and it was called "supersu". Is this folder something to do with the Stock Google OS or is this some kind of left-over folder from the ROM that I had used yesterday (unlikely seeing as I have just ran the factory image)?
Here is a DIR Listing of "/":
boot
cache
data
dev
etc
firmware
licence
persist
proc
recovery
res
root
sbin
sdcard
supersu (the folder which raised my suspicion)
sys
system
tmp
usb-otg
Am I in the wrong mindset? Does Google's Factory Image re-format the whole device including "/" or does it just do certain DIRs? Is that "supersu" folder mine or did Google already have that?
Thanks,
LewisD94
EDIT: I know what it is!
TWRP have a built-in service that allows you to install SuperSU to your device without having to download or flash it manually, I'm pretty sure that this folder would have landed it's self on my device when I installed the TWRP recovery through Fastboot... It's the only thing I can think of, testing it now but flashing the Factory Image without a custom recovery. Will report back with results.
FIXED: It must be something to do with TWRP's SuperSU service as I previously mentioned...
I have just ran Google's Factory Image: (https://developers.google.com/android/nexus/images#hammerhead) and installed ES File Explorer then navigated to "/" and I no longer have the folder in question...
New DIR listing of "/"
I don't have that folder. I have the latest TWRP installed. I really wouldn't worry about it though. Just delete it if you don't use Super SU
Sent from my Nexus 5
SuperSU is superuser which grants root access to apps. It was likely left over from a previous ROM because unless you completely wiped the SD card it remains inert.
When you return to completely stock like in the general sticky everything is going byebye.
There are stock ROMs hanging around development that are deodexed or odexed whatever you want. Some of them even have goodies inside.
When you root and unlock bootloader, the super user is installed during the process. Nothing to worry about. SU acts as your phones front door security screening any elevated/administrative task. This is what sprint personnel look for when excepting returns on devices. They know if your rooted and you try to say there is a issue with your device, if they see SU installed they'll know it was probably you who caused it. Besides the main fact but you have nothing to worry about. If you go completely stock and re lock your bootloader, just delete the folder off your SD card.
Sent from my Nexus 5 using XDA Premium 4 mobile app
Must be a TWRP thing. I use CWM and I dont have a supersu folder.
Hello,
I have a rooted Samsung Galaxy Note 3. I was experimenting with the build.prop file, having made a backup of the original version of it. After making some changes to the build.prop file and rebooting the device, the vast majority of the apps stopped working and what is worse, I somehow lost my root access. My original plan was to revert to the original version of the build.prop file if things didn't work as expected but now all I have is read-only access to the /system folder and I can't edit the build.prop file or replace it with the backup of the original I made. I also tried accessing the filesystem via an adb shell, but I still only get read-only access to the system areas. The problem is now 95% of my apps crash before they even start and I can't even run SuperSU, or playstore. I have Total Commander installed, and it is one of the very few apps that work, but again, I only get read-only access to the system area. All I need to do is delete the problem build.prop file and rename the backup file oldbuild.prop file, but how do I re-gain read/write access to the /system folder??
I would truly appreciate any help, ideas or advice
Thanks a lot
PS. I do not have a custom recovery installed. Just the Samsung stock recovery
memrah said:
Hello,
I have a rooted Samsung Galaxy Note 3. I was experimenting with the build.prop file, having made a backup of the original version of it. After making some changes to the build.prop file and rebooting the device, the vast majority of the apps stopped working and what is worse, I somehow lost my root access. My original plan was to revert to the original version of the build.prop file if things didn't work as expected but now all I have is read-only access to the /system folder and I can't edit the build.prop file or replace it with the backup of the original I made. I also tried accessing the filesystem via an adb shell, but I still only get read-only access to the system areas. The problem is now 95% of my apps crash before they even start and I can't even run SuperSU, or playstore. I have Total Commander installed, and it is one of the very few apps that work, but again, I only get read-only access to the system area. All I need to do is delete the problem build.prop file and rename the backup file oldbuild.prop file, but how do I re-gain read/write access to the /system folder??
I would truly appreciate any help, ideas or advice
Thanks a lot
PS. I do not have a custom recovery installed. Just the Samsung stock recovery
Click to expand...
Click to collapse
The solution would be flashing twrp, then using its build in terminal or adb shell to replace the infected build.prop
-Hope- said:
The solution would be flashing twrp, then using its build in terminal or adb shell to replace the infected build.prop
Click to expand...
Click to collapse
Thanks for your answer. I did manage to revert to the correct build.prop file and get rid the bad one. For some reason though, when I restarted my phone it is now getting stuck at the Samsung logo screen with a pulsing blue status LED. I know for a fact that the build.prop file is the correct/original one. So I'm clueless about what might be causing it to get stuck during boot. Any ideas or suggestions? Thanks in advance.
memrah said:
Thanks for your answer. I did manage to revert to the correct build.prop file and get rid the bad one. For some reason though, when I restarted my phone it is now getting stuck at the Samsung logo screen with a pulsing blue status LED. I know for a fact that the build.prop file is the correct/original one. So I'm clueless about what might be causing it to get stuck during boot. Any ideas or suggestions? Thanks in advance.
Click to expand...
Click to collapse
Clear cache
-Hope- said:
Clear cache
Click to expand...
Click to collapse
-Hope-, Thanks a lot for your help. I tried clearing the cache, didn't work. Tried a factory reset via Recovery mode, didn't work, so I think I will need to flash the ROM. Do you know where I can download a stock factory ROM for the Note3 that is unmodified and not tampered with (malware free), just the way Samsung released it?
Once again, thanks a lot for your help
memrah said:
-Hope-, Thanks a lot for your help. I tried clearing the cache, didn't work. Tried a factory reset via Recovery mode, didn't work, so I think I will need to flash the ROM. Do you know where I can download a stock factory ROM for the Note3 that is unmodified and not tampered with (malware free), just the way Samsung released it?
Once again, thanks a lot for your help
Click to expand...
Click to collapse
Updato.com
Sammobile.com < official site
Thanks. I flashed my Note3 with stock Lollipop ROM downloaded from Sammobile.