[RECOVERY][TWRP 3.3.1][For all Quark][Moto Maxx/Turbo and Droid Turbo]

[ivan.cwb]

I already mirror all do Gdrive but I miss to inform here is the link
https://drive.google.com/drive/folders/1VIsIlup3UTsjhFTGh7XTjR4A5vq32f1C

I assume that mfastboot is the port of fastboot linux tool to Microsoft OS or something like that, you can google and find more about it as I have no idea.

On a deb base linux system you can install using bellow

sudo apt-get -y fastboot

I don't use other then deb system so just google if you can't use above command on yours OS.

Oh, so the fastboot is not a modified version like the twrp, I see...

The thing is, I cannot flash and boot you modified recovery, only the original ones from twrp website, that are not able to install the ROM correctly (I can install lineage-14 correctly, though)...

I'm doing:

$ fastboot flash recovery original_twrp-3.3.1-0-quark.img # from the twrp website...
# OK

$ fastboot boot original_twrp-3.3.1-0-quark.img
# OK

# Modified version...

$ fastboot flash recovery twrp-3.3.1-mod_1-quark.img
# OK

$ fastboot boot twrp-3.3.1-mod_1-quark.img
# phone is restarted, but it is not going to recovery.

If I enter in fastboot mode and set 'Recovery' the phone simple restarts without going to recovery.

Do you know what could be the problem?

 

[fgl27]

Oh, so the fastboot is not a modified version like the twrp, I see...

The thing is, I cannot flash and boot you modified recovery, only the original ones from twrp website, that are not able to install the ROM correctly (I can install lineage-14 correctly, though)...

I'm doing:

$ fastboot flash recovery original_twrp-3.3.1-0-quark.img # from the twrp website...
# OK

$ fastboot boot original_twrp-3.3.1-0-quark.img
# OK

# Modified version...

$ fastboot flash recovery twrp-3.3.1-mod_1-quark.img
# OK

$ fastboot boot twrp-3.3.1-mod_1-quark.img
# phone is restarted, but it is not going to recovery.

If I enter in fastboot mode and set 'Recovery' the phone simple restarts without going to recovery.

Do you know what could be the problem?

