I installed vodoo lagfix (froyo 2.2) preview6 (or what is newest as today) Before that I had replaced sh with bash, sh was link in same directory binary bash. After vodoo lagfix i encountered reboots... Then i saw that shell is inacessible and now i need to copy bash back to /system/bin (bash is zero bytes) to acess shell and fix things Looks quite simple but i simply cant do it root explorer isint working android mate either any other suggestions? Maybe i can somehow can give root permisions to some simple file explorer? Now my phone restarts as soon as i unplug it and it goes into sleep mode...
Even before that I couldnt simply copy (why there is no cp command?) i had to cat file > file
BTW voodoo really works phone is fast
I hope i posted in right thread thanks for answers.
Had a similar problem: I have JG1, and clockwork replaces my shell and it then becomes unusable.
If you still have your old shell bianry lying around somewhere, or want to "install" your bash again, you can do it by creating an update.zip file.
I've attached a template for this - copy your desired shell binary to system/bin/sh, name it update.zip, place on SD card, go into recovery mode and hit "apply: update.zip"
IMPORTANT: the attached template is untested - you can, however, use the file I actually use, and simply adjust it for your needs (replace its shell binary, and look at the update script... nevermind the "root" text in it... I simply used the rooting update.zip as a base for it...)
Here's what I need when I play around with clockwork: http://db.tt/xGDcT1y
As for the template, see the post's attachments.
I hope this helps.
Cant apply update zip, because there is no such option only reinstall apps and so on... Have 2e recovery. Looks like i will need to use heidmall or similar app.
Hi all,
Ive spent to weekend reading about rooting and ROMS/Kernels and decided to try it. I used a root kit found here from Mskip (great kit). Ive sucessfully rooted, and then sucessfully installed Smooth Rom 4.3 with the Motley kernel.
Ive downloaded Titanium Backup and Rom Manager. TB worked and I did a backup (which I now cant find) (i have ES File Explorer). I upgraded to Titanium Pro, and now when I open the app is states root was denied. I remember when I first opened TB SuperSu asked me to grant it access. After a reboot I opened SuperSu and stated a Binary update was necessary and performed it.
Now TB pro states root was denied, when I open SuperSu there is nothing there in the apps list, and I dont know how to manually grant TB root access.
Sorry if this is noobish, not sure what to do and I dont want to keep going without a backup.
Edit: When I try to backup in ROM Manager I hit backup, it brings up the notification to name the backup, I hit ok and nothing happens.
cam75 said:
After a reboot I opened SuperSu and stated a Binary update was necessary and performed it.
Now TB pro states root was denied, when I open SuperSu there is nothing there in the apps list, and I dont know how to manually grant TB root access.
Click to expand...
Click to collapse
That sort of sounds like the SuperSU "su" update might have failed. Can you get root with other apps? (e.g. go in to a terminal emulator and type "su")
Note there is a chicken-and-egg problem if (either) SuperSU/su or Superuser/su fail: they need root themselves to remount /system so that the "su" binary can be updated.
If no apps can get root, then you sort of have "lost root", and the fix is to manually insert the .apk and su binary into /system/app and /system/bin/su (or /system/xbin/su depending on flavor!) either with a flash package in recovery, or manually via the adb shell command line (with custom recovery running).
HTH
PS you should be able to just manually start the recovery and do a backup in the meantime, no? The fact that ROM manager isn't doing anything could either be a lack-of-root problem or something else (a busybox dependency?)
bftb0 said:
That sort of sounds like the SuperSU "su" update might have failed. Can you get root with other apps? (e.g. go in to a terminal emulator and type "su")
Note there is a chicken-and-egg problem if (either) SuperSU/su or Superuser/su fail: they need root themselves to remount /system so that the "su" binary can be updated.
If no apps can get root, then you sort of have "lost root", and the fix is to manually insert the .apk and su binary into /system/app and /system/bin/su (or /system/xbin/su depending on flavor!) either with a flash package in recovery, or manually via the adb shell command line (with custom recovery running).
HTH
PS you should be able to just manually start the recovery and do a backup in the meantime, no? The fact that ROM manager isn't doing anything could either be a lack-of-root problem or something else (a busybox dependency?)
Click to expand...
Click to collapse
thx for the quick response, however much of that is WAY over my head. I opened terminal emulator and typed su and this is what popped up. 1 [email protected]:/ $
When TB is opened it states error "sorry I could not acquire root privilegdes. this applidation will not work. please verify that your rom is rooted and try again. this attempt was made using the "/system/xbin/su" command.
I dont see busybox in my app drawer
cam75 said:
thx for the quick response, however much of that is WAY over my head. I opened terminal emulator and typed su and this is what popped up. 1 [email protected]droid:/ $
Click to expand...
Click to collapse
If the SuperSU app (and companion binary) were working correctly, you should have seen one of those "Accept / Deny" pop-up messages coming from the SuperSU app... assuming that you didn't previously grant root access to that terminal emulator app. You didn't mention that happening.... ?
Also, usually the command prompt usually changes from $ to # when you have root, but not always; the explicit way to check would be to (after you have tried the "su" command) to type in "id" and hit return at the prompt - that will tell you explicitly if you are root or not. (That's the letter "i" followed by the letter "d" followed by the return key).
From the way you describe this, it is sounding like you lost root.
I gotta go watch part of the game. In the meantime, perhaps you should at least create a backup manually.
As I said, the simplest fix-up would be to get Superuser.apk/su or SuperSU/su re-installed into /system/app and /system/{x}bin/su (it seems that chainsDD and chainfire use different locations).
There might be floating around someplace a flashable zip file with this stuff in it - to be used for "lightly rooting" a stock ROM after a custom recovery is in place. But things have been in flux recently with both the SuperSU (chainfire) and Superuser (chainsDD) kits because of the JellyBean multi-user support, so the version you might need is important. So you would have to do the research to figure out where.
gotta go - good luck.
bftb0 said:
If the SuperSU app (and companion binary) were working correctly, you should have seen one of those "Accept / Deny" pop-up messages coming from the SuperSU app... assuming that you didn't previously grant root access to that terminal emulator app. You didn't mention that happening.... ?
Also, usually the command prompt usually changes from $ to # when you have root, but not always; the explicit way to check would be to (after you have tried the "su" command) to type in "id" and hit return at the prompt - that will tell you explicitly if you are root or not. (That's the letter "i" followed by the letter "d" followed by the return key).
From the way you describe this, it is sounding like you lost root.
I gotta go watch part of the game. In the meantime, perhaps you should at least create a backup manually.
As I said, the simplest fix-up would be to get Superuser.apk/su or SuperSU/su re-installed into /system/app and /system/{x}bin/su (it seems that chainsDD and chainfire use different locations).
There might be floating around someplace a flashable zip file with this stuff in it - to be used for "lightly rooting" a stock ROM after a custom recovery is in place. But things have been in flux recently with both the SuperSU (chainfire) and Superuser (chainsDD) kits because of the JellyBean multi-user support, so the version you might need is important. So you would have to do the research to figure out where.
gotta go - good luck.
Click to expand...
Click to collapse
Thanks again.
Im watching Superbowl as well. I didnt grant Terminal access. I rebooted into recovery and restored to right after I rooted. SuperSu auto updated through the play store, and stated the binary need updated. I canceled that. TB and ROM manager are showing up in SuperSu. So now Im rebooting into recovery again to after I installed the Smooth Rom/Motley Kernal. I did make a backup of where SuperSu lost root. I now have three backups.
Question on installing the SuperSu apk file. I want to be sure I do it right, if needed. Download the file on my 7. it will go to my download folder. Move it to the system folder and open/run it? what do i do with the current SuperSu folder?
thanks again
I went to my restore point after root and reinstalled 4.3 Smooth ROM Mkernel. I did not take the SuperSu update, (ill wait for the next update) and everything is fine TB an ROM manager working fine, did a backup in both.
Thanks for your help on this.
cam75 said:
Question on installing the SuperSu apk file. I want to be sure I do it right, if needed. Download the file on my 7. it will go to my download folder. Move it to the system folder and open/run it? what do i do with the current SuperSu folder?
Click to expand...
Click to collapse
Dealing with .apk's is not that difficult - drop them into the correct place and reboot.
In Android, apps (.apk files) are stored in one of two places: /system/app or /data/app. It is even possible for two versions of an app to be on the phone - one in /system/app and one in /data/app; that is how upgrades of factory-installed apps happen: the pre-installed app is in /system/app... and never gets deleted (read-only filesystem), whereas update versions get dropped into /data/app. Generally you can just drop an .apk file into either of these locations, wipe the dalvik cache and reboot. During the android boot, these files are compiled into .dex objects in the dalvik-cache, and various version, consistency, rights and permissions are cross-checked.
Think of it this way: when you boot a new ROM for the first time, /data starts out completely empty. Everything needed to support each pre-installed app in /system/app gets created automatically during the android layer start-up.
The "su" native binary is a bit more complicated - it needs to be:
- owned by the user.group root.root
- be executable
- be setuid/setgid
Imagine that you had a copy of these two files on your "/sdcard". If you booted into the custom recovery, you could affect these changes like this:
C:\foo> adb shell
# mount # show what is already mounted
# mount /sdcard # if needed
# mount /system # if needed
# mv /system/app/SuperSU.apk /system/app/SuperSU.apk.old
# cp /sdcard/SuperSU.apk /system/app/SuperSU.apk
# mv /system/xbin/su /system/xbin/su.old
# cp /sdcard/su /system/xbin/su
# chown root.root /system/xbin/su
# chmod 6755 /system/xbin/su
# cd /
# umount /system
# exit
C:\foo>
*
As a practical matter, it is probably easier to just make sure to make a fresh backup if you are about to update the su binary - in case anything goes wrong. It might also be useful to use a root-aware file manager to remount the /system partition in rw mode prior to doing the "update su binary" procedure in the SuperSU app.
Good luck
* note that SuperSU and Superuser apps choose different locations for the su executable file - one uses /system/bin/su and the other /system/xbin/su. There might also be a symlink between these locations. Best policy is probably to examine a known-working installation to determine how to proceed.
People experience battery drain issues after restoring their EFS and have no clue why. I did too for several months until I found out the solution. I think many people are not correctly setting permissions after restoring. You may be able to make calls but you will still experience crazy multipdp and wlan wakelocks. Fortunately, there is a very simple solution that will solve this problem.
Connect via ABD or install Terminal Emulator from the PlayStore.
Type in the following commands:
su
chmod -R 777 /efs <--- (Keep in mind, the R has to be uppercase.)
exit
That's it. If you check the efs folder, you'll see that everything in the efs folder is accessible. Although, it isn't the most elegant solution, your phone will at least have access to everything it needs for it to operate correctly. You'll see a dramatic increase in battery life if you hadn't restored permissions previously.
Cheers.
[GUIDE][7.1.1] Making The System Half-Writable & Convert The Apps To Be System-Apps
Okay. This is my first guide. My English isnt that so good. I tried something for my phone. I thought maybe it will helps you too.
HERE IS MY EASY GUIDE FOR UNINSTALL SYSTEM-APPS ON NOUGAT 7.1.1 VERSION 34.3.A.0.244 (AND ALSO MAKE THE SYSTEM HALF-WRITABLE?)(I DONT KNOW MUCH THESE SUBJECTS SORRY)
-Requires
- Version 34.3.A.0.244
- Magisked
- TWRPed
Note: Here is my TWRP and Magisking Guide Here Here Here
Installation
1. First Install
a. Android Terminal
b. Busybox By Meefik
2. Open Busybox and Install.
3. Open The Terminal Emulator. Its just like this
Code:
F5121:/ $
and type "su" just like this (NOT "Su", just "su" with little S)
Code:
F5121:/ $ su
press okay (on your keyboard)
Now this dollar symbol changed the like this #
Code:
F5121:/ #
That was First Step of terminal. Now the second step, type this command carefully
Code:
busybox mount -o rw,remount,rw /system
rw,remount,rw
-These are not dots, These are virgules.(commas)
Type and enter. If it doesnt give any error message just like this "mount: '/dev/block/bootdevice/by-name/system'->'/system': Device or resource busy" or something, congrats you did.
-Now you can delete your system-apps using Link2SD.
-But you cant still convert the u-apps to system-apps using Link2SD!
If you want convert user-apps to system-apps, use Root Explorer.
- User-apps located at root/data/app
- So cut the folder (wanted to convert system-app) from data/app
- Paste to root/system/app
- Restart The Phone
- I know this is manual guide for converting apps but it simple and easy.
(When some apps converted, maybe doesnt work. You have been warned.)
+thanks for the SoNyek for post
+commands from YasuHamed. Thanks. His guide is here
Hey S7 Users!
I don't know how many of you have experienced the problems that I have encountered while trying to run AOSP (Specifically Resurrection Remix 6.2.0) on the S7 such as passing integrity check or getting the gear app to work but they have been an issue for me. I'll be putting here what I did to get these things to work that I figured out over time and hopefully will save some people time. And sorry if the format is weird it's my first time making a guide and posting.
The problems that I'm going to address specifically are:
- Passing CTS Integrity
- Getting the Gear App to Work
First off, the CTS integrity. When you first install the ROM, you might find that you cannot download certain apps or that apps don't work correctly. Thats because the CTS integrity is tripped. This is because the Phone does not have a proper build fingerprint since it is a Custom ROM.
To fix this you're going to need Magisk (Link) and Magisk Manager and also Terminal Emulator (Link). Follow the instructions and once installed go into Magisk Manager and you can check that your CTS Integrity is False.
Next go to the download modules section
Screenshot
Then search for Magisk Hide Props Config, install it and then reboot.
Once rebooted open terminal emulator, grant it SU access and type "props"
A menu should appear: Screenshot
Now type 1 and press enter and this should pop up: Screenshot
Next type f then this will pop up: Screenshot
From there select the number that corresponds to Samsung or whatever phone you want although I haven't checked this to see if it works but I don't see why not. Then look and find the one labeled "Samsung Galaxy S7 (8.0.0)" should be 16.
Once you have selected 16(or what ever one you picked) type y and press enter to change the fingerprint: Screenshot
After it is finished it will ask you to reboot. Once rebooted go into Magisk Manager and check that CTS Integrity is now true. Also, go and clear the data and cache of the Play Store and the Play Services. Now you can download apps and use Google Pay
Now for the real challenge the Gear app. This one stumped me for a long time and made me want to just go back to stock. But I kept going and eventually figured it out.
Setting the fingerprint was only the first step because before you could not install it. Now when you open it it'll tell you that you've made unauthorized changes etc. because it thinks that the S7 is on stock firmware but when it checks it sees that it isn't. So what we are going to need to do is change the build.prop to make it look like a different phone. I'll link mine down below if you want it but it is a herolte (S7 Exenos) so keep that in mind as it might brick your system. This will involve some Linux skills.
For this one it is easier if you do it from a computer and then do adb shell. Enable Debugging in the Developer settings and then adb into the device with:
Code:
adb shell
Then
HTML:
su
(Allow it the Super User Access)
Next you have to set the /system to R/W so do that with the command:
Code:
mount -o rw,remount /system
After you have done that type:
Code:
cd /system
And then set permissions on the build.prop:
Code:
chmod 644 build.prop
At this point what you want to do is exit out of the shell (so type exit twice). Now type:
Code:
adb pull /system/build.prop
This will pull the build prop but it goes to different places. I suggest you look up where it stores it as it will vary where it drops it depending on operating systems. For me in Windows it is the following:
Code:
C:\Users\<account_name>\AppData\Local\VirtualStore\Program Files (x86)\MyCustomADBInstallLocation\
Now that you have it simply open it in a text editor and edit the following lines:
Code:
ro.product.brand=htc (change from samsung to htc)
ro.product.manufacturer=htc (also change from samsung to htc)
After that save the file and then go back to the terminal and type(Assuming you haven't moved the file):
Code:
adb push build.prop /sdcard
This will move it to the internal storage since at least for me i could not push it directly to /system
Now do another adb shell and su then type these commands to delete the old one, copy the new one in and then change the system back to read only(This is very important to avoid bootloops!):
Code:
rm /system/build.prop
cp /sdcard/build.prop /system
mount -o ro,remount /system
And then exit out of the adb then reboot the phone. If all goes well then it should reboot and the gear app should work now. Woohoo! That was pretty involved and I'm sure there is a more efficient way to do that (feel free to comment and suggest one) but I can guarantee that it works. Also feel free to ask questions and I can try to answer them. Anyways guys if this helped please hit the thanks button. This took many hours for me to figure out and I hope it all works out for you. Cheers!