All AOSP/CM ROMs bootlooping [FIXED] - HTC Sensation

All AOSP or CM ROMs are bootlooping. It gets to a certain stage in the boot animation, and then freezes for about 20-25 secs, then reboots and does the whole process again.
This only happens on AOSP or CM based ROMs. Doesn't happen on Sense based ROMs.
Anyone have any suggestions on how to solve this? I'm going to pull a logcat as soon as I can.
Thanks,
Phil

Probably wrong firmware.
Sent from my HTC Pyramid using xda premium

stonew5082 said:
Probably wrong firmware.
Sent from my HTC Pyramid using xda premium
Click to expand...
Click to collapse
So what firmware would I need for AOSP/CM based ROMs?

Steps to install rom properly after rooting and installing clockworkmod recovery.
For Gingerbread roms, 1.17 or 3.12, if you haven't touched the firmware, yours is 1.17.
For ICS roms, flash either 3.12 or 3.24. 3.12 is backwards compatible with GB roms, but 3.24 offers better performance.
Once you have the right firmware, put the rom onto your SD card and reboot into the recovery. There's an option to wipe data and factory reset, usually called "Wipe data/factory reset". Run that once, then install the rom from the zip that you copied earlier and that's about it. If you install anything cyanogen, make sure you flash Google Apps to get the market.
Roms should only take about 2 to 3 minutes to boot for the first time.
Possible issue you're having: Wrong firmware for the rom or you didn't wipe data before installing.

sshede said:
Steps to install rom properly after rooting and installing clockworkmod recovery.
For Gingerbread roms, 1.17 or 3.12, if you haven't touched the firmware, yours is 1.17.
For ICS roms, flash either 3.12 or 3.24. 3.12 is backwards compatible with GB roms, but 3.24 offers better performance.
Once you have the right firmware, put the rom onto your SD card and reboot into the recovery. There's an option to wipe data and factory reset, usually called "Wipe data/factory reset". Run that once, then install the rom from the zip that you copied earlier and that's about it. If you install anything cyanogen, make sure you flash Google Apps to get the market.
Roms should only take about 2 to 3 minutes to boot for the first time.
Possible issue you're having: Wrong firmware for the rom or you didn't wipe data before installing.
Click to expand...
Click to collapse
I do a superwipe and data wipe before installing, so it can't be that.
I'll try your solution now, thanks a lot!
I'm more of an app dev than firmware/ROM/kernels

redbullcat said:
I do a superwipe and data wipe before installing, so it can't be that.
I'll try your solution now, thanks a lot!
I'm more of an app dev than firmware/ROM/kernels
Click to expand...
Click to collapse
MAKE SURE MAKE SURE MAKE SURE your MD5s match. Flashing a firmware can brick your phone extremely easily so make sure your md5s match and that you have sufficient battery life left.
Also you will not be able to go back into bootloader without it asking if you want to flash the firmware if its still on your sd. If it asks you can say no but it will just reboot you into your system so if you have no system to boot into youll be stuck and will have to pull your sd card out and then reinsert it when in recovery.

It worked! Thanks guys, I owe you one

Related

[Q] First time flashing NS i9023 (serious flasher from SGS,SGS2)

