yashsingh1/xdaforums huggingface dataset:
[ZTE Blade S6 ROMs, Kernels, Recoveries, & Other De] lightwars:
Fantastic! Here we have an explanation. Your device reports 268 as id which equals to msm8929 and I have a device with id 239 which is msm8939. The kernel only holds a device tree blob (dtb) for the id 239. I thought that the variant were very similar, so last time I used a dtb from the eu release but only for id 239. Attached I have added a dtb for id 268. Please test this rom with that boot image.

Again, just unpack the bootASEU.img and copy it to your device, flash it after installing the lineageos zip.

Please make a backup beforehand and report back, when you have time. Happy trying out.
[ZTE Blade S6 ROMs, Kernels, Recoveries, & Other De] Kurt Krummbein:
One step ahead :)! Phone is booting with the new boot.img ... but ends with a bootloop.

Highest was one boot with start of the setup-wizard, but after setting language to "Deutsch (Deutschland)" (and several "Bluetooth is not working" messages) it went around again. Couldn't get logs yet ... well see ;):

Cheers

Kurt
[ZTE Blade S6 ROMs, Kernels, Recoveries, & Other De] lightwars:
Yeah! Would be best to build the dtb from source, rather than attaching just the right one to the kernel...

The bluetooth message can be made silent, by the way what build you are using? I think the first build has not the fix for the message. The build.prop should contain this line:

ro.boot.btmacaddr=00:00:00:00:00:00

and the message should not appear.

I hope there are not any preferences with could only be applied to msm8939 and not to msm8929.
[ZTE Blade S6 ROMs, Kernels, Recoveries, & Other De] lightwars:
[MENTION=4179977]Kurt Krummbein[/MENTION]

Here is my latest build or just grab the boot.img from the attachment. Which has a dtb for msm8929 build from source.

Maybe this will boot without any bootloop.
[ZTE Blade S6 ROMs, Kernels, Recoveries, & Other De] slawoko:
For which version is your latest build? the eu?

Thanks

BR Slawo
[ZTE Blade S6 ROMs, Kernels, Recoveries, & Other De] lightwars:
AS and hopefully EU.
[ZTE Blade S6 ROMs, Kernels, Recoveries, & Other De] Kurt Krummbein:
Hi!

You made it ... boots, no bootloops, no sudden reboots ... all looks fine now!

Attached find some screen-shots from LOS16 :) :good::cool::o

Cheers !!!

Kurt
[ZTE Blade S6 ROMs, Kernels, Recoveries, & Other De] lightwars:
Really great, thank you for your time and testing. :good:
[ZTE Blade S6 ROMs, Kernels, Recoveries, & Other De] R3demax:
Hi, I installed your firmware, the one that LOS 16 - is all fine, but bluetooth does not work unfortunately, have any ideas how to fix this flaw?
[ZTE Blade S6 ROMs, Kernels, Recoveries, & Other De] lightwars:
Hi, which version have you installed, please Name the date in the Rom? Which device variant have you got? EU vor AS?

Do you get the message Bluetooth is not working every other second?
[ZTE Blade S6 ROMs, Kernels, Recoveries, & Other De] R3demax:
I updated it with LOS 15.1, installed version 16 dated 2019.10.23. Well, I assume that the EU, if you turn it on, it crashes every 7-10 seconds, it only helps reboot, by the way - the firmware doesn’t really like mods, in my case it’s mostly sound, but I corrected this matter, but nothing can be done with SELinux status?:eek:
[ZTE Blade S6 ROMs, Kernels, Recoveries, & Other De] lightwars:
Maybe there is some misunderstanding here. I assume you had los15.1 running beforehand on your device, so you probably have got an AS variant. Only the latest los16.0 release supports the EU variant or there are different EU variants in the wild.

If you just installed los16.0 over los15.1 aka dirty flashed, then there should be no bluetooth crash messages. I had this on the first version, so I did not notice problems with that. But bluetooth should work normally on the build you installed, even if you do a clean install.

