[MOD] Advanced Power Menu for JWR66Y - Nexus 4 Themes and Apps

UPDATE: I added screenshot to the power menu for anyone who is interested.
Hello all!
I recently saw a pretty cool advanced power menu mod for the Nexus 7 and really wanted it for our Nexus 4. Unfortunately, the developer did not have time to make a version for the Nexus 4. I modified the framework-res.apk and androidpolicy.jar from the zip on the Nexus 7 thread to work on the Nexus 4. The result is pretty close to the original mod and it looks great. I've only tested it on a stock deodexed JWR66Y build. This won't work on odex ROMs. If you have any modifications to your framework-res.apk or androidpolicy.jar this modification will overwrite your current one.
I personally like to use the stock ROM and having this advanced power menu is really nice. I just wanted to share this with everyone!
All credit goes to scrosler for his awesome mod so go give him some thanks on the original thread:
http://forum.xda-developers.com/showthread.php?t=2380413
Instructions:
1. Reboot to recovery
2. Mount system
3. Flash zip
4. Reboot
Enjoy!!
With "Screenshot" in the power menu:
https://dl.dropboxusercontent.com/u/43701045/APM - 4.3 - DE-ODEX -(With Screenshot).zip
Without "Screenshot" in the power menu:
https://dl.dropboxusercontent.com/u/43701045/APM - 4.3 - DE-ODEX - (Without Screenshot).zip

Could you make a version for stock/odex please?

