[Q] How to install WW firmware in a CN recovery? - ZenFone 2 Q&A, Help & Troubleshooting

I bought Zenfone 2 that initially had a WW firmware but a CN recovery. When I tried updating the firmware to UL-Z00A-WW-2.15.40.10-user, it threw an assertion failure because the device image SKU is CN while the OTA image SKU is WW. I wanted to update the firmware because of the persistent permission bug that was claimed to be solved by just updating the firmware. Since there is an assertion failure, I tried installing UL-Z00A-CN-2.14.40.22-user and it installed successfully. Unfortunately, google play store is now gone.. And I wanted to install WW OTA but it continually fails.
How do I fix this? Help.

Xegara said:
I bought Zenfone 2 that initially had a WW firmware but a CN recovery. When I tried updating the firmware to UL-Z00A-WW-2.15.40.10-user, it threw an assertion failure because the device image SKU is CN while the OTA image SKU is WW. I wanted to update the firmware because of the persistent permission bug that was claimed to be solved by just updating the firmware. Since there is an assertion failure, I tried installing UL-Z00A-CN-2.14.40.22-user and it installed successfully. Unfortunately, google play store is now gone.. And I wanted to install WW OTA but it continually fails.
How do I fix this? Help.
Click to expand...
Click to collapse
1) Download recovery image file (https://app.box.com/s/ohk0aki3nfxjqyuygbl629612tfmi6d9)
2) Boot to fastboot mode (Power + Vol Up)
3) Using ADB command prompt flash recovery by using command : fastboot flash recovery recovery.img
4) reboot to fastboot again
5) launch recovery from fastboot
6) Flash the latest WW firmware same way u flashed latest CN firmware
7) wipe cache
8) reboot
Then Flash system.img directly like you flashed recovery.img :
1) Download system image file (http://www.mediafire.com/download/xf...oot_system.zip)
2) Boot to fastboot mode (Power + Vol Up)
3) Using ADB command prompt flash system by using command : fastboot flash system system.img
4) wipe cache
5) reboot
This will make ur phone WW and you can simply update with any ww firmware ota or by downloading zip from Asus site.

I followed your procedure from a previous thread and it worked perfectly! Thank you.

Broken link
Link for the system.img is dead.
The link redirects to...
HTTP WWW mediafire DOT com/error.php? errno=320

smartbuddy said:
1) Download recovery image file
2) Boot to fastboot mode (Power + Vol Up)
3) Using ADB command prompt flash recovery by using command : fastboot flash recovery recovery.img
4) reboot to fastboot again
5) launch recovery from fastboot
6) Flash the latest WW firmware same way u flashed latest CN firmware
7) wipe cache
8) reboot
Then Flash system.img directly like you flashed recovery.img :
1) Download system image file
2) Boot to fastboot mode (Power + Vol Up)
3) Using ADB command prompt flash system by using command : fastboot flash system system.img
4) wipe cache
5) reboot
This will make ur phone WW and you can simply update with any ww firmware ota or by downloading zip from Asus site.
Click to expand...
Click to collapse
Thank you for sharing your knowledge. But the link for the system.img is dead.
The link redirects to...
HTTP WWW mediafire DOT com/error.php? errno=320
Can I ask for another download link?

Xegara said:
Thank you for sharing your knowledge. But the link for the system.img is dead.
The link redirects to...
HTTP WWW mediafire DOT com/error.php? errno=320
Can I ask for another download link?
Click to expand...
Click to collapse
Will upload tommorrow. Sorry for the delay.

Same Problem. Now with CN Version and no google play etc
rootcron said:
I followed your procedure from a previous thread and it worked perfectly! Thank you.
Click to expand...
Click to collapse
Hi.. it seem that you were able to fix it.. to me its the first time trying to root or flash a phone.. what can i do in order to fix this? do you have like a step by step way .
I already download all the files and IMG files.. also i have the firmware downloads from asus support page.. i hope you can help me... thanks

Xegara said:
Thank you for sharing your knowledge. But the link for the system.img is dead.
The link redirects to...
HTTP WWW mediafire DOT com/error.php? errno=320
Can I ask for another download link?
Click to expand...
Click to collapse
Here you go for system.img :
http://www.mediafire.com/download/1nwpoqo8rpi1kur/Z00A_2.13.40.13_preroot_system.zip

smartbuddy said:
Here you go for system.img :
HTTP WWW mediafire DOT com download/1nwpoqo8rpi1kur/Z00A_2.13.40.13_preroot_system.zip
Click to expand...
Click to collapse
Thanks a lot! It worked! You just saved my zenfone 2! By the way, I was wondering why I needed to flash the pre-root system image if I already flashed the firmware? What is their difference aside from the pre-root system image being pre-rooted?
I installed the firmware which is UL-Z00A-WW-2.15.40.10-user. But now, the version was 2.13.40.13, same as the system.img.
So either of the images (firmware or pre-rooted system) is sufficient enough after installing the recovery image?

Xegara said:
Thanks a lot! It worked! You just saved my zenfone 2! By the way, I was wondering why I needed to flash the pre-root system image if I already flashed the firmware? What is their difference aside from the pre-root system image being pre-rooted?
I installed the firmware which is UL-Z00A-WW-2.15.40.10-user. But now, the version was 2.13.40.13, same as the system.img.
So either of the images (firmware or pre-rooted system) is sufficient enough after installing the recovery image?
Click to expand...
Click to collapse
Yes either of them should be ok. Some people are unable to update to latest ww firmware even after installing ww recovery hence need to flash pre root system.img.
Once u have installed ww recovery and ww system you have converted to ww phone and can update to any ww firmware in future.

smartbuddy said:
Yes either of them should be ok. Some people are unable to update to latest ww firmware even after installing ww recovery hence need to flash pre root system.img.
Once u have installed ww recovery and ww system you have converted to ww phone and can update to any ww firmware in future.
Click to expand...
Click to collapse
I see. I was wondering where did you find the recovery.img? The recovery.img cannot be found on asus official website. Is there a tool to extract the recovery.img of an existing android phone?

