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!
Related
Alright, I rooted my Nexus S 4G this guide. My phone was running 2.3.5 but I figured that these steps in Terminal wouldn't really change. When I flashed the "recovery-clockwork-3.0.0.5-crespo.img" it didn't install properly (I assume because it was out of date/wrong version) Anyway, I flashed this instead with no problems.
In my euphoria over solving my clockwork problem, I forgot to flash the "su-2.3.6.1-ef-signed.zip" and flashed the current version of MIUI. I am now stuck in a bootloop and I cannot enter recovery by using power+volume. I cannot turn the phone off. I can load the bootloader screen using Terminal while I plug it into my computer, but I don't know what to flash to fix the phone, and start over/end up with a Nexus running MIUI.
i dont know much about macs but you can flash the img files through fastboot.
imgs files are here
thank buglesspete
chewbz said:
i dont know much about macs but you can flash the img files through fastboot.
imgs files are here
thank buglesspete
Click to expand...
Click to collapse
I can handle the mac part if you can show me which files to flash in which order to make my phone work again.
Okay this will take your phone back to stock. Download the grj22 image files. When you open it up it should have like 4 or 5 img files. After that open up cmd and type in the commands buglesspete has in his first post. It should be under "return to stock" or sometime like that.
Sent from my Nexus S 4G using XDA App
XikkeN said:
Alright, I rooted my Nexus S 4G this guide. My phone was running 2.3.5 but I figured that these steps in Terminal wouldn't really change. When I flashed the "recovery-clockwork-3.0.0.5-crespo.img" it didn't install properly (I assume because it was out of date/wrong version) Anyway, I flashed this instead with no problems.
In my euphoria over solving my clockwork problem, I forgot to flash the "su-2.3.6.1-ef-signed.zip" and flashed the current version of MIUI. I am now stuck in a bootloop and I cannot enter recovery by using power+volume. I cannot turn the phone off. I can load the bootloader screen using Terminal while I plug it into my computer, but I don't know what to flash to fix the phone, and start over/end up with a Nexus running MIUI.
Click to expand...
Click to collapse
Just a general hint... if oyu own a Nexus S 4G, Crespo isn't the right codename to look for.. it's crespo4g. Get the cwm recovery from here and flash the 4G version via "fastboot flash recovery <recoveryname>.img": http://forum.xda-developers.com/showthread.php?t=988686
rentaric said:
Just a general hint... if oyu own a Nexus S 4G, Crespo isn't the right codename to look for.. it's crespo4g. Get the cwm recovery from here and flash the 4G version via "fastboot flash recovery <recoveryname>.img": http://forum.xda-developers.com/showthread.php?t=988686
Click to expand...
Click to collapse
I know. I linked to that thread in my first post. What step am I skipping to run MIUI without a bootloop?
XikkeN said:
I know. I linked to that thread in my first post. What step am I skipping to run MIUI without a bootloop?
Click to expand...
Click to collapse
I have no experience with the 4G version of this phone but I can tell your that bootloops are usually caused by failing permissions (fix permissions in cwm rec) or missing wipes before isntalling the actual rom.
So I'd go back to start, flash the 4g recovery, wipe everything (including "mount and storage"'s /boot and then flash MIUI for 4g from here afterwards.
Basically, that MIUI (and most other custom roms) includes superuser.zip aka root. No need to root the devices before, all you need is an unlocked bootloader.
rentaric said:
I have no experience with the 4G version of this phone but I can tell your that bootloops are usually caused by failing permissions (fix permissions in cwm rec) or missing wipes before isntalling the actual rom.
So I'd go back to start, flash the 4g recovery, wipe everything (including "mount and storage"'s /boot and then flash MIUI for 4g from here afterwards.
Basically, that MIUI (and most other custom roms) includes superuser.zip aka root. No need to root the devices before, all you need is an unlocked bootloader.
Click to expand...
Click to collapse
What he said, I always wipe 3x everything just to make sure it is a clean install. And some people will also suggest to let the rom boot up normally before flashing a different kernel.
Sent from my Nexus S 4G using XDA App
chewbz said:
What he said, I always wipe 3x everything just to make sure it is a clean install. And some people will also suggest to let the rom boot up normally before flashing a different kernel.
Sent from my Nexus S 4G using XDA App
Click to expand...
Click to collapse
wiping 3 times is senseless! and the kernel should be flashed right after the rom install!
oh and wiping the dalvik cache and chache after a rom-update is also senseless! the updater-script do this automatic!
Sent from my Nexus S using XDA Premium App
Borky_16 said:
wiping 3 times is senseless! and the kernel should be flashed right after the rom install!
oh and wiping the dalvik cache and chache after a rom-update is also senseless! the updater-script do this automatic!
Sent from my Nexus S using XDA Premium App
Click to expand...
Click to collapse
your assuming that the devs took the time to make sure to include that
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
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
Ever since I rooted my G2x I have not been able to flash a kernel. I have tried with Stock Gingerbread, CM7, Weapon, and Hellfire Sandwich. Usually I am trying to flash a Faux kernel, but I also tried a different one with Weapon.
I boot to CWM recovery and then flash the kernel and then reboot. I just get a black screen, no boot loop animation or anything, just black. I have to then pull the battery and wipe or restore a backup to be able to boot again.
Is there anything I'm missing that could fix this issue ? Thanks.
Are you wiping cache/dalvik first? Are you trying to install OC/UV?
Sent from my LG-P999 using xda premium
Yes, and yes. I just now tried it again. on Hellfire Sandwich using Faux Kernel 049 Beta Build 5(says Self Kang 3 only, but people in the Hellfire Sandwich thread are using it).
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