Related
I decided to downgrade to 1.85 for a fresh start after downgrading hboot to 1.09.000. 1.85, 1.73 RUUs failed and im trying 2.20 as we speak :// if this fails what are mmy options?
thanks
Did you relock the bootloader?
Sent from my HTC One XL using xda app-developers app
RUU's still fail after Jet to 1.09 due to version reported on mmcblk0p23.
Fix here:
http://forum.xda-developers.com/showthread.php?t=1671135
Note one user reported that going from 3.17 back to 1.81 ended in a bricked phone.
After Jet to 1.09 and altering mmcblk0p23 version, RUU accepted flashing, but bricked phone.
area51avenger said:
Did you relock the bootloader?
Sent from my HTC One XL using xda app-developers app
Click to expand...
Click to collapse
yes
twistedddx said:
RUU's still fail after Jet to 1.09 due to version reported on mmcblk0p23.
Fix here:
http://forum.xda-developers.com/showthread.php?t=1671135
Note one user reported that going from 3.17 back to 1.81 ended in a bricked phone.
After Jet to 1.09 and altering mmcblk0p23 version, RUU accepted flashing, but bricked phone.
Click to expand...
Click to collapse
I did this and I keep getting error 140- per this I am stuck in bl and I cant get adb
anyone? im in need of desperate help..
You don't need to run an ruu.... you downgraded your boot loader so just go on to flashing ROMs
You can flash the old radios and you should be set
No reason to put yourself through all this trouble
Sent from my One X using Tapatalk 2
superchilpil said:
You don't need to run an ruu.... you downgraded your boot loader so just go on to flashing ROMs
You can flash the old radios and you should be set
No reason to put yourself through all this trouble
Sent from my One X using Tapatalk 2
Click to expand...
Click to collapse
that's the problem, I relocked the BL, so now m stuck in fastboot with a locked boot loader any way I could get to adb so I can re unlock it?
Kole_Ackerson said:
that's the problem, I relocked the BL, so now m stuck in fastboot with a locked boot loader any way I could get to adb so I can re unlock it?
Click to expand...
Click to collapse
If you still have your unlock token
Fastboot flash unlocktoken unlocktoken.bin
Replace unlocktoken.bin with the location of your old unlock token
If you don't have it go through the steps on HTC dev to get a new one. You don't need to boot up the phone, just need fastboot
Sent from my One X using Tapatalk 2
superchilpil said:
If you still have your unlock token
Fastboot flash unlocktoken unlocktoken.bin
Replace unlocktoken.bin with the location of your old unlock token
If you don't have it go through the steps on HTC dev to get a new one. You don't need to boot up the phone, just need fastboot
Sent from my One X using Tapatalk 2
Click to expand...
Click to collapse
ok, I got the unlock token but its hanging on sending (0kb)
Kole_Ackerson said:
ok, I got the unlock token but its hanging on sending (0kb)
Click to expand...
Click to collapse
Make sure you're in fastboot not hboot
If that doesn't work reset your computer to make sure not programs are interfering with it
Sent from my One X using Tapatalk 2
it is in fastboot usb so ill reset my comp.
If it fails again, try running
Fastboot devices
To see if your device is showing up
Sent from my One X using Tapatalk 2
superchilpil said:
If it fails again, try running
Fastboot devices
To see if your device is showing up
Sent from my One X using Tapatalk 2
Click to expand...
Click to collapse
wow,i got it. it was my usb port... and ive been in 1.14 for so long I forgot that I can just unlock with 1.09... ill be buuying you a beer when I get paid.
Kole_Ackerson said:
wow,i got it. it was my usb port... and ive been in 1.14 for so long I forgot that I can just unlock with 1.09... ill be buuying you a beer when I get paid.
Click to expand...
Click to collapse
Nah don't worry about it!
Just helping out where I can
Sent from my One X using Tapatalk 2
Can only boot to bootloader and all RUU failed
I am in a bit of trouble at the moment. I will try to describe what I have done to end up where I am now.
I have a Telstra HTC One XL. Recently upgraded an already unlocked, rooted HOXL to JB using the OTA update (big mistake I know now). This upgraded the hboot to 2.14 and software to 3.17.8xxx.
Spent a lot of time trying to re-root. TWRP didn't work (no touch response). So I eventually found the Interim CWM Recovery (no touch) by Modaco. This seemed to work well and I managed to root the phone.
Then i followed the instructions to flash to KingBeatZ 1.2.0 ROM. Booted fine but had no touch response too.
So I wiped KingBeatZ 1.2.0 and went for the nightly CM10. Again, booted fine but no touch response.
OK, so I figured I should just go back to my restored data. Tried that but apparently no restore data (didn't realise a wipe wiped the restore data as well, what is the point of that?)
So I decided to wipe CM10 to try flashing the Stock Rooted Telstra ROM by pablo11. This wipe however seems to have wiped incorrectly and this is where my real problem begins. I can now only boot to BL and Recovery. I cannot mount the sdcard so I have no way of pushing ROMS to my phone. I have tried a Telstra RUU and the latest Asia one. About to try the 1.89 Telstra RUU but I don't think that will make any difference. The setups do not detect an existing version on my phone, and all fail with Error 155. I have read that this error generally occurs due to unlocked bootloader so I have already relocked it.
I do not know what I should do now to restore any functionality to my HOXL. Any help would be greatly appreciated.
o0okiato0o said:
So I decided to wipe CM10 to try flashing the Stock Rooted Telstra ROM by pablo11. This wipe however seems to have wiped incorrectly and this is where my real problem begins. I can now only boot to BL and Recovery. I cannot mount the sdcard so I have no way of pushing ROMS to my phone. I have tried a Telstra RUU and the latest Asia one. About to try the 1.89 Telstra RUU but I don't think that will make any difference. The setups do not detect an existing version on my phone, and all fail with Error 155. I have read that this error generally occurs due to unlocked bootloader so I have already relocked it.
Click to expand...
Click to collapse
You can't run the RUU for a different carrier (CID), and you can't run an RUU for an older version. So neither 1.89 Telstra or an Asia RUU will work. You may be stuck waiting for the 3.17 RUU (don't think its been posted yet?).
You might also be able to make your own RUU by sticking the ROM in the Development forum in an RUU package. I don't know the specifics, and haven't done it myself. But I think it was done for Rogers, which never had a proper RUU package. So others might be able to advise you better on this.
redpoint73 said:
You can't run the RUU for a different carrier (CID), and you can't run an RUU for an older version. So neither 1.89 Telstra or an Asia RUU will work. You may be stuck waiting for the 3.17 RUU (don't think its been posted yet?).
You might also be able to make your own RUU by sticking the ROM in the Development forum in an RUU package. I don't know the specifics, and haven't done it myself. But I think it was done for Rogers, which never had a proper RUU package. So others might be able to advise you better on this.
Click to expand...
Click to collapse
You would need the .img files EX: system.img boot.img
Since our ROMs aren't packaged that way it won't work.
There's a way to create the system.img but its beyond me, and I do believe if it isn't signed it will fail
The only thing you can flash in hboot by ruu without s-off without being signed would be a boot.img
I would suggest trying to flash a stock ROM and a different kernel, or waiting for the ruu
Sent from my One X using Tapatalk 2
superchilpil said:
You would need the .img files EX: system.img boot.img
Since our ROMs aren't packaged that way it won't work.
There's a way to create the system.img but its beyond me, and I do believe if it isn't signed it will fail
The only thing you can flash in hboot by ruu without s-off without being signed would be a boot.img
I would suggest trying to flash a stock ROM and a different kernel, or waiting for the ruu
Sent from my One X using Tapatalk 2
Click to expand...
Click to collapse
Could you elaborate on the different kernel bit? I have just tried flashing a stock rom via the fastboot flash zip rom.zip method, but it fails the hboot check. Cheers
o0okiato0o said:
Could you elaborate on the different kernel bit? I have just tried flashing a stock rom via the fastboot flash zip rom.zip method, but it fails the hboot check. Cheers
Click to expand...
Click to collapse
Take a stock ROM and pull out the boot.img
And fastboot flash boot boot.img just to make sure it flashes
Then flash the ROM in recovery
Sent from my One X using Tapatalk 2
Hey Guys,
So yesterday I decided I wanted to root my HTC One X (Rogers Canada Unlocked) so I followed the tutorials and unlocked the bootloader and went to install CWM recovery. I flashed it via fastboot, then when I restarted into recovery I was in a bootloop saying that this is for development purposes only, and it just kept restarting. So I booted back in to fastboot mode and installed TWRP 3.0.0.0 but the touch controls didnt work, so I reflashed TWRP 3.0.0.1 and the recovery was accessible. I tried to flash a rom and it said it succeeded but it just keeps going into that bootloop and there is no sign of the old stock ROM on the device at all. So I decided today to relock the bootloader, clear the cache and find a Rogers RUU to flash back on the phone with ARUwizard. It fails to install because of a conflict with my bootloader (obviously because mine is 2.14.000) but there is nowhere on the world wide web that has an updated Rogers RUU to flash to my phone. The only good thing that came out of it, is it just stays on the HTC splash screen and doesn't have the red development purposes only writing. I need some help, thanks in advance. If there is anything I missed please let me know.
Phone: HTC One X (Rogers Canada Unlocked) Evita
Bootloader Relocked, S-ON, Hboot 2.14.000
Secondary: HTC Incredible S (Vigin Mobile Canada)
Bootloader Unlocked, S-OFF, C10 ROM
RUU I have found in the past to be more difficult than the root process. make sure drivers installed and usb plugged into the back of pc.
CMW probably corrupt your SD card btw.
Use twrp. And looks like you did everything right for your flashing process except "fastboot flash boot.img" you could probably get the rom you want working if you extract the boot.img and flash in adb.
Sent from my HOX w/CM10.1
The problem is that there is no Rogers RUU for the latest hboot (2.14) that the OP is on. For some reason (that I've never completely understood) Rogers firmwares often don't have corresponding RUUs ever released. And he can't use an old RUU, as it fails version check (you can't run an RUU for a firmware version and/or hboot older than what is on the phone). Maybe they will release a Rogers RUU for the firmware that goes with 2.14. But it wouldn't surprise me if they never do.
The TWRP versions mentioned in the OP look wrong. The newest TWRP version is 2.3.3.1, and is supposed to be compatible with 2.14 (although I think some are still having some troubles). I'd start there, by re-unlocking and installing the latest TWRP:
http://forum.xda-developers.com/showthread.php?t=1677447
DvineLord posted the recovery img in Post 432.
If the OTA file is a complete zip, with hboot, sbl images, etc. It can be used as an RUU, but it isn't an automated process. as long as you install TWRP, and then install a ROM/kernel, your phone will work again
jjswain, if you need to RUU, find the complete zip OTA package, and follow the steps here http://forum.xda-developers.com/showthread.php?t=1974272
The same can be done in windows, start at step 9
subarudroid said:
looks like you did everything right for your flashing process except "fastboot flash boot.img" you could probably get the rom you want working if you extract the boot.img and flash in adb.
Sent from my HOX w/CM10.1
Click to expand...
Click to collapse
I'm in the same boat as OP, I did that exactly as I've flashed boot.img separate before and that fixes things. Problem is that once I flash boot.img and then flash the .zip it came out of the rom boots to completion, but the touch screen won't work. I think the solution is just to wait until 2.14.0000 is supported by other roms.
veemodz823 said:
I'm in the same boat as OP, I did that exactly as I've flashed boot.img separate before and that fixes things. Problem is that once I flash boot.img and then flash the .zip it came out of the rom boots to completion, but the touch screen won't work. I think the solution is just to wait until 2.14.0000 is supported by other roms.
Click to expand...
Click to collapse
I also flashed the boot, did factory reset, cleared cache, and davlik, installed rom (5 different ones to be exact) and they all booted but no touch screen either :crying: Any other idea's to try? Glad it's not bricked...it's just pricked for now
jjswain said:
I also flashed the boot, did factory reset, cleared cache, and davlik, installed rom (5 different ones to be exact) and they all booted but no touch screen either :crying: Any other idea's to try? Glad it's not bricked...it's just pricked for now
Click to expand...
Click to collapse
You can downgrade your hboot if you can access recovery to push a broken partition 4, then flash an old hboot, and then edit your software info and downgrade.. if you aren't comfortable we can do this over team viewer if you would like.
This sounds very similar to the situation I'm in. People have said the reason why there is no touch is because of 3.17 blah blah blah. If you want to read up on where I'm at, here's the link. We're pretty much in the same boat bro.
http://forum.xda-developers.com/showthread.php?t=2102729
absolutelygrim said:
You can downgrade your hboot if you can access recovery to push a broken partition 4, then flash an old hboot, and then edit your software info and downgrade.. if you aren't comfortable we can do this over team viewer if you would like.
Click to expand...
Click to collapse
I'm not sure if it's the hboot version that's messing it up or if it's the softare 3.17 that we OTA. I'm sure if we were still on ICS then rooted we'd be fine, but because we did the JB update and then attempted root....I think that's the issue
jjswain said:
I'm not sure if it's the hboot version that's messing it up or if it's the softare 3.17 that we OTA. I'm sure if we were still on ICS then rooted we'd be fine, but because we did the JB update and then attempted root....I think that's the issue
Click to expand...
Click to collapse
You have to downgrade your hboot to ruu downgrade to get the old firmware
absolutelygrim said:
You have to downgrade your hboot to ruu downgrade to get the old firmware
Click to expand...
Click to collapse
I could use this rom correct? Its based on 3.17
http://forum.xda-developers.com/showthread.php?t=2075783
Installed that Rom, phone works perfect except for LTE
Sent from my HTC One XL using xda app-developers app
Works..just shows 4g, but speedtest proves its lte
Search for TWRP for the HTC One X Evita (the north American model of the HTC one x) and make sure that the version is 2.3.3.1.
Then install Viper XL by Team Venom.
When installing the rom wipe everything that TWRP will let you wipe, then mount the phone as USB storage put the ZIP file on the phone, and then flash it.
If that doesn't work I dunno what will.
---------- Post added at 06:28 PM ---------- Previous post was at 06:17 PM ----------
So first you need to flash TWRP for HTC One X evita, you are going to need version 2.3.3.1.
Boot into the new recovery and wipe everything, SD Card, System everything.
Then download Viper XL by Team Venom, go to the mount menu, make sure everything is unchecked, and mount the phone as USB storage and put the rom on the phone.
Flash the rom and you now have a working phone.
jjswain said:
Installed that Rom, phone works perfect except for LTE
Sent from my HTC One XL using xda app-developers app
Works..just shows 4g, but speedtest proves its lte
Click to expand...
Click to collapse
This depends on the network icon set that was flashed with the rom you chose. For some roms, the values are as follows:
E - Extended network
3G - 3G
H - 4G
4G - LTE
On other icon sets, the last one is replaced by LTE - LTE. Some roms will actually let you install/use different network icons, so you could always take a look into something like that.
^what he said ^ also you can go to dialer and *#*#info#*#* go to phone info and see what network your connected to.
Sent from my HOX w/CM10.1
I'm somewhat in the same position as the OP, but every RUU or rom I try fails at signature check (although the latest one posted above seemed to work but then nothing at bootup). Being that I have stock CID ROGER001, and the same HBOOT 2.14 Evita, Radio .23a.32.09.29 and S-ON, is hoping a Rogers RUU is released my only option?
Well given my specs above I can confirm that the Hatka rom works (insofar as it has booted up and I have a phone again!!) Thank you so much for the link jjswain!!
you will only be able to downgrade if you s-off. i assume you are unlocked with twrp or the new cwm flashed if so as long as you wipe first you should be able to flash roms fine unless you are trying to flash non-evita roms for some reason. which roms have you tried flashing and what version of recovery are you using?
So... I had an awkward moment where I began looking at all the roms and seeing that they were all for a OneX not OneXL...:silly: Thanks for asking me to go through those as I probably would not have realized my mistake! Just flashed Viper3.2.6XL and I'm much happier with the look and feel.
I updated my One X Evita to jelly bean....I want to root my phone again. My last one x was on ICS and it was rooted but I got a new One X and now have Jelly Bean. My Hboot is 2.14. I been reading that people have been losing the touch screen? Has that problem been fixed with the new twrp2?
mcnaught82 said:
I updated my One X Evita to jelly bean....I want to root my phone again. My last one x was on ICS and it was rooted but I got a new One X and now have Jelly Bean. My Hboot is 2.14. I been reading that people have been losing the touch screen? Has that problem been fixed with the new twrp2?
Click to expand...
Click to collapse
You can't root now. There is no root method for jelly bean yet.
Sent from my Nexus 7 using Tapatalk HD
Hello, I have Unlocked bootloader, S-ON and rooted telephone , can I put custom ROM, or pre-rooted RUU-ICS, Version HBOOT is 2.00.02.
I Know that must downgrade on 09.000.02 hboot-a, that I have S-off.
Can I put custom ROM, or RUU, or pre-rooted ROM, I want ICS-RUU. on phone with this caracteristics.
I really confused because S-ON, did I can do this.
Thanks advanced.
dejanxxxx said:
Hello, I have Unlocked bootloader, S-ON and rooted telephone , can I put custom ROM, or pre-rooted RUU-ICS, Version HBOOT is 2.00.02.
I Know that must downgrade on 09.000.02 hboot-a, that I have S-off.
Can I put custom ROM, or RUU, or pre-rooted ROM, I want ICS-RUU. on phone with this caracteristics.
I really confused because S-ON, did I can do this.
Thanks advanced.
Click to expand...
Click to collapse
Yes you can. You don't need to achieve S-OFF to install custom ROM. I don't recommend you to install Official RUU ICS because it has been reported many times to be buggy and laggy. If you want a better feeling of that, you should install IceDS or IceCreamSaga ROMs.
I have another problem. I wanted put RUU-ICS, but always get message ERROR 155. Every time, I dont know why. I am from Serbia, and people from HTC send me a link for RUU - ICS, and when I start with proces- eject ERROR 155-every time, after I tried another RUU-ICS again error 155, I tried 4 RUU- ics, and always error 155.
Why I get always this message, and what I do?. S-ON, bootloader-relocked, rooted phone.
i tried this and i flashed a custom rom with s-on and it just keeps booting into recovery mode
dejanxxxx said:
I have another problem. I wanted put RUU-ICS, but always get message ERROR 155. Every time, I dont know why. I am from Serbia, and people from HTC send me a link for RUU - ICS, and when I start with proces- eject ERROR 155-every time, after I tried another RUU-ICS again error 155, I tried 4 RUU- ics, and always error 155.
Why I get always this message, and what I do?. S-ON, bootloader-relocked, rooted phone.
Click to expand...
Click to collapse
Is your phone branded to any mobile carrier- by any chance?
Because if it was, to override the branded version by WWE 4.0.4
( world wide english )
you should use < gold card >
http://forum.xda-developers.com/showthread.php?t=1248095
If i remember correctly, error 155 refers to CID mismatch- wrong RUU version
But in your best interest is to double check what others say
Edit: unles something has changed,
there was only one ics ruu version for desire s
to be found on htcdev website..
How come you found four of them?
seagheart89 said:
i tried this and i flashed a custom rom with s-on and it just keeps booting into recovery mode
Click to expand...
Click to collapse
Did you flash the boot.img?
"If I were two-faced, would I be wearing this one?"
- Abraham Lincoln (1809-1865)
jugg1es said:
Did you flash the boot.img?
"If I were two-faced, would I be wearing this one?"
- Abraham Lincoln (1809-1865)
Click to expand...
Click to collapse
it didnt give me an option for boot.img it used the aroma installer
message ERROR 155 for original RUU ICS - means that you have unlocked bootlocker.
You must relock bootlocker with fastboot and start installation again - it will work.
Commant: "fastboot oem lock"
BR.
continiven said:
message ERROR 155 for original RUU ICS - means that you have unlocked bootlocker.
You must relock bootlocker with fastboot and start installation again - it will work.
Commant: "fastboot oem lock"
BR.
Click to expand...
Click to collapse
I have this problem. Because my girl friend dont want custom ROM, I install RUU-ICS. But always when start flashing,eject 155 error, bootloader first unlocked, after before process I locked again bootloader,and in HBOOT writing RELOCKED-you say this is mistake because bootloader is unlocked, it not true- on my case.
After I use HTC SYNC- register phone and recognized, everything pass easy,and ROM is installed.
seagheart89 said:
it didnt give me an option for boot.img it used the aroma installer
Click to expand...
Click to collapse
Since your device is still s-on you need flash the boot.img manually.
Extract the boot.img from the rom, boot your device into fastboot and enter
Code:
fastboot flash boot boot.img
Flashing pacman into my friend's desire s , after unlocking it, i tried every recovery, formatting every partition manually, and flashing the boot.img using fast boot, but could not get beyond the white HTC screen. I wonder why it was being so... I own a one s, and have used multiple sense and aosp based ROMs on it without a hiccup (am s-on).
Any help would be really appreciated
Thanks a lot
Sent from my One S using xda premium
syed.shoaib said:
Flashing pacman into my friend's desire s , after unlocking it, i tried every recovery, formatting every partition manually, and flashing the boot.img using fast boot, but could not get beyond the white HTC screen. I wonder why it was being so... I own a one s, and have used multiple sense and aosp based ROMs on it without a hiccup (am s-on).
Any help would be really appreciated
Thanks a lot
Sent from my One S using xda premium
Click to expand...
Click to collapse
This might be the reason http://forum.xda-developers.com/showthread.php?t=1943524
[OFF-TOPIC] Non-Sony screen panel DS users lounge
"Happiness is good health and a bad memory."
- Ingrid Bergman (1917-1982)
I bought the phone when it first came out. Play around with unlock bootloader, root and custom roms. I Currently have an older version of CM running on the phone with custom recovery.
I haven't touch the phone for months, and certainly I havent follow the forum for a long time. Recently I wanted to start use this phone again. I would like some help to get this phone up-to-date again.
1. Is there a way to turn this phone to the latest stock configuration? I will follow the forum to unlock, s-off, root again. But I wanted to turn it back to stock completely with latest firmware and all.
2. what are the latest version of radio, kernel, stock rom version and so on? how can I get them?
3. Any instruction would help.
My questions may sound very noob, but I hope someone can point me to the right way.
jzhang0818 said:
I bought the phone when it first came out. Play around with unlock bootloader, root and custom roms. I Currently have an older version of CM running on the phone with custom recovery.
I haven't touch the phone for months, and certainly I havent follow the forum for a long time. Recently I wanted to start use this phone again. I would like some help to get this phone up-to-date again.
1. Is there a way to turn this phone to the latest stock configuration? I will follow the forum to unlock, s-off, root again. But I wanted to turn it back to stock completely with latest firmware and all.
2. what are the latest version of radio, kernel, stock rom version and so on? how can I get them?
3. Any instruction would help.
My questions may sound very noob, but I hope someone can point me to the right way.
Click to expand...
Click to collapse
flash a sense rom.
S-off
Ruu to latest.. with s-off bootloader can remain unlocked.
Flash a recovery ( nothing higher than twrp 2.3.3.1 cause of wiping issues)
Then flash a rom.
Hopefully that gets you on track
Sent from my HTC One XL running super smooth Sense 5
31ken31 said:
flash a sense rom.
S-off
Ruu to latest.. with s-off bootloader can remain unlocked.
Flash a recovery ( nothing higher than twrp 2.3.3.1 cause of wiping issues)
Then flash a rom.
Hopefully that gets you on track
Sent from my HTC One XL running super smooth Sense 5
Click to expand...
Click to collapse
Can you plz point me to a link for latest RUU?
Everything you need is in redpoint73's resource compilation thread stickied in the android development section.
Sent from my HTC One X using xda app-developers app
exad said:
Everything you need is in redpoint73's resource compilation thread stickied in the android development section.
Sent from my HTC One X using xda app-developers app
Click to expand...
Click to collapse
I have decided to run RUU and take the phone back to stock.
So i fastboot oem lock. and try to run RUU from computer.
I get error 170.
now my phone stuck in the bootloader, cant boot into system. cant boot into recovery.
Please help~!!!
jzhang0818 said:
I have decided to run RUU and take the phone back to stock.
So i fastboot oem lock. and try to run RUU from computer.
I get error 170.
now my phone stuck in the bootloader, cant boot into system. cant boot into recovery.
Please help~!!!
Click to expand...
Click to collapse
Seems u f'd up.. what exactly happened
Sent from my HTC One XL running super smooth Sense 5
31ken31 said:
Seems u f'd up.. what exactly happened
Sent from my HTC One XL running super smooth Sense 5
Click to expand...
Click to collapse
Thanks for your reply.
All I pretty much did was fastboot oem lock.
then try to connect to computer and run RUU. (I was told this is the way to restore the phone back to stock completely).
now all i can do is boot into bootloader. can't go in recovery can't boot into system.
I am looking for some to restore this phone completely to stock. (I don't need unlock or root).
I am only looking to make this phone an test phone for an new app that we are developing.
thank you
31ken31 said:
flash a sense rom.
S-off
Ruu to latest.. with s-off bootloader can remain unlocked.
Flash a recovery ( nothing higher than twrp 2.3.3.1 cause of wiping issues)
Then flash a rom.
Hopefully that gets you on track
Sent from my HTC One XL running super smooth Sense 5
Click to expand...
Click to collapse
He told you how to get to stock here. I don't see relocking in there anywhere so why would you relock? You can relock the phone after s-off and ruu. This phone will brick if you have supercid and ruu or update to 3.18 so returning completely stock is difficult to say the least.
Sent from my HTC One X using xda app-developers app
Hello,
I am trying to flash CleanRom 7.0 or any JB rom on my HTC One X (AT&T) but always gets stuck in bootloop (phone does not go past boot screen after flashing). This is what i have done.
The phone is on AT&T 1.82 stock room (rooted, SuperCID, S-Off). The phone was on some older HBoot version so I upgraded it to 2.15. Radio is 0.17.32.09.12. And I have TWRP recovery.
So I made a nadroid backup in recovery and than tried to install AT&T 3.82 rooted (downloaded from XDA, may be without radio and all). After successful flashing when I tried to reboot the system it got stuck on AT&T boot screen. So I rebooted in recovery and wiped everything. After that I tried to install CleanROM 7.0 R2 and same thing happened and even I tried latest elemental kernel but same thing is keep happening.
Can you please help me with this?
Thanks
At&t 3.82 rooted ROM? Where did you download that? It doesn't look familiar. What are your bootloader details? Which version of TWRP? How did you upgrade your hboot?
Sent from my Evita
timmaaa said:
At&t 3.82 rooted ROM? Where did you download that? It doesn't look familiar. What are your bootloader details? Which version of TWRP? How did you upgrade your hboot?
Sent from my Evita
Click to expand...
Click to collapse
Hey,
Thanks for reply. Sorry I think I mis-wrote it. It's AT&T 3.18 ROM from following link:
http://forum.xda-developers.com/showthread.php?t=2181891
I will check and let you know TWRP version when I get back home. I am not sure about the bootloader details either, what you need to know about the boot loader to help me?
I upgraded hboot by upgrading firmware to 2.15 by using instructions at one of the threads at xda (using adb and fastboot commands and pushing a 2.15 zip to device when it is in bootloader).
Note that I was never able to install any custom ROM on HTC One X. I rooted it before a year or so tried to install CleanROM 5.1 (I guess) but it din't work. I also tried few other ROMs but nothing worked and I gave up. Recently I read that I may need to update Hboot to flash the ROMs. So I did it (had a hard time installing drivers on windows 8 and ultimately have to try winXP!). Still after all this it is not working.
Let me know if you can suggest something based on this.
Thanks
alex8525 said:
Hey,
Thanks for reply. Sorry I think I mis-wrote it. It's AT&T 3.18 ROM from following link:
http://forum.xda-developers.com/showthread.php?t=2181891
I will check and let you know TWRP version when I get back home. I am not sure about the bootloader details either, what you need to know about the boot loader to help me?
I upgraded hboot by upgrading firmware to 2.15 by using instructions at one of the threads at xda (using adb and fastboot commands and pushing a 2.15 zip to device when it is in bootloader).
Note that I was never able to install any custom ROM on HTC One X. I rooted it before a year or so tried to install CleanROM 5.1 (I guess) but it din't work. I also tried few other ROMs but nothing worked and I gave up. Recently I read that I may need to update Hboot to flash the ROMs. So I did it (had a hard time installing drivers on windows 8 and ultimately have to try winXP!). Still after all this it is not working.
Let me know if you can suggest something based on this.
Thanks
Click to expand...
Click to collapse
Ok so you need to give us more info
Are you s-off
What version of twrp do you have
These things matter when you flash a rom. If you are s-on you need to flash boot.img after flashing. Just do
Fastboot flash boot.img
Sent from my HTC Butterfly s using Tapatalk
phonegeekjr said:
Ok so you need to give us more info
Are you s-off
What version of twrp do you have
These things matter when you flash a rom. If you are s-on you need to flash boot.omg after flashing.
Sent from my HTC Butterfly s using Tapatalk
Click to expand...
Click to collapse
Yes I am S-Off. I will let you know the version of TWRP when I get back home since I don't have phone with me right now. By the way I used goomanager to update TWRP, if that helps.
Thanks,
phonegeekjr said:
Ok so you need to give us more info
Are you s-off
What version of twrp do you have
These things matter when you flash a rom. If you are s-on you need to flash boot.img after flashing. Just do
Fastboot flash boot.img
Sent from my HTC Butterfly s using Tapatalk
Click to expand...
Click to collapse
One more thing, I am using TWRP to flash the ROM. Is it a correct way? or I need to flash it using fastboot commands (like you suggested for boot.img)?
I am not much fammilier with TWRP and HTC One X so.
Thanks
K so if you are s-off then you can just flash it. If you wernt then you would need to flash boot.img. now you can try to flash the boot.img. it might not fix it but start small and work up.
Sent from my HTC Butterfly s using Tapatalk
alex8525 said:
One more thing, I am using TWRP to flash the ROM. Is it a correct way? or I need to flash it using fastboot commands (like you suggested for boot.img)?
I am not much fammilier with TWRP and HTC One X so.
Thanks
Click to expand...
Click to collapse
TWRP is the correct way to install ROMs, but I have a feeling that your current version of TWRP is your problem. Some (2.4.x, 2.5.x) are buggy and have major problems. If your TWRP version is either of those that I've just mentioned you can update it to a known bug-free version like this:
Download the modified version of TWRP*2.6 from here. Put the file in your fastboot folder. Connect phone in fastboot mode, open command prompt from within fastboot folder, issue the following commands:
Code:
fastboot flash recovery "filename.img"
(the exact filename, minus the talking marks)
Code:
fastboot erase cache
Code:
fastboot reboot-bootloader
Sent from my Evita
That's the reason I asked what twrp version he had
Sent from my HTC Butterfly s using Tapatalk