Database Users

how to reverse LP kernel to KK redmi 2 PRO

then this problem install TWRP 3.0 changes the kernel for the installation of LP and MM over all users have this problem can not install another LP rom in my case only with the MIUI 5.1 LP installed OTHER roms for loop and do not know what to do to return to kernel kk
someone help
any suggestion

to reverse , install rom Miui KK using fastboot (MiFlash to PC).

already tried with fastboot mode
Cecell3000 said:
to reverse , install rom Miui KK using fastboot (MiFlash to PC).
Click to expand...
Click to collapse
over the issue I have to unlock it already tried but can not yet appear path not found

unpack rom specific to fastboot(miflash):
bigota.d.miui.com/V7.1.1.0.KHJMICK/wt88047_global_images_V7.1.1.0.KHJMICK_20151209.0000.6_4.4_global_a49c63ee30.tgz
tutorial:
xiaomiredmi2br.blogspot.com.br/2015/10/tutorial-instalando-rom-original-do.html?m=1

Cecell3000 said:
unpack rom specific to fastboot(miflash):
bigota.d.miui.com/V7.1.1.0.KHJMICK/wt88047_global_images_V7.1.1.0.KHJMICK_20151209.0000.6_4.4_global_a49c63ee30.tgz
tutorial:
xiaomiredmi2br.blogspot.com.br/2015/10/tutorial-instalando-rom-original-do.html?m=1
Click to expand...
Click to collapse
The main thing is, you have to extract the tgz file, which will result in a tar file, so extract that again, add the adb files in that folder and follow the other steps

[Guide][Zenfone 2]Flash Custom ROM in Unlocked Android 6.0

**All credit to @shakalaca for his dedication. Also thanks to Enjie in Taiwan Asus Zentalk forum.
**Do it at your risk
This guide is to help you flash custom rom, like CM 13, in unlocked Android 6.0.
The point of this thread is to pack signature files into TWRP and boot.img so that we can boot from custom roms.
This thread won't be needed if TWRP/Custom Rom patch into MM the signature file in the future. For now, sorry for the mess.
1.Add signature to TWRP
a. Download your favorite twrp. The latest official twrp is doable.
b.Download and unzip the attached file: recovery_z00a.sig
c.Copy the above 2 files in the same directory.
d.Activate cmd window in your pc (window button + R, type cmd, Enter)
e.Add signature to TWRP in cmd window: (Suppose you put all files in c:\) , replace <twrp.img> with your TWRP file name.
Code:
cd c:\
copy /b <twrp.img> + recovery_z00a.sig recovery_mod.img
Now you will see a new file, recovery_mod.img created.
2.Add signature to boot.img
a. Unzip and extract boot.img from custom rom.
b. Download and unzip the attached file: boot_z00a.sig
c.Copy the above 2 files in the same directory.
d.Activate cmd window in your pc (window button + R, type cmd, Enter)
e.Add signature to boot.img in cmd window: (Suppose you put all files in c:\)
Code:
cd c:\
copy /b boot.img + boot_z00a.sig boot_mod.img
Now you will see a new file, boot_mod.img created.
3.Unlock MM6.0.
Refer to this thread. This is a 2 click unlock procedure. The device should be unlocked before we can flash twrp and custom rom.
4. After the device is unlocked, in bootloader, flash TWRP recovery now:
Code:
fastboot flash recovery recovery_mod.img
5. Boot from TWRP
6. Flash custom rom from TWRP
7. After done flashing custom rom in TWRP, flash boot_mod.img from TWRP.
Or, from bootloader:
Code:
fastboot flash boot boot_mod.img
8.Reboot system.
*My suggestion is to put the revised kernel in SD card. Later on If you upgrade custom rom, it is easier to flash the repacked boot_mod.img again in TWRP.

god bless you

Thanks But is there any way I can add the signature in kernel and recovery in android without pc. Can I use those commands in android terminal?

Thanks,man

pless support Z008

MrPhamHpGYC said:
pless support Z008
Click to expand...
Click to collapse
Z008 files

Any other easy method for noob like me please..
Sent from my ASUS_Z008 using XDA-Developers mobile app

kjinx01 said:
Any other easy method for noob like me please..
Sent from my ASUS_Z008 using XDA-Developers mobile app
Click to expand...
Click to collapse
It won't be easy unless TWRP and Custorm Roms patch the signature files with them. Maybe we should wait after ASUS roll out its official release.

