Database Info

Help me please (noob @ flashing ROMS)

I loaded my Rogers HTC one X with the CyanogenMod 10 - Endeavor Unleashed | 027 | UNIFIED HBOOT. It worked for a bit but is now stuck in the loading screen. I connected it to my PC and put it in fastboot and attempt to reflash the boot img and nothing changes. I have attempted to find an original RUU as mine is corrupted.
I have read the forums and see alot of fixes if you can access the phone to move the files to the SD however I cant get to that point. I am sure this has been answered somewhere but i haven't been able to find it as yet.
This is my first attempt to use a ROM.. The phone was unlocked via HTC dev. I have since read I should have also turned the S-off but I missed that before I flashed the ROM.
Any ideas would be appreciated.
Here is the info from the device.
c:\Android>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.11.0000
(bootloader) version-baseband: 0.18as.32.09.28L
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 1.94.631.3
(bootloader) serialno: HT249W305429
(bootloader) imei: 359691042187149
(bootloader) product: evita
(bootloader) platform: HBOOT-8960
(bootloader) modelid: PJ8310000
(bootloader) cidnum: ROGER001
(bootloader) battery-status: good
(bootloader) battery-voltage: 4200mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: 8d23f0c0
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.076s
c:\Android>
I originally posted this in the wrong forum. I was told not to use the international ROMS. I did try flashing cm-10-20121126-NIGHTLY-evita using the One X One Click v 1.9. When I reboot it it just gives me the CM loading screen.

First, we don't have S-Off yet. Whoever told you that doesn't know what they're talking about.
Flashing international/Tegra3 roms on this phone, as you've learned, won't work. There are certain Tegra3 roms that will hard-brick you, but I've seen people recover from flashing the wrong CM10. If you can still get to the bootloader, you're okay.
It's possible you corrupted your sd card. Try reformatting it.

Drag0nus said:
I loaded my Rogers HTC one X with the CyanogenMod 10 - Endeavor Unleashed | 027 | UNIFIED HBOOT. It worked for a bit but is now stuck in the loading screen. I connected it to my PC and put it in fastboot and attempt to reflash the boot img and nothing changes. I have attempted to find an original RUU as mine is corrupted.
I have read the forums and see alot of fixes if you can access the phone to move the files to the SD however I cant get to that point. I am sure this has been answered somewhere but i haven't been able to find it as yet.
This is my first attempt to use a ROM.. The phone was unlocked via HTC dev. I have since read I should have also turned the S-off but I missed that before I flashed the ROM.
Any ideas would be appreciated.
Here is the info from the device.
c:\Android>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.11.0000
(bootloader) version-baseband: 0.18as.32.09.28L
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 1.94.631.3
(bootloader) serialno: HT249W305429
(bootloader) imei: 359691042187149
(bootloader) product: evita
(bootloader) platform: HBOOT-8960
(bootloader) modelid: PJ8310000
(bootloader) cidnum: ROGER001
(bootloader) battery-status: good
(bootloader) battery-voltage: 4200mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: 8d23f0c0
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.076s
c:\Android>
I originally posted this in the wrong forum. I was told not to use the international ROMS. I did try flashing cm-10-20121126-NIGHTLY-evita using the One X One Click v 1.9. When I reboot it it just gives me the CM loading screen.
Click to expand...
Click to collapse
Also, try to format system and do factory reset using TWRP
While in a directory with ADB, fastboot and TWRP (custom recovery), Do the following command
fastboot boot TWRP.img
Then, in TWRP, go to wipe
Then go toilet pap--- oops
Jk but go to Factory Reset
When it's done, do wipe system
Then, finally install a rom and flash the kernel
Hope I helped!

Tanmaynarang said:
Also, try to format system and do factory reset using TWRP
While in a directory with ADB, fastboot and TWRP (custom recovery), Do the following command
fastboot boot TWRP.img
Then, in TWRP, go to wipe
Then go toilet pap--- oops
Jk but go to Factory Reset
When it's done, do wipe system
Then, finally install a rom and flash the kernel
Hope I helped!
Click to expand...
Click to collapse
Thank you for the idea.
I tried this but it goes to the HTC screen and stops.
Also I am now noticing that my SD is not accessible. I think I did something way wrong when I originally flashed the rom.

Drag0nus said:
Thank you for the idea.
I tried this but it goes to the HTC screen and stops.
Also I am now noticing that my SD is not accessible. I think I did something way wrong when I originally flashed the rom.
Click to expand...
Click to collapse
Did you wipe/factory reset in bootloader? That will completely wipe your sd card so that you have to reformat it.

iElvis said:
Did you wipe/factory reset in bootloader? That will completely wipe your sd card so that you have to reformat it.
Click to expand...
Click to collapse
Yes I did. The thing is I can't access the SD card to format it. when I try to mount the SD from the phone it does nothing either. I am very lost now.

