Related
I am trying to make a minor change to my services.jar and so far have no been successful.
I deodexed the file with xultimate2.3.3 , extracted the classes.dex with 7zip 9.2, I used apktool 1.4.3 to "expand" the contents, made the change, repacked the dex file and put it back into services.jar and the phone cannot compelete boot. I made sure to change the permissions, owner a group to match the previous file.
I then tried using Xultimate to deodex the file and put it back on the phone and this also keeps it from booting.
I then tried using the already deodexed file from another rom (2.2.1 vs 2.2.2) and it had the same issue.
So far I have to reflash my phone with Odin every time and I am getting tired of making the same mistake over and over.
edit: Maybe I should ask - what is the appropraite way to move the file over? I am doing it by going into root explorer, deleting /system/framework/services.jar+services.odex, using adb push to put the file on the sdcard, using root explorer to move it from sdcard to /system/framework then changing the permissions in root explorer to match the previous file before finally running "chown root.root /system/framework/services.jar" from adb shell
Either my method for copying the file is bad or xultimate 2.3.3 is messing up the deodex. Any advice on another tool to use to deodex this file?
You should be using baksmali/smali to decompile/recompile classes.dex, not apktool :/
Apktool can decompile .jars too
I use it and works fine
@OP
After deodexing decompile the jar using Virtuous Ten Studio by Diamondback(Google it)
Burned from my laser torch using pencil cells
Thank you for the replies. I will try these suggestions.
As a side note I also tried to use Xultimate to deodex the file, then ran dexopt-wrapper on the output to reodex the unchanged file and the phone is stuck in a boot loop.
You can read about re-odexing files here http://themikmik.com/showthread.php...w-About-adb-odex-themes-etc&p=75225#post75225
Can you give suggestions on another tool to de-odex the services.jar file? I think xultimate is the problem. It is the only common denominator.
I forgot to add that the original services.odex is a different size and has different contents from the new services.odex created by xultimate+dexopt-wrapper
I didn't expect it to work but I took the modified/deodex services.jar from a 2.2.1 rom and put it into my 2.2.2 rom and it had the same non boot issue.
The newest version of xUltimate i could find.
Enjoy
http://www.xeudoxus.com/android/xUltimate-v2.4.2.zip
Normally to decompile my dex files I use smali and baksmali, how can I re-odex them?
Id like to get my service.jar re-odexed so I can try and push it to my phone via a zip update.
Sent from my MB865 using xda premium
[mini HOW-TO] Re-Odex (or create a new .odex file)
Fall of Enosis said:
Normally to decompile my dex files I use smali and baksmali, how can I re-odex them?
Id like to get my service.jar re-odexed so I can try and push it to my phone via a zip update.
Sent from my MB865 using xda premium
Click to expand...
Click to collapse
It all needs to be done on your phone, live.. with adb.
Here's how I accomplished it - I will use the services.jar in this example. Just change the file name and path to existing .odex accordingly for other files (not sure if all steps are required exactly, but it has worked for me multiple times with different jars and SysUI apk):
Requirements:
Odexed system
adb
dexopt-wrapper
Put this dexopt-wrapper file (unzip first) in /system/bin with 775 permissions:
X X X
X....X
X....X
Probably a good idea to reboot after pushing that file, if you use root explorer (like I did).
Put the deodexed services.jar (or other jar/apk file you want to make an new odex of) on your sd card.
Go to /system folder (with root explorer or equal) and mount it R/W (not sure if this is necessary - but won't hurt)
Put your USB connection to "Charge only" mode.
Go here (big props and credit to jhotmann for this) and follow steps 8-12 (I've recreated the steps with the A2's bootclasspath below).
The bootclass path is located in the /init.rc file at the root of your phone.
Connect with adb (do a adb devices check to make sure you're all good).
To create the new odex:
Code:
adb shell
su
cd /sdcard/
dexopt-wrapper services.jar new.odex /system/framework/core.jar:/system/framework/bouncycastle.jar:/system/framework/ext.jar:/system/framework/framework.jar:/system/framework/android.policy.jar:/system/framework/services.jar:/system/framework/core-junit.jar:/system/framework/com.motorola.android.frameworks.jar:/system/framework/com.motorola.android.widget.jar
I know it's a long entry for those who don't work with command lines often (like me), but double check your entry before hitting enter.
To copy the signature from the existing odex (change path to /system/app/.. if necessary):
Code:
busybox dd if=/system/framework/services.odex of=new.odex bs=1 count=20 skip=52 seek=52 conv=notrunc
Done! Rename new.odex (created on your /sdcard) to services.odex since that is your new signed odex file...
You can then get that on your odexed system by your choice of method (adb push, update.zip, root explorer push, etc.. - note: please know what you are doing before trying to push files with root explorer! - you cannot simply copy and paste!)
Or, if you want to deodex it right away again for some odd reason like I did (personal issues )... Take the services.jar and the new services.odex from your sdcard and put them on your computer - and open the services.jar with 7-zip (maybe winzip) and delete the classes.dex file from the 7-zip window. Now you have a fresh new set of .jar/.odex files ready for deodexing (I did this all with the SystemUI.apk last night, that's why I elaborated and re-typed this whole thing today..).
Frigging brilliant man.
Much appreciated. I'm super sick and my USB cable is at work.
Once i get it back on Wednesday, I'll work all this out. If I could thank you twice I would.
Thanks man!
Sent from my MB865 using xda premium
Fall of Enosis said:
Frigging brilliant man.
Much appreciated. I'm super sick and my USB cable is at work.
Once i get it back on Wednesday, I'll work all this out. If I could thank you twice I would.
Thanks man!
Sent from my MB865 using xda premium
Click to expand...
Click to collapse
Not a prob.
And, I updated the dexopt-wrapper link so it's easier to download - just unzip it first..
Good luck on your quest.. let me know if you catch any snags along the way - and i'll try and help you out.
Sent from my mind using XDA
Ok sooo, I think we (or most likely me) are confused on what I wanted to do. I don't want to make a NEW odex file. I need to recombine my modded classes.dex BACK with the service.jar.
Since I needed to modify some script in the services.jar I had to de-odex it so I had a classes.dex file to use baksmali with so I could modify it. Once I modded it I used smali to create the NEW MODDED classes.dex. And now I need to re-odex(bad terminology?) them to re-combine the services.jar with the classes.dex so the modded services.jar could be used on a odexed ROM.
I'm working on a de-odexed version also, but I'd like to be able to offer both
Fall of Enosis said:
Ok sooo, I think we (or most likely me) are confused on what I wanted to do. I don't want to make a NEW odex file. I need to recombine my modded classes.dex BACK with the service.jar.
Since I needed to modify some script in the services.jar I had to de-odex it so I had a classes.dex file to use baksmali with so I could modify it. Once I modded it I used smali to create the NEW MODDED classes.dex. And now I need to re-odex(bad terminology?) them to re-combine the services.jar with the classes.dex so the modded services.jar could be used on a odexed ROM.
I'm working on a de-odexed version also, but I'd like to be able to offer both
Click to expand...
Click to collapse
So, you have a deodexed services.jar (with an unedited classes.dex inside)? And, you also have an edited classes.dex (the new modded one). Just drag and drop the new modded classes.dex into the services.jar file with 7-zip to overwrite the old one.
Then I would check out the mods on a deodexed system, and provided they work, then go through the re-odexing process (separating that classes.dex from the apk and creating a new odex file) as described above to get it working on odexed systems.
Hope that helps.. Good luck!
Yes sir, you are correct. That was the first thing I tried to do was just drag and drop the modded classes.dex with 7zip, save it, however when i tried to flash the "modded" ROM it can't install the system folder because (according to Jim), when I modded copied the new classes.dex, I changed the size, and so the signature needed to be changed as well. They mismatched.
Fall of Enosis said:
Yes sir, you are correct. That was the first thing I tried to do was just drag and drop the modded classes.dex with 7zip, save it, however when i tried to flash the "modded" ROM it can't install the system folder because (according to Jim), when I modded copied the new classes.dex, I changed the size, and so the signature needed to be changed as well. They mismatched.
Click to expand...
Click to collapse
Not sure about the details of that.. I know the signatures can be tricky, but I've modded a few apks/jars similarly with no problems... when you say "can't install.." is that it wouldn't flash in recovery, or you bootlooped?
Just wouldn't flash at all.
And thanks for all your help man.
Sent from my MB865 using xda premium
I've updated the 2nd post with more detail on creating a new odex file...
Not to be a "rooster" (replace with your word of choice) or anything, but maybe this info has a place somewhere besides the general threads..?:angel: (and what is up with these new Smilies and posting reply layout?) - it just seems so hard to come by good literature on this process (which, I suppose, is a process so rarely needed though...)
So I need to perform the processes above while running in an odexed environment correct? Does this process change the deodexed APK we are running the script on to an odexed one as well as create a new .odex file for that APK? I am just confused about what the result is after running the script. For my situation I want to take 2 deodexed files (systemui and sec settings.apk) and odex them. Then push them into an odexed rom. Once I run the script above what am I left with?
Didact74 said:
So I need to perform the processes above while running in an odexed environment correct?
YES.
Does this process change the deodexed APK we are running the script on to an odexed one as well as create a new .odex file for that APK?
(Yes, it will create a new odex file that you will need to rename, but..)NO. You will need to take the classes.dex out of the deodexed apk/jar - use something like 7-zip. Unless you only edited smali, then you really only need the new odex file.
I am just confused about what the result is after running the script. For my situation I want to take 2 deodexed files (systemui and sec settings.apk) and odex them. Then push them into an odexed rom. Once I run the script above what am I left with?
Click to expand...
Click to collapse
I broke up your quote with my best answers...
As for what your're left with is a new.odex file, properly signed, if all goes well. You are going to need to do it for each of your deodexed files.
Rename them, remove the classes.dex from the deodexed files you used, and get them on your phone however you choose (I prefer zip packages and a restore.zip in case something goes wrong).
Also note that the bootclass path is different from GB to ICS.. and among different devices of course. Check init.rc file if need be. I posted the one to use for A2 ICS (think it may be the same for razr too) here: http://forum.xda-developers.com/showthread.php?t=1753659
I can't garuntee you won't have problems, but good luck... if you do you could try the dexopt-wrapper from here: http://forum.xda-developers.com/showthread.php?t=1645950 - just unzip it first obviously (but I think it's the exact same file though..)
Btw, it's all done with adb, one line at a time.. not really a script, but thank you for the idea - maybe a batch file?
Sent from my phone's mind
Great, thank you for the detailed response. Last question.
What if I have the original SystenUI.odex and SecSettings.odex files that used to be attributed to them before i deodexed them? Can I simply reuse those without having to run through the adb process?
Thanks,
Didact74 said:
Great, thank you for the detailed response. Last question.
What if I have the original SystenUI.odex and SecSettings.odex files that used to be attributed to them before i deodexed them? Can I simply reuse those without having to run through the adb process?
Thanks,
Click to expand...
Click to collapse
But, you deodexed them to edit the smali files in the classes.dex right? So, no, you will need to use the new odex files that are created from the modded deodexed files you used..
If you never edited any of the smali files, then you didn't need to deodex in the first place... you only need to deodex in order to mod the smali files - everything else in the apk can be modded as is on odexed systems.
Sent from my phone's mind
Thank you very much. Can you repost the wrapper file? Its not downloading correctly.
Didact74 said:
Thank you very much. Can you repost the wrapper file? Its not downloading correctly.
Click to expand...
Click to collapse
Updated the link in Post #2 with a zip file - you need to unzip it first then move it.
Thank you.
So I am getting an error trying to re-odex. See the attached image of the error.
Weird thing is that even though I get an error it still creates the new.odex file. I triedto go through the entire process even though I was getting errors and it just got stuck on the boot screen and never loaded. Anything in my error attached raise any flags?
Thanks,
Didact74 said:
Thank you.
So I am getting an error trying to re-odex. See the attached image of the error.
Weird thing is that even though I get an error it still creates the new.odex file. I triedto go through the entire process even though I was getting errors and it just got stuck on the boot screen and never loaded. Anything in my error attached raise any flags?
Thanks,
Click to expand...
Click to collapse
Hmmm... First thing I can think of is: are all of those framework files in the bootclass path that you used actually in your /framework folder? With our A2, in ICS there are a few extra .jar files listed that were not actually on our phone, so I had to remove those from the path...
I will try to make a new odex myself and make sure that's not a standard error message... @Fall of Enosis, you recall what it spits out?
EDIT: Shoot - forgot I'm deodexed right now... will attempt later or hear back from Fall by then..
alteredlikeness said:
Hmmm... First thing I can think of is: are all of those framework files in the bootclass path that you used actually in your /framework folder? With our A2, in ICS there are a few extra .jar files listed that were not actually on our phone, so I had to remove those from the path...
I will try to make a new odex myself and make sure that's not a standard error message... @Fall of Enosis, you recall what it spits out?
EDIT: Shoot - forgot I'm deodexed right now... will attempt later or hear back from Fall by then..
Click to expand...
Click to collapse
Yes, all .jar files listed in my bootclass were located in the framework directory.
Nevermind...my mistake. I had an issue with my files not being deodexed correctly from the start. I went back and deodexed, made the edits to res and smali then odexed using the method above again and all went well!
Thanks!
can anyone tell me how to change SystemUI.apk or framework-res.apk files and replace to the system correctly?.. coz when i try to change and replace them it doesnt work for me it keep saying SystemUI.apk unfortunately stopped working and freeze the status bar. it disappear when i replace a modified apks.. why is that? please help...
amjiffy70 said:
can anyone tell me how to change SystemUI.apk or framework-res.apk files and replace to the system correctly?.. coz when i try to change and replace them it doesnt work for me it keep saying SystemUI.apk unfortunately stopped working and freeze the status bar. it disappear when i replace a modified apks.. why is that? please help...
Click to expand...
Click to collapse
Because system UI is always in use...and is a major part of the phones layout
You should be able to replace it worn a root explorer and then reboot and be fine though...
If that didn't work then boot into recovery and adb push it...havebt done that in awhile but if my memory is correct the command is "adb push /system/app/SystemUI.apk" -without quotes of course then wipe cache and dalvic cache (don't wipe data tho) and reboot.
Sent from my HTC Holiday using Tapatalk 2
Or....
Download this http://goo.im/devs/Th3Bill/Infuse_4G/Blank_cwm_Infuse.zip (its a blank cwn flashable package...just add the files)
With 7zip open the zip (right click>open archive...don't extract)
Navigate to /system/app of the archive
Copy modded systemui to that location
Delete the file that was already in there (I think it says to delete after placing file in there)
Copy the zip to your phone
Flash it
Credit goes to th3bill for that blank cwm flashable package
Sent from my HTC Holiday using Tapatalk 2
So here I have noticed issue with using vrtheme on new 4.3 MJ2 and seeking some Linux expert help to solve it.
work around
Simply using vrtheme causing FCs, SO i have changes the destination to see outcome file structure.
-All changes we have applied through vrtheme applied to output file. but icons get changed to android icon.
-Now if you move that output file to other destination using root explorer then also it regenerates original icons and we can use as final apk ready to push to System/app
-Again if we giving same command through recovery, it doesn't works
-Also copying with terminal emulator with cat command, it regenerates original structure. again same command using recovery fails to do it.
May be recovery issue??
here is log cat along with used vrtheme script.
dr.ketan said:
So here I have noticed issue with using vrtheme on new 4.3 MJ2 and seeking some Linux expert help to solve it.
work around
Simply using vrtheme causing FCs, SO i have changes the destination to see outcome file structure.
-All changes we have applied through vrtheme applied to output file. but icons get changed to android icon.
-Now if you move that output file to other destination using root explorer then also it regenerates original icons and we can use as final apk ready to push to System/app
-Again if we giving same command through recovery, it doesn't works
-Also copying with terminal emulator with cat command, it regenerates original structure. again same command using recovery fails to do it.
May be recovery issue??
Click to expand...
Click to collapse
doc, am not a linux expert, but i tried to inject your black aosp vrtheme files into the apk and flash them from cwm, it kills the wifi and have to wipe and reflash the whole rom. so, perhaps you want to put more attention to it.
waiting for your aosp theme and thanks a lot.
Wifi issue will be solved by reflashing recovery
I can show you temporary solution.
Just change path of pushing files to other from System/app then 1. you want get FCc bcoz it is not in system/app
2. Now from where you have defined destination from there move to some pther place with root explorer, now you will be able to see icons, once icons are correct you can pust to system/app.
dr.ketan said:
Wifi issue will be solved by reflashing recovery
I can show you temporary solution.
Just change path of pushing files to other from System/app then 1. you want get FCc bcoz it is not in system/app
2. Now from where you have defined destination from there move to some pther place with root explorer, now you will be able to see icons, once icons are correct you can pust to system/app.
Click to expand...
Click to collapse
sorry doc, but i cannot understand what you mean.
do you mean i should change the flashing path (in the script)? or do you mean i should copy the apks manually into the system/app by root explorer? if you mean the later, i can do, but the first one i don't.
i can see all the icons, just the wifi would not start after i flashed the modified apks through cwm flash. what do you mean by reflashing recovery?
Ok making clear again who want to use vrtheme
1.Change path in vrtheme installertheme.sh from system/app to other (e.g. just system)
2.Now when you flash vrtheme, you won't see any changes in system bcoz all apps will be in system and not in System/app.
3. Manually cut all app with root explorer from system to SDcard
4. Now you can see correct icons of all appl after moving to sdcard.
5.Now move those apk to system/app OR System/framework, where it should be.
6.Enjoy all the changes now in system
7.By this process you will lose wifi and you have to reflash recovery to get it back.
PS : For AOSP for MJ2 I have made it with same method above and uploading, Once uploaded will post to MJ2 thread, you have to simply flash that file. without doing anything above.
dr.ketan said:
Ok making clear again who want to use vrtheme
1.Change path in vrtheme installertheme.sh from system/app to other (e.g. just system)
2.Now when you flash vrtheme, you won't see any changes in system bcoz all apps will be in system and not in System/app.
3. Manually cut all app with root explorer from system to SDcard
4. Now you can see correct icons of all appl after moving to sdcard.
5.Now move those apk to system/app OR System/framework, where it should be.
6.Enjoy all the changes now in system
7.By this process you will lose wifi and you have to reflash recovery to get it back.
PS : For AOSP for MJ2 I have made it with same method above and uploading, Once uploaded will post to MJ2 thread, you have to simply flash that file. without doing anything above.
Click to expand...
Click to collapse
will just wait for your file then. dont want to mess my setup again. spent too much time experimenting with it today. lucky it's saturday in my country...
ok then wait 10 min.
EDIT : AOSP theme for MJ2 ROM Posted to MJ2 thread post#2
Doc.
I just came across thia issue thread discussion.
Surprised to see vrtheme issues.
I think it is worth trying morphing instead of vrtheme.
If it fails, then it is not a recovery issue..m
It might be android 4.3 security files that I noticed in /system...
I will dig in further and check...
Thx for sharing this discussion thread. :thumbup:
wesamothman said:
Doc.
I just came across thia issue thread discussion.
Surprised to see vrtheme issues.
I think it is worth trying morphing instead of vrtheme.
If it fails, then it is not a recovery issue..m
It might be android 4.3 security files that I noticed in /system...
I will dig in further and check...
Thx for sharing this discussion thread. :thumbup:
Click to expand...
Click to collapse
Already fixed that (at least in my MJ2 rom)
vrtheme works perfect on framework-res.apk and secsettings.apk
Devs,
I modified the framework-res.apk file from NJ4 to remove the <item> lines out of the arrays.xml file:
Code:
<string-array name="config_mobile_hotspot_provision_app">
<item>com.sec.tetheringprovision</item>
<item>com.sec.tetheringprovision.TetheringProvisionActivity</item>
</string-array>
I have it working on my phone and native hotspot is working. I couldn't find any further information if anything more was needed to "not be detected" by the network as tethering.
If this is indeed, all that needs to be done, then someone may want to make it an SafeStrap install zip. I'm not sure how to do that.
You can manually add this fix, but will have to follow these instructions to the T, as not doing so will get you in a boot loop. I am not responsible for anything that happens to your phone, and doing anything with this modified file is at your own risk... I use Root Browser as my file manager to make these changes..
THIS ZIP FILE IS NOT FLASHABLE - IT'S MERELY IN ZIP SO IT COULD BE UPLOADED TO XDA..
1) Download zip file and extract it to your computer
2) Move the extracted framework-res.apk file to your SDCard
3) Now, move the file from your SDCard to /system/ (Temporarily).
4) Make a backup copy of the /system/framework/framework-res.apk file to your SDCard in another folder for backup purposes.
5) Change the permissions on the framework-res.apk file that you just copied to /system to 0644
6) Move the framework-res.apk file from /system to the /system/framework folder
7) Overwrite the original framework-res.apk file
8) Reboot your phone
9) Voila, native hotspot is active.
[EDIT TO REMOVE OLD FILE - SEE POSTS BELOW]
Thank you this worked for me
Thank you, rodin95, your steps worked for me on rooted stock NJ4. I installed apk following your steps, changing permissions, etc. Hotspot seem to work fine.
Additional information for those contemplating the same steps:
0644 means: Owner: read,write; Group:read,Other:read.
I used ES File Explorer app.
Before performing the steps: In ES File Explorer, choose "Root Explorer" , then choose "Mount R/W" and then chose "RW" for /system partition, otherwise moving the apk into /system/framework will not work.
Please note that removing the original apk from /system/framework seem to quickly render your phone unusable. So please follow instructions of the original post precisely . Good luck!
Thanks
oiakou said:
Thank you, rodin95, your steps worked for me on rooted stock NJ4. I installed apk following your steps, changing permissions, etc. Hotspot seem to work fine.
Additional information for those contemplating the same steps:
0644 means: Owner: read,write; Group:read,Other:read.
I used ES File Explorer app.
Before performing the steps: In ES File Explorer, choose "Root Explorer" , then choose "Mount R/W" and then chose "RW" for /system partition, otherwise moving the apk into /system/framework will not work.
Please note that removing the original apk from /system/framework seem to quickly render your phone unusable. So please follow instructions of the original post precisely . Good luck!
Click to expand...
Click to collapse
Thank you , i really don't know why he didn't mention that information because it's very important. It really works !
Thanks dude, working on my stock NJ4 rooted i337
Got it going but as mention mine frozen after over writing framework apk, phone rebooted but was in a bootloop. Pulled battery 2 times and still bootloop. So I pulled battery and went into Safestrap recovery/ advanced/ file manger and copied modified framework-res.apk again, over writing, rebooted with no problems and tethering works great. Just a thought and haven't tried it but I remember doing this another time and the instructions were to rename the stock framework app and then copy modified to framework folder? Wonder if this would stop device from freezing up????? Just a thought. Thanks
rodin95 said:
Devs,
I modified the framework-res.apk file from NJ4 to remove the <item> lines out of the arrays.xml file:
Code:
<string-array name="config_mobile_hotspot_provision_app">
<item>com.sec.tetheringprovision</item>
<item>com.sec.tetheringprovision.TetheringProvisionActivity</item>
</string-array>
I have it working on my phone and native hotspot is working. I couldn't find any further information if anything more was needed to "not be detected" by the network as tethering.
If this is indeed, all that needs to be done, then someone may want to make it an SafeStrap install zip. I'm not sure how to do that.
Click to expand...
Click to collapse
Glad to see new blood stepping up and contributing. Good work! Feel free to take one of these zip files, rename it for the new firmware, toss in your apk, and make it ss flashable. Again thanks for stepping up!: http://forum.xda-developers.com/showthread.php?t=2787681
muniz_ri said:
Glad to see new blood stepping up and contributing. Good work! Feel free to take one of these zip files, rename it for the new firmware, toss in your apk, and make it ss flashable. Again thanks for stepping up!: http://forum.xda-developers.com/showthread.php?t=2787681
Click to expand...
Click to collapse
Thank you for the steps you posted Muniz to repack it with Rodin_25 apk.
Flashed with SS from the instructions from original http://forum.xda-developers.com/showthread.php?t=2787681
Thank you Rodin_25 for the apk!
NJ4 SafeStrap Flashable file (thanks @muniz_ri)
lordnihilusmd said:
Thank you , i really don't know why he didn't mention that information because it's very important. It really works !
Click to expand...
Click to collapse
I didn't mention that because I mentioned that I use Root Browser in the posting, and it didn't require the steps you guys mentioned.
NP to all of you! Glad I was able to assist with this
I'd like to learn - how did you modify the framework-res.apk file?
I've extracted the file framework-res.apk, but don't see a file called "arrays.xml". I assume it's contained in the resources.arsc file. How did you extract it from the resources file and then repackage it after you modified the xml?
I've unsuccessfully Googled. Is there a tutorial you can link me to?
Thanks!
install
Excuse the noob here but if I understand correctly I need to root my phone, install SafeStrap, download & run the zip file for SafeStrap & I should be able to use my WiFi hotspot?
Worked Perfectly!
Thank you for posting this fix! It worked perfectly on my SGH-i337 running rooted NJ4.
Flash_Fire said:
Thank you for posting this fix! It worked perfectly on my SGH-i337 running rooted NJ4.
Click to expand...
Click to collapse
Stock rom only? I'm on Super Nexus Safestrap and I'm wanting my tethering to work again.
Thanks Rodin95. Your instructions and file worked perfectly.
So I just ran through the step listed above, word for word including mounting SYSTEM as RW. As soon as I asked ES File to copy the file from /system to /system/framework the phone rebooted itself and is now stuck at the AT&T splash screen with the globe in the middle of the screen.
Any ideas? Or am I going to have to Re-ODIN everything back and start over...
I am/was running on stock-rooted but WITHOUT SS...
Thanks for this.
Since I'm using my i337 on T-Mobile I absolutely need this fix to use tethering at all (OC3 has issues with Bluetooth AVRCP that makes it a deal-breaker for me).
I used the SafeStrap update.zip with FlashFire instead and it worked perfectly.
Just installed the SS update file. Worked great. So happy to finally have this. Running on stock, rooted, ROM.
MrPeeta said:
Thank you for the steps you posted Muniz to repack it with Rodin_25 apk.
Flashed with SS from the instructions from original http://forum.xda-developers.com/showthread.php?t=2787681
Thank you Rodin_25 for the apk!
Click to expand...
Click to collapse
rodin95 said:
NJ4 SafeStrap Flashable file (thanks @muniz_ri)
Click to expand...
Click to collapse
I know it's thier own fault for not reading a few lines down into post 3 and all but you should really update the OP so people don't get stuck in bootloader like they are still... this is orking perfect for 4.4.4 nj4 and the first quote is for 4.2 and 4.3 which all work if done the way explained above... I know it's real hard to follow instruction if you don't read more than 5 lines lol
Is there a version of this that works for 5.0.1?