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.
Related
Hi, I was trying to unroot my desire S, I have been following the desire fanatics guide on youtube (Can't post the link - sorry)
And I got up to the point where I was running the RUU utility. It started and then It got to about 50% in and then said Error, please use the correct RUU utility. (I'm guessing I've downloaded the incorrect RUU file.
So now, when I turn the phone on it goes right into the white menu with all the stuff on HBOOT etc.. fastboot I think it is, and it says security warning.
I'm guessing Its wiped the data but no longer has an OS to boot into. I honestly don't think it is bricked but I have no clue what to do from now!
I got my phone from mobiles.co.uk (A carphone warehouse subsidiary) and it is on contract with T-mobile. The phone had no branding on it from T-mobile so I guess its unlocked.
However I downloaded the T-mobile UK RUU and ran that..
Any advice on what to do from here? I'm currently in the process of downloading The Saga_HTC _Europe_1.28.401.1_Radio20.28b.30.0805U_38.03.02.11_M_release_177977_signed.exe
I don't even know if this will work because I can't get into any OS. I also read a lifehacker article and it said I can put a file onto the SD card and it will automatically run fixing the phone, making it better.
Please help me!
So far, I've tryed:
RUU_Saga_HTC_Europe_1.28.401.1_Radio_20.28b.30.0805U_38.03.02.11_M_release_177977_signed
and
RUU_Saga_TMO_UK_1.30.110.2_R_Radio_20.28b.30.0805U_38.03.02.11_M_release_180106_signed
But neither of these have worked, it gives me an error 140 saying I'm using the wrong version!
Can anybody tell me the correct version for an unlocked desire S bought in the UK from mobiles.co.uk?
Something that may of made this slightly more difficult for myself Is that While following the guide I followed, I used android flasher and flashed the bootloader included in the Revert to stock bundle kit thing, It was called engHBOOToverARX
I honestly have no Idea how I can fix this but Hopefully somebody else can!
can you tell me your current hboot version?
is your device detected by ADB?
if you have not set up ADB before read this below link
His device won't be detected by adb, only fastboot.
Run fastboot command "fastboot getvar all" and post the response.
Ok, this is what I get after fastboot getvar all:
Code:
(bootloader) version: 0.5
(bootloader) version-bootloader: 0.98.0000
(bootloader) version-baseband: 38.03.02.11_M
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 1.47.401.4
(bootloader) serialno: SH15NTJ00762
(bootloader) imei: 356708049175530
(bootloader) product: saga
(bootloader) platform: HBOOT-7230
(bootloader) modelid: PG8810000
(bootloader) cidnum: HTC__001
(bootloader) battery-status: good
(bootloader) battery-voltage: 4040mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: 361a7ba6
(bootloader) hbootpreupdate: 12
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.023s
And I have the ability to run adb commands but I don't know what command to use to check if its detecting my device, I type adb into cmd and loads of commands come up..
@imattacus
Okay you have a UK unbranded phone, I say this cause your CID is HTC__001 and your main version is 1.47.401.4.
So to fix you can either;
1) You can download this RUU (v1.47.401.4, hboot 0.98.0002) and run it from the PC.
Or
2) Change your main version (by getting shell root) then trying again with the 1.28.401.1 RUU. (but may be impossible since you can't get adb)
Option 1 is the easiest.
Same issue with Virgin Mobile RUU
Anyone got the correct RUU for me as I've got the same issue with a Virgin Mobile RUU. I followed the instructions for unrooting here. I was using the Virgin Mobile RUU listed on the link provided which was this list but I keep on getting error 140 when I run the RUU, telling me to use the correct one.
My bootloader is as follows:
SAGA PVT SHIP S-ON RL
HBOOT-0.98.0000
RADIO-38.03.02.15_M
eMMC-boot
I just need to find the right RUU version.
Any help would be greatly appreciated and as soon as possible.
Thanks
Just use Goldcard and try 1.47.401.4 again.
I also have a few problems with my Desire-S:
-my android email app keeps crashing when i try to open any email;
-official update aborts instalation (system 7) (even after hard reset).
So i decided to try fixing this via RUU. My phone is unbranded (bought in Slovenia's Vodafone), unrooted:
-android 2.3.3
-Sense 2.1
-Build 1.47.401.4
-Boot says: Saga PVT Ship S-on RL, Hbroot 0.98.0002, radio 3805.06.02.03_M
I tried to install:
-RUU_Saga_S_HTC_Europe_2.10.401.9_Radio_20.4801.30. 0822U_3822.10.08.04_M_release_234765_signed.exe
Every time i get an error 131- customer id error and message, that the ruu is wrong...
So i tried with the older one:
-RUU_Saga_HTC_Europe_1.47.401.4_Radio_20.28I.30.085 AU_3805.06.02.03_M_release_199410_signed.exe
And i keep getting error 140.
And i'm stuck here. Any help? I'd like to put on 2.3.5 with sense 3 without that email bug.... and i'm considering taking it to the repair service...
Thank You
i had in a way similar problem with imattacus...
only i can't run adb commands (adb devices returns no value)
i tried folowing ruu-s:
RUU_Saga_S_HTC_Europe_2.10.401.5_Radio_20.4801.30.0822U_3822.10.08.04_M_release_219480_signed
RUU_Saga_S_HTC_Europe_2.10.401.8_Radio_20.4801.30.0822U_3822.10.08.04_M_release_225161_signed
RUU's installed, but after boot phone was stuck in white screen with green htc.
after i installed this RUU my phone booted:
RUU_Saga_HTC_Europe_1.47.401.4_Radio_20.28I.30.085AU_3805.06.02.03_M_release_199410_signed
update>>
I checked for updates and there were some... After installing phone stuck on white screen...
I just whish to restore my phone to it's factory outofthebox state..
My getvar all result is::
Code:
(bootloader) version: 0.5
(bootloader) version-bootloader: 6.98.1002
(bootloader) version-baseband: 3822.10.08.04_M
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 13.10.401.8
(bootloader) serialno: HT13HTJ16283
(bootloader) imei: 355067040509788
(bootloader) product: saga
(bootloader) platform: HBOOT-7230
(bootloader) modelid: PG8810000
(bootloader) cidnum: HTC__032
(bootloader) battery-status: good
(bootloader) battery-voltage: 4020mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: 361a7ba6
(bootloader) hbootpreupdate: 12
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.017s
Any sugestions?
Goldcard
Sent from my HTC Desire S
I have installed ruu with the gold card, but I did removed it before update... Will try again and post back. Thank you very much for quick response!
>>>>>update...
Unfortunately, with gold card everything went same as before...
When i download and run update, phone reboots into update screen with progress bar, then reboots to update screen with same bar, then reboots to update screen without progress bar, then reboots and stays stuck on white screen...
i guess i have to find a way to unroot and s-on my device to the stock values before i try to update again...
my fastboot screen reads:
SAGA PVT SHIP S-OFF RL
HBOOT-6.98.1002
RADIO-3822.10.08.04_M
eMMC-boot
Mar 10 2011, 14:58:38
One more curious thing..
When i install RUU ver 1.47.401.4 (only i'm able to boot so far) image version that i overwrite (visible from RUU install screen) is 13.10.401.8... A bit large number, isn't it?
>>> FINAL UPDATE
SUCCESS!!!
as i suspected earlier, when i folowed first post on this topic i locked the phone, and then update worked.
have a nice day, everyone!
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...
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.
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
Dear all,
I tried to restore my phone to stock rom (for stability reasons)
however I tried RUU rom 3.18.502.6
Phone is Telstra Australia HTC one XL
now it goes into bootloop displaying HTC quietly brilliant logo then reboots and displays the same thing.
i can get into fastboot
fastboot getvar all
(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-OFF
(bootloader) serialno:
(bootloader) imei:
(bootloader) product: evita
(bootloader) platform: HBOOT-8960
(bootloader) modelid: PJ8312000
(bootloader) cidnum: 11111111
(bootloader) battery-status: good
(bootloader) battery-voltage: 3679mV
(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!
finished. total time: 0.069s
Any help would be much appreciated!!
Thank you
First thing you need to do is edit the IMEI out of your post, never post that publicly. Is there a reason you're using an at&t RUU? If you really want to return the device to stock you should use a Telstra RUU. The at&t RUU will work because you have s-off, but it isn't technically stock (plus tethering won't work on an at&t ROM). Have you tried running the RUU a second time?
Transmitted via Bacon
Good idea. Thanks! I have tried ruu with that file multiple times. I used it before people have said it is compatible with super cid and S-off
Is if worth trying another ruu?
Would it be compatible?
I just want a stock HTC rom as this is now my backup phone. Will just use it to stream music.
Cheers!
Because you're s-off you can use any Evita RUU.
http://androidruu.com/?developer=Evita
Transmitted via Bacon
hmm. Tried updating to HTC_One_X_RUU_5.18.502.1.exe
still no dice.
STill boot looping
then tried flashing the latest TWRP via fastboot.
can't even get into recovery. just reboots.
Any other ideas?
Many thanks!!
tzuyang said:
hmm. Tried updating to HTC_One_X_RUU_5.18.502.1.exe
still no dice.
STill boot looping
then tried flashing the latest TWRP via fastboot.
can't even get into recovery. just reboots.
Any other ideas?
Many thanks!!
Click to expand...
Click to collapse
also tried clear storage and factory reset. these just result in system rebooting.......