Database Users

Lemfo lem5 custom recovery - twrp

Was able to port twrp recovery of blitz smartwatch after unpacking and replacing the kernel file with the lemfo lem5's stock kernel file extracted from unpacking stock recovery of lemfo lem5 and then repacking and flashing it to lemfo lem5. The recovery got successfully installed and all features are working except the recovery screen is flipped / inverted but not the touch response. The touch inputs are the same as non inverted screen and using the touch is pain in the a**s. If the touch input field is at 45 degrees then to access it, need to tap at 225 degrees and on the same radius distance. Can anyone let me know how to flip the recovery screen without affecting the touch fields or is there a similar custom recovery for mtk6580 lollipop smartwatch with flipped screen.

I have not found solution
Same problem with kw88h
And all twrp apk from playstore does not recognize as twrp
Recovery
Flashify can make the job
Only commands from adb... for wipe.
There is not enough space to backup or restore and i think only root and flasify is all you need.

geowolf1000 said:
I have not found solution
Same problem with kw88h
And all twrp apk from playstore does not recognize as twrp
Recovery
Flashify can make the job
Only commands from adb... For wipe
There is not enough space to backup or restore and i think only root is all you need
Click to expand...
Click to collapse
I have got everything working in twrp recovery. The flip recovery is no more a problem now as with some practice now I am comfortably able to use this inverted twrp touch with ease. It works like a charm and just like the official twrp recovery. No problems at all. Now everything is set : bootloader unlocked, rooted with latest binary supersu, custom twrp recovery installed. I also have the stock recovery img backup file, hence can switch back and forth between stock and custom recovery whenever required. No space issue on lemfo lem5 as it has 8gb rom. lastly only xposed installer is to be installed which is not much of a problem as they are available for lollipop with supported sdk and for which as of now I don't see the use of xposed installer right now, hence will install when required. If I am able to somehow flip the recovery screen then that's it! ?

Gautam_Gundap said:
I have got everything working in twrp recovery. The flip recovery is no more a problem now as with some practice now I am comfortably able to use this inverted twrp touch with ease. It works like a charm and just like the official twrp recovery. No problems at all. Now everything is set : bootloader unlocked, rooted with latest binary supersu, custom twrp recovery installed. I also have the stock recovery img backup file, hence can switch back and forth between stock and custom recovery whenever required. No space issue on lemfo lem5 as it has 8gb rom. lastly only xposed installer is to be installed which is not much of a problem as they are available for lollipop with supported sdk and for which as of now I don't see the use of xposed installer right now, hence will install when required. If I am able to somehow flip the recovery screen then that's it! ?
Click to expand...
Click to collapse
If your rom size is not sufficient enough for backup then you can create full rom backup on pc and can restore the same from pc when the need arises. There are software packages available for the same
geowolf1000 said:
I have not found solution
Same problem with kw88h
And all twrp apk from playstore does not recognize as twrp
Recovery
Flashify can make the job
Only commands from adb... for wipe.
There is not enough space to backup or restore and i think only root and flasify is all you need.
Click to expand...
Click to collapse

Gautam_Gundap said:
If your rom size is not sufficient enough for backup then you can create full rom backup on pc and can restore the same from pc when the need arises. There are software packages available for the same
Click to expand...
Click to collapse
I have with chainfire but never had any problem to recover
Thanks

Gautam_Gundap, fantastic work - You've beaten me to the punch as I had been messing with this device since yesterday (already fixed two bootloops I had induced myself -_- ) and I've been looking for a method for porting a TWRP img that wouldn't brick the LEM5.
Would you mind sharing the port? ..Despite the mirrored display/input issues you have so far, having any recovery method right now is very appealing to me considering the hell I had luckily sidestepped, and want to dig further into their stock images: if only to rebuild them with better icons for starters....
If not, can you just run me through your steps for full-backup, and your modification of TWRP for use with LEM5? I don't mind doing the legwork but would rather not walk this firepath alone!
(After 4 years, finally signed up and posted. Feels good to be here, guys! )

cassettesgoboom said:
Gautam_Gundap, fantastic work - You've beaten me to the punch as I had been messing with this device since yesterday (already fixed two bootloops I had induced myself -_- ) and I've been looking for a method for porting a TWRP img that wouldn't brick the LEM5.
Would you mind sharing the port? ..Despite the mirrored display/input issues you have so far, having any recovery method right now is very appealing to me considering the hell I had luckily sidestepped, and want to dig further into their stock images: if only to rebuild them with better icons for starters....
If not, can you just run me through your steps for full-backup, and your modification of TWRP for use with LEM5? I don't mind doing the legwork but would rather not walk this firepath alone!
(After 4 years, finally signed up and posted. Feels good to be here, guys! )
Click to expand...
Click to collapse
There are many advantages of twrp custom recovery, one of them being very fast full rom backup and even faster full rom restore and that too with compression, the pc whereas takes at least 10 times the time to do the same. full rom restore for me does it within 4mins and backup size of full compressed rom is only 1.64GB whereas the pc takes 7GB for the same backup. Needless to say about advantages of other features like customized wipe, flash image and zip files etc. Now for the procedure for porting twrp custom recovery is as follows
Download latest version of mtk extractor for PC. I tried all other methods, but only this one worked for me.
Download custom twrp recovery of blitz or i2 smartwatch which you will find in this forum.
You will require your stock recovery image file for this method. Your watch needs to be rooted to extract the same. Flashify app from playstore will do the job.
Connect watch to pc. Hope you know how to do this. rename stock recovery img to boot. Open mtk extractor and unpack this renamed file. You will find the unpacked files in mtk folder.
Cut these files and paste in a new folder stock recovery.
now rename the custom twrp recovery img you are going to port to boot.
Unpack it, the files will be placed in mtk folder.
Now copy kernel file from the stock recovery folder and paste it in the new unpacked files of ported twrp. PC Prompts replace - yes.
Now repack and you will get boot.img. Rename to recovery.img.
Flash this via fastboot or Flashify. Done. You have now successfully installed twrp recovery.
Note: In the mtk extractor software use the boot feature for all above steps.
If you encounter any problems post here and I will fix it.

To use pc for full rom backup and restore and many other features use cracked version of miracle box v2. 27A. Mtk Droid tools and SP flash tools do not support this watch, so don't waste time trying with it.

