Develop Bugs

[Q] Help Please! Evo 4g (soft?) bricked!

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

[Q] Can't flash or change anything

I faced a strange behavior of HOX (tegra). It stuck in bootloops - complete boot, starts apps, then black screen and reboot, and all over again till battery drain.
But strange thing is that i can't do anything - all changes that i do disappear after reboot. Deleted files has returned. Disabled wifi|bt are working again. But there is more! About a year ago i has unlocked bootloader, flash cwm recovery. Now, if i flash other recovery (even stock) through fastboot, i still see my old cwm. If i do full wipe in recovery - phone still boot and all apps and files are there. fastboot oem lock has no effect - phone reboot and have "unlocked" message.
When i flash other rom from recovery, of course, nothing changed, however this process goes without any errors. But it does it too quickly, so i think it don't actually writes anything, only "simulates".
Maybe it hardware problem? Or some wicked setting that i've miss?

Arrgh! Looks like a hardware failure to me...
Post the result of fastboot getvar version-main
May b running a ruu or restoring a nandroid might fix this... However, if the Bootloader isn't getting locked... Then I'm afraid running a ruu would be useless...
-Sent from my IceCold One X!

vin4yak said:
Post the result of fastboot getvar version-main
Click to expand...
Click to collapse
version-main: 1.29.707.11
finished. total time: 0.008s

SonicGD said:
I faced a strange behavior of HOX (tegra). It stuck in bootloops - complete boot, starts apps, then black screen and reboot, and all over again till battery drain.
But strange thing is that i can't do anything - all changes that i do disappear after reboot. Deleted files has returned. Disabled wifi|bt are working again. But there is more! About a year ago i has unlocked bootloader, flash cwm recovery. Now, if i flash other recovery (even stock) through fastboot, i still see my old cwm. If i do full wipe in recovery - phone still boot and all apps and files are there. fastboot oem lock has no effect - phone reboot and have "unlocked" message.
When i flash other rom from recovery, of course, nothing changed, however this process goes without any errors. But it does it too quickly, so i think it don't actually writes anything, only "simulates".
Maybe it hardware problem? Or some wicked setting that i've miss?
Click to expand...
Click to collapse
What was the last thing you changed before the bootloop started?
You said you cant flash recovery, is the bootloader relocked?

tony_76 said:
What was the last thing you changed before the bootloop started?
You said you cant flash recovery, is the bootloader relocked?
Click to expand...
Click to collapse
Phone isn't mine, so i don't know what exactly happen, but owner said, that phone's batter just drain, so he attach charger, phone boot and start looping.
Bootloader said it's 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"
}
I can flash recovery:
Code:
fastboot.exe flash recovery endeavoru_recovery_signed.img
sending 'recovery' (5786 KB)...
OKAY [ 0.863s]
writing 'recovery'...
(bootloader) Format partition SOS done
OKAY [ 0.557s]
finished. total time: 1.425s
But after that recovery still cwm, whatever i flash - stock, twrp or other cwm version.

So i've managed to load RUU mode with "adb shell reboot oem-78". When i try to flash firmware.zip in stops at "adopting the signature contained in this image". So, i think, bootloader must be relocked. How can it be done not by "fastboot oem lock"? Maybe there is another way or command? Maybe patch file or so?

I was trying do something more and was found out that i even can't run parted on dev/block/mmcblk0. So, i think, i will return it to it's owner and he will send it to service center.
If I find out what the problem was - I write in this topic

[RESOLVED] Don't have an OS, in need of help

So I managed to get my phone to this state:
{
"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"
}
Actually I was using this tutorial: http://theunlockr.com/2014/07/15/how-to-unroot-the-htc-desire-816/
My laptop couldn't recognize the phone so I manually rebooted to fastboot, then I entered "fastboot oem relock" and tried to flash but it did NOT work. Now all I have is a bootloader menu. I also tried this but it says that the Hboot version is older. H E L P

Relock the bootloader and install custom ROM ? And are you try this command fastboot " fastboot flash zip 0P9CIMG.zip" ?

tifalyz said:
Relock the bootloader and install custom ROM ? And are you try this command fastboot " fastboot flash zip 0P9CIMG.zip" ?
Click to expand...
Click to collapse
Yup.
C:\Users\Chris\Desktop>fastboot flash zip 0P9CIMG.zip
< waiting for device >
sending 'zip' (1033121 KB)... OKAY [ 78.142s]
writing 'zip'... INFOsignature checking...
FAILED (remote: signature verify fail)
finished. total time: 153.473s

