Related
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?
Hey guys
I finished building CWM Recovery for locked bootloaders.
its still in the beta phases.... actually there was no alpha tests because no one on my team has a l5 II.
Due to forum rules I cannot choose who I want to give this recovery or exclude anyone from using it. so if you are a noob I cannot stop you from using it but please dont blame me if you brick your device!!!!!
The recovery as far as I know has no errors.
I have tested flashing Mother of all ad blocking and it worked perfectly.
How Does It Work?
the recovery uses 2nd int.
when your phone boots It is hacked to load scripts from init.d folder.
inside the init.d folder there is a script called 1.unsecure
this stops the system an kills process and launches the recovery.
How Do I Install?
Busybox must be installed
Extract the zip(attached)
Run the init.bat
Enjoy
How Do I Enter Recovery?
Reboot
after the lg logo before your boot animation starts repetitively hit the Vol + key
or run the reboot recovery app
Who do I thank?
ME for all the hard work testing and retesting
@IGGYVIP for giving me hope that its possible and all the support he has given me so far.
Optima Team for being such a great team
Can I port this to my device?
Yes!!
Port this to as many devices as possible. If you need advice or need to know how to port feel free to PM me.
It doesnt work for me?
some user experience problems when the script applies permissions
to fix this
Change permissions to all files in /system/bootstrap/* to 775
Download
DOWNLOAD
Great work man! Optima Team is proud of you!!!
Sent from my GT-I9300 using Tapatalk
slipsystem said:
Hey guys
I finished building CWM Recovery for locked bootloaders.
its still in the beta phases.... actually there was no alpha tests because no one on my team has a l5 II.
Due to forum rules I cannot choose who I want to give this recovery or exclude anyone from using it. so if you are a noob I cannot stop you from using it but please dont blame me if you brick your device!!!!!
The recovery as far as I know has no errors.
I have tested flashing Mother of all ad blocking and it worked perfectly.
How Does It Work?
the recovery uses 2nd int.
when your phone boots It is hacked to load scripts from init.d folder.
inside the init.d folder there is a script called 1.unsecure
this stops the system an kills process and launches the recovery.
How Do I Install?
Busybox must be installed
Extract the zip(attached)
Run the init.bat
Enjoy
How Do I Enter Recovery?
Reboot
after the lg logo before your boot animation starts repetitively hit the Vol + key
Who do I thank?
ME for all the hard work testing and retesting
@IGGYVIP for giving me hope that its possible and all the support he has given me so far.
Optima Team for being such a great team
Can I port this to my device?
Yes!!
Port this to as many devices as possible. If you need advice or need to know how to port feel free to PM me.
Download
https://dl.dropboxusercontent.com/u/51036208/Android/Stock/cwm.zip
Click to expand...
Click to collapse
why not mod one of the 2nd-init recovery apks with this?? Make much simpler for n00bs as well as give the reboot to recovery option.
Modding the apk I have exp with, I just never had any success building a working 2nd-init binary.
PlayfulGod said:
why not mod one of the 2nd-init recovery apks with this?? Make much simpler for n00bs as well as give the reboot to recovery option.
Modding the apk I have exp with, I just never had any success building a working 2nd-init binary.
Click to expand...
Click to collapse
The apk pushes the script to a different location and only executes on the l3 ii. So the app doesn't work on the l5 ii. I would have to do allot of editting. Enable init.d and change where the files get pushed to.
But it's pretty simple for noobs.
And this is not ment for noobs as I said on my thread its still on beta testing.
slipsystem said:
The apk pushes the script to a different location and only executes on the l3 ii. So the app doesn't work on the l5 ii. I would have to do allot of editting. Enable init.d and change where the files get pushed to.
But it's pretty simple for noobs.
And this is not ment for noobs as I said on my thread its still on beta testing.
Click to expand...
Click to collapse
ahh, I've just messed with 2nd-init on the LG Motion & Spirit and the same apk works on the F3, F6, & F7 (I think). The Spirit no longer needs 2nd-init tho.
PlayfulGod said:
ahh, I've just messed with 2nd-init on the LG Motion & Spirit and the same apk works on the F3, F6, & F7 (I think). The Spirit no longer needs 2nd-init tho.
Click to expand...
Click to collapse
Ya I think the apology works on most devices. If not then mine should work pr you will just have to change the key. It's pretty simple to port. I will try make. A guide tommorow
Awesome Work Mate !!!
@slipsystem
Great Job
You have made so much more out of that apk then i ever would
I can see Newsworthy thread when porting to other devices works
I can't reboon in recovery mode
Hello, I can not reboot in recovery mode, I was run the init.bat, then, reboot my L5 II (e450f) and pressed repetitively the Vol + key. But I never reboot in recovery
Could you help me?
PS. Your team is awesome!!
jamonazo3000 said:
Hello, I can not reboot in recovery mode, I was run the init.bat, then, reboot my L5 II (e450f) and pressed repetitively the Vol + key. But I never reboot in recovery
Could you help me?
PS. Your team is awesome!!
Click to expand...
Click to collapse
Check
/data/local/tmp
There is a file called init.d_log_test
Check if you have that file
Open it check if the date and time matches your last reboot.
Great! Now we only need custom roms and android updates.
jamonazo3000 said:
Hello, I can not reboot in recovery mode, I was run the init.bat, then, reboot my L5 II (e450f) and pressed repetitively the Vol + key. But I never reboot in recovery
Could you help me?
PS. Your team is awesome!!
Click to expand...
Click to collapse
Sorry its dues to permissions
Change permissions to all files in /system/bootstrap/* to 775
slipsystem said:
Sorry its dues to permissions
Change permissions to all files in /system/bootstrap/* to 775
Click to expand...
Click to collapse
the init.sh has chmod rules to 755
the attached one has 775
Updated Version in first post!
Now Includes Reboot Recovery app
and hopefully fixed permission problem.
slipsystem said:
Check
/data/local/tmp
There is a file called init.d_log_test
Check if you have that file
Open it check if the date and time matches your last reboot.
Click to expand...
Click to collapse
Hello, I was open /data/local/temp/ and only can see a file recoverylog.txt
I will check your new update.
Thanks for all
IGGYVIP said:
the init.sh has chmod rules to 755
the attached one has 775
Click to expand...
Click to collapse
sorry my math is bad. the permission are meant to be 755. for some reason when shell is changing permissions it gets permission denied.
I think that the script 001unsecureboot doesn't kill the bootanimation, in fact when I reboot to recovery there is the bootanimation (deformed and with strange colors) on the screen, and only when I press a key the recovery appears for one second.
After adding the line "$BB killall bootanimation" after "$BB mount -o remount,rw /system /system", the issue is solved.
ownership ?
slipsystem said:
sorry my math is bad. the permission are meant to be 755. for some reason when shell is changing permissions it gets permission denied.
Click to expand...
Click to collapse
May be try changing owner to root before changing permissions ?
in the .sh add this code before chmod but after the remount,rw
Code:
chown -R root /system/bootstrap
in theory as its owner it must allow change of permission
Let me know
IGGYVIP said:
May be try changing owner to root before changing permissions ?
in the .sh add this code before chmod but after the remount,rw
Code:
chown -R root /system/bootstrap
in theory as its owner it must allow change of permission
Let me know
Click to expand...
Click to collapse
I actually had the script setting permission for
/System/etc/bootstrap
And not
/System/bootstrap
@HandyMenny
Thanks For that. I added that in a update.
slipsystem said:
I actually had the script setting permission for
/System/etc/bootstrap
And not
/System/bootstrap
Click to expand...
Click to collapse
with system as System? never had em capped b4.
Does anyone know how I can implement a custom ROM but have it urooted
I need an unrooted for work. I have tried rootcloak type applications but they don't do the trick. Plus, this is for work so, in order to comply with requirements I want to make sure phone is not rooted rather than just hiding root
Reason I want to use custom ROM is to get additional features such as dropdown menu on main page, remove unwanted app (malware) and have smallest footprint possible
wrong thread. post in q&a
Flash custom ROM.
Download Root explorer or any other root explorer app
Navigate to system.
delete
Code:
/system/app/Superuser.apk
Code:
/system/xbin/su
or
Code:
/system/bin/su
reboot the phone
That should do it.
karandpr said:
Flash custom ROM.
Download Root explorer or any other root explorer app
Navigate to system.
delete
Code:
/system/app/Superuser.apk
Code:
/system/xbin/su
or
Code:
/system/bin/su
reboot the phone
That should do it.
Click to expand...
Click to collapse
Thank you - will try and see how it goes
jean001luc said:
Thank you - will try and see how it goes
Click to expand...
Click to collapse
No good. Deleted system/bin/su and xbin/su but could not find system/apps/superuser
Rebooted device and still rooted
what ROM are you using ?
it could be
/system/app/superuser.apk
/system/app/Superuser.apk
/system/app/SuperSU.apk
/system/app/eu.chainfire.supersu.apk
/system/app/com.koushikdutta.superuser.apk
/system/app/com.noshufou.android.su.apk
in anycase ,you will need to reflash ROM or reflash superuser.
Technically the "Superuser" app is a front end for /system/bin/su...So you are unrooted, Just you need to remove that app..
DISCLAIMER : You attempt the following at your own risk !
I'm not responsible if your phone blows up, bricks, you travel back in time or go bald or something!
Background :
I have the MT2-L05 Mate 2 from China.
When I received my Mate 2 last Thursday, the phone was on 4.2.2
After much hunting and downloading and flashing of ROMS, I managed to finally update to 4.4.2 KitKat.
Great ! I was happy. But I didn't have root access.
After trying and failing to use the various bootloader unlock tools on these forums, I Emailed Huawei, and politely asked them if I could have the 16 digit code for my Mate 2. An hour later an Email arrived with my bootloader unlock code, so I fastbooted, used the code and unlocked the Bootloader.....Cool ! Thanks Huawei, great customer service.
I then went to root my phone, and here the problems started. I tried at least 20 different Root tools, both via phone and over the pc, but no joy.
Nothing worked ! Vroot, Kingoroot, Towelroot, srs root, root genius 1.8.7, etc they all failed.
I was at the point of giving up, when I found a Chinese version of rootgenius 2.0.1.3......I ran it via pc........and Success ! I was finally rooted.
Supersu was installed, the binaries updated fine and all was good with the world. I tried wakelock detector first ( Yeah, I know, I REALLY need more battery life from the Mate 2 ! ), and Supersu asked for permission and it worked no problem.
I then tried to install adaway, and then I ran into problems, I was unable to edit my hosts file....ummm...odd. OK, then I tried to install xposed......Impossible to install.
I then read on these forums to edit build.prop and change a simple setting to get xposed running.......ok, no problem, yet when I edited my build.prop file, it would NEVER EVER save the edits. Weird? what's going on?.......after much searching and much reading I finally found the problem.................
Root Genius 2.0.1.3 :
http://www.shuame.com/root/
The Problem :
The 4.4.2 update adds a file to your System folder called :
set_immutable.list
this file contains :
Code:
/system/bin
/system/build.prop
/system/etc
/system/fonts
/system/framework
/system/isp.bin
/system/lib
/system/ons.bin
/system/usr
/system/vendor
/system/xbin
/system/app/HwLauncher6.apk
/system/app/HwLauncher6.odex
/system/app/systemUI.apk
/system/app/systemUI.odex
Any location listed above is IMPOSSIBE to mount as rw. Every file explorer or emulator you try will tell you it is rw, but it's not.
It's locked down completely...................and it's REALLY annoying.
This is why I could never edit my build.prop or Install Adaway etc..................
But I found a solution...... ( I think ! )..........
The Solution :
I spent the afternoon at work using google translate to find a fix for my problem and found a post from a guy called :
**** wire His Royal Highness Prince czx ( I cannot post the first 4 letters as it will probably be banned....It must be a Google translate error but it made me laugh ! )
His guide never worked for me until I made a few edits and added STEP 4. Then I got it to work.
The Solution :
1, First Root your Phone ( I suggest trying Root Genius 2.0.1.3 from my first post )
2, install busybox (I suggest BusyBox ( Stericson ) as I couldn't get this to work with the Jrummy BusyBox installer )
3, Install Rom Toolbox Pro ( I know it's payware and I tried other programs, but this is the only one that worked for me. I had already purchased ages ago. The free version may contain the following tools too, but I genuinely don't know )
4, open Scripter from Rom Toolbox pro and click " Mount System R/W "
5, open Terminal Emulator from Rom Toolbox Pro
Type: su then press enter
Type: mount -o rw, remount / system then press enter
Type: cd system then press enter
Type: chattr -R -i * then press enter
(On step 5 there is a space between remount forward slash and system and also between i and *)
6, Leave Terminal Emulator open, Hit your Home Button
7, then delete the file :system / set_immutable.list with Root Explorer. Other File managers with root access may work, I haven't tried
If you can not delete it, the above steps haven't worked, I can only suggest you try from step 4 after rebooting your phone.
If you are successful and manage to delete the set_immutable.list file then reboot your phone.
Job Done !
You now have full Root Access.
This has been tested by myself on my MT2-L05, it should work on ALL China Variants and presumably on the US MT2-L03 if this file is included in a 4.4.2 update, but I obviously cannot guarantee this.
I'm also curious as to whether anyone thinks this has left my phone open to exploits by the deleting this file....? Remember, if I have done something stupid by doing this, then so will you if you follow the above!
All I know is Xposed has installed perfectly after finally being able to edit my build.prop file and Adaway is running like a charm.
Feedback very welcome.
4L0M said:
The Solution :
Snip
5, open Terminal Emulator from Rom Toolbox Pro
Type: su then press enter
Type: mount -o rw, remount / system then press enter
Type: cd system then press enter
Type: chattr -R -i * then press enter
(On step 5 there is a space between remount forward slash and system and also between i and *)
Snip
Click to expand...
Click to collapse
I followed your guide, the part I bolded didn't seem to work for me, but after a few attempts I just kept going with the rest of the guide and I was still able to delete the file at the end of the day Thank you so much! I always felt like the root I had with 4.2 was kind of a pseudo root since I was limited by my root access, this is exactly what I needed!
I manage to get root and delete that file. Hooray and thanks! But after editing the build.prop, I still can't get xposed to install. I keep getting this error on the install screen.
scpion said:
I manage to get root and delete that file. Hooray and thanks! But after editing the build.prop, I still can't get xposed to install. I keep getting this error on the install screen.
Click to expand...
Click to collapse
Install xposed 2.5.1, it's the safest option for now and you will not get this error message.
I haven't tried too many xposed apps yet, but wanam works if you want circle battery etc
Experimental features of Greenify work too.
Gravity box Kitkat will not run properly for me.. I suggest you do not attempt to install it at the moment.
Let me know if you find anymore cool xposed modules to try!
4L0M said:
Install xposed 2.5.1, it's the safest option for now and you will not get this error message.
I haven't tried too many xposed apps yet, but wanam works if you want circle battery etc
Experimental features of Greenify work too.
Gravity box Kitkat will not run properly for me.. I suggest you do not attempt to install it at the moment.
Let me know if you find anymore cool xposed modules to try!
Click to expand...
Click to collapse
Thanks dude. Btw does your device support Google search by swiping up from home?
scpion said:
I manage to get root and delete that file. Hooray and thanks! But after editing the build.prop, I still can't get xposed to install. I keep getting this error on the install screen.
Click to expand...
Click to collapse
Same issue for me
janrck said:
Same issue for me
Click to expand...
Click to collapse
Install xposed 2.5.1, it's the safest option for now and you will not get this error message.
Cool xposed apps for 2.5.1 :
wanam kit : adds circle battery, expanded notifications, 4-way reboot menu etc etc
Android L Navbar : adds Android L navbar and Android L shapes Navbar
Both work flawlessly for me and have NEVER crashed once.
Hi, I followed your steps but in the step 5, when i type this : mount -o rw, remount / system it doesnt work.
4L0M said:
DISCLAIMER : You attempt the following at your own risk !
Nothing worked ! Vroot, Kingoroot, Towelroot, srs root, root genius 1.8.7, etc they all failed.
I was at the point of giving up, when I found a Chinese version of rootgenius 2.0.1.3......I ran it via pc........and Success ! I was finally rooted.
Supersu was installed, the binaries updated fine
I then tried to install adaway, and then I ran into problems, I was unable to edit my hosts file....ummm...odd. OK, then I tried to install xposed......Impossible to install.
Click to expand...
Click to collapse
I then read on these forums to edit build.prop and change a simple setting to get xposed running.......ok, no problem, yet when I edited my build.prop file, it would NEVER EVER save the edits. Weird? what's going on?.......after much searching and much reading I finally found the problem.................
/QUOTE]
How was SU installed if you had no rw privs?
vroot, kingroot, kingoroot, kinguser, srs root and rootgenius were created for a select few... it was a side effect of massive social engineering via the internet that they'd leak to so many others who weren't the target.
magicpromise said:
I then read on these forums to edit build.prop and change a simple setting to get xposed running.......ok, no problem, yet when I edited my build.prop file, it would NEVER EVER save the edits. Weird? what's going on?.......after much searching and much reading I finally found the problem.................
/QUOTE]
How was SU installed if you had no rw privs?
vroot, kingroot, kingoroot, kinguser, srs root and rootgenius were created for a select few... it was a side effect of massive social engineering via the internet that they'd leak to so many others who weren't the target.
Click to expand...
Click to collapse
I'm guessing because I could write rw to system folder. Set-immutable-list blocks folders inside system folder, not the basic system folder itself. ie/ system/xbin or system/etc they are blocked. /system on its own isn't.
4L0M said:
I'm guessing because I could write rw to system folder. Set-immutable-list blocks folders inside system folder, not the basic system folder itself. ie/ system/xbin or system/etc they are blocked. /system on its own isn't.
Click to expand...
Click to collapse
yes, and the instructions worked great.
i made a script with it in totalrom and set it to load on boot along with total rom itself to keep a strangle hold on the permissions.
magicpromise said:
yes, and the instructions worked great.
i made a script with it in totalrom and set it to load on boot along with total rom itself to keep a strangle hold on the permissions.
Click to expand...
Click to collapse
Can you please upload the script you made?
You'll make things easy for me, 'cause commands in terminal don't seem to work in my case.
Thank's !
So with Android 7 there seems to be a change in the way the system partition works and I tried a ton of ways to make my /system partition as writable. I tried an app, I tried terminal commands, and I tried a root file explorer. Nothing working; adaway wouldn't work without systemless zip flash. Emoji Switcher was also not working.
Well I found a fast and simple solution!
Install busy box and a terminal app
- Install busy box on system
- Open terminal app
- Run "su" (no quotes)
- Give the terminal app root access
- Then run "busybox mount -o rw,remount system" (no quotes)
- You should get no errors; it will actual do nothing, it will just go to the next line.
Now test that bad boy out and your system partition should be writeable. No more host errors in adaway!
Going to try this out. Been looking for a solution to this as well. Thanks.
Sent from my Nexus 6P using Tapatalk
---------- Post added at 08:50 PM ---------- Previous post was at 08:43 PM ----------
phillymade said:
Going to try this out. Been looking for a solution to this as well. Thanks.
Sent from my Nexus 6P using Tapatalk
Click to expand...
Click to collapse
So if Busy Box is installed to data, do I need to uninstall and install to system for this to work properly. As of now I'm getting a not found error.
Sent from my Nexus 6P using Tapatalk
phillymade said:
Going to try this out. Been looking for a solution to this as well. Thanks.
Sent from my Nexus 6P using Tapatalk
---------- Post added at 08:50 PM ---------- Previous post was at 08:43 PM ----------
So if Busy Box is installed to data, do I need to uninstall and install to system for this to work properly. As of now I'm getting a not found error.
Sent from my Nexus 6P using Tapatalk
Click to expand...
Click to collapse
Yeah you need your busybox installed on the system or it wont do anything
I have my busy box installed at /su/xbin
In terminal make sure you put su (then hit enter)
then type the command
If you put them together you get an error for some weird reason
Here is a picture of my busybox install https://www.dropbox.com/s/iwtutkots8bdd13/Screenshot_20160830-184451.png?dl=0
Will this thread make DPI change on rooted 7.0 possible ? :laugh:
ArminasAnarion said:
Yeah you need your busybox installed on the system or it wont do anything
I have my busy box installed at /su/xbin
In terminal make sure you put su (then hit enter)
then type the command
If you put them together you get an error for some weird reason
Here is a picture of my busybox install https://www.dropbox.com/s/iwtutkots8bdd13/Screenshot_20160830-184451.png?dl=0
Click to expand...
Click to collapse
I did su then enter and got the error. perhaps it's where I have busy box installed.
Sent from my Nexus 6P using Tapatalk
ps000000 said:
Will this thread make DPI change on rooted 7.0 possible ? :laugh:
Click to expand...
Click to collapse
Yeah dpi change it possible on Android 7! Currently running 420dpi!
phillymade said:
I did su then enter and got the error. perhaps it's where I have busy box installed.
Sent from my Nexus 6P using Tapatalk
Click to expand...
Click to collapse
Make sure you install busybox on /su
This doesn’t work. After running this and then touch /sbin/su /system/bin/su /system/xbin/su
It says Read-only file system. Tried on the pixel c.
backslashV said:
This doesn’t work. After running this and then touch /sbin/su /system/bin/su /system/xbin/su
It says Read-only file system. Tried on the pixel c.
Click to expand...
Click to collapse
Wondering if this might help—running `blockdev --getro /dev/block/dm-0´ (my /system) returned “1” when I checked on Nexus 6P, and returned “0” after --setrw.
I wasn't able to sucessfully remount with the second command, however, due to ‘/system is busy’ or some such thing.
Code:
blockdev --setrw /dev/block/dm-0
mount -o remount,rw /system
You are a saint! While my /system was "writable" after root using Magisk, I couldn't change file permissions. Stumbled upon your method and was able to correct this, although I used my laptop. I had already installed busybox with Magisk, so I opened an adb shell, typed "su," then issued: busybox mount -o rw,remount system
Adaway, and AFWall+ is working fine and I was finally able to chmod 644 bootanimation.zip in /system/media of my Moto X Pure.
Thank you! :good:
Ericarthurc said:
So with Android 7 there seems to be a change in the way the system partition works and I tried a ton of ways to make my /system partition as writable. I tried an app, I tried terminal commands, and I tried a root file explorer. Nothing working; adaway wouldn't work without systemless zip flash. Emoji Switcher was also not working.
Well I found a fast and simple solution!
Install busy box and a terminal app
- Install busy box on system
- Open terminal app
- Run "su" (no quotes)
- Give the terminal app root access
- Then run "busybox mount -o rw,remount system" (no quotes)
- You should get no errors; it will actual do nothing, it will just go to the next line.
Now test that bad boy out and your system partition should be writeable. No more host errors in adaway!
Click to expand...
Click to collapse
* I installed BusyBox to /system/xbin using the app's install.
* I opened my Terminal app and typed su.
* I granted it access.
* I ran the exact command.
It just gave me another prompt as you said it should. But the File Manager that I have used on many rooted devices still won't let me check the box in its settings for Root Explore, even though it prompted me and I granted SuperUser access.
I don't get what I'm missing here.
UPDATE: I am now able to Apply Hosts in AdAway.
However, my File Manager that I have used in Root mode on every device still won't allow me to turn on "Root Explorer" mode. It did prompt me for SuperUser access and I did grant it (and double checked), but when I go to choose that option in the apps' Preferences, it says my device is not Rooted.
Any ideas?
Thank You.
Hi,
Okay, got it! Cancel my distress call.
Thank You!
Hi,
Had to redo my phone and while I can apply Hosts in AdAway (not being able to is a sure sign /System isn't Writable), when I try to make a change to my Build.Prop file found in /System it won't stay changed. I am using Nougat 7.0 with Magisk and every other Root app works fine.
Just for kicks, I tried running the commands you posted to see if it would help, but this time it didn't take the command (I do have BusyBox installed). Instead, it responded with; "Invalid Argument" as follows;
"mounting /dev/block/bootdevice/by-name/system on /system failed: Invalid Argument"
Then the prompt changed to "255|elsa:/ #"
Any ideas? It appears to see that BusyBox is installed, but it isn't working. Also, how do I check where my BusyBox is installed?
Thanks,
Dave