Database Info

[Q] Switch from 4EXT to CWM ? / Flashing boot.img ? (CM10-alpha)

Hi XDA
My device before the procedure : HTC Desire S, unbranded, Bootloader locked,
HBoot 2.00.0002, S-ON, ICS stock rom via HTC RUU tool
I unlocked the bootloader via htcdev.com.
After hours of reading and testing "everything" I found here on xda (great stuff!!),
I finally managed to have a running CM10-alpha.
(http://forum.xda-developers.com/showthread.php?t=1776256 / Version 2012-09-17)
As I am new to this flashing stuff, I first tried to follow the flashing guide
on the CM-website. Was not workable because "Revolutionary" can not be used on hboot 2...
So I continued with flashing CWM-recovery and after a wipe (factory/reset/cache/dalvik),
I flashed CM10.zip and gapps.zip.
It went through without any errors, unfortunately, the device did not boot afterwards.
I found this guide :
http://forum.xda-developers.com/showthread.php?t=1525100 (CustomROM with 4EXT-recovery)
It indicates flashing "boot.img" (from the CM10 zip-file) as a last step.
Probably the most important step for this HTC device ?!
The Desire S booted CM10 without any further problems and is running since.
(I did not flash GApps.zip, just downloaded Maps and Youtube.)
I have 3 questions :
1. Is it possible to update to a newer version of 4EXT-recovery without losing
the CM10-installation ?
(e.g. 4EXT-Touch : http://forum.xda-developers.com/showthread.php?t=1377745)
2. Is it possible to switch from 4EXT to CWM-recovery without losing
the CM10-installation ? I would like to have CWM because I could then use the ROMManager App.
(e.g. http://forum.xda-developers.com/showthread.php?t=1484753)
3. If I would stick with the current 4EXT-recovery,
do I always have to flash "boot.img" as the last step before booting up the device ?
(e.g. after the next CM10-alpha release)
"fastboot flash boot boot.img"
Click to expand...
Click to collapse
Thanks so much !
CM10 is great, so much faster than HTC-stock rom ICS (with Sense 3.6) !!
CU

1) yes
2)yep
3)si
Edit: you only have to flash the boot.img when the kernel changes from cm10 to fallout yes.
Updating cm10 no, if the dev didn't change the kernel.
After a full wipe (in 4ext format everything exept SD-card) you also have to use fastboot. Because that wipes the boot.img

Thanks !
Just to recap, I can flash CWM-recovery and then do a normal bootup (with my existing CM10 installation). No further actions required !?
As the kernel will probably remain at v2.xx with the next CM10-alpha-release of nik111, I only wipe reset/factory/cache/dalvik
and then flash the new cm10.zip.
I do not think that I will format anything. But if I would, I would have to replace boot.img again.