Xposed framework installed successfully!

Anyone need full power button menu for lemfo lem5 install advance power menu app from playstore. It works well. Once you long press the power button you get options for power off, reboot, download, recovery, UI restart , screen shot, soft reboot and safe mode reboot. Select floating mode from settings. looks and works nice on smart watch display

Gautam_Gundap said:
There are many advantages of twrp custom recovery, one of them being very fast full rom backup and even faster full rom restore and that too with compression, the pc whereas takes at least 10 times the time to do the same. full rom restore for me does it within 4mins and backup size of full compressed rom is only 1.64GB whereas the pc takes 7GB for the same backup. Needless to say about advantages of other features like customized wipe, flash image and zip files etc. Now for the procedure for porting twrp custom recovery is as follows
Download latest version of mtk extractor for PC. I tried all other methods, but only this one worked for me.
Download custom twrp recovery of blitz or i2 smartwatch which you will find in this forum.
You will require your stock recovery image file for this method. Your watch needs to be rooted to extract the same. Flashify app from playstore will do the job.
Connect watch to pc. Hope you know how to do this. rename stock recovery img to boot. Open mtk extractor and unpack this renamed file. You will find the unpacked files in mtk folder.
Cut these files and paste in a new folder stock recovery.
now rename the custom twrp recovery img you are going to port to boot.
Unpack it, the files will be placed in mtk folder.
Now copy kernel file from the stock recovery folder and paste it in the new unpacked files of ported twrp. PC Prompts replace - yes.
Now repack and you will get boot.img. Rename to recovery.img.
Flash this via fastboot or Flashify. Done. You have now successfully installed twrp recovery.
Note: In the mtk extractor software use the boot feature for all above steps.
If you encounter any problems post here and I will fix it.
Click to expand...
Click to collapse
Very cool - seems straightforward enough. I'll see if I can find something to fix up or workaround to get the rotation back while I'm at it. First thing's first is to give this a shot though. Need to get a windows machine so I'll get it going at work tomorrow!
Will update again soon. Thanks so much for the steps!

Hi guys.. root + twrp ok.. but there are Custom ROM with full smartwatch function (not only standalone)? Or the only one solution (partial solution) is M2D?

Well done! :laugh: I've configured Lem5 TWRP how u can see here:
https://forum.xda-developers.com/smartwatch/other-smartwatches/twrp-lemfo-lem-5-twrp-t3544569
I think/hope i've solved recovery flipped screen issue, because X5 TWRP haven't this problem.
X5 TWRP + Lem5 kernel = solution? I hope so!
If someone want try, please post the result. Thanx at all...!
Sent from my S7 Edge using XDA Labs

I'm trying to flash the recovery through fastboot and I'm getting:
C:\platform-tools>fastboot flash recovery recovery.img
target reported max download size of 134217728 bytes
sending 'recovery' (9676 KB)...
OKAY [ 0.366s]
writing 'recovery'...
FAILED (remote: download for partition 'recovery' is not allowed
)
finished. total time: 0.383s
I tried rooting with Kingroot and it really bloated up my device. Factory reset still keeps Kingroot, so I kinda want to start over fresh with TWRP and a clean image. How do you flash TWRP on this watch?
---------- Post added at 02:53 PM ---------- Previous post was at 02:39 PM ----------
Update: I made sure OEM unlock was checked in developer settings and eventually was able to flash TWRP via Fastboot.
My watch is now bootlooping over and over again in TWRP, says:
"Done processing script file, renamed stock recovery file in /system to prevent the stock ROM from replacing TWRP."

dimex said:
I'm trying to flash the recovery through fastboot and I'm getting:
C:\platform-tools>fastboot flash recovery recovery.img
target reported max download size of 134217728 bytes
sending 'recovery' (9676 KB)...
OKAY [ 0.366s]
writing 'recovery'...
FAILED (remote: download for partition 'recovery' is not allowed
)
finished. total time: 0.383s
I tried rooting with Kingroot and it really bloated up my device. Factory reset still keeps Kingroot, so I kinda want to start over fresh with TWRP and a clean image. How do you flash TWRP on this watch?
---------- Post added at 02:53 PM ---------- Previous post was at 02:39 PM ----------
Update: I made sure OEM unlock was checked in developer settings and eventually was able to flash TWRP via Fastboot.
My watch is now bootlooping over and over again in TWRP, says:
"Done processing script file, renamed stock recovery file in /system to prevent the stock ROM from replacing TWRP."
Click to expand...
Click to collapse
if your bootloader is locked, it will not allow you to flash twrp recovery via fastboot . Use SP FLASH TOOLS for this purpose. Once you flash recovery do not reboot to system. Reboot to recovery for the first time and then it should be ok. Else root your watch first and flash recovery using Flashify. This method will also do the job.

Gautam_Gundap said:
if your bootloader is locked, it will not allow you to flash twrp recovery. Use SP FLASH TOOLS for this purpose. Once you flash recovery do not reboot to system. Reboot to recovery for the first time and then it should be ok. Else root your watch first and flash recovery using Flashify. This method will also do the job.
Click to expand...
Click to collapse
Did you read my update? It's bootlooping TWRP.

dimex said:
Did you read my update? It's bootlooping TWRP.
Click to expand...
Click to collapse
If you are unable to reboot to system, then you need to re flash complete stock rom. You can do this using cracked miracle software. I have already uploaded full stock rom for flashing via cracked miracle box software except data/userdata partition . you can find it in one of the lemfo lem5 threads here. After re flash you can use the steps explained earlier to flash twrp recovery

I just released a fully working TWRP 3.0.2 recovery for X5+ and LEM5 here:
http://roundandroidwatches.proboards.com/thread/1016/twrp-recovery-port-x5-lem5
Don't forget to read all the instructions.

Updating Asus Zenfone 3 Zoom ZE553KL by TWRP : some errors and difficulties

