Database Info

[Radio & WiMax] 2.05.00.06.10 update.zip (Full IMG)

UPDATE: Anyone who broke 4G using unrevoked, there is no fix yet, sorry.
I've been getting alot of questions and comments about this...
Why is this different from others?
Does not flash Recovery
Does not Flash Boot
Radio is a FULL image and not a diff
YOU MUST HAVE ALL THE 1.47.651.1 SYSTEM FILES FOR WIMAX! (Link Removed, Read)
You break your 4G being stupid, not my fault.
This is a full IMG, wont overwrite recovery or anything else, just radio or wimax!
Only requirement is to have the new system files, don't even need the last radio.
RADIO: Torrent or Direct Download
WIMAX: Torrent or Direct Download
*Disclaimer: These files work for me, if you use them properly they should work properly. I'm just not responsible for damage in any form.
If you want to support me, just check out my various websites, and spread word!
On a side note, I say "must" for the new system files as the new WiMax will break without.
I don't know about radio, but even if it does work, it's not good practice to use with older system files.

Baseband Requirement
Does this flash require that you have a certain baseband before flashing? I am running a stock rooted 1.47 rom that Caulkin posted and am still running the stock baseband radio...I have not updated to the 5.31 that toast posted yet.
Do I need to flash 5.31 radio before flashing this? Or I am ok using my stock .24 radio?
Do I need to reflash my recovery_img afterwards?

hecklbrg said:
Does this flash require that you have a certain baseband before flashing? I am running a stock rooted 1.47 rom that Caulkin posted and am still running the stock baseband radio...I have not updated to the 5.31 that toast posted yet.
Do I need to flash 5.31 radio before flashing this? Or I am ok using my stock .24 radio?
Do I need to reflash my recovery_img afterwards?
Click to expand...
Click to collapse
Ah yes, I knew I forgot to say something...you do need to latest radio.
Main post updated!
Like I said, radio may not fully update...but it doesn't break anything and it will update WiMax

I'm guessing that this does NOT require that you use Caulkin's Wimax fix first as well?

hecklbrg said:
I'm guessing that this does NOT require that you use Caulkin's Wimax fix first as well?
Click to expand...
Click to collapse
I'm not aware of any "fix" from Caulkin, but if you referring to his WiMax update, no you don't need it.

I'm honestly surprised nobody posted anything like this before me that didn't include the damn recovery.
It's annoying to have to flash recovery when it's not needed.

So I would have to flash Calkulin's 1.47.651.1 on top of DC 3.2.x then this radio file?

Neotelos_com said:
I'm honestly surprised nobody posted anything like this before me that didn't include the damn recovery.
It's annoying to have to flash recovery when it's not needed.
Click to expand...
Click to collapse
My sentiments exactly.
Anywho has anyone gotten this working yet? I'm not one for subjecting my phone to be a guinea pig when bricking is a possible side effect.
Does any ROM based on the 1.47.651.1 update work with this or does it have to be the stock ROM?

Neotelos_com, did your Baseband version change to reflect this update? Mine hadn't...

good stuff, gonna look into this...

jwegman said:
Neotelos_com, did your Baseband version change to reflect this update? Mine hadn't...
Click to expand...
Click to collapse
I did check and it seems it did not.
I'll look into this, I personally would like the new radio.

I've done it!
I don't know how but I am the first person to have the full new radio image!
WiMax update will be added back in soon!

Neotelos_com said:
I've done it!
I don't know how but I am the first person to have the full new radio image!
WiMax update will be added back in soon!
Click to expand...
Click to collapse
is this based off of the OTA released yesterday which was 21.4 MB or the OTA released today at 30.2 MB ?
im still grabbing the 30.2 MB OTA released today over my slow 3g right now so i haven't had a chance to compare the OTA .zip from yesterday to the one today.

joeykrim said:
is this based off of the OTA released yesterday which was 21.4 MB or the OTA released today at 30.2 MB ?
im still grabbing the 30.2 MB OTA released today over my slow 3g right now so i haven't had a chance to compare the OTA .zip from yesterday to the one today.
Click to expand...
Click to collapse
I wasn't aware of a new OTA today, these would be based off yesterdays.
It's possible Sprint just switched from a diff for the radio, that would cause about 10mb size difference....in witch this will be the same thing.
No guarantees though, until we find out.

