TWRP Error 9 while flashing stock recovery - Huawei P9 Questions & Answers

***edit to title: TWRP Error 9 while flashing stock ROM
I recently installed Magisk but it caused my EVA-AL00 to become stuck at the Huawei logo.
I have TWRP installed and I tried to flash update.zip, but it threw:
Full SELinux support is present.
MTP Enabled
Installing zip file '/external_sd/update.zip'
Checking for Digest file...
Skipping Digest check: no Digest file found
script succeeded: result was [/data]
script succeeded: result was [false]
writing radio image...
check_write_data_to_partition, write data error
update_huawei_pkg_from_ota_zip: update package from zip failed
E:unknown command [errno]
Update process ended with ERROR: 9
Error installing zip file '/external_sd/update.zip
Updating partition details...
...done
How do I fix this? Thank you!

george.tian said:
***edit to title: TWRP Error 9 while flashing stock ROM
I recently installed Magisk but it caused my EVA-AL00 to become stuck at the Huawei logo.
I have TWRP installed and I tried to flash update.zip, but it threw:
Full SELinux support is present.
MTP Enabled
Installing zip file '/external_sd/update.zip'
Checking for Digest file...
Skipping Digest check: no Digest file found
script succeeded: result was [/data]
script succeeded: result was [false]
writing radio image...
check_write_data_to_partition, write data error
update_huawei_pkg_from_ota_zip: update package from zip failed
E:unknown command [errno]
Update process ended with ERROR: 9
Error installing zip file '/external_sd/update.zip
Updating partition details...
...done
How do I fix this? Thank you!
Click to expand...
Click to collapse
I don't understand why you every day open a new thread, basically for the same problem - bricked AL00.
Also, which firmware version do you want to (re)install, is it Oreo (maybe b540) or Nougat (maybe b399)
If your phone is really AL00 (or it was previously branded to) and if your last installed/working stock firmware was Oreo (between b528 and b540), and if you didn't change things by trying to flash some Nougat firmwares:
-You can use Service Restoration b528 package as described
https://forum.xda-developers.com/showpost.php?p=78721851&postcount=1381
- Instead of keeping and copying to dload
floder on external SD two files update_sd.zip and EVA-AL10_all_cn (since I was restoring AL10, not AL00), you will have to keep and copy to dload folder on external SD: update_sd.zip and EVA-AL00_all_cn
- Service restoration package is simply flashed by dload method (no need for TWRP), and once b528 is restored you will start receiving OTA updates up to the last official stock firmware for your AL00 (and it's last OTA patch)

zgfg said:
I don't understand why you every day open a new thread, basically for the same problem - bricked AL00.
Also, which firmware version do you want to (re)install, is it Oreo (maybe b540) or Nougat (maybe b399)
If your phone is really AL00 (or it was previously branded to) and if your last installed/working stock firmware was Oreo (between b528 and b540), and if you didn't change things by trying to flash some Nougat firmwares:
-You can use Service Restoration b528 package as described
https://forum.xda-developers.com/showpost.php?p=78721851&postcount=1381
- Instead of keeping and copying to dload
floder on external SD two files update_sd.zip and EVA-AL10_all_cn (since I was restoring AL10, not AL00), you will have to keep and copy to dload folder on external SD: update_sd.zip and EVA-AL00_all_cn
- Service restoration package is simply flashed by dload method (no need for TWRP), and once b528 is restored you will start receiving OTA updates up to the last official stock firmware for your AL00 (and it's last OTA patch)
Click to expand...
Click to collapse
Hi zgfg, sorry for the multiple posts - I was trying to solve the Magisk problem yesterday, but now I'm just trying to reset everything.
- The phone was bought in China as AL00 - no rebranding done.
- I wish to reinstall Oreo, and B540 was the latest version I had before the phone was bricked.
- I have not flashed Nougat apart from the OTA update years ago which upgraded Marshmellow to Nougat
Are you saying the EVA-AL00_all_cn.zip is also in the 6GB Restoration B528 package you've linked?
Thank you for your help

george.tian said:
Hi zgfg, sorry for the multiple posts - I was trying to solve the Magisk problem yesterday, but now I'm just trying to reset everything.
- The phone was bought in China as AL00 - no rebranding done.
- I wish to reinstall Oreo, and B540 was the latest version I had before the phone was bricked.
- I have not flashed Nougat apart from the OTA update years ago which upgraded Marshmellow to Nougat
Are you saying the EVA-AL00_all_cn.zip is also in the 6GB Restoration B528 package you've linked?
Thank you for your help
Click to expand...
Click to collapse
I have already deleted everything I didn't need
Edit: It was, found a screenshot (attached)

Have you tried, were you able to recover AL00 Oreo?

zgfg said:
Have you tried, were you able to recover AL00 Oreo?
Click to expand...
Click to collapse
No answer...
Thanks for your engagement to help :good:
But some User's do not seem to appreciate it

Related

Update p9 lite nougat ota "s ​​no officials

I was given a link. cronociclope Senior Member
I tested it. 100 for 100 on :cyclops:
It is necessary to return or to be emu 4. (MM).
Have the unlock code. (Bootloader).
Have downloaded the full firmware (2 files) Full-ota-mf-pv that twrp can install.
And have downloaded the firmware update, full full-ota-mf (no pv). (3 files).
pc+ winzip+ twrp (chinois), carteSD,
regard
https://www.youtube.com/watch?v=oTBvz71l4s0&t=1s
So on the pc, with winzip. Because with winrar for me it does not want to transfer large volumes. :
_ Downloaded a firmware emui 5. Full-ota-mf-pv for your device (it's a firmware in two files, which twrp for MM can install).
_______ update.zip and datafull hw-eu.zip
Uploaded emui update 5. Full-ota-mf not written pv and that does not share ota. But we want it. : (this is a firmware in three files).
________update.zip, public file and data hw-eu.zip
_ Open the update file of the pv version and delete the update.app, then open the update of the no pv version, and transfer update.app in the pv version.
Do the same thing with the datafull file hw-eu and data hw-eu.
In the public zip, there is a data folder with the product and system files.
In the zip data hw-eu, there is a data folder with the cust and version.
We can also transfer them.
In the zip data full hw-eu to data / hw_init :cyclops:
_copy your two new .zip files onto the SD card.
_start the phone in recovery twrp MM.
_ Go to wipe, advanced wipe, check all except well-sure sd card, and wipe to wipe.
_allez to install, installed both zip, it will show you two errors ignore them.
_allez to reboot, reboot system.
Hello
in the public zip, there is a data folder with the product and system files.
In the zip data hw-eu, there is a data folder with the cust and version.
We can also transfer them.
In the zip data full hw-eu to data / hw_init
regard
2017.09.20 VNS-L21C432B382 http://update.hicloud.com:8180/TDS/data/files/p3/s15/G1903/g1755/v97161/f1/full/update.zip
filelist http://update.hicloud.com:8180/TDS/data/files/p3/s15/G1903/g1755/v97161/f1/full/filelist.xml
B383 was released on Firmware Finder.
Install the OTA one (mb version).
Johnny TDN said:
B383 was released on Firmware Finder.
Install the OTA one (mb version).
Click to expand...
Click to collapse
yes, full-ota-mf
2017.09.21 VNS-L21C432B383 http://update.hicloud.com:8180/TDS/data/files/p3/s15/G1903/g1755/v97303/f1/full/update.zip
filelist http://update.hicloud.com:8180/TDS/data/files/p3/s15/G1903/g1755/v97303/f1/full/filelist.xml
and
your pkg install full-ota-mf-pv vns-l21c432b371
2017.03.21 VNS-L21C432B371 http://update.hicloud.com:8180/TDS/data/files/p3/s15/G753/g104/v89798/f2/full/update.zip
filelist http://update.hicloud.com:8180/TDS/data/files/p3/s15/G753/g104/v89798/f2/full/filelist.xml
got an ota update b383.
failed at 32%
gg huawei
Johnny TDN said:
got an ota update b383.
failed at 32%
gg huawei
Click to expand...
Click to collapse
strange 32%
with this method, I can even install p10 lite.
can be checked, the update.app that is the good you place in the update.zip
go to wipe before installing update.zip edit this seems important.
2017.08.30 VNS-L31C432B390 http://update.hicloud.com:8180/TDS/data/files/p3/s15/G1903/g1755/v97199/f1/full/update.zip
filelist http://update.hicloud.com:8180/TDS/data/files/p3/s15/G1903/g1755/v97199/f1/full/update.zip
If I am rooted and I have TWRP, can I install the update?
I installed update without come back in mm and without reset phone by this steps:
1)flash Hassan twrp recovery
2)download the 3 update file
3)extract update.app from update.zip and from update_full_VNS-L11_hw_eu.zip.
4)With Huawei update extractor extract the image file (system boot vendor cust version misc) from the two update.app and flash It with recovery. The product Image is not falshable, you have to extract this with ext4imageview
5)do a wipe cache and davilk and flash magisk zip to root. Install magisk manager (with the new update b391 i have some problem with supersu)
6)copy the file extract from product Image and data file extract from update_full_VNS-L11_hw_eu.zip and data_full_pubblic.zip in /data and in /product partition with solid Explorer with root permission.
Reboot
It's ok
http://oi63.tinypic.com/29cncx4.jpg
Paolo83 said:
I installed update without come back in mm and without reset phone by this steps:
1)flash Hassan twrp recovery
2)download the 3 update file
3)extract update.app from update.zip and from update_full_VNS-L11_hw_eu.zip.
4)With Huawei update extractor extract the image file (system boot vendor cust version) from the two update.app and flash It with recovery. The product Image is not falshable, you have to extract this with ext4imageview
5)do a wipe cache and davilk and flash magisk zip to root. Install magisk manager (with the new update b391 i have some problem with supersu)
6)copy the file extract from product Image and data file extract from update_full_VNS-L11_hw_eu.zip and data_full_pubblic.zip in /data and in /product partition with solid Explorer with root permission.
It's ok
Click to expand...
Click to collapse
Hello
Hello
ALSO Product.img of update.zip?
Because, he does not want, that's why, I always go to MM.
bad reading sorry,
Chisetdel31260 said:
Hello
ALSO Product?
Click to expand...
Click to collapse
We are not able ti flash product with this recovery, we can try to ask information to Hassan. The solution is to extract product.img with Android ICS JB EXT4 imagefile unpacker and copy the folder in /product with solid Explorer and root permission. It replace the file with the correct attribute. You have to use this metod to copy data folder
Paolo83 said:
We are not able ti flash product with this recovery, we can try to ask information to Hassan. The solution is to extract product.img with Android ICS JB EXT4 imagefile unpacker and copy the folder in /product with solid Explorer and root permission. It replace the file with the correct attribute. You have to use this metod to copy data folder
Click to expand...
Click to collapse
I've already asked him to hassan and he added to install twrp product image, but its not working.
I tried to copy pasted already with a file explorer, but every time, things break. (either with force close parameters, or force close camera, or boot-animation disappears and becomes android).
there is always something wrong.
Yes, we leave from MM everything is ok, clean.
You have to use solid Explorer It works!! With this procedure In five minutes I upgrade to last version
Managed to update to b382.
Seems stable and somehow, the battery is much better o^o
go
time to download, c432b390.
And to transfer everything in the b370 zip, then to go back to c432b160, I installed it correctly.
so this version is emu 5.0.1, patch September 1, version kernel 25 aug and baseband 286.
as you can see.
Updated to b382 vns-l21.
Problem : No notifications on Hangouts. I must go to my friend's chat in order to see the notification.
I have a question for @Chisetdel31260 or @Paolo83 or for whom I can answer it.
Is it still unclear if it is necessary or not the data_full public, which contains this .zip? And how can I add it without errors? Thanks to whoever can guide me :angel:
Doble_f said:
I have a question for @Chisetdel31260 or @Paolo83 or for whom I can answer it.
Is it still unclear if it is necessary or not the data_full public, which contains this .zip? And how can I add it without errors? Thanks to whoever can guide me :angel:
Click to expand...
Click to collapse
Hello
yes, I add it.
you just have to open the folder data / hw_init /
sorry,
for my bad English.
yet I do a great deal of effort.
for that google translator, does not blow up the planet.
Hi Chisetdel, I share this video, which includes the files OEMinfo.zip, Update.zip and Update_data_full.zip modified and ready to install via TWRP directly from EMUI 4.1 for the L21 (C432B382/EMUI 5.0.1) and L23 (C605B372/EMUI 5.0.1): here
Greetings

