Database Users

[Q] NEED HELP!!! Boot/loading screen wont stop!!!

A few days ago my phone just started randomly flashing the boot screen. At the time I just thought it was annoying and was bogged down or something but would soon be gone.
But it hasn't!!
My phone is rooted with the gfree method and I was running this ROM
http://forum.xda-developers.com/showthread.php?t=1401556
The problem is this: anytime I'm not giving my phone a command and the screen is about to timeout, the boot animation starts up and loads to the home screen. At that point I have a few as ones to unlock.it and use my phone which will work.just like normal or if I don't respond soon enough it will start over and flash it again.... It repeats.continuously. If a webpage is loading or I am backing up something and don't keep touching the screen it will stop.the task and go into this "continuous boot mode"...
I've wiped everything, tried other roms.... It does it right after the intial setup everytime and won't go away...

I believe you're answering yourself. If you wiped everything and flashed different ROMs, but problem persisted - it means that your phone is most likely faulty.

k15goose said:
A few days ago my phone just started randomly flashing the boot screen. At the time I just thought it was annoying and was bogged down or something but would soon be gone.
But it hasn't!!
My phone is rooted with the gfree method and I was running this ROM
http://forum.xda-developers.com/showthread.php?t=1401556
The problem is this: anytime I'm not giving my phone a command and the screen is about to timeout, the boot animation starts up and loads to the home screen. At that point I have a few as ones to unlock.it and use my phone which will work.just like normal or if I don't respond soon enough it will start over and flash it again.... It repeats.continuously. If a webpage is loading or I am backing up something and don't keep touching the screen it will stop.the task and go into this "continuous boot mode"...
I've wiped everything, tried other roms.... It does it right after the intial setup everytime and won't go away...
Click to expand...
Click to collapse
The question is, what other roms have you tried? I seem to get the same problems on sense 3.5 roms which is why i am not using them currently. If this is happening on a clean install of cm7 or miui as well as sense then you may genuinely have a problem.
Things to try: full wipe system/data/cache/dalvik/sdcard
reboot recovery after wipe to start clean. verify md5sum of the rom you are flashing to eliminate possibility of error. dont install any of your own apps for 1 to 2 days and then if you still have the problem then you may want to unroot and try to get a warranty exchange if at all possible. Good Luck!

Dumb question, but how exactly do I verify that?? And yes it does seem to be with all the 3.5 sense Roms so I tried miui and a sense 3.0... While that did eliminate that problem another unique one showed up...the market wouldn't download anything! No apps.. it would always say due to an error "(-101)"
Just for the record, I rooted it a few weeks ago and the miui and energy 3.5sense both worked fine for at least a week.. does that help in any way??

k15goose said:
Dumb question, but how exactly do I verify that?? And yes it does seem to be with all the 3.5 sense Roms so I tried miui and a sense 3.0... While that did eliminate that problem another unique one showed up...the market wouldn't download anything! No apps.. it would always say due to an error "(-101)"
Just for the record, I rooted it a few weeks ago and the miui and energy 3.5sense both worked fine for at least a week.. does that help in any way??
Click to expand...
Click to collapse
Well that's good to hear that it isn't happening on all roms. I usually fix the market problems by doing a data wipe and then force close it. Usually will start being able to download after a fc. To check the md5sum on a file download mand5 free from the market and check the file that way.
Sent from my HTC Glacier using xda premium

[Q] Noob MT4G SLOW AFTER UNROOT

I couldnt find any thread with my problem so i makin my own, Im sorry if someone else already post it. Ok here is my problem I bought my phone already rooted and it worked well, i install other roms with the clockwork and all was ok, one day it started to shut down by itself, so i tought that a wipe will fix, thing is that the wipe never started, the progress bar never moved, so i took off the batery, then i tried to start the phone again and it just didnt start, I decided that all I can do was to install the M151MG RUU and it worked the phone turned on, but now it crashes, its extremely slow, everythin force closess, so i try to install it again and it just didint worked. I install an app to monitor what is using the memory, and kill all tasks and it just didnt helped. What can I do to start fresh other than reseting to factory because that doesnt works it doesnt start and finally it crashes. Hope you guys can help me and sorry for the bad english

do you mean pd15img?
--sent from my glacier.

Possibly another case of failed eMMC or HW failure. Might be caused by overheating. PD15IMG wipes everything clean and installs a stock 100% compatible ROM, so if it didn't solve your problem - it looks like a HW problem.

