Database Info

[RECOVERY] [UNOFFICIAL] [Phobos] TWRP 3.0.0-0 for the HP Slate 21

TWRP for the HP Slate 21 (phobos)
Code:
*
* Your warranty is now void.
*
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this recovery
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you.
* A lot.
*
TeamWin Recovery project (or TWRP for short) ported for the HP Slate 21 (s100 & k100).
Here are some images:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Download
https://www.androidfilehost.com/?fid=24399994186369430
Install/Flashing Instructions:
1. You will need the following things in order to install TWRP on the Slate 21: 1 USB male to USB male connector, a computer with ADB and fastboot installed, common sense.
2. Turn off device and boot into fastboot mode (Volume Down + Power)
3. Connect your device to your computer by plugging one end of the USB cord into the lone USB port on the left-hand side of the device and the other end on any USB port on your computer.
4. Run the command “fastboot oem unlock” (no quotes)
5. Select yes on your Slate 21, after this step you will lose all your data. Vol Up to move Up, Vol Down to move Down, Brightness Up to select.
6. After fastboot has been unlocked, you’ll need to flash TWRP to your recovery. Do do this run the following command:
fastboot flash recovery /path/to/downloaded/TWRP.img
Replace /path/to/downloaded/TWRP.img with where you downloaded TWRP provided by me (Quaesar). You can drag and drop the IMG into Terminal/CMD to do this easily.
7. Use the buttons on the side of the device to select “Recovery”
8. Profit! You now have the latest TWRP on your device!
Cyanogenmod 12.1:
http://forum.xda-developers.com/general/general/rom-cyanogenmod-12-1-hp-slate-21-t3201416
Donations:
You can donate to me for my hard work through PayPal. My donation email is [email protected]. Any and all donations are welcome regardless of amount. Thanks for supporting me!
Direct link: https://www.paypal.me/Quaesar
Credits
Building this was a collaborative effort. The following developers/beta testers helped me provide you with this:
Quaesar (me): Main person, started project, etc etc.
UnjustifiedDev: Device tree, initial setup
SLATE21&MOTOG: Beta testing
Vocoderism: Beta testing
JonasFi: Beta testing
Seanichigo: k100 testing
If you have any comments or questions, reply to this thread and I'll get to you whenever I can
PLEASE HIT THAT THANKS BUTTON!!! IT REALLY SHOWS YOU APPRECIATE MY WORK!!!!!
Peace,
Quaesar

Changelog:
Public Release 1:
- First public release of recovery. Nothing major to see here
Known Issues/Bugs:
- CPU temperature will show up as 0 sometimes (it's usually 40-50*C if you're wondering)

FAQs:
Q: Bruhhhh, hook me up with dem sources
A: Dem sources can be found at teh GitHubs: (Link)
Q: Should I backup my stuff?
A: Do I need to answer that?
Q: What is this fastboot your speak of and how can I get it?
A: This video explains everything nicely: https://www.youtube.com/watch?v=maLWScgXflk
Q: On a scale of one to ten, how cool are you?
A: 11

Version 3 works very well. I also resolves an issue with using the swipe control from the previous version. Thanks Q!

device not found

Desparragosa said:
device not found
Click to expand...
Click to collapse
Check your connection (wire, computer, Slate). Make sure you have the correct fastboot drivers installed. I've seen an issue with the Windows 10 where Windows doesn't want to recognize or flash to the device. If you're comfortable, you may want to try using Ubuntu (I use 14.04). If you want, you can always contact me over Hangouts at [email protected]
Peace,
Quaesar

Quaesar said:
Check your connection (wire, computer, Slate). Make sure you have the correct fastboot drivers installed. I've seen an issue with the Windows 10 where Windows doesn't want to recognize or flash to the device. If you're comfortable, you may want to try using Ubuntu (I use 14.04). If you want, you can always contact me over Hangouts at [email protected]
Peace,
Quaesar
Click to expand...
Click to collapse
Hi. I can't do the unlock. Started with windows 10, and now with windows 8. Get the same message FAILED (command write failed (Unknown error))
don't know what else to try. Can you provide the fastboot drivers you used?
EDIT: Found the problem. Had to disable MTP!

rgomesf said:
Hi. I can't do the unlock. Started with windows 10, and now with windows 8. Get the same message FAILED (command write failed (Unknown error))
don't know what else to try. Can you provide the fastboot drivers you used?
EDIT: Found the problem. Had to disable MTP!
Click to expand...
Click to collapse
Nice! I use Ubuntu anyway so I would know about drivers haha

Hi there
Is there any other way of installing TWRP onto the HP Slate s/k100 21 without using a male to female usb connector?
Like rooting the Slate then flashing using something like the app Flashify? Booting off the SD card?
Thanks in advance

Hey there! I tried to install your recovery on my HP Slate 21, but although the fastboot output looks good to me:
seems I have already unlocked previously:
Code:
$ sudo fastboot oem unlock
...
(bootloader) Bootloader is already unlocked.
OKAY [ 0.025s]
finished. total time: 0.025s
And flashing the recovery also seems like it works fine:
Code:
$ sudo fastboot flash recovery TWRP_3.0.0-0_phobos_Quaesar.img
target reported max download size of 641728512 bytes
sending 'recovery' (9256 KB)...
OKAY [ 0.329s]
writing 'recovery'...
OKAY [ 0.562s]
finished. total time: 0.892s
But when I boot into recovery afterwards I get not TWRP but a stock recovery that will not flash your cyanogenmod because it cannot verify it.

Apad121 said:
Hi there
Is there any other way of installing TWRP onto the HP Slate s/k100 21 without using a male to female usb connector?
Like rooting the Slate then flashing using something like the app Flashify? Booting off the SD card?
Thanks in advance
Click to expand...
Click to collapse
If you can get root then yeah it's good. However finding a way to root without a wire to connect to the computer is kinda hard. My suggestion is to skip that and just twist two male usb cables together
@kaefert, try locking and unclocking the bootloader. If that doesn't work wipe the recovery partition then flash it

Quaesar said:
If you can get root then yeah it's good. However finding a way to root without a wire to connect to the computer is kinda hard. My suggestion is to skip that and just twist two male usb cables together
@kaefert, try locking and unclocking the bootloader. If that doesn't work wipe the recovery partition then flash it
Click to expand...
Click to collapse
Thanks but I have already bought the cable and flagged TWRP on. I have also tried out your cm ROM.

I could use some advice. I enabled the USB developer option, when the cable is connected to my booted HP slate the ADB command window on my laptop works. I was able to send command adb reboot bootloader to reboot the Slate into the bootloader but once I get there, the cable disconnects from the Slate so I can't do the fastbook unlock command. Any tips ?

when I run the fastboot flash recovery /path/to/downloaded/TWRP.img command
error appears: can not open '/path/to/downloaded/TWRP.img'

im having issues installing TWRP on Slate21
hi, its been a while since I touched anything android, so its probably no surprise im having problems here! lol, anyhow, ive got a Slate 21 stuck on the 'HP Slate Android' boot screen and wanted to reflash it, so I follow the instructions here, and I get as far as the point where you flash TWRP and I get a problem and it doesn't flash?
this is what it says when I try>>>>>
Target reported Max download size of 641728512 bytes
error: cannot load 'c:\TWRP.img' : No error
obviously ive placed the TWRP.img on the root drive, am I doing something wrong here? have I got the wrong ADB driver? any help will be greatly appreciated. thanks Dee

