Hey Guys,
I have been getting an 18MB OTA for my Micromax AndroidOne. However the update keeps failing. I have captured the OTA. The lInk is:
Update to LMY47K
The update failed maybe because I was rooted. But then I factory reset the phone so now, Root should technically be gone. Before doing factory reset, I had also removed root from the SU app. Still, when I try to install OTA update, I am getting an error. So I Captured the OTA and then tried to flashed the zip via recovery as well as ADB Sideload. Both of them gave the same error at the Verifying Current System stage:
Verifying current system...
"/system/bin/install-recovery.sh" has unexpected contents.
E:Error in /sideload/package.zip
(Status 7)
Installation Aborted
The same error occurs every time via both flashing methods. Any idea guys??
Thanks
PLEASE FLASH ON YOUR WON RISK. I AM NOT RESPONSIBLE FOR ANY DAMAGE THAT MAY BE CAUSED TO YOUR PHONE
Finally
DO THE FOLLOWING AT YOUR OWN RISK. I AM NOT RESPONSIBLE IF YOU BRICK OR DAMAGE YOUR PHONE
Finally it's done. I did the following steps: (Obviously backup data first)
1. I Unlocked the bootloader *LOST ALL DATA AS EXPECTED*
2. Flashed Philz Recovery (You can install any other but this recovery will be lost once flashing official zip as a result making Official Stock ROM and Official Stock Recovery)
Did these above 2 steps using AndroidOne Tool Kit. There are thorough instructions and warning to do so.
3. Downloaded the official update file from here. Only LMY47O file. Copied it on an External SD card
4. Go to Philz recovery, Select Wipe and then Clean to Install ROM (Preferably without inserting the SD Card).
5. Now insert the SD card, wait for a minute for the recovery to recognize your card and then select, Install Zip and then select from SD Card. Select your zip files, confirm installation.. Reboot once done
6. Once done, you will have a brand new OS. Enter all the information. and you will get the next two updates OTA and get installed just fine
Enjoy Your latest update!!
ashhem said:
DO THE FOLLOWING AT YOUR OWN RISK. I AM NOT RESPONSIBLE IF YOU BRICK OR DAMAGE YOUR PHONE
Finally it's done. I did the following steps: (Obviously backup data first)
1. I Unlocked the bootloader *LOST ALL DATA AS EXPECTED*
2. Flashed Philz Recovery (You can install any other but this recovery will be lost once flashing official zip as a result making Official Stock ROM and Official Stock Recovery)
Did these above 2 steps using AndroidOne Tool Kit. There are thorough instructions and warning to do so.
3. Downloaded the official update file from here. Only LMY47O file. Copied it on an External SD card
4. Go to Philz recovery, Select Wipe and then Clean to Install ROM (Preferably without inserting the SD Card).
5. Now insert the SD card, wait for a minute for the recovery to recognize your card and then select, Install Zip and then select from SD Card. Select your zip files, confirm installation.. Reboot once done
6. Once done, you will have a brand new OS. Enter all the information. and you will get the next two updates OTA and get installed just fine
Enjoy Your latest update!!
Click to expand...
Click to collapse
Justcopying and pasting from www.dileepworld.blogspot.com isillegal...you better know that!
nexi4droid said:
Justcopying and pasting from www.dileepworld.blogspot.com isillegal...you better know that!
Click to expand...
Click to collapse
Hi nexi4droid, greetings of the day.
A few points:
1. I have NOT copied this stuff from anywhere. I have written it myself. However it is but OBVIOUS that the instructions are very similar to other present ALL OVER THE WEB as that is how it is done.
2. Also, as you must have seen, I have given links to official pages of toolkits or OTA captures from where I have taken stuff. If I wanted to "just Copy-Paste", I would not have done so. I am well aware of how much efforts you developers take to bring us custom ROMS and special tools. So, No I am not the type of guy that steals or copies other people's work
3. I went through the link you have given and I could not find identical instructions anywhere on that beautifully blog. But then again, as I said in the first point. That is how it is done so you will find similar instructions all over the web.
4. And finally, My post is OLDER!! than your http://dileepworld.blogspot.in/2015/08/solution-for-canvas-a1-getting-back-ota.html So if anything, I should be blaming you, not me. But I wont as it does not make any sense. Everyone reads things from different places and tries various things the find on the web and then finally may post what worked for them. I did the same in my words taking part instructions from 1cefire's post and the AndroidOne Toolkit (Links in the OP).
I hope I have cleared my self and have no intention to offend you. Have a great day
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
Hello Guys! In the past 2 days i wanted to rebrand my phone (Huawei P9 EVA-L09) to the AL10 chinese version with a guide i found in the thread of the HWOTA7 tool. I succesfully flashed it without complications. But then my luck went out and i maybe have softbricked my phone. Here's how it happened.
As i did't like huawei's emui i wanted to load the Base ROM on my phone for flashing my favorite rom, Resurrection Remix. After i flashed my phones RAMDISK with the TWRP version as explained in Tecalotes post (fastboot flash recovery_ramdisk P9-EVA-8.0.0-TWRP-v4.img) i went straight in it to flash the img because i didn't know what command i needed to flash it over fastboot. So i tried wiping the Dalvik-/cache, factory reset and then wiping data. Then i went to rebooting my phone into the OS to check if the files are in the right place, but then it just was stuck at the screen (Your device has been unlocked and can't be trusted.) and down below just stands "Your device is booting now". I thought it just could take a while, but even after 10 minutes it did't change a bit, then it automatically reset to the eRecovery. After browsing in some german forums i found out that my phone isn't lost yet After this i booted TWRP again over fastboot and deleted all system files. Then nothing worked anymore. Tried sideloading, it said adb: error: connect failed: closed. or uknowncommand[errno] and then it stopped). I sat there for 6 hours, then my big IQ tried the UPDATE.app extractor and extracted recovery, system, ramdisk and vendor and flashed it. And it worked, it booted in eRecovery again and said "Your OS has mayor errors, do you wan't to download latest version and recovery?". I accepted. It downloaded for 10 minutes, then i repeated the last step of HWOTA7 and again, it worked. Then i could boot in the OS again, and enable ADB Debug and USB debug. After that i booted in TWRP and tried staying at EMIU 8, but again, i couldn't find the files. Then i tried sideload, again a error telling me that sideloading can't be done. Rebooted in OS, again stuck at the screen after the unlocking. I did go to sleep. Now its day 2 and i am writing here with my phone at the side in eRecovery. This time i didnt wipe anything else than data and the cache, also i did a factory reset. I easely can go in the OS again, but then i still would get the false directory without any files and couldnt load OpenGapps and the network fix or the BASE ROM, because i know now that it isnt a problem with base rom. I grately would accept anyone that can help. Also i cant use a SD card because i do not have the money for it right now because i'm in high school. Besides that, I personally think it's a faulty directory because of the TWRP. Also i can't go back to nougat because i can't find the zips. If someone is a expert, hit me up in the DMs here and if i got a fix i write it on this post for everyone that has this problem and i will mention the god that found it!
Many regards!
Since you have followed the re-branding guide by @Tecalote, why didn't you follow also his instructions for going back to stock (Oreo or even Nougat)
https://forum.xda-developers.com/showpost.php?p=77161314&postcount=3
Same things have also been asked in the Open Kirin thread, see e.g.
https://forum.xda-developers.com/showpost.php?p=77589852&postcount=79
Good luck, as long as you have Fastboot and eRecovery, your phone is not dead
Restore your phone and try to be not confused
Bumo Gaming said:
Hello Guys! In the past 2 days i wanted to rebrand my phone (Huawei P9 EVA-L09) to the AL10 chinese version with a guide i found in the thread of the HWOTA7 tool.
As i did't like huawei's emui i wanted to load the Base ROM on my phone for flashing my favorite rom, Resurrection Remix.
After i flashed my phones RAMDISK with the TWRP version as explained in Tecalotes post (fastboot flash recovery_ramdisk P9-EVA-8.0.0-TWRP-v4.img) i went straight in it to flash the img because i didn't know what command i needed to flash it over fastboot.
Click to expand...
Click to collapse
Okay, first of all → You should learn to read the instructions carefully. And if you do not understand something, then you should ask first - in the Rebrand Thread - before you do something!
"After i flashed my phones RAMDISK with the TWRP" → which ramdisk to you mean? Since you speak of the "Base ROM", you refer to the renewed post # 2 in the Rebrand Thread. I did not mention anything about flashing a "Ramdisk" there.
Note: ramdisk.img = similar the same than boot.img on Android 7 → and if, it must be flashed to: ramdisk
recovery_ramdisk = on Oreo the place of Recovery on the phone (on Nougat it was: recovery) → and if, it must be flashed to: recovery_ramdisk
In post # 2 I do not offer "ramdisk" for download or to flash.
There are only two recoveries to flash there: 1) P9-EVA-8.0.0-TWRP-v4.img → which must be flashed to: recovery_ramdisk and
2) b528-RECOVERY_RAMDIS.img, which is the EMUI-Stock-Recovery → and must be flashed to the same place: recovery_ramdisk (after flashing the Base ROM for doing the Factory reset)
"After i flashed my phones RAMDISK with the TWRP version as explained in Tecalotes post (fastboot flash recovery_ramdisk P9-EVA-8.0.0-TWRP-v4.img) i went straight in it to flash the img because i didn't know what command i needed to flash it over fastboot."
BTW: every Recovery (TWRP, EMUI-Stock-Recovery) can be flashed in Fastboot Mode with: fastboot flash recovery_ramdisk "name-of-the-file".img
→ That means, you flashed already TWRP (P9-EVA-8.0.0-TWRP-v4.img) in Fastboot Mode and you did boot into TWRP → and then?? Which img did you flash then? I did not mention to flash any img immediately after flashing TWRP.
→ After flashing TWRP you should flash either the NetworkPatch.zip or the Base ROM (suitable for your device) and after that you should: Reboot Recovery from TWRP main menu, after TWRP is rebooted you should flash: b528-RECOVERY_RAMDIS.img to: recovery_ramdisk - and NOT TO: ramdisk!!
It is well explained in the Thread.
The next step would be to Reboot Recovery from TWRP main menu into Stock Recovery (which is flashed right now) and perform from EMUI-Stock-Recovery Wipe Cache Partition and Factoryreset....
→ if you flashed b528-recovery_ramdis.img to ramdisk instead to: recovery_ramdisk → then it's clear why your P9 did not boot into the system and was stuck on the Bootscreen!
→ But what I dont understand is: How could you flash recovery_ramdis.img with TWRP if you have no external SD??
I wrote directly under the Download-Link of TWRP a short summary about this TWRP and I told clearly, that this TWRP has currently no access to /data and the internal storage → therefore: nothing can be done without external SD!
So, my question is - from where can you flash anything?
→ It would only possible to flash anything without external SD, if you did "format data" → but that would be a completely wrong step that I have not mentioned anywhere in the instructions.
"Format data" is only required, if you use HuRUpdater, as long TWRP can not decrypt the encrypted data Partiton.
→ But "Format data" can not be used for doing the NetworkPatch or flashing the Base Rom → it requires, that /data is originally encrypted - and NOT formatted.
Bumo Gaming said:
So i tried wiping the Dalvik-/cache, factory reset and then wiping data. Then i went to rebooting my phone into the OS to check if the files are in the right place, but then it just was stuck at the screen (Your device has been unlocked and can't be trusted.) and down below just stands "Your device is booting now". I thought it just could take a while, but even after 10 minutes it did't change a bit, then it automatically reset to the eRecovery.
Click to expand...
Click to collapse
Clear, if you did several things wrong and and not according to the instructions, the phone can not boot and goes and goes after some unsuccessful attempts into eRecovery.
→ But that would not be any problem. Because it is possible on rebranded P9 to EVA-AL10 - to use eRecovery. Just click on "Download latest version and recovery" - then P9 connects to the wifi, get the info package and download and restore your P9 to latest approved Firmware.
"So i tried wiping the Dalvik-/cache, factory reset and then wiping data. " - forget about it → if TWRP has no access to /data - you can not wipe Dalvik and you can not do Factory reset and you can not wipe data with TWRP! → Thats why I advised to do it with Stock EMUI Recovery after the zips are flashed.
Bumo Gaming said:
After browsing in some german forums i found out that my phone isn't lost yet After this i booted TWRP again over fastboot and deleted all system files. Then nothing worked anymore. Tried sideloading, it said adb: error: connect failed: closed. or uknowncommand[errno] and then it stopped). I sat there for 6 hours, then my big IQ tried the UPDATE.app extractor and extracted recovery, system, ramdisk and vendor and flashed it. And it worked, it booted in eRecovery again and said "Your OS has mayor errors, do you wan't to download latest version and recovery?". I accepted.
It downloaded for 10 minutes, then i repeated the last step of HWOTA7 and again, it worked. Then i could boot in the OS again, and enable ADB Debug and USB debug. After that i booted in TWRP and tried staying at EMIU 8, but again, i couldn't find the files. Then i tried sideload, again a error telling me that sideloading can't be done. Rebooted in OS, again stuck at the screen after the unlocking.
Click to expand...
Click to collapse
→ There is a much more simple way to restore your Phone that it can work again properly. I will write at the end.
→ You should not flash any GApps - Open GApps - or whatever, because GApps are not compatible with this firmware and not necessary. All necessary Google core apps and Google services are included in the firmware. Most of them not in the system, but in the data partiton.
→ The NetworkPatch zip as well as the Base Rom are including Playstore and Gboard and all the other Google Apps you need, you can simply install from Playstore.
→ You should not use HWOTA7 on Oreo - it is programmed to work on Android 7 (hwota7) and not on Android 8. It includes TWRP for Android 7 and not for Android 8 - and I already mentioned it in OP.
Bumo Gaming said:
I grately would accept anyone that can help. Also i cant use a SD card because i do not have the money for it right now because i'm in high school. Besides that, I personally think it's a faulty directory because of the TWRP. Also i can't go back to nougat because i can't find the zips. If someone is a expert, hit me up in the DMs here and if i got a fix i write it on this post for everyone that has this problem and i will mention the god that found it! Many regards!
Click to expand...
Click to collapse
→ if you have no money for SD Card or USB OTG, you can go back to a working system (EVA-AL10 as well as make a downgrade to Nougat) - I have it already explained in Post #3 as @zgfg told you - but you will not be able for now to use the NetworkPatch.zip or the Base ROM.zip, because this TWRP can only flash from Micro SD or USB OTG (current version, until decryption of encrypted data is solved)
→ it could be done instead with Root and copy the files from the NetworkPatch.zip to the right places to replace the existent ones. But I made no instruction for it right now.
→ this TWRP has no "faulty directory" and everything is working correctly, except you can not use internal storage for now
→ "everyone that has this problem" - will only have it, if he is quite confused and does not know what he is doing - neither reads instructions properly, nor asks if he does not know
→ if you want to go back to Nougat, read Post #3, it is well explained. The Link EVA-AL10b399Sp17a /Android 7 you can find in Post #2
Using HuRUpdater from internal storage:
1) Flash TWRP for Oreo (not the one from hwota7, which is for Nougat) - flash it in Fastboot Mode with the code in Post #2
2) Boot into TWRP and use: Wipe and right down the Button: format data (for HuRUpdater it is required ) - confirm format data by typing:yes → go back (after) to main menu of TWRP and use: Reboot - but not system - Reboot instead: Recovery
3) Phone reboot again to TWRP and then TWRP is able to see the internal storage (because data is formatted - but note: this practice can not be used for the Base ROM and also not for the NetworkPatch, because it requires original encrypted storage!!)
4) Connect USB cable to P9 and PC - you should see internal storage in Windows Explorer.
If not, go to the Button "Mount" in TWRP and click 1x on "disable MTP" and then "enable MTP" - now you should see the internal storage in Windows Explorer.
6) Make a folder on your internal storage, name it as you like - Copy inside this folder:
a) HuRUpdater 0.4
b) update.zip
c) update_data_public.zip (= renamed, as written in OP)
d) update_all_hw.zip (=renamed, as written in OP)
→ Note: If you use EVA-AL10C00B528 for this operation, you will stay on Oreo, with properly installed Firmware (but without NetworkPatch...)
→ if you use instead EVA-AL10b399Sp17a for this operation, you will downgrade to Nougat, EVA-AL10 and can then use HWOTA7 to rebrand back to your original P9
After you copied the files, disconnect USB from P9.
7) Navigate to the folder you had created on internal storage (with HuRUpdater inside) and flash now ONLY the file: HuRUpdater.
8) The Battery will make some noice - in that moment press shortly VOL- (not Vol+) and HuRUpdater will flash the Firmware (all 3 zip files) from your folder automatically.
9) After it is succesfully flashed, click on the left button to Wipe Dalvik and Cache (it will work now, because of decrypted data) → the go back to the main menu and use again Reboot - But not System! - you choose: Reboot Recovery. This will reboot the Phone into EMUI-Stock-Recovery
10) In Stock Recovery make first Wipe Cache Partition and then Factory Reset → you have a properly working system back.
Can't you borrow an SD card of 4 GB to execute HuRU, I'm not sure could it work from Internal mem
zgfg said:
Can't you borrow an SD card of 4 GB to execute HuRU, I'm not sure could it work from Internal mem
Click to expand...
Click to collapse
SD Card is easier, but HuRUpdater works also from internal storage → and it works also from USB (with OTG cable)
Only problem, TWRP hasn't support for encrypted data yet - but the steps with format data and then copy with PC in Windows Explorer the required files to internal storage, should solve this. ( for this case)
Tecalote said:
Okay, first of all → You should learn to read the instructions carefully. And if you do not understand something, then you should ask first - in the Rebrand Thread - before you do something!
"After i flashed my phones RAMDISK with the TWRP" → which ramdisk to you mean? Since you speak of the "Base ROM", you refer to the renewed post # 2 in the Rebrand Thread. I did not mention anything about flashing a "Ramdisk" there.
Note: ramdisk.img = similar the same than boot.img on Android 7 → and if, it must be flashed to: ramdisk
recovery_ramdisk = on Oreo the place of Recovery on the phone (on Nougat it was: recovery) → and if, it must be flashed to: recovery_ramdisk
In post # 2 I do not offer "ramdisk" for download or to flash.
There are only two recoveries to flash there: 1) P9-EVA-8.0.0-TWRP-v4.img → which must be flashed to: recovery_ramdisk and
2) b528-RECOVERY_RAMDIS.img, which is the EMUI-Stock-Recovery → and must be flashed to the same place: recovery_ramdisk (after flashing the Base ROM for doing the Factory reset)
"After i flashed my phones RAMDISK with the TWRP version as explained in Tecalotes post (fastboot flash recovery_ramdisk P9-EVA-8.0.0-TWRP-v4.img) i went straight in it to flash the img because i didn't know what command i needed to flash it over fastboot."
BTW: every Recovery (TWRP, EMUI-Stock-Recovery) can be flashed in Fastboot Mode with: fastboot flash recovery_ramdisk "name-of-the-file".img
→ That means, you flashed already TWRP (P9-EVA-8.0.0-TWRP-v4.img) in Fastboot Mode and you did boot into TWRP → and then?? Which img did you flash then? I did not mention to flash any img immediately after flashing TWRP.
→ After flashing TWRP you should flash either the NetworkPatch.zip or the Base ROM (suitable for your device) and after that you should: Reboot Recovery from TWRP main menu, after TWRP is rebooted you should flash: b528-RECOVERY_RAMDIS.img to: recovery_ramdisk - and NOT TO: ramdisk!!
It is well explained in the Thread.
The next step would be to Reboot Recovery from TWRP main menu into Stock Recovery (which is flashed right now) and perform from EMUI-Stock-Recovery Wipe Cache Partition and Factoryreset....
→ if you flashed b528-recovery_ramdis.img to ramdisk instead to: recovery_ramdisk → then it's clear why your P9 did not boot into the system and was stuck on the Bootscreen!
→ But what I dont understand is: How could you flash recovery_ramdis.img with TWRP if you have no external SD??
I wrote directly under the Download-Link of TWRP a short summary about this TWRP and I told clearly, that this TWRP has currently no access to /data and the internal storage → therefore: nothing can be done without external SD!
So, my question is - from where can you flash anything?
→ It would only possible to flash anything without external SD, if you did "format data" → but that would be a completely wrong step that I have not mentioned anywhere in the instructions.
"Format data" is only required, if you use HuRUpdater, as long TWRP can not decrypt the encrypted data Partiton.
→ But "Format data" can not be used for doing the NetworkPatch or flashing the Base Rom → it requires, that /data is originally encrypted - and NOT formatted.
Clear, if you did several things wrong and and not according to the instructions, the phone can not boot and goes and goes after some unsuccessful attempts into eRecovery.
→ But that would not be any problem. Because it is possible on rebranded P9 to EVA-AL10 - to use eRecovery. Just click on "Download latest version and recovery" - then P9 connects to the wifi, get the info package and download and restore your P9 to latest approved Firmware.
"So i tried wiping the Dalvik-/cache, factory reset and then wiping data. " - forget about it → if TWRP has no access to /data - you can not wipe Dalvik and you can not do Factory reset and you can not wipe data with TWRP! → Thats why I advised to do it with Stock EMUI Recovery after the zips are flashed.
→ There is a much more simple way to restore your Phone that it can work again properly. I will write at the end.
→ You should not flash any GApps - Open GApps - or whatever, because GApps are not compatible with this firmware and not necessary. All necessary Google core apps and Google services are included in the firmware. Most of them not in the system, but in the data partiton.
→ The NetworkPatch zip as well as the Base Rom are including Playstore and Gboard and all the other Google Apps you need, you can simply install from Playstore.
→ You should not use HWOTA7 on Oreo - it is programmed to work on Android 7 (hwota7) and not on Android 8. It includes TWRP for Android 7 and not for Android 8 - and I already mentioned it in OP.
→ if you have no money for SD Card or USB OTG, you can go back to a working system (EVA-AL10 as well as make a downgrade to Nougat) - I have it already explained in Post #3 as @zgfg told you - but you will not be able for now to use the NetworkPatch.zip or the Base ROM.zip, because this TWRP can only flash from Micro SD or USB OTG (current version, until decryption of encrypted data is solved)
→ it could be done instead with Root and copy the files from the NetworkPatch.zip to the right places to replace the existent ones. But I made no instruction for it right now.
→ this TWRP has no "faulty directory" and everything is working correctly, except you can not use internal storage for now
→ "everyone that has this problem" - will only have it, if he is quite confused and does not know what he is doing - neither reads instructions properly, nor asks if he does not know
→ if you want to go back to Nougat, read Post #3, it is well explained. The Link EVA-AL10b399Sp17a /Android 7 you can find in Post #2
Using HuRUpdater from internal storage:
1) Flash TWRP for Oreo (not the one from hwota7, which is for Nougat) - flash it in Fastboot Mode with the code in Post #2
2) Boot into TWRP and use: Wipe and right down the Button: format data (for HuRUpdater it is required ) - confirm format data by typing:yes → go back (after) to main menu of TWRP and use: Reboot - but not system - Reboot instead: Recovery
3) Phone reboot again to TWRP and then TWRP is able to see the internal storage (because data is formatted - but note: this practice can not be used for the Base ROM and also not for the NetworkPatch, because it requires original encrypted storage!!)
4) Connect USB cable to P9 and PC - you should see internal storage in Windows Explorer.
If not, go to the Button "Mount" in TWRP and click 1x on "disable MTP" and then "enable MTP" - now you should see the internal storage in Windows Explorer.
6) Make a folder on your internal storage, name it as you like - Copy inside this folder:
a) HuRUpdater 0.4
b) update.zip
c) update_data_public.zip (= renamed, as written in OP)
d) update_all_hw.zip (=renamed, as written in OP)
→ Note: If you use EVA-AL10C00B528 for this operation, you will stay on Oreo, with properly installed Firmware (but without NetworkPatch...)
→ if you use instead EVA-AL10b399Sp17a for this operation, you will downgrade to Nougat, EVA-AL10 and can then use HWOTA7 to rebrand back to your original P9
After you copied the files, disconnect USB from P9.
7) Navigate to the folder you had created on internal storage (with HuRUpdater inside) and flash now ONLY the file: HuRUpdater.
8) The Battery will make some noice - in that moment press shortly VOL- (not Vol+) and HuRUpdater will flash the Firmware (all 3 zip files) from your folder automatically.
9) After it is succesfully flashed, click on the left button to Wipe Dalvik and Cache (it will work now, because of decrypted data) → the go back to the main menu and use again Reboot - But not System! - you choose: Reboot Recovery. This will reboot the Phone into EMUI-Stock-Recovery
10) In Stock Recovery make first Wipe Cache Partition and then Factory Reset → you have a properly working system back.
Click to expand...
Click to collapse
Thanks for your help for people that may come in this thread with the same problem, fortunally 2 days after this post i totally forgot about it and i allready got a fix that was right in my nose. With Ramdisk i ment the TWRP recovery_ramdisk that you provided for installing the network patch or the BaseRom on the Oreo version of the AL10 Firmware. In the timespan of 2 days i found myself finding a old SD Card in my old broken phone that had 64 GB, so plenty for installing everything. With my foolishness as a beginner at that time i cleared every system partition even if there was no need for it and as i said i had the eRecovery with the install newest version of recovery and EMUI, that for some reason was set on the AL10 8.0.0 patch what still was in beta. I figured it all out after looking in some posts of the thread of the HWOTA7 tool and the post for unofficial update to oreo and just followed everything once again but this time with the SD Card, now my phone is partly stable with the custom rom i installed because of your tutorial. I want to thank you for that and give you my up-most respect for taking the time and helping out people like me that just came to the forums and didn't really understand a thing at first. With that out of the way i will take insperation from you and help others out in this wonderfull community.
BTW: every Recovery (TWRP, EMUI-Stock-Recovery) can be flashed in Fastboot Mode with: fastboot flash recovery_ramdisk "name-of-the-file".img
→ That means, you flashed already TWRP (P9-EVA-8.0.0-TWRP-v4.img) in Fastboot Mode and you did boot into TWRP → and then?? Which img did you flash then? I did not mention to flash any img immediately after flashing TWRP.
→ After flashing TWRP you should flash either the NetworkPatch.zip or the Base ROM (suitable for your device) and after that you should: Reboot Recovery from TWRP main menu, after TWRP is rebooted you should flash: b528-RECOVERY_RAMDIS.img to: recovery_ramdisk - and NOT TO: ramdisk!!
Click to expand...
Click to collapse
I was refering to the TWRP.img i was talking about. I really don't know what i ment by not knowing the command. Also with the ramdisk i got confused between recovery_ramdisk and ramdisk, but i didn't flash the b528 in the wrong kind of ramdisk. Because i was still new to it i didn't know the difference and just called the recovery_ramdisk; ramdisk what may have confused you.
Also with the DATA i've figured out that it can't get accessed by TWRP due to not having encryption. That's where i tried sideloading baserom or network-patch that gave me back the error that it wouldn't install the zip. So i got confused because it worked when i still had the L09 Firmware and flashed RROS 5.8.5 that was on nougat and not on oreo, a big difference now for me after i was looking it up. Thats really the problem i had and fixed allready but i didn't want to leave you without an explanation.
→ You should not flash any GApps - Open GApps - or whatever, because GApps are not compatible with this firmware and not necessary. All necessary Google core apps and Google services are included in the firmware. Most of them not in the system, but in the data partiton.
Click to expand...
Click to collapse
Also also i tried flashing GApps because for some unknown reason the first time i had my os back to the CHINESE firmware that didn't come with the Playstore but rather their own chinese stuff so i got confused and tried getting the Playstore with flashing the OpenGapps what as we know didn't work out that well.
→ "everyone that has this problem" - will only have it, if he is quite confused and does not know what he is doing - neither reads instructions properly, nor asks if he does not know
Click to expand...
Click to collapse
i tried reading the instructions but i misinterpreted them for no reason what-so-ever. Also i had a bit of a problem with xda 'cus i couldn't create a account over my IP because it said i allready created one with this ip today, so i needed to figure out how to find my old account, but it's a whole story for itself. Still i want to thank you for taking out your time for helping people like me.
Many regards
Bumo Gaming said:
Thanks for your help for people that may come in this thread with the same problem, fortunally 2 days after this post i totally forgot about it and i allready got a fix that was right in my nose. With Ramdisk i ment the TWRP recovery_ramdisk that you provided for installing the network patch or the BaseRom on the Oreo version of the AL10 Firmware. In the timespan of 2 days i found myself finding a old SD Card in my old broken phone that had 64 GB, so plenty for installing everything. With my foolishness as a beginner at that time i cleared every system partition even if there was no need for it and as i said i had the eRecovery with the install newest version of recovery and EMUI, that for some reason was set on the AL10 8.0.0 patch what still was in beta. I figured it all out after looking in some posts of the thread of the HWOTA7 tool and the post for unofficial update to oreo and just followed everything once again but this time with the SD Card, now my phone is partly stable with the custom rom i installed because of your tutorial. I want to thank you for that and give you my up-most respect for taking the time and helping out people like me that just came to the forums and didn't really understand a thing at first. With that out of the way i will take insperation from you and help others out in this wonderfull community.
I was refering to the TWRP.img i was talking about. I really don't know what i ment by not knowing the command. Also with the ramdisk i got confused between recovery_ramdisk and ramdisk, but i didn't flash the b528 in the wrong kind of ramdisk. Because i was still new to it i didn't know the difference and just called the recovery_ramdisk; ramdisk what may have confused you.
Also with the DATA i've figured out that it can't get accessed by TWRP due to not having encryption. That's where i tried sideloading baserom or network-patch that gave me back the error that it wouldn't install the zip. So i got confused because it worked when i still had the L09 Firmware and flashed RROS 5.8.5 that was on nougat and not on oreo, a big difference now for me after i was looking it up. Thats really the problem i had and fixed allready but i didn't want to leave you without an explanation.
Also also i tried flashing GApps because for some unknown reason the first time i had my os back to the CHINESE firmware that didn't come with the Playstore but rather their own chinese stuff so i got confused and tried getting the Playstore with flashing the OpenGapps what as we know didn't work out that well.
i tried reading the instructions but i misinterpreted them for no reason what-so-ever. Also i had a bit of a problem with xda 'cus i couldn't create a account over my IP because it said i allready created one with this ip today, so i needed to figure out how to find my old account, but it's a whole story for itself. Still i want to thank you for taking out your time for helping people like me.
Many regards
Click to expand...
Click to collapse
Many thanks for your detailed feedback! :good:
slayernn said:
Plz HELP! History: I did everything from this thread and it worked fine for few monts until last official update, after that sim card was not recognised. I did lots of mistakes after,cant even imagine.. what i did in end is that i changed oem info via hwota to EVA-L09C636 and put again chinese EVA-AL10 oreo.. now my android system have lots of problem, no aps, keyboard was gone (only chinese kb and somehow i managed to put en). Everything is messed. Now problem gets bigger: OEM unlock is grayed in developer options, so i cant unlock bootloader (and in fastboot mode, bootloader and FRP are locked), so there is no way to put TWRP and everything look bricked (( Also dload update always fail at 5% with any room i try... Pls help me, i just want to go back to original nougat, like when i bought and forget chinese brand and oreo... Thanx in advance
droid info app:
Model: EVA-L09 (EVA-L09)
Manufacturer: HUAWEI
Baseband Version: 21.258.09.00.030
RIL Version: android infineon balong-ril 1.0
Build Number: System 8.0.0.046(0EET)
Build Fingerprint: Huawei/generic_a15/generic_a15:8.0.0/OPR6.170623.010/jenkin07111806:user/test-keys
Bootloader: unknown
Java VM: ART 2.1.0
OS Version: O (8.0.0)
SDK: 26
Click to expand...
Click to collapse
zgfg said:
First and most important for any further analysis, please clearly write on which exact build name/number you are
Can you post a screenshot of Setting/About
Click to expand...
Click to collapse
slayernn said:
Plz HELP! History: I did everything from this thread and it worked fine for few monts until last official update, after that sim card was not recognised. I did lots of mistakes after,cant even imagine..
Click to expand...
Click to collapse
1) It is normally → mobile network and IMEI is lost after OTA Update, but as you can read above - no problem to solve, if you doing the right steps
2) For the next time: First ask here in this Thread: https://forum.xda-developers.com/p9/development/rebrand-update-tool-hwota7-p9-eva-t3820849/page93#post77981310
if you face anything you dont know how to do.... before you are doing steps without sence
Where do you live? Because if you live in Germany, I could repair.
If not, we will find a solution - I am just think about it
@slayernn
I moved your issue to this Thread, because it is OT in the main Thread, since your problem is not made by me or my instructions, but because you did several things wrong without asking before.
Here is a Repair Firmware - which can be flashed with dload method (inside is also instructions). I will download in the evening and have a look. Then I can give you further instructions, how to use it. So far I remember, it must be extracted two times....
Huawei P9 EVA-AL10 8.0.0.528(C00) Firmware Android8.0:
https://androidhost.ru/6sl
Tecalote said:
1) It is normally → mobile network and IMEI is lost after OTA Update, but as you can read above - no problem to solve, if you doing the right steps
2) For the next time: First ask here in this Thread: https://forum.xda-developers.com/p9/development/rebrand-update-tool-hwota7-p9-eva-t3820849/page93#post77981310
if you face anything you dont know how to do.... before you are doing steps without sence
Where do you live? Because if you live in Germany, I could repair.
If not, we will find a solution - I am just think about it
@slayernn
I moved your issue to this Thread, because it is OT in the main Thread, since your problem is not made by me or my instructions, but because you did several things wrong without asking before.
Here is a Repair Firmware - which can be flashed with dload method (inside is also instructions). I will download in the evening and have a look. Then I can give you further instructions, how to use it. So far I remember, it must be extracted two times....
Huawei P9 EVA-AL10 8.0.0.528(C00) Firmware Android8.0:
https://androidhost.ru/6sl
Click to expand...
Click to collapse
Thanx man and sorry for posting in wrong thread. I'm looking forward! Downloading file right now.
Best regards , ps damn slow download from link (takes 8h to dl) you provide. Is there alternative?
slayernn said:
Thanx man and sorry for posting in wrong thread. I'm looking forward! Downloading file right now.
Best regards , ps damn slow download from link (takes 8h to dl) you provide. Is there alternative?
Click to expand...
Click to collapse
Yes, this is really a slow download, but no - it's the only place where you can get Firmware, which is installable with dload method!
If you create a User on this Site, download is faster, but needs even some hours....
@slayernn
When your Download is ready → you have: Huawei P9 EVA-AL10 8.0.0.528(C00) Firmware Android8.0 EMUI8.0.0 05014GSG androidhost.ru.zip
Rename it to: Huawei P9 EVA-AL10 8.0.0.528.zip
→ unpack/extract zip, then you have the folder: Huawei P9 EVA-AL10 8.0.0.528 - the folder contains:
ReleaseDoc
Software - go inside this folder, there is: SDupdate_Package.tar.gz → unzip/extract it, then you have the folder: SDupdate_Package.tar - this folder contains:
SDupdate_Package.tar - unzip/extract it, then you get finally the folder: SDupdate_Package - and this folder contains, what we need, the folder:
dload
Inside this folder you find the UPDATE.APP - and probably one or two additional folders with another UPDATE.APP (for the location, example: update_EVA-AL10_all_cn.app)
Now you have two possibilites
A)
1) Flash first the UPDATE.APP with dload method → after it is flashed, dont boot to system, press VOL+ during automatically restart to enter EMUI-Recovery
2) reject SD-Card, delete the previous update.app and copy the second update.app (update_EVA-AL10....) into dload folder → rename it to: UPDATE.APP
3) In EMUI-Recovery go to Reboot and during restart press Vol+ and Vol- to force update:
4) now second UPDATE.APP will be flashed → after it is flashed, dont boot to system, press VOL+ during automatically restart to enter EMUI-Recovery
5) delete second Update.app in dload folder and copy the first UPDATE.APP again into dload folder and flash it once again with dload → once you have done this and phone reboot automatically, press again VOL+ to enter EMUI-Recovery
6) Make Wipe Cache and Factoryreset
7) Phone should boot → and be able to enable OEM-Unlock → then a downgrade to Nougat and rebranding would be possible (ask me for the steps, before doing)
B) Second possibility (costs about 15 EUR, but it is easier and probably better)
Buy from DC 15 Credits (=15 EUR) from here: https://www.dc-unlocker.com/buy
Download DCPhoenix Software v63 - extract it and open DCPhoenix, log-in to your Account
In the first field above choose the big, first UPDATE.APP
on Customation field select the second UPDATE.APP (no need to rename for DC)
Flash it → additional you can change oeminfo on second tab....
Wish you success
@slayernn
I answered your PM → forgot to ask: Can you please tell me each exately name of the second two folders (with the two other update.app)
Thx
@slayernn It would be good if you write a summary here with the steps (as far as you remember) - how you managed to restore your P9
Tecalote said:
@slayernn It would be good if you write a summary here with the steps (as far as you remember) - how you managed to restore your P9
Click to expand...
Click to collapse
First of all, thank you Tecalote on all your tutorials and support in every step, without you restoring phone to original stock state would be imposible.
In short, i will explain what problem i had and how it is fixed.
History:
My P9 EVA-L09 was changed to EVA-AL10 and oreo, after few stupid mistakes in a rush, i changed oem info to EVA-L09c63.. and re-update AL-10 files in final step from hwota7. After that i got semi bricked device, oreo with damaged build number, oem info, and most important bootloader/frp was locked and couldnt change oem unlock (it was grayed). After that i tried many different fw/roms via dload method without success until Tecalote suggest downloading Huawei P9 EVA-AL10 8.0.0.528. UPDATE.app of that pack always worked and it was crucial later, but next dload EVA-AL10_all_cn didnt work, so i was at beginning again, with damaged oreo.
What i did later and steps that restore my device to stock nougat:
Next thing i did is taking DC-Phoenix + HCU timed license after which i tried to change oem info, but in dc-phoenix there was no EVA-L09 so i used EVA-L29 and tried some appropriate files to upload. It ended with errors and phone was dead bricked.. cant power on/dload/recovery but dc-phoenix still recognise it in fastboot so then i tried to upload EVA-AL10 8.0.0.528 again and it worked, during period of update device was unlocked and i realised i could use hwota7 tool during that time, just to unlock bootloader with code, so i did and it was successful, was it clever? dont know! What i got now is old oreo with f****d oem info / build etc but unlocked. Next thing i did is to use HCU program and in repair cdma tab, i changed model/vendor/country to EVA-L09/hw/eu! Right after that uploaded EVA-L09_C432B390_Firmware_France_Ger... and update_EVA-L09_C432B390_hw_eu from dc-phoenix and it was successful! Now i got nougat (poor without camera and so) and original EVA-L09 model name. Next, Tecalote send me HWOTA download link and steps to take https://forum.xda-developers.com/showpost.php?p=74913874&postcount=3 and after that, phone was fully restored to original state and everything is working perfecto. It took me 2-3 days of work, many errors.. in a moments i was thinking that device is completely bricked and want it to throw in trash can. Never give up..thats point Best regards!
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)