Looking for vendor.img file - Honor 6X Questions & Answers

Hello all,
Does anyone have a vendor.img file for US variant BLN-L24? I am attempting to get back to stock, and I have the boot, recovery, and system files, but my update.app seems to not have vendor.img for some reason. Any help on this is much appreciated.

Hi, a reason because your update.app wouldn't have the vendor.img could be that you're trying to extract the vendor from the wrong update package; which one you used? The vendor is present only in the biggest update.zip file around 1,64GB; are you sure you didn't tried to extract it from one of the other two packages (update data full public/update data hw region code)? The vendor is present only in the package labeled with FULL, and not in normals OTA that you receive through system update. Write me up here your build number for extended, and I'll provide you a download link for a package that will surely contain the vendor.img for BLN-L24

Thanks for the reply. I actually downloaded a new update.app last night that contained the necessary vendor.img.
I now have the issue that when I attempt to go back to stock via dload, my install will get to 5%, fail with a red exclamation point in the middle of the screen, and then only give an option to reboot.
From reading the rolling back to stock thread, it appears my version of update.app just may not be working correctly for dload. I have no clue what build number I was on previously, but it should be the latest update that was available as of a week ago. If you can direct me to a valid working update.app for this variant (BLN-L24), that should get me back to stock. Thanks again for any help.

You should try dload with the latest build available here for BLN-L24Cxxx that has "PV" at the end of the package name http://pro-teammt.ru/firmware-database/ (can't know code region so except if there is only one variant, like C583 for example, be careful on which package you download) i suppose that you could be on this USA variant, but i can't ensure it http://update.hicloud.com:8180/TDS/data/files/p3/s15/G1756/g1755/v103272/f1/full/update.zip

RedSkull23 said:
You should try dload with the latest build available here for BLN-L24Cxxx that has "PV" at the end of the package name http://pro-teammt.ru/firmware-database/ (can't know code region so except if there is only one variant, like C583 for example, be careful on which package you download) i suppose that you could be on this USA variant, but i can't ensure it http://update.hicloud.com:8180/TDS/data/files/p3/s15/G1756/g1755/v103272/f1/full/update.zip
Click to expand...
Click to collapse
Thanks for the link. I will double check when I get home later and try to use dload again.

TurtlePwr82 said:
Thanks for the link. I will double check when I get home later and try to use dload again.
Click to expand...
Click to collapse
You're welcome dude. Let me know if you can solve that out.

RedSkull23 said:
You're welcome dude. Let me know if you can solve that out.
Click to expand...
Click to collapse
So attempting to use the two latest updates available on that site for a basis, I did attempt to use the update.app from each one to attempt install, and get an error message each time when installing package (fail at 5%). At this point, I'm not sure where exactly the fault lies. Just wanted to give you an update.

TurtlePwr82 said:
So attempting to use the two latest updates available on that site for a basis, I did attempt to use the update.app from each one to attempt install, and get an error message each time when installing package (fail at 5%). At this point, I'm not sure where exactly the fault lies. Just wanted to give you an update.
Click to expand...
Click to collapse
I'm sorry that you still are in trouble. I never had luck using dload too, i tried 3 times but I remember that time ago, the thing about using the package with PV at the end was still unknown, so maybe that was the fault. I'll look for users who owns a BLN-L24 to call in cause, in way to ask them to provide a vendor.img for your build and solve this.

RedSkull23 said:
I'm sorry that you still are in trouble. I never had luck using dload too, i tried 3 times but I remember that time ago, the thing about using the package with PV at the end was still unknown, so maybe that was the fault. I'll look for users who owns a BLN-L24 to call in cause, in way to ask them to provide a vendor.img for your build and solve this.
Click to expand...
Click to collapse
Thanks for the help. I've pretty much gone to my backup phone at this point, though I am still trying to fix this one. I thought I had a breakthrough in getting back to stock last night, but upon boot the EliteRom without sound was still flashed. If I could get sound on the EliteRom when I flash it I could live with the phone. I did see that was a reported problem apparently with some of the rooms (loss of sound and video playback).
It's almost as if maybe the custom kernel can no longer be wiped from the phone once it is flashed, and I think that may be where my issue is stemming from, as I have attempted all update.apps from the most recent through to 7/31, all of which fail at 5% through dload, though flashing in fastboot for everything else goes smoothly. I will continue to try to work on it, or just sell the phone. Thanks again for all of your help, it is much appreciated.

Related

[Q] Original ENG version of Ascend Mate 7 MT7-TL10 (3Gb/32GB)

