Database Users

Can't install CWM or TWRP

So after rooting and unlocking my bootloader, I decided to install a custom recovery. However, it keeps failing every time.
C:\Users\Alberto\Desktop\ck>fastboot flash recovery twrp.img
(bootloader) Variable not supported!
target reported max download size of 31457280 bytes
sending 'recovery' (7594 KB)...
OKAY [ 0.597s]
writing 'recovery'...
OKAY [ 2.864s]
finished. total time: 3.461s
finished. total time: 0.007s
The phone reboots and still works as usual, but now I can't get into recovery. Is there any way to fix this problem? I am running .4.4.2 Kitkat

It looks like it's flashing correctly, but since you can't reboot into recovery, I would be willing to bet you're flashing the wrong file. What file are you using? Once you flash recovery, you need to boot straight into it so the install completes.
Sent from my HTC6525LVW using Tapatalk

ozeyguy said:
So after rooting and unlocking my bootloader, I decided to install a custom recovery. However, it keeps failing every time.
C:\Users\Alberto\Desktop\ck>fastboot flash recovery twrp.img
(bootloader) Variable not supported!
target reported max download size of 31457280 bytes
sending 'recovery' (7594 KB)...
OKAY [ 0.597s]
writing 'recovery'...
OKAY [ 2.864s]
finished. total time: 3.461s
finished. total time: 0.007s
The phone reboots and still works as usual, but now I can't get into recovery. Is there any way to fix this problem? I am running .4.4.2 Kitkat
Click to expand...
Click to collapse
Flashify works pretty well, maybe give it a shot. Also, make sure you have the correct versions.

RikRong said:
It looks like it's flashing correctly, but since you can't reboot into recovery, I would be willing to bet you're flashing the wrong file. What file are you using? Once you flash recovery, you need to boot straight into it so the install completes.
Sent from my HTC6525LVW using Tapatalk
Click to expand...
Click to collapse
I am using the right files.

Works like a charm. Thanks!

i am having the same problem even with flashify i am using recovery-clockwork-touch-6.0.4.4-xt907.img
after flashing with either flashify or adb i boot into recovery and it hangs at the unlocked bl screen, unlocked bl screen again, then it boots.

