Develop Bugs

[Q] How to make CWM 3.1.0.1 (Purple) flashable zip

Ok guys, I'm trying to make a zip of a mod I did to fix hulu on flash 10.3 on gingerbread, but I can't get the zip to be flashable. I'm on the purple cwm 3.1.0.1, I tried the android customization tools to build an empty zip, copied that to my Ubuntu partition so the permissions stick, added the appropriate files into the zip, but I get an error whenever I try to flash:
E: Error in /sdcard/gbflash.zip
(Status 0)
Installation aborted.
Any ideas? Or maybe I need a newer "blank" zip? If anyone can provide I'd be most appreciative
EDIT: I've attached my NON-WORKING zip file so that maybe some kind person might be able to see what the issue is.

Really? Nobody? Just trying to share my mods with the community, sure could use a little help

compuw22c said:
Really? Nobody? Just trying to share my mods with the community, sure could use a little help
Click to expand...
Click to collapse
Try mounting like this instead?
Code:
run_program("/sbin/mount", "/dev/block/stl9", "/system");
run_program("/sbin/mount", "/dev/block/stl10", "/data");
run_program("/sbin/mount", "/dev/block/stl11", "/cache");
If all else fails, try using an existing CWM flash-able as a skeleton for your work. That's what I do.

Cool, thanks for the advice. Will try, hopefully I'll have something to share soon!

Would it be possible to root my sg2 USCC version of Epic4gtouch.

I was looking at the auto root for FB15 and was wanting to know if it would work for my phone, Android version: 2.3.6, Baseband: S:R760.01 K.FB14. Any help is greatly appreciated.
Sent from my SCH-R760 using Tapatalk

^^ Second this. Just got SCH-R760 (SGS II) from USCC, there is currently ZERO support. Thanks!

I've tried the ek02 autoroot three times and it's not able to push the files. SuperOneClick didn't work either.
Sent from my SCH-R760 using xda premium

themac79 said:
I was looking at the auto root for FB15 and was wanting to know if it would work for my phone, Android version: 2.3.6, Baseband: S:R760.01 K.FB14. Any help is greatly appreciated.
Sent from my SCH-R760 using Tapatalk
Click to expand...
Click to collapse
The fb15 on this phone is ics so not going to work on your GB ROM .....maybe steady Hawkin can make you a kernel to root it with Odin ....all you have to do is ask him he may do it
He may port cwm for you too don't hurt to ask
Sent from my SPH-D710 using xda premium

Epix4G said:
The fb15 on this phone is ics so not going to work on your GB ROM .....maybe steady Hawkin can make you a kernel to root it with Odin ....all you have to do is ask him he may do it
He may port cwm for you too don't hurt to ask
Sent from my SPH-D710 using xda premium
Click to expand...
Click to collapse
That would be great! Thanks for the advice, really appreciate it.

not working
from what I hear zergrush no longer works in 2.3.6. I tried manually installing but it fails on the USCC GS2 (SCH-R760)
[+] Found a GingerBread ! 0x00000118
[+] Found a Samsung, running Samsung mode
[*] Scooting ...
[*] Sleeping a bit (~40s)...
[*] Waking !
[*] Sending 149 zerglings ...
[*] Sleeping a bit (~40s)...
[*] Waking !
[*] Sending 189 zerglings ...
[-] Hellions with BLUE flames !

mostly working
So I tried it with my SCH-R760 SGS2 I was able to get root boot recovery. Having the FB14 kernel would make this a snap however the Epic 4g Touch is so close it mostly worked. I seem to have intermittent wifi problems but everything else appears to work without issue.
I got the kernel from step two WISHLINK:wiki.rootzwiki.com/index.php/Samsung_Epic_4G_Touch or directly WISHLINK:goo-inside.me/epic4gtouch/kernel/acs-eb30-clockwork-epic-touch-4g-sep-20-4-00-pm.tar
I tried sweet talking USCC, evidently I'm not as charming as I think I am they told me I'm screwed and don't yet have the re-image. However, the above has the phone working and rooted minus a few problems with wifi.
Good luck.

