Database Develop

[Q] Stuck on LG screen [Solved]

Hello, this is my second post here though I visit this forum quite frequently.
I have a p990, and I have encountered a very strange problem with my phone:
Until yesterday, everything was normal, and every couple of weeks or so I installed a new/updated rom via CWM without any problem (usually).
Yesterday I installed the CM7 Kang from Ricardo, and this also worked well. However, when I tried to install my previous rom again (Gueste 3.1, after 3 wipes of course. The reason I didn't go back to a nandroid backup was because of problem in making the last backup) it got stuck on the 2ng LG screen. the buttons are lighted when I touch the screen, but even waiting 30 minutes doesn't change anything.
Since then, I tried to install many different roms (the latest CM7 nightly and some others), and all gave me the same problem. The only things that I've been able to do in order to boot successfully was to revert to an old backup that I had, or to install MIUI, which did work for some reason.
When I tried to install the same version of CM9 again, I always got a boot loop.
Any idea as to what could cause such a strange behavior and how can it be fixed?
Sorry for the long post, I just wanted to give as many details as possible, and I'll be happy to give more details if I can if there are things that I forgot.
Thanks,
Beorn

Beorn1 said:
Hello, this is my second post here though I visit this forum quite frequently.
I have a p990, and I have encountered a very strange problem with my phone:
Until yesterday, everything was normal, and every couple of weeks or so I installed a new/updated rom via CWM without any problem (usually).
Yesterday I installed the CM7 Kang from Ricardo, and this also worked well. However, when I tried to install my previous rom again (Gueste 3.1, after 3 wipes of course. The reason I didn't go back to a nandroid backup was because of problem in making the last backup) it got stuck on the 2ng LG screen. the buttons are lighted when I touch the screen, but even waiting 30 minutes doesn't change anything.
Since then, I tried to install many different roms (the latest CM7 nightly and some others), and all gave me the same problem. The only things that I've been able to do in order to boot successfully was to revert to an old backup that I had, or to install MIUI, which did work for some reason.
When I tried to install the same version of CM9 again, I always got a boot loop.
Any idea as to what could cause such a strange behavior and how can it be fixed?
Sorry for the long post, I just wanted to give as many details as possible, and I'll be happy to give more details if I can if there are things that I forgot.
Thanks,
Beorn
Click to expand...
Click to collapse
Try this: go to recovery > mounts and storage and wipe system, data and cache, and flash your rom.
If wiping system doesn't work neither, catch a logcat when the phone bootloops

markop90 said:
Try this: go to recovery > mounts and storage and wipe system, data and cache, and flash your rom.
If wiping system doesn't work neither, catch a logcat when the phone bootloops
Click to expand...
Click to collapse
This fixed the same issue for me.
Wiped everything and flashed CM9. Works great (but battery drain is incredible!!!)

Solved!
markop90 said:
Try this: go to recovery > mounts and storage and wipe system, data and cache, and flash your rom.
If wiping system doesn't work neither, catch a logcat when the phone bootloops
Click to expand...
Click to collapse
Thanks, I did this, and now I was able to boot again with Gueste 3.1 (I'd rather wait for a bit more stable and mature version of CM9).
Actually, I did this thing twice, and it still didn't help, and in the third time I tried to make a logcat (I'm rather new to this logcat thing), and while trying to boot and make a logcat at the same time it suddenly started workind
I just hope that it will stay good now, and that I won't have this problem again in future flashes...
Thanks!

[Q] Q - CM7.2.0 RC 1 - Random Reboots while charging into recovery menu

Hi,
Im using Cm7.2.0 RC1.
Every night during charge my OB reboots into the recovery mode. I didn't experience this problem with Zeus 4.02b or stock rom (shipped 2.2.0 and updated V20o).
It's a PITA, cause I use my phone as my alarm clock
Is there something like an error log? Does anybody already know a solution?
Tried google and this forum, no results

I had the same problem in an entirely different device but I know of some ways to possibly fix it. Check to see if you have the cyanogenmod tenkian kernel. Do this by opening up settings and scrolling down to the very bottom and hitting about phone. My other device randomly rebooted due to a problem with a kernel. What version of clockwork mod recovery do you have? Open up rom manager and update to the latest possible recovery by hitting "flash clockwork mod" at the top. If that doesn't fix it, boot into recovery and clear/wipe data (pain but usually fixes it) clear cache partition, and clear dalvik cache, then bootup and see. You can make a "logcat" file which gives details to devs about exactly what was happening when your device went wonky. I hope this helps
Sent from my LG-P970 using XDA, or something

vagubunt said:
Hi,
Im using Cm7.2.0 RC1.
Every night during charge my OB reboots into the recovery mode. I didn't experience this problem with Zeus 4.02b or stock rom (shipped 2.2.0 and updated V20o).
It's a PITA, cause I use my phone as my alarm clock
Is there something like an error log? Does anybody already know a solution?
Tried google and this forum, no results
Click to expand...
Click to collapse
reflash the file baby or the cm7 RC1 file babe

CyanogenMod 9 - Home Button & Lock Screen

[SOLVED]
Sorry I keep posting things to myself and solving it on my own after hours -__-.. I already struggled hours beforehand and was frustrated..
Anyways, I went to CMW recovery mod, deleted the back up that I backed earlier. And then format/reset to factory mod / wipe partition / cache / Dalv. Then I went to boot my device but after 10 minutes, it'd still be loading cyanogen.... so I reinstalled the CyanogenMod9. Wiped all the things I mentioned above again and when it loaded to OS, it worked..
I have no idea what was causing it.. probably the back up file interfering somehow? Because that's the only thing I got rid of and everything went back to normal.
_________________
Hey guys, I successfully installed CyanogenMod 9 on my Gingerbread 2.3.5.
Everything is great and slick. I used to use CyanogenMod 7.
Funny thing is, I enabled the lock screen (pattern) and it seems to be not working? I don't know if I'm missing something but after leaving my phone for good 20 minutes, I came back to turn on (from sleep) and it wasn't asking for lock screen pattern. I tried slide too, same.
Also, from my previous versions, whenever I was in setting or any app, if I were to press on Home Button it would bring my back to main screen. My Home button no longer does this. I have no idea what it does now, I press it and the phone vibrates (indicates that its been pressed) but no effect. I have to literately press Back like 5 times just to return to Main menu.
Is there something I'm suppose to enable or something?
Let me know, thank you
-Dan

danroh said:
[SOLVED]
Sorry I keep posting things to myself and solving it on my own after hours -__-..
Click to expand...
Click to collapse
lol, hate when that happens

Hey danroh,
I had same issue with home button and lockscreen and this steps fixed problem:
1) I accidentally downloaded Jelly Bean gapps instead of ICS version
2) Reinstalled CM9
3) Downloaded experimental build and flashed that over stable one
4) Flashed with proper ICS gapps
5) Factory reset/Data wipe, Clear Dalvik cache
6) Reboot
-----
Hit thanks if that worked for you

