Samsung Galaxy S4 Thread (All versions para masaya)

[Ryanandrei]

New galaxy s4 user here. i9505. pano iroot yung latest firmware? updated yung akin e. nakita ko dun sa net ay I9505XXUFNA1 lang pwede. eh I9505XXUGNH8 na ako. gagana parin ba yung cf auto root?

 

[jaylence10]

New galaxy s4 user here. i9505. pano iroot yung latest firmware? updated yung akin e. nakita ko dun sa net ay I9505XXUFNA1 lang pwede. eh I9505XXUGNH8 na ako. gagana parin ba yung cf auto root?

yap.. fully compatible ang cf autoroot,..
yun nga lang magkakaroon ka ng random reboot


Para mafix ang reboot, refer ka dito:

Samsung Kitkat SystemServer Crash Fix ( Random Restart Fix )

Fixes Random Reboots from Rooted or Unrooted Kitkat

Download Fix: https://mega.co.nz/#!swVxUCiT!dm3spQ...h-xWCdiR_8Q_XU

Download Exposed: https://mega.co.nz/#!slki0bzY!W8f7tP...H7oF8Fl63o4nPY

KAILANGAN:
--- Rooted phone
--- Xposed Framework
--- Samsung Kitkat SystemServer Crash Fix

INSTRUCTIONS:
---- Install Exposed Framework (yung dinownload kanina)
---- Run/Launch Xposed.
---- Go to " Framework "
---- click " Install/ Update "
---- Grant root access then reboot..
---- After rebooting, go to " Download " search for:

Samsung Kitkat SystemServer Crash Fix (ito yung dinownload kanina sa itaas)

--- Install
--- Pagkatapos mainstall, bumalik ka sa main menu ng Xposed.
--- Select MODULE.
--- Lagyan ng check ang:

" Samsung Kitkat SystemServer Crash Fix "

--- Reboot

OR.... Debloat para mawala yung random reboot (delete ang mga KNOX related apps)

 

[Ryanandrei]

yap.. fully compatible ang cf autoroot,..
yun nga lang magkakaroon ka ng random reboot


Para mafix ang reboot, refer ka dito:

Samsung Kitkat SystemServer Crash Fix ( Random Restart Fix )

Fixes Random Reboots from Rooted or Unrooted Kitkat

Download Fix: https://mega.co.nz/#!swVxUCiT!dm3spQ...h-xWCdiR_8Q_XU

Download Exposed: https://mega.co.nz/#!slki0bzY!W8f7tP...H7oF8Fl63o4nPY

KAILANGAN:
--- Rooted phone
--- Xposed Framework
--- Samsung Kitkat SystemServer Crash Fix

INSTRUCTIONS:
---- Install Exposed Framework (yung dinownload kanina)
---- Run/Launch Xposed.
---- Go to " Framework "
---- click " Install/ Update "
---- Grant root access then reboot..
---- After rebooting, go to " Download " search for:

Samsung Kitkat SystemServer Crash Fix (ito yung dinownload kanina sa itaas)

--- Install
--- Pagkatapos mainstall, bumalik ka sa main menu ng Xposed.
--- Select MODULE.
--- Lagyan ng check ang:

" Samsung Kitkat SystemServer Crash Fix "

--- Reboot

OR.... Debloat para mawala yung random reboot (delete ang mga KNOX related apps)

thank you po sa fast response. will do po yung mga sinabi nyo.

EDIT: Ano po yung mga idedebloat na knox related apps? dedelete ko nalang po gamit titanium backup

 

[jaylence10]

thank you po sa fast response. will do po yung mga sinabi nyo.

EDIT: Ano po yung mga idedebloat na knox related apps? dedelete ko nalang po gamit titanium backup

Heto sir.. refer ka sa list,.. yan yung mga tinanggal ko sa phone ko.

View attachment 206249

Wag mo na pansinin yung ibang texts kasi galing yan sa debloater flashable zip ko.
Focus ka dun sa mga directories at pangalan nung mga apps..