i try step by step and its work , i flash blurOS on my marshmallow based zenfone . thanks for your hardwork mate

Thanks a lot!!! I already wanted to throw this damn Z00A against the next wall, since neither 5.0 nor 6.0 were working flawlessly. But CM13 is fantastic! Best rom so far. Will never go back to stock.

delete

which rom do i use? can i use cm13 to get the boot.img file

Guys, I want to root my Z00A (MM beta -- .111 build). Is there a way without unlocking the bootloader?
Also I want to know whether the Asus official bootunlocker tool can be used in this MM .111 build so that I can flash CM13 instead.
Thanks in advance.

rohithramesh96 said:
Guys, I want to root my Z00A (MM beta -- .111 build). Is there a way without unlocking the bootloader?
Also I want to know whether the Asus official bootunlocker tool can be used in this MM .111 build so that I can flash CM13 instead.
Thanks in advance.
Click to expand...
Click to collapse
Try this.
http://forum.xda-developers.com/zenfone2/general/android-6-0-beta-root-xposed-downgrade-t3404321

Hi. where I can find more modern sig keys? I make custom kernel for marshmallow and use old ramdisk from 4.21.40.61 firmware. If I take ramdisk from boot.img from newer firmware and tnen pack back into boot.img, then to sign boot.img, device can't start. I suppose the reason of this- incompatible key?

Hi,
How could I manually sign these files on Ubuntu-based OS? I'm no longer use Windows as my daily OS. Thanks.
Also: Could anyone provide MM final signature keys?
Sent from my ASUS_Z00A using XDA Labs

krasCGQ said:
Also: Could anyone provide MM final signature keys?
Click to expand...
Click to collapse
yes, I get it and use it for sign my lastest kernels. for recovery sign you may use old keys, it compatible

Hi guys , my zf2 is unlocked and rooted ( MM stock .134 )
Is possible sign stock boot.img and stock recovery.img for pass the verification on boot ??

siteswap said:
Hi guys , my zf2 is unlocked and rooted ( MM stock .134 )
Is possible sign stock boot.img and stock recovery.img for pass the verification on boot ??
Click to expand...
Click to collapse
That's what I want to know. And, I want to know too if there is any ota for the marshmallow, and want to flash it, the bootloader needs to be relocked or not? And, dont need to un- systemless root+xposed, right?
Someone who uses MM beta before and succesfully flash ota with unlocked bootloader + systemless root and xposed can you confirm me please?
Sent from my ASUS_Z00A using Tapatalk

I used MM beta, and after that i update to MM ( .134 ) official Fw , and my bootloader was locked.
For unlock+root i used shakalaka metod in xda index.
At moment the last ota that you can find is .134 in Asus site , but i dont know if in future the new ota will relock bootloader

Guide to switch from Vendor ROM to EU ROM

This is for people who have received their phone with a pre-installed Vendor ROM (MIUI Global Stable 8.0.8.0) and wants to switch to the Unofficial EU ROM. In my opinion, the EU ROM is currently the best ROM without any Chinese bloatware or popups until Xiaomi decides to release an actual Global ROM.
For those who are already on a China Stable ROM, there is already an excellent guide to install TWRP, ROOT, compiled by @underlines. This is only intended for switching from a Vendor ROM as I wasn't able to switch from a Vendor ROM to an official build using the previous guide. You need to be on an official build to be able to use TWRP and flash the EU ROM.
EDIT : The reason why I have mentioned to flash an official build at first is because, TWRP can be unresponsive with some Vendor ROMS. You'll be able to boot TWRP but touch would be frozen. I've tried with both versions of TWRP and it wouldn't work with the Vendor ROM installed on my device. TWRP over the Vendor ROM may work for some users.. For some builds like the one which came installed on my phone, it may not work. If TWRP works for you without being on an official build, you can skip the part where you have to flash an official ROM.
1. You need to have an unlocked bootloader. Please follow instructions on the other guide on how to do this.
2. You need the older version of MiFlash found on this link. Thanks to @Thorin78 for this link.
3. Download and extract fastboot Stable or Dev ROM and extract ROM folder to the C:\ Drive. This is because MiFlash may show a "cannot find file" error if you have a lot of subfolders. To avoid this, its best if the folder is C:\ROM Folder.
4.In the older version of MiFlash, click advanced and change the fastboot script location to the flash_all.bat in your unzipped rom folder.
5.Connect your phone in fastboot mode, click "Refresh" in MiFlash. Once your phone is detected, click "Flash" and it should now successfully flash the official ROM of your choice.
If you wish to be on a Xiaomi Official Stable or Dev ROM, Stop here! If you wish to continue installing the EU ROM proceed with the steps below.
6. Now that you have successfully flashed Official Stable or Dev ROM, use Minimal ADB and flash TWRP RC2 using the instructions in the other guide.
7. Once you are in TWRP, Swipe right to allow System Modifications and copy the forced encryption disabler using MTP. Flash this file to ensure that there are no bootloops.
8. After this step, go to WIPE, Format Storage, type "yes" and then Reboot Recovery. Copy SuperSU and EU ROM to storage and flash. Phone may take a few minutes to boot up and you will successfully boot the EU ROM.
For everything else, please follow the guide posted by underlines.
TWRP EU RC2 works with the China Dev ROM as well. Once you Swipe to Right to allow modifications, don't forget to flash the latest dm-verity and forced encryption disabler script from here. This is to prevent the device going into a bootloop.
These are the steps I followed and I am on EU ROM. Hope this helps people who wish to switch to the EU ROM from the Vendor ROM.