From the first time i was not able to upgrade my phone to another new version of Android.
The phone was bought on chinese store with Android version : WW V10.40.47.107 (Android MM)
When i checked availability of new versions, phone showed me no result available.
Then following instructions i unlocked bootloader and then install TWRP as recovery system.
I tried to install updates of ROM downloaded from Asus website using this methods with this results :
installing by TWRP with ROM transfered to internal memory of phone KO
installing by "ADB sideload" command KO
I partially resolved after many attempts updating only to Version V11.41.87.2 (Android MM)
I solved in this way :
i used TWRP installing from file transfered directly in microSD
i extracted from zipped file "updater-script" file that is possible to find in the following folder path :
META-INF > com > google > android
and then deleted this rows :
(!less_than_int(1494697617, getprop("ro.build.date.utc"))) || abort("Can't install this package (2017年 05月 14日 星期日 01:46:57 CST) over newer build (" + getprop("ro.build.date") + ").");
.....
getprop("ro.build.asus.sku") == "WW" || abort("Please use the right SKU for updating...");
.....
and then save file extracted and compress into zip file.
During TWRP install process i got some error updates, it seems connected to System folder/partition update
but at the end i was able to update Android to my phone
I tried to do the same method with an other update Version V20.32.67.25 i got a corrupted System folder/partition
It seems essential to update this phone to use original recovery system. Can anyone give it to me?
Or is there someone who has been able to install updates using TWRP without any error ?
Also after installation I wiped the Boot, System, Data, Cache partitions and then I restored from Nandroid backup done by TWRP.
But the phone did not start at the reboot.
I then had to reinstall the update with the method described above to get the working phone back
Why did Nandroid backup with TWRP not correctly restore the phone?
Many thanks to anyone can help me

https://forum.xda-developers.com/showthread.php?p=72448182
There is a link to a rom in this post. In that zip you will find recovery.img. Flash it with adb, like you flashed twrp.
Then you can flash the last M official rom, and subsequently the first and last N roms.
That's the way I did it. I had to end up wiping data, to make it work correctly.
I'm also looking for a Nougat recovery.img.
I wouldn't like to go thru all the process again if there is another update.
Good luck.
Sent from my ASUS_Z01HD using Tapatalk

betche99 said:
https://forum.xda-developers.com/showthread.php?p=72448182
There is a link to a rom in this post. In that zip you will find recovery.img. Flash it with adb, like you flashed twrp.
Then you can flash the last M official rom, and subsequently the first and last N roms.
That's the way I did it. I had to end up wiping data, to make it work correctly.
I'm also looking for a Nougat recovery.img.
I wouldn't like to go thru all the process again if there is another update.
Good luck.
Sent from my ASUS_Z01HD using Tapatalk
Click to expand...
Click to collapse
I already downloaded that file but i didn't find any recovery.img file inside.
I try again
Many thanks :good::good::good:

johnjohnmel said:
I already downloaded that file but i didn't find any recovery.img file inside.
I try again
Many thanks :good::good::good:
Click to expand...
Click to collapse
i think you need flash full firmware bro ,
1. Download newer version firmware
2. You need Convert system.New.DAT to system.img
3. Move system.img and boot.img to minimal adb & fastboot folder
4. Open minimal adb & fastboot
5. Flash boot.img and system.img

halim_wijaya58 said:
2. You need Convert system.New.DAT to system.img
Click to expand...
Click to collapse
Hi Halim
Can I change *.DAT to *.img? or I should convert DAT to IMG with special app.?

Hi all.
I have the same room and can't seem to upgrade to N does anyone have a solution?

halim_wijaya58 said:
i think you need flash full firmware bro ,
1. Download newer version firmware
2. You need Convert system.New.DAT to system.img
3. Move system.img and boot.img to minimal adb & fastboot folder
4. Open minimal adb & fastboot
5. Flash boot.img and system.img
Click to expand...
Click to collapse
Just to let you know I did this then downloaded each update from Asus website. You have to do it in order ie newest MM to oldest N to newest N. Takes a lot of time but it works. I now have N on my phone.
Thanks everyone for all your help.

mikejasonsmith said:
Just to let you know I did this then downloaded each update from Asus website. You have to do it in order ie newest MM to oldest N to newest N. Takes a lot of time but it works. I now have N on my phone.
Thanks everyone for all your help.
Click to expand...
Click to collapse
Boss, I have Asus Zenfone 3 Zoom. I want to update Android nougat. Please help me . Already I unlocked bootloader and convert CN to WW Rom ........
Please help me ....... Please help me....... Please help me
???
---------- Post added at 12:13 PM ---------- Previous post was at 12:10 PM ----------
mikejasonsmith said:
Just to let you know I did this then downloaded each update from Asus website. You have to do it in order ie newest MM to oldest N to newest N. Takes a lot of time but it works. I now have N on my phone.
Thanks everyone for all your help.
Click to expand...
Click to collapse
Boss, I have Asus Zenfone 3 Zoom. I want to update Android nougat. Please help me . Already I unlocked bootloader and convert CN to WW Rom ........
Please help me ....... Please help me....... Please help me
???

Dear boss , please give me Asus Zenfone 3 Zoom Nougat flashable Rom or any easy solutions........
???

After 11 hours trying out finally solved!!!
I originally just wanted to do a factory reset, and swiped then not only data/cache, but unfortunally - because of lack of expirience - also system partition. After that all the problems occured like described above and partitionally in https://forum.xda-developers.com/zenfone-3/help/unbricking-zenfone-3-ze552kl-dm-verity-t3563970 (there was no OS anymore, twrp warned me this every time I wanted to power off, but I couldn't install the firmware again through fastboot neither through twrp -> install zip; have got error 7 or 6).
Afer a lot of fears and hours of trying aroud possibilities above as well as ideas from articles here:
https://forum.xda-developers.com/zenfone-3/help/unbricking-zenfone-3-ze552kl-dm-verity-t3563970
https://www.getdroidtips.com/v20-31-49-2-nougat-asus-zenfone-3-zoom/
https://forum.xda-developers.com/ze...om-ze553kl-t3612990/post72448182#post72448182
https://forums.oneplus.net/threads/twrp-failed-to-mount-system-invalid-argument.508967/
https://android.stackexchange.com/questions/165370/restoring-system-partition-in-twrp
https://4pda.ru/forum/index.php?showtopic=810939&st=240#entry63616813
I have finally founded a solution!!! This is in FIRSTLY restoring original recovery and just then flashing the stock ROM. Here the steps to do for it:
a.) Download original stock rom (raw-version!) from https://cloud.mail.ru/public/HuMJ/wEybSNsQA (raw is to flash through AFT - asus flash tool) or from any other source you can find online; official name seems to be "WW-ZE553KL-20.31.49.2-MR2-user-20170620235128-release_raw.zip"
b.) Exctract and move recovery.img to your adb-folder on PC
c.) Boot your phone into fastboot/boot mode, connect to PC through USB-Cable
d.) Run cmd in adb folder, then type in the command "fastboot flash recovery recovery.img"
e.) Reboot and choose recovery mode - now you have no twrp anymore, but the original recovery menue
f.) Install update, which means, original stock from your sd-card.
Be happy!
It would be nice if you could give me feedback, whether my solution was helpful for you, because it took time to write it and hope it will usefull