FrolicFrog said:
Thanks !
Just to recap, I can flash CWM-recovery and then do a normal bootup (with my existing CM10 installation). No further actions required !?
As the kernel will probably remain at v2.xx with the next CM10-alpha-release of nik111, I only wipe reset/factory/cache/dalvik
and then flash the new cm10.zip.
I do not think that I will format anything. But if I would, I would have to replace boot.img again.
Click to expand...
Click to collapse
Changing recovery will not touch anything else on your device. But there were some issues reported with CWM on some ROMs.
I think one of them is a lack of /system/lib partition support, which is important if you go from a ROM that has such to a ROM without one (it will end with two conflicting /system/lib directories and the device will not boot.
Also I am not sure that CWM wipes the .android-secure directory on the SDcard which can cause issues if going from AOSP to Sense ROM

For some reason I never changed from cwm to 4ext whilst I owned a ds but I can confirm it does wipe .android-secure on the sd card

pughie said:
For some reason I never changed from cwm to 4ext whilst I owned a ds but I can confirm it does wipe .android-secure on the sd card
Click to expand...
Click to collapse
I have used it about an year ago so it is definitely improved. But there was an user with Bluetooth issues after flashing my kernel and changing the recovery solved it. Also 4EXT has a lot of minor but very useful settings over CWM. Anyway the OP can try both and stick with the one he likes more
Btw Rom Manager can be used to check for updates and ROM downloads with 4EXT if you choose "manual flash override" from the menu
Sent from my HTC Desire S

amidabuddha said:
Btw Rom Manager can be used to check for updates and ROM downloads with 4EXT if you choose "manual flash override" from the menu
Click to expand...
Click to collapse
Ah, will check on this one. Thanks !

FrolicFrog said:
As the kernel will probably remain at v2.xx with the next CM10-alpha-release of nik111, I only wipe reset/factory/cache/dalvik
and then flash the new cm10.zip.
I do not think that I will format anything. But if I would, I would have to replace boot.img again.
Click to expand...
Click to collapse
Nk111 uploaded a screenshot today, that shows kernel v3.0.16
When upgrading cm10 wiping cache & dalvic cache should be enough. If you get any problems, apps fc or something like that, do a full wipe(I use format all partitions except SD card in 4ext, after that don't forget to flash the kernel with fastboot).
Btw wipe and format is the same.

Bug in CM10 Alpha by nk11
Hello XDA,
Sorry if this question is in the wrong thread.
It is regarding the cm10 alpha port by nk111.
I got it working, save one major bug, the speaker does not produce any sound output whatsoever:
This applies to ringtones, alarm tones and music.
The sound is perfectly audible through a pair of earphones.
I followed the steps in the official thread to delete the file /system/lib/hw/audio_policy.msm7x30.so and reboot
but this only aggravates the issue by disabling all audio outputs!!!
I am running clockwork mod v5 with HTC bootlocker unlocked, S-ON.
Any help would be greatly appreciated.

c.m.b said:
Nk111 uploaded a screenshot today, that shows kernel v3.0.16
When upgrading cm10 wiping cache & dalvic cache should be enough. If you get any problems, apps fc or something like that, do a full wipe(I use format all partitions except SD card in 4ext, after that don't forget to flash the kernel with fastboot).
Btw wipe and format is the same.
Click to expand...
Click to collapse
I saw the screenshot of kernel version 3, too. And was quite excited
Thanks for the hint with wiping only cache&dalvik.

[Q] Updating ROM via GooManager

Hi All,
I have posted this on the GooManager thread but there hasn't been much activity there recently so asking here as well. Noob question on GooManager...I have the AOKP rom installed on my Sensation and GooManager notifies me of updates to my ROM every now and then. I just want to know if updating my ROM build with GooManager will reset all my custom ROM settings and preferences or will they all be preserved? I'd like to keep my ROM up to date but if it means spending all the time again to setup my preferences and icons/widgets/home screens etc. then I'd rather stick with what I have.
TIA!

I'd recommend to use GooManager only to download the newest ROM and flash it from recovery.
I asume you're using AOKP Swagger from frankenstine, the same I use.
I just download the update from GooManager, boot to recovery, flash ROM, gapps and 4.2 stuff and are ready to go.
All my settings are their after updating - only AdAway needs a reconfiguration and a reboot (and I need to set my alarm clock since I'm overwriting that). Basically you keep all your settings except those you made to the kernel.
Regards

lolmachine4 said:
I'd recommend to use GooManager only to download the newest ROM and flash it from recovery.
I asume you're using AOKP Swagger from frankenstine, the same I use.
I just download the update from GooManager, boot to recovery, flash ROM, gapps and 4.2 stuff and are ready to go.
All my settings are their after updating - only AdAway needs a reconfiguration and a reboot (and I need to set my alarm clock since I'm overwriting that). Basically you keep all your settings except those you made to the kernel.
Regards
Click to expand...
Click to collapse
Oh perfect, yes indeed I am using that exact ROM.
OK so when I boot to recovery, I shouldn't do any wiping? Just simply flash the new file? Will the updated gapps package be in the download I get from GooManager?

freddysensation said:
Oh perfect, yes indeed I am using that exact ROM.
OK so when I boot to recovery, I shouldn't do any wiping? Just simply flash the new file? Will the updated gapps package be in the download I get from GooManager?
Click to expand...
Click to collapse
I only wipe dalvik & cache after each update.
I can't say something about what GooManager downloads as "gapps", I use some I downloaded some weeks ago + some old version of 4.2 stuff. I might need to update my flash-setup too

lolmachine4 said:
I only wipe dalvik & cache after each update.
I can't say something about what GooManager downloads as "gapps", I use some I downloaded some weeks ago + some old version of 4.2 stuff. I might need to update my flash-setup too
Click to expand...
Click to collapse
Thanks lolmachine, for the benefit of anyone who might have the same question as me the following worked:
- Downloaded latest build of my AOKP Rom via GooManager
- Downloaded latest gapps package for my ROM via GooManager
- Boot to Recovery
- Flash new ROM file and then gapps package
- Restart.
My only question is, I didn't wipe davlik and cache so should I, and what difference does it make if I don't?

I used Goo the other day to flash, ummm, bugger, can't remember if it was an update or a new rom.
Oh now I remember, the latest one was an update to Bruce's Rom. I do believe when I tapped flash rom it booted to recovery (the one it installs) and I may have had to select "Install" from there, don't think so though. Either way, I used Goo to handle the install.
I didn't do a wipe. From what I've picked up, wiping is a good way to cover your butt. So if you're having issues and didn't wipe, you go back and do it all again with a wipe. Doing the wipe to start with means you can eliminate those types of issues from the start.
Someone can correct me if I'm wrong (which I probably am )

Hi there, I also received an update to my ROM via Goo Manager. It is CyanogenMod 10.1 by Albinoman887 for my HTC Sensation XE. I am using the EXT4 bootloader. I just installed it a few nights ago so I am completely new to rooting. My question is that there is no option to wipe dalvik cach. EXT4 just says wipe cache, wipe data and wipe system. Does wipe cache wipe dalvik cache as well. Also do I need to re-flash gapps as well after updating and will this wipe my gmail accounts etc?
Thanks,
Adam

thisisadamh said:
Hi there, I also received an update to my ROM via Goo Manager. It is CyanogenMod 10.1 by Albinoman887 for my HTC Sensation XE. I am using the EXT4 bootloader. I just installed it a few nights ago so I am completely new to rooting. My question is that there is no option to wipe dalvik cach. EXT4 just says wipe cache, wipe data and wipe system. Does wipe cache wipe dalvik cache as well. Also do I need to re-flash gapps as well after updating and will this wipe my gmail accounts etc?
Thanks,
Adam
Click to expand...
Click to collapse
You want to select "wipe dalvik+cache" option when you flash an update.
There's no need to flash gapps after a ROM update.
Sent from my Ouya

AndroidSupporter318 said:
You want to select "wipe dalvik+cache" option when you flash an update.
There's no need to flash gapps after a ROM update.
Sent from my Ouya
Click to expand...
Click to collapse
Thanks very much, downloading it now.

Help
im using albinoman's jelly bean rom
excuse me for noob doubts but
1) goo manager shows i have an update, so ive downloaded it. its a zip just like the rom n not just a small update. i have downloaded it now what should i do?
2) if i have to go to the recovery and flash the zip then i have to wipe only the cache right? Im using 4ext recovery.
3) will all my apps get uninstalled? what about the app data?
4) what about gapps? i have a gapps zip file, will i have to flash it again after the update?
Please reply thanks

I finally rooted phone after silly VMUNE7 thing on Verizon but after I get the install openrecoverscript and hit reboot recovery it does not go to teamwiz bootload instead I get something with a green driod on the bottom saying downloading but above it saying in red can't download Odin mode?? Please help I want to run cleanrom for better battery and less bloatware and keep my touchwiz. :crying:

all3rd said:
I finally rooted phone after silly VMUNE7 thing on Verizon but after I get the install openrecoverscript and hit reboot recovery it does not go to teamwiz bootload instead I get something with a green driod on the bottom saying downloading but above it saying in red can't download Odin mode?? Please help I want to run cleanrom for better battery and less bloatware and keep my touchwiz. :crying:
Click to expand...
Click to collapse
sorry man but i think you are talking for a samsung device am i right?
if yes then this is only for sensation/XE/4G devices

yasho170 said:
im using albinoman's jelly bean rom
excuse me for noob doubts but
1) goo manager shows i have an update, so ive downloaded it. its a zip just like the rom n not just a small update. i have downloaded it now what should i do?
2) if i have to go to the recovery and flash the zip then i have to wipe only the cache right? Im using 4ext recovery.
3) will all my apps get uninstalled? what about the app data?
4) what about gapps? i have a gapps zip file, will i have to flash it again after the update?
Please reply thanks
Click to expand...
Click to collapse
Simple.
Go to recovery.
For s-on you must enable smartflash.
Do a nandroid backup.
Dirty flash the update (meaning flash over the previous rom without wiping).
Dirty flash gapps (signed only).
Wipe cache + dalvik.
Reboot.
If it can't boot/run properly then you can just restore the backup or do a clean flash.

