Debranding to India variant BKL-L09C675B151 (with Jio VOLTE) - Honor View 10 ROMs, Kernels, Recoveries, & Other D

Note- Files for BKL-L09 C432 added in 3rd and 4th Post if you want to debrand to EU version (procedure will remain the same).
This was working fine for me and should work for you as well if followed correctly unless your hardware of specific version/build number limits something.
Hey Guys,
Some background -
I was thinking of debranding/rebranding my Honor view 10 since few months but as we were lacking the full firmware, I did not attempt the same. As per my previous experience with Huawei/Honor phones, I knew I need at least OEMINFO file for the region I want to rebrand to and was aware that I need the custom.bin file to get the VOLTE working (in my case, Indian version). As soon as I got both the files (backup), I attempted it and was successful. So finally I am able to use JIO VOLTE calling on my Honor phone (only my Honor 5X had the official VOLTE updates). Recently, I put some effort and got VOLTE working on my Honor 5C as well. Now, I will attempt the VOLTE part on my Honor 6X which I already debranded from China to Indian variant (Guide in my signature) as was not aware of the custom bin and later when tried it was not working but I am sure I will get it working this time.
Coming to the debranding/rebranding guide for Honor v10, I debranded my Honor V10 BKL-L09C432 (EU) to BKL-L09C675 (Indian) variant. As usual, you need patience, all the files handy and trust in the guide that you will get what you want (Debranding in this case).
Click to expand...
Click to collapse
Screenshot of my EU version before attempting debranding.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Note/warning"
I am unable to unlock my bootloader now as it is giving me wrong password error (with same bootloader unlock which worked for me earlier but not anymore). I am figuring out the possible reasons for this. May be, post flashing the OEMINFO file, once its gets locked, unlock it there so that you are still on same old firmware but flashing the SD card update will lock it again (not sure if you will be able to do this then). Don’t want to invest for DC unlocker or HCU to get the code which may be the same as earlier code as serial number, IMEI and product ID doesn’t change in the process. Because of Huawei security , the unlock code can't be used anymore after rebranding.
For Safer side, I would advise to uninstall the magisk (during the process) and install stock ramdisk. (if you are using magisk as I have seen while coming back to stock from custom ROM that my IMEI was lost).
If you are using magisk then download stock ramdisk for your model. Download update.app via firmware finder for your curent version, use Huawei extractor and extract the ramdisk.img Thanks to @worstenbrood for his thread
You may skip trying reboot to system and then booting to recovery and all and save few more minutes if you are impatient and don’t want to wait for few more seconds.
Do not skip steps to backup the files and data (you may need it anytime).
DO not skip any step, it may take few more seconds only but if you avoid, you may face issue.
OK, so if you still want to debrand to Indian version, read further.
Download oeminfo backup , extract and save to TWRP backup folder on SD card. (path will look like SDcard\TWRP\BACKUPS\YourPhoneSerialNumber\TWRP Backup- BKL-L09 C675 OEMINFO) Thanks to @ankan1993 for sharing the backup on Facebook.
Download the custom.bin file and save to SD card. Thanks to @ankan1993 for sharing the file.
Download the full firmware for Indian variant. Thanks to @luckykhera2 for uploading it and thanks to @ankan1993 for sharing here
Create a folder dload under the root directory of SD card.
Extract the BKL-L09 C675B151.zip file and copy all the content to dload folder.
Download EU Ramdisk (if you are on EU version to flash during process for full stock boot if you have magisk, if you are not using magisk, can skip this) Thanks to @topjohnwu for his thread
Backup everything on you current model via hisuite.
Boot to bootloader as -
Code:
c:\adb>adb reboot bootloader
Flash stock ramdisk as below to uninstall magisk (can do initially via magisk manager and flash stock boot, I just flashed stock ramdisk and never did anything via magisk) –
Code:
c:\adb>fastboot flash ramdisk ramdisk.img
target reported max download size of 471859200 bytes
sending 'ramdisk' (16384 KB)...
OKAY [ 0.360s]
writing 'ramdisk'...
OKAY [ 0.095s]
finished. total time: 0.467s
Boot to system again as
Code:
c:\adb>fastboot reboot
rebooting...
finished. total time: 0.007s
Boot to bootloader as -
Code:
c:\adb>adb reboot bootloader
Download TWRP thanks to @Pretoriano80 his thread
Install TWRP as
Code:
c:\adb>fastboot flash recovery_ramdisk twrp_bkl_0.7.img
target reported max download size of 471859200 bytes
sending 'recovery_ramdisk' (23542 KB)...
OKAY [ 0.834s]
writing 'recovery_ramdisk'...
OKAY [ 0.163s]
finished. total time: 1.044s
Boot to system as
Code:
c:\adb>fastboot reboot
rebooting...
finished. total time: 0.015s
Boot to TWRP as
Code:
c:\adb>adb reboot recovery
Backup everything in TWRP and copy the backup folder to external memory, SD card, PC etc (you may need it in worst case, I have but wont need it anymore)
Backup OEM (this may help others if they want to debrand to your current model) and save to a safe storage.
Flash the custom.bin zip file given in the attachment via TWRP (it is flashable zip)
Restore the oeminfo backup via TWRP (it is TWRP backup and not flashable zip as I was unable to obtain the raw oeminfo file and received this)
Disconnect your phone USB cable, if connected by any chance, from PC/laptop.
Turn off your phone from TWRP recovery option.
Press volume up+ volume down and power key together and dload flash will start updating your phone to Indian firmware.
Do not interrupt the process as it may not show any progress initially for 30 seconds and then will take around a minute for verification with a message verifying the update, upto 5%.
It will start installing the update from 6% onwards and it will again verify the package at around between 60% to 70% (for 3-5 seconds) and then will continue installing the update (may take some time while at 74%) and then will flash very quickly to 98% and then slowly to 100%.
Phone will restart normally, may take upto 2-3 minutes (so do not interrupt anything assuming bootloop or anything) and will ask for initial setup.
Once you are through initial setup, check about phone section.
You are on Indian version now with Jio VOLTE working.
If you follow the guide, I am 100% sure you will be able to debrand without any issue.
No more need to pay anything (51 USD) to Funky Huawei for such processes as you have your way of doing it on your own XDA portal.
Please consider donation if you can or want it encourages to make more such efforts.
Happy Flashing!!!
Screenshots post debranding.
Note- You will get OTA post debrand as well so no issues with that, Just got B161 update via OTA and installed successfully.

shashank1320 said:
Hey Guys,
Some background (read only when you have time ) -
I was thinking of debranding/rebranding my Honor view 10 since few months but as we were lacking the full firmware, I did not attempt the same. As per my previous experience with Huawei/Honor phones, I knew I need at least OEMINFO file for the region I want to rebrand to and was aware that I need the custom.bin file to get the VOLTE working (in my case, Indian version). As soon as I got both the files (backup), I attempted it and was successful. So finally I am able to use JIO VOLTE calling on my Honor phone (only my Honor 5X had the official VOLTE updates). Recently, I put some effort and got VOLTE working on my Honor 5C as well. Now, I will attempt the VOLTE part on my Honor 6X which I already debranded from China to Indian variant (Guide in my signature) as was not aware of the custom bin and later when tried it was not working but I am sure I will get it working this time.
Coming to the debranding/rebranding guide for Honor v10, I debranded my Honor V10 BKL-L09C432 (EU) to BKL-L09C675 (Indian) variant. As usual, you need patience, all the files handy and trust in the guide that you will get what you want (Debranding in this case).
Screenshot of my EU version before attempting debranding.
Note/warning"
I am unable to unlock my bootloader now as it is giving me wrong password error (with same bootloader unlock which worked for me earlier but not anymore). I am figuring out the possible reasons for this. May be, post flashing the OEMINFO file, once its gets locked, unlock it there so that you are still on same old firmware but flashing the SD card update will lock it again (not sure if you will be able to do this then). Don’t want to invest for DC unlocker or HCU to get the code which may be the same as earlier code as serial number, IMEI and product ID doesn’t change in the process.
For Safer side, I would advise to uninstall the magisk (during the process) and install stock ramdisk. (if you are using magisk as I have seen while coming back to stock from custom ROM that my IMEI was lost).
If you are using magisk then download stock ramdisk for your model. Download update.app via firmware finder for your curent version, use Huawei extractor and extract the ramdisk.img Thanks to @worstenbrood for his thread
You may skip trying reboot to system and then booting to recovery and all and save few more minutes if you are impatient and don’t want to wait for few more seconds.
Do not skip steps to backup the files and data (you may need it anytime).
DO not skip any step, it may take few more seconds only but if you avoid, you may face issue.
OK, so if you still want to debrand to Indian version, read further.
Download oeminfo backup , extract and save to TWRP backup folder on SD card. (path will look like SDcard\TWRP\BACKUPS\YourPhoneSerialNumber\TWRP Backup- BKL-L09 C675 OEMINFO) Thanks to @ankan1993 for sharing the backup on Facebook.
Download the custom.bin file and save to SD card. Thanks to @ankan1993 for sharing the file.
Download the full firmware for Indian variant. Thanks to @luckykhera2 for uploading it and thanks to @ankan1993 for sharing here
Create a folder dload under the root directory of SD card.
Extract the BKL-L09 C675B151.zip file and copy all the content to dload folder.
Download EU Ramdisk (if you are on EU version to flash during process for full stock boot if you have magisk, if you are not using magisk, can skip this) Thanks to @topjohnwu for his thread
Backup everything on you current model via hisuite.
Boot to bootloader as -
Flash stock ramdisk as below to uninstall magisk (can do initially via magisk manager and flash stock boot, I just flashed stock ramdisk and never did anything via magisk) –
Boot to system again as
Boot to bootloader as -
Download TWRP thanks to @Pretoriano80 his thread
Install TWRP as
Boot to system as
Boot to TWRP as
Backup everything in TWRP and copy the backup folder to external memory, SD card, PC etc (you may need it in worst case, I have but wont need it anymore)
Backup OEM (this may help others if they want to debrand to your current model) and save to a safe storage.
Flash the custom.bin zip file given in the attachment via TWRP (it is flashable zip)
Restore the oeminfo backup via TWRP (it is TWRP backup and not flashable zip as I was unable to obtain the raw oeminfo file and received this)
Disconnect your phone USB cable, if connected by any chance, from PC/laptop.
Turn off your phone from TWRP recovery option.
Press volume up+ volume down and power key together and dload flash will start updating your phone to Indian firmware.
Do not interrupt the process as it may not show any progress initially for 30 seconds and then will take around a minute for verification with a message verifying the update, upto 5%.
It will start installing the update from 6% onwards and it will again verify the package at around between 60% to 70% (for 3-5 seconds) and then will continue installing the update (may take some time while at 74%) and then will flash very quickly to 98% and then slowly to 100%.
Phone will restart normally, may take upto 2-3 minutes (so do not interrupt anything assuming bootloop or anything) and will ask for initial setup.
Once you are through initial setup, check about phone section.
You are on Indian version now with Jio VOLTE working.
If you follow the guide, I am 100% sure you will be able to debrand without any issue.
No more need to pay anything (51 USD) to Funky Huawei for such processes as you have your way of doing it on your own XDA portal.
Please consider donation if you can or want it encourages to make more such efforts.
Happy Flashing!!!
Screenshots post debranding.
Click to expand...
Click to collapse
this is too helpful.