HP Slate 21-s100
Turn off device and boot into fastboot mode - OK
Connect your device to your computer by plugging USB male to USB male connector - OK
Run the command “fastboot oem unlock” - OK
fastboot oem unlock
(bootloader) Showing Options on Display.
(bootloader) Use device keys for selection.
(bootloader) erasing userdata...
(bootloader) erasing userdata done
(bootloader) erasing cache...
(bootloader) erasing cache done
(bootloader) unlocking...
(bootloader) Bootloader is unlocked now.
OKAY [ 19.503s]
Finished. Total time: 19.504s
fastboot flash recovery /path/to/downloaded/TWRP.img - OK
Use the buttons on the side of the device to select “Recovery” - OK
Profit! You now have the latest TWRP on your device! - NOPE! :crying: I see the original hp Android System Recovery :crying: WHY?
I was worng, Where am I doing wrong?

I did it the way you say here.
then i wanted to change the software.
i got this error.
I did something wrong.
I am installing twrp but it won't open.
Pressing volume + volume - power keys comes here.
I would be glad if you could help.
Thanks

[ROM] Unofficial LineageOS 14.1 [NJH47F] for ZTE Blade S6 (P839F30)

Code:
[I]DISCLAIMER[/I]
All information and files — both in source and compiled form — are provided on an as is basis. No guarantees or warranties are given or implied. The user assumes all risks of any damages that may occur, including but not limited to loss of data, damages to hardware, or loss of business profits. Please use at your own risk. Note that unless explicitly allowed by the warranty covering your device, it should be assumed that any warranty accompanying your device will be voided if you tamper with either the system software or the hardware.
Introduction
This is my unofficial build of LineageOS 14.1 for the ZTE Blade S6 aka P839f30.
This is a beta release, so just some basic functions will be given.
I have tested this version with my AS variant device. Other variants have to be tested.
Click to expand...
Click to collapse
Features
working:
ril: calls, sms, data.
wifi: good.
sensors
gps
sound: clear and loud.
camera: rear and front.
torch
headphone detection
flash is working in new test builds.
not working:
We have to test to find more.
Click to expand...
Click to collapse
Installation instructions
It is best to have installed the latest stock rom beforehand, so modem and all other vendor stuff is up to date.
If you like you can use this mod to have a unified data partition, please proceed with caution.
You will need TWRP or any other custom recovery.
Reboot into recovery and do a nand backup.
Do a factory format.
Download Rom and put it on your phone or use adb sideload.
Install the rom and then clear cache and dalvik cache.
optional: install su and/or gapps.
optional: install your favourite kernel tool and set the cpu governor to interactive for example - do not use performance it will drain your battery, while you are using your device - not for the new test builds.
Click to expand...
Click to collapse
Changelog:
11.10.2018 - test build:
update los sources, security patch level 05.09.
04.03.2018:
make flashlight work.
integrate headphone detection.
update los sources, security patch level 05.02.
14.06.2018 - test build:
flashlight works also in stock camera.
governor are set by the system, no need to set them.
cores are managed by the system, shuting down and launching them one by one. This should save energy.
back and menu button can be toggled in the settings -> additional buttons.
Using stock venus files, video recording is working also hd playback should be fine.
Update sensor hub firmware to version 2.8.
update los sources, security patch level 05.06.
13.02.2018:
rebasing lots of things like kernel and device tree and using different vendor blobs.
Thus wifi signal is great and the microphone is better.
update los sources, security patch level 05.01.
22.11.2017:
reboot to recovery, download mode and power off should work fine now.
update los sources, security patch level 06.11.
19.10.2017:
device reboot fixed, no reboot if the device attempts to suspend.
wifi signal strength is better now.
5GHz wifi support is activated - to be tested.
remove nfc things.
Click to expand...
Click to collapse
Downloads
test build - 11.10.2018:
Google Drive
beta version - 04.03.2018:
Google Drive
If you want root use the lineage addon package found here - download arm version.
Install it after flashing the rom or download your favourite root package and install it.
Sources
device
vendor
kernel
Click to expand...
Click to collapse
FAQ
Here you will find some answers to common question which could arise.
Q: How to give root access to an app or adb?
A: First install the su extra package from Lineage OS or any other su tool you like. Then go into settings and about device, click there multiple times on the build number until you unlocked the developer options. Go to developer options and look for root access.
Q: I thing I found an issue, what to do now?
A: Do a logcat or grab a dmesg while having the issue, otherwise we can't say what is happening. Report as much info as possible. Quote your stock rom your device shipped with or which device variant you possess.
Click to expand...
Click to collapse
XDA:DevDB Information
Unofficial LineageOS 14.1 [NJH47F] P839F30, ROM for all devices (see above for details)
Contributors
lightwars
ROM OS Version: 7.x Nougat
ROM Kernel: Linux 3.10.x
Based On: LineageOS 14.1
Version Information
Status: Beta
Current Beta Version: NJH47F
Beta Release Date: 2018-10-11
Created 2017-09-21
Last Updated 2018-10-11

Awesome, lightwars. Thank you for this Rom and the work you put into it.
I installed it on my EU Blade S6 and can confirm your points on working / non-working.
A couple additional points I discovered so far:
- phone reboots regulary after a couple of minutes (I did a couple of tests cycles with phone going to standby after 1 m inute and switching the phone "off"):
- reboots after 1.5, 2 and 3 minutes with phone going to standby after 1 minute
- reboots after 8.5 and 9 minutes if phone is switched off (standby)
- not able to turn phone off, shutdown and reboot both trigger reboot (with shutdown phone seems to stay "off" a little bit longer than with reboot)
- Wifi has weak signal, but works.
- Wifi only available for 2.4 Ghz, I haven't used the phone for a while, but believe it Supports 5 Ghz as well. Maybe that is connected to the weak 2.4 Ghz signal as well.
- could not get any GPS lock, even location using WLAN and mobile broadcast did not work.
- Screen Mirroring not working, I believe connected to the Wifi issues as well.
- NFC is shown in Settings, but not possible to activate (does the S6 even has NFC?)
Apart from that everything it working great. The phone feels way faster than in stock Rom, videos play smoothly in 720p, 3d performance seemed ok (only tried Google earth, that was way better than in stock rom).
Only issue preventing me from using the phone are the reboots.
Again thank you very much for your great work. Please let me know, if I can help with anything.

