Develop Bugs

Flashing a ROM won't work

So I wanted to flash the FNV AoSP ROM on my Galaxy Nexus GSM. First off al I flashed the 4.2 takyu version and rooted it with SuperSU. After that I flashed the recovery with Clockwork 6.0.1.5 after that I did the following things:
- Wipe data/factory reset
- Mounts and storage > Format /system
- Wipe cache
- Wipe dalvik
- Flashed ROM fnv_20121119_003_maguro.zip
- Flash 4.2 gapps
Am I doing something wrong?

When you say, won't work what do you mean?
Does the recovery not flash the file? If so, what error does it say?
Does it not boot after what seems to be a successful flash in recovery? Do you see the bootanimation?

cupfulloflol said:
When you say, won't work what do you mean?
Does the recovery not flash the file? If so, what error does it say?
Does it not boot after what seems to be a successful flash in recovery? Do you see the bootanimation?
Click to expand...
Click to collapse
It flashs the files and all but it gets into a bootloop. I see the costum bootanimation of the ROM, but it keeps playing and it won't start up. After some time the screen goes black, but it's not off, because if I hold down power it won't turn on so I have to pull battery.

CheesieOnion said:
It flashs the files and all but it gets into a bootloop. I see the costum bootanimation of the ROM, but it keeps playing and it won't start up. After some time the screen goes black, but it's not off, because if I hold down power it won't turn on so I have to pull battery.
Click to expand...
Click to collapse
Your ROM name seems to show that it is a recent build. A quick search around, the last official FNV ROM I see was uploaded in September. The Gerrit, Github, Twitter, and threads here and on another site seem to have been untouched for quite some time.
Of course I am a little out of the loop, so perhaps I am missing something. As devs often post things in IRC, or in other non-official channels. Did you get this ROM from a trusted spot?
That said, it could be a ROM issue perhaps.

CheesieOnion said:
So I wanted to flash the FNV AoSP ROM on my Galaxy Nexus GSM. First off al I flashed the 4.2 takyu version and rooted it with SuperSU. After that I flashed the recovery with Clockwork 6.0.1.5 after that I did the following things:
- Wipe data/factory reset
- Mounts and storage > Format /system
- Wipe cache
- Wipe dalvik
- Flashed ROM fnv_20121119_003_maguro.zip
- Flash 4.2 gapps
Am I doing something wrong?
Click to expand...
Click to collapse
it probably doesnt need the gapps. try reflashing, but without the gapps. don't wipe anything.

cupfulloflol said:
Your ROM name seems to show that it is a recent build. A quick search around, the last official FNV ROM I see was uploaded in September. The Gerrit, Github, Twitter, and threads here and on another site seem to have been untouched for quite some time.
Of course I am a little out of the loop, so perhaps I am missing something. As devs often post things in IRC, or in other non-official channels. Did you get this ROM from a trusted spot?
That said, it could be a ROM issue perhaps.
Click to expand...
Click to collapse
I got the rom from the topic here on XDA. It is the build from 19 november.
simms22 said:
it probably doesnt need the gapps. try reflashing, but without the gapps. don't wipe anything.
Click to expand...
Click to collapse
In the instuctions in the ROM-topic it says it needs them and I also need them to use.

CheesieOnion said:
I got the rom from the topic here on XDA. It is the build from 19 november.
In the instuctions in the ROM-topic it says it needs them and I also need them to use.
Click to expand...
Click to collapse
install the gapps from the play store. you can flash without them, besides the ones that you cant get from the play store are included. you can try it, or just stay in your bootloop, its your call.

CheesieOnion said:
I got the rom from the topic here on XDA. It is the build from 19 november.
Click to expand...
Click to collapse
Ah, my bad I didn't realize it was picked up by someone else, I see that now (which I thank you for the heads up that it is back in production). I was just making sure you weren't flashing something that wasn't ready for public use, and that it was a real ROM.

[Q] CM10 Stable - Completely Unstable and Broken