First off I'm not experienced in any way, got my Sensation unlocked, rootet and installed Sultanxda's 4.4.2 ROM for sensation. I'm on S-On, too, if anyone wonders.
Updating didnt affect my apps as far as I can tell. Everything seems to be the way as before and everything seems to be working.
What I did was download the ROM manually since the download with goomanager didn't work. I downloaded gapps as backup because I didnt have the zip on my SD, just in case anything would go wrong.
You only need to boot into recovery, with S-On make sure smartflashing or something like that is on, select the zip, flash it and then select wipe cache +dalvik.
It's pretty much what AndroidSupporter318 wrote, just wanted to give feedback and say what I did in detail in case anyone was still wondering.
LxMaD

I guaranted 4EXT Recovery for this type of problem. U don't need to boot into recovery and work with 4ext is very simple.

Trying to get back to CM 10.0 from 10.1

I know the CM 10.1 nightly was experimental.
I flashed it, and it worked decently well enough.
What I failed to realize was that 10.1 flashes a new kernel on the phone, one that is incompatible with CM 10.0. I'm guessing the 4.2 base requires a new kernel.
So Fine, I've tried flashing the stock kernel on my phone, and then installing CM10, but no fish.
Any attempts I've made to change my kernel and then install CM 10 have resulted in my phone being stuck on the CM boot screen (the cyan circle animation)
Flashing CM10.1 nightly from twrp lets my phone boot up, because (i suppose) that rom installation just installs the compatible kernel again.
Can someone please help me figure out what I'm doing wrong with my kernel flashing?