Hi,
It seems I was over zelaous in trying the updated ROMs that were posted on Huawei and NeedRom (didn't look at the file names that stated they Chinese versions).
Looking to see if anyone has a copy or a backup or their original ENGlish or international ROM that I can use to recover mine so I get GAPPS back, being able to define which slot is the 4G slot rather that being told the top one, etc.
I will be eternally grateful if someone can assist.
MT7 firmware
sketchykingy said:
Hi,
It seems I was over zelaous in trying the updated ROMs that were posted on Huawei and NeedRom (didn't look at the file names that stated they Chinese versions).
Looking to see if anyone has a copy or a backup or their original ENGlish or international ROM that I can use to recover mine so I get GAPPS back, being able to define which slot is the 4G slot rather that being told the top one, etc.
I will be eternally grateful if someone can assist.
Click to expand...
Click to collapse
The first link is for the L09 variant. The other, I'm not sure. Saw the TL10 Southeast Asia firmware a couple of days ago over at the official Huawei Philippines website, but it's no longer there now.
http://consumer.huawei.com/it/support/downloads/detail/index.htm?id=31149
http://consumer.huawei.com/pl/support/downloads/detail/index.htm?id=32122
monchinglopez said:
The first link is for the L09 variant. The other, I'm not sure. Saw the TL10 Southeast Asia firmware a couple of days ago over at the official Huawei Philippines website, but it's no longer there now.
Thanks for the links, I have tried no success, they all fail in the upgrade/install.
I went through all the locations/countries on the website looking for the TL10 version, I was unable to find one, even the Generic one that was listed didn't install and came out as a fail (assuming it is meant for TL09).
Oh well will just have to wait for an upload by someone or wait for Huawei to post the ENG ROM update.
Click to expand...
Click to collapse
sketchykingy said:
monchinglopez said:
The first link is for the L09 variant. The other, I'm not sure. Saw the TL10 Southeast Asia firmware a couple of days ago over at the official Huawei Philippines website, but it's no longer there now.
Thanks for the links, I have tried no success, they all fail in the upgrade/install.
I went through all the locations/countries on the website looking for the TL10 version, I was unable to find one, even the Generic one that was listed didn't install and came out as a fail (assuming it is meant for TL09).
Oh well will just have to wait for an upload by someone or wait for Huawei to post the ENG ROM update.
Click to expand...
Click to collapse
Here it is: http://consumer.huawei.com/en/support/downloads/detail/index.htm?id=32364
Click to expand...
Click to collapse
monchinglopez said:
sketchykingy said:
Here it is: http://consumer.huawei.com/en/support/downloads/detail/index.htm?id=32364
Click to expand...
Click to collapse
LEGEND!!!
Click to expand...
Click to collapse
Do you've already flashed it? Version 119 looks a little old, but the upload date seems to be 29th nov. I've patched my cust partition with the files from this version. SIM config, etc. is all there now and Vodafone 4G is selectable now, too. And it shows vodafone.de now instead of vodafone.de 3G. But it looks like it's still not activating 4G. Modem file size looks a little different, well i would try to flash modem, but i'm not sure to which partition, there are several partitions with modem in the name and the space used on these partitions isn't matching the size of the modem.img in the update.app file. Anybody flashed this is living in a 800Mhz lte area? Is it working? Any ideas about the modem partition?
pappschlumpf said:
Do you've already flashed it? Version 119 looks a little old, but the upload date seems to be 29th nov. I've patched my cust partition with the files from this version. SIM config, etc. is all there now and Vodafone 4G is selectable now, too. And it shows vodafone.de now instead of vodafone.de 3G. But it looks like it's still not activating 4G. Modem file size looks a little different, well i would try to flash modem, but i'm not sure to which partition, there are several partitions with modem in the name and the space used on these partitions isn't matching the size of the modem.img in the update.app file. Anybody flashed this is living in a 800Mhz lte area? Is it working? Any ideas about the modem partition?
Click to expand...
Click to collapse
Hi,
Not sure to tell you the truth, mine is stuck on the last 2-3% on the upgrade, regardless of if I do it via the APP, Bootrom, SD or internal card, or if it is plugged into power or PC. Never seems to complete, I have left it for an hour at a time. The Chinese ROMs completed in under 5 minutes so I am not sure what the issue is, I also tried a different SD card, formatted, cleared cache, reset to factory everything My Telstra Sims have the 800hz range but cant confirm at the moment.
Any guidance on the steps you took would be handy.
I've only modified cust partition with the files from the b119 update.app. I've tried to flash it and ended up like you, flashing process immediately stops. For sure this update checks build.prop and stops there. I'll have a look if i could find and mod the update script.
I have the latest version 120sp07 china
to me it does not "return" to that release .. dload fails
For sure because of checking rom version in build.prob in your system partition. You could try to replace it with the one in the update.app before flashing. Should i upload it for you?
I think so too, I can change the build prop ..
according to you which lines need to be changed?
I noticed that the model has changed in JAZZ
currently are with version 120sp07
among other things, now is the output 121sp02
I think the Chinese versions also complicate life here in europe, what do you think?
on the German site they say that you can not load the various firmware
Please and the steps taken.
sketchykingy said:
Please and the steps taken.
Click to expand...
Click to collapse
I received the phone from china with a rom in English already with root and cwm
I had the updates are ready to install rieusciva but not because there was cwm
I wanted to upgrade to a rom Chinese 120sp07 in a forced dload
I had to first remove the cwm recovery and put the original taken by unzipping the SP07
I installed the 120sp07 function forced dload
iI saw that after the phone has changed names in "jazz"
now I can not install the rom General English with dload why not complete the installation
I would go back to the general version eng
andytom69 said:
I received the phone from china with a rom in English already with root and cwm
I had the updates are ready to install rieusciva but not because there was cwm
I wanted to upgrade to a rom Chinese 120sp07 in a forced dload
I had to first remove the cwm recovery and put the original taken by unzipping the SP07
I installed the 120sp07 function forced dload
iI saw that after the phone has changed names in "jazz"
now I can not install the rom General English with dload why not complete the installation
I would go back to the general version eng
Click to expand...
Click to collapse
Andy,
As pappschlumpf said it is a difference in the build.prop file.
He is going to post up the one that he modified to work on his mobile and hopefully the steps taken to replace the file as well.
Then we can use the normal English version.
sketchykingy said:
Andy,
As pappschlumpf said it is a difference in the build.prop file.
He is going to post up the one that he modified to work on his mobile and hopefully the steps taken to replace the file as well.
Then we can use the normal English version.
Click to expand...
Click to collapse
Here's the build.prop as attachement. Extract and replace the one in /system with it. Permissions have to be set to rwrr. If it's still not working, other files are checked by the updater, too.
pappschlumpf said:
Here's the build.prop as attachement. Extract and replace the one in /system with it. Permissions have to be set to rwrr. If it's still not working, other files are checked by the updater, too.
Click to expand...
Click to collapse
@pappschlumpf did you have to root first, or can we get around it by doing something funky?
or do i just rebuild the UPDATE.APP with this new build.prop file?
You need root to replace files in the /system partition.
That's the build.prop from the B119 ROM. If you replace your B121/120 build.prop with it and start flash it could work if build.prop is the only file that is checked before starting flash procedure. I can not say that surely because of not finding an update script in huawei's update.app file.
So let's recap
discharge of the buildprop 119sp3 general attached
I replace this file on my 120sp07 I copy it over with write permissions
after restart or I can immediately update the dload 19sp03 eng general?
andytom69 said:
So let's recap
discharge of the buildprop 119sp3 general attached
I replace this file on my 120sp07 I copy it over with write permissions
after restart or I can immediately update the dload 19sp03 eng general?
Click to expand...
Click to collapse
Yes, i hope so. After replacing the file don't forget to set permissions for build.prop to rw-r-r again! And save a copy of your B120 build.prop to your external SD.

Problem downgrading from Nougat

Hello everybody, i'm having serious trouble trying to downgrade my honor 8 frd l09 to Marshmallow.
The sequence was like this:
I was trying to update to Nougat using several methods and the only one that worked was via de charles method, after using several responses one of them made it update to nougat to the NRD90M test-keys (it originally was FRD-L09C432B131) I though everything was OK until I realized that several apps where not working/missing (every finger id function besides unlocking, the updater app, etc.). The phone worked fine which made me realize one day that not every app was installed or working.
This made me decide to rollback to Marshmallow using this guide/files community .hihonor. com/thread/1700. It failed after the first step and started showing "Your device has failed verification and may not work properly".
So I tried to restore factory settings thinking it would at least install all the apps. This process stopped at 50% and now I'm stuck. I can barely use the phone now because it has very few apps, it doesn't even have the keyboard I can only use the voice command. (still this version NRD90M test-keys)
This is my situation now, can anybody tell me where did I mess up and how can I fix it?
Thanks.
I made the downgrade like 3 times and i had no problems, could you tell me what rollback package you used ?
I will write here what i've done, maybe you can find what you've did wrong.
1. Format SD Card
2. Copied update.app from that little rolback package in the dload folder on SD Card.
3. Flashed it. (Turned off the phone then holding Volume Up+Volume Down+Power Button to get into force update)
4. The phones restarted so i delete the update.app from the dload card an i put there the other update.app (From the B131 android zip)
5. Flashed it. (Turned off the phone then holding Volume Up+Volume Down+Power Button to get into force update)
Sheldd said:
I made the downgrade like 3 times and i had no problems, could you tell me what rollback package you used ?
I will write here what i've done, maybe you can find what you've did wrong.
1. Format SD Card
2. Copied update.app from that little rolback package in the dload folder on SD Card.
3. Flashed it. (Turned off the phone then holding Volume Up+Volume Down+Power Button to get into force update)
4. The phones restarted so i delete the update.app from the dload card an i put there the other update.app (From the B131 android zip)
5. Flashed it. (Turned off the phone then holding Volume Up+Volume Down+Power Button to get into force update)
Click to expand...
Click to collapse
Thanks for your asnwer.
I used this package from the honor website.
FRD-L09
1) FRD-L09 Rollback Package -
2) FRD-L09C432B131 Android M Firmware
I tried to flash the first one and it was when i started having trouble.
emi159 said:
Thanks for your asnwer.
I used this package from the honor website.
FRD-L09
1) FRD-L09 Rollback Package -
2) FRD-L09C432B131 Android M Firmware
I tried to flash the first one and it was when i started having trouble.
Click to expand...
Click to collapse
Are you flashing using the Vol up + vol down + power combination?
Do you have the file update.app on a dload folder on an external sd card?
ViCioPT said:
Are you flashing using the Vol up + vol down + power combination?
Do you have the file update.app on a dload folder on an external sd card?
Click to expand...
Click to collapse
Also make sure to use the key combo without the cable plugged to the phone. You can't go wrong, my phone was pretty much a brick and this method worked on it.
emi159 said:
Hello everybody, i'm having serious trouble trying to downgrade my honor 8 frd l09 to Marshmallow.
The sequence was like this:
I was trying to update to Nougat using several methods and the only one that worked was via de charles method, after using several responses one of them made it update to nougat to the NRD90M test-keys (it originally was FRD-L09C432B131) I though everything was OK until I realized that several apps where not working/missing (every finger id function besides unlocking, the updater app, etc.). The phone worked fine which made me realize one day that not every app was installed or working.
This made me decide to rollback to Marshmallow using this guide/files community .hihonor. com/thread/1700. It failed after the first step and started showing "Your device has failed verification and may not work properly".
So I tried to restore factory settings thinking it would at least install all the apps. This process stopped at 50% and now I'm stuck. I can barely use the phone now because it has very few apps, it doesn't even have the keyboard I can only use the voice command. (still this version NRD90M test-keys)
This is my situation now, can anybody tell me where did I mess up and how can I fix it?
Thanks.
Click to expand...
Click to collapse
I guess your phone cannot boot, you need sdcard then
Download rollback package of your device ( i guess this one) http://download-c.huawei.com/download/downloadCenter?downloadId=92130&version=360508&siteCode=de-h than download full firmware for your device( not ota update).it doesn't matter which version as long as its written full.
Refer this http://hwmt.ru/oth/HWFF/info/view.php?find_model=FRD-L09C432
Create dload folder inside sdcard, extract uppdate.app into dload folder.
Enter recovery by pressing all 3 buttons.
It will show you user reset.
Force shutdown the phone as your phone cannot boot because lacks of apps.
Replaced update.app from dload folder (sdcard) with update.app from your full firmware by extacting it.
Enter recovery again
That should do it.
I made what both said and had success this time. (which were the same I did the first time, don't know how I messed up yet..)
I still want to upgrade to Nougat, what is the best way? Eventually, will I receive the OTA ?
Thanks for your help
emi159 said:
I made what both said and had success this time. (which were the same I did the first time, don't know how I messed up yet..)
I still want to upgrade to Nougat, what is the best way? Eventually, will I receive the OTA ?
Thanks for your help
Click to expand...
Click to collapse
If you had the OTA notification before, you will have it again. Just boot normally, connect to the internet, open HiCare > services > early adopters.
The OTA update notification should pop up.
After updating to Nougat I suggest a factory reset.
emi159 said:
I made what both said and had success this time. (which were the same I did the first time, don't know how I messed up yet..)
I still want to upgrade to Nougat, what is the best way? Eventually, will I receive the OTA ?
Thanks for your help
Click to expand...
Click to collapse
I updated with charles 3 times and I had the same problem as you once. If the OTA package size shows around 2.38gb it will work fine. The one time I had the same issue, the OTA showed to be 1.38gb and after the update I had apps missing/non functional. See what you get this time and if it happens to be the full package.
Make sure you use a correct charles response from this thread: https://forum.xda-developers.com/honor-8/how-to/various-responses-charles-app-b360-t3541342
For me the following procedure was working marvellous:
Initial position: Android 7.0 having opened bootloader, bad working Root, bad working TWRP recovery, SuperSU and Busybox installed
intention (finish): the newest Nougat-FW with closed bootloader and no root-rights
1) First I deleted SuperSU and Busybox and flashed the extracted original honor-recovery from Marshmallow rom in adb
2) I flashed original rollback-package from Nougat to MM which I have downloaded from hihonor link. I put it in dload-folder in external sdcard, switched off phone and hold all 3 hardware.keys untill flashing was forced.
3) after this my Honor booted and I changed the rollback-package file to original Marshmallow-FW (from hihonor link) in dload-folder.
4) I flashed original honor Firmware Marshmallow the same way as it is told in point 2
5) The Honor 8 reboots and at this point I had absolutely clean Marshmallow without root and having the bootloader closed.
6) After about 30 Minutes and 2 or 3 reboots, hicare-app wanted me to upgrade to Nougat. I did.
- thats all. It took much time but it worked reliable on my Honor 8/European version (FRD-L09)
Thanks for all the replies. I'm now on frd -L09C432B131. I will try later to upgrade again with the charles method. I remember as you said that the previous update was 1.38gb, I will take that into consideration.
Thanks
faizalotai said:
I guess your phone cannot boot, you need sdcard then
Download rollback package of your device ( i guess this one) http://download-c.huawei.com/download/downloadCenter?downloadId=92130&version=360508&siteCode=de-h than download full firmware for your device( not ota update).it doesn't matter which version as long as its written full.
Refer this http://hwmt.ru/oth/HWFF/info/view.php?find_model=FRD-L09C432
Create dload folder inside sdcard, extract uppdate.app into dload folder.
Enter recovery by pressing all 3 buttons.
It will show you user reset.
Force shutdown the phone as your phone cannot boot because lacks of apps.
Replaced update.app from dload folder (sdcard) with update.app from your full firmware by extacting it.
Enter recovery again
That should do it.
Click to expand...
Click to collapse
Does Honor/Huawei officially post these update files? I didn't know there was 2 separate update.app files. I'm currently looking for them for my FRD-L04. I want to go back to Marshmallow. Having a hell of a time trying to get BT and NFC to work.
joesee said:
Does Honor/Huawei officially post these update files? I didn't know there was 2 separate update.app files. I'm currently looking for them for my FRD-L04. I want to go back to Marshmallow. Having a hell of a time trying to get BT and NFC to work.
Click to expand...
Click to collapse
BT and NFC files are located in data_full_usa.zip(l04),
If you're going to root and twrp, its better save that file after you wipe data to f2fs format in twrp, than flash those data.zip file....BUT remember, we're already converted the storage to f2fs in nougat to access data storage and that will be pain in a** if you forgot to convert back ext4 format for rollback.
Just remember to convert back to EXT4 in twrp before rollback in MM, otherwise you'll loose everything, no recoveries and bootlooping. Fastboot stated as abnormal thou.
Edit: the wierd thing is, if we looked at data backup in twrp MM, it is f2fs format..
faizalotai said:
BT and NFC files are located in data_full_usa.zip(l04),
If you're going to root and twrp, its better save that file after you wipe data to f2fs format in twrp, than flash those data.zip file....BUT remember, we're already converted the storage to f2fs in nougat to access data storage and that will be pain in a** if you forgot to convert back ext4 format for rollback.
Just remember to convert back to EXT4 in twrp before rollback in MM, otherwise you'll loose everything, no recoveries and bootlooping. Fastboot stated as abnormal thou.
Edit: the wierd thing is, if we looked at data backup in twrp MM, it is f2fs format..
Click to expand...
Click to collapse
Where does this mysterious data_full_usa.zip file come from? I don't see it anywhere in this thread or on XDA? sorry! I believe I found it here: http://modfullandroid.blogspot.com/2016/12/how-to-update-huawei-honor-8-model-frd.html but just want to confirm since it's a strange site I've not been to. Honor's official page doesn't have this file, or "region patch".
Also, it's funny you mentioned that. I COMPLETELY forgot about reformatting the data partition. What I did to downgrade was flash the small UPDATE.APP from the official honor website, then flash the large UPDATE.APP. It seemed to bring everything back up on MM OK for me. Just sucks, because now I miss Nougat after having to go back to emui 4.
joesee said:
Where does this mysterious data_full_usa.zip file come from? I don't see it anywhere in this thread or on XDA? sorry! I believe I found it here: http://modfullandroid.blogspot.com/2016/12/how-to-update-huawei-honor-8-model-frd.html but just want to confirm since it's a strange site I've not been to. Honor's official page doesn't have this file, or "region patch".
Also, it's funny you mentioned that. I COMPLETELY forgot about reformatting the data partition. What I did to downgrade was flash the small UPDATE.APP from the official honor website, then flash the large UPDATE.APP. It seemed to bring everything back up on MM OK for me. Just sucks, because now I miss Nougat after having to go back to emui 4.
Click to expand...
Click to collapse
Well, i got those mysterious data_full_usa.zip from this thread.
Even upgrade package from OFFICIAL released have data full zip with main updated in 1 file.
Thats just a warning if you're going to use recovery. If not then, nothing to be worried about..
Must bugs from TWRP then.
help wanted same problem, while the force update the little zip it was showing "incomfortable version" ....plz help mine is frd-L02
VenuGopalu said:
help wanted same problem, while the force update the little zip it was showing "incomfortable version" ....plz help mine is frd-L02
Click to expand...
Click to collapse
Check out this thread to download the smaller zip.
And pay closer attention to your build number.
takichiman said:
Check out this thread to download the smaller zip.
And pay closer attention to your build number.
Click to expand...
Click to collapse
Thanks for your reply.
I solved this problem by stock recovery flash and force updated mine now working fine . Thanks:good:
VenuGopalu said:
Thanks for your reply.
I solved this problem by stock recovery flash and force updated mine now working fine . Thanks:good:
Click to expand...
Click to collapse
I'm glad to hear that
I did not understand.
How can i recover BT/NFC?
You can explain in a simple way. Thank you.

