Related
Okay, so. I'd like to rope @weimerd and @MRDA1981 into a discussion here, because I know you guys have views on doing a full OTA update from a QFIL flash of ZUI 1.9.
But that's not very practical to do, takes a long time, and probably isn't a sustainable solution since Lenovo is trying to phase out the ZUK brand and I can only assume that they won't run the OTA servers forever.
I know that, obviously, the ZUI 1.9 QPST files include at least one more partition than later versions because they re-lock the bootloader (at least, they include a fresh bootloader). So yes, for the sake of completion, if one is trying to eliminate all possible leftover garbage and do a completely clean bring-up to a custom ROM to stick with for a while, I can understand beginning with flashing ZUI 1.9 QPST package via QFIL. I've done that too.
I'm not even going to touch on just doing the baseband flashes via TWRP; that might be fine, but if I already have QFIL set up and official ZUI firmware QPST packages then I think it's safer to just use those.
My specific question that I'd like you to discuss is: what's the practical difference between doing OTA updates after a 1.9 QFIL flash (which would require a good internet connection for several LARGE downloads and sideloading VPN software to get the latest versions, trusting that Lenovo keeps the OTA servers available for our phone, and takes a LONG time), vs. doing successive version QFIL flashes - that is, flash 1.9 and boot, then either go successively through 2.3, 2.5, and 3.1 or going straight from 1.9 to 3.1 (which doesn't require Lenovo's OTA servers to keep working or VPN, and the only internet connection you need is a little bit of data use for initial setup of the phone each time, and is MUCH faster). If the goal is to make sure that we didn't "miss anything" by doing OTA updates, wouldn't successively flashing QPST packages via QFIL do exactly that, in a fraction of the time?
I look forward to your insights, thanks folks.
You can flash 1.9.104 st and then 3.1.194 st by qfil . You don't have to use ota . Besides , I think that 3.5 with android 8 will relock bootloader as well .
mar.ur said:
You can flash 1.9.104 st and then 3.1.194 st by qfil . You don't have to use ota . Besides , I think that 3.5 with android 8 will relock bootloader as well .
Click to expand...
Click to collapse
Relocking bootloader isn't an issue; it's just two more fastboot commands to unlock it again (and I assume EVERYONE here is being very careful to save their unlock file and making backups, riiiiight?). Doing 1.9 and then straight to 3.1 QPST packages via QFIL (well then going to 3.5 dev leaks if my goal is an Oreo-based ROM) and then unlocking bootloader, setting up VoLTE in ZUI, and then going to town with TWRP, wiping internal storage/data/system/cache/dalvik and installing custom ROM/gapps/magisk has been my standard bring-up procedure for custom ROMs, and it seems to work well - I don't get wifi/bluetooth problems now, VoLTE works, and with AEX 5.1 I even have wifi calling working at home. I just thought it was good to compare vs. OTA updating, because that seems more & more to be unnecessary to be sure you're "doing it right".
All full zui roms flash all partitions . Zui 1.9.104 is not special . It' s the same . Only one difference is that relocked bootloader . I tried relock bootloader by twrp and was successed . The point is to unroot zui and flash stock recovery from zui you have . But when you back from custom the best way is flash 1.9 . That's all .
From my experience, performing the manual flash gave me the dreaded camera shake issue. Then again, the last QFIL load I did was via OTA and the problem sometimes resurfaces when starting up the Google Camera Mod. A firm tap usually gets rid of it, but it's bloody irritating all the same.
Recently, I've encountered the issue of my USB 3.0 ports/cable not reading my connection as USB 3 (which is far easier to flash 1.9 with without Sahara errors), so manual might be my only go-to should I ever need to flash back to ZUI again.
Hi, I've got problem with my huawei p9
I really wanted an update to a newer build, so i used firmware finder using app proxy to download it before it will show in system updater. Installation went fine but after all i noticed two things: gps is not working - it shows place where i was two weeks ago as my current location and apps from google play to repair this aren't working - and the second problem is my build number. Instead of EVA-L09C150B385 which this update supposed to bring, it is NRD90M test-keys
And my question is that: Is it possible to reverse the update? And if not is it possible to somehow easily flash stock rom to this phone. The device has stock recovery, locked bootloader and was never rooted (and if possible I would rather prefer to keep it in that state)
I've heard about some method using the sdcard but at the moment i don't have big enough at home, so is there any other way?
Previously I was using LG smartphone and it could easily be fixed using LG flash tool
Is there some kind of similar app for huawei?
I know that google isn't biting and that there were similar threads before, but neither one of them really answers my questions and most of them are more about devices with custom recovery or/and root
I would suggest following the debranding method with downgrading to old Android and then install newer version on top.
https://forum.xda-developers.com/p9/how-to/guide-debranding-to-c432-updating-to-t3551523
You will need the bootloader unlock code.
Of course because of unlocking the bootloader, your device will be wiped so make sure you will have a backup of your data
As @edmun says above, I'd rebrand your phone and then update from there. You must get an SD dude, I can't do without mine.
Once rebranded, use the following tool (all instructions are there) to get to the latest version. I got stuck on NDR test keys at the weekend and used this tool to roll-back and update.
https://forum.xda-developers.com/p9/development/rebrand-update-tool-hwota7-p9-eva-t3820849
You can always relock your bootloader and remove root once you've finished.
As far as I remember, if you will follow the "debranding" manual, at the end you will have bootloader locked.
The debranding method does not root the phone, so no need to "un-root" afterwards.
In my opinion, that is the easiest and cleanest way to restore the phone to a clean genuine software
What Newkeebrown suggested is to rebrand the phone to P9 China which will allow you to install Android 8.0 (Oreo).
Unfortunately, at this moment, I can't confirm whether it is a good idea as I am quite too busy to test this method (it would involve of course backup and restore which takes around half a day for me)
Kinda suggesting rebranding to L09C432 because there's more support on here for that version. But yes, definitely gives you the option to jump up to Oreo if you wish. I'm lucky, no backing up for me as all I need is my contacts, synced to Google. I always start fresh after flashing
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.
I'm looking for a new smartphone, and I'd like to get the P Smart 2019 model, because it seems well suited for my needs.
However, I haven't been able to find clear indication that it is rootable (yet). The instructions I find seem for the older (2018) model, or seem to be fake/incomplete.
One site states that huawei is no longer allowing the bootloader to be unlocked: https://www.xda-developers.com/huawei-p-smart-2019-launches-uk/
So - is there anything I can follow about a possible root for P Smart 2019, or should I look for a different phone?
You can use DC-Unlocker to unlock the bootloader, but i don't know if the device is supported yet by the software.
I think it can't be rooted yet because we don't have any custom recovery for it
alexmanu1 said:
You can use DC-Unlocker to unlock the bootloader, but i don't know if the device is supported yet by the software.
I think it can't be rooted yet because we don't have any custom recovery for it
Click to expand...
Click to collapse
Thanks.... I'll wait for a month or two to see if a recovery comes along.
Would you say the P Smart 2019 will be a popular phone (e.g. that can get enough community behind so that it will be well supported in terms of root/customizations), or are there better fish in the pond?
alexmanu1 said:
You can use DC-Unlocker to unlock the bootloader, but i don't know if the device is supported yet by the software.
I think it can't be rooted yet because we don't have any custom recovery for it
Click to expand...
Click to collapse
That's so bad. i bought today and 1/03 arrive to me and there isn't root method
mad_ady said:
Thanks.... I'll wait for a month or two to see if a recovery comes along.
Would you say the P Smart 2019 will be a popular phone (e.g. that can get enough community behind so that it will be well supported in terms of root/customizations), or are there better fish in the pond?
Click to expand...
Click to collapse
I would say we need to wait a bit as the phone still is at the beggining of the road
If DC-Unlocked provides a unlock method, we might have devs for the device...
you can root any phone with an unlocked bootloader... you patch the boot. img with magisk manager apk and flash it back using fastboot
your problem is that yes, dc-unlocker provides bootloader unlock codes for 4€..
HOWEVEr... you are SOL cos the huawei 2019 most likely will launch with a security patch that will stop dc-unlocker...
for the p smart 2018 you can downgrade to the first version of stock rom and then unlock but i think 2019 has launched with too high a security patch..
this dude who already ordered it should contact dc and see or post here the date of his security patch out of the box
lastly DO NOT Update.. just in case you can unlock anyway..
dont buy Huawei.. they are anti dev mod and root so don't support them
get a xiaomi.. same quality and price but more dev friendly
Thank you for your suggestion. I'll have a look at a different vendor as well.
Bluetooth still crappy on this one
Huawei P Smart 2019 root manual at techdroidtips
Not sure to what extent xdadevelopers permits external links, but google allows a quick find of instructions for rooting the 2019 at techdroidtips dot com. It looks very serious and reliable. What do you guys think about?
I would go for the first "manual" method, however the easy "automatic" option with KingRoot sounds convincing, too. Any recommendations or comments are welcome!
Sorry, that site doesn't seem reliable and the pages seem autogenerated:
Before rooting, do install TWRP Recovery on Huawei P Smart (2019) (IMP STEP TWRP File May Or May Not Be available as per the development) Though methods are mentioned below that require no Recovery.
Click to expand...
Click to collapse
I can't find any TWRP recovery for this model, so I assume none exists yet.
Klemse said:
Not sure to what extent xdadevelopers permits external links, but google allows a quick find of instructions for rooting the 2019 at techdroidtips dot com. It looks very serious and reliable. What do you guys think about?
I would go for the first "manual" method, however the easy "automatic" option with KingRoot sounds convincing, too. Any recommendations or comments are welcome!
Click to expand...
Click to collapse
jajaja ...are you joking ...kingroot ......kingroot is outdated and also adware / bloatware ....
you have been explained ...only root to road through unlocking your bootloader ....the question is whether the your security patch is outdated enough to allow you to use dc-unlocker to use their method to readback your code from your device for you
if you have an unlocked bootloader you can flash custom roms without root using fastboot and treble system images ( NO ROOT NEEDED) & If yourealky wanted root you could patch your boot.img with magisk and flash that back with fastboot
IN BOTH CASES NO TWRP EVEN NEEDED .....:silly:
In the meantime a have to admit, that you're right and the mentioned source may represent an useful general overview of available approaches, but is not at all device specific (and indeed automatic generated with replacing phone devices as tokens).
So, sorry for the terrible research so far. Hopefully the following summary is better:
1) Because Huawei stopped their Unlocking Support in Mid of 2018, we need alternative ways to do so. One of them could be DC-unlocker, however it doesn't seem to be supported yet (at least not listed as '(2019)'). So other services as for example mentioned at huaweiadvices dot com could be a solution, although they cost 35$ or more. I'm wondering how those companies (like FunkyHuawei or MinistryOfSolutions) do access/receive the Unlock code?
2) Because there aren't (somehow based on issue 1) compatible ROMs for Huawei-P-Smart-2019, yet, or at least no well known/tested ones, an experienced user like me should wait till there is an announced model supported release. A very interesting source seems to be OpenKirin. So waiting for a release for the Kirin 710 (which is not yet listed) could be promising. Btw, what ways do you know for finding fitting ROMs?
Do those two conditions seem proper to you?
Device specific custom roms seems to be the thing of the past . The future is project treble ....so for all intents and purposes there are many custom roms that could installed on your device ...read how treble works and perhaps you will understand....kirin 710 is irrelevant ...in treble you are flashing a system.img which is generic ( any treble device ) because the "drivers" for yourhardware is not in the system img ...
Magisk is the main and perhaps only cross platform root method ...once again ...your device is irrelevant ...
Your only mission here is to unlock your bootloader so you can flash .img files that are not approved by Huawei ...
So your only time spent that will be worth anything will be obtaining a bootloader unlock code
However Whichway because without it you will go pretty much nowhere ...with it ...you don't even need a twrp nor do you need a custom specifically announced as being for P smart 2019
Huawei is like Apple ..of Android ....without any jailbreak community and at a lower price / quality point
Since taking the step not to support bootloader unlocking ...they are worthless as a phone to a person who wants root and good custom roms ..
just because dc says unsupported doesn't mean it won't work ...i told you to contact by email your security patch level to enquire if it might work ...so until youhave done that this whole chat is worthless ...
if your security patch is quite recent you are SOL
you should off-load it on an old guy who doesn't know what root is and get another phone .
Hi KevMetal, thanks for your effort to clarify and increasing my understanding. Didn't want you to have yourself repeated...sry
Anyway, I tried to follow your advice and have sent now the following device information to [email protected]:
◦ Model: POT-LX1
◦ Build-Number: 9.0.1.129(C432E8R1P12)
◦ EMUI-Version: 9.0.1
◦ Android Security Patch: 1st Nov' 2018
Don't know if this is enough. However couldn't find a number for the Security Patch or anything beyond that release date.
Will share the information here, If I get an answer...
Klemse said:
Hi KevMetal, thanks for your effort to clarify and increasing my understanding. Didn't want you to have yourself repeated...sry
Anyway, I tried to follow your advice and have sent now the following device information to [email protected]:
◦ Model: POT-LX1
◦ Build-Number: 9.0.1.129(C432E8R1P12)
◦ EMUI-Version: 9.0.1
◦ Android Security Patch: 1st Nov' 2018
Don't know if this is enough. However couldn't find a number for the Security Patch or anything beyond that release date.
Will share the information here, If I get an answer...
Click to expand...
Click to collapse
The info is fine, it does according to release date ...i can almost guarantee that it's too recent .....but rather wait for confirmation ....if you are really lucky some really clever Dev or devs or unlock team looking for money will find another exploit to readback the bootloader code but as for now you are SOL ...but unless you see info floating in XDA or 4pda and it's vouched for by experienced members it's probably a scam to get cash or just adware or bloatware ... after android nougat there are / were very few legit root exploits and when legit they get patched in a security update after release locking down newer models ...cheaper or midrange devices just don't get enough attention from the right people ......not to mention that the OSgets locked down tighter and finding exploits is a time consuming past time ...:good:..sorry bro
tools like software based root exploit tools released to public depends on finding weaknesses in the security of the OS whereas bootloader unlock lets you flash images that includes root or boot images patched previously so its very different
Any news? I boutht the 2019 version and joping there will be some root method soon and perhaps some rom.
Any good dark material emui 9 theme in the meantime?
Is there any way I can enalrge icons in the status bar, they are so tiny no matter what font settings are applied?
Huawei P Smart 2019 root/magisk — missing Bootloader unlocking!
Well, unfortunately there is only little hope. I got answers from [email protected] that there is no support so far, however they „[…] hope so it will become supported in future, but there are no news or information available about it yet.“
I won't wait for it and switched to another phone...
Today, I have got bootloader unlock code for P Smart 2019 for 31 USD from
global-unlocking-solutions.miiduu.com/bootloader-unlock-codes-choose-model-below
Unfortunately I cannot get Magisk to work, tried so many things and still no root, also non of working twrp recoveries exist ...
xcodejps said:
Today, I have got bootloader unlock code for P Smart 2019 for 31 USD from
global-unlocking-solutions.miiduu.com/bootloader-unlock-codes-choose-model-below
Unfortunately I cannot get Magisk to work, tried so many things and still no root, also non of working twrp recoveries exist ...
Click to expand...
Click to collapse
if you unlocked your bootloader you can flash any prerooted treble system.img
....how is it exactly that you cant get magisk to work ....download your stock rom ..extract the boot.img ...patch it with magisk apk ...flash it back using fastboot
post screenshots here if your unlocked bootloader then i will explain you how to flash a treble GSI
NO TWRP NECESSARY ANYMORE SINCE PROJECT TREBLE ...WHAT DONT YOU UNDERSTAND ..just go read about treble a little ..:silly:
or is this fake spam to dupe people into forking out 31$ for a bootloader unlock code that doesnt arrive ..post proof of your unlocked bootloader with screenshots from fastboot
KevMetal said:
if you unlocked your bootloader you can flash any prerooted treble system.img
....how is it exactly that you cant get magisk to work ....download your stock rom ..extract the boot.img ...patch it with magisk apk ...flash it back using fastboot
post screenshots here if your unlocked bootloader then i will explain you how to flash a treble GSI
NO TWRP NECESSARY ANYMORE SINCE PROJECT TREBLE ...WHAT DONT YOU UNDERSTAND ..just go read about treble a little ..:silly:
or is this fake spam to dupe people into forking out 31$ for a bootloader unlock code that doesnt arrive ..post proof of your unlocked bootloader with screenshots from fastboot
Click to expand...
Click to collapse
Hi, I've been rooting other older phones before, i will read more about treble gsi, thank you, but i can promise you it is real, i've been tracking for unlock codes for my phone for two months and just yesterday they managed to generate the unlock code for me. I have no intention to lie, here are the screenshots i've been able to gather just now.
imgur.com/a/YuoGGvC
If i flash it to recovery_ramdisk and then quickly disconnect usb and hold vol up it will bootloop once (and never i get magisk installed) i have tried to install twrp for kirin 710 from honor device, but screen is not working can't touch anything then. I have downloaded latest full firmware 9.0.1.152(C432E8R1P12) and trie to patch RECOVERY_RAMDISK.IMG multiple times using magiskmanager with different versions of magisk 18v 19v with options enabled/disabled
Greetings Folks
For starters I just got Mi8 and am planning to go for Havoc or Pixel Experience there is a Pixel Port too I'll have to try which is best close to stock but with gestures features and full fledged Gcam support
Back to Questions
I have seen many threads where newer folks are victim of their devices getting bricked and paying for fix?
Why isnt there a proper guide thread to avoid these obstacles and spread awareness out ?
I know there are certain partitions you need to backup too e.g efs in case of lost IMEI there was a thread Its hell I have been through it with a Samsung Device,There was a guy who messed up his phone sensor files?
But most of all EDL and Devices getting brick so lets address the elephant in the room
Now My Phone is on
MIUI 10.3 Global 10.3.2.0(PEAMIXM)
Android Version : 9 PKQ1.180729.001
Android Security Patch : 2019-04-01
Rom threads say 9.3
take havoc for example
Help Appreciated thanks
@techyrock
Here is a guide : https://forum.xda-developers.com/mi-8/how-to/how-to-install-roms-resolve-issues-t3911611
Part 1 ( The OP is general info ) Below the first couple of comments have detailed steps for AOSP.
Be extremely careful, unfortunately this community doesn't have a lot of highly active professionals.
So definitely double check any advice that you are given, or that you find. With that being said there are definitely several members that are mature, knowledgeable, friendly and overall fantastic.
If you need help, feel free to ask me anytime, I haven't had a lot of time to use XDA recently. But if I am around, I am always willing to help. At the moment I am going to sleep, but go ahead and read my thread, and I have made some lengthy post that may be helpful as well. You can find those posts by reading my post history. Enjoy.
As long as your account is bound to your device, unbricking is pretty easy with these phones. If you want to avoid a brick, avoid brand new builds, test software etc. Some of the recent issues actually stemmed from the 7.11 china developer rom which had a major issue.
if you want to use Miui with zero ads, and every single feature, then Mi-Globe is pretty great, and solid on a week to week basis.
As far as AOSP, I feel that in my experience that Syberia is practically always highly stable, but it's a little plain compared to some other roms. I also liked Pixel 3, Bootleggers ( Newer version) and Havoc. ( I used Havoc in the beginning of July and loved it, that build is fantastic)
I haven't tried a lot of AOSP roms on this phone yet. So that is all I have
Addition to that, the main issue is people are using Miflash to flash a ROM from bootloader. DO NOT USE IT.
Just use the flash_all.bat in the fastboot rom zip, it's easy. Miflash chooses to lock bootloader by default, and if you don't change it, you'll need to use EDL to fix your device. People usually forget about it, and will whine here to be able to unbrick. Don't be one of them
Don't relock the damn bootloader. It's unnecessary, and dangerous on a Chinese machine.
The War Profiteer said:
Addition to that, the main issue is people are using Miflash to flash a ROM from bootloader. DO NOT USE IT.
Just use the flash_all.bat in the fastboot rom zip, it's easy. Miflash chooses to lock bootloader by default, and if you don't change it, you'll need to use EDL to fix your device. People usually forget about it, and will whine here to be able to unbrick. Don't be one of them
Don't relock the damn bootloader. It's unnecessary, and dangerous on a Chinese machine.
Click to expand...
Click to collapse
We ok that to unlock bootloader on mi8 we have to use mi "flash" unlock tool. Right?
Cheers
Erpe7 said:
We ok that to unlock bootloader on mi8 we have to use mi "flash" unlock tool. Right?
Cheers
Click to expand...
Click to collapse
Yes, that is the only way to unlock. he was talking about using Mi Flash to flash roms, which may seem to be user friendly which it is but is also extremely dangerous because the the option to lock the bootloader is checked by default. If using it make sure that its unchecked and you should not have any issues.
Personally, I prefer ADB if flashing via fastboot or TWRP with a OTG flash drive.
Also there is a tool that is excellent that I have also used many times, its called Tool all in One ( TAIO) After your bootloader is unlocked, you can use TAIO for many functions, including keep your PC's ADB platform tools, up to date, and providing system wide access. You can use it to remove encryption, flash recovery, root, roms or to restore to stock. It definitely worth installing if if you only use it to keep your drivers, and platform tools up to date.
First of all thanks guys for replies wasn't expecting this response
My device is Global Mi8 bootloader is locked for now I still have some hours left I'll be able to unlock it by 26th
miflash_unlock prompted to bind my account from developer option for unlocking,I did so it will be bound to my account and ill be unlocking it for first time I believe i bought it used but previous owner seemed to have know info about ROMs though
I have been using Pixel 2XL twice followed by Nokia 8 so I am much more inclined towards AOSP stock experience the two feature I would love to have from MIUI are the
1)MIUI gestures
2)MIUI Dual Apps (I am aware of Play store alternatives but clash of clans doesnt work as good on them as on dual apps )
I know gestures are on Havoc
guess you guys have been playing around with your mi8 kindly guide me to right directrion what ROMs you guys prefer and why ?
how would you prefer to flash a ROM do I need to back up any partitions ? if so which app should use for it ,Ill surely back up everything via TWRP for sure
also the encryption thingy should I sign out my google account before bootloader unlock and other stuff?
and since I am on
MIUI 10.3 Global 10.3.2.0(PEAMIXM)
Android Version : 9 PKQ1.180729.001
Android Security Patch : 2019-04-01
is it safe to flash havoc ?
tsongming said:
Yes, that is the only way to unlock. he was talking about using Mi Flash to flash roms, which may seem to be user friendly which it is but is also extremely dangerous because the the option to lock the bootloader is checked by default. If using it make sure that its unchecked and you should not have any issues.
Personally, I prefer ADB if flashing via fastboot or TWRP with a OTG flash drive.
Also there is a tool that is excellent that I have also used many times, its called Tool all in One ( TAIO) After your bootloader is unlocked, you can use TAIO for many functions, including keep your PC's ADB platform tools, up to date, and providing system wide access. You can use it to remove encryption, flash recovery, root, roms or to restore to stock. It definitely worth installing if if you only use it to keep your drivers, and platform tools up to date.
Click to expand...
Click to collapse
Thank you for this precious advices ;(
I'll note that!
Sent from my Redmi Note 5 Pro using XDA Labs
Thank you folks.
Could someone explain what EDL is meaning?
Gesendet von meinem BTV-DL09 mit Tapatalk
ktrokar said:
Thank you folks.
Could someone explain what EDL is meaning?
Gesendet von meinem BTV-DL09 mit Tapatalk
Click to expand...
Click to collapse
There's a primary bootloader that we consumer know of and there's Qualcomm's Emergency Download Mode bootloader (EDL) , since Mi8 has ARB(Anti Rollback) downgrading the phone gets it bricked to EDL mode requiring EDL authentication to my understanding thats why edl is a thing(since its just emergency bootloader for oems to work with) I have not experienced it personally so I don't know whether it bricks that way or not but ARB and EDL authentication are a thing with Mi8 from what I have read in different threads
Sent from my MI 8 using Tapatalk
ktrokar said:
Thank you folks.
Could someone explain what EDL is meaning?
Gesendet von meinem BTV-DL09 mit Tapatalk
Click to expand...
Click to collapse
EDL is Qualcomm recovery mode, it's the mode that you must be in to restore a hard bricked phone.
As long as you are careful you should never need to worry about EDL. Basically, you place the phone into a mode that the computer is able to recognise port 9008, once that is down you can use 1 of 4 techniques to restore your phone. Unbricking Xiaomi's is actually very easy to do, as long as the device is bound to your account.
The big issue is that unscrupulous Chinese vendors, used their own account to unlock bootloaders of Mi8's and other Xiaomi devices, then installed the Global Miui ROM and then sold the phone as new to unsuspecting western customers and at a lower price than western outlets such as Amazon. These vendors marketed the phones as Ïnternational versions" when they were actually Chinese devices and not the Global version that the customer thought they bought.
When these customer's used programs such as MiFlash to upgrade their phone's their bootloaders were locked and the are unable to log into their Mi Account to restore the phone. Remember the vendors unlocked the phone, so these Mi8's were bound to the vendor and not the final customer. This is the Primary reason why Xiaomi makes us wait to unlock the bootloader. Finally, ARB is potential issue, but it hasn't been implemented yet on Global devices.
So do your research before flashing anything and you should be safe.