Develop Bugs

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] Completely wiped my One X, cannot mount usb, no backups, need backups

Hello everybody,
This is my first post on XDA, although I've visited the site oftne
Anyways:
Yesterday I successfully rooted my One X and unlocked its bootloader. I also installed CWM recovery.
As the day came to a close I tried to install LC_MOD in an attempt to change the multitasking softkey to a menu button.
I did not make a backup, and the phone had no backups.
Needless to say the phone wouldnt boot. I panicked and in blind fear sortof erased everything off of my phone. everything. What I basically did was i went into advanced settings and formatted my /sdcard and all those other folders, hoping that would solve the issue (a simple data/cache wipe didnt work). So much data has been erased from the phone that I cannot even mount usb storage through CWM because im missing a file.
So, I come to you all, you gods of the tech world, with my head bowed, to ask for your help. I have literally tried everything in my power to fix the issue. I tried to install custom roms manually, that didnt work. I tried to install an RUU, and even that didnt work (the software could not detect my device). This was all made even more difficult because I myself have a mac, and much of the software I had to use was windows based, which led me on a journey to create a virtual machine.
I know i messed up, and what I'm really hoping someone out there cn do is upload one of their own backups of their One X's software, and show me how to use that to restore my phone.
Somebody out there please please help me :'(

Hi;
There is a reason all developers here shout out loud:
1- BACKUP YOUR PHONE BEFORE YOU F*** IT UP
2- DO NOT DO ANYTHING UNLESS YOU ABSOLUTELY KNOW HOW TO
But anyways, you ruined it, you should get it back, Hopefully you did not drain the battery below 30%, in that case keep on reading the next paragraph, but if you dropped the battery below 30, you should go to CWM Recovery, connect your phone to charger, and wait until it's charged properly...
After charging the phone, you need the correct RUU for your phone... As it seems, you don't know what you're doing, so go to fastboot, type this command:
Code:
fastboot oem readcid
Then post the code here in this topic, so someone can help you find the correct RUU for your phone...
After that go to THIS topic and follow the part where it says "If you DON'T have custom rom or Nandroid backup on internal SD card"

Thanks
Thanks a bunch bro!! And ye i get that it was completely my fault. I normally do backup before i do anything, but i guess i was just a bit too anxious. And I think you've told me everything i need to know, ill get that code out to you asap... And you're right, i seriously have no clue what im doing ^.^, I've never F***ed up this hard on any phone before

Xial649 said:
Thanks a bunch bro!! And ye i get that it was completely my fault. I normally do backup before i do anything, but i guess i was just a bit too anxious. And I think you've told me everything i need to know, ill get that code out to you asap... And you're right, i seriously have no clue what im doing ^.^, I've never F***ed up this hard on any phone before
Click to expand...
Click to collapse
Don't worry, with the correct version of RUU you can restore your phone...
Sent from my HTC One X using XDA

Next?
Alright I got the code:
<bootloader> DEBUG: cid: VODAP102
Whats next?

Xial649 said:
Alright I got the code:
<bootloader> DEBUG: cid: VODAP102
Whats next?
Click to expand...
Click to collapse
Your phone is from Voda Germany, and most probabely your correct RUU is this:
Code:
http://www.filefactory.com/file/t7qugfd3ey9/n/RUU_ENDEAVOR_U_ICS_40_Vodafone_CH-DE_1.26.166.2_Radio_1.1204.90.13_release_251279_signed.exe
Download it. Hopefully it would be the correct RUU for your phone.
1- Now open the exe file you just downloaded and make sure that it fully started.
2- Don't click anything, just open "Computer" (formerly known as my computer) in windows and enter %temp% in your address bar.
3- You will now see some folders, just search through these folders for the ROM.zip (using windows search function)
4- When you found it, copy it to your desktop.
5- Extract it with WinRar,7-zip or something like that and take the boot_signed.img and system.img.
6- 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)
7- Go to your One X, go into the bootloader and go into fastboot mode. then connect your phone to computer.
8- Open CMD and navigate to the folder in which you have the two images and the fastboot file. (using cd command and after that the address you want to go to)
9- Now type in that
Code:
fastboot flash boot boot_signed.img
10- Now this one
Code:
fastboot flash system system.img
if all this is successful, you can just reboot your phone and everything is OK.
If you can't do any of these, let us now, we will help you through it...
Good lock
---------- Post added at 03:52 PM ---------- Previous post was at 03:41 PM ----------
In other note, RUUs are build to do an stand alone recovery of your phone. So you can first try, just running the RUU application and following the instruction given in the RUU. it may work correctly