Hi there, I'm new to the forum but have been rooting for about a year. Here is my problem...
I was running stock firmware on my SGS3 and went through the standard cm10 root/rom install process. I flashed CMW with Odin, booted to recovery, installed cm10, jb gapps, cleared cache and delvik cache and rebooted. All the above processes worked fine and once it boots into JB, nothing seems to work. My home button does nothing, the top status bar is blank, no wifi, no keyboard (the process just crashes when I attempt to type).
I know this isn't an issue with CM10 on the SGS3 as this works for most people but does anyone have any ideas on how to remedy this? This may be a unique issue as I can't seem to find anyone else experiencing this.

Also...
I should also mention that I've tried a restore in recovery, reinstalled cm10, blah blah blah, and same results. I've also tried the cm10.m2 roms with the identical results. After reboot I don't even get the welcome wizard. It just boots right into the blank, default JB home screen and starts popping up process failure errors. I can navigate around (though the home button doesn't work) but can't use the keyboard etc.
Am I missing something? Is there a way for me to do a clean restore and try again?
Some technical info:
ClockworkMod Recovery v5.8.4.7
cm-10.0.0-d2att.zip
gapps-JB-20121130-signed.zip

Did you do a complete wipe? Data, cache, Davlik , System and then install cm10.
Coming from stock you need to fully wipe.
Sent from my SAMSUNG-SGH-I747 using xda premium

Machoscrawn said:
I should also mention that I've tried a restore in recovery, reinstalled cm10, blah blah blah, and same results. I've also tried the cm10.m2 roms with the identical results. After reboot I don't even get the welcome wizard. It just boots right into the blank, default JB home screen and starts popping up process failure errors. I can navigate around (though the home button doesn't work) but can't use the keyboard etc.
Am I missing something? Is there a way for me to do a clean restore and try again?
Some technical info:
ClockworkMod Recovery v5.8.4.7
cm-10.0.0-d2att.zip
gapps-JB-20121130-signed.zip
Click to expand...
Click to collapse
Your clockworkMod is out of date to run CM10 & the gapps. Upgrade to the latest clockwork mod, then the latest CM then the latest Gapps and you should be good to go.

dynamiclynk said:
Did you do a complete wipe? Data, cache, Davlik , System and then install cm10.
Sent from my SAMSUNG-SGH-I747 using xda premium
Click to expand...
Click to collapse
Thanks for the reply. This is what I did...
(Main cwm menu) -wipe cache partition
(Advanced) -wipe dalvik cache
+++go back+++
-reboot system now
Is there something additional I should clear?

Kweli87 said:
Your clockworkMod is out of date to run CM10 & the gapps. Upgrade to the latest clockwork mod, then the latest CM then the latest Gapps and you should be good to go.
Click to expand...
Click to collapse
Thanks for the reply,
How do i update to the latest clockworkMod? Do you happen to have a URL? I think I found the latest 6.something, but they all seem to be in .iso format.

You can't go from stock rom to CM10 without clearing factory reset thing in CWM.. I don't know the exact text string it uses but it should be right on top of clearing cache.. It looks like you only cleared cache and flashed a new rom.

i386W7 said:
You can't go from stock rom to CM10 without clearing factory reset thing in CWM.. I don't know the exact text string it uses but it should be right on top of clearing cache.. It looks like you only cleared cache and flashed a new rom.
Click to expand...
Click to collapse
Sorry I may have missed mentioning that. The first thing I did was the -factory restore/reset

If updating CWM doesn't help, I'd recommend re-downloading the CM10 zip and verifying the MD5 hash. It could be that the download got corrupted somehow...

goodtimes50 said:
If updating CWM doesn't help, I'd recommend re-downloading the CM10 zip and verifying the MD5 hash. It could be that the download got corrupted somehow...
Click to expand...
Click to collapse
Two questions:
1) What is the best way for me to update cwm?
2) I've seen this MD5 hash recommendation here and there. I have no idea what that means. How would I "verify the MD5 hash".

