Database Info

[Q] Reliably induce reset of NV550 (pls rd)

This is the Saga of three HTC Desire S'. The first one died in the bath while I was trying to watch Community. It wont become plot-relevant until the end of the story.
The second was purchased at the same time as the first and gifted by my mum to my older sister. She used it happily for several months, then got a Samsung Galaxy. She gave me her Desire, and I put in my drawer to be used as a backup since, after the bathtub incident, I'd quickly replaced my DS with another.
Six weeks ago I unfortunately was robbed at a festival - thieves went into my tent while I was asleep and took my wallet, my phone, and my camera. Police made a note (I can upload the scan of the police report) of the incident but told me the phone would probably never be found.
I called the phone company right up and asked them to put a lock on my account and block the phone. Being a Highly Organised Individual, I had taken care to write the equipment identities for all three phones in my diary. Being otherwise totally crap, I typically gave them the wrong number. Idiot.
Of course I called the company straight back and explained what had happened. They said it wouldn't be a problem and they'd put a lock on the correct phone right away. Can you guess what happened next? After frantic daily calls to Orange who at first told me it might be up to a week before the block was reversed, and then, with diminishing hope, still daily calls to the operator who after three weeks told me there was nothing they could do, I still have one barred phone. I even took the phone to a the dodgiest phone shop I could find to see if they could help, along with the crime report. They called the police. FML.
At the end of this Saga my thoughts returned to the first Desire S I ever owned, the one whose unfortunate immersion and hydrophobic sensitivities lead to its untimely demise. At this point I am very much thinking that I would like to use QPCT to clone NV item 550 from the old phone to the EEPROM of the newer one. But now I get the common "Item cannot be written and is thus read-only" error in qualcomm NV radio manager. SO I am looking for a way to reliably induce the resetting of NV item 550 to 0 so that the memory area can be re-written. I know some people on this forum have had that happen to them - for example by flashing the wrong RUUs, radios, etc. Rather than just randomly flashing different RUUs in the hope of accidentally stumbling across this bug, I was wondering if some kind soul on this forum could tell me how I could reliably induce it.
Phone is rooted (CM 10.2) with 4ext recovery, ENG hboot, locked bootloader, radio S-OFF. Drives all installed and working fine. Please PM me for more details or to give me private hints on any of this.
Thanks for everything.

radical.entropy said:
This is the Saga of three HTC Desire S'. The first one died in the bath while I was trying to watch Community. It wont become plot-relevant until the end of the story.
The second was purchased at the same time as the first and gifted by my mum to my older sister. She used it happily for several months, then got a Samsung Galaxy. She gave me her Desire, and I put in my drawer to be used as a backup since, after the bathtub incident, I'd quickly replaced my DS with another.
Six weeks ago I unfortunately was robbed at a festival - thieves went into my tent while I was asleep and took my wallet, my phone, and my camera. Police made a note (I can upload the scan of the police report) of the incident but told me the phone would probably never be found.
I called the phone company right up and asked them to put a lock on my account and block the phone. Being a Highly Organised Individual, I had taken care to write the equipment identities for all three phones in my diary. Being otherwise totally crap, I typically gave them the wrong number. Idiot.
Of course I called the company straight back and explained what had happened. They said it wouldn't be a problem and they'd put a lock on the correct phone right away. Can you guess what happened next? After frantic daily calls to Orange who at first told me it might be up to a week before the block was reversed, and then, with diminishing hope, still daily calls to the operator who after three weeks told me there was nothing they could do, I still have one barred phone. I even took the phone to a the dodgiest phone shop I could find to see if they could help, along with the crime report. They called the police. FML.
At the end of this Saga my thoughts returned to the first Desire S I ever owned, the one whose unfortunate immersion and hydrophobic sensitivities lead to its untimely demise. At this point I am very much thinking that I would like to use QPCT to clone NV item 550 from the old phone to the EEPROM of the newer one. But now I get the common "Item cannot be written and is thus read-only" error in qualcomm NV radio manager. SO I am looking for a way to reliably induce the resetting of NV item 550 to 0 so that the memory area can be re-written. I know some people on this forum have had that happen to them - for example by flashing the wrong RUUs, radios, etc. Rather than just randomly flashing different RUUs in the hope of accidentally stumbling across this bug, I was wondering if some kind soul on this forum could tell me how I could reliably induce it.
Phone is rooted (CM 10.2) with 4ext recovery, ENG hboot, locked bootloader, radio S-OFF. Drives all installed and working fine. Please PM me for more details or to give me private hints on any of this.
Thanks for everything.
Click to expand...
Click to collapse
have you tried the engHboot? it has these commands
Code:
...
(bootloader) command list
(bootloader) mb
(bootloader) mh
(bootloader) mw
(bootloader) ew
(bootloader) eh
(bootloader) eb
(bootloader) mmu
(bootloader) ram_test
(bootloader) jump
(bootloader) test
(bootloader) sdtest
(bootloader) eraseconfig
(bootloader) writeconfig
(bootloader) readconfig
(bootloader) writesku
(bootloader) readsku
(bootloader) rflash
(bootloader) tflash
(bootloader) block_test
(bootloader) partition_test
(bootloader) rbchk
(bootloader) erasesd
(bootloader) btrouter
(bootloader) tick
(bootloader) heaptable
(bootloader) emapi
(bootloader) emapiTest
(bootloader) emapiCountryID
(bootloader) emapiWlanMac
(bootloader) emapiSetDefCal
(bootloader) emapiReadCal
(bootloader) lr
(bootloader) imgcrc
(bootloader) resetautoimage
(bootloader) resetpreferdiag
(bootloader) resetRUUflag
(bootloader) writeserialno
(bootloader) readserialno
(bootloader) battcheck
(bootloader) enter
(bootloader) gotofastboot
(bootloader) gotohboot
(bootloader) writemid
(bootloader) usbtestmode
(bootloader) eraseWifiFlash
(bootloader) erase
(bootloader) readmbserialno
(bootloader) listpartition
(bootloader) erasebcid
(bootloader) writebcid
(bootloader) readbcid
(bootloader) fmrouter
(bootloader) fmtx
(bootloader) resetuP
(bootloader) bdaddress
(bootloader) wMfgTp
(bootloader) rMfgTp
(bootloader) emptypagecheck
(bootloader) saveprt2sd
(bootloader) savemem2sd
(bootloader) savefb2sd
(bootloader) emapiInit
(bootloader) emapiChannel
(bootloader) emapiBand
(bootloader) emapiRate
(bootloader) emapiRateset
(bootloader) emapiCountry
(bootloader) emapiTXpwr1
(bootloader) emapiPkteng_start
(bootloader) emapiPkteng_stop
(bootloader) emapiOut
(bootloader) emapiFqacurcy
(bootloader) emapiCrsuprs
(bootloader) emapiUp
(bootloader) emapiDown
(bootloader) emapiMpc
(bootloader) emapiCounters
(bootloader) emapiVersion
(bootloader) emapiEtheraddr
(bootloader) emapinRate
(bootloader) emapiSetIrqPin
(bootloader) bkflash2emmc
(bootloader) fl
(bootloader) loaddiag
(bootloader) lnb
(bootloader) init_a1026_fw
(bootloader) checkKeyCard
(bootloader) usbspeed
(bootloader) gpiow
(bootloader) gpior
(bootloader) mddiw
(bootloader) mddir
(bootloader) clock
(bootloader) i2cr
(bootloader) i2cw
(bootloader) i2ctest
(bootloader) ulpi
(bootloader) changeCid
(bootloader) read_l2_acc_fuse
(bootloader) qupi2cr
(bootloader) qupi2cw
(bootloader) pmgpiow
(bootloader) pmgpior
(bootloader) dgtest
(bootloader) entpa2051
(bootloader) bumpclk
(bootloader) switch_ddrfeq
(bootloader) ntrigsetcal
(bootloader) ltetest
(bootloader) sdio_loopback
(bootloader) sdio_setsize
(bootloader) sdio_readblk
(bootloader) sdio_writeblk
(bootloader) sdio_readblk
(bootloader) sdio_dumpreg
(bootloader) emmc_boot
(bootloader) fdisk_emmc
(bootloader) set_partition_emmc
(bootloader) erase_emmc
(bootloader) test_emmc
(bootloader) sector_erase_emmc
(bootloader) fat_format_emmc
(bootloader) init_emmc
(bootloader) reinit_emmc
(bootloader) write_mmc
(bootloader) set_wp_emmc
(bootloader) write_prot_test
(bootloader) clear_wp_emmc
(bootloader) set_enh_area_emmc
(bootloader) keytest
(bootloader) heap
(bootloader) boot
(bootloader) reset
(bootloader) powerdown
(bootloader) rebootRUU
(bootloader) heap_test
(bootloader) rtask
(bootloader) task
(bootloader) enableqxdm
(bootloader) gencheckpt
(bootloader) list_partition_emmc
(bootloader) load_emmc
(bootloader) check_emmc
(bootloader) check_emmc_mid
(bootloader) read_mmc
(bootloader) get_wp_info_emmc
(bootloader) send_wp_info_emmc
(bootloader) get_ext_csd_emmc
(bootloader) get_sector_info_emmc
OKAY [ 0.151s]
finished. total time: 0.152s
might help you out ?