Kung Knox-related lang ang tatanggalin mo heto yun (kasama na rin list sa itaas):

/system/app:

-- Bridge.apk
-- KNOXAgent.apk
-- KnoxMigrationAgent.apk
-- KnoxSetupWizardClient.apk
-- KnoxSetupWizardStub.apk
-- KNOXStore.apk

/system/priv-app:

-- KLMSAgent.apk

Meron pang ibang knox files, pero ok na yan, kahit hindi mo na tanggalin yung iba kasi critical yung mga natitira.
Bootloop ka pag nagkamali ka ng tanggal sa mga yun.. hehehe

Heto yung directory nung sinasabi kong iba pang files ng KNOX:

/system/container

 

[Ryanandrei]

Heto sir.. refer ka sa list,.. yan yung mga tinanggal ko sa phone ko.

View attachment 1012713

Wag mo na pansinin yung ibang texts kasi galing yan sa debloater flashable zip ko.
Focus ka dun sa mga directories at pangalan nung mga apps..

Kung Knox-related lang ang tatanggalin mo heto yun (kasama na rin list sa itaas):

/system/app:

-- Bridge.apk
-- KNOXAgent.apk
-- KnoxMigrationAgent.apk
-- KnoxSetupWizardClient.apk
-- KnoxSetupWizardStub.apk
-- KNOXStore.apk

/system/priv-app:

-- KLMSAgent.apk

Meron pang ibang knox files, pero ok na yan, kahit hindi mo na tanggalin yung iba kasi critical yung mga natitira.
Bootloop ka pag nagkamali ka ng tanggal sa mga yun.. hehehe

Heto yung directory nung sinasabi kong iba pang files ng KNOX:

/system/container

additional question lang po: bakit wala pong pit file yung odin? lagi po nagerror yung pagroroot. sinundan ko lang po yung nasa cf-auto root. tinry ko na rin yung towelroot pero not supported daw

 

[jaylence10]

additional question lang po: bakit wala pong pit file yung odin? lagi po nagerror yung pagroroot. sinundan ko lang po yung nasa cf-auto root. tinry ko na rin yung towelroot pero not supported daw

Hindi na kailangan ng pit file sir.. ginagamit lang yan kung bricked ang device or kung gusto mong mag repartition.
Kung CF autoroot ang gamit mo,

Dapat Autoreboot at F.Reset Time lang ang may check sa odin.
Lagay mo yung CF-Autoroot for i9505.tar.md5 sa AP.
Then reboot ka sa Download mode at connect sa computer ang phone.
Then hit START.

May isa pa akong gamit na pangroot dati sa NH8 ko.
Kingo Root v1.2.8 (pc app to sir at kailangan mong install sa computer)
Kailangan nya rin ng internet connection sa pagroot.
Working din yan. Maraming beses ko nang ginamit.

 

[Ryanandrei]

Hindi na kailangan ng pit file sir.. ginagamit lang yan kung bricked ang device or kung gusto mong mag repartition.
Kung CF autoroot ang gamit mo,

Dapat Autoreboot at F.Reset Time lang ang may check sa odin.
Lagay mo yung CF-Autoroot for i9505.tar.md5 sa AP.
Then reboot ka sa Download mode at connect sa computer ang phone.
Then hit START.

May isa pa akong gamit na pangroot dati sa NH8 ko.
Kingo Root v1.2.8 (pc app to sir at kailangan mong install sa computer)
Kailangan nya rin ng internet connection sa pagroot.
Working din yan. Maraming beses ko nang ginamit.

<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I9505_ROOT_Ker_W0lfDroid.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/004> Added!!
<ID:0/004> Odin v.3 engine (ID:4)..
<ID:0/004> File analysis..
<ID:0/004> SetupConnection..
<ID:0/004> Initialzation..
<ID:0/004> Get PIT for mapping..
<ID:0/004> Removed!!
<ID:0/004> There is no PIT partition.
<OSM> All threads completed. (succeed 0 / failed 1)