xris99 said:
I installed it on my EU Blade S6 and can confirm your points on working / non-working.
A couple additional points I discovered so far:
- phone reboots regulary after a couple of minutes (I did a couple of tests cycles with phone going to standby after 1 m inute and switching the phone "off"):
- reboots after 1.5, 2 and 3 minutes with phone going to standby after 1 minute
- reboots after 8.5 and 9 minutes if phone is switched off (standby)
- not able to turn phone off, shutdown and reboot both trigger reboot (with shutdown phone seems to stay "off" a little bit longer than with reboot)
- Wifi has weak signal, but works.
- Wifi only available for 2.4 Ghz, I haven't used the phone for a while, but believe it Supports 5 Ghz as well. Maybe that is connected to the weak 2.4 Ghz signal as well.
- could not get any GPS lock, even location using WLAN and mobile broadcast did not work.
- Screen Mirroring not working, I believe connected to the Wifi issues as well.
- NFC is shown in Settings, but not possible to activate (does the S6 even has NFC?)
Click to expand...
Click to collapse
It's good to hear, that this rom also work for the EU variant. Before,we have used different kernels...
Sadly I had discovered the reboots also. Thanks for doing some more testing.:good:
Will get some logs to see,if we could do something easily about it. Thought that it coul be related to just some kernel config mismatches, but it don't have to...
NFC is just left over from the starting point... It will be removed, but a little bit curious, that some variants have NFC support activated in the kernel config...

Out of curiousity, have you checked the GPS.conf? I've always had trouble with GPS on this phone but have got it mostly working after lots of fiddling, so I could post if that would be helpful.
xris99 said:
Awesome, lightwars. Thank you for this Rom and the work you put into it.
I installed it on my EU Blade S6 and can confirm your points on working / non-working.
A couple additional points I discovered so far:
- phone reboots regulary after a couple of minutes (I did a couple of tests cycles with phone going to standby after 1 m inute and switching the phone "off"):
- reboots after 1.5, 2 and 3 minutes with phone going to standby after 1 minute
- reboots after 8.5 and 9 minutes if phone is switched off (standby)
- not able to turn phone off, shutdown and reboot both trigger reboot (with shutdown phone seems to stay "off" a little bit longer than with reboot)
- Wifi has weak signal, but works.
- Wifi only available for 2.4 Ghz, I haven't used the phone for a while, but believe it Supports 5 Ghz as well. Maybe that is connected to the weak 2.4 Ghz signal as well.
- could not get any GPS lock, even location using WLAN and mobile broadcast did not work.
- Screen Mirroring not working, I believe connected to the Wifi issues as well.
- NFC is shown in Settings, but not possible to activate (does the S6 even has NFC?)
Apart from that everything it working great. The phone feels way faster than in stock Rom, videos play smoothly in 720p, 3d performance seemed ok (only tried Google earth, that was way better than in stock rom).
Only issue preventing me from using the phone are the reboots.
Again thank you very much for your great work. Please let me know, if I can help with anything.
Click to expand...
Click to collapse

Willing you on for success with this.
I have an EU model which I'd like to install this on once it's functional enough (my regular daily phone).
I also have an old AS model that I may be able to revive for testing purposes (backlight failing intermittently after I dropped it, possibly a loose connection).

Thank you for trying lightwars. You are the only one who work for zte blade s6. I hope you build a stable version soon.

; Wow, many thanks @lightwars !!!
Hopefully soon you'll be have a stable on, that's my hope from ID version...
Regards,
Killermonk

Ok guys i want to install this rom but i cant. I cant find a tutorial here how to root the device. I try to install the recovery [RECOVERY][p839f30 / ZTE Blade S6] UNOFFICIAL TWRP [3.1.0-0] first but i failed too. There is a full guide how to do this? And if I install this there is a way back to the stock rom. Thanks.

@lagos911, rooting is easy. Just use Mobilego like in this video https://www.youtube.com/watch?v=dPDbAdm7B1c
Installing recovery isn't hard either. http://konstakang.com/devices/blades6/TWRP/
It is possible that the adress of the sdcard is different. (For example: sdcard0 in stead of sdcard), use the correct adress.

i install the rom at my phone (eu version) I get black screen after the install for 3 minites and then the device is shuting down.
What I do wrong? I wipe the device and I install the rom from my external sdcard.

lagos911 said:
i install the rom at my phone (eu version) I get black screen after the install for 3 minites and then the device is shuting down.
What I do wrong? I wipe the device and I install the rom from my external sdcard.
Click to expand...
Click to collapse
After installing the rom and you push reboot system, if the black screen (download mode probably) appears, hold the power button until the phone vibrates and reboots.
Now the ZTE splash screen should come up and the phone should boot hopefully.

lightwars said:
After installing the rom and you push reboot system, if the black screen (download mode probably) appears, hold the power button until the phone vibrates and reboots.
Now the ZTE splash screen should come up and the phone should boot hopefully.
Click to expand...
Click to collapse
Yes I do that some times from the second time and after because i didnt want to wait. But black screen continues to appear.
I rewipe (all king of wipes) and reinstall the rom 5 times but nothing happend.
I install the old rom because i was needed the phone. Phone start to loop reboot when I found out the bootfix and now its OK.
Maybe I try lineageOS 14.1 again at the weekend.

So I try to install the rom yesterday. I keep get the black screen after the I reboot the phone. This time I install the fix boot EU from the cyanogen rom. I reboot the phone and I saw the animation boot logo. I think I did it but the animation never go away. I let the phone for 30 minites but i never saw the menu of the new android.

lagos911 said:
So I try to install the rom yesterday. I keep get the black screen after the I reboot the phone. This time I install the fix boot EU from the cyanogen rom. I reboot the phone and I saw the animation boot logo. I think I did it but the animation never go away. I let the phone for 30 minites but i never saw the menu of the new android.
Click to expand...
Click to collapse
Ok, so we've got some problems with EU devices... maybe there are more variants, I'm think of EU, DE, UK, ES, PT and who knows... Could be small differences have an impact here...
To say it clearly to install the boot EU fix from the CM-12.1 thread has installed an other boot image for your phone which have kernel which will not work with nougat.
But anyway I believe I know why the device reboots itself, cause it can't suspend itself in the right manner. Let me show you a kernel log, how it should be:
Code:
<6>[ 189.766084] PM: suspend entry 2017-10-13 04:49:15.725432575 UTC
<6>[ 189.767479] mmc1: Starting deferred resume
<6>[ 189.767983] mmc0: Starting deferred resume
<6>[ 189.861591] mmc0: Deferred resume completed
<6>[ 189.907006] mmc1: Deferred resume completed
<6>[ 189.766118] PM: Syncing filesystems ... done.
<3>[ 189.999154] Error: returning -512 value
<6>[ 189.998043] Freezing user space processes ... (elapsed 0.008 seconds) done.
<6>[ 190.006568] Freezing remaining freezable tasks ... (elapsed 0.005 seconds) done.
<6>[ 190.011790] Suspending console(s) (use no_console_suspend to debug)
<6>[ 190.018262] [AK4375] ak4375_suspend(1402)
<6>[ 190.025845] [TP:CORE]Enter fb_notifier_callback.
<6>[ 190.025845]
<6>[ 190.025892] [TP:CORE]Enter fb_notifier_callback.
<6>[ 190.025892]
<7>[ 190.034218] --CWMCU--CWMCU_suspend
<6>[ 190.046580] PM: suspend of devices complete after 33.038 msecs
<6>[ 190.048343] PM: late suspend of devices complete after 1.737 msecs
<6>[ 190.053764] PM: noirq suspend of devices complete after 5.409 msecs
<6>[ 190.053774] Disabling non-boot CPUs ...
<6>[ 190.081114] CPU0:msm_cpu_pm_enter_sleep mode:3 during suspend
...
<6>[ 400.663545] Enabling non-boot CPUs ...
<6>[ 400.664692] CPU1 is up
<6>[ 400.665735] CPU2 is up
<6>[ 400.666779] CPU3 is up
<6>[ 400.668230] CPU4 is up
<6>[ 400.669120] CPU5 is up
<6>[ 400.670027] CPU6 is up
<6>[ 400.670974] CPU7 is up
<6>[ 400.671561] PM: noirq resume of devices complete after 0.570 msecs
<6>[ 400.672983] PM: early resume of devices complete after 0.796 msecs
<7>[ 400.679137] --CWMCU--CWMCU_resume
<6>[ 400.689515] PM: resume of devices complete after 16.510 msecs
<6>[ 400.690769] runin_work:BatteryTestStatus_enable = 0 chip->usb_present = 0
<6>[ 400.690573] Restarting tasks ... done.
<6>[ 400.696613] PM: suspend exit 2017-10-13 05:59:11.279104088 UTC
But at the moment the device hangs up while trying to freeze the user space processes and fails.
I found that there is a problem with the device tree image of the kernel, so using the stock one everything is well.
I will make changes and a new version will appear soon.
In the meantime please try out flashing this bootimages after installing LOS-14.1:
Boot - LOS-14.1 standard image(AS)
Boot EU -LOS-14.1
Hopefully one of these works and the reboot issue shouldn't happen also.