This is good
Alright so i got everything going after downloading the RUU and it was in the process of restoring my phone, but then it said my battery went below 30% so i needed to recharge. At that point i had to leave, and so I noticed that if i left my phone in the booting animation (HTC logo) the LED light indicated that the phone was charging. Since I wasnt entirely convinced that my CWM recovery was actually charging the phone, i left it on booting while connected to my pc and hopefully itll be fully charged and ready to be restored tomorrow..... I really appreciate all the help you've given me man you've practically saved my life here , and I'd like to say that you've made my first cry for help a simple and smooth one.... Thank you very much my friend :victory: :highfive:

Problem
Ok so we have a new problem, the system.img file didnt flash. I tried and it said "FAILED"
What now??
& is the boot image supposed to only be around 4300 kb?
Could the sending of "system" failed because my phone had less than 30% batterylife???? & if its in Clockworkmod recovery5.8.4 while connected to an outlet will it be charging???
Edit: I've searched around and I saw this one guy who extracted the "boot_signed.img" and the "recovery_signed.img" (NOT the system.img), flashed them onto his phone, locked the bootloader with "fastboot oem lock", and then RAN the RUU..... He said he bricked his phone, and the situation he described is similar to mine. Any thoughts on which method of the two (yours and his) i should use?
Thanks again :3

Xial649 said:
Ok so we have a new problem, the system.img file didnt flash. I tried and it said "FAILED"
What now??
& is the boot image supposed to only be around 4300 kb?
Could the sending of "system" failed because my phone had less than 30% batterylife???? & if its in Clockworkmod recovery5.8.4 while connected to an outlet will it be charging???
Edit: I've searched around and I saw this one guy who extracted the "boot_signed.img" and the "recovery_signed.img" (NOT the system.img), flashed them onto his phone, locked the bootloader with "fastboot oem lock", and then RAN the RUU..... He said he bricked his phone, and the situation he described is similar to mine. Any thoughts on which method of the two (yours and his) i should use?
Thanks again :3
Click to expand...
Click to collapse
That's another method you can try, boot_signed is the stock kernel (and yes it's that small) and the recovery_signed is the stock recovery...
Since my previously mentioned method didn't work, do this:
1- flash the boot_signed.img into your device (fastboot flash boot boot_signed.img)
2- flash the recovery_signed.img in the device (fastboot flash recovery recovery_signed.img)
3- erase cache (fastboot erase cache)
4- lock your phone (fastboot oem lock)
5- now try again to flash the system image (fastboot flash system system.img)
And also, try having around 40% battery to do all this, don't let the battery drops under 30%

ALRIGHT!!!!
alright man!!!! that sounds like a plan... First thing tomorrow I'm going to try this method out.... and btw the RUU you linked me wasnt exactly working right (the software kept saying i had the wrong ruu), so i searched around and found someone with the same CID (VODAP102) and apperantly the uk RUU works fine on it, so i guess ill use that one ye? And btw does the bootloader have to be unlocked before i can flash these items? because i do believe its locked atm....

Xial649 said:
alright man!!!! that sounds like a plan... First thing tomorrow I'm going to try this method out.... and btw the RUU you linked me wasnt exactly working right (the software kept saying i had the wrong ruu), so i searched around and found someone with the same CID (VODAP102) and apperantly the uk RUU works fine on it, so i guess ill use that one ye? And btw does the bootloader have to be unlocked before i can flash these items? because i do believe its locked atm....
Click to expand...
Click to collapse
Your phone is "Vodafone Germany" version and the link I gave you is the "Voda DE" which seems right, but you can try that as well, doesn't heart...
No, for original ROM (RUU) you should have a locked boot-loader, unlocking is just for custom ROMs.

