Develop Bugs

Desire doesn't boot into recovery nor flash new one

So i tried to flash new ROM. got inte bootloader, chose option "recovery" but seems like it freezes at HTC splash screen. So i connected device to computer and tried to flash two new recoveries, CWM and...some other i can't name of the top of my head. Using fastboot flash recovery command. they resulted:
sending 'recovery' (4182 KB)...
FAILED (status malformed (1 bytes))
finished. total time: 0.001s
What should I do?`
Device S-OFF with alpharev

Amphor said:
So i tried to flash new ROM. got inte bootloader, chose option "recovery" but seems like it freezes at HTC splash screen. So i connected device to computer and tried to flash two new recoveries, CWM and...some other i can't name of the top of my head. Using fastboot flash recovery command. they resulted:
sending 'recovery' (4182 KB)...
FAILED (status malformed (1 bytes))
finished. total time: 0.001s
What should I do?`
Device S-OFF with alpharev
Click to expand...
Click to collapse
try this:
first:
Code:
fastboot erase recovery
then:
Code:
fastboot flash recovery [URL="http://www.mediafire.com/?5xrndbh5obumfz7"]recovery.img[/URL]
MD5: 6CBF5C129739F3DE0948EA6F3D274CEA

erasing 'recovery'...
FAILED (status malformed (1 bytes))
finished. total time: 0.002s

try different cable/pc
fastboot devices working?

Amphor said:
erasing 'recovery'...
FAILED (status malformed (1 bytes))
finished. total time: 0.002s
Click to expand...
Click to collapse
Put the attached file in the root of your sd-card, and boot into HBOOT (not fastboot).
You may need a goldcard for it to work.

I was always in hboot, not in fastboot, so flashing didn't work(but devices did)
My bad

Amphor said:
I was always in hboot, not in fastboot, so flashing didn't work(but devices did)
My bad
Click to expand...
Click to collapse
{
"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"
}

Not Booting

Today Morning My phone restarted automatically,then it not boot stuck at Google logo.
After some times Google logo turned into Graphic Glitches and restart.
Same thing happening again and again.
I can't able to go to recovery mode,when i tried to go,it stops at TeamWin logo and restart.
I can able to go to Fastboot mode.I tired to flash a Kernel(boot.img),same graphics glitches happen and stopped.
Fastboot error msg:
Code:
sending 'boot' (6014 KB)...
OKAY [ 0.766s]
writing 'boot'...
FAILED (status read failed (Too many links))
finished. total time: 0.797s
Any way to recover my phone?:crying:
Is it possible to reset my mobile via fastboot?
Any help please?:crying:
Graphics Glitches See Attachment.
{
"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"
}

I tried to flash a bootloader to from Nexus Images(Official).
Same error was showed.
"error out of memory"
Now i can't able go to fastboot mode
Is my mobile bricked?

Omap flash?
But it seems like your MMC died.
Beamed from my Maguro.

I tried to factory reset my mobile by flash stock image.
First i started with bootloader.img,it was stopped.
Now fastboot was not working.
Do i need to take to service center?

Read this thread http://forum.xda-developers.com/showthread.php?t=478820&page=4 and all of its posts.
Sent from my Nexus

I flashed OMAP and got fastboot.
Then i tired to flash radio,system etc..
Same error:
sending 'recovery' (4900 KB)...
OKAY [ 0.500s]
writing 'recovery'...
FAILED (status read failed (Too many links))
finished. total time: 0.571s
D:\Android\android-sdk\platform-tools>fastboot
tory-b2ebb5f3\image-yakju-jdq39\recovery.img
error: out of memory
i tired it on my Laptop and pc with different cable.

Hello? Did you read the ENTIRE, AND CLOSELY, the thread i linked you? That was only the first hit on Google-xda search.
Sent from my Nexus

Yeah i read that completely.
He has write error.
i have read error only.
Then also i tried many ports.But not succeeded.

I think it was a internal memory problem.
I can able to erase,format a system.
Only when i try to flash,problem occur.
Can any one tell me how to replace the internal memory?

Help needed with TWRP 3.3.1-0 (up & running)

Hi, that's my first customisation:
1. Device unlocked:
{
"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"
}
2. TWRP flashed + *zip ready on /sdcard1
3. Install Zip fails
The checksums of all zips are ok, verified on my notebook.
I also can't wipe. And the standard Android 7.1 is recovering itself, if I boot-up.
Please advise, thanks!

1. Try unchecking signature verification in TWRP
2. Most likely, you will have to downgrade to CM13.1 first with that mounting error
3. I recommend using the standard LOS zip, it seems you have one with microG embedded

