Database Info

[Q] Question on Flashing a Rom

Hello, recently i've just rooted my htc one s, s4. I stalled for a bit and had the 4.0.4 update already, so currently I have root access with the stock firmware. I'm looking through the rom list and the viper One s room caught my eye. So my question is, are there any prerequisite requirements before i flash this rom. Sorry for such a ridiculous question, but i havn't flashed a rom since the G1 and I remember having to flash certain kernels for certain roms. I still haven't messed with the kernel yet so that's stock too.
_________________________________________________________
My One S is s4 t-mobile, TWRP recovery, obtained root access with the All in One Toolkit v3.0 by hasoon2000. firmware is stock update 4.0.4 and everything else is just stock. so all i did was root

Just follow the instructions in the Viper Thread.
Since you have it rooted (and I assume a working recovery) you should already have all tools needed (fastboot etc).

On the Working Recovery, I would recommend installing TWRP. Best recovery atm for rom flashing. Get it thru the Goo Manager App on PlayStore. Just open Goo Manager then open Menu and tap on Install OpenScript Recovery.
Read OP pages carefully and scan the threads of the rom you want to flash. Depending on your hboot version, you may have to fastboot boot.img right after flashing rom. If at or above .13. Or, get Flash Image GUI from PlayStore and it will do it for you.
On CM roms there are some other quirks with radio etc, so some pre-study would be advised as well as nandroiding and backing up sdcard first. Put both backups on PC for extra safety.
Good Luck--

rugmankc said:
On the Working Recovery, I would recommend installing TWRP. Best recovery atm for rom flashing. Get it thru the Goo Manager App on PlayStore. Just open Goo Manager then open Menu and tap on Install OpenScript Recovery.
Read OP pages carefully and scan the threads of the rom you want to flash. Depending on your hboot version, you may have to fastboot boot.img right after flashing rom. If at or above .13. Or, get Flash Image GUI from PlayStore and it will do it for you.
On CM roms there are some other quirks with radio etc, so some pre-study would be advised as well as nandroiding and backing up sdcard first. Put both backups on PC for extra safety.
Good Luck--
Click to expand...
Click to collapse
Thanks! i went ahead and flashed viper rom and after reading a bit i noticed that i had hboot .14 so it broke my wifi . I'm still currently searching info and came across that i need linux to downgrade, which i don't have . do you know any other method? or roms beside trickdroid 7 that support the hboot version and allow wifi?

On .14 the items I mentioned will apply on all roms
Not sure on wifi, i use mostly cm roms atm

Im on Hboot .14, and wifi works fine for me on viperS

there is a wifi partition zip floating around for wifi issues. didn't pay much attn to it as i have no issues--maybe a search, or someone will post it

[Q] Phone screen unresponsive after flashing cm10

Hi guys. I have just recently bought this phone. This is my first HTC phone, ive always used samsung phones and wanted to try out the HTC. I managed to unlock the bootloader, root the phone and install twrp. My phone was bone stock so I downloaded the latest nightly for CM10 and gapps. Now for samsungs i didnt have to extract the boot.img and flash that via fastboot. so thinking the flashing process would be the same i flashed cm10, gapps and rebooted. And like clockwork the phone went into a boot loop. I found this little blurb in this thread http://forum.xda-developers.com/showthread.php?t=1957193
"5) Once your phone is in bootloader mode, type the following command fastboot flash boot boot.img ( If command prompt is closed then open command prompt in the folder where boot.img, adb, fastboot are present . For example: C:\android-sdk\platform-tools - Same folder used in step 3)
5) Then run the following command adb reboot recovery
6) Your phone is in TWRP recovery
7) Select mount from recovery ( See mount - image in the attachments for example)
8) Copy the ROM.zip which you downloaded earlier to the SD card ( For example cm-10-20121012-NIGHTLY-evita.zip) ( Not the extracted folder but the actual zip file which you downloaded)
4) Copy the gapps into sd card ( you need to download gapps if you using CM10 or ASOP roms )
5) Unmount, then select Wipe and select Factory reset ( it is recommended to do a factory reset before flashing the new ROM. ) (See wipe, wipe1 images below )
6) Select Install in recovery and flash the ROM.zip
7) You need flash gapps if you flashing CM10 or ASOP ROMS
so i re did the process. flashed boot img through fastboot, rebooted to recovery, flashed the rom that was already on the sd card, flashed the gapps package and rebooted phone. and i did do a factory reset when installing the rom. the phone rebooted, but this is where im stuck. the phone boots to the setup screen where you basically select the language. SCREEN is unresponsive, its not letting me click on start, its not registering my touch anywhere on the screen. I was thinking maybe it was the kernel so i made sure i was using the right kernel. i tried the whole process a few times but it didnt work. same problem. fone boots but doesnt register the touch. i even tried booting with flashing the gapps. so basically im stuck at the first screen. i had done a nandroid back up before and tried flashing that but that doesnt work either i guess because of the same reason.
Any help would be appreciated?
Thank you so much in advance

