I tried installing Lineage 18.1, the appropriate Gapps and Magisk. Booted directly into TWRP (without flashing it) and did everything as per usual, followed the instructions, so no rebooting in-between etc.
Now all my phone can do is bootloader. Notably, the usual "broken android guy" picture is gone and so are the labels of the volume up/down buttons (though they do function and it displays "restart bootloader" or "recovery mode" or "factory" etc on top of the screen). Trying to boot, even with "fastboot continue", just brings me back to the bootloader, same with attempting to use recovery (shows error message and brings me back).
The serial number has changed from what it used to be and while fastboot does detect the device (with the aforementioned new ID), it can't do anything. All attempts to boot or flash are met with errors, usually accompanied with:
FAILED (remote: '')
and usually with "permission denied". Bootloader claims "oem_locked". Trying to "oem get_unlock_data"
Attempting to flash recovery to boot shows "invalid partition name boot" (changing it to "boot_a" or "boot_b" doesn't help). Can't just boot the recovery image from the computer either - once again, "permission denied" and FAILED (remote: '').
The oem unlock command returns "feature disabled".
The getvar current-slot command returns "current-slot: "
Trying to set active slot to either A or B returns "Command is not allowed".
Trying to flash stock image is no use, as no commands (outside of getvar max-sparse-size) work at all.
Motorola's Rescue Assistant couldn't detect my device (or rather, it could - said my device is '' and wasn't able to do anything with it). I've reinstalled the Motorola drivers and it was no help, although I admittedly can't find it in the device manager - should it be under "Ports" or is "Android Device -> Motorola ADB Interface" all that's supposed to show?
Bootloader screen:
Code:
AP Fastboot Flash Mode (Secure)
BL: MBM-2.1-ocean_retail-cfdb645cf1d-210201
Baseband:
Product/variant: ocean radio6 64GB PVT1
Serial Number: d890e31
CPU: SDM632
eMMC: 64GB MICRON S0J9N8 RV=08 PV=10 FV=0000000000000004
DRAM: 4GB MICRON LP3 DIE=3Gb M5=FF M6=01 M&=00 M8=5F
Console [NULL]: null
Console [default]: ttyMSM0,115200,n8
(I can switch between the two with "Switch console" via the volume buttons)
Tools Mode Config: DISABLED/ENABLED
(can switch with "Switch Tools mode" via volume buttons)
Battery OK
oem_locked
Transfer Mode: USB Connected
I'm running out of ideas. I've had trouble before, but at least then I could use the bootloader to attempt some fixing. Worst case scenario used to be losing all data and having to reflash the stock. This is so much worse - I can't even do anything! Does anyone have any ideas??
EDIT: getvar all results just in case:
Code:
(bootloader) version: 0.5
(bootloader) version-bootloader: MBM-2.1-ocean_retail-cfdb645cf1d-210201
(bootloader) product: ocean
(bootloader) board: ocean
(bootloader) secure: yes
(bootloader) hwrev: PVT1
(bootloader) radio: 6
(bootloader) storage-type: emmc
(bootloader) emmc: 64GB MICRON S0J9N8 RV=08 PV=10 FV=0000000000000004
(bootloader) ram: 4GB MICRON LP3 DIE=8Gb M5=FF M6=01 M7=00 M8=5F
(bootloader) cpu: SDM632
(bootloader) serialno: d890e31
(bootloader) cid: 0xDEAD
(bootloader) channelid: 0x00
(bootloader) uid: 0000000000000000000000000000
(bootloader) securestate: oem_locked
(bootloader) factory-modes: disabled
(bootloader) iswarrantyvoid: n/a
(bootloader) max-download-size: 536870912
(bootloader) reason: Failed to initialize partition table
(bootloader) imei:
(bootloader) imei2:
(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-cfdb645cf1d-210201
(bootloader) frp-state: no protection (err)
(bootloader) ro.carrier:
(bootloader) current-slot:
(bootloader) running-boot-lun: must + g->mlen
(bootloader) running-slot:
(bootloader) slot-suffixes: _a
(bootloader) slot-count: 1
(bootloader) slot-successful:_a: INVALID
(bootloader) slot-successful:_b: INVALID
(bootloader) slot-bootable:_a: INVALID
(bootloader) slot-bootable:_b: INVALID
(bootloader) slot-retry-count:_a: unknown
(bootloader) slot-retry-count:_b: unknown
(bootloader) pcb-part-no:
all: listed above
UPDATE: The command oem blankflash successfully sends my phone into blank flash mode. However, all attempts at blankflashing end immediately with a:
FAILED: qb_flash_singleimage()->sahara_greet_device()->change_mode()->do_hello()->IO error
error message.
Code:
**** Log buffer [000001] 2021-04-03_13:03:13 ****
[ -0.000] Opening device: \\.\COM7
[ 0.009] Detecting device
[ 4.031] ERROR: sahara_greet_device()->change_mode()->do_hello()->IO error
[ 4.031] Check qboot_log.txt for more details
[ 4.031] Total time: 4.032s
[ 4.031]
[ 4.031] qboot version 3.40
[ 4.031]
[ 4.031] DEVICE {
[ 4.031] name = "\\.\COM7",
[ 4.031] flags = "0x64",
[ 4.031] addr = "0x61FE4C",
[ 4.031] api.bnr = "0xE52CF8",
[ 4.031] }
[ 4.031]
[ 4.031]
[ 4.031] Backup & Restore {
[ 4.031] num_entries = 0,
[ 4.031] restoring = "false",
[ 4.031] backup_error = "not started",
[ 4.031] restore_error = "not started",
[ 4.031] }
[ 4.031]
Try to reflash stock firmware from https://mirrors.lolinet.com/firmware/moto/ then you will be able to boot stock. The next time you flash a custom Rom flash copypartitionsAB.zip before flashing anything else
Related
Good my phone has suddenly been hung and when forced reboot is then left in the logo of motorola and it's not from there, I tried to make this tutorial and "appears" that does everything well but then when rebooting just does not start as usual
When trying to enter the recovery says "boot up failed" and tried to install a custom recovery and I get the same
angelgzg said:
Good my phone has suddenly been hung and when forced reboot is then left in the logo of motorola and it's not from there, I tried to make this tutorial and "appears" that does everything well but then when rebooting just does not start as usual
When trying to enter the recovery says "boot up failed" and tried to install a custom recovery and I get the same
Click to expand...
Click to collapse
Try to reflash the stock firmware or, even better, the 4.4.4 of your stock firmware.
oversleeper said:
Try to reflash the stock firmware or, even better, the 4.4.4 of your stock firmware.
Click to expand...
Click to collapse
Where I can download a 4.4.4 firmware and not a full upgrade? and 4.4.3 and try anything
angelgzg said:
Where I can download a 4.4.4 firmware and not a full upgrade? and 4.4.3 and try anything
Click to expand...
Click to collapse
Here
oversleeper said:
Here
Click to expand...
Click to collapse
I get these errors trying
hab check failed for boot
hab check failed for recovery
angelgzg said:
I get these errors trying
hab check failed for boot
hab check failed for recovery
Click to expand...
Click to collapse
That's because you're flashing a non stock firmware. Just ignore that error. Run all commands and all should work properly.
oversleeper said:
That's because you're flashing a non stock firmware. Just ignore that error. Run all commands and all should work properly.
Click to expand...
Click to collapse
This error also should ignore it?
piv signed invalid system image
Just do not start everything but it stays on the logo and I can not get into the recovery?
I'm thinking that the problem is hardware: ((((
angelgzg said:
This error also should ignore it?
piv signed invalid system image
Just do not start everything but it stays on the logo and I can not get into the recovery?
I'm thinking that the problem is hardware: ((((
Click to expand...
Click to collapse
Run the command fastboot.exe getvar all or mfastboot.exe getvar all and post the result.
oversleeper said:
Run the command fastboot.exe getvar all or mfastboot.exe getvar all and post the result.
Click to expand...
Click to collapse
C:\Users\Usuario\Desktop\Minimal ADB and Fastboot>mfastboot.exe getvar all
version: 0.5
version-bootloader: 4111
product: falcon
secure: yes
hwrev: 0x83C0
radio: 0x1
emmc: 16GB Sandisk REV=06 PRV=07 TYPE=17
ram: 1024MB Samsung S4 SDRAM DIE=4Gb
cpu: MSM8226 CS
serialno: TA93005UU8
cid: 0x0009
channelid: 0x00
uid: C3A9C5020F000000000000000000
unlocked: no
iswarrantyvoid: no
mot_sst: 0
max-download-size: 536870912
reason: Volume down key pressed
imei:
meid:
date:
sku:
iccid:
cust_md5:
max-sparse-size: 268435456
current-time: "Wed Aug 6 0:23: 7 UTC 2014"
ro.build.fingerprint[0]: motorola/falcon_retuglb/falcon_umt
ro.build.fingerprint[1]: s:4.4.3/KXB21.14-L1.32/33:user/rel
ro.build.fingerprint[2]: ease-keys
ro.build.version.full[0]: Blur_Version.210.12.32.falcon_umt
ro.build.version.full[1]: s.Retail.en.US
ro.build.version.qcom[0]: AU_LINUX_ANDROID_LNX.LA.3.5.1_RB1
ro.build.version.qcom[1]: .04.04.02.048.020
version-baseband:
kernel.version[0]: Linux version 3.4.42-g26ca2df ([email protected]
kernel.version[1]: ilclbld54) (gcc version 4.7 (GCC) ) #1 S
kernel.version[2]: MP PREEMPT Fri May 30 11:08:03 CDT 2014
sdi.git: git=MBM-NG-V41.11-0-gdc5aeaf
sbl1.git: git=MBM-NG-V41.11-0-gcff5797
rpm.git: git=MBM-NG-V41.11-0-g71b1aae
tz.git: git=MBM-NG-V41.11-0-ga27c415
aboot.git: git=MBM-NG-V41.11-0-g7d46a5a
qe: qe 0/1
ro.carrier: unknown
all: listed above
finished. total time: 0.155s
angelgzg said:
C:\Users\Usuario\Desktop\Minimal ADB and Fastboot>mfastboot.exe getvar all
version: 0.5
version-bootloader: 4111
product: falcon
secure: yes
hwrev: 0x83C0
radio: 0x1
emmc: 16GB Sandisk REV=06 PRV=07 TYPE=17
ram: 1024MB Samsung S4 SDRAM DIE=4Gb
cpu: MSM8226 CS
serialno: TA93005UU8
cid: 0x0009
channelid: 0x00
uid: C3A9C5020F000000000000000000
unlocked: no
iswarrantyvoid: no
mot_sst: 0
max-download-size: 536870912
reason: Volume down key pressed
imei:
meid:
date:
sku:
iccid:
cust_md5:
max-sparse-size: 268435456
current-time: "Wed Aug 6 0:23: 7 UTC 2014"
ro.build.fingerprint[0]: motorola/falcon_retuglb/falcon_umt
ro.build.fingerprint[1]: s:4.4.3/KXB21.14-L1.32/33:user/rel
ro.build.fingerprint[2]: ease-keys
ro.build.version.full[0]: Blur_Version.210.12.32.falcon_umt
ro.build.version.full[1]: s.Retail.en.US
ro.build.version.qcom[0]: AU_LINUX_ANDROID_LNX.LA.3.5.1_RB1
ro.build.version.qcom[1]: .04.04.02.048.020
version-baseband:
kernel.version[0]: Linux version 3.4.42-g26ca2df ([email protected]
kernel.version[1]: ilclbld54) (gcc version 4.7 (GCC) ) #1 S
kernel.version[2]: MP PREEMPT Fri May 30 11:08:03 CDT 2014
sdi.git: git=MBM-NG-V41.11-0-gdc5aeaf
sbl1.git: git=MBM-NG-V41.11-0-gcff5797
rpm.git: git=MBM-NG-V41.11-0-g71b1aae
tz.git: git=MBM-NG-V41.11-0-ga27c415
aboot.git: git=MBM-NG-V41.11-0-g7d46a5a
qe: qe 0/1
ro.carrier: unknown
all: listed above
finished. total time: 0.155s
Click to expand...
Click to collapse
Download this.
oversleeper said:
Download this.
Click to expand...
Click to collapse
Now try this firmware installation and does everything well without errors but when restart is the motorola logo
any way to know if this completely-dead?
angelgzg said:
Now try this firmware installation and does everything well without errors but when restart is the motorola logo
any way to know if this completely-dead?
Click to expand...
Click to collapse
Since you are under warranty the best thing to do is to send it to Motorola...
oversleeper said:
Since you are under warranty the best thing to do is to send it to Motorola...
Click to expand...
Click to collapse
Well I bought it from amazon USA, I'm from Venezuela so I think that's not a possibility? that alternatives do I have? it could be converted into brick? unbrick then?
I also tried unlocking the bootloader and I get the message in purple unlocked and restarted but then goes into fastboot mode as if not done
I changed usb cable and now I get status code = 3, but now does not advance after the warning screen and enter android recovery goes the "no command"
angelgzg said:
Well I bought it from amazon USA, I'm from Venezuela so I think that's not a possibility? that alternatives do I have? it could be converted into brick? unbrick then?
I also tried unlocking the bootloader and I get the message in purple unlocked and restarted but then goes into fastboot mode as if not done
I changed usb cable and now I get status code = 3, but now does not advance after the warning screen and enter android recovery goes the "no command"
Click to expand...
Click to collapse
Ok... now your bootloader is unlocked and your warranty gone, so you can try the next level. Follow my thread. You have to use the bricker script, then when your device will be recognized as qhsusb_bulk I'll give you the tool to reflash the bootloader.
oversleeper said:
Ok... now your bootloader is unlocked and your warranty gone, so you can try the next level. Follow my thread. You have to use the bricker script, then when your device will be recognized as qhsusb_bulk I'll give you the tool to reflash the bootloader.
Click to expand...
Click to collapse
Well now the computer does not pass the warning screen when entering the bootloader and recovery I get the android with exclamation mark and says no command
this is the phone info using this command (mfastboot.exe getvar all)
C:\Minimal ADB and Fastboot>mfastboot.exe getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 4111
(bootloader) product: falcon
(bootloader) secure: yes
(bootloader) hwrev: 0x83C0
(bootloader) radio: 0x1
(bootloader) emmc: 16GB Sandisk REV=06 PRV=07 TYPE=17
(bootloader) ram: 1024MB Samsung S4 SDRAM DIE=4Gb
(bootloader) cpu: MSM8226 CS
(bootloader) serialno: TA93005UU8
(bootloader) cid: 0x0009
(bootloader) channelid: 0x00
(bootloader) uid: C3A9C5020F000000000000000000
(bootloader) unlocked: yes
(bootloader) iswarrantyvoid: yes
(bootloader) mot_sst: 3
(bootloader) max-download-size: 536870912
(bootloader) reason: Volume down key pressed
(bootloader) imei:
(bootloader) meid:
(bootloader) date:
(bootloader) sku:
(bootloader) iccid:
(bootloader) cust_md5:
(bootloader) max-sparse-size: 268435456
(bootloader) current-time: "Wed Aug 6 3:39:14 UTC 2014"
(bootloader) ro.build.fingerprint[0]: motorola/falcon_retuglb/falcon_umt
(bootloader) ro.build.fingerprint[1]: s:4.4.3/KXB21.14-L1.32/33:user/rel
(bootloader) ro.build.fingerprint[2]: ease-keys
(bootloader) ro.build.version.full[0]: Blur_Version.210.12.32.falcon_umt
(bootloader) ro.build.version.full[1]: s.Retail.en.US
(bootloader) ro.build.version.qcom[0]: AU_LINUX_ANDROID_LNX.LA.3.5.1_RB1
(bootloader) ro.build.version.qcom[1]: .04.04.02.048.020
(bootloader) version-baseband:
(bootloader) kernel.version[0]: Linux version 3.4.42-g26ca2df ([email protected]
(bootloader) kernel.version[1]: ilclbld54) (gcc version 4.7 (GCC) ) #1 S
(bootloader) kernel.version[2]: MP PREEMPT Fri May 30 11:08:03 CDT 2014
(bootloader) sdi.git: git=MBM-NG-V41.11-0-gdc5aeaf
(bootloader) sbl1.git: git=MBM-NG-V41.11-0-gcff5797
(bootloader) rpm.git: git=MBM-NG-V41.11-0-g71b1aae
(bootloader) tz.git: git=MBM-NG-V41.11-0-ga27c415
(bootloader) aboot.git: git=MBM-NG-V41.11-0-g7d46a5a
(bootloader) qe: qe 0/1
(bootloader) ro.carrier: unknown
all: listed above
finished. total time: 0.054s
C:\Minimal ADB and Fastboot>
oversleeper said:
Ok... now your bootloader is unlocked and your warranty gone, so you can try the next level. Follow my thread. You have to use the bricker script, then when your device will be recognized as qhsusb_bulk I'll give you the tool to reflash the bootloader.
Click to expand...
Click to collapse
after using the recommended script happens happens happens
WARNING: READ CAREFULLY BEFORE YOU PROCEED!
THIS SCRIPT WILL DESTROY THE BOOTLOADER OF YOUR DEVICE.
DO NOT ATTEMPT TO USE UNLESS YOU'RE SURE ABOUT WHAT YOU'RE DOING.
ONLY YOU ARE RESPONSIBLE FOR YOUR ACTIONS.
Do you want to continue [Y / N]?, And
target-sparse max-size: 256MB
sending 'fsg' (102 KB) ...
OKAY [0.027s]
writing 'fsg' ...
OKAY [3.145s]
finished. Total time: 3.175s
target-sparse max-size: 256MB
sending 'rpm' (200 KB) ...
OKAY [0.038s]
writing 'rpm' ...
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. Total time: 0.330s
target-sparse max-size: 256MB
sending 'SBL1' (264 KB) ...
OKAY [0.057s]
writing 'SBL1' ...
OKAY [0.028s]
finished. Total time: 0.088s
target-sparse max-size: 256MB
sending 'sdi' (32 KB) ...
OKAY [0.058s]
writing 'sdi' ...
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. Total time: 0.343s
target-sparse max-size: 256MB
sending 'tz' (400 KB) ...
OKAY [0.084s]
writing 'tz' ...
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. Total time: 0.392s
rebooting ...
finished. Total time: 0.003s
Your device is now hard bricked!
Press any key to continue. . .
But still I can get into fastboot mode and the pc recognizes me as android device
angelgzg said:
after using the recommended script happens happens happens
WARNING: READ CAREFULLY BEFORE YOU PROCEED!
THIS SCRIPT WILL DESTROY THE BOOTLOADER OF YOUR DEVICE.
DO NOT ATTEMPT TO USE UNLESS YOU'RE SURE ABOUT WHAT YOU'RE DOING.
ONLY YOU ARE RESPONSIBLE FOR YOUR ACTIONS.
Do you want to continue [Y / N]?, And
target-sparse max-size: 256MB
sending 'fsg' (102 KB) ...
OKAY [0.027s]
writing 'fsg' ...
OKAY [3.145s]
finished. Total time: 3.175s
target-sparse max-size: 256MB
sending 'rpm' (200 KB) ...
OKAY [0.038s]
writing 'rpm' ...
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. Total time: 0.330s
target-sparse max-size: 256MB
sending 'SBL1' (264 KB) ...
OKAY [0.057s]
writing 'SBL1' ...
OKAY [0.028s]
finished. Total time: 0.088s
target-sparse max-size: 256MB
sending 'sdi' (32 KB) ...
OKAY [0.058s]
writing 'sdi' ...
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. Total time: 0.343s
target-sparse max-size: 256MB
sending 'tz' (400 KB) ...
OKAY [0.084s]
writing 'tz' ...
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. Total time: 0.392s
rebooting ...
finished. Total time: 0.003s
Your device is now hard bricked!
Press any key to continue. . .
But still I can get into fastboot mode and the pc recognizes me as android device
Click to expand...
Click to collapse
Try to download this and run the boot loader tool first. Post the result.
oversleeper said:
Try to download this and run the boot loader tool first. Post the result.
Click to expand...
Click to collapse
It seems like everything I do not change anything
Install recovery shows no error, but still comes out the same and yet so
C:\Users\PC\Desktop\Tools\DeviceInfo>mfastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 4111
(bootloader) product: falcon
(bootloader) secure: yes
(bootloader) hwrev: 0x83C0
(bootloader) radio: 0x1
(bootloader) emmc: 16GB Sandisk REV=06 PRV=07 TYPE=17
(bootloader) ram: 1024MB Samsung S4 SDRAM DIE=4Gb
(bootloader) cpu: MSM8226 CS
(bootloader) serialno: TA93005UU8
(bootloader) cid: 0x0009
(bootloader) channelid: 0x00
(bootloader) uid: C3A9C5020F000000000000000000
(bootloader) unlocked: yes
(bootloader) iswarrantyvoid: yes
(bootloader) mot_sst: 3
(bootloader) max-download-size: 536870912
(bootloader) reason: Volume down key pressed
(bootloader) imei:
(bootloader) meid:
(bootloader) date:
(bootloader) sku:
(bootloader) iccid:
(bootloader) cust_md5:
(bootloader) max-sparse-size: 268435456
(bootloader) current-time: "Wed Aug 6 14: 2:16 UTC 2014"
(bootloader) ro.build.fingerprint[0]: motorola/falcon_retuglb/falcon_umt
(bootloader) ro.build.fingerprint[1]: s:4.4.3/KXB21.14-L1.32/33:user/rel
(bootloader) ro.build.fingerprint[2]: ease-keys
(bootloader) ro.build.version.full[0]: Blur_Version.210.12.32.falcon_umt
(bootloader) ro.build.version.full[1]: s.Retail.en.US
(bootloader) ro.build.version.qcom[0]: AU_LINUX_ANDROID_LNX.LA.3.5.1_RB1
(bootloader) ro.build.version.qcom[1]: .04.04.02.048.020
(bootloader) version-baseband:
(bootloader) kernel.version[0]: Linux version 3.4.42-g26ca2df ([email protected]
(bootloader) kernel.version[1]: ilclbld54) (gcc version 4.7 (GCC) ) #1 S
(bootloader) kernel.version[2]: MP PREEMPT Fri May 30 11:08:03 CDT 2014
(bootloader) sdi.git: git=MBM-NG-V41.11-0-gdc5aeaf
(bootloader) sbl1.git: git=MBM-NG-V41.11-0-gcff5797
(bootloader) rpm.git: git=MBM-NG-V41.11-0-g71b1aae
(bootloader) tz.git: git=MBM-NG-V41.11-0-ga27c415
(bootloader) aboot.git: git=MBM-NG-V41.11-0-g7d46a5a
(bootloader) qe: qe 0/1
(bootloader) ro.carrier: unknown
all: listed above
finished. total time: 0.055s
C:\Users\PC\Desktop\Tools\DeviceInfo>pause
Presione una tecla para continuar . . .
angelgzg said:
It seems like everything I do not change anything
Install recovery shows no error, but still comes out the same and yet so
C:\Users\PC\Desktop\Tools\DeviceInfo>mfastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 4111
(bootloader) product: falcon
(bootloader) secure: yes
(bootloader) hwrev: 0x83C0
(bootloader) radio: 0x1
(bootloader) emmc: 16GB Sandisk REV=06 PRV=07 TYPE=17
(bootloader) ram: 1024MB Samsung S4 SDRAM DIE=4Gb
(bootloader) cpu: MSM8226 CS
(bootloader) serialno: TA93005UU8
(bootloader) cid: 0x0009
(bootloader) channelid: 0x00
(bootloader) uid: C3A9C5020F000000000000000000
(bootloader) unlocked: yes
(bootloader) iswarrantyvoid: yes
(bootloader) mot_sst: 3
(bootloader) max-download-size: 536870912
(bootloader) reason: Volume down key pressed
(bootloader) imei:
(bootloader) meid:
(bootloader) date:
(bootloader) sku:
(bootloader) iccid:
(bootloader) cust_md5:
(bootloader) max-sparse-size: 268435456
(bootloader) current-time: "Wed Aug 6 14: 2:16 UTC 2014"
(bootloader) ro.build.fingerprint[0]: motorola/falcon_retuglb/falcon_umt
(bootloader) ro.build.fingerprint[1]: s:4.4.3/KXB21.14-L1.32/33:user/rel
(bootloader) ro.build.fingerprint[2]: ease-keys
(bootloader) ro.build.version.full[0]: Blur_Version.210.12.32.falcon_umt
(bootloader) ro.build.version.full[1]: s.Retail.en.US
(bootloader) ro.build.version.qcom[0]: AU_LINUX_ANDROID_LNX.LA.3.5.1_RB1
(bootloader) ro.build.version.qcom[1]: .04.04.02.048.020
(bootloader) version-baseband:
(bootloader) kernel.version[0]: Linux version 3.4.42-g26ca2df ([email protected]
(bootloader) kernel.version[1]: ilclbld54) (gcc version 4.7 (GCC) ) #1 S
(bootloader) kernel.version[2]: MP PREEMPT Fri May 30 11:08:03 CDT 2014
(bootloader) sdi.git: git=MBM-NG-V41.11-0-gdc5aeaf
(bootloader) sbl1.git: git=MBM-NG-V41.11-0-gcff5797
(bootloader) rpm.git: git=MBM-NG-V41.11-0-g71b1aae
(bootloader) tz.git: git=MBM-NG-V41.11-0-ga27c415
(bootloader) aboot.git: git=MBM-NG-V41.11-0-g7d46a5a
(bootloader) qe: qe 0/1
(bootloader) ro.carrier: unknown
all: listed above
finished. total time: 0.055s
C:\Users\PC\Desktop\Tools\DeviceInfo>pause
Presione una tecla para continuar . . .
Click to expand...
Click to collapse
Try the others 2 tools in the package. Don't worry I think your device is ok.
oversleeper said:
Try the others 2 tools in the package. Don't worry I think your device is ok.
Click to expand...
Click to collapse
What other options do I have?
Good Night, a pleasure
I have a problem with my motoG 2013 XT1032 unisim, the bootloader was blocked and I followed the steps to request the unlock key, using the commands fastboot oem get_unlock_data and then I went to the page of motorola and I got my email the key to unlocking, I introduced it after this command
fastboot oem unlock ......... (in the points goes the key)
Everything worked perfect I installed a rom 4.4.2 and the cell started without problems, then I made the biggest mistake that I got an update via ota and I gave him from that moment the phone was completely brickeo and I could save was with the blankflash , but from there the phone is in fastboot and tried to install the same flash but everything says denied permissions, when I check the screen well, I get device is LOCKED Status Code: 0. I understand that the bootloader is blocked again but when I try to perform The same steps of deblocking bootloader with this line tells me the following:
D: \ MotoG \ ADB Tools> fastboot oem get_unlock_data
...
(bootloader) Could not get unlock data!
OKAY [0.006s]
finished Total time: 0.011s
Then I thought it was because I already had the password, I entered the password and it says the following:
D: \ MotoG \ ADB Tools> fastboot oem unlock (CLAVE)
...
(bootloader) fastboot oem unlock disabled!
FAILED (remote failure)
finished Total time: 0.015s
Now when introducing
D: \ MotoG \ ADB Tools> fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 411A (*)
(bootloader) product: falcon
(bootloader) secure: yes
(bootloader) hwrev: 0x83C0
(bootloader) radio: 0x1
(bootloader) emmc: 16GB Sandisk REV = 06 PRV = 07 TYPE = 17
(bootloader) ram: 1024MB Elpida S4 SDRAM DIE = 4Gb
(bootloader) cpu: MSM8226 CS
(bootloader) serialno: 1c5580f
(bootloader) cid: 0xFFFF
(bootloader) channelid: 0xDEAD
(bootloader) uid: ABF178040F000000000000000000
(bootloader) unlocked: Not supported
(bootloader) iswarrantyvoid: Not supported
(bootloader) mot_sst: 8
(bootloader) max-download-size: 536870912
(bootloader) reason: Volume down key pressed
(bootloader) imei:
(bootloader) meid:
(bootloader) date:
(bootloader) sku:
(bootloader) iccid:
(bootloader) cust_md5:
(bootloader) max-sparse-size: 268435456
(bootloader) current-time:
(bootloader) ro.build.fingerprint:
(bootloader) ro.build.version.full:
(bootloader) ro.build.version.qcom:
(bootloader) version-baseband:
(bootloader) kernel.version:
(bootloader) sdi.git:
(bootloader) sbl1.git:
(bootloader) rpm.git:
(bootloader) tz.git:
(bootloader) aboot.git: git = MBM-NG-V41.1A-0-g80481ae
(bootloader) qe:
(bootloader) ro.carrier:
all: listed above
finished Total time: 0.103s
Please can you help me and see how to solve, excuse my english.
rcheo22 said:
Good Night, a pleasure
I have a problem with my motoG 2013 XT1032 unisim, the bootloader was blocked and I followed the steps to request the unlock key, using the commands fastboot oem get_unlock_data and then I went to the page of motorola and I got my email the key to unlocking, I introduced it after this command
fastboot oem unlock ......... (in the points goes the key)
Everything worked perfect I installed a rom 4.4.2 and the cell started without problems, then I made the biggest mistake that I got an update via ota and I gave him from that moment the phone was completely brickeo and I could save was with the blankflash , but from there the phone is in fastboot and tried to install the same flash but everything says denied permissions, when I check the screen well, I get device is LOCKED Status Code: 0. I understand that the bootloader is blocked again but when I try to perform The same steps of deblocking bootloader with this line tells me the following:
D: \ MotoG \ ADB Tools> fastboot oem get_unlock_data
...
(bootloader) Could not get unlock data!
OKAY [0.006s]
finished Total time: 0.011s
Then I thought it was because I already had the password, I entered the password and it says the following:
D: \ MotoG \ ADB Tools> fastboot oem unlock (CLAVE)
...
(bootloader) fastboot oem unlock disabled!
FAILED (remote failure)
finished Total time: 0.015s
Now when introducing
D: \ MotoG \ ADB Tools> fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 411A (*)
(bootloader) product: falcon
(bootloader) secure: yes
(bootloader) hwrev: 0x83C0
(bootloader) radio: 0x1
(bootloader) emmc: 16GB Sandisk REV = 06 PRV = 07 TYPE = 17
(bootloader) ram: 1024MB Elpida S4 SDRAM DIE = 4Gb
(bootloader) cpu: MSM8226 CS
(bootloader) serialno: 1c5580f
(bootloader) cid: 0xFFFF
(bootloader) channelid: 0xDEAD
(bootloader) uid: ABF178040F000000000000000000
(bootloader) unlocked: Not supported
(bootloader) iswarrantyvoid: Not supported
(bootloader) mot_sst: 8
(bootloader) max-download-size: 536870912
(bootloader) reason: Volume down key pressed
(bootloader) imei:
(bootloader) meid:
(bootloader) date:
(bootloader) sku:
(bootloader) iccid:
(bootloader) cust_md5:
(bootloader) max-sparse-size: 268435456
(bootloader) current-time:
(bootloader) ro.build.fingerprint:
(bootloader) ro.build.version.full:
(bootloader) ro.build.version.qcom:
(bootloader) version-baseband:
(bootloader) kernel.version:
(bootloader) sdi.git:
(bootloader) sbl1.git:
(bootloader) rpm.git:
(bootloader) tz.git:
(bootloader) aboot.git: git = MBM-NG-V41.1A-0-g80481ae
(bootloader) qe:
(bootloader) ro.carrier:
all: listed above
finished Total time: 0.103s
Please can you help me and see how to solve, excuse my english.
Click to expand...
Click to collapse
try factory reset.
I'm just about ready to throw the G4 Plus in the bin, but before I do, I thought I'd give it one last chance.
Have been following instructions from https://forum.xda-developers.com/general/rooting-roms/real-official-stock-rom-xt1625-xt1642-t3575895 for example.
fastboot flash recovery recovery.img
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
(bootloader) has-slot:recovery: not found
target reported max download size of 536870912 bytes
sending 'recovery' (16484 KB)...
OKAY [ 0.563s]
writing 'recovery'...
(bootloader) Invalid partition name recovery
FAILED (remote failure)
finished. total time: 0.576s
So I think the invalid partition name recovery is an issue. Not sure how or why it got deleted, but I see that sku and imei are also set to [0000000000]
fastboot getvar all
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
(bootloader) version: 0.5
(bootloader) version-bootloader: moto-msm8952-B1.06(*)
(bootloader) product: athene_16mp
(bootloader) board: athene_16mp
(bootloader) secure: yes
(bootloader) hwrev: P2A
(bootloader) radio: 3
(bootloader) storage-type: emmc
(bootloader) emmc: 32GB SAMSUNG RX1BMB RV=08 PV=07 FV=0000000000000007
(bootloader) ram: 3GB SAMSUNG LP3 DIE=6Gb M5=01 M6=05 M7=00 M8=7B
(bootloader) cpu: MSM8952
(bootloader) serialno: 2931de5e
(bootloader) cid: 0x0032
(bootloader) channelid: 0x51
(bootloader) uid: 7AC8590200000000000000000000
(bootloader) securestate: oem_locked
(bootloader) iswarrantyvoid: yes
(bootloader) max-download-size: 536870912
(bootloader) reason: Failed to initialize partition table
(bootloader) imei: 000000000000000
(bootloader) meid:
(bootloader) date: 01-01-1970
(bootloader) sku: 000000000000000
(bootloader) battid:
(bootloader) iccid:
(bootloader) cust_md5:
(bootloader) max-sparse-size: 268435456
(bootloader) current-time:
(bootloader) ro.build.fingerprint:
(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) hyp.git: hyp.git
(bootloader) keymaster.git: keymaster.git
(bootloader) cmnlib.git: cmnlib.git
(bootloader) aboot.git: git=MBM-NG-VB1.06-0-g0edfb0d
(bootloader) qe:
(bootloader) frp-state: no protection (err)
(bootloader) ro.carrier:
all: listed above
finished. total time: 0.175s
I'm sorry I am really a complete noob to Android OS, so I don't fully understand what all this means. I just want to get my phone working again.
Any ideas please?
I've tried RSD Lite and Rescue & Smart Assistant, but neither of these seem to recognize the phone.
Hi, I have installed a custom rom and unintentionally stopped the installation process.
The oem is locked and won't let me unlock.
Start Up Failed
No Bootable A/B slot
Failed to boot Linux, falling back fastboot
TheKillerMaxOfficial said:
Hi, I have installed a custom rom and unintentionally stopped the installation process.
The oem is locked and won't let me unlock.
Start Up Failed
No Bootable A/B slot
Failed to boot Linux, falling back fastboot
Click to expand...
Click to collapse
You relocked bootloader or it relocked it self?
sd_shadow said:
You relocked bootloader or it relocked it self?
Click to expand...
Click to collapse
it self
TheKillerMaxOfficial said:
it self
Click to expand...
Click to collapse
I'm not sure what causes the problem, or what the issue really is, could be corrupt bootloader.
Only fix I've seen is boot to EDL mode and use a blankflash.
You can try LMSA' Flash rescue first
https://forum.xda-developers.com/general/general/update-moto-lenovo-moto-smart-assistant-t3951714
Not likely to fix but worth trying.
Assuming that doesn't work run
Getvar all
Code:
fastboot getvar all
To see device info, and post here.
Then try
Code:
fastboot oem blankflash
If that works device screen will turn black, and Window device manager will list it as a Qualcomm device.
If you get an error with that command you need to try booting Twrp and use
Code:
adb boot edl
You then need a blankflash for your device
You likely have Ocean, getvar all will tell.
If so try these
lolinet mirrors - firmware, software, iso etc.
lolinet mirrors - powered by h5ai
mirrors.lolinet.com
sd_shadow said:
I'm not sure what causes the problem, or what the issue really is, could be corrupt bootloader.
Only fix I've seen is boot to EDL mode and use a blankflash.
You can try LMSA' Flash rescue first
https://forum.xda-developers.com/general/general/update-moto-lenovo-moto-smart-assistant-t3951714
Not likely to fix but worth trying.
Assuming that doesn't work run
Getvar all
Code:
fastboot getvar all
To see device info, and post here.
Then try
Code:
fastboot oem blankflash
If that works device screen will turn black, and Window device manager will list it as a Qualcomm device.
If you get an error with that command you need to try booting Twrp and use
Code:
adb boot edl
You then need a blankflash for your device
You likely have Ocean, getvar all will tell.
If so try these
lolinet mirrors - firmware, software, iso etc.
lolinet mirrors - powered by h5ai
mirrors.lolinet.com
Click to expand...
Click to collapse
(bootloader) version: 0.5
(bootloader) version-bootloader: MBM-2.1-ocean_retail-7fd887897c6-200930
(bootloader) product: ocean
(bootloader) board: ocean
(bootloader) secure: yes
(bootloader) hwrev: PVT1
(bootloader) radio: 3
(bootloader) storage-type: emmc
(bootloader) emmc: 64GB MICRON S0J9N8 RV=08 PV=10 FV=0000000000000004
(bootloader) ram: 4GB MICRON LP3 DIE=8Gb M5=FF M6=01 M7=00 M8=5F
(bootloader) cpu: SDM632
(bootloader) serialno: f104484
(bootloader) cid: 0xDEAD
(bootloader) channelid: 0x00
(bootloader) uid: 0000000000000000000000000000
(bootloader) securestate: oem_locked
(bootloader) factory-modes: disabled
(bootloader) iswarrantyvoid: n/a
(bootloader) max-download-size: 536870912
(bootloader) reason: Failed to initialize partition table
(bootloader) imei:
(bootloader) imei2:
(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: 1
(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-7fd887897c6-200930
(bootloader) frp-state: no protection (err)
(bootloader) ro.carrier:
(bootloader) current-slot:
(bootloader) running-boot-lun: must + g->mlen
(bootloader) running-slot:
(bootloader) slot-suffixes: _a
(bootloader) slot-count: 1
(bootloader) slot-successful:_a: INVALID
(bootloader) slot-successful:_b: INVALID
(bootloader) slot-bootable:_a: INVALID
(bootloader) slot-bootable:_b: INVALID
(bootloader) slot-retry-count:_a: unknown
(bootloader) slot-retry-count:_b: unknown
(bootloader) pcb-part-no:
all: listed above
finished. total time: 0.144s
sd_shadow said:
I'm not sure what causes the problem, or what the issue really is, could be corrupt bootloader.
Only fix I've seen is boot to EDL mode and use a blankflash.
You can try LMSA' Flash rescue first
https://forum.xda-developers.com/general/general/update-moto-lenovo-moto-smart-assistant-t3951714
Not likely to fix but worth trying.
Assuming that doesn't work run
Getvar all
Code:
fastboot getvar all
To see device info, and post here.
Then try
Code:
fastboot oem blankflash
If that works device screen will turn black, and Window device manager will list it as a Qualcomm device.
If you get an error with that command you need to try booting Twrp and use
Code:
adb boot edl
You then need a blankflash for your device
You likely have Ocean, getvar all will tell.
If so try these
lolinet mirrors - firmware, software, iso etc.
lolinet mirrors - powered by h5ai
mirrors.lolinet.com
Click to expand...
Click to collapse
Motorola qboot utility version 3.40
[ 0.000] Opening device: \\.\COM3
[ 0.001] Detecting device
[ 4.057] ERROR: sahara_greet_device()->change_mode()->do_hello()->IO error
[ 4.057] Check qboot_log.txt for more details
[ 4.057] Total time: 4.060s
FAILED: qb_flash_singleimage()->sahara_greet_device()->change_mode()->do_hello()->IO error
TheKillerMaxOfficial said:
(bootloader) version: 0.5
(bootloader) version-bootloader: MBM-2.1-ocean_retail-7fd887897c6-200930
(bootloader) product: ocean
(bootloader) board: ocean
(bootloader) secure: yes
(bootloader) hwrev: PVT1
(bootloader) radio: 3
(bootloader) storage-type: emmc
(bootloader) emmc: 64GB MICRON S0J9N8 RV=08 PV=10 FV=0000000000000004
(bootloader) ram: 4GB MICRON LP3 DIE=8Gb M5=FF M6=01 M7=00 M8=5F
(bootloader) cpu: SDM632
(bootloader) serialno: f104484
(bootloader) cid: 0xDEAD
(bootloader) channelid: 0x00
(bootloader) uid: 0000000000000000000000000000
(bootloader) securestate: oem_locked
(bootloader) factory-modes: disabled
(bootloader) iswarrantyvoid: n/a
(bootloader) max-download-size: 536870912
(bootloader) reason: Failed to initialize partition table
(bootloader) imei:
(bootloader) imei2:
(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: 1
(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-7fd887897c6-200930
(bootloader) frp-state: no protection (err)
(bootloader) ro.carrier:
(bootloader) current-slot:
(bootloader) running-boot-lun: must + g->mlen
(bootloader) running-slot:
(bootloader) slot-suffixes: _a
(bootloader) slot-count: 1
(bootloader) slot-successful:_a: INVALID
(bootloader) slot-successful:_b: INVALID
(bootloader) slot-bootable:_a: INVALID
(bootloader) slot-bootable:_b: INVALID
(bootloader) slot-retry-count:_a: unknown
(bootloader) slot-retry-count:_b: unknown
(bootloader) pcb-part-no:
all: listed above
finished. total time: 0.144s
Click to expand...
Click to collapse
Looks pretty much like I've been seeing where only thing that works is a blankflash.
And Ocean is your device name
TheKillerMaxOfficial said:
Motorola qboot utility version 3.40
[ 0.000] Opening device: \\.\COM3
[ 0.001] Detecting device
[ 4.057] ERROR: sahara_greet_device()->change_mode()->do_hello()->IO error
[ 4.057] Check qboot_log.txt for more details
[ 4.057] Total time: 4.060s
FAILED: qb_flash_singleimage()->sahara_greet_device()->change_mode()->do_hello()->IO error
Click to expand...
Click to collapse
You may need to install Qualcomm driver and a newer blankflash version
There are several threads about this, may have to do some searching, often the newest versions are posted in the telegram group for g7 power
sd_shadow said:
Looks pretty much like I've been seeing where only thing that works is a blankflash.
And Ocean is your device name
Click to expand...
Click to collapse
it won't let me boot twrp, I didn't have it installed as recovery
sd_shadow said:
You may need to install Qualcomm driver and a newer blankflash version
There are several threads about this, may have to do some searching, often the newest versions are posted in the telegram group for g7 power
Click to expand...
Click to collapse
I don't know much about it and I don't know what else to do.
TheKillerMaxOfficial said:
it won't let me boot twrp, I didn't have it installed as recovery
Click to expand...
Click to collapse
Did you try
Code:
fastboot oem blankflash
sd_shadow said:
You may need to install Qualcomm driver and a newer blankflash version
There are several threads about this, may have to do some searching, often the newest versions are posted in the telegram group for g7 power
Click to expand...
Click to collapse
If you can find something to solve my problem, I would be very grateful.
sd_shadow said:
Did you try
Code:
fastboot oem blankflash
Click to expand...
Click to collapse
waiting for device
TheKillerMaxOfficial said:
waiting for device
Click to expand...
Click to collapse
How is it listed in device manager?
sd_shadow said:
How is it listed in device manager?
Click to expand...
Click to collapse
does not appear
TheKillerMaxOfficial said:
does not appear
Click to expand...
Click to collapse
It's there, you need to search for it, it maybe hidden in a collapsed section
sd_shadow said:
It's there, you need to search for it, it maybe hidden in a collapsed section
Click to expand...
Click to collapse
Qualcomm HS-USB QDLoader 9008 (COM3)
TheKillerMaxOfficial said:
Qualcomm HS-USB QDLoader 9008 (COM3)
Click to expand...
Click to collapse
Ok so it's in EDL mode
Try rebooting PC
sd_shadow said:
Ok so it's in EDL mode
Try rebooting PC
Click to expand...
Click to collapse
I already restarted it, what's next?
TheKillerMaxOfficial said:
I already restarted it, what's next?
Click to expand...
Click to collapse
try
[Guide] Recovering from a hard brick
This guide aims to recover your G7 power from a hard brick that leaves it in emergency download (EDL) mode. Will this work with my device? This should work on any device in EDL mode. To check for this mode, first try entering fastboot by...
forum.xda-developers.com
Hi Everyone!
I'm new here and need help with my LAKE XT1965-2 stuck on "your device is corrupt. it can´t be trusted and will not boot" So i know that have some smart solutions here but, all i tried was unsuccessful and i know that have a lot of Brazilians here (kkkk e ai man, sussa?) someone have a solution for this one?
Things i tried:
* LSMA - By Fastboot (Yes, i can go to fastboot but, aways receive a "Primary Partition fail message"
* ADB - command by command one at one, unfortunately unsuccessful.
* RSD LITE - Fail =(
* LAST one - EDL also unsuccessful
My device is NOT with debugging enabled and NOT bootloader unlocked. Any ideias?
Here is my GETVAR ALL:
Code:
D:\Lake Rom\minimal_adb_fastboot_1.4.3_portable>fastboot getvar all
(bootloader) kernel: uefi
(bootloader) version-bootloader: MBM-3.0-lake_retail-38523c9489-200524
(bootloader) product: lake
(bootloader) board: lake
(bootloader) secure: yes
(bootloader) hwrev: PVT
(bootloader) radio: LATAM
(bootloader) storage-type: eMMC
(bootloader) emmc: 64GB MICRON S0J9K8 RV=08 PV=10 FV=0000000000000004
(bootloader) ufs: N/A
(bootloader) ram: 4GB MICRON LP4 DIE=16Gb M5=FF M6=04 M7=10 M8=10
(bootloader) cpu: SDM636 1.0 (1)
(bootloader) serialno: 0054198036
(bootloader) cid: 0xDEAD
(bootloader) channelid: 0x00
(bootloader) uid: 00000000
(bootloader) securestate: oem_locked
(bootloader) verity-state: enforcing (0)
(bootloader) iswarrantyvoid: yes
(bootloader) max-download-size: 536870912
(bootloader) reason: Volume down key pressed
(bootloader) imei: 355577093484259
(bootloader) meid:
(bootloader) date: 02-12-2019
(bootloader) sku: XT1965-2
(bootloader) carrier_sku: XT1965-2
(bootloader) battid: SB18C36892
(bootloader) battery-voltage: 4274
(bootloader) iccid:
(bootloader) cust_md5:
(bootloader) max-sparse-size: 268435456
(bootloader) ro.build.fingerprint[0]: motorola/lake_n/lake_n:10/QPWS30.6
(bootloader) ro.build.fingerprint[1]: 1-21-11/e25a6:user/release-keys
(bootloader) poweroffalarm: 0
(bootloader) ro.build.version.full: <not found>
(bootloader) ro.build.version.qcom: LA.UM.8.2.r1-04300-sdm660.0
(bootloader) version-baseband: M636_13.45.02.60R LAKE_LATAMDSDS_CUST
(bootloader) kernel.version[0]: Linux version 4.4.192-perf+ ([email protected]
(bootloader) kernel.version[1]: oid-build) (gcc version 4.9.x 20150123 (
(bootloader) kernel.version[2]: prerelease) (GCC) ) #1 SMP PREEMPT Sun M
(bootloader) kernel.version[3]: ay 24 11:04:26 CDT 2020
(bootloader) git:abl: MBM-3.0-lake_retail-38523c9489-200524
(bootloader) git:xbl: MBM-3.0-lake_retail-efaf0cccb-200524
(bootloader) gitmic: MBM-3.0-lake_retail-efaf0cccb-200524
(bootloader) git:rpm: MBM-3.0-lake_retail-0dc899d-200524
(bootloader) git:tz: MBM-3.0-lake_retail-a1c95bed3-dirty-200524
(bootloader) git:hyp: MBM-3.0-lake_retail-a1c95bed3-dirty-200524
(bootloader) git:devcfg: MBM-3.0-lake_retail-a1c95bed3-dirty-200524
(bootloader) git:cmnlib: MBM-3.0-lake_retail-a1c95bed3-dirty-200524
(bootloader) git:cmnlib64: MBM-3.0-lake_retail-a1c95bed3-dirty-200524
(bootloader) git:keymaster: MBM-3.0-lake_retail-a1c95bed3-dirty-200524
(bootloader) gitrov: MBM-3.0-lake_retail-a1c95bed3-dirty-200524
(bootloader) git:storsec: MBM-3.0-lake_retail-a1c95bed3-dirty-200524
(bootloader) frp-state: protected (77)
(bootloader) ro.carrier: retbr
(bootloader) current-slot: a
(bootloader) running-bl-slot: _a/_a
(bootloader) running-boot-lun: 0
(bootloader) slot-count: 2
(bootloader) slot-successful:_a: yes
(bootloader) slot-successful:_b: yes
(bootloader) slot-unbootable:_a: no
(bootloader) slot-unbootable:_b: yes
(bootloader) slot-retry-count:_a: 6
(bootloader) slot-retry-count:_b: 6
all: listed above
finished. total time: 0.254s
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Richteeer said:
My device is NOT with debugging enabled and NOT bootloader unlocked. Any ideias?
Click to expand...
Click to collapse
That's the main problem you have.
Your phone has A/B partition layout hence its recovery partition is part of boot partition. Everything is managed by the boot partition now. Thus you now boot the recovery into the boot partition rather than flashing it to the non-existing recovery partition.
So this is my recommendation: boot into a custom recovery like TWRP and from therein flash a Custom ROM:
Code:
fastboot devices
fastboot boot twrp.img
jwoegerbauer said:
That's the main problem you have.
Your phone has A/B partition layout hence its recovery partition is part of boot partition. Everything is managed by the boot partition now. Thus you now boot the recovery into the boot partition rather than flashing it to the non-existing recovery partition.
So booting into a custom recovery like TWRP is required to flash a Custom ROM:
Code:
fastboot devices
fastboot boot twrp.img
Click to expand...
Click to collapse
Good idea but, here we have:
Code:
downloading 'boot.img'...
OKAY [ 0.734s]
booting...
(bootloader) permission denied!
FAILED (remote failure)
finished. total time: 0.754s
Wondering why you don't carefully read posts?
jwoegerbauer said:
Wondering why you don't carefully read posts?
Click to expand...
Click to collapse
I think I missed something, can you help me?
I'm new here, thanks for your patience
Richteeer said:
Hi Everyone!
I'm new here and need help with my LAKE XT1965-2 stuck on "your device is corrupt. it can´t be trusted and will not boot" So i know that have some smart solutions here but, all i tried was unsuccessful and i know that have a lot of Brazilians here (kkkk e ai man, sussa?) someone have a solution for this one?
Things i tried:
* LSMA - By Fastboot (Yes, i can go to fastboot but, aways receive a "Primary Partition fail message"
* ADB - command by command one at one, unfortunately unsuccessful.
* RSD LITE - Fail =(
* LAST one - EDL also unsuccessful
My device is NOT with debugging enabled and NOT bootloader unlocked. Any ideias?
Here is my GETVAR ALL:
Code:
D:\Lake Rom\minimal_adb_fastboot_1.4.3_portable>fastboot getvar all
(bootloader) kernel: uefi
(bootloader) version-bootloader: MBM-3.0-lake_retail-38523c9489-200524
(bootloader) product: lake
(bootloader) board: lake
(bootloader) secure: yes
(bootloader) hwrev: PVT
(bootloader) radio: LATAM
(bootloader) storage-type: eMMC
(bootloader) emmc: 64GB MICRON S0J9K8 RV=08 PV=10 FV=0000000000000004
(bootloader) ufs: N/A
(bootloader) ram: 4GB MICRON LP4 DIE=16Gb M5=FF M6=04 M7=10 M8=10
(bootloader) cpu: SDM636 1.0 (1)
(bootloader) serialno: 0054198036
(bootloader) cid: 0xDEAD
(bootloader) channelid: 0x00
(bootloader) uid: 00000000
(bootloader) securestate: oem_locked
(bootloader) verity-state: enforcing (0)
(bootloader) iswarrantyvoid: yes
(bootloader) max-download-size: 536870912
(bootloader) reason: Volume down key pressed
(bootloader) imei: 355577093484259
(bootloader) meid:
(bootloader) date: 02-12-2019
(bootloader) sku: XT1965-2
(bootloader) carrier_sku: XT1965-2
(bootloader) battid: SB18C36892
(bootloader) battery-voltage: 4274
(bootloader) iccid:
(bootloader) cust_md5:
(bootloader) max-sparse-size: 268435456
(bootloader) ro.build.fingerprint[0]: motorola/lake_n/lake_n:10/QPWS30.6
(bootloader) ro.build.fingerprint[1]: 1-21-11/e25a6:user/release-keys
(bootloader) poweroffalarm: 0
(bootloader) ro.build.version.full: <not found>
(bootloader) ro.build.version.qcom: LA.UM.8.2.r1-04300-sdm660.0
(bootloader) version-baseband: M636_13.45.02.60R LAKE_LATAMDSDS_CUST
(bootloader) kernel.version[0]: Linux version 4.4.192-perf+ ([email protected]
(bootloader) kernel.version[1]: oid-build) (gcc version 4.9.x 20150123 (
(bootloader) kernel.version[2]: prerelease) (GCC) ) #1 SMP PREEMPT Sun M
(bootloader) kernel.version[3]: ay 24 11:04:26 CDT 2020
(bootloader) git:abl: MBM-3.0-lake_retail-38523c9489-200524
(bootloader) git:xbl: MBM-3.0-lake_retail-efaf0cccb-200524
(bootloader) gitmic: MBM-3.0-lake_retail-efaf0cccb-200524
(bootloader) git:rpm: MBM-3.0-lake_retail-0dc899d-200524
(bootloader) git:tz: MBM-3.0-lake_retail-a1c95bed3-dirty-200524
(bootloader) git:hyp: MBM-3.0-lake_retail-a1c95bed3-dirty-200524
(bootloader) git:devcfg: MBM-3.0-lake_retail-a1c95bed3-dirty-200524
(bootloader) git:cmnlib: MBM-3.0-lake_retail-a1c95bed3-dirty-200524
(bootloader) git:cmnlib64: MBM-3.0-lake_retail-a1c95bed3-dirty-200524
(bootloader) git:keymaster: MBM-3.0-lake_retail-a1c95bed3-dirty-200524
(bootloader) gitrov: MBM-3.0-lake_retail-a1c95bed3-dirty-200524
(bootloader) git:storsec: MBM-3.0-lake_retail-a1c95bed3-dirty-200524
(bootloader) frp-state: protected (77)
(bootloader) ro.carrier: retbr
(bootloader) current-slot: a
(bootloader) running-bl-slot: _a/_a
(bootloader) running-boot-lun: 0
(bootloader) slot-count: 2
(bootloader) slot-successful:_a: yes
(bootloader) slot-successful:_b: yes
(bootloader) slot-unbootable:_a: no
(bootloader) slot-unbootable:_b: yes
(bootloader) slot-retry-count:_a: 6
(bootloader) slot-retry-count:_b: 6
all: listed above
finished. total time: 0.254s
View attachment 5277135
Click to expand...
Click to collapse
Try flashing
fastboot oem fb_mode_set
fastboot flash partition gpt.bin
fastboot oem fb_mode_clear
then try LMSA again
sd_shadow said:
Try flashing
fastboot oem fb_mode_set
fastboot flash partition gpt.bin
fastboot oem fb_mode_clear
then try LMSA again
Click to expand...
Click to collapse
Hi Sd_Shadow
I´ve got this error with fastboot commands:
Code:
C:\QPWS30.61-21-11>fastboot oem fb_mode_set
...
FAILED (remote failure)
finished. total time: 0.006s
C:\QPWS30.61-21-11>fastboot flash partition gpt.bin
target max-sparse-size: 256MB
sending 'partition' (37 KB)...
OKAY [ 0.005s]
writing 'partition'...
(bootloader) Validating 'gpt.default.xml'
(bootloader) Committing 'gpt.default.xml'
(bootloader) - flashing 'gpt_main0.bin' to 'partition:0'
(bootloader) Failed to commit transaction!
(bootloader) Transaction cancelled!
FAILED (remote failure)
finished. total time: 0.034s
C:\QPWS30.61-21-11>fastboot oem fb_mode_clear
...
FAILED (remote failure)
finished. total time: 0.014s