Develop Bugs

Computer won't connect to phone with updated drivers.

So yeah I think I really screwed the pooch on this one.
Here's what's going on.
-My stupid self tried to flash CM10 with a HBOOT v 1.14. Yeah... save it. I know.
-Now I've gotten so far into this thing that my computer won't recognize my phone in order to utilize fastboot to total wipe and retry to run the RUU.
-Computer has been updated with current drivers. I can get into bootloader, but anything I try after that is unable to be done. Cannot get into recovery, if it's even still there. I tried to reflash TWRP, unsuccessfully. When I try to even boot into recovery, it gets stuck on HTC's boot splash screen.
CID: 1111111
HBOOT: 1.14
Relocked
I am totally lost on this. I just want to get it back working ASAP.

do you have a nandroid backup?

robchongke said:
do you have a nandroid backup?
Click to expand...
Click to collapse
I don't. My dumbass self didn't make one.
And anytime I use the toolkit, to do ANYTHING, *device not found*. So i've royally screwed something up. Even after getting all the drivers. I think.
More info: version: 0.5
version-bootloader: 1.14.0002
version-baseband: 0.19as.32.09.11_
version-cpld: None
version-microp: None
version-main:
version-misc: PVT SHIP S-ON
serialno: HT29TW302342
imei: 359691048634839
product: evita
platform: HBOOT-8960
modelid: PJ8310000
cidnum: 11111111
battery-status: good
battery-voltage: 4107mV
partition-layout: Generic
security: on
build-mode: SHIP
boot-mode: FASTBOOT
commitno-bootloader: 1a7fdca3
hbootpreupdate: 11
gencheckpt: 0

KMiracle1984 said:
I don't. My dumbass self didn't make one.
Click to expand...
Click to collapse
if TWRP dont work maybe try CWM.
maybe you flash the wrong custom rom. this thread is for endeavour(international version) yours is evita, that's htc one xl.

robchongke said:
if TWRP dont work maybe try CWM.
Click to expand...
Click to collapse
I would, if I could get it to respond. I get notihing in either fastboot or through the toolkit.
The computer does it's beeping when you connect, but nothing happens.

Attempting to force a boot.img to the phone....
sending 'boot' (5248 KB)...
OKAY [ 0.889s]
writing 'boot'...
(bootloader) signature checking...
FAILED (remote: signature verify fail)
finished. total time: 1.274s

You are in the wrong forum mate, go to the HTC one XL forum. This is all for the endevouru !

Blaine999 said:
Click to expand...
Click to collapse
What's the matter mate.....trying to gather posts or what ?
Please bring something to the table other than a rolleyes !!! :thumbdown:
This is the second thread already ......

[Q] HOX stuck on slash screen

Hi,
It goes to show that a little knowledge is a dangerous thing!!!
I flashed my phone with Team Viper 2.6 (I think) and all was working fine ubtil I tried another Rom, can't remember which one and the phone will not boot past the HTC white screen.
After many hours of being unsuccessful, I sent the phone back to HTC for repair and after a few days they said that the mainboard needed replacing for almost £200 !!! So i decided against that and got the phone back.
I can get into HBoot and Fasboot USB, also can get into TWRP, so tried to reload Team Viper, as that is the only backup I had. It went through the installation process OK, but still won't get past the flash screen.
Here are some details of the phone:
*****UNLOCKED*****
Endeavoru PUT SHIP S-ON RL
HBOOT-1.39.0000
CPLD-None
MICROP-None
Radio-5.1204.162.29
eMMC-bootable: disabled
CPU-bootable: disabled
HW Secure boot: enabled
MODEM PATH: OFF
Dec 17 2012, 13:59:37
Using Hassoons Tool I got the following:-
bootloader) version: 0.5a
(bootloader) version-bootloader: 1.39.0000
(bootloader) version-baseband: 5.1204.162.29
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 3.14.401.31
(bootloader) serialno: Removed for security
(bootloader) imei: 353043057835673
(bootloader) product: endeavoru
(bootloader) platform: HBOOT-T30S
(bootloader) modelid: PJ4610000
(bootloader) cidnum: HTC__001
(bootloader) battery-status: good
(bootloader) battery-voltage: 3758mV
(bootloader) devpower: 37
(bootloader) partition-layout: None
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: None
(bootloader) hbootpreupdate: 2
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.876s
Sorry for the detailed post, but I wanted provide as much info as possible.
Now my question is: CAN SOMEONE PROVIDE A VERY SIMPLISTIC PROCEDURE TO RESTORE TO STOCK?
I feel the that phone is not "bricked" but maybe I'm wrong.
Your help and expertise would be so much appreciated for this noobie!!:fingers-crossed:

