Magisk has officially landed on the lovely Treble enabled Huawei devices! Props to Huawei reaching out and sent me a device for development
Instead of holding it off and wait till the next proper release, I decide to release it here so those willing to root their device can give it a try.
These Huawei Treble devices use an interesting setup: it no longer has a boot and recovery partition, but instead has a kernel partition, a ramdisk partition, and a recovery_ramdisk partition. Both boot and recovery share the same kernel, but with separate ramdisks on separate partitions. Since Magisk modifies the ramdisk in boot images, the patches will have to be applied to the ramdisk partition. This nature will very likely to also slightly change how custom recovery will be installed, my bet is similar to Pixel devices which ships with a full ramdisk image, and should be flashed to the recovery_ramdisk partition.
This build is only tested with Honor View 10, but it should work with Mate 10 and Mate 10 Pro in theory since these devices are very similar.
Enough of the rambling, let's get right into it!
Instructions
If your device have TWRP support, just directly flash it via TWRP. For devices without TWRP yet (currently all Huawei Treble devices), you can follow the instructions below:
Install latest Magisk Manager from the Official Thread
Go to Settings > Update Settings > Update Channel > Custom, and insert the following URL: https://goo.gl/jefZKH
Follow the instructions of "Install Via Magisk Manager" in the main thread, but instead of providing the boot image (which these devices do NOT have), provide the stock ramdisk.img.
If you are using EU View 10 with model BKL-L09, you can download the stock ramdisk.img I extracted from official OTAs in the attachments
If you have stock ramdisk images for other devices, please share them and I'll add them to the OP.
Make sure you are installing Magisk-v15.4(1541), which is only available through the custom channel you've set in step 2.
Pull the patched image with adb pull /sdcard/MagiskManager/patched_boot.img, and flash the patched ramdisk via fastboot:
fastboot flash ramdisk patched_boot.img
Reboot and you shall have a properly rooted device passing SafetyNet, start playing with some Magisk modules!
Donation
https://www.paypal.me/topjohnwu
topjohnwu said:
Magisk has officially landed on the lovely Treble enabled Huawei devices! Props to Huawei reaching out and sent me a device for development
Instead of holding it off and wait till the next proper release, I decide to release it here so those willing to root their device can give it a try.
These Huawei Treble devices use an interesting setup: it no longer has a boot and recovery partition, but instead has a kernel partition, a ramdisk partition, and a recovery_ramdisk partition. Both boot and recovery share the same kernel, but with separate ramdisks on separate partitions. Since Magisk modifies the ramdisk in boot images, the patches will have to be applied to the ramdisk partition. This nature will very likely to also slightly change how custom recovery will be installed, my bet is similar to Pixel devices which ships with a full ramdisk image, and should be flashed to the recovery_ramdisk partition.
This build is only tested with Honor View 10, but it should work with Mate 10 and Mate 10 Pro in theory since these devices are very similar.
Enough of the rambling, let's get right into it!
Instructions
If your device have TWRP support, just directly flash it via TWRP. For devices without TWRP yet (currently all Huawei Treble devices), you can follow the instructions below:
Install latest Magisk Manager from the Official Thread
Go to Settings > Update Settings > Update Channel > Custom, and insert the following URL: https://goo.gl/jefZKH
Follow the instructions of "Install Via Magisk Manager" in the main thread, but instead of providing the boot image (which these devices do NOT have), provide the stock ramdisk.img.
If you are using EU View 10 with model BKL-L09, you can download the stock ramdisk.img I extracted from official OTAs in the attachments
If you have stock ramdisk images for other devices, please share them and I'll add them to the OP.
Make sure you are installing Magisk-v15.4(1541), which is only available through the custom channel you've set in step 2.
Pull the patched image with adb pull /sdcard/MagiskManager/patched_boot.img, and flash the patched ramdisk via fastboot:
fastboot flash ramdisk patched_boot.img
Reboot and you shall have a properly rooted device passing SafetyNet, start playing with some Magisk modules!
Donation
https://www.paypal.me/topjohnwu
Click to expand...
Click to collapse
Finally!! [emoji16] was waiting for this.... Thank You.
Sent from my BKL-L09 using Tapatalk
Awesome mate. This also working with Huawei P10 plus running Treble V9. Thank you thank you :good:
Nice! Great job
We can do this follow instructions from completely stock bkl l09 C636? My 1st honor phone.. Not sure it have those locked boot loader like xiaomi or not..
Help..
Hey man, Thanks a lot.. It's really nice to have magisk for v10.. I am kind of a noob.. Can u provide step by step instructions and Patched Img for Indian version BKL-09..
Thanks
does this require an unlocked bootloader?
Root Final Stage issue!
I have done all the steps but on the last stage when I try to flash ramdisk it's giving me an error failed (remote: command not allowed) please help...thanks
Rj_Param said:
I have done all the steps but on the last stage when I try to flash ramdisk it's giving me an error failed (remote: command not allowed) please help...thanks
Click to expand...
Click to collapse
This could be due to locked bootloader...
bhargavpa said:
This could be due to locked bootloader...
Click to expand...
Click to collapse
Thanks... Let me try again after unlocking bootloader.
Sent from my BKL-L09 using Tapatalk
Wow, that's freaky fast man.. you are wonderful.
since we don't have official firmware released yet and out of concern I'm asking, is there any chance of bootloop or brick?
I understand it shouldn't be if we follow steps in OP, but sometimes people miss a step or do something else, so what's the worst can we expect?
Narasimha12 said:
Wow, that's freaky fast man.. you are wonderful.
since we don't have official firmware released yet and out of concern I'm asking, is there any chance of bootloop or brick?
I understand it shouldn't be if we follow steps in OP, but sometimes people miss a step or do something else, so what's the worst can we expect?
Click to expand...
Click to collapse
So long as you have a backup of your device's ramdisk image, you should be fine. The ramdisk for the Honor View 10 is attached to the OP.
Does the ramdisk.img work for indian variants?
shihabsoft said:
Does the ramdisk.img work for indian variants?
Click to expand...
Click to collapse
Yes it's working... Just finished installing magisk...so far everything is fine but somehow SafetyNet is not working.
Sent from my BKL-L09 using Tapatalk
Rj_Param said:
Yes it's working... Just finished installing magisk...so far everything is fine but somehow SafetyNet is not working.
Sent from my BKL-L09 using Tapatalk
Click to expand...
Click to collapse
so you unlocked bootloader right? and also any honor features broke??? like camera modes etc etc...and share bootloader unlock process too...
@topjohnwu
Its doesn't work with my twrp 3.2.1-0 for P10plus. A older twrp version works.
It's a twrp version thing or do I need to add something?
Rj_Param said:
Yes it's working... Just finished installing magisk...so far everything is fine but somehow SafetyNet is not working.
Sent from my BKL-L09 using Tapatalk
Click to expand...
Click to collapse
Thanks for letting me know. So what are those software changes happened right after bootloader unlocking?
To install Magisk and gain root in your honor view 10 you have to unlock your bootloader first.
##Please backup your data before proceeding with the process. You will loose all your data if you unlock the bootloader. ##
Please follow below steps to unlock bootloader
1) Create a Huawei ID on this page https://goo.gl/GkkdxE if you don’t have one already.
2) After creating a Huawei id, fill out the details.
3) You will need your phone’s IMEI number, to know that dial * # * # 1357946 # * # * on the dialer app. Fill the required fields and click the Submit button.
4) Save the unlock code you received.
5) Now connect your Honor View 10 to the PC with a USB cable.
6) In the ADB command window, type the following command to boot your Honor View 10 into fastboot mode.
adb reboot bootloader
7) To unlock the bootloader, type the following command and hit Enter. Replace key with the unlock key you’ve previously saved. For example, fastboot oem unlock 44801904392841
fastboot oem unlock [unlock key]
Sent from my BKL-L09 using Tapatalk
FWIW the Honor View 10's ramdisk works on the Huawei Mate 10 Pro. I would definitely not try that with any non-Kirin 970 device, though.
Rj_Param said:
To install Magisk and gain root in your honor view 10 you have to unlock your bootloader first.
##Please backup your data before proceeding with the process. You will loose all your data if you unlock the bootloader. ##
Please follow below steps to unlock bootloader
1) Create a Huawei ID on this page https://goo.gl/GkkdxE if you don’t have one already.
2) After creating a Huawei id, fill out the details.
3) You will need your phone’s IMEI number, to know that dial * # * # 1357946 # * # * on the dialer app. Fill the required fields and click the Submit button.
4) Save the unlock code you received.
5) Now connect your Honor View 10 to the PC with a USB cable.
6) In the ADB command window, type the following command to boot your Honor View 10 into fastboot mode.
adb reboot bootloader
7) To unlock the bootloader, type the following command and hit Enter. Replace key with the unlock key you’ve previously saved. For example, fastboot oem unlock 44801904392841
fastboot oem unlock [unlock key]
Sent from my BKL-L09 using Tapatalk
Click to expand...
Click to collapse
I know the procedure, but once you unlock the bootloader does any security features get disabled? And does it just wipe /data or including the internal storage?
Related
YOU MUST HAVE ACCESS TO TWRP TO PROCEED
THIS WILL NOT WORK IF YOU DON'T HAVE TWRP
I'M NOT RESPONSABLE IF THIS PROCESS CREATED A THERMAL NUCLEAR DEVICE
AND / OR TURN YOU INTO FIRESTORM.
NOT RESPONSABLE IF SOMETHING HAPPEN DURING THIS INSTALLATION OR IF
YOU DO A MISTAKE DURING THIS PROCESS
READ, READ , READ , READ AND BE CAREFULL WITH THE COMMAND LINES
PROCEED ON YOUR OWN RISK
READ, READ, READ BEFORE PROCEEDING....
Hi A7 Users
--------------
Here we are with a new / excited finding ( thanks @Unjustified Dev )for ALL of us A2017U and A2017G (IS GETTING OFFICIAL UNLOCK AND THIS METHOD NOT TESTED YET,ANY VOLUNTEER?)
and is about UNLOCKING the Bootloader for those who are stock B20 or B27 + Lock Booloader.
Only IMPORTANT requirement is you need to have TWRP install, so if you don't have TWRP install here is the link
and you just NEED TO INSTALL TWRP and if you haven't back-up your STOCK boot.img is the right time to do so
Click Here on How to Flash TWRP with Lock Bootloader, Thank You @tennear
NOTE : THIS PROCEDURE WILL ERASE , I REPEAT WILL ERASE YOUR DATA + INTERNAL STORAGE.
SDCARD IS SAFE.
Steps :
---------
1- Download this File TWRP_UnlockBootloaderPackage_by_DrakenFX.zip and move to your SDCard.
2- Enable "OEM UNLOCKING" under Developer Options
3- Reboot to TWRP
Code:
adb reboot recovery
4- Lets make sure your device is detected
Code:
adb devices
Great let keep going.
5- Open Command and navigate to your adb location.
6- Type the following
* BACK-UP AND PULL CURRENT FASTBOOT IMAGE
Code:
adb shell dd if=/dev/block/bootdevice/by-name/fbop of=/sdcard/fbop_lock.img
adb pull /sdcard/fbop_lock.img
* FLASH TWRP_UnlockBootloaderPackage_by_DrakenFX.zip
Awesome you have backup and flash the bootloader unlock package file but wait we're done yet
7- Type the Following
Code:
adb reboot bootloader
8- Lets make sure device is present
Code:
fastboot devices
9- Now let's Unlock the Bootloader (THIS WILL WIPE DATA+INTERNAL STORAGE)
Code:
fastboot oem unlock
10- You'll boot in TWRP once there do the following :
Code:
* tap [B]CANCEL[/B]
* tap [B]WIPE [/B]
* tap [B]FORMAT DATA[/B] and Follow the Instructions
11- Once done REBOOT
12- WHEN FULL BOOT GO BACK TO TWRP AND CREATE A BACK-UP AND KEEP IT SAFE
13- Have Fun you're now Bootloader Unlock With Stock B20 or B27 Software.
---------------------------------------------------------------------------------------
NOTE : A2017U.B27 Users Everytime you BOOT to System , Recovery, etc, etc you'll be getting a splash screen, JUST WAIT 5 SEC. and your device will boot to where you want to go.
---------------------------------------------------------------------------------------
If You Have the A2017G version and you are already on B03 you can follow step by @Starvirus
A2017G_B03 Unlock Bootloader Steps
---------------------------------------------------------------------------------------
CREDIT / Contributor
- @Unjustified Dev for testing in his Brand New just less than 3 hrs old A2017U and popping up in me the idea about this finding
- Thank you @regenwurm16 for Confirm New method working for A2017G
- Thank you @Starvirus for provide B03 steps
---------------------------------------------------------------------------------------
reserve 1
reserve 2
reserve 3
Mine
So.. this means unlocked bootloader for full flexibility but also OTA updates because it's still running stock?
So jelly. Stuck on B20_boot over here.
jpde said:
So.. this means unlocked bootloader for full flexibility but also OTA updates because it's still running stock?
Click to expand...
Click to collapse
about right, as long you have an Untouch/UnModded System + boot, so yeah
runderekrun said:
So jelly. Stuck on B20_boot over here.
Click to expand...
Click to collapse
@Unjustified Dev is uploading something that will help us go back to B20, I'll be testing this as soon is done and create a Thread for it, is just matter of time
DrakenFX said:
about right, as long you have an Untouch/UnModded System yeah
Click to expand...
Click to collapse
Holy crap, that sounds awesome. Huge thanks for all of your work! Hoping someone will be able to confirm that it works on the A2017G
Just wow!
Thats what I have talked about.
I hope it works on the A2017G version.
Is this reversible? Would ZTE somehow be able to tell if the bootloader was unlocked before when returning the device for a warranty?
legendarygizmo said:
Is this reversible? Would ZTE somehow be able to tell if the bootloader was unlocked before when returning the device for a warranty?
Click to expand...
Click to collapse
yes it is, just keep your fastboot img in a safe place backup is in OP part of the guide.
to revert back is very simple same step but instead using fastboot_unlock.img you use your fastboot backup and do the rest of the steps (wipe and so on)
DrakenFX said:
yes it is, just keep your fastboot img in a safe place backup is in OP part of the guide.
to revert back is very simple same step but instead using fastboot_unlock.img you use your fastboot backup and do the rest of the steps (wipe and so on)
Click to expand...
Click to collapse
Don't forget fastboot oem lock
Sent from my ZTE A2017U using Tapatalk
Unjustified Dev said:
Don't forget fastboot oem lock
Sent from my ZTE A2017U using Tapatalk
Click to expand...
Click to collapse
annnddd that too
Do you think there will ever be a way to unlock without wiping internal?
Sent from my ZTE A2017U using XDA-Developers mobile app
SinisterXReaper said:
Do you think there will ever be a way to unlock without wiping internal?
Sent from my ZTE A2017U using XDA-Developers mobile app
Click to expand...
Click to collapse
Unfortunately it's necessary.
Sent from my ZTE A2017U using Tapatalk
SinisterXReaper said:
Do you think there will ever be a way to unlock without wiping internal?
Sent from my ZTE A2017U using XDA-Developers mobile app
Click to expand...
Click to collapse
been honest in Marshmallow, i remember in Lollipop you could unlock bootloader and keep everything but in Marshmallow everything change, any device i had that need bootloader unlock it wipes.
We essentially just forced ZTE's legal department's hand. They now have no way of voiding warranty with unlocked bootloader. Nice job guys!
Can I do this procedure with Axon Zte 7 A2017? (China Model)
Moderator Edit: @blessingme - it is not necessary or desirable to quote the entire OP. It can cause page loading issues with those on limited bandwidth or when mobile.
Thanks
blessingme said:
Can I do this procedure with Axon Zte 7 A2017? (China Model)
Click to expand...
Click to collapse
If you have twrp installed, let us know and don't forget to backup your fastboot.img
Sent from my ZTE A2017U using Tapatalk
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!
Treble Flashing Guide For All nokia treble enabled phones
Note -1. Before Doing These Steps Your device bootloader should be unlocked. otherwise you may brick your device.
2.Copy img files according to GSI Android Version
Example - iam using Nokia 6.1 Plus & i want to flash Pixel-ex-periance-9
in my phone using GSI
METHOD 1 - VIA CMD
1. copy vendor.img & boot.img form Android 9 stock ota.zip or OST File
2. download gsi from aosp , lineage , pixel experiance etc but choose ab Arm 64
3. now keep 3 files in one folder
4. open cmd in that folder
5. now turn of your mobile and go to download mode
6. now type fastboot devices
7. type fastboot -w
8. type fastboot flash vendor vendor.img
9. type fastboot flash system PixelExperienceP-arm64-ab.img
10. type fastboot flash boot boot.img
11. type fastboot -w
12. fastboot reboot
METHOD 2 - VIA TWRP
1. copy Those 3 img files to your directory internal or external
2. wipe everything except your internal & sd
3. select install img
4. select vendor.img and select vendorimage in partition box swipe to flash
5. next select PixelExperienceP-arm64-ab.img and select systemimage in partition box swipe to flash
6. next select boot.img and select boot in partition box swipe to flash
7. reboot system
Download stock Vendor.img & boot.img files from the below links
Android 9 https://drive.google.com/open?id=1WC9iGS8QnnnBmG4KKL3sEcqlR8LceBUt
Android 8.1.0 https://drive.google.com/open?id=1yY3QvUCYKDXlfn9bREObS2XwCScnU-EN
Please Hit Thanks Button If You Understand My Guide. Hope Every One Will Boot GSI Successfully In Your Phones. Keep Going...!!!
Thank you
can you post 6.1plus vendor IMG and boot IMG here please
Or links
pawankonjarla said:
can you post 6.1plus vendor IMG and boot IMG here please
Or links
Click to expand...
Click to collapse
links updated now
BootLoader
Should the bootloader be unlocked to flash via CMD??
Thanks:good:
nikash07 said:
Should the bootloader be unlocked to flash via CMD??
Thanks:good:
Click to expand...
Click to collapse
yes Need to unlock your bootloader before flashing GSI Or else you may Brick your device
Raghu varma said:
yes Need to unlock your bootloader before flashing GSI Or else you may Brick your device
Click to expand...
Click to collapse
How to unlock bootloader, especially after August Security patch coz HMD doesn't allow to unlock bootloader of 6.1 plus anymore
nikash07 said:
How to unlock bootloader, especially after August Security patch coz HMD doesn't allow to unlock bootloader of 6.1 plus anymore
Click to expand...
Click to collapse
Just Go to Nearest Nokia Care Point And tell them Iam not comfort with Android Pie i want to revert back to oreo june Security Patch So Just Inform Them i mean tell them to flash DRG-229D File . This file will directly goes down to oreo june security Patch And give the mobile to them they will flash in 2minutes And request Unlock Key Just by in searching Google.
Raghu varma said:
Just Go to Nearest Nokia Care Point And tell them Iam not comfort with Android Pie i want to revert back to oreo june Security Patch So Just Inform Them i mean tell them to flash DRG-229D File . This file will directly goes down to oreo june security Patch And give the mobile to them they will flash in 2minutes And request Unlock Key Just by in searching Google.
Click to expand...
Click to collapse
I don't think Nokia is going to accept this and flash Oreo just like that.
nikash07 said:
I don't think Nokia is going to accept this and flash Oreo just like that.
Click to expand...
Click to collapse
Bro I updated to pie and went to care point and said some complaints about pie.they finally downgraded my phone . For example tell them Iam not comfort with pie so just flash DRG-229D File using ost. This file belongs to Oreo june security patch .
I have removed the Telegram link in your OP. Posting Telegram links or other ways of promoting social media is not allowed on XDA.
Forum Rules said:
Self-promotion is forbidden, this includes blogs, social media and video channels etc. Random links will be removed.
Click to expand...
Click to collapse
Raghu varma said:
Treble Flashing Guide For All nokia treble enabled phones
Note -1. Before Doing These Steps Your device bootloader should be unlocked. otherwise you may brick your device.
2.Copy img files according to GSI Android Version
Example - iam using Nokia 6.1 Plus & i want to flash Pixel-ex-periance-9
in my phone using GSI
METHOD 1 - VIA CMD
1. copy vendor.img & boot.img form Android 9 stock ota.zip or OST File
2. download gsi from aosp , lineage , pixel experiance etc but choose ab Arm 64
3. now keep 3 files in one folder
4. open cmd in that folder
5. now turn of your mobile and go to download mode
6. now type fastboot devices
7. type fastboot -w
8. type fastboot flash vendor vendor.img
9. type fastboot flash system PixelExperienceP-arm64-ab.img
10. type fastboot flash boot boot.img
11. type fastboot -w
12. fastboot reboot
METHOD 2 - VIA TWRP
1. copy Those 3 img files to your directory internal or external
2. wipe everything except your internal & sd
3. select install img
4. select vendor.img and select vendorimage in partition box swipe to flash
5. next select PixelExperienceP-arm64-ab.img and select systemimage in partition box swipe to flash
6. next select boot.img and select boot in partition box swipe to flash
7. reboot system
Download stock Vendor.img & boot.img files from the below links
Android 9 https://drive.google.com/open?id=1WC9iGS8QnnnBmG4KKL3sEcqlR8LceBUt
Android 8.1.0 https://drive.google.com/open?id=1yY3QvUCYKDXlfn9bREObS2XwCScnU-EN
My Teligram Group Link All Are invited And Feel Free to Ask your Questions MOD EDIT: LINKS REMOVED
My Teligram Channel For the Further Information
Please Hit Thanks Button If You Understand My Guide. Hope Every One Will Boot GSI Successfully In Your Phones. Keep Going...!!!
Thank you
Click to expand...
Click to collapse
the Doctor said:
I have removed the Telegram link in your OP. Posting Telegram links or other ways of promoting social media is not allowed on XDA.
Click to expand...
Click to collapse
thanks for the information. I won't repeat this again
thank you very much
Can we unlock now?
And
How to flash stock rom
I installed AEX gsi, but without TWRP I can't install gapps. Anyone know how to install gapps another way?
paul89rulez said:
thank you very much
Click to expand...
Click to collapse
Welcome
bbcastro said:
I installed AEX gsi, but without TWRP I can't install gapps. Anyone know how to install gapps another way?
Click to expand...
Click to collapse
Well now twrp thread is up in nokia 6.1 kenel and recovery development section check it out
earlier treble gsi's had issues with Nokia phones Sim cards not being detected - has this been resolved, specifically relating to TA-1103?
So should I download From "A" only roms or "A/AB" roms?
Nokia X6 with Custom Oreo ROM - How to load stock Android Pie 6.1 plus image
Hi,
I bought a Nokia X6 in September 2018 (6GB/64GB) and would like to install the Stock Nokia 6.1 Plus Android 9 image.
I see my phone is rooted and it shows the message "Your device has loaded a different operating system." everytime I start it and I have to use Magisk to hide several banking applications.
The phone works great and I knew it was going to be relased in Europe eventually, but I am scared to brick it by loading the Android 9 Image.
I already tried attempting the update through OTA but the zip file is ignored. Nothing happens.
I am new to this forum so I don't know if my question has been asked by someone else.
Can you please help me?
Thank you!
Image size is bigger than target device..
I am using nokia 6.1 plus .. its support project treble , and its ab device..
When i try to flash a gsi rom bigger than 2.5 gb its also eror that image size is bigger than target device ...:crying:
Many popular gsi like oos, one, hydrogen, color os file size over than 2.5 gb .. so always shows this eror..
Any solution for this eror..??
---------- Post added at 04:03 PM ---------- Previous post was at 03:28 PM ----------
I am using nokia 6.1 plus .. its support project treble , and its ab device..
When i try to flash a gsi rom bigger than 2.5 gb its also eror that image size is bigger than target device ...:crying:
Many popular gsi like oos, one, hydrogen, color os file size over than 2.5 gb .. so always shows this eror..
Any solution for this eror..??
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?
Hello everyone hope you are all keeping well.
Since I believe that many of you don't know about this, I've decided to share the steps I've done in order to root the OP 11R ( ACE 2 )
I cannot be responsible if you brick your device. Your phone, your choices, your responsibility!
1 - Unlock the bootloader (if you haven't done it already...beware that this will erase all of your user data). To do so, you must:
Enable developer options
Enable the "OEM unlocking" option
Enable USB debugging
Have both adb and fastboot, from SDK Platform Tools available on your PC
Connect your phone to your PC using the USB cable and run the following commands:
adb devices
adb reboot bootloader
(so your phone will reboot into fastboot mode)
fastboot flashing unlock
(device should now unlock)
fastboot reboot
(device reboots with an unlocked bootloader and data partition wiped so set up the device from scratch again)
2 - Download OP 11R stock boot.img that you may find later on this post, that matches your current build.
Copy the boot.img to your devices internal memory
Leave a copy of it on your PC (on the same folder you have adb and fastboot...you never know if you will need to use it again in the future...to restore the stock boot.img, aka revert to stock...)
Indian Boot.img A_0.8 - download
3 - Download latest Magisk Manager from HERE and install it on your phone
4 - Open Magisk Manager App and press:
Install
Select and Patch a File
Browse to the path where you saved stock boot.img and select it
Magisk Manager will now patch the boot image and store it in [Internal Storage]/Download/magisk_patched.img
5 - Copy the patched boot image from your device to your PC (Store it on the same folder where you have adb and fastboot)
6 - Flash the patched boot image to your phone by running these commands (remember, you must have patched boot image on the same folder you have adb and fastboot and, of course, your device must be connected to your PC...)
adb reboot bootloader
fastboot flash boot magisk_patched.img
fastboot reboot
7 - After the phone boots up, hopefully with a normal boot (almost feels like nothing happened....), install/open Magisk Manager App again and watch Magisk doing it's magic!
8 - Enjoy!
All credits goes to topjohnwu and his incredible work with Magisk.
Why title says NORD 2T?
firoz3321 said:
Why title says NORD 2T?
Click to expand...
Click to collapse
MB ... typo
Thank you for detailed steps.
Is there any benefit with KernelSU over this method ?
I always used Magisk on OP8, but recently saw an article for OP11 with Kernel SU.
Also is there MSM tool support to recover softbriked device ?
firoz3321 said:
Thank you for detailed steps.
Is there any benefit with KernelSU over this method ?
I always used Magisk on OP8, but recently saw an article for OP11 with Kernel SU.
Also is there MSM tool support to recover softbriked device ?
Click to expand...
Click to collapse
Sorry but there is no msm tool available for new OnePlus devices. + You can use Fastboot enhance tool from github to recover softbrick , magisk is always recommended for rooting because of ease of steps and simple to use
Hello, thanks for the detailed instructions. Today I updated to A. 10, and unfortunately lost my root access. Without the root cannot extract the boot image. If you're already updated and have a backup of A. 10 boot, can you please share?
saifsohel said:
Hello, thanks for the detailed instructions. Today I updated to A. 10, and unfortunately lost my root access. Without the root cannot extract the boot image. If you're already updated and have a backup of A. 10 boot, can you please share?
Click to expand...
Click to collapse
i didn't got the update yet ... + oxygen updater also showing A.08. i will update this post soon as I got update
shiki_senpai said:
i didn't got the update yet ... + oxygen updater also showing A.08. i will update this post soon as I got update
Click to expand...
Click to collapse
Then remember to take a backup of the boot before rebooting. I messed up big time.
Thanks for the detailed information man. Can I know if bootloader unlock decreases widevine L1 to L3? As this was case with my OP6