[WiFi] [Modules] Stock WiFi Modules ( flashable ) - T-Mobile myTouch 4G Slide

Return to Contents Page - doubleshot Developers Reference
Here are the WiFi modules needed for the following HTC software packages if you get 'error' when trying to enable wifi:
- Software Version: 1.63.531.2
- Radio Version: 11.59.3504.00U_11.16.3504.20_2
- kernel Version: 2.6.35.13-gf3a1982
Feb 3rd, 2012 - 21:34:43 CST
doubleshot_Stock_Module_1-63-531-2_installer.zip
Download Link
MD5: 674ad34b41a1de5af61321a2af8f39c3
Size: 310.92 KB
- Software Version: 1.55.531.3
- Radio Version: 11.59.3504.00U_11.16.3504.20_2
- kernel Version: 2.6.35.13-ge4be2bc
Nov 17th, 2011 - 18:32:14 CST
doubleshot_Stock_Module_1-55-531-3_installer.zip
Download Link
MD5: d4d7c22e93f77c9629ab414f08d9e75b
Size: 310.92 KB
- Software Version: 1.28.531.9
- Radio Version: 10.48.9007.00U_10.12.9007.07_M2
- kernel Version: 2.6.35.10-g6dea02d
Jun 27th, 2011 - 13:23:58 CST
doubleshot_Stock_Module_1-28-531-9_installer.zip
Download Link
MD5: 1c4dddcbe0567db6211c527d59bc7f38
Size: 309.8 KB
Just download the appropriate flashable attached to this post and install through recovery.
Some people have been having issues with not having them match the stock kernel?
Hopefully this is helpful to some.
Blue6IX said:
Guys - in /system/lib/modules there is a file called bcm4329.ko and another called kineto_gan.ko
These modules are kernel-specific, meaning that they must match the exact kernel they came from-regardless of who makes it (HTC, me, you - whoever)
If they do not, then you will not have wifi (no you don't NEED both, but if you want full functionality then you do)
Anyone having wifi errors this is why.
Fastboot flashing the boot.img file will actually write the kernel - if you try to do it through recovery there are securities in place preventing it actually writing the kernel (thanks HTC!!!!)
What happens without fastboot flashing the kernel (boot.img) is that you have those modules made for a kernel you don't have installed.
...just in case anyone was unsure as to what the problem was, this is it right here.
so you either have to:
-fastboot flash the kernel for the ROM you are using...
-or-
-install the modules in /system/lib/modules for the kernel you are using.
I will split those modules from the stock software packages and make them into flashable zips now, so i'll have then up within the next half hour or less.
This should make it easier for people on custom ROMs with stock kernels to just get their wifi back, so they can flash the modules they need for stock.
Click to expand...
Click to collapse

Related

[ROM] [32a] [Updated November 4th] The Officicial HoFo Community ROM 3.0.7 [Sense UI]

I've created a new ROM for the HoFo/Rogers community in the hope that others will help improve it. All of the other ROM's that I have tried had missing features or they were a bit buggy and power hungry just because they weren't made for the specific Rogers Magic. This ROM is based on the orginal Rogers ROM, so everything works and it is stable. Enjoy!
N.B. - If you get an error during an update please upgrade to the 2005 SPL: http://code.google.com/p/sapphire-port-dream/
Thanks to lifeflayer we have a great server for hosting the ROM's.
You have to wipe if you are coming in from a different ROM, not if you are updating the HoFo ROM.
To use the adb console in version 2.0 +, please update to the latest SDK.
To improve your battery life, go into Settings --> Wireless controls --> Mobile networks --> uncheck 'Enable always-on mobile'
It is recommended that you use Amon_RA's recovery image to update this ROM: http://forum.xda-developers.com/showthread.php?t=530492
If you are a non-English locale user, you will need to also run this keyboard update after the HoFo update:
http://hotweiss.lifeflayer.com/roms/originalkb.zip
HoFo Kernel
File contains wlan.ko, boot.img-kernel and config.
This kernel is a modification of cyanogen's kernel with TigerTael's V3 patch applied to it.
N.B. - To get the config's working with Donut, you have to enable video4linux.
V7 - http://www.4shared.com/file/138117137/a19e932c/HoFo-V7tar.html
V6 - http://www.4shared.com/file/136914156/2e1a52e2/HoFo-V6tar.html
V5 - http://www.4shared.com/file/135700242/8bcadce9/HoFo-V5tar.html
V4 - http://www.4shared.com/file/135574805/cdfe3d4/HoFo-V4tar.html
V3 - http://www.4shared.com/file/135233769/2d3de185/HoFo-V3tar.html
V2 - http://www.4shared.com/file/135004617/13b9d310/HoFo-V2tar.html
V1 - http://www.4shared.com/file/134706415/ef4895d5/HoFo-V1tar.html (only one that will work with a Hero ROM)
If you have any ideas about optimizing it any further, please let me know.
Developer
This update is for developer's who need access to the debugging infromation. The update contains an udpated boot.img and wlan.ko.
V6 kernel: http://hotweiss.lifeflayer.com/roms/HoFo-V6-dev.zip
V5 kernel: http://hotweiss.lifeflayer.com/roms/HoFo-V5-dev.zip
V3 kernel: http://hotweiss.lifeflayer.com/roms/HoFo-V3-dev.zip
Run it as an update, it can be applied to any version.
Change log
Version 3.0.7 (November 4th)
- fixed aGPS issue (thanks desmphil)
- fixed PDF viewer
- added SMSfixtimes as requested (it's uninstallable)
Download: http://hotweiss.lifeflayer.com/roms/hofo307.zip (rename to update.zip)
You don't have to wipe, all of your settings will remain after the update.
Version 3.0.6 (November 3rd)
- fixed ringtone lag (thanks to Case_)
- removed shutter sound file, as you cannot turn it off for some reason
- fixed the A2DP support (thanks to seto_613)
- optimized and zipaligned all of the apk's (thank Daneshm90 for pointing out which files could not be optimized)
- removed some useless files
- removed HTC Sync
- all the ringtones are back
Download: http://hotweiss.lifeflayer.com/roms/hofo306.zip (rename to update.zip)
You don't have to wipe, all of your settings will remain after the update.
Version 3.0.5 (October 30th)
- added a few scripts to /system/bin
- possibly fixed the Market issue that some have been experiencing
- Bluetooth should be fully working now
Download: http://hotweiss.lifeflayer.com/roms/hofo305.zip (rename to update.zip)
You don't have to wipe, all of your settings will remain after the update.
Version 3.0.4 (October 30th)
- this version does not have any issues after an update with out a wipe
- added sysctl.conf to improve performance and improve battery life (original code by droidbot)
- fixed WiFi tethering
- added tun.ko module to kernel
- reverted some Bluetooth files, let me know if you see any improvements
Download: http://hotweiss.lifeflayer.com/roms/hofo304.zip (rename to update.zip)
You don't have to wipe, all of your settings will remain after the update.
Version 3.0.3 (October 28th)
- as requested, HTC Sync is back
- HSPA icon is back
- camera shutter sound is back (you can turn it off)
- possible fix for the Bluetooth issues some are experiencing
Download: http://hotweiss.lifeflayer.com/roms/hofo303.zip (rename to update.zip)
You have to wipe.
Version 3.0.2 (October 27th)
- switched to yet another scheduler: anticipatory
- fixed WiFi glitch
Download: http://hotweiss.lifeflayer.com/roms/hofo302.zip (rename to update.zip)
You have to wipe.
Version 3.0.1 (October 27th)
- switched to deadline (scheduler)
- fixed GPS icon (thanks to zortoflaven)
- fixed BusyBox
- fixed HQ YouTube videos
Download: http://hotweiss.lifeflayer.com/roms/hofo301.zip (rename to update.zip)
You have to wipe.
Version 3.0.0 (October 26th)
- upgraded to the Sense UI (Taiwanese 3.03 release)
- AK Notepad & Teeter are uninstallable
- SMS timestamp issue still exists
- Chinese and English locale's have been integrated
Download: http://hotweiss.lifeflayer.com/roms/hofo300.zip (rename to update.zip)
You have to wipe.
Version 2.2.7 (October 20th)
- possibly fixed a bug that was causing a slow down for some people
Download: http://hotweiss.lifeflayer.com/roms/hofo227.zip (rename to update.zip)
Chinese input added by tom0927:
- Chinese input version: http://hotweiss.lifeflayer.com/roms/hofo227cime.zip (rename to update.zip)
You don't have to wipe, all of your settings will remain after the update.
Version 2.2.6 (October 14th)
- changed scheduler to CFQ, it's faster than deadline
Download: http://hotweiss.lifeflayer.com/roms/hofo226.zip (rename to update.zip)
Chinese input added by tom0927:
- Chinese input version: http://hotweiss.lifeflayer.com/roms/hofo226cime.zip (rename to update.zip)
You don't have to wipe, all of your settings will remain after the update.
Version 2.2.5 (October 10th)
- new boot animation, as requested by Daneshm90
- updated to the latest cyanogen kernel source (a WLAN bug was fixed)
- updated Loccy's Better Browser to version 1.5
Download: http://hotweiss.lifeflayer.com/roms/hofo225.zip (rename to update.zip)
Chinese input added by tom0927:
- Chinese input version: http://hotweiss.lifeflayer.com/roms/hofo225cime.zip (rename to update.zip)
You don't have to wipe, all of your settings will remain after the update.
Download: http://hotweiss.lifeflayer.com/roms/hofo220.zip (rename to update.zip)
Chinese input added by tom0927:
- Chinese input version: http://hotweiss.lifeflayer.com/roms/hofo220cime.zip (rename to update.zip)
You don't have to wipe, all of your settings will remain after the update.
Version 2.1.9 (September 27th)
- made some changes to the CPU scaling (please report back how your battery life is)
- since the sampling rate is now 100 (same as extended life version), the extended life version has now been removed; you can change CPU speed with any of the overclock Market applications
- you can now follow me on Twitter: http://twitter.com/paulweiss
Download: http://hotweiss.lifeflayer.com/roms/hofo219.zip (rename to update.zip)
Chinese input added by tom0927:
- Chinese input version: http://hotweiss.lifeflayer.com/roms/hofo219cime.zip (rename to update.zip)
You don't have to wipe, all of your settings will remain after the update.
Version 2.1.8 (September 26th)
- updated to the latest cyanogen kernel source
- added bfs230 kernel patch (updated from bfs222)
- fixed 'adb install'
Download: http://hotweiss.lifeflayer.com/roms/hofo218.zip (rename to update.zip)
Chinese input added by tom0927:
- Chinese input version: http://hotweiss.lifeflayer.com/roms/hofo218cime.zip (rename to update.zip)
You don't have to wipe, all of your settings will remain after the update.
Version 2.1.7 (September 25th)
- removed Sim Checker, as it was causing some trouble for some people
Download: http://hotweiss.lifeflayer.com/roms/hofo217.zip (rename to update.zip)
Chinese input added by tom0927:
- Chinese input version: http://hotweiss.lifeflayer.com/roms/hofo217cime.zip (rename to update.zip)
You don't have to wipe, all of your settings will remain after the update.
Version 2.1.6 (Setember 25th)
- fixed camera FC issue, reverted back to original unoptimized camera app
Download: http://hotweiss.lifeflayer.com/roms/hofo216.zip (rename to update.zip)
Chinese input added by tom0927:
- Chinese input version: http://hotweiss.lifeflayer.com/roms/hofo216cime.zip (rename to update.zip)
You don't have to wipe, all of your settings will remain after the update.
Follow me on Twitter: http://twitter.com/paulweiss
You can also follow this ROM via my blog and see all of the previous changes: http://seethisnowreadthis.com/2009/07/07/the-rogers-htc-magic-hofo-community-rom/
and on HoFo: http://howardforums.com/forumdisplay.php?f=514
do i have to root? what are the steps to get this? what does it look like
VarioIII said:
do i have to root? what are the steps to get this? what does it look like
Click to expand...
Click to collapse
This ROM is vanilla dry. It's basically for people who want stability and full functionality. And yes, this ROM is rooted.
im lost, do i have to spl and root? im getting my phone tomorrow and am coming from WM6.1, so im lost here. What the hell is vanilla dry, and what are the extra features here?
VarioIII said:
im lost, do i have to spl and root? im getting my phone tomorrow and am coming from WM6.1, so im lost here. What the hell is vanilla dry, and what are the extra features here?
Click to expand...
Click to collapse
I don't think you need the new SPL to flash this ROM; I have the new one. Vanilla dry basically means that I didn't mod the core of the system at all (minus the normoclocking), I just added features.
PS-normoclocking, because 528 is the native CPU speed
How did you set the Speed to 528 mhz?
ultraMX said:
How did you set the Speed to 528 mhz?
Click to expand...
Click to collapse
I've added this to the boot.img/init.rc file:
write /sys/devices/system/cpu/cpu0/cpufreq/scaling_max_freq 528000
Click to expand...
Click to collapse
Following you in hofo and xda. great work, i mean really. keep it up.
@hotweiss: wow! thank you so much!
I'm Curious. What is the max frequency set to on the rogers magic when you first get it?
electro-mike said:
I'm Curious. What is the max frequency set to on the rogers magic when you first get it?
Click to expand...
Click to collapse
384 MHz is the default speed, which is underclocked.
528 MHz is the native speed of the CPU.
Not sure if its due to the changing of the keyboard, but I noticed that the calibration tool doesn't work . Always crashes. Good ROM, thanks.
Hi hotweiss, great job but version 1.01 is corrupt on libsgl.so, i can't flash it.
Would you mind repack and upload.
hotweiss said:
384 MHz is the default speed, which is underclocked.
528 MHz is the native speed of the CPU.
Click to expand...
Click to collapse
What's the effect on battery life?
tribalmunky said:
What's the effect on battery life?
Click to expand...
Click to collapse
It shouldn't be much, as the CPU scales all the way from 82 MHz all the way upto the new set maximum of 528 MHz. So it will only shoot up to 528 MHz when needed.
jfive74 said:
Not sure if its due to the changing of the keyboard, but I noticed that the calibration tool doesn't work . Always crashes. Good ROM, thanks.
Click to expand...
Click to collapse
Version 1.0.2
- fixed calibration forced close error
- libgl.so error gone (previous upload must have been bad)
- removed Teeter
http://www.mediafire.com/?y15wj12cycd
hey hotweiss, i really want to use your ROM so I can get rid of all the rogers icons on my magic
but im having a hard time combining bits and pieces of each one's instructions together.
so I've downloaded your update.zip
do i just follow these instructions
http://forum.xda-developers.com/showpost.php?p=4036421&postcount=52
and boot into recovery mode?
how would I do step 8 here, if I dont have the "fastboot boot recovery-RAv1.0H.img" from you?
or can I just use the one from skittleguy as well?
so when i'm done, do I just click "reboot system now"??
or, would I have to follow skittleguy's other post on hofo, and do these steps again, after i've applied the update?:
5. power off phone, hold back button and power to boot into fastboot again
6. fastboot flash boot boot.img
7. fastboot flash recovery recovery.img
8. fastboot reboot
TIA, hope I can have some success with your rom!
hey hotweiss, i really want to use your ROM so I can get rid of all the rogers icons on my magic
but im having a hard time combining bits and pieces of each one's instructions together.
so I've downloaded your update.zip
do i just follow these instructions
http://forum.xda-developers.com/showpost.php?p=4036421&postcount=52
and boot into recovery mode by holding the Power and Back keys until the three skating droids appear??
how would I do step 8 here, if I dont have the "fastboot boot recovery-RAv1.0H.img" from you?
or can I just use the one from skittleguy as well?
so when i'm done, do I just click "reboot system now"??
or, would I have to follow skittleguy's other post on hofo, and do these steps again, after i've applied the update?:
5. power off phone, hold back button and power to boot into fastboot again
6. fastboot flash boot boot.img
7. fastboot flash recovery recovery.img
8. fastboot reboot
i'm very confused with all these little/differnet steps from each person
TIA, hope I can have some success with your rom!
ct809 said:
hey hotweiss, i really want to use your ROM so I can get rid of all the rogers icons on my magic
but im having a hard time combining bits and pieces of each one's instructions together.
so I've downloaded your update.zip
do i just follow these instructions
http://forum.xda-developers.com/showpost.php?p=4036421&postcount=52
and boot into recovery mode?
how would I do step 8 here, if I dont have the "fastboot boot recovery-RAv1.0H.img" from you?
or can I just use the one from skittleguy as well?
so when i'm done, do I just click "reboot system now"??
or, would I have to follow skittleguy's other post on hofo, and do these steps again, after i've applied the update?:
5. power off phone, hold back button and power to boot into fastboot again
6. fastboot flash boot boot.img
7. fastboot flash recovery recovery.img
8. fastboot reboot
TIA, hope I can have some success with your rom!
Click to expand...
Click to collapse
I would use this recovery image here:
http://rapidshare.com/files/252267998/recovery-RAv1.1.1H.img
It's the latest version.
As far as insalling the ROM, just follow these steps:
1) boot into fastboot mode (back and end)
2) fastboot boot recovery-RAv1.1.1H.img
3) run the update process
That's it.
Thanks a lot hotweiss!
it works perfectly now, im glad i got rid of the rogers icons