Don't know about any problems with mods, but I'm not responsible for the compatibility between the los16.0 rom and any mod. Sorry.

Selinux policies have to be added or corrected, then we can switch selinux to enforcing. But at the moment when we use permissive mode, anything works even if a policy is missing/broken.

By the way the ZTE stock rom was also in permissive, this way the led camera flash works on the stock rom, but did not work on cm12.1 with selinux enforcing. Crazy things ZTE have done.
[ZTE Blade S6 ROMs, Kernels, Recoveries, & Other De] lightwars:
New Version in the OP: updates los sources, so security patch level 05.12.; using power hidl and it can be used in EU variant devices.

Tip: have lesser power consumption with naptime, device got much faster into deep idle!
[ZTE Blade S6 ROMs, Kernels, Recoveries, & Other De] lagos911:
hey man... I am trying to install it to my device... EU version. When installation finish and I reboot. I dont reboot into the system. Its rebooting into recovery. After that I select reboot to system and I go back to recovery. Any advise?
[ZTE Blade S6 ROMs, Kernels, Recoveries, & Other De] Kurt Krummbein:
Hi! I've encrypted my device two weeks ago ... all went nice (lightning fast ;), much faster than my OnePlus Onyx). Wanted to flash your latest update, but TWRP refused to unlock data with my unlocking pattern (hm, was sure it already worked some days ago).

For system updates, that's no problem - flashed the 20191213 image and all runs well - but it is not possible to run TWRP-backups of data this way :(.

Cheers

Kurt
[ZTE Blade S6 ROMs, Kernels, Recoveries, & Other De] lagos911:
Hi again, now I use the boot.img to recovery and now the device its booting only at system.

I try facroty reset but its not working. I forgot to install the gaps.

OMG I am so sorry.

How can I go back to recovery?
[ZTE Blade S6 ROMs, Kernels, Recoveries, & Other De] lightwars:
Hey,

I was just asking about the factory reset and I did not want you to do so, because I have done this once a while back and think I got in this same situation, when you cannot boot the system from twrp... I have erased the misc partition like I stated and all was okay then.

So your system boots, but you have installed the boot.img on your recovery partition, that is not a problem. To get back to recovery you can reflash the recovery partition. Use an app to do so, adb or terminal command:

dd if=/path/to/recovery.img of=/dev/block/bootdevice/by-name/recovery

For example the image is twrp.img on your sdcard, than it is probably:

dd if=/external_sd/twrp.img of=/dev/block/bootdevice/by-name/recovery
[ZTE Blade S6 ROMs, Kernels, Recoveries, & Other De] lagos911:
yes I have this rom (I think the november version) my mom get a new device and after I take a backup I hard reset the blade.

After that I only can see the recovery and I cant not boot to system. I flash the rom again again november and december but nothing happens.

Thank you so much for your support.
[ZTE Blade S6 ROMs, Kernels, Recoveries, & Other De] lightwars:
Sorry, I didn't tested this myself. But I can imagine that there could be a point here, which is preventing you from accessing the data partition from within twrp.

There is a newer keymaster version, which has evolved since stock rom version 5.0.1 and twrp could be using some older version of keymaster.

Likely we need a newer version of twrp to support android pie and encryption. Not that sure here...
[ZTE Blade S6 ROMs, Kernels, Recoveries, & Other De] lightwars:
I quote myself here:
[ZTE Blade S6 ROMs, Kernels, Recoveries, & Other De] lagos911:
I try with a terminal app and I get permission denied...

I try with the app twrp manager and said that my device is not rooted.

@ dev options at root access I have only the option adb only and none.
[ZTE Blade S6 ROMs, Kernels, Recoveries, & Other De] lightwars:
I meant the terminal inside twrp, which is option 1.

Option 2 is to root your device with magsik.

Or option 3 connect to a pc and use adb, adb works from within twrp or system booted.
[ZTE Blade S6 ROMs, Kernels, Recoveries, & Other De] lagos911:
I cant use adb becuse my device cant boot to bootloader. When I give from adb the command reboot to bootloader device freeze.
[ZTE Blade S6 ROMs, Kernels, Recoveries, & Other De] lightwars:
Not sure what you want to achieve...:confused:

