Develop Bugs

[Q] bricked htc desire

hi,
first, excuse my poor english
then, I have a problem with my dear desire :-(
I have a rooted desire with an oxygen gingerbread rom. I was using it in the subway, as usual (I was looking at some video on youtube), and it freeze, as it sometime happen. I remove the battery to shut it down, replace it, power back and... it didn't restart! It show the white screen with green HTC letters, Vibrates 7 Times, and nothing more!
I can go into Hboot, but then, when I select recovery (to flash a rom), the phone reboot, vibrate 7 times, and that's all.
I have try with and without sdcard and simcard, => exactly the same.
what can I do? thanks for answers

Bring your back to complete stock. Download stock ruu here:
http://shipped-roms.com/download.ph...9.00.32U_5.11.05.27_release_159811_signed.exe
Boot your phone into fastboot mode and run the exe. When you get cid error, create goldcard with linux, put this in your desire and flash ruu again:
http://www.nazriawang.com/2010/04/how-to-create-goldcard-with-ubuntu.html

thanks, I'm trying it I hope it will work

I have no cid error, but the following messages:
Parsing....[SD ZIP]
[1] BOOTLOADER - OK
[2] RADIO_V2 - OK
[3] RADIO_CUST - OK
[4] BOOT -OK
[5] RECOVERY - Fail-PU
[6] SYSTEM - OK
[7] USERDATA - OK
[8] SPLASH1 - OK
Partition update fail!
Update fail!
Click to expand...
Click to collapse

I will try it: http://forum.xda-developers.com/showpost.php?p=15634713&postcount=108

I can not flash hboot; someone got an idea?
c:\Program Files (x86)\Android\android-sdk\tools>fastboot flash hboot bravo.img
sending 'hboot' (512 KB)...
OKAY [ 0.083s]
writing 'hboot'...
FAILED (remote: not allowed)
finished. total time: 0.086s
Click to expand...
Click to collapse

Post your hardware details from the bootloader please.
Sent from Oxygen with Transparent XDA App

Hi,
BRAVO PVTI SHIP S-OFF
HBOOT-0.8.0000
MICROP-031D
TOUCH PANEL-SYNT 0101
RADIO 4.06.00.02_2
MAR 29 2010, 21:34:33

Was your phone in fastboot when you wanted to flash the hboot?
Sent from Oxygen with Transparent XDA App

Hi,
Yes: since I try to install the RUU he always start in fastboot for recuperation (the black screen with HTC write in silver, and four little triangles).

Kerri007 said:
Hi,
Yes: since I try to install the RUU he always start in fastboot for recuperation (the black screen with HTC write in silver, and four little triangles).
Click to expand...
Click to collapse
This is not the fastboot mode. To get your phone into fastboot, you have to start it with pressed back and power button until the white screen with the three androids at the bottom appears, where you can see "FASTBOOT" in red highlighted letters.
Sent from Oxygen with Transparent XDA App

Hi,
I have no longer access to the boot loader; but I'm pretty sure that it is in fastboot since when I'm sending an img instead of hboot with fastboot.exe, it succeed to transfer and begin installation (but it fails with the "partition fails error", as the ruu file do)

Why can't you access bootloader/fastboot?
Sent from Oxygen with Transparent XDA App

because when I boot my phone, pressing vol. down, back, or anything, it always start on the htc black screen. If I unplug the phone, I access to hardware information and below "RUU" is write in orange

Kerri007 said:
because when I boot my phone, pressing vol. down, back, or anything, it always start on the htc black screen. If I unplug the phone, I access to hardware information and below "RUU" is write in orange
Click to expand...
Click to collapse
You have to press and hold volume down/back button FIRST and then power button. Do you do this in this order? When I read your post, I understand it so, you first press power button and then volume down or back button.

sorry, yes I press the button before pressing power; I know how to be in fastboot: I ever use it. I can not now, but, as you can see, when the phone boot on this special htc ruu mode, it is in fact in fastboot:

Kerri007 said:
sorry, yes I press the button before pressing power; I know how to be in fastboot: I ever use it. I can not now, but, as you can see, when the phone boot on this special htc ruu mode, it is in fact in fastboot:
Click to expand...
Click to collapse
What happens when you enter
Code:
fastboot reboot-bootloader
in quoted state?

MatDrOiD said:
What happens when you enter
Code:
fastboot reboot-bootloader
in quoted state?
Click to expand...
Click to collapse
hi,
the phone reboot in the ruu mode again :/
do you think that making a goldcard and puting update files on it would help?

Kerri007 said:
hi,
the phone reboot in the ruu mode again :/
do you think that making a goldcard and puting update files on it would help?
Click to expand...
Click to collapse
Maybe. Just try it.
How to create goldcard with linux:
http://www.nazriawang.com/2010/04/how-to-create-goldcard-with-ubuntu.html
How to extract rom from a ruu:
http://forum.xda-developers.com/showpost.php?p=10509780&postcount=102
Copy this file on goldcard, put this in your desire and press and hold first volume down and then power button for min 10 seconds (maybe the white screen will appear) and follow the instructions.

fastboot flash recovery problem (stuck at sending)

Hey there,
Got a bricked rom so wanna flash my Desire again.
My problem is my Recovery doesnt work.(Stucks in Mainscreen)
So i tried to flash it with fastboot (command: fastboot flash recovery recovery.img )(Security is Off) but during this command it stack at 'sending 'recovery' <3398>...'
Does anyone know why?
Help Please :S

Is 'fastboot devices' detecting the phone?
Sent from my HTC Desire using XDA App

my phone detects the fastboot usb
and in the command line doesn't stand [waiting for device] like when the phone is not connected
edit:
ah i guess you mind the fastboot devices command
yeah there is one device HT072...6 fastboot

Now I also got another error here the Details:
D:\Nero\Desktop\android-sdk-windows\tools>fastboot flash recovery recovery-cloc
kwork-3.0.0.5-bravo.img
sending 'recovery' (3398 KB)...
FAILED (status read failed (Too many links))
finished. total time: 0.002s
D:\Nero\Desktop\android-sdk-windows\tools>fastboot flash recovery recovery-cloc
kwork-3.0.0.5-bravo.img
sending 'recovery' (3398 KB)...
edit:
okay got it and flashed recovery v3.0.0.5 (i know not uptodate there is already 5.0.0.2 or sth =P)
looked up for the other error here and found a solution had to take another usb-port
but i still got the problem that i can not "install zip from sdcard" when i select it, i get a black screen with the icon of clockworkmod :S

try this http://forum.xda-developers.com/showthread.php?t=839621
you might have a PVT4 device which doesn't work with cwm

i already flashed my desire about 4times with clockworkmod
btw just checked its pvt1
but ill try alphaRev just give me a sec

after flashing it with that recovery it works
still don't know why clockworkmod won't this time cause as mentioned i used it for some ROMs before and was quiet simple
how ever at least it works again BIG thanks!

NeroBoron said:
after flashing it with that recovery it works
still don't know why clockworkmod won't this time cause as mentioned i used it for some ROMs before and was quiet simple
how ever at least it works again BIG thanks!
Click to expand...
Click to collapse
no prob, here to help

NeroBoron said:
Hey there,
Got a bricked rom so wanna flash my Desire again.
My problem is my Recovery doesnt work.(Stucks in Mainscreen)
So i tried to flash it with fastboot (command: fastboot flash recovery recovery.img )(Security is Off) but during this command it stack at 'sending 'recovery' <3398>...'
Does anyone know why?
Help Please :S
Click to expand...
Click to collapse
Hi,
I have a same problem with stucking on sending recovery...can u tell me how to resolve the problem??

mullamadd said:
Hi,
I have a same problem with stucking on sending recovery...can u tell me how to resolve the problem??
Click to expand...
Click to collapse
firstly, make sure you're phone is actually seen by the PC tpye in cmd (if you;ve got fastboot setup)
Code:
fastboot devices
should come up with you're phones serial number. If nothing comes up then a) if havent got fastboot/ SDK setup, or b) you're S-ON.
Secondly make sure you're S-OFF... if you're not you can't flash things..
thirdly, if you're S-OFF and your phone IS seen, make sure you're in FASTBOOT and not in BOOTLOADER.
to boot into fastboot you poweroff then hold BACK and POWER. or you boot it from the bootloader..
my advice to you, nothing else I can think of. At least when I'm not sober anyways

bortak said:
firstly, make sure you're phone is actually seen by the PC tpye in cmd (if you;ve got fastboot setup)
Code:
fastboot devices
should come up with you're phones serial number. If nothing comes up then a) if havent got fastboot/ SDK setup, or b) you're S-ON.
Secondly make sure you're S-OFF... if you're not you can't flash things..
thirdly, if you're S-OFF and your phone IS seen, make sure you're in FASTBOOT and not in BOOTLOADER.
to boot into fastboot you poweroff then hold BACK and POWER. or you boot it from the bootloader..
my advice to you, nothing else I can think of. At least when I'm not sober anyways
Click to expand...
Click to collapse
First of all, thanks for your answare.
My S is ON, how to make him go OFF??
When i type in fastboot devices i see my device HT97....
so, my ges is that it recognise my device...

You can download the original RUU from xda rename update put on SD. power off fastboot should run it back to stock I would then use alpharev's site to S-OFF easiest & safest. I'd run it through Virtual Machine as it saves wasting discs just remember to keep turning USB device on as it will unmount a couple of times during the procedure!
Sent from my HTC Desire using XDA App

=JP said:
You can download the original RUU from xda rename update put on SD. power off fastboot should run it back to stock I would then use alpharev's site to S-OFF easiest & safest. I'd run it through Virtual Machine as it saves wasting discs just remember to keep turning USB device on as it will unmount a couple of times during the procedure!
Sent from my HTC Desire using XDA App
Click to expand...
Click to collapse
Sory, i dont get it...downloaded apherev.iso but dont know how to use it?

You better use Revolitionary(.io)
Its more convenient an easier.
Just download ,then on windows you have to install fastboot drivers, the site will give you a betakey (for that you have to type in some phone information), extract the folder ,start revolutionary as admin ,then make sure usbdebugging is enabled an connect to charge only , type in beta key an hit enter.

WRson said:
You better use Revolitionary(.io)
Its more convenient an easier.
Just download ,then on windows you have to install fastboot drivers, the site will give you a betakey (for that you have to type in some phone information), extract the folder ,start revolutionary as admin ,then make sure usbdebugging is enabled an connect to charge only , type in beta key an hit enter.
Click to expand...
Click to collapse
i allredy try that, but, there is no support for my phone HTC magic sapphire 32b.
It sucks, im stuck here..and ther's no way to move acros.

I dont know what you have to do with a magic , sorry about that.
You may look a the magic forum if their is anything written about usbbrick ?

Ask in magic section, not in the one for desire.
Sent from dGB with Transparent XDA App

mullamadd said:
i allredy try that, but, there is no support for my phone HTC magic sapphire 32b.
It sucks, im stuck here..and ther's no way to move acros.
Click to expand...
Click to collapse
Magic ≠ Desire

Hello,
I have an HTC desire, root, s-off, oxygen rom installed.
When I switch on my phone stays in startup screen and does nothing.
Also I have problem accessing to recovery mode through fastboot.
When i choose recovery, the phone restarts and stays again to the startup screen.
-I have tried to access through the ADB (SDK manager) but in cmd cannot find my phone (adb devices)
-But if i write in cmd:
C:\>fastboot devices
everthing is ok it shows the serial number of my phone.
Then i wrote:
C:\>fastboot flash recovery recovery-clockwork-3.0.0.5-bravo.img
sending 'recovery' (3054 KB)...
OKAY [ 0.446s]
writting 'recovery'...
OKAY [ 0.912s]
finished. total time: 1.360s
After that i tried to access to recovery through the HBOOT and my phone restarted once again to the startup screen and did nothing.
Everytime i go to the recovery does the samething.
Does anyone knows what to do?
Thank you

dimitrisvel said:
Hello,
I have an HTC desire, root, s-off, oxygen rom installed.
When I switch on my phone stays in startup screen and does nothing.
Also I have problem accessing to recovery mode through fastboot.
When i choose recovery, the phone restarts and stays again to the startup screen.
-I have tried to access through the ADB (SDK manager) but in cmd cannot find my phone (adb devices)
-But if i write in cmd:
C:\>fastboot devices
everthing is ok it shows the serial number of my phone.
Then i wrote:
C:\>fastboot flash recovery recovery-clockwork-3.0.0.5-bravo.img
sending 'recovery' (3054 KB)...
OKAY [ 0.446s]
writting 'recovery'...
OKAY [ 0.912s]
finished. total time: 1.360s
After that i tried to access to recovery through the HBOOT and my phone restarted once again to the startup screen and did nothing.
Everytime i go to the recovery does the samething.
Does anyone knows what to do?
Thank you
Click to expand...
Click to collapse
try another recovery like RA Recover you can find it here:
http://forum.xda-developers.com/showthread.php?t=839621
I also got some problems with clockworkmod before, so i switched to RA and it works fine for me.

[TUT] Disaster Recovery - How to recover from nearly everything [Updated 28/04/2012]

Due to the lack of time, I cannot update this thread as frequently as I want to, so from now on, please refer to the HTC One X - XDA Developers Wiki
This guide is based on information found in leejames55 HBOOT loop thread and torxx tutorial, I just wanted to make thing clear, simple and consolidate all information in one place for non-dev users. So thanks to them and everyone who contributed.
After seeing alot of people having problem after flashing a rom, restoring RUU, re-locking bootloader, I've decided to make this guide in order to help everyone. If you follow this guide there's a good chance that you will manage to recover your phone
This is for people who have the following problem:
Cannot boot into ROM (e.g Stuck at the HTC Logo)
Boot Loop
Re-locked bootloader while having a non-working ROM
Cannot flash RUU because battery is below 30% - IMPORTANT: You must flash the new version of ClockWorkMod in order to be able to recharge the phone while off and from recovery
The most common problem is being stuck at the HTC Logo after flashing a ROM, try clearing the fastboot cache with these steps:
Power off your phone and hold the power button + volume down
Choose fastboot from bootloader
Connect the phone to your computer
On computer type:
Code:
fastboot erase cache
Choose "Reboot" in fastboot menu
If this doesn't work, try the rest of the guide
If you cannot flash RUU, go into recovery etc. because battery is below 30%
IMPORTANT: You must flash the new version of ClockWorkMod in order to be able to recharge the phone while off and from recovery. So, flash the new recovery and this problem will NOT happen.
ckpv5 said:
I don't think he can do that as more and more people have this problem as stated on OP:
Cannot flash RUU because battery is below 30%
But there is no explanation on how to to solve the problem. All the suggestions are good only when you have at least 20% battery.
So here I want to share on how I solve my problem to get the battery up to at least 20% so that you can fastboot flash anything, but to run RUU you need to have more than 30%. This works for me and hopefully it will work for others too.
Instead of plug in and plug out the usb cable to and from your phone when connected to PC (which actually not working for me), what I did was :
1) connect the phone to PC, your phone will boot into bootloader with red light flashing on and off or all the way red or no light at all.
2) use the vol button to scroll to power down and press power to off.
3) if the phone boot again to bootloader, repeat (2)
4) if the phone not booting, press the power button to on the phone, it will boot to bootloader again. Try the fastboot flash ** (whatever you want to do, either flash unlock.bin to unlock bootloader to flash CWM recovery or relock bootloader and flash stock recovery). If it fails due to low battery, repeat again (2) then (3) and (4). I did this less than ten times to have fastboot flash working.
What I notice is whenever we press power on, it will go to splash screen but unable to pass the bootanimation due to lack of battery, it will go back to bootloader. In the process, the battery get charging but stop when we are in bootloader. So restart again & again (power down in bootloader & power on again) will charge the battery until you have enough juice for fastboot flash.
Note: item (4), I did the fastboot flash ** before power on, it will say "waiting for device", once the phone is on and in fastboot mode, the command will runs. So once the battery reach about 20%, it will runs succesfully.
Click to expand...
Click to collapse
wolfraim said:
Well, i discover it because i brick my phone haha now i share it to you.
IF YOU HAVE ANY UNSIGNED RECOVERY:
1.- GO TO RECOVERY
2.- FORMAT SYSTEM
3.- RESTART NORMALLY
4.- YOUR PHONE WILL STOPS IN "HTC QUIETLY BRILLIANT" SCREEN
5.- PUT YOUR PHONE TO CHARGE (no light notification appears)
6.- LET IT CHARGE FOR A COUPLE HOURS (i put mine to charge for a complete night)
7.- Now restore your RUU, Flash, etc...
IF YOU HAVE SIGNED RECOVERY:
1.- GO TO FASTBOOT
2.- HIT "SHUT DOWN"
3.- WITH THE POWER OFF PUT IT TO CHARGE
4.- RED LIGHT NOTIFICATION SHOWS THE CHARGING PROGRESS.
5.- NEXT DAY YOU WILL SEE A SOLID GREEN LIGHT NOTIFICATIONS FOR A COMPLETE CHARGE.
PD: Sorry for ortography, im from Chile, my native speaking is spanish but i want to share my knowledge with XDA COMMUNITY !
Click to expand...
Click to collapse
If you re-locked the bootloader
Unlock with the same Unlock_code.bin file provided by HTC and follow this link: http://www.htcdev.com/bootloader/unlock-instructions/page-4/
If you have stock recovery
Download a Custom Recovery (e.g http://forum.xda-developers.com/showthread.php?t=1594819)
Then flash it with the command:
Code:
fastboot flash recovery recovery-clockwork-touch-5.8.2.7-endeavoru.img
If you have Custom ROM on or nandroid backup internal SD card
Reboot in recovery (If your still in fastboot, choose "Reboot Bootloader" and then go into recovery)
Restore a Nandroid Backup or flash Custom ROM
Reboot and go into fastboot
Clean cache in fastboot
If you DON'T have custom rom or Nandroid backup on internal SD card
torxx said:
So here a method which always works (many people have issues with flashing RUU's etc. having a bootlop.)
Download a RUU from here, thanks to Football!
Now open the .exe and make sure that it fully started.
Don't click anything, just go to windows icon and search for %temp%.
You will now find some folders, just search through these folders for the ROM.zip.
If you found it, you can copy it to your desktop or somewhere else.
Extract it with WinRar,7-zip or something like that and take the boot_signed.img and system.img.
Now copy the two files into the folder where the fastboot.exe is placed (if you have installed the Android SDK, it should be in platform-tools)
Plug in your One X, go into the bootloader and go into fastboot mode.
Navigate with the cmd in the folder with the fasboot.exe and the two .img's.
Now type in that:
Code:
fastboot flash boot boot_signed.img
After that:
Code:
fastboot flash system system.img
If everything worked, just reboot:
Code:
adb reboot
Click to expand...
Click to collapse
If you want to restore to original HTC ROM or have new HBOOT/Radio, you will have to do the step above and then the following:
Flash a ROM and boot image based on 1.26 (e.g ARHD 2.1)
Clear fastboot cache
Code:
fastboot clear cache
Boot your phone
Charge you phone completely
Download stock recovery
Flash stock recovery
Code:
fastboot flash recovery endeavoru_recovery_signed.img
Relock bootloader
Code:
fastboot oem lock
Run 1.26 RUU
Useful Links
HTC One X - IRC - This is the best way for you to get answer to you questions and help if you have problems
HTC One X - XDA Q&A
Don't hesitate to contibute to this guide, as this is made to anwser alot of questions and resolve most common problem when flashing custom roms.
We are all here to learn, take from community and give back to community!

thanks man, great thread

+1
Nice u will be helping a lot of people with this....

Any tut for no boot no recovery formatted sdcard ?
Sent from my HTC One X using XDA Premium HD app

I have a problem that I cant find a way to recharge my phone...

neo-kamui said:
I have a problem that I cant find a way to recharge my phone...
Click to expand...
Click to collapse
More information is needed, like which Recovery..
Anyway, good thread!

Help..
C:\Android>fastboot flash boot boot_signed.img
sending 'boot' (4278 KB)... OKAY [ 0.562s]
writing 'boot'... INFOFormat partition LNX done
OKAY [ 0.468s]
finished. total time: 1.030s
C:\Android>fastboot flash system system.img
sending 'system' (960424 KB)... FAILED (remote: (00000006))
finished. total time: 0.016s
C:\Android>
Any Help would by nice.
My cid "None"
I have no backups on phone
No files on phone.
ruu will not run error
Iv been all over the forums and tried many ruu`s
I think i have a brick
more info.. Was t-mobile branded but i flashed custom rom, then tried to update (epic fail) i the went back into recovery and was no files on phone sd.
i have tried with locked bootloader and unlocked bootloader with stock recovery and CWM recovery, i think iv tried all..
i`v just found a ruu_endeavor for t_mobile uk 1.26.110.2 i will give that ago when it downloads in about 1hr haha

This is really an excellent guide for everyone! THX from munich

Any Help would by nice.
My cid "None"
I have no backups on phone
No files on phone.
ruu will not run error
Iv been all over the forums and tried many ruu`s
I think i have a brick
Click to expand...
Click to collapse
SAME

Read my part..

I have a brick in 1.28
Have the newest CWM installed.
I only can go in the HBOOT or Recovery menu.
My device is S-off
Edit: sry i meant S-on

Raz0rX said:
I have a brick in 1.28
Have the newest CWM installed.
I only can go in the HBOOT or Recovery menu.
My device is S-off
Click to expand...
Click to collapse
S-off???
If not, what u need to do is flash stock recovery and lock ur device. Then place it on the charger while its off (Fastboot > Power Off). Let it charge (higher than 30%) and download and run RUU for your device.

S-OFF, really?
BTW, your device is not bricked, if you can enter the bootloader..

Raz0rX said:
I have a brick in 1.28
Have the newest CWM installed.
I only can go in the HBOOT or Recovery menu.
My device is S-off
Click to expand...
Click to collapse
No problem lucky guy.
With s-off you can supercid your Phone and flash every RUU.
How do you get s-off?

OH **** ... my brain was shortly off...
I mean S-ON, sry
The problem is .. there is no RUU for 1.28
So i can do nothing, this system and boot.img trick dont work for me

itswick said:
C:\Android>fastboot flash boot boot_signed.img
sending 'boot' (4278 KB)... OKAY [ 0.562s]
writing 'boot'... INFOFormat partition LNX done
OKAY [ 0.468s]
finished. total time: 1.030s
C:\Android>fastboot flash system system.img
sending 'system' (960424 KB)... FAILED (remote: (00000006))
finished. total time: 0.016s
C:\Android>
Any Help would by nice.
My cid "None"
I have no backups on phone
No files on phone.
ruu will not run error
Iv been all over the forums and tried many ruu`s
I think i have a brick
more info.. Was t-mobile branded but i flashed custom rom, then tried to update (epic fail) i the went back into recovery and was no files on phone sd.
i have tried with locked bootloader and unlocked bootloader with stock recovery and CWM recovery, i think iv tried all..
i`v just found a ruu_endeavor for t_mobile uk 1.26.110.2 i will give that ago when it downloads in about 1hr haha
Click to expand...
Click to collapse
OMG i did it... My x1 is now up and running,,,
You need to find the right ruu for your device,
mine was t-mobile uk 1.26.110.5
i download RUU_ENDEAVOR_U_ICS_40_TMO_UK_1.26.110.2_Radio_1.1204.90.13_release_251224_signed
and all flashed first time. with stock recovery and relocked bootloader.
I hope this will HELP you with your 1X..

woha nice ... i have an unbrandet device
i will search the right RUU
i used RUU_ENDEAVOR_U_ICS_40_HTC_Europe_1.26.401.2_Radio_1.1204.90.13_r and this will not work
The only difference is that i've CWM installed.. do you think this is the prob ?

Raz0rX said:
woha nice ... i have an unbrandet device
i will search the right RUU
i used RUU_ENDEAVOR_U_ICS_40_HTC_Europe_1.26.401.2_Radio_1.1204.90.13_r and this will not work
The only difference is that i've CWM installed.. do you think this is the prob ?
Click to expand...
Click to collapse
Im not expert... but i had stock recovery and relocked bootloader and all work for me.

Raz0rX said:
woha nice ... i have an unbrandet device
i will search the right RUU
i used RUU_ENDEAVOR_U_ICS_40_HTC_Europe_1.26.401.2_Radio_1.1204.90.13_r and this will not work
The only difference is that i've CWM installed.. do you think this is the prob ?
Click to expand...
Click to collapse
Yes, make sure u put ur device as stock, stock recovery, and locked bootloader.

Also you have flashed the boot_signed.img and the system.img?
I load a new RUU i hope this will work with it
Edit: How do i become a stock recovery ?

[Q] stuck in hboot. keys not working

Hi everybody. I've read the great compilation of problems/solutions but have not find mine
My desire bravo is rooted and s-off. It's got CM7 and was working fine until it run out of battery. When powered on again, the hboot window appears (Even if only power is pressed) and VOL buttons doesn't move the cursor nor the trackpad... (they were working fine before)
I've tried to connect it to the PC, and that works. ADB devices seems to find the phone (it replies SH13NPL06262 fastboot). I've then tried to reflash different hboot, recovery... doesn't work (it says FAILED (status malformed (1 bytes))
Using android flasher, the program does not complain, but stays working on it forever...
This is the window with details about what's inside were I the phone stays until battery is unplugged.
Could you help me bring it back to life?
Cheers

Try downloading a recovery.img of 4ext and booting it. To do this boot the phone into fastboot using power + back, then run:
fastboot boot recovery.img
Then once in recovery you can flash a ROM.
Sent using xda-developers app

Thanks, but it didn't work. It says
downloading 'boot.img'...
FAILED (status malformed (1 bytes))
finished. total time 0.005s
When I start with "back"+"power" the screen looks the same as when using just "power" or "vol-" and "power"... it appears the image I show in the first post... Is that fastboot?
P.D. Just in case it helped: the command "fastboot reboot" is accepted but nothing happens in the screen. "fastboot reboot-bootloader" is rejected as the other (FAILED (status malformed)...)

zumix said:
Thanks, but it didn't work. It says
downloading 'boot.img'...
FAILED (status malformed (1 bytes))
finished. total time 0.005s
When I start with "back"+"power" the screen looks the same as when using just "power" or "vol-" and "power"... it appears the image I show in the first post... Is that fastboot?
Click to expand...
Click to collapse
Yes, it's fastboot.
With the phone plugged in fastboot, what is the output of "fastboot devices"?

abaaaabbbb63 said:
Yes, it's fastboot.
With the phone plugged in fastboot, what is the output of "fastboot devices"?
Click to expand...
Click to collapse
it replies "SH13NPL06262 fastboot"

zumix said:
it replies "SH13NPL06262 fastboot"
Click to expand...
Click to collapse
So its being recognized which is good, but this malformed error is the problem. Try "fastboot erase recovery", then "fastboot boot recovery.img" again.

Chromium_ said:
Try "fastboot erase recovery".
Click to expand...
Click to collapse
Again the FAILED (status malformed)... when trying to ERASE the recovery

zumix said:
Again the FAILED (status malformed)... when trying to ERASE the recovery
Click to expand...
Click to collapse
Try installing the 2.3 RUU via PB99IMG method. Download the ruu here and read instructions on how to install it here.

Chromium_ said:
Try installing the 2.3 RUU via PB99IMG method. Download the ruu here and read instructions on how to install it here.
Click to expand...
Click to collapse
Well, it has loaded the PB99IMG, and after that it appears
Parsing...[SD_ZIP]
[1] Radio_V2
[2] splash1
[3] Recovery
...
[9]boot
But now... should I be able to move between options? None of the buttons appear to do anything...
IS it safe to unplug battery now? (not sure what I've done now

zumix said:
Well, it has loaded the PB99IMG, and after that it appears
Parsing...[SD_ZIP]
[1] Radio_V2
[2] splash1
[3] Recovery
...
[9]boot
But now... should I be able to move between options? None of the buttons appear to do anything...
IS it safe to unplug battery now? (not sure what I've done now
Click to expand...
Click to collapse
You just installed the ruu. That brings the phone back to complete stock. If it says its completed then i would assume its safe to unplug. ONLY UNPLUG IF YOU ARE SURE ITS DONE. Then boot it back up and hope for the best :fingers-crossed:

zumix said:
Hi everybody. I've read the great compilation of problems/solutions but have not find mine
My desire bravo is rooted and s-off. It's got CM7 and was working fine until it run out of battery. When powered on again, the hboot window appears (Even if only power is pressed) and VOL buttons doesn't move the cursor nor the trackpad... (they were working fine before)
I've tried to connect it to the PC, and that works. ADB devices seems to find the phone (it replies SH13NPL06262 fastboot). I've then tried to reflash different hboot, recovery... doesn't work (it says FAILED (status malformed (1 bytes))
Using android flasher, the program does not complain, but stays working on it forever...
This is the window with details about what's inside were I the phone stays until battery is unplugged.
Could you help me bring it back to life?
Cheers
Click to expand...
Click to collapse
Have you tried taking the batter out, removing the SIM and SD cards, cleaning the contacts, and trying to boot it again? The symptoms are similar to what I've seen on my Desire, but doing that seemed to sort it out (at least, for a bit) but I didn't mess around with the HBOOT or anything.

ever ruldsv
Chromium_ said:
You just installed the ruu. That brings the phone back to complete stock. If it says its completed then i would assume its safe to unplug. ONLY UNPLUG IF YOU ARE SURE ITS DONE. Then boot it back up and hope for the best :fingers-crossed:
Click to expand...
Click to collapse
Well during installation there was a progress bar un the top right side... when finished the "menu" I said appeared... or is it a list of the things has done? I assume It has finished becaused it has been like that many minutes by now...

zumix said:
Well during installation there was a progress bar un the top right side... when finished the "menu" I said appeared... or is it a list of the things has done? I assume It has finished becaused it has been like that many minutes by now...
Click to expand...
Click to collapse
Oh wait. I just realized you probably didnt even install it yet. It just parsed the zip and displayed all of the parts that it contains.
Below it should say "Do you want to start update?". You need to press volume up for "yes".

Chromium_ said:
Oh wait. I just realized you probably didnt even install it yet. It just parsed the zip and displayed all of the parts that it contains.
Below it should say "Do you want to start update?". You need to press volume up for "yes".
Click to expand...
Click to collapse
I have not seen that... this is what I get...
I have not been asked anything. Before that it looked for a couple of files that couldn't find (pb99diag.zip and pb99diag.nbh) then it found the PB99IMG.zip and started "reading" or installing...
I have disconnected and restarted and all the process starts again... Do I need those PB99DIAG files?

zumix said:
I have not seen that... this is what I get...
I have not been asked anything. Before that it looked for a couple of files that couldn't find (pb99diag.zip and pb99diag.nbh) then it found the PB99IMG.zip and started "reading" or installing...
I have disconnected and restarted and all the process starts again... Do I need those PB99DIAG files?
Click to expand...
Click to collapse
No you don't need any other files. Its supposed to work with just the pb99img. It seems to be stuck though, since like I said before you usually get a prompt asking if you want to install.
My next suggestion would be to use the ruu from your PC. You can get it here: http://www.htcdev.com/process/legal_download/152
Sent using xda-developers app

Chromium_ said:
No you don't need any other files. Its supposed to work with just the pb99img. It seems to be stuck though, since like I said before you usually get a prompt asking if you want to install.
My next suggestion would be to use the ruu from your PC. You can get it here: http://www.htcdev.com/process/legal_download/152
Sent using xda-developers app
Click to expand...
Click to collapse
Well, I have removed the SD, (or the pb99img file started to install again ) and tried to install RUU from PC, but always complains about Low battery. I've had it many hours charging, and battery was behaving fine up to now... very strange isn't it?
I'll keep it charging a few more hours, but I'm afraid it is not that

zumix said:
Well, I have removed the SD, (or the pb99img file started to install again ) and tried to install RUU from PC, but always complains about Low battery. I've had it many hours charging, and battery was behaving fine up to now... very strange isn't it?
I'll keep it charging a few more hours, but I'm afraid it is not that
Click to expand...
Click to collapse
Well, I have removed the Pb99img file from SD card to do the procedure with the SD inserted... After a whole day charging, the PC programs still complains about battery being too low.
If any of you know any other thing to try, I 'll be happy, but I understand this is too weird and the phone might be internally damaged for some reason.
I thank you all for so many messages helping me with it. :good:

[Q] Nexus 7 stuck in Fastboot

I was loading up my Nexus 7 (2013) with the Project L rom and ran into a problem. At the end of the install, I got an error that it could not erase the cache. I can boot into Bootloader but nothing else. It won't boot into recovery or launch the system OS. When I try to launch the system OS, I just get that updating animation that sits there for hours. Fastboot does recognize the device though, but when I try to do a fastboot erase of a partition, it just hangs. Anyone know how I can get out of this?

Try a complete reflash of 4.4.4 or 5 from fastboot.
Sent from my Nexus 7 using Tapatalk

ritchea said:
Try a complete reflash of 4.4.4 or 5 from fastboot.
Sent from my Nexus 7 using Tapatalk
Click to expand...
Click to collapse
I tried the process again. Whether I am trying to erase a partition, re-format a partition, or flash a partition, I get write errors. It is almost as if the rom is write-protected or something. It will copy partition images to whatever partition the bootloader is using, but just won't write them to the proper partitions.

So you are saying when you give the command [fastboot flash system system.img], you get a write error. I'm obviously not an expert, but i thought a new flash would do a complete wipe and create new partitions. If that is not the case (meaning flashing requires that partitions be in place), then you need someone who can tell you if/how to code for partitions or send it in for repair.
Is adb working? If so, you might want to try Wug's toolkit. (see android development).
When you try to start recovery from fastboot, do you get Andy with the red triangle, or what?
Sent from my Nexus 7 using Tapatalk

Check if your Android SDK is up to date

ritchea said:
So you are saying when you give the command [fastboot flash system system.img], you get a write error. I'm obviously not an expert, but i thought a new flash would do a complete wipe and create new partitions. If that is not the case (meaning flashing requires that partitions be in place), then you need someone who can tell you if/how to code for partitions or send it in for repair.
Is adb working? If so, you might want to try Wug's toolkit. (see android development).
When you try to start recovery from fastboot, do you get Andy with the red triangle, or what?
Sent from my Nexus 7 using Tapatalk
Click to expand...
Click to collapse
ADB doesn't find the device any longer, although it did when I started the process. So I am left with using Fastboot. When I try to go into recovery, the screen goes black, then I get the Google logo, and it just sits there. When I try to launch into the system, I get they Andy lying down with the rotating geometric shape in his belly - forever. All that seems to work is the bootloader, and it's not really working. This is the kind of results that I am getting.
Code:
C:\Users\Daniel\Downloads\Nexus 7>fastboot devices
07b8be03 fastboot
C:\Users\Daniel\Downloads\Nexus 7>fastboot flash recovery openrecovery-twrp-2.8.
0.1-flo.img
sending 'recovery' (7878 KB)...
OKAY [ 0.254s]
writing 'recovery'...
FAILED (remote: flash write failure)
finished. total time: 90.015s
C:\Users\Daniel\Downloads\Nexus 7>fastboot flash bootloader bootloader-flo-flo-0
4.04.img
sending 'bootloader' (3911 KB)...
OKAY [ 0.130s]
writing 'bootloader'...
FAILED (remote: flash write failure)
finished. total time: 1.067s
C:\Users\Daniel\Downloads\Nexus 7>

What happens when you do [fastboot reboot recovery]? I wish I understood more about this. First, lying down Andy with the red triangle is the recovery "pre" screen for stock recovery. The fact that system reboots to it may indicate you have no OS. Once you get to that screen, have you tried to get to the next screen (holding vol+/- and power at the same time for a few seconds)? It's tricky and directions say vol+ plus power, but it seems I've always had to press vol in middle. I've read it both ways. Try this first.
[When Stock Recovery starts you will see the Android fallen down screen
To bring up the Recovery menu
Power+VolUp to show recovery menu
Must be this sequence Press/Hold Power, THEN Press/Release VolUp, release Power]
Although I've found many instances of the write write failure you describe, no definitive answers. It does seem that Wug's Toolkit is worth a try. I read the following on his site. I realize it's about unlocking, but the point is you don't need adb to run commands from fastboot.
"WugFresh Mod Carey Parks • 4 days ago
You don't need to be connected via ADB (on with usb-debug enabled) to unlock. You just be connected via FASTBOOT (bootloader mode). Just use the "Unlock" button, and follow the instructions it gives you to MANUALLY boot your device into bootloader mode, then proceed from there. Its fine that your device is messed up.. you just have to get the bootloader unlocked. Once its unlocked you can use "Flash Stock + Unroot" with softbrick/bootloop mode to get your device back to normal. Cheers!"
Using the toolkit from fastboot without adb might help. (In fact, I didn't know this.) He further brought up these commands: You could also try to issue the commands (NRT advanced utilities > launch cmd prompt):
fastboot format system
fastboot format data
fastboot format cache
Of course this clears everything. But from this point, you could try the "Flash Stock+Unroot" step on the first page of the toolkit.
Have you tried to flash a totally different set of files (like the official 4.4.4 decompressed and placed into the fastboot folder)?
It is possible that your SD card has become corrupted. I'm pretty sure you can't issue any mount commands without adb so you can't set the card to write.
For the 15-20 minutes it will take to set up the toolkit and use it (it has to download files for your device, too). it may be worth the effort. Also, Wug is very good about helping. If you can provide him with a copy of what's happening (while using the toolkit), he will try to help. He really understands this stuff. If you're a "toolkit snob" (my term for those who deny usefulness of toolkits), then ignore that suggestion. You already understand how to use fastboot (which is why some say don't use toolkits). My personal experience is that the kit has helped me get out of bootloops a few times.

ritchea said:
What happens when you do [fastboot reboot recovery]? I wish I understood more about this. First, lying down Andy with the red triangle is the recovery "pre" screen for stock recovery. The fact that system reboots to it may indicate you have no OS. Once you get to that screen, have you tried to get to the next screen (holding vol+/- and power at the same time for a few seconds)? It's tricky and directions say vol+ plus power, but it seems I've always had to press vol in middle. I've read it both ways. Try this first.
[When Stock Recovery starts you will see the Android fallen down screen.
Click to expand...
Click to collapse
The Android logo I get when trying to boot into the OS is the animated one with the spinning wire-mesh ball thingy that one generally sees when the OS is updating itself. It just doesn't stop. I'll give the toolkit thing a try, but am about to head out for the day. Won't have a chance until later tonight or tomorrow.

djeaton said:
The Android logo I get when trying to boot into the OS is the animated one with the spinning wire-mesh ball thingy that one generally sees when the OS is updating itself. It just doesn't stop. I'll give the toolkit thing a try, but am about to head out for the day. Won't have a chance until later tonight or tomorrow.
Click to expand...
Click to collapse
Oh, I understand on the Andy. OK. Have a great day.
Kinda weird-- http://forum.xda-developers.com/showthread.php?t=2917463different circumstances but same problem. No one responding there, either.
I don't know why this would work when wug's does not, but some claim it did http://forum.xda-developers.com/showthread.php?t=2381582. You would download, extract, click Dead_Nexus7.bat file and run from fastboot.