figulus said:
I originally just wanted to do a factory reset, and swiped then not only data/cache, but unfortunally - because of lack of expirience - also system partition. After that all the problems occured like described above and partitionally in https://forum.xda-developers.com/zenfone-3/help/unbricking-zenfone-3-ze552kl-dm-verity-t3563970 (there was no OS anymore, twrp warned me this every time I wanted to power off, but I couldn't install the firmware again through fastboot neither through twrp -> install zip; have got error 7 or 6).
Afer a lot of fears and hours of trying aroud possibilities above as well as ideas from articles here:
https://forum.xda-developers.com/zenfone-3/help/unbricking-zenfone-3-ze552kl-dm-verity-t3563970
https://www.getdroidtips.com/v20-31-49-2-nougat-asus-zenfone-3-zoom/
https://forum.xda-developers.com/ze...om-ze553kl-t3612990/post72448182#post72448182
https://forums.oneplus.net/threads/twrp-failed-to-mount-system-invalid-argument.508967/
https://android.stackexchange.com/questions/165370/restoring-system-partition-in-twrp
https://4pda.ru/forum/index.php?showtopic=810939&st=240#entry63616813
I have finally founded a solution!!! This is in FIRSTLY restoring original recovery and just then flashing the stock ROM. Here the steps to do for it:
a.) Download original stock rom (raw-version!) from https://cloud.mail.ru/public/HuMJ/wEybSNsQA (raw is to flash through AFT - asus flash tool) or from any other source you can find online; official name seems to be "WW-ZE553KL-20.31.49.2-MR2-user-20170620235128-release_raw.zip"
b.) Exctract and move recovery.img to your adb-folder on PC
c.) Boot your phone into fastboot/boot mode, connect to PC through USB-Cable
d.) Run cmd in adb folder, then type in the command "fastboot flash recovery recovery.img"
e.) Reboot and choose recovery mode - now you have no twrp anymore, but the original recovery menue
f.) Install update, which means, original stock from your sd-card.
Be happy!
It would be nice if you could give me feedback, whether my solution was helpful for you, because it took time to write it and hope it will usefull
Click to expand...
Click to collapse
Boss,
This solutions can work with ASUS ZENFONE 3 ZOOM.........???
I have ZenFone 3 zoom. Already I successfully convert CN to WW Rom by following this introduction ... https://forum.xda-developers.com/zenfone-3-zoom/how-to/transfer-cn-rom-to-ww-rom-ze553kl-t3612990
But, I can't update android nougat any way. I convert system.new.dat to system.img...... And try to flash it but unfortunately that's not working......
Please help me .......:crying:

Yes, I did it with my Zenfone 3 Zoom (ze553kl). So, you have firstly to flash the original recovery - to find, as described, in the raw stock rom zip archive. Or, you can find all original recovery's also here: (not tested by myself) https://mega.nz/#F!p90wgAaY!l1JbJilmAUEKTKWu43pT9w
Copy recovery.img to adb-folder, then flash it in fastboot mode in the cmd with "fastboot flash recovery recovery.img". Also copy the original stock rom with Android N to your sd-card and put it into your phone.
Then reboot your phone into recovery - now you have no twrp anymore, but original recovery. Install now the zip with Android-N-stock-firmware from sd-card. Enjoy!

figulus said:
Yes, I did it with my Zenfone 3 Zoom (ze553kl). So, you have firstly to flash the original recovery - to find, as described, in the raw stock rom zip archive. Or, you can find all original recovery's also here: (not tested by myself) https://mega.nz/#F!p90wgAaY!l1JbJilmAUEKTKWu43pT9w
Copy recovery.img to adb-folder, then flash it in fastboot mode in the cmd with "fastboot flash recovery recovery.img". Also copy the original stock rom with Android N to your sd-card and put it into your phone.
Then reboot your phone into recovery - now you have no twrp anymore, but original recovery. Install now the zip with Android-N-stock-firmware from sd-card. Enjoy!
Click to expand...
Click to collapse
Boss ,
Thank you very much ...... Your solution absolutely excellent and work very well . I am very happy for your support . But unfortunately I found new problem on my phone ...... After update nougat a white line found on the display......
How can I solved it .......
Waiting for solution.......
Thanks again for your support ........

Glad to hear, that it worked for you as well. About white line I have no idea, but on other pages I have already seen somewhere, that other users also reported about this problem. Try to look at google "ze553kl update white line". You can also search a solution for ze552kl instead of ze553kl, because, as far as I know, the ze552kl (ZenFone 3, without "Zoom") is almost the same device, just with a little worse cam. Therefore, it seems to be longer on the market and to have more users, so there are also more solutions for problems which can occure to this device in the internet. Wish you a good luck!