ovation99 said:
Hi,
It goes to show that a little knowledge is a dangerous thing!!!
I flashed my phone with Team Viper 2.6 (I think) and all was working fine ubtil I tried another Rom, can't remember which one and the phone will not boot past the HTC white screen.
After many hours of being unsuccessful, I sent the phone back to HTC for repair and after a few days they said that the mainboard needed replacing for almost £200 !!! So i decided against that and got the phone back.
I can get into HBoot and Fasboot USB, also can get into TWRP, so tried to reload Team Viper, as that is the only backup I had. It went through the installation process OK, but still won't get past the flash screen.
Here are some details of the phone:
*****UNLOCKED*****
Endeavoru PUT SHIP S-ON RL
HBOOT-1.39.0000
CPLD-None
MICROP-None
Radio-5.1204.162.29
eMMC-bootable: disabled
CPU-bootable: disabled
HW Secure boot: enabled
MODEM PATH: OFF
Dec 17 2012, 13:59:37
Using Hassoons Tool I got the following:-
bootloader) version: 0.5a
(bootloader) version-bootloader: 1.39.0000
(bootloader) version-baseband: 5.1204.162.29
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 3.14.401.31
(bootloader) serialno: Removed for security
(bootloader) imei: 353043057835673
(bootloader) product: endeavoru
(bootloader) platform: HBOOT-T30S
(bootloader) modelid: PJ4610000
(bootloader) cidnum: HTC__001
(bootloader) battery-status: good
(bootloader) battery-voltage: 3758mV
(bootloader) devpower: 37
(bootloader) partition-layout: None
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: None
(bootloader) hbootpreupdate: 2
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.876s
Sorry for the detailed post, but I wanted provide as much info as possible.
Now my question is: CAN SOMEONE PROVIDE A VERY SIMPLISTIC PROCEDURE TO RESTORE TO STOCK?
I feel the that phone is not "bricked" but maybe I'm wrong.
Your help and expertise would be so much appreciated for this noobie!!:fingers-crossed:
Click to expand...
Click to collapse
You probably just need to flash the boot.img from the rom zip...extract it to your fastboot folder and then execute " fastboot flash boot boot.img" and then "fastboot erase cache" using cmd (command prompt) and then reboot
Sent from my HTC One X using xda app-developers app

Sadman Khan said:
You probably just need to flash the boot.img from the rom zip...extract it to your fastboot folder and then execute " fastboot flash boot boot.img" and then "fastboot erase cache" using cmd (command prompt) and then reboot
Sent from my HTC One X using xda app-developers app
Click to expand...
Click to collapse
Thanks for the reply, but where would I get the boot.img from?
Would that be from the Team Viper ROM, or do I download from elsewhere?

Look in the flashable zip. Simply extract the boot.img from the zip:thumbup:
Sent from my HTC One X using xda app-developers app

ovation99 said:
Thanks for the reply, but where would I get the boot.img from?
Would that be from the Team Viper ROM, or do I download from elsewhere?
Click to expand...
Click to collapse
U have a backup of viper rom right? And twrp recovery? So there is a boot.emmc.win file in twrp folder on your sd card.. Flash this boot file from fastboot( b4 or after restoring the backup)

ovation99 said:
Thanks for the reply, but where would I get the boot.img from?
Would that be from the Team Viper ROM, or do I download from elsewhere?
Click to expand...
Click to collapse
You will find it in the rom zip file or you can download the viper kernel from the rom's thread..either of them will work for you.. good luck mate
Sent from my HTC One X using xda app-developers app

Sadman Khan said:
You will find it in the rom zip file or you can download the viper kernel from the rom's thread..either of them will work for you.. good luck mate
Sent from my HTC One X using xda app-developers app
Click to expand...
Click to collapse
Thanks to all you guys for your help, but did as you suggested and still no further forward.
Is there a ROM that will return my phone to stock complete with kernel, boot.img etc, that will re-install everything, wike a Windows re-installation. Or am I asking too much here?
I am losing faith in this and I can see it being dumped in the trash before long.