heavy_metal_man said:
have you tried the engHboot? it has these commands might help you out ?
Click to expand...
Click to collapse
Thank you very much heavy_metal_man for your awesome reply. I'm actually on the 2.x ENG hboot, I did flash the 0.98 one you linked to earlier in the week though to get a command list but it didn't seem to offer anything different to the 2.x one. Perhaps I am mistaken?
Part of my problem is that I'm not sure what half of the commands to. Based on your excellent suggestion I have googled the ones which looked the most promising, but I don't think I managed to turn up anything conclusive. I did find this nice list here: http://pastebin.com/pgus10fN with some brief explanations for some of them though. Could you tell me which commands in particular were you thinking might help me?
Thanks again.

[Completed] Help Unlocking Soft-Bricked Nexus 5X

Hi all,
Sorry if this thread is in the wrong area.
I have in my possession a Nexus 5X which is stuck in a boot loop. I don't think it's a case of the power button being held down because the phone behaves differently depending on whether I hold the power button down or not.
I can boot into bootloader/fastboot mode which is locked. I have the standard options to Start/Restart bootloader/Recovery mode/Power off. If I try to get into recovery mode from here, the phone enters "download mode" for a short amount of time. After that, the bootloop begins again and I can only get the phone back to bootloader at best.
If I try to use the comment fastboot oem unlock I will get the message (remote: oem unlock is not allowed). I believe this is because don't have USB debugging/developer options enabled. I can't turn the phone on to enable this.
I have tried using Nexus Root Toolkit to unlock the bootloader (using the Flash Stock + Unroot and Soft-Bricked/Bootloop option) and everything seems to run fine until it restarts the phone. This triggers the boot loop again and the Nexus Root Toolkit hangs "waiting for phone..." after previously having been able to detect it.
I've tried using WinDroid Toolkit v3.1 also to unlock the bootloader without success.
Quite simply, is it possible to unlock the bootloader while the phone is in this state? I know this is a common problem with these phones but I'm not convinced this can't be fixed at home yet!
Thanks in advance for any help.
Some extra info:
fastboot getvar all
(bootloader) product: bullhead
(bootloader) off-mode-charge: 1
(bootloader) max-download-size: 0x20000000
(bootloader) battery-soc-ok: yes
(bootloader) battery-voltage: 4017mV
(bootloader) version-hardware: rev_1.0
(bootloader) version-baseband: M8994F-2.6.36.2.20
(bootloader) version-bootloader: BHZ11h
(bootloader) variant: bullhead LGH791 32GB
(bootloader) serialno: (hide)
(bootloader) kernel: lk
(bootloader) secure-boot: yes
(bootloader) partition-type:bootloader: emmc
(bootloader) partition-size:bootloader: 0xa80000
(bootloader) partition-type:boot: emmc
(bootloader) partition-size:boot: 0x2000000
(bootloader) partition-type:recovery: emmc
(bootloader) partition-size:recovery: 0x2000000
(bootloader) partition-type:system: ext4
(bootloader) partition-size:system: 0xc0000000
(bootloader) partition-type:userdata: ext4
(bootloader) partition-size:userdata: 0x65a3fb800
(bootloader) partition-type:cache: ext4
(bootloader) partition-size:cache: 0x6000000
(bootloader) partition-type:vendor: ext4
(bootloader) partition-size:vendor: 0xf800000
(bootloader) unlocked: no

mikeyrory said:
Hi all,
Sorry if this thread is in the wrong area.
I have in my possession a Nexus 5X which is stuck in a boot loop. I don't think it's a case of the power button being held down because the phone behaves differently depending on whether I hold the power button down or not.
I can boot into bootloader/fastboot mode which is locked. I have the standard options to Start/Restart bootloader/Recovery mode/Power off. If I try to get into recovery mode from here, the phone enters "download mode" for a short amount of time. After that, the bootloop begins again and I can only get the phone back to bootloader at best.
If I try to use the comment fastboot oem unlock I will get the message (remote: oem unlock is not allowed). I believe this is because don't have USB debugging/developer options enabled. I can't turn the phone on to enable this.
I have tried using Nexus Root Toolkit to unlock the bootloader (using the Flash Stock + Unroot and Soft-Bricked/Bootloop option) and everything seems to run fine until it restarts the phone. This triggers the boot loop again and the Nexus Root Toolkit hangs "waiting for phone..." after previously having been able to detect it.
I've tried using WinDroid Toolkit v3.1 also to unlock the bootloader without success.
Quite simply, is it possible to unlock the bootloader while the phone is in this state? I know this is a common problem with these phones but I'm not convinced this can't be fixed at home yet!
Thanks in advance for any help.
Some extra info:
fastboot getvar all
(bootloader) product: bullhead
(bootloader) off-mode-charge: 1
(bootloader) max-download-size: 0x20000000
(bootloader) battery-soc-ok: yes
(bootloader) battery-voltage: 4017mV
(bootloader) version-hardware: rev_1.0
(bootloader) version-baseband: M8994F-2.6.36.2.20
(bootloader) version-bootloader: BHZ11h
(bootloader) variant: bullhead LGH791 32GB
(bootloader) serialno: (hide)
(bootloader) kernel: lk
(bootloader) secure-boot: yes
(bootloader) partition-type:bootloader: emmc
(bootloader) partition-size:bootloader: 0xa80000
(bootloader) partition-type:boot: emmc
(bootloader) partition-size:boot: 0x2000000
(bootloader) partition-type:recovery: emmc
(bootloader) partition-size:recovery: 0x2000000
(bootloader) partition-type:system: ext4
(bootloader) partition-size:system: 0xc0000000
(bootloader) partition-type:userdata: ext4
(bootloader) partition-size:userdata: 0x65a3fb800
(bootloader) partition-type:cache: ext4
(bootloader) partition-size:cache: 0x6000000
(bootloader) partition-type:vendor: ext4
(bootloader) partition-size:vendor: 0xf800000
(bootloader) unlocked: no
Click to expand...
Click to collapse
Hello and welcome to xda-assist,
please refer to the device specific forum, especially the help section could be interesting to you..
https://forum.xda-developers.com/nexus-5x/help
Good luck

Pixel bricked overnight?