The link to miflash takes you DL minimal adb?

jazz452 said:
The link to miflash takes you DL minimal adb?
Click to expand...
Click to collapse
Corrected. Thanks for letting me know! Cheers!

satishp said:
Corrected. Thanks for letting me know! Cheers!
Click to expand...
Click to collapse
I managed to flash with latest miflash using your guide my bootloader was already unlocked check using:
boot your phone into fastboot and COMMAND PROMPT " fastboot oem device-info "
most are probably unlocked with vendor rom but not all.
Don't try to unlock with this method just check to save sometime.
guide: http://xiaomitips.com/guide/how-to-check-if-redmi-note-3-bootloader-is-locked-or-unlocked/

jazz452 said:
I managed to flash with latest miflash using your guide my bootloader was already unlocked check using:
boot your phone into fastboot and COMMAND PROMPT " fastboot oem device-info "
most are probably unlocked with vendor rom but not all.
Don't try to unlock with this method just check to save sometime.
guide: http://xiaomitips.com/guide/how-to-check-if-redmi-note-3-bootloader-is-locked-or-unlocked/
Click to expand...
Click to collapse
I guess it also depends on the Vendor ROM and customization which comes installed on your device. Not all Vendor ROMs for this device are the same. I tried everything under the sun with the latest miflash. It would detect device and even give a "success" output but the ROM was never actually flashed. The phone would still be on the Vendor ROM. Its as if some Vendor ROMs have some form of write protection baked in.
I could only get it working with the older miflash.

I'm not saying it was easy, the hard thing was making the unpack ING of the file. Sort of did it twice never had that problem before.

Why is it required to flash the official rom before flashing the EU rom?

nkatz565 said:
Why is it required to flash the official rom before flashing the EU rom?
Click to expand...
Click to collapse
This for people who don't want TWRP, root and dm-verify, just genuine Xiaomi rom with OTA updates and remove vendor rom.

QQ.
I did the following on my Mix and wondering if I am missing anything. I should say that everything "appears" to be working perfectly on the EU rom.
My Mix came with 8.0.8.0 Global (Vendor ROM) and I wanted to move onto the Xiaomi.eu rom. I loosely followed the above guide and did the following steps:
Applied for Unlock
Unlocked the device via MiUnlock
Used Minimal ADB and booted the device into FastBoot
Confirmed device was Bootloader unlocked
Flashed TWRP (latest non-eu build)
Booted to recovery
DID NOT swipe to edit system partition, left that read only
Flashed the latest Weekly Xiaomi.eu build
Wiped Dalvik/Cache
Booted phone
Performed a Factory reset.
All seemed a little too easy and I didnt need to go to an "Official" china ROM first. But I do have a few questions...
Should I have swiped Yes to enter Read/Write mode for the system partition and run a dm-verify? (I am not interested in Rooting the device at this stage)
Should I have performed a System clear in TWRP before installing Xiaomi.eu ontop of the Vendor ROM?