For the commands I gave you do not need the device's bootloader.

adb shell
su
dd if=/dev/zero of=/dev/block/bootdevice/by-name/misc
exit
exit

If your device is inside the recovery, no need to enter the su command and at the end the exit.
[ZTE Blade S6 ROMs, Kernels, Recoveries, & Other De] lagos911:
Sorry for the misunderstanding.

My device still rebooting to system. Because I flash the boot.img to recovery partition.

I am still trying to flash the twrp.img and I cant.

I am using a terminal app but I cant. permission denied.

---------- Post added at 01:29 PM ---------- Previous post was at 01:14 PM ----------

this what i get

C:\Users>cd..

C:\>cd adb

C:\adb>adb shell

Blade-S6:/ $ su

/system/bin/sh: su: not found

torage/E8BC-034B/twrp.img of=/dev/block/bootdevice/by-name/recovery <

dd: /dev/block/bootdevice/by-name/recovery: Permission denied

1|Blade-S6:/ $ adb shell

/system/bin/sh: adb: not found

127|Blade-S6:/ $ adb devices

/system/bin/sh: adb: not found

127|Blade-S6:/ $ dd if=/dev/zero of=/dev/block/bootdevice/by-name/misc

dd: /dev/block/bootdevice/by-name/misc: Permission denied

1|Blade-S6:/ $
[ZTE Blade S6 ROMs, Kernels, Recoveries, & Other De] lightwars:
OK, I thought you were able to get back into twrp and wanted to get the system booted.

Have you activated the root access for adb in the developer options?

Otherwise the su command and all succeeding commands will fail. If it is already enabled and the command will fail nevertheless, then I have no idea at the moment.
[ZTE Blade S6 ROMs, Kernels, Recoveries, & Other De] lagos911:
Its okay man I install aploite for the apps.

Hard reset its not working as well. Maybe because the recovery is missing.

I will try to root the device again. I try some apps but nothing happend.
[ZTE Blade S6 ROMs, Kernels, Recoveries, & Other De] AlexisBorovik:
Faced with problem related to FM radio on the latest beta build - "Function is not available". Is it known issue?
[ZTE Blade S6 ROMs, Kernels, Recoveries, & Other De] lightwars:
Thank you for letting us know. I have realized this also.
[ZTE Blade S6 ROMs, Kernels, Recoveries, & Other De] cd492:
I'm coming from LineageOS 14.0 and need help.

I installed the latest TWRP but can't find the img file in my Download folder. I don't see it in TWRP I only see it in Windows.
[ZTE Blade S6 ROMs, Kernels, Recoveries, & Other De] lightwars:
You want to install twrp or you have already installed it??

If you want to flash and img file with twrp, you are going into install and then click the button which changes to show img files at the bottom of the screen, select the img file and push install.
[ZTE Blade S6 ROMs, Kernels, Recoveries, & Other De] fm663:
Phone

Hi, my ZTE Blade S6 Plus, after switching on i get white screen, then after a while reboots again and again. What do I need to do to fix it and then install the latest new ROM? Thanks
[ZTE Blade S6 ROMs, Kernels, Recoveries, & Other De] lightwars:
This is probably bootloop, but you didn't state what you have done. So if you flashed a boot.img with a device tree missing for your variant this could happen, but it could be something else.

Get into recovery, backup you device and flash again, if it is right for your device. Or just install the newest rom, like state in the OP. Remeber that this thread is for the ZTE Blade S6, so thing might not work correctly.
[ZTE Blade S6 ROMs, Kernels, Recoveries, & Other De] dstruan:
Dear all,

unfortunately i need some expert support from you ;-)

Many thanks for the new 16 release ... great work

I tested the latest version yesterday on my old phone ... mainly just for interest.