If you have the bootloader unlocked to boot to recovery while in the bootloader you use the volume buttons to select "Recovery mode" and press the power button (sometime is need to press the power two or more times don't hold).

If you are on adb mode you can use a command "reboot recovery" to reboot the device to recovery. I don't know a command that boots from bootloader to recovery I don't think is a option on quark.

 

[ivan.cwb]

If you have the bootloader unlocked to boot to recovery while in the bootloader you use the volume buttons to select "Recovery mode" and press the power button (sometime is need to press the power two or more times don't hold).

If you are on adb mode you can use a command "reboot recovery" to reboot the device to recovery. I don't know a command that boots from bootloader to recovery I don't think is a option on quark.

I understand that, but as I said, I'm able to install lineageos-14 using original twrp from their website...
What is not working is the recovery mode when I flash the twrp_mod version that you provide... I simply cannot go to twrp with that version.

If I flash the modified version, and try to restart in recovery mode (or use fastboot boot twrp_mod) it restarts and after the 'logo part' it restarts again in 'normal mode', like the recovery mode failed or something like that.

I'm wondering if there's a gimmick that I need to do before all this (firmware or whatever)...

EDIT: just out of curiosity, I tried some old versions of modified twrp's, but it didn't work either:

811193f9bebb5e04f19ec709330f6322 twrp-3.2.3-mod_1-quark.img
e0730e6f308752df08ca0b167630ec56 twrp-3.2.3-mod_4-quark.img
920e4c857ac6a50600c2f41cdd48c07e twrp-3.3.1-mod_1-quark.img

 

[fgl27]

I understand that, but as I said, I'm able to install lineageos-14 using original twrp from their website...
What is not working is the recovery mode when I flash the twrp_mod version that you provide... I simply cannot go to twrp with that version.

If I flash the modified version, and try to restart in recovery mode (or use fastboot boot twrp_mod) it restarts and after the 'logo part' it restarts again in 'normal mode', like the recovery mode failed or something like that.

I'm wondering if there's a gimmick that I need to do before all this (firmware or whatever)...

EDIT: just out of curiosity, I tried some old versions of modified twrp's, but it didn't work either:

I don't know, all of those files work for me.

Just do the process as I described

fastboot flash recovery twrp_file.img

after if you receive a OK something like this

target max-sparse-size: 256MB
sending 'recovery' (16400 KB)...
OKAY [  0.547s]
writing 'recovery'...
OKAY [  0.516s]
finished. total time: 1.085s

Select "recovery mode" use the power key to go to recovery

noting else that include that boot command that you are using. after all I never requested no one to use

fastboot boot twrp-3.3.1-mod_1-quark.img

Maybe that mess up something.

 

[ivan.cwb]

I don't know, all of those files work for me.

Just do the process as I described

fastboot flash recovery twrp_file.img

after if you receive a OK something like this

target max-sparse-size: 256MB
sending 'recovery' (16400 KB)...
OKAY [  0.547s]
writing 'recovery'...
OKAY [  0.516s]
finished. total time: 1.085s

Select "recovery mode" use the power key to go to recovery

noting else that include that boot command that you are using. after all I never requested no one to use

fastboot boot twrp-3.3.1-mod_1-quark.img

Maybe that mess up something.

I was doing just for convenience to boot directly the image, but yes, I tried without it first...

OK, so my output is different from yours. I got:

(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' (15248 KB)...
OKAY [  0.491s]
writing 'recovery'...
OKAY [  0.240s]
finished. total time: 0.732s

I got almost the same output for the no-modified twrp (but this one worked):

(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' (12568 KB)...
OKAY [  0.399s]
writing 'recovery'...
OKAY [  0.185s]
finished. total time: 0.584s

 

[Kinzhal]

TWRP issues

Howzit, folks? There's a glitch when the device boots: it goes into recovery mode automatically and, when I select system reboot, it loops back into recovery. I have to select bootloader and use the power button; then, it gets stuck on the Motorola logo screen, I have to perform a hard reset and repeat the process once more. Only then does it boot to the system. I'm using TWRP 3.3.1-0. Has anyone else had a similar issue? Any thoughts? Thanks in advance.

 

[fgl27]

Howzit, folks? There's a glitch when the device boots: it goes into recovery mode automatically and, when I select system reboot, it loops back into recovery. I have to select bootloader and use the power button; then, it gets stuck on the Motorola logo screen, I have to perform a hard reset and repeat the process once more. Only then does it boot to the system. I'm using TWRP 3.3.1-0. Has anyone else had a similar issue? Any thoughts? Thanks in advance.

Are you using twrp download from first post links?

As twrp downloaded from trwp site have that issue, the one from first post don't.

 

[Kinzhal]

Re: TWRP issues

Are you using twrp download from first post links?

As twrp downloaded from trwp site have that issue, the one from first post don't.

Yas, I installed TWRP from the 1st post and so far, so good. The problem seems to have been fixed. Many thanks! @fgl27

 

[Kinzhal]

Boot issue

Yas, I installed TWRP from the 1st post and so far, so good. The problem seems to have been fixed. Many thanks! @fgl27

So, the loop to recovery mode is fixed (it would boot when connected to a power source and that's fixed too). On the other hand, the device refuses to boot to the system on the first try: it freezes on the OEM logo screen and will boot normally only after a manual reset (it sometimes takes more than one try)

 

[fgl27]

So, the loop to recovery mode is fixed (it would boot when connected to a power source and that's fixed too). On the other hand, the device refuses to boot to the system on the first try: it freezes on the OEM logo screen and will boot normally only after a manual reset (it sometimes takes more than one try)

Noting to do with recovery... try a full clean reinstall of the OS... by wiping the data (without media) and system partition , then re-flash yours ROM zip... if the issue continues maybe the device has a HW issue