Database Users

[FIX] fix hard brick / qhsub_bulk after bad flash / cm12 flash from 5.1

First of all:Remember:im just making a thread, all of this wasn´t possible if not for @ccfries(He works at motorola, and sent the files to shamu´s device tree repo)
and @Casper34
See: http://forum.xda-developers.com/showpost.php?p=59562745&postcount=9 and https://android-review.googlesource.com/#/c/143010/
Requirements:
Motorola Drivers:
http://storage.googleapis.com/tetheredupgrades/MotorolaDeviceManager_2.5.4.exe
Qualcomm Drivers:
http://forum.xda-developers.com/attachment.php?attachmentid=631288&d=1308601930
Optional: If having issues use:
http://forum.xda-developers.com/showthread.php?t=2263822
Unbrick Stuff:
https://www.dropbox.com/s/8783ohne2mufiwc/Nexus6Unbrick.rar?dl=0
or
https://drive.google.com/file/d/0BwduAK2l37Oaa1BQZncwaEpNb1E/view?usp=sharing
Factory Images for Nexus 6(needs to be 5.1)
https://dl.google.com/dl/android/aosp/shamu-lmy47d-factory-6c44d402.tgz
or via RSD Lite
http://motofirmware.center/files/file/1069-shamu-lmy47e-release-keys-subsidy-default-cfcxmlzip/
FASTBOOT AND ADB NEEDS TO BE ALREADY SETTED UP
Pre Requirements:
- Disable driver signature checking
Windows 7:
https://www.youtube.com/watch?v=k4RwaI4mn6Y
Windows 8:
https://learn.sparkfun.com/tutorial...abling-signed-driver-enforcement-on-windows-8
Windows 8.1:
http://www.howtogeek.com/167723/how...8.1-so-that-you-can-install-unsigned-drivers/
- Install the drivers:
Go to device manager, Unknown devices, double click qhusb_bulk, install driver, select location and select where you extracted the drivers.
{
"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"
}
- Next you should extract both zip files (Unbrick and factory images)
- Then Connect your nexus 6 on your computer (now should appear as Qualcomm HS-USB QD-Loader 9008 under "COM PORTS"):
- Open the Unbrick folder and run blank-flash.bat:
- Flash Stock factory images: (Problems see #2)
Your phone should show up on the computer as fastboot.Just flash stock factory images. (Motorola via "RSD Lite" or Google one should do the trick).
Thanks:
@ccfries(HUGE Thanks to him, turns out he is the one who made the commit with the necessary files, props to him!)
@Casper34 (Huge help with his working nexus 6)
@bitdomo (helped me a lot, and i got some images from another thread of his)

Problems that may occur during or after:
Stuck at waiting for device
Check if drivers are installed correctly and restart pc
Check if you have an updated fastboot
THESE TWO ARE THE MAIN REASON OF PROBLEMS (mostly outdated fastboot)
-Drivers
http://forum.xda-developers.com/showthread.php?t=2263822
http://storage.googleapis.com/tetheredupgrades/MotorolaDeviceManager_2.5.4.exe
Fastboot:
http://forum.xda-developers.com/showthread.php?t=2317790
Problems while flashing factory images:
ccfries said:
First, fastboot flash partition gpt.bin
Then flash the other images.
If you just bricked by downgrading bootloader, the persist and modem calibration should still be happily where it was when you started.
This won't help you if you're stuck with Allow OEM Unlock. Be careful locking on 5.1. There's accurate information elsewhere in the forum on that.
-Chris
Click to expand...
Click to collapse
PS:
ccfries said:
If you lock, it clears the setting by design, so you can't lock and unlock without booting up and checking the box.
Click to expand...
Click to collapse
Wifi / Bluetooh dosen´t work:
See http://forum.xda-developers.com/showpost.php?p=59561966&postcount=3
No IMEI / No Signal
Restore EFS Backup

If wifi/bt/camera dosen´t work Then probably your /persist got somehow corrupted. (Post Under construction)
For a fix:
Flash a custom recovery, and open a terminal with the phone booted to it
run
umount /persist
mkdir /persist
mount /dev/block/platform/msm_sdcc.1/by-name/persist /persist
#e2fsck /dev/block/platform/msm_sdcc.1/by-name/persist
you will be propmpted to check / repair errors, keep pressing enter for each that it appears
then run
umount /perist
and reboot phone

Wow! Very nice. I bet you just saved some poor guys from getting yelled at from wifey. Good job and thanks for helping the community. :highfive:

wow indeed!

jayharper08 said:
Wow! Very nice. I bet you just saved some poor guys from getting yelled at from wifey. Good job and thanks for helping the community. :highfive:
Click to expand...
Click to collapse
simms22 said:
wow indeed!
Click to expand...
Click to collapse
Thanks to both, thankfully cm already merged a check for the bootloader, but i hope this can fix phones that are already bricked for people who cant use warranty (outside area, on a trip, etc).
Oh yeah, or in the case of my friend, his mom

This needs stickied
Sent from my Nexus 6 using XDA Free mobile app

@opssemnik
No worries, glad to help out!
Sent from my Nexus 6

opssemnik said:
@ccfries(Huge thanks for him, for finding an un merged commit that had the partition layout)!.
Click to expand...
Click to collapse
I authored the commit this afternoon so finding it was pretty easy. :good:

ccfries said:
I authored the commit this afternoon so finding it was pretty easy. :good:
Click to expand...
Click to collapse
Oh no wait, I DIDN´T SEE THE AUTHOR LOL.
may i ask was it hard for you to get the permission to post? afaik these files are proprietary (aside from the paritition table) or aren´t they?.
also can i ask you something a bit more offtopic?
i noticied the nexus 6 works directly with QPST (at least it can communicate with it)
but some other devices (like the nexus 5) can´t, its something that qualcomm or the manufacturer decide / make?
Once again ,props to you and motorola!
Never thought of an oem doing that, even more that the bricks can only be achieved when messing with things you shouldnt be :good::good::good:

Erm, don't mind me asking one question.
How do you back up your efs if your phone is bricked?

So I thought I would rid myself of no Xposed or CM12 on 5.1 (LMY47D) by going back to 5.0.1 and flashing CM12 again from an older nightly I had downloaded already....I think we all know what happened.
I managed to get through it all and have the blank-flash boot loader screen up but I get hung up on <waiting for device> when trying to flash factory image (LMY45D). The boot loader shows as locked and as a result I am unable to flash a factory image. Hopefully I am not breaking any rules or anything by posting this here but this is the error I am getting when running the flash-all.sh:
target reported max download size of 536870912 bytes
sending 'bootloader' (3807 KB)...
OKAY [ 0.131s]
writing 'bootloader'...
(bootloader) Motoboot: Unknown partition name
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 0.181s
rebooting into bootloader...
OKAY [ 0.001s]
finished. total time: 0.001s
target reported max download size of 536870912 bytes
sending 'radio' (85422 KB)...
OKAY [ 2.769s]
writing 'radio'...
(bootloader) Motoboot: Unknown partition name
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 2.772s
rebooting into bootloader...
OKAY [ 0.001s]
finished. total time: 0.001s
target reported max download size of 536870912 bytes
archive does not contain 'boot.sig'
archive does not contain 'recovery.sig'
fastboot(665,0xa03911d4) malloc: *** mach_vm_map(size=1779851264) failed (error code=3)
*** error: can't allocate region
*** set a breakpoint in malloc_error_break to debug
failed to allocate 1778070480 bytes
error: update package missing system.img​
and when I try to run em unlock:
fastboot oem unlock
...
(bootloader) Check 'Allow OEM Unlock' in Developer Options.
FAILED (remote failure)
finished. total time: 0.002s​

Looks good. Does this only help the CM12 people or does it override the "enable OEM Unlock" people too?

serdaj said:
(bootloader) Motoboot: Unknown partition name
(bootloader) Preflash validation failed
Click to expand...
Click to collapse
First, fastboot flash partition gpt.bin
Then, fastboot reboot-bootloader
Then flash the other images.
If you just bricked by downgrading bootloader, the persist and modem calibration should still be happily where it was when you started.
This won't help you if you're stuck with Allow OEM Unlock. Be careful locking on 5.1. There's accurate information elsewhere in the forum on that.
-Chris

Damn, wish this was on here last week. Had to send my N6 off to repair centre for this as I thought it was a gonner. Fault diagnosed as 'Electrical issue - Replacement required'. Replacement is coming tomorrow hopefully. Will bookmark this, thanks.

Delboyd12 said:
Damn, wish this was on here last week. Had to send my N6 off to repair centre for this as I thought it was a gonner. Fault diagnosed as 'Electrical issue - Replacement required'. Replacement is coming tomorrow hopefully. Will bookmark this, thanks.
Click to expand...
Click to collapse
That was when he started this.... After many bricks. I know a lot of people RMAed their phones, but this can still help others!

ccfries said:
This won't help you if you're stuck with Allow OEM Unlock. Be careful locking on 5.1.
Click to expand...
Click to collapse
It would be helpful if the OP would add this to his first post.

@opssemnik Great Job can you please help me to do so with my HTC One M8 ?
i had the same problem " qualcomm hs-usb qdloader 9008 "
Thanks

bradputt said:
Erm, don't mind me asking one question.
How do you back up your efs if your phone is bricked?
Click to expand...
Click to collapse
Restore he wrote
Shamu/Hammerhead/Flounder Dkwhq www.jsand.dk

Please can someone help me?
I am stuck in the bootloader, which is locked. I can't boot the phone up. I am trying to flash stock images but nothing is happening. Just booting to the bootloader every time.
I can detect my device using fastboot devices, but every time I try and write an img it fails, because the bootloader's locked! Argh!
Thanks in advance,
Tom

[HELP] Problem flashing TWRP recovery on ZUI

Hello, i have a problem flashing custom recovery TWRP on ZUI.
below are the details of the problems:
ZUI Version: 1.2.040
Unlock Bootloader: YES (I feel a bit sketch on this part, because the process does not wipe any data)
Custom recovery to be installed: Un-Official 2.8.7.0 TWRP Recovery for ZUK Z1 by Breadcrust
1. when i try to flash the recovery on fastboot mode, it gives me this:
writing 'recovery'...
FAILED (remote : Invalid data)
finished. total time" 0.418s
2. when i try boot the recovery on fastboot mode, it also gives error:
downloading 'boot.img'...
OKAY [0.362s]
booting...
FAILED (remote: bootimage: incomplete or not signed)
finished. total time: 0.369s
* For the solution, i have tried kingroot to allow root access ---> NOT SUCCESFULL
** For 2nd solution, i have tried downgrading the ZUI version ----> NOT SUCCESFULL (cannot get into qdloader mode long enough).
*** I also have tried re-downloading the recovery image without using download accelarator (IDM) ---> NOT SUCCESFULL
edit: please... if somebody know the problem, please teach me how to overcome the problem. thank you (* sorry bad english)

Unlock your bootloader and retry.

Already retried to unlock the bootloader.. But no luck.. Thanks for the tips btw

I have found the solution.. I will post it in the weekend

luqmanhans said:
I have found the solution.. I will post it in the weekend
Click to expand...
Click to collapse
when u post please tell my in the praivte
[email protected]

Kingroot worked for me bit only after the second try

Tengo10 said:
Kingroot worked for me bit only after the second try
Click to expand...
Click to collapse
can u explain me please how u do it with king root??

eyalyagel said:
can u explain me please how u do it with king root??
Click to expand...
Click to collapse
I coud've offered more direct support if you messaged me or replied to my thread.

Have you found any solution?

Breadcrust said:
I coud've offered more direct support if you messaged me or replied to my thread.
Click to expand...
Click to collapse
can u give me please the link or explain may the way????
thank u very much

eyalyagel said:
can u give me please the link or explain may the way????
thank u very much
Click to expand...
Click to collapse
Did you do fastboot -i ox2b4c oem unlock?

Breadcrust said:
Did you do fastboot -i ox2b4c oem unlock?
Click to expand...
Click to collapse
yes,
FAILED (remote: Oem unlock is not support)
finished. total time: 0.008s
and i allow the oem in the developer option....
also i have the same phone in my home but the difrrent bitween them:
1. have only home press in the bottom
the ather phone have home, back,manu, bottom this phone can be unlocked and i sucsses to instal twrp

I have the same problem like it desribed by the OP.
I have the chinese version of the ZUK.
The Bootloader seems to be unlocked. When i check it, it says Unlocked: true.
When i did the Unlock, it didnt wipe something. When I do the unlock, it says ok, but there is no reboot.
But somehow, i cant boot or flash a recovery. Every time I have the error, Invalid data or not signed.
Root does also not work.
I have the latest version of ZUI installed. Is this the problem?
I read the problem several times, but nobody posted a solution for this.

xnoobx said:
I have the same problem like it desribed by the OP.
I have the chinese version of the ZUK.
The Bootloader seems to be unlocked. When i check it, it says Unlocked: true.
When i did the Unlock, it didnt wipe something. When I do the unlock, it says ok, but there is no reboot.
But somehow, i cant boot or flash a recovery. Every time I have the error, Invalid data or not signed.
Root does also not work.
I have the latest version of ZUI installed. Is this the problem?
I read the problem several times, but nobody posted a solution for this.
Click to expand...
Click to collapse
I'm also facing the same problem with my ZUK Z1

ZUI 1.2 locked the bootloader.If the TWRP recovery image file is twrp.img,You can try to do these:
Code:
fastboot -i 0x2b4c boot twrp.img
then you will boot into a temporary TWRP recovery.Now you can do everything here utill it reboots or shutdown.
if you want to flash a permanent recovery, I suggest to you to convert your ZUI to COS.

hfutxqd said:
ZUI 1.2 locked the bootloader.If the TWRP recovery image file is twrp.img,You can try to do these:
Code:
fastboot -i 0x2b4c boot twrp.img
then you will boot into a temporary TWRP recovery.Now you can do everything here utill it reboots or shutdown.
if you want to flash a permanent recovery, I suggest to you to convert your ZUI to COS.
Click to expand...
Click to collapse
Dear
I was using CM12 new version till last week and i have lots of problems, specially with mobile signal during the calls voice is dropping signal is too week as well. So i have decided to move to ZUI version and it's perfect so far i'm not facing any problem. Only the vulnerable is there some kind of malware and GPS having some bugs i have checked with bbs.zuk forms and they are suppose to fix it with next update. so i was trying to install the stagefright fix via recovery.remaining everything is smooth and faster than CM12.

hfutxqd said:
ZUI 1.2 locked the bootloader.If the TWRP recovery image file is twrp.img,You can try to do these:
Code:
fastboot -i 0x2b4c boot twrp.img
then you will boot into a temporary TWRP recovery.Now you can do everything here utill it reboots or shutdown.
if you want to flash a permanent recovery, I suggest to you to convert your ZUI to COS.
Click to expand...
Click to collapse
I also tried to boot. But it also denies this action :/.
So with the latest version my boot loader is locked. Sounds wonderful.

luqmanhans said:
Hello, i have a problem flashing custom recovery TWRP on ZUI.
below are the details of the problems:
ZUI Version: 1.2.040
Unlock Bootloader: YES (I feel a bit sketch on this part, because the process does not wipe any data)
Custom recovery to be installed: Un-Official 2.8.7.0 TWRP Recovery for ZUK Z1 by Breadcrust
1. when i try to flash the recovery on fastboot mode, it gives me this:
writing 'recovery'...
FAILED (remote : Invalid data)
finished. total time" 0.418s
2. when i try boot the recovery on fastboot mode, it also gives error:
downloading 'boot.img'...
OKAY [0.362s]
booting...
FAILED (remote: bootimage: incomplete or not signed)
finished. total time: 0.369s
* For the solution, i have tried kingroot to allow root access ---> NOT SUCCESFULL
** For 2nd solution, i have tried downgrading the ZUI version ----> NOT SUCCESFULL (cannot get into qdloader mode long enough).
*** I also have tried re-downloading the recovery image without using download accelarator (IDM) ---> NOT SUCCESFULL
edit: please... if somebody know the problem, please teach me how to overcome the problem. thank you (* sorry bad english)
Click to expand...
Click to collapse
In this case, you need flash fw Z1_CN_OPEN_USER_Q4275715.1_L_ZUI_1.0.050_ST_150910 via sd card ( root internal memory/creat sdfuse folder), after turn off fone and boot phone via factory mode recovery ( voulme down + power ). If phone flash ok, version is 1.0.050. So, phone can flash twrp recovery and rom CyanogenMod 12.1 .
Goodluck
{
"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"
}

luqmanhans said:
I have found the solution.. I will post it in the weekend
Click to expand...
Click to collapse
It is weekend now.
Can you please tell us the solution? I have the same problem & I have tried a lot of things with no luck!!! :crying:

hristos13gr said:
It is weekend now.
Can you please tell us the solution? I have the same problem & I have tried a lot of things with no luck!!! :crying:
Click to expand...
Click to collapse
First you must downgrade the ZUI from 1.2.040, just search this topic in this forum: how-to-flash-zuk-z1-zui-version-t3265741
After that you can boot with TWRP recovery. But if you failed to flash Cyanogen, use Modaco steps: 375804-convert-z1-from-zukui-to-cyanogen-os/
When your ZUK Z1 already use Cyanogen, you can flash to other recovery or ROMs easier .

[guide] root le x626

First, Unlock Bootloader
Install TWRP for Le X626
Download Magisk or SuperSU
Put Magisk or SuperSU in internal storage
Reboot to TWRP
Install from zip
Choose Magisk (Recommended) or SuperSU
Reboot
source : tickernel.tk

Can you please post something similar for rooting Le2 X526 model?
I would like to install Magisk instead of supersu as I have heard the former is better.

How to install TWRP for x626 according to the site the OP recommends.
From the same website, only without the adlinks. No guarantees from me, if you go through the instructions from the OP you will end up getting the same information.
– Make sure your Bootloader is Unlocked, if you don’t know how to Unlock the Bootloader then please go to here and Unlock the Bootloader of your Device.
– Download the Latest TWRP Recovery Image from https://dbr.ee/TKKC
– Reboot into Fastboot/Bootloader Mode.
– Run The Following Command from a Command Prompt in the Same Folder in which you downloaded the TWRP Recovery Image (Change twrp le x626.img to recovery.img):
fastboot flash recovery recovery.img
fastboot boot recovery.img
Click to expand...
Click to collapse

onlytanmoy said:
Can you please post something similar for rooting Le2 X526 model?
I would like to install Magisk instead of supersu as I have heard the former is better.
Click to expand...
Click to collapse
I can't, because it's have different chipset

okay, thanks for your response and clarification...cheers to that.

Hello,
I followed the instructions but I get this error message while install twrp, anyone have any ideas please?
C:\Users\Administrator\Downloads\fastboot>fastboot flash recovery recovery.img
target reported max download size of 134217728 bytes
sending ‘recovery’ (20480 KB)…
OKAY [ 9.809s]
writing ‘recovery’…
(bootloader) Fastboot oem devices is lock
(bootloader) Start unlock flow
(bootloader) Unlock Pass…continue to fastboot
OKAY [ 36.298s]
finished. total time: 53.258s
C:\Users\Administrator\Downloads\fastboot>fastboot boot recovery.img
downloading ‘boot.img’…
OKAY [ 7.198s]
booting…
(bootloader) Fastboot oem devices is unlock
(bootloader) Fastboot oem devices is unlock
(bootloader) Start lock flow
(bootloader) Lock Pass…continue to fastboot
FAILED (status read failed (Invalid argument))
finished. total time: 40.336s
C:\Users\Administrator\Downloads\fastboot>

tomfoley said:
Hello,
I followed the instructions but I get this error message while install twrp, anyone have any ideas please?
C:\Users\Administrator\Downloads\fastboot>fastboot flash recovery recovery.img
target reported max download size of 134217728 bytes
sending ‘recovery’ (20480 KB)…
OKAY [ 9.809s]
writing ‘recovery’…
(bootloader) Fastboot oem devices is lock
(bootloader) Start unlock flow
(bootloader) Unlock Pass…continue to fastboot
OKAY [ 36.298s]
finished. total time: 53.258s
C:\Users\Administrator\Downloads\fastboot>fastboot boot recovery.img
downloading ‘boot.img’…
OKAY [ 7.198s]
booting…
(bootloader) Fastboot oem devices is unlock
(bootloader) Fastboot oem devices is unlock
(bootloader) Start lock flow
(bootloader) Lock Pass…continue to fastboot
FAILED (status read failed (Invalid argument))
finished. total time: 40.336s
C:\Users\Administrator\Downloads\fastboot>
Click to expand...
Click to collapse
Unlock bootloader first
What rom do u use?

Hi Tickernel, and thank you for replying
I unlocked the bootloader as per Step 1 above and that completed successfully.
Moving on to Step 2 I got the recovery image following your links which led me to 'twrp le x626.img' (20MB), which I renamed to recovery.img.
There are two commands to execute in step 2, the first went ok, the second did not succeed
tickernel said:
Unlock bootloader first
What rom do u use?
Click to expand...
Click to collapse

Please see screenshot...
{
"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"
}
tickernel said:
Unlock bootloader first
What rom do u use?
Click to expand...
Click to collapse

tomfoley said:
Please see screenshot...
Click to expand...
Click to collapse
Have u tried boot to recovery?
Press vol up + power

Hi again Tickernel and thank you for your patience
I haven't tried boot to recovery, what would I need to do exactly? I'd need an update.zip file right? Any one in particular??

tomfoley said:
Hi again Tickernel and thank you for your patience
I haven't tried boot to recovery, what would I need to do exactly? I'd need an update.zip file right? Any one in particular??
Click to expand...
Click to collapse
After you flash the twrp, then boot into recovery by pressing vol up + power
You don't need update.zip

Hi Tickernel, so you're suggesting recovery in the sense of a total erasing of all apps and data? I'm willing to do it, but will make certain I have a backup first . Just want to confirm that this is what you think needs to be done.

tomfoley said:
Hi Tickernel, so you're suggesting recovery in the sense of a total erasing of all apps and data? I'm willing to do it, but will make certain I have a backup first . Just want to confirm that this is what you think needs to be done.
Click to expand...
Click to collapse
I'm not suggesting to erase all your data, i'm just suggesting after you flash the twrp but don't straight go to recovery then press vol up + power. That's it

Glad I asked My issue is it will not flash TWRP. It fails on the step 'fastboot boot recovery.img'

tomfoley said:
Glad I asked My issue is it will not flash TWRP. It fails on the step 'fastboot boot recovery.img'
Click to expand...
Click to collapse
Command 'fastboot boot recovery.img' is going boot to twrp. If you fail to do that, then just press vol up + power

Progress!! I switched to loading TWRP from a Windows OS to a Linux one and Fastboot completed without error. I have yet to complete the remainder of the steps but will do as soon as I get a chance. I'll report back. Thanks again Tickernel, looking forward to having a rooted device soon !

tomfoley said:
Progress!! I switched to loading TWRP from a Windows OS to a Linux one and Fastboot completed without error. I have yet to complete the remainder of the steps but will do as soon as I get a chance. I'll report back. Thanks again Tickernel, looking forward to having a rooted device soon !
Click to expand...
Click to collapse
Yeah, you're welcome

Don't suppose kingroot or similar works? I'm very lazy lol

I also have this problem were it fails in "fastboot boot recovery.img" but not in commanding "fastboot flash recovery recovery.img"
what to do?? :crying:
thanks for the help

Can't Re-Unlock bootloader?

Hi i've done something stupid, i've blocked bootloader idk why, anyway im in LineageOs 16, but now i can't back to stock or flash something else ¿i cant re-unlock bootloader?

What is the error that you're getting?

Fastboot flash bootloader permission denied

elHeisen said:
Fastboot flash bootloader permission denied
Click to expand...
Click to collapse
Yes you can't flash before unlocking? How about 'fastboot unlock bootloader' or was it 'fastboot bootloader unlock'? Sorry, tired hehe.

weazie said:
Yes you can't flash before unlocking? How about 'fastboot unlock bootloader' or was it 'fastboot bootloader unlock'? Sorry, tired hehe.
Click to expand...
Click to collapse
yep i've tried too but i get this
...
(bootloader) Check 'OEM unlocking' in Android Settings > Developer
(bootloader) Options
OKAY [ -0.000s]
finished. total time: -0.000s
and i can't enable OEM unlocking in Android P

elHeisen said:
yep i've tried too but i get this
...
(bootloader) Check 'OEM unlocking' in Android Settings > Developer
(bootloader) Options
OKAY [ -0.000s]
finished. total time: -0.000s
and i can't enable OEM unlocking in Android P
Click to expand...
Click to collapse
Did you find any solution?
Same problem!

Works for me!
elHeisen said:
yep i've tried too but i get this
...
(bootloader) Check 'OEM unlocking' in Android Settings > Developer
(bootloader) Options
OKAY [ -0.000s]
finished. total time: -0.000s
and i can't enable OEM unlocking in Android P
Click to expand...
Click to collapse
First, install gnirehtet for reverse tethering internet with usb and pc
https://github.com/Genymobile/gnirehtet
Then you will see that you can enable OEM

I'm still not able to unlock oem in settings. I have WIFI on and did all the updates to the latest

elHeisen said:
Fastboot flash bootloader permission denied
Click to expand...
Click to collapse
Same error here. Did anyone find a solution?

Constantinologia said:
Same error here. Did anyone find a solution?
Click to expand...
Click to collapse
Can you update your phone in settings? if not wait 7 days with phone on and try again. An update fixed my phone.

mrsiri said:
Can you update your phone in settings? if not wait 7 days with phone on and try again. An update fixed my phone.
Click to expand...
Click to collapse
I can't even load the system. The only two screens i can see are the Fastboot and "your device is corrupted". The Flashing option is locked and every rom i try to flash gives me the access denied error.
{
"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"
}

Constantinologia said:
I can't even load the system. The only two screens i can see are the Fastboot and "your device is corrupted". The Flashing option is locked and every rom i try to flash gives me the access denied error.
View attachment 5251849 View attachment 5251851
Click to expand...
Click to collapse
Can you download the stock rom from your current version flashed and boot it? use command "fastboot boot boot.img". Boot.img is inside of the flashable stock rom zip. After this try toggling the oem unlock if not wait 7 days and try to update phone like regular ota in setings

mrsiri said:
Can you download the stock rom from your current version flashed and boot it? use command "fastboot boot boot.img". Boot.img is inside of the flashable stock rom zip. After this try toggling the oem unlock if not wait 7 days and try to update phone like regular ota in setings
Click to expand...
Click to collapse
I found a stock rom that matches the descriptions from ro.build.fingerprint[0]: motorola/rav_retail/rav:10/QPJS30 and 63-35-1-15. Coudn'd find a match for 37df17:user/release-key.
Still got the error for fastboot boot boot.img:
downloading 'boot.img'...
OKAY [ 1.463s]
booting...
FAILED (status read failed (Too many links))
finished. total time: 37.486s

Constantinologia said:
I found a stock rom that matches the descriptions from ro.build.fingerprint[0]: motorola/rav_retail/rav:10/QPJS30 and 63-35-1-15. Coudn'd find a match for 37df17:user/release-key.
Still got the error for fastboot boot boot.img:
downloading 'boot.img'...
OKAY [ 1.463s]
booting...
FAILED (status read failed (Too many links))
finished. total time: 37.486s
Click to expand...
Click to collapse
I don't remember the steps to reproduce, but I remember being possible to take the very own boot.img currently flash on your phone. I think it was through adb commands, what if you try booting that one instead? That's what I did on mine, but it didn't help with toggling oem unlock, only entering the system

I accidentally locked mine and im in the same situation as everyone here, but i think the only solution is BlankFlashing or sideloading a signed OTA on it... Im trying everyday new possible methods of fixing it and if i get into some ill share here

hi guys, had exact same issue, spent hours trolling through the net, forums etc and this forum fixed it for me. I was about to throw the phone out.
something tells me that you have to have the boot image from the software you had installed before the crash/brick. Run the "fastboot boot boot.img"
i tried numerous boot.img's thinking I've spent too much time this device so as I turned my back on the phone I hear a 'Hello Moto' WTF...Up and running again. Good Luck

thehulk1969 said:
hi guys, had exact same issue, spent hours trolling through the net, forums etc and this forum fixed it for me. I was about to throw the phone out.
something tells me that you have to have the boot image from the software you had installed before the crash/brick. Run the "fastboot boot boot.img"
i tried numerous boot.img's thinking I've spent too much time this device so as I turned my back on the phone I hear a 'Hello Moto' WTF...Up and running again. Good LuckView attachment 5274327
Click to expand...
Click to collapse
It would be the solution if the stock was corrupted, but i have locked mine on StyxOS, and there isn't any boot.img for it so stock boot.img gives a system corrupted error. But nice idea.
Edit: Does it need to match the ro.fingerprint on getvar all? only tested with latest pie, so

How to unlock a Moto G7 xt1962-6

I rebooted my G7 into fastboot to wipe the cache and I got stuck in it. I wasn't trying to load a new image or replace anything. When I try any option (Start, Restart Bootloader, Recovery mode, Factory Mode, etc) it fails with the following message in the log:
Code:
SSM: Android image rollback: 8.9
failed to validate boot image
ERROR: Failed to pass validation, backup to fastboot
Boot up failed
So, I downloaded adb/fastboot, got the drivers installed, and tried to download the latest image from https:__mirrors.lolinet.com/firmware/moto/river/official/RETEU/ and then tried to flash it.
When I try to replace boot.img:
Code:
C:\temp\moto-g7-firmware> fastboot flash boot boot.img
(bootloader) is-logical:boot_a: not found
Sending 'boot_a' (32768 KB) OKAY [ 0.990s]
Writing 'boot_a' (bootloader) Image boot failed validation
(bootloader) Preflash validation failed
FAILED (remote: '')
fastboot: error: Command failed
Well, that's probably because I didn't unlock my bootloader first? I didn't know I'd be doing this. Maybe there's a stock boot image that wouldn't cause me problems?
I tried to unlock my bootloader. I got my boot key but when I run:
Code:
C:\temp\moto-g7-firmware> fastboot oem unlock XXXXXXXXXXXXXXXXXXXXXX
(bootloader) Check 'Allow OEM Unlock' in Android Settings > Developer
(bootloader) Options
OKAY [ 0.021s]
Finished. Total time: 0.027s
Well, this sucks. I can't get into the phone to get to the Android Settings menu. I feel stuck. Does anybody have any ideas for me?

rsshilli said:
I rebooted my G7 into fastboot to wipe the cache and I got stuck in it. I wasn't trying to load a new image or replace anything. When I try any option (Start, Restart Bootloader, Recovery mode, Factory Mode, etc) it fails with the following message in the log:
Code:
SSM: Android image rollback: 8.9
failed to validate boot image
ERROR: Failed to pass validation, backup to fastboot
Boot up failed
So, I downloaded adb/fastboot, got the drivers installed, and tried to download the latest image from https:__mirrors.lolinet.com/firmware/moto/river/official/RETEU/ and then tried to flash it.
When I try to replace boot.img:
Code:
C:\temp\moto-g7-firmware> fastboot flash boot boot.img
(bootloader) is-logical:boot_a: not found
Sending 'boot_a' (32768 KB) OKAY [ 0.990s]
Writing 'boot_a' (bootloader) Image boot failed validation
(bootloader) Preflash validation failed
FAILED (remote: '')
fastboot: error: Command failed
Well, that's probably because I didn't unlock my bootloader first? I didn't know I'd be doing this. Maybe there's a stock boot image that wouldn't cause me problems?
I tried to unlock my bootloader. I got my boot key but when I run:
Code:
C:\temp\moto-g7-firmware> fastboot oem unlock XXXXXXXXXXXXXXXXXXXXXX
(bootloader) Check 'Allow OEM Unlock' in Android Settings > Developer
(bootloader) Options
OKAY [ 0.021s]
Finished. Total time: 0.027s
Well, this sucks. I can't get into the phone to get to the Android Settings menu. I feel stuck. Does anybody have any ideas for me?
Click to expand...
Click to collapse
https://forum.xda-developers.com/general/general/update-moto-lenovo-moto-smart-assistant-t3951714/

Thank you for the response. Unfortunately, LMSA doesn't work either . It says "This device isn't supported". I have no idea why not.
{
"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"
}

rsshilli said:
Thank you for the response. Unfortunately, LMSA doesn't work either . It says "This device isn't supported". I have no idea why not.
Click to expand...
Click to collapse
It seems that your USB debugging or OEM unlock toggle was un-ticked.
Do you have recovery available to format/reset device?
RSDLite doesn't work with your model?

Negative
Nope. I can't seem to get RSD Lite to work on Windows 10 to recognize my phone .

rsshilli said:
Nope. I can't seem to get RSD Lite to work on Windows 10 to recognize my phone .
Click to expand...
Click to collapse
It is possible to flash the stock firmware while the bootloader is locked.
BUT: You can't only flash a single image, like the boot.img. You must execute the whole fastboot commands in the same order as you can find in the flashfile.xml inside the firmware.zip!!
I don't know why, but only single commands do not work.
BEFORE TRYING THIS: Make sure you flash the correct firmware! IT MUST be the same build as currently installed!! No RETAIL version or an older build version!

Well, that's weird
Huh. I tried LMSA tonight again just for fun and it worked fine this time. It found the image, downloaded it, and reflashed the phone to factory settings. Yay! I'm back in. I tried it many times before. I know my firmware updated on the phone a few days before this happened. I guess I just needed to wait for a bit. Thank you everybody.
Ryan

WoKoschekk said:
It is possible to flash the stock firmware while the bootloader is locked.
BUT: You can't only flash a single image, like the boot.img. You must execute the whole fastboot commands in the same order as you can find in the flashfile.xml inside the firmware.zip!!
I don't know why, but only single commands do not work.
BEFORE TRYING THIS: Make sure you flash the correct firmware! IT MUST be the same build as currently installed!! No RETAIL version or an older build version!
Click to expand...
Click to collapse
For next time, how does one find the exact firmware needed? I could never figure that out.

rsshilli said:
For next time, how does one find the exact firmware needed? I could never figure that out.
Click to expand...
Click to collapse
Code:
fastboot getvar all