Jack_R1 said:
Possibly another case of failed eMMC or HW failure. Might be caused by overheating. PD15IMG wipes everything clean and installs a stock 100% compatible ROM, so if it didn't solve your problem - it looks like a HW problem.
Click to expand...
Click to collapse
His english is poor, so in case he is using a translator...
Jack_R1 is saying that if the PD15IMG.zip doesn't fix it then you have a hardware issue. Meaning your phone is broken.
Sorry :-(

So if it is a Hardware issue, what can i do to fix it? Is hard to change the emmc? how can i know wich one to buy? You know the day it broke it was really hot, today it started after a flash with the RUU file but it crashed and died, now if turn it on it loops on the mytocuh scree (the second one).

ivancito130188 said:
So if it is a Hardware issue, what can i do to fix it? Is hard to change the emmc? how can i know wich one to buy? You know the day it broke it was really hot, today it started after a flash with the RUU file but it crashed and died, now if turn it on it loops on the mytocuh scree (the second one).
Click to expand...
Click to collapse
Uuuh, no. Its not fixable outside of an HTC lab. Sorry :-(

[Q] Conversion/flashing CM9 using Racks dualboot for SD

Here's my issue. I was using the latest racks prepared boot for CM9. The one dated 5/1 or so. I decided I wanted to try my hand at converting a nightly and flashing it on my own. I've been having nothing but trouble with the conversion process and I have no idea what I'm doing wrong.
And I've tried a few different ones of Eyeballers nightlies, but I'm always getting the same error. I just tried it using the Android script and the windows script and I'm getting different issues in each.. When I try to convert in dos, i'm getting really tiny files and most of the time it gives me a bunch of lines with items not found.
I'm really new at this but I've looked and was unable to find any answer to why this wouldnt be working or even what i could be doing wrong. I can get into the recovery, I install the converted nightly and when I try to boot into it I just get a black screen, I waited a few minutes to make sure it wasnt just something with the the device or just a first time thing but nothing happened.
on the android version I get the error attached. Im not sure how else to say whats going wrong but if someone has some suggestions I'd really appreciate it.

You might get a better response if you post this question in Racks conversion thread. Here:
http://forum.xda-developers.com/showthread.php?p=25648626
Sent from my Nook Color running ICS and Tapatalk

unfortunately I am not able to until I reach the 10 post threshold. but rather than spam to hit that. I figured I'd try this first. Thanks though. Hopefully he'll still see this.

kontam said:
unfortunately I am not able to until I reach the 10 post threshold. but rather than spam to hit that. I figured I'd try this first. Thanks though. Hopefully he'll still see this.
Click to expand...
Click to collapse
I will put a post there for you.

kontam said:
Here's my issue. I was using the latest racks prepared boot for CM9. The one dated 5/1 or so. I decided I wanted to try my hand at converting a nightly and flashing it on my own. I've been having nothing but trouble with the conversion process and I have no idea what I'm doing wrong.
And I've tried a few different ones of Eyeballers nightlies, but I'm always getting the same error. I just tried it using the Android script and the windows script and I'm getting different issues in each.. When I try to convert in dos, i'm getting really tiny files and most of the time it gives me a bunch of lines with items not found.
I'm really new at this but I've looked and was unable to find any answer to why this wouldn't be working or even what i could be doing wrong. I can get into the recovery, I install the converted nightly and when I try to boot into it I just get a black screen, I waited a few minutes to make sure it wasnt just something with the the device or just a first time thing but nothing happened.
on the android version I get the error attached. Im not sure how else to say whats going wrong but if someone has some suggestions I'd really appreciate it.
Click to expand...
Click to collapse
1.Are you using latest version of script 1.3?
2.Did you try the terminal emulator for running script?
3.Did you try to delete and extract again the folders of the c2dsd in case something went wrong during first extraction?

thanks for posting there for me.
RASTAVIPER said:
1.Are you using latest version of script 1.3?
2.Did you try the terminal emulator for running script?
3.Did you try to delete and extract again the folders of the c2dsd in case something went wrong during first extraction?
Click to expand...
Click to collapse
1. I updated both scripts and was still getting issues.
2. if you mean the one on android then yes, thats what I was using. I also tried it using the cmd on windows.
3. I've tried that at least two times with each including redownloading all aspects of it to make sure that wasn't the case.

kontam said:
thanks for posting there for me.
1. I updated both scripts and was still getting issues.
2. if you mean the one on android then yes, thats what I was using. I also tried it using the cmd on windows.
3. I've tried that at least two times with each including redownloading all aspects of it to make sure that wasn't the case.
Click to expand...
Click to collapse
Not sure about the windows issue. I'll have DizzyDen take a look at that. But with the Android version, i'll take a look at that in a little while. Looks like it's another mistake on my end. Mkimage is dependent on 'libmusl.so' which I did not include in the tools folder. I overlooked this tidbit because I had "BOTBREW" installed on my system so it never complained about linking to it.
Sorry for all the problems. I'll try and have a fix ASAP. Your feedback is much appreciated. Can't fix things if I don't know if their broken or not.
Thanks,
Racks
EDIT: Fixed I believe. Please try the v1.3a for the Android script.

I'm looking into the DOS version as we speak....

You guys are all really amazing for helping me out.
And as probably mentioned before by rasta Im not sure what the issue is but theres still something not quite gelling for the version. I took another screen to hopefully help you identify where its going weird. It is a little different but its still that crc cd issue. Im not going to try to flash it to see if it works, only because Im pretty certain that won't do it. But I really appreciate you looking into it.
and for clarity I also get a very similar if not exactly the same message when It trys to do the gapps as well. (using the 4/29 signed gapps)
And I decided now to try flashing the rom. it worked. Fantastically! though the boot animation is freezing. I dont even care about that since its actually working again. Awesome. But.. now im having those same issues as Rasta with the gapps. I flashed them and when I went to reboot it brought me to stock. When I converted them, i converted them with the rom. That rom worked. the gapps did not. if theres anything else I can help just ask and Ill try to do. Im just so happy to have a bootable CM9 again. Thank you so much

kontam said:
You guys are all really amazing for helping me out.
And as probably mentioned before by rasta Im not sure what the issue is but theres still something not quite gelling for the version. I took another screen to hopefully help you identify where its going weird. It is a little different but its still that crc cd issue. Im not going to try to flash it to see if it works, only because Im pretty certain that won't do it. But I really appreciate you looking into it.
and for clarity I also get a very similar if not exactly the same message when It trys to do the gapps as well. (using the 4/29 signed gapps)
And I decided now to try flashing the rom. it worked. Fantastically! though the boot animation is freezing. I dont even care about that since its actually working again. Awesome. But.. now im having those same issues as Rasta with the gapps. I flashed them and when I went to reboot it brought me to stock. When I converted them, i converted them with the rom. That rom worked. the gapps did not. if theres anything else I can help just ask and Ill try to do. Im just so happy to have a bootable CM9 again. Thank you so much
Click to expand...
Click to collapse
Thanks for the feedback... looking into gapps issue now... is this for primary or alternate?

Everything I'm referring to is for the alternate. Also not sure if this has anything to do with it but the calendar is broken with the gapps back from the novemeber or whenever dual boot apps. But flashing the fix doesnt fix it anymore, and then a reboot after that brings me to stock.
Also, im having issues doing a factory reset on stock when i take the SD card out.. is there something that clockwork did when it was trying to flash an incorrect rom?

If you want to return to stock situation, you probably should wipe everything and find stock image to flash.
Unleashed from my Revolutionized Desire HD

Updated to ICS -- Slightly Laggy Help

I have updated to ICS via OTA.
Now, if i open keypad to dial it first shows grey screen for 2seconds and then the numbers appears... Same with contacts.
I also got couple of times black screen as if phone frooze.
Once, even i got scrambled green images on screen which got corrected by pressing Home button multiple times.
Apart from this, Phone seems to be running fine.
So, how can i myself solve this problem now OR Do i have to go to Samsung service centre and let them reinstall ICS?
PS:
I am using Indian official ICS Baseband Ver. LP4 & Build Number LP8.
I have never rooted and was on Stock GB before the urgrade.
I fear if i try to fix this ICS problem myself i will run into bricking problem.
UPDATE
See post 7 & 13 Below

I had this issue but after i wired data using code *2767*3855# everything worked smoothly.
You can try this at your own risk as it might brick if yor device has emmc bug. I have already done it over 15 times and no issue
Sent from my GT-N7000 using XDA

olivespin said:
I have updated to ICS via OTA.
Now, if i open keypad to dial it first shows grey screen for 2seconds and then the numbers appears... Same with contacts.
I also got couple of times black screen as if phone frooze.
Once, even i got scrambled green images on screen which got corrected by pressing Home button multiple times.
Apart from this, Phone seems to be running fine.
So, how can i myself solve this problem now OR Do i have to go to Samsung service centre and let them reinstall ICS?
PS:
I am using Indian official ICS Baseband Ver. LP4 & Build Number LP8.
I have never rooted and was on Stock GB before the urgrade.
I fear if i try to fix this ICS problem myself i will run into bricking problem.
Click to expand...
Click to collapse
I rooted my Note after about two days so not sure if this will work on non-root....
Reboot into recovery (Power+Vol Up + Home) then clear cache and clear Dalvik cache. Reboot then see if lag continues. Clearing caches and reboot seems to get rid of lags and gives phone a new life

Today again phone got frooze on homescreen for 5mins and got back to life again after pressing Home key numerous times
So yes, something is wrong with this ICS update.
Plz provide a solution and also mention if tht solution can lead to bricking bug..

BUMP.

I had exactly the same problems while updating Gb to ICS using OTA update. Anywhow, I never got to fix this. I would try following steps:
Clean the cache of your ICS installations/apps using any Cache-cleaning tool on the Play Store
Reboot your phone like 2-3 times (sometimes this seems to fix some problems with your kernel/rom since they have to settle down.
Update all your apps to their latest versions, since most apps have fixes for ICS installations, and might slow your phone a bit down in some way
Click to expand...
Click to collapse
When you still would have problems with your ICS installations I would recommend installing a custom rom over your stock ICS installation. This did the trick for me eventually.. But depends on if you would like to have a stock or custom ICS rom.

HELP
I tried the above suggestion and done Factory Format via *2767*3855#.
Now, after entering code the device havent rebooted for the next 15mins, so i pressed the power key to reboot manually and then i got the message format failed or sumthing similar which i dont seem 2 recall.
Now, all my Smemo data & camera images is wiped... but phone numbers and messages intact.
and the originally mentioned problem is still there..... So wht is my solution now ?
I want to delete every old system files & Clean-install ICS - So Is it via kies?
Dont know much abt all this so a detailed help would be highly appreciated.

olivespin said:
I have updated to ICS via OTA.
Now, if i open keypad to dial it first shows grey screen for 2seconds and then the numbers appears... Same with contacts.
I also got couple of times black screen as if phone frooze.
Once, even i got scrambled green images on screen which got corrected by pressing Home button multiple times.
Apart from this, Phone seems to be running fine.
So, how can i myself solve this problem now OR Do i have to go to Samsung service centre and let them reinstall ICS?
PS:
I am using Indian official ICS Baseband Ver. LP4 & Build Number LP8.
I have never rooted and was on Stock GB before the urgrade.
I fear if i try to fix this ICS problem myself i will run into bricking problem.
Click to expand...
Click to collapse
Facing the EXACTLY the same problem man.. Feel i have done a mistake by upgrading to ics
Sent from my GT-N7000 using xda premium

androidlover1 said:
Facing the EXACTLY the same problem man.. Feel i have done a mistake by upgrading to ics
Sent from my GT-N7000 using xda premium
Click to expand...
Click to collapse
Somebody give us proper solution to this.. HELP!
Sent from my GT-N7000 using xda premium

Flash gingerbread again with odin, then do a factory reset... then upgrade to ics again using odin...

I dont want to go to GB again..... All i want is fresh clean install of ICS on my phone... So how to do tht ? (i dont wana play with my phones warrenty)

You can use pc odin to flash stock ics, not recommended though as you're on ics kernel now. Best to follow previous poster, fladh gb stock kernel first.
please hit thanks if i helped

SpyderTracks said:
You can use pc odin to flash stock ics, not recommended though as you're on ics kernel now. Best to follow previous poster, fladh gb stock kernel first.
Click to expand...
Click to collapse
If i use odin to flag GB first, will i loose my phones warrenty? (And i dont even knw how 2 use it)
Second, can i go 2 samsung service centre and let them delete all old files and install fresh copy of ICS? If i do, will i run a chance of bricking..... Coz i dont want to run into parts replacements and repairs problem...
What is the best solution now.

olivespin said:
If i use odin to flag GB first, will i loose my phones warrenty? (And i dont even knw how 2 use it)
Second, can i go 2 samsung service centre and let them delete all old files and install fresh copy of ICS? If i do, will i run a chance of bricking..... Coz i dont want to run into parts replacements and repairs problem...
What is the best solution now.
Click to expand...
Click to collapse
Since you did nothing wrong that could void your warranty, and you don't know too much about fixing it yourself, save yourself the hassle and let a Service center take cre of it for you .

CM9 on Nook Color is frustrating me

I just bought a Nook Color and installed CM9 on it. The bottom where it displays the notification and wireless signal is gone. Also every 5 seconds is force closing everything. Apollo looks cool but I cant check it out mainly cause itll force close it. N i forgot to add it FREEZES! Can anyone tell me if I downloaded the wrong thing n have to re install or just forget it. N if i have to re flash please give me the WORKING links n directions THANKS!!!

BennyP86 said:
I just bought a Nook Color and installed CM9 on it. The bottom where it displays the notification and wireless signal is gone. Also every 5 seconds is force closing everything. Apollo looks cool but I cant check it out mainly cause itll force close it. N i forgot to add it FREEZES! Can anyone tell me if I downloaded the wrong thing n have to re install or just forget it. N if i have to re flash please give me the WORKING links n directions THANKS!!!
Click to expand...
Click to collapse
How did you install it? To SD or internal memory. And which version of CM9 are you using? Opengl or non-opengl?
If you installed to internal memory, did you factory reset via CWM first? You need to if coming from stock. You can still do it now.
If you installed to SD, what class SD card are you using? It should be a Sandisk class 4.

Your download isn't broken. CM9 on the NC is - it isn't really *done* yet on the Nook Color. Developers are working on it, but for now your best bet is CM7.2. I expect we might hear an announcement very soon, but for now, use CM7.2.

It's obvious that the installation of this person has problems.
CM9 DOESNT have this kind of problems. It might be a bit slower in hardware acceleration matters in comparison to CM7, but it sure works fine in all other matters.
It's quite mature by now.
Produced by NookColor at ICS AOKP 4.0.4

BennyP86 said:
I just bought a Nook Color and installed CM9 on it. The bottom where it displays the notification and wireless signal is gone. Also every 5 seconds is force closing everything. Apollo looks cool but I cant check it out mainly cause itll force close it. N i forgot to add it FREEZES! Can anyone tell me if I downloaded the wrong thing n have to re install or just forget it. N if i have to re flash please give me the WORKING links n directions THANKS!!!
Click to expand...
Click to collapse
What did you download?
Edit: Forget it. LeapinLar already asked all the pertinent questions.

I'm having similar issues as well. It's kind of sluggish and it has frozen a few times already. I downloaded the nightly by Eyeballer over at Techerrata: cm-9-encore-20120904-0700-unofficial.zip.
In the instructions over at Androidforums does say that it might be sluggish the first few days so I guess I will just have to wait it out. I did just install about roughly 12 hours ago.

I just installed today, over my CM7.2 install in internal memory. It seemed okay at first, though a bit sluggish. But then I re-booted it and now it is acting possessed. Apps are launching by themselves (Play Store, a notepad app I had installed, voice command window, etc.) Very odd. I've shut it down and re-booted, same thing. I am thinking of maybe doing a complete fresh install from a SD card, wiping out all my apps from 7.2 and see if that helps at all. Or, I made a backup of my 7.2 install from CWM before installing CM9, so can always go back to that.

Just to follow up on my previous post: My NC running CM9 (latest GL version) did stabilize quite a bit after a day or so. But it still is very sluggish at times, to respond to screen touches, opening apps, and even loading webpages. I ran the Quadrant benchmark tool and the results are slightly lower than I got with CM7.2, but not terribly so. I'm debating whether to go back to 7.2, or do a factory reset and try a fresh install of CM9 and see if that's any better? Is there any evidence that a fresh install will work better than updating over a installed 7.2?

It's total mistake to update CM9 over Cm7 or any other different system.
To be able to talk about how things should be, you need to do a clean install and then for sure things will be better.
Powered by my IceCold 8.6.1 DHD

RASTAVIPER said:
It's total mistake to update CM9 over Cm7 or any other different system.
To be able to talk about how things should be, you need to do a clean install and then for sure things will be better.
Powered by my IceCold 8.6.1 DHD
Click to expand...
Click to collapse
Wow, that made a world of difference! Thanks. I thought I'd read somewhere else that it was okay to update from CM7 to CM9.