lightwars said:
Ok, so we've got some problems with EU devices... maybe there are more variants, I'm think of EU, DE, UK, ES, PT and who knows... Could be small differences have an impact here...
To say it clearly to install the boot EU fix from the CM-12.1 thread has installed an other boot image for your phone which have kernel which will not work with nougat.
But anyway I believe I know why the device reboots itself, cause it can't suspend itself in the right manner. Let me show you a kernel log, how it should be:
Code:
<6>[ 189.766084] PM: suspend entry 2017-10-13 04:49:15.725432575 UTC
<6>[ 189.767479] mmc1: Starting deferred resume
<6>[ 189.767983] mmc0: Starting deferred resume
<6>[ 189.861591] mmc0: Deferred resume completed
<6>[ 189.907006] mmc1: Deferred resume completed
<6>[ 189.766118] PM: Syncing filesystems ... done.
<3>[ 189.999154] Error: returning -512 value
<6>[ 189.998043] Freezing user space processes ... (elapsed 0.008 seconds) done.
<6>[ 190.006568] Freezing remaining freezable tasks ... (elapsed 0.005 seconds) done.
<6>[ 190.011790] Suspending console(s) (use no_console_suspend to debug)
<6>[ 190.018262] [AK4375] ak4375_suspend(1402)
<6>[ 190.025845] [TP:CORE]Enter fb_notifier_callback.
<6>[ 190.025845]
<6>[ 190.025892] [TP:CORE]Enter fb_notifier_callback.
<6>[ 190.025892]
<7>[ 190.034218] --CWMCU--CWMCU_suspend
<6>[ 190.046580] PM: suspend of devices complete after 33.038 msecs
<6>[ 190.048343] PM: late suspend of devices complete after 1.737 msecs
<6>[ 190.053764] PM: noirq suspend of devices complete after 5.409 msecs
<6>[ 190.053774] Disabling non-boot CPUs ...
<6>[ 190.081114] CPU0:msm_cpu_pm_enter_sleep mode:3 during suspend
...
<6>[ 400.663545] Enabling non-boot CPUs ...
<6>[ 400.664692] CPU1 is up
<6>[ 400.665735] CPU2 is up
<6>[ 400.666779] CPU3 is up
<6>[ 400.668230] CPU4 is up
<6>[ 400.669120] CPU5 is up
<6>[ 400.670027] CPU6 is up
<6>[ 400.670974] CPU7 is up
<6>[ 400.671561] PM: noirq resume of devices complete after 0.570 msecs
<6>[ 400.672983] PM: early resume of devices complete after 0.796 msecs
<7>[ 400.679137] --CWMCU--CWMCU_resume
<6>[ 400.689515] PM: resume of devices complete after 16.510 msecs
<6>[ 400.690769] runin_work:BatteryTestStatus_enable = 0 chip->usb_present = 0
<6>[ 400.690573] Restarting tasks ... done.
<6>[ 400.696613] PM: suspend exit 2017-10-13 05:59:11.279104088 UTC
But at the moment the device hangs up while trying to freeze the user space processes and fails.
I found that there is a problem with the device tree image of the kernel, so using the stock one everything is well.
I will make changes and a new version will appear soon.
In the meantime please try out flashing this bootimages after installing LOS-14.1:
Boot - LOS-14.1 standard image(AS)
Boot EU -LOS-14.1
Hopefully one of these works and the reboot issue shouldn't happen also.
Click to expand...
Click to collapse
I try to install the boot but file is corrupted

lagos911 said:
I try to install the boot but file is corrupted
Click to expand...
Click to collapse
I downloaded both files and they install just fine.
You have to switch from ZIP installing to image installing at the install dialog from twrp the button at the bottom right.

lightwars said:
I downloaded both files and they install just fine.
You have to switch from ZIP installing to image installing at the install dialog from twrp the button at the bottom right.
Click to expand...
Click to collapse
Yea i didnt know that with the image flashing. Thanks.
Actually I did it and I install the rom with your boot EU fix. No big diffrents at the interface from the 12.1 cm.
I dont working a lot with lineageOS but many thinks dont work. I enable wifi and disable automatic. Flashlight and some other thinks.
I hope you build a stable rom.
P.S. Now i have install the CM12.1 and when I try to enter the bootloader the device stuck.
Also I try to delete some system apps with ES explorer PRO and I get that my device its not rooted.
I have done something wrong with the rooting?

lagos911 said:
P.S. Now i have install the CM12.1 and when I try to enter the bootloader the device stuck.
Also I try to delete some system apps with ES explorer PRO and I get that my device its not rooted.
I have done something wrong with the rooting?
Click to expand...
Click to collapse
I am not sure I can follow your description... What means stuck? bootloader displays just a black screen.
Normally you can activate root in the developer settings, which are displayed after clicking serveral times on the build number. There you will find an option to enable/disable root for apps and adb.
Or if you prefer other tools like supersu install it first, then try again.
Remember to ask question for CM12.1 inside the appropriate thread.

Sorry for the wrong topic. I didint know that the bootloader appearing a black screen. Usually they have a menu.
I forgot to mention that the option for root explorer at ES explorer PRO you can activated from here.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

Please help :/
I've installed this onto my zte blade s6 but my internet doesn't turn on on the phone and I flashed the eu fix by lightwars on my recovery so now i don't have a recovery and my phone isn't rooted. PLEASE HELP.

SailfishOS 3 for Photon Q and siblings

