UZ801 V3.0 Support about openstick HOT 92 OPEN

regarding adb. I suspect that mobian bookworm repository got rid of adb bridge functionality (did bullseye had adb working ? I don't remember). At least this: "It's possible to connect to Mobian device with a similar end result as using adb shell with an Android device, but using the USB-C connection and SSH instead." sounds like adb is not possible source.

So after all I just figured out how to enable serial port over usb (I guess it is very similar to adb shell):

• edit /usr/sbin/mobile-usb-gadget by adding:

    # Create ACM (serial) function
    echo "Adding ACM function..."
    mkdir $CONFIGFS/functions/acm.usb0
    ln -s $CONFIGFS/functions/acm.usb0 $CONFIGFS/configs/c.1

after line 39

• enable serial console sudo systemctl enable [email protected]
• reboot

after that on Your host /dev/ttyACM<n> should appear

from openstick.

Can anyone please share a stock EDL dump for UZ801_v3.0 (board like the one on photo). My stock image is lost and SIM is constantly in "power state: off", no matter what I try.

I created this repository already half a year ago, the only thing is that the image is a little broken (read the release description) but overall it works

from openstick.

Your board is UFI003. Firmware files in debian.zip are for UFI001 and (as you've witnessed) aren't fully compatible.
WiFi may work somewhat with the wrong firmware, but it may not be fully stable and may have broken AP mode.
Unfortunately, unless someone else uploads dumps for UFI003, there isn't much you can do to fix the modem.

You should have taken a full flash dump before flashing. Or grabbed a 2-pack, like I did. These sticks are dirt cheap.

from openstick.

@lfgomez You can find kernel build instructions on OpenStick's Chinese wiki (use Google translate). They are somewhat incomplete, but it's not hard to figure out the missing parts. First, you will have to build kernel .DEB packages and install them on the stick. This will generate an initrd image. You can then build boot.img with mkbootimg tool using kernel+dtb and initrd images. The wiki suggests to use QEMU and chroot to ARM rootfs, but this is unnecessary. Simply installing the DEB packages on the stick with existing Debian installation will work just fine to generate the initrd.

I have tested mainline kernel 6.3-rc4 (mainline, not the msm8916 fork) on my UZ801 v3.0 and it appears to crash on boot, even though a dev who submitted a PR to mainline kernel with the DTS file for UZ801 v3.0 claims that the stick should fully work with the mainline kernel. Without access to UART console it's hard to tell what exactly is wrong with that kernel though, it could be just a simple configuration issue. Maybe you'll have better luck with the msm8916 fork on your UF896.

I'm the one who maintains the mainstream dts, do you mind PM me about the details? I have only tested a mainlined pmOS, which works as intended. It's recommended to read the relevant pmOS wiki page.

from openstick.

@ddscentral Thanks for all your work. I flashed succesfully my UZ801 V3.2 stick. After flashing with your very good manual https://zebra.ddscentral.org/pub/downloads/openstick/firmware/uz801_v30/README it works but there are three problems:

• The wifi connection is very slow (in AP modes with hostapd) max 2MB/sec
• Also the 4G/LTE connection is also very slow (also max 2MB/sec), tested with the USB ethernet connection and WIFI. With the original firmware i get 30MB/sec.
• UPDATE ISSUE SOLVED (with linux not windows) ADB is not working anymore (i can't use it also not with holding the button on booting)
  I upgrade this stick to bookworm with a apt dist-upgrade command.

What can i do to resolve these issues?

WIFI config:
`interface=wlan0
driver=nl80211
ssid=example
channel=1
hw_mode=g
macaddr_acl=0
auth_algs=3
ignore_broadcast_ssid=0

wpa=2
wpa_passphrase=pass
wpa_key_mgmt=WPA-PSK
wpa_pairwise=TKIP
rsn_pairwise=CCMP
obss_interval=1

ieee80211n=1
ht_capab=[HT40+][SHORT-GI-20][SHORT-GI-40][SMPS-STATIC][DSSS_CCK-40][MAX-AMSDU-3839]`

from openstick.

I have a UZ801 V3.0 stick that is still running the original firmware and I would like to get a dump of it.
Do you by chance know a link with some hints on how to do that with edl?
Thank you

from openstick.

Well, let's hope you're not the only one who has a V3.2 board.

from openstick.

ok, i will make a small tutorial how to do this

from openstick.

I have UZ801 v3.2 stick. I successfully flashed debian using @ddscentral instructions here.
Then I upgraded debian to bookworm using official debian procedure here
I fixed the mobian repository key using this
I created WIFI AP with NetworkManager using this

Everything seems to be working, but ... I made tests with iperf and:

• on usb ethernet I get aroung 100MB - cool
• on wifi ap I get around 30MB - cool ? does anyone get better results ?
• on LTE I get only 1/2MB - not cool. does anyone get better results ?

So reading the posts in this thread I tried to use firmware for V3.2. As I understand only @Smit1237 has dumped it, but the files are EXATCLY the same as V3.0 from @ddscentral. So the question is do @Smit1237 really has V3.2 ? What else can I do to investigate the problem ?

PS. I do not have stock firmware of the stick .... bummer

from openstick.

no, thanks

from openstick.

Firmware files and the fixed kernel can be found here.
Kernel is in the "kernel" directory, firmware is in "modem_wifi". Kernel is built using sources from here.

First, install the *.deb packages using dpkg, then flash the provided boot.img to /dev/mmcblk0p12. Simple "dd" command should work.
Do triple check the partition number ! Flashing to the wrong one will soft-brick your stick !
Do fdisk -l /dev/mmcblk0 if you are not sure which partition contains boot.img (it should be 64M in size). But I believe the partition layout is the same on all devices.

Reboot after flashing. If everything went fine, you should see the red LED blinking, indicating that the system is running. Blue LED is set to trigger on WiFi TX, Green LED has no default trigger.

After rebooting, old kernel packages can be uninstalled to free up space.

from openstick.

I'm just buy the stick and flash debian without any backup
Now my modem does not work, (sim-missing). But wifi, usb... are normal
How can i make my modem work please?

Every info i have now is this:

Show more info about it. Here is overview info on the device
SN: 1000000050797F
IMEI: 864686020681343
IMSI: 452040324276759
ICCID: 89840480003242767594
SSID: 4G-UFI-575C
Signal: -97
WAN IP: 21.61.175.108
HW Version: HW1.3
SW Version: UFI_003_V01_ZX_DD_221215
Web Version: WEB_V1.0.303#
Baseband: UFI003_CT 20220903

from openstick.

Hi, I followed all the steps, I copied the firmwares but when I check the modem information with mmcli -m 0, I get:

Status | lock: sim-pin2
| unlock retries: sim-pin (3), sim-puk (10), sim-pin2 (3), sim-puk2 (10)
| state: enabling
| power state: off
| signal quality: 0% (cached)

if i try to start modem :

user@openstick:~$ mmcli -m 0 --enable
error: couldn't enable the modem: 'GDBus.Error:org.freedesktop.libqmi.Error.Protocol.DeviceNotReady: Couldn't set operating mode: QMI protocol error (52): 'DeviceNotReady''

Do you have idea ? i try to make low cost lte proxy but with the stock firmware i have all the times crash etc (i have 200 dongles for this) my projet it's to pass my dongles to debian for more stability but lte don't work :/

from openstick.

Does the SIM card have a PIN code ? It looks like it's locked.

from openstick.

With the firmware uz801 https://github.com/OpenStick/OpenStick/releases i have this :

but i can't connect to the network :

user@openstick:~$ mmcli -m 0 --simple-connect="apn=internet.voo.be,user=,password="

error: couldn't connect the modem: 'GDBus.Error:org.freedesktop.ModemManager1.Error.Core.InProgress: Connection request forbidden: operation already in progress'

Do you have an idea ? i have FY_UZ801_V2.1 on the dongle

from openstick.

With the v1 version the 3g work but i cannot active the connection with nmtui. I need to find the firmware for V2 version :/

from openstick.

Status shows "Status: lock: sim-pin2" Again, have you tried unlocking ?
You can try my UZ801 v3.0 firmware.
It seems that different revisions of UZ801 have different firmwares. File sizes differ in mine and the UZ801 one from the "Releases" section.

from openstick.

@ddscentral May I ask you how did you generate the boot.img file? I compiled the last msm8916-mainline kernel release (v6.3: the change log says it should support the UF896 stick), but couldn't generate the boot.img. Thanks!

from openstick.

@lfgomez You can find kernel build instructions on OpenStick's Chinese wiki (use Google translate). They are somewhat incomplete, but it's not hard to figure out the missing parts.
First, you will have to build kernel .DEB packages and install them on the stick. This will generate an initrd image. You can then build boot.img with mkbootimg tool using kernel+dtb and initrd images.
The wiki suggests to use QEMU and chroot to ARM rootfs, but this is unnecessary. Simply installing the DEB packages on the stick with existing Debian installation will work just fine to generate the initrd.

I have tested mainline kernel 6.3-rc4 (mainline, not the msm8916 fork) on my UZ801 v3.0 and it appears to crash on boot, even though a dev who submitted a PR to mainline kernel with the DTS file for UZ801 v3.0 claims that the stick should fully work with the mainline kernel.
Without access to UART console it's hard to tell what exactly is wrong with that kernel though, it could be just a simple configuration issue.
Maybe you'll have better luck with the msm8916 fork on your UF896.

from openstick.

@185264646 Not sure which details do you mean.
A mainline kernel is supposed to run with all distros, not just postmarketOS. If one distro works, others should work too if the kernel config is correct.
If like you say mainline kernel has worked for you, it would be good to get the config file that you've used so I can test your DTS with a Debian installation.
Let's hope pmOS doesn't use major out-of-tree hacks to get things going. Alpine is not on my list of favorite distros (except for Docker containers).

from openstick.

@185264646 Not sure which details do you mean. A mainline kernel is supposed to run with all distros, not just postmarketOS. If one distro works, others should work too if the kernel config is correct. If like you say mainline kernel has worked for you, it would be good to get the config file that you've used so I can test your DTS with a Debian installation. Let's hope pmOS doesn't use major out-of-tree hacks to get things going. Alpine is not on my list of favorite distros (except for Docker containers).

Basically we use the same config, that is make msm8916_defconfig pmos.config. it should be generic enough for any distro. Some people in a forum has tested mainline kernel and it works. I want to know what firmwares has been replaced. Because it's known that it must use sbl1 from db410c unlike ufi001c(which does not need sbl1 from db410c) or it reboots as soon as rmtfs is up.

from openstick.

The SBL1 binary in my modded stick is from base.zip. Not sure where it was taken from. I assume it's from the UFI001C.
Would dumping one from the factory ROM help ? I have a second identical stick with stock Android on it.

Also, is it safe to swap just the SBL1 partition or would I need to reflash other sensitive partitions as well (hyp, rpm, tz, cdt) ? Sorry if this sounds noob-ish, just don't want to end up with a brick.

from openstick.

The SBL1 binary in my modded stick is from base.zip. Not sure where it was taken from. I assume it's from the UFI001C. Would dumping one from the factory ROM help ? I have a second identical stick with stock Android on it.

Also, is it safe to swap just the SBL1 partition or would I need to reflash other sensitive partitions as well (hyp, rpm, tz, cdt) ? Sorry if this sounds noob-ish, just don't want to end up with a brick.

Well, flashing any sbl1 is quite safe AFAIK. You only need to be careful when flashing tz and hyp since they must be paired, i.e., stock tz + stock hyp / db410c tz + db410c hyp(qhypstub). It'll brick before aboot (which provides fastboot interface) if you use other combination like stock tz+db410c hyp or db410c tz + stock hyp. CDT seems like an unused partition.

The base.zip should be okay. If you already flashed base.zip, sbl1 shouldn't be an issue.

from openstick.

@lfgomez You can find kernel build instructions on OpenStick's Chinese wiki (use Google translate). They are somewhat incomplete, but it's not hard to figure out the missing parts. First, you will have to build kernel .DEB packages and install them on the stick. This will generate an initrd image. You can then build boot.img with mkbootimg tool using kernel+dtb and initrd images. The wiki suggests to use QEMU and chroot to ARM rootfs, but this is unnecessary. Simply installing the DEB packages on the stick with existing Debian installation will work just fine to generate the initrd.

I have tested mainline kernel 6.3-rc4 (mainline, not the msm8916 fork) on my UZ801 v3.0 and it appears to crash on boot, even though a dev who submitted a PR to mainline kernel with the DTS file for UZ801 v3.0 claims that the stick should fully work with the mainline kernel. Without access to UART console it's hard to tell what exactly is wrong with that kernel though, it could be just a simple configuration issue. Maybe you'll have better luck with the msm8916 fork on your UF896.

Have you ever tried msm8916-mainline/linux.git? Does it work? Would you please bisect it if this fork is working while mainline is not? There are not too many downstream commits there and most of them are just dts changes so it shouldn't consume too much time.

from openstick.

Ok, I will give it a try and report back.

from openstick.

@lfgomez You can find kernel build instructions on OpenStick's Chinese wiki (use Google translate). They are somewhat incomplete, but it's not hard to figure out the missing parts. First, you will have to build kernel .DEB packages and install them on the stick. This will generate an initrd image. You can then build boot.img with mkbootimg tool using kernel+dtb and initrd images. The wiki suggests to use QEMU and chroot to ARM rootfs, but this is unnecessary. Simply installing the DEB packages on the stick with existing Debian installation will work just fine to generate the initrd.
I have tested mainline kernel 6.3-rc4 (mainline, not the msm8916 fork) on my UZ801 v3.0 and it appears to crash on boot, even though a dev who submitted a PR to mainline kernel with the DTS file for UZ801 v3.0 claims that the stick should fully work with the mainline kernel. Without access to UART console it's hard to tell what exactly is wrong with that kernel though, it could be just a simple configuration issue. Maybe you'll have better luck with the msm8916 fork on your UF896.

Have you ever tried msm8916-mainline/linux.git? Does it work? Would you please bisect it if this fork is working while mainline is not? There are not too many downstream commits there and most of them are just dts changes so it shouldn't consume too much time.

Yes, I was able to generate the boot deb file for the kernel and the boot image using the info of the address that @ddscentral replied. But I was unable to boot the stick with this image. After flash it, I always get a red led on and nothing more. I was able to revive the stick using EDL mode to flash a functional boot image. I have no idea what is the error during the boot as I don't have the Serial terminal output yet. If anyone has any other ideas, I can try on my stick.

from openstick.

Sorry, I did not have time to test the mainline kernel myself due to lack of free time.

@lfgomez What did you see on boot after flashing the kernel ? With the correct DTS file, you should have at the very least get a blinking red LED after power on (this indicates that the kernel is running). It would also be useful to change the green (or blue) LED trigger in the DTS file to mmc0. This would allow you to see if there's any disk activity during boot.

BTW, I have a fixed aboot.img with GPIO pins correctly assigned to match the UZ801's configuration. With this, you can boot to fastboot by holding the reset key during power on. Useful for testing kernels.

from openstick.

@jongerenchaos What's the overall stability of the device other than the issues you've mentioned ? Any spontaneous reboots/crashes ?
Also, what firmware did you use for WiFi and LTE ? Did you dump your own or used mine ?
ADB should run at boot, not sure why it doesn't work for you.
I've disabled ADB on my stick as I use USB in host mode with some extra storage connected.
For button to work at boot, you need to reflash the bootloader.
Glad to hear bookworm works :) Haven't tried any major OS upgrades on my stick yet.

My hostapd.conf looks like this

interface=wlan0
driver=nl80211
logger_syslog=-1
logger_syslog_level=2
logger_stdout=-1
logger_stdout_level=2
ctrl_interface=/run/hostapd
ctrl_interface_group=0
country_code=**
hw_mode=g
channel=6
beacon_int=100
dtim_period=2
max_num_sta=10
rts_threshold=-1
fragm_threshold=-1
macaddr_acl=0
auth_algs=1
ignore_broadcast_ssid=0
wmm_enabled=1
wmm_ac_bk_cwmin=4
wmm_ac_bk_cwmax=10
wmm_ac_bk_aifs=7
wmm_ac_bk_txop_limit=0
wmm_ac_bk_acm=0
wmm_ac_be_aifs=3
wmm_ac_be_cwmin=4
wmm_ac_be_cwmax=10
wmm_ac_be_txop_limit=0
wmm_ac_be_acm=0
wmm_ac_vi_aifs=2
wmm_ac_vi_cwmin=3
wmm_ac_vi_cwmax=4
wmm_ac_vi_txop_limit=94
wmm_ac_vi_acm=0
wmm_ac_vo_aifs=2
wmm_ac_vo_cwmin=2
wmm_ac_vo_cwmax=3
wmm_ac_vo_txop_limit=47
wmm_ac_vo_acm=0
ieee80211n=1
ht_capab=[SHORT-GI-20] [GF] [DSSS_CCK-40] [LSIG-TXOP-PROT]
eapol_key_index_workaround=0
eap_server=0
own_ip_addr=127.0.0.1
auth_algs=1
wpa=2
ssid=******
wpa_key_mgmt=WPA-PSK
wpa_pairwise=CCMP
wpa_passphrase=******

I've replaced the sensitive bits with asterisks.

from openstick.

@jongerenchaos What's the overall stability of the device other than the issues you've mentioned ? Any spontaneous reboots/crashes ?

Yeps it is not stable. The LTE connection lost his connection after some minutes

Also, what firmware did you use for WiFi and LTE ? Did you dump your own or used mine ?

I used yours and i didn't make a backup. I ordered a new one to save this files and use them on this stick. So maybe that's the reason that this not work properly....

ADB should run at boot, not sure why it doesn't work for you. I've disabled ADB on my stick as I use USB in host mode with
some extra storage connected. For button to work at boot, you need to reflash the bootloader.

Flashboot works after some extra tests (only for me on linux), so i can reflash it...

Glad to hear bookworm works :) Haven't tried any major OS upgrades on my stick yet.
;)

