yashsingh1/xdaforums huggingface dataset:
[Android Q&A, Help & Troubleshooting] pndwal:
Well done.

Seems this is an OTA Full Update (containing entire final state of the device - system, boot, and recovery partitions) produced from target-files .zip from the new build only.

Should be able to build considerably smaller OTA Incremental Update by plugging in both the target_files .zip from the previous build (the one you want to update from) as well as the target_files .zip from the new build. (An Incremental package need only contain an encoding of the differences between the any files that have changed, so while small, can only be installed on a device that has the old or source build used when constructing the package, ie. your original ROM.)

Full vs. Incremental OTA Update Package description:

https://source.android.com/devices/tech/ota/tools

Kind regards, PW.
[Android Q&A, Help & Troubleshooting] fwiep:
Thanks for the info and the link to the docs.

It took me some time, but I managed to get the incremental updates going.

I performed a test-build with no specific changes (relative to my build from 22-8-2018). I then worked my way towards an OTA-zipfile only 2,5 MB in size!

I plan to build and release next month's update with both a normal (full) zip and an incremental zip (relative to my 2018-08-22 build).

Wow, these have been a few of the most educational days in my programmer's life :)

Thanks for your input, kind regards,

FWieP
[Android Q&A, Help & Troubleshooting] pndwal:
No worries. Glad you were able to implement incremental updates. May be useful for many if you can post these. :svetius: PW
[Android Q&A, Help & Troubleshooting] pndwal:
New thread for official LineageOS 15.1 cherry builds for Huawei G620s/Honor 4/4x(msm8916) here:

https://xdaforums.com/honor-4x/development/rom-lineageos-15-1-huawei-g620s-honor-4-t3829618

First official ROMs 20/08/2018. PW
[Android Q&A, Help & Troubleshooting] kekkkko:
A moment. I flashed the rom lineage-14.1-20180812-UNOFFICIAL-y550 ,if I flash thi zip will have I ota update?
[Android Q&A, Help & Troubleshooting] pndwal:
If you flash you will be updated to 20180822. This is an OTA formatted update, and should be flashed from computer in the manner fweip described. (It will not make OTAs arrive over the air.)

Have a look at [MENTION=7866480]fwiep[/MENTION]s last post re future OTA files he is planning to provide. (These will only be available over the air if a server is set up and dedicated to this service, and generally this won't be done unless ROMs become official in any case.) PW.
[Android Q&A, Help & Troubleshooting] pndwal:
Can OTAs alternatively be flashed from TWRP, or is ADB sideload required? Thanks, PW.
[Android Q&A, Help & Troubleshooting] fwiep:
I don't know for sure. The instructions I found specifically talked about ADB sideload.

I will test upon next build and let you know.

Kind regards, FWieP
[Android Q&A, Help & Troubleshooting] pndwal:
Thanks for that. I remember reading way back about problems encountered flashing OTAs in unapproved ways due to differential nature of incremental update packages, but I've forgotten what specific cautions there were. I'll do a little digging on it too. PW
[Android Q&A, Help & Troubleshooting] pommegmx:
Hi,

Thanks for all of this !

Since the last time, I tried also with "vds cryptfs enablecrypto..." still not work.

I read your link, very interesting.

In my opinion, it's the 1, I tried a most of custom rom to do this (all in android 5+), so with differents kernels and differents boot.img.

I think I tried all I can do with my skills, so wait & see.
[Android Q&A, Help & Troubleshooting] pndwal:
Yes, but if kernel / boot.img were never altered to support encryption, the problem could still well be with these as y550 never had encryption with stock so support would need adding (/ commits updating) at some point.

I checked threads for G620s/Honor 4/4x(msm8916) too, and the same problems are reported for these with no solution, so official cherry devices (and builds) lack support, and all Y550 builds are cherry based.

Thanks for your efforts and for reporting. Of course, it is still apparently just as likely a bootloader problem, but if not a fix may be found to add support eventually. I'll wait and see too. :) PW.
[Android Q&A, Help & Troubleshooting] pndwal:
Another big subject, but here's what I found re installing OTAs (for everyone's edification):

