Develop Bugs

System using 19.9gb on a 32gb pixel xl

Last night i bricked my phone and accidently deleted system partitions i think from slot A and slot B when i was trying to install twrp. I always try to figure out how to fix it from reading helpful guides and without asking questions. I flashed full image a couple of times because i was getting bootloops everytime. In the last try, i flashed full image then gave me a bootloop again. So what i did, i adb sideload ota and it booted fine. Now im rooted and it seems i installed twrp correctly, i currently have nde63v build. At the moment i have supposedly used 22.71gb of 29.70gb.
So can someone let me know what i did wrong or point me out how to get those gbs back please.

ls2power said:
Last night i bricked my phone and accidently deleted system partitions i think from slot A and slot B when i was trying to install twrp. I always try to figure out how to fix it from reading helpful guides and without asking questions. I flashed full image a couple of times because i was getting bootloops everytime. In the last try, i flashed full image then gave me a bootloop again. So what i did, i adb sideload ota and it booted fine. Now im rooted and it seems i installed twrp correctly, i currently have nde63v build. At the moment i have supposedly used 22.71gb of 29.70gb.
So can someone let me know what i did wrong or point me out how to get those gbs back please.
Click to expand...
Click to collapse
I just did a factory reset and it fixed it. I also was stock without twrp though.

seshaz said:
I just did a factory reset and it fixed it. I also was stock without twrp though.
Click to expand...
Click to collapse
I tried factory reset already but still shows system using 19.9gbs.

Have you tried doing a complete full flash of nde63v without installing TWRP or root to see if it goes back to normal?

cambunch said:
Have you tried doing a complete full flash of nde63v without installing TWRP or root to see if it goes back to normal?
Click to expand...
Click to collapse
yes i did a few times, it would just bootloop. Until i sideloaded ota nde63v on top of full system img then it booted fine

ls2power said:
I tried factory reset already but still shows system using 19.9gbs.
Click to expand...
Click to collapse
Mine shows system using 19.9 gigs also. I posted this on another thread as I thought it seemed high but no one said weather it was high or was not so I assumed it was normal to use 19.9 gigs of space on my verizon pixel xl. I"am rooted on the x software but I couldnt get twrp working and I figured what good was TWRP if there was no supersu that was working with it and I decided to wait for TWRP to get out of beta to try again.

ls2power said:
yes i did a few times, it would just bootloop. Until i sideloaded ota nde63v on top of full system img then it booted fine
Click to expand...
Click to collapse
If you are getting a bootloop after flashing a factory image, I would assume it isn't flashing correctly. Can you post the output of what happens when you run the flashall.bat?

cambunch said:
If you are getting a bootloop after factory a factory image, I would assume it isn't flashing correctly. Can you post the output of what happens when you run the flashall.bat?
Click to expand...
Click to collapse
im able to flash every single img, but when i try to flash flashall.bat it doesnt seem to work. I will give it a try once i get home from work. The only thing bugging me is that the system shows using 19.9gb of space.

Mine is only using 6.79GB. Something is definitely off with yours.
Sent from my Pixel XL using XDA-Developers mobile app

Neomage84 said:
Mine is only using 6.79GB. Something is definitely off with yours.
Click to expand...
Click to collapse
yes there is. When you reboot your phone, which slot does it have? And do you have twrp installed and root?

M9guy said:
Mine shows system using 19.9 gigs also. I posted this on another thread as I thought it seemed high but no one said weather it was high or was not so I assumed it was normal to use 19.9 gigs of space on my verizon pixel xl. I"am rooted on the x software but I couldnt get twrp working and I figured what good was TWRP if there was no supersu that was working with it and I decided to wait for TWRP to get out of beta to try again.
Click to expand...
Click to collapse
I fixed it, i flashed full system image while i was on slot A. Now system is using 5.39gb, im on V build.

i have the same problem with a 128GB version not sure whats up but to fix it i just flashed over and over and one of them just worked would be nice to know the cause so i dont have to flash many times to get it to show full space again.

How do you select slot a while stock? I can select it in twrp but need to know how to get stock images to flash to a

theycallmerayj said:
How do you select slot a while stock? I can select it in twrp but need to know how to get stock images to flash to a
Click to expand...
Click to collapse
I figured out how to fix it by selecting slot a through twrp, booting into fastboot and flashing stock images. However, I am curious how it even ended up on slot b when I went from stock to unlocked and simply flashed the factory images. I never intended to switched from a to b.

