Related
not sure if this belongs here, but couldn't find a teclast x80 pro section
I was looking to make this tab android only and then root it
found on the internet different sources for each procedure, so decided to compile everything in one place with full credits
teclast x80 pro [root + keep android only for 25gb storage]
---------------------------------------------------------------------------------------------------------------------------------------
[for 25gb of storage and android only]
first get the tools: https://www.mediafire.com/?qxwxz1mz47g7mkv
install PhoneFlashTool, iSocUSB-Driver-Setup-1.2.0, IntelAndroidDrvSetup1.5.0
then you need to check what firmware your tab is on, it's written on the back of the tablet
mine was on E3E9 however teclast site didn't have the firmware so I used the e3e8 instead and it works fine
download the firmware from http://www.teclast.com/en/firmware/
you need to get the android.rar
when it's done, unpack the android.rar
then unpack the gpt.rar
take the gpt.bin and copy-paste it in the android folder, replacing the original gpt.bin
put tablet in dnx mode, press volume +, volume - and power at the same time
connect tab to pc with usb cable
run the phone flash tool browse for the android folder and flash the android image
after it is done you have 25gb all for android
--------------------------------------------------------------------------------------------------------------------------
[for root access]
you must have adb drivers installed for this to work
copy+paste the UPDATE-SuperSU.zip to the tablet
with the tab switched on normally and connected to pc with usb cable go to settings>developer options and check "oem unlocking" and "usb debugging"
then go to the toolbox folder and double-click 1.Unlock_Bootloader.bat
wait for it to do the work, then reboot and again go to settings>developer options and check "oem unlocking" and "usb debugging"
then double-click 2.Unlock_Verity-boot.bat, reboot and repeat oem and debug settings
then double click 3 Flash-boot.bat , reboot and repeat oem and debug settings
steps 4 and 5 from the toolbox folder didn't work for me, if it works for you after double-click all good
if it doesn't: shift+right click the toolbox folder with tab connected to pc and "open command window here"
copy and paste this in the command window:
adb reboot fastboot
"press enter"
fastboot flash recovery TWRP-X80-pro.img
"press enter"
adb reboot recovery
"press enter"
from the twrp menu, select install and browse for the UPDATE-SuperSU.zip you copy+pasted earlier
reboot and you should have root access + fully working twrp recovery
---------------------------------------------------------------------------------------------------------------------
full credits
machetekills from techtablets.com for porting this twrp and the toolbox!
https://techtablets.com/forum/topic/x80-pro-toolbox-unlock-new-tablet-twrp-2-8-7-0-root/
allember for the .gpt file
https://techtablets.com/forum/topic/x80-plus-android-os-only/#post-42636
-----------------------------------------
other stuff
this tab gets really hot when gaming by the way
one way to fix this is to get the no frills cpu control from the play store and set the max speed for the processor to
1,2 or 1,3, from 1,92, this gets the heat down to almost normal and won't burn your hand anymore like it used too
now I can play and read in peace
http://imgur.com/a/OZtGw
**********************************************************
here is WalterNimoy's solution to root on E3E9
thanks for sharing buddy ~
------------------------------------------------------------------
The problem is in the boot.img. So, to root the E3E9, you mus essentially follow the tutorial above, but instead of the backup for the E3E8, download the version for the E3E9. You can do it here.
E3E9 Teclast X80 Pro : http://www.teclast.com/tools/pad/pad.php?t=p
Then after, the real solution. You must absolutely use another version of the boot.img. If you use the one in the tutorial with the E3E9, you won't have sound, touchscreen buggy, etc. So use this one instead. It's also v. 1.07. I believe it's was originally made for the X80 Power, but it work perfectly with the X80 Pro E3E9.
boot.img v. 1.07 E3E9 https://yadi.sk/d/78MARiHGtyfdG
Finally, if you have a problem when it's time to root, inthe step 4, enter the command manually. It was the solution to make it work for me.
Here you go! Your X80 Pro E3E9 should be rooted, with everything working. Let me know if it also worked for you!
--------------------------------------------------------------------------
Houston, we have a problem. First, thank you for your work. Unfortunately, it doesn't go well from here. I have the E3E9 version of the tablet. I also used the firmware for this tablet , and not the E3E8 as you did. The firmware have about 50 %less brightness in the E3E8 firmware than in the E3E9, and is also compiled for a slower cpu. So, after I flash the ROM, all go well. The two first steps for root access also go well. The problem begin at the third step, after I flash the boot.img. The Gsensor stop working, and the sound as well. I succeed to root, but the tablet is not really usable... Do you have any idea? I really want to root, but with these limitations, it is better not to. Thank you.
A couple of notes for anyone attempting this:
1. There's a v1.07 ROM for E3E9 which I dug up from the Chinese website (don't ask me how I did this, I tried to replicate my steps with no success XD). Uploaded the file as-is to my Dropbox: https://www.dropbox.com/s/eoo8stw1xxyrif3/
2. In my testing, after rooting, I lost audio and access to SD card. The touch screen would also occasionally stop working. I used the ROM mentioned above, and not the one that the op used, so your mileage may vary.
3. I was extremely unpleased with the performance of the stock ROM, and the phenomenon I experienced after rooting made me look of an alternative solution - which I found in a Russian forum (https://4pda.ru/forum/index.php?showtopic=741990&st=1640#entry55200079). A gem in the form of custom CM12.1 ROM baked for the E3E7 model. Installed it on my tablet and it worked flawlessly! The default language is Russian, but your're prompted to change it on the first installation screen.
I'm using this for a couple of hours now and everything seems to be working extremely well, with no dropped frames or choppy animations I experienced in the stock version.
I'll keep testing and report back if I find any bugs.
Edit 1:
So I noticed just a couple of drawbacks for using the CM Rom:
1. Camera is not working (however, I don't think it's a big deal given its quality anyway)
2. I made sure to backup the "Boot to Windows" apk beforehand, but it won't let me install it. If anyone could grab their apk and upload here, I could try it and report back.
Succède, finally
I succeed to root v1.07, E3E9. Let me know if you want to know how I manage to do this. ?
WalterNimoy said:
I succeed to root v1.07, E3E9. Let me know if you want to know how I manage to do this. ?
Click to expand...
Click to collapse
Share it man. I want to buy this device
WalterNimoy said:
Houston, we have a problem. First, thank you for your work. Unfortunately, it doesn't go well from here. I have the E3E9 version of the tablet. I also used the firmware for this tablet , and not the E3E8 as you did. The firmware have about 50 %less brightness in the E3E8 firmware than in the E3E9, and is also compiled for a slower cpu. So, after I flash the ROM, all go well. The two first steps for root access also go well. The problem begin at the third step, after I flash the boot.img. The Gsensor stop working, and the sound as well. I succeed to root, but the tablet is not really usable... Do you have any idea? I really want to root, but with these limitations, it is better not to. Thank you.
Click to expand...
Click to collapse
in e3e8 that I flashed, everything but the camera works - the quality is [email protected] anyway so no real loss - g sensor works fine and underclocking makes the battery last a lot longer
I'm using this as a reader and some gaming with a 32gb sd card that has a tiny part of my library and some games and plays fine
this screen is perfect for reading
it looks like you found a way to root e3e9 tho
WalterNimoy said:
I succeed to root v1.07, E3E9. Let me know if you want to know how I manage to do this.
Click to expand...
Click to collapse
share away
11wallace11 said:
A couple of notes for anyone attempting this:
1. There's a v1.07 ROM for E3E9 which I dug up from the Chinese website (don't ask me how I did this, I tried to replicate my steps with no success XD). Uploaded the file as-is to my Dropbox: https://www.dropbox.com/s/eoo8stw1xxyrif3/
2. In my testing, after rooting, I lost audio and access to SD card. The touch screen would also occasionally stop working. I used the ROM mentioned above, and not the one that the op used, so your mileage may vary.
3. I was extremely unpleased with the performance of the stock ROM, and the phenomenon I experienced after rooting made me look of an alternative solution - which I found in a Russian forum (https://4pda.ru/forum/index.php?showtopic=741990&st=1640#entry55200079). A gem in the form of custom CM12.1 ROM baked for the E3E7 model. Installed it on my tablet and it worked flawlessly! The default language is Russian, but your're prompted to change it on the first installation screen.
I'm using this for a couple of hours now and everything seems to be working extremely well, with no dropped frames or choppy animations I experienced in the stock version.
I'll keep testing and report back if I find any bugs.
Edit 1:
So I noticed just a couple of drawbacks for using the CM Rom:
1. Camera is not working (however, I don't think it's a big deal given its quality anyway)
.
Click to expand...
Click to collapse
camera is not working even in the stock rom I flashed haha
I just asked stratos7 to post the solution to root the E3E9. I still cannot post outside link. So, just wait a little. He will surely see the message in his inbox.
So guys, how is your experience with teclast x80 pro. What is the pros and cons? I want to buy cheap tablet but still confused.
Teclast x80 pro
Onda v80 plus
Onda v891w CH
All below $100. Which one is your recomendation? Sorry a bit OOT
here is WalterNimoy's solution to root on E3E9
------------------------------------------------------------------
The problem is in the boot.img. So, to root the E3E9, you mus essentially follow the tutorial above, but instead of the backup for the E3E8, download the version for the E3E9. You can do it here.
E3E9 Teclast X80 Pro : http://www.teclast.com/tools/pad/pad.php?t=p
Then after, the real solution. You must absolutely use another version of the boot.img. If you use the one in the tutorial with the E3E9, you won't have sound, touchscreen buggy, etc. So use this one instead. It's also v. 1.07. I believe it's was originally made for the X80 Power, but it work perfectly with the X80 Pro E3E9.
boot.img v. 1.07 E3E9 https://yadi.sk/d/78MARiHGtyfdG
Finally, if you have a problem when it's time to root, inthe step 4, enter the command manually. It was the solution to make it work for me.
Here you go! Your X80 Pro E3E9 should be rooted, with everything working. Let me know if it also worked for you!
--------------------------------------------------------------------------
link to the e3e9 firmware is stating that a baidu account is needed to download some of the files, is there a way to get the files without this account?
avi321 said:
link to the e3e9 firmware is stating that a baidu account is needed to download some of the files, is there a way to get the files without this account?
Click to expand...
Click to collapse
You can download the full firmware from here: https://yadi.sk/d/2Fes5npR3GykqT it downloads quickly and its the correct files.
Just found it on the Russian forum: https://w3bsit3-dns.com/forum/index.php?showtopic=741990&st=2280
lost sound
I flashed E3E9 firmware from the yandisk above, the sound doesn't work after. I tried also the boot image from the post before, the tablet didn't boot.
I am now stuck with the device with no sound, using the E3E9 image. is there anything that can be done?
phone flash tool: "F..ailed to load" "There is no flash file in the archive". Please help.
...
..
If anyone still replies to this thread, im stuck at step 3 with the boot.img. after flashing the boot.img my tablet is stuck in a bootloop teclast screen. E3E9 model
With a X80 Pro E6E9 the procedure for remove the partition with Windows still work? i dont need the root but just remove Windows
...has anyone SUCCESSFULLY rooted thier Teclast-x80 pro...WITHOUT complications...?!?...
...and can I root my tablet without taking out the Windows part...?!?...
---------- Post added at 07:09 PM ---------- Previous post was at 07:06 PM ----------
...has anyone SUCCESSFULLY rooted thier Teclast-x80 pro...WITHOUT complications...?!?...
...and can I root my tablet without taking out the Windows part...?!?...
Android 6 and 7
This works well: http://www.android-x86.org/download
Someone should get the sound to work.
---------- Post added at 10:15 PM ---------- Previous post was at 10:11 PM ----------
Connect usb hub with keyboard and unetbootin Android ISO usb key. Boot into bios and select usb key as boot device.
shez2 said:
This works well: http://www.android-x86.org/download
Someone should get the sound to work.
---------- Post added at 10:15 PM ---------- Previous post was at 10:11 PM ----------
Connect usb hub with keyboard and unetbootin Android ISO usb key. Boot into bios and select usb key as boot device.
Click to expand...
Click to collapse
What is that? I see CM 14.1.
I read through quite a few post here to get everything sorted out and in order to save every one some time here is a summary of all the info I have gathered so far, and my way to thank the forum for offering me so many helpful tips. I'll try to keep this thread updated as information comes in.
All credit goes to their respective owners, I am only aggregating all the information here.
Current status on BL Unlock:
China version: OEM unlock not greyed out, direct BL unlock possible
EU/NA version (L09/L29/L0C): OEM unlock greyed out in developer options, BL unlock possible via FunkyHuawei method by upgrading to .170.
UPDATE 2019/01/02: Some users reported they have already received the .171 update from carrier (https://forum.xda-developers.com/showpost.php?p=78571337&postcount=6), if that is the case you can skip the FH Method part and go directly to unlock BL.
Note: Currently .170 is not GooglePay certified, so Google Pay won't work on this, if you must have Google pay please wait for your carrier to update to some version that support OEM unlock (tap build number 7x to get Developer Options in Settings -> System -> About Phone and then go to Settings -> System -> Developer Options and see if Enable OEM Unlock option is enabled).
Also current recovery install requires you to boot into recovery (Power and volume up with phone disconnected from USB) every single time if you want root, which is not perfect.
The only time you'd be required to wipe your phone is right after your BL is unlocked with fastboot OEM unlock, please make sure you have a backup before doing that step.
Where to get unlock code?
In order to get BL unlocked, you need both allow OEM unlock option NOT greyed out (i.e., you can enable it) AND a BL unlock code. BL unlock code can only be purchased either from FunkyHuawei (55 USD one time for BL unlock code only or if you buy an unlimited pass 132USD for unlimited flashing + BL unlock code (note that it is locked to your phone and can not be transferred)), or MinistryOfSolutions (30 Euro, https://ministryofsolutions.com/huawei-bootloader-unlock-service-all-new-models-new-firmwares, BL unlock code only).
FunkyHuawei Method (for non-China version)
1. Create an account in https://funkyhuawei.club/membersarea, buy 1 credit (if you just want to download .170 firmware, each credit cost 18USD).
2. Go to Select Firmware tab, use LYA-Global if you don't see the exact model. Then select .171 version.
3. Follow instructions here: https://pastebin.com/raw/Db5ZSyqu, you must download the specific HiSuite version (9.0.2.301）and the specific installer executable. Run the executable FHHiSuiteInstaller.exe as administrator (right-click and choose Run As Administrator) <- must run as admin since it will need to modify your host file. Make sure the script runs without error.
3.1 (Additional step for L0C): Edit the c:\users\YOURHOMEFOLDER\appdata\local\hisuite\userdata\updatedogdev\hisuiteconfig.xml file and change LYA-L29 to LYA-L0C everywhere it occurs and save the file. (Thanks to FunkyHuawei Support for pointing this one out).
4. Put the phone into fastboot mode (adb reboot-bootloader or with the phone off connect the usb cable while holding volume down, or boot the phone holding volume down with USB cable connected to PC).
5. Go to HiSuite on your PC and click on System Recovery (furthest to the right towards the bottom of the main screen), and let it do the magic. You will see some cmd windows pop up however it should get to the download progress with a percentage pretty fast, if you don't see that pop up then please check to make sure you have at least one credit in the FH Select Firmware tab and you have installed the specific versions of HiSuite and ran the installer as admin in Step 3.
6. Once everything is completed please verify to see if your firmware version is .171.
Unlock Bootloader
Again, get the BL code and go to Settings -> System -> Developer Options and make sure Enable OEM Unlock option is enabled. Also check to make sure you have everything backed up. Also enable USB Debugging in the same screen as well.
Rest is pretty standard:
Code:
adb devices (will bring up the authorization window on your phone, click on Always Trust)
adb reboot-bootloader
fastboot devices (make sure the device is in fastboot mode)
fastboot oem unlock *UNLOCK CODE*
at this point there will be a format operation performed on the phone, if it didn't complete successfully don't worry, your phone is wiped. During the boot you should see a black window with yellow text of warnings to tell you your phone is unlocked and not secured.
Go through all the steps to initialize the phone, turn on Developer options again, and enable USB Debugging again.
Root
1. Download and install Magisk Manager from this XDA post: https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445
2. Switch channel, go to Magisk Manager -> Settings -> Update Channel , set it to Custom, and the URL is https://bit.ly/2N8UVlq (at the moment, per https://forum.xda-developers.com/apps/magisk/dev-magisk-canary-channel-bleeding-edge-t3839337). Go back to main screen and down swipe to refresh, it should say Latest Version > v18.0.
3. You will need to find the stock RECOVERY_RAMDIS.img file, I used HW Firmware Finder (https://forum.xda-developers.com/tools/general/huawei-firmware-finder-team-mt-t3469146) to help me with the task, however I couldn't find the L0C update file and ended up using L09 update file instead, which appear to work. I also couldn't find the update.zip for .171 so I ended up using the latest full update version that was available to me (http://update.hicloud.com:8180/TDS/...69/g1750/v181585/f1/full/update_full_base.zip).
4. Unzip the file, drag out UPDATE.APP file in the zip package, and opened it with Huawei Firmware Extractor (I used 0.9.9.5 in this thread: https://forum.xda-developers.com/showthread.php?t=2433454). Extract and open the UPDATE.APP in update file. If you get a checksum error make sure to uncheck both of the verify checksum in Settings -> Extract.
5. Now you should see a RECOVERY_RAMDIS.img file, right click and extract it.
6. Send the RECOVERY_RAMDIS.img file back to your phone (anywhere is fine), go back to Magisk Manager -> Install -> Patch boot, get the patched_boot.img file from the phone back to the PC.
UPDATE 2019/01/02: @pvillasuso was kind enough to post the ramdisk image (both original and Magisk modified) for Mate 20 Pro LYA-L09 (Firmware version .171):https://forum.xda-developers.com/showpost.php?p=78575496&postcount=13, obviously use it at your own risk.
7. Go to fastboot mode again:
Code:
adb devices
adb reboot-bootloader
fastboot devices
fastboot flash recovery_ramdisk "PATH_TO_patched_boot.img"
fastboot reboot
Now your phone should be back to normal with no root yet, turn off your phone and turn it back on by booting into recovery (Power and volume up with phone disconnected from USB)
Boot up and if you go to Magisk now you should be able to see Magisk installed with Installed Version same as Latest Version.
Congrats you are now rooted!
In future you will need to boot into recovery each time to maintain root (which requires you to turn phone off and power + vol up), if you prefer not to do so @ThatsJustLogic suggested you can use the app https://forum.xda-developers.com/showpost.php?p=78569733&postcount=2 to add a one-click reboot from your dropdown menu.
Credits:
@ThatsJustLogic - Figured out the installation steps to patch ramdisk: https://forum.xda-developers.com/showpost.php?p=78554707&postcount=125
@duraaraa - Guy behind FunkyHuawei for figuring out the .171 upgrade and make everything works smoothly https://forum.xda-developers.com/mate-20-pro/how-to/unlock-rebrand-unbrick-update-t3855065
@mutahharbashir - Guy behind MinistryOfSolutions for the unlock BL code.
And creators of Magisk, HWFirmwareFinder, HWUpdateExtractor.
zhuanyi said:
Now your phone should be back to normal with no root yet, turn off your phone and turn it back on by booting into recovery (Power and volume up with phone disconnected from USB)
Click to expand...
Click to collapse
To stop you needing to do this on every boot this app: https://play.google.com/store/apps/details?id=com.superthomaslab.rootessentials allows you to add a "Reboot Recovery" button to your notification tray so its just a one tap reboot instead of holding volume up when you want to reboot after applying a change or something its something small but it saves some hassle.
Awwsome, thank you so much. Now I can finally use Google pay on global firmware 9.0.0.171. It's working perfectly
This is amazing development
Hi, can someone post his oeminfo?
On firmware versions; I have an Australian L29 running an ota update v 168. Oem unlock is available, and Google pay works.
Thank you for the guide.
Can we re-brand from Chinese to international now?
thunderpossuem said:
On firmware versions; I have an Australian L29 running an ota update v 168. Oem unlock is available, and Google pay works.
Click to expand...
Click to collapse
How come? Can you post a screenshot with developer options on yhe screen?? Oh, you have. Can this mean that we will be able to unlock bootloader for free when v168 update arrives to other countries??
Sent from my LYA-L29 using XDA Labs
The 171 official firmware also allows OEM Unlock..
Maybe wait until you get the new update , save a few bucks
deepsrd said:
The 171 official firmware also allows OEM Unlock..
Maybe wait until you get the new update , save a few bucks
Click to expand...
Click to collapse
That's just what i thought
Sent from my LYA-L29 using XDA Labs
Thanks for the guide , Im rooted now !
One question , I have the patched_boot.img file , is it the same for everyone ?
I can share it and it will save some extra steps
Let me know
pvillasuso said:
Thanks for the guide , Im rooted now !
One question , I have the patched_boot.img file , is it the same for everyone ?
I can share it and it will save some extra steps
Let me know
Click to expand...
Click to collapse
The patched file will work for anyone who has the mate 20 pro and the same FW version as you. Theres no extra steps it just removes the finding the FW, extracting and patching the image yourself They will still need magisk and the canary channel.
If you are going to share I would specify Firmware version and attach a non patched one incase people have issues and want to revert.
My phone model : Mate 20 Pro LYA-L09 (Firmware version 9.0.0.211)
patched_boot.img > https://www.mediafire.com/file/fp3jk281d47bh6k/patched_boot.img/file
Apply on your own risk , worked for me !
Hi, glad to hear that even L0C model has to the chance to root. Just wondering after flash the global .171 version which should solve the OEM greyed-out problem, the next step is to purchase a BL unlock code? And is there a chance that after BL and FRP unlocked. My model (LYA-L0C) can be rebrand to another one?
deepsrd said:
The 171 official firmware also allows OEM Unlock..
Maybe wait until you get the new update , save a few bucks
Click to expand...
Click to collapse
Indeed it is 18 USD saved, also hopefully it is more compatible with your phone.
Can you give an example of your path to "PATH_TO_patched_boot.img"
I must be getting syntax incorrect for the file in internal storage download folder, and I have tried everything with and without / leaving out folders.
is this ota proof?
Some rooting questions....
Hi.
I will try to be brief and on topic. Feel free to remove post if not according to Xda forum rules.
Long story short. I am an heavy iOS user from the apple jailbreak scene. I am no developer (only user) and now I have taken the big step from IOS to Android.
Huawei mate 20 pro broke my curiosity. I have always "jailbroken" my iPhone since 2007 and now I am considering root of my HM20PRO.
I have some questions before I try this and brick my phone.
I have Norwegian model, LYA-L29 with 9.0.0.153 (c432) software. (BL unlock greyed out here as well)
How is the partitions setup on this device?
Easy explanation of RAM disk, main disk or whatever?
Do I always have the option to revert to stock setup no matter what? With simple erase/wipe/recover?
Is hisuite the recovery software to use if I want to go back?
Is it possible to unlock the boot loader and go back to 9.0.0.153??
Is the software builds so the highest number software has the latest fixes? (108,122,153,168,171 +++)
Do i loose the safety net like google pay, and other apps that can see that my phone is rooted?
Is there an app to run to trick the apps into believing that the phone is not rooted? (like on iOS)
Hope that someone can take the time to help me with my questions.
The boot via ramdisk/fastboot or what you call it to get rooted is only nesecary on each boot up right? You stay rooted until the next shutdown?
(Semi.tethered on iOS)
sorry for the noob questions, but I am new with this so thanks...
Regards,
Kenneth - Trondheim, Norway
PS:I have to say the switch from iOS to android and Huawei mate 20 pro have been great so far (except new replacement phone on the first day with green screen on BOE screen.) Now all is good.
Main reasons to root android?
I like to have different custom gestures through out the software. And also tweaked apps and notification tweaks, icons.
fromiOS2Android said:
Hi.
How is the partitions setup on this device?
Easy explanation of RAM disk, main disk or whatever?
Do I always have the option to revert to stock setup no matter what? With simple erase/wipe/recover?
Is hisuite the recovery software to use if I want to go back?
Is it possible to unlock the boot loader and go back to 9.0.0.153??
Is the software builds so the highest number software has the latest fixes? (108,122,153,168,171 +++)
Do i loose the safety net like google pay, and other apps that can see that my phone is rooted?
Is there an app to run to trick the apps into believing that the phone is not rooted? (like on iOS)
The boot via ramdisk/fastboot or what you call it to get rooted is only nesecary on each boot up right? You stay rooted until the next shutdown?
(Semi.tethered on iOS)
Main reasons to root android? I like to have different custom gestures through out the software. And also tweaked apps and notification tweaks, icons.
Click to expand...
Click to collapse
Hi, first of all, welcome to Android
My advice is to NOT root until you got an answer to all your questions
I'll let some pros answer the technical questions on the partitions) but here's what I can tell you:
- Main reason to root for me is adblockers and (not a must though) custom roms.
- There is a function within magisk to hide root from apps.
- On the fixes, yes, 171 is the one that allows root and that's also the latest one with all the fixes.
- Once you root you stay rooted, you don't have to repeat the whole process at every boot.
- From what I read in several threads, right now you can't revert to older firmwares. Also, the 171 seems to be market specific, what I will do is to wait until the update gets rolled out in my market by Huawei, I read that the unlock bootloader option is then available officially.
- I would also like to know about google pay (does it brake with root?) and are there other functions that break (camera functions,etc) like it does on other phones (sony for instance)
charliebigpot said:
- I would also like to know about google pay (does it brake with root?) and are there other functions that break (camera functions,etc) like it does on other phones (sony for instance)
Click to expand...
Click to collapse
Using Magisk Hide on Google Pay will prevent it from detecting root, however if SafetyNet fails then it probably still won't work.
There are a few Magisk modules that can (apparently) force SafetyNet to pass, however I haven't ever used any of them.
Just in case you didnt know ive wrote this guide to help root your honor magic 2 model (TNY-AL00)
first you must have your bootloader unlocked and huawei does not give BL unlock codes anymore so youll have to get it from a third party source and they charge money for this service, i know it F**kin sucks but i havent found any workaround for this, i used funkyhuawei and it was 55 usd, they were quite quick with getting me the code and i cant use a phone without full control so it was worth it to me, ive heard of cheaper alternatives like ministry of solutions but i do not know the validity of this.
Second, you must find an update.zip firmware for TNY-AL00 which i could only find on easyfirmware.com which again they freaking charge money but look around you might be able to find free firmware someware, as far as i know at the time of this writing the huawei firmware finder app does not have the new models yet. Find this firmware and download to a pc "and yes you can use a lower version than the one your running as i used a .129 RECOVERY_RAMDIS.img and my system is on .150 and i havent run into any problems as of yet"
Third, download huawei update extractor on pc run it and in settings make sure the first two boxes are unchecked. Open update.zip with the extractor and extract RECOVERY_RAMDIS.img from it and transfer it to your phones storage
Fourth, magisk now supports emui 9 rooting but at the time of this writing its only available on the canary build,
To get to the canary version of magisk download and install magisk manager then ignore the install prompt magisk gives you when you run it and then go to settings and hit update channel and choose custom and paste this "https://raw.githubusercontent.com/topjohnwu/magisk_files/master/canary_builds/canary.json" and restart magisk and itll ask you to update, update the manager then when it asks to install magisk.zip go to install and patch boot image " make sure magisk version is on 18.1 not 18.0" and patch the recover_ramdis file on your phone. The patched boot image will be in the download folder of your phone, use pc and transfer the patched boot image to desktop on pc
Fifth, download minimal fastboot and adb drivers to yor pc and run command prompt, connect phone to pc and and run phone in fastboot mode " press and hold volume up right after pluging in usb from pc to enter fastboot" in command prompt type fastboot devices and it should show some numbers which means it recognizes your phone, now type "fastboot flash recovery_ramdisk /path/to/RECOVERY_RAMDIS.img" or just drag the RECOVERY_RAMDIS.img into command prompt after typing up to recovery_ramdisk
Then type fastboot reboot and get your phone to power down, to have root you now have to hold volume up and power to boot. You have to do this every time if you want root. Your now rooted..........
Has anyone tried this?
jaytee86 said:
Has anyone tried this?
Click to expand...
Click to collapse
what about you?
wei-steve said:
what about you?
Click to expand...
Click to collapse
Not yet. Seemed pretty risky...
Actually right now I'm just praying that my phone will continue working. Accidentally dropped it onto concrete from a great height tonight and it looks pretty roughed up...
If it continues to work maybe I'll tackle that in a few weeks.
jaytee86 said:
Not yet. Seemed pretty risky...
Actually right now I'm just praying that my phone will continue working. Accidentally dropped it onto concrete from a great height tonight and it looks pretty roughed up...
If it continues to work maybe I'll tackle that in a few weeks.
Click to expand...
Click to collapse
i can t root by magisk
jaytee86 said:
Not yet. Seemed pretty risky...
Actually right now I'm just praying that my phone will continue working. Accidentally dropped it onto concrete from a great height tonight and it looks pretty roughed up...
If it continues to work maybe I'll tackle that in a few weeks.
Click to expand...
Click to collapse
i rooded now, hahahahaha
wei-steve said:
i rooded now, hahahahaha
Click to expand...
Click to collapse
You used the above method and had to pay? Or is there another "free" way?
ajaffarali said:
You used the above method and had to pay? Or is there another "free" way?
Click to expand...
Click to collapse
There's no free method to unlock the bootloader
PalakMi said:
There's no free method to unlock the bootloader
Click to expand...
Click to collapse
That's unfortunate. Ny biggest reason for rooting would be to get better camera support. I dont suppose GCam works on this with a root? I don't see any ROM development for it either. Why did you decide to root?
Yes this is tryed and true method. I get it working on my phones first then i post guide, everything works fine, only thing ive noticed is sometimes itll take a min for magisk to ask for grant to su from app or service.
Linxy420 said:
Just in case you didnt know ive wrote this guide to help root your honor magic 2 model (TNY-AL00)
Click to expand...
Click to collapse
Tnx for sharing the info!
I'm considering trying the process and maybe attempt to build a TWRP image if rooted successfully.
Is your device still working properly?
Did you accept OTA updates and would you use the exact same steps and files if you were rooting today?
No ota
You have to reflash the original ramdisk.img to update then flash modded ramdisk.img
I'm considering buying this but only if it is rootable. Is it possible to install wearOS afterwards (soc compatibility ?)? Thank you very much
Hi. i need urgent help regarding downgrading my galaxy note 8 from pie to oreo or nougat. i am using android pie from last 1 month. some of my apps stop working so i decided to downgrade from pie to oreo. i had downloaded oreo firmware december 2018 version from sammobile and tried to flash with odin 3.13.1 but it failed. i had tried different versions of odin but every time flashing stuck at set partition nand write start.i always run odin as administrator. i also tried to flash different firmware version like sept version of oreo but still it failed. i downloaded nougat firmware from sammobile. it flashed normally and i was happy but when my phone restarted i was shocked. my device was factory reseted but with android pie version. it looked flashing nougat only formatted my device. i am tired. i tried every damn thing. i tried changing usb port, tried differant usb cable, reinstalled device drivers, made sure that usb debugging is on , even tried on differant pc. but no result. then i tried emergency software recovery in smart switch. if i connect my phone switched on then smart switch discover my device but when i connect my device in download mode then smart switch says that device not supported. i contacted service centre but they say they do not downgrade the device.please please please someone help me. i am attaching a screenshot of odin stuck at nand write start.
drvish said:
Hi. i need urgent help regarding downgrading my galaxy note 8 from pie to oreo or nougat. i am using android pie from last 1 month. some of my apps stop working so i decided to downgrade from pie to oreo. i had downloaded oreo firmware december 2018 version from sammobile and tried to flash with odin 3.13.1 but it failed. i had tried different versions of odin but every time flashing stuck at set partition nand write start.i always run odin as administrator. i also tried to flash different firmware version like sept version of oreo but still it failed. i downloaded nougat firmware from sammobile. it flashed normally and i was happy but when my phone restarted i was shocked. my device was factory reseted but with android pie version. it looked flashing nougat only formatted my device. i am tired. i tried every damn thing. i tried changing usb port, tried differant usb cable, reinstalled device drivers, made sure that usb debugging is on , even tried on differant pc. but no result. then i tried emergency software recovery in smart switch. if i connect my phone switched on then smart switch discover my device but when i connect my device in download mode then smart switch says that device not supported. i contacted service centre but they say they do not downgrade the device.please please please someone help me. i am attaching a screenshot of odin stuck at nand write start.
Click to expand...
Click to collapse
Unfortunately you can't downgrade. Once you have flashed a higher bootloader version you are stuck with it.
If you are on bootloader v5 you may be able to downgrade to the last Oreo build, I am not 100% sure on that though.
Only if they are same bootloader
Sent from SM-N950U Still Rooted Note 8
stonedpsycho said:
Unfortunately you can't downgrade. Once you have flashed a higher bootloader version you are stuck with it.
If you are on bootloader v5 you may be able to downgrade to the last Oreo build, I am not 100% sure on that though.
Click to expand...
Click to collapse
Oh.... i checked my bootloader version is 6. Is there any way to downgrade to version 5 ????
No, there is not, sorry
Ok. So the final note is that i am not able to downgrade... so let me help with other issue that might help me. Knox on my device is tripped so i cant use latest samsung health app. Earlier on oreo i was able to install older version of app and then update it. But now on pie. Older version is not installing. It always says apk not installed. Atleast help me with that
drvish said:
Ok. So the final note is that i am not able to downgrade... so let me help with other issue that might help me. Knox on my device is tripped so i cant use latest samsung health app. Earlier on oreo i was able to install older version of app and then update it. But now on pie. Older version is not installing. It always says apk not installed. Atleast help me with that
Click to expand...
Click to collapse
You need to be rooted to be able to get that working again, some roms also have that patched already...
Although the thread is about the s7 I believe it is exactly the same for our note 8.
https://www.google.com/amp/s/forum....de-how-to-s-health-devices-knox-t3543306/amp/
stonedpsycho said:
You need to be rooted to be able to get that working again, some roms also have that patched already...
Although the thread is about the s7 I believe it is exactly the same for our note 8.
https://www.google.com/amp/s/forum....de-how-to-s-health-devices-knox-t3543306/amp/
Click to expand...
Click to collapse
I dont want to root again.... rooting will not let banking apps work.moreover if i wanted to root. Root files for note 8 pie are not available right now. I installed patched app but it does not have heart rate monitor and spo2 which renders heart rate sensor useless.... thats why i am so desperate for that app
drvish said:
I dont want to root again.... rooting will not let banking apps work.moreover if i wanted to root. Root files for note 8 pie are not available right now. I installed patched app but it does not have heart rate monitor and spo2 which renders heart rate sensor useless.... thats why i am so desperate for that app
Click to expand...
Click to collapse
As far as I am aware it is not possible without root.
drvish said:
I dont want to root again.... rooting will not let banking apps work.moreover if i wanted to root. Root files for note 8 pie are not available right now. I installed patched app but it does not have heart rate monitor and spo2 which renders heart rate sensor useless.... thats why i am so desperate for that app
Click to expand...
Click to collapse
Just use Magisk Hide to disguise, that you are using root
Reaper1337 said:
Just use Magisk Hide to disguise, that you are using root
Click to expand...
Click to collapse
I dont want to root. Moreover rooting files are not available for pie update.... so i think i am left with only 1 option to wait for someone to patch samsung health app to include heart rate sensors.....
drvish said:
I dont want to root. Moreover rooting files are not available for pie update.... so i think i am left with only 1 option to wait for someone to patch samsung health app to include heart rate sensors.....
Click to expand...
Click to collapse
You can flash TWRP, copy /system/build.prop to the PC or SD Card, edit it on the PC, put it back in /system.
Once you are done, just flash stock revovery via TWRP.
It sounds hard, but it's eazy if you know what you are doing. Banking apps will still work, and with build.prop edited s health will work too.
I am not gonna walk you trough the entire process but this is a summary.
Xenos7 said:
You can flash TWRP, copy /system/build.prop to the PC or SD Card, edit it on the PC, put it back in /system.
Once you are done, just flash stock revovery via TWRP.
It sounds hard, but it's eazy if you know what you are doing. Banking apps will still work, and with build.prop edited s health will work too.
I am not gonna walk you trough the entire process but this is a summary.
Click to expand...
Click to collapse
Thats the problem bro.... i downloaded twrp from official twrp website and tried to flash it. Odin message was pass but when i rebooted my phone in recovery mode my phone was still on stock recovery.... same thing happened with my galaxy tab.
I hope someone can provide me edited s health apk
drvish said:
Thats the problem bro.... i downloaded twrp from official twrp website and tried to flash it. Odin message was pass but when i rebooted my phone in recovery mode my phone was still on stock recovery.... same thing happened with my galaxy tab.
Click to expand...
Click to collapse
Oooh that, it's nothin.
You just need to hold volume up + bixby and power just before the phone auto restarts from download mode. When you do that it will boot twrp.
If you don't understand it go watch MaxLee on youtube, his method of flashing twrp on s8/n8
Xenos7 said:
Oooh that, it's nothin.
You just need to hold volume up + bixby and power just before the phone auto restarts from download mode. When you do that it will boot twrp.
If you don't understand it go watch MaxLee on youtube, his method of flashing twrp on s8/n8
Click to expand...
Click to collapse
So there is no other method except flashing twrp.... i think i have to wait for patched s health app or to leave that.... coz i really dont want to mess with stock firmware anymore....
drvish said:
So there is no other method except flashing twrp.... i think i have to wait for patched s health app or to leave that.... coz i really dont want to mess with stock firmware anymore....
Click to expand...
Click to collapse
The way I know it, there is no way without twrp or root, and you said you don't want root because of banking apps.
If you flash twrp, do the thing with build.prop, and then flash stock recovery, you could still recive OTA updates and banking apps will work.
You just have to set up s health before the next OTA because that will revert built.prop back to normal.
But as long as you set up s health before that it will be ok.
Xenos7 said:
The way I know it, there is no way without twrp or root, and you said you don't want root because of banking apps.
If you flash twrp, do the thing with build.prop, and then flash stock recovery, you could still recive OTA updates and banking apps will work.
You just have to set up s health before the next OTA because that will revert built.prop back to normal.
But as long as you set up s health before that it will be ok.
Click to expand...
Click to collapse
Leave that bro coz m not ready to do that. Just help me with 1 thing if possible. There was other way to use s health on knox tripped device. That was downloading s health 4.8 version install it and open it. It will stuck at loading screen. Update it and it will work fine. Earlier i get it working that way when my device has oreo version. But now after pie update when i try to install any s health apk before version 5 that is 4.5, 4.7 or 4.8. I always get a message app not installed. After version 5 app get installed but again with root problem. Can u help me with installing old version. I dont know why s health old version is not getting installed. I had some other apps that are now discontinued. That apps get installed easily
drvish said:
Leave that bro coz m not ready to do that. Just help me with 1 thing if possible. There was other way to use s health on knox tripped device. That was downloading s health 4.8 version install it and open it. It will stuck at loading screen. Update it and it will work fine. Earlier i get it working that way when my device has oreo version. But now after pie update when i try to install any s health apk before version 5 that is 4.5, 4.7 or 4.8. I always get a message app not installed. After version 5 app get installed but again with root problem. Can u help me with installing old version. I dont know why s health old version is not getting installed. I had some other apps that are now discontinued. That apps get installed easily
Click to expand...
Click to collapse
The reason you can't install the modded version is because the version that was modded is less than pre-installed version on the device. As of now, you can't downgrade apps, only upgrade. Your only option is to wait for someone to patch a later version from the version you got installed on your phone.
I think someone can even just change a number in AndroidManifest.xml install it and then just upgrade.
I'm sure a patched version will pop-up again somewhere on xda, just make sure it's later version than the version pre-installed into the system.
Xenos7 said:
The reason you can't install the modded version is because the version that was modded is less than pre-installed version on the device. As of now, you can't downgrade apps, only upgrade. Your only option is to wait for someone to patch a later version from the version you got installed on your phone.
I think someone can even just change a number in AndroidManifest.xml install it and then just upgrade.
I'm sure a patched version will pop-up again somewhere on xda, just make sure it's later version than the version pre-installed into the system.
Click to expand...
Click to collapse
Hmmm.... lets wait for some godman to do the favour..... i am from medical profession so dont know much abt this coding stuff. Otherwise i would have done that myself :laugh:
Hi all! So, you have a P8 lite in your pocket and you hate EMUI? Well, that was my case too, it's uncustomizable, ugly, and removes plenty of features from android stock. I do not like it one bit, and I like even less the fact that this phone is getting no more updates, ever. This sucks, it all sucks, luckily we can say "F all that" and do whatever we want with this device, provided you follow this guide.
I am making this guide because I want to condensate every single thing I know about this device in one single thread. One big guide to help all of you out installing custom ROMs. Without this, you would have to do research along multiple threads, often with conflicting information, and what's even worse, DEAD LINKS! There's nothing more frustrating than finally finding the solution to your problem, just one download away, just to be greeted by a dead link, and you would need to scout for another file that may or may not work... ugly stuff.
So, the point of this is to bring up to date info so you can make this device rock. This guide assumes you have Huawei's EMUI 4.0 installed which runs on Android 6.0. I'm also assuming you have your bootloader locked, and I will explain how to unlock it FOR FREE. No need to pay to some shady site in order to access what effectively belongs to you.
These are the requirements for this guide:
Code:
#USB cable
#A PC
#Some charge on the device to ensure nothing goes wrong
#An SD Card
#Patience
Before beggining, a quick disclaimer:
Code:
#It's not my objective to break your device, however there's always a risk when doing these kind of things.
#When you follow this guide's steps your are accepting the risks and are taking full responsiblity for whatever may happen to your device.
#Don't blame me for breaking your stuff if that happens, all I'm listing here worked for me, and should work for you.
#I won't be babysitting anybody to help solve their specific problems, don't PM me asking me why X doesn't work.
#I am unaware if this works in other versions of this device, but I'm positive this works on both ALE-L23 and ALE-L21
#If you have a "CAM-XXX" device, it's highly likely this works for you too, but as with everything, TRY AT YOUR OWN RISK.
#YOU HAVE BEEN WARNED!
Ok, so let's begin. As the title says, the guide is applicable to any custom ROM. However, I will be installing Lineage OS 14.1 which runs on (almost stock) Android 7.1.2. Regardless, the final step where we install the custom ROM is interchangable, and you can use whichever you please.
This process WILL wipe all of your data (except SD card). Make sure to make a backup of everything you want to save (app configs, photos, videos and whatever else).
1. DOWNGRADING TO ANDROID 5
As you may know, Huawei has stopped providing bootloader unlock codes for very stupid reasons. This has led to many unable to unlock their bootloader and having to pay for third party apps in hopes they don't get scammed. There are some trustworthy sites where you can get these at a fee tho (mainly DC Unlocker at 4 bucks), so if you want to pay up to avoid having to downgrade to Android 5, you can do so. However, I understand that you may not want to pay at all, I didn't want to either.
To get the bootloader unlock code, we need root, and to get root, we need Android 5. Why? Because getting root in Android 6 requires us to flash some zips, and for that we need TWRP, and for that we need an unlocked bootloader, everyhing closes up very nicely. So, we have no choice but to downgrade.
An SD card is not needed for this process, but it is going to be required at a later point, so why not use it now too?
NOTE: It may be a good idea to make a factory reset at this point, to avoid issues. For that, do the following:
Turn your phone off.
Boot the phone by holding the power button and the volume up button at the same time.
Wait untill the Huawei logo appears, then let go of both buttons.
You should be in recovery mode, navigate with the volume keys to the "Wipe data/factory reset" option.
Select it with the power button and wipe everything.
Reboot the device with the option in the menu.
Once the device has booted up, follow the guide.
Alright, once that's done, connect your phone to the PC to transfer some files:
NOTE: There's two Stock Android 5s downloads ("HW_Android_5_Transition.zip" and "HW_Stock_Android_5.zip"). One is a transition package, as the name implies, and the other is Huawei's EMUI 3.1 in all of it's glory. What's the difference? The transition package is a much smaller file that is designed to downgrade the phone from EMUI 4.0 (Android 6) to EMUI 3.1 (Android 5). If you are running EMUI 4.0 (which should be the case) then you can use the transition package which will take less to download. If you have another version (i.e. EMUI 4.1) you should use "HW_Stock_Android_5.zip". However, the latter is the safe bet. If you are not sure which one to use, use "HW_Stock_Android_5.zip". The process is exactly the same for both packages.
Extract the "UPDATE.APP" file from "HW_Stock_Android_5.zip" or "HW_Android_5_Transition.zip".
Navigate to your phone's internal memory or SD card (whichever you want to use) and locate a folder called "dload". If there's not one, create it.
Put the "UPDATE.APP" file inside of the "dload" folder.
Turn your phone off.
Once it's off, press the power button and the two volume buttons until you see the Huawei logo.
That should make the phone recognize the "update" and start flashing it. Once it finishes, it will try to boot by itself, so pressing those 3 buttons was your last input until the phone boots into Android 5. It will take a long time for it to both finish and boot, don't be afraid, the phone is not bricked. If you think the phone is indeed bricked because it has been stuck at the logo screen for way to long (longer than an hour) then proceed to the "Unbricking" section of this guide. However, it's highly unlikely that this will happen, as Huawei checks the file before flashing it, so if it's incompatible with your device it should not do anything and boot again into Android 6 with everything untouched.
2. ROOTING ON ANDROID 5 AND EXTRACTING BOOTLOADER UNLOCK CODE
Once you are in Android 5, we will need to root the device. Download KingRoot (proved to work) or another one click root app of your choice. I'm aware of KingRoot's bad reputation because of the spyware accusations, but the phone will be wiped anyway and we are sure it works, so it doesn't really harm at all. If you still don't want to use it, check with other apps, I haven't done so myself so I don't know what else works.
Once your phone is rooted, we will need to use the terminal for the first time. We will need to setup ADB and Fastboot, if you already have that, skip this step.
Extract the "platform-tools" folder from the zip and place it somewhere nice.
Shift right click on a blank space INSIDE of the "platform-tools" folder.
Select "Open command window here".
This should be enough to get ADB working, but we need to make some config on the phone itself too.
Go to Settings -> About Phone
Look for a line that says "Build Number" and tap it multiple times.
When the message saying "You are now a developer" pops up, go back and enter the new "Developer Options" menu.
In there, look for an option called "USB Debugging" and turn it on.
Connect the phone to your PC via USB cable.
A message should have popped up on the phone asking for permission to use USB Debugging, tap on "Always allow from this PC" and then on "Allow".
NOTE: If the message doesn't pop up, you can try a number of things. I prefer to tap the "Revoke USB debugging authorizations" button to ensure that no PC is authorized, so the message must pop up at some point. Once you revoked authorizations, disconnect and connect the phone again, if you still don't see it, try to select MTP as the transfer protocol. If not, then PTP, if you still don't see it install Hi Suite on your PC and open it, it should pop up now.
Once you have everything working, type the following in the terminal in your PC:
Code:
adb devices
If you see a serial number there, that's your phone, and that means everything is set up correctly (make sure you don't have any other device attached to your PC, or you could confuse the two and make bad stuff happen for that other device). If you don't see it, make sure USB Debugging is enabled. You can try to use different cables if you still have problems. Now type:
Code:
adb shell
And then:
Code:
su -c "grep -m1 -aoE 'WVLOCK.{14}[0-9]{16}' /dev/block/mmcblk0p7 |grep -aoE '[0-9]{16}'"
KingRoot (or the app you used to root) should prompt you (in your phone) if you want to give ADB root access, make sure to allow it to make this work. This should give you your unlock code. SAVE IT INTO A TXT FILE AND COPY THAT FILE TO ALL OF YOUR PCS, ALL OF YOUR CLOUD ACCOUNTS AND ALL OF YOUR MOBILE DEVICES.
(Maybe the terminal gets stuck at this point, press CTRL + D (or C) to get it unstuck).
Seriusly tho, it didn't happen to me, but it is a possibility that your Bootloader can re lock after doing some of the things that follow, in which case you will need to unlock it again, and if you don't have that code... it's back to square one.
3. GOING BACK TO ANDROID 6
Now that we have done all that we wanted on Android 5, it's time to go back. The process is exactly the same.
Extract the "UPDATE.APP" file from the "HW_Stock_Android_6.zip" file and move it to the dload folder (SD card or Internal).
Turn off your phone and turn it on again with all three buttons pressed.
Wait.
???
Profit.
So, we're back on Android 6. Why did we go back you may ask? Why did we not just flash our precius custom ROM? Well, for once, this gives people the chance to stay on EMUI if all they wanted was to unlock the bootloader and maybe root on Android 6 (which I will explain how to do too, in case you want to). Another, more important reason, we need Android 6 to install the B895/B896 update, which is a requirement for any custom ROM (mainly Android 7.0+) if you don't want any problems with your SIM card (and others that may arise).
4. UNLOCKING BOOTLOADER AND FLASHING TWRP
Now, we need to turn on USB Debugging again, and to allow our PC... again. Do so, and check that everything is right with:
Code:
adb devices
If that's the case, then type the following:
Code:
adb reboot bootloader
Your phone will reboot, and you should see a white screen with a wasted android above a green text saying "PHONE LOCKED". If that's the case, take a moment to say goodbye to that green text, because it will soon turn very red. We will need to unlock the bootloader with the code you got from the previous steps, for that type the following:
Code:
fastboot oem unlock ****************
In place of the "****************" you must enter your code, of course. And that was it, now the green text is replaced with a red "PHONE UNLOCKED". This are good news. Now, we need to flash our custom recovery if we want to do anything fancy with the device. For that, extract the "recovery.img" file from the "TWRP_3.1.1.zip" file and paste it into the same folder where all of the ADB files are located (where "adb.exe" is). Now type:
Code:
fastboot flash recovery recovery.img
This will flash TWRP into your device, hooray! Now type:
Code:
fastboot reboot
And your device should turn back on, today is a bright day my son. Now you must take a decision, do you want to flash a custom ROM and get very nice and fancy features or do you want to stay with what you have? If you prefer Huawei's EMUI 4.0, then follow to the next step. If you want to flash custom ROMs, then skip the next one.
5. ROOTING ON ANDROID 6 (OPTIONAL)
I don't know why you would prefer EMUI over... anything else really, but it's your call. I'll tell you how to root it so you can at least take some advantage of it. You see that file called "HW_Android_6_Root.zip"? Extract it, inside there will be... another folder called Root... huh? Redundant. Anyway, inside of that there should be two zips. 1.zip and 2.zip. You will need to place the folder called "Root" inside of your SD card or your internal storage. Then, go back to the terminal and type:
Code:
adb reboot recovery
You should reboot into TWRP, isn't it nice? Anyway, we have to flash some zips! Go to "wipe" first and wipe the "Cache" partition and the "Dalvik" partition. Once that's done, go to install and navigate to the Root folder your placed... well, you know where. Select 1.zip and flash it, once it's finished reboot the device. If TWRP prompts you to install it's app, DO NOT DO IT. Once the phone has rebooted (it will take longer because of the cache and dalvik wipe), repeat the process but flash 2.zip this time, reboot and your phone should be rooted. This is the end of the line for you now, as you don't want to make anything else to the phone. However, you can go to the final chapter where I explain how to install Xposed framework, if you want more customization. EMUI doesn't like Xposed very much, so there's little you can do with it, but it's something I guess.
6. INSTALLING THE B895/B896 UPDATE
So, you followed the power user path, the one we all really want deep down. That's cool, I respect you. We gotta use that custom recovery we just flashed, but first we need to transfer some files into our phone's memory. We need to install an update to the phone, for which you need Android 6 (that you should already have anyway). There's two different updates, B895 and B896. As you may guess, B896 is newer. However, any of these two will (or rather should) work without issues. I personally used B896, but some people claim B895 is more stable. I can't find a difference really, but the process is the same regardless of which you choose. Once you have made that decision, move "B895_update.zip" or "B896_update.zip" to your phone's internal storage or SD card AS IS (don't extract it). Then type into the terminal:
Code:
adb reboot recovery
You should be in TWRP now. Go to wipe and select the "Cache" and "Dalvik" partitions ONLY, then wipe them. Once that's done, go to install and flash your update of choice. Once finished, reboot the device. If TWRP prompts you to install it's app, DO NOT DO IT. The boot should take longer than usual because of the "Cache" and "Dalvik" wipe... and because of the update too. Once booted, you should be in EMUI 4.1. Go to settings and into "About Phone". In there, look for a field called "IMEI". If you see a number, that means you did everything properly, if you see "unkown" or nothing at all, then that means you lost your IMEI... which means you will have connectivity issues. To fix this, you will need to do a full wipe (so, boot into recovery (we lost TWRP due to the update) and then go to wipe, in there select everything except SD card) and follow the steps again starting from 3, this time flashing the other update (so if you flashed B895, flash B896 this time and vice versa)).
Now, this last step we made has wiped our custom recovery... so sad. We have to flash it again, but we are almost finished!! Now it's time for you to move the custom ROM you want to your SD card (SD card is mandatory, as we will wipe internal storage). You should also move your custom ROM of choice. If you want root, also move the "SuperSUv82.zip" file.
OPTIONAL:
If you want Gapps, that means the Google apps, so PlayStore, Google services and such (and you really should want them, as Android without PlayStore is kinda rough), then you need to download them separately.
So, go to the Gapps website and select the pacakge you want. You NEED to choose the ARM64 platform, the android version depends on the ROM you are flashing, so check which version it runs, and the package itself is personal preference. Here you can see a comparison of each package, detailing what each one contains so you can make a decision. The aroma package is kinda bugged, I would avoid it. Choose wisely, as flashing another Gapps package once you have flashed a different one can and most likely will cause issues. If you want my opinion, I would stick to the nano package. It offers the basic Google functionality and allows you to download other Google apps you may need/use with the PlayStore once you are booted up.
Once you choose your package, move it to your phone's SD card along with the ROM and the SuperSU zip if you want it.
Check that USB Debugging is still enabled, and then type:
Code:
adb reboot bootloader
Once into the bootloader, flash the custom recovery once again with:
Code:
fastboot flash recovery recovery.img
Then:
Code:
fastboot reboot
Once booted up again, type:
Code:
adb reboot recovery
And now it's time to drop the bomb, say bye bye to EMUI, and say hello to... whatever it is you are installing.
7. FLASHING YOUR CUSTOM ROM OF CHOICE
MOST CUSTOM ROMS REQUIRE AN LTE CAPABLE SIM IN ORDER TO HAVE CELLULAR NETWROK WORKING CORRECTLY, THIS DEPENDS ON A ROM TO ROM BASIS, DO YOUR RESEARCH BEFORE FLASHING
Once in TWRP, go to wipe and check every box, I'm serius, check everything except the SD card. Once that's finished, the moment of glory has come. Go to install and flash your ROM. It will take a while, and when that's done reboot. The phone should boot into your ROM. If you want either Gapps or SuperSU, make a quick setup and enable USB Debugging again, then reboot to recovery with:
Code:
adb reboot recovery
Once in TWRP, go to install and flash the Gapps package and the SuperSU zip (in that order) if you want it. Reboot. That should be it! You are done!
8. UNBRICKING
I don't know why, but with all the flashing and the testing I've done you would have thinked that I should have suffered of a brick state at least once... that was, luckily, not the case. I haven't suffered a single brick. I don't know if I'm extremely lucky or if this phone is tremendously resilient, but the case is I haven't had any issues of this kind.
However, I can understand that it is a possibility, so if this happens to you my best advice is to do the following: Boot into recovery mode (either stock or TWRP depending on where in the whole process you got stuck), make a full wipe and apply the update from "HW_Stock_Android_6.zip" with the dload folder and the three buttons method. That should get it unstuck, if not... try the same with the "HW_Stock_Android_5.zip" 's "UPDATE.APP".
9. INSTALLING XPOSED FRAMEWORK (OPTIONAL)
What? A custom ROM is not enough for you? Getting freed from EMUI is not enough? Well fear not then, because there's one last step for the true power user, for that man who thinks that everything is not enough, the good old Xposed Framework *queue fireworks and trumpets.
So, you need to install the Xposed Installer apk. Get it from here, and ONLY THERE. I once installed an apk from another source... ended up being adware, not fun. The apk is at the very bottom of the thread. You will also need the framework itself, get it from here.
Get the latest (arm64) version for your ROM. This depends on what Android version it is running on:
Code:
SDK21 = Android 5.0
SDK22 = Android 5.1
SDK23 = Android 6.0
SDK24 = Android 7.0
SDK25 = Android 7.1
SDK26 = Android 8.0
SDK27 = Android 8.1
You should also get the uninstaller in case things go south.
Once you got the files, install the apk on your phone. Open the app once. Transfer the framework and the uninstaller into your SD or internal storage. Boot into TWRP recovery and install the framework, reboot the device.
NOTE: Android 6.0 takes about 20 mins to boot, wait about an hour before deciding that it's bricked. Android 7.1.2 took me about 2 mins. I'm unaware of the boot times of other versions, but be aware that it can take LONG. If you think it really got bricked, boot into TWRP again and flash the uninstaller. That should get it unstuck and you can either try again or leave it as is.
----------------------------------------------------------------------------
Well guys, that's all I got, quite a big write up huh? I don't really have nothing else to say, just remember that what you are doing here is at your own risk and I don't want anybody blaming me for the bad things that can happen. I will proceed to leave you with the download links so you can try this yourself. I'm currently running Lineage OS 14.1 which features Android Nougat 7.1.2 on my Huawei P8 lite ALE-L23, I've never been happier to be free from the manufacturer's ROM.
DOWNLOADS
(The B895 and B896 update's links are not mine)
Huawei's Stock Android 5:
Android Filehost
Mediafire
Huawei's Android 5 Transition:
Android Filehost
Mediafire
Huawei's Stock Android 6:
Android Filehost
Mediafire
Huawei's Android 6 Root:
Android Filehost
Mediafire
EMUI 4.1 (B895):
Android Filehost
EMUI 4.1 (B896):
Android Filehost
Platform-Tools:
Android Filehost
Mediafire
TWRP 3.1.1:
Android Filehost
Mediafire
Gapps:
Open Gapps
SuperSU:
Android Filehost
Google Drive
Hi,
I didn't understand what do you mean whan you write: Once booted, you should be in EMUI 4.1. If you retained your IMEI, you are in good path, if not... then do a factory reset (wipe everything) and repeat the steps starting from 3.
Could you explain it better?
Thank you
ilmatte said:
Hi,
I didn't understand what do you mean whan you write: Once booted, you should be in EMUI 4.1. If you retained your IMEI, you are in good path, if not... then do a factory reset (wipe everything) and repeat the steps starting from 3.
Could you explain it better?
Thank you
Click to expand...
Click to collapse
Yes, it's basically this: If you go into the "About Phone" section you will see that there's a field detailing your IMEI. I won't lie, I don't know exactly what it is, but it's a unique number for every phone and has something to do with your cellular network connection.
If you messed up at some point, you can lose your IMEI (i.e. you won't see it in that field or it will say "unknown" or something of the sort). If that happens, then it means you did something wrong, and proceeding in this state will make you have problems with your connection. The signal would be really unstable and it would be practically unusable.
To make a simpler check, if you have a cellular network connection, and can make calls and send/receive SMS on EMUI 4.1, then you won't have any problems.
Ah ok it wasn't so clear but I know what an imei is luckily it didn't erase it in my case. Anyway, I don't know how to thank you bro! You saved my life. I beleived to be screwed when I learned that Huawei stopped releasing the bootloader unlock code. How stupid they are. I blamed them through the customer support. I'm running lineage now! Kiss my ass Huawei!
ilmatte said:
Ah ok it wasn't so clear but I know what an imei is luckily it didn't erase it in my case. Anyway, I don't know how to thank you bro! You saved my life. I beleived to be screwed when I learned that Huawei stopped releasing the bootloader unlock code. How stupid they are. I blamed them through the customer support. I'm running lineage now! Kiss my ass Huawei!
Click to expand...
Click to collapse
Glad to hear I helped! Mind dropping a thank on the main thread? Hope you enjoy your phone
Thanks <3 -notes
Thank you tralph3, you make my life so easy, great easy guide. I have a few suggestions for improving clarity:
Step 1. "Stock_Android_5.zip" contains "transitional" android 6.0 ALE-L21C900B500 firmware According to including Spanish documentation "3., 3.1 Download the Android5.0 update package" It must be downloaded another 5.0 firmware. I use this 5.0 firmware to make kingroot preform root.
Firmware: huaweidl.com/download/p8-lite/ale-l21/b204/
Look for a line that says "Compilation Number" and tap...
Click to expand...
Click to collapse
Step 2. second point 2. Change to "Build Number"
su -c "grep -m1 -aoE 'WVLOCK.{14}[0-9]{16}' /dev/block/mmcblk0p7 |grep -aoE '[0-9]{16}'"
Click to expand...
Click to collapse
Step 2. getting unlock code. After executing command. Add step -Kingsroot display root access prompt ALLOW it.
t
Thanks for your work.
BelisTT said:
Thank you tralph3, you make my life so easy, great easy guide. I have a few suggestions for improving clarity:
Step 1. "Stock_Android_5.zip" contains "transitional" android 6.0 ALE-L21C900B500 firmware According to including Spanish documentation "3., 3.1 Download the Android5.0 update package" It must be downloaded another 5.0 firmware. I use this 5.0 firmware to make kingroot preform root.
Firmware: huaweidl.com/download/p8-lite/ale-l21/b204/
Step 2. second point 2. Change to "Build Number"
Step 2. getting unlock code. After executing command. Add step -Kingsroot display root access prompt ALLOW it.
t
Thanks for your work.
Click to expand...
Click to collapse
Thanks for pointing this stuff out, I'll make those changes you suggested and try to fix some typos too. So, what I gather from what you told me about that Android 5 thing is that in order to correctly flash the update I'm providing you NEED to be in Android 6, right? Whereas with the one you are providing me it should boot into Android 5 regardless of what you currently have. If that's the case, I'll include both and tell people of the distinction between the two so they can use the one they want/need (after all, the transition package is much smaller and easier to download). I'll download the package and upload it to Android Filehost along with everything else. I think I'll keep the mediafire downloads as a mirror. I'll get to that, thanks.
tralph3 said:
.... in Android 6, right? Whereas with the one you are providing me it should boot into Android 5 regardless of what you currently have.
Click to expand...
Click to collapse
Yes, exactly. Thanks for curating this additional download, good idea.
Does this also work for the PRA-LX1 version?
I have Android 8.0 on it and absolutely no idea what EMUI version or eben the firmware version.
I want to put crDroid on this phone because EMUI ... you know, it's bad.
Otherwise: I am ok with paying these 4€ if this payed unlock works.
WHICH of all these DC Unlocker Apps do I need for getting the unlock code?
Badoolo said:
Does this also work for the PRA-LX1 version?
I have Android 8.0 on it and absolutely no idea what EMUI version or eben the firmware version.
I want to put crDroid on this phone because EMUI ... you know, it's bad.
Otherwise: I am ok with paying these 4€ if this payed unlock works.
WHICH of all these DC Unlocker Apps do I need for getting the unlock code?
Click to expand...
Click to collapse
DON'T TRY ANY OF THIS. All of what I've detailed is for the P8 lite 2015, your phone is a different 2017 version that's basically another completely different phone with the same name, because Huawei doesn't know how to namr their devices. You have a different chipset, doing anything of what's described here will most likely brick your phone. With that said, maybe the bootloader unlock method works IF YOU FIND ANOTHER WAY TO ROOT YOUR PHONE. DON'T ROLL BACK TO ANDROID 5 WITH THE FILES I'M PROVIDING PLEASE.
This forum is dedicated to P8 lite 2015, you can see there's a different forum for 2017. Good luck.
Hello, I have ALE-L21 with EMUI 4.0.3 - MM 6.0 - version B633 and i can not downgrade to android 5, phone says : update failed, or stuck on 5%. could someone help me please ?
I tried a lot of stock ROMs, 5.0 , 6.0 etc, nothing worked for me.
Thanks,
Ax1qwer said:
Hello, I have ALE-L21 with EMUI 4.0.3 - MM 6.0 - version B633 and i can not downgrade to android 5, phone says : update failed, or stuck on 5%. could someone help me please ?
I tried a lot of stock ROMs, 5.0 , 6.0 etc, nothing worked for me.
Thanks,
Click to expand...
Click to collapse
Are you using the stock package or the transition package? If you are using the transition package, try stock.
I tried both, with no success. And many others.
I tried to update via internal storage and SDcard too, with no success.
If phone is connected to pc, updating stuck on 5%, if not connected to PC, update fails.
Ax1qwer said:
I tried both, with no success. And many others.
I tried to update via internal storage and SDcard too, with no success.
If phone is connected to pc, updating stuck on 5%, if not connected to PC, update fails.
Click to expand...
Click to collapse
Did you wipe all of your data with the stock recovery? If nothing works then I could suggest you to try to apply the downgrade with sideload. (Boot into recovery and select to apply update from adb, then you type adb sideload <filename>)
I'm clueless on why it doesn't work on your device, it should.
Also, you can try to flash the stock android 6 rom first, that's an older emui version (4.0). If you can flash that, then maybe you can flash android 5 after it.
i have tried intalling both the 5.0 stock roms but it always fails at 5%. i got ALE-L21C02B896 with emui 4.1 and android 6.0. i've been trying different guides but all lead me to dead ends. please help
thanks in advance
Wazu786 said:
i have tried intalling both the 5.0 stock roms but it always fails at 5%. i got ALE-L21C02B896 with emui 4.1 and android 6.0. i've been trying different guides but all lead me to dead ends. please help
thanks in advance
Click to expand...
Click to collapse
I have the exact same firmware(ALE-L21C02B896) that you have and I also cant downgrade to android 5.0 using any of the tutorials that I found in XDA Furum.
razorfancy said:
I have the exact same firmware(ALE-L21C02B896) that you have and I also cant downgrade to android 5.0 using any of the tutorials that I found in XDA Furum.
Click to expand...
Click to collapse
Yeah it very frustrating, please let me know if you find a way and ill do the same.
Wazu786 said:
Yeah it very frustrating, please let me know if you find a way and ill do the same.
Click to expand...
Click to collapse
Told you guys, try to flash android 6 and see if that works, afterwards you can flash android 5.
tralph3 said:
Told you guys, try to flash android 6 and see if that works, afterwards you can flash android 5.
Click to expand...
Click to collapse
I tried your Huawei's Stock Android 5, Huawei's Android 5 Transition and Huawei's Stock Android 6 and all failed to install giving error at 5 percent.
tralph3 said:
Told you guys, try to flash android 6 and see if that works, afterwards you can flash android 5.
Click to expand...
Click to collapse
i tried android 6 also and it also failed at 5%, please is there anything else i can try?