what hboot version do you have? There is an issue with the 2.14 hboot as HTC modified the firmware so the touchscreen drivers don't work for the older ICS or AOSP roms. If you have the 2.14 hboot, you'll need a JB sense ROM (like jokers or viperXL 3.1, or maybe Newts), check the forums themselves to see if they are compatible with the 2.14 hboot if you have it.\
If you don't have the newest hboot, maybe check the md5sum of the one you downloaded in case it is corrupted? If not try reflashing it, or flashing a different ROM and report back with results.
Good luck.

codeprimate said:
There is an issue with the 2.14 hboot
Click to expand...
Click to collapse
I hate that people are so hell bent on that this is a "2.14 hboot" issue.
2.14 hboot was just one of the many firmware updates pushed with 3.17 ROM's. I have not seen any knowledged person yet claim that the issue is actually in 2.14 hboot.
I believe if you revert your hboot with JET to 1.09 which you can do, the Touchscreen still does not work with incompatible kernels.
Which to me makes it pretty clear the issue is not in the hboot update at all but instead in one of the other updates.

twistedddx said:
I hate that people are so hell bent on that this is a "2.14 hboot" issue.
2.14 hboot was just one of the many firmware updates pushed with 3.17 ROM's. I have not seen any knowledged person yet claim that the issue is actually in 2.14 hboot.
I believe if you revert your hboot with JET to 1.09 which you can do, the Touchscreen still does not work with incompatible kernels.
Which to me makes it pretty clear the issue is not in the hboot update at all but instead in one of the other updates.
Click to expand...
Click to collapse
So in your opinion what is the solution i can try? Im not able to boot my phone so i cant really transfer any ROM zips to my phone. I have to use the bootloader or recovery to somehow get my phone back into workin order and then go from there. Thank you for your response

codeprimate said:
what hboot version do you have? There is an issue with the 2.14 hboot as HTC modified the firmware so the touchscreen drivers don't work for the older ICS or AOSP roms. If you have the 2.14 hboot, you'll need a JB sense ROM (like jokers or viperXL 3.1, or maybe Newts), check the forums themselves to see if they are compatible with the 2.14 hboot if you have it.\
If you don't have the newest hboot, maybe check the md5sum of the one you downloaded in case it is corrupted? If not try reflashing it, or flashing a different ROM and report back with results.
Good luck.
Click to expand...
Click to collapse
So i checked in the bootloader screen and i do have 2.14 hboot. so as the other person said i can downgrade my hboot using JET? and If im not mistaken you said that 2.14 may not be the latest hboot. If not where can i get the latest hboot. The other thing was since im not able to transfer any files to the phone.

Like twisted said you're going to have to flash a sense jb Rom right now go try viper.... Until the others update touch drivers to accommodate you people you have to use jb sense

marijuana king said:
Like twisted said you're going to have to flash a sense jb Rom right now go try viper.... Until the others update touch drivers to accommodate you people you have to use jb sense
Click to expand...
Click to collapse
ok so i downloaded jokers rom, and i was reading this link http://forum.xda-developers.com/showpost.php?p=32794132&postcount=7 to put the rom on my sd card. this link says they are using cwm recovery but i have read in many places that twrp should be used because it is officially supported for our devices. when i boot into recovery and try mount usb storage it doesnt show up on my computer as a flash drive. i have checked the drivers. im going to uninstall them and reinstall them, reboot my lappy and see if it recognizes the device. if you have any suggestions please throw them at me. at this time im looking for any straw that i can get to keep afloat.

