Related
Good evening dev community, I'm trying to create a flashable .zip that will replace the wpa_supplicant file with one that can connect to Ad-hoc networks. Replacing the file is actually really easy to do but I want to make a flashable .zip for others who don't want to mess with root explorer or ADB.
I have taken a .zip that works for the CWM 2.x for my phone but that won't flash on the xoom because CWM 3.x doesn't support the amend language so I converted it using amend2edify by nubecoder and I was so excited when it seemed to work but it will look like it's flashing and not actually do anything.
I was wondering it someone who knows more than me might want to lend a hand.
Please take a look and see if you can see anything wrong with my updater-script
Here is what I have so far. (see attachment)
Disclaimer: I got bored with not getting anywhere so I changed some of the display text so it's goofy so try to ignore that.
You shouldn't need to be afraid to flash it, it's harmless... that's the problem.
But as always you do so at your own risk.
Bump?
Sent from my Xoom using Tapatalk
Take a look at this thread. There is a link to a generic update script that works on the xoom. Just put your file in the right folder / subfolder and you should be good to go.
http://forum.xda-developers.com/showthread.php?t=1041205
I'll take a look at it. Thanks.
Sent from my Xoom using Tapatalk
Thanks for the help. It's exactly what I needed. I put a thank you in my new thread on this http://forum.xda-developers.com/showthread.php?t=1106130.
Do you know where I can get the wpa_supplicant file that will work with my Toshiba Thrive Tablet running Android Stock ROM 3.1? Thanks!
I've created a few mods in the Kitchen for the Unity Rom and have a couple things I need help on. I flash the zip and part of the mods work but not all of them. I changed the battery but it only changes on my phone when I charge it. I used the 1.24 Rom they have listed and I have 1,25. Could this be causing an issue or am i doing something wrong.
louslugger15 said:
I've created a few mods in the Kitchen for the Unity Rom and have a couple things I need help on. I flash the zip and part of the mods work but not all of them. I changed the battery but it only changes on my phone when I charge it. I used the 1.24 Rom they have listed and I have 1,25. Could this be causing an issue or am i doing something wrong.
Click to expand...
Click to collapse
Instead of choosing the rom from the list, just upload a copy of your framework-res.apk and the systemUI.apk. That takes away some of the guesswork. Also add the com.htc.resources.apk if you are running a sense rom.
louslugger15 said:
I've created a few mods in the Kitchen for the Unity Rom and have a couple things I need help on. I flash the zip and part of the mods work but not all of them. I changed the battery but it only changes on my phone when I charge it. I used the 1.24 Rom they have listed and I have 1,25. Could this be causing an issue or am i doing something wrong.
Click to expand...
Click to collapse
It could be.
Whenever I have trouble with the UOT Kitchen...I upload my own files instead of using the files they have.
Try uploading your own framework-res.apk and systemui.apk. I think if its a Gingerbread sense ROM you also have one more file you have to upload.
From the UOT Kitchen How To:
Files you need to upload:
Froyo rom: framework-res.apk
Gingerbread rom: framework-res.apk and SystemUI.apk
Gingerbread with sense rom: framework-res.apk, SystemUI.apk and com.htc.resources.apk
Cyanogenmod7 rom: Cyanbread.apk or Androidian.apk or any theme for ThemeChooser (rename as you like it to apear in theme menu)
How do I upload these files. I'm still somewhat new to this.
louslugger15 said:
How do I upload these files. I'm still somewhat new to this.
Click to expand...
Click to collapse
download Root Explorer or File Expert from the Market (I personally use File Expert...its a free app...does everything Root Explorer does). Navigate to your Root directory...thats where you will find these files. When you find them...copy and paste them to your desktop. That way when you get to that point with the Kitchen, you can easily find them to upload.
I had the same problem. You need to disable the battery percentages in the build.prop file. See the OP and then reboot. Problem solved.
Sent from my Inspire 4G using XDA App
Hello Guys,
still fairly new to flashing so far i am running the unleashed rom and loving all the features and looks that come with it. I just ran into Mins synergy rom and like what im seeing with all the progress guys have made from the beta testers. i have just downloaded the rom and had one question for you guys before i started the flash process. i know when i got the Unleashed rom it was in Zip form and would use that file to flash the rom. Now this Syneregy rom is not one zip file but one file with many files within it. would i just flash the rom from the main Folder or did i download the wrong file?
What is the .extention of the file you have now?
Did you accidently unzip the file? Try downloading the file again. As far as I know all roms are in 1 flashable zip.
Sent from Gerard Butler
doesnt rom manager do all the work for u after u download the files whether its .zip or already extracted?
DON'N unzip anything just put the zip on your sdcard and flash it through amonra or cwm.
...
Hey guys thanks for the responses. i actually went in and checked the file. ended up downloading again and actually got the zip file this time and flashing had no problem. looks like last time i had the actual file and not the zip. Im running the Synergy and enjoying the look of my EVO 4G now. going thru it now to see what bugs/ hiccups im going thru so far. are you guys running into any?
I have been searching on xda for some time now and here is a question. I am looking to change my bootanimation on the s3 as I am not happy with the verizon animation. When I had the droid bionic, all I had to do was change the name of the animation in system/media and place the new one and change accordingly. I saw two posts in here that did not exactly answer the question completely. If I flash an animation with cwm do I need to rename or move anything in system/media beforehand? Can the animation be extracted and just placed in the system/media folder? What is the best way to do this? I am rooted, stock with frozen bloat and some inverted gapps.
If you are rooted, you can use ROM Manager to change your boot animation quickly.
I have tried with rom toolbox however it did not work and I believe it mentioned something in rom toolbox about how it will not change if samsung uses a qmg format. Basically, I am asking for directions on how to change the boot animation once I have the new bootanimation.zip on my sd card. Is it even possible on the stock rooted s3?
I just used rom toolbox, found the one I wanted and installed it. Then went to recovery and flashed it, it showed an error, but I just left it alone and rebooted, and now I have a dancing droid! I would also recommend buying the full version so you can use the randomizer, its a fun feature.
hotnvicious5 said:
I just used rom toolbox, found the one I wanted and installed it. Then went to recovery and flashed it, it showed an error, but I just left it alone and rebooted, and now I have a dancing droid! I would also recommend buying the full version so you can use the randomizer, its a fun feature.
Click to expand...
Click to collapse
I have the full version but changing the boot animation definitely does not work on a rooted stock ROM setup.
The bootanimation.zip support is dependent on a custom kernel on Samsung devices. In stock form only .qmg format will play. No one to this point can edit or create .qmg files, they are proprietary to Samsung devices and their Bada OS. If you want to change it you will need to flash imnuts' lean kernel (assuming you are stock rooted as it is a touchwiz kernel). On a side note i personally think the boot animation from the droid charge is pretty BA and is floating around the net in .qmg format, don't know if it would work or not though due to differences in screen resolution. Here it is if you want to give it a try, just unzip and rename/paste the files where they need to go. It also has audio, place in system/media/audio/ui.
http://db.tt/spY4QX4p
Like i said,i have no clue if it will actually work or not but you could try ..... or just flash the kernel and use whatever lol. It's not my fault if it breaks stuff. Sorry for the long winded answer.
Sent from my Galaxy S III using Xda Premium
Thank you. I just changed the animation to the stock Samsung one that I believe came on the i9300. Nothing special, but it is 100 times better than that Verizon boot animation.
Did you flash the zip file in recovery? If you use the randomizer I don't think you have to flash the zip though.
Sent from my VZW Galaxy S3
elreydenj said:
Thank you. I just changed the animation to the stock Samsung one that I believe came on the i9300. Nothing special, but it is 100 times better than that Verizon boot animation.
Click to expand...
Click to collapse
I did the same thing. I also swapped the PowerOn.ogg and PowerOff.ogg files for files with no sounds so the boot up and shutdown are now quiet. The replacement audio files may be found in this thread.
hesh.monster said:
The bootanimation.zip support is dependent on a custom kernel on Samsung devices. In stock form only .qmg format will play. No one to this point can edit or create .qmg files, they are proprietary to Samsung devices and their Bada OS. If you want to change it you will need to flash imnuts' lean kernel (assuming you are stock rooted as it is a touchwiz kernel). On a side note i personally think the boot animation from the droid charge is pretty BA and is floating around the net in .qmg format, don't know if it would work or not though due to differences in screen resolution. Here it is if you want to give it a try, just unzip and rename/paste the files where they need to go. It also has audio, place in system/media/audio/ui.
http://db.tt/spY4QX4p
Like i said,i have no clue if it will actually work or not but you could try ..... or just flash the kernel and use whatever lol. It's not my fault if it breaks stuff. Sorry for the long winded answer.
Sent from my Galaxy S III using Xda Premium
Click to expand...
Click to collapse
You can edit the .qmg files. You have to use Samsung's Theme Designer to view the .pngs. From there, you can edit the bootanimation how you like.
can the png sequence be extracted now? I wrote off using the theme designer a long time ago because i could not extract them
Sent from my Galaxy S III using Xda Premium
elreydenj said:
Thank you. I just changed the animation to the stock Samsung one that I believe came on the i9300. Nothing special, but it is 100 times better than that Verizon boot animation.
Click to expand...
Click to collapse
Do you have a link for this file?
http://forum.xda-developers.com/showthread.php?t=1835143
Google my friend...it was the first search result. The instructions are in the OP at the link.
Sent from my Galaxy S III using Xda Premium
hesh.monster said:
http://forum.xda-developers.com/showthread.php?t=1835143
Google my friend...it was the first search result. The instructions are in the OP at the link.
Sent from my Galaxy S III using Xda Premium
Click to expand...
Click to collapse
I presumed that if elreyden was able to change the animation to the i9300 stock one, that I should be able to do it also. The animation that he refers to won't work with a stock rom (contains jpg, not qmg files), hence my confusion. I thought I must have had found the wrong link.
michael* said:
I presumed that if elreyden was able to change the animation to the i9300 stock one, that I should be able to do it also. The animation that he refers to won't work with a stock rom (contains jpg, not qmg files), hence my confusion. I thought I must have had found the wrong link.
Click to expand...
Click to collapse
Not sure what your particular situation is, but try putting the bootanimation.zip (not a flashable file. If you have one of those, extract the bootanimation.zip) to /data/local/ instead.
Tried it and it didn't work. I've given up - there doesn't seem to be a solution for stock rom. I will wait and probably flash a rom when they've had a chance to get solid.
michael* said:
Tried it and it didn't work. I've given up - there doesn't seem to be a solution for stock rom. I will wait and probably flash a rom when they've had a chance to get solid.
Click to expand...
Click to collapse
I'm on a stock rom and changed my VZW animation to the I9300 w/o any real problem, other than locating the qmg files. I've included to 2 files that I used in the attached zip so you should have it pretty easy To use them simply extract the files and put them into the /system/media folder using Root Explorer or whatever root based file utility you prefer. I simply renamed my existing versions and then copied these into the folder and made sure the permissions were the same. Once done I rebooted and the VZW version was nowhere to be seen.
It's also possible to replace the audio files. I wound up using "empty" files so I no longer have to listen to startup/shutdown sounds either. :good:
ETA: Here's the link to the thread with the silent startup & shutdown sounds. Scroll down to post #9.
http://forum.xda-developers.com/showthread.php?t=1801554
tgmorris said:
I'm on a stock rom and changed my VZW animation to the I9300 w/o any real problem, other than locating the qmg files. I've included to 2 files that I used in the attached zip so you should have it pretty easy To use them simply extract the files and put them into the /system/media folder using Root Explorer or whatever root based file utility you prefer. I simply renamed my existing versions and then copied these into the folder and made sure the permissions were the same. Once done I rebooted and the VZW version was nowhere to be seen.
It's also possible to replace the audio files. I wound up using "empty" files so I no longer have to listen to startup/shutdown sounds either. :good:
ETA: Here's the link to the thread with the silent startup & shutdown sounds. Scroll down to post #9.
http://forum.xda-developers.com/showthread.php?t=1801554
Click to expand...
Click to collapse
Thank you. I did this last week and it worked great. Stock Samsung bootanimation is less annoying than the Verizon 4glte one.
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.