I will try your wifi config and i let you know the results

from openstick.

@jongerenchaos WiFi issues may also be caused by mismatched firmware and/or NVRAM. You can try out my hostapd config. If it doesn't fix your WiFi issues, you will need to wait for the second stick to arrive to get the correct firmware and NVRAM from it.
As for LTE, you will need to wait for the second stick to dump the modem firmware.
Let's hope your second stick will have the same board revision.

from openstick.

I've got two V3.2 sticks and was lucky enough to want a full test of the first one before flashing the second one, so it's still untouched beyond enabling adb via http://192.168.100.1/usbdebug.html . I have a root shell and adb access, and I'm willing to dump files from it. I'd be glad to get instructions, and will browse the rootfs otherwise when I find some time.

from openstick.

Full backup more info: https://forum.xda-developers.com/t/guide-full-phone-backup-without-unlock-or-root.1420351/

For only the files for using debian

1. Enable ADB
2. Backup WIFI firmware (adb pull persist) and copy them to the ddscentral image, step 2
3. Backup Modem files (adb pull firmware) and copy them to the ddscentral image, step 1

from openstick.

Thanks @jongerenchaos. I've pulled persist, and WCNSS_qcom_wlan_nv.bin is unchanged since 3.0 (same SHA1). I also get ~6MB/s over client-mode WiFi with that, as opposed to ~2MB/s with the one bundled with the Debian image.