Incremental updates are also known own as differential or delta updates.

Regarding official OTAs from manufacturers-

https://twrp.me/faq/officialota.html:

'Installing official updates from your manufacturer or carrier is not supported by TWRP. Reasons:

Most official updates are differential in nature. On a completely stock device when used in the way that Google and manufacturers intend, users will never modify the system partition... Unfortunately this method also means that users who have modified their system by rooting, installing busybox, and removing unwanted system apps may experience unexpected behavior when they install a differential update.

Also, device manufacturers may have made changes to their recoveries that we aren't aware of... Those changes may not be present or supported by TWRP which may result in unexpected behavior, especially when it comes to updating items like radios, bootloaders, and modems.

If you... still want to install an official update from your manufacturer, the recommended process is to first return your device to completely stock including replacing TWRP with a copy of the stock recovery.'

Regarding OTAs from ROM developers-

From the above it seems that even on non stock devices, differential OTA updates may be a problem if system.img or boot.img files that have been patched by users (eg installing by Magisk, etc) are then altered by differential updates not expecting an altered file. Unless developer is sure no files updated are likely to have been altered by user patching etc, it seems restoring boot.img to developers ROM version (effectively unrooting, unless boot.img is pre-rooted) would be a minimum requirement before flashing OTA.

If the above is given consideration, TWRP flashing is probably fine, esp. as radios, bootloaders, and modems are unlikely to be included in developer OTA updates. These issues may be handled correctly in latest TWRP with OTA support now in any case, but I don't know for sure. See below.

Looks like OTAs (presumably for custom ROMs only) now (since ver. TWRP-3.2.2-0) play nicely with TWRP.

https://www.xda-developers.com/twrp-3-2-2-0-adb-fixes-improve-ota/

However people still reported bugs on XDA with 3.2.2-0 and incremental OTAs. Apparently this was fixed in 3.2.3-0 (fixed error asking to decrypt /data also)

https://twrp.me/site/update/2018/07/01/twrp-3.2.2-0-released.html

https://twrp.me/site/update/2018/08/06/twrp-3.2.3-0-released.html

Interestingly, rom-manager app has long had support for delta downloads. It can apparently send comparison info. re. ROM files in zip on your phone to a 'delta server', which analyses differences between these and files in complete ROM specified on another web server, creates a small delta file for you to download, and you can then update differentially to latest ROM.

https://www.androidpolice.com/2013/02/13/rom-manager-adds-support-for-delta-downloads/

Looking forward to giving your incremental OTAs a go using latest TWRP. PW.
[Android Q&A, Help & Troubleshooting] TsiaoTai:
Hi, my current phone passed away so I try to revive my old Huawei Y550. When I connect it, the red led lights up for few minutes and then goes out. On my PC, the phone is recognized as "Qualcomm HB USB 9008". I tried to flash stock ROM with QFIL : unsucessfully. I also tried this : http://huawei-firmware.com/rom/huawei-ascend-y550/y550-l02/61 : same issue...

I don't know what to do, if you could help me ?

Thanks and sorry for poor english
[Android Q&A, Help & Troubleshooting] rudolfm:
I have problems reading this thread. When i want to see a specific page via bookmark, i often get "403 forbidden - nginx". Then i have to go to the first page, then klick last page.

Right now, i can't read page 629. Whether I click 629, or try with arrows from 628 or 630, I always get the 403.

