yashsingh1/xdaforums huggingface dataset:
[HTC One S] KuGeSch:
that's what I tried, but after I interrupted the boot process and rebooted into recovery (via ADB) I only could find the previous "last_kmsg" in the directory /proc using the filemanager in the recovery... :(
[HTC One S] ninjamirage:
Yeah I've had this problem on multiple devices with AOSP Roms. I think you're right. Just have to live with it.
[HTC One S] pavel.bosco:
# new version uploaded

lineage-14.1-20170224-UNOFFICIAL-ville.zip

android ver 7.1.1_r21 https://review.lineageos.org/#/c/160504/

security update of 5.02.2017

no cherry-picks
[HTC One S] KuGeSch:
Same result as with 2017.2.18

boot process running eternally

TWRP 3N2

OpenGapps Micro
[HTC One S] pavel.bosco:
only can recommend wipe /system & /data now, since I have no idea that is going on w/o logs, don't forget to backup important data.
[HTC One S] KuGeSch:
since I cannot produce/provide logs I will stick to 2017.2.12

clean install is too much hassle at the moment

anyway thanks a lot for this Nougat ROM!
[HTC One S] Fear of Oneself:
No issues with the latest build. Not running gapps though. Fdroid for apps, oandbackup to replace titanium backup.
[HTC One S] pavel.bosco:
but, 18-Feb is not the latest for the moment
[HTC One S] Wel1973:
Dirty flash over , no issues with 02/24 rom here. I´ve also decompiled framework-res.apk to modify power_profile.xml for recognize my 2300 battery that I´ve installed and no troubles. THX for that!!
[HTC One S] KuGeSch:
finally I could retrieve the appropriate last_kmsg

I flashed the boot.img of the 2017.2.24 rom

relevant vars:

version-bootloader: 2.16.0000

version-baseband: 1.11.50.05.28

version-cpld: None

version-microp: None

version-main: 4.05.401.1

version-misc: PVT SHIP S-OFF

product: vle

platform: HBOOT-8960

modelid: PJ4010000

cidnum: 11111111

Tampered

Unlocked
[HTC One S] pavel.bosco:
try to boot with this: boot.img
[HTC One S] KuGeSch:
no difference
[HTC One S] pavel.bosco:
that's good, because I excluded 2 commits for linker, which I commited myself (I'm not the author though), so at least this is not them, thanks.

from logs I see your proximity&light sensors init fails to initialize, nothing more to say for now.
[HTC One S] The Setlaz:
Looks to me you didn't do firmware upgrade, only HB2.16.

Could this be the cause? :confused:
[HTC One S] KuGeSch:
it works up to 2017.2.12

any suggestion is welcome
[HTC One S] Flippy498:
4.x is the latest firmware. It doesn't matter whether you use the 4.6.x version from llabtoofer's thread or the unofficial 4.5.x RUU. Only the radio seems to be outdated. However, since you can flash single firmware files with S-OFF that might be intended by KuGeSch...
[HTC One S] pavel.bosco:
this is strange, because I believe last boot.img which I gave you, only contains changes up to Feb 7.

maybe your own setup changed since.
[HTC One S] moozon:
I have the same behavior. In my case the hero of the occasion was "substratum theme engine" app.
[HTC One S] KuGeSch:
ok guys

I exploited all of your suggestions in order to provide enough facts for improvement.

Last but not least I upgraded the firmware as questioned by [MENTION=2268315]The Setlaz[/MENTION] using the file

'firmware_hboot2.16_radio1.20.zip' as it was given at the beginning of this thread.

Attached please find the corresponding last_kmsg file.

Being a physicist and not an IT-Engineer I just can tell you my opinion

If 2017.2.12 works on my system&configuration and 2017.2.24 does not, it must

