I write data, cache, and dalvik cache. But none of my soft keys work, non voodoo it does though.. I tried the stock voodoo kernel that comes with it and the new ones
I may be a total noob here (but trying to help). I've found that quirky things sometimes respond to "Fix Permissions" in CWM
Related
O.K. I'm still a noobie at this so just a simple question. I currently have Bionix-V running and want to flash Bionix-V 1.2.1. Once the rom is on the internal sdcard and I reboot in recovery do I simply install zip from sdcard, or do I have to wipe data?
Its always good to wipe data/factory reset, its one of the CWM options, then flash, BUT before you flash, backup your apps through Titanium Backup and you'll be good to go, after you flash bionix v 1.2.1, your phone will take a while to boot up, when it does, let it stand alone for 10 min, then hold the power button to reboot so it clan clear aany bugs when it was flashing, then restore all your apps through titanium, and then your set!
actually Bionix should wipe by itself, no need to choose that option in CW.
ok i attempted to install BAMF Remix v1.6. is there a way to confirm that this was flashed properly? i still have bloatware like blockbuster etc. i think i missed something along the way.
is it possible i just did a factory reset?
thanks
markkal123 said:
ok i attempted to install BAMF Remix v1.6. is there a way to confirm that this was flashed properly? i still have bloatware like blockbuster etc. i think i missed something along the way.
is it possible i just did a factory reset?
thanks
Click to expand...
Click to collapse
How did you flash it? Did you do it through ROM Manager? Did you wipe data and cache? Something's not quite right, the bloatware should be gone.
i am having the same issue. are you also missing stuff like the notification power control widget?
io flashed mine from cwm and wiped everything.
phatjames167 said:
i am having the same issue. are you also missing stuff like the notification power control widget?
io flashed mine from cwm and wiped everything.
Click to expand...
Click to collapse
Hmm. Count me in on this one too then: http://forum.xda-developers.com/showthread.php?t=1069980
count me in as part of the galactically stupid. (worse than nube)
go to here http://forum.xda-developers.com/showthread.php?t=1027804
download and install
BAMF Remix v1.6:http://tinyurl.com/3wkpmh3
MD5: CF461768DBC8A729CB7D28B97D5B8717
download and install
BAMF Remix Patch 1.6.2: http://tinyurl.com/3ntawj6
MD5: d45d597d42d40ca31319786cfb9450dc
i was only installing BAMF Remix Patch 1.6.2 not realinzing it is only a patch to BAMF Remix v1.6!!!
i booted into ClockworkMod
everything now appears to be as expected for the ROM
thanks for your help.
it looks like this worked. when it first boots though the wallpaper is black with a red streak but then changes to the default wallpaper from stock. is that normal?
That got me closer to everything being 100%. I installed Remix 1.6 and 1.6.2 and I noticed changes like the battery indicator and the market being black (very nice, btw), but I still have bloat & the notification bar is missing. Wiped Dalvic Cache both times, wiped data fully when I installed the main BAMF 1.6 at the start of this.
aerojad said:
That got me closer to everything being 100%. I installed Remix 1.6 and 1.6.2 and I noticed changes like the battery indicator and the market being black (very nice, btw), but I still have bloat & the notification bar is missing. Wiped Dalvic Cache both times, wiped data fully when I installed the main BAMF 1.6 at the start of this.
Click to expand...
Click to collapse
I had this same exact issue. The cause of mine was installing through ROM Manager. I was wiping everything that should be just like you are it sounds. The fix I found was rebooting into recovery and flashing manually. There is an option in ROM manager to reboot into recovery. Once you are into recover wipe data/cache three times. Wipe cache partition three times. Wipe Davlik Cache(Under advanced menu) three times. I usually wipe three just to be sure everything is clean before I flash. Flash 1.6. Now load 1.6.3(since it's out now) onto the SD card. Boot into recovery again, wipe cache partion and davlik cache three times. Install 1.6.3.
devindpotts said:
I had this same exact issue. The cause of mine was installing through ROM Manager. I was wiping everything that should be just like you are it sounds. The fix I found was rebooting into recovery and flashing manually. There is an option in ROM manager to reboot into recovery. Once you are into recover wipe data/cache three times. Wipe cache partition three times. Wipe Davlik Cache(Under advanced menu) three times. I usually wipe three just to be sure everything is clean before I flash. Flash 1.6. Now load 1.6.3(since it's out now) onto the SD card. Boot into recovery again, wipe cache partion and davlik cache three times. Install 1.6.3.
Click to expand...
Click to collapse
I did the install through the ROM manager, so I'm hoping your solution works out. I'll give it a try this evening. Thanks for the suggestion!
aerojad said:
I did the install through the ROM manager, so I'm hoping your solution works out. I'll give it a try this evening. Thanks for the suggestion!
Click to expand...
Click to collapse
Actually I just looked and 1.6.3 is an entire rom instead of a patch so you can skip flashing 1.6. And just flash 1.6.3 after wiping data/cache/davlik cache.
devindpotts said:
Actually I just looked and 1.6.3 is an entire rom instead of a patch so you can skip flashing 1.6. And just flash 1.6.3 after wiping data/cache/davlik cache.
Click to expand...
Click to collapse
Thank you very much, your suggestions were exactly what I was looking for. Now have that full BAMF Remix experience
aerojad said:
Thank you very much, your suggestions were exactly what I was looking for. Now have that full BAMF Remix experience
Click to expand...
Click to collapse
Not a problem at all, enjoy.
devindpotts said:
I had this same exact issue. The cause of mine was installing through ROM Manager. I was wiping everything that should be just like you are it sounds. The fix I found was rebooting into recovery and flashing manually. There is an option in ROM manager to reboot into recovery. Once you are into recover wipe data/cache three times. Wipe cache partition three times. Wipe Davlik Cache(Under advanced menu) three times. I usually wipe three just to be sure everything is clean before I flash. Flash 1.6. Now load 1.6.3(since it's out now) onto the SD card. Boot into recovery again, wipe cache partion and davlik cache three times. Install 1.6.3.
Click to expand...
Click to collapse
I had the same issue and this worked for me. I just reflashed 1.6.3 directly from CWR (after wiping everything 3x) and everything worked correctly (notification widget, etc.)
thanks for the help
I am glad I found this, I had this same issue and it was driving me nuts. I'm reinstalling now and hopefully everything just comes out perfect.
I am adding this to my list of why I don't like RM.
Is it possible to pull out the kernel from JT's CM7 and then flash it?
I can't seem to find it in the CM7 rom package, and not even sure if it is possible. Somebody mentioned that it should be titled kernel_update, as that is usually the case, but I can't seem to find that.
I am on the OTB, and I would like to try out the original kernel.
One more thing, in case the kernel cannot be extracted, if I wipe cache and dalvik and then reinstall the rom with no data wipe will I be good? I've never installed a rom without data wipe and I just want to be sure that installing a rom twice on top of itself won't make it have some problems or bog down. If it will, I guess I can just bite the bullet and wipe everything and reinstall to get the kernel.
I reflashed the rom after a cache and dalvik wipe and everything is working great.
AlgorithmX said:
I reflashed the rom after a cache and dalvik wipe and everything is working great.
Click to expand...
Click to collapse
I'll give it a shot.
Couple people posted that they thought the included kernel had less hangs than OTB. Anybody have a similar experience?
They are both great kernels but I had to reflash the rom because my phone got stuck in headset mode after the latest voodoo control plus update. I think JT's currently has a few more gpio fixes.
I think your best bet would be to reflash the rom without wiping anything. You would get the original kernel while keeping your settings and data. If you were so technically inclined I believe the kernel is in the boot.img file in the zip but it is above me to try to make that its own flashable file.
Hi there. I want to switch from ICS Passion v12 with kernel 3.1.10 ICS Passion Kissed by ICS to ICS Euphoria RC2.1.
What steps are involved in doing this? Can I just flash one on top of the other? What kernels/roms would i need to flash first? Thanks
Reboot in Recovery
Goto MOUNTS & STORAGE >> FORMAT SYSTEM
Wipe Data / Factory Reset
Wipe Cache + Dalvik Cache
Flash the file. You may need to flash file twice if there is bootloop due to CWM version mismatch.
Reboot.
Reboot once again after you see everything settled and you are on your homescreen.
thanks!
Little Problem
Hello i installed rom ICS_Euphoria_RC2.1 with the kernel ICS_Kiss_v5.1_CWM
i wipe data/ factory reset
i wipe cache & Delvik
then installed kernel ICS_Kiss_v5.1_CWM got in to a little boot loop
but was able to get to Recovery.
Then installed Rom: ICS_Euphoria_RC2.1
Everything is working fine, except every time i call someone and use speaker phone i hear everyone fine, but apparently all the hear is really loud static. They say that it sound like i am in the free-way and wind is blowing straight in to the microphone.
If i make a call normal with no speaker it works fine. Any ideas on what to do or how to fix this? Thanks
Howdy partners, not sure if I should have started my own thread...let me know if that is proper procedure please. I've already read the recent boot loop thread by vlmaadir t=2558286, but I'm unsure as to the applicability of the solutions in that thread to my problem.
I'm in a similar situation as the vlmaadir, except I've been running the most recent stock ROM (UCMD8) and have rooted via framaroot and flashed the AJKv4.9 - NoSwap Kernal successfully around 12/5/2013. Of course I've yet to do a backup of the OS or apps, but pics/vids/contacts were all recently backed up.
About two weeks ago I started noticing random reboots, but wasn't really sure what to make of that, never any boot looping though. Well this morning the phone was working when i woke (phone alarm raised me from the dead on time) and had approx. 70% battery, but by the time I got to work, the phone had apparently powered off.
When I powered it back on, it took a several minutes to boot up (normally around 45sec-1min), once booted the battery showed about 10-15% (in the red). The few apps I opened worked (naked browser, outlook), but were a bit laggy. I decided to restart the phone from the regular power menu to see if that would help the laggy/battery issue, and upon restart I am now solidly stuck in my 1st android boot loop!!!
I can boot into CWM recovery, but have yet to do any wiping as I wanted to seek a bit of advice here 1st.
If anyone has any pointers, I'm listening.
Thanks!
I would 1st try a wipe cache and wipe dalvik cache from cwm recovery and see if it will reboot.
If it doesn't then u will probably have to wipe data/factory reset from cwm recovery and then reboot.
If ya have been runnin good for a while with AJ's kernel, then a rogue app may be the cause of ur problem.
R u tweakin anything in the kernel through stweaks apk ?
Sent from my SAMSUNG-SGH-I747 using Tapatalk
4-2ndtwin said:
I would 1st try a wipe cache and wipe dalvik cache from cwm recovery and see if it will reboot.
If it doesn't then u will probably have to wipe data/factory reset from cwm recovery and then reboot.
If ya have been runnin good for a while with AJ's kernel, then a rogue app may be the cause of ur problem.
R u tweakin anything in the kernel through stweaks apk ?
Sent from my SAMSUNG-SGH-I747 using Tapatalk
Click to expand...
Click to collapse
Thanks 4-2.
If I have to go wipe data/factory reset, should i have to re-flash the rom and kernel?
I've been running the AJK for about a month, no tweaks. Like I said in the OP, I had noticed some random reboots in the past few weeks and at some point over Christmas day, when I was doing a good bit of pic/video work on my phone, it came up with a message that the internal storage memory was low. I knew this wasn't the case, at least as far as the entire internal memory, which had around 3 gigs free. Just a few strange things I've noticed since having AJK in place.
Are there any other good kernels for stock 4.1.2? AJK seemed to be the go-to of main stock and custom ROM folks.
I did a cache wipe, but when I enter the dalvik wipe confirm menu, the output shows
E:unknown volume for path [/sd-ext]
and when I confirm yes, wipe dalvik, the screen goes black, then the phone restarts into the boot loop.
Any one know what is up here?
^^
Doing and wipe data/factory reset in the cwm recovery will just return the Stock MD8 to just full stock, as if u first installed it through Odin or att official, Except u will still have the AJ kernel. There is no need to reflash the rom as u say.
But if u cannot find an app that is causing the problem, then a complete Odin flash to Stock MD8 should help in the troubleshooting.
---------- Post added at 07:40 PM ---------- Previous post was at 07:37 PM ----------
wolfboogie said:
I did a cache wipe, but when I enter the dalvik wipe confirm menu, the output shows
E:unknown volume for path [/sd-ext]
and when I confirm yes, wipe dalvik, the screen goes black, then the phone restarts into the boot loop.
Any one know what is up here?
Click to expand...
Click to collapse
The "E:unknown volume for path [/sd-ext]" is the norm from what i remember.
But not sure why choosing to wipe dalvik cache resulted in a bootloop.
Have ya tried the wipe data/factory reset yet ?
Just did a wipe data/factory reset and I got out of the boot loop! Now I just have to set the phone up like I had it once again! Boo!
Thanks for the input 4-2!!!
Glad ya got it going. :good:
If any other problems arise, just let us know. There are several good members around that are glad to help.