Quick notes:
ALL files/software needed are linked below
Process only confirmed working for this model, A2017U
Desktop PC used is on Windows 10 x64, no 3rd Party Antivirus
I assume you have ADB installed on your computer, but if not here is an easy guide:
https://forum.xda-developers.com/showthread.php?p=48915118#post48915118
Also assumed you have the Axon7 connected to PC via USB cable
Here's the steps I took, with info compiled and reorganized from the two guides linked at bottom of post:
1. The downgrade from B15 Nougat to B29 Marshmallow
(skip to step 2 if you are already on B29)
A- Download the full B29 software package, provided by ZTE on their website. Select the support tab halfway down the page, then select the software updates to download the .ZIP (mirror provided at bottom in case ZTE changes things)
B- Download it, unzip it once, then put the update.zip file on your SD card.
C- Turn on OEM unlocking in the Axon Settings Menu (it is needed to flash from sd card)
You can do this by navigating to Settings -> About phone -> Tap "Build number" 7 times.
Now navigate to Settings -> Advanced settings -> Developer options -> Enable "OEM unlocking".
D- Boot phone to recovery - [Power] + [Volume Up] key combo - Release the keys when you see the ZTE logo.
E- Choose update from sd card, then pick the update.zip from the sdcard
F- The phone will flash the B29 software. It is a bit slow, have patience and let it do what it needs to do.
2. Unlocking Bootloader and installing TWRP
A- Install the Qualcomm QUSB_BULK drivers. You should be able to simply extract them, then right click qcser.inf and press Install.
B- Boot the Axon7 into EDL mode. [Power] + [Volume Up] + [Volume Down]
C- Your device should be recognized in Windows’ Device Manager as a COM port called "Qualcomm HS-USB QDLoader 9008".
D- Download and Unzip the FASTBOOT_UNLOCK EDL file.
E- Install MiFlash on your computer. Open the program.
F- In MiFlash, Select the folder "A2017U_FASTBOOT_UNLOCK_EDL". Use the child folder inside containing fastboot.img and other files. Do not use the parent folder containing the META-INF folder, it caused flashing to fail for me.
G- Now just hit [flash] - watch the progress bars move and wait for the device row to turn green with flash complete!
H- Use [Power] + [Volume Up] key combo to exit EDL mode and enter recovery
I- Open CMD window as admin, and use "fastboot oem unlock" command to unlock (and wipe) your device. When prompted on Axon7, select Yes to unlock bootloader
J- Reboot phone into EDL mode
K- Return to MiFlash, Select the folder "A2017U_B29_TWRP_EDL". Click [refresh] if device row shows anything under status.
L- Now just hit [flash] like before - watch the progress bars move and wait for the device row to turn green with flash complete!
M-Reboot phone to TWRP
If the flash fails or is unable to communicate with the device, use the [Power] + [Volume Up] + [Volume Down] key combo to restart EDL mode.
Release the keys after 5 seconds then wait another 5 seconds before using the [refresh] or [flash] buttons on MiFlash.
3. Installing Lineage OS With Root
A- Using TWRP, Wipe the device (data/cache/dalvik, all that stuff)
B- Install the Universal Bootloader (A2017X_B15_Universal_Bootloader.zip), and modem (A2017U_N_Modem.zip)
C- Install Lineage OS ROM .zip, with root addon (addonsu-arm64-signed.zip)
D- Install Gapps
E- Restart Axon7, enjoy!
Thanks to the reply made by u/tabletalker7 on my last thread, I now have an unlocked bootloader, TWRP, and LineageOS with root. 10/10 !
DOWNLOADS:
Official ZTE B29 Marshmallow Software Package:
ZTE Website
Gdrive Mirror
Qualcomm QUSB_BULK Drivers: (WHQL certified)
Click here to download
FASTBOOT_UNLOCK EDL Package:
Click here to download
TWRP for A2017U EDL Package:
Click here to download
Universal Bootloader and Modem packages for A2017U:
Click here to download
Lineage Official Builds:
Click here to download
Lineage OS root addon:
Click here to download
Open GApps: (arm64) (use 7.1 if using Lineage 14.1)
Click here to download
CREDITS:
[OFFICIAL] LineageOS 14.1 for ZTE Axon 7 by Unjustified Dev:
https://forum.xda-developers.com/axon-7/development/unofficial-lineageos-14-1-zte-axon-7-t3545679
[EDL][A2017/A2017U] Emergency DL Mode TWRP + Unlock + Upgrade By jcadduono:
https://forum.xda-developers.com/axon-7/development/edl-emergency-dl-mode-twrp-unlock-t3553514
Downgrading is not necessary.
Downgrading step is not necessary, upgrading Bootloader and modem neither.
So, is the bootloader unlockable on Nougat? Could someone link me to a guide?
sdaddy said:
So, is the bootloader unlockable on Nougat? Could someone link me to a guide?
Click to expand...
Click to collapse
A-Yes
B- Read from post #1
I am getting an error when I try to flash FASTBOOT_UNLOCK EDL with MiFlash. Error is "can not found file flash_all_except_storage.bat". Anyone else seeing this?
Now make a guide to go back to stock
lafester said:
Downgrading is not necessary.
Click to expand...
Click to collapse
The fewer steps the better, of course.
So if we are on B15, we can just skip section 1 of the guide, and the rest of the steps will work without the downgrade to B29?
Excited to try this, since I've used CM ever since it was the cat's pajamas on the HTC G1/Dream but haven't even rooted the Axon 7 yet.
im getting "cannot read hello packet" and failing write
Unlocking problem
Hi guys
i flashed the "A2017U_FASTBOOT_UNLOCK_EDL" successfully but i could't run the "fastboot oem unlock" in cmd ...Then i flashed the "A2017U_B29_TWRP_EDL"
and now i can't enter to recovey ( neither stock nor twrp)
is there anyone can help me...:crying:
mortkarg5 said:
Hi guys
i flashed the "A2017U_FASTBOOT_UNLOCK_EDL" successfully but i could't run the "fastboot oem unlock" in cmd ...Then i flashed the "A2017U_B29_TWRP_EDL"
and now i can't enter to recovey ( neither stock nor twrp)
is there anyone can help me...:crying:
Click to expand...
Click to collapse
https://forum.xda-developers.com/axon-7/development/edl-emergency-dl-mode-twrp-unlock-t3553514
vinicioh23 said:
Now make a guide to go back to stock
Click to expand...
Click to collapse
Going back to stock is easy peasy.
use the official update from ZTE, place update.zip on sdcard
boot to recovery and wipe (cache/data/system) then flash update.zip
reboot and you're back to stock
want to lock the bootloader too?
boot to fastboot
fastboot oem lock
sauerkraut17 said:
Going back to stock is easy peasy.
use the official update from ZTE, place update.zip on sdcard
boot to recovery and wipe (cache/data/system) then flash update.zip
reboot and you're back to stock
want to lock the bootloader too?
boot to fastboot
fastboot oem lock
Click to expand...
Click to collapse
Thanks!
I can flash the fastbook unlock in MiFlash, but I get stuck trying to actually unlock the bootloader afterwards. ADB recognizes the device when it's turned on, but when it's in recovery, it doesn't recognize it at all. So I am lost as to what to do.
Edit: Alright, I got it to work. I just went into bootloader and unlocked instead of recovery. Maybe I misread the instructions but all of your other instructions were spot on! Thanks
Is there any way to do this on a macbook?
williamthardy said:
https://forum.xda-developers.com/axon-7/development/edl-emergency-dl-mode-twrp-unlock-t3553514
Click to expand...
Click to collapse
I saw it before...
My problem began when i forget to install ADB drivers and flashed twrp before unlock bootloader by cmd
I can not boot into recovery
Neither android stock recovery nor twrp
Is there any way to flash the stock recovery in EDL mode?
I don't know how to delete my comments, but yohobojo helped me figure out my problems. Just chose reboot into bootloader in recovery screen.
mortkarg5 said:
I saw it before...
My problem began when i forget to install ADB drivers and flashed twrp before unlock bootloader by cmd
I can not boot into recovery
Neither android stock recovery nor twrp
Is there any way to flash the stock recovery in EDL mode?
Click to expand...
Click to collapse
Yes, there is a one flash installation fix. Installed B15-NEW_FULL (Nougat) twice to recover from failed LOS installs.
https://forum.xda-developers.com/axon-7/development/edl-emergency-dl-mode-twrp-unlock-t3553514
williamthardy said:
Yes, there is a one flash installation fix. Installed B15-NEW_FULL (Nougat) twice to recover from failed LOS installs.
https://forum.xda-developers.com/axon-7/development/edl-emergency-dl-mode-twrp-unlock-t3553514
Click to expand...
Click to collapse
Thank you bro...
I had flashed it before i send these posts...
But failed
I now need another way
After flashing the Fastboot unlock EDL, I can get into recovery but I get no indication my computer detects my phone when it is in recovery. Halp?
Related
This is long, but it's nice for noobs because it's detailed. It's honestly kind of fun, I promise. I'm assuming you have WINDOWS. This is based off of the guide by torxx!. It's modified because some of the info is outdated (you don't have to flash the boot.mg separately, for example). If you are NOT a noob you can just look at the "overview" for each step.
UNLOCKING YOUR DEVICE WILL WIPE YOUR DEVICE. THIS IS A SECURITY FEATURE. BACKUP FIRST.
Part 1- gaining unlock token
Overview: go to htcdev.com and unlock bootloader
Be sure you've turned off fast boot option in power menu; usb debugging should be on (settings -> developer options).
Go to http://www.htc.com/www/software/htc-sync-manager/[1] and install HTC SYNC. Alternatively, if you know what you're doing, you can install these drivers:
x86 http://www.mediafire.com/?qabo1tue2v1ky75 x64 http://www.mediafire.com/?8dl8s3l9mr6ggr9
Go on http://www.htcdev.com[4] and create yourself an account on HTCDEV.
Download these adb/fastboot files: http://d-h.st/RvD
Make a new folder anywhere. We'll use C:/fastboot as an example.
Extract the zip downloaded to the new folder
Go Here http://www.htcdev.com/bootloader/[6] and select "All Other Supported Models" and "then begin unlock bootloader" (check the boxes, click proceed, all that good stuff). YOU CAN IGNORE THE DIRECTIONS THAT THEY TELL YOU (and follow this guide instead).
Power off your phone. Power your phone on by holding power and volume down.
Highlight 'Fastboot' the volume buttons then press power to "select".
Plug your phone into your PC and open a Command Prompt. (windows XP - Click Start > Run > type CMD in box then press OK; Windows 7 - Click Start > type CMD in search box then press Enter) Change directory to your folder where we put fastboot files by typing cd c:\fastboot for example.*
*Alternatively, you can just hold down shift and right click in the folder and select "open command window here". Neat huh?
Type this into your command prompt window: fastboot oem get_identifier_token
Select & copy the text as per step 9 on the HTCDev website
Paste your identifier token into the box at the bottom and submit
You Will Very Shortly Receive an email from HTCDev with a link to the second part of the instructions and your "Unlock_code.bin" attached
Download the "Unlock_code.bin" from the email and save it to the same folder that we extracted fastboot files
Type this into your command prompt window: fastboot flash unlocktoken Unlock_code.bin
The Display Will change on your phone, press Vol+ to accept and power to confirm.
Part 2
Overview: flash your recovery. Boot into recovery. Turn phone off if it boots into OS. Boot into back into recovery. You're done!
Download a recovery:
TWRP (the one I use): http://forum.xda-developers.com/showthread.php?t=2173870
CWM 2: http://forum.xda-developers.com/showthread.php?t=2172979
CWM: http://forum.xda-developers.com/showthread.php?t=2173863
Place the Recovery file to the folder where the fastboot.exe is.
Same thing as above- boot (volume down + power) into the bootloader and highlight 'Fastboot' the volume buttons then press power to "select".
Do the same thing as with the command prompt above. This time, however, you'll be typing:
fastboot flash recovery "name_of_the_recovery.img"
For example:
fastboot flash recovery openrecovery-twrp-2.5.0.0-m7.img
then type:
fastboot erase cache
From the menu, boot into recovery (use volume to move up and down, power to select). The phone might boot to the OS instead of recovery, don't worry!
Turn off phone then turn on (while holding volume down) to boot back into the bootloader.
TAMPERED shows up, boot into recovery and now your recovery should be working!
Part 3- obtaining root
Overview: flash a super tool
Download a super user tool for root:
SuperSU (I use this one): http://forum.xda-developers.com/showthread.php?t=1538053
SuperUser: http://download.clockworkmod.com/superuser/superuser.zip
Alternatively, download this: http://forum.xda-developers.com/showthread.php?t=2252959. This is a stock rooted rom for ATT. If you download and flash this instead of the super user tool, you're done. (This rom includes super user) Or you can download a custom rom such as this one: http://forum.xda-developers.com/showthread.php?t=2183023
Turn on your phone again (and disable usb debugging) and connect to computer, copy the .zip super user tool to a location you remember ON the phone.
Flash it with the Recovery: Power off your device and then hold the VOL DOWN + Power to boot into the Bootloader Navigate with VOL and Power to Recovery Now flash the .zip:
- install zip from sdcard
- choose zip from sdcard
- select the downloaded SuperSU/SuperUser zip file and flash it
- Reboot now
You're not out of the woods yet! The stock kernel is system write protected, so you still can't modify it (changes won't "stick"). You'll have to flash a custom rom or a kernel if you want stock instead.
I recommend these kernels: http://forum.xda-developers.com/showthread.php?t=2255900 or http://forum.xda-developers.com/showthread.php?t=2233665&highlight=menu
Download it.
Installing custom rom/kernel ("flashing a rom")
Overview: Download Rom, boot into recovery and wipe and then flash.
According to Shenye, even though your device is s-on, you can still flash boot now. So just do this:
Turn on your phone again (and disable usb debugging) and connect to computer, copy the .zip kernel/cutom rom to a location you remember ON the phone.
Flash it with the Recovery: Power off your device and then hold the VOL DOWN + Power to boot into the Bootloader Navigate with VOL and Power to Recovery Now flash the .zip:
- install zip from sdcard
- choose zip from sdcard
- select the downloaded SuperSU/SuperUser zip file and flash it
- Reboot now
I feel like this title should be changed to clarify that it's unlocking the bootloader, not the SIM lock.
Just wanted to say this tutorial was 100% dead on and what I used to unlock bootloader and root/rom my One.
Oddity - Did everything, I've got root but I -AM- out of the woods. Was installing bulletproof mod through recovery but it kept failing due to missing a MD5 file or something -- Trying to work that out through that thread atm but anyway, rebooted the phone a couple of times now and I still have root, Tit back up works OR are we talking about things like CPU clocking won't work since it can't rewrite?
Sticking this.
Excellent tutorial. One thing to add:
If you flash the TWRP recovery you link to, after TWRP boots for the first time, if you reboot into System, TWRP will offer to install SuperSU for you; no need to find another to flash. Once the system reboots, you can launch the GUI installer to finish the SU install (it will boot into TWRP and back one more time to do the actual flash).
Does anyone know if this will work on the Rogers HTC One?
Thank you. Followed this last night. Worked flawlessly. The only thing that threw me was rebooting into recovery. It took maybe 3 or 4 reboots for it to say "TAMPERED" at the top. When it didn't say tampered, it would not boot to recovery.
TELUS?
DannySmurf said:
Excellent tutorial. One thing to add:
If you flash the TWRP recovery you link to, after TWRP boots for the first time, if you reboot into System, TWRP will offer to install SuperSU for you; no need to find another to flash. Once the system reboots, you can launch the GUI installer to finish the SU install (it will boot into TWRP and back one more time to do the actual flash).
Click to expand...
Click to collapse
Did you happen do run this tutorial on a TELUS device?
Viceroy_N said:
Does anyone know if this will work on the Rogers HTC One?
Click to expand...
Click to collapse
Yes it does. I have a Rogers phone, and it worked perfectly.
richnanaimo said:
Did you happen do run this tutorial on a TELUS device?
Click to expand...
Click to collapse
No, I have a Rogers device. But the procedure should not be any different.
followed step by step and got an error that says submitted token wrong length
I'm on ubuntu 13.04 and I get stuck at getting the token. I type in fastboot oem get unlock_identifier_token and it says waiting for device. Tried it with sudo and it says error and sudo ./fastboot and it says no such command.
Sent from my HTC One using xda app-developers app
Having a really odd problem. I flash the twrp recovery per instructions. I try to reboot to recovery and it seems to try and then, blam, the att boot.
I have tried this from the bootloader, selecting Recovery, as well as from a booted stated using "adb reboot recovery".
Any hints for me? I originally had a silver One and today got my Black One replacement,. Had no issues on the original one. Hmm. Guess I will try CWM.
FYI: Yes I unlocked the bootloader and it says Unlocked in there
-I also notice that I seem to go right into fastboot, when I boot the bootloader. Now, I believe that is normal if you have the usb cable attached, but this happens regardless.
-flashed stock recovery back and can get into it. trying twrp again, renaming the file to "recovery.img" just because...and it worked on that stock recovery file
-Also, very hard to get into bootloader from powered off state. I may flash RUU_M7_UL_JB_50_Cingular and see if it helps me.
OK, maybe it is the phone or ATT has done something screwy on the latest. I can not even get the RUU install to pass inspection. Wants me to check the connection. I know all my stuff is in order, as I did this all on the previous one. grrr
-Just noticed mine does say Unlocked but it does not say Tampered.
-Crazy. I decided to get a new Unlock token and redo the unlock with it. Now, the bootloader finally says Tampered and I got into TWRP. I have no idea why, since I would think that if the original Unlock token was incorrect, it would not have unlocked the phone.
So, rather than providing worthwhile information for anyone else having problems, I think this post is probably deletable and that is fine by me should the powers so decide.
How would one go back to locking the device for a return?!?
Sent from my Nexus 4 using xda premium
tacotino said:
How would one go back to locking the device for a return?!?
Sent from my Nexus 4 using xda premium
Click to expand...
Click to collapse
fastboot oem lock
but, it will say relocked. nobody cares or seems to check. also, it will say tampered until you restore a stock ruu to flash. I used RUU_M7_UL_JB_50_Cingular.exe for mine when switching from silver to black. it is the right one for att. sorry, don't have the link to the download anymore.
great writeup! quick comment though, just helped my brother unlock his phone. i had a similar issue to @Barsky above so I decided to try to reflash the recovery. The first time I used the line fastboot erase cache after flashing the recovery and I think that's what caused it to not boot into recovery. The second time I flashed TWRP, I didn't enter that line and voila it worked on the first try!
can anyone post a mirror of the dev host files? devhost seems to be down.
nice...
help please
I seem to be stuck in recovery after installing super su/ rom. I messed up the order and did the rom then su. Any ideas on how I can get it to boot? I tried installing clean rom 2.5 and used the su file i found here ----> http://www.teamandroid.com/2013/03/17/root-htc-one-supersu-android-41-jelly-bean-tutorial/2/
any help is greatly appreciated... I just want my phone back
---------- Post added at 09:44 AM ---------- Previous post was at 09:36 AM ----------
also, i did hit factory reset under bootloader/fastboot screen (where it says tampered/unlocked),
mbroch89 said:
I seem to be stuck in recovery after installing super su/ rom. I messed up the order and did the rom then su. Any ideas on how I can get it to boot? I tried installing clean rom 2.5 and used the su file i found here ----> http://www.teamandroid.com/2013/03/17/root-htc-one-supersu-android-41-jelly-bean-tutorial/2/
any help is greatly appreciated... I just want my phone back
---------- Post added at 09:44 AM ---------- Previous post was at 09:36 AM ----------
also, i did hit factory reset under bootloader/fastboot screen (where it says tampered/unlocked),
Click to expand...
Click to collapse
I think the last bit was your problem. You can't factory reset from bootloader. Try to push twrp again in fastboot then load/flash clean romantic, then boot up. It already has root so you don't need to push su.
Sent from my HTC One X using xda app-developers app
Are there other ways to flash a recovery with a locked bootloader?
My Problems:
I can't flash my stock recovery through fastboot with a locked bootloader.
I can't boot into my recovery because my current recovery is TWRP 2.5.0.1 and I have a locked bootloader.
I can't unlock my bootloader because I have used an IMEI Hack Tool and set my IMEI to 0 (I guess).
I can't boot into my ROM because I used an IMEI Hack Tool.
I can't Force Upgrade too (Vol Up + Down + Power). It only shows a pink/purple screen.
Solutions:
I can only flash a recovery with an unlocked bootloader.
I can only boot into a recovery with an unlocked bootloader (except for stock).
I can only unlock bootloader if my IMEI has restored.
I can only restore my IMEI if I can boot into my ROM.
I can only boot into my ROM if I have a stock recovery.
I can only Force Upgrade if I have restored my IMEI.
If I could only restore my IMEI through fastboot, that would be great!
So, please help!
You cant restore stock recovery ?
You cant enter to trwp ?
You cant restore IMEI cuz rom bootloop ?
You cant force flash stock firmware cuz fastboot is pink ?
I also "zero" my imei many times to flash stock firmware, but i allways can enter trwp and restore buckup or flash rom in zip
OmenHTX said:
You cant restore stock recovery ?
You cant enter to trwp ?
You cant restore IMEI cuz rom bootloop ?
You cant force flash stock firmware cuz fastboot is pink ?
I also "zero" my imei many times to flash stock firmware, but i allways can enter trwp and restore buckup or flash rom in zip
Click to expand...
Click to collapse
I can force upgrade now since i formatted my sd card. But the force upgrade fails at step 2/2.
.vonpatrick. said:
I can force upgrade now since i formatted my sd card. But the force upgrade fails at step 2/2.
Click to expand...
Click to collapse
If upgrade fail as step 2/2 your IMEI its not "zero" cuz IMEI block upgrading firmware from branded to nonbranded
OmenHTX said:
If upgrade fail as step 2/2 your IMEI its not "zero" cuz IMEI block upgrading firmware from branded to nonbranded
Click to expand...
Click to collapse
If my imei is not zero, then why can't i boot my phone?
And why can't i unlock my bootloader with my unlock code?
.vonpatrick. said:
If my imei is not zero, then why can't i boot my phone?
And why can't i unlock my bootloader with my unlock code?
Click to expand...
Click to collapse
OK, lest start from beggining
1.You must unlock bootloader by code ( first run check Lock / Unlock status ) (fastboot mod)
2. Flash TRWP (fastboot mod)
3. Flash SuperSU or Superuser zip (trwp)
4. Backup IMEI on running rom
5. Hack IMEI on running rom
6. Update phone by forceupdate flash update.app (rom in root of sd card > folder dload > update.app)
7. Run stock rom , lest install, shut down phone
8. Run TRWP to install SuperSU/Superuser zip
8. Restore IMEI (on working rom)
9. Go to TRWP and Wipe dalvik cache
10. Now you have working newest stock rom with root
So :
1. You cant have trwp in lockedbootloader
2. If update fail on 2/2 IMEI is not "zero"
3. Pink LCD on "update mod" = no rom in sd card
Next :
Hold Vol Down + Vol Up + Power to forceupdate firmware mod
Hold Vol Up + Power to run TRWP or stock recovery ( hold about 5s)
Hold Vol Down + Power for fastboot mod (5s-10s)
If you now have locked bootloader , with stock recovery, and force update fail, you cant unlock bootloader and flash trwp > Last hope is in "oryginal" rom, your IMEI will not block it.
OmenHTX said:
OK, lest start from beggining
1.You must unlock bootloader by code ( first run check Lock / Unlock status ) (fastboot mod)
2. Flash TRWP (fastboot mod)
3. Flash SuperSU or Superuser zip (trwp)
4. Backup IMEI on running rom
5. Hack IMEI on running rom
6. Update phone by forceupdate flash update.app (rom in root of sd card > folder dload > update.app)
7. Run stock rom , lest install, shut down phone
8. Run TRWP to install SuperSU/Superuser zip
8. Restore IMEI (on working rom)
9. Go to TRWP and Wipe dalvik cache
10. Now you have working newest stock rom with root
So :
1. You cant have trwp in lockedbootloader
2. If update fail on 2/2 IMEI is not "zero"
3. Pink LCD on "update mod" = no rom in sd card
Next :
Hold Vol Down + Vol Up + Power to forceupdate firmware mod
Hold Vol Up + Power to run TRWP or stock recovery ( hold about 5s)
Hold Vol Down + Power for fastboot mod (5s-10s)
If you now have locked bootloader , with stock recovery, and force update fail, you cant unlock bootloader and flash trwp > Last hope is in "oryginal" rom, your IMEI will not block it.
Click to expand...
Click to collapse
Wait, let me put this in summary:
1.
- I have a locked bootloader.
- I can't unlock the bootloader because it says "recovery image verify failed".
- It can only mean one thing: my IMEI must have changed.
2.
- I have a TWRP recovery.
- At first, my original recovery was the stock when I have a locked bootloader.
- Then I flashed the TWRP recovery even if I have a locked bootloader and didn't warned me. (Shoudn't it be accepted to be flashed since I have a locked bootloader).
- In my experience, if I have a stock recovery when I'll hack my IMEI, it will format my cache and data and let me boot into my phone.
- If I have a TWRP recovery when I'll hack my IMEI, it will only redirect me to the TWRP menu.
3.
- I can access Force Upgrade.
- But it doesn't show any text. (For example: it doesn't show if it is unpacking or installing, only a bar.)
- When I access Force Upgrade, the loading stops at 1/4 of the bar. (So I'm not really sure if it failed at step 2/2.)
So my questions are:
1. Why can't I unlock my bootloader with my original IMEI's unlock code if my IMEI is not "zero"?
2. Why is it when I Force Upgrade, it doesn't show any text?
3. Why did fastboot accepted the TWRP recovery being flashed when my bootloader was locked?
And, what do you mean by "original"? Do you mean the B182 firmware upgrade, not the B175?
After hacking IMEI you cant have stock recovery, cuz you need root for shell script. So its not making "auto wipe" to change OEM info.
TRWP should not be installed on lockbootloader, but i dont make it ...
So , do you have working trwp or not ?
Oryginal firmware ... version when you get with phone, like my Y300-0100 branded T-Mobile PL B167
OmenHTX said:
After hacking IMEI you cant have stock recovery, cuz you need root for shell script. So its not making "auto wipe" to change OEM info.
TRWP should not be installed on lockbootloader, but i dont make it ...
So , do you have working trwp or not ?
Oryginal firmware ... version when you get with phone, like my Y300-0100 branded T-Mobile PL B167
Click to expand...
Click to collapse
I am sure i have twrp.
If i have a stock recovery, i would be able to boot into recovery.
Based in my experience:
1. To hack the imei, you must first root your phone.
2.a. Next, the phone will reboot, but it won't boot into system.
2.b. Fastboot, force upgrade, and recovery is still accessible.
3.a. If you have a twrp recovery when you hacked the imei and rebooted, it will redirect you to the twrp menu.
3.b. If you tried to restore from twrp recovery, it still won't reboot into system.
3.c. If you have a stock recovery, it will directly boot into stock recovery and format your cache and data and reboot to system (still leaves your imei to zero)
4. If you go to force upgrade, you can flash any official roms (leaves your imei to zero)
5. After you have flashed a rom or was redirected to stock recovery, your phone will reboot.
6.a. Then root your phone and restore imei then your phone will reboot.
6.b. If you have a stock recovery, it will wipe your cache and data.
6.c. If you have a twrp recovery, it will redirect you to the twrp menu (you can manually reboot into system)
Am i right?
And where can i get the original rom for my b182? There's no local huawei store here.
.vonpatrick. said:
I am sure i have twrp.
If i have a stock recovery, i would be able to boot into recovery.
Click to expand...
Click to collapse
So why you dont run TRWP and flash any rom in zip ?
OmenHTX said:
So why you dont run TRWP and flash any rom in zip ?
Click to expand...
Click to collapse
Twrp is not accessible if you have a locked bootloader.
bricked
I have a big problem. My Ascend y300 started to work strange yesterday, my PC didnt see the internal sd nor the external SD correctly. Today I restarted it and now I get blue screen when I start it. I had TWRP installed, but when I try to access it, it gives blue screen aswell. Any solutions?
gery0518 said:
I have a big problem. My Ascend y300 started to work strange yesterday, my PC didnt see the internal sd nor the external SD correctly. Today I restarted it and now I get blue screen when I start it. I had TWRP installed, but when I try to access it, it gives blue screen aswell. Any solutions?
Click to expand...
Click to collapse
Try this through fastboot:
fastboot erase recovery
fastboot flash recovery <path to recovery.img>
.vonpatrick. said:
Try this through fastboot:
fastboot erase recovery
fastboot flash recovery <path to recovery.img>
Click to expand...
Click to collapse
My problem is a little bit more complex unfortunately. I tried what you said. When I push the buttons to enter fastboot, my phone dont freez at splashscreen and I get bluescreen. When I connect it to my PC my PC recognizes it though, BUT ADB cant see it. I reinstalled the drivers any times, without success.
gery0518 said:
My problem is a little bit more complex unfortunately. I tried what you said. When I push the buttons to enter fastboot, my phone dont freez at splashscreen and I get bluescreen. When I connect it to my PC my PC recognizes it though, BUT ADB cant see it. I reinstalled the drivers any times, without success.
Click to expand...
Click to collapse
What did you do anyway why it got the blue screen?
.vonpatrick. said:
What did you do anyway why it got the blue screen?
Click to expand...
Click to collapse
That is the most strange part of the story. I totally did nothing. I opened bootloader, installed twrp, rooted it, installed init.d support, installed a ramscript. The phone worked totally fine until yesterday. I did a restart yesterday and bumm, bluescreen. And I did nothing before this happened. Srsly, no problems detected, it came from nothing...
gery0518 said:
That is the most strange part of the story. I totally did nothing. I opened bootloader, installed twrp, rooted it, installed init.d support, installed a ramscript. The phone worked totally fine until yesterday. I did a restart yesterday and bumm, bluescreen. And I did nothing before this happened. Srsly, no problems detected, it came from nothing...
Click to expand...
Click to collapse
Can't you really boot into fastboot (Power + up)?
Hold it for like 10 seconds.
If it still shows blue screen, try connecting it to pc, maybe it'll read it.
Then erase recovery and flash twrp.
Wipe everything and restore a backup you made.
.vonpatrick. said:
Can't you really boot into fastboot (Power + up)?
Hold it for like 10 seconds.
If it still shows blue screen, try connecting it to pc, maybe it'll read it.
Then erase recovery and flash twrp.
Wipe everything and restore a backup you made.
Click to expand...
Click to collapse
Well, my problem is, that despite of the blue screen, fastboot seems to work. My pc sees my device, BUT ADB refuses to see it, and I dont know why. I will try it from win xp under virtualbox now.
hi Gery
How do you manage to get the phone into fastboot mode?
my y300 also enters blue screen everytime now. I try to press voldown + power for like 10 seconds, yet the fastboot command is not working.
gery0518 said:
Well, my problem is, that despite of the blue screen, fastboot seems to work. My pc sees my device, BUT ADB refuses to see it, and I dont know why. I will try it from win xp under virtualbox now.
Click to expand...
Click to collapse
Well, that's perfect! If the PC can read the device from fastboot, you can erase the recovery and flash the twrp and restore from backup. But if it still goes blue, flash the system, data, cache, boot, recovery from your twrp backup.
Hello Guys,
I was trying to install OxygenOS 3.1.0 when I was on Sultanxda's CM13 but instead bricked the device.
What I did:-
1. Rebooted to TWRP and flashed stock OOS recovery and then clicked reboot into recovery.
2. Instead of rebooting in recovery my phone got stuck at the OnePlus logo.
3. I booted into fastboot to flash twrp.img but it says 'writing 'recovery'...
FAILED (remote: device is locked. Cannot erase)'
4. I repeated the same with stock recovery but no success and was not even able to boot to CM13 now.
Hence I was stuck on the OnePlus logo without any booting ROM or recovery and a locked bootloader (according to fastboot)
What I have already tried but failed:-
1. Tried to root with kingroot etc. (Before bricking)
2. Tried to unlock bootloader but failed because it has no recovery.
3. Tried to flash stock OOS 2.1.3-x
4. For now I used fastboot continue to boot back into CM13
Please help, I'm now stuck with cm13 without root and without any recovery installed.
P.S. I'm not even sure that if I clicked reboot then the phone will boot.
Thanks.
Okay, calm down.
Go to developer options and see if "OEM Unlocking" is enabled. If not, enable it.
Cool. Now enable USB Debugging, connect the phone to PC, open CMD and type
Code:
adb reboot bootloader
then
Code:
fastboot oem unlock
Download TWRP from the official website, rename it to recovery.img and then
Code:
fastboot flash recovery recovery.img
Now you have a recovery and an unlocked bootloader. Profit?
I hope this helps.
Thunderbottom said:
Okay, calm down.
Go to developer options and see if "OEM Unlocking" is enabled. If not, enable it.
Cool. Now enable USB Debugging, connect the phone to PC, open CMD and type
then
Download TWRP from the official website, rename it to recovery.img and then
Now you have a recovery and an unlocked bootloader. Profit?
I hope this helps.
Click to expand...
Click to collapse
Thanks for your help,
But if you read my post then you'll understand that due to absence of a recovery I can't unlock the bootloader and hence cannot flash twrp
gavisharora said:
Thanks for your help,
But if you read my post then you'll understand that due to absence of a recovery I can't unlock the bootloader and hence cannot flash twrp
Click to expand...
Click to collapse
You don't need recovery to unlock bootloader, you need fastboot.
Thunderbottom said:
You don't need recovery to unlock bootloader, you need fastboot.
Click to expand...
Click to collapse
But in OnePlus devices the phone asks a confirmation through recovery recovery to wipe data and unlock
gavisharora said:
But in OnePlus devices the phone asks a confirmation through recovery recovery to wipe data and unlock
Click to expand...
Click to collapse
Try the Mega Unbrick Guide then.
Deleted
Same problem. But i dont have pc with windows and can't use mega unbrick guide(
Any news with solution?
Obs: these were the steps that i did to get it, try it by your own risk
----------------------update------------------------
Some people are saying that can't get the 11.1.021 via ota from zui10, but I got the information that this version of qfil 11.1.021 is getting ota to the 11.5, so you should try it just changing the files in the tutorial of step 1 and if don't get the ota, jump to the step 3
-------------------------------------------------------
I did the first part with my bootloader locked, and just got it working this way. I tried to qfil directly the 11.1.021 or use the version updated with the bootloader unlocked but i got error 7 later.
To start, you will need adb and fastboot, and you can get them from here
1- Qfil the zui 10 version from this tutorial
2- Set up a pin (it will be important) and update the zui to version 11.1.021 (right after you install the zui 10 it will pop the update, if not you can use the zui update app)
3- Now that you have 11.1.021 from ota you have to go to fastboot mode (adb reboot bootloader) and unlock your bootloader, if you do this on zui 10 or zui 11.5 you will got on bootloop and have to start all again (tutorial <- you can use this to lock your bootloader for start the proccess too)
4- Go again to bootloader and use fastboot flash recovery twrp.img (download twrp)
5- From fastboot mode, press volume down repeatly until you see "Recovery mode" then press power button, the phone will reboot twice and enter in twrp, you will need to put the pin set on step 2
6- Pass this update zip to your phone from the PC then select it on "install" section and swipe to flash (this was the step where i got error 7 with qfil version of 11.1.021, if you got this, the only solution i know is start all over again owith qfil zui 10)
7- After flash is done, go back to the home page of twrp, select "wipe" and mark "dalvik", "cache" and "data" then reboot system
Your phone will be on bootloop and this is the part that i discover after 2 days trying
8- Turn off your phone and turn it back pressing the power button and the volume down to enter in fastboot mode, you will see on last line that your bootloader will be locked again, and this is the cause of bootloop
9- Use the commands to unlock bootloader again (fastboot flash unlock your_unlock_img.img and fastboot oem unlock-go)
Your phone will boot and reboot in twrp that will do an automatic process, than will reboot again in ZUI 11.5.141 (may take some minutes)
Obs²: After this proccess, if you want to use TWRP to install a rom or something, you will need to flash it again
when I try to install just I got error 7 for everstep :S how can I solve it ?
brujaboy said:
when I try to install just I got error 7 for everstep :S how can I solve it ?
Click to expand...
Click to collapse
Did you try it from qfil the zui 10 with the locked bootloader?
Because i got this error when i ota updated from 10 to 11.1.021 with the bootloader unlocked
Astronomico said:
Did you try it from qfil the zui 10 with the locked bootloader?
Because i got this error when i ota updated from 10 to 11.1.021 with the bootloader unlocked
Click to expand...
Click to collapse
yes I did my friend I installed zui10 with QFIL after that I ınstalled 11.0.21 with twrp and when I try to install 11.5 I got error 7, I did edit with notepad++ but still have this problem
brujaboy said:
yes I did my friend I installed zui10 with QFIL after that I ınstalled 11.0.21 with twrp and when I try to install 11.5 I got error 7, I did edit with notepad++ but still have this problem
Click to expand...
Click to collapse
I think the problem is with the version you're installing in TWRP , after qfil zui10, wait for the OTA for 11.1.021 of the app zui update, it seems to exist some versions of 11.1.021 and the TWRP version is not the same of the OTA
The version of 11.1.021 that i've got by OTA with my bootloader already unlocked on zui10 got error 7 too, just the version i've got with the bootloader locked worked
Astronomico said:
I think the problem is with the version you're installing in TWRP , after qfil zui10, wait for the OTA for 11.1.021 of the app zui update, it seems to exist some versions of 11.1.021 and the TWRP version is not the same of the OTA
The version of 11.1.021 that i've got by OTA with my bootloader already unlocked on zui10 got error 7 too, just the version i've got with the bootloader locked worked
Click to expand...
Click to collapse
we need wait thank u bro
Microsoft Windows [Version 10.0.18362.657]
(c) 2019 Microsoft Corporation. All rights reserved.
C:\Program Files (x86)\Minimal ADB and Fastboot> adb reboot bootloader
error: no devices/emulators found
C:\Program Files (x86)\Minimal ADB and Fastboot>
Click to expand...
Click to collapse
Fixed
this is whilest in fastboot.. ^^
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
View attachment 4951729
it pushes a command when phone was on but when in fastboot / bootloader nothing ? any ideas?
Fixed
every time i push recovery img twrp via ADB it gets bootloader loop
leerh said:
every time i push recovery img twrp via ADB it gets bootloader loop
Click to expand...
Click to collapse
That's weird, i've uploaded the same img i used on mine smartphone, it reboot twice, but starts after in my case, i just got bootloop after unlock the bootloader, but never after flash the twrp...
Try to turn your phone on holding the vol down button to enter in fastboot and check if it's really unlocked, since you flashed the twrp, you will need it
Btw, try to use the files of this tutorial
Astronomico said:
That's weird, i've uploaded the same img i used on mine smartphone, it reboot twice, but starts after in my case, i just got bootloop after unlock the bootloader, but never after flash the twrp...
Try to turn your phone on holding the vol down button to enter in fastboot and check if it's really unlocked, since you flashed the twrp, you will need it
Btw, try to use the files of this tutorial
Click to expand...
Click to collapse
yhyh it says device is unlocked ive used unlock image from lenovo site to unlock it.
im currently on 11.1.021 st cant install twrp affter installing keeps booting to bootloader (unlocked) from here i will need to use qfill to get stock firmware 10.5.304 cn version stock recovery still works
ive also tried on ZUI_10.5.304 same thing
qill emergency flash dose not lock bootloader for me? well i cant twrps anymore makes me feel its step away from total brick
do i need to lock it then qfill then 11.1.021st via OTA then unlock it
I've Just googled It and i found that flash magisk could repair the twrp bootloop, because magisk changes the boot.img that is the cause of the problem
You can download It on magiskmanager site, put it on your phone, than use twrp install session to flash it
And Qfil doesn't Lock your bootloader
Astronomico said:
I've Just googled It and i found that flash magisk could repair the twrp bootloop, because magisk changes the boot.img that is the cause of the problem
You can download It on magiskmanager site, put it on your phone, than use twrp install session to flash it
And Qfil doesn't Lock your bootloader
Click to expand...
Click to collapse
thanks for looking into it for me and i will try this out now and let you know the results done.
this a fresh from factory flash so there is no magisk modules. can you post the links to the information you found.. i cant flash any files affter installing twrps which is successful the via ADB but affter the reboot or trying twrps or access phone or recovery will bootloop my phone to go into fast boot every single time...
can i install twrps on 10.304 and 11.021 both are offical cn roms? device has to be unlocked right which it is? is there any place i can get stock recovry image?
i wanna try= fastboot flash boot_a stockboot.img=fastboot flash boot_b stockboot.img
but i dont think i should as qfil provides stock factory flash? means its fully fresh?
leerh said:
thanks for looking into it for me and i will try this out now and let you know the results done.
this a fresh from factory flash so there is no magisk modules. can you post the links to the information you found.. i cant flash any files affter installing twrps which is successful the via ADB but affter the reboot or trying twrps or access phone or recovery will bootloop my phone to go into fast boot every single time...
can i install twrps on 10.304 and 11.021 both are offical cn roms? device has to be unlocked right which it is? is there any place i can get stock recovry image?
i wanna try= fastboot flash boot_a stockboot.img=fastboot flash boot_b stockboot.img
but i dont think i should as qfil provides stock factory flash? means its fully fresh?
Click to expand...
Click to collapse
Oh, i thought you could access the twrp after install it, sorry
The tutorial on step 1 provides the official cn rom zui10, if you use it, your phone will probably boot normally.
I think you should lock your bootloader and use the official, you will have the updates via OTA, since you can't use TWRP, I think it will be the best for you, I don't know how help you more :/
I have a request anyone can share with my twrp back up clear update without data like zip file because I have problem with my QFIL and when I try to install zui 10.5 give me sahara error and I thought about this option
brujaboy said:
I have a request anyone can share with my twrp back up clear update without data like zip file because I have problem with my QFIL and when I try to install zui 10.5 give me sahara error and I thought about this option
Click to expand...
Click to collapse
Sorry, i didn't see it, but saraha error is probably caused because wrong version of USB drivers in your PC, or you're being too slow to press "download content" on qfil after plug the phone (I don't know exactly why, but you have to click it fairly fast)
Astronomico said:
Sorry, i didn't see it, but saraha error is probably caused because wrong version of USB drivers in your PC, or you're being too slow to press "download content" on qfil after plug the phone (I don't know exactly why, but you have to click it fairly fast)
Click to expand...
Click to collapse
doesn't matter, thank u so much for replying yesterday I installed all of driver versions but I saw still again and I find another method like pushing very fast download click button and I did successfully 11.1.021 thank u so much again for supporting
Astronomico said:
Obs: these were the steps that i did to get it, try it by your own risk
I did the first part with my bootloader locked, and just got it working this way. I tried to qfil directly the 11.1.021 or use the version updated with the bootloader unlocked but i got error 7 later.
To start, you will need adb and fastboot, and you can get them from here
1- Qfil the zui 10 version from this tutorial
2- Set up a pin (it will be important) and update the zui to version 11.1.021 (right after you install the zui 10 it will pop the update, if not you can use the zui update app)
3- Now that you have 11.1.021 from ota you have to go to fastboot mode (adb reboot bootloader) and unlock your bootloader, if you do this on zui 10 or zui 11.5 you will got on bootloop and have to start all again (tutorial <- you can use this to lock your bootloader for start the proccess too)
4- Go again to bootloader and use fastboot flash recovery twrp.img (download twrp)
5- From fastboot mode, press volume down repeatly until you see "Recovery mode" then press power button, the phone will reboot twice and enter in twrp, you will need to put the pin set on step 2
6- Pass this update zip to your phone from the PC then select it on "install" section and swipe to flash (this was the step where i got error 7 with qfil version of 11.1.021, if you got this, the only solution i know is start all over again owith qfil zui 10)
7- After flash is done, go back to the home page of twrp, select "wipe" and mark "dalvik", "cache" and "data" then reboot system
Your phone will be on bootloop and this is the part that i discover after 2 days trying
8- Turn off your phone and turn it back pressing the power button and the volume down to enter in fastboot mode, you will see on last line that your bootloader will be locked again, and this is the cause of bootloop
9- Use the commands to unlock bootloader again (fastboot flash unlock your_unlock_img.img and fastboot oem-unlock go)
Your phone will boot and reboot in twrp that will do an automatic process, than will reboot again in ZUI 11.5.141 (may take some minutes)
Obs²: After this proccess, if you want to use TWRP to install a rom or something, you will need to flash it again
Click to expand...
Click to collapse
Hi bro. I see a little error in your command: The second command in the 9th step is wrong, the correct command is: "fastboot oem unlock-go".
Greetings.
leerh said:
yhyh it says device is unlocked ive used unlock image from lenovo site to unlock it.
im currently on 11.1.021 st cant install twrp affter installing keeps booting to bootloader (unlocked) from here i will need to use qfill to get stock firmware 10.5.304 cn version stock recovery still works
ive also tried on ZUI_10.5.304 same thing
qill emergency flash dose not lock bootloader for me? well i cant twrps anymore makes me feel its step away from total brick
do i need to lock it then qfill then 11.1.021st via OTA then unlock it
Click to expand...
Click to collapse
i got step 1,2,3,4,5 and 6, got an error #7.
so i used the tutorial to flash the device in step 1
it was unable to update cuz bootloader was unlock
i locked bootloader and update to 11.1.021
so afther that, i unlocked again to install twrp.
intalled twrp and transfer file to phone
booted twrp and installed the zip, got the error 7 again.
lipeneiva said:
i got step 1,2,3,4,5 and 6, got an error #7.
so i used the tutorial to flash the device in step 1
it was unable to update cuz bootloader was unlock
i locked bootloader and update to 11.1.021
so afther that, i unlocked again to install twrp.
intalled twrp and transfer file to phone
booted twrp and installed the zip, got the error 7 again.
Click to expand...
Click to collapse
best thing is to try again an follow every letter and step this only way to install 11.5 (beta) did u set a pin it is needed ive not seen another guide to install android 10
Lombachita said:
Hi bro. I see a little error in your command: The second command in the 9th step is wrong, the correct command is: "fastboot oem unlock-go".
Greetings.
Click to expand...
Click to collapse
Ops, fixed
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.