EDIT: ATTENTION! The below is not from a V3.2 but from a V3.0 stick!

Quite a few files are changed in /firmware/image, I've dumped them to https://op-co.de/tmp/firmware-image-3.2.tar.xz and copied them over root@openstick:/lib/firmware/, and now the modem status is alternating between "enabling" and "disabled". With the 3.0 modem files, I was able to connect with one of two SIMs I tested, while the other SIM was (edit follows) showing as "enabled" but not providing an IP address on the wwan interface.

from openstick.

Using the 3.0 firmware files, ModemManager is looping through this every minute for a while before giving up:

Aug 08 07:51:14 openstick ModemManager[308]: <info>  [modem0] 3GPP registration state changed (unknown -> idle)
Aug 08 07:51:37 openstick ModemManager[308]: <info>  [modem0] simple connect started...
Aug 08 07:51:37 openstick ModemManager[308]: <info>  [modem0] simple connect state (4/8): wait to get fully enabled
Aug 08 07:51:37 openstick ModemManager[308]: <info>  [modem0] simple connect state (5/8): register
Aug 08 07:51:53 openstick ModemManager[308]: <info>  [modem0] 3GPP registration state changed (idle -> unknown)
Aug 08 07:51:53 openstick ModemManager[308]: <warn>  [modem0] couldn't load operator code: Current operator MCC/MNC is still unknown
Aug 08 07:51:53 openstick ModemManager[308]: <warn>  [modem0] couldn't load operator name: Current operator id is still unknown

