Related
I screwed up my phone, I rooted it and was uninstalling some bloatware that came with it (sound hound, check-in app etc) but I deleted something important and for some reason I my internet browser was uninstalled and I cannot install CWM (will clarify below). Before my brower was uninstalled I was unable to install any more apps (things from the Market would download, but never install), so I tried a factory reset (being stupid since I uninstalled so much from the stock ROM) and then my browser was gone.
Being a total moron I did not back anything up, so I thought I could install CWM to just reflash the stock ROM. I rooted my phone successfully (following htc dev) but could not install CWM, after flashing the .img file and rebooting it just reboots as normal and shows no evidence of CWM being installed.
My phone is a Rogers HTC One X and I've been making sure to find the guides for Rogers/AT&T HTC's, but I'm still failing .
Use ADB to push the missing apps to the phone?
But it sounds like you want to restore the phone to the state it was before you removed apps?
If so, first step is to get a working recovery. Can you get Rom Manager on your phone? If so, you could flash CM from there.
If not, find a thread on flashing recovery. I have not yet rooted mine so can't be more specific.
And you do know how to get into recovery by holding volume down and power etc? Sorry if I underestimate your experience but sometimes people miss basic stuff.
Sent from my EPAD using Tapatalk 2
Whatever you do, don't flash an HTC official RUU (rom) over all of this.... The only hard bricks you read about are caused by people flashing manufacturers' roms after rooting.
Edit: I see from comments below it appears that some people think I was being sarcastic in making this post: however, see this thread:
http://forum.xda-developers.com/showthread.php?p=22897771
I have seen a number of other warnings over the years of inexperienced users who try to get out of trouble by simply applying manufacturers' updates or factory images to an unlocked phone with a custom recovery and make things much worse.
Sent from my EPAD using Tapatalk 2
How do I use ABD to push missing apps back? Don't worry about underestimating my knowledge at all, this is my first android phone.
I googled how to install custom ROMs and CWM and TWRP came up, I tried both and neither installed. I unrooted my phone successfully and started phone in fastboot, flashed the .img files and then restarted but nothing new was installed.
tangiers said:
Whatever you do, don't flash an HTC official RUU (rom) over all of this.... The only hard bricks you read about are caused by people flashing manufacturers' roms after rooting.
Sent from my EPAD using Tapatalk 2
Click to expand...
Click to collapse
Why are you saying that? Nobody is hard bricking a phone by flashing the correct RUU.
Whatever you do, don't flash an HTC official RUU (rom) over all of this.... The only hard bricks you read about are caused by people flashing manufacturers' roms after rooting. <br />
<br />
Sent from my EPAD using Tapatalk 2
Click to expand...
Click to collapse
Funny guy.
Sent from my HTC One X using xda premium
The FUD is strong in this one...
So what do you guys suggest I do? Should I just bring it back to the store? I got it like four days ago. How do I unroot it? I can't access the market (no brower or market app) so I can't get SU to unroot.
to get back to factory you can do the following
relock the bootloader.
reboot to bootloader and use the command fastboot oem lock
after that install the 1.85 RUU from here http://forum.xda-developers.com/showthread.php?t=1670238
it will take longer than the 10 minutes it says it will take so don't worry.
after that you can unlock again with that same token you used to unlock in the first place.
I'm at work right now so I can't do that yet
If I bring it in without doing that stuff will they know or even care? I have some BS story made up D). Also mine is a Rogers, but the AT&T stuff works with it right?
I appreciate your quick responses
Rogers phone would need rogers ruu loaded
ATM I still have the Rogers RUU, just broken XD
Would it be enough to just lock the blootloader again before returning it to the store?
bman3k said:
ATM I still have the Rogers RUU, just broken XD
Would it be enough to just lock the blootloader again before returning it to the store?
Click to expand...
Click to collapse
why do you want to return it? For this problem or is there something else?
Yes it is for this problem (and all the ones in the first post) I tried for several hours last night to fix it, but couldn't.
I followed the guides for how to install CWM and TWRP to the word and they would not install. If I cannot install them, I cannot reflash stock RUU right?
I still want the HTC One X... just one I didn't screw up XD.
This will put you back to stock and you won't need to return anything
http://forum.xda-developers.com/showthread.php?t=1658929
Ok, I'll try that when I get home, thanks for your help.
PJ83IMG_Evita_UL_Rogers_WWE_1.73.631.1_Radio_0.16a.32.0... from http://forum.xda-developers.com/showthread.php?t=1543593 is what I'll need right?
Correct.
Thanks for your help, that last guide you linked solved it. The first time I looked at it I misread "lock" for "unlock", but I got it to work now . Thanks for your patience and help gunny.
No problem. I'm glad you got it sorted.
I just got my rogers one x and, I'm fairly disappointed in the storage capacity. What advantages would I gain from routing a phone that is already as fast and responsive as it is?
Sent from my HTC One X using xda premium
Okay first off, i know this is the wrong section. I can not post in development because I am new here, but I am in need of help desperately. Okay so I am rooted on 1.85 and the bootloader is NOT unlocked. Well i decided today to take the update to 4.0.4 before I did research. (Stupid me eh?) Well I start the OTA and then do some research. I learn that the update to 4.0.4 might be harmful to rooted users. So I disconnect from WiFi knowing it will pause the download. Well now I have a download that is just paused in the notification bar, and any time i connect to wifi it will continue the download. While the download is paused, can i unroot and take the update safely? I have seriously been searching for hours on end to find someone with a situation that I am in and i can not.
If you do a factory reset the update will go away. But that would also make you loose root. You should unlock the bootloader, then flash the rooted 2.20 update from the dev section.
Sent from my HTC One XL using xda app-developers app
Yep, get that bootloader unlocked immediately and flash a rooted stock ROM or a custom ROM. Make sure you backup all your stuff with Titanium because the bootloader unlock will wipe your phone.
Also, just so you know, this thread most definitely did NOT belong in development, which is reserved for ROMs and kernels and root guides and the like ONLY. Threads like this belong in Q+A but nobody is gonna kill you for posting it in General.
After the download, you should get a prompt to either Install, Postpone, or you can press the "back" capacitive button to cancel. Cancel should stop the update notifications. At least this is how its worked on past HTC OTAs. I personally can't verify, as I haven't gotten the notification yet. But others seem to verify this: http://forum.xda-developers.com/showthread.php?t=1817429
But if you want to be safe, you should SuperCID and unlock bootloader first, as others have suggested. Pressing the wrong button for the method I suggested above will be catastrophic otherwise (lose the ability to root and unlock BL).
Thanks for your help guys!
I just did a factory data reset on my phone. Honestly, I've gotten myself into trouble with rooting. I really need to read up before i continue with things of this sort. So since i did a factory data reset, am i 100% unrooted? Will i be safe to take the OTA now? Thanks for your help guys!
If you were stock 1.85, and rooted using the one-click or "manual" method (which you must be, if you you are still BL locked), then you are now unrooted. You are either rooted or not, there is no "percentage" of rooted.
What kind of trouble have you gotten into rooting, and what do you typically use root for?
I've been debating on whether or not to just go ahead and install the OTA to 2.2. The only thing I've used for root was for WiFi-Tether and I don't even use that anymore so I think I don't even necessarily NEED root anymore. I'm just tired of the updater telling me there's a new update to install - frankly very annoying. I've been just using the back capacitive button to cancel it. BUT, the last time I did this when 1.73 went to 1.85, I was just stock rooted, no unlocked BL (just like I am now), when I tried to install the OTA, went to that error with the triangle and exclamation point and wouldn't let me install it. I had to reflash to stock RUU because it was giving me a bootloop. I just don't want that to happen again... What does that triangle and exclamation point even really mean? I can't find a definitive answer on it. Shouldn't the OTA just install as normal, but it'll remove root in the process?
extol1337 said:
BUT, the last time I did this when 1.73 went to 1.85, I was just stock rooted, no unlocked BL (just like I am now), when I tried to install the OTA, went to that error with the triangle and exclamation point and wouldn't let me install it. I had to reflash to stock RUU because it was giving me a bootloop. I just don't want that to happen again... What does that triangle and exclamation point even really mean? I can't find a definitive answer on it. Shouldn't the OTA just install as normal, but it'll remove root in the process?
Click to expand...
Click to collapse
Red triangle and exclamation point is the stock recovery. This appears if something about the ROM is missing or corrupted. Not sure why this happened to you in that particular case. But installing OTAs on rooted phones is always a crap shoot. Sometimes it works, and you just lose root. Sometimes you boot loop or other things.
redpoint73 said:
Red triangle and exclamation point is the stock recovery. This appears if something about the ROM is missing or corrupted. Not sure why this happened to you in that particular case. But installing OTAs on rooted phones is always a crap shoot. Sometimes it works, and you just lose root. Sometimes you boot loop or other things.
Click to expand...
Click to collapse
That's what I was afraid of. Actually, I remember trying to install the 2.2 OTA a few days ago as well. Same red triangle and exclamation point. This time wasn't a boot loop and I just rebooted again and ever since, just kept canceling the update. Not sure what's going on...
extol1337 said:
That's what I was afraid of. Actually, I remember trying to install the 2.2 OTA a few days ago as well. Same red triangle and exclamation point. This time wasn't a boot loop and I just rebooted again and ever since, just kept canceling the update. Not sure what's going on...
Click to expand...
Click to collapse
Is the update actually downloaded to your phone? You may need to locate and delete it.
It may be trying to install the OTA from recovery, which makes sense. Don't actually know what happens when an OTA installs.
I've never installed an OTA! I'm always rooted, always will be!!!!
Just to be sure.
I did a factory data reset the night of the problem, been good ever since! I have not done anything to the phone except install a few apps. Should i be okay to take the OTA now? Sorry i just really want to be sure. This is my 3rd phone is 3 months so... no second chances.
SOLVED
Okay, so i took a chance on the update. It worked! I will not be rooting anymore until i read up. Sorry guys if you feel this thread was unnecessary. Just an FYI to any who are worried about taking the newest update after a factory data reset, don't be! Thank you to all:highfive:
Did everyone got an update ?
I still do not see update notification
From beast called HTC One X
It's a little late for this probably but for future reference if you are rooted and want to stop receiving OTA updates remove/rename/delete HtcOMADM_ATT.apk and HtcOMADM_ATT.odex from system/apps, wipe cache and dalvik. If you want to remove "AT&T software update" from the "Settings" then remove HtcOMADM_SettingsPlugin_ATT.apk and HtcOMADM_SettingsPlugin_ATT.odex from system/apps, wipe cache and dalvik.
wantabe said:
It's a little late for this probably but for future reference if you are rooted and want to stop receiving OTA updates remove/rename/delete HtcOMADM_ATT.apk and HtcOMADM_ATT.odex from system/apps, wipe cache and dalvik. If you want to remove "AT&T software update" from the "Settings" then remove HtcOMADM_SettingsPlugin_ATT.apk and HtcOMADM_SettingsPlugin_ATT.odex from system/apps, wipe cache and dalvik.
Click to expand...
Click to collapse
Excellent info!
ssteven232 said:
Okay, so i took a chance on the update. It worked! I will not be rooting anymore until i read up. Sorry guys if you feel this thread was unnecessary. Just an FYI to any who are worried about taking the newest update after a factory data reset, don't be! Thank you to all:highfive:
Click to expand...
Click to collapse
Looks like you will not be rooting anymore for a while now, since there is no method to root the 2.2 update. AT&T / HTC made sure the current rooting method won't work on it. Hopefully, the devs will eventually crack this one too.
I hope you knew that before making the dive ... I would have just unlocked the bootloader and flashed a ROM with the update baked into it to get the best of both worlds. But that's just me. I can't own an android without root access. To reach his own.
Sent from my HTC One X using xda app-developers app
borets.boris said:
Looks like you will not be rooting anymore for a while now, since there is no method to root the 2.2 update. AT&T / HTC made sure the current rooting method won't work on it. Hopefully, the devs will eventually crack this one too.
I hope you knew that before making the dive ... I would have just unlocked the bootloader and flashed a ROM with the update baked into it to get the best of both worlds. But that's just me. I can't own an android without root access. To reach his own.
Sent from my HTC One X using xda app-developers app
Click to expand...
Click to collapse
Yeah, I hear what you're saying and you are right. The current rooting method does not work with the new hboot. But.... If you have your bootloader unlocked beforehand you can still still get root after taking the OTA... And you can still flash a custom rom afterwards, from what I understand you would just need to fastboot flash the boot.img. I haven't personally tried it because I like staying fairly stock, just seriously cleaned up with some mods (init.d support, wifi/usb tethering, missing apps replaced). One thing I am curious about and to be honest I haven't spent any time researching the answer, what kernel are the roms using that are based on the 2.23 (4.0.4) Asian RUU? I wonder because I know the combination of the AT&T 2.20 (4.0.4) update with the new kernel and radio is working very, very well on my phone! My quadrant went up 800 points and battery life is still ridiculously good! I also have to agree with "I can't own an android without root access" especially on AT&T. Personally I'm good to go until the Jelly Bean update! Decisions, decisions! :laugh:
wantabe said:
Yeah, I hear what you're saying and you are right. The current rooting method does not work with the new hboot. But.... If you have your bootloader unlocked beforehand you can still still get root after taking the OTA... And you can still flash a custom rom afterwards, from what I understand you would just need to fastboot flash the boot.img. I haven't personally tried it because I like staying fairly stock, just seriously cleaned up with some mods (init.d support, wifi/usb tethering, missing apps replaced).
Click to expand...
Click to collapse
I've never installed an OTA, so I wouldn't know either. Honestly, I don't know why one would do that, when the awesome devs here post ROMs with the latest OTAs and root prebaked into them. There are "modded" ROMs and "stock" (or close to stock) ROMs available to everyone's taste.
wantabe said:
One thing I am curious about and to be honest I haven't spent any time researching the answer, what kernel are the roms using that are based on the 2.23 (4.0.4) Asian RUU? I wonder because I know the combination of the AT&T 2.20 (4.0.4) update with the new kernel and radio is working very, very well on my phone!
Click to expand...
Click to collapse
Right now, I'm running CleanROM 4.5, which is based on the 2.23 RUU. I did install the 2.20 radio, thinking it would work better, since I'm on AT&T. I took a screenshot of the kernel screen for you.
wantabe said:
My quadrant went up 800 points and battery life is still ridiculously good!
Click to expand...
Click to collapse
Where was your improvement? Did the increase happen in the aspect/area that directly affects your daily use, or in some esoteric algorithm that the phone all of a sudden processes faster? I used to go crazy on quadrant scores, but now I don't really understand their value/accuracy. As long as the phone feels buttery smooth while lasting 5+ hours of screen time, I'm happy!
Since you're interested in the scores, I installed quadrant and ran it, so you can compare.
Sent from my HTC One X using xda app-developers app
in admiration, totally confused!
borets.boris said:
Right now, I'm running CleanROM 4.5, which is based on the 2.23 RUU. I did install the 2.20 radio, thinking it would work better, since I'm on AT&T. I took a screenshot of the kernel screen for you.
Click to expand...
Click to collapse
Hi, do you think you could point me in the right direction for this? I found the general thread on radios, but am at a total loss about what it means or what to do with it!
You knew this was the wrong section but posted here anyway? Not a good way to start your membership on XDA. First rule of thumb is to search before creating a thread. Google is a great source for information. For future reference, all questions belong in the Q&A section, where coincidentally, this is being moved to.
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
"If you choose not to decide, you still have made a choice"
Sent from my HTC One X, using XDA Premium.
Okay so obviously to use any of the AOSP Roms with the 3.4 kernel, you have to s-off then RUU, ect.. ect...ect...
I'm on vanilla root-box 6/11 right now and it just refuses to keep apps in memory. I don't have time to really try a new ROM or learn how to s-off and stuff ATM. I plan to sometime next week., but in the mean time, I was wondering if I flash a ROM that uses the 3.4 kernel and then immediately flash a different kernel before even booting. Would that get me past the previous requirements?
kyleallen5000 said:
Okay so obviously to use any of the AOSP Roms with the 3.4 kernel, you have to s-off then RUU, ect.. ect...ect...
I'm on vanilla root-box 6/11 right now and it just refuses to keep apps in memory. I don't have time to really try a new ROM or learn how to s-off and stuff ATM. I plan to sometime next week., but in the mean time, I was wondering if I flash a ROM that uses the 3.4 kernel and then immediately flash a different kernel before even booting. Would that get me past the previous requirements?
Click to expand...
Click to collapse
Nope, you'll probably brick doing that.
kyleallen5000 said:
Okay so obviously to use any of the AOSP Roms with the 3.4 kernel, you have to s-off then RUU, ect.. ect...ect...
I'm on vanilla root-box 6/11 right now and it just refuses to keep apps in memory. I don't have time to really try a new ROM or learn how to s-off and stuff ATM. I plan to sometime next week., but in the mean time, I was wondering if I flash a ROM that uses the 3.4 kernel and then immediately flash a different kernel before even booting. Would that get me past the previous requirements?
Click to expand...
Click to collapse
You can't flash a different kernel because those ROMs require the 3.4 kernel. There are a few lucky individuals that have been able to flash the newer 3.4 ROMs without going through the s-off & RUU process but that is definitely not the norm. You could try it but you will probably end up in a boot loop just like I did. I was already s-off so I just had to run the RUU. But even doing the whole process isn't a very time consuming ordeal. I did the whole process on a friend's phone yesterday and it took around 30 minutes and was very easy.
RollTribe said:
Nope, you'll probably brick doing that.
Click to expand...
Click to collapse
Yeah i figured it was a long shot, glad i asked first lol. Thanks dude!
pside15 said:
You can't flash a different kernel because those ROMs require the 3.4 kernel. There are a few lucky individuals that have been able to flash the newer 3.4 ROMs without going through the s-off & RUU process but that is definitely not the norm. You could try it but you will probably end up in a boot loop just like I did. I was already s-off so I just had to run the RUU. But even doing the whole process isn't a very time consuming ordeal. I did the whole process on a friend's phone yesterday and it took around 30 minutes and was very easy.
Click to expand...
Click to collapse
Oh I'm sure it's not to bad, but I have no idea how to use fastboot or adb (I've lucked by without having to use either, at least to my knowledge). Plus I don't readily have a windows PC, I just want make sure I know what I'm doing before I even attempt it. I've been looking over gunnyman's adb for noobs (http://forum.xda-developers.com/showthread.php?t=1754018), I'll give it a shot sometime next week when I've worked up the courage. Thanks for the advice!
pside15 said:
There are a few lucky individuals that have been able to flash the newer 3.4 ROMs without going through the s-off & RUU process but that is definitely not the norm.
Click to expand...
Click to collapse
3.4 kernel requires only 3.18/2.14 hboot.
If you already meet those requirements there is no need to RUU to 3.18
If you don't need to RUU to 3.18, you don't need to S-OFF.
It's really just that simple.
exad said:
3.4 kernel requires only 3.18/2.14 hboot.
If you already meet those requirements there is no need to RUU to 3.18
If you don't need to RUU to 3.18, you don't need to S-OFF.
It's really just that simple.
Click to expand...
Click to collapse
I meant there are people who have gotten it to work on an older hboot. Also, you can't just update your hboot without doing the ruu. There's something else in the update that it requires. So if you were s-off and just updated your hboot to 2.14 like I tried, the 3.4 kernel ROMs still won't flash correctly. I had an 2.14 hboot and still had to run the ruu.
Sent from my One X using Tapatalk 2
pside15 said:
I meant there are people who have gotten it to work on an older hboot. Also, you can't just update your hboot without doing the ruu. There's something else in the update that it requires. So if you were s-off and just updated your hboot to 2.14 like I tried, the 3.4 kernel ROMs still won't flash correctly. I had an 2.14 hboot and still had to run the ruu.
Sent from my One X using Tapatalk 2
Click to expand...
Click to collapse
Yes, you require all the files in the firmware zip. It's not so much the hboot that matters hence why I put 3.18 software/2.14 hboot.
The people who managed to do it with lower hboot did the 3.18 update at some point and then downgraded just the hboot using the modded hboot file.
exad said:
Yes, you require all the files in the firmware zip. It's not so much the hboot that matters hence why I put 3.18 software/2.14 hboot.
The people who managed to do it with lower hboot did the 3.18 update at some point and then downgraded just the hboot using the modded hboot file.
Click to expand...
Click to collapse
Not trying to start an argument or anything but, I have seen and responded to users that have gotten a 3.4 kernel ROM to boot on an older hboot without ever having done the 3.18 update. It's definitely not the norm and I wouldn't even recommend trying it but there are a few people that have done it successfully.
pside15 said:
Not trying to start an argument or anything but, I have seen and responded to users that have gotten a 3.4 kernel ROM to boot on an older hboot without ever having done the 3.18 update. It's definitely not the norm and I wouldn't even recommend trying it but there are a few people that have done it successfully.
Click to expand...
Click to collapse
The ones I've seen pull that off had run the 3.18 ruu then downgraded the hboot. If it was that simple I doubt the the Rom would say it was required. And even if it was pulled of it was done by not following directions. Noobs with this phone that don't know how quirky it is can brick it. So I recommend following the steps the Rom calls for. There are more bricks from people skipping steps or not following directions
Sent from my HTC One XL using xda premium
31ken31 said:
The ones I've seen pull that off had run the 3.18 ruu then downgraded the hboot. If it was that simple I doubt the the Rom would say it was required. And even if it was pulled of it was done by not following directions. Noobs with this phone that don't know how quirky it is can brick it. So I recommend following the steps the Rom calls for. There are more bricks from people skipping steps or not following directions
Sent from my HTC One XL using xda premium
Click to expand...
Click to collapse
I'm not saying it's that simple and yes, I agree about following the steps. That's why I said I wouldn't even recommend trying the newer ROMs without updating first. I have seen it work though. That's all I'm saying. Maybe those users were ignorant on exactly what they did but I'm just going on what I've read and responded to.
Same ken. I have not seen anyone manage without having 3.18 at some point and I chill on here and in facepalm quite often. In fact, I don't even have a physical body. I am just a conciousness who lives within a hoxl. j/k
Pside if you say you've seen it, that's cool. But it is true that I live on these forums and find it odd that I have not encountered that situation yet.
Sent from my HTC One X using xda app-developers app
exad said:
Same ken. I have not seen anyone manage without having 3.18 at some point and I chill on here and in facepalm quite often. In fact, I don't even have a physical body. I am just a conciousness who lives within a hoxl. j/k
Pside if you say you've seen it, that's cool. But it is true that I live on these forums and find it odd that I have not encountered that situation yet.
Sent from my HTC One X using xda app-developers app
Click to expand...
Click to collapse
Go to my profile and look at my quoted posts or just go back a bit in the Carbon thread. You will see where I quoted someone who was s-on and on the 1.14 hboot that flashed one of the 3.4 nightlies successfully. He was wondering if his phone was going to mess up now. That's the only specific one I remember off the top of my head but I know I've seen others as well. Like I said I'm just going by what I read. They could be completely wrong, lying, or just ignorant noobs. I live on these forums as well and have absolutely no reason to make something like this up.
Sent from my One X using Tapatalk 2
Stuck...just displays the HTC logo on white screen.
I had cleanrom 5.0 final. TWRP, super SU, rooted, unlocked. Firmware 2.20.
I dropped in the new ROM, did a factory reset in TWRP, and installed new rom. I read that that would work with my current setup, but apparently not. I am unclear on the part where it says "Highly recommend latest Jellybean firmware and S-Off!" Not sure how to determine this or proceed. Things here seem to be getting increasingly more jargoned rather than step by step for those of us that do this once a year or so :/
I flashed back to 5.0 with no issues, but I would really like to try to get the cleanrom 7 working if possible. Any ideas?
It sounds like you're s-on, if so you'd need to flash the boot.img via fastboot. Is this the first ROM you've flashed? Please post your bootloader details.
Sent from my Evita
timmaaa said:
It sounds like you're s-on, if so you'd need to flash the boot.img via fastboot. Is this the first ROM you've flashed? Please post your bootloader details.
Sent from my Evita
Click to expand...
Click to collapse
Thanks for your reply. You are correct, I am s-on. But I was able to re-load CleanROM 5. This is my second custom rom on this phone (the first being CleanROM 5). But this is only my third custom rom ever, so I am pretty much of a noober. :cyclops:
klaypigeon said:
I am unclear on the part where it says "Highly recommend latest Jellybean firmware and S-Off!" Not sure how to determine this or proceed. Things here seem to be getting increasingly more jargoned rather than step by step for those of us that do this once a year or so :/
Click to expand...
Click to collapse
The ROM threads are to inform you of the features and requirements of the ROM, not to be a step-by-step guide. There are plenty of step-by-step guides in various places, for those that care to read and look.
If you don't flash often, a good resource is my Index thread: http://forum.xda-developers.com/showthread.php?t=1671237
My Index will at least point you to the s-off process. I intend to add some info about the 2.15 firmware (as people keep constantly asking about it), but work has been chaotic, to say the least.
Another good thing to do, is read through the more recent pages of the ROM thread, or do a search on the thread.
Thanks, I am subscribed to your index, that's where I found the ROM and what I used during my first flash.
I did the process for unlocking the 2.20 firmware about a year ago as that is what my phone came with. I assume that would have given me superCID and s-off in order to install my old ROM (CleanROM 5).
'CID Getter' says I have no CID, which I read means I have superCID.
Firmware : 2.20
SuperSU installed and functioning (I have root)
Current ROM: CleanROM 5 Final
S-ON
TWRP 2.3.1.0
So you think I need to do s-off as described here? http://forum.xda-developers.com/showthread.php?t=2155071
If I brick this phone I am using a clam-shell for a year until contract renewal :/
klaypigeon said:
I assume that would have given me superCID and s-off in order to install my old ROM (CleanROM 5).
Click to expand...
Click to collapse
You shouldn't be assuming anything. You just said the CID Getter says S-on. You can also confirm s-on or s-off by going into bootloader.
The main reason CleanROM7 will not boot, is that you forgot to extract boot.img from the ROM file, and flash it separately using fastboot. Some older versions of CleanROM didn't require this (boot.img was flashed in the AROMA installer), so that may be why you don't remember doing this.
S-off removed the requirement to flash boot.img separately (will flash in recovery automatically when you flash the ROM). It will also allow you to install hboot 2.15 and associated firmware, if you happen to suffer from signal drops or random reboots while on Sense 5 ROMs.
Further to that, CID Getter doesn't show your actual CID. The proper way to display your CID is by using the fastboot command "fastboot oem readcid". Like Redpoint said, you shouldn't be assuming anything.
Sent from my Evita
Well...its pretty much dead. I verified supercid and then I flashed the bootloader and now it is just in a slow bootloop. It shows the HTC developer splash screen and then shuts down then a few minutes later does it again and so on. Looks like I am clamshell bound.
What did you flash?
Sent from my Evita
Muahahaaha, WORKING! Had to hold down volume through 5 reboot cycles and it finally picked up bootloader. set S-OFF. Tried CleanROM every which way and flashed boo.img as well, never could get it to make it past google boot animation. Installed ViperXL and boot.img without issue. Jelly Bean 4.2.2 sweetness! I lost hope there for about an hour, glad I didn't launch phone into the woods.
timmaaa said:
Further to that, CID Getter doesn't show your actual CID.
Click to expand...
Click to collapse
Ha, that's not a very useful app, then. What is it actually reading?
---------- Post added at 09:24 AM ---------- Previous post was at 09:21 AM ----------
klaypigeon said:
Well...its pretty much dead. I verified supercid and then I flashed the bootloader and now it is just in a slow bootloop. It shows the HTC developer splash screen and then shuts down then a few minutes later does it again and so on. Looks like I am clamshell bound.
Click to expand...
Click to collapse
Do you mean "locked the bootloader" instead of "flashed"?
If you locked the bootloader, this is what is supposed to happen. Locking the bootloader assumes you will be running RUU, and renders the phone unable to boot normally.
I know you got it back up and running. But for future reference, this phone is almost never bricked, as long as the screen comes on.
---------- Post added at 09:26 AM ---------- Previous post was at 09:24 AM ----------
klaypigeon said:
Muahahaaha, WORKING! Had to hold down volume through 5 reboot cycles and it finally picked up bootloader. set S-OFF. Tried CleanROM every which way and flashed boo.img as well, never could get it to make it past google boot animation. Installed ViperXL and boot.img without issue. Jelly Bean 4.2.2 sweetness! I lost hope there for about an hour, glad I didn't launch phone into the woods.
Click to expand...
Click to collapse
Flashing boot.img manually is not necessary with s-off, it should happan automatically when you flash a ROM. I suspect you may be having trouble with CleanROM due to a buggy or outdated TWRP version. What version of TWRP are you using?
It also seems that you are pretty unclear about some of the basic concepts around flashing ROMs on this phone. It would probably benefit you to read and learn a bit more before something bad actually happens due to negligence.
I'm not sure what CID Getter is actually reading, but when I used it it came up with the incorrect CID, can't remember exactly what it was now but it was definitely incorrect because I already had SuperCID.
Sent from my Evita
Flashing boot.img manually is not necessary with s-off, it should happan automatically when you flash a ROM. I suspect you may be having trouble with CleanROM due to a buggy or outdated TWRP version. What version of TWRP are you using?
It also seems that you are pretty unclear about some of the basic concepts around flashing ROMs on this phone. It would probably benefit you to read and learn a bit more before something bad actually happens due to negligence.
Click to expand...
Click to collapse
I am using 2.3.1 TWRP. In the viperXL thread they said I may have to flash the boot.img if I had hboot 1.14 which I do. As far as read and learning, I do this once a year I am not a ROM junkie. Every time I do it I have to re-learn. I work in IT so it is a use it or lose it world in my brain - volumes of info in > volumes out
klaypigeon said:
I am using 2.3.1 TWRP. In the viperXL thread they said I may have to flash the boot.img if I had hboot 1.14 which I do. As far as read and learning, I do this once a year I am not a ROM junkie. Every time I do it I have to re-learn. I work in IT so it is a use it or lose it world in my brain - volumes of info in > volumes out
Click to expand...
Click to collapse
If you have s-off you don't need to flash the boot.img via fastboot, that's only required if you're s-on. It might be worthwhile updating your TWRP to the 2.6 version though.
What Redpoint was saying is that you need to have a firm understanding of what you're doing when it comes to modifying your phone. If you only do it once a year that's cool, but that probably means that once a year you need to brush up before making any changes to your device. Rushing in without the required knowledge is how bricks occur. This is only being suggested to help you, for your own good.
Sent from my Evita
klaypigeon said:
I am using 2.3.1 TWRP. In the viperXL thread they said I may have to flash the boot.img if I had hboot 1.14 which I do.
Click to expand...
Click to collapse
Only with hboot 1.14 or later and s-on. If s-off the protection which prevents boot.img from being written in recovery is bypassed.
I believe TWRP 2.3.1 was a pretty trustworthy version (although older). So not sure why CleanROM didn't flash. Might not be a bad idea to update to 2.6.0 (although the latest 2.6.4 seems to have some bugs).
klaypigeon said:
I do this once a year I am not a ROM junkie. Every time I do it I have to re-learn. I work in IT so it is a use it or lose it world in my brain - volumes of info in > volumes out
Click to expand...
Click to collapse
Yeah, I understand that you only do this on a seldom basis. And its a lot of esoteric knowledge to have to relearn (or take in, since things have likely changed since lasts time). However, that doesn't change the fact that not fully understanding all the concepts and steps can have dire consequences for your phone.
So my AT&T HTC One X is bootloader unlocked, super CID and was rooted. I installed a copy of Viper XL 4.2.0 that had issues with the radio turning off so I thought I'd try Maximus HD. I flashed the boot.img and went to install the rom only to find that the rom was for the international version of the HTC One X only (this was conveniently overlooked in the thread). I backed out of installation, went to restore with my TWRP backup and it had been deleted. I reinstalled the Viper XL rom and my phone booted up to the HTC developers screen (red text) and went black. This now happens every time I try to boot the phone up.
I have access to fastboot and clockwork recovery. I can't get ADB to work as I don't have access to enable USB debugging. I have flashed a few roms since with their respective boot.img to no avail. The phone still just boots to the HTC screen and blacks out.
I don't have S-off and, from my research, I can't get it without ADB so I can't RUU and return to stock without bricking (apparently). I've been at this for about a month and this soft brick is starting to look a whole lot like a hard brick.
Any suggestions, or am I out of business?
Thanks in advance!
roycedavies said:
So my AT&T HTC One X is bootloader unlocked, super CID and was rooted. I installed a copy of Viper XL 4.2.0 that had issues with the radio turning off so I thought I'd try Maximus HD. I flashed the boot.img and went to install the rom only to find that the rom was for the international version of the HTC One X only (this was conveniently overlooked in the thread). I backed out of installation, went to restore with my TWRP backup and it had been deleted. I reinstalled the Viper XL rom and my phone booted up to the HTC developers screen (red text) and went black. This now happens every time I try to boot the phone up.
I have access to fastboot and clockwork recovery. I can't get ADB to work as I don't have access to enable USB debugging. I have flashed a few roms since with their respective boot.img to no avail. The phone still just boots to the HTC screen and blacks out.
I don't have S-off and, from my research, I can't get it without ADB so I can't RUU and return to stock without bricking (apparently). I've been at this for about a month and this soft brick is starting to look a whole lot like a hard brick.
Any suggestions, or am I out of business?
Thanks in advance!
Click to expand...
Click to collapse
Not sure if I can help you much but I did notice an important clue by what you said. It looks like you flashed the boot.img before flashing the Rom. This is backwards. You are supposed to flash the Rom first and then the boot.img. If you are not S-Off this will indeed cause problems. If you are still able and have the files on the phone, try flashing in that order and see if that clears it up. Oh and P.S. I'm sure you already are kicking yourself but yes, stick to Roms made for our phone in this forum.
Just noticed something else:
you said you had access to fastboot? Connect the phone and open a CMD prompt, navigate to your ADB/Fastboot folder (Where ever you keep your adb/fastboot tools) and then type "fastboot devices" to see if your computer is talking to your phone. If it is, you said you can flash Viper. you will just need to unzip the Viper zip and get the boot.img. Put that file in your ADB/Fastboot folder. open a CMD prompt again and navigate once again to you ADB/Fastboot folder, then type "fastboot flash boot boot.img and that should get you back on the road.
This is assuming you have a folder with the required ADB/Fastboot resources (if you don't I recommend you learn how) and knowledge on how to navigate to that folder with DOS commands.
roycedavies said:
So my AT&T HTC One X is bootloader unlocked, super CID and was rooted. I installed a copy of Viper XL 4.2.0 that had issues with the radio turning off so I thought I'd try Maximus HD. I flashed the boot.img and went to install the rom only to find that the rom was for the international version of the HTC One X only (this was conveniently overlooked in the thread). I backed out of installation, went to restore with my TWRP backup and it had been deleted. I reinstalled the Viper XL rom and my phone booted up to the HTC developers screen (red text) and went black. This now happens every time I try to boot the phone up.
I have access to fastboot and clockwork recovery. I can't get ADB to work as I don't have access to enable USB debugging. I have flashed a few roms since with their respective boot.img to no avail. The phone still just boots to the HTC screen and blacks out.
I don't have S-off and, from my research, I can't get it without ADB so I can't RUU and return to stock without bricking (apparently). I've been at this for about a month and this soft brick is starting to look a whole lot like a hard brick.
Any suggestions, or am I out of business?
Thanks in advance!
Click to expand...
Click to collapse
You said you flashed the boot.img from Maximus before flashing the ROM (which is ok, the previous member is incorrect in saying that it must be afterwards, it can be either), but did you flash the boot.img from the Viper XL ROM when you flashed that? If not your phone is trying to boot Viper while the Maximus boot.img is still installed, obviously this won't work.
One thing. The fact that Maximus ROM is only for the Endeavoru wasn't "conveniently overlooked" as you sarcastically put it. You were in the wrong forum. The ROM itself is in the Endeavoru forum and you have the Evita so you shouldn't be in the Endeavoru forum in the first place. The ROM is in the correct forum, it doesn't need to be labelled "Endeavoru only" because the user should be aware of which device they have and be aware of which forum they are in. The fact that you're bouncing around both forums is a bit of a worry. You have no reason to be in that forum.
Our forum is here:
http://forum.xda-developers.com/forumdisplay.php?f=1538
Our two development sections are here:
http://forum.xda-developers.com/forumdisplay.php?f=1541
http://forum.xda-developers.com/forumdisplay.php?f=1726
Stay within our device forum, you don't ever need to be anywhere else. You're pretty lucky you haven't actually bricked your phone by flashing that ROM. By the way, there's no such thing as a soft brick. A brick is when your phone will not power on at all. It's either bricked or it isn't.
Sent from my Evita
timmaaa said:
You said you flashed the boot.img from Maximus before flashing the ROM (which is ok, the previous member is incorrect in saying that it must be afterwards, it can be either), but did you flash the boot.img from the Viper XL ROM when you flashed that? If not your phone is trying to boot Viper while the Maximus boot.img is still installed, obviously this won't work.
One thing. The fact that Maximus ROM is only for the Endeavoru wasn't "conveniently overlooked" as you sarcastically put it. You were in the wrong forum. The ROM itself is in the Endeavoru forum and you have the Evita so you shouldn't be in the Endeavoru forum in the first place. The ROM is in the correct forum, it doesn't need to be labelled "Endeavoru only" because the user should be aware of which device they have and be aware of which forum they are in. The fact that you're bouncing around both forums is a bit of a worry. You have no reason to be in that forum.
Our forum is here:
http://forum.xda-developers.com/forumdisplay.php?f=1538
Our two development sections are here:
http://forum.xda-developers.com/forumdisplay.php?f=1541
http://forum.xda-developers.com/forumdisplay.php?f=1726
Stay within our device forum, you don't ever need to be anywhere else. You're pretty lucky you haven't actually bricked your phone by flashing that ROM. By the way, there's no such thing as a soft brick. A brick is when your phone will not power on at all. It's either bricked or it isn't.
Click to expand...
Click to collapse
Thanks for the reply. I believe the reason I'm not bricked is because I backed out of the installation of Maximus HD during the setup screen progression. The actual ROM was never flashed. However, I have flashed the boot.img and ROMs for Viper, Xylon, and Cyanogenmod with no success. The result is the same every time (HTC screen, then black). I extract the boot.img from each of the roms, flash it, and then flash the ROM. The ROM I flash is a copy of the the original with the boot.img still inside. Perhaps I should be removing the boot.img if I am going to flash it separately in fastboot? And I realize that the threads are specific for certain phones now. It's all kind of a mess to get into at first.
I understanding that it can be a bit confusing at first, especially with the phones betting similarly named. But you know now so you shouldn't have this problem again. I believe you will probably need to run an RUU to get out of this mess, but I'll need to see your bootloader details first, just the first five lines.
Sent from my Evita
Madcat8686 said:
Not sure if I can help you much but I did notice an important clue by what you said. It looks like you flashed the boot.img before flashing the Rom. This is backwards. You are supposed to flash the Rom first and then the boot.img. If you are not S-Off this will indeed cause problems. If you are still able and have the files on the phone, try flashing in that order and see if that clears it up. Oh and P.S. I'm sure you already are kicking yourself but yes, stick to Roms made for our phone in this forum.
Just noticed something else:
you said you had access to fastboot? Connect the phone and open a CMD prompt, navigate to your ADB/Fastboot folder (Where ever you keep your adb/fastboot tools) and then type "fastboot devices" to see if your computer is talking to your phone. If it is, you said you can flash Viper. you will just need to unzip the Viper zip and get the boot.img. Put that file in your ADB/Fastboot folder. open a CMD prompt again and navigate once again to you ADB/Fastboot folder, then type "fastboot flash boot boot.img and that should get you back on the road.
This is assuming you have a folder with the required ADB/Fastboot resources (if you don't I recommend you learn how) and knowledge on how to navigate to that folder with DOS commands.
Click to expand...
Click to collapse
Dude, you are a golden-freaking genius. Your suggestion to flash the boot.img second did the trick! I'm currently running Uxylon! Hopefully things continue to work. Thank you, thank you, thank you.
Oh, that's great. Usually it shouldn't matter which order you flash in, but at least it got you out of trouble this time.
Sent from my Evita
roycedavies said:
Dude, you are a golden-freaking genius. Your suggestion to flash the boot.img second did the trick! I'm currently running Uxylon! Hopefully things continue to work. Thank you, thank you, thank you.
Click to expand...
Click to collapse
Actually I can't take credit for this. Timmaaa pointed out something I didn't know. You can flash them in either order (mind blown!) I've only see it one way. I learn a ton every day. @timmaaa pointed out you had the Maximus boot.img loaded. I think you just flashed over it and now you have the correct boot.img for the Rom you are running. Glad everything worked out for you and I learned something in the process too. Cheers!
Madcat8686 said:
Actually I can't take credit for this. Timmaaa pointed out something I didn't know. You can flash them in either order (mind blown!) I've only see it one way. I learn a ton every day. @timmaaa pointed out you had the Maximus boot.img loaded. I think you just flashed over it and now you have the correct boot.img for the Rom you are running. Glad everything worked out for you and I learned something in the process too. Cheers!
Click to expand...
Click to collapse
Hey, you should take the credit, I believe flashing it afterwards was what got his phone booted :thumbup:
Sent from my Evita
Madcat8686 said:
Actually I can't take credit for this. Timmaaa pointed out something I didn't know. You can flash them in either order (mind blown!) I've only see it one way. I learn a ton every day. @timmaaa pointed out you had the Maximus boot.img loaded. I think you just flashed over it and now you have the correct boot.img for the Rom you are running. Glad everything worked out for you and I learned something in the process too. Cheers!
Click to expand...
Click to collapse
thanks again for your help and this might be a total shot in the dark but I am still having the boot to black issue after installing uxylon. the room is running well enough (4g won't turn on but one problem at a time) but every time I turn the phone off or rent I have to get into fastboot and flash the boot.img to get the phone on again. is that normal? the only other ROM I have ever had working is viper but I haven't seen any indication that having to use fastboot to turn the phone on every time is normal. is there a way to fix this possibly?
timmaaa said:
I understanding that it can be a bit confusing at first, especially with the phones betting similarly named. But you know now so you shouldn't have this problem again. I believe you will probably need to run an RUU to get out of this mess, but I'll need to see your bootloader details first, just the first five lines.
Sent from my Evita
Click to expand...
Click to collapse
Thanks for the reply! I will get the bootloader info ASAP bit don't I need to be s-of in order to RUU? from what I've read, if you don't have unlocked bootloader, root access, and s-off, you'll end up bricking your phone with RUU. I'd really like to do it but I have tried to get s-off to no avail.
No, that isn't normal at all, there's definitely something screwy there. I think you're gonna need to run an RUU, so you'll need to get s-off. Try this:
Http://Rumrunner.us
Sent from my Evita
roycedavies said:
thanks again for your help and this might be a total shot in the dark but I am still having the boot to black issue after installing uxylon. the room is running well enough (4g won't turn on but one problem at a time) but every time I turn the phone off or rent I have to get into fastboot and flash the boot.img to get the phone on again. is that normal? the only other ROM I have ever had working is viper but I haven't seen any indication that having to use fastboot to turn the phone on every time is normal. is there a way to fix this possibly?
Click to expand...
Click to collapse
Definitely not normal. A few recommendations:
1. Back up all your stuff, wipe everything except the SD card, Flash a fresh copy of the Rom, Flash the boot.img (you really should consider S-Off), Wipe the cache and DALVIK cache one more time, boot up the system.
2. Same as above except choose another Rom. There are plenty to choose from. The 4.4 Roms are getting a lot better now that the new Kernel fix got rid of the boot loops/reboots.
Sorry about the delay, it's been a heavy week at work. Hope things work out for you.
I don't think flashing another ROM is going to fix the problem at hand. There's very possibly something much deeper wrong here, which a ROM flash won't fix. I honestly think it's better to run an RUU which will bring everything back to the way it's meant to be and the user can start with a blank slate.
Sent from my One XL using XDA Premium 4 mobile app
timmaaa said:
No, that isn't normal at all, there's definitely something screwy there. I think you're gonna need to run an RUU, so you'll need to get s-off. Try this:
Http://Rumrunner.us
Sent from my Evita
Click to expand...
Click to collapse
Sometimes is pays to see if there is a page 2 to the thread...Sorry about that! lol
---------- Post added at 08:48 PM ---------- Previous post was at 08:45 PM ----------
timmaaa said:
I don't think flashing another ROM is going to fix the problem at hand. There's very possibly something much deeper wrong here, which a ROM flash won't fix. I honestly think it's better to run an RUU which will bring everything back to the way it's meant to be and the user can start with a blank slate.
Sent from my One XL using XDA Premium 4 mobile app
Click to expand...
Click to collapse
You have no idea how much I have vicariously learned from your posts. Thanks Timmaa! I keep thinking if more of these folks would go ahead and get S-Off they would have waaaaaaaaaay less issues.
Flashing another ROM could be worth a try, but the fact that the boot.img seems to be disappearing whenever the screen is off suggest something has gone wrong at a lower level.
I'm glad to help, I'm still learning something new just about every day too from XDA.
Sent from my One XL using XDA Premium 4 mobile app
timmaaa said:
Flashing another ROM could be worth a try, but the fact that the boot.img seems to be disappearing whenever the screen is off suggest something has gone wrong at a lower level.
I'm glad to help, I'm still learning something new just about every day too from XDA.
Sent from my One XL using XDA Premium 4 mobile app
Click to expand...
Click to collapse
I totally agree now because after rereading the post, there is a radio issue in addition to the boot issue. Is it possible that the Endeverou boot.img messed something up?
Yeah, that's exactly what I'm thinking. An RUU will hopefully fix that right up.
Sent from my Evita.
timmaaa said:
No, that isn't normal at all, there's definitely something screwy there. I think you're gonna need to run an RUU, so you'll need to get s-off. Try this:
Http://Rumrunner.us
Sent from my Evita
Click to expand...
Click to collapse
That sounds like a good plan. (I'm really appreciating all your input by the way! Thanks so much!) One question though, upon checking out the rumrunner website, there isn't specific mention of the HTC One X Evita. Call me paranoid, but after what I've been through I want to make 100% sure I'm compatible before moving forward. Have you or anyone used this specific method for S-Off on the One X Evita?
For the Evita you use the universal HTC method. I've created a thread for it if you want to make sure it's worked for other Evita owners.
http://forum.xda-developers.com/showthread.php?t=2540232
Sent from my Evita.