ok
ok so this is what ill do tomorrow:
1) make sure bootloader is unlocked
2) fastboot flash boot boot_service.img
3) fastboot flash recovery recovery_service.img
4) fastboot oem lock
5) fastboot flash system system.img
did i get everything?

Xial649 said:
ok so this is what ill do tomorrow:
1) make sure bootloader is unlocked
2) fastboot flash boot boot_service.img
3) fastboot flash recovery recovery_service.img
4) fastboot oem lock
5) fastboot flash system system.img
did i get everything?
Click to expand...
Click to collapse
The two first commands should work on a LOCKED boot-loader, so I think step 1 would not be necessary... If your phone is locked you should be able to do all steps 2, 3, 5 without problem (step 1 and 4 are the exact opposite of each other and if the phone is locked already I think can be skipped)

ok so its still not working.... I managed to flasht he boot_signed.img and the recovery_signed.img, clear cache and lock the bootloader after it, but i still cannot seem to flash the damn system.img... Any thoughts?
what happens is command prompt stays static for a second and then says sending 'system' (1000596 KB)
FAILED (remore: (00000006))
finished. total time: -0.000s
so? What now??

Xial649 said:
ok so its still not working.... I managed to flasht he boot_signed.img and the recovery_signed.img, clear cache and lock the bootloader after it, but i still cannot seem to flash the damn system.img... Any thoughts?
what happens is command prompt stays static for a second and then says sending 'system' (1000596 KB)
FAILED (remore: (00000006))
finished. total time: -0.000s
so? What now??
Click to expand...
Click to collapse
Any luck in running the RUU itself directly?

i gave up
alright so nothig worked. Not the manual flash, and not the RUU itself. So ive resolved to visit my local help center for HTC devices, and see what they can do, if they cant fix it the least they can do is send it to the german branch for repairs. Thanks for all your help mate, you've really proven to be a great guide, but I guess something just isnt clicking in this case :/.......... i love u man

I'm not sure if this would work.
If you are still htcdev unlocked:
1. Enter bootloader in fastboot usb
2. Fasboot flash recovery -your recovery .img here"
3. Boot into recovery
4. Go to "mounts and storage"
5. Mount SD(I think this is right) and your sd should show up in your pc
6. Copy your rom zips and other zips you need/want
7. Unmount SD
8. By this time you should be able to flash your rom
9. Make sure you flash boot.img again in bootloader.
Hope this helps
Sent from my HTC One X using xda app-developers app

Isn't it mount usb storage?
Sent from my HTC One X using XDA Premium App

You couldn't mount the USB storage / sdcard because you were running CWM from the bootloader. If you connect it to the pc you can put the recovery file you flashed into the fastboot folder and do:
fastboot boot *recoveryfilename*.img
Then you can mount the sdcard etc.
If you have photos and things you don't want an ruu to get ride of, you can fix the ROM. You broke it by trying to install an deodrexed mod for an odexed Rom. If you're interested I can tell you how to fix it.

You could also take this opportunity to install a custom Rom, with which I can also help.

[Q] Recovery wont work

Hey guys , am having a problem with my htc one x recovery ,
as i was going with the rooting of my phone i got stack at 1 point where i needed to use recovery so i could access the zipped file in my htc (i have already unlocked the bootloader). So when am getting to the point of using recovery from the fastboot screen with the color letters (using volume up and the power button to navigate as always) the htc message pops up trying to load the recovery and then a black screen pops up with the icon of the mobile and a green cyrcle, and after a few secs of loading theres another icon with a red triangle and a exclamation mark. at that point the phone stacks with that icon and i can do nothing. after a couple of mins the phone just restarts by itself and am back on the normal htc interface...
In the video i saw after he used recovery none of those icons where seen and it loaded up the default directories of the phone, as i was searching in net i saw a prob like that and the solution was to erase the fastboot erase cache, already erased the cahe but the problem is still there, if any solutions for that would be greatly apreciated !

Did u flash a custom recovery ? Latest is cwm 5.8.4.0
The one u are describing is the stock one.
Verstuurd van mijn HTC One X

The recovery you described is HTC's stock recovery ... Go to here - > http://forum.xda-developers.com/showthread.php?t=1594819 < - and download the first link and put it into your phone sdcard then reboot into fastboot and fastboot flash recovery <recovery name>.img and you're good to go for flashing ROMs

