Database Develop

[DEV][4.0.7]Huawei USB Dongles.

[UPDATE]2012-08-06 This is not the only way of getting Dongle's working on Android, If widgets are your thing and you doing feel confident working with system files etc then you may be better served using the ppp widget form draisberghof.de, these are the folks who piratically wrote the book on getting dongles working on linux and by extension android.
[UPDATE]2012-08-06 The source to libhuaweigeneric-ril ( github ) has been updated to include fixes made by omegaRed7 - This massively improves the fault tolerance upon RIL Startup, Tests were carried out on the E173s-1 but it should be beneficial to all modems ( I hope ).
[UPDATE]2012-07-28 As the Rom Version is quite old and it doesn't really require it's own rom I've extracted the files required to implement this functionality - Download Here, The Archive contains a README file with installation instructions
IMPORTANT - pppd permission need changing to 6755 also change to ownership to the root account ( Thanks to __DS__ ). you can do this through adb or terminal emulator
Code:
adb shell chown 0:0 /system/bin/pppd
adb shell chmod 6755 /system/bin/pppd
for this to function
[UPDATE]2012-06-25 Added Forked libhuaweigeneric-ril to Github Repo this includes all the changes I've made - Check This Post For Details
[UPDATE]2012-06-23 Added Github Repo - Check This Post For Details
[UPDATE]2012-06-16 THE DOWNLOAD LINK HAS BEEN UPDATED AS THE FILES IN /etc/system/usb_modeswitch WHERE NAMED INCORRECTLY[/UPDATE]
Hi Folks - This post is going to change fairly often, there is still more info to add, I just got bored with typing for now
The Sales Pitch
This rom aims to provides the same "hands free" approach offered by the Archos 3G Key and extends this functionality to Huawei Branded USB Modems.
Introduction
Here is a custom rom I've currently been hacking away at, if feels like I've had it under wraps for months.
That being the case. I'd like to thking on to enable Huawei USB Modems - This is still a WORK IN PROGRESS but It feels like i've been keeping it under wraps for months, So it's time to throw it out there for further testing. So Dongles at the Ready! It could get a little hacky
WARNING
The Full Size USB Slot has been known to fail from moderate use. As such I would recommend using an USB extensions cable for connecting devices.
VERY IMPORTANT NOTES - PLEASE READ
1. This is definitely not an every day use rom on any other device this woud have been deployed as a recovery flashable update. The reasoning behind the rom deployment is it's only one file to copy and youi're ready to go. It is also a tedious task to manually go through (especially on the 100th time
2. Please don't ask a me if a certain device will work or not. It is not helpful on a number of levels,
a) I simply don't know - I don't own the model in question. Further more you can figure it out yourself.
b) The Chances are that you could probably find out the answer without leaving the comfort of xda - The libhuaweigeneric-ril has been passed around xda like a <Insert Well Used Analogy Here> so a quick search of xda may turn up something useful to reassure you.
c) In reality though we are not going to know if your dongle is working until you "Try It Yourself".
3. if you find your device doesn't work then you need to gather all the relevant information to help get a feel of what's going on; See Below
SUPPORTED DEVICES
The theoretical list of supportted devices come from those devices supportted by usb_wwan and option kernelp drivers.
IMPORTANT NOTES - WHAT YOU NEED TO KNOW
In a perfect world you can download/flash the attached update file. Reload your SDE, Plug a USB 3G Dongle and have It connect and go about you day .
This is the ultimate goal and currently what happens on my own device
TROUBLESHOOTING
There's about a 25% based on my current test this won't happen. There are 2 main ways your connection attempt can fail.
1. The UsbStick has not switched to modem mode
2. The ppp connection script failed
Either Way it would be highly useful post the list of system properties, outputs of dmesg and also a full logcat aswell as the vendor/product id from lsusb,
some like this throught the adb
Code:
adb shell getprops
adb shell lsusb
adb shell dmesg
adb logcat -b radio -b system -b main -b events
Please have a glance over it before posting as It may contain information that you would not want others to see!
ROM DETAILS
Android Version: 4.0.3
Archos Version: SDE 4.06
Removed : Nothing
ADDITIONS
init.dongle.rc - initialization script, I wanted to avoid "polluting" any other init file too much
/lib/modules/usb_wwan.ko and /lib/modules/option.ko - USB Drivers for GSM modems
/system/lib/libhuaweigeneric-ril.so - A slightly tweaked version of DerArtem original huaweigeneric-ril
/system/etc/usb_modeswitch - the latest version of the usb-modeswitch-data
/etc/ppp - Added separate gprs scripts to retain compatibility with the Archos datakey
/system/bin/hotplugd - A new native android service; Manages Modeswitching and connection initialization for any Usb Device which has a valid configuration file present.
DOWNLOAD
3G Modem Redist Pack - For use with newer roms
Hotfile - archos.ext4.update.
INSTALL
Unpack zip and copy unpacked update file to the device
Code:
adb push archos.ext4.update /mnt/storage
restart device in sde mode
script should update automatically
KNOWN ISSUES
"3G Stick Connected" Icon remains in notification list after device disconnection.
pppd needs to be executed with elevated privileges.
pppd is not exiting correctly on some occasions and cause reconnection issues when using multiple sticks.
Thanks go to surdu_petru for the base sde, derAtem for his original work on the libhuaweigeneric-ril.so and pretty much every developer who has worked on these dongles with android, I think I've read every thread on XDA regarding this subject

