Hello,
I am new with the Htc One X , I also have the nexus 4 and previously had galaxy nexus and had rooted them thought the HTC one X was quite different from that so I really wasn able to understand much abt it while I was done rooting it I tried flashing a rom with CWM but then i did not know that I had to flash the boot .img via cmd then when I tried to do that it didn show the serial in ADB devices as the Developer Options was Off is there ANY OTHER way to push the files in or any other solution to make it work? At the moment its not turning on it directly takes it to the bootloader...
Could somebody please help me with it ?
Hoping for a positive response : (
You don't need adb to flash the boot.img.
What does 'fastboot devices' return?
TToivanen said:
You don't need adb to flash the boot.img.
What does 'fastboot devices' return?
Click to expand...
Click to collapse
MB240W101829 fastboot
this is what it shows on fastboot devices
now what should i do?
Put the boot image to the same folder as your fastboot files and type: fastboot flash boot boot.img
Sent from my One X using xda premium
Type in adb devices and see what it returns.
If you can enter fastboot mode, and have the original boot.img (or custom kernel)
Fastboot flash boot nameofboot.img
Sent from my V360 using xda app-developers app
TToivanen said:
You don't need adb to flash the boot.img.
What does 'fastboot devices' return?
Click to expand...
Click to collapse
I even tried fastboot flash boot boot.img and it didn work here is what i got
C:\Users\Sayf\Downloads\OneXRoot>fastboot flash boot boot.img
sending 'boot' (9799 KB)...
OKAY [ 1.261s]
writing 'boot'...
(bootloader) Format partition LNX done
FAILED (remote: err = 0xa)
finished. total time: 1.492s
Are you sure that is the correct boot.IMG
It looks very large.
Someone correct me if I'm wrong but I'm pretty sure that the boot partition on the phone is only 8mb and the error you're getting is because the file you're trying to flash is larger than the available space for the image
Sent from my HTC One X using xda app-developers app
Correct ! boot.img are never that large !!! The stock is around 8 Mb but not much more than that. all the custom boot.img files are between 5 and 6 Mb.....
i correct myself the stock bot.img is exactly 8 Mb....at least for the 2.17 and 3.18 stock !
Related
Ok im not usually this stupid but for some unknown reason my brain went on holiday this morning and I deleted the framework-res.apk from the system/framework folder on the phone when performing a mod. As expected now my nice new phone is stuck in the animation screen and I dont know how to get the file back on the phone.
* The bootloader is unlocked and I have rooted it.
* Adb is setup on my pc but if I boot the phone into the fastboot screen I get no device found when I type adb devices.
* I have tryed the same thing in the Recovery screen.
* Fastboot works and I can lock and unlock the bootloader.
I have installed the samsung usb driver pack which and used the samsung android adb interface as my Adb Interface driver.
I need to somehow push the framework-res.apk (which I have on my pc) back to the /system/framework folder on my phone so it will boot back up or im going to have to send it back ;[
I know there is a dump in the Development forum so I dont know if I can use part of that to flash the system image using fastboot?
Im not too big to ask for help when I need it and thisd isnt my speciality. I have been googling this all night to no avail so now I pass it over to you.
Im not going to bed I hope someone will be able to help when I wake up or its off to phones4u with my broken phone lol.
Mark.
EDIT: Fix can be found *HERE*
As long as that dump is correct, and it seems to be judging from the other replies in the thread, you should be able to simply flash it using 'fastboot flash system system.img' (or whatever he called the file).
If you don't want to do that for some reason you could check if ADB is enabled in recovery as it is in custom roms. If so, you could mount the system partition (mount /system) and then push it from there. Might not be enabled in stock recovery though.
EDIT: I saw you mention adb devices. That only works when adbd is running which it naturally isn't in fastboot mode as that is a much lower level than that. The command 'fastboot devices' exists though.
I'm not familiar with fastboot at all but have you tried adb kill-server and then adb devices?
I had an issue before with finding a device and it fixed it
altimax98 said:
I'm not familiar with fastboot at all but have you tried adb kill-server and then adb devices?
I had an issue before with finding a device and it fixed it
Click to expand...
Click to collapse
ADB is handled by the daemon adbd which starts during boot and is an Android/linux binary. The bootloader most certainly isn't something that high-level though so it makes no sense to try to interface with it using ADB in that mode.
Recovery is a very slimmed down Android though so it would work if it's enabled in stock recovery.
blunden said:
As long as that dump is correct, and it seems to be judging from the other replies in the thread, you should be able to simply flash it using 'fastboot flash system system.img' (or whatever he called the file).
Click to expand...
Click to collapse
I just tryed to flash the system image using fastboot flash system gnsys.img from *THIS* thread and got the following:
sending 'system' (669696 KB)... FAILED (remote: Exceed Buffer Size (0x16400000))
Kinda getting lost here. Any experts around?
Mark.
mskip said:
I just tryed to flash the system image using fastboot flash system gnsys.img from *THIS* thread and got the following:
sending 'system' (669696 KB)... FAILED (remote: Exceed Buffer Size (0x16400000))
Kinda getting lost here. Any experts around?
Mark.
Click to expand...
Click to collapse
http://www.hard-reset.com/samsung-galaxy-nexus-hard-reset.html
?
winwiz said:
http://www.hard-reset.com/samsung-galaxy-nexus-hard-reset.html
?
Click to expand...
Click to collapse
Doesnt do anything I have tryed going through the recovery selection in the fastboot screen. Also that page is inacurate as you need to hold Volume Up + Volume Down while powering up. Volume Up + Power just boots up as normal..
My only bet before taking it back is via fastboot which works fine. I still have the bootloader unlocked but that system image wouldnt flash .
Mark.
Well theoretically you can try to use fastboot and
fastboot flash system system.img
All you need to do is to make system.img
mskip said:
I just tryed to flash the system image using fastboot flash system gnsys.img from *THIS* thread and got the following:
sending 'system' (669696 KB)... FAILED (remote: Exceed Buffer Size (0x16400000))
Kinda getting lost here. Any experts around?
Mark.
Click to expand...
Click to collapse
The system image is probably not a sparse image -- that is, the image exceeds the RAM size for fastboot. Same issue with the Nexus S.
mike1986. said:
Well theoretically you can try to use fastboot and
fastboot flash system system.img
All you need to do is to make system.img
Click to expand...
Click to collapse
How do I make a system image from the system dump *HERE*?
Mark.
ydaraishy said:
The system image is probably not a sparse image -- that is, the image exceeds the RAM size for fastboot. Same issue with the Nexus S.
Click to expand...
Click to collapse
Yes thats exactly what I read about in the Nexus S thread when I was researching this. Is there any way to make it smaller so its flashable?
Mark.
Post here your framework-res.apk
mike1986. said:
Post here your framework-res.apk
Click to expand...
Click to collapse
Here you go
Mark.
In the meantime - have you tried this? http://forum.xda-developers.com/showthread.php?t=1193915
It has "Flash multiple files in one click by using custom folders and tags."
Worth to give a shot. Let me know if it works.
Ok I think I know how to solve your problem What is your stock ROM? ITL41D?
mike1986. said:
Ok I think I know how to solve your problem What is your stock ROM? ITL41D?
Click to expand...
Click to collapse
Yes its the retail build which is ITL41D
Mark.
So here is what I have done:
I included framework-res.apk in ramdisk inside boot.img. This way it should fix your problem but now keep in mind that you can't replace framework-res.apk because it will be reloaded from ramdisk on every boot. So if your device will boot with boot.img from me then adb push framework-res.apk /system/framework and reboot in fastboot and fastboot flash boot boot.img BUT stock boot.img this time so it wont replace your framework-res.apk. So:
1. Modified ITL41D boot.img - flash in fastboot using fastboot flash boot boot_mod.img
2. If system boots (I'm not sure if will) then adb push framework-res.apk /system/framework
3. Boot in fastboot and flash Stock ITL41D boot.img - flash in fastboot using fastboot flash boot boot_stock.img
mike1986. said:
So here is what I have done:
I included framework-res.apk in ramdisk inside boot.img. This way it should fix your problem but now keep in mind that you can't replace framework-res.apk because it will be reloaded from ramdisk on every boot. So if your device will boot with boot.img from me then adb push framework-res.apk /system/framework and reboot in fastboot and fastboot flash boot boot.img BUT stock boot.img this time so it wont replace your framework-res.apk. So:
1. Modified ITL41D boot.img - flash in fastboot using fastboot flash boot boot_mod.img
2. If system boots (I'm not sure if will) then adb push framework-res.apk /system/framework
3. Boot in fastboot and flash Stock ITL41D boot.img - flash in fastboot using fastboot flash boot boot_stock.img
Click to expand...
Click to collapse
WOW. nice if it works!
Doesnt work im afraid..
I get the following information in the command screen:
fastboot flash boot boot_mod.img (my input)
> sending 'boot' (8752 KB)... OKAY
> writing 'boot'... FAILED (remote: Write Fail)
On the phone is displays:
FASTBOOT STATUS - FAILWrite Fail
Mark.
mskip said:
Doesnt work im afraid..
I get the following information in the command screen:
fastboot flash boot boot_mod.img (my input)
> sending 'boot' (8752 KB)... OKAY
> writing 'boot'... FAILED (remote: Write Fail)
On the phone is displays:
FASTBOOT STATUS - FAILWrite Fail
Mark.
Click to expand...
Click to collapse
rename it to boot.img and try again.
HI Guys... this is my first post here so thanks for the great forum
Here is my issue, I've installed The All-in-one tool kit to unlock my phone, all went ok for unlocking,
then i tried to flash a rom and i think i messed up pretty bad.
Just had my One X 2 weeks ago fist time flashing a One X (Did it several times with my Galaxy Ace)
Now my phone keeps on rebooting and eventually gets stuck on boot animation with the red message from CMW saying That this build is for development purposes only ect....
I cant even get in the bootloader, what are my option here?
Thanks in advance
Miamijice
it's strange that you can't go into bootloader, but anyway, can you go to recovery? if so, try to reflash. but anyway you'll need bootloader to flash boot.img ("fastboot flash boot boot.img" on cmd).
or, try to go into recovery, connect to pc, and type in cmd: "adb reboot bootloader", and you should go into bootloader, then flash boot.img
glukosio said:
it's strange that you can't go into bootloader, but anyway, can you go to recovery? if so, try to reflash. but anyway you'll need bootloader to flash boot.img ("fastboot flash boot boot.img" on cmd).
or, try to go into recovery, connect to pc, and type in cmd: "adb reboot bootloader", and you should go into bootloader, then flash boot.img
Click to expand...
Click to collapse
Ok... so i got into bootloader now (kinda tricky when phone reboots on it own.)
Once in bootloader i choose fastboot, then pc connects to phone, then i did fastboot flash boot boot.img in cmd in my c:/android folder (i have the ziped rom file in there too)
C:\Android>fastboot flash boot boot.img
sending 'boot' (4302 KB)... OKAY [ 0.953s]
writing 'boot'... OKAY [ 1.210s]
finished. total time: 2.165s
This is the result. My guess from there is to go in recovery from the bootloader. But i get stuck again rebooting and nothing happends.
I guess im missing something here... Thanks for your patience!
Reflash the recovery again and erase cache with fastboot commands, maybe it helps
Verstuurd van mijn HTC One X
Try this tool to flash recovery and boot.img http://forum.xda-developers.com/showthread.php?t=1734365
Sent from my HTC One X using xda premium
joewong1991 said:
Try this tool to flash recovery and boot.img http://forum.xda-developers.com/showthread.php?t=1734365
Sent from my HTC One X using xda premium
Click to expand...
Click to collapse
hi
i have the same problem with my SE neo ,, i dont know what is this starnge thing happening
i will try the tool and kindly suggest me what i can do now?
Enter bootloader by holding power + volm down for 10 seconds, check if your phone says ***LOCKED*** or ***UNLOCKED at the top and also check if it says 'endeavoru' or 'evita'.
Hi All,
I can't get any version of CWM Recovery working on updated HOX
I'm not flashing it, just doing "fastboot boot imgname" ( this worked for me well before ), and phone hangs with white htc boot screen
I'd like to do backup before i try new Android Revolution HD
After i reset it ( pwr+voldown ), phone boots correctly and works fine, it's just recovery that is not working.
cid HTC_032, hboot 1.36
Any idea ? Am I the only one having this problem ?
Best Regards.
Edit:
fastboot shows this:
downloading 'boot.img'... OKAY
booting... OKAY
it seems like image is being correctly uploaded to memory but not executed
Flash recovery:
fastboot flash recovery imgname
Sent from my HTC One X using xda app-developers app
hahhahhaaa said:
Flash recovery:
fastboot flash recovery imgname
Sent from my HTC One X using xda app-developers app
Click to expand...
Click to collapse
Yes, but i don't want to flash it. i want to boot into cwm recovery without flashing it. This was possible before ota today.
Code:
C:\aaa>fastboot.exe
usage: fastboot [ <option> ] <command>
commands:
update <filename> reflash device from update.zip
flashall flash boot + recovery + system
flash <partition> [ <filename> ] write a file to a flash partition
erase <partition> erase a flash partition
getvar <variable> display a bootloader variable
[U][B] boot <kernel> [ <ramdisk> ] download and boot kernel[/B][/U]
flash:raw boot <kernel> [ <ramdisk> ] create bootimage and flash it
devices list all connected devices
reboot reboot device normally
reboot-bootloader reboot device into bootloader
options:
-w erase userdata and cache
-s <serial number> specify device serial number
-p <product> specify product name
-c <cmdline> override kernel commandline
-i <vendor id> specify a custom USB vendor id
You want to enter the stock or custom recovery ?
Do this
Fastboot erase cache
Helped many people not being able to enter the recovery
And if you want to flash a boot.img its not
Fastboot boot boot.img
But
Fastboot flash boot.img
With fastboot boot boot.img you run the phone once with that specific kernel and with a reboot its undone ! It's more used for test purposes
Your edited tekst in the op says clearly
Downloading boot.img and not recovery.img
Was your command right ?
And btw what's wrong with running the custom recovery and enter from the bootloader or directly from the os . I have a 4-way reboot (also the option to boot into recovery)
Erasing cache didn't help
What's wrong with flashing custom recovery, is that i always try read-only methods before i alter something, even if its useless but working
And I'm genuinely afraid of flashing something that seems to not work
Anyway, this is output from cmd:
Code:
C:\Users\gstawik\Desktop\Android\Flash_boot_17.x_0.1\fastboot>fastboot-windows.e
xe boot ..\..\recovery-clockwork-5.8.4.0-endeavoru.img
downloading 'boot.img'... OKAY
booting... OKAY
C:\Users\gstawik\Desktop\Android\Flash_boot_17.x_0.1\fastboot>
And it DID work many times before the HTC JellyBean OTA update.
Also, i get it, "fastboot flash recovery imgname" to flash, "fastboot boot imgname" to boot directly, now I'm sad, because i feel like my English sucks :crying:
EDIT:
Other fastboot binary versions, including newest one from SDK, do not solve this problem.
Well then i'm a bit in the dark now,.never "played" with these commands. I just flash the damn thing and enter it
I damn did flash this thing and it's working, damn thanks for help anyway
Sent from my HTC One X using xda app-developers app
staviq said:
I damn did flash this thing and it's working, damn thanks for help anyway
Sent from my HTC One X using xda app-developers app
Click to expand...
Click to collapse
:thumbup:
hi guys sorry if i put this in the wrong place but i tried to put the jelly bean on my htc one x on o2 and ive completely messed it up and now it wont boot up its stuck on the o2 screen i don't know what ive done but is there anyway i can get it back to its original state i feel like a complete retard i would be very happy if some one could help me :crying:
What hboot do you have ? And did you flash the boot.img with fastboot commands ?
Can you do fastboot commands
Put the phone in fastboot usb mode and do these commands
Fastboot getvar version-main
Fastboot oem readcid
Post the outcome here please
Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.
C:\Users\Laptop>fastboot getver version-main
'fastboot' is not recognized as an internal or external command,
operable program or batch file.
C:\Users\Laptop>
i take it i cant do commands lol
my hboot-1.12.0000
Mr Hofs said:
What hboot do you have ? And did you flash the boot.img with fastboot commands ?
Can you do fastboot commands
Put the phone in fastboot usb mode and do these commands
Fastboot getvar version-main
Fastboot oem readcid
Post the outcome here please
Click to expand...
Click to collapse
Oke 2 mistakes on your side, you dont have the updated hboot to run JB roms and since fastboot commands do not work you didn't flash the boot.img with the commands
Do you have a folder on the pc with adb and fastboot files ? If no
Download this
http://db.tt/ldx3qOOU
And place it like this
C:\fastboot\the files i gave you
And then open a cmd prompt in the folder and do those commands again
sorry for the long wait
it still say waiting for device + i dont think my usb debugging is enabled
Do you have java sdk and the hyc drivers installed ?
Mr Hofs said:
Do you have java sdk and the hyc drivers installed ?
Click to expand...
Click to collapse
(bootloader) DEBUG: cid: O2___001
OKAY [ 0.110s]
finished. total time: 0.110s
C:\Users\Laptop>C:\fastboot\Fastboot getvar version-main
version-main: 2.17.206.2
finished. total time: 0.063s
C:\Users\Laptop>
there we go sorted it
I don't see your ruu on htcruu.com ! You didn't do a nandroid backup before flashing the JB rom ?
Maybe its on file factory but i don't have an account there
I know somebody that has the nandroid backup that you need, he stated the 28th that he was uploading it.
Its in the nandroid backup thread by Matt95 in the general section ! Gonna PM the guy for the nandroid !!! :thumbup:
Mr Hofs said:
I don't see your ruu on htcruu.com ! You didn't do a nandroid backup before flashing the JB rom ?
Maybe its on file factory but i don't have an account there
Click to expand...
Click to collapse
lol so what do i do now lol i aint bothered about jb i just ics back so i can use my hox again
and as for this (You didn't do a nandroid backup before flashing the JB rom) i dont know what you mean so i guess i didnt do it lol
Now lets get a working phone back for you
Do he next please
Download any ICS rom (i can recommend the viper x) and put it on the sdcard of the phone (do that by mounting the sdcard as a usb disk within the recovery) copy the boot.img file from within the rom.zip file and copy it to the fastboot folder
Put the phone in fastboot usb mode and flash the boot.img with this command
Fastboot flash boot boot.img
Fastboot erase cache
Enter the recovery and do a full wipe (do not wipe the sdcard)
Then choose install zip from sdcard and choose the rom.zip and install it ! Reboot and you have a working phone until I have news about the nandroid backup you need, i already sent him a message
Mr Hofs said:
Now lets get a working phone back for you
Do he next please
Download any ICS rom (i can recommend the viper x) and put it on the sdcard of the phone (do that by mounting the sdcard as a usb disk within the recovery) copy the boot.img file from within the rom.zip file and copy it to the fastboot folder
Put the phone in fastboot usb mode and flash the boot.img with this command
Fastboot flash boot boot.img
Fastboot erase cache
Enter the recovery and do a full wipe (do not wipe the sdcard)
Then choose install zip from sdcard and choose the rom.zip and install it ! Reboot and you have a working phone until I have news about the nandroid backup you need, i already sent him a message
Click to expand...
Click to collapse
i do not how to do this you say put it on my sd card how do i that is there any chance you could show me on skype or something matey ?
Sorry mate no Skype here, and I have only my phone now.....but
Can you get into fastboot mode ?
Unplug the cable to the pc
And choose with the volume rocker the HBOOT press 1 time the power button, it loads a second screen and you see the text RECOVERY and navigate to that again and press power button 1 more time , it will start the recovery .....check which version you have (5.4.8.0)
Then select mounts & storage and check the last option .... Mount as usb disk and plug in the cable
Don't worry mate we will get there .... Just stay with me
tommydee90 said:
i do not how to do this you say put it on my sd card how do i that is there any chance you could show me on skype or something matey ?
Click to expand...
Click to collapse
i did what you said and it puts me right where i started again recovery dont work for me
Reflash the recovery , download this one
http://db.tt/Krlm4dPs
Rename it to recovery.img and put it in the fastboot folder on the pc, put the phone back into fastboot usb mode
Do
Fastboot erase cache
Fastboot flash recovery recovery.img
Fasrrboot erase cache
And enter the recovery again !
C:\Users\Laptop>c:\fastboot\fastboot erase cache
erasing 'cache'...
OKAY [ 0.111s]
finished. total time: 0.111s
C:\Users\Laptop>c:\fastboot\fastboot flash recovery recovery.img
error: cannot load 'recovery.img'
C:\Users\Laptop>c:\fastboot\fastboot erase cache
erasing 'cache'...
OKAY [ 0.093s]
finished. total time: 0.094s
C:\Users\Laptop>c:\fastboot\fastboot flas recovery recovery.img
usage: fastboot [ <option> ] <command>
commands:
update <filename> reflash device from update.zip
flashall flash boot + recovery + system
flash <partition> [ <filename> ] write a file to a flash partition
erase <partition> erase a flash partition
getvar <variable> display a bootloader variable
boot <kernel> [ <ramdisk> ] download and boot kernel
flash:raw boot <kernel> [ <ramdisk> ] create bootimage and flash it
devices list all connected devices
continue continue with autoboot
reboot reboot device normally
reboot-bootloader reboot device into bootloader
help show this help message
options:
-w erase userdata and cache
-s <serial number> specify device serial number
-p <product> specify product name
-c <cmdline> override kernel commandline
-i <vendor id> specify a custom USB vendor id
-b <base_addr> specify a custom kernel base address
-n <page size> specify the nand page size. default:
2048
C:\Users\Laptop>c:\fastboot\fastboot erase cache
erasing 'cache'...
OKAY [ 0.086s]
finished. total time: 0.086s
i pressed recovery again and it takes me back to fastboot.. the htc load screen come on with red writing at the bottom end of it also i have in pink ***relocked***security warning ***
Ah its relocked, that explains it. Can you find back the unlock_code.bin file that you received by the hycdev site when you first unlocked the device ?
Put that file also in the fastboot folder on pc and reboot the phone again into fastboot usb mode
Do
Fastboot flash unlocktoken unlock_code.bin
This will unlock the bootloader and you will be able to flash the recovery .... So try again
Tom,
If you want I will walk not run you through everything buddy. PM me and we can chat on FB or whatever so you not only sort yourself out but you understand too!
Sent from my HTC One X using xda premium
leonforthewin said:
Tom,
If you want I will walk not run you through everything buddy. PM me and we can chat on FB or whatever so you not only sort yourself out but you understand too!
Sent from my HTC One X using xda premium
Click to expand...
Click to collapse
This feels like a small kick in the nuts, you think i ain't helping him the right way
But you can take over and i will enjoy the rest of my evening
Mr Hofs said:
This feels like a small kick in the nuts, you think i ain't helping him the right way
But you can take over and i will enjoy the rest of my evening
Click to expand...
Click to collapse
My bad man, I didn't even think about that. I did the exact same thing when I first messed around with my HOX and I completely panicked. I'm sure after the next reply the issue will be resolved.
leonforthewin said:
My bad man, I didn't even think about that. I did the exact same thing when I first messed around with my HOX and I completely panicked. I'm sure after the next reply the issue will be resolved.
Click to expand...
Click to collapse
No mate you didn't mean no harm, and if its easier for him .... He's has the choice always good that people want to help ! Just messing with ya for a bit
While rooting my One X I may have gotten a bit stuck, the phone hangs at the HTC loading screen.
And I cannot load a custom recovery onto the phone.
I have unlocked the boot loader, but got to the step of flashing the custom recovery and I get this error:
sending 'recovery' <6038 KB>...
FAILED (command write faileed (Unknown error))
finsihed. total time: 0.642s
I got boot into fastboot, and can see my phone, appear with the command "fastboot devices" but am unable to do anything else.
Any help to get my phone back would be appresiated
Vest1ge said:
While rooting my One X I may have gotten a bit stuck, the phone hangs at the HTC loading screen.
And I cannot load a custom recovery onto the phone.
I have unlocked the boot loader, but got to the step of flashing the custom recovery and I get this error:
sending 'recovery' <6038 KB>...
FAILED (command write faileed (Unknown error))
finsihed. total time: 0.642s
I got boot into fastboot, and can see my phone, appear with the command "fastboot devices" but am unable to do anything else.
Any help to get my phone back would be appresiated
Click to expand...
Click to collapse
how did you flash the recovery? i mean the command.
robchongke said:
how did you flash the recovery? i mean the command.
Click to expand...
Click to collapse
I have never managed to get a successful flash.
I have tired through the CMD command as well as One X toolkit by Hansoon2000
fastboot flash recovery <file>
Vest1ge said:
I have never managed to get a successful flash.
I have tired through the CMD command as well as One X toolkit by Hansoon2000
Click to expand...
Click to collapse
i used hassoon's toolkit and it never gave me problem. maybe you forgot to place the recovery.img in the fastboot folder?
robchongke said:
i used hassoon's toolkit and it never gave me problem. maybe you forgot to place the recovery.img in the fastboot folder?
Click to expand...
Click to collapse
I got the same error, with the CMD command, I think i've done something to the phone..
Vest1ge said:
I have never managed to get a successful flash.
I have tired through the CMD command as well as One X toolkit by Hansoon2000
fastboot flash recovery <file>
Click to expand...
Click to collapse
did you enter the command
fastboot flash recovery.img or fastboot flash recovery recovery.img?
robchongke said:
did you enter the command
fastboot flash recovery.img or fastboot flash recovery recovery.img?
Click to expand...
Click to collapse
fastboot flash recovery CWM.img (to be precise)
I wish it was that simple.
Just tried it again first ime same eorr, then tried it again and it just held on sending ' recovery' and the phone went unresponsive
it is that simple. put recovery.img inside fastboot folder. go into bootloader then flash recovery via cmd with the command fastboot flash recovery recovery.img. that's it. did you try downloading another recovery? might be a bad download. i guess.
Tried another USB port or cable?
Sent from my HTC One X using xda app-developers app
tomascus said:
Tried another USB port or cable?
Sent from my HTC One X using xda app-developers app
Click to expand...
Click to collapse
That worked perfect.
Manged to install clockwork recovery, but still once loading CM10.1 onto my phone, can't get past the htc screen.
Went Factory Reset -> Reset Cache -> Loaded ROM from SD
Vest1ge said:
That worked perfect.
Manged to install clockwork recovery, but still once loading CM10.1 onto my phone, can't get past the htc screen.
Went Factory Reset -> Reset Cache -> Loaded ROM from SD
Click to expand...
Click to collapse
Did you flash the boot.img file from the rom.zip via fastboot? And then did you erase fastboot cache? Did you wipe everything before installing the rom via recovery?
-Sent from my IceCold One X!