Related
Here's what I've learned far about the E6:
Mostly from Treble Info app from Hackintosh Five
VNDK-28
Arm32 BINDER64
It's actually AB, according to it having System As Root.
No Seamless upgrade.
Binder64-AB/A64-AB GSIs work on this device.
Quack GSI should be the first we focus on.
TO INSTALL:
Code:
fastboot -w flash system <gsiname.img>
BOOTS
Quack GSI (AOSP 10, bb)!
Will list others as I come across them.
This is awesome.
I got LOS 16 bvn to boot.
The ril must be off or something, it had no connection.
I've got stock rom with encryption disabled and verity disabled, full magisk root living inside the boot.img..
And got twrp with touch adb and mtp working...
But it looks a lil funny cause the port has slightly smaller image so it doesn't fully fill screen.
But everything seems to work, including flashing zips..
Should that be a thread by its self?
LgPWN'd said:
This is awesome.
I got LOS 16 bvn to boot.
The ril must be off or something, it had no connection.
I've got stock rom with encryption disabled and verity disabled, full magisk root living inside the boot.img..
And got twrp with touch adb and mtp working...
But it looks a lil funny cause the port has slightly smaller image so it doesn't fully fill screen.
But everything seems to work, including flashing zips..
Should that be a thread by its self?
Click to expand...
Click to collapse
Yes, please! it's very nice that u did that, I'll link it in the main post when u do
For a working recovery see this
https://forum.xda-developers.com/moto-e6/development/development-team-looking-testors-t4120171
tried:
>fastboot flash system <image.img>
for all the 3 Quack GSI: system-quack-arm32_binder64-ab-gapps.img.xz, system-quack-arm32_binder64-ab-go.img.xz and system-quack-arm32_binder64-ab-vanilla.img.xz
The system just keeps looping the andriod logo...
Anyone knows of a twrp version that works with this moto e6?
soulmaker2207 Did you do the -w in fastboot after you installed the gsi? If you didn't it is definitely worth a try Beware it will erase all data including the internal sd
soulmaker2207 said:
tried:
>fastboot flash system <image.img>
for all the 3 Quack GSI: system-quack-arm32_binder64-ab-gapps.img.xz, system-quack-arm32_binder64-ab-go.img.xz and system-quack-arm32_binder64-ab-vanilla.img.xz
The system just keeps looping the andriod logo...
Anyone knows of a twrp version that works with this moto e6?
Click to expand...
Click to collapse
Alongside the fastboot -w advice, try renaming every img you download to "system.img." I have had way more success doing that than using long img names.
Also, I noticed that for a lot of GSIs, USB Tethering does not work.
Just installed latest phusson aosp android 11 gsi, over latest stock pie, using fastboot -w option, of course. Boots great, working VoLTE, sms, etc. Super fast performance. Usb tethering greyed out. That's the only problem I sound so far.
scottyrick2 said:
Just installed latest phusson aosp android 11 gsi, over latest stock pie, using fastboot -w option, of course. Boots great, working VoLTE, sms, etc. Super fast performance. Usb tethering greyed out. That's the only problem I sound so far.
Click to expand...
Click to collapse
Yeah USB Tethering doesn't seem to work for ANY GSI ROMs.
I am running Android 11 AOSP now using phhusson gsi rom V300.l. For your phone calling and sms to work properly, you need to follow this guide every time you reboot or power off/on. I mean every time.
[Razer Phone 2/as of v300.l/non-Verizon] IMS still needs some manual intervention to re-enable after reboot. · Issue #1681 · phhusson/treble_experimentations · GitHub
I have done this often enough now that I can do it in under 30 seconds. Hopefully, this issue will be fixed soon, but it is not that difficult to fix yourself.
scottyrick2 said:
I am running Android 11 AOSP now using phhusson gsi rom V300.l. For your phone calling and sms to work properly, you need to follow this guide every time you reboot or power off/on. I mean every time.
[Razer Phone 2/as of v300.l/non-Verizon] IMS still needs some manual intervention to re-enable after reboot. · Issue #1681 · phhusson/treble_experimentations · GitHub
I have done this often enough now that I can do it in under 30 seconds. Hopefully, this issue will be fixed soon, but it is not that difficult to fix yourself.
Click to expand...
Click to collapse
How odd. I can't get any Android 11 GSI to work on my E6
Are you trying to update from Android 10? I don't think you can.
scottyrick2 said:
Are you trying to update from Android 10? I don't think you can.
Click to expand...
Click to collapse
Yes I was trying to update from Android 10
I am running phhusson aosp 11 v300.l gsi rom right now. Super fast. Amazing, really.
If you are on the T-Mobile system, you need to do 3 things in order to make VoLTE and sms work properly. Hopefully, this will not be needed in future updates, but it might be.
1. using a root file explorer (I use 3C) to locate and move the org.codeaurora.ims folder from /data/app to /system/app
2. reboot
3. using *#*#4636*#*# on the dialer to open "phone information menu", change the band to GMS/WCDMA/LTE, and close the menu.
That's it. I hope this helps you to consider moving up to gsi roms. They are truly amazing.
Greetings people and like minded friends of the internet (and fellow trashman) I come bearing great gifts of flashing goodness. For the XT2005-5, I needed a nice de-Googled imaged phone for usage. As most of you probably have found in searching, finding TWRP and getting it to work has been a tedious journey. Never fear, there is a way to drop images on this phone. I will give you my experience and steps I took, in hopes it may help you save a bit of time.
1.) Download the factory image for the device found here
https://mirrors.lolinet.com/firmware/motorola/surfna/official/RETUS/ I used this one https://mirrors.lolinet.com/firmwar...-DEFAULT_regulatory-XT2005-5-SKU6_CFC.xml.zip Use a program like 7-Zip to extract it to a folder of your liking and you will use this folder later in the process. Of course, you're welcome to stop here and just flash the factory image and be done. But after all, why would you be reading this post if you wanted to just stop here, right?!
2.) Now find a GSI system image of your liking for flashing to the phone. I used the following system image from PHH (KUDOS FOR THE MAN WHO ROCKS GREAT ANDROID SKILLS) https://github.com/phhusson/treble_experimentations/releases For this phone you can you ARM32/Binder64/AB and I decided to go with
system-roar-arm32_binder64-ab-vndklite-vanilla.img.xz as I wanted no GAPPS. You will need to use 7-Zip again to extract the image from the archive file you've download. You can extract this file anywhere for the time being.
3.) Rename the extracted image from step 2 to system.img (just for simplicity) and put the file in the same directory you've created from step1.
4.) Now create a flashfile2.bat with the following and put this .bat file in the same directory as Step1
echo off
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 flash dsp adspso.bin
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash dtbo dtbo.img
fastboot flash system system.img
fastboot flash recovery recovery.img
fastboot flash vendor vendor.img
fastboot flash oem oem.img
fastboot erase modemst1
fastboot erase modemst2
fastboot erase userdata
fastboot erase cache
fastboot erase DDR
fastboot flash fsg fsg.mbn
fastboot oem fb_mode_clear
echo -------------------------------------------------------------------------
echo please scroll up and check your flash for any errors
echo -------------------------------------------------------------------------
pause
fastboot reboot
exit
5.) You will notice that I modified the .bat to flash the system.img that was downloaded in Step 2. Keep in mind, this method will re-write your system and you will LOSE ALL OF YOUR DATA so ensure you have YOUR DATA BACKED UP.
Run the flashfile2.bat file after you've connected your USB cable and you're at the bootloader screen
You already unlocked the bootloader, right? Hopefully, you're at least to BL screen, right after you've researched a bit about your phone .
b00ster23 said:
Greetings people and like minded friends of the internet (and fellow trashman) I come bearing great gifts of flashing goodness. For the XT2005-5, I needed a nice de-Googled imaged phone for usage. As most of you probably have found in searching, finding TWRP and getting it to work has been a tedious journey. Never fear, there is a way to drop images on this phone. I will give you my experience and steps I took, in hopes it may help you save a bit of time.
1.) Download the factory image for the device found here
https://mirrors.lolinet.com/firmware/motorola/surfna/official/RETUS/ I used this one https://mirrors.lolinet.com/firmwar...-DEFAULT_regulatory-XT2005-5-SKU6_CFC.xml.zip Use a program like 7-Zip to extract it to a folder of your liking and you will use this folder later in the process. Of course, you're welcome to stop here and just flash the factory image and be done. But after all, why would you be reading this post if you wanted to just stop here, right?!
2.) Now find a GSI system image of your liking for flashing to the phone. I used the following system image from PHH (KUDOS FOR THE MAN WHO ROCKS GREAT ANDROID SKILLS) https://github.com/phhusson/treble_experimentations/releases For this phone you can you ARM32/Binder64/AB and I decided to go with
system-roar-arm32_binder64-ab-vndklite-vanilla.img.xz as I wanted no GAPPS. You will need to use 7-Zip again to extract the image from the archive file you've download. You can extract this file anywhere for the time being.
3.) Rename the extracted image from step 2 to system.img (just for simplicity) and put the file in the same directory you've created from step1.
4.) Now create a flashfile.bat with the following and put this file in the same directory as Step1
echo off
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 flash dsp adspso.bin
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash dtbo dtbo.img
fastboot flash system system.img
fastboot flash recovery recovery.img
fastboot flash vendor vendor.img
fastboot flash oem oem.img
fastboot erase modemst1
fastboot erase modemst2
fastboot erase userdata
fastboot erase cache
fastboot erase DDR
fastboot flash fsg fsg.mbn
fastboot oem fb_mode_clear
echo -------------------------------------------------------------------------
echo please scroll up and check your flash for any errors
echo -------------------------------------------------------------------------
pause
fastboot reboot
exit
5.) You will notice that I modified the .bat to flash the system.img that was downloaded in Step 2. Keep in mind, this method will re-write your system and you will LOSE ALL OF YOUR DATA so ensure you have YOUR DATA BACKED UP.
Run the .bat file after you've connected your USB cable and you're at the bootloader screen
You already unlocked the bootloader, right? Hopefully, you're at least to BL screen, right after you've researched a bit about your phone .
Click to expand...
Click to collapse
ARM32/Binder64/AB = a64 a/b OR potentially a64bvN/a64bvS
Something to make it easier on others.
There was a link for TWRP on this post but had to remove it because the link is dead. I'll explore other options before re-updating this post
koyo said:
Some things to add to this post to make it easier
1) ARM32/Binder64/AB = a64 a/b OR potentially a64bvN/a64bvS
2) I prefer doing it via this method rather than flashing stock files: - E6 AIO ToolKit Mod Release- | XDA Developers Forums (xda-developers.com)
This has a TWRP for E6 which allows you to flash things like magisk, universal encryption disabler, gapps, et cetera. Things that might not be built into the native ROM.
Click to expand...
Click to collapse
The links are all broken, and I see no TWRP available.
b00ster23 said:
The links are all broken, and I see no TWRP available.
Click to expand...
Click to collapse
Ugh oops. This is the result of going off of memory from months ago rather than checking to see if everything's up to date.
The developers that made that TWRP have an OrangeFox recovery to download on their telegram
Telegram: Contact @android_general_chat
t.me
koyo said:
Ugh oops. This is the result of going off of memory from months ago rather than checking to see if everything's up to date.
The developers that made that TWRP have an OrangeFox recovery to download on their telegram
Telegram: Contact @android_general_chat
t.me
Click to expand...
Click to collapse
Yeah, I don't see any links to the OrangeFox recovery img... Keep in mind this is for the XT2005-5 variant (SURFNA) unless OrangeFox is universal
b00ster23 said:
Yeah, I don't see any links to the OrangeFox recovery img... Keep in mind this is for the XT2005-5 variant (SURFNA) unless OrangeFox is universal
Click to expand...
Click to collapse
Telegram: Contact @Android_General_Chat
t.me
Android devices can have different designs, so there is no generic command or set of instructions for flashing a GSI to apply to all devices. Specially for Xperias am i writing this Guides for You. So please read carefully...
1. Ensure that You have the following before You start:
Latest Fastboot Version (Or the used fastboot commands may not work)
A Method for disabling Android Verified Boot (Part of the Guide)
An unlocked Bootloader State (Official Instructions HERE)
To Start:
Download the Basic Package from Google: https://developer.android.com/topic/generic-system-image/releases
Download the AOSP Vendor Package from Sony: https://developer.sony.com/develop/open-devices/downloads/software-binaries
Open up the Zip Files and place the 3 included Images on Your fastboot destination
Boot Your Device into Fastboot:
Code:
Turn off Your Device and hold VolumeUP while connecting via USB to a PC or use ADB to reboot to fastboot
Disable the verified booting (AVB) by flashing vbmeta.img:
Code:
fastboot --disable-verification flash vbmeta vbmeta.img
Flash the Vendor to the Primary A Slot OEM:
Code:
fastboot flash oem_a nameofthesonyoemimage.img
Repeat to flash to the B Slot OEM
Code:
fastboot flash oem_b nameofthesonyoemimage.img
Flash the GSI to the Primary A Slot System:
Code:
fastboot flash system_a system.img
Repeat to flash to the B Slot System
Code:
fastboot flash system_b system.img
Wipe the user data and clear the data from other necessary partitions (for example, user data and system partitions):
Code:
fastboot -w
Reboot:
Code:
fastboot reboot
Additional:
You can use any Android 9+ GSI out of the XDA Forum here: https://forum.xda-developers.com/project-treble/trebleenabled-device-development
To get Magisk/Root; just patch Your actual Kernel with the Magisk Manager App and flash the Boot Image together with the GSI (Example below)
Patched Boot Image for Xperia 5 Users: https://forum.xda-developers.com/xp...isk-v20-3-patched-boot-image-android-t4033547
Hi,
A few things
Why flash all on both slots? Not needed
Why flash OEM? Not needed, android 10 GSI work with stock vendor.
niaboc79 said:
Hi,
A few things
Why flash all on both slots? Not needed
Why flash OEM? Not needed, android 10 GSI work with stock vendor.
Click to expand...
Click to collapse
After testing with Magisk have i faced that A only flashing ends up in softbricked devices since it can't boot into the second Slot. Fastboot will tell You what it does flash over the output. You can also erase one slot without touching the other like that. there are A Only ROMs that can be used like that but in case of A/B ROMs should we flash to both Slots.
Flashing the AOSP Vendor prepares the device for all Kinds of GSIs. In case of people like me who have just a Linux PC to use, will it be helpful to be also able to run AOSP from Scratch. Just My 2 Cents after using different machines and devices ofter the time... The AOSP Vendor does also not have any disadvantages in any view on GSIs and NewFlasher will flash stock fully anyways and reverts that if wanted.
BR
Miustone said:
After testing with Magisk have i faced that A only flashing ends up in softbricked devices since it can't boot into the second Slot. Fastboot will tell You what it does flash over the output. You can also erase one slot without touching the other like that. there are A Only ROMs that can be used like that but in case of A/B ROMs should we flash to both Slots.
Flashing the AOSP Vendor prepares the device for all Kinds of GSIs. In case of people like me who have just a Linux PC to use, will it be helpful to be also able to run AOSP from Scratch. Just My 2 Cents after using different machines and devices ofter the time... The AOSP Vendor does also not have any disadvantages in any view on GSIs and NewFlasher will flash stock fully anyways and reverts that if wanted.
BR
Click to expand...
Click to collapse
Sure but stock vendor give better results with wireless charging and fingerprint.
Thanks for your the explanations ?
niaboc79 said:
Sure but stock vendor give better results with wireless charging and fingerprint.
Thanks for your the explanations
Click to expand...
Click to collapse
Nice to know! Fingerprints are the worst on Xperia 1 and 5. Hope it will be better on the Mark 2...
Just made an Overlay over Night for GSIs, after experimenting around with them again. Finally got some essential Features working like AoD. Still missing is VoLTE and wifi calling which is a common Android 10 GSI bug i think. Double Touch to work does also not work on My Xperia 5 (Dunno why).
Thread; https://forum.xda-developers.com/xp...eriment-mars-vendor-overlay-gsi-roms-t4128449
which AOSP Vendor Package from Sony can be use on xperia 1 ii
I was wondering, is this device Xperia 1ii is able to recieved GSI 13?
I have the previous model Xperia 1 running GSI 13 really well, and was wondering if this device is similar to do the same?
Kind of a dumb question, because I would assume yes?... But would like to know just the same, as I saw a bargain price for a new Xperia 1ii, and hoping it to be similar.
So I have tried to flash a GSI on my Nord N100 and while it boots the phone gets stuck at the boot animation for a good long while. The steps I have taken to flash the GSI were to oem unlock the phone, boot into the bootloader,fastboot reboot fastboot, flash the gsi system image,flash the stock vbmeta image, flash the stock vbmeta system image I also have and then finally rebooting the device after using the fastboot -w command. Did I maybe do something wrong in the steps I took or use a wrong file?
Hi, I think you have to disable AVB, not try to use vbmeta from stock
Here are instructions from Oneplus Nord, you can try again with those vbmeta files
How to: Run an GSI on NORD
To run an GSI on your Nord: Unlock bootloader Toogle oem unlock in Developer options Reboot to fastboot (turn of phone, press volume down and start) Run -fastboot oem unlock Install GSI (check...
forum.xda-developers.com
Wouldn’t using vbmeta files made for a different phone mess up my phone?
svaethier said:
Wouldn’t using vbmeta files made for a different phone mess up my phone?
Click to expand...
Click to collapse
I'd guess it's an empty image created as described here: https://wiki.postmarketos.org/wiki/Android_Verified_Boot_(AVB) section disable verrified boot. And an empty image should be universal I would think
well i tried using that vbmeta file and the phone still gets stuck at the boot animation so maybe it's not the vbmeta file that's not working
Someone came out with TWRP for the 5 here: https://forum.xda-developers.com/t/...mwin-recovery-project-redfin-testing.4240711/
I tried booting it on the 5g, and it loaded but touch controls not working and adb not working;. The phones share kernels. I'm guessing it wouldn't be too hard to adapt it to the 5g. Would be amazing!
mistermojorizin said:
Someone came out with TWRP for the 5 here: https://forum.xda-developers.com/t/...mwin-recovery-project-redfin-testing.4240711/
I tried booting it on the 5g, and it loaded but touch controls not working and adb not working;. The phones share kernels. I'm guessing it wouldn't be too hard to adapt it to the 5g. Would be amazing!
Click to expand...
Click to collapse
I imagine this will be ported to our device once the P5 version is working properly. It's still in "testing" according to @bigbiff. I'd just be patient for that since he's been working on it since I had my Pixel 3 XL. Lots of hurdles to overcome unfortunately.
mistermojorizin said:
Someone came out with TWRP for the 5 here: https://forum.xda-developers.com/t/...mwin-recovery-project-redfin-testing.4240711/
I tried booting it on the 5g, and it loaded but touch controls not working and adb not working;. The phones share kernels. I'm guessing it wouldn't be too hard to adapt it to the 5g. Would be amazing!
Click to expand...
Click to collapse
Yes, but it is for Android 10 (Q): TWRP 3.5.0_10-0 -
mistermojorizin said:
Someone came out with TWRP for the 5 here: https://forum.xda-developers.com/t/...mwin-recovery-project-redfin-testing.4240711/
I tried booting it on the 5g, and it loaded but touch controls not working and adb not working;. The phones share kernels. I'm guessing it wouldn't be too hard to adapt it to the 5g. Would be amazing!
Click to expand...
Click to collapse
mistermojorizin said:
Someone came out with TWRP for the 5 here: https://forum.xda-developers.com/t/...mwin-recovery-project-redfin-testing.4240711/
I tried booting it on the 5g, and it loaded but touch controls not working and adb not working;. The phones share kernels. I'm guessing it wouldn't be too hard to adapt it to the 5g. Would be amazing!
Click to expand...
Click to collapse
-Try a GSI 10(Q) in activeslot=a
-reboot-bootloader
-./fastboot --set-active=b
-reboot-bootloader
-./fastboot flash --disable-verity --disable-verification vbmeta vbmeta.img
-reboot-bootloader
-./fastboot -w boot xxx.img
v.garne said:
-Try a GSI 10(Q) in activeslot=a
-reboot-bootloader
-./fastboot --set-active=b
-reboot-bootloader
-./fastboot flash --disable-verity --disable-verification vbmeta vbmeta.img
-reboot-bootloader
-./fastboot -w boot xxx.img
Click to expand...
Click to collapse
welcome to the forum, i notice this is your first post.
what does gsi 10q mean? I know what active slot means
what does flash disable verity and disable verifaction do? also, what is vbmeta and where do I get vbmeta.img?
one the last command, what does the -w do? I know I usually delete all -w as they indicate a data wipe.
for what it's worth, my normal android runs on slot b, don't know if that makes a difference for these specific steps.
rspkt said:
I imagine this will be ported to our device once the P5 version is working properly. It's still in "testing" according to @bigbiff. I'd just be patient for that since he's been working on it since I had my Pixel 3 XL. Lots of hurdles to overcome unfortunately.
Click to expand...
Click to collapse
Sounds like it's already able to make backups on the P5, which is the main function I'm interested in, even if can't decrypt /system yet.
I'd like to help him as much as possible. I posted on his thread and he said he needs dmesg to see what's not working. Any idea how to provide that?
mistermojorizin said:
welcome to the forum, i notice this is your first post.
what does gsi 10q mean? I know what active slot means
what does flash disable verity and disable verifaction do? also, what is vbmeta and where do I get vbmeta.img?
one the last command, what does the -w do? I know I usually delete all -w as they indicate a data wipe.
for what it's worth, my normal android runs on slot b, don't know if that makes a difference for these specific steps.
Click to expand...
Click to collapse
mistermojorizin said:
welcome to the forum, i notice this is your first post.
what does gsi 10q mean? I know what active slot means
what does flash disable verity and disable verifaction do? also, what is vbmeta and where do I get vbmeta.img?
one the last command, what does the -w do? I know I usually delete all -w as they indicate a data wipe.
for what it's worth, my normal https://github.com/phhusson/treble_experimentations/wiki/Generic-System-Image-(GSI)-list runs on slot b, don't know if that makes a difference for these specific steps.
Click to expand...
Click to collapse
Generic system image,
mistermojorizin said:
welcome to the forum, i notice this is your first post.
what does gsi 10q mean? I know what active slot means
what does flash disable verity and disable verifaction do? also, what is vbmeta and where do I get vbmeta.img?
one the last command, what does the -w do? I know I usually delete all -w as they indicate a data wipe.
for what it's worth, my normal android runs on slot b, don't know if that makes a difference for these specific steps.
Click to expand...
Click to collapse
Generic System Image (GSI) list
Notes about tinkering with Android Project Treble. Contribute to phhusson/treble_experimentations development by creating an account on GitHub.
github.com
I was able to get touchscreen working in TWRP by flashing it to the boot partition, then booting the proton kernel installer (which flashes the proton kernel to the boot partition). no ADB though. Can't get the dev a dmesg/catlog, unless someone knows how to get one without ADB from inside TWRP.
v.garne said:
-Try a GSI 10(Q) in activeslot=a
-reboot-bootloader
-./fastboot --set-active=b
-reboot-bootloader
-./fastboot flash --disable-verity --disable-verification vbmeta vbmeta.img
-reboot-bootloader
-./fastboot -w boot xxx.img
Click to expand...
Click to collapse
Is there a GSI 10(Q) available for redfin or bramble? I can't find any.
mistermojorizin said:
I was able to get touchscreen working in TWRP by flashing it to the boot partition, then booting the proton kernel installer (which flashes the proton kernel to the boot partition). no ADB though. Can't get the dev a dmesg/catlog, unless someone knows how to get one without ADB from inside TWRP.
Click to expand...
Click to collapse
I could not mount /data or /storage so I couldn't make a backup.
Master Cylinder said:
Is there a GSI 10(Q) available for redfin or bramble? I can't find any.
I could not mount /data or /storage so I couldn't make a backup.
Click to expand...
Click to collapse
yes, it was mentioned that it doesn't decrypt yet.
We got TWRP now!
[RECOVERY][UNOFFICIAL] - (1/16/22) TeamWin Recovery Project [BRAMBLE]
Essentially copy/paste from the official TWRP for redfin thread, except I've made my own unofficial build for the Pixel 4a5G that in my own testing appears to be on feature parity with the official build for the Pixel 5! There are reports of the...
forum.xda-developers.com
Had an 11.2.3.3 Global rooted via Magisk OP9 Pro that I wanted to update via OTA to 11.2.4.4, which was offered via system update. I used Magisk to restore images before update, did the update, and then went back to install to inactive slot. Rebooted and it was still on 11.2.3.3 so I tried again. Upon trying again, my phone got to a Qualcomm debug/error mode. I experienced this before when on a different boot slot for some other diagnosis of another issue in the past so I switched boot slots.
The other boot slot is stuck in fastboot mode I come to find so I check what it shows if I reverted back to the other boot slot, which was the Qualcomm error. Now instead of a Qualcomm error, it shows language options, one of which is English, and then gives me "boot reason", "wipe data and cache" and "advanced". I believe this is the OnePlus recovery menu, which I have not needed to use before and in the past, used TWRP on other devices.
Can't I just reflash a whole system image for 11.2.4.4 (it'd have to be the European one right now since Global isn't available) via fastboot and it should be fixed, albeit unrooted and I can just re-root? I'd like to try this, but there's no "flash-all.bat" and I don't know the proper flash order for the Euro images within payload.bin as there's no xml file (I looked up a guide for directions on how to flash without flash-all.bat that I have used on other devices). Oh, and I tried to fastboot a known good boot.img and on one of the slots, it works fine, but still wont boot. The other gives error "FAILED (remote: Failed to load/authenticate boot image: Load Error)". I'm stumped.
Wondering if this has been experienced by anyone else before. Wiping my device is the last resort and shall be avoided at all costs after how much I have configured it to my liking.
I saw the following on another guide:
Code:
fastboot flash boot boot.img
fastboot flash dtbo dtbo.img
fastboot flash modem modem.img
fastboot flash recovery recovery.img
fastboot --disable-verity flash vbmeta vbmeta.img
fastboot --disable-verity flash vbmeta_system vbmeta_system.img
fastboot reboot fastboot
fastboot flash abl abl.img
fastboot flash aop aop.img
fastboot flash bluetooth bluetooth.img
fastboot flash cmnlib cmnlib.img
fastboot flash cmnlib64 cmnlib64.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 logo logo.img
fastboot flash mdm_oem_stanvbk mdm_oem_stanvbk.img
fastboot flash multiimgoem multiimgoem.img
fastboot flash odm odm.img
fastboot flash opproduct opproduct.img
fastboot flash qupfw qupfw.img
fastboot flash spunvm spunvm.img
fastboot flash storsec storsec.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 system system.img
fastboot flash vendor vendor.img
fastboot flash product product.img
Followed this guide here after extracting the Europe full system image via Payload-dumper and it now boots somewhat, but after it looks like it's loading into OOS and boot is complete, I get a black screen instead of the lock screen. I get charging sounds when plugged into the computer, but just a black screen.
How to Create Fastboot-flashable Factory Image for Any OnePlus Phone
Learn how to create a factory image for any OnePlus phone and flash it using Fastboot. Useful for restoring stock OxygenOS software and unbricking.
www.thecustomdroid.com
Wondering if this has to do with the Europe 11.2.4.4 on my Global device. Going to try reverting to 11.2.2.2 Global full image now.
Geez, good luck
vibrantliker said:
Geez, good luck
Click to expand...
Click to collapse
Just tried flashing the older 11.2.2.2 images one at a time and now it's stuck in recovery...
The closest I can get it to full booting is with 11.2.4.4 Europe full image and I get a black screen only, after it boots up with the OnePlus logo. When plugged in, I get a charging sound every 10-20 seconds or so. Too bad there's no 11.2.4.4 full image for Global or I'd try that.
Also just tried fastboot boot 11.2.4.4_global_boot.img on this 11.2.4.4 Europe image and still no go. Boots and makes sounds, but black screen still.
Have you tried the MSM tool?
hadesflames said:
Have you tried the MSM tool?
Click to expand...
Click to collapse
I was considering it, but don't want to lose any data. Next step is to contact OnePlus technical support during normal hours and see if they can work with me to resolve this one. I believe I read here on XDA that people have contacted them and usually are able to resolve the issue. Trying to avoid clearing data as the device is fine as it boots, but I think the Europe image is conflicting somewhere and not allowing me into the system since it boots all the way to the lock screen, but I don't see a lock screen, just a blank screen with sounds after boot seemingly working, along with charging sounds (albeit, sounding every 10-20s like its periodically charging).
This is so odd though because I did everything as I should've and update seemingly occurred, but system version still showed 11.2.3.3. So I go back to system update and it said there was an issue and to restart again. Did that two times with magisk revert image and restore to inactive and it then stopped booting.
If you're able to get to the recovery you can try sideloading the zip file
ADB Sideload name.zip
That should put the rom back to default, I would reboot the phone back into recovery and then do a wipe or go to fastboot and use "fastboot -w" to wipe the userdata
djsubterrain said:
If you're able to get to the recovery you can try sideloading the zip file
ADB Sideload name.zip
That should put the rom back to default, I would reboot the phone back into recovery and then do a wipe or go to fastboot and use "fastboot -w" to wipe the userdata
Click to expand...
Click to collapse
Does stock recovery support ADB? At 8 pro you needed modified one..
pyry666 said:
Does stock recovery support ADB? At 8 pro you needed modified one..
Click to expand...
Click to collapse
As far as I know, it should do as long as the drivers are installed properly, you can check with "ADB Devices", if you see the number returned then the phone is responding.
As for the fastboot commands above, I know there was a post on the OP7P forum that would make fastboot script packs for each build, if you use the script from those, you should able to amend it to flash the images above. Afaik the structure is likely the same anyway. The post also shows "ADB push" commands you can use to flash individual images to the phone.
I might have a look later and see if I can make a similar one although there seems to be a lot more build versions on the OP9P than there were for the OP7P.
Might just be easier to use the Payload Dumper program to unpack the images from the payload.bin file (instructions here) and then use a generic script to flash them to the phone, all the different models should have similar images although I do know there's an additional India.img for the Indian models (which I think is also shown in the global rom).
djsubterrain said:
As far as I know, it should do as long as the drivers are installed properly, you can check with "ADB Devices", if you see the number returned then the phone is responding.
Click to expand...
Click to collapse
I was just corious, not at home right now so i cant test. My drivers are fine and have no issues..I am using linux myself though
pyry666 said:
I was just corious, not at home right now so i cant test. My drivers are fine and have no issues..I am using linux myself though
Click to expand...
Click to collapse
Yeah I'm working at the moment so not on my own PC, can't really test it out
djsubterrain said:
Yeah I'm working at the moment so not on my own PC, can't really test it out
Click to expand...
Click to collapse
Just tried. ADB with stock recovery is "unauthorized"..So modified is needed if one wants to use stock recovery with adb
djsubterrain said:
As far as I know, it should do as long as the drivers are installed properly, you can check with "ADB Devices", if you see the number returned then the phone is responding.
As for the fastboot commands above, I know there was a post on the OP7P forum that would make fastboot script packs for each build, if you use the script from those, you should able to amend it to flash the images above. Afaik the structure is likely the same anyway. The post also shows "ADB push" commands you can use to flash individual images to the phone.
I might have a look later and see if I can make a similar one although there seems to be a lot more build versions on the OP9P than there were for the OP7P.
Might just be easier to use the Payload Dumper program to unpack the images from the payload.bin file (instructions here) and then use a generic script to flash them to the phone, all the different models should have similar images although I do know there's an additional India.img for the Indian models (which I think is also shown in the global rom).
Click to expand...
Click to collapse
I tried flashing all of the 11.2.4.4 Europe full system image payload_dumper extracted images (such as boot.img, system.img, dtbo.img) to the phone and I get where I am now. It goes through boot, but no lock screen, just a non-lit/black screen with sounds that the phone is charging when plugged in and is recognized by the computer (but can't see internal storage since you have to use notification center to turn on usb storage).
bulletbling said:
I tried flashing all of the 11.2.4.4 Europe full system image payload_dumper extracted images (such as boot.img, system.img, dtbo.img) to the phone and I get where I am now. It goes through boot, but no lock screen, just a non-lit/black screen with sounds that the phone is charging when plugged in and is recognized by the computer (but can't see internal storage since you have to use notification center to turn on usb storage).
Click to expand...
Click to collapse
See if you can do a fastboot -w to wipe the userdata in case it's been left with unusable data.
djsubterrain said:
See if you can do a fastboot -w to wipe the userdata in case it's been left with unusable data.
Click to expand...
Click to collapse
This is what I'm trying to avoid...
Since it mostly boots on the Euro 11.2.4.4, I feel that the Global full image would resolve this, but OnePlus never updates their darn website with the latest for Global.
bulletbling said:
This is what I'm trying to avoid...
Since it mostly boots on the Euro 11.2.4.4, I feel that the Global full image would resolve this, but OnePlus never updates their darn website with the latest for Global.
Click to expand...
Click to collapse
Are there actual hw differences between AA and BA?
bulletbling said:
This is what I'm trying to avoid...
Since it mostly boots on the Euro 11.2.4.4, I feel that the Global full image would resolve this, but OnePlus never updates their darn website with the latest for Global.
Click to expand...
Click to collapse
There's a pinned post at the top of the forum with all the available latest roms. Not sure they've added Global yet tho. Best going there or Oxygen Updater (when the phone is working) than the download page tbh, OnePlus ALWAYS takes ages to add builds there
pyry666 said:
Are there actual hw differences between AA and BA?
Click to expand...
Click to collapse
Not that I know of, but I have seen users use the Europe image to update their device on this forum before with the OP9Pro because they either didn't want to wait or needed to fix their device for whatever reason and the Europe version worked fine. So I don't know if this is different on 11.2.4.4.
bulletbling said:
Not that I know of, but I have seen users use the Europe image to update their device on this forum before with the OP9Pro because they either didn't want to wait or needed to fix their device for whatever reason and the Europe version worked fine. So I don't know if this is different on 11.2.4.4.
Click to expand...
Click to collapse
I know that BA is coming first than AA. Dont know reason for that but with op8p situation was same. Then was talk about googles servers or something but cant remember what that was exactly because it never affected me..
pyry666 said:
I know that BA is coming first than AA. Dont know reason for that but with op8p situation was same. Then was talk about googles servers or something but cant remember what that was exactly because it never affected me..
Click to expand...
Click to collapse
I wish I could go without my phone for weeks until they post the latest firmware to see if that even works, but I can't so I guess I'll have to use the msm tool and wipe all of my internal storage of documents, including taxes, and various files and downloads I've amassed over the past half decade. This really sucks. All because of a simple OTA that should've never caused this. They really should prevent this from being possible with the OTA update tool built-in to their system.