[RECOVERY][2018-08-06][UNOFFICIAL] TWRP 3.2.3 for ZE520KL and ZE552KL

[CygnusBlack]

so baseband cannot be updated using custom rom!?

Sent from my ASUS_Z012D using Tapatalk

The baseband "firmware" needed for a custom ROM to work usually comes from the manufacturer of the phone (or carrier).
So, if you have Android 8.x as stock rom, devs will take that baseband material and implement it to the custom Oreo rom. That's why people, sometimes, have troubles with a custom ROM running (for example) Android 4.2.2 when the firmware is from 4.1.2.
Stock will flash the latest firmware of the modem and customs can go alongside. That way, it'll be compatible and will not freak out, dropping mobile data and cellular connection.

 

[Syahid M.]

The baseband "firmware" needed for a custom ROM to work usually comes from the manufacturer of the phone (or carrier).
So, if you have Android 8.x as stock rom, devs will take that baseband material and implement it to the custom Oreo rom. That's why people, sometimes, have troubles with a custom ROM running (for example) Android 4.2.2 when the firmware is from 4.1.2.
Stock will flash the latest firmware of the modem and customs can go alongside. That way, it'll be compatible and will not freak out, dropping mobile data and cellular connection.

hmm... okay got it

Sent from my ASUS_Z012D using Tapatalk

 

[lanserffnt]

I want to cover data to f2fs but

mkfs.f2fs -t 0 -r 16384 /dev/block/mmcblk0p67 error :1

How to fix it ?

I try to edit recovery.fstab it's ok

 

[saswatmeher05]

not working with latest stock rom .55 for ze520kl

I tried to flash it from fastboot and it was successfully flashed. After rebooting to system then recovery, asus stock recovery was replaced. If I try to boot into recovery after flashing before booting to stock rom it boots but restarting to system makes a boot loop. I was unable to use this recovery and latest stock rom at the same time...

 

[planet9]

I tried to flash it from fastboot and it was successfully flashed. After rebooting to system then recovery, asus stock recovery was replaced. If I try to boot into recovery after flashing before booting to stock rom it boots but restarting to system makes a boot loop. I was unable to use this recovery and latest stock rom at the same time...

After first booting to TWRP, don't boot to the still unaltered stock rom. Flash Magisk before booting the stock rom to solve the bootloop. Magisk alters the rom so that it accepts modifications.

 

[saswatmeher05]

After first booting to TWRP, don't boot to the still unaltered stock rom. Flash Magisk before booting the stock rom to solve the bootloop. Magisk alters the rom so that it accepts modifications.

thanks it worked

 

[planet9]

TWRP build 2018-05-16 has been released!

This TWRP image is unified and works on the ZE520KL and ZE552KL.
Changes:

• USB now reports the proper device model.
• More F2FS kernel features.
• Updated fstab with more partitions.
• Updated device tree for oreo-mr1, built with 8.1 omni sources.
• Latest LineageOS kernel: Linux 3.18.108, CAF-Tag LA.UM.6.6.r1-08500-89xx.0.
  Thanks to @makorn645:
• Logic to detect the device model.
• Fixed serial number detection.
• Unified tree.
• Misc updates.

 

[planet9]

I want to cover data to f2fs but

mkfs.f2fs -t 0 -r 16384 /dev/block/mmcblk0p67 error :1

How to fix it ?

I try to edit recovery.fstab it's ok

The new 2018-05-16 twrp image finally offers proper F2FS support.
To format /data to F2FS follow these steps:

1. (Backup /data and your internal storage.)
2. From the TWRP main menu navigate to "Wipe"->"Advanced Wipe" and select the "Data" partition.
3. Choose "Repair or Change File System" below.
4. Select "Change File System", then choose "F2FS".
5. Swipe to format /data to F2FS. This will wipe all app data AND your internal storage!
6. (Restore the previously created backup of /data.)

You can do the same for the cache partition.

 

[lanserffnt]

Thanks

 

[DallasBelt]

After doing factory reset using twrp suddenly twrp doesn't detect touches, it only responds when pressing the lock button. Does anyone know how to fix this? Am in the latest twrp version.