I had the latest official ZTE Android 5 version installed on my S6 and after some struggle i was able to flash the Lineage OS 16 release using Kingroot and TWRP all with latest version i found on internet, and yes i did backups of Boot and Recovery with TWRP ...

After flasing i was able to boot my phone successfully and i was able to do the post configuration and all seems to work fine. Next i wanted to install google apps ...

But now my problems starts ... Kingroot is not able to root the device anymore (and Dr. Fon either) ... and when i want to use recovery mode i'm only getting ZTE recovery mode, not TWRP recovery console.

In ZTE recovery console i tested nearly everything to get a recovery installed or package installed, even with adb sideboard installation ... but nothing is accepted even my original boot and recovery images are not recognize by process. In ZTE recovery console I'm able to get a connection via adb. ">adb devices" is working ...

Futhermore i recognize that it looks like i not have fastboot installed/available on phone.

Everytime when i try to enter bootloader mode I only see blank screen ... and from computer i'm not able to connect via platform tools - fastboot to my phone to do recovery ...

I try to enter bootloader mode on phone by ZTE recovery console (Reboot fo bootloader), but without any success ... Switch on with Power on + Buttom up for 8 sec. will open ZTE recovery console

I'm frustrated ... any chance or advice ???
[ZTE Blade S6 ROMs, Kernels, Recoveries, & Other De] dstruan:
No solution ??

No advices ??

No hints ??

Whats up ??

I not understand why it is not possible to activate root-modus on a custom rom

Sorry for complaining
[ZTE Blade S6 ROMs, Kernels, Recoveries, & Other De] lightwars:
How about reading what is stated in the OP about root or inform yourself about lineage os and their addon for root. You could also use Magisk, which I do.

To your main problem, it seems you have installed the lineage rom but kept the original zte recovery. So with this recovery you can only flash zte signed roms.
[ZTE Blade S6 ROMs, Kernels, Recoveries, & Other De] dstruan:
Thanks lightwars for your reply, but instead to blame somebody how is running into an issue it would be better to help them to fix the issue.

First of all ... I read the treat and more, but maybe I missed a thing, second to run the Lineage OS installation I did it from a custom recovery, otherwise it was not possible, third I tried Magisk on the Lineage OS installation right now, but without success providing me root access and unfortunately fourth, with the ZTE recovery I was not able to recover my backup image or any other ZTE Image that I downloaded for whatever reason.

Nevertheless thanks
[ZTE Blade S6 ROMs, Kernels, Recoveries, & Other De] lightwars:
I did not want to blame you, it is just I wrote that for root there is an extra package to flash and this is not new to lineage os, that the roms comes without root and they provide the su addon.

To my knowledge if all went well you shouldn't have the zte recovery, but it is on your phone. The recovery indicates that you have a german device variant, so it will just accepts roms for this variant, so eu roms might also not work. I havn't seen any de rom.

Nevertheless I understand that you might want to use lineage, so please try this "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." There should be still the option to give adb root access.

If it is there and you can active it and have a pc/notebook. Install adb xda-how-to-install-adb, if you havn't.

Connect your phone to the pc open the command prompt and type

adb root
adb shell

If twrp is on your sdcard you can flash it like this:

dd if=/storage/XXXX-XXXX/twrp.img of=/dev/block/bootdevice/by-name/recovery

XXXX-XXXX should be numbers and letters representing your card, maybe use

ls /storage

beforehand to see it.

Let me know how it works.
[ZTE Blade S6 ROMs, Kernels, Recoveries, & Other De] lightwars:
New version in the op
[ZTE Blade S6 ROMs, Kernels, Recoveries, & Other De] dstruan:
H

Hi lightwars, sorry for the late reply and thanks for you guide ...

adb was already installed on my Laptop and I was able to connect to my phone ... Android debugging is activated and Root Access is open for ADB.

When i connect to adb on my ZTE S6 it gives me the ability to browse the filesystem .. But unfortunately i'm not able to do the "su" command ... same for "sudo" i got ... "/system/bin/sh: su: not found"