Code:
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it!
SailfishOS 3 for Photon Q
Continuation from 2.0 thread to keep most important information in first post. Thanks to vevgeniev for initial port, without it I would never buy Photon Q.
Repo with my apps is added to image. Packages can by installed via terminal:
Code:
devel-su zypper in "package name"
Images
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Click to expand...
Click to collapse
Installation
Download and flash cm-11-20150626-SNAPSHOT-XNG3CAO1L8-moto_msm8960_jbbl.zip via twrp-3.0.2-0-asanti_c.img according to ordinary cm instruction. Use ext4 filesystem for /data partition. Boot to android and make sure everything works.
Download SailfishOS 4 image (open browser in private mode if onedrive ask you to login) and flash it over cyanogenmod. It's compressed tarball so installation may take even 10 minutes.
OTA
Read about Stop Releases and make backup using TWRP
Code:
/usr/share/sfos-moto_msm8960_jbbl-adaptation/upgrade.sh
# after reboot execute pkcon refresh to update all repositories
For any issues with upgrade.sh script download more up-to-date version, add --verbose argument or execute commands from real-upgrade.sh manually: https://build.sailfishos.org/packag...bl:4.4.0.68/sfos-moto_msm8960_jbbl-adaptation
At first boot tracker might slow down phone and eat a lot of storage. If it's too resource hungry move your media files out of device or create .nomedia empty file to exclude particular directory from tracker. Then force reset it:
Code:
tracker reset --hard
Custom Bootlogo
vevgeniev created a custom bootlogo:
Instruction how to use it
Known issues
Half screen mirror glitch occurs sometimes. Blank/unblank display fixes it
Sometimes removing files does not have any effect, i.e. free space doesn't increase and sdcard can't be unmounted. Could be easily triggered by mtp or dd usage. For sdcard access use FileZilla (SFTP).
QProcess:startDetached can hang randomly. Workaround added to fingerterm. Looks like it's bug in Qt and it is not photon q specific: https://together.jolla.com/question/202337/bug-fingerterm-terminal-freezes-after-opening-new-window
There are no 2.XG, 3.XG network indicators.
glReadPixels() return empty content in some cases. This means no screen recording, screenshots and thumbnails in browser. Workaround for screenshots added to lipstick.
All bugs at first boot are features.
FAQ
Q: How to run apk?
A: It's not android, you can't
Q: Can I switch between hardware keyboard layouts?
A: Default xkb layout switch shortcut: "shift + sym". You need to also set second keyboard layout:
dconf write /desktop/lipstick-jolla-home/layout "'us,ru'"
Click to expand...
Click to collapse
In newer releases layouts can be enabled in settings and switched via "shift + space"
Tips
Fast way to restart lipstick:
shift + tab + k
Alt + Tab like switching (if you have sailfishos-alttab-patch installed):
OK + tab
To disable volume media keys:
dconf write /apps/photonq-helper/mediaKeysEnabled 0
batt_health can cause reported battery capacity decrease which I am not sure works correctly at least on my aging battery. It's disabled since 3.3.0 in 2 places in /init.target.rc. Therefore btry will not report Aged Capacity anymore.
To use h264 (hardware accelerated) decoder in youtube set in about:config media.mediasource.webm.enabled to false
user name is still 'nemo' instead 'defaultuser' even for latest releases
Changelog
4.4.0.68
* Partially usable browser. Javascript doesn't cause crash on almost all sites like in 4.0-4.3 sfos. Tabs in landscape mode are unusable.
* Using browser probably breaks video encoding/decoding ('vid_dec_open() max number of clientslimit reached' in dmesg). Killing minimediaservice/browser usually helps.
* Disabled sailjail, and enabled start up boosters back.
* Few general sfos bugs more (see patchmanager catalogue for my patches)
4.3.0.15 - No for daily use, just required Stop Release
4.2.0.21 - No for daily use, just required Stop Release
4.1.0.24 - No for daily use, just required Stop Release
4.0.1.48
Broken browser
3.4.0.24 - Latest usable version
Fix memory leak when taking screenshot
Add workaround for remembering wlan state after reboot in airplane mode
Media keys works only in locked screen
3.3.0.16
NFC pn544 plugin added
batt_health disabled in /init.target.rc
glibc 2.30, gcc 8.3
3.1.0.12
kernel: hold volume up/down to select next/previous song
droid-hal-init: disable mpdecision due to constant cpu usage
3.0.3.9
Patch glibc for 3.0 kernel
3.0.2.8
Handle system and data partition automatically
New methods to wake up sensors
3.0.1.11
kernel: Fix crashes caused by new firewall rules
kernel: Experimental multi LUNs support
droidmedia: Fix random audio/video fail in browser
usb-moded: Mass storage was dropped in upstream. Use patched one
Click to expand...
Click to collapse
XDA:DevDB Information
SailfishOS 3 for Photon Q, ROM for the Motorola Photon Q 4G LTE
Contributors
elros34, vevgeniev
Source Code: https://github.com/elros34?utf8=✓&tab=repositories&q=msm8960&type=&language=
ROM OS Version: 4.4.x KitKat
ROM Kernel: Linux 3.0.x
Based On: CyanogenMod
Version Information
Status: Alpha
Created 2018-11-23
Last Updated 2019-08-20

Thanks for maintaining this for our devices @elros34
I have been meaning to try Sailfish for some time on my RAZR HD (xt926) and i finally got around to it the other day only to find that it wont boot up.
As per the 2.0 thread i can flash CM11 and that will boot and work fine but once i flash Sailfish over the top it wont boot past the bootloader unlocked logo. I have tried both the xt907 and photonq zips but neither will boot.
The xt907 zip did shown some signs of something happening since the led would light up either orange or white but after leaving it for 45 mins with no other signs of life i gave up on it.
Please find attached a list of my device drivers using the following command:
Code:
ls -alR /dev
Are there any chances of this running on my xt926 ?

Thanks, so it has xt907 like partition table, you can't use photon q image. LED glowing means system is booting.
Boot to TWRP then:
Code:
rm /data/.stowaways/sailfishos/init_disable_telnet
Now reboot, connect phone to usb and telnet to it:
Code:
telnet 192.168.2.15 2323
In windows you can use putty but it's hard to copy logs from it.
Then wait a while so logs are complete and run:
Code:
dmesg
journalctl --no-page
logcat
evdev_trace -I

elros34 said:
Thanks, so it has xt907 like partition table, you can't use photon q image. LED glowing means system is booting.
Boot to TWRP then:
Code:
rm /data/.stowaways/sailfishos/init_disable_telnet
Now reboot, connect phone to usb and telnet to it:
Code:
telnet 192.168.2.15 2323
In windows you can use putty but it's hard to copy logs from it.
Then wait a while so logs are complete and run:
Code:
dmesg
journalctl --no-page
logcat
evdev_trace -I
Click to expand...
Click to collapse
Thanks @elros34
Please find attached the various logs from my xt926.
Note i'm still running Sailfish 2.1.3.7, i figured it would be easier to start with that but if needed i can re-run these on 3.0.0.8
I have no idea what most of it means for the most part but a few errors did stand out to me in particular
Code:
Dec 12 20:20:16 Sailfish systemd[1407]: Failed to start The lipstick UI.
Could this possibly explain why its not booting any further?

Lipstick fails to start because xt926 use different touchscreen driver. Change "/dev/touchscreen" to "/dev/input/event1" in /var/lib/environment/compositor/droid-hal-device.conf
Also paste output of:
Code:
udevadm info -a /dev/input/event1

