Database Info

[THINKTNK] Getting faux GingerAOSP running on (broken?) G2X's!

So after trying, and trying, and trying some more to get Faux's Roms/Kernels to run on my G2x. I know a handful of other people are having the same issues.
Due to the lack of efforts on trying to get this to work other than "Get a new device" (which I refuse to believe that its the release date of the phones that can't do it) I would like to give a bit of info about what i've done so far, and start a think tank to get those of us who want to run this great rom a future where we CAN run it!
So that being said;
When faux first released the AOSP gingerbread and I flashed it, I HAVE had it running. Something between the most recent updates, and the Clockwork recovery updates caused me to not be able to. SO
I put my phone back to complete stock 100%
Then rooted the phone.
flashed the original clockwork recovery ( orange color one ) (EXTERNAL not INTERNAL)
copied over faux AOSP latest, gapps, and ext4 kernel
wiped data
wiped cash
wiped dalvik
format /system
installed from SD faux AOSP, then flashed gapps
rebooted
(went to LG screen, then went black, then lit-up, then black again)
pulled battery (went back into recovery)
I've tried full wipe/format then flashing aosp with and without gapps, and fixed permissions, and tried it without fixing permissions. NOTHING.
Any other ideas from anyone else who can't get it to work, or maybe couldn't but then figured out how?

check the md5 checksum of the ROM

worker1 said:
check the md5 checksum of the ROM
Click to expand...
Click to collapse
you wanna give me more info about how to do that and what it is?

javolin13 said:
you wanna give me more info about how to do that and what it is?
Click to expand...
Click to collapse
Md5 checksum is a unique string if numbers that you compare to ensure that you did not download a corrupt file.
Most rom cookers will provide an md5 that you can compare against.
Google md5 checksum for freeware to generate the number.

diablos991 said:
Md5 checksum is a unique string if numbers that you compare to ensure that you did not download a corrupt file.
Most rom cookers will provide an md5 that you can compare against.
Google md5 checksum for freeware to generate the number.
Click to expand...
Click to collapse
Thanks for the reply, i'll give this a check

So after downloading the 1.2.0 file again, and comparing the MD5 checksum's are both the same:
MD5 checksum: 295e1224a85794ec354e69906432c560

Mine worked right away. I went from stock to eb froyo to cm7 then to this. I did the usual wipes prior to installing. I'm using the ext4 red text recovery.
Not sure if it matters but try cm7 then wipe then install this rom?
G2x with faux AOSP

tackleberry said:
Mine worked right away. I went from stock to eb froyo to cm7 then to this. I did the usual wipes prior to installing. I'm using the ext4 red text recovery.
Not sure if it matters but try cm7 then wipe then install this rom?
G2x with faux AOSP
Click to expand...
Click to collapse
Testing now.

After trying, now it no longer goes to the black screen. I flashed cm7, then wiped ALL again, and reflashed AOSP ginger 1.2.1, rebooted, and it is stuck now at the LG screen and does nothing ( I waited for 10 minutes at the LG screen )

did you flash the ext4 kernel after you flashed the rom? if you have ext4 partitioned and you flash a rom with an ext3 kernel it will boot hang until you install a kernel that uses ext4...
easiest way to solve this is restore the stock nandroid, which uses ext3 and start all over with whatever you want, in your case from there wipe everything, flash rom, then flash whatever ext4 kernel you want...

JHaste said:
did you flash the ext4 kernel after you flashed the rom? if you have ext4 partitioned and you flash a rom with an ext3 kernel it will boot hang until you install a kernel that uses ext4...
easiest way to solve this is restore the stock nandroid, which uses ext3 and start all over with whatever you want, in your case from there wipe everything, flash rom, then flash whatever ext4 kernel you want...
Click to expand...
Click to collapse
Latest update:
I flashed CM7 back on the phone, using red cw recovery, then tried the latest faux cm7 kernel which has ext4 and it would not boot, it hung at LG, then went to a black screen.
did a full wipe again, and didn't flash the kernel, and the phone boots fine with cm7
so whatever the issue is, it seems to be only with things faux is cooking/building ( i've flashed EVERY rom for g2x and they all work fine except faux )

javolin13 said:
Latest update:
I flashed CM7 back on the phone, using red cw recovery, then tried the latest faux cm7 kernel which has ext4 and it would not boot, it hung at LG, then went to a black screen.
did a full wipe again, and didn't flash the kernel, and the phone boots fine with cm7
so whatever the issue is, it seems to be only with things faux is cooking/building ( i've flashed EVERY rom for g2x and they all work fine except faux )
Click to expand...
Click to collapse
When you say "full wipe" are you formatting /system as well?

sryan1983 said:
When you say "full wipe" are you formatting /system as well?
Click to expand...
Click to collapse
Yes that is correct full wipe;
wipe data
wipe cash
wipe dalvik
format /system

hmmm sounds like a kernel incompatibility of some sort... i dont have everything on my phone right now to try and recreate the situation or else id help you out... i will check tomorrow and if you have not figured it out i will see what i can do...
for now, nandroid back to complete stock and start from there and see if that fixes anything...

JHaste said:
hmmm sounds like a kernel incompatibility of some sort... i dont have everything on my phone right now to try and recreate the situation or else id help you out... i will check tomorrow and if you have not figured it out i will see what i can do...
for now, nandroid back to complete stock and start from there and see if that fixes anything...
Click to expand...
Click to collapse
Thanks for your input, i've already went to 100% stock, and rooted, put cw recovery (red) on and wiped everything, then flashed faux and gapps, and it didn't work.

intriguing. I was thinking it was a hardware change that did it. Have you tried the Trinity kernel? I am guessing that something must be changed in the hardware between ones that work and ones that don't. I have run every version of this ROM since day 1 without a single issue with booting. That includes all kernels as well.

javolin13 said:
Thanks for your input, i've already went to 100% stock, and rooted, put cw recovery (red) on and wiped everything, then flashed faux and gapps, and it didn't work.
Click to expand...
Click to collapse
I am in the EXACT same boat.
I've flashed every possible rom and it loads without fail. Anything faux and it locks at the LG boot screen.
Trinity kernel loads just fine as well as all the stock ones.

Wow I'm so dumb... after you flash the rom then do a wipe and then flash the kernel of your choice...

javolin13 said:
Thanks for your input, i've already went to 100% stock, and rooted, put cw recovery (red) on and wiped everything, then flashed faux and gapps, and it didn't work.
Click to expand...
Click to collapse
You need to flash 0.1.1 ext4 kernel if you are using CW recovery *RED*. Faux's AOSP rom only comes with ext3 built-in. You have to flash ext4 kernel after flashing rom then GApps.

JHaste
"Wow I'm so dumb... after you flash the rom then do a wipe and then flash the kernel of your choice"
-flash the ROM then do a wipe, then flash the kernel???? What was the point in flashing the ROM then?

[Q] Having slight problems with CROMI 3.0.4

First of all, this is an awesome rom and I'm very thankful to the developer.
My problem is that there is still some lag here and there and I've had a couple of random reboots. I'm wondering if I made a mistake flashing the rom.
I was on the .23 firmware. I flashed TWRP 2.2.2.3 because that's what it says in the how-to-root-JB guide and I was too impulsive to notice that in the cleanrom thread it says to flash latest TWRP. D: Does it matter?
After booting to recovery I flashed 3.0.3, wiped cache and dalvik, then booted to the rom to see it working fine. Went back to recovery, flashed 3.0.4, wiped cache and dalvik again. Everything looked fine except for the occasional slight lag and the random reboots.
If this is caused by using a wrong version of TWRP, how should I proceed?
I made a backup of stock rom before flashing; Do I restore stock, then flash the newest version of TWRP and then cleanrom? Would that be the safe way to fix the leftover lag and reboot?

furou said:
First of all, this is an awesome rom and I'm very thankful to the developer.
My problem is that there is still some lag here and there and I've had a couple of random reboots. I'm wondering if I made a mistake flashing the rom.
I was on the .23 firmware. I flashed TWRP 2.2.2.3 because that's what it says in the how-to-root-JB guide and I was too impulsive to notice that in the cleanrom thread it says to flash latest TWRP. D: Does it matter?
After booting to recovery I flashed 3.0.3, wiped cache and dalvik, then booted to the rom to see it working fine. Went back to recovery, flashed 3.0.4, wiped cache and dalvik again. Everything looked fine except for the occasional slight lag and the random reboots.
If this is caused by using a wrong version of TWRP, how should I proceed?
I made a backup of stock rom before flashing; Do I restore stock, then flash the newest version of TWRP and then cleanrom? Would that be the safe way to fix the leftover lag and reboot?
Click to expand...
Click to collapse
It probably doesn't make any difference but I would use the latest twrp as that guide is out of date.
You should not get any reboots at all. Most people are rock solid stable and so should you be.
Maybe your infinity can't cope with the overclocked kernel. Please reflash with the stock kernel for testing.

I think I read somewhere about a CROMI forum? If there is one, can someone point me to it?

sbdags said:
It probably doesn't make any difference but I would use the latest twrp as that guide is out of date.
You should not get any reboots at all. Most people are rock solid stable and so should you be.
Maybe your infinity can't cope with the overclocked kernel. Please reflash with the stock kernel for testing.
Click to expand...
Click to collapse
The correct way to do this would be to use the kernel switcher? Or reflash 3.0.3 + the patch?

furou said:
The correct way to do this would be to use the kernel switcher? Or reflash 3.0.3 + the patch?
Click to expand...
Click to collapse
Either is ok but kernel Installer is faster to do

Trying to get back to CM 10.0 from 10.1

I know the CM 10.1 nightly was experimental.
I flashed it, and it worked decently well enough.
What I failed to realize was that 10.1 flashes a new kernel on the phone, one that is incompatible with CM 10.0. I'm guessing the 4.2 base requires a new kernel.
So Fine, I've tried flashing the stock kernel on my phone, and then installing CM10, but no fish.
Any attempts I've made to change my kernel and then install CM 10 have resulted in my phone being stuck on the CM boot screen (the cyan circle animation)
Flashing CM10.1 nightly from twrp lets my phone boot up, because (i suppose) that rom installation just installs the compatible kernel again.
Can someone please help me figure out what I'm doing wrong with my kernel flashing?

taurius1 said:
I know the CM 10.1 nightly was experimental.
I flashed it, and it worked decently well enough.
What I failed to realize was that 10.1 flashes a new kernel on the phone, one that is incompatible with CM 10.0. I'm guessing the 4.2 base requires a new kernel.
So Fine, I've tried flashing the stock kernel on my phone, and then installing CM10, but no fish.
Any attempts I've made to change my kernel and then install CM 10 have resulted in my phone being stuck on the CM boot screen (the cyan circle animation)
Flashing CM10.1 nightly from twrp ets my phone boot up, because (i suppose) that rom installation just installs the compatible kernel again.
Can someone please help me figure out what I'm doing wrong with my kernel flashing?
Click to expand...
Click to collapse
What hboot r u on? You're full wiping right? And if you're on hboot 1.14 grab the boot.img our of the Rom zip you desire to flash and Fastboot flash it

a box of kittens said:
What hboot r u on? You're full wiping right? And if you're on hboot 1.14 grab the boot.img our of the Rom zip you desire to flash and Fastboot flash it
Click to expand...
Click to collapse
I'm on the 1.09 hboot. I haven't messed with my hboot ever. Should I be upgrading? I'll have to look it up.
I did try what you suggested.
I extracted the boot.img from CM10 stable for evita, flashed it via fastboot.
Then i rebooted into recovery, wiped my system, my cache, my dalvik cache, and did a factory reset.
Then I flashed CM 10.
After all this, still stuck on the cm boot animation. :3 I give it about 10 minutes before I decide its stuck. That is enough time, I think.

taurius1 said:
I'm on the 1.09 hboot. I haven't messed with my hboot ever. Should I be upgrading? I'll have to look it up.
I did try what you suggested.
I extracted the boot.img from CM10 stable for evita, flashed it via fastboot.
Then i rebooted into recovery, wiped my system, my cache, my dalvik cache, and did a factory reset.
Then I flashed CM 10.
After all this, still stuck on the cm boot animation. :3 I give it about 10 minutes before I decide its stuck. That is enough time, I think.
Click to expand...
Click to collapse
Ok no you want to stay on hboot 1.09 and redownload the latest cm10..and do these exact instructions
Wipe factory reset
System
Caches
Install Rom
Install gapps
I'm thinking you just had a bad download

a box of kittens said:
Ok no you want to stay on hboot 1.09 and redownload the latest cm10..and do these exact instructions
Wipe factory reset
System
Caches
Install Rom
Install gapps
I'm thinking you just had a bad download
Click to expand...
Click to collapse
I've done that. But just to be sure, I'm gonna try a fresh download once more. ^_^ Brb 10 minutes.

Curious what happened, as I think I may be having this same issue.

a box of kittens said:
Ok no you want to stay on hboot 1.09 and redownload the latest cm10..and do these exact instructions
Wipe factory reset
System
Caches
Install Rom
Install gapps
I'm thinking you just had a bad download
Click to expand...
Click to collapse
OOh that worked. Thanks a ton! ^_^
Probably was a bad download all three times I tried to download it before. :/ (I should probably buy a lottery ticket now :/ )
Now, Let me try installing my rooted stock rom. :3

Almost Same Problem
I have HTC One XL
-rooted
-unlocked
-bootloader unlocked
-hboot 1.14
-twrp recovery
I was also running the 10.1 expiremental (the first one). It was very buggy, so I tried out the newer experimental to see if the problems were fixed. The newer one was worse, so I decided to switch back to 10.0 nightly. I used fastboot to change the kernel to the one extracted from the 10.0 rom zip. I went to recovery and installed the 10.0 rom, but I DID NOT WIPE ANYTHING THE FIRST TIME. Either it slipped my mind, or I was thinking it wasn't necessary because I was still using a CM rom. The device would not boot, but instead of hanging on the cm animation screen, I'm stuck on the HTC logo screen. I went back to fastboot and did the kernel again and the phone automatically rebooted up correctly, however after a reboot i'm still stuck at the htc logo screen. It reminds me of tethered jailbreaks on iOS, lol. I may have to reflash the kernel every time I reboot. I tried stable, nightly, 10.1 nightly. no dice. any ideas?

lucasjohnsond said:
I have HTC One XL
-rooted
-unlocked
-bootloader unlocked
-hboot 1.14
-twrp recovery
I was also running the 10.1 expiremental (the first one). It was very buggy, so I tried out the newer experimental to see if the problems were fixed. The newer one was worse, so I decided to switch back to 10.0 nightly. I used fastboot to change the kernel to the one extracted from the 10.0 rom zip. I went to recovery and installed the 10.0 rom, but I DID NOT WIPE ANYTHING THE FIRST TIME. Either it slipped my mind, or I was thinking it wasn't necessary because I was still using a CM rom. The device would not boot, but instead of hanging on the cm animation screen, I'm stuck on the HTC logo screen. I went back to fastboot and did the kernel again and the phone automatically rebooted up correctly, however after a reboot i'm still stuck at the htc logo screen. It reminds me of tethered jailbreaks on iOS, lol. I may have to reflash the kernel every time I reboot. I tried stable, nightly, 10.1 nightly. no dice. any ideas?
Click to expand...
Click to collapse
Sounds like the best solution would be what I did, thanks to box of kittens.
Full wipe. (factory reset, system, cache)
Flash a download of CM to make sure you don't have a damaged copy.

taurius1 said:
Sounds like the best solution would be what I did, thanks to box of kittens.
Full wipe. (factory reset, system, cache)
Flash a download of CM to make sure you don't have a damaged copy.
Click to expand...
Click to collapse
Actually, I just remembered. If you're on the new hboot, you should be flashing the boot img through fastboot, and then installing the zip. Since you've been doing all that anyway, perhaps its time to just wipe everything and start over, step by step.
> download cm 10.0
> check md5 to make sure it's proper
> extract boot.img and flash it via fastboot
> reboot into recovery.
> wipe system, cache, dalvik cache, and factory reset
> transfer the rom and flash it via recovery
:/ I'm no expert here, but that's what I'd be doing now.

[Q] phone will not boot after installing any kernel

about a week ago i updated to the newest cm10.1 nightly with gapps 4.2. after flashing those i tried to flash leankernel. my battery was low and the phone turned off when rebooting after the leankernel flash. since then i cannot flash any kernel. i have to do a battery pull to get back into cwm recovery. once in recovery i can wipe data and reinstall cm 10.1 with the standard kernel. i have tried just about every combo of wiping cache, davlik, fix permissions. still not able to flash any kernel. could it have something to do with gapps 4.2 or the phone shutting off mid flash? if so does anyone know how to repair? i already flashed back to stock and rerooted re-unlocked, etc. thanks

and to clarify , it was gapps 4.2.2

Ive found that 3.4 based kernels work with some roms and not with others.
try an older build date its likely not 3.4 based.
or, if your trying a non 3.4 kernel and it wont boot, try a 3.4 kernel.

If you're trying to flash LeanKernel, what's the zip file you're attempting to flash? Also, what are you wiping prior to flashing the kernel?
Sent from my SCH-I535 using xda app-developers app

i tried the mastamoon 3.4 kernel with no luck . the rom i amrunning is the cm-10 nightly 2013-03-24. the leankernel version i am running is lk_s3vzw_aosp_jb42-v2.9. i wipe cache then wipe davlik then flash, it always worked with that procedure before, but since the problem i have tried wiping both after along with fixing permissions. before this issue it was simple as pi, wipe cache, davlik, flash, reboot .

You could always try twrp. Ha. It would make no sense why you couldn't install a kernel.
I would assume since you went back to Odin stock. It would flash factory kernel and give you a clean slate.
So unless cwm is outdated.... ?
Sounds very weird.

actually that is another variable that i didnt think of. cwm updated from 6.0.1 to 6.0.3 or something like that. but then again the original recovery i used after the clean slate was the ez recovery which used 6.0.1 stupid question, but how does twrp work? i always used cwm. i tried flashing twrp but cwm came up when i went to recovery when i tried using twrp?! that was before i did a stock recovery so it couldnt be possible that i am running both? should i delete cwm before i use twrp? if so how? if you dont feel like going into that much detail, i can search it.

i figured out twrp. never gave it achance. ill see if that does the trick

tried twrp. still the same thing going on. gonna go to bed now. ill check back tomorrow after work to see if there are any more ideas. thanks

Problem solved. I went into my internal SD via astro and deleted all old traces of cwm as well as ez unlock and ez recovery. I was getting a generic (showed setting icon instead of regular su icon)super user screen come up prior to that, after deleting those files the regular super user came back. Rebooted into recovery via twrp , cleared cache, Davlik, flashed lean kernel and it worked. What do you think the issue was? Lingering files from ez recovery? That weird su thing?

[Q] Stuck on the bootscreen

So guys, I've been at this for days.
I was originally using AK's kernel, TWRP Recovery and the official 44S ROM, but had issues with logging being disabled, so I fugured I'd go for the cm12 nightlies. I installed the latest AK kernel (102), updated TWRP to 2.8.4.1 and tried to dirty flash the 20150130 nightly, just to find that I'm stuck on the boot screen. I then on found about a firmware update that I installed after I wiped everything clean. Installed cm12 again and I was stuck in the same bootloop. I've even tried cm11 with the intention to OTA to cm12, but that had the same issue. That went through many different ROM's I've tried. I am kind of fed up by now and I would appreciate any input.
Thanks.

So you initially tried to dirty flash CM12 over CM11S? And you did that after flashing the AK kernel? If so you've got one major problem there: never dirty flash when switching ROMs or Android versions, you did both in one hit. And the minor problem: you're meant to flash a kernel after flashing a ROM, if you do it the other way around the stock kernel from the ROM zip just overwrites the custom kernel.
Anyway, I think your best bet is to flash the stock images with fastboot, see section 8 of my guide thread .
Transmitted via Bacon

I can flash any 11S rom, but the problem is installing and booting into cm12. But I think I'll just wait for 12S as it should come up soon. Would be cool if I had access to nightlies though.
Well' you can't win them all.

There's no reason why you shouldn't be able to flash the nightlies? Did you update your firmware appropriately before flashing CM12?
Transmitted via Bacon

@timmaaa I am also wondering why does he face bootloop issues every time. If there is no essential change in the latest OTA update (like updated bootloader) maybe his recovery doesn't wipe /system properly.
Hey, @BigWaxx, did you manually format /system in TWRP before flashing CM12? If yes, maybe give a try with PhilZ recovery.
tetakpatalked from Nexus 7 flo

tetakpatak said:
@timmaaa I am also wondering why does he face bootloop issues every time. If there is no essential change in the latest OTA update (like updated bootloader) maybe his recovery doesn't wipe /system properly.
Hey, @BigWaxx, did you manually format /system in TWRP before flashing CM12? If yes, maybe give a try with PhilZ recovery.
tetakpatalked from Nexus 7 flo
Click to expand...
Click to collapse
It's definitely possible, the firmware is the most likely culprit at this stage though.
Transmitted via Bacon

I have updated the firmware properly before that. Also no other custom ROM runs - not only cm12. I've tried cm11, OmniROM, TGM, BlissPop and temarek.
I have also tried CWM, but not PhilZ. I made sure to format everything - even internal storage. I've tried both F2FS and EXT4 as filesystems for /system.
I will try PhilZ though.
Cheers.