Related
Hello you guys I have a s-on rooted M8,I am trying to apply an OTA update halfway through red triangle appears. When I go to the menu I can see the following error:
Package expects build fingerprint of htc/vodafone_uk/htc_m8:4.4.4/KTU84P/392065.9:user/release-keys or htc/vodafone_uk/htc_m8:5.0.1/LRX22C/457188:2user/release keys; this device has (my device's code)
As far as I can understand there is a mismatch of build fingerprints.
Without going s-off how can I fix it.
PS:I am still rooted but flashed custom recovery..
Many thanks in advance
Flash stock recovery..
It is stock recovery or let me say that way it is the recovery image which I used to apply last OTA
daneland said:
It is stock recovery or let me say that way it is the recovery image which I used to apply last OTA
Click to expand...
Click to collapse
You need the right stock recovery as mentioned in error log:
Package expects build fingerprint of htc/vodafone_uk/htc_m8:4.4.4/KTU84P/392065.9:user/release-keys or htc/vodafone_uk/htc_m8:5.0.1/LRX22C/457188:2user/release keys; this device has (my device's code)
this device has (my device's code) is not helping much without full description.
I suspect that your device has htc/vodafone_uk/htc_m8:4.4.4/KTU84P/392065.5 when the OTA needs 392065.9
Just use htc/vodafone_uk/htc_m8:5.0.1/LRX22C/457188:2 which you can get from the OTA.zip itself.
Copy the OTA.zip (sdcard\Download\) to PC, open it with 7-zip, then open firmware.zip, extract out the recovery.img from it. This is the one that you need.
ckpv5 said:
Just use htc/vodafone_uk/htc_m8:5.0.1/LRX22C/457188:2 which you can get from the OTA.zip itself.
Click to expand...
Click to collapse
Thank you so much for your reply.I dont want to be a pain but how can I download it manually or locate it after I downloaded through normal way of software update?
Copy the OTA.zip (sdcard\Download\) to PC, open it with 7-zip, then open firmware.zip, extract out the recovery.img from it. This is the one that you need.
sdcard/Download is where the location of OTA.zip is downloaded to.
Download as usual with software update, when it ask to install select install later, then copy the OTA.zip to PC
Boot to bootloader (you know how to) to flash the extracted recovery.img
Reboot - do software update checking again (it will ask to download again, select download but actually it won't go the download process again .. the complete one will pop-up and ask to install now or later, select install now .. done
ckpv5 said:
Copy the OTA.zip (sdcard\Download\) to PC, open it with 7-zip, then open firmware.zip, extract out the recovery.img from it. This is the one that you need.
sdcard/Download is where the location of OTA.zip is downloaded to.
Download as usual with software update, when it ask to install select install later, then copy the OTA.zip to PC
Boot to bootloader (you know how to) to flash the extracted recovery.img
Reboot - do software update checking again (it will ask to download again, select download but actually it won't go the download process again .. the complete one will pop-up and ask to install now or later, select install now .. done
Click to expand...
Click to collapse
I have the same issue, did the thing you said, didn't work..
Ricky757 said:
I have the same issue, did the thing you said, didn't work..
Click to expand...
Click to collapse
You may have different issue.
At the red triangle, press and hold volume button and tap power button once. You'll see error log
Read this : http://forum.xda-developers.com/htc-one-m8/help/failure-to-update-to-lollipop-t3016953
ckpv5 said:
You may have different issue.
At the red triangle, press and hold volume button and tap power button once. You'll see error log
Read this : http://forum.xda-developers.com/htc-one-m8/help/failure-to-update-to-lollipop-t3016953
Click to expand...
Click to collapse
I had the exact same errormessage. But apparently I relocked the bootloader so that was the reason I couldn't flash the stock recovery.. Silly me! haha anyway my problem is fixed. Thank you for your time and help!
I upgraded my phone to android EMUI8 and tried to install the RR 8.1 ROM but my device wouldn't boot up. Then I tried to reflash the stock system.img but it won't let me. I don't have TWRP on my phone but I can acces fastboot. Does anyone know what to do? Thanks in advance :^l
jetzecazemier said:
I upgraded my phone to android EMUI8 and tried to install the RR 8.1 ROM but my device wouldn't boot up. Then I tried to reflash the stock system.img but it won't let me. I don't have TWRP on my phone but I can acces fastboot. Does anyone know what to do? Thanks in advance :^l
Click to expand...
Click to collapse
What is it you mean , it won't let you. Does it give a message. Failed?
Are you at frp locked?
mrmazak said:
What is it you mean , it won't let you. Does it give a message. Failed?
Are you at frp locked?
Click to expand...
Click to collapse
Well when I try to flash the stock 8.0 system.img it gives me a "Invalid sparse file format at header magi" and when I try to flash TWRP it gives me a "FAILED (remote: partition length get error) I am frp unlocked by the way.
jetzecazemier said:
Well when I try to flash the stock 8.0 system.img it gives me a "Invalid sparse file format at header magi" and when I try to flash TWRP it gives me a "FAILED (remote: partition length get error)
Click to expand...
Click to collapse
Ok, that does not seem too bad, yet.
I suppose you are using system.img downloaded from web.
That image has given many that same error.
Best to use your system.img.
And the error flashing twrp, is common when using the nougat command or nougat recovery on Oreo.
Solutions.
Find your firmware on pro-teammt
http://pro-teammt.ru/firmware-database/?firmware_model=Bnd-&firmware_page=0
Then download update.zip
Extract files.
Get hauwei update extractor.
https://www.google.com/url?sa=t&sou...FjAAegQIARAB&usg=AOvVaw0xkKEyI85nY9x4Fjr1AWJl
Extract the system.img
Then fastboot flash it.
Recovery:
Oreo command== fastboot flash recovery_ramdisk twrp_ramdisk
Twrp name depends on version used. I use build 4 from here
https://forum.xda-developers.com/p10-lite/development/recovery-twrp-3-2-1-0-t3783447
mrmazak said:
Ok, that does not seem too bad, yet.
I suppose you are using system.img downloaded from web.
That image has given many that same error.
Best to use your system.img.
And the error flashing twrp, is common when using the nougat command or nougat recovery on Oreo.
Solutions.
Find your firmware on pro-teammt
http://pro-teammt.ru/firmware-database/?firmware_model=Bnd-&firmware_page=0
Then download update.zip
Extract files.
Get hauwei update extractor.
https://www.google.com/url?sa=t&sou...FjAAegQIARAB&usg=AOvVaw0xkKEyI85nY9x4Fjr1AWJl
Extract the system.img
Then fastboot flash it.
Recovery:
Oreo command== fastboot flash recovery_ramdisk twrp_ramdisk
Twrp name depends on version used. I use build 4 from here
https://forum.xda-developers.com/p10-lite/development/recovery-twrp-3-2-1-0-t3783447
Click to expand...
Click to collapse
Okay so I've downloaded the latest firmware for my model but when I try to extract the update.app inside of the update.zip file the huawei zip extractor gives me "RECOVERY_RAMDIS.img: Invalid header crc - Expected: 15200 Got: 44917
jetzecazemier said:
Okay so I've downloaded the latest firmware for my model but when I try to extract the update.app inside of the update.zip file the huawei zip extractor gives me "RECOVERY_RAMDIS.img: Invalid header crc - Expected: 15200 Got: 44917
Click to expand...
Click to collapse
yes there is a bug either in the extractor or the update files. they all do it. Go to the settings tab and take check mark off verify header.
mrmazak said:
yes there is a bug either in the extractor or the update files. they all do it. Go to the settings tab and take check mark off verify header.
Click to expand...
Click to collapse
I flashed the system.img but now the phone bootloops. It could be possible I got the wrong system.img because I don't know exactly what firmware my phone was on before I messed up. I only know it was EMUI8. Is there a way to completely reflash everything?
jetzecazemier said:
I flashed the system.img but now the phone bootloops. It could be possible I got the wrong system.img because I don't know exactly what firmware my phone was on before I messed up. I only know it was EMUI8. Is there a way to completely reflash everything?
Click to expand...
Click to collapse
Yes. I have guide thread here for that.
https://forum.xda-developers.com/honor-7x/how-to/guide-honor-7x-flash-oreo-update-t3781649
But also wipe in factory reset from stock recovery may solve the bootloop.
mrmazak said:
Yes. I have guide thread here for that.
https://forum.xda-developers.com/honor-7x/how-to/guide-honor-7x-flash-oreo-update-t3781649
But also wipe in factory reset from stock recovery may solve the bootloop.
Click to expand...
Click to collapse
Alright, I'll try that before I have a look at that thread
mrmazak said:
Yes. I have guide thread here for that.
https://forum.xda-developers.com/honor-7x/how-to/guide-honor-7x-flash-oreo-update-t3781649
But also wipe in factory reset from stock recovery may solve the bootloop.
Click to expand...
Click to collapse
I tried rebooting to stock recovery in order to factory reset but it only shows me the update, power off and reboot options so no factory reset possibility. I read through the entire thread you linked here but I'm very confused as to what to do with the full OTA file. I'm on a broken EMUI8 that bootloops and I'd like to clean flash EMUI8 again so I can flash an AOSP Oreo rom after that. What do I do?
jetzecazemier said:
I tried rebooting to stock recovery in order to factory reset but it only shows me the update, power off and reboot options so no factory reset possibility. I read through the entire thread you linked here but I'm very confused as to what to do with the full OTA file. I'm on a broken EMUI8 that bootloops and I'd like to clean flash EMUI8 again so I can flash an AOSP Oreo rom after that. What do I do?
Click to expand...
Click to collapse
Just made updates to guide last night. I think it is worded simple now.
Download my update "package" from step E
Extract it to a folder on your PC.
You are on emui8, so copy the HWOTA folder from the extracted zip to your sdcard
Also put hwota-update-7-8-auto.zip on sdcard.
Put the three (3) update files from pro-teammt.ru in the HWOTA8 folder on your sdcard
Put card into phone
Boot into twrp
Select install
Choose sdcard as source
Install hwota-update-7-8-auto.zip
mrmazak said:
Just made updates to guide last night. I think it is worded simple now.
Download my update "package" from step E
Extract it to a folder on your PC.
You are on emui8, so copy the HWOTA folder from the extracted zip to your sdcard
Also put hwota-update-7-8-auto.zip on sdcard.
Put the three (3) update files from pro-teammt.ru in the HWOTA8 folder on your sdcard
Put card into phone
Boot into twrp
Select install
Choose sdcard as source
Install hwota-update-7-8-auto.zip
Click to expand...
Click to collapse
So far so good but the FULLOTA update file I got from that website only has one file (update.zip) Do I need to extract that? And if so, what 3 files do I put on my sdcard?
jetzecazemier said:
So far so good but the FULLOTA update file I got from that website only has one file (update.zip) Do I need to extract that? And if so, what 3 files do I put on my sdcard?
Click to expand...
Click to collapse
No do not extract it.
On that site, next to link for update file, is "file list"
Click this. It gives links for all three files.
Put those three zip files into hwota folder
mrmazak said:
No do not extract it.
On that site, next to link for update file, is "file list"
Click this. It gives links for all three files.
Put those three zip files into hwota folder
Click to expand...
Click to collapse
Alright, I got it! Now I need to flash TWRP but the executable to install TWRP says my adb drivers are outdated. I have the minimal fastboot and adb installation from XDA.
jetzecazemier said:
Alright, I got it! Now I need to flash TWRP but the executable to install TWRP says my adb drivers are outdated. I have the minimal fastboot and adb installation from XDA.
Click to expand...
Click to collapse
That should be fine.
Usually means you have other adb also , probably from other tool.
If you have twrp , not need to use the terp recovery installer
mrmazak said:
That should be fine.
Usually means you have other adb also , probably from other tool.
If you have twrp , not need to use the terp recovery installer
Click to expand...
Click to collapse
Well the problem is I don't have TWRP and none of the versions i've tried to install work. The installer doesn't work either, it says closing adb daemon and stays on that.
jetzecazemier said:
Well the problem is I don't have TWRP and none of the versions i've tried to install work. The installer doesn't work either, it says closing adb daemon and stays on that.
Click to expand...
Click to collapse
Each step of the tool I put pause.
So it stopped on command and not closed.
Press spacebar
mrmazak said:
Each step of the tool I put pause.
So it stopped on command and not closed.
Press spacebar
Click to expand...
Click to collapse
Dude, you're the man! I got my device up and running again. I'll probably stay on EMUI8 since it's more stable than the current AOSP rom. I wanna root it tho so can I just use the lazy recovery tool to install twrp and simply install magisk?
jetzecazemier said:
Dude, you're the man! I got my device up and running again. I'll probably stay on EMUI8 since it's more stable than the current AOSP rom. I wanna root it tho so can I just use the lazy recovery tool to install twrp and simply install magisk?
Click to expand...
Click to collapse
Yes.
The lazy tool has recovery with encryption working
I got it working on EMUI8 but I decided to flash the aosp rom cuz i prefer stock android. Can't seem to get twrp to install tho. I keep getting "1 was unexpected at this time"
Hi All
Note: This procedure is for Windows PC only.
I can see there is a similar thread to help on rooting your device.
I created this thread it make it more easier and focussed just on rooting your device rather with additional information.
This menthod is to root your device without TWRP.
There is a detailed guide by @Freak07 which you can find here.
Prerequisite:
1. Your device bootloader is unlocked
2. You have enabled your Developer Options and enabled USB debugging (Settings > System > About phone > Software information, tap build number 7 times to enable Developer options)
3. Flash Tools, download from here and extract to your PC
4. Latest Magisk Manager which you can download from the relevant thread (search or click here)
BOOT IMAGES
Stock Boot images:
Firmware WW_16.1220.1906.174_0 >>>> Click here
Firmware WW_16.1220.1908.189_1.1.1 >>>> Click here
Patched Boot images:
Firmware WW_16.1220.1906.174_0 (patched with Magisk 19.3 stable version) >>>> Click here
Firmware WW_16.1220.1908.189_1.1.1 (patched with Magisk 19.3 stable version) >>>> Click here
Steps to Root:
1. Connect your device with USB cable
2. Go to the folder where you copied Flash Tools and double click to run cmd-here.exe
3. In the command prompt run the command adb devices, this will run the Deamon and show your device under List of devices attached. If doesn't show your device, check your device is connected and USB debugging is enabled.
4. Now run the command adb reboot bootloader to boot your device in to Fastboot mode
5. Now flash the patched boot image with the command fastboot flash boot magisk_patched.img
Restart your device with the fastboot command fastboot reboot and enjoy your ROOTED device
It works great, thanks!!
But then I installed miracast magisk module and now everytime I flash magisk patched boot, my phone is stuck on Asus logo so I have to flask stock boot to use my phone.
I think I should flash system image but when I unzip firmware from Asus site ( https://www.asus.com/Phone/ZenFone-6-ZS630KL/HelpDesk_Download/ ) on my mac,
It doesn't show any system image (or even boot image), only "compatibility" , "payload" and some other stuff.
Can you tell me what I am doing wrong?
EMJI79 said:
But then I installed miracast magisk module and now everytime I flash magisk patched boot, my phone is stuck on Asus logo so I have to flask stock boot to use my phone.
I think I should flash system image but when I unzip firmware from Asus site ( https://www.asus.com/Phone/ZenFone-6-ZS630KL/HelpDesk_Download/ ) on my mac,
It doesn't show any system image (or even boot image), only "compatibility" , "payload" and some other stuff.
Can you tell me what I am doing wrong?
Click to expand...
Click to collapse
Hi ASUS firmware for Zenfone do not have system img and instead it is the payload.bin which holds all system files. You can extract system image using python based tools.
You can remove the module if you flash TWPR and using file manger in TWRP to remove magix folder. This will remove magisk completely. Or, reset system via stock recovery. Completely switch off your device. Now, press and hold volume up button and press power button. It will help you to boot in to stock recovery. Or you can follow the guide here
If you still want to flash stock firmware, this link may help.
smohanv said:
Hi ASUS firmware for Zenfone do not have system img and instead it is the paylod.bin which holds all system files. You can extract system image using python based tools.
You can remove the module if you flash TWPR and using file manger in TWRP to remove magix folder. This will remove magisk completely. Or, reset system via stock recovery. Completely switch off your device. Now, press and hold volume up button and press power button. It will help you to boot in to stock recovery. Or you can follow the guide here
If you still want to flash stock firmware, this link may help.
Click to expand...
Click to collapse
If I just reset system via stock recovery, will I lose user data?
EMJI79 said:
If I just reset system via stock recovery, will I lose user data?
Click to expand...
Click to collapse
Yes you do. But you will not loose the files and folder in internal storage like photos etc..
You have to install all user applications again.
I would suggest you to follow the thread to flash TWRP and just remove magisk folder in TWRP file manager.
smohanv said:
Yes you do. But you will not loose the files and folder in internal storage like photos etc..
You have to install all user applications again.
I would suggest you to follow the thread to flash TWRP and just remove magisk folder in TWRP file manager.
Click to expand...
Click to collapse
I will do that.
Just another question: can I just boot in Twrp without installing it?
EMJI79 said:
I will do that.
Just another question: can I just boot in Twrp without installing it?
Click to expand...
Click to collapse
You can boot in to TWRP without permanently flashing it.
Take few cautions before you attempt to boot in to TWRP using this option,
1. Remove fingerprint in security settings (settings > Security & lock screen > Fingerprint)
2. Remove screen lock PIN in settings > security & lock screen > screen lock > select NONE here and also make sure Fingerprint is not enabled in this screen
How to boot in to TWRP:
Download TWRP from here
Use the command in Fastboot > fastboot boot twrp-3.3.1-15-ASUS_I01WD.img
Now you can use file manager in TWRP and remove magisk folder. You have to mount system folder to do so.
EMJI79 said:
I will do that.
Just another question: can I just boot in Twrp without installing it?
Click to expand...
Click to collapse
Did you try the method I explained here >> https://forum.xda-developers.com/showpost.php?p=80100285&postcount=8
smohanv said:
Did you try the method I explained here >> https://forum.xda-developers.com/showpost.php?p=80100285&postcount=8
Click to expand...
Click to collapse
I will do that now. I just came back home.
Thanks.
---------- Post added at 04:28 PM ---------- Previous post was at 03:58 PM ----------
Do you think I can this:
https://magiskroot.net/uninstall-magisk-module-twrp/
edit: it's for older versions of Magisk
Still I can't see the Magisk modules or Magisk folder in /data or /system/data , it appears empty
EMJI79 said:
I will do that now. I just came back home.
Thanks.
---------- Post added at 04:28 PM ---------- Previous post was at 03:58 PM ----------
Do you think I can this:
https://magiskroot.net/uninstall-magisk-module-twrp/
edit: it's for older versions of Magisk
Still I can't see the Magisk modules or Magisk folder in /data or /system/data , it appears empty
Click to expand...
Click to collapse
Are you able to boot in TWRP recovery as I mentioned. Please confirm.
Have you mounted system in twrp. It won't go anywhere. You should find it. I have done this several times.
Read here for some more help.
https://magiskroot.net/uninstall-magisk-module-twrp/
Sent from ASUS ZenFone 6 (2019) using Tapatalk
smohanv said:
Are you able to boot in TWRP recovery as I mentioned. Please confirm.
Have you mounted system in twrp. It won't go anywhere. You should find it. I have done this several times.
Read here for some more help.
https://magiskroot.net/uninstall-magisk-module-twrp/
Sent from ASUS ZenFone 6 (2019) using Tapatalk
Click to expand...
Click to collapse
Yes I am able to boot in TWRP and browse inside the files.
I am checking system square in TWRP mount section however I tried to mount data also and it isn't possible.
I will try the advised link later today, thanks for the help.
EMJI79 said:
Yes I am able to boot in TWRP and browse inside the files.
I am checking system square in TWRP mount section however I tried to mount data also and it isn't possible.
I will try the advised link later today, thanks for the help.
Click to expand...
Click to collapse
Yes. I did try as well. It seems like TWRP is loading in READ ONLY mode. I doubt whether you can flash the uninstall mod as well. But worth trying as you can save all your installed apps.
smohanv said:
Yes. I did try as well. It seems like TWRP is loading in READ ONLY mode. I doubt whether you can flash the uninstall mod as well. But worth trying as you can save all your installed apps.
Click to expand...
Click to collapse
Which method from the link do you advise to try first?
smohanv said:
Yes. I did try as well. It seems like TWRP is loading in READ ONLY mode. I doubt whether you can flash the uninstall mod as well. But worth trying as you can save all your installed apps.
Click to expand...
Click to collapse
Check this link and follow. https://forum.xda-developers.com/showpost.php?p=72542167&postcount=242
smohanv said:
Check this link and follow. https://forum.xda-developers.com/showpost.php?p=72542167&postcount=242
Click to expand...
Click to collapse
No luck, can't flash anything in TWRP ...
Guess I have to wait TWRP is updated.
Mauronofrio telling that one have to install 3.3.1-15 to write on data:
https://forum.xda-developers.com/ze...cial-twrp-recovery-asus-t3937844/post80108953
EMJI79 said:
Mauronofrio telling that one have to install 3.3.1-15 to write on data:
https://forum.xda-developers.com/ze...cial-twrp-recovery-asus-t3937844/post80108953
Click to expand...
Click to collapse
yes. I can see that there is an installer (magisk module) which has to be flashed in magisk in order for TWRP to write on data partition.
In your case, you cannot boot your device with rooted image as you have a module which is causing bootloop. Catch 22 sistuation.
In this situation I think you have only one option left which is resetting your device loosing all installed apps. Sorry mate. Could not help you at this time.
New Update
smohanv said:
yes. I can see that there is an installer (magisk module) which has to be flashed in magisk in order for TWRP to write on data partition.
In your case, you cannot boot your device with rooted image as you have a module which is causing bootloop. Catch 22 sistuation.
In this situation I think you have only one option left which is resetting your device loosing all installed apps. Sorry mate. Could not help you at this time.
Click to expand...
Click to collapse
Hello Smohanv,
Say I want to update to the latest Firmware that got released yesterday, and I am currently rooted via the method you introduced on the first page with firmware 16.1220.1906.174_0, how do I go about it?
If I do the Manual update, will I loose root? Or should I wait for you to release a patched one, and then do the manual update?
Thanks.
Damionix said:
Hello Smohanv,
Say I want to update to the latest Firmware that got released yesterday, and I am currently rooted via the method you introduced on the first page with firmware 16.1220.1906.174_0, how do I go about it?
If I do the Manual update, will I loose root? Or should I wait for you to release a patched one, and then do the manual update?
Thanks.
Click to expand...
Click to collapse
Yes you will loose root. Why do you go for build 171 when 189 is available now.
Official link: >>> https://www.asus.com/us/Phone/ZenFone-6-ZS630KL/HelpDesk_Download/
New build can be downloaded from here >>> Download
TWRP 3.3.1 & Root for Moto 1 VisionThanks to the efforts of yuri-2016 and and my humble contribution, the TWRP 3.3.1 was made from scratch and a new method of Root was tested.
Accept this gift from the bottom of your heart! :highfive:
Instructions
USB debugging must be enabled on the phone and the bootloader must be unlocked!
1. Download attached archive TWRP_Root_Motne_Vision.zip and extract files from it in the following order::
- .bat executive file and vbmeta.img to the folder with the firmware files;
- TWRP-3.3.1_Motorola_One_Vision.img to \adb\ folder.
- TWRP-3.3.1_Installer_Motorola_One_Vision.zip, Disable_Dm-Verity_ForceEncrypt.zip, Magisk Installer, MagiskManager copy to External SDcard in your phone.
2. Load phone in fastboot mode, then connect it to PC, then start an executive file .bat. At the end of flashing the phone will reboot into bootloader-mode and then TWRP again.
3. In the Recovery at the very beginning we put a checkmark in the checkbox to avoid this request in future, and give permission to modify the system for writing.
4. Go to the Wipe page and run the Format Data for decryption. Enter "yes" for the request. Exit to the Main Menu and reboot to Bootloader.
5. Attention! You mus BOOT into Recovery mode (DO NOT INSTALL it !), through the command:
Code:
fastboot boot C:\adb\TWRP-3.3.1_Motorola_One_Vision.img
6. Flash an archive TWRP-3.3.1_Installer_Motorola_One_Vision.zip which will make TWRP permanent.
NOTE: If you want to keep the stock Recovery , do not install this archive, but in order to boot into TWRP you will need to run the command from Step 5 every time.
7. Configure TWRP via “Settings”-page (time, time zone, language, etc.) as you want.
8. Go to “Install” page and flash the Magisk Installer , and flash Disable_Dm-Verity_ForceEncrypt.zip
9. Reboot in System. Phone will reboot several times, don`t worry. Perform initial settings again.
10. Install MagiskManager.apk, because the application installed in the system generates an error and does not start.
Now your device has a custom recovery TWRP and Root rights! :good: :victory:
01/10/2019 New instruction have been made
30/09/2019 New build TWRP !!!
Fixed: Removed the "Enable MTP" button.
Note: Who will reinstall the new TWRP build over the old one, follow these steps:
1. Download new TWRP_Root_Motne_Vision.zip
2. Load into Recovery mode via the command:
Code:
fastboot boot C:\adb\TWRP-3.3.1_Motorola_One_Vision.img
3. Install TWRP-3.3.1_Installer_Motorola_One_Vision.zip
4. Flash Magisk installer, Disable_Dm-Verity_ForceEncrypt.zip.
5. Reboot in the Recovery again.
6. Try to adjust the brightness, connect USB-OTG, check the absence of the "Enable MTP" button.
Old instructions
Friends! I got the Root for this device.
I'm not saying it's the only way to get a Root. I suggest something I used on my own device.
You are responsible for everything you do with your device!
Getting Root was performed on firmware XT1970-3_KANE_RETEU_DS_9.0_PSA29.160-30
Attention! The process of receiving the Root will delete all your data from the device.
1. The bootloader must be unlocked on the device beforehand.
2. Extract files from the archive https://drive.google.com/open?id=1xgTVlIXOFWq59I1-D9bnRlj1heJycT_I :
- vbmeta.img, vbmeta_patch.img and boot_patch.img to the adb folder;
- MagiskManager-v7.3.4.apk to a convenient folder for you. It will then need to be copied either to the phone memory or to the SD Card.
3. Load the device into fastboot mode and connect it to your PC.
4. Flash vbmeta.img with the command:
Code:
fastboot flash vbmeta_a vbmeta.img
5. Flash boot_patch.img with the command:
Code:
fastboot flash boot_a boot_patch.img
6. Flash vbmeta_patch.img command:
Code:
fastboot flash vbmeta_a vbmeta_patch.img
7. Load the device into the system by pressing the Start button. Phone will reboot in Recovery where there will be a warning that it is necessary to execute Factory reset. It is necessary to give your consent.
The phone will reboot several times again, don't worry.
8. Perform the initial setup. Install MagiskManager-v7.3.4.apk.
9. Launch the MagiskManager application. He will offer to update the application, click the Yes button. The phone will reboot.
Your device now has Root permissions and access to the system!
ilia3367 said:
Friends! I got the Root for this device. Tomorrow I will try to describe in detail the process of getting the Root.
Click to expand...
Click to collapse
Thank you so much!
That's incredible. I hope it works on Moto One Action too.
ilia3367 said:
Friends! I got the Root for this device. Tomorrow I will try to describe in detail the process of getting the Root.
Click to expand...
Click to collapse
This is excellent news, thanks !
Unlock the bootloader
Download the stock rom
Install magisk manager
Click install and chose patch boot image
Copy the patched boot image to your PC
Flash the new image using ADB
I think these are the steps to root the phone
SnoopDoggyStyleDogg said:
Unlock the bootloader
Download the stock rom
Install magisk manager
Click install and chose patch boot image
Copy the patched boot image to your PC
Flash the new image using ADB
I think these are the steps to root the phone
Click to expand...
Click to collapse
Those step give you the validation img error
I'm continuing with my friend to create TWRP
SnoopDoggyStyleDogg said:
Unlock the bootloader
Download the stock rom
Install magisk manager
Click install and chose patch boot image
Copy the patched boot image to your PC
Flash the new image using ADB
I think these are the steps to root the phone
Click to expand...
Click to collapse
That's what a lot of people think. I thought so too.
Thank you so much for the guide... I'll try in the afternoon
@ilia3367
Hello
I have a One Action, could you help me to get root?
Do I need to patch all those images with Magisk?
Thanks in advanced.
sfoot13 said:
@ilia3367
Do I need to patch all those images with Magisk?
Click to expand...
Click to collapse
Make a modified boot.img with Magisk and take my other files. Try to do it according to the instructions.
ilia3367 said:
Make a modified boot.img with Magisk and take my other files. Try to do it according to the instructions.
Click to expand...
Click to collapse
Thank you so much for your help and work!
I'll do that when I arrive at home
Hey! That's really good news pal. Do you think I can flash your Vision's vbmeta.img and vbmeta_patch.img and my magisk-patched boot.img on my Motorola One Action?
Tuandroidaldia said:
Hey! That's really good news pal. Do you think I can flash your Vision's vbmeta.img and vbmeta_patch.img and my magisk-patched boot.img on my Motorola One Action?
Click to expand...
Click to collapse
Replied on the previous page.
ilia3367 said:
Replied on the previous page.
Click to expand...
Click to collapse
Nope, it's not working on Motorola One Action, it says: "<bootloader> validation image failed" using my Magisk Patched Boot.img. Did you patched your boot using another tool or how?
Thanks.
@ilia3367 Finally Rooted. Thank you so much for your work. Very appreciate!
Tuandroidaldia said:
Nope, it's not working on Motorola One Action, it says: "<bootloader> validation image failed" using my Magisk Patched Boot.img. Did you patched your boot using another tool or how?
Thanks.
Click to expand...
Click to collapse
what about vbmeta? was possible to flash it?
@ilia3367 before Root and after unlock the bootloader when I touched the system update option, it said: "system integrity is compromised" now after Root when i touch it , it check for update again. It means that I can update the firmware via ota?
AndresOrue said:
@ilia3367 before Root and after unlock the bootloader when I touched the system update option, it said: "system integrity is compromised" now after Root when i touch it , it check for update again. It means that I can update the firmware via ota?
Click to expand...
Click to collapse
Magisk probably hides the bootloader status so that update check works, but it will most likely fail during install. At least that's how it works on moto one and moto one power.
On moto one I either reflash current build without wipe and then take ota and re-root after, or just flash the update if I get them early, and re-root-
AndresOrue said:
It means that I can update the firmware via ota?
Click to expand...
Click to collapse
I don't think it's possible. The system must be completely virgin to update the OTA. Then why do I need a Root? I need it to customize the system.
ilia3367 said:
I don't think it's possible. The system must be completely virgin to update the OTA. Then why do I need a Root? I need it to customize the system.
Click to expand...
Click to collapse
Thanks a lot. I just unlocked my BL for the second time and this root method is working fine.
May I ask if you just used magisk manager to patch boot, cause when I do I get error on flash.
Code:
(bootloader) is-logical:boot_a: not found
Sending 'boot_a' (33792 KB) OKAY [ 1.172s]
Writing 'boot_a' FAILED (Status read failed (Too many links))
And how did you patch vbmeta?
I'm just curious since this patched boot isn't the latest and I wonder how to make this work with the latest boot.img from September patch update.
FIrst off many thanks to @vhercastillojr (as this thread is essentially his) and Chicken from the Vietnam telegram group for providing the RAW's/img's
********** DO THIS AT YOUR OWN RISK!!! I am not liable to any damage if you accidentally brick your device. This will void your warranty, if you had one. Also, using this method you won't be able to revert back to CN roms, lock your bootloader again and recieve OTAs, your device will be blacklisted by Asus ************
NOTE: To check your current fingerprint, download and install device info HW from the playstore. Under 'system' you'll find the current rom (CN or WW), the product id and fingerprint - they all need to match to be able to update your device later
NOTE 2: The main guide below skips early roms straight to last Android 9 for ROG II. For one user it didn't work and they had to use the previous, unedited guide which was based on 1910.35 RAW. If the below guide fails to update follow the additional guide at the end of this post.
----------
0) Download the ROG phone unlock tool and copy it on your phone and install it then run it. The phone will boot twice. DO NOT PRESS POWER TO STOP THE BOOT. It will wipe your data automatically. This will unlock your bootloader. EDIT: NEWER VERSION OF THE TOOL CAN BE FOUND here
NOTE: this will void your warranty, if you had one, with Asus, even if you re-lock your bootloader later... (Although, having bought mine as an import from China, I'm think the warranty only stands with the seller - in my case, 1 year, not Asus - but i may be wrong)
1) Download the WW International RAW rom from here
2) Extract the file on your PC. Boot the phone into fastboot mode (hold volume up then press and hold power button, Fastboot mode is the 1st screen you come across, the one with the options to Start, boot to recovery, etc...) connect to the side port and run "flashall_AFT.cmd" wait for it to finish and the phone will restart itself (it will take a number of minutes to complete, with the cmd window open all the time. If the cmd window only flashes up and closes down, then check the rest of the notes with this step).
NOTE: you need to remove or delete the original zip from the raw folder once extracted as it confuses the Flashall_AFT.cmd with the raw rom and zip having the same name. Also, it can help to extract to the root of C drive.
3) Download and install Minimal ADB and Fastboot app (windows). Install it on your PC to root of C drive
4) Download the rootww191064.img and place it in the Minimal ADB and Fastboot Folder (C:\Program Files (x86)\Minimal ADB and Fastboot) from here
5) Run Minimal ADB and Fastboot by double clicking ''cmd-here.exe''. Switch the phone into fastboot mode (hold volume up then press and hold power button) then type "fastboot flash boot rootww191064.img" without quotation marks
NOTE: you can also check your device is recognised in fastboot mode by the pc/laptop by running ''fastboot devices'' cmd which should show your device serial
6) Reboot the phone and connect it to PC, copy and install Magisk and Root Explorer
Magisk
root explorer
-run magisk, (update if necessary) and grant access to root explorer (after opening root explorer you should be prompted by magisk to gain root access, click 'allow')
7) Open the Root Explorer App on you phone. Then from the app, select Mount R/W to R/O. Search for "/vendor/factory" folder and Edit the file content COUNTRY from CN to WW (ALL Capital). Scroll to "/system/etc/AsusTheme/themes" then delete the hidden file to enable the hidden themes.
8) Restart the Phone. You are done. Check again with device info HW that your fingerprint has indeed been successfully changed.
From here, if you want to be on latest Android 10, download version 2004.60 from here (full zip), place it in root of internal storage and reboot. That'll bring you to A10.
NOTE: For those of you that are rooted: Download the full zip, move to root of internal storage and reboot. System will detect and prompt to update, click update. Wait until it finishes but DON'T click 'restart', instead, click 'restart later'. Go to Magisk manager. Click 'install' for Magisk. Click the last option 'install to inactive slot after OTA'. Click confirm force flash. Reboot when prompted. Done - root kept intact.
Repeat the process for latest (currently 2012.65) using the same link above. Your phone should hopefully skip the other versions and be straight to latest. If not, you'll have to go through 2007.27, 2009.49 and finally to current latest 2012.65. Repeat the process mentioned above for keeping root if so desired
----------
For anyone still running early roms that 1910.64 won't flash directly to, use the same guide above but with the following corrections:
2) Follow the exact same instructions but using this 1910.35 RAW
4) Download root and stock boot img's and extract them to Minimal ADB and Fastboot Folder (C:\Program Files (x86)\Minimal ADB and Fastboot)
5) Run Minimal ADB and Fastboot by double clicking ''cmd-here.exe''. Switch the phone into fastboot mode (hold volume up then press and hold power button) then type "fastboot flash boot rootww191035.img" without quotation marks
NOTE: you can also check your device is recognised in fastboot mode by the pc/laptop by running ''fastboot devices'' cmd which should show your device serial
After doing the ammended steps above for 1910.35, follow the rest of the guide to change fingerprint, then update to 1910.64 zip, place it in root of internal storage and reboot.
NOTE: For those of you that are rooted: Download the full zip, move to root of internal storage and reboot. System will detect and prompt to update, click update. Wait until it finishes but DON'T click 'restart', instead, click 'restart later'. Go to Magisk manager. Click 'install' for Magisk. Click the last option 'install to inactive slot after OTA'. Click confirm force flash. Reboot when prompted. Done - root kept intact.
******************* Thanks to @Barbatos19, who suggested I make video. Sorry to say I wont be, BUT several of you guys have recommended THIS VIDEO as a good reference guide... Hope it helps some others *******************
Finally(!!!), apologies that this post has become cluttered with instructions, I have tried to cater for all you and all eventualities!! Good luck
Thanks for this guide bro. Fully converted from CN to WW.
It wilk work if i have now flashed WW rom but with CN fingerprint? It was like this when i bought from GearBest
Zdrpkamil said:
It wilk work if i have now flashed WW rom but with CN fingerprint? It was like this when i bought from GearBest
Click to expand...
Click to collapse
Which rom version are running, if it's already 1910.35 then you can skip the flashing rom part. But if it's different, you need to follow each step
reg66 said:
Which rom version are running, if it's already 1910.35 then you can skip the flashing rom part. But if it's different, you need to follow each step
Click to expand...
Click to collapse
1906.19
Zdrpkamil said:
1906.19
Click to expand...
Click to collapse
You need to follow each step then
reg66 said:
You need to follow each step then
Click to expand...
Click to collapse
Ok, thanks. I'll do it at weekend and tell if works
what to do when the phone gets stuck on bootloop after flashing rootww191035.img and holding the power button doesnt work either?
Spawn_Ishan said:
what to do when the phone gets stuck on bootloop after flashing rootww191035.img and holding the power button doesnt work either?
Click to expand...
Click to collapse
Edit; didn't realise you were at this stage... Are you sure the flashing of the raw rom worked OK? Did you a cmd window open for a good 5-10 mins while the rom flashed?
Will KingRoot app work to root this phone? Don't want to have to wipe data to root.
I am pretty sure it won't, but humor me. Or is their something else out there that works?
jkeener88 said:
Will KingRoot app work to root this phone? Don't want to have to wipe data to root.
Click to expand...
Click to collapse
No idea... But im doubtful
hi bro
your link unlock tool its 190702..i can use it?
my rom ww1908.12 with finger CN
your file link name in step 4 is not same and file name is step 5..
its a same file to use?step 4 name boot&rootww and step 5 file ne to use rootww..do need to rename file step 4 to rootww?
and u have link l file to unroot 191035?
thx bro
wilsen1985 said:
hi bro
your link unlock tool its 190702..i can use it?
my rom ww1908.12 with finger CN
your file link name in step 4 is not same and file name is step 5..
its a same file to use?step 4 name boot&rootww and step 5 file ne to use rootww..do need to rename file step 4 to rootww?
and u have link l file to unroot 191035?
thx bro
Click to expand...
Click to collapse
One moment, I'll check the links... And yes, that is the only unlock tool available from asus website...
EDIT: yes, the zip file to download in step 4 needs to be extracted. it contains both the root boot img and stock img for later on when you unroot etc (both root and stock boot img's are for 1910.35). you need to place the rootww191035.img in the same folder as adb... and do the same for the stock boot.img for later use... read the instructions carefully...
reg66 said:
One moment, I'll check the links... And yes, that is the only unlock tool available from asus website...
Click to expand...
Click to collapse
i can't find link unroot 191035..
do u have thats link?
wilsen1985 said:
i can't find link unroot 191035..
do u have thats link?
Click to expand...
Click to collapse
in step 4) you download a .zip file that conatins BOTH rootww191035.img AND boot.img - the boot.img IS the stock boot for unrooting 1910.35, you need to extract both img's to adb folder on your pc.
reg66 said:
One moment, I'll check the links... And yes, that is the only unlock tool available from asus website...
EDIT: yes, the zip file to download in step 4 needs to be extracted. it contains both the root boot img and stock img for later on when you unroot etc (both root and stock boot img's are for 1910.35). you need to place the rootww191035.img in the same folder as adb... and do the same for the stock boot.img for later use... read the instructions carefully...
Click to expand...
Click to collapse
oh ok thx bro
1 question again
yesterday i download file raw ww1910.35 zip on asus website
can i use its raw file to this tutor or must download raw file in page 1?
wilsen1985 said:
oh ok thx bro
1 question again
yesterday i download file raw ww1910.35 zip on asus website
can i use its raw file to this tutor or must download raw file in page 1?
Click to expand...
Click to collapse
What you downloaded is not, I think, the raw rom, its the update zip for those who have already changed fingerprint and are simply updating... Please use the links in 1st page...
reg66 said:
What you downloaded is not, I think, the raw rom, its the update zip for those who have already changed fingerprint and are simply updating... Please use the links in 1st page...
Click to expand...
Click to collapse
oh ok bro
i download raw in page 1 n when its complete i start for flash..
hope im succes for all convert
thx bro..
wilsen1985 said:
oh ok bro
i download raw in page 1 n when its complete i start for flash..
hope im succes for all convert
thx bro..
Click to expand...
Click to collapse
Good luck, make sure you read it all and follow each step accurately
reg66 said:
Good luck, make sure you read it all and follow each step accurately
Click to expand...
Click to collapse
ok bro very thx..