Margey said:
So I tried it with my SCH-R760 SGS2 I was able to get root boot recovery. Having the FB14 kernel would make this a snap however the Epic 4g Touch is so close it mostly worked. I seem to have intermittent wifi problems but everything else appears to work without issue.
I got the kernel from step two WISHLINK:wiki.rootzwiki.com/index.php/Samsung_Epic_4G_Touch or directly WISHLINK:goo-inside.me/epic4gtouch/kernel/acs-eb30-clockwork-epic-touch-4g-sep-20-4-00-pm.tar
I tried sweet talking USCC, evidently I'm not as charming as I think I am they told me I'm screwed and don't yet have the re-image. However, the above has the phone working and rooted minus a few problems with wifi.
Good luck.
Click to expand...
Click to collapse
If you can get the E4GT kernel to boot on your phone then just use it to install su onto your ROM (/system), then put back your original USCC kernel and you'll be rooted with everything working.
So basically if your adb shell has a "#" prompt, you can just use Auto Root Option A on your phone and install root onto your phone's ROM. Just ignore the zergrush status, even though it fails, the script is still smart enough to install root onto your rom in your situation.
Then to get your original kernel back, figure out which partition has the recovery.bin, which is an unused mirror of your original kernel/zImage.
In the case of E4GT, this is partition /dev/block/mmcblk0p6
To get the mirror of your zImage type the following in adb shell
Code:
cd /sdcard
dd if=/dev/block/mmcblk0p6 of=zImage bs=256 count=32765
Now it is very important that the partition you chose above is really the recovery.bin partition, otherwise the file you just created will essentially be junk and won't allow you to boot your phone (ie *IF* you installed it, your phone *would not boot*)
Assuming you had the correct partition, to install it as your running kernel, you can do
Code:
cd /sdcard
dd if=zImage of=/dev/block/mmcblk0p5 bs=256 count=32765
Please don't go jumping into this unless you fully understand what I suggested.
YOU CAN MAKE YOUR PHONE UNBOOTABLE IF YOU DO THINGS WRONG.
I don't have your phone and the partitions could be different, so I'm depending on you to figure out if things don't make sense.
If you are unsure, ask questions before doing anything.

While I'm just understanding partitions and the like I'm able to follow your instructions but the *IF* parts I'd like to question.
I have:
/dev/block/mmcblk0p6
and
/dev/block/mmcblk0p5
I'm not sure how this correlates to the recovery.bin unless it is apart of one of those files. So for the SCH-R760 with FB14 I'd be looking for how to verify this. I can easily run the suggested lines and looks like everything is there. However to get this far it's been several hours and I'm a bit gun shy as I have to work tomorrow and actually need my phone. Again thank you for the suggestions and help. I'm very close. Everything but wifi is working and very well.