figulus said:
I originally just wanted to do a factory reset, and swiped then not only data/cache, but unfortunally - because of lack of expirience - also system partition. After that all the problems occured like described above and partitionally in https://forum.xda-developers.com/zenfone-3/help/unbricking-zenfone-3-ze552kl-dm-verity-t3563970 (there was no OS anymore, twrp warned me this every time I wanted to power off, but I couldn't install the firmware again through fastboot neither through twrp -> install zip; have got error 7 or 6).
Afer a lot of fears and hours of trying aroud possibilities above as well as ideas from articles here:
https://forum.xda-developers.com/zenfone-3/help/unbricking-zenfone-3-ze552kl-dm-verity-t3563970
https://www.getdroidtips.com/v20-31-49-2-nougat-asus-zenfone-3-zoom/
https://forum.xda-developers.com/ze...om-ze553kl-t3612990/post72448182#post72448182
https://forums.oneplus.net/threads/twrp-failed-to-mount-system-invalid-argument.508967/
https://android.stackexchange.com/questions/165370/restoring-system-partition-in-twrp
https://4pda.ru/forum/index.php?showtopic=810939&st=240#entry63616813
I have finally founded a solution!!! This is in FIRSTLY restoring original recovery and just then flashing the stock ROM. Here the steps to do for it:
a.) Download original stock rom (raw-version!) from https://cloud.mail.ru/public/HuMJ/wEybSNsQA (raw is to flash through AFT - asus flash tool) or from any other source you can find online; official name seems to be "WW-ZE553KL-20.31.49.2-MR2-user-20170620235128-release_raw.zip"
b.) Exctract and move recovery.img to your adb-folder on PC
c.) Boot your phone into fastboot/boot mode, connect to PC through USB-Cable
d.) Run cmd in adb folder, then type in the command "fastboot flash recovery recovery.img"
e.) Reboot and choose recovery mode - now you have no twrp anymore, but the original recovery menue
f.) Install update, which means, original stock from your sd-card.
Be happy!
It would be nice if you could give me feedback, whether my solution was helpful for you, because it took time to write it and hope it will usefull
Click to expand...
Click to collapse
Very helpful, thanks!
I must've messed something up when I flashed TWRP.
TWRP ran fine, but when I tried to start it up, it stayed stuck at the Android logo.
Then errors popped up when I tried to install the stock rom through TWRP.
I never would've thought or had the guts to restore stock recovery first.
This should get its own thread.
Edit: I think my mistake was unchecking "Mount system partition read-only."

halim_wijaya58 said:
i think you need flash full firmware bro ,
1. Download newer version firmware
2. You need Convert system.New.DAT to system.img
3. Move system.img and boot.img to minimal adb & fastboot folder
4. Open minimal adb & fastboot
5. Flash boot.img and system.img
Click to expand...
Click to collapse
After many days i finally found enough time to try to use your tips.
I tried to convert system.New.DAT to system.img but without success using this program Autotool 3.0
http://www.droidviews.com/convert-and-extract-system-img-and-system-new-dat-files-on-windows/
After this attempt i used a ROM provided by chinese store to flash its content :
system.img
boot.img
recovery.img
Original recovery.img is essential to install other updates.
After that i tried to install other updates recognized directly starting by phone but always without success.
So i have had to install updates using original recovery tool.
Now i got Android 7.1.1 last version installed on my phone but it's impossible to use
TWRP recovery tool.
Obviously it's possible to install TWRP instead of original recovery tool and also possible to make a nandroid backup
but it's impossible to use it to install original ROMs released from Asus and it's not possible
to use to restore nandroid backups.
Is it eventually possible to use a custom ROM ? If it's, which one and possibly compatible with TWRP ?

i solved issue of update, but TWRP ?
halim_wijaya58 said:
i think you need flash full firmware bro ,
1. Download newer version firmware
2. You need Convert system.New.DAT to system.img
3. Move system.img and boot.img to minimal adb & fastboot folder
4. Open minimal adb & fastboot
5. Flash boot.img and system.img
Click to expand...
Click to collapse
After many days I finally found enough time to try to update my Asus Zenfone 3 Zoom to Android Nougat.
To solve the issue, I used an original Rom from the Chinese store because it contains useful files for purpose without any conversion:
boot.img
system.img
recovery.img
I flashed all 3 IMG files.
Recovery.img that it's necessary to get original recovery without which any update can be done.
You must use a microSD and the original recovery tool to be able to upgrade your system.
The problem is that it does not seem possible to use TWRP. It is possible to install it in place of the original recovery and you can do also a nandroid backup but in practice you can not use it to install any updates and restore any nandroid backups.
Is there a custom rom that you can use instead of the original one?

SUJAN SN HW said:
Boss,
This solutions can work with ASUS ZENFONE 3 ZOOM.........???
I have ZenFone 3 zoom. Already I successfully convert CN to WW Rom by following this introduction ... https://forum.xda-developers.com/zenfone-3-zoom/how-to/transfer-cn-rom-to-ww-rom-ze553kl-t3612990
But, I can't update android nougat any way. I convert system.new.dat to system.img...... And try to flash it but unfortunately that's not working......
Please help me .......:crying:
Click to expand...
Click to collapse
how did you convert the .dat to .img?

josejbs said:
how did you convert the .dat to .img?
Click to expand...
Click to collapse
Here's a link to the tool
https://forum.xda-developers.com/android/general/tools-extract-dat-t3467581

Razer 2 Global MR2 Sept 2019 Release Magisk Root & Arter97 Kernel / TWRP ?

Can someone confirm these steps will work..
MR1 that has Arter97 Kernel with TWRP and is rooted with Magisks
----------------------------------------------------------------------------------
1. Flash back to factory P-MR1-RC003-RZR-190305.3110 using instructions on Razer Develope Portal
https://developer.razer.com/razer-phone-dev-tools/factory-images/
2. Lock the Bootloader Critical Partitions
command: fastboot flashing lock_critical
3. Locking the Bootloader
command: fastboot flashing lock
4. Reboot phone and let it setup
5. Enable OEM locking
6. Wait/Take OTA for MR2
Re-Root MR2
----------------
1. FLash MR2 rooted image via FASTBOOT
https://forum.xda-developers.com/showpost.php?p=80553681&postcount=57
2. Flash Arter97 Kernel & TWRP via FASTBOOT
3. Reboot
??????????????????????????????????
Is the above the best way? Can we just flash the factory MR1 bootloader and recovery and take the OTA, then install Arter97/TWRP and then install Magisks?
Please advise...
Thanks,
RJR

I'm in the same boat, waiting for confirmation before installing September update.
I need root, and if we can't root the new September release, then I rather stay in the current version.

1. install factory images
2. update
3. flash arter and root
if you notice any bootloop i recommend u use gsi because i had once bootloop for no reason on stock but gsi is just fine

RKBD said:
1. install factory images
2. update
3. flash arter and root
if you notice any bootloop i recommend u use gsi because i had once bootloop for no reason on stock but gsi is just fine
Click to expand...
Click to collapse
Sorry but I have seen in another thread that to get root on latest September update, we had to flash the modded boot provided. So if we root after arter, we will loose arter?
Sorry if it's a noob question but rooting last update isn't clear to me.

