Database Info

[BOUNTY] HP Slate 21 Pro - Android 4.3 [$100]

I have a Slate 21 pro, and need to get it so that when power is applied (power cord plugged in) the unit starts up without having to press the power button.
root instructions are here: http://forum.xda-developers.com/showthread.php?t=2709467
Based on the work done in that thread, the slate has been unlocked and rooted (before towelroot became available).
Very busy at the moment, so I am putting up a bounty.
relevant info:
on some samsung devices, this script can be modified: /system/bin/playlpm or /system/bin/lpm
that does not work here
on some devices one can do "fastboot oem-off-mode charge 0"
that also does not work.
c:\adt-bundle-windows-x86_64-20131030\sdk\platform-tools>fastboot getvar all
(bootloader) version-bootloader: 1.0
(bootloader) version-baseband: 2.0
(bootloader) version: 0.4
(bootloader) serialno: 3CQ40902ZV
(bootloader) mid: 001
(bootloader) product: Macallan
(bootloader) secure: no
(bootloader) unlocked: yes
(bootloader) partition-size:bootloader: 0x0000000000600000
(bootloader) partition-type:bootloader: basic
(bootloader) partition-size:recovery: 0x0000000001000000
(bootloader) partition-type:recovery: basic
(bootloader) partition-size:boot: 0x0000000000800000
(bootloader) partition-type:boot: basic
(bootloader) partition-size:dtb: 0x0000000000400000
(bootloader) partition-type:dtb: basic
(bootloader) partition-size:system: 0x0000000030000000
(bootloader) partition-type:system: ext4
(bootloader) partition-size:cache: 0x0000000040000000
(bootloader) partition-type:cache: ext4
(bootloader) partition-size:userdata: 0x000000031d800000
(bootloader) partition-type:userdata: ext4
all:
finished. total time: 0.573s
Any takers?

bump

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.

Help unbricking moto g7 power

Hi, I was wondering if anyone could help me to unbrick my network free moto g7 power UK dual sim edition: xt1955-4. It was working completely fine until one day it got caught in a bootloop, and then when attempting to restart again it only goes as far as the fastboot menu, where it says 'failed to validate boot image'.
I have attempted a few fixes, based on reading forum posts here, but I can't get into the recovery menu, and when I've tried to unlock the bootloader, I receive the error: 'feature disabled'. When I try to flash any firmware images using code people have given, I just get a long string of error messages, essentially telling me that the flash isn't working. My phone is listed under fastboot devices, but is not listed with adb devices (even though it shows up in device manager. LMSA is also unable to detect my phone model, which was the first fix I tried, and nor is RSD Lite.
I am completely new to this, so plz ELI5 if you have any suggestions of potential fixes. Thank you for your help!
If helpful, this is the result of the 'fastboot getvar all' command
(bootloader) version: 0.5
(bootloader) version-bootloader: MBM-2.1-ocean_retail-0ff20295b20-200403
(bootloader) product: ocean
(bootloader) board: ocean
(bootloader) secure: yes
(bootloader) hwrev: PVT1
(bootloader) radio: 6
(bootloader) storage-type: emmc
(bootloader) emmc: 64GB SAMSUNG RH64AB RV=08 PV=05 FV=0000000000000005
(bootloader) ram: 4GB SAMSUNG LP3 DIE=8Gb M5=01 M6=06 M7=00 M8=5F
(bootloader) cpu: SDM632
(bootloader) serialno: 2a4eacbd
(bootloader) cid: 0xDEAD
(bootloader) channelid: 0x00
(bootloader) uid: 5584240700000000000000000000
(bootloader) securestate: oem_locked
(bootloader) iswarrantyvoid: n/a
(bootloader) max-download-size: 536870912
(bootloader) reason: Last time flashing failed
(bootloader) imei:
(bootloader) meid:
(bootloader) date:
(bootloader) sku:
(bootloader) carrier_sku:
(bootloader) battid:
(bootloader) iccid:
(bootloader) cust_md5:
(bootloader) max-sparse-size: 268435456
(bootloader) current-time:
(bootloader) ro.build.fingerprint:
(bootloader) poweroffalarm: 0
(bootloader) ro.build.version.full:
(bootloader) ro.build.version.qcom:
(bootloader) version-baseband:
(bootloader) kernel.version:
(bootloader) sbl1.git: sbl1.git
(bootloader) rpm.git: rpm.git
(bootloader) tz.git: tz.git
(bootloader) devcfg.git: devcfg.git
(bootloader) keymaster.git: keymaster.git
(bootloader) cmnlib.git: cmnlib.git
(bootloader) cmnlib64.git: cmnlib64.git
(bootloader) prov.git: prov.git
(bootloader) aboot.git: MBM-2.1-ocean_retail-0ff20295b20-200403
(bootloader) frp-state: no protection (err)
(bootloader) ro.carrier:
(bootloader) current-slot: a
(bootloader) running-boot-lun: 0
(bootloader) running-slot: _a
(bootloader) slot-suffixes: _a,_b
(bootloader) slot-count: 2
(bootloader) slot-successful:_a: Yes
(bootloader) slot-successful:_b: Yes
(bootloader) slot-bootable:_a: Yes
(bootloader) slot-bootable:_b: Yes
(bootloader) slot-retry-count:_a: 6
(bootloader) slot-retry-count:_b: 6
all: listed above