elros34 said:
Lipstick fails to start because xt926 use different touchscreen driver. Change "/dev/touchscreen" to "/dev/input/event1" in /var/lib/environment/compositor/droid-hal-device.conf
Also paste output of:
Code:
udevadm info -a /dev/input/event1
Click to expand...
Click to collapse
Thanks @elros34 its working now after changing the touchscreen driver boots up fine. I'm not seeing any immediate issues but will see how i get on with it. First impressions are very good, a really nice os i'm actually surprised at how fast and fluid it is.
Here is the output of
Code:
udevadm info -a /dev/input/event1
Code:
sh-3.2# udevadm info -a /dev/input/event1
Udevadm info starts with the device specified by the devpath and then
walks up the chain of parent devices. It prints for every device
found, all possible attributes in the udev rules key format.
A rule to match, can be composed by the attributes of the device
and the attributes from one single parent device.
looking at device '/devices/i2c-3/3-0048/input/input1/event1':
KERNEL=="event1"
SUBSYSTEM=="input"
DRIVER==""
looking at parent device '/devices/i2c-3/3-0048/input/input1':
KERNELS=="input1"
SUBSYSTEMS=="input"
DRIVERS==""
ATTRS{name}=="melfas-ts"
ATTRS{phys}=="3-0048/input0"
ATTRS{properties}=="2"
ATTRS{uniq}==""
looking at parent device '/devices/i2c-3/3-0048':
KERNELS=="3-0048"
SUBSYSTEMS=="i2c"
DRIVERS=="melfas-ts"
ATTRS{drv_debug}=="Debug Setting: 0"
ATTRS{drv_reset}=="Reset: HIGH"
ATTRS{hw_irqstat}=="Interrupt line is HIGH."
ATTRS{ic_reflash}=="No firmware loading in progress."
ATTRS{irq_enabled}=="Interrupt: 1"
ATTRS{latency_debug}=="Latency Debug Setting: 0"
ATTRS{latency_times}==""
ATTRS{latency_values}=="Touch Latency Time: Average 0uS, High 0uS,0 interrupts of 0 were slow"
ATTRS{name}=="melfas-ts"
looking at parent device '/devices/i2c-3':
KERNELS=="i2c-3"
SUBSYSTEMS=="i2c"
DRIVERS==""
ATTRS{name}=="QUP I2C adapter"
I'll also see if i can convert some of the other xt925 and xt926 users for testing.

Absolutely love this - haven't had a single problem yet. Thank you so much elros34.

Could somebody check what "getprop ro.product.device" returns for xt926 or xt907 with sailfish installed?

mounting /dev/mmcblk0p39 on /data failes
Hi,
at first i would like to thank you for building SFOS3 for the Photon Q series, i bought another XT907 to finally get SF running on this pretty nice and tiny handset.
As @drkdeath5000 i stuck at the bootloader unlocked screen but with another problem as the touchscreen driver for his XT926.
I think it's a problem with the partition table here the error from /init.log
mount: mounting /dev/mmcblk0p39 on /data failed: No such file or directory
I followed the installation instructions you provided and flashed cm11, which is booting without issues. I already tried it with and without wiping dalvik/cache, with and without booting to cm11 first. So i would really appreciate your help. If i can provide some more detail just tell me.
Best regards
André

rkdeath5000 get further because he used old xt907 image, you can't use photon q image in XT907.
I have tried to support all devices in one image. I even prepared untested script to update kernel but need a nice way to distingnues between devices. No feedback so far.
Few days ago I came up with different an idea how to auto detect correct partitions in all devices but so far I am struggling with some serious issue in 3.0.2 so I am not sure when I will release it.

elros34 said:
Could somebody check what "getprop ro.product.device" returns for xt926 or xt907 with sailfish installed?
Click to expand...
Click to collapse
On my XT907 it returns scorpion_mini

Thank you for your fast response,
as you recommended Version Alpha3 is running but of course i would like to run SFOS3 So i would like to help you in any way possible.
Best regards
André

If you could test whether this image works (boots without issue and touchscreen works) then it would be great. This is image I just built with new method to detect correct partitions but without all needed patches for middleware so other bugs are not important for now.

Thank you so much! I can hardly tell you how happy you made me I always wanted i tiny handset running on SFOS and finally after i already had given up on that your rom make it happen.
I just started some basic testing on it, as i want to wait for the screen protector before starting to really use it so i'll give you a feedback on the rom later.

3.0.2.8 Released as OTA and new image probably for all moto_msm8960_jbbl devices.
Also I created new patch for Alt+Tab (OK + Tab key) like switching between windows. It's added to my obs repo.

So far the new version alpha9 installs without issues on the XT907. Right now i have just one problem, as in version alpha8 I'm not able to send text messages (SMS). I tried different sim cards from two different networks, so i think it's a problem within the ROM. How could i help you on this? Maybe collecting some logs?

What about Alpha3 or android? To boot android you don't have to flash whole system, just boot cm11 kernel via fastboot. Have you tried to set "Prefer 3G" in cellular settings?
To get most basic logs, reboot phone and try to send sms, then:
Code:
dmesg
journalctl --no-page
logcat -b radio
If it's something more serious then you will need to follow:
https://jolla.zendesk.com/hc/en-us/articles/203761078-How-to-collect-SMS-logs-

Thanks so much for 3.0.2.8 - works great. Really hope you're able to give us a 3.0.3 with the updated browser.
Don't know if you have any interest/knowledge on Maemo Leste or PMOS, but since you're the most knowledgeable person on the Photon Q, just wondered if you could hazzard a guess as to how possible it might be to get them working on this device further down the line?
Thanks again.

Yes, updated browser is tempting so I will definitely bring 3.0.3 when it will be available for ported devices.
Unfortunately I have never ported Leste or Postmarketos so I have limited knowledge here.
With Photon there are several issue like: no sim without modification and no flex cable to buy. Also we are stuck with android drivers and ancient 3.0 kernel with no chance for upstream. It means to run anything (in usable form) other than android we need libhybris. I think there are better devices with more active developers for these systems: droid 4 - have ongoing upstream efforts, Fxtec pro1 for sure will have 4.x or even 5.x kernel. That's why you will not find photon in actively supported devices in postmarketos or leste site.
- Leste use hildon-desktop (x window manager) so it would be probably not trivial to get libhybris based ui acceleration if it's possible at all. Is that os even daily usable?
- After a quick read of Postmarketos wiki looks like it support wayland based compositor like weston so it is a good sign. I was able to run libhybris accelerated weston in ubuntu chroot in sailfish. It has some touch issues but it may be because I run it nested in lipstick. From what I understand if device doesn't have upstream kernel then postmarketos requires ported halium and lxc containers. That might be not possible because of 3.0 kernel but you will never know until you try.
Take everything I said with a grain of salt and start porting. For halium you will probably need newer base than cm11. There are few important commits which are needed otherwise kernel will not work.

SMS issue could be general ofono bug: https://together.jolla.com/question...installing-3028/?answer=205366#post-id-205366
Jolla is focused on android8 base so older bases are neglected. Upstream libhybris is also broken for hybris-11 base.

Looking for kernel module cdc_acm (ttyacm/ttyacm0)

Hi,
I'm looking for a way to get support for an USB CDC ACM device on my OnePlus 6 with OxygenOS 9.0.9.
If I plug in the USB device it is correctly detected but the driver is missing. (On my linux box, the kernel module cdc_acm is loaded and I can connect via the device /dev/ttyACM0).
I did not find an offered kernel which supports my goal. So I suspect such a kernel does not exist. Perhaps some kernel provider could add this support?
Or would it be possible to compile the module on my own? Any help or link welcome!
Thank you very much.