Reserved for OEMINFO of other variant.
BKL-L09 C432 OEMINFO TWRP backup- https://mega.nz/#!eUdDHSaB!MLiRjJN6d5xc7IpdAoIHSk2Poian7hpsECpIER9zAbQ

Reserved for custom.bin of other variant.
BKL-L09 C432 custom BIN- https://mega.nz/#!PdV1XaAQ!dmRs_hf3QSvKN6CvGfDMMNdSeZCv93yk_Asgnzy4R3A

Let me try, but not sure suitable for my latest chinese 190 version with GPU Turbo technology or not ?
because 190 version enhance the security and much more safe.

richard_li said:
Let me try, but not sure suitable for my latest chinese 190 version with GPU Turbo technology or not ?
because 190 version enhance the security and much more safe.
Click to expand...
Click to collapse
It shouldn't make any difference. It will work for sure.

Great..I have an Indian c675
Maybe debrand to USA version
They have 8.1

br54 said:
Great..I have an Indian c675
Maybe debrand to USA version
They have 8.1
Click to expand...
Click to collapse
Unless someone with BKL-L04 can share oeminfo and custom bin or atleast oeminfo, you cant

shashank1320 said:
Unless someone with BKL-L04 can share oeminfo and custom bin or atleast oeminfo, you cant
Click to expand...
Click to collapse
Base on funkyhuawei website, BKL-04 and BKL-09 can't be rebrand each other ; so I am scared to do the trial;
Anyhow my chinese latest version 190 with GPU Turbo technology has been rebranded to India version successfully. Thanks a Lot !!!
The manually rebranding method is completely same as Mate 9 rebranding method......
Because of Huawei security , the unlock code can't be used anymore after rebranding.... the unlock code can be only used by one time..
---------- Post added at 01:28 PM ---------- Previous post was at 01:20 PM ----------
richard_li said:
Base on funkyhuawei website, BKL-04 and BKL-09 can't be rebrand each other ; so I am scared to do the trial;
Anyhow my chinese latest version 190 with GPU Turbo technology has been rebranded to India version successfully. Thanks a Lot !!!
The manually rebranding method is completely same as Mate 9 rebranding method......
Because of Huawei security , the unlock code can't be used anymore after rebranding.... the unlock code can be only used by one time..
Click to expand...
Click to collapse
Oh NO!!! still not successful, now the system is system 8.0.046 (0AJU), device is OXF, i flash twice already !!! how to fix ????
---------- Post added at 02:01 PM ---------- Previous post was at 01:28 PM ----------
@shashank1320
Urgent !!!!
I restored india OEMinfo successfully , it means the phone rebranded to india version, also can flash the india ROM (sdcard dload files in this thread) , i flashed 3 times already ,but still in abnormal status.
sorry i don't know how to upload screenshot , below is the record:
Device name : OXF
Model : BKL-09
Build number : system 8.0.0.046 (0AJU)
RAM : 3G , actually it should be 6G
internal storage :34GB (intotal) , actually it should be 120GB

richard_li said:
Oh NO!!! still not successful, now the system is system 8.0.046 (0AJU), device is OXF, i flash twice already !!! how to fix ????
---------- Post added at 02:01 PM ---------- Previous post was at 01:28 PM ----------
@shashank1320
Urgent !!!!
I restored india OEMinfo successfully , it means the phone rebranded to india version, also can flash the india ROM (sdcard dload files in this thread) , i flashed 3 times already ,but still in abnormal status.
sorry i don't know how to upload screenshot , below is the record:
Device name : OXF
Model : BKL-09
Build number : system 8.0.0.046 (0AJU)
RAM : 3G , actually it should be 6G
internal storage :34GB (intotal) , actually it should be 120GB
Click to expand...
Click to collapse
Uplaoding a file, please flash that as well and see. I will share the link in few minutes.

richard_li said:
Base on funkyhuawei website, BKL-04 and BKL-09 can't be rebrand each other ; so I am scared to do the trial;
Anyhow my chinese latest version 190 with GPU Turbo technology has been rebranded to India version successfully. Thanks a Lot !!!
The manually rebranding method is completely same as Mate 9 rebranding method......
Because of Huawei security , the unlock code can't be used anymore after rebranding.... the unlock code can be only used by one time.
Click to expand...
Click to collapse
May be due to Android version 8.0 vs 8.1 they cant be rebranded to each other.

shashank1320 said:
Uplaoding a file, please flash that as well and see. I will share the link in few minutes.
Click to expand...
Click to collapse
but I can't use my previous unlock code anymore, so how can flash another file ? will you upload some workable files but still in dload flash method ???
waiting for your good news & workable solution ............
thanks in advance !

richard_li said:
but I can't use my previous unlock code anymore, so how can flash another file ? will you upload some workable files but still in dload flash method ???
waiting for your good news & workable solution ............
thanks in advance !
Click to expand...
Click to collapse
You can flash that via dload. Actually that was already tehre but as I was able to debrand using only one file and no issues, I didnt share. I flashed that on mine but that made no difference. You can try in your case. only 10-12 minutes for uplaod time.

shashank1320 said:
You can flash that via dload. Actually that was already tehre but as I was able to debrand using only one file and no issues, I didnt share. I flashed that on mine but that made no difference. You can try in your case. only 10-12 minutes for uplaod time.
Click to expand...
Click to collapse
ok,make sure it is belong to india version. i will keep waiting .
thanks bro !!!

richard_li said:
ok,make sure it is belong to india version. i will keep waiting .
thanks bro !!!
Click to expand...
Click to collapse
Download and flash this via dload. extract first and then put all the content under dload folder.
https://mega.nz/#!PcFhGQqA!TkFs5Zj2lc32RkiwTuhcSCH5lA7r7YygaHeJdXYmFFU

shashank1320 said:
Download and flash this via dload. extract first and then put all the content under dload folder.
https://mega.nz/#!PcFhGQqA!TkFs5Zj2lc32RkiwTuhcSCH5lA7r7YygaHeJdXYmFFU
Click to expand...
Click to collapse
Thanks bro , I am downloading now , will finish within 7min.
i will try immediately .... hope it works..........
God bless me !!!

richard_li said:
Thanks bro , I am downloading now , will finish within 7min.
i will try immediately .... hope it works..........
God bless me !!!
Click to expand...
Click to collapse
Good luck. Hope this works for you

shashank1320 said:
Good luck. Hope this works for you
Click to expand...
Click to collapse
Just tried ,unfortunately it failed ... The files you just uploaded is not workable dload way...
If you have official & original india dload files, may it works ...
I think the previous dload files , is extracted from official update.zip ; if yes, it is not official sd update file ... the real official sd update file has different structure in the folder.
Anyhow , if you have other solution, please just feel free to share ...
thanks for your hard working !!!

richard_li said:
Just tried ,unfortunately it failed ... The files you just uploaded is not workable dload way...
If you have official & original india dload files, may it works ...
I think the previous dload files , is extracted from official update.zip ; if yes, it is not official sd update file ... the real official sd update file has different structure in the folder.
Anyhow , if you have other solution, please just feel free to share ...
thanks for your hard working !!!
Click to expand...
Click to collapse
It was correct file, see credit to person who uploaded the same. I used the same file and using my phone just fine. See my about phone screenshot in OP. I extracted the same file and flashed via dload without any issue. You may try renaming the hw_in.app file to update.app and try again and see.

shashank1320 said:
It was correct file, see credit to person who uploaded the same. I used the same file and using my phone just fine. See my about phone screenshot in OP. I extracted the same file and flashed via dload without any issue. You may try renaming the hw_in.app file to update.app and try again and see.
Click to expand...
Click to collapse
yes, it works after renaming the hw_in.app file to update.app ; now the device name/storage/build number is in normal status...
Now I am updating the FF method again, hope I can get full ROM package this time ;
Also suggest Bro to have a dload with full ROM package inside , it is the best way. because I feel still lacking something even the phone is in normal working status.

Related

[ROM][Official Beta][7D-503L & 7D-501u][Lollipop 5.1.1][EMUI 3.1][C208B011SP05/SP06]