Drag0nus said:
Yes I did. The thing is I can't access the SD card to format it. when I try to mount the SD from the phone it does nothing either. I am very lost now.
Click to expand...
Click to collapse
You need to mount it from your computer.

iElvis said:
You need to mount it from your computer.
Click to expand...
Click to collapse
Ok thanks. Can you point me in the right direction to be able to do so?

Drag0nus said:
Ok thanks. Can you point me in the right direction to be able to do so?
Click to expand...
Click to collapse
Just plug it in and navigate to your phone in Explorer. You should then get a prompt to format it.

iElvis said:
Just plug it in and navigate to your phone in Explorer. You should then get a prompt to format it.
Click to expand...
Click to collapse
That's the thing. I hook it to the PC, it will open sence but it doesnt show in explorer now.

Drag0nus said:
That's the thing. I hook it to the PC, it will open sence but it doesnt show in explorer now.
Click to expand...
Click to collapse
Are you in bootloader? Try a different cable, or different USB port.
Try plugging it in, shutting down, and rebooting to bootloader. Sometimes it takes some effort to get it to show up.

Go to my computer. Right click where it says removable storage .... format.. it WILL erase everything. But hey, at least you Still have a phone right
Sent from my One X using Tapatalk 2

Just run rogers 1.94 ruu

The problem is that the computer does not see it as a storage device because the SD card doesn't show up I have tried multiple computers and multiple cables any suggestions
Sent from my SGH-I747M using xda app-developers app

try this
http://forums.team-nocturnal.com/showthread.php/1050

You are going into TWRP and clicking mount usb storage to get windows to recognize it right?

codeprimate said:
try this
http://forums.team-nocturnal.com/showthread.php/1050
Click to expand...
Click to collapse
Thanks. this worked and I just finished flashing the new ROM and am waiting for it to complete and then I should be golden.

Cannot get into recovery