chaun1308 said:
The recovery you described is HTC's stock recovery ... Go to here - > http://forum.xda-developers.com/showthread.php?t=1594819 < - and download the first link and put it into your phone sdcard then reboot into fastboot and fastboot flash recovery .img and you're good to go for flashing ROMs
Click to expand...
Click to collapse
Wrong mate....
Download the cwm recovery and put in the fastboot folder on PC.
And also give this command before AND after flashing the recovery.
Fastboot erase cache
And why giving the answer again, i already gave the answer, and get your facts right ! This is the second post i see around with a small error in it
Sent from my ..........

MarcelHofs said:
Wrong mate....
Download the cwm recovery and put in the fastboot folder on PC.
And also give this command before AND after flashing the recovery.
Fastboot erase cache
And why giving the answer again, i already gave the answer, and get your facts right ! This is the second post i see around with a small error in it
Sent from my ..........
Click to expand...
Click to collapse
no need to put the recovery.img in the fastboot folder:
Code:
fastboot flash recovery path/to/recovery.img

Very true .... but to keep it more clear (just like putting the boot.img in the fastboot folder,.like most tut's say) i advice to do it straight from the fastboot folder, so in that way the commands stay the same.......if you get my point
Verstuurd van mijn HTC One X

tyvm guys really helped , the guy in the video i was watching forgot that step ... well either way flashed the recovery and after following the next steps i rooted + tried to load the new maximus v6. and huston we have a problem . when i rebooted after the instalation of the custom rom my phone stack in the white first loading screen of the phone (htc quitely brilliant) any suggestions in that?

Solidarious said:
tyvm guys really helped , the guy in the video i was watching forgot that step ... well either way flashed the recovery and after following the next steps i rooted + tried to load the new maximus v6. and huston we have a problem . when i rebooted after the instalation of the custom rom my phone stack in the white first loading screen of the phone (htc quitely brilliant) any suggestions in that?
Click to expand...
Click to collapse
Have you flashed boot.img?

I think it's better to read more rather then watching half baken video's (what you did not know) it's better to follow the tutorials here ! :thumbup:
And yes like said before flash the boot.img
Extract it from the rom.zip and place it in fastboot folder
Phone in fastboot USB mode and do the following command
Fastboot flash boot boot.img
Fastboot erase cache
Just like you did with the recovery
Reboot !
Verstuurd van mijn HTC One X

ok.. so i just searched a bit in this forum and the tutorials here as u said , and y after i saw in here am not going to trust any videos and just follow the forum.. i missed a couple of steps first i dont know what CID i have , which as i've seen its very important ( any ways to check now that i cant use my htc and am stack in bootloader?) 2nd i ve seen i need to have the hboot 1.31 for it to work and currently i don't. thought that maybe that would fix it and downloaded it and as the steps told me
1.i relocked the bootloader
2.downloaded the firmware.zip from the forum instructions
3.entered succesfully the command "fastboot oem rebootRUU"
4. { (4) In order to flash new hboot write "fastboot flash zip firmware.zip" } and here am stuck cause when am typing the command am getting FAILED <remote : not allowed) and in that step i saw a vid again (i know...but am desperate) which he said if that happens u should use the
adb reboot oem-78. which i did and after it opens deamon it says error : device not found

and also u said:
And yes like said before flash the boot.img
Extract it from the rom.zip and place it in fastboot folder
i know i might be asking for much but plz put some more detail form me as am somewhat new to this and i might not understand some of the ways
for example which one is the boot img? the hboot 1.31 ? and what do u mean extract from rom.zip ( the custom rom maximus v6 i downloaded u mean?) and i really apreciate ur time guys ur helping me much hope i can still use my phone after ur instructions atm i crying over a my dead phone help me bring it back ( if its possible ;/)

boot.img is insite the custom rom zip file open the zip file with totalcommander take out the boot.img an fastboot it