[ROM][Official Beta][7D-503L & 7D-501u][Lollipop 5.1.1][EMUI 3.1][C208B011SP05/SP06]
Huawei has officially started its lollipop upgrade program for MediaPad X1 (7D-503L & 7D-501u) by pushing the first OTA updates to beta testers.
If you are not one of them but would still like to give it a swirl, ROM files and update instructions as below.
Flashing method is standard huawei procedures other than u will need to flash 2 files this time round, the first serves to re-partition the internal memory to accommodate lollipop.
The usual 'be careful, do it at your own risks' caveats apply, do take note that everything on the phone's internal memory (the 16GB part) will be wiped, your microSD card will not be affected though.
Have fun!
Not working:
1) Please note MHL (HDMI) function is not available in this ROM, if you require this function, do not update.
2) Xposed Framework is also a no go on EMUI 3.1 without modding, if u really must try, remember to have the uninstaller (flashable zip) ready in your microSD card, u will need that when you run into a X1 that fails to boot
(Huawei's default per app 320/400 dpi setting is working fine, thus non working Xposed is non consequential if u only need it for this purpose)
Steps:
1) Ensure your X1 (501u and 503L) is on the latest official (non-rooted) EMUI 3.0 B011 ROM, if not, kindly update to it
7D-501u - http://emuirom123.dbankcloud.com/7D-501u_EMUI3.0_Android4.4_V100R002C208B011.zip?rid=1141
7D-503L - http://emuirom123.dbankcloud.com/7D-503L_EMUI3.0_Android4.4_V100R002C208B011.zip?rid=1142
Clear cache and reset to factory settings before you flash the Beta 5.1.1 below.
2) Download the 2 necessary ROM files (the smaller 30+MB one is an update for modem / radio / kernel and also for re-partitioning etc; the larger near 1GB file is the ROM proper)
7D-503L
http://www.mediafire.com/download/9ea7yb206d869ya/7D-503LV100R002C208B011SP05.zip
http://www.mediafire.com/download/7o9g94z8c756ijs/7D-503LV100R002C208B011SP05_Main.zip
7D-501u
http://www.mediafire.com/download/pfp85guitv71745/7D-501uV100R002C208B011SP06.zip
http://www.mediafire.com/download/dld8lxrewj288tm/7D-501uV100R002C208B011SP06_Main.zip
3) At the root of your microSD card, create a folder and name it 'dload', rename the 30+MB file to 'update.zip' and copy that into 'dload' folder
4) Go to 'Settings', 'Updater', 'Menu' and 'Local update'. Choose the (only) update available and perform the update.
5) Phone will reboot and update will run, when you see a big tick, eject the microSD card and the phone will reboot again (if it doesn't, simply long press the power button to force shut and restart it).
6) After the phone has rebooted, re-insert the microSD, navigate to 'dload' folder and erase the update.zip file
7) Unzip the near 1GB ROM file and copy the update.app file into 'dload' folder
8) Download unlmt.rar file below and copy the 0 byte cfg file into the dload folder
9) repeat above steps 4) to 6) (delete update.app instead at step 6)**
** If you are prompted for a PIN code when the phone reboots after a flash, fret not, simply force shut it by long pressing the power button, then enter Recovery by pressing the vol+ & power button simultaneously, and choose to clear cache. The PIN code request will be gone when the phone reboots
Google Play Store and Calendar / Contacts Sync
10) Your X1 should now be on 5.1.1, download and install the 3 google apk files below to get Play Store and Calendar / Contacts Sync.
(Good news here is the whole google framework already exists in the ROM, therefore there is no need to mess with root to do that)
Root
To obtain root access on this ROM, use the latest Wondershare MobileGo one click root (Win) program - thanks to jonjong http://forum.xda-developers.com/showpost.php?p=63397619&postcount=34 - to root it.
There is also another 'cleaner' method of flashing custom CWM recovery and then chainfire's update.zip, but this will involve unlocked bootloader and some knowledge or ability to read chinese, will find some time to include a detailed write-up if there is demand for it. For now, you can download the necessary below:
http://www.mediafire.com/download/i564vr6587r2ma8/X1_5.1.1_Root.rar
Both methods need an unlocked bootloader AFAIK. If u come from B011, the bootloader should already have been unlocked.
If your X1 is 501L, you can unlock your bootloader by flashing the latest B102 ROM (EMUI3.0 / KK 4.4.2 / International / GAPPS) released by Huawei Germany - thanks to super_sonic http://forum.xda-developers.com/showpost.php?p=63420650&postcount=50
B102 download: http://www.mediafire.com/download/i...iaPad_X1_SDCard_Update_Android_4.4.2_B102.zip
Do note that if you do a factory reset after updating to 5.1.1 or re-flash 5.1.1 within 5.1.1, there is a chance that the bootloader will be re-locked.
Your mileage may vary.
Good luck
what about 501u ??
Great! Finally! Waiting for 501U
How is the performance guys. Is it snappier or the same lags?
Thank you very much, have been waiting for this since August as promised by Huawei. I don't want to stuck at kitkat (B011).
---------- Post added at 01:36 PM ---------- Previous post was at 01:33 PM ----------
With my 2 cents, you can use this rom on 501u with 4G switch off.
I dont understand,i have done everything right,but still its 4.4.2 and not 5.1.1.
And it doesnt recognize which version i have!!
When it boots it says android,and it doesnt have the Honor X1 logo.
drake19 said:
I dont understand,i have done everything right,but still its 4.4.2 and not 5.1.1.
And it doesnt recognize which version i have!!
When it boots it says android,and it doesnt have the Honor X1 logo.
Click to expand...
Click to collapse
reset the phone to factory settings, clear cache and re-flash.
hope it helps.
potatohead said:
reset the phone to factory settings, clear cache and re-flash.
hope it helps.
Click to expand...
Click to collapse
I have reset the phone,cleared cache but it does not re-flash the rom,it says something in chinese and it has and explanion mark.
When i flashed the first small update,in system info,it was saying that is B011SP5 but it wasnt 5.1.1.
drake19 said:
I have reset the phone,cleared cache but it does not re-flash the rom,it says something in chinese and it has and explanion mark.
When i flashed the first small update,in system info,it was saying that is B011SP5 but it wasnt 5.1.1.
Click to expand...
Click to collapse
have u tried flashing the big file it in recovery?
if still not working, download and unzip the attached file, put the unzipped 0 byte cfg file together with update.app in dload folder, reboot the phone and see if it auto flashes, if it does, hope it flashes as per normal.
if it doesn't, restart in recovery and tried flashing it again.
potatohead said:
have u tried flashing the big file it in recovery?
if still not working, download and unzip the attached file, put the unzipped 0 byte cfg file together with update.app in dload folder, reboot the phone and see if it auto flashes, if it does, hope it flashes as per normal.
if it doesn't, restart in recovery and tried flashing it again.
Click to expand...
Click to collapse
It flashes the rom but its the same,old android logo on boot and it thinks that it have 4.4.2 not 5.1.1.
Mine X1 it came with european rom 7D-501L but on the box the model is 7D-503L,i flashed the 4.4.2 with the product flag.
drake19 said:
It flashes the rom but its the same,old android logo on boot and it thinks that it have 4.4.2 not 5.1.1.
Mine X1 it came with european rom 7D-501L but on the box the model is 7D-503L,i flashed the 4.4.2 with the product flag.
Click to expand...
Click to collapse
1st try also same problem as yours, I tried with dload contain only update.app then successful. Hope this will help.
jonjong said:
1st try also same problem as yours, I tried with dload contain only update.app then successful. Hope this will help.
Click to expand...
Click to collapse
Have you flashed it via updater at second time!?
Thank you so much, working great for 501L
Please more details for my 501l
Should i flash the modem file too before updating with the main file as per suggested procedure.. how did you manage to make this work on a 501l .. please clarify..
anyone got root?
giuliano.rigon said:
Should i flash the modem file too before updating with the main file as per suggested procedure.. how did you manage to make this work on a 501l .. please clarify..
Click to expand...
Click to collapse
1. Ensure your X1 501L is on the latest EMUI 3.0 7D-503LV100R002C208B011 ROM.
2. Flash this rom => http://www.mediafire.com/download/9e...08B011SP05.zip
3. Follow post #9 put attach file to dload folder + main rom and copy to micro sd card, and go to restart your phone.
Good luck.
sikidim7 said:
anyone got root?
Click to expand...
Click to collapse
Same question here, tried a few methods but no prevail, my bootloader is unlocked & rooting were easy on Kitkat. Any advise?
File was removed from mediafire apparently.. .. is it the same one you can download at the start of this post? i have dowloaded it already.. the file you tried to share has been in any waymodified for 501l.. thanks
---------- Post added at 09:42 AM ---------- Previous post was at 09:40 AM ----------
Cannot find file on mediafire.. is it a modificstionof the one at the start of the post, the 503l one.. i got that one..
Sorry but mediafire lists your file as unavailable.. thanks for reposting if you can..
---------- Post added at 04:22 PM ---------- Previous post was at 04:05 PM ----------
Eoo007 said:
Thank you so much, working great for 501L
Click to expand...
Click to collapse
Unrooted 501l on european b103.. how do i proceed please to flash this lollipop 503l on my phone.. if anyone could help..
giuliano.rigon said:
Sorry but mediafire lists your file as unavailable.. thanks for reposting if you can..
Unrooted 501l on european b103.. how do i proceed please to flash this lollipop 503l on my phone.. if anyone could help..
Click to expand...
Click to collapse
it is the same file i posted in the OP, it is not removed, rather Eoo007 didn't do a proper link, here u go:
http://www.mediafire.com/download/9ea7yb206d869ya/7D-503LV100R002C208B011SP05.zip
from huawei's forum, this file apparently also serves the purpose of re-partitioning to accommodate lollipop, other than updating the necessary modems.
good luck