Hi!
Thanks trevd!
I do not have this USB modem ....but you did a good job for those who have this modem ! Good luck...

i have a Huawei E160E
It is possible to add this modle on your rom ?
---------- Post added at 06:46 PM ---------- Previous post was at 06:23 PM ----------
For the buzz in FRANCE (and in the World :-= )
http://www.jbmm.fr/?p=28280

cajl said:
i have a Huawei E160E
It is possible to add this modle on your rom ?
Click to expand...
Click to collapse
Is this a new model ( released this year )? It may already be in there, The easiest thing to do is plug it in.
If you install this app you can find out what the product_id is and then we can find out for sure.

Thanks
no released in 2009
Device Class: Use class information in the Interface Descriptors (0x0)
Vendor ID: 12d1
Vendor Name: Huawei Technologies Co., Ltd.
Product ID: 03eb

Hi trevd.
Thanks for the work.
Before installing your rom, I'd like to know if my Huawei K3565 is or will be supported.
I can't remember when it was released, but it not a new one ; may be 2009 or 2010.

Rackham666 said:
Hi trevd.
Thanks for the work.
Before installing your rom, I'd like to know if my Huawei K3565 is or will be supported.
I can't remember when it was released, but it not a new one ; may be 2009 or 2010.
Click to expand...
Click to collapse
Hi Rackham666
I'd refer back to my first post, I've tried to make it a little more clear what this "rom" exactly is, more a testing ground, my apologises if that wasn't very clear at first glance, So to switch this query right back at you.
After installing my rom, I'd like to know if your Huawei K3565 is supported?.

For my usn dongle , is it ok for you ?

Okay.
I'll try your additions manually when [email protected] V3 will be released by Petru.

Get The Code
Hi Folks.
I've started a github repo if anyone wants to hack on this stuff.... It only contains the code for the hotplug service at the moment but I will obviously add more when I get chance and apply all the proper GPL licenses to it.
A personal word of note : C is not my first language by any stretch ( although it is fast becoming the case ) so If It causes any memory leaks or starts nuclear war I can't be held responsible, however if there is any noob coding errors in there then I'm ready to learn off those more knowledgeable than I. I have a feeling we have some hardcore developers lurking in Archos Development community
Equally If anyone has any fixes drop me a pm and I'll sort commit access on the repo or post them right here in the thread,
The code can be found here https://github.com/trevd

Hi Folks, Me Again!
Just to let you guys know I've added a forked libhuaweigeneric-ril to my github ( https://github.com/trevd )
It includes the changes I made to enable it to work the Archos.
You'll want to clone the ics branch if you want to compile yourself.

cajl said:
For my usn dongle , is it ok for you ?
Click to expand...
Click to collapse
???
I'm not sure I understand what you mean.... can you explain a little more
Thanks

Hi, I'm sorry if I'm bothering you but I've done the steps for installing this but when I get to sde menu nothing happens. You said script should install the update automatically but nothing happens. Is there something else I have to do?
Sorry again and thank you for your work
Sent from my ARCHOS 101G9 using xda premium

alahkel said:
Hi, I'm sorry if I'm bothering you but I've done the steps for installing this but when I get to sde menu nothing happens. You said script should install the update automatically but nothing happens. Is there something else I have to do?
Sorry again and thank you for your work
Sent from my ARCHOS 101G9 using xda premium
Click to expand...
Click to collapse
Hi Alahkel
You're not bothering me .... DO I really sound/come across as that grumpy/angry in my first post.... sometimes I get cranky when I don't get enough sleep.... too much time looking at code.... :laugh:
Thanks for having a go, Are you using the official SDE? and have you got a working SDE Rom already installed?
For now I would forget about the rom image and bear with me, I'm working on an installer APK which will probably better help with testing, I'll also put the manual installation method up for those who want to get dirty with adb.

Hi, i succesfully installed your build then, btw running unoff sde. I have a huawei 170something, I don't remember the model, but it's working great with no problems, but using a otg cable only. I didn't get it to work using the big usb slot
Sent from my ARCHOS 101G9 using xda premium

alahkel said:
Hi, i succesfully installed your build then, btw running unoff sde. I have a huawei 170something, I don't remember the model, but it's working great with no problems, but using a otg cable only. I didn't get it to work using the big usb slot
Sent from my ARCHOS 101G9 using xda premium
Click to expand...
Click to collapse
That's great news Interesting that you couldn't/haven't got it working on the full size port... It should function the same as the official Archos Stick, You need to switch on the 3G Stick in the settings and the full size slot should "Just Work". I may have missed that little detail out
If that doesn't work your full size slot is maybe broken A not uncommon issue it seems. unfortunately.
Out of interest what network are you on?
I'm just working on the installer now so you won't be stuck with old archos versions.