hmmm

Any ideas ??
[ZTE Blade S6 ROMs, Kernels, Recoveries, & Other De] lightwars:
There is of course the qualcomm hs-dloader mode, which can be also used to unbrick the device, unluckily I had to used it at the beginning of my lineage-17.1 test, because my recovery was erased. This was due some update settings. This is maybe the last to try.

What if you install the latest magisk.apk, what can magisk do? Maybe give me sometime, so I can prepare my device, cause it is my daily driver, to see what can be done.
[ZTE Blade S6 ROMs, Kernels, Recoveries, & Other De] lightwars:
I have updated the instruction above. Before typing "adb shell" in the command prompt type "adb root". If you then enter "adb shell" you should see the # instead of the $ sign in the adb shell.
[ZTE Blade S6 ROMs, Kernels, Recoveries, & Other De] dstruan:
Ohhh ... Mea maxima culpa ... I didn't recognized you last post ...

The "adb root" before "adb shell" worked for me ... I was able to to run the dd command and flash twrp image to recovery

Now I'm able to use twrp from recovery console ...

Many many thanks ... I hope I will be able to install the google tools right now ... That's all i need for now
[ZTE Blade S6 ROMs, Kernels, Recoveries, & Other De] dstruan:
Ahhhhh ... i get mad (not your fault). Sorry sorry ... seems i'm to stupid to do it correctly ....

TWRP is installed to recovery. LinageOS was booting after a normal restart. When i read install instruction for Google Tools, they mentioned to "factory reset" to install Google apps accordingly. So I did ... but after doing factory reset, my mobile no starts in TWRP recovery mode always ... Ahhhhhh

Finally i wiped phone and install linageOS image again ... but same same result ... Phone always boots in TWPR recovery mode

Hope i will find a solution on internet .... hmmm
[ZTE Blade S6 ROMs, Kernels, Recoveries, & Other De] dstruan:
dd if=/dev/zero of=/dev/block/bootdevice/by-name/misc

This fixed boot issue for me ...
[ZTE Blade S6 ROMs, Kernels, Recoveries, & Other De] dstruan:
I finally managed to get it done properly ... but ...

During the installation of the LinageOS Image i figured out that TWRP ask before reboot to install TWRP as System app. If i allow to install as System app, System reboot ends in a boot loop without starting the config wizard (language, WLAN, etc.). If i not allow TWRP after LinageOS installation to install TWRP as System app ... Than LinageOS boot regulary and start config wizard ... either the own one or the google config wizard (if gapps are installed as well before reboot).

So now i'm happy ;-)

I only need to find out how to recover fastboot Bootloader ... looks like it is gone.

Reboot in recovery starts TWRP recovery

Reboot to bootloader ends in a black screen

Anyway ... many thanks @lightwars for the support and your patience ...
[ZTE Blade S6 ROMs, Kernels, Recoveries, & Other De] Kurt Krummbein:
Hm, what else do you expect? If you get a reaction from fastboot commands from PC, then booloader does what it should do ;-).

Greetz

Kurt

P.S.: maybe Lightwars find some muse to update to LOS18.1 ;-).
[ZTE Blade S6 ROMs, Kernels, Recoveries, & Other De] ChrisMDA:
Happy new year, I just broke my iPhone X and have to use my old Blade S6.

Thanks Lightwars for LOS 16 just updated and noticed that my Blade is still rock'n solid.

Do you intend to update this built or maybe upgrade to LOS 18.1 ? I have some ugly grafic bugs while scrolling at the bottom of some apps, especially the contacts app which aren't there with your LOS 15.1 realease? Just tested.

Looking at some Xiaomi devices with 2GB Ram and Mediatek G25 our Blade S6 should be able to handle Android 11, too ;-)