deathwithafi said:
i am having the same problem even with flashify i am using recovery-clockwork-touch-6.0.4.4-xt907.img
after flashing with either flashify or adb i boot into recovery and it hangs at the unlocked bl screen, unlocked bl screen again, then it boots.
Click to expand...
Click to collapse
i was having the exact same problem. if you check out this post (http://forum.xda-developers.com/show....php?t=2785214) they suggest using CWM 6.0.4.9 recovery for KK bootloader. i did a fastboot with this and haven't had any problems since.

chuck solid said:
i was having the exact same problem. if you check out this post (http://forum.xda-developers.com/show....php?t=2785214) they suggest using CWM 6.0.4.9 recovery for KK bootloader. i did a fastboot with this and haven't had any problems since.
Click to expand...
Click to collapse
Thank you i will try that
That link goes to 404 error
i found it and it works. thank you

deathwithafi said:
Thank you i will try that
That link goes to 404 error
i found it and it works. thank you
Click to expand...
Click to collapse
Where did you find it? I'm having the same issue, but I can't locate it.
Thanks.

drenze said:
Where did you find it? I'm having the same issue, but I can't locate it.
Thanks.
Click to expand...
Click to collapse
Second link
We cannot teach people anything; we can only help them discover it within themselves.

ezknives said:
Second link
We cannot teach people anything; we can only help them discover it within themselves.
Click to expand...
Click to collapse
Thanks!

ezknives said:
Second link
We cannot teach people anything; we can only help them discover it within themselves.
Click to expand...
Click to collapse
Link is dead... is there another? TIA!

ozeyguy said:
So after rooting and unlocking my bootloader, I decided to install a custom recovery. However, it keeps failing every time.
C:\Users\Alberto\Desktop\ck>fastboot flash recovery twrp.img
(bootloader) Variable not supported!
target reported max download size of 31457280 bytes
sending 'recovery' (7594 KB)...
OKAY [ 0.597s]
writing 'recovery'...
OKAY [ 2.864s]
finished. total time: 3.461s
finished. total time: 0.007s
The phone reboots and still works as usual, but now I can't get into recovery. Is there any way to fix this problem? I am running .4.4.2 Kitkat
Click to expand...
Click to collapse
Im having the same exact problem. I cannot get into recovery. I've tried mfastboot to load CWM (recovery-clockwork-6.0.4.4-xt907.IMG) and TWRP (XT901-XT907-TWRP-2.6.3.0-recovery.img) as well as TWRP Manager and Flashify on the phone. My bootloader is UNLOCKED and This is my config:
{
"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"
}
Does it have something to do with the version of KK? TIA

I believe the TWRP built for this phone is still unofficial, so you probably can't flash it with the app. When you flash with fastboot, do you power off after flashing, and then reboot straight back into recovery? If you don't do this, the stock recovery will over write.
Sent from my Nexus 5

When you flash with fastboot, do you power off after flashing, and then reboot straight back into recovery?
Click to expand...
Click to collapse
I did. I would get a (I dont know how to describe it) but a small "blip" at the bottom of the screen then it boot normal. I tried it several times and the same thing happened, like it was "trying" to get into recovery then just simply boots. I tried different IMG's thinking maybe they were corrupt. Also different USB ports and cables (motorola). NADA. Does it have something to do with the stock KK (I have a verizon phone) is there something in there that is keeping it from "sticking"?

UPDATE: Problem Solved... found in another post that someone was having a similar issue and they used xt926-KK-CWM-6048.img (which is compatible with xt907) I flashed it and CWM came up like normal! Thanks for all your efforts...I hope this helps someone in the future! Cheers!~

Update on the update!
KarmaKid said:
UPDATE: Problem Solved... found in another post that someone was having a similar issue and they used xt926-KK-CWM-6048.img (which is compatible with xt907) I flashed it and CWM came up like normal! Thanks for all your efforts...I hope this helps someone in the future! Cheers!~
Click to expand...
Click to collapse
So I was having issues with that version of CWM ... I found the version of TWRP that works with xt907 and now I get this?!
the screen is not sized properly. Thoughts? TIA

KarmaKid said:
So I was having issues with that version of CWM ... I found the version of TWRP that works with xt907 and now I get this?!
the screen is not sized properly. Thoughts? TIA
Click to expand...
Click to collapse
Though that version will flash to the 907, it's still designed for the 926's screen. You need to find the correct file.
Sent from my Nexus 5

I got the same thing before - It happens when using the wrong version of TWRP
I believe the correct versions are here : http://downloads.blissroms.com/Recovery/Recovery/xt907/

beeewell said:
I got the same thing before - It happens when using the wrong version of TWRP
I believe the correct versions are here : http://downloads.blissroms.com/Recovery/Recovery/xt907/
Click to expand...
Click to collapse
FIXED: THANKS! TWRP 2850...no issues!

[FIX] Android Lollipop OTA GPE stuck at bootlogo

For those who are stuck at bootlogo, the problem is the same as the one when we tried before downgrading from 4.4.4 to 4.4.2 it is with the partition table, the version in the ota is older that the one we have on our devices, I dunno how the hell is that but it is what happened to most of us, though the easy fix, flash the attached gpt through fastboot command:
fastboot flash partition gpt.bin
Hope this fixed everything ​

Thanks very much for the information!
I recently tried flashing the 4.4.4 GPE firmware onto my XT1032 and I got an error when trying to flash the GPT.bin partition using mfastboot. It said "failed". I got nervous and went back to the retail US firmware just in case. We need more people to confirm that this fix will work.
OP do you know if it's safe to flash your GPT partition before installing the OTA update on the 4.4.4 GPE ROM?

It works!
I cant flash any rom to my phone and everything failed on half proces and with this file i rescued my phone i flashed 4.4.4 gpe and than 5.0.1 ota (by sideload) !
My Moto Gpe was brick!! And now it works again!!!! Thanks!!!!

Yes I can confirm, I faced this issue myself and used this fix for it )​

Yeah!!! this work very well, you save my phone, thanks man

seriusly that was all? i had 2 moto g at home and when the first one got the ota it got hard bricked, but stupid me got back to 4.4.2 and at the 4.4.4 ota the phone hard bricked, i think that the bootloader is corrupted and now i have to wait for the full 5.0 rom to be aviabable. Thanks man i appreciate it (i had another moto g and just got the ota and booted because of this)

can't use that, i've got the 41.18 bootloader so i have to wait a 5.0 original firmware :/
or am i doing something wrong?

Bad news
ssalamon said:
can't use that, i've got the 41.18 bootloader so i have to wait a 5.0 original firmware :/
or am i doing something wrong?
Click to expand...
Click to collapse
We have the same problem fella. We must wait the firmware with the image of new bootloader...Maybe in one month we take a solution...

So, with new bootloader is not possible to apply OTA. I have received 5.0.1 OTA on my 4.4.4 GPE converted XT1032, but this failed to start after latest try to update

sebadomaitis said:
We have the same problem fella. We must wait the firmware with the image of new bootloader...Maybe in one month we take a solution...
Click to expand...
Click to collapse
The original GPE firmware has a bootloader version older than that of the 4.4.4 "again I don't know why" the only fix is by flashing the gpt file included, if you flashed the android lollipop and it didn't work, flash this and give it a shot .
"bear in mind also that this fix is for devices stuck at bootlogo not bootanimation, not a fix for bootloop"

ruphert said:
So, with new bootloader is not possible to apply OTA. I have received 5.0.1 OTA on my 4.4.4 GPE converted XT1032, but this failed to start after latest try to update
Click to expand...
Click to collapse
I faced exactly what you are facing now, flash this and everything will go smooth

Rostomania said:
I faced exactly what you are facing now, flash this and everything will go smooth
Click to expand...
Click to collapse
Thanks for you reply. After sideload 5.0.1 and stucking and google logo should I flash only your gptfix.zip and reboot?
{
"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"
}
Phone is stucking after reboot.

ruphert said:
Thanks for you reply. After sideload 5.0.1 and stucking and google logo should I flash only your gptfix.zip and reboot?
Phone is stucking after reboot.
Click to expand...
Click to collapse
No man, do the following:
1- Reboot Into bootloader and connect your device via usb.
2- In your adb folder paste the gpt file I included and press right click and shift in any white space in the folder and choose start command prompt.
3- type fastboot flash partition gpt.bin and your problem should be fixed.

Rostomania said:
No man, do the following:
1- Reboot Into bootloader and connect your device via usb.
2- In your adb folder paste the gpt file I included and press right click and shift in any white space in the folder and choose start command prompt.
3- type fastboot flash partition gpt.bin and your problem should be fixed.
Click to expand...
Click to collapse
Thanks a lot, you rocks!
Code:
sudo fastboot flash partition gpt.bin 12:02
target reported max download size of 536870912 bytes
sending 'partition' (32 KB)...
OKAY [ 0.036s]
writing 'partition'...
(bootloader) This may take a few seconds, if a
(bootloader) different partition table is being
(bootloader) flashed since we need to backup
(bootloader) and restore a few partitions
(bootloader) Flashing primary GPT image...
(bootloader) Flashing backup GPT image...
OKAY [ 0.320s]
finished. total time: 0.356s
sudo fastboot reboot
Phone is booting now

boot stuck
Hi, I've stucked on "android logo with unlocked lock icon".
Originally I had xt1033 asian, which was converted to 4.4 GPE one sim. Today I've tried to flash the 5.0.1 lollipop via adb, and as many of you guys, stucked on boot.
I've already tried your fix, and tried to downgrade following this thread http://forum.xda-developers.com/moto-g/general/guide-xt1033-downgrade-lollipop-5-0-to-t2969729
but still phone doesn't boot, just "Google" and lock icon...
can you help me, at least boot it, android version doesn't metter
** UPDATE **
So, I've managed to boot phone thatks to this thread http://forum.xda-developers.com/moto-g/general/guide-restore-softbricked-phone-t2965459
Gonna make a backup and try installing 5.0.1 again

sebadomaitis said:
We have the same problem fella. We must wait the firmware with the image of new bootloader...Maybe in one month we take a solution...
Click to expand...
Click to collapse
Not exactly, my XT1033 had 41.18 bootloader when i applied the 5.0.1 ota, it just worked with the following tutorial. I didn't even use the gpt file here.
http://forum.xda-developers.com/moto-g/general/guide-convert-brazilian-firmware-gpe-5-t2969472

awesome.. this works like wonder.. but now i am not getting the network .. any idea what to do?

ghost9685 said:
awesome.. this works like wonder.. but now i am not getting the network .. any idea what to do?
Click to expand...
Click to collapse
Look at this tread
http://forum.xda-developers.com/moto-g/general/gpe-ota-lrx21z-5-0-1-xt1033-xt1032-t2969847
1st post
Step 5
Maybe it could work

My Own devices is a XT1032, and this fix has nothing to do with the XT1033 converted to GPE .​

I can also confirm that this works. But my phone was already converted to GPE and had 4.4.4 before I did the OTA update.
Giovani's guide works if you're stuck on the bootlogo after updating to 4.4.4 and then lollipop through OTA (on a gpe converted device of course). I used the second method in that thread.

DFU and fastboot. Brick Axon 7 A2017

I cant enter adb. only something like fastboot (bootloader) . also can start like ZTE Handset Diagnostic Interface(DFU)
can you help me? nothing works
{
"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"
}
C:\adb> adb devices
List of devices attached
C:\adb>fastboot devices
2a47d296 fastboot
C:\adb>fastboot flash recovery twrp-3.0.3-1-ailsa_ii.img
target reported max download size of 536870912 bytes
sending 'recovery' (13536 KB)...
OKAY [ 0.316s]
writing 'recovery'...
FAILED (remote: unknown command)
finished. total time: 0.331s

I HAVE THE SAME ISSUE!(A2017G) SOMEONE HELP! :crying:

You're not bricked, you're just down ATM. If you can get into bootloader or EDL mode you're fine. Just gotta put some work in. First, you've probably got a bootloader that doesn't allow fastboot commands. (the reason why you're getting the unknown command error). You need to flash that via EDL if you don't want to downgrade/unlock your bootloader. There is SOOOO much to read out there that with a little searching and reading you'll be up in no time. This toolkit is a good place to start looking. https://forum.xda-developers.com/axon-7/development/tool-axon7toolkit-t3573108