I have this stock, deodexed JWR66Y rom installed,
http://forum.xda-developers.com/showthread.php?t=2010887
I'm trying to flash your mod. It appears to flash successfully in TWRP, but it is not working. Neither android.policy.jar or framework-res.apk are modified when I reboot after flashing this. I'm using ziddey's kernel based off franco's kernel, and there have been changes to framework-res.apk. Could that be the reason that nothing gets installed?
EDIT: I decided to manually install the 2 files, and that works fine. So I'm guessing that the mount command in the updater-script is incorrect? Did you actually get your zip file to install successfully on the Nexus 4? Or did you just install the files manually?
EDIT2: A couple of hours later, I changed the mount command in your updater-script (to be like one I have in another Nexus 4 update.zip), and it flashes just fine! But another person has reported that this works fine for him, so I'm very confused.
EDIT3: Well, here are my conclusions, some of which are the same as already described above. (I do know that I can use an app to get the advanced power menu, but I'm trying to figure out why this mod works for some but not for me).
1. Flashing this zip as-is does not install either file (android.policy.jar and framework-res.apk). I believe it's due to the mount.
2. Manually installing the 2 files DOES work, i.e. the advanced power menu displays when holding down the power button.
3. Changing the mount command in the updater-script DOES work.
original mount (fails?): mount("ext4", "EMMC", "/dev/block/platform/sdhci-tegra.3/by-name/APP", "/system");
modified mount (works): mount("ext4", "EMMC", "/dev/block/platform/msm_sdcc.1/by-name/system", "/system");
4. I found another mod for the advanced power menu which only modifies android.policy.jar and NOT framework-res.apk, and it DOES work. See this thread. http://forum.xda-developers.com/showthread.php?t=2383509
By the way, it has a completely different way of mounting, i.e. run_program("/sbin/busybox", "mount", "/system");
I'm hoping babalonius508 (or anyone else who says this mod is working) can help me figure out why the mount works for them and not for me!
EDIT4: I'm using TWRP. I booted into recovery and used ADB. I tried a mount similar to the "tegra" one that is in this mod's updater-script (see 3. above). It failed. Then I did one with the "sdcc" one (again, see 3. above). It worked.
So...does this have something to do with which recovery is used? I'm wondering if those who are failing to get this to install are running TWRP (like me), while those who are successful are running CWM. I could try installing CWM and test this myself, but it's late, and maybe some others can chime in here and see if I'm on the right track. Well, if I really think about it, I don't think recovery has anything to do with it. I don't see how this could possibly be working with that mount command. Anyone who has this working on the Nexus 4, please post here and tell me how!

random hero said:
Could you make a version for stock/odex please?
Click to expand...
Click to collapse
I'm searching stock / odex, too! Would be great! :good:

alfiriel said:
I'm searching stock / odex, too! Would be great! :good:
Click to expand...
Click to collapse
Here!
http://forum.xda-developers.com/showthread.php?t=2383509

Very useful . Thanks
Sent from my Nexus 4 using xda app-developers app

random hero said:
Could you make a version for stock/odex please?
Click to expand...
Click to collapse
alfiriel said:
I'm searching stock / odex, too! Would be great! :good:
Click to expand...
Click to collapse
I'll definitely try and do an odex version as soon as I can!

sga999 said:
I have this stock, deodexed JWR66Y rom installed,
http://forum.xda-developers.com/showthread.php?t=2010887
I'm trying to flash your mod. It appears to flash successfully in TWRP, but it is not working. Neither android.policy.jar or framework-res.apk are modified when I reboot after flashing this. I'm using ziddey's kernel based off franco's kernel, and there have been changes to framework-res.apk. Could that be the reason that nothing gets installed?
EDIT: I decided to manually install the 2 files, and that works fine. So I'm guessing that the mount command in the updater-script is incorrect? Did you actually get your zip file to install successfully on the Nexus 4? Or did you just install the files manually?
EDIT2: A couple of hours later, I changed the mount command in your updater-script (to be like one I have in another Nexus 4 update.zip), and it flashes just fine! But another person has reported that this works fine for him, so I'm very confused.
EDIT3: Well, here are my conclusions, some of which are the same as already described above. (I do know that I can use an app to get the advanced power menu, but I'm trying to figure out why this mod works for some but not for me).
1. Flashing this zip as-is does not install either file (android.policy.jar and framework-res.apk). I believe it's due to the mount.
2. Manually installing the 2 files DOES work, i.e. the advanced power menu displays when holding down the power button.
3. Changing the mount command in the updater-script DOES work.
original mount (fails?): mount("ext4", "EMMC", "/dev/block/platform/sdhci-tegra.3/by-name/APP", "/system");
modified mount (works): mount("ext4", "EMMC", "/dev/block/platform/msm_sdcc.1/by-name/system", "/system");
4. I found another mod for the advanced power menu which only modifies android.policy.jar and NOT framework-res.apk, and it DOES work. See this thread. http://forum.xda-developers.com/showthread.php?t=2383509
By the way, it has a completely different way of mounting, i.e. run_program("/sbin/busybox", "mount", "/system");
I'm hoping babalonius508 (or anyone else who says this mod is working) can help me figure out why the mount works for them and not for me!
EDIT4: I'm using TWRP. I booted into recovery and used ADB. I tried a mount similar to the "tegra" one that is in this mod's updater-script (see 3. above). It failed. Then I did one with the "sdcc" one (again, see 3. above). It worked.
So...does this have something to do with which recovery is used? I'm wondering if those who are failing to get this to install are running TWRP (like me), while those who are successful are running CWM. I could try installing CWM and test this myself, but it's late, and maybe some others can chime in here and see if I'm on the right track. Well, if I really think about it, I don't think recovery has anything to do with it. I don't see how this could possibly be working with that mount command. Anyone who has this working on the Nexus 4, please post here and tell me how!
Click to expand...
Click to collapse
I actually don't use TWRP so its hard for me to guide you on that because I have very little experience with it. When flashing this mod in ClockworkMod recovery, I simply mount system before I flash.
If all else fails just take the framework-res.apk and androidpolicy.jar out of the flashable zip, put it in system/framework, and change the permissions of both the files to rw-rw-r-- and reboot. Don't forget to make a backup of your current framework-res.apk and androidpolicy.jar. I hope you can get it working!

Not bad, i'll give a try!

babalonius508 said:
I actually don't use TWRP so its hard for me to guide you on that because I have very little experience with it. When flashing this mod in ClockworkMod recovery, I simply mount system before I flash.
If all else fails just take the framework-res.apk and androidpolicy.jar out of the flashable zip, put it in system/framework, and change the permissions of both the files to rw-rw-r-- and reboot. Don't forget to make a backup of your current framework-res.apk and androidpolicy.jar. I hope you can get it working!
Click to expand...
Click to collapse
If you look at my first EDIT comment, you'll see that I did do each part manually, and it worked fine. But the issue was how to get your zip file to work "as is", i.e. without issuing a mount command during recovery (whether CWM or TWRP). With other zip files that I flash, the mount is done correctly in the script. I've moved on to using Xposed with either GravityBox or Xblast, which means no more flashing.

Related

[MOD] Nexus S Gingerbread on Steam (with working keyboard)

Just to demonstrate the power of Steam, I hereby provide you a Steam Powered Gingerbread
This is based on SC's idea of using /data to store the gingerbread files, which works even if FSR is not loaded.
I also went forward and fixed the keyboard issue, so now the home, back and menu buttons work as expected! Oh, and also added recovery mode (running steam recovery of course ), that can be opened using the ususal three button combo. ("adb reboot recovery" or similar will not work however)
What still doesn't work:
- Wifi
- Modem (3g and phone)
- Camera
- Gps
Installation:
1. Download the system dump from here, and put the file on the root of your internal SD card
2. If not already on ext2 or ext4, convert your /data partition to ext4. (because the next step requires Steam Recovery, I'd go with Steam kernel, if your current one doesn't support ext on /data)
3. Download the afterburner install files from here
4. Create a steam directory on your internal sdcard, and put the previously downloaded file there. If there are other afterburner*.zip files there, delete them.
5. Enter Steam Recovery (there are multiple ooptions on how you can get it), choose afterburner, select both options, then press "Install". This will take a while. You might want to switch to log window 1, where you can see the /system extraction progress
6. After finished, reboot. Gingerbread will boot up.
7. If asked to install Steam kernel you can do so, but first read note.
8. Enjoy. To switch back, flash any kernel. If you want your old data back, flash a kernel with ext4 support.
9. If you switched back to a "normal" kernel, you can use afterburner to get back to gingerbread too. Only select the second option when running afterburner, and on the next reboot, gingerbread will greet you in a state as you've never left it.
Note: A steam kernel installation requires you to reboot into recovery after installing it. On base Galaxy S ROMs this is done automatically, but gingerbread's kernel lacks the commands needed to programmatically reboot into recovery. Therefore it will always reboot into normal android mode, where he finds out that he needs to reboot into recovery, but boots into normal mode, etc... to exit this loop simply reboot into recovery manually (using the three button combo), to finish installation of Steam Kernel. You will be greeted with the afterburner window, press back without selecting any of the options (they won't work anyway), and you're done.
Alternate install: Of course you don't need afterburner to install this. Simply follow the instructions on supercurio's page, but use the kernel found inside afterburner.zip, instead of the one provided on the mentioned thread. /data needs to be converted to ext4 though.
Source:
Steam Kernel: https://github.com/SteamMOD (all directories starting with android_bootable_steam_ / tag 2.9.9.1)
Fixed kernel: https://github.com/SteamMOD/steam_kernel_ns_on_galaxys
Initramfs: https://github.com/SteamMOD/steam_initramfs_galaxys/tree/master/ns-on-sgs-i9000
You can compile it by yourselves using the Android Compiler VM 2.0 with the compiler scripts found here
Not exactly following you on how to install the Steam Kernel. Do I need to pull the battery at some point? If so, when? If not, what am I supposed to to do manually get it into recovery mode? No matter what I do I am always greeted with "Steam doesn't seem to be installed, or it was recently uninstalled." etc.
Nice work, you lift up the level of this forum
Some x-mas beer for you :16T35690B39571910
This is awesome!
Happy x-mas
74W90842E13524051
Great job, will play with it ...
Thx a lot for your work ! -> 1VL15892XA210614G
you are awesome. just awesome.
i have a vibrant. But i lurk here to keep an eye on development.
Great very interesting indeed. May I know wats working and wats not? Thx and gd work!
Sent from my GT-I9000 using XDA App
Amazing. i will pay you the 2011 Sziget if that works. lol
Hmmmm nothing happens when I choose "Install" in afterburner menu.. It seems to be instant. Just like it didn't found the install file.
I named the folder "steam" at the root and put the afterburner.zip into it though..
Edit: Okay I'm f***** stupid, didn't check the two options. It works now.. really sorry
Edit2: It seems like I'm stuck in steam recovery. Everytime I reboot I get this message : "Partition /res/.fake/gingerbread/cache could not be mounted!"
The "format partition to ext4" function doesn't seem to work as well. Same for the proposition of installing Steam kernel..
I had my /data partition formatted in ext4 via voodoo though.
So basically, whatever choice I make, it'll never boot... Do I have any other solution than a flash with odin to get something working ?
huge work, and it works !
well done
Awsome, my Hungarian friend! It's not a slogan: you are really the best.
Sent from my GT-I9000 using Tapatalk
Can anyone report on what features work/ don't work. Will be real helpful for those willing to try it out. Thanks!
Ehm....ehm....but...what is Steam????
zat81 said:
Ehm....ehm....but...what is Steam????
Click to expand...
Click to collapse
steam is much more powerfull than CWM ... already intruduced in this forum ...
respect and nice work though
Yeah seems very nice. However I'm interested what's working and what not. Can please someone who already flasht this thing provide.me an answer?
Sent from my GT-I9000 using XDA App
Karupan said:
Can anyone report on what features work/ don't work. Will be real helpful for those willing to try it out. Thanks!
Click to expand...
Click to collapse
Ya would really like to know eagerly too
Sent from my GT-I9000 using XDA App
Is this a working gingerbread port with wifi,... ?
Sent from my GT-I9000 using Tapatalk
PhilAd said:
steam is much more powerfull than CWM ... already intruduced in this forum ...
respect and nice work though
Click to expand...
Click to collapse
Where can i read something about?
And what about a small vid like supercurio did, if it is possible ? would be very nice

[Q] Help with making a custom flashable zip

I am attempting to make a flashable zip that adds MIUI camera and a boot animation to CM7. Every time I attempt to flash my zip, I get 'Installation Aborted' with no other messages or errors. I am at a loss to what I've done wrong, and I think I signed it correctly.
I attached my file, any help would be appreciated.
I am also at a loss for what exactly the update-binary file is for, or how to go about getting one.
JetBomber117 said:
I am attempting to make a flashable zip that adds MIUI camera and a boot animation to CM7. Every time I attempt to flash my zip, I get 'Installation Aborted' with no other messages or errors. I am at a loss to what I've done wrong, and I think I signed it correctly.
I attached my file, any help would be appreciated.
I am also at a loss for what exactly the update-binary file is for, or how to go about getting one.
Click to expand...
Click to collapse
you can try changing
mount("MTD", "system", "/system");
to
mount("yaffs2", "MTD", "system", "/system");
take out the mounts and unmounts of data and cache...you don't need them. If it still fails you can do adb pull cache/recovery/log x (where x is location and name of where you want to save it)
the log will give you more detail of why it's failing but it's probably that line.
Now it is giving me an error 6. Lame. :/

[MOD] Hulu Hack GB/ICS 11.1.115.12

Ok guys, so I absolutely love Hulu and other legit TV sites, some of which prohibit mobile devices based on a "flash id" similar to what you have with a User Agent string for the browser. It is based on this ID that it prohibits mobile phones from accessing content such as hulu and HBO (I think?). With this mod your phone will appear as though it is a PC running flash and I believe it also modifies your version number to be something like 99.9.999.99 for sites that try and check the version number. I also must make sure to give credit where credit is due. Credit goes to imneveral0ne who posted the modified lib files in the Thunderbolt forums http://forum.xda-developers.com/show...6#post12433036.
His mod stopped working because Gingerbread (and 10.3) copies the lib files from the APK itself back into the lib folder (/data/data/com.adobe.flashplayer/lib/) on boot, thus require the mod be redone every reboot. I simply took his mod, wrote a simple script that installs the hacked lib files to /data/flash/ at first for storage, modifies permission of /data/data/com.adobe.flashplayer/lib/ so that it can be written to by the script, and also installs a "run on boot" script at /system/etc/init.d/01-fixflash.sh which will copy the hacked lib files from /data/flash to /data/data/com.adobe.flashplayer/lib/. It also adds Hulu Bookmark app (1.0) to /data/app.
REQUIREMENTS:
Kernel with init.d support (most custom kernels with root support) and root
Busybox (for running the copy commands. If you don’t have it, install ‘busybox installer’ from the market once you are rooted)
Root explorer (recommended, not required)
NOTE: I have developed this file FOR gingerbread.
INSTRUCTIONS:
Install latest flash player (11.1.115.12) from the market FIRST and be sure to uncheck automatic updates (and don't manually either)
Make sure busybox is installed. One way to test this is to type cp –help in ADB and see if it can run the command. If it does, you’re good to go.
Next, simply flash the zip. Wipe cache/dalvik if you want (I don't believe it's necessary, although again, this is my first time and for whatever reason the script doesn't seem to want to run on its own the first time)
Upon first reboot, you MAY be lucky enough that it simply just works and you’re all set.If you still get the “Hulu not available for your platform” error, simply use either root explorer or adb to run the script for the first time manually. In root explorer, navigate to /system/etc/init.d, tap on S98fixflash and select “execute”. In ADB, navigate to /system/etc/init.d and type ‘sh S98fixflash’. Wait a sec for it to run, then try Hulu again. It should be working immediately (without a reboot required) AND the script should then run correctly on subsequent reboots.
Like I said this is my first "product" I've been able to make available to the community and am more than open to suggestions, criticisms and ideas of how I can make this script better. Enjoy guys!
EDIT: If you do have issues with the script not running on every reboot, simply install "Script Manager" from the market, navigate to /system/etc/init.d, select S98fixflash and check the "run on boot" checkbox.
NOTE: ICS Only version now (least as far as I know). May work on others, please let me and others know if it does work on GB
File is now attached to post due to multiupload being unavailable -
UPDATE 6/26/2012 for 11.1.115.12
Note: after more feedback it seems using busybox installer from the market helps if running the script, even manually does nothing.
ahh too much to do
cba
Sorry, lots of explaining. If your rooted just update flash to latest in market, uncheck auto update adobe flash, then flash the zip. Should just work like it did on my gsII.
Sent from my GT-I9100 using XDA App
A query
I was going thru your update-script. What does this line do?
Code:
set_perm(0, 2000, 0755, "/system/etc/init.d/01-fixflash.sh");
I did not find a 01-fixflash.sh in /system/etc/init.d folder, only S98fixflash?
sileshn said:
I was going thru your update-script. What does this line do?
Code:
set_perm(0, 2000, 0755, "/system/etc/init.d/01-fixflash.sh");
I did not find a 01-fixflash.sh in /system/etc/init.d folder, only S98fixflash?
Click to expand...
Click to collapse
Oops, your right. Sorry I quickly modified this script from my old one I used on my epic and forgot to change that line. Will repair and repost now...
http://www.multiupload.com/VJWDKZ23FR
compuw22c said:
Oops, your right. Sorry I quickly modified this script from my old one I used on my epic and forgot to change that line. Will repair and repost now...
http://www.multiupload.com/VJWDKZ23FR
Click to expand...
Click to collapse
No problem. I already made the necessary changes. Will help others.
Sent from my GT-I9100 using Tapatalk
Cool. Also, it did work for you after those changes correct?
Sent from my SPH-D700 using XDA App
Note: after more feedback it seems using busybox installer from the market helps if running the script, even manually does nothing.
Sent from my GT-I9100 using XDA App
update 9/5/2011 for 10.3.186.6 AND hopefully fixed data mounting issues on certain devices so it works easily on CWM on more devices
NOTE: Latest update includes a brand new flashplayer.so files freshly edited, so no more issues with youtube in the browser, and uses TRUE flash 10.3.186.6 libraries for increased performance (no longer based on 10.2)
does nothing no matter what on kh3 deodexed
I'm using it now on litening 6.1 (kh3) just fine with nymphetamine kernel. This thread is also in the epic 4g forums. Troubleshooting instructions are there a well as the op. Understand what the mod does by reading, then find out where its getting hung up. I guarantee if you read you'll find your problem. Sorry but I keep having to help people read my own posts... First guesses, reflash, check to see files were installed, run busybox installer,.try another kernel with working init.d support... Run script manually?
Nice work. Any way of getting this to work for HC on the Xoom?
Maybe, try it let me know. Our buy me a 10.1
compuw22c said:
Maybe, try it let me know. Our buy me a 10.1
Click to expand...
Click to collapse
LOL! Nah didn't work for me.
Actually I feel I remember it working fire xoom.maybe try the manual troubleshooting in the op. find and replace libflashplayer.so with what's in the zip
it won't let me even flash the file says:
E: Error in /sdcard/gb_hack_flash_hulu10.3.186.6.zip
(Status 0)
Installation aborted.
all you need to do to get it to work is to extract the libflashplayer.so from the zip the op posted and copy it to (and replace) the libflashplayer.so in
Code:
/data/flash/libflashplayer.so
and
Code:
/data/data/com.adobe.flashplayer/lib/libplayerflash.so
do this using root explorer
this also enables crackle as well
there is no need to run a script
Beautiful, tried so many things in the past, and this works beautifully! Thanks!
Um, at the risk of sounding like a complete euro-dummy: What is Hulu, what does this hack do? Perhaps a bit of description in the first post?
ogdobber said:
all you need to do to get it to work is to extract the libflashplayer.so from the zip the op posted and copy it to (and replace) the libflashplayer.so in
Code:
/data/flash/libflashplayer.so
and
Code:
/data/data/com.adobe.flashplayer/lib/libplayerflash.so
do this using root explorer
this also enables crackle as well
there is no need to run a script
Click to expand...
Click to collapse
Yes but when you reboot with 2.3 or higher it replaces those files again back to stock.

[HowTo] Create your own custom rom using kitchen

Not my responsibility if you soft brick your phone.
What you need:
1.Kitchen by Dsixda http://forum.xda-developers.com/showthread.php?t=633246
2./system directory of your custom/stock rom.
3.Root access on phone
Root browser https://play.google.com/store/apps/...xLDEsImNvbS5qcnVtbXkucm9vdC5icm93c2VyZnJlZSJd
Root explorer https://play.google.com/store/apps/details?id=com.speedsoftware.rootexplorer&feature=search_result
5.Common sense and half an hour (MOST IMPORTANT)
Instructions:
(I presume that you have already installed Cygwin.)
GETTING SYSTEM FILES
1.Install your preferable Root file browser in your phone.
2.Open and look down for system folder in it.
3.Copy the whole folder on your sd card
OR
1.Open your favourite custom rom and copy the system files in there.I personally used creeds v2.5
(Use this method if you want to test it or you are a lazy kid like me!)
SETTING UP ROM
1.Open Cygwin and type "cd kitchen" and press enter
2.Type "./menu" in it. You will see a menu after that.
3.Go to Cygwin>>home>>user>>kitchen>>original_update
4.Make a folder there named as "WORKING_XXXXX" and put the /system files you obtained in it.
5.Go back to Cygwin and press 1.
6.Press enter once again and select the name of your working folder by pressing the number against it.
7.After this it will ask for naming another folder.Do as you want.
8.Now you have a working folder which is going to become your future rom. Select any options from the menu which you would like to have in your rom.(I have not tested all of them so there is a chance that some of them wont work).
BUILDING THE ROM
1.Press 99 to build the working folder.
2.Go for the interactive mode so press 1.
3.Zipalign them by pressing y. A wall of text would come but dont worry
4.Add updater-script. Again a hell lot of text
5.Press y again
6.Sign your rom by pressing y
7.Change the name of your rom by pressing y
8.Press Enter to finish!
9.Go to OUTPUT_ZIP and open the your rom and go in META-INF fodler.Over here you need to put the updater scripts which you want for your rom. I have tested the scripts from Creeds v2.5 and it installs perfectly. (This is not a necessary step because you can also install your rom with the original META-INF script.)
10.Copy the rom to your sdcard
11.Boot in cwm and wipedata+cache and then install your rom.(Have a backup in hand)
12.It should install perfectly cuz it booted properly in my 9/10 tests.
If you want to customise your rom then look below. It should be done before the building the rom.
UNDER CONSTRUCTION
MORE TO COME: TWEAKS,ICONS,ICS SETTINGS,USEFUL APPS and many other customizations.
DONT KNOW IF THEY WORK OR NOT. I AM STILL TESTING THEM.
Ok here is it for tweaking and making your rom beautiful.
Tweaking-
Use these links for init.d scripts. To install them open the zip files on your pc and drag the scripts in system>>etc>>init.d into the WORKING_XXXX folder.
http://forum.xda-developers.com/showthread.php?t=1491714- [email protected]
http://forum.xda-developers.com/showthread.php?t=1227269
http://forum.xda-developers.com/showthread.php?t=1353903
http://forum.xda-developers.com/showthread.php?t=991276
Icon Packs-
Open the links and install these packs through cwm.
http://forum.xda-developers.com/showthread.php?t=1553292 - Specifically for Galaxy Y
http://forum.xda-developers.com/showthread.php?t=824656- Supports all phones and has over 700+ packs!!
http://forum.xda-developers.com/showthread.php?t=1552767- 3D icons
ICS Settings Mod-
Follow the thread
http://forum.xda-developers.com/showthread.php?t=1576565
Now adding launchers: There are two ways 2 do this.
1.Remove touchwiz30.apk from your system>>app and replace it with the apk of your launcher.
2.Put your launcher.apk system>>app directory and flash it. http://www.mediafire.com/?kr1oc425451nzvy (Please thank here once of you use htis http://forum.xda-developers.com/showthread.php?t=1602200 its the source of script)
Adding lidroid 14 bar toggle
http://forum.xda-developers.com/showthread.php?t=1511307
Locker
http://forum.xda-developers.com/showthread.php?t=1403761
UOT kitchen for many customizations
http://galaxyygaming.blogspot.in/2012/03/uotdevelop-ur-own-themesmaking-ur-own.html
Bootanimation
http://forum.xda-developers.com/showthread.php?t=1602200
Useful Apps:
UNDER CONSTRUCTION
Will add new things as I discover them. I am forgetting alot of things right now.
Sent from my GT-S5360 using XDA
TROUBLESHOOTING
1. If you get problems in installing a rom then change your META-INF folder with this one :http://www.mediafire.com/?0g1m8cobnby046u
1A .Use the script above if you have integrated kernel in your rom.
1B. If you have a rom without kernel then remove these lines:
Code:
assert(package_extract_file("boot.img", "/tmp/boot.img"),
write_raw_image("/tmp/boot.img", "boot"),
delete("/tmp/boot.img"));
2. If there is a package error then extract the files of the rom and repack them using any compression software.
3. If rom installed correctly but stuck onto logo screen?? Then remove try removing kernel and flashing rom again.
4. If rom installed correctly but got onto bootloop then there could be many possibilities which could lead to this. If you want accurate cause of it then do a logcat.
5. If there are some apk's which are not working then check if you correctly modded them.
Most of the problems occur because of updater-script problems so before trying any of the troubleshooting try the first tip.If you face different problem then post below.
Sent from my GT-S5360 using XDA
Last one maybe.
Sent from my GT-S5360 using XDA
in case if dsixda's script didn't work (show error 7) we can follow these guide:
1. extract the rom.
2. open updater-script with notepad++
3.1 if we want install only the rom, without kernel. delete 'write_raw_image PACKAGE:boot.img BOOT:'
3.2 if we want install the kernel and the rom, replace 'write_raw_image PACKAGE:boot.img BOOT:' with
package_extract_file("bmlunlock", "bmlunlock");
package_extract_file("boot.img", "boot.img");
set_perm(0, 0, 0755, "bmlunlock");
mount("vfat", "/dev/block/mmcblk0p1", "/sdcard", "rw");
run_program("bmlunlock");
run_program("/system/bin/dd", "if=boot.img", "of=/dev/block/bml7");
4. save the file
5. rezip the rom
kurotsugi said:
in case if dsixda's script didn't work (show error 7) we can follow these guide:
1. extract the rom.
2. open updater-script with notepad++
3.1 if we want install only the rom, without kernel. delete 'write_raw_image PACKAGE:boot.img BOOT:'
3.2 if we want install the kernel and the rom, replace 'write_raw_image PACKAGE:boot.img BOOT:' with
package_extract_file("bmlunlock", "bmlunlock");
package_extract_file("boot.img", "boot.img");
set_perm(0, 0, 0755, "bmlunlock");
mount("vfat", "/dev/block/mmcblk0p1", "/sdcard", "rw");
run_program("bmlunlock");
run_program("/system/bin/dd", "if=boot.img", "of=/dev/block/bml7");
4. save the file
5. rezip the rom
Click to expand...
Click to collapse
No chance of that error because I am not using any kernel (boot.img) in my rom.
well...you didn't need that but someone may want to install another kernel in their rom.
kurotsugi said:
well...you didn't need that but someone may want to install another kernel in their rom.
Click to expand...
Click to collapse
hmm.. ur right
btw, you can add another method to get system folder. in case if we dont have rootex we can get it from a nandroid backup. we can copy system.rfs.tar from the backup folder to original_update then use kitchen to extract it.
kurotsugi said:
btw, you can add another method to get system folder. in case if we dont have rootex we can get it from a nandroid backup. we can copy system.rfs.tar from the backup folder to original_update then use kitchen to extract it.
Click to expand...
Click to collapse
I hav not tried it so cant assure it yet
it is an exact copy of system partition. i made my rom in this way. you may test it if you want
sir can you update this? been waiting..by the way...have you created your custom rom already?
devion14 said:
sir can you update this? been waiting..by the way...have you created your custom rom already?
Click to expand...
Click to collapse
its already complete for basic cooking. I'm sure it will work. do you need another spesific information?
about this one?
MORE TO COME: TWEAKS,ICONS,ICS SETTINGS,USEFUL APPS and many other customizations.
will it be the same with your tut sir?
nope...I already put all I want on my post. there are several things that should be learned by ourself. I want my guide as easy as possible to be followed. I think its already too long to be called 'simple' guide (lol)
ok..thanks....by the way is there any offline uot kitchen or theming kitchen?
theming is not as difficult as you think. create our own theme is sure fun. I think you should give it a shot.
devion14 said:
sir can you update this? been waiting..by the way...have you created your custom rom already?
Click to expand...
Click to collapse
I will update this post tomorrow and yes I have created my own custom rom using this but its only for my friends presently ... u can also use kurotsugi's thread for some customization too...
will be waiting....
devion14 said:
will be waiting....
Click to expand...
Click to collapse
Updated it... There isnt a step by step tut cuz i dont hav much time(exams are near) and the threads are pretty much self explanatory. I will add many more, I just made this in a hurry.

CWM and TWRP

Just curious. Will CWM will completely placed by TWRP nowadays?
I personally use CWM since the first time i use android. And now i saw on many forums, most of the custom Roms used TWRP to flash.
Are all the devs (and their roms) use only TWRP since now? Or are CWM still can be use to flash the roms too?
What? Use what you like, both should work just fine.
I thought some of the devs made and will make the roms only compatible with TWRP only. Thanks if they're not
alph0 said:
I thought some of the devs made and will make the roms only compatible with TWRP only. Thanks if they're not
Click to expand...
Click to collapse
It's my understanding that almost any rom will flash in any recovery. There are probably exceptions but this is what I've found to be the case most of the time.
Sent from my ThunderBolt using xda app-developers app
alph0 said:
I thought some of the devs made and will make the roms only compatible with TWRP only. Thanks if they're not
Click to expand...
Click to collapse
The ROMs are compatible with either recovery, but the OTA updating apps are not. Some newer ROMs use GooManager for OTA updates:
https://play.google.com/store/apps/details?id=com.s0up.goomanager&hl=en
...and this requires TWRP to automatically flash ROM updates.
Many older ROMs use ROM Manager for updates:
https://play.google.com/store/apps/details?id=com.koushikdutta.rommanager&hl=en
...and this requires CWM to flash ROMs from within the app.
Any recovery should flash any ROM (the newer versions of TWRP may have trouble with older ROMs due to those having outdated installer binaries), but if you use ROM Manager or GooManager to flash ROMS, you need the recovery that is compatible with the app.
Goo manager needs TWRP to OTA update. I switched from CWM to TWRP and I like TWRP better. IT has a much better interface, scrollable on the touch screen and the backups are compressible.
I tried twrp and could not get it to install a kernel zip. Kept giving an error.
Sent from my ADR6300 using xda premium
normanx said:
I tried twrp and could not get it to install a kernel zip. Kept giving an error.
Sent from my ADR6300 using xda premium
Click to expand...
Click to collapse
Probably because of...
musical_chairs said:
Any recovery should flash any ROM (the newer versions of TWRP may have trouble with older ROMs due to those having outdated installer binaries)
Click to expand...
Click to collapse
So you'll have to get with your kernel dev to update his update-binary.
It is pretty easy to update the files your self. Just open the flashables zip with a zip program like 7zip. Navigate to META-INF/com/google/android. Replace the update-binary in the zip with this one http://dinc.does-it.net/Recoveries/TWRP_2.3.1.0/update-binary compatible with twrp 2.3+.
With the updated binary comes some new coding in the updater-script also. Open the updater-script with a good text editor like Text Pad, do not use notepad or wordpad. Look for mount and format commands that look like this:
Code:
format("MTD", "system", "/system");
mount("MTD", "system", "/system");
format("MTD", "cache", "/cache");
And change them to look like this:
Code:
format("yaffs2", "MTD", "system", "0", "/system");
mount("yaffs2", "MTD", "system", "/system");
format("ext4", "MTD", "cache", "0", "/cache");
The above is just an example of the formating required for the new binary. Your roms updater-script may have other lines which format or mount other partitions than those listed. Format has 5 arguments "file system of partition - MTD - partition name - 0 - and mount point". Mount has 4 arguments "file system of partition - MTD - partition name - mount point".
If your decent with reading coding and have a little time its not to dificult to accomplish.
If anyone who cant figure it out is interested, i will start a new post in general where i will update your flashable for you. I know a lot of the roms kernels and flashables around arent really supported by their devs anymore, but are still used.
FYI. All flashable files on dinc.does-it.net are now twrp 2.3+ compatible.

Categories

Resources