Installation issue with UBports-installer with Z4-Tab
-
@guf please read my statement carefully it is an endless loop in which the device is stuck. So I can no longer install anything, etc.
I am afraid my tablet is only scrap metal now! -
@z4tab
Hi,
Did you only turn off the tablet with your method or did you also reset it, for example with the following Procdedur.
Try a total reboot by pressing and holding the power button until the device vibrates 3 times in quick succession.
The device should always have enough 'juice' in the battery. -
@mario-ch said in Installation issue with UBports-installer with Z4-Tab:
@z4tab
Hi,
Did you only turn off the tablet with your method or did you also reset it, for example with the following Procdedur.
Try a total reboot by pressing and holding the power button until the device vibrates 3 times in quick succession.
The device should always have enough 'juice' in the battery.Considering the fact that the device has a old Qualcomm SoC according to it's devices page : https://devices.ubuntu-touch.io/device/karin/
It got me thinking of the same thing : Try all the tricks that go with that generation of SoC's
- Pressing the Power button for a long time and waiting for EDL Mode to be entered.
- In the worst case you can use a spare USB Cable and then shorten the right wires together to get to EDL Mode : https://www.getdroidtips.com/5-methods-to-enter-edl-mode-on-any-xiaomi-smartphones-qualcomm/
Also see : https://duckduckgo.com/?t=ffab&q=qualcomm+edl+mode&iax=images&ia=images
For pictures of the cables you can buy so you don't have to build them yourself!
TL;DR : Bootloops are OK! That means you can safe your device!
-
@Mario-CH:
The only way to turn off is press "PWR"+"Vol-". Then the tab vibrates 3 times and is really off. But only pressing "PWR", also for a long time - nothing is happen!@nero355:
EDL-mode sounds good. May be this is the only way to activate the tablet again. But I can't find any way to set the tablet in EDL-mode. Also with edl-cable (short D+ with GND) is not working! -
This weekend I was able to successfully flash the tablet with Android again. I'm very glad it's not junk after all.
Meanwhile, is there anyone who has successfully flashed Ubuntu touch on this device? Please report!
-
I too have the Karin device and experienced the exact same err using the installer as @z4Tab--> e:failed to mount /cache (Invalid argument) etc.. Right now, device has nothing but TWRP on it and I can't seem to get any UBTouch installed. I started the install with stock Android 7.1 installed. Got some message that I may need Android 8 installed but ignored that. Saw lots of files in @Guf post, but don't know how to use them. Is there a step-by-step install doc that explains how? I tried to flash system5.img and got a TWRP err like "Size of image is larger than target device." So, I'm not sure how to proceed, any help is appreciated.
-
@yvoiera said in Installation issue with UBports-installer with Z4-Tab:
Got some message that I may need Android 8 installed but ignored that.
So, I'm not sure how to proceed, any help is appreciated.
Maybe start by installing the rom installer tells you ?
-
@keneda Thanks much! I'm a beginner, have just flashed phones with pre-built ROMs.
Unsure about Android 8 (A8), because there's no "stock" A8 for Karin, I understood https://forum.xda-developers.com/t/no-android-8-oreo-for-our-z4-tablets.3679395/.
Also, installer page implied Halium 7.1 needed Android 7.1 (already there) to match the Halium version. ¹ Devices generally require a specific version of Android/stock rom to be installed. This depends on the halium version the port is build on. For example, if the port is based on halium 9, make sure you have Android version 9 installed before running the installer.
How do I build stock Android 8 for this device?
-
@keneda I assumed Lineage 15.1 would suffice for Android 8, so was able to flash with that. Re-ran install with installer version 0.9.7 (Snap on Ubuntu box). It recognized the device and did install then at end, got the "ADB is Scanning for Devices" - walked away a few mins and it now is just in a bootloop, flashing this message "E:failed to mount /cache (Invalid argument), E:Can't mount /cache/recovery/last_locale". Any ideas on why, or what to do to solve this? Thanks!
-
I had the same issue on my SGP771 device no matter which version of UBports Installer I have tried and which settings I have chosen. After not being able to find any clue I have installed Ubuntu 22.04 on my old desktop and went through these steps to install UT without the installer:
- Flashed my device with Android 7 using Flashtool.
- Downloaded system.img, halium-boot.img (old) and TWRP-3.1.1-lineageos-karin-20170520.img using links from Guf's porting page.
- Installed custom recovery TWRP-3.1.1-lineageos-karin-20170520.img on the device using these instructions.
- Installed system.img and rootfs with halium-install + flashed halium-boot.img as described here.
- I ran those two blocks of code on Guf's porting page in TWRP command line (under “Important note for UT rootfs to work”).
I am a newbie in this area and not sure if that is all correct but UT is running, except for the camera and bluetooth, I didn’t figure out yet how to enable them.