SECURE BOOT - enabled — Am I root?
kabu83 said:
1. Try unchecking signature verification in TWRP
2. Most likely, you will have to downgrade to CM13.1 first with that mounting error
3. I recommend using the standard LOS zip, it seems you have one with microG embedded
Click to expand...
Click to collapse
Thanks, I did all that and much more, trying to install CM 13.1, crDroid, OrangeFox, SuperSu => nothing installs!
Now I wonder: Am I root at all? I thought so, since I installed TWRP on a naked device?!
The bootloader shows: DEVICE STATE - unlocked

The Problem is, that TWRP cannot mount /system in the first place.
Have you tried downgrading following these steps: https://forum.xda-developers.com/showpost.php?p=72261104

TWRP cannot mount /system
kabu83 said:
The Problem is, that TWRP cannot mount /system in the first place.
Have you tried downgrading following these steps: https://forum.xda-developers.com/showpost.php?p=72261104
Click to expand...
Click to collapse
Now, that my holidays are over, I want this Crackling to crack!
Here my efforts to crack it via Fastboot:
Since the vintage Cyanogen fails as well as the state of the art Linage, I suspect that the payload might not be the cause for the failure?!
Code:
# fastboot flash system lineage-16.0-20190826-microG-crackling.zip
target reported max download size of 268435456 bytes
Invalid sparse file format at header magic
error: write_sparse_skip_chunk: don't care size 271225615 is not a multiple of the block size 4096
error: write_sparse_skip_chunk: don't care size 2794255 is not a multiple of the block size 4096
erasing 'system'...
OKAY [ 0.841s]
sending sparse 'system' 1/3 (262140 KB)...
error: write_sparse_skip_chunk: don't care size 271225615 is not a multiple of the block size 4096
error: write_sparse_skip_chunk: don't care size 271225615 is not a multiple of the block size 4096
OKAY [ 8.258s]
writing 'system' 1/3...
FAILED (remote: buffer overreads occured due to invalid sparse header)
finished. total time: 16.173s
# fastboot erase system
******** Did you mean to fastboot format this ext4 partition?
erasing 'system'...
OKAY [ 1.042s]
finished. total time: 1.043s
# fastboot flash system SW27-WF-CRACKLING-CM-13.1.5-ZNH2KAS7EB-RECOVERY.zip
target reported max download size of 268435456 bytes
Invalid sparse file format at header magic
error: write_sparse_skip_chunk: don't care size 619158578 is not a multiple of the block size 4096
error: write_sparse_skip_chunk: don't care size 350727218 is not a multiple of the block size 4096
error: write_sparse_skip_chunk: don't care size 82295858 is not a multiple of the block size 4096
erasing 'system'...
OKAY [ 0.831s]
sending sparse 'system' 1/4 (262140 KB)...
error: write_sparse_skip_chunk: don't care size 619158578 is not a multiple of the block size 4096
error: write_sparse_skip_chunk: don't care size 619158578 is not a multiple of the block size 4096
OKAY [ 8.290s]
writing 'system' 1/4...
FAILED (remote: buffer overreads occured due to invalid sparse header)
finished. total time: 14.176s
# fastboot erase recovery
erasing 'recovery'...
OKAY [ 0.205s]
finished. total time: 0.205s
# fastboot flash recovery twrp-3.3.1-0-crackling.img
target reported max download size of 268435456 bytes
sending 'recovery' (16984 KB)...
OKAY [ 0.563s]
writing 'recovery'...
OKAY [ 1.188s]
finished. total time: 1.751s
# fastboot boot twrp-3.3.1-0-crackling.img
downloading 'boot.img'...
OKAY [ 0.535s]
booting...
OKAY [ 0.672s]
finished. total time: 1.208s

Boot to recovery (TWRP), then touch the bottom right menu button, what does it say in the terminal log? (Similar to the 2nd screenshot you posted.)

Bootloader vs BIOS
kabu83 said:
Boot to recovery (TWRP), then touch the bottom right menu button, what does it say in the terminal log? (Similar to the 2nd screenshot you posted.)
Click to expand...
Click to collapse
At the time of the Cyanogen/Linage installation I had no TWRP installed! Would it help to repeat the process?
In general, I assumed the Bootloader to function similar to the BIOS at a PC? That makes me wonder, why an Android installation-process via Fastboot can't just reformat the entire drive and do a fresh partitioning? (instead of complaining about 'chunks' and 'block-sizes')
Thanks for all your assistance, most appreciated! :good:

[email protected] said:
At the time of the Cyanogen/Linage installation I had no TWRP installed! Would it help to repeat the process?
In general, I assumed the Bootloader to function similar to the BIOS at a PC? That makes me wonder, why an Android installation-process via Fastboot can't just reformat the entire drive and do a fresh partitioning? (instead of complaining about 'chunks' and 'block-sizes')
Thanks for all your assistance, most appreciated! :good:
Click to expand...
Click to collapse
I would recommend installing TWRP, Version 3.2.1-0.
Then boot to recovery and check, if TWRP can mount the system Partition.
What OS do you have currentyl installed?

