**** BEGIN LOGGING AT Sun Apr 25 02:59:56 2021 Apr 25 03:55:37 I found GSI for the Ubuntu Port Apr 25 04:02:01 just it does it for 8GB :/ Apr 25 04:27:31 Bro Apr 25 04:27:36 One help Apr 25 04:28:50 I am using Lenovo k8 note mobile … Run on Android operating system currently … But, I want change in Ubuntu OS Apr 25 04:29:15 Please guide to me … how to change Apr 25 04:45:29 [Edit] I am using Lenovo k5 vibe note mobile … Run on Android operating system currently … But, I want change in Ubuntu OS Apr 25 05:18:56 Docs.ubports.org Apr 25 05:20:44 @Vellai1 [I am using Lenovo k5 vibe note mobile … Run on Android operating system currently …], Docs.ubports.com and docs.halium.org Apr 25 05:41:23 Ok Apr 25 05:41:25 Bro Apr 25 08:02:40 Morning Apr 25 08:13:18 KarateMonk was added by: KarateMonk Apr 25 08:37:34 Good morning Apr 25 08:47:12 Good night Apr 25 09:51:50 Morning @Herrie1982 Apr 25 09:58:25 @Theodore [Morning @Herrie1982], Hi, fighting a bit with your kernel in our toolchain ;) Apr 25 09:58:39 I read a lot last night and got scared. Apr 25 09:58:47 I saw a lot of devices got bricked Apr 25 09:58:49 HARD* Apr 25 09:59:04 Well when you have proper partitions you should be OK: https://paste.ubuntu.com/p/GR3HsKKnb5/ Apr 25 09:59:16 Only way to hard brick is to flash a wrong partition somehow Apr 25 09:59:30 Which I managed to do on my Mido on first try :P Apr 25 09:59:41 Oh so that's why there's a lot of bricked message on here Apr 25 10:00:10 (Photo, 545x800) https://irc.ubports.com/Q2eM0QZO.png Apr 25 10:00:46 Yikes the logs don't look good Apr 25 10:01:27 Also just curious did I give you the right partition list? Apr 25 10:05:45 No, I'm trying to find the right command somewhere in my logs Apr 25 10:06:12 I dont have the parition command yet I'll prob need to root again Apr 25 10:06:34 (also my bootloader is really strange sometimes) A/B partitions are weird Apr 25 10:29:10 Seems your having problems with mod names Apr 25 10:32:26 In TWRP can you try: ls -l /dev/block/platform/*/*/by-name Apr 25 10:32:52 In twrp or booted into the OS with root? Apr 25 10:34:06 Well either works I guess Apr 25 10:34:27 I see a ton of stuff being printed Apr 25 10:34:33 boot_a Apr 25 10:34:34 etc... Apr 25 10:34:40 Yeah can you paste it somewhere? Apr 25 10:34:47 yes gimme a sec Apr 25 10:36:10 pastebin.com/SewH3zJu Apr 25 10:45:49 Is it what you were looking for Apr 25 10:47:57 Yes thanks Apr 25 10:48:12 Awesome I hope it works as I see linux being perfect for this device. Apr 25 10:48:42 Why does Halium Reparition the phone? Apr 25 10:50:14 It doesn't, it just indicates which partitions to use Apr 25 10:50:35 so fastboot breaks which the phone go in EDL mode if you have the wrong parititions Apr 25 10:50:46 No Apr 25 10:51:04 Ah alright. Just trying to make sure things will atleast be recovreable Apr 25 10:51:41 May get stuck in fast boot Apr 25 10:51:45 Worst I've had Apr 25 10:51:56 I saw some Razer Phones get into EDL mode Apr 25 10:52:11 the worst brick i've seen on this device is stuck on on bootlogo Apr 25 10:52:21 Well EDL is fixable in general Apr 25 10:52:30 I needed to short some pins on my Mido to get into EDL ;) Apr 25 10:53:07 Mine is not fixable Apr 25 10:53:11 I have no Programmer for it Apr 25 10:53:22 None are available I've tried to get them but no results Apr 25 10:54:49 So if it goes in EDL mode its a hard brick for me Apr 25 10:55:06 Qualcomm one should work? Apr 25 10:55:18 The programmer Apr 25 10:55:19 But you need to have the right USB drivers... Apr 25 10:55:19 ??? Apr 25 10:55:24 Qualcomm tool Apr 25 10:55:28 QPST or whatever it's called Apr 25 10:55:37 Theres no QPST file Apr 25 10:55:48 only flash_all.sh Apr 25 10:58:31 Hopefully we won't go there Apr 25 10:59:45 Well you have A/B as well so that helps Apr 25 10:59:58 how would that help Apr 25 11:00:02 And you can always start with "fastboot boot image" instead of flash ;) Apr 25 11:00:16 So you don't flash boot partition ;) Apr 25 11:00:18 fastboot boot does not work on razer phones Apr 25 11:00:20 they disabled it Apr 25 11:00:24 Ah :S Apr 25 11:00:27 you can only flash it Apr 25 11:00:38 Why would they do that :S Apr 25 11:00:43 idk Apr 25 11:01:47 fastboot flash boot_a recovery.img … fastboot flash boot_b recovery.img Apr 25 11:01:51 This is what we do for TWRP Apr 25 11:02:13 then flash TWRP instal zip Apr 25 11:03:30 You think we could make a NAND copy and make it into a QPST Apr 25 11:08:22 Ah OK Apr 25 11:08:38 Thats why I got a bit of fear with this device Apr 25 11:08:46 Lineage works fine tho Apr 25 11:11:44 As long as we flash the right partitions worst that could happen is a bootloop Apr 25 11:11:57 flash the right partitions? Apr 25 11:12:03 You mean boot and system? Apr 25 11:12:10 Yes Apr 25 11:12:19 Do some mix it up or something Apr 25 11:14:11 (Photo, 744x596) https://irc.ubports.com/fzwvnYm0.png Apr 25 11:14:14 Well that reassures me Apr 25 11:15:59 That's what happened on my mido, I flashed aboot instead of boot or system (don't remember exactly) Apr 25 11:16:04 Anyway kernel built inside LuneOS now! Apr 25 11:16:18 I don't think I can flash aboot Apr 25 11:16:40 https://pastebin.com/pvdCCtxG Apr 25 11:16:43 as you might notice here Apr 25 11:18:33 [Android Bootloader (ABOOT)] … | `-. … | [boot.img] Apr 25 11:18:39 Also the boot.img is below ABOOT Apr 25 11:19:15 OK Apr 25 11:19:21 we should be good Apr 25 11:24:08 Let me see if I can get this LuneOS image to complete building Apr 25 11:24:23 Is it being weird Apr 25 11:27:55 No, I just need to add some device specific configs ;) Apr 25 11:30:41 meta-smartphone and meta-webos-ports need device specific config for build. meta-smartphone is done: https://github.com/Herrie82/meta-smartphone/commit/6e282341f04d23bfb18ebd56d5752faec2c0ec1d Apr 25 11:31:04 sweet Apr 25 11:32:20 For meta-webos-ports I'll need to do something similar to: https://github.com/webOS-ports/meta-webos-ports/commit/a98afa71ebdb66dc17dd1c7f0f67edb0a7282977 Apr 25 11:32:47 what is that Apr 25 11:36:29 It's device specific config used for building a flashable ZIP ;) Apr 25 11:36:39 we need a zip? Apr 25 11:36:59 Well it's a ZIP which contains rootfs, kernel (boot.img) and android bits as well Apr 25 11:37:04 So Halium + LuneOS Apr 25 11:37:08 + kernel Apr 25 11:37:25 Once we get that running well basicly the hard part is gone and no need to worry about bricking again cause Halium is a LXD? Apr 25 11:38:05 or we need to reflash each time we change desktop env Apr 25 11:39:08 @Theodore [or we need to reflash each time we change desktop env], Yes you would, but if 1 works, other ones are easy usually Apr 25 11:39:13 Phone has 1 sim right? Apr 25 11:39:20 1 sim Apr 25 11:39:35 https://www.gsmarena.com/razer_phone-8923.php Apr 25 11:40:37 OK just double checking Apr 25 11:41:18 I'm quite happy to support this community cause well its quite important 1. we have privacy 2. we have linux on our phones Apr 25 11:45:36 Image is building, fingers crossed :P Apr 25 11:45:53 The real finger crossing is flashing it Apr 25 11:46:08 8039 tasks to complete, but it will fly through it ;) Apr 25 11:46:27 It will reuse what it can from other Aarch64 targets Apr 25 11:46:35 Already @ 7200 tasks completed Apr 25 11:46:37 I got a idea how I could flash it and know if boot works? Apr 25 11:46:53 fastboot flash boot img.img && fastboot reboot bootloader Apr 25 11:47:04 if it boots into bootloader nothing bricked Apr 25 11:47:08 Well you can just flash the ZIP from TWRP and keep fingers crossed :p Apr 25 11:47:21 TWRP is sketchy Apr 25 11:47:27 Lineage recovery works better Apr 25 11:48:05 @Herrie1982 [Well you can just flash the ZIP from TWRP and keep fingers crossed :p], how many devices have you ported and how many succeeded and failed Apr 25 11:49:36 Probably around 20, nothing hard bricked except my own Apr 25 11:49:44 About half booted Apr 25 11:49:49 what was the mistake on that one? Apr 25 11:49:56 Flashing aboot Apr 25 11:50:11 I don't even think I got a aboot partition Apr 25 11:50:14 I coulden't find it Apr 25 11:50:22 With the ones not working it was usually some kernel issue somewhere Apr 25 11:50:34 These things are hard to debug without a device at hand Apr 25 11:51:08 oh so it was still booting in fastmode Apr 25 11:51:10 Good :) Apr 25 11:51:25 The only bricks i've heard for razer is unplugging cable while flashing Apr 25 11:51:36 or magisk fucking up badly Apr 25 11:51:44 (Flashing boot into system part) Apr 25 11:53:15 Seems image is almost ready Apr 25 11:53:43 Had issue with WLAN kernel module but we can fix that later Apr 25 11:53:54 As long as we can boot into the devic Apr 25 11:53:59 Yes Apr 25 11:53:59 I'm happy then we can fix issues Apr 25 11:54:09 I saw someone tried to port Postmarket OS for cheryl Apr 25 11:54:21 https://wiki.postmarketos.org/wiki/The-big-list-of-who-has-what-device Apr 25 11:54:28 Razer Phone 1 (razer-cheryl) (Notes: bricked) Apr 25 11:55:18 Its prob the mainline kernel they did Apr 25 11:55:37 How can I make ubuntu touch ...for my redmi note 4 mido.. Apr 25 11:55:48 Is it a/b? Apr 25 11:57:40 I chose the a partitions for now, so boot_a, system_a and userdata Apr 25 11:57:52 @Theodore [Is it a/b?], it's probably not Apr 25 11:58:15 only android 8+ devices can be a/b iirc Apr 25 11:58:19 @Herrie1982 [I chose the a partitions for now, so boot_a, system_a and userdata], That's my current slot Apr 25 11:58:35 @Theodore [Is it a/b?], [Edit] it's probably non-a/b Apr 25 11:58:38 should I switch to B? then flash to A? Apr 25 11:58:57 It will flash to a Apr 25 11:59:16 Image is ready, uploading Apr 25 11:59:16 I'm guessing you did this so it does not brick completely Apr 25 11:59:19 O Apr 25 11:59:42 Well we can only specify 1 partition for boot and system currently so we need to choose ;) Apr 25 11:59:51 ETA 3 mins ;0 Apr 25 12:00:03 Hopefully it will go flawless Apr 25 12:00:10 Getting excited Apr 25 12:03:46 battery is at 100% :D Apr 25 12:04:00 http://build.webos-ports.org/halium-luneos-9.0/luneos-dev-package-cheryl-0-0.zip Apr 25 12:04:04 There you go :) Apr 25 12:04:15 is it the only file i need Apr 25 12:04:18 Yes Apr 25 12:04:20 All is in there Apr 25 12:04:27 If you flash the ZIP it will do all that's needed Apr 25 12:04:28 Vendor? Apr 25 12:04:36 So system, vendor, android bits and kernel Apr 25 12:05:14 so it overwrite the vendor I have rn right? Apr 25 12:05:19 Cause rn that is modified Apr 25 12:06:09 (Photo, 694x662) https://irc.ubports.com/wqM9T0nt.png Apr 25 12:06:11 flashing TWRP Apr 25 12:07:07 No it will mount it inside android I think Apr 25 12:07:25 so I have to flash my stock vendor? Apr 25 12:07:29 If all OK and doesn't bootloop, you shoudl have ADB shell Apr 25 12:07:32 Im now in TWRP Apr 25 12:07:39 No, it will use the one from Halium build Apr 25 12:07:43 And mount it Apr 25 12:07:52 Ok Apr 25 12:07:52 At least I think ;) Apr 25 12:07:55 We'll see Apr 25 12:07:56 So i just flash zip? Apr 25 12:07:59 Yes Apr 25 12:08:07 any wipes required Apr 25 12:09:37 I wiped data and did factory reset so we can have a clean data partition Apr 25 12:10:25 (Photo, 1135x142) https://irc.ubports.com/vUTCwFwc.png Apr 25 12:11:11 Format data to remove encryption Apr 25 12:11:19 Deploying LuneOS Apr 25 12:11:21 If not done yet Apr 25 12:11:27 its done Apr 25 12:11:33 OK Apr 25 12:11:41 my heart is pumping rn Apr 25 12:11:43 LOL Apr 25 12:12:01 Installation completed please reboot Apr 25 12:12:24 want me to wipe data again? Apr 25 12:15:16 No Apr 25 12:15:25 Just reboot Apr 25 12:15:25 So i reboot? Apr 25 12:15:36 We got a boot img Apr 25 12:15:40 Like a boot splash Apr 25 12:15:44 Its boot looping Apr 25 12:15:52 i think? Apr 25 12:15:59 LineageOS Apr 25 12:16:25 I think something did not work Apr 25 12:16:45 abuntu was added by: abuntu Apr 25 12:17:20 how can we know what failed? Apr 25 12:18:11 Hmmz Apr 25 12:18:18 Seem it might have booted b slot? Apr 25 12:18:26 Yeah Apr 25 12:18:37 Let me try fetching the fastboot vars Apr 25 12:19:34 (bootloader) slot-retry-count:b:5 … (bootloader) slot-unbootable:b:no … (bootloader) slot-successful:b:yes … (bootloader) slot-retry-count:a:0 … (bootloader) slot-unbootable:a:no … (bootloader) slot-successful:a:no Apr 25 12:19:56 (bootloader) current-slot:b Apr 25 12:21:06 Current slot should be a Apr 25 12:21:23 so I switch back? Apr 25 12:21:37 Yeah would try Apr 25 12:21:42 a/b always hassle Apr 25 12:22:02 fastboot -aa Apr 25 12:22:05 For slot a Apr 25 12:22:07 (bootloader) current-slot:a … (bootloader) has-slot:boot:yes Apr 25 12:22:13 -ab for b Apr 25 12:22:26 it keeps rebooting Apr 25 12:22:48 I think it switched slot again Apr 25 12:23:02 yap Apr 25 12:23:08 (bootloader) current-slot:b Apr 25 12:23:10 Yeah so something wrong Apr 25 12:23:13 Try get logs Apr 25 12:23:20 How can I? Apr 25 12:23:28 pstore or logcat Apr 25 12:23:34 in twrp? Apr 25 12:23:37 Pstore from twrp Apr 25 12:23:38 on slot a Apr 25 12:23:41 k Apr 25 12:23:48 @Herrie1982 [Pstore from twrp], Yeah Apr 25 12:23:59 @Theodore [on slot a], Slot irrelevant with pstore Apr 25 12:24:06 Oh Apr 25 12:24:22 so i type pstore in terminal Apr 25 12:24:49 cause that gives me su: pstore not found Apr 25 12:25:24 No Apr 25 12:25:35 Folder on phone Apr 25 12:25:54 theres 2 files Apr 25 12:26:06 Pull them Apr 25 12:26:08 Send them here Apr 25 12:26:16 We can figure out what's wrong Apr 25 12:26:30 I pulled both of them to externel SD Apr 25 12:27:24 (Document) https://irc.ubports.com/qxy0i9IJ.txt Apr 25 12:27:28 (Document) https://irc.ubports.com/xafRNFUR.bin Apr 25 12:28:16 already opening thoes file something looks odd Apr 25 12:28:24 [ 3.881138] init: DM_DEV_STATUS failed for system: No such device or address … [ 3.881164] init: DM_DEV_STATUS failed for vroot: No such device or address Apr 25 12:29:51 [ 3.873254] init: Command 'mkdir /dev/stune/nnapi-hal' action=init (/system/etc/init/hw/init.rc:147) took 0ms and failed: mkdir() failed on /dev/stune/nnapi-hal: No space left on device This also looks quite bad. Apr 25 12:30:04 Try using system_a Apr 25 12:30:12 Hmmz weird it dooes that Apr 25 12:30:23 I can't boot in system_A Apr 25 12:30:28 it will switch to system_B Apr 25 12:30:28 I find manually specifying slot can fix weird issues Apr 25 12:30:50 let me see what we do for tissot Apr 25 12:30:53 Atleast the phone didint brick :D Apr 25 12:31:07 It like knew something was wrong and switched to the other slot Apr 25 12:31:26 @Theodore [It like knew something was wrong and switched to the other slot], That's why ab exists Apr 25 12:31:38 ah now I get why it exists. Apr 25 12:31:46 to prevent partition fails Apr 25 12:31:49 In a stock scenario if an update fails, it can boot the old versions Apr 25 12:31:55 [Edit] In a stock scenario if an update fails, it can boot the old version Apr 25 12:33:49 so technically the boot.img works Apr 25 12:33:54 on part b Apr 25 12:33:57 and A Apr 25 12:35:01 Yeah Apr 25 12:35:15 Seems issue might be schedtune defconfig Apr 25 12:35:25 what does that do Apr 25 12:35:36 Some perf tuning I think Apr 25 12:35:48 I'm preparing lunch now, will check in a bit Apr 25 12:35:48 Do we need that? Apr 25 12:35:55 We shouldn't Apr 25 12:36:04 Could be it was enabled in LOS kernel by default Apr 25 12:36:21 what worries me is No space left on device Apr 25 12:36:25 Idk if its normal or not Apr 25 12:36:54 a lot of worring things in that file Apr 25 12:37:22 did you see this btw? Operation not permitted while trying to open /dev/block/by-name/system_a Apr 25 12:39:11 Well for a first try I'm not too worried Apr 25 12:39:18 We get a decent log already Apr 25 12:39:21 That helps Apr 25 12:39:38 I'm quite happy you know your stuff cause I'm now officially lost in the progress Apr 25 12:40:10 @Theodore [I'm quite happy you know your stuff cause I'm now officially lost in the progres …], I get too at times Apr 25 12:40:15 But logs are always good Apr 25 12:40:18 Give clues Apr 25 12:40:29 It seems like boot_a works fine Apr 25 12:40:34 I see no logs about that failing Apr 25 12:41:25 it seems Boot_A loaded then it tried to access system_a and vendor_a which failed and it resulted in it retrying multiple times until giving up and going to Boot_B which booted system_b Apr 25 12:41:30 (Idk if i'm right) Apr 25 13:02:44 Yo herman do you have discord Apr 25 13:06:57 Nope Apr 25 13:07:14 IRC/Telegram/WhatsApp/Signal Apr 25 13:07:19 You got signal Apr 25 13:07:21 I do too! Apr 25 13:07:33 signal is my main app Apr 25 13:07:38 i dont trust google Apr 25 13:08:06 (Sticker, 512x512) https://irc.ubports.com/tMDg0OK3.webp Apr 25 13:08:27 lol Apr 25 13:08:42 (Photo, 689x419) https://irc.ubports.com/0hOMl5nX.png Apr 25 13:08:55 I made a thing for storing our code eventually to maintain it Apr 25 13:14:47 you might wanna maintain your own versions of the device and vendor trees Apr 25 13:14:58 Yeah Apr 25 13:15:03 I just have them on github as ubuntu_vendor_j5xnlte Apr 25 13:17:14 @Theodore [I made a thing for storing our code eventually to maintain it], I can transfer the repos there Apr 25 13:18:50 ;) Apr 25 13:19:05 we have a company called longhorn Apr 25 13:19:15 so we wanna try to make it our first open source project Apr 25 13:19:25 we want to focus on snap dragon devicse Apr 25 13:20:47 @Herrie1982 [I can transfer the repos there], how is the fix going Apr 25 13:38:42 @Theodore [how is the fix going], Just done with lunch, will have a look now Apr 25 13:38:49 sweet Apr 25 13:45:38 Jagaur_87 was added by: Jagaur_87 Apr 25 13:51:08 The console-ramoops actually looks pretty decent for most part Apr 25 13:51:21 So thats a good thing? Apr 25 13:58:58 Yeah, just I'm not sure what's the issue yet Apr 25 13:59:18 Should I try restoring back to stock Apr 25 13:59:20 And trying again Apr 25 13:59:32 Like I had android 11 vendors and stuff Apr 25 13:59:46 I had to re-upgrade cause stock did not boot fine. Apr 25 14:01:45 (Document) https://irc.ubports.com/U8uKwfny.null Apr 25 14:01:46 (Document) https://irc.ubports.com/iFiNT6j0.null Apr 25 14:01:49 I got more logs for you Apr 25 14:04:05 Ah OK Apr 25 14:04:12 Yeah might be worth a retry Apr 25 14:04:16 Ok Apr 25 14:04:18 Reflashing stock Apr 25 14:04:34 I can also create a new boot.img which adds androidboot.selinux=permissive to kernel cmdline Apr 25 14:07:09 What does that do? Apr 25 14:08:57 btw the halium did not modify partitions right? Apr 25 14:10:03 See: https://variwiki.com/index.php?title=Android_Customizing_SePolicy#Bringup_Stages_and_SELinux_Permissive Apr 25 14:10:11 No, we just use the existing partitions normally Apr 25 14:10:24 Basically not enforcing selinux ;) Apr 25 14:10:25 ok cause I'm reflashing without repartition Apr 25 14:10:59 the stock rom is known not to boot sometimes Apr 25 14:11:02 its funny Apr 25 14:11:10 Well I see some audit warning in log Apr 25 14:11:18 what's that? Apr 25 14:11:30 Stuff like: [ 7.286909] type=1400 audit(1619349773.862:4): avc: denied { write } for comm="update_engine" name="tasks" dev="tmpfs" ino=19370 scontext=u:r:update_engine:s0 tcontext=u:object_r:device:s0 tclass=file permissive=0 Apr 25 14:11:48 So its prob what's causing it? Apr 25 14:14:18 I think i'll have to do a full flash Apr 25 14:14:22 stock rom bootlooping Apr 25 14:14:41 OK Apr 25 14:14:49 or it might be that's using B part Apr 25 14:20:01 I did a full repartition Apr 25 14:20:08 fixed problem Apr 25 14:22:23 Prob android 11 does some repartitioning Apr 25 14:22:26 or something like that. Apr 25 14:24:23 Stock just booted should I reinstall TWRP and try again @Herrie1982 Apr 25 14:33:51 Yes try that Apr 25 14:34:03 should I download a lineage build Apr 25 14:34:04 before? Apr 25 14:34:09 (Photo, 781x210) https://irc.ubports.com/QYWwlPey.png Apr 25 14:34:15 Cause this is a very old archive version of it Apr 25 14:34:54 You shouldn't really need that normally, but it doens't hurt either if LOS works ;) Apr 25 14:35:02 Might be a good test Apr 25 14:35:12 without or with? (the good test) Apr 25 14:35:23 I would test LOS 16 first Apr 25 14:35:34 👍 Apr 25 14:35:53 cause we got LOS 16 sources Apr 25 14:35:55 makes sense Apr 25 14:37:02 there's 26 mins left cause their archive server is slow Apr 25 14:40:41 https://www.youtube.com/watch?v=eGjplOtzSFI&t=243s this lavander guy is installing the 16 LOS fisrtt then ubport Apr 25 14:49:32 After flashing what should it Say? Apr 25 14:50:01 New boot image to try if current one doesn't work: http://build.webos-ports.org/halium-luneos-9.0/Image.gz-dtb--4.4.185%2Bgitr0%2B4b92e45fd9-r0-cheryl-0-0.fastboot Apr 25 14:50:16 .fastboot?? Apr 25 14:50:19 is it a .img Apr 25 14:50:22 Yeah ;) Apr 25 14:50:27 It should be Apr 25 14:50:29 what changed Apr 25 14:52:12 TWRP flashed succesfully Apr 25 14:55:33 Well I just made the selinux permissive Apr 25 14:55:38 That's it Apr 25 14:55:45 Should I flash the selinux one Apr 25 14:55:51 or the old one Apr 25 14:56:31 Well you can first try the old one (just do the ZIP) Apr 25 14:56:50 waiting for lineage to finish rn Apr 25 14:57:01 If it doesn't work, you can do "fastboot flash boot_a Image.gz-dtb--4.4.185+gitr0+4b92e45fd9-r0-cheryl-0-0.fastboot" Apr 25 14:57:27 it has a weird file extension Apr 25 14:57:32 i never seen it before Apr 25 14:58:43 flashing step 2/2 rn for LOS Apr 25 14:58:57 it's flashing to slot B is that fine? Apr 25 14:59:31 Yeah that's fine in general Apr 25 14:59:44 Although you could flash to both A & B Apr 25 14:59:44 (in general) please elaborate lol Apr 25 14:59:53 So you have LOS on both Apr 25 14:59:57 But first try if it works on B Apr 25 15:00:05 with stock on A? Apr 25 15:00:09 Yeah Apr 25 15:00:11 For now Apr 25 15:00:12 ok Apr 25 15:00:17 If LOS boots on B, I would flash it to A Apr 25 15:00:26 I'm not really sure either to be honest, trial and error a bit Apr 25 15:00:40 I think A/B is really fussy Apr 25 15:00:47 it wants something to be done 1 way. Apr 25 15:00:57 Failed to unmount /vendor device or resource busy? Apr 25 15:02:06 is that bad? Apr 25 15:02:15 did not happen on LOS 19 Apr 25 15:02:18 18& Apr 25 15:03:37 cheryl:/ # umount /vendor … umount: /vendor: Device or resource busy Apr 25 15:03:45 yeah something is wrong Apr 25 15:06:03 Ooh the fun stuff sometimes :S Apr 25 15:06:12 How would I go on fixing that Apr 25 15:06:15 DO i just reboot to system? Apr 25 15:07:56 Wait flashing again fixed it Apr 25 15:08:01 Now it says reboot? Apr 25 15:08:48 graphical glitches Apr 25 15:09:33 that was scary. Weird static Apr 25 15:10:43 it booted into LOS recovery so I will try to reflash LOS 16 Apr 25 15:10:53 OK Apr 25 15:11:00 This is LOS? Apr 25 15:11:03 Yeah Apr 25 15:11:10 it had weird lines and static and artifacting Apr 25 15:11:26 (mostlikely vendor) Apr 25 15:13:59 yeah boot animation is messed up Apr 25 15:14:45 you see its booting tho cause the lines move Apr 25 15:16:19 Well boot animation isn't end of the world normally Apr 25 15:16:22 If rest of GUI is OK Apr 25 15:18:16 the rest of GUI is corrupted Apr 25 15:18:25 i can still touch device etc... Apr 25 15:18:52 Should I try Ressurection Remix 9 Apr 25 15:20:53 nvm its android 10 Apr 25 15:21:02 idk what to do lol Apr 25 15:21:17 Seems like some corrupt vendor Apr 25 15:21:32 How does one even fix that Apr 25 15:21:57 fastboot? Apr 25 15:22:53 I guess you could, not sure, never had to do it Apr 25 15:23:38 Seems so: fastboot flash vendor .img Apr 25 15:24:11 fastboot flash vendor_a vendor.img Apr 25 15:24:16 fastboot flash vendor_b vendor.img Apr 25 15:25:17 Vendor_A succeded Apr 25 15:26:06 Now I try booting in LOS or reflashing it? Apr 25 15:29:26 Try booting just Apr 25 15:29:31 Should work I'd day Apr 25 15:29:32 say Apr 25 15:30:01 nope\ Apr 25 15:30:15 i think it's prob LOS Apr 25 15:30:48 (bootloader) current-slot:b … (bootloader) has-slot:boot:yes … (bootloader) slot-retry-count:b:5 … (bootloader) slot-unbootable:b:no … (bootloader) slot-successful:b:yes … (bootloader) slot-retry-count:a:0 … (bootloader) slot-unbootable:a:no … (bootloader) slot-successful:a:no Apr 25 15:32:48 That's the version I was using lineage-16.0-20200322-nightly-cheryl Apr 25 15:33:08 i'm trying lineage-16.0-20200325-nightly-cheryl Apr 25 15:48:56 Flashing... Apr 25 15:51:55 still has graphical glitches Apr 25 15:58:38 Well you could try to flash LuneOS Apr 25 15:58:44 It might not be fatal in the end Apr 25 15:58:54 i'm flashing Lineage 18 rn Apr 25 15:59:02 I would be happy if we get to graphical glitches already :P Apr 25 15:59:18 I think my TWRP version might be too new Apr 25 15:59:20 or something Apr 25 16:00:22 That's possible too Apr 25 16:00:30 vendor fails again Apr 25 16:00:35 I'm using 3.5.0_9 Apr 25 16:00:40 For most targets Apr 25 16:00:44 The vendor part is fucked i think Apr 25 16:00:53 Stock rom time? Apr 25 16:01:54 Yeah why not Apr 25 16:02:02 I'm flashing Mido here with 4.9 kernel and Halium 9.0 Apr 25 16:02:04 See how it behaves Apr 25 16:02:07 I really don't know what happend to the kernel Apr 25 16:02:21 i mean vendor Apr 25 16:05:51 I really hope we can get it booting Apr 25 16:07:42 Stock boots fine now Apr 25 16:07:54 Should I flash it ontop of the stock? Apr 25 16:08:01 Yeah that should work as well Apr 25 16:08:09 Let's try Apr 25 16:08:15 Cause stock is 9.0 Apr 25 16:15:16 is it luneos-dev-0.0 Apr 25 16:18:51 Did not work Apr 25 16:18:56 still bootlooping (SE Linux?) Apr 25 16:19:17 Any logs? Apr 25 16:19:29 dumping rn Apr 25 16:20:41 pstore has no logs Apr 25 16:21:29 (Document) https://irc.ubports.com/R84NFEIG.null Apr 25 16:21:36 (Document) https://irc.ubports.com/RcYDOVjQ.null Apr 25 16:21:38 That's all I have Apr 25 16:22:40 You sure you tried to boot A? Apr 25 16:22:45 i can try again Apr 25 16:23:06 im on A now Apr 25 16:23:10 Sometimes it takes a few tries to get it Apr 25 16:23:26 YOu could also try to do "adb shell" before it reboots Apr 25 16:23:33 By the looks of it, it was running adbd Apr 25 16:25:11 (bootloader) current-slot:a … (bootloader) has-slot:boot:yes … (bootloader) slot-retry-count:b:0 … (bootloader) slot-unbootable:b:no … (bootloader) slot-successful:b:no … (bootloader) slot-retry-count:a:0 … (bootloader) slot-unbootable:a:yes … (bootloader) slot-successful:a:no Apr 25 16:25:40 booting recovery on B Apr 25 16:26:06 pstore is empty Apr 25 16:26:50 [ 9.752616] audit: type=1400 audit(5075941.089:3): avc: denied { setcheckreqprot } for pid=1 comm="init" scontext=u:r:init:s0 tcontext=u:object_r:kernel:s0 tclass=security permissive=1 Apr 25 16:26:57 This line gets me curious Apr 25 16:27:16 The A partition does not have a recovery also Apr 25 16:27:19 Well I could disable audit in defconfig I guess Apr 25 16:27:26 it just does not boot into the recovery A Apr 25 16:27:40 I'm not sure what the issue is Apr 25 16:30:05 6.263365] Alternate GPT is invalid, using primary GPT. … [ 6.263423] sde: sde1 sde2 sde3 sde4 sde5 sde6 sde7 sde8 sde9 sde10 sde11 sde12 sde13 sde14 sde15 sde16 sde17 sde18 sde19 sde20 sde21 sde22 sde23 sde24 sde25 sde26 sde27 sde28 sde29 sde30 sde31 sde32 sde33 sde34 sde35 sde36 sde37 sde38 sde39 sde40 sde41 sde42 sde43 sde44 sde45 Apr 25 16:30:05 sde46 sde47 sde48 Apr 25 16:30:14 what does that mean? Apr 25 16:32:15 huhhhhh Apr 25 16:33:20 Weird Apr 25 16:33:27 I see that lune OS is installed at data/luneos Apr 25 16:33:31 Yes Apr 25 16:33:32 with android,bin boot dev Apr 25 16:33:33 home Apr 25 16:33:50 is the system part broken? Apr 25 16:34:56 vendor has a folder with lib64 Apr 25 16:35:03 and it includes so files Apr 25 16:36:29 lrwxrwxrwx 1 root root 38 1970-02-28 18:14 system -> /dev/block/bootdevice/by-name/system_b … lrwxrwxrwx 1 root root 15 1970-02-28 18:06 system_a -> /dev/block/sda6 … lrwxrwxrwx 1 root root 15 1970-02-28 18:06 system_b -> /dev/block/sda8 Apr 25 16:36:32 I would say there's something off with your partitions somehow Apr 25 16:36:50 Well I specified system_a I think which should be /dev/block/sda6 Apr 25 16:36:52 but I just came from stock wut? Apr 25 16:37:20 how does stock break partitions Apr 25 16:38:03 Yes: sda6: https://github.com/Herrie82/meta-smartphone/blob/herrie/cheryl-9.0/meta-razer/recipes-core/initrdscripts/initramfs-scripts-halium/cheryl/machine.conf#L2 Apr 25 16:38:30 weird why would it not boot then Apr 25 16:41:37 repartioning rn Apr 25 16:54:12 @Herrie1982 Should we make a unofficial Lineage 16 build then flash that. Then the LuneOS Apr 25 16:54:37 Well it shouldn't really matter to be honest Apr 25 16:54:54 so its a problem with lune? Apr 25 16:58:27 wait I just realised Apr 25 16:58:36 on the BOOTLOADER Page it says SECURE BOOT - yes Apr 25 16:58:40 would that cause it? Apr 25 16:58:51 DEVICE STATE - unlocked Apr 25 16:59:03 Varient - MSM UFS Apr 25 16:59:37 Not sure to be honest ;) Apr 25 16:59:59 I'm quite sad. Apr 25 17:00:10 maybe we should try Halium? Apr 25 17:00:21 I found one of the GSis for it Apr 25 17:00:38 (Photo, 717x57) https://irc.ubports.com/rKAxTOix.png Apr 25 17:03:00 Yes Apr 25 17:03:05 I would try Apr 25 17:03:15 I just don't have the halium boot img Apr 25 17:03:51 https://github.com/ubports/porting-notes/wiki/Generic-system-image-(GSI) Apr 25 17:05:24 also would Halium 7 work? Apr 25 17:09:50 Well it might have the same issue ;) Apr 25 17:10:05 this device is so weird... Apr 25 17:11:04 i guess my dream of running Linux on my phone is not too good lol Apr 25 17:11:15 Well it could work Apr 25 17:11:24 I'd need some help from Tofe maybe when he's around Apr 25 17:11:28 It could once we figure out what's wrong withut bricking the device Apr 25 17:11:31 He knows a lot more low-level stuff ;) Apr 25 17:11:41 I can just fiddle a bit with bits :P Apr 25 17:11:43 I saw the ether device running Ubuntu Apr 25 17:11:48 And quickly mock stuff together Apr 25 17:11:51 And the razer cheryl is almost the same phone Apr 25 17:12:08 I'll try building a lineage 16 binary for fun Apr 25 17:12:11 while I wait Apr 25 17:12:20 Well I'm fighting with Mido with 4.9 kernel here :P Apr 25 17:12:30 Same issues lol? Apr 25 17:12:39 dw i got a lineage build server called losdragon Apr 25 17:13:06 omg i just found a Samsung s5 motherboard with nothing attached to it lol Apr 25 17:13:09 (in a bin) Apr 25 17:13:49 Well I got LXC container running, but no logcat ;) Apr 25 17:13:56 So cannot really debug much so far Apr 25 17:15:59 If it gets to a point we really can't get it running I'd prob 1. Switch phone buy a new one or 2. Try to pay someone to use their genius things to make it work. Apr 25 17:17:29 Well it's really not that far off to be honest Apr 25 17:17:41 The status we got initially was pretty good already Apr 25 17:17:54 That was on android 11 Apr 25 17:18:09 on android 9 nothing happens Apr 25 17:18:30 refuses to do anything Apr 25 17:19:36 like the goal was running linux inexpensively but I guess not going to happen I'll have to spend like 900$ on a pinephone Apr 25 17:24:07 Pinephone is not $900 ;) Apr 25 17:24:16 There are plenty of options with pmOS as well Apr 25 17:24:20 well their not cheap for performance they off Apr 25 17:24:22 offer* Apr 25 17:25:09 @Theodore: it's 150$, everything is open and it's produced in small batches, it makes the price go up Apr 25 17:26:17 Ahh I would buy it but cant rn Apr 25 17:26:23 I see its on sale Apr 25 17:42:28 I was able to restore my phone to a fully working order with LOS 18.1 with both slot working Apr 25 17:47:14 https://www.ebay.ca/itm/174111161664?chn=ps&norover=1&mkevt=1&mkrid=706-89093-2056-0&mkcid=2&itemid=174111161664&targetid=884345177219&device=c&mktype=pla&googleloc=1002053&poi=&campaignid=9557028239&mkgroupid=97795562386&rlsatarget=pla-884345177219&abcId=1063836&merchantid=138569652&gclid=Cj0KCQjwppSEBhCGARIsANIs4p6w0mbX_7Es_7-eZWH11SNC Apr 25 17:47:15 C4GEAWpNlplvFf1Qf125d18kw5a9sfcaApXZEALw_wcB I foudn this. Apr 25 17:47:17 if i wanted to go that route Apr 25 17:53:24 Found this also. which might give me hope in the future https://twitter.com/Khode_Erfan/status/1353296176649539584/photo/1 Apr 25 18:02:59 @Theodore [Found this also. which might give me hope in the future https://twitter.com/Khod …], Yes … Halium 10 is close:) Apr 25 18:03:20 Well that would really help in my case prob cause 16 LOS got removed for my device Apr 25 18:03:27 And i have no luck booting on the Cheryl Apr 25 18:25:29 One of the things that makes it hard to develop for this device "Unlike the Pixel devices, Razer has disabled fastboot boot so there is no way to temporarily boot TWRP to perform an installation." Apr 25 18:27:43 @Theodore [Well that would really help in my case prob cause 16 LOS got removed for my devi …], u should still have the sources Apr 25 18:27:54 I do have sources Apr 25 18:27:55 i guess mike is the lineage maintainer Apr 25 18:28:01 I got the 16, 17,18 sources Apr 25 18:28:03 his trees are very nice Apr 25 18:28:22 if I share you a log Apr 25 18:28:29 could you help me figure out what's happening here Apr 25 18:28:40 (Document) https://irc.ubports.com/05uh0Q2H.bin Apr 25 18:29:51 (Document) https://irc.ubports.com/yvA3SLmA.txt Apr 25 18:30:28 halium isn't booted here Apr 25 18:30:40 well that explains a lot. Apr 25 18:30:56 I need a android 9 OS installed right for halium to work? Apr 25 18:31:06 I currently have 11 installed. Apr 25 18:31:12 show me your kernel source Apr 25 18:31:20 https://github.com/Freehorn-GNU-Linux Apr 25 18:31:21 @Theodore [I need a android 9 OS installed right for halium to work?], yes … need 9 vendor Apr 25 18:31:41 Thoes are @Herrie1982's vendors and stuff Apr 25 18:31:42 that he patches Apr 25 18:31:49 add git history Apr 25 18:31:55 sec Apr 25 18:33:57 https://github.com/lynxodore Apr 25 18:34:01 Check the 2 repos Apr 25 18:42:06 @erfanoabdi [add git history], as I think what is happening is we tried to boot LuneOS into a 11 vendor from LOS 11 and it failed. Apr 25 18:42:35 So to fix that we should prob go make a LOS 9 vendor with a system too. then try to build an image for it. Apr 25 18:45:37 @Theodore [So to fix that we should prob go make a LOS 9 vendor with a system too. then try …], Well I build LOS 16 with 9 vendor Apr 25 18:45:43 That should work Apr 25 18:45:50 I am already working on that rn Apr 25 18:45:54 Very slow Apr 25 18:45:57 I did that already Apr 25 18:46:00 Oh LOL Apr 25 18:46:03 That's what I did yesterday Apr 25 18:46:22 So you got the cheryl recovery + zip Apr 25 18:46:22 for los 16? Apr 25 18:46:49 Well I don't have the proper halium-boot for Cheryl, because I don't use it @ LuneOS Apr 25 18:46:51 But rest is there Apr 25 18:46:55 system.img and vendor.img Apr 25 18:47:09 Building halium should be the same right? Apr 25 18:47:13 Yes Apr 25 18:52:23 what vendors did you use Apr 25 18:52:30 like the muppets? Apr 25 19:00:24 Yes Apr 25 19:00:32 Nice Apr 25 19:04:49 you mind uploading your LOS 16 for cheryl? Apr 25 19:04:54 So I can try it out? Apr 25 19:07:23 I didn't build full LOS Apr 25 19:07:29 Ah Apr 25 19:07:34 Just the minimal Halium build Apr 25 19:07:43 What does that do? Apr 25 19:07:48 is it like a android Apr 25 19:13:26 Yes the one we start inside of LXC container Apr 25 19:13:34 So OS can talk to hardware via Android side Apr 25 19:13:40 So that one should boot then? Apr 25 19:13:44 Without vendors Apr 25 19:13:51 Well it has a vendor.img too Apr 25 19:14:05 that was in the luneos right? Apr 25 19:14:16 cause i find it weird it did not work Apr 25 19:15:49 Well there's also some config on LuneOS side that could be wrong, but it looked OK based on your logs Apr 25 19:16:05 im trying to install LOS again Apr 25 19:16:52 Yeah LOS does graphical bugs Apr 25 19:17:26 no fix lol Apr 25 19:18:35 Hmmz Apr 25 19:18:47 im trying to install LuneOS on top Apr 25 19:19:42 deploying Apr 25 19:21:35 maybe it will work who knows Apr 25 19:23:29 Yeah it might Apr 25 19:23:37 Or at least some logs would be helpful Apr 25 19:23:44 (bootloader) current-slot:a … (bootloader) has-slot:boot:yes … (bootloader) slot-retry-count:b:6 … (bootloader) slot-unbootable:b:no … (bootloader) slot-successful:b:yes … (bootloader) slot-retry-count:a:5 … (bootloader) slot-unbootable:a:no … (bootloader) slot-successful:a:yes Apr 25 19:23:59 not booting bootlooping Apr 25 19:25:12 cheryl:/ # ls /sys … block bus class dev devices firmware fs kernel module power … cheryl:/ # ls /sys/fs … cgroup ext4 f2fs fuse pstore selinux … cheryl:/ # ls /sys/fs/pstore/ Apr 25 19:25:12 … cheryl:/ # Apr 25 19:25:22 nothing Apr 25 19:27:13 what in the world? Apr 25 19:27:19 It's booting LOS now Apr 25 19:28:19 Well bootloop, you should be able to pull a log from pstore again on next boot Apr 25 19:29:20 cheryl:/ # ls /sys/fs/pstore/ Apr 25 19:29:21 empty Apr 25 19:53:51 Hmmz Apr 25 19:54:30 its prob impossible to boot Apr 25 19:54:57 I would try to fastboot boot, the .fastboot that I linked Apr 25 19:55:05 Then when it reboots, directly to recovery and try to pull Apr 25 19:55:16 With directly I mean hold the button so it goes into recovery Apr 25 19:55:39 only flash the .fastboot Apr 25 19:55:50 or flash it with the luneos Apr 25 19:58:17 Well you flashed the LuneOS ZIP Apr 25 19:58:26 This would just be a new kernel that you flash and boot Apr 25 19:58:29 Removed it Apr 25 19:58:33 I flashed LOS again Apr 25 20:02:28 bootlooping Apr 25 20:02:49 cheryl:/ # ls /sys/fs/pstore/ … cheryl:/ # Apr 25 20:03:31 hı. how fix this problem? https://github.com/Halium/projectmanagement/issues/218#issuecomment-684076809 Apr 25 20:12:12 @Herrie1982 [Well you flashed the LuneOS ZIP], I think I'll wait for Halium 10 unless we get a fix made up. Apr 25 20:12:17 Was fun experimenting tho Apr 25 20:13:46 Yeah it's hard for me to help when I don't have a device at hand Apr 25 20:13:49 It's hit & miss Apr 25 20:13:54 Even with a device ;) Apr 25 20:14:03 Anyway the work is out there Apr 25 20:14:04 I have the device but i'm completely lost Apr 25 20:14:06 Easy to pick up agian Apr 25 20:14:12 Yeah I got the repos saved Apr 25 20:14:12 At any point Apr 25 20:14:13 imgs too Apr 25 20:14:17 Same here Apr 25 20:14:29 I'll prob just end up buying a compatible phoen Apr 25 20:14:30 LuneOS can be fully built from scratch in general ;) Apr 25 20:14:40 from no vendor? Apr 25 20:14:42 No nothing? Apr 25 20:14:45 I'll merge the work in regular branches Apr 25 20:14:54 Well you need LOS & Vendor Apr 25 20:14:58 ah Apr 25 20:15:04 BUt I built those already Apr 25 20:15:06 So those are on the build server Apr 25 20:15:10 Rest is all from source Apr 25 20:15:30 I've heard bootloader on razer phone is weird and complicated Apr 25 20:15:41 it acts weird with boot imgs Apr 25 20:16:35 even lineage os is difficult to flash Apr 25 20:17:00 Nord n10 Apr 25 20:17:11 Is that a good device or what? Apr 25 20:17:24 Sorry that was supposed to be a search 😊 **** ENDING LOGGING AT Mon Apr 26 03:00:18 2021