Related
So, I've gotten my SGS2 today and went ahead to root it. Flashed CF-Root matching my current version (KE7 PDA/KE4 baseband). I used the S2Root app posted here on the forum to get root and flashed a stock kernel back.
In either of these stages, I couldn't get ADB to run as root, needed for a modification i'm trying to do (can't write to /system/framework otherwise).
Is there a known way to get ADB to run as root?
(The issue at hand - /default.prop contains ro.secure=1 and ro.debuggable=0 - And i can't edit this file in order for it to persist after reboot)
even in CWM i can't get ADB to run as root and thus cannot copy files to /system/framework even though /system is mounted as r/w.
Thanks for the help.
ransagy said:
So, I've gotten my SGS2 today and went ahead to root it. Flashed CF-Root matching my current version (KE7 PDA/KE4 baseband). I used the S2Root app posted here on the forum to get root and flashed a stock kernel back.
In either of these stages, I couldn't get ADB to run as root, needed for a modification i'm trying to do (can't write to /system/framework otherwise).
Is there a known way to get ADB to run as root?
(The issue at hand - /default.prop contains ro.secure=1 and ro.debuggable=0 - And i can't edit this file in order for it to persist after reboot)
even in CWM i can't get ADB to run as root and thus cannot copy files to /system/framework even though /system is mounted as r/w.
Thanks for the help.
Click to expand...
Click to collapse
Try this:
adb shell mkdir /sdcard/temp/
adb push fileToPush /sdcard/temp/
adb shell
$ su
# cp /sdcard/temp/ /system/path/to/push/to/
ADB doesn't run as root, as it's not safe to, as you can bypass superuser security in a rogue app otherwise
I'll try it ASAP, Thanks.
Isn't there a way to edit /default.prop though?
I'd prefer to have adb run in root at the very least while running this mod, and then restore it.
the mod currently patches framework.jar/libwebcore.so for RTL issues, and relays on scripted access to adb and r/w access to /system.
I ended up discovering that i need a different ROM either way since stock is odexed.
I'll try making my own ROM based on stock with deodexed files and make the fix before hand.
i'm on clockworkmod 5.0.2.3, my device is galaxy tab 10.1 P7510. i backup it with Titanium Backup. i've done CWM backup, i do know the CWM's backup file is sdcard/clockworkmod, but i can't delete it, either on my tablet or computer!! i've tried ES file and RE, nothing changes,,,,and the CWM file is as large as 1G, but i can't see anything in it! is that a new function of 5.0.2.3, to hide and protect its file? i've format the whole SDcard on my computer, and everything's gone, BUT the CLOCKWORKMOD file!!!!!! i'm crazy!!!!!
wohenyingyu01 said:
i'm on clockworkmod 5.0.2.3, my device is galaxy tab 10.1 P7510. i backup it with Titanium Backup. i've done CWM backup, i do know the CWM's backup file is sdcard/clockworkmod, but i can't delete it, either on my tablet or computer!! i've tried ES file and RE, nothing changes,,,,and the CWM file is as large as 1G, but i can't see anything in it! is that a new function of 5.0.2.3, to hide and protect its file? i've format the whole SDcard on my computer, and everything's gone, BUT the CLOCKWORKMOD file!!!!!! i'm crazy!!!!!
Click to expand...
Click to collapse
try makeing a new backup file in recovery as this should overright the last one
the file is probably corrupt
or using root explorer find the file and check the that folder is R/W
i dnt know if you can doo this on the sd card
You should be able to delete any file on the "SD card". Personally, although I use titanium backup as a great tool, CWM's backup is so easy and reliable for me.
thank u but it doesn't work. new backup changes nothing but make it biger, it seems that i can delete it by RE, but if i refresh i appears again. is there any way to format?
BroBot175 said:
try makeing a new backup file in recovery as this should overright the last one
the file is probably corrupt
or using root explorer find the file and check the that folder is R/W
i dnt know if you can doo this on the sd card
Click to expand...
Click to collapse
Tubes6al4v said:
You should be able to delete any file on the "SD card". Personally, although I use titanium backup as a great tool, CWM's backup is so easy and reliable for me.
Click to expand...
Click to collapse
yep, but it confuses me if the backup exists forever.......
wohenyingyu01 said:
yep, but it confuses me if the backup exists forever.......
Click to expand...
Click to collapse
aha me to :L did you try the root explorer way?
BroBot175 said:
aha me to :L did you try the root explorer way?
Click to expand...
Click to collapse
yep, it doesn't work.....finally i flash the rom with formating scripts through odin, it seems xwkg4, and flash back. now everything's gone~
You can rename and delete backups with the rom manager app from the market.
http://market.android.com/details?id=com.koushikdutta.rommanager
while in recovery:
adb shell mount /data
adb shell rm -r /data/media/clockworkmod/backup/DATED_FOLDER
Are you talking about the nandroid backup? If so, open the CWM recovery and the option to delete backups is there...
Also, you do realize that the CWM backup is not the same thing as the titanium backup, right? CWM backup is the whole system; titanium is just apps and settings...
got the same problem and tried a lot
slack04 said:
Are you talking about the nandroid backup? If so, open the CWM recovery and the option to delete backups is there...
Also, you do realize that the CWM backup is not the same thing as the titanium backup, right? CWM backup is the whole system; titanium is just apps and settings...
Click to expand...
Click to collapse
hi, i got the same issue and have tried to figure it out for hours and turn to here for help finally. my clockworkmod recovery's version is 5.5.0.4, probably. and i flashed 5.8.3.1 minutes ago.
i've tried to delete the backups in rom manager, but still can't and was told error occured while deleting.
and i tried to remove them in adb shell, rm command, and it says permission denied.
Code:
[email protected]:/sdcard/clockworkmod/backup # rm -r 2005-06-01.07.50.08
rm -r 2005-06-01.07.50.08
rm failed for 2005-06-01.07.50.08, Permission denied
255|[email protected]:/sdcard/clockworkmod/backup #
really need reply if anyone else is confused with the same problem ...
chenxian352 said:
hi, i got the same issue and have tried to figure it out for hours and turn to here for help finally. my clockworkmod recovery's version is 5.5.0.4, probably. and i flashed 5.8.3.1 minutes ago.
Click to expand...
Click to collapse
Is 5.8.3.1 for this tablet? If not...
chenxian352 said:
and i tried to remove them in adb shell, rm command, and it says permission denied.
Code:
[email protected]:/sdcard/clockworkmod/backup # rm -r 2005-06-01.07.50.08
rm -r 2005-06-01.07.50.08
rm failed for 2005-06-01.07.50.08, Permission denied
255|[email protected]:/sdcard/clockworkmod/backup #
Click to expand...
Click to collapse
In recovery (CWM) or android? Try with the -f switch (rm -rf), and do it in recovery from your PC (don't forget to mount the partition).
BTW, I can delete cwm backups in android with Root Explorer without problem.
slack04 said:
Is 5.8.3.1 for this tablet? If not...
Click to expand...
Click to collapse
If his tablet is the GT-P7510 model, yes.
slack04 said:
Is 5.8.3.1 for this tablet? If not...
Click to expand...
Click to collapse
sure about that, i got the recovery from clockworkmod.com.
i formatted it in windows, and everything was deleted but the clockworkmod folder! ghostly exist
something i just thought.. i'm using windows 7, when the tablet connect to my laptop, windows recognize it as a portable device. it's special i guess. is there any way to let it be removable disk?
---------- Post added at 04:43 AM ---------- Previous post was at 04:17 AM ----------
MapleSyrup said:
In recovery (CWM) or android? Try with the -f switch (rm -rf), and do it in recovery from your PC (don't forget to mount the partition).
BTW, I can delete cwm backups in android with Root Explorer without problem.
If his tablet is the GT-P7510 model, yes.
Click to expand...
Click to collapse
thx for reply. yes my tablet is GT-P7510. i can't delete them in re explorer, delete failed.
could you please tell me how to mount the partition?
chenxian352 said:
could you please tell me how to mount the partition?
Click to expand...
Click to collapse
One way is, in cwm, select "mount and storage" > "mount /data"
The other way is with adb (you're going to use it any way)
Code:
adb root
Code:
adb shell
Code:
mount /dev/block/mmcblk0p8 /data
If you keep getting the same error, try deleting everything inside the backup directory, I mean the 2005-06-01.07.50.08 directory.
Code:
cd /sdcard/clockworkmod/backup/2005-06-01.07.50.08
Inside the directory (be 100% sure to be in 2005-06-01.07.50.08 or you're going to delete something important. Always be careful when using the rm -rf * command)
Code:
rm -rf *
Or in one line
Code:
rm -rf /sdcard/clockworkmod/backup/2005-06-01.07.50.08/*
Then, delete the directory:
Code:
rmdir /sdcard/clockworkmod/backup/2005-06-01.07.50.08/
problem solved! thanks MapleSyrup
really thanks MapleSyrup! i executed all commands after normally powerup.
i just did them in cmw mode, all worked!
when normally powerup, in adb shell, command line prompt start with
Code:
[email protected]:/ #
in cmw(recovery) mode, it changes to
Code:
~ #
and no 'Permission denied' anymore when execute rm
i'm not English actually, literal words may be incorrect, hope readers could get it.
thanks sincerely. i've spent almost half day on the issue, you cant imagine how happy i am now, ha
MapleSyrup said:
One way is, in cwm, select "mount and storage" > "mount /data"
The other way is with adb (you're going to use it any way)
Code:
adb root
Code:
adb shell
Code:
mount /dev/block/mmcblk0p8 /data
If you keep getting the same error, try deleting everything inside the backup directory, I mean the 2005-06-01.07.50.08 directory.
Code:
cd /sdcard/clockworkmod/backup/2005-06-01.07.50.08
Inside the directory (be 100% sure to be in 2005-06-01.07.50.08 or you're going to delete something important. Always be careful when using the rm -rf * command)
Code:
rm -rf *
Or in one line
Code:
rm -rf /sdcard/clockworkmod/backup/2005-06-01.07.50.08/*
Then, delete the directory:
Code:
rmdir /sdcard/clockworkmod/backup/2005-06-01.07.50.08/
Click to expand...
Click to collapse
I'm a little more of a newb here, and Don't understand the above stuff. I'm having the exact same issue.
ROM Manager basically just messed up my phone to the point that I can't delete backups in clockworkmod. Also the backups are showing 0 bytes in size even though they've taken up 3 gigs on my SDCard
I Got ROM manager to install the latest CWM, which is great. I Then was trying it out, and noticed you can do a backup right from it. It Loads CWM and performs a normal Nandroid backup.
Here is the issue, It shows that it has take up the space on my SDCard, but the folder contents are empty in clockworkmod/backups
Also, I can't delete them at all. I Tried ES Explorer and nothing worked. Said denied.
Hello everybody,
i have gained root access to my phone via backup/restore method through adb where local.prop is stored in /data/. So when i log onto my phone with adb i have root access. I copied busybox, su and the superuser.apk to the right place and removed the local.prop file again. After a reboot I was hoping to remove some crapware off my phone but to my surprise the binaries i copied vanished from the filesystem. So the phone reverted the changes by itself. I did this process several times copying busybox and su to various places referred to by $PATH, but it´s everytime the same after i reboot. The files are gone.
After the first attempts failed i tried to make changes to my phone while logged in as root. I wanted to uninstall unnecessary packages with "pm uninstall" but that failed also. The command just responds "failed". Even when /system is mounted rw (it remounts itself to ro after a while though). I´ve also made changes to /init.rc but they are also gone after a reboot as other changes i´ve made. Basically i wasn´t able to accomplish anything with root access no matter what i did.
So what i want to know is how this black magic works andy why i cant do anything with root. I know how to achieve real root through htc dev and various other methods.
Thanks for reading!
nasenstueber said:
Hello everybody,
i have gained root access to my phone via backup/restore method through adb where local.prop is stored in /data/. So when i log onto my phone with adb i have root access. I copied busybox, su and the superuser.apk to the right place and removed the local.prop file again. After a reboot I was hoping to remove some crapware off my phone but to my surprise the binaries i copied vanished from the filesystem. So the phone reverted the changes by itself. I did this process several times copying busybox and su to various places referred to by $PATH, but it´s everytime the same after i reboot. The files are gone.
After the first attempts failed i tried to make changes to my phone while logged in as root. I wanted to uninstall unnecessary packages with "pm uninstall" but that failed also. The command just responds "failed". Even when /system is mounted rw (it remounts itself to ro after a while though). I´ve also made changes to /init.rc but they are also gone after a reboot as other changes i´ve made. Basically i wasn´t able to accomplish anything with root access no matter what i did.
So what i want to know is how this black magic works andy why i cant do anything with root. I know how to achieve real root through htc dev and various other methods.
Thanks for reading!
Click to expand...
Click to collapse
is your RECOVERY.img
and beside i dont really think your /system is fully mounted rw
mauricio.valladolid said:
is your RECOVERY.img
and beside i dont really think your /system is fully mounted rw
Click to expand...
Click to collapse
Thanks for the reply. i use mount -o remount,rw /system as mount command to get read/write permission on /system. If there is something more to do please let me know. And if the behavior i ve seen is caused by the recovery.img is there something i can do about it?
nasenstueber said:
Thanks for the reply. i use mount -o remount,rw /system as mount command to get read/write permission on /system. If there is something more to do please let me know. And if the behavior i ve seen is caused by the recovery.img is there something i can do about it?
Click to expand...
Click to collapse
why dont you just install ext4 recovery and flash supersu.zip?
I really dont get it why are you trying to do it the hard way
Enable all toggles + unlock native Tethering
If you have Safestrap installed and are on a MK2 or MJ7 rom/build you can flash the corresponding zip below and you will unlock native built-in tethering and also get all the toggles including the usually absent Wifi Hotspot toggle. Both versions have been tested and confirmed to be work. This also enables all the missing toggles, not only the Wifi Hotspot toggle. Toggle issue = solved. If you don't have Safestrap then let me know, I'll write up a script to do the same thing if needed.
@Scottchy014 made an awesome video of the process that you can watch here
Devs/Modders/Themers - You can use my script without my permission and you don't need to give me credit. I don't do this for ego/pride I'm already narcissistic enough as it is.
I545VRUFNC5_Tether_unlock_&_toggle.zip
md5:690b28f995fe7b33d2f1407a25b1abea
MJ7 Tether unlock w/ toggle
md5:b382d98e112adc5e48c7b37b2bb4bd6a
MK2 Tether unlock w/ toggle
md5:12e3eab158521d355ddd3956f340cf70
Verizon Galaxy S4 VRUEMJ7 Tether unlock
Unlocks WifiHotspot, USB Tether, and Bluetooth
Developed by Surge1223
11/02/2013
Please read the instructions; accidents while flashing framework-res.apk can and do happen and those mistakes lead to having to use full Odin restore tars. I almost made open1your1eyes0 brick had he not caught my mistake in the code. Luckily he was nice enough to test again, luckily that one worked
Instructions:
(Try the alternate method below first, it seems to work with less errors, but if you insist on using the script then FOR MK2 replace all instances of "MJ7" below with "MK2")
1. Extract MJ7_tether_unlock.zip and move the MJ7_tether_unlock folder to the root
of your micro sdcard so the structure looks like this: /mnt/extSdCard/MJ7_tether_unlock/
also make sure you have busybox installed and are using SuperSu and not the chinese superuser.
Finally, before continuing, remember to disable the Knox apps (5 I believe?) and security apps (the 4 VZW security apps) install busybox, remove the Chinese superuser, update SuperSu's binaries, enable usb debugging and under security disable verify apps while enabling unknown sources.
2. Download terminal emulator then type the following in terminal:
Code:
su
cd /mnt/extSdCard/MJ7_tether_unlock/
sh tether.sh
3. After that your phone should reboot, and tethering should be unlocked! Also a copy of your original framework-res.apk
can be found in the following directory /mnt/extSdCard/MJ7_tether_unlock/orig-framework-res.apk
4. To restore back to your original framework-res.Code:apk, (i.e, relock tethering) then type the following in terminal:
Code:
su
cd /mnt/extSdCard/MJ7_tether_unlock/
sh untether.sh
Downloads
MJ7
Download the zip here
Alternate link: Mirror
MD5: 029780a103ab8fb4929bb83b2270d6ef
To download just the modded MJ7 framework-res.apk click here
MK2
Download the zip here
MD5: ed0e0f974d7d8720690b8eb96461b5f3
To download just the modded MK2 framework-res.apk click here
ALTERNATE METHOD
DO NOT RENAME the original framework-res.apk file! You will have to use an Odin tar to recover!
1.Download the modded framework-res.apk from here for MJ7 or here for MK2 then copy it to /system first then change framework-res.apk's permissions to rw-r--r-- (chmod 644) and then MOVE it to /system/framework and overwrite framework-res.apk. Then reboot and you should have tethering!
Simply copy and pasting will cause you to boot loop so instead move it to /system first and change the permissions then and only then move it to /system/framework/ and overwrite the original
The Mod itself:
This is from the original arrays.xml
Code:
Code:
usb\\d
rndis\\d
wlan0
bt-pan
[color=red] [/color]
[color=red]com.samsung.spg
com.samsung.spg.NewSPGActivity[/color]
0
1
5
This is the modified arrays.xml
Code:
Code
usb\\d
rndis\\d
wlan0
bt-pan
0
1
5
[COLOR=Lime]7[/COLOR]
Give credit to @open1your1eyes0 for testing the second build after I screwed up the first just his input on the shell script and mod in general. Thanks internet, specifically this page. Also @Sir_Eagle for the MK2 framework-res.apk
Does this work on non rooted devices??
phgoodwrench said:
Does this work on non rooted devices??
Click to expand...
Click to collapse
Unfortunately, no. It has to overwrite a system file.
Sent from my SCH-I535 using xda app-developers app
Surge1223 said:
Unfortunately, no. It has to overwrite a system file.
Sent from my SCH-I535 using xda app-developers app
Click to expand...
Click to collapse
Was a stupid question. Just saw the first command in TE was to type SU. Guess I'll root this junk. Been putting it off forever since I didn't want to flash a ROM and tethering worked.
confirmed
I have gs4 Verizon running MJ7 4.3 and used this to unlock my tethering capability.
Thank you for this information and your work!
I have unlimited data plan and was stuck using WiFi router which burned up battery like crazy. This is so much better now.
Thanks again! :good:
Surge1223 said:
I see people complain about not having the Wifi or WifiHotspot toggles working depending on the rom they are on. The solution doesn't require SQLite Editor. You can solve this problem by appending the below to your /system/csc/feature.xml under <!-- Settings --> header by changing system to r/w while edition then chmod back to 644.
[/SIZE]
Code:
[SIZE=3]<CscFeature_Setting_DefQuickPanelOrder>Wifi;Bluetooth;Location;AirplaneMode;WiFiHotspot;SmartStay;AutoRotate;MobileData;SilentMode;PowerSaving;MultiWindow;AirGesture;AllShareCast;SBeam;Nfc;AirView;Sync;SmartScroll;DrivingMode;DormantMode;BlockMode</CscFeature_Setting_DefQuickPanelOrder>[/SIZE]
[/SIZE]
Click to expand...
Click to collapse
Not sure what you are saying here can you do a more detailed description?
Thanks
Sent from my VZW Galaxy Note 3
This is an amazing development and greatly appreciated, however, I don't understand the purpose of the APK file? Is this an APK that needs to be installed for any reason?
---------- Post added at 09:54 AM ---------- Previous post was at 09:52 AM ----------
Jsyme222 said:
This is an amazing development and greatly appreciated, however, I don't understand the purpose of the APK file? Is this an APK that needs to be installed for any reason?
Click to expand...
Click to collapse
Terribly sorry! I just read the developer note concerning the APK! OOPS! Forgot to read!
---------- Post added at 10:06 AM ---------- Previous post was at 09:54 AM ----------
Surge1223 said:
Verizon Galaxy S4 VRUEMJ7 Tether unlock
Unlocks WifiHotspot, USB Tether, and Bluetooth
Developed by Surge1223
11/02/2013
Please read the instructions; accidents while flashing framework-res.apk can and do happen and those mistakes lead to having to use full Odin restore tars. I almost made open1your1eyes0 brick had he not caught my mistake in the code. Luckily he was nice enough to test again, luckily that one worked
Instructions:
1. Extract MJ7_tether_unlock.zip and move the MJ7_tether_unlock folder to the root
of your micro sdcard so the structure looks like this: /mnt/extSdCard/MJ7_tether_unlock/
2. Download terminal emulator then type the following in terminal:
Code:
su
cd /mnt/extSdCard/MJ7_tether_unlock/
sh tether.sh
3. After that your phone should reboot, and tethering should be unlocked! Also a copy of your original framework-res.apk
can be found in the following directory /mnt/extSdCard/MJ7_tether_unlock/orig-framework-res.apk
4. To restore back to your original framework-res.apk, (i.e, relock tethering) then type the following in terminal:
Code:
su
cd /mnt/extSdCard/MJ7_tether_unlock/
sh untether.sh
Downloads
Download the zip here
Devs, I've included just the framework-res.apk w/ just the mod here so you can customize it more as needed for your roms.
The Mod itself:
This is from the original arrays.xml
Code:
</integer-array>
<string-array name="config_tether_usb_regexs">
<item>usb\\d</item>
<item>rndis\\d</item>
</string-array>
<string-array name="config_tether_wifi_regexs">
<item>wlan0</item>
</string-array>
<array name="config_tether_wimax_regexs" />
<string-array name="config_tether_bluetooth_regexs">
<item>bt-pan</item>
</string-array>
<array name="config_tether_dhcp_range" />
[COLOR=Red] [COLOR=Black]<[/COLOR]string[COLOR=Black]-array[/COLOR][/COLOR] name="config_mobile_hotspot_provision_app"[COLOR=Red]>[/COLOR]
[COLOR=Red]<item>com.samsung.spg</item>[/COLOR]
[COLOR=Red] <item>com.samsung.spg.NewSPGActivity</item>[/COLOR]
[COLOR=Red]</string-array[COLOR=Black]>[/COLOR][/COLOR]
<integer-array name="config_tether_upstream_types">
<item>0</item>
<item>1</item>
<item>5</item>
</integer-array>
This is the modified arrays.xml
Code:
</integer-array>
<string-array name="config_tether_usb_regexs">
<item>usb\\d</item>
<item>rndis\\d</item>
</string-array>
<string-array name="config_tether_wifi_regexs">
<item>wlan0</item>
</string-array>
<array name="config_tether_wimax_regexs" />
<string-array name="config_tether_bluetooth_regexs">
<item>bt-pan</item>
</string-array>
<array name="config_tether_dhcp_range" />
<array name="config_mobile_hotspot_provision_app" />
<integer-array name="config_tether_upstream_types">
<item>0</item>
<item>1</item>
<item>5</item>
[COLOR=Lime] <item>7</item>[/COLOR]
</integer-array>
I see people complain about not having the Wifi or WifiHotspot toggles working depending on the rom they are on. The solution doesn't require SQLite Editor. You can solve this problem by appending the below to your /system/csc/feature.xml under <!-- Settings --> header by changing system to r/w while edition then chmod back to 644. Following your next reboot/hot reboot/restarted systemui, pull down the toggle bar, click the settings button and it should allow you to choose to add any that weren't available previously.
Code:
[SIZE=3]<CscFeature_Setting_DefQuickPanelOrder>Wifi;Bluetooth;Location;AirplaneMode;WiFiHotspot;SmartStay;AutoRotate;MobileData;SilentMode;PowerSaving;MultiWindow;AirGesture;AllShareCast;SBeam;Nfc;AirView;Sync;SmartScroll;DrivingMode;DormantMode;BlockMode</CscFeature_Setting_DefQuickPanelOrder>[/SIZE]
Give credit to @open1your1eyes0 for testing the second build after I screwed up the first just his input on the shell script and mod in general. Thanks internet, specifically this page.
Click to expand...
Click to collapse
I am so happy to have tether again, but I am very curious as to how this goes unnoticed by Verizon? Since this gets processed through the native tethering app how does it stay below the radar of Big Red?
Caution
Southern_mind said:
Not sure what you are saying here can you do a more detailed description?
Thanks
Sent from my VZW Galaxy Note 3
Click to expand...
Click to collapse
So I saw this portion of the thread and thought I would try to achieve this also. I messed with the system folder and totally bricked my phone. No hope of recovery. It was my fault for messing with something that I knew nothing about but just want to caution anyone thinking of doing this to be very careful.
I changed permissions for this folder and locked up the phone and it won't even let me Odin, flash through recovery or sideload through adb.
So my device is toast.
Just be wary of messing with things unfamiliar.
dimitrisg said:
So I saw this portion of the thread and thought I would try to achieve this also. I messed with the system folder and totally bricked my phone. No hope of recovery. It was my fault for messing with something that I knew nothing about but just want to caution anyone thinking of doing this to be very careful.
I changed permissions for this folder and locked up the phone and it won't even let me Odin, flash through recovery or sideload through adb.
So my device is toast.
Just be wary of messing with things unfamiliar.
Click to expand...
Click to collapse
Sorry I changed the directions because I could have been more clear. You messed with the system folder? I was saying to make the system r/w and chmod 644 the file feature.xml under /system/csc/. The system folder it self should be chmod 755, but you dont chmod the system to anything, leave the system folder alone in fact never change the permissions of /system or any folder within the /system directory, only change it on files within a folder. For example /system and /system/csc should both be rwxr-xr-x (755) and never changed, while /system/csc/feature.xml should have its permissions set to rw-r--r-- (644) What do you mean you cant Odin what happens when you try?
what's chmod 644?? I've been around a while but I never heard that before?
Sent from my VZW Galaxy Note 3
Southern_mind said:
what's chmod 644?? I've been around a while but I never heard that before?
Sent from my VZW Galaxy Note 3
Click to expand...
Click to collapse
When people say"push the app to /system and then change permissions" the permissions they are referring to is setting chmod the app to 644 which is setting the permissions for the owner, group and others.
chmod 644 = rw-r--r--
Owners -6 = read and write
Group - 4 = read only
Others -4 = read only
Number convention:
4 = read only
2 = write only
4 + 2 = 6
6 = read and write
5 = read and execute
5+2 =7
7= read, write and execute
Sent from my SCH-I535 using xda app-developers app
Southern_mind said:
what's chmod 644?? I've been around a while but I never heard that before?
Click to expand...
Click to collapse
That's the UNIX "change mode" command. That's the way that UNIX systems define the protection mode for files.
644 is a protection mode, meaning read/write for owner (6), read for group (4), read for all (4).
Your root file manager should be able to allow you to set the mode and ownership of any file that you copy around.
Surge1223 said:
When people say"push the app to /system and then change permissions" the permissions they are referring to is setting chmod the app to 644 which is setting the permissions for the owner, group and others.
chmod 644 = rw-r--r--
Owners -6 = read and write
Group - 4 = read only
Others -4 = read only
Number convention:
4 = read only
2 = write only
4 + 2 = 6
6 = read and write
5 = read and execute
5+2 =7
7= read, write and execute
Sent from my SCH-I535 using xda app-developers app
Click to expand...
Click to collapse
k1mu said:
That's the UNIX "change mode" command. That's the way that UNIX systems define the protection mode for files.
644 is a protection mode, meaning read/write for owner (6), read for group (4), read for all (4).
Your root file manager should be able to allow you to set the mode and ownership of any file that you copy around.
Click to expand...
Click to collapse
Well thanks for the info. I've been doing that for years and didn't know that.
Surge1223 said:
Sorry I changed the directions because I could have been more clear. You messed with the system folder? I was saying to make the system r/w and chmod 644 the file feature.xml under /system/csc/. The system folder it self should be chmod 755, but you dont chmod the system to anything, leave the system folder alone in fact never change the permissions of /system or any folder within the /system directory, only change it on files within a folder. For example /system and /system/csc should both be rwxr-xr-x (755) and never changed, while /system/csc/feature.xml should have its permissions set to rw-r--r-- (644) What do you mean you cant Odin what happens when you try?
Click to expand...
Click to collapse
I am certainly not blaming anyone for this, it was clearly my fault for messing where I shouldn't be but I appreciate you wanting to help.
After I changed the system folder permissions, it immediately crashed. When it rebooted it bootlooped twice then booted into system recovery where the android guy lay on his back dead with a red exclamation point in his belly. It simply said error and nothing else but gave options to update, reboot, wipe, the usual.
I tried every file to be had that I could download for Odin, or recovery update. Odin simply failed every time. Recovery update always said signature match fail on every rom file. I must have tried 6 different rom files including one that is claimed to be the ME7 newest update untouched.
All methods completely failed.
I have rooted for years, installed countless ROM files on all my phones and this is the first I have bricked. I am not anything more than a reader that follow directions when it comes to this stuff, but have always been able to fix any problems until this one.
I have read threads on unbricking until I am sick of reading and trying. I guess its time to throw in the towel.
Thanks for updating the directions so nobody else does the stupid that I did.
dimitrisg said:
I am certainly not blaming anyone for this, it was clearly my fault for messing where I shouldn't be but I appreciate you wanting to help.
After I changed the system folder permissions, it immediately crashed. When it rebooted it bootlooped twice then booted into system recovery where the android guy lay on his back dead with a red exclamation point in his belly. It simply said error and nothing else but gave options to update, reboot, wipe, the usual.
I tried every file to be had that I could download for Odin, or recovery update. Odin simply failed every time. Recovery update always said signature match fail on every rom file. I must have tried 6 different rom files including one that is claimed to be the ME7 newest update untouched.
All methods completely failed.
I have rooted for years, installed countless ROM files on all my phones and this is the first I have bricked. I am not anything more than a reader that follow directions when it comes to this stuff, but have always been able to fix any problems until this one.
I have read threads on unbricking until I am sick of reading and trying. I guess its time to throw in the towel.
Thanks for updating the directions so nobody else does the stupid that I did.
Click to expand...
Click to collapse
Did you try to use adb at all? Where does odin fail at? You can try three suggestions I have, but first install android-sdk tools and make sure adb is working.
1. Connect your phone to your pc via usb and run the attached adb_system_fix.bat file found in the the Samsung_Tools folder ive uploaded here while your phone is attempting to boot.
2. Boot to recovery and try the to use adb/ab sideload there and enter the following
Code:
adb shell su -c "mount -o remount rw /system"
adb shell chmod 755 /system
3.(last resort, try any other suggestion first!)
Download the VRUEMJ7 stock odin tar from here and extract the .pit file from within (temporarily rename the tar.md5 to tar to extract) then boot to download mode and open Odin 3.09 and select the pit file in the pit slot (also check repartition) and the odin tar in AP. Hit start
Sent from my SCH-I535 using xda app-developers app
Surge1223 said:
Did you try to use adb at all? Where does odin fail at? You can try three suggestions I have, but first install android-sdk tools and make sure adb is working.
1. Connect your phone to your pc via usb and run the attached adb_system_fix.bat file found in the the Samsung_Tools folder ive uploaded here while your phone is attempting to boot.
2. Boot to recovery and try the to use adb/ab sideload there and enter the following
Code:
adb shell su -c "mount -o remount rw /system"
adb shell chmod 755 /system
3.(last resort, try any other suggestion first!)
Download the VRUEMJ7 stock odin tar from here and extract the .pit file from within (temporarily rename the tar.md5 to tar to extract) then boot to download mode and open Odin 3.09 and select the pit file in the pit slot (also check repartition) and the odin tar in AP. Hit start
Sent from my SCH-I535 using xda app-developers app
Click to expand...
Click to collapse
Wow! Ok, sounds promising. Will do so now. I will post again with results.
Thanks!:fingers-crossed:
---------- Post added at 09:12 PM ---------- Previous post was at 08:37 PM ----------
Surge1223 said:
Did you try to use adb at all? Where does odin fail at? You can try three suggestions I have, but first install android-sdk tools and make sure adb is working.
1. Connect your phone to your pc via usb and run the attached adb_system_fix.bat file found in the the Samsung_Tools folder ive uploaded here while your phone is attempting to boot.
2. Boot to recovery and try the to use adb/ab sideload there and enter the following
Code:
adb shell su -c "mount -o remount rw /system"
adb shell chmod 755 /system
3.(last resort, try any other suggestion first!)
Download the VRUEMJ7 stock odin tar from here and extract the .pit file from within (temporarily rename the tar.md5 to tar to extract) then boot to download mode and open Odin 3.09 and select the pit file in the pit slot (also check repartition) and the odin tar in AP. Hit start
Sent from my SCH-I535 using xda app-developers app
Click to expand...
Click to collapse
Can you give me some direction on how to perform the adb operation. I am able to boot to recovery, I have adb installed and know how to access it from CMD window. But not sure how to send commands to phone.
Can you help a little more?
I tried method 1 but it did nothing. What I did was starting the bat file and then booted phone. It just kept buzzing over and over like a fast bootloop.
Going to try method 2 but a little lost.
Please help a little more?
Thanks
dimitrisg said:
Wow! Ok, sounds promising. Will do so now. I will post again with results.
Thanks!:fingers-crossed:
---------- Post added at 09:12 PM ---------- Previous post was at 08:37 PM ----------
Can you give me some direction on how to perform the adb operation. I am able to boot to recovery, I have adb installed and know how to access it from CMD window. But not sure how to send commands to phone.
Can you help a little more?
I tried method 1 but it did nothing. What I did was starting the bat file and then booted phone. It just kept buzzing over and over like a fast bootloop.
Going to try method 2 but a little lost.
Please help a little more?
Thanks
Click to expand...
Click to collapse
Alright open a cmd prompt as admin. Then type:
Code:
adb devices
It should say something
Then type
Code:
adb shell
su
mount -o remount,rw /system
chmod 755 /system
adb reboot
Sent from my SCH-I535 using xda app-developers app
Surge1223 said:
Alright open a cmd prompt as admin. Then type:
Code:
adb devices
It should say something
Then type
Code:
adb shell
su
mount -o remount,rw /system
chmod 755 /system
adb reboot
Sent from my SCH-I535 using xda app-developers app
Click to expand...
Click to collapse
Well as expected it failed. Anything I type in and enter I get "error: closed"
It is a lost cause I am afraid.
I am considering method 3 and can follow most of the instructions, but the last instruction is where I lose you. It says "..and the Odin file in the AP". is that supposed to be PDA?
After this I wont bug you anymore since it is obviously a lost cause.
Thanks for everything.
dimitrisg said:
Well as expected it failed. Anything I type in and enter I get "error: closed"
It is a lost cause I am afraid.
I am considering method 3 and can follow most of the instructions, but the last instruction is where I lose you. It says "..and the Odin file in the AP". is that supposed to be PDA?
After this I wont bug you anymore since it is obviously a lost cause.
Thanks for everything.
Click to expand...
Click to collapse
Alright I sent you a pm
Will this trigger any part of verizons security? will the system know if something was flashed?
can someone explain how to use bypasslkm in further detail. i looked through multiple threads but im stilll not getting the handle on it,
Open your terminal emulator on your phone (download one from Google play if you don't have one) open the terminal and type the following commands (Pressing enter to execute each one)
su (sands for switch user, used alone will switch you to the "root" user. Equilivent to Admin in windows)
cd /data/local/temp (cd - change directory, followed by the complete folder path you want to navigate to)
chmod 755 bypasslkm (not going to get too in depth with this one because I could go on for a while with it but "chmod 755" changes the permissions to read, write, execute for the root user and read/execute for everyone else)
. /bypasslkm (. / tells the system to look in the current directory and, in this case, execute bypasslkm)
Hope this helps clear some things up for you!
Sent from my SCH-I545 using XDA Premium HD app
sfgrimes said:
Open your terminal emulator on your phone (download one from Google play if you don't have one) open the terminal and type the following commands (Pressing enter to execute each one)
su (sands for switch user, used alone will switch you to the "root" user. Equilivent to Admin in windows)
cd /data/local/temp (cd - change directory, followed by the complete folder path you want to navigate to)
chmod 755 bypasslkm (not going to get too in depth with this one because I could go on for a while with it but "chmod 755" changes the permissions to read, write, execute for the root user and read/execute for everyone else)
. /bypasslkm (. / tells the system to look in the current directory and, in this case, execute bypasslkm)
Hope this helps clear some things up for you!
Sent from my SCH-I545 using XDA Premium HD
I keep getting a message saying that there is no such directory after trying to execute "chmod 755 bypasslkm"
Click to expand...
Click to collapse
Deleted
Sent from my SCH-I545 using Tapatalk
JTSDeveloper said:
I keep getting a message saying that there is no such directory after trying to execute "chmod 755 bypasslkm"
Click to expand...
Click to collapse
I had the same issue. Here is the binary from Surges dropbox https://www.dropbox.com/s/9rdz9ff6x5foech/bypasslkm
Make sure you copy it to the right directory and follow all the commands.
Sent from my SCH-I545 using XDA Premium HD app
To add to the above post, after downloading that just execute this in terminal
Code:
su
mount -o remount,rw /system
find . -name "bypasslkm" -exec cp {} /data/local/tmp \;
find /data/local/tmp -name "bypasslkm" -type f -exec chmod 755 {} \;
./data/local/tmp/bypasslkm
insmod /system/lib/modules/dhd.ko
exit
Surge1223 said:
To add to the above post, after downloading that just execute this in terminal
Code:
su
mount -o remount,rw /system
find . -name "bypasslkm" -exec cp {} /data/local/tmp \;
find /data/local/tmp -name "bypasslkm" -type f -exec chmod 755 {} \;
./data/local/tmp/bypasslkm
insmod /system/lib/modules/dhd.ko
exit
Click to expand...
Click to collapse
I got the following error trying to execute after downloading the bypasslkm file and doing what you said
JTSDeveloper said:
I got the following error trying to execute after downloading the bypasslkm file and doing what you said
Click to expand...
Click to collapse
Thats not an error. If you had bypasslkm anywhere on your phone, it should now be in /data/local/tmp with the right permissions and should have executed. Make sure you downloaded the bypasslkm binary linked above
Edit: Also just copy and paste the whole script to make things easier
Sent from my SCH-I545 using XDA Premium 4 mobile app
Surge1223 said:
Thats not an error. If you had bypasslkm anywhere on your phone, it should now be in /data/local/tmp with the right permissions and should have executed. Make sure you downloaded the bypasslkm binary linked above
Edit: Also just copy and paste the whole script to make things easier
Sent from my SCH-I545 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
It's still not working. Any ideas? Should I move it directly into /data/local/tmp
Surge1223 said:
Thats not an error. If you had bypasslkm anywhere on your phone, it should now be in /data/local/tmp with the right permissions and should have executed. Make sure you downloaded the bypasslkm binary linked above
Edit: Also just copy and paste the whole script to make things easier
Sent from my SCH-I545 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
I downloaded the binary from above and pasted it directly in data/local/tmp then tried it and it still didn't work :/ what should the permissions on the file be? I'm a noob at this stuff
JTSDeveloper said:
I downloaded the binary from above and pasted it directly in data/local/tmp then tried it and it still didn't work :/ what should the permissions on the file be? I'm a noob at this stuff
Click to expand...
Click to collapse
The permissions should be 755, as Surge said.
If you KNOW it's in /data/local/tmp, then do this in a terminal emulator window:
Code:
su
mount -o remount,rw /system
chmod 755 /data/local/tmp/bypasslkm
/data/local/tmp/bypasslkm
insmod /system/lib/modules/dhd.ko
mount -o remount,ro /system
exit
If this doesn't work, DO NOT post just "it didn't work". Say what you did, why you think it failed. Capture the output and reply here with it.
Solution to the 755 bypasslkm issue!!!!!
k1mu said:
The permissions should be 755, as Surge said.
If you KNOW it's in /data/local/tmp, then do this in a terminal emulator window:
Code:
su
mount -o remount,rw /system
chmod 755 /data/local/tmp/bypasslkm
/data/local/tmp/bypasslkm
insmod /system/lib/modules/dhd.ko
mount -o remount,ro /system
exit
If this doesn't work, DO NOT post just "it didn't work". Say what you did, why you think it failed. Capture the output and reply here with it.
Click to expand...
Click to collapse
I figured it out! Here is exactly what I did:
after downloading the bypasslkm.bin from the dropbox link, I used ES File Explorer (WITH ROOT ENABLED) to move the bypasslkm file to directly to the data/local/tmp location. NOTE: there are a few places marked "data" and "local" on the phone, so when you open a "data" folder, make sure you find the path in the right order [ i.e. first data, then local, and then tmp]
Using a ROOT FILE EXPLORER app (because ES doesn't have what you will need) go to the bypasslkm file, long press, and select permissions. It will display with permissions are currently set. At the bottom, it SHOULD display the total sum of the permissions selected. Basically, that means by selecting the right boxes, you can change the permissions to 755 !
7 5 5
user group world
r+w+x r+x r+x
4+2+1 4+0+1 4+0+1 = 755
These setting will give you the 755 that you need to pull this off .
When you have the permissions changed to 755, the last step was actually very easy. But if you want to play it safe, then I will tell you the root file browser I specifically used to do the last step.
I used the app Root Browser version 2.2.3 ( i literally googled for any generic root file explorer and this came up )
ok, so when you have the permissions changed, long press on the bypasslkm file.
select "Open With" and then select the option "Open As.."
At the bottom of the options is "script file" select it.
after doing so, select the option "Execute" and... Voila! I immediately regained my WIFI !!!!! \>w</
I hope this guide helped everyone out. I tried to be as specific as possible.
EinGlo said:
I figured it out! Here is exactly what I did:
after downloading the bypasslkm.bin from the dropbox link, I used ES File Explorer (WITH ROOT ENABLED) to move the bypasslkm file to directly to the data/local/tmp location. NOTE: there are a few places marked "data" and "local" on the phone, so when you open a "data" folder, make sure you find the path in the right order [ i.e. first data, then local, and then tmp]
Using a ROOT FILE EXPLORER app (because ES doesn't have what you will need) go to the bypasslkm file, long press, and select permissions. It will display with permissions are currently set. At the bottom, it SHOULD display the total sum of the permissions selected. Basically, that means by selecting the right boxes, you can change the permissions to 755 !
7 5 5
user group world
r+w+x r+x r+x
4+2+1 4+0+1 4+0+1 = 755
These setting will give you the 755 that you need to pull this off .
When you have the permissions changed to 755, the last step was actually very easy. But if you want to play it safe, then I will tell you the root file browser I specifically used to do the last step.
I used the app Root Browser version 2.2.3 ( i literally googled for any generic root file explorer and this came up )
ok, so when you have the permissions changed, long press on the bypasslkm file.
select "Open With" and then select the option "Open As.."
At the bottom of the options is "script file" select it.
after doing so, select the option "Execute" and... Voila! I immediately regained my WIFI !!!!! \>w</
I hope this guide helped everyone out. I tried to be as specific as possible.
Click to expand...
Click to collapse
worked perfectly and all my confusion is now gone thank you.
Fix works but new issue
JTSDeveloper said:
worked perfectly and all my confusion is now gone thank you.
Click to expand...
Click to collapse
Thanks for the support. Glad I could help. Has your WIFI remained on, though? The solution I posted works, but only for a short amount of time. rebooting the system undoes the work I did and I have to go back into the root browser and execute the file all over again to get wifi.
Can Surge or someone else offer any expertise?
with the permissions changed properly, I tried executing the code, and still not working.
I have safestrap enabled, and I have sound restored. I am currently on android 4.3 from the downgrade provided by Surge. Its rooted.
If I were to upgrade to the rooted version of NC5, would that help fix the wifi issue, or would it carry over?
Any input going forward is appreciated!
EinGlo said:
Thanks for the support. Glad I could help. Has your WIFI remained on, though? The solution I posted works, but only for a short amount of time. rebooting the system undoes the work I did and I have to go back into the root browser and execute the file all over again to get wifi.
Can Surge or someone else offer any expertise?
with the permissions changed properly, I tried executing the code, and still not working.
I have safestrap enabled, and I have sound restored. I am currently on android 4.3 from the downgrade provided by Surge. Its rooted.
If I were to upgrade to the rooted version of NC5, would that help fix the wifi issue, or would it carry over?
Any input going forward is appreciated!
Click to expand...
Click to collapse
It is possible to automate this.
Create a file with the following contents:
Code:
#!/system/bin/sh
/data/local/tmp/bypasslkm
insmod /system/lib/modules/dhd.ko
exit
Save this file as /system/etc/install-recovery-2.sh.
Make sure that the bypasslkm file is in /data/local/tmp.
Reboot, and you should now have WiFi again.
[Note: this assumes SuperSU has it's custom copy of /system/etc/install-recovery.sh in place. If that's not there, it's still possible to edit /init.rc to add a stanza to run this command.]
Issue with auto-running my solution
k1mu said:
It is possible to automate this.
Create a file with the following contents:
Code:
#!/system/bin/sh
/data/local/tmp/bypasslkm
insmod /system/lib/modules/dhd.ko
exit
Save this file as /system/etc/install-recovery-2.sh.
Make sure that the bypasslkm file is in /data/local/tmp.
Reboot, and you should now have WiFi again.
[Note: this assumes SuperSU has it's custom copy of /system/etc/install-recovery.sh in place. If that's not there, it's still possible to edit /init.rc to add a stanza to run this command.]
Click to expand...
Click to collapse
I do NOT have supersu's install recovery 2 file in the location you said. I only have the regular install recovery file.
What I should I do? Could I create the file in laptops termial?
The first line of code gave me the error "file not found"
update
EinGlo said:
I do NOT have supersu's install recovery 2 file in the location you said. I only have the regular install recovery file.
What I should I do? Could I create the file in laptops termial?
The first line of code gave me the error "file not found"
Click to expand...
Click to collapse
I tried again.
Ok, so I figured out the coding a little bit. Im not used to this, so forgive my ignorance.
I did the code as u typed it. BUT I made a change. Because I kept getting the "file not found " error. I added ".bin" to the end of the bypasslkm code line. It generated a real response. I felt relieved. I went ahead and typed the last line of code.
THEN I was told the file already exists... I have attached a picture of what I got in android Terminal
EinGlo said:
I do NOT have supersu's install recovery 2 file in the location you said. I only have the regular install recovery file.
What I should I do? Could I create the file in laptops termial?
The first line of code gave me the error "file not found"
Click to expand...
Click to collapse
You should have /system/etc/install-recovery.sh
It will run /system/etc/install-recovery-2.sh if it exists. What I would do is to create the file on your PC, put it onto your SDcard on the PC, then use Root Explorer to put it into place.
The "file exists" error is because you already have the WiFi module installed. That won't happen when this script runs at boot.
Question
k1mu said:
You should have /system/etc/install-recovery.sh
It will run /system/etc/install-recovery-2.sh if it exists. What I would do is to create the file on your PC, put it onto your SDcard on the PC, then use Root Explorer to put it into place.
The "file exists" error is because you already have the WiFi module installed. That won't happen when this script runs at boot.
Click to expand...
Click to collapse
Ok. I'll try that tonight.
But I have a few questions
Im basically trying to autostart the wifi module when the phone boots up right? Are there any apps that can accomplish this specific task?
Also about the downgrade in general. Did anyone get their SD card permissions restored after downgrading? I donwgraded to 4.3, rooted the phone, and somehow I STILL cant move apps to the sd card! Im beginning to suspect that thr issue may be with the card itself, which can be fixed with formatting the sd card. But has anyone had any problems with moving apps to the sd card?
Finally, the bug question concerning the wifi issue.
Is this probkem specific only to those with the downgrade? If so, should upgrading to Surge's rooted kitkat (with sd card permissions and tethered enabled) resolve the wifi issue?
I also noticed that I had wifi access when the phone had no sound. Only when I flashed the Non-HLOS bin file did I encounter this wifi issue.
Thanks for the feedback so far, I just need to understand whrre to go from here
EinGlo said:
Ok. I'll try that tonight.
But I have a few questions
Im basically trying to autostart the wifi module when the phone boots up right? Are there any apps that can accomplish this specific task?
Click to expand...
Click to collapse
I'm sure there are programs that can be set up to run scripts as root during boot; However, that's complicated since you want this to run while the phone is booting, before there's any opportunity to allow SuperSU to ask for permission.
EinGlo said:
Also about the downgrade in general. Did anyone get their SD card permissions restored after downgrading? I donwgraded to 4.3, rooted the phone, and somehow I STILL cant move apps to the sd card! Im beginning to suspect that thr issue may be with the card itself, which can be fixed with formatting the sd card. But has anyone had any problems with moving apps to the sd card?
Click to expand...
Click to collapse
That's a problem that's fixed by an edit to /system/etc/permissions/platform.xml, adding a stanza that permits external storage write access.
EinGlo said:
Finally, the bug question concerning the wifi issue.
Is this probkem specific only to those with the downgrade? If so, should upgrading to Surge's rooted kitkat (with sd card permissions and tethered enabled) resolve the wifi issue?
I also noticed that I had wifi access when the phone had no sound. Only when I flashed the Non-HLOS bin file did I encounter this wifi issue.
Thanks for the feedback so far, I just need to understand whrre to go from here
Click to expand...
Click to collapse
The need to run the "bypasslkm" program is because of the downgrade. If you go to a clean rooted Kit Kat ROM, it shouldn't have any issues with WiFi being enabled. That may be the easiest way to fix this.