[Huawei P9 Lite ROMs, Kernels, Recoveries, & Other ] k1ll3r8e:
Heyho,

THX for the detailed info! ;)

-

I tested it on B130 only... But i tested it now also with another path like "/sdcard/HwOUC/00000/..." but it doesn't work anymore...

(I think, there is another check, because after the restart i have a "/storage/emulated/0/HwOUC/SUROAM/..." folder... But it's empty... I just check it with different builds... I'll report back when i get an result.)

THX for the report and info!

-

I also just try it with B150/210, lets see what it brings.

UPDATE:

I think i found the bad boy ;) - Just test it with another build, will report soon ;)

UPDATE 2:

I could reproduce my 1st attempt on the B130... But not on B150 or higher...

Seems i used a bug^^ - I used FF proxy, then i deleted the update after the "Authorizing" and placed my files and commands. After that it worked. But also not ever, did this now 7 times with B130 and it worked 4 times...

About the higher builds... What i tried:

The "sdcard" (internal storage) is mounted in the stock recovery as "/HWUserData/" and there is the folder "/HwOUC/" and the next folder stage is "/66015/" (B160 - FULL)... This folder contains the .zips...

So the "/cache/recovery/command" will look like:

--update_package=/HWUserData/HwOUC/66015/update.zip
--update_package=/HWUserData/HwOUC/66015/update_data_full_hw.zip
//empty line

The difference between B130 and B160 is for example the "/cache/recovery/HwoucHotaFlag" file... Which is empty so far i can read/copy it before the reset...

But it seems that the "/cache/recovery/command" file is not enough to tell the recovery-update interface that there is an update... Because i still get package not found... Looks like there is somewhere in the system a .xml or something else, which implies that there is an update... Maybe i can figure it out... But this will take a bit time because, i have only 16 mbit... And to check what the "original" updater do, i have to download the update for each attempt (really time consuming, 20-30 min per attempt)...

UPDATE 3:

Seems on some builds like B150/160 it's not possible to update with unlocked bootloader... The update apk gave me "Authorized! Reboot now?" and the recovery gave me "Unable to verify update package!"... So on this builds, even if it would work, it won't work based on some checks running inside the recovery... Funny thing is, after i placed the update.app's (B150/160) manually in the "dload" folder, they installed fine... So proven by this, there are 2 different "update" mechanics inside the stock recovery...

UPDATE 4:

Seems i'm no longer able to install N... No updates anymore after B160... Even after manual switch to B210 no update... FF and proxy also doesn't work anymore... Will report back when i got N back to work on my device.

UPDATE 5:

Back in the game... Notice: When u get stuck on B160, search in FF for "L31C432B370 - 80460" and install it the proxy way.

UPDATE 6:

Sooo, seems i got it reproduce able to work! The main problem is/was to get the right ID for the update package... It's very important to have the correct directory structure for the update... This means the location MUST be like this scheme:

[COMMAND][SD-CARD][HwOUC][BUILD-ID][FILES]
--update_package=/HWUserData/HwOUC/012345/update.zip
--update_package=/HWUserData/HwOUC/012345/update_data_full_public.zip
--update_package=/HWUserData/HwOUC/012345/update_full_VNS-Lxx_hw_eu.zip
//empty line

I'll try this now an different builds, because i still get no N update... And i'm still not able to flash the update manually. The given info's only end in the file detection by the stock recovery. But, the "Verification" dialog will still fail, even with correct oeminfo. So i'm atm a little bit lost, because i don't know what to do, to trick the stock recovery, that it don't care on other things except the oeminfo...

UPDATE 7:

Finally, i'll remove the update tab in the next build. (Maybe not forever) - Reason, after ~12h testing there are the following problems:

* On builds like B130 - B210 we are not able to flash a build like B380++ (The recovery say, package not found, the build-id and everything is correct... But, when i try it with an build like B160 on B130 or B210 on B160 it works... So there is somewhere a list or something else which accept only a range or specific "build-ids"... If the id is unknown, like the B380 [83116] u'll also get the "package not found" even it's there...)

* On builds like B370 (maybe also higher, can't test, because i can't flash them anymore. I'm currently stuck on B370) we can write the command file, but the recovery will fail on the "Verification" dialog.

So based on these probs, there is currently no option to flash the N (non beta) builds this way... And the MM builds can be flashed by "dload", so there is no need for the update view until i get it work for the N (non beta) builds...

Note: The nougat (beta/preview) builds can be flashed by this way (B328 - B370 [MF-PV]). The B370 [MF] will not work.

Regards,

Sebastian