trevd said:
That's great news Interesting that you couldn't/haven't got it working on the full size port... It should function the same as the official Archos Stick, You need to switch on the 3G Stick in the settings and the full size slot should "Just Work". I may have missed that little detail out
If that doesn't work your full size slot is maybe broken A not uncommon issue it seems. unfortunately.
Out of interest what network are you on?
I'm just working on the installer now so you won't be stuck with old archos versions.
Click to expand...
Click to collapse
Hi, thx for answering. Well of course I turn on the 3g key in settings for big-size usb and my huawei 3gkey is on indeed (led on key) but the tab doesn't recognize that o.o I'm on tim (italy ) Thank you
Sent from my ARCHOS 101G9 using xda premium

Hi trevd,
i'm guessing this won't work on CM9 by JackpotClavin, or would it? If yes, would i install it the same way as described?
Thanks in advance!
Edit: Sorry i'm obviously still running in 1st gear in the morning... There's no 3G support in the CM9 port so there's no way this would just "work"...
Edit2: And confirmation that i need more coffee: Saw your post in CM9 thread about the successful connection with Archos' 3G stick and a Huawei 3G stick, but only through the browser... Any progress on fixing things so the ppp connection is fully usable by other apps & services?

Hi, trevd!
how to launch the modem on a firmware 4.0.7?
I copy these files from your firmware
init.dongle.rc - initialization script, I wanted to avoid "polluting" any other init file too much
/lib/modules/usb_wwan.ko and /lib/modules/option.ko - USB Drivers for GSM modems
/system/lib/libhuaweigeneric-ril.so - A slightly tweaked version of DerArtem original huaweigeneric-ril
/system/etc/usb_modeswitch - the latest version of the usb-modeswitch-data
/etc/ppp - Added separate gprs scripts to retain compatibility with the Archos datakey
/system/bin/hotplugd - A new native android service; Manages Modeswitching and connection initialization for any Usb Device which has a valid configuration file present.
Click to expand...
Click to collapse
I change the init.rc file for init.dongle.rc start
but the Huawei E1550 modem doesn't work
what it is necessary to change still?
Thanks!
=========================
sorry, everything earned, it was necessary to update a modem firmware

Hi deman05
You were nearly there, init.dongle.rc is imported on the very first line of init.rc so you need both files.
You shouldn't have to do anything with the modem firmware as usb_modeswitch will handle turning the modem.
The files required are.
init.rc
init.dongle.rc
/lib/modules/usb_wwan.ko
/lib/modules/option.ko
/system/lib/libhuaweigeneric-ril.so
/system/bin/hotplugd
Also you need the full contents of the following directories
/system/etc/usb_modeswitch
/system/etc/ppp
/system/etc/chatscripts
I've attached the latest versions to this post (hopefully I've not missed anything), you will need to change the permissions on /system/bin/pppd.
chmod 6755 pppd
[EDIT] I did miss something, please see the first post for the correct download link.
The new version also handles a cold boot ( modem plugged in on startup ) scenario.
If you are still having issues please refer to the troubleshooting section in my original post
Thanks

[PATCH] Kexec-hardboot patch

In this post, I would like to explain what kexec-hardboot patch is.
@kernel developers: I would like to ask you to merge this patch to your kernels, because it is essential part of MultiROM - it allows to boot any kernel without changing the boot partition. I realize that it is no small request, but the patch is not big, touches relatively stable parts of kernel and should not cause any problems. Thank you.
What is kexec?
It is syscall of Linux kernel, which allows you to boot another Linux kernel without restarting the device - "Linux boots itself". The functionality is equivalent to fastboot -c *cmdline* boot zImage initrd.img, but without PC and fastboot. It is fairly known thing, so more info at wikipedia and man kexec.
What is the difference between normal and hardboot exec?
Kexec-hardboot patch adds a real device restart to that process, so that all the drivers can be properly reinitialized. It stores new kernel to RAM, reboots the device as usual, and kernel from boot partition immediately jumps to the one which was stored to RAM before reboot.
Unlike grouper's kexec-hardboot patch, this one only requires the host kernel to be patched. This is one of the improvements Tasssadar made, and I think it is pretty significant.
To sumarize the process:
kexec --load-hardboot.... is called and kernel it loaded into RAM.
kexec -e is called. Special info is written to memory (to area which is not overwritten on reboot) and the device is rebooted.
After reboot, very early in the boot process, kernel checks if that special info is present in RAM and if so, it loads new kernel from RAM and jumps to it.
Kexecd' kernel starts and boots.
For more info, read the original thread.
Patches:
Kernel patch: https://gist.github.com/PatrikKT/50faf32e8931d51c0c9a,
This is the kernel patch. Only the host kernel needs to be patched.
Related CONFIG options:
CONFIG_KEXEC=y
CONFIG_KEXEC_HARDBOOT=y
CONFIG_PROC_DEVICETREE=y
CONFIG_ATAGS_PROC=n # This one is turned on automatically, but it is not needed, so you can disable it.
All these options must be enabled.​
Userspace kexec binary: https://github.com/Tasssadar/kexec-tools
I had to change some things in kexec userspace binary because of some kernel bugs, complete description is in that repository. You can get statically built binary at https://github.com/Tasssadar/multirom/blob/master/install_zip/prebuilt-installer/multirom/kexec​
Usage:
Once you have the kernel patches and kexec userspace binary in place, just run following command to boot into new kernel:
Code:
kexec --load-hardboot zImage --initrd=initrd.img --mem-min=0x20000000 --command-line="$(cat /proc/cmdline)" --dtb
kexec -e
Note the command line parameter - cmdline from bootloader is not added automatically, you have to put it there by yourself.
Authors:
This patch was made by Mike Kasick for Samsung Epic 4G. Since that, it was ported to several devices, one of them is Asus Transformer TF201 - he used patch from TF201 and modified it a bit (basically just changed few SoC specific constants). People at #ubuntu-arm helped him out with that, thanks.
For hammerhead, he has improved the patch a bit - only the host needs to be patched now and he has added support for DTB.
This thread was used as a template Credits to @Tasssadar for his Nexus 5 patch

