Ok, so for the slightly less noob-y among us, here are some CWM variants of the now-released EP4D OTA, in all of its bloated glory! Thanks go to spjetrovic (provided the OTA leak) and spc_hicks09 (provided a file dump), as well as pentafive for the full factory ODIN. Thanks also go out to skydeaner on IRC and gunnermike53 for offering up some server space for files. Download speeds were pretty atrocious on the two sites I had been previously using.
I AM IN NO WAY RESPONSIBLE FOR ANYTHING THAT HAPPENS (GOOD OR BAD) AS A RESULT OF FLASHING OR ATTEMPTING TO FLASH WHAT IS POSTED HERE! As an additional disclaimer - I'm still pretty new to all of this, but it has worked for me and a few others that were kind enough to try. That being said, as always YMMV.
While there are very likely much better ways to go about this, the current work here is all pulled from the factoryfs.rfs in the full factory ODIN posted by pentafive (originally found here) - and it is from this same ODIN that I pulled the stock kernel and modem files. Just to see if I could figure it out, I took a stab at repacking the kernel with one or two things I was missing from the full-on stock kernel, but those are not included in the main EP4D CWM files (see bottom of OP for links).
The odexed version I did NOTHING to (except pull it from factoryfs.rfs and fashion it into something CWM flashable), which means it is unrooted and it will (if on a stock kernel) overwrite CWM recovery with the stock recovery after rebooting. The deodexed/zipaligned version includes superuser/su (found here) as well as busybox (from here). The same goes for the ODIN version of the deodexed EP4D, except there is a version that includes the latest 5.0.2.7 recovery by imnuts found here as well as my attempt at a repacked kernel. In either case the changes were pretty minimal - it's simply deodexed bloated stock.
You will need to have either CWM (version 5.0.2.7 can be found here, but earlier versions like 4.0.1.4 will work fine as well) already on your phone or ODIN already on your computer, and I would strongly recommend doing a data wipe/factory reset within CWM before flashing either the odexed or deodexed CWM EP4Ds as well (that's what I've been doing at least and I have had no problems).
Also - if you are flashing one of the kernels, either stand alone or as part of a CWM zip, MAKE SURE voodoo lagfix is completely disabled (i.e. /data, /dbdata, /cache, and /system all need to be rfs, NOT ext4) BEFORE flashing.
CWM Installation instructions:
- Download file and place on sdcard
- Boot into CWM recovery
- If flashing odexed/deodexed EP4D wipe data/factory reset (Recommended)
- If flashing kernel only or CWM that includes kernel - you better not be ext4, and I tend to always wipe cache/dalvik for CWM flashes fwiw
- Install the .zip you put on your sdcard
ODIN Installation instructions:
- Download file on to computer and unzip it (w/ 7-zip or the like)
- Put phone into download mode
- Connect phone to computer (assuming all is well with the drivers)
- Open ODIN (I have been using 1.83)
- Place the .tar.md5 file in PDA!
- If flashing kernel only - you better not be ext4!
- Flash away
NOTES:
While I am unsure how relevant it is now, I have encountered an occasional odd issue in the past with CWM after flashing that seems to require adb to resolve.
The issue is that after flashing and then booting into recovery, I occasionally get a "can't mount /sdcard" error. Apparently that in itself is a known issue, and it is listed as such in the CWM recovery thread.
The fix requires you to perform the following commands using ADB:
Code:
adb shell
umount /sdcard
rm -f /sdcard
mkdir /sdcard
exit
If you do not have ADB installed and you are having the "can't mount /sdcard" error after flashing - I have a possible workaround for you. Download the ADBsdcardFix.zip here - then extract the folder (should be fine to extract it to your desktop) and attach your phone to the computer via USB (I did this while the phone was already in CWM). Open the newly-extracted ADB folder, and then double-click on the CWMsdcardFix.bat - something should pop up on the screen for a brief second, which is completely normal. After double-clicking the .bat file, on the phone go to mounts and storage, then select mount /sdcard - and it now should work!
Either approach here (adb code or the stuff in ADBsdcardFix.zip) has worked every time I have needed it, although again in my experience I have not been able to cull the rhyme or reason out of when that need will present itself.
For those who dabble in ADB, I noticed that adb shell seems to work "differently" on the stock EP4D kernel - well, differently in the sense that I haven't dabbled much in using stock kernels, so my basis of comparison consists of custom kernels. Normally entering adb shell would lead to a # prompt, but with the stock kernel it stays as $ - however, if you then enter su it goes to the # prompt. This also means you have to exit twice to leave shell - once for su, and once for shell. This also causes problems when using the adb push command - but the tweaked kernel I managed to repack and put together seems to circumvent such issues. I'm very new to such kernel repack tweaks so I am unaware if any other issues come about, but it has been running fine for myself for some time - again, at least on the surface. Take from that what you will.
Now that pentafive has posted a full factory ODIN, you no longer have to go through the OTA or CWM updater from EE4 modems route. Instead you can just flash the EP4D Modem package listed below in ODIN.
Please let me know if there are any problems/issues.
---CWM EP4D STOCK FILES---
BLOATED EP4D DEODEXED ZIPALIGNED CWM .ZIP
md5: 2413D8C0D97C314AD62105270370D4DC
BLOATED EP4D ODEXED CWM .ZIP
md5: E852D91C12FDF9C9ED71D9AA67AC367C
NOTE: This includes the stock kernel, so you MUST be rfs for this. If you are ext4, you WILL have problems.
---ODIN EP4D STOCK FILES---
BLOATED EP4D DEODEXED ZIPALIGNED .TAR.MD5
NOTE: This does NOT include a kernel or recovery, but it does include the EP4D modems. This should also wipe your data.
md5: F97C271E70A4B39C9D7211EEF17BCBF1
BLOATED EP4D DEODEXED ZIPALIGNED .TAR.MD5 + REPACKED KERNEL & RECOVERY
NOTE: This includes my attempt at a repacked kernel and the latest 5.0.2.7 CWM recovery found here, as well as the EP4D modems. This should also wipe your data.
md5: 13DD3B5300D92E10EBB000C724225990
---CWM EP4D KERNEL FILES---
NOTE: Only flash these if you are rfs - issues will abound when flashed over ext4 setups
NOTE2: Also - the repacked one is a HUGE experiment on my part - it works fine for me (at least on the surface), but YMMV. FLASH WITH CAUTION!
REPACKED STOCK EP4D KERNEL CWM .ZIP
md5: CE78B23A7FA6CBED9E2A927A7722A8F3
STOCK EP4D KERNEL CWM .ZIP
md5: AEE483F6513E742349D5F3A2D65007F2
---ODIN EP4D KERNEL FILES---
NOTE: Only flash these if you are rfs - issues will abound when flashed over ext4 setups
NOTE2: Also - the repacked one is a HUGE experiment on my part - it works fine for me (at least on the surface), but YMMV. FLASH WITH CAUTION!
REPACKED STOCK EP4D KERNEL ODIN .TAR.MD5
md5: 17C22365FACDB239479D72E348B0D2DB
STOCK EP4D KERNEL ODIN .TAR.MD5
md5: 93AF45F86C8B51B9EF19C789055E0B66
---ODIN EP4D MODEM FILE---
EP4D MODEM
md5: 6F84382BFCF28131DC572A6F9019AFE6
NOTE: This is for the .7z file - you will need 7-zip or something similar to decompress the ODINable .tar.md5 file
---MISCELLANEOUS---
NOTE: READ DESCRIPTION ABOVE FOR HOW AND WHY TO USE THE FILE BELOW -
--- DO NOT FLASH IN CWM!! ---
ADBsdcardFix.zip
md5: 5A362D2AB8BD5D7878AC1835A4AD558E
dwitherell said:
I posted this elsewhere, but in the spirit of sharing I figured it might be of some use to folks if I posted it here as well. Ok, so for the slightly less noob-y among us, here is a CWM variant of the imminent EP4D OTA.
Click to expand...
Click to collapse
Thanks for putting this out!
spc_hicks09 said:
Thanks for putting this out!
Click to expand...
Click to collapse
No problem - and thanks for the help!
dwitherell said:
No problem - and thanks for the help!
Click to expand...
Click to collapse
Very welcome!
Post Removed.
Post removed.
I'll remove the file from my server. I tend to get ahead of myself (and have been known to put my foot in my mouth on a number of occasions) when providing files and help to other users who may want some custom packages for this ROM. I do give full credit to those people who deserve the credit, I just package them into ZIP files for people to use.
I do apologize. The file has been removed from the server.
You'd think that I'd have learned from this considering that imnuts got pissed at me for doing the same thing. But... I have a thick skull and sometimes things don't get through it unless it's pounded into it.
OP has been updated. There were some issues with force closes in Settings.apk that are now fixed.
trparky said:
I'll remove the file from my server. I tend to get ahead of myself (and have been known to put my foot in my mouth on a number of occasions) when providing files and help to other users who may want some custom packages for this ROM. I do give full credit to those people who deserve the credit, I just package them into ZIP files for people to use.
I do apologize. The file has been removed from the server.
You'd think that I'd have learned from this considering that imnuts got pissed at me for doing the same thing. But... I have a thick skull and sometimes things don't get through it unless it's pounded into it.
Click to expand...
Click to collapse
As you can see, there is a new file in the OP now. And no worries on this - it was on my to-do list anyway, it just happened to slip my mind last night. Thanks for pointing out the utility of it.
Am I allowed to post that package? If so, I'll repost that when I get home.
It's just the stock EP4D theme with the Extended Power Menu Options that you made that I just packed so you can install it as a ZIP file in CWM.
Sent from my SCH-I510 using Tapatalk
trparky said:
Am I allowed to post that package? If so, I'll repost that when I get home.
It's just the stock EP4D theme with the Extended Power Menu Options that you made that I just packed so you can install it as a ZIP file in CWM.
Sent from my SCH-I510 using Tapatalk
Click to expand...
Click to collapse
To be honest, I'm not sure how worthwhile it would be to post what you had, as what you have already posted in the themes subforum and what is posted in the OP here gets the same job done (and can be combined by folks on their own if desired).
Thanks for this! I'm a Linux user so Odin really isn't an option for me
shobon said:
Thanks for this! I'm a Linux user so Odin really isn't an option for me
Click to expand...
Click to collapse
Glad it was useful for you!
As for the "EE4B TO EP4D MODEM PATCHER" patch, do you have to use Stock Recovery or can you use CWM to install the modem patch?
Why I ask is that I looked at the updater-script and it looks very very similar to the same scripts we use in the install packs that are used with CWM.
trparky said:
As for the "EE4B TO EP4D MODEM PATCHER" patch, do you have to use Stock Recovery or can you use CWM to install the modem patch?
Why I ask is that I looked at the updater-script and it looks very very similar to the same scripts we use in the install packs that are used with CWM.
Click to expand...
Click to collapse
It's a CWM package. At least that's how I flashed it. I'm pretty sure I saw dwitherell post in a different thread on Rootz that he built that package himself for CWM based on the deltas in the original update.zip, so it'll actually probably not work in stock recovery.
So I decided to go back to EE4 (only the modems, not the ROM) and flash the new modems via CWM. Sure enough, it worked and now EP4 shows up in About Phone.
I just updated the modems to EP4D from EP4P (CDMA). Thanks!
Thank you for this! Running this package without any hitches. Still not sold on the EP4D modem but that is neither here nor there. Good job!
Sent from my SCH-I510 using xda premium
I have the OTA EP4D installed, rooted and CWR installed but would like a deodexed version. It seems this version is from the last EP4 leak rather than the OTA which did get some changes over the last leak? Does anyone know?
Thanks
Nope, this is the same version people got from the OTA just a bit customized.
Thanks TR
Sent from my SCH-I510 using Tapatalk
Related
CAUTION: ANY CUSTOM ROM WHICH HAS A MODIFIED KERNEL, PROBABLY WILL BREAK BY USING THIS.
More than likely you will need to copy over the ramdisk. If you don't know how to do this, then wait until your ROM developer does it for you!
Who: For those who are ANXIOUS and the DEVELOPER type (more advanced users) who want to load the new kernel which comes with the OTA_Supersonic_1.47.651.1-1.32.651.6_release.zip released today.
If you're not an advanced user or the developer type, please wait for the builder of the ROM you're using to release their own update!
What: I've pulled the boot.img from the firmware.zip inside of the OTA_Supersonic_1.47.651.1-1.32.651.6_release.zip and put it into this update.zip.
Tech Details: This update.zip copies flash_image and boot.img to /system/bin and /system, flashes the new boot.img and deletes boot.img from /system. My first time creating this type of update.zip on the EVO!
Advantages:
npace said:
Here's a rundown of the issues that I tested for fixes:
1. Touch input lag -- fixed -- tried with multitouch visualizer 2
2. Improperly grounded touchscreen -- fixed -- tried on multiple surfaces
Click to expand...
Click to collapse
http://www.joeyconway.me/evo/stock/jk-stock-OTA-1.47.651.1-kernel-signed.zip - WiFi will not work until the System Software portion of the OTA update is loaded
I got my retard helmet on and I'm ready to test this baby on Avalaunch's Froyo ROM.
Sorry for the noob question, I'm new to android. Is this for stock rooted roms? I am running stock evo rom rooted and nand unlocked, so is this essentially an update for rooted users running stock rom? And will I have to update the radio with a seperate flash? Thanks for your help, and everyone's hard work!
I'm using Jk-original 1.0.8 odex and I flashed the update image...giving error..."Can't chown/mod /system/flash_image (No such file or directory) Failure at line 3:set_perm 0 0 0755 SYSTEM:flash_image Installation aborted." I do have "flash_image" in /system/bin.? Also, followed Joey's script for that update.zip in adb manually and didn't get any error, I just don't know how to verify the install. Will it show in build???
snandlal said:
I'm using Jk-original 1.0.8 odex and I flashed the update image...giving error..."Can't chown/mod /system/flash_image (No such file or directory) Failure at line 3:set_perm 0 0 0755 SYSTEM:flash_image Installation aborted." I do have "flash_image" in /system/bin.? Also, followed Joey's script for that update.zip in adb manually and didn't get any error, I just don't know how to verify the install. Will it show in build???
Click to expand...
Click to collapse
Re-download. He had to make a change and just re-uploaded it, I just downloaded and applied it without a problem, after having the same error you did with the first file.
Any comments from people that have this applied (and working with full root)?
Shane Pitman said:
Re-download. He had to make a change and just re-uploaded it, I just downloaded and applied it without a problem, after having the same error you did with the first file.
Click to expand...
Click to collapse
Do you have any of the Sprint and/or HTC apps removed? I removed a bunch of that bloatware and I read that some people couldn't get the update to install. Wondering if OP fixed that in this kernel.
That worked Thanx
Kernel's working just fine with Avalaunch's Froyo ROM.
joeykrim,
Have you used Koush's anykernel? I think you can make a update.zip that works with any kernel..
It just hasn't worked properly for me yet...
Here's link:
http://github.com/koush/AnyKernel
It should extract the ramdisk and everything from your current kernel and just replace the zImage and then flashes boot.img.
Kiraly said:
Do you have any of the Sprint and/or HTC apps removed? I removed a bunch of that bloatware and I read that some people couldn't get the update to install. Wondering if OP fixed that in this kernel.
Click to expand...
Click to collapse
I've got most of the Sprint/HTC crap removed, rooted, nand unlocked, custom recovery, running joeykrim-original-1.0.8 deodex rom, and this worked just fine.
lafrad said:
Any comments from people that have this applied (and working with full root)?
Click to expand...
Click to collapse
this ONLY updates the kernel and will not effect root access.
Kiraly said:
Do you have any of the Sprint and/or HTC apps removed? I removed a bunch of that bloatware and I read that some people couldn't get the update to install. Wondering if OP fixed that in this kernel.
Click to expand...
Click to collapse
this is ONLY the kernel. has nothing to do with ANYTHING in /system including bloatware/apps.
npace said:
joeykrim,
Have you used Koush's anykernel? I think you can make a update.zip that works with any kernel..
It just hasn't worked properly for me yet...
Here's link:
http://github.com/koush/AnyKernel
It should extract the ramdisk and everything from your current kernel and just replace the zImage and then flashes boot.img.
Click to expand...
Click to collapse
nice. i remember seeing this once but had forgot about it.
i prob wont delve into this yet cuz i haven't modified the ramdisk at all, but this is encouraging!
ill prob wait till we get some htc source code for the kernel, and then dive into customizing the kernel and the ramdisk or if i get bored and wanna customize my ROM with this stock kernel and custom ramdisk!
this is def good to know! thanks for the link!
Did anyone else have an issue with 4G stuck saying its turning on? Worked fin again after.restoring a backup.
Yep... 4th got stuck for me. Camera ad ADW also crashed a bunch too
Sent from my PC36100 using Tapatalk
I'm sure that a lot of people already know about the -=V6 SuperCharger=- by zeppelinrox.
If you are not familiar with his great work please follow the link above and read more about it on his thread.
Those of you who have already tried it on their HTC One S (stock) will probably know that there is a whole different level of complexity when it comes to installing it on an ICS ROM. First of all, on any ICS ROM you have to patch the framework library services.jar to get the full functionalaty of the V6 SuperCharger. To make matters worse the HTC Sense is an odexed ROM meaning that you have to do all the patching manually, which is by no means a trivial exercise. Of course you may decide that you don't want to go patching any files and you may be happy with the limited functionality that you get from the V6 SuperCharger as it is. If that's the case you probably won't find this thread very useful...
However, if you're one of those who will not settle for anything less than the full functionality, you need not worry anymore!
Over the last few days I've done all the hard work of decompiling and manually patching the stock services.odex library so people don't have to do it themselves anymore. Not only that, but I've prepared separate versions of the services.odex for each of the three launcher SuperCharge options available:
1. Hard-to-Kill (downloads 1 & 5)
2. Die-Hard (downloads 2 & 6)
3. Bullet-Proof (downloads 3 & 7)
In addition, I'm also including the stock services.odex file so you can restore it back to your system in case you have any problems with the patched files.
4. Stock services.odex (download 4)
Installation procedure:
DISCLAIMER: I take no responsibility whatsoever for anything that might go wrong with your phone, for any and all data loss, for bricking your phone, etc. You do this at your own risk and it is 100% your responsibility.
WARNING! The files provided are specifically for, and have only been tested on, HTC One S with Stock Sense ROM v1.53.401.2 (Europe). These files may also work fine on different versions of the Stock Sense ROM but I haven't tested that. However, if you use them on any other (custom) ROM they are most likely to get your phone either stuck at boot or into a boot loop!
REQUIREMENTS:
a. First and foremost your phone needs to be rooted and have BusyBox v1.16.2 or higher installed. This is a requirement for the V6 SuperCharger script to run so there's no way to get around it.
b. To install the patched services.odex file you ideally need to have a custom recovery installed, such as ClockworkMod. This way you can just flash the patched services.odex from the recovery and if anything goes wrong, simply flashing the stock services.odex over should get you out of trouble (stock file also provided as a recovery update). While it is not absolutely necessary to save a recovery image of your ROM, I would strongly advise you to do so as it's always a good idea to have a recent recovery image to hand just in case (e.g. there is a chance that the stock services.odex included in here may not work if you have a region/operator specific Sense ROM on your HTC One S). Please keep in mind that the stock services.odex included in here comes from Stock Sense ROM v1.53.401.2 (Europe) so it may not work on other versions of Sense ROM!
c. If you don't want to use the recovery update file, you can also download just the services.odex and install it manually. However, if you choose to do this then you're on your own as I don't have enough time to write a tutorial on how to install it manually.
Step 1. If you haven't already done it, go to the -=V6 SuperCharger=- thread by zeppelinrox and read up on the script and what it does.
Step 2. Follow the instructions on the thread (see Step 1) on how to install the -=V6 SuperCharger=- on a typical non-ICS system.
You can get the latest version of the script from this post: http://forum.xda-developers.com/showpost.php?p=18703418&postcount=5021
Step 3. Forget about manually patching the services.jar or the services.odex file! Just download the version you need from the bottom of this post AS WELL AS THE STOCK VERSION! You will need the stock if your phone gets stuck on boot. For the installation, see the two options below. Before you do anything however, I strongly advise you to save a system recovery image just in case.
a.The first 4 attached files, named update-services.odex-[something].zip, are recovery update files meant to be flashed via a custom recovery such as ClockworkMod. After flashing the recovery update, also wipe cache and dalvik cache and then reboot.
b. The last 3 attached files are just archives of the patched service.odex files. If you want to go this route you can find some guidance on the -=V6 SuperCharger=- thread in terms of where it needs to be installed and what permissions it should have. Also, if you're using this method don't forget to do a SuperClean & Reboot using the option in the V6 SuperCharger script.
Step 4. It is normal for the first boot after installation to take longer than usual. If your phone has gone past the boot animation and is displaying a windows saying something like 'upgrading applications...' then it's all gone fine so just wait for it to finish. If your phone hangs on the boot animation longer than usual it means that it's probably stuck there and the patched services.odex file is not compatible with your ROM. DO NOT PANIC! Simply go to the recovery instructions further on.
Recovery.
a. If you phone is stuck on the boot screen, hold the power button pressed for about 10 seconds so that the phone goes into hard power off (the touch keys below the screen will start blinking after a few seconds, that's normal).
b. After that just boot into recovery as you nomally do (while holding the volume down pressed, also press the power button briefly and the phone should start into the boot menu; in there, scroll using the volume up / down keys and select the RECOVERY option by pressing the power key).
c. In the recovery simply flash the stock services.odex update file, wipe cache and dalvik cache and reboot. Now the phone should start up fine but your services.odex will not be patched.
d. If your phone is again stuck on the boot screen, you'll have to do a full restore of your ROM from the image that I have strongly advised you to save earlier.
Good luck and I hope you find this useful!
Oh, and pleeease use the Thanks button!
thanx, just installed busybox then flashed "Hard to kill" thru recovery, booted right up on Noble 4.0
Bxrxyxaxn said:
thanx, just installed busybox then flashed "Hard to kill" thru recovery, booted right up on Noble 4.0
Click to expand...
Click to collapse
Thanks, but if you're using this patch on Noble 4.0 it will have absolutely no effect.
That's because Noble 4.0 is a deodexed ROM which means that the services.odex file you've just installed is simply ignored by the system.
Instead you should patch the services.jar file using the online patching tool for deodexed ROMs provided on the V6 SuperCharger thread.
will try on stock T-MobileUS nand later...but thanx for the heads up, will do, edit: Noble already has it
Flashed bullet-proof on stock TMOUS rooted ROM. Caused boot loop. No surprise, it's a different ROM but thought I would give it a go anyways.
Thanks for the post, will definitely use if I go with an EU ROM.
tmobile us
Will this work on the tmobile us one s? Update: noticed the post above stating it doesnt work for T-Mobile us.
for what ever reason i fought with 1.2 bootloader for about 6 days straight with 0 luck loading any ics rom's. so i decided to try the 1.1 bootloader and it works just fine. i have loaded every ics rom i have downloaded and every single one booted with no problems. i followed the process from the frozen ice rom for each of them. i am currently running the g harmony 4.o.4 ics 120 rom and it has been very stable and everything works except the camera and mic which is already a known issue with the ics rom's for the gtab.
jamcar's frozen ice thread
http://forum.xda-developers.com/showthread.php?t=1707503
a little video i made of the bootloader rebooting into ics
http://www.youtube.com/watch?v=7L2KYaiu0OI&list=UUitE779SbBIZKk0EGlnHWVg&index=1&feature=plcp
i don't know if this will work for everyone but it did work very well for me.
Possible other solution.
I had the same experience. Installed ICS bootloader 1.2 just fine. Then couldn't download any apps from anywhere. Went back and researched some more, downloaded 3DGtab-GAppZ- 8.3.zip, installed it the same way as ICS and everything fixed itself. Been using ICS for several weeks. Never going back! :good:
I'm curious about the speed of ICS? I just installed Frozen Ice and it seems that it takes some apps up to 30 seconds to load and the wi-fi has just been horrendous (other users are reporting that as well). Wondering if its just the Frozen Ice build that is doing this or if all the ICS Roms have this problem..
JJewel is the harmony ROM you are running available here?
jjewell said:
for what ever reason i fought with 1.2 bootloader for about 6 days straight with 0 luck loading any ics rom's. so i decided to try the 1.1 bootloader and it works just fine. i have loaded every ics rom i have downloaded and every single one booted with no problems. i followed the process from the frozen ice rom for each of them. i am currently running the g harmony 4.o.4 ics 120 rom and it has been very stable and everything works except the camera and mic which is already a known issue with the ics rom's for the gtab.
jamcar's frozen ice thread
http://forum.xda-developers.com/showthread.php?t=1707503
a little video i made of the bootloader rebooting into ics
http://www.youtube.com/watch?v=7L2KYaiu0OI&list=UUitE779SbBIZKk0EGlnHWVg&index=1&feature=plcp
i don't know if this will work for everyone but it did work very well for me.
Click to expand...
Click to collapse
thats insane!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
for two reasons:
1.) wrong bootloader
2.) the CWM version you have wasnt supposed to be able to flash above froyo but let you have ICS
---------- Post added at 07:48 PM ---------- Previous post was at 07:47 PM ----------
Dymondy2k said:
I'm curious about the speed of ICS? I just installed Frozen Ice and it seems that it takes some apps up to 30 seconds to load and the wi-fi has just been horrendous (other users are reporting that as well). Wondering if its just the Frozen Ice build that is doing this or if all the ICS Roms have this problem..
JJewel is the harmony ROM you are running available here?
Click to expand...
Click to collapse
yes it was the Fr0z3n 1c3 build. it was due to a bad upload so users had a bad download, but it has been fixed
Jamcar.. It seems to be running great for me now.. much faster speeds in both wi-fi and opening apps...
jamcar said:
thats insane!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
for two reasons:
1.) wrong bootloader
2.) the CWM version you have wasnt supposed to be able to flash above froyo but let you have ICS
Click to expand...
Click to collapse
There's something definitely puzzling here but those 2 are not the reason for puzzlement.
As for point #1: yes, the TeamDRH 2.6.39.x kernel works on both the 1.1 and 1.2 bootloaders--it definitely was a surprise. This is what nVidia/ViewSonic should've done with their older 2.6.32.x kernels also when they updated the bootloader.
Point #2 is not puzzling either: Recovery (we're discussing only CWM here) mode consists of 2 components both of which are build when you compile CWM:
a) the /sbin/recovery program proper which puts up the menus and performs the tasks chosen by the user, and,
b) (for installation only) a program called (for Froyo onwards) META-INF/com/google/android/update-binary in the installation zip file.
It is this update-binary program which is responsible for reading and executing a META-INF/com/google/android/updater-script file which is where the steps required to install a ROM are written. Ie. it is not the recovery program which does the installation. So, as long as you have an update-binary program which understands the updater-script in the installation zip file, all CWM versions > 2.5.x will be able to do the job.
The only puzzling thing is how the 1.1 bootloader was put back.
If it was using one of the 1.1 nvflash packages we have floating around on this board, then the "system" partition would have been shrunk back to 200 MB. This means that during the ICS ROM install, some apps/programs wouldn't have been written--/tmp/recovery.log should show a lot of file copy failures during installation due to "no space left on device" errors. That file will also show which files were not copied. And depending on which files were not copied, it could or, could not--in this case--adversely affect the final ROM install.
rajeevvp said:
There's something definitely puzzling here but those 2 are not the reason for puzzlement.
As for point #1: yes, the TeamDRH 2.6.39.x kernel works on both the 1.1 and 1.2 bootloaders--it definitely was a surprise. This is what nVidia/ViewSonic should've done with their older 2.6.32.x kernels also when they updated the bootloader.
Point #2 is not puzzling either: Recovery (we're discussing only CWM here) mode consists of 2 components both of which are build when you compile CWM:
a) the /sbin/recovery program proper which puts up the menus and performs the tasks chosen by the user, and,
b) (for installation only) a program called (for Froyo onwards) META-INF/com/google/android/update-binary in the installation zip file.
It is this update-binary program which is responsible for reading and executing a META-INF/com/google/android/updater-script file which is where the steps required to install a ROM are written. Ie. it is not the recovery program which does the installation. So, as long as you have an update-binary program which understands the updater-script in the installation zip file, all CWM versions > 2.5.x will be able to do the job.
The only puzzling thing is how the 1.1 bootloader was put back.
If it was using one of the 1.1 nvflash packages we have floating around on this board, then the "system" partition would have been shrunk back to 200 MB. This means that during the ICS ROM install, some apps/programs wouldn't have been written--/tmp/recovery.log should show a lot of file copy failures during installation due to "no space left on device" errors. That file will also show which files were not copied. And depending on which files were not copied, it could or, could not--in this case--adversely affect the final ROM install.
Click to expand...
Click to collapse
wait then why does cm9 require that you CWM 5.x.x.x ( the one koush made for ICS)?
jamcar said:
wait then why does cm9 require that you CWM 5.x.x.x ( the one koush made for ICS)?
Click to expand...
Click to collapse
Is it a "hard" requirement or a "soft" recommendation? Because CWM works as I've described for user-driven zip file installs.
I used gtab.nvflash.1.2.branch.20110508 with cwmv3028 To go to BL 1.2 and then flashed G_Harmony_ICSv1.5(120)(SuperCharged)
It went smooth, works great, and I am very happy with my GTAB
rajeevvp said:
Is it a "hard" requirement or a "soft" recommendation? Because CWM works as I've described for user-driven zip file installs.
Click to expand...
Click to collapse
For cm9 I'm honestly not 100% sure, but in cm7 you had to have CWM v3.x.x.x it was a hard requirement. It wouldn't install if you weren't on v3.x.x.x
Sent from my SPH-D710 using xda app-developers app
jamcar said:
... but in cm7 you had to have CWM v3.x.x.x it was a hard requirement. It wouldn't install if you weren't on v3.x.x.x
Click to expand...
Click to collapse
Check this again: Official CM7 installs just fine with 2.x for these 2 reasons:
1. All official CM7 releases (even the latest 7.2) come with a kernel built for a 1.1 bootloader. This means that they expect to run on a 1.1 bootloader, which, in turn, means that recovery image must also necessarily have a 1.1 kernel.
2. All the versions of CWM v3.x that I've seen on this board have a 1.2 kernel in the recovery image.
This means that if you were planning to install any of the official CM7 builds, then you would not be able to do it by using any of the CWM-v3.x versions built by roebeet--CWM-v3.x just wouldn't boot. You would need to be running one of the 2 CWM versions for a 1.1. bootloader: CWM-v2.5.1.x or CWM-4.0.1.5.
Note:
CWM >= 3.x officially dropped support for "Amend" scripting. CWM-2.5.x supports both the old "Amend" and the newer "Edify" scripting.
There are unofficial CM7 repacks and RCs which have a 1.2 kernel and so will run on the 1.2 bootloader.
You could also insert a 1.1 kernel into a 1.2-based recovery image and get more choices of CWM versions--I'm running CWM-5.5.0.4Beta15 on my 1.1 right now, for instance.
These last 2 are the exceptions rather than the rule-- but, really, there's no need for any ambiguity in any of this. The fact that ICS ROMs and CM7.x can be installed using any version of CWM >= 2.5.1.x can easily be checked.
That's interesting. Wish I knew that before I switched over to 1.2
Sent from my VS910 4G using xda premium
opening this up for anyone that may have problems installing the kernel etc.
first question, i've out all of the necessary files into the CNA.zip (Codename Android) that i want to flash, but whenever i boot into TWRP to flash it, it fails. i could've sworn i saw @FBis251 say that zips didn't need to be signed, maybe i'm misunderstanding his meaning. anyone with advice?
I only really provide support for AOKP as TWRP was compiled using the AOKP source code. There may be differences in the code from other roms' recoveries that make the zip installations fail. What I can recommend you try is to try flashing it via TWRP + AOKP to verify that it isn't a TWRP error.
If you continue having problems it's up to the rom devs to make other mods work with their roms. There are just too many roms for me to keep up with and I haven't had time to be doing that.
I'm on AOKP (pay no attention to my sig) with TWRP and it's not checking signing on the zips, so I guess I don't know what the issue is
Sent from my Unicorn powered SGS4G
I'm assuming other zips flash fine? It might be a problem with the way the rom dev created the zip. Normally using 7-zip with highest compression (lvl 9) works for me in case you want to try re-zipping it yourself, assuming there aren't any other problems with the zip file.
It's the same zip I flashed (your) AOKP from. I did rezip it, on my Mac, so I don't know if the issue might arise with how he program is rezipping the file
Sent from my Unicorn powered SGS4G
well you might have better luck with the command line zip utility that comes with your mac.
You can extract the rom zip, then try doing this
cd /path/to/extracted_files
zip -9 -r ~/destination.zip *
that'll zip all the rom files up into a high compression zip. Try flashing after that.
Still nothing. Hmmm, I wonder what is causing this
Sent from my Unicorn powered SGS4G
Juls: Try "Betterzip" for Mac - that's what I used to set up Slim with Thomas's LZ kernel. It allows you to modify the zip file without extracting/unzipping it.
I installed the LZ kernal into the latest miui v4 rom Erik released today and when i flashed it through TWRP if flash successfully but i lost root access, so i tried flashing it through cm9 recovery because that's how i fixed the root access on gummy mutt but it didn't give me the option to fix root. Any help ?
allstar1397 said:
I installed the LZ kernal into the latest miui v4 rom Erik released today and when i flashed it through TWRP if flash successfully but i lost root access, so i tried flashing it through cm9 recovery because that's how i fixed the root access on gummy mutt but it didn't give me the option to fix root. Any help ?
Click to expand...
Click to collapse
Flash the superuser binary zip with cwm? Just google superuser binary and it should link you to it
----------------------------------------------
If helped don't be afraid to hit the thanks button it doesn't bite lol
Hey everybody -
Seems folks are wanting some sort of cwm recovery flashable twist on the i577 stock ICS rom that was first posted here, but is also discussed here and can be attained in an easy one-click odin fashion from here thanks to thomas.raines. Well, I think I managed to put one together. I don't know if I will tinker on this much, but you never know - I can't stop myself most of the time.
I AM IN NO WAY RESPONSIBLE FOR ANYTHING THAT HAPPENS (GOOD OR BAD) AS A RESULT OF FLASHING OR ATTEMPTING TO FLASH WHAT IS POSTED HERE!
The process to get here was rather simple (though the updater-script editing was rather annoying). After flashing via thomas.raines's handy dandy odin 1-click tool, I got a system dump. Originally I was just going to open up the system.img.ext4 and get what I needed from there, but I did it this way to figure out some permissions and symlink issues I was having with the updater-script. I then went through and deodexed, debloated, added in busybox, added in SuperSU, and made one small smali hack to Contacts.apk to stop a rather annoying insistence on checking AT&T subscriber crap every time you went into contacts. That's it - so this is not really all that "developed" or anything. All that is contained within the cwm zip is the same stuff that is contained in the one-click - it's just /system and boot.img (kernel) - nothing more (i.e. this does NOT change your modems). That all being said, let me know if things work, or if any oddities come up. Also feel free to comment on how this might improve or if I've gone about anything in a not-so-smart way.
Usual rules apply - make sure to wipe data/factory reset to avoid issues. Flash in CWM recovery.
CWM Installation instructions:
- Backup your current setup/data
- Download file and place on sdcard
- Boot into CWM recovery
- Recommended to wipe data/factory reset in CWM recovery
- Select and install the .zip you put on your sdcard
---DOWNLOAD LINKS - CWM---
Debloated deodexed rooted busybox-ed i577 stock rom and kernel
md5: 5645D032DA35923A9B00F15539D06AEA
---OTHER DOWNLOADS---
i577 ICS Deodexed System Apps
NOTE: This IS NOT CWM RECOVERY FLASHABLE!!!
md5: AC0171AD8010E54FDD7C25D33CA576B3
Empty SystemApp Flasher
NOTE: MUST place apks in the app folder within the system folder inside the zip file PRIOR to flashing
NOTE2: This is the same as what is linked in the Tweaked OP here - which is fine. This works on any blaze setup when using cwm recovery.
md5: F5B562DFCED08D8F55E5CF5EDF4DB444
Let me know if there are any problems! Also - it seems like general discussion should get pointed to here, as it's all the same thing really (read: I didn't think it warranted a new thread).
THANKS GO TO -
j3r3goss - initial letting folks know of i577 possibility and providing a link to a stock tar
2vivid and afoster1003 - bravely flashing said stock tar
thomas.raines - making things one-click easy, both to flash the rom and to return to gingerbread; helping with troubleshooting
2vivid and chjema - testing my attempts
erikmm - because I can
all of the folks in #teamfah-q
all of the folks in teamsbrissenmod, as I would know very little and be able to do even less if it weren't for them
-----------------------------
---CHANGELOG---
Final update - 10/2/12
- Somewhat fixed camera.apk
***** Viewer still appears upside down for rear camera, but all images/videos taken are correct orientation
- Changed stock boot animation
- Updated some apks
Initial Posting - 10/1/12
- Deodexed
- Took out lots of what I call bloat
***** If I took out something you wanted, use the links in the OP to get it back
***** If I left something you didn't want - let me know and I'll think about removing
- Added in SuperSU v0.96 by Chainfire (from here)
- Added busybox 1.19.4 (CM9)
- Edited Contacts.apk to avoid AT&T Subscriber checking when entering Contacts
- Added .bak to PowerOn.ogg in /system/etc/ to eliminate boot sound
-----------------------------
NOTES
Known issues:
1) Camera is upside-down
This only affects the rear-facing camera. The recent "fix" does not change the preview/viewer (the "live action" view of what the camera sees), but now all pictures or videos you take will be right-side up - so it's better than nothing I suppose
2) Softkeys/capacitive buttons no longer work
This seems to happen from time to time (though not very often by any means), in a way/manner that is as of yet predictable. That being said - all three times I have encountered this issue the below process has fixed it (thanks go to j3r3goss for providing the info needed for the solution):
- Open dialer/phone
- Type in the following in the dialer
*#*#2663#*#*
- Once the last * is entered, a new screen will show that has some information and (more importantly) two buttons. Press the BOTTOM buttom (the one that says "Touch key FW update"). Wait for this to complete (NOTE: This can take a LONG time, and you may have to reboot on your own if it hasn't said its completed its process after 10 or so minutes (my experience - no reasoning or logic behind it really, so be cautious)), then reboot the phone.
3) No WiFi Calling ability
Yep. It's an AT&T stock rom, and as they don't have the wifi calling capability, so too does this lack such fun functionality.
Reserved for something... not really sure what though. Figured I should grab it in case this little thing grows in the future - better safe than sorry I suppose.
confirmed flash good, no softkey issues
great job!
Good job man! Going to flash this tonight and make a 1 click for you with some Lightning Zap! goodies and modems (if it all works right...lol)...
saving this for later
Running great so far, definitely a lot snappier on first boot. No errors so far, glad the contact bug was fixed
There sure was a lot of bloat huh? I thought Tmo was bad lol.
Well I guess you beat me to it, way to go.
Sent from my SGH-T769 using xda app-developers app
I heard the radios were a little weak. Did you fix that in this file or is it the same?
Sent from my SGH-T769 using xda app-developers app
There are no radios included, so you keep whatever you had (and the blaze ones do seem a bit better than the exhilarate ones)
I just flashed, loving it btw, but my radios are a little weak? I factory reset, flashed the rom, factory reset again because it said to do so before reboot (idk I was a little paranoid lol) and then flashed system apps and boot.
Edit: i didnt realize earlier but all the bloat and such is remaining too? I'm gonna reflash in a bit and get back to you
Sent from my SAMSUNG-SGH-I577 using xda app-developers app
Push this apk to system to get weather working on lockscreen
WiFi calling should be able to be integrated into the ROM. It's not kernel specific, but might require some framework alterations. IMHO, it would be best to take this new ICS kernel and pair it with the OS from SGS2, that is made for T-mobile.
I haven't gotten a chance yet to look at the kernel to see if the flipped camera can be fixed there, or if just replacing it with the SGS2 camera app might do the trick.
Lots of opportunities for hacking together a great ROM from this.
Concerning the radios guys and gals!
It seems to be an ICS thing with the radios. We had the same issue on the SGS4G. They have to be padded in order to function properly since the SGS4G never got an official ICS update and we are still running on gb modem and kernel... Maybe Sammy will un-ass the update for us and all will be good...lol
thomas.raines said:
Concerning the radios guys and gals!
It seems to be an ICS thing with the radios. We had the same issue on the SGS4G. They have to be padded in order to function properly since the SGS4G never got an official ICS update and we are still running on gb modem and kernel... Maybe Sammy will un-ass the update for us and all will be good...lol
Click to expand...
Click to collapse
Yeah, I use to have a G2x with ICS and the developers always made it clear that the Radio issue is a problem with ICS 4.0.4 itself.
Sent from my SGH-T769 using xda premium
chjema said:
Push this apk to system to get weather working on lockscreen
Click to expand...
Click to collapse
how do you push it to the system? every time I try it just says it has failed
crazydrummer95 said:
how do you push it to the system? every time I try it just says it has failed
Click to expand...
Click to collapse
How are you trying to push, via root explorer (something alike) or adb?
thomas.raines said:
How are you trying to push, via root explorer (something alike) or adb?
Click to expand...
Click to collapse
Well, I tried using ES file explorer and it did not work. So I went into the root settings in the application, and I have everything checked, but when I try to mount the filesystem as writable, it says "failed to mount". I tried setting it as rw in adb, and it said it was a read-only file system
Es never worked for me with the root functions. Always has to use root explorer or adb
Sent from my SGH-T769 using xda app-developers app
skullreapper66 said:
Es never worked for me with the root functions. Always has to use root explorer or adb
Sent from my SGH-T769 using xda app-developers app
Click to expand...
Click to collapse
But the problem is that everytime I try to push a file to /system in ADB it says that its a read-only file system