Hi guys,
I have worked with miui one my HTC one V for some time but my whatsapp became very slow so I decided I wanted to go back to the "regular" android. I looked up a dutch step-by-step because i'm not very into the flashing thing. Everything worked out fine until step 15 where I came into a bootloop. I managed to acces clockworkMod Recovery but what should I do now? Where did I go wrong?
Thanks!
Step by step: techtastic.nl/2013/03/installeer-android-4-2-2-jelly-bean-op-de-htc-one-v/ (can't post links)
What did I do:
- Started with Miui 2.8.3
- Installed Clockworkmod (again)
- Downloaded primou_PAC_JB_4.2.2-v20.1.0_03MAR2013-224423.zip
- Downloaded Gapps
- Followed the Step-by-Step very carefully
- After step 14 i came into a bootloop.
I can't see what is your tutorial but the first thing I think is: Have hou flash the good kernel for your new rom via fastboot? And of course have you wipe everything?
Follow this
http://forum.xda-developers.com/showthread.php?p=34236649
Sent from my One™ V using xda-developers-app
yeah I guess you are both right. I forgot to flash the kernel :s
Thanks for the link, really helped!
I made a new plan after reading the whole afternoon and it is the following:
1. Factory reset + wipe cache
2. Flash CM9 20121016
3. Flash boot.img (the right one this time, HELLBOY)
4. Flash gapps-ics-20120429 signed
5. Reboot
What do you think of this plan?
Thanks so much for your help!
Should work
But why don't you try CM 10 or for me the best, Slim bean?
patgou.007 said:
Should work
But why don't you try CM 10 or for me the best, Slim bean?
Click to expand...
Click to collapse
Yeah I considered that but I'm switching from miui because some apps were very slow. So I'm worried the same issue will pop up if I go for CM10...
When I fix this I can always switch off course
I'm with slim bean since two months and for me, it's faster than CM 9. I reboot the phone one time a week and no problem.
patgou.007 said:
I'm with slim bean since two months and for me, it's faster than CM 9. I reboot the phone one time a week and no problem.
Click to expand...
Click to collapse
Sounds nice! I might try it later, enough stress for today!
Problem solved btw! Thanks a lot for your help :laugh:
I tried same this morning and same issue happened with me. PACman ROM is still having some issue u can read it in PACman forum of ROM. Go to latest comments posted by users.
As far as I know there is a issue of boot.img for PACman ROM.
To solve this,
1.I went to fast boot mode using hreset
2. Then I flashed boot.IMG from 4.1.2 aokp ROM for HTC one v.
3. Then I just shut down my cell.
4. Go to recovery and then installed aokp 4.1.2 ROM
5. And everything went back to normal.
Sent from my One V using xda app-developers app
Related
After installing Cyanogenmod 9 on the One X I started to notice extremely poor signal, Mobile and Wi-Fi. Also the phone would crash and randomly reboot when doing simple tasks such as opening messages etc.
Upon trying to get into recovery to install a different rom, the phone now flashes on a black screen and restarts the phone.
To try and solve this issue, I unrooted the phone and restored to stock recovery.
I then re-rooted the phone and installed clockworkmod recovery again.
I can now access clockworkmod recovery although it seems to have no effect. Installations of any rom fail and cyanogenmod always pops straight back up again after rebooting.
Has anyone else had this issue?
Does anyone have a way to fix this? Possibly to force the phone completely back to stock?
You can try first "SuperWipe" (from ARHD's thread) and flash a new ROM (don't forget boot.img before...)
Kamiil29 said:
You can try first "SuperWipe" (from ARHD's thread) and flash a new ROM (don't forget boot.img before...)
Click to expand...
Click to collapse
Thanks for your quick reply, how do I do the super wipe? and where can I download the One X stock roms from?
AndyB said:
Thanks for your quick reply, how do I do the super wipe? and where can I download the One X stock roms from?
Click to expand...
Click to collapse
Unfortunately I can't help you with SuperWipe, but you can find the HOX stock ROMs here.
Sent from my HTC One X using Tapatalk 2
Ran superwipe and tried to install the stock rom. Superwipe ran fine and did the job, although the rom installation still failed as it was doing before and I am now stuck with a htc bootloop. The device won't boot into recovery either. Any ideas anyone?
AndyB said:
Ran superwipe and tried to install the stock rom. Superwipe ran fine and did the job, although the rom installation still failed as it was doing before and I am now stuck with a htc bootloop. The device won't boot into recovery either. Any ideas anyone?
Click to expand...
Click to collapse
Did you try holding down the Power and Volume Down buttons while in the bootloop to enter the bootloader? Hold them down until the lights start to flash, the screen goes off and then the bootloader comes up.
If you can get into recovery with that, factory reset, clear cache and dalvik cache (under advanced) then try install the ROM.
I'm not the best person to be helping, but I hope that works for you!
I had a similar problem once where the phone would just sit on the HTC One X screen, and trying to go into recovery just put the phone back to the HTC screen. I fixed it by flashing the boot.img, factory reseting, clearing out caches and installing the ROM again. No problems since.
I'm afraid if this doesn't work, I may have to abandon you and let someone else take over, as I'm no expert, but I'll see what I can do to help.
Edit: sorry, it is 2AM here and I need some rest for an early start at 6AM. I will check up on this thread when I wake.
Sent from my HTC One X using Tapatalk 2
FIXED!!!
To anyone else having this problem, I downloaded ARHD Flashboot 7.0.0 and ARHD 7.0.0, followed the instructions on what to do and installed ARHD successfully.
This has now completely gotten rid of Cyanogenmod and seems to have got clockworkmod working again.
It's probably work using the "Fix Permissions" option in ROM manager before you attempt this as I believe that is what got clockworkmod working and able to install files again. (I may be wrong)
Thankyou for everyone's assistance.
AndyB said:
To anyone else having this problem, I downloaded ARHD Flashboot 7.0.0 and ARHD 7.0.0, followed the instructions on what to do and installed ARHD successfully.
This has now completely gotten rid of Cyanogenmod and seems to have got clockworkmod working again.
It's probably work using the "Fix Permissions" option in ROM manager before you attempt this as I believe that is what got clockworkmod working and able to install files again. (I may be wrong)
Thankyou for everyone's assistance.
Click to expand...
Click to collapse
Glad you got if working
Sent from my HTC One X using Tapatalk 2
I've tried to flash the two different ROMs out for JB and for some reason it is not getting past the Nexus Logo Boot screen. I can flash any ICS ROM but JB never gets past the boot screen. I've been flashing ROMs since the OG Droid and have never experienced this before.
Steps already taken:
1) Full wipe
2) Format of system and data
3) executed Super Wipe Script
4) Battery Pulls
5) Backed out of CWM and unmounted system and data
6) Flashed Various AOKP and AOSP ROMs and tried to JB ROM from those ICS ROMs
7) Performed a factory restore of the phone using WugFresh's ToolKit (un-rooted and locked phone) and then Rooted, unlocked, and flashed CWM again
8) Flashed Team Win Recovery and re-flashed JB ROMs
I have tried everything I can think of and yet nothing has worked. Has anyone Else experienced this or does anyone have any suggestions on what I can possibly do to get past the Nexus Boot screen? Thanks in advance.
how long are you waiting after the install?
Zepius said:
how long are you waiting after the install?
Click to expand...
Click to collapse
Average wait time is 20 minutes but I've waited up to 4 hours.
which rom are you flashing?
try this one: http://www.teambamf.net/topic/4064-romtoro-jellybamf-13/
it works for me perfectly (thanks adrynalyne)
Zepius said:
which rom are you flashing?
it works for me perfectly (thanks adrynalyne)
Click to expand...
Click to collapse
I've tried Liquid Vicious Versions 1-3 and BAMF Versions 1.0 and 1.2. Thanks for the updated BAMF...I'll try that one now.
I am having the same problem as you, I flashed multiple JB roms and it is stuck at the X screen. I can flash ics roms easily tho.
I had the freeze at logo issue a few times while I was trying to get my JB up and running.
1. I got superwipe from http://forum.xda-developers.com/showthread.php?p=20473980
2. I dl JellyBelly and GApps from http://rootzwiki.com/topic/28677-rom-jelly-belly-v17-07012012-jellybean-41-its-all-about-speed/
3. Cleared cache/factory reset
4. Flashed and used superwipe
5. Flashed JellyBelly then GApps
I had to wait about 5 minutes while it booted. Hope this helps, yall.
I'll definitely try those steps...Thanks!
Sent from my HTC One X using Tapatalk 2
keno23 said:
I'll definitely try those steps...Thanks!
Sent from my HTC One X using Tapatalk 2
Click to expand...
Click to collapse
Glad to pass along the help I got earlier :highfive:
consultant.ben said:
I had the freeze at logo issue a few times while I was trying to get my JB up and running.
1. I got superwipe from http://forum.xda-developers.com/showthread.php?p=20473980
2. I dl JellyBelly and GApps from http://rootzwiki.com/topic/28677-rom-jelly-belly-v17-07012012-jellybean-41-its-all-about-speed/
3. Cleared cache/factory reset
4. Flashed and used superwipe
5. Flashed JellyBelly then GApps
I had to wait about 5 minutes while it booted. Hope this helps, yall.
Click to expand...
Click to collapse
Unfortunately it did not work...same Nexus Bootscreen forever. Thanks though.
i have the same the problem with my phone , i flash the jb rom it works fine the first time booting i setup my account download my apps every thing works fine BUT when i re-start the phone the phone got stock on the google logo and don't re-start again, so guess what i have to try another rom so i try a regular ICS rom guess what on the first boot the phone got stock on the boot logo so i try another ICS rom and the same thing happing stock again on the boot logo, so i have to do flash the google factory rom to my phone got back to work
Same her.. infinite boot loop.. I'm tired of unbricking back to stock
Flash all kinds of from and kernel combo and still got boot loop.. I hope someone can help us with this..
Try mROM http://forum.xda-developers.com/showthread.php?t=1763823
Make sure wipe/factory reset and also wipe caches while you're at it. Also make sure that CWM is updated.
keno23 said:
Unfortunately it did not work...same Nexus Bootscreen forever. Thanks though.
Click to expand...
Click to collapse
Same here, I've tried just about every rom out there now and have cleaned the phone out several times. Wonder if there is anyone who had a boot longer than 20 minutes and finally was able to get it to boot, wonder what they did to get it to boot. I've waited hours with some of these roms and still no luck.
nothingshocking said:
Same here, I've tried just about every rom out there now and have cleaned the phone out several times. Wonder if there is anyone who had a boot longer than 20 minutes and finally was able to get it to boot, wonder what they did to get it to boot. I've waited hours with some of these roms and still no luck.
Click to expand...
Click to collapse
Are you wiping dalvik and system cache along with doing data wipe?
mb9023 said:
Are you wiping dalvik and system cache along with doing data wipe?
Click to expand...
Click to collapse
wipe data/factory reset -> wipe cache partition -> wipe dalvik -> format /system -> format /data -> format/cache. I've tried super wipe. All Roms never get passed the boot animation. I get past the "Google" unlock symbol, but it just sits at the boot animation. It doesn't reboot or anything, just sits there for hours or when I get bored looking at it after about 30 minutes or so.
@nothingshocking
We have the same problem.. I been flashing all kinds of jb rom since last week..I'm not new in flashing rom and kernel so I know what doing.. it so weird that it only stay in Google logo (x) when I flash jb rom..but if I flash ics it will boot up.. hayzzz I hope someone can help us with this issue.. calling all great dev. I hope u can help us..
Sent from my Galaxy Nexus using XDA Premium App
landrian18 said:
@nothingshocking
We have the same problem.. I been flashing all kinds of jb rom since last week..I'm not new in flashing rom and kernel so I know what doing.. it so weird that it only stay in Google logo (x) when I flash jb rom..but if I flash ics it will boot up.. hayzzz I hope someone can help us with this issue.. calling all great dev. I hope u can help us..
Sent from my Galaxy Nexus using XDA Premium App
Click to expand...
Click to collapse
Not going to happen man...I've tried EVERYTHING and have gotten feedback from various devs to no avail. All I get is Nexus boot logo FOREVER.
Solution is to flash it back to stock (plus unroot and re-lock) and then take it in to a store and get another one shipped to you since it's still under the annual warranty. As for the issue for bringing it in, just say it boot loops at random times (that's not technically a lie).
Sent from my Galaxy Nexus using Tapatalk 2
Have you tried flashing the JB Boot loader and then flashing the JB ROM??
It is from jakeday and his Jelly Belly ROM
adclem said:
Have you tried flashing the JB Boot loader and then flashing the JB ROM??
It is from jakeday and his Jelly Belly ROM
Click to expand...
Click to collapse
That doesn't work either. Thanks though.
Sent from my HTC One X using Tapatalk 2
Hello Folks
I have a problem booting my GNex when particularity I flash gapp (20120726). Right now, it has BlackBean Rom that includes gapp. A few days ago I tried flash XenonHD, when I did it, boot everythings is ok, but when I flashed the Gapps, GNex presents GoogleLogo and reboot again, going to Recovery. I made a Full Wipe, Dalki, etc... nothing. it stays trying to reboot and going to Recovery
The same thing happens when yerstady I tried to flash AOKP.
Thank you.
I run into really weird problems if I don't flash the ROM and gapps at the same time, depending on the ROM, anything from boot loops to misbehaving apps. Try and start from scratch: make a titanium backup, wipe everything, then install ROM+gapps. If that doesn't work, it's probably your version of gapps. Maybe a bad download or just a bad package entirely.
Sent from my Galaxy Nexus using xda app-developers app
I did it, same result. It´s weird. I just can flash Roms with Gapps included. I downloaded several times the gapp zip.
Could be kernel? Maybe, I dont know.
On ICS´s times I could flash every rom I want (even MIUI), but on JB no.
What exactly are you doing? Give me a step by step from the beginning.
Sent from my Galaxy Nexus using xda app-developers app
Echo5ive said:
What exactly are you doing? Give me a step by step from the beginning.
Sent from my Galaxy Nexus using xda app-developers app
Click to expand...
Click to collapse
Firstly, thank you for you time
Step GNex Maguro
1) FullWipe
2) Wipe cache, Dalvik, etc
3) Flash ROM (XenoxHD or AOKP) JB
4) Flash gapps (ver. 20120726), downloaded from goo.im
5) reboot system
then...
...
Appear GoogleScreen
...(10 secs)
reboot
...
Appear GoogleScreen (again)
...10 secs
(PUFF) Go to Recovery.
...
I reboot again and it keep going back to recovery
But, when I flash a ROM that includes gapp inside (ie Black Bean aokp), everything is ok. Boot normaly.
http://forum.xda-developers.com/showthread.php?t=1778555
Looks like it might just be an issue with your phone. A hand full of other people are experiencing similar things with jb.
There should be a super wipe utility that you can flash before you flash the ROM. You'll have to search for it tho. I'll look for it when I have a second but that's about the best I can do for you right now.
Sent from my Galaxy Nexus using xda app-developers app
Ooh my... Thank you
http://forum.xda-developers.com/showthread.php?t=1361348
Here's the original.. the link is at the bottom of the OP. The direct download is http://goo.gl/Lerzy
I haven't tried it but all it does is format everything except your sdcard... It's technically made for the GSM version but if you have the CDMA, it should do the exact same thing. The same usual disclaimer applies...
If that does not work, I would try and find another GB ROM and take the gapps from that. Try out a few other ones to see if it works. If you install over clean (as mentioned before) it seems to be more stable.
Thank you
Now I can notice that when I flash Rom based CM/AOSP I can flash gapps normally, but AOKP not. Hmm.. it´s wierd.
I dont know what I did, but now I cant flash AOKP Rom, noone, even I can´t restore my backup from CMW... I get /system problem...
Well, for a while I will stay on a ROM based CM/AOSP til I get or find the cause.
Thank everyone.
Hello guys!
As the title says, I keep on having boot loops after flashing any custom JB Roms (Jedi, LiquidSmooth, CM Nightly, Slimbean). I'm not new to flashing roms (I got LG units though, SU660 and KU5900). When I tried flashing ICS Roms, I don't have any problem. But I want JB that bad!
I followed KonstantinKeller's thread of restoring/recovering from a bad flash (going back to GB), rooted following Melvin's thread. Then did all the prerequisites..like the common wiping of data, clear cache & davlik. But then again after flashing JB roms listed above, I keep on having boot loops!
What did I do wrong? This ain't my first time flashing (first time on this phone -T989- though)
I read some posts with almost the same problem, but I don't think I found a solution for this. Any good soul that can extend their help is highly appreciated. Thank you in advance.
I got a bootloop before when trying to flash JB roms and what I did was restore to original state (using the bad flash recovery technique), and then not rooting it but installing cwm through Odin and dirty flashing the Rom in cwm. Once it flashed I used it for a few to make sure that everything was working correctly. Then I got the goo manager app and got twrp. After that I followed all the steps in the OP (Jedi jelly) and flashed the Rom. Now I'm running Jedi jelly 3.1 perfectly. Hope this method helps.
Sent from my SAMSUNG-SGH-T989 using xda premium
djtreo said:
Hello guys!
As the title says, I keep on having boot loops after flashing any custom JB Roms (Jedi, LiquidSmooth, CM Nightly, Slimbean). I'm not new to flashing roms (I got LG units though, SU660 and KU5900). When I tried flashing ICS Roms, I don't have any problem. But I want JB that bad!
I followed KonstantinKeller's thread of restoring/recovering from a bad flash (going back to GB), rooted following Melvin's thread. Then did all the prerequisites..like the common wiping of data, clear cache & davlik. But then again after flashing JB roms listed above, I keep on having boot loops!
What did I do wrong? This ain't my first time flashing (first time on this phone -T989- though)
I read some posts with almost the same problem, but I don't think I found a solution for this. Any good soul that can extend their help is highly appreciated. Thank you in advance.
Click to expand...
Click to collapse
are you using darkside scripts to wipe? because they will cause bootloops
skinsfanbdh said:
are you using darkside scripts to wipe? because they will cause bootloops
Click to expand...
Click to collapse
is there any way to reverse the loop that the darkside wipe is causing?
it REALLY sounds like the recovery u are using is TOO OLD. Make sure u are using the latest version of twrp (2.3.3) to flash all jellybean roms.
TWRP is backwards compatible and touch capable, so if you're worried about flashing GB or ICS ROMs it'll do the trick just fine
it is however a requirement for flashing all 4.1 ROMs.
Basic install instructions:
make sure u have root
download goo manager from play
open > menu > install open script recovery
agree to everything, but make sure t989 is in the downloaded image name
reboot to recovery u should see twrp
Having only dabbled with rooting and upgrading a Evo View tablet, I jumped into the deep end with my Incredible 2.
I got it to S-off and rooted and have been trying a few different ROMS (mostly chillybean's) and have what seems to be a common problem:
Sound works fine until a call is received. The ringtone fails to play and then sound doesn't work at all until its reset. I have had success resetting the sound by activating Google Voice Search with a long press of the search button. This seems to be true for CM10.2 and PAC. I didn't test this on an Evervolv because 3G never comes back on after Wi-fi has been turned on.
Has anybody had better luck with a particular 4.3 ROM? Does this sound issue affect pre-4.3 JB roms?
Thanks!
brettbee said:
Having only dabbled with rooting and upgrading a Evo View tablet, I jumped into the deep end with my Incredible 2.
I got it to S-off and rooted and have been trying a few different ROMS (mostly chillybean's) and have what seems to be a common problem:
Sound works fine until a call is received. The ringtone fails to play and then sound doesn't work at all until its reset. I have had success resetting the sound by activating Google Voice Search with a long press of the search button. This seems to be true for CM10.2 and PAC. I didn't test this on an Evervolv because 3G never comes back on after Wi-fi has been turned on.
Has anybody had better luck with a particular 4.3 ROM? Does this sound issue affect pre-4.3 JB roms?
Thanks!
Click to expand...
Click to collapse
I answered part of my own question:
I confirmed that the Evervplv nightly 2013.09.24 has a working ringtone. But once WiFi is turned on, 3G is off until reboot.
try beanstalk 1.300
brettbee said:
I answered part of my own question:
I confirmed that the Evervplv nightly 2013.09.24 has a working ringtone. But once WiFi is turned on, 3G is off until reboot.
Click to expand...
Click to collapse
I have been using beanstalk 1.300 with the b-team CM kernel.it has 4.2.2 and everything works! its fast and smooth with great battery life the 4.3 roms have some issues so I am gonna stick with this one
AFAIK everything in the newest Evervolv works.
phillibl said:
AFAIK everything in the newest Evervolv works.
Click to expand...
Click to collapse
Are you using a nightly? Which one?
Does 3G come back after WiFi is turned on?
Chillybean updated his CM10.2 ROM -- the 20130929 build has the sound issue fixed.
kahlil88 said:
Chillybean updated his CM10.2 ROM -- the 20130929 build has the sound issue fixed.
Click to expand...
Click to collapse
The 929 rom is not working for me and I know at least of couple of other folks in the same situation.
Are you using the 929 ROM with sound successfully? What - exactly - did you do to install it? I'm wondering if it's a I'm-doing-something-stupid/wrong thing or maybe a hardware revision thing.
Thanks!
brettbee said:
The 929 rom is not working for me and I know at least of couple of other folks in the same situation.
Are you using the 929 ROM with sound successfully? What - exactly - did you do to install it? I'm wondering if it's a I'm-doing-something-stupid/wrong thing or maybe a hardware revision thing.
Click to expand...
Click to collapse
Flashed it like any new ROM. Backup important data and reboot into recovery mode. Once in recovery mode:
Factory reset
Wipe cache
Advanced -> wipe dalvik cache
Mount/unmount -> format system
Format boot
Install AntiVenom SDW
Flash a ROM
Flash GApps
Wipe dalvik cache
Reboot and you should be golden. I've had it hang at the boot screen a few times, had to start over and skip installing GApps until I was sure it would boot.
kahlil88 said:
Flashed it like any new ROM. Backup important data and reboot into recovery mode. Once in recovery mode:
Factory reset
Wipe cache
Advanced -> wipe dalvik cache
Mount/unmount -> format system
Format boot
Install AntiVenom SDW
Flash a ROM
Flash GApps
Wipe dalvik cache
Reboot and you should be golden. I've had it hang at the boot screen a few times, had to start over and skip installing GApps until I was sure it would boot.
Click to expand...
Click to collapse
Thanks! I'll give that a try. I wasn't quite as thorough with wiping/formatting as you were. Fingers crossed....
kahlil88 said:
Flashed it like any new ROM. Backup important data and reboot into recovery mode. Once in recovery mode:
Factory reset
Wipe cache
Advanced -> wipe dalvik cache
Mount/unmount -> format system
Format boot
Install AntiVenom SDW
Flash a ROM
Flash GApps
Wipe dalvik cache
Reboot and you should be golden. I've had it hang at the boot screen a few times, had to start over and skip installing GApps until I was sure it would boot.
Click to expand...
Click to collapse
brettbee said:
Thanks! I'll give that a try. I wasn't quite as thorough with wiping/formatting as you were. Fingers crossed....
Click to expand...
Click to collapse
Well, that didn't work for me. The only thing I didn't do was "Format boot." I couldn't find that in Revolutionary CMW.
I'm thinking there's something different about my phone. Hardware? How I rooted it?
brettbee said:
Well, that didn't work for me. The only thing I didn't do was "Format boot." I couldn't find that in Revolutionary CMW.
I'm thinking there's something different about my phone. Hardware? How I rooted it?
Click to expand...
Click to collapse
What version of gapps are you installing? Try flashing the ROM without installing gapps and see if it will boot, then if you're successful go back into recovery mode and flash gapps-jb-20130813-signed.zip from here.
funny question, does docking mode work with these roms?
Check Chilly's forum. The Inc S Dev posted a flashable fix for the sound problems. I flashed it and all is fine.
EDIT: Damn autocorrect...
Sent from my Nexus 7 using xda app-developers app
flinzak said:
Check Chilly's forum. The Inc S Dev posted a flashable fix for the sound problems. I flashed it and all is fine.
EDIT: Damn autocorrect...
Sent from my Nexus 7 using xda app-developers app
Click to expand...
Click to collapse
Thanks - found it and downloaded it! I'll give it a try when I can have my phone out of service.....
I flashed Evervolv 10/30 nightly yesterday and it looks like they have the 3G/WiFi toggle issue resolved. The quick settings were missing but, I'm guessing that'll be corrected in the next build. Also, flashed B-Team Kernel. 4.3-s2w version resulted in bootloops but, the 4.3-v2 version worked just fine. No sound issues as far as I can tell.
Does the latest Everlov nightly work? Also what are you all referring to when you say Chilly's forum, the "Inc S dev fix", and AntiVenom SDW? I went through 5-10 of the most recent pages on Everlov and didn't see any of these things, so would someone mind providing links?
Thanks
jonatcer said:
Does the latest Everlov nightly work? Also what are you all referring to when you say Chilly's forum, the "Inc S dev fix", and AntiVenom SDW? I went through 5-10 of the most recent pages on Everlov and didn't see any of these things, so would someone mind providing links?
Thanks
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2049902 this is chillybean's thread you can find AntivenomSDW in the other section of the OP (first post) the inc S dev fix can be found here http://d-h.st/1h6
ArslanQureshi said:
http://forum.xda-developers.com/showthread.php?t=2049902 this is chillybean's thread you can find AntivenomSDW in the other section of the OP (first post) the inc S dev fix can be found here http://d-h.st/1h6
Click to expand...
Click to collapse
Alright thanks a bunch. One more question though - what exactly is AntivenomSDW? Where can I find more information on it? Google is little help here.
jonatcer said:
Alright thanks a bunch. One more question though - what exactly is AntivenomSDW? Where can I find more information on it? Google is little help here.
Click to expand...
Click to collapse
its an flashable zip that completely wipes your device it is highly recommended to use whenever you flash a new rom it is developed by Chillybean
ArslanQureshi said:
its an flashable zip that completely wipes your device it is highly recommended to use whenever you flash a new rom it is developed by Chillybean
Click to expand...
Click to collapse
Alright thanks a bunch.
Would you, or anyone else still reading this thread, care to weight in on whether Evervolv or CB's rom (Which? Beanstalk?) is more stable?