[GUIDE] Debranding to C432 and updating to B361 (Nougat) for EVA-L09

Like many people here, I was eager to get onto Android 7 but the issue I faced was the fact that I got a branded phone and a long wait till I officially get the Android 7 update. Looking through this forum I was very put off on manually updating it to Android 7 with so many threads about bricked phones. However, the urge to get onto Android 7 was too great so ultimately, I decided to do my research and just do it. I am not new to flashing and custom roms but I am new to Huawei but I had confidence that I will recover if I do brick my new P9. In the end (after a few bricks and a couple of mild heart attacks), I got there and to get there, I needed to grab information from multiple threads. So I have decided to put together this guide so people have a singular guide to debrand and get onto Android 7. Below are steps and threads I took to debrand my C34 to C432 and update it to B361.
What listed below is what I did to get onto Android 7, this may or may not work for you so use this guide at your own risk.
Using this Guide - Please read through this guide BEFORE attempting it. There is a lot of large files to download so I recommend that you download everything you need before you make a start and a fast and reliable internet is strongly recommended.
Prep Work
- Backup all your data because your phone will get wiped.
- Make sure you have the stock recovery already flashed and make sure your phone is not rooted (may not be necessary but this was the state my phone was in).
- Get yourself a bootloader code from Huawei. Go to http://www.emui.com/en/plugin/hwdownload/download, you will need to create a Huawei ID if you haven't already done so. Click on the Unlock Bootloader link and fill out the form, you should get a bootloader code almost instantly after submitting the form.
- Download and install HiSuite (http://consumer.huawei.com/minisite/HiSuite_en/index.html).
- Download the SRK Tool from here: https://forum.xda-developers.com/showpost.php?p=66737472&postcount=2
Now lets make a start.
1. Download and flash the dload-huawei-p9-eval09-eva-b136.zip from this thread: https://forum.xda-developers.com/p9/development/stock-rom-dload-file-p9-eva-l09-b136-t3382818. Instructions on how to flash this is in the first post. After flashing, you should be on the L09C900B136 firmware. NOTE: If it boots up to a white screen asking you to enter password, reboot into recovery by holding volume up when you powering up your phone, do a wipe partition and factory reset. You may need to reboot your phone a number times before the phone boots up correctly.
2. After flashing and booting into the L09C900B136 firmware, you will need to unlock your bootloader and install TWRP. You can use the SRK Tool to do this, please have a look at this thread (https://forum.xda-developers.com/showpost.php?p=66737472&postcount=2) and watch the video on how to do this. NOTE: You only need to unlock bootloader and install the TWRP recovery.
3. After your phone has been unlocked with TWRP recovery installed, download oeminfo-huawei-p9-eval09-c432.zip from this thread: https://forum.xda-developers.com/p9/development/c432-oeminfo-flash-twrp-t3384903 and flash it via TWRP. To get into TWRP, power off your phone and go into recovery by powering up your phone while holding volume up.
4. Once you flashed the oeminfo file via TWRP, power off your phone and repeat step 1. So you need to flash the dload-huawei-p9-eval09-eva-b136.zip file again via the dload method (power on the phone while holding volume up and volume down). NOTE: When you flash this firmware again, it will lock your bootloader (Fastboot will tell you that the phone is unlocked but I assure you, your bootloader is locked) and restore to stock recovery.
5. Once your phone has booted back up, go into the phone settings and you should see that your phone is now on the EVA-L09C432B136 firmware. To test that the firmware is working as intended, go into the phone settings and go into Updater, updater should pick up the B182 firmware and you should be able to update it to B182 without an issue.
UPDATE: A number of people has reported that they are getting the B166 update instead of B182, if this happes, do a wipe partition and a factory reset after updating to B166. When you get back in, you should be able to update to B182 via Updater in the Settings menu. If this method does not work, you can manually update to B182 by following the steps here: http://www.carbontesla.com/2016/11/download-huawei-p9-b182-marshmallow-update-europe/
6. After your phone has rebooted and you are on the B182 firmware, you need to now update the firmware to B361 via Huawei Updater 2.0 using this guide: https://forum.xda-developers.com/showpost.php?p=70594380&postcount=2.
After all that is done, you should now have a debranded UK C432 P9 running EMUI 5.0.
Special thanks to @paulobrien, @somboons and @KrAzYtHeBoY for their guide, tools, files and video to make this update possible.
Props to you sir. I will try this when I get back. I don't have any doubts now after reading this guide.
Does debranding will affect warranty of the device? Mine is quite new.
zoold3vil said:
Does debranding will affect warranty of the device? Mine is quite new.
Click to expand...
Click to collapse
Its very likely that debranding will void your warranty since you will need to unlock the bootloader and flash a firmware that is not the same as your original model.
Z-Blade said:
Its very likely that debranding will void your warranty since you will need to unlock the bootloader and flash a firmware that is not the same as your original model.
Click to expand...
Click to collapse
Thanks for the feedback!
Thanks for the guide. I've recently been battling away trying to go from C34 to C636 - still never got to the bottom of it.
Is that a typo in your post for your original model number - C43? Or did you come from Optus AU C34?
Either way - have you had any network issues in Australia with the new firmware?
Cheers.
halliday77 said:
Thanks for the guide. I've recently been battling away trying to go from C34 to C636 - still never got to the bottom of it.
Is that a typo in your post for your original model number - C43? Or did you come from Optus AU C34?
Either way - have you had any network issues in Australia with the new firmware?
Cheers.
Click to expand...
Click to collapse
Yep, its a typo, thanks for pointing it out. I have no issues what so ever, everything works perfectly fine and there has been no drop in cellular reception, wifi reception, GPS accuracy and etc. Apart from the build saying L09C432, you wouldnt be able to tell the difference.
Z-Blade said:
Yep, its a typo, thanks for pointing it out. I have no issues what so ever, everything works perfectly fine and there has been no drop in cellular reception, wifi reception, GPS accuracy and etc. Apart from the build saying L09C432, you wouldnt be able to tell the difference.
Click to expand...
Click to collapse
Legend. Appreciate the reply - it was tough to find experienced Aussies on the same starting build/carrier.
Now I just wish I hadn't wasted the time going for the Asia Pacific variant!
Will get stuck into it this evening.
Thanks!
Great guide! Reading through it seems easier for it to be managed through hisuite/windows but I have a big issue. For some reason my computer won't recognize my phone! I installed the beta and am on build number EMUI-A168-L09C900B040SP11-log and since doing this stupid move I have been unable to connect to a computer nor install other builds or rollbacks directly on the device so I just feel like smashing it and claiming the insurance. Is there any advise that could be offered to maybe force a firmware upgrade?
Nawor81 said:
Great guide! Reading through it seems easier for it to be managed through hisuite/windows but I have a big issue. For some reason my computer won't recognize my phone! I installed the beta and am on build number EMUI-A168-L09C900B040SP11-log and since doing this stupid move I have been unable to connect to a computer nor install other builds or rollbacks directly on the device so I just feel like smashing it and claiming the insurance. Is there any advise that could be offered to maybe force a firmware upgrade?
Click to expand...
Click to collapse
How did you get onto that build? Have you tried following the guide I put up?
Ha I don't have a clue how I ended up with that build but I've regretted my decision to install a beta version of the nougat every day since. I will try this method this afternoon and see how I go!
Nawor81 said:
Ha I don't have a clue how I ended up with that build but I've regretted my decision to install a beta version of the nougat every day since. I will try this method this afternoon and see how I go!
Click to expand...
Click to collapse
I cant promise you that the guide I put together will work for you. If its a Nougat beta firmware then you would be technically doing a rollback to MM. Just a bit of a warning, a lot of people who try to roll back to MM, usually encounter problems, annoying problems. Unfortunately, I dont have much experience with this phone or how Huawei does things so I cant help you much. If I am in your shoes, I wouldn't attempt to debrand and flash Nougat using this guide.
Z-Blade said:
I cant promise you that the guide I put together will work for you. If its a Nougat beta firmware then you would be technically doing a rollback to MM. Just a bit of a warning, a lot of people who try to roll back to MM, usually encounter problems, annoying problems. Unfortunately, I dont have much experience with this phone or how Huawei does things so I cant help you much. If I am in your shoes, I wouldn't attempt to debrand and flash Nougat using this guide.
Click to expand...
Click to collapse
That's not the news I wanted to hear! I guess I'll keep this guide in mind and do some more research, hopefully find someone in love with Huawei that might be able to assist. Thanks
SmartPhonesFan said:
Hi z-blade I flashed B136 but it didn't put icons and themes back .. I flashed B182 and STILL didn't put icons and themes back
BUT only B166 gave me proper theme and icons back.. ! After that I flashed I had to flash B182 and so on.. B166 is the key important
Click to expand...
Click to collapse
I got theme and icon on mine but it may have came through when I flash B361. I went from a full factory reset on B136 to B182 to B361, not once did I stop to check to make sure all of the apps are installed, I only started setting up my phone and have a browse once I was on EMUI 5.0. It may be un-necessary to flash B166 if flashing B361 give you themes and icons.
If someone could double check on this when following this guide and report in, that would be great. I am not willing to test it out by rolling back to mushmellow.
Nawor81 said:
Ha I don't have a clue how I ended up with that build but I've regretted my decision to install a beta version of the nougat every day since. I will try this method this afternoon and see how I go!
Click to expand...
Click to collapse
Are you on an unbranded device?
If so, the official Huawei support page offers a rollback package if you updated to the Nougat beta.
Make sure you go to the page specific to your country.
---------- Post added at 02:42 AM ---------- Previous post was at 02:34 AM ----------
Z-Blade said:
I got theme and icon on mine but it may have came through when I flash B361. I went from a full factory reset on B136 to B182 to B361, not once did I stop to check to make sure all of the apps are installed, I only started setting up my phone and have a browse once I was on EMUI 5.0. It may be un-necessary to flash B166 if flashing B361 give you themes and icons.
If someone could double check on this when following this guide and report in, that would be great. I am not willing to test it out by rolling back to mushmellow.
Click to expand...
Click to collapse
Broken themes/icons seem to be caused by missing assets in the /CUST/ partition. I managed to get around it on my broken C900 firmware by separately flashing the /hw/normal/ package specific to the build. These can be found in the filelist.xml in the [WAREHOUSE] post - but you need to change the URL manually to grab the file.
SmartPhonesFan said:
So B361 will? Didn't know that.. Didn't want to risk it it took ages to download.. I had 3 folders in B136 but I flashed it via dial pad options.. Not 3btn..maybe if I would flash via 3btn it will give it back then and I wouldn't need B166..
Cannot be bothered.. It's done now..
Nougat best..
Click to expand...
Click to collapse
It makes no difference if you use the 3 button method or via the dial menu, both does exactly the same thing. I am only assuming that Themes could be installed when I flashed B361, I was not paying attention to the apps that was installed but I think this may be the case because I believe the Theme app was updated for EMUI 5.0, again all assumptions here.
Can I jump directly from b136 to b361?
Thanks in advance.
halliday77 said:
Are you on an unbranded device?
If so, the official Huawei support page offers a rollback package if you updated to the Nougat beta.
Make sure you go to the page specific to your country.
Click to expand...
Click to collapse
It's from Vodafone unfortunately
I've followed the guide as far as step 5. When I got there, I ended up getting an update for L09C432B166 which installed fine, but I'm not getting the B182 update. Anyone else run into an issue like this?
trouble2000 said:
Can I jump directly from b136 to b361?
Thanks in advance.
Click to expand...
Click to collapse
No you cant, you need to get to B182 before flashing B361.
d_mouse81 said:
I've followed the guide as far as step 5. When I got there, I ended up getting an update for L09C432B166 which installed fine, but I'm not getting the B182 update. Anyone else run into an issue like this?
Click to expand...
Click to collapse
Try wiping partition and a factory rest and see if you get the B182 update. If not, you can download the B182 update and flash it via dload but if that does not work, you can try doing it via the Hisuite and Updater method.

what is official nougat update for bll-l22

what is the official update for my phone it is BLL-L22 and it is now on b160 (marshmallow)
i have installed the b360 but it has few issues such as 1) no update app 2) build no is tester not official no and so on
yoko89 said:
what is the official update for my phone it is BLL-L22 and it is now on b160 (marshmallow)
i have installed the b360 but it has few issues such as 1) no update app 2) build no is tester not official no and so on
Click to expand...
Click to collapse
It may be because you flashed it manually. And unless we have rollback package for your model you may not be able to rollback to MM. Are you planning to install custom ROM or want to be on stock rom only.
Updater is not there means tou wont get OTA bit test build wont impact anything.
You may need to flash the oeminfo of your model as well.
shashank1320 said:
It may be because you flashed it manually. And unless we have rollback package for your model you may not be able to rollback to MM. Are you planning to install custom ROM or want to be on stock rom only.
Updater is not there means tou wont get OTA bit test build wont impact anything.
You may beed to flash the oeminfo of your model as well.
Click to expand...
Click to collapse
I forgot to update oeminfo now i am updating to 370 as it is the latest and will update oeminfo
yoko89 said:
I forgot to update oeminfo now i am updating to 370 as it is the latest and will update oeminfo
Click to expand...
Click to collapse
Good luck. If need help just post it with details. We will try as much as we can
shashank1320 said:
Good luck. If need help just post it with details. We will try as much as we can
Click to expand...
Click to collapse
Updated successfully using firmware finder
yoko89 said:
Updated successfully using firmware finder
Click to expand...
Click to collapse
I knew from the first post that it was Firmware Finder's fault!! Now your build number is correct?
RedSkull23 said:
I knew from the first post that it was Firmware Finder's fault!! Now your build number is correct?
Click to expand...
Click to collapse
Yes
yoko89 said:
Yes
Click to expand...
Click to collapse
Ok perfect
yoko89 said:
Yes
Click to expand...
Click to collapse
Hide IMEI.
Also, updater in setting visible? How about FM, manager, theme etc?
shashank1320 said:
Hide IMEI.
Also, updater in setting visible? How about FM, manager, theme etc?
Click to expand...
Click to collapse
Yes every thing is working more tha fine
yoko89 said:
Yes every thing is working more tha fine
Click to expand...
Click to collapse
That is cool. Few reported one or the other things missing
Bll-l22c636 b160 to nougat
shashank1320 said:
That is cool. Few reported one or the other things missing
Click to expand...
Click to collapse
Hi.
Bought gr 5 '17 yesterday. Running MM.
I want to update to Nougat, cant find my build number in firmware finder list.
Fb group admin (also member here...) suggested to download a B 370 package.
I want to ask will it work for B160?
Also, any link to step by step instructions for update? Sorry, non tech person here...
Note: if i click to dl a package from Firmware finder, it shows dl as a zip file. Once download is complete, then what?
Thanks in Advance.
GR5_17 said:
Hi.
Bought gr 5 '17 yesterday. Running MM.
I want to update to Nougat, cant find my build number in firmware finder list.
Fb group admin (also member here...) suggested to download a B 370 package.
I want to ask will it work for B160?
Also, any link to step by step instructions for update? Sorry, non tech person here...
Note: if i click to dl a package from Firmware finder, it shows dl as a zip file. Once download is complete, then what?
Thanks in Advance.
Click to expand...
Click to collapse
Give me your exact current build number
shashank1320 said:
Give me your exact current build number
Click to expand...
Click to collapse
Thank you for your reply.
Build number : BLL-L22C636B160
GR5_17 said:
Thank you for your reply.
Build number : BLL-L22C636B160
Click to expand...
Click to collapse
I would advise to wait for official OTA (as you got the phone yesterday) but if you really want to do it-
Download this- http://update.hicloud.com:8180/TDS/data/files/p3/s15/G1279/g104/v82620/f2/full/update.zip
and this http://update.hicloud.com:8180/TDS/...cseas/update_data_full_BLL-L22_hw_spcseas.zip
Flash first file and boot to system. Then 2nd and boot.
You need to use dload method as below
Unzip 1st file and extract the package. You will get few files including update.app.
Few suggest to use only update.app file but I would advise, based on my personal experience for all dload method I tried, use all the files.
Create a folder dload under SD card and copy all the files to this folder.
Power off the phone. Remove USB cable, if connected.
Press volume up+volume down keys and simultaneously press power button (3 keys together)
Your phone will automatically detect the package and will start the update process.
Once the update process is successful, you will get a message as update was successful and your phone will restart automatically.
During restart, phone will verify the system image.
This verification and 1st boot may take upto 2-3 minutes so do not panic.
Repeat the same with 2nd zip file.
Good luck. Happy Flashing.
shashank1320 said:
I would advise to wait for official OTA (as you got the phone yesterday) but if you really want to do it-
Download this- http://update.hicloud.com:8180/TDS/data/files/p3/s15/G1279/g104/v82620/f2/full/update.zip
and this http://update.hicloud.com:8180/TDS/...cseas/update_data_full_BLL-L22_hw_spcseas.zip
Flash first file and boot to system. Then 2nd and boot.
You need to use dload method as below
Unzip 1st file and extract the package. You will get few files including update.app.
Few suggest to use only update.app file but I would advise, based on my personal experience for all dload method I tried, use all the files.
Create a folder dload under SD card and copy all the files to this folder.
Power off the phone. Remove USB cable, if connected.
Press volume up+volume down keys and simultaneously press power button (3 keys together)
Your phone will automatically detect the package and will start the update process.
Once the update process is successful, you will get a message as update was successful and your phone will restart automatically.
During restart, phone will verify the system image.
This verification and 1st boot may take upto 2-3 minutes so do not panic.
Repeat the same with 2nd zip file.
Good luck. Happy Flashing.
Click to expand...
Click to collapse
Thank you very much for the detailed instructions and links.
I think I will take your advice and wait for OTA update.
As mentioned, I am not too 'tech' and am worried might do the wrong thing.
Is it normal for my build # not to have nougat update yet?....
I will bookmark this post and report back in a week. Hopefully I will have an update by then.
Thank you again shashank1320
GR5_17 said:
Thank you very much for the detailed instructions and links.
I think I will take your advice and wait for OTA update.
As mentioned, I am not too 'tech' and am worried might do the wrong thing.
Is it normal for my build # not to have nougat update yet?....
I will bookmark this post and report back in a week. Hopefully I will have an update by then.
Thank you again shashank1320
Click to expand...
Click to collapse
You welcome. Welcome to XDA and tech stuff.
Yes it is normal. Update may pop up anytime. Have you inserted the SIM yet? If not, putting the SIM may help. Also it may take upto a week for your phone to register and get update.
Regards,
Shashank
shashank1320 said:
You welcome. Welcome to XDA and tech stuff.
Yes it is normal. Update may pop up anytime. Have you inserted the SIM yet? If not, putting the SIM may help. Also it may take upto a week for your phone to register and get update.
Regards,
Shashank
Click to expand...
Click to collapse
Thank you for your Welcome Shashank I hope to learn alot from the XDA Forum and you, since this is my 1st Android phone o).
I had not inserted the SIM before, since I'm still learning how the phone works and was playing around with the GR 5 17 without the SIM.
I have inserted the SIM and just like you said; I got an update from the Settings menu.
I am downloading update : BLL-L22C636B360 as we speak.
I am worried since I read on this thread that it might have some problems....
I will post an update once completed.
I am excited to learn more about Android from the XDA Forum, and how I can keep my GR 5 17 in the best condition.
Thank you again for your support Shashank. Stay Well
GR5_17 said:
Thank you for your Welcome Shashank I hope to learn alot from the XDA Forum and you, since this is my 1st Android phone o).
I had not inserted the SIM before, since I'm still learning how the phone works and was playing around with the GR 5 17 without the SIM.
I have inserted the SIM and just like you said; I got an update from the Settings menu.
I am downloading update : BLL-L22C636B360 as we speak.
I am worried since I read on this thread that it might have some problems....
I will post an update once completed.
I am excited to learn more about Android from the XDA Forum, and how I can keep my GR 5 17 in the best condition.
Thank you again for your support Shashank. Stay Well
Click to expand...
Click to collapse
Don't worry, download and install it. If there is any issue you may download further updates. There will few more if your model has it. I got a phone couple of days back amd got 3 updates(different model though)
shashank1320 said:
Don't worry, download and install it. If there is any issue you may download further updates. There will few more if your model has it. I got a phone couple of days back amd got 3 updates(different model though)
Click to expand...
Click to collapse
I have downloaded the B360 update. As you mentioned, I have received another update and am now on : Build number ~: BLL-L22C636B384 , EMUI : 5.0.1, Android : 7.0
Things seem to be working fine for now.
I wanted to ask you about any good Dark theme for the GR5-17.
Do you suggest from the Huawei themes (built in) or from :EMUI theme factory? (an app I dl from PlayStore.
Thank you, Stay Well

Reverted to stock. There are some issues. (SOLVED)

I reverted to stock after messing up my BLN-L24. The ROM is a bit different than the one that shipped with the phone. Some apps are missing. The play store doesn't seem to detect updates even though they can be updated manually when searched. The phone also wont let me update to the latest version. The os it shipped with could update to the latest security update. The play store also says the phone is uncertified. Why is this ROM different? Is there any way i can force an update?
is model number and everything in about section still the same ?
sreekantt said:
is model number and everything in about section still the same ?
Click to expand...
Click to collapse
Yea. I figured it out. I flashed the updates in the wrong order. So i was missing all of the USA files because they were flashed before the actual ROM
sreekantt said:
is model number and everything in about section still the same ?
Click to expand...
Click to collapse
Nevermind. Its still messed up. I dont understand why im not getting any of the USA features installed. i believe its all stock. BLN-L24C567B342 is the build number. BLN-L24 is the model number.
BakedOnSomeSour said:
Nevermind. Its still messed up. I dont understand why im not getting any of the USA features installed. i believe its all stock. BLN-L24C567B342 is the build number. BLN-L24 is the model number.
Click to expand...
Click to collapse
Don't u have any old TWRP backup which consists of OEM info, vendor, product, boot ???
If not, i think you have to use Huawei update extractor on US firmware
Twrp backup would have made the process easy and reliable
There is something very screwed up with the OTA updates for this model phone right now. Consider yourself lucky that your phone still works, I'm dealing with a BLN-L24 that is more than likely unrecoverable all due to some wierd firmware that the official updater installed on the phone on Christmas Eve. Its like the servers are sending bad firmware that isn't for this model but the phone accepts it since it's OTA.
If you haven't read it yet please check out my thread and tell me if you are experiencing anything similar since your OTA. Check out the 3rd post too.
https://forum.xda-developers.com/honor-6x/help/bln-l24-stuck-device-booting-rollback-t3725319
I forgot to mention in my post that overall the phone ran extremely sluggish for a fresh update even though I have no idea what firmware was on the phone. All I know is it was completely foreign to me in all aspects....it was just very wierd overall and in pretty sure you know exactly what I mean since you said it was different.
As for uncertified in play store, try clearing app data for play store and see if it changes to certified.
sreekantt said:
Don't u have any old TWRP backup which consists of OEM info, vendor, product, boot ???
If not, i think you have to use Huawei update extractor on US firmware
Twrp backup would have made the process easy and reliable
Click to expand...
Click to collapse
Unfortunately i don't. I will try to flash the files from the update file with the extractor.
BakedOnSomeSour said:
Unfortunately i don't. I will try to flash the files from the update file with the extractor.
Click to expand...
Click to collapse
Yeah...try
Verify if u downloaded from the appropriate firmware
http://pro-teammt.ru/firmware-database/?firmware_model=BLN-L24C567&firmware_page=0
sreekantt said:
Yeah...try
Verify if u downloaded from the appropriate firmware
http://pro-teammt.ru/firmware-database/?firmware_model=BLN-L24C567&firmware_page=0
Click to expand...
Click to collapse
I flashed the vendor, boot, recovery, and system images with fastboot and then installed the update through erecovery. First i flashed update.zip. Then i flashed update_data_full_BLN-L24_hw_usa. Im still missing all of the USA features. I know all of the apks are in the update_data_full_BLN-L24_hw_usa folder but they arent being put on the system. Is there something i could be missing? Also the install time for update_data_full_BLN-L24_hw_usa is rather short for its size. Is it just being skipped?
BakedOnSomeSour said:
I flashed the vendor, boot, recovery, and system images with fastboot and then installed the update through erecovery. First i flashed update.zip. Then i flashed update_data_full_BLN-L24_hw_usa. Im still missing all of the USA features. I know all of the apks are in the update_data_full_BLN-L24_hw_usa folder but they arent being put on the system. Is there something i could be missing? Also the install time for update_data_full_BLN-L24_hw_usa is rather short for its size. Is it just being skipped?
Click to expand...
Click to collapse
Just to confirm we r on the same lines
U just mentioned that u flashed update.zip
Did u mean 'install it via dload method' .....If installing via dload method...u need to extract update.zip and place the contents in dload folder of sd card.
If u r doing the same....what are the exact apps and features which are missing ?
sreekantt said:
Just to confirm we r on the same lines
U just mentioned that u flashed update.zip
Did u mean 'install it via dload method' .....If installing via dload method...u need to extract update.zip and place the contents in dload folder of sd card.
If u r doing the same....what are the exact apps and features which are missing ?
Click to expand...
Click to collapse
Yes by flash i mean using the dload method. I extracted the content of the update.zip and put it in the dload folder on the sd card. After that i put the files from update_data_full_BLN-L24_hw_usa folder into dload and run the update. When the phone boots i am taken to a rather boring stock setup without any bloat apps. Its missing default wallpapers and themes. The play store fails to detect that the preinstalled apps need updates. Its almost like a completely different phone. A completely different broken phone. The apps below should be on the phone
UPDATe: Got an OTA and everything is back to normal. Thanks for the help
BakedOnSomeSour said:
Yes by flash i mean using the dload method. I extracted the content of the update.zip and put it in the dload folder on the sd card. After that i put the files from update_data_full_BLN-L24_hw_usa folder into dload and run the update. When the phone boots i am taken to a rather boring stock setup without any bloat apps. Its missing default wallpapers and themes. The play store fails to detect that the preinstalled apps need updates. Its almost like a completely different phone. A completely different broken phone. The apps below should be on the phone
UPDATe: Got an OTA and everything is back to normal. Thanks for the help
Click to expand...
Click to collapse
:highfive: nice

Categories

Resources