Hello,
I have been searching for different rom builds and rom build versions trying to get on main european version CUSTC432 and reason is that I want to have latest and official ROM version.
So far i found and tried to flash B126; B133; B602; B609.
I tried local update way and also forced flashing. result still the same.
B126 and B133 I downloaded was marked as CUSTC432 however after flashing I always see CUSTC555
B602 and B609 after flashing doesnt not show any CUSTC version. line with custom version info is not provided in 'About Phone' menu.
Maybe anyone know and can help me to find the way to get version CUSTC432?
don't know what you exactly mean and want..
but my cust is what you are searching,right?
Gesendet von HUAWEI Ascend P7-L10 B609 - rooted
yes, right. that one is what I wanted to get as well
ok felas, after spending 4 days finally i managed to get rid of CUSTC555 version.
It was strange how it worked but maybe for some other people it will work same way, so make it on your own risk.
I found in one of huawei provided software packages additional update.app.
I copied this and started 'local update'
This removed everything(format data, format cache) from internal card, as well as it changed rom version to CUSTC432.
Installation of the update.app actually failed on the end however cleanup scripts probably were the only thing needed.
Straight after reboot I got OTA from huawei for B609 (this was my main target to get)
attached update.app correct size should be around 18KB
extract it and place on sdcard/dload/
yrxe said:
ok felas, after spending 4 days finally i managed to get rid of CUSTC555 version.
It was strange how it worked but maybe for some other people it will work same way, so make it on your own risk.
I found in one of huawei provided software packages additional update.app.
I copied this and started 'local update'
This removed everything(format data, format cache) from internal card, as well as it changed rom version to CUSTC432.
Installation of the update.app actually failed on the end however cleanup scripts probably were the only thing needed.
Straight after reboot I got OTA from huawei for B609 (this was my main target to get)
attached update.app correct size should be around 18KB
extract it and place on sdcard/dload/
Click to expand...
Click to collapse
Mine is CUSTC10D609, is it worth to keep it ?
I think 432 has all functions included so nothing comes to my mind why would you need that to keep
yrxe said:
I think 432 has all functions included so nothing comes to my mind why would you need that to keep
Click to expand...
Click to collapse
I did everything as you mentioned above, currently im on b609, but when i tried to local update, it failed, but i'm still on the same CUSTC
http://forum.xda-developers.com/showthread.php?p=57504273
Try this maybe it will work
I missed to notice that you are on b609. I think these debranding methods will work only on b133.
So if you may try to rollback to b133 and then try these update packages.
Related
Hi.
I'm just wondering if anybody can help me please?
I have a UK Huawei P9 EVA-L09 with Marshmallow currently on it (B166) build I think. It is unlocked and has TWRP 3.0.2.0 Recovery installed on it.
I would like to upgrade to Nougat 7.0 and EMUI 5.0, but most of my attempts have failed and I have had to use the rollback method to get back to Marshmallow.
I have tried to do it by flashing an Update.zip and subsequent EU_Apps package.zip through TWRP to no avail.
I have also tried the 'Dload' folder method, also to no avail. The closest I've gotten is to build no B378, but it shows up as NRD90M Test-Keys on the Build No in the phone settings instead and all apps such as camera, NFC, Bluetooth are missing / not working etc. Trying to then flash the EU_Apps package through 'Dload' method doesn't alleviate the problem of missing apps.
Does anybody have any tips for what I could try to get it onto a working Nougat build with apps please?
Also, if anybody has any links to any relevant firmware etc, then that would be very helpful too.
I'm pulling my hair our trying to get this to work. Surely it's can't be that hard can it??
Many thanks, Bill.
Is your phone branded? For a particular UK network I mean? And if so are you flashing ROMs for that network?
I don't know if that's the problem but I was on Vodafone UK B137 (which is Marshmallow) and flashed the 2 update zips for a Vodafone Nougat ROM thru TWRP and it was successful. I then flashed an updated zip using the "dload method" and that was successful too.
When you say you flashed the zips in TWRP "to no avail", what exactly was the end result?
Also might help if you give the full version of your starting ROM, and what zips you were trying to flash, ie full names and sources.
I'm kinda new to this device forum but seems like people get varying results with different flashing methods, for no particular reason either!
Peace.
chris5s said:
Is your phone branded? For a particular UK network I mean? And if so are you flashing ROMs for that network?
I don't know if that's the problem but I was on Vodafone UK B137 (which is Marshmallow) and flashed the 2 update zips for a Vodafone Nougat ROM thru TWRP and it was successful. I then flashed an updated zip using the "dload method" and that was successful too.
When you say you flashed the zips in TWRP "to no avail", what exactly was the end result?
Also might help if you give the full version of your starting ROM, and what zips you were trying to flash, ie full names and sources.
I'm kinda new to this device forum but seems like people get varying results with different flashing methods, for no particular reason either!
Peace.
Click to expand...
Click to collapse
Hi. Thanks for your reply.
When I tried to flash .Zips through TWRP it kept coming up with errors and didn't flash them (something about being umnable to mount /System).
I was on EE UK, but found a method yesterday for debranding my phone and setting it to C432. I also managed to successfully flash C432B182 firmware on it.
I have since attempted to flash Nougat B360 using the 'Dload' method and now my phone keeps asking me to enter my password to decrypt storage. Multiple attempts to reset my phone and wipe cache partitian don't seem to be working. Do you have any idea how I can get around this?
It's so hard and it's so annoying how other people seem to be getting it right and mine is proving to be a swine. Makes me want to get rid of it to be honest and get something easier.
Thanks again, Bill.
I'm concerned that this may be bricked right now. No amount of using eRecovery to reset the phone will stop it from going onto the dreaded 'enter password to decrypt storage' screen! I will see if I can re flash it using Fastboot, but I'm a bit concerned right now...
I have an O2 Branded one. I'm too chicken to mess with it in case I brick it!
Just waiting for the official UK O2 OTA update to arrive &
tmohammad said:
I have an O2 Branded one. I'm too chicken to mess with it in case I brick it!
Just waiting for the official UK O2 OTA update to arrive &
Click to expand...
Click to collapse
Probably advisable unless you absolutely know what you're doing and don't mind taking the risk. I'm a bit annoyed with Huawei and my carrier, they are always so slow with providing updates and Hmui 5.0 is only what Hmui 4.0 should have been in the first place. I'm done with these manufacturer's stupid over bloated overlays and will be going to an official Google phone in future!
If you can get it into fastboot mode, flash TWRP, then you should be able to progress from there, hopefully by at least formatting data to get rid of the encryption! Sounds like.a royal pita tho to be honest.
When I flashed to Nougat from MM using TWRP I got a bunch of error messages too, but it (eventually) booted up ok....
chris5s said:
If you can get it into fastboot mode, flash TWRP, then you should be able to progress from there, hopefully by at least formatting data to get rid of the encryption! Sounds like.a royal pita tho to be honest.
When I flashed to Nougat from MM using TWRP I got a bunch of error messages too, but it (eventually) booted up ok....
Click to expand...
Click to collapse
Hi again all.
Success! I finally managed to crack it.
I downloaded MM Firmware version C432B136 and used Huawei Extractor to extract the Boot.img, Recovery.img and System.img files and was able to boot into Fastboot mode fortunately. I used a Command Prompt to unlock the Bootloader again and flashed each .img file in line.
The phone booted up into the B136 firmware and I was then able to update OTA to B166, but not B182 strangely. So I downloaded a B182 version firmware and placed it in the 'dload' folder of the phone's S.D Card, before forcibly flashing it by holding volume up, volume down and the power button on boot up.
I subsequently used the below link, which showed me how to use Huawei Updater and HiSuite to update to B361 firmware.
https://forum.xda-developers.com/showpost.php?p=70594380&postcount=2
Once on Nougat B361 firmware, my phone's update setting prompted me to update to the latest B378 firmware OTA.
Finally, to achieve Root status I followed the below guide and am now running root with SuperUser and BusyBox installed. I'm happy to report that both Nougat 7.0 and HMUI 5.0 are running smoothly on my phone and all features are working (i.e. Bluetooth, Camera and NFC) and performance and battery life are all noticeably better than ever.
https://forum.xda-developers.com/showpost.php?p=70927601&postcount=456
Be aware that my phone is EVA-L09, so I followed all guides and downloaded all firmware that related to my specific phone model.
Phew! Thanks for all of your help and good luck to those who are attempting to get this working.
Bill.
I have a SIM free UK P9. Early on in its life it received updates happily but I have still not received Nougat and I'm still on the September 2016 Security Patch from Google. I've never rooted or tampered with the device, so where are my updates? Are Huawei simply too busy with other phones to bother updating flagships from only last year?
It is unacceptable to me that a £450 device from a manufacturer purportedly looking to compete with the big guns in the premium phone space cannot be bothered to keep its older handsets up to date. How is a user supposed to put his trust in a company when they seem to forget about their older devices once newer ones are released onto the market?
Meanwhile a friend of mine with a SIM free Samsung Galaxy Note 4 (!) has June's security patches.
Small wonder people don't take Huawei seriously. This P9 is a lovely device with great battery life and is still (for my usage) an excellent handset; however I will not be buying another Huawei until I am confident that they are willing to maintain support for older devices. So far it seems that some people in different parts of the world on various carriers *do* get updates (or at least have more recent ones) but Huawei seem incapable of rolling them out consistently and across the board.
Disappointing.
Anyone else have any thoughts on this? I don't wish to put Huawei down too much as I think they bring some interesting things to the market but one of my biggest bugbears is where manufacturers forget that after-sales support and updates are some of the things that contribute to people's perception of a company. Might as well just buy Doogees and Vernees off Banggood without it.
Don't wait huawei to send update,use firmware finder from play store,or dload method,or hisuite method,all these methods are officially safe and keep your warranty. What your build number ?
Build number is EVA-L09C432B182.
I'm not really into flashing ROMs these days as i don't want to mess anything up. I don't want to flash firmware that isn't UK SIM free either, and if I haven't had that update OTA then I assume it simply hasn't been released.
I don't have a PC anyway as I sold my Surface Pro and now only have a MacBook.
Use firmware finder from play store,and firmware finder proxy,it is the easy way,only search for the rom u want and let your system update search for update by using proxy,if from MM to nougat u will not loose anything.
You'd have to guide me through that step by step as to be honest I don't entirely understand anything other than the bit about using something from the Play Store
OK so I worked this out. The only firmware it says is approved for my device is the next up on the list - EVAL09C432B330-LOG.
This downloads fine through the stock Huawei update menu (as if i am just doing a normal update) and the phone reboots but then the installation fails, whether I choose the full package or standard update option.
leoni1980 said:
OK so I worked this out. The only firmware it says is approved for my device is the next up on the list - EVAL09C432B330-LOG.
This downloads fine through the stock Huawei update menu (as if i am just doing a normal update) and the phone reboots but then the installation fails, whether I choose the full package or standard update option.
Click to expand...
Click to collapse
do you have a way to get the files from firmware finder onto your SD card? If so create a folder called DLOAD on the root directory and then put the update file in that folder. Power off the phone and hold all three buttons (power and vol+/-) until you get the firmware updating screen.
Let me know if it still fails.
Thanks. Will doing this cause any mismatches in future and stop me being able to receive OTA updates, or affect Android Pay?
I have put the update.zip in a folder called dload in the root of the SD but neither the boot method of installation nor the dialler method seems to find it. I've tried with a different update.zip with the same result
leoni1980 said:
I have put the update.zip in a folder called dload in the root of the SD but neither the boot method of installation nor the dialler method seems to find it. I've tried with a different update.zip with the same result
Click to expand...
Click to collapse
Who told u that??, incorrect my friend,extract the update.zip and put only update.app inside dlod folder in the root of your sd card,it is explain hunderds of time everywhere
Hi, this isn't all that clear in the other instructions I've read, and historically flashing update.zip from the root of an SD card is quite a typical way to flash software, so you can understand the confusion!
Are you sure this will work? Other threads online indicate that flashing is much more difficult than this and requires unlocking the bootloader. Am I missing something here?
I also tried this but failed on my phone. I put the update.app in the dload folder but always fails after about 14%
leoni1980 said:
Hi, this isn't all that clear in the other instructions I've read, and historically flashing update.zip from the root of an SD card is quite a typical way to flash software, so you can understand the confusion!
Are you sure this will work? Other threads online indicate that flashing is much more difficult than this and requires unlocking the bootloader. Am I missing something here?
Click to expand...
Click to collapse
after you download the zip file and then unzip it. Put thr UPDATE.APP in the dload folder on your internal memory. and then perform the update.
sprouts4all said:
I also tried this but failed on my phone. I put the update.app in the dload folder but always fails after about 14%
Click to expand...
Click to collapse
try redownloading the file.
sprouts4all said:
I also tried this but failed on my phone. I put the update.app in the dload folder but always fails after about 14%
Click to expand...
Click to collapse
Just to let you know, after downloading a bazillion files and trying every method under the sun I finally got this to work. It is now running B386 firmware.
Using the manual update method didn't work for me; the steps I had to follow are as follows:
With Firmware Finder, choose the B386 full OTA package - check for compatibility first (it said mine was compatible with it) and choose to install via proxy. Set up your WiFi to run the localhost/8080 proxy settings as instructed by FF. While the file is downloading, remove the proxy settings from your WiFi, allow it to reconnect and continue the download.
I then just left the phone to its own thing. I was actually watching a video in the background when it rebooted itself and began the installation process, which didn't fail as I expected it to.
Everything seems to be running fine now.
Thanks to the person in this thread who suggested using Firmware Finder.
leoni1980 said:
Just to let you know, after downloading a bazillion files and trying every method under the sun I finally got this to work. It is now running B386 firmware.
Using the manual update method didn't work for me; the steps I had to follow are as follows:
With Firmware Finder, choose the B386 full OTA package - check for compatibility first (it said mine was compatible with it) and choose to install via proxy. Set up your WiFi to run the localhost/8080 proxy settings as instructed by FF. While the file is downloading, remove the proxy settings from your WiFi, allow it to reconnect and continue the download.
I then just left the phone to its own thing. I was actually watching a video in the background when it rebooted itself and began the installation process, which didn't fail as I expected it to.
Everything seems to be running fine now.
Thanks to the person in this thread who suggested using Firmware Finder.
Click to expand...
Click to collapse
What firmware was you on before. I have tried this method with other versions but no luck. I will try with the B386.
sprouts4all said:
What firmware was you on before. I have tried this method with other versions but no luck. I will try with the B386.
Click to expand...
Click to collapse
I was on B182. If you're on the exact same firmware as me then try the steps above exactly and you might have more luck. I also deleted all old downloaded update files before I commenced with it.
Thanks
leoni1980 said:
I was on B182. If you're on the exact same firmware as me then try the steps above exactly and you might have more luck. I also deleted all old downloaded update files before I commenced with it.
Thanks
Click to expand...
Click to collapse
Still didnt work, went to install but failed. Says incompatible firmware
Follow these like i just did
https://forum.xda-developers.com/showpost.php?p=70594380&postcount=2)
mazsuper said:
Follow these like i just did
https://forum.xda-developers.com/showpost.php?p=70594380&postcount=2)
Click to expand...
Click to collapse
Didn't work, managed to get to B360 but now Huawei apps are missing including camera
goto b300 then b182 then follow above instructions , and rtfm
skip 361 and goto 378 via hisuite update
Hi !
I have a NEM-L51C432. I recently installed the new update available (B357) using Huawei Firmware Finder.
Due to some issues, I then decided to rollback to a previous build using the dload method. I succeeded, although I can't recall if the one which worked was B350 or B355.
The problem is, my build is still B357 in the "About phone" menu even though I have the March security patch.
I also noticed that the clock app is missing. Moreover, I get a notification telling me that apps are non-compatible with my phone when I install/update them, even though they work fine.
I can't update system apps (like Chrome or WebView for instance) due to different signature.
I have no idea if these things are related.
So, can someone please tell me how can I get my phone to display the correct build number and eventually correct the other issues in the process ? I'm ready to wipe and re-flash if I have to.
Side question, when I download from HFF in order to use the dload method, most of the time I have the choice between one, two, or even three zips to download.
Each contain a UPDATE.APP file, but I don't get the same files when I extract from it, depending on the zip I downloaded.
Can someone explain me this as well as which file I should prefer (update.zip or one of the other two if available) ?
Thank you.
You need to flash all 3 files via dload.
There is a detailed quide in my signature for dload method. You can flash b350/355/357 or above using that.
shashank1320 said:
You need to flash all 3 files via dload.
There is a detailed quide in my signature for dload method. You can flash b350/355/357 or above using that.
Click to expand...
Click to collapse
Thank you for your answer.
Do you mean I need the three zips from HFF ? For instance, if I try to download B355, I have the choice between these :
http://update.hicloud.com:8180/TDS/data/files/p3/s15/G1581/g104/v84990/f1/full/update.zip
http://update.hicloud.com:8180/TDS/...90/f1/full/public/update_data_full_public.zip
http://update.hicloud.com:8180/TDS/...l/NEM-L51_hw_eu/update_full_NEM-L51_hw_eu.zip
They all have a UPDATE.APP within them, but they don't have the same files when I extract. What should I do ?
Zarou said:
Thank you for your answer.
Do you mean I need the three zips from HFF ? For instance, if I try to download B355, I have the choice between these :
http://update.hicloud.com:8180/TDS/data/files/p3/s15/G1581/g104/v84990/f1/full/update.zip
http://update.hicloud.com:8180/TDS/...l/NEM-L51_hw_eu/update_full_NEM-L51_hw_eu.zip
They all have a UPDATE.APP within them, but they don't have the same files when I extract. What should I do ?
Click to expand...
Click to collapse
Let me check the files on PC. Will guide you further
shashank1320 said:
Let me check the files on PC. Will guide you further
Click to expand...
Click to collapse
Okay, thanks.
Today I tried re-flashing the update.zip file of all versions via dload, even MM versions. In the end, the only one which worked was the FullOTA-MF-PV of NEM-L51C432B350. All other versions failed to install at 5 %.
I don't know if this is related, but this is the only update which is available as "PV", whatever that means.
In any case, as I said in my first post, my build number is still B357 (while it should be 350) and I don't have the Huawei clock app. Some system apps are impossible to update as well. Plus, this will probably cause issue with future updates...
Zarou said:
Okay, thanks.
Today I tried re-flashing the update.zip file of all versions via dload, even MM versions. In the end, the only one which worked was the FullOTA-MF-PV of NEM-L51C432B350. All other versions failed to install at 5 %.
I don't know if this is related, but this is the only update which is available as "PV", whatever that means.
In any case, as I said in my first post, my build number is still B357 (while it should be 350) and I don't have the Huawei clock app. Some system apps are impossible to update as well. Plus, this will probably cause issue with future updates...
Click to expand...
Click to collapse
Pv is something you can flash via twrp. Regarding misssing apps, flash the smaller file, around 600-800 MB, via twrp and it will restore apps, themes, fm radio etc.
shashank1320 said:
Pv is something you can flash via twrp. Regarding misssing apps, flash the smaller file, around 600-800 MB, via twrp and it will restore apps, themes, fm radio etc.
Click to expand...
Click to collapse
Can't flash the update.zip with TWRP (at least, with OldDroid's). However, I did managed to get back missing apps by flashing the second zip file, thank you about that.
Doesn't work with the third one though, and my build number is still wrong. Any idea about how to fix this ?
Zarou said:
Can't flash the update.zip with TWRP (at least, with OldDroid's). However, I did managed to get back missing apps by flashing the second zip file, thank you about that.
Doesn't work with the third one though, and my build number is still wrong. Any idea about how to fix this ?
Click to expand...
Click to collapse
Which build number you flash and which is the one showing?
yes, only 2nd file will work and bring back the missing apps.
shashank1320 said:
Which build number you flash and which is the one showing?
yes, only 2nd file will work and bring back the missing apps.
Click to expand...
Click to collapse
In the end, I solved the issue by extracting the VERSION.img file from the UPDATE.APP of the third zip and flashing it with TWRP.
I then updated to B355 and B357 with HFF proxy.
Weird thing is, the B357 update re-locked my bootloader and when I unlocked it again, I was stuck with an old version of Google Play Services which couldn't be updated (different signature issue). Luckily, I had a backup from the previous update but this is weird.
Thanks for your help. You've done a lot.
Hi,
Sorry of this is a bit of a newbie question but:
What is the purpose of each of the 3 different update zip files ?
And do I have to apply them all - and in what order ?
In my case, I am about to update to B389, and I have downloaded 3 files for VIE-L29C636B389 (currently on VIE-L29C636B130), and I have an update.zip, an update_full_VIE-L29_hw_spcseas.zip and an update_data_full_public.zip.
I was planning on doing the first two by the dload method (with reboots in between), but the update_data_full_public.zip doesn't appear to have an update.app, so how do I load that ? (I do have TWRP on my phone, so could probably figure it out - eventually).
Cheers,
SZ
same question
I read somewhere that it should be flashed in that exact order. i'm guessing that is the same procedure as with auto OTA updates, except now we have rooted phones, so bye-bye to auto updates. I am currently on VIE-L29CB636B387 and i received an automatic Huawei notification of a new version (VIE-L29CB636B388) about a week ago. I tried to update to that version in System Update-Quick Update, but that didn't work (surprise!). There was no issue though as when I rebooted it just went back to 387. However, I now have a red "New Version" notification in my System Update. Please tell me how your upgrade went if you went ahead and flashed 389. I have the three files already from filefinder, i also have TWRP and/or I could use adb fastboot to install. Thanks in advance.
Hey,
I am not sure I want to proceed on the basis of something that somebody 'read somewhere' ....
Anyhow - I've not run these updates yet, as I wanted to backup my phone first, but TWRP keeps blowing up with an error in the middle of the backup, so I am not going to try anything until I get to the bottom of that.
Will let you know if/when I ever go ahead!
Cheers,
SZ
Hi,
TWRP blowing up during NAND backups? thats not a good thing. Upon the advice of a forum member (xzanium) I flashed TWRP 3.1.1-1 instead of TWRP-3.2.1-0-vienna. No hitches so far, solid backups and no hiccups in flashing SuperSU, also got xposed to work seamlessly and other stuff. I hope you are able to resolve the issue you mentioned and get around to getting VIE-L29CB636B389 on your phone.
Well good luck to you, and post here any progress if you would.
SZ,
I have an idea on what the purpose of each of the 3 different update zip files are for and whether you have to apply them all - and in what order.
Since I could make a NAND backup using TWRP without issues, and there was an OTA update notice for an upgrade to VIE-L29CB636B388 which I couldn't upgrade to while rooted, I decided to unroot in order to upgrade to that. First i did the requisite steps - uninstalled the xposed framework and proceeded with the full unroot with SuperSU. Then I performed the dload method to flash the update.app that I extracted from the update.zip.
It was here where i hit a snag. What followed was, I found out that Huawei needs a verified stock rom, meaning it has to be a fullOTA-MF-PV in order that the bootloader could be relocked. So I tried my luck and downloaded the stock ROM VIE-L29C636B370 and flashed that. Success! From there, and several auto upgrades later I was back to L29C636B370. Reinstalling my Google account also locked back FRP. At this point i am full stock EMUI 5
Now, to answer your question. When I tried to upgrade to VIE-L29C636B388 via system update quick update. I only saw one file - update.zip therefore this must the only one needed for incremental patches. The same holds true with update_data_full_public.zip as I later learned when I decided to use the proxy upgrade method in MT filefinder . It applied a 2nd patch. The third file, namely, update_full_VIE-L29_hw_spcseas.zip was not required for this incremental update. In fact, the update process was cut short and an error message appeared that the file could not be located, even though i copied that to the HwOUC folder. It appears that this was deleted before the fullOTA update could finish during the incremental update process. Clearly, this last zip is not necessary for incremental updates. So this must be the package which delivers the rest of the ROM, or the parts of it that needs to be changed.
So, obviously what "I read somewhere" was legit. I hope that answers your question.
cheers!
mm
Hello everyone.
Last night i am tried to update my EMUI 5.0.2 Pra-lx1 p8 lite 2017 phone to the Oreo update 8.0.0.322 downloaded from Team TMs' huawei firmware finder.
My phone is allready "Bootloader unlocked" and "FRP unlocked" there is no problem. I can reach to TWRP( there is a huge problem i will explain it).
on the top of my way i got EMUI 5.0.2 and i unlocked the bootloader and FRP.
then i installed the EliteTWRP-3.2.1.
after this i downloaded
HuRUpdater 0_3.zip
and the 3 neccesery FullOTA-MV-OP files that includes the
update.zip
update_data_full_public.zip
update_full_PRA-L11_hw_eu.zip
then i do everything exatly on this thread
https://forum.xda-developers.com/honor-9/development/tool-flash-official-firmware-recovery-t3769279
and voilla!!! i got the Oreo update installed.
BUT....
i dont get the file manager app its lost!
i can not get themes or get in any of huawei apps sign in or get in!
so for this. my next step is goint to do reflash the oreo how i did it again.
BUT....
i can not do this because the instaled TWRP does NOT support OREO. Applause for this
so i'am tried 3 different TWRP that can be used on HUAWEI phones.
First one is this i dont know who is the developer but ists intercafe is chinese or korean.
https://drive.google.com/file/d/1rlQPRP234PoXY_yqup3oK_joOZGSIker/view
i tried to instal this over adb fastboot. BUT I can NOT. Because Oreo will do this on RAMDISK_RECOVERY!!!! WOOOWWWW
i did this and i reinstaled the oreo update like i did it first but in this new TWRP.
İt flashed my OREO but on the bootlogo the HUAWEI opening sound curropted before finished the sound and gets to restart.
after restart eRecovery opens and give me TWO funcional choises!!! Like Jig SAW
anyway...
the first option is DOWNLOAD LATEST VERSION AND RECOVERY
BUT for my chanse!!!! or mean bad LUCK!!! eRecovery WiFi doesnt see the EDUROAMs ACCESS POINTS WELL RIGHT!!!!
so i passed the first one and we are on the MAGICAL point.
the second option is the WIPE DATA/FACTORY RESET
on this time i CAN NOT DO THIS BECAUSE THE ORGININAL RECOVERY PART IS GONE!!!! YEAP I CAN NOT DO FACTORY RESET.
WHEN i choose this option it will go to the TWRP recovery nice huh!? NO.
so what will i do i know my phone is not BRICKED YET! İF THERE İS TWRP THERE İS HOPE!
BUT I DO NOT KNOW WHAT SHOULD I DO RIGHT KNOW
please help me....
with this Recovery (TWRP)( not usefull beacuse you can not use them )
https://forum.xda-developers.com/p8lite/p8-lite-2017-development/recovery-recoveryoreonocheck-install-t3777974
i found this under a members signature and i give a try but it wont work this gives me just a big error
But this error gets my phone a factory reset after than i flashed this Recovery (better then the chinesee korean languges type one ;D )
https://forum.xda-developers.com/p8lite/p8-lite-2017-development/unofficial-twrp-3-2-1-0-oreo-t3773970
and i tried to flash the Oreo update again with HuRUpdater_0_3.zip
but now I am at the begining. System works there is no issue over hardware.
But there is missing system apps like File Manager. Themes and so on....
And the best thing is The BUILD NUMBER is 8.0.0.046(08TO)
BUT I flashed the f*ckn' 8.0.0.322!!!!! WHY GOD!!!! WHY!!!!
Could anybody iluminte about what the hell is going on right now please i need to know why is why
Dude you need to rename the files before you put them in the folder
HuRUpdater 0_3.zip --> just delete the number (HuRUpdater.zip)
update_data_full_public.zip --> update_data_public.zip
update_full_PRA-L11_hw_eu.zip --> update_all_hw.zip
marstonpear said:
Dude you need to rename the files before you put them in the folder
HuRUpdater 0_3.zip --> just delete the number (HuRUpdater.zip)
update_data_full_public.zip --> update_data_public.zip
update_full_PRA-L11_hw_eu.zip --> update_all_hw.zip
Click to expand...
Click to collapse
thanks for your response. but i mention it i did it everything right. i do not think that only delete 3 piece of character get back the File manager or themes or huawei applications .
z1rqdym said:
thanks for your response. but i mention it i did it everything right. i do not think that only delete 3 piece of character get back the File manager or themes or huawei applications .
Click to expand...
Click to collapse
It would, main issue is that HuRUpdater is made for many Huawei phones not just for prague, when you flash the HuRUpdater.zip it can only flash the update.zip because you don't need to rename it. It doesn't flash the other zips because they're not named correctly, hence the updater can't find the zips to flash.
marstonpear said:
It would, main issue is that HuRUpdater is made for many Huawei phones not just for prague, when you flash the HuRUpdater.zip it can only flash the update.zip because you don't need to rename it. It doesn't flash the other zips because they're not named correctly, hence the updater can't find the zips to flash.
Click to expand...
Click to collapse
there is a misunderstood i allready rename the 3 update files. i used two times the nocheck recovery method and works well but the issue is the same. i only dont rename the hurupdater file. i will give a try now.
Let me know if it works, if that doesn't work for you too I can't help you but I just uploaded the stock oreo erecovery to GDrive and you can download it and flash it to recovery_ramdisk partition (because you are on Oreo) then make a factory reset or go back to nougat https://drive.google.com/open?id=157C0CI5CqSEzvQRB7Yt5K1WPtYBcaO08
EDIT: I didn't read it right sorry that you can't connect to wifi. Try wiping data-cache-dalvik-system on TWRP and then flashing the HuRUpdater.zip
You may also have a bad download, I mean one of the zip files you have may be corrupted
marstonpear said:
Let me know if it works, if that doesn't work for you too I can't help you but I just uploaded the stock oreo erecovery to GDrive and you can download it and flash it to recovery_ramdisk partition (because you are on Oreo) then make a factory reset or go back to nougat https://drive.google.com/open?id=157C0CI5CqSEzvQRB7Yt5K1WPtYBcaO08
EDIT: I didn't read it right sorry that you can't connect to wifi. Try wiping data-cache-dalvik-system on TWRP and then flashing the HuRUpdater.zip
You may also have a bad download, I mean one of the zip files you have may be corrupted
Click to expand...
Click to collapse
same result i did it just you are said. it flashed oreo and it booted and works. But there is no File manager can not use themes. Build number is 8.0.0.046(08TO). I can make call connect to internet over LTE / 3G / EDGE.
is this issue are from that my phone is from another region instead from europe? İ downloaded the PRA-LX1C432B322-(8.0.0.322) from Team MT FirmwareFinder over Huawei host servers three times. even i download the stock nougat rom in the same way. I flashed the nougat but this time build number is NRD-testkeys . same issue file manager themes not appear or work.
z1rqdym said:
same result i did it just you are said. it flashed oreo and it booted and works. But there is no File manager can not use themes. Build number is 8.0.0.046(08TO). I can make call connect to internet over LTE / 3G / EDGE.
is this issue are from that my phone is from another region instead from europe? İ downloaded the PRA-LX1C432B322-(8.0.0.322) from Team MT FirmwareFinder over Huawei host servers three times. even i download the stock nougat rom in the same way. I flashed the nougat but this time build number is NRD-testkeys . same issue file manager themes not appear or work.
Click to expand...
Click to collapse
If you get that build number issue on nougat it might be about your oeminfo partition. Try flashing PRA-LX1C432 oeminfo on this thread : https://forum.xda-developers.com/8-lite/how-to/share-oeminfo-t3740734
Beware, it locks your bootloader, so unlock it after you flash the file. Then start erecovery and download the nougat firmware to get your device ready for Oreo, then flash the HuRUpdater.zip . I hope this works!
marstonpear said:
If you get that build number issue on nougat it might be about your oeminfo partition. Try flashing PRA-LX1C432 oeminfo on this thread : https://forum.xda-developers.com/8-lite/how-to/share-oeminfo-t3740734
Beware, it locks your bootloader, so unlock it after you flash the file. Then start erecovery and download the nougat firmware to get your device ready for Oreo, then flash the HuRUpdater.zip . I hope this works!
Click to expand...
Click to collapse
is this rebranding changes my device IMEI adress? if it is so my unlock code do not work?
z1rqdym said:
is this rebranding changes my device IMEI adress? if it is so my unlock code do not work?
Click to expand...
Click to collapse
I don't think it changes the IMEI. I had a pra-lx1c464(Turkey) and I rebranded it to c432 I had no issues with it. It will change your device to Dual-SIM though if you have a single SIM device, which has no effect at all. I can still use my bootloader unlock code, and I have used it many time again and again after rebranding the device. Also you're trying to install PRA-LX1C432B322 Oreo right? Your device should be branded as PRA-LX1C432 first
is it neccesery to download the nougat rom from eRecovery over wifi?
z1rqdym said:
is it neccesery to download the nougat rom from eRecovery over wifi?
Click to expand...
Click to collapse
I'm not sure but it is necessary to have it branded as PRA-LX1C432
I will give a try flash the oeminfo c432 then try to flash nougat with nocheck image.
nope nothing works... I flashed the oem info from the link that you givin here. but the oeminfo doesnt change the Build number but the device changed to honor 8 lite chinese normal version on nougat. After flashed the oreo the build number dont changed and the themes not working file manager also not excist.
Factory reset
z1rqdym said:
nope nothing works... I flashed the oem info from the link that you givin here. but the oeminfo doesnt change the Build number but the device changed to honor 8 lite chinese normal version on nougat. After flashed the oreo the build number dont changed and the themes not working file manager also not excist.
Click to expand...
Click to collapse
Have you tried to reset the phone to its factory defaults . In this way I fixed missing apps problem .
I tried factory reset over Recovery bu it doesnt changed any thing. Then i tried the factory reset from the settings of the rom. Same result.
I just installed it manually. I have the 8.0.0.46 (08TO) but I don't have any issue, I have apps and themes..is it correct the version not should I expecting something different?
Please let me know
Same build number as in my settings. Themes wont work because regional issues. When i change phones language to english themes apps works well. Thats the themes app i admit it but.. in the other hand i dont get the in games(i dont remember the original name of it) app comes with oreo. I dont have the huawei login future anymore i think this is because of the unlocked bootloader not tried to look again then do a factory reset. I can not rebrand my phone. I know because when i flash europen oeminfo or not if i install the stock emui 5.0.3 again it says no build number against test keys . On the other side i can use my phone well i dont have any problem. And i forgot to say i dont even the file manager i installed the hidisk apk that i found on internet.
My advise is dont do this to your phones wait for a official update. But for us this is a long hard road