Machoscrawn said:
Two questions:
1) What is the best way for me to update cwm?
2) I've seen this MD5 hash recommendation here and there. I have no idea what that means. How would I "verify the MD5 hash".
Click to expand...
Click to collapse
Flash one of the rooted stock ROMs. Preferably an ICS one since you are on an older cwm. Wipe data, cache, dalvik. Download ROM manager from the play store. Update your recovery to the latest through that. Than flash back to cm10.

BAM1789 said:
Flash one of the rooted stock ROMs. Preferably an ICS one since you are on an older cwm. Wipe data, cache, dalvik. Download ROM manager from the play store. Update your recovery to the latest through that. Than flash back to cm10.
Click to expand...
Click to collapse
Ok thanks! I'm going to give that a shot and see how it goes.

Machoscrawn said:
Ok thanks! I'm going to give that a shot and see how it goes.
Click to expand...
Click to collapse
Ok so I tried flashing a stock rooted ICS ROM and now I'm stuck on the Samsung logo boot screen. Here is the method I tried, using Odin. http://forum.xda-developers.com/showthread.php?t=1739426
I used the "Bell Image (This works with Canadian Virgin Mobile SGH-I747M) - Old Image I747MVLALH1 (ICS 4.0.4)"
After flashing I booted into the stock recovery and cleared the cache partition then rebooted. Still stuck on the Samsung boot screen.
UPDATE: I just let it sit on the Samsung logo boot screen and it eventually loaded into ICS.

Machoscrawn said:
Two questions:
1) What is the best way for me to update cwm?
2) I've seen this MD5 hash recommendation here and there. I have no idea what that means. How would I "verify the MD5 hash".
Click to expand...
Click to collapse
1) I believe Rom Manager (from the Play Store) can do this.
2) Basically an MD5 value is generated when the file is created and is usually listed on the download page (on get.cm look for "md5sum" right under the download link for each build). There are apps that create an MD5 value from the file that you download and compare against the original to ensure that it's intact. If the values don't match, something's wrong with the file. Check out FastSum (there are lots of others out there too).

goodtimes50 said:
1) I believe Rom Manager (from the Play Store) can do this.
2) Basically an MD5 value is generated when the file is created and is usually listed on the download page (on get.cm look for "md5sum" right under the download link for each build). There are apps that create an MD5 value from the file that you download and compare against the original to ensure that it's intact. If the values don't match, something's wrong with the file. Check out FastSum (there are lots of others out there too).
Click to expand...
Click to collapse
Ok cool. Well i have downloaded ROM Manager but when I try to flash the latest recovery and it gives me a list of devices, mine isn't there. The only S3 listed is "Galaxy S3 (MetroPCS)". The list itself looks incomplete, maybe only 20 devices listed. I've rebooted the phone since installing ROM Manager but the list still only shows the one SGS3.

Machoscrawn said:
Ok cool. Well i have downloaded ROM Manager but when I try to flash the latest recovery and it gives me a list of devices, mine isn't there. The only S3 listed is "Galaxy S3 (MetroPCS)". The list itself looks incomplete, maybe only 20 devices listed. I've rebooted the phone since installing ROM Manager but the list still only shows the one SGS3.
Click to expand...
Click to collapse
Try to download GooManager and select the Flash Roms option, it will prompt you, select *Find one for me* reboot into recovery try to wipe/reset and reinstall the ROM and gapps and see if it works

wally3614 said:
Try to download GooManager and select the Flash Roms option, it will prompt you, select *Find one for me* reboot into recovery try to wipe/reset and reinstall the ROM and gapps and see if it works
Click to expand...
Click to collapse
Ok I tried the Goomanager route. When I'm in recovery doing the install of the rom, I get a FAILED error right after it tries updating partition... I've tried installing from internal and external sd with the same results...
I've attached a screenshot. Well I attempted to with my webcam, hopefully it's semi-readable.

