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.
Related
First: Thanks to this great forum of developers and users, I have learned a lot in a short period of time. The HTC One S is my first Android handset, and I love it. All the wonderful tutorials and threads you guys created made learning the basics of rooting/flashing easy.
This is my second HTC One S handset, the previous one died from hardware failure. The previous handset had HBoot 1.06, and so I was able to flash the TWRP recovery and use the Trickdroid 9.1.0 flawlessly. The problem comes with this new handset, and I am not sure exactly what it is to troubleshoot. The current HBoot on the phone is 1.14 (which means I can't flash radios, etc.). After unlocking the bootloader, I flashed the latest TWRP recovery (2.4.1.0). After factory resetting the phone and installing the Trickdroid 9.1.0, the phone won't boot. If I hold the power for 5-10 seconds, the keys flash, that's it. I am able to get into the bootloader using the power + volume down method, and then I have to recover my phone back to factory settings using the RUU avaliable online. I have tried redoing this process 2-3 times now, and everytime I flash the JB rom, the phone won't boot. I am not sure if having a HBoot 1.14 prevents me from upgrading from ICS --> JB, recovery, or anything else. As I said, my knowledge of Android is very limited as I am a new user. I really would like to use the JB rom that is cleaned and optimized. If anyone has any suggestions on what I can do, I would greatly appreciate it. Right now, I just did the perm root to be able to get rid of some of the bloat (T-Mobile comes with so much garbage!). Thank you so much, once again, and any troubleshooting help will be returned with big kiss! :angel:
bombina said:
First: Thanks to this great forum of developers and users, I have learned a lot in a short period of time. The HTC One S is my first Android handset, and I love it. All the wonderful tutorials and threads you guys created made learning the basics of rooting/flashing easy.
This is my second HTC One S handset, the previous one died from hardware failure. The previous handset had HBoot 1.06, and so I was able to flash the TWRP recovery and use the Trickdroid 9.1.0 flawlessly. The problem comes with this new handset, and I am not sure exactly what it is to troubleshoot. The current HBoot on the phone is 1.14 (which means I can't flash radios, etc.). After unlocking the bootloader, I flashed the latest TWRP recovery (2.4.1.0). After factory resetting the phone and installing the Trickdroid 9.1.0, the phone won't boot. If I hold the power for 5-10 seconds, the keys flash, that's it. I am able to get into the bootloader using the power + volume down method, and then I have to recover my phone back to factory settings using the RUU avaliable online. I have tried redoing this process 2-3 times now, and everytime I flash the JB rom, the phone won't boot. I am not sure if having a HBoot 1.14 prevents me from upgrading from ICS --> JB, recovery, or anything else. As I said, my knowledge of Android is very limited as I am a new user. I really would like to use the JB rom that is cleaned and optimized. If anyone has any suggestions on what I can do, I would greatly appreciate it. Right now, I just did the perm root to be able to get rid of some of the bloat (T-Mobile comes with so much garbage!). Thank you so much, once again, and any troubleshooting help will be returned with big kiss! :angel:
Click to expand...
Click to collapse
Did you flash the boot.img via fastboot after flashing the rom?
rustykwak said:
Did you flash the boot.img via fastboot after flashing the rom?
Click to expand...
Click to collapse
That seemed to be the problem this whole time! Argh! Thanks! In the previous phone, I always flashed it after rebooting via FlashGUI. I guess the only looming problem now is that the Wifi doesn't work on this Trickdroid ROM for my HBoot (1.14). Blah.
bombina said:
That seemed to be the problem this whole time! Argh! Thanks! In the previous phone, I always flashed it after rebooting via FlashGUI. I guess the only looming problem now is that the Wifi doesn't work on this Trickdroid ROM for my HBoot (1.14). Blah.
Click to expand...
Click to collapse
theres a thread in dev section wifi partions perhaps that will help you out!
rustykwak said:
theres a thread in dev section wifi partions perhaps that will help you out!
Click to expand...
Click to collapse
Unfortunatly on that hboot I dnt think we can
Sent from my HTC One S using xda app-developers app
siqbudz said:
Unfortunatly on that hboot I dnt think we can
Sent from my HTC One S using xda app-developers app
Click to expand...
Click to collapse
Yes, that is right. I think any HBoot higher than 1.09 (I am 1.14) will not be able to flash WiFi partitions. Any way we can make WiFi work on JB? Would upgrading the HBoot to 2.x fix this Wifi problem? I still don't know why it doesn't work though and not having Wifi is kind of a big deal.
Followed the steps in Hassoon's toolkit, installed recovery, sideloaded CM, and now I have no OS. I can still access fastboot and recovery, see attached image for more info. Any more information needed, please let me know. This is pretty frustrating, no wonder I like Nexus devices.
(sorry for double posting, I also put this in Hassoon's thread, but felt it'd be more appropriate to post here)
first man... you'll only be able to use sense roms most likely, as the newer aosp roms dont mix with the upgraded touchscreen on the 3.18 firmware. so you can head to the original dev section to find the "downgrade touchscreen" thread to use aosp...
second, you have to fastboot flash the boot.img of every rom because the newer hboots dont allow it. easy solution to that is to go to original dev section and follow the s-off thread. if you can s-off you can say bye bye to fastboot for the most part
Also, you need to S-OFF to downgrade touchscreen firmware.
But yeah, if you can get into recovery just wipe everything and flash a rom.. (has to be sense until you s-off and downgrade touchscreen firmware)
exad said:
Also, you need to S-OFF to downgrade touchscreen firmware.
But yeah, if you can get into recovery just wipe everything and flash a rom.. (has to be sense until you s-off and downgrade touchscreen firmware)
Click to expand...
Click to collapse
Never thought I had to pull the boot image out, flash that through fastboot, THEN install the OS. Thanks for the help guys, I tested it out with the copy of CM I had (unofficial port on the threads) and sure enough, it booted up fine. Of course, as stated previously, I can't click anything b/c of the upgraded touchscreen, so I'm omw to flashing a sense rom and getting s-off and a downgraded touch screen. Thanks for the help guys!
Dolfan058 said:
Never thought I had to pull the boot image out, flash that through fastboot, THEN install the OS. Thanks for the help guys, I tested it out with the copy of CM I had (unofficial port on the threads) and sure enough, it booted up fine. Of course, as stated previously, I can't click anything b/c of the upgraded touchscreen, so I'm omw to flashing a sense rom and getting s-off and a downgraded touch screen. Thanks for the help guys!
Click to expand...
Click to collapse
Yea man its a pain to get everything going. But once you s-off, downgrade etc this phone really flies on aosp. There's also an (optional) thread in development section to rid the splash screen of the red text. Its a simple 3 step process that should only take 20 seconds. After that you're golden
Sent from my One X using Tapatalk 2
InflatedTitan said:
Yea man its a pain to get everything going. But once you s-off, downgrade etc this phone really flies on aosp. There's also an (optional) thread in development section to rid the splash screen of the red text. Its a simple 3 step process that should only take 20 seconds. After that you're golden
Sent from my One X using Tapatalk 2
Click to expand...
Click to collapse
I'll bet. Getting S-off to work is killing me though. Keep running into the 99 unknown error while flashing the RUU file. I've done complete wipes, made sure i have superCID, and still no luck. So close and yet so far...
Dolfan058 said:
I'll bet. Getting S-off to work is killing me though. Keep running into the 99 unknown error while flashing the RUU file. I've done complete wipes, made sure i have superCID, and still no luck. So close and yet so far...
Click to expand...
Click to collapse
are you using a sense rom or aosp?
you need to be on a sense rom since your hboot is 2.14 because aosp requires you change a setting to allow you to soff which you cant since the touchscreen doesnt work.
if you are already on a sense rom. simulate a battery pull by pressing and holding power on your phone till the capacative buttons blink a bunch of times and then it shuts off. then try again.
Dolfan058 said:
I'll bet. Getting S-off to work is killing me though. Keep running into the 99 unknown error while flashing the RUU file. I've done complete wipes, made sure i have superCID, and still no luck. So close and yet so far...
Click to expand...
Click to collapse
I feel bad, I see all these people having trouble getting s-off to work, and I did it today without any hassles at all.
Sent from my Evita using XDA Premium
exad said:
are you using a sense rom or aosp?
you need to be on a sense rom since your hboot is 2.14 because aosp requires you change a setting to allow you to soff which you cant since the touchscreen doesnt work.
if you are already on a sense rom. simulate a battery pull by pressing and holding power on your phone till the capacative buttons blink a bunch of times and then it shuts off. then try again.
Click to expand...
Click to collapse
Definitely a sense rom (http://forum.xda-developers.com/showthread.php?t=1868236), still trying to work through it. It's so annoying, I'm dying to get the unofficial CM build on here already.
Dolfan058 said:
Definitely a sense rom (http://forum.xda-developers.com/showthread.php?t=1868236), still trying to work through it. It's so annoying, I'm dying to get the unofficial CM build on here already.
Click to expand...
Click to collapse
if a simulated battery pull isnt working for you, you can paste your cmd prompt window in here and i can check if anything weird is going on.
usually it should work by the third try or so if not after the first simulated battery pull.
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
I have the htc one x with Rogers, version 3.17.631.2... the RUU isn't available for this version.
***TAMPERED***
***UNLOCKED***
s-on
Currently I have no OS installed, I have been searching through forums on this website for about 6 hours last night with no solution. Can someone please help. Thanks
I also have the token ID saved on my computer.
What I tried was:
installing the stock rogers PJ83IMG.zip from here
but since my version is 3.17.631.2 it wouldn't let me downgrade to the 1.73.631.1 version
Any suggestions?
Why are you trying to ruu. In order to ruu downgrade you will need to be s-off.
Sent from my VENOMized HoxL
is there any way to be s-off with no OS installed?
1. How did you even delete the OS?
2. Do you have a custom recovery?
Sent from my HTC One XL using XDA Premium 4 mobile app
I was installing a custom rom, and erased the OS by accident in TRWP, and I can flash a custom recovery on my phone. What would i do after that though?
Also go to the cleanROM thread and use their boot.img to get things at least booting up
You don't need soff to flash img files via fastboot
Sent from my HTC One XL using XDA Premium 4 mobile app
alright im giving it a try atm!
Why not just flash a ROM? You already have a custom recovery on your phone, that's what TWRP is. Should you really be messing with your phone in the first place though? It doesn't seem like you have the faintest idea of what you're doing if you can't even recover from deleting your OS.
Sent from my Evita
I LOVE YOU GUYS!
its all fixed up
timmaaa said:
It doesn't seem like you have the faintest idea of what you're doing if you can't even recover from deleting your OS.
Click to expand...
Click to collapse
I tend to agree. There has also seems to be an increase of this occurrence in the last several months of "I wiped the OS accidentally and I don't know how to recover". Which is a bit troubling since the default wipe in TWRP is factory reset, Dalvik, and cache. The Wipe screen on TWRP explicitly states that this is all the is usually needed. If you wipe /system, you did so deliberately by going into the Advanced screen and picking it from there. Meaning the OP took extra steps to do something without knowing if it was necessary, and without knowing how to recover from it.
This also means the OP didn't create a nandroid backup in TWRP, which would have been a simple way to recover. This is basic, fundamental step that should be taken whenever modding a phone, but something n00bs seem to be "skipping" (or ignorant of) lately.
This type of behavior/mindset while modding does not bode well for the life of your phone.
actually the TWRP recovery i had on my phone was really outdated. i didnt have the advanced option. I simply had to pick from a list and i wiped it all without warning.
I've learned what i have done wrong, and thank you guys for it.
I currently have cleanROM flashed on my phone, but its really buggy.. it even turns off randomly and if i ever lose reception I will have to restart my phone to gain reception again. Not sure why this is happening? What do you guys suggest I do?
You need to search properly before posting. It's XDA rules. The reboots and signal loss problems have been discussed countless times in the Cleanrom thread. Read a few of the last pages and you're guaranteed to find the solution.
Sent from my Evita
ecakici said:
actually the TWRP recovery i had on my phone was really outdated. i didnt have the advanced option. I simply had to pick from a list and i wiped it all without warning.
Click to expand...
Click to collapse
That's a pretty lame excuse. My previous general notion still holds: You took deliberate steps to wipe the OS (/system) as that option is still not selected as default even on older versions of TWRP. And you were therefore wiping things willy-nilly without understanding what they were, whether they really needed to be wiped, or how to recover from them.
And you still should have made a nandroid (TWRP backup).
All in all, it implies a careless mindset while modding your phone (skipping steps and doing things without understanding).
I have searched the forum: [ROM][9/11] - CleanROM 7.0.P1 -★| Android 4.2.2! | Sense 5! | Lite! | Stable! |★-
and found that if i install hboot 2.15 on my phone it should stop rebooting and the reception would go back to normal right?
is there anything else I have to do.
please, if it isn't too much trouble link me to a guide that fixes these issue for the HTC One X (Rogers)
or just give me a few steps of how to fix these issue.
Thank you so much!
PS my battery life improved so much, i usually charged my phone twice a day, and I haven't charged my phone at since 7am today.
Yes. Flash the 2.15 firmware. It's in the first post of Turge's stock Sense 5 ROM thread in the development section.
Sent from my Evita
Step 1: SuperCID 11111111
Step 2: S-Off using beaups guide
Step 3: Flash the 2.15 firmware
Can someone link me to the best guide to follow for step 1?
You can do it two ways, here's the first:
Step 1: SuperCID with hex edit method.
Step 2: S-off with Facepalm S-off.
Step 3: Flash firmware.
Or the other way:
Step 1: S-off with Rumrunner S-off.
Step 2: SuperCID with fastboot command:
Code:
fastboot oem writecid 11111111
Step 3: Flash firmware.
I believe the second method is easier. The Rumrunner s-off process seems much easier, it doesn't require you to have SuperCID first to work. Once s-off is achieved you can easily change your CID by fastboot command as opposed to messing around with hex editing.
Sent from my Evita
thanks a lot guys!
i learned a lot through this forum!
HTC One X plus OS has been deleted accidentaly
ecakici said:
I LOVE YOU GUYS!
its all fixed up
Click to expand...
Click to collapse
Can u plz tell me how did u u fixed it
reachsoumendra said:
Can u plz tell me how did u u fixed it
Click to expand...
Click to collapse
What is your exact problem?
Sent from my Evita.
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.