Related
So after an official way to do so Just unlocked my Nokia 8 bootloader.
I don't want to flash recovery as need system updates, so I tried booting to latest official twrp from fastboot "fastboot boot recovery.img" but it only take me to android logo and nothing happens. Any help regarding how to boot in twrp?
Also, is it okay to flash magisk with temporary twrp?
me too , just stuck there =(
you need to fastboot boot to even be able to install it anyway, but it seems to not be working for us that used the official unlock, either that or september update might be the problem
It works tho, I unlocked through official method and downgraded by switching slot a to slot b (search it up) then reboot ur phone you will see it's downgraded to the August update. Then boot the latest TWRP and follow the steps. It works, I assure you. Somehow TWRP is not compatible with the September patch.
iKillua said:
It works tho, I unlocked through official method and downgraded by switching slot a to slot b (search it up) then reboot ur phone you will see it's downgraded to the August update. Then boot the latest TWRP and follow the steps. It works, I assure you. Somehow TWRP is not compatible with the September patch.
Click to expand...
Click to collapse
How to check the current active slot?
fastboot - - set-active a
Will only this command do everything? Or do I need some firmware?
iKillua said:
It works tho, I unlocked through official method and downgraded by switching slot a to slot b (search it up) then reboot ur phone you will see it's downgraded to the August update. Then boot the latest TWRP and follow the steps. It works, I assure you. Somehow TWRP is not compatible with the September patch.
Click to expand...
Click to collapse
Hmmm i'm still on august , did not receive the september yet ( , but still can't boot , so i'm going to down to june by change the slot to a ( mine is b ) , thanks for the info , will try your way )
Sahilsinghlodhi said:
How to check the current active slot?
fastboot - - set-active a
Will only this command do everything? Or do I need some firmware?
Click to expand...
Click to collapse
you can check the current active slot by doing
fastboot getvar current-slot
emoklaga113 said:
Hmmm i'm still on august , did not receive the september yet ( , but still can't boot , so i'm going to down to june by change the slot to a ( mine is b ) , thanks for the info , will try your way )
Click to expand...
Click to collapse
After getting back to August patch it didn't boot for me directly but it did after entering fastboot mode from custom recovery.
1. Boot into Nokia recovery
2. Select reboot to fastboot
3. Use fastboot boot twrp.img
iKillua said:
you can check the current active slot by doing
fastboot getvar current-slot
Click to expand...
Click to collapse
Rooted with magisk ?
Though unable to update to September.(not able to Install), on stock Recovery.
Sahilsinghlodhi said:
So after an official way to do so Just unlocked my Nokia 8 bootloader.
I don't want to flash recovery as need system updates, so I tried booting to latest official twrp from fastboot "fastboot boot recovery.img" but it only take me to android logo and nothing happens. Any help regarding how to boot in twrp?
Also, is it okay to flash magisk with temporary twrp?
Click to expand...
Click to collapse
Just flash the official twrp on both slot, official or unofficial bl unlock works, then after flashing the twrp on both slot run cmd "fastboot reboot recovery" then it's done. You can now flash magisk.
---------- Post added at 04:03 PM ---------- Previous post was at 03:24 PM ----------
Lee Castro said:
Just flash the official twrp on both slot, official or unofficial bl unlock works, then after flashing the twrp on both slot run cmd "fastboot reboot recovery" then it's done. You can now flash magisk.
Click to expand...
Click to collapse
After unlocking the bootloader (official or unofficial bl unlock), run the cmd for flashing the official twrp "fastboot flash boot_a twrp-3.2.3-1-NB1.img" & "fastboot flash boot_b twrp-3.2.3-1-NB1.img" then after flashing run the cmd "fastboot reboot recovery", then flash magisk for rooting.
Sahilsinghlodhi said:
Rooted with magisk ?
Though unable to update to September.(not able to Install), on stock Recovery.
Click to expand...
Click to collapse
you need to update to september security patch then unlock your bootloader officially, flash the official twrp on both slots run cmd "fastboot reboot recovery" then install magisk.
Sent from my TA-1004 using XDA-Developers Legacy app
Similar to the previous threads for OnePlus 5, OnePlus 5T or OnePlus 6, here are the necessary packages to unbrick/revive a hard bricked OnePlus 7 Pro.
The following hardware revisions are supported:
GM1910: China
GM1911: India
GM1913: Europe
GM1917: Global/US Unlocked
Download: https://www.androidfilehost.com/?w=files&flid=294744
guacamole_21_H.04_190416_unlocked.zip
After using it, the phone will be restored to HydrogenOS aka Chinese firmware.
Click to expand...
Click to collapse
guacamole_21_E.08_190515_unlocked.rar
After using it, the phone will be restored to OxygenOS 9.5.4.GM21BA aka European firmware.
Click to expand...
Click to collapse
guacamole_21_O.07_190512_unlocked.zip
After using it, the phone will be restored to OxygenOS 9.5.3.GM21AA aka global firmware.
Click to expand...
Click to collapse
In every case, it is possible to upgrade to latest OxygenOS by using full signed zip from this thread via Local Upgrade.
With the device powered off, hold Volume Up & Volume Down buttons to force it to boot to Qualcomm download mode.
Use the most updated signed driver (2.1.2.2 at this moment) to avoid potential issues..
For detailed procedures, please consult the linked threads above. There is no reason to repeat the same thing again.
Make sure the path of the extracted files doesn't contain any non-English character. The tool isn't unicode aware.
Source:
HydrogenOS package: 人艱不拆 (OnePlus China forum thread), @trollavin & @Some_Random_Username for the help in mirroring
OxygenOS (EU) package: @MrVoshel
OxygenOS (global) package: @Lucifer6
Reserved for future.
Thank you for this!!
Doesn't this leave you with a Chinese modem (limited LTE bands and roaming configs?) and critical partitions? Wouldn't an international or European tool be more suitable considering that Oxygen zips may not overwrite everything? Or is this just a temporary guide with what we have?
LLStarks said:
Doesn't this leave you with a Chinese modem (limited LTE bands and roaming configs?) and critical partitions? Wouldn't an international or European tool be more suitable considering that Oxygen zips may not overwrite everything? Or is this just a temporary guide with what we have?
Click to expand...
Click to collapse
Temp? yes and no, I would say. Better than warranty R&D in days no phone for use.
As far as you can revive the phone from QDL9008 back to HOS/OOS, you now have a chance Again to switch over whatever ROM or OS you want later on.
jkyoho said:
Temp? yes and no, I would say. Better than warranty R&D in days no phone for use.
As far as you can revive the phone from QDL9008 back to HOS/OOS, you now have a chance Again to switch over whatever ROM or OS you want later on.
Click to expand...
Click to collapse
Well, that's the perfect explanation.
:highfive:
Can you turn TMobile to int'l with this ?
HtcOnekid said:
Can you turn TMobile to int'l with this ?
Click to expand...
Click to collapse
What he said
When i start MsmdownloadtoolV4.0.exe it says :
Packet image not exist!
Take out the Chinese characters in the file name and then try
joemossjr said:
Take out the Chinese characters in the file name and then try
Click to expand...
Click to collapse
Yep that's i though, but i finaly looking for EU version. Because i think with OTA upgrade to GMBA EU modem will not contain the good modem right ?
---------- Post added at 12:59 AM ---------- Previous post was at 12:27 AM ----------
failed to install on EU model : param preprocessing and stop at 5 ou 7 sec before flashing. I tryed using anothere patched tool and not working :s
Please help me, I failed pretty hard and bricked my phone.
I rooted my phone with stock recovery using a patched magisk boot image and all went fine.
Today, I deviced to temporarily boot into twrp to check it out, so I booted into fastboot and used "fastboot boot twrp.img"
and booted into system. I was confused and rebooted but now I was stuck in stock recovery. So I completely flashed TWRP
on boot_a and boot_b and into TWRP I rooted my device. But even now I am always bootlooping into TWRP and can't
get my phone to boot into system.
I tried using the unbrick tool but my device won't show up on my computer, even with the driver installed.
I'm screwed, can someone help?
Can I somehow reflash the stock recovery and revert back to my patched boot image?
uniQ191 said:
Please help me, I failed pretty hard and bricked my phone.
I rooted my phone with stock recovery using a patched magisk boot image and all went fine.
Today, I deviced to temporarily boot into twrp to check it out, so I booted into fastboot and used "fastboot boot twrp.img"
and booted into system. I was confused and rebooted but now I was stuck in stock recovery. So I completely flashed TWRP
on boot_a and boot_b and into TWRP I rooted my device. But even now I am always bootlooping into TWRP and can't
get my phone to boot into system.
I tried using the unbrick tool but my device won't show up on my computer, even with the driver installed.
I'm screwed, can someone help?
Can I somehow reflash the stock recovery and revert back to my patched boot image?
Click to expand...
Click to collapse
what is your device OOS 9.5.3/4/5/6 ?
flash the co-responding stock boot.img from twrp with magisk zip together, and see if you can boot
uniQ191 said:
Please help me, I failed pretty hard and bricked my phone.
I rooted my phone with stock recovery using a patched magisk boot image and all went fine.
Today, I deviced to temporarily boot into twrp to check it out, so I booted into fastboot and used "fastboot boot twrp.img"
and booted into system. I was confused and rebooted but now I was stuck in stock recovery. So I completely flashed TWRP
on boot_a and boot_b and into TWRP I rooted my device. But even now I am always bootlooping into TWRP and can't
get my phone to boot into system.
I tried using the unbrick tool but my device won't show up on my computer, even with the driver installed.
I'm screwed, can someone help?
Can I somehow reflash the stock recovery and revert back to my patched boot image?
Click to expand...
Click to collapse
You havn't bricked your phone, just put it in fastboot mode and reupload boot image to the correct slot !
Regards,
thebigtross said:
You havn't bricked your phone, just put it in fastboot mode and reupload boot image to the correct slot !
Regards,
Click to expand...
Click to collapse
Thanks for your replies! I was on OOS 9.5.5 and I tried flashing the twrp/magisk zips but that didn't work either. I also tried applying the stock boot.img to the active slot, but still got the recovery bootloop.
So as my last hope, I wiped all data in recovery mode, rebooted to fastboot and sideloaded the complete stock image from here https://forum.xda-developers.com/oneplus-7-pro/how-to/rom-stock-fastboot-roms-oneplus-7-pro-t3931424
I reconfigured my phone from scratch, rooted with the patched boot image like before and everythings works now. Guess I will not bother with TWRP any time soon.
Added global and EU packages.
Titokhan said:
Added global and EU packages.
Click to expand...
Click to collapse
Will global work for 1911 (India)
Mr.Crucial said:
Will global work for 1911 (India)
Click to expand...
Click to collapse
Yes, the packages are interchangable.
[/COLOR]
Titokhan said:
Yes, the packages are interchangable.
Click to expand...
Click to collapse
But I think that these packages will not work on T-mobile 1915!
When I reboot into edl mode, it recognizes the "Qualcomm HS-USB QDLoader 9008", but then 10 seconds later, the phone automatically boots the the battery display, which disables edl. The same this happens whether I use the vol up+down and plug in, or `adb reboot edl`.
Edit: "How I learned to stop worrying and risk a brick"
Selecting the right COM and hitting start in MSMtool in that 10 second window kept it in edl mode for the duration of the flash.
Hi Guys
UPDATE 2: (2/11/2019) Boot img now patched to Magisk V20.1 and added Google Drive as a mirror
UPDATE: It has come to my attention that some users are having issues with this version, please note this is still in beta and root isn't fully supported yet, also please make sure your running the latest magisk manager (version 7.3.5 at the time of this update) BEFORE flashing the patched boot IMG, those currently having issues, try flashing the stock IMG provided and installing the latest magisk manager then flashing the patched IMG
here is a working magisk patched boot img for you guys wanting root on your new android 10 open beta 1 software.
PLEASE BE AWARE THIS DOESNT COME WITH TWRP, THIS MAY ALSO BREAK THE ORIGINAL STOCK RECOVERY, BY FLASHING THIS BOOT IMG, YOU TAKE FULL RESPONSIBILITY FOR YOUR DEVICE AND NEITHER I OR XDA WILL BE HELD RESPONSIBLE
this DOESNT contain TWRP but is just rooted with magisk v20.0
simply flash the provided file in fastboot with the following command
Code:
fastboot flash boot magisk_patched.img
Code:
fastboot reboot
Please note this will ONLY work with the OnePlus 6T
i have also provided the stock android 10 boot img in case anything goes wrong
DOWNLOADS::
[CURRENT VERSION - Magisk V20.1]
Mega -> https://mega.nz/#!YI5BkICC!66fiUUdmg1EgGcTNExHZ52IoliVY4HBMBdwxErpI-co
Google Drive -> https://drive.google.com/file/d/1xyRPzsKh1kQXK0_RpdnesuR85vc6FvRf/view?usp=sharing
[OLD Versions]
[Magisk V20.0]
https://mega.nz/#!cQRFwA7b!R1yLz1ozFUTEOLXv-OREK-oF5YeUGN1PrWvSSh22vHw
Stock Boot img
https://mega.nz/#!1BAnRCoK!nu6UVAnR2yHnbaf54FEhc7U_3oEyP1q2BFMU0LK7XC4
Credits:
@oneplus for the phone and stock boot image
@topjohnwu for magisk and his boot image patcher
Trying now. Will report.
Update: Well, after a reboot, it is just sitting at the spinning animated boot logo...been like 10 minutes.
Also couldn't enter recovery after flashing the new patched boot img.
Update 2: Flashed back stock boot.img then recovery worked and phone booted fine.
Do i need a computer for this ?
techlogik said:
Trying now. Will report.
Update: Well, after a reboot, it is just sitting at the spinning animated boot logo...been like 10 minutes.
Also couldn't enter recovery after flashing the new patched boot img.
Update 2: Flashed back stock boot.img then recovery worked and phone booted fine.
Click to expand...
Click to collapse
Did you try this by chance? We have the A/B partitions I don't think "fastboot flash boot ... " flashes both partitions.
Code:
fastboot flash boot_a magisk_patched.img
fastboot flash boot_b magisk_patched.img
charlie95113 said:
Do i need a computer for this ?
Click to expand...
Click to collapse
yes because fastboot command is needed, henced done using pc.
mywebslave said:
Did you try this by chance? We have the A/B partitions I don't think "fastboot flash boot ... " flashes both partitions.
Code:
fastboot flash boot_a magisk_patched.img
fastboot flash boot_b magisk_patched.img
Click to expand...
Click to collapse
Only the active partition gets flashed by default that is booting...it does that fine. I don't think Magisk is compatible on the OP6T for rooting and patching the new boot.img.
Same thing even manually flashing both. It just sits with the spinning boot animation for eternity.
I also used the payload extractor and took the stock boot.img and patched it with Magisk myself. Same issue. So obviously Magisk just doesn't suppor this phone yet and Devs need to work on it.
Thx
techlogik said:
Did you try this by chance? We have the A/B partitions I don't think "fastboot flash boot ... " flashes both partitions.
Only the active partition gets flashed by default that is booting...it does that fine. I don't think Magisk is compatible on the OP6T for rooting and patching the new boot.img.
Same thing even manually flashing both. It just sits with the spinning boot animation for eternity.
I tried patching the stock boot.img myself as well, it ends up being the exact same size as the TS for this method...same problem.
Thx
Click to expand...
Click to collapse
Weird I was able to do the local update and install magisk to the inactive partition prior to reboot. On reboot worked fine just no recovery.
Maybe it just doesn't like this particular one. I used the latest canary version.
I'll try patching one when I get home and see how it goes. If it works out I'll post it here.
mywebslave said:
Weird I was able to do the local update and install magisk to the inactive partition prior to reboot. On reboot worked fine just no recovery.
Maybe it just doesn't like this particular one. I used the latest canary version.
I'll try patching one when I get home and see how it goes. If it works out I'll post it here.
Click to expand...
Click to collapse
Yes, I did the same thing. Also, as mentioned above, I used the payload extractor and grabbed the stock boot.img right from the Beta1 zip file.
Then, cppied over to the phone, used Magisk with Canary build as well, then flashed both boot_a and b directly with the patched file. Just sits at the animated boot spinning.
Flash stock images back, boots right up. I'm on a OP6T unlocked US phone on VZW. No problems with any other build beta or stable with twrp or magisk and custom kernels.
Thanks
techlogik said:
Yes, I did the same thing. Also, as mentioned above, I used the payload extractor and grabbed the stock boot.img right from the Beta1 zip file.
Then, cppied over to the phone, used Magisk with Canary build as well, then flashed both boot_a and b directly with the patched file. Just sits at the animated boot spinning.
Flash stock images back, boots right up. I'm on a OP6T unlocked US phone on VZW. No problems with any other build beta or stable with twrp or magisk and custom kernels.
Thanks
Click to expand...
Click to collapse
So weird. Same setup as mine op6t, unlocked, Verizon. Haven't had a single issue. I'm gonna give it a try in a few minutes. I'll see what happens
---------- Post added at 08:19 PM ---------- Previous post was at 07:43 PM ----------
I did a fresh payload dump. Flashed to both A/B partitions, reboot, booted up fast as hell.
Here's the one I patched
magisk_patched.img
boot.img
Not sure if it makes a difference but I did mine on linux with latest platform tools.
mywebslave said:
So weird. Same setup as mine op6t, unlocked, Verizon. Haven't had a single issue. I'm gonna give it a try in a few minutes. I'll see what happens
---------- Post added at 08:19 PM ---------- Previous post was at 07:43 PM ----------
I did a fresh payload dump. Flashed to both A/B partitions, reboot, booted up fast as hell.
Here's the one I patched
magisk_patched.img
boot.img
Not sure if it makes a difference but I did mine on linux with latest platform tools.
Click to expand...
Click to collapse
So should we be using this instead?
Sent from my ONEPLUS A6013 using Tapatalk
mywebslave said:
So weird. Same setup as mine op6t, unlocked, Verizon. Haven't had a single issue. I'm gonna give it a try in a few minutes. I'll see what happens
---------- Post added at 08:19 PM ---------- Previous post was at 07:43 PM ----------
I did a fresh payload dump. Flashed to both A/B partitions, reboot, booted up fast as hell.
Here's the one I patched
magisk_patched.img
boot.img
Not sure if it makes a difference but I did mine on linux with latest platform tools.
Click to expand...
Click to collapse
Gave this a try, no luck. Stuck in bootloop but as soon as I flashed back the stock boot, it booted up just fine
zhenliang1102 said:
Gave this a try, no luck. Stuck in bootloop but as soon as I flashed back the stock boot, it booted up just fine
Click to expand...
Click to collapse
And this one?
fastboot --set_active=a
fastboot flash boot magisk_patched.img
fastboot --set_active=b
fastboot flash boot magisk_patched.img
fastboot --set_active=a
fastboot reboot
when i flash the magisk_patched.img and my cellphone reboot my cellphone does not recognize my simcard and have no network, am back on the stock boot.img
cultofluna said:
And this one?
fastboot --set_active=a
fastboot flash boot magisk_patched.img
fastboot --set_active=b
fastboot flash boot magisk_patched.img
fastboot --set_active=a
fastboot reboot
Click to expand...
Click to collapse
I doubt this would work because the patched image is only 26mb while the stock boot image is 64mb. Someone mentioned this in the OB thread
Black screen after the update
[Solved] I am facing a serious issue. I was on Magisk v20.0 and Twrp 3.3.1-1
- I uninstalled Magisk
- Installed the OTA from local
- Installed Magisk on the second partition
- Reboot
Phone rebooted
But I am getting a totally blacked out screen. Calls work, vibration, Oneplus gestures work, just the screen is black (even in safe mode)
Can anyone please help me get this sorted (with data preserved if possible) I didn't back up the data cuz I wanted to do it after I updated to 10 (as downgrading wipes the system)
Problems:
ADB is not working (unauthorized) as I haven't turned on any developer options yet and can't due to black screen.
No way to unroot at this point without adb or twrp.
Thanks in advance.
UPDATE: Flashed boot.img and it worked. I guess magisk.img is not compatible or I am doing it wrong. My bet is on the latter.
Hy, do you have proximity sensor problem after update?! Thanks...is anything i can do?
jack5225 said:
[Solved] I am facing a serious issue. I was on Magisk v20.0 and Twrp 3.3.1-1
- I uninstalled Magisk
- Installed the OTA from local
- Installed Magisk on the second partition
- Reboot
Phone rebooted
But I am getting a totally blacked out screen. Calls work, vibration, Oneplus gestures work, just the screen is black (even in safe mode)
Can anyone please help me get this sorted (with data preserved if possible) I didn't back up the data cuz I wanted to do it after I updated to 10 (as downgrading wipes the system)
Problems:
ADB is not working (unauthorized) as I haven't turned on any developer options yet and can't due to black screen.
No way to unroot at this point without adb or twrp.
Thanks in advance.
UPDATE: Flashed boot.img and it worked. I guess magisk.img is not compatible or I am doing it wrong. My bet is on the latter.
Click to expand...
Click to collapse
Same happened to me
Phone boots to a Black screen
adb reboot bootloader -> works
fastboot flash boot boot.img -> works
Only Patched boot.img -> boots to black screen
Sent from my ONEPLUS A6010 using Tapatalk
Same for me. Softbrick and phone doesn't boot. It also encrypted my whole /data with diferent password i think and I had to wipe whole /data partition. System boots after wiping data storage but as soon as I install magisk it doesn't want to boot again. I guess I will wait for final image and TWRP support.
i couldnt flash it manually (via cmd), but all in one tool managed it well.
worked fine and quick,thank you
Crazy that some phones it is working and others it doesn't. Nothing we are doing wrong, OP has work to do still. I can imagine this official update to Q is going to cause a support fiasco...if you want to root that is. ROFL. All works fine with stock though upgrade. Understand it is Beta, but they claim a November official release
We are going to need some Dev help. Or going to need to sell this phone and upgrade to the 7t or Pro..haha
Here ya go, couldn't find it anywhere so I figured I would save people some time.
I was trying to get Magisk to work on A11 Beta, but I can't even get into TWRP because Im getting Quallcom Crash Dump when I try to boot into TWRP.
Could you give some info how to flash this (fastboot ?) to get Magisk working?
And will I have to reflash once OOS hits stable or gets an update?
Thanks!
Yeah, same issue here. Install magisk 23 apk, then reboot to fastboot. Now, fastboot flash boot_a "patched boot image attached" then fastboot flash boot_b with the same img. Fastboot reboot
Hopefully we will have a working TWRP soon so by the time the next release is out everything can be done with the oxygen updater app or through TWRP itself
Yeedatoy said:
Here ya go, couldn't find it anywhere so I figured I would save people some time.
Click to expand...
Click to collapse
can this work for oneplus 6 too?
deeptanshuB said:
can this work for oneplus 6 too?
Click to expand...
Click to collapse
I don't think so, unfortunately
hello evryone i need to root my phone sm a202f i tried evrythimg if i try to flash twrp odin says complete write operation failed on my bootloader custom binary blocked i also tried with ADB but no so can someone tell me how to root it please Android 11
Picked one of these up on the weekend and was looking at going to linageos.
patched upto latest, and went through the linage install steps but missed the step on after installing the bootloader unlock software going into options and unlocking.
Went ahead and installed the linage recovery but now just get a basic screen with options of
START
RESTART BOOTLOADER
RECOVERY MODE
POWER OFF
All options loop me around back to the same place.
trying to start, ends me up with a your device is corrupt message.
I've been trying to get it back to factory.
QPST and QFIL can't see the device.
i can see the device in fastboot.
have downloaded latest firmware.
extracted using payload_dumper
no recovery.img on there.
updated the boot.img, vendor_boot.img dtbo.img from Question - My Asus Zenfone 8 flip is STUCK in CSC FASTBOOT MODE PLZ HELP!, RAW FIRMWARE ANYONE??? | XDA Forums
but no luck as there is no recovery.img in the firmware package.
Any ideas?
Somewhere there was FW update (at least I remember .115) to downgrade from beta A12 to .115FW (android 11). And it could help you I hope. At least you can try.
Yeah all is not lost. Etract and run this to get you back to factory stock. If you can't connect with fastboot, it's a driver issue and you'll just have Google it and pay around until you get the driver right.
Firmware I'm on would be WW-30.12.112.62 i think
is that android 11?
thatguy222 said:
Yeah all is not lost. Etract and run this to get you back to factory stock. If you can't connect with fastboot, it's a driver issue and you'll just have Google it and pay around until you get the driver right.
Click to expand...
Click to collapse
Thanks, will give this a go
no luck, same message.
That link doesn't have a recovery.img either.
am I missing something
running fastboot for boot.img and vendor_boot.img
fastboot flash boot D:\asus\payload_dumper-master\output\boot.img
fastboot flash vendor_boot D:\asus\payload_dumper-master\output\vendor_boot.img
is there more img's i'm meant to be flashing?
Onthax said:
no luck, same message.
That link doesn't have a recovery.img either.
am I missing something
running fastboot for boot.img and vendor_boot.img
fastboot flash boot D:\asus\payload_dumper-master\output\boot.img
fastboot flash vendor_boot D:\asus\payload_dumper-master\output\vendor_boot.img
is there more img's i'm meant to be flashing?
Click to expand...
Click to collapse
I was once stuck in a bootloop after flashing a custom rom and did a fresh install of official firmware.
Go to this website https://www.asus.com/Content/Android-12-Beta/ and scroll down to "How to opt-out and revert back to Android 11" section. There you can download the firmware file and a 3 step instruction.
By doing so I was able to bring back my phone.
The version of the firmware is from 2021/09/03 (WW-30.11.51.115) so you just need to update to newest release and everything should be fine.
T3chDelicious said:
I was once stuck in a bootloop after flashing a custom rom and did a fresh install of official firmware.
Go to this website https://www.asus.com/Content/Android-12-Beta/ and scroll down to "How to opt-out and revert back to Android 11" section. There you can download the firmware file and a 3 step instruction.
By doing so I was able to bring back my phone.
The version of the firmware is from 2021/09/03 (WW-30.11.51.115) so you just need to update to newest release and everything should be fine.
Click to expand...
Click to collapse
Thanks T3chDelicious
That did the trick, back to a working stock phone
Onthax said:
Thanks T3chDelicious
That did the trick, back to a working stock phone
Click to expand...
Click to collapse
You're welcome