Database Develop

[Q] Can't Flash Recovery for Root

I have a Sprint Moto X 4.4.2. The bootloader is unlocked. All ADB commands work fine until I get to flashing a recovery. It doesn't matter how I type it (the actual file name.img or recovery.img). The error I receive is:
fastboot flash recovery recovey.img
(bootloader) Variable not supported!
target reported max download size of 805306368 bytes
error: cannot load 'recovey.img': No such file or directory
What can I do to fix this?

I'm running Linux just in case that makes a difference...

Try using moto-fastboot/mfastboot instead of the standard fastboot. The download link is around here somewhere.
Sent from my XT1060 Dev Edition

pkomarnicki said:
Try using moto-fastboot/mfastboot instead of the standard fastboot. The download link is around here somewhere.
Sent from my XT1060 Dev Edition
Click to expand...
Click to collapse
If you are referring to the snapdragon-fastboot file then I have tried with that and get the same result.

So I just tried flashing the Unofficial CWM and got:
fastboot flash recovery cwm6.0.3.6.img
(bootloader) Variable not supported!
target reported max download size of 805306368 bytes
sending 'recovery' (8504 KB)...
OKAY [ 0.774s]
writing 'recovery'...
OKAY [ 0.930s]
finished. total time: 1.704s
It booted into the recovery but there were no options and it reset...
Same thing happens with TWRP

jjchdc said:
So I just tried flashing the Unofficial CWM and got:
fastboot flash recovery cwm6.0.3.6.img
(bootloader) Variable not supported!
target reported max download size of 805306368 bytes
sending 'recovery' (8504 KB)...
OKAY [ 0.774s]
writing 'recovery'...
OKAY [ 0.930s]
finished. total time: 1.704s
It booted into the recovery but there were no options and it reset...
Same thing happens with TWRP
Click to expand...
Click to collapse
now, what i'm about to say may be wrong, because i'm useing verizon. howerver, why arn't u useing RSD? also, do you have a full charge? I've heard that could do it too. what about your antivirus, and firewall...?

xpsychox said:
now, what i'm about to say may be wrong, because i'm useing verizon. howerver, why arn't u useing RSD? also, do you have a full charge? I've heard that could do it too. what about your antivirus, and firewall...?
Click to expand...
Click to collapse
I'm not sure what RSD is, haven't heard of it before. I was using Linux with mfastboot which apparently does not work. I used a VM for Windows 7 and did it all over again and it worked. If anyone else has this problem in the future make sure to name your recovery recovery.img. It would not flash for me correctly as the file name.

are you sure you are using motorola fastboot (mfastboot)
check here: https://www.google.com/url?sa=t&rct...o-eIsOYmBKsSwexGw&sig2=8dqw-10kR7K9LB-A4fI8nQ
normally the issues with size are due to using google fastboot binary.

Help - Stuck in Bootloop

The point in which everything took a turn for the worst was while trying to update firmware via SD update method. At which point it just stayed on android boot screen.
Recovery was broken at this point
I successfully flashed an older CWM version, but that was useless for reflashing the latest Asus firmware.
I tried flashing stock recovery again and it appeared to succeed, but now when I try to boot to recovery, it just goes back to bootloop.
I'm trying to flash the US version now via fastboot I get bootloop again and I'm getting weird errors every time I try regarding filesize. (See below)
I tried flashing CROMbi as well and it went through the install process successfully, but that resulted in bootloop as well.
Tried flashing Asus US firmware again without success,
Kind of pissed that this all started when following the instructions on the Asus site to upgrade to their latest firmware via SD card.
Code:
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot -i 0x0B05 flash system
asusus.zip
target reported max download size of 643825664 bytes
Invalid sparse file format at header magi
error: write_sparse_skip_chunk: don't care size 425021387 is not a multiple of t
he block size 4096
erasing 'system'...
OKAY [ 1.457s]
sending sparse 'system' (628732 KB)...
error: write_sparse_skip_chunk: don't care size 425021387 is not a multiple of t
he block size 4096
error: write_sparse_skip_chunk: don't care size 425021387 is not a multiple of t
he block size 4096
OKAY [ 86.837s]
writing 'system'...
OKAY [ 17.080s]
sending sparse 'system' (415060 KB)...
OKAY [ 57.305s]
writing 'system'...
OKAY [ 11.353s]
finished. total time: 174.042s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot -i 0x0B05 reboot
rebooting...
finished. total time: 0.021s
C:\Program Files (x86)\Minimal ADB and Fastboot>