[GUIDE][Experience] HOW TO unlock, flash TWRP and root your Huawei Mate 9 Pro (LON)

This thread applies to Huawei Mate 9 Pro only (model LON*, as M9Pro below). For Mate 9 (model MAH*) please go to the corresponding forum.
-----
Disclaimer:
I won't be responsible for bricked phone. Proceed with your own risk, make sure you know what you are doing.
This thread can be seen as a guide if your phone has exactly the same model and build version as mine. Otherwise please consider it as a description of my experiences for unlocking, flashing and rooting the phone.
SUPPORTED DEVICES:
LON-L29
LON-AL00
-----
As a start, this phone is great and I feel that it doesn’t need to be unlocked and rooted for a stable and long lasting daily use. However, unlock and root is almost a religion if you use Android phones
As a piece of info, big thanks to @raimondomartire, there is a thread for unlock, flash TWRP and root in the Mate 9 forum https://forum.xda-developers.com/mate-9/development/recovery-huawei-mate-9-pro-unofficial-t3546976, which is however according to my experience not totally applicable for the M9Pro anymore. There are also several other threads on the Mate 9 forum. Many things can be shared between both phones, but not always. Be careful about what you are doing!
-----
General info and attentions:
- My phone is M9Pro LON-AL00 (All net version from Chinese Mainland); LON-L29 (International version) should also work.
- This thread applies for build LON-AL00C00B213. Can be also applicable for similar builds, but I couldn’t test. Please report.
- None of the current builds of TWRP (up to 3.1.0) can decrypt data partition by default, which means you could only format the data partition in TWRP in order to access it in recovery (for backup to and install from internal storage etc.). But after formatting, you have to flash Huawei’s special stock data back to data partition (/data/hw_init), otherwise several functions of Huawei ROM won’t work. Refer to this (https://forum.xda-developers.com/showpost.php?p=71302827&postcount=627) or this (https://forum.xda-developers.com/showpost.php?p=72497328&postcount=204). Thanks to @gm007 and @ante0
- There are several root methods which handles encrypted or decrypted data partition. I didn’t format the data partition, i.e. data is still encrypted. If you want to format the data partition, please refer to this thread: https://forum.xda-developers.com/mate-9/how-to/guide-how-to-root-mate-9-decrypt-data-t3569986. Thanks to @eddmecha
- If you need stock ROM, refer to useful links below. Use Huawei Update Extractor to extract the individual partitions from the ROM: https://forum.xda-developers.com/showthread.php?t=2433454
-----
Unlock bootloader:
There is enough info in the internet about unlocking M9Pro’s bootloader. Just a few points to mention:
- Generally, you can follow the steps in @raimondomartire thread (https://forum.xda-developers.com/mate-9/development/recovery-huawei-mate-9-pro-unofficial-t3546976). But unlike he describes in his thread, there is no OEM Unlock options in the developer options anymore. Just use ADB to unlock.
- FRP unlock is not required!
- Huawei enables now a 14-day limitation, where you can officially get the bootloader unlock code 14 days after you first activate your Huawei ID on your phone and have logged in using your Huawei ID 14 CONSECUTIVE days.
- To go around this limitation, you can use dc-unlocker to get the bootloader code immediately. Google yourself
-----
Flash TWRP:
- Still, you can follow the steps in @raimondomartire thread (https://forum.xda-developers.com/mate-9/development/recovery-huawei-mate-9-pro-unofficial-t3546976).
- The image from this thread is 3.0.3, which has some bugs built in, especially when flashing SuperSU.
- You could use TWRP 3.1.0-1 from https://forum.xda-developers.com/mate-9/development/recovery-unofficial-twrp-huawei-mate-9-t3515617, but this one seems to have problem to be recognized as ADB device in recovery.
- There is a version 3.0.2 for Mate 9, which seems to have problem mounting USB-OTG.
- If your data partition is encrypted, you can only use ADB sideload or USB-OTG to install anything.
- If you want to do data wipe in TWRP, you have to flash Huawei’s special stock data back to data partition. See above general info and attentions.
-----
Root:
Firstly, thanks to @ante0 for explaining different flags in the root methods: https://forum.xda-developers.com/showpost.php?p=72504501&postcount=210. Some more discussions between us are also around this post.
I also tried several other root tools on the market (mobilego, vroot, YoRoot, OneClickRoot, iRoot etc.), NONE of them works.
As mentioned, there are different root methods around for unlocking M9Pro, depending on if you want to format your data partition. For me, I didn’t format, and SuperSU works for me. And the mate_9_pro_root.zip from @raimondomartire thread didn’t work for me.
I followed the steps below:
1. Get TWRP 3.1.0-1 (https://forum.xda-developers.com/mate-9/development/recovery-unofficial-twrp-huawei-mate-9-t3515617)
2. Disable fingerprint ID (I think it’s probably optional, but have read somewhere that fingerprint stops working after flashing root).
3. Flash stock boot image for B213D (in download section). I think it’s optional too, but if you have tried other methods before, you can do this step to make sure your boot is stock and clean
4. Flash TWRP 3.1.0-1
5. Flash SuperSU-v2.79-MATE9-init.d_support_no_decrypt-signed.zip (in download section) via USB-OTG (in TWRP the device is not recognized as an ADB device, hence no “ADB sideload”). Thanks to @ante0 for building this zip!
6. Reboot – phone will reboot itself twice and SuperSU.apk will be installed automatically
7. You could flash back to 3.0.3, if you want the ADB sideload function.
-----
Download:
- TWRP 3.0.3-1: https://forum.xda-developers.com/mate-9/development/recovery-huawei-mate-9-pro-unofficial-t3546976
- TWRP 3.1.0-1: https://forum.xda-developers.com/mate-9/development/recovery-unofficial-twrp-huawei-mate-9-t3515617
- SuperSU modified for M9Pro (thanks to @ante0): https://mega.nz/#!bR8D2Bab!bIgMLVmoll9R0GFqoFgkLxULrXlQ2710INt3TNbuI0c
- Boot image from B213D: https://mega.nz/#!LFlGTTZY!AaFq-_quM44YlK_Qdh9PgOjBE3Wtepmyz5OAuo_mabw
-----
Useful links:
- Stock firmware: http://hwmt.ru/oth/HWFF/info/view.php?find_model=lon
- Huawei Update (ROM) Extractor: https://forum.xda-developers.com/showthread.php?t=2433454
Enjoy your Mate!
Just some clarification: (eventhough you wrote it's for AL00C00B213, which I missed xD)
Flashing stock boot is only needed if you're already rooted.
Boot image B213D is only for AL00C00. If you have a different model/build, use the boot image for that specific build:
Download your stock firmware from hwmt.ru and Huawei Update Extractor. Extract update.app from your firmware zip.
Open update.app in Huawei Update Extractor. Rightclick on BOOT and click on Extract selected.
Flash the extracted boot.img using fastboot in download mode (fastboot flash boot boot.img).
OEM Unlocking is required to be enabled. It's just not there in the chinese version (AL00). So check if it's there first and enable if it is.
Hi guys. Not sure if this is the right place to ask but how do I get rid of that annoying "your device is unlocked and can't be trusted....etc " msg?
I have a mate 9 pro and I want to flash twrp and to root it. I did it for some one plus, xiaomi, samsung so I have some experience. reading xda posts about the case of M9pro I understood that is not a simple path and I dont want to hard brick the phone. what precautions should I take?
attached phone config
thank you in advance
ante0 said:
Just some clarification: (eventhough you wrote it's for AL00C00B213, which I missed xD)
Flashing stock boot is only needed if you're already rooted.
Boot image B213D is only for AL00C00. If you have a different model/build, use the boot image for that specific build:
Download your stock firmware from hwmt.ru and Huawei Update Extractor. Extract update.app from your firmware zip.
Open update.app in Huawei Update Extractor. Rightclick on BOOT and click on Extract selected.
Flash the extracted boot.img using fastboot in download mode (fastboot flash boot boot.img).
OEM Unlocking is required to be enabled. It's just not there in the chinese version (AL00). So check if it's there first and enable if it is.
Click to expand...
Click to collapse
hwmt. ru is unavailable
mcn1970 said:
hwmt. ru is unavailable
Click to expand...
Click to collapse
http://hwmt.ru/hwmtsite/firmware-database/
working fine for me.
Edit: I should probably have posted the full link in my previous post. Sorry.
ante0 said:
http://hwmt.ru/hwmtsite/firmware-database/
working fine for me.
Edit: I should probably have posted the full link in my previous post. Sorry.
Click to expand...
Click to collapse
is it all procedures safe? no risk of hard brick?
ante0 said:
Just some clarification: (eventhough you wrote it's for AL00C00B213, which I missed xD)
Flashing stock boot is only needed if you're already rooted.
Boot image B213D is only for AL00C00. If you have a different model/build, use the boot image for that specific build:
Download your stock firmware from hwmt.ru and Huawei Update Extractor. Extract update.app from your firmware zip.
Open update.app in Huawei Update Extractor. Rightclick on BOOT and click on Extract selected.
Flash the extracted boot.img using fastboot in download mode (fastboot flash boot boot.img).
OEM Unlocking is required to be enabled. It's just not there in the chinese version (AL00). So check if it's there first and enable if it is.
Click to expand...
Click to collapse
i unlocked the bootloader and flashed recovery but my OTG stick is not recognized and cannot be mounted. also while in recovery the phone is not seen on PC.
i tried with both recoveries above.
ADB sideload doesnt work...keeps saying starting ADB sideloading features...in TWRP sdcard content is a bunch of files with weird names...
therefore how can I root the phone?
someone please help me!!
mcn1970 said:
i unlocked the bootloader and flashed recovery but my OTG stick is not recognized and cannot be mounted. also while in recovery the phone is not seen on PC.
i tried with both recoveries above.
ADB sideload doesnt work...keeps saying starting ADB sideloading features...in TWRP sdcard content is a bunch of files with weird names...
therefore how can I root the phone?
someone please help me!!
Click to expand...
Click to collapse
edit: solved it
any OTA after?
hi guys. You may or may not find this interesting. I certainly did. I'll post this in the mate 9 pro forum as well but i just thought i could get some ideas from as many of guys as possible seeying that theres a lot more posts here for mate 9 in general.
I have chinese version mate 9 pro that has been rebranded from AL00 to LON Spcseas and rooted. Build number b228. Anyway i recently saw in FF the new b229 so i downloaded all three files which had longer file names than usuall by the way. In twrp, the only file that was visable was the update.zip. So i renamed the hw and public zip files to what they would usually be named. Wiped data, and flashed all three files. Then reflashed supersu.
This is the interesting bit ( i think ). My imei numbers have changed, before flashing, the first imei number ended in 7 - now it ends with 4, the second imei number ended in 9 and now it ends with 7. Also, i now have a MEID number visable which was not there before and a section called android security patch level. Oddly enough im not getting any issues out of play store, im on play store right now and not a single problem regarding authentication. The build number is the same as well. As far as functionality goes, everything seems to be tip top, in fact everything seems to be working better, even unofficial exposed is working well. Only one thing isn't working properly. In phone manager there was a feature in the battery section that darkens the interface for everything to save power and prolong battery. That doesn't seem to be working anymore. In App - Permissions, the permissions is greyed out and it says no permissions requested.. Any thoughts or explenations guys??
Trying to flash another orginal stock rom
I bought a Mate 9 Pro, China Version (LON-AL00C00) want to install Mate 9 Pro, Asia Version (LON-L29C636) software on it. All explanations about Mate 9 Pro is for models which have SD Card. My Mate 9 Pro with dual sims and not containing a SD Card enrty.
I succesfully unlocked the bootloader, installed TWRP but couldn't flash LON-L29C636 stock software. Because TWRP don't see update.zip file. Not only update.zip, any files I downloaded or copied before. When I put a OGT TWRP suddenly exits and phone restarts.:crying:
As you see I can't flash a zip file and ofcourse superuser zip file to root as well. I'm stuck in this triangle. Please give me a hand guys.
I can't root my phone. Because I can't view and locate any file of my phone. When I plug a ogt cable twrp exits and phone restarts. 6GB-128GB Dual Sim version
---------- Post added at 11:48 AM ---------- Previous post was at 11:47 AM ----------
Seems I am the only one who is looking for something about Mate 9 Pro
CrisperNeO said:
This thread applies to Huawei Mate 9 Pro only (model LON*, as M9Pro below). For Mate 9 (model MAH*) please go to the corresponding forum.
-----
Disclaimer:
I won't be responsible for bricked phone. Proceed with your own risk, make sure you know what you are doing.
This thread can be seen as a guide if your phone has exactly the same model and build version as mine. Otherwise please consider it as a description of my experiences for unlocking, flashing and rooting the phone.
SUPPORTED DEVICES:
LON-L29
LON-AL00
-----
As a start, this phone is great and I feel that it doesn’t need to be unlocked and rooted for a stable and long lasting daily use. However, unlock and root is almost a religion if you use Android phones
As a piece of info, big thanks to @raimondomartire, there is a thread for unlock, flash TWRP and root in the Mate 9 forum https://forum.xda-developers.com/mate-9/development/recovery-huawei-mate-9-pro-unofficial-t3546976, which is however according to my experience not totally applicable for the M9Pro anymore. There are also several other threads on the Mate 9 forum. Many things can be shared between both phones, but not always. Be careful about what you are doing!
-----
General info and attentions:
-My phone is M9Pro LON-AL00 (All net version from Chinese Mainland); LON-L29 (International version) should also work.
-This thread applies for build LON-AL00C00B213. Can be also applicable for similar builds, but I couldn’t test. Please report.
-None of the current builds of TWRP (up to 3.1.0) can decrypt data partition by default, which means you could only format the data partition in TWRP in order to access it in recovery (for backup to and install from internal storage etc.). But after formatting, you have to flash Huawei’s special stock data back to data partition (/data/hw_init), otherwise several functions of Huawei ROM won’t work. Refer to this (https://forum.xda-developers.com/showpost.php?p=71302827&postcount=627) or this (https://forum.xda-developers.com/showpost.php?p=72497328&postcount=204). Thanks to @gm007 and @ante0
-There are several root methods which handles encrypted or decrypted data partition. I didn’t format the data partition, i.e. data is still encrypted. If you want to format the data partition, please refer to this thread: https://forum.xda-developers.com/mate-9/how-to/guide-how-to-root-mate-9-decrypt-data-t3569986. Thanks to @eddmecha
-If you need stock ROM, refer to useful links below. Use Huawei Update Extractor to extract the individual partitions from the ROM: https://forum.xda-developers.com/showthread.php?t=2433454
-----
Unlock bootloader:
There is enough info in the internet about unlocking M9Pro’s bootloader. Just a few points to mention:
-Generally, you can follow the steps in @raimondomartire thread (https://forum.xda-developers.com/mate-9/development/recovery-huawei-mate-9-pro-unofficial-t3546976). But unlike he describes in his thread, there is no OEM Unlock options in the developer options anymore. Just use ADB to unlock.
-FRP unlock is not required!
-Huawei enables now a 14-day limitation, where you can officially get the bootloader unlock code 14 days after you first activate your Huawei ID on your phone and have logged in using your Huawei ID 14 CONSECUTIVE days.
-To go around this limitation, you can use dc-unlocker to get the bootloader code immediately. Google yourself
-----
Flash TWRP:
-Still, you can follow the steps in @raimondomartire thread (https://forum.xda-developers.com/mate-9/development/recovery-huawei-mate-9-pro-unofficial-t3546976).
-The image from this thread is 3.0.3, which has some bugs built in, especially when flashing SuperSU.
-You could use TWRP 3.1.0-1 from https://forum.xda-developers.com/mate-9/development/recovery-unofficial-twrp-huawei-mate-9-t3515617, but this one seems to have problem to be recognized as ADB device in recovery.
-There is a version 3.0.2 for Mate 9, which seems to have problem mounting USB-OTG.
-If your data partition is encrypted, you can only use ADB sideload or USB-OTG to install anything.
-If you want to do data wipe in TWRP, you have to flash Huawei’s special stock data back to data partition. See above general info and attentions.
-----
Root:
Firstly, thanks to @ante0 for explaining different flags in the root methods: https://forum.xda-developers.com/showpost.php?p=72504501&postcount=210. Some more discussions between us are also around this post.
I also tried several other root tools on the market (mobilego, vroot, YoRoot, OneClickRoot, iRoot etc.), NONE of them works.
As mentioned, there are different root methods around for unlocking M9Pro, depending on if you want to format your data partition. For me, I didn’t format, and SuperSU works for me. And the mate_9_pro_root.zip from @raimondomartire thread didn’t work for me.
I followed the steps below:
1.Get TWRP 3.1.0-1 (https://forum.xda-developers.com/mate-9/development/recovery-unofficial-twrp-huawei-mate-9-t3515617)
2.Disable fingerprint ID (I think it’s probably optional, but have read somewhere that fingerprint stops working after flashing root).
3.Flash stock boot image for B213D (in download section). I think it’s optional too, but if you have tried other methods before, you can do this step to make sure your boot is stock and clean
4.Flash TWRP 3.1.0-1
5.Flash SuperSU-v2.79-MATE9-init.d_support_no_decrypt-signed.zip (in download section) via USB-OTG (in TWRP the device is not recognized as an ADB device, hence no “ADB sideload”). Thanks to @ante0 for building this zip!
6.Reboot – phone will reboot itself twice and SuperSU.apk will be installed automatically
7.You could flash back to 3.0.3, if you want the ADB sideload function.
-----
Download:
-TWRP 3.0.3-1: https://forum.xda-developers.com/mate-9/development/recovery-huawei-mate-9-pro-unofficial-t3546976
-TWRP 3.1.0-1: https://forum.xda-developers.com/mate-9/development/recovery-unofficial-twrp-huawei-mate-9-t3515617
-SuperSU modified for M9Pro (thanks to @ante0): https://mega.nz/#!bR8D2Bab!bIgMLVmoll9R0GFqoFgkLxULrXlQ2710INt3TNbuI0c
-Boot image from B213D: https://mega.nz/#!LFlGTTZY!AaFq-_quM44YlK_Qdh9PgOjBE3Wtepmyz5OAuo_mabw
-----
Useful links:
-Stock firmware: http://hwmt.ru/oth/HWFF/info/view.php?find_model=lon
-Huawei Update (ROM) Extractor: https://forum.xda-developers.com/showthread.php?t=2433454
Enjoy your Mate!
Click to expand...
Click to collapse
I unlocked bootloader but couldn't root. Anyway I wanted to rebrand my phone to Asia version. Now I'm done but not successful because there is no Google,frp locked, and version is test one.
I can't install twrp because frp lock don't allow it. Also twrp can't read 128 GB internal memory, so I needed to install from pc.
Is there anyway to resolve and install stock Oreo version to my Mate 9 Pro or do you suggest me to resolve it via paid services?
PRA-LX1 cihazımdan Tapatalk kullanılarak gönderildi
livevalue said:
I unlocked bootloader but couldn't root. Anyway I wanted to rebrand my phone to Asia version. Now I'm done but not successful because there is no Google,frp locked, and version is test one.
I can't install twrp because frp lock don't allow it. Also twrp can't read 128 GB internal memory, so I needed to install from pc.
Is there anyway to resolve and install stock Oreo version to my Mate 9 Pro or do you suggest me to resolve it via paid services?
PRA-LX1 cihazımdan Tapatalk kullanılarak gönderildi
Click to expand...
Click to collapse
I've installed Oreo to Mate 9 Pro. If you have 128GB edition don't try to install anything from internal storage. That's it.
PRA-LX1 cihazımdan Tapatalk kullanılarak gönderildi
Hi guys, for re-branding there are threads in general Mate 9 forum. I didnt do it and am not planning to do it either...
CrisperNeO said:
Hi guys, for re-branding there are threads in general Mate 9 forum. I didnt do it and am not planning to do it either...
Click to expand...
Click to collapse
Rebranding is easy with HWOTA system if you will keep your phone EMUI 5.0 Nougat. And there is no risk if you make everything clearly.
PRA-LX1 cihazımdan Tapatalk kullanılarak gönderildi
never used Huawei before have a couple of questions
1. Is there anyway to get back to full stock with relock bootaloder in case the device need to go to service center?
(assume unlock bootloader with dc-unlocker not huawei id one)
2. From question 1 what do i need to do or backup before root?
thnak you so much!
44alphabeT said:
never used Huawei before have a couple of questions
1. Is there anyway to get back to full stock with relock bootaloder in case the device need to go to service center?
(assume unlock bootloader with dc-unlocker not huawei id one)
2. From question 1 what do i need to do or backup before root?
thnak you so much!
Click to expand...
Click to collapse
Yes you can always flash stock ROM as factory out, if you are not in Oreo.
And you can root it. It's your own protection to have a backup. I suggest you have, anyway it's up to you. You can loose all your data after root.
Hi, yersterday I used TWRP trying to install a newer firmware and I wiped system partition and now it does not boot because it doesn't have an OS. I was on EMUI 8 (636) trying to update the firmware.
Is there any way to flash a firmware via TWRP or Fastboot on EMUI 8 (i know partition names change on Oreo).
Thanks!

Stuck on huawei erecovery

Hello.
My honor 9 (stf al00) cant boot. It stuck on huawei erecovery.
I've tried hard reset, wipe cache & wipe data but still stuck.
And also I dont have the driver.
Can anyone please help me.
What happened before ?
You were on nougat or oreo ? which build ?
Which region ? C00 ? or rebranded C432 or else ?
oslo83 said:
What happened before ?
You were on nougat or oreo ? which build ?
Which region ? C00 ? or rebranded C432 or else ?
Click to expand...
Click to collapse
I dont know what happend, give my brother use for awhile, suddenly he return to me with this problem.
its on nougat. sorry what build, i dont know.
Region China?. i dont know about the C00 or rebranded and c432 that you said. really have no idea.
OK.
So your Honor9 is STF-AL00 and was on nougat.
But:
-you don't know on which firmware region it was and you don't know if it was rebranded to STF-L09
-i guess your brother could also have updated it to oreo, or rebranded it before bricking it...
If you did not have any chinese app stock installed like QQ, Weibo or Tancent News then you could be probably on region C432 (or C10 or C185) ;
If so use this with an exfat external micro sdcard or usb-otg EXFAT formatted:
https://forum.xda-developers.com/honor-9/development/firmware-huawei-honor-9-stf-l09-stock-t3696892
First try with C432B130, read the instructions inside, do it, then report.
thanks.. i will try it tonight,
i've done try update with sd card before, but not with those file inside the link you give.
and also not with EXFAT fromat sd card, but it said Software Update Failed.
i will try this and update here again..
thanks
honor 9 stf-al00
phone unlocked and frp unlock
bricked the phone installing oreo.
twrp is installed but all the roms i flash i get error 9.
dload with update.app get stuck at 5% and after "system update failed"
i also extracted update.app and i can flashed boot,kernel and recovery but i get an error flashing system
At this point i just want the phone running anything but everything that i do doenst work
ruigarcia said:
honor 9 stf-al00
phone unlocked and frp unlock
bricked the phone installing oreo.
twrp is installed but all the roms i flash i get error 9.
dload with update.app get stuck at 5% and after "system update failed"
i also extracted update.app and i can flashed boot,kernel and recovery but i get an error flashing system
At this point i just want the phone running anything but everything that i do doenst work
Click to expand...
Click to collapse
Are you with nougat or oreo partitionni'g scheme ?-> are you actually booting on a nougat twrp or on a oreo twrp ?
Which region your phone were on on ?
original chinese C00 ?
or rebranded C432, C10 or else?[/QUOTE]
oslo83 said:
Are you with nougat or oreo partitionni'g scheme ?-> are you actually booting on a nougat twrp or on a oreo twrp ?
Which region your phone were on on ?
original chinese C00 ?
or rebranded C432, C10 or else?
Click to expand...
Click to collapse
[/QUOTE]
right now with oreo partitions, never rebranded the phone, and i was running update b362 so i assume im still on c00, otherwise i dont think i would have worked.
twrp is 3.1.1.1 open kirin edition
right now with oreo partitions, never rebranded the phone, and i was running update b362 so i assume im still on c00, otherwise i dont think i would have worked.
twrp is 3.1.1.1 open kirin edition[/QUOTE]
OK so, the facts :
1) B362 firmware are mostly european (C432) or russian (C10) and could be japanese (C635).
So your phone was previously rebranded from chinese to one of these region.
It's not a problem if not done wrong, maybe your case...
2)'twrp 3.1.1.1 open kirin edition' is a custom recovery for NOUGAT and not for oreo.
And then some more questions:
-Can you boot your phone to normal mode ?
-You were on nougat before brick ?
-You were one oreo B362 before brick ?
-The brick happens after it upgraded from mogat to oreo B362 ? If so, how did you update ? normal OTA ? forced OTA with android app Firmware Finder ?
i can only boot the phone in recovery mode (twrp and erecovery) and fastboot
i installed b360 through forced ota and then when i was in the system i updated again to b362 throught settings\system update
i was on oreo b362 before brick, and i remember now that my navigations buttons were not working so i flashed a custom kernel to fix it, but
that prevented me from booting to the system again. (Proto Kernel)
edit: used that tool you gave me and i managed to flash STF-L09_C432B360.
ruigarcia said:
i installed b360 through forced ota and then when i was in the system i updated again to b362 throught settings\system update
Click to expand...
Click to collapse
So your phone was correctly rebranded in the past and we can deduce you are now on region C432 or C10.
ruigarcia said:
i was on oreo b362 before brick, and i remember now that my navigations buttons were not working so i flashed a custom kernel to fix it, but
that prevented me from booting to the system again. (Proto Kernel)
Click to expand...
Click to collapse
You flashed a custom B360 kernel over your B362 : It was why your phone bootlooped just after !!
Flashing a stock B362 kernel would have solve the bootloop.
ruigarcia said:
i also extracted update.app and i can flashed boot,kernel and recovery but i get an error flashing system
Click to expand...
Click to collapse
You said you had flashed boot, kernel and recovery from an update.app.... Which build number and region this update.app was from ?
You could flash back B362 stock boot, kernel and recovery and it should boot if you did not messed something else...
So, the best for you will be to:
1) use HuRUpdater to flash C432B360 or C10B360 firmware (depending of your actual phone region)
2)then flash the B360 kernel fix
3)then update via OTA or huRUpdater.
oslo83 said:
So your phone was correctly rebranded in the past and we can deduce you are now on region C432 or C10.
You flashed a custom B360 kernel over your B362 : It was why your phone bootlooped just after !!
Flashing a stock B362 kernel would have solve the bootloop.
You said you had flashed boot, kernel and recovery from an update.app.... Which build number and region this update.app was from ?
You could flash back B362 stock boot, kernel and recovery and it should boot if you did not messed something else...
So, the best for you will be to:
1) use HuRUpdater to flash C432B360 or C10B360 firmware (depending of your actual phone region)
2)then flash the B360 kernel fix
3)then update via OTA or huRUpdater.
Click to expand...
Click to collapse
i flashed many update.app, i messed up with that, cant remember the last one.
just flashed twrp for oreo now, went to terminal and i can see "ro.hw.vendor: (hw)
does this tell me my phone region?
with this twrp for oreo i also get another error when flashing a rom zip "failed to mount "\system" (permission denied)
Stop messing with random dload folder and update.app ; From what i seen only special one called 'service repair' will work.
No. It does not.
Stop messing trying to flash random zip when on twrp ; From what i heard only special one called 'FullOTA-MF-PV' will work this way with twrp.
Be bold and try HuRUpdater witj C432B360 following my latter post.
oslo83 said:
Stop messing with random dload folder and update.app ; From what i seen only special one called 'service repair' will work.
No. It does not.
Stop messing trying to flash random zip when on twrp ; From what i heard only special one called 'FullOTA-MF-PV' will work this way with twrp.
Be bold and try HuRUpdater witj C432B360 following my latter post.
Click to expand...
Click to collapse
i used HuRUpdater and worked. thank you! cant update to b362 through settings tho
C432 is maybe the wrong region if you don't get ota update notification to b362/b364 when checking for update in settings :
1) What's your build number version on Settings/System/about ?
2) What's the country shown when you dial**#*#2846579#*#**- on the dial pad, then go to 'Network Information Query' and then to 'Vendor Country Info' ?
---------- Post added at 19:44 ---------- Previous post was at 19:42 ----------
Dial**#*#2846579#*#*
---------- Post added at 19:46 ---------- Previous post was at 19:44 ----------
sorry typos.
So dial:
Code:
*#*#2846579#*#*
im so sorry, i cant access my pc right now.
i will update soon i can get access to my pc.
oslo83 said:
C432 is maybe the wrong region if you don't get ota update notification to b362/b364 when checking for update in settings :
1) What's your build number version on Settings/System/about ?
2) What's the country shown when you dial**#*#2846579#*#**- on the dial pad, then go to 'Network Information Query' and then to 'Vendor Country Info' ?
---------- Post added at 19:44 ---------- Previous post was at 19:42 ----------
Dial**#*#2846579#*#*
---------- Post added at 19:46 ---------- Previous post was at 19:44 ----------
sorry typos.
So dial:
Code:
*#*#2846579#*#*
Click to expand...
Click to collapse
vendor:hw
country:eu
build number:stf-l09 8.0.0.360(c432)~
reflashed b360 and now i get update to b364 on settings. still no capacity buttons..
So, you're fine on C432.
Just flash the B360 kernel fix while you're still on B360 https://forum.xda-developers.com/showpost.php?p=75772700 ;
This will fix your buttons.
You can then do a normal update via settings
ok so i tried to update using vol up + vol down + power button, again it said software install failed
inside those rar file got 2 file, 1 is UPDATE.APP which is 4gb++ and another one is update_STF-L09_hw_eu.app size around 1.4gb.
try update with 4gb file, appear 5% loading and then appear software install failed, same with 1.4gb file...
the only option i got is reboot system now when the error come out..
already did wipe cache & data before i do the update..
any idea? am i doing wrong step?
I have the same problem...When the installation begins, it stops at 5%
My phone is turned off. I tried to install recovery but got nothing
any idea please