taurius1 said:
I know the CM 10.1 nightly was experimental.
I flashed it, and it worked decently well enough.
What I failed to realize was that 10.1 flashes a new kernel on the phone, one that is incompatible with CM 10.0. I'm guessing the 4.2 base requires a new kernel.
So Fine, I've tried flashing the stock kernel on my phone, and then installing CM10, but no fish.
Any attempts I've made to change my kernel and then install CM 10 have resulted in my phone being stuck on the CM boot screen (the cyan circle animation)
Flashing CM10.1 nightly from twrp ets my phone boot up, because (i suppose) that rom installation just installs the compatible kernel again.
Can someone please help me figure out what I'm doing wrong with my kernel flashing?
Click to expand...
Click to collapse
What hboot r u on? You're full wiping right? And if you're on hboot 1.14 grab the boot.img our of the Rom zip you desire to flash and Fastboot flash it

a box of kittens said:
What hboot r u on? You're full wiping right? And if you're on hboot 1.14 grab the boot.img our of the Rom zip you desire to flash and Fastboot flash it
Click to expand...
Click to collapse
I'm on the 1.09 hboot. I haven't messed with my hboot ever. Should I be upgrading? I'll have to look it up.
I did try what you suggested.
I extracted the boot.img from CM10 stable for evita, flashed it via fastboot.
Then i rebooted into recovery, wiped my system, my cache, my dalvik cache, and did a factory reset.
Then I flashed CM 10.
After all this, still stuck on the cm boot animation. :3 I give it about 10 minutes before I decide its stuck. That is enough time, I think.