[RECOVERY][11.0][UNOFFICIAL] TWRP 3.7.0_11-0 for Unihertz Atom L and XL [Alpha] [2023-04-16]

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Code:
* Your warranty is now void.
*
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you.
This is a TWRP 3.7.0_11-0 recovery for the Helios P60 based Atom L (Atom_L) and Atom XL (Atom_XL), two rugged Android phone released by Unihertz in July 2020.
This recovery supports both devices as well as both regional variants!
You need to make sure which device and variant you need!
Team Win Recovery Project, or twrp for short, is a custom recovery built with ease of use and customization in mind. Its a fully touch driven user interface no more volume rocker or power buttons to mash. The GUI is also fully XML driven and completely theme-able. You can change just about every aspect of the look and feel.
Warning
Backup your data before trying to decrypt inside TWRP.
Decrypting could potentially lock you out from your ROM. I learned that the hard way.
Although I'm quite certain that I fixed the underlying issue it's better to be save than sorry.
Not Working
You tell me
Releases
Atom L EEA (european union)
Atom XL EEA (european union)
Atom L TEE (non-european union)
Atom XL TEE (non-european union)
How to install
How to Update
Links
LineageOS
Common device tree
Device tree Atom L EEA (european union)
Device tree Atom XL EEA (european union)
Device tree Atom L TEE (non-european union)
Device tree Atom XL TEE (non-european union)
Bug reporting
Spoiler: Changelog
2023-04-16
* Decryption is working now
2022-10-05
* Modified the second touchpad driver to work in recovery mode too
2022-07-15
* Switched to TWRP 3.6.2_11-0
* July 2021 vendor updates included (needs vendor to be upgraded manually)
* Decryption is not working (for now)
2022-01-30 (Only for Atom L TEE)
* Changed the patched kernel to the one from the Atom L EEA
2021-08-10
* Security string set to 2099-12-05
2021-06-16
* May vendor updates included (needs vendor update to be applied beforehand)
2021-05-11
* Decryption is fully working now
2021-04-15
* Version bump to TWRP 3.5.2
* Combining the work for the Atom L and XL
2021-03-11
* Version bump to TWRP 3.5.1
* Decryption is working now (with the exception of the user scope like /data/media/0 & others)
2021-02-18
* trustkernel daemon (teed) is working now, decryption still doesn't work
* adb is working now without the need to deactivate mtp
2021-01-15
* Timezone set to europe by default
* Vibration is back (but turned down)
2021-01-14
* Sideload is working
* Install zip/img is working
* Data decryption is not working
* MTP is not working
* ADB is working (MTP needs to be disabled)
Help from other developers is certainly welcome.
Credit and Thanks
TWRP team
@PeterCxy for starting the work on the Atom L
Enjoy!
XDA:DevDB Information
TWRP 3.7.0_11-0 for Unihertz Atom L and XL, ROM for the Android General
Contributors
a-dead-trousers
Source Code: https://github.com/ADeadTrousers/twrp_device_Unihertz_Atom_LXL
ROM OS Version: Android 11
ROM Kernel: Linux 4.x
Based On: TWRP
Version Information
Status: Alpha
Created 2021-01-15
Last Updated 2022-10-05

Hello a-dead-trousers
I bought an Atom L and want to install Lineage OS on it. As a newbie to Customs ROM, I'm trying to get ahead with the details here. ADB and Fastboot drivers on the PC are installed and I'm trying to work through points 1. Unlocking and 2. Installing TWRP recovery but am running into difficulties on my device and hoping for help: after typing `adb reboot bootloader` the phone's screen gets black with the indication '=> FASTBOOT mode...' in the lower left corner in very small caracters. Any further command on the prompt leads to an error < waiting for any devices > and < Too many open files in system > See attached image. I have to press the Power button to restart the official Android OS. How can I overcome this issue?

Honestly I normally also use Windows but for this work I switched to Linux.
`Fastboot mode` on phone screen is correct.
If the phone is in fastboot mode, connected to your PC and you type `fastboot devices` you should see it's serial number along with `fastboot` indicating the mode. Like you see it with `adb devices`.
So my guess is a problem with the windows drivers especially the fastboot portion.
Have you tried it with the MTK drivers?
https://github.com/ADeadTrousers/android_device_Unihertz_Atom_XL/blob/master/docs/HOW-TO-SPFLASH.md

Thank you for the quick response, @a-dead-trousers!
I installed the MTK drivers on my Win 8.1 PC from the link. I am still using this ADB driver . This info I got from here and also the ADB Tools needed. The result is pretty much the same. See images.
I must also mention that a pulsing sound (device driver sound) is heard when I enter `adb reboot bootloader` . This was also the case when i tried it before. The sound does not stop; I can only turn it off by pressing the Power button and starting the official OS again.
What am I doing wrong?

Sadly fastboot is quite different than adb.
In the case of adb there is a running application (adb daemon) that's communicating with your computer. It's part of the OS and can be rplaced/updated.
Fastboot on the other hand is running in a low-level hardware environment and cannot be (easily) replaced/updated.
"Hearing" sound while the phone is connected to the PC often happens when there is some sort of stray electric current or a short circuit.
To rule out a problem with your PC I would suggest you try it on another one (preferably with linux to even rule out windows as culprit)

Or try the official drivers: https://dl.google.com/android/repository/platform-tools-latest-windows.zip

Thanks so far. I had already installed the official drivers, as you can see in the prompts screen prints (version r30.0.5).
Is a Linux installation in a virtual machine (Virtual Box) promising or would the underlying Windows OS continue to cause possible problems with Fastboot? Is a direct linux installation mandatory?
How could Fastboot be updated even if it is more difficult? I think somehow Fastboot is ticking around.
I would like to try my Windows laptop first instead of the desktop. Installing Linux natively would only be the very last variant because of the considerable additional effort.

Logiciel-XDA said:
Thanks so far. I had already installed the official drivers, as you can see in the prompts screen prints (version r30.0.5).
Click to expand...
Click to collapse
Sorry I've overlooked that.
Logiciel-XDA said:
Is a Linux installation in a virtual machine (Virtual Box) promising or would the underlying Windows OS continue to cause possible problems with Fastboot? Is a direct linux installation mandatory?
Click to expand...
Click to collapse
Windows would need to provide the drivers so it would still interfere. I don't know of any VM that supports native USB passthrough but I could be wrong. So a linux installation would be mandatory for now.
Logiciel-XDA said:
How could Fastboot be updated even if it is more difficult?
Click to expand...
Click to collapse
That would require a serial interface (COM) or an unsoldering of the chip to flash it with an EPROM burner.
Logiciel-XDA said:
I think somehow Fastboot is ticking around.
Click to expand...
Click to collapse
Honestly I'm more concerned (or should I say in hopes) about the windows inbetween. The only other option would be a problem with the phone itself (see previous answer) and to get this through Unihertz support you would need to confess that you tried to tinker with the internals while the phone itself is operating just fine. If I were Unihertz I would say "Sorry, no replacement for you".
Logiciel-XDA said:
I would like to try my Windows laptop first instead of the desktop. Installing Linux natively would only be the very last variant because of the considerable additional effort.
Click to expand...
Click to collapse
Don't you have a friend or colleague with a linux machine you could ask for help? Or you could buy a RasberryPi or a similar device. Those are not so expensive and on the plus side you could use them afterwards for many other things like a home streaming server.