Try this RUU maybe? http://forum.xda-developers.com/desire-816/general/0p9cimga5ulk44desiresense60htceurope1-t2946515
If you still get the signature verify fail error theres something wrong.

FoxyDrew said:
Try this RUU maybe? http://forum.xda-developers.com/desire-816/general/0p9cimga5ulk44desiresense60htceurope1-t2946515
If you still get the signature verify fail error theres something wrong.
Click to expand...
Click to collapse
Since swearing around here is blocked, imma try something new
C:\Users\Chris\Desktop>fastboot flash zip filename.zip
sending 'zip' (1023339 KB)... OKAY [ 70.279s]
writing 'zip'... INFOsignature checking...
FAILED (remote: signature verify fail)
finished. total time: 144.966s
What does *** TAMPERED *** even mean though, it's on the top of the screen on the screenshot.

exlective said:
Since swearing around here is blocked, imma try something new
C:\Users\Chris\Desktop>fastboot flash zip filename.zip
sending 'zip' (1023339 KB)... OKAY [ 70.279s]
writing 'zip'... INFOsignature checking...
FAILED (remote: signature verify fail)
finished. total time: 144.966s
What does *** TAMPERED *** even mean though, it's on the top of the screen on the screenshot.
Click to expand...
Click to collapse
The tampered just means that your phone was previously unlocked/rooted.
Follow all the instructions in the second part of THIS thread, making sure to use YOUR RUU file.
If that fails, re-unlock your bootloader, re-flash a custom recovery, and install custom ROM or a backup.
I have to ask, why did you decide to unroot and relock?
Also swearing isn't allowed on the forums in any way, don't try to get around it.

FoxyDrew said:
The tampered just means that your phone was previously unlocked/rooted.
Follow all the instructions in the second part of THIS thread, making sure to use YOUR RUU file.
If that fails, re-unlock your bootloader, re-flash a custom recovery, and install custom ROM or a backup.
I have to ask, why did you decide to unroot and relock?
Also swearing isn't allowed on the forums in any way, don't try to get around it.
Click to expand...
Click to collapse
After it didn't work using CMD, I looked up the thread you linked and what do I see? You saying it should be done with the sdcard method haha, so I tried it that way and it worked. Thanks for all the help Drew.
I wanted to return to stock because of 3 reasons. I might be swapping my phone for an M7, because even though we have to wait till March/April, I do want that sweet, sweeeet Lollipop+Sense update (if the trade doesn't work), and because even though CM11 is stable, I got sick of it. CM12 has some minor bugs that just get on my nerves.

exlective said:
After it didn't work using CMD, I looked up the thread you linked and what do I see? You saying it should be done with the sdcard method haha, so I tried it that way and it worked. Thanks for all the help Drew.
I wanted to return to stock because of 3 reasons. I might be swapping my phone for an M7, because even though we have to wait till March/April, I do want that sweet, sweeeet Lollipop+Sense update (if the trade doesn't work), and because even though CM11 is stable, I got sick of it. CM12 has some minor bugs that just get on my nerves.
Click to expand...
Click to collapse
No problem, and the Desire 816 is also getting the Lollipop+Sense update from HTC in March.

FoxyDrew said:
No problem, and the Desire 816 is also getting the Lollipop+Sense update from HTC in March.
Click to expand...
Click to collapse
That's what I said At least I think that's what I said, I've been struggling with this phone for 4 hours and my brain is melting atm

os missing
exlective said:
So I managed to get my phone to this state:
Actually I was using this tutorial: http://theunlockr.com/2014/07/15/how-to-unroot-the-htc-desire-816/
My laptop couldn't recognize the phone so I manually rebooted to fastboot, then I entered "fastboot oem relock" and tried to flash but it did NOT work. Now all I have is a bootloader menu. I also tried this but it says that the Hboot version is older. H E L P
Click to expand...
Click to collapse
hii
can you please tell me how that happened .. how the OS deleted >> please

smtb said:
hii
can you please tell me how that happened .. how the OS deleted >> please
Click to expand...
Click to collapse
That's easy, if you wipe system partition in custom recovery, your Rom will be gone, you'll need to flash a nandroid backup (easy) or RUU (harder)to get it back

'(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