motog7help said:
Hi, I was wondering if anyone could help me to unbrick my network free moto g7 power UK dual sim edition: xt1955-4. It was working completely fine until one day it got caught in a bootloop, and then when attempting to restart again it only goes as far as the fastboot menu, where it says 'failed to validate boot image'.
I have attempted a few fixes, based on reading forum posts here, but I can't get into the recovery menu, and when I've tried to unlock the bootloader, I receive the error: 'feature disabled'. When I try to flash any firmware images using code people have given, I just get a long string of error messages, essentially telling me that the flash isn't working. My phone is listed under fastboot devices, but is not listed with adb devices (even though it shows up in device manager. LMSA is also unable to detect my phone model, which was the first fix I tried, and nor is RSD Lite.
I am completely new to this, so plz ELI5 if you have any suggestions of potential fixes. Thank you for your help!
If helpful, this is the result of the 'fastboot getvar all' command
(bootloader) version: 0.5
(bootloader) version-bootloader: MBM-2.1-ocean_retail-0ff20295b20-200403
(bootloader) product: ocean
(bootloader) board: ocean
(bootloader) secure: yes
(bootloader) hwrev: PVT1
(bootloader) radio: 6
(bootloader) storage-type: emmc
(bootloader) emmc: 64GB SAMSUNG RH64AB RV=08 PV=05 FV=0000000000000005
(bootloader) ram: 4GB SAMSUNG LP3 DIE=8Gb M5=01 M6=06 M7=00 M8=5F
(bootloader) cpu: SDM632
(bootloader) serialno: 2a4eacbd
(bootloader) cid: 0xDEAD
(bootloader) channelid: 0x00
(bootloader) uid: 5584240700000000000000000000
(bootloader) securestate: oem_locked
(bootloader) iswarrantyvoid: n/a
(bootloader) max-download-size: 536870912
(bootloader) reason: Last time flashing failed
(bootloader) imei:
(bootloader) meid:
(bootloader) date:
(bootloader) sku:
(bootloader) carrier_sku:
(bootloader) battid:
(bootloader) iccid:
(bootloader) cust_md5:
(bootloader) max-sparse-size: 268435456
(bootloader) current-time:
(bootloader) ro.build.fingerprint:
(bootloader) poweroffalarm: 0
(bootloader) ro.build.version.full:
(bootloader) ro.build.version.qcom:
(bootloader) version-baseband:
(bootloader) kernel.version:
(bootloader) sbl1.git: sbl1.git
(bootloader) rpm.git: rpm.git
(bootloader) tz.git: tz.git
(bootloader) devcfg.git: devcfg.git
(bootloader) keymaster.git: keymaster.git
(bootloader) cmnlib.git: cmnlib.git
(bootloader) cmnlib64.git: cmnlib64.git
(bootloader) prov.git: prov.git
(bootloader) aboot.git: MBM-2.1-ocean_retail-0ff20295b20-200403
(bootloader) frp-state: no protection (err)
(bootloader) ro.carrier:
(bootloader) current-slot: a
(bootloader) running-boot-lun: 0
(bootloader) running-slot: _a
(bootloader) slot-suffixes: _a,_b
(bootloader) slot-count: 2
(bootloader) slot-successful:_a: Yes
(bootloader) slot-successful:_b: Yes
(bootloader) slot-bootable:_a: Yes
(bootloader) slot-bootable:_b: Yes
(bootloader) slot-retry-count:_a: 6
(bootloader) slot-retry-count:_b: 6
all: listed above
Click to expand...
Click to collapse
I don't believe there is much hope.
There is some instructions for flashing with a locked bootloader in my thread
https://forum.xda-developers.com/general/rooting-roms/guide-flashing-motorola-firmware-t4042039
Also some instructions for RSD Lite
You need Windows 7 or old for RSD Lite
For any flashing with locked bootloader you need the correct firmware
The getvar all has a lot of missing info
I'm not sure which firmware channel is the correct one.
There is a RetGB but I don't know if its dual sim
https://mirrors.lolinet.com/firmware/moto/ocean/official/RETGB/
Or it could on one of the EU channels
Like RetEU2
Sent from my ocean using XDA Labs