why is it a MUST that we use the .47 system files?

KERKEDAGAIN said:
why is it a MUST that we use the .47 system files?
Click to expand...
Click to collapse
It's been said WiMax wont work without.
I don't know about radio...but you can go ahead and try the radio.
It can always be reverted back using toasts old radio update.zip
It's just good practice to use the system files that these were designed for.
I'm still running DamageControl as a base (with .47), it didn't need a clear for me.

ah, ok..i shall report back w/ my findings!

Radio flashed ok. Tried flashing the WiMax zip and it failed and said it couldn't find the radio.diff?

I did notice the wimax zip has the update-script still looking for the radio.diff to update. This probably needs revised?

grkfire said:
Radio flashed ok. Tried flashing the WiMax zip and it failed and said it couldn't find the radio.diff?
Click to expand...
Click to collapse
haha, my bad, I will have it fixed asap

[FIXED] Downgrading HBOOT to 0.80 from 0.92

Ok so this issue has now been fixed, download the following file and place it on your SD card, start your phone up with, volume down + power and follow the instructions.
PB99IMG.zip
Thanks to everybody who tweeted this in.

o.o adamg - not really! Why did you do that?
That could not mean the end of opendesire and your sense roms could it?

Adam you should have known better, but still look at root method now on my gf's desire will post when I get root

ohh crap i was holding out hoping you'd have an update. hope someone figures it out for your sake if any

I will still be releasing, I have people on the team who test the roms and report the bug errors for me to fix

I will still be releasing, I have people on the team who test the roms and report the bug errors for me to fix
Click to expand...
Click to collapse
If need more help testing email me I'm global mod on villainrom.co.uk
Email [email protected]
Lots of experience
Cheers
Mike

any chance of getting a full root while were at it? it would be awesome to use metamorph

i'm sorry to hear that adam,
but i seriously lol ...... so sorry.
i love your roms.

i got the same problem

http://htcpedia.com/forum/showthread.php?t=2934

Prema999 said:
http://htcpedia.com/forum/showthread.php?t=2934
Click to expand...
Click to collapse
Not possible because you need root to place the flash-executable and the img into a read only directory.
Tried it too but you definitly need a method to execute some lines of code. adb push to /data is not possible because:
- adb is not working
- you can't get root to remount /data rw instead of ro.

Before i flash anything... How did you get there?? Flashed new 2.2 ROM? Or RADIO? or????

after we upgraded the official version throw htc live update

And this?
Isn't it possible to hex edit the version string to trick it into believing it is a newer version?

Prema999 said:
http://htcpedia.com/forum/showthread.php?t=2934
Click to expand...
Click to collapse
twicejr said:
Isn't it possible to hex edit the version string to trick it into believing it is a newer version?
Click to expand...
Click to collapse
that's not so easy, i think it is nearly impossible, you can't hex edit something on a read only phone (if we could edit sth we could flash the 0.80 hboot back), and hex-editing the whole RUU is - as i think - because of encryption and checksum checks etc impossible, too. we have to inject the flash software and the image - and this is impossible without rw / root.

wiggy2k said:
that's not so easy, i think it is nearly impossible, you can't hex edit something on a read only phone (if we could edit sth we could flash the 0.80 hboot back), and hex-editing the whole RUU is - as i think - because of encryption and checksum checks etc impossible, too. we have to inject the flash software and the image - and this is impossible without rw / root.
Click to expand...
Click to collapse
damn you htc

madman_cro said:
damn you htc
Click to expand...
Click to collapse
I think there WILL be a root-hack. it is just a cat and mouse game, htc is now in front, but the dev scene will be back soon with successful rooting i think. so dont fear and be patient
the only hardware which was not exploit-hacked for now is the playstation 3. (I hate not having otherOS anymore ...)

yes should they come with a new release because all the new htc devices will come with 0.92 at least

Adam, get on Freenode IRC and query me.
There's a few things I'd like to test with you
(IRC nick = IEF)

same problem impossible to downagrad hboot or install "RUU_Bravo_HTC_WWE_1.21.405.2_Radio_32.36.00.28U_4.06.00.02_2_release_126984_signed"

[Q] Can VRLG1 be downgraded back to VRLF2 if needed?

