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"
}
Related
My Evo 4G is boot looped on the "HTC EVO 4G" whitescreen.
Instead of giving the whole story, I'm just going to supply what I believe is relevant - please let me know if additional info would help.
Bootloader Reads:
SUPERSONIC EVT2-3 SHIP S-OFF
HBOOT-2.10.0001
RADIO-2.15.00.11.19
Symptoms/Behavior Observed:
I cannot boot into recovery (I just end up boot looping as described).
I can enter FASTBOOT USB and the "fastboot devices" command indicates my phone is connected.
Any "fastboot erase" or "fastboot flash" command results in "FAILED (remote: not allowed)", so I suspect my HBOOT is not the engineering version.
I cannot seem to connect with ADB, though I've only tried from FASTBOOT USB and HBOOT USB, since I can't fully boot.
Attempting to flash any image with the PC36IMG.zip method results in the file being loaded and parsed, but I'm never prompted to update or reboot, I just end up back at the main bootloader screen.
Restoring from an RUU appears to complete successfully, (radio version changes accordingly if I do so), but the phone still boot loops. I've tried multiple RUU versions.
Selecting "clear storage" from the boot menu also doesn't have any apparent effect.
Thoughts appreciated...thanks
EDIT: #5 is no longer a problem - now I seem to be able to flash via the PC36IMG method just fine.
U might have a bad SD card. Try wiping card and then try again
Here's an update:
Did a full format of the SD card as you suggest.
Then I tried flashing the 2.10 spoofed HBOOT from this thread:
http://forum.xda-developers.com/showthread.php?t=805612&page=3
That got me somewhere! From there I could execute:
C:\EVO_Softbrick\EVO\ADB>fastboot erase recovery
erasing 'recovery'... OKAY [ 0.061s]
finished. total time: 0.061s
C:\EVO_Softbrick\EVO\ADB>fastboot flash recovery recovery-RA-supersonic-v2.3.img
sending 'recovery' (3544 KB)... OKAY [ 1.038s]
writing 'recovery'... OKAY [ 1.474s]
finished. total time: 2.512s
Unfortunately, no luck getting into recovery at this point - now I get white htc screen, followed by black screen, 5 vibrations and blinking green LED. (I've seen this before - it seems to happen when I flash to an older stock rom. Flashing back to a newer stock rom causes boot looping from the white htc screen to black.)
From there I ran this RUU:
http://shipped-roms.com/download.ph....651.1_Radio_1.39.00.04.26_release_171253.exe
Which brought my HBOOT back to 0.79.0000, or so it says.
However, there were no improvements in my ability to boot to recovery or the full OS.
I also tried flashing the PC36IMG version of recovery, but I'm still getting the same behavior.
rymiwe said:
Here's an update:
Did a full format of the SD card as you suggest.
Then I tried flashing the 2.10 spoofed HBOOT from this thread:
http://forum.xda-developers.com/showthread.php?t=805612&page=3
That got me somewhere! From there I could execute:
C:\EVO_Softbrick\EVO\ADB>fastboot erase recovery
erasing 'recovery'... OKAY [ 0.061s]
finished. total time: 0.061s
C:\EVO_Softbrick\EVO\ADB>fastboot flash recovery recovery-RA-supersonic-v2.3.img
sending 'recovery' (3544 KB)... OKAY [ 1.038s]
writing 'recovery'... OKAY [ 1.474s]
finished. total time: 2.512s
Unfortunately, no luck getting into recovery at this point - now I get white htc screen, followed by black screen, 5 vibrations and blinking green LED. (I've seen this before - it seems to happen when I flash to an older stock rom. Flashing back to a newer stock rom causes boot looping from the white htc screen to black.)
From there I ran this RUU:
http://shipped-roms.com/download.ph....651.1_Radio_1.39.00.04.26_release_171253.exe
Which brought my HBOOT back to 0.79.0000, or so it says.
However, there were no improvements in my ability to boot to recovery or the full OS.
I also tried flashing the PC36IMG version of recovery, but I'm still getting the same behavior.
Click to expand...
Click to collapse
I'm on the same boat.
Please update, did you ever get it fixed!
ebay have unbrick service
What is up with all these people having boot loops lately? I've seen about 2-3 threads a week about it.
{
"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'm not sure who to give credit to for this picture. I randomly found it
Sent from my PC36100 using xda app-developers app
Don't know about the others, but the original poster killed that phone, I hate to say it, by flashing the wrong and too many RUUs, in particular from the link that was posted, OUCH. Maybe others are doing the same. I don't know.
Sent from my SAMSUNG-SGH-I747 using xda premium
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?
Hello
Please help me out
I have literally soft bricked my mobile and now I am trying to recover it
I am able to use fastboot
but now few times it is also not able to recognise the device
Also I can't use adb as my device is not found when i type
< >/adb devices
I relocked my mobile with help of thread
http://forum.xda-developers.com/showthread.php?t=1957376
and trying to recover it as per detail but it give following eror
C:\Users\Awanendra\Desktop\OneX>fastboot flash zip firmware.zip
sending 'zip' (369765 KB)...
OKAY [ 46.188s]
writing 'zip'...
(bootloader) signature checking...
FAILED (remote: 12 signature verify fail)
finished. total time: 62.624s
C:\Users\Awanendra\Desktop\OneX>fastboot flash zip firmware.zip
sending 'zip' (369765 KB)...
OKAY [ 46.271s]
writing 'zip'...
(bootloader) signature checking...
FAILED (status read failed (Too many links))
finished. total time: 58.695s
i am presently having
HTC One X -international version- Asia- India with following detail
HBOOT 1.73.0000
Radio 5.1204.167.31
cid 4.19.720.2
and my last update was to Android Jellybean
plz provide me the RUU which can help me to reuse my mobile
Please provide me the stockrecovery for same and help me out..
PLzzzzzz
awanendra said:
Hello
Please help me out
I have literally soft bricked my mobile and now I am trying to recover it
I am able to use fastboot
but now few times it is also not able to recognise the device
Also I can't use adb as my device is not found when i type
< >/adb devices
I relocked my mobile with help of thread
http://forum.xda-developers.com/showthread.php?t=1957376
and trying to recover it as per detail but it give following eror
C:\Users\Awanendra\Desktop\OneX>fastboot flash zip firmware.zip
sending 'zip' (369765 KB)...
OKAY [ 46.188s]
writing 'zip'...
(bootloader) signature checking...
FAILED (remote: 12 signature verify fail)
finished. total time: 62.624s
C:\Users\Awanendra\Desktop\OneX>fastboot flash zip firmware.zip
sending 'zip' (369765 KB)...
OKAY [ 46.271s]
writing 'zip'...
(bootloader) signature checking...
FAILED (status read failed (Too many links))
finished. total time: 58.695s
i am presently having
HTC One X -international version- Asia- India with following detail
HBOOT 1.73.0000
Radio 5.1204.167.31
cid 4.19.720.2
and my last update was to Android Jellybean
plz provide me the RUU which can help me to reuse my mobile
Please provide me the stockrecovery for same and help me out..
PLzzzzzz
Click to expand...
Click to collapse
No RUU for this base is tooo newer, unlock your bootloader and find nandroid backup and restor it or install custom rom on the phone you are with latest firmware and you daon't have nothing to do with the firmware
Thant said:
No RUU for this base is tooo newer, unlock your bootloader and find nandroid backup and restor it or install custom rom on the phone you are with latest firmware and you daon't have nothing to do with the firmware
Click to expand...
Click to collapse
Thanks but I am not able to use adb to install nandroi or custom rom so is the problem tha I am still in problem
Plz help me out
awanendra said:
Thanks but I am not able to use adb to install nandroi or custom rom so is the problem tha I am still in problem
Plz help me out
Click to expand...
Click to collapse
why you need adb you need working fastboot flash philz recovery 5.15.9 and then mount sd card copy your rom or nand backup to sd card install it flash the boot.img and vola you have working phone
Thanks a ton
u have saved me
{
"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"
}
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
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