Alright everyone, I need XDAs collective wisdom to help me out on this one. I have a 128gb Verizon Google Pixel. I unlocked the bootloader early on, but I only ever installed Google official builds. I recently clean installed Oreo and it had been working great for the most part. The other morning I wake up with my phone on a distorted version of the bootloader screen, with half of the image and text going past the edge of the screen and onto the opposite side. It will not boot into android, will sometimes show Google logo before showing distorted bootloader screen again. I can load it into the normal bootloader but I have gone through every troubleshooting step I can find. I cannot flash ANYTHING, cannot relock bootloader (gives me data wipe message then reboots and goes to distorted image again. still shows unlocked in bootloader mode).
When I type in "fastboot getvar all" I get this:
fastboot getvar all
(bootloader) version:0.5
(bootloader) hw-revisionVT
(bootloader) vzwisLTE:
(bootloader) vzwmid:AOSP on msm8996
(bootloader) mid:G-2PW4100
(bootloader) version-main:1.0.0.33
(bootloader) imei:352531083644268
(bootloader) ramdump-mode:false
(bootloader) boot-mode:FASTBOOT
(bootloader) has-slot:radio:yes
(bootloader) has-slot:bootloader:yes
(bootloader) has-slot:reserve5:no
(bootloader) has-slot:devinfo:no
(bootloader) has-slot:fsg:no
(bootloader) has-slot:mfg:no
(bootloader) has-slot:board_info:no
(bootloader) has-slot:reserve4:no
(bootloader) has-slot:metadata:no
(bootloader) has-slotg2fs:no
(bootloader) has-slotg1fs:no
(bootloader) has-slot:ramdump:no
(bootloader) has-slot:frp:no
(bootloader) has-slot:reserve3:no
(bootloader) has-slot:cdt:no
(bootloader) has-slot:ddr:no
(bootloader) has-slot:modemst2:no
(bootloader) has-slot:modemst1:no
(bootloader) has-slot:fsc:no
(bootloader) has-slot:dip:no
(bootloader) has-slot:dpo:no
(bootloader) has-slot:devinfobak:no
(bootloader) has-slot:sec:no
(bootloader) has-slotersist:no
(bootloader) has-slot:ssd:no
(bootloader) has-slot:misc:no
(bootloader) has-slot:xbl:yes
(bootloader) has-slot:reserve0:no
(bootloader) has-slot:userdata:no
(bootloader) has-slot:system:yes
(bootloader) has-slot:vendor:yes
(bootloader) has-slot:apdp:yes
(bootloader) has-slot:msadp:yes
(bootloader) has-slot:modem:yes
(bootloader) has-slot:devcfg:yes
(bootloader) has-slot:hosd:yes
(bootloader) has-slot:boot:yes
(bootloader) has-slot:aboot:yes
(bootloader) has-slot:cmnlib64:yes
(bootloader) has-slot:cmnlib32:yes
(bootloader) has-slot:hyp:yes
(bootloader) has-slotmic:yes
(bootloader) has-slot:rpm:yes
(bootloader) has-slot:tz:yes
(bootloader) has-slot:keymaster:yes
(bootloader) has-slot:bootlocker:yes
(bootloader) slot-count:2
(bootloader) current-slot:b
(bootloader) slot-retry-count:b:2
(bootloader) slot-unbootable:b:no
(bootloader) slot-successful:b:yes
(bootloader) slot-retry-count:a:2
(bootloader) slot-unbootable:a:no
(bootloader) slot-successful:a:yes
(bootloader) battery-soc-ok:yes
(bootloader) battery-voltage:3595000
(bootloader) variant:US
(bootloader) secure:no
(bootloader) unlocked:yes
(bootloader) version-baseband:N/A
(bootloader) version-bootloader:N/A
(bootloader) off-mode-charge:1
(bootloader) charger-screen-enabled:1
(bootloader) max-download-size: 0x20000000
(bootloader) partition-type:userdata:ext4
(bootloader) partition-size:userdata: 0x1c8d800000
(bootloader) partition-type:system_b:ext4
(bootloader) partition-size:system_b: 0x80000000
(bootloader) partition-type:system_a:ext4
(bootloader) partition-size:system_a: 0x80000000
(bootloader) partition-type:vendor_b:ext4
(bootloader) partition-size:vendor_b: 0x12c00000
(bootloader) partition-type:vendor_a:ext4
(bootloader) partition-size:vendor_a: 0x12c00000
(bootloader) partition-type:boot_b:raw
(bootloader) partition-size:boot_b: 0x2000000
(bootloader) partition-type:boot_a:raw
(bootloader) partition-size:boot_a: 0x2000000
(bootloader) serialno:FA6C90302723
(bootloader) kernel:lk
(bootloader) product:sailfish
all:
finished. total time: 2.301s
Any help would be appreciated. If you have things for me to try, I'd be happy to try them

tychastain said:
Alright everyone, I need XDAs collective wisdom to help me out on this one. I have a 128gb Verizon Google Pixel. I unlocked the bootloader early on, but I only ever installed Google official builds. I recently clean installed Oreo and it had been working great for the most part. The other morning I wake up with my phone on a distorted version of the bootloader screen, with half of the image and text going past the edge of the screen and onto the opposite side. It will not boot into android, will sometimes show Google logo before showing distorted bootloader screen again. I can load it into the normal bootloader but I have gone through every troubleshooting step I can find. I cannot flash ANYTHING, cannot relock bootloader (gives me data wipe message then reboots and goes to distorted image again. still shows unlocked in bootloader mode).
When I type in "fastboot getvar all" I get this:
fastboot getvar all
(bootloader) version:0.5
(bootloader) hw-revisionVT
(bootloader) vzwisLTE:
(bootloader) vzwmid:AOSP on msm8996
(bootloader) mid:G-2PW4100
(bootloader) version-main:1.0.0.33
(bootloader) imei:352531083644268
(bootloader) ramdump-mode:false
(bootloader) boot-mode:FASTBOOT
(bootloader) has-slot:radio:yes
(bootloader) has-slot:bootloader:yes
(bootloader) has-slot:reserve5:no
(bootloader) has-slot:devinfo:no
(bootloader) has-slot:fsg:no
(bootloader) has-slot:mfg:no
(bootloader) has-slot:board_info:no
(bootloader) has-slot:reserve4:no
(bootloader) has-slot:metadata:no
(bootloader) has-slotg2fs:no
(bootloader) has-slotg1fs:no
(bootloader) has-slot:ramdump:no
(bootloader) has-slot:frp:no
(bootloader) has-slot:reserve3:no
(bootloader) has-slot:cdt:no
(bootloader) has-slot:ddr:no
(bootloader) has-slot:modemst2:no
(bootloader) has-slot:modemst1:no
(bootloader) has-slot:fsc:no
(bootloader) has-slot:dip:no
(bootloader) has-slot:dpo:no
(bootloader) has-slot:devinfobak:no
(bootloader) has-slot:sec:no
(bootloader) has-slotersist:no
(bootloader) has-slot:ssd:no
(bootloader) has-slot:misc:no
(bootloader) has-slot:xbl:yes
(bootloader) has-slot:reserve0:no
(bootloader) has-slot:userdata:no
(bootloader) has-slot:system:yes
(bootloader) has-slot:vendor:yes
(bootloader) has-slot:apdp:yes
(bootloader) has-slot:msadp:yes
(bootloader) has-slot:modem:yes
(bootloader) has-slot:devcfg:yes
(bootloader) has-slot:hosd:yes
(bootloader) has-slot:boot:yes
(bootloader) has-slot:aboot:yes
(bootloader) has-slot:cmnlib64:yes
(bootloader) has-slot:cmnlib32:yes
(bootloader) has-slot:hyp:yes
(bootloader) has-slotmic:yes
(bootloader) has-slot:rpm:yes
(bootloader) has-slot:tz:yes
(bootloader) has-slot:keymaster:yes
(bootloader) has-slot:bootlocker:yes
(bootloader) slot-count:2
(bootloader) current-slot:b
(bootloader) slot-retry-count:b:2
(bootloader) slot-unbootable:b:no
(bootloader) slot-successful:b:yes
(bootloader) slot-retry-count:a:2
(bootloader) slot-unbootable:a:no
(bootloader) slot-successful:a:yes
(bootloader) battery-soc-ok:yes
(bootloader) battery-voltage:3595000
(bootloader) variant:US
(bootloader) secure:no
(bootloader) unlocked:yes
(bootloader) version-baseband:N/A
(bootloader) version-bootloader:N/A
(bootloader) off-mode-charge:1
(bootloader) charger-screen-enabled:1
(bootloader) max-download-size: 0x20000000
(bootloader) partition-type:userdata:ext4
(bootloader) partition-size:userdata: 0x1c8d800000
(bootloader) partition-type:system_b:ext4
(bootloader) partition-size:system_b: 0x80000000
(bootloader) partition-type:system_a:ext4
(bootloader) partition-size:system_a: 0x80000000
(bootloader) partition-type:vendor_b:ext4
(bootloader) partition-size:vendor_b: 0x12c00000
(bootloader) partition-type:vendor_a:ext4
(bootloader) partition-size:vendor_a: 0x12c00000
(bootloader) partition-type:boot_b:raw
(bootloader) partition-size:boot_b: 0x2000000
(bootloader) partition-type:boot_a:raw
(bootloader) partition-size:boot_a: 0x2000000
(bootloader) serialno:FA6C90302723
(bootloader) kernel:lk
(bootloader) product:sailfish
all:
finished. total time: 2.301s
Any help would be appreciated. If you have things for me to try, I'd be happy to try them
Click to expand...
Click to collapse
Will it let you fastboot reformat. Not sure what the exact Command is. Or maybe try fastboot continue. And do you have the most updated platform tools?