eto po lumilitaw na error sakin..

EDIT: nevermind. cable problem. gumamit ako ng mas maikling cable tapos ok na

 

[jaylence10]

<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I9505_ROOT_Ker_W0lfDroid.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/004> Added!!
<ID:0/004> Odin v.3 engine (ID:4)..
<ID:0/004> File analysis..
<ID:0/004> SetupConnection..
<ID:0/004> Initialzation..
<ID:0/004> Get PIT for mapping..
<ID:0/004> Removed!!
<ID:0/004> There is no PIT partition.
<OSM> All threads completed. (succeed 0 / failed 1)


eto po lumilitaw na error sakin..

EDIT: nevermind. cable problem. gumamit ako ng mas maikling cable tapos ok na

Heto sir ang gamitin mo:

https://mega.co.nz/#!h19CmRwI!n31osEWV7Dked452rUMlp_0TYjCCwtIId7zeVPPrhUE

Awww.. okay.. hehehe

 

[Ryanandrei]

Heto sir ang gamitin mo:

https://mega.co.nz/#!h19CmRwI!n31osEWV7Dked452rUMlp_0TYjCCwtIId7zeVPPrhUE

Awww.. okay.. hehehe

thanks po ulit btw.

 

[SigurdPutter]

ilang bwan pa kaya bago marelease yang lollipop update na yan?

 

[asus_abz]

ME nkasubok na ba neto?
Stock Lollipop for i9505 : Download LINk

eto ung link nung thread sa XDA: http://forum.xda-developers.com/showthread.php?t=2265477

 

[jaylence10]

ME nkasubok na ba neto?
Stock Lollipop for i9505 : Download LINk

eto ung link nung thread sa XDA: http://forum.xda-developers.com/showthread.php?t=2265477

Lollipop nga ang pinag-uusapan namin ngayon sir.
1week ko nang gamit yun German Lollipop Firmware,, na-root ko na rin.. na-deodedexed at na-debloat..
May mga screenshots na rin sa mga previous posts.

Katatapos lang 2nd full charge after ng deodex at debloat.
Heto ang estimated na battery consumption.

4days daw in idle mode

View attachment 206281 View attachment 206282

Pero hindi yan ang concern ko, mas okay sana kung sa mismong actual usage.
Okay na sakin ang kayang tumagal ng buong araw na diretso ang gamit.
Lagi kasi connected phone ko sa wifi.

 

[rickytech]

thanks for this guide bro!

 

[greenAngel03]

Sirjay ask po.. kasi kitkat and globe lock phone ko rooted n sya. Ano po uunahin regionlockaway tapos upgrade to lolipop or lolipop muna tapos region lock away? Thanks sir.

 

[jaylence10]

Sirjay ask po.. kasi kitkat and globe lock phone ko rooted n sya. Ano po uunahin regionlockaway tapos upgrade to lolipop or lolipop muna tapos region lock away? Thanks sir.

Wala sa nabanggit... hehehehe..
Hindi gagana ang RegionLockAway sa Kitkat/Lollipop na modem.
Kialangan mo muna magdowngrade ng Modem via Odin... 4.2.2 JB modem yung kailangan.

I9505XXUAME2 4.2.2 Modem: https://mega.co.nz/#!osMxCDTZ!mggOTBqKQ440S8JVsqK5OHedrHNyMp_pXRdryYVwnmU

After mo magdowngrade, gamitin mo na ang RegionLockAway.

Then pag openline na sya, meron kang dalawang options:

Option 1: Ibalik yung original 4.4 Kitkat modem then flash ng Lollipop
Option 2: Directly i-fash yung Lollipop

 

[greenAngel03]

Wala sa nabanggit... hehehehe..
Hindi gagana ang RegionLockAway sa Kitkat/Lollipop na modem.
Kialangan mo muna magdowngrade ng Modem via Odin... 4.2.2 JB modem yung kailangan.