The SIM didn't need any special config with the original Android firmware on that dongle, so there must be something missing in the drivers or firmware or config.

from openstick.

@ge0rg Did you copy region-specific mcfg_sw.mbn from image/modem_pr ? I'm asking because this step is somewhat unuintuitive and easy to skip accidentally. I'm not entirely sure whether it's absolutely necessary though.

As for other issues, WiFi is indeed somewhat slow'ish, about 14-16mbits/s but I only tested using a WiFi to Ethernet bridge (repurposed cheap router) with a plasterboard wall between the stick and the bridge. Will try testing directly to see if performance remains the same.
Modem itself does about 5-16 mbits/s down (with speedtest-cli, depending on server) and about 1 mbits/s up. Not bad considering the poor reception and the quality of the stick's LTE antenna.

from openstick.

@ddscentral I tried modem_pr/mcfg/configs/mcfg_sw/generic/common/default/default/mcfg_sw.mbn as well as common/row as there is no specific config file for EU/Germany, but it didn't have any effect, the error message remains the same. Neither did setting the APN via mmcli or qmicli help.

For reference, I was able to do LTE at 90Mbit/s down, 50Mbit/s up via USB rndis on the Android firmware. I'll post comparison numbers with Debian as soon as I get this SIM card to work, but I have zero experience with debugging mobile modems, all my Hayes knowledge is from the 1990s ;)