Awesome people helping with our G2's development. Thank YOU!

patrik.KT said:
I would like to ask you to merge this patch to your kernels, because it is essential part of MultiROM - it allows to boot any kernel without changing the boot partition.
Click to expand...
Click to collapse
What benefit would there be to non-MultiROM users? (Just curious.)

blastagator said:
What benefit would there be to non-MultiROM users? (Just curious.)
Click to expand...
Click to collapse
Any. Just any.

Actually I can't think of anything. It's only to bring the device to a full reboot to load a new kernel.
Odoslané z môjho HTC Desire 601

blastagator said:
What benefit would there be to non-MultiROM users? (Just curious.)
Click to expand...
Click to collapse
Not for common user, in epic4g kexec used by kernel devs to test a new kernel build without replace the existing kernel.
They just load a temporary kernel to test. Then that kernel will gone after a reboot.

Hope to see new kernels that support MultiRom! Great work man!

Would this allow a multiboot with AOSP and Stock roms?

AbdulrahmanAmir said:
it doesnt work while i have stock and the secondary is aosp (dU-dirty.unicorn) when i boot the secondary it works sound only but no display just black screen plzz help
Click to expand...
Click to collapse
The patch is not necessary at the moment, because of the locked bootloader. It's just for devs to be prepared with their kernel when we can unlock the bootloader, so that multirom will work as it should.
Odoslané z môjho HTC Desire 601

Thanks for your great thread. But there is no instruction about how we can add that patch to kernel source. Could you write more details about implanting this patch?

No response??

mohamaadhosein said:
No response??
Click to expand...
Click to collapse
Download the patch file from first post and place it in the kernel root directory. Then you should use this command to check if there are any conflicts: git apply --check <path_to>.patch
If there are no errors, use this to apply: git apply <path_to>.patch
Sorry for the late response but I checked xda when I wasn't home and I forgot to reply when I got home
Odoslané z môjho HTC Desire 601

Hey, some changes need to be made to the patch.
On line 353, change the number from 22 to 21. Also, it has some errors when modifying head.S, which I had to fix manually..
But guys, my kernel is building with the latest multirom. This **** is going to maybe work soon!
I'll keep you all posted.

Thank you man

Guys, I think I've done it. Kexec hardboot patched kernel for 5.1.1 and thus multirom compliant, which I am preparing to build with twrp. this is very exciting.

When will it be ready?

Are you kidding me? No ETAs. I literally haven't even announce it yet and somebody asks for an ETA.... It will be ready once I test everything to boot well on my device.

patrik.KT said:
Download the patch file from first post and place it in the kernel root directory. Then you should use this command to check if there are any conflicts: git apply --check <path_to>.patch
If there are no errors, use this to apply: git apply <path_to>.patch
Sorry for the late response but I checked xda when I wasn't home and I forgot to reply when I got home
Odoslané z môjho HTC Desire 601
Click to expand...
Click to collapse
It says the patch is corrupted on the line 375

Guide for Building Custom Kernel XPERIA E1

This is not my work this a reply i got from a guy when i posted in the sony developers forum ...I hope someone finds this useful:angel: .And since i m a new user i can post links for some stupid reasons...so i will get creative
by fzort
Kernel source for the Xperia E1 is available as a tarball on the "Xperia open source archives" site. I'm running a custom-built kernel on my Xperia E1 (D2114). I documented what I did here:
[https://
github.com
/mpersano
/xperia-e1-kernel-patches
/blob
/master
/README.md]

https://github.com/mpersano/xperia-e1-kernel-patches/blob/master/README.md

This is for KK or JB4.3?
Since im starting development for this device, idk much and i not read actual progress. @Kizoky you can resume progress for me?