This Works I've done it on my razor phone 2 Global
This does work
rrusek said:
Can someone confirm these steps will work..
MR1 that has Arter97 Kernel with TWRP and is rooted with Magisks
----------------------------------------------------------------------------------
1. Flash back to factory P-MR1-RC003-RZR-190305.3110 using instructions on Razer Develope Portal
https://developer.razer.com/razer-phone-dev-tools/factory-images/
2. Lock the Bootloader Critical Partitions
command: fastboot flashing lock_critical
3. Locking the Bootloader
command: fastboot flashing lock
4. Reboot phone and let it setup
5. Enable OEM locking
6. Wait/Take OTA for MR2
Re-Root MR2
----------------
1. FLash MR2 rooted image via FASTBOOT
https://forum.xda-developers.com/showpost.php?p=80553681&postcount=57
2. Flash Arter97 Kernel & TWRP via FASTBOOT
3. Reboot
??????????????????????????????????
Is the above the best way? Can we just flash the factory MR1 bootloader and recovery and take the OTA, then install Arter97/TWRP and then install Magisks?
Please advise...
Thanks,
RJR
Click to expand...
Click to collapse

macjunkie said:
This does work
Click to expand...
Click to collapse
OK thanks I'll do that!
But the download link doesn't work anymore...

http://arter97.com/browse/aura/kernel/ latest 12r kernel won't bootloop so.
1. flash untouched RP2 mr1 firmware (latest for now in razer factory images)
2. update it to mr2
3. fastboot flash boot [arter r12 kernel]
4. then root or whatever you want

RKBD said:
http://arter97.com/browse/aura/kernel/ latest 12r kernel won't bootloop so.
1. flash untouched RP2 mr1 firmware (latest for now in razer factory images)
2. update it to mr2
3. fastboot flash boot [arter r12 kernel]
4. then root or whatever you want
Click to expand...
Click to collapse
Root before flashing GSI or after?

EMJI79 said:
Root before flashing GSI or after?
Click to expand...
Click to collapse
after.
it doesn't matter tho because it's on boot partition not system. but you won't need to reboot twice if you install it after flashing gsi.

RKBD said:
http://arter97.com/browse/aura/kernel/ latest 12r kernel won't bootloop so.
1. flash untouched RP2 mr1 firmware (latest for now in razer factory images)
2. update it to mr2
3. fastboot flash boot [arter r12 kernel]
4. then root or whatever you want
Click to expand...
Click to collapse
Well bad luck for me: it says device is corrupt after flashing mr1.
Maybe it has to do with I didn't unlock critical Bootloader. Will try.

EMJI79 said:
Well bad luck for me: it says device is corrupt after flashing mr1.
Click to expand...
Click to collapse
don't worry it's because you are on A/B device and you installed it on B partition instead of A
fastboot set_active a
then flash mr1 again

RKBD said:
don't worry it's because you are on A/B device and you installed it on B partition instead of A
fastboot set_active a
then flash mr1 again
Click to expand...
Click to collapse
Off topic: you said you wanted to have gestures, there's even better than Q gestures, with the app fluid navigation gestures you can set gestures to whatever you want. For example you could get close to Oxygen OS gestures which are great.

EMJI79 said:
Off topic: you said you wanted to have gestures, there's even better than Q gestures, with the app fluid navigation gestures you can set gestures to whatever you want. For example you could get close to Oxygen OS gestures which are great.
Click to expand...
Click to collapse
i know that app. but they're not that smooth and integrated with system

so no flawless alternative rom here?
Resurection get some issue with bluetooth audio(car audio HFP), and some trouble with fingerprint (works some times)
and havoc 2.9 GSI same issue
i don't know, leave original one?
now i've rolled back the MR1, but get persistent error upgrading MR1 (all restored to original one, boot and system )

igiolo said:
so no flawless alternative rom here?
Resurection get some issue with bluetooth audio(car audio HFP), and some trouble with fingerprint (works some times)
and havoc 2.9 GSI same issue
i don't know, leave original one?
now i've rolled back the MR1, but get persistent error upgrading MR1 (all restored to original one, boot and system )
Click to expand...
Click to collapse
Nope, no solid alternative. Unfortunately, development for the RP2 (and most Android phones these days) has been almost non-existent. Our options are either stay stock, or use one of the GSI's that all have issues of various kinds with our phone.

Hey everyone,
Apologies on the redundancy - but for someone who just scored this phone from Razer for 299 and took the MR2 update the minute it got on wifi, would these steps work to just get root/magisk going?
Enable OEM unlock
reboot to the bootloader
use fastboot command to unlock bootloader
flash mr2 rooted image via fastboot
flash arter97 and twrp via fastboot
reboot
profit?
I'm just looking to get root/magisk, no ROMS or anything.
Thanks all

shokxdauser said:
Hey everyone,
Apologies on the redundancy - but for someone who just scored this phone from Razer for 299 and took the MR2 update the minute it got on wifi, would these steps work to just get root/magisk going?
Enable OEM unlock
reboot to the bootloader
use fastboot command to unlock bootloader
flash mr2 rooted image via fastboot
flash arter97 and twrp via fastboot
reboot
profit?
I'm just looking to get root/magisk, no ROMS or anything.
Thanks all
Click to expand...
Click to collapse
1 enable oem unlock
2 reboot to bootloader via power down and click bootloader unlock
3 flash kernel via fastboot (twrp is inside kernel)
4 flash magisk

RKBD said:
1 enable oem unlock
2 reboot to bootloader via power down and click bootloader unlock
3 flash kernel via fastboot (twrp is inside kernel)
4 flash magisk
Click to expand...
Click to collapse
As always, much appreciated.

shokxdauser said:
As always, much appreciated.
Click to expand...
Click to collapse
Hmm. I thought maybe using the fastboot flash boot_a command would help but I am still getting this error when I try to flash the kernel when I try this full command:
fastboot flash boot_a arter97.img
gets me -
error: failed to identify current slot
I'm guessing I missed something obvious..?
---------- Post added at 11:49 PM ---------- Previous post was at 11:23 PM ----------
Just to note from my previous post about the error - failed to identify current slot -
I am able to see the device when I type fastboot devices. Still trying to figure out why it's saying failed to identify current slot..

