AOSP ICS pre-alpha now available.
With the release of the kernel source i was able to hack pmem to get it mostly working. Its still broke and needs fixed proper. But is ok for now.
Working:
Bluetooth
HWA (mostly)
Most (maybe all) Sensors (Gyro,compass,rotation,proximity,light)
Wifi
Click to expand...
Click to collapse
Broke:
GSM calls data sms (everything radio)
many other things (no need to report them)
Click to expand...
Click to collapse
**Only flash if you already have ics. I flashed whatever ruu was leaked a few weeks ago.
**You must have and unlocked bootloader
**I am s-off with the eng bootloader. I highly doubt that is needed. Before i did that i was able to flash with just being unlocked.
**If you get a bootloop it's cause the boot.img didn't get flashed. You need to look up how to do that.
**NOT FOR DAILY USE**YOU'VE BEEN WARNED**
DOWNLOADS
Evervolv-Iaceo-2.2.0p1-ruby: (7/11)
Initial Release:
ZIP: http://goo.im/devs/evervolv/20120711/Evervolv-Iaceo-2.2.0p1-ruby.zip
OMG, soo close to my dream. Thanks so much in advance and keep up the good work! I won't be testing as I use my phone for business, but look forward to this maturing.
Isn't evervolv x's?
Sent from my HTC_Amaze_4G using Tapatalk 2
Flipnfr3ak said:
Isn't evervolv x's?
Sent from my HTC_Amaze_4G using Tapatalk 2
Click to expand...
Click to collapse
No. Texasics is part of Evervolv. Texas and X were working together before.
this is cool, do you suppose you and sportsstar89 could hook up and share ideas. (since you two are smart in the aosp area)
Yess!!!!!
Sent from my HTC_Amaze_4G using XDA Premium HD app
Alright. Let's keep the thread for development purposes only.
Try using our ril blobs instead of the skyrocket ones. I haven't tested it or the one s libs yet though. Also copying rild is usually not necessary after comparing with the one series
Sent from my HTC_Amaze_4G using xda premium
Woooaahhh, hope this gets fixed asap ^___^
Sent from my HTC_Amaze_4G using xda app-developers app
Related
A new leak has shown up.
Pure Stock:
http://minus.com/mbfFf1ZHwR
https://rapidshare.com/files/4176456401/rezound_ics_androidpolice_3.11.605.22.zip
https://rapidshare.com/#!download|1...639511|R~433652DA5B6A28056726434541730E53|0|0
http://lts.cr/Be5_
Team Bamf Rooted Version (NOTE: HAS PROBLEMS RECOGNIZING SD CARDS)
http://www.teambamf.net/f59/[rom]3-11-605-22-stock-rooted-debloated-possible-ics-ota-4623/
Story on Android Police:
http://www.androidpolice.com/2012/0...id-4-0-build-3-11-605-22-for-the-htc-rezound/
Yay! Ruu? Is this safe to flash over rooted gingerbread? I don't care if I lose root. At all. My phone won't flash ics roms the normal way
Sent from my ADR6425LVW using xda premium
I was told this one was coming
con247 said:
I was told this one was coming
Click to expand...
Click to collapse
Actually team bamf has you covered. It looks fine.
Can I put this on a non rooted rezound
Sent from my ADR6425LVW using XDA
sped_13 said:
Can I put this on a non rooted rezound
Sent from my ADR6425LVW using XDA
Click to expand...
Click to collapse
If your willing to flash it even though it's a leaked version and not the official
sent from my sexy Htc Rezound
okay I'll hold of my wife won't let me touch her phone anyways lol
Sent from my ADR6425LVW using XDA
sped_13 said:
Can I put this on a non rooted rezound
Sent from my ADR6425LVW using XDA
Click to expand...
Click to collapse
Yep.
Sent from my ADR6425LVW using xda premium
I think it is the offical OTA
All i want are custom ICS kernels.
mighty_markus12 said:
All i want are custom ICS kernels.
Click to expand...
Click to collapse
wont get that until our precious HTC releases their kernel sources which could be a while considering they havent released htc sensation/xe kernel sources for ics yet
mighty_markus12 said:
All i want are custom ICS kernels.
Click to expand...
Click to collapse
Well we should get source soon after this is official.
Still no go on Sense 4.0 (screen caps show 3.6 still)
Hopefully HTC plans to release Sense 4.0 on the Rezound.
ih8mydroid said:
Still no go on Sense 4.0 (screen caps show 3.6 still)
Hopefully HTC plans to release Sense 4.0 on the Rezound.
Click to expand...
Click to collapse
It will be 3.6 I'm afraid
Sent from my ADR6425LVW using xda premium
JoelZ9614 said:
wont get that until our precious HTC releases their kernel sources which could be a while considering they havent released htc sensation/xe kernel sources for ics yet
Click to expand...
Click to collapse
Yeah i know, was just saying.
Ya I don't think they're planning on changing the sense version yet.
Sent from my ADR6425LVW using xda premium
That site is getting bombed. If anyone can post a mirror please do
Sent from my ADR6425LVW using xda premium
I want to see what HTC has accomplished with this "OTA" version of ICS!
+1 on custom kernels!
Lol. This is looking to be a great weekend, though I feel sorry for all the devs who are going to be locked away in front of their computers for the next 24 to 48 hours re-basing/creating from scratch the crack that we are addicted to.
A BIG THANKS to all the great devs and all their hard work! We do greatly appreciate what you do and for putting up with us!
Ill be desensing anyways until aosp comes.
JoelZ9614 said:
wont get that until our precious HTC releases their kernel sources which could be a while considering they havent released htc sensation/xe kernel sources for ics yet
Click to expand...
Click to collapse
They probably plan on releasing the family all at once.
aostl said:
Ya I don't think they're planning on changing the sense version yet.
Click to expand...
Click to collapse
They might not change it. Have they upgraded Sense versions much before? I know the Incredible never got a new Sense.
Has anyone built cm7 for the Rezound? I know I'm going backwards, but I want a stable, fully functional aosp rom til ics kernel source is released. I've searched, but don't see anything
Sent from my ADR6425LVW using xda app-developers app
No.
All efforts are being made for ics....working in gb would be counter productive since its been replaced by ics, and the work wouldn't translate to ics.
That's from what I've heard the last few months....
Sent from my ADR6425LVW using xda app-developers app
ericsignals said:
All efforts are being made for ics....working in gb would be counter productive since its been replaced by ics, and the work wouldn't translate to ics.
That's from what I've heard the last few months....
Sent from my ADR6425LVW using xda app-developers app
Click to expand...
Click to collapse
I'm not sure if there's a base for a 720p resolution lol
haliwa04 said:
Has anyone built cm7 for the Rezound? I know I'm going backwards, but I want a stable, fully functional aosp rom til ics kernel source is released. I've searched, but don't see anything
Sent from my ADR6425LVW using xda app-developers app
Click to expand...
Click to collapse
this should be possible now that chad has a working ril on gingerbread kernel.
synisterwolf said:
this should be possible now that chad has a working ril on gingerbread kernel.
Click to expand...
Click to collapse
Kernel doesnt impact the RIL version wise. To my knowledge you would have to rewrite a new java RIL
Ok I have been working on getting wimax working in the evervolv jellybean build. I have spent the week only about an hour a day (darn kids won't leave me alone 8)) setting it all up. Im able to bring up the wimax menu and attempt to connect. My problem is that i can get the wimax server to start. If I rip apart cm10's boot img and input my kernel leaving everything alone it boots up wimax server and im able to run with no problem well other problems because im using a little different setup. So I have it down to the boot img specificly the files inside initrd.img. I have reviewed all those files and can't seem to find anything wrong. Everything is setup properly from what i can tell. Im stuck and i know there is alot of great people on this fourms that will help me . I have a github with my device tree and kernel for review https://github.com/flintman
Pre thanks
flintman said:
Ok I have been working on getting wimax working in the evervolv jellybean build. I have spent the week only about an hour a day (darn kids won't leave me alone 8)) setting it all up. Im able to bring up the wimax menu and attempt to connect. My problem is that i can get the wimax server to start. If I rip apart cm10's boot img and input my kernel leaving everything alone it boots up wimax server and im able to run with no problem well other problems because im using a little different setup. So I have it down to the boot img specificly the files inside initrd.img. I have reviewed all those files and can't seem to find anything wrong. Everything is setup properly from what i can tell. Im stuck and i know there is alot of great people on this fourms that will help me . I have a github with my device tree and kernel for review https://github.com/flintman
Pre thanks
Click to expand...
Click to collapse
Good luck Flintman!! I'll be cheering you on!!:highfive::good:
evervolv JB is a source built rom....
if you set up your github and repos to sync evervolv
then all u need to do is fork cmwimaxsettings
then cherry pick two commits to add the wimax
PM me for links and details
Lens_flare said:
evervolv JB is a source built rom....
if you set up your github and repos to sync evervolv
then all u need to do is fork cmwimaxsettings
then cherry pick two commits to add the wimax
PM me for links and details
Click to expand...
Click to collapse
It's not as easy as that... We had to do some more modifications to get it working tonight (flintman and myself). Seems that most aosp jellybean builds had been using a prebuilt HTC init binary, but we figured out how to get around this. At least everything seems to be working properly now. Flintman will be testing it out later tomorrow morning.
Working Great. I posted under comments in gerrit. I notice one more small thing.
So hows the progress
Sent from my PG86100 using xda app-developers app
thatboiken said:
So hows the progress
Sent from my PG86100 using xda app-developers app
Click to expand...
Click to collapse
Go check the evervolv thread............this thread was just used to discuss things
Wimax already works on Evervolv....lol
thatboiken said:
So hows the progress
Sent from my PG86100 using xda app-developers app
Click to expand...
Click to collapse
Latest Nightly includes the Wimax and it is working very well.
preludedrew said:
It's not as easy as that... We had to do some more modifications to get it working tonight (flintman and myself). Seems that most aosp jellybean builds had been using a prebuilt HTC init binary, but we figured out how to get around this. At least everything seems to be working properly now. Flintman will be testing it out later tomorrow morning.
Click to expand...
Click to collapse
Thanks for the headsup....
forgot AOSP is alot different than CM10
and may depend on some different things
Im glad to see you got it up and running
Sorry I have been very busy this is working in evervolv. The status bar indicator isn't working yet. I'm on hold with that until 4.2 has been fully merge. Once the merge is complete I want to fix the indicator then move onto another broken feature. Thanks to prelude for the help in getting a fully working WiMAXwith thether capabilities
Sent from my PG86100 using xda app-developers app
Random question has anyone got 4g to work in a sense 4.0 rom?
Sent from my Evo3D using xda app-developers app
thatboiken said:
Random question has anyone got 4g to work in a sense 4.0 rom?
Sent from my Evo3D using xda app-developers app
Click to expand...
Click to collapse
Supposedly newtoroot has http://forum.xda-developers.com/showthread.php?t=1981551 BUT he's yet to put out anything OTHER then screenshots hahahaha
Mazda said:
Supposedly newtoroot has http://forum.xda-developers.com/showthread.php?t=1981551 BUT he's yet to put out anything OTHER then screenshots hahahaha
Click to expand...
Click to collapse
Well you gotta trust the guy, he is the one that started all of the sense 4 Rom fad in the 3d forums
Sent from my PG86100 using Tapatalk 2
No update since last month but thanks anyways
Sent from my Evo3D using xda app-developers app
VictoriousShooter said:
Well you gotta trust the guy, he is the one that started all of the sense 4 Rom fad in the 3d forums
Sent from my PG86100 using Tapatalk 2
Click to expand...
Click to collapse
Didn't say I don't trust him, just said it was only screenshots
I'm sure there's other things to be worked out with wimax on sense 4.0 and when is ready, it'll come........WHEN will it come? Who knows hahahahaha
Mazda said:
..WHEN will it come? Who knows hahahahaha
Click to expand...
Click to collapse
The day after I upgrade in July to the newest Evo.
coal686 said:
The day after I upgrade in July to the newest Evo.
Click to expand...
Click to collapse
Not before I get mine in april
are there wimax drivers that are released, i want to experiment putting wimax in a sense 4 rom
You know I have posted in my public github how I got Wimax working in my MIUI jb builds although I haven't updated it on there since September. What I've learned while trying to get it to work on sense based ROMs is that HTC has about 10000 lines of fairly useless code to sort through to get it going. In most sense ROMs for our device, and of course this is all smali, everything you need is in framework.jar, only the connection service email in services.jar, wimax.jar of course, and believe it or not the bear of the whole thing Settings. apk. Settings is where my focus has been on DH Miui ICS. See settings has all the action for the most part such as all the messy HTCPreference* classes. Those classes are crazy in the sense that there are so many events triggered in each one that most of my days trying to get it to work have been spent trying to follow all of these events to see which ones are necessary and which aren't. The Aosp wimax on our devices only requires a third of that editing and the rest is getting the right libs and modules for the most part. If you do a grep of the word wimax after decompiling everything in the sense roms you'll see all of the places you need to mess with and sometimes write your own smali classes from scratch for the most part. I believe someone could do it without much difficulty but its the time it will take that's most likely the hardest part. As long as you have the correct binaries.
Sent from my Evo 3D CDMA using Tapatalk 2
cmbaughman said:
I believe someone could do it without much difficulty
Sent from my Evo 3D CDMA using Tapatalk 2
Click to expand...
Click to collapse
I vote for you to be that someone.
I've been watching development progress on this since I bought this phone back in March. I'm running one of the latest CM9 builds and while it runs very well, there are still a number of issues with it in terms of stability and functionality. As we know, development on CM9 has mostly come to a standstill.
I've been excited keeping up with the CM10 progress and how it seems to be coming to a usable and relatively stable state, however now I'm reading everybody is working on getting CM10.1 booting instead of continuing to fix the issues with CM10.
Now I don't want to seem unappreciative of the work our developers do on their free time, but what's the point of all of this effort if it doesn't result in a good, usable product?
cloakzore said:
I've been watching development progress on this since I bought this phone back in March. I'm running one of the latest CM9 builds and while it runs very well, there are still a number of issues with it in terms of stability and functionality. As we know, development on CM9 has mostly come to a standstill.
I've been excited keeping up with the CM10 progress and how it seems to be coming to a usable and relatively stable state, however now I'm reading everybody is working on getting CM10.1 booting instead of continuing to fix the issues with CM10.
Now I don't want to seem unappreciative of the work our developers do on their free time, but what's the point of all of this effort if it doesn't result in a good, usable product?
Click to expand...
Click to collapse
What exactly makes cm9 unusable? As far as I know blue tooth (Edit) and MHL are the only things that have yet to be perfected. I've run a couple cm9 builds that really blow jb on my friend's phones away.
Sent from my ADR6425LVW using Tapatalk 2
With everything 100% working? No you won't. Blame it on HTC, not us.
And cm9 runs fine. 10 runs great but has a purple camera and the FFC isn't likely to get fixed easily, if ever. We don't have the jb blobs for it. And the ICS blobs only support pmem.
Can always go back to pmem for everything but it runs terribly then.
The point is I like to tinker and problem solve. Brain exercise so to speak. I don't release ROMs for this reason. I have zero desire to provide support for them. I personally just like to see what I'm able to do and build skills.
Sent from my ADR6425LVW using xda app-developers app
chad0989 said:
With everything 100% working? No you won't. Blame it on HTC, not us.
And cm9 runs fine. 10 runs great but has a purple camera and the FFC isn't likely to get fixed easily, if ever. We don't have the jb blobs for it. And the ICS blobs only support pmem.
Can always go back to pmem for everything but it runs terribly then.
The point is I like to tinker and problem solve. Brain exercise so to speak. I don't release ROMs for this reason. I have zero desire to provide support for them. I personally just like to see what I'm able to do and build skills.
Sent from my ADR6425LVW using xda app-developers app
Click to expand...
Click to collapse
And I must say you do it extremely well
Sent from my ADR6425LVW using Xparent ICS Tapatalk 2
CM9 is extremely stable. I have used it as a daily driver for a long time now.
I have had CM9 on here longer than any other ROM even stock.
We need someone like Linus Torvalds around here.
HTC doesn't give support to developers?
*cue middle finger seen by millions*
Sent from my HTC Rezound using Tapatalk 2
wlmeng11 said:
We need someone like Linus Torvalds around here.
HTC doesn't give support to developers?
*cue middle finger seen by millions*
Sent from my HTC Rezound using Tapatalk 2
Click to expand...
Click to collapse
This.
Sent from my SCH-I535 using xda app-developers app
chad0989 said:
With everything 100% working? No you won't. Blame it on HTC, not us.
And cm9 runs fine. 10 runs great but has a purple camera and the FFC isn't likely to get fixed easily, if ever. We don't have the jb blobs for it. And the ICS blobs only support pmem.
Can always go back to pmem for everything but it runs terribly then.
The point is I like to tinker and problem solve. Brain exercise so to speak. I don't release ROMs for this reason. I have zero desire to provide support for them. I personally just like to see what I'm able to do and build skills.
Sent from my ADR6425LVW using xda app-developers app
Click to expand...
Click to collapse
Understood. I really didn't mean to be seem to be assigning blame -- I'm extremely appreciative of and wholly admire the work you and others have put into this device. I was asking as a genuine question as it was unclear to me what kind of direction is being aimed for and what the goals are.
Keep doing your thing, and I appreciate the input. :good:
And I'm far from an expert on these things (my background is in system administration and networking, not programming), but on the camera issue, doesn't the Rezound use the same camera module as the Droid Incredible? I know there are working CM10 builds with everything on the camera working but video. Perhaps this could be of use?
GrayTheWolf said:
CM9 is extremely stable. I have used it as a daily driver for a long time now.
I have had CM9 on here longer than any other ROM even stock.
Click to expand...
Click to collapse
This.
Sent from my HTC Rezound.
alphabets said:
This.
Sent from my HTC Rezound.
Click to expand...
Click to collapse
This.
Obaterista93 said:
This.
Click to expand...
Click to collapse
That.
alphabets said:
This.
Sent from my HTC Rezound.
Click to expand...
Click to collapse
Obaterista93 said:
This.
Click to expand...
Click to collapse
These.
Sent from my HTC Rezound using Tapatalk 2
wlmeng11 said:
These.
Sent from my HTC Rezound using Tapatalk 2
Click to expand...
Click to collapse
Those.
jon7701 said:
Those.
Click to expand...
Click to collapse
dat there
dyetheskin said:
dat there
Click to expand...
Click to collapse
Dass es.
Sent from my SCH-I535 using xda premium
Obaterista93 said:
Dass es.
Sent from my SCH-I535 using xda premium
Click to expand...
Click to collapse
Beanstalk.
Sent from my ADR6425LVW using xda app-developers app
Ya some funny dudes....lol.
How about THAT!
imparables said:
Ya some funny dudes....lol.
How about THAT!
Click to expand...
Click to collapse
You mean... THIS?
Obaterista93 said:
You mean... THIS?
Click to expand...
Click to collapse
Well,
You can go with this, or you can go with that.
But this is where it's at
Sent from my ADR6425LVW using xda app-developers app
Squirrel1620 said:
Well,
You can go with this, or you can go with that.
But this is where it's at
Sent from my ADR6425LVW using xda app-developers app
Click to expand...
Click to collapse
That commercial....................
Since Google built 4.4 to run with older devices with 512mb. Pulling the 4.4 image and installing on our device shouldn't be too difficult.
This thread I put up for us to collaborate info to see what we can do to get this to work. Once a completed install fully works a new thread can be put together for a complete how to install.
Lets put our community heads together and get a full stock 4.4 KitKat build for all EVO LTE owners.
Sent from my EVO using XDA Premium 4 mobile app
I'm currently not rooted yet. I kind of stepped away due to work, family and personal life struggles. So I have a bit of catching up to do. But know this. I'm will to put both feet in on getting caught up and succeeding getting this going for us all.
Personally I'm tired of Sense and love the new look and function of 4.4. Having this running on my device. I know I'm not alone on this.
Sent from my EVO using XDA Premium 4 mobile app
The CM team is currenty figuring out what needs to be added or changed / merged in to the CM10.2 code to turn this in to 10.3 Once they are done I am sure we will see one populate for the LTE.
Kushdeck has already started compiling 4.4 kitkat cm builds, it's awesome
OK. So here is my question. Can't the build of 4.4 just be built to run on our phone? Does there have to be a special kernal or firmware or both in order to build a full stock of what Google put together just just run as intended for what specs we have?
Sent from my EVO using XDA Premium 4 mobile app
Case in point how we have JB running with a specific to kernel, radios etc.
Sent from my EVO using XDA Premium 4 mobile app
z3r0t0l0rEnCe said:
OK. So here is my question. Can't the build of 4.4 just be built to run on our phone? Does there have to be a special kernal or firmware or both in order to build a full stock of what Google put together just just run as intended for what specs we have?
Sent from my EVO using XDA Premium 4 mobile app
Click to expand...
Click to collapse
z3r0t0l0rEnCe said:
Case in point how we have JB running with a specific to kernel, radios etc.
Sent from my EVO using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Just get to kushdeck thread on development and u'll know...
Sent from my EVO using Tapatalk 2
z3r0t0l0rEnCe said:
OK. So here is my question. Can't the build of 4.4 just be built to run on our phone? Does there have to be a special kernal or firmware or both in order to build a full stock of what Google put together just just run as intended for what specs we have?
Sent from my EVO using XDA Premium 4 mobile app
Click to expand...
Click to collapse
No, it can't just be built. The nexus device's differ than our device. In theory yes it could be built fairly quickly and easily but this isn't a perfect world. Cm is built by having a device tree, that's the core think of it as well a tree, this is what tells the computer its compiled on what files and resources are need to make the software function with the hardware, now think of a tree growing leaves but some sections are bare or bald the compiler/developer then has to sort out why that area is not functioning correctly its a long process and it takes time. Basically our device and the nexus software dont fit so the process takes longer for a build to come out. Hope this have you some insight I tried to avoid going on and on and being to detailed and typing in binary.
Sent from my EVO using xda app-developers app
I know you want a stock build but kushdeck just made a version of CM, and that is as close to stock as I think you are gonna get.
You can find it here, http://forum.xda-developers.com/showthread.php?t=2518211
good luck!:fingers-crossed:
Martin6040 said:
I know you want a stock build but kushdeck just made a version of CM, and that is as close to stock as I think you are gonna get.
You can find it here, http://forum.xda-developers.com/showthread.php?t=2518211
good luck!:fingers-crossed:
Click to expand...
Click to collapse
I am running this on my phone and compared it to a friend's Nexus 5. I found very few differences in customization, mostly in the default apps that were loaded and backgrounds/bootloader things. Also ART works on his phone, while it doesn't work on mine. Overall it is pretty close to stock.
Thanks for the info. That does clear it up.
rosswil said:
I am running this on my phone and compared it to a friend's Nexus 5. I found very few differences in customization, mostly in the default apps that were loaded and backgrounds/bootloader things. Also ART works on his phone, while it doesn't work on mine. Overall it is pretty close to stock.
Click to expand...
Click to collapse
I see/hear that CM is working on CM 11 which is 4.4. I'll wait for a stable of that to see how things go. I lookied over kushdecks thread and i see way too many issues that I don't want to deal with.
z3r0t0l0rEnCe said:
I see/hear that CM is working on CM 11 which is 4.4. I'll wait for a stable of that to see how things go. I lookied over kushdecks thread and i see way too many issues that I don't want to deal with.
Click to expand...
Click to collapse
FWIW, deck is the official maintainer for this device for CM. (With the change to CM inc, I don't know if that may change).
I.e., deck is CM.
Sent from my EVO 4G LTE using XDA Premium 4 mobile app
Cm11 has been my daily for about a week, less random reboots(for me) than late builds of cm10.2
The cm "stable" builds are just snapshots, there is literally nothing special about them
Sent from my EVO using xda app-developers app
scottspa74 said:
FWIW, deck is the official maintainer for this device for CM. (With the change to CM inc, I don't know if that may change).
I.e., deck is CM.
Sent from my EVO 4G LTE using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Learn something new everyday. Thanks for that info.
Since I can't ask in the real dev thread:
I have hboot 1.12.1111 and radio 1.12.11.1210. I know I have to update twrp, but do I have to update the hboot or radio (or anything else) to install cm11?
phoenix0783 said:
Since I can't ask in the real dev thread:
I have hboot 1.12.1111 and radio 1.12.11.1210. I know I have to update twrp, but do I have to update the hboot or radio (or anything else) to install cm11?
Click to expand...
Click to collapse
no need to update your hboot. update your radio man, you'll see better 4G and 3G signal.
I'm pretty sure captain suggested update hboot around page 18 in decks thread. Thought he said it had something to do with mounting or reading partitions correctly. I reluctantly updated mine.
Sent from my EVO 4G LTE using XDA Premium 4 mobile app
Yeah, I did, but the change that was going to require it is now not going to happen. Though updating to the rumrunner hboot does provide access to ENG commands which can be useful in a crisis.