nolimit78 said:
You're not bricked, you're just down ATM. If you can get into bootloader or EDL mode you're fine. Just gotta put some work in. First, you've probably got a bootloader that doesn't allow fastboot commands. (the reason why you're getting the unknown command error). You need to flash that via EDL if you don't want to downgrade/unlock your bootloader. There is SOOOO much to read out there that with a little searching and reading you'll be up in no time. This toolkit is a good place to start looking. https://forum.xda-developers.com/axon-7/development/tool-axon7toolkit-t3573108
Click to expand...
Click to collapse
Hey, I CAN use Fastboot commands. but i cant get to recovery mode even tho i flash it. my bootloader is unlocked. please help!! i am stuck

Well with the error message you posted, "unknown command" means that you're on the wrong bootloader. You have two methods to install TWRP. Bootloader or EDL. If you want to do it via bootloader you need to load the B20 bootloader and that'll allow for the fastboot flash recovery "name of img file".img command. If you're wanting to use EDL you'll need to use a tool to force the recovery image.

nolimit78 said:
You're not bricked, you're just down ATM. If you can get into bootloader or EDL mode you're fine. Just gotta put some work in. First, you've probably got a bootloader that doesn't allow fastboot commands. (the reason why you're getting the unknown command error). You need to flash that via EDL if you don't want to downgrade/unlock your bootloader. There is SOOOO much to read out there that with a little searching and reading you'll be up in no time. This toolkit is a good place to start looking. https://forum.xda-developers.com/axon-7/development/tool-axon7toolkit-t3573108
Click to expand...
Click to collapse
fastboot flash recovery twrp-3.0.3-1-ailsa_ii.img
target reported max download size of 536870912 bytes
sending 'recovery' (13536 KB)...
OKAY [ 0.316s]
writing 'recovery'...
FAILED (remote: unknown command)
finished. total time: 0.331s
I cant go to edl. Only DFU.
C:\adb>fastboot oem device-info
...
FAILED (remote: unknown command)
finished. total time: 0.034s
FAILED to all commands in fastboot

