X/SUZU/F5121 OmniROM BUILDS
OREO 8.1
DOWNLOAD WEEKLY
REQUIREMENTS TO SUCCESSFULLY FLASH OMNIROM:
1. The device has the latest stock ftf
2. The device has an unlocked bootloader
3. The ODM image zip has been downloaded from HERE, and the ODM image has been extracted from it
4. The WEEKLY zip file has been downloaded and copied to the device
INSTALLATION INSTRUCTIONS:
1. Reboot device to fastboot mode, and flash the ODM image with this command
Code:
fastboot flash oem <ODM image>
2. Reboot device to TWRP and flash the WEEKLY zip file
3. (Optional) Flash a gapps package
4. Reboot device to system
CURRENT ISSUES ON OFFICIAL:
1. No USB tethering
2. Wifi sometimes fails to turn on
KERNEL SOURCE: https://github.com/omnirom/android_kernel_sony_msm/tree/android-8.1
BUG REPORTS
REPORT BUGS ONLY:
- AFTER A CLEAN INSTALL
- USING STOCK OMNI KERNEL
- NO MODS OF ANY SORT
OMNI GERRIT REVIEW
[url]https://gerrit.omnirom.org/[/URL]
DISCLAIMER:
No one is responsible for any damage done to your device but YOU. You've been warned.
oshmoun said:
X/SUZU/F5121 OmniROM BUILDS
OREO 8.1
DOWNLOAD WEEKLY
REQUIREMENTS TO SUCCESSFULLY FLASH OMNIROM:
1. The device has the latest stock ftf
2. The device has an unlocked bootloader
3. The ODM image has been downloaded from HERE
4. The WEEKLY zip file has been downloaded and copied to the device
INSTALLATION INSTRUCTIONS:
1. Reboot device to fastboot mode, and flash the ODM image with this command
Code:
fastboot flash oem odm_loire.simg
2. Reboot device to TWRP and flash the WEEKLY zip file
3. (Optional) Flash a gapps package
4. Reboot device to system
CURRENT ISSUES ON OFFICIAL:
1. Wifi sometimes disconnects (fixed by enabling/disabling wifi)
2. Fingerprint sensor sometimes fails to detect or add new fingerprints (workaround available HERE )
3. No USB tethering
KERNEL SOURCE: https://github.com/omnirom/android_kernel_sony_msm/tree/android-8.0
BUG REPORTS
REPORT BUGS ONLY:
- AFTER A CLEAN INSTALL
- USING STOCK OMNI KERNEL
- NO MODS OF ANY SORT
OMNI GERRIT REVIEW
https://gerrit.omnirom.org/
DISCLAIMER:
No one is responsible for any damage done to your device but YOU. You've been warned.
Click to expand...
Click to collapse
Hi, I'm happy for the new version.
I'm already trying.
P.S. I noticed an error in the fastboot command [fastboot flash oem odm_loire.simg]
Thank you so much for your work!
Im getting error message bluetooth has stopped and phone restarts is there any particular reason clean install as it mentioned
Looks promising. Is video recording supported? And if yes, will you add [email protected] video capturing in the future? Current kernel codecs supports that...
Seems that Microg does not work properly. UnifiedNLP cannot be registered.
Are you able to get the dark mode? I enabled it, but it stays light.
Pico-TTS works again.
Gray47Maxx said:
Looks promising. Is video recording supported? And if yes, will you add [email protected] video capturing in the future? Current kernel codecs supports that...
Click to expand...
Click to collapse
video recording works, 60fps mode is probably not feasible currently.
mase76 said:
Seems that Microg does not work properly. UnifiedNLP cannot be registered.
Are you able to get the dark mode? I enabled it, but it stays light.
Pico-TTS works again.
Click to expand...
Click to collapse
microg requires some patches right? That's probably why it doesn't work.
Dark mode works here, the background of quicktiles changes to black (note that what you're changing is systemui style)
oshmoun said:
X/SUZU/F5121 OmniROM BUILDS
1. The device has the latest stock ftf
3. The ODM image has been downloaded from...
Two things are unclear to me:
What and for what is the ODM_image?
Why is the latest stock ftf required?
Thanks for ROM and answers
Click to expand...
Click to collapse
MichaBit said:
oshmoun said:
X/SUZU/F5121 OmniROM BUILDS
1. The device has the latest stock ftf
3. The ODM image has been downloaded from...
Two things are unclear to me:
What and for what is the UDM_image?
Why is the latest stock ftf required?
Thanks for ROM and answers
Click to expand...
Click to collapse
Hi
He probably meant OEM image...
Click to expand...
Click to collapse
Olimpo83 said:
MichaBit said:
Hi
He probably meant OEM image...
Click to expand...
Click to collapse
Exactly at the same minute I improved it - ODM is in op. ;P
---------- Post added at 10:23 PM ---------- Previous post was at 10:16 PM ----------
Olimpo83 said:
MichaBit said:
Hi
He probably meant OEM image...
Click to expand...
Click to collapse
Ahh, maybe right now im getting it; u mean 'OEM' is equal to stock?
(so i dont have to use Emma) :angel:
Click to expand...
Click to collapse
Click to expand...
Click to collapse
Why the latest stock ftf is also unclear to me. I did a dirty flash from Omni 7.1.2, flashed that odm image and things work so far.
I did not know, that darkmode is for the quicktiles only. I thought, that would also make the system apps dark.
My powermenu is strange. Only a poweroff and a silent button. How can I get the reboot menu? I also checked the extended reboot, but I never got it to see.
MichaBit said:
Two things are unclear to me:
What and for what is the ODM_image?
Why is the latest stock ftf required?
Click to expand...
Click to collapse
1. The ODM image contains proprietary binaries that are required by the system
2. The latest stock ftf is required to guarantee having the latest bootloader. That way support for flashing ODM image using fastboot is guaranteed.
Olimpo83 said:
Hi
He probably meant OEM image...
Click to expand...
Click to collapse
well, depends on how you define it:
1. if you define the image by its intended usage, it's an ODM image according to google.
2. if you define the image by the target partition on our devices, it's an OEM image.
I Have this Problem
On my device is omnirom 7.1.2
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash oem odm_loire.simg
target reported max download size of 536870912 bytes
sending 'oem' (347357 KB)...
OKAY [ 11.403s]
writing 'oem'...
FAILED (remote: Command not allowed)
finished. total time: 11.456s
Alsano86 said:
I Have this Problem
On my device is omnirom 7.1.2
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash oem odm_loire.simg
target reported max download size of 536870912 bytes
sending 'oem' (347357 KB)...
OKAY [ 11.403s]
writing 'oem'...
FAILED (remote: Command not allowed)
finished. total time: 11.456s
Click to expand...
Click to collapse
Please check OP more thoroughly, especially the part about having the latest stock ftf flashed
Alsano86 said:
I Have this Problem
On my device is omnirom 7.1.2
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash oem odm_loire.simg
target reported max download size of 536870912 bytes
sending 'oem' (347357 KB)...
OKAY [ 11.403s]
writing 'oem'...
FAILED (remote: Command not allowed)
finished. total time: 11.456s
Click to expand...
Click to collapse
i had the same problem you should not use by flash tool you have to do it on command prompt, place the file on a folder name it as flash then open the command prompt then paste fastboot flash oem odm_loire.simg thats it
---------- Post added at 06:33 AM ---------- Previous post was at 06:22 AM ----------
oshmoun said:
Please check OP more thoroughly, especially the part about having the latest stock ftf flashed
Click to expand...
Click to collapse
i manage to do as it mentioned but after few hours phone start to restart i cant make calls even i really wants to have this rom i tried
GCam5.1.018-Arnova8G2-V1.5.apk little buggy but portrait mode is awesome i cant imagine the pictures are so good on suzu
Alsano86 said:
I Have this Problem
On my device is omnirom 7.1.2
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash oem odm_loire.simg
target reported max download size of 536870912 bytes
sending 'oem' (347357 KB)...
OKAY [ 11.403s]
writing 'oem'...
FAILED (remote: Command not allowed)
finished. total time: 11.456s
Click to expand...
Click to collapse
I had written it in the second post.
The OEM file must have the extension .img
Rename it in oem_loire.img Change the file extension, put it in the platforms-tools folder, click with the right mouse button and at the same time click the Ctrl key on the keyboard to display the option OPEN CONTROL WINDOW HERE.
Turn off the mobile phone and then reconnect it to the PC by holding the VOLUME UP button, until the blue LED (Adb mode) appears. After doing this in the terminal enter the command FASTBOOT FLASH OEM OEM_LOIRE.IMG (written in lower case).
No way for install for me, got newest ftf and flashed oem image. Flashing of omnirom always ends at
Patching system image unconditionally...
E1001: Failed to update system image.
Updater process ended with ERROR 7
Error installing zip file
Click to expand...
Click to collapse
EDIT: Figured it out. I had to change odm_loire.img into oem_loire.img
rheckr said:
No way for install for me, got newest ftf and flashed oem image. Flashing of omnirom always ends at
EDIT: Figured it out. I had to change odm_loire.img into oem_loire.img
Click to expand...
Click to collapse
Those two things are absolutely unrelated.
Flashing the odm image does not change anything concerning how the zip is flashed in recovery. Simply renaming the file name also obviously has no effect.
So it must be something else that allowed the zip to successfully flash.
Fingerprint scanner doesn't work. Unable to add any finger.
Face unlock (trusted face) is missing. This omnirom is lacking two of most important features...
Front camera autofocus is messed also. I'll wait for stable release. Anyway good job.
hey guys,
since the lat update is online for the xperia x, my phone shows me that i can download and patch it automaticly. phone downloaded the rom, try to falsh it in twrp, restarts, but then it stucks at the white screen with the sony logo. i runned this for 2 hours, nothing happens. restartet in recovery mode, installed back to 7.1.2, phone works fine again. downloading the 8.1 rom and install it with twrp also ends in the same result.
someone of u have the same problems? is there an solution?
greetz
Related
How-to get a GSI running on your HTC U11 life Android One
Bootloader must be Unlocked
Stock Update to 8.1 must be installed
The Kernel must be Stock without any changes (no Magisk)
Make a Backup thats not Stored on Your Device
Remove the Google Account from the Device and Factory Reset the Device using the Recovery How-to
Download the correct GSI (arm64 a/b)
Flash the system.img using fastboot in Download Mode:
Code:
fastboot flash system_<slot> system.img
where <slot> is a or b depending on your active partition
Reboot the Device and Enjoy
Bugs with phh treble GSI (most others are based on this):
Mobile data doesnt work
Notification LED doesnt work
Audio Output only over speaker (known bug in this GSI for several devices)
List of compatible Roms
If you want to go back to Stock, just download the latest Full Firmware File here in post #2 and Restore the Device using SD Card method like written in post #1 of the same thread.
Updated, added the Guide
I try to flash GSI treble on HTC U11 Life but it doesn't work...
fastboot flash system_a /Users/thibautmaringer/Downloads/PixelExperienceP-arm64-ab.img
Sending sparse 'system_a' 1/3 (1048572 KB) OKAY [ 36.946s]
Writing sparse 'system_a' 1/3 (bootloader) HOSD CL#1033709
(bootloader) [email protected]
(bootloader) [email protected]%
FAILED ()
Finished. Total time: 111.730s
I don't understand...
this is the way to go when, i won't say if, HTC goes down and support will end for our phones.
maybe a bit more difficult than to just flash an image as we've always done, but not much more.
if HTC doesn't present a 9.0 before Xmas i will definitely install AOSP instead with no google at all.
titimar16 said:
I try to flash GSI treble on HTC U11 Life but it doesn't work...
fastboot flash system_a /Users/thibautmaringer/Downloads/PixelExperienceP-arm64-ab.img
Sending sparse 'system_a' 1/3 (1048572 KB) OKAY [ 36.946s]
Writing sparse 'system_a' 1/3 (bootloader) HOSD CL#1033709
(bootloader) [email protected]
(bootloader) [email protected]%
FAILED ()
Finished. Total time: 111.730s
I don't understand...
Click to expand...
Click to collapse
You should place the system.img (gsi) in the same folder where your adb and fastboot installation is. And you can see on the display of your device the progress of writing from 0% to 100% maybe you can have a look at it next time you flash something to see if it flashes at all.
saturday_night said:
You should place the system.img (gsi) in the same folder where your adb and fastboot installation is. And you can see on the display of your device the progress of writing from 0% to 100% maybe you can have a look at it next time you flash something to see if it flashes at all.
Click to expand...
Click to collapse
I tried that but it stuck on "system_a O%" then my cmd says "failed()"
./fastboot flash system_a system.img
Sending sparse 'system_a' 1/2 (1048572 KB) OKAY [ 35.131s]
Writing sparse 'system_a' 1/2 (bootloader) HOSD CL#1033709
(bootloader) [email protected]
(bootloader) [email protected]%
FAILED ()
Finished. Total time: 115.146s
I think that we can't flash GSI like that with the HTC U11 Life
titimar16 said:
I tried that but it stuck on "system_a O%" then my cmd says "failed()"
./fastboot flash system_a system.img
Sending sparse 'system_a' 1/2 (1048572 KB) OKAY [ 35.131s]
Writing sparse 'system_a' 1/2 (bootloader) HOSD CL#1033709
(bootloader) [email protected]
(bootloader) [email protected]%
FAILED ()
Finished. Total time: 115.146s
I think that we can't flash GSI like that with the HTC U11 Life
Click to expand...
Click to collapse
It works that way, already did it three times with three different systems. What file are you using? Do you even have the android one version of the u11 life or the Sense version?
saturday_night said:
It works that way, already did it three times with three different systems. What file are you using? Do you even have the android one version of the u11 life or the Sense version?
Click to expand...
Click to collapse
2 GSI: pixelexperience and phh-treble because I want to install Android P on my phone. I have the one version. So I'm on stock Android 8.1.
The files:
https://github.com/phhusson/treble_experimentations/releases/tag/v104 (ab arm64)
https://forum.xda-developers.com/pr...ce-development/9-0-pixelexperience-p-t3833294 (ab arm64 v9.0.0.r1)
titimar16 said:
2 GSI: pixelexperience and phh-treble because I want to install Android P on my phone. I have the one version. So I'm on stock Android 8.1.
The files:
https://github.com/phhusson/treble_experimentations/releases/tag/v104 (ab arm64)
https://forum.xda-developers.com/pr...ce-development/9-0-pixelexperience-p-t3833294 (ab arm64 v9.0.0.r1)
Click to expand...
Click to collapse
Android 9 GSIs are in an very early development stage and if you would read their threads you would know this. I dont even try it until phh treble has its first stable release.
saturday_night said:
Android 9 GSIs are in an very early development stage and if you would read their threads you would know this. I dont even try it until phh treble has its first stable release.
Click to expand...
Click to collapse
Okay, Thank you. And what have you tried ?
titimar16 said:
Okay, Thank you. And what have you tried ?
Click to expand...
Click to collapse
Android 8.1 GSIs
Today i tested for the first time an Android 9 GSI, phh treble got an update yesterday with a lot of bug fixes and it looks pretty good so far. Sadly we have the same bugs as with Android 8.1 GSIs. Its the first time phh treble gsi android 9 has GApps + Root integrated. I think those bugs we have are related to a faulty treble integration by HTC and cant be fixed by a dev of a GSI but its running good so far.
saturday_night said:
Today i tested for the first time an Android 9 GSI, phh treble got an update yesterday with a lot of bug fixes and it looks pretty good so far. Sadly we have the same bugs as with Android 8.1 GSIs and one additional bug. Its not possible to connect to hidden wifi networks, as long as the networks ssid is visible there is no problem to connect to it. Its the first time phh treble gsi android 9 has GApps + Root integrated. I think those bugs we have are related to a faulty treble integration by HTC and cant be fixed by a dev of a GSI but its running good so far.
Click to expand...
Click to collapse
Hi. Sorry but for me it doesn't work again. I did all the steps:
1) unlock bootloader
2) I'm on stock 2.13.401.1
3) I flashed using fastboot flash system_a system.img (from phh-treble 9 GSI with su and gapps)
4) it says again
Code:
fastboot flash system_a /Users/thibautmaringer/Downloads/system.img
Sending sparse 'system_a' 1/2 (1048572 KB) OKAY [ 32.109s]
Writing sparse 'system_a' 1/2 (bootloader) HOSD CL#1033709
(bootloader) [email protected]
(bootloader) [email protected]%
FAILED ()
Finished. Total time: 109.315s
and on my phone it says "flash success 2/2 start flashing" but nothing happened.
So can you explain how you did that well because for me it doesn't work.
titimar16 said:
Hi. Sorry but for me it doesn't work again. I did all the steps:
1) unlock bootloader
2) I'm on stock 2.13.401.1
3) I flashed using fastboot flash system_a system.img (from phh-treble 9 GSI with su and gapps)
4) it says again
Code:
fastboot flash system_a /Users/thibautmaringer/Downloads/system.img
Sending sparse 'system_a' 1/2 (1048572 KB) OKAY [ 32.109s]
Writing sparse 'system_a' 1/2 (bootloader) HOSD CL#1033709
(bootloader) [email protected]
(bootloader) [email protected]%
FAILED ()
Finished. Total time: 109.315s
and on my phone it says "flash success 2/2 start flashing" but nothing happened.
So can you explain how you did that well because for me it doesn't work.
Click to expand...
Click to collapse
Hmm, there are just two things where i could imagin that it causes a problem for you. First if you try to flash stuff from bootloader and not from download mode. Second would be a problematic usb connnection during the flash process. I have no other ideas sorry.
saturday_night said:
Hmm, there are just two things where i could imagin that it causes a problem for you. First if you try to flash stuff from bootloader and not from download mode. Second would be a problematic usb connnection during the flash process. I have no other ideas sorry.
Click to expand...
Click to collapse
Do you have
Code:
secure boot: PRODUCTION
? Because my usb connection is good and I flash files in "htc download mode"
Maybe can you explain precisely how you flash the GSI ?
titimar16 said:
Do you have
Code:
secure boot: PRODUCTION
? Because my usb connection is good and I flash files in "htc download mode"
Maybe can you explain precisely how you flash the GSI ?
Click to expand...
Click to collapse
1. I remove my Google Account from the Stock System
2. Reboot to bootloader - reboot to recovery and factory reset the device
3. reboot to bootloader and identify the active partition
4. reboot to download mode
5. flash Stock boot.img (because i was rooted before)
6. flash GSI system.img
If you need it more in detail just read the first posts in these two threads: https://forum.xda-developers.com/u11-life/how-to/collection-htc-u11-life-android-one-t3768265 https://forum.xda-developers.com/u11-life/how-to/treble-gsi-running-android-one-8-1-t3823015
And yes i have secure boot production and device state unlocked
saturday_night said:
1. I remove my Google Account from the Stock System
2. Reboot to bootloader - reboot to recovery and factory reset the device
3. reboot to bootloader and identify the active partition
4. reboot to download mode
5. flash Stock boot.img (because i was rooted before)
6. flash GSI system.img
If you need it more in detail just read the first posts in these two threads: https://forum.xda-developers.com/u11-life/how-to/collection-htc-u11-life-android-one-t3768265 https://forum.xda-developers.com/u11-life/how-to/treble-gsi-running-android-one-8-1-t3823015
And yes i have secure boot production and device state unlocked
Click to expand...
Click to collapse
What's your GSI file and android version ? (I mean the entire like 2.12.401....)
titimar16 said:
What's your GSI file and android version ? (I mean the entire like 2.12.401....)
Click to expand...
Click to collapse
I used the Stock boot.img from 2.12.401.17 and phh treble GSI arm64 a/b gapps su... exactly this file https://github.com/phhusson/treble_...download/v105/system-arm64-ab-gapps-su.img.xz
saturday_night said:
1. I remove my Google Account from the Stock System
2. Reboot to bootloader - reboot to recovery and factory reset the device
3. reboot to bootloader and identify the active partition
4. reboot to download mode
5. flash Stock boot.img (because i was rooted before)
6. flash GSI system.img
If you need it more in detail just read the first posts in these two threads: https://forum.xda-developers.com/u11-life/how-to/collection-htc-u11-life-android-one-t3768265 https://forum.xda-developers.com/u11-life/how-to/treble-gsi-running-android-one-8-1-t3823015
And yes i have secure boot production and device state unlocked
Click to expand...
Click to collapse
saturday_night said:
I used the Stock boot.img from 2.12.401.17 and phh treble GSI arm64 a/b gapps su... exactly this file https://github.com/phhusson/treble_...download/v105/system-arm64-ab-gapps-su.img.xz
Click to expand...
Click to collapse
And did you change something about CID of MID ?
titimar16 said:
And did you change something about CID of MID ?
Click to expand...
Click to collapse
No, dont change anything, that can cause a lot of problems
Hello Everyone!
I unlocked and installed TWRP on my P20 lite, but now I want to be able to install the updates of Huawei again (especially when Android P is about to release).
So how do I uninstall TWRP and if it's possbile lock my phone again?
(am not that amazing with Smartphone software, so just saying...)
Greets Louis
LouisJ444 said:
Hello Everyone!
I unlocked and installed TWRP on my P20 lite, but now I want to be able to install the updates of Huawei again (especially when Android P is about to release).
So how do I uninstall TWRP and if it's possbile lock my phone again?
(am not that amazing with Smartphone software, so just saying...)
Greets Louis
Click to expand...
Click to collapse
Maybe this thread somehow can helps you:
https://forum.xda-developers.com/huawei-p20-lite/help/req-stock-recovery-p20-lite-t3803027
Don't need lock bootloader to install or receive via OTA official updates.
Lock the bootloader is not possible (maybe it is, but is a pay service).
You can relock instead of lock, but don't do it if your device is not completely stock.
Within the little experience that I have with this team I have investigated the following, when flasheas the official roms by twrp the boatloader is blocked again and the twrp is erased
kilroystyx said:
Maybe this thread somehow can helps you:
https://forum.xda-developers.com/huawei-p20-lite/help/req-stock-recovery-p20-lite-t3803027
Don't need lock bootloader to install or receive via OTA official updates.
Lock the bootloader is not possible (maybe it is, but is a pay service).
You can relock instead of lock, but don't do it if your device is not completely stock.
Click to expand...
Click to collapse
I still don't really understand how it works:
I downloaded the huawei extractor and extracted the files in a folder on my computer.
I got a update.zip file from my phone and extracted it on my computer.
But when I try to open the update.app file I get an error message saying:
https://i.gyazo.com/abce07c696fb31f15b95c832e3baa899.png
(if it doesn't work: ERECOVERY_VBMET.img: Invalid header crc - Expected: 42613 Got 18415)
LouisJ444 said:
I still don't really understand how it works:
I downloaded the huawei extractor and extracted the files in a folder on my computer.
I got a update.zip file from my phone and extracted it on my computer.
But when I try to open the update.app file I get an error message saying:
https://i.gyazo.com/abce07c696fb31f15b95c832e3baa899.png
(if it doesn't work: ERECOVERY_VBMET.img: Invalid header crc - Expected: 42613 Got 18415)
Click to expand...
Click to collapse
Remove the verification on the settings, check pic enclosed.
Mannuok said:
Within the little experience that I have with this team I have investigated the following, when flasheas the official roms by twrp the boatloader is blocked again and the twrp is erased
Click to expand...
Click to collapse
Your are partially correct.
Flashing official firmware with TWRP, have to be done with HuRUpdater, during installation the TWRP is replaced by stock recovery, then is your decision keep it or not.
About lock bootloader, mine is unlocked since day one and every time that I install new firmware it keep it unlocked. My experience so far is installing ANE-LX1 firmware in my ANE-LX1 device, probably with other firmware like ANE-AL00 or ANE-TL00 it can be different.
kilroystyx said:
Remove the verification on the settings, check pic enclosed.
Click to expand...
Click to collapse
So I can't seem to do "adb reboot bootloader" It will just go to the system.
And when I manually go into the bootloader and try to flash it, I get this error
Before this I tried to flash an other recovery on it which I found on a guide, but after I did that TWRP did get removed but I can't get on the recovery anymore and updating doesn't work either.
LouisJ444 said:
So I can't seem to do "adb reboot bootloader" It will just go to the system.
And when I manually go into the bootloader and try to flash it, I get this error
Before this I tried to flash an other recovery on it which I found on a guide, but after I did that TWRP did get removed but I can't get on the recovery anymore and updating doesn't work either.
Click to expand...
Click to collapse
In the Fastboot&Rescue Mode screen did you see phone unlocked and FRP unlock ?
Can you share all commands that you are using, can be text like you see bellow:
Code:
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash recovery_ramdisk TWRP_3.2.1-0_ANE-LX1_Full_01.img
target reported max download size of 471859200 bytes
sending 'recovery_ramdisk' (24962 KB)...
OKAY [ 0.861s]
writing 'recovery_ramdisk'...
OKAY [ 0.109s]
finished. total time: 0.970s
Are you trying to use command recovery instead of recovery_ramdisk?
kilroystyx said:
In the Fastboot&Rescue Mode screen did you see phone unlocked and FRP unlock ?
Can you share all commands that you are using, can be text like you see bellow:
Code:
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash recovery_ramdisk TWRP_3.2.1-0_ANE-LX1_Full_01.img
target reported max download size of 471859200 bytes
sending 'recovery_ramdisk' (24962 KB)...
OKAY [ 0.861s]
writing 'recovery_ramdisk'...
OKAY [ 0.109s]
finished. total time: 0.970s
Are you trying to use command recovery instead of recovery_ramdisk?
Click to expand...
Click to collapse
1. It says: Phone Unlocked
FRP Unlock
2. When I was in this screen I do:
- cd C:\Users\Louis\Desktop\platform-tools
- fastboot flash recovery RECOVERY_RAMDIS.img
then it gives the error
3. When I try to do it normally, I do:
- cd C:\Users\Louis\Desktop\platform-tools
- adb reboot bootloader
LouisJ444 said:
1. It says: Phone Unlocked
FRP Unlock
2. When I was in this screen I do:
- cd C:\Users\Louis\Desktop\platform-tools
- fastboot flash recovery RECOVERY_RAMDIS.img
then it gives the error
3. When I try to do it normally, I do:
- cd C:\Users\Louis\Desktop\platform-tools
- adb reboot bootloader
Click to expand...
Click to collapse
You have to use recovery_ramdisk because this is the name of the partition in this Android version.
I assume that you didn't change the name of the stock recovery extracted, for your case the right command is:
Code:
fastboot flash recovery_ramdisk RECOVERY_RAMDIS.img
kilroystyx said:
You have to use recovery_ramdisk because this is the name of the partition in this Android version.
I assume that you didn't change the name of the stock recovery extracted, for your case the right command is:
Code:
fastboot flash recovery_ramdisk RECOVERY_RAMDIS.img
Click to expand...
Click to collapse
Thanks, that seemed to work!
kilroystyx said:
Your are partially correct.
Flashing official firmware with TWRP, have to be done with HuRUpdater, during installation the TWRP is replaced by stock recovery, then is your decision keep it or not.
About lock bootloader, mine is unlocked since day one and every time that I install new firmware it keep it unlocked. My experience so far is installing ANE-LX1 firmware in my ANE-LX1 device, probably with other firmware like ANE-AL00 or ANE-TL00 it can be different.
Click to expand...
Click to collapse
Where I get the original romes of Huawei???
Mannuok said:
Where I get the original romes of Huawei???
Click to expand...
Click to collapse
web version:
http://pro-teammt.ru/firmware-database/?firmware_model=&firmware_page=0
android version:
https://play.google.com/store/apps/details?id=com.teammt.gmanrainy.huaweifirmwarefinder
some tips:
https://forum.xda-developers.com/hu...om-official-emui-8-0-huawei-p20-lite-t3773999
kilroystyx said:
Your are partially correct.
Flashing official firmware with TWRP, have to be done with HuRUpdater, during installation the TWRP is replaced by stock recovery, then is your decision keep it or not.
About lock bootloader, mine is unlocked since day one and every time that I install new firmware it keep it unlocked. My experience so far is installing ANE-LX1 firmware in my ANE-LX1 device, probably with other firmware like ANE-AL00 or ANE-TL00 it can be different.
Click to expand...
Click to collapse
ANE LX3 no funciona asi,
Mannuok said:
ANE LX3 no funciona asi,
Click to expand...
Click to collapse
what do you mean by that?
kilroystyx said:
Maybe this thread somehow can helps you:
https://forum.xda-developers.com/huawei-p20-lite/help/req-stock-recovery-p20-lite-t3803027
Don't need lock bootloader to install or receive via OTA official updates.
Lock the bootloader is not possible (maybe it is, but is a pay service).
You can relock instead of lock, but don't do it if your device is not completely stock.
Click to expand...
Click to collapse
Hi all,
Getting a "lock" state is possible indeed. I believe you @kilroystyx had seen it as well on @Merlin_99 's thread:
https://forum.xda-developers.com/huawei-p20-lite/how-to/root-how-to-install-update-t3841557
This will erase all data, except from sdcards of course
Cheers,
AS
Mannuok said:
ANE LX3 no funciona asi,
Click to expand...
Click to collapse
ars_chelsea said:
Hi all,
Getting a "lock" state is possible indeed. I believe you @kilroystyx had seen it as well on @Merlin_99 's thread:
https://forum.xda-developers.com/huawei-p20-lite/how-to/root-how-to-install-update-t3841557
This will erase all data, except from sdcards of course
Cheers,
AS
Click to expand...
Click to collapse
You are right, first post was on the August 20th, at that time I didn't knew that was possible lock bootloader, only after Merlin_99 create that thread on September 12th.
I'm trying to root my Pixel 3 and my device is stuck on the white google loading screen after flashing the patched boot file.
Here is what I've done so far:
Downloaded the boot image -> Installed Magisk on my phone -> patched the boot image -> booted into Fastboot -> flashed the patched boot image -> then my phone restarted and has been stuck on the white google loading screen.
If I hold the volume down button and the power button, my screen goes to the Fastboot mode. Then if I try to power off and start the phone, I get back to the white google loading screen which doesn't change.
Heres the logs from terminal if that provides any info:
(base) [email protected] android % ./fastboot flash boot magisk_patched.img
Sending 'boot_b' (31860 KB) OKAY [ 0.310s]
Writing 'boot_b' OKAY [ 0.258s]
Finished. Total time: 0.837s
(base) [email protected] android % ./fastboot reboot
Rebooting OKAY [ 0.080s]
Finished. Total time: 0.080s
Anyone have any ideas? everything was going smoothly until this point so not sure what I've done wrong. Any help is appreciated, thanks!
@MHuncho
Looks like the boot-loader got broken. Not unusal when flashing a system-less framework as Magisk. Probably dm-verity was enabled when you flashed Magisk's boot.img.
My advice: Try to re-flash Stock ROM.
jwoegerbauer said:
@MHuncho
Looks like the boot-loader got broken. Not unusal when flashing a system-less framework as Magisk.
Try to re-flash Stock ROM.
Click to expand...
Click to collapse
Thanks for the reply but slight issue. I got impatient and tried another solution which was:
(base) [email protected] android % ./fastboot flash boot --slot all magisk_patched.img
Sending 'boot_a' (31860 KB) OKAY [ 0.310s]
Writing 'boot_a' OKAY [ 0.494s]
Sending 'boot_b' (31860 KB) OKAY [ 0.200s]
Writing 'boot_b' OKAY [ 0.192s]
Finished. Total time: 1.760s
Now my device is stuck in a loop on the Fastboot Mode screen with following info:
Device state: unlocked
Boot slot: a
Enter Reason is: "no valid slot to boot'.
Also my device is now NOT recognised by my laptop so I'm unable to re-flash stock ROM as you suggested or do anything. sigh... I shouldn't have rushed.
@MHuncho
Congrats ... This is the price that people who think they must put up a better (?) ROM than that what gets pre-installed by OEM/Carrier - in their R&D department there are certainly no idiots sitting around - pay.
jwoegerbauer said:
@MHuncho
Congrats ... This is the price that people who think they must put up a better (?) ROM than that what gets pre-installed by OEM/Carrier - in their R&D department there are certainly no idiots sitting around - pay.
Click to expand...
Click to collapse
@jwoegerbauer
Slight success, after restarting my laptop, my device is now recognised but my devices is not found when I do ./adb devices and it is found when I do ./fastboot devices. Hence I'm unable to do the command ./adb reboot Bootloader and start the flashing stock ROM. I get the following when I do ./adb reboot Bootloader
(base) [email protected] android % ./adb reboot bootloader
error: no devices/emulators found
From research this may be because USB Debugging is not enabled? which I can't do because my device is stuck in fastboot.. ahh pls help
MHuncho said:
@jwoegerbauer
Slight success, after restarting my laptop, my device is now recognised but my devices is not found when I do ./adb devices and it is found when I do ./fastboot devices. Hence I'm unable to do the command ./adb reboot Bootloader and start the flashing stock ROM. I get the following when I do ./adb reboot Bootloader
(base) [email protected] android % ./adb reboot bootloader
error: no devices/emulators found
From research this may be because USB Debugging is not enabled? which I can't do because my device is stuck in fastboot.. ahh pls help
Click to expand...
Click to collapse
Hold power and volume down buttons to get to fastboot.
Tulsadiver said:
Hold power and volume down buttons to get to fastboot.
Click to expand...
Click to collapse
I'm already in fastboot, thats the only thing I can get to regardless of what I do the phone. Either completed off, or in fastboot
apparently I dont need ./adb to flash the factory image so I'll try just using fastboot
MHuncho said:
I'm already in fastboot, thats the only thing I can get to regardless of what I do the phone. Either completed off, or in fastboot
apparently I dont need ./adb to flash the factory image so I'll try just using fastboot
Click to expand...
Click to collapse
Unzip factory image zip and double click flash-all.bat. edit the flash-all.bat by taking off the -w if you don't want to delete data.
Tulsadiver said:
Unzip factory image zip and double click flash-all.bat. edit the flash-all.bat by taking off the -w if you don't want to delete data.
Click to expand...
Click to collapse
Would this work if I'm on a Mac? as its a bat file
MHuncho said:
Would this work if I'm on a Mac? as its a bat file
Click to expand...
Click to collapse
You should use the .sh file.
Tulsadiver said:
You should use the .sh file.
Click to expand...
Click to collapse
wooohoooo finally restored to factory image. I didn't use the .sh file as it was opening in notepad but got it working through terminal! thanks a lot!
I still want to root the phone again so how what would I need to change from my original post in this thread? as said @jwoegerbauer "better (?) ROM than that what gets pre-installed by OEM/Carrier" . does that mean I downloaded and patched the wrong boot image? hence why my phone was stuck in the white google loading screen for 1hour+?
MHuncho said:
wooohoooo finally restored to factory image. I didn't use the .sh file as it was opening in notepad but got it working through terminal! thanks a lot!
I still want to root the phone again so how what would I need to change from my original post in this thread? as said @jwoegerbauer "better (?) ROM than that what gets pre-installed by OEM/Carrier" . does that mean I downloaded and patched the wrong boot image? hence why my phone was stuck in the white google loading screen for 1hour+?
Click to expand...
Click to collapse
I believe that he was inferring that you are rooting in order to run a custom ROM and that maybe you should have stayed stock.
I don't know where you got your boot image but if you will unzip the image zip that was inside your firmware where you found the flash-all zips you should find the correct boot image to use. First you should enable developer settings and enable USB debugging so you can use USB. What you did sounded correct.
And yeah, despite the fact that I'm flashing phones since a long time,
I've tried to flash my Pxl6 to the November factory image with adb and fastboot coming from a 2 years old tools pack (adb, fastboot)
- unlock bootloader
- flash recovery image was done
- fastboot reboot ok
- flash radio was done
- fastboot reboot failed
- fastboot reboot restarted
- flash system image fails every time I try trough command line or online with Android Flash Tool (whetever wiping option I choose with the online tool)
when the process reboots to Fasbootd
Code:
Writing 'vendor_boot_a' OKAY [ 0.079s]
extracting super_empty.img (0 MB) to disk... took 0.001s
Rebooting into fastboot OKAY [ 0.000s]
< waiting for any device >
fastboot: error: Failed to boot into userspace fastboot; one or more components might be unbootable.
or
Code:
Writing 'vendor_boot_a' OKAY [ 0.112s]
extracting super_empty.img (0 MB) to disk... took 0.000s
Rebooting into fastboot OKAY [ 0.000s]
< waiting for any device >
Sending 'super' (4 KB) FAILED (Status read failed (Too many links))
fastboot: error: Command failed
the update process fails despite that fasbootd initiates and appears.
When trying to boot fastboot manually with the device, it's difficult to make it appear but possible.
Bootlooping on starting the OS otherwise.
I've updated to the latest commandline tools from Google but the issue remains.
The driver works ok, the usb cable allows flashing the recovery and the radio, so should not be the issue.
SDK is not installed on the PC.
I'm blocked, can someone help me to even reinstall the december or whatever version ?
I fear it's bricked this time
cAnArdtichAud said:
And yeah, despite the fact that I'm flashing phones since a long time,
I've tried to flash my Pxl6 to the November factory image with adb and fastboot coming from a 2 years old tools pack (adb, fastboot)
- unlock bootloader
- flash recovery image was done
- fastboot reboot ok
- flash radio was done
- fastboot reboot failed
- fastboot reboot restarted
- flash system image fails every time I try trough command line or online with Android Flash Tool (whetever wiping option I choose with the online tool)
when the process reboots to Fasbootd
Code:
Writing 'vendor_boot_a' OKAY [ 0.079s]
extracting super_empty.img (0 MB) to disk... took 0.001s
Rebooting into fastboot OKAY [ 0.000s]
< waiting for any device >
fastboot: error: Failed to boot into userspace fastboot; one or more components might be unbootable.
or
Code:
Writing 'vendor_boot_a' OKAY [ 0.112s]
extracting super_empty.img (0 MB) to disk... took 0.000s
Rebooting into fastboot OKAY [ 0.000s]
< waiting for any device >
Sending 'super' (4 KB) FAILED (Status read failed (Too many links))
fastboot: error: Command failed
the update process fails despite that fasbootd initiates and appears.
When trying to boot fastboot manually with the device, it's difficult to make it appear but possible.
Bootlooping on starting the OS otherwise.
I've updated to the latest commandline tools from Google but the issue remains.
The driver works ok, the usb cable allows flashing the recovery and the radio, so should not be the issue.
SDK is not installed on the PC.
I'm blocked, can someone help me to even reinstall the december or whatever version ?
I fear it's bricked this time
Click to expand...
Click to collapse
You definitely have to wipe to go back. Did you remove the -w from the install bat file?
You should update your platform tools and you'll need to format data to go back to the November factory image.
Tulsadiver said:
You definitely have to wipe to go back. Did you remove the -w from the install bat file?
Click to expand...
Click to collapse
Uh no, it was the 1st time I was trying to use directly the flash-all script, so no I used the fastboot -w parameter.
Later I tried the flash online tool from Google and I ticked wipe.
Yeah sorry that's not the exact code I used, so yes..w was used.
What are my options? Fastbootd seem broken because flashing fails when rebooting to fastbootd.
Edmontonchef said:
You should update your platform tools and you'll need to format data to go back to the November factory image.
Click to expand...
Click to collapse
Yeah thanks I updated them after I had the issue and retried without working.
cAnArdtichAud said:
Uh no, it was the 1st time I was trying to use directly the flash-all script, so no I used the fastboot -w parameter.
Later I tried the flash online tool from Google and I ticked wipe.
Yeah sorry that's not the exact code I used, so yes..w was used.
What are my options? Fastbootd seem broken because flashing fails when rebooting to fastbootd.
Click to expand...
Click to collapse
Perhaps you didn't get a good download of your firmware. Try downloading it again.
Edit: usual things, try a different usb port on your pc, try a different pc, use a different cable. Check version. fastboot -- version
Tulsadiver said:
Perhaps you didn't get a good download of your firmware. Try downloading it again.
Edit: usual things, try a different usb port on your pc, try a different pc, use a different cable. Check version. fastboot -- version
Click to expand...
Click to collapse
This. Make sure you're using the latest Platform Tools - current version is 31.0.3, Aug '21.
I am going to take a wild guess that the reason for the rollback. Is because of the data issues.
If so,
Just flash the November radio image on top of the December update.
"Fastboot flash radio radio.img"
The above is what I did. And it has worked well for me.
vandyman said:
I am going to take a wild guess that the reason for the rollback. Is because of the data issues.
If so,
Just flash the November radio image on top of the December update.
"Fastboot flash radio radio.img"
The above is what I did. And it has worked well for me.
Click to expand...
Click to collapse
Yeah but I've already flashed back recovery and radio the OS part is failing
V0latyle said:
This. Make sure you're using the latest Platform Tools - current version is 31.0.3, Aug '21.
Click to expand...
Click to collapse
thx. I tried several images but will retry on another port, another cable same PC (only one...)
I have 31.03 command tools
funkin' love you guys: ensuring I was on a powered usb port, changing cable made me flash the data/os files
funkin' pixel 6 reverted back to the entire previous rom
funkin Xmas to you guys , #heartWithFingers!
vandyman said:
I am going to take a wild guess that the reason for the rollback. Is because of the data issues.
If so,
Just flash the November radio image on top of the December update.
"Fastboot flash radio radio.img"
The above is what I did. And it has worked well for me.
Click to expand...
Click to collapse
I have the Dec update on my P6 unlocked on Verizon but would like to revert back to the Nov one without doing a complete wipe of my phone. Is this what you did?
sniff1 said:
I have the Dec update on my P6 unlocked on Verizon but would like to revert back to the Nov one without doing a complete wipe of my phone. Is this what you did?
Click to expand...
Click to collapse
You can't go back without a full wipe.
Tulsadiver said:
You can't go back without a full wipe.
Click to expand...
Click to collapse
Because when you unlock the bootloader prior to flashing, the phone is wiped.
cAnArdtichAud said:
Because when you unlock the bootloader prior to flashing, the phone is wiped.
Click to expand...
Click to collapse
Even if your bootloader is already unlocked.
sniff1 said:
I have the Dec update on my P6 unlocked on Verizon but would like to revert back to the Nov one without doing a complete wipe of my phone. Is this what you did?
Click to expand...
Click to collapse
No. I have the Dec. 15th update and the mid November radio.
If you would like to install the older radios. You will need to download the older factory image and extract the radio image.
Than flash the older radio image with fastboot on your PC.
You need to have the USB devloper checked to use adb/fastboot on your PC.
vandyman said:
No. I have the Dec. 15th update and the mid November radio.
If you would like to install the older radios. You will need to download the older factory image and extract the radio image.
Than flash the older radio image with fastboot on your PC.
You need to have the USB devloper checked to use adb/fastboot on your PC.
Click to expand...
Click to collapse
That is just the radio.....not the system.
vandyman said:
No. I have the Dec. 15th update and the mid November radio.
If you would like to install the older radios. You will need to download the older factory image and extract the radio image.
Than flash the older radio image with fastboot on your PC.
You need to have the USB devloper checked to use adb/fastboot on your PC.
Click to expand...
Click to collapse
This is exactly what I want to do. I know how to extract the radio image, but not too certain on the fastboot commands to do it
Tulsadiver said:
That is just the radio.....not the system.
Click to expand...
Click to collapse
Yes ,just the radio image from November on top of the complete December image.
What I did;
Flash-all (December factory image with the -w removed for no data wipe)
Next, I extracted the November radio image from the November factory image.
Than , fastboot flash radio radio.img.
I know it sounds confusing. Lol..
sniff1 said:
This is exactly what I want to do. I know how to extract the radio image, but not too certain on the fastboot commands to do it
Click to expand...
Click to collapse
Fastboot flash radio yourradio.img
Yes the radio command needs to be there after the flash command and before your radio.img.
Very similar to to flashing a boot image,
Example, fastboot flash boot boot.img
Every time I wanna flash Rom files with fastboot or adb side load
System partition failed to flash
even I have tried fastboot enhanced tool but it states all .img file is not logical even .img for stock rom.
Before using MSM tool I haven't faced this kinds of problems but once my device stuck in qualcom crush dump mode and I have to use MSM tool to unbrick my device and after that I think my partition type have changed and I can not flash any kind of rom. Every time I got the following error:
Invalid sparse file format at header magic
Sending sparse 'system_b' 1/5 (773795 KB) OKAY [ 17.926s]
Writing 'system_b' FAILED (remote: 'Partition not found')
fastboot: error: Command failed
Invalid sparse file format at header magic
My bootloader is unlocked
I have searched a lot and didn't got any solution and there are many users they are also facing the same problem but didn't got any solutions.
Does anyone know how to fix this problem?
Use adb reboot fastboot instead of adb reboot bootloader
御坂19041号 said:
Use adb reboot fastboot instead of adb reboot bootloader
Click to expand...
Click to collapse
Fastboot working fine here no issue with fastboot.
nowshadalve1 said:
Every time I wanna flash Rom files with fastboot or adb side load
System partition failed to flash
even I have tried fastboot enhanced tool but it states all .img file is not logical even .img for stock rom.
Before using MSM tool I haven't faced this kinds of problems but once my device stuck in qualcom crush dump mode and I have to use MSM tool to unbrick my device and after that I think my partition type have changed and I can not flash any kind of rom. Every time I got the following error:
Invalid sparse file format at header magic
Sending sparse 'system_b' 1/5 (773795 KB) OKAY [ 17.926s]
Writing 'system_b' FAILED (remote: 'Partition not found')
fastboot: error: Command failed
Invalid sparse file format at header magic
My bootloader is unlocked
I have searched a lot and didn't got any solution and there are many users they are also facing the same problem but didn't got any solutions.
Does anyone know how to fix this problem?
Click to expand...
Click to collapse
maybe on the wrong version or wrong recovery
dfm000 said:
maybe on the wrong version or wrong recovery
Click to expand...
Click to collapse
I have tried to flash fastboot stock rom also.....
Everytime says partition not found or volume full.
Look at the screenshot
nowshadalve1 said:
I have tried to flash fastboot stock rom also.....
Everytime says partition not found or volume full.
Click to expand...
Click to collapse
which oxygen os version you are on
dfm000 said:
which oxygen os version you are on
Click to expand...
Click to collapse
It's oos 11.2.7.7
After using MSM tool this problem appears before I can flash custom rom without any issue.
nowshadalve1 said:
It's oos 11.2.7.7
After using MSM tool this problem appears before I can flash custom rom withoutwh
Click to expand...
Click to collapse
which rom you trying to install
nowshadalve1 said:
It's oos 11.2.7.7
After using MSM tool this problem appears before I can flash custom rom without any issue.
Click to expand...
Click to collapse
use msm tool again to start fresh. update to version 11.2.8.8 from settings after that. use the recovery included with the rom provider. all should work well
dfm000 said:
use msm tool again to start fresh. update to version 11.2.8.8 from settings after that. use the recovery included with the rom provider. all should work well
Click to expand...
Click to collapse
I have tried this process so many times but still not working.
I can't fastboot any system Img any fix?
Every time I wanna flash Rom img files with fastboot System partition failed to flash Invalid sparse file format at header magic Sending sparse 'system_b' 1/5 (773795 KB) OKAY [ 17.926s] Writing 'system_b' FAILED (remote: 'Partition not...
forum.xda-developers.com
Check the link he also facing same problem...
nowshadalve1 said:
I have tried this process so many times but still not working.
I can't fastboot any system Img any fix?
Every time I wanna flash Rom img files with fastboot System partition failed to flash Invalid sparse file format at header magic Sending sparse 'system_b' 1/5 (773795 KB) OKAY [ 17.926s] Writing 'system_b' FAILED (remote: 'Partition not...
forum.xda-developers.com
Check the link he also facing same problem...
Click to expand...
Click to collapse
https://t.me/OnePlus9ROfficial ask here
Finally I got the solution :
1. update the oos to 11.2.8.8 from system updater.
2. Then unlock the bootloader. -> fastboot flashing unlock
3. Then flash custom recovery -> fastboot flash recovery recovery.img
4.Then enable adb sideload.
5. Then flash rom using-> adb sideload rom.zip
( After 47% it will show an error msg but don't worry)
6. Then back to recovery and formate user data.(most important otherwise you will stuck in bootloop and have to use msm tool)
7. Then reboot to system.
Done.
Who will face this problem on future follow the steps.
Thanks to https://t.me/OnePlus9ROfficial
And also thanks you bro @dfm000
im unable to enter fastboot mode after updating to OOS 12... anyone facing this issue?
gohaaron said:
im unable to enter fastboot mode after updating to OOS 12... anyone facing this issue?
Click to expand...
Click to collapse
Yes I was facing this issue also...you have to rollback to oos 11.
nowshadalve1 said:
Yes I was facing this issue also...you have to rollback to oos 11.
Click to expand...
Click to collapse
i have... so r u saying i need to root from OOS 11? my phone got bricked just now i had to use Msmtool to reflash back to OOS 11... but ive updated back to 12
Yes currently you need to root from oos 11. I don't weather you can root your device from oos 12 or not.
Ask here: https://t.me/OnePlus9ROfficial
And using MSM tool there is no big deal with Android 12. You will flash your device in edl mode so everything will be fine.
nowshadalve1 said:
Yes currently you need to root from oos 11. I don't weather you can root your device from oos 12 or not.
Ask here: https://t.me/OnePlus9ROfficial
And using MSM tool there is no big deal with Android 12. You will flash your device in edl mode so everything will be fine.
Click to expand...
Click to collapse
ok ive joined thanks
gohaaron said:
ok ive joined thanks
Click to expand...
Click to collapse
If you wanna rollback from 12 to 11 can follow this article:
Steps to Downgrade or Rollback Oneplus 8, 8 pro, 8T & 9R from Stable OxygenOS 12 to OxygenOS 11
Oneplus user are not happy about changes done on OxygenOS 12 for Oneplus 8, 8 pro, 8T & 9R. Now users want to downgrade to Stable.
techibee.in
nowshadalve1 said:
If you wanna rollback from 12 to 11 can follow this article:
Steps to Downgrade or Rollback Oneplus 8, 8 pro, 8T & 9R from Stable OxygenOS 12 to OxygenOS 11
Oneplus user are not happy about changes done on OxygenOS 12 for Oneplus 8, 8 pro, 8T & 9R. Now users want to downgrade to Stable.
techibee.in
Click to expand...
Click to collapse
yes i follow him too... but i saw him enter fastboot with OOS 12