Machoscrawn said:
Ok I tried the Goomanager route. When I'm in recovery doing the install of the rom, I get a FAILED error right after it tries updating partition... I've tried installing from internal and external sd with the same results...
I've attached a screenshot. Well I attempted to with my webcam, hopefully it's semi-readable.
Click to expand...
Click to collapse
Well at least you have the proper twrp definitely try and re download the ROM, carefully make sure it is absolutely the correct ROM(I rushed once, thought I was sure n dl'd the wrong one and bricked my older s3) if u have the slightest break during DL this can happen. I KNOW it is frustrating but worth it in the end

wally3614 said:
Well at least you have the proper twrp definitely try and re download the ROM, carefully make sure it is absolutely the correct ROM(I rushed once, thought I was sure n dl'd the wrong one and bricked my older s3) if u have the slightest break during DL this can happen. I KNOW it is frustrating but worth it in the end
Click to expand...
Click to collapse
Alright, I downloaded the latest stable (the only one) build of CM 10 from get.cm. Removed the current version from my internal sd and tried the process again. Same error...
So again, I'm now using GooManager, TeamWin Rocovery v2.3.1.0, CM10 Stable. Doing a factory reset, then wiping system, then install cm10, this is where it fails.
Any way that I can restore everything on my phone completely to stock and start from scratch? Anything else you/anyone can recommend?

Machoscrawn said:
Alright, I downloaded the latest stable (the only one) build of CM 10 from get.cm. Removed the current version from my internal sd and tried the process again. Same error...
So again, I'm now using GooManager, TeamWin Rocovery v2.3.1.0, CM10 Stable. Doing a factory reset, then wiping system, then install cm10, this is where it fails.
Any way that I can restore everything on my phone completely to stock and start from scratch? Anything else you/anyone can recommend?
Click to expand...
Click to collapse
If youre looking to completely start over. Just grab an unrooted stock .tar from one of the links somewhere around here, put your phone in download mode and let it flash. Clean slate.

GNex stuck in boot loop since 4.3 flash

Few hours before this post I flashed a rooted version of android 4.3 from the thread by "Carlos_Manuel". However, following that the supersu was not working I flashed the supersu binaries over the ROM from TWRP. Since then, it is stuck in boot loop at the Google Logo. Tried flashing PA, Sourcery, CM but nothing seems to work. What should I do?

Flash the official Google image: http://forum.xda-developers.com/showthread.php?t=2376687

check dreams rom thread and see my post there
Sent from my Galaxy Nexus using Tapatalk 4 Beta

Fix it by flashing factory images! do a full wipe, you can get imprtant stuff from your Nexus by using adb pull commands!
Users was blaming me when they screwed their Nexus with the root files!
I can successfully even flash old root files and no bootloops but ofc. root wont work if using those old root files.

OP, did you factory reset between ROM flashes?

beekay201 said:
OP, did you factory reset between ROM flashes?
Click to expand...
Click to collapse
pulling files then flashing 4.2.2 stock image to start fresh

NyPlaya513 said:
Ok, I am paranoid and want to be sure about this. I am in the same boat as the OP. I have a 32gb toro on twrp 2.5. I am under the impression that flashing the stock images will flash my sdcard partition and I want to pull some files if that is the case. Is there anyway to pull the files or am I stuck and need to start fresh.
Click to expand...
Click to collapse
You cant use the stock images they are for gsm not toro/cdma, have to use a custom zip only one is that light speed one in development right now I am waiting for muzzys but, full wipe, flash rom, gapps, supersu.

NeoMagus said:
You cant use the stock images they are for gsm not toro/cdma, have to use a custom zip only one is that light speed one in development right now I am waiting for muzzys but, full wipe, flash rom, gapps, supersu.
Click to expand...
Click to collapse
nvm pulling files

If you tried wiping just cache/dalvik after the flash I dont know there may be another way to get it to boot or not but yeah the factory image will start it over fresh and get you out of it

NeoMagus said:
If you tried wiping just cache/dalvik after the flash I dont know there may be another way to get it to boot or not but yeah the factory image will start it over fresh and get you out of it
Click to expand...
Click to collapse
nvm got the toolkit to pull files via adb for me on my parallels

agent47er said:
Few hours before this post I flashed a rooted version of android 4.3 from the thread by "Carlos_Manuel". However, following that the supersu was not working I flashed the supersu binaries over the ROM from TWRP. Since then, it is stuck in boot loop at the Google Logo. Tried flashing PA, Sourcery, CM but nothing seems to work. What should I do?
Click to expand...
Click to collapse
"just wipe data" in recovery after flashing, solve bootloop issue

dexviajiboy said:
"just wipe data" in recovery after flashing, solve bootloop issue
Click to expand...
Click to collapse
thanks for your help.. but I ended up flashing factory image of 4.3 which fixed the problem. Also I wnted to ask if you know of any 4.3 kernels that have implemented high performance audio mod. So far I have tried Faux and Hybrid but both dont have it.

agent47er said:
thanks for your help.. but I ended up flashing factory image of 4.3 which fixed the problem. Also I wnted to ask if you know of any 4.3 kernels that have implemented high performance audio mod. So far I have tried Faux and Hybrid but both dont have it.
Click to expand...
Click to collapse
i dont think there's any kernel for now, give it some time and you'll get one

[Q] TORO 4.3 problems

I have a Verizon GNex, Toro. I was running PA 3.60 4.2.2 and all was fine, but I go the bug for 4.3
I flashed FTL 4.3 rom for toro, had it booted up the first time, and was loading apps and setting up my phone, when it froze after about 15 minutes and I had to pull battery.
I tired to reboot but it got stuck on Google logo for 10-15 each time, nothing would happen, so I wiped and tried to restore my old backups, all of them failed, i try to restore everything but data and is it says successful in TWRP (v2.5.0.0) but when I go to reboot system it hangs again on the Google logo for long periods of time, I've waited upwards of 15 minutes.
I still have the PA 3.60 files in my downloads so I tried to wipe and flash it back on my phone, again it hangs at the Goggle logo and wont go past it.
I can get to the bootloader, I can get to TWRP, but nothing else.
Any advice on what I should try next?
Do I need to flash a stock image? I'm at work at the moment so I will have to wait till later to do it, but at home I have a Mac, which makes things that much more confusing for me.

mhport2 said:
I have a Verizon GNex, Toro. I was running PA 3.60 4.2.2 and all was fine, but I go the bug for 4.3
I flashed FTL 4.3 rom for toro, had it booted up the first time, and was loading apps and setting up my phone, when it froze after about 15 minutes and I had to pull battery.
I tired to reboot but it got stuck on Google logo for 10-15 each time, nothing would happen, so I wiped and tried to restore my old backups, all of them failed, i try to restore everything but data and is it says successful in TWRP (v2.5.0.0) but when I go to reboot system it hangs again on the Google logo for long periods of time, I've waited upwards of 15 minutes.
I still have the PA 3.60 files in my downloads so I tried to wipe and flash it back on my phone, again it hangs at the Goggle logo and wont go past it.
I can get to the bootloader, I can get to TWRP, but nothing else.
Any advice on what I should try next?
Do I need to flash a stock image? I'm at work at the moment so I will have to wait till later to do it, but at home I have a Mac, which makes things that much more confusing for me.
Click to expand...
Click to collapse
Did you flash the new bootloader before you tried to flash the 4.3 ROM? I've heard that it is unnecessary but I would highly recommend using the bootloader designed for the current version of Android. What were the exact steps you took to flash the new 4.3 ROM?
I'm beginning to suspect that people are either getting bad downloads or the data cables being used are not working properly which is causing bad flashes. This is just speculation, but I am using the data cable supplied with my phone and have yet to have one single problem flashing the 4.3 ROM.

jaizero said:
Did you flash the new bootloader before you tried to flash the 4.3 ROM? I've heard that it is unnecessary but I would highly recommend using the bootloader designed for the current version of Android. What were the exact steps you took to flash the new 4.3 ROM?
Click to expand...
Click to collapse
No, I did not flash a new bootloader, I followed the FTL steps he posted except for wiping cache and davilk cache.
Instructions:
1) Download ROM:
Dev-Host: http://d-h.st/s7b
2) Download Gapps:
Dev-Host: http://d-h.st/UDe
Source: http://forum.xda-developers.com/show...38&postcount=1
*** Goo.im Gapps for 4.2.2 did not work. Use other Gapps at your own risk! ***
3) Download SuperSU:
Dev-Host: http://d-h.st/h3h
4) Backup Device
5) Flash the zips in order
Click to expand...
Click to collapse