did anyone try flashing the cwm from the touch. it should work because the mount points line up the same. if so i can finish the ics rom and give it to who ever is willing to try
---------- Post added at 09:13 PM ---------- Previous post was at 08:56 PM ----------
sfhub said:
If you can get the E4GT kernel to boot on your phone then just use it to install su onto your ROM (/system), then put back your original USCC kernel and you'll be rooted with everything working.
So basically if your adb shell has a "#" prompt, you can just use Auto Root Option A on your phone and install root onto your phone's ROM. Just ignore the zergrush status, even though it fails, the script is still smart enough to install root onto your rom in your situation.
Then to get your original kernel back, figure out which partition has the recovery.bin, which is an unused mirror of your original kernel/zImage.
In the case of E4GT, this is partition /dev/block/mmcblk0p6
To get the mirror of your zImage type the following in adb shell
Code:
cd /sdcard
dd if=/dev/block/mmcblk0p6 of=zImage bs=256 count=32765
Now it is very important that the partition you chose above is really the recovery.bin partition, otherwise the file you just created will essentially be junk and won't allow you to boot your phone (ie *IF* you installed it, your phone *would not boot*)
Assuming you had the correct partition, to install it as your running kernel, you can do
Code:
cd /sdcard
dd if=zImage of=/dev/block/mmcblk0p5 bs=256 count=32765
Please don't go jumping into this unless you fully understand what I suggested.
YOU CAN MAKE YOUR PHONE UNBOOTABLE IF YOU DO THINGS WRONG.
I don't have your phone and the partitions could be different, so I'm depending on you to figure out if things don't make sense.
If you are unsure, ask questions before doing anything.
Click to expand...
Click to collapse
Here is a mount print out of the sgs2 from uscc that i had someone give me.
http://pastebin.com/k0nXEcKt
---------- Post added at 09:19 PM ---------- Previous post was at 09:13 PM ----------
Can't they just odin flash or heimdall flash the kernel/recovery in, that would be easier, then they truly don't have to root the rom first.

ironfisted said:
Can't they just odin flash or heimdall flash the kernel/recovery in, that would be easier, then they truly don't have to root the rom first.
Click to expand...
Click to collapse
They already did that. That is why they have rooted adb through the kernel. The issue is they are using an Epic 4G Touch kernel which causes some things to not work on their phone. I am suggesting they install their root functionality in the ROM and restore their original USCC kernel/zImage.
Since (according to them) they don't have a package to return to stock, basically they don't have a kernel/zImage to flash in ODIN because it was never provided to them.
Their original kernel/zImage is gone because they flashed over it (presumably before backing it up). That is why I gave them instructions to pull the backup kernel/zImage. Once they do that, whether they install that zImage within Android or through ODIN is not really important. The important part is they get the correct partition to use to pull the backup from so that they have a valid kernel/zImage to flash.
---------- Post added at 09:55 PM ---------- Previous post was at 09:42 PM ----------
Margey said:
While I'm just understanding partitions and the like I'm able to follow your instructions but the *IF* parts I'd like to question.
I have:
/dev/block/mmcblk0p6
and
/dev/block/mmcblk0p5
I'm not sure how this correlates to the recovery.bin unless it is apart of one of those files. So for the SCH-R760 with FB14 I'd be looking for how to verify this. I can easily run the suggested lines and looks like everything is there. However to get this far it's been several hours and I'm a bit gun shy as I have to work tomorrow and actually need my phone. Again thank you for the suggestions and help. I'm very close. Everything but wifi is working and very well.
Click to expand...
Click to collapse
Based on the previous pastebin that was posted it looks like the partitions on the USCC GS2 line up with the Sprint E4GT so it should be safe to run what I suggested.
Both /dev/block/mmcblk0p5 and /dev/block/mmcblk0p6 are linux device files that map to partitions in your phone's EMMC memory.
mmcblk0p5 is labeled zImage (on Sprint) and mmcblk0p6 is labeled recovery.bin (on Sprint). They have the exact same contents. zImage is the kernel and recovery for your phone.
recovery.bin is not being used (on Sprint) so it basically ends up being a backup of your zImage/kernel. Since you overwrote your USCC zImage with the Sprint E4GT zImage (presumably before backing it up) you cannot recover the original from your phone using the partition assigned to zImage.
I am suggesting you retrieve your original zImage from what is essentially a backup in the partition labeled recovery.bin (mmcblk0p6). This can then be installed in your zImage partition (mmcblk0p5) either directly through Android or through ODIN.
Once you create the zImage file as above, keep a copy off your phone on your PC just in case.
The whole purpose of putting back your original USCC zImage/kernel is so all the features work again, but since your root was achieved through the kernel, putting back the original zImage/kernel would cause you to lose root. That is why I suggested, prior to putting back the original USCC kernel, you install persistent root inside your ROM (ie /system)
You can do that by running Auto Root - Option A and ignoring the Blue Hellions error. If your adb is rooted as you described above, Auto Root will still install persistent root in your ROM despite the failure of the zergrush exploit. Once you install the persistent root in your ROM, you can restore the original USCC kernel/zImage and still have root for your applications. You can confirm that Auto Root - Option A did its job by typing:
Code:
ls -l /system/xbin/su
and verifying su is there and it has the proper permissions. If you are unsure, post the output and I can confirm.