anandsamuel said:
ok so i downloaded jokers rom, and i was reading this link http://forum.xda-developers.com/showpost.php?p=32794132&postcount=7 to put the rom on my sd card. this link says they are using cwm recovery but i have read in many places that twrp should be used because it is officially supported for our devices. when i boot into recovery and try mount usb storage it doesnt show up on my computer as a flash drive. i have checked the drivers. im going to uninstall them and reinstall them, reboot my lappy and see if it recognizes the device. if you have any suggestions please throw them at me. at this time im looking for any straw that i can get to keep afloat.
Click to expand...
Click to collapse
you should be able to flash that from TWRP instead of CWM without any dramas. if you can't see the device from your pc while it is booted into TWRP you can use "adb push C:\somepath\somefile /sdcard" to copy it onto your sdcard (you'll need the right version of the drivers and adb in your path). If you can't find the drivers or figure out anything let us know.
twistedddx said:
I hate that people are so hell bent on that this is a "2.14 hboot" issue.
2.14 hboot was just one of the many firmware updates pushed with 3.17 ROM's. I have not seen any knowledged person yet claim that the issue is actually in 2.14 hboot.
I believe if you revert your hboot with JET to 1.09 which you can do, the Touchscreen still does not work with incompatible kernels.
Which to me makes it pretty clear the issue is not in the hboot update at all but instead in one of the other updates.
Click to expand...
Click to collapse
You are right, it isn't the bootloader, it was the firmware upgrade pushed out alongside it, but it is a lot easier to check your hboot version from the bootloader than it is to check what software/firmware version you have, as the OP didn't list his software version, and had since blown it away with a new ROM, it seemed easier to check the firmware compatibility via the hboot version. I know strictly speaking the hboot isn't responsible for the touchscreen drivers, but they got the point quite quickly.

Update: so I was able to get my phone working I had to reinstall drivers on my computer restart the computer and then I was able to actually view my phone on my computer through TWRP and I transferred the ROM on to my phone and rebooted back into the bootloader flashed via boot image then went back to recovery and flash the ROM and everything is good to go now thank you all for your help this is an amazing phone
Sent from my HTC One XL using xda app-developers app

twistedddx said:
I hate that people are so hell bent on that this is a "2.14 hboot" issue.
2.14 hboot was just one of the many firmware updates pushed with 3.17 ROM's. I have not seen any knowledged person yet claim that the issue is actually in 2.14 hboot.
I believe if you revert your hboot with JET to 1.09 which you can do, the Touchscreen still does not work with incompatible kernels.
Which to me makes it pretty clear the issue is not in the hboot update at all but instead in one of the other updates.
Click to expand...
Click to collapse
Because it's the easiest way to identify that they are running the new firmware?

Yes. HTC went off and made some firmware updates to the touchscreen firmware.
We can't do anything about it until kernel source for the jellybean update is released.
Basically, if you took the new hboot EVER(since it updates the touchscreen firmware), that means you cant use AOSP Roms until we get source and can fix it in CM.
Aokp, pa, jellybam, kingkang, etc. All of those Roms use our kernel and device trees as a base. Once we get source and fix, they will update and everyone will be back in business.
The guys at TWRP were able to make recovery work because they just used the prebuilt stock kernel. On AOSP...we need source.
Sorry guys. Pester and scream at HTC to release JB source and that is the only way to help with this. Sorry to all of those that are affected....just know we are waiting impatiently as you are.
Sent from my Nexus 4 using xda app-developers app

h8rift said:
Yes. HTC went off and made some firmware updates to the touchscreen firmware.
We can't do anything about it until kernel source for the jellybean update is released.
Basically, if you took the new hboot EVER(since it updates the touchscreen firmware), that means you cant use AOSP Roms until we get source and can fix it in CM.
Aokp, pa, jellybam, kingkang, etc. All of those Roms use our kernel and device trees as a base. Once we get source and fix, they will update and everyone will be back in business.
The guys at TWRP were able to make recovery work because they just used the prebuilt stock kernel. On AOSP...we need source.
Sorry guys. Pester and scream at HTC to release JB source and that is the only way to help with this. Sorry to all of those that are affected....just know we are waiting impatiently as you are.
Sent from my Nexus 4 using xda app-developers app
Click to expand...
Click to collapse
lol, I've tried arguing with HTC's "support" for the source code, they are either extremely thick or deliberately obtuse. They kept telling me how to check if my carrier has released jellybean. I kept telling them that they are required under the GPL to release the source for the kernel along with any binaries.
I think the only way they'll release them in a timely fashion is if we get organised in a class action suit for violation of the GPL. It is for HTC's point blank refusal to meet it's legal requirement in a timely fashion that I refuse to ever buy another HTC device. I'll use this one for the term of my contract and then jump ship to a manufacturer that doesn't treat the open source community with contempt.