jaizero said:
Did you flash the new bootloader before you tried to flash the 4.3 ROM? I've heard that it is unnecessary but I would highly recommend using the bootloader designed for the current version of Android. What were the exact steps you took to flash the new 4.3 ROM?
I'm beginning to suspect that people are either getting bad downloads or the data cables being used are not working properly which is causing bad flashes. This is just speculation, but I am using the data cable supplied with my phone and have yet to have one single problem flashing the 4.3 ROM.
Click to expand...
Click to collapse
I downloaded the files directly from chrome on the phone. Is that a problem? That is how I have done most of the ROM's I have ever downloaded.

Try this..
Boot into recovery
Factory reset
Wipe dalvik/cache
Install ROM
Install Gapps
Install SU zip
Reboot
The first boot can take a few minutes so be patient. You'll sit at the "Google" screen for a minute or two then the "android" boot animation for 2-5 minutes. I also wouldn't recommend restoring any backups as I ran into some issues doing this. If you can get the ROM to boot do a fresh install of all your apps from the Play Store.

I never flashed the bootloader and I have had zero problems with flashing and booting 4.3. I dont know what people are doing to have issues. One thing I can think of is after flashing everything and you select restart device, it gives you this option that doesnt usually show up. I cant think of the wording. Something about "erasing flash something or other". there is a whole list of "No" and one line of "erase....". Are people clicking the option to erase and get problems from it? I always just select to go back and it restarts.