taurius1 said:
I'm on the 1.09 hboot. I haven't messed with my hboot ever. Should I be upgrading? I'll have to look it up.
I did try what you suggested.
I extracted the boot.img from CM10 stable for evita, flashed it via fastboot.
Then i rebooted into recovery, wiped my system, my cache, my dalvik cache, and did a factory reset.
Then I flashed CM 10.
After all this, still stuck on the cm boot animation. :3 I give it about 10 minutes before I decide its stuck. That is enough time, I think.
Click to expand...
Click to collapse
Ok no you want to stay on hboot 1.09 and redownload the latest cm10..and do these exact instructions
Wipe factory reset
System
Caches
Install Rom
Install gapps
I'm thinking you just had a bad download

a box of kittens said:
Ok no you want to stay on hboot 1.09 and redownload the latest cm10..and do these exact instructions
Wipe factory reset
System
Caches
Install Rom
Install gapps
I'm thinking you just had a bad download
Click to expand...
Click to collapse
I've done that. But just to be sure, I'm gonna try a fresh download once more. ^_^ Brb 10 minutes.

Curious what happened, as I think I may be having this same issue.

a box of kittens said:
Ok no you want to stay on hboot 1.09 and redownload the latest cm10..and do these exact instructions
Wipe factory reset
System
Caches
Install Rom
Install gapps
I'm thinking you just had a bad download
Click to expand...
Click to collapse
OOh that worked. Thanks a ton! ^_^
Probably was a bad download all three times I tried to download it before. :/ (I should probably buy a lottery ticket now :/ )
Now, Let me try installing my rooted stock rom. :3

Almost Same Problem
I have HTC One XL
-rooted
-unlocked
-bootloader unlocked
-hboot 1.14
-twrp recovery
I was also running the 10.1 expiremental (the first one). It was very buggy, so I tried out the newer experimental to see if the problems were fixed. The newer one was worse, so I decided to switch back to 10.0 nightly. I used fastboot to change the kernel to the one extracted from the 10.0 rom zip. I went to recovery and installed the 10.0 rom, but I DID NOT WIPE ANYTHING THE FIRST TIME. Either it slipped my mind, or I was thinking it wasn't necessary because I was still using a CM rom. The device would not boot, but instead of hanging on the cm animation screen, I'm stuck on the HTC logo screen. I went back to fastboot and did the kernel again and the phone automatically rebooted up correctly, however after a reboot i'm still stuck at the htc logo screen. It reminds me of tethered jailbreaks on iOS, lol. I may have to reflash the kernel every time I reboot. I tried stable, nightly, 10.1 nightly. no dice. any ideas?

lucasjohnsond said:
I have HTC One XL
-rooted
-unlocked
-bootloader unlocked
-hboot 1.14
-twrp recovery
I was also running the 10.1 expiremental (the first one). It was very buggy, so I tried out the newer experimental to see if the problems were fixed. The newer one was worse, so I decided to switch back to 10.0 nightly. I used fastboot to change the kernel to the one extracted from the 10.0 rom zip. I went to recovery and installed the 10.0 rom, but I DID NOT WIPE ANYTHING THE FIRST TIME. Either it slipped my mind, or I was thinking it wasn't necessary because I was still using a CM rom. The device would not boot, but instead of hanging on the cm animation screen, I'm stuck on the HTC logo screen. I went back to fastboot and did the kernel again and the phone automatically rebooted up correctly, however after a reboot i'm still stuck at the htc logo screen. It reminds me of tethered jailbreaks on iOS, lol. I may have to reflash the kernel every time I reboot. I tried stable, nightly, 10.1 nightly. no dice. any ideas?
Click to expand...
Click to collapse
Sounds like the best solution would be what I did, thanks to box of kittens.
Full wipe. (factory reset, system, cache)
Flash a download of CM to make sure you don't have a damaged copy.