geubes said:
QQ.
I did the following on my Mix and wondering if I am missing anything. I should say that everything "appears" to be working perfectly on the EU rom.
My Mix came with 8.0.8.0 Global (Vendor ROM) and I wanted to move onto the Xiaomi.eu rom. I loosely followed the above guide and did the following steps:
Applied for Unlock
Unlocked the device via MiUnlock
Used Minimal ADB and booted the device into FastBoot
Confirmed device was Bootloader unlocked
Flashed TWRP (latest non-eu build)
Booted to recovery
DID NOT swipe to edit system partition, left that read only
Flashed the latest Weekly Xiaomi.eu build
Wiped Dalvik/Cache
Booted phone
Performed a Factory reset.
All seemed a little too easy and I didnt need to go to an "Official" china ROM first. But I do have a few questions...
Should I have swiped Yes to enter Read/Write mode for the system partition and run a dm-verify? (I am not interested in Rooting the device at this stage)
Should I have performed a System clear in TWRP before installing Xiaomi.eu ontop of the Vendor ROM?
Click to expand...
Click to collapse
Wouldn't worry about it the vendor ROMs aren't poison, not sure about dm-verify if you kept read only. I would of swiped then flashed dm-verify but didn't mean I know what I'm doing.

nkatz565 said:
Why is it required to flash the official rom before flashing the EU rom?
Click to expand...
Click to collapse
This is because some Vendor ROMS have some compatibility issues with TWRP. Touch screen wouldn't work on TWRP. I tried both TWRP versions and couldn't get touch to work.
Finally, I flashed the China Dev ROM and then used TWRP RC2 and touch functionality worked.
As some users below have pointed out that they could get to EU without flashing the one of the official builds, I guess it depends on the amount or type of vendor customizations applied on your device.

Which version do you own? I was wondering if this would work with the 6GB as well.

dbesada said:
Which version do you own? I was wondering if this would work with the 6GB as well.
Click to expand...
Click to collapse
This works with both versions. The ROM is compatible with both variants as the size of memory and storage doesn't affect compatibility.
I have the 6\256 variant.

satishp said:
This works with both versions. The ROM is compatible with both variants as the size of memory and storage doesn't affect compatibility.
I have the 6\256 variant.
Click to expand...
Click to collapse
Thank you. It worked. I fastboot twrp then factory reset the device and flashed the eu rom. All good. My bootloader was unlocked by the vendor.

Can someone please give me some advice? Just got the phone a couple hours ago. I took a picture of the info page. Based on the screenshot am I on the vendor ROM or official? I'm thinking I'm on Vendor because it has GAPPS already included.
If I'm on Vendor ROM and want to get to rooted EU Rom I can follow directions in the OP right?
How do I know is if my bootloader is already unlocked? Many thanks

SantinoInc said:
Can someone please give me some advice? Just got the phone a couple hours ago. I took a picture of the info page. Based on the screenshot am I on the vendor ROM or official? I'm thinking I'm on Vendor because it has GAPPS already included.
If I'm on Vendor ROM and want to get to rooted EU Rom I can follow directions in the OP right?
How do I know is if my bootloader is already unlocked? Many thanks
Click to expand...
Click to collapse
Vendor (there is no Global ROM for Mix). You should unlock your bootloader (check if it's already unlocked using "fastboot oem device-info"), flash TWRP, wipe and flash EU

Razorbacktrack5535 said:
Vendor (there is no Global ROM for Mix). You should unlock your bootloader (check if it's already unlocked using "fastboot oem device-info"), flash TWRP, wipe and flash EU
Click to expand...
Click to collapse
Do I have to do Power + Vol Down (that's bootloader mode right) in order to input the ADB code you gave me?

SantinoInc said:
Do I have to do Power + Vol Down (that's bootloader mode right) in order to input the ADB code you gave me?
Click to expand...
Click to collapse
Yes, you have to use Fastboot Mode

Razorbacktrack5535 said:
Yes, you have to use Fastboot Mode
Click to expand...
Click to collapse
I'm not unlocked right? Hope they approve my unlock request soon

SantinoInc said:
I'm not unlocked right? Hope they approve my unlock request soon
Click to expand...
Click to collapse
Yes, you have to wait

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

flashing roms with 4.4.x kernel without qpst

If you afraid to flash qpst rom, here a method which will update your baseband/bootloader without qpst tool.
1) flash vendor to factory ( if you already flashed factory to vendor )
2) flash zui 3.5.389 full ota which has firmware included ( not the deodexed one by hendibudi )
Link :https://drive.google.com/file/d/1knkZxUyLNZO7uS8u_CK7j4j5-UqqGs5l/view (don't reboot
3) flash hendibudi's twrp for zui and reboot to rom
( The step 2 will lock your bootloader/ update your firmware/ bootloader. So we need to unlock bootloader again. To avoid wiping of internal storage we use twrp recovery which will only wipe /data
4)unlock your bootloader by following this
https://forum.xda-developers.com/lenovo-zuk-z2/how-to/how-bootloader-zuk-z2-pro-t3415392
( You can use your old unlock image )
5) clean flash any nontreble rom( needed)
Reboot to rom.
6)Reboot to recovery, flash factory to vendor zip.
( Don't reboot )
7) install latest twrp from twrpbuilder.org for our device ( install--image -- select -- recovery-swipe to flash )
8) reboot to recovery
9) clean flash your fav 4.4. kernel ROMs.
Note:
I am not tested new twrp by twrpbuilder.org instead of hendibudi twrp at step 3.
If it doesn't encrypt internal storage, there is no need of step 5&7
I followed this and worked. Don't miss any steps