be the changes in the rom which are causing the failure to perform on my device...
[HTC One S] derkleinebroicher:
Same for me. Unfortunately I had no Nandroid without substratum, so I had to do a clean install. Now I have the same problem again. Currently I am running [MENTION=6095106]pavel.bosco[/MENTION] latest build. My only backup again includes a substratum theme. If I try to uninstall it, phone won't boot. Dirty flashing the build from 12.02. does not boot either. But I don't want to make a clean install again. So any help or suggestions is highly appreciated.
[HTC One S] KuGeSch:
I can only give this suggestion, which worked for me:

wipe cache, dalvik and system

install 2017.2.12 and opengapps at your choice

this will not touch your data...

btw I don't believe that substratum is the problem,

after upgrading the firmware I had a complete empty phone (=clean install?!) and 2017.2.24 did not finish the boot process
[HTC One S] pavel.bosco:
I guess that Setlaz means is using RUU to upgrade to HBOOT2.16 will also repartition your device in correct way. only guessing, that could be wrong.

it's probably of no sence, but could you execute

adb shell df

the ps-sensor which fails in your device is same as in mine. the kernel probably not an issue, you can double check this, by flashing newest rom (2017.2.24) and then boot into fastboot and make

fastboot boot boot.img

, where boot.img - is kernel

extracted from older

(2017.02.12) rom.zip - it will fail if problem is NOT in new kernel

and if it's indeed kernel which fails, you could flash newest rom and reflash on top of it the older kernel with

fastboot flash boot boot.img

, where boot.img - kernel extracted from (2017.2.

24

) - it will succeed if problem is in new kernel

but, I suspect it's not the kernel.
[HTC One S] KuGeSch:
this would be nothing but trial and error

my questions are:

- what are the differences between 2017.2.12 and 2017.2.24?

- which of these differences could cause the error?

- how can we verify each possible cause?
[HTC One S] pavel.bosco:
I give you only 2 test-cases, while you can be sure there is a lot more in "each possible causes"
[HTC One S] KuGeSch:
of course it's a lot more

I am used to work in a systematic way

if that is not valuable here, I don't have any problem

but I will not waste my time in doing trial and error experiments without knowing any background.
[HTC One S] pavel.bosco:
to make things easier: there a lot of projects which are compiled during rom build. kernel project is the root one. so this is pretty much systematic, from my perspective, to exclude it first.

kernel is all that in boot.img - very small file.

then there is another set of projects, they form system image, which is a bit harder to split into parts and test.

but as your boot fail in sensors part, it narrow things down - i.e. it likely not any system app/gapp or so, mb some script or config. but only if it's NOT kernel itself.

if you look to my message announcing rom 2017-02-18, there are 3 link of commit's I cherry-picked, 2 of this links was later commited to kernel, and one goes to system.img.