P.S: could you add Provides: wireguard-modules (= 1.0.0) to your kernel .deb next time you recompile? :)

from openstick.

Using the 3.2 firmware files, it busy-loops really fast through this, and there is nothing suspicious in dmesg:

<warn>  [modem0] couldn't enable interface: 'Couldn't set operating mode: QMI protocol error (52): 'DeviceNotReady''
<info>  [modem0] state changed (enabling -> disabled)
<info>  [modem0] simple connect started...
<info>  [modem0] simple connect state (3/8): enable
<info>  [modem0] state changed (disabled -> enabling)

from openstick.

Using the 3.2 firmware files, it busy-loops really fast through this, and there is nothing suspicious in dmesg:

<warn>  [modem0] couldn't enable interface: 'Couldn't set operating mode: QMI protocol error (52): 'DeviceNotReady''
<info>  [modem0] state changed (enabling -> disabled)
<info>  [modem0] simple connect started...
<info>  [modem0] simple connect state (3/8): enable
<info>  [modem0] state changed (disabled -> enabling)

Exactly the same issues (device not ready) and same slow WIFI speed with your files (also with EU firmware). For the Netherlands there is no mcfg_sw.mbn firmware file that i can use and try also the EU default version. I get a new stick with another firmware version (v2.1) without files that we can use on this model.