I9505XXUAME2 4.2.2 Modem: https://mega.co.nz/#!osMxCDTZ!mggOTBqKQ440S8JVsqK5OHedrHNyMp_pXRdryYVwnmU

After mo magdowngrade, gamitin mo na ang RegionLockAway.

Then pag openline na sya, meron kang dalawang options:

Option 1: Ibalik yung original 4.4 Kitkat modem then flash ng Lollipop
Option 2: Directly i-fash yung Lollipop

Thanks sir. Yown modem muna para mkpgopenline then direct ko n cguro sa lolipop.. thanks sir sa quick response.. sundan ko nlng yong tut mo sa regionlockaway. Thanks ulit sir.

 

[manghuwan]

<?xml version="1.0" encoding="utf-8"?>
<!-- Copyright (C) 2008 The Android Open Source Project
Copyright (C) 2013 Broadcom Corporation
Licensed under the Apache License, Version 2.0 (the "License");
you may not use this file except in compliance with the License.
You may obtain a copy of the License at

http://www.apache.org/licenses/LICENSE-2.0

Unless required by applicable law or agreed to in writing, software
distributed under the License is distributed on an "AS IS" BASIS,
WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
See the License for the specific language governing permissions and
limitations under the License.
-->

<!-- This file is used to define the mappings between lower-level system
user and group IDs and the higher-level permission names managed
by the platform.

Be VERY careful when editing this file! Mistakes made here can open
big security holes.
-->
<permissions>

<!-- ================================================================== -->
<!-- ================================================================== -->
<!-- ================================================================== -->

<!-- The following tags are associating low-level group IDs with
permission names. By specifying such a mapping, you are saying
that any application process granted the given permission will
also be running with the given group ID attached to its process,
so it can perform any filesystem (read, write, execute) operations
allowed for that group. -->

<permission name="android.permission.BLUETOOTH_ADMIN" >
<group gid="net_bt_admin" />
</permission>

<permission name="android.permission.BLUETOOTH" >
<group gid="net_bt" />
</permission>

<permission name="android.permission.BLUETOOTH_STACK" >
<group gid="net_bt_stack" />
</permission>

<permission name="android.permission.NET_TUNNELING" >
<group gid="vpn" />
</permission>

<permission name="android.permission.SYSTEM_GROUP_INTERNAL" >
<group gid="system" />
</permission>

<permission name="android.permission.INTERNET" >
<group gid="inet" />
</permission>

<permission name="com.sec.android.permission.CAMERA" >
<group gid="camera" />
</permission>

<permission name="android.permission.READ_LOGS" >
<group gid="log" />
</permission>

<permission name="android.permission.READ_EXTERNAL_STORAGE" >
<group gid="sdcard_r" />
<group gid="media_rw" />
</permission>

<permission name="android.permission.WRITE_EXTERNAL_STORAGE" >
<group gid="sdcard_r" />
<group gid="sdcard_rw" />
<group gid="media_rw" />
</permission>

<permission name="android.permission.ACCESS_ALL_EXTERNAL_STORAGE" >
<group gid="sdcard_r" />
<group gid="sdcard_rw" />
<group gid="sdcard_all" />
</permission>

<permission name="com.sec.android.app.sysscope.permission.SYSSCOPE_ACCESS_SYSTEM_INFO" >
<group gid="radio" />
</permission>

<permission name="android.permission.WRITE_MEDIA_STORAGE" >
<group gid="media_rw" />
</permission>

<permission name="android.permission.ACCESS_MTP" >
<group gid="mtp" />
</permission>

<permission name="android.permission.NET_ADMIN" >
<group gid="net_admin" />
</permission>

<!-- The group that /cache belongs to, linked to the permission
set on the applications that can access /cache -->
<permission name="android.permission.ACCESS_CACHE_FILESYSTEM" >
<group gid="cache" />
</permission>

<!-- RW permissions to any system resources owned by group 'diag'.
This is for carrier and manufacture diagnostics tools that must be
installable from the framework. Be careful. -->
<permission name="android.permission.DIAGNOSTIC" >
<group gid="input" />
<group gid="diag" />
</permission>

