I have a problem i am running the rom Bionix 2 - The Legacy Continues - RC1, i like it and everything but when ever i try to flash a kernerl from CM or Trinity my phone either doesent boot at all or if it does the is no haptic feedback, no internet and nothing is working plus the phone is super slow. Ive tried the install a different like CM7 but i get a message that say that installation aborted, Ive also tried Eaglesblood the rom flashes but when i flash the kernel to that rom it still doesent work. Someone please me i wan to overclock my phone. Im on 2.3.3 rooted and i have the newest CWM i think is 5.0.2.0 or something like that the blue one, IDK if that has anything to do with it
You could try a new ROM first then the kernel. When I flash I wipe data, cache, dalvik the format /system then install ROM then fix permissions then restart. When I add the kernel I want I wipe cache and dalvik then flash the kernel then fix permissions and restart. Some of these steps are extra but I have only had 1 problem before and that was because I didn't wipe dalvik before my kernel.
Also, is bionix based off of cm7? Even if it is some kernels might not work, they could have modified it enough that it makes cm7 kernels not work.
Sent from my LG-P999 using xda premium
I already everything that you explain the only thing that sounds unfamiliar is the "fix permissions" i dont know what that is. I dont know much about the rom here is a link to it http://forum.xda-developers.com/showthread.php?t=1080045 I tried flashing other rom but it doesent let me it say s instillation aborted when i try CM7 or anything else the only rom that i can install is bionix or eagles blood im new at this. I see kernels that allow you to oc to 1.5 an even some that let you get to 1.56 and i want my phone to be able to run them
Fix permissions is in rom manager (app for the phone) and cwm. Did you flash using nvflash or rom manager?
Sent from my LG-P999 using xda premium
I flash everything from CWM because some of these kernels cause my phone to boot loop. I fixed the permissions but still no luck
I flashed with NV Flasher
wgrant said:
Fix permissions is in rom manager (app for the phone) and cwm. Did you flash using nvflash or rom manager?
Sent from my LG-P999 using xda premium
Click to expand...
Click to collapse
Yea i flashed with nvflasher
Related
I'm currently using Eagleblood v1.8 without any problems...but when i installed Eagleblood v1.9 the phone does not start on boot up..after trying to boot it a minimum 5 times, then the phone out of nowhere boots up!
tried wiping data,cache,dalvik cache..
Any solutions to it?
didnt know that ver 1.9 was ready, Installing now will let ypo u know if I get the same problem.
Were you using 1.8 for 2.3.3, or 1.8 for 2.3.5?
Either way, since you said you already wiped your data, you might as well format /system. You'll need to reinstall your apps, but you'll have a clean install.
Wipe cache
Advanced --> Wipe Dalvik
Mounts and Storate --> format /system
Wipe data/factory reset
Flash rom
Flash gapps
Advanced --> fix permissions
Reboot
Same thing happened to me just go back to recovery do a full wype and flash the rom again and your good to go
mmapcpro said:
Were you using 1.8 for 2.3.3, or 1.8 for 2.3.5?
Either way, since you said you already wiped your data, you might as well format /system. You'll need to reinstall your apps, but you'll have a clean install.
Wipe cache
Advanced --> Wipe Dalvik
Mounts and Storate --> format /system
Wipe data/factory reset
Flash rom
Flash gapps
Advanced --> fix permissions
Reboot
Click to expand...
Click to collapse
I'm using 1.8 on 2.3.5
followed all of the above steps mentioned..
same boot problem...
gypsy214 said:
Same thing happened to me just go back to recovery do a full wype and flash the rom again and your good to go
Click to expand...
Click to collapse
i did try that...i tried factory resetting via privacy settings and performed wipe, still no use...
i also installed version 1.07 which has morfics kernel..v 1.07 works fine..tried installing 1.9 again...same problem
OK if u downloaded it from the directdownload, don't do that that one was messed up for me too, download the one from multi-upload and see if that works
Sent from my LG-P999 using XDA App
i found a weirdo solution to it...every time i have to install a fresh copy of morfics kernel to start the phone...
if i reboot...phone doesn't start....for god knows what reason!
it only starts after wiping cache,dalvik n flashing kernel!
Any better solution?
demonkicks said:
i found a weirdo solution to it...every time i have to install a fresh copy of morfics kernel to start the phone...
if i reboot...phone doesn't start....for god knows what reason!
it only starts after wiping cache,dalvik n flashing kernel!
Any better solution?
Click to expand...
Click to collapse
Hey DemonKicks, are you using a REFURBISHED G2X?? Have you done a warranty exchange at ANY TIME on your handset?
I am having problems with EaglesBlood 1.8, 1.9, and a couple other ROMS. I think that my REFURBISHED HANDSET is to blame!!
TeldenW said:
Hey DemonKicks, are you using a REFURBISHED G2X?? Have you done a warranty exchange at ANY TIME on your handset?
I am having problems with EaglesBlood 1.8, 1.9, and a couple other ROMS. I think that my REFURBISHED HANDSET is to blame!!
Click to expand...
Click to collapse
not a refurbished piece....anyways i cant exchange it.. warranty void
if you downdoaded the one from the direct download that one is messed up, try the one from multiupload
is this anywhere related to chip stability issue??
phone heats up
When in clockwork recovery go to mounts/storage then format/system then reflash Rom..find yourself a kernel while your at it ...try MORFIC's T15 or faux's 0.4.1 if you want to try undervolting..
Sent from my LG-P999 using xda premium
rymenigmatic said:
When in clockwork recovery go to mounts/storage then format/system then reflash Rom..find yourself a kernel while your at it ...try MORFIC's T15 or faux's 0.4.1 if you want to try undervolting..
Sent from my LG-P999 using xda premium
Click to expand...
Click to collapse
tried morfics t15 didnt work.....stock version cm7 faux's 0.4.1 works...thanks..
You got it...by the way 0.4.2 is out..
Sent from my LG-P999 using xda premium
Im running Oxygen 2.3.2 with whatever kernel came with that. I've been trying to flash Glados v2.2, it flashes properly in CWM but then, while rebooting, my phone gets stuck in the google boot screen, does anyone know how I can get it to boot properly?
FirePoncho86 said:
Im running Oxygen 2.3.2 with whatever kernel came with that. I've been trying to flash Glados v2.2, it flashes properly in CWM but then, while rebooting, my phone gets stuck in the google boot screen, does anyone know how I can get it to boot properly?
Click to expand...
Click to collapse
Flash another kernel instead. AFAIK, Oxygen 2.3.2 is Gingerbread-based ROM and GLaDOS v2.x is an Ice Cream Sandwich-based kernel. It will never boots.
I just tried Netarchy 1.40...same results
Sent from my Nexus S using XDA App
FirePoncho86 said:
I just tried Netarchy 1.40...same results
Sent from my Nexus S using XDA App
Click to expand...
Click to collapse
Is that a kernel for GB? If so try to wipe cache and dalvik cache before flashing.
First check the post where you're downloading the kernel from and make sure it works with your phone model/version. Oxygen is a GB rom so use a kernel for GB.
To flash just put the kernel file on your root directory of your SD and boot into clockwork. After that wipe cache, go into advanced and wipe dalvik, and then flash the kernel. There shouldn't be any problems after that.
OH and don't forget that the first boot always takes long so have some patience!
Hi.
today i flashed cm7.1 to my g2x, and later on i flashed the trinity kernel. when i flashed the trinity kernel, my g2x it wont boot to cm7, instead it will stay in a black screen. however, i can get into clockworld mod recovery. Any help??
Thanks.
did i actually brick it???
im not sure i am new to this phone...
Did you nvflash cwm? If so, Reflash cm7 and don't flash the new kernel
Sent from my Galaxy Nexus using xda premium
kwes1020 said:
Did you nvflash cwm? If so, Reflash cm7 and don't flash the new kernel
Sent from my Galaxy Nexus using xda premium
Click to expand...
Click to collapse
thanks for the reply.
I did use nvflash. should i wipe data and cache before reinstalling cm7?
thanks
yes, wipe data, cache, dalvic, and do a factory reset (which I think does the first two, but most everything sys to also do a factory reset from CWM)
P.s. Damn, how many other night owls are there on this forum?
thanks guys the phone works now after reinstalling and wiping.
honestly the best rom on the g2x is eaglebloodv2.5 based of cyanogenmod 7.1 with the trinity 15 uc/uv kernal. dont get me wrong i love cm but i can overclock to 1.5 per core with -150mv stable
hey so my g2x has this thing where each time i try to flash an update or zip after a clean install and initial boot, it won't boot up and continue to boot into CWR...So if i want to update my phone or rom I'll have to reflash the stock T-Mobile rom and then install CWR and then install any zip i need.... It's just kind of a hassle honestly.... any suggestions? and yes i have tried reflashing CWR many times using different programs to nvflash it correctly...
Are you flashing Harsh's kernel?
Which recovery are you using?
Sent from my LG-P999 using Tapatalk 2
i have harsh kernel flashed and i have tried flashing different versions of CWR but right now im on the experimental touch version
Don't use the touch version, it has bugs and doesn't support ext4.
And it's CWM standing for Clock Work Mod. I don't know where you're getting that R from.
No matter what ROM I'm on, or the compatible custom kernel I try to flash with whatever ROM I'm using at that time, I am still yet to have a successful flash of a kernel without rebooting the device only to have to pull my battery because it boots the first screen and then goes black and flashes the red LED, forcing me to restore to a backup I made prior.
I am running the most updated version of Liquidsmooth, and the most updated versions of CWM/TWRP. Any suggestions or possible causes? I always wipe cache/dalvik and fix permissions like I previously read was required in other threads.Thanks in advance!
StayingSober said:
No matter what ROM I'm on, or the compatible custom kernel I try to flash with whatever ROM I'm using at that time, I am still yet to have a successful flash of a kernel without rebooting the device only to have to pull my battery because it boots the first screen and then goes black and flashes the red LED, forcing me to restore to a backup I made prior.
I am running the most updated version of Liquidsmooth, and the most updated versions of CWM/TWRP. Any suggestions or possible causes? I always wipe cache/dalvik and fix permissions like I previously read was required in other threads.Thanks in advance!
Click to expand...
Click to collapse
What kernels did you flashed? And with what ROM?
If you are on liquid 2.2 I believe it need a aosp 3.4 kernel. I know the latest BMS kernel works. But the latest KT747 will not work unless you are using a new nightly of liquid 2.3. Be sure to wipe cache and dalvik cache after flashing but before rebooting.
Sent from my SCH-I535 using xda app-developers app
jmxc23 said:
What kernels did you flashed? And with what ROM?
Click to expand...
Click to collapse
Basically tried flashing any compatible kernel with the ROM I was running at the time. For example yesterday I tried flashing the KT747 kernel for Jellybean with the current ROM I'm running, which is the most recent Liquidsmooth 4.2.2 ROM. Still no success
Here is the latest liquid...
Nightly Builds 04/29/13 for d2att, d2spr, d2tmo, and d2vzw available on GooInsideMe
http://goo.im/devs/liquidsmooth/nightly/042913 These Builds Are Very STABLE!
View changes & bug fixes made to our source code here http://github.com/LiquidSmooth
This is quoted from liquid0624 in the liquid smooth thread.
Sent from my SCH-I535 using xda app-developers app
redKrome said:
If you are on liquid 2.2 I believe it need a aosp 3.4 kernel. I know the latest BMS kernel works. But the latest KT747 will not work unless you are using a new nightly of liquid 2.3. Be sure to wipe cache and dalvik cache after flashing but before rebooting.
Sent from my SCH-I535 using xda app-developers app
Click to expand...
Click to collapse
Sorry for taking forever to reply, I originally posted this on my lunch break and am finally out of work to reply freely. Anyways, I tried what you said, and downloaded the BMS 3.4 kernel that states is compatible with the version of Liquidsmooth 4.2.2 I am running. Let's just say I yet again had to restore twice once because it did exactly what I stated above, where it gives me the splash screen saying it's running the custom kernel and doesn't boot any further after the Galaxy S3 screen. The first time, I flashed it and then wiped cache/dalvik and fixed permissions before booting up like everyone says you need to do after flashing a kernel, no success.
Then, I read in the kernel's thread that there is no need to do that for this most up to date release, it says you just have to flash the kernel and reboot like with any other zip file. Well that didn't work either, and was forced to restore a backup a second time! What could the problem be?! I'm using the most updated version of TWRP, I'm on the most updated nightly of the Liquidsmooth ROM, I'm using a highly confirmed working and compatible kernel, and following the directions to the T! When it comes to flashing a different ROM, modem, rpm, backup, etc. I have no problem whatsoever. But trying to flash a kernel has never been successful for me so far
Any help from anyone else? It's frustrating that I've never been able to flash any kernels to any ROM I've ever run
Sent from my Samsung SCH-I535 running Liquidsmooth 4.2.2
Im no expert on any of this but this is what i would do. Odin back to stock ROM and reroot and unlock bootloader. Id do this cause i would want a clean slate so i know there is no previous kernel/rom files that may be effecting something. Make a new nandroid backup then reflash the rom ya want to use. Once booted up and everything is running, restart the phone and boot into recovery. Wipe the dalvik and cache like normal then flash the kernel. Hopefully that would take care of the problem.
Only other thing i can think of is to maybe wipe data/factory reset like 2 or 3 times and wipe the caches again and reinstall your current rom. Then flash the kernel. Other than that im out of ideas. Hopefully someone can get your problem solved!
Sent from my SCH-I535 using xda premium