Database Develop

[Q] Overwrote playlogos1!

As I was following the guide to improve the galaxy's quadrant score, I messed on one of the lines and overwrote the playlogos1 file that was meant to be renamed to playlogosnow.
I'm currently running JM5; do I need a file from the same version or can I take it from something like froyo which I found?
Or will this require me to reflash, and is it safe to do so without the file?

you need this file only to play the startup animation. if you don't care for the animation you can just delete it or replace it with a script (as you did, i suspect?!).
anyway, you can take this file from any firmware to replace your's...

Ah damn. Just to be on the safe side as I had no idea of the file's importance, I've just finished reflashing the firmware to restore it.
Thanks anyway.

SYUNIXT said:
Ah damn. Just to be on the safe side as I had no idea of the file's importance, I've just finished reflashing the firmware to restore it.
Thanks anyway.
Click to expand...
Click to collapse
you'r welcome ... if you want to do the fix again:
the playlogos1 file ist just the binary that play's the animation. it will be started with root-permissions, so you can replace it to run custom commands as root. in our case we want it to
*) make the loop device and set it up
*) mount the ext2.data file
to make the fix permanent.
mine looks like (you have to make the ext2.data file, format it, copy the data and relink before!!!!):
busybox mknod /dev/loop0 b 7 0
busybox losetup /dev/loop0 /data/ext2.data
busybox mount -t ext2 -o noatime,nodiratime /dev/loop0 /data/ext2.data_mp
and if you want your sgs to play the startup animation. you have to rename playlogos1 to something else and start it from the script...got it?
but again, if the file is not there (eg. you deleted it) nothing bad will happen, you will just not see the animation. the sound will still play and everything else will be fine

Can anyone provide me with the playlogos1 file, or somewhere that I can get it? I updated my rom and it somehow was erased.

ayinyesh said:
Can anyone provide me with the playlogos1 file, or somewhere that I can get it? I updated my rom and it somehow was erased.
Click to expand...
Click to collapse
Try OCLF from the market - it used to have a restore playlogo script.

http://www.youtube.com/comment?lc=8KNWgMta4EvqAcKfdwk-z2flON7mZ3RxQDynukPTSjk
Fix boot screen after one click lag fix:
1: Download playlogosnow megaupload. com/?d=M1N9RFMM
2: place the file on your internal sd.
3: replace (copy past) the file using a root manager in /system/bin
4: reboot

Should have posted this in Q&A....

jodue said:
you need this file only to play the startup animation. if you don't care for the animation you can just delete it or replace it with a script (as you did, i suspect?!).
anyway, you can take this file from any firmware to replace your's...
Click to expand...
Click to collapse
You better not advice people to brick their phones. Missing playlogo1 causes your sgs wont boot because it freezes trying to load playlogos1. Thanks for the advice, now i have bricked phone.

Best partition for custom bootanimation in Android 5+