so u mean the boot.img inside the zipped folder from the instuctions named firmware ? the one that has the hboot 1.31? cause if thats the case i tried and i unzipped it put it on the fastboot folder and tried to run the commands like this
fastboot flash boot boot.img
what i got is
sending 'boot' <5260 KB>....
OKAY [ 0.6s ]
writing ' boot'....
FAILED < remote : not allowed>
finished . total time : 0.9s
so that got me curious and i typed adb devices to check on cmd ... but my phone is not listed there o-o
while i was doing this the phone is on fastboot menu with the cable attached and says FASTBOOT USB.
any ideas? also how could i manage to come so far if the phone couldnt be reached in the first place (something changed meanwhile?) any ideas?

Solidarious said:
sending 'boot' <5260 KB>....
OKAY [ 0.6s ]
writing ' boot'....
FAILED < remote : not allowed>
finished . total time : 0.9s
Click to expand...
Click to collapse
that's because you bootloader is locked
EDIT: also install the htc drivers

matt95 said:
that's because you bootloader is locked
EDIT: also install the htc drivers
Click to expand...
Click to collapse
well i relocked the bootloader cause the instructions said i had2 , also the htc drivers are installed and the device in device manager on my pc is running smoothly. So i have to reunlock in order to boot the boot.img? if so how can i reunlock it :? can u type me the exact commands? thought it was fastboot oem unlock but there seems to be an error !

Solidarious said:
well i relocked the bootloader cause the instructions said i had2 , also the htc drivers are installed and the device in device manager on my pc is running smoothly. So i have to reunlock in order to boot the boot.img? if so how can i reunlock it :? can u type me the exact commands? thought it was fastboot oem unlock but there seems to be an error !
Click to expand...
Click to collapse
you have to unlock it in order to upgrade th firmware but when the firmware is flashed you have to unlock it again, because with the bootloader locked you can't use fastboot to flash anything....

matt95 said:
you have to unlock it in order to upgrade th firmware but when the firmware is flashed you have to unlock it again, because with the bootloader locked you can't use fastboot to flash anything....
Click to expand...
Click to collapse
ok i get it i have to reunlock the bootloader but how? ... the last step i remember from the first time i did was till i got in my email the unlock.bin after that? isnt it the fastboot oem unlock? idk ;/ help
and btw i found a way to check my cid fastboot oem readcid lolz was typing random xD. E11 is my cid so 1 less thing to worry about as its supported

Solidarious said:
ok i get it i have to reunlock the bootloader but how? ... the last step i remember from the first time i did was till i got in my email the unlock.bin after that? isnt it the fastboot oem unlock? idk ;/ help
and btw i found a way to check my cid fastboot oem readcid lolz was typing random xD. E11 is my cid so 1 less thing to worry about as its supported
Click to expand...
Click to collapse
unlock the phone via HTCdev.com...

matt95 said:
unlock the phone via HTCdev.com...
Click to expand...
Click to collapse
well actually didnt need to do anything via htcdev but i did the same steps and found the command i needed
which was:
fastboot flash unlocktoken Unlock_code.bin but ty though gave me the idea
just did booted the boot.img and i ll let u guys know what happend next ! great help from all of u
thanks to all

Solidarious said:
well actually didnt need to do anything via htcdev but i did the same steps and found the command i needed
which was:
fastboot flash unlocktoken Unlock_code.bin but ty though gave me the idea
just did booted the boot.img and i ll let u guys know what happend next ! great help from all of u
thanks to all
Click to expand...
Click to collapse
glad to help

Can't find any rom working with my htc

Hello
I have htc one x with the following information:
cid HTC__Y13
s-on
hboot-0.95.0000
imei unknown
But if i connect the phone to the computer with fastboot i can get the imei from cmd
My own rom is almost wrecked every time i start the phone it restarts .. i have tried a dozen of roms non have worked
Please please please
Any one can help me

To begin with your HBOOT is an old version. Upgrade it and then flash the ROM you want or find the right RUU to flash
You will need HBOOT 1.39 at least. See this link
http://d-h.st/users/ClydeB1/?fld_id=8110

