Database Info

Can't use themes on SR sense 3.5

okay...I'm using skyraider sense 3.5, but for some reason when I try to use rommanager to install themes for it, it goes to the recovery, tries to flash it, but says "operation unsuccessful." I believe it is due to me accidentally updating my clockworkmod. I have tried downgrading back to cwm 2.5.0.5, but when I flash that, it says operation unsuccessful also...i can flash fonts fine. I have no idea what is wrong. Does anyone have any idea how I could flash a theme for it Other than completely clearing everything and reinstalling sr sense 3.5?
Thanks in advance
Sent from my ADR6300 using XDA App

Use amonRA. I think its compatible with amend script. Or u can downgrade clockwork with a pb31img.zip...you can also try update your zip to edify script using amend2edify script converter. I've had mixed results though. Its pretty easy to just recompile the zip in edify

I've never recompiled any script before. I wouldn't know what to do. And amonra - is there a certain version i could use? Or should any work?
I'm going to try amonra tomorrow night after work i suppose. Lol. I just want to try and be able to flash a theme lol. I tried the PB31IMG.zip with no luck. It does the same thing :-/ i tried renaming it, caps, no caps, changing it to update.zip, having it in the root of my sdcard, in my download
Folder... No luck :-(
Sent from my ADR6300 using XDA App

Don't forget you flash the pb31img thru hboot. All letters capitalized. Compiling is easy. Just get a program that generates a zip with update binary in it. You can probably just take a zip you know works and delete everything but the com folder inside Meta. Than drop the files you need inside the zip. I think any amonra should work for you. Alexander uploaded cw 2.5 zip on SR forum.

Major Problem- installation aborting!!

Hey all. I have a galaxy S 4G and I already rooted it. Am currently trying to install the Bionix Frost ROM. Also some lock screens. The problem is every time I try to reboot to recovery it says installation aborted. I don't know what to do. Can someone please help me. Thank you.

guitarology said:
Hey all. I have a galaxy S 4G and I already rooted it. Am currently trying to install the Bionix Frost ROM. Also some lock screens. The problem is every time I try to reboot to recovery it says installation aborted. I don't know what to do. Can someone please help me. Thank you.
Click to expand...
Click to collapse
Are you trying to use the stock recovery or cwm recovery
Sent from my SGH-T959V using XDA Premium App

You need to use krylons final cwm. Also, to make your life easier, push the tweaks into the zip file prior to flashing. Init.d. Kg6 fugu. Updated builds prop...or just flash icbinb.
Sent from my SGH-T959V using XDA Premium App

jager555 said:
You need to use krylons final cwm. Also, to make your life easier, push the tweaks into the zip file prior to flashing. Init.d. Kg6 fugu. Updated builds prop...or just flash icbinb.
Sent from my SGH-T959V using XDA Premium App
Click to expand...
Click to collapse
How do you push tweaks into a zip file prior to flashing?

guitarology said:
Hey all. I have a galaxy S 4G and I already rooted it. Am currently trying to install the Bionix Frost ROM. Also some lock screens. The problem is every time I try to reboot to recovery it says installation aborted. I don't know what to do. Can someone please help me. Thank you.
Click to expand...
Click to collapse
are you trying to install lock screens from the vibrant if so it wont work
as the vibrant uses amand scripting and sgs4g uses edify
hince why your getting installation aborted

the bionix frost rom zip file. open up the cwm flashable for the tweaks and you will notice they are in a specific folder structure. the rom has the same folder structure. move the file from the cwm flashable to the rom zip file following the same folder structure and replace the file in the rom zip file. for example, if the cwm flashable has folders system/app, then move the file to the system/app folder in the rom.

jager555 said:
the bionix frost rom zip file. open up the cwm flashable for the tweaks and you will notice they are in a specific folder structure. the rom has the same folder structure. move the file from the cwm flashable to the rom zip file following the same folder structure and replace the file in the rom zip file. for example, if the cwm flashable has folders system/app, then move the file to the system/app folder in the rom.
Click to expand...
Click to collapse
that works to but i was wondering what he was trying to replace lol
so he doesnt soft brick

o i was just going to say build.prop, fugu from kg6, bootanimations and sounds, perhaps the launchers, he can build in his apps via the data folders all prior to flashing, the icbinb init.d/ext4 optimizations and so forth. nothing too crazy.

[Q] Moving modified .apks to the same roms update

Hello so what I've got is this. I've modified some of the system .apks and the framework on my current rom well an update has rolled out and i was wondering how do i take those modded apps with me I've used zipthemer and cwm but i get a bootloop using zipthemer i had wrote my xml to install the entire .apk is this wrong any help would be greatly appreciated thanks

Use Super Manager to make a backup of all your .APK's on the device it will be under the .APK section in Super Manager around tab 4 or 5 i believe! Mount your SD card in your PC after the backup and push the backup .APK's to a new folder on your PC and do a fresh clean flash of the new ROM then push the .APK's back onto the device after you reboot! If this is not exactly what you are looking for feel free to elaborate a bit more im pretty sure i understand the concept you are going for!

That's pretty much what I'm aiming at only im talking about modified /system apks I usually wind up pulling the apps and framework and replacing the image files inside the new ones with the ones ive edited using 7.zip and pushing them back to /system/app or framework with adb but man that takes forever lol I guess what ive done here is created a system wide theme including system apps and framework but i dont know how to write the xml to push the images into the framework and apks through a cwm flashable
I guess im kinda looking for building a flashable theme something i can just flash after installing the rom update but I''m not really sure if what I've done is or could be considered a theme i guess it would be seeing as how it changes the look of the apps and framework its seems like I'm themeing the hard way
(btw typing while i think sorry if it doesn't make sense)
edit - but it seems like ive tried pushing the actual "old" apk from an older version to a new version of the same rom and it force closes
Sent from my Incredible 2 using xda premium

AHH yea now i fully understand what you are getting at... props br0... i for one have never used ABD to push system modified values back to the droid but i completely get what your doing. I assume the "old.apk" force closes because your modified values collide with the default values resulting in a source error, are you using some sort of hex editor to modify anything? or just extracting .png's and swapping? if swapping .png's only you should be able to extract swap and rebuild with success but im sure there will be bugs as this is open source of sorts! I'll take a look around and see if i can find anything structured towards this because i gotta tell you man that is something i have thought about taking on myself for a little bit now just haven't gotten around to it. Sounds easy enough to do what you are going for as does most things... until you put it into practice lol i'll have a look around br0

No I'm not using an editor just 7zip to open the apk and pulling pngs from old and placing them in the "new" apk and pushing it back to the system folder if you can download something like this from the market surely I can build one I think I'm just missing something
That would be awesome man any help further into this would be greatly appreciated and Ill do the same and post here
Sent from my Incredible 2 using xda premium

Nevaloud said:
No I'm not using an editor just pulling pngs from old and placing them in the "new" apk and pushing it back to the system folder
That would be awesome man any help further into this would be greatly appreciated and Ill do the same and post here
Sent from my Incredible 2 using xda premium
Click to expand...
Click to collapse
Download a apk editor just Google how to edit apk and you should find a nice set of script put together as a cmd promt.There extract the apk both old and new then replace the PNG files.After that repackage them using the script and also sign them as a system apk (there is a script for this too).After that just copy it to the folder you took it from or via ADB.I edited mine SystemUI.apk like this and now my status bar is exactly like the one in ICS
Sent from my LG-P350 using xda premium

This sounds like what I do with with 7zip i keep the drawable files ive edited on my cpu after a rom update i pull the new apk and open with seven zip and just drag and drop what I've edited to the open res
push back reboot success
Sent from my Incredible 2 using xda premium

Nevaloud said:
This sounds like what I do with with 7zip i keep the drawable files ive edited on my cpu after a rom update i pull the new apk and open with seven zip and just drag and drop what I've edited to the open res
push back reboot success
Sent from my Incredible 2 using xda premium
Click to expand...
Click to collapse
Yeah but i think you need to sign them too in order for them not to FC and yeah rebooting after you pushet them is a must
Sent from my LG-P350 using xda premium

O no no they don't force close doing this at all
they only force close when I tried pushing an "old" apk to the "new" rom
If you pull the new ones and change with 7zip and push back they're money
I really just want to build a flashable theme zip so I don't have to pull all kinds of stuff after an update
Just a simple flash maybe even something i could deploy onto another inc2 but I'm really not sure if that's possible because of the amount of changes done to multiple apks and framework
If you guys would like to see screen shots ill post some just for fun I've done alot of work
Sent from my Incredible 2 using xda premium

http://forum.xda-developers.com/showthread.php?t=1111476
you can have a look at this

Thank you for the link but I'm not using apktool to decompile apps I'm just editing .Png images and putting what I pull from the phone back on the phone like a theme would but I'm not just editing the framework-Res I've "themed" 6 or 7 system apks aswell but I have done zero XML editing to anything
From my Inc2 Nevaloud V2.6

[Q] How to change Kernel of ROM Before installatio in it's zip file.

I would like to learn how one can change the kernel/modem in a ROM's zip BEFORE flashing it. I often use the Entropy Kernel after I flash a new ROM. The Kernel has a zimage file. How do I incorporate it into the zip? Same for modem file.
Thanks in advance.

NeoMustain said:
I would like to learn how one can change the kernel/modem in a ROM's zip BEFORE flashing it. I often use the Entropy Kernel after I flash a new ROM. The Kernel has a zimage file. How do I incorporate it into the zip? Same for modem file.
Thanks in advance.
Click to expand...
Click to collapse
Whats worked for me:
First get 7zip if you are on windows
Open the kernel zip with 7zip move the redbend_ua and zImage into this location (rom name here).zip/updates
For modem do the same, open up the modem zip with 7zip, and then move the modim.bin into (rom name here).zip/update
You may need to delete the redbend and zImage already in the rom, but just overwriting it with the new ones should work
Once the new kernel/modem is copied over, just put it on your sdcard and you should be able to flash it without any problems
Sent from my SAMSUNG-SGH-I997 using XDA

or just the zimage...since the ua is same...

Never tried it without doing the ua when it came to the kernel, but it does make sense since i never moved the ua when ever id move the modem
Sent from my SAMSUNG-SGH-I997 using XDA

The ua is universal on all roms... its just an installer for the modem and kernel ... no need to change it. If the rom already has it then just replace the zimage and your good.
Sent from my SAMSUNG-SGH-I997 using xda premium

I request some experienced sr. member to comeup by posting new thread covering some of topics like safely adding and removing apks, libs. Fonts, apps, wallpapers, kernel. Modem etc. in Rom's zip with little flavouring. It will help new member to start some development work.

Thanks guys ... 1 more small step

hey can anyone give instructions on fixing RIL bug...it would be so much helpful...thnx

How to create your own tw rom on your phone using root explorer

In this tutorial I will show you how to create your own T.W. rom using your GS3 and Root Explorer. There are many ways you can create a rom but not everyone has the time to sit at a computer every night. However, your phone is always on you and can find a few minutes here and there to create your own masterpiece.
For the sake of this tutorial, we will name our new rom "SLICK".
Here are a few things you will need...
1. The rom base from Scottsroms. I'm NOT talking about Cleanrom but the unmodified stock rooted rom.
2. Root Explorer.
3. Script Manager
4. Any mod you can flash or come up with on your own.
1. GET STARTED!
Download the base rom to your phones EXT-sdcard and extract it using Root Explorer. After it's extracted the new unziped rom will be located in /storage/sdcard0/SpeedSoftware/Extracted. The extracted rom is now your new base. At this point it would be a great idea to move it to your EXT-sdcard and create a new project folder for it and label the folder "Project SLICK". inside the folder is your rom. lets rename that rom "SLICK".
Lets open your new SLICK rom. You should have some folders...
BOOT IMAGE
DATA
META-INF
SYSTEM
3. THE SYSTEM FOLDER
/SYSTEM/APP
Most of your work will done in the System folder so lets open that up. This is the heart of your rom! There are many folders here but lets start with the app folder. This folder has every app installed in your rom. This is a good time to remove the bloat you don't want in your rom. Go ahead and delete the apk's you don't want or need.
/SYSTEM/BIN
Here you can speed up your system or make it more battery efficient by deleting things like "mpdecision" and things like that. Be careful what you delete though. In general you won't do much in here.
/SYSTEM/BUILD.PROP
Here you can change values or add values. The one value we are concerned with is "ro.build.display.id" This build property's value will be displayed in the end users settings menu under "about phone". So let's give this property the correct value "ro.build.display.id=SLICK ROM v1.0" The rest of the build properties you can do as you wish. Build.prop is simply a text file. You can use the text editor built into Root Explorer.
/SYSTEM/CSC
Open this file and you will see more files. Listed is "feature.xml". Here you can edit values for various items for texting and mms.
/SYSTEM/ETC
Here is where you will find a folder called "init.d". Located in this folder are various text files. The text files are scripts that are told to run when your phone boots. You can add or modify to the existing scripts or create a new text file.
So we went over a few of the basics of modding your new rom and molding it into something you can call your own but does it work??
4. TESTING YOUR NEW BASE.
So we have already modified our rom a considerable amount and should have a good solid base. Before we go any further we should really test things out first. If we did something wrong earlier we will at least have an idea where to look. So lets flash our new rom. Go to you EXT-sdcard and find our project folder. you should still have your SLICK file. Zip this file with Root Explorer. Make sure you have a good battery and a cool environment because it's going to take your GS3 about 30min of hard work to zip this file. When that is finally completed, flash your new rom located in /storage/sdcard0/SpeedSoftware/Archives. Flash it just like you would any other rom.
Test your new rom out on your GS3 and see how things are running. Check your existing modifications you did earlier. If everything looks good, we can continue modding. If not you will need to go back to your base to see where you went wrong. This is also a great time to check your init.d scripts. One way to do this is to download "Script manager" from the market and click on your init scripts to read there log. It will tell you if something went wrong.
If everything is looking good, we can continue modding...

5. THE MODS
So we have that nice clean base but what about all them mods in the roms we download and flash everyday? There are a few different ways we can do this and we will start with the easiest but first, do a nandroid backup of your new base. If one of your mods you perform next goes bad it's simply quicker to recover. Now, If you have flashable zips of some of the mods you like then you can flash them now and make sure they are working the way they should in your rom. Remember, just cause we have the d2vzw does not mean mods from the sprint or T-mobile won't work on our devices. Sometimes it's worth a try. It's all about which firmware they are on and what has changed with the firmware.
So we flashed a few mods but don't have everything we wanted. At this point you are left with only one option and that is to get on that PC of yours and learn to decompile a APK. I may touch on this subject later as it is a bit more involved for someone new to this sort of thing.
6. UNDERSTANDING THE FLASHABLE ZIP
The alternate method of a flashable zip is to extract your flashable using Root Explorer and picking it apart. For example we will use "Lean Kernel" and kill 2 topics with one stone. If you unzip the kernel you will see...
BOOT.IMG
META-INF
SYSTEM
As you can see there are some familiar files to us just like when we extracted our base rom in the beginning. Basically when you flash a mod like this or any flashable for that matter, it installs files into your rom in certain places. In this example we will be installing in BOOT.IMG and SYSTEM. But what? And what is that META-INF file for? Well this META-INF file is what tells your rom what files and what to do with those files. Inside META-INF is a text file called an "updater script".
Here is what it looks like...
Code:
show_progress(0.500000, 0);
mount("ext4", "EMMC", "/dev/block/mmcblk0p14", "/system");
package_extract_dir("system", "/system");
set_perm(0, 0, 0777, "/system/etc/init.d/00leanKernel");
unmount("/system");
assert(package_extract_file("boot.img", "/cache/boot.img"),
write_raw_image("/cache/boot.img", "/dev/block/mmcblk0p7"),
delete("/cache/boot.img"));
show_progress(0.100000, 0);
Line 2 shows it mounting the system so we can write to it.
Line 3 shows us extracting the entire directory of the system file in the flashable into the system file of our rom.
Line 4 shows we are setting permissions for one of the system files we just installed in the rom. In this case it is an INIT.D file.
Line 5 shows us returning the system to an un-writable state.
Line 6 shows we are now installing the other file called BOOT.IMG.
So we installed BOOT.IMG and the SYSTEM file. The BOOT.IMG file is usually only found in a rom or kernel zip so most of the time you won't see this file in a flashable but I wanted to use this as an example to show a bit about the kernel side of things.
Ok, so lets get back to the original files of this flashable zip. The updater script stated we installed a new system file into the rom so whats in there? If we open the SYSTEM file from our flashable with Root Explorer you will find a file hierarchy...
SYSTEM
-- ETC
--- INIT.D
---- "00LEANKERNEL"
-- LIB
--- MODULES
---- Listed here are a bunch of ".ko" modules and i'm not listing them all.
So whats the point of all this? Well lets say when we originally debloated our rom in the begining we could of included some of our flashable mods like a custom kernel before we zip the rom to test the base. So in this case we can manually install this kernel before we zip the base. We can take the BOOT.IMG from our extracted kernel and replace the BOOT.IMG in our extracted rom. We only need the files from the flashable so we need to copy and paste the "00LEANKERNEL" file from our flashable to our roms /system/etc/init.d folder. We can also take those ".ko" files from the flashable and dump those into the /system/lib/module folder and we are done. You have now manually installed a kernel into your base rom before you zipped it. Now when you zip your rom and flash it, your new base rom will boot with your custom kernel. Since we manually installed the kernel we don't need the META-INF file provides an auto install script for installing through recovery. Technically we could take all of our flashable mods, extract them, look at the file hierarchy and copy and paste the those files to our extracted base rom. That way we can zip our rom and test it with the mods right off the bat. You can really make things quicker this way and is in general the way to go.
I think it's rather important to fully understand a flashable zip. How it's built and how it completes it's task. It's used so often and makes mods so incredibly easy to install but it is also what installs our rom! One of the files we see when we open "slick" is a META-INF and there inside is the updater script to flash the rom. Again we are doing the same thing as we do with the flashable mod but this time we are installing a lot more files with a lot more permissions. It is the exact same thing as shown above just a bit more extensive.

7. PUT THE PIECES TOGETHER
Ok so we have our base rom running on our phone and possibly a few mods installed. We also have our extracted and debloated "slick" rom on the EXT-sdcard inside our project folder. The next part is rather easy if you understand how those flashable mods were installed. If you understand the whole flashable and its files, your better off just extracting them and then copy and paste them where they need to go. After you have all your mod files in place you can now zip your official "Slick" rom using Root Explorer of course. Prepare yourself for another 30 minutes for it to zip. After it's zipped your done. You have now created your first fully modded rom! However...
Lets say you don't get the whole flashable thing and or you had made some other changes to the rom while you were testing. Lets say you flashed some mods and created a few init.d scripts or the build.prop along the way. NO WORRIES! We can put the rom together another way. A lot of the mods you flash will install files in some usual areas of the rom like your Framework folder and such. Lets just say we don't know though. You can actually copy complete folders from the rom you are running right there and now and paste them into your extracted "Slick" base rom using Root Explorer. So you can take "/system/framework" from your currently running rom, copy it, and paste it in "/storage/EXT-sdcard/project folder/slick/system/framework". In short just take your copy of the framework file and put it in your extracted base and paste it. Root Explorer will then ask you if you want to replace this file and click yes. You have just transferred any modded file that might have been in framework to your extracted rom. Any folder you may think was modded, simply copy and paste it to your extracted base rom on your EXT-sdcard. Once you think you have it all the modded files transferred you can zip your new "Slick rom! Flash and enjoy!!

FINISHED
So we have now completed our own rom on the device itself. It's really not too difficult just a bit more time consuming with zipping and that. However, you may need to do a bit more research on how to decompile and recompile an APK. This is one of things that can really be a pain to setup. It's again the basics that will kill you. The whole PITA is not decompiling or making changes to a framework file, it's setting up the environment that sucked for me. You have to get the Java and files in order and all the little crap to get it to work. IMO, if you haven't decompiled an APK yet it's really not difficult at all. Like I said. It's the basics. I encourage you to learn this because it's so freakin easy after it's all setup and you will be able to do so much more with your rom. Once you get this APK thing down don't be afraid to take someone elses work and reverse engineer it. Try to figure out what that developer did to accomplish what he wanted. It's a great way to learn and thats what it's about.
I may add to this somewhere down the road but for now it's all I have. I hope this helped and motivated someone to create a rom and begin there journey to become developer someday! We can all use fresh ideas for development. There is so much more to come for Android so get your hands dirty and share!
Thanks guys!

Ha never really thought of doing this on the fly with my phone. Even though all the right stuff was sitting in my face thanks for opening my eyes razz1
Sent from my SCH-I535 using Tapatalk 4 Beta

dincdoes.me said:
Ha never really thought of doing this on the fly with my phone. Even though all the right stuff was sitting in my face thanks for opening my eyes razz1
Sent from my SCH-I535 using Tapatalk 4 Beta
Click to expand...
Click to collapse
It's another way. May not be the fastest way but it's another option. I also wanted to write this as a general rom creation and learning some basics. It's always the basics that will kill a project and motivation. I would like to see a complete newb to be able to complete a rom with this tutorial. Then I accomplished something. Going to have to finish this tomorrow though. It's taking longer than I thought lol.

Yea I mean I'm a newb at doing it from my phone if that counts =) .. What explorer do you like to use to repack the zips. I'm sure I'll try this method soon to play while bored at work. Rom tool box will help with boot animations, fonts and transition animations too take care thanks for giving our community some new skills I'm sure it will help out down the road.
Sent from my SCH-I535 using Tapatalk 4 Beta

Thank you for this post. This will definitely get me to try and make my own ROM the way I like, also I might just learn some new stuff. Great post thanks again
Sent from my SCH-I535 using xda app-developers app

Nice tutorial.
It's a great way to show what can be done just from your phone.
:good:

Right on man. Been waiting for this. Thank you.
Sent from my SCH-I535 using xda app-developers app

dincdoes.me said:
Yea I mean I'm a newb at doing it from my phone if that counts =) .. What explorer do you like to use to repack the zips. I'm sure I'll try this method soon to play while bored at work. Rom tool box will help with boot animations, fonts and transition animations too take care thanks for giving our community some new skills I'm sure it will help out down the road.
Sent from my SCH-I535 using Tapatalk 4 Beta
Click to expand...
Click to collapse
I use androzip man.
Sent from my SCH-I535 using xda app-developers app

More added

So would I make, say ROM manager a system app? Just copy the apk into the /System/App folder?

Evil Genius Jr. said:
So would I make, say ROM manager a system app? Just copy the apk into the /System/App folder?
Click to expand...
Click to collapse
Yes, but not all apps you download from google play work in /system/app. Some want to be installed into /data/app. However /data/app doesn't exist till after the rom is booted. You would need to add the folder to your extracted rom and modify the updater script.

razz1 said:
Yes, but not all apps you download from google play work in /system/app. Some want to be installed into /data/app. However /data/app doesn't exist till after the rom is booted. You would need to add the folder to your extracted rom and modify the updater script.
Click to expand...
Click to collapse
You are the fu**ing man razz1.
Sent from my SCH-I535 using xda app-developers app

That's about all I have for now. OP completed!:sly:

Hello. Ok so I created a ROM what I call MyTWGE (Tuchwiz Google Edition). Followed the instructions, unzipped the stock Verizon OS went into the -app- folder deleted all the Verizon, Samsung and Google apps (only the ones that are download able from Google Play). Replaced the stock launcher with the 5x6 version that I extracted from another zip, replaced the camera with the Google edition camera (download able from GP), replaced the keyboard with the Note2 keyboard (also unzipped from another zip). Looked around and deleted a few more files I found that were connected to some Samsung apps and zipped it up. Flashed the zip yesterday onto the phone and it's ALIVE working.
Thank you for your patience to write up all these instructions. I previously used TB to debloat my phone and that was it, learned a few thing thanks again
Sent from my SCH-I535 using xda app-developers app

Lehocki said:
Hello. Ok so I created a ROM what I call MyTWGE (Tuchwiz Google Edition). Followed the instructions, unzipped the stock Verizon OS went into the -app- folder deleted all the Verizon, Samsung and Google apps (only the ones that are download able from Google Play). Replaced the stock launcher with the 5x6 version that I extracted from another zip, replaced the camera with the Google edition camera (download able from GP), replaced the keyboard with the Note2 keyboard (also unzipped from another zip). Looked around and deleted a few more files I found that were connected to some Samsung apps and zipped it up. Flashed the zip yesterday onto the phone and it's ALIVE working.
Thank you for your patience to write up all these instructions. I previously used TB to debloat my phone and that was it, learned a few thing thanks again
Sent from my SCH-I535 using xda app-developers app
Click to expand...
Click to collapse
Lol the whole time I was reading this I was waiting for you to say something didn't work out for you but it all did I guess. Nice!!

Yeah running for the past 24h no problems everything works. Thanks
Sent from my SCH-I535 using xda app-developers app
---------- Post added at 02:24 AM ---------- Previous post was at 02:07 AM ----------
Only thing that that's annoying is the wifi in the taskbar. I read in one of the posts that I have to go into systemui and some other files within n delete lines 12 through 21 but that didn't work , am guessing I need to decompile systemui to do that. The person in the post didn't clarify and I'm not ready to do that yet. Reason is I don't know anything about programming or linux or decompiler or anything like that. Deleting files I can do replacing some sure. But I'm happy my first attempt to mix something together worked and I'll keep doing it till I actually figure out what it is that I am doing. Thanks again for the post
Sent from my SCH-I535 using xda app-developers app

Yea. Follow Didacts write ups to get you through it. It's all in framework res apk.