smartbuddy said:
1) Download recovery image file ...
2) Boot to fastboot mode (Power + Vol Up)
3) Using ADB command prompt flash recovery by using command : fastboot flash recovery recovery.img
4) reboot to fastboot again
5) launch recovery from fastboot
6) Flash the latest WW firmware same way u flashed latest CN firmware
7) wipe cache
8) reboot
Then Flash system.img directly like you flashed recovery.img :
1) Download system image file ...
2) Boot to fastboot mode (Power + Vol Up)
3) Using ADB command prompt flash system by using command : fastboot flash system system.img
4) wipe cache
5) reboot
This will make ur phone WW and you can simply update with any ww firmware ota or by downloading zip from Asus site.
Click to expand...
Click to collapse
I get error, when try to flash system.img
C:\fastboot_adb(1.0.32)_071114_r21>fastboot flash recovery system.img
target reported max download size of 536870912 bytes
sending sparse 'recovery' (524257 KB)...
OKAY [ 18.063s]
writing 'recovery'...
FAILED (remote: flash_cmds error!)
finished. total time: 19.015s
there is any clue ?

sonic2epix said:
I get error, when try to flash system.img
C:\fastboot_adb(1.0.32)_071114_r21>fastboot flash recovery system.img
target reported max download size of 536870912 bytes
sending sparse 'recovery' (524257 KB)...
OKAY [ 18.063s]
writing 'recovery'...
FAILED (remote: flash_cmds error!)
finished. total time: 19.015s
there is any clue ?
Click to expand...
Click to collapse
Your command is wrong, fastboot flash recovery system.img (You are giving command to flash recovery and giving system.img )
Use the command fastboot flash system system.img
If you still get the error, try after restarting the PC.

smartbuddy said:
Your command is wrong, fastboot flash recovery system.img (You are giving command to flash recovery and giving system.img )
Use the command fastboot flash system system.img
If you still get the error, try after restarting the PC.
Click to expand...
Click to collapse
Oops, sorry .. my command is wrong, thanks ..

http://forum.xda-developers.com/zenfone2/help/how-to-upgrade-cn-version-to-ww-t3101556

help with zenfone 2
I ordered a zenfone 2 from Taiwan but its the ww version. My question is....I ordered it because it says that it supports 1700mhz/2100mhz and aws band 4...I am with Mobilicity in Canada...For the life of me I cannot get this stupid phone to recognize my sim card. Ive messed around with the settings, changed sim card slots...tried everything I can think of, and its still not working. Will this method (or any you know of) get it working?

Are 2nd Set of Steps Necessary?
smartbuddy said:
1) Download recovery image file
2) Boot to fastboot mode (Power + Vol Up)
3) Using ADB command prompt flash recovery by using command : fastboot flash recovery recovery.img
4) reboot to fastboot again
5) launch recovery from fastboot
6) Flash the latest WW firmware same way u flashed latest CN firmware
7) wipe cache
8) reboot
Then Flash system.img directly like you flashed recovery.img :
1) Download system image file
2) Boot to fastboot mode (Power + Vol Up)
3) Using ADB command prompt flash system by using command : fastboot flash system system.img
4) wipe cache
5) reboot
This will make ur phone WW and you can simply update with any ww firmware ota or by downloading zip from Asus site.
Click to expand...
Click to collapse
First of all, thanks so much smartbuddy for taking the time to write up these steps and provide the necessary files. I've been working on this issue for 12+ hours and am now finally resolving with your information. I just have a couple of questions.
I completed the first set of steps without issue and ended up right where I wanted to be - with the most recent firmware version and the ability to check for software upgrades OTA (finally had the button now!). I then went through the second set of steps without issue until I booted my phone after clearing the cache - it hung while booting. I waited for like 15-20 min. and then rebooted, but it hung again. No errors or anything, just booting. So when this happened, I went back through the first set of steps and am now again right where I want to be - with the firmware I want and the ability to check for upgrades OTA.
So do I have to attempt to go through the second set of steps again? And if so, do you have any idea why my phone hung while doing so the first time? Also, with my phone in it's current state, if I were to do a factory reset in the future, would it take me all the way back to square one without any of these updates? Sorry if this is a nube question, I'm still learning.
Thanks again for all your help. You da man! :good:

tapierce said:
First of all, thanks so much smartbuddy for taking the time to write up these steps and provide the necessary files. I've been working on this issue for 12+ hours and am now finally resolving with your information. I just have a couple of questions.
I completed the first set of steps without issue and ended up right where I wanted to be - with the most recent firmware version and the ability to check for software upgrades OTA (finally had the button now!). I then went through the second set of steps without issue until I booted my phone after clearing the cache - it hung while booting. I waited for like 15-20 min. and then rebooted, but it hung again. No errors or anything, just booting. So when this happened, I went back through the first set of steps and am now again right where I want to be - with the firmware I want and the ability to check for upgrades OTA.
So do I have to attempt to go through the second set of steps again? And if so, do you have any idea why my phone hung while doing so the first time? Also, with my phone in it's current state, if I were to do a factory reset in the future, would it take me all the way back to square one without any of these updates? Sorry if this is a nube question, I'm still learning.
Thanks again for all your help. You da man! :good:
Click to expand...
Click to collapse
No you can skip that if you wish. I have moved to Oneplus 2 so dont have a zenfone 2 anymore.

Related

[Q] HTC M8 Developer edition