I've Lost my unclocked bootloader file. There is a way to extract It from my Zuk? Thanks?
Inviato dal mio Z2 Plus utilizzando Tapatalk

sandruman said:
I've Lost my unclocked bootloader file. There is a way to extract It from my Zuk? Thanks?
Inviato dal mio Z2 Plus utilizzando Tapatalk
Click to expand...
Click to collapse
You can request unlock .img again

The way I got it working was by
1. Flashing deodexed TWRP flashable ZUI 4.0.233 rom and then set it up along with magisk.
2. Flashed factory2vendor.zip
3. Flashed TWRP by z2_plus_treble-TWRP-3.2.2_kubersharma_v2.img available in his thread.
4. Clean Flashed AEX 5.8
5. After setup again in TWRP clean flashed a Beta version of AEX v6.0
6. Again after that clean flashed the Official version of AEX v6.0.
You can skip step 4 & 5. I followed those steps to avoid any Blue Screen issue recently reported by some users. I didn't face any Bootloader problem.
*Remember to use Kubersharma TWRP in step 3. I don't know why, but Treble TWRP compiled by Davide is not reading internal storage when flashed after ZUI deodexed.
*And I am not responsible for anything that happens during your adventures.

ShaktiSW said:
The way I got it working was by
1. Flashing deodexed TWRP flashable ZUI 4.0.233 rom and then set it up along with magisk.
2. Flashed factory2vendor.zip
3. Flashed TWRP by z2_plus_treble-TWRP-3.2.2_kubersharma_v2.img available in his thread.
4. Clean Flashed AEX 5.8
5. After setup again in TWRP clean flashed a Beta version of AEX v6.0
6. Again after that clean flashed the Official version of AEX v6.0.
You can skip step 4 & 5. I followed those steps to avoid any Blue Screen issue recently reported by some users. I didn't face any Bootloader problem.
*Remember to use Kubersharma TWRP in step 3. I don't know why, but Treble TWRP compiled by Davide is not reading internal storage when flashed after ZUI deodexed.
*And I am not responsible for anything that happens during your adventures.
Click to expand...
Click to collapse
Didn't you every flashed a 3.1+ zui via qpst before?
Because as far as i know the deodexed zui 4.0. 233 doesn't updates the bootloader

satyen_ said:
Didn't you every flashed a 3.1+ zui via qpst before?
Because as far as i know the deodexed zui 4.0. 233 doesn't updates the bootloader
Click to expand...
Click to collapse
I never needed to. And AEX 6.0 run pretty much smooth without blue screen issue. I just followed the above mentioned procedures.

Deleted.

senthamizhan said:
If you afraid to flash qpst rom, here a method which will update your baseband/bootloader without qpst tool.
1) flash vendor to factory ( if you already flashed factory to vendor )
2) flash zui 3.5.389 full ota which has firmware included ( not the deodexed one by hendibudi )
Link :https://drive.google.com/file/d/1knkZxUyLNZO7uS8u_CK7j4j5-UqqGs5l/view (don't reboot
3) flash hendibudi's twrp for zui and reboot to rom
( The step 2 will lock your bootloader/ update your firmware/ bootloader. So we need to unlock bootloader again. To avoid wiping of internal storage we use twrp recovery which will only wipe /data
4)unlock your bootloader by following this
https://forum.xda-developers.com/lenovo-zuk-z2/how-to/how-bootloader-zuk-z2-pro-t3415392
( You can use your old unlock image )
5) clean flash any nontreble rom( needed)
Reboot to rom.
6)Reboot to recovery, flash factory to vendor zip.
( Don't reboot )
7) install latest twrp from twrpbuilder.org for our device ( install--image -- select -- recovery-swipe to flash )
8) reboot to recovery
9) clean flash your fav 4.4. kernel ROMs.
Note:
I am not tested new twrp by twrpbuilder.org instead of hendibudi twrp at step 3.
If it doesn't encrypt internal storage, there is no need of step 5&7
I followed this and worked. Don't miss any steps
Click to expand...
Click to collapse
First of all, kudos for the great job! I'm anxious to test it.
But please forgive my stupidity.
Which hendibudi TWRP build you mean? I could only find a 3.2.1 but I'm not sure it can handle Treble.

