Related
Please Read
This will not change anything on your phone that would prevent you from ever flashing a new rom or nandroiding back to a working one. Everything this update will do can completely be erased with a wipe or nandroid. Also flashing any rom, clean install or not, will preplace the boot.img this update.zip puts on your phone. So dont blame these downloads for your simple user errors of not being able to flash a new rom or nandroiding.
This is an overclocked kernel from toastcfh godmode .29 source. The kernel was actually pulled from Fresh Toast
This works on DamageControl and roms based off of his, it will not effect any of DC mods, including the Dconig app.
UPDATE
6/6/10- This should be working on the newest damagecontrol 2.09. Please report (if overclocking has worked in the past for you) if you have a problem on the newest release.
Click to expand...
Click to collapse
I made an attempt to get compcache to work, so it might or it might not. Someone with more experience might want to double check it.
Both include setcpu.txt for Setcpu OC app.. Select "custom" at the very bottom for device. Do not select hero. Or you can select "Auto Detect" at the top, this does not need the setcpu.txt.
*View attachment damage710v2.zip* THIS IS A TEST KERNEL FOR THE NEWEST DAMAGECONTROL 2.09.. It is the exact same as damage710 but with a newer ramdisk, this is in hope of fixing any problems anyone is having with 2.09 and OC kernel. There might not even be a difference in the new ramdisk between the old one. I didnt have time to check. Sooo ya.
*View attachment damage537.zip* 537mhz is the default.. scalable to 768 if you use an OC'ing app
*View attachment damage768.zip* 768mhz default clock speed -read below
*View attachment damage710.zip* 710mhz default clock speed -read below
Both can be scaled from 19.2 to 768mhz..
DAMAGE710--The damage710 will default 710mhz, you must use an OC app to scale it to 768. Use damage710 if your phone can not boot the 768mhz. And dont scale any higher then 710mhz or your phone might reboot.
DAMAGE768--If your phone can boot the 768mhz then either download will work. But if you dont want to use an OC'ing app then the damage768 will scale to 768mhz.
This IS a flashable update.zip.. This will only replace your boot.img of your phone. So it is not a full rom. This is applied on top of your rom.
ALWAYS MAKE A NANDROID BEFORE FLASHING.
You Do Not Need A Partition On Your Sdcard For Overclocking
THIS IS A MUST FOR SWAP/compcache
To get swap working, you must have an ext partition on your sdcard. This will format you sdcard erasing everything, so do the following. Back up everything from your sdcard to your computer(exp- In a folder on your desktop named Sdcard). In recovery, select partition sdcard, use all default values, 32mb swap, 512mb ext partition, the rest fat32. Then when its finished change ext2 to ext3. Then reboot the phone. And then move all the files you backed up to the computer back to your sdcard.
If thanking me for putting this together. You should also give an even bigger thanks to Toastcfh for this kernel.
Thanks also goes to flipzmode, cuz i pulled the kernel from his boot.img in fresh toast.
Also darchstar for the defaulting clock speed tip.
So does this mean we can get the real AOSP dialer on Damaged's ROM?
mattshaver said:
So does this mean we can get the real AOSP dialer on Damaged's ROM?
Click to expand...
Click to collapse
No.. this just adds overclocking and the few extra things that come along with it in the kernel. Has nothing to do with AOSP.
you rock
10 char
Excuse my ignorance on this topic.
But with Darchdroid, the issue was porting the Eris .29 Kernal to get a full hardware working AOSP Rom (I think) , so what is the difference?
My apologizes for taking up the space with my questions. Just a noob trying to get his facts straight.
If anyone wants to know how to do this, follow this guide starting at Step 8.
Essentially just extract the kernel you want from the right boot.img, extract the ramdisk from the other boot.img, then use mkbootfs and makebootimg to put them back together.
PM me if you need help.
mattshaver said:
Excuse my ignorance on this topic.
But with Darchdroid, the issue was porting the Eris .29 Kernal to get a full hardware working AOSP Rom (I think) , so what is the difference?
My apologizes for taking up the space with my questions. Just a noob trying to get his facts straight.
Click to expand...
Click to collapse
I dont mind, ask anything here. Its how we learn
But that was the issue with all 2.1 roms. Toastchf cracked the code (in a way, not literally). And was able to give us a working source for .29 kernel. That kernel can then be used to work on any cdma hero 2.1 rom. But there are different things you have to do to get it to work on Darchdroid AOSP rom, he has already done that and its in his newest release. This one I posted above is just to work with damagecontrol roms or ones based off of it.
To get the AOSP dialer working you would have to have a rom based on AOSP, which darchdroid is the only rom so far. All the other roms are based on htc framework or just something different then AOSP. But im pretty sure theres AOSP dialers for damagecontrol. Go check the apps and themes section.
EDIT: the dialers are also completely separate from the kernel. Its based on what the rom is.
i'm running ic3rom and in the process testing it out
jeremysterling said:
i'm running ic3rom and in the process testing it out
Click to expand...
Click to collapse
If you downloaded the compcache one, can you go into terminal and type
adb shell
free
Tell me if it says "swap" in what comes up and that it doesnt have all 0's.
ive been running the 2.07.2.3333 with jit enabled for weeks now flawlessly..... will flashing this zip cause the jit to stop working... or will they work in unison like i want? if its a one or the other deal ill just keep jit... thanks for your help
I think I may be confused as to what exactly the kernel's role/job is, as well as to what the drivers role/function are.
a kernel is what tells the hardware how to interact with the software, and drivers are what tell the software how to interact with the hardware? Correct?
So, why would it take a different kernel to run a full AOSP ROM? Why not just write new drivers for the difference of hardware?
On another topic. The framework would be comparable to what CounterStike is to Half-Life. It still uses the underling software, but is modified and branded in its own way as to give such a "proprietary" feel?
I am so confused. (Google here I come)
schmooo said:
ive been running the 2.07.2.3333 with jit enabled for weeks now flawlessly..... will flashing this zip cause the jit to stop working... or will they work in unison like i want? if its a one or the other deal ill just keep jit... thanks for your help
Click to expand...
Click to collapse
It doesnt effect jit at all. It only adds a few files and changes your boot.img.
schmooo said:
ive been running the 2.07.2.3333 with jit enabled for weeks now flawlessly..... will flashing this zip cause the jit to stop working... or will they work in unison like i want? if its a one or the other deal ill just keep jit... thanks for your help
Click to expand...
Click to collapse
JIT is controlled by other variables, namely build.prop and the dalvikvm.so library; it won't hinder those settings at all.
Jus10o said:
If you downloaded the compcache one, can you go into terminal and type
adb shell
free
Tell me if it says "swap" in what comes up and that it doesnt have all 0's.
Click to expand...
Click to collapse
i used adb on my computer (not sure if that makes a difference):
C:\androidsdk\tools>adb shell
# free
free
total used free shared buffers
Mem: 195764 193404 2360 0 7384
Swap: 0 0 0
Total: 195764 193404 2360
#
Re: [KERNEL] Toast-godmode .29 source for DamageControl
So I can flash this and oc icerom? Etc....
-------------------------------------
Sent via the XDA Tapatalk App
mattshaver said:
I think I may be confused as to what exactly the kernel's role/job is, as well as to what the drivers role/function are.
a kernel is what tells the hardware how to interact with the software, and drivers are what tell the software how to interact with the hardware? Correct?
So, why would it take a different kernel to run a full AOSP ROM? Why not just write new drivers for the difference of hardware?
On another topic. The framework would be comparable to what CounterStike is to Half-Life. It still uses the underling software, but is modified and branded in its own way as to give such a "proprietary" feel?
I am so confused. (Google here I come)
Click to expand...
Click to collapse
Haha well you are right sorta on what the kernel does, but all cdma htc heros use the same kernels but it depends on what android version you are using. 1.5 uses .27 kernel, and 2.1 can use a edited .27 kernel but something things wont work, like camera. What toast did was made his own .29 kernel based on other sources and what we already have then we use for our 2.1 roms. The 2.1 roms that come from sprint use a .29 kernel that work, but we cant edited anything within the kernel until they release the source to the kernel. You must have source to the kernel to be able to change anything with in it. You cant download a rom from xda and take the kernel out and change the files and put them back. You have to already have the files to the kernel, change what you want, make your own kernel and then put it on the rom. Cuz once you compile the kernel its not able to be opened back up.
In a boot.img there are 2 parts, the kernel and a ramdisk. The ramdisk CAN be opened back up and changed. But if its trying to call something within the kernel it has to already be there, since you cant add anything to it. If you start with all the kernel files and compile your own like what toast did, then you can add the special things like overclocking frequencies.
I know I really suck at explaining things. I only know the basics of how it all works.
jeremysterling said:
i used adb on my computer (not sure if that makes a difference):
C:\androidsdk\tools>adb shell
# free
free
total used free shared buffers
Mem: 195764 193404 2360 0 7384
Swap: 0 0 0
Total: 195764 193404 2360
#
Click to expand...
Click to collapse
And you have the compcache.. or the newer one i posted?
Jus10o said:
It doesnt effect jit at all. It only adds a few files and changes your boot.img.
Click to expand...
Click to collapse
Decad3nce said:
JIT is controlled by other variables, namely build.prop and the dalvikvm.so library; it won't hinder those settings at all.
Click to expand...
Click to collapse
sweet im gonna give it a try
Jus10o said:
And you have the compcache.. or the newer one i posted?
Click to expand...
Click to collapse
i downloaded and flashed damage1.zip with compcache
jeremysterling said:
i downloaded and flashed damage1.zip with compcache
Click to expand...
Click to collapse
Ok thanks.. yea compcache and swap arent working. Ill work on it.
But overclocking and everything else is. So its not gunna make a noticeable difference.
Hello, I'm new to all this Android stuff (I don't even have a phone yet, but its on it way)
I have been reading up on custom ROM creation but there are some things I don't quite understand.
Let's say I have a phone in Android 2.3. I want to create an Android 4.0 ROM to put on the phone.
Now... to compile Android 4.0 I need the drivers for my phone (which I doubt I will ever have access too since its only a cheap Android with a MediaTek CPU)
So I have a 2.3 ROM that contains all the compiled drivers and the Android 4.0 source code.
Is it possible to compile 4.0 and replace the zImage (if I'm correct) with the 2.3 zImage. From what I have read, that's where all the drivers are stored.
I guess its not that simple since I also think the zImage contains the OS. If so, is it then possible to extract the zImage and replace the invalid driver files in 4.0 with the correct drivers from 2.3?
Also, I think my phone will arrive with an annoying UI, is it possible to just get any 2.3 ROM (that doesn't have an annoying UI and shares the same CPU as my phone) and replace the zImage in that with my phones 2.3 zImage?
Sorry, if my questions are stupid but this is all new to me. I've tryed to read up on this but nothing is straight to the point.
Thanks
Anyone there?
try out some roms first. see what you like and dont like. it'll probably give you a better idea for how you would make your own rom.
I don't think you could just port an entire zimage to ICs and say it will work (it might not even compile i think). It won't work. You could probably take some drivers' code (screen, speaker, etc), modify them a bit so it compiles, and test to so if it works. You more than likely have to modify the ICS code also so it works. And the zimage is just the kernel no? And the kernel really only has to do with low level system processes, drivers, etc. I think UI's and such are more fitted in frameworks and such.
Personally if it was so easy to port ICS by simply replacing the zimage or file with another, ICS would have been ported to many devices, fully working, by now.
Kailkti said:
I don't think you could just port an entire zimage to ICs and say it will work (it might not even compile i think). It won't work. You could probably take some drivers' code (screen, speaker, etc), modify them a bit so it compiles, and test to so if it works. You more than likely have to modify the ICS code also so it works. And the zimage is just the kernel no? And the kernel really only has to do with low level system processes, drivers, etc. I think UI's and such are more fitted in frameworks and such.
Personally if it was so easy to port ICS by simply replacing the zimage or file with another, ICS would have been ported to many devices, fully working, by now.
Click to expand...
Click to collapse
Yeh, but my problem is I don't have the drivers for the phone. I just have the stock ROM that come with it.
Is not that simple. I am 99% sure that you can't do that.
The phone I'm getting has a horrible theme on it. Its running Android 2.3
I have the ROM for a very similar phone (also using Android 2.3), uses the exact same CPU so it should be compiled using the correct platform.
Is it possible to use that phones ROM but replace it with my phones Kernel and .prop (so it has all my phones drivers and settings etc...)?
the hard work required in making a custom rom
I think you can take from the stock rom and compared with existing custom rom
but some sources are not shared freely as an example Tegra
CMIIW
I will mess about with the ROM when I get my phone. Hopefully I wont brick it...
I too am fairly new to android. I spent a couple weeks reading and watching TONS of youtube videos on how to ROOT and Unlock my bootloader. My best advice from one n00b to another would be to do the same. In particular...research how to do it on YOUR phone. Also, Roms are device specific. I recommend you finding the forum here on XDA for your phone and read up on whatever ROMS are available here. This might not be the ONLY place to find ROMS, but this place simply rocks! Once you get your device rooted and if necessary, your bootloader unlocked...you can easily try out any ROM without much fear. Just make a good backup...make sure you also have a factory recovery image too...just in case. For backups...if you install and use Clockwork Mod (CWM) you can use the nandroid backup it offers. I bought Titanium backup from the market and used it to do a full backup before I started...it backs up to dropbox even, which was a nice feature for me. Extra safety so incase I hosed my external SD card which had my backups...I could easily retrieve a backup ANY place that had internet access. Lastly...get ready to have some FUN! Flashing ROMs is VERY addictive!! :-D
Ok, Thanks. I will see what I can do then.
Hey all, buying an XT720 today.
Looking to get it up from 2.1
What is the most stable update at the moment?
I have done CM 6.1 on a HTC Dream, was pretty happy with it.. would like to get up to 2.3 on this..
Suggestions? I am using Wind Mobile in Canada for this phone if it makes a difference.
James
Hi
Their are choices cm6 is very stable
I would try flfalcon cm7.
Their are J.Y.Daddy cm7 these were made for the motorio to use these you would need to apply bootfix.
J.Y.Daddy even ported miui ics 4.01.
You need check out the development page.
Sent from my XT720 using xda premium
I also have a list of most of the ROMs and their +/-'s. Ill find the link and post it. I'm mobile now so can't find it that way.
Im on wind also and i truthfully find bravo the best.... everything is really stable and HD cam and whatnot works
Here is a somewhat dated list but a list nonetheless and here is the thread it came from.
http://forum.xda-developers.com/showthread.php?t=1298208
Woodrube said:
There are a host or ROMs for this phone right now and it is quite hard to narrow down to "The Best". Each as their own +/-'s and while one might be a monster in speed, it might have poor muti-tasking or bad camera. Here are some of the ROMs we have and some of the +/-'s they have (not all, just some +/-'s).
In no particular order other than the top came out first and bottom is the latest.
2.1 Stock - Came with the phone. You can falsh via RSDlite the sbf file for your region.
2.1 Stock~ESB (Eclair Strikes Back) - Same as above, but has aorking app2ext, camera, FM Radio. Still it is 2.1
Dexters 2.2 with MZ patch - First successful attempt to port 2.2 to our phones. All features of 2.2 but camera is sketch and FM radio doesn't work (unless you apply FJfalcon radio patch but then it is still loud), media button doesn't work.
Kahlpower's V2/3/4 - Optimized version of Dexters. Same issues as above but is more stable and generally was the choice as a "home" ROM for many users. I have my wife on this one as we speak. Low maintenance, a good everyday driver. Has App2ext/ Link2sd, native Froyo App2sd.
Cincinnati Bell's "official" 2.2 - More or less a glorified version of Dexters 2.2 but I think the Mioz7AE found a "listening" script that may or may not send info back to developer. I would stay away from this one. Plenty more to choose from.
Wanhu 2.2 (also Wanhu's Kahl's Optimized) - Korean port of 2.2. FM radio and camera does work. Number formatting is off. App2ext works fine as does native Froyo app2sd.
XDA Special/ Hellmonger Edition - This was moveing really well and then Hellmonger's phone crapped out on him and his carrier gave him an HTC Penache, so no more support for this one. But is DOES work and worth a try.
CM6 - our developer Mioze7Ae's masterpiece (for now until he moves on to something else) All the features of CM6, including themer. Has App2ext and Link2sd.
WIPs
Brianlili's Brovo 2.2 - This one is almost done, jsut a few little thing to finish it off.
JYDaddy's CM7 (nightly/ HoNo/ iceandfire...)
FJfalcon's CM7.1 (make massive progress daily on this one as it is being built from source).
Like I said there are +/-'s to each but the are all spelled out for you in the OP of each thread. Plus, unlike other phone forums, we actually answer your questions and dont respond with, "search".
Good luck and remember to always BACK UP.
Click to expand...
Click to collapse
S7icky said:
Im on wind also and i truthfully find bravo the best.... everything is really stable and HD cam and whatnot works
Click to expand...
Click to collapse
Where is this Bravo??
Also I have rooted..
but I have not found a good guide on Openrecovery. (EDIT) got this done, went through ADB shell.
I unzip the the openrecovery to the sd card.. gives me openrecovery.zip a directory and an images directory.
SO then to flash a new rom I just put the .zip file in the updates directory.. and bingo bongo?
Going to try Cyanogenmod 7.1 first.. not sure where to find the brovo? bravo? mentioned.
James
Custom Recovery is here
http://forum.xda-developers.com/showthread.php?t=1242259
Bravo is here
http://forum.xda-developers.com/showthread.php?t=1332410
All ROMs and Mods are in the Dev thread.
I vote for CM6 RC3 / RC4
it's by far the most stable & fast which allows you to run most resources intensive games
AllGamer said:
I vote for CM6 RC3 / RC4
it's by far the most stable & fast which allows you to run most resources intensive games
Click to expand...
Click to collapse
I might give this a try next.. I have bravo tweeked out.. and I like it for the most part.. but there are somethings that dont seem to work as well as my G1.
I will just save my current phone in nand and then I can just reload it all back in - correct??
James
Yes
10chars
this one fjfalcon's CM7 , http://forum.xda-developers.com/showthread.php?t=1350453
Nandroid and battery
I just bought an XT720 (Rooted and unlocked)
Is there any way to change the battery level increments from 10% to something more exact like 5% and how do we create a Nandroid back up?
I also want to install bravo2.2 do I need to do a factory reset before installing this rom?
I am running stock rom 2.1
Well if its Rooted, then you should have Open Recovery on it.
When you boot the phone hold VOL up and it will boot in OR...
or when you power off.. it should give you the option to reboot into RECOVERY.
There are lots of threads on here about OR .. but if you follow the menus you should be fine.. on an XT720 you push the camera button (big one) to accept a selection in the OR menu.
You can back up - which will save EVERYTHING.. a Nandroid backup is the best thing to store away somewhere should you mess up your phone.
YES you will have to loose everything when switching from 2.1 to (anything else)
If you are just updating to a newer build of something you put on.. then no.
You do the RESET and clear caches etc.. in OR.
Do a search its all on here .. usually the first page of whatever rom you want to TRY.
Have fun.
James
Thanks for the reply, time to install some rom's
Hilarious...after wading thru a few hundred pages of replies on this phone and the various roms, I completely missed your thread here James which is about as close to what I'm trying to accomplish as imaginable..
I posted some of my saga over here: http://forum.xda-developers.com/showthread.php?t=1399242
Do you mind me asking James/BikerBob...how did you make out? Anything I should know (if you have a sec read my long winded post lol!)
Did you have 3G/Wifi switching issues with stock, or maybe you didn't bother testing that / noticed it..before rooting I mean..
thnks!
(don't know if mods merge threads in this forum but mine is probably a candidate! sorry!)
racer321 said:
I just bought an XT720 (Rooted and unlocked)
Is there any way to change the battery level increments from 10% to something more exact like 5% and how do we create a Nandroid back up?
I also want to install bravo2.2 do I need to do a factory reset before installing this rom?
I am running stock rom 2.1
Click to expand...
Click to collapse
No, kernal(maybe driver) can't support 5% or 1% percentage battery level.
OK, so I decided that changing the SD card to a class 10 might help app usage ..
I copied the old sd card to the new one.. and if I try and get into OR .. I get the exclimation mark in triangle instead of the OR logo.
What do I need to do to get back into OR? do I need to RE-Root?
James
If you don't have it already, grab Mioze's modded OR for the xt720 & follow the instructions. If that's all you did was to switch sdcards there should be no need to redo everything.
Sorry, never mind the OR issue, my bad.
I have played with this too much.. lol.. get things mixed up..
I had the OpenRecovery.zip from one version mixed with the directory of the other..
Jezz
OR runs from the files on the sdcard (the openrecovery folder & openrecovery.zip) if something is corrupted (or missing) you wont be able to boot into OR.
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
Is it actually possible to use fuse to mount my external SD card when it is formatted with ext4 when on a TW ROM on my VZW GS3?
From reading, it seems like it should be possible, but nothing I have tried has worked. Seems like CM/ASOP does it automatically but when trying to duplicate it on TW, I've hit a wall.
I've read that you need a custom kernel to do it, but not sure which kernels support it as I'm not sure what needs added in order to support this. Is it some module that needs compiled in or just support for inet.d? Since even stock supports ext4, I'm guessing inet.d is all that's needed, meaning the stock kernel with inet.d support added should work, but I'm willing to use other kernels. (Tried lean, Zeus, and a couple others I can't think of off the top of my head but had no luck.)
If someone can direct me to a howto or give instructions that work for the GS3 on TW, I'd appreciate it. The ones I've been able to find via search, I've not had any luck getting to work. If using fuse won't work, but directly mounting it does, that would work for me as well as my Windows machines are able to read ext file systems. Fuse would be more convenient for plugging into other PCs though. (Maybe I'll install the ext drivers on all the computers in the district as part of the summer updates...)
--
Tapatalked from my VZW Galaxy S III.
Bumping this in hopes that someone knows the answer and just didn't notice the post.
Stock kernel and Anthrax kernel are the only two I know that support ext4 on TW. Anthrax is invite only currently. So that leaves stock pretty much.
countryfolk07 said:
Stock kernel and Anthrax kernel are the only two I know that support ext4 on TW. Anthrax is invite only currently. So that leaves stock pretty much.
Click to expand...
Click to collapse
You wouldn't happen to know how to get it to recognize my ext4 SD card would you? I've yet to be able to get it to mount. I'll flash stock back on and give it another try.
--
Tapatalked from my VZW Galaxy S III.
countryfolk07 said:
Stock kernel and Anthrax kernel are the only two I know that support ext4 on TW. Anthrax is invite only currently. So that leaves stock pretty much.
Click to expand...
Click to collapse
You sure stock kernel supports ext4?