tychastain said:
Alright everyone, I need XDAs collective wisdom to help me out on this one. I have a 128gb Verizon Google Pixel. I unlocked the bootloader early on, but I only ever installed Google official builds. I recently clean installed Oreo and it had been working great for the most part. The other morning I wake up with my phone on a distorted version of the bootloader screen, with half of the image and text going past the edge of the screen and onto the opposite side. It will not boot into android, will sometimes show Google logo before showing distorted bootloader screen again. I can load it into the normal bootloader but I have gone through every troubleshooting step I can find. I cannot flash ANYTHING, cannot relock bootloader (gives me data wipe message then reboots and goes to distorted image again. still shows unlocked in bootloader mode).
When I type in "fastboot getvar all" I get this:
fastboot getvar all
(bootloader) version:0.5
(bootloader) hw-revisionVT
(bootloader) vzwisLTE:
(bootloader) vzwmid:AOSP on msm8996
(bootloader) mid:G-2PW4100
(bootloader) version-main:1.0.0.33
(bootloader) imei:352531083644268
(bootloader) ramdump-mode:false
(bootloader) boot-mode:FASTBOOT
(bootloader) has-slot:radio:yes
(bootloader) has-slot:bootloader:yes
(bootloader) has-slot:reserve5:no
(bootloader) has-slot:devinfo:no
(bootloader) has-slot:fsg:no
(bootloader) has-slot:mfg:no
(bootloader) has-slot:board_info:no
(bootloader) has-slot:reserve4:no
(bootloader) has-slot:metadata:no
(bootloader) has-slotg2fs:no
(bootloader) has-slotg1fs:no
(bootloader) has-slot:ramdump:no
(bootloader) has-slot:frp:no
(bootloader) has-slot:reserve3:no
(bootloader) has-slot:cdt:no
(bootloader) has-slot:ddr:no
(bootloader) has-slot:modemst2:no
(bootloader) has-slot:modemst1:no
(bootloader) has-slot:fsc:no
(bootloader) has-slot:dip:no
(bootloader) has-slot:dpo:no
(bootloader) has-slot:devinfobak:no
(bootloader) has-slot:sec:no
(bootloader) has-slotersist:no
(bootloader) has-slot:ssd:no
(bootloader) has-slot:misc:no
(bootloader) has-slot:xbl:yes
(bootloader) has-slot:reserve0:no
(bootloader) has-slot:userdata:no
(bootloader) has-slot:system:yes
(bootloader) has-slot:vendor:yes
(bootloader) has-slot:apdp:yes
(bootloader) has-slot:msadp:yes
(bootloader) has-slot:modem:yes
(bootloader) has-slot:devcfg:yes
(bootloader) has-slot:hosd:yes
(bootloader) has-slot:boot:yes
(bootloader) has-slot:aboot:yes
(bootloader) has-slot:cmnlib64:yes
(bootloader) has-slot:cmnlib32:yes
(bootloader) has-slot:hyp:yes
(bootloader) has-slotmic:yes
(bootloader) has-slot:rpm:yes
(bootloader) has-slot:tz:yes
(bootloader) has-slot:keymaster:yes
(bootloader) has-slot:bootlocker:yes
(bootloader) slot-count:2
(bootloader) current-slot:b
(bootloader) slot-retry-count:b:2
(bootloader) slot-unbootable:b:no
(bootloader) slot-successful:b:yes
(bootloader) slot-retry-count:a:2
(bootloader) slot-unbootable:a:no
(bootloader) slot-successful:a:yes
(bootloader) battery-soc-ok:yes
(bootloader) battery-voltage:3595000
(bootloader) variant:US
(bootloader) secure:no
(bootloader) unlocked:yes
(bootloader) version-baseband:N/A
(bootloader) version-bootloader:N/A
(bootloader) off-mode-charge:1
(bootloader) charger-screen-enabled:1
(bootloader) max-download-size: 0x20000000
(bootloader) partition-type:userdata:ext4
(bootloader) partition-size:userdata: 0x1c8d800000
(bootloader) partition-type:system_b:ext4
(bootloader) partition-size:system_b: 0x80000000
(bootloader) partition-type:system_a:ext4
(bootloader) partition-size:system_a: 0x80000000
(bootloader) partition-type:vendor_b:ext4
(bootloader) partition-size:vendor_b: 0x12c00000
(bootloader) partition-type:vendor_a:ext4
(bootloader) partition-size:vendor_a: 0x12c00000
(bootloader) partition-type:boot_b:raw
(bootloader) partition-size:boot_b: 0x2000000
(bootloader) partition-type:boot_a:raw
(bootloader) partition-size:boot_a: 0x2000000
(bootloader) serialno:FA6C90302723
(bootloader) kernel:lk
(bootloader) product:sailfish
all:
finished. total time: 2.301s
Any help would be appreciated. If you have things for me to try, I'd be happy to try them
Click to expand...
Click to collapse
YES THIS HAPPENED TO ME TOO!! JUST YESTERDAY!!! I already applied for a replacement phone and paid the 78$ since mine has some small amounts of cosmetic scars here and there so i've already paid for the replacement. But yes i had the EXACT same issue.

i love how this is an issue multiple people are now reporting and no one wants to continue the conversation to find a solution.

Happened to me twice in a span of a week. All within a few days of updating to Oreo. Details in another thread. Only choice was to RMA to Google.
https://forum.xda-developers.com/pixel/help/google-pixel-bricked-oreo-twice-ideas-t3671302

any solution to this issue yet? i think i have my pixel with USB debugging enabled because I tend to enable that by default any time i start fresh with a device, so i should have USB debugging enabled already. But would flashing stock image really work in this case? all I have access to is the bootloader menu and nothing else. any attempt to boot into recovery is met with a failed to boot into recovery message. I have no clue what to do, I've already requested a standard exchange with Google for a brand new device but that means sending in my device first before receiving my new device and blarg that's just frustrating to do at this point. However if others are saying flashing lead to it bricking AGAIN either way it just seems a lost cause to try and fix my phone myself right?

silvernirvash said:
any solution to this issue yet? i think i have my pixel with USB debugging enabled because I tend to enable that by default any time i start fresh with a device, so i should have USB debugging enabled already. But would flashing stock image really work in this case? all I have access to is the bootloader menu and nothing else. any attempt to boot into recovery is met with a failed to boot into recovery message. I have no clue what to do, I've already requested a standard exchange with Google for a brand new device but that means sending in my device first before receiving my new device and blarg that's just frustrating to do at this point. However if others are saying flashing lead to it bricking AGAIN either way it just seems a lost cause to try and fix my phone myself right?
Click to expand...
Click to collapse
Well if it's not working and you are actually able to flash it via fastboot then I'd give that a go before sending it back. It cant hurt anything since it's already not functioning. Try flashing Stock Oreo and try flashing Latest Nougat too if needed.
Is there anything that you guys have done to your phones recently other than update to Oreo? Unlock Bootloader? Flash Twrp? Flash any other rom? Custom Kernel? Flash custom mod?...I think there's lack of discussion here because there's really not enough info to determine anything. What type of phone is it (which variant)? How old it is? How you acquired it? Any bit of info because you never know what the common factor may be in these freak scenarios.

My Pixel XL (128gb) had never been unlocked or rooted; completely stock. Rarely had a random reboot until updating to Android 8. Then it was reboot-city from there. I performed a factory reset & that helped for about 3 days or so, then back to rebooting 3-4 times a day up until about a week and half in, when it finally shut off for good. Was just streaming youtube to my tv via chromecast when I noticed the screen was still on & had frozen up. Did a hard reboot but it wouldn't come back on. Tried to boot up into fastboot mode but no dice. Ended up calling Google tech support. They said it was a software issue & started the RMA process.
Received my replacement (a stinking refurb...) a couple days later & immediately disabled the system update notifications. Gonna stay on 7 for awhile & monitor the message boards & Google Issue Tracker forum until I see it's fixed, then I'll update. But at the moment, the October monthly security update has pushed out recently and was supposed to fix things but hasn't, from what I'm seeing. Maybe next month's update?? (Sigh...)

Weird. Something like this just happened to me this morning. I've never unlocked the bootloader on my Google Store purchased 128 GB XL. I plugged it in to charge last night as I always do, and when I woke up this morning, it was dead.
BL and Baseband show up as N/A. Others have reported this same issue. Since my bootloader is locked, I can't do anything with fastboot. Entering recovery gives an error. I contacted Google and was set up with a replacement.

it seems everyone is having the exact same issue at this point. thanks google for ****ing it up.

silvernirvash said:
it seems everyone is having the exact same issue at this point. thanks google for ****ing it up.
Click to expand...
Click to collapse
There's another thread from January of this year when this happened. Whatever the issue is, it's not new.
https://forum.xda-developers.com/pixel-xl/help/pixel-xl-bricked-bootloader-n-baseband-n-t3537379

I did a clean install of Android and no issues so far. Again I'm stock and locked bootloader

hp13 said:
I did a clean install of Android and no issues so far. Again I'm stock and locked bootloader
Click to expand...
Click to collapse
Was your Pixel bricked and you were able to recover it?

I had the same problem. It was working, now it is not.

