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] Flashing firmware error

A friend of mine has a CID 044 and still got ICS since his Bootloader is already unlocked and he doesn't get OTAs
So, he tried to install the Jelly bean firmware from here: http://forum.xda-developers.com/showthread.php?t=1957376
and while writing the commands he ran into a problem, thats what he said happened:
After he wrote the first command [fastboot oem rebootRUU] the phone rebooted into the HTC logo and got stuck there, so he rebooted it again and it rebooted as usual
Then he got it back to fastboot USB, wrote the second command and this is what he got:
{
"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"
}
Anyone knows whats wrong?

You can't run that command in fastboot mode. When he ran 'fastboot oem rebootRUU' the phone should have rebooted to a black screen with the HTC logo - this is normal. While on that screen run the second command to flash the zip (he'll probably have to run it twice because it usually throws an error the first time round).

hopscotchjunkie said:
You can't run that command in fastboot mode. When he ran 'fastboot oem rebootRUU' the phone should have rebooted to a black screen with the HTC logo - this is normal. While on that screen run the second command to flash the zip (he'll probably have to run it twice because it usually throws an error the first time round).
Click to expand...
Click to collapse
Hey, im his friend with the firmware problem.
I did as you said (did it more then twice) and got the next problem:
I cant post photoes here so i'll just copy it
c:\fastboot>fastboot flash zip firmware.zip
sending 'zip' <12875 KB>...
OKAY [ 1.672s]
writing 'zip'...
<bootloader> adopting the signature contained in this image...
FAILED <remote: 99 unknown fail>
finished. total time: 2.281s
Click to expand...
Click to collapse
Any chance you know whats the problem is?
Thanks alot

1. Which version of the firmware are you trying to flash?
2. Did you relock your bootloader before starting? If not, boot back into fastboot, run 'fastboot oem lock' and then try again.

hopscotchjunkie said:
1. Which version of the firmware are you trying to flash?
2. Did you relock your bootloader before starting? If not, boot back into fastboot, run 'fastboot oem lock' and then try again.
Click to expand...
Click to collapse
1. copyed from where i downloaded
x.xx.707.x - Asia WWE (World Wide English)
cidnum: HTC__044
Download:
firmware.zip with hboot 1.36
2. I didnt relock my bootloader before starting,
Now it finnaly worked, but it stuck on the black screen with the htc logo, and it added like a green loading bar that showed that it had finished loading but still stuck on this screen.
Should I wait for something to happend or reboot manually?

Reboot manually (use 'fastboot reboot-bootloader' to get back into the bootloader and unlock it again)

