I have tried many times and have no clue Please help me thanks
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
https://download.pixelexperience.org/changelog/h8266/PixelExperience_h8266-10.0-20191205-1106-OFFICIAL.zip
turnout96 said:
I have tried many times and have no clue Please help me thanks
https://download.pixelexperience.or...erience_h8266-10.0-20191205-1106-OFFICIAL.zip
Click to expand...
Click to collapse
Like you install a ROM in recovery
MartinX3 said:
Like you install a ROM in recovery
Click to expand...
Click to collapse
but that rom have to flash oem first
so can`t boot to twrp (no twrp for android 10)
MartinX3 said:
Like you install a ROM in recovery
Click to expand...
Click to collapse
First you need to refresh the latest Sony Open Devices binary file and restart to TWRP to flash this ROM.But TWRP cannot be used after refreshing the binary file
But stock and the 9.0 roms have twrp for the initial installation
After that you should get OTA updates
you can unpackage the rom with payload dumper，and flash it like flashing Aosp 10.
你直接用 payload dumper把包拆了，然后像刷马丁的Aosp10一样刷它就行了。你可以酷安直接搜xz2，我有分享一个东西
pixel experience .zip doesn't flash on twrp it just says error flashing without an error code so the way to install is (as stated in the previous reply) extract the payload.bin and use payload dumper to get the .img files and flash them with fastboot one by one
Faruk.ErdaL said:
pixel experience .zip doesn't flash on twrp it just says error flashing without an error code so the way to install is (as stated in the previous reply) extract the payload.bin and use payload dumper to get the .img files and flash them with fastboot one by one
Click to expand...
Click to collapse
Can you give me the logs listed in the twrp thread?
Don't worry if logcat doesn't work
MartinX3 said:
Can you give me the logs listed in the twrp thread?
Don't worry if logcat doesn't work
Click to expand...
Click to collapse
Sorry, I'm already back on stock but will try again with newer oem
Faruk.ErdaL said:
Sorry, I'm already back on stock but will try again with newer oem
Click to expand...
Click to collapse
No problem
To flash a zip you don't need a specific OEM, you can do it with the stock twrp, too.
---------- Post added at 11:01 AM ---------- Previous post was at 10:07 AM ----------
Faruk.ErdaL said:
pixel experience .zip doesn't flash on twrp it just says error flashing without an error code so the way to install is (as stated in the previous reply) extract the payload.bin and use payload dumper to get the .img files and flash them with fastboot one by one
Click to expand...
Click to collapse
problem found, will be fixed in the next release.
MartinX3 said:
No problem
To flash a zip you don't need a specific OEM, you can do it with the stock twrp, too.
I know, I was just looking for a motivation to try to install it again
---------- Post added at 11:01 AM ---------- Previous post was at 10:07 AM ----------
problem found, will be fixed in the next release.
Click to expand...
Click to collapse
oh nice, that was quick. so it was a problem with twrp itself? not the .zip
Faruk.ErdaL said:
oh nice, that was quick. so it was a problem with twrp itself? not the .zip
Click to expand...
Click to collapse
The zip, I mean the Pixel Experience ROM code, not twrp.
I'm everywhere, muahahahaha. :silly:
The /tmp/recovery.log shows more than the onscreen log. (Sadly).
The device in case of the XZ2 searched for a H8216 (RoW) or H8266 (DD), but receives an akari on SODP 9.0 based ROMs. (On stock it should give you the correct H8216, H8266; BUT sadly H8296 or H8276 depending on if you use the canadian or asian firmware).
So it tells you "I found an akari, not a H8266/H8216, I don't know which device is that, so I cancel the installation before doing anything wrong"
MartinX3 said:
The zip, I mean the Pixel Experience ROM code, not twrp.
I'm everywhere, muahahahaha. :silly:
The /tmp/recovery.log shows more than the onscreen log. (Sadly).
The device in case of the XZ2 searched for a H8216 (RoW) or H8266 (DD), but receives an akari on SODP 9.0 based ROMs. (On stock it should give you the correct H8216, H8266; BUT sadly H8296 or H8276 depending on if you use the canadian or asian firmware).
So it tells you "I found an akari, not a H8266/H8216, I don't know which device is that, so I cancel the installation before doing anything wrong"
Click to expand...
Click to collapse
That's it, thanks. Is there any way to skip the twrp's model certification and directly flash in h8296?
shibUyA- said:
That's it, thanks. Is there any way to skip the twrp's model certification and directly flash in h8296?
Click to expand...
Click to collapse
Could you try the new OTA?
MartinX3 said:
Could you try the new OTA?
Click to expand...
Click to collapse
PixelExperience has updated and I tried to flash it in latest stock twrp. But it failed and recovery log showed [0105/121511.271501:ERROR:delta_performer.cc(1582)] Public key verification failed, thus update failed.
[0105/121511.271537:ERROR:download_action.cc(397)] Download of file:///sdcard/PixelExperience_h8266-10.0-20191211-2317-OFFICIAL.zip failed due to payload verification error.
[0105/121511.271577:INFO:action_processor.cc(116)] ActionProcessor: finished DownloadAction with code ErrorCode::kDownloadPayloadPubKeyVerificationError
[0105/121511.271619:INFO:action_processor.cc(121)] ActionProcessor: Aborting processing due to failure.
shibUyA- said:
PixelExperience has updated and I tried to flash it in latest stock twrp. But it failed and recovery log showed [0105/121511.271501:ERROR:delta_performer.cc(1582)] Public key verification failed, thus update failed.
[0105/121511.271537:ERROR:download_action.cc(397)] Download of file:///sdcard/PixelExperience_h8266-10.0-20191211-2317-OFFICIAL.zip failed due to payload verification error.
[0105/121511.271577:INFO:action_processor.cc(116)] ActionProcessor: finished DownloadAction with code ErrorCode::kDownloadPayloadPubKeyVerificationError
[0105/121511.271619:INFO:action_processor.cc(121)] ActionProcessor: Aborting processing due to failure.
Click to expand...
Click to collapse
Thank you for your bug report
I redirected it to the team.
---------- Post added at 09:05 AM ---------- Previous post was at 08:34 AM ----------
shibUyA- said:
PixelExperience has updated and I tried to flash it in latest stock twrp. But it failed and recovery log showed [0105/121511.271501:ERROR:delta_performer.cc(1582)] Public key verification failed, thus update failed.
[0105/121511.271537:ERROR:download_action.cc(397)] Download of file:///sdcard/PixelExperience_h8266-10.0-20191211-2317-OFFICIAL.zip failed due to payload verification error.
[0105/121511.271577:INFO:action_processor.cc(116)] ActionProcessor: finished DownloadAction with code ErrorCode::kDownloadPayloadPubKeyVerificationError
[0105/121511.271619:INFO:action_processor.cc(121)] ActionProcessor: Aborting processing due to failure.
Click to expand...
Click to collapse
Could you try to disable the signature verification in twrp?
MartinX3 said:
Thank you for your bug report
I redirected it to the team.
---------- Post added at 09:05 AM ---------- Previous post was at 08:34 AM ----------
Could you try to disable the signature verification in twrp?
Click to expand...
Click to collapse
I disabled all options in the settings panel, but the problem remains the same
shibUyA- said:
I disabled all options in the settings panel, but the problem remains the same
Click to expand...
Click to collapse
But you already did download it again?
MartinX3 said:
But you already did download it again?
Click to expand...
Click to collapse
I tried to re-download the adb tools, stock firmware, twrp and PE zip. But still fails
shibUyA- said:
I tried to re-download the adb tools, stock firmware, twrp and PE zip. But still fails
Click to expand...
Click to collapse
Aye aye aye thank you and the others for the hint
It works with the delivered boot.img but not with stock or in my case the 4.9 sodp boot.img environment
I generated and forwarded the needed logs.
Please use a payload extractor and flash the stuff in fastboot.
https://github.com/cyxx/extract_android_ota_payload
This might be useful
Related
If someone wants to make mirrors or a flashable zip, feel free to contact me and I will update thread
I've got my new OP3 today and what I've noticed that it runs with Oxygen OS 3.2.5. So I have looked around and saw that nobody backed up their 3.2.5 und uploaded it so I decided to do it.
Here is the download link: https://mega.nz/#!PJhzRDyL!wX12zmq9ptiu8gNbtfQfypB2Q6wGdu3IfNFFwi9acQk
The only requirement is an unlocked bootloader as fastboot doesn't allow to flash on locked devices
How to install:
via twrp:
- boot into twrp recovery
- press "install"
- press "install image" on the bottom right
- select the image and confirm on which partition it should flash
(not recommended) via fastboot:
- boot into fastboot
- use these commands to flash it:
ignore the little warning message and pe patient because it can take a while till you get a response from cmd because fastboot splits the image into 6 parts
Code:
fastboot flash boot boot.img
fastboot flash system system.img
Note: if your phone isn't booting, flash supersu and it should boot.
screenshots:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Fastboot flashing is not working.
Can you comment on the LTE reception and performance? It was the only issue i had with 3.2.4
Anyone tried looks tempting
Sent from my ONEPLUS A3003 using XDA-Developers mobile app
TWRP is working, fastboot not.
Im on 3.2.5 now so yes its working, but only with TWRP
*Extracted fine with newest winrar*
Error on my end, sorry, thank you!
Chronzy said:
@hellcat50 zip is corrupt, "unexpected end of archive" when I tried to extract the img's. Downloaded it twice. Don't recommend wiping and trying to install at this time.
Would love to have this though, would you mind repacking?
---------- Post added at 12:19 PM ---------- Previous post was at 12:18 PM ----------
you were able to extract the imgs? I downloaded it twice and got corrupt zip both times.
Click to expand...
Click to collapse
It did extract without any issues on my end.
I downloaded and extracted the file on my PC with the latest winrar.
EDIT:
Worked as described in the first post.
I flashed both files, followed by the latest SuperSU 2.78 and Xposed,
then did a reboot.
All works well!
So, I will not lose my data, right?
No, but you should still do a backup in TWRP.
AcmE85 said:
No, but you should still do a backup in TWRP.
Click to expand...
Click to collapse
Sorry, but I haven't installed TWRP. I'm completely on stock (system and recovery)
Andrea224 said:
Sorry, but I haven't installed TWRP. I'm completely on stock (system and recovery)
Click to expand...
Click to collapse
Then there is probably no way to install this to your device, as a user already said that using fastboot does not work.
I also think that your bootloader should be unlocked for this to work.
AcmE85 said:
Then there is probably no way to install this to your device, as a user already said that using fastboot does not work.
I also think that your bootloader should be unlocked for this to work.
Click to expand...
Click to collapse
Mmh...ok, thanks anyway.
So basically you should have unlocked bootloader, supersued, and TWRP'ed
Reconfigured said:
So basically you should have unlocked bootloader, supersued, and TWRP'ed
Click to expand...
Click to collapse
SuperSU is not needed, why should it be? With this you overwrite the whole System partition, thus removing all mods including SuperSU and Xposed.
waiting for someone to confirm the LTE issue resolution.. if it's resolved, I'll flash this ASAP..
AcmE85 said:
EDIT:
Worked as described in the first post.
I flashed both files, followed by the latest SuperSU 2.78 and Xposed,
then did a reboot.
All works well!
Click to expand...
Click to collapse
Pick your brain for a moment if you don't mind...
Still having issues with both methods... in TWRP, at the install image screen i'm only getting boot and recovery partition options, supposed to have system too right?
Fastboot it hangs for a moment at an error of something about invalid sparsing but continues to flash, apparently successfully, but when i reboot system it just boots back to recovery.
Chronzy said:
Pick your brain for a moment if you don't mind...
Click to expand...
Click to collapse
I am using this recovery
http://forum.xda-developers.com/oneplus-3/development/recovery-twrp-3-0-2-0-touch-recovery-t3402999
After switching to image install, I simply picked the system.img and was able to pick between system, boot and recovery.
Repeated for boot.img as boot...
AcmE85 said:
I am using this recovery
http://forum.xda-developers.com/oneplus-3/development/recovery-twrp-3-0-2-0-touch-recovery-t3402999
After switching to image install, I simply picked the system.img and was able to pick between system, boot and recovery.
Repeated for boot.img as boot...
Click to expand...
Click to collapse
Can we directly flash it over 3.2.4 in twrp ?
Any differences with the previous version guys?3.2.4....Tnx!!
AcmE85 said:
I am using this recovery
http://forum.xda-developers.com/oneplus-3/development/recovery-twrp-3-0-2-0-touch-recovery-t3402999
After switching to image install, I simply picked the system.img and was able to pick between system, boot and recovery.
Repeated for boot.img as boot...
Click to expand...
Click to collapse
I was on an older recovery, should have known... that did it, Thanks! :good:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Based on B140 of TL00/DL00 of Huawei P10+
Work on all Huawei P10 (any variant) and Huawei P10+ (any variant)
READ ALL POST FOR RESOLVE YOUR QUESTIONS.
Requisites:
Bootloader unlocked
Have TWRP Recovery
Download the files
Charecterist:
Call Recorder.
Intelligent Assistant.
Smart-E.
Custom Launcher Design
Advanced Reboot Menu.
K Settings (for custom settings)
Root.
DPI.
Better Battery Life.
And more, more....
Images:
The images are from the original post, in chinese, but the ROM are in all languajes, and the KangVip Settings APP on English.
Notes:
The fix contain the boot pre-rooted for run on all Europe/USA variants, with functional camera, and delete all chinese app's (know bloatware) and install the 360.apk modified for launch KangSettings app without waste resources, add's GPlay Services and GPlay Sotore, fixed the AdBlocker and Recovery Flash with Recovery Flasher on Kang-Vip, this fix it's from me, i created the fix for my P10+, and work for other's P10/+
How-To install:
Download the files
Copy to external storage
Reboot on TWRP
Install the "ROM" file
Install "FIX" file
Reboot
*The first run its slow (aprox 10 minuts).
Downloads:
ROM: https://mega.nz/#!wZcGRaaQ!pv5GD3Y9o6FvlNNc5TKDt1Nqp_1BLzQrABhJqiiL7hU
Fix: https://mega.nz/#!QU1m1DjR!Szmu5t0Owr7LV9w9MO0bZvV43YKL5H0X4C2DXyt3b-A
Regards.
Thank you so much. Theme are bugs or problem?
420hazee said:
Thank you so much. Theme are bugs or problem?
Click to expand...
Click to collapse
no problem there.
Hay man thanks.
Looks great.
Excellent! Used these roms on my old P9.
Which root does it use? SuperSU or Phh's?
When i flash i get error. why?
---------- Post added at 04:13 PM ---------- Previous post was at 04:08 PM ----------
Failed to mount '/system' (invalid argument). i get this error why?
Looks like I will have to give this a try soon ! Would love to increase battery life
420hazee said:
When i flash i get error. why?
---------- Post added at 04:13 PM ---------- Previous post was at 04:08 PM ----------
Failed to mount '/system' (invalid argument). i get this error why?
Click to expand...
Click to collapse
You need to mount "system" at the TWRP before starting to flash.
The button "Mount" is in the main menu in TWRP.
bozikakis said:
You need to mount "system" at the TWRP before starting to flash.
The button "Mount" is in the main menu in TWRP.
Click to expand...
Click to collapse
Obviously i had do it, but i got this error. Never seen before. I can't understand why.
420hazee said:
Obviously i had do it, but i got this error. Never seen before. I can't understand why.
Click to expand...
Click to collapse
I have same error message.
It's solving the latest version of stock recovery flash and then follow the instructions flashing the b140.
Stock recovery b140 B113
Badwolfe add the stock recovery link. Ok
M.KK said:
I have same error message.
It's solving the latest version of stock recovery flash and then follow the instructions flashing the b140.
Stock recovery b140 B113
Badwolfe add the stock recovery link. Ok
Click to expand...
Click to collapse
Wait what i have to do? Install the stock recovery on twrp? And after stock the kangvip rom and fix?
420hazee said:
Wait what i have to do? Install the stock recovery on twrp? And after stock the kangvip rom and fix?
Click to expand...
Click to collapse
Huawei haa.
No I saying to you
1 flash stock recovery b140.
2 flash twrp.
3 flash rom and fix.
Ok
M.KK said:
Huawei haa.
No I saying to you
1 flash stock recovery b140.
2 flash twrp.
3 flash rom and fix.
Ok
Click to expand...
Click to collapse
I'm onVKY-l29C636B124 will it work?
where can i find the stock recovery b140?
420hazee said:
I'm onVKY-l29C636B124 will it work?
where can i find the stock recovery b140?
Click to expand...
Click to collapse
Badwolfe
M.KK said:
Badwolfe
Click to expand...
Click to collapse
Well, so i have to flash in twrp the stock recovery b140 and, after in the stock recovery b140 reflash the twrp and, after when i will flash the kangvip rom i will get no error?
420hazee said:
Well, so i have to flash in twrp the stock recovery b140 and, after in the stock recovery b140 reflash the twrp and, after when i will flash the kangvip rom i will get no error?
Click to expand...
Click to collapse
Yes
Stock recovery is a partion file and Huawei update the firmware the change the partion user build number is chang to b140 ok.
Twrp working with stock recovery.
Then you flash the twrp you have already stock recovery one side. Ok
And i think I guide to be a school child. Ok
M.KK said:
Yes
Stock recovery is a partion file and Huawei update the firmware the change the partion user build number is chang to b140 ok.
Twrp working with stock recovery.
Then you flash the twrp you have already stock recovery one side. Ok
And i think I guide to be a school child. Ok
Click to expand...
Click to collapse
I don't get it still error "can't mount system" Can you tell me about detail, please
my devices P10+ VKY-L29C636B133
BadWolfYe said:
Images:
The images are from the original post, in chinese, but the ROM are in all languajes, and the KangVip Settings APP on English.
Regards.
Click to expand...
Click to collapse
Bro, it there any chance to see the screenshots of your firmware in english?
Here is my B140 but i use different method from the OP i use VKY system flash directly from fastboot.
Sent from my VKY-L29 using Tapatalk
bozikakis said:
Bro, it there any chance to see the screenshots of your firmware in english?
Click to expand...
Click to collapse
It's fully English and rooted.
You can uninstall Chinese applicants.
And b happy all thing in there you can wont.
This is the good way to flashing the b140 only system can flash. Don't boot. Img
Hi,
I have a rooted NEM-L51 (with TWRP 3.1.1-0 as recovery) running Android 7.0/EMUI 5.0 (build number NEM-L51C432B350).
A new OTA update is available (build number NEM-L51C432B355) but after downloading and rebooting to recovery (TWRP) to apply it, it fails with the following error:
Code:
script aborted: assert failed: block_image_verify("/dev/block/bootdevice/by-name/system", package_extract_file("system.transfer.list"), "system.new.dat", "system.patch.dat")
assert failed: block_image_verify("/dev/block/bootdevice/by-name/system", package_extract_file("system.transfer.list"), "system.new.dat", "system.patch.dat")
Updater process ended with ERROR: 7
I googled it but couldn't find anything that seems useful. You'll find attached the complete log (I was using TWRP 3.1.0-2 at the time and has since upgraded, thinking it could be related to it).
Does anyone have any idea about what's going wrong here?
Could it be because the system partition has been modified in the process of rooting the phone (I'm thinking about that because of the 'block_image_verifiy(.../system...)') — note that I was able to apply OTA updates on my rooted device in the past?
Thanks!
You have magisk or SuperSU?!
why you trying to install updates on twrp....
Try useing stock recovery from the update.
PalakMi said:
You have magisk or SuperSU?!
Click to expand...
Click to collapse
SuperSU, v2.82.
thelous said:
why you trying to install updates on twrp....
Click to expand...
Click to collapse
It reboots automatically under TWRP after downloading the update. If I choose to apply the update later, I can force it to boot to Huwaei eRecovery but I'm not sure I can apply the update from here without wiping my /data ?
As far as I remember it didn't reboot to TWRP for the previous OTA updates but since it seems to be executing a script for the update what difference does it make if it's executed from TWRP?
AlexMihai26 said:
Try useing stock recovery from the update.
Click to expand...
Click to collapse
I'm not sure about what you mean: do you suggest I try to extract the Honor recovery from the update files and flash it using fastboot?
Try magisk!
In order to do a normal ota update you need the stock recovery. To update with twrp you need to have the zip file to flash. (someone please confirm if it is zip or update.app). Are you using the openkirin twrp?
fishnchips2 said:
In order to do a normal ota update you need the stock recovery. To update with twrp you need to have the zip file to flash. (someone please confirm if it is zip or update.app). Are you using the openkirin twrp?
Click to expand...
Click to collapse
Update.app with stock recovery, zip with twrp
sclarckone said:
SuperSU, v2.82.
It reboots automatically under TWRP after downloading the update. If I choose to apply the update later, I can force it to boot to Huwaei eRecovery but I'm not sure I can apply the update from here without wiping my /data ?
As far as I remember it didn't reboot to TWRP for the previous OTA updates but since it seems to be executing a script for the update what difference does it make if it's executed from TWRP?
I'm not sure about what you mean: do you suggest I try to extract the Honor recovery from the update files and flash it using fastboot?
Click to expand...
Click to collapse
Yep
PalakMi said:
Try magisk!
Click to expand...
Click to collapse
I'm OK to switch to Magisk if necessary but why would it solves my error during update? Is it because Magisk doesn't touch the /system partition (I don't even know if SuperSU did)?
Besides, this thread says I must restore my stock boot image and I don't have it.
fishnchips2 said:
In order to do a normal ota update you need the stock recovery. To update with twrp you need to have the zip file to flash.
Click to expand...
Click to collapse
OK. What's "strange" about this is that I was able to apply the last two OTA updates even though I did have a custom recovery at the time -- and I had to flash TWRP and root again after each of these updates.
Anyway, I got the updates files (by looking for the files mentioned in the TWRP log) and they already are zip files (the error I get occurs while executing the first) :
update.zip (around 180MB), which contains among other files the UPDATE.APP file.
update_data_public.zip (around 13 MB) which seems to contain updates for Honor system apps.
update_NEM-L51_hw_eu.zip (around 16MB), which might be a firmware update given the name?
Are these the files I'm supposed to flash with TWRP?
fishnchips2 said:
Are you using the openkirin twrp?
Click to expand...
Click to collapse
Yes.
@AlexMihai26: I've looked into the zip files mentioned above and didn't spot any file that should be the stock recovery. Do you have any idea where it should be located?
And thank you all for your help, of course! ^^
I haven't flashed an update with TWRP myself but I think the first file is the critical one and the others are regional patches and app packages. I think you should flash them in the order: Update.zip, update_nem-l51_hw_eu.zip then update_data_public.zip. However I should stress that I haven't done it myself.
As for the files you're looking for, https://forum.xda-developers.com/honor-5c/development/repository-honor-5c-file-depot-t3640712 should contain most of the necessary files but oddly doesn't have a stock Nougat recovery...
Twrp and root were lost during the update because the rom replaces them with its own files in the first boot. I don't know why the ota updates worked before.
Because you can hide root with magisk.
fishnchips2 said:
I haven't flashed an update with TWRP myself but I think the first file is the critical one and the others are regional patches and app packages. I think you should flash them in the order: Update.zip, update_nem-l51_hw_eu.zip then update_data_public.zip. However I should stress that I haven't done it myself.
Click to expand...
Click to collapse
Just to be clear, these files I mentioned in my previous post are the one downloaded by the OTA updater of EMUI (and TWRP fails on flashing the first one, update.zip) so I shouldn't flash them with TWRP, right?
I'm a bit confused about this because if ZIP files are supposed to be used with TWRP and the APP files with the stock recovery, why did the EMUI OTA updater download ZIP files (I would expect it to download files as if I had a stock recovery)?
fishnchips2 said:
As for the files you're looking for, https://forum.xda-developers.com/honor-5c/development/repository-honor-5c-file-depot-t3640712 should contain most of the necessary files but oddly doesn't have a stock Nougat recovery...
Click to expand...
Click to collapse
So these are the files flashable with TWRP (in that case I don't need the stock recovery)? The ones corresponding to the upgrade I'm looking for seem to be the following:
The OTA one seems to be exactly the same update.zip that was downloaded by the EMUI OTA updater. Should I try the FullOTA variant?
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Sorry if I sound a bit meticulous but I'd rather not brick my phone and understand what I'm doing. ^^
The error you're getting is error 7 which means the rom is supposedly incompatible with your device. As this is the official update, I have no idea why this error is coming up. I think that once you get past that error, twrp should be fine flashing the zip file.
The difference between ota files and fullota files is that a fullota contains most of the files needed by the rom while the ota only replaces files that have changed. As you are on b350 nougat already, an update to b355 should only need a normal ota update.
Don't worry about asking questions, it's good that you're cautious with your phone.?
---------- Post added at 09:52 PM ---------- Previous post was at 09:45 PM ----------
EDIT!!!
Sorry I was wrong in the previous reply. Twrp can't flash an ota update because it only replaces some files, whereas twrp will flash the entire system. However, a fullota file should work (haven't tried??).
This also explains why it had error 7: the manufacturer doesn't want someone accidentally flashing an incremental update as a full rom.
More info is here : https://twrp.me/faq/officialota.html
---------- Post added at 10:01 PM ---------- Previous post was at 09:52 PM ----------
Further edit : I believe that you have to wipe certain partitions (system and cache?) before flashing an update because 'dirty flashing' doesn't always fully replace everything and causes issues later. However this may be different for stock roms. Nevertheless, always make a backup!
Hopefully final edit: a dirty flash means that you don't wipe data first. This should be fine for an official update. Opinions vary on wiping system, cache and dalvik but I think the recovery should do that for you.
Yes, as you said TWRP flashes the entire system, that's you need fullOTA,?.
PalakMi said:
Yes, as you said TWRP flashes the entire system, that's you need fullOTA,?.
Click to expand...
Click to collapse
Yup I believe so
Honor devices are one of the most complicated when it comes to flashing ROMs.
I know ? at least it isn't the s8 exynos version. I hear you can't even unlock the bootloader on that.
Yeah, however, I wish honor makes it simple with upcoming devices (like OnePlus)
sclarckone said:
I'm OK to switch to Magisk if necessary but why would it solves my error during update? Is it because Magisk doesn't touch the /system partition (I don't even know if SuperSU did)?
Besides, this thread says I must restore my stock boot image and I don't have it.
OK. What's "strange" about this is that I was able to apply the last two OTA updates even though I did have a custom recovery at the time -- and I had to flash TWRP and root again after each of these updates.
Anyway, I got the updates files (by looking for the files mentioned in the TWRP log) and they already are zip files (the error I get occurs while executing the first) :
update.zip (around 180MB), which contains among other files the UPDATE.APP file.
update_NEM-L51_hw_eu.zip (around 16MB), which might be a firmware update given the name?
Are these the files I'm supposed to flash with TWRP?
Yes.
@AlexMihai26: I've looked into the zip files mentioned above and didn't spot any file that should be the stock recovery. Do you have any idea where it should be located?
And thank you all for your help, of course! ^^
Click to expand...
Click to collapse
Use Huawei update extractor,and you should find a recovery.img
NOW WE GOT THE ROOT!
First, I was been able to get the bootloader unlocked by standard unlocking method. Head to this Thread [url]https://forum.xda-developers.com/zenfone-4-max/how-to/guide-how-to-unlock-bootloader-zc554kl-t3677270[/URL]
And now, We are able to get root via Magisk Manager that will not mess with our Asus Stock ROM in benefit systemless root from Magisk. Thanks for @topjohnwu !!
You can get more information about Magisk in this thread:
[url]https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445[/URL]
And now, there are few steps for how to get systemless root on our device.
1. You need to extract the boot.img of you current ROM which can be obtained in the flashable ZIP made by Asus
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
2. After getting the boot.img of your current ROM, download Magisk Manager and then select install in the app. Select the Patch boot image file, and search the boot.img from the Step 1.
Wait until you get automatic process running and get you a patched_boot.img within the directory cantaining that.
3. The last, Just copy to your computer and flash out the patched_boot.img to your device with fastboot command, restart then you'll get the magisk manager work.
type this command on fastboot interface
fastboot flash boot *.img
Note:
*=Name and location of your patched_boot.img
Click to expand...
Click to collapse
That's all that you must do for gaining root access. I don't know and I don't care to what happened with your device or what is that you blame about. Just take the risk alone!
:silly::silly::silly:REMEMBER! ALWAYS DO WITH YOUR OWN RISK! I'M NOT RESPONSIBLE AT ALL! WHAT YOU'VE DONE IS DONE!:silly::silly::silly:
Best regards.:good::highfive:
Nice job! Say, will this work on the Zenfone 4 Max Pro? Specifically, model ASUS_X00ID. It's a different model than the Zenfone 4 Max, but they share the same ZC554KL code (whatever that is.)
TheStrangeStarfish said:
Nice job! Say, will this work on the Zenfone 4 Max Pro? Specifically, model ASUS_X00ID. It's a different model than the Zenfone 4 Max, but they share the same ZC554KL code (whatever that is.)
Click to expand...
Click to collapse
You can try unlocking the bootloader first. Then try this patching method. The msm8917 and msm8937 just a same structured chispset. Asus had the two config at the source code at once. Go and try. And report here too.
Unfortunately, it doesn't work. Can't get the bootloader to unlock. I go as far as fastboot oem get_unlock_key , which gives me an "OKAY" but when I enter "fastboot oem unlock-go" if gives me a "FAILED (remote:unknown command)
I am sure I installed ADB and Fastboot correctly. At least I hope I did. I'd be happy to know that I didn't install fastboot correctly.
---------- Post added at 10:57 AM ---------- Previous post was at 10:44 AM ----------
TheStrangeStarfish said:
Unfortunately, it doesn't work. Can't get the bootloader to unlock. I go as far as fastboot oem get_unlock_key , which gives me an "OKAY" but when I enter "fastboot oem unlock-go" if gives me a "FAILED (remote:unknown command)
I am sure I installed ADB and Fastboot correctly. At least I hope I did. I'd be happy to know that I didn't install fastboot correctly.
Click to expand...
Click to collapse
I lied. Apparently IT WORKS.
I just did this in particular:
Typed: fastboot reboot bootloader (I did not do this at first, I went to bootloader manually)
Typed: fastboot oem get_unlock_key (got the okay)
Typed fastboot oem unlock (Got a "Device already : Unlocked!")
Rebooted to be sure. DEVICE STATE is UNLOCKED
Got a pic for proof
Edit: Pics don't upload properly. URL -https://pasteboard.co/GM8QVeF.jpg
Also I can't see the images on your guide.
TheStrangeStarfish said:
Unfortunately, it doesn't work. Can't get the bootloader to unlock. I go as far as fastboot oem get_unlock_key , which gives me an "OKAY" but when I enter "fastboot oem unlock-go" if gives me a "FAILED (remote:unknown command)
I am sure I installed ADB and Fastboot correctly. At least I hope I did. I'd be happy to know that I didn't install fastboot correctly.
---------- Post added at 10:57 AM ---------- Previous post was at 10:44 AM ----------
I lied. Apparently IT WORKS.
I just did this in particular:
Typed: fastboot reboot bootloader (I did not do this at first, I went to bootloader manually)
Typed: fastboot oem get_unlock_key (got the okay)
Typed fastboot oem unlock (Got a "Device already : Unlocked!")
Rebooted to be sure. DEVICE STATE is UNLOCKED
Got a pic for proof
Edit: Pics don't upload properly. URL -https://pasteboard.co/GM8QVeF.jpg
Also I can't see the images on your guide.
Click to expand...
Click to collapse
I dont have other device to picture it and forgot to screenshot all the fastboot attempt. But I sure that my way to unlock bootloader is work. Sorry for the guide, you can post the picture at the guide to unlock to make sure it works.
aaaaaaziskurnia said:
I dont have other device to picture it and forgot to screenshot all the fastboot attempt. But I sure that my way to unlock bootloader is work. Sorry for the guide, you can post the picture at the guide to unlock to make sure it works.
Click to expand...
Click to collapse
Okay, my bad. Apparently my browser's mucking things up. I can see the images clearly now. Gonna try for root. Will report soon :good:
TheStrangeStarfish said:
Okay, my bad. Apparently my browser's mucking things up. I can see the images clearly now. Gonna try for root. Will report soon :good:
Click to expand...
Click to collapse
Okay, write down the reports here. That can help the others.
We have Root! Thank you!
So far, guide is easy enough once you have everything you need.
Proof of Root
aaaaaaziskurnia said:
NOW WE GOT THE ROOT!
First, I was been able to get the bootloader unlocked by standard unlocking method. Head to this Thread [url]https://forum.xda-developers.com/zenfone-4-max/how-to/guide-how-to-unlock-bootloader-zc554kl-t3677270[/URL]
And now, We are able to get root via Magisk Manager that will not mess with our Asus Stock ROM in benefit systemless root from Magisk. Thanks for @topjohnwu !!
You can get more information about Magisk in this thread:
[url]https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445[/URL]
And now, there are few steps for how to get systemless root on our device.
That's all that you must do for gaining root access. I don't know and I don't care to what happened with your device or what is that you blame about. Just take the risk alone!
:silly::silly::silly:REMEMBER! ALWAYS DO WITH YOUR OWN RISK! I'M NOT RESPONSIBLE AT ALL! WHAT YOU'VE DONE IS DONE!:silly::silly::silly:
Best regards.:good::highfive:
Click to expand...
Click to collapse
Do you have boot.img from UL-ASUS_X00ID-WW-14.2016.1708.156-user.zip file? I've downloaded several times but ended up the zip file is corrupt.
komtek said:
Do you have boot.img from UL-ASUS_X00ID-WW-14.2016.1708.156-user.zip file? I've downloaded several times but ended up the zip file is corrupt.
Click to expand...
Click to collapse
You can bootup with older version boot.img. earlier 153 version booted up. You can use that by using "fastboot boot boot.img" without flashing to emmc. Then after booting the 153 boot.img, you can patch the 156 version that placed on mmcbkl0p24
komtek said:
Do you have boot.img from UL-ASUS_X00ID-WW-14.2016.1708.156-user.zip file? I've downloaded several times but ended up the zip file is corrupt.
Click to expand...
Click to collapse
had the same problem. Fixed it by opening the zip on winrar, going to tools and selecting repair archive.
TheStrangeStarfish said:
had the same problem. Fixed it by opening the zip on winrar, going to tools and selecting repair archive.
Click to expand...
Click to collapse
I didn't recommend the 156 zip stock because that messed up by asus it self. I use the 153 zip file
hmm, I used the 156 zip stock in particular. Is there anything I should be concerned about? Everything seems okay so far.
TheStrangeStarfish said:
hmm, I used the 156 zip stock in particular. Is there anything I should be concerned about? Everything seems okay so far.
Click to expand...
Click to collapse
Don't ever try to flash that zip to your phone. I'm wandering why the latest version just 1,32 Gb when the earlier version is 1,69 Gb. Maybe corrupted or some thing. The boot.img must be okay for flash, but other than that of course not. The boot.img is on the header of the zip so it's safe and doesn't corrupted.
aaaaaaziskurnia said:
Don't ever try to flash that zip to your phone. I'm wandering why the latest version just 1,32 Gb when the earlier version is 1,69 Gb. Maybe corrupted or some thing. The boot.img must be okay for flash, but other than that of course not. The boot.img is on the header of the zip so it's safe and doesn't corrupted.
Click to expand...
Click to collapse
Okay, good to know. All I used was the boot.img anyway.
Thanks for the heads-up!
OTA Update
Hi mate! As we know update v.158 is released. Just wanna ask, can we apply this update safely if my device is rooted? Should I unroot the device first so I can install this update?
---------- Post added at 07:33 AM ---------- Previous post was at 07:28 AM ----------
komtek said:
Hi mate! As we know update v.158 is released. Just wanna ask, can we apply this update safely if my device is rooted? Should I unroot the device first so I can install this update?
Click to expand...
Click to collapse
I tried to apply the update via OTA, but it failed. Luckily my device doesn't bricked :silly:
komtek said:
Hi mate! As we know update v.158 is released. Just wanna ask, can we apply this update safely if my device is rooted? Should I unroot the device first so I can install this update?
---------- Post added at 07:33 AM ---------- Previous post was at 07:28 AM ----------
I tried to apply the update via OTA, but it failed. Luckily my device doesn't bricked :silly:
Click to expand...
Click to collapse
Any modification will breaks OTA. That's was the risk if you have root.
Bro i have some question. Can we just root asus zenfone 4 max pro without installing twrp inside ? Thanks
Hallo guys... Theres new update 160
Is it worth to try root with that version?
christotoruan said:
Bro i have some question. Can we just root asus zenfone 4 max pro without installing twrp inside ? Thanks
Click to expand...
Click to collapse
At now still no. Android nowadays using verity that verifying the /system partitions that makes our device hangs or brick if there is a modification. That's means to us to using twrp to install magisk that can handle modification systemlessly. So the device won't brick. SuperSu itself using systemless injection.
Disclaimer: No guarantees. Follow at your own risk. I am not responsible for bricked phones.
Credits to 4PDA
Prerequisites:
Knowledge of OEM unlocking from Developer options, adb, and fastboot
Knowledge of QPST in case you encounter bootloop, so you can revert to a reliable stock ROM
Unlocked bootloader (from here)
1) Get your bootloader unlocked, if you haven't already.
- Visit https://www.zui.com/iunlock
- Enter the IMEI1 (Second number when you call *#06# with the phone)
- Enter the Device ID from the Bootloader/Fastboot (Hold VOL- and Power, while device is off)
- Enter your email and captcha and set the checkmark to acknowledge voiding your warranty.
- If you get an error saying that your IMEI1 is wrong, put in a sim card and wait a few hours. If it still doesn't work, write an email to [email protected]
- In the developer settings in android, enable usb debugging and oem unlock.
- Flash the sn.img file you receive with fastboot (again, hold vol- and power while the device is off). Command is 'fastboot flash unlock sn.img'. You need compatible usb drivers, qualcom drivers and adb/fastboot to do that. Use google or write me a PM if you have trouble with that.
- execute 'fastboot oem unlock-go'
- This allows you to use fastboot to flash custom system/boot/vendor/vbmeta images
Click to expand...
Click to collapse
@wzsx150's recovery-TWRP-3.3.1-1015-LENOVO_Z5S-CN-wzsx150.img MEGA Google Drive
@wzsx150's TWRP for Android 10 TWRP-3.3.2B-0508-LENOVO_Z5S-10.0-CN-wzsx150-fastboot.7z (extract the IMG file and flash using fastboot)
3) Now you can flash TWRP.
- Download ...
- Flash it from the Bootloader with 'fastboot flash recovery recovery-TWRP-3.3.1-1015-LENOVO_Z5S-CN-wzsx150.img'
- Press VOL UP / VOL DOWN to navigate to recovery.
Click to expand...
Click to collapse
11.3.169: L78071_11.3.169_DEV_FullOTA.zip
11.5.096 Update: ZUI_11.3.169_DEV_TO_ZUI_11.5.096_ST.zip
11.5.111 Update: ZUI_11.5.096_TO_ZUI_11.5.111_ST.zip
Other files, use at your own risk
Disable_Dm-Verity_ForceEncrypt_08.18.2019.zip
Official TWRP for jd2019
In recovery, Format data, then wipe Dalvik/ART Cache, Cache, Data
Reboot to recovery
Install in order, without rebooting, 11.3.169 -> 11.5.096 Update -> 11.5.111 Update.
Install Magisk 20.4
Install TWRP for Android 10 (above) using fastboot if the update replaces stock recovery after rebooting
Edited out from original
Wipe Data and flash Disable_Dm-Verity_ForceEncrypt_08.18.2019.zip
In order not to encrypt Data in the future, install Official TWRP immediately after installing updates. Install > Install Image > twrp-3.3.1-0-jd2019.img
Install GApps
Note: I do not know if the 11.5 update relocks the bootloader. It doesn't lock the bootloader.
I had bootloop from OpenGApps. 4PDA post advises to use BiTGApps. You can install Google Play Store from the built-in Lenovo App Center and that's what I did.
Haven't tried disabling dm-verity and forceencrypt.
Good job, my man, I'll check it out tonight and prepare ourselves an updateable package for people coming from any rom to avoid the hassle of going through all of that. As soon as I get it working will release a new TWRP for Android 10.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
carlshark said:
View attachment 5036881
Click to expand...
Click to collapse
Nice job man, so the update works as it should? I'm patching the images and will upload a full ota update to make it easier to move between Pie and 10. Regarding recoverys, did you test any twrp? Any decryption working? What about this official twrp, does it actually work? Thanks for the files man, this will make everything much easier
jacoghi said:
Nice job man, so the update works as it should? I'm patching the images and will upload a full ota update to make it easier to move between Pie and 10. Regarding recoverys, did you test any twrp? Any decryption working? What about this official twrp, does it actually work? Thanks for the files man, this will make everything much easier
Click to expand...
Click to collapse
I've been using the phone on 11.5.111 for a couple of days now.
I flashed both the 3.3.2 TWRP of @wzsx150 and the official TWRP and they seem to be working. I didn't turn off encryption so it seems to work well.
Happy to have helped in a small way. Thank you for your hard work!
links not works
vesdan said:
links not works
Click to expand...
Click to collapse
Thanks for the heads up, apparently the original poster removed the links. Will be uploading the ones I used.
Reuploading done.
Thank you very much
Thanks for the rom my friend.
Can you please upload the latest update cause i am rooted and it cannot be installed via the system.
Also guys ,does anyone knows if i can put the latest android 10 with multilanguage rom ?Thank you for everything ,i appreciate.
thx for the post, i am wondering if the ota will be avaliable, because the bootloader unlock site does not approve my imei number
sorry guys, i rushed and flashed the gapps and now facing a bootloop, i prepared qpst and a stock rom but i verz rom i am missing a content.xml file, can anyone please help me?
galardo_2 said:
sorry guys, i rushed and flashed the gapps and now facing a bootloop, i prepared qpst and a stock rom but i verz rom i am missing a content.xml file, can anyone please help me?
Click to expand...
Click to collapse
https://mega.nz/folder/PegDDQ7I#bmCCIt1lAWAe7ui_gkmwSQ/folder/fOAQ1QCa
here is many ROMS
Do not install gapps on ZUI !!!!
vesdan said:
https://mega.nz/folder/PegDDQ7I#bmCCIt1lAWAe7ui_gkmwSQ/folder/fOAQ1QCa
here is many ROMS
Do not install gapps on ZUI !!!!
Click to expand...
Click to collapse
but the qpst app need an aditional content.xml file, where can i get one
Install global via fastboot, all is included or in qfil ROM is all in zip file
vesdan said:
Install global via fastboot, all is included or in qfil ROM is all in zip file
Click to expand...
Click to collapse
I tried and failed again
i tired and failed again
galardo_2 said:
thx for the post, i am wondering if the ota will be avaliable, because the bootloader unlock site does not approve my imei number
Click to expand...
Click to collapse
I tried unlocking 2 Lenovo phones. The first attempt had sent me an email, but the second attempt did not. The unlock procedure went through though. So I tried changing the link provided in the first email http://cdn.zui.lenovomm.com/developer/lenovoboot/xxxxxxxx/sn.img (xxxxxxxx - serial number of phone) and it worked. This might not work for you though.
As for the OTA, I really am not sure... Probably
carlshark said:
I tried unlocking 2 Lenovo phones. The first attempt had sent me an email, but the second attempt did not. The unlock procedure went through though. So I tried changing the link provided in the first email http://cdn.zui.lenovomm.com/developer/lenovoboot/xxxxxxxx/sn.img (xxxxxxxx - serial number of phone) and it worked. This might not work for you though.
As for the OTA, I really am not sure... Probably
Click to expand...
Click to collapse
after a few atempts (3-4 days) the imei number got accepted, but now i have another problem as you can see, i flashed the gapps and now i have the bootloop and i dont have a clue how to undone it
hello friends I have all the updates installed, but it tells me that there is a new one, where can I download it?
On the other hand, what difference is there between installing by twrp and qfill?
galardo_2 said:
i tired and failed again
Click to expand...
Click to collapse
This is problem with program, drivers sahara. Try fastboot