Flash this recovery
http://db.tt/SPXdFfPw
Rename it to recovery.img and flash it :
Fastboot flash recovery recovery.img
Fastboot erase cache
Then flash the boot.img from the viper x 3.7.5 (open the rom.zip with 7zip and copy the file)
Fastboot flash boot boot.img
Fastboot erase cache
Then go into recovery and wipe all :
Factory reset
Wipe cache partition
Mounts & storage - format cache,data,system
Advanced - wipe dalvik cache
Then install the viper x rom.zip and follow instructions.
When you get a question about a kernel....choose viper x delivered !
Done

HOX stuck on splash screen
Mr Hofs said:
Flash this recovery
Rename it to recovery.img and flash it :
Fastboot flash recovery recovery.img
Fastboot erase cache
Then flash the boot.img from the viper x 3.7.5 (open the rom.zip with 7zip and copy the file)
Fastboot flash boot boot.img
Fastboot erase cache
Then go into recovery and wipe all :
Factory reset
Wipe cache partition
Mounts & storage - format cache,data,system
Advanced - wipe dalvik cache
Then install the viper x rom.zip and follow instructions.
When you get a question about a kernel....choose viper x delivered !
Done
Click to expand...
Click to collapse
Many thanks for your detailed and simple instructions.
Howerver, I am having trouble finding the Viper X 3.7.5 ROM, could you post a link for download?
Again, many many thanks:fingers-crossed:

http://forum.xda-developers.com/showthread.php?t=2087443
Here you go

Mr Hofs said:
http://forum.xda-developers.com/showthread.php?t=2087443
Here you go
Click to expand...
Click to collapse
Mr Hofs, many thanks for the links. I downloaded 3.7.4 and the update 3.7.5.
That was the good bit......I tried to push the ROM using adb in command mode, but I couldn't get it to recognise the phone.
I thought I maybe able to drop the files onto the sd card via Windows, but althought the phone is recognised in Device Manager, it doesn't show up in Windows Explore.
I am sorry that all your help and advice has been wasted, maybe it will help others whose phone isn't as sick as mine.
I may have another go tomorrow, but it's looking like it's headed for that great waste bin in the sky.:crying:

If you want to copy the rom to the phone you go into the recovery and then to
Mounts & storage - mount as mass storage (last option in that list)
Its now a usb diskdrive and windows will recognize it (if its not, wait long enough like a minute or so. It can take a while)
Then copy the stuff you need.

Mr Hofs, Many thanks for your help.
I downloaded 3.7.4 and update 3.7.5 and tried adb push and sideload but my device wasn't recognised, although W8 could see it in Device Manager.
I will give it one more go today and if that doesn't work, it's that great trash bin in the skt.
Again many thanks for your help.:crying:

Like i said you don't need to sideload or adb anything, just do as above and you can copy it normally

Mr Hofs said:
Like i said you don't need to sideload or adb anything, just do as above and you can copy it normally
Click to expand...
Click to collapse
Mr Hofs, YOU ARE THE MAN !!!
I finally got it working and thereby saving me almost £200 for a HTC repair. Robbin' barst***s !!
I cannot thank you enough for your help and perseverence with a newbie.
I have printed your instructions for future reference. It's great to get help from someone who really knows what they're talking about.
Thank You, Thank You, Thank You. :good::good::good:

Very good !!!
CASE CLOSED !

Mr Hofs said:
Very good !!!
CASE CLOSED !
Click to expand...
Click to collapse
Mr Hofs,
Just one last question.... is there a way to get back to the Viper default settings, colours etc, without re-installing the ROM?

What do you mean exactly with colours and stuff, did you flash a theme ?

Mr Hofs said:
What do you mean exactly with colours and stuff, did you flash a theme ?
Click to expand...
Click to collapse
Yes I did ! I used your dark and yellow theme, but the trouble is now that I can't read texts and the normal (HTC) settings are all in yellow and very difficult to read.
Should I do a complete install of Viper again?

Lol did you picked the yellow theme on the skin picker ?

[Q] HTC One X: Maybe bricked phone, stays in Bootloader