theycallmerayj said:
How do you select slot a while stock? I can select it in twrp but need to know how to get stock images to flash to a
Click to expand...
Click to collapse
theycallmerayj said:
I figured out how to fix it by selecting slot a through twrp, booting into fastboot and flashing stock images. However, I am curious how it even ended up on slot b when I went from stock to unlocked and simply flashed the factory images. I never intended to switched from a to b.
Click to expand...
Click to collapse
whenever you flash a factory img or an OTA, or any firmware, the slots will switch unless told not to, i believe this is to keep them in sync aka the seamless updates. here is some info on that - http://www.androidpolice.com/2016/1...-partition-changes-and-new-fastboot-commands/
Quick Tip - while in cmdlne for ADB and Fastboot, and fully updated, just type
Code:
adb
to get all the ADB commands available, and likewise for fastboot, just type
Code:
fastboot
And to switch active slots type
Code:
fastboot set_active -a
or
Code:
fastboot set_active -b
. Then to activate slot
Code:
fastboot reboot bootloader
I believe with TWRP installed you have to switch slots in TWRP.
Click to expand...
Click to collapse
Moving on, I found this to be pretty helpful, it's not the exact answer you are looking for, but i think it will come in handy.
All dual-booting credit in this thread goes to hucqym, this wasn't my idea, im just a messenger.
hucqym said:
so I successfully have the dual boot running on my pixel (verizon edition) with the same configuration you are trying (one is NDE63X image rooted and one is NDE63X image stock/unrooted). Here were my steps:
-> dePixel8 to unlock bootloader (because verizon edition pixel)
-> download NDE63X image from google and modified flash_all.sh to flash stock images to both slots manually
using the --slot _a/_b and --skip-secondary flags. Modified scripts below. At this point I confirmed that I could boot to both slots. I also verified bootloader lock/unlock again to make sure it was stock image on both slots
-> TWRP alpha2 to get recovery on both slots
-> with slot _b selected as active in TWRP, i installed the SuperSU v2.78 SR4 zip
-> with slot _a as active in TWRP, installed ElementalX-P-1.00 zip for the kernel patch to pass SafetyNet
voila, I now have non-rooted on slot _a and rooted on slot _b
Note that TWRP is not really a requirement for doing this. I had the same dual boot configuration working with SuperSU v2.78 SR3 rooting one slot directly. The only reason I needed TWRP is so that I can switch slots easily on the device and don't need a cable and a laptop just to switch the bootloader flag
Although, I got this to work it still falls short of what I really wanted to do. For my use-case I would really want an isolated userdata for the two slots so I can use the rooted slot as a complete sandbox. and then perhaps have a shared folder mechanism between the two. ...so if somebody has an idea on this, I'm all ears.
[UPDATE]: Note that the unrooted slot is still limited in the sense that safetynet checks fail and so AndroidPay etc.. that use that API will still not work. This, however, has little to do with the dual boot setup and more because SafetyNet now fails on just unlocked bootloader and we do need it unlocked. On Conchors' suggestion, I installed ElementalX kernel on slotA from TWRP and now my 'otherwise-stock' non-rooted image on slotA passes SafetyNet while slotB is successfully rooted
flash_all_slot-a.sh
Code:
fastboot flash --slot _a bootloader bootloader-sailfish-8996-012001-1608281716.img
fastboot reboot-bootloader
sleep 5
fastboot flash --slot _a radio radio-sailfish-8996-012511-1609191801.img
fastboot reboot-bootloader
sleep 5
#fastboot -w update image-sailfish-nde63x.zip
fastboot update --slot _a --skip-secondary image-sailfish-nde63x.zip
flash_all_slot-b.sh
Code:
fastboot flash --slot _b bootloader bootloader-sailfish-8996-012001-1608281716.img
fastboot reboot-bootloader
sleep 5
fastboot flash --slot _b radio radio-sailfish-8996-012511-1609191801.img
fastboot reboot-bootloader
sleep 5
#fastboot -w update image-sailfish-nde63x.zip
fastboot update --slot _b --skip-secondary image-sailfish-nde63x.zip
Click to expand...
Click to collapse
I switched it up a bit, and to be perfectly honest, the script is easier, this is just an alternate way of doing it
I did this for both slot_a and slot_b (not sure if it is needed for the flrst one, but that is what i did), both ways are correct, this way is much longer, but it gives some control, plus it's a nice learning process as it is pretty easy going.
If you are going to erase, erase first before you start anything, because you know...science.
Code:
fastboot erase boot
fastboot erase cache
fastboot erase system
fastboot erase vendor
the cache partition, i dont remember if this worked or not, I'm too tired to verify
Code:
fastboot flash --slot _b --skip-secondary bootloader "name-of-bootloader.img"
fastboot reboot-bootloader
fastboot flash --slot _b --skip-secondary radio "name-of-radio.img"
fastboot reboot-bootloader
fastboot flash --slot _b --skip-secondary system system.img
fastboot flash --slot _b --skip-secondary boot boot.img
fastboot flash --slot _b --skip-secondary vendor vendor.img
If you want to wipe everything, use the following commands next:
Code:
fastboot erase userdata
fastboot flash userdata userdata.img
fastboot reboot
system.img and userdata.img take time to flash— the command prompt appears to stop. Let it do it's thing, when it's done the cursor will begin blinking again.
All dual-booting credit goes to hucqym; again, not my idea.
Slightly Off Topic -
Has anyone tried this on a specific slot, does it make any difference?) I haven't actually even thought of this till now
something like:
Code:
fastboot erase --slot _(a/b) --skip-secondary userdata
fastboot flash --slot _(a/b) --skip-secondary userdata userdata.img[/B]
theycallmerayj said:
I figured out how to fix it by selecting slot a through twrp, booting into fastboot and flashing stock images. However, I am curious how it even ended up on slot b when I went from stock to unlocked and simply flashed the factory images. I never intended to switched from a to b.
Click to expand...
Click to collapse
ls2power said:
Last night i bricked my phone and accidently deleted system partitions i think from slot A and slot B when i was trying to install twrp. I always try to figure out how to fix it from reading helpful guides and without asking questions. I flashed full image a couple of times because i was getting bootloops everytime. In the last try, i flashed full image then gave me a bootloop again. So what i did, i adb sideload ota and it booted fine. Now im rooted and it seems i installed twrp correctly, i currently have nde63v build. At the moment i have supposedly used 22.71gb of 29.70gb.
So can someone let me know what i did wrong or point me out how to get those gbs back please.
Click to expand...
Click to collapse
I was noticing quite a bit of space missing as well. what i did was boot into the slot I wanted as secondary (do this in TWRP), and i wiped just the system (which includes cache) and reflashed the system.img directly pulled from factory.zip. I noticed twice as much space had been gained then what was actually said to be there. I was a little surprised...it was over 5 gb I had gained while the system only said 2.5ish gb. (perhaps there was a second other_system.img wrapped up in it, I don't know. Then i went back to the primary slot and booted back up.
It's possible I got off course, I'm tired.

Can I flash any GSI ?

My device (Redmi 8) is Treble supported & A-only Arm64 system.
Can I flash any A-only ARM64 GSI rom ?
I tried couple of A-only Arm64 GSI's, those flash successfully but my device start and Redmi logo appears and its restart again & again.

+1

ahmd gom3aa said:
+1
Click to expand...
Click to collapse
??

Tauseef786 said:
My device (Redmi 8) is Treble supported & A-only Arm64 system.
Can I flash any A-only ARM64 GSI rom ?
I tried couple of A-only Arm64 GSI's, those flash successfully but my device start and Redmi logo appears and its restart again & again.
Click to expand...
Click to collapse
Does the device have encryption disabled?
Do you use patch files to start / force the start?
Do you have the boot or recovery in permissive mode?

@Tauseef786
Did make a wipe of the userdata after flashing the GSI?
Did you try to flash the vbmeta linked from phh in his quack thread before flashing the GSI?

dhacke said:
@Tauseef786
Did make a wipe of the userdata after flashing the GSI?
Did you try to flash the vbmeta linked from phh in his quack thread before flashing the GSI?
Click to expand...
Click to collapse
Excuse me, I went to phh thread to see where is this vbmeta but I didn't find it...where is it & what does it do?

Magdy Doze said:
Excuse me, I went to phh thread to see where is this vbmeta but I didn't find it...where is it & what does it do?
Click to expand...
Click to collapse
That's the link to the vbmeta which phh suggests:
https://dl.google.com/developers/android/qt/images/gsi/vbmeta.img
Some devices need it to allow a GSI boot.

dhacke said:
That's the link to the vbmeta which phh suggests:
https://dl.google.com/developers/android/qt/images/gsi/vbmeta.img
Some devices need it to allow a GSI boot.
Click to expand...
Click to collapse
so its flashed before the system image right?
& the order would be (fastboot flash system vbmeta.img)?
---------- Post added at 08:35 PM ---------- Previous post was at 08:32 PM ----------
Tauseef786 said:
??
Click to expand...
Click to collapse
he meant to say (same) as he has the same problem...it came from the like button on social media when it shows the (+1) to endorse a certain comment/post

Magdy Doze said:
so its flashed before the system image right?
& the order would be (fastboot flash system vbmeta.img)?
Click to expand...
Click to collapse
Yes first vbmeta and then system.
But the command you wrote is wrong. You need to execute one command for the vbmeta and one for the system.
So the commands would be:
1. fastboot flash vbmeta 'name of the vbmeta img'
2. fastboot flash system 'name of the system img'
If you have a device which comes with Android 10 out of the box you can only flash the system.img in fastbootd mode probably. This means you need one extra command between the ones i wrote. In this case it would show as follows:
1. fastboot flash vbmeta 'name of the vbmeta img'
2. fastboot reboot fastboot
3. fastboot flash system 'name of the system img'

dhacke said:
Yes first vbmeta and then system.
But the command you wrote is wrong. You need to execute one command for the vbmeta and one for the system.
So the commands would be:
1. fastboot flash vbmeta 'name of the vbmeta img'
2. fastboot flash system 'name of the system img'
If you have a device which comes with Android 10 out of the box you can only flash the system.img in fastbootd mode probably. This means you need one extra command between the ones i wrote. In this case it would show as follows:
1. fastboot flash vbmeta 'name of the vbmeta img'
2. fastboot reboot fastboot
3. fastboot flash system 'name of the system img'
Click to expand...
Click to collapse
Got it now..thanks a lot

Tauseef786 said:
My device (Redmi 8) is Treble supported & A-only Arm64 system.
Can I flash any A-only ARM64 GSI rom ?
I tried couple of A-only Arm64 GSI's, those flash successfully but my device start and Redmi logo appears and its restart again & again.
Click to expand...
Click to collapse
I have a Redmi 8 and i remember flashing an A-only rom resulting in bootloop too. I also had problems with A/B roms but i fixed it by formatting (not just wiping) /data, after you do that it will reboot once in the Redmi logo then all the next boots will work. Currently running A/B Lineage 17 while before i was running Pixel Experience 10 A/B just fine. I know technically it's an A/B rom but it works.
Please try formatting /data first with the A-Only image. You can do so by going in TWRP>Wipe>Format Data. Let me know if this worked. If it didn't, flash an A/B image then format data with the instructions above. I know that the Redmi 8 technically is A-Only, but this worked fine for me soo feel free to try. Remember to format data for A/B images too, or they will bootloop!
EDIT:
Why should I use GSI for A/B devices to some A-only devices? : On Android 9, Google changed the requirements and all devices shipped with Android 9 must use "system-as-root". Before this change, only A/B devices were system-as-root and GSI name was separated by A-only and A/B. For this historical reasons, you have to use GSI for A/B on the devices shipped with Android 9+. (source: https://github.com/phhusson/treble_experimentations/wiki)
Click to expand...
Click to collapse
Redmi 8 comes with Android 9, thus it needs A/B GSIs as the above and the device list on the article says.

While the issue for the OP was solved, I still wanted to repeat the question: Can I flash any A/B/AB Treble ROM (according to my device) onto my phone? So basically all Treble ROMs will be compatible to my treble-enabled device?
I already understood the general principle of Treble, I just am thankful for a last bit of comfirmation about this.
Thanks in advance.

BenjyTec said:
While the issue for the OP was solved, I still wanted to repeat the question: Can I flash any A/B/AB Treble ROM (according to my device) onto my phone? So basically all Treble ROMs will be compatible to my treble-enabled device?
I already understood the general principle of Treble, I just am thankful for a last bit of comfirmation about this.
Thanks in advance.
Click to expand...
Click to collapse
B-Only doesn't exist
But as long as it has a fitting variant (in this case AOnly Arm64)
Everything should be fine

0

Question 11.2.4.4 Update Ended Badly - Assistance is Needed on This One

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.

General Soft bricked when update C.62 to C.63, help needed please.

I was on C.62 AA with a working Magisk.
Yesterday I tried to update to C.63 AA with following steps:
1. Disable all Magisk module and reboot.
2. Restore Stock Image from Magisk Manager.
3. Update to C.63 from System Settings menu.
4. Install Magisk to inactive slot, then reboot.
That's it.
After reboot, my OP9P starts, but can't get into lock screen. Instead it only show black screen with a nonstop vibration.
I didn't do backup since I was NOT expecting this to happen.
Now I'm desperate for any help to unbick it or at lease get my files in sdcard back.
I can go into bootloader and fastbootd mode. ANY help would be much appreciated.

dna1982 said:
I was on C.62 AA with a working Magisk.
Yesterday I tried to update to C.63 AA with following steps:
1. Disable all Magisk module and reboot.
2. Restore Stock Image from Magisk Manager.
3. Update to C.63 from System Settings menu.
4. Install Magisk to inactive slot, then reboot.
That's it.
After reboot, my OP9P starts, but can't get into lock screen. Instead it only show black screen with a nonstop vibration.
I didn't do backup since I was NOT expecting this to happen.
Now I'm desperate for any help to unbick it or at lease get my files in sdcard back.
I can go into bootloader and fastbootd mode. ANY help would be much appreciated.
Click to expand...
Click to collapse
Unfortunately the only thing that's going to get device up and going again is msm or factory reset. You could possibly get a boot without wiping if you have untouched boot images of build you were on but then you don't know which side it booted to. I'd factory reset . Or keep device dead. You will still have patched boot.img so just reinstall magisk manager after reset.

mattie_49 said:
Unfortunately the only thing that's going to get device up and going again is msm or factory reset. You could possibly get a boot without wiping if you have untouched boot images of build you were on but then you don't know which side it booted to. I'd factory reset . Or keep device dead. You will still have patched boot.img so just reinstall magisk manager after reset.
Click to expand...
Click to collapse
I do have untouched boot images(C.63 AA) from the other thread.
I did try to "fastboot boot boot.img", result the same -- black screen with a nonstop vibration.
I think something went wrong during the update process.
Maybe flashing a stock rom in fastboot mode will help, but I don't know how and I can't find any info about howto flash OxygenOS 12 in fastboot on OP9P.

what you can try is the c63 full rom via fastbootd with the tool Fastboot Enhance to flash
[TOOL][Windows] Fastboot Enhance [Payload Dumper & Image Flasher]
Fastboot Enhance What it can do? - Show fastboot vars - Switch between fastbootd & bootloader - Switch between A & B slot - Flash Payload.bin in fastbootd - Flash images - Erase partitions - Delete logical partitions - Create logical partitions...
forum.xda-developers.com

but that will be difficult because there is no aa full rom (only india) since the update to c63 was only released globally as an incremental update

ChrisFeiveel84 said:
what you can try is the c63 full rom via fastbootd with the tool Fastboot Enhance to flash
[TOOL][Windows] Fastboot Enhance [Payload Dumper & Image Flasher]
Fastboot Enhance What it can do? - Show fastboot vars - Switch between fastbootd & bootloader - Switch between A & B slot - Flash Payload.bin in fastbootd - Flash images - Erase partitions - Delete logical partitions - Create logical partitions...
forum.xda-developers.com
Click to expand...
Click to collapse
ChrisFeiveel84 said:
but that will be difficult because there is no aa full rom (only india) since the update to c63 was only released globally as an incremental update
Click to expand...
Click to collapse
The Fastboot Enhance Tool you post does look promising.
I guess I will just wait for AA full rom to come out.
Thank you.

dna1982 said:
The Fastboot Enhance Tool you post does look promising.
I guess I will just wait for AA full rom to come out.
Thank you.
Click to expand...
Click to collapse
Last full rom for aa is
C48
I don't think that oneplus will release a full aa again

ChrisFeiveel84 said:
Last full rom for aa is
C48
I don't think that oneplus will release a full aa again
Click to expand...
Click to collapse
I will wait a week or two before flash DA C.63.

dna1982 said:
I do have untouched boot images(C.63 AA) from the other thread.
I did try to "fastboot boot boot.img", result the same -- black screen with a nonstop vibration.
I think something went wrong during the update process.
Maybe flashing a stock rom in fastboot mode will help, but I don't know how and I can't find any info about howto flash OxygenOS 12 in fastboot on OP9P.
Click to expand...
Click to collapse
It's fastboot flash boot boot.img sir.

mattie_49 said:
It's fastboot flash boot boot.img sir.
Click to expand...
Click to collapse
1. "fastboot flash" change partition permanently, while "fastboot boot" change partition temporary.
2. I also tried "fastboot flash", no luck.

dna1982 said:
I will wait a week or two before flash DA C.63.
Click to expand...
Click to collapse
The problem came up when you tried carrying root over. I've had issues as well . Make sure your on 25.2 magisk manager, disable all modules . Only uninstall magisk,restore images,start system update when finished don't reboot. Go into magisk install to inactive slot for ota. And reboot.

Just flash the full DA C.63 over it using FBE. Make sure you go to the partitions screen and search cow and delete all cow partitions before you flash or you will brick. This should at least enable you to get your files backed up so you can MSM.
Before that though, go to fastboot and try fastboot --getvar current-slot to find out what slot you're on. From there do fastboot --set-active=a or --set-active=b, whichever is not active currently. Fastboot reboot and see if your old OTA boots.

EtherealRemnant said:
Just flash the full DA C.63 over it using FBE. Make sure you go to the partitions screen and search cow and delete all cow partitions before you flash or you will brick. This should at least enable you to get your files backed up so you can MSM.
Before that though, go to fastboot and try fastboot --getvar current-slot to find out what slot you're on. From there do fastboot --set-active=a or --set-active=b, whichever is not active currently. Fastboot reboot and see if your old OTA boots.
Click to expand...
Click to collapse
he can also see which slot is active directly with fbe because fbe shows this itself, just like he can change the slot with fbe

dna1982 said:
1. "fastboot flash" change partition permanently, while "fastboot boot" change partition temporary.
2. I also tried "fastboot flash", no luck.
Click to expand...
Click to collapse
fastboot flash only flashes the active slot and does not switch to the inactive slot.. and fastboot boot only boots an image that you have specified

ChrisFeiveel84 said:
he can also see which slot is active directly with fbe because fbe shows this itself, just like he can change the slot with fbe
Click to expand...
Click to collapse
FBE's slot changer doesn't always work in my experience. Both times I tried it for the purposes of changing the slot to boot from, it didn't actually change the slot, but when I switched slots to choose which to install to, that worked correctly. I only tell people to use things I'm confident work correctly and I know fastboot slot switching is one of those things that does.

EtherealRemnant said:
FBE's slot changer doesn't always work in my experience. Both times I tried it for the purposes of changing the slot to boot from, it didn't actually change the slot, but when I switched slots to choose which to install to, that worked correctly. I only tell people to use things I'm confident work correctly and I know fastboot slot switching is one of those things that does.
Click to expand...
Click to collapse
I also noticed that if you change the slot with fbe, the active slot is still displayed in fbe, but if you then reconnect the cell phone to the pc, fbe then shows that it has changed the slot

dna1982 said:
I was on C.62 AA with a working Magisk.
Yesterday I tried to update to C.63 AA with following steps:
1. Disable all Magisk module and reboot.
2. Restore Stock Image from Magisk Manager.
3. Update to C.63 from System Settings menu.
4. Install Magisk to inactive slot, then reboot.
That's it.
After reboot, my OP9P starts, but can't get into lock screen. Instead it only show black screen with a nonstop vibration.
I didn't do backup since I was NOT expecting this to happen.
Now I'm desperate for any help to unbick it or at lease get my files in sdcard back.
I can go into bootloader and fastbootd mode. ANY help would be much appreciated.
Click to expand...
Click to collapse
Is there any update regarding this thread? The same thing happens to me after I update my phone from C.62 DA to C.63 DA my phone is stuck on a black screen and then keeps on vibrating. I am also desperate to at least recover my data.

JeanFlasher said:
Is there any update regarding this thread? The same thing happens to me after I update my phone from C.62 DA to C.63 DA my phone is stuck on a black screen and then keeps on vibrating. I am also desperate to at least recover my data.
Click to expand...
Click to collapse
Sorry to hear that.
But you don't have to wait, since there is DA C.63 full rom.
Just flash it in fastboot mode by using Fastboot Enhance tool.
Good luck and tell us how it goes.

dna1982 said:
Sorry to hear that.
But you don't have to wait, since there is DA C.63 full rom.
Just flash it in fastboot mode by using Fastboot Enhance tool.
Good luck and tell us how it goes.
Click to expand...
Click to collapse
It didn't work for me real bummer. I've tried to do what EtherealRemnant suggested (ie: full flash DA C.63 over it using FBE), still out of luck.

JeanFlasher said:
It didn't work for me real bummer. I've tried to do what ChrisFeiveel84 suggested, still out of luck.
Click to expand...
Click to collapse
Did you follow the steps that @EtherealRemnant post?
And what is the result? We need details to help you.

[Unlocked Bootloader][OOS13/OOS 13 based ROMs] How to remove bootloader unlocked message for OnePlus 8 Pro

This is a guide to remove the ugly "Your device has been unlocked and can't be trusted" or "The bootloader is unlocked and software integrity cannot be guaranteed" for OP8 Pro.
This message was removed on OOS 12 which was one great thing by OP other than the other broken parts.
So this guide is for OOS 13 not 12 as the message was removed on 12.
But OnePlus brought the message back on OOS 13.
IMPORTANT:
*I am not responsible for bricked devices, damage to your device*
I am here to post my method for anyone who is interested.
The methods have been tested
Prerequisities:
You need a unlocked bootloader
YOU NEED TO HAVE THE STOCK RECOVERY INSTALLED
If you're on a custom ROM that'll be the ROM recovery
This is XDA thread and abl.img is only for the OnePlus 8 Pro, but this method has worked for 8 series devices.
You need to be on OOS 13 and have your bootloader unlocked.
The abl.img doesn't rely on the region so it can be used on any OP8 Pro
The abl.img can be extracted using payload dumper, but download the full zip version.
I have added abl.img from OOS 13 F.10 as this is the newest abl.img that has the message removed and is from @bowow
It is recommended to backup your data before modifying anything on your system
Follow one method and stick to that method
Each method is different where one is for Stock OOS 13 and the other is for OOS 13 based Custom ROMs
Method:
Download the abl.img
Copy and paste the abl.img to platform-tools
If u don't have platform-tools, download the .zip file from download links and extract it
For Stock OOS 13
This method was tested and is from @MeHigh.G
This is for on Stock OOS 13 users
Reboot to bootloader
Type " fastboot devices " to check if your device is connected
Type " fastboot reboot fastboot "
Once booted into Fastbootd Mode, type " fastboot devices " to check if your device is connected
Then type " fastboot flash --slot=all abl abl_filename.img "
Now reboot device and done
For OOS 13 based Custom ROMs
This method was tested by me and it does work
This is for OOS 13 based ROM users
Reboot to recovery
Enter advanced
Enter fastboot
The recovery should now show fastbootd
Type " fastboot devices " to check if your device is connected
Type " fastboot flash --slot=all abl abl_filename.img
Reboot to system and done
Download Links:
SDK Platform Tools (Fastboot Tools) Here
MSMDownloadTool for OP8Pro Here
Bowow's OnePlus Firmware Updates abl section Here
OrangeFox Recovery for OP8+OP8 Pro ext4 erofs
OFox Install instructions Here
OrangeFox Community Telegram
Credits:
@HELLBOY017 For the method and using abl.img to remove the bootloader unlocked message
@MeHigh.G For his method on flashing abl.img on stock OOS 13
@bowow For this F.10 abl.img for OP8 and 8 Pro

reserved

Updates
21/11/22 - Released the XDA thread as a guide to remove the ugly "Your device has been unlocked" message for the OP8 Pro
Not sure if this method does work, but I have contacted ROM developers and they say this is the way...
I'm currently not on OOS 13 based ROM, so I can't try and hopefully this does work
21/12/22 - It has been a month and after checking with devs + testers the method does work!
I have tested the method myself
I have updated the method as there's new steps you need like flashing abl.img in both slots
But the method does work on OOS 13 based ROMS! The message can be removed!
22/12/22 - I have found the method that works on Stock OOS 13 thanks to @MeHigh.G
Stock OOS 13 users should be able to remove the bootloader unlocked message
Added new OOS 13 F.10 abl.img file and removed OOS 12 C36 abl.img due to F.10 being newer to ensure users have a newer bootloader
Credited Bowow for giving the F.10 abl.img file for OP8/8 Pro
5/1/23 - Updated methods to flash abl.img in both slots easily instead of flashing abl.img in one slot
Changed "fastboot flash abl abl.img" to " fastboot flash --slot=all abl abl_filename.img " which will flash abl.img in both slots.
For custom ROM method, you will no longer need to reboot and switch slots with the new command

Nice!

Hello!
Since this is working through fastboot, why does it matter what version of Android you are on? So long as abl exixts. Or is abl partition specific to OOS 13?
Thank you
Hmmm, this abl.img is bootloader (version) specific?? Anyone try on anything other than OOS 13?

gregpilot said:
Hello!
Since this is working through fastboot, why does it matter what version of Android you are on? So long as abl exixts. Or is abl partition specific to OOS 13?
Thank you
Hmmm, this abl.img is bootloader (version) specific?? Anyone try on anything other than OOS 13?
Click to expand...
Click to collapse
Abl is part of the bootloader. Well, normally people from oneplus 9 forum got abl from open beta 2, which is oos13 too but without yellow reminder, they flashed it and yeah, it worked, but guy who tried that wrote that he have problems in his oos13. He was stuck in setupwizard and couldn't go on, so he needed to do few more steps.
Btw with all respect to autor of 1. post i will not trust this guy. He don't say any single word where he get this file, from which version, and best part is that, he clearly stated that he didn't even try this, because he's not on oos13. IMO this yellow reminder is ok, and i will not trust guy, who even didn't try to check if it's working. But... It's me.
EDIT: i found this topic here
Check this guys, as you might be stuck in setupwizard or something. Don't blindly use this method, but first read how it works and how to eventually fix this.

ShadoV90 said:
Abl is part of the bootloader. Well, normally people from oneplus 9 forum got abl from open beta 2, which is oos13 too but without yellow reminder, they flashed it and yeah, it worked, but guy who tried that wrote that he have problems in his oos13. He was stuck in setupwizard and couldn't go on, so he needed to do few more steps.
Btw with all respect to autor of 1. post i will not trust this guy. He don't say any single word where he get this file, from which version, and best part is that, he clearly stated that he didn't even try this, because he's not on oos13. IMO this yellow reminder is ok, and i will not trust guy, who even didn't try to check if it's working. But... It's me.
EDIT: i found this topic here
Check this guys, as you might be stuck in setupwizard or something. Don't blindly use this method, but first read how it works and how to eventually fix this.
Click to expand...
Click to collapse
That's for the OP9 Pro not the OP8 Pro...
I only learned about this from the dev @HELLBOY017 and it worked for him. He never stated u needed a data wipe.
So I did check that it was working otherwise I would never post something that wouldn't work and wasn't tested.
And I did say.... *I am not responsible for bricked devices, damage to your device* I am here to post my method for anyone who is interested.
I have now posted where I got the abl.img from and the tool I used to extract the payload.bin.
It was from EU OOS 12 C36 full zip
We'll see how it goes as this is new for 8 Pro users and hopefully it does work
Thanks for the reminder of the missing info to include

Extreme_Ninja2099 said:
That's for the OP9 Pro not 8 Pro...
I have now posted where I got the abl.img from and the tool I used to extract the payload.bin.
It was from EU OOS 12 C36 full zip
Click to expand...
Click to collapse
I know that's for OP9 Pro. But if their device might have problems with it, our device can have problems too.
Maybe it will be without problems, maybe problems will occur. You don't know, because you don't even test it.
We don't even know possible bad outcome. That's all.
And to be clear...
I'm not attacking you or something. I just want to warn people to be careful with messing with critical partitions.

ShadoV90 said:
I know that's for OP9 Pro. But if their device might have problems with it, our device can have problems too.
Maybe it will be without problems, maybe problems will occur. You don't know, because you don't even test it.
We don't even know possible bad outcome. That's all.
And to be clear...
I'm not attacking you or something. I just want to warn people to be careful with messing with critical partitions.
Click to expand...
Click to collapse
Never considered it as an attack, just posting to clarify where I got this info and everything from.
I only found out about this yesterday from Hellboy017 and it worked for him.
I would recommend this only for users on OOS 13 just to be safe
If something does go wrong, follow the link by @ShadoV90
Do a factory reset or use MSMDownload Tool

thanks for the tip, i'll check it out asap
Edit : FAILED (remote: 'Flashing is not allowed for Critical Partitions. ')
we might have to use the --force argument in the fastboot command
try at your own risk

Neil_Armstrong_ said:
thanks for the tip, i'll check it out asap
Edit : FAILED (remote: 'Flashing is not allowed for Critical Partitions. ')
we might have to use the --force argument in the fastboot command
try at your own risk
Click to expand...
Click to collapse
Yep, because abl is critical partition (part of bootloader) as i said. There are two "unlocks".
Normal unlock, where you can change boot image or recovery, etc, which will cause softbrick if something goes wrong.
Critical unlock, in most devices allows to mess with partitions which MUST be signed and (if something will go wrong) can brick your device harder, and will lead to use MSM as last resort.
Unlocking critical part can be achieved MOSTLY (not always from what i know) by typing in fastboot mode (in command prompt):
fastboot flashing unlock_critical
Sincerely, idk if it's working, as for me it wasn't needed. If this command isn't supported then you will just get info about it.

ShadoV90 said:
Yep, because abl is critical partition (part of bootloader) as i said. There are two "unlocks".
Normal unlock, where you can change boot image or recovery, etc, which will cause softbrick if something goes wrong.
Critical unlock, in most devices allows to mess with partitions which MUST be signed and (if something will go wrong) can brick your device harder, and will lead to use MSM as last resort.
Unlocking critical part can be achieved MOSTLY (not always from what i know) by typing in fastboot mode (in command prompt):
fastboot flashing unlock_critical
Sincerely, idk if it's working, as for me it wasn't needed. If this command isn't supported then you will just get info about it.
Click to expand...
Click to collapse
the flashing unlock_critical output is the fastboot help, i guess it's not working
I will try again saturday on Linux to see if it helps

ShadoV90 said:
Yep, because abl is critical partition (part of bootloader) as i said. There are two "unlocks".
Normal unlock, where you can change boot image or recovery, etc, which will cause softbrick if something goes wrong.
Critical unlock, in most devices allows to mess with partitions which MUST be signed and (if something will go wrong) can brick your device harder, and will lead to use MSM as last resort.
Unlocking critical part can be achieved MOSTLY (not always from what i know) by typing in fastboot mode (in command prompt):
fastboot flashing unlock_critical
Sincerely, idk if it's working, as for me it wasn't needed. If this command isn't supported then you will just get info about it.
Click to expand...
Click to collapse
if you try to fastboot flash abl abl.img in bootloader it will give you that error YES!
But if you boot to a custom recovery and from there boot into fastboot mode then there will be no error and the file will be flashed successfully.
I talk from experience! And BTW just did that a minute ago.

MeHigh.G said:
if you try to fastboot flash abl abl.img in bootloader it will give you that error YES!
But if you boot to a custom recovery and from there boot into fastboot mode then there will be no error and the file will be flashed successfully.
I talk from experience! And BTW just did that a minute ago.
Click to expand...
Click to collapse
Nice feedback, can you share what custom recovery you use on OOS 13 ?

so this work or not?

Neil_Armstrong_ said:
Nice feedback, can you share what custom recovery you use on OOS 13 ?
Click to expand...
Click to collapse
There's no custom recovery currently for OOS 13... Only for custom ROMs

Neil_Armstrong_ said:
Nice feedback, can you share what custom recovery you use on OOS 13 ?
Click to expand...
Click to collapse
I use oFox or the one provided with Flamingo OS or Pixel Blaster

so the steps are :
1- extracting the abl file from the rom we are running using paylaod.bin.
2- booting to recovery using oFox or the one provided with Flamingo OS or Pixel Blaster.
3- booting from there to fastboot
4- flashing the abl file.
right .?

STALKER18 said:
so the steps are :
1- extracting the abl file from the rom we are running using paylaod.bin.
2- booting to recovery using oFox or the one provided with Flamingo OS or Pixel Blaster.
3- booting from there to fastboot
4- flashing the abl file.
right .?
Click to expand...
Click to collapse
I've already extracted it for the 8 pro... Up to u
For step 4 it's fastboot flash abl abl.img

i'm unable to unlock bootloader says command not supported in default implementation.
IN2021 One plus 8 pro.