This does not happen when i read the wireguard thread. I tried different devices/browsers. All devices were android.
[Android Q&A, Help & Troubleshooting] pndwal:
Try XDA labs app. Jumps to pages fine, but has the same problem if I click Load in Browser. I go to first page also, open in browser, then go to any page without issues. Open in Chrome works too. I think this started happening when we reached about 500 pages. PW
[Android Q&A, Help & Troubleshooting] pndwal:
Should that be 'Qualcomm HS-USB QDLoader 9008'? (Haven't seen HB mentioned before.)

Were you using QFIL when problem first occurred? Or did you alter (or try any software that alters or flashes) critical partitions (other than data, system, boot, recovery)?

Anyway, seems you may have damaged emmc and need to rebuild it. :(

Check here:

https://xdaforums.com/android/help/to-root-huawei-y500-t2923318/page611

Read all posts on pages 611 & 612 regarding rebuilding your emmc using QFIL (Qualcomm Flash Image Loader). You may want to ask for help from [MENTION=9078544]x.ak****[/MENTION] as he has experience fixing emmc on phone with the same Snapdragon 410 chipset as ours using QFIL.

See also post #6043 re. using QDLoader 9008 software. Firehose file in my link posted there (rebuild file specific to Snapdragon 410, ie prog_emmc_firehose_8916.mbn) will probably be good for either software.

Hope this helps. Please report, and all the best with it, PW.
[Android Q&A, Help & Troubleshooting] TsiaoTai:
Thanks for your reply. When I try Qfil I have this error :

or this one :

I don't think I alter my phone in any way
[Android Q&A, Help & Troubleshooting] pndwal:
Recommend you check you are using a good USB data cable - try with others (Tip: make sure it's a thick one), try another port, and check drivers are set up for phone properly (no yellow marks in device manager when connected).

Sadly, if you put phone in download mode successfully, it is appearing as 'Qualcomm HS-USB QDLoader 9008', all the above is set up properly and you are using correct firmware .zip and firehouse file, ie prog_emmc_firehose_8916.mbn, it may well indicate that the emmc memory has simply failed physically. Please check carefully. Hope it hasn't, but doesn't sound good. PW.
[Android Q&A, Help & Troubleshooting] TsiaoTai:
Ty, I download the firmware here : http://huawei-firmware.com/rom/huawei-ascend-y550/y550-l01/18812

I will try what you say. Can my windows version has an impact ? And is it necessary to have an unlocked bootloader, or we can use QFIL with a locked one ?
[Android Q&A, Help & Troubleshooting] pndwal:
-Firmware looks ok if you have L01. Could try with others from post #2, ROMs, here: https://xdaforums.com/android/development/huawei-y550-development-t3425524

-Not sure about windows version, but I doubt it.

-I think you can use QFIL with locked bootloader for stock ROM.

-***Please can you confirm phone is appearing exactly as 'Qualcomm HS-USB QDLoader 9008'. If phone is recognized as "Qualcomm HB USB 9008" as you stated, or anything else, it probably indicates a bad port or setup.

-Could try Qualcomm drivers from here: https://www.getdroidtips.com/install-use-qualcomm-flash-image-loader-qfil/ or here: https://www.androidbrick.com/lenovo-zuk-phones-qfil-roms-unbrick-guide/ (This was from a quick google search - you may find better sources.)

-May need to change “device type” to UFS from EMMC in “Firehose Download configuration” under Configuration menu, but I'm not sure for our device.

-Check using QFIL build 430 or later.

PW.
[Android Q&A, Help & Troubleshooting] TsiaoTai:
Yes it's Qualcomm HS-USB QDLoader 9008. I made a mistake in my first post.

To use Qfil, I created rawprogram0.xml and patch0.xml from firmware following this video : https://www.youtube.com/watch?v=Yn1TyC20Dh8 . Is it a good method ?
[Android Q&A, Help & Troubleshooting] pndwal:
-Good

-rawprogram0.xml and patch0.xml was addressed on page 612. I don't think you need to or should create them, just extract from ROM:

[MENTION=9078544]x.ak****[/MENTION] said: 'Flat build is a type of flashing and use the rom specified for your device! All the files are in the extracted folder only'

I said: 'Seems you simply use Flat Build type flash in QFIL software, and point it to folder containing extracted official stock ROM, which should contain all files required. I think the ones QFIL needs to find to start rebuilding emmc, from my research, are specifically named prog_emmc_firehose_8916.mbn, rawprogram0.xml and patch0.xml. (ensure the last two are from official stock Y550-L0X ROM.)'

There's a fair chance you'll succeed - unless emmc damaged physically, but these problems reportedly can occur in case of a bad flash only.

Hope this helps. Let us know how you get on. PW
[Android Q&A, Help & Troubleshooting] Lhfskl:
Hi everybody.

I have a problem with my phone.

When i connect my phone to my laptop, its touch screen doesn't work correctly. And lots of sudden touches occure.

No difference which Rom, in all of Roms i had this problem.

Do u have any solution?

Thank u.
[Android Q&A, Help & Troubleshooting] TsiaoTai:
But the ROM does not contain rawprogram0.xml and patch0.xml .

Just "UPDATE.APP" and if I extract this file I have this :
[Android Q&A, Help & Troubleshooting] TsiaoTai:
maaaaan [MENTION=7550078]pndwal[/MENTION] I think my problem has nothing to do with emmc but just a problem of overheating... I left my telephone a few seconds in front of wind then I plug into charger. A yellow led lights on and the battery image charging appears with the %. But I can't turn on my phone.

Also on my computer the phone is no longer recognized "Quacomm HS USB 9008" but "J:" but I can't interact with it.
[Android Q&A, Help & Troubleshooting] pndwal:
May be good, but sounding more and more like memory has been physically damaged, whether by heat or other.

Can you now boot to Fastboot&Rescue or Recovery / android robot image screen? (Could put phone in fridge a short while to diagnose if cold helps :) )

Even if above fails, you could now try dload method. Should work if non-critical partitions simply got messed up. PW.
[Android Q&A, Help & Troubleshooting] TsiaoTai:
I can turn on my phone but this message appears "internal storage damaged is now unavailable, please choose one of the following options"

options are reboot and factory reset but nothing change Also I have access to settings so I can activate USB debuging And I have access to recovery, but no bootlader When I type the command "adb reboot bootloader" nothing happens and it shows the first screen whith the message of internal storage damaged... Indeed I think it's a physical problem

Strange fact : the option "allow OEM unlock" in developer settings is not here
[Android Q&A, Help & Troubleshooting] pndwal:
Commiserations, and thanks for reporting.

Interesting you got the message to confirm it.

You still have stock ROM? Don't think we had "allow OEM unlock" in developer options in 4.4.4. (doesn't show on stock with unlocked bootloader anyway).

Reckon you should try second-hand market for Y550 - great phone (SD410) for little money, looks like Oreo (LOS 15.1) is immenent (already have official cherry - for some :) ), LOS14.4 now near perfect [thanks [MENTION=4479868]desalesouche[/MENTION]!] (adoptive storage is great on N), and you have a spare screen complete assembly (hard part when replacing is separating digitizer and LCD), speaker etc! (Shame memory is not replaceable without main board.)