Hello everyone,
I might have bricked my HTC One X while preparing for a custom rom. A year ago I flashed a custom rom on my Desire S without any problems
so I have a basic idea about this process.
First, I unlocked my phone using HTC Dev, worked fine (Unlocked but S-ON).
Next, I wanted to flash OpenRecovery TWRP 2.6.3.0. This is what I got:
C:\one>fastboot flash recovery recovery.img
sending 'recovery' (8432 KB)...
OKAY [ 1.117s]
writing 'recovery'...
(bootloader) Format partition SOS done
FAILED (remote: err = 0xa)
finished. total time: 1.344s
So I couldn´t flash TWRP. I also tried using Desire S All-In-One Toolkit with the same outcome.
I repeated this a couple of times without success. Tried the Goo App, but it couldn´t download the files needed (WiFi worked).
Also, ADB is not recognizing my device (list of devices stays emtpy).
adb kill-server
adb start-server
adb devices does not help.
Stupidly, while being in Bootloader mode, I tried "Factory Reset" and now the phone always starts in this mode.
I can´t access Android any more.
Using the function "Recovery", the phone will either hang itself showing the closing sequence logo or return to the Bootloader
menu after a second.
I tried finding a new firmware, but following the link (http://forum.xda-developers.com/show....php?t=1957376), I can´t identify a correct firmware at the download chapter.
C:\one>fastboot getvar all
(bootloader) version: 0.5a
(bootloader) version-bootloader: 1.39.0000
(bootloader) version-baseband: 5.1204.162A.29
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 3.20.401.1
(bootloader) serialno: HT23LW105257
(bootloader) imei: 359188041126251
(bootloader) product: endeavoru
(bootloader) platform: HBOOT-T30S
(bootloader) modelid: PJ4610000
(bootloader) cidnum: HTC__102
(bootloader) battery-status: good
(bootloader) battery-voltage: 3945mV
(bootloader) devpower: 76
(bootloader) partition-layout: None
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: None
(bootloader) hbootpreupdate: 2
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.827s
Because the phone was bricked at this point, I tried flashing five different firmware.zip`s, and none worked (could not be flashed / got a message like different version or checksum) - in the end, all this had no effect on the current status / remained all unchanged. I am not sure which firmware version could work.
I searched about all these problems but could not find a solution yet.
HTC Drivers are ver. 3.0.0.007 / Windows 7 64bit / HTC Sync was closed while flashing, USB port is 2.0.
I also tried to restart the phone without fastboot mode, but it also did not work:
fastboot -i 0x1949 oem idme bootmode 4000
fastboot -i 0x1949 reboot
Now I have no idea how to continue. I guess the trick is to avoid the fastbood mode to flash the recovery and then perform the rest as usual,
but nothing seems to work.
Anyone got an idea?

First of all..
Why are you using a toolkit for a different phone?
Second, try to rwflash the recovery and do fastboot erase cache, I recommend flash philz touch recovery
Sent from my HTC One X using xda app-developers app

Stefan0vic said:
First of all..
Why are you using a toolkit for a different phone?
Second, try to rwflash the recovery and do fastboot erase cache, I recommend flash philz touch recovery
Sent from my HTC One X using xda app-developers app
Click to expand...
Click to collapse
Hi, at first, many thanks. Philz touch worked perfectly. Tried TWRP. After hours, I got it running, but the touchpad functiond didn´t work.
Philz recovery is way better than TWRP.
Finally I´ve been able to flash my new (Venom) rom.
Thanks a lot!

Glad it works never use a toolkit imho.. it's also way more fun to flash everything yourself.
No hard feelings against the developers though enjoy the phone
Sent from my HTC One X using xda app-developers app

Stefan0vic said:
Glad it works never use a toolkit imho.. it's also way more fun to flash everything yourself.
No hard feelings against the developers though enjoy the phone
Sent from my HTC One X using xda app-developers app
Click to expand...
Click to collapse
Yeah, I guess I had a wrong version of TWRP at the beginning.
Manual fastboot command line options are way quicker.
In the end, it tool me less then 20mins to complete flashing.
Maybe one last question: I did a nandroid backup of the existing system before.
I think it´s stored on the internal storage, not on the extension which is visible in Windows via USB.
Should I just leave the nandroid backup where it is or make a copy to my computer?
If yes, how can I "extract" it?
Thx!

cometophob said:
Yeah, I guess I had a wrong version of TWRP at the beginning.
Manual fastboot command line options are way quicker.
In the end, it tool me less then 20mins to complete flashing.
Maybe one last question: I did a nandroid backup of the existing system before.
I think it´s stored on the internal storage, not on the extension which is visible in Windows via USB.
Should I just leave the nandroid backup where it is or make a copy to my computer?
If yes, how can I "extract" it?
Thx!
Click to expand...
Click to collapse
Recoveries don't save Nandroids to the data partition, so it's definitely on your virtual sdcard, the phones storage. Search for the folder ClockworkMod on your sdcard and it should be there.
Sent from my HTC One X using Tapatalk

Yes and you may also want to upload your nandroid in the general section with a collection of all nandroid backups, you could save someone's phone that way!
I also always make sure I have a copy of my stock Rom on dropbox. Also a stock recovery just to be safe. If I ever need to return to stock i have the files needed.
Sent from my HTC One X using xda app-developers app

Hi, need some help

Ive been reading this section of the forum for 2 nights now. read various threads and none the wiser.
Ive unlocked my htc one x using the windroid htc one app which worked fine, but installing a rom was not as easy. now < i admit, i dived in and installed a ROM without seeing what else it needs to work ( am used to flashing nexus roms) and now its stuck at the HTC screen. Now i've tried various ways to rectify the proplem. uisng various roms, flashing boot.img before flashing the rom, no go. tried older roms, no go.
I know the hboot needs updating, but without a cid id then i cant find a matching firmware.zip.
Ive tried to do a RUU boot by locking the bootloader but get this:
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash zip rom.zip
sending 'zip' (153709 KB)...
OKAY [ 19.444s]
writing 'zip'...
(bootloader) signature checking...
FAILED (remote: 12 signature verify fail)
finished. total time: 29.009s
So am at a loss and asking for help.
(bootloader) version: 0.5a
(bootloader) version-bootloader: 0.95.0000
(bootloader) version-baseband: 2.1204.135.20
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 1.29.401.11
(bootloader) serialno: HT
(bootloader) imei:
(bootloader) product: endeavoru
(bootloader) platform: HBOOT-T30S
(bootloader) modelid: PJ4610000
(bootloader) cidnum: None
(bootloader) battery-status: good
(bootloader) battery-voltage: 3990mV
(bootloader) devpower: 82
(bootloader) partition-layout: None
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: None
(bootloader) hbootpreupdate: 2
(bootloader) gencheckpt: 0
hope the above info helps.

ajg008 said:
Ive been reading this section of the forum for 2 nights now. read various threads and none the wiser.
Ive unlocked my htc one x using the windroid htc one app which worked fine, but installing a rom was not as easy. now < i admit, i dived in and installed a ROM without seeing what else it needs to work ( am used to flashing nexus roms) and now its stuck at the HTC screen. Now i've tried various ways to rectify the proplem. uisng various roms, flashing boot.img before flashing the rom, no go. tried older roms, no go.
I know the hboot needs updating, but without a cid id then i cant find a matching firmware.zip.
Ive tried to do a RUU boot by locking the bootloader but get this:
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash zip rom.zip
sending 'zip' (153709 KB)...
OKAY [ 19.444s]
writing 'zip'...
(bootloader) signature checking...
FAILED (remote: 12 signature verify fail)
finished. total time: 29.009s
So am at a loss and asking for help.
(bootloader) version: 0.5a
(bootloader) version-bootloader: 0.95.0000
(bootloader) version-baseband: 2.1204.135.20
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 1.29.401.11
(bootloader) serialno: HT
(bootloader) imei:
(bootloader) product: endeavoru
(bootloader) platform: HBOOT-T30S
(bootloader) modelid: PJ4610000
(bootloader) cidnum: None
(bootloader) battery-status: good
(bootloader) battery-voltage: 3990mV
(bootloader) devpower: 82
(bootloader) partition-layout: None
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: None
(bootloader) hbootpreupdate: 2
(bootloader) gencheckpt: 0
hope the above info helps.
Click to expand...
Click to collapse
Lock your bootloader fastboot oem lock after this run RUU 1.29.401.11 as administrator and follow the instruction. After RUU finish update the phone to latest JB from Settings/About/Software Updates!
Report back

thanks. Downloading now, will try when i return home from work

Thant said:
Lock your bootloader fastboot oem lock after this run as administrator and follow the instruction. After RUU finish update the phone to latest JB from Settings/About/Software Updates!
Report back
Click to expand...
Click to collapse
thanks for your help that got the phone back to booting properly
I flashed it and it worked. I got myself back to the latest update. Now i tried various roms again as i'm one for experimenting but some of the newest ones dont seem to want to work.
ones i've tried>
Android_Revolution_HD-One_X_33.1
HTC_One_X_-_MaximusHD_21.0.0
OneX The Next Chapter! v1.2
but none of them worked for me.
So i went lower with
cm-10.1.3-endeavoru which worked
then updated to
cm-10.2.0-endeavoru and flashed the boot.img for it to work.
Now for the other roms, what am i missing? is it the firmware.zip? hboot level?
Am bowing down to Thant, and hoping he can tell a mere minion what he's doing wrong

I don't think you updated far enough ! Post the outcome of :
Fastboot getvar version-main
Edit :
I see thant is offline, so i chip in......

Mr Hofs said:
I don't think you updated far enough ! Post the outcome of :
Fastboot getvar version-main
Edit :
I see thant is offline, so i chip in......
Click to expand...
Click to collapse
the result is:
version-main: 2.17.401.2

What i thought. You need to run another ruu and update many more ota's
Here is the ruu
http://www.persianhtc.net/index.php...Radio_2.1204.135.20_release_274900_signed.exe

Mr Hofs said:
What i thought. You need to run another ruu and update many more ota's
Here is the ruu
[ul]h*tp://w*w.persianhtc.net/index.php?dir=One%20X%28Endeavor%29/rom/original/exe/&file=RUU_ENDEAVOR_U_ICS_40_S_HTC_Europe_2.17.401.2_Radio_2.1204.135.20_release_274900_signed.exe[/url]
Click to expand...
Click to collapse
downloading now, but need sleep now and will report back tomorrow.
thanks very much for your help.
bows to Mr Hofs

Same here.

cyanogenmod stable rom not recognising sim, and not being recognised by htc sync
Hi i just unlocked and rooted my phone. one of the first things i did after having rooted it was go into rom-manager and download the highest rated cyanogen mod stable rom...expecting it to reboot itself and do the update automatically once id downloaded the file i was suprised when nothing happened...so i put it into recovery mode myself and searched the phone's storage for the rom file...it was infact two files, one the rom, the other gapps...i installed both of them and rebooted the phone...at first i was left on cyanogenmod bootloop...after a few restarts, and factory resets, i eventually got past the cyanogen mod intro wheel, to its actual introduction *asking me to choose a language*, as soon i choose my language i get notification asking me to insert my simcard (it already is, OF COURSE...), as i go through the rest of the setup there is no network coverage or internet..so i cant simply download rom-manager and try another flash..it also wont come up as a recognised device on my macbook...ive downloaded another flash of cyanogenmod on my laptop along with a new gapps, but im utterly lost about what to do now...i cant even put them on the phone....
wud love any help
The recovery version I'm using is clockworkMod Recovery v5.8.2.7
And here is my bootloader
ENDEAVORU PVT SHIP 2-ON RL
HBOOT-1.72.0000
CPLD-None
RADIO-5.1204.167.31
eMMC-bootmode: disabled
CPU-bootmode: disabled
HW Secure boot: enabled
MODEM PATH: OFF
Jun 21 2013,18:24:21

tekkr said:
Hi i just unlocked and rooted my phone. one of the first things i did after having rooted it was go into rom-manager and download the highest rated cyanogen mod stable rom...expecting it to reboot itself and do the update automatically once id downloaded the file i was suprised when nothing happened...so i put it into recovery mode myself and searched the phone's storage for the rom file...it was infact two files, one the rom, the other gapps...i installed both of them and rebooted the phone...at first i was left on cyanogenmod bootloop...after a few restarts, and factory resets, i eventually got past the cyanogen mod intro wheel, to its actual introduction *asking me to choose a language*, as soon i choose my language i get notification asking me to insert my simcard (it already is, OF COURSE...), as i go through the rest of the setup there is no network coverage or internet..so i cant simply download rom-manager and try another flash..it also wont come up as a recognised device on my macbook...ive downloaded another flash of cyanogenmod on my laptop along with a new gapps, but im utterly lost about what to do now...i cant even put them on the phone....
wud love any help
The recovery version I'm using is clockworkMod Recovery v5.8.2.7
And here is my bootloader
ENDEAVORU PVT SHIP 2-ON RL
HBOOT-1.72.0000
CPLD-None
RADIO-5.1204.167.31
eMMC-bootmode: disabled
CPU-bootmode: disabled
HW Secure boot: enabled
MODEM PATH: OFF
Jun 21 2013,18:24:21
Click to expand...
Click to collapse
Rom manager not working on S-ON devices flash the boot.img manually from fastboot with command fastboot flash boot boot.img take the boot.img from rom arhiv wich you want to install

Thant said:
Rom manager not working on S-ON devices flash the boot.img manually from fastboot with command fastboot flash boot boot.img take the boot.img from rom arhiv wich you want to install
Click to expand...
Click to collapse
the reason i'm so frustrated is aside from the supposedly stable build of cyanogen mod i downloaded in rommanager not working, the rom doesnt recognise my sim, i dont have access to the internet, so i cant simply download a new rom to flash straight from rom manager...as well as this the wifi doesn't seem to work on this flash...and to make matters worse it's not being recognised by the drivers...i'm using htc sync manager..when i plug in the phone it will open htc sync manager but wont show that a phone is paired to my macbook
...when u say manually can i do this directly from my phone or do i need to connect it to a computer?

You must connect it to PC..And then go to fastboot and flash boot.img file..Then you will have signal,wifi etc..

big noob said:
You must connect it to PC..And then go to fastboot and flash boot.img file..Then you will have signal,wifi etc..
Click to expand...
Click to collapse
its not being recognised as a device since i flashed the *cyanogen mod stable rom*...i plugged it to my computer though, and put it into fastboot and it says FASTBOOT USB...the options it gives me from here are
HBOOT
REBOOT
REBOOT BOOTLOADER
POWER DOWN

Here is guide how to use ADB on macbook:
http://forum.xda-developers.com/showthread.php?t=1917237
And then you can use fastboot commands..

Mr Hofs said:
What i thought. You need to run another ruu and update many more ota's
Here is the ruu
[ul]ht*p://w*w.persianhtc.net/index.php?dir=One%20X%28Endeavor%29/rom/original/exe/&file=RUU_ENDEAVOR_U_ICS_40_S_HTC_Europe_2.17.401.2_Radio_2.1204.135.20_release_274900_signed.exe[/url]
Click to expand...
Click to collapse
ive tried that but keep getting signature error

ajg008 said:
ive tried that but keep getting signature error
Click to expand...
Click to collapse
Relocked the bootloader ?

Mr Hofs said:
Relocked the bootloader ?
Click to expand...
Click to collapse
yep fastboot oem lock

Then it might be easier to flash the 3.14.401 firmware to upgrade the hboot to 1.39. Then you can flash any rom you want, and there is also a ruu for that. Sorry i have no time to explain now (heading home from work)
Look for the firmware placeholder thread, read the instructions and download the 3.14.401 firmware.zip from there.
http://forum.xda-developers.com/showthread.php?t=1957376

Mr Hofs said:
Then it might be easier to flash the 3.14.401 firmware to upgrade the hboot to 1.39. Then you can flash any rom you want, and there is also a ruu for that. Sorry i have no time to explain now (heading home from work)
Look for the firmware placeholder thread, read the instructions and download the 3.14.401 firmware.zip from there.
[rl]htp://forum.xda-developers.com/showthread.php?t=1957376[/url]
Click to expand...
Click to collapse
i already had the ota 3.14.401 and got the firmware.zip from there.
its installed fine and i now can put most roms onto it.
:victory: thank you Mr Hofs
So i get this right in my head. The phones firmware.zip needed updated so it would update hboot and other things.
Now to flash roms is the procedure to flash the boot.img contained inside first then install the rom <----which is they way ive being doing it

Boot Loop/No Recovery

Hey all
I tried to flash over a Google Edition Rom from Cyanogen Mod by following a guide and now I am stuck on a google boot loop. Ive tried to enter recovery but it just leads me back to the google boot loop and the same happens when I try to choose factory reset. Ive tried to flash back to cyanogen and I get this error FAILED (remote: 24 parsing android-info fail) I have also tried to flash back to a sense rom and get this error FAILED (remote: 24 parsing android-info fail). So how can I either get my recovery working or getting back to Cyanogen.
Also I changed my model ID when following the guide... So Im guessing that has something to do with it but I am unsure how to change my model ID back without having access to recovery.
Heres what I got from the getvar command
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.54.0000
(bootloader) version-baseband: 4T.21.3218.21
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 3.62.1700.1
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno: FA37MS910651
(bootloader) imei: 990004281021810
(bootloader) meid: 99000428102181
(bootloader) product: m7_wlv
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0712000
(bootloader) cidnum: GOOGL001
(bootloader) battery-status: good
(bootloader) battery-voltage: 4090mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: RUU
(bootloader) commitno-bootloader: dirty-0e82187e
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
[Edit] I also tried flashing a recovery and got FAILED (remote: not allowed)

Try flashing twrp using ruu mode. http://vzw1files.dyndns.org/RECOVERIES/twrp/Twrp_2.6.3.4_RUU_Mode.zip
fastboot reboot bootloader
fastboot oem rebootRUU
fastboot flash zip nameoffile.zip
(may fail with flush error just do cmd again)
fastboot reboot

cmlusco said:
Try flashing twrp using ruu mode.
fastboot reboot bootloader
fastboot oem rebootRUU
fastboot flash zip nameoffile.zip
(may fail with flush error just do cmd again)
fastboot reboot
Click to expand...
Click to collapse
I do that and get FAILED (remote: 41 model id check fail)

Ok try the same thing only with this file https://www.dropbox.com/s/k52zdjv453isy0h/PN07IMG.zip

cmlusco said:
Ok try the same thing only with this file
Click to expand...
Click to collapse
I got the same FAILED (remote: 42 custom id check fail) error. I reran getvar all and saw that the cidnum changed from GOOGL001 to VZW__001

Ok try this one then https://www.dropbox.com/s/f8vtvu1ahg2uqql/PN07IMG2.zip

That worked! Thank you! I was able to sideload cyanogen back on but now it reboots after a couple minutes of being in the rom...

You may need to flash the latest firmware after changing your mid back if you havent already.

cmlusco said:
You may need to flash the latest firmware after changing your mid back if you havent already.
Click to expand...
Click to collapse
The latest stock firmware? Where would I get that

http://vzw1files.dyndns.org/FIRMWARE/3.11.605.1-NO-BootIMG_firmware.zip
You flash it in ruu mode with fastboot.
fastboot oem rebootRUU
fastboot flash zip nameoffile.zip
fastboot reboot

cmlusco said:
You flash it in ruu mode with fastboot.
fastboot oem rebootRUU
fastboot flash zip nameoffile.zip
fastboot reboot
Click to expand...
Click to collapse
When I try to flash over the file in RUU it gives me this FAILED (remote: 42 custom id check fail)
(bootloader) modelid: PN0731000
(bootloader) cidnum: GOOGL001
That is what shows up when I getvar all

Change your cid back to VZW__001
fastboot oem writecid VZW__001

cmlusco said:
Change your cid back to VZW__001
fastboot oem writecid VZW__001
Click to expand...
Click to collapse
When I run that I get
(bootloader) Start Verify: 0
(bootloader) Input CID is not super CID
(bootloader) Start Verify: 0
OKAY [ 0.064s]
finished. total time: 0.064s
And when I getvar all my cid still says GOOG001

Try changing it to super cid 11111111 eight ones

That worked and so far Cyanogen is not randomly rebooting!
Thanks again! You are a life saver

cmlusco said:
http://vzw1files.dyndns.org/FIRMWARE/3.11.605.1-NO-BootIMG_firmware.zip
You flash it in ruu mode with fastboot.
fastboot oem rebootRUU
fastboot flash zip nameoffile.zip
fastboot reboot
Click to expand...
Click to collapse
Hey dude why do you keep mirroring Santod's files? Just link him to the OP. The way you're doing this kind of makes it look like you made this. No credits or anything given to the dev.

disconnecktie said:
Hey dude why do you keep mirroring Santod's files? Just link him to the OP. The way you're doing this kind of makes it look like you made this. No credits or anything given to the dev.
Click to expand...
Click to collapse
Not my intention at all. 99.8% of the stuff on that site is not made by me. I do it to make it easier on my self when trying to help others, so i dont have to search all over for links. I also do it as a backup of sorts. I have seen file sharing sites go down (some permanetly), xda members leave or close threads or not maintain them once they move to a new phone or what ever. Then these critical files are lost, or a massive time consuming manhunt insues to find them. It also provides one easy organized place to find the files you need .And just to be clear, the no boot img file you are refering to was not made by santod. It was one i edited my self by pulling the boot img from a firmware zip file. Just because he did it, dosent mean someone else cant do the same. Im not here for credit, im here to help people and to get help. I give santod and any other dev whos files i mirror full credit. If its that big of a freakin deal, i will just shut the site down. I have done the same thing with several other phones i have had, and have never had an issue from anyone like i have had here in the vzw one forums.

Well on several phones I've owned it was rude to mirror devs files without their permission or without them requesting it. It is one thing for the dev to ask for a mirror and someone mirror the file for them. All the links in his op work and they aren't hard to find at all. So other than having a site for your own personal reasons there doesn't seem to be a very good reason to have mirrors of every file that has been posted to this forum.

Well your opinion is yours. I dont see what its hurting. Its not like im mirroring roms or anything. File a complaint with xda if you think its against the rules in some way. Untill they kick me off xda, you can find me here helping others in the best way i can.

cmlusco said:
Well your opinion is yours. I dont see what its hurting. File a complaint with xda if you think its against the rules in some way. Untill they kick me off xda, you can find me here helping others in the best way i can.
Click to expand...
Click to collapse
I'm not at all saying you can't help people but how much more difficult would it be to link back to the op where you got the file from? As far as I know all the links are working.