Caio99BR said:
This is for KK or JB4.3?
Since im starting development for this device, idk much and i not read actual progress. @Kizoky you can resume progress for me?
Click to expand...
Click to collapse
This is for KK kernel, but I couldn't not build kernel because I'm still a rookie
Camera drivers exists for MSM8610(Xperia E1's chipset) on sonyxperiadev Github
Recovery exists (you can find PhilZ recovery in this forum)
what is still missing is a working Device tree, and vendor libs (and of course a cm compatible kernel)

Kizoky said:
This is for KK kernel, but I couldn't not build kernel because I'm still a rookie
Camera drivers exists for MSM8610(Xperia E1's chipset) on sonyxperiadev Github
Recovery exists (you can find PhilZ recovery in this forum)
what is still missing is a working Device tree, and vendor libs (and of course a cm compatible kernel)
Click to expand...
Click to collapse
Ok, but for now a kernel working in Stock is good, so how i can unpack boot.img?
Enviado de meu E435 (L3 II Dual) usando Tapatalk

Use this:

Zsenyka said:
Use this:
Click to expand...
Click to collapse
Edited: The Bootloader is locked, so the boot.img is "Encripted", and no way to unpack this, i will unlock this.

Ok, i changed boot.img, now i have CWM from boot, and bootsrap.
I tried to boot it, but this get bootloop, the bootanimation is loaded but bootloop, maybe dt.img.
I cant access dmesg command. @Kizoky any tip?
---------- Post added at 10:44 PM ---------- Previous post was at 10:44 PM ----------
https://github.com/Caio99BR/android_kernel_sony_falconss

Caio99BR said:
Ok, i changed boot.img, now i have CWM from boot, and bootsrap.
I tried to boot it, but this get bootloop, the bootanimation is loaded but bootloop, maybe dt.img.
I cant access dmesg command. @Kizoky any tip?
Click to expand...
Click to collapse
Hi! I'm the owner of the github repo mentioned at the top of this thread.
Getting a working ramdisk took me a while. I think that what finally worked was downloading an official firmware image with XperiFirm (you don't even need to wait for it to finish downloading the full image - one of the first files downloaded is the kernel one, containing boot.img), then I extracted boot.img with the unofficial XPERIA flash tool, then extracted the ramdisk. (The kernel command line I used is the same one in the official boot.img, by the way.) As for the device tree image, you can build it from the kernel sources.
Note that boot.img on this phone has a device tree blob appended to the end. I wrote a small script to unpack the official boot.img and compare it to the one that I built and check if I was doing everything right (can't post links as I'm a new user, but it's linked in the README.md file linked above).
I'll try to add more details to those instructions when I have some time (I didn't think anyone else would be interested in building a kernel for this cheap phone ). By the way, I use the E1 with a custom kernel as my main personal phone and it works fine (for a 512M phone), kudos to Sony for not compromising the quality of even their lowest end model.

I think everyone is interested in making this phone better
Since July 2014 we tried porting Cyanogenmod without success, now last year we modified a Moto E ROM and made it work with E1, only the ril is not working
So sad that Sony didn't made this phone even better
So the device tree is located in the ramdisk?

Kizoky said:
I think everyone is interested in making this phone better
Since July 2014 we tried porting Cyanogenmod without success, now last year we modified a Moto E ROM and made it work with E1, only the ril is not working
So sad that Sony didn't made this phone even better
So the device tree is located in the ramdisk?
Click to expand...
Click to collapse
The device tree is located after the ramdisk in boot.img, but you can build it from the kernel sources provided by Sony. The `msm8610-v2-mtp.dtb` make target will build the device tree blob. Then mkqcdtbootimg will build a boot.img containing kernel + ramdisk + device tree blob. The only thing that you need for this which is not provided by Sony (well, other than more detailed build instructions...) is a ramdisk image, I had to extract it from the stock firmware...
If you want to split boot.img into kernel / ramdisk / device tree, you can use this script: github.com/mpersano/bootimg-tools/blob/master/split-bootimage.py
Good luck!

fzort said:
The device tree is located after the ramdisk in boot.img, but you can build it from the kernel sources provided by Sony. The `msm8610-v2-mtp.dtb` make target will build the device tree blob. Then mkqcdtbootimg will build a boot.img containing kernel + ramdisk + device tree blob. The only thing that you need for this which is not provided by Sony (well, other than more detailed build instructions...) is a ramdisk image, I had to extract it from the stock firmware...
If you want to split boot.img into kernel / ramdisk / device tree, you can use this script: github.com/mpersano/bootimg-tools/blob/master/split-bootimage.py
Good luck!
Click to expand...
Click to collapse
I've been trying to get that script work like ages
Does it require Linux, or just Python?
EDIT: nvm, I figured it out

So is CM for E1 finally possible or just custom kernel?

@fzort @Kizoky i make this booting with the stock dt blob (device tree means the Android Device Tree, and this is totally diff, use "dt blob")
See my changes in https://github.com/Caio99BR/android_kernel_sony_falconss
Ah, only with msm8610-v2-mtp.dtb this works too, i tested after.
("I not reply more earlier because the phone is from my father and yesterday ran out of energy.")
The ramdisks works and dt blobs too.
The screenshot

Caio99BR said:
@fzort @Kizoky i make this booting with the stock dt blob (device tree means the Android Device Tree, and this is totally diff, use "dt blob")
See my changes in https://github.com/Caio99BR/android_kernel_sony_falconss
Ah, only with msm8610-v2-mtp.dtb this works too, i tested after.
("I not reply more earlier because the phone is from my father and yesterday ran out of energy.")
The ramdisks works and dt blobs too.
The screenshot
Click to expand...
Click to collapse
I saw you are doing the device part of E1 too
If you need any help just ask me (or tests)

Kizoky said:
I saw you are doing the device part of E1 too
If you need any help just ask me (or tests)
Click to expand...
Click to collapse
Ok man, im trying to do kernel fully working (solved problem of dt blobs. We cant pack qrd dt, so comment build of then), and zip easy flashing, but not working at moment, my father will get crazy when him try to play FM Radio.
After i will merge code to a CAF Linux Kernel, so this is more easy to update.
By last finish the Android Device Tree with a E1 Caf Kernel.
I will try to post the custom kernel.
Im thinking in VeeSSKernel (Since my kernel of L3II is VeeKernel), what do you think?
Enviado de meu E435 (L3 II Dual) usando Tapatalk

Caio99BR said:
Ok man, im trying to do kernel fully working (solved problem of dt blobs. We cant pack qrd dt, so comment build of then), and zip easy flashing, but not working at moment, my father will get crazy when him try to play FM Radio.
After i will merge code to a CAF Linux Kernel, so this is more easy to update.
By last finish the Android Device Tree with a E1 Caf Kernel.
I will try to post the custom kernel.
Im thinking in VeeSSKernel (Since my kernel of L3II is VeeKernel), what do you think?
Enviado de meu E435 (L3 II Dual) usando Tapatalk
Click to expand...
Click to collapse
Would be really great
We still don't have a custom kernel (only Stock kernel with PhilZ)
I can't wait to see it

Kizoky said:
Would be really great
We still don't have a custom kernel (only Stock kernel with PhilZ)
I can't wait to see it
Click to expand...
Click to collapse
We have a problem, the TV is not working anymore, idk why
I will check it, we need TV Support working, or i need it, since my father use it
EDIT: The problem is inside kernel or ramdisk.

it's amazing .. Very good work .. Congratulations friends??

racer.z said:
it's amazing .. Very good work .. Congratulations friends����
Click to expand...
Click to collapse
@Kizoky TV is fixed
Edit: THANKS, i forget ever
---------- Post added at 10:59 PM ---------- Previous post was at 10:19 PM ----------
I will try to release tomorrow, since i want to make a new banner, based on my old VeeKernel banner.
For CM i will need to redownload CAF Kernel MSM (since im stupid and overwrited .git in tests).
I will start building TWRP (V3), merging it to stock ramdisk and update to make cwm and twrp side-by-side.
So i have done this in two weeks for make a custom kernel, thanks @fzort
Enviado de meu E435 (L3 II Dual) usando Tapatalk

[MODULE] Wireless Firmware for Nethunter

This Magisk module adds the required firmware for external wireless adapters to be used with Nethunter.
NOTE: Your kernel still needs to support external network adapters. This module only provides missing firmware, if any.
The list of included firmware is given below. For other devices, create a new issue on GitHub here.
This module should work with any variant of Nethunter, but it was created to work with Nali Kethunter (https://forum.xda-developers.com/an...li-kethunter-modded-kernel-supported-t3770455) - another Magisk module by @LazerL0rd which systemlessly installs Kali Nethunter.
Supported chipsets:
htc_7010 (used by TL-WN722N)
htc_9271
RT2870 (used by AWUS036NEH)
RT3070, RT3071 (used by TE-W322U)
RTL8188EU (used by TL-WN722N-V2)
RTL8192* (CU, EU, DE, SE)
MT7601u
Downloads
Available in Magisk Manager, also flashable zip attachment.
Changelog
Code:
v2.0.3
Added files for bcm43xx (meant for bcm4358)
v2.0.2
Added all Ralink files
Check chipset list above
v2.0.1
Added files for AR7010 and RTL8821
v2.0.0
Migrated to new Magisk Installer template
Added upater-script for zip flashing
v1.0.5
Added files for AR9170
v1.0.4
Added files for RTL8192
v1.0.3
Added files for RTL8188EU
v1.0.2
Added files for RT3070 and RT3071
v1.0.1
Added files for RT2870 and MT7601u
v1.0
Initial release
Source: https://github.com/rithvikvibhu/nh-magisk-wifi-firmware
Issues / Request other firmware: https://github.com/rithvikvibhu/nh-magisk-wifi-firmware/issues

any chance of adding in RT 8187?

thirtythr33 said:
any chance of adding in RT 8187?
Click to expand...
Click to collapse
Hm. I only seem to find drivers for RTL8187. Is that what you're looking for?

rithvikvibhu said:
Hm. I only seem to find drivers for RTL8187. Is that what you're looking for?
Click to expand...
Click to collapse
yes that is it! that would be perfect!

thirtythr33 said:
yes that is it! that would be perfect!
Click to expand...
Click to collapse
From what I can find, this should already be present by default. There are very old drivers which can be installed separately, but I don't have a lot of hope for that. Can you send a dmesg log right after plugging the adapter in? The problem might be something else.

rithvikvibhu said:
From what I can find, this should already be present by default. There are very old drivers which can be installed separately, but I don't have a lot of hope for that. Can you send a dmesg log right after plugging the adapter in? The problem might be something else.
Click to expand...
Click to collapse
yes I will definitely do that. I'm glad you said they may already be present because I am working on getting my kernel patched to enable external adapter support. so it may not even be an issue with the module I just didn't see it listed in the supported chipsets. antsy I'll respond once I get the kernel patched. thank you for responding!

not find for antheros AR9271L or AR9002U chipset
I do not find support about Atheros chipset AR9271L OR Atheros AR9002U in his description whether you can add the driver for wifi adapter card TP-Link tl-wn722n v1.
Please Help me..!!
---------- Post added at 04:47 AM ---------- Previous post was at 04:17 AM ----------
rithvikvibhu said:
From what I can find, this should already be present by default. There are very old drivers which can be installed separately, but I don't have a lot of hope for that. Can you send a dmesg log right after plugging the adapter in? The problem might be something else.
Click to expand...
Click to collapse
can you help me please to add driver for Atheros AR9271L on tl-wn722n v1

Tarra Ista said:
I do not find support about Atheros chipset AR9271L OR Atheros AR9002U in his description whether you can add the driver for wifi adapter card TP-Link tl-wn722n v1.
Please Help me..!!
---------- Post added at 04:47 AM ---------- Previous post was at 04:17 AM ----------
can you help me please to add driver for Atheros AR9271L on tl-wn722n v1
Click to expand...
Click to collapse
Both AR9271L (same as AR9271) and AR9002U are supported right from V1. Must've missed it while updating the README.
Thanks for letting me know, I'll add it to the list. Btw did you try the module? Did it work? If there are any issues, feel free to create a new issue at https://github.com/rithvikvibhu/nh-magisk-wifi-firmware/issues

rithvikvibhu said:
This Magisk module adds the required firmware for external wireless adapters to be used with Nethunter.
Supported chipsets:
htc_7010 (used by TL-WN722N)
Click to expand...
Click to collapse
What about ath9k_htc driver ?
Its better than htc_7010

bezpieka said:
What about ath9k_htc driver ?
Its better than htc_7010
Click to expand...
Click to collapse
I haven't given it much thought really. This has been working for me for years without issues.

Zip flashable thru TWRP?
Sent from my POCOPHONE F1 using Tapatalk

help please
i was searching for the MT7612U driver, can you add it or tell me how i can add by myself plz?
thanks

ellednarb666 said:
Zip flashable thru TWRP?
Sent from my POCOPHONE F1 using Tapatalk
Click to expand...
Click to collapse
Yes. Both via Magisk Manager and TWRP.
SPIKELORD said:
i was searching for the MT7612U driver, can you add it or tell me how i can add by myself plz?
thanks
Click to expand...
Click to collapse
You basically have to find the correct firmware files for that chipset. I'll try to look for it and add it.

I already flashed thru magisk (repo) but still my external adapter is undetected.
My device is Poco F1 and my question is, should I just flash the zip or extract the firmware and place to the right path?
Sent from my POCOPHONE F1 using Tapatalk

ellednarb666 said:
I already flashed thru magisk (repo) but still my external adapter is undetected.
My device is Poco F1 and my question is, should I just flash the zip or extract the firmware and place to the right path?
Sent from my POCOPHONE F1 using Tapatalk
Click to expand...
Click to collapse
Just flash it. No need to extract anything.
Get the latest copy from the GitHub repo. I haven't updated the files on XDA or even GitHub releases in a long time.

Flashing didnt work.
Btw, my phone is Poco and my Ext Wifi is Tenda W311M v2
Sent from my POCOPHONE F1 using Tapatalk

ellednarb666 said:
Flashing didnt work.
Btw, my phone is Poco and my Ext Wifi is Tenda W311M v2
Sent from my POCOPHONE F1 using Tapatalk
Click to expand...
Click to collapse
Check out GitHub issues, feel free to create one with dmesg right after plugging the adapter.
Also, some people miss it:
If it does not work, then make sure you have the correct drivers installed, kernel built with support, etc. This module only adds some firmware files required, systemless-ly.

What that means?
NOTE:*Your kernel still needs to support external network adapters.*
I need custom kernel with rtl8812au drivers inside? So why i need this firmware if i need kernel? Or just kernel with enabled modules?

unknown1818 said:
What that means?
NOTE:*Your kernel still needs to support external network adapters.*
I need custom kernel with rtl8812au drivers inside? So why i need this firmware if i need kernel? Or just kernel with enabled modules?
Click to expand...
Click to collapse
This module only provides firmware files that some devices need (located at /etc/firmware/). It isn't a replacement for kernels with support for the adapters.

Will try it, i found files for rtl8188eu in the kernel source of NetHunter for OnePlus7

[UEFI][Bootloader]EDK II port for sagit

An explain goes first:
This may surprise a lot of people ,"Whaaaat ? Isn't UEFI a kind of BIOS on PC?"Well, it can also be on your phone too , in fact.
This is an EDK II (UEFI) port for MI 6.Currently it's incomplete,and how much it will be in the future depends on whether I have enough time.
What is this port for?
This is an UEFI port, so there are many possibilities. As a second-stage bootloader, it can boot any ARM64 OSes that support UEFI.
But at this point, only Linux is capable.Windows booting still need more efforts.
See Github README.md for more details.
Download:
Only source is provided since it's not completed.
Source: https://github.com/fxsheep/edk2-sagit

What the ****...... Dude you're awesome. I'll be glad to help in testing if you need.
Keep it up...

neXus PRIME said:
What the ****...... Dude you're awesome. I'll be glad to help in testing if you need.
Keep it up...
Click to expand...
Click to collapse
Thanks

Love this. Thanks for your work. Will test it tomorror.

wow! How amazing it is !

Thanks for the source and btw, @vantoman has built it yesterday and I tried it (fastboot boot uefi.img), it starts up and shows a grub shell just fine. But I couldn't figure out the way to input anything to there (tried usb otg keyboard but nope, not even the usb port outputs power lol). But to me, this is a proof of concept so, if we can help in any ways, please let us know ?

ccelik97 said:
Thanks for the source and btw, @vantoman has built it yesterday and I tried it (fastboot boot uefi.img), it starts up and shows a grub shell just fine. But I couldn't figure out the way to input anything to there (tried usb otg keyboard but nope, not even the usb port outputs power lol). But to me, this is a proof of concept so, if we can help in any ways, please let us know ?
Click to expand...
Click to collapse
That's right as USB OTG hasn't been implemented yet.And probably it won't be easily.Basically I use drivers extracted from the device's XBL.While the OTG isn't probably even exist in that, I just wonder if it's possible.Maybe the bios from some SD835 laptops will help though.

Anyway input isn't necessary for GRUB2 to boot a linux kernel

fxsheep said:
That's right as USB OTG hasn't been implemented yet.And probably it won't be easily.Basically I use drivers extracted from the device's XBL.While the OTG isn't probably even exist in that, I just wonder if it's possible.Maybe the bios from some SD835 laptops will help though.
Click to expand...
Click to collapse
Hmmm, right.. Tell me if I can help you in any ways then ?
---------- Post added at 12:47 PM ---------- Previous post was at 12:46 PM ----------
fxsheep said:
Anyway input isn't necessary for GRUB2 to boot a linux kernel
Click to expand...
Click to collapse
Yeah But streamlining the installation processes etc (but yeah, üt could be done after getting the more important parts to work).

ccelik97 said:
Hmmm, right.. Tell me if I can help you in any ways then ?
---------- Post added at 12:47 PM ---------- Previous post was at 12:46 PM ----------
Yeah But streamlining the installation processes etc (but yeah, üt could be done after getting the more important parts to work).
Click to expand...
Click to collapse
You can do all the installation process on your PC instead on phone.Just use a chroot environment.
Mount the phone's storage to PC using mass_storage in Android kernel.

fxsheep said:
You can do all the installation process on your PC instead on phone.Just use a chroot environment.
Mount the phone's storage to PC using mass_storage in Android kernel.
Click to expand...
Click to collapse
Hmmm I didn't know about that. Thanks for letting me know, I'll look for it.

@fxsheep Could you please port EDK II to Xiaomi mi 5 (MSM8996)?

zengxianxi said:
@fxsheep Could you please port EDK II to Xiaomi mi 5 (MSM8996)?
Click to expand...
Click to collapse
In theory 8996 already uses UEFI as a part of the boot chain, thus porting is not difficult(at least bring up emmc).But you know, this port isn't complete either:

fxsheep said:
In theory 8996 already uses UEFI as a part of the boot chain, thus porting is not difficult(at least bring up emmc).But you know, this port isn't complete either:
Click to expand...
Click to collapse
And how to extract UEFI DXE efi files from the original XBL of msm8996 and port it?

zengxianxi said:
And how to extract UEFI DXE efi files from the original XBL of msm8996 and port it?
Click to expand...
Click to collapse
dump XBL from your device, unpack it with 7zip,or uefi-firmware-parser on github

can we run windows 10 core someday on sagit ?

Just to know about the possibilities and implications:
Could it be possible to multiboot some day?
And something like the efidroid project?

leo.sfsm said:
Just to know about the possibilities and implications:
Could it be possible to multiboot some day?
And something like the efidroid project?
Click to expand...
Click to collapse
If you are asking about 'possibilities', then of course, it is possible,by porting EFIDroid multiboot components to ARM64.
(Yeah nothing is impossible, even Windows 10 Desktop.There's already working SoC drivers available and touchscreen driver is probably also available ,since MI6 has synaptics_dsx ,the same as Lumia950XL)
But again, it needs countless efforts, especially UEFI part, and that's currently out of my reach.

leo.sfsm said:
Just to know about the possibilities and implications:
Could it be possible to multiboot some day?
And something like the efidroid project?
Click to expand...
Click to collapse
actually there is a project named multirom for modified twrp:crying:

Thanks for the source bro , but , anyone know how to debug ? Cas there's no input avalaible on the shell , no usb output or input ...? Anyone help
edit: i can boot the last manline ubuntu kernel 5.4-arm64 to the initeamfs no kernel panic
usin a startup.nsh script uder the root of firmware partition
the txt file attatched rename it to startup.nsh and place it to /vendor/firmware_mnt/startup.nsh
and place your initrd to /vendor/firmware_mnt/initrd.img
copy your vmlinuz to /vendor/firmware_mnt/efi/boot/vmlinuz.efi
reboot to fastboot than fastboot boot uefi.img