grwalker said:
To begin with your HBOOT is an old version. Upgrade it and then flash the ROM you want or find the right RUU to flash
You will need HBOOT 1.39 at least. See this link
First of all i want to thank you very very much for your replay
So i tried what you said and i successfully updated the hboot to 1.39
then did a bootloader reboot but when the phone restarts it stucks on (white htc one screen) can't load to the standard screen.. i pressed the power button for 5 sec and the phone restarted .. pressed the vol down and entered the boot loader .. at boot loader if i tried to access the recovery or factory reset the phone simply display a black screen and downloading bar lookalike for 5 sec then restarts
I tried to flash a rom via cmd but i got the following error:
FAILED (remote: Heap not enough)
Ps: i can't try the ruu ENDEAVOR cuz the phone can't access the standard screen
Click to expand...
Click to collapse

After flashing a new HBOOT your bootloader is now locked. It needs to be unlocked
take a look at this link and it will help you unlock your bootloader. Then you can flash a costume recovery and then flash your ROM
http://onexroot.com/one-x-root/how-to-root-one-x/
You need to do a bit of reading about all the steps needed for getting the ROM you want. Jumping in to quick could cause problems. Luckily you have S_ON so that will help prevent making big mistakes

grwalker said:
After flashing a new HBOOT your bootloader is now locked. It needs to be unlocked
take a look at this link and it will help you unlock your bootloader. Then you can flash a costume recovery and then flash your ROM
You need to do a bit of reading about all the steps needed for getting the ROM you want. Jumping in to quick could cause problems. Luckily you have S_ON so that will help prevent making big mistakes
Click to expand...
Click to collapse
Thank you again i really appreciate your help
So i did what you said and flashed a costume recovery .. I've tried both clockwork and philz toch 6 .. i successfully flashed both but neither i could flash a rom with ..
Every time i try new rom i get installation aborted
And if i try to flash with cmd i get Failure (heap not enough)
What can i do now ?? ?

What commands are are you using in CMD to flash your ROM
Did you Flash boot.img from the ROM before flashing ROM
I assume you can get to fastboot mode and recovery mode?
Please do command fastboot getvar version-main and post result

grwalker said:
What commands are are you using in CMD to flash your ROM
Did you Flash boot.img from the ROM before flashing ROM
I assume you can get to fastboot mode and recovery mode?
Please do command fastboot getvar version-main and post result
Click to expand...
Click to collapse
Version-main: 3.14.401.31
I tried the following cmd commands in fastboot :
Fastboot oem rebootruu
Fastboot flash zip 3.zip
And I got the following error message :
Failed <remote: heap not enough >
I tried to flash the boot.img before I flash the rom and get the next error message :
Failed <remote: err = 0xa>
I tried to wipe everything and push the rom to Sdcard with adb push command and tried to flash it via recovery cwm and philz but every time I got (installation aborted ) I tried to install super su the same way and it worked so I guess the rom is not suitable for my device I tried to flash two more roms but with no luck I always get the same error

Not sure what you have done. Try this.
Download the following RUU
http://www.androidruu.com/getdownlo...Radio_5.1204.162.29_release_302015_signed.exe
Put phone in fastboot mode
connect to PC and make sure it says fastboot USB
Open command prompt from what ever folder you fastboot files are in.
type fastboot oem lock (this will lock your bootloader )
Run this RUU
Let me know

grwalker said:
Not sure what you have done. Try this.
Download the following RUU
Put phone in fastboot mode
connect to PC and make sure it says fastboot USB
Open command prompt from what ever folder you fastboot files are in.
type fastboot oem lock (this will lock your bootloader )
Run this RUU
Let me know
Click to expand...
Click to collapse
Thank you very very very very very much u saved my mobile :highfive:
I really appreciate your help and i am thankful to you
Every thing works now .. thaaaaaaank you <3

You are welcome
Note that your bootloader will now be locked and your phone is not rooted.
If you want to experiment with custom ROMs when you must (FIRST) unlock the bootloader and (SECOND) root your phone
onexroot.com is a good site with tutorials to help you.

grwalker said:
You are welcome
Note that your bootloader will now be locked and your phone is not rooted.
If you want to experiment with custom ROMs when you must (FIRST) unlock the bootloader and (SECOND) root your phone
onexroot.com is a good site with tutorials to help you.
Click to expand...
Click to collapse
Ok I'll do that but not now for sure .. I'm just glad that it works
Thanks again man i really appreciate your help <3 <3 <3