I read in a thread that someone lost their imei and it was suggested for them to use *2767*3855# to restore everything back to factory and reactivate the sim. I know this won't update oyur baseband to the newer editions, but it made me think about if someone bought a new phone that has the updated firmware, or somehow got their baseband/radios/kernel updated to the new version (whether through OTA or through getting a new phone), would it be possible to downgrade baseband/radio/firmware back to the previous edition since the VRLF2 version is also signed and authentic?
If it is possible to downgrade, does anyone have the dump files needed from an "older" version to do this? How would it be done, through odin or recovery, or terminal/adb (like backing up and restoring /efs partition)?
Thanks

newuser134 said:
If it is possible to downgrade, does anyone have the dump files needed from an "older" version to do this? How would it be done, through odin or recovery, or terminal/adb (like backing up and restoring /efs partition)?
Click to expand...
Click to collapse
Yep, see http://forum.xda-developers.com/showthread.php?t=1788313 for details.
The forum post has links to both the old and new modem, and full flashing instructions.

yes and I would only use the VLRF2 since it does not have the dumbed down search...the update is a downgrade!! If you like you can upgrade to the VRLG1 radio/modem and stay on the VRLF2 software.

droidstyle said:
yes and I would only use the VLRF2 since it does not have the dumbed down search...the update is a downgrade!! If you like you can upgrade to the VRLG1 radio/modem and stay on the VRLF2 software.
Click to expand...
Click to collapse
True, although you can just get the full featured googlequicksearchbox APK and replace the new one with it.

pjamv5 said:
True, although you can just get the full featured googlequicksearchbox APK and replace the new one with it.
Click to expand...
Click to collapse
indeed...more than one way to skin a cat.

Is there a general concensus yet on the newer modem? seems the posts go both ways... a lot of people saying it's better, others saying it's not.
I guess the only way to be sure is to try it out

Desterly said:
Is there a general concensus yet on the newer modem? seems the posts go both ways... a lot of people saying it's better, others saying it's not.
Click to expand...
Click to collapse
I used the Phone Info app to shut off 4g, and made a number of before/after test of the 3g signal.
It seems to be consistantly 2 or 3 db better with the new modem.
For example, sitting at my desk, I would show -82 dBm with the old modem, and -79 dBm with the new modem.
Can't say if there is any difference in 4g performance, it's nice and fast both before and after.
One change that I noticed, with the new modem, when switching from 3g to 4g, it changes over almost instantly. Before the modem upgrade, it would take maybe 30 seconds or so to pick up the 4g signal.

I535VRLG1 update
I also wondered this. Is there a reason except for the search function to go back to the first radio?
Also on a side note, I never accepted an OTA update! Was this pushed without the user's consent?

excelsisba said:
I also wondered this. Is there a reason except for the search function to go back to the first radio?
Click to expand...
Click to collapse
Updating the radio has nothing to do with the search function. If you currently have the VRLF2 build, you can update the radio (also the kernel) to the newer version without changing the build version.
If you purchased an updated phone, or take an OTA update, then you will have the downgraded google search. As pointed out by pjamv5, that's easy enough to fix if you want the old google search.
I've updated the kernel and radio, here's the end result:

Desterly said:
Is there a general concensus yet on the newer modem? seems the posts go both ways... a lot of people saying it's better, others saying it's not.
I guess the only way to be sure is to try it out
Click to expand...
Click to collapse
I first flashed the G1 radio firmware and kept the F2 ROM. I didn't notice much of a difference. Went ahead and flashed BeanTown R2 ROM which is based on the G1 rom but customized. It all works well for me.

[Kernel / boot.img / STOCK][8/22] - V3 ** Unsecured** VRALG1 kernel with init.d

As the name implies this the unsecure stock kernel boot.img
You can use the adb remount command to push files to system now!
YOU MUST HAVE AN UNLOCKED BOOTLOADER FOR THIS! See here for more info: http://forum.xda-developers.com/showpost.php?p=30274025&postcount=317
If you dont know what this then it may not be for you. This is more so developers can use in there ROMS.
No need to ask to use it, just give credit if you do.
Download HERE

Chang Log
v3 - Corrected incorrect adbd in /sbin for proper colors when using screen capture while in Dalvik Debug Manager.
v2 - Added Lib folder for that need it.

New clean ROM soon then?
Sent from my SCH-I535 using xda app-developers app

Would it be too much to ask for an AOSP kernel (ICS)? I'd do it myself, but I don't know much about kernels lol

