Database Info

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?

[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.

[Q] Firmware update 2.15 and 5.08

Having problems getting the latest firmware/ hboot installed on my att htc one xl. I did try turges but would not take the zip file. So instead i used carls zip through twrp and this is what i found out. Im currently running turges viperxl 4.2.0 with elementalx 8.3.2 kernal installed.
my getvar all:
(bootloader) version: 0.5
(bootloader) version-bootloader: 2.14.0000
(bootloader) version-baseband: 1.31a.32.45.16_2
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 3.18.502.6
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) product: evita
(bootloader) platform: HBOOT-8960
(bootloader) modelid: PJ8310000
(bootloader) cidnum: 11111111
(bootloader) battery-status: good
(bootloader) battery-voltage: 4163mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-97c9a06e
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
let me know what i need to do and what i did wrong. Thanks for the help appreciate you guys!

I have some questions about this too , I running cleanrom , if I flash turge 's firmware ,that's the tmobile version right , is there any way to revert back to the att version( 3.18 hboot 2.14, my current) to return to stock
Sent from my HTC One XL using xda app-developers app

mrmcshagbag said:
Having problems getting the latest firmware/ hboot installed on my att htc one xl. I did try turges but would not take the zip file. So instead i used carls zip through twrp and this is what i found out. Im currently running turges viperxl 4.2.0 with elementalx 8.3.2 kernal installed.
my getvar all:
(bootloader) version: 0.5
(bootloader) version-bootloader: 2.14.0000
(bootloader) version-baseband: 1.31a.32.45.16_2
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 3.18.502.6
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) product: evita
(bootloader) platform: HBOOT-8960
(bootloader) modelid: PJ8310000
(bootloader) cidnum: 11111111
(bootloader) battery-status: good
(bootloader) battery-voltage: 4163mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-97c9a06e
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
let me know what i need to do and what i did wrong. Thanks for the help appreciate you guys!
Click to expand...
Click to collapse
Did you flash Turge's firmware twice as per the instructions?
Sent from my Evita
---------- Post added at 01:30 PM ---------- Previous post was at 01:29 PM ----------
kevintran.98 said:
I have some questions about this too , I running cleanrom , if I flash turge 's firmware ,that's the tmobile version right , is there any way to revert back to the att version( 3.18 hboot 2.14, my current) to return to stock
Sent from my HTC One XL using xda app-developers app
Click to expand...
Click to collapse
I answered your question in the CR thread.
PS. Duplicate posts aren't allowed.
Sent from my Evita

