Related
RIVER_RETAIL_9.0_PPO29.114-134_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip
also available for xt1962-4
Change log?
ptn107 said:
RIVER_RETAIL_9.0_PPO29.114-134_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip
also available for xt1962-4
Click to expand...
Click to collapse
Thanks a lot, my friend... Now I can root my Moto G7 River again! ?
How do I flash this .zip?
ptn107 said:
RIVER_RETAIL_9.0_PPO29.114-134_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip
also available for xt1962-4
Click to expand...
Click to collapse
Tried to install on a xt1962-4 and it goes bootloop :c
MatheusDeFino said:
Tried to install on a xt1962-4 and it goes bootloop :c
Click to expand...
Click to collapse
-
My link is for the xt1962-1. Did you get the appropriate xt1962-4 image for your device?
XT1962-4_RIVER_RETBR_9.0_PPO29.114-134_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip
XT1962-4_RIVER_RETLA_9.0_PPO29.114-134_cid50_subsidy-DEFAULT_regulatory-XT1962-4-SUTEL-DS_CFC.xml.zip
The xt1962-4 has options. You need to know which one is correct for you.
ptn107 said:
-
My link is for the xt1962-1. Did you get the appropriate xt1962-4 image for your device?
XT1962-4_RIVER_RETBR_9.0_PPO29.114-134_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip
XT1962-4_RIVER_RETLA_9.0_PPO29.114-134_cid50_subsidy-DEFAULT_regulatory-XT1962-4-SUTEL-DS_CFC.xml.zip
The xt1962-4 has options. You need to know which one is correct for you.
Click to expand...
Click to collapse
How install?
Mathiusb said:
How install?
Click to expand...
Click to collapse
Code:
fastboot getvar max-sparse-size
fastboot oem fb_mode_set
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot flash modem NON-HLOS.bin
fastboot flash fsg fsg.mbn
fastboot erase modemst1
fastboot erase modemst2
fastboot flash dsp adspso.bin
fastboot flash dtbo dtbo.img
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash system system.img_sparsechunk.0
fastboot flash system system.img_sparsechunk.1
fastboot flash system system.img_sparsechunk.2
fastboot flash system system.img_sparsechunk.3
fastboot flash system system.img_sparsechunk.4
fastboot flash system system.img_sparsechunk.5
fastboot flash system system.img_sparsechunk.6
fastboot flash system system.img_sparsechunk.7
fastboot flash system system.img_sparsechunk.8
fastboot flash system system.img_sparsechunk.9
fastboot flash system_b system_b.img_sparsechunk.0
fastboot flash system_b system_b.img_sparsechunk.1
fastboot flash system_b system_b.img_sparsechunk.2
fastboot flash vendor vendor.img_sparsechunk.0
fastboot flash vendor vendor.img_sparsechunk.1
fastboot flash vendor vendor.img_sparsechunk.2
fastboot flash oem oem.img
fastboot flash oem_b oem_other.img
fastboot erase userdata
fastboot erase DDR
fastboot oem fb_mode_clear
Unroot first?
I'm fairly new to rooting on the Moto G7 since I've only tinkered with my Asus Zenfone. I'm currently rooted on the G7 running PPOS29.114-16-5-2 and patched with Magisk. Do I need to unroot, ie. go back to stock, then upgrade to PPO29.114-134 then root and patch again?
eztechio said:
I'm fairly new to rooting on the Moto G7 since I've only tinkered with my Asus Zenfone. I'm currently rooted on the G7 running PPOS29.114-16-5-2 and patched with Magisk. Do I need to unroot, ie. go back to stock, then upgrade to PPO29.114-134 then root and patch again?
Click to expand...
Click to collapse
You can manually download and flash the new firmware and then patch boot with magisk again. You do not need to go back to stock first.
adb sideload
I'm trying to adb sideload the zip from recovery and the minute I execute I get adbd status 1 Installation aborted. Also it seems through RSD lite that the zip is corrupted. Anyone else get this issue?
Filename differences PPO vs PPOS
Does PPO vs PPOS in the filename mean that PPOS can be sideloaded and the other only via OTA or from internal?
ptn107 said:
Code:
fastboot getvar max-sparse-size
fastboot oem fb_mode_set
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot flash modem NON-HLOS.bin
fastboot flash fsg fsg.mbn
fastboot erase modemst1
fastboot erase modemst2
fastboot flash dsp adspso.bin
fastboot flash dtbo dtbo.img
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash system system.img_sparsechunk.0
fastboot flash system system.img_sparsechunk.1
fastboot flash system system.img_sparsechunk.2
fastboot flash system system.img_sparsechunk.3
fastboot flash system system.img_sparsechunk.4
fastboot flash system system.img_sparsechunk.5
fastboot flash system system.img_sparsechunk.6
fastboot flash system system.img_sparsechunk.7
fastboot flash system system.img_sparsechunk.8
fastboot flash system system.img_sparsechunk.9
fastboot flash system_b system_b.img_sparsechunk.0
fastboot flash system_b system_b.img_sparsechunk.1
fastboot flash system_b system_b.img_sparsechunk.2
fastboot flash vendor vendor.img_sparsechunk.0
fastboot flash vendor vendor.img_sparsechunk.1
fastboot flash vendor vendor.img_sparsechunk.2
fastboot flash oem oem.img
fastboot flash oem_b oem_other.img
fastboot erase userdata
fastboot erase DDR
fastboot oem fb_mode_clear
Click to expand...
Click to collapse
Is this method to install for RIVER_RETAIL_9.0_PPO29.114-134_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip or it is for Mathiusb's xt1962-4 version?
---------- Post added at 02:21 AM ---------- Previous post was at 02:00 AM ----------
Actually ignore my posts. I just read the flashfile.xml in the zip and it has the same steps. duh!
Fastboot 'waiting for any device'
A new Moto G7 XT-1962 US-Retail running the original ROM, unlocked, rooted, and with TWRP installed. It seems to be working okay but somehow during unlocking and setup, it no longer detects the SIM.
So I thought that flashing the most-recent update might also resolve the SIM problem at the same time. Steps from this forum were followed with a difference that I was using a Mac. The contents of the platform-tools (adb-fastboot) directory were combined with the extracted ROM zip files and the terminal launched from there. Like the Windows technique.
ADB works now and Fastboot had worked before using this same approach for the oem unlocking routine:
Code:
$ adb devices
* daemon not running; starting now at tcp:5037
* daemon started successfully
List of devices attached
ZY226JMG38 device
Now Fastboot (from platform-tools_r29.0.4-darwin.zip) returns "waiting…" and hangs:
Code:
$ fastboot device
< waiting for any device >
$ fastboot getvar max-sparse-size
< waiting for any device >
$ fastboot oem fb_mode_set
< waiting for any device >
$ sudo fastboot device
Password:
< waiting for any device >
Any suggestions about Fastboot and comments about fixing my undetected SIM appreciated. This flashing routine is a scary undertaking for this dummie.
@dlfuller - Is your device booted in bootloader? When you do fastboot devices -l does your device show up?
eztechio said:
@dlfuller - Is your device booted in bootloader? When you do fastboot devices -l does your device show up?
Click to expand...
Click to collapse
Thanks @eztechio, but the problem turns out to be the fastboot command itself. Only <waiting for device> in the code sample of my post.
---------- Post added at 11:32 AM ---------- Previous post was at 11:25 AM ----------
I stumbled across the answer to my main question elsewhere and hope this might be helpful to other Mac users.
In MacOS adb and fastboot commands must be preceded with "./" most of the time. Why the exception where some adb commands work without it I don't know.
Code:
$ adb devices
List of devices attached
ZY226JMG38 device
$ ./adb devices
List of devices attached
ZY226JMG38 device
$ ./adb reboot bootloader
$ ./fastboot devices
ZY226JMG38 fastboot
$ ./fastboot getvar max-sparse-size
max-sparse-size: 268435456
finished. total time: 0.000s
With fastboot working now, it's on to this dummie adventuring into the ROM update…
Thanks @ptn107. Your fastboot steps worked like a charm. I'm now up to date on ROM Build PPOS29.114-134-2
A fresh, clean slate. Just had to install TWRP and Magisk again. My problem before of not detecting the SIM now resolved.
Just wish I could have retained my user apps and data through the upgrade process. Not executing fastboot erase userdata might have been the approach, but I didn't want to chance it.
eztechio said:
I'm trying to adb sideload the zip from recovery and the minute I execute I get adbd status 1 Installation aborted. Also it seems through RSD lite that the zip is corrupted. Anyone else get this issue?
Click to expand...
Click to collapse
I think u have to unzip and flash files through fastboot commands
@HueyT - Yes I had to extract the files and perform each fastboot command in my command prompt terminal. All is good now. I'm actually now on the latest released firmware by doing the same update steps.
Will it bootloop if I install RETUS on AMZ XT1962-1 phones?
am stuck on the bootloader after using the following commands :
Code:
fastboot flash boot_a twrp.img
Code:
fastboot flash boot_b twrp.img
I don't know how to go back...
Thanks for your help
Our old twrp have been great compared to nothing but it isn't exactly fully working and freezes a lot on splash screen.
Thanks to @Stricted and @deadman96385 we now have a more functional twrp.
Support for A/B slots.
ADB working.
No need to flash full firmware. Just flash the vbmeta_patch.img and boot twrp.
!!BOOTLOADER MUST BE UNLOCKED!!
YOUR DATA WILL BE WIPED!!
Code:
fastboot flash vbmeta vbmeta_patch.img
fastboot boot twrp-3.3.1-test3.img
Now that we booted to TWRP it's time to format data.
Go to wipe -> format data -> type yes.
"Permanent" install of TWRP (optional):
Copy "twrp-3.3.1-test3.img" to your device.
Boot "twrp-3.3.1-test3.img" from fastboot and go to advanced settings.
Use the option to install recovery ramdisk. In the "file manager" you pick the "twrp-3.3.1-test3.img"
This will extract the twrp ramdisk and install it to your boot.img.
When it's done, tap the "fix recovery bootloop" in advanced settings so that it won't reboot to recovery instead of system..
Since this replaces the ramdisk in boot.img you'll have to reflash magisk afterwards if you want root.
This must be done every time you update your boot.img.
-------------------------------------------------------------------------------------------------------------------------------------------------------
# ROOT:
-----------
# First time:
# Method 1: Root, forced encryption disabled. Full access to data from twrp:
Flash Magisk and Disable_Dm-Verity_ForceEncrypt.zip.
# Method 2: Root only. Device still encrypted and won't be able to decrypt / mount data in twrp.
Magisk modules through Magisk manager still works:
Flash only Magisk.
----------------------------------------------------------------------------------------------------
# Fastboot flash update without loosing root or data:
----------------------------------------------------------------------------------------
# Already rooted with encryption disabled:
Extract the firmware zip to your adb/fastboot folder.
You already have the patched vbmeta flashed so just remove the stock vbmeta.img from the folder after extraction to avoid flashing it by mistake.
Flash full firmware without wipe. (Use cmds from below. Save as .bat to make it more simple.)
Boot twrp and then install it, fix recovery bootloop.
Reboot recovery, flash Magisk and Disable_Dm-Verity_ForceEncrypt.zip.
Boot system.
Code:
echo off
echo - UPDATE AND PRESERV ROOT -
fastboot flash pit diskmap.pit
fastboot flash fwbl1 fwbl1.img
fastboot flash ldfw_a ldfw.img
fastboot flash ldfw_b ldfw.img
fastboot flash keystorage_a keystorage.img
fastboot flash keystorage_b keystorage.img
fastboot flash bootloader_a bootloader.img
fastboot flash bootloader_b bootloader.img
fastboot flash modem_a modem.bin
fastboot flash oem_a oem.img
fastboot flash oem_b oem_other.img
fastboot flash logo_a logo.bin
fastboot flash dtbo_a dtbo.img
fastboot flash system_a system.img_sparsechunk.0
fastboot flash system_a system.img_sparsechunk.1
fastboot flash system_a system.img_sparsechunk.10
fastboot flash system_a system.img_sparsechunk.2
fastboot flash system_a system.img_sparsechunk.3
fastboot flash system_a system.img_sparsechunk.4
fastboot flash system_a system.img_sparsechunk.5
fastboot flash system_a system.img_sparsechunk.6
fastboot flash system_a system.img_sparsechunk.7
fastboot flash system_a system.img_sparsechunk.8
fastboot flash system_a system.img_sparsechunk.9
fastboot flash system_b system_other.img_sparsechunk.0
fastboot flash system_b system_other.img_sparsechunk.1
fastboot flash system_b system_other.img_sparsechunk.2
fastboot flash vendor_a vendor.img
fastboot reboot bootloader
pause 10
fastboot boot twrp-3.3.1-test3.img
echo TWRP is booting..
echo - install recovery ramdisk, fix bootloop, flash magisk & dm-verity zip.
echo - alternatively flash only magisk and Disable_Dm-Verity_ForceEncrypt.zip if you want to keep stock recovery.
pause
# Already rooted with device still encrypted:
Flash firmware update, except vbmeta.
Boot twrp and flash Magisk with adb sideload.
(alternative method: boot twrp and flash magisk patched boot.img)
Download TWRP: https://images.stricted.net/test/troika/twrp-3.3.1-test3.img
Download Magisk: https://github.com/topjohnwu/Magisk/releases
Download vbmeta_patch.img & Disable_Dm-Verity_ForceEncrypt.zip attached below.
PLEASE, DON't QUOTE THE WHOLE OP.
Can I flash this image from inside existing twrp to update?
wolf45801 said:
Can I flash this image from inside existing twrp to update?
Click to expand...
Click to collapse
Not really. A/B devices doens't have recovery partition to flash the whole img to it's own partition.
Instead we have to install recovery ramdisk in to our boot.img but that option is missing in the old twrp.
I guess you could take the twrp installer zip for the old twrp and replace ramdisk-twrp.cpio in that zip to the ramdisk from new twrp, but I guess it's just easier to fastboot boot the new version and from there choose to install recovery ramdisk.
tys0n said:
Not really. A/B devices doens't have recovery partition to flash the whole img to it's own partition.
Instead we have to install recovery ramdisk in to our boot.img but that option is missing in the old twrp.
I guess you could take the twrp installer zip for the old twrp and replace ramdisk-twrp.cpio in that zip to the ramdisk from new twrp, but I guess it's just easier to fastboot boot the new version and from there choose to install recovery ramdisk.
Click to expand...
Click to collapse
Ok I'll do that thank you
Can't seem to find the download links for the vbmeta en Disable_Dm-Verity_ForceEncrypt.zip
nickholtus said:
Can't seem to find the download links for the vbmeta en Disable_Dm-Verity_ForceEncrypt.zip
Click to expand...
Click to collapse
Ah you're right. I made threads in both action and vision forum but apparently I forgot to add the files here. Sorry about that.
They've been added now.
Recently i was trying to flash Stag OS when i accidentally flashed the wrong img to the system partition. now I can only boot into fastboot and the Qualcomm Crash Dump Mode. Is there a way out of this? I tried unpacking my payload.bin and flashing each img individually but it took me back to the same error.
I have had this happen to two separate oneplus 9's. My recommendation would be to start trying to run MSM tools from the forums here (both for your correct device and then for other 9 variants, i had the most success using the India 9+ version then running the correct version once the phone was booting again)
I did that and it worked! I was having issues getting into msm mode but then I realized I wasn't supposed to hold the power button. Thanks!
Not everything must/and should use MSM since it's quite an advanced and dangerous tools. For Qualcomm CrashDump mode, you guys can just normally download full OTA ROM, use Payload Dumper to extract all the images, then flash with fastboot ( in fastbootD ), it can easily fix the situation without any risks using MSM.
For some who may concern :
fastboot flash abl abl.img
fastboot flash aop aop.img
fastboot flash bluetooth bluetooth.img
fastboot flash devcfg devcfg.img
fastboot flash dsp dsp.img
fastboot flash cpucp cpucp.img
fastboot flash featenabler featenabler.img
fastboot flash hyp hyp.img
fastboot flash imagefv imagefv.img
fastboot flash keymaster keymaster.img
fastboot flash modem modem.img
fastboot flash multiimgoem multiimgoem.img
fastboot flash oplus_sec oplus_sec.img
fastboot flash oplusstanvbk oplusstanvbk.img
fastboot flash qupfw qupfw.img
fastboot flash qweslicstore qweslicstore.img
fastboot flash shrm shrm.img
fastboot flash tz tz.img
fastboot flash uefisecapp uefisecapp.img
fastboot flash vbmeta vbmeta.img
fastboot flash vbmeta_system vbmeta_system.img
fastboot flash vbmeta_vendor vbmeta_vendor.img
fastboot flash vendor_boot vendor_boot.img
fastboot flash vm-bootsys vm-bootsys.img
fastboot flash xbl xbl.img
fastboot flash xbl_config xbl_config.img
fastboot flash odm odm.img
fastboot flash product product.img
fastboot flash system system.img
fastboot flash system_ext system_ext.img
fastboot flash vendor vendor.img
LinhBT said:
Not everything must/and should use MSM since it's quite an advanced and dangerous tools. For Qualcomm CrashDump mode, you guys can just normally download full OTA ROM, use Payload Dumper to extract all the images, then flash with fastboot ( in fastbootD ), it can easily fix the situation without any risks using MSM.
For some who may concern :
fastboot flash abl abl.img
fastboot flash aop aop.img
fastboot flash bluetooth bluetooth.img
fastboot flash devcfg devcfg.img
fastboot flash dsp dsp.img
fastboot flash cpucp cpucp.img
fastboot flash featenabler featenabler.img
fastboot flash hyp hyp.img
fastboot flash imagefv imagefv.img
fastboot flash keymaster keymaster.img
fastboot flash modem modem.img
fastboot flash multiimgoem multiimgoem.img
fastboot flash oplus_sec oplus_sec.img
fastboot flash oplusstanvbk oplusstanvbk.img
fastboot flash qupfw qupfw.img
fastboot flash qweslicstore qweslicstore.img
fastboot flash shrm shrm.img
fastboot flash tz tz.img
fastboot flash uefisecapp uefisecapp.img
fastboot flash vbmeta vbmeta.img
fastboot flash vbmeta_system vbmeta_system.img
fastboot flash vbmeta_vendor vbmeta_vendor.img
fastboot flash vendor_boot vendor_boot.img
fastboot flash vm-bootsys vm-bootsys.img
fastboot flash xbl xbl.img
fastboot flash xbl_config xbl_config.img
fastboot flash odm odm.img
fastboot flash product product.img
fastboot flash system system.img
fastboot flash system_ext system_ext.img
fastboot flash vendor vendor.img
Click to expand...
Click to collapse
It's not dangerous to use the MSM tool that's made for your device. Manual fastboot flashing is more likely to cause problems due to human error than the MSM is. The MSM is done quicker too.
Hi,
I'll try to follow your tutorial, I have an LE2113 and I only cna boot into Qualcomm Crash Dump Mode, sometimes into bootloader mode.
I tried to follow the tutorials to root the phone, but I didn't do it until my OnePlus6, and the tutorials looks more complicated than in the past, in my opinion, it missed a lot of step for the beginners.
I'll try to find a way to make my phone alive again.
EtherealRemnant said:
It's not dangerous to use the MSM tool that's made for your device. Manual fastboot flashing is more likely to cause problems due to human error than the MSM is. The MSM is done quicker too.
Click to expand...
Click to collapse
I always trust myself more than any other tools But yeah, for some, the tools would be more confort
LinhBT said:
I always trust myself more than any other tools But yeah, for some, the tools would be more confort
Click to expand...
Click to collapse
Yeah I have never had an issue with manual flashing either but all the reports of people bricking and having to use MSM tell me that it's pretty common with OnePlus devices. I saw so many of those reports that I made sure MSM Tool was working before I even unlocked my bootloader lol.
EtherealRemnant said:
Yeah I have never had an issue with manual flashing either but all the reports of people bricking and having to use MSM tell me that it's pretty common with OnePlus devices. I saw so many of those reports that I made sure MSM Tool was working before I even unlocked my bootloader lol.
Click to expand...
Click to collapse
True bro. I used to try in vain lots of MSM build just to find one which can actually works and unbrick my 8T, but if not sahara error, then would be param or else. At last, fastboot saved my ass ))
LinhBT said:
True bro. I used to try in vain lots of MSM build just to find one which can actually works and unbrick my 8T, but if not sahara error, then would be param or else. At last, fastboot saved my ass ))
Click to expand...
Click to collapse
I was kind of surprised at how straightforward it was. I booted up Windows 11, installed the drivers, put the USB cord for my Pixel 3 XL in the USB-C port, put phone in EDL with the key combo, ran MSM. Zero issues either time I have tried it. I was absolutely prepared to have to fight with it.
EtherealRemnant said:
I was kind of surprised at how straightforward it was. I booted up Windows 11, installed the drivers, put the USB cord for my Pixel 3 XL in the USB-C port, put phone in EDL with the key combo, ran MSM. Zero issues either time I have tried it. I was absolutely prepared to have to fight with it.
Click to expand...
Click to collapse
Yeah, after I figured out what happened, then the rest are just like what u said. Turns out that my 8T was having CyberPunk param ( I did tried to convert ) therefore, MSM doesn't recognized it since MSM is specific for each model ))
LinhBT said:
Not everything must/and should use MSM since it's quite an advanced and dangerous tools. For Qualcomm CrashDump mode, you guys can just normally download full OTA ROM, use Payload Dumper to extract all the images, then flash with fastboot ( in fastbootD ), it can easily fix the situation without any risks using MSM.
For some who may concern :
fastboot flash abl abl.img
fastboot flash aop aop.img
fastboot flash bluetooth bluetooth.img
fastboot flash devcfg devcfg.img
fastboot flash dsp dsp.img
fastboot flash cpucp cpucp.img
fastboot flash featenabler featenabler.img
fastboot flash hyp hyp.img
fastboot flash imagefv imagefv.img
fastboot flash keymaster keymaster.img
fastboot flash modem modem.img
fastboot flash multiimgoem multiimgoem.img
fastboot flash oplus_sec oplus_sec.img
fastboot flash oplusstanvbk oplusstanvbk.img
fastboot flash qupfw qupfw.img
fastboot flash qweslicstore qweslicstore.img
fastboot flash shrm shrm.img
fastboot flash tz tz.img
fastboot flash uefisecapp uefisecapp.img
fastboot flash vbmeta vbmeta.img
fastboot flash vbmeta_system vbmeta_system.img
fastboot flash vbmeta_vendor vbmeta_vendor.img
fastboot flash vendor_boot vendor_boot.img
fastboot flash vm-bootsys vm-bootsys.img
fastboot flash xbl xbl.img
fastboot flash xbl_config xbl_config.img
fastboot flash odm odm.img
fastboot flash product product.img
fastboot flash system system.img
fastboot flash system_ext system_ext.img
fastboot flash vendor vendor.img
Click to expand...
Click to collapse
I'll try your method, MSM don't work, even on test mode on Windows10. Last chance operation :/ but when I fastboot flash abl abl.img, I have the actual message:
fastboot: error: cannot load 'abl.img': No such file or directory
Click to expand...
Click to collapse
BroenGuiraldson said:
I'll try your method, MSM don't work, even on test mode on Windows10. Last chance operation :/ but when I fastboot flash abl abl.img, I have the actual message:
Click to expand...
Click to collapse
Normally, it's abl.elf bro, depends on the Firm u r using to flash
I'm trying to flash the "OnePlus9Oxygen_22.E.47_OTA_1470_all_2203102118_ad7f1.zip" for my LE2113 version.
I extracted all the img files. How can I know if it's abl.elf instead of abl ? What about the other image flash ?
I tried with the aop and it returns the same error.
In parallel, still trying to detect my phone on MSM :/
LinhBT said:
Not everything must/and should use MSM since it's quite an advanced and dangerous tools. For Qualcomm CrashDump mode, you guys can just normally download full OTA ROM, use Payload Dumper to extract all the images, then flash with fastboot ( in fastbootD ), it can easily fix the situation without any risks using MSM.
For some who may concern :
fastboot flash abl abl.img
fastboot flash aop aop.img
fastboot flash bluetooth bluetooth.img
fastboot flash devcfg devcfg.img
fastboot flash dsp dsp.img
fastboot flash cpucp cpucp.img
fastboot flash featenabler featenabler.img
fastboot flash hyp hyp.img
fastboot flash imagefv imagefv.img
fastboot flash keymaster keymaster.img
fastboot flash modem modem.img
fastboot flash multiimgoem multiimgoem.img
fastboot flash oplus_sec oplus_sec.img
fastboot flash oplusstanvbk oplusstanvbk.img
fastboot flash qupfw qupfw.img
fastboot flash qweslicstore qweslicstore.img
fastboot flash shrm shrm.img
fastboot flash tz tz.img
fastboot flash uefisecapp uefisecapp.img
fastboot flash vbmeta vbmeta.img
fastboot flash vbmeta_system vbmeta_system.img
fastboot flash vbmeta_vendor vbmeta_vendor.img
fastboot flash vendor_boot vendor_boot.img
fastboot flash vm-bootsys vm-bootsys.img
fastboot flash xbl xbl.img
fastboot flash xbl_config xbl_config.img
fastboot flash odm odm.img
fastboot flash product product.img
fastboot flash system system.img
fastboot flash system_ext system_ext.img
fastboot flash vendor vendor.img
Click to expand...
Click to collapse
Are you sure this is right? I don't see boot.img in that list.
Z-Blade said:
Are you sure this is right? I don't see boot.img in that list.
Click to expand...
Click to collapse
boot.img dtbo.img ( and sometimes stock recovery.img )you will have to flash before execute this commands, since we will need to boot into fastbootD which only available in wherether boot.img or recovery.img
I accidentally flashed twrp-3.7.0_11-0-lemonadep.img onto my OP9 and is not met by Qualcomm Crashdump Mode constantly when trying to boot. wanted to boot it temporarily, but did this instead.
I tried temparirely booting after but it did not work sadly.
I read that I have to boot into Oxygen again, but I am pretty stuck on what's to do next, since I booting into fastbootd with no luck, which led me to not be able boot Oxygen.
Do any of you guys have any idea of what I can do to get out of this state and booted into LineageOS.
dimitrysulah6211 said:
I accidentally flashed twrp-3.7.0_11-0-lemonadep.img onto my OP9 and is not met by Qualcomm Crashdump Mode constantly when trying to boot. wanted to boot it temporarily, but did this instead.
I tried temparirely booting after but it did not work sadly.
I read that I have to boot into Oxygen again, but I am pretty stuck on what's to do next, since I booting into fastbootd with no luck, which led me to not be able boot Oxygen.
Do any of you guys have any idea of what I can do to get out of this state and booted into LineageOS.
Click to expand...
Click to collapse
reflash to stock and try again
I am doing this:
Restore OnePlus 9 to Stock via Fastboot Commands
This guide assumes you have the SDK Platform Tools installed and working, along with USB drivers for your device (if needed), and have your full update zip which you've already extracted the payload.bin from, and then dumped the images using...
forum.xda-developers.com
And already came to the part where I need to enter fastbootd, but when I turn off OP9 it boots into fastboot and if I do the command "fastboot reboot fastboot", it says this:
C:\Users\%Username%>fastboot reboot fastboot
usage: fastboot [ <option> ] <command>
This is the error codewhen flashing:
fastboot flash abl abl.img
target reported max download size of 805306368 bytes
sending 'abl' (2132 KB)...
OKAY [ 0.047s]
writing 'abl'...
FAILED (remote: Flashing is not allowed for Critical Partitions.
dimitrysulah6211 said:
I am doing this:
Restore OnePlus 9 to Stock via Fastboot Commands
This guide assumes you have the SDK Platform Tools installed and working, along with USB drivers for your device (if needed), and have your full update zip which you've already extracted the payload.bin from, and then dumped the images using...
forum.xda-developers.com
And already came to the part where I need to enter fastbootd, but when I turn off OP9 it boots into fastboot and if I do the command "fastboot reboot fastboot", it says this:
C:\Users\%Username%>fastboot reboot fastboot
usage: fastboot [ <option> ] <command>
This is the error codewhen flashing:
fastboot flash abl abl.img
target reported max download size of 805306368 bytes
sending 'abl' (2132 KB)...
OKAY [ 0.047s]
writing 'abl'...
FAILED (remote: Flashing is not allowed for Critical Partitions.
Click to expand...
Click to collapse
use these commands
fastboot reboot bootloader
after flash press space drag and drop the img file and wait for it to flash
fastboot flash
dimitrysulah6211 said:
I am doing this:
Restore OnePlus 9 to Stock via Fastboot Commands
This guide assumes you have the SDK Platform Tools installed and working, along with USB drivers for your device (if needed), and have your full update zip which you've already extracted the payload.bin from, and then dumped the images using...
forum.xda-developers.com
And already came to the part where I need to enter fastbootd, but when I turn off OP9 it boots into fastboot and if I do the command "fastboot reboot fastboot", it says this:
C:\Users\%Username%>fastboot reboot fastboot
usage: fastboot [ <option> ] <command>
This is the error codewhen flashing:
fastboot flash abl abl.img
target reported max download size of 805306368 bytes
sending 'abl' (2132 KB)...
OKAY [ 0.047s]
writing 'abl'...
FAILED (remote: Flashing is not allowed for Critical Partitions.
Click to expand...
Click to collapse
Never mind
bloxycola said:
use these commands
fastboot reboot bootloader
after flash press space drag and drop the img file and wait for it to flash
fastboot flash
Click to expand...
Click to collapse
try this
download the fastboot folder and driver from here ---> https://highonandroid.com/fastboot-zip-android-usb-drivers/
extract the fastboot folder
drag and drop the .imgs onto the fastboot folder then where the directory is (if your on windows) press on it and type in cmd the command promt will apear now connect your phone and turn it on and type
fastboot reboot bootloader
fastboot -w
fastboot flash boot boot.img
fastboot flash cpucp cpucp.img
fastboot flash dtbo dtbo.img
fastboot flash modem modem.img
fastboot flash oplusstanvbk oplusstanvbk.img
fastboot flash oplus_sec oplus_sec.img
fastboot flash qweslicstore qweslicstore.img
fastboot flash shrm shrm.img
fastboot flash splash splash.img
fastboot flash vbmeta vbmeta.img
fastboot flash vbmeta_vendor vbmeta_vendor.img
fastboot flash vbmeta_system vbmeta_system.img
fastboot flash vendor_boot vendor_boot.img
fastboot flash vm-bootsys vm-bootsys.img
fastboot reboot bootloader
fastboot flash abl abl.img
fastboot flash aop aop.img
fastboot flash bluetooth bluetooth.img
fastboot flash devcfg devcfg.img
fastboot flash dsp dsp.img
fastboot flash featenabler featenabler.img
fastboot flash hyp hyp.img
fastboot flash imagefv imagefv.img
fastboot flash keymaster keymaster.img
fastboot flash multiimgoem multiimgoem.img
fastboot flash qupfw qupfw.img
fastboot flash tz tz.img
fastboot flash uefisecapp uefisecapp.img
fastboot flash xbl xbl.img
fastboot flash xbl_config xbl_config.img
fastboot flash product product.img
fastboot flash system system.img
fastboot flash system_ext system_ext.img
fastboot flash vendor vendor.img
fastboot flash odm odm.img
fastboot reboot
if fastboot reboot bootloader not allowing you to flash try fastboot reboot fastboot
bloxycola said:
try this
download the fastboot folder and driver from here ---> https://highonandroid.com/fastboot-zip-android-usb-drivers/
extract the fastboot folder
drag and drop the .imgs onto the fastboot folder then where the directory is (if your on windows) press on it and type in cmd the command promt will apear now connect your phone and turn it on and type
fastboot reboot bootloader
fastboot -w
fastboot flash boot boot.img
fastboot flash cpucp cpucp.img
fastboot flash dtbo dtbo.img
fastboot flash modem modem.img
fastboot flash oplusstanvbk oplusstanvbk.img
fastboot flash oplus_sec oplus_sec.img
fastboot flash qweslicstore qweslicstore.img
fastboot flash shrm shrm.img
fastboot flash splash splash.img
fastboot flash vbmeta vbmeta.img
fastboot flash vbmeta_vendor vbmeta_vendor.img
fastboot flash vbmeta_system vbmeta_system.img
fastboot flash vendor_boot vendor_boot.img
fastboot flash vm-bootsys vm-bootsys.img
fastboot reboot bootloader
fastboot flash abl abl.img
fastboot flash aop aop.img
fastboot flash bluetooth bluetooth.img
fastboot flash devcfg devcfg.img
fastboot flash dsp dsp.img
fastboot flash featenabler featenabler.img
fastboot flash hyp hyp.img
fastboot flash imagefv imagefv.img
fastboot flash keymaster keymaster.img
fastboot flash multiimgoem multiimgoem.img
fastboot flash qupfw qupfw.img
fastboot flash tz tz.img
fastboot flash uefisecapp uefisecapp.img
fastboot flash xbl xbl.img
fastboot flash xbl_config xbl_config.img
fastboot flash product product.img
fastboot flash system system.img
fastboot flash system_ext system_ext.img
fastboot flash vendor vendor.img
fastboot flash odm odm.img
fastboot reboot
if fastboot reboot bootloader not allowing you to flash try fastboot reboot fastboot
Click to expand...
Click to collapse
I fixed it by downloading the MSM tool and flashing it into stock OxygenOS, with no issues whatsoever.
I will now try again, but this time boot it into TWRP temporarily and then flash it after.
dimitrysulah6211 said:
I fixed it by downloading the MSM tool and flashing it into stock OxygenOS, with no issues whatsoever.
I will now try again, but this time boot it into TWRP temporarily and then flash it after.
Click to expand...
Click to collapse
Yes
dimitrysulah6211 said:
I fixed it by downloading the MSM tool and flashing it into stock OxygenOS, with no issues whatsoever.
I will now try again, but this time boot it into TWRP temporarily and then flash it after.
Click to expand...
Click to collapse
Your trying to flash LineageOS right?
bloxycola said:
Your trying to flash LineageOS right?
Click to expand...
Click to collapse
Boot intro TWRP flash LineageOS then flash TWRP and try to se eif it boots
I believe that the right procedure is to update all the way up to OOS 13 F.20 firmware, then flash the Lineage Rec and from there flash LOS