I followed the instructions exactly, but now the phone loops on the unihertz boot screen with the unlocked warning. It won't even turn off. No button combination does anything, except that volume up + power makes it reboot faster.
On Linux, using the latest android tools.
Is there any way to at least stop it from constantly booting? Is it possible to get it into fastboot any other way?
EDIT: For anyone else who has this problem, the manufacturer provides drivers and tools to re-flash the entire phone to stock. All the relevant links are here. This didn't work on my Windows machine, but it worked using Linux.
My phone has now been flashed back to stock, most stuff restored using Google's backup, but I guess I won't try this TWRP again, and stick to the LineageOS recovery instead.

uzalu said:
I followed the instructions exactly, but now the phone loops on the unihertz boot screen with the unlocked warning. It won't even turn off. No button combination does anything, except that volume up + power makes it reboot faster.
On Linux, using the latest android tools.
Is there any way to at least stop it from constantly booting? Is it possible to get it into fastboot any other way?
EDIT: For anyone else who has this problem, the manufacturer provides drivers and tools to re-flash the entire phone to stock. All the relevant links are here. This didn't work on my Windows machine, but it worked using Linux.
My phone has now been flashed back to stock, most stuff restored using Google's backup, but I guess I won't try this TWRP again, and stick to the LineageOS recovery instead.
Click to expand...
Click to collapse
Hi.
Sorry to hear that. This TWRP release was intended for those who had problems with the LineageOS recovery (stuck on green line on reboot and so on). I have an Atom XL so I cannot test it with 100% certainty but as the two devices are quite similar I myself had no problems with this exact TWRP on my own device.
If you stuck in a recovery "bootloop" you could try to press vol-down to boot into the bootloader (not fastboot). But the menu is in chineese.
For the TWRP release for the Atom XL I got this reply:
https://forum.xda-developers.com/t/...tom-xl-alpha-2021-01-15.4218695/post-84402809
Maybe this will help you.
In the meantime I'm planning to build a release without accessing the "/data" partition. Since it is encrypted and I wasn't able to find the correct setting for unencryption yet it doesn't make any sense to have it anyway. Also when tinkering with the encryption settings I wasn't able to boot into recovery too. So I believe this is the source of most of the problems.
Until then, stay tuned.
Cheers.
ADT

Also, I made a more up-to-date tutorial with the latest versions (drivers & tool) for flashing the stock rom:
https://github.com/ADeadTrousers/an...tom_XL/blob/master/docs/HOW-TO-FLASH-STOCK.md
If your device is stuck in a "bootloop" that is no problem at all because on every restart there is a 2 - 3 sec. time frame for the flashing to start.

Now Atom L and Atom XL are supported as well as both regional variants EEA (european union) and TEE (non-european union)

I just updated my Lineage releases but I've to postpone their TWRP counterparts.
Why, you ask? Well I had a major breakthrough on the decryption front. I'm now able to decrypt /data completely. But as always, with great power comes great responsibility ... or in this case great destruction.
Well it's true I was able to decrypt /data in TWRP but right after that LOS wasn't able to do the same anymore. Somehow running a full decrypt (by providing your pattern/password) on TWRP "destroys" all the information needed by LOS to decrypt. After that only TWRP is able to decrypt. Maybe that's a "security" feature of trustkernel ... I don't know yet.
Anyway, I had to completely reset my phone (even lost some data cause google drive couldn't load my backups).
Therefore I'm not going to release any updates until I figured out how to prevent this catastrophe for good.

I was able to fix the issue with decryption and locking yourself out from your ROM:
Decryption of /data in TWRP messes up password recognition on LOS · Issue #4 · ADeadTrousers/twrp_device_Unihertz_Atom_LXL
Right after providing my pattern in TWRP /data got decrypted but also LOS wasn't able to decrypt any more. My pattern always gets rejected. As far as I can tell /mnt/vendor/persists/t6 gets changed...
github.com
So now it's save enough for me to post an update.
But be warned:
The problem could still resurface so backup your data beforehand. It's better to be save than sorry.

I've been wasting so much time now in trying to get MTP working from within TWRP only to find out that under Windows it works just fine.
So it's only a problem under Linux (either only on Ubuntu/Debian or general I don't know)
I need to get some fresh air now or I'll go ape ****.

Hi! I've just bought Atom L and want to do some mods... Your how-to manual is awesome, thanks for that!
I'm just at the beginning on my way to flash LineageOS, but I can't get TWRP to work.
All of your TWRP versions are crashing on my device (european L, fresh new, no data), attaching adb log. I'm not sure where exactly the problem is...
ofc I've flashed vbmetas. The older lineageos TWRP image from peterCxy not just crashes, but also reboots phone, so i have no log....
I'm thinking about trying to build my own TWRP image when I'll have free time (but did this last time many years ago), but maybe it is just some small bit to tweak to make it work on my device? TIA!
edit: cannot attach log, dont know why...: https://mega.nz/file/JEAWwZgD#0EtOnG2_DNOry40D3PL6rGsJw7HUCcnKTBNYtu3bOj0

Code:
Fatal signal 11 (SIGSEGV), code 1 (SEGV_MAPERR), fault addr 0x0 in tid 357 (recovery), pid 357 (recovery)
This looks like a null-pointer exception (0x0) within TWRP main process (recovery).
And it's trying to do it 6 times and then gives up.
Can you try to provide a kernel dump?
Code:
adb shell dmesg > dmesg.log
or maybe even download the TRWP log?
Code:
adb pull /tmp/recovery.log

Thx for fast reply! Here are dmesg and recovery logs:
319.1 KB file on MEGA
mega.nz
9.7 KB file on MEGA
mega.nz
Now it looks its crashing when composing gui, and its not giving up, it is in loop, not only 6 times

Recovery is rebooting on 'Checking resolution...'
And according to dmesg the init script keeps repeating in the end.
You said you did everything on a 'fresh new, no data'? How did you do that?
At least you'd need to activate oem-unlock from within the rom and that would 'initialize' data.

It is brand new phone, never switched on wifi or sim. I got it today, just unboxed it, and started with enabling developer tools, adb enabled, oem unlocked and then fastboot flashing unlock, vbmetas and TWRP flash.
I don't know, maybe I will connect it to wifi and try to update to newest stock firmware, then try again.
I'm just little concerned about this section, which is telling me I have debug build kernel. but maybe it is OK, original system works OK.
Code:
[ 0.000000] -(0)[0:swapper]**********************************************************
[ 0.000000] -(0)[0:swapper]** NOTICE NOTICE NOTICE NOTICE NOTICE NOTICE NOTICE **
[ 0.000000] -(0)[0:swapper]** **
[ 0.000000] -(0)[0:swapper]** trace_printk() being used. Allocating extra memory. **
[ 0.000000] -(0)[0:swapper]** **
[ 0.000000] -(0)[0:swapper]** This means that this is a DEBUG kernel and it is **
[ 0.000000] -(0)[0:swapper]** unsafe for production use. **