With the 3.0 files the modem works but very slow (2Mbit).

Maybe that there is somebody who have another solution for this issue.

from openstick.

Okay, so I ordered another stick. The "new" one turned out to be a V2.1 (reported V3.4.3.1 in the web interface). I used the occasion to open the other one of the "old" ones I had, and to my huge disgrace I had to realize that it was actually a V3.0 and not a V3.2 one, so the firmware files I uploaded earlier are from V3.0 actually. Now I have a 3.2 with no backup, a 3.0 and a 2.1 (the latter two have the same firmware files). Bummer.

The 2.1 and 3.0 are still on original Android with adb, so I can provide additional files / data from them if needed. Also it looks that none of them works with my SIM card that's also causing trouble on the 3.2 stick with 3.0 firmware (but used to work before flashing Debian).

from openstick.

Web interface only reports the firmware version, not the hardware version (which is printed on the board itself).
One of the major issues when buying these sticks is that it's impossible to know in advance which hardware version you will get. And they all look identical from the outside.
I guess I must be lucky that everything on my V3.0 works with Debian.

from openstick.

from openstick.

I have a fresh 3.2 stick with stock firmware, what files do you guys need ?

from openstick.

Modem and WiFi firmwares are in the "modem" partition (vfat filesystem, can't recall what it's mounted as).
WiFi NVRAM file (needed for stable AP mode) is in the /persist partition.

from openstick.

I have a fresh 3.2 stick with stock firmware, what files do you guys need ?

You should be able to enable adb access on the latest firmware by opening http://192.168.100.1/usbdebug.html and waiting until it's rebooted.

Then follow above advice by @jongerenchaos:

1. Enable ADB
2. Backup WIFI firmware (adb pull persist) and copy them to the ddscentral image, step 2
3. Backup Modem files (adb pull firmware) and copy them to the ddscentral image, step 1

from openstick.

Modem firmware and wifi firmware for 3.2 stick

from openstick.

Alternate link for downloads without a browser (wget, curl, etc.)
Modem and WiFi firmware UZ801 v3.2

from openstick.

I also can create a full flash backup of 3.2 stick if anyone want it and 3.0 also, just found a solution how to do it

from openstick.

I also can create a full flash backup of 3.2 stick if anyone want it and 3.0 also, just found a solution how to do it

I have a 3.0 stick that I would like to back up before flashing.
Could you please just send some quick tips on how to create a full flash backup?
I would be extremely grateful for that. Thank you!

from openstick.

ok, i will make a small tutorial how to do this

it would be just great!

from openstick.

You need EDL mode to dump the eMMC.
https://wiki.postmarketos.org/wiki/File:Uz801_board.jpg

from openstick.

You need EDL mode to dump the eMMC. https://wiki.postmarketos.org/wiki/File:Uz801_board.jpg

alright, from what I understand I need to put the stick in EDL mode through a button on the board.
then I need to install EDL
do you guys have by chance a quick list of commands to correctly dump the eMMC?
thank you again

from openstick.

In short: All you need is to switch it to debug mode from webui , use miko service tool to switch stick to edl mode( Reboot to -> Adb reboot - > EDL(9008) ) then navigate to flash tab press on button labelled "Load partition structure" after that press " Read full image " ( do not forget to select folder where to store image)

from openstick.

In short: All you need is to switch it to debug mode from webui , use miko service tool to switch stick to edl mode( Reboot to -> Adb reboot - > EDL(9008) ) then navigate to flash tab press on button labelled "Load partition structure" after that press " Read full image " ( do not forget to select folder where to store image)

Thank you for your answer.
I have never heard about miko service tool, it looks like a windows program. I'm on linux, I guess I should set up a virtual machine and download a cracked version to run that. It would probably take too much time. I'll probably go ahead and flash the key with linux without dumping the emmc. Thanks again

from openstick.

yes it is windows but this is basically a nice gui for all console tools, i am a bit too lazy to discover all the right options for them so i went that way
i also saw linux live cd with edl preinstalled, if you absolutely want a backup i can provide you with mine, but for sure you will loose your modem original imei and wifi mac

from openstick.

it is possible that i've uploaded 3.0 instead of 3.2 firmware files, i messed up modem files, i have a full dump of firmware but for some reason it do not want to restore properly, so can't check files, if you want i can provide you with the full dump of 3.2 stick so you can tinker with it