OpenRecovery 2ndbootOR v1.2 (SD-card writing fixed; Battery charging added)

No matter what I tried via kernel modules (mmcfix), I was not able to fix the issues with writing to certain sdcards under 2.6.29 kernel (of our 'vulnerable' recovery that we use to start OpenRecovery).
So I decided to give a try to 2ndboot from 2.6.29 to 2.6.32 kernel under recovery.
Here is a version of OpenRecovery 1.46 that runs under custom 2.6.32 kernel using 2ndboot:
Download: http://code.google.com/p/cyanogenmod4milestone/downloads/detail?name=OpenRecovery_2ndbootOR_v1_2.zip
Fixes:
- all issues with writing to some sdcards under recovery ("DMA transaction error with device 61" in dmesg)
- missing huge_file feature of ext4 filesystem under recovery
New features:
- battery charging under recovery
Please let me know if you encounter any problems.
The start of OpenRecovery with 2ndboot takes a bit longer, so be patient.
You can see a phone reboot during the start of OR under certain conditions - it's intentional, just wait, the OR will start automatically afterwards.
Kernel source: https://github.com/nadlabak/kernel/tree/recovery
UPDATE 30.01.2013
- prevent watchdog reboot (by automatic reboot of recovery if it was not started via /cache/recovery/command)
- use 10% battd for better compatibility with 3rd party batteries
- modversion set to 2ndbootOR v1.2
UPDATE 03.11.2012
- kernel and 2ndboot files updated (2.6.32.60, L2 cache enabled etc.)
- patches by justcsdr from issue #773 included (power off, mass storage with complete access to all sdcard partitions etc.)
- modversion set to 2ndbootOR v1.1
UPDATE 26.09.2012 (2)
- fixed linker issues - IMPORTANT! please update from the previous version
- modversion set to 2ndbootOR v1.0
UPDATE 26.09.2012
- battery charging and status display added
UPDATE 23.09.2012
- workaround for occasionally non-working adb
- clean kernel build (no change in functionality)
UPDATE 21.09.2012:
- fixed backup of logo, bpsw, lbl and devtree partitions
- added 2ndboot splash screen
Seems to be working for me. No issues
Sorry for the dumb question, but what is the purpose of this OR?
Erovia said:
Sorry for the dumb question, but what is the purpose of this OR?
Click to expand...
Click to collapse
Read the first post...
LuigiC6 said:
Read the first post...
Click to expand...
Click to collapse
Oh god, i really should go to sleep..
By the way, i tried it, works fine, no issues so far. :good:
Works great, slowest but for me without issues
Now my nandroid backups are not hanging on system dump anymore. Great work man. Thanks a lot.
Update:
- fixed backup of logo, bpsw, lbl and devtree partitions
- added 2ndboot splash screen
Download: http://d-h.st/AeS
Kabaldan I have one question.
Is there possibility to run rom on this second kernel? Maybe this is the way to make kernel more complatible for rom
Just a suggestion/question - can't you change version numbers so not to confuse new 1.46 with old 1.46?
DJPatriX said:
Kabaldan I have one question.
Is there possibility to run rom on this second kernel? Maybe this is the way to make kernel more complatible for rom
Click to expand...
Click to collapse
DJ,
As far as I understand, Rom already runs on this "second" kernel. This second kernel is the Motorola Froyo Kernel, recovery was using an older kernel to boot. Both are signed by motorola, so, it is not a custom kernel.
It actually is a custom kernel (2.6.32.59), not signed by Motorola (the last kernel released by Motorola for Milestone is 2.6.32.9 from early 2011).
Check 'cat /proc/version' and see when it was compiled .
You could even use swap with this kernel, if it would make sense under recovery .
But you're right that it's not the main point - this OR release is about recovery to be run under 2.6.32 kernel to achieve reliability in sdcard operations, which was not possible under 2.6.29 kernel of our old recovery.
The problem with 2ndboot (or kexec) method to run custom kernel is that there is no known way to get the Wrigley 3G BP working afterwards (BP = Baseband Processor - the gsm/umts phone features).
This is fine under recovery as the phone functionality is not needed there.
But there's no known way to run a custom kernel on Milestone (or any other Wrigley 3G BP phone such as Defy(+), Milestone 2 etc.) while the device would still be able to function as a phone.
Thanks for the update. Seems to be working fine. Console, nandroid backup/delete (haven't tried restoring yet), scripts...
Btw., indeed very nice 2nd boot splash image
Thank you
Thank you for this update, everything is working just fine!
the dl-link does not work for me. could you reupload it, please?
As dev-host seems to be off-line, I've uploaded new update to issue-tracker site
http://code.google.com/p/cyanogenmo...nRecovery_v1_46_SHOLS_2ndboot_2_6_32_kern.zip
UPDATE 23.09.2012
- added workaround for occasionally non-working adb
- clean kernel build (no change in functionality)
Thanks for the reply. I've seen some issues with radio an other roms who runs on "second kernel". Now everything is clear 4 me.
Cheers
battery charging under recovery added
Link
That is amazing... Thank you.
Btw., you might have forgotten a link http://code.google.com/p/cyanogenmo...1_46_SHOLS_2ndboot_2_6_32_Charge.zip&can=2&q=
New version uploaded:
http://code.google.com/p/cyanogenmod4milestone/downloads/detail?name=OpenRecovery_2ndbootOR_v1_0.zip
It contains important fix for a nasty bug introduced with the addition of battery charge support. Please update.

TW-4.4 ROM-FIX DevEd Devices

TouchWiz-4.4 ROM FIXER for Developer Edition devices
WARNING: These files are for Developer Edition devices ONLY. Kernels cannot be flashed on the retail VZW Note 3 devices!
THIS PROCESS ALSO SETS KNOX 0x1
Own a DevEd? Flashed the firmware/modem bits to the new TW4.4 in hopes of seeing some of the improvements or running a stock-modded ROM?
FIRST: Big shout out to @Imoseyon who has a VERY nice kernel for unlocked devices here:
http://forum.xda-developers.com/showthread.php?t=2488082
Go over there and tell him thanks, because I had spent a day or so trying to fix up a boot.img but wasn't having much luck due to a crash in TIMA memory. But, then I read that someone had gotten the leak booted w/ Imoseyon's kernel and was able to rip it apart and pull just the absolute minimum changes to get a VERY close to stock kernel / ramdisk setup for the 4.4 leak.
WHAT IS THIS?
Several issues were noticed immediately on DevEd devices due to the fact that we can't flash certain portions of the updated ODIN files (aboot, sbls, etc):
Play Movies won't stream
External SD card won't mount
Lockscreen settings don't work
Imoseyon's kernel was the only boot.img which would run 4.4 leak due to aboot/devicetree changes and TIMA crashes
The files below fix these issues and provide a VERY close to stock boot.img for use on DevEd devices.
FIX FILES: 2 flashable .zip files (for use in recovery):
1st flash.zip file is for a new stock-based kernel with CONFIG_TIMA disabled, dt.img created from NC2 sources but combined with 1st ed dtbTool, and default.prop changes for disabling TIMA, securestorage and KNOX (default.prop changes pulled from Imoseyon's leanKernel 2.4 -- thanks!) This file only needs to be flashed once (as long as you don't swap to AOSP ROMs). You can also use leanKernel by @Imoseyon if you like his work. The difference between this kernel and his are: I used the identical settings as the stock NC2 kernel (Kernel modules are enabled, etc) in an attempt to eliminate as many differences between the DevEd and the retail device. His kernel has a TON of tweaks and updates. But, could in theory have issues running the stock NC2 VZW leak.
Kernel source: https://github.com/Hashcode/android_kernel_samsung_hlte/tree/hlteatt-kk-nc2
2nd flash.zip file is a set of file changes which fix the issues noted by DevEd users on the leak (this file should be flashed after EVERY TW-based ROM is flashed)
Downloads:
Mirror 1 (Goo.im)
Mirror 2 (Crackflashers)
Instructions:
Download the above files and place them on your device's storage
Reboot into recovery
Flash flash-vzw-de-4.4-kernel-v1.0.zip if you need to fix kernel (coming from AOSP)
Flash flash-tw44-sys-files-fixes-v1.0.zip after ANY flash of TW-based 4.4 ROMs to fix system files
Reboot, no need to wipe cache, etc
XDA:DevDB Information
TW-4.4 ROM-FIX DevEd Devices, a Tool/Utility for the Samsung Galaxy Note 3
Contributors
Hashcode
Version Information
Status: Beta
Stable Release Date: 2014-04-27
Created 2014-04-27
Last Updated 2014-04-27
Reserved
Thanks
Sent from my SM-N9005 using Tapatalk
How do you know if you have a DevEd device?
Any way to check it? Just curious
Edit: Nevermind... just found it
Only for Veryzon

[STOCK][LP][PATCH][d800] Patch Any Stock G2 ROM for AT&T

Patch a ROM for LG G2 d800!
---- Supports Model d800 ONLY! ----
Lollipop ONLY!​
What this is:
This patch can be flashed after flashing a full non-d800 ROM (DO NOT REBOOT AFTER FLASHING A NON-D800 ROM, even into recovery!) It changes the appropriate system files to the d800 variant version, as well as makes the proper build.prop changes. Note: If you use a vs980, ls980, l01f, or f320 specific ROM, there may be additional build.prop changes that need to be made. I didn't add all those because most of the development is on d80* models. Even if it is specific to these other models, patch will likely work just fine.
I took the basic idea from @dev>null (see here) I had previously dumped all of our stock, d80030f partitions. I took those dumps and combined them with the basic gist of this other patch dev>null made.
What changes this makes:
(1) Your entire bootloader is replaced. (a hybrid of 20y and 30f is applied)
(2) Stock lollipop 30f modem/baseband is installed.
(3) Stock lollipop 30f boot image, that has been bumped, is installed.
(4) Variant specific /system files are deleted. Then they are replaced with the d800 30f version of those files.
Installation:
(1) Boot into recovery, flash your desired ROM. (for my test, I used a d802 ROM)
DO NOT REBOOT RECOVERY, DO NOT!!!! If your ROM asks you to reboot after install, DO NOT!!!!!
(2) Flash this patch.
(3) That's it, you're done! It is okay to reboot now.
Note: Some ROMs might replace your /recovery partition, in which case you should re-flash your recovery before rebooting.
Troubleshooting:
SELinux / Bootloop
This patch properly sets permissions on the files it replaces. That being said, the boot.img in this patch is set to selinux ENFORCING. This means if the ROM you flashed does not have proper support for selinux to begin with, you'll get a boot loop, or hang on the glowing notification LED. Go yell at your ROM dev to fix it, or flash a boot.img that has selinux PERMISSIVE.
ROMs for models other than d80*
There are some additional build.prop changes that might need to be made if the ROM you want to use is f320/ls980/vs980/l01f. There isn't much development on ROMs specific to those models. I'll probably release a version 2 of the patch, eventually, to make these extra tweaks. However, it should work fine as is! The big exception is l01f ROMs. These ROMs are missing NFC files, so either NFC won't work, or the whole thing won't fail.
Major Thanks to:
dev>null
Download:
Did you read EVERYTHING above? If so, proceed -
https://www.gregtwallace.com/lg-g2/d800-rom-patch/
Shameless plug for donations:
Venmo Preferred (No Fee)
Zelle, send to [email protected]
Backup (Charges Fee)
Paypal
XDA:DevDB Information
d800 Lollipop ROM Patch, ROM for the AT&T LG G2
Contributors
blastagator
ROM OS Version: 5.0.x Lollipop
Version Information
Status: Stable
Created 2015-06-01
Last Updated 2019-12-31
Change Log
July 29, 2015 (v1.5) (LP 5.0.x)
-Do not flash misc partition. Not needed.
-Overwrites MAC addresses and things.
June 23, 2015 (v1.4) (LP 5.0.x)
-If /data/media exists, set the proper permissions and context
-DONT use TWRP to wipe Internal Storage after running the patch/fix. If you want to wipe internal, do so BEFORE the patch/fix.
June 23, 2015 (v1.3) (LP 5.0.x)
-Change version number to be same for both files (so skipped v1.2 for permission fixer)
-Updated to latest file_contexts from dorimanx
-FIX!!! - ROM Patch and SELinux Context patch both fix ntcode_listing.sh context
++First boot was hanging on completely clean wipe, d800 does not support context: ubject_r:ntcode_listing_exec:s0
++ntcode file only executes on first boot
++Add build prop tweaks to remove lines that cause execution of ntcode_listing.sh
++In case build.prop tweaks fail and file is executed for some reason, fix its permissions so d800 can execute
June 12, 2015 (LP 5.0.x)
-Permission fixer v1.1
-Fixes a couple of contexts (thanks @dorimanx)
June 11, 2015 (LP 5.0.x)
-Created zip that should fix all SELinux Context and allow boot to ENFORCED mode.
-Posted on my site as "LP ROM SELinux Context Fixer"
-Flash after ROM, ONLY IF SELinux ENFORCE doesn't already work!
June 4, 2015 (v1.2) (LP 5.0.x)
-Added automatic flash of d800 recovery - TWRP 2.8.6.3 (in case ROM overwrote recovery)
-Also posted:
++Added a flashable zip containing devnull's permissive boot.
++Removed my permissive boot, it wasn't working right. Sorry!
June 1, 2015 (v1.1) (LP 5.0.x)
-Supports conversion for Stock Lollipop ROMs from any LG G2 variant, except l01f and lgl22.
-I will probably never add support for those two models since development is very minimal on them.
-Also added other flashable zips to easily switch between ENFORCING and PERMISSIVE.
-Replacement files come from Stock Lollipop d80030f.
June 1, 2015 (v1) (LP 5.0.x)
-Initial Patch
-Fully supports all d80* and f320 ROMs.
-Will do update shortly to add support for converting ls/vs ROMS
-Replacement files come from Stock Lollipop d80030f.
[]
res3
Dude!!! You rock
Sent from my LG-D800 using XDA Free mobile app
Yeah!
Bro thank you! Not only for this, but everything you do for the g2!
thank you.. thank you... thank you.. thank you
So could I use the stock system partition from the d800 lollipop and run it with this?
Thank you very much @blastagator!
Now I can flash any AOSP rom and back to stock easyly. :XXX
I dont think there are any lollipop for L22. L22 is the lonely baby in G2 family without lollipop.
thanks
vannhut07vn said:
thanks
Click to expand...
Click to collapse
You're welcome. Now please kindly delete your quote of the entire OP...
@blastagator
would this patch work with CloudyG2 3.0?
Abrilabr said:
@blastagator
would this patch work with CloudyG2 3.0?
Click to expand...
Click to collapse
It should. If it doesn't boot, permissive-boot flashable would be needed.
You are awesome...insane.. Go on man..!!
Thanks a lot...
Gonna try hunting some Lollipop roms
Nicely Done....
man U R just great.......
thanks for the excellent work....
Hello friends greetings from Venezuela, where I can find a tutorial to update my LG G2 to lollipop, possess a model D800 20Y
@blastagator it's a great idea.Thank you for test with SRKG2
Sent from my LG-H818
it'll work with this rom ?
http://forum.xda-developers.com/lg-g2/development/rom-lg-g2-pro2-v5-final-acura-d802-d805-t3095500

[MODEM][GUIDE] Alcatel Ideal (4060A) Stock Baseband (Radio/Modem) Firmware

AT&T Alcatel Ideal (4060A)
Android Version: 5.1.1
Baseband Version:
MSM8909.LA.1.1.c7.1-113370119-
TWRP Flashable Stock Baseband Installer
GUIDE
The purpose of this thread is to provide members both the instructions and the resources to flash their AT&T Alcatel Ideal (4060A) with the stock baseband (modem/radio) firmware. This procedure could be warranted in situations whereas the device has no signal, poor signal, diminished data connectivity, or any other situation adversely affecting the telephony of the device. I have compiled a TWRP flashable zip installer which will flash the modem & radio partitions back to stock factory condition, as well as reset the device network configurations back to factory default.
UPDATE: In the download link below is v2 of my baseband installer. This version has been optimized for domestic roaming. Also, I have tweaked the installer to fully reset all network configs to factory default, thus your device may commence with cellular activation upon reboot.
DISCLAIMER
As always, flashing the partitions of your device involves an inherent risk of bricking or otherwise rendering your device inoperable. I have fully tested this zip installer and have experienced no adverse effects. Nonetheless, I am not responsible if this bricks or damages your device. Follow the instructions carefully, however, and things should go smooth.
INSTRUCTIONS & REQUIREMENTS
First of all, you must have TWRP custom recovery installed on your device in order to use this zip installer. If you do not have TWRP installed, search XDA Forums for the thread on how to install it.
1. Download the 4060A_Baseband.zip file from the below link and save it either to internal storage or to your external micro SD card;
2. Boot your Alcatel Ideal into TWRP recovery;
3. Select "INSTALL" from TWRP's main screen then navigate to the storage location of the zip you downloaded. Swipe and commence with installation;
4. When TWRP indicates the installation is complete, reboot system.
Your Modem & Radio Firmware (Baseband) should now be restored to stock factory condition.
DOWNLOAD LINK
Baseband Installer: https://drive.google.com/file/d/0B1Sfod4HWfk2TnhtR3I2Qmt4bnc/view?usp=sharing
Baseband Installer v2: https://drive.google.com/file/d/0B1Sfod4HWfk2XzFRbUc3TXRpNlU/view
kindly also upload the drivers <adb, recovery, fastboot, mtp, sideload>. Since, windows 10 allow only signed drives.
Here is alcatel 4060a driver found inside phone /system/etc/USBDriver.iso
why this Baseband Version: MSM8909.LA.1.1.c7.1-113370119- ends with -
While modifying /fastab.qcom (which I have backed up as /fastab.qcom.bck) I stuck into bootloop. I have booted into TWRP but don't where these file are. (Maybe in /boot). Can you help me fix. I don't want to flash whole system my /data is encrypted.
Thanks
Can anyone upload latest ROM
/system /boot /modem*
Alcatel IDEAL (4060A)
Here is the current update: Android 5.1.1 Lollipop
The details:
Release date: July 24, 2017
Android version: 5.1.1
Security patch level (SPL): July 1, 2017
Baseband version: MSM8909.LA.1.1.c7.1-113370123-
Kernel version: 3.10.49-g07ffc9a
Build number: M7UUAU1
Previous versions required: M7QUAQ0
File size: 11.5MB
Previous updates are as follows:
April 18, 2017
What's changing: Android device security updates
Android version: 5.1.1
Security patch level (SPL): February 1, 2017
Baseband version: MSM8909.LA.1.1.c7.1-113370123-
Kernel version: 3.10.49-g053692e
Build number: M7QUAQ0
Previous versions required: Build number ending in AK2, AR4, AB0, or AJ0
Hardware version: 02
File size: Up to 30MB
Jan. 5, 2017
What's new: AT&T HD Voice
What's changing: Android device security updates
Android version: 5.1.1
Security patch level (SPL): November 1, 2016
Baseband version: MSM8909.LA.1.1.c7.1-113370123-
Kernel version: 3.10.49-g5a229e7
Build number: M7JUAJ0
Previous versions required: Build number ending in AK2, AR4, or AB0
Hardware version: 02
File size: 30MB
Oct. 19, 2016
What's new: Device enhancements
Android version: 5.1.1
Security patch level (SPL): May 1, 2016
Baseband version: MSM8909.LA.1.1.c7.1-113370119-
Kernel version: 3.10.49-g3d12fcb
Build number: M5RUAR4
File size: 1.7MB
kdm6389 said:
Can anyone upload latest ROM
/system /boot /modem*
Alcatel IDEAL (4060A)
Here is the current update: Android 5.1.1 Lollipop
The details:
Release date: July 24, 2017
Android version: 5.1.1
Security patch level (SPL): July 1, 2017
Baseband version: MSM8909.LA.1.1.c7.1-113370123-
Kernel version: 3.10.49-g07ffc9a
Build number: M7UUAU1
Previous versions required: M7QUAQ0
File size: 11.5MB
Previous updates are as follows:
April 18, 2017
What's changing: Android device security updates
Android version: 5.1.1
Security patch level (SPL): February 1, 2017
Baseband version: MSM8909.LA.1.1.c7.1-113370123-
Kernel version: 3.10.49-g053692e
Build number: M7QUAQ0
Previous versions required: Build number ending in AK2, AR4, AB0, or AJ0
Hardware version: 02
File size: Up to 30MB
Jan. 5, 2017
What's new: AT&T HD Voice
What's changing: Android device security updates
Android version: 5.1.1
Security patch level (SPL): November 1, 2016
Baseband version: MSM8909.LA.1.1.c7.1-113370123-
Kernel version: 3.10.49-g5a229e7
Build number: M7JUAJ0
Previous versions required: Build number ending in AK2, AR4, or AB0
Hardware version: 02
File size: 30MB
Oct. 19, 2016
What's new: Device enhancements
Android version: 5.1.1
Security patch level (SPL): May 1, 2016
Baseband version: MSM8909.LA.1.1.c7.1-113370119-
Kernel version: 3.10.49-g3d12fcb
Build number: M5RUAR4
File size: 1.7MB
Click to expand...
Click to collapse
I'm presently compiling the latest build for a TWRP flashable version. Thanks to @scohut for providing the base files.
MotoJunkie01 said:
I'm presently compiling the latest build for a TWRP flashable version. Thanks to @scohut for providing the base files.
Click to expand...
Click to collapse
Do you mean this one?
The details:
Release date: July 24, 2017
Android version: 5.1.1
Security patch level (SPL): July 1, 2017
Baseband version: MSM8909.LA.1.1.c7.1-113370123-
Kernel version: 3.10.49-g07ffc9a
Build number: M7UUAU1
please make sure it has all the necessary (boot, system, modem*, *persists*,) last time one has upload on system resulting in bootloop. [SuperGuide]...
kdm6389 said:
Do you mean this one?
The details:
Release date: July 24, 2017
Android version: 5.1.1
Security patch level (SPL): July 1, 2017
Baseband version: MSM8909.LA.1.1.c7.1-113370123-
Kernel version: 3.10.49-g07ffc9a
Build number: M7UUAU1
please make sure it has all the necessary (boot, system, modem*, *persists*,) last time one has upload on system resulting in bootloop. [SuperGuide]...
Click to expand...
Click to collapse
Yeah that's the one I'm doing. And yes I always like to include /boot & /modem files. You're wanting /persist added?
One more thing, since you have no time, give me the base file. I will install on my phone; and convert into TWRP flashable and upload. Since I have 20mbps line till 29th 3pm.
---------- Post added at 01:56 AM ---------- Previous post was at 01:55 AM ----------
Or add me in your Google drive repository [email protected]
---------- Post added at 01:58 AM ---------- Previous post was at 01:56 AM ----------
MotoJunkie01 said:
Yeah that's the one I'm doing. And yes I always like to include /boot & /modem files. You're wanting /persist added?
Click to expand...
Click to collapse
Thanks for this.
---------- Post added at 02:03 AM ---------- Previous post was at 01:58 AM ----------
I just wanted all the necessary partition. I don't know what it is. I wrote all that I am knowing.
kdm6389 said:
One more thing, since you have no time, give me the base file. I will install on my phone; and convert into TWRP flashable and upload. Since I have 20mbps line till 29th 3pm.
---------- Post added at 01:56 AM ---------- Previous post was at 01:55 AM ----------
Or add me in your Google drive repository [email protected]
---------- Post added at 01:58 AM ---------- Previous post was at 01:56 AM ----------
Thanks for this.
---------- Post added at 02:03 AM ---------- Previous post was at 01:58 AM ----------
I just wanted all the necessary partition. I don't know what it is. I wrote all that I am knowing.
Click to expand...
Click to collapse
I'll probably be rolling mine out late tonight sometime.
Good
Modifying the stock boot image in the updated stock ROM for unsecured boot support with init.d. I will post the updated ROM when I have had a chance to test for stability and bugs.
@MotoJunkie01 if possible put both boot.orignal.img (unsecure) and boot.patched.img (secure) inside the zip, but ROM should flash boot.patched.img by default.
Thanks I am waiting to test.
kdm6389 said:
@MotoJunkie01 if possible put both boot.orignal.img (unsecure) and boot.patched.img (secure) inside the zip, but ROM should flash boot.patched.img by default.
Thanks I am waiting to test.
Click to expand...
Click to collapse
The ROM will flash an insecure boot image. I'll post a copy of the original stock boot image as well so members can have the option to use it in lieu of the modified boot image.
All,
Let's please keep this thread on topic as @MotoJunkie01 requests. This isn't a ROM thread, so please no asking for ETAs and generally cluttering the thread.
-snickler
People are so dum these days, that don't simply copy boot image and upload to site. I ask to @scohut way ago send me all the file. But he sent to someone now he is cooking what I don't know.
kdm6389 said:
People are so dum these days, that don't simply copy boot image and upload to site. I ask to @scohut way ago send me all the file. But he sent to someone now he is cooking what I don't know.
Click to expand...
Click to collapse
One more time in case you didn't see the Moderator's post, this is not a ROM thread. Stop posting off topic in the modem thread.
I am taking about boot image this time, its not ROM
---------- Post added at 06:34 PM ---------- Previous post was at 06:33 PM ----------
Got, it this is for only Modem confused with this https://forum.xda-developers.com/an...-android-5-t3637885/post73143789#post73143789
kdm6389 said:
I am taking about boot image this time, its not ROM
---------- Post added at 06:34 PM ---------- Previous post was at 06:33 PM ----------
Got, it this is for only Modem confused with this https://forum.xda-developers.com/an...-android-5-t3637885/post73143789#post73143789
Click to expand...
Click to collapse
This thread has nothing to do with boot image. It's a modem thread, not a ROM thread, not a boot image thread, etc etc. Stay on topic. Ok. I saw the second part of your post. Thank you for keeping on point. @kdm6389 you should start a Q & A thread for the Alcatel Ideal. That way, questions & issues not on topic with the available device threads could be addressed.

Categories

Resources