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.
Related
Hi All,
I am having trouble reverting my HTC One S back to stock. I have tried several different RUUs but receive various errors with each. To be honest, I'm not even sure if I am using the correct RUUs.
Phone details:
(bootloader) version: 0.5
(bootloader) version-bootloader: 2.13.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: T-MOB005
(bootloader) battery-status: good
(bootloader) battery-voltage: 4128mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-26dff973
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
I have read through the forums but just can't find a solution that works. Please help!
Wow I thought someone would've replied to this already?
I had the exact same problem when I tried to flash my current ROM incorrectly. This link helped me immensly:
http://www.htconeforum.com/forum/ht...unbrick-restore-htc-one-s-stock-relocked.html
IntelligentAj said:
Wow I thought someone would've replied to this already?
I had the exact same problem when I tried to flash my current ROM incorrectly. This link helped me immensly:
Click to expand...
Click to collapse
I was also expecting a little more help..
Just taken a look at the link - thanks! - and it sets out the same process as I have been following. I think my main issue is finding a correct RUU. I have tried the TMOUS 2.35 which gave error 130 (model ID error) and the JB HTC Europe which gave error 132 (signature error)...
Based on my information above, can anyone send me a link to a correct RUU? I am on T-Mobile UK.
Anyone have any ideas for an RUU that would work for me?
Have just changed my CID to HTC__001 to see if it made any difference, but I still get the same errors as before. Please help!!
Dammermann said:
Have just changed my CID to HTC__001 to see if it made any difference, but I still get the same errors as before. Please help!!
Click to expand...
Click to collapse
Sorry man I thought that would've helped, I'll look for the ROM today
Update found this page with what looks the RUU for you though I'm not sure which version you have...
http://forum.gsmhosting.com/vbb/archive/t-1565294.html
The RUU: RUU_VILLEC2_U_ICS_40_S_HTC_Europe_2.15.401.100_Rad io_16.21.20.02U_16.09.20.11_M2
Also what radio do you have? You should be able to see your radio on the Fastboot screen
Thanks again - all my information is in my first post. Radio 1.11.50.05.28 and hboot 2.13.....
I find it unbelievable that these forums encourage people to move on to custom roms but do not help with any issues you then encounter!
Did you try the RUU in my post?
Sent from my One S using xda app-developers app
Dont have a nandroid from your original romfiles?
You want to go stock tmobile? Then you need the UK tmob ruu.
Or just stock HTC? Use the original UK htc-cid instead of HTC__001. Then run the 2.31 ruu.
Look here for the ruu
http://www.androidfiles.org/ruu/?dir=Ville
I dont see any UK tmobile ruus, i only see a german ruu, you could try that since EU ruus almost have all languages, and are mostly the same.
Verstuurd van mijn One S met Tapatalk
---------- Post added at 03:04 PM ---------- Previous post was at 02:56 PM ----------
IntelligentAj said:
Did you try the RUU in my post?
Sent from my One S using xda app-developers app
Click to expand...
Click to collapse
I think its for the S3 version (villeC2) if you have a S4 device dont flash. Wouldnt work anyways
Verstuurd van mijn One S met Tapatalk
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...
So i'm new here and was messing around with the phone and exploring the different things I can do with this phone.
I want to go back to stock ROM, my problem is that I do not know my original cid before I rooted it. Is this a problem here is my main-ver information
(bootloader) version: 0.5
(bootloader) version-bootloader: 2.14.0000
(bootloader) version-baseband: 0.24p.32.09.06
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 3.18.502.6
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: XXXXXXXX
(bootloader) imei: XXXXXXXXXXXX
(bootloader) product: evita
(bootloader) platform: HBOOT-8960
(bootloader) modelid: PJ8310000
(bootloader) cidnum: 11111111
(bootloader) battery-status: good
(bootloader) battery-voltage: 4145mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-97c9a06e
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
I apologize greatly if I can not find this anywhere on the forums. I have access to a Linux box if that helps. I am trying to just get back to at&t bloatware rom.
You could just get s-off so then you can run an RUU without worrying. S-off thread is here.
Sent from my Evita
---------- Post added at 05:01 AM ---------- Previous post was at 05:00 AM ----------
Or you could just flash a stock ROM from the Android Development section.
Sent from my Evita
I found my RUU and got the Rom_01.zip and Rom_02.zip
Rom_02.zip - SFX ZIP archive, unpacked size 1,680,452,716 bytes
that file has boot in there and recovery could I just flash that zip and be ok?
timmaaa said:
You could just get s-off so then you can run an RUU without worrying. S-off thread is here.
Sent from my Evita
---------- Post added at 05:01 AM ---------- Previous post was at 05:00 AM ----------
Or you could just flash a stock ROM from the Android Development section.
Sent from my Evita
Click to expand...
Click to collapse
How did you retrieve those zips from an RUU? An RUU is an exe file.
And why did you even do that? I gave you the options you should try.
Sent from my Evita
scrizo said:
I found my RUU and got the Rom_01.zip and Rom_02.zip
Rom_02.zip - SFX ZIP archive, unpacked size 1,680,452,716 bytes
that file has boot in there and recovery could I just flash that zip and be ok?
Click to expand...
Click to collapse
I would NOT mess with it. Both the Jellybean RUU and OTA will brick the phone, so its not exclusive to the RUU, and running the extracted file may still brick you.
The consequences are catastrophic (a true brick, only fixable by JTAG), so its not worth the risk when easy and low risk options exist. Either just S-off (as previously suggested) or another option is to change the CID back to your proper carriers ID.
I unencrypted them and extracted them. In regards to S-off I believe I have it except my phone won't run the SuperSU.zip file, I have Tampered and Unlocked on my bootloader screen.
timmaaa said:
How did you retrieve those zips from an RUU? An RUU is an exe file.
And why did you even do that? I gave you the options you should try.
Sent from my Evita
Click to expand...
Click to collapse
If you have s-off it will say so in your bootloader.
Sent from my Evita
Ok looking now. Will let you know.
timmaaa said:
If you have s-off it will say so in your bootloader.
Sent from my Evita
Click to expand...
Click to collapse
Followed steps and now have S-OFF !
timmaaa said:
If you have s-off it will say so in your bootloader.
Sent from my Evita
Click to expand...
Click to collapse
Ok, now you can run an RUU to get back to stock. Don't mess with it though, just run the exe program.
Sent from my Evita
Successfully installed ViperXL ROM
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.
I'm really in need of help here
so first some background, i have a verizon htc one m8 being used on a gsm carrier outside of the us..i had the latest digital high rom running with his 5.0 firmware and supercid as well as googleplay MID
today i tried to flash the latest GPE firmware 5.0.1 and after a sucessfull flash the phone went back to the bootloader screen but this time its black and not white as before and for some reason it deleted my os and partitions..now i am stuck in bootloader and even tho i am able to flash twrp recovery each time i install a rom via RUU (in this case stock gpe rom since i changed the phone to gpe) it will not boot into the rom..ive tried and searched all day but cant find anything that helps
i tried flashing digital highs's firmware again but it does not change/overwrite the gpe firmware
and i am unable to flash a stock verizon RUU because the MID has changed..
BTW my sdcard slot does not work
C:\android-tools>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.19.0.0000
(bootloader) version-baseband: 1.21.213311491.A04G
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 3.11.1700.5
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno: HT43XSF01633
(bootloader) imei: 990004998541332
(bootloader) imei2: Not Support
(bootloader) meid: 99000499854133
(bootloader) product: m8_wlv
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B17000
(bootloader) cidnum: 11111111
(bootloader) battery-status: good
(bootloader) battery-voltage: 0mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: c88f4560
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.029s
kooliebwoy said:
I'm really in need of help here
so first some background, i have a verizon htc one m8 being used on a gsm carrier outside of the us..i had the latest digital high rom running with his 5.0 firmware and supercid as well as googleplay MID
today i tried to flash the latest GPE firmware 5.0.1 and after a sucessfull flash the phone went back to the bootloader screen but this time its black and not white as before and for some reason it deleted my os and partitions..now i am stuck in bootloader and even tho i am able to flash twrp recovery each time i install a rom via RUU (in this case stock gpe rom since i changed the phone to gpe) it will not boot into the rom..ive tried and searched all day but cant find anything that helps
i tried flashing digital highs's firmware again but it does not change/overwrite the gpe firmware
and i am unable to flash a stock verizon RUU because the MID has changed..
BTW my sdcard slot does not work
C:\android-tools>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.19.0.0000
(bootloader) version-baseband: 1.21.213311491.A04G
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 3.11.1700.5
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno: HT43XSF01633
(bootloader) imei: 990004998541332
(bootloader) imei2: Not Support
(bootloader) meid: 99000499854133
(bootloader) product: m8_wlv
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B17000
(bootloader) cidnum: 11111111
(bootloader) battery-status: good
(bootloader) battery-voltage: 0mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: c88f4560
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.029s
Click to expand...
Click to collapse
Pm me teamviewer info and I can help you.
---------- Post added at 05:50 PM ---------- Previous post was at 05:06 PM ----------
kooliebwoy said:
I'm really in need of help here
so first some background, i have a verizon htc one m8 being used on a gsm carrier outside of the us..i had the latest digital high rom running with his 5.0 firmware and supercid as well as googleplay MID
today i tried to flash the latest GPE firmware 5.0.1 and after a sucessfull flash the phone went back to the bootloader screen but this time its black and not white as before and for some reason it deleted my os and partitions..now i am stuck in bootloader and even tho i am able to flash twrp recovery each time i install a rom via RUU (in this case stock gpe rom since i changed the phone to gpe) it will not boot into the rom..ive tried and searched all day but cant find anything that helps
i tried flashing digital highs's firmware again but it does not change/overwrite the gpe firmware
and i am unable to flash a stock verizon RUU because the MID has changed..
BTW my sdcard slot does not work
C:\android-tools>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.19.0.0000
(bootloader) version-baseband: 1.21.213311491.A04G
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 3.11.1700.5
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno: HT43XSF01633
(bootloader) imei: 990004998541332
(bootloader) imei2: Not Support
(bootloader) meid: 99000499854133
(bootloader) product: m8_wlv
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B17000
(bootloader) cidnum: 11111111
(bootloader) battery-status: good
(bootloader) battery-voltage: 0mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: c88f4560
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.029s
Click to expand...
Click to collapse
And don't do anything else in the meantime to it.
dottat said:
Pm me teamviewer info and I can help you.
---------- Post added at 05:50 PM ---------- Previous post was at 05:06 PM ----------
And don't do anything else in the meantime to it.
Click to expand...
Click to collapse
thanks alot for the response..It looks like i have found a solution....
it seems that the hboot got updated which caused the problem i downloaded firewaters hboot and flashed it which allowed me to sideload dh custom rom and with that as soon as i got into the rom i changed back to VZW official 4.4.4 firmware to get the latest compatible hboot and then did another flash of dh's custom 5.0 firmware and finally reflashed the OS with my prefered settings and im currently updating all my apps..so far the device functions fine
I hope this helps someone else who may get into this dilemma..
kooliebwoy said:
thanks alot for the response..It looks like i have found a solution....
it seems that the hboot got updated which caused the problem i downloaded firewaters hboot and flashed it which allowed me to sideload dh custom rom and with that as soon as i got into the rom i changed back to VZW official 4.4.4 firmware to get the latest compatible hboot and then did another flash of dh's custom 5.0 firmware and finally reflashed the OS with my prefered settings and im currently updating all my apps..so far the device functions fine
I hope this helps someone else who may get into this dilemma..
Click to expand...
Click to collapse
helped me ty
Same issue with my m8 whl
kooliebwoy said:
thanks alot for the response..It looks like i have found a solution....
it seems that the hboot got updated which caused the problem i downloaded firewaters hboot and flashed it which allowed me to sideload dh custom rom and with that as soon as i got into the rom i changed back to VZW official 4.4.4 firmware to get the latest compatible hboot and then did another flash of dh's custom 5.0 firmware and finally reflashed the OS with my prefered settings and im currently updating all my apps..so far the device functions fine
I hope this helps someone else who may get into this dilemma..
Click to expand...
Click to collapse
hi i have an htc one m8_whl(sprint unlocked gsm bought from aliexpress refurbished). S-off Unlocked boot loader, Rooted. it was on 4.4.2 i tried to flash this rom using adbRUU-HTC_One_M8_GPE_5.1-4.04.1700.4.zip(from graffixnyc ). i had installed twrp custom recovery before. now when i flashed this rom after i rebooted its just stuck at boot loader page. i can go to recovery options and i did sideload this rom again but it didn't work. same stuck at boot loader page. please help me with this situation. i really wanna install GPE rom on my phone.
ksingh007 said:
hi i have an htc one m8_whl(sprint unlocked gsm bought from aliexpress refurbished). S-off Unlocked boot loader, Rooted. it was on 4.4.2 i tried to flash this rom using adbRUU-HTC_One_M8_GPE_5.1-4.04.1700.4.zip(from graffixnyc ). i had installed twrp custom recovery before. now when i flashed this rom after i rebooted its just stuck at boot loader page. i can go to recovery options and i did sideload this rom again but it didn't work. same stuck at boot loader page. please help me with this situation. i really wanna install GPE rom on my phone.
Click to expand...
Click to collapse
sprint isnt a gsm native phone. You are in the verizon section and likely will have more luck in either the regular M8 section and likely less luck in the sprint section. You will have no luck here.....
Need Help plz
dottat said:
Pm me teamviewer info and I can help you.
---------- Post added at 05:50 PM ---------- Previous post was at 05:06 PM ----------
And don't do anything else in the meantime to it.
Click to expand...
Click to collapse
Hello plz help me out my htc m8 just got dead, i was going back to stock with ARU wizard after 80% phone got stuck and now dead tried all methods volume+power buttons but no luck so plz help me
ok_then_so said:
Hello plz help me out my htc m8 just got dead, i was going back to stock with ARU wizard after 80% phone got stuck and now dead tried all methods volume+power buttons but no luck so plz help me
Click to expand...
Click to collapse
Is your battery dead?
Sent from my HTC6535LVW using Tapatalk
dottat said:
Pm me teamviewer info and I can help you.
---------- Post added at 05:50 PM ---------- Previous post was at 05:06 PM ----------
And don't do anything else in the meantime to it.
Click to expand...
Click to collapse
I need HTC Desire 620G dual sim stock rom. Can you please help me sir.
punkshamil said:
I need HTC Desire 620G dual sim stock rom. Can you please help me sir.
Click to expand...
Click to collapse
No.
Sent from my XT1575 using Tapatalk