Huawei E3276 (huawei-e3276)
| This device is unsupported by Nura (most likely due to its architecture being unsupported, or limited system resources).
Reason: Awful kernel source, and unsupported kernel version |
 The modem | |
| Manufacturer | Huawei |
|---|---|
| Name | E3276 LTE Modem |
| Codename | huawei-e3276 |
| Model | E3276 |
| Released | 2012 |
| Type | embedded |
| Hardware | |
| Chipset | Huawei Balong (HiSilicon) Hi6920 V7R1 |
| CPU | ARM Cortex-A9 |
| GPU | Unknown |
| Display | none |
| Storage | 256 mb |
| Memory | 256 mb |
| Architecture | armv7 |
| Software | |
Original software  The software and version the device was shipped with. |
Huawei HiLink proprietary software (Android based) Unknown |
Extended version The most recent supported version from the manufacturer. |
Huawei HiLink proprietary software (Android based) Unknown |
| Nura | |
Pre-built images Whether pre-built images are available from the Nura Installation page. |
no |
Mainline Instead of a Linux kernel fork, it is possible to run (Close to) Mainline. |
no |
pmOS kernel The kernel version that runs on the device's port. |
2.6 |
Unixbench score Unixbench Whetstone/Dhrystone score. See Unixbench. |
0.0 |
Contributors
Users owning this device
How to enter flash mode
Balongdload and balongflash is very unstable on linux. You should and must use the windows versions instead.
The pin near the mmc boots to 3G PCUI mode that needs usbloader loading.
The pin near the soc boot to Application n PCUI mode. You do not need to load usbloader.
telnet access
Any firmware for e3276 or e3272 work (BE CAREFUL)
Make sure it has "TLN" or "ADB" if you want telnet or/with adb over tcpip
Extracting firmware
If you have the firmware binary (extracted from the program on telnet section it is named 279 and 50 mb) you can extract it using balong flash.
00-00000100-Ptable_R1.bin: data 01-00000101-Bootloader_R1.bin: data 02-00000102-Bootrom_R1.bin: data 03-00550103-VxWorks_R1.bin: data 04-00000104-Fastboot_R1.bin: data 05-00000105-Kernel_R1.bin: Android bootimg, kernel (0x33f10000), ramdisk (0x34f08000), page size: 2048, cmdline (root=/dev/ram0 rw console=ttyAMA0,115200 console=uw_tty0,115200 rdinit=/init mem=44m lpj=3989504) 06-00000107-System_R1.bin: YAFFS filesystem root entry (little endian), type root or directory, v1 root directory 07-00000066-Nvimage_R1.bin: data 08-00000109-APP_R1.bin: YAFFS filesystem root entry (little endian), type root or directory, v1 root directory
You can see that it has an android boot image, an (suspicious) fastboot thing, and a system partition (with yaffs filesystem)