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 !
Related
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!
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.
Hello guys i rooted the nokia 3.2 with magisk by patching the boot.img and flash it using adb , younhave to unlock the bootloader which is very simple have just to enable developers options and then enable oem unlocking after that enter fastboot mode and open a powershell comand and type fastboot oem unlock and hit enter a message will apear n ur phone then select unlock bootloader with volume records and power buton to confirm , then copy the patched boot.img to the same folder as adb wich is located onthe local C/adb and the type fastboot flash boot boot.img and voila
patched boot.img :
https://mega.nz/#!XJVGiYCA!bp3shLR24J7WFZ7hxft-8LSD2fhKkw6nCvdOKcU1j0w
bouyhy01 said:
Hello guys i rooted the nokia 3.2 with magisk by patching the boot.img and flash it using adb , younhave to unlock the bootloader which is very simple have just to enable developers options and then enable oem unlocking after that enter fastboot mode and open a powershell comand and type fastboot oem unlock and hit enter a message will apear n ur phone then select unlock bootloader with volume records and power buton to confirm , then copy the patched boot.img to the same folder as adb wich is located onthe local C/adb and the type fastboot flash boot boot.img and voila
Click to expand...
Click to collapse
Hi, might be a stupid question but where is the patched boot.img/how do I do it myself?
Craventoby said:
Hi, might be a stupid question but where is the patched boot.img/how do I do it myself?
Click to expand...
Click to collapse
I will upload it, i downloaded the new firmware with june security patch and extracted the boot.img from it, you can do the same or wait when i go home to upload it for you
https://mega.nz/#!XJVGiYCA!bp3shLR24J7WFZ7hxft-8LSD2fhKkw6nCvdOKcU1j0w
Craventoby said:
Hi, might be a stupid question but where is the patched boot.img/how do I do it myself?
Click to expand...
Click to collapse
https://mega.nz/#!XJVGiYCA!bp3shLR24J7WFZ7hxft-8LSD2fhKkw6nCvdOKcU1j0w
enjoy
bouyhy01 said:
Hello guys i rooted the nokia 3.2 with magisk by patching the boot.img and flash it using adb , younhave to unlock the bootloader which is very simple have just to enable developers options and then enable oem unlocking after that enter fastboot mode and open a powershell comand and type fastboot oem unlock and hit enter a message will apear n ur phone then select unlock bootloader with volume records and power buton to confirm , then copy the patched boot.img to the same folder as adb wich is located onthe local C/adb and the type fastboot flash boot boot.img and voila
patched boot.img :
Click to expand...
Click to collapse
Hey, I did root my phone with that but the wifi doesn't seem to work anymore.. do you have the same issue or/and do you have the stock boot.img file that I can try to flash ?
Thanks !
Hironichu said:
Hey, I did root my phone with that but the wifi doesn't seem to work anymore.. do you have the same issue or/and do you have the stock boot.img file that I can try to flash ?
Thanks !
Click to expand...
Click to collapse
https://mega.nz/#!6nJhQKba!XylZfJqVyRCXdIzZnVbhwhQFs5arpPf6Cg36mR0L9_Q
Hironichu said:
Hey, I did root my phone with that but the wifi doesn't seem to work anymore.. do you have the same issue or/and do you have the stock boot.img file that I can try to flash ?
Thanks !
Click to expand...
Click to collapse
Small update on this, there was an Android update recently, and it fixes everything ??* so if someone else here has the same issues somehow, updating to July update fixes it
I've some questions:
-does Nokia release his kernel source and which version use? on their website there is only for 3.1 I don't know if are same thing.
-Does support treble?
hello, now there is a august update for nokia 3.2 Do u have the boot file for that.. or how can I find it??
I add this phone to the list of my amazon.it account to make some stuff like twrp and roms but didn't buy yet, I'm afraid that Nokia will not release kernel source soon so in case of taking one I can make a twrp with stock kernel extracted from boot.img see ya.
Edit: buying this phone has been cancelled after reading unlocking bootloader seems to be "impossible" shame on you dear Nokia
disy
bouyhy01 said:
Hello guys i rooted the nokia 3.2 with magisk by patching the boot.img and flash it using adb , younhave to unlock the bootloader which is very simple have just to enable developers options and then enable oem unlocking after that enter fastboot mode and open a powershell comand and type fastboot oem unlock and hit enter a message will apear n ur phone then select unlock bootloader with volume records and power buton to confirm , then copy the patched boot.img to the same folder as adb wich is located onthe local C/adb and the type fastboot flash boot boot.img and voila
patched boot.img 8LSD2fhKkw6nCvdOKcU1j0w"]https://mega.nz/#!XJVGiYCA!bp3shLR24J7WFZ7hxft-8LSD2fhKkw6nCvdOKcU1j0w[/URL]
Click to expand...
Click to collapse
Good afternoon, I HAVE BY THIS METHOD THE PHONE IN THE LOADER HANGED, HELP TO RETURN TO THE OPERATIONAL CONDITION.
bouyhy01 said:
Hello guys i rooted the nokia 3.2 with magisk by patching the boot.img and flash it using adb
Click to expand...
Click to collapse
Can you tell what your current build number is?
I suspect there is more than one firmware flavor around.
Thanks!
.
JFDee said:
Can you tell what your current build number is?
I suspect there is more than one firmware flavor around.
Thanks!
.
Click to expand...
Click to collapse
i dont know coz i sold the phone months ago but i managed to root it without problems you have just to patch it by your self with your current build and then flash it using fastboot mode
bouyhy01 said:
i dont know coz i sold the phone months ago but i managed to root it without problems you have just to patch it by your self with your current build and then flash it using fastboot mode
Click to expand...
Click to collapse
Thanks for replying!
Unfortunately, I don't have my current build as a separate firmware file, and QFIL is not able to get the boot image from my phone because the communication stops right away.
My build number starts with 00EEA, whereas your boot image (and the full stock ROM on Mega that you linked) contains 00WW. I'm not sure this firmware is compatible with my Nokia 3.2 ...
.
JFDee said:
Thanks for replying!
Unfortunately, I don't have my current build as a separate firmware file, and QFIL is not able to get the boot image from my phone because the communication stops right away.
My build number starts with 00EEA, whereas your boot image (and the full stock ROM on Mega that you linked) contains 00WW. I'm not sure this firmware is compatible with my Nokia 3.2 ...
.
Click to expand...
Click to collapse
if you have a link for the whole firmware i can download it and extract the boot.img for you and then upload it i do have a gigabit internet speed
bouyhy01 said:
if you have a link for the whole firmware i can download it and extract the boot.img for you and then upload it i do have a gigabit internet speed
Click to expand...
Click to collapse
Thanks!
I've looked around and so far could not find the stock firmware for my phone.
If I had it, I'm sure I could manage to extract the boot.img and let Magisk patch it (I've done that before with other devices).
JFDee said:
Thanks!
I've looked around and so far could not find the stock firmware for my phone.
If I had it, I'm sure I could manage to extract the boot.img and let Magisk patch it (I've done that before with other devices).
Click to expand...
Click to collapse
i found it but its a .bin
bouyhy01 said:
i found it but its a .bin
Click to expand...
Click to collapse
Thanks for your efforts - I was able to solve the problem today.
It seems there are different versions of the same "programmer" around that is used in QFIL to extract your own boot image from the phone.
Originally, I used the one provided by @hikari_calyx in his unlock thread. Today I noticed that the programmer file in the stock firmware you provide here has a slightly different size. I tried this one and it worked.
So I could extract my "boot.img" from the phone. Rooting was easy after that.
I think it's always safer to use one's own boot image than trying to flash one that was lying around elsewhere.
Here is my post in the other thread for reference. Thanks again for your research and for providing the stock firmware!
.
Hello JFDee,
is it possible that you upload your original or modified boot image also?
Because i flashed the boot image that was given here and now i have the same problem, like said before.
WLAN is not working anymore and the Boot time is very long. Updating also don't work.
I also saw the differences in the build numbers.
My is like yours 00EEA....
This would be really nice, because i don'T find the stock image for this number.
Best regards!!!!
JFDee said:
Thanks for your efforts - I was able to solve the problem today.
It seems there are different versions of the same "programmer" around that is used in QFIL to extract your own boot image from the phone.
Originally, I used the one provided by @hikari_calyx in his unlock thread. Today I noticed that the programmer file in the stock firmware you provide here has a slightly different size. I tried this one and it worked.
So I could extract my "boot.img" from the phone. Rooting was easy after that.
I think it's always safer to use one's own boot image than trying to flash one that was lying around elsewhere.
Here is my post in the other thread for reference. Thanks again for your research and for providing the stock firmware!
.
Click to expand...
Click to collapse
I can add your Moto e6 on here if you send me a copy of your recovery.img so o can port it it only takes me a few minutes now to port to new device I will be uploading more this weekend if you want one for your device send me your recovery.img and I will port it to you real fast
Thanks to A-Team Digital for all there help
This certainly works with usb mouse plugged into usb port. No touch otherwise.
I need 2 files from your device to get touch working
Let me know which ones and I will send them to you. Thanks.
Pick the 2 you need from these files
What carrier do you have what is the model number o have all the files I just need to know the model number and carrier please
I'm repacking a universal one with all the files for all models and carriers right now give me a little bit and I should have it uploaded
I have it built but can't upload it here too big of files in total it is just over 3gb but it adds something's to the system so you don't have to boot into recovery to get root and you have rw access in twrp and Android if you have a telegram let me know and I can send you the files on there if you like
If not I'm uploading them to google drive right now
I got the download size down to 1.6gb zipped and 3.3gb unziped that have to be flashed please read readme.txt
Here is the link to google drive it has 2 zip files download both and it has all the files you need to flash to device
Moto e6 - Google Drive
drive.google.com
Sorry for delay in getting back to you. First, I downloaded the zip files and the readme. Thank you. Second I have the latest version of the T-Mobile Rom, which, I believe, is very similar, if not identical to, the MetroPCS version you have. I will check out the readme file and let you know how it goes. Thanks again.
Okay. I reviewed your zip files and they are the ones from AIO. I looked at all of these files before and decided not to install them since it prohibited upgrading the firmware in the future. If these are required to have a touch-friendly TWRP recovery, then I will pass. I like my Moto E6 security updates too much. By the way, I admire the A-Team work.
They are not the same as there's I added the ability to update you just have to use magisk and go to update in settings and keep magisk after update you can get security updates for a while but moto is stoping updates on that phone next month
I just added a few lines to allow security updates because I started with there base and needed updates for my work phone
I change a few files in the recovery file but twrp will have touch but can not mount as rw or anything no back ups or nothing unless you go my route right now at least you get security updates
Thanks for the explanation. I think I will give it a try.
I tried it and I am now running my T-Mobile version fully rooted with a fully operating TWRP touch working recovery!
The system.img would not install, and that was a very good thing. It was not needed. Everything works. I have done full backups, including non-encrypted data, using the Batik-TWRP. I did update to Magisk 23 and that worked just fine as well. Thank you so much for finally giving us a way to fully root and backup this phone!
You are welcome sir Al software updates will work just remember to go in magisk manger and keep magisk after update
I have two moto e6:
1. XT2005-5 RETCA (bootloader unlocked & rooted with Magisk, but via recovery only)
2. XT2005-1PP Verizon version (Brand new state. Not even activated. But fastboot is available).
Both are with the newest stock rom for their channel (rescued by LMSA).
I followed the readme, but fastboot could not flash any image.
I got error like this:
Sending 'boot' (32768 KB) OKAY [ 1.279s]
Writing 'boot' (bootloader) Image boot failed validation
(bootloader) Preflash validation failed
FAILED (remote: '')
fastboot: error: Command failed
Can you make images if I upload boot, dbt, recovery?
Or can you show instruction to patch/modify images?
Also, I have tried to flash the stock ROM from RECTA onto Verizon version but failed (went into fastboot loop).
Then I tried to falsh back stock Verizon ROM, and failed, as well.
Yet, LMSA could flash the stock Verizon ROM.
Maybe we can copy patched images into LMSA Download folder (C:\ProgramData\LMSA\Download\RomFiles), over the stock ROM, and let it flash for us (probably depending on the "Preflash validation").
Received the tablet in the mail, and now looking to root via Magisk (and ideally a custom recovery like TWRP).
I found this video describing a way to download the stock ROM from Teclast:
Has anyone achieved root on this device? Can anyone confirm Treble ROM compatability for GSI A/B?
On the russian forum 4pda somebody posted the patched boot.img and vbmeta.img files required for rooting.
If anyone is registered on the forum he might try to grab the files, for me it gives 404 error when trying to download, though im not registered..
Teclast T40 Plus - Обсуждение - 4PDA
Teclast T40 Plus - Обсуждение, Планшет, 10,4
4pda.to
NightLord said:
On the russian forum 4pda somebody posted the patched boot.img and vbmeta.img files required for rooting.
If anyone is registered on the forum he might try to grab the files, for me it gives 404 error when trying to download, though im not registered..
Teclast T40 Plus - Обсуждение - 4PDA
Teclast T40 Plus - Обсуждение, Планшет, 10,4
4pda.to
Click to expand...
Click to collapse
Good find, but the link no longer works. It gives me a 404: https://4pda.to/forum/dl/post/24458874/T40_Plus_root.7z
My guess is it would work if we were logged in, its just that i cant create an account since i cannot get past rhe russian captcha
Yeah, I also can't register without knowing the Russian keyboard layout and how to identify the characters. Perhaps someone with this knowledge can register and attach the required images to root here?
Slightly off topic while someone manages to grab the files from 4pda
Do you actually get 50000+ gpu score in antutu with the t40? I have the maxpad i11 which is in theory the same hardware, and I only get 42000. I even flashed the t40 firmware on the device, but gpu score didnt budge.
To be on topic: if you want root, you may also flash phhuson's treble GSI rom-s. I tried his version of android 12, and it works, and has root.
NightLord said:
Slightly off topic while someone manages to grab the files from 4pda
Do you actually get 50000+ gpu score in antutu with the t40? I have the maxpad i11 which is in theory the same hardware, and I only get 42000. I even flashed the t40 firmware on the device, but gpu score didnt budge.
To be on topic: if you want root, you may also flash phhuson's treble GSI rom-s. I tried his version of android 12, and it works, and has root.
Click to expand...
Click to collapse
These ROMs? https://github.com/phhusson/treble_experimentations/releases
ForgottenSolstace said:
These ROMs? https://github.com/phhusson/treble_experimentations/releases
Click to expand...
Click to collapse
Yes.
You can either install them via DSU as dual-boot OS beside your stock rom, or just flash system partition (inside super) via fastbootd (you are going to have to delete product partition to have enough space inside super for the system image) and use them as primary OS.
Gotcha:
Just ordered a T40 Plus, did you manage to get root?
Flashing the boot and vbmeta partitions with the images attached to my previous post will grant you root on the stock t40 plus firmware.
I myself moved on to using android 12 gsi images.
NightLord said:
Flashing the boot and vbmeta partitions with the images attached to my previous post will grant you root on the stock t40 plus firmware.
I myself moved on to using android 12 gsi images.
Click to expand...
Click to collapse
Hi NightLord, can you explain easily the root steps for this device? do we need the software that we see in the video at the beginning or is ADB enough?
Marynboy78 said:
Hi NightLord, can you explain easily the root steps for this device? do we need the software that we see in the video at the beginning or is ADB enough?
Click to expand...
Click to collapse
Hey,
You need to use the spreadtrum research download tool (RDT), not the one seen in tthe video in the first post.
See this guide on how to use the RDT.
The basic concept is that you need to download the official firmware from the teclast homepage, load it into RDT, uncheck all partitions (save for those that are compulsory and cannot be unchecked), select only boot and vbmeta partitions, and as images to be flashed you need to browse the ones found in the archive I posted, instead of those found in the original firmware package.
Begin flashing, your device will perform a hard reset, and then you should boot into rooted firmware.
Theoretically you should be able to flash both partitions (boot and vbmeta) via fastboot too, but when I tried, i got an error message saying boot.img was too large or something. Flashing via RDT went without problem. The only caveat is that flashing via RDT will always hard reset your device.
NightLord said:
Flashing the boot and vbmeta partitions with the images attached to my previous post will grant you root on the stock t40 plus firmware.
I myself moved on to using android 12 gsi images.
Click to expand...
Click to collapse
How to install android 12 gsi on this device?
marinzrncic said:
How to install android 12 gsi on this device?
Click to expand...
Click to collapse
First you need to unlock the bootloader. You need to be patient when you are flashing the unlock, my device took some 10 mins to complete, but in the end it succeeded (on the 2nd try, mind you.)
Here is a guide for unlocking in windows, though it is in russian (Im attaching the required modified fastboot in case you cannot download it from 4pda).
When you're done unlocking the bootloader, you've already done the hard part.
Next, download your preferred GSI image from Google, from phhusson's, or whatever else you find (Pixel Experience for eg.). Mind you, that the image from Google contains the Android 12L version.
Next you will flash your active system partition with the GSI image. To do that, initate ADB connection to your tablet, then enter fastbootd, by issuing the command:
fastboot reboot fastboot
you can check your active system slot by:
fastboot getvar all (but it will be slot "a" unless you have received an OTA update previously)
you need to free up some space by deleting the logical partition product otherwise you wont be able to flash your gsi:
fastboot delete-logical-partition product_a
(in case your active slot is "a")
then you can move forward to actually flashing your GSI:
fastboot flash system_a whateverisyourimagefilename.img
Lastly, you will need to wipe userdata, which can be done on the tablet by switching to recovery from fastbootd, and then selecting wipe userdata, or maybe the fastboot -w command does the same.
Reboot, and enjoy your GSI.
I'm using the Google 12L GSI, and it is perfectly stable for daily usage. For bluetooth audio to work, you will have to disable bluetooth a2dp hardware offload in developer options.
NightLord said:
First you need to unlock the bootloader. You need to be patient when you are flashing the unlock, my device took some 10 mins to complete, but in the end it succeeded (on the 2nd try, mind you.)
Here is a guide for unlocking in windows, though it is in russian (Im attaching the required modified fastboot in case you cannot download it from 4pda).
When you're done unlocking the bootloader, you've already done the hard part.
Next, download your preferred GSI image from Google, from phhusson's, or whatever else you find (Pixel Experience for eg.). Mind you, that the image from Google contains the Android 12L version.
Next you will flash your active system partition with the GSI image. To do that, initate ADB connection to your tablet, then enter fastbootd, by issuing the command:
fastboot reboot fastboot
you can check your active system slot by:
fastboot getvar all (but it will be slot "a" unless you have received an OTA update previously)
you need to free up some space by deleting the logical partition product otherwise you wont be able to flash your gsi:
fastboot delete-logical-partition product_a
(in case your active slot is "a")
then you can move forward to actually flashing your GSI:
fastboot flash system_a whateverisyourimagefilename.img
Lastly, you will need to wipe userdata, which can be done on the tablet by switching to recovery from fastbootd, and then selecting wipe userdata, or maybe the fastboot -w command does the same.
Reboot, and enjoy your GSI.
I'm using the Google 12L GSI, and it is perfectly stable for daily usage. For bluetooth audio to work, you will have to disable bluetooth a2dp hardware offload in developer options.
Click to expand...
Click to collapse
thank you very much
NightLord said:
Hey,
You need to use the spreadtrum research download tool (RDT), not the one seen in tthe video in the first post.
See this guide on how to use the RDT.
The basic concept is that you need to download the official firmware from the teclast homepage, load it into RDT, uncheck all partitions (save for those that are compulsory and cannot be unchecked), select only boot and vbmeta partitions, and as images to be flashed you need to browse the ones found in the archive I posted, instead of those found in the original firmware package.
Begin flashing, your device will perform a hard reset, and then you should boot into rooted firmware.
Click to expand...
Click to collapse
Did we need unlock bootloader first or we can flash root without unlock bootloader?
Thx
ardianz said:
Did we need unlock bootloader first or we can flash root without unlock bootloader?
Thx
Click to expand...
Click to collapse
I have no idea because I havent tried yet. But I would guess it might be possible that you can flash the patched boot.img along with vbmeta.img with RDT, and it might work, if they do pass Android Verified Boot check.
NightLord said:
Gotcha:
Click to expand...
Click to collapse
will these files work on android 10 or android 11? I have a unisoc T618 and unisoc T310. I was hoping to flash both tablets to get root access.
and also do you have a twrp for T40_plus or any unisoc generic twrp?