shokxdauser said:
Hmm. I thought maybe using the fastboot flash boot_a command would help but I am still getting this error when I try to flash the kernel when I try this full command:
fastboot flash boot_a arter97.img
gets me -
error: failed to identify current slot
I'm guessing I missed something obvious..?
---------- Post added at 11:49 PM ---------- Previous post was at 11:23 PM ----------
Just to note from my previous post about the error - failed to identify current slot -
I am able to see the device when I type fastboot devices. Still trying to figure out why it's saying failed to identify current slot..
Click to expand...
Click to collapse
Let us know if you get it. I have this phone coming to me and want only TWRP/Magisk.
Thanks.

mi9t loop to TWRP recovery after install MIUI 11

Hello
today I got an update for MIUI 11 by OTA, I press agree for "UPDATE", my phone restarted to TWRP, it's Installed some files for update, after finished that my phone keep restarting to TWRP recovery again (LOOP)
I tried to download official rom and install by TWRP ,but after finish and restart device still rebooting to TWRP recovery
is there any solution for not losing my data ?
BTW : flash stock rom didn't remove TWRP recovery , why ?
(I download rom from xiaomifirmware [dot] com)

I am not expert on that field but from my knowledge try booting twrp and copy all your files to your pc or laptop (the one you need at least for saving some photos or videos ) then flash a fastboot ROM
And as I said from my knowledge not sure there might be other ways

testemailmailx said:
Hello
today I got an update for MIUI 11 by OTA, I press agree for "UPDATE", my phone restarted to TWRP, it's Installed some files for update, after finished that my phone keep restarting to TWRP recovery again (LOOP)
I tried to download official rom and install by TWRP ,but after finish and restart device still rebooting to TWRP recovery
is there any solution for not losing my data ?
BTW : flash stock rom didn't remove TWRP recovery , why ?
(I download rom from xiaomifirmware [dot] com)
Click to expand...
Click to collapse
Your phone was on a custom ROM but you didn't know it? oO
No Official ROM will boot and auto-install in TWRP...
Try to clear "Dalvik/Cache" and if still not booting then you will need to "Format Data" in TWRP (loose data).
If still not working, flash a fastboot image...

Micdu70 said:
Your phone was on a custom ROM but you didn't know it? oO
No Official ROM will boot and auto-install in TWRP...
Try to clear "Dalvik/Cache" and if still not booting then you will need to "Format Data" in TWRP (loose data).
If still not working, flash a fastboot image...
Click to expand...
Click to collapse
No it’s official rom miui 10
I clear theme many times even when install stock rom by twrp but still looping after appear xiaomi logo (andriod logo never shows)

testemailmailx said:
No it’s official rom miui 10
I clear theme many times even when install stock rom by twrp but still looping after appear xiaomi logo (andriod logo never shows)
Click to expand...
Click to collapse
Maybe it's a miui.eu or a different region ROM that was installed as .zip so it still appear as mi/redmi logo

batman957 said:
Maybe it's a miui.eu or a different region ROM that was installed as .zip so it still appear as mi/redmi logo
Click to expand...
Click to collapse
Installed from xiaomifirmware site
Is there any opportunity to fix phone ?

testemailmailx said:
Installed from xiaomifirmware site
Is there any opportunity to fix phone ?
Click to expand...
Click to collapse
Try flashing the fastboot ROM the .tgz one not the .zip using miflash but try to use the miui 10 one and later on update (getting the phone to work is more important right now )

batman957 said:
Try flashing the fastboot ROM the .tgz one not the .zip using miflash but try to use the miui 10 one and later on update (getting the phone to work is more important right now )
Click to expand...
Click to collapse
I could make it work easily, but I want keep that step as final step cuz will wipe everything

testemailmailx said:
I could make it work easily, but I want keep that step as final step cuz will wipe everything
Click to expand...
Click to collapse
Then if you can fully boot to twrp try to connect it with an otg or to pc and copy Ur files
It happened to me once btw I deleted the system partition(first time flashing) ? then I flashed the fastboot ROM
If I was in Ur place I would never flash any custom ROM to trigger the anti rollback or lose widevine l1
You may try but be careful of going through wrong things such as edl mode

batman957 said:
Then if you can fully boot to twrp try to connect it with an otg or to pc and copy Ur files
It happened to me once btw I deleted the system partition(first time flashing) then I flashed the fastboot ROM
If I was in Ur place I would never flash any custom ROM to trigger the anti rollback or lose widevine l1
You may try but be careful of going through wrong things such as edl mode
Click to expand...
Click to collapse
God bless us
I’m not using custom rom at all
BTW is there any way to delete twrp recovery without delete system ?

Did you by any chance flashed with the greek TWRP? I got the same bootloop so I get back to miui 10 official global version (the one I updated from) and it booted alright without wipe needed...
I'll try other TWRP versions as well though but right now I don't think I wanna update :|

Yup you should disable disable dm verity and verification
just flash this using fastboot and you're good to go, I am now running official miui 11 without wiping the data.
Code:
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
https://gofile.io/?c=fgyAB3

sijav said:
Yup you should disable disable dm verity and verification
just flash this using fastboot and you're good to go, I am now running official miui 11 without wiping the data.
Code:
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
https://gofile.io/?c=fgyAB3
Click to expand...
Click to collapse
Hey,
The file you mentioned is not founded! could you please re upload it somewhere ?

m-Khadem said:
Hey,
The file you mentioned is not founded! could you please re upload it somewhere ?
Click to expand...
Click to collapse
Here is patched vbmeta for davinci (K20/Mi 9T) => https://drive.google.com/file/d/1IC78J20ovcZudWYlijgSGdjeP6D3hx2V/view?usp=sharing

Guide to flash realmeUI 2.0 beta builds [Global Variant Only]