Nopi45 said:
New clean ROM soon then?
Sent from my SCH-I535 using xda app-developers app
Click to expand...
Click to collapse
Well, this is more for developers.
It just unlocks the /system partition so you can push files. I mean, yeah, it will be in the next CleanROM but its not urgent from a user perspective.

PureMotive said:
Would it be too much to ask for an AOSP kernel (ICS)? I'd do it myself, but I don't know much about kernels lol
Click to expand...
Click to collapse
This is a Stock kernel. I just modified the RAM Disk to remove security and to add init.d support and set up the script so it can be flashed.
I didint build the kernel. Its just stock.
How come your user name is in italics BTW?

Not sure on run parts... Need to check. Unsecure is still a go!

scrosler said:
This is a Stock kernel. I just modified the RAM Disk to remove security and to add init.d support and set up the script so it can be flashed.
I didint build the kernel. Its just stock.
How come your user name is in italics BTW?
Click to expand...
Click to collapse
I know it's stock. I was just wondering whether you were able to get an unsecured AOSP kernel for all of the AOSP ROMs out there. It'd also help with Sense 4.
To get your username in italics (RDs only):
Go to User CP
Select "Group Membership" from the side bar
Select "Recognized Developer - Identify me as a member of this group"
Save

Well this work on lf2?

Neverendingxsin said:
Well this work on lf2?
Click to expand...
Click to collapse
Are you a dev?
No?
Keep moving
VERIZON GALAXY S 3

PureMotive said:
I know it's stock. I was just wondering whether you were able to get an unsecured AOSP kernel for all of the AOSP ROMs out there. It'd also help with Sense 4.
To get your username in italics (RDs only):
Go to User CP
Select "Group Membership" from the side bar
Select "Recognized Developer - Identify me as a member of this group"
Save
Click to expand...
Click to collapse
To make it unsecure its just some changes in the RAM Disk. Im sure if the AOSP guys are out they know how to do that. If not they can reach out to me for help but they tend to know more than I do about kernels and all
Thanks for the heads up the italics!
Neverendingxsin said:
Well this work on lf2?
Click to expand...
Click to collapse
DROID3R said:
Are you a dev?
No?
Keep moving
VERIZON GALAXY S 3
Click to expand...
Click to collapse
Click to expand...
Click to collapse
This is mostly for developers that want to do things that having a locked boot.img normally stops you from doing. An average user will gain little value...
But lets say you were making a theme and had to "push" files to the /system folder you can NOW do that with this boot.img. It makes Dev's lives a LOT more easy now, lol

scrosler said:
To make it unsecure its just some changes in the RAM Disk. Im sure if the AOSP guys are out they know how to do that. If not they can reach out to me for help but they tend to know more than I do about kernels and all
Thanks for the heads up the italics!
This is mostly for developers that want to do things that having a locked boot.img normally stops you from doing. An average user will gain little value...
But lets say you were making a theme and had to "push" files to the /system folder you can NOW do that with this boot.img. It makes Dev's lives a LOT more easy now, lol
Click to expand...
Click to collapse
yes it does, copying files to my sdcard and then moving them with root explorer, or packaging them in a flashable zip and copying to sdcard and flashing everytime is frustrating. specially if your doing it every 10-15 mins.

nosympathy said:
yes it does, copying files to my sdcard and then moving them with root explorer, or packaging them in a flashable zip and copying to sdcard and flashing everytime is frustrating. specially if your doing it every 10-15 mins.
Click to expand...
Click to collapse
Tell me about man, tell me about it!
And I confirmed init.d support is functional as well!

I know this is just a simplification process for devs and it helps skip the extra step of moving files somewhere else first then move to /system with root explorer if you're rooted, so please don't ask if I'm a dev, the answer is: no, I'm not. I would appreciate if someone could only answer this question without getting into other details. I would like to know if it would harm or break anything if I have VRALF2 rom and radio/stock kernel and I flash a VRALG1 kernel, but keep the rest as it is? Would this newer kernel work with my older version rom, or do I have to flash the whole package first? I basically don't want to renew my rom to the new G1 version since there is no apparent improvement (it's actually worse) over the older F2 version rom, since it downgrades certain things.
Thanks

