yashsingh1/xdaforums huggingface dataset:
[Android Q&A, Help & Troubleshooting] pndwal:
Thanks - Working well as usual. :)

As to earlier question:

-Yes, this is unusual and concerning.

[MENTION=4479868]desalesouche[/MENTION] still hasn't been active on XDA since 17/11/2018. Hope he's OK. He's almost singlehandedly responsible for our Y550 LOS unofficial Cherry port. :( [- France Telecom (Orange) may know something more.]

[MENTION=7866480]fwiep[/MENTION], you now seem to be our only current source for updates! Many thanks for filling this gap. PW.
[Android Q&A, Help & Troubleshooting] GotoDengo:
Thanks again for the update. All OK so far after dirty flash. :)
[Android Q&A, Help & Troubleshooting] pndwal:
Wow! Hotspot bug is cured with this build. Thanks [MENTION=7866480]fwiep[/MENTION].

Seems we're still getting a few bug fixes with LOS14.1 updates. :)

I wonder if any other known bugs have now been fixed. PW.
[Android Q&A, Help & Troubleshooting] fwiep:
You're welcome :)

The real thanks go to the LineageOS developers. I'm just the one putting the pieces together on a regular basis.

Kind regards,

FWieP
[Android Q&A, Help & Troubleshooting] pndwal:
... And delivering them - an essential service. :)

You're really to our devices what the support fleet is to a battleship or what the shuttle was to the space station - we'd never receive the needed upgrades and refurbs without you, especially now that we're down to just one shuttle.

Failing some Russian Dev delivering our payloads, I guess the time has to come when Y550 will be marooned, one more piece of space junk, a wreck on the seabed of technology, the useless legacy of progress, a distant memory from yesteryear...

But what an example of a workhorse she will have been! What a noble vessel she was! And how honourable an enterprise was that of keeping the Good Ship Y550 afloat and that of supporting every adventurer who sailed her, especially those who maintained her and navigated treacherous reaches long after her founders had abandoned her, after her glory days had faded and the rising hulks of progress had overtaken...

And the veterans of this voyage salute the delivery vessel just as they do the architects who have refurbished our humble boat and made her the worthy ship that she is, able to withstand the storms of time and to deliver us to destinations well beyond those envisaged...

Yes, please take a bow. You won't be getting a medal, but we are thankful to the stalwarts who weather the tests of time and remain aboard with us. And we remember the mighty who have fallen...

Again, many thanks [MENTION=7866480]fwiep[/MENTION]. (And stay humble!) Kind regards, PW
[Android Q&A, Help & Troubleshooting] pndwal:
Things I like about / use with LOS14.1:

