Database Info

[Q] - Random reboots on my evita

When trying to update my evita to JB, I faced random reboots when running the roms.
ROMs tried include MagioRom e.5, JellyBam, CleanRom 6.5, and even the stock 3.17 ROM by Taichi91.
All had random reboots when using the ROM.
Can anyone help to suggest solutions?
Phone: evita
Hboot: 1.09 S-Off
ROM: Stock ICS 1.85 asia

Try running an RUU, that will take you back to stock. Use the stock software for a day or two and see if the problem persists. If it does, it's likely a hardware issue.
Sent from my Evita

timmaaa said:
Try running an RUU, that will take you back to stock. Use the stock software for a day or two and see if the problem persists. If it does, it's likely a hardware issue.
Sent from my Evita
Click to expand...
Click to collapse
Hi Timmaaa,
Thanks for the reply
I am actually on stock ICS 4.0.3 which has no issues.
The problem is when I flash the JB custom ROMs that I faced random reboots.
Do you mean to run RUU back to 1.85 stock? or to 3.17 stock?
I am concerned if I would lose S-Off if I run any RUU.

You will not lose S-off if you RUU. The only thing that can change S-off, is if you manually change it yourself.
Running the 3.18 RUU has solved the problem of random reboots for lots of people running 3.18 custom ROMs.

redpoint73 said:
You will not lose S-off if you RUU. The only thing that can change S-off, is if you manually change it yourself.
Running the 3.18 RUU has solved the problem of random reboots for lots of people running 3.18 custom ROMs.
Click to expand...
Click to collapse
Thanks redpoint
I'll try to run the 3.18 RUU and see if this resolves my issue.
May take some time as the phone will leave my side for about a month

s79336951 said:
When trying to update my evita to JB, I faced random reboots when running the roms.
ROMs tried include MagioRom e.5, JellyBam, CleanRom 6.5, and even the stock 3.17 ROM by Taichi91.
All had random reboots when using the ROM.
Can anyone help to suggest solutions?
Phone: evita
Hboot: 1.09 S-Off
ROM: Stock ICS 1.85 asia
Click to expand...
Click to collapse
Random reboots may have to due with voltages being too low. I've never tried any of the ROMs you mentioned other than CleanROM, but if you're running a custom kernel or even stock, see if you can raise global voltages by +25 mV or +50 mV.. Try Kernel Tuner if you're looking for an app that'll allow you to do that. Again, only if you're running a kernel that supports custom voltages.

I have the same problem.
Tried CM 10.1/2 and AOKP and had random reboots.
I'm very frustrated...
Could you solve the issue? Read about RUU firmeware updates to solve this. But i don't know how to do so.

You haven't provided anywhere near enough information for anyone to help you.
Sent from my Evita

timmaaa said:
You haven't provided anywhere near enough information for anyone to help you.
Sent from my Evita
Click to expand...
Click to collapse
German T-Mobile Evita
S-OFF
SuperCID
HBoot 2.14
Radio 0.24a.32.45.03
Is that enough? thanks

The AOKP builds are fairly old, and there's been a whole bunch of issues on cm recently, maybe you need to try a different ROM. No need to RUU as it looks as though you're currently on the correct firmware package to run these ROMs.
Sent from my Evita

install this
s79336951 said:
When trying to update my evita to JB, I faced random reboots when running the roms.
ROMs tried include MagioRom e.5, JellyBam, CleanRom 6.5, and even the stock 3.17 ROM by Taichi91.
All had random reboots when using the ROM.
Can anyone help to suggest solutions?
Phone: evita
Hboot: 1.09 S-Off
ROM: Stock ICS 1.85 asia
Click to expand...
Click to collapse
install this kernel
http://forum.xda-developers.com/showthread.php?t=2061577 and if u still have issue then install it again with higher voltage i had same issue and now m happy with my phone