HElp ME
hard2play said:
Hey danroh,
I had same issue with home button and lockscreen and this steps fixed problem:
1) I accidentally downloaded Jelly Bean gapps instead of ICS version
2) Reinstalled CM9
3) Downloaded experimental build and flashed that over stable one
4) Flashed with proper ICS gapps
5) Factory reset/Data wipe, Clear Dalvik cache
6) Reboot
-----
Hit thanks if that worked for you
Click to expand...
Click to collapse
IT didnt wok, maybe because i dont have the needed gapps. Do you have a link?

danroh said:
[SOLVED]
Sorry I keep posting things to myself and solving it on my own after hours -__-.. I already struggled hours beforehand and was frustrated..
Anyways, I went to CMW recovery mod, deleted the back up that I backed earlier. And then format/reset to factory mod / wipe partition / cache / Dalv. Then I went to boot my device but after 10 minutes, it'd still be loading cyanogen.... so I reinstalled the CyanogenMod9. Wiped all the things I mentioned above again and when it loaded to OS, it worked..
I have no idea what was causing it.. probably the back up file interfering somehow? Because that's the only thing I got rid of and everything went back to normal.
Click to expand...
Click to collapse
Weirdly, my brother's Galaxy S had the same thing. Home button just would not work after installing CM9. Tried a few things, failed.
Then, I found this thread and I remembered that I'd backed up his old CM7 a while before. Deleted that backup in CWM Recovery, factory wiped/cache wipe, reinstalled CM9 and Gapps for 9 and boom, everything was fine.
EDIT:
Another thing to note is that when the home button wouldn't work, there was no Lockscreen either, just like you had. On first boot it didn't prompt me for a google account either, which it did do after I deleted the backup.