newuser134 said:
I know this is just a simplification process for devs and it helps skip the extra step of moving files somewhere else first then move to /system with root explorer if you're rooted, so please don't ask if I'm a dev, the answer is: no, I'm not. I would appreciate if someone could only answer this question without getting into other details. I would like to know if it would harm or break anything if I have VRALF2 rom and radio/stock kernel and I flash a VRALG1 kernel, but keep the rest as it is? Would this newer kernel work with my older version rom, or do I have to flash the whole package first? I basically don't want to renew my rom to the new G1 version since there is no apparent improvement (it's actually worse) over the older F2 version rom, since it downgrades certain things.
Thanks
Click to expand...
Click to collapse
When you say no improvement are you talking the Modems? If you are only flashung a rom and havent changed the kernel then it would be the same as just flashing the g1 modem with a different rom correct.

Hey scrosler how can I identify that the flash worked. The ROM booted normally but in the kernel name I don't see any change.

wooddale said:
When you say no improvement are you talking the Modems? If you are only flashung a rom and havent changed the kernel then it would be the same as just flashing the g1 modem with a different rom correct.
Click to expand...
Click to collapse
I'm not talking about the modem, I'm asking about the kernel, if I flash THIS unsecure (G1) kernel, but otherwise have ALL F2 stuff (modem, rom, etc), will it mess up anything? I think u misunderstood my question, I don't want to flash a G1 rom or modem, just the kernel, because the modems are same, so no improvement there, and the F2 rom is better than the G1 rom, so I'm keeping everything as F2 like it was, but flashing this G1 kernel. Will that be compatible/ok?

Try it??? If it fails just restore from backup?
Sent from my Nexus 7 using Tapatalk

newuser134 said:
I'm not talking about the modem, I'm asking about the kernel, if I flash THIS unsecure (G1) kernel, but otherwise have ALL F2 stuff (modem, rom, etc), will it mess up anything? I think u misunderstood my question, I don't want to flash a G1 rom or modem, just the kernel, because the modems are same, so no improvement there, and the F2 rom is better than the G1 rom, so I'm keeping everything as F2 like it was, but flashing this G1 kernel. Will that be compatible/ok?
Click to expand...
Click to collapse
I tried this out and did not see ANY difference. But then again it's midnight and I won't know if anything will be wonky until I use it at work tomorrow
sent from a locked downloader

newuser134 said:
I know this is just a simplification process for devs and it helps skip the extra step of moving files somewhere else first then move to /system with root explorer if you're rooted, so please don't ask if I'm a dev, the answer is: no, I'm not. I would appreciate if someone could only answer this question without getting into other details. I would like to know if it would harm or break anything if I have VRALF2 rom and radio/stock kernel and I flash a VRALG1 kernel, but keep the rest as it is? Would this newer kernel work with my older version rom, or do I have to flash the whole package first? I basically don't want to renew my rom to the new G1 version since there is no apparent improvement (it's actually worse) over the older F2 version rom, since it downgrades certain things.
Thanks
Click to expand...
Click to collapse
Well, you can try it but my experieince tells me that you may loose LTE and WiFi because yo dont have matching modules. The modules (aka drivers if it were windfows) hare specific to a kernel. If you took the /system/lib/modules folder from a G1 ROM like mine or nosympathy and pushed them in I bet it would work just fine. But why on earth are you on older build?
wooddale said:
When you say no improvement are you talking the Modems? If you are only flashung a rom and havent changed the kernel then it would be the same as just flashing the g1 modem with a different rom correct.
Click to expand...
Click to collapse
No, Gerneally ROMS dont include the radios from my experience. BUt I heard int he samsung world Devs do things differently so I dont honestly now.
jb_alphamale said:
Hey scrosler how can I identify that the flash worked. The ROM booted normally but in the kernel name I don't see any change.
Click to expand...
Click to collapse
Thats easy... Before you flashed the boot.img was USB deggign turned on? If not it would be turned on now.
If USB degging was already on or not on turn it on... Then... connect phone and wait for the connection to finish. Then type "adb remount" (assuming you have ADB handy) and it should say "remount succeeded" If it says operation not permitted then it did not take.
newuser134 said:
I'm not talking about the modem, I'm asking about the kernel, if I flash THIS unsecure (G1) kernel, but otherwise have ALL F2 stuff (modem, rom, etc), will it mess up anything? I think u misunderstood my question, I don't want to flash a G1 rom or modem, just the kernel, because the modems are same, so no improvement there, and the F2 rom is better than the G1 rom, so I'm keeping everything as F2 like it was, but flashing this G1 kernel. Will that be compatible/ok?
Click to expand...
Click to collapse
Hipcatjack said:
I tried this out and did not see ANY difference. But then again it's midnight and I won't know if anything will be wonky until I use it at work tomorrow
sent from a locked downloader
Click to expand...
Click to collapse
What difference did you expect? Its a STOCK kernel and will behave like a stock kernel except give full and true root access to the device. Its not for the end user its for developers. Of course this ramdisk will also allow us to start modifying and shutting off services, tweak things at the kernel level, etc... But right now, this is just bone stock with init.d support and root level access to the file system via ADB.
Hope that explains it some.