DISCLAIMER: YOU ARE RESPONSIBLE FOR WHAT YOU DO​The only reason behind posting this guide is because now we have a way to fix device if any unusual things happen after flashing beta builds. Beginners & noobs who doesn't have any idea about flashing stuff should stay away.
PREREQUISITES:
1. Bootloader Unlocked Device
2. OrangeFox
3. Stable OZIP (Android 10 | realmeUI 1.0 | C35)
4. Beta ZIP (Android 11 | realmeUI 2.0 | F06)
5. Unofficial OrangeFox beta build (For realmeUI 2.0 A11 FW only)
6. realmeUI 2.0 stock recovery
7. A11 VBMETA
8. Patched VBMETA
PROCESS TO FLASH:
1. Just to be on safer side we are going to make sure everything is stock & all partitions are unmodified. So reflash latest Stable OZIP (C35) via OrangeFox.
2. Format data & reboot to System (This is optional but better to do it, we never know what might happen with realme device)
3. Reboot back to Bootloader if realmeUI 1.0 boots fine
4. Flash OrangeFox build which you used previously & also flash patched vbmeta (fastboot flash vbmeta patched_vbmeta.img)otherwise you get "Boot is destroyed........"
5. Boot into custom recovery & copy downloaded Beta ZIP
6. Flash the Beta ZIP & format data.
7. Reboot to System. realmeUI 2.0 should boot now.
COMMON ISSUES & FIXES:
1. Device stuck at white realme splash logo
Sol. Few people reported it booted when they flashed patched vbmeta so you can first try that. If doesn't work then you can flash A11 vbmeta (fastboot flash vbmeta vbmeta.img) attached here & reboot to system
2. Device stuck at Yellow realme boot animation
Sol. If it's stuck for more than 2-3mins then reboot to bootloader & format data by executing fastboot erase userdata ., never do fastboot -w it's messing up data partition in A11 due to new changes introduced by realme
3. Stuck in bootloader (fastboot)
Sol. Flash the unofficial OrangeFox rescue build & boot into it, copy C35 OZIP to internal storage. Flash it & format data. Reboot to System. Wait for public realmeUI 2.0 release.
4. Unofficial OrangeFox beta build stuck at Ofox splash & display keeps blinking
Sol. This happens because Ofox can't decrypt realmeUI 2.0 data, only way to boot this ofox build properly is by formatting data, reboot back to bootloader. fastboot erase userdata
5. Device doesn't have realmeUI 2.0 Stock Recovery
Sol. Flash the attached stock recovery

reserved

Congrats! Will try now
EDIT: Works fine but just 2 hints.
1: Don't Use TWPR 3.5.0_9 or you will get Zip Treble Error
2: After you flash RUI 2.0 it's a MUST flash A11 VBMETA

Can i Flash on Locked Bootloader device via stock recovery or filemanager currently i am c 34 locked bootloader

bharatgsp said:
Can i Flash on Locked Bootloader device via stock recovery or filemanager currently i am c 34 locked bootloader
Click to expand...
Click to collapse
na it doesn't work

ChromiumPD said:
Congrats! Will try now
EDIT: Works fine but just 2 hints.
1: Don't Use TWPR 3.5.0_9 or you will get Zip Treble Error
2: After you flash RUI 2.0 it's a MUST flash A11 VBMETA
Click to expand...
Click to collapse
Right will update guide, thank you

What does the check look like that prevents the stock recovery from accepting to flash the beta build (if you try to upgrade from C.35)?

kurtextrem said:
What does the check look like that prevents the stock recovery from accepting to flash the beta build (if you try to upgrade from C.35)?
Click to expand...
Click to collapse
Stock recovery only accepts signed OZIP/ZIP like the ones uploaded in their website, OTA updates we receive are signed with different certificate that's why installing those custom OZIPs fail if we do it manually.

It can't install on TWRP 3.4.0.0 -> Error this package is for RMX1931L1, this is a ""

Zippka224 said:
It can't install on TWRP 3.4.0.0 -> Error this package is for RMX1931L1, this is a ""
Click to expand...
Click to collapse
edited guide, use ofox only. TWRP doesn't seem to work for everyone.

Hi, first thanks for the post.
I would like to ask you if there is a way to revert back to c35 after?
Thank you in advance

4j17h said:
Stock recovery only accepts signed OZIP/ZIP like the ones uploaded in their website, OTA updates we receive are signed with different certificate that's why installing those custom OZIPs fail if we do it manually.
Click to expand...
Click to collapse
Thank you. I wonder how the software update works then? How does the software update "app" manage to flash those builds then?

Tierri said:
Hi, first thanks for the post.
I would like to ask you if there is a way to revert back to c35 after?
Thank you in advance
Click to expand...
Click to collapse
Well there are two ways, we can use stock recovery to downgrade from beta builds to C34
Another way would be to flash unofficial Ofox build, copy C34 OZIP to internal storage & flash it.

kurtextrem said:
Thank you. I wonder how the software update works then? How does the software update "app" manage to flash those builds then?
Click to expand...
Click to collapse
OTA updater app is verifying the update & rebooting to stock recovery, so if we can figure out the same way we can install custom ozips via stock recovery too

How would you recommend to bring over apps & their settings to A11? After formatting data they'll be lost. Which backup method is able to restore them? Have you rooted it already?

Magisk?
Cool ! It works fine thank you.
but I noticed that the "Unofficial OrangeFox beta build" cant mount internal storage issue with following error : "could not mount /data and unable to find crypto footer"
So is there another way to Root my device without wiping data?

Hi
First Thank you for this post .
I want to restore a stock recovery UI 1.0 now i am using orangefox recovery on C.34
can i restore without format data or waiting UI 2.0 stable ??
Many Thanks

Hi,
I've followed the steps and no errors. After reboot, the system stucks at Realme white logo. How it's said on common issues, i've flashed then A11 vbmeta, and the same. Ive waited about 10minutes and it keeps there. I've tried flash the Ofox recovery again to repeat the process but now I can't get Ofox working. I can access fastboot and if I try reboot to recovery, it symply reboots to bootloader... What should I do? I also tried all the options in common issues but without success...
Thanks

tuga49 said:
Hi,
I've followed the steps and no errors. After reboot, the system stucks at Realme white logo. How it's said on common issues, i've flashed then A11 vbmeta, and the same. Ive waited about 10minutes and it keeps there. I've tried flash the Ofox recovery again to repeat the process but now I can't get Ofox working. I can access fastboot and if I try reboot to recovery, it symply reboots to bootloader... What should I do? I also tried all the options in common issues but without success...
Thanks
Click to expand...
Click to collapse
try to install patched vbmeta its work form me

So for me I dirty flashed the f06.zip beta on c.35 in official [email protected]_1 release and flashed vbmetaA11 but it failed to then i flashed patched_vbmeta.img and voila it booted just fine and optimizing apps appeared.
Thanks very much to Original Poster we can now use Realme UI 2.0 because of him.
Thanks a lot once again