Database Develop

Can't install a custom rom on Vivid

Hello everyone,
I've tried to look for anyone has experienced the same problem and found a solution and didn't find any post close to my case, but I am sure you guys knows what's wrong with it.
I have just rooted, unlocked, S Off and Hboot my Vivid, I have followed all the steps to do all of that but it's seems like there's something is wrong. I have tried to flash many different roms but I couldn't. Every time when I flash a rom and it says installing zip completed and reboot the phone it shows the rom's intro animation after showing HTC logo and then it restarts.
It happened with like 7 or 8 different roms, I even tried three different recoveries (TWRP 2.2, ClockWorkMod 5.0.2.7, and 5.0.2.0), and it's always the same problem!
I would really appreciate if somebody can tell me how to solve this problem.
Thanks

itodance said:
Hello everyone,
I've tried to look for anyone has experienced the same problem and found a solution and didn't find any post close to my case, but I am sure you guys knows what's wrong with it.
I have just rooted, unlocked, S Off and Hboot my Vivid, I have followed all the steps to do all of that but it's seems like there's something is wrong. I have tried to flash many different roms but I couldn't. Every time when I flash a rom and it says installing zip completed and reboot the phone it shows the rom's intro animation after showing HTC logo and then it restarts.
It happened with like 7 or 8 different roms, I even tried three different recoveries (TWRP 2.2, ClockWorkMod 5.0.2.7, and 5.0.2.0), and it's always the same problem!
I would really appreciate if somebody can tell me how to solve this problem.
Thanks
Click to expand...
Click to collapse
Are you flashing the kernel with fastboot over pc or no?
I had the same problems with mine after s-off, I'm using Pegasus_2.5.0a With WildChild's Recovery and all worked fine, anymore help PM me.

Thanks. And I did pm you.
Sent from my HTC PH39100 using xda app-developers app

I've used ClockWorkMod v5.5.0.4 (it's non-touch) and I have had no issues with it. If you'd like to try it, here is a mirror:
Filename: CWM-beta2.img (inside the below zip)
http://www.4shared.com/zip/tAZgjz25/CWM-beta2.html
Also - are you doing all the appropriate wipes before you flash the custom rom? (There are 4 wipes: Wipe Data, Wipe Cache, Wipe Dalvik in advanced, and wipe /system in Mounts&Storage).

Thanks
LaZiODROID said:
I've used ClockWorkMod v5.5.0.4 (it's non-touch) and I have had no issues with it. If you'd like to try it, here is a mirror:
Also - are you doing all the appropriate wipes before you flash the custom rom? (There are 4 wipes: Wipe Data, Wipe Cache, Wipe Dalvik in advanced, and wipe /system in Mounts&Storage).[/QUOTE]
thanks LaZiODROID , actually my problem is solved by Maqical as he figured out that I have to update my system to ICS first through the OTA or the RUU so I would be able to install a custom ICS roms. I was on GB stock Rom.
Thanks to Maqical and to you.
Click to expand...
Click to collapse

[Q] "Process System Not Responding" on all JB ROMs