w/o this 2 commits, I believe kernel was the same as your previous one. and probably we already proved today/yesterday (depends on TZ), that even old kernel will fail with newer rom.
[HTC One S] derkleinebroicher:
Following [MENTION=8038666]KuGeSch[/MENTION] suggestion, I wiped system and caches, installed build from 12.02. and opengapps package (the aroma package, which I use since don't know when and which never gave me any problems). My device boots, but now I get android.process.acore FC's. This means, my phone app does not work. Phone rings on an incoming call, but I can't receive the call and can't make an outgoing call.

From my point it seems, that there is something in the system settings, which are restored in the data partition of a nandroid, which is incompatible between the build from 12.02. and the one from 24.02. But this is only an idea, I wold call myself an amateur, concerning this stuff :o
[HTC One S] Flippy498:
Until now, I didn't have the time to update my phone since the version from the 1st February. The version from the 24th February works just fine for me (dirty flashed over the old setup). However, since I'm using magisk instead of SuperSU I reflashed the latest version of it before I booted the new rom version the first time. Therefore, I'm not sure whether that is the reason because of which I didn't face any problems.
[HTC One S] KuGeSch:
carried out your proposed experiments

no boot process finished...

see attached files

01=rom2017.2.24boot.img2017.2.12

02=rom2017.2.24boot.img2017.2.24
[HTC One S] pavel.bosco:
the second should be rom2017.2.12boot.img2017.2.24,

and, btw, I see same error in 01 log. PS-sensor fails to start. which prove my guess it's not kernel.

ok, let's say "partially prove"
[HTC One S] KuGeSch:
sorry, maybe I got you wrong in your experiment instruction

if you need any additional experiment, please let me know
[HTC One S] pavel.bosco:
if it doesn't harm you much, please try to

1. flash rom of 2017-02-12

2. boot into bootloader

3. fastboot flash boot boot.img

^^^^^ this time boot.img should be from _latest_ rom of 2017-02-24 (extracted)

4. reboot

you should be fine then. but apps will be from 2017-02-12, only kernel will be new.

I know it might sounds as too much, but I actually make a lot of similar experiments every week (not kidding)
[HTC One S] KuGeSch:
no problem

what about wiping?

at the moment I have installed rom 2017.2.12

is it enough just to boot into bootloader and flash boot.img2017.2.24? and reboot

if not, please give me exact details how to proceed
[HTC One S] pavel.bosco:
yes, you can make even better, by not flashing, instead just

fastboot boot boot.img2017.2.24

this way new kernel will be effective only until next restart, after restart you'll boot into boot.img2017.2.12 from rom you flashed before.
[HTC One S] KuGeSch:
booting rom 2017.2.12 with boot.img2017.2.24 works
[HTC One S] pavel.bosco:
there are now 2 suspects:

1. your hboot is wrong (or not correcltly set up)

2. some projects have wrong commits

giving that others have successfully installed/boot latest rom, including me, while my phone uses same sensor on latest rom, which fails to start in your, I think we need to check if your bootloader (hboot) are ok.

for this I asked you before to exec "adb shell df" - it shows how partitions splitted on sdcard.
[HTC One S] KuGeSch:
Filesystem 1K-blocks Used Available Use% Mounted on

tmpfs 406632 616 406016 1% /dev

tmpfs 406632 0 406632 0% /mnt

/dev/block/mmcblk0p17 204580 34152 170428 17% /firmware_radio

/dev/block/mmcblk0p18 204580 6136 198444 3% /firmware_q6

/dev/block/platform/msm_sdcc.1/by-name/system 1677156 841368 835788 51% /system

/dev/block/mmcblk0p34 258012 5892 252120 3% /cache

/dev/block/mmcblk0p35 12643488 10803516 1839972 86% /data

/dev/fuse 12643488 10803516 1839972 86% /storage/emulated
[HTC One S] pavel.bosco:
unfortunately I can't say is it right or wrong. it differ from mine: your /dev is bigger +16K, and /data is bigger for same +16K, not sure is it ok or not.

I checked the hex difference between hboot which you probably used (is it from https://xdaforums.com/showpost.php?p=63384790&postcount=22 ??), looks the same with that as I use (excluding red text during boot).
[HTC One S] KuGeSch:
Yes, it is from this link, I installed this after [MENTION=2268315]The Setlaz[/MENTION] mentioned the firmware does not look complete...
[HTC One S] The Setlaz:
Just in case - I am building my own ROMs but shouldn't be any different from [MENTION=6095106]pavel.bosco[/MENTION] - I didn't build much in February, made the leap from 20170203 to 20170225 then to 20170302 without any problem. (no root - flash zip separately if needed / no CMFM)

You can give it a go: Android File Host
[HTC One S] pavel.bosco:
in attemp to test if something got broken in commits after feb-12, which should be very odd

system.img

this is build of almost latest sources of yesterday, except init scripts for kernel, they are of feb-3, if this will start, we on the right way.

you should first boot into recovery and clean dalvik & cache, then reboot directry from recovery to fastboot and

fastboot flash system system.img

flashing system is like flashing new rom.zip, don't be surprised

I didn't try that myself, so do it in your spare time only.
[HTC One S] KuGeSch:
did not work

last_kmsg attached
[HTC One S] KuGeSch:
gave it a try

wiped cache&dalvik

installed rom 20170302 in recovery (TWRP N2)

interrupted boot process after about 12'

last_kmsg attached
[HTC One S] pavel.bosco:
[binary removed]

now I put some "new" commits which deal with different initialization error on i2c bus, which handle sensors

tried myself, see no difference, so it's compatible with currently working devices.

not sure if it will help you, because actually it's not clear why your sensor fails.

you can try this kernel with any rom, which doesn't work now for you.

it this doesn't help we can try to increase retry pause for reading ID of your PS-sensor, the operation which fails 10 times in your log.
[HTC One S] KuGeSch:
tried it with 20170302 from [MENTION=2268315]The Setlaz[/MENTION]

didn't work

last_kmsg attached
[HTC One S] pavel.bosco:
(binary removed)

well, last chance!

same as before + increased timeout for PS sensor id reading (only first init of sensor)
[HTC One S] KuGeSch:
last chance missed :crying:

last_kmsg attached
[HTC One S] pavel.bosco:
now you are on your own with your hboot.

I would suggest to try to stay with unworked rom and try to reflash different options of hboot.

mb also try to rollback to M5 TWRP, as Matt Mower suggested at the beginning - and reflash rom using it.

I'm still on N1, it works for me.
[HTC One S] KuGeSch:
what do you mean with "my hboot"?

sounds a bit like I chose a wrong one

I tried M5, did not work

where can I find a better hboot?
[HTC One S] Flippy498:
There are only two ways for updating the One S correctly. Either by flashing the full firmware pack that got leaked by Llabtoofer (the one that is linked on page one of this thread is just a re-upload by another user - the original one is inside the install package.rar which can be found on Llabtoofer's Mega.nz account) or by using the unofficial RUU. The differences on the firmware side are only minor between version 4.06.401.1 (Llabtoofer's pack) and version 4.05.401.1 (the RUU). Therefore it shouldn't matter for a custom rom which one you use. Aside from that the firmware pack is nothing more than a RUU without a system/rom. Therefore you need to flash a compatible rom after using the firmware pack or the phone won't boot whereas the RUU would boot to a unofficial stock-like rom.

I personally have used both in the past and never had any problems with "hboot 2.16 roms". Currently, I'm using the firmware from the RUU.
[HTC One S] pavel.bosco:
I initially used RUU, then re/updated to modded hboot version about a month ago, which seems the same binary as 4.06.401.1 you mentioned except red label text not shown during boot (hex-edited to spaced). I do have some problems during recent hboot update, including bootloop, but it was solved somehow during set of reflashes, can't recall details.
[MENTION=5872674]Flippy498[/MENTION], btw could you remember sensor/bootloop problem after updating hboot, either your own or from threads, wchich prevent's it from loading?

personally I have a problem from flashing RUU in the past till today, that my PS-sensor got incorrectly calibrated during the boot, and always report far. which I workaround using custom script to recalibrate it back. but this error doesn't prevent boot to succeed, while for KuGeSch PS sensor seems to appear completely as missed at boot initialization.
[HTC One S] Flippy498:
Sorry, this is the only thread in which I read something about sensor issues. (Well, maybe there have been some reports in the liberty rom thread but I'd say those aren't important since that rom is a port from another phone. Therefore issues with the hardware are expected to happen until the port is completely finished.) And I never noticed any misscalibration on my phone, yet.

I can't promise a specific date for having them finished but I can try make some tests with my phone if you need some more logs. Just tell me the scenarios that are needed to be tested (rom build, gapps build/no gapps, rooted with SuperSU/rooted with magisk/not rooted). If I cannot reproduce the issues then I can try to test the same scenarios with the other 4.x firmware. If the problem still doesn't occur then we can say that the hardware of the bootlooping phones is probably dying. (Don't forget that the One S is 5 years old. I know several people whose smartphones' hardware died after 2 or 3 years of usage.) If the problems occur on both firmware versions than it's probably the rom's fault and if the problem only appears while one of the firmware versions is in use then we have found the first custom rom of the One S which requires a specific 4.x firmware.
[HTC One S] mraabs:
Hi,

I have to questions I would like to ask you guys

1. Currently I am running android 5.1 how can I install this rom?

2. How smooth is this rom on our one s?
[HTC One S] KuGeSch:
1. Please have a look at the first page of this thread, there you will find the required info.

2. On my device it's running smoothly (better than CM 12.1), but I can only run 2017-02-12, others are running 2017-02-24 which doesn't run on my device because of ps-sensor issues.
[HTC One S] Flippy498:
Just a little sidenote [MENTION=6095106]pavel.bosco[/MENTION] in regard to the opening post: Facepalm works fine with ViperOneS, too. I used it myself with that rom. (Maybe that information might be useful since you can't download CM11 from the CM servers, anymore.)
[HTC One S] pavel.bosco:
can't just leave it..

added more commits for i2c-qup bus,

make this driver in sync with list of commits from there https://github.com/LineageOS/androi.../commits/cm-14.1/drivers/i2c/busses/i2c-qup.c,

but, for now I don't see any difference in my setup (which works fine even w/o them), for instance, still see same retries for other sensor, but this is ok, as it works at the end

[ 0.697451] [cap] cy8c_init_sensor
[ 0.697573] qup_i2c qup_i2c.5: QUP: I2C status flags :0x1363c8, irq:187
[ 0.697634] qup_i2c qup_i2c.5: I2C slave addr:0x20 not connected
[ 0.707767] qup_i2c qup_i2c.5: QUP: I2C status flags :0x1363c8, irq:187
[ 0.707797] qup_i2c qup_i2c.5: I2C slave addr:0x20 not connected
[ 0.717930] qup_i2c qup_i2c.5: QUP: I2C status flags :0x1363c8, irq:187
[ 0.717961] qup_i2c qup_i2c.5: I2C slave addr:0x20 not connected
[ 0.728124] qup_i2c qup_i2c.5: QUP: I2C status flags :0x1363c8, irq:187
[ 0.728155] qup_i2c qup_i2c.5: I2C slave addr:0x20 not connected
[ 0.739081] [cap] CY8C_Smart_V94
[ 0.739569] [cap] config = 3
[ 0.739752] input: cy8c-touchkey as /devices/virtual/input/input3

the PS sensor picked up from first try in all my logs.

99.9% this boot.img is also useless for you.
[G4 Q&A, Help & Troubleshooting] Hotfudge:
My front camera mirror settings have stopped working. Selfies change based on settings, but videos stay in a similar orientation regardless of setting. I haven't factory reset yet, advice?
[XDA Assist] amofush:
I want to download custom rom nought 7.x for my HTC Desire 620g
[XDA Assist] :
Hello,

Thanks for using XDA Assist.

There's no Nougat ROM for your device yet here on XDA.

Please keep an eye here Miscellaneous Android Development for development related to your device.

Also you may try creating your own ROM [GUIDE][COMPLETE] Android ROM Development From Source To End

Regards

Vatsal,

Forum Moderator.
[ZTE Axon 7 Questions & Answers] ramnkc:
Anyone having issues with Waze? I am on A2017G B08.

I can't move on map using my finger to pinch in and out and I can move the map sometimes.... Tried reinstalling it does not work... I use Google maps and it is fine and I don't think its a hardware issues.
[ZTE Axon 7 Questions & Answers] Keiler90:
I use Waze ever day. Had never issues with it.
[ZTE Axon 7 Questions & Answers] Oki:
Do this in the settings > app manager for Waze:

1. Force stop the app.

2. under Storage, Clear cache and then Data

3. Uninstall Waze

4. Reinstall waze from Play Store

This should fix your problem. Let us know.
[ZTE Axon 7 Questions & Answers] ramnkc:
Tried, still having the same issues.... It was ok for the first then I restarted my phone then this issues come back again... I am thinking it was being messed up by the power management.
[ZTE Axon 7 Questions & Answers] Kinanizer:
People have complained about the power management screwing things up before. The power management APK is safe to remove if simply disabling "Smart Power" in the pull down doesn't work for you. Hopefully a fix will be coming in this months update.
[ZTE Axon 7 Questions & Answers] nuserame:
No problems here with Waze with or without power management. Make sure Waze has all the permissions it needs. Or maybe a third-party app is interfering.
[ZTE Axon 7 Questions & Answers] chanter100:
I also have no issues with waze and use it 5 days a week on the job. I have a bone stock axon 7.
[OnePlus 3 Guides, News, & Discussion] Nishidh:
You can enable it just as u enable system ui tuner

I do not know what it does yet

May be something will be added in the next update

But il update as soon as I know
[OnePlus 3 Guides, News, & Discussion] mharis05:
I wish it would have something to do with even more accent colors :fingers-crossed:
[OnePlus 3 Guides, News, & Discussion] Essyy786:
How to enable?
[OnePlus 3 Guides, News, & Discussion] nikhil.agrawal:
I hope its not another bloatware like their own apps. I personally don't like how they are adding more and more of their own apps and replacing google ones.
[OnePlus 3 Guides, News, & Discussion] s.supervisor:
you'll have to enable the developer options

Swipe down the Quick Settings panel and you'll see the settings gear icon at the top of the display. Press and hold this.

and now in settings at the bottom you see laboratory ;)
[OnePlus 3 Guides, News, & Discussion] Essyy786:
I have developer options enabled and when i hold the settings gear icon in the quick settings panel nothing happens
[OnePlus 3 Guides, News, & Discussion] neeraj679:
Thanks I unlocked laboratory but how to unlock system UI tuner
[OnePlus 3 Guides, News, & Discussion] bassgenerator:
Similarly. nothing is going on
[OnePlus 3 Guides, News, & Discussion] liam_davenport:
More bloatware well done 1+ used to love OOS back on 3.2.8
[OnePlus 3 Guides, News, & Discussion] Rajeev:
U need to enable ur animations. Set all animations to 1 and then see..

---------- Post added at 11:27 AM ---------- Previous post was at 11:26 AM ----------

SystemUI tuner is replaced with Laboratory..

But really i miss a useful option called Power Notification. We can control our notification. Anyway wait for updates from OP
[Huawei P9 Lite Questions & Answers] spukispuki:
I have Huawei P9 lite VNS-L31.I have successfully installed emui 5 with nougat,but i want to root it,and in order ti do so i have to flash recovery.But everytime i turn usb debugging ON it turns OFF in few seconds.Any solution?
[Huawei P9 Lite Questions & Answers] :
It's normal. I think.
[Huawei P9 Lite Questions & Answers] spukispuki:
I dont think its normal.In emui 4.1 you turned on USB debugging and it stayed on forever,even if you unplugged usb.Now because i have that problem i cant flash recovery and root my device. :crying:
[Verizon Galaxy S 5 Q&A, Help & Troubleshooting] darktyroll:
Hello 2 all, my mom just received a gift from USA, an Samsung S5 from Verizon. She can use it on Europe, network gsm is working. Still, she cannot use internet on it, i tryed to set up APN manualy, everything is fine, but when i connect to our network Orange, the H sign is there but look like no internet connectivity. Phone cannot connect to internet. I tryed to pun only on GSM and not CDMA, nothing, still no internet connectivity.

Is any way to use this phone in Europe with internet on?

Thanks in advance!
[Huawei P9 Lite Questions & Answers] punteruk:
According to this https://www.androidpit.com/huawei-p9-android-nougat-and-emui-5-0

Have seen a download link too

Anybody tried it and can verify the download is genuine?
[Huawei P9 Lite Questions & Answers] Erazor84:
it's for P9, not p9 lite ;)
[Huawei P9 Lite Questions & Answers] Coolyou:
Why do people post here things from p9
[Windows 10 Mobile] ARDV:
hello

is there A windows 10 FFU package for lumia 925 that i cant flash via Windows device recovery tool?