can anyone tell me how i can root my n200 stock rom now with android 12 update on it now i cannot get twrp on it or even just boot twrp to flash Magisks with android 11 no issue but now with 12 i can't get it done Thanks for any help
PS shoutout to whomever posted msm tool for global de2117 finally !
The fastboot boot option has been removed from the N200 Android 12 update.
I have extracted the A12 boot.img file with payload-dumper-go from the payload.img and posted it at the N200 Telegram channel while waiting for approval to post at Androidfilehost.
You can then patch it with latest Magisk and fastboot flash it.
Nord N200 Testers
A group for discussing N200 custom software testing. All off topic discussion has been moved to this group: https://t.me/+1qZHIItf9R80MTYx Check pinned messages for important messages and shared/confirmed working files.
t.me
Boot.img for DE2118_11_C.15 T-Mobile/MetroPCS AOSP 12 posted here
scanman0 said:
The fastboot boot option has been removed from the N200 Android 12 update..
Click to expand...
Click to collapse
I'm on Android 12 with the unlocked version and fastboot is still available with either:
adb reboot bootloader
From powered off, press and hold vol down, volume up and power. When the OnePlus logo appears release power but continue holding the other buttons until the fastboot screen appears.
yeswap said:
I'm on Android 12 with the unlocked version and fastboot is still available with either:
adb reboot bootloader
From powered off, press and hold vol down, volume up and power. When the OnePlus logo appears release power but continue holding the other buttons until the fastboot screen appears.
Click to expand...
Click to collapse
I have C.16 stock unlocked boot elsewhere
mingkee said:
I have C.16 stock unlocked boot elsewhere
Click to expand...
Click to collapse
What is C.16? T-Mobile version? With the factory SIM unlocked Android 12 my build number ends in C.15.
When would someone need to flash your boot image and what advantages would it have over the stock boot?
yeswap said:
What is C.16? T-Mobile version? With the factory SIM unlocked Android 12 my build number ends in C.15.
When would someone need to flash your boot image and what advantages would it have over the stock boot?
Click to expand...
Click to collapse
It's stock unlocked C16 boot I got yesterday (neither T-Mobile nor Metro version)
As soon as I received the OTA, I grabbed boot and uploaded it
yeswap said:
I'm on Android 12 with the unlocked version and fastboot is still available with either:
adb reboot bootloader
From powered off, press and hold vol down, volume up and power. When the OnePlus logo appears release power but continue holding the other buttons until the fastboot screen appears.
Click to expand...
Click to collapse
scanman0 means you can no longer run "fastboot boot" from the computer to send a boot image without flashing, you have to flash with "fastboot flash boot" to test a new boot image on your phone
towardsdawn said:
scanman0 means you can no longer run "fastboot boot" from the computer to send a boot image without flashing, you have to flash with "fastboot flash boot" to test a new boot image on your phone
Click to expand...
Click to collapse
Thanks
towardsdawn said:
scanman0 means you can no longer run "fastboot boot" from the computer to send a boot image without flashing, you have to flash with "fastboot flash boot" to test a new boot image on your phone
Click to expand...
Click to collapse
Does that mean I can flash without unlocking the bootloader?
NeonWhitey said:
Does that mean I can flash without unlocking the bootloader?
Click to expand...
Click to collapse
No, unlocking bootloader gives you access to boot sector and allows you to flash boot images. Unlocking bootloader on Android 11 on this device also let you run "fastboot boot" which let you run boot images without flashing but with upgrade to Android 12 that is no longer the case.
towardsdawn said:
No, unlocking bootloader gives you access to boot sector and allows you to flash boot images. Unlocking bootloader on Android 11 on this device also let you run "fastboot boot" which let you run boot images without flashing but with upgrade to Android 12 that is no longer the case.
Click to expand...
Click to collapse
How would i go about doing it on android 12 because the firmware version I'm on has a major bug.
NeonWhitey said:
How would i go about doing it on android 12 because the firmware version I'm on has a major bug.
Click to expand...
Click to collapse
Follow this guide, if you have T-Mobile version and need a SIM unlock, you only need to run the one line ADB command to remove qti.uim you don't need the full debloat script.
You don't need to unlock bootloader if you just want to factory reset the device. If you have T-mobile use MSM tool, otherwise you can try your luck with this guide
Related
I restored a Moto E LTE to stock 5.02 that had a unlocked bootloader with twrp custom recovery. Flashed it with mfastboot. Then I did a OTA system update. It rebooted to install and after that black screen. Is there any hope to unbrick with blankflash?
You didn't mention... Can't you boot into the fastboot screen? If so, I see no reason you cannot flash the factory image again. OTAs always scare me after a phone has been modified -- I've always avoided them at that point.
ya OP can you load recovery or the bootloader itself ?
xpmule said:
ya OP can you load recovery or the bootloader itself ?
Click to expand...
Click to collapse
No, won't boot into Fastboot, screen is blank
Read this: http://forum.xda-developers.com/moto-e-2015/general/danger-hard-brick-t3217358
simeydupes said:
I restored a Moto E LTE to stock 5.02 that had a unlocked bootloader with twrp custom recovery. Flashed it with mfastboot. Then I did a OTA system update. It rebooted to install and after that black screen. Is there any hope to unbrick with blankflash?
Click to expand...
Click to collapse
Try hard resetting the phone by pressing the power button for aeound 10 secs and if that doesn't help then ,if u have enabled Android debugging in the developer options then using fastboot type 'adb reboot bootloader'. And see if u can open the bootloader!
I'm an idiot and was tired... Make sure you run fastboot as Administrator...
Hi,
My Poco F1 was upgraded to Android Q using beryllium_global_images_V11.0.6.0.QEJMIXM_20200227.0000.00_10.0_global.tar.gz via MiFlash tool. In the background this just runs a batch script from the unpacked file.
Now I'm stuck with replacing the recovery. This simply won't work. OEM Locking/Unlocking doesn't help. Reverted back to Android 9 and still I can't install lineage-17.1-20200417-recovery-beryllium.img nor twrp-3.3.0-0-beryllium.img
It will report OKAY but a fastboot reboot recovery skips the recovery, and shutting down and starting with Vol-Up + Power, I get the MI-Recovery 3.0.
Any hints/tips appreciated!
spiloss said:
Hi,
My Poco F1 was upgraded to Android Q using beryllium_global_images_V11.0.6.0.QEJMIXM_20200227.0000.00_10.0_global.tar.gz via MiFlash tool. In the background this just runs a batch script from the unpacked file.
Now I'm stuck with replacing the recovery. This simply won't work. OEM Locking/Unlocking doesn't help. Reverted back to Android 9 and still I can't install lineage-17.1-20200417-recovery-beryllium.img nor twrp-3.3.0-0-beryllium.img
It will report OKAY but a fastboot reboot recovery skips the recovery, and shutting down and starting with Vol-Up + Power, I get the MI-Recovery 3.0.
Any hints/tips appreciated!
Click to expand...
Click to collapse
Have you unlocked the bootloader.......
stinka318 said:
Have you unlocked the bootloader.......
Click to expand...
Click to collapse
Yes, the bootloader is unlocked. Unlocking was the first thing I did after buying the device. Bootloader shows "Unlocked" too.
spiloss said:
Yes, the bootloader is unlocked. Unlocking was the first thing I did after buying the device. Bootloader shows "Unlocked" too.
Click to expand...
Click to collapse
Glad to see you have solved the problem.......
spiloss said:
I'm an idiot and was tired... Make sure you run fastboot as Administrator...
Hi,
My Poco F1 was upgraded to Android Q using beryllium_global_images_V11.0.6.0.QEJMIXM_20200227.0000.00_10.0_global.tar.gz via MiFlash tool. In the background this just runs a batch script from the unpacked file.
Now I'm stuck with replacing the recovery. This simply won't work. OEM Locking/Unlocking doesn't help. Reverted back to Android 9 and still I can't install lineage-17.1-20200417-recovery-beryllium.img nor twrp-3.3.0-0-beryllium.img
It will report OKAY but a fastboot reboot recovery skips the recovery, and shutting down and starting with Vol-Up + Power, I get the MI-Recovery 3.0.
Any hints/tips appreciated!
Click to expand...
Click to collapse
Can u tried cmd command fastboot boot twrp name and enter it will boot into twrp then u can manually install twrp
Here is a patched MSM download tool for TMobile OP7T Pro 5G McLaren.
It will bypass the need to sim unlock before unlocking the bootloader, and will also bypass the need of an unlock token file from OnePlus (hence skip the wait period of 1 week to get the privilege to unlock). It will NOT sim unlock the phone.
1) Download the patched MSM download tool: http://www.mediafire.com/file/6r6vn...04+patched+for+easy+bootloader+unlock.7z/file
EDIT: 10.0.39 version: http://www.mediafire.com/file/vdphi4ncs9alxv6/hotdogg_13_A.01_200915_patched_10.0.39.7z/file
2) Run the tool, select "other" in "Login type", click Next, connect your phone in EDL mode, ensure the "sha256 check" is NOT checked, select "TMO" in the Target dropdown, click the Start button and wait until it's completed.
3) The phone will show a red warning saying "device is corrupt", just ignore that and wait some time. It will fallback in fastboot because it's not able to boot. Update your fastboot executable, otherwise fastboot might not recognise the following command. Download it here: https://dl.google.com/android/repository/platform-tools-latest-windows.zip. Now run the following fastboot command, and follow the instructions on the screen of the phone:
Code:
fastboot flashing unlock_critical
4) Bootloader is now unlocked.
5) If you want to be able to boot, you'll probably need to flash again the boot.img of the rom. Download it here: http://www.mediafire.com/file/37rl13s60rsqy5m/boot.img/file
EDIT: 10.0.39 boot.img : http://www.mediafire.com/file/tt6c58u519d8ktc/boot.img_10.0.39.7z/file
And run the command:
Code:
fastboot flash boot boot.img
6) Run "fastboot reboot".
Thread re opened by moderators.
The placeholder for the link has now been replaced by the actual link to download the tool.
Could you use this tool to flash mclaren 7t pro Global to tmo version? Even if it means giving up 5g?
So with this you would not need to contact TMobile to permanent unlock and the OEM unlock the phone? And you would also not need to get the unlock code from OnePlus for the bootloader?
inneyeseakay said:
Could you use this tool to flash mclaren 7t pro Global to tmo version? Even if it means giving up 5g?
Click to expand...
Click to collapse
It doesn't work like that.
And this thread is not about converting the phone to international.
t436h05t said:
So with this you would not need to contact TMobile to permanent unlock and the OEM unlock the phone? And you would also not need to get the unlock code from OnePlus for the bootloader?
Click to expand...
Click to collapse
Yes and yes, that is explained in the first post.
Superboy58 said:
Yes and yes, that is explained in the first post.
Click to expand...
Click to collapse
when I open the tool is asking for account and password. how do I get that information?
noobiedev83 said:
when I open the tool is asking for account and password. how do I get that information?
Click to expand...
Click to collapse
Just click on Login type and select "Other" in the dropdown.
The tool will open without credentials.
Superboy58 said:
Just click on Login type and select "Other" in the dropdown.
The tool will open without credentials.
Click to expand...
Click to collapse
ok so I did it but im stuck in fastboot and the phone wont reboot to the os, any ideas?
---------- Post added at 04:42 PM ---------- Previous post was at 04:37 PM ----------
in fastboot mode under bootloader version I dont have anything in there and on Baseband either is blank. is that normal?
noobiedev83 said:
ok so I did it but im stuck in fastboot and the phone wont reboot to the os, any ideas?
---------- Post added at 04:42 PM ---------- Previous post was at 04:37 PM ----------
in fastboot mode under bootloader version I dont have anything in there and on Baseband either is blank. is that normal?
Click to expand...
Click to collapse
Install a ROM to be able to boot
Superboy58 said:
Install a ROM to be able to boot
Click to expand...
Click to collapse
how can you please help that im stuck in Fastboot
noobiedev83 said:
how can you please help that im stuck in Fastboot
Click to expand...
Click to collapse
If you don't know how to install a ROM you should not be using this tool.
Go in this forum section and read the posts, choose one of the available ROMs and install it.
https://forum.xda-developers.com/7t-pro-mclaren/development
Superboy58 said:
If you don't know how to install a ROM you should not be using this tool.
Go in this forum section and read the posts, choose one of the available ROMs and install it.
https://forum.xda-developers.com/7t-pro-mclaren/development
Click to expand...
Click to collapse
you never mention that you have to install a rom I tought I was going to unlock the phone but my os was going to stay ok!
you should post that in the thread because I didnt want to install any third party roms
Ok, I understand what happened.
I talked with the person who proposed to test the tool, @omariscal1019 , and we think you can't boot because you were for example on the rom 10.0.30 but you flashed this MSM which is based on 10.0.36 rom.
You might need to flash back only the boot.img of the 10.0.30 ROM.
I will extract boot and recovery partitions of each rom versions and post them on the first post of this thread.
Now that you are unlocked you only need to run
"fastboot flash boot boot.img" (not exactly sure of the syntax but it's close)
That will flash your boot partition
Superboy58 said:
Ok, I understand what happened.
I talked with the person who proposed to test the tool, @omariscal1019 , and we think you can't boot because you were for example on the rom 10.0.30 but you flashed this MSM which is based on 10.0.36 rom.
You might need to flash back only the boot.img of the 10.0.30 ROM.
I will extract boot and recovery partitions of each rom versions and post them on the first post of this thread.
Now that you are unlocked you only need to run
"fastboot flash boot boot.img" (not exactly sure of the syntax but it's close)
That will flash your boot partition
Click to expand...
Click to collapse
I was in the latest software update that tmobile release 2 days ago
Try this flash msm .36 the original one, then let it boot skip everything to home screen then msm the patched one then u can go from there it should work
omariscal1019 said:
Try this flash msm .36 the original one, then let it boot skip everything to home screen then msm the patched one then u can go from there it should work
Click to expand...
Click to collapse
Good suggestion, i think it should work.
If you're still stuck in fastboot, try the "fastboot continue" command.
Please share the results,
Thanks
Superboy58 said:
Good suggestion, i think it should work.
If you're still stuck in fastboot, try the "fastboot continue" command.
Please share the results,
Thanks
Click to expand...
Click to collapse
tested all the suggestions and no go, still get stuck in fastboot mode after trying to unlock bootloader with this tool.
noobiedev83 said:
tested all the suggestions and no go, still get stuck in fastboot mode after trying to unlock bootloader with this tool.
Click to expand...
Click to collapse
You say "after trying to unlock bootloader" which suggest the bootloader unlock failed ?
Does the fastboot mode shows unlocked bootloader ? If it's locked, that's normal that the phone is stuck in fastboot.
Have you tried to flash the original T-Mobile 10.0.36 MSM, then the patched 10.0.36 MSM?
Superboy58 said:
You say "after trying to unlock bootloader" which suggest the bootloader unlock failed ?
Does the fastboot mode shows unlocked bootloader ? If it's locked, that's normal that the phone is stuck in fastboot.
Have you tried to flash the original T-Mobile 10.0.36 MSM, then the patched 10.0.36 MSM?
Click to expand...
Click to collapse
well it shows that is unlock in the fastboot menu but it wont reboot to the os, is stuck in the fastboot mode and I already reflash the newest 10.0.36 msm and I try to patch again but no go.
I recently bought an unlocked Moto G Play 2021 with the intent of learning how to flash custom rom's etc. The steps I've done so far are below.
Went to Motorola's site and got the code to unlock the bootloader
Waited for the "OEM Unlock" button to be available in the Developer Options menu.
Followed the directions Here to try to get an unofficial version of TWRP installed.
when I type fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img Using the vbmeta.img from the link above, I get some kind of anti-rollback error and can't boot to recovery.img
So far, what I've found says I need to be on Android 10 for this to work but I can't find a stock rom of Android 10 for this device. Electimon posts AOSP builds for this phone Here so I assume there's a way to get this to work, I just don't know what it is and I've gone through these threads a few times now and can't piece it together. Any assistance would be greatly appreciated.
Additionally, thanks Electimon for doing those AOSP builds.
Try to download Miracle Thunder Modified (Withouth Box) like there are other tools, but if not, just try to root. kind of for you to root, download the TWRP app and install or use Flashify to flash img using root
Luiz Vinicius said:
Try to download Miracle Thunder Modified (Withouth Box) like there are other tools, but if not, just try to root. kind of for you to root, download the TWRP app and install or use Flashify to flash img using root
Click to expand...
Click to collapse
I'm not sure entirely what happened, but after I used the TWRP app my phone bricked and I had to use the Lenovo rescue app on my pc to factory reset it.
First update your phone
Then download twrp from
https://forum.xda-developers.com/t/...st-port-but-everything-works-amazing.4330775/
Then adb reboot bootloader
Then fastboot flash recovery MotoGuamnaFixed2.img
then you have twrp installed then you can go thru the steps at
https://forum.xda-developers.com/t/rom-12-0-guamna-aosp-12-0-monthly-builds.4392303/#post-86610039
to get Android 12 couatom rom
svoc said:
First update your phone
Then download twrp from
https://forum.xda-developers.com/t/...st-port-but-everything-works-amazing.4330775/
Then adb reboot bootloader
Then fastboot flash recovery MotoGuamnaFixed2.img
then you have twrp installed then you can go thru the steps at
https://forum.xda-developers.com/t/rom-12-0-guamna-aosp-12-0-monthly-builds.4392303/#post-86610039
to get Android 12 couatom rom
Click to expand...
Click to collapse
Thank you for the response!
I made sure my phone was on wi-fi and checked for updates. I then rebooted to fastboot and flashed recovery to the MotoGuamnaFixed2.img. I still got a blank screen when I tried to reboot to recovery. I then rebooted to fastboot manually and did
fastboot flash recovery_a MotoGuamnaFixed2.img
fastboot flash recovery_b MotoGuamnaFixed2.img
It said ok both times, and when I try to reboot to recovery, I get a blank screen that I can't interact with. Pressing the power and volume buttons does nothing. Rebooting and letting the phone go through the boot process, to include waiting for the warning about the unlocked bootloader to go away results in a blank screen.
I also tried booting to fastboot and selecting "Recovery Mode" from the fastboot menu. Same result. That being said, I followed the instructions in the second link anyway, which are
fastboot -w
fastboot update (filename).zip
Now my phone has a blank screen I cannot interact with, but when I type "adb devices" I see the phone. Typing "adb shell ls -l" shows there is definitely a file structure there.
Just download the rom for the version that your device is unzip it and manual flash each one to the correct spot except recovery flash the twrp and then reboot and let me know look at flash file.xml to see where to flash each IMG and bin to make shur you download your rom and not another one for the same device but different carrier what it sounds like to me is happening is you downloaded the wrong ROM when you tried to do a force update
Send me a screenshot of your about device screen please I might need to make a change to a few things to get it working
I'm stuck in a boot loop right now. WIll the output from fastboot getvar work?
What carrier do you have
Download your rom first then follow my last post to get it back out of a bootloop
svoc said:
What carrier do you have
Click to expand...
Click to collapse
It's an unlocked phone, no carrier, no SIM. I did the factory reset with the Lenovo rescue tool and sent you the screen shot of the device info page.
Update - svoc has spent a crap ton of his personal time trying to help me with this. I've learned a bunch and wanted to publicly acknowledge his willingness to go way above and beyond trying to get this working.
I don't understand why I can't get twrp to boot I'm not for shut what the problem is if any one has any idea please let me and I will try
Big thanks to svoc for all the phone calls and troubleshooting my device, that is apparently possessed by at least 3 demons and a donkey. There are two links below. The first is the link to the intstructions that worked.
The second is to the compressed file that gave me a degoogled android. It's really, really basic and you'll have to side load the app store of your choice onto the device but it works.
*NOTE* I have not used a sim card or tested the cellular capability. If you do the things below and it doesn't work, reboot to bootloader and flash the radio.img with the one from your stock rom, which can be obtained from lolinet.
Any custom ROMs out there for Moto g play 2021 (guamna)?
Can't find any custom ROMs for this device. I guess it is too early. I'll probably have to get another phone. Can't even find a twrp for it. New to this. Any suggestions?
forum.xda-developers.com
https://github.com/phhusson/treble_experimentations/releases/download/v412/system-squeak-arm64-ab-vanilla.img.xz
My Zenfone9 AI2202 (JP) Stopped at bootloader screen.
When I select recovery, it reboots and goes back to "Start" screen.
I used the following as a reference
Rooting Zenfone 9 with Magisk
Guide has been reworked to be more clear and based on comments. [Part One] Backup Data Update phone to latest version [Part Two] Download the Firmware for the Zenfone 9...
forum.xda-developers.com
Steps
- I have implemented the following steps
- Update OTA with Version WW-33.0804.2060.113 (2023/03/31)
- Download Same version of firmware
- dump boot.img using Payload Dumper GUI
- I patched boot.img with Magisk
- Execute the following command.
$fastboot flash boot patched_boot.img
I fell into a bootloop.
It is recognized as a fastboot device by Windows11.
Tried
I flashed boot.img before modifying it with Magisk.
Maybe I had wrong version on my device.
ASUS Flash Tool v2.0.1.0 only recognizes it as State: Fast boot device
I referred to the following
https://www.getdroidtips.com/asus-zenfone-9-ai2202-firmware-flash-file/
It says I can select "apply update from sd card." in Recovery mode,
But when I press the power button in Recovery mode, it reboots and won't let me enter recovery mode.
Question
How do I write the whole firmware?
I wish there was a flash-all.bat in the firmware like in Pixel series...
couldn't start from TWRP
$fastboot oem device-info
Device unlocked: false
The device may not have been successfully unlocked.
But then shouldn't fastboot flash boot boot.img fail?
Can boot.img be written without unlocking?
pompom252 said:
couldn't start from TWRP
Click to expand...
Click to collapse
I couldn't boot twrp after flashing magisk too until i remove magisk completely
pompom252 said:
My Zenfone9 AI2202 (JP) Stopped at bootloader screen.
When I select recovery, it reboots and goes back to "Start" screen.
I used the following as a reference
Rooting Zenfone 9 with Magisk
Guide has been reworked to be more clear and based on comments. [Part One] Backup Data Update phone to latest version [Part Two] Download the Firmware for the Zenfone 9...
forum.xda-developers.com
Steps
- I have implemented the following steps
- Update OTA with Version WW-33.0804.2060.113 (2023/03/31)
- Download Same version of firmware
- dump boot.img using Payload Dumper GUI
- I patched boot.img with Magisk
- Execute the following command.
$fastboot flash boot patched_boot.img
I fell into a bootloop.
It is recognized as a fastboot device by Windows11.
Tried
I flashed boot.img before modifying it with Magisk.
Maybe I had wrong version on my device.
ASUS Flash Tool v2.0.1.0 only recognizes it as State: Fast boot device
I referred to the following
https://www.getdroidtips.com/asus-zenfone-9-ai2202-firmware-flash-file/
It says I can select "apply update from sd card." in Recovery mode,
But when I press the power button in Recovery mode, it reboots and won't let me enter recovery mode.
Question
How do I write the whole firmware?
I wish there was a flash-all.bat in the firmware like in Pixel series...
Click to expand...
Click to collapse
Did you unlock your phone via Asus unlock app tool?
this is the link thread to restore back to stock
ZenFone 9 (AI2202) Repair to bootloader package
Download: Link 🔗 Steps: 1. Only works on EDL mode. 2. Run script 0-8475_update_image_EDL_fh_loader.bat 3. Update Official OTA package in recovery or install UserRAW in bootloader Thanks ASUS Taiwan, @EdwardWu6688 , and don't use it for...
forum.xda-developers.com
and for future reference, do not ever ever EVER
"Fastboot boot twrp.img"
Read the thread below, Asus have boot protection so fastboot boot is blocked and can lead to brick
[RECOVERY][OFFICIAL] TWRP for ASUS ZenFone 9
Official TWRP is now available: https://twrp.me/asus/zenfone9.html IMPORTANT NOTES: CleanSlate custom kernel is not currently compatible with TWRP for this device (Kirisakura is compatible as of v2.0.6). This device has a recovery partition (2...
forum.xda-developers.com
Jairus980 said:
and for future reference, do not ever ever EVER
"Fastboot boot twrp.img"
Read the thread below, Asus have boot protection so fastboot boot is blocked and can lead to brick
[RECOVERY][OFFICIAL] TWRP for ASUS ZenFone 9
Official TWRP is now available: https://twrp.me/asus/zenfone9.html IMPORTANT NOTES: CleanSlate custom kernel is not currently compatible with TWRP for this device (Kirisakura is compatible as of v2.0.6). This device has a recovery partition (2...
forum.xda-developers.com
Click to expand...
Click to collapse
Thanks for the reply.
Yes, I used Asus unlock app tool.
However, seeing that it is not locked, it may be that the unlocking was not successful.
I have attached a screenshot.
Is an EDL cable required to enter EDL mode?
pompom252 said:
Thanks for the reply.
Yes, I used Asus unlock app tool.
However, seeing that it is not locked, it may be that the unlocking was not successful.
I have attached a screenshot.
Is an EDL cable required to enter EDL mode?
Click to expand...
Click to collapse
adb dont work while on fastboot mode, you cant do via "adb"
I suggest you read the thread above
"ZenFone 9 (AI2202) Repair to bootloader package"​
Take your time to read one by one
Jairus980 said:
adb dont work while on fastboot mode, you cant do via "adb"
I suggest you read the thread above
"ZenFone 9 (AI2202) Repair to bootloader package"​
Take your time to read one by one
Click to expand...
Click to collapse
Thank you very much. In the relevant thread, you had the information after exchange about whether "EDL cable" is needed or not.
It is important to read carefully.
I solved the problem by running "flashall_AFT.cmd" with device recognized as fastboot device.
Android 12 is now booted!
I was worried that IMEI would disappear, but I was able to keep IMEI.
My device was purchased in Japan, so it was equipped with Felica, which could also continue to be used.
Thank you very much for your good advice.