jsgraphicart said:
I never flashed the bootloader and I have had zero problems with flashing and booting 4.3. I dont know what people are doing to have issues. One thing I can think of is after flashing everything and you select restart device, it gives you this option that doesnt usually show up. I cant think of the wording. Something about "erasing flash something or other". there is a whole list of "No" and one line of "erase....". Are people clicking the option to erase and get problems from it? I always just select to go back and it restarts.
Click to expand...
Click to collapse
The OP is using TWRP which is what I used and I got no such options.
---------- Post added at 11:47 AM ---------- Previous post was at 11:45 AM ----------
mhport2 said:
I downloaded the files directly from chrome on the phone. Is that a problem? That is how I have done most of the ROM's I have ever downloaded.
Click to expand...
Click to collapse
It could be, I can't speculate on that as I have only downloaded the files to my PC.

jaizero said:
The OP is using TWRP which is what I used and I got no such options.
Click to expand...
Click to collapse
Oh. I never use TWRP. I have never liked it. I dont know how TWRP handles stuff then.

jaizero said:
Try this..
Boot into recovery
Factory reset
Wipe dalvik/cache
Install ROM
Install Gapps
Install SU zip
Reboot
The first boot can take a few minutes so be patient. You'll sit at the "Google" screen for a minute or two then the "android" boot animation for 2-5 minutes. I also wouldn't recommend restoring any backups as I ran into some issues doing this. If you can get the ROM to boot do a fresh install of all your apps from the Play Store.
Click to expand...
Click to collapse
I have tried this a few times now, it just hang at the Google Logo, I have waited 15 minutes now, that shouldn't be right.

mhport2 said:
I have tried this a few times now, it just hang at the Google Logo, I have waited 15 minutes now, that shouldn't be right.
Click to expand...
Click to collapse
My next suggestion is going to be a /system wipe. Not sure If you want to go this route but if you choose to (at your own risk)..
Boot into recovery
Factory reset
wipe dalvik/cache
wipe /system
install ROM
install Gapps
install SU zip
reboot
As a warning if this doesn't work you will not have a booting system. You will be forced to reinstall an older factory image via fastboot.
Do you have a 4.2.2. ROM saved on your SD card that you can install? It might be a good idea to get a booting system first before trying anything else from this point on.