Hi all
I use HTC One X, but bought some time ago HTC One S, it worked fine for some time, but yesterday restarted and from that point I could not get it back neither to recovery nor ROM anymore. Phone bootloops and I can only get to fastboot.
I've unlocked the bootloader (*** UNLOCKED *** shows on top when in fastboot) and fastboot getvar all returns:
(bootloader) version: 0.5
(bootloader) version-bootloader: 2.15.0000
(bootloader) version-baseband: 1.11.50.05.28
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 3.16.666.9
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno: HT24AW408183
(bootloader) imei: 352103050022322
(bootloader) product: vle
(bootloader) platform: HBOOT-8960
(bootloader) modelid: PJ4011000
(bootloader) cidnum: 11111111
(bootloader) battery-status: good
(bootloader) battery-voltage: 3695mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-64bedd38
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
When I flash recovery (fastboot flash recovery recovery.img and recovery.img is from here (http://forum.xda-developers.com/showthread.php?t=2528113 under Recovery HBOOT 2.15 Users Only ClockworkMod 6.0.4.5), it does flash ok
sending 'recovery' (8106 KB)..
OKAY [ 1.079s]
writing 'recovery'...
OKAY [ 1.856s]
finished. total time: 2.943s
but I still cannot get into recovery (phone restarts to screen with red text (for dev only...) and then restarts and bootloops.
Can anybody please help me with this?
Thanks

I suggest reflashing kernel.
Wysłane z mojego HTC One S przy użyciu Tapatalka

jaco_lbn said:
I suggest reflashing kernel.
Wysłane z mojego HTC One S przy użyciu Tapatalka
Click to expand...
Click to collapse
Thanks, but I even cannot get into recovery

velvel said:
Thanks, but I even cannot get into recovery
Click to expand...
Click to collapse
Hm, really strange behavior, had couple of HTC phones but never seen something like this happening.
I did run RUU (first changed cid and relocked), everything went fine (no errors), but still cannot boot. My experience so far was that if RUU runs fine, you should boot without problem. Thinking more and more that there is some hardware problem, that is causing phone to bootloop.
If anyone has any idea, I would appreciate it a lot.
Thanks

Build me a scenario
velvel said:
Hm, really strange behavior, had couple of HTC phones but never seen something like this happening.
I did run RUU (first changed cid and relocked), everything went fine (no errors), but still cannot boot. My experience so far was that if RUU runs fine, you should boot without problem. Thinking more and more that there is some hardware problem, that is causing phone to bootloop.
If anyone has any idea, I would appreciate it a lot.
Thanks
Click to expand...
Click to collapse
According to your first post, everything seems to be okay. Your drivers are seeing the phone, and the phone is recognizing its hardware.
Which recoveries did you try to flash? (TWRP, CWM)
And which version?
Have you tried to reroot the device and flash a recovery again since running the RUU?
From my experience with running an RUU, you should be able to boot right away. What were the steps you took (in order) before you ran the RUU?
Sorry for all the questions, trying to establish a scenario.
[EDIT] Also, I see that you got the initial recovery from the CM11 ROM page. You didn't happen to flash a ROM that is meant for HBOOT 2.16 did you? I sure hope not. That could be a possibility as to why you can not boot anything.

42freelancer said:
Which recoveries did you try to flash? (TWRP, CWM)
Click to expand...
Click to collapse
I've tried both. fastboot flash recovery imgname would work fine, but I would again finish in bootloop after restart.
And which version?
Click to expand...
Click to collapse
TWRP_2.6.1.0_ville_4.2.2 and latest CWM
Have you tried to reroot the device and flash a recovery again since running the RUU?
Click to expand...
Click to collapse
You mean reunlock, not reroot, right? I've done reunlock so I could flash recovery.
From my experience with running an RUU, you should be able to boot right away. What were the steps you took (in order) before you ran the RUU?
Click to expand...
Click to collapse
I would run:
fastboot erase cache
fastboot reboot-bootloader
and then start RUU.
Sorry for all the questions, trying to establish a scenario.
Click to expand...
Click to collapse
You are welcome and thanks for the help.
[EDIT] Also, I see that you got the initial recovery from the CM11 ROM page. You didn't happen to flash a ROM that is meant for HBOOT 2.16 did you? I sure hope not. That could be a possibility as to why you can not boot anything.
Click to expand...
Click to collapse
No, 2.15 all the time...

velvel said:
I've tried both. fastboot flash recovery imgname would work fine, but I would again finish in bootloop after restart.
TWRP_2.6.1.0_ville_4.2.2 and latest CWM
You mean reunlock, not reroot, right? I've done reunlock so I could flash recovery.
I would run:
fastboot erase cache
fastboot reboot-bootloader
and then start RUU.
You are welcome and thanks for the help.
No, 2.15 all the time...
Click to expand...
Click to collapse
Try getting into bootloader and pushing the kernel this way: fastboot flash boot boot.img
you don't have to be in recovery for this. The phone is s-on right?
[edit] actually your security says it's off.

42freelancer said:
Try getting into bootloader and pushing the kernel this way: fastboot flash boot boot.img
you don't have to be in recovery for this.
Click to expand...
Click to collapse
No, it didn't work, this is something more serious
I've basically tried all I could think of, from doing RUUs (3 of them), flashing boot and recovery images, going 2.15, 2.16, locking/unlocking (obviously) and finally going S-On (ok, might be stupid, but I run out of ideas).
Bottom line is that all of the flashing worked for me, I get no error, but even simple fastboot boot recovery.img brings back the bootloop.
For example:
>fastboot flash recovery openrecovery-twrp-2.6.3.0-ville-selinux.img
sending 'recovery' (8668 KB)...
OKAY [ 1.108s]
writing 'recovery'...
OKAY [ 2.059s]
finished. total time: 3.173s
>fastboot reboot
and if I hold Vol- and select recovery in bootloader I am back to bootloop.
Same thing if I try:
>fastboot boot openrecovery-twrp-2.6.3.0-ville-selinux.img
I just do not understand why I am not getting any error message when flushing and is it possible that there is something wrong with the hardware that causes this behavior...

velvel said:
No, it didn't work, this is something more serious
I've basically tried all I could think of, from doing RUUs (3 of them), flashing boot and recovery images, going 2.15, 2.16, locking/unlocking (obviously) and finally going S-On (ok, might be stupid, but I run out of ideas).
Bottom line is that all of the flashing worked for me, I get no error, but even simple fastboot boot recovery.img brings back the bootloop.
For example:
>fastboot flash recovery openrecovery-twrp-2.6.3.0-ville-selinux.img
sending 'recovery' (8668 KB)...
OKAY [ 1.108s]
writing 'recovery'...
OKAY [ 2.059s]
finished. total time: 3.173s
>fastboot reboot
and if I hold Vol- and select recovery in bootloader I am back to bootloop.
Same thing if I try:
>fastboot boot openrecovery-twrp-2.6.3.0-ville-selinux.img
I just do not understand why I am not getting any error message when flushing and is it possible that there is something wrong with the hardware that causes this behavior...
Click to expand...
Click to collapse
Sounds like you have a soft brick on your hands.
Can you boot the device at all, stock or custom ROM?
Maybe reverting to COMPLETE STOCK and starting over fresh will help?
What was the last thing you did right before you got stuck?

42freelancer said:
Sounds like you have a soft brick on your hands.
Can you boot the device at all, stock or custom ROM?
Maybe reverting to COMPLETE STOCK and starting over fresh will help?
What was the last thing you did right before you got stuck?
Click to expand...
Click to collapse
No, I cannot boot, after RUU that runs fine, phone still bootloops and only thing I can do is go into bootloader.
When you say COMPLETE STOCK, you mean RUU, right?
I was talking on the phone and phone restarted. After that I was able to boot after many tries, after restart, could not boot and than tried RUU etc...

velvel said:
No, I cannot boot, after RUU that runs fine, phone still bootloops and only thing I can do is go into bootloader.
When you say COMPLETE STOCK, you mean RUU, right?
I was talking on the phone and phone restarted. After that I was able to boot after many tries, after restart, could not boot and than tried RUU etc...
Click to expand...
Click to collapse
And here we are. Do you happen to have the old All In One Kit that became obsolete, by hasoon2000? It has the function to flash your recovery back to stock. I found two mirrors on the internet, but because of the rules, I can't post them. But they are accessible through the internets if you use the right keywords.

42freelancer said:
And here we are. Do you happen to have the old All In One Kit that became obsolete? It has the function to flash your recovery back to stock. It's probably floating around the internet somewhere. If you don't I can try to find it.
Click to expand...
Click to collapse
Tried that too, no luck. Looks like I am getting a new paperweight

velvel said:
Tried that too, no luck. Looks like I am getting a new paperweight
Click to expand...
Click to collapse
If you haven't lost all hope, try reading through this and (Return to Stock - http://forum.xda-developers.com/showthread.php?t=2164783) see if you missed anything?
You seem pretty savvy in your HTC ONE S know-how. But it's always good to follow someone else's tutorial just for guidance.

Seems issue with Recovery, bootloop is normal
velvel said:
Hi all
I use HTC One X, but bought some time ago HTC One S, it worked fine for some time, but yesterday restarted and from that point I could not get it back neither to recovery nor ROM anymore. Phone bootloops and I can only get to fastboot.
I've unlocked the bootloader (*** UNLOCKED *** shows on top when in fastboot) and fastboot getvar all returns:
(bootloader) version: 0.5
(bootloader) version-bootloader: 2.15.0000
(bootloader) version-baseband: 1.11.50.05.28
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 3.16.666.9
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno: HT24AW408183
(bootloader) imei: 352103050022322
(bootloader) product: vle
(bootloader) platform: HBOOT-8960
(bootloader) modelid: PJ4011000
(bootloader) cidnum: 11111111
(bootloader) battery-status: good
(bootloader) battery-voltage: 3695mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-64bedd38
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
When I flash recovery (fastboot flash recovery recovery.img and recovery.img is from here (http://forum.xda-developers.com/showthread.php?t=2528113 under Recovery HBOOT 2.15 Users Only ClockworkMod 6.0.4.5), it does flash ok
sending 'recovery' (8106 KB)..
OKAY [ 1.079s]
writing 'recovery'...
OKAY [ 1.856s]
finished. total time: 2.943s
but I still cannot get into recovery (phone restarts to screen with red text (for dev only...) and then restarts and bootloops.
Can anybody please help me with this?
Thanks
Click to expand...
Click to collapse
Hi,
Bootloop is normal for ROM geeks.
In your case, it seems your phone has issue with version of Recovery. I had this issue too and found correct Recovery @ http://techerrata.com/browse/twrp2/ville ....
You can give a try..:fingers-crossed::fingers-crossed::fingers-crossed:

velvel said:
Hi all
I use HTC One X, but bought some time ago HTC One S, it worked fine for some time, but yesterday restarted and from that point I could not get it back neither to recovery nor ROM anymore. Phone bootloops and I can only get to fastboot.
I've unlocked the bootloader (*** UNLOCKED *** shows on top when in fastboot) and fastboot getvar all returns:
(bootloader) version: 0.5
(bootloader) version-bootloader: 2.15.0000
(bootloader) version-baseband: 1.11.50.05.28
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 3.16.666.9
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno: HT24AW408183
(bootloader) imei: 352103050022322
(bootloader) product: vle
(bootloader) platform: HBOOT-8960
(bootloader) modelid: PJ4011000
(bootloader) cidnum: 11111111
(bootloader) battery-status: good
(bootloader) battery-voltage: 3695mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-64bedd38
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
When I flash recovery (fastboot flash recovery recovery.img and recovery.img is from here (http://forum.xda-developers.com/showthread.php?t=2528113 under Recovery HBOOT 2.15 Users Only ClockworkMod 6.0.4.5), it does flash ok
sending 'recovery' (8106 KB)..
OKAY [ 1.079s]
writing 'recovery'...
OKAY [ 1.856s]
finished. total time: 2.943s
but I still cannot get into recovery (phone restarts to screen with red text (for dev only...) and then restarts and bootloops.
Can anybody please help me with this?
Thanks
Click to expand...
Click to collapse
Did you check the fast boot option in the powermenue under settings? If its check it will happen like ur problem.

velvel said:
No, I cannot boot, after RUU that runs fine, phone still bootloops and only thing I can do is go into bootloader.
When you say COMPLETE STOCK, you mean RUU, right?
I was talking on the phone and phone restarted. After that I was able to boot after many tries, after restart, could not boot and than tried RUU etc...
Click to expand...
Click to collapse
Have you tried this? :
--> flash STOCK recovery via fastboot or toolkit
--> Boot to bootloader --> Factory Reset(Userdata) / Clear Stotage (SD-card) (these commands only work with STOCK recovery)

Before I got the same problem, so in Bootloader I did Factory Reset and then flash the Recovery TWRP 2.6.3.0. Now it works

I just broke the whole phone..

Hello! Before you guys flame me with messages of how much dumb I am or anything similar - don't bother, i already know it and i regret it...
So... I have AT&T HTC One X, with Hboot 2.14, CID CWS__01 which i just destroyed as much as i could >.> Let me reproduce things i've tried..
First of i changed my CID to 11111111 and unlocked the bootloader - took me an hour, but i did it and it was working...
I've installed recovery, even rooted the ROM... But that wasn't enough - i wanted to install ParanoidAndroid ( and i didn't read that it needs S-OFF, realized that just after i installed it and rebooted the phone )..
So after a reboot, the white HTC logo it just went black screen and nothing else... So i've began to look up on forums if someone else had this kind of a problem...
Then i tried another 2 ROM's, which worked as well as PA - just black screen...
So i thought - maybe i'll do everything from scratch ? Why not, I changed CID back to stock, wiped everything etc. and locked the bootloader....
But now I've got a weird problem - i can't change CID with "fastboot oem writecid" - it returned me error
(bootloader) elite_init_sd, SD card already power on
(bootloader) sdhw_7xxx_open: id=0
(bootloader) [SD_HW_ERR] SD: No device attached
(bootloader) 902910 902E20
FAILED (status read failed (No such file or directory))
finished. total time: 1.282s
Click to expand...
Click to collapse
So now i have no access to recovery, so i can't even do anything to the storage, the phone doesn't boot up, tried RUU for ATT version ( RUU_Evita_UL_ATT_US_1.44.502.1_Radio_0.15.3201.09_release_249105 - i guess its for HBoot 1.44, not 2.14 >.> ) it just showed me an error that it couldn't send data to the phone and i should check my connection to the phone ( drivers are installed and working fine )
I've also tried fastbooting the OTA zip to the phone - well, the phone is on S-ON and it just declines any zip that i try to flash
Also i lost connection to ADB - its impossible to connect to it while phone is in bootloader, right? : /
So i'm left with empty phone without any rom, recovery - anything...
Is there any way of fixing it ? Its 5th hour where i just sit and try to look up for any information, but I just can't find anything...
I guess i just hard bricked the phone and i can try to play some volleyball with it >.>

Your mistake was thinking that you needed s-off to flash the ROM(s), you don't, all you needed to do was flash the boot.img via fastboot after flashing the ROM with your recovery. There's an Evita FAQ thread which contains this information stickied at the top of the q&a section you've posted this thread in . This is in no way intended to flame you, just show you the catalyst point for this mayhem.
Anyway, what is your current CID? Check it with this command:
Code:
fastboot oem readcid
You must be connected in fastboot mode (bootloader) in order for fastboot commands to work (and in answer to your question, no, adb does not work in fastboot mode, only in Android and in recovery).
Transmitted via Bacon

thanks for Your reply : )
My current CID is CWS__001. Im posting the whole information from fastboot
(bootloader) version: 0.5
(bootloader) version-bootloader: 2.14.0000
(bootloader) version-baseband: 0.24p.32.09.06
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: HT28GW304238
(bootloader) imei: xxxxxxxxxxxxxxx
(bootloader) product: evita
(bootloader) platform: HBOOT-8960
(bootloader) modelid: PJ8310000
(bootloader) cidnum: CWS__001
(bootloader) battery-status: low
(bootloader) battery-voltage: 3403mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-97c9a06e
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.094s
Click to expand...
Click to collapse
I should mention that the battery was at ~95% at the time i was trying to flash/do anything.
So, is there any way to make at least recovery working? As for now i flash recovery using fastboot flash, but that does nothing - it says that its done, but when i get into bootloader and check recovery then enter it, it goes to white htc logo and goes back to bootloader >.>
EDIT!!!!!
I managed to get it working! I downloaded RUU_EVITA_UL_JB_45_S_Cingular_US_3.18.502.6_Radio_0.24p.32.09.06_10.130.32.34_release_signed_With_Partial which worked flawlessly and stock ROM just booted up! Jesus christ, thank You internet for providing exact links to the RUU's etc >.> I guess i'll try to not brick the phone again ^^ Thanks for the reply again : )
Topic can be closed now : )

prechcik said:
thanks for Your reply : )
My current CID is CWS__001. Im posting the whole information from fastboot
I should mention that the battery was at ~95% at the time i was trying to flash/do anything.
So, is there any way to make at least recovery working? As for now i flash recovery using fastboot flash, but that does nothing - it says that its done, but when i get into bootloader and check recovery then enter it, it goes to white htc logo and goes back to bootloader >.>
EDIT!!!!!
I managed to get it working! I downloaded RUU_EVITA_UL_JB_45_S_Cingular_US_3.18.502.6_Radio_0.24p.32.09.06_10.130.32.34_release_signed_With_Partial which worked flawlessly and stock ROM just booted up! Jesus christ, thank You internet for providing exact links to the RUU's etc >.> I guess i'll try to not brick the phone again ^^ Thanks for the reply again : )
Topic can be closed now : )
Click to expand...
Click to collapse
Glad to see you're all working now. But you need to edit your IMEI out of your post asap, never post your IMEI publicly.
Transmitted via Bacon

[Q] Rogers HTC One X help with customer recovery issue...

Pretty sure I effed up... Before reading further please know I am a very novice Android user, but am great at following directions.
In an attempt to install a custom ROM on my phone I'm having some serious issues getting it to work. I was able to unlock the bootloader on my device quite easily but after attempting to install TWRP the device boots to a black screen when trying to load the recovery. I know the phone is on because I have to press and hold power for a while before I can get back into the actual system. I figured I'd try installing CWM but it does the same thing. I installed the ROM Manager app as suggested by another site but it really is of no help to me without my phone being rooted, which it is not... yet. The app does show that both TWRP and CWM are installed but gets an error flashing CWM and if i try to set it to use the outdated version of CWM or TWRP it says that it's configured to use the existing recovery installation and makes no difference trying to load the recovery.
Phone info: (Let me know if you need anything not listed.)
Android Version: 4.1.1
HTC Sense: 4+
Software#: 3.17.631.3
HTC SDK API leve: 4.63
Build#: 3.17.631.3
Kernel version: 3.4.0-g240d4d5
I'm at a loss for what to do to either get a working custom recovery or restore the factory one to working condition, which I can't seem to find online anywhere.
Edit: Grammar.
Edit2: Update - I was able to get TWRP to run and then attempted to install CyanogenMod, when it installs it says MD5 file not found but says successfully installed. After rebooting to system it just gets stuck in an endless reboot cycle. Ideas / Suggestions?

If it's Rogers it isn't a one x. It's a one xl so you are in the wrong forum which will be why it has all gone wrong

nogotaclue said:
If it's Rogers it isn't a one x. It's a one xl so you are in the wrong forum which will be why it has all gone wrong
Click to expand...
Click to collapse
I've ensured to use Evita for all the guides. I double triple and quadruple checked everything before performing any steps. Posting in the wrong thread doesn't change the situation. Is there a way to move this to the correct thread?
Edit: Also, according to HTC the Evita was a code name used for both the One XL and One X simultaneously. One XL applied specifically to releases in Hong Kong, Australia, Germany, Singapore, and United Kingdom. One X applied to Canada (where I am) and USA.

13rennon said:
I've ensured to use Evita for all the guides. I double triple and quadruple checked everything before performing any steps. Posting in the wrong thread doesn't change the situation. Is there a way to move this to the correct thread?
Edit: Also, according to HTC the Evita was a code name used for both the One XL and One X simultaneously. One XL applied specifically to releases in Hong Kong, Australia, Germany, Singapore, and United Kingdom. One X applied to Canada (where I am) and USA.
Click to expand...
Click to collapse
Reported and will be moved

Boot into fastboot and run the command getvar and post the results. Be sure to block out your imei and serial before posting. This may help XDA members diagnose the problem.
Are you full wiping cache, data, and Dalvik before and after flashing CM?

audit13 said:
Boot into fastboot and run the command getvar and post the results. Be sure to block out your imei and serial before posting. This may help XDA members diagnose the problem.
Are you full wiping cache, data, and Dalvik before and after flashing CM?
Click to expand...
Click to collapse
Yes I was doing a full wipe before flashing, but not after. Situation has changed a bit though... I was working with someone via reddit (Full thread here: reddit.com/r/root/comments/3a4cc2/htc_one_x_root_for_beginner/ ) Long story short: Finally got CyanogenMod installed but let it sit over an hour and just stuck on spinning CM logo. Forced shutdown, booted into TWRP and wouldn't recognize SD or mount (eMMC). Read this can be due to not doing a factory reset, tried to do the factory reset but same deal. Tried to ruin an RUU that matched my info but it failed and with a locked bootloader I cant even get into TWRP, I need to unlock the bootloader and reinstall TWRP after failing an RUU.
Phone details as requested:
(bootloader) version: 0.5
(bootloader) version-bootloader: 2.14.0000
(bootloader) version-baseband: 0.23a.32.09.29
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 3.17.631.3
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: xxxxxxxxxxxx
(bootloader) imei: xxxxxxxxxxxxxxx
(bootloader) product: evita
(bootloader) platform: HBOOT-8960
(bootloader) modelid: PJ8310000
(bootloader) cidnum: ROGER001
(bootloader) battery-status: good
(bootloader) battery-voltage: 4017mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-97c9a06e
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.156s
When I try to RUU I start by relocking the bootloader with "fastboot oem lock" and then I run "fastboot erase cache" then "fastboot oem rebootRUU" then "fastboot flash zip RUU.zip" when it's on the black screen with silver HTC logo. I get this:
c:\Android>fastboot flash zip RUU.zip
sending 'zip' (650005 KB)...
OKAY [ 25.324s]
writing 'zip'...
(bootloader) signature checking...
FAILED (remote: 12 signature verify fail)
finished. total time: 97.643s
The RUU file I'm using is OTA_EVITA_UL_JB_45_S_Rogers_WWE_3.17.631.2_0.23a.32.09.29_10.128.32.34a_release_299850qstr7rxdbfuofl6j.zip I've read they can sometimes give odd errors so I ran it a second time as suggested, same error running a second time. If I try to boot after this it boots to the white HTC quietly brilliant screen.

I see you have s-on and you do not have super CID.
With s-on, I think you have to flash the boot.img file for the phone to boot.
Easiest way to solve the problem may be to get s-off and supercid.
This is what my Rogers HTC One X says:
version: 0.5
version-bootloader: 2.14.0000
version-baseband: 0.23a.32.09.29
version-cpld: None
version-microp: None
version-main: 3.17.707.1
version-misc: PVT SHIP S-OFF
serialno: HT
imei: 3596
product: evita
platform: HBOOT-8960
modelid: PJ8310000
cidnum: 11111111
battery-status: good
battery-voltage: 4081mV
partition-layout: Generic
security: off
build-mode: SHIP
boot-mode: FASTBOOT
commitno-bootloader: dirty-97c9a0
hbootpreupdate: 11
gencheckpt: 0
all: Done!

HTC U11 please help!!!!

First to admit I did something stupid. I am looking for anyone to help me.
Long story short I think I have locked my bootloader. I dont know if i have the stock bootloader or twrp.
C:\adb>fastboot getvar all
< waiting for device >
(bootloader) kernel: lk
(bootloader) product: htc_ocnwhl
(bootloader) version: 1.0
(bootloader) max-download-size: 1560800000
(bootloader) slot-count: 0
(bootloader) current-slot:
(bootloader) version-main: 2.31.617.2
(bootloader) boot-mode: download
(bootloader) version-baseband: 8998-002772-1711021119
(bootloader) version-bootloader: 1.0.0.0000
(bootloader) mid: 2PZC50000
all:
finished. total time: 0.005s
I cant get into the twrp bootloader menu and I tried to use the RRU from htc to reload my phone. I get a 155 error. I tried to unlock the bootloader again with the htc ulock_code.bin error message
sending 'unlocktoken' (0 KB)...
OKAY [ 1.001s]
writing 'unlocktoken'...
(bootloader) flash unlocktoken
(bootloader) [KillSwitch] : /dev/block/bootdevice/by-name/frp
(bootloader) [KillSwitch] Last Byte is 0X01, enable unlock
FAILED (remote: UnlockToken Verify Fail!!)
finished. total time: 1.199s
I am at a loss on what to do. Am I screwed? I am within the htc 30 day window but dont think they will accept my phone.

skinny1439 said:
First to admit I did something stupid. I am looking for anyone to help me.
Long story short I think I have locked my bootloader. I dont know if i have the stock bootloader or twrp.
C:\adb>fastboot getvar all
< waiting for device >
(bootloader) kernel: lk
(bootloader) product: htc_ocnwhl
(bootloader) version: 1.0
(bootloader) max-download-size: 1560800000
(bootloader) serialno: FA79G0500641
(bootloader) slot-count: 0
(bootloader) current-slot:
(bootloader) imei: 358182081003810
(bootloader) version-main: 2.31.617.2
(bootloader) boot-mode: download
(bootloader) version-baseband: 8998-002772-1711021119
(bootloader) version-bootloader: 1.0.0.0000
(bootloader) mid: 2PZC50000
(bootloader) cid: BS_US001
all:
finished. total time: 0.005s
I cant get into the twrp bootloader menu and I tried to use the RRU from htc to reload my phone. I get a 155 error. I tried to unlock the bootloader again with the htc ulock_code.bin error message
sending 'unlocktoken' (0 KB)...
OKAY [ 1.001s]
writing 'unlocktoken'...
(bootloader) flash unlocktoken
(bootloader) [KillSwitch] : /dev/block/bootdevice/by-name/frp
(bootloader) [KillSwitch] Last Byte is 0X01, enable unlock
FAILED (remote: UnlockToken Verify Fail!!)
finished. total time: 1.199s
I am at a loss on what to do. Am I screwed? I am within the htc 30 day window but dont think they will accept my phone.
Click to expand...
Click to collapse
Delete your SN and Imei.
Wysłane z mojego HTC U11 przy użyciu Tapatalka

skinny1439 said:
First to admit I did something stupid. I am looking for anyone to help me.
Long story short I think I have locked my bootloader. I dont know if i have the stock bootloader or twrp.
C:\adb>fastboot getvar all
< waiting for device >
(bootloader) kernel: lk
(bootloader) product: htc_ocnwhl
(bootloader) version: 1.0
(bootloader) max-download-size: 1560800000
(bootloader) slot-count: 0
(bootloader) current-slot:
(bootloader) version-main: 2.31.617.2
(bootloader) boot-mode: download
(bootloader) version-baseband: 8998-002772-1711021119
(bootloader) version-bootloader: 1.0.0.0000
(bootloader) mid: 2PZC50000
all:
finished. total time: 0.005s
I cant get into the twrp bootloader menu and I tried to use the RRU from htc to reload my phone. I get a 155 error. I tried to unlock the bootloader again with the htc ulock_code.bin error message
sending 'unlocktoken' (0 KB)...
OKAY [ 1.001s]
writing 'unlocktoken'...
(bootloader) flash unlocktoken
(bootloader) [KillSwitch] : /dev/block/bootdevice/by-name/frp
(bootloader) [KillSwitch] Last Byte is 0X01, enable unlock
FAILED (remote: UnlockToken Verify Fail!!)
finished. total time: 1.199s
I am at a loss on what to do. Am I screwed? I am within the htc 30 day window but dont think they will accept my phone.
Click to expand...
Click to collapse
Skip again the bootloader unlocking procedure via htcdev
HTC U11 & Tapatalk

linar10 said:
Skip again the bootloader unlocking procedure via htcdev
Delete imei and serialno
HTC U11 & Tapatalk
Click to expand...
Click to collapse
Thanks I was able to unlock the bootloader via the htc dev. I just had to redownload the unlock key.

HTC u11 fails to boot.
skinny1439 said:
Thanks I was able to unlock the bootloader via the htc dev. I just had to redownload the unlock key.
Click to expand...
Click to collapse
I have a new problem.
I will start at the beginning. I was running stock htc oreo. I really wanted to install viperu 1.7. I assumed that I needed to reinstall nougat. I attemped to use the htc ruu to roll back. This failed. I booted into twrp and performed a wipe and restore to a known good nougat backup. When I rebooted the device started to boot gets past the htc logo and the shuts off. Thinking that something failed I rebooted into twrp and attempted to reinstall a stock zip. This fails to install. I wiped again and installed viperu 1.7 everything installs properly per the viper install guide. When the phone reboots it starts to install the apps. It finishes but shuts off. I connected it to a charger and booted the phone and attempted to boot but shuts off.
Can someone please tell me what I have done wrong and how to fix it.
thanks in advance.

Without s-off, the older ruu will not work. Probably older rom on newer firmware may not work. Download stock backup 2.xx.xxx.x and restore in twrp and do not forget full wipe before restoring backup
HTC U11 & Tapatalk

linar10 said:
Without s-off, the older ruu will not work. Probably older rom on newer firmware may not work. Download stock backup 2.xx.xxx.x and restore in twrp and do not forget full wipe before restoring backup
HTC U11 & Tapatalk
Click to expand...
Click to collapse
Do you have a stock backup 2.xx.xxx.x or know where I can get one. I looked online but they dont have 2.x on the list.
My phone is 2PZC50000 BS_US001 WHL (Single SIM) US Unlocked.

RUU and backup
https://forum.xda-developers.com/showthread.php?p=74694695
HTC U11 & Tapatalk

IT works again!!
linar10 said:
RUU and backup
https://forum.xda-developers.com/showthread.php?p=74694695
HTC U11 & Tapatalk
Click to expand...
Click to collapse
You saved me. I am extremely grateful of your knowledge. I thought I flushed 700 buck down the drain.
Whats the best way to revert back to nougat so I can flash to viperu 1.7. Right now I am on 2.31.617.2 from the backup you sent me to in the link. I do need to root the phone but have not attempted yet. I was planning to root the phone at the same time as installing viperu. Much thanks again.

skinny1439 said:
You saved me. I am extremely grateful of your knowledge. I thought I flushed 700 buck down the drain.
Whats the best way to revert back to nougat so I can flash to viperu 1.7. Right now I am on 2.31.617.2 from the backup you sent me to in the link. I do need to root the phone but have not attempted yet. I was planning to root the phone at the same time as installing viperu. Much thanks again.
Click to expand...
Click to collapse
Can't roll back to 7.1.1 yet. You need to be S-Off and Sunshine isn't fully working on Oreo at this time.
But there is a ViperU Oreo Rom available now. If you want, to just flash it and sick with 8.0.

linar10 said:
RUU and backup
https://forum.xda-developers.com/showthread.php?p=74694695
HTC U11 & Tapatalk
Click to expand...
Click to collapse
You're the man.

henslo said:
Can't roll back to 7.1.1 yet. You need to be S-Off and Sunshine isn't fully working on Oreo at this time.
But there is a ViperU Oreo Rom available now. If you want, to just flash it and sick with 8.0.
Click to expand...
Click to collapse
Thanks for all your help. I really appreciate it!

skinny1439 said:
Thanks for all your help. I really appreciate it!
Click to expand...
Click to collapse
The viper rom for oreo doesn't really work right yet and they're working on it. I'm using stock with magisk beta 14.5. Substratum works a bit too.