hard2play said:
Hey danroh,
I had same issue with home button and lockscreen and this steps fixed problem:
1) I accidentally downloaded Jelly Bean gapps instead of ICS version
2) Reinstalled CM9
3) Downloaded experimental build and flashed that over stable one
4) Flashed with proper ICS gapps
5) Factory reset/Data wipe, Clear Dalvik cache
6) Reboot
-----
Hit thanks if that worked for you
Click to expand...
Click to collapse
hey man!!..thnx for your guide...i w as actually in great trouble coz of this error..nd now its fixed!!...thnx a lot!!...

[Q] Aroma installer stuck

Hello,
I am a noob trying to install a rom with aroma installer. But now it has been stuck at the page where it says: The installation wizard has successfully installed *********. Press next to exit.
What do i do? Power off?

Is it definitely stuck? Aroma doesn't always recognise touch events very accurately, and I usually have to tap the "next" button a few times before it registers. Failing that, if it's finished installing whatever you flashed, you should be fine to reboot manually anyway.

Yes,i have tried to push the next button many times but nothing happens. It has been like this for 30 minutes now. The successfully installed text appeared very fast, a second or two maybe after the previous screen. So if it has installed the rom, it was def a fast install.
Anyway, is it safe to try to reboot, even if it was in the middle of the install? Rebot to recovery and try again?

Well, there certainly isn't anything else to be done besides rebooting. I don't know what you were trying to install - if it was a several-hundred-MB ROM, as most things that use Aroma are, you would expect it to take a while. Smaller things can be flashed very quickly. If it _did_ go wrong somewhere, there are a few things:
1. What recovery, and what version thereof, are you using?
2. Did you wipe data before using the installer?
3. Most of all, what were you trying to install? There might be some known issue with certain configurations.
I wouldn't necessarily expect a working OS when you reboot, depending on what you were trying to install and how badly things went wrong, but you should be able to get back into recovery easily enough.

Thank you for your quick reply.
1. I use the CWM recovery in this http://forum.xda-developers.com/showthread.php?t=1914394 thread, not the newest, but 5.5 something i believe.
2. Yes, wiped all data + dalvik.
3. I was trying to install rXTREME on my SGS III lte i9305.
I've rebooted now, and everything works perfect as the phone was before i tried to do the install. No brick. I also tried to flash it one more time, but stuck at the same place again. Rebooted fine at stock rom again. Maybe i should take this as a hint that someone else should be put at the steering wheel.. :laugh:
EDIT: forgot link above

Found out what the problem was.
In Aroma Installer i selected EFS backup both times. The third time i tried i did not do this. And everything went fine. Runs smooth.

my galaxy s3 international version got stuck at 30% of formatting\data partition while trying to flash s4 revolution 4.1 rom
what should i do?

jehad.drarjeh said:
my galaxy s3 international version got stuck at 30% of formatting\data partition while trying to flash s4 revolution 4.1 rom
what should i do?
Click to expand...
Click to collapse
This is I9305 forum is this your phone ??
This thread is about Aroma installer is that your problem ???
Suggest you read the basic faqs and guides first looks like from your post you are either flashing wrong rom to your phone or have hijacked a thread in the wrong forum ./
jje

[Q] Repair Galaxy Note N7000 SystemUI / TouchWiz home stopped working errors?