[US996] 100% Stock deODEXd ROM

Do you have a US996, and want to be able to start modding/theming the ROM? FINE! HERE! Lol...
Please know, this is 100% stock, including kernel. Also, I do not own a US996 (but I do own the H918). This ROM has already been tested (thanks @monsieurtalbot !)
No changes on the ROM. SuperSU gets flashed alongside the ROM. Oh, and setenforce=0 is set via init.qcom.post-boot
Before proceeding. It is absolutely necessary for you to be on a stable TWRP build (currently, RC8, 3.0.2-0, and 3.0.2-1). Also, you must have already have had decrypted your ENTIRE phone. If your phone bootloops into TWRP, you probably didn't decrypt, and/or didn't flash no-verity properly, or it could also be that you are on an old TWRP build. . You have been warned.
This is for the Factory Unlocked US Cellular. Untested on the other US996.
Here we have the base NRD90M ROM from LG. The only difference from this, and what came on your phone is, that it is not ODEXd anywhere. DeODEXing basically bundles all parts of an APK together which saves space, allows for modification of the APK (like for System UI and stuff), and ever so slightly increases performance (by the littlest amount possible). This is ONLY for the US996.
Also, no need to wipe, as /system is fully removed (your apps and settings will stay since that is in /data). Since we only have 1 base from LG, ROMs don't need to be wiped, even if coming from ODEX.
Major thanks to @Chainfire for creating SuperSU
Major thanks to @jcadduono for the root exploit, AND for the TWRP image(s), AND for inspiring me to learn to do it. Also, he supplied the stock System.img, boot.img, and sources for a custom kernel!/RealMVP

SUPER happy to say I am using this currently and it is flawless. Fantastic base for our custom unlocked US996 community.
No more systemless root. This is a full root and I was finally able to delete the stupid boot sounds.
Thx for letting me be the test dummy.
Just so everyone knows I dirty flashed in TWRP from stock and I have had 0 issues. I am a heavy power user.
Everything is working as it should be.
Since it's not specified in the OP - let me make sure that everyone understands that this is for the USA Factory Unlocked US996 ONLY.
Super excited for some custom roms. =)
---------- Post added at 10:53 PM ---------- Previous post was at 10:39 PM ----------
Moving this conversation over from the H918 thread...
I would love to see the FM working on our US996 . . .
BUT - I've had no luck flashing the available zips so far that are for the H918.
FM Service crashes - I figure the chip is there - just needs to likely be enabled on the kernel end.
SO - if you are truly looking into making us a kernel, let's put that on a likely very long todo list. lmao <3

monsieurtalbot said:
Since it's not specified in the OP - let me make sure that everyone understands that this is for the USA Factory Unlocked US996 ONLY.
Click to expand...
Click to collapse
I mean, they would have to be to have TWRP
And it does say US996 in title, as well as in OP

Tilde88 said:
I mean, they would have to be to have TWRP
And it does say US996 in title, as well as in OP
Click to expand...
Click to collapse
There's another US996 for US Cellular - as we all know - so as things get released possibly for that model (which holds the same model number for whatever reason) and this thread ages - it might not be a terrible idea to exclusively specify so some poor soul down the road doesn't flash this to the wrong device... :highfive:

monsieurtalbot said:
I would love to see the FM working on our US996 . . .
BUT - I've had no luck flashing the available zips so far that are for the H918.
FM Service crashes - I figure the chip is there - just needs to likely be enabled on the kernel end.
SO - if you are truly looking into making us a kernel, let's put that on a likely very long todo list. lmao <3
Click to expand...
Click to collapse
Shouldn't be too hard to enable in the kernel. And if it isn't in the source, it could added i guess

