My p9 lite is VNS-L22C706B120. I never upgraded it since I bought it in New Zealand, though I have received notification of updating to B130 for a long while.
Recently I tried updating to B130 in order to get Android 7 finally, but got problem that the successful update takes no effect at all. I still remain at B120 and keep receiving update notification to B130. I described my steps recently as below:
Try Updater
First of all, I tried using Updater downloading the package and install, it says update failed because the package it not found. I found the reason is the update package is stored in internal storage other than SD card. Then I created dload folder and moved update package to SD card, but Updater cannot detect it and keep telling me to download B130. Therefore, I tried pressing Volume Up, Down and Power button together. Then the package is detected and installing started. It is very fast and I was told install success. However, after rebooting I still have B120 and am told to update to B130 by Updater.
Unlock bootloader and root
Yesterday, I decided to try custom ROM, so I managed to unlock the bootloader, install TWRY and root the phone, though I still cannot make B130 update take effect. I searched for a few custom Rom with Android 7, but I found they still required a higher firmware version than B120, like this ROM, which requires EMUI 5.X.
The help I need
I wonder if I can flash the ROMS that require a higher firmware version when I only got B120 firmware. If I cannot, how can I get my firmware updated, through Updater or any other way (like TWRY possibly) ?
I hope I have stated my problem properly so that you guys can understand. I appreciate any suggestions!
Jlw_ said:
My p9 lite is VNS-L22C706B120. I never upgraded it since I bought it in New Zealand, though I have received notification of updating to B130 for a long while...
Click to expand...
Click to collapse
I don't have this device but, your best bet is to post this question within the following Q&A thread that's specific to your device.
https://forum.xda-developers.com/showthread.php?t=3461043
Good Luck!
~~~~~~~~~~~~~~~
I DO NOT provide support via PM unless asked/requested by myself. PLEASE keep it in the threads where everyone can share.
Related
hello, i am new to this site i signed up just to ask this question. i have spent so many hours trying to find a way to downgrade / roll back to the previous version of my device, i have tried to download the stock rom and install it that way but it does not work, it just says it cannot install the update and suggests a website for me to download the stock rom from, which i then downloaded to only find out it still gives me the same error message, is there anyway i can downgrade to lollipop(emui 3.1) from marshmallow (emui 4.0). can i flash the files over or something, please help, also i have tried to unlock the bootloader and everything but it wont allow me to do that, also if you are able to help me root the device then i wont need to rollback to a previous version, kingroot and anything similar only was able to root my phone when i was on lollipop ever since i upgraded kingroot wont root my phone, any help is greatly appreciated, thanks
Really HuaweiP8max is unstable on android 6...? So I am not going to update to 6... Really sad
What is the main problem with 6 ?
Hello xda,
i'm going straight to the problem, i used to have my Huawei GR3 rooted but i decided that i wanted to receive official updates so i could try a specific app that starts with P and ends in GO, thing is, after i flashed my phone with the stock rom from the huawei official website my phone doesn't say it can't receive updates because the phone was modified anymore but won't receive them either, i'm stuck on TAG-L21C328B126, tried using the huawei firmware search app to download the most recent version of the TAG-L21C328 but when i try to update my phone with the most recent updates, the phone always gets a error saying that the package can't find the fingerprints and asks for L21C328B127 or L21C328B128.
Is there a way i can fix this ?
Error mentioned above:
"Package expects build fingerprint of huawei/tag-l21/hwtag-l6753:5.1/huaweitag1/c328b127:user/release-keys or huawei/tag-l21/hwtag-l6753:5.1/huaweitag-l21/c328b128:user/release-keys; this device has huawei/tag-l21/hwtag-l6753:5.1/huaweitag-l21/c328b126:"
PS: Is there a way to update the stock rom update.zip with the small ota updates manually on your computer ? i contacted huawei help center on my country, all they told me was that TAG-L21C440B139 is the last ota for my phone, and since i can't update via android, i was thinking if i could grab the stock rom and just update it with all the otas till it reach TAG-L21C440B139 on my computer.
Best Regards
RD
I have read about this problem on another thread but the problem was poorly explained and i couldn't follow to the processes explained on the replies, so i have created another new thread regarding this problem, because, in addition to being very useful for me, it might be even more useful for people that are searching for a solution.
I will explain briefly the scenario before talking about the problem itself.
I recently (1d ago) got my telephone blocked because of a Hard Brick that i managed to overcome using
DC Phoenix, from which i installed Emui 4.1 and then automatically updated via the built-in updater to Emui 5.0
As before my hard brick i was on a more recent build, Emui 5.1 (B394), i searched on the internet and understood that my current Firmware, "NRD90M test-keys" is a test build (or something like that) which can't be updated with the built-in updater.
So, i want to ask, in order to avoid getting bricked again, if there is a way i can update to the latest Emui available for my device, as in the current state the build, in addition to being obsolete, is also unstable and reports some compatibility errors, E.G. error retrieving microphone service when sending audio messages on WhatsApp, ecc.
i have heard of a method consisting of rolling-back the device to 4.1 again and installing 5.1 via Dload, but can you tell me how to do it more in detail?
EDIT:
Problem solved by rolling back to 4.1 b131 and then updated from internal updater app
Thanks in advance,
Federico
Federico Cervelli said:
I have read about this problem on another thread but the problem was poorly explained and i couldn't follow to the processes explained on the replies, so i have created another new thread regarding this problem, because, in addition to being very useful for me, it might be even more useful for people that are searching for a solution.
I will explain briefly the scenario before talking about the problem itself.
I recently (1d ago) got my telephone blocked because of a Hard Brick that i managed to overcome using
DC Phoenix, from which i installed Emui 4.1 and then automatically updated via the built-in updater to Emui 5.0
As before my hard brick i was on a more recent build, Emui 5.1 (B394), i searched on the internet and understood that my current Firmware, "NRD90M test-keys" is a test build (or something like that) which can't be updated with the built-in updater.
So, i want to ask, in order to avoid getting bricked again, if there is a way i can update to the latest Emui available for my device, as in the current state the build, in addition to being obsolete, is also unstable and reports some compatibility errors, E.G. error retrieving microphone service when sending audio messages on WhatsApp, ecc.
i have heard of a method consisting of rolling-back the device to 4.1 again and installing 5.1 via Dload, but can you tell me how to do it more in detail?
Thanks in advance,
Federico
Click to expand...
Click to collapse
This Should Help You.
https://forum.xda-developers.com/honor-8/how-to/to-emui5-custom-roms-tested-openkirin-t3638445
I assume since you rolled back you have a locked bootloader atm.
Now i know these guides are somewhere but now that you mention it they do seem somewhat hard to find. ( on the app anyways)
But as for rolling back and then updating again via dload ( not TWRP) you need the rollback package and official firmware for your phone model.
Google and/or the guides section here should help you find those.
It should give you two zips containing an UPDATE.APP file each.
You need to put these on a folder named dload (one file at a time)on your sdcard( internal storage should do, too but no guarantees).
Create the folder if it doesn't exist.
Put in the rollback update.app in first.
Then power down and hold vol up+ vol down while powering up and it should flash the file.
Let it finish, boot up, put in the update.app from the firmware in the dload folder ( remove the old file) and repeat the process.
That should be it.
Also, you might be able to sinply dload the actual firmware from the test key build without rolling back but i haven't tried ( i think )
Should the dload process fail, you most likely have the wrong file in your dload folder, or multiple files.
I should mention that the rollback file actually brings you to a test.keys build. It's necessary to flash to full firmware afterwards and dloading the rollback file has always worked for me.
Personally i found that keeping the rollback update.app file for the rollback in the dload folder at all times is a good security measure. (besides the usual backups)
Sent from my OnePlus5 using XDA Labs
SharxX8 said:
I assume since you rolled back you have a locked bootloader atm.
Now i know these guides are somewhere but now that you mention it they do seem somewhat hard to find. ( on the app anyways)
But as for rolling back and then updating again via dload ( not TWRP) you need the rollback package and official firmware for your phone model.
Google and/or the guides section here should help you find those.
It should give you two zips containing an UPDATE.APP file each.
You need to put these on a folder named dload (one file at a time)on your sdcard( internal storage should do, too but no guarantees).
Create the folder if it doesn't exist.
Put in the rollback update.app in first.
Then power down and hold vol up+ vol down while powering up and it should flash the file.
Let it finish, boot up, put in the update.app from the firmware in the dload folder ( remove the old file) and repeat the process.
That should be it.
Also, you might be able to sinply dload the actual firmware from the test key build without rolling back but i haven't tried ( i think )
Should the dload process fail, you most likely have the wrong file in your dload folder, or multiple files.
I should mention that the rollback file actually brings you to a test.keys build. It's necessary to flash to full firmware afterwards and dloading the rollback file has always worked for me.
Personally i found that keeping the rollback update.app file for the rollback in the dload folder at all times is a good security measure. (besides the usual backups)
Sent from my OnePlus5 using XDA Labs
Click to expand...
Click to collapse
can you tell me what rollback package to use? i tried "(FRD-L19&L09, from Android 7.0, EMUI 5.0 to Android 6.0 EMUI 4.1, C900B300, Western Europe)" and didn't work
If you have an L09/19 it should work. Just make sure to flash the rollback package first.
Otherwise since you are on a test key build already, you might want to try to dload MM directly or if that doesn't work, try a stock nougat firmware via dload.
You could also try updating with Firmware Finder via proxy
Sent from my OnePlus5 using XDA Labs
SharxX8 said:
If you have an L09/19 it should work. Just make sure to flash the rollback package first.
Otherwise since you are on a test key build already, you might want to try to dload MM directly or if that doesn't work, try a stock nougat firmware via dload.
You could also try updating with Firmware Finder via proxy
Sent from my OnePlus5 using XDA Labs
Click to expand...
Click to collapse
i'm at 4.1 b131, now should i update via updater (ver. L09C432B380 2,36GB) or it's test keys?
Federico Cervelli said:
i'm at 4.1 b131, now should i update via updater (ver. L09C432B380 2,36GB) or it's test keys?
Click to expand...
Click to collapse
If you are on a regular version of MM, as I understand it, you can update normally, yes
SharxX8 said:
If you are on a regular version of MM, as I understand it, you can update normally, yes
Click to expand...
Click to collapse
but last time i did it it brang me to test keys .-.
EDIT: i tried and it's all working, Thanks!
Federico Cervelli said:
I have read about this problem on another thread but the problem was poorly explained and i couldn't follow to the processes explained on the replies, so i have created another new thread regarding this problem, because, in addition to being very useful for me, it might be even more useful for people that are searching for a solution.
I will explain briefly the scenario before talking about the problem itself.
I recently (1d ago) got my telephone blocked because of a Hard Brick that i managed to overcome using
DC Phoenix, from which i installed Emui 4.1 and then automatically updated via the built-in updater to Emui 5.0
As before my hard brick i was on a more recent build, Emui 5.1 (B394), i searched on the internet and understood that my current Firmware, "NRD90M test-keys" is a test build (or something like that) which can't be updated with the built-in updater.
So, i want to ask, in order to avoid getting bricked again, if there is a way i can update to the latest Emui available for my device, as in the current state the build, in addition to being obsolete, is also unstable and reports some compatibility errors, E.G. error retrieving microphone service when sending audio messages on WhatsApp, ecc.
i have heard of a method consisting of rolling-back the device to 4.1 again and installing 5.1 via Dload, but can you tell me how to do it more in detail?
EDIT:
Problem solved by rolling back to 4.1 b131 and then updated from internal updater app
Thanks in advance,
Federico
Click to expand...
Click to collapse
I am in a very similar situation and unable to solve this. Could some one help in this?
I had unlocked bootload, TWRP and Root. I decided to unroot and lock the bootloader. So, by following the steps mentioned in a different thread, I could successfully flash Marshmallow B130 through Force Update.
Steps followed:
1. Flash Rollback package
2. Flash Full OTA (Marshmallow on B130) from Huawei website which flashed
Now, the real problem started while trying to upgrade to Nougat.
I tried downloading B350 firmware from Firmware Finder. After slow download, it installs fine. But, after reboot I face below problems.
1. The OS is very sluggish and crashes so often
2. The build number says NRD***-test keys
3. No keyboard installed, so not able to login to Google as well.
4. At this point, Factory Reset, Wipe Cache Partition, rollback everything fails.
I had to unlock the bootloader and again force update Rollback Package and then to Marshmallow B130.
Now, I am stuck with B130. I tried downloading B340 and B361 thru Firmware Finder. Both of them installed but with the same result. I mean No keyboard, Test-keys build, Crashes
My Honor 8 model: FRD-L02
What should I do upgrade to Nougat? I have no confidence in Firmware Finder method. Any help appreciated
It's EMUI 5.0.1 not 5.1, I think.
First of all, sorry for both repeating the topic, and for my ignorance!
I have an Honor 8 which is stuck on FRD-L09C432B394 and Android security patch level: 5 August 2017. I have received at least 2 OTA updates since I purchased the device almost 2 years ago but not since September last year (2017)!
I’m in the UK, I did not do anything with the device since I purchased it, and using the latest HiSuite version (HiSuite 8.0.1.300_OVE), no updates available either!
I downloaded a ROM from // huawei - firmware com/ (Sorry, can’t post links!) which is holds the description:
Build: FRDL09C432B521 800521FRDL19C432B521 800521FRDL02C432B521 800521
Android: 8.x - Oreo
Emui: 8.0
Size: 1.38GB
When I unzip this file I only copied UPDATE.APP to dload on MicroSD card, when trying to update via *#*#2846579#*#*, it starts but then fails at 5%!
Now I did some research and it seems like there’s more files required to update, when I unzip the downloaded ROM I only get the following files though:
full_mainpkg.tag (1KB)
new_filecontext_system (27KB)
new_filecontext_vendor (49KB)
UPDATE.APP (2,920,857KB)
VERSION.mbn (1KB)
And one folder named META-INF containing a few files.
When I did some research it seems like the files required are:
1) update.zip
2) update_full_xxxx_yyyy.zip ("xxxx" and "yyyy" = depending from hardware model/region)
3) update_data_full_public.zip
Where do I get these from? Is it UPDATE.APP or update.zip?
What am I missing? And if anyone knows, why am I not getting the update via HiSuite?
Thank you in advance!
YorkiEg said:
First of all, sorry for both repeating the topic, and for my ignorance!
I have an Honor 8 which is stuck on FRD-L09C432B394 and Android security patch level: 5 August 2017. I have received at least 2 OTA updates since I purchased the device almost 2 years ago but not since September last year (2017)!
I’m in the UK, I did not do anything with the device since I purchased it, and using the latest HiSuite version (HiSuite 8.0.1.300_OVE), no updates available either!
I downloaded a ROM from // huawei - firmware com/ (Sorry, can’t post links!) which is holds the description:
Build: FRDL09C432B521 800521FRDL19C432B521 800521FRDL02C432B521 800521
Android: 8.x - Oreo
Emui: 8.0
Size: 1.38GB
When I unzip this file I only copied UPDATE.APP to dload on MicroSD card, when trying to update via *#*#2846579#*#*, it starts but then fails at 5%!
Now I did some research and it seems like there’s more files required to update, when I unzip the downloaded ROM I only get the following files though:
full_mainpkg.tag (1KB)
new_filecontext_system (27KB)
new_filecontext_vendor (49KB)
UPDATE.APP (2,920,857KB)
VERSION.mbn (1KB)
And one folder named META-INF containing a few files.
When I did some research it seems like the files required are:
1) update.zip
2) update_full_xxxx_yyyy.zip ("xxxx" and "yyyy" = depending from hardware model/region)
3) update_data_full_public.zip
Where do I get these from? Is it UPDATE.APP or update.zip?
What am I missing? And if anyone knows, why am I not getting the update via HiSuite?
Thank you in advance!
Click to expand...
Click to collapse
The only method to install Oreo without unlocking bootloader is to flash via HiSuite... Have you tried?
ScardracS said:
The only method to install Oreo without unlocking bootloader is to flash via HiSuite... Have you tried?
Click to expand...
Click to collapse
I'm not sure if you mean flash via HiSuite as in downloading the Oreo ROM then use HiSuite to install it? Or just use HiSuite to check for updates and let it install it?
I do have the latest version of HiSuite (8.0.1.300_OVE) installed. Checking for updates through the software says that I've got the latest official version
YorkiEg said:
I'm not sure if you mean flash via HiSuite as in downloading the Oreo ROM then use HiSuite to install it? Or just use HiSuite to check for updates and let it install it?
I do have the latest version of HiSuite (8.0.1.300_OVE) installed. Checking for updates through the software says that I've got the latest official version
Click to expand...
Click to collapse
Oh, I'm sorry.
You could try method posted on my signature for flashing b399 and then watch if it update to b407
ScardracS said:
Oh, I'm sorry.
You could try method posted on my signature for flashing b399 and then watch if it update to b407
Click to expand...
Click to collapse
You Sir are a genius! :good::good:
I didn’t have the time to try it last week but I just did and miraculously your 2 Update.app files have worked and flashed my device to B399!
Immediately after I got an OTA update to B404! But stuck there unfortunately! No updates available OTA nor on HiSuite after B404! Also trying to instal B407 via dload keeps failing at 5% every time! I read in your thread saying you haven’t done anything to the B399 file? Just deleted ‘Other files’ and rezipped? It worked anyway! Would be great if you could advise me on how to do it for a B407 or B521! If not, you’re still a genius!
Stuck on B404 now! An upgrade from B394, but wouldn’t mind moving up the line a bit!
YorkiEg said:
You Sir are a genius! :good::good:
I didn’t have the time to try it last week but I just did and miraculously your 2 Update.app files have worked and flashed my device to B399!
Immediately after I got an OTA update to B404! But stuck there unfortunately! No updates available OTA nor on HiSuite after B404! Also trying to instal B407 via dload keeps failing at 5% every time! I read in your thread saying you haven’t done anything to the B399 file? Just deleted ‘Other files’ and rezipped? It worked anyway! Would be great if you could advise me on how to do it for a B407 or B521! If not, you’re still a genius!
Stuck on B404 now! An upgrade from B394, but wouldn’t mind moving up the line a bit!
Click to expand...
Click to collapse
For b406 and/or b407 I think you have to expect a bit
ScardracS said:
For b406 and/or b407 I think you have to expect a bit
Click to expand...
Click to collapse
I’m not sure what do you mean? Do I need to expect a bit of patience to get B406/7? I don’t have any patience left, I've had enough with Huawei
I’ve downloaded about 6 different firmware files from B405 to B521, I always tried the FullOTA-MF files first, then OTA-MF, all keeps failing at 5% but I ALWAYS get the ‘Software install failed’ message at 5% every time I try the SD Card\dload\UPDATE.APP method Are the firmware files I’m downloading corrupt? Your files did work so I don't think it's anything to do with my phone, but your files are the only ones that worked! I can't get my head around it
YorkiEg said:
I’m not sure what do you mean? Do I need to expect a bit of patience to get B406/7? I don’t have any patience left, I've had enough with Huawei
I’ve downloaded about 6 different firmware files from B405 to B521, I always tried the FullOTA-MF files first, then OTA-MF, all keeps failing at 5% but I ALWAYS get the ‘Software install failed’ message at 5% every time I try the SD Card\dload\UPDATE.APP method Are the firmware files I’m downloading corrupt? Your files did work so I don't think it's anything to do with my phone, but your files are the only ones that worked! I can't get my head around it
Click to expand...
Click to collapse
You first have to check if installation of each firmware is approved using Firmware Finder app. If it says it's not approved, it will fail at 5%, so there is no point downloading them
For me on my L09-C432, 406 was approved but was not displayed in system update app, I had to use Firmware Finder proxy to send it to system update app. Then I got 407, and could update to Oreo using hisuite on PC.
This method will fail on newer versions, but if 406 is approved for you and not displayed in system update app you can try it.
pix106 said:
You first have to check if installation of each firmware is approved using Firmware Finder app. If it says it's not approved, it will fail at 5%, so there is no point downloading them
For me on my L09-C432, 406 was approved but was not displayed in system update app, I had to use Firmware Finder proxy to send it to system update app. Then I got 407, and could update to Oreo using hisuite on PC.
This method will fail on newer versions, but if 406 is approved for you and not displayed in system update app you can try it.
Click to expand...
Click to collapse
That’s what’s frustrating me, all the firmware files I’ve downloaded are approved for my device Or so does Firmware Finder app says! Yet they all fail to install at 5%!
Proxy method doesn’t work on B404, or at least not working for me So nothing is working now
I’ve had enough with this phone, just to avoid smashing it into a wall next time it drives me crazy, I’m looking to get another phone, Xiaomi Mi A2 might be the one. Still looking though
Successful update
Frustrated as I was I decided to try one last time and I’m running Oreo now
Trick is to use the official Honor rollback package from Android 7.0 to Android 6.0 (B131 in UK), let it preform OTA update back to Android 7 (B380 if I remember correctly) then use Firmware Finder application's in-app proxy to let the phone do the update at this stage! And it worked!
It downloaded the ROM files then when download completed it said the package has changed and requested to download again! I downloaded that and it started installation! Everything went well during installation but at the end it said it has failed because it could not find the update package I thought it failed and restarted the device only to find it running Android 8 and EMUI 8! Full reset and all working flawlessly
HiSuite acknowledges the update and offers to rollback to B407 if you’re having problems! Please note that I was stuck on B394! So even rolling back would be an upgrade
I’ve tested different apps, NFC (I never use it for contactless payments though so can’t confirm that, but I can’t see why it wouldn’t work) Also GPS and everything’s working just fine! Only issue is/was battery draining but that’s due to the auto launch in battery settings! I changed some of the application settings into manual launch and all great now!
Thank you for all those who helped :good: And hopefully this might help some of the frustrated Honor 8 users like myself! And hopefully won’t be stuck on B521 now!
YorkiEg said:
Trick is to use the official Honor rollback package from Android 7.0 to Android 6.0 (B131 in UK)
Click to expand...
Click to collapse
Sorry for the possibly stupid question, but how did you find/apply the rollback package? Was it through firmware finder or is there some other way?
Himmagery said:
Sorry for the possibly stupid question, but how did you find/apply the rollback package? Was it through firmware finder or is there some other way?
Click to expand...
Click to collapse
No such thing as stupid question! We all need to start somewhere
Finding the rollback package is via the official Honor support website for (Preferably) the country where you purchased your handset from. Or if it was EU, any EU country.
Rollback process will be executed by downloading and unzipping 2 files, the Honor 8_Rollback Package_FRD-L09_from Android 7.0 EMUI 5.0 to Android 6.0 EMUI 4.1_C900B300 (Around 75 MB in size) and the Honor 8_Firmware_FRD-L09_Android 6.0_EMUI 4.1_CXYZB131 (Around 1.75GB in size).
Next you should have a MicroSD Card installed, formatted, and create a folder on root called dload.
Then Unzip the files you downloaded, will get you 2 Update.app files, copy the first one (From C900B300) to the dload folder, switch phone off, press Volume-, Volume+ and the Power button and don’t let go till system starts updating, this one won’t take long.
When finished, format you MicroSD Card, create dload folder again, then copy the second Update.app file (From CXYZB131) into the folder, same button combination to update. This update will take longer.
When finished, try Firmware Finder app immediately if you can and use the in-app proxy method to let your phone do the update, if it didn't work, let the phone do OTA update but don’t let it update too many times because Firmware Finder doesn’t work with newer System Update apps.
Hope that helps. And good luck :good:
YorkiEg said:
Frustrated as I was I decided to try one last time and I’m running Oreo now
Trick is to use the official Honor rollback package from Android 7.0 to Android 6.0 (B131 in UK), let it preform OTA update back to Android 7 (B380 if I remember correctly) then use Firmware Finder application's in-app proxy to let the phone do the update at this stage! And it worked!
Click to expand...
Click to collapse
Thanks for the post, finally got some time where I could try this out and i'm now upgraded to 8.0 from the B394 I was previously stuck on.
I noticed a huge lag when first running 8.0 but it seems to have settled.
For me everything seems to be running just fine, all my apps works, all hardware works and, as far as I can see in 0.5 days use the phone runs it all about as good as it did on 7.0 after the initial lag that is
darklighthim said:
Thanks for the post, finally got some time where I could try this out and i'm now upgraded to 8.0 from the B394 I was previously stuck on.
I noticed a huge lag when first running 8.0 but it seems to have settled.
For me everything seems to be running just fine, all my apps works, all hardware works and, as far as I can see in 0.5 days use the phone runs it all about as good as it did on 7.0 after the initial lag that is
Click to expand...
Click to collapse
Glad it worked for you :good:
The fingerprint scanner was a bit of a hit and miss for me when I first updated but it wasn't bad enough to mention, and it has settled now! Other than that, still running smoothly
Hello! I have a Huawei Honor 4C V100R001C636B190. I bought this phone from the Philippines two years ago. I just realized how outdated my phone was now and so it lacked so many new features brought by newer Android versions. So I consulted the EMUI updater but it did not show any updates. Feeling desperate, I searched online for any updates for my phone. I did know that 4C can upgrade to Marshmallow at maximum but I need to upgrade to Lollipop first. So I found a website called CarbonTesla which had Over-the-Air firmware for this specific device. So I chose my region, Asia Pacific, and downloaded the firmware. The firmware for that region was Lollipop, and it said it was compatible with C636 branding, so I thought I was okay. I extracted the .zip file downloaded and copied the dload folder to the top directory of my SD card. After that I did the local update option from the updater and it went to recovery mode. When it booted up, after an instant, it said,
"Version Check fail! Software Install Failed!"
It gave me the option to shutdown the system. So I rebooted the system and got confused why it just said that. I searched it online but none emerged. I tried downloading other ROMs but all showed the same error.
I tried the download mode by pressing all three buttons at once and plugged my phone to a USB cable. The process worked but it got stuck so close to the end and it did not finish installing ever since. So I rebooted and almost lost hope. I checked the word documents that came with the file and saw the supported devices. Apparently, B190 did not come with the supported ones. I searched online for any ROMs that support B190 but none just came out. Are there any other ROMs that are compatible with B190? Or is there a direct link to get it working? Please help me. Thank you so much. Upgrading my phone to the latest version it can get is very wonderful for me. ?