[Q] HTC One X Bootloop. Help, please? - HTC One X

Hello,
I am completely new to the android world. I got an HTC One X (International) a while ago, and I tried to boot it and install a custom ROM. I followed some steps on a YouTube video, and I messed the situation so much that I can't find a way to fix it.
My phone is stuck in a bootloop and it won't work at all. When I get into the bootloader it gives me the following info. :
*** RELOCKED ***
ENDEAVOUR PVT SHIP S-ON RL
HBOOT-1.39.0000
CPLD- None
MICROP- None
RADIO- 5.1204.162.29
eMMC-bootmode: disabled
CPU- bootmode: disabled
HW Secure boot: enabled
MODEM PATH: OFF​
I tried to download an RUU but I couldn't find the 3.16.415.4 Arabic version. I am very unfamiliar with the whole boot/roms thing.
Can anyone please help me?

Niklaus11 said:
Hello,
I am completely new to the android world. I got an HTC One X (International) a while ago, and I tried to boot it and install a custom ROM. I followed some steps on a YouTube video, and I messed the situation so much that I can't find a way to fix it.
My phone is stuck in a bootloop and it won't work at all. When I get into the bootloader it gives me the following info. :
*** RELOCKED ***
ENDEAVOUR PVT SHIP S-ON RL
HBOOT-1.39.0000
CPLD- None
MICROP- None
RADIO- 5.1204.162.29
eMMC-bootmode: disabled
CPU- bootmode: disabled
HW Secure boot: enabled
MODEM PATH: OFF​
I tried to download an RUU but I couldn't find the 3.16.415.4 Arabic version. I am very unfamiliar with the whole boot/roms thing.
Can anyone please help me?
Click to expand...
Click to collapse
Unlock your bootloader because you relocked I don't know why then flash Philz 5.15.9 charge the phone inside recovery and when you finish with this we will see other thing

Thant said:
Unlock your bootloader because you relocked I don't know why then flash Philz 5.15.9 charge the phone inside recovery and when you finish with this we will see other thing
Click to expand...
Click to collapse
I tried to unlock the bootloader with "fastboot oem unlock", at first it gave me a <waiting for device> message and nothing ever happened. I tried again and it now gives me the following:
C:\Users\Home>fastboot oem unlock
...
(bootloader) [ERR] Command error !!!
OKAY [ 0.123s]
finished. total time: 0.124s​
I tried different cables and different USB ports and nothing changed.

Niklaus11 said:
I tried to unlock the bootloader with "fastboot oem unlock", at first it gave me a <waiting for device> message and nothing ever happened. I tried again and it now gives me the following:
C:\Users\Home>fastboot oem unlock
...
(bootloader) [ERR] Command error !!!
OKAY [ 0.123s]
finished. total time: 0.124s​
I tried different cables and different USB ports and nothing changed.
Click to expand...
Click to collapse
Go to Settings->Power->Fast boot..untick that box and try to do it again.

Niklaus11 said:
I tried to unlock the bootloader with "fastboot oem unlock", at first it gave me a <waiting for device> message and nothing ever happened. I tried again and it now gives me the following:
C:\Users\Home>fastboot oem unlock
...
(bootloader) [ERR] Command error !!!
OKAY [ 0.123s]
finished. total time: 0.124s​
I tried different cables and different USB ports and nothing changed.
Click to expand...
Click to collapse
the command is not write the right command is fastboot flash unlocktoken Unlock_code.bin second install latest htc drivers or htc sync and then remove only htc sync. Report back

Related

[HELP ME] Possible BRICK, Need Help BIGTIME