L29-C432B380 needed

Well i done goofed... installed LOS 15.1 from the mate 10 and now i can't go back to stock..
can someone get me the system and boot image and the recovery?
i've looked arround but wasn't able to found
B380? I didn't know that this is released. The last update I know for VTR-L29C432 is B360.
I had a similar problem a few days ago and found a solution by @Blackball (I hope I'm allowed to post is work here):
For this solution you need a SD card, TWRP and the B360 update files (file1, file2, file3).
Download the file from this post by @Blackball.
- Unzip the OREO_FLASH.zip to your SD card.
- Place the three update files into the OREO_FLASH directory on your SD card and rename them as following:
- update.zip stays update.zip
- update_data_full_public.zip to update_data_public.zip
- update_full_VTR-L29_hw_eu.zip to update_all_hw.zip
- The OREO_FLASH directory should now contain all needed files:
oreo_update.zip, update.zip, update_all_hw.zip, update_data_public.zip, OREO_NoCheck_VKY.img.
- Install provided TWRP with "fastboot flash recovery_ramdisk TWRPPATH.img".
- Now insert the SD card and boot into TWRP recovery.
- Tap on install, choose the OREO_FLASH directory and install the oreo_update.zip.
The script installs the original Oreo recovery from the P10Plus (for me, it was working on my P10, VTR-C432! BUT NO WARRANTY FOR THIS!!!).
The recovery installs the update without a online validation.
For me it was working perfectly and now I'm on B360. BUT, again, NO WARRANTY!
I hope it's working for everyone and I hope that @Blackball isn't mad about my tutorial!
Thank you very much Blackball for your good work!
Thanks Jannomag and Blackball... This is Perfect :good:
Jannomag said:
B380? I didn't know that this is released. The last update I know for VTR-L29C432 is B360.
I had a similar problem a few days ago and found a solution by @Blackball (I hope I'm allowed to post is work here):
For this solution you need a SD card, TWRP and the B360 update files (file1, file2, file3).
Download the file from this post by @Blackball.
- Unzip the OREO_FLASH.zip to your SD card.
- Place the three update files into the OREO_FLASH directory on your SD card and rename them as following:
- update.zip stays update.zip
- update_data_full_public.zip to update_data_public.zip
- update_full_VTR-L29_hw_eu.zip to update_all_hw.zip
- The OREO_FLASH directory should now contain all needed files:
oreo_update.zip, update.zip, update_all_hw.zip, update_data_public.zip, OREO_NoCheck_VKY.img.
- Install provided TWRP with "fastboot flash recovery_ramdisk TWRPPATH.img".
- Now insert the SD card and boot into TWRP recovery.
- Tap on install, choose the OREO_FLASH directory and install the oreo_update.zip.
The script installs the original Oreo recovery from the P10Plus (for me, it was working on my P10, VTR-C432! BUT NO WARRANTY FOR THIS!!!).
The recovery installs the update without a online validation.
For me it was working perfectly and now I'm on B360. BUT, again, NO WARRANTY!
I hope it's working for everyone and I hope that @Blackball isn't mad about my tutorial!
Thank you very much Blackball for your good work!
Click to expand...
Click to collapse
well I do know this method, I've used it on nougat multiple times but I don't want to reformat my phone a 9th time this week ?
I just want the recovery to flash it on its partition
and @Jannomag it's B360 you're right i'm doing it right now..
my themes stopped working and the heath app didn't open
everything worked just fine thanks for letting me know and thank you @Blackball for the script to get it working

Updater process ended with ERROR: 1

Hello, help would be amazing as this is my 2nd day trying to root my xPeria XZ Premium!
I've finally flashed twrp , I'm trying to install this rom:
https://forum.xda-developers.com/xz-premium/development/kernel-sony-xz-premium-5-2018-t3784669
But I'm getting stuck when trying to install magisk, OR move any zip files from my SD card to my Internal Storage.
Could anyone guide me through how to resolve this? :crying:
Have unlocked boot loader?
Need to format data first
xStatiZx said:
Hello, help would be amazing as this is my 2nd day trying to root my xPeria XZ Premium!
I've finally flashed twrp , I'm trying to install this rom:
https://forum.xda-developers.com/xz-premium/development/kernel-sony-xz-premium-5-2018-t3784669
But I'm getting stuck when trying to install magisk, OR move any zip files from my SD card to my Internal Storage.
Could anyone guide me through how to resolve this? :crying:
Click to expand...
Click to collapse
Hey my dude follow these steps, in twrp select wipe->format data (You'll lose all your files) now try flash the rom, you should find a custom kernel for your device as well and install it after the rom. If the Kernel doesnt install magisk now would be a good time to do it :highfive:
Matthewwwww1998 said:
Hey my dude follow these steps, in twrp select wipe->format data (You'll lose all your files) now try flash the rom, you should find a custom kernel for your device as well and install it after the rom. If the Kernel doesnt install magisk now would be a good time to do it :highfive:
Click to expand...
Click to collapse
This isn't necessary. Just extract boot.img from whatever rom.zip you're using, flash that in recovery, reboot to recovery again and magisk should install.
murph187 said:
This isn't necessary. Just extract boot.img from whatever rom.zip you're using, flash that in recovery, reboot to recovery again and magisk should install.
Click to expand...
Click to collapse
You're a GOD. Thank You!!!!!
updater process ended with error: 1
I was able to install magisk but after that if i try to install nethunter I get this same error. I am using redmi 4(santoni). have installed lineage OS 15.1
Can someone please help me?
logs
I had similar error shown below while installing a custom ROM:
Error applying update: 7 (ErrorCode:: kInstallDeviceOpenError )Updater process ended with ERROR: 1 Error installing zip file
Solved by using slightly older version of TWRP
i try and didnt work how to extract boot image in steps ??
magicstep said:
I had similar error shown below while installing a custom ROM:
Error applying update: 7 (ErrorCode:: kInstallDeviceOpenError )Updater process ended with ERROR: 1 Error installing zip file
Solved by using slightly older version of TWRP
Click to expand...
Click to collapse
which version you use
murph187 said:
This isn't necessary. Just extract boot.img from whatever rom.zip you're using, flash that in recovery, reboot to recovery again and magisk should install.
Click to expand...
Click to collapse
Hi, which option may i have to choose? there are 4 options
magicstep said:
I had similar error shown below while installing a custom ROM:
Error applying update: 7 (ErrorCode:: kInstallDeviceOpenError )Updater process ended with ERROR: 1 Error installing zip file
Solved by using slightly older version of TWRP
Click to expand...
Click to collapse
3.2.2 worked for me.
In my case unmounting all the partitions fixed it for me, the boot.img method didn't work.
magicstep said:
I had similar error shown below while installing a custom ROM:
Error applying update: 7 (ErrorCode:: kInstallDeviceOpenError )Updater process ended with ERROR: 1 Error installing zip file
Solved by using slightly older version of TWRP
Click to expand...
Click to collapse
I had flashed new version on firmware but forgot to update TWRP recovery that is why I was getting this error. I updated TWRP recovery. also flashed boot.img image then I was able to fix this issue.
guys please help me i have xiaomi mi a2 lite whit twrp 3.5.0_9 installed and unlocked bootloader i downloaded android 11 rom link: https://forum.xda-developers.com/t/rom-11-0-daisy-aosp-11-0.4167961/. When i go to recovery mode i flash the rom and appears this error: Updater process ended whit error: 1 to flash additional zips please reboot recovery to switch to the updated slots. Error installing zip file rom.zip. please help me.
THANKS
samyxy said:
guys please help me i have xiaomi mi a2 lite whit twrp 3.5.0_9 installed and unlocked bootloader i downloaded android 11 rom link: https://forum.xda-developers.com/t/rom-11-0-daisy-aosp-11-0.4167961/. When i go to recovery mode i flash the rom and appears this error: Updater process ended whit error: 1 to flash additional zips please reboot recovery to switch to the updated slots. Error installing zip file rom.zip. please help me.
THANKS
Click to expand...
Click to collapse
I was having the same issue... After hours of research I finely managed to fix it. Try the following:
1 - Install TWRP (I also had the 3.5.0_9 version).
2 - Format data and wipe all the advanced options possible.
3 - Download the program "payload_dumper-win64".
3.1 - Following the payload dumper instructions, I've copied the payload.bin from my custom ROM to the payload_input folder.
3.2 - Execute payload_dumper.exe and wait, a lot!
3.3 - Copy the resulted files (boot.img, system.img, vendor.img) in to the phone.
4 - In TWRP, go to install, select from images, and, one by one, install the images you've just copied.
4.1 - Note that during the install process, you will have to select the correct "slots" to flash the images. In my case, there where to options for system and vendor. I've chosen the "System Image" and "Vendor Image" option.
5 - Restart.
That's it! I didn't had to change slots nor wipe data after the installation... I don't know if this was the correct approach, but after many tries this is what worked for me
Sorry about my bad english...
Sometimes it is caused due to corrupted file. While transferring file through MTP it is likely to corrupt large files. I had the same problem. Then I tried copying file while in TWRP (sure it is also MTP) and it worked.
PendiukG said:
I was having the same issue... After hours of research I finely managed to fix it. Try the following:
1 - Install TWRP (I also had the 3.5.0_9 version).
2 - Format data and wipe all the advanced options possible.
3 - Download the program "payload_dumper-win64".
3.1 - Following the payload dumper instructions, I've copied the payload.bin from my custom ROM to the payload_input folder.
3.2 - Execute payload_dumper.exe and wait, a lot!
3.3 - Copy the resulted files (boot.img, system.img, vendor.img) in to the phone.
4 - In TWRP, go to install, select from images, and, one by one, install the images you've just copied.
4.1 - Note that during the install process, you will have to select the correct "slots" to flash the images. In my case, there where to options for system and vendor. I've chosen the "System Image" and "Vendor Image" option.
5 - Restart.
That's it! I didn't had to change slots nor wipe data after the installation... I don't know if this was the correct approach, but after many tries this is what worked for me
Sorry about my bad english...
Click to expand...
Click to collapse
It's legit procedure. Also you don't need to manage slots here, caz recovery automatically does that for you.
Hello guys, i'm from Russia, sorry for my bad English. I using Poco X3 Pro, and i have some troubles. I wanted to install custom firmware. First ROM
delivered successfully, unlike the second. After clearing all sections except sd cart and otg, I tried to install the original MIUI build, but it didn't work. I downloaded the original MIUI, but still. When installing, it says: "Update process ended with ERROR: 1" The methods from the top didn't help, please help!
Sushanthn94 said:
updater process ended with error: 1
I was able to install magisk but after that if i try to install nethunter I get this same error. I am using redmi 4(santoni). have installed lineage OS 15.1
Can someone please help me?
logs
Click to expand...
Click to collapse
Kali Nethunter on redmi 4x (santoni) is updated here:
Releases · Neternels/android_kernel_xiaomi_msm8937
Redmi 4X (santoni) NetHunter Kernel. Contribute to Neternels/android_kernel_xiaomi_msm8937 development by creating an account on GitHub.
github.com
Follow it and flash firmwares (if needed).

Cannot find ramdisk/boot.img from Update.zip

I recently bricked my EVA-AL00 from installing Magisk and I'm using Tecalote's post (https://forum.xda-developers.com/showpost.php?p=77560239&postcount=27389) to resolve it.
I downloaded the update zip file (first result on https://pro-teammt.ru/firmware-database/?firmware_model=eva-al00&firmware_page=0), extracted, then used the Extractor software to extract UPDATE.APP. However, the Extractor tool did not show either ramdisk.img or boot.img. Only files are: CURVER.img, EFI.img, PACKAGE_TYPE.img, SHA256RSA.img, VERLIST.img, VERSION.img, crc.img and cust.img.
Could someone please help me find the right file?
george.tian said:
I recently bricked my EVA-AL00 from installing Magisk and I'm using Tecalote's post (https://forum.xda-developers.com/showpost.php?p=77560239&postcount=27389) to resolve it.
I downloaded the update zip file (first result on https://pro-teammt.ru/firmware-database/?firmware_model=eva-al00&firmware_page=0), extracted, then used the Extractor software to extract UPDATE.APP. However, the Extractor tool did not show either ramdisk.img or boot.img. Only files are: CURVER.img, EFI.img, PACKAGE_TYPE.img, SHA256RSA.img, VERLIST.img, VERSION.img, crc.img and cust.img.
Could someone please help me find the right file?
Click to expand...
Click to collapse
It must be FullOTA-MF, not OTA-MF, you must first unzip update.zip and then open update.app by Huawei Update Extractor.
You can also download b540 FullOTA from Firmware Finder, see eg
https://forum.xda-developers.com/showpost.php?p=78511904&postcount=1261
IMO, would be better to obtain support if you asked through HWOTA7 thread
Anyway, on my Mega, there are various stock kernels, ramdisks, etc from b535, b539 and b540, including b540 ramdisk patched for Magisk v18.
I've been using it and several other users and it worked fine
https://mega.nz/#F!JwkVyRya!Rb7OUE0z3PEpXBRxGOM-vQ
However, if you recived OTA Patch02 for b540, you will need to patch/install Magisk by checking both Preserving Encryption and Preserving AVB - for b535, b539 and b540 before Patch02, Preserving AVB was not needed. (only Preserve Encryption)
I'm currently back on b535, but with OTA Patch02, you can find on my Mega also its patched ramdisk, but again, because of Patch02, it was needed now to check also Preserve AVB.
If you are already on b540 with Patch02, I"m not sure if its stock ramdisk is the same as for b540 before Patch02 (probably yes, because OTA Patch02 was only few MB)
You can also extract ramdisk from your currently installed firmware directly from Oreo TWRP, go to Advanced, Terminal and use the command
Code:
dd if=/dev/block/bootdevice/by-name/ramdisk of=/external_sd/ramdisk.img
Extracted ramdisk.img will be saved to external SD card.
You can do the same from TWRP also for kernel and system - however, not for data partition (since TWRP lacks support to read encrypted data partition)
Hey please I'm looking for boot _recovery_crc.img
Eteon x said:
Hey please I'm looking for boot _recovery_crc.img
Click to expand...
Click to collapse
Hi there,
Without information about which device you have (model number, Android version, build number, custom version) it is not possible to give you a suitable tip.
It would also be helpful to know why you need a specific image.
Up to Android 7 there was a boot.img and a recovery.img, as well as a recovery2.img.
From Android 8 on there was no longer a boot.img, but instead the ramdisk.img. And for the recovery the so-called recovery_ramdisk.img.
Both images are different for each firmware, which is why precise information is necessary. The images can be extracted from the Update.App.
To do this, the firmware suitable for the device must be downloaded.
A xxx.crc.img is meaningless because it's just a checksum and not an image to flash!
Tecalote said:
Hi there,
Without information about which device you have (model number, Android version, build number, custom version) it is not possible to give you a suitable tip.
It would also be helpful to know why you need a specific image.
Up to Android 7 there was a boot.img and a recovery.img, as well as a recovery2.img.
From Android 8 on there was no longer a boot.img, but instead the ramdisk.img. And for the recovery the so-called recovery_ramdisk.img.
Both images are different for each firmware, which is why precise information is necessary. The images can be extracted from the Update.App.
To do this, the firmware suitable for the device must be downloaded.
A xxx.crc.img is meaningless because it's just a checksum and not an image to flash!
Click to expand...
Click to collapse
I was trying to flash an XML file from a board firmware using IDT and it's showing me that
Eteon x said:
I was trying to flash an XML file from a board firmware using IDT and it's showing me that
Click to expand...
Click to collapse
Your Screenshot shows a Huawei p10 VTR Board firmware.
But this Thread is for P9, not for P10.
Is your device a Huawei P10?
Please ask in the Huawei P10 Forum.
I can't help you with IDT flashing method.
I worked for such cases only with ChimeraTool and sometimes with DC Phoenix. (Both are paid Services)

SM-T819 - Installation problem

Hallo, I hope someone in this forum can help me with a problem with my SM-T819 TWRP.
I tried to install a CustomRom without making a back-up copy and apparently I removed all details on the tablet.
The installation of TWRP was succesful, however all my recent trials to install a CustomRom failed with the following comments:
Updating partition details….
…done
Full SELinux support is present
MTP enabled
Installing zip file `/sdcard1/lineage-16.0-20181203_161503-Unofficial-gts210velte.zip`
Checking for digest file...
Updater process ended with ERROR: 7
Error installing zip file `/sdcard1/lineage-16.0-20181203_161503-Unofficial-gts210velte.zip`
Updating partition details…
…done
installing zip file `/ sdcard1/lineage-16.0-20181203_161503-Unofficial-gts210velte.zip`
Checking for digest file...
Warning: No file_contexts
Comparing TZ version TZ.BF.3.0.3-00054 to TZ.BF.3.0.3-00077
Comparing TZ version TZ.BF.3.0.3-00064 to TZ.BF.3.0.3-00077
Comparing TZ version TZ.BF.3.0.3-00067 to TZ.BF.3.0.3-00077
Comparing TZ version TZ.BF.3.0.3-00071 to TZ.BF.3.0.3-00077
assert failed: samsung.verify_trustzone ("TZ.BF.3.0.3-00054", "TZ.BF.3.0.3-00044",
"TZ.BF.3.0.3-00067", "TZ.BF.3.0.3-00071") == "1"
Updater process ended with ERROR: 7
Error installing zip file `/sdcard1/lineage-16.0-20181203_161503-Unofficial-gts210velte.zip`
Updating partition details…
… done
I have done this trial with various TWRP and Lineage varieties but in vain and always with the identical error.
The only thing I could do was via TWRP the installation of “SMT819_Deodex_Debloated Custom Rom” (based on Stock-Samsung-Firmware.
I have also tried via Odin (several versions) to apply the original firmware. The installation proceeds without error, the tablet starts,
the progress is shown on the blue screen and every time it is cancelled after 25 % and 32%. Then the tab shuts down and starts again and remains in a continous loop with the splash screen.
Well, what is the reason to install a ... REALLY REALLY OLD version like this?
Try this https://lineageos.wickenberg.nu/gts210velte/ or that https://drive.google.com/drive/folders/1VsHc9-k4LA3-n19dp6Gkvqwf0GZLTRcA depending on what you want to have, LOS 16 or 17.1

Categories

Resources