Related
Hi,
My battery has been acting up for almost half a year now and my usage time is half of what it was when i got it. I have been installing several different ROMs and kernels so I am at a lost on what's wrong. So I have decided to install a RUU to see if a total reset can fix my phone.
I found this page: http://www.androidfiles.org/ruu/?developer=Ville
Does anybody know which RUU from the link is the newest/best? Will I get updates from HTC when I do this?
Currently running trickdroid 10.3.2, bricked kernel, twrp 2.3.3, S-OFF and superCID - is there anything in particular I should know before doing this?
I have never installed a RUU before, hope somebody can help
anyone? Or perhaps just a part answer
teamet said:
anyone? Or perhaps just a part answer
Click to expand...
Click to collapse
Choose RUU according to your CID.
Must restore original CID to avaoid having problems with OTA updates.
If you receive OTA updates with superCID, a brick is going to welcome you.
Sent from my HTC One S using Tapatalk 4 Beta
khan.orak said:
Choose RUU according to your CID.
Must restore original CID to avaoid having problems with OTA updates.
If you receive OTA updates with superCID, a brick is going to welcome you.
Sent from my HTC One S using Tapatalk 4 Beta
Click to expand...
Click to collapse
Ok so i am in a similar fix.
I obtained S-Off/superCID the very next day i got my One S .. things were running smooth on stock. Looked out for some ROMS and finally installed one. Now I want to revert to my stock ROM while maintaining S-off/root. My problem is only that i don't find this ROM stable or the kernel .. just want to revert to stock.
Live in Pakistan, hence i doubt OTA is going to ever cause me any trouble. Could you please recommend which RRU should i install?
Would really appreciate some help from a fellow countryman
G.Rabbani said:
Ok so i am in a similar fix.
I obtained S-Off/superCID the very next day i got my One S .. things were running smooth on stock. Looked out for some ROMS and finally installed one. Now I want to revert to my stock ROM while maintaining S-off/root. My problem is only that i don't find this ROM stable or the kernel .. just want to revert to stock.
Live in Pakistan, hence i doubt OTA is going to ever cause me any trouble. Could you please recommend which RRU should i install?
Would really appreciate some help from a fellow countryman
Click to expand...
Click to collapse
Yes, you're right. Latest 4.2.2 Custom ROMs are having some bugs at the moment.
I need to know some details before I recommend anything.
1. S3/S4 version processor? (CPU-Z from play store will tell you that)
2. CID & MID (CID getter from play store will tell you that)
3. Last Stock firmware you had/installed?
4. HBOOT version?
Sent from my Nexus 7 using Tapatalk HD
khan.orak said:
Yes, you're right. Latest 4.2.2 Custom ROMs are having some bugs at the moment.
I need to know some details before I recommend anything.
1. S3/S4 version processor? (CPU-Z from play store will tell you that) -----> S4
2. CID & MID (CID getter from play store will tell you that) -----> 11111111
3. Last Stock firmware you had/installed? -----> JB 4.1.1
4. HBOOT version? -----> 2.15.0000
Sent from my Nexus 7 using Tapatalk HD
Click to expand...
Click to collapse
Thanks for the response I've responded to your queries inline.
G.Rabbani said:
Thanks for the response I've responded to your queries inline.
Click to expand...
Click to collapse
Okay that's good but I need to know the original CID that the phone was shipped with.
Also, I'll need to know MID (Model ID). You can find it out via CID GETTER. When you open the app search for the line [ro.aa.modelid]: PJxxxxxxx that's the model ID
Sent from my Nexus 7 using Tapatalk HD
khan.orak said:
Okay that's good but I need to know the original CID that the phone was shipped with.
Also, I'll need to know MID (Model ID). You can find it out via CID GETTER. When you open the app search for the line [ro.aa.modelid]: PJxxxxxxx that's the model ID
Sent from my Nexus 7 using Tapatalk HD
Click to expand...
Click to collapse
Thanks a lot for the hint. The CID on the top in CID getter was showing all ones. Ok so following is the information i made out from the verbosity, related to CID and Model ID and all of the rest that made sense to me.
ro.aa.cutomizationid: 452550
ro.aa.maincid: HTC__001
ro.aa.modelid: PJ4010000
ro.baseband: 1.11.50.05.28
ro.bootloader:2.15.0000
ro.aa.project: Ville_U_JB_45_S
ro.aa.rid: 386
G.Rabbani said:
Thanks a lot for the hint. The CID on the top in CID getter was showing all ones. Ok so following is the information i made out from the verbosity, related to CID and Model ID and all of the rest that made sense to me.
ro.aa.cutomizationid: 452550
ro.aa.maincid: HTC__001
ro.aa.modelid: PJ4010000
ro.baseband: 1.11.50.05.28
ro.bootloader:2.15.0000
ro.aa.project: Ville_U_JB_45_S
ro.aa.rid: 386
Click to expand...
Click to collapse
Ok. I deem this RUU to be the most suitable for you, which is Here.
Just run the RUU and it will do the job for you.
A word or two of caution here:
1. The RUU will erase everything.
2. After the RUU, you might want to change your CID back to HTC__001 because it has been rumored that HTC will release JellyBean 4.2.2 + Sense 5 for the One S. If you update the ONE S via OTA with SUPERCID, you will brick your device.
And anyway, SuperCID is not necessary at all for flashing Custom ROMs.
3. You will lose the Root for sure. But you can flash custom recovery + SuperSU again after going stock.
Edit: Oh! and match the MD5 hash of the downloaded file and the one on the server. MD5 checking utility is on XDA somewhere.
Edit 2: The CID in all cases comprises of 8 characters. i.e HTC__001 (8 chars), BM___001 (8 chars, my CID) etc. So when changing the CID, be sure to have an 8 character CID.
regards
khan.orak said:
Ok. I deem this RUU to be the most suitable for you, which is Here.
Just run the RUU and it will do the job for you.
A word or two of caution here:
1. The RUU will erase everything.
2. After the RUU, you might want to change your CID back to HTC__001 because it has been rumored that HTC will release JellyBean 4.2.2 + Sense 5 for the One S. If you update the ONE S via OTA with SUPERCID, you will brick your device.
And anyway, SuperCID is not necessary at all for flashing Custom ROMs.
3. You will lose the Root for sure. But you can flash custom recovery + SuperSU again after going stock.
Edit: Oh! and match the MD5 hash of the downloaded file and the one on the server. MD5 checking utility is on XDA somewhere.
regards
Click to expand...
Click to collapse
Thanks a lot brother!
Will follow your instructions. I was following a guide (All in one tool kit for ONE S) to achieve S-OFF for rooting and following that procedure the CID was reset as well. Not sure whether i can achieve S-OFF without meddling with the CID .... This being my first HTC after SGS and SGS2.
G.Rabbani said:
Thanks a lot brother!
Will follow your instructions. I was following a guide (All in one tool kit for ONE S) to achieve S-OFF for rooting and following that procedure the CID was reset as well. Not sure whether i can achieve S-OFF without meddling with the CID .... This being my first HTC after SGS and SGS2.
Click to expand...
Click to collapse
No problem at all.
Ok. Some interesting info for you again:
- S-OFF/SuperCID is not necessary for Rooting/Custom Recovery/Flashing Custom ROMs. You must have missed something.
- Just need to Unlock bootloader to Root/Flash custom recovery/custom ROM
khan.orak said:
No problem at all.
Ok. Some interesting info for you again:
- S-OFF/SuperCID is not necessary for Rooting/Custom Recovery/Flashing Custom ROMs. You must have missed something.
Click to expand...
Click to collapse
Hain ??
For all I have read, the reason for going after S-Off to begin with is essentially to gain capability to flash customer roms. I feel sorry for being a consistent bother, but could you please guide me towards a thread where I can learn rooting without messing with S-Off ...
G.Rabbani said:
Hain ??
For all I have read, the reason for going after S-Off to begin with is essentially to gain capability to flash customer roms. I feel sorry for being a consistent bother, but could you please guide me towards a thread where I can learn rooting without messing with S-Off ...
Click to expand...
Click to collapse
haha... Yes..
Well the All-in-One-Toolkit by Hasoon2000 is the one you have to follow. But no S-OFFing/SuperCID.
You just need the bootloader unlocked to get Rooted/Custom ROM/Recovery.
Since you have already unlocked the bootloader, I think it's not necessary to use the AIO toolkit again.
What we need is this:
- Run the RUU. (Run it first, and if it gives you errors, you might need to Relock your bootloader which is quite simple).
[For the latter part] - Then if you want to Root you stock ROM, we will have to flash custom Recovery, which again is quite simple and can be flashed from fastboot. I'll guide you on this part later when you are stock again. No biggy.
khan.orak said:
haha... Yes..
Well the All-in-One-Toolkit by Hasoon2000 is the one you have to follow. But no S-OFFing/SuperCID.
You just need the bootloader unlocked to get Rooted/Custom ROM/Recovery.
Since you have already unlocked the bootloader, I think it's not necessary to use the AIO toolkit again.
What we need is this:
- Run the RUU. (Run it first, and if it gives you errors, you might need to Relock your bootloader which is quite simple).
[For the latter part] - Then if you want to Root you stock ROM, we will have to flash custom Recovery, which again is quite simple and can be flashed from fastboot. I'll guide you on this part later when you are stock again. No biggy.
Click to expand...
Click to collapse
YOU ARE THE MAN! :good:
Take care bro. I'll catch up with you tomorrow after going through the RUU part :highfive:
G.Rabbani said:
YOU ARE THE MAN! :good:
Take care bro. I'll catch up with you tomorrow after going through the RUU part :highfive:
Click to expand...
Click to collapse
glad I could help
Sent from my HTC One S using Tapatalk 4 Beta
khan.orak said:
glad I could help
Sent from my HTC One S using Tapatalk 4 Beta
Click to expand...
Click to collapse
AOA Orak,
I installed the RUU and am back to stock now. Using the toolkit installed TWRP S4 recovery but when i try to go into recovery a red triangle with an exclamation mark appears; the phone stays with it for a while and then reboots to normal desktop. Tried it a number of times with the same result. Since i am unable to go into recovery, i cannot flash the supersu.zip and thus no root :/ Should I go for CWM?
G.Rabbani said:
AOA Orak,
I installed the RUU and am back to stock now. Using the toolkit installed TWRP S4 recovery but when i try to go into recovery a red triangle with an exclamation mark appears; the phone stays with it for a while and then reboots to normal desktop. Tried it a number of times with the same result. Since i am unable to go into recovery, i cannot flash the supersu.zip and thus no root :/ Should I go for CWM?
Click to expand...
Click to collapse
W/S
Okay first you boot into bootloader and tell me the details ..
To go into bootloader, turn off device, then hold power + vol down ... A white background with details..
Post them here.
Sent from my HTC One S using Tapatalk 4 Beta
khan.orak said:
W/S
Okay first you boot into bootloader and tell me the details ..
To go into bootloader, turn off device, then hold power + vol down ... A white background with details..
Post them here.
Sent from my HTC One S using Tapatalk 4 Beta
Click to expand...
Click to collapse
Ok so i figured it out in the meanwhile .. I had locked the bootloader before running the RUU. Unlocked it, installed recovery and flashed SU successfully.
So now I have two questions:
1- Do i need to re-lock the bootloader? If yes, will I still be able to flash custom roms?
2- How do i revert my original CID value? Will 'fastboot writecid HTC__001' do the trick? Are there any pre-requisites for it?
G.Rabbani said:
Ok so i figured it out in the meanwhile .. I had locked the bootloader before running the RUU. Unlocked it, installed recovery and flashed SU successfully.
So now I have two questions:
1- Do i need to re-lock the bootloader? If yes, will I still be able to flash custom roms?
2- How do i revert my original CID value? Will 'fastboot writecid HTC__001' do the trick? Are there any pre-requisites for it?
Click to expand...
Click to collapse
- Okay before anything, i would advise to flash TWRP 2.3.3.0 recovery and you will avoid many issues currently being faced with 2.5.0.0.
You can find 2.3.3.0 Here.
If you need help on flashing, ask away.
- now your questions:
1. No and No
2. You have to boot into bootloader and then go into FASTBOOT and write the command
fastboot oem writecid HTC__001
BTW, I assume you have adb+fastboot files on your PC?
Sent from my Nexus 7 using Tapatalk HD
khan.orak said:
fastboot oem writecid HTC__001
Click to expand...
Click to collapse
This only works if you are S-OFF
hTConeS | SoFF | ChaRmAnDrOiD | BuLLetprOOf
Inverted Sense 5 Theme Updates+Tweaks
Inverted Sense 4+
I am looking for a Stock T-Mobile Jelly Bean image that won't brick my phone. I tried searching for one, but I couldn't find anything or I found RUUs for outdated versions of HBoot. I am trying to revert back to stock, but I am sorta scared to do so with an outdated RUU. I have HBoot version 2.15 and Radio version 1.13.50.05.31. Thanks in advance.
Would this be the RUU I have to download? http://bugsylawson.com/files/file/1...531-10305008l-release-309489-signed-ics-2exe/
I would just prefer a nandroid backup of the stock image that I can just flash with CWM.
I downloaded the RUU, I just need to know if that is the correct one for my phone before I use it. I really don't want a bricked phone. I checked the MD5sum already and it matches, that is the only thing holding me back.
Sent from my One S using xda premium
I have ran that RUU with the same hboot and radio as you. Why do you think it would brick your phone? you haven't supercid and have locked your bootloader right?
(didn't download from that site though)
http://forum.xda-developers.com/showthread.php?t=2094414
Okay, thank you for the reassurance. I just am pretty paranoid about bricking my phone. I have been looking up how to use RUUs for the last day or so, I just couldn't find anything on how to select the right one. Thanks again.
I just checked out your link and I am downloading now. I do not have SuperCID and I will be looking my boot loader.
Sent from my One S using xda premium
OccupyDemonoid said:
Okay, thank you for the reassurance. I just am pretty paranoid about bricking my phone. I have been looking up how to use RUUs for the last day or so, I just couldn't find anything on how to select the right one. Thanks again.
I just checked out your link and I am downloading now. I do not have SuperCID and I will be looking my boot loader.
Sent from my One S using xda premium
Click to expand...
Click to collapse
If you are on TMOB US then it's for you. Furthermore, you can match thr CID of your phone to that in the RUU.exe --> Firmware.zip --> android-info.txt.
You'll have to extract firmware.zip from temporary files when you run RUU without connecting phone.
Sent from my Nexus 7 using Tapatalk HD
I ended up using that RUU that was linked earlier in this thread and everything went fine. I just don't have the stock recovery. I guess that isn't that much of a problem though.
Sent from my HTC VLE_U using xda premium
OccupyDemonoid said:
I ended up using that RUU that was linked earlier in this thread and everything went fine. I just don't have the stock recovery. I guess that isn't that much of a problem though.
Sent from my HTC VLE_U using xda premium
Click to expand...
Click to collapse
The RUU installs the Stock Recovery automatically. You don't have to do anything extra.
You can find stock recovery (if you want to keep it for any purpose) inside the RUU (extraction would require you to run the RUU and then extract the recovery from Temporary Files)
OR
you can find it in the forums.
Hmmm, that's strange. Oh well I guess. When I tried to go into the recovery it just showed a red exclamation mark with a phone under it. I don't really need a recovery right now. Thanks for letting me know where I can find it.
Sent from my HTC VLE_U using xda premium
OccupyDemonoid said:
Hmmm, that's strange. Oh well I guess. When I tried to go into the recovery it just showed a red exclamation mark with a phone under it. I don't really need a recovery right now. Thanks for letting me know where I can find it.
Sent from my HTC VLE_U using xda premium
Click to expand...
Click to collapse
I believe that is the stock recovery. The red exclamation mark is telling you that you don't have access to it. Perfectly normal.
tivofool said:
I have ran that RUU with the same hboot and radio as you. Why do you think it would brick your phone? you haven't supercid and have locked your bootloader right?
(didn't download from that site though)
http://forum.xda-developers.com/showthread.php?t=2094414
Click to expand...
Click to collapse
Can I also run this same RUU as quoted in this thread ?
I have the same radio but different hboot ...
SuperCID = HTC__001 <---- I got this right now, I will have to put in TMO CID before I run RUU, is that true?
VLE PVT SHIP S-ON RL
HBOOT-1.13.0000
RADIO-1-13.50.05.31
I would like to go back to Stock becuase after rooting and putting custom ROM (AOKP, I lost 4g, it was working before)
DroidLuvver said:
Can I also run this same RUU as quoted in this thread ?
I have the same radio but different hboot ...
SuperCID = HTC__001 <---- I got this right now, I will have to put in TMO CID before I run RUU, is that true?
VLE PVT SHIP S-ON RL
HBOOT-1.13.0000
RADIO-1-13.50.05.31
I would like to go back to Stock becuase after rooting and putting custom ROM (AOKP, I lost 4g, it was working before)
Click to expand...
Click to collapse
Yes, I think it will give you an error with that cid. Someone could correct me, but with s-off you can run whatever ruu you want.
tivofool said:
Yes, I think it will give you an error with that cid. Someone could correct me, but with s-off you can run whatever ruu you want.
Click to expand...
Click to collapse
I am planning on changing the CID to match what's in the firmware and then running this RUU but... what about my hboot.. it's different than what you guys have. Its 1.13
DroidLuvver said:
I am planning on changing the CID to match what's in the firmware and then running this RUU but... what about my hboot.. it's different than what you guys have. Its 1.13
Click to expand...
Click to collapse
It will install the newer hboot to 2.15
tivofool said:
It will install the newer hboot to 2.15
Click to expand...
Click to collapse
So I should be able to run the RUU with lower boot like mine and it will upgrade the boot to 2.15 -
Is it true that with 2.15 hboot, modifying the CID is not allowed ?
Any reason why I should stay with 1.13 HBOOT and not go to 2.15 Hboot? Meaning any disadvantages of upgrading to HBOOT 2.15 ?
Well, say you updated your phone via ota & your cid is European or something. And all of the ruus for that CID are lower hboots. If u are s-on and and needed to ruu you wouldn't be able to.
But there is a guide to run a ota.zip for those people, so it isn't hopeless.
So not too many disadvantages.
In fact I just installed the newest Rom and firmware today. So my hboot is 2.16.
And the gossip is that update will be officially put out by HTC in a few weeks.
Sent from my HTC One S using Tapatalk 2
Remember this.
if you want to go stock again in future (warranty purpose)
some providers have only provided an ota (only ruu with lower hboots) when upgrading to jb. So downgrading gets hard
It's not that easy to flash an ota as is a ruu.
If your s-off downgrading is no issue.
Verstuurd van mijn HTC One S met Tapatalk
Hi everyone,
This is my very first post and I'll admit I am a NOOB.
As I've searched XDA and Google for my questions, I am really at a loss and thought I would pose my question(s) to the community.
I have a Rogers HTC One X(Evita) running CM 10.0, I am currently S-ON, with TWERP 2.3.1
I would like to install the latest CM but it would seem my HBOOT (1.11) needs to be upgraded.
My first question is if my CID is Roger001 is this similar to being SuperCID?
If so, which firmware is recommended? Which is the latest HBOOT I should upgrade to?
I guess this brings me to my next question, what exactly do I need to be able to upgrade my HBOOT?
I've seen a few walkthroughs but none mention Roger001 as CID and I'd rather not risk bricking my phone.
If you need any other information, please let me know.
Any assistance is greatly appreciated.
You definitely need to update your phone in order to flash the latest cm ROM. But, with your phone in its current state you'll brick it. You don't have SuperCID (11111111), you'll definitely need to get that first, then get s-off, then you can RUU up to the latest. Links to everything you need are in this thread.
Sent from my Evita
Thanks Tim.
I'll give that a whirl and let you know how it turns out.
Another silly question, what exactly is RUU?
Sent from my One X using xda app-developers app
RUU stands for ROM Update Utility. It basically takes your phone back to being completely stock, including recovery. The beauty of being s-off when you run an RUU is the s-off status survives the process, and so will your unlocked bootloader. So all you need to do when it's finished is flash TWRP again via fastboot, then flash your ROM via TWRP.
Sent from my Evita
Ahh
That makes perfect sense!
If I wanted to stay stock, I could?
Sent from my One X using xda app-developers app
Yeah there's nothing stopping you. Then if you change your mind it's as simple as following the steps I mentioned before.
Sent from my Evita
I haven't had a chance to try anything as of yet but I've been doing some reading, could I use the One X Att all-in-one kit 3.0.1 to obtain SuperCID as well S-Off?
I tried another apparently popular program yesterday but it didn't work, as my CID is still Roger001.
Thanks!
Sent from my One X using xda app-developers app
Yeah you might as well try anything you can to get it done.
Sent from my Evita
Yes!
timmaaa said:
Yeah you might as well try anything you can to get it done.
Sent from my Evita
Click to expand...
Click to collapse
Hey timmaa,
Just wanted to say thanks for the help!
I managed to get CID 11111111, as well as S-OFF.
I've just relocked and I am currently downloading the Rogers stock RUU, with that comes HBoot 2.14 and the latest CM!
Thanks again:good::laugh:
Spoke too soon.. :S
asarrecchia said:
Hey timmaa,
Just wanted to say thanks for the help!
I managed to get CID 11111111, as well as S-OFF.
I've just relocked and I am currently downloading the Rogers stock RUU, with that comes HBoot 2.14 and the latest CM!
Thanks again:good::laugh:
Click to expand...
Click to collapse
So, I flashed that latest Rogers RUU using ARUWizard, everything looked to be okay, as now I am now on H-Boot 2.14.
However, I cant boot into anything..
For some reason, when it tries to boot up it shows the CyanogenMod logo when loading but nothing.
Windows recognizes my phone and tries to install new drivers but fails.
I can boot into the bootloader but when I hit recover, the screen goes black and then after awhile a red ! with a phone beneath it shows up.
Any ideas anyone?
asarrecchia said:
So, I flashed that latest Rogers RUU using ARUWizard, everything looked to be okay, as now I am now on H-Boot 2.14.
However, I cant boot into anything..
For some reason, when it tries to boot up it shows the CyanogenMod logo when loading but nothing.
Windows recognizes my phone and tries to install new drivers but fails.
I can boot into the bootloader but when I hit recover, the screen goes black and then after awhile a red ! with a phone beneath it shows up.
Any ideas anyone?
Click to expand...
Click to collapse
Ok, firstly you didn't need to relock your bootloader to run the RUU because you have s-off. And what exactly is aruwizard? And how did you flash CM after you ran the RUU?
Sent from my Evita
timmaaa said:
Ok, firstly you didn't need to relock your bootloader to run the RUU because you have s-off. And what exactly is aruwizard? And how did you flash CM after you ran the RUU?
Sent from my Evita
Click to expand...
Click to collapse
I followed the steps from the link you gave me, under the RUU section, as there was a guide on how to install an RUU for Rogers HTC One X.
It said to relock the phone, so, I did.
ARWizard was part of the guide.
The weird thing is, I didn't flash CM, I flashed the Rogers RUU, so, I'm not even sure how CM10 is even on my phone.
I can get to the Bootloader but I can't launch TWERP and my windows PC now doesn't recognize my phone, it says installing drivers but never does. I had HTC Sync installed in hopes that it would help, it didn't.
Is my only option to do a Factory Reset in Hboot? I've read ill lose all my info on the SD card.
Thanks
Which RUU did you run? Something has gone wrong.
Sent from my Evita
timmaaa said:
Which RUU did you run? Something has gone wrong.
Sent from my Evita
Click to expand...
Click to collapse
I followed the steps in the below thread to help me flash the RUU
http://forum.xda-developers.com/showthread.php?t=1658929&nocache=1
I went to this site to get the Stock image:
http://forum.xda-developers.com/showthread.php?p=37227608
It's 3.17.631.2
OTA_EVITA_UL_JB_45_S_Rogers_WWE_3.17.631.2_0.23a.3 2.09.29_10.128.32.34a_release_299850qstr7rxdbfuofl 6j.zip
I really do appreciate the help, by the way.
I'm not familiar with that method, but it seems to me that it doesn't do a full RUU. And evidently it hasn't because you still have cm on your phone. What hboot version does your phone list in bootloader now? You could just run the at&t 3.18 RUU which will do the whole job. You're s-off so it should be fine.
Sent from my Evita
timmaaa said:
I'm not familiar with that method, but it seems to me that it doesn't do a full RUU. And evidently it hasn't because you still have cm on your phone. What hboot version does your phone list in bootloader now? You could just run the at&t 3.18 RUU which will do the whole job. You're s-off so it should be fine.
Sent from my Evita
Click to expand...
Click to collapse
I am 2.14 HBOOT and S-off.
The problem is that while my Windows PC recognizes my phone, it doesnt load the drivers and therefore, I cant send any ADB commands.
I am not even able to go into TWERP.
How will I be able to run the AT&T if I cant push any ADB commands from my PC?
You don't need any adb commands to run an RUU, but you do need the pc to recognize the phone. I'd try uninstalling all drivers, then installing them again to see if it helps.
Sent from my Evita
Ota is not the same as aruwizard zip. Aru zip is exactly the same as Rom.zip you find inside ruu files, evita ones get the name pj83img.
Not sure why everyone thinks ota is ruu, nowhere is it refered to as being the same thing.
Maybe the firmware.zip in the ota managed to flash though hence your hboot and other firmware was upgraded.
If you follow the "or" method for flashing the zip it actually should work. The better correct answer is once s-off to download/install the latest ruu available that you want and ota up from there.
twistedddx said:
Ota is not the same as aruwizard zip. Aru zip is exactly the same as Rom.zip you find inside ruu files.
Not sure why everyone thinks ota is ruu, nowhere is it refered to as being the same thing.
Maybe the firmware.zip in the ota managed to flash though hence your hboot and other firmware was upgraded.
Click to expand...
Click to collapse
That's what I thought, but if he has used this aru zip, it's had the opposite effect. He now has the upgraded hboot but the previous ROM is still intact.
Sent from my Evita
timmaaa said:
That's what I thought, but if he has used this aru zip, it's had the opposite effect. He now has the upgraded hboot but the previous ROM is still intact.
Sent from my Evita
Click to expand...
Click to collapse
Thanks guys.
I'll try uninstalling the phone drivers and reinstall them, hopefully, it'll allow my PC to see my phone.
Worse case scenario, if my computer doesn't load the drivers for my phone, what are my options?
What if I select factory reset from HBOOT?
Hi guys,
As you can see in the title, it's impossible for me to upgrade my HTC One X to Android 4.2.2.
I recently relocked the bootloader, to hopefully succesfully upgrade my HTC One X JB 4.2.2 OTA update..
When I boot the phone, I get the notification that the update is ready to be installed, since it has already been downloaded.
When I tap "Install update", my phone turns off and immediately boots into fastboot, without being connected with a usb to the computer or so.
My question is;
How can it be that everytime I try to install the update, my phone boots into fastboot (bootloader)?
Thanks in advance
You don't have stock recovery installed?
Ota on modified phones is risky.
Are you on the correct stock ROM, correct firmware, s-off and supercid?
I would not attempt ota unless it was after ruu.
Sent from my One X using xda app-developers app
How do I RUU exactly??
Sent from my HTC One X using xda app-developers app
twistedddx said:
You don't have stock recovery installed?
Ota on modified phones is risky.
Are you on the correct stock ROM, correct firmware, s-off and supercid?
I would not attempt ota unless it was after ruu.
Sent from my One X using xda app-developers app
Click to expand...
Click to collapse
How do I RUU exactly? I don't know what s-off means, and supercid or something. Could you give some further explain, please?
Sent from my HTC One X using xda app-developers app
What ROM were you on when you tried to use the OTA?
If you don't know what SuperCID, RUU, and s-off mean I would strongly suggest you do some research before attempting to do anything else to your phone. Trying these things without a proper understanding could lead to you bricking your phone.
Sent from my Evita
timmaaa said:
What ROM were you on when you tried to use the OTA?
If you don't know what SuperCID, RUU, and s-off mean I would strongly suggest you do some research before attempting to do anything else to your phone. Trying these things without a proper understanding could lead to you bricking your phone.
Sent from my Evita
Click to expand...
Click to collapse
It's just crazy, because I'm on my stock rom.. Can it be possible it's because of the root files which are still in a file somewhere on my phone..??
Sent from my HTC One X using xda app-developers app
It's not that crazy, while you may have been on a stock ROM, having SuperCID and s-on while running an update are a sure fire way for something to go wrong.
But, if you don't have the stock recovery installed (you still have TWRP/CWM) it just won't work. Simply relocking the bootloader won't achieve anything. You need to make sure you have the stock recovery, but before all that you need to check your s-on/s-off status, and your CID.
Or you could just flash the stock 4.2.2 ROM that's in our development section, it's gonna be exactly the same as doing this update but without any of the hassle.
Sent from my Evita
timmaaa said:
It's not that crazy, while you may have been on a stock ROM, having SuperCID and s-on while running an update are a sure fire way for something to go wrong.
But, if you don't have the stock recovery installed (you still have TWRP/CWM) it just won't work. Simply relocking the bootloader won't achieve anything. You need to make sure you have the stock recovery, but before all that you need to check your s-on/s-off status, and your CID.
Or you could just flash the stock 4.2.2 ROM that's in our development section, it's gonna be exactly the same as doing this update but without any of the hassle.
Sent from my Evita
Click to expand...
Click to collapse
I already relocked my bootloader. I absolutely don't know how to s-off, still after 2 hours of Googling. What else?
Sent from my HTC One X using xda app-developers app
timmaaa said:
It's not that crazy, while you may have been on a stock ROM, having SuperCID and s-on while running an update are a sure fire way for something to go wrong.
But, if you don't have the stock recovery installed (you still have TWRP/CWM) it just won't work. Simply relocking the bootloader won't achieve anything. You need to make sure you have the stock recovery, but before all that you need to check your s-on/s-off status, and your CID.
Or you could just flash the stock 4.2.2 ROM that's in our development section, it's gonna be exactly the same as doing this update but without any of the hassle.
Sent from my Evita
Click to expand...
Click to collapse
Okay, so my CID is:
(bootloader) DEBUG: cid: HTC__E11
OKAY [ 0.106s]
finished. total time: 0.107s
I read somewhere that I have to change it to 1111111 to achieve SuperCID?
And I'm currently S-ON:
(ENDEAVORU PVT SHIP S-ON RL)
Ok well you're in the wrong forum then, this is the Evita forum. You have Endeavor so you'll want to find the HTC One X forum and ask again there, we have no experience with your phone here unfortunately so we can't really help you.
Sent from my Evita
You must flash the 4.0.4 RUU(HK、AT&T）first,next ota to 4.1.1 to 4.2.2.
elivastar said:
You must flash the 4.0.4 RUU(HK、AT&T）first,next ota to 4.1.1 to 4.2.2.
Click to expand...
Click to collapse
Dude, you're at it again giving wrong advice. Did you not read the other posts? He doesn't have our phone. Please, you need to educate yourself before you try to educate others, you don't know nearly enough to be giving advice.
@cvv4HOX
Don't take this person's advice, it does not apply to your phone.
Sent from my Evita
I know he didn't have the XL,but one x ota to sense5 order is same as our XL.
elivastar said:
I know he didn't have the XL,but one x ota to sense5 order is same as our XL.
Click to expand...
Click to collapse
That might be true, but are you experienced with his device and fully aware of any quirks that exist? I can tell you now that not even all the people who have our phone are aware of the quirks that exist for their own device.
Sent from my Evita
Hi guys, first time poster - I want to install the following custom rom...
http://forum.xda-developers.com/showthread.php?t=2442946
... and being new to android modding, do not want to brick it by doing something wrong.
I gather i need to set up superCID and then set to s-off - would anyone be able to point me in the right direction on how to do these correctly for a Telstra phone?
My phone is rooted with CWM, from whati gather (it says "ClockworkMod recovery" in recovery mode).
Thanks
jacen72 said:
Hi guys, first time poster - I want to install the following custom rom...
http://forum.xda-developers.com/showthread.php?t=2442946
... and being new to android modding, do not want to brick it by doing something wrong.
I gather i need to set up superCID and then set to s-off - would anyone be able to point me in the right direction on how to do these correctly for a Telstra phone?
My phone is rooted with CWM, from whati gather (it says "ClockworkMod recovery" in recovery mode).
Thanks
Click to expand...
Click to collapse
You might already have SuperCID, you can use a fastboot command to check. The command is:
Code:
fastboot oem readcid
If it comes back as anything other than 11111111 you can use this method to get SuperCID.
Once you have SuperCID you can use this method to get s-off.
Sent from my Evita
timmaaa said:
You might already have SuperCID, you can use a fastboot command to check. The command is:
Code:
fastboot oem readcid
If it comes back as anything other than 11111111 you can use this method to get SuperCID.
Once you have SuperCID you can use this method to get s-off.
Sent from my Evita
Click to expand...
Click to collapse
Thanks, i will take a closer look soon. Is it true that for Telstra phones the CID needs to be 22222222, or is 11111111 okay as well?
jacen72 said:
Thanks, i will take a closer look soon. Is it true that for Telstra phones the CID needs to be 22222222, or is 11111111 okay as well?
Click to expand...
Click to collapse
The 22222222 CID only applies to at&t phones trying to unlock their bootloader via htcdev, this is because at&t stock CID (cws__001) plus 11111111 CID have been blocked at htcdev. For your purposes 11111111 will be fine.
Sent from my Evita
timmaaa said:
The 22222222 CID only applies to at&t phones trying to unlock their bootloader via htcdev, this is because at&t stock CID (cws__001) plus 11111111 CID have been blocked at htcdev. For your purposes 11111111 will be fine.
Sent from my Evita
Click to expand...
Click to collapse
Thanks for the info - i know i need to superCID as i checked last night and CID was TELST001 (from memory). Will use 11111111.
No problems, did you use the fastboot command the check your CID? I only ask because there are apps available which claim to display your CID but they show the original CID, not the current one.
Sent from my Evita
timmaaa said:
No problems, did you use the fastboot command the check your CID? I only ask because there are apps available which claim to display your CID but they show the original CID, not the current one.
Sent from my Evita
Click to expand...
Click to collapse
I tried so many things last night i couldn't tell you exactly what i did, haha! Will try your way and see what it says.
A quick question - in regard to the facepalm link, it says "Download patcher and unzip it in your working directory" - can this be any folder on my phone (eg: Downloads)? I'm also guessing the other file (OneX.zip) goes in the same directory?
No you place the extracted patcher files and the PJ8312000-OneX.zip into your fastboot folder on your pc.
You need to have adb/fastboot and HTC drivers installed on your pc to do the s-off process.
Sent from my Evita
jacen72 said:
I tried so many things last night i couldn't tell you exactly what i did, haha
Click to expand...
Click to collapse
You should keep better track of things you are doing or you will end like NASA on Apollo 1 and not knowing what went wrong.
To repair something you need to know what you did to break it.
Big thanks timmaaa, have upgraded successfully!
twistedddx, you're not wrong - i should have kept an eye on what i was doing. Luckily for me, all went well!
Thanks again.
Glad to see you got it all sorted mate.
Sent from my Evita
Hi guys, since updating Android, i seem to find my service connection (no service) is being lost fairly easily - is there something i need to do in regard to this, or is it just me?!
Cheers
Which ROM are you on?
Sent from my Evita
timmaaa said:
Which ROM are you on?
Sent from my Evita
Click to expand...
Click to collapse
the one from the following link:
http://forum.xda-developers.com/showthread.php?t=2442946
You either need to update your firmware to 2.15 or just flash the Beastmode kernel.
Sent from my Evita
timmaaa said:
You either need to update your firmware to 2.15 or just flash the Beastmode kernel.
Sent from my Evita
Click to expand...
Click to collapse
Thanks, when you talk about beastmode, is the following link what you are referring to?
http://forum.xda-developers.com/showthread.php?t=1797251
Also, with firmware 2.15 - i would actually like to keep it as stock as possible, so perhaps the firmware upgrade would be the better option? I have found a link that looks like it goes to the correct download:
http://forum.xda-developers.com/showthread.php?p=45646878 - (see last post)
Would i be right in saying the instructions for updating the kernel would be the same as at the following link:
http://forum.xda-developers.com/showthread.php?t=2423735 - (OPTIONAL: Installing the Firmware)
Thanks again for your help.
The first link is incorrect, you can find the Beastmode kernel in our development section. The kernel you just install in recovery.
The last link you quoted is where you'll find the 2.15 firmware, and the install instructions see in the first post on that thread (it's a manual install using fastboot).
Sent from my Evita
timmaaa said:
The first link is incorrect, you can find the Beastmode kernel in our development section. The kernel you just install in recovery.
The last link you quoted is where you'll find the 2.15 firmware, and the install instructions see in the first post on that thread (it's a manual install using fastboot).
Sent from my Evita
Click to expand...
Click to collapse
Thanks - looks easy enough. Can i ask what why i would install Beastmode instead of the firmware upgrade? From what i gather, it is to overclock the CPU?
You can leave the Beastmode settings stock, it's just an easier and safer fix rather than upgrading firmware. You can OC if you wish to of course. There's always a small risk involved with anything that touches your hboot.
Sent from my Evita
timmaaa said:
You can leave the Beastmode settings stock, it's just an easier and safer fix rather than upgrading firmware. You can OC if you wish to of course. There's always a small risk involved with anything that touches your hboot.
Sent from my Evita
Click to expand...
Click to collapse
Thanks, maybe i will install beastmode instead then if it will help fix my connection issues. Sorry, but would you be able to point in the direction of where it is in the development section, i cannot seem to find it.
I promise if this works you wont have to hear my noob questions anymore!!