TO CONTENT FARMS ESPECIALLY GETDROIDTIPS: DO NOT REPOST THIS TOPIC ON YOUR WEBSITE!
点击这里查看中文版(Click here for Chinese Version Guide)
Click to expand...
Click to collapse
If you're looking for how to unbrick the phone that received May 2023 Security Update, you've come to the right place.
You have two options to unbrick your Nokia 8.3
If you prefer not to unlock the bootloader, visit here:
[GUIDE] How to Unbrick Nokia 8.3 affected by May 2023 Security Patch
As I mentioned before, unlocking the bootloader will fix this issue. But if you don't want to unlock the bootloader, then this guide is for you. DO NOT USE THIS METHOD IF JUNE 2023 OR NEWER UPDATE RELEASES IN FUTURE! YOU SHOULD NOT IGNORE...
forum.xda-developers.com
Or if you don't mind unlocking the bootloader, do these steps before you proceed to bootloader unlock:
1. Use volume key to select "Recovery mode", power key to enter.
2. When you see android robot lying on the ground, hold power key and press volume up key once. Then you'll get recovery screen.
3. Download this package: https://android.googleapis.com/packages/ota-api/package/627142c637bf373410e6b8911aeb9b2e65bd5969.zip
4. Select Apply Update from ADB, then sideload it with adb command.
5. Once the sideload procedure finishes, select "reboot to bootloader", then follow this guide to unlock the bootloader.
Existing Android 10 builds has a critical problem, that allowed us to flash or erase any bootloader partition even if the bootloader is not unlocked. However, Android 11 builds blocked this method, but there's a known workaround for this.
Therefore, I think it's time to disclose the unlock method now. It's known working on both TA-1243 and TA-1251.
The critical part for unlocking the bootloader is - the prototype bootloader of this phone. By opportunity, I got the early bootloader from a prototype unit that allows us to unlock the bootloader, thanks to the help of a Canadian people who claimed to have a Nokia 8.3 prototype himself.
Click this for Android 11 or Android 12 users
Your warranty will be void as bootloader unlock is not reverseable - you cannot relock it. Prototype ABL for normal Nokia 8.3 and 8V 5G UW are not interchangeable, flashing wrong ABL image will cause your phone hard brick.
To use this method, you need to ensure your phone has Android 10 installed - the latest build that we can use this method is 00WW_1_150-B01, you can confirm this by dialing *#*#7837#*#*.
If your phone has Android 11 installed (00WW_2_180-B01 or newer), then this bootloader unlock method has been blocked, but there's known workaround for this. Check 2nd reply for details.
UPDATE: Russian version Nokia 8.3 5G cannot be downgraded yet. If you're using Russian version Nokia 8.3 5G (Software version has RU tag), use EDL method for bootloader unlock.
Please download the prototype bootloader from here:
Click here for Nokia 8.3 5G (BGT TA-1243/1251)
Click here for Nokia 8V 5G UW (RAV TA-1257)
If you see Error code 00000101 during download - please use industrial standard web browser to download it, like Google Chrome.
SHA256
Code:
Nokia 8.3 5G: e253b67fa028b1ea9ca714bee6d95902e2b340ae201e0c88adc12781279b8fd5
Nokia 8V 5G UW: 70391abce694c95d7bb9d2c3fa1bcbfd66f26f42a766bc8d8c4d222caf8a62d4
Root Key Hashes
Code:
Nokia 8.3 5G: E3B22179CCBFB91730E233C4162E2D9DD33D02C97289EC1E9F787AC52CBDE3E0
Nokia 8V 5G UW: C3CEDC3A4612C85DD70EEDFA8ABA75621D579CEA62BB9A8D805DD4E9C542A6F0
(For Nokia 8.3 5G only), flash it under fastboot mode, and unlock the bootloader - pretty simple:
Code:
fastboot flash abl BGT-abl.elf
fastboot reboot-bootloader
fastboot oem unlock-go
Confirm unlock on your phone and it's all done. You can safely update the phone to Android 11 right after unlocked. Since we cannot perform critical unlock properly, we can only do regular unlock, but this should be enough.
Video demonstration:
For Nokia 8V 5G UW only:
1. Ask someone who has access of HDK to grant service permission for you.
2. Execute these commands (please download frp_oemunlock.img from https://forum.xda-developers.com/t/...rom-nokia-xr20-for-bootloader-unlock.4455845/ ):
Code:
fastboot flash abl RAV-abl.elf
fastboot reboot-bootloader
fastboot flash frp frp_oemunlock.img
fastboot reboot-bootloader
fastboot flashing unlock_critical
(confirm unlock)
fastboot flashing unlock
(confirm unlock)
Have fun for modding this device!
If you don't mind take apart your phone, you can use EDL method - but you know doing so will definitely void the warranty, and the stubborn triple-color company could remove these pads in later batches.
Firehose programmer for this phone is attached here.
Since we didn't grab downgrade OTA package for Russian variant, they cannot pass full OTA package verification and has to use EDL method for downgrading ABL. Thanks to Russian users for providing info.
In case Android 12 update from future cannot be downgraded, you'll have to use EDL method as well.
Example of using edl.py from bkerler (https://github.com/bkerler/edl):
Code:
edl.py w abl_a abl_proto_e253b67f.elf --memory=ufs --loader=prog_firehose_ddr.elf
edl.py w abl_b abl_proto_e253b67f.elf --memory=ufs --loader=prog_firehose_ddr.elf
edl.py reset
Keep in mind doing so will 100% void your warranty, and you cannot relock the bootloader.
For archiving purposes:
00WW_1_150-B01 full OTA zip: https://android.googleapis.com/packages/ota-api/package/627142c637bf373410e6b8911aeb9b2e65bd5969.zip
00WW_2_180-B01 full OTA zip: https://android.googleapis.com/packages/ota-api/package/12a35835cf4034f539ae7d03ffecd0682bef1b66.zip
You can use them for OS rooting.
Also after @jnappert 's testing, the workaround works great.
1. Sideload 00WW_1_150-B01 OTA package under recovery. You may see downgrade not allowed prompt but it will install anyway.
2. Reboot to bootloader under recovery mode. Although Anti-Rollback protection is triggered, the abl is not protected and is now downgraded to vulnerable build.
3. You can now follow the guide to unlock the bootloader.
I hope this will help everybody to bring up custom rom development for this phone.
hikari_calyx said:
Existing Android 10 builds has a critical problem, that allowed us to flash or erase any bootloader partition even if the bootloader is not unlocked.
Click to expand...
Click to collapse
Does that mean that they forgot to blow eFUSE of secure boot in this model? On a different device, once I flashed tampered ABL image after unlocking (and unlock_critical) the blootloader, XBL refuses to load ABL because of tampering. It hard bricked the device, but EDL mode was working.
It could be that ABL_proto image that you extracted might be signed by the OEM.
Volski_ said:
Does that mean that they forgot to blow eFUSE of secure boot in this model? On a different device, once I flashed tampered ABL image after unlocking (and unlock_critical) the blootloader but XBL refuses to load ABL because of tampering. It hard bricked the device, but EDL mode was working.
It could be that ABL_proto image that you extracted might be signed by the OEM.
Click to expand...
Click to collapse
It's signed by OEM - you can compare it yourself.
In demonstration video, the secure boot is already enabled as you can see.
Can anybody tell does it pass CTS with Magisk hide?
mingkee said:
Can anybody tell does it pass CTS with Magisk hide?
Click to expand...
Click to collapse
It will pass - at least that's the situation on 00WW_1_150-B01.
Now I have mine turn off to avoid further update.
I was unaware and it went up to 11, so I have to use different bootloader to root.
mingkee said:
Now I have mine turn off to avoid further update.
I was unaware and it went up to 11, so I have to use different bootloader to root.
Click to expand...
Click to collapse
If bootloader unlocked, it will be safe to update to Android 11.
Hello everybody. I was minding: because i've upgraded my nokia 8.3, is it possibile to roll back to android 10, unlock bootloader and install superSU?
I tried downgrading to Android 10 yesterday und sucessfully unlocked bootloader (which deletes user-data). Then the OTA Update to 00WW_2_200 installed without problem.
jnappert said:
I tried downgrading to Android 10 yesterday und sucessfully unlocked bootloader (which deletes user-data). Then the OTA Update to 00WW_2_200 installed without problem.
Click to expand...
Click to collapse
can you please type here the steps you've made to downgrade your phone?
For Nokia 8 V 5G UW users:
I suspect devices with 00VPO_1_260-B01 or older should be vulnerable, but I think many users should have the phone updated to 00VPO_1_280-B01 already.
Need further investigation whenever I got firmware.
I tried to downgrade mine from Android 11 to 10. Anyways, when i sideload the "update", the recovery text "downgrade not allowed". When it finishes the install, my phone just boot in fastboot mode and the only way to get it back is to install the Android 11 update. Still waiting any tips to downgrade
TheDuke94 said:
can you please type here the steps you've made to downgrade your phone?
Click to expand...
Click to collapse
I downgraded from 00WW_2_180 to 00WW_1_150-B01:
- installed adb and drivers
- enabled USB Debug
- bootet to stock recovery: "adb reboot recovery"
- in recovery "apply update from adb"
- adb sideload 00WW_1_150-B01 from post #3
- rebootet to fastboot and continued with steps from post #1 to unlock bootloader
- after reboot device updated directly to 00WW-2_200
Now i am looking for working custom recovery...
jnappert said:
I downgraded from 00WW_2_180 to 00WW_1_150-B01:
- installed adb and drivers
- enabled USB Debug
- bootet to stock recovery: "adb reboot recovery"
- in recovery "apply update from adb"
- adb sideload 00WW_1_150-B01 from post #3
- rebootet to fastboot and continued with steps from post #1 to unlock bootloader
- after reboot device updated directly to 00WW-2_200
Now i am looking for working custom recovery...
Click to expand...
Click to collapse
Thanks for sharing the tip. But apparently the triple-color company will block this
hikari_calyx said:
Thanks for sharing the tip. But apparently the triple-color company will block this
Click to expand...
Click to collapse
Looks like it already happened, 'cause mine says "downgrade not allowed" gonna try again friday. I'll update you
I was lucky enough to get this phone from bh photos as shelf stock and it shipped with android 10. They are currently on sale there for $320. I installed and unlocked bootloader. I may get a pixel as a backup so id be willing to test recovery,roms etc...when someone comes up with something. Ive been out of the Android scene for a while and im curious if root is possible at this time or if that would require 3rd party recovery and/or a kernel
A little update
Bootloader unlocked
This time is a bit tricky
I tried to enter recovery and got "no command". Press volume up + power together every 2 seconds and I got actual recovery
Tried update from SD...no go
Tried update from adb... downgrade is not allowed
Somehow I went to fastbootd and nothing worked
I chose bootloader and this time elf file from post 1 worked (it didn't work when I enter bootloader normal way)
Now I have to find out where I can get boot to patch
mingkee said:
A little update
Bootloader unlocked
This time is a bit tricky
I tried to enter recovery and got "no command". Press volume up + power together every 2 seconds and I got actual recovery
Tried update from SD...no go
Tried update from adb... downgrade is not allowed
Somehow I went to fastbootd and nothing worked
I chose bootloader and this time elf file from post 1 worked (it didn't work when I enter bootloader normal way)
Now I have to find out where I can get boot to patch
Click to expand...
Click to collapse
You can extract boot image from OTA package via payload dumper.
Related
I have the Redmi note 3 pro 2gb snapdragon version I have unlocked my bootloader officially. I cannot seem to be able to root/flash recovery onto my phone.
I tried the Miui India toolkit - I get an error message: error unhandled exception has occurred in your application blah blah blah Could not find file c:\1.txt
I tried following this guide, and it worked once but it also broke Wifi - wifi refused to turn on
http://xiaomitips.com/guide/root-redmi-note-3-snapdragon/
I'm on Global Stable 7.1.8.0. I've tried the China rom and Global 7.2.3.0 but both roms are much worse on my phone - I no longer get notifications from my messaging apps, Blackplayer keeps stopping and restarting from the very first song it started playing, and other random bugs
Any help would be greatly appreciated, thank you
pyro224 said:
I have the Redmi note 3 pro 2gb snapdragon version I have unlocked my bootloader officially. I cannot seem to be able to root/flash recovery onto my phone.
I tried the Miui India toolkit - I get an error message: error unhandled exception has occurred in your application blah blah blah Could not find file c:\1.txt
I tried following this guide, and it worked once but it also broke Wifi - wifi refused to turn on
http://xiaomitips.com/guide/root-redmi-note-3-snapdragon/
I'm on Global Stable 7.1.8.0. I've tried the China rom and Global 7.2.3.0 but both roms are much worse on my phone - I no longer get notifications from my messaging apps, Blackplayer keeps stopping and restarting from the very first song it started playing, and other random bugs
Any help would be greatly appreciated, thank you
Click to expand...
Click to collapse
You unlocked your bootloader on stable ROM? Are you sure? According to this post it doesn't work on stable and it didn't work for me (same model).
Check it in fastboot (power off device and boot by holding Power + Vol Down):
1. Connect your RN3 SD to PC
2. Open cmd.exe and change to your ADB/fastboot folder with "cd <X:\myADBandFASTBOOTfolder\>" (replace with whereever fastboot.exe is located)
3. Check the connection with "fastboot devices". It should show something, meaning that your PC recognizes your device being connected through fastboot.
4. Enter "fastboot oem device-info". The line where it says "Device unlocked:" should be "true". If not, your bootloader is still locked.
Anyway, I suggest going to an official Developer Version (if you are on Global Stable, install Global Dev; China Stable -> China Dev). IMPORTANT: Search through forums, if an OTA update is safe to do, when your bootloader is unlocked. It might (!) lock it again, meaning you have to wait again, since Xiaomi only allows one unlock a month per device.
When you are on Dev ROM with bootloader unlocked, follow this guide to flash TWRP and patch the boot.img (important, so it doesn't replace TWRP with stock recovery again after the next boot). Go into recovery (Power + Vol Up) immediately after flashing TWRP, without rebooting to system. If TWRP is in Chinese, check out my comment here on how to fix it.
After successful installation of TWRP make sure that it's permanent (reboot the device at least twice and enter TWRP again). If that is the case you can search for the latest SuperSU.zip and flash it through TWRP which should give you root.
Hope this helps.
Immortal68 said:
You unlocked your bootloader on stable ROM? Are you sure? According to this post it doesn't work on stable and it didn't work for me (same model).
Check it in fastboot (power off device and boot by holding Power + Vol Down):
1. Connect your RN3 SD to PC
2. Open cmd.exe and change to your ADB/fastboot folder with "cd <X:\myADBandFASTBOOTfolder\>" (replace with whereever fastboot.exe is located)
3. Check the connection with "fastboot devices". It should show something, meaning that your PC recognizes your device being connected through fastboot.
4. Enter "fastboot oem device-info". The line where it says "Device unlocked:" should be "true". If not, your bootloader is still locked.
Anyway, I suggest going to an official Developer Version (if you are on Global Stable, install Global Dev; China Stable -> China Dev). IMPORTANT: Search through forums, if an OTA update is safe to do, when your bootloader is unlocked. It might (!) lock it again, meaning you have to wait again, since Xiaomi only allows one unlock a month per device.
When you are on Dev ROM with bootloader unlocked, follow this guide to flash TWRP and patch the boot.img (important, so it doesn't replace TWRP with stock recovery again after the next boot). Go into recovery (Power + Vol Up) immediately after flashing TWRP, without rebooting to system. If TWRP is in Chinese, check out my comment here on how to fix it.
After successful installation of TWRP make sure that it's permanent (reboot the device at least twice and enter TWRP again). If that is the case you can search for the latest SuperSU.zip and flash it through TWRP which should give you root.
Hope this helps.
Click to expand...
Click to collapse
Hello
Sorry to rephrase: I flashed to China Dev rom via MiFlash and unlocked the bootloader offically, however this rom had odd errors and bugs so I went back to the older Global Stable. My understanding is that the bootloader is now unlocked regardless of what ROM i am running?
In the guide you linked, the OP mentione "no patched boot.img required" yet you recommend I patch the boot.img? Can you advise how I should do this?
pyro224 said:
Hello
Sorry to rephrase: I flashed to China Dev rom via MiFlash and unlocked the bootloader offically, however this rom had odd errors and bugs so I went back to the older Global Stable. My understanding is that the bootloader is now unlocked regardless of what ROM i am running?
In the guide you linked, the OP mentione "no patched boot.img required" yet you recommend I patch the boot.img? Can you advise how I should do this?
Click to expand...
Click to collapse
I think going from China Dev to Global Stable is giving you troubles. Since you already flashed another Official ROM after unlocking the bootloader I don't think it would make matters worse if you did it again now. Try flashing the official Global Dev Qualcom http://en.miui.com/download-301.html and check again if your bootloader is unlocked through the method I posted. After that - if it's still unlocked - you should be able to follow through with the guide.
Right, the boot.img is patched automatically through TWRP when you enter and exit it. Just flash the recovery and confirm overwriting files, so it doesn't go back to stock, when you exit TWRP. You should get a notification when you try to rebbot to system through TWRP.
Just as an update - I was able to flash Cofface's recovery on Global Stable 7.1.8.0 (since my phone refused to update me to any other rom) using the provided guide http://forum.xda-developers.com/redmi-note-3/development/recovery-kenzotwrp-cafface-3-0-0-t3369341
BACKUP YOUR DATA FIRST
Only for zs570kl 2.15ghz CPU; NO zs570klPRO 2.4ghz device.
Hi all,
official image to flash Android 8 Oreo.
HOW TO:
Method fast 1
1.Extract ZIP
2.Go into the fastboot (key vol + and power on)
3. On the folder extract open update_image.bat
Wait to done 2/3 minut and ENJOY android Oreo
Method 2
Flash using Asus Flash Tool
to download and info
https://www.asus-zenfone.com/2017/03/download-asus-flashtool-10045-for-zenfone-3.html?m=1
Update file Android 8 Oreo 15.0210.1804.47:
https://drive.google.com/open?id=1U5SBXDpezUIIxisDPY8qm85LoGNfS5i6
I take no responsibility for brick device.
Have testeted the rom and work fine.
That's official from Asus?
If I flash it from TWRP Will replace stock recovery?
tecnicopascoal said:
That's official from Asus?
If I flash it from TWRP Will replace stock recovery?
Click to expand...
Click to collapse
official Asus, no only in fastboot mode
Has anyone suffering battery drain? I've updated my ZS570KL to 8.0 with Asus official but phone became hot and battery drain is dramatical…. obvious reset many time to factory default and wipe all…. The problem appears from the beginning…. starting the initial setup. Thanks.
grean said:
official Asus, no only in fastboot mode
Click to expand...
Click to collapse
So is this rootable or is it pre-rooted? I also am wondering if this Oreo update fixed the Quickcharge limit (where QC is disabled)?
It is the only way to update?? Except ota
EDIT. Guys, the other way you can update to oreo is flashing oreo stock recovery and then install the firmware
Wheres the MAGIC
have oreo up and running no problem, lost root/magisk and cant seem to get it back. trying to flash magisk installer failed even up to 16.4 just goes into bootloop, flashing stock boot back and it boots up ok to oreo.
If any one on ZS570KL 2.1ghz has oreo running with MAGISK please post a copy of your boot.img.
the only other thing I can think off is that the bootloader is relocked. Anybody with any experience of this?
Aussiewaterdragon said:
have oreo up and running no problem, lost root/magisk and cant seem to get it back. trying to flash magisk installer failed even up to 16.4 just goes into bootloop, flashing stock boot back and it boots up ok to oreo.
If any one on ZS570KL 2.1ghz has oreo running with MAGISK please post a copy of your boot.img.
the only other thing I can think off is that the bootloader is relocked. Anybody with any experience of this?
Click to expand...
Click to collapse
I'm having the same issue, also I can't seem to unlock my bootloader using the unlock tool on asus website it always says "Failed to unlock this device, please try again later"
also what's up with this automatic device encryption ? I flashed twrp recovery and it can't decrypt the device using the password or the PIN i've set, I even tried "default_password" still doesn't work
BahaStriker said:
I'm having the same issue, also I can't seem to unlock my bootloader using the unlock tool on asus website it always says "Failed to unlock this device, please try again later"
also what's up with this automatic device encryption ? I flashed twrp recovery and it can't decrypt the device using the password or the PIN i've set, I even tried "default_password" still doesn't work
Click to expand...
Click to collapse
Have you had any luck? I'm having a similar problem to you. When I try to unlock my bootloader using the unlock tool it complains that I don't have a PIN set (even though I do) then fails and says "Failed to unlock this device, please try again later".
karlnorth said:
Have you had any luck? I'm having a similar problem to you. When I try to unlock my bootloader using the unlock tool it complains that I don't have a PIN set (even though I do) then fails and says "Failed to unlock this device, please try again later".
Click to expand...
Click to collapse
Tried all means, I just gave up
I'm happy to say that I got it working. It appears the Unlock tool gives the "Can't unlock your phone right now" error if your phone is already unlocked.
Previously, I was running the Turbo ROM 6.01 found in the ZF3 Deluxe thread. My phone was BootLoader unlocked and Rooted. I upgraded to 8.0 by running the very straightforward "Update_Image.bat" command found in the 8.0 ROM folder. I figured the update would re-lock my BootLoader, so I ran the 8.0 version of the Unlock tool. Then I ran into the previously mentioned error. In my frustration I just said 'screw it, I have 4 of these phones'. So I booted the phone into fastboot mode and flashed TWRP 3.2.2. I expected it to fail; however, it WORKED! I then booted the TWRP 3.2.2 image and flashed SuperSU v2.82 SR5. That worked! I then flashed the Xposed v90-sdk27-arm64-beta3 zip and THAT worked! I rebooted the phone and it loaded up pretty as you please.
I've followed this procedure with all 4 of my ZF3 Deluxe phones and they are all happily on 8.0.0, Rooted, and have Xposed running
Doing this quick update because today, when trying to root my phone, bricked it several times and lost all app info
If you are using android 7.11, this guide works fine: https://forum.xda-developers.com/zenfone-3-zoom/how-to/how-to-root-zenfone-3-zoom-ze553kl-t3622256
If on android 8, SuperSU will brick your phone. Use Magisk instead:
- enable usb debug mode on your phone
- unlock bootloader
- plug phone into your computer
on your pc
- Download fastboot and adb:
* Windows: https://dl.google.com/android/repository/platform-tools-latest-windows.zip
* macos: https://dl.google.com/android/repository/platform-tools-latest-darwin.zip
* linux: https://dl.google.com/android/repository/platform-tools-latest-linux.zip
- download the latest Magisk unlock script from https://github.com/topjohnwu/Magisk/releases and copy it to a MicroSD or USB that you can attach to your phone. Look for Magisk, not Magisk Manager
- download twrp v 3.1.0-0-Z01H-20170408: https://mega.nz/#F!p90wgAaY!l1JbJilmAUEKTKWu43pT9w?E81jQTCD (this is from https://mega.nz/#F!p90wgAaY!l1JbJilmAUEKTKWu43pT9w, as described in the old root guide using twrp + supersu. It is supposed to be safe)
- `adb reboot bootloader`
- `fastboot flash recovery <path to twrp image downloaded>`
- `fastboot reboot`
Right now, you should probably backup your phone.
back on your phone:
- before booting, press volume up on the bootloader, there, select Recovery. Using fastboot to reboot into recovery might cause the stock recovery image to reflash
- if prompted to enable system modifications, allow it.
- If prompted to decrypt your data in TWRP, use the PIN you setup. If it doesn't work, I can't guarantee you won't brick our phone. Feeling brave enough? In case of brick keep reading, it is easy to restore your phone to stock Android 8 using official firmware.
- press install, choose the device attached to your phone that has Magisk-xxx.zip and select it
- flash the image and it should be OK
In case of brick or unsuccessful flash from SuperSU and without backup:
- Don't panic, like I did today
- download the latest firmware from Asus: https://www.asus.com/us/Phone/ZenFone-3-Zoom-ZE553KL/HelpDesk_BIOS/
- follow this guide: https://forum.xda-developers.com/zenfone-3-zoom/how-to/manually-update-to-7-11-t3815703
- when the phone reboots, boot into recovery
- enable ADB sideload
- on your pc: `adb sideload <path to newest firmare>`
- now follow the root guide above before starting your phone
- ???
- profit
Note: commands using adb and fastboot assume you have put the contents from the downloaded platform tools in your PATH, else execute them from the directory in which they were extracted, for instance, on linux:
- `cd /home/$USER/Downloads`
- `unzip platform-tools-latest-linux.zip`
- `cd platform-tools`
- `./adb devices`
Bricked my phone.
in which step?
You should have access to fastboot, try the downgrade tutorial and install android 7 then imediately flash the latest image from ASUS
gchamon said:
in which step?
You should have access to fastboot, try the downgrade tutorial and install android 7 then imediately flash the latest image from ASUS
Click to expand...
Click to collapse
After the magisk install. It logged some "can't mount partition" errors, I tried to wipe, but do not worked.
It got stucked on Asus logo.
I did the unbrick tutorial.
This is strange. Magisk is supposed to patch the boot image and install its app (by the way, if you update magisk using the app, phone enters bootloop)
Anyway, I have encountered myself many problems when installing, but nothing like this. Bootloops and corruption message on bootloader yes, but I can't seem to recall anything about partitions not being mounted. If installing stock recovery image, boot image and system doesn't do the trick, in my experience it is either bad partitioning, although unlikely, because those procedures doesn't repartition anything, or bad internal storage.
But just to be sure, you should reflash stock 7.1 image (recovery, boot and system) with fastboot, enter stock recovery and wipe cache/factory reset. If your phone is physically healthy, this should work
anonymousbsb said:
After the magisk install. It logged some "can't mount partition" errors, I tried to wipe, but do not worked.
It got stucked on Asus logo.
I did the unbrick tutorial.
Click to expand...
Click to collapse
Try to use twrp-3.2.3-0-Z01H-20181014, i faced the same issue and fixed by flash it
Enrico06 said:
Try to use twrp-3.2.3-0-Z01H-20181014, i faced the same issue and fixed by flash it
Click to expand...
Click to collapse
Cool, if this fixes the issue I will update the guide with this info
bro pls give an unofficial process to unlock this device because official unlock tool not working it shows "unknown network error".
kingairtel08 said:
bro pls give an unofficial process to unlock this device because official unlock tool not working it shows "unknown network error".
Click to expand...
Click to collapse
Downgrade to 7.1.1 and try it again.
Already tried on 7.1.1 lot of times same error shows.
please share a working process of unlock bootloader without asus unlock tool apk....i m waiting for 3 years
kingairtel08 said:
please share a working process of unlock bootloader without asus unlock tool apk....i m waiting for 3 years
Click to expand...
Click to collapse
normal. please wait 15min max
kingairtel08 said:
please share a working process of unlock bootloader without asus unlock tool apk....i m waiting for 3 years
Click to expand...
Click to collapse
I can't really help you there. This guide is supposed to work for those who are able to unlock bootloader using official asus tools. Never heard of unofficial unlock methods. It is possible that you have a hardware problem if you use those tools and they just don't work.
kingairtel08 said:
please share a working process of unlock bootloader without asus unlock tool apk....i m waiting for 3 years
Click to expand...
Click to collapse
Have you used the latest official unlocking tool? I see there's a July 2019 version available.
If you are on an older version of Android (not Oreo) are you presently still getting OTA update prompts?
I tried this tool but no result.
is it possible to root ZE553KL without loosing user application's data? I have unrooted device, wanted to migrate telegram secret chats to new phone. it is doable but with rooted smartphone only. if rooting process is destructive I cannot migrate. if rooting is doable with preserving installed applications along with their data then there is a hope for successful migration.
does this method look promising or it is just fake method?
Asus Zenfone 3 Zoom ZE553KL root using Magisk [No need TWRP Recovery
How to root Asus Zenfone 3 Zoom ZE553KL with Magisk [no need TWRP recovery, easy method to rood your Android device.
www.mobilewithdrivers.com
Ho, I have an Asus Zenfone 3 Max ZC520TL X008. Chipset MT6737m. Firmware WW. Android Oreo 8.1. Locked bootloader. I'm desperate.
I would like to root it with Magisk but for this device I don't find any guide or method. The first problem is how to unlock the bootloader? Asus usually releases an unlock tool but they didn't upgrade it for Oreo 8.1.
Is there a way to unlock it without this tool?
I would like to install twrp so I can flash Magisk.
I hope someone can realise a guide o give me some indications. Or if there is no possible with Oreo, there is a tutorial to downgrade Android in this device?
Thank you
unlocking bootloader is the same procedure as usual, isn't it? enable oem unlocking in developer options (do you have this?) and what is the error for fastboot flashing unlock?
aIecxs said:
unlocking bootloader is the same procedure as usual, isn't it? enable oem unlocking in developer options (do you have this?) and what is the error for fastboot flashing unlock?
Click to expand...
Click to collapse
thanks for your reply. I don't have that option in developer options. Only debug USB. I don't know what is the usual way to unlock bootloader. I rooted 2 zenfone Asus and for the two I used Asus unlock bootloader tool. But for this model they released the tool for Nougat. After they released Oreo 8.1 and abandoned this device without releasing the unlock tool for Oreo
fastboot available?
aIecxs said:
fastboot available?
Click to expand...
Click to collapse
Yes, available
and what is the error for
Code:
fastboot flashing unlock
aIecxs said:
and what is the error for
Code:
fastboot flashing unlock
Click to expand...
Click to collapse
no error. I didn't try because for Asus I always used the unlock tool they released and for this reason I wanted to know another way.
I put the smartphone in fastboot mode and give that command right?
Another question I found a root guide for my smartphone but with Nougat. Could I use the twrp they put in that guide even if I have Oreo?
Thank you
i don't understand you. you did not try, or you got no error?
if this is the guide you found, you can use this TWRP as base for porting (if not working out of the box). But you are runnning Oreo and i am not aware about secure boot enabled for this ROM, so i strongly recommend to make a full ROM dump for your device and create your own scatter file, in case you brick your device
it might be possible to unlock bootloader by hexpatching /dev/block/bootdevice/by-name/devinfo partition as @Titokhan did for Zenfone 2 Laser, but this is not recommended for daily drivers and you may need the full ROM dump for unbricking with SP Flash Tool
there is bootless root method with suboot script for locked bootloader, but again, this is dangerous for secure boot / dm-verity enabled device. in case any app tries to alter your boot or system partition, this will break boot chain and brick your device
so please don't follow any guides if you not 100% know what you are doing
start with installing MediaTek MT65xx USB VCOM Preloader USB Drivers for Windows, and report back once you managed to see the preloader showing up for ~ 1 second in device manager like this
aIecxs said:
i don't understand you. you did not try, or you got no error?
if this is the guide you found, you can use this TWRP as base for porting (if not working out of the box). But you are runnning Oreo and i am not aware about secure boot enabled for this ROM, so i strongly recommend to make a full ROM dump for your device and create your own scatter file, in case you brick your device
it might be possible to unlock bootloader by hexpatching /dev/block/bootdevice/by-name/devinfo partition as @Titokhan did for Zenfone 2 Laser, but this is not recommended for daily drivers and you may need the full ROM dump for unbricking with SP Flash Tool
there is bootless root method with suboot script for locked bootloader, but again, this is dangerous for secure boot / dm-verity enabled device. in case any app tries to alter your boot or system partition, this will break boot chain and brick your device
so please don't follow any guides if you not 100% know what you are doing
start with installing MediaTek MT65xx USB VCOM Preloader USB Drivers for Windows, and report back once you managed to see the preloader showing up for ~ 1 second in device manager like this
Click to expand...
Click to collapse
I didn't try because Asus didn't release their usually app to unlock bootloader for this model with Oreo. The app is available until Nougat and after they abandoned this device. So before installing twrp my first problem is how to unlock the bootloader without this app. So I'm looking for a way to unlock the bootloader. Someone told me to unlock with ADB/Fastboot but I don't know how to do it.
In another way I would like to know if I can downgrade to Nougat with SPflash even if my bootloader is locked so that after I could use the apk unlock bootloader tool for this device.
It is a very negative device for everything. A lot of problems.
This is the guide I found
https://www.asus.com/zentalk/thread-189650-1-1.html
It is for my model with Nougat and it uses the Asus tool to unlock the bootloader. I wanted to know if I could use twrp version of this guide.
Thanks for your reply and kindness
yes you can use this twrp.
no you (probably) can't downgrade to nougat because of anti-rollback protection (at least, i don't know). if you wanna try, please follow the steps for full ROM dump (because i strongly recommend to have this backup), first step is install preloader drivers. can you do this please?
Someone told you to unlock bootloader with fastboot. and so did i (the command for unlocking is: fastboot flashing unlock) which is your native language? seems you have problems with reading & understanding (because of language barrier?) my native language is german
Hello, I'm new to the Android hacking/modding scene with this being the first phone I am able to unlock the bootloader for. I recently picked this phone up (Model DE2118 to be specific), and got it's bootloader unlocked and installed Lineage. Now that it is all done and out of the way, would it be possible to lock the bootloader to prevent further modifications and potential security risks? Thank you in advance.
Gateway05184 said:
Hello, I'm new to the Android hacking/modding scene with this being the first phone I am able to unlock the bootloader for. I recently picked this phone up (Model DE2118 to be specific), and got it's bootloader unlocked and installed Lineage. Now that it is all done and out of the way, would it be possible to lock the bootloader to prevent further modifications and potential security risks? Thank you in advance.
Click to expand...
Click to collapse
Under no circumstance should you relock the bootloader. The only OS that I know of that currently lets you do that on any device is Graphene OS on pixel devices. And that is written by extremely gifted developers. So... no... not now or anytime soon. Sorry!
Nope. While you could relock your bootloader now, you'd get an error message the next time you turned on your phone and it would refuse to boot. (And there's no guarantee that you could recover it, though usually the MSM tool works.) In most cases, you should never relock the bootloader unless you're on stock, unmodified firmware. In some cases, it is possible if the custom ROM you're using instructs you to relock your bootloader and provides their own keys for you to flash or if you build and sign your own ROMs yourself, but otherwise, it's just not worth it.
You should read this reddit post for more details as to why you shouldn't relock your bootloader.
Yeah, I kind of figured. I tried locking the bootloader out of curiosity (obviously, you shouldn't do this.) which caused it to brick. I unbricked it using the MSM tools for the specific model. I also tried flashing the public key but it only allows recovery to boot and boot loops if you just leave it sit. lol
Don't' try this ever, you will most probably soft brick the device without being able to recover it.
You can only safely relock the bootloader on stock OS without the risk of bricking the device.
Sprunglicious said:
Under no circumstance should you relock the bootloader. The only OS that I know of that currently lets you do that on any device is Graphene OS on pixel devices. And that is written by extremely gifted developers. So... no... not now or anytime soon. Sorry!
Click to expand...
Click to collapse
Gateway05184 said:
Hello, I'm new to the Android hacking/modding scene with this being the first phone I am able to unlock the bootloader for. I recently picked this phone up (Model DE2118 to be specific), and got it's bootloader unlocked and installed Lineage. Now that it is all done and out of the way, would it be possible to lock the bootloader to prevent further modifications and potential security risks? Thank you in advance.
Click to expand...
Click to collapse
Not entirely true. CalyxOS allows relocking bootloader on Pixels. My own development for Oneplus 6/6T/8/8T/8Pro/9 and 9Pro allows relocking bootloader.
I managed to find a way to relock the bootloader with LineageOS installed by compiling it from source and patching a few files. Then I flashed the avb_custom_key partition via fastboot with the key I used to sign the image I've compiled. This resulted in me getting the yellow error screen (Your device has loaded a different OS.) rather than the usual orange screen you get with the bootloader unlocked. I even used a tool called "avbroot" to patch the image for magisk support.
just use the MSMDownload tool for the firmware you want, it will set it back to factory defaults and factory OS including re-locking the bootloader
NOTE: if you ever want to unlock it again just use the token file/bin file that oneplus sent you originally to unlock. no need to re-apply or ask oneplus again for new token, can just use the original one they sent you.
Gateway05184 said:
Hello, I'm new to the Android hacking/modding scene with this being the first phone I am able to unlock the bootloader for. I recently picked this phone up (Model DE2118 to be specific), and got it's bootloader unlocked and installed Lineage. Now that it is all done and out of the way, would it be possible to lock the bootloader to prevent further modifications and potential security risks? Thank you in advance.
Click to expand...
Click to collapse
I don't like seeing my Nord n200 boot to the unlocked bootloader screen, and found a way to prevent that.
I found the method on the Reddit forum for LineageOS.
From CevicheMixto:
I was able to complete the upgrade (dirty flash from the latest LineageOS 19.1). Here's what I had to do.
First, I upgraded the device firmware, following this guide. Note that the oneplus.com page that is linked from that guide does not appear to actually provide firmware for the Nord N200. The Oxygen Updater app does allow you to download the firmware, once the app's settings have been changed to enable "Advanced mode." It will save the firmware file in the /sdcard directory, and adb can be used to transfer it to your PC. (Alternatively, the firmware can be directly downloaded from https://android.googleapis.com/packages/ota-api/package/6be3f133f8fb9bbcc30d787679bd7b5da5e30995.zip.)
At this point, my phone would not boot into the LineageOS recovery (19.1 or 20); it kept returning to bootloader mode. I fixed this by flashing the LineageOS 20 boot, dtbo, and vendor_boot images onto the device. These images can be extracted from the LineageOS 20 ZIP file with payload-dumper-go, or they can be downloaded from the dre builds page.
fastboot flash boot boot.img
fastboot flash dtbo dtbo.img
fastboot flash vendor_boot vendor_boot.img
(Unlike fastbootd, the bootloader does not appear to support the --slot=all option, but I only needed to flash these for the active slot.)
I was now able to boot into the (installed) LineageOS 20 recovery, choose "Apply update" and "Apply from ADB" to put the device into sideload mode. I then followed the upgrade instructions to flash the LineageOS 20 ZIP file, reboot back to recovery, and flash the MindTheGapps ZIP file.
Do yourself a favor and just load Oxygen Updater onto another Android phone and download the files. It will pop up a notice that the phone isn't the correct one, but just click advanced and download the file, then continue on.
My Nord n200 now boots with the OnePlus logo then directly to LineageOS with Android 13
KeysStickler said:
I don't like seeing my Nord n200 boot to the unlocked bootloader screen, and found a way to prevent that.
I found the method on the Reddit forum for LineageOS.
From CevicheMixto:
I was able to complete the upgrade (dirty flash from the latest LineageOS 19.1). Here's what I had to do.
First, I upgraded the device firmware, following this guide. Note that the oneplus.com page that is linked from that guide does not appear to actually provide firmware for the Nord N200. The Oxygen Updater app does allow you to download the firmware, once the app's settings have been changed to enable "Advanced mode." It will save the firmware file in the /sdcard directory, and adb can be used to transfer it to your PC. (Alternatively, the firmware can be directly downloaded from https://android.googleapis.com/packages/ota-api/package/6be3f133f8fb9bbcc30d787679bd7b5da5e30995.zip.)
At this point, my phone would not boot into the LineageOS recovery (19.1 or 20); it kept returning to bootloader mode. I fixed this by flashing the LineageOS 20 boot, dtbo, and vendor_boot images onto the device. These images can be extracted from the LineageOS 20 ZIP file with payload-dumper-go, or they can be downloaded from the dre builds page.
fastboot flash boot boot.img
fastboot flash dtbo dtbo.img
fastboot flash vendor_boot vendor_boot.img
(Unlike fastbootd, the bootloader does not appear to support the --slot=all option, but I only needed to flash these for the active slot.)
I was now able to boot into the (installed) LineageOS 20 recovery, choose "Apply update" and "Apply from ADB" to put the device into sideload mode. I then followed the upgrade instructions to flash the LineageOS 20 ZIP file, reboot back to recovery, and flash the MindTheGapps ZIP file.
Do yourself a favor and just load Oxygen Updater onto another Android phone and download the files. It will pop up a notice that the phone isn't the correct one, but just click advanced and download the file, then continue on.
My Nord n200 now boots with the OnePlus logo then directly to LineageOS with Android 13
Click to expand...
Click to collapse
That doesn't solve what I was originally attempting to do but I appreciate the suggestion nonetheless. However, the DE2117 OTA update is not meant for the carrier exclusive models (i.e. DE2118 aka the MetroPCs T-Mobile model.) I've already attempted this on my own DE2118 and it resulted in a boot loop. This problem doesn't exist in Lineage 19.1.
Gateway05184 said:
That doesn't solve what I was originally attempting to do but I appreciate the suggestion nonetheless. However, the DE2117 OTA update is not meant for the carrier exclusive models (i.e. DE2118 aka the MetroPCs T-Mobile model.) I've already attempted this on my own DE2118 and it resulted in a boot loop. This problem doesn't exist in Lineage 19.1.
Click to expand...
Click to collapse
I used this to update to LineageOS 20
there is no known way to relock the boot-loader on a custom rom on the nord n200 . However you can re-lock in on the official firmware. You can always go back to the official firmware with the locked bootloader by flashing the official firmware via MSM Download tool