<!-- Group that can read detailed network usage statistics -->
<permission name="android.permission.READ_NETWORK_USAGE_HISTORY">
<group gid="net_bw_stats" />
</permission>

<!-- Group that can modify how network statistics are accounted -->
<permission name="android.permission.MODIFY_NETWORK_ACCOUNTING">
<group gid="net_bw_acct" />
</permission>

<permission name="android.permission.LOOP_RADIO" >
<group gid="loop_radio" />
</permission>

<!-- The group that releated with VPN -->
<permission name="android.permission.SAMSUNG_MODIFY_ROUTE" >
<group gid="net_admin" />
</permission>

<permission name="android.permission.SAMSUNG_TUNTAP" >
<group gid="vpn" />
</permission>

<permission name="android.permission.SAMSUNG_MODIFY_IPTABLES" >
<group gid="net_raw" />
</permission>

<!-- The group that releated with VPN -->
<permission name="com.sec.android.SAMSUNG_MODIFY_ROUTE" >
<group gid="net_admin" />
</permission>

<permission name="com.sec.android.SAMSUNG_TUNTAP" >
<group gid="vpn" />
</permission>

<permission name="com.sec.android.SAMSUNG_MODIFY_IPTABLES" >
<group gid="net_raw" />
</permission>

<!-- The group that releated with URL -->
<permission name="com.sec.android.SAMSUNG_GET_URL" >
<group gid="secnetfilter" />
</permission>

<!-- Group that can use gscaler -->
<permission name="com.sec.android.permission.USE_GSCALER" >
<group gid="graphics" />
</permission>

<!-- Except for SysScope, DO NOT USE this permission. -->
<permission name="com.sec.android.app.sysscope.permission.ACCESS_SYSTEM_INFO_SYSSCOPE_ONLY" >
<group gid="radio" />
</permission>

<!-- ================================================================== -->
<!-- ================================================================== -->
<!-- ================================================================== -->

<!-- The following tags are assigning high-level permissions to specific
user IDs. These are used to allow specific core system users to
perform the given operations with the higher-level framework. For
example, we give a wide variety of permissions to the shell user
since that is the user the adb shell runs under and developers and
others should have a fairly open environment in which to
interact with the system. -->

<assign-permission name="android.permission.MODIFY_AUDIO_SETTINGS" uid="media" />
<assign-permission name="android.permission.ACCESS_SURFACE_FLINGER" uid="media" />
<assign-permission name="android.permission.WAKE_LOCK" uid="media" />
<assign-permission name="android.permission.UPDATE_DEVICE_STATS" uid="media" />
<assign-permission name="android.permission.UPDATE_APP_OPS_STATS" uid="media" />

<assign-permission name="android.permission.ACCESS_SURFACE_FLINGER" uid="graphics" />

<!-- This is a list of all the libraries available for application
code to link against. -->

<library name="android.test.runner"
file="/system/framework/android.test.runner.jar" />
<library name="javax.obex"
file="/system/framework/javax.obex.jar"/>
<!--
<library name="javax.btobex"
file="/system/framework/javax.btobex.jar"/>
-->
</permissions>

Yan na o yung permissions ko. Pano po gamitin yung advance apktool?

 

[jaylence10]

Okay naman yung permissions.. ayaw pa rin ba?

Di pa ako nakakagamit ng apktool na automatic yung pag decompile/compile.
Manual yung gamit ko.

 

[manghuwan]

Okay naman yung permissions.. ayaw pa rin ba?

Di pa ako nakakagamit ng apktool na automatic yung pag decompile/compile.
Manual yung gamit ko.

Ayaw pa rin sir. Haha, Patut naman po yung manual way niyo.

 

[jaylence10]

Ayaw pa rin sir. Haha, Patut naman po yung manual way niyo.

Okay sir.. wait.. lipat ako sa laptop