mrmcshagbag said:
my getvar all:
(bootloader) version: 0.5
(bootloader) version-bootloader: 2.14.0000
(bootloader) version-baseband: 1.31a.32.45.16_2
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 3.18.502.6
(bootloader) version-misc: PVT SHIP S-OFF
let me know what i need to do and what i did wrong. Thanks for the help appreciate you guys!
Click to expand...
Click to collapse
The radio was updated, but hboot did not. My guess, is that you did not pick the option in AROMA to update hboot. You can just flash again, and pick the option to flash hboot.
---------- Post added at 11:58 AM ---------- Previous post was at 11:54 AM ----------
kevintran.98 said:
I have some questions about this too , I running cleanrom , if I flash turge 's firmware ,that's the tmobile version right , is there any way to revert back to the att version( 3.18 hboot 2.14, my current) to return to stock
Click to expand...
Click to collapse
Yes, you can always revert hboot with s-off (which is required to run Turge's firmware update, anyway).
But unless you want to run an AOSP ROM that does not support hboot 2.15, there shouldn't be any reason to revert hboot.

redpoint73 said:
The radio was updated, but hboot did not. My guess, is that you did not pick the option in AROMA to update hboot. You can just flash again, and pick the option to flash hboot.
---------- Post added at 11:58 AM ---------- Previous post was at 11:54 AM ----------
Yes, you can always revert hboot with s-off (which is required to run Turge's firmware update, anyway).
But unless you want to run an AOSP ROM that does not support hboot 2.15, there shouldn't be any reason to revert hboot.
Click to expand...
Click to collapse
Thanks for the info. Turges zip wouldn't flash at all for me tried 20 times. So i got carls twrp zip and it worked installed all but the kernal for fw update since im running elementalx on my viperxl rom. it updated everything but htboot. will this be a problem since im on an att phone or will this be okay.. also reflashed carls same as above still on 2.14 hboot.

mrmcshagbag said:
it updated everything but htboot. will this be a problem since im on an att phone or will this be okay.. also reflashed carls same as above still on 2.14 hboot.
Click to expand...
Click to collapse
Maybe, maybe not. Are you getting any signal issues or random reboots? If not, then the radio and other modules alone may have taken care of this. Or if you never had these problems to begin with, it might just not apply to you (not everyone gets these issues).
Being AT&T doesn't have any effect on what hboot you should have (2.14 versus 2.15). 2.15 is not even an official hboot version for AT&T yet anyway (might be once they release Sense 5 officially, or they might get their own hboot version).
I don't foresee to many problems being on hboot 2.14, as long as your phone is operating correctly. The only thing I can think of, is if AOSP devs decide in the future they want to force everyone to hboot 2.15 like they did with 2.14. If that happens, you won't be able to flash those ROMs, or you would have to find some way to upgrade hboot.

redpoint73 said:
Maybe, maybe not. Are you getting any signal issues or random reboots? If not, then the radio and other modules alone may have taken care of this. Or if you never had these problems to begin with, it might just not apply to you (not everyone gets these issues).
Being AT&T doesn't have any effect on what hboot you should have (2.14 versus 2.15). 2.15 is not even an official hboot version for AT&T yet anyway (might be once they release Sense 5 officially, or they might get their own hboot version).
I don't foresee to many problems being on hboot 2.14, as long as your phone is operating correctly. The only thing I can think of, is if AOSP devs decide in the future they want to force everyone to hboot 2.15 like they did with 2.14. If that happens, you won't be able to flash those ROMs, or you would have to find some way to upgrade hboot.
Click to expand...
Click to collapse
I see. Yeah i had to flash the 3.18 radio and wifi partitions back because carls was giving me problems. i only seem to get reboots during music playback with screen off via htc music.

Problem with flashing

Hi. It was long time ago I played with Sensation. A friend of mine brought his phone asking for help. That's the story:
He had problems with ARHD installed, wanted to clean flash. He wiped and started to install ROM. Android_Revolution_HD_Super_Wipe_Sensation.zip was used.
Firmware was 3.33 universal, hboot original 1.29 was downgraded and unlocked previously via controlbear method.
Phone had problems with entering into CWM, so he flashed CWM. No go.
He flashed firmware again and on bootscreen we have now:
LOCKED
s-off
hboot 1.29.0000
Mar 2 2012
fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.29.0000
(bootloader) version-baseband: N/A
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 1.24.401.1
(bootloader) serialno:
(bootloader) imei:
(bootloader) product: pyramid
(bootloader) platform: HBOOT-8260
(bootloader) modelid: PG5813000
(bootloader) cidnum: HTC__001
(bootloader) battery-status: good
(bootloader) battery-voltage: 3780mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: 705f86f6
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
Click to expand...
Click to collapse
Looks like radio is missing ( he said about some problems when he tried RUU for first time.
Now:
Unable to install RUU - no phone connected (phone states fastbootUSB)
Unable to install firmware fron sdcard, unable to change CID.
How to bring it to life?
Thanks, Mike

sp5it said:
Hi. It was long time ago I played with Sensation. A friend of mine brought his phone asking for help. That's the story:
He had problems with ARHD installed, wanted to clean flash. He wiped and started to install ROM. Android_Revolution_HD_Super_Wipe_Sensation.zip was used.
Firmware was 3.33 universal, hboot original 1.29 was downgraded and unlocked previously via controlbear method.
Phone had problems with entering into CWM, so he flashed CWM. No go.
He flashed firmware again and on bootscreen we have now:
LOCKED
s-off
hboot 1.29.0000
Mar 2 2012
Looks like radio is missing ( he said about some problems when he tried RUU for first time.
Now:
Unable to install RUU - no phone connected (phone states fastbootUSB)
Unable to install firmware fron sdcard, unable to change CID.
How to bring it to life?
Thanks, Mike
Click to expand...
Click to collapse
the device still has gb firmware
that's why you can't boot the rom(if i understand well)
try this
http://forum.xda-developers.com/showthread.php?t=1459767
flash 3.33 universal
follow the indtructions to the letter
and before flashing check md5 sums(important)

I tried 3.33 FW.
I have message: [7]Bootloader - Fail-PU
Update fail.
M

sp5it said:
I tried 3.33 FW.
I have message: [7]Bootloader - Fail-PU
Update fail.
M
Click to expand...
Click to collapse
that is not good
ok then since you are on S-OFF change your cid to supercid
then use again any ruu.exe
best wishes

[Q] Back to Stock

Before I installed CM 10.2, I backed up everything in TWRP 2.5.0.0. I then upgraded to TWRP 2.7.0.0 and installed CM11.
I don't like them and want to go back to my stock rom. Do I need TWRP to be back to 2.5.0.0? Do I need to do the fastboot boot boot.img thing again? (my back up from 2.5.0.0 doesn't have a boot.img file in it).
Any help would be greatly appreciated. Thank you

Fastboot flash 2.5.0.0
Then try recover you're stock rom.
Stock is awesome in audio, with Beats Audio integrated & "Ultimate Xperia HTC Fusion:
https://code.google.com/p/htc-one-s...?name=Ultimate Xperia HTC Fusion.zip&can=2&q=
New roms are les eating ram, but audio suck.

null0seven said:
Fastboot flash 2.5.0.0
Then try recover you're stock rom.
Stock is awesome in audio, with Beats Audio integrated & "Ultimate Xperia HTC Fusion:
New roms are les eating ram, but audio suck.
Click to expand...
Click to collapse
Thank you for the help with cm 10.2 and 11, my battery life is terrible and my phone gets extremely hot. Then as you say, the audio isn't as good and the keyboard is terrible

jake000 said:
Thank you for the help with cm 10.2 and 11, my battery life is terrible and my phone gets extremely hot. Then as you say, the audio isn't as good and the keyboard is terrible
Click to expand...
Click to collapse
I'm a bit confused as to what I need to do. I either want a custom rom (kernal?) with good battery life or my original back on.
Based on the following, what RUU do I need to get?
C:\Android>fastboot getvar all
(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) serialno: ****
(bootloader) imei: ****
(bootloader) product: vle
(bootloader) platform: HBOOT-8960
(bootloader) modelid: PJ4010000
(bootloader) cidnum: VODAP001
(bootloader) battery-status: good
(bootloader) battery-voltage: 3768mV
(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
Thank you

jake000 said:
I'm a bit confused as to what I need to do. I either want a custom rom (kernal?) with good battery life or my original back on.
Based on the following, what RUU do I need to get?
C:\Android>fastboot getvar all
(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) serialno: ****
(bootloader) imei: ****
(bootloader) product: vle
(bootloader) platform: HBOOT-8960
(bootloader) modelid: PJ4010000
(bootloader) cidnum: VODAP001
(bootloader) battery-status: good
(bootloader) battery-voltage: 3768mV
(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
Thank you
Click to expand...
Click to collapse
Looks like you will need the JellyBean ruu for your carrier if you need help with the ruu look here
http://forum.xda-developers.com/showthread.php?t=2678700
Sent from my One S using Tapatalk

Flashalot said:
Looks like you will need the JellyBean ruu for your carrier if you need help with the ruu look here
http://forum.xda-developers.com/showthread.php?t=2678700
Sent from my One S using Tapatalk
Click to expand...
Click to collapse
Thank you for the link to your guide Which JB one do I need? My phone was from Vodafone UK. Do I need an RUU one or an OTA one? How do I flash the stock recovery?
You seem very experienced with flashing. What would you recommend for good battery life?
Thank you

jake000 said:
Thank you for the link to your guide Which JB one do I need? My phone was from Vodafone UK. Do I need an RUU one or an OTA one? How do I flash the stock recovery?
You seem very experienced with flashing. What would you recommend for good battery life?
Thank you
Click to expand...
Click to collapse
flash this RUU: RUU_Ville_U_ICS_40_S_Vodafone_UK_2.38.161.6_Radio_1.08es.50.02.21_10.09c.50.04L_release_280400_signed.exe
from here
http://androidruu.com/?developer=Ville
its ICS but u'll get jb update on first boot.
make sure u're s-off.
there is no jb ruu avaliable for our CID.

bilal_liberty said:
flash this RUU: RUU_Ville_U_ICS_40_S_Vodafone_UK_2.38.161.6_Radio_1.08es.50.02.21_10.09c.50.04L_release_280400_signed.exe
from here
http://androidruu.com/?developer=Ville
its ICS but u'll get jb update on first boot.
make sure u're s-off.
there is no jb ruu avaliable for our CID.
Click to expand...
Click to collapse
Thank you I will start reading about doing S-Off.

Best stock rom:
http://forum.xda-developers.com/showthread.php?t=2082451
Thank you!

null0seven said:
Best stock rom:
http://forum.xda-developers.com/showthread.php?t=2082451
Thank you!
Click to expand...
Click to collapse
Thank you just to make sure, I would use the Vodafone one?

null0seven said:
Best stock rom:
http://forum.xda-developers.com/showthread.php?t=2082451
Thank you!
Click to expand...
Click to collapse
I just installed the one from the link and it asked about updating an OTA update. I said yes, it downloaded but wouldn't install. For now, i've gone back to CM11. If I can get better battery life, I will keep CM11. I understand I need a different kernel to help with that. Not sure which one and that's the boot.img file I think?
Thank you

The OTA update (401.9) i could not install it.
Android 4.4.2 eat fewer resources. I like: TwistedKat, EOS, Resurrection Remix, CandyKat, Carbon, Slim, Codename Lungo.
For battery life, disable everything you don't use (in particular bluetooth, wifi, GPS, data, location). Uninstall apps. you dont use.

null0seven said:
The OTA update (401.9) i could not install it.
Android 4.4.2 eat fewer resources. I like: TwistedKat, EOS, Resurrection Remix, CandyKat, Carbon, Slim, Codename Lungo.
For battery life, disable everything you don't use (in particular bluetooth, wifi, GPS, data, location). Uninstall apps. you dont use.
Click to expand...
Click to collapse
This is the OTA file: OTA_Ville_U_JB_45_S_Vodafone_UK_3.16.161.9_1.11.50.05.28_10.27.50.08L_release_3022141tqgb65s4u2oovvj.zip
I have disabled stuff like you mentioned and have CM11 running the same as I had my stock ROM running and I used to get 2 or 3 times better battery life.
I will look into the other ROMs you suggested. Thank you for the help

I updated TWRP to 2.7.0.8 and installed Codename Lungo. It seems better so far and the battery is lasting longer as well. I will post tomorrow again after seeing how well my battery lasts on a full charge. Thanks again for the help

After 5 days with lungo, the battery life is a lot better than cm11 but still bad compared to my stock ROM. I was originally on ICS. Does that require less battery or are there new features in kitkat that drain the battery? Thank you

Lungo is very slim. Almost "nude".
4.4 rom are much smaler than stock rom. Some 4.4 have 120-130mb.
Some stock rom have 1 - 1,2Gb. Because "sense" and applications, languages included.
Applications on you're phone ar working in background. So, eat resources.

I understand what you're saying about applications running in the background but I have my apps set up exactly the same as I did on my stock ROM and the battery life and heat problems are really bad. I really like not having the bloatware on here but I'd prefer my battery to last longer. Thank you again for your help

As you can see most of the custom ROMs are made after CM11.
Depends on what the creator likes and put into rom.