taurius1 said:
Sounds like the best solution would be what I did, thanks to box of kittens.
Full wipe. (factory reset, system, cache)
Flash a download of CM to make sure you don't have a damaged copy.
Click to expand...
Click to collapse
Actually, I just remembered. If you're on the new hboot, you should be flashing the boot img through fastboot, and then installing the zip. Since you've been doing all that anyway, perhaps its time to just wipe everything and start over, step by step.
> download cm 10.0
> check md5 to make sure it's proper
> extract boot.img and flash it via fastboot
> reboot into recovery.
> wipe system, cache, dalvik cache, and factory reset
> transfer the rom and flash it via recovery
:/ I'm no expert here, but that's what I'd be doing now.

[Q] Questions regarding liquidsmooth

Hi all,
Over the past few days I have been using this splendid ROM, however something went wrong during the flashing of the ROM or I missed something, because all of my apps keep crashing and my stock browser app crashes everytime I use it. And I also get random reboots. I think it's the boot.img, but i'm tired of trying
I installed this rom in the Following order:
1. Wipe cache
2. Factory reset
3. Wipe dalvik cache
4. Flash the ROM
5. Rebooted into fastboot
6. Fasboot flash boot boot.img
And I also tried it in this order:
1. Fasboot flash boot boot.img
2. Wipe cache
3. Factory reset
4. Wipe dalvik cache
5. Flash the ROM
6. Reboot
What am I doing wrong here?
----------------------------------------------------------------
Adding some extra info just incase:
I came from stock sense 4.1+ android 4.1.1
Current device info:
UNLOCKED
S-ON
Hboot version 2.15.0000
Radio 1.11.50.05.28
I also tried redownloading the zip, but got the same result
At last i'm wondering if there are any specific kernels available for this ROM, and which 1 you guys recommend.
Thanks in advance!

In TWRP you want to factory reset then wipe system and then flash the rom and see if that works for you.

Darknites said:
In TWRP you want to factory reset then wipe system and then flash the rom and see if that works for you.
Click to expand...
Click to collapse
Ok ty, will try and see if that will sort it all out

Sadly, same story... :crying::crying::crying::crying: Is installation of the rom supposed to happen in 30 seconds?

Boyyoka said:
Sadly, same story... :crying::crying::crying::crying: Is installation of the rom supposed to happen in 30 seconds?
Click to expand...
Click to collapse
Em not sure but sounds a bit to quick. Get yourself 2.3.3.0 of TWRP and try with that and if its still being quick then do the wipes like I said but reboot but back into the recovery then flash the rom.

nevermind cheered too early... Seriously something is corrupting my phone

Maybe you have a bad download, try redownloading and flash.

[Q] ViperOneS 2.2.0 OTA

