Its jellybean 4.2 that was on my phone not ICS i made that mistake when you asked.
would this rom work?
[ROM][JB][Sense 5][15.03] Team Venom presents: ViperOne S 3.1.3 - Welcome to the future - xda-developers
-
After 15+ years, we've made a big change: Android Forums is now Early Bird Club. Learn more here.
Root I really need help figuring this out.. USB Problems
Its jellybean 4.2 that was on my phone not ICS i made that mistake when you asked.
would this rom work?
[ROM][JB][Sense 5][15.03] Team Venom presents: ViperOne S 3.1.3 - Welcome to the future - xda-developers
Team Venom presents: ViperOne S 3.1.3
Actually installed said everything was successful
When it reboot its stuck on the HTC screen with a warning in red
" This build is for Development purposes only
Don not distribute outside of HTC
with out HTC written permission.
Failure to comply may lead to legal problems "
How do I fix this??? There is no boot.img in this rom.
Actually installed said everything was successful
When it reboot its stuck on the HTC screen with a warning in red
" This build is for Development purposes only
Don not distribute outside of HTC
with out HTC written permission.
Failure to comply may lead to legal problems "
How do I fix this??? There is no boot.img in this rom.
Attached is the TWRP log for attempt ROM install to this
LiquidSmooth-Kitkat-v3.0-NIGHTLY 19/12/2013[UNOFFICIAL] - xda-developers
If I cant even get past the first step on your list than Im really screwed lol, the viper rom [ROM][JB][Sense 5][15.03] Team Venom presents: ViperOne S 3.1.3 - Welcome to the future - xda-developers
actually installs and says all is successful but when I reboot I get the locked up HTC screen with Red developer warning.
I'm gonna watch some of my TV shows I watch on Sunday and come back to this later. Please don't give up on this I really need my phone, no can call me or get a hold of me without my phone
HERES some from the log
E:Error in /sdcard/Liquid-Kitkat-v3.0-NIGHTLY-ville.zip
(Status 7)
Error flashing zip '/sdcard/Liquid-Kitkat-v3.0-NIGHTLY-ville.zip'
Updating partition details...
Hello?? I guess being sunday people are relaxing.. Im not going to quit this till its running on something.
I'm downloading now to see about the boot.img
what does that htc reboot screen mean?? Viper is the only rom that installed successfully.
I don't know enough about this device to tell you which kernel to flash and I hesitate to steer you in the wrong direction.
EarlyMon was pretty specific not to deviate from the numbered steps if you got stuck on one. If the rom he suggested didn't flash, then it'd probably be best to let him look at the log you provided.
That being said, the other ROM you installed looks like there are two kernels, one for hboot 2.15 and one for hboot 2.16.
I don't know which you have and I can't confidentially tell you to flash one of those.
Did that rom use the aroma installer? Just curious how it knows which kernel to choose out of the two.
EarlyMon was pretty specific not to deviate from the numbered steps if you got stuck on one. If the rom he suggested didn't flash, then it'd probably be best to let him look at the log you provided.
That being said, the other ROM you installed looks like there are two kernels, one for hboot 2.15 and one for hboot 2.16.
I don't know which you have and I can't confidentially tell you to flash one of those.
Did that rom use the aroma installer? Just curious how it knows which kernel to choose out of the two.
Your phone has security signature turned on in the bootloader.
For that reason, the boot.img won't always install for you during the normal rom install.
So you have to install it separately when that happens.
Therefore yes, you're seeing the screen that you see because the kernel didn't install (it's inside the boot.img). No kernel is the same as kernel not matching.
Brian, when you get Viper disassembled, are you going to zip the boot.img and post it here?
For that reason, the boot.img won't always install for you during the normal rom install.
So you have to install it separately when that happens.
Therefore yes, you're seeing the screen that you see because the kernel didn't install (it's inside the boot.img). No kernel is the same as kernel not matching.
Brian, when you get Viper disassembled, are you going to zip the boot.img and post it here?
It means that you are almost there.
The message is nonsense.
It means that you've unlocked your bootloader.
I get the same message on every reboot because my phone is from the same era.
And I unlocked properly through HTC.
IGNORE the message.
Yes I will post in a few. Does he need 2.15 or 2.16?
I can post both but would like to keep it as simple as possible.
There was no boot.img in the main rom folder there usually is. I've not seen that before. There were just the two I mentioned in a folder named kernel.
It does use the Aroma installer.
It seems to be looking at the bootloader version and deciding which way to go.
They also said this about installation instructions:
Emphasis theirs, not mine.
TWRP 2.4.3 is being used here.
So OP - when you boot into your bootloader or fastboot, what hboot version does it say you have?
I agree, let's just go with the right one.
Ordinarily I'd suggest updating TWRP properly so this would just install properly.
It's likely got the haus s-on kernel installer and that's that.
I was on the Viper4G team, fwiw, so I can guarantee that Viper roms tend to have requirements for a reason.
Worth trying just to get him running though.
Here's a link to both boot images:
https://copy.com/lVtO1HDW61vxAFR
https://copy.com/lVtO1HDW61vxAFR
Before charging off and downloading - what hboot do you have?
I haven't deviate from his instructions the 2 is to install the rom and I still couldn't get a rom to install until viper.
when I installed viper I did chose to install there kernel and it error out saying there is no kernel installed. There was only one kernel to chose from.
ver 2.15.0000
I want you to know I haven't steered away from your list, you said start at the top and I been working on getting a rom installed and finally viper work but here was no boot.img.
I'm still in windows, I have to reboot to get into Ubuntu it gives me an error running the virtual box.
There's no need to go in circles.
We know what you did from your first description.
Now we need to know what version of hboot you have.
Ok, hang on.
We're posting at the same time.
Just wait, and I'll wait.
We'll pick up from this point.
Good idea trying VirtualBox but we're not there yet.
ver 2.15.0000
so now hopefully, get the fastboot working in Ubuntu to take care of that hboot?
Yes, it's for Viper.
I removed the second file and left only the one for hboot 2.15. So I think you're good to download that now.
Here's the boot.img.zip you need with Viper.
I've renamed the img so that we don't have to modify my numbered instructions - with one difference.
You can download your boot.img.zip right here and not have to mail it to yourself.
Boot into Ubuntu on your live usb as you did before, and repeat all of the steps - including downloading fastboot again, etc etc etc - except use this boot.img.
In the long run that will be easier, we need to stay focused on the boot issue.
Here's your boot.img, our fingers are crossed.
I've renamed the img so that we don't have to modify my numbered instructions - with one difference.
You can download your boot.img.zip right here and not have to mail it to yourself.
Boot into Ubuntu on your live usb as you did before, and repeat all of the steps - including downloading fastboot again, etc etc etc - except use this boot.img.
In the long run that will be easier, we need to stay focused on the boot issue.
Here's your boot.img, our fingers are crossed.
And whether your phone boots or not, please stay in Ubuntu, tell us what's up.
If everything works, we're going to update your TWRP from Ubuntu and then you can do a clean re-install of Viper.
If everything works, we're going to update your TWRP from Ubuntu and then you can do a clean re-install of Viper.