Hi All,
I have severely screwed up my One X.
The status of my device is as follows:
Normal boot will go directly to bootloader, no operating system on it. The bootloader appears as follows:
(before this appears, some strange red text flashes saying 'This build is for development purposes only')
*** RELOCKED ***
*** Security Warning ***
ENDEAVORU PVT SHIP S-ON RL
HBOOT-0.94.0000
CPLD-None
MICROP-None
RADIO-1.1204.90.13H
eMMC-bootmode: disabled
CPU-bootmode: disabled
HW Secure boot: enabled
MODEM PATH: OFF
Apr 11 2012,02:17:11
In fastboot, it will not allow me to flash to boot, system or recovery. Various errors appears like:
- not allowed
- error code 0000008 (or something)
- '...' then 'complete', but its a total lie because its done nothing.
My network is Three UK, this is a result of getting halfway through running:
"RUU_ENDEAVOR_U_ICS_40_H3G_UK_1.26.771.2_Radio_1.1204.90.13H_release_251403_signed.exe"
Then it telling me that my bootloader version is incorrect.
Future runs of this tell me that my battery is too low, even though I chareged it till green last night.
If it 'reboot bootloader' the same screen as above loads without the *** Security Warning ***
Nothing Ive found on these forums work, Im in serious need of HELP!!
You're on wrong section mate.
You will have better assistance in Q&A section.
Tips: you need 1.28.771.x RUU to revert to stock. 1.26.771.2 won't work as yours is HBOOT-0.94.0000
I tried
RUU_ENDEAVOR_U_ICS_40_HTC_Europe_1.28.401.9_Radio_1.1204.103.14_release_256469_signed
and it says there is a customer id error,
Do i need specifically 1.28.771?
Jaso333 said:
I tried
RUU_ENDEAVOR_U_ICS_40_HTC_Europe_1.28.401.9_Radio_1.1204.103.14_release_256469_signed
and it says there is a customer id error,
Do i need specifically 1.28.771?
Click to expand...
Click to collapse
Yes as that is the correct one for three UK, that's why you had the I'd error.
ckpv5 said:
You're on wrong section mate.
You will have better assistance in Q&A section.
Tips: you need 1.28.771.x RUU to revert to stock. 1.26.771.2 won't work as yours is HBOOT-0.94.0000
Click to expand...
Click to collapse
Well, he has 'developed' a brick....it's just not the development that's normally discussed here ;-)
ewok666 said:
Well, he has 'developed' a brick....it's just not the development that's normally discussed here ;-)
Click to expand...
Click to collapse
Haha!
Sorry , don't wanna laugh on the brick but what he said was funny.
Sent from my HTC One X using Tapatalk 2
Even though my CLID is coming up at 'NONE'?
It'll say none but you'll have the 3UK CID - you will have to wait for the 1.28.771.9 RUU to surface (if at all) or send it back to 3
Jaso333 said:
Hi All,
I have severely screwed up my One X.
The status of my device is as follows:
Normal boot will go directly to bootloader, no operating system on it. The bootloader appears as follows:
(before this appears, some strange red text flashes saying 'This build is for development purposes only')
*** RELOCKED ***
*** Security Warning ***
ENDEAVORU PVT SHIP S-ON RL
HBOOT-0.94.0000
CPLD-None
MICROP-None
RADIO-1.1204.90.13H
eMMC-bootmode: disabled
CPU-bootmode: disabled
HW Secure boot: enabled
MODEM PATH: OFF
Apr 11 2012,02:17:11
In fastboot, it will not allow me to flash to boot, system or recovery. Various errors appears like:
- not allowed
- error code 0000008 (or something)
- '...' then 'complete', but its a total lie because its done nothing.
My network is Three UK, this is a result of getting halfway through running:
"RUU_ENDEAVOR_U_ICS_40_H3G_UK_1.26.771.2_Radio_1.1204.90.13H_release_251403_signed.exe"
Then it telling me that my bootloader version is incorrect.
Future runs of this tell me that my battery is too low, even though I chareged it till green last night.
If it 'reboot bootloader' the same screen as above loads without the *** Security Warning ***
Nothing Ive found on these forums work, Im in serious need of HELP!!
Click to expand...
Click to collapse
Have you tried unlocking the bootloader again to flash anything?
or
In fastboot "fastboot boot new-recoveryver.img"
Then "adb push rom.zip /sdcard/"
fastboot boot says its not allowed
wtfhax said:
Have you tried unlocking the bootloader again to flash anything?
Click to expand...
Click to collapse
Quoting myself
it wont let me unlock the bootloader!
to prove this:
C:\Android>fastboot oem lock
...
(bootloader) Device was already locked!
OKAY [ 0.020s]
finished. total time: 0.020s
C:\Android>fastboot oem unlock Unlock_code.bin
...
(bootloader) [ERR] Command error !!!
OKAY [ 0.030s]
finished. total time: 0.030s
completely ruined?
yea this happened to my phone
I had to reboot it a few times and keep trying fastboot oem unlock/lock
it should come good.
Jaso333 said:
Hi All,
I have severely screwed up my One X.
The status of my device is as follows:
Normal boot will go directly to bootloader, no operating system on it. The bootloader appears as follows:
(before this appears, some strange red text flashes saying 'This build is for development purposes only'
My network is Three UK, this is a result of getting halfway through running:
"RUU_ENDEAVOR_U_ICS_40_H3G_UK_1.26.771.2_Radio_1.1204.90.13H_release_251403_signed.exe"
Then it telling me that my bootloader version is incorrect.
Future runs of this tell me that my battery is too low, even though I chareged it till green last night.
If it 'reboot bootloader' the same screen as above loads without the *** Security Warning ***
Nothing Ive found on these forums work, Im in serious need of HELP!!
Click to expand...
Click to collapse
Had you try reflash stock recovery. I had successfully Ruu 1.26.707.2 from cook 1.28.401.09 then OTA to 1.28.707.10 and pass through a lot of pain warnings.
With correct original ruu, it allows you to recover (try mainfixer.bat) to origin factory status.
Sent from my HTC One X using xda premium
Jaso333 said:
it wont let me unlock the bootloader!
to prove this:
C:\Android>fastboot oem lock
...
(bootloader) Device was already locked!
OKAY [ 0.020s]
finished. total time: 0.020s
C:\Android>fastboot oem unlock Unlock_code.bin
...
(bootloader) [ERR] Command error !!!
OKAY [ 0.030s]
finished. total time: 0.030s
completely ruined?
Click to expand...
Click to collapse
Proper unlock command
fastboot flash unlocktoken Unlock_code.bin
EddyOS said:
It'll say none but you'll have the 3UK CID - you will have to wait for the 1.28.771.9 RUU to surface (if at all) or send it back to 3
Click to expand...
Click to collapse
Just seen on twitter @Three_UK have just tweeted that 1.28.771.9 is available.
wtfhax said:
Proper unlock command
fastboot flash unlocktoken Unlock_code.bin
Click to expand...
Click to collapse
DUDE [email protected] A F***ING LIFE SAVER!!!!!!!
I WAS USING THE WRONG COMMAND TO UNLOCK IT... FFS. IM SUCH AN IDIOT
ITS ALL WORKING NOW
Now to cancel the HTC Service.....

Locking/relocking bootloader

Hey guys, I'm not very adept at android stuff so please bear with me.
I unlocked my bootloader yesterday via the HTC Dev site with an attempt to convert my ROM to CM10 (the Jellybean one). However, I realized that the process was a little too complex for me, so I decided to relock the bootloader first until I decide whether I want to get CM10/figure the process out.
Hence, I relocked the bootloader using the cmd command fastboot oem lock.
So, what I see on the command prompt is something similar to this.
<Bootloader> Lock successfully
FAILED <status read failed <Too many links>>
finished. total time: 0.142s
On the bootloader window (is that what you guys call it? It's the window you get when booting the phone while pressing power+volume down),
the information (in pink and green text) reads:
*** Relocked ***
ENDEAVORU PVT SHIP S-ON RL
HBOOT-1.12.0000
CPLD-None
MICROP-None
RADIO-2.1204.135.20
eMMC-bootmode: disabled
CPU-bootmode : disabled
HW Secure boot: disabled
MODEM PATH : OFF
Jun 28 20212, 11:31:28
I apologize for being a little paranoid, but since I didn't "flash" any custom ROMs or anything, but merely unlocked and relocked the bootloader, is there anything which might brick my phone when the next OTA comes in?
Also, should I be worried about the command prompt text (the one with FAILED) although the previous line reads "lock successfully"? After the relock my phone rebooted as normal, and I experience no problems using the phone.
Can anyone help with all this? Thanks in advance guys.
It's fine, you're good to go
All is good. As you haven't modified the ROM or recovery then ota will work fine.
The status read failed is nothing to worry about.
Mine does tat every time when locking or unlocking but none the less the process still completes
Sent from my Nexus 7
Thanks a lot for the replies. It had me worried there for a while. Cheers!
So if you have "relocked" your boot loader and want to unlock it again do you hace to flash the "Unlock_code.bin" again, or is there a faster way?
nuckel82 said:
So if you have "relocked" your boot loader and want to unlock it again do you hace to flash the "Unlock_code.bin" again, or is there a faster way?
Click to expand...
Click to collapse
Use the Unlock_code.bin again
sent from my One X using xda venom premium

[Q] How to get RUU - i need it to revert back to stock ROM

Hi, i read somewhere that i need to use the correct RUU to revert back to my stock rom htc one x. i kinda lost my nandroid backup.
is the RUU can be found in fastboot? if so, here are the details.
ENDEAVORU PVT SHIP S-ON RL
HBOOT-1.12.0000
CPLD-None
MICROP-None
RADIO-2.1204.135.20
eMMC-bootmode: disabled
CPU-bootmode: disabled
HW secure boot: enabled
MODEM PATH: Off
June 28 2012, 11:31:28
here you'll find everything you need
Fastboot getvar version-main
Fastboot oem readcid
Will give you the info you need
hi, i know this thread was created last month.. sorry for bringing this up again, i didnt want to create a new one for the same purpose. also, i was busy from work so i didnt had time to work on this. now ive got my hands full on this to work..
c:\android>fastboot getvar version-main
version-main: 2.17.707.3
finished. total time: 0.007s
c:\android>fastboot oem readcid
...
(bootloader) DEBUG: cid: HTC__044
OKAY [ 0.013s]
finished. total time: 0.013s
these are the info on my phone, can someone kindly direct me to the correct RUU? there are tons out there and im afraid that i might get the wrong.
if you need other info, just let me know.
thanks
http://bugsylawson.com/index.php/fi...73-radio-2120413520-release-278245-signedexe/
Firstly lock the bootloader, "fastboot oem lock"
Then right click the RUU and select "run as administrator"
TToivanen said:
http://bugsylawson.com/index.php/fi...73-radio-2120413520-release-278245-signedexe/
Firstly lock the bootloader, "fastboot oem lock"
Then right click the RUU and select "run as administrator"
Click to expand...
Click to collapse
thanks for this i managed to bring back the original ROM.
also just want to give background info. on this..
after I bring back Sense ROM in this unit, i will be surrendering it to HTC center because the LCD was broken and need of replacement.
last month i brought it there and they were charging me a couple of hundred dollars on top of the LCD replacement, due to the reason im using a different kind of ROM and such..
How can i guarantee that the ROM im using is a legit one and so i wont be questioned by them anymore and just replace the screen?
I checked the software info on my phone now, and it displays:
Android Version: 4.0.4
HTC sense version: 4.1
Software Number: 2.17.707.3
HTC SDK API level: 4.23
HTC extension version: HTCExtension_403_1_GA_20
i hope this can be any of help to you
If you run the ruu succesfully its full stock. You can't run another ruu then the one that is released for your phone with your software number ! Don't worry about that.
The only thing that they will see is the relocked bootloader, they always know its been unlocked before. That's all.
They can make a problem of that, because in certain cases unlocking means no more warranty
how to get RUU - i need it to revert back to stock ROM
how to get RUU - i need it to revert back to stock ROM
my device
endeavoru pvt ship s-on rl
hboot-0.94.0000
cpld-none
MICROP-NONE
RADIO-2.1204.135.20
eMMC-BOOTMODE : DISABLE
CPU -bootable : disable
HW secure boot : enable
modem path ff
apr 11 2012 ,02,27,11
IME : 359188044706349
SN : HT242W100676
MB: 419G223826444
please help me
:crying::crying::crying:
zqutli said:
how to get RUU - i need it to revert back to stock ROM
my device
endeavoru pvt ship s-on rl
hboot-0.94.0000
cpld-none
MICROP-NONE
RADIO-2.1204.135.20
eMMC-BOOTMODE : DISABLE
CPU -bootable : disable
HW secure boot : enable
modem path ff
apr 11 2012 ,02,27,11
IME : 359188044706349
SN : HT242W100676
MB: 419G223826444
please help me
:crying::crying::crying:
Click to expand...
Click to collapse
First delete your IMEI and S/N. Second post the result from command fastboot getvar all and again delete your IMEI and S/N.
What CID are you what is your main version?
the result : waiting for device
Thant said:
First delete your IMEI and S/N. Second post the result from command fastboot getvar all and again delete your IMEI and S/N.
What CID are you what is your main version?
Click to expand...
Click to collapse
My CID : htc_e11
When Ienter fastboot getvar all
the result : waiting for device
:crying::crying::crying:
zqutli said:
My CID : htc_e11
When Ienter fastboot getvar all
the result : waiting for device
:crying::crying::crying:
Click to expand...
Click to collapse
When you connect your phone to computer what are you see in device manager are you install the latest HTC drivers
Ah at least HTC E11 is dutch and a main 401
android ADB interface
Thant said:
When you connect your phone to computer what are you see in device manager are you install the latest HTC drivers
Click to expand...
Click to collapse
I see android ADB interface
Do you see a MYHTC ?
Getvar all
Thant said:
When you connect your phone to computer what are you see in device manager are you install the latest HTC drivers
Click to expand...
Click to collapse
version : 0.5a
version-baseband : 2.1204.135.20
version-microp: none
imei:
platform: HBOOT-T30S
cidnum:none
battery-voltage:3549mV
SECURITY: ON
COMMITNO-BOOTLOADER : NONE
DONE
First things first.......put the phone on charge ! Put it inside the recovery (tell us what recovery you have ?) Otherwise you get stuck with a drained battery soon !
Then try this :
Download the full android sdk bundle, unpack it and go to the platform tools folder. Open a command window there and type
Fastboot devices (with the phone in fastboot usb mode)
yes i see my htc
Mr Hofs said:
Do you see a MYHTC ?
Click to expand...
Click to collapse
yes i see my htc:good:
Oke now try it via the Android sdk package which i mentioned.

[Q] SoftBricked HTC One X don't know what else to try

Hi Guys, let me express my gratitude beforehand for all the help that you have provided gratuitously to so many users so far. I happen to find myself in a delicate situation with my newly acquired(last week) HTC One X, that after a few days of use prompted me to install an update. I foolishly accepted and started the installation. After it rebooted it found itself in a bootloop - starting, vibrating for a second, displaying the Quietly Brilliant logo and then restarting again. I then began browsing on the XDA forum and researching on this particular problem. I started with the common troubleshooting steps : tried entering the recovery menu (power+vol down) and selecting "Recovery" - that didn't do anything differently-, then i tried a factory reset, same thing, then i tried and installed the RUU that i think is for my device(i'll post the name below) that ended up with what i thought was a successful process but ended up in the same bootloop after the restart.​
At that point i read further and decided to root/unlock my device so i can try and install a custom ROM. Unlocked my device using the unlock token provided by HTC and then installed the clockwork recovery tool. After that i tried installing a couple of custom roms like ARHD31 which seemed like it was going to work(got through the configuration settings but after the restart this time was stuck at a HTC ONE logo ). I later read that for this to work you need a newer HBoot(mine is 1.12.0000). I then tried flasing an older rom with ICS(Renovate) that did not work either. I am not ruling out that i may be botching up somewhere in the process though, that's why i am seeking your help.​
The RUU that i tried for my device is:
RUU_Endeavor_U_ICS_40_S_HTC_Europe_2.17.401.2_Radi o_2.1204.135.20_release_274900_signed.exe
My details for my device were as follows(also attached a picture):
****LOCKED**** (it now reads UNLOCKED or RELOCKED if i lock it to try the RUU)
ENDEAVORU XE SHIP S-OFF RL
CID-11111111 (I read that this is the SUPERCID but i did not change that, it was like that)
HBOOT- 1.12.0000
CPLD-None
MICROP-None
RADIO-2.1204.135.20
eMMC..: disabled
CPU..: disabled
HW Secure boot : enabled
Modem path : OFF
June 28 2012, 11:31:28
The GetVar allinfo command :
Code:
c:\Fastboot>fastboot getvar all
INFOversion: 0.5a
INFOversion-bootloader: 1.12.0000
INFOversion-baseband: 2.1204.135.20
INFOversion-cpld: None
INFOversion-microp: None
INFOversion-main: 2.17.401.2
INFOserialno: SH27DW101219
INFOimei: 353426058867508
INFOproduct: endeavoru
INFOplatform: HBOOT-T30S
INFOmodelid: PJ461****
INFOcidnum: 11111111
INFObattery-status: good
INFObattery-voltage: 3694mV
INFOdevpower: 6
INFOpartition-layout: None
INFOsecurity: off
INFObuild-mode: SHIP
INFOboot-mode: FASTBOOT
INFOcommitno-bootloader: None
INFOhbootpreupdate: 2
INFOgencheckpt: 0
all: Done!
finished. total time: 0.821s
Sorry for the long read but I'm hoping that you guys can help me with this, i even took it to a "specialized" repair service but they just ended up by draining my battery(recharging with script now).
Oke i will give it a try
Download this firmware
http://arhd.onedroid.net/db_mirror/Firmware/HTC/HTC_One_X/401/3.14.401.31.zip
1: Rename the file to firmware.zip and copy it to the fastboot folder
2: put the phone in fastboot usb mode/bootloader
3: enter these commands
Fastboot oem RebootRUU
Fastboot flash zip firmware.zip
(maybe needed a second time, watch the outcome of the flash on the pc)
4: reboot the bootloader and check if the bootloader changed from 1.12 to 1.39
After that we continue, or find another way to flash it back.
Mr Hofs said:
Oke i will give it a try
Download this firmware
1: Rename the file to firmware.zip and copy it to the fastboot folder
2: put the phone in fastboot usb mode/bootloader
3: enter these commands
Fastboot oem RebootRUU
Fastboot flash zip firmware.zip
(maybe needed a second time, watch the outcome of the flash on the pc)
4: reboot the bootloader and check if the bootloader changed from 1.12 to 1.39
After that we continue, or find another way to flash it back.
Click to expand...
Click to collapse
Hi Mr Hofs and thank you for taking the time to help me, when i run the commands i get the below:
Code:
c:\Fastboot>Fastboot oem RebootRUU
... FAILED (unknown status code)
finished. total time: 0.001s
c:\Fastboot>Fastboot flash zip firmware.zip
sending 'zip' (12876 KB)... FAILED (unknown status code)
finished. total time: 0.054s
The "Fastboot devices" comand returns the SN of my device, however the "adb devices does not list anything". Also looking in device manager i can no longer see my device, could that have to do anything with it? should i reinstall the HTC drivers maybe?
Alex_chaingun said:
Hi Mr Hofs and thank you for taking the time to help me, when i run the commands i get the below:
Code:
c:\Fastboot>Fastboot oem RebootRUU
... FAILED (unknown status code)
finished. total time: 0.001s
c:\Fastboot>Fastboot flash zip firmware.zip
sending 'zip' (12876 KB)... FAILED (unknown status code)
finished. total time: 0.054s
The "Fastboot devices" comand returns the SN of my device, however the "adb devices does not list anything". Also looking in device manager i can no longer see my device, could that have to do anything with it? should i reinstall the HTC drivers maybe?
Click to expand...
Click to collapse
no thats oke, in the bootloader you can only use fastboot commands. But try again but this time use :
Fastboot oem rebootRUU (watch the capitals)
it has worked this time! waiting at a HTC black screen now and after that i'll try the command to update the firmware.
LE: Should the phone take that long after the RebootRUU command? been sitting at the htc screen for 5 minutes now
Yes please
Edit :
Once its on 1.39 you keep the phone in the bootloader and execute this ruu.exe from the pc with admin rights (select with right mouse button and run as administrator)
http://www.androidruu.com/getdownlo...Radio_5.1204.162.29_release_302015_signed.exe
Once the phone hits that screen with the HTC logo you do the firmware flash command !
I'm beginning to think that it's stuck as it has been sitting at the black HTC screen for 10 minutes now. Also the back of the phone is quite warm (near the camera). Could it represent a hardware problem maybe?
Refresh.....edited my post. You have to flash the firmware when the phone is on that screen !
Mr Hofs said:
Refresh.....edited my post. You have to flash the firmware when the phone is on that screen !
Click to expand...
Click to collapse
Sorry one of those PICNIC moments on my part ran the command, it's doing it now. Will let you know how i get on shortly.
LE : Does it need to reboot itself automatically after the bar has filled? looking at a full bar currently.
No reboot it please
Fastboot reboot bootloader
Or hold the power button and the volume - button to enter the bootloader again
Did the flash on the pc say OKEY ?
I have rebooted, the H-boot now reads 1.39.0000 i think that's what we wanted, but the Radio also changed to 5.1204.162.29. I am waiting now for the RUU to finish downloading.
Okey, that's cool. Well to give some background info on the meanwhile.... The XE variant you have seems to be a HTC developers phone. Hard and sometimes unable to officially update via HTC ota. This is a way that might work. If the ruu does not work we can always install a custom rom.
I also don't know when the ruu is flashed successfully and the phone boots again if it will find any further updates to android 4.2.2 sense 5. But that's a thing we will address later
problem solved
You sir are a genius and a blessing that has managed to explain the steps so well and with patience that i managed to bring my phone back to life just when i was about to give up. I cannot express my gratitude for the help that you have provided, if you ever find yourself in Romania please contact me via my email(sent you one on gmail) and i will happily meet with you and have some drinks!!
As far as the updates go i will never install one on this phone again, as i have just noticed when i was setting it up that there was a red warning saying that this is a test device and it will send feedback automatically to HTC and i cannot turn off that feature. Does that mean that it might be limited in some regards if it's a developers phone (maybe hardware or does not have all the features)?
Again cannot thank you enough! problem solved by this awesome man.:highfive:
Ah awesome news. Well if you ever want to go up to sense 5 just let me know
Cheers ! And have fun with the hox
Mr Hofs said:
Ah awesome news. Well if you ever want to go up to sense 5 just let me know
Cheers ! And have fun with the hox
Click to expand...
Click to collapse
I am fine with a "living" phone no more messing around, thanks again Mr. Hofs!
Softbrick - Similar Issue
While installing CM10.2, i had flashed cm10.2 and the gapps. however forgot to flash boot.img through fastboot.
Now, none of the systems around me are recognizing my phone nor he drivers are getting installed. Upon reboot screen gets stuck on CM boot logo. Unluckily not expecting any of this, i havn't made a backup as well. Please help. Thanks in advance.

[Q] HTC One Verizon Bricked Badly! PLease Help

okay so My HTC One M7 Verizon which I use in India on a Vodafone Network is stuck on the bootloader menu.
3 weeks ago i rooted my phone and installed a custom ROM but it got stuckk in wiping the cache but somehow i fixed it and installed a stock ROM (4.4.2) after doing all this my phone worked fine for 2 weeks and suddenly early morning it went off and dint boot-up and now its stuck in the bootloader menu, and no recovery, so i tried to get it back to Stock so as i started i got my Phone into re-lock state and made it S-ON but now it doesnt accept the RUU and even The OEM RUU BOOT fails! and if i try to UNLOCK AND S-OFF again it says no device found.
Phone state
***TAMPERED***
***RELOCKED***
m7_WLV PVT SHIP S-ON RH
HBOOT-1.54.0000
RADIO 1.12.42.0731
OpenDSP v31.120.274.0617
OS- 1.10.605.8 (1.10.605.10)
so now it only boots up into the bootload
when i try to unlock+S-OFF it says so devices found
and when i try to flash the RUU and type 'oem rebootRUU' this shows up
"bootloader) Start Verify: 3
(bootloader) SD: write failed in CMD25.
OKAY [ 1.492s]
rebooting...
finished. total time: 1.582s" (phone goes off!)
PLEASE HELP!
architsheth said:
okay so My HTC One M7 Verizon which I use in India on a Vodafone Network is stuck on the bootloader menu.
3 weeks ago i rooted my phone and installed a custom ROM but it got stuckk in wiping the cache but somehow i fixed it and installed a stock ROM (4.4.2) after doing all this my phone worked fine for 2 weeks and suddenly early morning it went off and dint boot-up and now its stuck in the bootloader menu, and no recovery, so i tried to get it back to Stock so as i started i got my Phone into re-lock state and made it S-ON but now it doesnt accept the RUU and even The OEM RUU BOOT fails! and if i try to UNLOCK AND S-OFF again it says no device found.
Phone state
***TAMPERED***
***RELOCKED***
m7_WLV PVT SHIP S-ON RH
HBOOT-1.54.0000
RADIO 1.12.42.0731
OpenDSP v31.120.274.0617
OS- 1.10.605.8 (1.10.605.10)
so now it only boots up into the bootload
when i try to unlock+S-OFF it says so devices found
and when i try to flash the RUU and type 'oem rebootRUU' this shows up
"bootloader) Start Verify: 3
(bootloader) SD: write failed in CMD25.
OKAY [ 1.492s]
rebooting...
finished. total time: 1.582s" (phone goes off!)
PLEASE HELP!
Click to expand...
Click to collapse
Don't ever s on again
The command is "fastboot oem rebootRUU"
Use this ruu... http://click.xda-developers.com/api...TC One | XDA Forum&txt=1.10.605.10 Signed RUU
Try It
First you need to do is s-off it and then flash the ruu that is given in #2 i used the same and i had no problems at all . I am form India as well
Unlock your bootloader later on but soff it first.
https://www.youtube.com/watch?v=e4zBk2m1FPU
architsheth said:
okay so My HTC One M7 Verizon which I use in India on a Vodafone Network is stuck on the bootloader menu.
3 weeks ago i rooted my phone and installed a custom ROM but it got stuckk in wiping the cache but somehow i fixed it and installed a stock ROM (4.4.2) after doing all this my phone worked fine for 2 weeks and suddenly early morning it went off and dint boot-up and now its stuck in the bootloader menu, and no recovery, so i tried to get it back to Stock so as i started i got my Phone into re-lock state and made it S-ON but now it doesnt accept the RUU and even The OEM RUU BOOT fails! and if i try to UNLOCK AND S-OFF again it says no device found.
Phone state
***TAMPERED***
***RELOCKED***
m7_WLV PVT SHIP S-ON RH
HBOOT-1.54.0000
RADIO 1.12.42.0731
OpenDSP v31.120.274.0617
OS- 1.10.605.8 (1.10.605.10)
so now it only boots up into the bootload
when i try to unlock+S-OFF it says so devices found
and when i try to flash the RUU and type 'oem rebootRUU' this shows up
"bootloader) Start Verify: 3
(bootloader) SD: write failed in CMD25.
OKAY [ 1.492s]
rebooting...
finished. total time: 1.582s" (phone goes off!)
PLEASE HELP!
Click to expand...
Click to collapse
Here is how to fix it
Download this RUU file which matches your hboot
http://bit.ly/vzwone10
then put the file in your fastboot / adb directory, and rename it to Rom.zip
Put the device in fastboot mode
(Volume down and power until menu appears, select fastboot using power button)
Connect the device to the computer
Enter the following commands from terminal/command prompt in the fastboot directory, one at a time:
fastboot oem rebootRUU (this puts the device in RUU mode)
fastboot flash zip Rom.zip (rename file to Rom.zip)
It will say that the update did not finish, to flush again, so repeat the above step:
fastboot flash zip Rom.zip
Then when it finishes, type "fastboot reboot"
Enjoy.
PS - NEVER s-on your phone. You do not to be s-on for ANYTHING. But being s-on will stop you from doing pretty much everything. The only reason to EVER revert to S-on is to send your phone in for a warranty replacement.
As soon as you finish those steps, go ahead and use rumrunner for your hboot version to get s-off again. Once you are s-off, you can take all your ota updates to get the newest firmware / stock rom, then flash a custom recovery through fastboot, and flash superuser or a custom rom from your recovery. You NEED s-off though. If you were s-off now this would be a simple fix, just flash firmware / recovery and a rom, but since you are s-on you are going to have to go to the matching stock RUU for your bootloader, and start from scratch. Hope i helped.

Categories

Resources