nolimit78 said:
Well with the error message you posted, "unknown command" means that you're on the wrong bootloader. You have two methods to install TWRP. Bootloader or EDL. If you want to do it via bootloader you need to load the B20 bootloader and that'll allow for the fastboot flash recovery "name of img file".img command. If you're wanting to use EDL you'll need to use a tool to force the recovery image.
Click to expand...
Click to collapse
Check This;;
:\Users\Bumthimble\Desktop\ADB>fastboot flash recovery recovery.img
target reported max download size of 536870912 bytes
sending 'recovery' (17917 KB)...
OKAY [ 0.424s]
writing 'recovery'...
OKAY [ 0.141s]
finished. total time: 0.565s
I get this but when i try to boot into recovery, it boots into fastboot mode. Help

Ok that means that both of you are using the G model. If you're able to get to your bootloader try using the tool that I linked above. I have the U model so I can't relate with some of your issues but I believe that if you can reach the bootloader the tool can help. Have you tried manually booting to EDL?

nolimit78 said:
Ok that means that both of you are using the G model. If you're able to get to your bootloader try using the tool that I linked above. I have the U model so I can't relate with some of your issues but I believe that if you can reach the bootloader the tool can help. Have you tried manually booting to EDL?
Click to expand...
Click to collapse
I did. but it doesnt boot into EDL ever. I dont know why, i doesnt recognise its commands