renatohm said:
First of all, kudos for the great job! I'm anxious to test it.
But please forgive my stupidity.
Which hendibudi TWRP build you mean? I could only find a 3.2.1 but I'm not sure it can handle Treble.
Click to expand...
Click to collapse
Yes it doest support treble partition. But we need that twtp to avoid internal storage encryption problem.
So we can flash any non treble ROM, reboot yo ROM, reboot to recovery , flash factory to vendor zip, flash latest treble twrp, reboot to twrp then flash 4.4 ROMs.
My entire point is flashing vendor to factory and and full ota 3.5.389 zip will update bootloader, firmware ( it will work just as qfil flash )
My guide can be followed if someone having trouble with qfil . ( tested by at least 2 people )
Other steps are just to avoid encryption and internal storage wipe problems that may come after flash.
Hope it'll remove doubts

senthamizhan said:
Yes it doest support treble partition. But we need that twtp to avoid internal storage encryption problem.
So we can flash any non treble ROM, reboot yo ROM, reboot to recovery , flash factory to vendor zip, flash latest treble twrp, reboot to twrp then flash 4.4 ROMs.
My entire point is flashing vendor to factory and and full ota 3.5.389 zip will update bootloader, firmware ( it will work just as qfil flash )
My guide can be followed if someone having trouble with qfil . ( tested by at least 2 people )
Other steps are just to avoid encryption and internal storage wipe problems that may come after flash.
Hope it'll remove doubts
Click to expand...
Click to collapse
Thanks for your kindness!
Alright then, I'm next on line to test! I'll just backup (it sucks...) then I'll flash!

Out of luck, flashing via Mi Tool now...

renatohm said:
Out of luck, flashing via Mi Tool now...
Click to expand...
Click to collapse
What happened

senthamizhan said:
What happened
Click to expand...
Click to collapse
Blue screen. I'm stuck on Qfil too, it also resulted in blue screen. Starting from scratch.

renatohm said:
Blue screen. I'm stuck on Qfil too, it also resulted in blue screen. Starting from scratch.
Click to expand...
Click to collapse
There is baseband zip file of 3.5 zui (in guides and discussion section) you can flash that if you don't want to go through the long process of Qfil, I flash that zip and i am able to use 4.4 kernels
This will not lock your bootloader and can be flashed by official TWRP

satyen_ said:
There is baseband zip file of 3.5 zui (in guides and discussion section) you can flash that if you don't want to go through the long process of Qfil, I flash that zip and i am able to use 4.4 kernels
This will not lock your bootloader and can be flashed by official TWRP
Click to expand...
Click to collapse
Yes, that's the reason I tried this in the first place, but it didn't work for me.
Qfil did work, and I'm now on Bootleggers.

sandruman said:
I've Lost my unclocked bootloader file. There is a way to extract It from my Zuk? Thanks?
Inviato dal mio Z2 Plus utilizzando Tapatalk
Click to expand...
Click to collapse
Bro,if u had used your email address try checking in your inbox again for image, just search bootloader .

I've changed my mail with a Gmail one and it work. Now I've my unl files
Inviato dal mio Z2 Plus utilizzando Tapatalk

flash vendor to factory ( if you already flashed factory to vendor ) "
explain this line

In these forums there was a file for updating baseband to 1.70. I flashed it promptly and my phone also went into soft brick. Because accidentally my bootloader got locked and got revised also. By using certain key combinations I succeeded in again unlocking my bootloader without formatting my inner storage . now I am able to flash 4.4 ROMs. Without going through all the hassles of backup, formatting and again flashing twrp.

Your guide didn't work for me (but step 2 using your file didn't lock my bootloader). It would be nice if you gave direct link to items in your steps (for i.e factory to vendor.zip, twrp...). I guess I'll try using qfil unless someone has some tips... BTW I can't find a good qfil guide for 4.4 kernel roms, could anyone give me a link to a helpful thread for it if I can't get it working using this method?