Thank you very much for your help! At least I was on the right track, and even though that's a shame it's most likely dead, it's good to know that it's not just an easy fix that I'm not seeing at the moment.
For flashing with a locked bootloader, is it just the firmware channel that needs to be right, or is it the actual firmware version as well? i.e. the phone broke at the beginning of September - will I need to use the OTA update from September, or is it best to just use the most up-to-date version of the firmware?
Thanks again for the guidance

motog7help said:
Thank you very much for your help! At least I was on the right track, and even though that's a shame it's most likely dead, it's good to know that it's not just an easy fix that I'm not seeing at the moment.
For flashing with a locked bootloader, is it just the firmware channel that needs to be right, or is it the actual firmware version as well? i.e. the phone broke at the beginning of September - will I need to use the OTA update from September, or is it best to just use the most up-to-date version of the firmware?
Thanks again for the guidance
Click to expand...
Click to collapse
All I need is to run a blank flash which will get u back up and running
---------- Post added at 04:09 PM ---------- Previous post was at 04:07 PM ----------
roadkill42 said:
All I need is to run a blank flash which will get u back up and running
Click to expand...
Click to collapse
https://mirrors.lolinet.com/firmware/gsi/. Go here and u cans find the blank flash

Thank you - I have tried a blank flash as well, but after running the .bat file, it unfortunately it just hangs on 'waiting for device' I think it is because the phone is not detected as an adb device (I didn't have usb debugging enabled when it broke).
From a quick google it looks like there's no way to change this from fastboot - does anyone have any tips for applying a blank flash when phone is not listed as an adb device on the console? (As I mentioned in the original post, under device manager it is showing up as 'Motorola ADB Interface')

U need the quilt com drivers installed to pc and the moto usb drivers

roadkill42 said:
U need the quilt com drivers installed to pc and the moto usb drivers
Click to expand...
Click to collapse
Thank you for the help - I have installed both sets of drivers, although the qualcomm drivers don't display a device under 'ports' as reported by some people. I have also tried changing drivers on the 'Motorola ADB Interface' from the Motorola specific one to a generic one, but it doesn't seem to make a difference? Is there anything I might be doing wrong here?

motog7help said:
Thank you for the help - I have installed both sets of drivers, although the qualcomm drivers don't display a device under 'ports' as reported by some people. I have also tried changing drivers on the 'Motorola ADB Interface' from the Motorola specific one to a generic one, but it doesn't seem to make a difference? Is there anything I might be doing wrong here?
Click to expand...
Click to collapse
You cannot use a blankflash unless the device is in emergency download mode (EDL)
To my knowledge the is no way to enter EDL with a locked bootloader.
Sent from my ocean using XDA Labs

https://t.me/joinchat/MmtXRlRyFn498KnQGBsmyw fastboot oem blankflash try this comand in terminal then if screen goes black click on the blank flash .bat file should work cause u are simi bricked can go to that link I sent b easer to help

Sure try
Code:
fastboot oem blankflash
Not very likely to work with a locked bootloader.
Sent from my ocean using XDA Labs
---------- Post added at 03:40 PM ---------- Previous post was at 03:29 PM ----------
You will most likely see.
Code:
...fastboot oem blankflash
(bootloader) command restricted
FAILED (remote: '')
fastboot: error: Command failed

sd_shadow said:
Sure try
Code:
fastboot oem blankflash
Not very likely to work with a locked bootloader.
Sent from my ocean using XDA Labs
---------- Post added at 03:40 PM ---------- Previous post was at 03:29 PM ----------
You will most likely see.
Code:
...fastboot oem blankflash
(bootloader) command restricted
FAILED (remote: '')
fastboot: error: Command failed
Click to expand...
Click to collapse
Thanks for the suggestions, both. You're absolutely right - it did return the 'command restricted' result. Any last ditch ideas that I might try?

motog7help said:
Sure try
Not very likely to work with a locked bootloader.
Sent from my ocean using XDA Labs
---------- Post added at 03:40 PM ---------- Previous post was at 03:29 PM ----------
You will most likely see.
Thanks for the suggestions, both. You're absolutely right - it did return the 'command restricted' result. Any last ditch ideas that I might try?
Click to expand...
Click to collapse
RSD Lite using a Windows 7 or older PC
https://forum.xda-developers.com/general/rooting-roms/guide-flashing-motorola-firmware-t4042039
Sent from my ocean using XDA Labs

https://www.5g-m.com/en/micro-usb-datacable-for-android/17894-edl-cable-w230.html is said to work

Thank you - I will give both of these a try and report back!

motog7help said:
Thank you - I will give both of these a try and report back!
Click to expand...
Click to collapse
Are u able to get into the quialcom minue using the volume bottons?

can someone help me with advice to get booting again
it was oem unlocked before fail to boot
fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: MBM-2.1-ocean_vzw-16222030b3b-200930
(bootloader) product: ocean
(bootloader) board: ocean
(bootloader) secure: yes
(bootloader) hwrev: PVT1
(bootloader) radio: 1
(bootloader) storage-type: emmc
(bootloader) emmc: 32GB SKHYNIX hB8aP> RV=08 PV=03 FV=0000000034303030
(bootloader) ram: 3GB SKHYNIX LP3 DIE=8Gb M5=06 M6=03 M7=01 M8=5F
(bootloader) cpu: SDM632
(bootloader) serialno: ZY323W4FKR
(bootloader) cid: 0x0032
(bootloader) channelid: 0x96
(bootloader) uid: C82C277300000000000000000000
(bootloader) securestate: flashing_unlocked
(bootloader) factory-modes: disabled
(bootloader) iswarrantyvoid: yes
(bootloader) max-download-size: 536870912
(bootloader) reason: Volume down key pressed
(bootloader) imei: 359525091092315
(bootloader) imei2:
(bootloader) meid:
(bootloader) date: 04-17-2019
(bootloader) sku: XT1955-5
(bootloader) carrier_sku: XT1955-5
(bootloader) battid: SB18C28957
(bootloader) iccid: 89148000005008330805
(bootloader) cust_md5:
(bootloader) max-sparse-size: 268435456
(bootloader) current-time: "Thu Oct 1 5: 5:18 UTC 2020"
(bootloader) ro.build.fingerprint[0]: motorola/ocean/ocean:10/QCOS30.85-
(bootloader) ro.build.fingerprint[1]: 18-6/691ed:user/release-keys
(bootloader) poweroffalarm: 0
(bootloader) ro.build.version.full: <not found>
(bootloader) ro.build.version.qcom: LA.UM.8.6.2.r1-06600-89xx.0
(bootloader) version-baseband: <not found>
(bootloader) kernel.version[0]: Linux version 4.9.206-perf+ ([email protected]
(bootloader) kernel.version[1]: oid-build) (clang version 8.0.12 for And
(bootloader) kernel.version[2]: roid NDK) #1 SMP PREEMPT Wed Sep 30 23:2
(bootloader) kernel.version[3]: 2:14 CDT 2020
(bootloader) sbl1.git: MBM-2.1-ocean_vzw-a30e356d6d-200930
(bootloader) rpm.git: MBM-2.1-ocean_vzw-20f2cf34-200930
(bootloader) tz.git: MBM-2.1-ocean_vzw-6814a8d41f-200930
(bootloader) devcfg.git: MBM-2.1-ocean_vzw-6814a8d41f-200930
(bootloader) keymaster.git: MBM-2.1-ocean_vzw-6814a8d41f-200930
(bootloader) cmnlib.git: MBM-2.1-ocean_vzw-6814a8d41f-200930
(bootloader) cmnlib64.git: MBM-2.1-ocean_vzw-6814a8d41f-200930
(bootloader) prov.git: MBM-2.1-ocean_vzw-6814a8d41f-200930
(bootloader) aboot.git: MBM-2.1-ocean_vzw-16222030b3b-200930
(bootloader) frp-state: no protection (0)
(bootloader) ro.carrier: comcast
(bootloader) current-slot: a
(bootloader) running-boot-lun: 0
(bootloader) running-slot: _a
(bootloader) slot-suffixes: _a,_b
(bootloader) slot-count: 2
(bootloader) slot-successful:_a: Yes
(bootloader) slot-successful:_b: No
(bootloader) slot-bootable:_a: Yes
(bootloader) slot-bootable:_b: Yes
(bootloader) slot-retry-count:_a: 4
(bootloader) slot-retry-count:_b: 0
(bootloader) pcb-part-no: SP69A6P237
all: listed above
finished. total time: 0.307s

roadkill42 said:
https://t.me/joinchat/MmtXRlRyFn498KnQGBsmyw fastboot oem blankflash try this comand in terminal then if screen goes black click on the blank flash .bat file should work cause u are simi bricked can go to that link I sent b easer to help
Click to expand...
Click to collapse
Thx, this command save me phone.

"Dynamic System Update" package bricked phone

I installed a "Dynamic System Update" package and after rebooting the OS is not detected, bootloader (Vol D + Power) opens, but start and recovery lead to the same missing os screen.
Is there some way to fix this? I need my phone working
I can get to fastboot but not adb, this is `fastboot getvar all`
(bootloader) kernel: uefi
(bootloader) version-bootloader: MBM-3.0-uefi-df63f3de4a8-210524
(bootloader) product: denver
(bootloader) board: denver
(bootloader) secure: yes
(bootloader) hwrev: PVT
(bootloader) radio: NA
(bootloader) storage-type: UFS
(bootloader) emmc: N/A
(bootloader) ufs: 128GB SAMSUNG KM5V8001DM-B622 FV=2702 WB=2048
(bootloader) ram: 4GB SAMSUNG LP4x DIE=16Gb M5-M8=01 07 01 12
(bootloader) cpu: SM_MANNAR 1.1
(bootloader) serialno: ZY22CKXBPJ
(bootloader) cid:
(bootloader) channelid: 0x99
(bootloader) uid:
(bootloader) securestate: oem_locked
(bootloader) factory-modes: disabled
(bootloader) verity-state: enforcing (0)
(bootloader) iswarrantyvoid: no
(bootloader) max-download-size: 788201472
(bootloader) reason: Volume down key pressed
(bootloader) imei:
(bootloader) imei2:
(bootloader) meid:
(bootloader) date: 06-16-2021
(bootloader) sku: XT2131-1
(bootloader) carrier_sku: XT2131-1
(bootloader) battid: SB18D00294
(bootloader) battery-voltage: 4333
(bootloader) iccid:
(bootloader) cust_md5:
(bootloader) max-sparse-size: 268435456
(bootloader) poweroffalarm: 0
(bootloader) ro.carrier: boost
(bootloader) ro.build.fingerprint[0]: motorola/denver_global/denver:11/R
(bootloader) ro.build.fingerprint[1]: RE31.Q2-11-52/a40ec:user/release-k
(bootloader) ro.build.fingerprint[2]: eys
(bootloader) ro.build.version.qcom: LA.UM.9.16.r1-03500-MANNAR.0
(bootloader) version-baseband[0]: M4350_HI405_19.533.01.79R DENVER_BOOST
(bootloader) version-baseband[1]: _CUST
(bootloader) kernel.version[0]: Linux version 5.4.61-moto-gfa1749a591f9
(bootloader) kernel.version[1]: ([email protected]) (Android (6443078
(bootloader) kernel.version[2]: based on r383902) clang version 11.0.1
(bootloader) kernel.version[3]: (https://android.googlesource.com/toolch
(bootloader) kernel.version[4]: ain/llvm-project b397f81060ce6d701042b78
(bootloader) kernel.version[5]: 2172ed13bee898b79), LLD 11.0.1 (/buildbo
(bootloader) kernel.version[6]: t/tmp/tmp6_m7QH b397f81060ce6d701042b782
(bootloader) kernel.version[7]: 172ed13bee898b79)) #1 SMP PREEMPT Mon Ma
(bootloader) kernel.version[8]: y 24 04:24:01 CDT 2021
(bootloader) git:xbl: MBM-3.0-uefi-71c7a1ab-210524
(bootloader) git:xbl_config: MBM-3.0-uefi-71c7a1ab-210524
(bootloader) git:abl: MBM-3.0-uefi-df63f3de4a8-210524
(bootloader) git:rpm: MBM-3.0-uefi-1573f88-210524
(bootloader) git:tz: MBM-3.0-uefi-ecdb076-210524
(bootloader) git:hyp: MBM-3.0-uefi-ecdb076-210524
(bootloader) git:devcfg: MBM-3.0-uefi-ecdb076-210524
(bootloader) git:keymaster: MBM-3.0-uefi-9731016-210524
(bootloader) git:storsec: MBM-3.0-uefi-9731016-210524
(bootloader) git:uefisecapp: MBM-3.0-uefi-9731016-210524
(bootloader) gitrov: MBM-3.0-uefi-ecdb076-210524
(bootloader) git:qupfw: MBM-3.0-uefi-7b29c10-210524
(bootloader) frp-state: no protection (77)
(bootloader) current-slot: a
(bootloader) running-bl-slot: _a/_a
(bootloader) running-boot-lun: 1
(bootloader) slot-count: 2
(bootloader) slot-successful:_a: no
(bootloader) slot-successful:_b: no
(bootloader) slot-unbootable:_a: no
(bootloader) slot-unbootable:_b: no
(bootloader) slot-retry-count:_a: 6
(bootloader) slot-retry-count:_b: 0
(bootloader) logical-block-size: 0x1000
(bootloader) erase-block-size: 0x1000
(bootloader) is-userspace: no
(bootloader) pcb-part-no: SB28C93368
(bootloader) primary-display: auo_nt36675_fhd_vid
(bootloader) secondary-display:
all: listed above
Finished. Total time: 0.159s
Click to expand...
Click to collapse

ShayBox said:
I installed a "Dynamic System Update" package and after rebooting the OS is not detected, bootloader (Vol D + Power) opens, but start and recovery lead to the same missing os screen.
Is there some way to fix this? I need my phone working
I can get to fastboot but not adb, this is `fastboot getvar all`
Click to expand...
Click to collapse
The bootloader is locked, I doubt it can be fixed.

A slightly bigger doubt. How is the device detected as a PVT??
You can also just go to recovery and send us an image to show what it says , maybe the Lenovo Motorola Smart Assistant will help (QFIL flash tool with a good looking UI for Lenovo and moto devices , destroyed my tab due to the Lenovo Smart Assistant installing the firmware in a wrong method causing failures! but lets hope yours will survive!)

Slot b retry count is 0 , we could retry to set slot b as primary slot it might just work! but locked bootloaders don't allow this.... maybe just maybe you can ask Moto about this and they might be able to help , the device is QCOM based so QFIL should work (Lenovo Smart Assistant should also work????)

Seems lenovo moto smart assistant isn't working because support.lenovo.com is down until tomorrow.
Can the device be unlocked like this? or is that a bad idea.
I just got this phone 2 days ago, bought it after breaking my old free phone screen

ShayBox said:
Seems lenovo moto smart assistant isn't working because support.lenovo.com is down until tomorrow.
Can the device be unlocked like this? or is that a bad idea.
I just got this phone 2 days ago, bought it after breaking my old free phone screen
Click to expand...
Click to collapse
I doubt LMSA can help, it pulls info from the phone to match firmware.
Getvar all doesn't show the info needed, so you would just get an error from LMSA.
You should try Moto support

sd_shadow said:
I doubt LMSA can help, it pulls info from the phone to match firmware.
Getvar all doesn't show the info needed, so you would just get an error from LMSA.
You should try Moto support
Click to expand...
Click to collapse
support.motorola.com is also broken, but not for maintenance so who knows how long that will take to work again, this sucks...
EDIT: Its back online, I'll try it

IT WORKED! I used the updated lenovo software and it worked!

Help - HTC U11 Life (Sense not working, Software modified)

I recently got an HTC U11 Life (Sense Version) in a joblot. Its running android 8.0.0 I tried to check If there are pending updates, there were none. I boot in recovery, that is when i noticed that the bootloader has a "relocked" flag. The problem I have with the phone, Blinkfeed does not work whatsoever. SENSE also is not working proper, I cannot download or check out phone themes. Please see attached images. What can i do? I wish someone had figured if there was a way to convert from sense to androidone. How can I have the Sense working again? Let me know.
Code:
C:\adb>fastboot getvar all
(bootloader) boot-mode:FASTBOOT
(bootloader) unlocked:no
(bootloader) off-mode-charge:0
(bootloader) charger-screen-enabled:0
(bootloader) battery-soc-ok:yes
(bootloader) battery-voltage:4259
(bootloader) version-baseband:
(bootloader) version-bootloader:
(bootloader) variant:SDM EMMC
(bootloader) partition-type:cache:ext4
(bootloader) partition-size:cache: 0xE000000
(bootloader) partition-type:userdata:ext4
(bootloader) partition-size:userdata: 0x60B000000
(bootloader) partition-type:system:ext4
(bootloader) partition-size:system: 0xEF000000
(bootloader) secure:yes
(bootloader) serialno:HT7AL1C01429
(bootloader) product:HTC_Phone
(bootloader) max-download-size:536870912
(bootloader) kernel:uefi
all:
finished. total time: 0.033s