[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

fastboot flash system: partition not found

Hi All,
used my OP7T for a week before deciding to unlock. That went fine, but when I tried to flash a GSI (no custom ROMs available yet), it says partition not found?? Tried system and system_a.
Code:
[email protected]:~/Downloads/Android$ fastboot flash system system-quack-arm64-ab-vanilla.img
Sending sparse 'system' 1/3 (786428 KB) OKAY [ 24.933s]
Writing sparse 'system' 1/3 FAILED (remote: 'Partition not found')
Finished. Total time: 24.950s
[email protected]:~/Downloads/Android$ fastboot flash system_a Havoc-OS-3.0_ARM64-AB.img
Sending sparse 'system_a' 1/3 (786428 KB) OKAY [ 24.953s]
Writing sparse 'system_a' 1/3 FAILED (remote: 'Partition not found')
Finished. Total time: 24.965s
[email protected]:~/Downloads/Android$

Hey,
I have the same issue, did you ever find a solution?

You must unlock first

You don't say
In the meantime I found the actual solution, here it is for the record : reboot from fastboot to fastbootd using "fastboot reboot fastboot"
And then the commands will work

natinusala said:
You don't say
In the meantime I found the actual solution, here it is for the record : reboot from fastboot to fastbootd using "fastboot reboot fastboot"
And then the commands will work
Click to expand...
Click to collapse
Got: "fastboot: usage: unknown reboot target fastboot"

bump
SecondSon1 said:
Got: "fastboot: usage: unknown reboot target fastboot"
Click to expand...
Click to collapse
been messing all night with fastboot trying to get it to boot to fastbootd
i keep getting this same error and so my phone is currently bricked as i cannot install the
system.img or anything that follows. also tried booting to fastbootd by doing
fastboot reboot recovery but it cannot find reboot target recovery either.

this is what i did
dosnoventa said:
been messing all night with fastboot trying to get it to boot to fastbootd
i keep getting this same error and so my phone is currently bricked as i cannot install the
system.img or anything that follows. also tried booting to fastbootd by doing
fastboot reboot recovery but it cannot find reboot target recovery either.
Click to expand...
Click to collapse
i got it working

Please help
sathara said:
i got it working
Click to expand...
Click to collapse
I'm getting
remote: Failed operation not permitted
and
remote: value to large for defined data type please help

i had the same problem. solved it by flashing msm extended recovery to both slots. that recovery has option to enter fastbootd

altojd said:
i had the same problem. solved it by flashing msm extended recovery to both slots. that recovery has option to enter fastbootd
Click to expand...
Click to collapse
Can you share that recovery image?
I couldn't find it in the Rom files.

For my 600th post on XDA, I offer this info in hopes it will help.
This one is T-mobile. Don't know if it will help ort harm but it works for me.
I don't have both hands right now; yoiu'll have to search for yourself on how to enter "EDL" mode and possibly an MSM (or is it MDM?) version of stock flashable file for your model and carrier, else maybe try the T-Mobile one at your own risk: Unbrick Tool for T-Mobile
GOOD LUCK

Hi guys,
When I type ' fastboot reboot fastboot ' in windows command prompt, I got the help menu of fastboot, anyone got a solution ?
My phone (Redmi 9 Note Pro) is bricked because I can't flash a system.img
Booting into fastboot using volumedown + power isn't working.
OKAY [ 17.778s]
writing 'system'...
FAILED (remote: Partition not found)

josdehaes said:
Hi All,
used my OP7T for a week before deciding to unlock. That went fine, but when I tried to flash a GSI (no custom ROMs available yet), it says partition not found?? Tried system and system_a.
Code:
[email protected]:~/Downloads/Android$ fastboot flash system system-quack-arm64-ab-vanilla.img
Sending sparse 'system' 1/3 (786428 KB) OKAY [ 24.933s]
Writing sparse 'system' 1/3 FAILED (remote: 'Partition not found')
Finished. Total time: 24.950s
[email protected]:~/Downloads/Android$ fastboot flash system_a Havoc-OS-3.0_ARM64-AB.img
Sending sparse 'system_a' 1/3 (786428 KB) OKAY [ 24.953s]
Writing sparse 'system_a' 1/3 FAILED (remote: 'Partition not found')
Finished. Total time: 24.965s
[email protected]:~/Downloads/Android$
Click to expand...
Click to collapse
Did you find a solution ?

Download latest fastboot drivers.
From OS:
adb reboot fastboot
Or from bootloader
fastboot reboot fastboot
With devices launched on Android 10 there is a new interface called fastbootd, this is where you flash the system.

Lethien said:
Did you find a solution ?
Click to expand...
Click to collapse
clearly. there is a difference between "old" fastboot (bootloader) and fastbootd (userspace fastboot to support dynamic partitions). You need to be in fastbootd to do most stuff nowadays.

{
"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"
}
My problem is bit different, can anybody help through this --- System partitioned doesn't exist !!!! while Gsi flashing on Realme 7 RMX2151

So when you see people posting in their tutorial;
fastboot reboot fastboot
NOW we type in;
fastboot reboot fastbootd?

No, same command, but you need stock recovery for this to work (twrp prevents fastbootd entry)

I tried for days to get to work but for TMobile follow guide on here and if it doesn't work even after you install drivers and all then use a different PC bc I have 7t and 8t OnePlus and my 8t unlocked works on my gf PC and her 7t TMobile works on mine figured that out the hard way but it's truthfully a solution when everything won't work

Levi0630 said:
I tried for days to get to work but for TMobile follow guide on here and if it doesn't work even after you install drivers and all then use a different PC bc I have 7t and 8t OnePlus and my 8t unlocked works on my gf PC and her 7t TMobile works on mine figured that out the hard way but it's truthfully a solution when everything won't work
Click to expand...
Click to collapse
Convert TMobile op7t to global using msmtool

need help! accidentally flashed twrp.img as boot, now phone shows that it's destroyed

Hi guys, i really need help here.
i wanted to flash and install TWRP.img on my redmi note 8 today, but i accidentally used the cmd command fastboot flash boot TWRP.img .
my phone then only boots to TWRP instead of my usual MIUI. so i tried flashing the whole note 8 rom using MiFlashTool. However, there is a error (error:Mismatching image and device), and now my phone only shows me that "the system has been destroyed".
when i tried to flash another boot.img to the phone, it shows "FAILED (command write failed (unknown error))"
{
"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"
}
anyone know what i should do to fix this phone? will really appreciate any help... :crying:

I don't know if you can enter to fastboot mode (power + vol down button). If you can, you can try fastboot flash recovery TWRP.img and search for boot.img at Google I think....
---------- Post added at 23:41 ---------- Previous post was at 23:36 ----------
I think this may helps: https://c.mi.com/thread-2542493-1-0.html
I think that the key is to get boot.img (miui or custom rom) from installation zip and flash it again to the phone via fastboot

If you could boot into twrp, then try to flash the boot image of your firmware from twrp. First extract the boot image and place it in your SD card, then in twrp select flash image and flash it to the boot partition, might work.

I got the same message even when trying to boot into recovery, even flashing the recovery again didn't work, so I downloaded The stock rom uncompressed and flashed each img manually with fastboot

Leeban Joseph said:
If you could boot into twrp, then try to flash the boot image of your firmware from twrp. First extract the boot image and place it in your SD card, then in twrp select flash image and flash it to the boot partition, might work.
Click to expand...
Click to collapse
This is the right solution
Dont worry you phone isnot destroyed ,just fellow these instructions

Hello Community!
I unlocked my 7 days old REDMI NOTE 8 with MI UNLOCK. All fine.
Then I Boot into Fastboot-mode and flashed TWRP.IMG (twrp-3.3.1-0-ginkgo.img) and started into TWRP (Recovery). On internal drive i copied new XIAOMI.EU, deleted all data. Take a reboot into Recovery, too.
But now I get "Message THE SYSTEM hat been destroyed".
MI UNLOCK SAYs UNLOCK no Nessesary. Is unlocked.
I COULD NOT BOOT INTO TWRP after Flashing TWRP.IMG
Devicecheck:
d:\platform-toolsfastboot devices
130fd5f2 fastboot
Writing TWRP is possible:
d:\platform-toolsfastboot flash recovery twrp.imgSending 'recovery' (65536 KB) OKAY [ 1.673s]
Writing 'recovery' OKAY [ 0.287s]
Finished. Total time: 1.980s
Command CONTINUE:
d:\platform-toolsfastboot continue
resuming boot FAILED (status read failed (Too many links))
Finished. Total time: 30.073s
Can Someone help me, please?
Many Thanks!

I tried to flash with MI Flash (Fastboot.rom)
ginkgo_global_images_V11.0.3.0.PCOMIXM_20191119.0000.00_9.0_global_a8923e1765.tgz
Now I am back to Stock!
Thank you!