from openstick.

So You have rootfs image of the stock firmware ? can it be mounted ?

from openstick.

Each partition saved in separate file, probably you can, but i am lazy to investigate them

from openstick.

ok, so if You upload them somwhere I could try to get firmware from it

from openstick.

hmm, It seems that after fixing mobian repository key and upgrading to bookworm usb ethernet is broken ... I reinstalled the stick and after sudo apt-get full-upgrade with bookworm source.list mobian-usb-gadget.service disapeared.

EDIT:
ater fixing mobian repo key install mobile-usb-networking - this reenables the usb etherent

EDIT2:
still adb is not functioning after update to bookworm :/

from openstick.

Each partition saved in separate file, probably you can, but i am lazy to investigate them

Yes, it's possible to mount partition dumps. Also, 7-zip may be able to read some file systems without mounting.

from openstick.

Ok i probably overwritten my 3.2 image. i have so many of them so i no longer know which dump is from 3.2 🤣 i can upload one that i think is from 3.2 but it can be 3.0 also

from openstick.

@Smit1237 Yes please :)
Currently UZ801_V3.2 using firmware from V3.0 has poor performance, constant connection drops (after few minutes) and 1/2MBps connection speed.

from openstick.

So I got another UZ801_V3,2 with stock firmware and pulled out firmware files from it. They are exactly the same as in V3.0 @ddscentral posted.

from openstick.

Sorry been busy lately, so i think you don't need firmware anymore?

from openstick.

LTE problem solved - there was no problem to begin with ... It was just a signal strength problem. when mmcli shows about 50% signal strength I get 1/2MBps, when I got outside buiding the signal strength went to 67% and the speed went to 18MBps ! :)
So I suppose the connection dropouts were also caused by the weak signal - but that I need to test more.

So to sum up, UZ801_V3.2 has the same firmware as V3.0 and WIFI and LTE works ok on debian bookworm.
Problems left:

• after upgrading to bookworm I lost the adb - need to figure out how to enable it again
• the stick goes silent after couple of hours/days. The red led is blinking, wifi hotspot is alive but I cannot connect to it, ethernet connection is down but the usb ethernet interface on the host exist (cannot get ip from dhcp). If I manage to enable adb I will try to connect with adb shell in that situation.

from openstick.

it is possible that i've uploaded 3.0 instead of 3.2 firmware files, i messed up modem files, i have a full dump of firmware but for some reason it do not want to restore properly, so can't check files, if you want i can provide you with the full dump of 3.2 stick so you can tinker with it

@Smit1237 would it be possible to get a full dump of the stock firmware for version 3.2? I was messing around with edl and managed to overwrite my backup so I have no way to recover my bricked UZ801 v3.2 stick.

I found a stock firmware here https://github.com/Mio-sha512/openstick-stuff/releases but it seems to be an older version and for Chinese base-band so I can't get the modem to work.

from openstick.

well i can't be sure that this is exactly 3.2 image, it can be also 3.0 image since i messed up naming , if you ok to try it i can upload

from openstick.

well i can't be sure that this is exactly 3.2 image, it can be also 3.0 image since i messed up naming , if you ok to try it i can upload

Happy to try it. Would great if you can upload it. I'll make sure to set the IMEI to the stick I have when trying it out.

from openstick.

OK, i managed to get proper 3.2 firmware since i received new device, it is 100% proper firmware, it contains two type of backups, single file and so called xml backup with separate partitions, after unpacked it requires 7.2 gigs of storage
here is the link

from openstick.

@Smit1237 Your partition dumps are bad. But the raw eMMC dump seems to be OK. I will examine it's contents and, in case they differ from what we already have, mirror the download so we do not have to rely on Google.

from openstick.

no idea why the miko tool produces partition dumps like this, but i ruined one stick with them, so yeah included both to be completely safe

from openstick.

I wrote a script to generate and flash boot.img right on the stick. gist

Kernel source from msm8916-mainline works fine for me, device tree is OK.

from openstick.

Kernel source from msm8916-mainline works fine for me, device tree is OK.

The mainline kernel don't need additional dtb config for GPIO and other stuffs?

from openstick.

Kernel source from msm8916-mainline works fine for me, device tree is OK.

The mainline kernel don't need additional dtb config for GPIO and other stuffs?

Actually I didn't use the real mainline kernel, but msm8916-mainline.
Haven't tried the real mainline, because the msm8916-mainline repo seems pretty up-to-date.

DTS can be found even in the real mainline kernel: https://github.com/torvalds/linux/blob/master/arch/arm64/boot/dts/qcom/msm8916-yiming-uz801v3.dts

Default config (make msm8916_defconfig) is fully functional, except adb and USB Ethernet, which will need USB gadget drivers.