I was doing more digging on emmc, and it seems stock Qualcomm ROMs don't always include programmer files needed for QFIL, and Huawei ROMs apparently lack them too. Best QFIL tutorial I found is here: https://forum.hovatek.com/thread-22466.html - see important notes at bottom. Site hosts many stock ROMs also, incl. Latest Y550. Could try this to fix broken bootloaders to re-enable ability too flash: https://forum.hovatek.com/thread-19721.html

- You did very well following that video - must have taken some patience. Likely the rawprogram0.xml and patch0.xml would work with undamaged phones, and could be very useful for others. Would you be able to upload them here? And which firehose file were you trying? Thanks and regards, PW.
[Android Q&A, Help & Troubleshooting] TsiaoTai:
Thanks for your help I appreciate

Yes I have stock ROM 4.4, probably that's why I can't see "oem unlock" in developers settings

here the files I try to use for qfil

View attachment rawprogram0.xml

View attachment patch0.xml

I used firehose 8916, the one you telled me to use
[Android Q&A, Help & Troubleshooting] pndwal:
Well done. Thanks for files. PW
[Android Q&A, Help & Troubleshooting] pndwal:
With [MENTION=5091734]dianlujitao[/MENTION]'s new release ROMs for official cherry devices yesterday, seems previously common boot loops and boot logo crashes are fixed. This may bode well for proper booting of LOS15.1 unofficial cherry on Y550. :) PW.
[Android Q&A, Help & Troubleshooting] Saint_13:
all y550 have this problem from factory!!! :D:D:D

