Hi all,
New to the developer scene in terms of android phones so this current situation is causing a head scratch.
I think the problem lies because i've i tried flashing the x.x.401.x version when my phones branded software is x.x.61.x and i can't seem to find a RUU for it (20+ forum pages later). I've unlocked the HBOOT using HTCDev and i've managed to get clockworkmod on it under the recovery but the phone is still S-On and while I keep installing SU-3.0 through clockworkmod I still don't think I have root access according to ROM manager.
Any custom ROM I try to install (CyanogenMod, MIUI english fan version, MIUI official version) successfully installs on clockworkmod but just hangs on the HTC logo upon reboot and has been left for hours to make sure. I'm guessing this is down to actually having root or not?
As i've said I can't find the downgraded software version but the Europe RUU has the same radio as my phone, I am guessing that the branded software version is more important than matching radio's?
If anyone can help i'll be greatly appreciated because i'm starting to tear my hair out
Seany
EDIT: there is a x.x.61.x RUU for orange UK online somewhere but the radio is not the same (Radio_20.28b.30.0805U _38.03.02.11_M_release, as opposed to mine: 20.4801.30.0822U_3822.10.08.04_M) i'm guessing it would be a bad idea to flash until I get confirmation as I have no idea what would happen.
EDIT EDIT: That RUU is for an older version of gingerbread (V2.3.3 compared to V2.3.5 on mine) and HTC Sense V2.1 of which mine is V3.0
Then you should keep reading. Not sure what you getting at with the RUU stuff.
As for the custom ROM,.......
You need to flash the boot.img of the ROM you are trying to flash. Look into it.
fastboot flash boot boot.img
From what I've researched the RUU was needed in order to downgrade the bootloader from 2.00.0002 to 0.98.0000 in order to use the Revolutionary io in order to S-Off.
As for the custom ROM I've flashed the boot and now I've got bootloop for the cyanogenmod ROM, going to try the MIUI and see what happens. It's like it isn't installing the files but I can flash the boot
EDIT: MIUI also in bootloop, I'm thinking it has something to do with the flashing of the ROM using clockworkmod because it seems like it has no progression from the boot file.
Thankyou so much foX2delta, it was a boot.img issue and to do with flashing the boot, problem resolved
So I unlocked my Bootloader and achieved S-OFF.
I got root access. This is where things went wrong. I tried to install a custom ROM (CM9.0.1 if its relevant) and at first it appeared to be working. It boots the the boot screen however it gets stuck there. I can still access HBOOT but when I did I noticed its now S-ON.
Help! I feel the brickness spreading...
Duulicious said:
So I unlocked my Bootloader and achieved S-OFF.
I got root access. This is where things went wrong. I tried to install a custom ROM (CM9.0.1 if its relevant) and at first it appeared to be working. It boots the the boot screen however it gets stuck there. I can still access HBOOT but when I did I noticed its now S-ON.
Help! I feel the brickness spreading...
Click to expand...
Click to collapse
Hi,
What does your hboot say?
your device is not bricked
post your bootloader details as malybru said
Solved
I figured it out. Since it was S-ON (HBOOT 1.27.0000 by the way) I had to install 4Ext over CWM then wiped everything, enabled 4Ext Smartflash and reflashed it all. Works now, although I'm finding I don't like CM9. ANy suggestions for a good ROM?
Duulicious said:
I figured it out. Since it was S-ON (HBOOT 1.27.0000 by the way) I had to install 4Ext over CWM then wiped everything, enabled 4Ext Smartflash and reflashed it all. Works now, although I'm finding I don't like CM9. ANy suggestions for a good ROM?
Click to expand...
Click to collapse
Hi,
They are all HERE
ARHD is good.
malybru said:
Hi,
They are all HERE
ARHD is good.
Click to expand...
Click to collapse
Precisely what I was looking for! A thanks to you when I figure out how to do it.
Going to check out Android Revolution HD. Although I'm new to flashing ROMs and just rooted my phone yesterday. I don't know what it means by flash firmware first.
Duulicious said:
Precisely what I was looking for! A thanks to you when I figure out how to do it.
Going to check out Android Revolution HD. Although I'm new to flashing ROMs and just rooted my phone yesterday. I don't know what it means by flash firmware first.
Click to expand...
Click to collapse
Hi,
Any problems,post HERE
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
Need some help here please. My phone was running CM11, hboot 2.14 but I had to unlock the phone (locked to Rogers). So I s-off, and RUU the only version there is available. Now the unit is unlocked but running hboot 1.09. I tried flashing twrp so I can install CM back but fastboot say flash successful but won't boot to it in recovery, it boots straight to OS. Something I'm doing wrong? And should I upgrade hboot to 2.14 again? If so, how? Btw, the OS works fine but it'll ask if I want to install OTA but once it reboots, it just goes back to the OS without upgrading.
Thanks
You can find the most recent hboot & how to flash it here - http://forum.xda-developers.com/showthread.php?t=2659091
I found the easiest way was to flash the zip rather than use the FUU but use what works for you
Ahh, found the problem. Didn't know I have to manually reboot it after flashing. Thank you
Two years ago I had this phone and I wanted to flash. I did. I don't remember all the details of it, but I do know that someone on here helped me flash it and it ended up with a European(?) flash on it and I remember he helped me do something with the radio in order that it would take the flash. I also remember that the reason for the flash was so that TMO wouldn't charge me for tethering. In any case, here's the current situation. I sold the phone and the person came and said they were having issues... so I was trying to restore it to a TMOUS ROM. Eventually, I bricked it, and got the qualcom download mode issue. I found the thread on that on how to fix it, and I did. Now the phone boots to the recovery screen and does nothing else. I am unable to flash ANY of TMO's RUU's, some of the PG58IMG.zip files that I've been able to find all fail... very frustrating.
I followed another thread that talked about how to unlock the bootloader, which involved copying the Identifier Token and sending it in to HTC. I received the response, and ran the command and was successful in unlocking it. When the device rebooted, it even showed the Tmobile animated logo. When I go back into the boot loader, it now reads:
My bootloader screen reads as follows:
*** UNLOCKED ***
PYRAMID PVT SHIP S-ON RL
HBOOT - 1.27.0000
eMMC-boot
JAN 13 2012.17:33:34
Software info shows:
Android Version: 4.0.3
HTC Sense Version: 3.6
Software number: Blitz_2.0.0
Kernel: 3.0.16-gda3fdfc
[email protected]#1
Baseband version: 11.76A3504300U_11.24A.3504.31_M
Build Number 3.33.401.106 CL391535 release-keys
Browser version: WebKit/534.30
At this point, I would try any flash, any rom, any thing to get this phone working for the guy again. I am skittish about flashing anything from this point so I don't mess up and have to start all over somewhere. Can I flash something working from this point? Can I flash a TMO RUU from here?
I have the RUU_Pyramid_TMOUS_1.27.531.2_RADIO_10.42.9007.00P_10.11.9007.15_M_release_192098_signed.exe as well as several others. Id' rather put this phone onto something stock from tmo but will do a custom as long as the phone is restored to working order.
I won't say I'm a newb... but having been away from flashing for a while, I could really use some step by steps to get going again.
The computer I am using to flash with is a Windows XP machine with all the HTC drivers working etc.
**** UPDATE ****
The phone now boots up as it did when this all started. After I did the token thing and got the bin file from HTC, I applied it and the result was the boot loader info above. It got past the tmobile animated logo and actually into the phone starting up as new including applying all the settings I want. Awesome that the phone now functions like a phone again, but I would still like to flash an official TMO Rom to it to restore it back to like out of the box condition. Any help is appreciated.
read this thread
http://forum.xda-developers.com/showthread.php?t=1672425
rzr86 said:
read this thread
http://forum.xda-developers.com/showthread.php?t=1672425
Click to expand...
Click to collapse
I actually have read that... like 6 times to make sure I'm not missing anything. I do remember having to flash the radio back when I did my original flashing, and I think that process is preventing me from using any of the RUU's that I find. Are there any posts/files/resources that will help me flash the radio back to its default, so that I can then flash the RUU?
Also, I am S-ON already, but ANY RUU that I try to flash fails. Do I need to go to S-OFF and then RUU, then back to S-ON?
sc.lord said:
I actually have read that... like 6 times to make sure I'm not missing anything. I do remember having to flash the radio back when I did my original flashing, and I think that process is preventing me from using any of the RUU's that I find. Are there any posts/files/resources that will help me flash the radio back to its default, so that I can then flash the RUU?
Also, I am S-ON already, but ANY RUU that I try to flash fails. Do I need to go to S-OFF and then RUU, then back to S-ON?
Click to expand...
Click to collapse
no you don't need S-OFF
post your cid
rzr86 said:
no you don't need S-OFF
post your cid
Click to expand...
Click to collapse
CID is 11111111
I think I have it licked now.
Used the universal firmware and the viper 5.2.1 flash and it loaded just fine. Never got S-OFF on it, but the viper flash so far is working excellent.
sc.lord said:
CID is 11111111
I think I have it licked now.
Used the universal firmware and the viper 5.2.1 flash and it loaded just fine. Never got S-OFF on it, but the viper flash so far is working excellent.
Click to expand...
Click to collapse
how do you have supercid with S-ON?
also how did you flashed the universal firmware while on S-ON?
those two things can be done only on S-OFF
rzr86 said:
how do you have supercid with S-ON?
also how did you flashed the universal firmware while on S-ON?
those two things can be done only on S-OFF
Click to expand...
Click to collapse
Wish I could tell you.... hence the reason for the original help request.
I can tell you that I hit softbrick on it once and had to unbrick in linux.
Then I got the LOCKED with Security Warning. Then I got the unlock bin file from HTC Dev, used that and got back to UNLOCKED, with no security warning. Then I tried Rumunner without any success at all, stayed S-ON.
in any case, after trying just about everything I could think of, I found the viper post, saw that you said you don't need S-OFF to flash new rom... so i gave it a shot. Updated EXT, flashed the firmware, then the rom and it all went very smoothly. Phone's been working fine since. <shrug>