I open this up to the broader community for discussion: Where do you think custom bootanimations should be stored on Lollipop devices?
Android 5.0 introduces a new /oem partition, that allows for a /oem/media/bootanimation.zip file that seems to take precedence over a system/media/bootanimation.zip file (although I haven't checked AOSP source yet to confirm the exact logic). So far only AT&T+Motorola has utilized this functionality on the AT&T-branded Nexus 6, although I imagine many more OEMs will follow, given the added simplicity it provides.
Given this new option, I humbly suggest that the bootanimation community collectively decide to start placing their bootanimations in oem/media/ (via manual directions and flashable zips) for Lollipop devices, for a number of reasons:
- If a device has a pre-loaded /oem/media/bootanimation.zip, the current flashable zips and manual directions to place at /system/media/bootanimation.zip simply will not work (/oem takes precedence)
- Placing the animation on the /oem partition will persist through an OTA update, ROM update, etc.
- Placing the animation on the /oem partition preserves the ability to receive OTA updates, while placing on the /system partition causes Android 5.0+ updates to fail
Ideally, all flashable zips would contain an updater-script that is more thoughtful than all that I've seen to date; specifically testing for an /oem partition and reacting appropriately.

I haven't looked at source yet, but it's interesting to note that /oem/media/bootanimation.zip seems to supercede /system/media/bootanimation.zip (if /oem is present, then only /oem matters), however /oem/media/audio is additive (ringtones and notifications from both /oem and /system are available to the user).

there are only 2 places to boot a boot animation into.. 1st is /system/media/, but its temporary there, and will get replaced when you flash a rom. 2nd place is /data/local/, there it will not get replaced if you flash a rom.

DA6030 said:
I haven't looked at source yet, but it's interesting to note that /oem/media/bootanimation.zip seems to supercede /system/media/bootanimation.zip (if /oem is present, then only /oem matters), however /oem/media/audio is additive (ringtones and notifications from both /oem and /system are available to the user).
Click to expand...
Click to collapse
That's because audio is selected out of a picklist whereas you cannot choose a boot loader.
Its always been the case that boot animation in /data/local will take over /system/media.

rootSU said:
Its always been the case that boot animation in /data/local will take over /system/media.
Click to expand...
Click to collapse
D'oh, I had forgotten about /data/local. So, that means there are three locations now.
/oem/media is documented in the AT&T Nexus 6 thread, although I'm not sure anyone's checked source to see how it's implemented, nor tested to see where it falls in precedence to /data/local.
http://forum.xda-developers.com/showpost.php?p=56942290&postcount=11
And for reference, looking at the Shamu build.prop, it looks like the oem.prop items are imported explicitly into the build.prop, so the precedence there is clear.

DA6030 said:
D'oh, I had forgotten about /data/local. So, that means there are three locations now.
/oem/media is documented in the AT&T Nexus 6 thread, although I'm not sure anyone's checked source to see how it's implemented, nor tested to see where it falls in precedence to /data/local.
http://forum.xda-developers.com/showpost.php?p=56942290&postcount=11
And for reference, looking at the Shamu build.prop, it looks like the oem.prop items are imported explicitly into the build.prop, so the precedence there is clear.
Click to expand...
Click to collapse
you cant just add it there after manually. and theres another place to put the boot animation, but only when building a rom. i dont remember the location, but you can see it yourself, if you delete the boot animations from /system/media/ and /data/local it will appear. this one just says android

simms22 said:
you cant just add it there after manually. and theres another place to put the boot animation, but only when building a rom. i dont remember the location, but you can see it yourself, if you delete the boot animations from /system/media/ and /data/local it will appear. this one just says android
Click to expand...
Click to collapse
It used to be compiled into the frameworks I think.. Not sure if thats still the case.

Heads UP
Don't know if this is actually what caused my bootloop... but I figured I'd mention it here.
I was trying to get rid of the AT&T boot animation on my N6 and while i was renaming to .bak thought to myself, "why don't I just do my own?" Grabbed another one online, put it in /oem/media/ and bam. No boot.
The worst part is I can't fix it without full restore to stock, because I can't seem to access or even view the /oem/ folder at all through recovery. Is it only mounted after boot?
Don't kow if this means anything to y'all, but I figured someone would find this information interesting.

I have tried several times to make use of the /OEM partition with no success. Every time I reboot the contents disappear.

i tried /data/local to see if it still worked and it didnt work for me....

cmh714 said:
i tried /data/local to see if it still worked and it didnt work for me....
Click to expand...
Click to collapse
i just tried myself, you are right. not working here as well.

simms22 said:
you cant just add it there after manually. and theres another place to put the boot animation, but only when building a rom. i dont remember the location, but you can see it yourself, if you delete the boot animations from /system/media/ and /data/local it will appear. this one just says android
Click to expand...
Click to collapse
It is within framework-res.apk/assets/images/ . . there are two images.
android-logo-mask.png
android-logo-shine.PNG
The mask is a static image with partial transparency. The shine scrolls from left to right behind the mask in a loop, shinning through the mask transparency. It is actually a pretty cool way to do it and I know @rascarlo uses it in rastapop instead of the traditional bootanimation.zip

hlxanthus said:
I have tried several times to make use of the /OEM partition with no success. Every time I reboot the contents disappear.
Click to expand...
Click to collapse
I have also tried (only on stock Google builds), and had the same experience.

OEM partition unformatted on non-ATT devices
hlxanthus said:
I have tried several times to make use of the /OEM partition with no success. Every time I reboot the contents disappear.
Click to expand...
Click to collapse
I just realized that on my device (not AT&T-branded), the /oem partition has always been RAW. So, I flashed the oem.img partition from AT&T firmware (although "fastboot format ext4 oem" would probably be good enough) the partition is now formatted correctly, and now I can use it for storing personalized ringtones, bootanimations, etc. that persist through a factory reset.

DA6030 said:
I just realized that on my device (not AT&T-branded), the /oem partition has always been RAW. So, I flashed the oem.img partition from AT&T firmware (although "fastboot format ext4 oem" would probably be good enough) the partition is now formatted correctly, and now I can use it for storing personalized ringtones, bootanimations, etc. that persist through a factory reset.
Click to expand...
Click to collapse
Okay, I gotta ask. I haven't been able to find the OEM.IMG in any of my searches, just the contents found there. I wasn't aware of any att specific factory images . . got a link you can share? If you don't remember, could you upload the IMG?

hlxanthus said:
Okay, I gotta ask. I haven't been able to find the OEM.IMG in any of my searches, just the contents found there. I wasn't aware of any att specific factory images . . got a link you can share? If you don't remember, could you upload the IMG?
Click to expand...
Click to collapse
There are definitely firmware repositories other than the official Google Developers site. The one I'm thinking of hosts the full .zip file they apply using mfastboot at the factory, which includes the signed oem.img, as well as radio parameters (e.g., SIM lock/unlock for subsidized phones). I can't remember XDA's policy on linking to other sites, so I'll leave it to say that if I search for "Motorola Firmware" (incognito, to avoid personalized search results) it's the 3rd and 4th link right now. The specific file you're looking for is SHAMU_LMY47D_release-keys_subsidy-ATT_CFC.xml.zip. I want you to find it, so if that's not helpful, let me know.

DA6030 said:
There are definitely firmware repositories other than the official Google Developers site. The one I'm thinking of hosts the full .zip file they apply using mfastboot at the factory, which includes the signed oem.img, as well as radio parameters (e.g., SIM lock/unlock for subsidized phones). I can't remember XDA's policy on linking to other sites, so I'll leave it to say that if I search for "Motorola Firmware" (incognito, to avoid personalized search results) it's the 3rd and 4th link right now. The specific file you're looking for is SHAMU_LMY47D_release-keys_subsidy-ATT_CFC.xml.zip. I want you to find it, so if that's not helpful, let me know.
Click to expand...
Click to collapse
Found it, thanks!
Edit: for the record fastboot format didn't work on OEM as it won't work on raw partitions. Extracted and flashed it just as you suggested and now have the crazy att boot animation . . which I will be deleting right now. Thanks a bunch. I will likely post something soon for people who wish to do this themselves.
For those interested in this, here is the OEM.IMG. Once I play with it some more I will open a dedicated thread on how to make use of this partition.
As a little teaser, as expected you can place and set default ringtone, alarm and notification tones. Or add a bootanimation.zip. What I expected to work though did, adding user apps to it. Simply create a directory of /app within the oem partion and place your apps in there. It should be noted there is only about 50mb of space in there. I simply used a file manager to go to the /data/app and copy the desired app folder to the oem partition.(not sure you have to but I simply mirrored the file structure used there). In my case I added a copy of Root Explorer and Titanium Backup in there so they are present for all new rom installs.
Download - SHAMU_subsidy-ATT_OEM.zip

hlxanthus said:
Edit: for the record fastboot format didn't work on OEM as it won't work on raw partitions. Extracted and flashed it just as you suggested and now have the crazy att boot animation . . which I will be deleting right now. Thanks a bunch. I will likely post something soon for people who wish to do this themselves.
As a little teaser, as expected you can place and set default ringtone, alarm and notification tones. Or add a bootanimation.zip. What I expected to work though did, adding user apps to it. Simply create a directory of /app within the oem partion and place your apps in there. It should be noted there is only about 50mb of space in there. I simply used a file manager to go to the /data/app and copy the desired app folder to the oem partition.(not sure you have to but I simply mirrored the file structure used there). In my case I added a copy of Root Explorer and Titanium Backup in there so they are present for all new rom installs.
Click to expand...
Click to collapse
That's a great discovery! Would you consider submitting this as a feature request to Titanium Backup ("move app to oem partition")?
Such a pity the partition can't be formatted from fastboot. Did you try including all the option parameters (ext4 and size)? Do you think it could work from the terminal in recovery (and therefore flashable zip)?

DA6030 said:
That's a great discovery! Would you consider submitting this as a feature request to Titanium Backup ("move app to oem partition")?
Such a pity the partition can't be formatted from fastboot. Did you try including all the option parameters (ext4 and size)? Do you think it could work from the terminal in recovery (and therefore flashable zip)?
Click to expand...
Click to collapse
Alas, I tried just a few variables with fastboot format and gave up and just flashed the OEM.IMG. But fastboot did throw an error stating it could not use the format function on a RAW partition, so I don't know if there is some variable that may have worked.
Only real problem is now that I have it formated I can no longer really test what may or may not work. I can play with it some and see if OEM is accessible via recovery (it is not shown in twrp file manager, that I do know). I have a few shamu guys I can call upon to test, so if I think something might work I will give it a shot.
As for any official TiBu support I doubt it would be accepted, the partition is only 50mb so not a lot of room for stuff.

hlxanthus said:
I can play with it some and see if OEM is accessible via recovery (it is not shown in twrp file manager, that I do know). I have a few shamu guys I can call upon to test, so if I think something might work I will give it a shot.
Click to expand...
Click to collapse
Oh, really good point - TWRP support (at minimum ability to for AT&T customers to wipe the partition, but also file manager) is a way better idea. If your shamu guys are able to format /dev/block/platform/dw_mmc.0/by-name/oem from RAW to ext4 using the appropriate updater-script or recovery terminal command, that would be great to point that out to the TWRP team, to add support for format and file manager. Worst case, I would think TWRP could implement wipe (for AT&T customers) using a delete_recursive. And if format is entirely off the table, one could accomplish the same thing with a flashable zip that flashes the AT&T oem.img and then does a delete_recursive.
By the way, have you tried the format commands in any of fastboot, updater-script or recovery terminal to format your ext4 partition back to RAW?

[SOLVED] How to change Boot animation of Huawei P8 Lite (ALE-L21)

Hello buddies,
Today I wanna share a little thing to you.. I always want to change the boot animation of my phone. when I bought Huawei P8 lite I had tried to do so. But I failed because like other previous version of Android (ICS,JB,KK) I didn't find the /media folder in root/system.. That's way flashble zip files of boot animation don't work if you flash them via custom recovery
I searched in google for a solution. I didn't find nothing new there. I also tried some apps like Bootanimation.apk. But the result was same. :crying: :crying:
Finally I solved this problem with my own effort and successfully changed the boot animation..
To change boot animation first of all you must root your device.. if you have a rooted device then download Root Explorer/ Es File Explorer or Something like these.
1. Launch the application which you installed and go to /root folder of your device.
2. Find /cust folder and Click on it.
3. Here you will see some folders. Just click on preinstalled folder.
4. Then go to /public/media folder and you will get a zip named bootanimation.zip. Just delete it or rename it like bootanimation.zip.bak.
5. Now just put your boot animation file in that folder and Reboot your device.
THAT'S ALL
CAUTIONS:
1. Download the boot animation file according to your disply resolution [P8 Lite (ALE-L21) Resolution is 720x1280 ]. Boot animation of other resolution won't work at all.
2. If you download a flashable zip file then extract it and use the bootanimation.zip file which you get inside it.
DOWNLOAD:
Android L Boot Animation Collection
Android Marshmallow Boot Animation Collection

Hi
Do you know how to change a logo to Huawei? Got problem with update via dload - that's ok - I do it with fastboot. I flash system, cust, boot and recovery. Boot animation changed to Huawei but operator's logo (with 'powered by Android') after I power on is still there. Any ideas?
Thanks
Tomek

Thanks, I was searching for that bootanimation.zip. I searched in Google and found nothing.
Very Helpful. Thanks AGAIN!:good:

I can't find my root folder?
Will it work in other huawei devices mine is huawei x1

Rifat Nurr said:
Hello buddies,
Today I wanna share a little thing to you.. I always want to change the boot animation of my phone. when I bought Huawei P8 lite I had tried to do so. But I failed because like other previous version of Android (ICS,JB,KK) I didn't find the /media folder in root/system.. That's way flashble zip files of boot animation don't work if you flash them via custom recovery
I searched in google for a solution. I didn't find nothing new there. I also tried some apps like Bootanimation.apk. But the result was same. :crying: :crying:
Finally I solved this problem with my own effort and successfully changed the boot animation..
To change boot animation first of all you must root your device.. if you have a rooted device then download Root Explorer/ Es File Explorer or Something like these.
1. Launch the application which you installed and go to /root folder of your device.
2. Find /cust folder and Click on it.
3. Here you will see some folders. Just click on preinstalled folder.
4. Then go to /public/media folder and you will get a zip named bootanimation.zip. Just delete it or rename it like bootanimation.zip.bak.
5. Now just put your boot animation file in that folder and Reboot your device.
THAT'S ALL
CAUTIONS:
1. Download the boot animation file according to your disply resolution [P8 Lite (ALE-L21) Resolution is 720x1280 ]. Boot animation of other resolution won't work at all.
2. If you download a flashable zip file then extract it and use the bootanimation.zip file which you get inside it.
DOWNLOAD:
Android L Boot Animation Collection
Android Marshmallow Boot Animation Collection
Click to expand...
Click to collapse
i have already done this with all these methods (with 3 method) but its the same bootloader :crying: :crying: :crying:
pls help me

Iona.bartishvili said:
i have already done this with all these methods (with 3 method) but its the same bootloader :crying: :crying: :crying:
pls help me
Click to expand...
Click to collapse
Try this....
Is a Spanish tool that works like a charm for changing bootlogo and bootanimation
https://mega.nz/#!8BN1FLQB!l-9gTB4NTFLg6bi9Yp86KMz2ZeMsockseWx-Y-ZxY4E
Don't forget to say thanks,
Link to original thread
http://www.htcmania.com/showthread.php?t=1192627
Iona.bartishvili said:
i have already done this with all these methods (with 3 method) but its the same bootloader :crying: :crying: :crying:
pls help me
Click to expand...
Click to collapse
Sent from my Edison 3 using XDA-Developers mobile app

Iona.bartishvili said:
i have already done this with all these methods (with 3 method) but its the same bootloader :crying: :crying: :crying:
pls help me
Click to expand...
Click to collapse
my root file is empty, why? :/
---------- Post added at 01:21 AM ---------- Previous post was at 01:18 AM ----------
Rifat Nurr said:
Hello buddies,
Today I wanna share a little thing to you.. I always want to change the boot animation of my phone. when I bought Huawei P8 lite I had tried to do so. But I failed because like other previous version of Android (ICS,JB,KK) I didn't find the /media folder in root/system.. That's way flashble zip files of boot animation don't work if you flash them via custom recovery
I searched in google for a solution. I didn't find nothing new there. I also tried some apps like Bootanimation.apk. But the result was same. :crying: :crying:
Finally I solved this problem with my own effort and successfully changed the boot animation..
To change boot animation first of all you must root your device.. if you have a rooted device then download Root Explorer/ Es File Explorer or Something like these.
1. Launch the application which you installed and go to /root folder of your device.
2. Find /cust folder and Click on it.
3. Here you will see some folders. Just click on preinstalled folder.
4. Then go to /public/media folder and you will get a zip named bootanimation.zip. Just delete it or rename it like bootanimation.zip.bak.
5. Now just put your boot animation file in that folder and Reboot your device.
THAT'S ALL
CAUTIONS:
1. Download the boot animation file according to your disply resolution [P8 Lite (ALE-L21) Resolution is 720x1280 ]. Boot animation of other resolution won't work at all.
2. If you download a flashable zip file then extract it and use the bootanimation.zip file which you get inside it.
DOWNLOAD:
Android L Boot Animation Collection
Android Marshmallow Boot Animation Collection
Click to expand...
Click to collapse
my root file is empty, why?

Thanks bro you are the best

for marshmallow rom the location of bootanimation is system/etc/media, 720p zip worked fine for me. also don't forget to give it rw-r-r permissions.

Well how to change Honor logo at the boot that appears just before boot animation ?
and from where we can get nice boot logos for honor

Program to do that all for you
Rifat Nurr said:
Hello buddies,
Today I wanna share a little thing to you.. I always want to change the boot animation of my phone. when I bought Huawei P8 lite I had tried to do so. But I failed because like other previous version of Android (ICS,JB,KK) I didn't find the /media folder in root/system.. That's way flashble zip files of boot animation don't work if you flash them via custom recovery
I searched in google for a solution. I didn't find nothing new there. I also tried some apps like Bootanimation.apk. But the result was same. :crying: :crying:
Finally I solved this problem with my own effort and successfully changed the boot animation..
To change boot animation first of all you must root your device.. if you have a rooted device then download Root Explorer/ Es File Explorer or Something like these.
1. Launch the application which you installed and go to /root folder of your device.
2. Find /cust folder and Click on it.
3. Here you will see some folders. Just click on preinstalled folder.
4. Then go to /public/media folder and you will get a zip named bootanimation.zip. Just delete it or rename it like bootanimation.zip.bak.
5. Now just put your boot animation file in that folder and Reboot your device.
THAT'S ALL
CAUTIONS:
1. Download the boot animation file according to your disply resolution [P8 Lite (ALE-L21) Resolution is 720x1280 ]. Boot animation of other resolution won't work at all.
2. If you download a flashable zip file then extract it and use the bootanimation.zip file which you get inside it.
DOWNLOAD:
Android L Boot Animation Collection
Android Marshmallow Boot Animation Collection
Click to expand...
Click to collapse
So I FOUND a program to do all that for you but it was in Spanish, so I translated it and uploaded it here

It doesnot work in my p8 lite ALE-L02 Any solution for installing custom boot animation in Huawei P8 lite ALE-L02
Thank you.:good:

Huawei Honor 4x Balong and Hi6210sft

Hi all
As I said in title I updated to android 5 and now my model number and biuld numbers are changed to "hi6210sft" and "BalongC52B311"
also lots of files like "oeminfo" is deleted and when I copy it, after a reboot its deleted again!
I checked this link and edited "ro.build.display.id" and "ro.product.model" in "build.prop" file
https://forum.xda-developers.com/honor-4x/help/huawei-honor-4x-balong-hi6210sft-fixed-t3324335
but when I flashed again, all things returned to past!
also I changed all of "hi6210sft" to "Che2-L11" in "build.prop" file (because I think maybe the problem is that!) and after flashing all that lines are deleted! and I can't change them back because they are deleted!
now when I turn on my phone the red screen comes up and after some secconds honor logo comes and phone starts
I thing I should copy fresh file of "build.prop"
am I right?
if yes please help me
where can I find fresh file?
please help
Best Regards
PS. I don't know my original build number!

can you give me the link of your downloaded rom?
you have installed the wrong one of your region.

nicolasecc said:
Hi all
As I said in title I updated to android 5 and now my model number and biuld numbers are changed to "hi6210sft" and "BalongC52B311"
also lots of files like "oeminfo" is deleted and when I copy it, after a reboot its deleted again!
I checked this link and edited "ro.build.display.id" and "ro.product.model" in "build.prop" file
https://forum.xda-developers.com/honor-4x/help/huawei-honor-4x-balong-hi6210sft-fixed-t3324335
but when I flashed again, all things returned to past!
also I changed all of "hi6210sft" to "Che2-L11" in "build.prop" file (because I think maybe the problem is that!) and after flashing all that lines are deleted! and I can't change them back because they are deleted!
now when I turn on my phone the red screen comes up and after some secconds honor logo comes and phone starts
I thing I should copy fresh file of "build.prop"
am I right?
if yes please help me
where can I find fresh file?
please help
Best Regards
PS. I don't know my original build number!
Click to expand...
Click to collapse
have you got twrp installed on your device ? if yes now make a clean install of the ROM again.It will mostly solve the problem.

nicolasecc said:
Hi all
As I said in title I updated to android 5 and now my model number and biuld numbers are changed to "hi6210sft" and "BalongC52B311"
also lots of files like "oeminfo" is deleted and when I copy it, after a reboot its deleted again!
I checked this link and edited "ro.build.display.id" and "ro.product.model" in "build.prop" file
https://forum.xda-developers.com/honor-4x/help/huawei-honor-4x-balong-hi6210sft-fixed-t3324335
but when I flashed again, all things returned to past!
also I changed all of "hi6210sft" to "Che2-L11" in "build.prop" file (because I think maybe the problem is that!) and after flashing all that lines are deleted! and I can't change them back because they are deleted!
now when I turn on my phone the red screen comes up and after some secconds honor logo comes and phone starts
I thing I should copy fresh file of "build.prop"
am I right?
if yes please help me
where can I find fresh file?
please help
Best Regards
PS. I don't know my original build number!
Click to expand...
Click to collapse
You are right , u have to replace the build.prop with an original one.

My VIE-L09C432 identifies as EVA now..

Hi,
I am very unsure how this happened, but I think we all can agree that I f***ed up somehow.
Ive been trying to get back to stock B373 (or B370), but with no luck. NOTHING I do works. Flash manually in fastboot with extracted .imgs from Update.App, tools, or trying to get the recovery to flash the Update.APP file (stuck at 5%).
Finally I tried installing the Marshmellow Resurrection Remix, and it says it can't because my device doesn't match the 'allowed ones', and my device is EVA.
So, how the heck do I go back to VIE-L09? Like, I respect that my phone identifies as EVA now, and I support her efforts, but I got work to do
Help?

deecept said:
Hi,
I am very unsure how this happened, but I think we all can agree that I f***ed up somehow.
Ive been trying to get back to stock B373 (or B370), but with no luck. NOTHING I do works. Flash manually in fastboot with extracted .imgs from Update.App, tools, or trying to get the recovery to flash the Update.APP file (stuck at 5%).
Finally I tried installing the Marshmellow Resurrection Remix, and it says it can't because my device doesn't match the 'allowed ones', and my device is EVA.
So, how the heck do I go back to VIE-L09? Like, I respect that my phone identifies as EVA now, and I support her efforts, but I got work to do
Help?
Click to expand...
Click to collapse
Well, looks like your efforts to fix your mobile brought you to an update.app that was made for the "regular" P9 - that's actually called EVA. As Huawei successfully pulled all ROMs from their servers it looks like you have to send your EVA in to their service centre for reassigning surgery
There might be a slight change to change things back to normal yourself with SRK-Tool.
Good luck!

if you can pull out the oeminfo, you can edit it via an hexadecimal editor and change the value EVA to VIE.

xzanium said:
if you can pull out the oeminfo, you can edit it via an hexadecimal editor and change the value EVA to VIE.
Click to expand...
Click to collapse
Do you have any guides to do this? Ill start googlin

helmuth said:
Well, looks like your efforts to fix your mobile brought you to an update.app that was made for the "regular" P9 - that's actually called EVA. As Huawei successfully pulled all ROMs from their servers it looks like you have to send your EVA in to their service centre for reassigning surgery
There might be a slight change to change things back to normal yourself with SRK-Tool.
Good luck!
Click to expand...
Click to collapse
Thank you so much for answering, even tho you couldnt help Appreciate it! Nothing worse than complete silence

boot into twrp -> advanced -> File Manager -> /dev/block/platform/hi_mci.0/by-name/ -> copy "oeminfo" into SD card or other folder visible by computer
then copy the copied "oeminfo" to your computer
open it with an hexadecimal editor (you can use this editor : HxD )
goto offset : 5A200 (just press ctrl+G then write 5A200 then OK) and change EVA to VIE
then goto offset 60200 and change EVA to VIE again
warning : do not change other values in oeminfo
save the changes
recopy the modified oeminfo to your phone then to /dev/block/platform/hi_mci.0/by-name/
reboot

xzanium said:
boot into twrp -> advanced -> File Manager -> /dev/block/platform/hi_mci.0/by-name/ -> copy "oeminfo" into SD card or other folder visible by computer
then copy the copied "oeminfo" to your computer
open it with an hexadecimal editor (you can use this editor : HxD )
goto offset : 5A200 (just press ctrl+G then write 5A200 then OK) and change EVA to VIE
then goto offset 60200 and change EVA to VIE again
warning : do not change other values in oeminfo
save the changes
recopy the modified oeminfo to your phone then to /dev/block/platform/hi_mci.0/by-name/
reboot
Click to expand...
Click to collapse
So, after hours and hours .. Im still stuck.
I've tried the above, but it doesnt fix it. I . have C432 oeminfo file, and custom.bin file. However, I have no clue as to where to put the custom.bin file. It says to place it in /data/, but there arent any custom.bin file there from before, so I'm unsure.
Im really really stuck here, for the first time ever in all my years screwing up in modding/flashing
Any and all help will be greatly appreciated, and there's 0.5 Decred (DCR) for whoever gives me a tip that helps me solve this ****.

try update to your original rom with firmwarefinder (proxy methode)
if FF detect your phone as EVA you can change the model (tap to change model in the menu)