Hey guys,
I have been looking everywhere and I know there are tonnes of threads on this but I cannot seem to find anything that will work for me.
Here is my dilemma:
My current Rogers HTC One X is on a PACMAN ROM, the last few days it has been awful. Several bootloops and it will not stay on. My current setup is this:
Unlocked
S-off
HBOOT - 2.14
Radio - 0.23a.32.09.29
I feel that the issue is maybe I need to be using firmware 3.18 and HBOOT 2.15, but for the life of me cannot find anything for Rogers to get me to this point.
Like I said, I am sure there are hundreds of threads but I have looked and cannot seem to find what I am looking for.
I am wondering if i should go to stock and start over....if so, I hear that I cna use the AT&T RUU....again, whatever info or direction that anybody can point me will be greatly appreciated.
Have you tried clean flashing the ROM again? Have you tried flashing another ROM? You show that you have the 2.14 hboot but then mention you have the 2.15 hboot, which one is it?
Sent from my Evita
timmaaa said:
Have you tried clean flashing the ROM again? Have you tried flashing another ROM? You show that you have the 2.14 hboot but then mention you have the 2.15 hboot, which one is it?
Sent from my Evita
Click to expand...
Click to collapse
I have 2.14, I cleaned flashed with the Beanstalk ROM, seems to be ok, a couple of freezes and reboots still.
I've experienced the same issues with Beanstalk, try flashing the Torched kernel and those issues should stop.
Sent from my Evita
uyndot different
timmaaa said:
I've experienced the same issues with Beanstalk, try flashing the Torched kernel and those issues should stop.
Sent from my Evita
Click to expand...
Click to collapse
I flashed the kernel, everything was working ok for a bit.
I rebooted the phone and it stuck at the Beanstalk flash screen, so I had to reflash everything again. Started to reinstall everything and it did it again. So my phone is now stuck at the Beanstalk flash screen.
I updated the ROM to 10/27 as well.
I would like to flash it back to stock and start over but cannot find the stock RUU for Rogers, I have looked but everything seems to be AT&T RUU's.
http://androidruu.com
Sent from my Evita
Perfect
So i will download the stock firmware and the 2 OTAs
Flash back to stock, will I need to flash the OTAs or will they just automaticlaly download once I am back to stock. I did this once before but cannot remember??
I know there is a link on this site showing how to flash back to stock, I use to have it as a favorite but I formatted the pc, so i dont have it any longer. Would you happen to have a link??
Hate to bug you for this, just want to get my phone back up and running.
Thanks for all you help
You can try using the "search for updates" tool in settings, it may or may not work. I don't have a link but there really isn't much to using an RUU, just connect your phone in fastboot mode and start the exe program in Windows. Make sure no other programs are running and make sure screen saver / hibernation is turned off. Follow the prompts once the program has initiated and that's it.
Sent from my Evita
timmaaa said:
You can try using the "search for updates" tool in settings, it may or may not work. I don't have a link but there really isn't much to using an RUU, just connect your phone in fastboot mode and start the exe program in Windows. Make sure no other programs are running and make sure screen saver / hibernation is turned off. Follow the prompts once the program has initiated and that's it.
Sent from my Evita
Click to expand...
Click to collapse
Awesome.....for some reason i thought there were a bunch of fastboot commands that had to be done for RUUing. If the phone doesnt automaticlaly find the OTAs, then i can do each one separately the same way as the stock firmware.
If it doesn't find the OTA's and install them automatically, you can install them manually through the stock recovery.
Sent from my Evita
timmaaa said:
If it doesn't find the OTA's and install them automatically, you can install them manually through the stock recovery.
Sent from my Evita
Click to expand...
Click to collapse
Alright, was able to flash back to stock and then it automatically updated the OTAs
I am now back at firmware 3.17.631.2(4.1.1), hboot 2.14, with s-off
Everyone is taking about being on 3.18 and hboot 2.15, does that make a big diference?
I havent reflashed my ROM yet....will also flash the kernel at the same time
anything else i should do before i flash my ROM
mikeyb1974 said:
Alright, was able to flash back to stock and then it automatically updated the OTAs
I am now back at firmware 3.17.631.2(4.1.1), hboot 2.14, with s-off
Everyone is taking about being on 3.18 and hboot 2.15, does that make a big diference?
I havent reflashed my ROM yet....will also flash the kernel at the same time
anything else i should do before i flash my ROM
Click to expand...
Click to collapse
Flashing 2.15 is only really suggested for sense 5 4.2 roms as it will eliminate any issues you might run into. While its often ok to flash both rom and kernel at the same time I always push for a full boot after a rom flash before flashing something else and factory reset prior to flashing the kernel.
3.18 software vs 3.17 is just carrier related and makes no difference.
exad said:
Flashing 2.15 is only really suggested for sense 5 4.2 roms as it will eliminate any issues you might run into. While its often ok to flash both rom and kernel at the same time I always push for a full boot after a rom flash before flashing something else and factory reset prior to flashing the kernel.
3.18 software vs 3.17 is just carrier related and makes no difference.
Click to expand...
Click to collapse
Good to know, i havent used any sense 5 ROMS, been using PACMAN, Beanstalk, ones like that
Since I am on Rogers, is there even a way to get to 3.18, would it have to be a different carriers firmware to get there??
mikeyb1974 said:
Good to know, i havent used any sense 5 ROMS, been using PACMAN, Beanstalk, ones like that
Since I am on Rogers, is there even a way to get to 3.18, would it have to be a different carriers firmware to get there??
Click to expand...
Click to collapse
The 2.14 firmwares are practically identical except the radio firmwares theres really no point but you could run an at&t ruu if you wanted. 3.18 is the software version which will be overwritten when you flash a new rom anyway so its beyond pointless.
Related
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
Hi everyone,
I don't quite have 10 posts yet, so I can't post in the UrDroid thread.
I had UrDroid 1.8, and it worked just fine, had some wifi issues (sometimes after turning the wifi off, it wouldn't turn on again unless I rebooted), so I upgraded to 1.9
Now I have a few issues:
It stays "connected" to a wifi network even after losing connection
Occasionally, after rebooting, my Beautiful Widgets go away and my default keyboard reverts to the stock keyboard (from swype)
occasionally I cannot turn the wifi back on after turning it off without a reboot
That's about it. If anyone has any ideas, please let me know. Thanks! :good:
Could be just bugs in the software. Recommend trying different ROMs
Sent from my Carbon-ize Evita using xda-developers app
I really wish I could try other roms, for some reason UrDroid is the only one that actually works, I have no idea why this is!
For instance, when flashing any verison of CM, after flashing and rebooting, it stays stuck on the loading screen, and doesn't go further, even after waiting a half an hour. AOKP and the others basically brick my phone. I think it has something to do with the UrDroid using Aroma Installer that seems to work well with my phone and twrp. I'm a bit of a n00b, so don't know for sure.
Was hoping someone else had these issues and could tell me how they fixed them.
Herc08 said:
Could be just bugs in the software. Recommend trying different ROMs
Sent from my Carbon-ize Evita using xda-developers app
Click to expand...
Click to collapse
What recovery are you using and version?
What hboot do you have?
Sent from my One X using xda app-developers app
Sorry for the late reply,I've had the darndest time getting into recovery since installing UrDroid 1.9!
I have HBOOT-1.14.002 and TWRP v. 2.3.1.0
Thanks for any help you could offer- I like UrDroid, but would like to try CM or the other ones!
exad said:
What recovery are you using and version?
What hboot do you have?
Sent from my One X using xda app-developers app
Click to expand...
Click to collapse
choeffe said:
Sorry for the late reply,I've had the darndest time getting into recovery since installing UrDroid 1.9!
I have HBOOT-1.14.002 and TWRP v. 2.3.1.0
Thanks for any help you could offer- I like UrDroid, but would like to try CM or the other ones!
Click to expand...
Click to collapse
Because of your hboot version you need to flash the boot.img seperately. It is possible that you are doing this but still encountering bootloops and the reason for that would be Hboot compatibility. I have noticed that some ROMs just do not play nice with certain hboots. The most compatible hboot that I've seen is 2.14 which seems to be the same accross all carrier phones.
That being said, my suggestion to you is to S-OFF if you aren't already, then, while keeping your bootloader unlocked, RUU up to 3.18 or 3.17 or whatever is the latest for your carrier which will update your hboot to 2.14 and then downgrade your touchscreen firmware which is super easy and there's a sticky for the process in the Original Android Development section.
After that, you should be able to run all roms without much issue AND you won't have to fastboot flash boot boot.img anymore.
That explains it- I literally have just been going into TWRP, installing the zip file, and then rebooting. I'm not even sure where I would find the boot.img, would that be inside the zip file?
So to S-OFF, should I follow the directions here: http://forum.xda-developers.com/showthread.php?t=2155071
I'm not sure how to RUU, any chance you or someone might have a link on instructions to do that? (I have an AT&T phone that I use on Straight Talk)
Thanks for your help, and if I'm asking for too much information, I'll keep doing some reasearch. I think the RUU is what kind of puzzles me (I'm clearly pretty green when it comes to rooting, I've only ever done it on this phone, not very successfully!
exad said:
Because of your hboot version you need to flash the boot.img seperately. It is possible that you are doing this but still encountering bootloops and the reason for that would be Hboot compatibility. I have noticed that some ROMs just do not play nice with certain hboots. The most compatible hboot that I've seen is 2.14 which seems to be the same accross all carrier phones.
That being said, my suggestion to you is to S-OFF if you aren't already, then, while keeping your bootloader unlocked, RUU up to 3.18 or 3.17 or whatever is the latest for your carrier which will update your hboot to 2.14 and then downgrade your touchscreen firmware which is super easy and there's a sticky for the process in the Original Android Development section.
After that, you should be able to run all roms without much issue AND you won't have to fastboot flash boot boot.img anymore.
Click to expand...
Click to collapse
choeffe said:
That explains it- I literally have just been going into TWRP, installing the zip file, and then rebooting. I'm not even sure where I would find the boot.img, would that be inside the zip file?
Click to expand...
Click to collapse
Yes it's in the zip. You extract it then fastboot flash boot boot.Img right before or after flashing the rom in recovery. Before flashing the rom and boot.img you should wipe cache, dalvik, system and factory reset. And only ever flash roms for the one xl or you risk bricking.
choeffe said:
So to S-OFF, should I follow the directions here: http://forum.xda-developers.com/showthread.php?t=2155071
Click to expand...
Click to collapse
Yes
choeffe said:
I'm not sure how to RUU, any chance you or someone might have a link on instructions to do that? (I have an AT&T phone that I use on Straight Talk)
Thanks for your help, and if I'm asking for too much information, I'll keep doing some reasearch. I think the RUU is what kind of puzzles me (I'm clearly pretty green when it comes to rooting, I've only ever done it on this phone, not very successfully!
Click to expand...
Click to collapse
To ruu, just download the ruu exe file and run it. But make sure you're s-off first or you'll brick.
Reading the stickies is suggested. You picked a ***** of a phone to be your first to root.
Sent from my One X using xda app-developers app
Thanks for your help thus far! I'm going to give it a try and see how it goes.
Yeah, I definitely wish I would have started with a Nexus or Sony device, but I changed from T-Mobile (worse decision of my life to go with them in the first place) to Straight Talk SIM with AT&T, and the HTC One X looked so pretty! Next phone is going to be a Nexus!
exad said:
Yes it's in the zip. You extract it then fastboot flash boot boot.Img right before or after flashing the rom in recovery. Before flashing the rom and boot.img you should wipe cache, dalvik, system and factory reset. And only ever flash roms for the one xl or you risk bricking.
Yes
To ruu, just download the ruu exe file and run it. But make sure you're s-off first or you'll brick.
Reading the stickies is suggested. You picked a ***** of a phone to be your first to root.
Sent from my One X using xda app-developers app
Click to expand...
Click to collapse
Hello.
I have an htc one xl (evita) which will not boot certain roms. I can boot some roms such as miui v5 and magiRom but I can not figure out why it will not boot roms such as CyanogenMod, ChameleonOS or TeamBaked BB9 as examples. These that will not boot will only boot loop and I'm going froot loop.
I am S-off, HBoot 1.09. Using TWRPv2.3.1.0.
I have tried TWRPv2.5, Hboot >1.09 and flashing boot.bin separately.
I have also tried some suggestions from these posts with no success so far ..
http://www.smartphonejam.com/2013/0...-on-HTC-Screen-Logo-Bootloop-after-Flash.html
http://forum.xda-developers.com/showthread.php?t=2159863
Any suggestions on how to boot other roms?
Thanks in advance for your help.
ps. I'm on mac - so if you have any suggestions and tools, please keep the mac in mind.
andason said:
Hello.
I have an htc one xl (evita) which will not boot certain roms. I can boot some roms such as miui v5 and magiRom but I can not figure out why it will not boot roms such as CyanogenMod, ChameleonOS or TeamBaked BB9 as examples. These that will not boot will only boot loop and I'm going froot loop.
I am S-off, HBoot 1.09. Using TWRPv2.3.1.0.
I have tried TWRPv2.5, Hboot >1.09 and flashing boot.bin separately.
I have also tried some suggestions from these posts with no success so far ..
http://www.smartphonejam.com/2013/0...-on-HTC-Screen-Logo-Bootloop-after-Flash.html
http://forum.xda-developers.com/showthread.php?t=2159863
Any suggestions on how to boot other roms?
Thanks in advance for your help.
ps. I'm on mac - so if you have any suggestions and tools, please keep the mac in mind.
Click to expand...
Click to collapse
3.18 ruu.
Sent from my One X using xda premium
jacobas92 said:
3.18 ruu.
Sent from my One X using xda premium
Click to expand...
Click to collapse
man i've looked at a lot of stuff regarding how to get to 3.18 but i keep finding a bunch of conflicting info that my brain is busted. If anyone can reply to some answers with my further info I would appreciate it...
My CID is 11111111
I'm S-off
hboot 1.09
What steps do I need to take to get to 3.18?
I can't seem to find a stock evita recovery image. My understanding is I need to relock boot loader, install stock recovery, upgrade to 3.18 and then restart the process of unlocking. Is this correct? Is the stock recovery located in an original at&t update?
andason said:
man i've looked at a lot of stuff regarding how to get to 3.18 but i keep finding a bunch of conflicting info that my brain is busted. If anyone can reply to some answers with my further info I would appreciate it...
My CID is 11111111
I'm S-off
hboot 1.09
What steps do I need to take to get to 3.18?
I can't seem to find a stock evita recovery image. My understanding is I need to relock boot loader, install stock recovery, upgrade to 3.18 and then restart the process of unlocking. Is this correct? Is the stock recovery located in an original at&t update?
Click to expand...
Click to collapse
As long as you're s-off, just go ahead and run this http://bugsylawson.com/index.php/fi...radio-024p320906-101303234-release-signedexe/ I know you wrote s-off, I'm just being double sure because if you're s-on it'll brick you. S-off you'll be fine. You won't have to relock or anything like that. With s-off you can just do whatever you want :good:
RollTribe said:
As long as you're s-off, just go ahead and run this http://bugsylawson.com/index.php/fi...radio-024p320906-101303234-release-signedexe/ I know you wrote s-off, I'm just being double sure because if you're s-on it'll brick you. S-off you'll be fine. You won't have to relock or anything like that. With s-off you can just do whatever you want :good:
Click to expand...
Click to collapse
Thanks. I'll find me a windows pc tomorrow and go for it. After I flash this in windows, do i then just flash any custom rom I want to go to which has the 3.4 kernel and will I be limited only to those now?
andason said:
Thanks. I'll find me a windows pc tomorrow and go for it. After I flash this in windows, do i then just flash any custom rom I want to go to which has the 3.4 kernel and will I be limited only to those now?
Click to expand...
Click to collapse
Yeah any 3.4 ROM, but you can also use non-3.4 if you so choose.
RollTribe said:
Yeah any 3.4 ROM, but you can also use non-3.4 if you so choose.
Click to expand...
Click to collapse
Thanks again. Much easier then what I thought I was understanding in my reads. I did see other people mention that as long as you were s off then everything else just about doesn't matter and then other contradicting that. Got to the point that I thought it made be easier to start all over in combination I was trying to install wine and it failed after about 45 minutes of downloading.
arrrggh.
andason said:
Thanks again. Much easier then what I thought I was understanding in my reads. I did see other people mention that as long as you were s off then everything else just about doesn't matter and then other contradicting that. Got to the point that I thought it made be easier to start all over in combination I was trying to install wine and it failed after about 45 minutes of downloading.
arrrggh.
Click to expand...
Click to collapse
Yeah, man, Wine doesn't work, I tried back when I used Mac for my Android needs. Everything is SO much easier with a windows PC
after flashing the 3.18 ruu, i can still flash any custom roms i want? aosp, sense base. what about ics version roms?
claudiuslu2011 said:
after flashing the 3.18 ruu, i can still flash any custom roms i want? aosp, sense base. what about ics version roms?
Click to expand...
Click to collapse
Yup all Roms
is there any advantage on the 3.18ruu?
Yeah, you need it to run AOSP 3.4 kernel roms
andason said:
Thanks again. Much easier then what I thought I was understanding in my reads. I did see other people mention that as long as you were s off then everything else just about doesn't matter and then other contradicting that. Got to the point that I thought it made be easier to start all over in combination I was trying to install wine and it failed after about 45 minutes of downloading.
arrrggh.
Click to expand...
Click to collapse
Thanks. Everything seems to work fine now.
A couple of things to note for others who make look at this thread - After flashing the rom in your link: http://bugsylawson.com/index.php/fi...radio-024p320906-101303234-release-signedexe/
1. Hboot will be at 2.14 - So if you wish, downgrade back to 1.09, otherwise you will need to flash the boot.img and then the rom when trying new roms.
2. The after market recovery (will now be oem recovery) will be gone so be sure to reinstall your preferred recovery (TWRP or CW)
3. The touchscreen may not respond in some roms, so you may have to downgrade your touchscreen panels firmware http://forum.xda-developers.com/showthread.php?t=2159863
exad said:
You only need to downgrade touchscreen firmware if:
You're on 2.14 hboot + You are flashing an AOSP ROM not yet on 3.4 Kernel.
Click to expand...
Click to collapse
Thanks again for the help.
andason said:
Thanks. Everything seems to work fine now.
A couple of things to note for others who make look at this thread - After flashing the rom in your link:
1. Hboot will be at 2.14 - So if you wish, downgrade back to 1.09, otherwise you will need to flash the boot.img and then the rom when trying new roms.
2. The after market recovery (will now be oem recovery) will be gone so be sure to reinstall your preferred recovery (TWRP or CW)
3. The touchscreen may not respond in some roms, so you may have to downgrade your touchscreen panels firmware http://forum.xda-developers.com/showthread.php?t=2159863
Thanks again for the help.
Click to expand...
Click to collapse
You actually don't need to downgrade your hboot, if you're s-off you don't need to manually flash boot.img no matter what your hboot version is.
Sent from my Evita
odd that rom would not boot with 2.14..but with 1.09 no problems?
andason said:
odd that rom would not boot with 2.14..but with 1.09 no problems?
Click to expand...
Click to collapse
There was probably some other factor causing the issue. I boot all roms with 2.14 no problem.
andason said:
odd that rom would not boot with 2.14..but with 1.09 no problems?
Click to expand...
Click to collapse
Which ROM? After s-off?
Sent from my Evita
timmaaa said:
You actually don't need to downgrade your hboot, if you're s-off you don't need to manually flash boot.img no matter what your hboot version is.
Sent from my Evita
Click to expand...
Click to collapse
do i need to downgrade my touch firmware?
claudiuslu2011 said:
do i need to downgrade my touch firmware?
Click to expand...
Click to collapse
You only need to downgrade touchscreen firmware if:
You're on 2.14 hboot + You are flashing an AOSP ROM not yet on 3.4 Kernel.
timmaaa said:
Which ROM? After s-off?
Sent from my Evita
Click to expand...
Click to collapse
It may be I am mistaken. I thought it was baked but i was also trying a rom I was trying to port. During the time i was flashing from 1.09 to 2.14 and also seen that baked required 2.14. So with all that going on i was just trying boot.img and then the rom to ensure no errors.
Hello to all!
I just followed this thread to root/unlock my AT&T One X. For some reason, I was unable to flash custom roms through TWRP and accidentally deleted the stock rom off of the phone. The phone is currently blank, and I am stuck in bootloader.
So, I tried following this , thinking I could RUU my way back to stock. Problem is, I am not on S-OFF. In order to make my phone S-OFF, I need to be in the OS, according to this.
Now I am stuck without software on the phone, unable to load any ROMS or to S-OFF my phone to RUU it.
Would anyone have an idea on how to proceed?
Can you please post your hboot details, we need as much info as possible to assist. You probably can flash custom ROMs, what happens when you try to install a ROM?
Sent from my Evita
re:
timmaaa said:
Can you please post your hboot details, we need as much info as possible to assist. You probably can flash custom ROMs, what happens when you try to install a ROM?
Sent from my Evita
Click to expand...
Click to collapse
Actually got RUU 3.18 to get the phone back on stock firmware. Still cannot install custom roms on TWRP/Clockwork. Currently back on TWRP.
HBOOT details as requested: Tampered,Unlocked, S-ON.
Any reason I shouldn't be able to install custom roms?
You didn't say what happens when you try to install custom ROMs. It's probably something as simple as flashing the boot.img manually which I can help you with.
Sent from my Evita
re:
timmaaa said:
You didn't say what happens when you try to install custom ROMs. It's probably something as simple as flashing the boot.img manually which I can help you with.
Sent from my Evita
Click to expand...
Click to collapse
When I try installing a custom rom, TWRP says flashing 1/1 for a brief moment, then goes to say 1/0, then a red FAILED! comes onto the screen. No matter what rom I try installing, however many times, I will get the same result.
Ok, which version of TWRP are you using? Also, where are you getting the ROMs?
Sent from my Evita
re:
timmaaa said:
Ok, which version of TWRP are you using? Also, where are you getting the ROMs?
Sent from my Evita
Click to expand...
Click to collapse
TWRP version 2.3.3.1
Getting ROMs from practically anywhere, but I've tried a few CM roms from their website.
The reason I got an older version of TWRP is because I thought it supported all roms. Is this true?
If you were able to successfully go back to stock using the 3.18 RUU and are still unlocked, you should try and s-off your device. make sure you're on TWRP 2.6. Most aosp roms with the 3.4 kernel require s-off. and older roms will also require downgraded touchpanel firmware since you're on the newest firmware released by HTC (correct me if I'm wrong here please). Make sure you're flashing roms for your specific device (evita) and the place to get those roms is in this sections subforums, either One X Android Development or One X Original Android Development.
That TWRP version is ok. They might be failing because they're not meant for our device though. Are you able to post the text log that displays when you're flashing the ROMs?
Also, don't download ROMs from anywhere except this forum, and links within this forum. The two development sections for our phone are here and here.
Sent from my Evita
re:
timmaaa said:
That TWRP version is ok. They might be failing because they're not meant for our device though. Are you able to post the text log that displays when you're flashing the ROMs?
Also, don't download ROMs from anywhere except this forum, and links within this forum. The two development sections for our phone are here and here.
Sent from my Evita
Click to expand...
Click to collapse
got CM10 working! So as long as the ROMs are made for Evita I don't need to be s-off?
Also, I'll be giving you a thanks!
No you don't need to be s-off, but because you're s-on you need to flash the boot.img manually. If you need to know how to do that, let me know. And yeah only get ROMs for Evita.
Sent from my Evita
Hey guys. Ive been debating for so long whether I should update to the new 2.16 HBOOT. I am currently running 2.15. If i update will I be able to run older roms like ViperOneS and so on. I know that I cant run Maximus on 2.15 so i was just wondering if the opposite is true. Thanks
nez762 said:
Hey guys. Ive been debating for so long whether I should update to the new 2.16 HBOOT. I am currently running 2.15. If i update will I be able to run older roms like ViperOneS and so on. I know that I cant run Maximus on 2.15 so i was just wondering if the opposite is true. Thanks
Click to expand...
Click to collapse
No, you will have to revert back to old firmware to run the ROMs that require 2.15 HBoot.
I have done it 2 different times, so it isn't hard.
My prefered way is to put stock recovery on and do a factory reset. Then I run a RUU. From there I flash a custom recovery and the ROM I want to try out.
tivofool said:
No, you will have to revert back to old firmware to run the ROMs that require 2.15 HBoot.
I have done it 2 different times, so it isn't hard.
My prefered way is to put stock recovery on and do a factory reset. Then I run a RUU. From there I flash a custom recovery and the ROM I want to try out.
Click to expand...
Click to collapse
Why would you have to put stock recovery to run an RUU? Arent you S-OFF?
nez762 said:
Why would you have to put stock recovery to run an RUU? Arent you S-OFF?
Click to expand...
Click to collapse
Yep, I haven't just run the ruu only to see if everything goes back to normal.
A factory reset from bootloader with stock recovery in place is overkill, but I have the files in a folder and just takes a minute extra to be safe.
Sent from my HTC One S using Tapatalk