Formatting with DLOAD method

Well, i want to exit of the list of safetynet, i tried magisk safetynet fix, nothing works, this happened after a HOTA Downgrade to Nougat because Oreo (EMUI B330) made me lose too much performance of my Mate 10 Lite (RNE-L03C178) and the APi interpreted the downgrade how a dangerous modification of the system for the apps or in other words a cheating action, i want to exit of the list of the api, i listened with a complete format of a device the safetynet will provide the apps (With SafetyNet block) back in Play Store.
Well i want to format my device with the DLOAD method or other method, could someone explain to me how to do it? (the process of the dload)
Sorry for the grand explanation and my too very bad english, my language is spanish...
Koa1 said:
Well, i want to exit of the list of safetynet, i tried magisk safetynet fix, nothing works, this happened after a HOTA Downgrade to Nougat because Oreo (EMUI B330) made me lose too much performance of my Mate 10 Lite (RNE-L03C178) and the APi interpreted the downgrade how a dangerous modification of the system for the apps or in other words a cheating action, i want to exit of the list of the api, i listened with a complete format of a device the safetynet will provide the apps (With SafetyNet block) back in Play Store.
Well i want to format my device with the DLOAD method or other method, could someone explain to me how to do it? (the process of the dload)
Sorry for the grand explanation and my too very bad english, my language is spanish...
Click to expand...
Click to collapse
In theory, you should download the stock rom from here: http://pro-teammt.ru/firmware-database/
Then, unzip the file and copy UPDATE.APP on your SD card. It has to be in a folder named dload on the root of the card.
Afterwards, reboot on download mode (turn off your phone, then, press volume up + volume down + power button until Huawei logo appears). This should trigger the process to install the app UPDATE.APP file.
If you have TWRP recovery, you will need to go back to your stock recovery (on that... please search on this forum).
I hope this helps!
jeinnerabdel said:
In theory, you should download the stock rom from here: http://pro-teammt.ru/firmware-database/
Then, unzip the file and copy UPDATE.APP on your SD card. It has to be in a folder named dload on the root of the card.
Afterwards, reboot on download mode (turn off your phone, then, press volume up + volume down + power button until Huawei logo appears). This should trigger the process to install the app UPDATE.APP file.
If you have TWRP recovery, you will need to go back to your stock recovery (on that... please search on this forum).
I hope this helps!
Click to expand...
Click to collapse
I'm understanding the next step...the download of all 3 files (update.zip and the others files) of a one file and extract it
Because Firmware Finder gives me 3 zip files and i not understand wich of 3 decompress the update.app
Sorry for my english...again...
jeinnerabdel said:
In theory, you should download the stock rom from here: http://pro-teammt.ru/firmware-database/
Then, unzip the file and copy UPDATE.APP on your SD card. It has to be in a folder named dload on the root of the card.
Afterwards, reboot on download mode (turn off your phone, then, press volume up + volume down + power button until Huawei logo appears). This should trigger the process to install the app UPDATE.APP file.
If you have TWRP recovery, you will need to go back to your stock recovery (on that... please search on this forum).
I hope this helps!
Click to expand...
Click to collapse
I listened about to do this with the 3 update.app files
1.-update.zip
2.-update_data_full_public.zip
3.-update_full_RNE-L03_xxxxx_la.zip
Extract their update.app and install in order
Is this correct?
Koa1 said:
I listened about to do this with the 3 update.app files
1.-update.zip
2.-update_data_full_public.zip
3.-update_full_RNE-L03_xxxxx_la.zip
Extract their update.app and install in order
Is this correct?
Click to expand...
Click to collapse
Update.app in update.zip and update.app in update_full_RNE-L03_xxxxx_la.zip
Unless it's offline firmware it won't install.
And in most cases it's online only.
ante0 said:
Update.app in update.zip and update.app in update_full_RNE-L03_xxxxx_la.zip
Unless it's offline firmware it won't install.
And in most cases it's online only.
Click to expand...
Click to collapse
I install in order specified and finally wipe with erecovery, is this correct?
ante0 said:
Update.app in update.zip and update.app in update_full_RNE-L03_xxxxx_la.zip
Unless it's offline firmware it won't install.
And in most cases it's online only.
Click to expand...
Click to collapse
And the last question...
What is the diference of a Online Firmware and a Offline Firmware?
ante0 said:
Update.app in update.zip and update.app in update_full_RNE-L03_xxxxx_la.zip
Unless it's offline firmware it won't install.
And in most cases it's online only.
Click to expand...
Click to collapse
Nothing, i resolved it, thanks very much!
ante0 said:
Update.app in update.zip and update.app in update_full_RNE-L03_xxxxx_la.zip
Unless it's offline firmware it won't install.
And in most cases it's online only.
Click to expand...
Click to collapse
I tried to install it, it stucks at 5% and error message, what i do? Please help...
(Huawei MATE 10 ALP-L09) Hello, I tell you my situation, I am in the emui 8 version with cust 432 in the 150 sp1 version (xloader 1).
I want to try emui 9 so I'm going to switch to xloader 2.
I have the bootloader open and I'll leave it like this to update manually.
I'm going to use the HWOTA system, but when downloading the files of the latest version of emui 9 (version 159) I realize that 3 * .zip files are no longer the same as before, now only 2 files form it. The steps are the same? I put those two files in the Repack folder and then I go to the Ota folder and run the ota.bat ??
And another thing, should we rename those two files as was done before?
Thank you. A greeting.
Koa1 said:
I tried to install it, it stucks at 5% and error message, what i do? Please help...
Click to expand...
Click to collapse
quite old topic i know but i faced the same problem here with my mediapad now. copied all files and update.app to sd card under dload folder but got the error message at 5 percent. there was any solution for this?
artifexor said:
quite old topic i know but i faced the same problem here with my mediapad now. copied all files and update.app to sd card under dload folder but got the error message at 5 percent. there was any solution for this?
Click to expand...
Click to collapse
From dload folder you can flash Service ROM only,
you can download the S. ROM here:
https://androidhost.ru/search.html
Follow the instructions in "ReleaseDoc" . GL!
Warning: this process will erase all the data from your device!!!
bozka1 said:
https://androidhost.ru/search.html
Click to expand...
Click to collapse
Thank you very much! This site contains only service ROM? I have not found any explicit service ROM just regular looking ROM file and some repair ROM but for different region and with password. My current ROM version is BTV-DL09C100B311.
artifexor said:
Thank you very much! This site contains only service ROM? I have not found any explicit service ROM just regular looking ROM file and some repair ROM but for different region and with password. My current ROM version is BTV-DL09C100B311.
Click to expand...
Click to collapse
Yes, only service and board ROM.
Explicit service ROM for your device/ROM version :
https://androidhost.ru/8Xg
bozka1 said:
Yes, only service and board ROM.
Explicit service ROM for your device/ROM version :
https://androidhost.ru/8Xg
Click to expand...
Click to collapse
Is there any service ROM for RNE-L03C178 or C605? I’ve been searching a lot, and well I don’t find anything. And sorry to answer to this old post
Koa1 said:
Is there any service ROM for RNE-L03C178 or C605? I’ve been searching a lot, and well I don’t find anything. And sorry to answer to this old post
Click to expand...
Click to collapse
Enjoy
C605
https://androidhost.ru/311B
https://androidhost.ru/afs
https://androidhost.ru/7AU
C178 (paid service, 17euros )
https://easy-firmware.com/index.php?a=downloads&b=file&id=173660
https://easy-firmware.com/index.php?a=downloads&b=file&id=150819
bozka1 said:
Yes, only service and board ROM.
Explicit service ROM for your device/ROM version :
https://androidhost.ru/8Xg
Click to expand...
Click to collapse
bozka1 said:
Enjoy
C605
https://androidhost.ru/311B
https://androidhost.ru/afs
https://androidhost.ru/7AU
C178 (paid service, 17euros )
https://easy-firmware.com/index.php?a=downloads&b=file&id=173660
https://easy-firmware.com/index.php?a=downloads&b=file&id=150819
Click to expand...
Click to collapse
Thanks! But, do you have the one for Android 7.0?
Koa1 said:
Thanks! But, do you have the one for Android 7.0?
Click to expand...
Click to collapse
For A 7 I don’t find anything on androidhost.ru , try
https://easy-firmware.com/index.php?a=downloads&b=folder&id=31285&p_start=1 .
P.S.: If I may ask, why A7 ?
bozka1 said:
For A 7 I don’t find anything on androidhost.ru , try
https://easy-firmware.com/index.php?a=downloads&b=folder&id=31285&p_start=1 .
P.S.: If I may ask, why A7 ?
Click to expand...
Click to collapse
Because Android 8 in this phone works bad and slow
Koa1 said:
Because Android 8 in this phone works bad and slow
Click to expand...
Click to collapse
Okay, but if You now running A8 , You can downgrade to A7 using HiSuite (Update > Other version) , or, if You have TWRP on board, You can downgrade flashing A7 firmware via HuRupdater 0.4 . It's strongly not recommended downgrade via dload method, it may brick Your phone.

