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.
XZ/KAGURA/F8331 OmniROM BUILDS
PIE 9.0
DOWNLOAD WEEKLY
REQUIREMENTS TO SUCCESSFULLY FLASH OMNIROM:
1. The device has the latest stock ftf
2. The device has an unlocked bootloader
3. The ODM image zip (version 9) has been downloaded from HERE, and the ODM image has been extracted from it
4. The WEEKLY zip file has been downloaded and copied to the device
INSTALLATION INSTRUCTIONS:
1. Reboot device to fastboot mode, and flash the ODM image with this command
Code:
fastboot flash oem <ODM image>
2. Reboot device to TWRP and flash the WEEKLY zip file
3. (If coming from an 8.1 ROM) Fix /dsp SELinux labels with the dsp-label-fixer.zip
4. (Optional) Flash a gapps package
5. Reboot device to system
CURRENT ISSUES ON OFFICIAL:
1. Device wakes up by itself every 5 seconds, reason unknown
2. Camera quality is suboptimal
KERNEL SOURCE: https://github.com/omnirom/android_kernel_sony_msm/tree/android-9.0
BUG REPORTS
REPORT BUGS ONLY:
- AFTER A CLEAN INSTALL
- USING STOCK OMNI KERNEL
- NO MODS OF ANY SORT
OMNI GERRIT REVIEW
https://gerrit.omnirom.org/
DISCLAIMER:
No one is responsible for any damage done to your device but YOU. You've been warned.
XDA:DevDB Information
[ROM][XZ][P][9.0][WEEKLY]OmniROM, ROM for the Sony Xperia XZ
Contributors
oshmoun, humberos, local__hero
Source Code: https://github.com/omnirom
ROM OS Version: 9.x Pie
ROM Kernel: Linux 4.x
ROM Firmware Required: latest stock ftf
Version Information
Status: Beta
Created 2019-03-17
Last Updated 2019-05-31
Thank you for the separate this from the other pie roms.
I will flash it after I arrive home.
Thank you all for the hard work!
Sent from my kagura using XDA Labs
I'm loving the fact Omnipie is official. I will be flashing this right now. Thank you so much.
Finally flashed! been using it for less than an hour, i can say that its definitely good for daily use. Camera seems better and hasnt crashed yet (like it use to), mic actually picks up audio properly, brightness slider is finally proportional to the brightness level, and its pie
however, the stereo speaker seems to muffle at high volumes (especially with the ringtones and less with youtube, but still a little prevelent), app opening times seem a little longer than 8.1, and 120HZ still doesnt work
im also curious why the linked odm isnt the latest one (im pretty sure the latest is 1st march not feb)
anyways, thanks dev! (may be editing this thread after more use for battery etc)
XxperexX said:
however, the stereo speaker seems to muffle at high volumes (especially with the ringtones and less with youtube, but still a little prevelent)
Click to expand...
Click to collapse
Could it be this kernel bug: https://github.com/sonyxperiadev/bug_tracker/issues/336 ? Looks like the sonyxperiadev team is working on it.
XxperexX said:
im also curious why the linked odm isnt the latest one (im pretty sure the latest is 1st march not feb)
Click to expand...
Click to collapse
The March 1 release says "Android 8.1", the linked one looks like the latest for Pie.
sinivalas23 said:
Could it be this kernel bug: https://github.com/sonyxperiadev/bug_tracker/issues/336 ? Looks like the sonyxperiadev team is working on it.
The March 1 release says "Android 8.1", the linked one looks like the latest for Pie.
Click to expand...
Click to collapse
Ah, your correct it does say 8.1 my bad
opps
I saw this version from delta updater (using 8.1 omni) and immediately downloaded flashed oem for pie and downloaded omni 9 but it stucked new omni animated logo. Waited like 10 minutes but nothing happened then rebooted phone but same thing happened. Should i wait more or something went wrong?
Im here with OmniROM freshly flashed trough Open Delta.
I have some problems. First boot never ends, BUT restart worked for me but I have another problem.
Now I need 10 min to unlock the phone when Im lucky.
I unlock with the code and then its instantly relock and it say I cant use fingerprint for first unlock, so I use code again and not work again and still can't use fingerprint.
I do this A LOT OF TIME before I can use my phone. Sometimes it helps sometimes not if I not unlock my phone but use corner dial icon first and then if its ask for code i use it and then I got SystemUI crash error again and again and again.
As I said I try to repeat this methods for like 10 min after every restart. I tried to delete some maybe not compatible apps with this new update but still nothing. Now I will remove some Magisk modules. I will write again.
KikiGames said:
Im here with OmniROM freshly flashed trough Open Delta.
I have some problems. First boot never ends, BUT restart worked for me but I have another problem.
Now I need 10 min to unlock the phone when Im lucky.
I unlock with the code and then its instantly relock and it say I cant use fingerprint for first unlock, so I use code again and not work again and still can't use fingerprint.
I do this A LOT OF TIME before I can use my phone. Sometimes it helps sometimes not if I not unlock my phone but use corner dial icon first and then if its ask for code i use it and then I got SystemUI crash error again and again and again.
As I said I try to repeat this methods for like 10 min after every restart. I tried to delete some maybe not compatible apps with this new update but still nothing. Now I will remove some Magisk modules. I will write again.
Click to expand...
Click to collapse
you need to do a full wipe before upgrading to p
Just as @oshmoun said; before flashing new ROMs, it's imperative to do full wipe (if you don't want to lose all your data, then do a full backup in TWRP), as flashing without full wiping can cause TONS of problems. Don't be lazy and follow the instructions properly.
oshmoun said:
you need to do a full wipe before upgrading to p
Click to expand...
Click to collapse
I used the same rom before but the last update. I updated through OpenDelta.
Hello !
It's cool to see our XZ is alive !
I have some problems with this rom after a full wipe and update to oem V6 :
- no sounds during calls, no mic, no earphone, no sounds on speaker
- Magisk 18.1 not working
- With official camera app, while using the flash, only the autofocus led is lit, the second and much powerful led is never triggered resulting on dark shots
For now that's all
Thx
Performance is somewhat distressed and the camera does not work for the sound is not working after restarting the device is improving
KikiGames said:
I used the same rom before but the last update. I updated through OpenDelta.
Click to expand...
Click to collapse
you cant do that. its pretty misleading having it available on that opendelta ota thingy. you have to follow the instructions in this thread
Flashed data, cache and dalvik, factory reset. And installed latest nightly with gapps and magisk 18.1.
Only reason I did it this way is because I was on a unofficial build on Omni. Everything is working as it should. Very snappy and no lag. Still have to see how the ROM handles after it's settled for a couple day, but right off the bat it's amazing. Thank you very much Dev, and happy to see you back on XDA.
XxperexX said:
you cant do that. its pretty misleading having it available on that opendelta ota thingy. you have to follow the instructions in this thread
Click to expand...
Click to collapse
Why this ROM showed up as an update then?
I just don't understand it.
Nevermind this is my main and only phone and I work 4 days straight before I can use my PC so I need to use this ROM buggy for me. :/
KikiGames said:
Why this ROM showed up as an update then?
I just don't understand it.
Nevermind this is my main and only phone and I work 4 days straight before I can use my PC so I need to use this ROM buggy for me. :/
Click to expand...
Click to collapse
You need a PC to flash this. Follow all steps in order and it'll work. Always remember, unless you have a messaging app that backups texts, you will lose them flashing a cfw. Always always backup anything you don't want to lose.
---------- Post added at 12:56 AM ---------- Previous post was at 12:28 AM ----------
I've had a reoccurring issue on the unofficial and official builds so far. I do not have the option to use my phone when calling unless speaker phone or a Bluetooth headset. I cannot put the phone to my head and use normally. Is there any kind of option to fix this nuisance. Any feedback is truly appreciated
Every 9.0 ROM I ever flash, I always seem to have the same problem. Whether its dirty flashing, or starting with flashtool, to CMD, and then to TWRP, the same problem seems to happen. After the ROM has settled, audio quality through calls becomes a huge problem. I'm not sure if I'm doing something wrong, but it has been a persistent bug, next chance I get for the next nightly ill send a logcat, kinda cant not since back on stock. I need good call quality for work lol. Either way, thank you for bringing OMNI to 9.0 official
anyone having problems with video playback? videos dont play on instagram, youtube or snapchat. using magisk 18.1 and latest omni 9 rom
edit: nvm, found out that the Google camera fix module for magisk was the problem
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?
Android Version : MIUI-11-EU-PIE Easy recovery install.
You should be having proper knowledge of flashing Custom ROM and how to Restore a phone if anything goes wrong.
Take complete backup before taking any action based on this thread. I am not responsible for any action taken by you.
I am just compiling all the information / files available on different websites into this thread, I have patched together with cyber spit, bubblegum, and tape, for a pretty much fully working MIUI-11--EU-PIE running rom. With the help from Mohzuned. I have removed what I believe to be all of the bloat. We worked to modify a working pie vendor. Magisk v20 modified boot for root access, Just install magisk manager.
All Credit goes to respective developer/s. I request XDA moderator and or Developer of Respective files to let me know if I have forgotten to mentioned (give credit) their name in this thread. The Download Links are given directly from respective Developer/s.
You need the following two files to Test MIUI-11-EU-PIE on Mi Max 2 (Oxygen). This ROM recovery is ported from the Xiaomi RedMi with many patches and customized from various sources. This ROM maybe Stable enough for your daily use on Mi Max 2. I have access to two MM2 4/64 Global versions using a 1tb sd card one on At&t the other on Tmobile and MOST features I need are currently working.
1a. Treble Mi Max 2 Recovery 3.2.1 https://androidfilehost.com/?fid=5862345805528056270
1b. OrangeFox Recover 10
https://sourceforge.net/projects/ora...n.zip/download
2. MIUI-11-EU-PIE
https://drive.google.com/file/d/15lRb49s75rqVV0Kg8C16Eao_BuTPvBWr/view?usp=drivesdk
First step:
Start your phone into recovery and Flash a Treble recovery, if already not flashed. Restart into Recovery.
Click Wipe then Advance wipe and clear System, Vendor, Boot, Data, Cache, and Dalvick cache.
Second step:
Now Extract the Downloaded Rom files in Recovery backup folder. You should know where and how to Extract. (Use extract tool for android or pc then copy paste to recovery backup folder.)
Third step:
Click Restore and Select System, Boot, Vendor and Swipe to confirm. Wait for restore to complete. If any errors, Reboot recovery and try again. Or Mount the System, Vendor, Boot and try again. After Restore completes Reboot. Please allow 1-2 Minutes for first boot.
What works:
?
What doesn't work:
?
If I missed anything in the above, kindly let me know to include. If you make any further updates / patches that makes this ROM more stable / perfect or enables new features, please don't hesitate to message me to include in this thread.
I have an old PC running windows with 8gb max HDD at any one given time, So if you would like to make the recovery image into a flashable zip, I'd be happy to update/add it.
If you can afford it, Im trying to save for a computer from this decade, any help is appreciated
https://www.paypal.me/LiamMcGinnisIv
If you would like to use the boot, vendor, system, or any other files, All I ask is pass on the proper credits.
Any Others Who May Have Been Missed
Best of Luck and Happy Flashing )
Camera/Torch.
Camera, fingerprint and fm radio, dont work, congratulations, good rom. Thanks.
Cool....... thanks dude
liammc83 said:
Camera/Torch.
Click to expand...
Click to collapse
Iam ready for the test ride......
I will test today. Thank you for your job!
Beast developer...too fast man thanks
If you will fix Camera and Torch it will be great! We are all waiting! Thank you!
---------- Post added at 06:51 AM ---------- Previous post was at 06:38 AM ----------
May be it is better to do Port from Mi Mix 2S? Camera and Torch worked on that port.
Bro.......
I cannot find the fingerprint option in the rom..?
Firstly I upgraded from the nougat rom.,it made me to suck....it booted but instantly rebooted to recovery on every boot......
Cannot find the fingerprint option ..,Cannot add the face unlock option due to the camera bug...,it's harder always using pattern/pin.,? flashlight ? issue is negligible.....
But mi cloud has no issues and working fine able to login..
Home button isn't working.,full screen guesture option isn't seen in the rom..
May be it's because of the redmi note 4x....it might be good if it's from max3 or mix2s as u done previously.,only hotspot bug majorly
You are too good bro....,you are beastly fast and tough..,???
Please fix the camera!!!
zavorotnii said:
Please fix the camera!!!
Click to expand...
Click to collapse
He is trying continuously and I believe soon it will be resolved.
zavorotnii said:
Please fix the camera!!!
Click to expand...
Click to collapse
I'm not screaming "Donate!!!!!"
I do this for free for a phone I no longer use, please be patient.
Considering all sources from xiaomi are outdated, And this is being done again for FREE with modifications on an ancient netbook.
I also can now verify, I have a working modified vendor/boot image that will run gsi images, But again since problems with vendor no camera, Still working on it.
Sorry, I just asked. I understand your position and ready to test new changes
No need to wait for me to port.
https://forum.xda-developers.com/mi-max-2/development/mi-max-2-oxygen-gsi-bootable-vendor-t3987191
I really liked this rom .. I want to use daily ... only thing that is bothering me is the home button and the camera that is not working? already have a solution? fingerprint to taste .. but you can use with the pin normally
Hi Guys,
Ever since GSI support has been introduced for the Asus ROG Phone 2, I've been experimenting with the possibilities of what works on the Asus ROG Phone 2.
Since OxygenOS has been a major favorite of mine, I decided to download ErfanGSI's port of OxygenOS-Android9-AB.
However, the final result is no where near daily usage.
Here's what works.
-Calls
-Messaging
-Chrome
What doesn't work
-Google Play Store
-Settings ( The main settings section isn't launching, although, if you tap and hold the icons in the status bar, the Wifi settings and stuff works fine, but the background is transparent, merging the home screen and settings together.
It definitely seems like the Asus ROG Phone 2 could handle OxygenOS, but since I'm no developer, I think a bit of work from some enthusiastic developers should be able to make it work.
If you want to get to where I am, here's what you have to do...
- Unlock the bootloader via the Asus Bootloader Unlock Tool
- Next, disable vbmeta with the help of a vbmeta patch (More info here)
- Next, install TWRP via the excellent guide posted here.
- Wipe everything
- Download and install EfranGSI's OxygenOS Port with Android 9 / AB
- To install the OxygenOS img file, go to Enter TWRP, copy the OxygenOS file to your phone, and Install IMG into the system
- Next, install the Permissive V4 zip file via TWRP.
- Lastly, install root by entering TWRP's Advanced -> Install Root
Once that's done, you should see the ROG Phone 2 boot up for a few seconds before rebooting. Once it begins booting for the second time, it should show OnePlus's bootup animation.
Let me know if there are any different outcomes. Can't wait to see where this goes.
usmangta said:
Hi Guys,
Ever since GSI support has been introduced for the Asus ROG Phone 2, I've been experimenting with the possibilities of what works on the Asus ROG Phone 2.
Since OxygenOS has been a major favorite of mine, I decided to download ErfanGSI's port of OxygenOS-Android9-AB.
However, the final result is no where near daily usage.
Here's what works.
-Calls
-Messaging
-Chrome
What doesn't work
-Google Play Store
-Settings ( The main settings section isn't launching, although, if you tap and hold the icons in the status bar, the Wifi settings and stuff works fine, but the background is transparent, merging the home screen and settings together.
It definitely seems like the Asus ROG Phone 2 could handle OxygenOS, but since I'm no developer, I think a bit of work from some enthusiastic developers should be able to make it work.
If you want to get to where I am, here's what you have to do...
- Unlock the bootloader via the Asus Bootloader Unlock Tool
- Next, disable vbmeta with the help of a vbmeta patch (More info here)
- Next, install TWRP via the excellent guide posted here.
- Wipe everything
- Download and install EfranGSI's OxygenOS Port with Android 9 / AB
- To install the OxygenOS img file, go to Enter TWRP, copy the OxygenOS file to your phone, and Install IMG into the system
- Next, install the Permissive V4 zip file via TWRP.
- Lastly, install root by entering TWRP's Advanced -> Install Root
Once that's done, you should see the ROG Phone 2 boot up for a few seconds before rebooting. Once it begins booting for the second time, it should show OnePlus's bootup animation.
Let me know if there are any different outcomes. Can't wait to see where this goes.
Click to expand...
Click to collapse
There are no devs with this phone. Either get used to Asus stock fw, or get a different phone.
suzook said:
There are no devs with this phone. Either get used to Asus stock fw, or get a different phone.
Click to expand...
Click to collapse
Come on man, you shouldn't be so negative about this. He can become a dev for this phone. Technically he already is now.
Jammol said:
Come on man, you shouldn't be so negative about this. He can become a dev for this phone. Technically he already is now.
Click to expand...
Click to collapse
LOL, Hes a dev loading a gsi?
suzook said:
LOL, Hes a dev loading a gsi?
Click to expand...
Click to collapse
Regardless, he has done a lot more than you have in this thread. You are missing the point. His interest is sparked, how about encouraging them instead of putting them down?!
There will always be people doing nothing complaining about people doing nothing and telling you their phone development is dead based on no intel whatsoever.
Last phone I had, Lenovo P2, we had to wait quite a long time, not much happened.
Then it got Official Lineage 14/15/16 and sh*tload of ROMs.
We just don't know.
usmangta said:
Hi Guys,
Ever since GSI support has been introduced for the Asus ROG Phone 2, I've been experimenting with the possibilities of what works on the Asus ROG Phone 2.
Since OxygenOS has been a major favorite of mine, I decided to download ErfanGSI's port of OxygenOS-Android9-AB.
However, the final result is no where near daily usage.
Here's what works.
-Calls
-Messaging
-Chrome
What doesn't work
-Google Play Store
-Settings ( The main settings section isn't launching, although, if you tap and hold the icons in the status bar, the Wifi settings and stuff works fine, but the background is transparent, merging the home screen and settings together.
It definitely seems like the Asus ROG Phone 2 could handle OxygenOS, but since I'm no developer, I think a bit of work from some enthusiastic developers should be able to make it work.
If you want to get to where I am, here's what you have to do...
- Unlock the bootloader via the Asus Bootloader Unlock Tool
- Next, disable vbmeta with the help of a vbmeta patch (More info here)
- Next, install TWRP via the excellent guide posted here.
- Wipe everything
- Download and install EfranGSI's OxygenOS Port with Android 9 / AB
- To install the OxygenOS img file, go to Enter TWRP, copy the OxygenOS file to your phone, and Install IMG into the system
- Next, install the Permissive V4 zip file via TWRP.
- Lastly, install root by entering TWRP's Advanced -> Install Root
Once that's done, you should see the ROG Phone 2 boot up for a few seconds before rebooting. Once it begins booting for the second time, it should show OnePlus's bootup animation.
Let me know if there are any different outcomes. Can't wait to see where this goes.
Click to expand...
Click to collapse
Interesting. Are your connections working alright? Wifi, bluetooth, 4G, etc
Jammol said:
Regardless, he has done a lot more than you have in this thread. You are missing the point. His interest is sparked, how about encouraging them instead of putting them down?!
Click to expand...
Click to collapse
At least the ROG 2 is better off than my second phone which is the Nubia Z20. XDA moderators just don't care to even make a sub forum for it so people are just talking inside the 1 thread titled "Please make a sub forum for the Nubia Z20" under general Android section.
This is a cool idea that I hope somebody is doing something with