I recently posted the B136 EVA-L09 dload file in this topic, which a number of people are using to de-brand their UK devices on operators such as Vodafone.
If you do so, you end up on C900, which is a cross-flash version, which isn't safetynet certified (no Android Pay compatibility).
The solution to unlock your bootloader (using the official method or dc-unlocker), flash TWRP, flash this zip then reflash the dload file.
You'll then be on C432B136 and safetynet friendly.
oeminfo-huawei-p9-eval09-c432.zip - DOWNLOAD - MD5: f5b757f76f99e9c50555a6616802c41e
Enjoy!
P
Be warned that debranding your device fully will cause the phone to be wiped so you'll need to backup files first.
When flashing the B136 ROM after you have updated oeminfo, make sure you copy all files and folders to your sdcard.
It should look like this on your SD:
Code:
/dload/UPDATE.APP
/dload/dt/default/update_data_dt_default.app
/dload/hw/eu/update_data_hw_eu.app
/dload/hw/normal/update_data_hw_normal.app
If you just flash the UPDATE.APP then you'll end up with a broken /cust partition with incorrect icons, theming not working, etc.
EMUI recovery will flash UPDATE.APP then flash the dt, then hw updates after.
Once booted into Android, open the dialer then dial:
Code:
* # * # 2 8 4 6 5 7 9 # * # *
then tap 3. Network Information Query, Vendor Country Info. If OEMINFO was correctly updated then this will show
Code:
Vendor: hw
Country: eu
Now open Settings > About Phone. Build should be EVA-L09C432B136
If build is showing C900B136 and vendor country info showing Vodafone, you'll need to do a factory reset.
I installed this ZIP, once this is done it reseted my phone and even my bootloader locked again as originally (it was marked locked and relocked not as original. Probably a good zip has flashed before returning to service
marmottator said:
I installed this ZIP, once this is done it reseted my phone and even my bootloader locked again as originally (it was marked locked and relocked not as original. Probably a good zip has flashed before returning to service
Click to expand...
Click to collapse
Which ROM build did you have previously and which version is being shown now?
before C900b136, after c432b136
I just used this to attempt to update my Vodafone P9 to C432B136. It didn't reset my phone (all my data are still there) and I am stuck on EVA-C900B136. Have tried flashing oeminfo and then running the update twice. Vendor Country Info says "Vendor: vodafone Country: gb"
---------- Post added at 09:09 PM ---------- Previous post was at 08:47 PM ----------
tnhh said:
I just used this to attempt to update my Vodafone P9 to C432B136. It didn't reset my phone (all my data are still there) and I am stuck on EVA-C900B136. Have tried flashing oeminfo and then running the update twice. Vendor Country Info says "Vendor: vodafone Country: gb"
Click to expand...
Click to collapse
Oh no never mind. I had selected the wrong storage in TWRP. Device is resetting now.
---------- Post added at 09:11 PM ---------- Previous post was at 09:09 PM ----------
tnhh said:
I just used this to attempt to update my Vodafone P9 to C432B136. It didn't reset my phone (all my data are still there) and I am stuck on EVA-C900B136. Have tried flashing oeminfo and then running the update twice. Vendor Country Info says "Vendor: vodafone Country: gb"
---------- Post added at 09:09 PM ---------- Previous post was at 08:47 PM ----------
Oh no never mind. I had selected the wrong storage in TWRP. Device is resetting now.
Click to expand...
Click to collapse
Sorry for all the edits! My bootloader was also relocked after (correctly!) installing this zip file.
---------- Post added at 09:21 PM ---------- Previous post was at 09:11 PM ----------
tnhh said:
I just used this to attempt to update my Vodafone P9 to C432B136. It didn't reset my phone (all my data are still there) and I am stuck on EVA-C900B136. Have tried flashing oeminfo and then running the update twice. Vendor Country Info says "Vendor: vodafone Country: gb"
---------- Post added at 09:09 PM ---------- Previous post was at 08:47 PM ----------
Oh no never mind. I had selected the wrong storage in TWRP. Device is resetting now.
---------- Post added at 09:11 PM ---------- Previous post was at 09:09 PM ----------
Sorry for all the edits! My bootloader was also relocked after (correctly!) installing this zip file.
Click to expand...
Click to collapse
Success! EVA-L09C432B136
Yes, flashing a stock rom will lock the bootloader again. This is normal. As long as you kept a copy of your unlock code then you can unlock your bootloader again.
flibblesan said:
Yes, flashing a stock rom will lock the bootloader again. This is normal. As long as you kept a copy of your unlock code then you can unlock your bootloader again.
Click to expand...
Click to collapse
Thanks. That's good to know since I had tried relocking the bootloader using fastboot and failed.
flibblesan said:
Yes, flashing a stock rom will lock the bootloader again. This is normal. As long as you kept a copy of your unlock code then you can unlock your bootloader again.
Click to expand...
Click to collapse
Are you sure? It didn't relock my bootloader! But then I was
a C432 before I flashed the stock rom if that makes a difference.
marmottator said:
I installed this ZIP, once this is done it reseted my phone and even my bootloader locked again as originally (it was marked locked and relocked not as original. Probably a good zip has flashed before returning to service
Click to expand...
Click to collapse
same problem for me
i made a reset data factory and now ask me type password to decrypt storage
help me please :crying:
scedric57 said:
same problem for me
i made a reset data factory and now ask me type password to decrypt storage
help me please :crying:
Click to expand...
Click to collapse
La seule solution dans ton cas sera de faire un gros reset, c'est ce que j'ai fait
marmottator said:
I installed this ZIP, once this is done it reseted my phone and even my bootloader locked again as originally (it was marked locked and relocked not as original. Probably a good zip has flashed before returning to service
Click to expand...
Click to collapse
marmottator said:
La seule solution dans ton cas sera de faire un gros reset, c'est ce que j'ai fait
Click to expand...
Click to collapse
i'm reflashing with the dload directory on external SD i pray now
---------- Post added at 12:16 AM ---------- Previous post was at 12:11 AM ----------
yes all it's ok now thank you @marmottator
Hi all, what's the best way of doing a backup so that data can be restored once this has been done (and therefore wiped?). I'm eager not to lose my apps data, but I thought I needed root access to backup and restore that? Thanks in advance!
Sent from my EVA-L09 using Tapatalk
dcfowler01 said:
Hi all, what's the best way of doing a backup so that data can be restored once this has been done (and therefore wiped?). I'm eager not to lose my apps data, but I thought I needed root access to backup and restore that? Thanks in advance!
Click to expand...
Click to collapse
I used Titanium Backup. I also used adb to pull the whole of /sdcard just to be on the safe side. You need to unlock the bootloader anyway to flash this zip file, so you may as well just root your device at the same time.
Sorry how do I gain root access? I suspect that's what I'm missing. Does unlocking the bootloader give you that by default?
Sent from my EVA-L09 using Tapatalk
dcfowler01 said:
Sorry how do I gain root access? I suspect that's what I'm missing. Does unlocking the bootloader give you that by default?
Click to expand...
Click to collapse
No, you need to flash SuperSU as per http://forum.xda-developers.com/p9/how-to/guide-root-huawei-p9-t3367800
Ok Thankyou! In which case I guess I also have to unlock the boot loader and root *afterwards*, so I can then restore the backup? Thanks.
Sent from my EVA-L09 using Tapatalk
dcfowler01 said:
Ok Thankyou! In which case I guess I also have to unlock the boot loader and root *afterwards*, so I can then restore the backup? Thanks.
Click to expand...
Click to collapse
Yep, that's exactly what I did.
paulobrien said:
I recently posted the B136 EVA-L09 dload file in this topic, which a number of people are using to de-brand their UK devices on operators such as Vodafone.
If you do so, you end up on C900, which is a cross-flash version, which isn't safetynet certified (no Android Pay compatibility).
The solution to unlock your bootloader (using the official method or dc-unlocker), flash TWRP, flash this zip then reflash the dload file.
You'll then be on C432B136 and safetynet friendly.
oeminfo-huawei-p9-eval09-c432.zip - DOWNLOAD - MD5: f5b757f76f99e9c50555a6616802c41e
Enjoy!
P
Click to expand...
Click to collapse
Hi guys
I have a dual sim Chinese EVA-ALOO P9 from Aliexpress. Worked out of the box fine, but with the heavy influences of Chinese in all the apps.
I've managed to unlock the Bootloader (re-lock it again when needed, install TWRP and remove it again etc)... I've tried every firmaware on the XDA threads (it just tells me its not compatible - so no firmware upgrades have been possible)
What I was able to do was apply this OEMINFO file and trick my P9 into thinking is a UK version.... although not quite. I seem to get a verification failure when trying to do a factory reset....
So am I correct in thinking, I just have to wait until the Chinese ROM is availble before I can reset everything back to the way it was, or how do I undo the OEMINFO update?
it's not a train smash if I have to wait, just being impatient as per normal
Thanks
what would happen, if I flash this OEMinfo over my EVA-AL10? same as with the AL00 or will it deny booting, because it has different hardware (4GB/64GB)?
Related
Here is the OTA Kitkat update
https://drive.google.com/file/d/0B7UQWkPdlFVDbHdQc1EzdTEyR1k/edit?usp=sharing
not work witch cwm or other custom recovery, if tried not working, need stock recovery, and stock rom us.
share it if you find the solution.
Click to expand...
Click to collapse
Note: Dont worry if dont see icon H+ when you flashes Stock Rom US, I Test Velocity, is HSPA +. You can see the screenshot int attached.
1.- For Install just flash stock rom IMPORTANT umts.Retail.en.US http://sbf.droid-developers.org/phone.php?device=14
2.- Copy the OTA KITKAT 4.4.2 to sdcard or use adb sideload
3.- Apply update from sdcard
4.- Enjoy :laugh:
Root Working method:
http://forum.xda-developers.com/showthread.php?t=2583652
Merry Christmas
Best regards Amigos
Downloading, testing on a UK XT1032
Fails to apply over UK firmware due to incorrect device id. I guess I'll need to flash 4.3 US first...
---------- Post added at 09:35 AM ---------- Previous post was at 09:18 AM ----------
nupi said:
Downloading, testing on a UK XT1032
Fails to apply over UK firmware due to incorrect device id. I guess I'll need to flash 4.3 US first...
Click to expand...
Click to collapse
Now I get mismatch between expected falcon_umts and existing xt1032. Guess I'll have to see about hacking the install script.
nupi said:
Downloading, testing on a UK XT1032
Fails to apply over UK firmware due to incorrect device id. I guess I'll need to flash 4.3 US first...
---------- Post added at 09:35 AM ---------- Previous post was at 09:18 AM ----------
Now I get mismatch between expected falcon_umts and existing xt1032. Guess I'll have to see about hacking the install script.
Click to expand...
Click to collapse
yep, you need modified script or install stock rom us
ZealotRush said:
yep, you need modified script or install stock rom us
Click to expand...
Click to collapse
Even stock US didn't seem to help.
Flashed stock US again and wiped data this time round, the device still identifies as xt1032 instead of the required falcon_umts
Playing around with the script now... Actually, come to think of it, would you be able to post a CWM backup of the applied OTA? that ought to be much easier
I just tried to flash this update over official US global fw (http://forum.xda-developers.com/showthread.php?t=2578997) on a fr Moto G. I got an error during the verification of the curre,t system: "not enough free space on /system to appl patches. Installation aborted."
F***...
Any idea?
-----Update-----
The first try was with the original recovery.
I just tried with cwm, it says the device is xt1032 but the package is for falcon_umts...
When attempting to flash via CWM on UK XT1032, the following is returned:
Package expects build fingerprint of motorola/falcon_retuglb/falcon_utms:4.3/14.10.0Q3.X-84-16/6:user/release-keys or motorla/falcon_retuglb/falcon_utms:4.4.2/KXB20.9-1.8-1.1/4:user/release-keys; this device has motorola/cm_xt1032:4.3.1/JLS36I/126
Click to expand...
Click to collapse
lost101 said:
When attempting to flash via CWM on UK XT1032, the following is returned:
Click to expand...
Click to collapse
Did you flash US stock firmware first? (though for me that didn't help, either)
No, UK GSM XT1032 with Stock Retail Rom. What to see if it can be forced onto non-US XT1032. Changing device name from 'falcon_retgb' to 'falcon_retuglb' using Android Model Changer makes no difference.
EDIT: Forgot to change build number.
lost101 said:
No, UK GSM XT1032 with Stock Retail Rom. What to see if it can be forced onto non-US XT1032. Changing device name from 'falcon_retgb' to 'falcon_retuglb' using Android Model Changer makes no difference.
EDIT: Forgot to change build number.
Click to expand...
Click to collapse
Since the OTA is a patch rather than a full firmware, I doubt forcing it onto another base would work (UK and US do not behave entirely the same, even after initial boot up!)...
Has anybody tried flashing this over the telus/koodo version of the moto G?
It appears the device name is stored somewhere outside of android. So to flash the US ROM is not enough. Two obvious choices: Find that location and change it, if that's even possible, or attempt to modify the install script.
You must be doing something wrong. The OTA flashes fine here onto a UK device running US Global ROM.
You must be running the US_retail_XT1032_14.10.0Q3.X-84-16_CFC.xml.zip ROM on your device with an unlocked bootloader. Ignore the errors whilst flashing the ROM. Let the phone boot up once, then turn it off. Open bootloader menu then go to recovery and open it. Now use adb sideload to push the Blur_Version.14.14.16.falcon_umts.Retail.en.US.zip OTA over to the phone and flash it. Wait for the patching to finish and you'll be on US global kitkat.
Before anyone asks.. sorry but I don't have the time to extract the system as it's Christmas and I have family stuff to deal with.
1. I am not a "noob" I am flashing roms, kernel and recovery since the begining of Android.
2. I have done exactly what you said:
I followed the other thread, i am in US_retail_XT1032_14.10.0Q3.X-84-16_CFC (i verified it in settings)
I tried to flash the file by sideload, by copy and flash from the original recovery and cwm and it does not work!
SouSoulebarbu said:
1. I am not a "noob" I am flashing roms, kernel and recovery since the begining of Android.
2. I have done exactly what you said:
I followed the other thread, i am in US_retail_XT1032_14.10.0Q3.X-84-16_CFC (i verified it in settings)
I tried to flash the file by sideload, by copy and flash from the original recovery and cwm and it does not work!
Click to expand...
Click to collapse
Agreed and even removing the falcon_umts check in the install script does nothing, the update never actually proceeds on my device.
SouSoulebarbu said:
1. I am not a "noob" I am flashing roms, kernel and recovery since the begining of Android.
2. I have done exactly what you said:
I followed the other thread, i am in US_retail_XT1032_14.10.0Q3.X-84-16_CFC (i verified it in settings)
I tried to flash the file by sideload, by copy and flash from the original recovery and cwm and it does not work!
Click to expand...
Click to collapse
All the update checks for is the correct build fingerprint in build.prop so I don't quite understand why you are having problems. You do have an XT1032 device right?
Excellent!!! Installed without problems
Enviado desde mi XT1032 mediante Tapatalk
m_loaiza said:
Excellent!!! Installed without problems
Enviado desde mi XT1032 mediante Tapatalk
Click to expand...
Click to collapse
From which software versión did you come from?
newdeal99 said:
Has anybody tried flashing this over the telus/koodo version of the moto G?
Click to expand...
Click to collapse
Yes I have this phone and have flashed the US Global. All works but you will lose HSPA+ and only get 3G!
psychodogg said:
Yes I have this phone and have flashed the US Global. All works but you will lose HSPA+ and only get 3G!
Click to expand...
Click to collapse
You still get HSPA. It's just shown as '3G' on US devices rather that 'H'.
---------- Post added at 05:57 PM ---------- Previous post was at 05:32 PM ----------
Gone back to the UK ROM myself. Keep losing cell signal with the US global ROM which is weird as I thought the US Global was supposed to be pretty much the same as the European global?.. I'm on EE.
flibblesan said:
You still get HSPA. It's just shown as '3G' on US devices rather that 'H'.
---------- Post added at 05:57 PM ---------- Previous post was at 05:32 PM ----------
Gone back to the UK ROM myself. Keep losing cell signal with the US global ROM which is weird as I thought the US Global was supposed to be pretty much the same as the European global?.. I'm on EE.
Click to expand...
Click to collapse
i test velocity dont worry for an icon, is nesesary an stock rom us and recovery for the moment.
WARNING: THIS HAS BRICKED PHONES! It is suspected that having an encrypted phone causes these bricks, but that has not been confirmed. If your data partition is encrypted, it is extra important that you perform a factory reset before taking this OTA. Doing this will remove the encryption.
WARNING: INSTALLING THIS ON A LOCKED BOOTLOADER WILL ELIMINATE ALL CHANCE OF YOU EVER UNLOCKING YOUR BOOTLOADER.
If your bootloader is unlocked, it will not be re-locked after this update.
Do NOT flash this using TWRP. If you want to do that, use this version: http://forum.xda-developers.com/droid-turbo/development/rom-mcg24-251-5-100-stock-t3512949
So if you're a bad enough dude to flash this anyway, follow these instructions:
1. Backup all data on your phone. It will be lost.
2. If your bootloader is locked, make sure you are on SU4TL-49. If you aren't, take all available OTAs until you are.
3. If your bootloader is unlocked and you have TWRP installed, flash SU4TL-49 using this package: https://mega.nz/#!3xRhiaSR!KxH2Ya_BYK4zBjrxmej7dqaaDJVT1coTFJVJ5Fvb2WM
4. If you have TWRP installed on your phone, download the stock SU4TL-49 recovery here: https://mega.nz/#!L1AkQD4T!qoZIlLa-wuUBLMEi_gE574meiHd6Pehb34a-x3Gb-V8 and install it using the install image option in the install menu in TWRP. Reboot to recovery.
3. Perform a factory reset using the stock recovery menu. This will wipe all data and ensure that everything is formatted exactly as it should be.
4. Boot the phone normally and place the marshmallow update on the root of the directory that pops up when you plug in your phone.
5. Boot to recovery and at the stock recovery menu, select "apply update from sdcard."
6. Select the update and cross your fingers.
Get the update here: https://mega.nz/#!v0pRwThS!Pz9xuOSPjiOMtjlORkFrZ_ok0GTKqCfGzi5KmbDpHQ8
TheSt33v said:
WARNING: THIS HAS BRICKED PHONES! Do not use this unless you know what you're doing.
I will do my best to provide more detailed instructions later today. Good luck.
https://mega.nz/#!v0pRwThS!Pz9xuOSPjiOMtjlORkFrZ_ok0GTKqCfGzi5KmbDpHQ8
Click to expand...
Click to collapse
Are you sure that that file is the right one? It has the same version number as su4tl-49.
zys52712 said:
Are you sure that that file is the right one? It has the same version number as su4tl-49.
Click to expand...
Click to collapse
I'm positive. I seem to remember they did the same thing with SU4TL-49. The OTA was named after SU4TL-44 for some reason.
This is the stock recovery version, correct?
koftheworld said:
This is the stock recovery version, correct?
Click to expand...
Click to collapse
Correct. You install this using the sideload option in the stock recovery.
TheSt33v said:
Correct. You install this using the sideload option in the stock recovery.
Click to expand...
Click to collapse
Thanks for the info and the download! You finally brought the wall down. I'm waiting for the twrp version myself
.
Thank you, now we can see what can be done with the new modem, kernel, etc...
Looking forward to a plethora of improvements to our phones
koftheworld said:
Thanks for the info and the download! You finally brought the wall down. I'm waiting for the twrp version myself
.
Click to expand...
Click to collapse
I'm testing the TWRP version now. It should be up shortly.
EDIT: I flashed it and it seems to work fine. Uploading now. Should be up in a few hours. I'll check on it after I go run some errands real quick.
Despite having software status report official, not modified, I too got a status 7 error. Downloading again.
---------- Post added at 09:52 PM ---------- Previous post was at 09:51 PM ----------
zys52712 said:
Are you sure that that file is the right one? It has the same version number as su4tl-49.
Click to expand...
Click to collapse
This used to always be Motorola's naming scheme. New updates were named after the firmware version they replaced.
Sweet. I am going to wait till it is more stable. I do have a bad esn Turbo but I will need to unlock to bootloader to test.
Mirror for people having "quota exceeded" error at Mega
https://yadi.sk/d/AhmhE-yX32E84p
Rename to Blur_Version.24.81.5.quark_verizon.verizon.en.US.zip before use, throw in internal storage, and check for updates.
PS: I have 64Gb Employee Edition, and still had not receive update by air. What a shame, VZ! )
kitcostantino said:
Despite having software status report official, not modified, I too got a status 7 error. Downloading again.
---------- Post added at 09:52 PM ---------- Previous post was at 09:51 PM ----------
This used to always be Motorola's naming scheme. New updates were named after the firmware version they replaced.
Click to expand...
Click to collapse
Error 7? Are you trying to flash this in TWRP? Because you can't do that with this package. You need the stock recovery. I'm uploading a TWRP-friendly version now, but the internet is being slow today.
TheSt33v said:
Error 7? Are you trying to flash this in TWRP? Because you can't do that with this package. You need the stock recovery. I'm uploading a TWRP-friendly version now, but the internet is being slow today.
Click to expand...
Click to collapse
Negative. Stock recovery on a system that reports "Official". I'm at a loss.
kitcostantino said:
Negative. Stock recovery on a system that reports "Official". I'm at a loss.
Click to expand...
Click to collapse
Strange. Try reflashing SU4TL-49. If my TWRP package doesn't do it for you, use the full firmware package and do it manually with fastboot.
Installed successfully on two devices.
...
kitcostantino, did you refresh system, kernel, modem and recovery by SU4TL-49? Are you sure you didn't mess with Turbo Maxx ROMs in the past? Foreign bootloader can cause even brick, not just error. See bootloader status at fastboot mode should be " locked, status 0"
s5610 said:
Installed successfully on two devices.
...
kitcostantino, did you refresh system, kernel, modem and recovery by SU4TL-49? Are you sure you didn't mess with Turbo Maxx ROMs in the past? Foreign bootloader can cause even brick, not just error. See bootloader status at fastboot mode should be " locked, status 0"
Click to expand...
Click to collapse
lol. lawd, No. Ive been rocking status 3 for over a year.
As a tip, if anyone else with an unlocked bootloader runs into this,
what i had to do was restore my su-44 unmodified backup, OTA to SU-49, and then, after confirming my
q/e status was 0/1 i was able to update via the file in my Mega download folder. all is well now. they even added the newer version of command center. sweet. thank you all!!
It works in LOCKED BOOTLOADER??? .-.
square1230 said:
It works in LOCKED BOOTLOADER??? .-.
Click to expand...
Click to collapse
Um, I couldn't tell you.i be been unlocked since the day Sunshine could unlocked our bootloader's. What I can tell you is you should absolutely unlock that via Sunshine before you even dream of applying this update. There will never be another opportunity.
Just my
.02. This is likely the last update for this phone, and your only chance of seeing N is via custom Roms.
TWRP version up now: http://forum.xda-developers.com/droid-turbo/development/rom-mcg24-251-5-100-stock-t3512949
square1230 said:
It works in LOCKED BOOTLOADER??? .-.
Click to expand...
Click to collapse
Yes it should. See instructions in OP.
Hi,
you want to flash EMUI 9 Beta, are FRP and bootloader unlocked and rooted? Great, here we go.
Disclaimer: I am not responsible for your bricked devices. I only tested this on my Windows 10 x64 computer with my CLT-L09 C432 - I don't know if this works with your phone or your computer. Other models may or may not work. Please don't use that method if you don't know how to recover your phone from a bricked or semi-bricked state.
It might be a good idea to disable your antivirus if you run into warnings. There is no root.
Steps:
- Download THE TOOL™ v0.2
- Download the matching firmware bundle for your device. With EMUI 9 the firmware files for L09 and L29 differ.
- Extract THE TOOL™
- Extract the firmware bundle, you'll get two ZIPs and some XMLs.
- Start FLASH.bat inside of the extracted tool folder - it will guide you through the procedure.
- I did not have to factory reset. Maybe you will still need to.
- I have no idea if you will be able to receive OTAs or upgrade to future builds.
Disclaimer: Its not my fault or my responsibility if you brick your phone. I have almost no spare time at the moment, so I will probably not be able to help you. Also, there is no root.
Download:
CLT-L09 C432 - Build 9.0.0.108
CLT-L29 C432 - Build 9.0.0.108
Upgrade / Downgrade:
Upgrade from Beta to Beta: CLICK HERE (thanks @side_flip15)
Downgrade back to Oreo: CLICK HERE (thanks @Androlark)
Massive thanks to:
- @Atarii
- @Androlark
- @ante0
- @dkionline
- @frantorresm5434
- laststandingdroid
- @mankindtw for the original NoCheck recovery
- @Pretoriano80
- @shimp208 for the bundled minimal ADB + Fastboot
- and of course to all the brave testers!
There is no root. Also, please don't blame if your device dies. And I don't know if VoLTE works.
Click HERE for the P20 (EML) thread.
02.10.2017 - v0.2 - updated download links from 9.0.0.47 to 9.0.0.108; added links to downgrade and upgrade instructions
07.09.2017 - v0.2 - script now should work inside path containing spaces
06.09.2018 - v0.1 - initial release
windows only :-/. Luckily seems easy enough
---------- Post added at 11:48 PM ---------- Previous post was at 11:40 PM ----------
Thanks. Does this update the bootloader? Can you downgrade again?
josdehaes said:
windows only :-/. Luckily seems easy enough
---------- Post added at 11:48 PM ---------- Previous post was at 11:40 PM ----------
Thanks. Does this update the bootloader? Can you downgrade again?
Click to expand...
Click to collapse
Yes, the bootloader (xloader) will be updated, there's no way around it. Yes, downgrading works, but you will have to factory reset after downgrading.
Having a problem after renaming the second update zip. After I press enter with both zip files in the zip folder it says I'm missing zip files.
---------- Post added at 02:18 AM ---------- Previous post was at 02:16 AM ----------
CaseyS said:
Having a problem after renaming the second update zip. After I press enter with both zip files in the zip folder it says I'm missing zip files.
Click to expand...
Click to collapse
Solved
Nice thanks man
Pretoriano80 said:
Yes, the bootloader (xloader) will be updated, there's no way around it. Yes, downgrading works, but you will have to factory reset after downgrading.
Click to expand...
Click to collapse
If ever I want to go back to 8.1 which method should I use? Will HuRu or eRecovery work?
Worked great.
Should add in op that tool folder needs to be in c drive directory else you will get a ton of replies about missing zips.
side_flip15 said:
If ever I want to go back to 8.1 which method should I use? Will HuRu or eRecovery work?
Click to expand...
Click to collapse
NoCheck works. (from BKL/Honor View 10)
side_flip15 said:
If ever I want to go back to 8.1 which method should I use? Will HuRu or eRecovery work?
Click to expand...
Click to collapse
No - as @ante0 said in his comment: You'll need the NoCheck recovery. I'm probably going to make a rollback bundle, too - but since I'm moving this is going to take at least until Sunday.
JamieD81 said:
Worked great.
Should add in op that tool folder needs to be in c drive directory else you will get a ton of replies about missing zips.
Click to expand...
Click to collapse
Thank you. It should be fixed inside the updated link in OP.
Anybody can upload any file server?megaupload have limited..
ekremxx said:
Anybody can upload any file server?megaupload have limited..
Click to expand...
Click to collapse
Use MEGASync desktop app
---------- Post added at 11:00 AM ---------- Previous post was at 10:58 AM ----------
Possible to flash this on region other than 432???
side_flip15 said:
Use MEGASync desktop app
---------- Post added at 11:00 AM ---------- Previous post was at 10:58 AM ----------
Possible to flash this on region other than 432???
Click to expand...
Click to collapse
/cust contain all different cust (like eu, meafnaf, us etc) so it should be possible.
Seeing this post https://forum.xda-developers.com/showpost.php?p=77551305&postcount=6 it has been done partially already (L09 on L29)
And as Oreo TWRP is pretty functional it is easily re-flashed.
ekremxx said:
Anybody can upload any file server?megaupload have limited..
Click to expand...
Click to collapse
I updated the links in OP.
What about magisk anybody know how to root?
without root. Pie is not worth.
david6910 said:
What about magisk anybody know how to root?
Click to expand...
Click to collapse
As it is stated in the OP (three times ) there is currently no known rooting method.
otonieru said:
without root. Pie is not worth.
Click to expand...
Click to collapse
ok
david6910 said:
What about magisk anybody know how to root?
Click to expand...
Click to collapse
otonieru said:
without root. Pie is not worth.
Click to expand...
Click to collapse
There is no way to flash Magisk, yet anyway.
But I'm not certain TopJohnWu will be working on fixing it after he found out Patch01 broke Magisk (Which apparently has been fixed by @Tecalote)
Hi, I created a shell script for usage on Linux/MacOS. Should run if bash is available.
!! Note that you need to have adb/fastboot already in your $PATH and working!!
enjoy.
Tried like many others to flash RROS, but once booted it does not do anything, just a black screen. Tried using the dload method but it fails right away (i used Full-OTA same build as i had before trying to install RROS). I have Bootloader and FRP unlocked, Fastboot mentions AP_S_ABNORMAL. I can also enter TWRP, but i just cannot boot or reflash anything... Do i have to use B131 for the dload method ? Or is there anything else ?
EDIT : Resolved, see last post.
Hello. Do u know Funky Huawei? It's your friend! But, you have to pay unfortunately.
stuckoutside said:
Tried like many others to flash RROS, but once booted it does not do anything, just a black screen. Tried using the dload method but it fails right away (i used Full-OTA same build as i had before trying to install RROS). I have Bootloader and FRP unlocked, Fastboot mentions AP_S_ABNORMAL. I can also enter TWRP, but i just cannot boot or reflash anything... Do i have to use B131 for the dload method ? Or is there anything else ?
Click to expand...
Click to collapse
Envoyé de mon COL-L29 en utilisant Tapatalk Pro
nico97470 said:
Hello. Do u know Funky Huawei? It's your friend! But, you have to pay unfortunately.
Click to expand...
Click to collapse
Any way to do it for free ? I am pretty sure there is, but i'll pay as a last resort, thanks
EDIT : Did it, i installed the Rollback package and then B131, everything got relocked and i lost the bootloader code, but at least it works now. Damn, i need to stop opening such useless threads...
stuckoutside said:
Any way to do it for free ? I am pretty sure there is, but i'll pay as a last resort, thanks
EDIT : Did it, i installed the Rollback package and then B131, everything got relocked and i lost the bootloader code, but at least it works now. Damn, i need to stop opening such useless threads...
Click to expand...
Click to collapse
HuRUpdater. You just need TWRP, all of the firmware zips and huru itself. It's guaranteed that HuRUpdater brings back the phone from dead.
https://forum.xda-developers.com/honor-9/development/tool-flash-official-firmware-recovery-t3769279
But remember: after you rebooted your phone, please go to eRecovery and perform a factory reset there. If you perform a factory reset with TWRP, your phone stays bricked.
---------- Post added at 07:48 PM ---------- Previous post was at 07:46 PM ----------
ThePS4Gamer said:
HuRUpdater. You just need TWRP, all of the firmware zips and huru itself. It's guaranteed that HuRUpdater brings back the phone from dead.
https://forum.xda-developers.com/honor-9/development/tool-flash-official-firmware-recovery-t3769279
But remember: after you rebooted your phone, please go to eRecovery and perform a factory reset there. If you perform a factory reset with TWRP, your phone stays bricked.
Click to expand...
Click to collapse
Update: If you figured it out, then it's OK. But you could keep the bootloader unlocked if you used HuRUpdater.
Hello everyone.
As mentioned above, my HTC is stuck in a Bootloop (Unlocked warning, white HTC Icon, and again) after I uninstalled a Magisk Module via Magisk Manager. I have no TWRP Recovery installed. Any advise how to get the phone operational again? In case of a full reset of data and storage, i am not afraid to do so. Any help is much appreciated.
Greetings
Stefan
*Edit*
I just noticed that adb doesn't recognizes the Phone via command adb devices. Therefore I'm not able to flash a ruu for my phone. Now I have no idea left what to do
Stefan-Duisburg said:
Hello everyone.
As mentioned above, my HTC is stuck in a Bootloop (Unlocked warning, white HTC Icon, and again) after I uninstalled a Magisk Module via Magisk Manager. I have no TWRP Recovery installed. Any advise how to get the phone operational again? In case of a full reset of data and storage, i am not afraid to do so. Any help is much appreciated.
Greetings
Stefan
*Edit*
I just noticed that adb doesn't recognizes the Phone via command adb devices. Therefore I'm not able to flash a ruu for my phone. Now I have no idea left what to do
Click to expand...
Click to collapse
you can flash from sd card
---------- Post added at 11:29 AM ---------- Previous post was at 11:26 AM ----------
tolgazorba said:
you can flash from sd card
Click to expand...
Click to collapse
You can find the same software number at the top of the device or the numbered software in the android file host ziand folder
Hello @tolgazorba.
Thank you for your answer. Right now I'm heading to work, but I will try your Advise this evening. Fortunately i downloaded a ruu zip matching with my firmware (2.55.bla bla) and matching with my cid as well. I will report if everything worked, or, hopefully not, not.
Thanks again
Stefan
hello
no problem I would like to explain in detail but my english is very bad
Hi there. That advice was great, everything works now fine again. I guess I let my hands off rooting for now, at least there's an official LOS for this device lol
Thanks again
En joy
You're welcome
I have little similar problem. I bricked phone after updating magisk.
Then I tried to flash original boot.img but didn't know which slot A or B so flashed both. Unfortunately, it doesn't help.
Please help me
Merhaba
are you serious
---------- Post added at 06:49 PM ---------- Previous post was at 06:48 PM ----------
lulonen said:
I have little similar problem. I bricked phone after updating magisk.
Then I tried to flash original boot.img but didn't know which slot A or B so flashed both. Unfortunately, it doesn't help.
Please help me
Click to expand...
Click to collapse
because I need help with something
---------- Post added at 06:55 PM ---------- Previous post was at 06:49 PM ----------
my problem is that i can't assign custom rom to your device why do you think
I thinked that's because of slots
Hi
buddy what exactly is the problem
completely don't know how to solve it.
bootimg flashed over TWRP, now i have original boot.img and cant start temporary recovery.
lulonen said:
completely don't know how to solve it.
bootimg flashed over TWRP, now i have original boot.img and cant start temporary recovery.
Click to expand...
Click to collapse
Maybe just flash actual firmware.zip with sdcard as i have done? With that you are back on full stock and you can root again etc...
Thx. unfortunately, I don't have a backup of one important app which is more important than the whole phone so I want to find every possibility without losing data.
hi
lulonen said:
Thx. unfortunately, I don't have a backup of one important app which is more important than the whole phone so I want to find every possibility without losing data.
Click to expand...
Click to collapse
You are a very old user, I think you know how to do it
Hi
full rom viper twrp with temporary rom flash without wipe i not temporary to permanent summer device
can't boot TWRP and dont have stock rom without wipe.
Don't you know why I can't boot temporary TWRP? download mode always stuck at booting
so find a backup of the auto and load it with adb sideload, whichever version you have is the backup of that version
---------- Post added at 04:09 PM ---------- Previous post was at 04:03 PM ----------
https://androidfilehost.com/?fid=6006931924117931578
isn't full wipe?
don't remember but EU version (043). I am on LeeDrOiD U12 V1.3
re-install the same rum without deleting or update it with adb sideload
tolgazorba said:
so find a backup of the auto and load it with adb sideload, whichever version you have is the backup of that version
---------- Post added at 04:09 PM ---------- Previous post was at 04:03 PM ----------
https://androidfilehost.com/?fid=6006931924117931578
Click to expand...
Click to collapse
If I only had a backup different to TWRP.... ;-(