Images for Nokia 3.2 [Magisk][System and User Images]

Hello,
I've uploaded some image files for Nokia 3.2 and want to share them.
I've packed some images for Nokia 3.2 00WW variant (e.g. Magisk, fastboot ROM) and will upload user images for the 00EEA variant, too.
It just needs some more time to upload completely.
EDIT: I transfered all the files to Mega.nz
https://mega.nz/folder/hVMTiCbT#OhmmxhtKabnNn2hWfiIgHQ
P.S. if someone has the european Variant and wants to provide matching Magisk Patched boot images just send me a link to those and i will add them to my Mega.nz folder
Hello,
i just uploaded the patched boot image december 2019 for the europe 00EEA version in other thread under https://forum.xda-developers.com/attachment.php?attachmentid=4929795&d=1579367908.
Perhaps you can add it to your google drive.
Greetings
Hi, sorry i didnt see it. Could you created a Copy of it with dm-verity disabled? You can do it with superr's kitchen. So that we have a magisk Image for GSIs.
Thanks
P.S. i will Upload the magisk patched image tomorrow.
EDIT: I can Just remove dm verity on my own. :silly:
I've created a Telegram Channel for Nokia 3.2
Updates regarding Source Code, the Google Drive mirror (magisk stuff,Firmwares etc.) And any helpful information will be posted by me on the Channel.
Note information inside ReadMe file on the Google Drive link
TA-1156 Qcn
Hello, can you upload Nokia 3.2 TA-1156 models qcn file?
accidentally delete all partitions and now i want to restore imei numbers and serial number to get the mobile network
chinovaso said:
Hello, can you upload Nokia 3.2 TA-1156 models qcn file?
accidentally delete all partitions and now i want to restore imei numbers and serial number to get the mobile network
Click to expand...
Click to collapse
Hi I don't have any qcn file. My Nokia 3.2 is currently being repaired. But I've found a tool what could help you.
https://www.getdroidtips.com/download-imei-qcn-tool/
Just test it and look if it works
chinovaso said:
Hello, can you upload Nokia 3.2 TA-1156 models qcn file?
accidentally delete all partitions and now i want to restore imei numbers and serial number to get the mobile network
Click to expand...
Click to collapse
Thank you s3tupw1zard, but I try this tool already, it works , *06# when it checks it shows the imei numbers but there still no a gsm signal.
Also the serial number is shown as 012345678E0000 and in *#*#4636#*#* servise menu when i chek says Mobile radio is oFF
How to flash using fastboot
Hey mate
Can u guide me through flashing magisk boot img
Im kinda of confused becoz of A B partitions
Any detailed guide would be appreciated
Im on latest January update 2020
Nokia 3.2 (deadpool)
chinovaso said:
Thank you s3tupw1zard, but I try this tool already, it works , *06# when it checks it shows the imei numbers but there still no a gsm signal.
Also the serial number is shown as 012345678E0000 and in *#*#4636#*#* servise menu when i chek says Mobile radio is oFF
Click to expand...
Click to collapse
Hi,
I can't help you in this case. Best would be if you send it in.
You can get your imei with 'fastboot getvar all' (without quotes) to send it in.
You need the imei for sending it in. Dont worry about warranty the ar not allowed anymore to denying warranty due to new google terms.
Just go to nokia website and order a repair.
No0bGuy said:
Hey mate
Can u guide me through flashing magisk boot img
Im kinda of confused becoz of A B partitions
Any detailed guide would be appreciated
Im on latest January update 2020
Nokia 3.2 (deadpool)
Click to expand...
Click to collapse
I write a short guide into a new thread. I pack some files for gsi flashing together.
You will find this guide in about 30 Minutes on the Nokia 3.2 Guides section
Hello,
i uploaded the january 2020 patched boot.img for the European 00EA with dm-verify=off.
Please include on your googledrive!
https://forum.xda-developers.com/attachment.php?attachmentid=4956671&d=1582404743
Greetings
Using these images
Hi All
i've bought a Nokia 3.2 for installing lineageOS ! So i could unlock it and installed this ASOP-Image (probably the 00WW-Version) thru ADB and fastboot with the result to get a crappy OS without WiFI.
At the end i needed about 10 days to get a connection (probably thru qualcomm-drivers) to the pc again, where i can use your (hopefully working) images.
In order to avoid a malfunctioning NOKIA, i am asking about the right way to install the 00EA-Version:
Again i can use adb and fastboot, so first step is to use flash-user-bin.bat for flashing boot.bin, dtbo.bin, system.bin, vendor.bin and vbmeta.bin !
Now there should be a working OS with WiFI, second step would be patching boot_jan2020_dmOFF_00EA.img and third step patching twrp-3.2-dpl-00eea.img.
At last it should be possible to install LineAgeOS thru Magisk Manager (or CWM) ?
Thanks for your advices
Your device needs the images with the same version. So boot.img from January combined with firmware from December lead into bugs like WiFi not working. Reboot to bootloader, there is a info where either 00WW (international Variant) or 00EEA (European Variant) is written. I've uploaded a GSI base for both variants on the Google drive Link at the beginning of this thread. You can find both base 7z Files Inside GSI folder. But be sure which Variant you have. After executing flash-all.bat execute the other bat file (it will flash magisk patched img with dm-verity removed) and after that finishes you can flash any GSI to system.
And you can't install ROMs through Magisk. It is Superuser. You need to be in Bootloader mode.
And USB debugging needs to be on and your PC needs to be authorized by your device. Just activate USB debugging in developer options and type adb devices. There should appear a prompt.
thx
for fast reply. It should be 00EEA, because i've bought it in Austria. I think, i have seen it in the settings/my phone too.
So i will use the GSI-Version tomorrow. With Magisk-Manager i should could load this TWRP-Image (on a SD-Card) too ?
Stupid Question: what is the meaning of the shortciut GSI ?
Regards
other bat-file
s3tupw1zard said:
Your device needs the images with the same version. So boot.img from January combined with firmware from December lead into bugs like WiFi not working. Reboot to bootloader, there is a info where either 00WW (international Variant) or 00EEA (European Variant) is written. I've uploaded a GSI base for both variants on the Google drive Link at the beginning of this thread. You can find both base 7z Files Inside GSI folder. But be sure which Variant you have. After executing flash-all.bat execute the other bat file (it will flash magisk patched img with dm-verity removed) and after that finishes you can flash any GSI to system.
Click to expand...
Click to collapse
Hi s3tupw1zard !
where is this other bat-File ? This GSI (generic system image)-Folder of 00EEA is empty, but i've used user_images_00EEA.7z and this is working perfectly.
In spite of it i would like to change booting (with magisk-patched.img). but this is existing for 00WW only. I've tried to flash twrp-Image too, but there i've got errors, so i've flashed user_images_00EEA completely again.
Thanks for your work
At last
i could create something, but still there is something missing !
I've downloaded boot_nodm_magisk_patched.img from shared googleDrive and patched it with MagiskManager.
Unfortunelately i tried to flash this file without renaming - so i had to reset to factory settings, because booting was not working.
After that, i was remembering to rename this boot-file to boot.img, flashed to factory new system - following flashing the system with LineAgeOS from Andy - https://sourceforge.net/projects/andyyan-gsi/files/lineage-17.x/ (renamed it to system.img)
The result: booting procedure for working LineAgeOS needs about 5 minutes and wifi is missing !
Does anyone have a clue ?
Do i need to setup system with user-Image (December 2019) from Manuels Google Drive before ?
ThankYou for advices
Gerhard
Then you flashed the wrong boot.img.
You must look for your Version - 00WW or 00EEA - and you must have the corresponding security level to your firmware, means January or December ........
00ww - 00eea
page1875 said:
Then you flashed the wrong boot.img.
You must look for your Version - 00WW or 00EEA - and you must have the corresponding security level to your firmware, means January or December ........
Click to expand...
Click to collapse
thanks for reply.
If i am lucky, i will use boot_jan2020_dmOFF_00EA.img next time - but for now i have (possibly) corrupted partition table file and so device is ended in a fastboot-mode loop - Android ONE Logo flashes up less than 1 second
So hopefully with fastboot flash partition Firmware\gpt_both0.bin (gpt_both0.bin from Nokia_3.2_TA-1156_HMDSW_DPL_015B-0-00WW-B01_QFIL) i can restore partition table file in spite of this 00WW-Version.
Does anyone have seen firmware for 00EEA-Version ?
cheers
Idiots Guide
The reason for infinite bootloop and ADB-Flash error messeage 'FAILED (remote: partition table doesn't exist)' may be (as i remember) is to rename boot.bin from user_images_00EEA of our wizard to boot.img.
Resetting to factory defaults is not possible anymore - so beware of it !

Categories

Resources