What didn't work? maybe its a matter of the rom difference that makes stuff not work. Just an idea. I was thinking of porting the ics rom over to the sgs2 for them.

ironfisted said:
What didn't work? maybe its a matter of the rom difference that makes stuff not work. Just an idea. I was thinking of porting the ics rom over to the sgs2 for them.
Click to expand...
Click to collapse
As mentioned by Margey's post, the wifi wasn't working well. wifi drivers are in the kernel. Margey installed just the kernel/recovery, not the ROM.

sfhub said:
As mentioned by Margey's post, the wifi wasn't working well. wifi drivers are in the kernel.
Click to expand...
Click to collapse
hmmm, so ics is still doable then. hmmmmmm

I just wanted to thank everyone for their help it is very much appreciated. I'm going to try what sfhub posted. I still have my stock kernel since I've been working and haven't had time to do anything. I will try and make a copy of my stock kernel. Can I push superuser into my rom using adb or do I need to flash the Epic 4G's kernel then push superuser and then flash my stock kernel back.
Sent from my SCH-R760 using xda premium

eureka
sfhub said:
They already did that. That is why they have rooted adb through the kernel. The issue is they are using an Epic 4G Touch kernel which causes some things to not work on their phone. I am suggesting they install their root functionality in the ROM and restore their original USCC kernel/zImage.
Since (according to them) they don't have a package to return to stock, basically they don't have a kernel/zImage to flash in ODIN because it was never provided to them.
Their original kernel/zImage is gone because they flashed over it (presumably before backing it up). That is why I gave them instructions to pull the backup kernel/zImage. Once they do that, whether they install that zImage within Android or through ODIN is not really important. The important part is they get the correct partition to use to pull the backup from so that they have a valid kernel/zImage to flash.
---------- Post added at 09:55 PM ---------- Previous post was at 09:42 PM ----------
Based on the previous pastebin that was posted it looks like the partitions on the USCC GS2 line up with the Sprint E4GT so it should be safe to run what I suggested.
Both /dev/block/mmcblk0p5 and /dev/block/mmcblk0p6 are linux device files that map to partitions in your phone's EMMC memory.
mmcblk0p5 is labeled zImage (on Sprint) and mmcblk0p6 is labeled recovery.bin (on Sprint). They have the exact same contents. zImage is the kernel and recovery for your phone.
recovery.bin is not being used (on Sprint) so it basically ends up being a backup of your zImage/kernel. Since you overwrote your USCC zImage with the Sprint E4GT zImage (presumably before backing it up) you cannot recover the original from your phone using the partition assigned to zImage.
I am suggesting you retrieve your original zImage from what is essentially a backup in the partition labeled recovery.bin (mmcblk0p6). This can then be installed in your zImage partition (mmcblk0p5) either directly through Android or through ODIN.
Once you create the zImage file as above, keep a copy off your phone on your PC just in case.
The whole purpose of putting back your original USCC zImage/kernel is so all the features work again, but since your root was achieved through the kernel, putting back the original zImage/kernel would cause you to lose root. That is why I suggested, prior to putting back the original USCC kernel, you install persistent root inside your ROM (ie /system)
You can do that by running Auto Root - Option A and ignoring the Blue Hellions error. If your adb is rooted as you described above, Auto Root will still install persistent root in your ROM despite the failure of the zergrush exploit. Once you install the persistent root in your ROM, you can restore the original USCC kernel/zImage and still have root for your applications. You can confirm that Auto Root - Option A did its job by typing:
Code:
ls -l /system/xbin/su
and verifying su is there and it has the proper permissions. If you are unsure, post the output and I can confirm.
Click to expand...
Click to collapse
I doubled checked su, good. Re-ran the image per your suggestion, all good. I have wifi, I have 3G, I have phone and I have root and CWM.
Thank you.