also all y550 suffer from overheating on 4G!
[Android Q&A, Help & Troubleshooting] Lhfskl:
Hi everybody.

A question!!

I have LOS14.1

How can i reset settings?
[Android Q&A, Help & Troubleshooting] pndwal:
Whatever you changed in settings, change it back. :) ... Or backup everything and factory reset. Or probably best bet - but I haven't tried it - go to Settings, Apps, scroll down and click Settings, click Storage, click Clear Data. PW.
[Android Q&A, Help & Troubleshooting] pndwal:
Thats interesting, I haven't noticed either problem on LO2. Screen works fine both in Tethering and File Transfer modes. And I'm on LTE most of the time, and don't think it's overheating. :):):) PW.
[Android Q&A, Help & Troubleshooting] Saint_13:
it depends on usb cable, pc usb port or usb charger and rom. my L02 with stock rom and charger and with my old pc usb port, lots of sudden touches occurs with lots of overheating. but with htc charger and my new pc with usb3 and new roms it works fine. also I noticed sudden touches increase when device start to overheat.

I experience overheating in 4G with games like soccer star. but in normal use like web browsing and app like instagram it just get a little hot.

Besides, Y550 is low end device from 2014 and now is 2018. and I can't expect too much from it after 4 years of daily use. ;)
[Android Q&A, Help & Troubleshooting] pndwal:
Yup - its a hardy little phone! - Haven't played games on it myself which may be why I haven't had heat issues. I take it you don't have overheating if playing over WiFi? PW.
[Android Q&A, Help & Troubleshooting] Saint_13:
much less overheat on WiFi or 3G.

My P8 lite also start to overheat on 4G when I push it hard! :laugh: but because of leather phone cover! my Y550 have plastic cover. I can confirm less overheat when I use this phones without cover.

mobile phone with aluminum body have much less overheat issue. but those phone with plastic or glass body can't transfer heat easily. :cool:
[Android Q&A, Help & Troubleshooting] yasharGG:
someone need to compile new kernel and add more features(CPU oc1800,GPU 700,governor,scheduler,fast charge,hotplug:intelliplug,alucard...)

bff kernel from hacker was great.

thanks for support!
[Android Q&A, Help & Troubleshooting] rudolfm:
Take a look at the App "Kernel Auditor" if you want to change these settings.

https://f-droid.org/de/packages/com.nhellfire.kerneladiutor/
[Android Q&A, Help & Troubleshooting] desalesouche:
los14.1

update coming...
[Android Q&A, Help & Troubleshooting] Lhfskl:
thnx

please don't forget poor y550, and make LOS15 for it.
[Android Q&A, Help & Troubleshooting] desalesouche:
trying to...:silly:
[Android Q&A, Help & Troubleshooting] pndwal:
Impressive number of commits on Sept. 16, 17! https://github.com/HUAWEI-Y550-Y635/android_kernel_huawei_msm8916/commits/los-14.1 :) PW.
[Android Q&A, Help & Troubleshooting] desalesouche:
/e/ interesting project

https://e.foundation/community/