Same happened to me! I thought my screen got broken! I'm trying with previous versions, but no luck so far (it gets stuck on the ASUS logo)
Did you solve the issue?

EDIT: Tried with twrp-3.2.1-Z017-20180309, but it's the same, the touch commands don't work at all. I think I'm going to redo the bootloader unlock process...

 

[Saktis_STi]

Same happened to me! I thought my screen got broken! I'm trying with previous versions, but no luck so far (it gets stuck on the ASUS logo)
Did you solve the issue?

EDIT: Tried with twrp-3.2.1-Z017-20180309, but it's the same, the touch commands don't work at all. I think I'm going to redo the bootloader unlock process...

Did you unlock unofficially?

If yes, did you flash Oreo RAW after unlocking?

 

[gamehelp16]

Same happened to me! I thought my screen got broken! I'm trying with previous versions, but no luck so far (it gets stuck on the ASUS logo)
Did you solve the issue?

EDIT: Tried with twrp-3.2.1-Z017-20180309, but it's the same, the touch commands don't work at all. I think I'm going to redo the bootloader unlock process...

I have solved the issue, if I remember correctly all I did was flashing stock oreo RAW and install TWRP again. Keep in mind that flashing stock oreo RAW deletes all data, though.

 

[abbassbhai]

can someone tell me how do we remove data encryption on our device.????
i get a encryption whenever i boot up the custom rom or twrp.
thanks.

 

[DallasBelt]

I have solved the issue, if I remember correctly all I did was flashing stock oreo RAW and install TWRP again. Keep in mind that flashing stock oreo RAW deletes all data, though.

Thank you, I did the same and now it seems that TWRP is workink properly. I was missing the flashing the RAW file part... Anyway, thanks for your help!!

---------- Post added at 03:51 PM ---------- Previous post was at 03:48 PM ----------

Did you unlock unofficially?

If yes, did you flash Oreo RAW after unlocking?

That was exactly the problem :silly: Now it's working fine, thanks for clarifying that part!

 

[kiq1702]

Someone help me for God's sake?

I've tried installing several rom's, but it always gives the same error (attachment)

rom that failed installation:
LineageOS 15.1
Ressurection Remix v6.0
Bootleggers
AOSPExtended

The only ones I can install are:
CarbonRom 8.1

I already installed the latest firmware (WW-15.0410.1804.62)
I already installed and reinstalled TWRP 3.2.1-0
I've done all Wipes (data, internal memory, cache, dalvick, system, etc ...)
I have already modified the Updater-Script file.

Always the same mistake, Can you help me?

ZE552KL Z012DC Brazil

 

[nicky-xda]

How can i flash this TWRP after unlocking the bootloader? Shall i do it in ADB? If so: which command do i have to use?

 

[Saktis_STi]

How can i flash this TWRP after unlocking the bootloader? Shall i do it in ADB? If so: which command do i have to use?

FASTBOOT mode

Tutorial:
1) Download TWRP
2) Create New Folder and put TWRP in it
3) Hold Shift & Right Click in the folder (open CMD/Powershell)
4) Enter Fastboot & connect phone to PC
5) type: fastboot flash recovery (TWRP name).img
6) type: fastboot reboot (hold volume down button)

 

[nicky-xda]

MOUNT not working?
I do not see mounted data / microSD in windows explorer and the phone does not apeear as portable device in windows device manager.

Both microSD and internal storage show up as expected when in android and connected by USB.

Why does that not work in TWRP?

 

[Saktis_STi]

MOUNT not working?
I do not see mounted data / microSD in windows explorer and the phone does not apeear as portable device in windows device manager.

Both microSD and internal storage show up as expected when in android and connected by USB.

Why does that not work in TWRP?

The latest TWRP has MTP bug. Use older build to use MTP.

 

[nicky-xda]

The latest TWRP has MTP bug. Use older build to use MTP.

I've tried several of them down to ver 3.1.1 and unfortunately never was able to connect: my device simply does not appear in the file manager.