Cheers,
[ZTE Blade S6 ROMs, Kernels, Recoveries, & Other De] theemokid:
anyone got Au boot.img?
[Xiaomi Mi A1 Questions & Answers] Rohitkalla:
I rooted my mi a1 a while ago and I want to completely unroot it. I used magisk for rooting. Now that I'm trying to uninstall magisk by removing it from app or by flashing magisk uninstaller, the device gets stuck in bootloop until I reinstall magisk. Could someone please guide me on how to proceed with complete unrooting on my device?
[Xiaomi Mi A1 Questions & Answers] coremania:
For stock reflash with fastboot.

For custom reinstall rom and twrp.
[HTC Oxygen] Geo2000:
Hi.Am tried to turn the splash screen spv c100 and we have not succeeded. Please managed some? a tutorial something. Thank
[ASUS ROG Phone II Questions & Answers] nikolaus_:
Hello guys ,

i just have my new rog phone 2 8-128 tencent version

version is WW_16.0622.1906.19_0

First of all i cant log in youtube , youtube go or yt studio. there is an error.

There is no netflix in play store , but i downloaded apk.

Twin apps not working , i have facebook instagram whatsapp but when i enter twin app menu it says there is no app.

Also is there any shortcut to get screenshot?

Thanks.
[ASUS ROG Phone II Questions & Answers] nikolaus_:
heres are the screenshots

https://eksiup.com/p/sj2315047mtj

https://eksiup.com/p/47231507r58s
[ASUS ROG Phone II Questions & Answers] bryanpen:
I also have been having problems with data not working at times. Don't know what to do
[ASUS ROG Phone II Questions & Answers] nikolaus_:
Yep same only on data ,

does your twin app working ?
[ASUS ROG Phone II Questions & Answers] bryanpen:
I don't know what that is lol
[ASUS ROG Phone II Questions & Answers] cimbom:
where did you get the phone where do you live (nerden aldın kardeşim ya biz bulamıyoruz turkiyede) :)
[ASUS ROG Phone II Questions & Answers] bryanpen:
May have found the problem. Turn off all auto start manager functions and data should work for apps again
[ASUS ROG Phone II Questions & Answers] Mayank7795:
Since you have a Tencent variant with WW ROM, the issue might be because the WW ROM was partially loaded, i.e., the device fingerprint still belongs to CN firmware whereas you havea WW ROM image. Check for threads in the ROG Phone 2 forum for full CN->WW conversion. These issues should stop then.
[ASUS ROG Phone II Questions & Answers] bryanpen:
Yeah I found that out when rooting. Used root explorer to change country fingerprint and it all went away. Now I will keep the phone:good:
[ASUS ROG Phone II Questions & Answers] bryanpen:
I got mine on eBay. It was shipped from New Jersey. I live in California
[ASUS ROG Phone II Questions & Answers] Mayank7795:
Great man. Happy to help.
[ASUS ROG Phone II Questions & Answers] no go0d:
Any thread that shows how to update to latest firmware and have root on WW rom or US version?
[ASUS ROG Phone II Questions & Answers] no go0d:
I know I have to patch the boot img through magisk. But how can I get the boot img? I have the US version and my build number is different from everything listed on ASUS website.
[ASUS ROG Phone II Questions & Answers] sesz:
I don't see that firmware on the Asus site, maybe it never auto updated on initial setup. I rooted on 1907.33 firmware so maybe try updating to that then root.

1. Download firmware WW-16.0622.1907.33 from Asus to the root of your phone (take it out of download folder and put directly in internal memory no folder)

2. Reboot the phone, upon reboot you will be asked to install the updated firmware. Install and reboot.

To root;

3. Sign out of google account

4. Download and install Asus bootloader unlocker apk HERE

(this will wipe your device so backup anything you need on the phone first. Also the phone may boot twice DO NOT press power button to pause the boot process)

5. Now your bootloader is unlocked and 1907.33 firmware installed you can follow this guide to root the device. (since you are on 1907.33 start at step 4. Only do steps 4-7 in this guide)

To udate to latest firmware;

6. Delete the previous firmware 1907.33 you just downloaded on internal memory. Download the new WW-16.0631.1908.12 and put it in internal memory no folder.

7. Follow this guide HERE