Related
I want to flash the marshmallow update to my phone and I can't seem to find the stock system image for the TMO xt1095. Anyone have a good download link for this file? I went to file factory but I have to wait 6 hours for the download.
There's one here, it seems a little newer:
https://mega.nz/#F!ow8igZRL!Z7vmN8GOpez2bVMYDvEKkg!h9FWBQha
Hello guys,
I'm not a noob at Android (have flashed my fair share of ROMs, recoveries and kernels on Nexus and Samsung), but I am a noob at Xiaomi, and trying to install the latest Dev Global ROM (mainly for the purpose of having root to restore a bunch of Titanium Backups) is giving me a headache.. mostly since there are multiple tools / ROM types out there and I am not really sure of which to use when. The Device is a Mi5 64GB running China Stable 7.3, purchased through Xiaomi in China (so no possibility of funny ROMs installed).
What I did up to now is:
1. requested bootloader unlock on xiaomi website > unlocking the bootloader using Miunlock tool
2. downloaded official Global Stable and Global Dev and tried to flash them (yeah both, I am that desperate ) using MiPCSuite, but it does not recognize my device, says to update device first which I'm currently doing
3. downloaded official Global Stable and Global Dev and tried to flash them using Updater tool on the phone, but it says "unable to verify package".
4. got lost reading about Miflash, custom recoveries, decryption etc.
I loooked around but I cannot:
1. for the life of me understand what is the difference between Miflash and fastboot, if they use same type of ROMs etc
2. find a fastboot flashable Global Dev ROM
3. understand what the stock recovery does.. it just shows a device pic saying to connect the cable
4. quite figure out if I need to decrypt the device to make root work
Any help would be greatly appreciated.. sorry if the above was already explained elsewhere but couldn't find anything solid about it!
Lazer Bear said:
Hello guys,
I'm not a noob at Android (have flashed my fair share of ROMs, recoveries and kernels on Nexus and Samsung), but I am a noob at Xiaomi, and trying to install the latest Dev Global ROM (mainly for the purpose of having root to restore a bunch of Titanium Backups) is giving me a headache.. mostly since there are multiple tools / ROM types out there and I am not really sure of which to use when. The Device is a Mi5 64GB running China Stable 7.3, purchased through Xiaomi in China (so no possibility of funny ROMs installed).
What I did up to now is:
1. requested bootloader unlock on xiaomi website > unlocking the bootloader using Miunlock tool
2. downloaded official Global Stable and Global Dev and tried to flash them (yeah both, I am that desperate ) using MiPCSuite, but it does not recognize my device, says to update device first which I'm currently doing
3. downloaded official Global Stable and Global Dev and tried to flash them using Updater tool on the phone, but it says "unable to verify package".
4. got lost reading about Miflash, custom recoveries, decryption etc.
I loooked around but I cannot:
1. for the life of me understand what is the difference between Miflash and fastboot, if they use same type of ROMs etc
2. find a fastboot flashable Global Dev ROM
3. understand what the stock recovery does.. it just shows a device pic saying to connect the cable
4. quite figure out if I need to decrypt the device to make root work
Any help would be greatly appreciated.. sorry if the above was already explained elsewhere but couldn't find anything solid about it!
Click to expand...
Click to collapse
If you unlocked the bootloader, then it's pretty simple now.
-Download and install miflash in windows
-Download this rom and extract it to a folder. Should be no spaces in the folder name or it won't work.
-Boot the phone to fastboot mode(turn off, press volume down and power button in the same time for 3 sec)
-Start miflash
-Press refresh, it should find your phone
-Browse the folder where you extracted the rom
-Choose flash all option and the bottom right corner
-Flash the rom
-If it finished, then the phone reboots, if not, then you hold the power button for 10 sec.
Well, that worked! I still have no idea why (I mean, I know "why", but I haven't cleared quite all of my doubts about how to go around flashing ROMs with Xiaomi) but thanks a bunch!!
BTW for anyone referring to this thread in the future, note that MiFlash might require the extracted ROM to be placed in the root directory of the HDD (can be C:\ or D:\ or whatever as long as it is not in a subfolder). I got an error at the beginning but managed to solve it that way.
hello friends today i will share a method that i found on youtube how to switch from chinese to global firmware on Meizu Pro 7
all the credits are for Uncle MokuS
i just wanted to help people that is searching for it like me
so just follow the totorial - https://www.youtube.com/watch?v=aDp...5wdjofattwgksn3zi1jpw03c010c.1508299039136556
the totorial is in russian so if you have any doubt just read the coments in video discription
that method is different that the one that i use in my old mx5 by terminal emulator... i really would prefer the terminal emulator method because just change the phone and you can install any G firmware by flyme recovery and keep with ota updates and without the phone rooted (i dont want root because i use some apps that doesnt allow me use if i have root) but i didnt find a diferent mode yet i hope some one could show a diferent method like i did to mx5
everything works because its original firmware the only thing is that to next updates you´ll have to do by flashfire
anyway i hope you all enjoy G firmware
Hi, thanks for the good news.
Does anyone know whether this method also works with the Meizu Pro 7 PLUS?
The people in comments say that its not working
You can find an english Guide for the installation of the Global ROM on the chinese Meizu Pro 7 here:
https://www.china-phone.net/meizu-pro-7-global-rom-guide.html
Lost imei
I have lost my imei numbers and they become null.
Also i have lost root access after intalling the update.zip from flymeos.com. Because i cant login into meizu account after installing the update.zip,
it says ''invalid parameter ''.
Phone has locked bootlader. Cant flash anything..
Any suggestions ?
Dennis1311 said:
Hi, thanks for the good news.
Does anyone know whether this method also works with the Meizu Pro 7 PLUS?
Click to expand...
Click to collapse
I've got this one working for Pro 7 Plus, model M793Q:
1. Download Flyme 6.7.10.31 beta rom from official chinese Flyme site and put it to your phone's main folder
2. Enter Recovery mode (Volume Up + Power), select "Update firmware" and "Wipe data", then wait until the update is done
3. Download Flyme 6.1.2.0G rom from official site and also put it to your phone just like the chinese rom
4. Enter Recovery mode again and do the same things - select "Update firmware" and "Wipe data", then wait until the update is done
Thanks for your Method..It is working great on Meizu Pro 7 PLUS Model: M793H to :good:
T3Rm0 said:
I've got this one working for Pro 7 Plus, model M793Q:
1. Download Flyme 6.7.10.31 beta rom from official chinese Flyme site and put it to your phone's main folder
2. Enter Recovery mode (Volume Up + Power), select "Update firmware" and "Wipe data", then wait until the update is done
3. Download Flyme 6.1.2.0G rom from official site and also put it to your phone just like the chinese rom
4. Enter Recovery mode again and do the same things - select "Update firmware" and "Wipe data", then wait until the update is done
Click to expand...
Click to collapse
Just one thing you still have ota updates right?
im trying in my pro 7 (standard) and when i try to install the G firmware in recovery i got the message firmware corrupt do the people with pro 7 plus is lucky
its not working in the standard version i give up xD
1. I have still my ota updates on Meizu pro 7 plus with the global version that i recently update from A chinese firmware to beta chinese then to Global version.
2. You need to have the Chinese Beta version first on your phone to update to Global version.
3. You can download the chinese flyme firmware beta version from Meizufans. Search Meizufans on the Google.
4. Allways backup your Imei number so you can restore it. That is only if the Imei NR gets NULL.Best place to have your backup is PC.
5. Download the global version from the flymeos.com
6. It should work on the standard version because it has the beta version too.
Good Luck :good:
DiogoSepultura said:
Just one thing you still have ota updates right?
im trying in my pro 7 (standard) and when i try to install the G firmware in recovery i got the message firmware corrupt do the people with pro 7 plus is lucky
its not working in the standard version i give up xD
Click to expand...
Click to collapse
TedGok said:
1. I have still my ota updates on Meizu pro 7 plus with the global version that i recently update from A chinese firmware to beta chinese then to Global version.
2. You need to have the Chinese Beta version first on your phone to update to Global version.
3. You can download the chinese flyme firmware beta version from Meizufans. Search Meizufans on the Google.
4. Allways backup your Imei number so you can restore it. That is only if the Imei NR gets NULL.Best place to have your backup is PC.
5. Download the global version from the flymeos.com
6. It should work on the standard version because it has the beta version too.
Good Luck :good:
Click to expand...
Click to collapse
lets see...
so i download the firmwares from flyme websites (they are the same that we have in meizu fans) so i installed flyme 6.7.10.31 beta
after that i went to recovery and put the G firmware inside the phone main folder, the only G firmware version that pro7 standard has is 6.1.3.0
and in recovery i try to update and always say that the firmware is corrupt
DiogoSepultura said:
lets see...
so i download the firmwares from flyme websites (they are the same that we have in meizu fans) so i installed flyme 6.7.10.31 beta
after that i went to recovery and put the G firmware inside the phone main folder, the only G firmware version that pro7 standard has is 6.1.3.0
and in recovery i try to update and always say that the firmware is corrupt
Click to expand...
Click to collapse
Try to do this:
1. Get Root permissions in settings and download Root Explorer
2. Put Global rom into your main folder
3. Start Root Explorer, grant root permissions to him and go to /dev/block/platform/bootdevice/by-name
4. Open devinfo as text file and change it from 0x79101001 to 0x79151001, then save it
5. Open the standard Flyme explorer, click on your global rom and agree with wipe
I can't guarantee that it will work but if it won't nothing bad will happen - the phone will just reboot
T3Rm0 said:
Try to do this:
1. Get Root permissions in settings and download Root Explorer
2. Put Global rom into your main folder
3. Start Root Explorer, grant root permissions to him and go to /dev/block/platform/bootdevice/by-name
4. Open devinfo as text file and change it from 0x79101001 to 0x79151001, then save it
5. Open the standard Flyme explorer, click on your global rom and agree with wipe
I can't guarantee that it will work but if it won't nothing bad will happen - the phone will just reboot
Click to expand...
Click to collapse
Hello! But i have there not 0x79101001 in "devinfo" i have 0x79201001
How can i change?
best regards
peter
pmartin said:
Hello! But i have there not 0x79101001 in "devinfo" i have 0x79201001
How can i change?
best regards
peter
Click to expand...
Click to collapse
In that case change it to 0x79251001, "5" means european device
Do you have Pro 7 HE or something? I thought there are only 2 IDs:
PRO 7 Plus 0x79351001
PRO 7 0x79151001
T3Rm0 said:
In that case change it to 0x79251001, "5" means european device
Do you have Pro 7 HE or something? I thought there are only 2 IDs:
PRO 7 Plus 0x79351001
PRO 7 0x79151001
Click to expand...
Click to collapse
pmartin did you tried this already? let us know what happend
DiogoSepultura said:
pmartin did you tried this already? let us know what happend
Click to expand...
Click to collapse
I've already tried it on my Plus device and nothing happened
The problem is that the developer has made a protection against changing ID - there are several scripts named loop, so if you change ID in devinfo and reboot they will roll back the changes.
Also I've searched for previous scripts that were working on old meizu devices, there are several ways of doing that:
1. Rewrite devinfo by using unix commands - as I understood the program finds a sector where the ID is based and replaces it. The problem is that you need to know an exact binary address for the ID but I don't know how to disassemble .img files :<
2. Get devinfo straight from the same EU device and replace it - it's easier but I don't have an EU file (If someone has it please contact me)
3. Use flash tool to write the ID directly in chipset - the most dangerous way but I can't find binary files for Helio X30, and also you need to know an adress of ID
So the easiest and the most safe way is method 2, because even if something will go wrong you can just reinstall rom from recovery mode, but if someone here knows unix\assembler he can try to locate the ID, I have extracted devinfo file (it's still has chinese ID but I believe we can find a way out)
Hello!
At first i had to install the "beta"-Rom. Because i had installed the SuperSu and i am at the "bootloop".
I am back, i try the version.
regards
peter
T3Rm0 said:
In that case change it to 0x79251001, "5" means european device
Do you have Pro 7 HE or something? I thought there are only 2 IDs:
PRO 7 Plus 0x79351001
PRO 7 0x79151001
Click to expand...
Click to collapse
pmartin said:
Hello!
At first i had to install the "beta"-Rom. Because i had installed the SuperSu and i am at the "bootloop".
I am back, i try the version.
regards
peter
Click to expand...
Click to collapse
it work´d for you?
Hi
I just tried the devinfo method with no success, as stated before, it rolls back to it original stage, I even change the permissions of devinfo file with read and exwcute only, but the permissions Also rolls back
I purchased a meizu pro 7, spanish model(global model) And I will probably Return it since I purchased Also one meizu pro 7 plus, but if you want, I can accept it a few days in order to get the files needed from the European model.
Thanks!
kralde said:
Hi
I just tried the devinfo method with no success, as stated before, it rolls back to it original stage, I even change the permissions of devinfo file with read and exwcute only, but the permissions Also rolls back
I purchased a meizu pro 7, spanish model(global model) And I will probably Return it since I purchased Also one meizu pro 7 plus, but if you want, I can accept it a few days in order to get the files needed from the European model.
Thanks!
Click to expand...
Click to collapse
if you can just share the information mate, i praying for someone who understant about this crack this thing so we can all use global firmware in our phones
T3Rm0 said:
Try to do this:
1. Get Root permissions in settings and download Root Explorer
2. Put Global rom into your main folder
3. Start Root Explorer, grant root permissions to him and go to /dev/block/platform/bootdevice/by-name
4. Open devinfo as text file and change it from 0x79101001 to 0x79151001, then save it
5. Open the standard Flyme explorer, click on your global rom and agree with wipe
I can't guarantee that it will work but if it won't nothing bad will happen - the phone will just reboot
Click to expand...
Click to collapse
DiogoSepultura said:
it work´d for you?
Click to expand...
Click to collapse
Hey guys! Now i have the beta-version from "a" but no "g" version!
I have change the devinfo but nothing happend.
Has anyone an idea how i can install the "g" version?
Best regards.
peter
hello everybody,
i have a note 8 sm-n950u1. and i need combination file for oreo ...crg9. so when i search combination file, i seen nougat's combination files (fa71). is there a combination file for oreo?
btw what should i do to nougat from oreo? is that possible?
I am running into the same issue with a samsung a8-SM-530w. Funny enough the first time I flashed the combo file it worked then I tried again later with the same file and now it fails everytime. Ive tried to find the oreo combo file 8.0 but the only one available it seems to be is the fa71 for Nougat. I also tried to make my own combo file but can't find a tool that works... I am still working on it so if I find anything I think might be of use I will let you know.
hojo68 said:
I am running into the same issue with a samsung a8-SM-530w. Funny enough the first time I flashed the combo file it worked then I tried again later with the same file and now it fails everytime. Ive tried to find the oreo combo file 8.0 but the only one available it seems to be is the fa71 for Nougat. I also tried to make my own combo file but can't find a tool that works... I am still working on it so if I find anything I think might be of use I will let you know.
Click to expand...
Click to collapse
The reason it doesn't work is because you cannot downgrade! Once you update to Oreo there's no going back to Nougat.. Samsung blocked that.
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.