I have been trying to use the auto-root method after installing the recovery kernel and it keeps saying waiting for device to connect? How can I get it to see my device?

themac79 said:
I have been trying to use the auto-root method after installing the recovery kernel and it keeps saying waiting for device to connect? How can I get it to see my device?
Click to expand...
Click to collapse
You can actually just copy the files to your sdcard and run the script by hand, but the specific reason it is waiting for your phone is because ADB cannot see your phone.
That might be because you haven't enabled USB debugging. It might be because of driver problem. It could be because your ##8778# setting is incorrect.
Have you ever been able to use "adb" with your phone?

sfhub said:
You can actually just copy the files to your sdcard and run the script by hand, but the specific reason it is waiting for your phone is because ADB cannot see your phone.
That might be because you haven't enabled USB debugging. It might be because of driver problem. It could be because your ##8778# setting is incorrect.
Have you ever been able to use "adb" with your phone?
Click to expand...
Click to collapse
I finally got it, the problem was I was missing a driver for my phone. Now I'm trying to make a copy of my stock kernel using your instructions but for some reason when I type cd /sdcard it says it can't find the path specified. It shows my device listed, I don't know what I'm doing wrong? Wait..do you mean to use my phone to make a copy?

themac79 said:
I finally got it, the problem was I was missing a driver for my phone. Now I'm trying to make a copy of my stock kernel using your instructions but for some reason when I type cd /sdcard it says it can't find the path specified. It shows my device listed, I don't know what I'm doing wrong?
Click to expand...
Click to collapse
Are you doing that from an "adb shell"?
You can replace with "cd /data/local/tmp", it can really be any directory where you have write permissions.
If you want to be more bold, you can skip the step of creating a zImage file and write directly from the recovery.bin partition into the zImage partition. The zImage file is nice because if you screw things up and your phone won't boot, you can still use ODIN to flash the zImage (assuming you moved it to your PC)
Code:
dd if=/dev/block/mmcblk0p6 of=/dev/block/mmcblk0p5 bs=256 count=32765

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.

[MOD] Advanced Power Menu for JWR66Y

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.

[RECOVERY][All-F2FS] TWRP-2.7.0.0 with All-F2FS support [10/05/14]