Still nothing works, I formatted all data and do not have an OS at this point.
When I get home I will adb sideload a 4.2.2 rom and gapps (Most likely Mmuzzy for the time being) from my mac and install it in TWRP. I've done this before and it should work and get me out of this mess.
Thanks for your help.

mhport2 said:
Still nothing works, I formatted all data and do not have an OS at this point.
When I get home I will adb sideload a 4.2.2 rom and gapps (Most likely Mmuzzy for the time being) from my mac and install it in TWRP. I've done this before and it should work and get me out of this mess.
Thanks for your help.
Click to expand...
Click to collapse
did it work? i am also having this problem but when i go into my bootloader it tells me my device is tuna even though its a toro if that matters. and to make things wierder when i try to adb it says i dont have fastboot even though i had it less than 3 hrs ago when i was flashing the rom.(supernova) it worked then i shut off and rebooted the next morning and i just get stuck at the google logo. if anyone can help me i would appriciate it.

[Q] CM 9.1 crashes continiously

Dear Community,
this is my first post on XDA-devloppers.
I ask you for help as y have a serious promlem with CM 9.1 on my xperia arc.
I flashed CM on my phone using the latest stable rom downloaded from the official cyanogenmod website (cm-9.1.0-anzu.zip)
Everything worked perfectly and i was delightet.
Unfortunately, after two days my phone crashed.
By crashed i mean that it first reacted very slow then froze. After this, the screen went black (backlight on) an then dark.
no button could get me back to lockscreen.
then suddenly the phone rebootet.
this happened every time about one minute after booting my phone.
As the problem didn't seem to get away i decided to reflash it:
wipe SD
delete davlik cache
reseting to factory
and then istalling the same rom and gapps from zip
everything worked fine again, but after one day i got the same problem again.
what can I do to fix this?
I would appreciate any kind of help
and excuse me if this isn't the right forum (search also, didn't help)
sincerly,
PraetorAce

You might want to try FXP's release:
http://forum.xda-developers.com/showthread.php?t=1356685
僕のLT18iから送られてきた

popthosegaskets said:
You might want to try FXP's release:
http://forum.xda-developers.com/showthread.php?t=1356685
僕のLT18iから送られてきた
Click to expand...
Click to collapse
thank you!
but which version should I take and how do I flash it? (just copy on SD and then install from zip?)

PraetorAce said:
thank you!
but which version should I take and how do I flash it? (just copy on SD and then install from zip?)
Click to expand...
Click to collapse
You can try the nightly versions if the stable doesn't work for you.
Take out the boot.img inside the ROM zip and flash with fastboot. Then put ROM zip onto SD card and flash with CWM.
僕のLT18iから送られてきた

I tried a few roms and it didn't work.
with the latest nightley version from cyanogenmod website gapps wans't installed properly and my home button didn't work.
and the roms I tried from the link you gave me abortet the installation.
i always flashed the kernel (boot.img) via flashtool and then used CWM to: 1 wipe davlic cache, 2 reset to factory and 3 install from zip
will it maybe work with odin (or is odin only for samsung devices?)
thnx

PraetorAce said:
I tried a few roms and it didn't work.
with the latest nightley version from cyanogenmod website gapps wans't installed properly and my home button didn't work.
and the roms I tried from the link you gave me abortet the installation.
i always flashed the kernel (boot.img) via flashtool and then used CWM to: 1 wipe davlic cache, 2 reset to factory and 3 install from zip
will it maybe work with odin (or is odin only for samsung devices?)
thnx
Click to expand...
Click to collapse
Odin is for Samsung devices only. If CM9.1 doesn't work for you then you might want to try CM10.
僕のLT18iから送られてきた