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.
Related
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?
Hi all,
Currently running Oreo (via OldDroid manual update) then LOS 15.1 (Berkley unofficial) on top, which is great but would like NFC, buttons, flashlight.
What is the best method to reinstate this functionality? I have tried the rollback for OldDroid rollback to no avail. I believe this method assumes you are rooted, which i am not.
Happy to be on EMUI 5 if necessary as i believe i can now update to Oreo OTA.
Cheers
Can i provide further pertinent information or ask elsewhere to get replies?
What did you do in the fist place to go from stock oreo to LOS 15.0 ; any links ?
Thank you.
I flashed the system image using "fastboot flash system system.img" via article https://www.xda-developers.com/lineageos-honor-view-10-huawei-mate-10-pro-project-treble/
Cheers
I think, once unrooted, you'll have to flash back stock system.
oslo83 said:
I think, once unrooted, you'll have to flash back stock system.
Click to expand...
Click to collapse
Great, thank you. I am not rooted so I extracted the system.img from STF-L09SC432B360a (from http://pro-teammt.ru/firmware-database/?firmware_model=STF-L09&firmware_page=0) using this guide https://forum.xda-developers.com/mate-10/how-to/guide-extracting-stock-firmware-files-t3756733
Then using that stock emui 8 system image:
"fastboot flash system system.img"
I receive the following error:
error: cannot load 'SYSTEM.img'
Any ideas?
Cheers
Another attempt at system.img extract using my windows box and the windows software referred to in https://forum.xda-developers.com/mat...files-t3756733.
This time i was able to flash the system.img successfully. When the device booted, it boot looped 3/4 times then i received :
Huawei eRecovery :
"Serious problems occurred when the phone boot, you are recommended to do factory data reset
NOTE: user data will be wiped after recovery".
I performed this reset and device booted to TWRP some commands took place but too quick (saw selinux buts thats it). Device rebooted twice then loaded Huawei eRecovery where the only option is :
Download latest version and recovery
Restore system with wifi
Entered wifi details
Getting package info from server
Getting package info failed.
Booting into TWRP the 'Factory Reset' option performs the same process that i saw when Huawei eRecovery recommended the factory data reset. Some i'm confident in what happened at that point now. Unsure as to what to try at this point. The phone does not boot into EMUI and will only boot to Huawei eRecovery.
The bootloader is unlocked, as per the process to install LineageOS 15.1 in the link in the OP. I've not checked if its still unlocked, but guess that could be causing a problem?
Just checked and bootloader is unlocked.
Interestingly the process to re lock it from the Huawei site (https://emui.huawei.com/en/unlock_step) shows that you have to use the same command to lock the bootloader as to lock it again:
Note: to re-lock the bootloader after unlocking it, restore the device’s software to the Huawei official version using a microSD card then switch the device to fastboot mode and enter “fastboot oem unlock ****************” in the computer’s command prompt, where * refers to the 16-digit unlock password. The device will then restart, and the bootloader lock status will change to “Bootloader Lock State: RELOCKED”.
If i follow those instructions i get the below error:
Code:
fastboot oem unlock **************** <-my 16 digit code
...
FAILED (remote: already fastboot unlocked)
Stop trying to lock your bootloader, it won't help you. Interresing info though.
Did it occur to you that after flashing back successfully system.img it could have been good to flash back stock recovery over twrp ?
This way you would have bootloop 3 or 4 times, and then stock recovery would have launch, not twrp.
I think a format system from this stock recovery, not twrp, would have solve your problem.
Thanks. So I can leave the boot loader unlocked at this point and run stock emui? I'll flash stock recovery. Perhaps that will suggest factory reset and then I'll be able to boot.
Thanks again.
oslo83 said:
Stop trying to lock your bootloader, it won't help you. Interresing info though.
Did it occur to you that after flashing back successfully system.img it could have been good to flash back stock recovery over twrp ?
This way you would have bootloop 3 or 4 times, and then stock recovery would have launch, not twrp.
I think a format system from this stock recovery, not twrp, would have solve your problem.
Click to expand...
Click to collapse
In order to revert to the stock recovery is it necessary to flash all three recovery images from the update.app file? :
recovery_ramdisk
recovery_vendor
recovery_vbmeta
Looking at flashing the recovery_ramdisk image with the stock version i have extracted using the below:
Code:
fastboot flash recovery_ramdisk RECOVERY_RAMDISK.img
Noticed the stock recovery_ramdisk i extracted has a filename of 'RECOVERY_RAMDIS.img', not ending in 'K' for 'RAMDISK. Presumably i can simply rename my recovery_ramdisk to "RECOVERY_RAMDISK.img" unless a 15 character filename is a limitation, or adjust my fastboot command to :
Code:
fastboot flash recovery_ramdisk RECOVERY_[B]RAMDIS[/B].img
Code:
fastboot flash recovery_ramdisk RECOVERY_RAMDIS.img
Did the trick to boot back into EMUI 8. However, i still have an intermittent torch/flashlight and the navigation keys/buttons do not work.
Any ideas on where i go from here?
mightyjcb said:
Code:
fastboot flash recovery_ramdisk RECOVERY_RAMDIS.img
Did the trick to boot back into EMUI 8. However, i still have an intermittent torch/flashlight and the navigation keys/buttons do not work.
Any ideas on where i go from here?
Click to expand...
Click to collapse
Follow instrucTions of this post: https://forum.xda-developers.com/showpost.php?p=75772700&postcount=2
and you will have all working again in B360 ;
This time while on bootloader:
fastboot flash kernel KERNEL_B360a_TOUCH_FIX.img
oslo83 said:
Follow instrucTions of this post: https://forum.xda-developers.com/showpost.php?p=75772700&postcount=2
and you will have all working again in B360 ;
This time while on bootloader:
fastboot flash kernel KERNEL_B360a_TOUCH_FIX.img
Click to expand...
Click to collapse
Many thanks @oslo83 followed that and just as you said hardware functioning correctly once again!
One further question for future reference, am i now in a position to apply OTA updates when released?
Cheers
You'll need to be unrooted and with stock recovery for applying ota when it will be available.
I don't know if you'll need stock kernel for ota...
mightyjcb said:
This time i was able to flash the system.img successfully. When the device booted, it boot looped 3/4 times then i received :
Huawei eRecovery :
"Serious problems occurred when the phone boot, you are recommended to do factory data reset
NOTE: user data will be wiped after recovery".
Click to expand...
Click to collapse
You need to flash stock recovery and do a factory reset in stock recovery.
oslo83 said:
You'll need to be unrooted and with stock recovery for applying ota when it will be available.
I don't know if you'll need stock kernel for ota...
Click to expand...
Click to collapse
Great, i should be able to meet this criteria quite easily then :
+ I've never rooted the device
+ I have reverted to stock recovery
+ I flashed the stock kernel over the top of the button fix kernel mentioned earlier in this thread.
Thanks again for your help, much appreciated.
zxz0O0 said:
You need to flash stock recovery and do a factory reset in stock recovery.
Click to expand...
Click to collapse
That seemed to do the trick! Ta.
I unlocked the bootloader succesfully then i tried to root the phone so i downloaded a relame 7 rom and patched boot.img with magisk then i did a fastboot then i typed in my pc cmd (fastboot flash magisk_patched.img) then (fastboot reboot) then i stucked at bootloop and i can't go to fastboot or recovery , Even the pc don't detect my phone, I think its because i downloaded a rom of newer version that i didn't update to it before flashing the patched boot or maybe i typed wrong cmd , Please any help guys there isn't any realme support center in my country, Thanks in advance.
you should have flashed vbmeta.img so that you don't get in bootloop
You mean your phone wouldn't go into bootloader by "Vol. down button + power button" holding from power off state?
T59y9 said:
fastboot flash magisk_patched.img
Click to expand...
Click to collapse
Do you mean "fastboot flash recovery magisk_patched.img"??
the correct command is fastboot flash boot magisk_patched.img
Maybe he wrote fastboot flash magisk_patched .img
but I think it would have returned an error
T59y9 said:
I unlocked the bootloader succesfully then i tried to root the phone so i downloaded a relame 7 rom and patched boot.img with magisk then i did a fastboot then i typed in my pc cmd (fastboot flash magisk_patched.img) then (fastboot reboot) then i stucked at bootloop and i can't go to fastboot or recovery , Even the pc don't detect my phone, I think its because i downloaded a rom of newer version that i didn't update to it before flashing the patched boot or maybe i typed wrong cmd , Please any help guys there isn't any realme support center in my country, Thanks in advance.
Click to expand...
Click to collapse
Maybe the rom you downloaded and the base rom running on your device is not the same version, that may cause the error. {Mod edit}
@T59y9
Hi
did you solve in some way?
My realme 7 5G is not rooted.
Just arrived me friday, I udated to new firmware trought recovery. After the reboot did not woke up anymore.
Black screen. no realme logo. nothing.
tried all button combinations, nothing. no boot, no logo, recovery, no fastboot.
tried also with charger attached, with usb on PC.
Nothing...
Any idea to solve my problem?
thank you.
how did you unlock the bootloader?
in depth test app says my model does not support in-depth test
if you are asking me, I did not unlock anything.
just flashing new OS update trought recovery. after that device dead. not buttons combinations to get fastboot or anything else...
gannjunior said:
if you are asking me, I did not unlock anything.
just flashing new OS update trought recovery. after that device dead. not buttons combinations to get fastboot or anything else...
Click to expand...
Click to collapse
oh sorry
any idea how to solve?
T59y9 said:
I unlocked the bootloader succesfully then i tried to root the phone so i downloaded a relame 7 rom and patched boot.img with magisk then i did a fastboot then i typed in my pc cmd (fastboot flash magisk_patched.img) then (fastboot reboot) then i stucked at bootloop and i can't go to fastboot or recovery , Even the pc don't detect my phone, I think its because i downloaded a rom of newer version that i didn't update to it before flashing the patched boot or maybe i typed wrong cmd , Please any help guys there isn't any realme support center in my country, Thanks in advance.
Click to expand...
Click to collapse
same anyone know how to solve this pls :/
First you all. Say the Model Number. You talk about Realme 7/Pro or 5G...
This issues is fixable. Just need extra tools to bypass Google FRP and a factory images ROM versions. Fixed few devices with the same situation!
T59y9 said:
I unlocked the bootloader succesfully then i tried to root the phone so i downloaded a relame 7 rom and patched boot.img with magisk then i did a fastboot then i typed in my pc cmd (fastboot flash magisk_patched.img) then (fastboot reboot) then i stucked at bootloop and i can't go to fastboot or recovery , Even the pc don't detect my phone, I think its because i downloaded a rom of newer version that i didn't update to it before flashing the patched boot or maybe i typed wrong cmd , Please any help guys there isn't any realme support center in my country, Thanks in advance.
Click to expand...
Click to collapse
T59y9 said:
I unlocked the bootloader succesfully then i tried to root the phone so i downloaded a relame 7 rom and patched boot.img with magisk then i did a fastboot then i typed in my pc cmd (fastboot flash magisk_patched.img) then (fastboot reboot) then i stucked at bootloop and i can't go to fastboot or recovery , Even the pc don't detect my phone, I think its because i downloaded a rom of newer version that i didn't update to it before flashing the patched boot or maybe i typed wrong cmd , Please any help guys there isn't any realme support center in my country, Thanks in advance.
Click to expand...
Click to collapse
did you find soultion of this at now because i also have same problem?
I've done the same thing I accidently typed "fastboot flash recovery magisk_patched.img" and now I cannot get out of the boot loop as there is no way due to messed up recovery + boot. I have been reading about finding and downloading a firmware in zip format that can be flashed with "SP Flash Tool" but when I try I cannot get it to work. The Firmware should be for the Realme 7 5G [RMX2111].
If anyone else can figure it out.... Please help!
martinbrettphilo said:
I've done the same thing I accidently typed "fastboot flash recovery magisk_patched.img" and now I cannot get out of the boot loop as there is no way due to messed up recovery + boot. I have been reading about finding and downloading a firmware in zip format that can be flashed with "SP Flash Tool" but when I try I cannot get it to work. The Firmware should be for the Realme 7 5G [RMX2111].
If anyone else can figure it out.... Please help!
Click to expand...
Click to collapse
It'll be kinda hard. You're gonna have to find a stock ROM - not an OTA update - and you're gonna need to use python to extract the contents from the .OFP file. This should be it. https://firmwarefile.com/oppo-realme-7-5g-rmx2111
basically you can follow this tutorial
the only difference is you have to use realme 7 firmware not C3. this is ofp file for rmx2151 you can extract it with ofp extractor. also I link this guide for RMX2155. its bootloader unlock guide for RMX2155, but you also follow that guide to revive RMX2151 (until step 10 is sufficient, unless you want unlocked bootloader too)
SF Flash tool is a quite useful for flashing/unbrick Mediatek phones. just read instruction more carefully from now
immns said:
basically you can follow this tutorial
the only difference is you have to use realme 7 firmware not C3. this is ofp file for rmx2151 you can extract it with ofp extractor. also I link this guide for RMX2155. its bootloader unlock guide for RMX2155, but you also follow that guide to revive RMX2151 (until step 10 is sufficient, unless you want unlocked bootloader too)
SF Flash tool is a quite useful for flashing/unbrick Mediatek phones. just read instruction more carefully from now
Click to expand...
Click to collapse
good. this for Realme 7 :
- Textguide : https://telegra.ph/Hard-Brick-Fix-for-Realme-7-01-25
hello guys, i'm having a problem here, I just installed a pixel plus ui and then installed the magisk app, then I renamed it to a zip file as mentioned in the website and went to flash it on my phone (Realme 7) after flashing successfully completed I pressed the reboot to system option, now it's stuck on the realme logo and doesn't budge anymore... I'm really worried please help me.
Attached is the stock boot image pulled via payload dumper for the OnePlus Nord N200 5G. It is from the full OTA zip - Official Build 11.0.2.0.DE17AA dated September 2nd 2021.
It seems quite a few folks are trying to get ahold of this. *Download link at the bottom*
I AM NOT A DEVELOPER!! I am just posting this for those who need the image file.
The guide to install this is pretty simple. If you have previously rooted the device then you most likely have installed the partially functional version of TWRP for the device. If you have, then you can use the same method for installing TWRP to install the factory boot image. Keep in mind that if you have installed Magisk to the device then you may encounter problems. The following pre-requisites should be followed prior to flashing.
1.) Do a complete uninstall of Magisk if you wish to no longer retain root. There are no guarantees this will work if you keep Magisk on the device. Since Magisk changes the system binaries, stock recovery may not work properly.
2.) Make sure the bootloader remains UNLOCKED! Attempting to lock the bootloader WILL cause an error message that the "Device is corrupt and will NOT BOOT"
3.) Make sure you have enabled USB debugging and your PC can recognize the device. You can do this by booting up the device normally and use the command prompt
adb devices
If the device is recognized it will return with your device ID and "device". If you see anything other than the ID and device (such as unauthorized) then please check to make sure you have enabled USB debugging, the device is plugged to the PC and the path to your platform tools of ADB and Fastboot tools is proper in your command prompt sequence
HOW TO INSTALL:
1.) With the device on and plugged in, open a command prompt in the path that your ADB and Fastboot platform tools are located and type:
adb devices
If properly read, ADB should return with the device ID and "device" as stated above.
2.) Now execute the ADB command:
adb reboot bootloader
Wait a few seconds. The device should now boot into Fastboot Mode.
3.) Now execute the fastboot command:
fastboot devices
The device should now read like earlier with the device ID and "fastboot". If true, fastboot commands will be accepted. Also please double check the device state on the phone screen. Make sure the device is UNLOCKED. If so, stop reading this step and go to step 4. If it is not unlocked DO NOT proceed and reboot the device using the volume keys when the word "START" is in green letters at the top and pressing the power key. DO NOT proceed any further. If your device is functioning in a locked state then stop reading this guide and go back to playing minecraft or flappy bird or whatever it is you do with your phone.
4.) VERY IMPORTANT!! Execute the following fastboot command:
fastboot getvar current-slot
The device will give a letter, either a or b. PLEASE remember the letter as the next step will require that letter after the underscore in the next fastboot command. If slot a, type a; if slot b, type b after typing the underscore.
5.) Make sure this boot image file is located in the same folder as your adb and fastboot for your platform tools and execute the fastboot command:
fastboot flash boot_a boot.img (this is for those who are on slot a from step 4) OR
fastboot flash boot_b boot.img (this is for those who are on slot b from step 4)
6.) You are welcome to flash to both slots if you like as no harm will come from doing this, but only the current slot is necessary for it to work. You can also flash it as many times as you like but that's just dirty flashing over TWRP over and over. Finally wipe the cache and reboot by typing the following fastboot commands:
fastboot -w (this wipes the cache - not necessary but helpful)
fastboot reboot
7.) Enjoy stock recovery. You can also use the volume keys to navigate to "Start" and reboot the device or even try "Recovery Mode" to ensure it worked. I would highly suggest that you boot into recovery and factory reset the device, wiping everything.
*This has been tested and works on the UNLOCKED US variant (Basically, if you can update via the OnePlus website and the build number is DE17AA you're good to go.) DO NOT ATTEMPT THIS ON ANY OTHER CARRIER LOCKED MODEL!!
**While the device is back to stock recovery, the chances are very high that any future OTA's (Full or partial) may not load or install if binaries were altered by Magisk. The best thing to do here is to wait for a full package and install via Oxygen Updater or attempt a partial via Oxygen Updater.
LINK TO IMAGE FILE:
https://www.androidfilehost.com/?w=files&flid=330195
I know I'm replying to an old thread, sorry. I'm wondering if any has the stock T-Mob boot image for Android 12, I flashed a boot.img for the unlocked one and now my phone is boot looping. Has anyone pulled the stock Android 12 boot image for T-Mob yet? Or have a link for the full T-mob Android 12 OTA?
Replying to my own reply here, but I found a link to the T-Mobile Android 12 OTA here: https://community.oneplus.com/thread?id=1599362
Using this, I flashed the correct boot image which fixed the bootloop and now I've rooted it with Magisk.
Can you use this method to flash to de2117_11_c.15?
Hi this was a good guide. Is there a stock boot image for N200 Unlocked Android 12?
rick909 said:
Hi this was a good guide. Is there a stock boot image for N200 Unlocked Android 12?
Click to expand...
Click to collapse
You need to look at the dates of the messages you are replying to as this is a very old thread.
I maintain a thread with the latest boot image to root with guide here:
Root latest US OEM (DE2117)C_23/T-Mobile-Metro(DE2118) C_21 OTA for dummies
I have posted all the boot.img files for N200 A12 to AFH for DE2117 US OEM firmware and now latest for DE2118 (Tmobile/metro) I have posted both the original file as well as pre-patched with Magisk v25.2 for each. The T-Mobile/Metro image...
forum.xda-developers.com
Device does not boot, i can bring it into bootloader but the recovery is also failing. I have no clue what to do next
Vipin_31 said:
Device does not boot, i can bring it into bootloader but the recovery is also failing. I have no clue what to do next
Click to expand...
Click to collapse
Try TWRP maybe.
I had the same problem in the past. There are some things you can try:
First of all, check this Telegram channel, as it has everything it needs for your device.
Second, download OrangeFox recovery from here.
Also, you may need Vbmeta.img for Android 11+, that you can download from here (Be sure to be logged into Telegram Web) or download the Vbmeta attached, it's the same.
- Boot your device into bootloader
- Connect your phone to PC and run ADB
Type:
- Fastboot flash recovery recovery.img (Rename OF recovery to recovery for your ease).
- Fastboot flash vbmeta vbmeta.img
- Reboot to recovery
If this fails, your super partition may got corrupted. To fix this, you may need to reflash the super partition
- Download Flashtool from here,
- Reboot into Bootloader
- Open & Update the app (Click Check for updates).
- While in bootloader and connected to PC, click unbrick and wait for the process to end.
- Try flashing OF recovery and Vbmeta again.
Only use this method as a last resort as it may cause your fingerprint to stop working.​
deserted said:
Try TWRP maybe.
Click to expand...
Click to collapse
i tried it but it shows the same problem as orangefox it shows it logo and turns off