/system is empty
kabu83 said:
I would recommend installing TWRP, Version 3.2.1-0.
Then boot to recovery and check, if TWRP can mount the system Partition.
What OS do you have currently installed?
Click to expand...
Click to collapse
As mentioned, I prefer a clean install. Thus formatted /system with ext4 via Fastboot (it's default). It should be possible to mount an empty /system -- isn't it?

A clean install is needed anyway. It seems just easier to install the OS via TWRP and for future nightly updates anyway.

Heureka!
kabu83 said:
I would recommend installing TWRP, Version 3.2.1-0.
Click to expand...
Click to collapse
With TWRP 3.2.1-0 I managed to install SW27-WF-CRACKLING-CM-13.1.5-ZNH2KAS7EB-RECOVERY.zip :good:
(I failed though to install "lineage-16.0-20190826-microG-crackling.zip" before.)
What's next? Replacing Cyanogen Bootloader with TWRP 3.2.1-0 again?
Then trying a pure Lineage and later Gapps seperately?

[email protected] said:
With TWRP 3.2.1-0 I managed to install SW27-WF-CRACKLING-CM-13.1.5-ZNH2KAS7EB-RECOVERY.zip :good:
(I failed though to install "lineage-16.0-20190826-microG-crackling.zip" before.)
What's next? Replacing Cyanogen Bootloader with TWRP 3.2.1-0 again?
Then trying a pure Lineage and later Gapps seperately?
Click to expand...
Click to collapse
Can you boot into CM 13 now?
Has it replaced TWRP as recovery?

Bingo!
kabu83 said:
Can you boot into CM 13 now?
Has it replaced TWRP as recovery?
Click to expand...
Click to collapse
I've got Cyanogen Fastboot, Lineage Bootloader, and Lineage Crackling 190801.002 up and running… :good:
With CM 13 installed, TWRP directly installed "lineage-16.0-20190826-microG-crackling.zip" from SD-card.
Thanks again for your advice, it appears that the Android System which Google offers as update to CM13, indeed prevented the alternative OS installation somehow.

[email protected] said:
I've got Cyanogen Fastboot, Lineage Bootloader, and Lineage Crackling 190801.002 up and running… :good:
With CM 13 installed, TWRP directly installed "lineage-16.0-20190826-microG-crackling.zip" from SD-card.
Thanks again for your advice, it appears that the Android System which Google offers as update to CM13, indeed prevented the alternative OS installation somehow.
Click to expand...
Click to collapse
Happy to help. So you are all set now?

'(bootloader) is-logical:recovery: not found' error when trying to flash TWRP

Hello
Today I tried to flash TWRP on my Moto G5S because I wanted to use a custom ROM. While trying to flash TWRP on the phone, I got this error:
Code:
(bootloader) is-logical:recovery: not found
Sending 'recovery' (15850 KB) OKAY [ 0.696s]
Writing 'recovery' (bootloader) Image not signed or corrupt
OKAY [ 0.387s]
Finished. Total time: 1.191s
I have USB Debugging enabled, the bootloader is unlocked, and I'm using the latest version of TWRP (3.3.1.0) made for this phone.
I have never installed TWRP or anything similar before, so I don't know how to fix this. I have searched on Google, but no results are about this same problem. If anyone knows how to fix this issue, please tell me how.
Thanks.

Lekrkoekj said:
Hello
Today I tried to flash TWRP on my Moto G5S because I wanted to use a custom ROM. While trying to flash TWRP on the phone, I got this error:
Code:
(bootloader) is-logical:recovery: not found
Sending 'recovery' (15850 KB) OKAY [ 0.696s]
Writing 'recovery' (bootloader) Image not signed or corrupt
OKAY [ 0.387s]
Finished. Total time: 1.191s
I have USB Debugging enabled, the bootloader is unlocked, and I'm using the latest version of TWRP (3.3.1.0) made for this phone.
I have never installed TWRP or anything similar before, so I don't know how to fix this. I have searched on Google, but no results are about this same problem. If anyone knows how to fix this issue, please tell me how.
Thanks.
Click to expand...
Click to collapse
DId this ever get fixed? I have been going through the same process on my moto x4 - twrp - flashing lineageOS but I am having hang ups and I think they are bootloader related

Lekrkoekj said:
Hello
Today I tried to flash TWRP on my Moto G5S because I wanted to use a custom ROM. While trying to flash TWRP on the phone, I got this error:
Code:
(bootloader) is-logical:recovery: not found
Sending 'recovery' (15850 KB) OKAY [ 0.696s]
Writing 'recovery' (bootloader) Image not signed or corrupt
OKAY [ 0.387s]
Finished. Total time: 1.191s
I have USB Debugging enabled, the bootloader is unlocked, and I'm using the latest version of TWRP (3.3.1.0) made for this phone.
I have never installed TWRP or anything similar before, so I don't know how to fix this. I have searched on Google, but no results are about this same problem. If anyone knows how to fix this issue, please tell me how.
Thanks.
Click to expand...
Click to collapse
its says image not signed or corrupt, did you make sure that flashing=unlocked at the bootom of the screen on bootloader menu (fastboot)?????????

Rush said:
its says image not signed or corrupt, did you make sure that flashing=unlocked at the bootom of the screen on bootloader menu (fastboot)?????????
Click to expand...
Click to collapse
Yes

I want this to get fixed because LineageOS 17.1 is taking a lot of space on my Moto X4. I wanna flash PixelExperience... You can see the screenshot I have attached.
{
"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"
}

Maybe its too late but I solved it by activating USB Debugging

Lenovo P2 stuck in "Fast boot" menu. Bricked?

I have a Lenovo P2, unrooted, on stock Android, with a 256mb micro SD card. It hasn't been unlocked/flashed/rooted in any way apart from Developer Options to allow ADB.
A couple of days ago the phone started to lag and lock up, and then rebooted into "AP Fastboot Flash Mode (Secure)" menu. The only options are Start/Barcodes/Power Off.
The Start and Power Off/On options simply reboot back to the same screen after a couple of seconds. It won't boot back into Android with any combination of volume up/down/power buttons, or offer me any other options such as recovery or clear cache etc.
I've tried rebooting with/without the SD card - it makes no difference.
The phone still appears to be recognised by ADB when I connect it to a laptop - it appears in 'fastboot devices' - but I still can't get it to exit fastboot and boot back into Android with any ADB command.
I've tried downloading Reiboot and "15 second adb" toolkits which claim to exit fastboot mode, but without success.
I'm assuming the bootloader is corrupted.
Can anyone please point me towards any possible action for fixing it, or is it bricked?
Many thanks.
{
"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"
}

The thing you are on now is the bootloader...
What you did is probably soft bricked the phone.
What did you perform with adb?

If your rom is not booting you might need to reinstall it.

Keno_I said:
The thing you are on now is the bootloader...
What you did is probably soft bricked the phone.
What did you perform with adb?
Click to expand...
Click to collapse
Here's what I've tried with ADB - the phone seems to be connected as evidenced by "fastboot devices", but I don't know what to do now. "Fastboot reboot" just brings me back to the same Fastboot screen in my original post, as does holding down vol+/vol-/power for several seconds.
I successfully unlocked/flashed a ZTE San Francisco Blade back in the day, so I don't mind trying to flash this P2 if that's the answer and you can point me towards a noob-friendly guide, please.

Reinstall the stock rom from fastboot

@Kenora_I
To try and reinstall stock, I'm following the instructions here --> https://forum.xda-developers.com/t/lenovo-p2-fastboot-files-of-every-stock-firmware.3649914/
and have downloaded all the firmware files linked on that page, ie https://www.androidfilehost.com/?w=files&flid=205781
Do I need to unlock the bootloader first?
Well, when I tried to "fastboot oem unlock", I got
fastboot oem unlock
...
FAILED (remote: oem unlock error: partition tampered
I then tried the Flash commands given, and got this error;
Fastboot flash system systemchunk0.img
target reported max download size of 536870912 bytes
sending 'system' (260121 KB)...
OKAY [ 9.303s]
writing 'system'...
FAILED (remote: Not official valid sparse image)
finished. total time: 9.379s
I got this with every set of firmware files on the download link. Am I trying to use the wrong firmware images?
Thanks for any tips and suggestions.

bigajm said:
@Kenora_I
To try and reinstall stock, I'm following the instructions here --> https://forum.xda-developers.com/t/lenovo-p2-fastboot-files-of-every-stock-firmware.3649914/
and have downloaded all the firmware files linked on that page, ie https://www.androidfilehost.com/?w=files&flid=205781
Do I need to unlock the bootloader first?
Well, when I tried to "fastboot oem unlock", I got
fastboot oem unlock
...
FAILED (remote: oem unlock error: partition tampered
I then tried the Flash commands given, and got this error;
Fastboot flash system systemchunk0.img
target reported max download size of 536870912 bytes
sending 'system' (260121 KB)...
OKAY [ 9.303s]
writing 'system'...
FAILED (remote: Not official valid sparse image)
finished. total time: 9.379s
I got this with every set of firmware files on the download link. Am I trying to use the wrong firmware images?
Thanks for any tips and suggestions.
Click to expand...
Click to collapse
You have to find and flash a valid flash image, try with the same version you were installed on

Can someone provide me with a twrp restore file? I tried to flash the stock rom but the bat file that came with it tampered with some files and I can't even boot into the stock rom