Related
Mod info:
Method doesn't work anymore and will result in a hard brick.
Make sure you’ve backed up all of your IMPORTANT DATA before unlocking/relocking bootloader
I am not responsible for bricked devices and dead SD cards. YOU are choosing to make these modifications, and if you point the finger at me for messing up your device, I will laugh at you.
1) Download the Factory RAW ROM here:
ZE520KL: https://drive.google.com/drive/folders/11rwuLclwgwPl5W0L2L9ZQJN10beLLaER?usp=sharing
ZE552KL: https://drive.google.com/drive/folders/1D-tF9EiARrGgsYADaMRwZu02hFTdUrgZ?usp=sharing
2) Download ASUS Flash Tool here:
https://drive.google.com/drive/folders/1Zmc9L0tPbSMSkzHfmSAA_0AxzTRZffP6?usp=sharing
3) Flash the firmware via ASUS Flash Tool by entering FASTBOOT MODE (Power Off + Volume Up)
*Note: This firmware can only boot into FASTBOOT Mode. So, don’t panic
4) Download Unlock Bootloader Toolkit for ZenFone 3 here:
https://drive.google.com/drive/folders/1Fk5cu6Hk-0WaBn7OvHQ8rNPNLRaxzQKO?usp=sharing
5) Enter FASTBOOT mode (Power Off + Volume Up)
UNLOCKING
6) Unzip the files and click on
unlock_ZE520KL.bat (For ZE520KL)
unlock_ZE552KL.bat (For ZE552KL)
Congratulations, your device has been unlocked unofficially. (You can see the Bootloader status on FASTBOOT splash screen)
RELOCKING
6) Unzip the files and click on Install adb-setup-1.4.3.exe (You can find this in Bootloader Toolkit)
Hold Shift and Right Click on any area in the folder (click on ”Open Powershell window/Open Command Window)
Now copy and paste this: fastboot devices
If it shows your serial number of ZenFone 3, you are good to go
Now copy and paste this: fastboot oem lock
Congratulations, your device has been locked (You can see the Bootloader status on FASTBOOT splash screen)
P.S: If you unlocked officially and you want to relock your bootloader, OTA does not work because your Serial Number has been recorded by ASUS.
7) After that, download the stock ROM here and flash it via ASUS Flash Tool (FASTBOOT Mode):
ZE520KL: https://drive.google.com/drive/folders/1KeH2s9Vfw6lvg9pQ-1WKrwss3GbSxpNV?usp=sharing
ZE552KL: https://drive.google.com/drive/folders/1etLCGRdj6ft7e-PAi1hr5q4Gxrpq3eR1?usp=sharing
vivek2368 said:
Thanks mate
Click to expand...
Click to collapse
Don't quote the full thread.
Join our ZenFone 3 Development Telegram chat here:
MOD EDIT: LINK REMOVED
The distribution of social media links is no longer allowed on XDA. Please refer to the thread linked below:
Telegram and Whatsapp Channels - Going Forward
Saktis_Impreza said:
Make sure you’ve backed up all of your IMPORTANT DATA before unlocking/relocking bootloader
I am not responsible for bricked devices and dead SD cards. YOU are choosing to make these modifications, and if you point the finger at me for messing up your device, I will laugh at you.
1) Download the Factory RAW ROM here:
ZE520KL: https://drive.google.com/drive/folders/11rwuLclwgwPl5W0L2L9ZQJN10beLLaER?usp=sharing
ZE552KL: https://drive.google.com/drive/folders/1D-tF9EiARrGgsYADaMRwZu02hFTdUrgZ?usp=sharing
2) Download ASUS Flash Tool here:
https://drive.google.com/drive/folders/1Zmc9L0tPbSMSkzHfmSAA_0AxzTRZffP6?usp=sharing
3) Flash the firmware via ASUS Flash Tool by entering FASTBOOT MODE (Power Off + Volume Up)
*Note: This firmware can only boot into FASTBOOT Mode. So, don’t panic
4) Download Unlock Bootloader Toolkit for ZenFone 3 here:
https://drive.google.com/drive/folders/1Fk5cu6Hk-0WaBn7OvHQ8rNPNLRaxzQKO?usp=sharing
5) Enter FASTBOOT mode (Power Off + Volume Up)
UNLOCKING
6) Unzip the files and click on
unlock_ZE520KL.bat (For ZE520KL)
unlock_ZE552KL.bat (For ZE552KL)
Congratulations, your device has been unlocked unofficially. (You can see the Bootloader status on FASTBOOT splash screen)
RELOCKING
6) Unzip the files and click on Install adb-setup-1.4.3.exe (You can find this in Bootloader Toolkit)
Hold Shift and Right Click on any area in the folder (click on ”Open Powershell window/Open Command Window)
Now copy and paste this: fastboot devices
If it shows your serial number of ZenFone 3, you are good to go
Now copy and paste this: fastboot oem lock
Congratulations, your device has been locked (You can see the Bootloader status on FASTBOOT splash screen)
P.S: If you unlocked officially and you want to relock your bootloader, OTA does not work because your Serial Number has been recorded by ASUS.
7) After that, download the stock ROM here and flash it via ASUS Flash Tool (FASTBOOT Mode):
ZE520KL: https://drive.google.com/drive/folders/1KeH2s9Vfw6lvg9pQ-1WKrwss3GbSxpNV?usp=sharing
ZE552KL: https://drive.google.com/drive/folders/1etLCGRdj6ft7e-PAi1hr5q4Gxrpq3eR1?usp=sharing
Click to expand...
Click to collapse
Thanks!
if i unlock bootloader then relock it, will i get ota or not? thanks
indunrise said:
if i unlock bootloader then relock it, will i get ota or not? thanks
Click to expand...
Click to collapse
You will get OTAs if you follow my steps
I just tried this method and it definitely works! Unlocked my device and currently updating via OTA.
- FORGET -
Bootloader locked now for me i confirm no ota
rafik25 said:
Bootloader locked now for me i confirm no ota
Click to expand...
Click to collapse
Did you unlock officially or in unofficial method?
Can this method used in Oreo... ?
I just bought this device, and last night updated to oreo.
tkhquang said:
Did you unlocked officially or in unofficial method?
Click to expand...
Click to collapse
Unlocked last year with officially method
rafik25 said:
Unlocked last year with officially method
Click to expand...
Click to collapse
Yeah, that was stated in the thread already. I unlocked my phone officially as well, sadly
P.S: If you unlocked officially and you want to relock your bootloader, OTA does not work because your Serial Number has been recorded by ASUS.
Click to expand...
Click to collapse
-Deleted_
7) After that, download the stock ROM here and flash it via ASUS Flash Tool (FASTBOOT Mode):
Click to expand...
Click to collapse
So I went through this steps, and seems to work well so far. But when I went to update using the flash tool, the tool itself told me there was a newer version of the raw firmware, more specifically the
WW_ZE520KL_15.0410.1712.31_M3.10.47.16_Phone-user.raw
So I googled, and found it for download here:
https://androidfilehost.com/?fid=746010030569949679
Meaning that one can go straight to Oreo, instead of upgrading over and over.
Edit: Just tested, and it works! Got oreo straight!
---------- Post added 2nd February 2018 at 12:08 AM ---------- Previous post was 1st February 2018 at 11:10 PM ----------
RELOCKING
6) Unzip the files and click on Install adb-setup-1.4.3.exe (You can find this in Bootloader Toolkit)
Hold Shift and Right Click on any area in the folder (click on ”Open Powershell window/Open Command Window)
Now copy and paste this: fastboot devices
If it shows your serial number of ZenFone 3, you are good to go
Now copy and paste this: fastboot oem lock
Congratulations, your device has been locked (You can see the Bootloader status on FASTBOOT splash screen)
Click to expand...
Click to collapse
I did not understand one detail about locking the phone. I got that it is only possible to lock/unlock once you have installed the factory_raw image. Ok.
So I wanted to lock my phone and then install the latest WW_ZE520KL_15.0410.1712.31_M3.10.47.16_Phone-user.raw. In this case the Asus flash tool gives an error saying that your phone is locked and can not install the image.
At the same time, if I install the image, and then try to lock it it is too late, since the lock command wont work anymore...
So, after all, what should I do to lock it and get the OS installed afterwards?
Ok, I figured it out.
So you can actually LOCK it, and then install the WW_ZE520KL_15.0410.1712.31_M3.10.47.16_Phone-user.raw. However, after the phone reboots, the Asus Flash program will try to erase it from the fastboot, which it cant, so it gives an error message.
So one has to go to recovery mode, and wipe and format partitions manually before it can actually boot.
joaofl said:
Ok, I figured it out.
So you can actually LOCK it, and then install the WW_ZE520KL_15.0410.1712.31_M3.10.47.16_Phone-user.raw. However, after the phone reboots, the Asus Flash program will try to erase it from the fastboot, which it cant, so it gives an error message.
So one has to go to recovery mode, and wipe and format partitions manually before it can actually boot.
Click to expand...
Click to collapse
What error message are you receiving? (Boot image still persist or something). If you receive that, it is not a problem. Just follow my thread
---------- Post added at 04:59 AM ---------- Previous post was at 04:52 AM ----------
Join our ZenFone 3 Development Telegram chat here:
MOD EDIT: LINK REMOVED
The distribution of social media links is no longer allowed on XDA. Please refer to the thread linked below:
Telegram and Whatsapp Channels - Going Forward
ZenFone_3 said:
What error message are you receiving? (Boot image still persist or something). If you receive that, it is not a problem. Just follow my thread
Click to expand...
Click to collapse
The error was because the Asus Flash tool was trying to wipe the memory after rebooting in fasboot mode, which It was unable to do. So one have to boot in recovery mode to wipe manually so it can boot.
(I've dropped the link to the oreo user raw image. Maybe it is worth putting it in the main post)
joaofl said:
The error was because the Asus Flash tool was trying to wipe the memory after rebooting in fasboot mode, which It was unable to do. So one have to boot in recovery mode to wipe manually so it can boot.
(I've dropped the link to the oreo user raw image. Maybe it is worth putting it in the main post)
Click to expand...
Click to collapse
That doesn't matter, If ASUS Flash Tool gives error such as Error 5 (FRP error) / Flash image still persist, ignore it. If your phone asks for PIN and it's incorrect, Enter recovery mode and wipe data and cache.
The reason why I don't suggest users to flash Oreo directly is because RIL might not work.
Edit: You can flash directly to 15.0410.1712.31 RAW firmware
Hi !
I had follow this thread https://forum.xda-developers.com/nokia-3/how-to/guide-how-to-flash-twrp-magisk-t3785768
and I had install TWRP but now when i try to start my phone,I can access to TWRP and fastboot but I can't access to the system.
My Nokia 3 freeze on "Powered by Android - Orange state -Your device has been unlocked and can't be trusted - Your device will boot in 5 seconds"
------
Nokia 3 - 1032 / Dowgraded to 7.0
Somebody help me plz ! :fingers-crossed:
>Taps< said:
Hi !
I had follow this thread https://forum.xda-developers.com/nokia-3/how-to/guide-how-to-flash-twrp-magisk-t3785768
and I had install TWRP but now when i try to start my phone,I can access to TWRP and fastboot but I can't access to the system.
My Nokia 3 freeze on "Powered by Android - Orange state -Your device has been unlocked and can't be trusted - Your device will boot in 5 seconds"
------
Nokia 3 - 1032 / Dowgraded to 7.0
Somebody help me plz ! :fingers-crossed:
Click to expand...
Click to collapse
Did you unlocked your bootloader and after that did you flash TWRP without reboot?
Maybe I'm wrong but when you unlock your bootloader, the phone automatically reboots into stock recovery and and immediately wipe everything (included your internal storage) and then reboots normally. If you flashed TWRP after unlocking your bootloader, your phone will boot into TWRP but it won't wipe anything.
I think that happened.
Isrks said:
Did you unlocked your bootloader and after that did you flash TWRP without reboot?
Maybe I'm wrong but when you unlock your bootloader, the phone automatically reboots into stock recovery and and immediately wipe everything (included your internal storage) and then reboots normally. If you flashed TWRP after unlocking your bootloader, your phone will boot into TWRP but it won't wipe anything.
I think that happened.
Click to expand...
Click to collapse
Mmh after I unlocked the bootloader, my phone was freeze on this
Select Boot Mode :
[VOLUME_UP to select. VOLUME DOWN is OK]
[Recovery Mode]
[Fastboot Mode] <<==
[Normal Mode]
=> FASTBOOT mode.....
So, I forced it to reboot, after everything seems ok.
What part must I reflash ?
>Taps< said:
Mmh after I unlocked the bootloader, my phone was freeze on this
Select Boot Mode :
[VOLUME_UP to select. VOLUME DOWN is OK]
[Recovery Mode]
[Fastboot Mode] <<==
[Normal Mode]
=> FASTBOOT mode.....
So, I forced it to reboot, after everything seems ok.
What part must I reflash ?
Click to expand...
Click to collapse
When I unlocked the bootloader my phone freezed too, so I typed in Windows cmd "fastboot reboot". After that, my phone was formatted by stock recovery.
You should reflash stock recovery if you have TWRP, so the stock recovery can format your internal storage, if not, your phone won't boot.
:fingers-crossed:
Isrks said:
When I unlocked the bootloader my phone freezed too, so I typed in Windows cmd "fastboot reboot". After that, my phone was formatted by stock recovery.
You should reflash stock recovery if you have TWRP, so the stock recovery can format your internal storage, if not, your phone won't boot.
:fingers-crossed:
Click to expand...
Click to collapse
Ok, so fastboot didn't work at all (just waiting devices)
I tried to reflash TWRP nothing happens, I tried to do a factory wipe with twrp but nothing happens too.
I searched a stock recovery for nokia 3 1032- Android 7.0 but found nothing - must i use stock recovery for Android 7.1.1 or do you have a link to a stock recovery for 7.0 ?
------------
I found this on XDA : Is it a good way if nothing work ?
Hi, I was able to unbricked my phone using this:
"https://mega.nz/#F!0lMBiIIYgB!c9TeOWFrKpf0XfOwXzunrg"
Here is the SP Flash tool, the download agent for Nokia's phones and the ROM unpacked
As SkaboXD said (i don't know if it were in this post or in other one) you must:
1- Download the files I provided you
2- Install SP Flash Tool
3- Choose the download agent
4- Choose the scatter
5- Press download and plug your phone (it must be OFF)
6- Wait and enjoy.
I must thank to everyone who give us this files. I couldn't unbricked my phone without your help
Click to expand...
Click to collapse
>Taps< said:
Ok, so fastboot didn't work at all (just waiting devices)
I tried to reflash TWRP nothing happens, I tried to do a factory wipe with twrp but nothing happens too.
I searched a stock recovery for nokia 3 1032- Android 7.0 but found nothing - must i use stock recovery for Android 7.1.1 or do you have a link to a stock recovery for 7.0 ?
------------
I found this on XDA : Is it a good way if nothing work ?
Click to expand...
Click to collapse
I think that this is the link:
https://forum.xda-developers.com/nokia-3/help/nokia-3-preloader-bricked-t3719357/post76069467#post76069467
I used SP flash tools to downgrade and install TWRP in my phone.
Which tool did you use to downgrade your phone?
Isrks said:
I think that this is the link:
https://forum.xda-developers.com/nokia-3/help/nokia-3-preloader-bricked-t3719357/post76069467#post76069467
I used SP flash tools to downgrade and install TWRP in my phone.
Which tool did you use to downgrade your phone?
Click to expand...
Click to collapse
Ok thanks :fingers-crossed:, I will try it
To downgrade I used OST LA and to flash TWRP I used SP flash tools
>Taps< said:
Ok thanks :fingers-crossed:, I will try it
To downgrade I used OST LA and to flash TWRP I used SP flash tools
Click to expand...
Click to collapse
Good luck. :fingers-crossed:
You can flash again with OST LA. Or try to flash with SP flash tool the whole rom or just the recovery. To flash with SP flash tools you need a nb0 unpacker tool (my previous post have a link to another post with the tool link).
BTW feel free to ask something that you don't understand. :highfive:
Isrks said:
Good luck. :fingers-crossed:
You can flash again with OST LA. Or try to flash with SP flash tool the whole rom or just the recovery. To flash with SP flash tools you need a nb0 unpacker tool (my previous post have a link to another post with the tool link).
BTW feel free to ask something that you don't understand. :highfive:
Click to expand...
Click to collapse
Heyyyyy !!! Thank you !!!
It works again :victory: !!!
I used OST LA to reflash it !!! Thanks again <3
I think I will use the second alternative step to not get a brick bootloader ^^' https://forum.xda-developers.com/nokia-3/how-to/guide-how-to-flash-twrp-magisk-t3785768
----------
Do you know the safest way to relock the bootloader ?
>Taps< said:
I think I will use the second alternative step to not get a brick bootloader ^^' https://forum.xda-developers.com/nokia-3/how-to/guide-how-to-flash-twrp-magisk-t3785768
----------
Do you know the safest way to relock the bootloader ?
Click to expand...
Click to collapse
Is like unlock bootloader, just change "fastboot oem unlock" to "fastboot oem lock".
But your internal storage will be formatted again by stock recovery, so you must have stock recovery installed.
After relock, your device will get ota updates, so you need stock recovery to install them.
I recommend root your device after all the updates, even you can install TWRP without problems.
I installed TWRP, root and installed stock recovery to get updates. Choose the method that you like.
Good luck. :highfive:
Team Win Recovery Project For Zenfone Max Pro M2
WARNING:
Code:
I am not responsible for bricked devices, dead SD cards,
thermonuclear war, or you getting fired because the alarm app failed. Please
do some research if you have any concerns about features included in this Kernel
before flashing it! YOU are choosing to make these modifications, and if
you point the finger at me for messing up your device, I will laugh at you.
Downloads: recovery-X01BD.img
Installation Instructions:
Install fastboot tools from google's sdk on your PC
Enter fastboot mode
Unlock your bootloader
Run "fastboot flash recovery imgfilename.img" in command line
Reboot and enjoy it
Credits:
TeamWin Team and @Dees_Troy - For Creating TWRP!!!
Thanks to #ArtFul for testing the recovery.
Sources : https://github.com/rk779/android_device_asus_X01BD
XDA:DevDB Information
TWRP Recovery, Tool/Utility for the Asus Zenfone Max Pro M2
Contributors
Rk585
Version Information
Status: Stable
Created 2019-01-03
Last Updated 2019-01-03
:3
Thx
Is device encryption issue still on this one ?
finally the most awaited day has come. Thank
Awesome Thanks so much... But I am new to unlocking bootloaders ... Never had to do it since I had a Samsung device before...
Can you please give us some instructions on how to unlock the bootloader on this device ?
And is it possible to relock the bootloader ? (So as to not void the warranty)
Tyakrish said:
Awesome Thanks so much... But I am new to unlocking bootloaders ... Never had to do it since I had a Samsung device before...
Can you please give us some instructions on how to unlock the bootloader on this device ?
And is it possible to relock the bootloader ? (So as to not void the warranty)
Click to expand...
Click to collapse
Look in the themes mods and apps section of the thread. The bootloader unlock method is posted there. Method for relocking the BL is also provided along with it.
Thanks @Rk585!
Nice to see the development has kick-started!
Which magisk version we have to installed and how to relock or get back to stock recovery again?
not working on my device. I flashed the twrp and it says it succeed. Then i turned off my device. after that i pressed vol down + power button but intead of booting into twrp it boots into stock recovery. i tried to flash recovery more than 2-3 times. I dont understand what is wrong here.
boosters said:
Which magisk version we have to installed and how to relock or get back to stock recovery again?
Click to expand...
Click to collapse
Always use the latest magisk
Here are the links for unlock and relock
https://forum.xda-developers.com/max-pro-m2/how-to/unlook-bootloader-root-asus-zenfone-max-t3885457
https://forum.xda-developers.com/max-pro-m2/how-to/unroot-relock-bootloader-max-pro-m2-t3885870
Karvrock said:
not working on my device. I flashed the twrp and it says it succeed. Then i turned off my device. after that i pressed vol down + power button but intead of booting into twrp it boots into stock recovery. i tried to flash recovery more than 2-3 times. I dont understand what is wrong here.
Click to expand...
Click to collapse
After flashing twrp, try fastboot reboot recovery
Sorry, this version is suitable for Asus_X01BDA?
kuchivas said:
Sorry, this version is suitable for Asus_X01BDA?
Click to expand...
Click to collapse
Yeah.. its compatible.. I'm just installed it yesterday n try treble rom..?
X10MINISTER said:
Yeah.. its compatible.. I'm just installed it yesterday n try treble rom..?
Click to expand...
Click to collapse
Thanks so much!
ok I look through the instruction, just some question:
1. can I flash the TWRP without unlocking the bootloader?
2. from the unlock bootloader thread, upon unlocking the phone the phone will be formatted, any way to prevent that so I can do a full backup of the system? It is a real pain to reinstall everything.
learnyee said:
ok I look through the instruction, just some question:
1. can I flash the TWRP without unlocking the bootloader?
2. from the unlock bootloader thread, upon unlocking the phone the phone will be formatted, any way to prevent that so I can do a full backup of the system? It is a real pain to reinstall everything.
Click to expand...
Click to collapse
1. No
2. No, the phone will be formatted. All you can do is, backup your internal storage data
#ArtFuL said:
1. No
2. No, the phone will be formatted. All you can do is, backup your internal storage data
Click to expand...
Click to collapse
No 2. using ADB backup? or any other way that would cut down the re installation of everything?
learnyee said:
No 2. using ADB backup? or any other way that would cut down the re installation of everything?
Click to expand...
Click to collapse
You may use this adb command to backup data
Code:
adb backup [-f <file>] [-apk|-noapk] [-obb|-noobb] [-shared|-noshared] [-all] [-system|nosystem] [<packages...>]
-f : the path of the *.ab file that will be saved on your computer. This file is a compressed file that contains an archive of the data/apks from your device.
-apk|-noapk : indicates if the *.apk files should be backed up (default is -noapk)
-obb|-noobb : enable/disable backup of any installed apk expansion (aka .obb) files associated with each application (default is -noobb)
-shared|-noshared: enable/disable backup of the device's shared storage / SD card contents (default is -noshared)
-all : indicates that you want the entire system backed up. you can use the packages filter to just backup specific packages, or use -all for a full system backup.
-system|-nosystem: indicates if all the system applications and data are included when backing up. (default is -system)
<packages> : this is where you can list specific packages to backup. Use these if you want to back up only specific applications. If using -all, you do not need to specify packages.
This will not backup contacts or sms
and to restore
Code:
adb restore [<name of backup>.ab]
Or this might help you http://forum.xda-developers.com/showthread.php?p=36499906
Thank god u have this device i have just came from leeco le 2 x526 to this device
Karvrock said:
not working on my device. I flashed the twrp and it says it succeed. Then i turned off my device. after that i pressed vol down + power button but intead of booting into twrp it boots into stock recovery. i tried to flash recovery more than 2-3 times. I dont understand what is wrong here.
Click to expand...
Click to collapse
i had this problem too.. anyone can solve this problem,
What is a brick?If there is no usual way to recover your mobile, then it is called brick in my opinion. That means if you can't able to go to recovery and fastboot mode or the device is just blank with no sign of life.
When brick happens?It will happen because of locking bootloader with custom images or just because of Mediatek/Realme strange behaviour.
What we have to do if brick happens?Simply we have to flash stock firmware with Smart Phone Flash Tool(aka SPFlash Tool). With only SPFlash Tool we can't do anything, since we don't have permission for it. But with the advent of MTK-bypass, we can have full control over our device. If we don't have this MTK-bypass, then we have search for costly alternative's.
You can't flash only if your eMMC is damaged, which is the worst case because oppo phones are prone to eMMC failure.
Click to expand...
Click to collapse
Where to get firmware to flash?Download decrypted .ofp firmware from https://drive.google.com/file/d/1SOmRxix9_UtjOLLanXPYxf4YK1NrA_RW/view
Thanks to @bx2_nero for it.
What is the procedure for using MTK-bypass and SPFlashTool?MTK-bypass is a Python script and it needs different USB ways for working. So with these two in place, we can get our work done.
Linux UsersFor Linux we have to use FireISO or patched kernels for working of MTK-bypass.
Use the Linux guide by @bx2_nero at https://forum.xda-developers.com/t/...our-realme-6-6i-india-6s-linux-method.4251077
Windows UsersFor Windows we have to use libusb32 filter for MTK-bypass working.
Use the guide by @daeSundae at https://forum.xda-developers.com/t/...india-6s-using-spflash-tool-for-free.4222027/
MTK-bypass Official instructionsSee Github ReadMe at https://github.com/MTK-bypass/bypass_utility and XDA support thread at https://forum.xda-developers.com/t/mod-dev-mediatek-mtk-auth-bypass-sla-daa-utility.4232377/
Creditsxyzz / xyz`: GitHub | XDA
chaosmaster / k4y0z: GitHub | XDA
Dinolek: GitHub | XDA
References- https://forum.hovatek.com/thread-37957.html
- https://www.xda-developers.com/bypass-mediatek-sp-flash-tool-authentication-requirement/
- https://forum.xda-developers.com/t/repair-dead-hard-bricked-realme-3-3i-tutorial.4224255/
- https://forum.xda-developers.com/t/...d-flash-in-edl-with-no-auth-for-free.4229683/
- https://forum.xda-developers.com/t/...ash-tool-authentication.4236881/post-84627359
MTKClient
After MTK-bypass got success, @viperbjk who is a reverse engineer came up with a FOSS replacement of SP Flash Tool.
MTKClient combines MTK-bypass and SP Flash Tool together and with many improvements and new features.
Ability to flash partitions without Scatter file
Ability to Readback partitions without specifying address and length
Ability to Format partitions without specifying address and length
Run multiple commands without reconnecting the device
Flash protected partitions(opporeserve2, special_preload, my_custom and cdt_engineering) with locked bootloader
Unlock bootloader without need of in-depth test/Deep testing app from Realme
GitHub - bkerler/mtkclient: MTK reverse engineering and flash tool
MTK reverse engineering and flash tool. Contribute to bkerler/mtkclient development by creating an account on GitHub.
www.github.com
Reserved
I need help, my C12 is stuck on fastboot mode. This happened after flashing a GSI using TWRP and flashing the image in the Super (System and Vendor) partition.
I tried rebooting to recovery mode by executing fastboot reboot recovery but it says that bootloader is not known.
I also tried to flash a GSI (taught it might fix the problem) using fastboot flash system system.img but it says that no partition named system exists.
Please suggest what I should do.
Bro, can you make a video about this? my realme c12 got hardbricked after I flashed ozip file from stock recovery while bootloader is unlocked. it got hardbricked when I reboot it after flashing ozip
DFM23 said:
Bro, can you make a video about this? my realme c12 got hardbricked after I flashed ozip file from stock recovery while bootloader is unlocked. it got hardbricked when I reboot it after flashing ozip
Click to expand...
Click to collapse
What is the present state of the device? Can you able to boot to fastboot mode?
HemanthJabalpuri said:
What is the present state of the device? Can you able to boot to fastboot mode?
Click to expand...
Click to collapse
it has no sign of life, cant go to recovery or fastboot. when I connect it to pc it goes connect and disconnected.
How can I reboot to recovery mode when in fastboot mode? The command fastboot reboot recovery is not working for me.
youcancallmekhen said:
How can I reboot to recovery mode when in fastboot mode? The command fastboot reboot recovery is not working for me.
Click to expand...
Click to collapse
Use latest platform tools
youcancallmekhen said:
How can I reboot to recovery mode when in fastboot mode? The command fastboot reboot recovery is not working for me.
Click to expand...
Click to collapse
HemanthJabalpuri said:
Use latest platform tools
Click to expand...
Click to collapse
Sir I've finally able to reboot to recovery. I've tried flashing the OZIP file for my model but after some time it says Installation failed. When I was still using custom recovery, I wasn't able to mount System and Vendor. My bootloader is also unlocked sir.
Should I lock my bootloader sir?
youcancallmekhen said:
Should I lock my bootloader sir?
Click to expand...
Click to collapse
Don't lock bootloader.
Download this https://drive.google.com/file/d/1jLdDz7M0G_KPDn4jXjTeuFnO1C-MFaBs/view (It is from A.87 UI 1.0 Stock ROM)
Extract above 7z file and flash ONLY super partition from it and TWRP from https://androidfilehost.com/?fid=7161016148664807816 with below commands
Code:
fastboot -w
fastboot flash super super.img
fastboot flash recovery TWRP.img
fastboot reboot recovery
Now enable 'Skip Treble Compatibility error' in TWRP settings and flash stock ROM .ozip in TWRP.
Thanks
HemanthJabalpuri said:
Don't lock bootloader.
Download this https://sourceforge.net/projects/realmec11/files/Fastboot-ROM/[email protected]/download
Extract above 7z file and flash ONLY super partition from it with below commands
Code:
fastboot -w
fastboot flash super super.img
fastboot flash recovery stock-recovery.img
fastboot reboot recovery
Now flash stock ROM .ozip in stock recovery.
Thanks
Click to expand...
Click to collapse
Oh my, thank you so much sir. You have no idea how much you are helping me sir! My parents will be so happy, and we won't waste money… Thank you so much sir…
I'll update you sir after doing these, thank you sir! ♥
HemanthJabalpuri said:
Don't lock bootloader.
Download this https://sourceforge.net/projects/realmec11/files/Fastboot-ROM/[email protected]/download
Extract above 7z file and flash ONLY super partition from it with below commands
Code:
fastboot -w
fastboot flash super super.img
fastboot flash recovery stock-recovery.img
fastboot reboot recovery
Now flash stock ROM .ozip in stock recovery.
Thanks
Click to expand...
Click to collapse
I don't have much data left today sir, so I will download this later. Thank you very much again sir, you're my hero!
DFM23 said:
it has no sign of life, cant go to recovery or fastboot. when I connect it to pc it goes connect and disconnected.
Click to expand...
Click to collapse
Follow the guide and you can get your mobile back to life.
Thanks
HemanthJabalpuri said:
Follow the guide and you can get your mobile back to life.
Thanks
Click to expand...
Click to collapse
thank you bro, Ill follow your guide then. btw does the RMX2185 firmware you provided works with realme c12? I look it up and saw that it was for realme c11
DFM23 said:
thank you bro, Ill follow your guide then. btw does the RMX2185 firmware you provided works with realme c12? I look it up and saw that it was for realme c11
Click to expand...
Click to collapse
Yes, both use same firmware.
I tried the guide but when I click download on sp flash tool it would stay in red bar for 1 min or more then message will appear saying STATUS_EXT_RAM_EXCEPTION. I have read a same comment here in xda about realme c12 I dont know if its only on realme c12.
Thanks for your works sir, you are super awesome!
I rooted My Device (Realme X2 Pro) by Magisk. And Since My Device Bootloader was unlocked I Unrooted/Uninstalled MAgisk.
While Locking Bootloader My Device is Stuck where It displays { The Current Image (boot/recovery) have been destroyed dand cannot boot. Please flash the correct Image or Contact Customer Service to fix it }
While Trying to ENter the Fast Boot Mode {By pressing Volume + - and Power Button} Its Unresponsive
It shows Realme Logo And chrging Display for a Instant
Do you Know any way around to fix my Problem?
Bhuprab said:
I rooted My Device (Realme X2 Pro) by Magisk. And Since My Device Bootloader was unlocked I Unrooted/Uninstalled MAgisk.
While Locking Bootloader My Device is Stuck where It displays { The Current Image (boot/recovery) have been destroyed dand cannot boot. Please flash the correct Image or Contact Customer Service to fix it }
While Trying to ENter the Fast Boot Mode {By pressing Volume + - and Power Button} Its Unresponsive
It shows Realme Logo And chrging Display for a Instant
Do you Know any way around to fix my Problem?
Click to expand...
Click to collapse
Since your device is Qualcomm, I don't know. In any device, we have to flash stock rom (or atleast the partitions that are modified) to get device in working state.
You may get better help at https://forum.xda-developers.com/f/realme-x2-pro-questions-answers.9439/
Thanks
Asus rog phone 5 guide
note: you follow this guide on your own responsibility. also You should note that unlocking via the official Asus app will void warranty and blacklist the device for future otas.
bootloader unlock:
! note that unlocking the bootloader will erase the phone, back up your data before starting !
- install asus unlock application from asus website (direct link)
- open the app, scroll to the bottom accept the user agreement
-scroll to the bottom, click on agree. enter your pin
- your phone should now reboot and you should see the warning message indicating that you have unlocked bootloader
! now if you don't see the warning screen and your phone was not formatted, this means this unlock method didn't work and you should seek other methods !
updating to the latest ww firmware
- download the latest firmware zip from asus website (direct link) to Version WW-18.0830.2101.86.
-move the .zip file to your main storage directory.
the phone should detect the update file, if it doesn't reboot your device and it should detect it.
after updating, set up your device, then install magisk app (download link)
extract the boot.img from the above software downloaded from asus, using payload dumper (google it).
then copy the extracted boot.img to your phone.
install magisk.
open magisk
click install.
choose patch boot.img
once the patch is completed, copy the patched boot.img to you pc
for further info, magisk patching guide
on your PC you need to install your device drivers, and ADB & fastboot. and enable usb debugging on your device
flashing patched boot image
- open adb, approve the request on your device
- enter the command
Code:
adb devices
you should see your device and authorized. if not find a guide how to access your device
-next reboot to bootloader using the command
Code:
adb reboot bootloader
- in bootloader flash the boot.img from above using the following command
Code:
fastboot flash boot boot.img
where boot image should be the address to the location of your boot image.
if you boot image is on your D:/ drive and in a folder called rootstuff.
your command should look like this.
Code:
fastboot flash boot D:\rootstuff\boot.img
once you flash the patched boot.img, reboot your phone.
open magisk app, check your root status you should be rooted.
congratulations
Check pm's.
m8822 said:
- open the app, scroll to the bottom accept the user agreement
-scroll to the bottom, click on agree. enter your pin
- your phone should now reboot and you should see the warning message indicating that you have unlocked bootloader
Click to expand...
Click to collapse
hello and thank you very much for the detailed guide.
i was ready to do all that, i always unlock and root my devices so i'm savvy just enough to try, or so i thought.
after using asus unlock tool and rebooting, my phone ended up showing the indicated warning message but proceeded in a bootloop which is not generally a great problem, you can always flash partitions with fastboot !
But in my case the phone doesn't get recognised by "fastboot devices" command in bootloader mode nor in fastbootd (yes i have the latest adb & fastboot package installed with the latest platform tools)
so now i've got a very espensive and fancy paper holder.
if any of you encountered the same problem or maybe knows a way to get the device to be recognised by my pc I'll be very happy to donate for your trouble.
i already downloaded the latest firmware and extracted it with payload_dumper.py.
thank you very much to any of you who will take time to look into my issue.
also may i suggest adding a step to your guide ?
before flashing boot.img it might be a good idea to try it first using
Code:
Fastboot boot boot.img
i've had problems in the past with some bad patched boot.img images and this may be a way to avoid problems.
sorry if this sound patronising. just wanted to help
sabnack said:
also may i suggest adding a step to your guide ?
before flashing boot.img it might be a good idea to try it first using
Code:
Fastboot boot boot.img
i've had problems in the past with some bad patched boot.img images and this may be a way to avoid problems.
sorry if this sound patronising. just wanted to help
Click to expand...
Click to collapse
Thanks, is your currently rooted now? I tried module "Fullscreen/Immersive Gesture" to hide the annoying,ugly gesture indicator (thank Apple & Google for great idea). All worked except gesture swipe up from bottom to open desktop. Do you know any module to hide that pill
hilary trump said:
Do you know any module to hide that pill
Click to expand...
Click to collapse
I'm sorry i don't know but i will gladly look into that issue as soon as i can boot my phone, currently i'm stuck in a bootlop and my phone doesn't get recognised. i put all my hopes in the unbrick tool at this point, whenever it will be out.
I will let you know
hilary trump said:
Thanks, is your currently rooted now? I tried module "Fullscreen/Immersive Gesture" to hide the annoying,ugly gesture indicator (thank Apple & Google for great idea). All worked except gesture swipe up from bottom to open desktop. Do you know any module to hide that pill
Click to expand...
Click to collapse
the root guide worked on another rog 5, however mine is completely nricked and i myslef is waaiting for unbrick tools
sabnack said:
hello and thank you very much for the detailed guide.
i was ready to do all that, i always unlock and root my devices so i'm savvy just enough to try, or so i thought.
after using asus unlock tool and rebooting, my phone ended up showing the indicated warning message but proceeded in a bootloop which is not generally a great problem, you can always flash partitions with fastboot !
But in my case the phone doesn't get recognised by "fastboot devices" command in bootloader mode nor in fastbootd (yes i have the latest adb & fastboot package installed with the latest platform tools)
so now i've got a very espensive and fancy paper holder.
if any of you encountered the same problem or maybe knows a way to get the device to be recognised by my pc I'll be very happy to donate for your trouble.
i already downloaded the latest firmware and extracted it with payload_dumper.py.
thank you very much to any of you who will take time to look into my issue.
Click to expand...
Click to collapse
Connect your phone with the side port it will work.
sorankira said:
Connect your phone with the side port it will work.
Click to expand...
Click to collapse
yes it did work, i flashed every partition and now i'm locked again, recovery doesn't work, could you please dump yours and post it ? hope i'm not asking too much.
EDIT: nevermind i finally solved it, i flashed a raw img of the system, it works now, thanks for your time
m8822 said:
Asus rog phone 5 guide
note: you follow this guide on your own responsibility. also You should note that unlocking via the official Asus app will void warranty and blacklist the device for future otas.
bootloader unlock:
! note that unlocking the bootloader will erase the phone, back up your data before starting !
- install asus unlock application from asus website (direct link)
- open the app, scroll to the bottom accept the user agreement
-scroll to the bottom, click on agree. enter your pin
- your phone should now reboot and you should see the warning message indicating that you have unlocked bootloader
! now if you don't see the warning screen and your phone was not formatted, this means this unlock method didn't work and you should seek other methods !
updating to the latest ww firmware
- download the latest firmware zip from asus website (direct link) to Version WW-18.0830.2101.86.
-move the .zip file to your main storage directory.
the phone should detect the update file, if it doesn't reboot your device and it should detect it.
after updating, set up your device, then install magisk app (download link)
extract the boot.img from the above software downloaded from asus, using payload dumper (google it).
then copy the extracted boot.img to your phone.
install magisk.
open magisk
click install.
choose patch boot.img
once the patch is completed, copy the patched boot.img to you pc
for further info, magisk patching guide
on your PC you need to install your device drivers, and ADB & fastboot. and enable usb debugging on your device
flashing patched boot image
- open adb, approve the request on your device
- enter the command
Code:
adb devices
you should see your device and authorized. if not find a guide how to access your device
-next reboot to bootloader using the command
Code:
adb reboot bootloader
- in bootloader flash the boot.img from above using the following command
Code:
fastboot flash boot boot.img
where boot image should be the address to the location of your boot image.
if you boot image is on your D:/ drive and in a folder called rootstuff.
your command should look like this.
Code:
fastboot flash boot D:\rootstuff\boot.img
once you flash the patched boot.img, reboot your phone.
open magisk app, check your root status you should be rooted.
congratulations
Click to expand...
Click to collapse
Mine causes bootloop
sorankira said:
Mine causes bootloop
Click to expand...
Click to collapse
What ? Why!
what happened? Did you get this after unlocking the bootloader or after boot.img?
My troubkeshooting will consiste of flashing raw, but i am not sure if that will lock your bootloader
sorankira said:
Mine causes bootloop
Click to expand...
Click to collapse
can you enter recovery and fastbootd ? if you only get access to bootloader, flashing a raw image does work !
then you can apply ota update zips from booted android and subsequently patch boot.img extracted from payload.bin from the ota update.
worked for me and i thought i bricked my device. let us know if we can do something to help.
sabnack said:
can you enter recovery and fastbootd ? if you only get access to bootloader, flashing a raw image does work !
then you can apply ota update zips from booted android and subsequently patch boot.img extracted from payload.bin from the ota update.
worked for me and i thought i bricked my device. let us know if we can do something to help.
Click to expand...
Click to collapse
I fixed the bootloop but without root access
sorankira said:
I fixed the bootloop but without root access
Click to expand...
Click to collapse
i believe you already have version WW-18.0830.2101.86 for WW only ( i just checked, i believe it was you who posted it here ). you can use this guide to extract boot.img from the payload.bin from the "UL-ASUS_I005_1-ASUS-18.0830.2101.81-1.1.64-user.zip" then if you continue by following the guide at the top of this thread you will be rooted in 15 minutes at most.
sabnack said:
i believe you already have version WW-18.0830.2101.86 for WW only ( i just checked, i believe it was you who posted it here ). you can use this guide to extract boot.img from the payload.bin from the "UL-ASUS_I005_1-ASUS-18.0830.2101.81-1.1.64-user.zip" then if you continue by following the guide at the top of this thread you will be rooted in 15 minutes at most.
Click to expand...
Click to collapse
Yes i used this method, and causes bootloop sadly.
sorankira said:
Yes i used this method, and causes bootloop sadly.
Click to expand...
Click to collapse
oh ! dammit it's weird... you could try to patch the boot image with another phone.
or maybe the update file isn't right for your phone. i don't get it
Somebody successfully succeeded with the bootloader & Rooting this Asus ROG 5 phone?
my experience rooting was as follows:
I bought the rog phone 5 I005DA in china, in which the store changed the rom CN to WW version WW-18.0830.2101.86 and blocked the bootloader.
When my hands arrived I updated the firmware to WW-18.0840.2103.26 (the last one available).
I followed all the steps in this post and I was successful with root.
(Attention, extract the boot.img from the firmware that you currently have installed on the phone)
miguel.jackass said:
my experience rooting was as follows:
I bought the rog phone 5 I005DA in china, in which the store changed the rom CN to WW version WW-18.0830.2101.86 and blocked the bootloader.
When my hands arrived I updated the firmware to WW-18.0840.2103.26 (the last one available).
I followed all the steps in this post and I was successful with root.
(Attention, extract the boot.img from the firmware that you currently have installed on the phone)
Click to expand...
Click to collapse
how did you open the bootloader? using asus app?
because it did not work before i rooted i was on 2101.86 at the time. i tried goind down to 2100.95 also did not work.
i had to rent a guy to do it via edl. which he is not sharing the method because he wants to make money
m8822 said:
how did you open the bootloader? using asus app?
because it did not work before i rooted i was on 2101.86 at the time. i tried goind down to 2100.95 also did not work.
i had to rent a guy to do it via edl. which he is not sharing the method because he wants to make money
Click to expand...
Click to collapse
I updated the firmware to the latest official version, extract the boot.img from the last official firmware, and installed the official unlock tool from the ASUS website, I just had to follow the tutorial.