nolimit78 said:
Ok that means that both of you are using the G model. If you're able to get to your bootloader try using the tool that I linked above. I have the U model so I can't relate with some of your issues but I believe that if you can reach the bootloader the tool can help. Have you tried manually booting to EDL?
Click to expand...
Click to collapse
I have China version. I cant manually booti to EDL. it booting in DFU

i can only boot it to fastboot

See this thread: https://forum.xda-developers.com/axon-7/help/edl-twrp-stuck-fastboot-luck-t3569879

don't work.
ZTE Handset Diagnostic Interface(DFU)
with handmade deepflash cable
if I connect with a closed cable, it blinks the symbol of charging(empty battery with the lightning bolt) several times and boot in DFU

fatax said:
don't work.
ZTE Handset Diagnostic Interface(DFU)
with handmade deepflash cable
if I connect with a closed cable, it blinks the symbol of charging(empty battery with the lightning bolt) several times and boot in DFU
Click to expand...
Click to collapse
I have exactly the same issue.
And 2 weeks already. Can't find any solution. Searched all the internet.
There is no solution so far.
Have to wait untill someone will create a flashtool for DFU mode for Snapdragon 820.

Vick78 said:
I have exactly the same issue.
And 2 weeks already. Can't find any solution. Searched all the internet.
There is no solution so far.
Have to wait untill someone will create a flashtool for DFU mode for Snapdragon 820.
Click to expand...
Click to collapse
I gave the phone to a service center (unofficial) they will try to flash the phone directly to memory

fastboot still locked. they can not do anything

fatax said:
fastboot still locked. they can not do anything
Click to expand...
Click to collapse
that's a sad news. did they say anything?
what do they need to fix?

Vick78 said:
that's a sad news. did they say anything?
what do they need to fix?
Click to expand...
Click to collapse
I do not know, but my acquaintance with 4pda wrote: Hello. It's JOY NEWS! We HAVE RISE ONE BRICK! So wait soon we will lay out the instruction how to raise. The phone will have to be dismantled.

I have now the same problem how did you solved the problem? Or is there generaly any solution?

cybertronixx said:
I have now the same problem how did you solved the problem? Or is there generaly any solution?
Click to expand...
Click to collapse
Did you search on the forum before bumping a year-old thread?
So far there are 2 DFU guides, mine is the latest. (Google "dfu unbrick"). Though you might want to try an EDL cable before doing the process on the guide. Just use MiFlash or EDL Tool along with the cable, and you might fix it.

[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