Hi
I own a HTC M8 Developer edition with TWRP recovery.
Pretty new to thisforum, so any guidance/help would be much appreciated.
I am getting OTA updates on mobile, but when i try to install it; it takes me to TWRP screen and update doesnt get installed.
Currently, i am running on android 4.4.2 And i badly want to update my Android
Please guide me, how to install the update and any future updates(steps to follow)
Thanks
prashanal said:
Hi
I own a HTC M8 Developer edition with TWRP recovery.
Pretty new to thisforum, so any guidance/help would be much appreciated.
I am getting OTA updates on mobile, but when i try to install it; it takes me to TWRP screen and update doesnt get installed.
Currently, i am running on android 4.4.2 And i badly want to update my Android
Please guide me, how to install the update and any future updates(steps to follow)
Thanks
Click to expand...
Click to collapse
All Your Ques/Ans Goes Here : HTC One M8 Help Forums
prashanal said:
Hi
I own a HTC M8 Developer edition with TWRP recovery.
Pretty new to thisforum, so any guidance/help would be much appreciated.
I am getting OTA updates on mobile, but when i try to install it; it takes me to TWRP screen and update doesnt get installed.
Currently, i am running on android 4.4.2 And i badly want to update my Android
Please guide me, how to install the update and any future updates(steps to follow)
Thanks
Click to expand...
Click to collapse
it depends on how much you have done to the phone while it's rooted
the system / and recovery must be completely stock for the OTA to work
if your s-off it's easy to flash an older RUU to restore your phone to stock
I have all the Developer Edition files needed here >> https://www.androidfilehost.com/?w=files&flid=21320
the steps if your s-on are
fastboot flash recovery recovery.img (use the one that matches your current firmware version)
then attempt to install the OTA
if the OTA fails just use the RUU for the latest version
for s-on you have to fastboot oem lock the bootloader to flash the RUU
fastboot oem rebootRUU
fastboot flash zip RUU.zip
fastboot flash zip RUU.zip
fastboot reboot
Hi
Thanks man, had some errors and mistakenly deleted the OS on TWRP...
now im stuck without a OS.
So just posted another thread...help me if you can
Connect your phone in fastboot, the post the output of fastboot getvar all (but remove your IMEI and serial number) and we can go from there
EddyOS said:
Connect your phone in fastboot, the post the output of fastboot getvar all (but remove your IMEI and serial number) and we can go from there
Click to expand...
Click to collapse
im currently in office, as soon as i hit home!! i will post the necessary stuff man...
thanks
Prashan
found the details... eddyOS please have a look and guide me..
OK, for a start you do not have the Developer Edition. you first need to get back to stock which will more likely involve restoring this backup using TWRP 2.8.1.0 https://mega.co.nz/#!sYQFjSYK!Q6BZ4FxxQj7raBSxQFHBGRPYBFO69PwrjQxMo1bJaoA
You'll then need the stock recovery for 1.60.708.2 (that's the backup build) and then get the OTAs to get to Lollipop
@ckpv5 might be better to ask as he is the backup king but he is busy
clsA said:
it depends on how much you have done to the phone while it's rooted
the system / and recovery must be completely stock for the OTA to work
if your s-off it's easy to flash an older RUU to restore your phone to stock
I have all the Developer Edition files needed here >> https://www.androidfilehost.com/?w=files&flid=21320
the steps if your s-on are
fastboot flash recovery recovery.img (use the one that matches your current firmware version)
then attempt to install the OTA
if the OTA fails just use the RUU for the latest version
for s-on you have to fastboot oem lock the bootloader to flash the RUU
fastboot oem rebootRUU
fastboot flash zip RUU.zip
fastboot flash zip RUU.zip
fastboot reboot
Click to expand...
Click to collapse
Do this. Your firmware version is a few versions old and this will update it for you. You should probably learn how to return to stock (RUU) and use fastboot/adb if you are going to start flashing things, because things like this happen.
Sent from my HTC M8
Keithn said:
Do this. Your firmware version is a few versions old and this will update it for you. You should probably learn how to return to stock (RUU) and use fastboot/adb if you are going to start flashing things, because things like this happen.
Sent from my HTC M8
Click to expand...
Click to collapse
It won't work as the OP doesn't have the DE
EddyOS said:
It won't work as the OP doesn't have the DE
Click to expand...
Click to collapse
thanks for the reply... please can you tell me steps to follow after i download the zip.
i have very limited idea on installing the stuff
would appreciate your, help on steps to follow.
Prashan
1. Install TWRP 2.8.1.0 - http://techerrata.com/browse/twrp2/m8
command fastboot flash recovery openrecovery-twrp-2.8.1.0-m8.img
2. Download TWRP backup 1.60.708.2 from the link that EddyOS gave you
3. Download stock 1.60.708.2 recovery - http://sourceforge.net/projects/htconem8/files/Recovery/recovery_1.60.708.2.img/download
4. Extract the downloaded M8_CID_HTC__622_1.60.708.2.7z on PC
5. Boot to TWRP recovery and make a backup of boot only, this is to see where the backup goes on your device.
6. Reboot, connect device to PC then open Internal Storage, TWRP/BACKUPS/SerialNo./
7. Transfer the extracted [M8_CID_HTC__622_1.60.708.2 folder (the last folder) and its content to the backup path on your device
TWRP/BACKUPS/SerialNo./BackupFolderHere
8. Reboot to TWRP, wipe your device - in TWRP go to wipe - advance - select dalvik cache, cache, data, system (only these)
9. Restore the transferred backup - make sure all boot, data & system are ticked - swipe to restore
10. In reboot menu select bootloader
11. fastboot flash stock recovery that you downloaded - command fastboot flash recovery recovery_1.60.708.2.img
12. reboot - check for OTA, download, install
13. repeat step 12 until the last OTA 4.18.708.12
14. done
If you want to flash TWRP again, use the latest TWRP 2.8.5.0 after last OTA 4.18.708.12
ckpv5 said:
1. Install TWRP 2.8.1.0 - http://techerrata.com/browse/twrp2/m8
command fastboot flash recovery openrecovery-twrp-2.8.1.0-m8.img
2. Download TWRP backup 1.60.708.2 from the link that EddyOS gave you
3. Download stock 1.60.708.2 recovery - http://sourceforge.net/projects/htconem8/files/Recovery/recovery_1.60.708.2.img/download
4. Extract the downloaded M8_CID_HTC__622_1.60.708.2.7z on PC
5. Boot to TWRP recovery and make a backup of boot only, this is to see where the backup goes on your device.
6. Reboot, connect device to PC then open Internal Storage, TWRP/BACKUPS/SerialNo./
7. Transfer the extracted [M8_CID_HTC__622_1.60.708.2 folder (the last folder) and its content to the backup path on your device
TWRP/BACKUPS/SerialNo./BackupFolderHere
8. Reboot to TWRP, wipe your device - in TWRP go to wipe - advance - select dalvik cache, cache, data, system (only these)
9. Restore the transferred backup - make sure all boot, data & system are ticked - swipe to restore
10. In reboot menu select bootloader
11. fastboot flash stock recovery that you downloaded - command fastboot flash recovery recovery_1.60.708.2.img
12. reboot - check for OTA, download, install
13. repeat step 12 until the last OTA 4.18.708.12
14. done
If you want to flash TWRP again, use the latest TWRP 2.8.5.0 after last OTA 4.18.708.12
Click to expand...
Click to collapse
step 5: when i try this, it shows as back up fail(E im unable to see device on the PC to transfer the downloaded file!! any help?
EddyOS said:
It won't work as the OP doesn't have the DE
Click to expand...
Click to collapse
Ah okay. Thought it was because of how it was listed. There might still be an RUU for whichever model that is.
Sent from my HTC M8
Thank you
prashanal said:
step 5: when i try this, it shows as back up fail(E im unable to see device on the PC to transfer the downloaded file!! any help?
Click to expand...
Click to collapse
@EddyOS @ckpv5 you guys are great!! you guys just restored faith in online forums......advise and file from eddy and steps from ckpv5 just worked like a charm...
Thank you guys......thanks isnt enough for this help......
Prashan
:victory: :victory: :victory: :victory:

Zenfone 2 Z00AD doesn't have "System update"

Hi guys,
I just bought an Asus ZE551ML Z00AD. I do not have the "System update" voice under Settings > About, and i noticed that the DM Client is not installed.
What can I do? Thanks!
giuliog.96 said:
Hi guys,
I just bought an Asus ZE551ML Z00AD. I do not have the "System update" voice under Settings > About, and i noticed that the DM Client is not installed.
What can I do? Thanks!
Click to expand...
Click to collapse
Have you tried a factory reset? Either by recovery or settings should work fine
I tried a factory reset, without results.
I'm going to try to download the update from Asus website, hoping that it will find it when i put it in the root of the sdcard.
I'll let you know!
Go to about and check the rom version, it could be a WW rom over a CN rom but if the bootloader has been flashed you can't seem to go to a lower firmware version than whats on.
Go to the Android developement>pre-rooted roms and download a pre-rooted rom from there... Make sure it has an equal or higher build date than the installed rom.
I installed all the img files through fastboot using these commands (make sure you use these commands exactly or you will brick your phone, just flashing something over the same partition does nothing)-
fastboot flash recovery recovery.img
fastboot flash boot boot.img
fastboot flash fastboot droidboot.img
fastboot flash system system.img
The img files are inside the fastboot tools folders and must be named the same as the the end, system.img for the rom must be system.img, not 139.img or it won't find it...
Then I wiped cache also using "Fastboot erase cache".
I now have a pre-rooted rom installed with WW firmware. I may not get OTA as the serial number would be registered on the CN server not WW but these updates are easily installed thanks to the hard work of people like Shakalaka...
Just go to the ASUS website and download the latest update that matches your firmware, for example ww, cn, jp etc. When I first got my device it had a firmware from May installed which had no update options under the about phone settings too and as soon as I downloaded the latest firmware put it on the root of my device it detected it and installed.

[HELP] Can't flash Stock 7.0Nougat via Stock Recovery...

I got a ZF3 Deluxe from Italy, is TIM branded, and stuck on MM 6.0, no updated released for this brand, so a friend of mine told me there is of course android 7 for ZF3Deluxe, so i wanted to manually upgrade system to 7.0 Nougat, i downloaded the Stock ROM from asus (2.15ghz cpu, i've checked of course) but when i try to flash it from the Stock Recovery i get this error (see the attachment) i also attach the software informations, (looking at the error i receive it may see the archive is corrupted, but i've tried to download it from Asus many and many times)
You have a carrier rom on your phone and the international version fails the upgrade check.
If you could get your bootloader unlocked that would be a way around it but you need to upgrade to a certain rom version to do that and the carrier hasn't supplied that rom...
You're essentially screwed until the carrier either releases the bootloader unlockable rom or upgrades the rom to nougat...
LeGrim said:
I got a ZF3 Deluxe from Italy, is TIM branded, and stuck on MM 6.0, no updated released for this brand, so a friend of mine told me there is of course android 7 for ZF3Deluxe, so i wanted to manually upgrade system to 7.0 Nougat, i downloaded the Stock ROM from asus (2.15ghz cpu, i've checked of course) but when i try to flash it from the Stock Recovery i get this error (see the attachment) i also attach the software informations, (looking at the error i receive it may see the archive is corrupted, but i've tried to download it from Asus many and many times)
Click to expand...
Click to collapse
You should try to flash stock recovery of WW in fastboot.
And then flash 6.0 WW rom by WW recovery.
Even though ,I didn't sure that if it will work(because I don't have Z016S),but you can try it.
samson1357924 said:
You should try to flash stock recovery of WW in fast boot.
And then flash 6.0 WW rom by WW recovery.
Even though ,I didn't sure that if it will work(because I don't have Z016S),but you can try it.
Click to expand...
Click to collapse
Ok thanks, i can give a try, but where i can download the WW stock recovery? There is no recovery.img inside the WW_user.zip ROM
LeGrim said:
Ok thanks, i can give a try, but where i can download the WW stock recovery? There is no recovery.img inside the WW_user.zip ROM
Click to expand...
Click to collapse
Here it comes~
ZenFone 3 Deluxe ZS570KL_WW stock recovery
Ok guys, i think i've found a way to debrand my Zenfon 3 Deluxe, im testint the procedure right now, i will post the whole procedure if i succeed
Install : ADB & Minimal Fastboot.
Install : pyton 3.6 https://www.python.org/downloads/
Download the latest WW-4.12.40.1698 (For 2.15GHz CPU or 2.40GHz CPU) from Asus WebSite.
Download "Dat to img by stupdroid.com" (search it with google).
Extract Dat to img by stupdroid.com in a Folder.
Open the Firmware ZIP and copy system.new.dat, system.transfer.list e file_contexts in the Dat2IMG's folder.
Execute system.new.dat 2 flashable img converter.exe and just press ENTER and wait till the end of procedure, you will receive 2 files : system.raw.img e system.new.img.
Copy system.new.img in your Fastboot's folder.
Put the Phone into Fastboot mode.
Open fastboot and put this command: " fastboot flash system system_new.img "
Wait the end of flash procedure and type : Fastboot Reboot.
Enter recovery wipe data and cache.
Done.
LeGrim said:
Install : ADB & Minimal Fastboot.
Install : pyton 3.6 https://www.python.org/downloads/
Download the latest WW-4.12.40.1698 (For 2.15GHz CPU or 2.40GHz CPU) from Asus WebSite.
Download "Dat to img by stupdroid.com" (search it with google).
Extract Dat to img by stupdroid.com in a Folder.
Open the Firmware ZIP and copy system.new.dat, system.transfer.list e file_contexts in the Dat2IMG's folder.
Execute system.new.dat 2 flashable img converter.exe and just press ENTER and wait till the end of procedure, you will receive 2 files : system.raw.img e system.new.img.
Copy system.new.img in your Fastboot's folder.
Put the Phone into Fastboot mode.
Open fastboot and put this command: " fastboot flash system system_new.img "
Wait the end of flash procedure and type : Fastboot Reboot.
Enter recovery wipe data and cache.
Done.
Click to expand...
Click to collapse
I forgot to say, after this procedure, just flash the stock WW recovery via Fastboot, then download from asus the lastest 7.0 firmware SKU WW, all perfect. tested by me.
Ok I already have system.new.img, I copied it to the root folder of the SD. Device restart in Fastboot mode (power + vol.up key). Exit screen with message Fastboot mode and does nothing.
Install in the computer the pyton 3.6, I suppose that it serves for the process of generating system.new.img.
I do not know how to do the first step "Install: ADB & Minimal Fastboot.".
Thank you and forgive my translator
If i want to unlock the bootloader for root and unbrand this phone what i have to do? I need unbranded nougat with root but the phone is TIM branded
Ryder. said:
If i want to unlock the bootloader for root and unbrand this phone what i have to do? I need unbranded nougat with root but the phone is TIM branded
Click to expand...
Click to collapse
What version is your phone right now??
Now only have official unluck
For 2.15GHz:8996(None-PRO) UnlockTool
For 2.4GHz:8996P(PRO) UnlockTool
If you are WW version right now,try these tools.
samson1357924 said:
What version is your phone right now??
Now only have official unluck
For 2.15GHz:8996(None-PRO) UnlockTool
For 2.4GHz:8996P(PRO) UnlockTool
If you are WW version right now,try these tools.
Click to expand...
Click to collapse
It's not WW. I'ts from italy and it's tim branded
Ryder. said:
If i want to unlock the bootloader for root and unbrand this phone what i have to do? I need unbranded nougat with root but the phone is TIM branded
Click to expand...
Click to collapse
Try this
or try flash ZenFone 3 Deluxe ZS570KL_WW stock recovery of 4.12.40.1698 and flash UL-Z016-WW-4.12.40.1698-user.zip in recovery (by micro sd or adb sideload)not sure if it work(need verification,I wish you to try first).
Please help me, my model is the Z016S
I can convert UL-Z016-WW-4.12.40.1698-user.zip img and flash with fastboot.
Reboot and it works, but I do not know how to get into recovery.
I have also installed the Z016-WW-4.11.40.1085_recovery.img. The TIM DISAPPEARED
Then I copied the UL-Z016-WW-5.14.44.1898-user.zip into the internal memory and it does not install well.
I have proven the same with UL-Z016-WW-5.14.44.1898-user.zip and it does not work me it stays in a non-comands and will not boot.
greetings and thanks
P.S. At least you do not see the TIM anywhere.
barbapapa said:
Please help me, my model is the Z016S
I can convert UL-Z016-WW-4.12.40.1698-user.zip img and flash with fastboot.
Reboot and it works, but I do not know how to get into recovery.
I have also installed the Z016-WW-4.11.40.1085_recovery.img. The TIM DISAPPEARED
Then I copied the UL-Z016-WW-5.14.44.1898-user.zip into the internal memory and it does not install well.
I have proven the same with UL-Z016-WW-5.14.44.1898-user.zip and it does not work me it stays in a non-comands and will not boot.
greetings and thanks
P.S. At least you do not see the TIM anywhere.
Click to expand...
Click to collapse
So,what is your system version right now?4.12.40.1698?
Why not flash the recovery of 4.12.40.1698?
samson1357924 said:
So,what is your system version right now?4.12.40.1698?
Why not flash the recovery of 4.12.40.1698?
Click to expand...
Click to collapse
This is my situation
samson1357924 said:
So,what is your system version right now?4.12.40.1698?
Why not flash the recovery of 4.12.40.1698?
Click to expand...
Click to collapse
I have done this and it installs,
fastboot flash recovery Z016-WW-4.12.40.1698_recovery.img
reboot, boot system, detect update file is installed, reboot and then gives error (3) unknown.
barbapapa said:
I have done this and it installs,
fastboot flash recovery Z016-WW-4.12.40.1698_recovery.img
reboot, boot system, detect update file is installed, reboot and then gives error (3) unknown.
Click to expand...
Click to collapse
Tow solution you can try
1.install the rom of 4.12.40.1698 again(some of tile,such as xbl,devcfg,devcfgbak..... may be still TIM versio.install it in recovery may turn it into WW version)
2.If fail, try flash these files in fastboot.(I will upload these files for you to flash,also you can draw by yourself)
Ok already worked, the solution is to unlock as you put in # 11.
Thank you
barbapapa said:
Ok already worked, the solution is to unlock as you put in # 11.
Thank you
Click to expand...
Click to collapse
Good!
Can you share what step did you do? Which might help another TIM user.

ERROR MODE Attention! Please update system again.

Hi
I have a problem with my Honor 7X L21.
Because online update dose not work for this model I decided to updated my smartphone offline.
I downloaded Oreo update file
Unlock my phone
install twrp
update phone
every thing is going well until here
then I decided to root my phone but I saw there is no twrp on my phone
I search and I found a thread here that show how install twrp with adb use recovery ramdisk.
I install twrp on recovery ramdisk and try to root my phone. its OK but when my phone want to start its stuck on google page "just a sec..."
I boot my device on twrp and I did factory reset but the problem was still exist.
then I decided to flash update again.
I copy update file on SD card and wright code on twrp
but at the end when I reboot the recovery, twrp except stock recovery came up and my stock recovery was gone.
I reboot the system but Its loop on this page that says:
ERROR MODE
Attention!
Please update system again.
Error!
Func NO : 11 (recovery image)
Error NO : 2 (load failed!)
Please help me!!!
I try to install stock recovery and twrp with adb and huawei multi tools but it didn't work.
it shows:
"FAILED (remote: partition length get error)"
I try to unbrick my phone too but it shows same message that "FAILED (remote: partition length get error)"
Helllllp lpeaeaeaeaeaseeee!!!
Mohammadreza76646 said:
Hi
I have a problem with my Honor 7X L21.
Because online update dose not work for this model I decided to updated my smartphone offline.
I downloaded Oreo update file
Unlock my phone
install twrp
update phone
every thing is going well until here
then I decided to root my phone but I saw there is no twrp on my phone
I search and I found a thread here that show how install twrp with adb use recovery ramdisk.
I install twrp on recovery ramdisk and try to root my phone. its OK but when my phone want to start its stuck on google page "just a sec..."
I boot my device on twrp and I did factory reset but the problem was still exist.
then I decided to flash update again.
I copy update file on SD card and wright code on twrp
but at the end when I reboot the recovery, twrp except stock recovery came up and my stock recovery was gone.
I reboot the system but Its loop on this page that says:
ERROR MODE
Attention!
Please update system again.
Error!
Func NO : 11 (recovery image)
Error NO : 2 (load failed!)
Please help me!!!
I try to install stock recovery and twrp with adb and huawei multi tools but it didn't work.
it shows:
"FAILED (remote: partition length get error)"
I try to unbrick my phone too but it shows same message that "FAILED (remote: partition length get error)"
Helllllp lpeaeaeaeaeaseeee!!!
Click to expand...
Click to collapse
Doing the update second time is fine, and best way to restore full stock. But you needed to use Oreo version of no-check recovery and the Oreo partition to flash it to.
So if still able to get into twrp, can try with correct no-check recovery and correct partition it's flashed to.
Also
With multi tool , make sure you put check mark on emui 8. Up in upper right corner. That way it uses Oreo partition names and file not nougat.
The partition length over message usually means nougat file or partition name used on Oreo system
mrmazak said:
Doing the update second time is fine, and best way to restore full stock. But you needed to use Oreo version of no-check recovery and the Oreo partition to flash it to.
So if still able to get into twrp, can try with correct no-check recovery and correct partition it's flashed to.
Also
With multi tool , make sure you put check mark on emui 8. Up in upper right corner. That way it uses Oreo partition names and file not nougat.
The partition length over message usually means nougat file or partition name used on Oreo system
Click to expand...
Click to collapse
Thank you for your answer.
But I try to extract update.app (oreo version) but its failed! huawei update extractor cant open it and 7zip cant extract it with (unexpected error...)!
And unfortunately my TWRP dos not work anymore
Mohammadreza76646 said:
Thank you for your answer.
But I try to extract update.app (oreo version) but its failed! huawei update extractor cant open it and 7zip cant extract it with (unexpected error...)!
And unfortunately my TWRP dos not work anymore
Click to expand...
Click to collapse
I give my phone to a friend to work on it. If he can't fix it I try new multi tools version to flash phone.
Mohammadreza76646 said:
Thank you for your answer.
But I try to extract update.app (oreo version) but its failed! huawei update extractor cant open it and 7zip cant extract it with (unexpected error...)!
And unfortunately my TWRP dos not work anymore
Click to expand...
Click to collapse
On the extractor app. On options tab uncheck the verify header option, it should extract then.
Then perhaps first do these three partitions.
Kernel.img
Ramdisk.img
Then
twrp_ramdisk or for stock use recovery_ramdisk
Mohammadreza76646 said:
Hi
I have a problem with my Honor 7X L21.
Because online update dose not work for this model I decided to updated my smartphone offline.
I downloaded Oreo update file
Unlock my phone
install twrp
update phone
every thing is going well until here
then I decided to root my phone but I saw there is no twrp on my phone
I search and I found a thread here that show how install twrp with adb use recovery ramdisk.
I install twrp on recovery ramdisk and try to root my phone. its OK but when my phone want to start its stuck on google page "just a sec..."
I boot my device on twrp and I did factory reset but the problem was still exist.
then I decided to flash update again.
I copy update file on SD card and wright code on twrp
but at the end when I reboot the recovery, twrp except stock recovery came up and my stock recovery was gone.
I reboot the system but Its loop on this page that says:
ERROR MODE
Attention!
Please update system again.
Error!
Func NO : 11 (recovery image)
Error NO : 2 (load failed!)
Please help me!!!
I try to install stock recovery and twrp with adb and huawei multi tools but it didn't work.
it shows:
"FAILED (remote: partition length get error)"
I try to unbrick my phone too but it shows same message that "FAILED (remote: partition length get error)"
Helllllp lpeaeaeaeaeaseeee!!!
Click to expand...
Click to collapse
I ever have similiar problem with you dude, but it's solved now, if you always stuck on " its OK but when my phone want to start its stuck on google page "just a sec...", its call google accont verification, i'll by bypass with this script, save as to .bat and put on adb folder
adb devices
adb shell content insert --uri content://settings/secure --bind name:s:user_setup_complete --bind value:s:1
adb shell am start -n com.google.android.gsf.login/
adb shell am start -n com.google.android.gsf.login.LoginActivity
pause
in fastboot type:
fastboot -w
after all it's works to me to bypass google account verification
and if now your problem is
ERROR MODE
Attention!
Please update system again.
Error!
Func NO : 11 (recovery image)
Error NO : 2 (load failed!)
i solve with re-flash system from this
https://androidfilehost.com/?fid=673956719939830152
fastboot flash system system.img
and doing TWRP Flashing
https://forum.xda-developers.com/devdb/project/?id=25826#downloads
fastboot flash recovery_ramdisk complete_twrp_ramdisk.img
and voila my problem solved..
mrmazak said:
On the extractor app. On options tab uncheck the verify header option, it should extract then.
Then perhaps first do these three partitions.
Kernel.img
Ramdisk.img
Then
twrp_ramdisk or for stock use recovery_ramdisk
Click to expand...
Click to collapse
Hello again dude.
Finally I flashed my phone and I got the system installed.
But now my phones IMEI is lost. and I cant put sim on it!!!
what should I do now???
FRP is locked! (
Mohammadreza76646 said:
Hello again dude.
Finally I flashed my phone and I got the system installed.
But now my phones IMEI is lost. and I cant put sim on it!!!
what should I do now???
FRP is locked! (
Click to expand...
Click to collapse
So now is locked frp. Does phone have twrp or stock now.?
I think when you tried to install the oreo update for second time, you followed same tutorial as the first time. And that made you problem worse. The tutorial has you flash no-check recovery to 2 partition by block number. 22 & 29. On nougat that is "recovery" and "recovery2". On Oreo partion table it is "reserved2" & "erecovery_vendor"
I don't know how to fix imei. Have hope that if to ucan have a full ota install , maybe can be fixed.
There is available a "service rom" (used to fix most all problem) for Europe region with l21.
I can share link to site with service rom if you want , but I have not used it myself so not gonna be much help with it.
Link is to rusian language page. Google should translate for you.
https://4pda.ru/forum/index.php?showtopic=879524&view=findpost&p=73818595
mrmazak said:
So now is locked frp. Does phone have twrp or stock now.?
I think when you tried to install the oreo update for second time, you followed same tutorial as the first time. And that made you problem worse. The tutorial has you flash no-check recovery to 2 partition by block number. 22 & 29. On nougat that is "recovery" and "recovery2". On Oreo partion table it is "reserved2" & "erecovery_vendor"
I don't know how to fix imei. Have hope that if to ucan have a full ota install , maybe can be fixed.
There is available a "service rom" (used to fix most all problem) for Europe region with l21.
I can share link to site with service rom if you want , but I have not used it myself so not gonna be much help with it.
Link is to rusian language page. Google should translate for you.
https://4pda.ru/forum/index.php?showtopic=879524&view=findpost&p=73818595
Click to expand...
Click to collapse
It have stock recovery.
Mohammadreza76646 said:
It have stock recovery.
Click to expand...
Click to collapse
in summery. because i have been going back and forth in multiple different groups, multiple problem, i cant remember it all.
you have broken system, from failed root attempt, followed by failed update.
device condition is as follows.
--system not booting
--stock recovery loads
--fastboot/bootloader loads, but is in frp lock status
options are limited, at best.
I think "dload" method with service rom is best.
other option is maybe paid service like dc-unlock. But I can recall some note on there service about frp-unlock, that can only be used on device with working system. (of course if was working system, wouldn't need dc-unlock)
mrmazak said:
in summery. because i have been going back and forth in multiple different groups, multiple problem, i cant remember it all.
you have broken system, from failed root attempt, followed by failed update.
device condition is as follows.
--system not booting
--stock recovery loads
--fastboot/bootloader loads, but is in frp lock status
options are limited, at best.
I think "dload" method with service rom is best.
other option is maybe paid service like dc-unlock. But I can recall some note on there service about frp-unlock, that can only be used on device with working system. (of course if was working system, wouldn't need dc-unlock)
Click to expand...
Click to collapse
No. System boot successfully!
I will send you screenshot:
Mohammadreza76646 said:
No. System boot successfully!
I will send you screenshot:
Click to expand...
Click to collapse
here you are
Mohammadreza76646 said:
here you are
Click to expand...
Click to collapse
what about the "about phone" screen
what does it show for version?
If is all stock you should be able to go into deveolper options and enable "oem unlock". If it is greyed out and cannot switch it. Try First to remove google account (all accounts ). and reboot. See if can change then. If not, try Second to do "fastboot oem relock [enter your bootloader code here]
after relock and rebooted oem switch should be enabled again.
****RELOCK IS ONLY ADVISED IF 100% STOCK ROM****
otherwise relock could make more trouble.
Still not sure how to get IMEI back even if unlocked frp though.
**And please stop posting in other threads , the same problem , because you are getting help here.
your post in recovery thread is off topic to that thread and just makes the forum harder to maintain.
mrmazak said:
what about the "about phone" screen
what does it show for version?
If is all stock you should be able to go into deveolper options and enable "oem unlock". If it is greyed out and cannot switch it. Try First to remove google account (all accounts ). and reboot. See if can change then. If not, try Second to do "fastboot oem relock [enter your bootloader code here]
after relock and rebooted oem switch should be enabled again.
****RELOCK IS ONLY ADVISED IF 100% STOCK ROM****
otherwise relock could make more trouble.
Still not sure how to get IMEI back even if unlocked frp though.
**And please stop posting in other threads , the same problem , because you are getting help here.
your post in recovery thread is off topic to that thread and just makes the forum harder to maintain.
Click to expand...
Click to collapse
Thanks )
I'm so sorry for my posts, it's because I don't have a stable connection and I can't see notification of my thread.
I gave my phone to friend an he fix IMEI (I don't know how)
But OEM is steel lock.
I think he did it with using special box.
Mohammadreza76646 said:
Hi
I have a problem with my Honor 7X L21.
Because online update dose not work for this model I decided to updated my smartphone offline.
I downloaded Oreo update file
Unlock my phone
install twrp
update phone
every thing is going well until here
then I decided to root my phone but I saw there is no twrp on my phone
I search and I found a thread here that show how install twrp with adb use recovery ramdisk.
I install twrp on recovery ramdisk and try to root my phone. its OK but when my phone want to start its stuck on google page "just a sec..."
I boot my device on twrp and I did factory reset but the problem was still exist.
then I decided to flash update again.
I copy update file on SD card and wright code on twrp
but at the end when I reboot the recovery, twrp except stock recovery came up and my stock recovery was gone.
I reboot the system but Its loop on this page that says:
ERROR MODE
Attention!
Please update system again.
Error!
Func NO : 11 (recovery image)
Error NO : 2 (load failed!)
Please help me!!!
I try to install stock recovery and twrp with adb and huawei multi tools but it didn't work.
it shows:
"FAILED (remote: partition length get error)"
I try to unbrick my phone too but it shows same message that "FAILED (remote: partition length get error)"
Helllllp lpeaeaeaeaeaseeee!!![/QUOTE
Are u able.to boot into twrp ?
Click to expand...
Click to collapse
Hello I have a Huawei Mate-SE (with bootloader unlocked and rooted with magisk v16). I have been using the android custom rom RRO v6 (RR-O-v6.0.0-20180401-bnd-OpenKirin) for around a month now. I got this exact same problem about the White Screen saying "ERROR MODE Attention...." since I updated the Magisk to latest version (from the installed application) and rebooted my phone. SInce I rebooted I am getting that same error which makes the phone loops into it for a few times and then it loads the Huawei eRecovery that offers me some options that I am not sure what would do to my phone.
I have been trying to connect to adb tools/fastboot but it doesn't detect the phone and im pretty sure I have the device drivers installed on my computer since nothing have changed in my pc for a month now since I flashed RRO on it.
Is there any other mode besides recovery that would allow me to connect adb/fastboot to it? Or does anyone knows how should I proceed?
IonDEfeso said:
Hello I have a Huawei Mate-SE (with bootloader unlocked and rooted with magisk v16). I have been using the android custom rom RRO v6 (RR-O-v6.0.0-20180401-bnd-OpenKirin) for around a month now. I got this exact same problem about the White Screen saying "ERROR MODE Attention...." since I updated the Magisk to latest version (from the installed application) and rebooted my phone. SInce I rebooted I am getting that same error which makes the phone loops into it for a few times and then it loads the Huawei eRecovery that offers me some options that I am not sure what would do to my phone.
I have been trying to connect to adb tools/fastboot but it doesn't detect the phone and im pretty sure I have the device drivers installed on my computer since nothing have changed in my pc for a month now since I flashed RRO on it.
Is there any other mode besides recovery that would allow me to connect adb/fastboot to it? Or does anyone knows how should I proceed?
Click to expand...
Click to collapse
I have seen where the magisk update screwed up and patches the kernel intead of the ramdisk.
Power off , long press power button.
Hold volume down and plug in USB from PC.
This should cause it to boot into fastboot mode.
Then flash the stock kernel. And the stock or first patched ramdisk. (From earlier root)
mrmazak said:
I have seen where the magisk update screwed up and patches the kernel intead of the ramdisk.
Power off , long press power button.
Hold volume down and plug in USB from PC.
This should cause it to boot into fastboot mode.
Then flash the stock kernel. And the stock or first patched ramdisk. (From earlier root)
Click to expand...
Click to collapse
Hi thank you I was able to finally detect the device now. I am unsure about the kernel is that the recovery.img or system.img files I downloaded (i saved every file i used when I installed the rom) or do I need to look for the kernel somewhere else? I do have the complete_twrp_ramdisk.img file though.
Edit, I did more research and found the stock kernel is withing the boot.img file which I dont have so I looked up for the official BND-L34 oreo update and im currently downloading to extract the stock boot.img from the update.zip and flash it. Since that download was going to take me a while anyway i tried flashing the twrp recovery file without success (didn't changed anything) so i guess I should follow the instructions you gave me by flashing the kernel first then the twrp recovery.
mrmazak said:
I have seen where the magisk update screwed up and patches the kernel intead of the ramdisk.
Power off , long press power button.
Hold volume down and plug in USB from PC.
This should cause it to boot into fastboot mode.
Then flash the stock kernel. And the stock or first patched ramdisk. (From earlier root)
Click to expand...
Click to collapse
Do you know what the boot.img files name is after extraction?
I have extracted all 3 update zips and cannot find anything called boot.img
By the way, thank you.. After updating magisk I have been dealing with failed recovery and failed boot for over a week and this is the first reply anywhere that looks promising
IonDEfeso said:
Hi thank you I was able to finally detect the device now. I am unsure about the kernel is that the recovery.img or system.img files I downloaded (i saved every file i used when I installed the rom) or do I need to look for the kernel somewhere else? I do have the complete_twrp_ramdisk.img file though.
Edit, I did more research and found the stock kernel is withing the boot.img file which I dont have so I looked up for the official BND-L34 oreo update and im currently downloading to extract the stock boot.img from the update.zip and flash it. Since that download was going to take me a while anyway i tried flashing the twrp recovery file without success (didn't changed anything) so i guess I should follow the instructions you gave me by flashing the kernel first then the twrp recovery.
Click to expand...
Click to collapse
if you were on oreo. then there is not a boot.img, instaed there is seperate ramdisk.img and kernel.img.
i have all the files already extracted for oreo and a backup from nougat as well.
https://androidfilehost.com/?w=files&flid=265998
make sure you know what you are doing before flashing.
for example. on oreo the boot and recovery share one kernel image. SO if kernel is messed up you will not be able to boot "boot" or "recovery"

TWRP 3.3.1 & Root for Moto 1 Vision

TWRP 3.3.1 & Root for Moto 1 Vision​Thanks 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.

Categories

Resources