tl;dr: I tried to hack the SystemUI.apk file to get rid of the s-finder notification bar, I needed to deodex the apk to do this. I did that (first time ever), but then I didn't know what to do with the .odex.art.xz file, so I removed the whole arm/ folder from the SystemUI directory, and just left my modified SystemUI.apk file in there. After clearing the cache and dalvik, the SystemUI app kept crashing and I had to restore from backup. What do I do with the arm directory, and is that even the problem, or should I not even try to do this?
I have a sprint Galaxy S4 (jfltespr; SPH-L720) that I just upgraded to lollipop via the regular system update, now have Android 5.0.1, baseband L720VPUGOD2, kernel 3.4.0. My phone is rooted with BusyBox installed. I used to use CyanogenMod (for a long time), but the stability was low for me, particularly when travelling internationally and changing SIMs: I would frequently lose GPS completely (see http://forum.xda-developers.com/galaxy-s4-sprint/help/gps-cyanogen-mod-install-t3009245/), requiring me to flash the stock ROM again. So I reverted to stock, and used xposed. Unfortunately, following the upgrade to 5.0.1, xposed now requires flashing a zip and is in super-alpha, and so I am nervous about using it. The only thing I really want a custom ROM or xposed for is to get rid of bloat. I have managed with just Titanium to get rid of the most annoying apps, but I am still stuck with that stupid 'S-Finder'/'Quick Connect' bar. I can get rid of it by switching my device name to jfltevzr or jflteatt in build.prop, but then I lose other features, such as the ability to change to the GSM network.
So, I tried to hack the SystemUI apk according to the instructions here and here. Essentially my plan was: download SystemUI.apk, edit the PhoneStarusBar.smali, and profit.
I have never done this before, so I rapidly ran into the issue that I needed to deodex the apk. I followed this guide and everything seemed to go smoothly, except that the PhoneStatuBar.smali file had different code from the tutorial. In the tutorial I had to change
Code:
if-nez v8, ;cond_0
to
Code:
if-nex v8, :cond_5
but in my file it seemed that the syntax was similar, but the labels were different, so I ended up changing
Code:
if-nez v8, ;cond_15
to
Code:
if-nex v8, :cond_c0
I created the classes.dex file and packaged it into the apk with the command
Code:
7za u -tzip SemcVideo.apk classes.dex
However, I was confused about what to do with the new apk. In my system, the original apk lives in /system/priv-app/SystemUI/SystemUI.apk, and next to the apk is an arm directory with an odex.xz file (which I deodexed) and an art.odex.xz file that I have no idea what to do with. Since I didn't know what to do, I just deleted the whole arm directory, put the modified (deodexed) SystemUI.apk file in /system/priv-app/SystemUI/, cleared the cache and dalvik cache, and rebooted. After about 20 minutes of rebuilding the cache for all of my apps, the phone started, but it had the dreaded 'SystemUI is not responding, do you want to restart it' message. I ended up having to restore a backup and wipe the cache again.
So, my question is: what do I do with that arm directory? Is that what broke it, or is the problem that I just screwed up the PhoneStatusBar.smali file? I don't really know what I am doing as I don't know java that well, but I would like to get this to work.
Alternatively, do you guys think that maybe the Google Play Edition ROM might be more stable that CyanogenMod, or that I should just try to flash to xposed alpha even though it is so 'unstable'? It looks to me like the GPE ROM might be more stable than CM, but I have no idea. I know that it hasn't been patched for StageFright yet, even though CM has.
Finally, I should specify that I am not an Android hacker, I have a full time job in science research and I volunteer a lot. My top priority for my phone is stability and reliability, and I don't want to spend too many hours on this. Secondary concerns for me are not having to deal with all of Samsung's bloatware and increasing my battery life.
Thanks in advance for all of your help, and apologies if I am posting in the wrong place.
MikeDacre said:
tl;dr: I tried to hack the SystemUI.apk file to get rid of the s-finder notification bar, I needed to deodex the apk to do this. I did that (first time ever), but then I didn't know what to do with the .odex.art.xz file, so I removed the whole arm/ folder from the SystemUI directory, and just left my modified SystemUI.apk file in there. After clearing the cache and dalvik, the SystemUI app kept crashing and I had to restore from backup. What do I do with the arm directory, and is that even the problem, or should I not even try to do this?
I have a sprint Galaxy S4 (jfltespr; SPH-L720) that I just upgraded to lollipop via the regular system update, now have Android 5.0.1, baseband L720VPUGOD2, kernel 3.4.0. My phone is rooted with BusyBox installed. I used to use CyanogenMod (for a long time), but the stability was low for me, particularly when travelling internationally and changing SIMs: I would frequently lose GPS completely (see http://forum.xda-developers.com/galaxy-s4-sprint/help/gps-cyanogen-mod-install-t3009245/), requiring me to flash the stock ROM again. So I reverted to stock, and used xposed. Unfortunately, following the upgrade to 5.0.1, xposed now requires flashing a zip and is in super-alpha, and so I am nervous about using it. The only thing I really want a custom ROM or xposed for is to get rid of bloat. I have managed with just Titanium to get rid of the most annoying apps, but I am still stuck with that stupid 'S-Finder'/'Quick Connect' bar. I can get rid of it by switching my device name to jfltevzr or jflteatt in build.prop, but then I lose other features, such as the ability to change to the GSM network.
So, I tried to hack the SystemUI apk according to the instructions here and here. Essentially my plan was: download SystemUI.apk, edit the PhoneStarusBar.smali, and profit.
I have never done this before, so I rapidly ran into the issue that I needed to deodex the apk. I followed this guide and everything seemed to go smoothly, except that the PhoneStatuBar.smali file had different code from the tutorial. In the tutorial I had to change
Code:
if-nez v8, ;cond_0
to
Code:
if-nex v8, :cond_5
but in my file it seemed that the syntax was similar, but the labels were different, so I ended up changing
Code:
if-nez v8, ;cond_15
to
Code:
if-nex v8, :cond_c0
I created the classes.dex file and packaged it into the apk with the command
Code:
7za u -tzip SemcVideo.apk classes.dex
However, I was confused about what to do with the new apk. In my system, the original apk lives in /system/priv-app/SystemUI/SystemUI.apk, and next to the apk is an arm directory with an odex.xz file (which I deodexed) and an art.odex.xz file that I have no idea what to do with. Since I didn't know what to do, I just deleted the whole arm directory, put the modified (deodexed) SystemUI.apk file in /system/priv-app/SystemUI/, cleared the cache and dalvik cache, and rebooted. After about 20 minutes of rebuilding the cache for all of my apps, the phone started, but it had the dreaded 'SystemUI is not responding, do you want to restart it' message. I ended up having to restore a backup and wipe the cache again.
So, my question is: what do I do with that arm directory? Is that what broke it, or is the problem that I just screwed up the PhoneStatusBar.smali file? I don't really know what I am doing as I don't know java that well, but I would like to get this to work.
Alternatively, do you guys think that maybe the Google Play Edition ROM might be more stable that CyanogenMod, or that I should just try to flash to xposed alpha even though it is so 'unstable'? It looks to me like the GPE ROM might be more stable than CM, but I have no idea. I know that it hasn't been patched for StageFright yet, even though CM has.
Finally, I should specify that I am not an Android hacker, I have a full time job in science research and I volunteer a lot. My top priority for my phone is stability and reliability, and I don't want to spend too many hours on this. Secondary concerns for me are not having to deal with all of Samsung's bloatware and increasing my battery life.
Thanks in advance for all of your help, and apologies if I am posting in the wrong place.
Click to expand...
Click to collapse
Just go into res/values/dimens.xml once you have it decompiled and change every line with SFinder or QuickConnect to "0.0dip" using Notepad++ then recompile the apk and remove the SF and QC apks... It's a lot easier that way. Xposed works fine but you have to use the Samsung specific one. There is a link in my Wicked X thread.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
bilgerryan said:
Just go into res/values/dimens.xml once you have it decompiled and change every line with SFinder or QuickConnect to "0.0dip" using Notepad++ then recompile the apk and remove the SF and QC apks... It's a lot easier that way. Xposed works fine but you have to use the Samsung specific one. There is a link in my Wicked X thread.
Click to expand...
Click to collapse
Thanks so much bilgerryan, I am doing that now. I have another dumb question: what is the best way to copy back the new apk? Is it fine for me to use adb to do it from the recovery? I would just delete the original (after backing up) and then copy my modified version in.
Also, (sorry for the multi-post), do I need to wipe both the Cache and the Dalvik Cache partitions after making the switch?
MikeDacre said:
Thanks so much bilgerryan, I am doing that now. I have another dumb question: what is the best way to copy back the new apk? Is it fine for me to use adb to do it from the recovery? I would just delete the original (after backing up) and then copy my modified version in.
Click to expand...
Click to collapse
You have to set permissions to 0644 after you copy it over.. I use root browser. Long press on the file, press Permissions and then make it look like the screenshot. Or you can just use my ROM (second screenshot), it is already removed plus a bunch of other fun stuff... Wicked X v10.6 in Android Development section.
bilgerryan said:
You have to set permissions to 0644 after you copy it over.. I use root browser. Long press on the file, press Permissions and then make it look like the screenshot. Or you can just use my ROM (second screenshot), it is already removed plus a bunch of other fun stuff... Wicked X v10.6 in Android Development section.
Click to expand...
Click to collapse
Great, thanks. I will give your ROM a try in the future, but right now I want to figure out how to do this I just tried it copying back my modified apk and wiping the cache and dalvik, but after it booted, there was no systemui
I just changed the permissions to 644 now, they were 777 before, so that may have been the problem.
Do I need to wipe the cache and dalvik every time? It takes a really long time to boot after that.
Thanks again!
MikeDacre said:
Great, thanks. I will give your ROM a try in the future, but right now I want to figure out how to do this I just tried it copying back my modified apk and wiping the cache and dalvik, but after it booted, there was no systemui
I just changed the permissions to 644 now, they were 777 before, so that may have been the problem.
Do I need to wipe the cache and dalvik every time? It takes a really long time to boot after that.
Thanks again!
Click to expand...
Click to collapse
No, you only need to do that when completely removing a system app. A record is enough. I haven't worked with odex in a long time, I can't remember if there is anything extra you need to do.
bilgerryan said:
No, you only need to do that when completely removing a system app. A record is enough. I haven't worked with odex in a long time, I can't remember if there is anything extra you need to do.
Click to expand...
Click to collapse
OK, unfortunately after making the changes, there is no SystemUI; all I have is my launcher (SmartLauncher) with a black background and no notification bar. After restarting I have the same issue. By putting back the old SystemUI.apk I fix the problem.
Here is what I tried:
Copy the SystemUI.apk file from /system/priv-app/SystemUI/SystemUI.apk
Copy the frameworks from /system/frameworks/twframework-res.apk and /system/framework/framework-res.apk
Install all frameworks:
Code:
apktool if framework-res.apk
apktool if twframework-res.apk
apktool if SystemUI.apk
Decompile the apk:
Code:
apktool d SystemUI.apk
Edit res/values/dimens.xml with vim. Here is the patch of my edits:
Code:
--- /tmp/vqMxlsi/3 2015-08-19 18:23:07.346653666 -0700
+++ /tmp/vqMxlsi/4 2015-08-19 18:23:07.369986999 -0700
@@ -832,8 +832,8 @@
<dimen name="finder_connect_button_padding_top">11.0dip</dimen>
<dimen name="finder_connect_button_height">35.0dip</dimen>
<dimen name="finder_connect_layout_height">57.0dip</dimen>
- <dimen name="tw_quick_panel_sfinder_qconnect_button_text_size">16.0dip</dimen>
- <dimen name="tw_quick_panel_sfinder_qconnect_drawable_padding">5.0dip</dimen>
+ <dimen name="tw_quick_panel_sfinder_qconnect_button_text_size">0.0dip</dimen>
+ <dimen name="tw_quick_panel_sfinder_qconnect_drawable_padding">0.0dip</dimen>
<dimen name="notificatoin_big_picture_height">176.0dip</dimen>
<dimen name="rssi_battery_gap">3.0dip</dimen>
<dimen name="battery_icon_width">10.0dip</dimen>
Recompile the apk:
Code:
apktool b SystemUI
Zipalign the apk:
Code:
zipalign -v 4 SystemUI/dist/SystemUI.apk final/SystemUI.apk
Copy the new apk to my external sd
Connect with adb and do the following:
Code:
mount -o remount,rw /system
cd /system/priv-app/SystemUI
cp SystemUI.apk /storage/extSdCard/Backup/SystemUI.apk
rm SystemUI.apk
cp /storage/extSdCare/SystemUI.apk .
chmod 644 SystemUI.apk
reboot
Is there something else I am missing? It seems that after my edits, SystemUI.apk just doesn't launch at all. There isn't even an error message. But all I changed are those two lines. The problem is the same with or without the zipalign step. Doing essentially the same procedure above to restore the old SystemUI.apk brings everything back to normal, so I don't think it is a permissions issue. Wiping the cache and dalvik and restarting makes no difference, I have the same problem. Restarting a couple of times also does not resolve the problem.
Any ideas?
MikeDacre said:
OK, unfortunately after making the changes, there is no SystemUI; all I have is my launcher (SmartLauncher) with a black background and no notification bar. After restarting I have the same issue. By putting back the old SystemUI.apk I fix the problem.
Here is what I tried:
Copy the SystemUI.apk file from /system/priv-app/SystemUI/SystemUI.apk
Copy the frameworks from /system/frameworks/twframework-res.apk and /system/framework/framework-res.apk
Install all frameworks:
Code:
apktool if framework-res.apk
apktool if twframework-res.apk
apktool if SystemUI.apk
Decompile the apk:
Code:
apktool d SystemUI.apk
Edit res/values/dimens.xml with vim. Here is the patch of my edits:
Code:
--- /tmp/vqMxlsi/3 2015-08-19 18:23:07.346653666 -0700
+++ /tmp/vqMxlsi/4 2015-08-19 18:23:07.369986999 -0700
@@ -832,8 +832,8 @@
<dimen name="finder_connect_button_padding_top">11.0dip</dimen>
<dimen name="finder_connect_button_height">35.0dip</dimen>
<dimen name="finder_connect_layout_height">57.0dip</dimen>
- <dimen name="tw_quick_panel_sfinder_qconnect_button_text_size">16.0dip</dimen>
- <dimen name="tw_quick_panel_sfinder_qconnect_drawable_padding">5.0dip</dimen>
+ <dimen name="tw_quick_panel_sfinder_qconnect_button_text_size">0.0dip</dimen>
+ <dimen name="tw_quick_panel_sfinder_qconnect_drawable_padding">0.0dip</dimen>
<dimen name="notificatoin_big_picture_height">176.0dip</dimen>
<dimen name="rssi_battery_gap">3.0dip</dimen>
<dimen name="battery_icon_width">10.0dip</dimen>
Recompile the apk:
Code:
apktool b SystemUI
Zipalign the apk:
Code:
zipalign -v 4 SystemUI/dist/SystemUI.apk final/SystemUI.apk
Copy the new apk to my external sd
Connect with adb and do the following:
Code:
mount -o remount,rw /system
cd /system/priv-app/SystemUI
cp SystemUI.apk /storage/extSdCard/Backup/SystemUI.apk
rm SystemUI.apk
cp /storage/extSdCare/SystemUI.apk .
chmod 644 SystemUI.apk
reboot
Is there something else I am missing? It seems that after my edits, SystemUI.apk just doesn't launch at all. There isn't even an error message. But all I changed are those two lines. The problem is the same with or without the zipalign step. Doing essentially the same procedure above to restore the old SystemUI.apk brings everything back to normal, so I don't think it is a permissions issue. Wiping the cache and dalvik and restarting makes no difference, I have the same problem. Restarting a couple of times also does not resolve the problem.
Any ideas?
Click to expand...
Click to collapse
It's because it's odexed. That is why almost every ROM you see is deodexed except stock ROMs.
bilgerryan said:
It's because it's odexed. That is why almost every ROM you see is deodexed except stock ROMs.
Click to expand...
Click to collapse
Do you think it is possible for me to deodex it? I did that before after editing the smali as described above, but I didn't know what to do with the arm/ directory and so I just deleted it, and that didn't work (Got a SystemUI has crashed message).
MikeDacre said:
Do you think it is possible for me to deodex it? I did that before after editing the smali as described above, but I didn't know what to do with the arm/ directory and so I just deleted it, and that didn't work (Got a SystemUI has crashed message).
Click to expand...
Click to collapse
You would have to deodex the entire ROM.
bilgerryan said:
You would have to deodex the entire ROM.
Click to expand...
Click to collapse
Ah! I understand. Sorry for all of these super basic beginner questions. OK, so I am thinking about deodexing the system ROM now, I realize that I could just install an already made custom ROM, but I would like to try this.
As this is my first time trying this, could you clarify if this will work:
Download this tool: http://androidforums.com/threads/tool-linux-batch-lollipop-deodex-v1-9-8-9-15.931146/
Copy /system/app, /system/priv-app, and /system/framework to my computer
Run the 'deodex_lollipop' tool
Create a very simple flashable zip using the sample here: http://www.droidviews.com/create-flashable-zips-cwmtwrp-recovery/ with the contents of the deodexed /system folder I just created
Flash that in TWRP
Then make the edits I mentioned above to the SystemUI.apk
Will that work? Or is it likely to be very difficult?
If it does work, are there downsides to doing it? Not getting future updates, running slower, etc, or should it be basically the same as before except with the s-finder toolbar gone?
Thanks so much for all of your help, this is really great. :good:
MikeDacre said:
Ah! I understand. Sorry for all of these super basic beginner questions. OK, so I am thinking about deodexing the system ROM now, I realize that I could just install an already made custom ROM, but I would like to try this.
As this is my first time trying this, could you clarify if this will work:
Download this tool: http://androidforums.com/threads/tool-linux-batch-lollipop-deodex-v1-9-8-9-15.931146/
Copy /system/app, /system/priv-app, and /system/framework to my computer
Run the 'deodex_lollipop' tool
Create a very simple flashable zip using the sample here: http://www.droidviews.com/create-flashable-zips-cwmtwrp-recovery/ with the contents of the deodexed /system folder I just created
Flash that in TWRP
Then make the edits I mentioned above to the SystemUI.apk
Will that work? Or is it likely to be very difficult?
If it does work, are there downsides to doing it? Not getting future updates, running slower, etc, or should it be basically the same as before except with the s-finder toolbar gone?
Thanks so much for all of your help, this is really great. :good:
Click to expand...
Click to collapse
It should work but line with everything on here requires a lot of trial and error. If it sounds like something you want to try then go ahead.
Related
Hi guys! I see many people trying to learn how to make roms, Here i show the easiest and shortest way on how anyone can begin making roms for the Galaxy S3.
Requirements:
Prepared CWM Stock Package.
Apktool
7-zip
Notepad ++
Setting Up, and Introduction
IF you have downloaded firmware from sammobile instead of zoot1's package, use this part for Setting up and introduction: http://forum.xda-developers.com/showpost.php?p=37812381&postcount=33
OR ELSE THE EASIER WAY
To start with, Download the prepared CWM Stock Rom by zoot1 here: http://forum.xda-developers.com/showthread.php?t=1868004
I personally use firmware from sammobile, because i like to do everything myself. Though this method would be easier for beginners.
Extract the zip file to folder called "ROM".
Now lets head towards the customizing.
Thanks to Prawesome alot for this part. I took some info from his guide.
So now, open up the system folder. You'll find loads of folders in it. Here is a brief introduction to each of those folders:
1. apps
When you open this folder. You will find apk's. An apk is an install-able app package for any Android Device.
You can delete specific apps incase you want to delete. But take extra precautions on what you're deleting. As some apps are useful. You can add apps here as well in formats of apk's. But note, adding Play Store apps to the system/app folder is not recommended. For example you don't want Google Talk in your rom, you just have to delete the Talk.apk.
2. bin
Nothing really to mod in this folder. Full of advanced techy stuff. xD
3. etc
Here is where most of the tweaks come in. There is a folder called init.d where mods like the V6 Supercharger or multi-tasking fixes can be applied. Note! Don't add more than 1 or 2 scripts. Most of them usually conflict with each other.
In the gps.conf file, you can edit your gps info to make the gps more accurate. Pretty good guides about this, search them out.
Next is the hosts file. Devs use this to block sites from generating ads, and keeping their roms ad-free. Take a look at my DroidS3 hosts file, there are over 20,000 hosts blocked. You can use the same hosts file for your rom too.
4. Fonts
Very easy folder to understand. All you need to do here is replace ttf files, and you'll change the fonts.
5. Framework
Here is where the big mods come in. I'll explain further on about this. It contains the android.policy.jar, a useful element to add many mods. Framework-res is used to change wallpapers and theme the rom. I'll explain later.
6. libs
Contains all the libs needed for specific system apps to work. Don't mess here unless you're adding a mod.
7. Folders like csc, hdic, sipdb, wakeupdata, vendor, excetra..
These are the folders, there isn't much to do. Csc folder contains the feature.xml where some mods can be added. Search the forums for that. The rest contain multi-languages and more stuff.
8. xbin folder
Used to add scripts like busybox, dexdump, openvpn support. More like the bin folder but smaller.
9. Build.prop
Ever wondered how some roms have android 5.0, when it hasn't even released? All you need to change is the ro.build.version.release to any number you like. Even Android 20! Go change it, and fool some noobs out there. More mods can be added to this file. e.g:
Code:
debug.sf.hw=1
video.accelerate.hw=1
debug.performance.tuning=1
profiler.force_disable_err_rpt=1
profiler.force_disable_ulog=1
ro.config.nocheckin=1
ro.media.enc.jpeg.quality=100
ro.media.dec.jpeg.memcap=8000000
ro.media.enc.hprof.vid.bps=8000000
ro.telephony.call_ring.delay=0
ro.lge.proximity.delay=15
mot.proximity.delay=15
ro.ril.disable.power.collapse=0
pm.sleep_mode=1
ro.config.nocheckin=1
The codes listed above are for improving jpeg quality, saving some battery life, reducing call delay and more. Search for build.prop mods, you'll find loads of them. Now, a small explanation of the Meta-inf folder.
In Meta-Inf you'll find the updater-script.
Since this is aimed at beginners, I'll just show you how to change what text is shown during install in CWM.
Just edit what's in the quotes of the ui_print code in the file, and enter your own text. e.g:
Code:
ui_print("Hi, This message in quotes is displayed in recovery");
Modding!
It's time for the modding to begin.
Get apktool from: http://forum.xda-developers.com/showthread.php?t=1755243
Now, first copy your framework-res from the /system/framework directory to where you extracted apktool files. Let's call this folder "apktool"
Open the folder apktool, press shift and right click. Click on "Open command window here". Type:
Code:
apktool if framework-res.apk
Now you are ready to decompile apk's.
I'm going to show you how to mod different files. Copy over:
SystemUI.apk
android.policy.jar
framework-res.apk
1. SystemUI.apk
Just showing you basic modding here. Copy over SystemUI.apk to apktool folder. In the command prompt, type
Code:
apktool d SystemUI.apk
After it's done, you should see a SystemUI folder in the apktool directory.
I'm going to show you how to make the status bar transparent, thanks to raubkatze for this part.
Navigate to res/layout/tw_super_status_bar.xml and change android:background to match the red line.
Code:
<com.android.systemui.statusbar.phone.StatusBarWindowView [B][COLOR="Red"]android:background="#00000000[/COLOR][/B]" android:focusable="true" android:fitsSystemWindows="true" android:descendantFocusability="afterDescendants"
xmlns:android="http://schemas.android.com/apk/res/android"
xmlns:systemui="http://schemas.android.com/apk/res/com.android.systemui">
Save and close.
Then navigate to /res/values/drawables.xml
Edit to match:
Code:
<item type="drawable" name="status_bar_background">[COLOR="red"][B]#00000000[/B][/COLOR]</item>
That's it. Save and close.
Go back to your command prompt and type
Code:
apktool b SystemUI SystemUI-new.apk
After it's done, probably will take around 5-10 minutes. You'll find SystemUI-new.apk in your apktool folder. Open both SystemUI.apk and SystemUI-new.apk with 7-zip. Delete AndroidManifest.xml from SystemUI-new.apk and copy AndroidManifest.xml and META-INF from SystemUI.apk to SystemUI-new.apk
That's it. Close the zip files.
If you have adb or android-sdk push SystemUI-new.apk to your phone using:
Code:
adb remount
adb push SystemUI-new.apk /system/app/SystemUI.apk
adb reboot
If you don't have adb, just copy over SystemUI-new.apk to your phone. Rename it to SystemUI.apk and copy to system/app with root explorer. Reboot.
There you have transparent statusbar now!
2. android.policy.jar
Decompile android.policy.jar with:
Code:
apktool d android.policy.jar
You will find android.policy.jar.out, open it and use Cristiano Matos guide to mod the files: http://forum.xda-developers.com/showthread.php?t=2018633
After that use:
Code:
apktool b android.policy.jar.out
Open the android.policy.jar.out folder, you will find a dist folder created and inside that is your modified android.policy.jar.
You can use adb again by:
Code:
adb push android.policy.jar /system/framework
or the normal root explorer method.
3. framework-res.apk
Here i'll show you small mods.
Decompile it using
Code:
apktool d framework-res.apk
Navigate to res/values/bools.xml. Here you can add these. Thanks to DSA for this! :
4 Way Rotation:
Code:
Code:
<bool name="config_allowAllRotations">false</bool>
Change to:
Code:
Code:
<bool name="config_allowAllRotations">true</bool>
Lock Screen Rotation:
Code:
Code:
<bool name="config_enableLockScreenRotation">false</bool>
Change to:
Code:
Code:
<bool name="config_enableLockScreenRotation">true</bool>
and
Code:
Code:
<bool name="lockscreen_isPortrait">true</bool>
change to
Code:
Code:
<bool name="lockscreen_isPortrait">false</bool>
Disable Keyboard Switch In StatusBar When Typing
Code:
Code:
<bool name="show_ongoing_ime_switcher">true</bool>
Change to:
Code:
Code:
<bool name="show_ongoing_ime_switcher">false</bool>
Unplugging From USB doesn't Turn Screen On
Code:
Code:
<bool name="config_unplugTurnsOnScreen">true</bool>
Change to:
Code:
Code:
<bool name="config_unplugTurnsOnScreen">false</bool>[/indent]
Now to change wallpaper. Change the default_wallpaper.jpg in drawable-xhdpi and to change lockscreen wallpaper change keyguard_default_wallpaper.jpg.
Now recompile using:
Code:
apktool b framework-res framework-new.apk
Delete AndroidManifest.xml from framework-new. Copy AndroidManifest.xml and META-INF from framework-res.apk to framework-new.apk
To test use adb:
Code:
adb push framework-new.apk /system/framework/framework-res.apk
Or rename to framework-res.apk and copy to system/framework using root explorer. Reboot.
Once you've added everything, your modified apks. Ui_print mods, A custom kernel (just replace boot.img) it's time to compile. Now this is really easy. Just highlight all the folders/files like system, meta-inf and boot.img. Right click. Hover over 7-zip and click Add to Rom.zip. Wait for it to be done, and copy Rom.zip to your sd card and flash. Voila! You've made your rom!!
You can get more mods to add from here: http://forum.xda-developers.com/showpost.php?p=26583654&postcount=4
I was a beginner once, everyone was a beginner once. People helped me, and now I want to help people.
Press the Thanks button, and/or rate this thread 5 stars to show your support.
FAQ
- How do i add a mod?
To add a mod, just download it. Open it and copy over all the folders from the zip file EXCEPT the META-INF.
- How can i set up apktool on windows?
To set up apktool on windows, you need aapt, apktool.jar and apktool.bat
- My modified apk is not working?
Do some testing and get to know what went wrong. I'm always here. I'll be glad to help.
- Are these the only apps i can modify?
Ofcourse not! Any apk can be modified. Just decompile it, and make your changes.
- I'm looking for a guide on something i want to learn. Can you add it here?
I'll try my best.
Reserved
Reserved one more.
Any feedback guys? I hope this is useful.
Forget that i had to reserve one more.
R: [GUIDE] Beginners/Ref Guide to Making Roms.
Looks interesting...when i will finish my exam i will check with more attention
Sent from my GT-I9300 using xda app-developers app
Willy89 said:
Looks interesting...when i will finish my exam i will check with more attention
Sent from my GT-I9300 using xda app-developers app
Click to expand...
Click to collapse
Thanks. Glad it's of help.
Sent from my GT-I9300 using xda premium
Thnx for making this thread.
It's always useful to read thread's like this.
Nice job.
Verzonden door mijn GT-I9300 met xda premium
Great guide, thanks, I will point Theshawty in this direction :thumbup::thumbup:
slaphead20 said:
Great guide, thanks, I will point Theshawty in this direction :thumbup::thumbup:
Click to expand...
Click to collapse
Too late old man. Not interested in building roms anymore.
Thanks guys.
If there's anything you'd like to have added.
Let me know.
AW: [GUIDE] Beginners/Ref Guide to Making Roms.
Thanks. That's it what i searched for to start. Great.
weli..this would be intersting..and will c hw thread moves...
I Need Help In Building the ROM
Hi,
I am steinert. i need your help in biulding the rom, actually i finished everything but getting the problem while flashing the rom. when i googled it. i came to know that the problem lies in updater-script. i used root explorer to find out the reason. it was like.
FINISHED EXECUTING SCRIPT FILE
EXIT VALUE:126
STDOUT:
NULL
STDERR:
SH:<STDIN>[1]:/CACHE/RECOVERY/LAST_LOG:CAN'T EXECUTEERMISSION DENIED.
I Hope that You help a NOOB like me....
Thank you in advance....
Jacqueline Steinert said:
Hi,
I am steinert. i need your help in biulding the rom, actually i finished everything but getting the problem while flashing the rom. when i googled it. i came to know that the problem lies in updater-script. i used root explorer to find out the reason. it was like.
FINISHED EXECUTING SCRIPT FILE
EXIT VALUE:126
STDOUT:
NULL
STDERR:
SH:<STDIN>[1]:/CACHE/RECOVERY/LAST_LOG:CAN'T EXECUTEERMISSION DENIED.
I Hope that You help a NOOB like me....
Thank you in advance....
Click to expand...
Click to collapse
After flashing the rom.
Check the error through Advanced > Show recovery log in recovery.
Post results here.
I : checking for entendedcommand..
I : skipping execution of extendedcommand, file not found...
Jacqueline Steinert said:
I : checking for entendedcommand..
I : skipping execution of extendedcommand, file not found...
Click to expand...
Click to collapse
Huh?
Get me a screenshot of your meta-inf/com/google/android directory.
What exactly did you modify? It should work if you left the meta-inf untouched.
masterex567 said:
Huh?
Get me a screenshot of your meta-inf/com/google/android directory.
What exactly did you modify? It should work if you left the meta-inf untouched.
Click to expand...
Click to collapse
I just removed all the apps and inserted new apps...!!
Should i send you my updater-script?
Jacqueline Steinert said:
I just removed all the apps and inserted new apps...!!
Should i send you my updater-script?
Click to expand...
Click to collapse
Removed all?
Some are core apps like SystemUI, etc.
Get me a screenshot of your rom.zip..
masterex567 said:
Removed all?
Some are core apps like SystemUI, etc.
Get me a screenshot of your rom.zip..
Click to expand...
Click to collapse
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
This is the screenshot of my rom..! and before also i got the same problem with out changing the system .apk's
Jacqueline Steinert said:
View attachment 1700664
This is the screenshot of my rom..! and before also i got the same problem with out changing the system .apk's
Click to expand...
Click to collapse
Highlight those 3 and in 7zip options click add to " ".zip
Sent from my GT-I9300 using xda premium
Guide: Getting Xposed RunningThis morning, I finally managed to get Xposed up and running on my Turbo. So I thought I'd write up a guide as to how!
What you'll need:
A paid copy of Mofo (obviously)
Either a modified system image containing Xposed already, or if you like, you can modify one yourself as described in this tutorial. I've already created a modified system image to include Xposed as well as Wifi Tethering and a modified hosts file for ad blocking.
The Xposed Installer apk
Xposed Installer needs to be installed on your phone
Terminal Emulator and ES File Explorer from the play store need to be installed on your phone
A rooted image flashed to your phone
Before flashing anything, this is what you need to do:
On your computer, find your de.robv.android.xposed.installer_v33_36570c.apk and rename it to be a .zip file.
Open this .zip file and extract /assets/XposedBridge.jar and, if you're modifying your own system image, extract /assets/arm/app_process_xposed_sdk16 as well.
Put XposedBridge.jar somewhere on your phone, I like to use the Downloads folder so I don't lose track of it later.
In ES File Explorer, navigate to /data (NOT SDCARD/DATA)
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Make sure it doesn't say sdcard > data!
Create a folder called "xposed"
Long press the folder, select properties, and set permissions to 755
Set the owner of the folder to root and the group to shell
Move XposedBridge.jar into the xposed folder we just created.
Make the permissions of XposedBridge.jar 644
As before, make the owner root and the group shell.
Open the Xposed Installer app on your phone.
Open terminal emulator and type
Code:
ps | grep xposed
This will return a pattern like the following. Make a note of the first seven characters, as shown (the first is a lowercase u)
Return to /data/xposed
Create two new files: modules.list and modules.whitelist
Make the permissions on both files 644 as above
Set the owner to the seven characters we noted down earlier and the group to shell on both files
If you're flashing a pre-compiled image with Xposed, you're done here! Go ahead and flash, and enjoy!
If you're modifying your own system image, you've got some more work to do. Take app_process_xposed_sdk16 from the Xposed apk and rename it to app_process.
In your turbo system image, navigate to /bin/ and replace app_process with the one from Xposed Framework. Make sure its permissions are set to 755:
Code:
sudo chmod 755 /path/to/img/bin/app_process
Linux does not allow setting the group of a file to a nonexistent group, so on your pc you'll have to make a shell group:
Code:
sudo groupadd shell
Change the group of app_process to shell:
Code:
sudo chgrp shell /path/to/img/bin/app_process
You're ready to flash!
NOTE: If XposedBridge.jar reports problems, try setting installation mode in the Xposed installer app to recovery (flash manually) and hitting install, then reboot.
You're done! Xposed should show up as installed! Don't use any modules that require system write access, such as replacing system icons, but most modules (ie GravityBox) work fine without it.
Ekkoria said:
This morning, I finally managed to get Xposed up and running on my Turbo. So I thought I'd write up a guide as to how!
Click to expand...
Click to collapse
Gahhh I was working all day on getting Xposed baked in
Thanks for the write up! I'm finding modifying the image file and flashing it to be just as addictive if not more than flashing someones prebuilt roms on other devices. I never got into compiling android so this feels like a way to tinker on my own without jumping into the deep end of code.
ntxct said:
Gahhh I was working all day on getting Xposed baked in
Thanks for the write up! I'm finding modifying the image file and flashing it to be just as addictive if not more than flashing someones prebuilt roms on other devices. I never got into compiling android so this feels like a way to tinker on my own without jumping into the deep end of code.
Click to expand...
Click to collapse
Same here! When I finally opened Xposed Installer and saw it read the framework as installed, I've almost never been so excited about something Android.
i dont need it but its a great guide, easy, short and with pictures!
Does the phone need to be flashed with a rooted image, like that in the tutorial of how to modify system images? I can't write to /data, presumably because I don't have the rooted image flashed yet. Also my /data directory is empty.
I have a copy of mofo, and copies of the rooted system image and your already compiled system image. Is there something I am missing? Thank you in advance.
Thanks so much man, about to flash. Will let you know how it goes.
Ah damn, I actually just did a bit different process of installing Xposed on a image for myself, (which involved baking it into the rom that didn't have it) totally got it working and I've rebooted 3 times so far and everything sticks. Loving having battery percentage now! I can write a quick tutorial writing xposed files into a fresh rooted image via Virtualbox and such... Took me a few hours
It did not work for xposedbridge.jar
aven1357 said:
Does the phone need to be flashed with a rooted image, like that in the tutorial of how to modify system images? I can't write to /data, presumably because I don't have the rooted image flashed yet. Also my /data directory is empty.
I have a copy of mofo, and copies of the rooted system image and your already compiled system image. Is there something I am missing? Thank you in advance.
Click to expand...
Click to collapse
Yes, you will need to be rooted first to perform these actions. Apologies for not originally including this. OP updated
savagebunny said:
Ah damn, I actually just did a bit different process of installing Xposed on a image for myself, (which involved baking it into the rom that didn't have it) totally got it working and I've rebooted 3 times so far and everything sticks. Loving having battery percentage now! I can write a quick tutorial writing xposed files into a fresh rooted image via Virtualbox and such... Took me a few hours
Click to expand...
Click to collapse
Yes please do so. I'd be very interested.
Sent from my XT1254 using XDA Free mobile app
I am having trouble with es file explr it tells me the operation failed when trying to do anything I have root and I enabled root for ES it seemed to work on root browser fine (I reset my device and just installed es so far)
edit checked and the root enhancement options are greyed out?
After following directions for all files and then subsequent flashing of your pre-built image xposed installer still reports framework problem. I've gone back and double checked the user:group and perm masks and everything looks good. Any ideas what else I should check?
I am having same problem as u smokie
smokie75 said:
After following directions for all files and then subsequent flashing of your pre-built image xposed installer still reports framework problem. I've gone back and double checked the user:group and perm masks and everything looks good. Any ideas what else I should check?
Click to expand...
Click to collapse
What's reporting a problem? Is it XposedBridge.jar?
If so, try setting the installation mode to recovery (flash manually) and hitting install, then reboot.
Ekkoria said:
What's reporting a problem? Is it XposedBridge.jar?
If so, try setting the installation mode to recovery (flash manually) and hitting install, then reboot.
Click to expand...
Click to collapse
Thanks! That worked!
Thanks for this , works great , now we just need one with busybox preinstalled
Stuck at this point any help?[/ATTACH]
Ekkoria said:
What's reporting a problem? Is it XposedBridge.jar?
If so, try setting the installation mode to recovery (flash manually) and hitting install, then reboot.
Click to expand...
Click to collapse
so will doing this enable gravitybox to work on the turbo?
hmltnjrmy7 said:
Stuck at this point any help?[/ATTACH]
Click to expand...
Click to collapse
You should be able to foloow the instruction you quoted from that point. You should go back and check your permissions, ownership and group for the 4 files. first
Do the change in install mode to manual. Hit install and go to recovery
recovery should give you the dead droid an then reboot
Also don't worry if the group "shell" shows up as something else in app_proces
rayjr13 said:
You should be able to foloow the instruction you quoted from that point. You should go back and check your permissions, ownership and group for the 4 files. first
Do the change in install mode to manual. Hit install and go to recovery
recovery should give you the dead droid an then reboot
Also don't worry if the group "shell" shows up as something else in app_proces
Click to expand...
Click to collapse
Lol the dead droid freaked me out at first, but I'm so happy xposed finally works!!!
Fix found and released:
http://forum.xda-developers.com/showthread.php?p=60454547
Downloads & instructions: http://forum.xda-developers.com/showthread.php?t=3034811
Discussion & Q&A:http://forum.xda-developers.com/xposed/official-xposed-lollipop-t3030118
I asked moderator to close this thread as issue was fixed by releasing new version of Xposed framework. Please send your further questions and post to respective thread.
This thread is about workaround found for bootloops of Xposed in XPERIA family Lollipop. Because of development progress, I have decided to remove historical development, you can see it here:
LATEST VERSION will be always posted at the END of this post
PLEASE READ INSTRUCTIONS .... The attachment IS NOT flashable!!! For flashables see EDIT 5 and bellow...
I hope I can present some good news for users with locked bootloaders who are getting bootloops with Xposed and Lollipop.
This is still continuous WIP. Know what you do, this is a development thread.
For time being, most complete solution by my opinion was made by @mionica, see EDIT 6 and hist post http://forum.xda-developers.com/showpost.php?p=60298690&postcount=123? and for latest development at http://forum.xda-developers.com/showpost.php?p=60333600&postcount=285
As you may already know, we have find out, that some undetected error is causing system to bootloop, if too many applications are installed.
Exact numbers are varying between different ROMs and devices, generally the maximum number of apps is about 320-330.
Debloating (uninstalling unnecessary apps) helps, but remains limiting and for many frustrating. After a research, we have found out,
that there is probably a bug, that is causing many files being left open when booting Lollipop with Xposed.
Users on unlocked bootloader may modify certain kernel parameters to raise number of open files. This can not be done on Locked Bootloader.
After some research and hours of experiments, I found a way, how to change the filelimit for Zygote and subsequent processes. Therefore every child of zygote (hence every app etc.) will inherit raised open files limit from 1024 to 4096.
This change should work on all 5.0 compatible system, not only XPERIAs, however I only tested it on Z3 D6603 fw 690. But the modification
is done on Linux system level, therefore it should teoretically work just everywhere... It should work also on Locked bootloaders as well.
The principle is easy, however implementation was a tricky, because of lack of native linux utils support on Android and fact that we can not
easily modify booting behaviour. But gladly enough we have XZDualRecovery (gret thanks @[NUT])....
XZDualRecovery enables to call init scripts on startup. I have created a startup script that waits for zygote process to come up, and calls
external program that changes open file limits for that process. This external program is compiled by me from source provided by http://lzone.de/cheat-sheet/ulimit
Prerequisities: Functional XZDualRecovery or other form of init.d support.
Installation:
Extract downloaded ZIP file, it contains:
flimit-binary executable for changing open file limits
01_flimit - shell script called by init
flimit.c - source code of binary executable
Enable init.d support in XZDualRecovery by editing XZDR.prop and change dr.initd.active=true
Dont forget to have enabled byeselinux (dr.keep.byeselinux=true)
copy flimit and 01_flimit to /data/local/tmp (or push adb)
remount /system rw (mount -o remount,rw /system)
create directory /data/flimit
copy flimit to /data/flimit and make executable (chmod 777)
create directory /system/etc/init.d with and chmod 777 /system/etc/init.d
copy 01_flimit to /system/etc/init.d and chmod 777 /system/etc/init.d/01_flimit
test run installation:
Code:
su
/data/flimit/flimit $(pgrep zygote)
output should be:
Code:
[email protected]:/data # /data/flimit/flimit $(pgrep zygote)
Previous limits: soft=1024; hard=4096
New limits: soft=4096; hard=4096
If not, check permissions etc.
Check script by running:
Code:
su
sh /system/etc/init.d/01_flimit
it should now give output (if you succesfully ran /data/flimit/flimit....):
Code:
[email protected]:/data # /data/flimit/flimit $(pgrep zygote)
Previous limits: soft=4096; hard=4096
New limits: soft=4096; hard=4096
reboot
Thats all. Now you can install and update lot more applications. Now I have about 455 packages reported by pm list packages and no bootloop.
But as soon as I disable the init.d support, it bootloops. So re-enable by edititng XZDR.prop and it again boots.
EDIT:Please let me know, if you had to modify the script or instructions to work on your device, so I can perhaps make better or more universal version. Thank you guys.
EDIT 2:While this workaround makes it possible to run Xposed on untouched vanilla Stock ROM, you may still consider debloating it, as debloating will make run your device more smoothly and saves battery. Guys who made debloating scripts made significant efforts in identifying which apps can be safely removed without harming any significant functionality.
EDIT 3:The ZIP is NOT flashable, follow instructions ^^^^ --- buddy @McBane87 is developing flashable version.
EDIT 4:Buddy @nurps found a bug causing Opera browser to quit upon starting. @mionica proposed lowering softlimits for open files to 2048 from 4096 in first version of script. Version 1.1 is released.
EDIT 5:Buddy @McBane87 created customized flashable version of this workaround, so you can flash it from recovery if you struggle with bootloops, dont like to wait fro 300apps to optimize after Dalvik wipe and mess with adb/terminal..
http://forum.xda-developers.com/showthread.php?p=60276913
EDIT 6:Buddy @mionica published another flashable zip. It is complete installer for the workaround, so far most sofisticated workaround from system point of view. The uninstaller completely removes Xposed if you are too tired of it and forgot to make backup Files are bellow, for instructions etc. check it out on http://forum.xda-developers.com/showpost.php?p=60298690&postcount=123 and for latest development at http://forum.xda-developers.com/showpost.php?p=60333600&postcount=285
Changelog:
v1: Initial release
v1.1: Changed limits to 2048 from 4096 as high limits caused Opera Webbrowsers to crash
v2.0 Reference script - for production please flash @mionica version of flashable, my script is published for educational purposes. added mionicas mod to detect only changed limits and subsequently remove only those that are child of zygote
***************************************
I would like to thank mainly to @[NUT] and to guys who made significant effort with debloating, made other discoveries or were an inspiration
for me, including but not limited to @serajr @moly82 @AndroPlus (for his work on file limits in kernel) @redincali and of course to @rovo89
for his Xposed framework. My apologies if I forgot someone, PM me, its 2 o'clock in morning
or in this post http://forum.xda-developers.com/showpost.php?p=60349914&postcount=354
While I have developed initial version (see history), other guys (mainly @mionica and @McBane87) greatly enhanced and redeveloped whole thing.
Current development version and downloadable files you can always find in @mionica post http://forum.xda-developers.com/showpost.php?p=60298690&postcount=123
@mionica managed to analyze boot process on both ROMs with and without Xposed and came to conclusion that leaks are caused by Xposed process leaking open file handles, see here http://forum.xda-developers.com/showpost.php?p=60373854&postcount=417
There is a current version of the workaround fix (see above), that seems to be the last possible, before Xposed will be released with patch addressing that issue. Good news is that thanks to @mionica precise analysis, @rovo89 - developer of Xposed is already aware of the problem nad it´s cause.
Recommended installation steps:
by @mionica
Anybody who is still having any kind of issues, for whatever reason, please do the following:
get into TWRP;
install, in this order, without rebooting:
xposed-uninstall-v1.1.zip
If you don't have an sd card, you'll need to reboot once after the uninstall .zip, boot the system normally, then get back in the recovery and install the other 3. This only applies to people who don't use an SD card
xzdr-busybox-enable-v1.0.zip
xposed-sdk21-arm-date.zip
xposed-leakplug-v1.2.zip
copy the logs to the PC, over USB:
uninstall_xposed.log
install_busybox.log
install_leakplug.log
each of the 3 zip's will tell you where it saved the log (it's usually the external sdcard)
reboot to system
Thanks in advance for not asking any questions about whether you have to do any of these steps; yes, you have to.
Click to expand...
Click to collapse
If you follow other instructions than provided by @mionica please get then support from someone else than him.
The basic idea behind is that Xposed bootloops because of it exhausted resources available due to probably internal bug. The workaround basically provides higher limits for open files during boot and restores previous limits after device has booted. The latest flashable installer is very advanced and automates the installation, including necessary checks for proper XZDR configuration, busybox etc.
When you experience bootloops after installing Xposed, or you had Xposed working and it started to bootloop after you have installed new app or upgraded a system app, simply reboot to recovery and flash the zip. No need to wipe anything.
When installing new, I recommend flashing this zip first, then install Xposed usual way (flash, wipe, reboot, install Xposed apk, install modules).
Be aware that while the workaround works for about 80% of cases, there are people who have lots of applications or heavily modified system, experiencing random reboots. Cause is under investiogation, but most probably is in Xposed itself.
Excellent work friend @ondrejvaroscak. Congrats! Awesome
Was waiting a long time for this! Thanks man! working perfectly.
Working perfectly on D6603, thanks
I am gonig to try this asap! Awesome job!
One more thing, if i understand right, now we can install as many apps as we want or the limit is just higher but still there?
Can we now use regular reboot button from power menu withouth getting bootloop?
--Guys lets go ahead and rape the thanks button
Thank you @ondrejvaroscak for this solution!
@rovo89 any chance this could be integrated in the xposed installer?
Thanks Bro , Very Nice !!
Perfect Work !!
Z1, C6903
Thank you for this great solution, works on Z1.
NetSkill said:
I am gonig to try this asap! Awesome job!
One more thing, if i understand right, now we can install as many apps as we want or the limit is just higher but still there?
Can we now use regular reboot button from power menu withouth getting bootloop?
--Guys lets go ahead and rape the thanks button
Click to expand...
Click to collapse
Unless I will be blessed with some debugging skills, I have no clue... I think limit is just much higher. Once you reach limit you can simply edit script and change two numbers...
Yes, now regular reboot works.
Sent from my D6603 using XDA Free mobile app
norti said:
Thank you @ondrejvaroscak for this solution!
@rovo89 any chance this could be integrated in the xposed installer?
Click to expand...
Click to collapse
I think it will take time, because first @rovo89 would probably want to investigate, how much is it a bug, a constellation of coincidences and so on. I am not sure, if the same bootloops appear only on XPERIAs or it is a phenomenon on other brands as well... And given the fact, that big number of Samsungs can not run Xposed at all, maybe he will try to solve that Samsung puzzle as priority. But that is only guess..
Working on fully setup 5.02 on Z2 thanks.
ondrejvaroscak said:
Installation:
Extract downloaded ZIP file, it contains:
flimit - binary executable for changing open file limits
01_flimit - shell script called by init
flimit.c - source code of binary executable
Enable init.d support in XZDualRecovery by editing XZDR.prop and change dr.initd.active=true
Dont forget to have enabled byeselinux (dr.keep.byeselinux=true)
copy flimit and 01_flimit to /data/local/tmp (or push adb)
create directory /data/flimit
copy flimit to /data/flimit and make executable (chmod 777)
create directory /system/etc/init.d with and chmod 777 /system/etc/init.d
copy 01_flimit to /system/etc/init.d and chmod 777 /system/etc/init.d/01_flimit
Click to expand...
Click to collapse
Thank a lot for big news.... just a clarification:
Which xdual recovery we must have ? also the last 2.8.12 ?
The file XZDR.prop i have located on external memoery...it's correct ?
When you said create a directory /data/flimit.. in where ?
In which way i can "..enabled byeselinux (dr.keep.byeselinux=true).."
Thank
Hispa
hispanico957 said:
Thank a lot for big news.... just a clarification:
Which xdual recovery we must have ? also the last 2.8.12 ?
The file XZDR.prop i have located on external memoery...it's correct ?
When you said create a directory /data/flimit.. in where ?
In which way i can "..enabled byeselinux (dr.keep.byeselinux=true).."
Thank
Hispa
Click to expand...
Click to collapse
Any recovery that supports init.d and byeselinux. So if you find this two settings in your XZDR.prop, you just enable them by setting "true".
I tested with 2.8.12,
XZDR.prop is located in /sdcard1 so its External SD card. If no SD card, then its located in /cache.
/data/limit you create absolutely, it means in / is folder data (that already exists) and you create flimit in /data, so:
Code:
adb shell
su
mkdir /data/flimit
byeselinux you enable by setting "dr.keep.byeselinux=true" in XZDR.prop (it may be set to false by default depending on version fo XZDR you have).
Ok fine... for verify all you said:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
dont find ? where i wrong ??? the folder and file are present
Thank
Hispa
P.S.
Whe you said :
But as soon as I disable the init.d support, it bootloops. So re-enable by edititng XZDR.prop and it again boots.
Click to expand...
Click to collapse
i mean to pu dr.initd.active=false ??
and last after all i can install xposed over .726 odexed ?
hispanico957 said:
Ok fine... for verify all you said:
su
/data/flimit/flimit $(pgrep zygote)
this command from ADB ?
Thank
Hispa
Click to expand...
Click to collapse
from adb or directly in terminal app if you have one..
Sent from my D6603 using XDA Free mobile app
Great thanks
ondrejvaroscak said:
from adb or directly in terminal app if you have one..
Sent from my D6603 using XDA Free mobile app
Click to expand...
Click to collapse
Thank solved but see please my post #14
Hispa
In XZDR.prop i dont have: dr.keep.byeselinux so must i add it if so then under which line ?
I have the latest version of recovery.
Sent From MoonWalker Provolution V1.0 [Beta] Based On LP 5.0.2 !
Pandemic said:
In XZDR.prop i dont have: dr.keep.byeselinux so must i add it if so then under which line ?
I have the latest version of recovery.
Sent From MoonWalker Provolution V1.0 [Beta] Based On LP 5.0.2 !
Click to expand...
Click to collapse
+1 i too cannot find thet line
hispanico957 said:
Ok fine... for verify all you said:
dont find ? where i wrong ??? the folder and file are present
Click to expand...
Click to collapse
can you run "ls -l /data/flimit/*" and paste output to reply?
Whe you said :
i mean to pu dr.initd.active=false ??
Click to expand...
Click to collapse
Exactly, when you put dr.initd.active=false and have full stock, it should again bootloop. Then you replace the XZDR.prop file with version with init.d enabled and it should boot normally again.
and last after all i can install xposed over .726 odexed ?
Click to expand...
Click to collapse
I think without any problem. Deodexing has nothing to do with working Xposed, but it is may be necessary for some modules (Gravitybox?)?
EDIT: The latest oat2dex solves this issue altogether.
WTF IS THE PROBLEM?
The OpenGL and Google Play Store refuse to work because baksmali inside the oat2dex tool misinterprets some fields in a single smali file and breaks "services.jar" when deodexing, and the main problem it causes is mistakenly setting your OpenGL version to 0 (instead of 3), basically disabling it.
oat2dex, for some reason, flips just a few specific fields (name and type) when deodexing, as if there is an ambiguity between 2 fields on the same offset.
When you flash the deodexed services.jar back to your phone and clear dalvik-cache, Android re-optimizes it (takes the "classes.dex" inside your new JAR file, does dex2oat on it, and saves it in /data/dalvik-cache/arm/). The deodexed file is broken, so that optimized file is broken too.
You take that broken odex file from dalvik-cache and deodex it again. Since it contains those flipped field names, this time it flips them again but to the correct fields.
The result DEX file you get by that second deodexing is a properly working DEX file, and if you rename it to "classes.dex" and replace "classes.dex" inside your broken "services.jar", you'll get a working "services.jar" and all your OpenGL and Google Play Store problems will disappear immediately.
HOW TO QUICKLY GET A WORKING DEX?
* Extract classes.dex from the JARs, rename them to framework.dex and services.dex.
* Copy them to your internal SD.
* Enable "USB debugging" in Developer options.
* Connect your device to your PC and open Command Prompt:
Code:
[B]adb shell[/B] (confirm ADB on your device)
[B]su[/B] (confirm SU on your device)
[B]dex2oat --dex-file=/sdcard/framework.dex --oat-file=/sdcard/framework.odex[/B]
[B]dex2oat --dex-file=/sdcard/services.dex --oat-file=/sdcard/services.odex[/B]
* Copy these odex files to your PC and deodex them again with oat2dex.
* Rename the new framework.dex and services.dex to classes.dex and add them to their JARs, replacing the broken classes.dex.
JARS AFFECTED BY THIS BUG
framework.jar/classes.dex --- only a single non-critical error in NumberPicker.smali (classes2.dex is fine)
http://forum.xda-developers.com/attachment.php?attachmentid=3338076&d=1432918042
services,jar/classes.dex --- Total of 8 errors, described below...
http://forum.xda-developers.com/attachment.php?attachmentid=3335118&d=1432772056
BUG REPRODUCTION
Requirements:
1) Java installed
2) oat2dex_bug.zip
ZIP contents:
* baksmali.jar
* oat2dex.jar
* boot.oat --- taken from /framework/arm/
* services.dex --- this is "classes.dex" from the deodexed "services.jar" (which breaks OpenGL)
* services-from-dcache.odex --- this is the odex file taken from "/data/dalvik-cache/arm/" that was created by Android after flashing the broken deodexed "services.jar" and clearing dalvik-cache
Reproduction steps:
1) Open "oat2dex_bug" folder, right-click inside it and then select "Open command window here".
2) Write the following lines exactly as follows:
java -jar oat2dex.jar boot boot.oat
java -jar oat2dex.jar services-from-dcache.odex odex
java -jar baksmali.jar -o services-from-dcache services-deodex.dex
java -jar baksmali.jar -o services services.dex
3) With WinMerge, compare folders "services" and "services-from-dcache".
You'll see that only one file has differences, and it's "ActivityManagerService.smali", that's the file you need to fix.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
In the above images are the only affected areas you need to fix.
Holy @#%. Well done! This issue was a real pain. Thanks
What about fixing framework.jar ? Play store compatibility ?
Sent from my C6903 using XDA Free mobile app
dstrikersZ1 said:
What about fixing framework.jar ? Play store compatibility ?
Sent from my C6903 using XDA Free mobile app
Click to expand...
Click to collapse
framework.jar has only 1 error in NumberPicker.smali, and it's not very critical. Has nothing to do with the Play Store bug. After you've fixed services.jar by deodexing it twice, Play Store is fixed.
IaguCool said:
WTF IS THE PROBLEM?
The OpenGL and Google Play Store refuse to work because baksmali inside the oat2dex tool misinterprets some smali files and breaks "services.jar" when deodexing, and the main problem it causes is mistakenly setting your OpenGL version to 0 (instead of 3), basically disabling it.
oat2dex, for some reason, flips just a few specific fields (name and type) when deodexing, as if there is an ambiguity between 2 fields on the same spot.
When you flash the deodexed services.jar back to your phone and clear dalvik-cache, Android re-optimizes it (takes the "classes.dex" inside your new JAR file, does dex2oat on it, and saves it in /data/dalvik-cache/arm/). The deodexed file is broken, so that optimized file is broken too.
You take that broken odex file from dalvik-cache and deodex it again. Since it contains those flipped field names, this time it flips them again but to the correct fields.
The result DEX file you get by that second deodexing is a properly working DEX file, and if you rename it to "classes.dex" and replace "classes.dex" inside your broken "services.jar", you'll get a working "services.jar" and all your OpenGL and Google Play Store problems will disappear immediately.
JARS AFFECTED BY THIS BUG
framework.jar/classes.dex --- only a single non-critical error (classes2.dex is fine)
services,jar/classes.dex --- described below
BUG REPRODUCTION
Requirements:
1) Java installed
2) oat2dex_bug.zip
ZIP contents:
* baksmali.jar
* oat2dex.jar
* boot.oat --- taken from /framework/arm/
* services.dex --- this is "classes.dex" from the deodexed "services.jar" (which breaks OpenGL)
* services-from-dcache.odex --- this is the odex file taken from "/data/dalvik-cache/arm/" that was created by Android after flashing the broken deodexed "services.jar" and clearing dalvik-cache
Reproduction steps:
1) Open "oat2dex_bug" folder, right-click inside it and then select "Open command window here".
2) Write the following lines exactly as follows:
java -jar oat2dex.jar boot boot.oat
java -jar oat2dex.jar services-from-dcache.odex odex
java -jar baksmali.jar -o services-from-dcache services-from-dcache.dex
java -jar baksmali.jar -o services services.dex
3) With WinMerge, compare folders "services" and "services-from-dcache".
You'll see that only one file has differences, and it's "ActivityManagerService.smali", that's the file you need to fix.
And here are the only differences you find in the file (notice especially the first one and the last one):
Click to expand...
Click to collapse
java -jar baksmali.jar -o services-from-dcache services-from-dcache.dex
Click to expand...
Click to collapse
Error: "Can´t find the file services-from-dcache.dex"
There is no such file in the zip either - only services-from-dcache.odex, but with this file it did not work
moonryder said:
Error: "Can´t find the file services-from-dcache.dex"
There is no such file in the zip either - only services-from-dcache.odex, but with this file it did not work
Click to expand...
Click to collapse
Then you made a mistake somewhere.
IaguCool said:
Then you made a mistake somewhere.
Click to expand...
Click to collapse
tried it again, step 1 and 2 without problems, but step3 the same error as mentioned before
there is a new file in the folder called "services-deodex.dex"
moonryder said:
tried it again, step 1 and 2 without problems, but step3 the same error as mentioned before
there is a new file in the folder called "services-deodex.dex"
Click to expand...
Click to collapse
Ahh I see that oat2dex renames the file for some reason. I fixed line 3 to
java -jar baksmali.jar -o services-from-dcache services-deodex.dex
You could figure that out yourself, you know... by looking inside the folder, I don't see why you repeat every step like a robot uncritically.
IaguCool said:
...I don't see why you repeat every step like a robot uncritically....
Click to expand...
Click to collapse
cause i am not a programmer and a noob in this field contrary to you (maybe you are a genius and i am a little user :angel: )
moonryder said:
cause i am not a programmer and a noob in this field contrary to you (maybe you are a genius and i am a little user :angel: )
Click to expand...
Click to collapse
So basically it's like pushing a screwdriver into a wall socket without knowing what electricity is... I don't get why people that don't develop even try to deodex themselves in the first place. Deodexing is meant for developers, not "little users"...
so its must to be writen GL_ES_VERSION:I
its i/1/L ?
Alvian_P said:
so its must to be writen GL_ES_VERSION:I
its i/1/L ?
Click to expand...
Click to collapse
It's "I" for Integer. Seriously what are you people doing here? It's for *developers*, normal users have nothing to gain from this process.
That's how I have fixed it too, well done
Take care that mWentToSleep must also be fixed.
Both lines are inverted.
Edit: nevermind, your method is inverting both... I did it manually.
Please tell what command compiles the folder "services" into file "services.dex" back?
Bazooka Joe said:
Please tell what command compiles the folder "services" into file "services.dex" back?
Click to expand...
Click to collapse
Google for "smali-2.0.5.jar" for that. baksmali only decompiles.
IaguCool said:
It's "I" for Integer. Seriously what are you people doing here? It's for *developers*, normal users have nothing to gain from this process.
Click to expand...
Click to collapse
@laguCool
1. thx for discovering that problem and its solution
2. all devs began once upon a time, so i think threads like this one are very helpful for users who want to learn and become a dev in future too. So
3. please be soft with all of them who asks questions here.
Thx again for your excellent work and knowledge.
m.
moonryder said:
@laguCool
1. thx for discovering that problem and its solution
2. all devs began once upon a time, so i think threads like this one are very helpful for users who want to learn and become a dev in future too. So
3. please be soft with all of them who asks questions here.
Thx again for your excellent work and knowledge.
m.
Click to expand...
Click to collapse
Well, being soft isn't my thing, it's against my nature...
Anyways, if a person doesn't know what "I" means in Dalvik opcode, they are doing the learning process wrong. They need to be familiar with Dalvik datatypes beforehand.
IaguCool said:
It's "I" for Integer. Seriously what are you people doing here? It's for *developers*, normal users have nothing to gain from this process.
Click to expand...
Click to collapse
just look around , anyways my college is IT
ah sorry if this thread not open for normal users
IaguCool, Big, big Thanks!!! OpenGL worked now! :good:
There is a more simple way for obtain dirty odex from dirty dex file. Just copy deodexed services.dex to sdcard and type in terminal
dex2oat --dex-file=/sdcard/services.dex --oat-file=/sdcard/services.odex
Then copy created /sdcard/services.odex to PC and deodex them again to obtain correct services.dex.
_SIL_ said:
IaguCool, Big, big Thanks!!! OpenGL worked now! :good:
There is a more simple way for obtain dirty odex from dirty dex file. Just copy deodexed services.dex to sdcard and type in terminal
dex2oat --dex-file=/sdcard/services.dex --oat-file=/sdcard/services.odex
Then copy created /sdcard/services.odex to PC and deodex them again to obtain correct services.dex.
Click to expand...
Click to collapse
Thank you I rarely use the terminal so I missed that. I actually copied all /framework/ odex files from dalvik-cache to see if there are more JARs affected by this bug, will add them to the list if I find any.
Hello Guy today I want to teach you how to fix WiFi region code problem on Nought and Oreo roms
FIX FOR NOUGHT ROMS AND OREO ROMS(ONLY FOR BUILDS BEFORE 19/1/2018)(NOT FOR cypherOS)
If you are on builds after 19/1/2018 or cypherOS go down ; there is a way with xposed to fix the problem
reqierments :
1. knowing how decompile .jar files (you can use This tool)
2. notepad ++(for editing some files)
3. "telephony-common.jar" from rom (you can find it in "system -> framwork)
4. framwork-res.apk of rom (you can find it in "system -> framwork)(the process may work without it)
** if you see this mark on TUT it means "if you use the tool that is on first requierments"
Steps :
1. install the "framework-res.apk" for apktool (** copy it to "in" folder of tool
then choose " 1 " and choose the "framwork-res.apk" of rom)
2. decompile the "telephony-common.jar" file and go the folder of the decompiled file (** copy the file to "in" folder open the tool and choose " 2 " then choose the "telephony-common.jar" and continue the process to complete decompile and then you can find the folder of decompiled file in "out" folder)
3. After you go to the folder of decompiled file go to " smail -> com -> android -> internal -> telephony " then search for " MccTable " and open it with "notepad ++"
4. on " notepad ++ " search for " setWifiCountryCode " and you will find three lines with it
go to first line
under it you will see " .locals 5 " change it to " .locals 13 "
( as you can see in picture )
first line
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
then go to second line
go a little upper and found (here is .line 199)(but the line number may change duo to rom)
:cond_1
Click to expand...
Click to collapse
and change the line below of it to
goto :goto_0
Click to expand...
Click to collapse
( as you can see in picture )
second line
there is no need to touch the third line
5. save the file and close " notepad ++ "
6. now recompile the file (** choose " 3 " to recompile the file and choose "telephony-common.jar" and then press NUM "4" option (Recompile, Sign And Then Zipalign)and continue the process to complete recompile )
6.1 ( ** you can find the file on " done " folder)
7. after the recompile completed copy the file to your phone
8. on your phone replace old " telephony-common.jar " with the new one and set permissions and reboot phone
P.S. after the reboot the phone may not boot at the first time (dont worry) just force shutdown your phone ( by press and holding "power button" and "volume up" and phone will vibrate 3 times ) then turn on your phone again
and you will see the problem of region code is gone :good:
FIX FOR all Nought and OREO BUILDS (LOS & RR & CARBON & CYPHER OS)
first of all thanks to @ali6944 for finding this xposed modules
you just need xposed for it and install this modules then active it and reboot your phone and problem is gone :good:
Cool to see it nicely put in an easy to follow format, Good job!:highfive:
I have done exactly what you did with the same tool, but only in step 6 when recompiling, I am getting four options :
Recompile "telephony-common.jar"
1 - Only Recompile
2 - Recompile And Then Sign
3 - Recompile And Then Zipalign
4 - Recompile, Sign And Then Zipalign
I chose the first one and I got the file in "done" folder but in zip format like this telephony-common.zip
I changed the extension to .jar and copied it to phone, replaced the old one and gave permissions, powered off the device (force shut down) and turned it on but I didn't get a working WIFI, I am on RR 5.8.5 BTW, thanks for the help.. hope you can reply soon..
Dr.TheMaster said:
I have done exactly what you did with the same tool, but only in step 6 when recompiling, I am getting four options :
Recompile "telephony-common.jar"
1 - Only Recompile
2 - Recompile And Then Sign
3 - Recompile And Then Zipalign
4 - Recompile, Sign And Then Zipalign
I chose the first one and I got the file in "done" folder but in zip format like this telephony-common.zip
I changed the extension to .jar and copied it to phone, replaced the old one and gave permissions, powered off the device (force shut down) and turned it on but I didn't get a working WIFI, I am on RR 5.8.5 BTW, thanks for the help.. hope you can reply soon..
Click to expand...
Click to collapse
yes you are right i have forgot to say anything about that four option
i choose " 4 " ( Recompile, Sign And Then Zipalign )
and i dont know why it was in zip format
and another thing is i did this for carbon rom which has no option to change wifi region code i dont know if it works on RR
BTW try again with the NUM 4 option and if it didnt worked send the telephony-common.jar file to me to see what can i do
I got it working for RR using this..
raminta said:
yes you are right i have forgot to say anything about that four option
i choose " 4 " ( Recompile, Sign And Then Zipalign )
and i dont know why it was in zip format
and another thing is i did this for carbon rom which has no option to change wifi region code i dont know if it works on RR
BTW try again with the NUM 4 option and if it didnt worked send the telephony-common.jar file to me to see what can i do
Click to expand...
Click to collapse
After doing exactly as you showed, but instead of recompiling using this tool I recompiled the file using the APKTOOK that was installed previously on my computer using this command (after opening CMD in the out folder)
Code:
apktool b -f -d telephony-common.jar
after that I copied the output file from the dist folder (telephony-common.jar\dist) and replaced it with permissions and it worked perfectly (RR 5.8.5), thanks for helping and keep it up for more tutorials :highfive:
Newest Carbon rom build has 410byte dummy version of telephony-common.jar, this fix cannot be enabled.
jjanggukin said:
Newest Carbon rom build has 410byte dummy version of telephony-common.jar, this fix cannot be enabled.
Click to expand...
Click to collapse
Sorry im a little bussy (with exam) i will look at it tomorrow
jjanggukin said:
Newest Carbon rom build has 410byte dummy version of telephony-common.jar, this fix cannot be enabled.
Click to expand...
Click to collapse
It's because the rom is not deodexed, I've spent a lot of time searching for a way to deodex and found out that android 8.1 moved to .vdex instead of .odex so there isn't yet a way to deodex to apply this fix, you can learn more about this here: https://github.com/JesusFreke/smali/issues/498
ali6944 said:
It's because the rom is not deodexed, I've spent a lot of time searching for a way to deodex and found out that android 8.1 moved to .vdex instead of .odex so there isn't yet a way to deodex to apply this fix, you can learn more about this here: https://github.com/JesusFreke/smali/issues/498
Click to expand...
Click to collapse
For linux you can use this: https://github.com/anestisb/vdexExtractor
for windows: https://github.com/Furniel/Apk-Changer
i successfully deodexed the whole framework but there's something wrong!
if you removed oat and arm folders then flashed the deodexed framework you will enjoy with the lovely bootloop, if you flashed without removing oat and arm folders it's fine but not effects for any modded jars!! so basically the deodexed framework is useless!!
here is the file which you need already deodexed and patched and if you find anyway to get it working please let me know because i miss some mods since the latest build
rocker00 said:
For linux you can use this: https://github.com/anestisb/vdexExtractor
for windows: https://github.com/Furniel/Apk-Changer
i successfully deodexed the whole framework but there's something wrong!
if you removed oat and arm folders then flashed the deodexed framework you will enjoy with the lovely bootloop, if you flashed without removing oat and arm folders it's fine but not effects for any modded jars!! so basically the deodexed framework is useless!!
here is the file which you need already deodexed and patched and if you find anyway to get it working please let me know because i miss some mods since the latest build
Click to expand...
Click to collapse
Nice work, will keep on the case, can't stand being on an obsolete build forever!
ali6944 said:
Nice work, will keep on the case, can't stand being on an obsolete build forever!
Click to expand...
Click to collapse
Latest build of Lineage and CypherOS is the same, so that's might be the new style and i think it's better if we can find a solution for that rather than using old builds!
rocker00 said:
Latest build of Lineage and CypherOS is the same, so that's might be the new style and i think it's better if we can find a solution for that rather than using old builds!
Click to expand...
Click to collapse
You are absolutely right, also it's a universal thing with all the new 8.1 roms, even the Pixel phone OTAs have it so a lot of effort is being but into this right now, I'll keep trying, I'm even using the latest build of carbon right now, it's a bit inconvenient having to reboot the phone every time you disconnect from WiFi, but this motivates me to try even further!
@rocker00 can you try installing vdex extractor, you can find it compiled and ready here:
https://www.dropbox.com/s/cbqs5e8nwy...actor.exe?dl=0
it didn't want to install on my PC for some reason, if you can get it working try using it on boot-telephony-common.vdex from framwork/arm and see what comes up
ali6944 said:
@rocker00 can you try installing vdex extractor, you can find it compiled and ready here:
https://www.dropbox.com/s/cbqs5e8nwy...actor.exe?dl=0
it didn't want to install on my PC for some reason, if you can get it working try using it on boot-telephony-common.vdex from framwork/arm and see what comes up
Click to expand...
Click to collapse
Link doesn't work(404)
raminta said:
Link doesn't work(404)
Click to expand...
Click to collapse
Here it is on Google Drive: https://drive.google.com/open?id=13PLmXstJs5GfrJT5ji4-yuE_8WjaA8Xj
ali6944 said:
@rocker00 can you try installing vdex extractor, you can find it compiled and ready here:
https://www.dropbox.com/s/cbqs5e8nwy...actor.exe?dl=0
it didn't want to install on my PC for some reason, if you can get it working try using it on boot-telephony-common.vdex from framwork/arm and see what comes up
Click to expand...
Click to collapse
This is not an app to install, it's like command line, also it doesn't make any sense to try this because the tool i mentioned for windows also based on vdexextractor, it's just implemented for windows.
now am confused more and more, i flash deodexed patched services.jar (aka superuser mod) and it worked! then i tried to remove services.vdex from oat/arm and it worked also!! so why it worked with or without .vdex from oat/arm and the other mods based on arm folder doesn't work and if you removed boot-......vdex for any jar you will have bootloop!!
rocker00 said:
This is not an app to install, it's like command line, also it doesn't make any sense to try this because the tool i mentioned for windows also based on vdexextractor, it's just implemented for windows.
now am confused more and more, i flash deodexed patched services.jar (aka superuser mod) and it worked! then i tried to remove services.vdex from oat/arm and it worked also!! so why it worked with or without .vdex from oat/arm and the other mods based on arm folder doesn't work and if you removed boot-......vdex for any jar you will have bootloop!!
Click to expand...
Click to collapse
here is a thread that i found helpful: https://forum.xda-developers.com/pi...lly-deodex-stock-oreo-systemui-t3685034/page3
It seems like even the gods of deodexing are having the same issues, you can deodex pretty much anything including services.jar, but you can't touch any other framework file without causing a bootloop, if i got the conclusion right then i think we need to wait for jesusfreake to update smali and backsmali to support vdex
ali6944 said:
here is a thread that i found helpful: https://forum.xda-developers.com/pi...lly-deodex-stock-oreo-systemui-t3685034/page3
It seems like even the gods of deodexing are having the same issues, you can deodex pretty much anything including services.jar, but you can't touch any other framework file without causing a bootloop, if i got the conclusion right then i think we need to wait for jesusfreake to update smali and backsmali to support vdex
Click to expand...
Click to collapse
Yeah, the latest post in the thread you mentioned exactly the same issue i have, looks like we are out of luck now!
I can't believe I forgot about this, but while I was looking for a fix for nougat months ago I found this xposed module that fixes the issue, but since I got WiFi working before that, I totally forgot about it, I just tried it with the latest Carbon rom and it works! Can't believe it was right there for so long
Here it is http://repo.xposed.info/module/android.wifiregionalfix
ali6944 said:
I can't believe I forgot about this, but while I was looking for a fix for nougat months ago I found this xposed module that fixes the issue, but since I got WiFi working before that, I totally forgot about it, I just tried it with the latest Carbon rom and it works! Can't believe it was right there for so long
Here it is http://repo.xposed.info/module/android.wifiregionalfix
Click to expand...
Click to collapse
added to first post thanks alot