jahanzaiblohani said:
install this kernel
http://forum.xda-developers.com/showthread.php?t=2061577 and if u still have issue then install it again with higher voltage i had same issue and now m happy with my phone
Click to expand...
Click to collapse
Thanks jahanzaiblohani. Will do that.
First of all, sorry for the long disappearance.
I finally have the phone back to resolve the random reboot problem.
There have been much development and from my readings, here are the options to solve the problem.
Kindly let me know if the thinking is correct.
Stock route
Custom ROMs
For stock, I have to RUU to JB 3.17, before applying OTA to 5.xx Sense 5.
I am currently on hboot 1.09, S-OFF, SuperCID and unlocked bootloader, TWRP 2.6.0.
This is an Asia HOXL 1.88.707.2.
Code:
> fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.09.0000
(bootloader) version-baseband: 0.17a.32.09.16_2
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 1.88.707.2
(bootloader) serialno: **REMOVED**
(bootloader) imei: **REMOVED**
(bootloader) product: evita
(bootloader) platform: HBOOT-8960
(bootloader) modelid: PJ8312000
(bootloader) cidnum: 11111111
(bootloader) battery-status: good
(bootloader) battery-voltage: 4169mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: e964c535
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
Steps:
Run 3.17 RUU. I read that it should work with unlocked bootloader and TWRP since I'm S-OFF
Flash stock recovery.
Apply Sense 5 OTA. Do I need to relock the bootloader?
Flash TWRP 2.6.0
Root
For custom route, I'm currently running MagioROM R4.02 with the kernel that came with it.
The random reboot issue is encountered.
To resolve I can try the following steps:
Update to 2.15 firmware; OR
Flash Zarboz's Beastmode kernel
I tried to follow the steps to update firmware, but saw that modelid: PJ8310000 in the android-info.txt in the firmware zip.
However, my HOXL has modelid: PJ8312000. Can I update the firmware?
I am currently trying out Beastmode Reloaded 3.5 to see if it fixes the issue.
Does ElementalX 8.3.2 resolve the random reboot issue?
Thanks all.

sm753 said:
Random reboots may have to due with voltages being too low. I've never tried any of the ROMs you mentioned other than CleanROM, but if you're running a custom kernel or even stock, see if you can raise global voltages by +25 mV or +50 mV.. Try Kernel Tuner if you're looking for an app that'll allow you to do that. Again, only if you're running a kernel that supports custom voltages.
Click to expand...
Click to collapse
Just to update that I had tried this but couldn't resolve it.
I'll try it again after running custom kernel.
Thanks!

wanted to give you a short update:
still on AOKP, but:
- updated TWRP from 2.5.0.0 to 2.6.3.0 -> random reboots
- updated firmware as described here -> waiting for reboots...
current config:
(bootloader) version: 0.5
(bootloader) version-bootloader: 2.15.0000
(bootloader) version-baseband: 1.31a.32.45.16_2
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 5.08.111.2
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno: XX
(bootloader) imei: XX
(bootloader) product: evita
(bootloader) platform: HBOOT-8960
(bootloader) modelid: PJ8311000
(bootloader) cidnum: 11111111
(bootloader) battery-status: good
(bootloader) battery-voltage: 3991mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-de589c6eef
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
just saw that you're on BeanStalk which shouldn't have Reboots like the topic says... that would be the next to try

Engelhuber said:
wanted to give you a short update:
still on AOKP, but:
- updated TWRP from 2.5.0.0 to 2.6.3.0 -> random reboots
- updated firmware as described here -> waiting for reboots...
current config:
(bootloader) version: 0.5
(bootloader) version-bootloader: 2.15.0000
(bootloader) version-baseband: 1.31a.32.45.16_2
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 5.08.111.2
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno: XX
(bootloader) imei: XX
(bootloader) product: evita
(bootloader) platform: HBOOT-8960
(bootloader) modelid: PJ8311000
(bootloader) cidnum: 11111111
(bootloader) battery-status: good
(bootloader) battery-voltage: 3991mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-de589c6eef
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
just saw that you're on BeanStalk which shouldn't have Reboots like the topic says... that would be the next to try
Click to expand...
Click to collapse
Hi Engelhubber,
Good luck to you. Hope the firmware update resolves the random reboot issue.
A question to you, as seeing that you have modelid: PJ8311000.
Looks like you updated the firmware as provided in Turge's T-Mobile Sense 5 thread, which had modelid: PJ8310000 in the file andriod-info.txt.
Can you help confirm this?
Does anyone know if the modelid matters?

s79336951 said:
Hi Engelhubber,
Good luck to you. Hope the firmware update resolves the random reboot issue.
A question to you, as seeing that you have modelid: PJ8311000.
Looks like you updated the firmware as provided in Turge's T-Mobile Sense 5 thread, which had modelid: PJ8310000 in the file andriod-info.txt.
Can you help confirm this?
Does anyone know if the modelid matters?
Click to expand...
Click to collapse
Hi, it's the file from the post mentioned above.
Credits go to Turge, so i think its the same!? Don't know. Sorry
Mine is a german T-Mobile Evita...