I don't mean to hijack this thread, but I'm facing a related issue.
I had rooted and unlocked my bootloader, hadn't yet installed any custom ROM. So today, without thinking, I install the OTA 4.1.1 update. Now of course I lost root, but even worse, when I boot in TWRP, my touchscreen is also unresponsive. I have the hboot 2.14.
I tried flashing TWRP again, but the same deal happens: the touchscreen won't register anything.
When you said that TWRP were able to make the recovery work, was this after the recent firmware update? Do I need a more recent version of TWRP (I'm using 2.3.3.1)?
I asked about this in the TWRP thread, but this seems closely related so I posted again here.
Edit- All is well, goo manager was installing 2.3.3.0 for some reason.

[SOLVED] Need To Fuly Revert To Stock

Hello, my HTC One S was fine on the stock things, but I decided to root it and add a custom ROM.
Bad idea.
I can't install Linux, so I can't downgrade the bootloader, and I can't find any ROMs where wifi will work without doing so. How can I revert to full stock, or is there a ROM where wifi works on hboot version 1.14?
Click to expand...
Click to collapse
I no longer need to downgrade to get the WiFi thanks to this great post here: WiFi Fix
I hope this helps people in the future.

All roms wifi works fine for me on hboot 1.14...

Vuciz said:
Hello, my HTC One S was fine on the stock things, but I decided to root it and add a custom ROM.
Bad idea.
I can't install Linux, so I can't downgrade the bootloader, and I can't find any ROMs where wifi will work without doing so. How can I revert to full stock, or is there a ROM where wifi works on hboot version 1.14?
Click to expand...
Click to collapse
i regret rooting my phone.. i cant sell it because they dont want a rooted phone

Re: Need To Fuly Revert To Stock
There's a guide somewhere in here how to revert to stock. I used it and worked perfectly. You should be able to find it using the search .
Basically the procedure goes like this:
1. Install zenROM (it's in the dev section).
2. Install stock recovery (also posted here in several threads)
3. Boot the phone into zenROM and look for OTA updates. ZenROM can find and install official updates.
4. Once updates are ready, you should be running stock JB rom.
5. Relock bootloader, or root or whatever. Now you are on the stock rom.
Of course this requires that there is a JB update available for your CID.
Sent from my HTC One S using xda app-developers app

zaak00 said:
There's a guide somewhere in here how to revert to stock. I used it and worked perfectly. You should be able to find it using the search .
Basically the procedure goes like this:
1. Install zenROM (it's in the dev section).
2. Install stock recovery (also posted here in several threads)
3. Boot the phone into zenROM and look for OTA updates. ZenROM can find and install official updates.
4. Once updates are ready, you should be running stock JB rom.
5. Relock bootloader, or root or whatever. Now you are on the stock rom.
Of course this requires that there is a JB update available for your CID.
Sent from my HTC One S using xda app-developers app
Click to expand...
Click to collapse
so let me post it the fourth time ..
http://forum.xda-developers.com/showpost.php?p=37942416&postcount=2

Usually you'll find answers to your problems in the according rom section as you're not the only one with it.
But as you are pretty new here:
1. You can use Linux livecd for downgrading. More here. The process isn't that easy so and you'll need to be patient and careful. (I did that couple of times on my device. The first time it was really worse also I was/am not new to Linux).
2. 1.14 means you have been on ICS only so far. So any ICS rom should work for you. If there is still trouble with wifi, search for answers in that rom section. I remember some guys editing a file for enabling/boosting wifi. As I'm not concerned by this, I have no links.
3. If you'd like to move to JB roms search for 'flashing wifi partitions' as long as you want to keep 1.14. If flashing the OTA update for JB your bootloader version will be 2.15 and the according wifi partitions will be working as well. For both, ICS and JB.
Substantially there will be no real differences for you between 1.14 and 2.15 as only with 1.06 and 1.09 you don't need to flash kernels via fastboot mode.
Hope you got the point as my answer is very short.

[Q] 1.85 rooted to scottsrom JB rooted

Ok, I know this is probably already all documented somewhere, but the problem is, there is also lots of out of date info, and I'm not sure how to tell which info is current, and which isn't. This is my first Android phone, so I'm not completely up to speed on the meanings of everything.
I have an AT&T (evita) HOX. Its on 1.8.5 stock, and is rooted. I also set supercid some time ago, in preparation for unlocking it. I didn't proceed with the unlock at that time because I wasn't yet comfortable that everything I wanted backed up was backed up, and everything said unlock would wipe all user data.
I believe I have backup under control now, and I'd like to get to where I can put the "Scottsroms" rooted JB on, and do whatever I need to ensure that I can keep root. I want to stay as close to stock as possible, but with root, and that seems to be the best path for that.
I've been doing a bit of reading (including stuff linked from the rollup thread) and I have some questions I haven't been able to answer.
- Do I need to unlock the BL in order to get S-off? Or, if I S-off, do I not need to unlock the bootloader?
- I see the note about htc blocking supercid unlocking and using all 2's instead - is this still valid?
- I had read CWM didn't support this phone, but now I see something that contradicts that.
Basically, while I understand that there are no guarantees, I'd like to at least avoid doing things that are KNOWN not to work.
FWIW, I am a long time linux user. I have the Android sdk installed with adb and fastboot programs... I'm very comfortable at the command line.
If anyone can suggest what the recommended procedure is, which steps I need, which I should avoid, which info is current, which is out of date, I'd be very thankful.
If more info from me is needed, just let me know...

Megadave123 said:
Ok, I know this is probably already all documented somewhere, but the problem is, there is also lots of out of date info, and I'm not sure how to tell which info is current, and which isn't. This is my first Android phone, so I'm not completely up to speed on the meanings of everything.
I have an AT&T (evita) HOX. Its on 1.8.5 stock, and is rooted. I also set supercid some time ago, in preparation for unlocking it. I didn't proceed with the unlock at that time because I wasn't yet comfortable that everything I wanted backed up was backed up, and everything said unlock would wipe all user data.
I believe I have backup under control now, and I'd like to get to where I can put the "Scottsroms" rooted JB on, and do whatever I need to ensure that I can keep root. I want to stay as close to stock as possible, but with root, and that seems to be the best path for that.
I've been doing a bit of reading (including stuff linked from the rollup thread) and I have some questions I haven't been able to answer.
- Do I need to unlock the BL in order to get S-off? Or, if I S-off, do I not need to unlock the bootloader?
- I see the note about htc blocking supercid unlocking and using all 2's instead - is this still valid?
- I had read CWM didn't support this phone, but now I see something that contradicts that.
Basically, while I understand that there are no guarantees, I'd like to at least avoid doing things that are KNOWN not to work.
FWIW, I am a long time linux user. I have the Android sdk installed with adb and fastboot programs... I'm very comfortable at the command line.
If anyone can suggest what the recommended procedure is, which steps I need, which I should avoid, which info is current, which is out of date, I'd be very thankful.
If more info from me is needed, just let me know...
Click to expand...
Click to collapse
Finish unlocking bootloader
Flash recovery twrp 2.3.3.1 or lower being higher versions have mount and wipe bugs.
Backup your current Rom via recovery.
Copy Rom of choice to sd card
Wipe everything except sd card. Wipe cache,dalvik, system, factory reset.
Flash Rom.
If you are on hboot 1.14 or higher you will need to extract boot.img from Rom.zip and flash via fastboot, flash boot boot.img
Good luck
Sent from my HTC One X using xda app-developers app

31ken31 said:
Finish unlocking bootloader
Flash recovery twrp 2.3.3.1 or lower being higher versions have mount and wipe bugs.
Backup your current Rom via recovery.
Copy Rom of choice to sd card
Wipe everything but sd card, cache,dalvik, system, factory reset.
Flash Rom. If you are on hboot 1.14 or higher you will need to extract boot.img from Rom.zip and flash via fastboot, flash boot boot.img
Good luck
Sent from my HTC One X using xda app-developers app
Click to expand...
Click to collapse
Regarding unlocking - can I do it with supercid set, or do I need to change to all 2's ?
Should I do s-off?
I'm on whatever versions of everything are stock for a device shipped with 1.85 - ok, the bootloader screen says hboot is 1.09.0000
I'll search around but are there docs on the specific steps for flashing roms?
BTW, thanks for the quick reply...

Hit install from recovery pick Rom and flash.. don't worry about s-off being on hboot 1.09 u can flash whatever from recovery. Htcdev has 1111111 blocked I think if it is use all 2's
Sent from my HTC One X using xda app-developers app

FWIW supercid seemed to work for unlock just fine...

31ken31 said:
Flash recovery twrp 2.3.3.1 or lower being higher versions have mount and wipe bugs.
Click to expand...
Click to collapse
Ok, looking for a bit of an expansion on this, and possibly some second opinions?
Looks like TWRP is up to 2.5.0.0 now, and the changelog shows a number of bugfixes since 2.3.x
Goomanager puts 2.5.0.0 on by default, I installed ROM Manager and it puts CWM..
The rollup page on the HOX says CWM officially supports it now..
The ROM I want says CWM "not supported" - I'm wondering if that is a holdover from when CWM didnt support HOX..

Megadave123 said:
Ok, looking for a bit of an expansion on this, and possibly some second opinions?
Looks like TWRP is up to 2.5.0.0 now, and the changelog shows a number of bugfixes since 2.3.x
Goomanager puts 2.5.0.0 on by default, I installed ROM Manager and it puts CWM..
The rollup page on the HOX says CWM officially supports it now..
The ROM I want says CWM "not supported" - I'm wondering if that is a holdover from when CWM didnt support HOX..
Click to expand...
Click to collapse
It's says bugs fixed but it's not fixed.. I don't recommend cwm for this device. Go to twrp website and download 2.3.3.1 and flash it
Sent from my HTC One X using xda app-developers app

[Q] Htc One X Unique problem

So as a n00b, I posted in the wrong forum earlier, lol
Anyways , long story short, htc one x evita, unlocked bootloader, tampered, rooted, will not flash past htc splash screen, when I try to restore, it does nothing, when going into folders there is NOTHING there, so random, I did clear my caches as instructed, maybe I am n00bish and deleted the wrong things, I can read the phone in adb, will go into teamwin screen,
REgardless, If I can get this fixed, I will not be messing with it again, lol(as all noobs say)
IS there anything I can do at this point before I throw my hands in the air and throw my phone at a wall?

Far from unique. It's possible that you've accidentally wiped the sd at some point, or did you possibly do a factory reset from the bootloader? Why haven't you just copied a ROM to the device to flash?
Sent from my Evita

timmaaa said:
Far from unique. It's possible that you've accidentally wiped the sd at some point, or did you possibly do a factory reset from the bootloader? Why haven't you just copied a ROM to the device to flash?
Sent from my Evita
Click to expand...
Click to collapse
HI, I may have wiped the sd, let's say sure to this..lol..
I have tried to copy a rom, I had Viper somewhat load, then it flashes back to htc splash, then to twrp,
Any insite to one that may possibly work?(the others will not load at all, they all fail install)

I need a bit more background on the device, please post your bootloader details (the first five lines). What TWRP version are you using? What had you done to the device directly before encountering this problem?
When you say you had Viper somewhat load what do you mean? Did it boot into the ROM at all? Or did it only boot as far as the Viper boot animation? Or did it only make it as far as the HTC splash screen?
I can't really say what's going to work until we figure out exactly what's wrong. Make sure you answer all the above questions with as much relevant detail as possible and we'll see if we can sort it out.
Sent from my Evita

timmaaa said:
I need a bit more background on the device, please post your bootloader details (the first five lines). What TWRP version are you using? What had you done to the device directly before encountering this problem?
When you say you had Viper somewhat load what do you mean? Did it boot into the ROM at all? Or did it only boot as far as the Viper boot animation? Or did it only make it as far as the HTC splash screen?
I can't really say what's going to work until we figure out exactly what's wrong. Make sure you answer all the above questions with as much relevant detail as possible and we'll see if we can sort it out.
Sent from my Evita
Click to expand...
Click to collapse
First off, thank you for your prompt replies
Venom loaded splash screen, then reboot to htc splash with the red developer on the bottom
twrp is the newest one
first 5 lines are you meaning?
*** TAMPERED ****
*** UNLOCKED ****
Evita put ship s-on rl
hboot-2.14.0000
radio-0.23a.32.09.29
??
Well I tried to load the stock RUU from rogers, (ota one)
then after rooting,unlocking bootloader, I tried to load a custom rom(slimkat IIRC)
then IT shut down, I left it for the night, and then nothing, so I tried to install slimkat again, nothing, so I tried venom, and I had the splash screen for the rom, now I am basically back at square one, nothing lol

Yes those are the bootloader details I needed. When you say the latest TWRP I'm assuming you mean 2.6.3.0? There are two versions of 2.6.3.0, the official version and the modified version.
Official version
Can flash any ROM except 4.4 ROMs. If you're using this one it is why SlimKat (plus any other 4.4 ROM) is failing to install.
Modified version
This is required to flash 4.4 ROMs. It does work on some pre 4.4 ROMs but it doesn't on others.
The most common cause for your current situation to happen is that you've forgotten to flash the boot.img with fastboot. Your phone is s-on, this means that the boot.img is unable to be flashed during the recovery install due to security restrictions on hboots equal to or greater than 1.14. So, make sure you're using the correct recovery for the ROM you want to flash (official 2.6.3.0 for Viper, modified 2.6.3.0 for 4.4 ROMs), and make sure you flash the boot.img with fastboot. I have detailed instructions on how to flash a boot.img in my How-To Guide For Beginners thread, link in my signature.
Do that and report back with how you go.
Sent from my Evita

timmaaa said:
Yes those are the bootloader details I needed. When you say the latest TWRP I'm assuming you mean 2.6.3.0? There are two versions of 2.6.3.0, the official version and the modified version.
Official version
Can flash any ROM except 4.4 ROMs. If you're using this one it is why SlimKat (plus any other 4.4 ROM) is failing to install.
Modified version
This is required to flash 4.4 ROMs. It does work on some pre 4.4 ROMs but it doesn't on others.
The most common cause for your current situation to happen is that you've forgotten to flash the boot.img with fastboot. Your phone is s-on, this means that the boot.img is unable to be flashed during the recovery install due to security restrictions on hboots equal to or greater than 1.14. So, make sure you're using the correct recovery for the ROM you want to flash (official 2.6.3.0 for Viper, modified 2.6.3.0 for 4.4 ROMs), and make sure you flash the boot.img with fastboot. I have detailed instructions on how to flash a boot.img in my How-To Guide For Beginners thread, link in my signature.
Do that and report back with how you go.
Sent from my Evita
Click to expand...
Click to collapse
Thank you so very much, once again with the quick replies and the "dumming" it down for me,
I will try in a little bit, to be honest, im not sure what twrp it is, I know its 2.3.6.0, it was the newest one,
in your instructions is there a way to boot just back to stock rom as well?(my pc is horrible, if I load more then one page it dies off lol) I will try this when I get home in a little bit herre.

I can almost positively say you're on the official version of TWRP, you'd need to go out of your way to find the modified one usually. With your phone in its current state you can't use an RUU to go back to stock. The latest Rogers RUU is older than your current firmware and you can't run an older RUU while s-on. If you made a TWRP backup of your stock ROM before wiping you could restore that backup though.
Your best and easiest option right now is to just flash a ROM. Once you've gotten a custom ROM booted up my guess is you won't want to go back to stock
Once you've gotten a ROM booted you can get s-off on your device which will make life a lot easier for you. It means no more flashing a boot.img, you'll be able to flash radios, you can run any Evita RUU (forwards or backwards, and from any carrier), and more benefits. But for now just concentrate on getting the ROM booting.
I'm assuming you have adb/fastboot installed on your PC already? If not you'll need to do that first, Google search "minimal adb and fastboot", the first result should take you to a thread that can get it done with very little effort.
Sent from my Evita

timmaaa said:
I can almost positively say you're on the official version of TWRP, you'd need to go out of your way to find the modified one usually. With your phone in its current state you can't use an RUU to go back to stock. The latest Rogers RUU is older than your current firmware and you can't run an older RUU while s-on. If you made a TWRP backup of your stock ROM before wiping you could restore that backup though.
Your best and easiest option right now is to just flash a ROM. Once you've gotten a custom ROM booted up my guess is you won't want to go back to stock
Once you've gotten a ROM booted you can get s-off on your device which will make life a lot easier for you. It means no more flashing a boot.img, you'll be able to flash radios, you can run any Evita RUU (forwards or backwards, and from any carrier), and more benefits. But for now just concentrate on getting the ROM booting.
I'm assuming you have adb/fastboot installed on your PC already? If not you'll need to do that first, Google search "minimal adb and fastboot", the first result should take you to a thread that can get it done with very little effort.
Sent from my Evita
Click to expand...
Click to collapse
Yes I have a basic Adb/fastboot setup already, is there a particular rom you recommend?(I will trust your best judgement here) I am home now, I will try and let you know
Thank you again

Asking for a ROM recommendation isn't allowed on XDA so I can't answer that question, here's why. To say one ROM is better is to infer that the others are inferior in some way. This is disrespectful to the devs who spend their spare time bringing us these awesome ROMs free of charge.
Each user has different tastes anyway. Some people like Sense ROMs, some like aosp ROMs. Personally I'm an aosp guy, aosp ROMs are generally a bit snappier, plus you can run the latest version of Android (Sense ROMs are limited to 4.2.2 for our device). I'd suggest having a look at the ROMs on offer, check out their features and pick one to flash. If you don't end up liking it you can always just flash another, and that's half the fun.
As a side note, getting s-off via Rumrunner s-off seems to work better on Sense ROMs. I know someone very recently got s-off while on the Kickdroid ROM so if you do want to get s-off I'd suggest flashing that ROM purely for the s-off process. You might like it and want to stay on it, if not just flash away.
Sent from my Evita

timmaaa said:
Asking for a ROM recommendation isn't allowed on XDA so I can't answer that question, here's why. To say one ROM is better is to infer that the others are inferior in some way. This is disrespectful to the devs who spend their spare time bringing us these awesome ROMs free of charge.
Each user has different tastes anyway. Some people like Sense ROMs, some like aosp ROMs. Personally I'm an aosp guy, aosp ROMs are generally a bit snappier, plus you can run the latest version of Android (Sense ROMs are limited to 4.2.2 for our device). I'd suggest having a look at the ROMs on offer, check out their features and pick one to flash. If you don't end up liking it you can always just flash another, and that's half the fun.
As a side note, getting s-off via Rumrunner s-off seems to work better on Sense ROMs. I know someone very recently got s-off while on the Kickdroid ROM so if you do want to get s-off I'd suggest flashing that ROM purely for the s-off process. You might like it and want to stay on it, if not just flash away.
Sent from my Evita
Click to expand...
Click to collapse
I understand and apologize, Never thought of it that way,
Anyways an update, I followed your tutorial, and I am not having much luck here, It still maintains to say NO OS installed (through twrp when rebooting after I do adb and such)
maybe I am missing something ?

Adb or fastboot?
Sent from my Evita

timmaaa said:
Adb or fastboot?
Sent from my Evita
Click to expand...
Click to collapse
Fastboot,
Small update I did manage to get a rootbox rom to load, but its not stable by anymeans...Ugh super frustrated with it

Are you wiping in TWRP before flashing? It's very important to wipe system/factory reset/cache/dalvik cache before installing a ROM. Just never do a factory reset in the bootloader, that'll corrupt your sd card.
Sent from my Evita

timmaaa said:
Are you wiping in TWRP before flashing? It's very important to wipe system/factory reset/cache/dalvik cache before installing a ROM. Just never do a factory reset in the bootloader, that'll corrupt your sd card.
Sent from my Evita
Click to expand...
Click to collapse
Yes to wiping before flashing in TWRP just those ones mentioned, (if you do sd you loose your flash right?), anyways the rom I flashed yesterday was super unstable, just trying a few diff. ones out and trying to find one that will continue to stay working lol!! Your tutorial in your signature is very helpful
thank you so much for all your help,and patience

Yeah you don't want to wipe sd card/internal storage or you'll lose all of your personal data like images, music, ROM zips, backups.
Sent from my Evita

timmaaa said:
Yeah you don't want to wipe sd card/internal storage or you'll lose all of your personal data like images, music, ROM zips, backups.
Sent from my Evita
Click to expand...
Click to collapse
Oh this is a clean phone, I already backed up on pc Before lol
Question though, I installed Viper again(just to try it) and it loads a menu showing ram, one of the memory sections shows -1? is this correct?

On a side note, I got Venom up and running and WOW!!!
once again, a super thank you for your patience and help all along Timmaaa,

I'm not sure what you're talking about, is that after booting into the ROM? Can you show me a screenshot?
Sent from my Evita

timmaaa said:
I'm not sure what you're talking about, is that after booting into the ROM? Can you show me a screenshot?
Sent from my Evita
Click to expand...
Click to collapse
it was while I was installing, everything seems fine, still no wifi(original issue)
im thinking the logic board may be buggered...sad day...lol
But, it is fast as heck now, running venom rom, I will try to get S-off and then maybe try to get it so I can load up the 4.4X roms
Thanks for all the help