Hey guys, since my post count is too low to post my problems with this OTA update in the development section of this rom, ill do it here. Sorry for that.
I think im having no problems with flashing the 2.1. ROM yet but i have my concerns if i did that right.
First problem with flashing it, is the question if im having a custom kernel. I flashed ViperOneS a several times but made a fullwipe before.
So am i having a custom kernel or not?
Next issue is that im only able to flash this ROM with CWM. TWRP 2.5 doesnt work and even 2.3.3.0, which should work, but does not for me...
Well with CWM i ll do it that way:
1. Doing Fullwipe in CWM (Factory reset, Wipe Cache, Wipe Dalvik and System).
2. Flashing the ROM and choosing HTC Theme > Custom Kernel? > not sure sometimes "yes" sometimes "no".
3. Flash finished? > asks me if i want to reboot (into system) or save the logs. Since the instruction tells me to flash the boot.img first before rebooting...
4. ... im going into bootloader via adb which works
5. flash the boot.img
6. fastboot erase cache
7. reboot system
8. before doing the first setup i go into recovery and wipe cache.
I think 2.1 works but i want to be sure if i did everything right, especially with the custom kernel question and that i reboot into bootloader right after aroma says that the flash is finished.
Now i want to flash the 2.2.0 OTA because the update function through the ROM didnt work for me last time (it downloads the OTA but wasnt able to flash)
Im not sure how to flash the OTA right via recovery. Everytime i did that the ROM was kinda messed up, like when im turning the screen off and on Sense keeps loading and it takes some sec to unlock. And the venom tweaks app is totally laggy, even with the "trick" to go into app settings and wipe the cache and data which found on any other site (not xda...).
The problem is that they dont keep their instructions up-to-date (+ how to flash the OTA... right)
It looks to my like there are 100 different ways to flash 2.1.0 and 2.2.0 and only 1 is the right way which lets the ROM being amazing...
Hope you can help me. Thanks in advance!

turnschuh said:
Now i want to flash the 2.2.0 OTA because the update function through the ROM didnt work for me last time (it downloads the OTA but wasnt able to flash)
Im not sure how to flash the OTA right via recovery. Everytime i did that the ROM was kinda messed up, like when im turning the screen off and on Sense keeps loading and it takes some sec to unlock. And the venom tweaks app is totally laggy, even with the "trick" to go into app settings and wipe the cache and data which found on any other site (not xda...).
Click to expand...
Click to collapse
All you have to do ist to flash the OTA with your custom recovery like any other flashable zip if this isn't done automatically. You can simply copy it to your device from your pc or flash it from your mobiles download folder, it doesn't matter which way.
The 'trick' is very well known here at xda, but simply nobody wants to repeat it a hundred times... Here at xda there is even included the fact, that after rebooting you should change your skin once to get things going besides wiping cache and data in venom tweaks and hub.
What EXACTLY doesn't work with TWRP 2.3.3.0?

All you have to do ist to flash the OTA with your custom recovery like any other flashable zip if this isn't done automatically. You can simply copy it to your device from your pc or flash it from your mobiles download folder, it doesn't matter which way.
Click to expand...
Click to collapse
yea i did it like that. i just flashed it in the recovery, but im not sure if i have to wipe caches after or before doing that.
The 'trick' is very well known here at xda, but simply nobody wants to repeat it a hundred times... Here at xda there is even included the fact, that after rebooting you should change your skin once to get things going besides wiping cache and data in venom tweaks and hub.
Click to expand...
Click to collapse
about finding such "tricks": the problem is that those ROM release threads have tons of post (500+ sites of them) and it seems like 90% are from people who didnt even flash the ROM... i think you ll excuse me if i say i got tired of searching for my problems there^^
well can u tell me which skin i have to change? on venom tweaks or the htc skin on personalization? and app settings > venom tweaks > wipe cache and data right?
What EXACTLY doesn't work with TWRP 2.3.3.0?
Click to expand...
Click to collapse
when i flash it with 2.3.3.0 (or 2.5... its the same), the flash process doesnt even take up to 2 seconds and it says its finished and that causes a bootloop but doesnt make me wonder.
dont you have problems with TWRP flashing sense roms either?
ah and another one: did i flash the version 2.1 right and what about the custom kernel question?
well thanks for ur time.
edit: well this time flashing with twrp 2.3.3.0 worked somehow, but i choosed flashing without wipe (made it in recovery) and not to delete apps with aroma installer (which i did before)... just strange.

new problem. dont know whats wrong with my phone but:
wanted to make a backup of my ViperOneS 2.1 with TWRP 2.3.3.0 after lets say 70% of progress it starts turning off my phone and restarts into system. i flashed 2.5.0.0 but its the same issue (edit#1: with CWM too...). strange is that TWRP turned out my phone before when i wiped something there.
i think somethings really messed up atm...
edit#2: had to run a ruu over the system again, flashed twrp and backups seem work again..strange ****