Last time something like this happened, I had to wipe everything and reflash. so I did the following.
fastboot -i 0x0b05 erase boot
fastboot -i 0x0b05 erase cache
fastboot -i 0x0b05 erase userdata
fastboot -i 0x0b05 erase recovery
fastboot -i 0x0b05 erase staging
fastboot -i 0x0b05 erase system
and now I get a bootloader error on startup
I was able to successfully flash CWM 6037 again. I tried newer ones, but 6037 is the only one that will work.
Stock firmware from custom recovery fails every time. "Installing update... Installation aborted."
Crombi installer goes through without any problems. but just never boots once completed.
I tried installing the latest Cyanogen Nightly and got the following error "This package is for tF701T devices; this is a K00C."
But the K00C is a TF701T
After installing CROMbi again, I'm no longer getting the bootloader error in red letters, but I am still bootlooping.
When crombi installer completes I do get one error at the very end. "set_metadata_recursive:some changes failed".
I looked at the log and it says Cant partition non-vfat datamedia.
Does bootloop after apparently successful fstboot flash have anythignt o do with why in the FAW's ASUS recommends ignoring the software update for 4.3? Afterall this is what put me in this situation.

The SD update is designed to work with the stock recovery. What made you think it would work with CWM?
The only successful recovery from a similar situation I remember is the following (and I'm quoting from memory here - it's too late here for me to find the thread, but it is somewhere here in this forum - search for it.
Download the stock recovery to your fastboot folder from here: http://droidbasement.com/db-blog/?p=3210
Also download the 10.26.1.18 firmware, unzip it once, put it on a microSD and insert into tablet.
Enter fastboot mode
Issue:
Code:
fastboot [b]boot[/b] recovery.img
Note: You do not flash the recovery, you boot it!
The recovery should recognize the firmware on the microSD and start to flash it.
If that is successful, you would have stock recovery and firmware again.
Then download the latest firmware, unzip it, put into microSD or internal and the stock recovery should flash it.
Good luck!
Sent from my K00C using Tapatalk

berndblb said:
The SD update is designed to work with the stock recovery. What made you think it would work with CWM?
The only successful recovery from a similar situation I remember is the following (and I'm quoting from memory here - it's too late here for me to find the thread, but it is somewhere here in this forum - search for it.
Download the stock recovery to your fastboot folder from here: http://droidbasement.com/db-blog/?p=3210
Also download the 10.26.1.18 firmware, unzip it once, put it on a microSD and insert into tablet.
Enter fastboot mode
Issue:
Code:
fastboot [b]boot[/b] recovery.img
Note: You do not flash the recovery, you boot it!
The recovery should recognize the firmware on the microSD and start to flash it.
If that is successful, you would have stock recovery and firmware again.
Then download the latest firmware, unzip it, put into microSD or internal and the stock recovery should flash it.
Good luck!
Sent from my K00C using Tapatalk
Click to expand...
Click to collapse
The attempted SD update was done with custom recovery as I couldn't get stock recovery to work after the initial SD update with stock recovery.
Thanks for the info. I'll update.

gorilla p said:
Last time something like this happened, I had to wipe everything and reflash. so I did the following.
fastboot -i 0x0b05 erase boot
fastboot -i 0x0b05 erase cache
fastboot -i 0x0b05 erase userdata
fastboot -i 0x0b05 erase recovery
fastboot -i 0x0b05 erase staging
fastboot -i 0x0b05 erase system
and now I get a bootloader error on startup
I was able to successfully flash CWM 6037 again. I tried newer ones, but 6037 is the only one that will work.
Stock firmware from custom recovery fails every time. "Installing update... Installation aborted."
Crombi installer goes through without any problems. but just never boots once completed.
I tried installing the latest Cyanogen Nightly and got the following error "This package is for tF701T devices; this is a K00C."
But the K00C is a TF701T
After installing CROMbi again, I'm no longer getting the bootloader error in red letters, but I am still bootlooping.
When crombi installer completes I do get one error at the very end. "set_metadata_recursive:some changes failed".
I looked at the log and it says Cant partition non-vfat datamedia.
Does bootloop after apparently successful fstboot flash have anythignt o do with why in the FAW's ASUS recommends ignoring the software update for 4.3? Afterall this is what put me in this situation.
Click to expand...
Click to collapse
That error message means that your internal sdcard is no t available to format. Erasing all partitions is a dangerous thing to do.
The only way you will get back to normal is to try and flash the stock asus rom now as that will recreate everything. I recommend you start with the 4.2.2 one - need to flash it over fastboot - I can't see anything else working as you have erased it all.....
Also you used 0x0b05 which is the code for the last generation of transformers..... You don't need it for the TF701 but not sure if that has caused additional grief now. Probably not but you never know .....

Yeah IO'm getting the same issue that I was having before. I tried both the 4.3 and 4.2 boot.img and the recommended recovery.img file. Each time I ran
fasboot boot recovery.img
downloading 'boot.img'...
OKAY [ 1.121s]
booting...
OKAY [ 0.032s]
finished. total time: 1.157s
booting from downloaded boot.img (on tablet)
Then it goes to boot into the image and...bootloop.
C:\Program Files (x86)\Minimal ADB and Fastboot\asus>fastboot flash system asus4
22.zip
target reported max download size of 643825664 bytes
Invalid sparse file format at header magi
error: write_sparse_skip_chunk: don't care size 346827884 is not a multiple of t
he block size 4096
erasing 'system'...
OKAY [ 1.515s]
sending sparse 'system' (628732 KB)...
error: write_sparse_skip_chunk: don't care size 346827884 is not a multiple of t
he block size 4096
error: write_sparse_skip_chunk: don't care size 346827884 is not a multiple of t
he block size 4096
OKAY [ 86.861s]
writing 'system'...
OKAY [ 17.098s]
sending sparse 'system' (338700 KB)...
OKAY [ 46.823s]
writing 'system'...
OKAY [ 9.280s]
finished. total time: 161.586s
Bootloop...
Could the inability to flash or boot from stock recovery have anything to do with the CWM recovery protection?

Well after those attempts it's totally shot.
Now I can't even get to fastboot. Every reboot results in "Unrecoverable bootloader error..."
Files RMA. Returned.
Moral of story. Don't do anything on a Tegra device without previous documentation that doesn't have NVFlash available.

[Q] Moto XT1097 AT&T fastboot loop.

I tried to update my moto XT1097 AT&T locked version and it did not complete the update successfully. It goes until flashing the boot.img, failed and don't go any further. I supposed it is because it is a locked phone. After this, the phone went to a fastboot mod loop. Even If I tried to sideload the orignial rom or use the fsaboot comandts to restore the original rom it remains in this mode.
It generates a first error when I tried to issue the command "fastboot flash partition gpt.bin" returning this:
target reported max download size of 536870912 bytes
sending 'partition' (32 KB)...
OKAY [ 0.004s]
writing 'partition'...
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 0.013s
And the phone display shows "hab check failed for primary_gpt"
I am issuing this command from the folder where the files of the original rom are located.
I tried to use a different gpt.bin file, from other ROMs and the same thing happen. I also tried another Lollipop ROM and not luck at all.
What I understand is that the gpt is the partion table that indicates where begins and where finish the diferent partitions into the phone, so I guess the problem could be resolve if I can change the gpt file into the phone for the original one.
I have tried to follow with the rest of the instalation but the motoboot and the boot files also are rejected and the system files are denied due an authentication problem.
The roms I have tried are:
ATT_XT1097_4.4.4_KXE21.187-38_cid1_CFC.xml
TMO_21.21.42.victara_tmo.tmo.en.US
4.4.4_to_5.0-11OTA
And the first one I used, which reach the same stage every time is:
RETBR_XT1097_5.0_LXE22.46-17_cid12_CFC.xml
I really appreciate any help and ideas you can give me to get my phne back to kitkat. I am not an expert but I am willing to do and learn what it takes

Did you solve this? How?

I am into this problem too. Any news?

XT1097 Marshmallow TWRP not loading

Hey everyone
I'm trying to root my XT1097 (Canadian on Wind Mobile) but I cant seem to get TWRP to install. Everytime I try to boot into recovery it just boots normally. I have been searching these forums (and the internet) for days and can't seem to find a solution. I did see one mention of some devices automatically replacing a custom recovery when trying to boot into recovery for the first time and needing to hold a specific key combo while booting to prevent this but as near as I can tell this device is not one of them. It sure seems to be acting that way though, am I missing something?
Here is the info
Moto X 2014 XT1097 on Wind Mobile in Canada
Unlocked bootloader
Dev options on with USB debugging enabled
"twrp-3.0.2-1-victara.img" is the file I am trying to use from the twrp website, which I believe is the correct one
I enter the following in cmd
E:\Programs\Android>fastboot boot recovery.img
downloading 'boot.img'...
OKAY [ 0.328s]
booting...
OKAY [ 0.251s]
finished. total time: 0.578s
and it reboots normally. If I try this:
E:\Programs\Android>fastboot flash recovery recovery.img
target reported max download size of 536870912 bytes
sending 'recovery' (9160 KB)...
OKAY [ 0.328s]
writing 'recovery'...
OKAY [ 0.407s]
finished. total time: 0.734s
Then select recovery on the phone, it just shuts off.
It says "Mismatched partition size (recovery)" in pink when I flash the recovery image but I read that that can be ignored if you use the first method.
Any help would be great!

Jackson604 said:
Hey everyone
I'm trying to root my XT1097 (Canadian on Wind Mobile) but I cant seem to get TWRP to install. Everytime I try to boot into recovery it just boots normally. I have been searching these forums (and the internet) for days and can't seem to find a solution. I did see one mention of some devices automatically replacing a custom recovery when trying to boot into recovery for the first time and needing to hold a specific key combo while booting to prevent this but as near as I can tell this device is not one of them. It sure seems to be acting that way though, am I missing something?
Here is the info
Moto X 2014 XT1097 on Wind Mobile in Canada
Unlocked bootloader
Dev options on with USB debugging enabled
"twrp-3.0.2-1-victara.img" is the file I am trying to use from the twrp website, which I believe is the correct one
I enter the following in cmd
E:\Programs\Android>fastboot boot recovery.img
downloading 'boot.img'...
OKAY [ 0.328s]
booting...
OKAY [ 0.251s]
finished. total time: 0.578s
and it reboots normally. If I try this:
E:\Programs\Android>fastboot flash recovery recovery.img
target reported max download size of 536870912 bytes
sending 'recovery' (9160 KB)...
OKAY [ 0.328s]
writing 'recovery'...
OKAY [ 0.407s]
finished. total time: 0.734s
Then select recovery on the phone, it just shuts off.
It says "Mismatched partition size (recovery)" in pink when I flash the recovery image but I read that that can be ignored if you use the first method.
Any help would be great!
Click to expand...
Click to collapse
You use Volume Up, not the power button to select Recovery. The mismatch is normal because you're flashing a non-stock recovery.

Wow I knew it was going to be something dead simple I was missing, thanks I'll give that a go when I get home!

help with VTR-L09 wrong pie?

Hi All.
Today i flashed TWRP on my phone Huawei P10 (europe version)
This works great so far so good.
I downloaded on this site and section:
1
VTR-L09C432E1R1P9B157 (9.0.1.157) the files:
update_full_VTR-L09_hw_eu.zip
update.zip
i cleaned cache/dalvik and i done a clean on internal storage.
then i say install :
HuRUpdater_0.3
boot no go...
then i install VTR-L09_hw_eu.zip
update.zip
but got allot of errors but i boots anyway....
It boots into PIE and touchscreen is not at correct place (its 3mm off) and i have no services with my provider (simcart not working)
when i take a closer look what software its running its:
model VKY
BUILD NR: LGRP2-OVS 9.0.1.163
EMUI 9.0.1
BASEBAND: 21C30B323S006C000
So its not VTR but i have PIE VKY... and i think the VKY got a different chipset for service provider then the VTR.
But my question is:
what am i doing wrong? do i need other flash file? can someone please point me to the good direction.
Regards.
Tim

Oke i discovered maybe the problem. I think its not flashing at all.. and the VKY is a wrong downloaded img from erecovery (i tryed that also) he connected thru wifi before and downloaded a img from huawei site.
When i flash update i got these msg:
installing zip file /external_sd/update/update.zip
no digest file found
script succeeded /data
script succeeded false
write radio image
check_write_data_to_partition,write data error
update_huawei_pkg_from_ota_zip update package from zip failed
E: unknown command errno
E: unknown command subproccesresult
updater ended with error 9
error installing zip file
updating partition details
...done.

update: and i hope someone would help me..
I have now TWRP only.
But for some reason i cant install the images i download. So i dont get a OS installed.
Can please someone help me
regards, Tim
is it possible that this is the problem:
c:\Users\Tim\Desktop\w>fastboot flash recovery twrp.img
target reported max download size of 471859200 bytes
sending 'recovery' (32034 KB)...
OKAY [ 0.693s]
writing 'recovery'...
FAILED (remote: partition length get error)
finished. total time: 0.705s
c:\Users\Tim\Desktop\w>fastboot flash recovery_ramdisk twrp.img
target reported max download size of 471859200 bytes
sending 'recovery_ramdisk' (32034 KB)...
OKAY [ 0.695s]
writing 'recovery_ramdisk'...
OKAY [ 0.301s]
finished. total time: 1.001s
Only recovery_ramdisk gives me TWRP not like the tutorials tell me todo (recovery)