the model id doesnt matter. I believe I was the first person to flash 2.15 with a different mid as I had random reboots with 2.14 and sense 5 roms. After flashing 2.15 firmware no issues ever arose.

exad said:
the model id doesnt matter. I believe I was the first person to flash 2.15 with a different mid as I had random reboots with 2.15 and sense 5 roms. After flashing 2.15 firmware no issues ever arose.
Click to expand...
Click to collapse
Thank you exad for the confirmation.
I have updated the firmware and the modelid remains unchanged.
Seems to be running fine now.

Engelhuber said:
wanted to give you a short update:
still on AOKP, but:
- updated TWRP from 2.5.0.0 to 2.6.3.0 -> random reboots
- updated firmware as described here -> waiting for reboots...
just saw that you're on BeanStalk which shouldn't have Reboots like the topic says... that would be the next to try
Click to expand...
Click to collapse
Seems stable. So far no reboots:
- updated TWRP from 2.5.0.0 to 2.6.3.0 -> random reboots
- updated firmware as described here -> seems ok
- switching from AOKP 20130820 back to CM10.2 20131106 nightly...

Remove S-Off / Fix Edge only problem

I've been struggling with a problem since I updated my kernel to 3.4.
I'm not sure if getting rid of S-Off is the solution but it's worth trying. I have been having problem using my 3g/H+ network since some time now and I've been trying to get back to a stock version of my phone to try to fix it (or so at least I could get it repaired)
My problem is exactly as explained in this thread:
http://forum.xda-developers.com/showthread.php?t=2160389
It seems like the guy has been trying pretty much everything without any luck but then some guy posted on the AOSP Kernel 3.4 thread that getting rid of S-Off could be a solution to this problem. I believe it's worth trying:
http://forum.xda-developers.com/showpost.php?p=44408494&postcount=319
Anyhow, my phone is on the Fido network and I had previously S-Offed and SuperCid it. Since then, I've been having some troubles with the radio not being able to connect to 3g/H+. How exactly can I go back to S-On, just so at least I can see if that fixes my problem.
Here's my var all for more info:
(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:
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno: *****
(bootloader) imei: ******
(bootloader) product: vle
(bootloader) platform: HBOOT-8960
(bootloader) modelid: PJ4011000
(bootloader) cidnum: ROGER001
(bootloader) battery-status: good
(bootloader) battery-voltage: 3810mV
(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
Let me know if more infos are needed, I'd really want to fix that if possible

GabeyC said:
I've been struggling with a problem since I updated my kernel to 3.4.
I'm not sure if getting rid of S-Off is the solution but it's worth trying. I have been having problem using my 3g/H+ network since some time now and I've been trying to get back to a stock version of my phone to try to fix it (or so at least I could get it repaired)
My problem is exactly as explained in this thread:
http://forum.xda-developers.com/showthread.php?t=2160389
It seems like the guy has been trying pretty much everything without any luck but then some guy posted on the AOSP Kernel 3.4 thread that getting rid of S-Off could be a solution to this problem. I believe it's worth trying:
http://forum.xda-developers.com/showpost.php?p=44408494&postcount=319
Anyhow, my phone is on the Fido network and I had previously S-Offed and SuperCid it. Since then, I've been having some troubles with the radio not being able to connect to 3g/H+. How exactly can I go back to S-On, just so at least I can see if that fixes my problem.
Here's my var all for more info:
(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:
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno: *****
(bootloader) imei: ******
(bootloader) product: vle
(bootloader) platform: HBOOT-8960
(bootloader) modelid: PJ4011000
(bootloader) cidnum: ROGER001
(bootloader) battery-status: good
(bootloader) battery-voltage: 3810mV
(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
Let me know if more infos are needed, I'd really want to fix that if possible
Click to expand...
Click to collapse
From my own experience, my phone stuck to edge nearly all the time after updating to the Rogers/Fido 4.1.1 OTA update. I've never been s-off, only rooted and unlocked. The problem happened even on the stock rom, but only after the update. Tried different roms and nothing seemed to fix the problem. What I noticed was if I reset the phone, it would stick to 3G/H+, however as soon as the screen was turned off and went to sleep for a few minutes it would go back to edge and forcing WCDMA only would only result in a slow decline of network reception until it went out completely.
Currently trying to get back to stock so I can send my phone in to get it repaired under warranty. Seriously considering sim unlocking it after I get it back, selling it and buying another phone.

I don't recall which phone I had, I know it had to have been an htc but again, forget which. Anyways I recall when I s-off that phone it basically had the same problem. The fix was rather simple. Just flash the stock recovery, then in the bootloader choose factory reset, then reflash whatever recovery you were using.
Data worked perfectly on any rom after.
Don't know if it will fix your problem but may be worth looking into.
That problem had to have happened on either my old sensation, incredible 2, or rezound. But I do remember specifically many people had that problem.

Dalamar1320 said:
I don't recall which phone I had, I know it had to have been an htc but again, forget which. Anyways I recall when I s-off that phone it basically had the same problem. The fix was rather simple. Just flash the stock recovery, then in the bootloader choose factory reset, then reflash whatever recovery you were using.
Data worked perfectly on any rom after.
Don't know if it will fix your problem but may be worth looking into.
That problem had to have happened on either my old sensation, incredible 2, or rezound. But I do remember specifically many people had that problem.
Click to expand...
Click to collapse
Do you have to have the stock rom flashed to do a factory reset? What will happen if you try to factory reset with a custom rom flashed?

I tried to flash my stock recovery but I couldn't seem to find how.
How exactly can I find the stock recovery for the phone?

Here:
http://www.mediafire.com/?444r63wp7fzi52r
Sent from my One S using Tapatalk 4

Perfect,
And like booenson asked, you can do a factory reset on a custom rom?? Don't you need to have the stock ROM??

GabeyC said:
I've been struggling with a problem since I updated my kernel to 3.4.
I'm not sure if getting rid of S-Off is the solution but it's worth trying. I have been having problem using my 3g/H+ network since some time now and I've been trying to get back to a stock version of my phone to try to fix it (or so at least I could get it repaired)
My problem is exactly as explained in this thread:
http://forum.xda-developers.com/showthread.php?t=2160389
It seems like the guy has been trying pretty much everything without any luck but then some guy posted on the AOSP Kernel 3.4 thread that getting rid of S-Off could be a solution to this problem. I believe it's worth trying:
http://forum.xda-developers.com/showpost.php?p=44408494&postcount=319
Anyhow, my phone is on the Fido network and I had previously S-Offed and SuperCid it. Since then, I've been having some troubles with the radio not being able to connect to 3g/H+. How exactly can I go back to S-On, just so at least I can see if that fixes my problem.
Here's my var all for more info:
(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:
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno: *****
(bootloader) imei: ******
(bootloader) product: vle
(bootloader) platform: HBOOT-8960
(bootloader) modelid: PJ4011000
(bootloader) cidnum: ROGER001
(bootloader) battery-status: good
(bootloader) battery-voltage: 3810mV
(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
Let me know if more infos are needed, I'd really want to fix that if possible
Click to expand...
Click to collapse
I have the same problem. After many trails to repair it, only solution I found is, getting rid of the phone. :crying:

GabeyC said:
Perfect,
And like booenson asked, you can do a factory reset on a custom rom?? Don't you need to have the stock ROM??
Click to expand...
Click to collapse
No you don`t need the stock rom, only recovery.
Sent from my One S using Tapatalk 4

Dalamar1320 said:
I don't recall which phone I had, I know it had to have been an htc but again, forget which. Anyways I recall when I s-off that phone it basically had the same problem. The fix was rather simple. Just flash the stock recovery, then in the bootloader choose factory reset, then reflash whatever recovery you were using.
Data worked perfectly on any rom after.
Don't know if it will fix your problem but may be worth looking into.
That problem had to have happened on either my old sensation, incredible 2, or rezound. But I do remember specifically many people had that problem.
Click to expand...
Click to collapse
Tried that without success... starting to think that it's simply broken, it seems like every thread i stumble upon where people had a similar problem, they had to send it to repair to fix it. Thing is, I don't see how upgrading a kernel could damage any hardware thus it must be somehow related to a software, however low level it is. Also, it seems like after a clean install, the H+/3G will work for a few minutes but will stop working after that. That seems to indicate a software problem more than a hardware one also.
Still trying to figure out how to s-on the phone and get it back to a completely stock state, I couldn't find exactly how. I tried to install the OTA zip from my carrier but that didn't work.
Seems like I'm starting to run out of options

GabeyC said:
Tried that without success... starting to think that it's simply broken, it seems like every thread i stumble upon where people had a similar problem, they had to send it to repair to fix it. Thing is, I don't see how upgrading a kernel could damage any hardware thus it must be somehow related to a software, however low level it is. Also, it seems like after a clean install, the H+/3G will work for a few minutes but will stop working after that. That seems to indicate a software problem more than a hardware one also.
Still trying to figure out how to s-on the phone and get it back to a completely stock state, I couldn't find exactly how. I tried to install the OTA zip from my carrier but that didn't work.
Seems like I'm starting to run out of options
Click to expand...
Click to collapse
I think we're in the same boat, only my problems started after updating to the 4.1.1 Rogers/Fido OTA. Little to no H+/3G service, forcing it only leads to my service going out completely. There aren't any ruu's available for the hboot we're on, I'm back on the stock rom using an ota however SuperSU is still present for some reason, which is keeping my bootloader saying "tampered" and "relocked"

So I received my phone back from HTC today, and 4G is back!

booenson said:
I think we're in the same boat, only my problems started after updating to the 4.1.1 Rogers/Fido OTA. Little to no H+/3G service, forcing it only leads to my service going out completely. There aren't any ruu's available for the hboot we're on, I'm back on the stock rom using an ota however SuperSU is still present for some reason, which is keeping my bootloader saying "tampered" and "relocked"
Click to expand...
Click to collapse
Technically, we should be able to flash the OTA zip, but I wasn't able to do it.
If my phone is SuperCID, can I flash any RUU on it? Any RUU with the same radio?

Problems installing custom ROM One S C2

Hi Everyone I tried every rom in this form but no success my stock rom's backup is also deleted as it was in internal memory.
I tried all the ways still no success from last 2 days. Please help me out.
I install the rom and the flash boot.img but the device keeps rebooting.
HTC ONE S c2
fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 2.09.0001
(bootloader) version-baseband: 16.05.20.24_M
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) product: villec2
(bootloader) platform: HBOOT-8260
(bootloader) modelid: PJ4020000
(bootloader) cidnum: HTC__J15
(bootloader) battery-status: good
(bootloader) battery-voltage: 3748mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: f616909f
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.489s

Update to newest hboot via ota, jellybean update for HTC__J15 is avalible

dominos_liberty said:
Update to newest hboot via ota, jellybean update for HTC__J15 is avalible
Click to expand...
Click to collapse
Can you please provide me the links. Really appreciate that.

Lock your bootloader, Run this RUU: http://bugsylawson.com/index.php/fi...212002u-16092011-m2-release-286571-signedexe/
then check for updates, there will be JB OTA take that and then you can install any custom rom

I have to run this RUU setup in fastboot or some where else. As there is no Rom in the mobile to boot.

sweetdreamz338 said:
I have to run this RUU setup in fastboot or some where else. As there is no Rom in the mobile to boot.
Click to expand...
Click to collapse
Put phone into fastboot mode. Then run this RUU.
Also remove your IMEI & SERIAL NO. from first post
Sent from my HTC One S using Tapatalk 4 Beta

Thank God finally back to normal Stock Rom. Thanks every one for Helping .....

Is it possible to root the phone and keep the stock rom.
Sent from my HTC One S using xda app-developers app

sweetdreamz338 said:
Is it possible to root the phone and keep the stock rom.
Sent from my HTC One S using xda app-developers app
Click to expand...
Click to collapse
Yeah.
Flash a custom recovery, then flash a flashable zip of superuser.
Sent from my Nexus 7 using Tapatalk HD

I am on stock rom JB 4.1.1 Software Number: 3.19.415.102 i install the super user but now my Wifi is notworking

sweetdreamz338 said:
I am on stock rom JB 4.1.1 Software Number: 3.19.415.102 i install the super user but now my Wifi is notworking
Click to expand...
Click to collapse
Factory reset from inside the ROM.
Sent from my Nexus 7 using Tapatalk HD

khan.orak said:
Factory reset from inside the ROM.
Sent from my Nexus 7 using Tapatalk HD
Click to expand...
Click to collapse
I did but still not working. it show error on wifi

[Q] Second hand HTC ONE XL Update issues

Hi!
I've just purchased an HTC One XL 16GB X325s. It has the stock 4.1.1 with Sense 4.
I wanted to update it to the 4.2.2 stock with Sense 5, but OTA did not find any updates.
When I checked the version information, it seems that already had S-OFF and SUPER CID.
Here are my current versions of the software installed on the phone:
Software information:
Android Version: 4.1.1
HTC Sense Version: 4.0
Software Number: 1.77.708.2
HTC SDK API levelL 4.11
HTC Extension version: HTCExtension_403_1_GA_4
Kernel Verrsion: 3.0.8-01129-g3dc-8148, [email protected], SMP PREEMPT Wed Apr 18 21:23:23 CST 2013
Baseband version: 0.16a.32.09.17_2_10.83.32.16L
Build number: 1.77.708.2 CL57351 release-keys
Browser version: WebKit/534.30
Bootloader data:
*** LOCKED ***
EVITA PDT SHIP S-OFF RL
CID-11111111
HBOOT-1.09.0000
RADIO-0.16a.32.09.17_2
OpenDSP-v25.1.0.32.0405
eMMC-boot
Apr 2 2012,21:08:24
One weird thing is that 1.77.708.2 should be for 4.0, but I have 4.1.1. How could this be?
Is there any way to reset the phone back to factory settings for OTA to work?
If not, how should I proceed to install the stock 4.2.2?
Thank you,
Adrian.

Flash the RUU without root,then you can find the ota message.

I would strongly suggest you don't take an OTA even after running an RUU, your phone has been modified. Modified phone + OTA = bad news.
If you really want the latest 4.2.2 just unlock the bootloader so you can flash the stock 4.2.2 ROM in our Android Development section.
Sent from my Evita

adibe said:
One weird thing is that 1.77.708.2 should be for 4.0, but I have 4.1.1. How could this be?
.
Click to expand...
Click to collapse
I assume you are basing that on info I have given.
I think I was wrong about the details of 1.77.708.2, I never actually fully checked. Several(now including you) have said 1.77.708.2 is 4.1.1.
Can you let me know where your device came from?
Country?
Type of store? Eg Official carrier store purchased on a carrier contract, official carrier store but outright purchase, independent store?
Thanks
Edit: oh wait second hand. I dont think this is the first time these have been second hand either. I think independent secondhand dealers got their hands on this weird RUU and flash it randomly to devices.

Hi!
I've got the phone from an eBay-like site here in Romania (Okazii). I don't think that "second hand" was the most correct term, maybe refurbished should be accurate because the phone was visually new (it even had plastic foils on it), but at home I found that it had this HK version, SuperCID, S-off and root.
I've got the the info regarding the version from your thread (Default HTC OTA and RUU collection).
Another weird thing is that Antutu says that I have the Android SDK version 15 (Android 4.0.3), but the version is 4.1.1.
Ideally I would like to install to install CyanogenMod or Paranoid, but on the thread it said that I must update the RUU to 3.18.
Could you please direct me to a compatible RUU for my device? Or should I just install "[STOCK ROM] Android 4.2.2 / Sense 5 - 5.08.111.2" from the Android Development section? Is compatible with my current setup?
Also, here is the fastboot variables:
D:\adt-bundle-windows-x86_64-20130729\sdk\platform-tools>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.09.0000
(bootloader) version-baseband: 0.16a.32.09.17_2
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 1.77.708.2
(bootloader) serialno: HT25...
(bootloader) imei: 359...
(bootloader) product: evita
(bootloader) platform: HBOOT-8960
(bootloader) modelid: PJ83*****
(bootloader) cidnum: 11111111
(bootloader) battery-status: good
(bootloader) battery-voltage: 3788mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: e964c535
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
Thank you,
Adrian.

The phone is definitely used, with what you've shown there. You're lucky that it's s-off, that removes the risk involved with running an RUU.
You'll want to install adb/fastboot, and you'll need HTC drivers.
Click the link in my signature and then find the RUU thread, find the at&t 3.18 RUU and run that. All you do is put the phone in fastboot mode, connect it to the pc and run the RUU exe file. Just make sure there are no other programs running, and screen saver/hibernation is turned off.
Then you can unlock the bootloader, just go to htcdev.com and follow the instructions there. Once your bootloader is unlocked you can flash TWRP 2.6 which you'll find here. Put the file in your fastboot folder. Connect phone in fastboot mode, open command prompt from within fastboot folder, issue the following commands:
Code:
fastboot flash recovery "filename.img"
(the exact filename, minus the talking marks)
Code:
fastboot erase cache
Code:
fastboot reboot-bootloader
Now you can enter recovery on your phone and install the ROM you want to.
Sent from my Evita

Thanks for the help!
One more thing - Just to be safe: The AT&T RUU is compatible with my current setup? (HK ROM)

My phone is a Hong Kong model and I've run the at&t RUU without any problems.
Sent from my Evita

First of all timmaaa and twistedddx: thanks for all your help!
I've installed the 3.18 AT&T RUU, TWRP 2.6 and CM 10.2.
Everything's great, but on both the 3.18 AT&T RUU and CM 10.2 I had an issue with my data connection.
After reboot everything works great, but after some time the connection drops.
I've tried some radios from the the radio thread and there still are drops, but rarer.
I will try some other radios, but maybe I am on the wrong path. Any ideas?
My network operator is Orange Romania - frequencies: GSM-900/1800 (GPRS, EDGE), 900/2100 MHz (UMTS, HSPA, HSPA+, DC-HSDPA).
Thank you,
Adrian.
EDIT: I forgot to mention that this did not happen on the original ROM with radio 0.16a.32.09.17_2, but I am unable to find it anywhere.

Is it just the data connection that is dropping out or is it a full signal drop?
Sent from my Evita

You did not say if you updated firmware to 5.xx to suit sense 5.
You should flash turges firmware in his stock 5.08.111.2 thread.
Sent from my One X using xda app-developers app

Hi!
Only the data has drops. Voice works fine.
What I did:
- Installed 3.18 RUU
- Unlocked boot loader
- Installed TWRP 2.6
- Installed CM 10.2
I did not install the firmware from the Stock 4.2.2 thread because, from what I read, that was only needed for a Sense 5 ROM, not for an AOSP one.

Which cm build are you running?
Sent from my Evita

CM 10.2 9.15 build, but the data issue was also present on RUU 3.18.
I'm now on the "HTC O2 2.29 (0.19as.32.09.20_3_10.107.32.25" radio and data seems OK for the last few hours.

Try flashing a different radio. Did you do a full wipe before installing the ROM?
Sent from my Evita

timmaaa said:
Try flashing a different radio. Did you do a full wipe before installing the ROM?
Sent from my Evita
Click to expand...
Click to collapse
Yes I did a full wipe before installing CM.
The O2 radio seems the most stable for me.
If this issue appears again, is there anything more I could do besides trying another radio?
Thanks!

There could be multiple reasons: radio, firmware, voltage settings, etc.
Sent from my Evita

Hi!
I've tried with the firmware from Turge's thread and I still have data connectivity issues.
Here is my current setup CM 10.2 9.18 nightly, Turge's firmware and TWRP 2.6:
D:\adt-bundle-windows-x86_64-20130729\sdk\platform-tools>fastboot getvar all
< waiting for device >
(bootloader) version: 0.5
(bootloader) version-bootloader: 2.15.0000
(bootloader) version-baseband: 1.31a.32.45.16_2
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 5.08.111.2
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno: HT***
(bootloader) imei: 35****
(bootloader) product: evita
(bootloader) platform: HBOOT-8960
(bootloader) modelid: PJ83*****
(bootloader) cidnum: 11111111
(bootloader) battery-status: good
(bootloader) battery-voltage: 4013mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-de589c6eef
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.085s
What I did (Had CM 10.2 9.15 nightly):
- Factory Reset
- Flashed the T-Mobile Sense 5 ROM + Root zip
- From fastboot flashed the firmware from the thread
- Factory Reset
- Flashed the CM 10.2 9.18 nightly.
What should I do now besides trying other radios?

adibe said:
I've tried with the firmware from Turge's thread and I still have data connectivity issues.
Here is my current setup CM 10.2 9.18 nightly, Turge's firmware and TWRP 2.6:
D:\adt-bundle-windows-x86_64-20130729\sdk\platform-tools>fastboot getvar all
< waiting for device >
(bootloader) version: 0.5
(bootloader) version-bootloader: 2.15.0000
(bootloader) version-baseband: 1.31a.32.45.16_2
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 5.08.111.2
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno: HT***
(bootloader) imei: 35****
(bootloader) product: evita
(bootloader) platform: HBOOT-8960
(bootloader) modelid: PJ83*****
(bootloader) cidnum: 11111111
(bootloader) battery-status: good
(bootloader) battery-voltage: 4013mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-de589c6eef
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.085s
What I did (Had CM 10.2 9.15 nightly):
- Factory Reset
- Flashed the T-Mobile Sense 5 ROM + Root zip
- From fastboot flashed the firmware from the thread
- Factory Reset
- Flashed the CM 10.2 9.18 nightly.
What should I do now besides trying other radios?
Click to expand...
Click to collapse
The firmware 2.15 suggestion is specific to data drops on Sense 5 ROMs (and past responses to you regarding the 2.15 firmware were clear on this). I don't think its going to help you at all on a CM10.2.
It also seems that you are hopping around a bit, asking about how to install the OTA or stock ROM, then going to CM10.2, so I'm not really sure what you are trying to accomplish.
You might check the CM10.2 thread regarding data drop issues. But trying other radios may be your best bet.

redpoint73 said:
The firmware 2.15 suggestion is specific to data drops on Sense 5 ROMs (and past responses to you regarding the 2.15 firmware were clear on this). I don't think its going to help you at all on a CM10.2.
It also seems that you are hopping around a bit, asking about how to install the OTA or stock ROM, then going to CM10.2, so I'm not really sure what you are trying to accomplish.
You might check the CM10.2 thread regarding data drop issues. But trying other radios may be your best bet.
Click to expand...
Click to collapse
Thanks! I will try other radios.
It's true that I've jumped around at first. I basically installed CM in tough of fixing my data drops, but after giving it a spin I've decided that I liked it more than the Sense 4+ or Sense 5. Now I'm 100 % committed to CM.

RUU needed for O2 UK Please.

Hi,
Had a look around and some reason cant find the answer (sure to be told I didnt look hard enough)
Im looking for a stock RUU which match these details
Code:
(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:
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) product: vle
(bootloader) platform: HBOOT-8960
(bootloader) modelid: PJ4010000
(bootloader) cidnum: O2___001
(bootloader) battery-status: good
(bootloader) battery-voltage: 3865mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-64bedd38
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
Been using custom roms for a while, but looking to go back to stock and start again if need be. Also cant seem to SuperCID this phone, any help on that would be great too.
Thanks

stoneblade said:
Hi,
Had a look around and some reason cant find the answer (sure to be told I didnt look hard enough)
Im looking for a stock RUU which match these details
Code:
(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:
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) product: vle
(bootloader) platform: HBOOT-8960
(bootloader) modelid: PJ4010000
(bootloader) cidnum: O2___001
(bootloader) battery-status: good
(bootloader) battery-voltage: 3865mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-64bedd38
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
Been using custom roms for a while, but looking to go back to stock and start again if need be. Also cant seem to SuperCID this phone, any help on that would be great too.
Thanks
Click to expand...
Click to collapse
no love?

Change your CID to another, which has RUU
Sent from my HTC One S using XDA Premium 4 mobile app

Have already tried, everytime I change it (following guide on here) it reverts back to original cid
Sent from my HTC One S using Tapatalk

Been told to downgrade my radio but reading guides says I can't do this on hboot 2.15 please could someone help point me the right direction. Just want to get back to stock
Sent from my HTC One S using Tapatalk

stoneblade said:
Been told to downgrade my radio but reading guides says I can't do this on hboot 2.15 please could someone help point me the right direction. Just want to get back to stock
Sent from my HTC One S using Tapatalk
Click to expand...
Click to collapse
Are you on MaximusHD rom? what are you using currently?

Hi I was using magiorom and having some reboots, so want to go back to stock(just ordered Nexus 5) ready to sell on the phone. Currently have zenrom installed but would love to be able to get back to stock either Europe ruu or original O2. In the past having phone rooted lowers price because some people don't want to have the root option, and some apps don't allow it eg Barclays or sky
Sent from my HTC One S using Tapatalk

Even a nanoid without super user or root would do, just back to stock as close as possible. Major noob mistake not to make my own nanoid when first started, learnt for next time!
Sent from my HTC One S using Tapatalk

stoneblade said:
Even a nanoid without super user or root would do, just back to stock as close as possible. Major noob mistake not to make my own nanoid when first started, learnt for next time!
Sent from my HTC One S using Tapatalk
Click to expand...
Click to collapse
Yeah I have a nandroid in my thread. Refer to my signature. It's for T-Mobile UK but it will work for you.

khan.orak said:
Yeah I have a nandroid in my thread. Refer to my signature. It's for T-Mobile UK but it will work for you.
Click to expand...
Click to collapse
Great thanks, is it rooted? I will have a look after breakfast
Sent from my HTC One S using Tapatalk

stoneblade said:
Great thanks, is it rooted? I will have a look after breakfast
Sent from my HTC One S using Tapatalk
Click to expand...
Click to collapse
No it's not.
Sent from my HTC One S using Tapatalk

khan.orak said:
No it's not.
Sent from my HTC One S using Tapatalk
Click to expand...
Click to collapse
Mate you have saved my life, phone back to semi normal stock (add tmobile logos) but its way closer than what was on there before. Im guessing I have to leave the bootloader unlocked but can install stock recovery?

stoneblade said:
Mate you have saved my life, phone back to semi normal stock (add tmobile logos) but its way closer than what was on there before. Im guessing I have to leave the bootloader unlocked but can install stock recovery?
Click to expand...
Click to collapse
Flash Stock recovery, and then if you want, you can lock bootloader.