Hello everyone,
I've been literally 12 hours searching for possible answers on how to repair my Galaxy Note N7000 which from what I've concluded, has a problem that can be easily repaired but I've found nothing but limitations when I have a go at it. It doesn't seem to be bricked as I can still access recovery mode, download mode and it effectively boots, it's only giving me errors.
Here's what happened:
1) I tried rooting it using UnlockRoot PRO. Paid the PRO version, detected the device. Later I find it says the N7000 with 4.1.2 is not compatible so the rooting process was never completed, so I rooted it using Root_SuperSU.0.95.Only-signed and it worked just fine.
2) Everything worked fine, downloaded Andromizer to customize the phone.
3) Changed the DPI size to test it, then went to Developer Options and changed the Animation scales to 0.5 to make it all run faster.
4) Rebooted the device. Once I did, I got nothing but "SystemUI has stopped working" together with "TouchWiz home has stopped working errors".
I checked around the web and so far, what I've found (and tried) is this:
1) There seems to be a bug related to TouchWiz and the Animation Scale option (or perhaps the DPI size option in Andromizer). So I tried to do a wipe data / factory reset through recovery mode.
2) When trying the wipe data / factory reset through recovery mode, I rebooted the phone, only to find the SAME errors after I registered everything.
3) First option that came to mind was to wipe everything and immediatly reinstall the Official JellyBean 4.1.2 firmware (at this point I want to pretty much unroot the device as I didn't know it was going to give me so much trouble). When I tried that, I realized that SUDDENLY, Odin (nor Heimdall) are NOT detecting the phone in download mode. I'm guessing it's because USB Debugging is turned off but, I can't access the phone settings. It's my only logical conclusion, although it should be turned on given I could install PhilZ Custom Recovery later.
4) I search around the web and it says it's a driver problem. So I uninstall everything, run CCleaner, USBDeview to uninstall everything related to the Samsung Galaxy. Reboot. Install drivers again. Reboot. Plug booted phone and let Windows detect the device, installed successfully. Reboot in download mode. Let windows detect the device, installed successfully. Run Odin: DEVICE NOT DETECTED. (It does detect it while it's booted though, only it doesn't work for **** obviously).
I've literally tried everything. I've tried checking for a way to install the firmware via Recovery Mode instead of Download Mode. I've tried checking for a way to remotely access the device and mod the settings from there using ADB, and I get the same problem in ADB, doesn't detect the device.
Also tried to reset settings to normal via PhilZ Custom Recovery which I managed to install later.
Isn't there just a way to reset all settings to normal? Shouldn't a factory reset do this? How can I get SOMETHING to work and try to recover the phone? Any Aroma Recovery Script? Any way to mess with the system folder and modify settings manually via notepad or something since due to the SystemUI / TouchWiz home errors I can't access the phone settings?
I'm barely awake at this point. Can't believe I've stressed myself this much. Please help. This is beyond retarded.
Thank you,
Z

i had the same exact problem just few hours ago.....first of all you should boot into recovery mood by pressing vol up+ home button+lock button until samsung logo shows and then wipe all data/factory reset and wipe all cache partitions..........if that didnt fix it you should try rerooting it againg after re wiping

I read the post but it seems you have done a lot of things and nothing worked. So what is the situation right now? You can boot as normal but cannot get any icons or settings as sysUI and TW crashes?

Try installing GB ROM then wipe/cache first. If good, root GB ROM then do full wipe. Then test ROM for crashing.
If good then install JB rom and test. Let us know.

unable to enter phone setting ？ then just simply look for a secsetting.apk for ur version then replace it n set the permission rw-r--r--

You could use adb to modify your build.prop
Sent from my SGNote

Makrilli said:
You could use adb to modify your build.prop
Sent from my SGNote
Click to expand...
Click to collapse
Bwahahah, now I see why you guys enjoy calling newcomers "noobs".
It was a computer problem. I just reinstalled JB 4.1.2 from my netbook and it worked.
Weird as hell though, given that I updated my GT-N7000 to JB 4.1.2 through Odin in this computer and it never gave me any problems.
I AM going to learn some ADB / Android SDK though. I'd rather learn everything before something like this happens to me again.
I appreciate everyone's concern, and thank you all for it.

nice to hear that you had this one fixed

Glad to hear its working now.

n7000 touchwiz home stopped
Zardonic said:
Bwahahah, now I see why you guys enjoy calling newcomers "noobs".
It was a computer problem. I just reinstalled JB 4.1.2 from my netbook and it worked.
Weird as hell though, given that I updated my GT-N7000 to JB 4.1.2 through Odin in this computer and it never gave me any problems.
I AM going to learn some ADB / Android SDK though. I'd rather learn everything before something like this happens to me again.
I appreciate everyone's concern, and thank you all for it.
Click to expand...
Click to collapse
hi.... im having the same problem as yours. i dont know what to do

lulu2050 said:
i had the same exact problem just few hours ago.....first of all you should boot into recovery mood by pressing vol up+ home button+lock button until samsung logo shows and then wipe all data/factory reset and wipe all cache partitions..........if that didnt fix it you should try rerooting it againg after re wiping
Click to expand...
Click to collapse
I have tried to upgrade my touchwiz to the new one, but got the danger message, would clearing the cache help?
Sent from my SM-N910C using Tapatalk