I managed to unlock root and install TWRP recovery.
Before and after flashing the ROM i even tried to flash the boot.img file by "fastboot flash boot boot.img"
No matter what ALL ROMS hang at the splash screen.
These are the ROMS i tried:
Viper - http://forum.xda-developers.com/showthread.php?t=1868236
Clean ROM -
Android Revolution
Kinda getting frustrated, HTC desire was not that hard to root and flash, not sure why the one X is taking the breath outta me.
HTC One X:
Unlocked
ENDEAVORU PVT SHIP S-ON RL
HBOOT 0.32.0000
CPLD-None
MICROP-None
RADIO-None
eMMC-bootmode: disabled
CPU-bootmode: disabled
HW SEcure boot: enabled
MODEM PATH: OFF
Mar 1 2012 01:43:15
Please help!
Your hboot is WAY to low ! Give the outcome of :
Fastboot getvar version-main
Sent from my HTC One X using XDA Premium 4 mobile app
Mr Hofs said:
Your hboot is WAY to low ! Give the outcome of :
Fastboot getvar version-main
Sent from my HTC One X using XDA Premium 4 mobile app
Click to expand...
Click to collapse
1.19.707.1
So here is what I did, tried downloading JBFWTools and up the hboot version but I think i am doing something wrong because it keeps redirecting me to the web page.
I have copied the firmware file to the SD card and follow the 5 step instruction as what was mentioned in the prompt in the batch file but to no +ve result..
http://forum.xda-developers.com/showthread.php?t=1924003
My guess is that your hboot is so low that it won't update via that way. Try this....
Relock the bootloader :
Fastboot oem lock
Then execute this ruu with admin rights
http://www.androidruu.com/getdownlo..._Radio_1.1204.90.13_release_251281_signed.exe
Once that one is done you install this one
http://www.androidruu.com/getdownlo...Radio_1.1204.105.14_release_260743_signed.exe
Then this one
http://www.androidruu.com/getdownlo...Radio_2.1204.135.20_release_278245_signed.exe
And last but least this one
http://www.androidruu.com/getdownlo...Radio_5.1204.162.29_release_296434_signed.exe
After the last one you let the phone search for manual ota updates, do that multiple times until you are sure there aren't any left !
Ow and btw....a firmware is not flashed via the sdcard of the phone. But from the pc to the phone in fastboot mode.
Sent from my HTC One X using XDA Premium 4 mobile app
Crap that is a ton of steps!
Thanks Mr Hofs will try out tonite and keep you posted.
The reason why i never bothered to do this is because the phone did pretty well for the last few years with the ROM that it came with, its just lately with all the higher requirements of softwares its about time that I cleaned it up. Din know I joined the dinosaurs!
Fastboot oem lock
Outcome - worked
The following were Run as Administator
http://www.androidruu.com/getdownloa...281_signed.exe
Nothing happened, no screen or anything else came up
http://www.androidruu.com/getdownloa...743_signed.exe
Stopped with and exit error code 800700002
http://www.androidruu.com/getdownloa...245_signed.exe
Nothing happened, no screen or anything else came up
http://www.androidruu.com/getdownloa...434_signed.exe
A proper installation screen came up and pushed a file and did some installation but the end result said something like "Unable to update ROM"
I think there is still something missing or fishy.
danceunlimited said:
Fastboot oem lock
Outcome - worked
The following were Run as Administator
http://www.androidruu.com/getdownloa...281_signed.exe
Nothing happened, no screen or anything else came up
http://www.androidruu.com/getdownloa...743_signed.exe
Stopped with and exit error code 800700002
http://www.androidruu.com/getdownloa...245_signed.exe
Nothing happened, no screen or anything else came up
http://www.androidruu.com/getdownloa...434_signed.exe
A proper installation screen came up and pushed a file and did some installation but the end result said something like "Unable to update ROM"
I think there is still something missing or fishy.
Click to expand...
Click to collapse
In fastboot mode run the command - fastboot oem rebootRUU
You'll see a black screen with HTC logo.
After this, run the RUU
Sent from my HTC One X
athulele said:
In fastboot mode run the command - fastboot oem rebootRUU
You'll see a black screen with HTC logo.
After this, run the RUU
Sent from my HTC One X
Click to expand...
Click to collapse
That's not how you run a ruu ! A ruu is with the phone in the bootloader (with a relocked or locked bootloader) then right click the ruu.exe and select run as administrator. The problem could be the low hboot. It might not be able to update the hboot with big steps like these !
A firmware flash might solve that (and that's where you need that particular command)
@ OP :
Check here
http://forum.xda-developers.com/showthread.php?t=1957376
Mr Hofs said:
That's not how you run a ruu ! A ruu is with the phone in the bootloader (with a relocked or locked bootloader) then right click the ruu.exe and select run as administrator. The problem could be the low hboot. It might not be able to update the hboot with big steps like these !
A firmware flash might solve that (and that's where you need that particular command)
Click to expand...
Click to collapse
Ah I see, thanks for correcting me.
Sent from my HTC One X
I see the firmwares are still off-line so i have another idea.
Download this ota
http://androidruu.com/getdownload.p....29.707.11_release_278501swqci0rxt8n4m2hf.zip
Take out the firmware.zip and follow the procedures in the thread i linked.
After that you try the 2.17.707 or the 3.14.707 ruu again.
Sent from my HTC One X using XDA Premium 4 mobile app
OK this is weird or there is a rookie mistake here .. my fastboot does not have a OEM REBOOT option
here is the help output from my fastboot, what am doing wrong chiefs?
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:
Fastboot commands are executed from the pc to the phone in bootloader mode !
And watch the capital letters they are important too
And where does it say the command OEM REBOOT ? In the guide i linked with the firmwares there is no such command mentioned at all
Sent from my HTC One X using XDA Premium 4 mobile app
I did run it from my PC in bootloader mode and it was in lower case.
For this set of instructions can you please explain or lead me to a thread for the following areas:
Download this ota http://androidruu.com/getdownload.ph...rxt8n4m2hf.zip
OK Understand
Take out the firmware.zip and follow the procedures in the thread i linked.
OK Understand but which thread?
After that you try the 2.17.707 or the 3.14.707 ruu again.
Previously posted links did not contain these two numbers, so possible to pls post the link.
Sorry for the trouble. Just want to make sure I am taking all precautions and doing things right so as to not brick my phone.
These are the commands ! The firmware zip is in the OTA file....and the 2 ruu's are linked a page back. The one starting with 2.17.707 and 3.14.707 check those links. They are direct download links, can't mis them !!!
Sent from my HTC One X using XDA Premium 4 mobile app
Previous posts did not contain these numbers ? What are the bottom 2 ruu.exe files then ?
It says firmware.zip is invalid.
How did you take the firmware zip out of the ota ? I always use 7zip to open the archive and drag the firmware zip out.
Worst case scenario is that your hboot is to low .... maybe and even older ruu might work. Or look for another older ota and take the firmware zip out of that.
Sent from my HTC One X using XDA Premium 4 mobile app
I ll try 7zip now. I am using winzip. Tried opening the zip file in explorer which always works. But not in this case.
7zip works winzip doesnt .. back on track.. work in progress ..
Battery low: need to charge up and continue after a few hours of sleep, will keep you posted Mr Hofs! Need to get some sleep for the moment.
Related
I bought DHD, which won't boot at all, I thought maybe I can fix it, but dunno anymore. Here's what hboot screen says:
ACE PVT SHIP S-ON RL
HBOOT-2.00.0027
MICROP-0438
RADIO-26.14.04.28_M
eMMC-boot
Sep 7 2011, 19:06:24
I've tried to flash recovery from 2 different SD-cards, but hboot doesn't recognize my sd's at all. I have thought, that it should check the card and scan it at the beginning, but that won't happen. Filesystem is FAT32. I've also tried to unlock the bootloader, but it gets stuck to error message 'Command error' (fastboot oem get_identifier_token). When I try to flash recovery, it says 'Signature verify fail' (fastboot flash recovery recovery.img)
RUU is RUU_Ace_Sense30_S_HTC_WWE_3.12.405.1_Radio_12.65.60.29_26.14.04.28_M_release_225512_signed
When I try to install another (older) RUU it stops always to signature error (132)
Is there any way to get this phone to working condition again? No need to root nor Custom ROM...
Oh, almost forgot. fastboot getvar_all shows:
version: 0.5
version-bootloader: 2.00.0027
version-baseband: 26.14.04.28_M
version-cpld: None
version-microp: 0438
version-main: 3.12.405.1
serialno: HT0C8RX02173
product: ace
platform: HBOOT-7230
modelid: PD9810000
cidnum: HTC__Y13
battery-status: good
battery-voltage: 4152mV
partition-layout: Generic
security: on
build-mode: SHIP
boot-mode: FASTBOOT
commitno-bootloader: 743ca94a
hbootpreupdate: 11
gencheckpt: 0
region-id: 0
There's always a danger of buying a phone of this nature without knowing its history. Usually when they don't do any flashing and this happens its hardware problem. I bought one with the same problem as yours and i tried every known method sad to say i was resign to having bought a brick but lucky for me i bought another cheap with cracked screen so i took out the main board and switch it over use the best parts of both phones and i got myself a nice working DHD with a spare chrome housing. So maybe yr best bet is to lookout for a cracked screen one and do the same. Put an ad on web for yr area..you never know .....good luck cheers
Sent from my Desire HD using xda premium
ndmuni said:
There's always a danger of buying a phone of this nature without knowing its history. Usually when they don't do any flashing and this happens its hardware problem. I bought one with the same problem as yours and i tried every known method sad to say i was resign to having bought a brick but lucky for me i bought another cheap with cracked screen so i took out the main board and switch it over use the best parts of both phones and i got myself a nice working DHD with a spare chrome housing. So maybe yr best bet is to lookout for a cracked screen one and do the same. Put an ad on web for yr area..you never know .....good luck cheers
Sent from my Desire HD using xda premium
Click to expand...
Click to collapse
Yeah, I also think that the phone is bricked, I've tried anything, and because it doesn't recognize SD-card in the hboot, I think it's a hardware problem...
Oh, and another thing: Phone LED stays red always when usb plugged, even when I remove USB cable... It turns off when I pull the battery off. I've never seen any other colour, even after all night loading...
Now I'm beginning to search one with cracked screen also. Luckily I didn't pay much for that brick.
Have you tried putting phone in fastboot and running the current ruu. Older ruu won't run on newer hboot.
Sent from my Inspire 4G using xda premium
You need http://www.mobfirmware.com/dl/behtash/imei dhd/rom.zip
Move it to where your adb files are.
Then do the following from adb:
adb reboot oem-78 >> this will put you in RUU download mode. I found you can run this command from CWM Recovery. Though... if you don't have any recovery I'm unsure how to hit RUU download mode. There is an .exe from HTC Dev that'll do it from Fastboot, so there must be a command (fastboot reboot oem-78 maybe??)
Once you're at the black screen w/ silver HTC logo, type:
fastboot flash zip rom.zip >> This will change your hboot to one w/ an oem signature. Once it's successful, type:
fastboot reboot
Now, you'll need to go to htcdev.com/bootloader and follow the instructions to get your KEY (fastboot oem get_identifier_token) and paste it to HTCDev to get your boot unlock bin file emailed to you. Follow the last steps to unlock your bootloader.
The steps are something like: boot to fastboot> type oem command> copy / paste key to htcdev> receive email> download .bin file to adb folder> run command to unlock w/ .bin file (it's on the htcdev site).
NOW you can flash the custom recovery or boot imgs without getting the "Signature Verified Fail" Error.
Goodluck! I just went through this whole process so you can get your phone up and going w/ a custom rom from where you're stuck! Don't give up!
luncht1me said:
Then do the following from adb:
adb reboot oem-78 >> this will put you in RUU download mode. I found you can run this command from CWM Recovery. Though... if you don't have any recovery I'm unsure how to hit RUU download mode. There is an .exe from HTC Dev that'll do it from Fastboot, so there must be a command (fastboot reboot oem-78 maybe??)
Once you're at the black screen w/ silver HTC logo, type:
fastboot flash zip rom.zip >> This will change your hboot to one w/ an oem signature. Once it's successful, type:
fastboot reboot
Now, you'll need to go to htcdev.com/bootloader and follow the instructions to get your KEY (fastboot oem get_identifier_token) and paste it to HTCDev to get your boot unlock bin file emailed to you. Follow the last steps to unlock your bootloader.
The steps are something like: boot to fastboot> type oem command> copy / paste key to htcdev> receive email> download .bin file to adb folder> run command to unlock w/ .bin file (it's on the htcdev site).
NOW you can flash the custom recovery or boot imgs without getting the "Signature Verified Fail" Error.
Goodluck! I just went through this whole process so you can get your phone up and going w/ a custom rom from where you're stuck! Don't give up!
Click to expand...
Click to collapse
Thank you! I'll try that. I've tried to unlock bootloader, though, but when I type fastboot oem get_identifier_token, it won't do anything, just says 'command error' ...
luncht1me said:
Then do the following from adb:
adb reboot oem-78 >> this will put you in RUU download mode. I found you can run this command from CWM Recovery. Though... if you don't have any recovery I'm unsure how to hit RUU download mode. There is an .exe from HTC Dev that'll do it from Fastboot, so there must be a command (fastboot reboot oem-78 maybe??)
Once you're at the black screen w/ silver HTC logo, type:
fastboot flash zip rom.zip >> This will change your hboot to one w/ an oem signature. Once it's successful, type:
fastboot reboot
Now, you'll need to go to htcdev.com/bootloader and follow the instructions to get your KEY (fastboot oem get_identifier_token) and paste it to HTCDev to get your boot unlock bin file emailed to you. Follow the last steps to unlock your bootloader.
The steps are something like: boot to fastboot> type oem command> copy / paste key to htcdev> receive email> download .bin file to adb folder> run command to unlock w/ .bin file (it's on the htcdev site).
NOW you can flash the custom recovery or boot imgs without getting the "Signature Verified Fail" Error.
Goodluck! I just went through this whole process so you can get your phone up and going w/ a custom rom from where you're stuck! Don't give up!
Click to expand...
Click to collapse
OMG, I got the bootloader unlocked, but then what? I tried to flash ROM from RUU, but it stopped to error message "FAILED (remote: not allowed)" ... ? Sorry for my stupid questions, but this is all new for me. I'm fast to learn, though
deezaye said:
OMG, I got the bootloader unlocked, but then what? I tried to flash ROM from RUU, but it stopped to error message "FAILED (remote: not allowed)" ... ? Sorry for my stupid questions, but this is all new for me. I'm fast to learn, though
Click to expand...
Click to collapse
Ruu can not be flashed with unlocked bootloaders.
Sent from my GT-N7000 using xda app-developers app
glevitan said:
Ruu can not be flashed with unlocked bootloaders.
Sent from my GT-N7000 using xda app-developers app
Click to expand...
Click to collapse
OK. Can I flash any custom ROM then? What version should hboot be? It's now 2.00.0029, what if I put custom recovery and custom rom in? Do I need to downgrade hboot, or do I need S-OFF, or ENG S-OFF?
deezaye said:
OK. Can I flash any custom ROM then? What version should hboot be? It's now 2.00.0029, what if I put custom recovery and custom rom in? Do I need to downgrade hboot, or do I need S-OFF, or ENG S-OFF?
Click to expand...
Click to collapse
What you,need is to read. You have idea of what you are doing. Use the guide in my signature, it will help.
Sent from my GT-N7000 using xda app-developers app
glevitan said:
What you,need is to read. You have idea of what you are doing. Use the guide in my signature, it will help.
Sent from my GT-N7000 using xda app-developers app
Click to expand...
Click to collapse
Thanks, only problem is that I can't use adb, since it doesn't recognize my phone at all, nor flash anything from SD, it's not recognized either.
I can only use fastboot commands
fastboot flash zip cwm-5.0.2.7-ace.zip --> Failed (Remote: 32 header error)
fastboot flash zip pd98img.zip --> Failed (Remote: 24 parsing android-info fail) OR 41 model id check fail
deezaye said:
Thanks, only problem is that I can't use adb, since it doesn't recognize my phone at all, nor flash anything from SD, it's not recognized either.
I can only use fastboot commands
fastboot flash zip cwm-5.0.2.7-ace.zip --> Failed (Remote: 32 header error)
fastboot flash zip pd98img.zip --> Failed (Remote: 24 parsing android-info fail) OR 41 model id check fail
Click to expand...
Click to collapse
Make sure that you are on fastboot. Are you putting you phone on ruu mode first? (fastboot oem rebootRUU)
Sent from my GT-N7000 using xda app-developers app
glevitan said:
Make sure that you are on fastboot. Are you putting you phone on ruu mode first? (fastboot oem rebootRUU)
Sent from my GT-N7000 using xda app-developers app
Click to expand...
Click to collapse
Yes, and yes.
deezaye said:
Yes, and yes.
Click to expand...
Click to collapse
Sorry, do you mind if I have a look over teamviewer? Maybe, there is something missing...
Sent from my GT-N7000 using xda app-developers app
glevitan said:
Sorry, do you mind if I have a look over teamviewer? Maybe, there is something missing...
Sent from my GT-N7000 using xda app-developers app
Click to expand...
Click to collapse
OK
deezaye said:
OK
Click to expand...
Click to collapse
Conclusion: Hardware/mobo failure... Thanks Glevitan for help!
Lo all!
My HTC One X is stuck in a reboot loop after trying to root today.
I unlocked the bootloader through the HTC site with no issues, and I tried to root using the "insecurebootandroot" method. I still have access to the bootloader/fastboot where it says *unlocked*. I've tried performing a factory reset from here but that has not made a diffference.
Any help appreciated!
c:\fastboot>fastboot getvar version-main
version-main: 2.17.61.3
hboot-1.12.0000
CPLd-None
MICROP-None
RADIO-None
eMMC-bootmode: disabled
CPU-bootmode: disabled
HW secure boot: enabled
MODEM PATH: OFF
Try fastboot erase cache in cmd
Sent from my HTC One X using xda premium
Was the insecure boot compatible with your main version? Link to guide?
Sent from my HTC One X using xda app-developers app
Thanks for the replies guys.
The guide I followed is below:
knowyourmobile.com/smartphones/htc/onex/onexuserguides/1419609/ how_to_root_your_htc_one_x. html
I think I have already tried the fastboot erase cache command.
I have had to insert spaces into the link as I am not allowed to post them yet
girbot said:
Thanks for the replies guys.
The guide I followed is below:
knowyourmobile.com/smartphones/htc/onex/onexuserguides/1419609/ how_to_root_your_htc_one_x. html
I think I have already tried the fastboot erase cache command.
I have had to insert spaces into the link as I am not allowed to post them yet
Click to expand...
Click to collapse
Here's the deal: the guide you followed was super old and the 2.17 update of your phone has broken the compatibility to the insecureboot root method.
You need your stock boot.img back in order to recover.
Acquire the stock boot.img with the following steps:
Dowbload the appropriate nandroid backup from this thread: http://forum.xda-developers.com/showthread.php?t=1975140
If you can't find the exact same version as yours, any 2.17 should do.
Extract boot.img from the downloaded backup and place it in your fastboot folder. Flash it by typing:
"fastboot flash boot boot.img"
Followed by
"fastboot erase cache"
Then your phone should boot up just fine.
Sent from my One X
Its there, the exact nandroid you need
Apologies for the slow reply. Yeah I just the correct boot.img and I was all fixed. Thanks for the help.
Now, to the rooting:
Download the clockworkmod recovery here:
http://www.clockworkmod.com/rommanager
And place it in fastboot folder.
Then flash by typing: fastboot flash recovery filename.zip
And
Fastboot erase cache.
Then download supersu here:
http://download.chainfire.eu/298/SuperSU/CWM-SuperSU-v0.99.zip
Place it on your sd.
Flash in recovery with the install zip from sdcard option.
Sent from my HTC One X using xda app-developers app
Done, all rooted and booted
Good!
CASE CLOSED
shall we say
Sent from my HTC One X using xda app-developers app
If i may.. This case i not quite closed yet..
PERFORM A FULL BACKUP USING CLOCKWORKMOD!
- And then keep it safe, should you ever need it!
Hi all
I have the HTC ONE X International TEGRA 3 version.
Could do with some help.
I've updated HBOOT to 1.28 and when i try to install aokp_ICJ422-V2.9.5.zip in recovery this is what i get:
updating partition details...
installing '/sdcard/0/roms/aokp_ICJ422-V2.9.5.zip'...
checking for md5 file...
skipping md5 check: no md5 file found.
assert failed: getprop("ro.bootloader") == "1.28.0000" ||
E:error in 'sdcard/0/roms/aokp_ICJ422-V2.9.5.zip'
updating partition details...
Then it says Failed underneath
This is using Team Win Recovery Project v2.4.1.0
Any help is appreciated
AFAIK it should work on 1.28 hboot but it seems that LorD made a slight mistake while writing the updater script...
Is there any way you could update the hboot even further?
Sent from my IceCold One X
TToivanen said:
AFAIK it should work on 1.28 hboot but it seems that LorD made a slight mistake while writing the updater script...
Is there any way you could update the hboot even further?
Sent from my IceCold One X
Click to expand...
Click to collapse
I dont think i can as it was what was on the htc dev website and i just use the identifier token thats shown in cmd prompt
Ahem, hboot version has nothing to do with either htcdev or identifier token.
Please do:
fastboot oem readcid
And post the result here.
Sent from my IceCold One X
TToivanen said:
Ahem, hboot version has nothing to do with either htcdev or identifier token.
Please do:
fastboot oem readcid
And post the result here.
Sent from my IceCold One X
Click to expand...
Click to collapse
INFODEBUG: cid: HTC__001
You can go up to 1.39. Please stand by for instructions.
Download this: http://goo.gl/M0hLq
Rename it "firmware" if it isn't already named so. Copy it to the fastboot folder.
Put your Unlock_code.bin to your fastboot folder (search email inbox if you've lost it)
Then do the commands one by one:
fastboot oem lock
fastboot oem rebootRUU
fastboot flash zip firmware.zip (do several times if it fails)
fastboot flash unlocktoken Unlock_code.bin
Then flash the recovery of your choice and proceed.
jaymz_uk said:
INFODEBUG: cid: HTC__001
Click to expand...
Click to collapse
just checked in recovery and it still says HBOOT-1.12.0000 even though ive done " fastboot flash unlocktoken Unlock_code.bin
So as it stands i have bootloader and recovery but no OS.
Thanks for the help usually i can install rom's fine as i was using the 4.2.1 AOKP rom
Ive done what you said hboot is still 1.12.0000
firmware.zip keeps saying failed remote not allowed and remote 000000008.
still failing on writing zip
TToivanen said:
You can go up to 1.39. Please stand by for instructions.
Download this: http://goo.gl/M0hLq
Rename it "firmware" if it isn't already named so. Copy it to the fastboot folder.
Put your Unlock_code.bin to your fastboot folder (search email inbox if you've lost it)
Then do the commands one by one:
fastboot oem lock
fastboot oem rebootRUU
fastboot flash zip firmware.zip (do several times if it fails)
fastboot flash unlocktoken Unlock_code.bin
Then flash the recovery of your choice and proceed.
Click to expand...
Click to collapse
Will it write the zip file if its relocked?
jaymz_uk said:
Will it write the zip file if its relocked?
Click to expand...
Click to collapse
Still not working can someone help me get this sorted as i need my phone.
jaymz_uk said:
Will it write the zip file if its relocked?
Click to expand...
Click to collapse
It MUST be relocked in order to flash.
Sent from my IceCold One X
TToivanen said:
It MUST be relocked in order to flash.
Sent from my IceCold One X
Click to expand...
Click to collapse
well it keeps saying failed when trying to write. Should i just keep trying it?
jaymz_uk said:
well it keeps saying failed when trying to write. Should i just keep trying it?
Click to expand...
Click to collapse
It should flash fine after 2-3 tries.
Sent from my IceCold One X
TToivanen said:
It should flash fine after 2-3 tries.
Sent from my IceCold One X
Click to expand...
Click to collapse
for some reason it keeps saying failed when writing and then it just says waiting for device for ages
Does it have to be s-off as mines s-on
jaymz_uk said:
for some reason it keeps saying failed when writing and then it just says waiting for device for ages
Does it have to be s-off as mines s-on
Click to expand...
Click to collapse
Also rebooting the RUU is it supposed to show the word htc then go to something or do i reboot
jaymz_uk said:
Also rebooting the RUU is it supposed to show the word htc then go to something or do i reboot
Click to expand...
Click to collapse
Ok it worked turned phone off waited a couple of minutes then tried it all again and it worked. Just got to try the rom now will post back if all worked.
Thanks
All sorted and working just got to set it up. your a life save thanks for the help.
Great! Enjoy that masterpiece of a ROM.
Sent from my IceCold One X
MARVEL PVT SHIP S-ON RL
HBOOT 1.09.0099
MICROP-0451
RADIO-7.57.39.10M
Feb 8 2012, 18:29:31
Hello,
Recently my htc wildfire S crashed and only boots to Hboot mode..
cannot go to recovery and cannot do factory reset.. when i press these options the phone just reboots to hboot mode
the phone can be detected via usb and i do get hboot usb plug detection as well fastboot usb mode..
I have tried hundreds of possibilities to flash but failed..
Have tried the RUU method via computer whereby i get different errors and also tried different RUU but unsuccessful
The last RUU that i had used to root my phone was
RUU_Marvel_S_HTC_Europe_2.26.401.3_Radio_47.23e.35.3038H_7.57.39.10M_release_261695_signed
which worked well for one year but crashed after reseting to factory settings
now..
when my bootloader is unlocked i got error 155 image error
when my bootloader is relocked i get error 140 bootloader version error
both ways it stops during verifying for signature
and on the phone it shows main version older.. update failed
have tried to place PM76IMG.zip on sdcard but the phone reads as wrong or no image
(and this goes for different RUU as well)
have tried to use fastboot via cmd commands but get
FAILED (remote: 12 signature verify fail)
or
FAILED (remote: 43 signature verify fail)
images do load without problem but fail after signature checking
there is no other RUU newer than 2.26
cannot downgrade hboot cause cannot access my phone just hboot mode only
cannot do flash recovery as i have tried many recovery images all failing as well as clockword mode recovery image
PLEASE HELP load the ROM and make the phone usable again
Did you make a Gold card before placing PG76IMG in SD card?
tahaice said:
MARVEL PVT SHIP S-ON RL
HBOOT 1.09.0099
MICROP-0451
RADIO-7.57.39.10M
Feb 8 2012, 18:29:31
Hello,
Recently my htc wildfire S crashed and only boots to Hboot mode..
cannot go to recovery and cannot do factory reset.. when i press these options the phone just reboots to hboot mode
the phone can be detected via usb and i do get hboot usb plug detection as well fastboot usb mode..
I have tried hundreds of possibilities to flash but failed..
Have tried the RUU method via computer whereby i get different errors and also tried different RUU but unsuccessful
The last RUU that i had used to root my phone was
RUU_Marvel_S_HTC_Europe_2.26.401.3_Radio_47.23e.35.3038H_7.57.39.10M_release_261695_signed
which worked well for one year but crashed after reseting to factory settings
now..
when my bootloader is unlocked i got error 155 image error
when my bootloader is relocked i get error 140 bootloader version error
both ways it stops during verifying for signature
and on the phone it shows main version older.. update failed
have tried to place PM76IMG.zip on sdcard but the phone reads as wrong or no image
(and this goes for different RUU as well)
have tried to use fastboot via cmd commands but get
FAILED (remote: 12 signature verify fail)
or
FAILED (remote: 43 signature verify fail)
images do load without problem but fail after signature checking
there is no other RUU newer than 2.26
cannot downgrade hboot cause cannot access my phone just hboot mode only
cannot do flash recovery as i have tried many recovery images all failing as well as clockword mode recovery image
PLEASE HELP load the ROM and make the phone usable again
Click to expand...
Click to collapse
Your recoverys are not flashing as you have relocked your bootloader pal. Try flashing the stock recovery from hboot this should at least have a factory reset option. Failing this, you should try re-unlocking your bootloader and then flashing cwm.
If all of this fails then you will need to gain access to an xtc clip, make the phone s-off and then flash any ruu you want bump this thread if you need anymore help
Sent from my Nexus 7 using Tapatalk HD
varun26296 said:
Did you make a Gold card before placing PG76IMG in SD card?
Click to expand...
Click to collapse
thanks for reply
i did not make a gold card.. my phone crashed on me without consent lol..
and i cannot make one now coz there is no shell or rom on my phone.. just bootloader and thats it..
unless there is a way around to make a goldcard via fastboot menu??
heavy_metal_man said:
Your recoverys are not flashing as you have relocked your bootloader pal. Try flashing the stock recovery from hboot this should at least have a factory reset option. Failing this, you should try re-unlocking your bootloader and then flashing cwm.
If all of this fails then you will need to gain access to an xtc clip, make the phone s-off and then flash any ruu you want bump this thread if you need anymore help
Sent from my Nexus 7 using Tapatalk HD
Click to expand...
Click to collapse
Thanks for reply
none of the recoverys are flashing either bootloader is unlocked or relocked.. Tried even flashing CWM but all i get is errors that image verify fail!! unless i am going somewhere wrong..??
My phone is S-ON is there no around this without an xtc clip..?? coz thats another issue
tahaice said:
Thanks for reply
none of the recoverys are flashing either bootloader is unlocked or relocked.. Tried even flashing CWM but all i get is errors that image verify fail!! unless i am going somewhere wrong..??
My phone is S-ON is there no around this without an xtc clip..?? coz thats another issue
Click to expand...
Click to collapse
What errors are you getting when trying to flash cwm via fastboot while the bootloader is unlocked. Be specific please
Also their is no other way to s-off bar the xtc clip. But, once you have s-off trouble shooting bootloader/ruu issues is far easier
Sent from my Nexus 7 using Tapatalk HD
heavy_metal_man said:
What errors are you getting when trying to flash cwm via fastboot while the bootloader is unlocked. Be specific please
Also their is no other way to s-off bar the xtc clip. But, once you have s-off trouble shooting bootloader/ruu issues is far easier
Sent from my Nexus 7 using Tapatalk HD
Click to expand...
Click to collapse
#heavymetal
when UNLOCKED
image update error
when RELOCKED
signature verify fail
i tried flashing CWM version 5.0.2.8 image file..
(the same happens while flashing other files!!)
tahaice said:
#heavymetal
when UNLOCKED
image update error
when RELOCKED
signature verify fail
i tried flashing CWM version 5.0.2.8 image file..
(the same happens while flashing other files!!)
Click to expand...
Click to collapse
Ok while unlocked, take your cwm recovery image and rename it to recovery.img if you have not already.
Then boot into fastboot and use the command
Fastboot boot recovery recovery.img
Hopefully it will boot into the recovery. This is only tempoary, do not reboot until you have wiped everything. Check and see if it boots after full wipes.
If this fails you will need a xtc clip...
Sent from my HTC Sensation XE with Beats Audio Z715e using xda premium
---------- Post added at 09:45 PM ---------- Previous post was at 09:04 PM ----------
heavy_metal_man said:
Ok while unlocked, take your cwm recovery image and rename it to recovery.img if you have not already.
Then boot into fastboot and use the command
Fastboot boot recovery recovery.img
Hopefully it will boot into the recovery. This is only tempoary, do not reboot until you have wiped everything. Check and see if it boots after full wipes.
If this fails you will need a xtc clip...
Sent from my HTC Sensation XE with Beats Audio Z715e using xda premium
Click to expand...
Click to collapse
Edit: the more i look into this the more it doesn't look good to be honest pal, most people who get into this state send it back to the manufacturer and get the motherboards replaced....
Sent from my HTC Sensation XE with Beats Audio Z715e using xda premium
heavy_metal_man said:
Ok while unlocked, take your cwm recovery image and rename it to recovery.img if you have not already.
Then boot into fastboot and use the command
Fastboot boot recovery recovery.img
Hopefully it will boot into the recovery. This is only tempoary, do not reboot until you have wiped everything. Check and see if it boots after full wipes.
If this fails you will need a xtc clip...
Sent from my HTC Sensation XE with Beats Audio Z715e using xda premium
---------- Post added at 09:45 PM ---------- Previous post was at 09:04 PM ----------
Edit: the more i look into this the more it doesn't look good to be honest pal, most people who get into this state send it back to the manufacturer and get the motherboards replaced....
Sent from my HTC Sensation XE with Beats Audio Z715e using xda premium
Click to expand...
Click to collapse
tried again all possibilities..
with fastboot boot recovery recovery.img it does download successfully and writes booting.. however after the phone has booted by itself the htc screen shows up (with white background) and directly goes into fastboot menu without other options...
Maybe i am uploading wrong recovery image??
if its loading into bootloader menu that means my phone is soft bricked right?? which can be undone??
my dilemma is that i live in a third world country with no htc service providers or good phone repair shops who would have an xtc clip..
tahaice said:
tried again all possibilities..
with fastboot boot recovery recovery.img it does download successfully and writes booting.. however after the phone has booted by itself the htc screen shows up (with white background) and directly goes into fastboot menu without other options...
Maybe i am uploading wrong recovery image??
if its loading into bootloader menu that means my phone is soft bricked right?? which can be undone??
my dilemma is that i live in a third world country with no htc service providers or good phone repair shops who would have an xtc clip..
Click to expand...
Click to collapse
The main issue is that it should still boot into the recovery via fastboot regardless of its working state from what i have read the main nand seems to have some sort of error that it cannot over write so its not letting you boot anything weither that is a fail safe or not i dont know. At this point a xtc clip would be your last hope, but i cannot guarrentee it would work... I have an xtc clip, but i dont want to post it outside of the uk ......
Sent from my Nexus 7 using Tapatalk HD
Were you overclocked ? Were you using some sort of memory script ?
I'd say your best option is to have it sent back, smells like a burnt motherboard.
heavy_metal_man said:
The main issue is that it should still boot into the recovery via fastboot regardless of its working state from what i have read the main nand seems to have some sort of error that it cannot over write so its not letting you boot anything weither that is a fail safe or not i dont know. At this point a xtc clip would be your last hope, but i cannot guarrentee it would work... I have an xtc clip, but i dont want to post it outside of the uk ......
Sent from my Nexus 7 using Tapatalk HD
Click to expand...
Click to collapse
thanks for your help heavy metal.. seems i am left with a dead fone after all RIP :crying:
omnomnomkimiiee said:
Were you overclocked ? Were you using some sort of memory script ?
I'd say your best option is to have it sent back, smells like a burnt motherboard.
Click to expand...
Click to collapse
no didnt mess with phone settings.. didnt overclock it.. and no memory scripts.. though had installed avast anti-theft software.. would it have played a part? but i remember uninstalling the software before resetting my to factory settings!!
im sorry for your loss man what do you think you will do with the device? bin?
Recover soft-bricked HTC Wildfire S
tahaice said:
no didnt mess with phone settings.. didnt overclock it.. and no memory scripts.. though had installed avast anti-theft software.. would it have played a part? but i remember uninstalling the software before resetting my to factory settings!!
Click to expand...
Click to collapse
Hi tahaice!.
I just recovered an HTC Wildfire S A510e for a friend with a problem similar to yours!
He entered on HBOOT and wiped & format some partitions: data/factory reset, system, data, sdcard, etc.....
I read quickly your problem and I think that this can help you:
1.- Download the correct RUU from: androidfiles.org/ruu/?developer=Marvel_MarvelC
For instance, I used RUU_Marvel_S_HTC_Europe_2.26.401.3_Radio_47.23e.35.3038H_7.57.39.10M_release_261695_signed for Spain (Device was with last update, my friend was sure).
You can check it on HBOOT:
MARVEL PVT SHIP S-ON RL
HBOOT 1.09.0099
MICROP-0451
RADIO-7.57.39.10M
Feb 8 2012, 18:29:31
Click to expand...
Click to collapse
And when you finish restore: go to Settings/About phone/Software info/More. Base band version must match the file you used (you will not restore radio.img, if not needed).
2.- Run the RUU until the wizard comes up. While the RUU wizard is open, find the temporary folder it created. (Open Explorer in Windows and type %temp% in the navigation bar.) There will be folders with long names (C:\Users\lefe\AppData\Local\Temp\{9739F95A-99D7-43BA-8AB6-E4F02264D361}\{50F2F878-636A-496F-A7CB-544C067E0C4B} for instance).
Inside one of them you will find the file rom.zip from RUU. Open it with 7zip and extract recovery.img, boot.img and system.img. Put it in the location you preffer (C:\Users\lefe\HTC Wildfire S A510e\ADB in the example).
You also need adb.exe, AdbWinApi.dll and fastboot.exe. Copy from the folder you found the file rom.zip (or from Android SDK tools if you have installed it).
3.- Boot the phone into bootloader (power off, hold down volume and press power) and highlight FASTBOOT using the volume rocker and pressing power. Then connect the USB cable. You should see FASTBOOT USB.
As you say, this is not needed in your case because your phone goes directly. Just plug.
4.- Open a command prompt in Windows and navigate to the folder where you unpacked ADB / installed Android SDK tools. Flash the stock images extracted in step 2 above using the following commands (Remember to turn your firewall off):
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system.img
Click to expand...
Click to collapse
Example (what I did):
Code:
C:\Users\lefe\HTC Wildfire S A510e\ADB>fastboot flash boot boot.img
sending 'boot' (2870 KB)...
OKAY [ 1.336s]
writing 'boot'...
OKAY [ 1.650s]
finished. total time: 2.994s
C:\Users\lefe\HTC Wildfire S A510e\ADB>fastboot flash recovery recovery.img
sending 'recovery' (3494 KB)...
OKAY [ 1.572s]
writing 'recovery'...
OKAY [ 1.970s]
finished. total time: 3.554s
C:\Users\lefe\HTC Wildfire S A510e\ADB>fastboot flash system system.img
sending 'system' (259862 KB)...
OKAY [ 31.535s]
writing 'system'...
OKAY [ 64.846s]
finished. total time: 96.393s
5.- Finally, in your phone go to HBOOT menu and make a FACTORY RESET.
If needed, PowerOff device (remove battery for 3 seconds) and Boot the phone into bootloader (hold down volume and press power).
That's all!!.
I hope you get lucky!
[Plz, mark thread as Solved if that helped you, other users will love to read it when googling]
heavy_metal_man said:
im sorry for your loss man what do you think you will do with the device? bin?
Click to expand...
Click to collapse
right now its hidden deep inside my cupboard.. dont want to see it near me!! a disappoinment
bolzass said:
Hi tahaice!.
I just recovered an HTC Wildfire S A510e for a friend with a problem similar to yours!
He entered on HBOOT and wiped & format some partitions: data/factory reset, system, data, sdcard, etc.....
I read quickly your problem and I think that this can help you:
1.- Download the correct RUU from: androidfiles.org/ruu/?developer=Marvel_MarvelC
For instance, I used RUU_Marvel_S_HTC_Europe_2.26.401.3_Radio_47.23e.35.3038H_7.57.39.10M_release_261695_signed for Spain (Device was with last update, my friend was sure).
You can check it on HBOOT:
And when you finish restore: go to Settings/About phone/Software info/More. Base band version must match the file you used (you will not restore radio.img, if not needed).
2.- Run the RUU until the wizard comes up. While the RUU wizard is open, find the temporary folder it created. (Open Explorer in Windows and type %temp% in the navigation bar.) There will be folders with long names (C:\Users\lefe\AppData\Local\Temp\{9739F95A-99D7-43BA-8AB6-E4F02264D361}\{50F2F878-636A-496F-A7CB-544C067E0C4B} for instance).
Inside one of them you will find the file rom.zip from RUU. Open it with 7zip and extract recovery.img, boot.img and system.img. Put it in the location you preffer (C:\Users\lefe\HTC Wildfire S A510e\ADB in the example).
You also need adb.exe, AdbWinApi.dll and fastboot.exe. Copy from the folder you found the file rom.zip (or from Android SDK tools if you have installed it).
3.- Boot the phone into bootloader (power off, hold down volume and press power) and highlight FASTBOOT using the volume rocker and pressing power. Then connect the USB cable. You should see FASTBOOT USB.
As you say, this is not needed in your case because your phone goes directly. Just plug.
4.- Open a command prompt in Windows and navigate to the folder where you unpacked ADB / installed Android SDK tools. Flash the stock images extracted in step 2 above using the following commands (Remember to turn your firewall off):
Example (what I did):
Code:
C:\Users\lefe\HTC Wildfire S A510e\ADB>fastboot flash boot boot.img
sending 'boot' (2870 KB)...
OKAY [ 1.336s]
writing 'boot'...
OKAY [ 1.650s]
finished. total time: 2.994s
C:\Users\lefe\HTC Wildfire S A510e\ADB>fastboot flash recovery recovery.img
sending 'recovery' (3494 KB)...
OKAY [ 1.572s]
writing 'recovery'...
OKAY [ 1.970s]
finished. total time: 3.554s
C:\Users\lefe\HTC Wildfire S A510e\ADB>fastboot flash system system.img
sending 'system' (259862 KB)...
OKAY [ 31.535s]
writing 'system'...
OKAY [ 64.846s]
finished. total time: 96.393s
5.- Finally, in your phone go to HBOOT menu and make a FACTORY RESET.
If needed, PowerOff device (remove battery for 3 seconds) and Boot the phone into bootloader (hold down volume and press power).
That's all!!.
I hope you get lucky!
[Plz, mark thread as Solved if that helped you, other users will love to read it when googling]
Click to expand...
Click to collapse
thank bolzass for ur reply..
without doubt we have the same ROM version and i had downloaded the same RUU from androidfiles website.. but still getting those silly errors despite following each step carefully!! i dont know what has gone wrong
BY THE WAY I CANNOT ERASE USERDATA
it says FAILED (remote: not allowed)
can this be causing other errors???
tahaice said:
right now its hidden deep inside my cupboard.. dont want to see it near me!! a disappoinment
Click to expand...
Click to collapse
At this point its probably for the best
Sent from my HTC Sensation XE with Beats Audio Z715e using xda premium
tahaice said:
thank bolzass for ur reply..
without doubt we have the same ROM version and i had downloaded the same RUU from androidfiles website.. but still getting those silly errors despite following each step carefully!! i dont know what has gone wrong
Click to expand...
Click to collapse
Ops!?!?..., Can you detail these errors?.
I'm also reading your message bellow about erasing Userdata...:$, detail also this scenario so we can think about your concret issues.
Keep fighting till you're sure there's nothing to do...
I tried to update this HTC ONE X (fastboot oem readcid "HTC_622", fastboot getvar version-main "9.29.709.7", HBOOT-0.43.0000, RADIO-1.1204.104.14) from ICS to JB but failed now it will not go past the boot screen. I have tried searching for the exact RUU but haven't had any luck. Any help will be appriciated.
I hope you mean 1.29.709 ?
Try this one
http://androidruu.com/getdownload.p...Radio_1.1204.104.14_release_259284_signed.exe
Mr Hofs said:
I hope you mean 1.29.709 ?
Try this one
http://androidruu.com/getdownload.p...Radio_1.1204.104.14_release_259284_signed.exe
Click to expand...
Click to collapse
RUU_ENDEAVOR_U_ICS_40_hTC_Asia_TW_1.26.709.3_Radio_1.1204.90.13_release_251853_signed (CID ERROR)
RUU_ENDEAVOR_U_JB_45_S_hTC_Asia_TW_3.14.709.20_Radio_5.1204.162.29_release_292865_signed (CID ERROR)
RUU_ENDEAVOR_U_JB_45_S_HTC_Europe_3.14.401.31_R_Radio_5.1204.162.29_release_302015_signed (CID ERROR)
RUU_ENDEAVOR_U_ICS_40_hTC_Asia_HK_1.29.708.9_Radio_1.1204.104.14_release_259897_signed (CID ERROR)
RUU_ENDEAVOR_U_ICS_40_hTC_Asia_TW_1.29.709.7_Radio_1.1204.104.14_release_259284_signed (DOES NOT RUN)
But does fastboot getvar version-main come up with 9.29.709 or 1.29.709 ?
When the main comes up with 709 you can't run a 708 ruu and vice versa !
Try the 1.29.709 ruu again but make sure to turn off firwewalls and anti-virus software, also make sure to put the phone in the fastboot usb mode (do : fastboot devices command prior to run the ruu to see if it comes up with the serial) and also execute the ruu with admin rights. Right click the ruu and select run as administrator
Thanks I downloaded it twice but it doesn't run. Guess something's wrong with that file.
Sent from my SAMSUNG-SGH-I337 using XDA Premium 4 mobile app
Mr Hofs said:
But does fastboot getvar version-main come up with 9.29.709 or 1.29.709 ?
Click to expand...
Click to collapse
This question still stands !
Am so sorry. My version is 9.29.709.7.
Sent from my SAMSUNG-SGH-I337 using XDA Premium 4 mobile app
In my existence here in the hox section i have never.....ever seen a main number like that !
Please attach a picture of your complete hboot !