Hey!
First let me say that I know all about flashing SGS and SGS2. Im a proud owner of SGS1 from day 1.
Last week I decided to finally flash my brothers i9023 so I flashed stock 4.0.3 with stock recovery. Then we wanted to flash some XDA stuff and I don't understand these guides...
I found one guide where you get superuser access with one click and usb cable, I did that, then I flashed CWM through Rom manager and flashed 4.0.4 from evilisto (v1.1) and it worked. Now I'm trying to flash some others, like nuhetri reloaded or pixel rom and I'm always getting stuck at boot animation. It just keeps "working" and nothing happens for 5+ minutes.
What am I doing wrong? Please help!
Best Regards
Luka
(in general)in recovery wipe data factory reset, format cache, davlik cache, system, boot. then flash new rom.
with nuhetri i think there is a bug where your not supposed to wipe data coming from another rom only davlik cache and cache then flash nuhetri
sean1984 said:
(in general)in recovery wipe data factory reset, format cache, davlik cache, system, boot. then flash new rom.
with nuhetri i think there is a bug where your not supposed to wipe data coming from another rom only davlik cache and cache then flash nuhetri
Click to expand...
Click to collapse
Hey and thanks for such quick reply!
I did all these now, rebooted to recovery (from CWM) and flashed this Fully Touched:
http://forum.xda-developers.com/showthread.php?t=1411734
Its stuck at boot image for 5 minutes now.
What now?
your using updated version of cwm? http://forum.xda-developers.com/showpost.php?p=22044793&postcount=82
steps
put rom on sd card
reboot into cwm recovery
wipe data, cache, davlik cahe, and format system and boot
install zip from sd card
choose rom you put on sd card
should say install from sd complete or something like that
reboot system now
let it boot into new rom (should not take more than 3-5 min)
edit: just seen this post in the rom thread your trying to flash http://forum.xda-developers.com/showpost.php?p=23255456&postcount=389 try redownloading again
sean1984 said:
your using updated version of cwm? http://forum.xda-developers.com/showpost.php?p=22044793&postcount=82
steps
put rom on sd card
reboot into cwm recovery
wipe data, cache, davlik cahe, and format system and boot
install zip from sd card
choose rom you put on sd card
should say install from sd complete or something like that
reboot system now
let it boot into new rom (should not take more than 3-5 min)
edit: just seen this post in the rom thread your trying to flash http://forum.xda-developers.com/showpost.php?p=23255456&postcount=389 try redownloading again
Click to expand...
Click to collapse
I did all that before... Im going to redownload, maybe its corrupted but I doubt it. Is it maybe because I have locked bootloader or something? Beacause I didnt use that long guide with "android SDK" in General, but some other very quick guide. Just plug USB, enable debugging and run some script and thats it.
devianceluka said:
I did all that before... Im going to redownload, maybe its corrupted but I doubt it. Is it maybe because I have locked bootloader or something? Beacause I didnt use that long guide with "android SDK" in General, but some other very quick guide. Just plug USB, enable debugging and run some script and thats it.
Click to expand...
Click to collapse
do yourself a favor, do it the right way the first time and save yourself headaches in the future. its not hard. fastboot oem unlock(bootloader), flash a custom recovery, flash a custom rom(and gapps) via the recovery, then boot up. thats it.
If you are more of a visual type of guy I suggest going on YouTube and search "zedomax". He has some really simple videos on how to root your nexus s, he has a couple videos on how to root but make sure its for a GSM nexus.
Simms got all in a simply way.
Unlock boot loader
Install or flash cwm
install the new stuff from SD card
reboot
Can anyone tell me or please provide a link to what unlocking bootloader does please.
Best Regards
Excuse my ignorance, I'm pretty new to this and I might not be of any help at all... but is it even possible to flash a custom recovery without unlocking the bootloader on the Nexus S?
I followed the instructions found on the NexusShacks.com website (How to root Nexus S or Nexus S 4G on ICS or Gingerbread) without any issues at all (sorry, can't post links due to low postcount :/)
No problems for me, I had zero experience with this sort of stuff but I have flashed a new ROM a every few days now without any issues whatsoever.
devianceluka said:
Can anyone tell me or please provide a link to what unlocking bootloader does please.
Best Regards
Click to expand...
Click to collapse
use this link: http://nexusshacks.com/
its complete with the files, pictures, video and some ics roms that you can try. let me know if you have any other question

Switching from one ROM to another

I'm currently using SkyRocket ICS (2.3.5 Gingerbread)
http://forum.xda-developers.com/showthread.php?t=1377087
and everything is awesome but my phone signal, att logo, wifi, notifications, doesnt appear on the top of the phone so i want to try out another ROM. This one in particular, NexusMod 4
http://forum.xda-developers.com/showthread.php?t=1426590
Do I just flash the new ROM in CWM recovery like I did to get my first ROM? Or is there more to it?
Thanks!
That's a problem on your end, that rom is flawless and you flashed it wrong
This is the guide I used to flash the ROM
http://www.traemcneely.com/2011/12/27/install-custom-rom-at-ciq-removed-short-review-instructions/
I compared it with ones on xda and it was identical but more noob friendly which I preferred. I dont know what I couldve possibly done wrong.. I followed EVERYTHING step by step. I love everything about this ROM except this one major annoyance.
penance said:
This is the guide I used to flash the ROM
http://www.traemcneely.com/2011/12/27/install-custom-rom-at-ciq-removed-short-review-instructions/
I compared it with ones on xda and it was identical but more noob friendly which I preferred. I dont know what I couldve possibly done wrong.. I followed EVERYTHING step by step. I love everything about this ROM except this one major annoyance.
Click to expand...
Click to collapse
It was a bad flash or bad download. Try to redownload and check the md5, then simply reflash it making sure to follow instructions and wipe properly
Sorry, but may I ask what an md5 is? And the specific ROM I want
http://forum.xda-developers.com/showthread.php?t=1377087
doesn't provide instructions, at least that I know of so I followed this guide
http://www.traemcneely.com/2011/12/27/install-custom-rom-at-ciq-removed-short-review-instructions/
Only problem I can think of that I made was flashing the RC 6.75 Stock ROM and then wiping cache partition and flashing the 7.4 Stock Nonewipeupdate right afterwards which is exactly what the guide asked for. Was I suppose to reboot after flashing the stock RC 6.75 ROM before flashing the 7.4 Stock Nonewipeupdate?
penance said:
Sorry, but may I ask what an md5 is? And the specific ROM I want
http://forum.xda-developers.com/showthread.php?t=1377087
doesn't provide instructions, at least that I know of so I followed this guide
http://www.traemcneely.com/2011/12/27/install-custom-rom-at-ciq-removed-short-review-instructions/
Only problem I can think of that I made was flashing the RC 6.75 Stock ROM and then wiping cache partition and flashing the 7.4 Stock Nonewipeupdate right afterwards which is exactly what the guide asked for. Was I suppose to reboot after flashing the stock RC 6.75 ROM before flashing the 7.4 Stock Nonewipeupdate?
Click to expand...
Click to collapse
You need to flash the base and boot it before flashing an update, like you said.
Before flashing any rom this is a general procedure
wipe data/factory reset 3x
Wipe cache 3x
wipe dalvik cache 3x
format system 3x
flash radio if need be
flash rom
reboot
dont touch phone for at least 10 mins
set up basics
if it has an update
reboot to cwm
wipe cache 3x
wipe dalvik cache 3x
flash update
reboot
Okk. ONE LAST question. The SkyRocket ICS (2.3.5 Gingerbread) ROM I'm using doesn't have or provide a radio file to DL on the page which I linked earlier. Does that imply that this particular ROM doesn't need it? Or am I suppose to find a radio to flash before flashing the ROM and update?
Thanks alot for your help/advice!! Really appreciate it!
penance said:
Okk. ONE LAST question. The SkyRocket ICS (2.3.5 Gingerbread) ROM I'm using doesn't have or provide a radio file to DL on the page which I linked earlier. Does that imply that this particular ROM doesn't need it? Or am I suppose to find a radio to flash before flashing the ROM and update?
Thanks alot for your help/advice!! Really appreciate it!
Click to expand...
Click to collapse
In about phone, what does it say for baseband? Kj2 is the 2.3.5 stock radio
Sent from my SAMSUNG-SGH-I727 using Tapatalk 2
If the radio you're using is working and you're flashing from gb to gb, you shouldn't have to worry about the radio. You'll still have the same one. Radios flash separately from roms. I don't think you'll NEED to flash a new radio unless you change to an ICS rom.
Sent from my SAMSUNG-SGH-I727 using xda premium
Android version 2.3.6
Baseband version I727UCKJ2
Kernal version 2.6.35.11+
Build number Sky-ICS RC7.4 Stock
When I purchased my phone and after I rooted it, I was v2.3.5 but after I flashed my first ROM (which is my current ROM) the android version changed to v2.3.6. So if KJ2 is the stock radio for v2.3.5 is there a possibility my problem of not having the att logo and wifi signal on the top of my phone due to not having the correct radio for this ROM? or for v2.3.6 in general? Or is it from what you said earlier, my flashing process was wrong? Or a mixture or not having the correct radio and flashing wrong?
boobah204 said:
If the radio you're using is working and you're flashing from gb to gb, you shouldn't have to worry about the radio. You'll still have the same one. Radios flash separately from roms. I don't think you'll NEED to flash a new radio unless you change to an ICS rom.
Sent from my SAMSUNG-SGH-I727 using xda premium
Click to expand...
Click to collapse
Well, I don't really know whether or not the radio is working. I suppose in my case it is working since I am able to recieve and make calls, text, and go on the web. However, I am unable to see the att logo, wifi/cell signal on the top of my phone. I don't know if this problem has anything to do with the radio though. Sorry for my lack of understanding..
I'm assuming the problem is more my fault in terms of not flashing correctly. I have no idea whether or not I need a separate radio for this ROM.
Sounds like a systemui /frame work problem
Wipe data/cache/dalvik
Reflash
Fully boot
Shutdown
Flash update
Wipe dalvik
Reboot.
The signals at the top wouldn't be affected by he radio. You would most likely get them back if you reflashed your from or flashed another. As long as it's a 2.3.5 or 2.3.6. And also follow the instructions (usually pretty standard, wipe data factory reset a few times, wipe cache partition, advanced, wipe dalvik cache a few times, go back, mounts and storage, format system a few times. Then install zip from SD card) oh and always backup first and make sure you can restore the backup. But yeah if you can make calls and use internet, your radio should be OK.
Sent from my SAMSUNG-SGH-I727 using xda premium
silver03wrx said:
Sounds like a systemui /frame work problem
Wipe data/cache/dalvik
Reflash
Fully boot
Shutdown
Flash update
Wipe dalvik
Reboot.
Click to expand...
Click to collapse
Thanks! That's what I figured the problem to be JK.
I'll give it go and hope for the best this time around.
boobah204 said:
The signals at the top wouldn't be affected by he radio. You would most likely get them back if you reflashed your from or flashed another. As long as it's a 2.3.5 or 2.3.6. And also follow the instructions (usually pretty standard, wipe data factory reset a few times, wipe cache partition, advanced, wipe dalvik cache a few times, go back, mounts and storage, format system a few times. Then install zip from SD card) oh and always backup first and make sure you can restore the backup. But yeah if you can make calls and use internet, your radio should be OK.
Sent from my SAMSUNG-SGH-I727 using xda premium
Click to expand...
Click to collapse
Alright thanks alot for your guide and clarification. Still learning day by day
penance said:
Alright thanks alot for your guide and clarification. Still learning day by day
Click to expand...
Click to collapse
Just do this and skip the radio step
xcrazydx said:
You need to flash the base and boot it before flashing an update, like you said.
Before flashing any rom this is a general procedure
wipe data/factory reset 3x
Wipe cache 3x
wipe dalvik cache 3x
format system 3x
flash radio if need be
flash rom
reboot
dont touch phone for at least 10 mins
set up basics
if it has an update
reboot to cwm
wipe cache 3x
wipe dalvik cache 3x
flash update
reboot
Click to expand...
Click to collapse
Not sure the deal with your cell/wifi signals not showing in your status bar, but, the carrier logo could have been removed in the ROM itself.
I would try out the nexusmod zero ics I'm running it now and I like it a lot more than nexus 4. Also when I went from the from you are on now I had to do a super wipe before I could get the ics rom to work without bootloop
Sent from my SAMSUNG-SGH-I727 using XDA

Bricked G2x trying to install Eaglesblood HELP!

Hi everyone, Im relatively new to the whole flashing and custom rom scene. I rooted my wind mobile (Canadian carrier) LG-P999 and ran CMR before trying to flash EGB. I used the instructions on the forum post to install EGB. In the installation process however, It looked like Gapps were already installed, I installed the Gapps I was told to download here http://forum.xda-developers.com/showthread.php?t=1575199 again anyways. My phone will now not start, all that happens when I press the power button is the LG logo flashes, and then the Eaglesblood logo flashes then the phone shuts down. I have the CWM recovery file saved on my computer. Can someone help me unbrick my phone? thanks in advance, and please excuse my horrible grammar, I'm quite terrified right now.
EDIT: I messed around with my phone, and I am able to get into the Android System Recovery. Should I wipe data/factory reset? Will that solve my issues?
First get the rom you want to install on a sd card boot into recovery and wipe and install. If you factory reset it still will try and load eaglesblood. If using a cm 7 rom like eb or hellfire flash gapps right after the rom. Hope this helps
Sent from my LG-P999 using xda premium
How I do it with no problems
monte666 said:
First get the rom you want to install on a sd card boot into recovery and wipe and install. If you factory reset it still will try and load eaglesblood. If using a cm 7 rom like eb or hellfire flash gapps right after the rom. Hope this helps
Sent from my LG-P999 using xda premium
Click to expand...
Click to collapse
Anytime you flash rom, I recommend these steps. (Some may argue that it's over kill)
Get a Copy of Titanium Backup Pro.apk
Batch back-up all your user apps if you so wish. (These first two are optional, but I highly recommend)
Copy ROM, Kernel, and Gapps to MicroSD card. (EXTERNAL)
Boot into CWM.
Do a Wipe data/factory reset
Wipe cache partition
select advanced-->wipe dalvik cache
mounts and storage-->format /system
Install zip from sdcard (not the apply update option!)
select your ROM, flash
select you kernel, flash,
<optional, if your on March BB and depending on ROM, you may need to flash new baseband.zip, forum search for it)
select gapps, flash
Reboot!
Sometimes upon booting you made need to wait 5-10min for phone to come up and be speedy. Be patient.
Hope some of this helps since your able to boot into CWM, which means your not bricked, yet. I;ve been there in a loop, called it soft bricked. Performed all of the above steps, never had the problem occur since. I jump between two GB 2.3.7 ROMS and two ICS ROMs with ease.

Help! Trying to revert to stock rooted from CM10

I upgraded to CM10 from the original OS and I am using the latest version to root my phone, I am using TWRP. Anyway, Everything worked fine, I rooted the phone, I upgraded to CM10. I want to go back to the original OS. I downloaded [ROM][8/3] - Stock Rooted AT&T 2.20.502.7 - Android 4.0.4 - Odex or De-Odex, I got the ODEX version, I flashed it to my phone but its just hangs at the HTC One X Splash screen with the red lettering. What am I missing here? I can get back into recovery and I backed up my old ROM just in case.
How long are you letting it hang for? Try 2 more power downs and power ons. The first few times it took about 5 min to load.
mgutierrez87 said:
How long are you letting it hang for? Try 2 more power downs and power ons. The first few times it took about 5 min to load.
Click to expand...
Click to collapse
It just shuts off and turns back on again, it basically loops. Did I download the wrong file maybe? Is there a specific ROM I need other than the one I mentioned earlier?
Boot into recovery and wipe your cache and dalvik cache again
mgutierrez87 said:
Boot into recovery and wipe your cache and dalvik cache again
Click to expand...
Click to collapse
Factory reset, wipe system, flash ROM, wipe cache and delvik.
Any time you go from non sense to sense or vise versa you have to wipe the system and factory reset.
Sent from my One X using xda app-developers app
This was the ROM that worked when i did it.
http://forum.xda-developers.com/showthread.php?t=1872842
---------- Post added at 04:53 AM ---------- Previous post was at 04:46 AM ----------
Myrder said:
Factory reset, wipe system, flash ROM, wipe cache and delvik.
Any time you go from non sense to sense or vise versa you have to wipe the system and factory reset.
Sent from my One X using xda app-developers app
Click to expand...
Click to collapse
He mentioned in another thread that he did those steps. The only other thing I would try is to flash the boot.IMG from the ROM you want to use
I still want to keep my phone rooted. This wont kill the root right?
No the ROM posted above is stock rooted
But if you made a backup as you said in the first post why are you not just restoring the backup?
Sent from my Nocturnalized One XL using Forum Runner
Basically where I am right now. I downloaded the original OS, by following instructions, I have managed to delete my backed up rom of CM10 that i backed up earlier. I was able to FLASH the OS I wanted, I flashed the boot.img file using fastboot. I restarted the phone and now its just stuck on the HTC Quietly Brilliant screen with the red lettering at the bottom. It doesn't restart or anything, it just hangs there. What am I missing here guys? ):
I'm going to install cm10 right now them go back to stock rooted and see what's up with this
There's no issues going back and forth. You probably flashed a bad ROM
yea, your most likely just doing it wrong. you need to do a full wipe and flash boot.img
answer: oh yea cant flash the stock rom using twrp 2.3.1.0 you will need to flash twrp 2.2.2.0 then flash stock rom. that is actually most likely your problem.
What hboot are you on? If you separately flashed boot.img from CM10 via fastboot, you might need to again separately flash the boot.img from the stock ROM. Also remember that the procedure employed to root 2.20 is substantially different from the root procedure to root the previous build of stock. Not sure what software you rooted, or whether this would pose a problem, but it's a consideration.
Another option is to just restore to stock via RUU and re-unlock, re-root, if nothing else works. Getting stuck on HTC splash screen sounds like a boot.img issue. Good luck.
DvineLord said:
answer: oh yea cant flash the stock rom using twrp 2.3.1.0 you will need to flash twrp 2.2.2.0 then flash stock rom. that is actually most likely your problem.
Click to expand...
Click to collapse
Really? Why is that?
Just curious, I haven't heard this before. Is this a known issue with flashing the 2.20 stock ROM? I haven't seen any cases of ROMs (stock rooted or otherwise) being sensitive to version of TWRP. At least not the case of having to use an older version (keeping TWRP updated is usually the recommendation).
Of course, just because I haven't heard of it, doesn't mean it didn't happen!
Did you fastboot flash boot boot.img?
Sent from my HOX running Cyanogenmod 10
redpoint73 said:
Really? Why is that?
Just curious, I haven't heard this before. Is this a known issue with flashing the 2.20 stock ROM? I haven't seen any cases of ROMs (stock rooted or otherwise) being sensitive to version of TWRP. At least not the case of having to use an older version (keeping TWRP updated is usually the recommendation).
Of course, just because I haven't heard of it, doesn't mean it didn't happen!
Click to expand...
Click to collapse
im assuming the age of the stock rooted would have conflicts with the new twrp. i have had problems with roms not flashing with newest twrp. it is also a known problem since twrp 2.3.1.0 release.

[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 ****

Categories

Resources