I have a Sprint HTC One M7WLS, unlocked, S-ON, Clockwork Recovery.
The problems started with me flashing Revolution HD. I wasn't aware Revolution wasn't available for the WLS (Sprint) model, so I installed it as 'International + Non-listed Models'. The phone booted up into the ROM after installation, but with limited connectivity. The phone would reboot about a minute after loading. I wiped Cache, Dalvik, System, SDCard, Data (everything CWM allows me to format). Reinstalled a new ROM, still experienced reboot issue. The new ROM (TrickMod) gave me a 'Process System Not Responding' error, and then a reboot about thirty seconds after error. All ROMs are having wifi issues. In initial setup, if I'm able to get the keyboard to type in the WiFi Password, my device refuses to connect due to 'temporarily avoiding poor connection' error. I believe this may be the root of, or related to my problems. I get no cellular signal, and am unable to launch 'Activate Device' on any ROM. So far all the ROMs I've tried include:
Revolution HD, TrickMod, SuperNexus, and D3rp. Not all give the 'Process System Not Responding' error, but none of them can connect to WiFi, none can activate the device, and all of them reboot about a minute or two after boot.
Any ideas or solutions?
---
PS: Before flashing Revolution HD (my phone was still running on factory stock ROM), I used TWRP to backup all partitions. After Revolution HD, I attempted to restore all partitions, but the phone would boot up, error, and reboot as with all other ROMs that I tried after this. I installed CWM for TrickMod, SuperNexus, and D3rp so I could sideload ROMs (TWRP would hang on sideload, and I can't boot into the system to transfer ROMs to the sdcard).
---
Edit: I also wiped Dalvik and Cache and Fixed Permissions after ROM install. Still erroring out.

CM 10.1
We can add CM 10.1 to the list of ROMs that don't work.

Have you tried the Ruu?

oppressedtoaster said:
We can add CM 10.1 to the list of ROMs that don't work.
Click to expand...
Click to collapse
SOUNDS LIKE YOU need to flash a stock kernel.

RUU
gmentals said:
Have you tried the Ruu?
Click to expand...
Click to collapse
I downloaded the RUU. Using the All-in-One Toolkit informed me I needed to relock my device and restore stock recovery. I haven't done either of those things yet. I don't know how to reinstall stock recovery.
What exactly does the RUU do though?

Have you tried to flash a stock kernal as suggested above?
I haven't used the toolkit but I read it will relock the bootloader for you. The stock recovery will be flashed during the Ruu process.

Flashing Stock Kernel
Aldo101t said:
SOUNDS LIKE YOU need to flash a stock kernel.
Click to expand...
Click to collapse
Don't many of these ROMs flash their own kernels?
It's my understanding I'll need an unsecure boot.img to flash a stock kernel.
How do I unsecure my boot.img?
Where can I find stock kernel download?

Yes, the roms flash a kernal. Have you tried any of the sprint specific roms since this started happening? I would suggest you try one of viperboys roms.

Viper ROM
gmentals said:
Yes, the roms flash a kernal. Have you tried any of the sprint specific roms since this started happening? I would suggest you try one of viperboys roms.
Click to expand...
Click to collapse
All ROMs have been found on Sprint HTC One Development forums. Except Revolution HD, which I installed as 'International' since 'Sprint' wasn't an option. That's when everything went foul, including my Nandroid restores. This leads me to believe a botched install of Revolution is the cause of my problems.
I'm downloading Viper for Sprint One right now, give it a go.
Just tried Tranquility, still got reboot issues.
If Viper doesn't work, I'm going to try the RUU. RUU will flash stock kernel, correct?

RUU Worked!
oppressedtoaster said:
All ROMs have been found on Sprint HTC One Development forums. Except Revolution HD, which I installed as 'International' since 'Sprint' wasn't an option. That's when everything went foul, including my Nandroid restores. This leads me to believe a botched install of Revolution is the cause of my problems.
I'm downloading Viper for Sprint One right now, give it a go.
Just tried Tranquility, still got reboot issues.
If Viper doesn't work, I'm going to try the RUU. RUU will flash stock kernel, correct?
Click to expand...
Click to collapse
RUU worked! Lovely! So happy!
I'm going to install a ROM now and mess it all up again xD
Thanks everyone!

I'm glad you got it figured out.

[Q] ElementalX ROM - Rebooting during Installation

I'm trying to install the ElementalX Kernel onto my HTC One for overclocking. I've had it installed before but have since downloaded and installed an updated ROM which removed the kernel. When installing the Kernel using TWRP I'm able to go all the way though the setup of the Kernel but when I select to install it shows /wipecache as the first line then goes black before restarting back to android.
I've checked the MD5 on the phone itself and it matches up, I've performed a system reset, and a fastboot cache erase as well as selecting different frequencies in the kernal installer itself but still have the same issue. I've had a search of the forums and wasn't able to find any matching exactly so any advice is appreciated.
Some of the Versions:
Sense: 5.5
Android 4.4
ROM: Android Revolution HD One 40.3
TWRP v2.6.3.3
Trying to install
ElementalX-m7-10.5

Nevermind, reinstalled the ROM again, restarted, factory reset, and working.

kylel6 said:
Nevermind, reinstalled the ROM again, restarted, factory reset, and working.
Click to expand...
Click to collapse
Sometimes it happens when you instal bulletproof or elementalx kernels. Although you didn't have to factory reset, all you have to do in this situation is either dirty flash your rom again, or backup the system partition and then restore it, and then reboot, and just to be safe fastboot erase cache and then flash the kernel again and it should be good now.

[Q] ViperOne v5.8 Installation Help.

This is the second time happening. The first time I came from the previously supported Viper One Rom version from sprint, and when I flashed 5.8 I lose my recovery and just get stuck into bootloader. The second time I was coming from the recent Dirty Unicorns Rom, and the same thing happened. I'm currently using the latest Philz Recovery, and I did wipe my phone numerous times before flashing. Am I installing the wrong file? or Am I doing something else wrong? Also the only way it seems to come back from flashing the rom is using an RUU to get me back to stock. Flashing another ROM after ViperOne failing puts me in a bootloop.

zasuncion said:
This is the second time happening. The first time I came from the previously supported Viper One Rom version from sprint, and when I flashed 5.8 I lose my recovery and just get stuck into bootloader. The second time I was coming from the recent Dirty Unicorns Rom, and the same thing happened. I'm currently using the latest Philz Recovery, and I did wipe my phone numerous times before flashing. Am I installing the wrong file? or Am I doing something else wrong? Also the only way it seems to come back from flashing the rom is using an RUU to get me back to stock. Flashing another ROM after ViperOne failing puts me in a bootloop.
Click to expand...
Click to collapse
... try flashing ViperOne with TWRP 2.6.3.0 at least. i think this is going to solve your problem ...

That's really weird.
I've flashed stock to insertcoin to viper 5.7 to viper 5.8 then to bad seeds sense six. I now go back and fourth between viper and sense six no problems at all.
I've only used twrp though, used 2.6 all the way to the newest 2.7.0.4 I believe it is.
What I do when I switch is:
Nandroid*optional*
Flash superwipe for twrp2*so it wipes clean the Rom*
Restore a previous nandroid*viper, stock, etc*
Clear cache and davlik cache.
Reboot.
That's all I do.
I stopped using cwm a while ago with my DINC, my power button was shot*couldn't press it cause it was damaged* at that time twrp had a touch based recovery*2.3.x I believe*, so been using twrp since then.

New Recovery, can't install new rom's....

So I installed a "new" recovery, TWRP 2.6.3.3, and I'm running Viperone 7.0.1 and ElementalX-m7. I'm currently S-On and in the process of trying to go s-off. I created a backup of this before I went to install any new roms. The issue I'm having is whenever I try installing another ROM such as MaximusHD or ARHD, the aroma installer installs the rom but right when it goes back to TWRP, the screen goes black and I have to hold down the power and down button to get back into the recovery. If I try booting it up, the phone just stays on the HTC logo and never boots into the new rom. If you could help me in what I'm doing wrong that would be awesome.
The reason I'm trying to download new roms is I'm trying to go s-off on my phone and convert it to a google play edition.
Thanks.

Bump?
Sent from my HTC One using XDA Free mobile app

Try to isolate the problem. Like restore your backup and just install the rom. See if it works. Then add the kernel after and see if it still works. Your phone might just not like one or the other. Make sure the kernel matches the android version you're installing, too.
Also remember to wipe your dalvik and cache. Try that first, actuall... .