Tilde88 said:
Shouldn't be too hard to enable in the kernel. And if it isn't in the source, it could added i guess
Click to expand...
Click to collapse
Any chance you could post the md5 sum for the ROM to check that we got a good download? I want to ensure a good file before flashing a new system.

AlkaliV2 said:
Any chance you could post the md5 sum for the ROM to check that we got a good download? I want to ensure a good file before flashing a new system.
Click to expand...
Click to collapse
It would have to be later tonight, getting ready for work now. You can just double click the zip on your pc. If it opens without an error, you are good to go.

Would you happen to have a stock ODEXed rom for US996 to post as you did for the H918?
Also, are you planning to build anything off the US996 stock deODEXed rom or is it for safety net purposes?

I was thinking about diving into the v20 world to do some dev work, though am I reading this right? Each ROM has to be based off of the system.img for each model number? That makes it hard to decide which device model to buy
--->

Mentalmuso said:
I was thinking about diving into the v20 world to do some dev work, though am I reading this right? Each ROM has to be based off of the system.img for each model number? That makes it hard to decide which device model to buy
--->
Click to expand...
Click to collapse
I honestly am not sure, but I did this just to be safe. As it turns out, FM is not included in the US996 ROM or kernel. I don't know of any other discrepancies, but that was enough for me.
IMO the H918 is the way to go, and just Unlock it from Tmobile. But that's just my opinion.

papashex said:
Would you happen to have a stock ODEXed rom for US996 to post as you did for the H918?
Also, are you planning to build anything off the US996 stock deODEXed rom or is it for safety net purposes?
Click to expand...
Click to collapse
I suppose I could upload a stock ODEXd, but, I don't see the point. :cyclops:

You're right, no point. It's early in the game, hopefully there will be a .tot or .kdz (lg equivalent of ruu) for the eventual 7.1 update.
Thanks for your efforts to date.

Can this ROM be flashed on a sprint 997 that was unlocked and rooted using the dirty Santa method?
The reason I'm asking is because that process seems to change my phone to an unlocked 996 and I want to start fresh with a stock ROM.

Well this is weird. I went to install this and TWRP is telling me I have the wrong device. It is telling me i have a 918 when I know for a fact its a 996....

bryancotton84 said:
Well this is weird. I went to install this and TWRP is telling me I have the wrong device. It is telling me i have a 918 when I know for a fact its a 996....
Click to expand...
Click to collapse
It detects your model from build.prop I believe.
Can you change your model in your build.prop and retry?

Would anyone be willing on trying out a custom kernel? FM might be working. Plus other things and stuff .
I don't have a US996, so I can't test it. So be sure to have a stock boot.img and your stock /system/lib/modules folder. If this fails, you can simply flash your stock boot.img right within twrp, and then push the modules folder into /system/lib/modules. Or you can reflash the ROM.

i was able to dirty flash this straight onto my stock VS995 with the konverge kernel flashed as well and the only problem i have is the static boot but that's easily fixed

Get Ur Noob On said:
i was able to dirty flash this straight onto my stock VS995 with the konverge kernel flashed as well and the only problem i have is the static boot but that's easily fixed
Click to expand...
Click to collapse
What is static boot?
Anyone willing to test the custom kernel, be sure to read what I wrote in the post above. You can find it here

Tilde88 said:
What is static boot?
Anyone willing to test the custom kernel, be sure to read what I wrote in the post above. You can find it here
Click to expand...
Click to collapse
basically until the phone actually boots into the os it looks like a messed up tv showing only static colors and you cant see anything, what you do is you wait until it boots into the os and shut the screen off then hold your finger over the front camera and it fixes it and everything is normal.

Tilde88 said:
I suppose I could upload a stock ODEXd, but, I don't see the point. :cyclops:
Click to expand...
Click to collapse
Any chance you could do it, If it's not too much trouble? I'd like to install it on my F800L, if I can, and I seem to be having issues with the current deodex'd version.
If I'm honest, I have no idea if it will make any difference whatsoever, and the issue could be something completely unrelated (ihavenoideawhatimdoing), but I'd just like to try it, anyway. I got an odex'd H918 working, so It has me wondering if it makes any difference?