from openstick.

@qnnnnez Good to know it works. Did you test 4G on msm8916 mainline ?

from openstick.

@qnnnnez Good to know it works. Did you test 4G on msm8916 mainline ?

Actually I don't know! I think I have damaged my modem when I tried to replace the eMCP chip. Now the modem doesn't work even in stock firmware as well as Debian 11 with OpenStick kernel.
Or maybe it's a firmware problem, I don't know. I got "Status | lock: sim-pin2" in mmcli output.

from openstick.

you probably lost imei , because i ruined 4 modems , and they all have same issue 😁

from openstick.

You should have dumped flash contents before swapping chips. That would likely allow you to restore the modem to a working state.

from openstick.

you probably lost imei , because i ruined 4 modems , and they all have same issue 😁

I am unable to get the modem working with multiple sticks (I do receive signal reception but always encounter a timeout when trying to connect). You can re-add the IMEI to the stick through the Qualcomm application. However, it seems that doing so actually renders the modem non-functional. Even if you use the original firmware, it still doesn't work. Does anyone have an idea what's going wrong there?

from openstick.

I got another stick labelled UFI103S_V03, and modem works as intended (but without roaming, don't know how to enable it).
It turns out that UZ801 variants are particularly hard to deal with.

from openstick.

IMEI is not included in a flash dump.
QCN could be backed up in stock Android firmware through a diag serial port. The diag port is named Qualcomm HS-USB MDM Diagnostics XXXX in Windows. I'm wondering how this port works.

from openstick.

Can anyone please share a stock EDL dump for UZ801_v3.0 (board like the one on photo).
My stock image is lost and SIM is constantly in "power state: off", no matter what I try.

from openstick.

I have both versions uz801_v3.0 and uz801_v3.2, I flashed them with Openwrt, they are actually both working good except for the WiFi speed which I noticed is slower than stock ROM, both sticks are identical and can run the same firmware just make sure to dump the modem.bin and restore later to /lib/firmware.
I noticed that v3.0 has an esim hardware unlike v3.2.
I heard getting esim to work under openwrt is a pain so I am going to restore the original android ROM of the stick and try to get it to work.

from openstick.

WiFi speed which I noticed is slower than stock ROM

Maybe it's because openwrt is using open source drivers instead of the proprietary ones in Android. The driver issues also exists in many android phones and routers when community try to port Linux/AOSP to them..

from openstick.

Can anyone please share a stock EDL dump for UZ801_v3.0 (board like the one on photo). My stock image is lost and SIM is constantly in "power state: off", no matter what I try.

I have a firmware dump with a board the same as you

from openstick.

Hi, I entered in adb mode by clicking /usbdebug.html just for curiosity but never planed to hack my UZ801 v3.0 device, and I didn't tried it.
Now the Wifi/4G leds work but no wifi network is created and the USB isn't recognized in my computer as a tethering device.

How can revert to functional state with stock rom as before ?

Thanks in advance

from openstick.

Hi, I entered in adb mode by clicking /usbdebug.html just for curiosity but never planed to hack my UZ801 v3.0 device, and I didn't tried it. Now the Wifi/4G leds work but no wifi network is created and the USB isn't recognized in my computer as a tethering device.

How can revert to functional state with stock rom as before ?

Thanks in advance

As far as I know usbdebug.html is a temporary thing, and to get everything back you just need to reboot the modem by turning off the power from it, I can also say for sure that when usbdebug is turned on, the modem functionality continues to work and what you described clearly should not happen, unless you removed the system from emmc via fastboot or edl
If this is really the case, then all you have to do is use fastboot or edl to restore the modem

from openstick.

I still have a stock unmodified UZ801 V3.0 stick. I will try to find some time to grab a full dump if anyone needs it.

from openstick.

Recoverable?

from openstick.

I have both versions uz801_v3.0 and uz801_v3.2, I flashed them with Openwrt, they are actually both working good except for the WiFi speed which I noticed is slower than stock ROM, both sticks are identical and can run the same firmware just make sure to dump the modem.bin and restore later to /lib/firmware. I noticed that v3.0 has an esim hardware unlike v3.2. I heard getting esim to work under openwrt is a pain so I am going to restore the original android ROM of the stick and try to get it to work.

what version did you flash @cashin79 ?

from openstick.

what version did you flash @cashin79 ?

Immortalwrt

from openstick.

Sorry for being off-topic, but my modem’s wifi died, and I want to find something more reliable, can you please tell me where I can find lists of devices on which I can install aka mobian (the main thing is not openwrt, I’m tired of it, maybe something like debian) and use them As a portable 4G router, having a battery and working without a week of setup will be a plus. Thank you.

from openstick.