here is a new project i will try to compile. let me know your what you think about that
[Android Q&A, Help & Troubleshooting] pndwal:
Yes, I read the XDA article re Gaël Duval (https://en.m.wikipedia.org/wiki/Gaël_Duval), his '/e/ foundation' (https://e.foundation), and de-Googling phones with interest too. -https://www.xda-developers.com/e-google-free-lineageos-fork-nexus-oneplus-xiaomi/ (I was about to ask him if '/e/' might just run on a phone already running LOS 14.1 by keeping device specific LOS kernel as /e/ is LOS based)

Its eye opening to see how much info. is leaked to / collected by Google by stock apps, and even by subsystem (here is Gaël's appraisal of the ethics: https://www.indidea.org/gael/blog/e...roid-monopoly-and-its-a-good-thing/#more-1237), so looks like a very useful project for those interested in privacy / security, but it seems to have a long way to go (even just moving from N to O based). Also, many reviewers are sceptical that the project will get momentum as most users will likely take the easy road and restore apps that use Google services, or be reluctant to give them up in the first place. More info: https://hackernoon.com/leaving-apple-google-e-first-beta-is-here-89e39f492c6f

I for one, would certainly be interested in trying, evaluating, testing /e/. Gaël Duval, who originally created Mandrake Linux (now Mandriva Linux) only to be fired by the company (perhaps for his ethical views regarding its future direction), just might succeed spectacularly if users like XDA community members adopt and support it. (His '/e/' team to date includes some 40 members including at least 15 software engineers - https://e.foundation/about-e/.)

Thanks for your interest in it, PW.
[Android Q&A, Help & Troubleshooting] desalesouche:
los 14.1 update

http://www.mediafire.com/file/spt3mfophz9i333/lineage-14.1-20180916-UNOFFICIAL-y550.zip/file

expecting feed back...:D

i wrote to some devs to ask help about y550, cos my skill is not enough to get los 15.0 and 15.1 compiled...:crying:

:) i hope they will answer me in a positive way....
[Android Q&A, Help & Troubleshooting] rudolfm:
I don't think /e//makes much sense. You need really lots of infrastructure to keep something like LineageOs going on in a reliable manner. The /e/ folks will not get that kind of (voluntary) manpower.

It would make sense to set up a project where you have a zip that converts a Lineage to an /e/. Leave all the hassle with kernels and Android patches to the (many) folks doing Lineage, and then have a zip like MicroG that removes the unwanted google stuff, and installs the alternatives. With their concept the /e/ folks need to maintain a release for every phone. If they "cannibalize" Lineage, all they need to do is maintain a .zip for 14.1 and 15.1 which then can be used on any phone.

I do the same thing with my phones btw. I install Lineage, disable lots of stuff, install Afwall, K9, Firefox Yalp, etc. That gets my phone as close as needed to what /e/ is intended to be.
[Android Q&A, Help & Troubleshooting] pndwal:
Many thanks. One way or another it will be done by your efforts. Kudos to you! PW.
[Android Q&A, Help & Troubleshooting] GotoDengo:
I've dirty flashed this and all seems well so far. :)

Thanks for another sterling effort! :good:

I do hope you get help to move to LOS 15 though, that would be amazing to have on our phone!
[Android Q&A, Help & Troubleshooting] pndwal:
Running lineage-14.1-20180916-UNOFFICIAL-y550. No issues yet! Any specific changes to test?

And are you still considering porting Y550 to /e/? Many thanks, PW.
[Android Q&A, Help & Troubleshooting] desalesouche:
yes. As soon as source are ready.....
[Android Q&A, Help & Troubleshooting] pndwal:
:good::good::good::good:
[Android Q&A, Help & Troubleshooting] pndwal:
Can you let us know - did you get any answers / help for this?

Can you tell us how compilation breaks? Thanks, PW.
[Android Q&A, Help & Troubleshooting] desalesouche:
compilation breaks because kernel needs to be audio updated. Kernel need many more commits by the way.
[Android Q&A, Help & Troubleshooting] pndwal:
Many thanks for the info. I take it you've not received offers of help yet. Regards, PW.