TWRP-2.7.0.0 with "All-F2FS" support​
NOTE: I don't have a Nexus 5 to test this. It should work.
Please report back.​
I have modified the standard TWRP recovery to work with F2FS partitions.
This is for "All-F2FS" that mean that /system, /cache and /data are formatted with F2FS.
Keep in mind that this can work only with a compatible kernel and ROM.
What is F2FS?
F2FS (Flash-Friendly File System) is a flash file system created by Kim Jaegeuk at Samsung for the Linux operating system kernel. The motive for F2FS was to build a file system that from the start takes into account the characteristics of NAND flash memory-based storage devices (such as solid-state disks, eMMC, and SD cards), which are widely used in computer systems ranging from mobile devices to servers.
Download:
FormatPartitions.zip: Here (It is named mako but work on N5 too)
TWRP-recovery img: Here
Chagelogs:
- 10/05/14: Fix TWRP
- 08/05/14: Initial release
Here are some explanations. Read them
Recovery has the usual red back key to remember you that you are using a F2FS-recovery.
If wiping /system and /cache and making a factory reset from Wipe menu doesn't work, use FormatPartitions.zip. (<- READ THIS)
Instead wiping /data is fine within the wipe menu.
To switch your /system, /cache and /data partitions to F2FS follow instructions:
Keep in mind that you will lose all the files on the memory of your N5.
You need:
- Two files you can download above (img and FormatPartitions.zip)
- A ROM with "All-F2FS" support
(One way to make your ROM is with Convert To F2FS)
- GApps (i think you want PlayStore.) Usual GApps. Slim AiO work well.
Copy a ROM with "All-F2FS" support to your N5
Copy GApps to your N5
Copy FormatPartitions.zip to your N5
Reboot in bootloader
Flash this recovery with Fastboot (Maybe Flashify works too)
Reboot in new recovery
Flash FormatPartitions.zip
Reboot recovery (It's needed for some reasons..)
Flash ROM
Flash GApps
Go to Wipe Menu and Format Data (Not a simple wipe)
Reboot
Done.
It's easier than it seems
To restore partitions to stock:
- Download a standard TWRP
- Download RestorePartitions.zip (It is named mako but work on N5 too)
Flash RestorePartitions.zip (Untested)
Flash standard Recovery
Format Data in Wipe Menu
Enjoy.
Thanks for:
- dennes544 (All-F2FS Recovery is based on his Recovery)
(Required Commit)
(Source Here)

Looks interesting. I'll give it a shot this weekend. Thanks for this!

I'm glad to see this. Thanks man!!
Sent from my Nexus 5 using XDA Free mobile app

Are there any compatible roms+kernels yet for this device? I've used the nodded slimkat on my 2012 nexus 7

This looks like a great thing! Thank you for taking your time to make this

Hi... First of all thank you been waiting for this mod
I have followed all the steps but no luck... Even got new convert to f2fs app and converted a rom but it fails to flash giving error with updater script.. And normal Roms kill recovery and have to restock

ishaqs60 said:
Hi... First of all thank you been waiting for this mod
I have followed all the steps but no luck... Even got new convert to f2fs app and converted a rom but it fails to flash giving error with updater script.. And normal Roms kill recovery and have to restock
Click to expand...
Click to collapse
As stated i don't have the Nexus 5. But i think that if you give me the recovery.log after the failed flash i can solve the problem.
If you have some time can you retry and after the failed flash go to Advanced -> Recovery log. And then send it to me? Thank you.

Can i use it with ParanoidAndroid?

@legolas93 can this be done without the play store app? I can't afford to buy it, but I am comfortable grabbing recovery logs. I just haven't messed with this F2FS stuff yet. Not sure what ROMs, if any, are F2FS compatible already.

RoyJ said:
@legolas93 can this be done without the play store app? I can't afford to buy it, but I am comfortable grabbing recovery logs. I just haven't messed with this F2FS stuff yet. Not sure what ROMs, if any, are F2FS compatible already.
Click to expand...
Click to collapse
There r no Roms which r f2fs-all compatible yet. But u can edit them urself to make them compatible.
Without the playstore app also its simple u just hv to change the updater-script of the rom in the META-INF folder
find for lines as below:
HTML:
format("ext4", "EMMC", "/dev/block/platform/msm_sdcc.1/by-name/system", "0", "/system");
mount("ext4", "EMMC", "/dev/block/platform/msm_sdcc.1/by-name/system", "/system");
and replace them with this:
HTML:
run_program("/sbin/mkfs.f2fs", "/dev/block/platform/msm_sdcc.1/by-name/system");
run_program("/sbin/busybox", "mount", "/system");
and sometimes u can see this line isolated
HTML:
mount("ext4", "EMMC", "/dev/block/platform/msm_sdcc.1/by-name/system", "/system");
so do the same thing and change it to this
HTML:
run_program("/sbin/busybox", "mount", "/system");
and u need f2fs-all compatible kernels aswell..

@kdh2834 is this method works on caf roms???

notthesun said:
@kdh2834 is this method works on caf roms???
Click to expand...
Click to collapse
Hmm.. Idk I'm not sure but.. Give it a try
I use only aosp ROMs.. So can't give u exact answer...
Sent from my Nexus 5 using XDA Free mobile app

kdh2834 said:
Hmm.. Idk I'm not sure but.. Give it a try
I use only aosp ROMs.. So can't give u exact answer...
Sent from my Nexus 5 using XDA Free mobile app
Click to expand...
Click to collapse
Any f2fs-all kernels out there?
Sent from my Nexus 5 using XDA Premium 4 mobile app

ishaqs60 said:
Any f2fs-all kernels out there?
Sent from my Nexus 5 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
hmm.. not yet for f2fs-all.. if u need i can upload some of kernels i use..
like furnace, franco.. i use these two the most..
and zeta kernel and elemetalx will work without editing

kdh2834 said:
Hmm.. Idk I'm not sure but.. Give it a try
I use only aosp ROMs.. So can't give u exact answer...
Sent from my Nexus 5 using XDA Free mobile app
Click to expand...
Click to collapse
I tried it and it does not work...tested on beanstalk rom

notthesun said:
I tried it and it does not work...tested on beanstalk rom
Click to expand...
Click to collapse
hmm.. maybe CAF roms need different codes..
OP's app also doesnt hv CAF option.. so i guess its different

kdh2834 said:
There r no Roms which r f2fs-all compatible yet. But u can edit them urself to make them compatible.
Without the playstore app also its simple u just hv to change the updater-script of the rom in the META-INF folder
find for lines as below:
HTML:
format("ext4", "EMMC", "/dev/block/platform/msm_sdcc.1/by-name/system", "0", "/system");
mount("ext4", "EMMC", "/dev/block/platform/msm_sdcc.1/by-name/system", "/system");
and replace them with this:
HTML:
run_program("/sbin/mkfs.f2fs", "/dev/block/platform/msm_sdcc.1/by-name/system");
run_program("/sbin/busybox", "mount", "/system");
and sometimes u can see this line isolated
HTML:
mount("ext4", "EMMC", "/dev/block/platform/msm_sdcc.1/by-name/system", "/system");
so do the same thing and change it to this
HTML:
run_program("/sbin/busybox", "mount", "/system");
and u need f2fs-all compatible kernels aswell..
Click to expand...
Click to collapse
Hello i tried yesterday and today with this trick, from mako thread, but with no success
Everytime i get a failed on twrp

micr0g said:
Hello i tried yesterday and today with this trick, from mako thread, but with no success
Everytime i get a failed on twrp
Click to expand...
Click to collapse
I think it only works with NON-CAF ROMS (AOSP)
so.. if u tried it with a CAF ROM it might give errors... but not in twrp for sure..
see if u did the zip properly..

kdh2834 said:
I think it only works with NON-CAF ROMS (AOSP)
so.. if u tried it with a CAF ROM it might give errors... but not in twrp for sure..
see if u did the zip properly..
Click to expand...
Click to collapse
I tried with Slimkat,so AOSP
replaced
format("ext4", "EMMC", "/dev/block/platform/msm_sdcc.1/by-name/system", "0", "/system");
with
run_program("/sbin/mkfs.f2fs", "/dev/block/platform/msm_sdcc.1/by-name/system");
and
mount("ext4", "EMMC", "/dev/block/platform/msm_sdcc.1/by-name/system", "/system");
with
run_program("/sbin/busybox", "mount", "/system");

micr0g said:
I tried with Slimkat,so AOSP
replaced
format("ext4", "EMMC", "/dev/block/platform/msm_sdcc.1/by-name/system", "0", "/system");
with
run_program("/sbin/mkfs.f2fs", "/dev/block/platform/msm_sdcc.1/by-name/system");
and
mount("ext4", "EMMC", "/dev/block/platform/msm_sdcc.1/by-name/system", "/system");
with
run_program("/sbin/busybox", "mount", "/system");
Click to expand...
Click to collapse
Have you flashed the recovery i posted in OP? Can i have a recovery.log of the failed flash?