This has happened to me 3 times now. Hoping this time I don't have issues as they finally sent me a brand new pixel as opposed to refurb.

Bricked pixel 2 because of locked bootloader?

I'm trying to keep my problem short. I had unlocked my bootloader for years now and I know the whole subject quite well. I decided to lock my bootloader and put everything back.
Because I was at the official beta of android 9 I decided to flash a factory image of the latest version.
Also the start in the new environment worked out. Therefore I locked the bootloader in the OS and did the same in the bootloader via fastboot.
Now I have a locked bootloader which I cannot unlock due to the os settings.
At boot I get the error: Slot Unbootable: Load Error.
fastboot continue ends in the same error
I don't recover from the same error either.
I cannot change boot slot because of the locked recovery.
fastboot works.
adb sideload not because I only hang in the bootloader.
Do I only have some chance to lock the bootloader or to cause some kind of factory reset?
fastboot getvar all tells me that slot a is unbootable...yeah i know. however b is not. So how can i tell my bootloader to start from B????
I've read a lot now but I'm at a loss. I am grateful for any help or advice.
I hope I don't have to take care of an RMA =(
I hope i missed some way to bypass this locked bootloader. im going crazy
Pleaaaaaase need help =( i spend paypal-beer for help
Here some more infos:
Code:
fastboot getvar all
(bootloader) avb_err:0(0)
(bootloader) is_avb_critical_error:no
(bootloader) have_oem_lock_id:yes
(bootloader) avb_stored_rollback_indexes:
(bootloader) avb_user_settable_key_set:no
(bootloader) avb_version:1.0.0
(bootloader) mid:G011A
(bootloader) version-main:
(bootloader) imei:***censored***
(bootloader) boot-mode:FASTBOOT
(bootloader) logical-block-size:0x1000
(bootloader) erase-block-size:0x1000000
(bootloader) unlocked:no
(bootloader) off-mode-charge:1
(bootloader) charger-screen-enabled:1
(bootloader) battery-soc-ok:yes
(bootloader) battery-voltage:4111
(bootloader) version-baseband:g8998-00253-1809191716
(bootloader) version-bootloader:mw8998-002.0073.02
(bootloader) variant:
(bootloader) partition-type:userdata:ext4
(bootloader) partition-size:userdata: 0xD49BFB000
(bootloader) partition-type:vendor_b:ext4
(bootloader) partition-size:vendor_b: 0x1F400000
(bootloader) partition-type:vendor_a:ext4
(bootloader) partition-size:vendor_a: 0x1F400000
(bootloader) partition-type:system_b:ext4
(bootloader) partition-size:system_b: 0xA0000000
(bootloader) partition-type:system_a:ext4
(bootloader) partition-size:system_a: 0xA0000000
(bootloader) partition-type:boot_b:raw
(bootloader) partition-size:boot_b: 0x2000000
(bootloader) partition-type:boot_a:raw
(bootloader) partition-size:boot_a: 0x2000000
(bootloader) has-slot:radio:yes
(bootloader) has-slot:bootloader:yes
(bootloader) has-slot:vendor:yes
(bootloader) has-slot:modem:yes
(bootloader) has-slot:system:yes
(bootloader) has-slot:vbmeta:yes
(bootloader) has-slot:dtbo:yes
(bootloader) current-slot:a
(bootloader) has-slot:boot:yes
(bootloader) slot-retry-count:b:7
(bootloader) slot-unbootable:b:no
(bootloader) slot-successful:b:no
(bootloader) slot-retry-count:a:6
(bootloader) slot-unbootable:a:yes
(bootloader) slot-successful:a:yes
(bootloader) slot-count:2
(bootloader) cid:00000000
(bootloader) secure:yes
(bootloader) serialno:FA7C61A00757
(bootloader) hw-revision:MP1
(bootloader) product:walleye
(bootloader) max-download-size:0x20000000
(bootloader) kernel:uefi
all:
finished. total time: 0.090s

Did you ever resolve this? The December update doesn't play well with bootloader enumeration. This thread here should help. As always, there's never a guarantee of data preservation, so unless you have a Titanium Backup, i'd manually backup the really important stuff. Hope it helps!

D3RP_ said:
Did you ever resolve this? The December update doesn't play well with bootloader enumeration. This thread here should help. As always, there's never a guarantee of data preservation, so unless you have a Titanium Backup, i'd manually backup the really important stuff. Hope it helps!
Click to expand...
Click to collapse
Your post wont work for me because i cannot unlock my bootloader as a result of the bricked boot slot. So i cant flash images or flash ota's . But Thanks!!!
I couldn't solve the problem, but I could at least figure out what it is.
Never ever relock the bootloader in the os again until you are 100% sure. In my case i was sure but i didnt recognized that one boot slot is unable to start. that would have been verifiable with fastboot getvar all (see first post).
In the end i am stucked now with a hard bricked phone. I contacted google and at this moment my mobile phone is at google for an RMA. I hope it doesn't take too long.
And yes in my case the December update in combination with my (wrong) relock hard bricked my phone.
Never ever relock the bootloader in the os

Solved for me
I had the same problem with the bootloader locked but I solved it unlocking it "fastboot flashing unlock" then you have flashing the factory image

Camiloecu said:
I had the same problem with the bootloader locked but I solved it unlocking it "fastboot flashing unlock" then you have flashing the factory image
Click to expand...
Click to collapse
If the bootloader shows 'Device State: locked' this command will return an error: 'Flashing Unlock is not allowed'.

Question Rescue OnePlus 9 - TWPR recovery boot loop

Hi guys,
I have a OnePlus 9 5G that was running LineageOS 19. Due to some water damage on the screen, the phone was not used for 6 months. When finally getting the replacement screen I found out that I forgot the pattern (5 x 5 grid). I'm apparently no longer logged into the device via Google, so I can't unlock from there, though it does show up on the activity history.
I tried following a couple of guides online but it seems my device is encrypted and the files are not accessible (like over-writing LineageOS Recovery with TWPR)
I do have adb access and fastboot, USD-Debugging and can still enter fastboot. But I "bricked" the phone (trying to install TWPR and other things to try to get into su mode or find some other way of extracting the media on the device) to the point where I can now only access fastboot reliably and not boot normally anymore.
In fastboot I get
Code:
Product Name - lahaina
Secure Boot - yes
Device State - unlocked
Can anyone tell me:
1. How can I fix the boot partion to boot into the OS again (and keep trying my lock pattern until I find it)
2. Fix the TWPR (is that possible?) and see if I can access the photos that way
3. Best of all: Remove the lock pattern with su via adb?!
Let me know if I missed any information that's critical to help

RobSteward said:
Hi guys,
I have a OnePlus 9 5G that was running LineageOS 19. Due to some water damage on the screen, the phone was not used for 6 months. When finally getting the replacement screen I found out that I forgot the pattern (5 x 5 grid). I'm apparently no longer logged into the device via Google, so I can't unlock from there, though it does show up on the activity history.
I tried following a couple of guides online but it seems my device is encrypted and the files are not accessible (like over-writing LineageOS Recovery with TWPR)
I do have adb access and fastboot, USD-Debugging and can still enter fastboot. But I "bricked" the phone (trying to install TWPR and other things to try to get into su mode or find some other way of extracting the media on the device) to the point where I can now only access fastboot reliably and not boot normally anymore.
In fastboot I get
Code:
Product Name - lahaina
Secure Boot - yes
Device State - unlocked
Can anyone tell me:
1. How can I fix the boot partion to boot into the OS again (and keep trying my lock pattern until I find it)
2. Fix the TWPR (is that possible?) and see if I can access the photos that way
3. Best of all: Remove the lock pattern with su via adb?!
Let me know if I missed any information that's critical to help
Click to expand...
Click to collapse
I followed the MSM tool guide pinned at the top of the op9 thread. Works great, But it means you lose everything .. hope you find a fix. But last resort is always MSM tool.

Vmo x said:
I followed the MSM tool guide pinned at the top of the op9 thread. Works great, But it means you lose everything .. hope you find a fix. But last resort is always MSM tool.
Click to expand...
Click to collapse
Thanks for chipping in @Vmo x, but that's against the point of my post I know how to hard reset the device, if I'm okay losing the data. I was wondering if, given that I have all the other access (Fastboot, fastootd, adb and root), I would be able to find a way to break the pattern lock

No actually. There's no way you can bypass the pattern lock/PIN/password without having to reset the data (userdata) if you have forgotten pattern/PIN/password. It is encrypted, and no TWRP (or anything) can help you decrypt it if you don't know the password. That's the reason phones data partition is encrypted in the first place. You can however format the data partition from TWRP and get your system back up like factory reset; but given your current situation, I don't know if that would even be possible now. Looks to me you would need to go the MSM route.

Have you tried flashing LOS back on to your phone? I have not dived into Custom ROMs yet on the OP 9 but with previous phones I have, I could flash the Custom ROM back on to restore all of the imgs allowing it to boot.
I am just throwing ideas without really knowing if it would help.

Z-Blade said:
Have you tried flashing LOS back on to your phone? I have not dived into Custom ROMs yet on the OP 9 but with previous phones I have, I could flash the Custom ROM back on to restore all of the imgs allowing it to boot.
I am just throwing ideas without really knowing if it would help.
Click to expand...
Click to collapse
I have managed to overwrite this and get the LineageOS recovery and most recent LineageOS working again. I had to basically "update" the phone. I can input patterns but it locks for 1 minute after every attempt.
Are there any people/services I can contact that can brute force this? Even just getting a copy of the encrypted storage would work for me, then I can run this brute force for some years somewhere and hope I find it. Just goes a bit beyond what I'm able to do with my limited knowledge.

So you have flashed LineageOS without wiping data? And now it boots up successfully to the lockscreen? I don't think that can work.

Well,
I followed the LineageOS install instructions to the letter. See below for proof. I'm obviously not sure if it completely reset and added a random pattern . But if it would have reset the phone I would have expected a set up wizard instead of a lock screen. Additionally, the phone does accept my fingerprint (which would also have been wiped). The problem is just that the lock screen triggers on reboot.
I'm guessing the fixing update worked because I already had a working LineageOS installed without breaking changes (I think the original install was 19.X). Fixing recovery seems to be something that's independent from the OS, so that should not be a surprise to be fixed.
Here's the full sequence that worked:
Code:
PS C:\Users\XXX\downloads\mobilerecovery\20230312\oneplus9> ls
Directory: C:\Users\XXX\downloads\mobilerecovery\20230312\oneplus9
Mode LastWriteTime Length Name
---- ------------- ------ ----
-a---- 2/4/2023 4:47 AM 201326592 boot-oos12-firmware.img
-a---- 3/12/2023 7:06 PM 1395646798 lineage-20.0-20230312-nightly-lemonade-signed.zip
-a---- 3/12/2023 7:02 PM 25165824 lineage-20.0-20230312-nightly-lemonade-signed_dtbo.img
-a---- 3/12/2023 7:02 PM 201326592 lineage-20.0-20230312-nightly-lemonade-signed_vendor_boot.img
-a---- 3/12/2023 6:43 PM 201326592 magisk_patched-lineage-20.0-20230312-nightly-lemonade-signed_boot.img
-a---- 2/4/2023 4:50 AM 37719266 ramdisk-recovery.img
-a---- 2/4/2023 4:52 AM 33714989 twrp-installer-3.7.0-12.1-4-lemonadep.zip
PS C:\Users\XXX\downloads\mobilerecovery\20230312\oneplus9> fastboot oem unlock
FAILED (remote: ' Device already : unlocked!')
fastboot: error: Command failed
PS C:\Users\XXX\downloads\mobilerecovery\20230312\oneplus9> fastboot flash dtbo lineage-20.0-20230312-nightly-lemonade-signed_dtbo.img
Sending 'dtbo' (24576 KB) OKAY [ 0.617s]
Writing 'dtbo' OKAY [ 0.066s]
Finished. Total time: 0.713s
PS C:\Users\XXX\downloads\mobilerecovery\20230312\oneplus9> fastboot flash vendor_boot lineage-20.0-20230312-nightly-lemonade-signed_vendor_boot.img
Sending 'vendor_boot' (196608 KB) OKAY [ 4.911s]
Writing 'vendor_boot' OKAY [ 0.594s]
Finished. Total time: 5.540s
PS C:\Users\XXX\downloads\mobilerecovery\20230312\oneplus9> fastboot getvar all
(bootloader) parallel-download-flash:yes
(bootloader) hw-revision:20001
(bootloader) unlocked:yes
(bootloader) off-mode-charge:1
(bootloader) charger-screen-enabled:1
(bootloader) battery-soc-ok:yes
(bootloader) battery-voltage:8806
(bootloader) version-baseband:
(bootloader) version-bootloader:
(bootloader) erase-block-size: 0x1000
(bootloader) logical-block-size: 0x1000
(bootloader) variant:SM_ UFS
(bootloader) partition-type:oplusreserve1:raw
(bootloader) partition-size:oplusreserve1: 0x800000
(bootloader) partition-type:fsc:raw
(bootloader) partition-size:fsc: 0x20000
(bootloader) partition-type:fsg:raw
(bootloader) partition-size:fsg: 0x300000
(bootloader) partition-type:modemst2:raw
(bootloader) partition-size:modemst2: 0x300000
(bootloader) partition-type:modemst1:raw
(bootloader) partition-size:modemst1: 0x300000
(bootloader) partition-type:ALIGN_TO_128K_2:raw
(bootloader) partition-size:ALIGN_TO_128K_2: 0x1A000
(bootloader) partition-type:hyp_log:raw
(bootloader) partition-size:hyp_log: 0xFD0000
(bootloader) partition-type:qsee_log:raw
(bootloader) partition-size:qsee_log: 0xFD0000
(bootloader) partition-type:android_log:raw
(bootloader) partition-size:android_log: 0xFD0000
(bootloader) partition-type:kernel_log:raw
(bootloader) partition-size:kernel_log: 0xFD0000
(bootloader) partition-type:abl_log:raw
(bootloader) partition-size:abl_log: 0xFD0000
(bootloader) partition-type:apdp_full:raw
(bootloader) partition-size:apdp_full: 0x40000
(bootloader) partition-type:rtice:raw
(bootloader) partition-size:rtice: 0x80000
(bootloader) partition-type:spunvm:raw
(bootloader) partition-size:spunvm: 0x2000000
(bootloader) partition-type:tzsc:raw
(bootloader) partition-size:tzsc: 0x20000
(bootloader) partition-type:connsec:raw
(bootloader) partition-size:connsec: 0x20000
(bootloader) partition-type:mdcompress:raw
(bootloader) partition-size:mdcompress: 0x1400000
(bootloader) partition-type:vm-data:raw
(bootloader) partition-size:vm-data: 0x20A4000
(bootloader) partition-type:secdata:raw
(bootloader) partition-size:secdata: 0x7000
(bootloader) partition-type:uefivarstore:raw
(bootloader) partition-size:uefivarstore: 0x80000
(bootloader) partition-type:storsec:raw
(bootloader) partition-size:storsec: 0x20000
(bootloader) partition-type:modemdump:raw
(bootloader) partition-size:modemdump: 0x12C00000
(bootloader) partition-type:logdump:raw
(bootloader) partition-size:logdump: 0x4000000
(bootloader) partition-type:logfs:raw
(bootloader) partition-size:logfs: 0x800000
(bootloader) partition-type:limits-cdsp:raw
(bootloader) partition-size:limits-cdsp: 0x1000
(bootloader) partition-type:limits:raw
(bootloader) partition-size:limits: 0x1000
(bootloader) partition-type:apdp:raw
(bootloader) partition-size:apdp: 0x40000
(bootloader) partition-type:dip:raw
(bootloader) partition-size:dip: 0x100000
(bootloader) partition-type:devinfo:raw
(bootloader) partition-size:devinfo: 0x1000
(bootloader) partition-type:oplus_sec_b:raw
(bootloader) partition-size:oplus_sec_b: 0xA00000
(bootloader) partition-type:splash_b:raw
(bootloader) partition-size:splash_b: 0x20A4000
(bootloader) partition-type:qweslicstore_b:raw
(bootloader) partition-size:qweslicstore_b: 0x40000
(bootloader) partition-type:vendor_boot_b:raw
(bootloader) partition-size:vendor_boot_b: 0xC000000
(bootloader) partition-type:featenabler_b:raw
(bootloader) partition-size:featenabler_b: 0x20000
(bootloader) partition-type:cpucp_b:raw
(bootloader) partition-size:cpucp_b: 0x100000
(bootloader) partition-type:multiimgoem_b:raw
(bootloader) partition-size:multiimgoem_b: 0x8000
(bootloader) partition-type:vm-bootsys_b:raw
(bootloader) partition-size:vm-bootsys_b: 0x10625000
(bootloader) partition-type:shrm_b:raw
(bootloader) partition-size:shrm_b: 0x20000
(bootloader) partition-type:imagefv_b:raw
(bootloader) partition-size:imagefv_b: 0x200000
(bootloader) partition-type:uefisecapp_b:raw
(bootloader) partition-size:uefisecapp_b: 0x200000
(bootloader) partition-type:dtbo_b:raw
(bootloader) partition-size:dtbo_b: 0x1800000
(bootloader) partition-type:vbmeta_b:raw
(bootloader) partition-size:vbmeta_b: 0x10000
(bootloader) partition-type:qupfw_b:raw
(bootloader) partition-size:qupfw_b: 0x14000
(bootloader) partition-type:devcfg_b:raw
(bootloader) partition-size:devcfg_b: 0x20000
(bootloader) partition-type:boot_b:raw
(bootloader) partition-size:boot_b: 0xC000000
(bootloader) partition-type:keymaster_b:raw
(bootloader) partition-size:keymaster_b: 0x80000
(bootloader) partition-type:dsp_b:raw
(bootloader) partition-size:dsp_b: 0x4000000
(bootloader) partition-type:abl_b:raw
(bootloader) partition-size:abl_b: 0x800000
(bootloader) partition-type:mdtp_b:raw
(bootloader) partition-size:mdtp_b: 0x2000000
(bootloader) partition-type:mdtpsecapp_b:raw
(bootloader) partition-size:mdtpsecapp_b: 0x400000
(bootloader) partition-type:bluetooth_b:raw
(bootloader) partition-size:bluetooth_b: 0x200000
(bootloader) partition-type:modem_b:raw
(bootloader) partition-size:modem_b: 0x14A00000
(bootloader) partition-type:hyp_b:raw
(bootloader) partition-size:hyp_b: 0x800000
(bootloader) partition-type:tz_b:raw
(bootloader) partition-size:tz_b: 0x400000
(bootloader) partition-type:aop_b:raw
(bootloader) partition-size:aop_b: 0x80000
(bootloader) partition-type:oplus_sec_a:raw
(bootloader) partition-size:oplus_sec_a: 0xA00000
(bootloader) partition-type:splash_a:raw
(bootloader) partition-size:splash_a: 0x20A4000
(bootloader) partition-type:qweslicstore_a:raw
(bootloader) partition-size:qweslicstore_a: 0x40000
(bootloader) partition-type:qmcs:raw
(bootloader) partition-size:qmcs: 0x1E00000
(bootloader) partition-type:vendor_boot_a:raw
(bootloader) partition-size:vendor_boot_a: 0xC000000
(bootloader) partition-type:featenabler_a:raw
(bootloader) partition-size:featenabler_a: 0x20000
(bootloader) partition-type:cpucp_a:raw
(bootloader) partition-size:cpucp_a: 0x100000
(bootloader) partition-type:multiimgoem_a:raw
(bootloader) partition-size:multiimgoem_a: 0x8000
(bootloader) partition-type:vm-bootsys_a:raw
(bootloader) partition-size:vm-bootsys_a: 0x10625000
(bootloader) partition-type:shrm_a:raw
(bootloader) partition-size:shrm_a: 0x20000
(bootloader) partition-type:imagefv_a:raw
(bootloader) partition-size:imagefv_a: 0x200000
(bootloader) partition-type:uefisecapp_a:raw
(bootloader) partition-size:uefisecapp_a: 0x200000
(bootloader) partition-type:dtbo_a:raw
(bootloader) partition-size:dtbo_a: 0x1800000
(bootloader) partition-type:vbmeta_a:raw
(bootloader) partition-size:vbmeta_a: 0x10000
(bootloader) partition-type:qupfw_a:raw
(bootloader) partition-size:qupfw_a: 0x14000
(bootloader) partition-type:devcfg_a:raw
(bootloader) partition-size:devcfg_a: 0x20000
(bootloader) partition-type:boot_a:raw
(bootloader) partition-size:boot_a: 0xC000000
(bootloader) partition-type:keymaster_a:raw
(bootloader) partition-size:keymaster_a: 0x80000
(bootloader) partition-type:dsp_a:raw
(bootloader) partition-size:dsp_a: 0x4000000
(bootloader) partition-type:abl_a:raw
(bootloader) partition-size:abl_a: 0x800000
(bootloader) partition-type:mdtp_a:raw
(bootloader) partition-size:mdtp_a: 0x2000000
(bootloader) partition-type:mdtpsecapp_a:raw
(bootloader) partition-size:mdtpsecapp_a: 0x400000
(bootloader) partition-type:bluetooth_a:raw
(bootloader) partition-size:bluetooth_a: 0x200000
(bootloader) partition-type:modem_a:raw
(bootloader) partition-size:modem_a: 0x14A00000
(bootloader) partition-type:hyp_a:raw
(bootloader) partition-size:hyp_a: 0x800000
(bootloader) partition-type:tz_a:raw
(bootloader) partition-size:tz_a: 0x400000
(bootloader) partition-type:aop_a:raw
(bootloader) partition-size:aop_a: 0x80000
(bootloader) partition-type:DRIVER:raw
(bootloader) partition-size:DRIVER: 0x2000000
(bootloader) partition-type:oplusreserve5:raw
(bootloader) partition-size:oplusreserve5: 0x4000000
(bootloader) partition-type:oplusreserve4:raw
(bootloader) partition-size:oplusreserve4: 0x2000000
(bootloader) partition-type:oplusreserve3:raw
(bootloader) partition-size:oplusreserve3: 0x4000000
(bootloader) partition-type:oplusreserve2:raw
(bootloader) partition-size:oplusreserve2: 0x10000000
(bootloader) partition-type:engineering_cdt_b:raw
(bootloader) partition-size:engineering_cdt_b: 0x100000
(bootloader) partition-type:dinfo:raw
(bootloader) partition-size:dinfo: 0x4000
(bootloader) partition-type:ocdt:raw
(bootloader) partition-size:ocdt: 0x20000
(bootloader) partition-type:engineering_cdt_a:raw
(bootloader) partition-size:engineering_cdt_a: 0x100000
(bootloader) partition-type:ddr:raw
(bootloader) partition-size:ddr: 0x100000
(bootloader) partition-type:cdt:raw
(bootloader) partition-size:cdt: 0x20000
(bootloader) partition-type:ALIGN_TO_128K_1:raw
(bootloader) partition-size:ALIGN_TO_128K_1: 0x1A000
(bootloader) partition-type:xbl_config_b:raw
(bootloader) partition-size:xbl_config_b: 0x80000
(bootloader) partition-type:xbl_b:raw
(bootloader) partition-size:xbl_b: 0x600000
(bootloader) partition-type:xbl_config_a:raw
(bootloader) partition-size:xbl_config_a: 0x80000
(bootloader) partition-type:xbl_a:raw
(bootloader) partition-size:xbl_a: 0x600000
(bootloader) partition-type:userdata:f2fs
(bootloader) partition-size:userdata: 0x1986FB3000
(bootloader) partition-type:super:raw
(bootloader) partition-size:super: 0x29B000000
(bootloader) partition-type:rawdump:raw
(bootloader) partition-size:rawdump: 0x8000000
(bootloader) partition-type:metadata:ext4
(bootloader) partition-size:metadata: 0x1000000
(bootloader) partition-type:vbmeta_vendor_b:raw
(bootloader) partition-size:vbmeta_vendor_b: 0x10000
(bootloader) partition-type:vbmeta_vendor_a:raw
(bootloader) partition-size:vbmeta_vendor_a: 0x10000
(bootloader) partition-type:vbmeta_system_b:raw
(bootloader) partition-size:vbmeta_system_b: 0x10000
(bootloader) partition-type:vbmeta_system_a:raw
(bootloader) partition-size:vbmeta_system_a: 0x10000
(bootloader) partition-type:persist_bkp:raw
(bootloader) partition-size:persist_bkp: 0x2000000
(bootloader) partition-type:opluslog:raw
(bootloader) partition-size:opluslog: 0x10000000
(bootloader) partition-type:carrier:raw
(bootloader) partition-size:carrier: 0x4000000
(bootloader) partition-type:oplusstanvbk_b:raw
(bootloader) partition-size:oplusstanvbk_b: 0xA00000
(bootloader) partition-type:oplusstanvbk_a:raw
(bootloader) partition-size:oplusstanvbk_a: 0xA00000
(bootloader) partition-type:oplusdycnvbk:raw
(bootloader) partition-size:oplusdycnvbk: 0xA00000
(bootloader) partition-type:frp:raw
(bootloader) partition-size:frp: 0x80000
(bootloader) partition-type:keystore:raw
(bootloader) partition-type:misc:raw
(bootloader) partition-size:misc: 0x100000
(bootloader) partition-type:persist:raw
(bootloader) partition-size:persist: 0x2000000
(bootloader) partition-type:param:raw
(bootloader) partition-size:param: 0x800000
(bootloader) partition-type:ssd:raw
(bootloader) partition-size:ssd: 0x2000
(bootloader) has-slot:modem:yes
(bootloader) has-slot:system:no
(bootloader) current-slot:a
(bootloader) has-slot:boot:yes
(bootloader) slot-retry-count:b:0
(bootloader) slot-unbootable:b:yes
(bootloader) slot-successful:b:no
(bootloader) slot-retry-count:a:7
(bootloader) slot-unbootable:a:no
(bootloader) slot-successful:a:no
(bootloader) serialno:8ac546c0
(bootloader) product:lahaina
(bootloader) snapshot-update-status:snapshotted
(bootloader) is-userspace:no
(bootloader) max-download-size:805306368
(bootloader) kernel:uefi
all:
Finished. Total time: 0.507s
PS C:\Users\XXX\downloads\mobilerecovery\20230312\oneplus9> fastboot flash boot_a magisk_patched-lineage-20.0-20230312-nightly-lemonade-signed_boot.img
Sending 'boot_a' (196608 KB) OKAY [ 4.911s]
Writing 'boot_a' OKAY [ 0.581s]
Finished. Total time: 5.526s
## Rebooted phone to recovery
## In LineageOS Recovery (now showing Version 20.0 (20230312)) click "Apply Update"
PS C:\Users\XXX\downloads\mobilerecovery\20230312\oneplus9> adb sideload lineage-20.0-20230312-nightly-lemonade-signed.zip
Total xfer: 1.00x
## Rebooted phone to recovery
## In LineageOS Recovery (now showing Version 20.0 (20230312)) click "Apply Update"
PS C:\Users\XXX\downloads\mobilerecovery\20230312\oneplus9> cd .../..
PS C:\Users\XXX\downloads\mobilerecovery\20230312\oneplus9> adb sideload NikGapps-XXX-arm64-13-20230220.zip
PS C:\Users\XXX\downloads\mobilerecovery> adb sideload NikGapps-XXX-arm64-13-20230220.zip
Total xfer: 1.00x
## Rebooted phone to system
Your browser is not able to display this video.

shadabkiani said:
So you have flashed LineageOS without wiping data? And now it boots up successfully to the lockscreen? I don't think that can work.
Click to expand...
Click to collapse
Given the above post - Any tips on things I can try now?

Well, it is not accepting your fingerprint. When you tap on fingrprint scanner after reboot, it would automatically take you to pattern/PIN/password. So don't think that it's accepting your fingerprint.
With a 5x5 grid, the possibilities are 2^25 (source here), so consider it almost impossible in a lifetime that you would crack it by hit-and-trial.
Also, I noticed that you ran fastboot flashing unlock which means unlocking bootloader, and that in turn means the consent to format data. I don't if you are trying to save data, or just trying to get the phone working at the cost of data loss.

shadabkiani said:
Well, it is not accepting your fingerprint. When you tap on fingrprint scanner after reboot, it would automatically take you to pattern/PIN/password. So don't think that it's accepting your fingerprint.
With a 5x5 grid, the possibilities are 2^25 (source here), so consider it almost impossible in a lifetime that you would crack it by hit-and-trial.
Also, I noticed that you ran fastboot flashing unlock which means unlocking bootloader, and that in turn means the consent to format data. I don't if you are trying to save data, or just trying to get the phone working at the cost of data loss.
Click to expand...
Click to collapse
I'm trying to save the data. But even if the fingerprint is not detected and it's the default action on reboot, the pattern should not longer exist, if the phone was wiped?! I can also see the little contact logo on the top right, which I believe is the account indicator? All hints telling me that the pattern is still set and data persisted so far.
Or am I missing something?

RobSteward said:
I'm trying to save the data. But even if the fingerprint is not detected and it's the default action on reboot, the pattern should not longer exist, if the phone was wiped?! I can also see the little contact logo on the top right, which I believe is the account indicator? All hints telling me that the pattern is still set and data persisted so far.
Or am I missing something?
Click to expand...
Click to collapse
So you came from LOS 19.1 to 20 by dirty flashing. In that case, yes, you are right data is still intact I think, otherwise pattern would go away since lock settings are stored in data. Ok, so how about you try adb shell and running as root (provided you had given root access to adb before)? Are you familiar with that method?

shadabkiani said:
So you came from LOS 19.1 to 20 by dirty flashing. In that case, yes, you are right data is still intact I think, otherwise pattern would go away since lock settings are stored in data. Ok, so how about you try adb shell and running as root (provided you had given root access to adb before)? Are you familiar with that method?
Click to expand...
Click to collapse
I know adb and I have shell access. I believe I should have root, but haven't been able to figure this part out in the past. Do you have specific commands I can run or a guide I can follow to understand the access right situation on the device?
What I've done in the past is booting into recovery. From there
Advanced
Enable ADB
JavaScript:
adb devices
adb shell
And then? What should I test?

Just tried this following the first google result and.. it.....looks good?
Code:
PS C:\Users\XXX> adb devices
List of devices attached
8ac546c0 recovery
PS C:\Users\XXX> adb root
adbd is already running as root
PS C:\Users\XXX> adb shell
OnePlus9:/ #
OnePlus9:/ # exit
PS C:\Users\XXX> adb shell id
uid=0(root) gid=0(root) groups=0(root),1004(input),1007(log),1011(adb),1015(sdcard_rw),1028(sdcard_r),1078(ext_data_rw),1079(ext_obb_rw),3001(net_bt_admin),3002(net_bt),3003(inet),3006(net_bw_stats),3009(readproc),3011(uhid),3012(readtracefs) context=u:r:su:s0

When you are in recovery, does it ask for decryption at the start?
How about you go to File Manager in TWRP and then navigate to /data/ or even /sdcard/? Or try connecting to PC through cable and see if you can access your data from there?

In TWRP, check the log (tap on recents button). Does it say /data/ decrypted, or does it show some red warning?

shadabkiani said:
When you are in recovery, does it ask for decryption at the start?
How about you go to File Manager in TWRP and then navigate to /data/ or even /sdcard/? Or try connecting to PC through cable and see if you can access your data from there?
Click to expand...
Click to collapse
It does not ask for decryption.
I'm on LineageOS Recovery. I can access the sdcard folder but it does not show any data. Since it's a OP9, it does not have an external sdcard. Not sure where images would be stored.
shadabkiani said:
In TWRP, check the log (tap on recents button). Does it say /data/ decrypted, or does it show some red warning?
Click to expand...
Click to collapse
I'm on LineageOS Recovery. I've tried changing customer recovery to TWRP by booting into twrp-3.7.0_11-0-lemonadep.img (could not find a "lemonade" version) via fastboot and I'm not sure if I'm doing something wrong, but I just get stuck in Fastboot Mode. When hard resetting I get a normal system/recovery again (which makes sense, as the first step is to just temp boot into TWRP). Any suggestions?

The official recovery is only compatible with Android 11 firmware. For Android 12/13, you have to use this unofficial one. It's unified for OP9 and OP9 Pro, so don't worry. Make sure you fastboot boot it, NOT fastboot flash boot....

That worked! I now do get the decrypt question. I'm guessing I'll cancel this and move to permanently replacing LineageOS Recovery with TWRP by going
Advanced
Flash Current TWRP
Adb push twrp-installer-3.7.0-12.1-6-lemonadep.zip to phone
Select twrp-installer-3.7.0-12.1-6-lemonadep.zip (donwloaded from the GDrive folder you linked)
Flash
Correct?

RobSteward said:
That worked! I now do get the decrypt question. I'm guessing I'll cancel this and move to permanently replacing LineageOS Recovery with TWRP by going
Advanced
Flash Current TWRP
Adb push twrp-installer-3.7.0-12.1-6-lemonadep.zip to phone
Select twrp-installer-3.7.0-12.1-6-lemonadep.zip (donwloaded from the GDrive folder you linked)
Flash
Correct?
Click to expand...
Click to collapse
I won't recommend having TWRP permanent. It's not needed for OnePlus 9 as we can flash ROMs through sideload from LOS recovery, which is recommended. OnePlus 9 doesn't have dedicated recovery partition (as is the case with modern phones), so to have TWRP permanent, it would need to patch boot, which might cause problems. You can do this from TWRP. Just boot the TWRP temporarily as you just did, go to Advanced and select Flash Current Recovery.
But there are no huge benefits to have TWRP permanent, LOS recovery is good for all intents a d purposes. If you ever need to do some stuff from TWRP (which I don't think so), just boot temporarily as you just did.