"cLock" widget with OpenWeatherMap as Weather Provider. (Replace original clock with this, install OpenWeatherMapWeatherProvider.apk from https://download.lineageos.org/extras, sign up and get free API key and enter in OpenWeatherMap settings, customise font, colours, screen position & size, location etc. Geolocation is default.)

Adopted SD storage with Force Allow Apps on External enabled in Developer Options.

[Some apps (especially those whose functions require root permission) may suffer reduced functionality if installed on SD, and should be moved after consideration, or moved back to internal. Eg. ES file Explorer - if you use it's 'root explorer'. - It will lose root permission (fails initial test) and won't allow root / system level access when on SD card.]

Smart Launcher 3 (free, but I paid for Pro version - I didn't like the later version 5) as I like homescreen layout, customisability (think I may have coined that one), and especially self sorting app draws (six basic categories, can add more, launcher checks database when installing any app for category) which makes apps simple to find when you have too many.

Settings, Buttons, Long Press for Torch

Settings, Status bar, Clock - Show Seconds

Settings, Status bar, Network traffic monitor, Display mode, Upload and download. PW
[Android Q&A, Help & Troubleshooting] stephendt0:
Error 7 when installing LineageOS update on Y550-02. Is there an updated TWRP? The old 3.1.1.0 version caused my system to no longer boot because my system has adoptable storage :(
[Android Q&A, Help & Troubleshooting] pndwal:
See my post #6470 (last page) re official 3.2.3.0, unofficial 3.1.1.0, and errors flashing on L02, L03.

You'll need unofficial 3.1.1.0 to flash ROM on L02, L03 though, but my system still boots fine with either TWRP (- Just can't see adoptive in unofficial TWRP.) See methods below:

-From post #6343, were I posted a number of other tips re adoptive storage etc also. Hope it helps, PW
[Android Q&A, Help & Troubleshooting] stephendt0:
I had no other choice but to factory reset my device to finish updating my ROM. Very annoying but not much you can do when TWRP isn't working properly.
[Android Q&A, Help & Troubleshooting] pndwal:
Is that 3.1.1.0, Dec. 16 2017 by [MENTION=4479868]desalesouche[/MENTION] I linked? I've had no problems dirty flashing my L02 with this. And encryption key is preserved and adopted storage unaffected. :confused:

Nb. Even with the same version number, two TWRPs can vary a lot as devs can include differing features, different hardware blobs etc, The version number shown in loaded TWRP only relates to base TWRP version used. So please ensure you have the unofficial 3.1.1.0 I linked. (Official one with same ver. number will give error 7 when flashing ROM on L02, L03.) PW

---------- Post added at 05:22 PM ---------- Previous post was at 04:47 PM ----------

@stephendt0:

Check "Development" thread, Post #2 maintained regularly by [MENTION=6726815]Saint_13[/MENTION], for all Y550 related files and tips:

https://xdaforums.com/android/development/huawei-y550-development-t3425524

[Tip: view this post post in browser. XDA Labs app doesn't handle formatting properly, and makes it hard to navigate.]

You'll find several older TWRPs there too.

[MENTION=6726815]Saint_13[/MENTION]:

Latest official TWRP is 3.2.3-0, (https://dl.twrp.me/y550/) by [MENTION=6829336]Hacker432[/MENTION].

Latest unofficial is 3.1.1.0, Dec. 16 2017 (https://xdaforums.com/showpost.php?p=74856798&postcount=5850) by [MENTION=4479868]desalesouche[/MENTION].

It may be a good idea update development thread post #2 to include these, especially latest unofficial TWRP which may now be essential for ROM flashing on L02, L03. Thanks, PW.
[Android Q&A, Help & Troubleshooting] Saint_13:
[MENTION=7550078]pndwal[/MENTION]

Done! :good:
[Android Q&A, Help & Troubleshooting] alexa10:
can enable fast charging in lineage os 14.1?
[Android Q&A, Help & Troubleshooting] pndwal:
Don't think we have Fast charge (or Quick Charge for Qualcomm chip enabled chargers) implemented now. Recent ROMs lack kernel support for quick charge.

Snapdragon 410 supports Qualcomm Quick Charge 2.0, enabling up to 24 watt charging over micro USB. Hacker and Nato had Quick Charge kernel support for y550 in previous ROMs (eg Soviet bastard ROM).

You could try Magisk modules for fastcharge, but I don't think they'll have an effect without kernel support. PW
[Android Q&A, Help & Troubleshooting] kekkkko:
android oreo?
[Android Q&A, Help & Troubleshooting] pndwal:
Post #s 6452, 6467. PW
[Android Q&A, Help & Troubleshooting] fwiep:
7.1.2 update

Thanks to the LineageOS-developers and [MENTION=4479868]desalesouche[/MENTION], this is today's build containing the April-2019 security patches.

Recent changes: LineageOS 14.1

Kernel: https://github.com/HUAWEI-Y550-Y635/android_kernel_huawei_msm8916/commits/los-14.1

Update: download links have been removed. Please use the most recent ROM, see this link:

Unofficial LineageOS 14.1 (Android 7.1.2) ROM with June-2020 security patches

Known bugs:

- the WiFi MAC-address sometimes switches between a Huawei-prefix 68:a0:f6 and an Airgo-prefix 00:0a:f5 on reboot

- the setting to disable battery optimization for an app does not survive a reboot (for me, WhatsApp should not be optimized to enable backup over WiFi at night)

Note: I do not use the Y550 as my primary device anymore, but will keep them around for updating as long as possible.

Kind regards,

FWieP
[Android Q&A, Help & Troubleshooting] pndwal:
That's much appreciated.

Just wondering if you could give an outline of how you update our unofficial cherry Y550 LOS ROM with latest sources. (Setup needed, software, links, settings, traps for young players, traps for older players, etc. - I was going to say 'brief', but perhaps it can't be.) Then one of the old brigade could give it a whirl. - I'd like to try as soon as I'm not so pressed for time.

As always, many thanks for your support for Y550 users to date. - Love your work.

What's your new device?

Kind regards, PW
[Android Q&A, Help & Troubleshooting] fwiep:
I am planning to write a step-by-step documentation for setting up the build environment, things I ran into, how I do things at the moment when building and posting to this forum. Most of the info comes from LineageOS itself, XDA and all across the rest of the internet. But (also for me) it is important to have it all in one place. I wrote several (Dutch) posts in my weblog over the years, but they are somewhat out of date and: not in one place anymore :)

Please bear with me, and provide helpful feedback when the docs are there. I would like for them to be useful for both beginners and advanced users. (considering myself to be an intermediate). It will probably take about a week or so.

A Motorola moto G6 (ali). It has no official LineageOS support yet, but we're sailing on the wings of the manufacturer (with Android 8.0.0 and security patches of January-2019). I hope, when the warranty period is over, some (official) developer will have gotten a port of Lineage to this device working properly. Who knows, that developer may even be me :P (In Germany, they call such a statement "Wunschdenken", I don't know the English word for it).

Kind regards,

FWieP
[Android Q&A, Help & Troubleshooting] pndwal:
Sounds great! Please take your time. That will be another way your talent will benefit users.

I like to post on XDA for my own future reference also. Its the best place for ones own notes.

Yes, Moto is generally well supported by devs so probably a good choice.

With 8.0, may also be easy to get Project Treble support, then you'll be away laughing...

'Wishful Thinking', but I don't think that's applicable. Judging by your exploits with Y550 you could easily be that dev. You just need to overcome any obstacles; - I recommend you tackle them one at a time... :laugh:

Kind regards, PW
[Android Q&A, Help & Troubleshooting] pndwal:
Just flashed, and working well as usual.

Had a problem flashing with Magisk SU this time (probably due to changes in Magisk SU itself). LOS14.1 ROM flash kept ending with errors.

Solution for me was to flash latest Magisk uninstaller, flash Rom and latest Gapps, flash Magisk 18.1, boot and find and reinstall Magisk modules in Downloads folder.

Possibly simply reflashing Magisk 18.1 after ROM would have fixed ROM installation as errors occurred in Magisk (SU) boot.img setup stage after system seemed to have finished flashing successfully, but I didn't try this. Someone else using Magisk SU may like to.

Thanks, PW
[Android Q&A, Help & Troubleshooting] GotoDengo:
Thanks again for your efforts.

I look forward to your documentation, I am dying to try building an update myself.
[Android Q&A, Help & Troubleshooting] Osman Khafan:
Hi, time you good, please link to download custom ROM r remix 7.1.2 got for me to send thanks
[Android Q&A, Help & Troubleshooting] pndwal:
Latest Y550 RR ROM was [MENTION=6864096]NATO66613[/MENTION]'s RR of 03-08-2017. See post #5500 here.

Unfortunately download link is broken. [MENTION=6864096]NATO66613[/MENTION] may be able to repost it, or someone who had it. ([MENTION=7866480]fwiep[/MENTION]? [MENTION=6726815]Saint_13[/MENTION]?)

Other than that, we have old RR, Jan 2017, 7.1.1 from Nato66613 - see post #4579 here. PW.
[Android Q&A, Help & Troubleshooting] NATO66613:
Not sure I need to check my drives
[Android Q&A, Help & Troubleshooting] pndwal:
Thanks. That would be one unique ROM worth resurrecting / reintroducing to the mix. PW.
[Android Q&A, Help & Troubleshooting] fwiep:
Well, here it is: a tutorial on how to build Android 7.1.2 for Y550 devices. Thanks to [MENTION=7550078]pndwal[/MENTION] for proofreading and feedback. It's a standalone HTML file which should be readable to anyone.

https://fwiep.nl/y550/how-to-build-7.1.2.html

Please DO try this at home and feedback. :)

Kind regards,

FWieP
[Android Q&A, Help & Troubleshooting] pndwal:
Frans-Willem, you're a legend!

This is a great tutorial, and bound to work as you have have tested each step until a ROM is produced without errors. Truely a 'labour of love' for Y550 community.

"Please DO try this at home and feedback. :) "

We're privileged to have such keen help with Y550 and this is way beyond my expectations.

I fear others (like [MENTION=9334953]GotoDengo[/MENTION]) will trial this before I do as I still have serious time constraints. Very much looking forward to seeing / reading of results here!

[MENTION=6726815]Saint_13[/MENTION], please take a look and consider linking this tutorial (Building LOS Custom ROM For Y550) in post #2 of 'development' thread as this will undoubtedly be a boon for us.

Kind Regards, PW

PS. If you check root website from link in Chrome (articles all trsnslate beautifully into English from Dutch) you can check [MENTION=7866480]fwiep[/MENTION]'s personal webpage / blog, incl. his instructions on How to upgrade Y550 to custom ROM, old version of this tutorial etc, and even sample his musical talents if you wish. PW
[Android Q&A, Help & Troubleshooting] GotoDengo:
Thanks very much, you've obviously put in some hard work creating this guide! :)

It might take me some time to get around to trying out as I don't have a Linux system at the moment! I've only got 8GB of memory on my Windows 10 PC so I don't think running a virtual machine will help.

BTW how long does the initial build take? Several hours I'd imagine?
[Android Q&A, Help & Troubleshooting] fwiep:
Actually, I set up a VirtualBox VM with about 7GB of RAM (my host system has 8 GB of physical RAM). The system monitor on the (Ubuntu) host showed 100% RAM usage and almost 100% swap usage, but the build succeeded. Don't forget to shut down the VM when you're done; your host system will not like so little RAM for itself :)

It took about 90 minutes in the said VM. The subsequent builds (monthly updates) take between 25 and 35 minutes.

Kind regards,

FWieP
[Android Q&A, Help & Troubleshooting] GotoDengo:
Thanks for the tips. I'll definitely have to try it when I've got some spare time. :)
[Android Q&A, Help & Troubleshooting] pndwal:
Hey [MENTION=6864096]NATO66613[/MENTION], what device do you have now? Regards, PW
[Android Q&A, Help & Troubleshooting] GotoDengo:
Just to let you know that my attempt at building Lineage are proving slow and frustrating. I suspect my lowly dual core is not up to the job! :(

If Virtualbox doesn't work out for me I'll give Windows Subsystem for Linux a go or upgrade my PC!

All to keep a 5 year old budget phone updated! :D
[Android Q&A, Help & Troubleshooting] pndwal:
Glad you're attempting it!

Suggest you mention [MENTION=7866480]fwiep[/MENTION] (like that!) in posts, then he'll get email notice and may be able to assist as he's been there / done that!

Hope you get the resources you need - It is a great phone, ain't it? :D PW
[Android Q&A, Help & Troubleshooting] pndwal:
Guess this'll help ... one day soon ... [especially WSL2]:

https://www.xda-developers.com/microsoft-announces-windows-terminal/
[Android Q&A, Help & Troubleshooting] rudolfm:
Instead of experimenting with VMs on smaller computers, I would get a cheap SSD, put the linux on there and boot the ssd when you want to make a build. I think 128 gb should be enough, you get those around for around 20 € or $.

Using a VM on a bigger computer is ok.

The Windows subsystem won't work.
[Android Q&A, Help & Troubleshooting] fwiep:
7.1.2 update

Thanks to the LineageOS-developers and [MENTION=4479868]desalesouche[/MENTION], this is today's build containing the May-2019 security patches.

Recent changes: LineageOS 14.1

Kernel: https://github.com/HUAWEI-Y550-Y635/android_kernel_huawei_msm8916/commits/los-14.1

Update: download links have been removed. Please use the most recent ROM, see this link:

Unofficial LineageOS 14.1 (Android 7.1.2) ROM with June-2020 security patches

Known bugs:

- the WiFi MAC-address sometimes switches between a Huawei-prefix 68:a0:f6 and an Airgo-prefix 00:0a:f5 on reboot

Note: I cannot test the battery-save-setting bug anymore; I use WhatsApp only on my primary device. Please test and let us know.

Note: I upgraded my building environment (Ubuntu 18.10) to Ubuntu Disco (19.04). It still works :)

Kind regards,

FWieP
[Android Q&A, Help & Troubleshooting] pndwal:
Does anyone know if it is possible / what problems must be overcome - to build / port treble ROM for our device? - Or just to 'switch on' treble support? (I lack the requisite experience / understanding of programming terms to know :( ). Thanks, PW

https://xdaforums.com/project-trebl...uide-how-to-build-project-treble-gsi-t3801803
[Android Q&A, Help & Troubleshooting] pndwal:
Re. Huawei ban...

WOW!

https://mobile-reuters-com.cdn.ampp.../idUSKCN1SP0NB?usqp=mq331AQCCAE=&amp_js_v=0.1

https://www.xda-developers.com/google-revoke-huawei-android-ban-blacklist/

Edit: Wait! There's more (re. Qualcomm, Intel etc)...

https://www-androidauthority-com.cd...comm-huawei-988011/amp/?amp_js_v=a2&amp_gsa=1

XDA article above updated also.
[Android Q&A, Help & Troubleshooting] gon6697:
Hey there! I'm having an issue with a Y550-L03 in version ending in ARGC25B262. The phone is stuck in a bootloop where it says "boot image verify failed", I tried using the dload method, flashing OTA through recovery which fails due to something with phone.apk, tried fastboot commands to flash another boot image and got "command not allowed". I don't know what else to do, I guess it's due to not being able to find full firmware of that version (just the OTA).

Any suggestions?
[Android Q&A, Help & Troubleshooting] pndwal:
Sorry to bring bad news, but seems updates from Huawei - since they stopped supplying bootloader unlock codes - have also updated bootloader to effectively prevent unlocking, rollback, rebranding or region changing, and they also brick devices where unofficial update methods are attempted. It seems this affects Y550 with any stock ROM past B247.

Was your bootloader unlocked before OTA updates applied? (I'm guessing its still locked.)

See previous info I posted on this below.

I'd try the ADB boot TWRP method at the end and try flashing custom ROM that way (but you'll undoubtedly need unlocked bootloader), which worked for others, despite finding TWRP cannot be flashed (won't stick).

See [MENTION=5150462]YuT666[/MENTION]'s saga on pages 641, 642 here.

Also, dload or other methods (Qualcomm QDLoader, etc) should work with B249 or later full stock ROM (or better, your full B262 ROM) as long as you use one compatible with your updated xloader.img version. These ROMs can be obtained from official site: http://huawei-firmware.com/phone-list/huawei-ascend-y550

Nb. The first thread linked in Original Post below contains xloader checking tool. I'd definitely check xloader version before flashing anything other than your original ROM as others have permanently bricked their devices (no methods to restore work) after rolling back to a ROM with older xloader, or flashing a ROM with different xloader.

WARNING To Others who want to customise Y550:

Do not update past B247. If you do, don't attempt to flash TWRP, only boot using ADB to flash ROMs. PW.
[Android Q&A, Help & Troubleshooting] gon6697:
Thanks for the help and the quick reply! I tried again formatting the SD card and copying this firmware "V100R001ARGC25B249" since there is no way to find the "V100R001ARGC25B262" that i have.

The dload method ended in an error saying:

"chcking sd update pkg...

file:/sdcard/dload/update.app,size=1432341464

oemsbl version list check error!

check_write_data_to_partition, write data error

Error: update.app is a invalid package

Error: SD card update failure, SD card update abort!"

And it takes me to a recovery in which the version appearing on top is the one that i just tried updating.

EDIT: Sorry, I forgot to say that the bootloader has always been locked. (The phone belongs to a friend of mine that barely knows about phone tweaking and has never been interested on it)
[Android Q&A, Help & Troubleshooting] pndwal:
Did you try your ROM from link I gave? Its there, but only OTA it seems.
[Android Q&A, Help & Troubleshooting] gon6697:
Oh, could it work with the OTA? How is the procedure? I tried copying update.zip to SD card and installing update from SD card option in recovery mode. It says "assert failed: apply patch check ("/system/priv-app/Phone.apk)

As I was writing I repeated the procedure of this to check the error message properly, the phone booted back up to android and it's usable (though the error appeared), but I suspect a reboot will get it back on loop. Any suggestions on what to try having a usable phone before trying anything else?
[Android Q&A, Help & Troubleshooting] pndwal:
I'm not sure either. What changes produced boot loop in first place?

Edit: May need to find a full ROM with same xloader as your OTA ROM, and use xloader check tool to see which you have, and check ROMs. Hope there is one!

I'm guessing dload should work if you find one (guess you error 'oemsbl version list check error!' means 'OEM-something-Boot Loader version list check error!'), or try ADB, QDLoader, etc. PW
[Android Q&A, Help & Troubleshooting] gon6697:
My friend showed me that the phone was suddenly dropping the error "com.android.phone stopped working" and she would normally accept it and keep on using the phone, on one occasion we tapped accept, the phone rebooted to bootloader and never got back until now.

Maybe changing the phone.apk could work (I guess it got corrupted somehow) but idk how to do it either
[Android Q&A, Help & Troubleshooting] pndwal:
See my edit in last post. Full ROM flash would be best if compatible one can be found.

However, I'm suspicious phone may have developed memory (emmc) fault (ie physical problem) as it suddenly failed, and this was not due to bad flash, messing with critical partitions, etc. Also, it boots up spasmodically, and these are often symptoms of bad memory, especially in old phone. PW.
[Android Q&A, Help & Troubleshooting] gon6697:
Thanks again, the only link i could get to the xloader drops "update.zip could not be extracted when I run it
[Android Q&A, Help & Troubleshooting] pndwal:
Is that to use xloader check tool?

I'd try to apply official 100MB OTA (B262CUSTC25D001) again using ADB or stock recovery. Search instructions, or see here: https://www.theandroidsoul.com/how-to-install-ota-updates-manually-using-recovery-and-adb-sideload/

Also, you could try to unlock bootloader using DC Unlocker so you can flash any costom ROM. This will likely fail due to updated xloader.img, but were only assuming all ROMs post B247 have updated bootloader. This could be wrong. PW
[Android Q&A, Help & Troubleshooting] gon6697:
Flashing the zip through recovery fails due to phone.apk issue. On the other hand i cannot get adb to recognize the device, though fastboot does.
[Android Q&A, Help & Troubleshooting] pndwal:
I'd try to get ADB working. What happens when you try?
[Android Q&A, Help & Troubleshooting] gon6697:
Writing ".\adb devices" returns an empty list and trying to type the command anyway states that no device is connected. Problem is that I had to reboot to recovery so the phone is back dead, luckily I did enable USB debugging when it revived before.
[Android Q&A, Help & Troubleshooting] pndwal:
Does ADB work with other android devices? Likely drivers not working. Is HiSuite installed and up to date?
[Android Q&A, Help & Troubleshooting] gon6697:
Yes, I have tested it on my Galaxy S7 Edge and it works fine, also HiSuite was installed yesterday and used it for the phone to detect my computer address and save the debugging permission.