Note:
This is not bootanimation, this is the splash screen (the 'Huawei' boot logo which is displayed when device is switched ON)
This is for Huawei P8 Lite 2017 Only.. (Resolution 1080x1920)
For other devices, please send me your splash.img so that I can create a tool for you too.
Requirements:
1. Rooted Huawei P8 Lite 2017 (any ROM)
2. Optional: Terminal Emulator app or Custom Recovery or atleast working fastboot in computer
3. You're proceeding at your own risk.
Use this tool and instructions:
Huawei OEM_logo Changer
Note: Use a 1080x1920 pic, as .bmp file (in rgb565 format as specified in that post)
Old method:
STEPS to create boot logo:
1. Download & Extract this in computer: Huawei_P8_Lite_2017_Logo_Maker.zip
2. Make sure you have a picture in BMP format with resolution exactly 1080x1920px. (Can be of any format)
3. Now rename your picture as logo.bmp & replace it inside "pics" folder of the extracted folder. (Or directly edit the 'logo.bmp' file)
4. Finally, run the 'CREATE_LOGO.bat' to create oeminfo.img and flashable zip file, which you can find inside the "output" folder after completion.
STEPS to flash boot logo:
Steps to backup your oeminfo.img:
Open Terminal Emulator, type the following command to save your stock oeminfo.img to your Internal Storage:
Code:
su
dd if=/dev/block/platform/hi_mci.0/by-name/oeminfo of=/sdcard/oeminfo_stock.img
Now, choose any one easy method to install:
a. To flash from recovery:
Transfer the flashable_logo.zip to your device and flash from TWRP or CWM or Philz or any other custom recovery.
b. To flash from Terminal Emulator:
Transfer the oeminfo.img to your device's Internal Storage, Open Terminal Emulator & enter the following to flash it:
Code:
su
dd if=/sdcard/oeminfo.img of=/dev/block/platform/hi_mci.0/by-name/oeminfo
c. To flash from Fastboot mode:
Code:
fastboot flash oeminfo oeminfo.img
Finally, Reboot and check if the bootlogo has changed!!
Note:
Incase something goes wrong or device doesn't bootup, just flash the stock oemlogo.img from custom recovery or fastboot.
Credits:
1. @CrimsonBloodfang who provided the stock oemlogo.img of P8 Lite 2017 (PRA-LX2)..
2. @GokulNC (myself ) who wrote this script
Hit the Thanks :good: button if it worked for you
You're welcome to post the splash images that you created..
Is that working with all variants of the p8lite 2017? I rebranded mine to the Chinese Honor Version.
Doesn't work for me., same logo as before.
rebranded mine too
---------- Post added at 09:07 PM ---------- Previous post was at 09:05 PM ----------
https://imgur.com/a/XAup4
just made this btw, it's already in the right format.
GokulNC said:
TESTING:
@CrimsonBloodfang
1. Can you please check if this tool is working??
2. Please check if flashing the zip from custom recovery works.
3. Please attach your 'oeminfo' partition backup. I guess it might have the logo inside it (if the above procedure doesn't work)
4. Are there different variants of P8 Lite like P8lite 2017 , etc. ?
Click to expand...
Click to collapse
1. I am able to create a new "oemlogo.mbn" and a "flashable_logo.zip" through your tool but unfortunately the stock boot logo of Huawei still shows up in every reboot, after using the two files.
2. The zip file works in TWRP Recovery and was flashed without errors but the stock boot logo still shows upon reboot then after rebooting, I checked /product/etc/logo/ and the stock oemlogo.mbn was not replaced with the new one.
3. Here is the oeminfo.img backup, by using this command in a terminal emulator
Code:
su
dd if=/dev/block/platform/hi_mci.0/by-name/oeminfo of=/sdcard/oeminfo.img
and this one is the raw file itself. I only used two out of three methods of backing up the oeminfo partition based from this thread because I was unsure as to where in TWRP Recovery should I find the backup for oeminfo partition since it only has the options Boot, Cache, Data, System and Vendor for backup. Maybe in the "Vendor" partition, but the backup size is 394 MB.
4. I'm not sure for the variants of Huawei P8 Lite, maybe only Huawei P8 Lite (2017) and the ones on the "download section" in this link? If you meant the Huawei P8 Lite (2017) variants, the ones I know are Huawei P8 Lite (2017) PRA-LX1, PRA-LX2, PRA-LX3, PRA-LA1 and PRA-TL00. I'm using the Huawei P8 Lite (2017) PRA-LX2.
I've also tried copy pasting the new oemlogo.mbn then changed it to the correct permissions (-rw-r--r--). I even tried renaming it to "oemlogo.mbn.bak" to see if there's any change but it seems that this file is not in control of the boot logo. We also have the boot warning logo too by the way, the one that is caused by unlocking the bootloader.
Here is my own logo.bmp boot logo, 1080x1920 resolution, edited through Gimp 2 and exported as .bmp file format.
Edit: Does anyone know where is the exact location for our boot logo files? I've also found the same oemlogo.mbn file on some folders in /product/hw_oem
@CrimsonBloodfang
The oeminfo.img file had the pictures as I guessed.
I have updated the OP with the new tool. Please check if it's working
Also, I think the files in the '/product/hw_oem/whatever' directory are created from the oemlogo partition while booting (not sure though).
So maybe using the old tool, setting the permissions for oemlogo.bin as -r--r--r-- might have worked (since write access is denied).
Edit:
As specified in GSMArena website, is it true that P8 Lite (2017) is also called Huawei P9 Lite (2017), Huawei Honor 8 Lite, Huawei Nova Lite, Huawei GR3 (2017) ???
If yes, this tool MIGHT work for those devices too.
Thanks! I will be testing it now.
GokulNC said:
@CrimsonBloodfang
Edit:
As specified in GSMArena website, is it true that P8 Lite (2017) is also called Huawei P9 Lite (2017), Huawei Honor 8 Lite, Huawei Nova Lite, Huawei GR3 (2017) ???
If yes, this tool MIGHT work for those devices too.
Click to expand...
Click to collapse
Yes, it is called with different names from different countries and they are more or less, just the same devices.
In the Philippines, this phone is called the Huawei GR3 (2017).
Edit:
Maybe the users need to backup their own "oeminfo.img" first before using the tool and can you add it on OP? They might use my device's oeminfo.img if they forgot to backup and it might change their device's region settings then their stock updates would be based from my country.
I haven't rebranded my phone, just went straight to LineageOS 14.1 so I'm not sure about the consequences of flashing other oeminfo.
still not working for me. Now it's just booting into eRecovery and the logo was changed to the original one
@GokulNC
It also didn't work for me. I've tested it six or more times with both the Terminal Emulator and the TWRP Recovery flash method.
Edit:
The logo file in "pics" folder of the tool has a logo.png and not anymore a logo.bmp, so I tried both file formats just in case. I've tried replacing it with logo.bmp, I've tried replacing it with logo.png and I've tried placing both logo.bmp and logo.png together on the "pics" folder. Then flashed the six different files of oeminfo.img and flashable_logo.zip with Terminal Emulator and TWRP Recovery, but on every reboot, the boot logo is still at stock.
The only locations left I can guess as to where the boot logo files for Huawei P8 Lite (2017) are maybe in the Boot partition or it's embedded in the Kernel.
@CrimsonBloodfang
Actually there were many .bmp pics inside the oeminfo.img
I didn't look at that properly.
When I extracted them, I saw 2 bootlogo images.
So I've modified the tool to change them both.
Try the new tool that I've uploaded now and see if it's working
It should contain 2 files named logo1.png and logo2.png
CrimsonBloodfang said:
The only locations left I can guess as to where the boot logo files for Huawei P8 Lite (2017) are maybe in the Boot partition or it's embedded in the Kernel.
Click to expand...
Click to collapse
Nope, I don't think so..
MIcHiJK said:
Is that working with all variants of the p8lite 2017? I rebranded mine to the Chinese Honor Version.
Click to expand...
Click to collapse
I'm not sure if the oeminfo partition is same across all the different firmwares.
I guess they all must be the same. If you can attach your stock 'oemlogo.img', I'll take a look at it.
CrimsonBloodfang said:
The logo file in "pics" folder of the tool has a logo.png and not anymore a logo.bmp, so I tried both file formats just in case. I've tried replacing it with logo.bmp, I've tried replacing it with logo.png and I've tried placing both logo.bmp and logo.png together on the "pics" folder.
Click to expand...
Click to collapse
My tool automatically converts everything to .bmp format, so it doesn't matter
Striike said:
still not working for me. Now it's just booting into eRecovery and the logo was changed to the original one
Click to expand...
Click to collapse
I'm not sure about the rebranded device. Can you please attach your 'oeminfo' file?
I'll check that out.
GokulNC said:
@CrimsonBloodfang
Actually there were many .bmp pics inside the oeminfo.img
I didn't look at that properly.
When I extracted them, I saw 2 bootlogo images.
So I've modified the tool to change them both.
Try the new tool that I've uploaded now and see if it's working
It should contain 2 files named logo1.png and logo2.png
Click to expand...
Click to collapse
Ok, I've flashed the flashable_logo.zip using the new tool and it seems to work. Boot logo is not anymore the stock one but instead, it's replaced by a "glitched image" with a color green background and two rectangles with colors pink and blue, not the boot logo I made. Boot warning sign is still there afterwards though.
It may be a wrong procedure on my part because I just placed my logo.bmp together with the logo1.png and logo2.png but I will continue tinkering and testing it or have a lower file sized image to see if I can finally get the desired boot logo.
---------- Post added at 11:04 PM ---------- Previous post was at 10:52 PM ----------
Also flashed my backup oeminfo.img through Terminal Emulator or TWRP Recovery and everything went back to normal.
@GokulNC
Tested it many times, boot logo always end up with the "glitched image" as attached below.
This is not the original image. Just an edited image through Gimp 2, for reference.
CrimsonBloodfang said:
@GokulNC
Tested it many times, boot logo always end up with the "glitched image" as attached below.
This is not the original image. Just an edited image through Gimp 2, for reference.
Click to expand...
Click to collapse
Does this arise after changing the logo2.png (or logo2.bmp)??
Is that the same output no matter what the logo2 is?
I mean, even for the default one that I've placed in pics folder or what you replaced with, is the output the same weird image??
FYI, ensure there are only 2 images in the pics folder while creating the oemlogo.img, ie, logo1.<whatever_format> and logo2.<whatever_format>
GokulNC said:
Does this arise after changing the logo2.png (or logo2.bmp)??
Is that the same output no matter what the logo2 is?
I mean, even for the default one that I've placed in pics folder or what you replaced with, is the output the same weird image??
FYI, ensure there are only 2 images in the pics folder while creating the oemlogo.img, ie, logo1.<whatever_format> and logo2.<whatever_format>
Click to expand...
Click to collapse
Yes, I've already tried different ways like replacing only the logo2.png or replace both images and also ensured there are two images in the pics folder.
I also tried using only the "default images" and did not replace anything in the pics folder, then flashed the newly created files and the resulting boot logo is still the glitched image.
Edit:
The image in this post is what the glitched image of the boot logo, actually looks like.
GokulNC said:
Note:
This is not bootanimation, this is the splash screen (the 'Lenovo' boot logo which is displayed when device is switched ON)
This is for Huawei P8 Lite 2017 Only.. (Resolution 1080x1920)
For other devices, please send me your splash.img so that I can create a tool for you too.
Requirements:
1. Rooted Huawei P8 Lite 2017 (any ROM)
2. Optional:Terminal Emulator app or Custom Recovery or atleast working fastboot in computer
3. You're proceeding at your own risk.
STEPS to create boot logo:
1. Download & Extract this in computer: Huawei_P8_Lite_2017_Logo_Maker.zip
2. Make sure you have a picture in BMP format with resolution exactly1080x1920px. (Can be of any format)
3. Now rename your picture as logo.bmp & replace it inside "pics" folder of the extracted folder. (Or directly edit the 'logo.bmp' file)
4. Finally, run the 'CREATE_LOGO.bat' to create oeminfo.img and flashable zip file, which you can find inside the "output" folder after completion.
STEPS to flash boot logo:
Choose any one easy method:
a. To flash from recovery:
Transfer the flashable_logo.zip to your device and flash from TWRP or CWM or Philz or any other custom recovery.
b. To flash from Terminal Emulator:
Transfer the oeminfo.img to your device's Internal Storage, Open Terminal Emulator & enter the following to flash it:
c. To flash from Fastboot mode:
Finally, Reboot and check if the bootlogo has changed!!
Note:
Incase something goes wrong or device doesn't bootup, just flash the stock oemlogo.img from custom recovery or fastboot.
Credits:
1. @CrimsonBloodfang who provided the stock oemlogo.img of P8 Lite 2017 (PRA-LX2)..
[email protected] (myself ) who wrote this script
Hit the Thanks:good: button if it worked for you
You're welcome to post the splash images that you created..
Click to expand...
Click to collapse
Thanks bro
Very useful guide
CrimsonBloodfang said:
Yes, I've already tried different ways like replacing only the logo2.png or replace both images and also ensured there are two images in the pics folder.
I also tried using only the "default images" and did not replace anything in the pics folder, then flashed the newly created files and the resulting boot logo is still the glitched image.
Edit:
The image in this post is what the glitched image of the boot logo, actually looks like.
Click to expand...
Click to collapse
Hi, sorry for my late reply. Got stuck up with something lately.
I have attached a new tool, with little changes.
Please check if it's working.
If it doesn't, I'm not sure what else to do.
honorfan said:
Thanks bro
Very useful guide
Click to expand...
Click to collapse
Hi, did this work for you?
Thanks, I will be testing it later. I've also found out from another user that changing the boot logo using the tool, has stopped working in Nougat and Oreo.
Here is what he said, and this thread is also changing their Huawei device using the oeminfo partition.
Maybe you already know these?
@GokulNC
Tested it twice, it's still showing the glitched image.
My first attempt was replacing the logo2.png with another image as logo2.bmp. Flashed the files through TWRP Recovery, rebooted and the result is still the glitched image.
Second attempt was to not replace anything in the "pics" folder. Created the files, flashed them in TWRP Recovery, rebooted and the result is still the same.
I've been searching around xda forums for information about editing Huawei's oeminfo for its boot logo image and I noticed that their tutorials needs to follow a "specific RGB format" when editing the images to be used as a boot logo. (Bitmap file with color depth not less than 16 bit, supported color schemes: RGB555, RGB565, RGB888, RGB8888)
Although, I'm uncertain that this might be the cause of the problems and I haven't tried it yet.
- Follow any of the RGB formats to fix the problem.
I've only tried "RGB565" and "RGB888 with color depth of 24 bits".
On the other hand, seeing the "glitched image" as a boot logo, might just only be an indication of a corrupted oeminfo, when it's not properly recompiled or reconstructed?
Just to be sure, I'll place the links of the threads and posts, that I think might be useful for reference.
You might have already read these threads before.
- How To Change The Splash Screen or Boot Logo In Huawei Honor 7 at post #2
- Scroll down to Part VII - How To Change The Splash Screen
- Solution by Kostyan_nsk
- [HOW TO] Replace initial splash screen (logo) on Huawei P7
- [GUIDE] Changing boot splash image on the Huawei Y6
I will try changing the RGB formats for the image that I'll be editing, to see if it makes a difference.
Related
If somebody want to replace provider/operator/or any other splash screen on Huawei device just do as follow:
Root required
First way:
Install Adb and Fastboot
Download this utility to ADB folder on PC
By Windows CMD go to ADB folder and use this commands:
(observe phone and make appropriate permissions if needed)
adb shell su -c "dd if=/dev/block/platform/hi_mci.0/by-name/oeminfo of=/sdcard/oeminfo"
adb pull /sdcard/oeminfo oeminfo
Make copy original oeminfo file
Download stock HW splash (logo) or make your own picture *.bmp. Bitmap resolution should match your device resolution (1080x1920 pixels). Put it to ADB folder.
In ADB folder use commands:
oem_logo.exe oeminfo logo.bmp
adb push oeminfo /sdcard/oeminfo
adb shell su -c "dd if=/sdcard/oeminfo of=/dev/block/platform/hi_mci.0/by-name/oeminfo"
adb rm -f /sdcard/oeminfo
Reboot
More options described here.
Second way:
Download this (translated bye me) utility
Unzip and use it
Additionally:
If you want to use Huawei stock splash screen you can install this file by custom recovery. It replace any splash screen you have installed by original HW.
Off course you can use this script to installing your own logo. Just replace file \dev\block\platform\hi_mci.0\by-name\oeminfo in downloaded zip by your own file created accordingly to above first method (by oem_logo.exe).
All credits to:
Kostyan_nsk
wistonbogarde
For my just click thanks
Notice !
Everything you are doing on your own RISK !
nice ,but warning oeminfo contain such things as IMEI
Z!L0G80 said:
nice ,but warning oeminfo contain such things as IMEI
Click to expand...
Click to collapse
Are you sure? I'dont think so. At least, I was unable to find IMEI there. And it would be too easy to change IMEI if it could be in oeminfo partition...
Kostyan_nsk said:
Are you sure? I'dont think so. At least, I was unable to find IMEI there. And it would be too easy to change IMEI if it could be in oeminfo partition...
Click to expand...
Click to collapse
imei is crypted by aes key, oeminfo probably contain some other phone related information I DONT RECOMENDED TO FLASH THIS < YOU CAN PROBABLY BRICK YOUR PHONE
hi Kostyan_nsk and z!log80 !
I have recently flashed oeminfo.img without isssues (thanks again Kostyan_nsk)
I wanted to give it a try and ask please Kostyan_nsk or z!log80 for a brief explanation about how oem_logo.exe performs the bitmap replacement. Is it possible to mount oeminfo.img browse its file system and replace a particular file, or is it by searching bitmap signature, …?
Thanks Ziolek67 for starting this thread :laugh:
Printusrzero said:
hi Kostyan_nsk and z!log80 !
I have recently flashed oeminfo.img without isssues (thanks again Kostyan_nsk)
I wanted to give it a try and ask please Kostyan_nsk or z!log80 for a brief explanation about how oem_logo.exe performs the bitmap replacement. Is it possible to mount oeminfo.img browse its file system and replace a particular file, or is it by searching bitmap signature, …?
Thanks Ziolek67 for starting this thread :laugh:
Click to expand...
Click to collapse
do you have same imei as before ? oeminfo doesnt contain filesystem - no mount
yes, same as before
if no file system or mount then I guest search for a pattern or dedicated tool to package... I have been trying to find further more precise information about oeminfo.img but had not found much so far. I would appreciate if you can contribute to make this a bit clearer for me
thanks
[Edited]
After a bit of research I have found other mods for factory device location, etc. writing to particular offsets, tools to modify, backup and restore oeminfo.img. It is a data store. No embedded code. Thnx!
Z!L0G80 said:
imei is crypted by aes key, oeminfo probably contain some other phone related information I DONT RECOMENDED TO FLASH THIS < YOU CAN PROBABLY BRICK YOUR PHONE
Click to expand...
Click to collapse
Eazy. I tried it many times... It works perfectly. I never publish potentially dangerous untested features.
Z!L0G80 said:
imei is crypted by aes key, oeminfo probably contain some other phone related information I DONT RECOMENDED TO FLASH THIS < YOU CAN PROBABLY BRICK YOUR PHONE
Click to expand...
Click to collapse
I flashed whole oeminfo partition from other device and my IMEI stayed the same. As I supposed, it's somewhere else, but not in oeminfo partition. You are wrong.
You must NOT be alarm
Kostyan_nsk said:
I flashed whole oeminfo partition from other device and my IMEI stayed the same. As I supposed, it's somewhere else, but not in oeminfo partition. You are wrong.
Click to expand...
Click to collapse
Do not worry, I also used HW-OEM_LOGO.ZIP to change the booting logo for the original one, and my IMEI is the same as I bought it in the store, so do not be alarmed !!!!:laugh:
Also worked on P8 B321, IMEI stayed the same.
Download links not working, could someone provide new ones please?
Fedroid said:
Download links not working, could someone provide new ones please?
Click to expand...
Click to collapse
Hi!
You can to use the last version File, this is for change the intial Logo and/or bootanimation.
Thanks!
Note:
This is not bootanimation, this is the splash screen (the 'LeEco' boot logo which is displayed when device is switched ON)
This is for LeEco Le 2 / S3 Snapdragon variants Only, like X522/S3 (USA), X520 (Chinese), X526 (Indian), and X527 (International)..
For Mediatek variants, check Post #2..
For other devices, please send me your splash.img so that I can create a tool for you too..
Requirements:
1. Rooted LeEco Le 2 / S3 (any ROM)
2. Optional: Terminal Emulator app or Custom Recovery or atleast working fastboot in computer
3. You're proceeding at your own risk.
STEPS to create splash.img:
1. Download & Extract this in computer: LeEco_Le2_Splash_Maker.zip
2. Make sure you have 4 pictures (same or different) in 1080x1920 px resolution in PNG format.
(It seems Le2 displays any 1 picture from the 4 pictures randomly while switching ON, so I think you'll have to use 4 pictures)
3. Now rename your 4 pictures as logo1.png, logo2.png, logo3.png, logo4.png & replace it inside "pics" folder of the extracted folder.
(Similarly you can replace other pictures in it carefully if you wish)
4. Finally, run the 'CREATE_LOGO.bat' to create splash.img and flashable zip file, which you can find inside the "output" folder after completion.
STEPS to flash splash.img:
Optional: To backup your original splash.img:
Code:
dd if=/dev/block/bootdevice/by-name/splash of=/sdcard/splash.img
(Not necessary though.. You may get it from the stock firmware itself.)
Now, Choose any one easy method:
a. To flash from recovery:
Transfer the flashable_splash.zip to your device and flash from TWRP or CWM or Philz or any other custom recovery.
b. To flash from Terminal Emulator:
Transfer the splash.img to your device's Internal Storage, Open Terminal Emulator & enter the following to flash it:
Code:
su
dd if=/sdcard/splash.img of=/dev/block/bootdevice/by-name/splash
c. To flash from Fastboot mode:
Code:
fastboot flash splash splash.img
Note:
Incase something goes wrong or device doesn't bootup, flash the stock splash.img from custom recovery or fastboot.
If some pictures are jumbled or do not appear, check this trick here: https://forum.xda-developers.com/showpost.php?p=71454608&postcount=18
(Or send me your stock splash.img)
Thanks to @Achyuth Reddy who provided the stock splash.img of Le 2 X526 ..
Hit the Thanks :good: button if it worked for you
You're welcome to share the splash images that you created
For Le 2 Mediatek Variants
For MTK devices, you might have a different partition for that called 'logo'.
Browse in /dev directory to find out where that is present.
After you have found out, dump the logo.bin file by:
Code:
dd if=/<the_directory_where_logo_is_present>/logo of=/sdcard/logo.bin
Now you can edit the logo.bin using this tool:
Changing Boot Logo (logo.bin) - LOGO BUILDER Program
After editing, you can reflash it by:
Code:
dd if=/sdcard/logo.bin of=/<the_directory_where_logo_is_present>/logo
If you did this successfully, please share the details of how you did it so that it will be helpful for others..
Or if that tool doesn't work, send me your logo.bin or splash.img, I'll check it..
Thanks.. Gone try it.. :laugh:
worked fine for me, but couldn't flash it in bootloader mode (had to flash the zip file in twrp). Thanks!
it didn't work properly for me.... the images were not centered and also it got jumbled.... any fix?
Is there any known limitation in image size (not resolution)?
Samples are about 200kb at maximum, what about 500 kb?
update: ok it works with files up to 500kb.
update2: just for demo, btw it's a x527...
JamBax said:
update2: just for demo, btw it's a x527...
Click to expand...
Click to collapse
Hi, can you share this splash Image ?
I have x527 and i like it. :good:
Thanks.
marco-ko said:
Hi, can you share this splash Image ?
I have x527 and i like it. :good:
Thanks.
Click to expand...
Click to collapse
I can and I will do
But I'll have to recreate that one, because I made another one already.
Guess it will be online tomorrow, not to say 'soon'
btw. if anyone knows where to find that android font, that would be great :good:
marco-ko said:
Hi, can you share this splash Image ?
I have x527 and i like it. :good:
Thanks.
Click to expand...
Click to collapse
I uploaded the files to mega (this is first version). (link removed)
sometimes the images seem to be out of order, for example fastboot and recovery are exchanged
Maybe @GokulNC knows why this happens??
JamBax said:
I uploaded the files to mega (this is first version).
sometimes the images seem to be out of order, for example fastboot and recovery are exchanged
Maybe @GokulNC knows why this happens??
Click to expand...
Click to collapse
Thanks JamBax but when i try to open the link to Mega it asks to enter the "Decryption key"
Please verify it.
Can You share also the newest splash You made (if they are for X527)?
marco-ko said:
Thanks JamBax but when i try to open the link to Mega it asks to enter the "Decryption key"
Please verify it.
Can You share also the newest splash You made (if they are for X527)?
Click to expand...
Click to collapse
Sorry for that, try this link
the other one will be in the same folder (V2 of course).
JamBax said:
Sorry for that, try this link
the other one will be in the same folder (V2 of course).
Click to expand...
Click to collapse
Ok i downloads it.
In the folder there is V1 and V1a.....Not V2
Is V1a that You mean V2?
marco-ko said:
Ok i downloads it.
In the folder there is V1 and V1a.....Not V2
Is V1a that You mean V2?
Click to expand...
Click to collapse
V1 is original order which is mixed up at my device,
V1a is mixed up, but shows correct on my device
V2 will be there when it's ready, I'm working on it... :angel:
btw, V2 will be named V2
@marco-ko V2 is online
JamBax said:
@marco-ko V2 is online
Click to expand...
Click to collapse
Thanks :good: :good:
Have anyone tried this X526 splash.img on X520?
Because I have X520 (Chinese version) and I want to see only english text when my phone is booting.
umarbest said:
Because I have X520 (Chinese version) and I want to see only english text when my phone is booting.
Click to expand...
Click to collapse
You can try it yourself :good: the original splash.img is inside the stock rocm archive.
Size should be equal.
Only the cpu (snapdragon) is important.
For all those having issues with the incorrect images appearing.
What worked for me was changing the order the images are processed in CREATE_LOGO.bat, I simply moved logo4 to the bottom of the list.
How to:
Using a text editor to modify CREATE_LOGO.bat
Change:
Code:
set pic4_path="not_found"
if exist "pics\logo4.png" set pic4_path="pics\logo4.png"
if exist "pics\logo4.jpg" set pic4_path="pics\logo4.jpg"
if exist "pics\logo4.jpeg" set pic4_path="pics\logo4.jpeg"
if exist "pics\logo4.bmp" set pic4_path="pics\logo4.bmp"
if exist "pics\logo4.gif" set pic4_path="pics\logo4.gif"
if %pic4_path%=="not_found" echo.logo4.png or logo4.jpg not found in 'pics' folder.. EXITING&echo.&echo.&pause&exit
set pic5_path="not_found"
if exist "pics\fastboot.png" set pic5_path="pics\fastboot.png"
if exist "pics\fastboot.jpg" set pic5_path="pics\fastboot.jpg"
if exist "pics\fastboot.jpeg" set pic5_path="pics\fastboot.jpeg"
if exist "pics\fastboot.bmp" set pic5_path="pics\fastboot.bmp"
if exist "pics\fastboot.gif" set pic5_path="pics\fastboot.gif"
if %pic5_path%=="not_found" echo.fastboot.png or fastboot.jpg not found in 'pics' folder.. EXITING&echo.&echo.&pause&exit
set pic6_path="not_found"
if exist "pics\recovery.png" set pic6_path="pics\recovery.png"
if exist "pics\recovery.jpg" set pic6_path="pics\recovery.jpg"
if exist "pics\recovery.jpeg" set pic6_path="pics\recovery.jpeg"
if exist "pics\recovery.bmp" set pic6_path="pics\recovery.bmp"
if exist "pics\recovery.gif" set pic6_path="pics\recovery.gif"
if %pic6_path%=="not_found" echo.recovery.png or recovery.jpg not found in 'pics' folder.. EXITING&echo.&echo.&pause&exit
set pic7_path="not_found"
if exist "pics\battery.png" set pic7_path="pics\battery.png"
if exist "pics\battery.jpg" set pic7_path="pics\battery.jpg"
if exist "pics\battery.jpeg" set pic7_path="pics\battery.jpeg"
if exist "pics\battery.bmp" set pic7_path="pics\battery.bmp"
if exist "pics\battery.gif" set pic7_path="pics\battery.gif"
if %pic7_path%=="not_found" echo.battery.png or battery.jpg not found in 'pics' folder.. EXITING&echo.&echo.&pause&exit
To:
Code:
set pic4_path="not_found"
if exist "pics\fastboot.png" set pic4_path="pics\fastboot.png"
if exist "pics\fastboot.jpg" set pic4_path="pics\fastboot.jpg"
if exist "pics\fastboot.jpeg" set pic4_path="pics\fastboot.jpeg"
if exist "pics\fastboot.bmp" set pic4_path="pics\fastboot.bmp"
if exist "pics\fastboot.gif" set pic4_path="pics\fastboot.gif"
if %pic4_path%=="not_found" echo.fastboot.png or fastboot.jpg not found in 'pics' folder.. EXITING&echo.&echo.&pause&exit
set pic5_path="not_found"
if exist "pics\recovery.png" set pic5_path="pics\recovery.png"
if exist "pics\recovery.jpg" set pic5_path="pics\recovery.jpg"
if exist "pics\recovery.jpeg" set pic5_path="pics\recovery.jpeg"
if exist "pics\recovery.bmp" set pic5_path="pics\recovery.bmp"
if exist "pics\recovery.gif" set pic5_path="pics\recovery.gif"
if %pic5_path%=="not_found" echo.recovery.png or recovery.jpg not found in 'pics' folder.. EXITING&echo.&echo.&pause&exit
set pic6_path="not_found"
if exist "pics\battery.png" set pic6_path="pics\battery.png"
if exist "pics\battery.jpg" set pic6_path="pics\battery.jpg"
if exist "pics\battery.jpeg" set pic6_path="pics\battery.jpeg"
if exist "pics\battery.bmp" set pic6_path="pics\battery.bmp"
if exist "pics\battery.gif" set pic6_path="pics\battery.gif"
if %pic6_path%=="not_found" echo.battery.png or battery.jpg not found in 'pics' folder.. EXITING&echo.&echo.&pause&exit
set pic7_path="not_found"
if exist "pics\logo4.png" set pic7_path="pics\logo4.png"
if exist "pics\logo4.jpg" set pic7_path="pics\logo4.jpg"
if exist "pics\logo4.jpeg" set pic7_path="pics\logo4.jpeg"
if exist "pics\logo4.bmp" set pic7_path="pics\logo4.bmp"
if exist "pics\logo4.gif" set pic7_path="pics\logo4.gif"
if %pic7_path%=="not_found" echo.logo4.png or logo4.jpg not found in 'pics' folder.. EXITING&echo.&echo.&pause&exit
On my Le x522 I can verify logo1-3, recovery, fastboot, and battery were displayed correctly while logo4 never made an appearance..
JamBax said:
You can try it yourself :good: the original splash.img is inside the stock rocm archive.
Size should be equal.
Only the cpu (snapdragon) is important.
Click to expand...
Click to collapse
Hi guys,
Link was removed ?
where I can to download IMG for X527_english_SplashScreen ?
Which link, which img?
This thread is about how to create your own img (or zip if you like better).
So I have a p10, and decided to see what i could do with it. Having little experience, I managed to get somewhere. Unlocked the bootloader, got twrp, installed it with the command fastboot flash recovery recovery.img and got:
target reported max download size of 471859200 bytes
sending 'recovery' (32034 KB)...
OKAY [ 1.012s]
writing 'recovery'...
OKAY [ 0.200s]
finished. total time: 1.222s
WOOT! Awesome! No problems! Then I issued: fastboot boot recovery.img
And got
downloading 'boot.img'...
OKAY [ 1.020s]
booting...
FAILED (remote: Command not allowed)
finished. total time: 1.030s
WTF?!
So after a bit, I misread and flashed boot.img with: fastboot flash boot boot.img
I guess I flashed the wrong image. I dunno. But now it boots into the screen that tells me "Your device is unlocked and can'r be trusted" tells me its booting, reboots, goes to the same screen again, says its rebooting again, then brings me to Huawei eRecovery. I connect to my wifi network, telling it to download the latest version and recover, and it says "getting package info failed" So I ma stuck with a device that won't boot.
Oh yes, and down volume and power don't bring me to fastboot anymore.
Begging for help here please.
Do the whole rebranding to unbrick, not sure if you flashed wrong image on boot.
Advice: When flashing recovery boot it by powering off and using key combo. Or adb command. Not from fastboot as IMG.
I did a google search on rebranding to unbrick, and found a guide on the 9. So I assume its similar. It first tests me to boot into twrp. I can't. Twrp never got installed. The next step is to get the offical firmware and put it on the SD card. I can't find it. I am in Canada, and can't find any firmware for canada, nevermind anything north american. It is however possible I have found the wrong guide, as I don't really know what I am doing. As a complete noob, links to guides would be nice when possible and available when making recommendations.
The guide is the same for Mate 9/pro and P10/plus
Original: https://forum.xda-developers.com/mate-9/how-to/guide-mate-9-flash-update-package-t3593108
Explained as easy as posible:
Unlock bootloader (check again that boot loader is unlocked)
Download Update ZIP. I suggest rebrand to VTR-L29 C432 !
A. Get ROM update link through hwmt.ru. Click "filelist.xml". ---> http://hwmt.ru/hwmtsite/firmware-database/?firmware_model=VTR-L29&firmware_page=0
B. Observe "update.zip" size, choose more than 1GB file size FULL OTA . Example VTR-L29C432B164 filelist Link, all three update files and path are in the filelist.xml content.
update.zip: Change URL last "filelist.xml" to "update.zip" download file.
update_data_public.zip: Change URL last "filelist.xml" to "public/update_data_full_public.zip" download file, and rename it to "update_data_public.zip"
update_all_hw.zip: Change URL last "filelist.xml" to "hw/spcseas/update_full_hw_spcseas.zip" download file, and rename it to "update_all_hw.zip" Where spcseas is the model of the file you are downoloading.
Update Package (Download these at original post)
Base: HWOTA_2017050101_Base.zip
OS: Windows -> HWOTA_2017050101_Windows.zip
Model: P10 -> HWOTA_2017050201_VTR.zip [Thanks to @crucky verify]
Put HWOTA on pc desktop and on your external SD card (if you have one, otherwise update process will took a couple of minutes more)
Those 3 downloaded files goes on UPDATE dir, inside HWOTA
Run batch file "update.bat" for same model update or rebrand with/without sdcard.
Select rebrand chose what model is desired (Must be the same as the update package)
Always check the process continues (Sometimes it stucks on twrp or need reconnect to PC)
Once finished Factory default reset will start
Do the process twice! select "Same model update" on the second time.
After update successfully, device might be locked again.
smariob said:
The guide is the same for Mate 9/pro and P10/plus
Original: https://forum.xda-developers.com/mate-9/how-to/guide-mate-9-flash-update-package-t3593108
Explained as easy as posible:
Unlock bootloader (check again that boot loader is unlocked)
Download Update ZIP. I suggest rebrand to VTR-L29 C432 !
A. Get ROM update link through hwmt.ru. Click "filelist.xml". ---> http://hwmt.ru/hwmtsite/firmware-database/?firmware_model=VTR-L29&firmware_page=0
B. Observe "update.zip" size, choose more than 1GB file size FULL OTA . Example VTR-L29C432B164 filelist Link, all three update files and path are in the filelist.xml content.
update.zip: Change URL last "filelist.xml" to "update.zip" download file.
update_data_public.zip: Change URL last "filelist.xml" to "public/update_data_full_public.zip" download file, and rename it to "update_data_public.zip"
update_all_hw.zip: Change URL last "filelist.xml" to "hw/spcseas/update_full_hw_spcseas.zip" download file, and rename it to "update_all_hw.zip" Where spcseas is the model of the file you are downoloading.
Update Package (Download these at original post)
Base: HWOTA_2017050101_Base.zip
OS: Windows -> HWOTA_2017050101_Windows.zip
Model: P10 -> HWOTA_2017050201_VTR.zip [Thanks to @crucky verify]
Put HWOTA on pc desktop and on your external SD card (if you have one, otherwise update process will took a couple of minutes more)
Those 3 downloaded files goes on UPDATE dir, inside HWOTA
Run batch file "update.bat" for same model update or rebrand with/without sdcard.
Select rebrand chose what model is desired (Must be the same as the update package)
Always check the process continues (Sometimes it stucks on twrp or need reconnect to PC)
Once finished Factory default reset will start
Do the process twice! select "Same model update" on the second time.
After update successfully, device might be locked again.
Click to expand...
Click to collapse
okay, i know you are trying to be helpful, but I just can't follow it...
You said "Download Update ZIP. I suggest rebrand to VTR-L29 C432 !" Which one of them? Is the B just a build number, and I should get the latest? please remember, you are talking to a noob.
You talk about 3 files, update.zip, update_data_public.zip and update_all_hw.zip Do I need them all? If so the last one, where I change filelist.xml to all /cn/update_full_all_cn.zip doesn't work. See the following link http://update.hicloud.com:8180/TDS/.../v92067/f2/full/all/cn/update_full_all_cn.zip
Also, rename the file, "Where spcseas is the model of the file you are downoloading" Huh? I know I have to replace the word spcseas with something, but with that?
Now it says to run update.bat Whats the point? I have not been directed to plug the phone into the computer, and even if I did, the computer won't recognize it because I can't get it into any mode... Where do I put these files? They all go in the same directory? I just can't follow this guide as much as I try..
THERE IS GOOD NEWS HOWEVER!
I have been able to get it into TWRP! This means I can get into fastboot, which means I can re-flash the correct boot.img, IF I can get my hands on it (and assuming that's the actual issue It likely is. It was working until I flashed this other boot.img file.). So if I can get direction on how to get it, I should be okay. Double triple and quadruple bonus points for just providing me a direct link to the boot.img file to use without having to play around trying to follow guides I can't seem to understand.
UPDATE!!
Now although I can get into TWRP, its hit and miss, but I can get there eventually, it will no longer boot into fastboot/recovery. When I click reboot, and choose bootloader in TWRP, it just freezes..
This is getting frustrating. Apparently getting into the bootloader is hit and miss, but i can do it.
Search for Huawei update extractor in order to get BOOT.IMG from update.app (inside update zip) I could upload one myself, but I'm not at home right now.
TWRP doesn't support reboot atm. You must power off completly. To boot to recovery press power on and vol + until huawei logo appears, then relase power. It should boot to recovery TWRP in this case.
For boot bootloader you press vol - when you are connecting usb cable to PC.
smariob said:
The guide is the same for Mate 9/pro and P10/plus
Original: https://forum.xda-developers.com/mate-9/how-to/guide-mate-9-flash-update-package-t3593108
Explained as easy as posible:
Unlock bootloader (check again that boot loader is unlocked)
Download Update ZIP. I suggest rebrand to VTR-L29 C432 !
A. Get ROM update link through hwmt.ru. Click "filelist.xml". ---> http://hwmt.ru/hwmtsite/firmware-database/?firmware_model=VTR-L29&firmware_page=0
B. Observe "update.zip" size, choose more than 1GB file size FULL OTA . Example VTR-L29C432B164 filelist Link, all three update files and path are in the filelist.xml content.
update.zip: Change URL last "filelist.xml" to "update.zip" download file.
update_data_public.zip: Change URL last "filelist.xml" to "public/update_data_full_public.zip" download file, and rename it to "update_data_public.zip"
update_all_hw.zip: Change URL last "filelist.xml" to "hw/spcseas/update_full_hw_spcseas.zip" download file, and rename it to "update_all_hw.zip" Where spcseas is the model of the file you are downoloading.
Update Package (Download these at original post)
Base: HWOTA_2017050101_Base.zip
OS: Windows -> HWOTA_2017050101_Windows.zip
Model: P10 -> HWOTA_2017050201_VTR.zip [Thanks to @crucky verify]
Put HWOTA on pc desktop and on your external SD card (if you have one, otherwise update process will took a couple of minutes more)
Those 3 downloaded files goes on UPDATE dir, inside HWOTA
Run batch file "update.bat" for same model update or rebrand with/without sdcard.
Select rebrand chose what model is desired (Must be the same as the update package)
Always check the process continues (Sometimes it stucks on twrp or need reconnect to PC)
Once finished Factory default reset will start
Do the process twice! select "Same model update" on the second time.
After update successfully, device might be locked again.
Click to expand...
Click to collapse
smariob said:
Search for Huawei update extractor in order to get BOOT.IMG from update.app (inside update zip) I could upload one myself, but I'm not at home right now.
TWRP doesn't support reboot atm. You must power off completly. To boot to recovery press power on and vol + until huawei logo appears, then relase power. It should boot to recovery TWRP in this case.
For boot bootloader you press vol - when you are connecting usb cable to PC.
Click to expand...
Click to collapse
Thats good to know. I was getting TWRP more often when I did it from off. What was happening was I would holds power and volume up, release power when the logo appeared, and MOST of the time I would boot into TWRP. Sometimes it would just reboot, I would continue to hold up, and it would either reboot, or boot into TWRP. Occasionally I would get the recovery that came with the phone ?!?!
In any event, I managed to get into TWRP, boot into recovery, extract the boot.img, flash it... AND IT WORKED! Phone booted!
So after all this, I backed up EVERYTHING I could using TWRP. The Boot partition, System partition, EVERYTHING! It kept failing on the Data partition, but from my research that wasn't that important anyway. I then installed SuperRoot_noverity_nocrypt.zip, rebooted, installed phh's SuperUser, installed Root Checker, and finally, I have root!!
Thank you so much for the help. About to go "thank clicking" for all the help you provided.
He guys,
as you've read I bricked my phone and I don't know how or where I did the mistake?
Status before brick:
-) FW: EMUI 8.xxx (not exactly sure which one it was)
-) TWRP: 3.2.3.0
-) Rooted
-) BL: unlocked
-) PHONE Unlock
-) FRP Unlock
What I wanted to do:
-) FW Update to: EMUI 9.0 via FirmwareFinder
What I've done:
-) Did a Titanium Backup
-) Installed Firmware Finder
-) Downloaded the Firmware CLT-L29C432E5R1P9B195 (9.0.0.195) (BUT there were ONLY 2 files)
-) 1. file was "update.zip"
-) 2. file was "update_full_CLT-L29_hw_eu.zip"
-) Renamed the files to
-) 1. kept file name "update.zip"
-) 2. file renamed "update_full_CLT-L29_hw_eu.zip" --> update_all_hw.zip
-) Put the 2 files + hurupdater_04.zip + recovery.img (TWRP 3.2.1.0.img) to a folder in Root on my device
-) Reboot to recovery -> TWRP
-) TWRP -> Install -> hurupdater_04.zip
ERRORS:
-) first I saw a message --> "CLT-L09 "Firmware installing --> how can that happened, if I downloaded the CLT-L29 version?
-) Then it aborted the installing process
Current situation:
-) TWRP is installed again --> TWRP 3.2.1.-0 by Pretorian
-) PHONE Unlock
-) FRP Unlock
-) no OS
!! Cannot access my files either via TWRP or Windows explorer --> all files are encrypted and have totally weird names
So please, please help me installing an OS again!
!! And is there a chance to get access to my pictures back???
I appreciate every helpfull advise.
Thanks in advance!!!
He guys,
nobody has an idea to solve/help me with my issues/situation?
I searched the forum and also other forums and pages to find a solution to "my" problem, but without any helpful results.
I am afraid of doing an eRecovery restore because of losing all my data.
I have currently: TWRP installed -> Files/folders with weird names (shown in TWRP & Phone connected to PC "Explorer")
What can I do to save, restore, copy my pictures and files from phone to PC?
Please give me some hints.
This way brought me back
Try downloading the firmware here: FIRMWARE
Then follow these instructions: HEREhttps://forum.xda-developers.com/huawei-p20-pro/development/huawei-p20-pro-charlotte-l29c432b131-8-t3809964
Got me out of a pinch a few times.
Vedrick said:
Try downloading the firmware here: FIRMWARE
Then follow these instructions: HEREhttps://forum.xda-developers.com/huawei-p20-pro/development/huawei-p20-pro-charlotte-l29c432b131-8-t3809964
Got me out of a pinch a few times.
Click to expand...
Click to collapse
Thanks for the help and the links.
BUT before I'll start doing this, there is just one issue left: the encrypted "storage / files" (pics etc.) in TWRP.
BEFORE I want to say, that I've removed all the security barriers like fingerprint, pattern and faceID !!!!
I tried using this https://forum.xda-developers.com/huawei-p20-pro/development/recovery-twrp-3-2-1-0-t3779400
with different kinds of TWRP versions:
TWRP 3.2.1-0.img
twrp_clt_0.1.img frome here
https://forum.xda-developers.com/huawei-p20-pro/development/recovery-twrp-3-2-1-0-t3779400
twrp-3.2.1-0-charlotte-mod.img frome here
https://forum.xda-developers.com/huawei-p20/how-to/how-to-how-to-unbrick-clt-l29c432-t3878714
twrp-3.2.3-4-charlotte.img
But nothing works, my files shown in TWRP -> storage are still encrypted and still shown with weird gibberish names?
Do you know how to solve this, or where I can get the right TWRP version?
I'm totally at the end of ideas and not finding the right way to get access to my pictures and stuff again.
Da_Hausa said:
Thanks for the help and the links.
BUT before I'll start doing this, there is just one issue left: the encrypted "storage / files" (pics etc.) in TWRP.
BEFORE I want to say, that I've removed all the security barriers like fingerprint, pattern and faceID !!!!
I tried using this https://forum.xda-developers.com/huawei-p20-pro/development/recovery-twrp-3-2-1-0-t3779400
with different kinds of TWRP versions:
TWRP 3.2.1-0.img
twrp_clt_0.1.img frome here
https://forum.xda-developers.com/huawei-p20-pro/development/recovery-twrp-3-2-1-0-t3779400
twrp-3.2.1-0-charlotte-mod.img frome here
https://forum.xda-developers.com/huawei-p20/how-to/how-to-how-to-unbrick-clt-l29c432-t3878714
twrp-3.2.3-4-charlotte.img
But nothing works, my files shown in TWRP -> storage are still encrypted and still shown with weird gibberish names?
Do you know how to solve this, or where I can get the right TWRP version?
I'm totally at the end of ideas and not finding the right way to get access to my pictures and stuff again.
Click to expand...
Click to collapse
I honestly don't think any twrp will work, another reason i'll never buy a huawei again. You could try extracting the image files from the update.app that you get from the update.zip file. then manually flash:
You can extract the image files using EMUI Extractor Application.
fastboot flash cust cust.img
fastboot flash system system.img
I believe the pictures are located on the userdata partition. be sure to flash the right android version as it may depend on what framework you have and how far you got when it was updating. You may want to verify the location of those pictures first.
SO I replicated your soft brick, after I backup up my photos. I ccouldn't save them. I'm up and running though. Turns out I had to first manually flash those image files located in update.app. Then I had to do this
Modified\Updated (Bricked device fix)
1) Try downloading the firmware here: FIRMWARE
2) Extract the update.app file from the update.zip, then use EMUI extractor to extract all the image files. You'll then need to manually flash a few of them: (You can move all these images into the main folder of the Reflash tools located in step 3, then run CMD-HERE)
Commands: (Some might error, i forget which but its alright)
fastboot flash cust cust.img
fastboot flash cache cache.img
fastboot flash kernel kernel.img
fastboot flash recovery_ramdisk recovery_ramdis.img (Very Important)
fastboot flash recovery_vbmeta recovery_vbmeta.img
fastboot flash recovery_vendor recovery_vendor.img
fastboot flash vbmeta vbmeta.img
fastboot flash vector vector.img
fastboot flash system system.img
fastboot reboot, unplug the USB-C cable and hold the volume up button. this will put you into recovery mode.
Then you'll need to format data using with the EMUI recovery and if given the option format cache.
Reboot back into bootloader\Download mode.
3) Then follow these instructions: HEREhttps://forum.xda-developers.com/huawei-p20-pro/development/huawei-p20-pro-charlotte-l29c432b131-8-t3809964
Got me out of a pinch a few times.
Unfortunately I seem to have the same issue. I followed @Vedrick's tutorial.
However after fastboot reboot I'm stuck on 'Your device is booting now...'
Any ideas?
I worry that perhaps the 'boot image' on my p20 is messed up. However in the .APP file I can't find the boot image to restore. I do however see 2 SYSTEM images.
nvm! Got it! Had to fastboot erase userdata.
I have the VTR-L29C605E2R1P8B119-log (9.0.1.119), EMUI 9 (android pie) of the P10 and I accidentally deleted my system, with only fastboot and twrp working. My EMUI erecovery is broken since there is no official global PIE update for the P10 (except the chinese) It will say "Failed to get package info"
I need help on how to fix this because I have tried downgrading and no avail.
Tried using funkyhuawei well, i'm getting "Failed to get package info" and i can assure you that the dns was working, and my oem isn't damaged.
Tried using DC-Pheonix but then it says phone not supported.
What a waste of 30$ but it's better than wasting 200$ for a new motherboard.
Tried using the Dload method. Software Install Failed (using the same rom)
Tried doing the HWOTA but it won't write to my recovery because it's set to "Recovery" not "recovery_ramdisk" I tried changing it's script to recovery_ramdisk, but when I tried to boot up to twrp and it gave me func 11 and 2 errors.
Tried flashing the images... Well, I couldn't flash system because of the "cannot load system.img" file.
Tried using oreo images, failed.
Tried using the Multi-Tool for huawei, well i thought it worked but it didn't because it flashed the system and everything else (the program doesn't know that the ramdisk is inside system) it gave me the error #1 at the end. Still didn't boot.
Tried flashing AOSP Roms and I bam it didn't work.
Do you guys have anymore solutions?
Did you try this?
Jannomag said:
Did you try this?
Click to expand...
Click to collapse
I did. But without adb working, I can't get it to work since it will look for devices/emulators which needed adb and it seems like my phone isn't responding to those.
If you flash the twrp image from the archive of the post I linked before, does it boot up and is adb then available?
Jannomag said:
If you flash the twrp image from the archive of the post I linked before, does it boot up and is adb then available?
Click to expand...
Click to collapse
Nope. It does not detect the adb.
Can you try this TWRP please, eventhough it's for Oreo.
If this isn't gonna work do something for me:
- Boot into your working TWRP and open the terminal (under Advanced).
- Type: "ls /dev/block/platform"
- You should get something like "FF3B0000.UFS" or other, please post in the next reply.
- Now type "ls /dev/block/platform/RESULT/by-name" - for RESULT enter the output of the first command.
- Please post the recovery and erecovery lines from the output in your reply.
With this output I should be able to write a small script, but I can't guarantee that this will work.
EDIT: I made a script based on my UFS device. Please do the commands above first.
If it shows "ff3b0000.ufs", then proceed with my script:
- create a new directory on your sdcard (it has to be sd, not internal!) called "downgrade" (without qoutes).
- Download my zip package and put it into /sdcard/downgrade
- Download your desired firmware - it has to be the same region C605! (Links for B374: update.zip, update_full_VTR-L29_hw_la.zip, update_data_full_public.zip)
- put all three zip files into /sdcard/downgrade and rename "update_full_VTR-L29_hw_la.zip" to "update_hw.zip".
- Boot into TWRP, tap in Install and navigate to the sdcard/downgrade directory.
- Install downgrade.zip. If there's any output, post it here.
The device will reboot itselfs and should start into Huawei's recovery, which should install the firmware.
Download my script here.
Jannomag said:
Can you try this TWRP please, eventhough it's for Oreo.
If this isn't gonna work do something for me:
- Boot into your working TWRP and open the terminal (under Advanced).
- Type: "ls /dev/block/platform"
- You should get something like "FF3B0000.UFS" or other, please post in the next reply.
- Now type "ls /dev/block/platform/RESULT/by-name" - for RESULT enter the output of the first command.
- Please post the recovery and erecovery lines from the output in your reply.
With this output I should be able to write a small script, but I can't guarantee that this will work.
EDIT: I made a script based on my UFS device. Please do the commands above first.
If it shows "ff3b0000.ufs", then proceed with my script:
- create a new directory on your sdcard (it has to be sd, not internal!) called "downgrade" (without qoutes).
- Download my zip package and put it into /sdcard/downgrade
- Download your desired firmware - it has to be the same region C605! (Links for B374: update.zip, update_full_VTR-L29_hw_la.zip, update_data_full_public.zip)
- put all three zip files into /sdcard/downgrade and rename "update_full_VTR-L29_hw_la.zip" to "update_hw.zip".
- Boot into TWRP, tap in Install and navigate to the sdcard/downgrade directory.
- Install downgrade.zip. If there's any output, post it here.
The device will reboot itselfs and should start into Huawei's recovery, which should install the firmware.
Download my script here.
Click to expand...
Click to collapse
Thanks for trying to help me, but I think this would work. I tried the ls /dev/block/platform command but it gave me the "sh ls /dev/block/platform: not found. " Is my device unrecoverable now? I tried to flash but gave me the error: 255 Maybe a backup twrp of kernel,cust,oeminfo,product,recovery,system,sys img, vendor, vendor img, version would work if i use the restore button in twrp but I don't have any backups because I forgot to. If you have any it might work I think?
[Solved]
Thanks for your help, I did a bit of changes though to your script.
Instead of of=/dev/block/platform/ff3b0000.ufs/by-name/recovery_ramdisk_a
I changed it to: of=/dev/block/sdd37
It installed the update well.
This explained that the other tools like HWOTA8 didn't work. sdd37 is only on eMMC device which are rare. I forgot that the eMMC devices have a different path tree under /dev than UFS devices.
I'm glad that this works now.
The script is based on HWOTA and I use this in my Update Guide, too.
have u tried to "reinstall" the FULL OTA (the version that u have installed) via HuRu updater?