Related
Hey all, I've been looking around the past few days and didn't see anything on this particular issue.
Basically, I washed my G1 and had to get a new one. The one that got washed has been starting up (slowly, and not always), but the touchscreen no longer works. I reflashed the software to hopefully alleviate any of the problems when it was starting up. My initial thought was to use fastboot to flash the backup I made on my new phone with nandroid, but the bootloader isn't working properly (I'll try a reflash of that too).
So, do any of you guys know of any other ways to bypass the startup welcome touchscreen?
Try placing your finger on the Android, press the trackball, then lift the finger and press the trackball again
Tommy
IzzeLing said:
Hey all, I've been looking around the past few days and didn't see anything on this particular issue.
Basically, I washed my G1 and had to get a new one. The one that got washed has been starting up (slowly, and not always), but the touchscreen no longer works. I reflashed the software to hopefully alleviate any of the problems when it was starting up. My initial thought was to use fastboot to flash the backup I made on my new phone with nandroid, but the bootloader isn't working properly (I'll try a reflash of that too).
So, do any of you guys know of any other ways to bypass the startup welcome touchscreen?
Click to expand...
Click to collapse
Flash the ADP1 software.
Edit: You'd still need touch for that, sorry.
The driver was all wonky, uninstalled, reinstalled, fastboot works now Flashed over to my new G1's state, but forgot to take off the lock screen... Flashing yet again. Everything should be good from here.
Edit: Alright, washing the G1 makes it wacky. The touchscreen works now after restoring it to the new G1's state. Weeeirrrdd.
Edit 2: Anddd now the touchscreen doesn't work :S
well.. when my touchscreen broke i used remote control software to control my ppc from pc .. thats one way to bypass welcome screen, but won't get you much further. I used it for making a backup from my phone.
just leave it off for a while and keep it someplace dry and warm so it can dry out.
You may try to modify build.prop in the rom you flash
ro.setupwizard.mode=DISABLED
I think it will skip the setup
Sorry can't help myself. In the laundry?
I guess I'm wondering what exactly you did. I'm assuming it didn't make it into the dryer....
If you need the data off it, you might be able to ADB pull what you want to keep. If I'm not mistaken, ADB is as close as we have to remote controlling for Android at the moment.
There may be some places around, like PPC Techs, that can do hardware repair. I'm guessing what will happen is you'll occaisionally get it to work for brief stints after reflashing or whatever, but it'll keep conking out until the hardware issue goes away/gets fixed. Hardware issues do that, printers, routers, sometimes PCs.
Not to be a naysayer, but I don't think changing out the software is going to help.
I washed my G1 (was in pocket of jeans under the water for about 90 seconds), and after that I disassembled it to let it dry. It was running fine up to the day I SPL bricked it.
Hey.. i split water on my phone.. it couldnt have been that much but the touch screen wasnt working.. thought if i factory reset it, it may started working..
I dont actually understand all the lingo you guys use.. but any ideas on how i can fix it?
J x
oh the main issue is i cant get past the touch android to continue set up... please i just want my android to work!!! J x
I'm having a similar issue... My phone randomly stopped loading android.process.acore and it's messing with my heart. The touch screen doesn't respond but I can use the trackball to navigate, and every acore process force closes instantly upon activation, such as dialer, contacts, music, etc. The wonderfully helpful people at T-Mobile instructed me to do a factory reset on my G1, and it should fix the problem.
New problem: I can't get past the "Touch me, I'm an Android logo" screen. When I click Emergency Dial, it force closes because the acore processes are still messing up. The intention today was to reload the Cupcake SPL and Radios onto the phone. The issue there is that I can't touch the screen to start the USB connection with my computer.
Anyone have any suggestions aside from paying another $130 bucks??
This will do the trick
google androidscreencast it will allow you to contol your G1 via your PC
...let me know if you have resolved android.process.acore im on the same boat and a wipe and flash has yet to solve it...
same boat for me too! wow, this is three, maybe 4 of us currently experiencing same problem!
I love screen cast. Droid explorer is great too, basically a GUI for adb, and has a plugin for screen cast. Too bad you have to be online though, I'd love to use screencast offline!
I'll update if I figure out the error problem!
Well it looks like a complete wipe and a flash back to non root status is whats gonna take to fix the android.process.acore issue. BUT now w/o root, I cant access the G1 via android screen cast...so im totally stuck on the "Touch Android to begin" screen... sucks to be me lol
I think I'm in the same boat. I didn't know about the screencast application before I did a complete wipe to stock. So I'm stuck at the "touch android" as well. This phones pretty much junk to me right now.
I wonder if any of you have tried restoring your latest back up?
Yes, no help, either on the touchscreen, or the incessant errors. I think there must be some code that checks whether the touchscreen works, and sends back an error if it doesn't. I've tried almost every combination of radios and spls mixed with several different cyanogen roms going back to 4.1, both fresh installs and nand restores.
Currently I'm running the latest cyanogen, radio and hard spl. I get errors often, and can't use the phone / dialer at all without force closing. For now texts and google voice work so I have at least some communication. Ironically, I can't even unroot because none of the spls will flash dreaimg.nbh, but that probelm is in my unresponsive bootloader thread.
Sorry to hear about your predicaments allthrottle and r1ch. Strangely you are right where I'm trying to get, I have warranty coverage to fall back on.
Can someone please help me..
I installed Cyanogen 3.4 when it got released a few days ago and it was running smoothly.. I think he is a genious. Just today my phone shut off on its own and I had to take the battery out and put it back in to get it to come back on. I don't know if it is Cyanogen or some sort of app, as I download apps quiet frequently. I am going to go through my apps now and also reinstall Cyanogen 3.4 tonight and leave my phone on all night. I guess I will have to see in the morning..
Anyways, can someone help
I ve fot sometimes the same issue with dudes cupcake which use th cygnonen kernel...
I ll be glad to have a fix
Are you overclocking the processor? That might contribute to it shutting down.
I do overclock but why do i have to 'battery pull' to make it reboot?
Yes, same issue here.
Uhh, again...
Powered up, set to standby, waited 1 min, shut down.
EDIT: I'm on Rogers Cyanigenized.
Same issue here. Complete lockup with screen off, have to pull battery to boot again. Seems to happen every 6-12 hours for me.
My Phone:
Cyanogen 3.4
radio 2.22.19.26I
Haykuro's SPL
Kernel 2.6.27.24-cm by [email protected] )
NOT overclocked, and no clocking tools even installed. Persists after several clean wipe and reflash also.
This thread's timing is great... I was just about to reset back to rc29 and build back up. Thought I was going to have to replace my phone
Rastasia said:
I do overclock but why do i have to 'battery pull' to make it reboot?
Click to expand...
Click to collapse
This question should probably be in the Dream section and will probably get locked/moved but Pulling the battery reset the "overclock" until it boots back up. This would be why pulling the battery helps.
hey you don't havbe to pull battery just push end call start call and menu all at once it will reboot you phone
Ok, thanks to Jakob, we know, that android freezes, is doesn't shut down.
I now tested with and without overclock, it made no matter to me not to overclock, there's no difference.
But I experienced it didn't happen when it's connected to a charger..
mysterious..
This keeps hapening to me, first it was happening in Cyanogized Rogers rom, then in The Dudes 1.3 b 12, I'm flashing JAC1.62 right now, this never happened to me before I got my class 6 16gb and started using apps2sd
Just curious, does this happen to anyone without a2sd
i'm having the same problem
seems to happen in the builds using the Cyanogen kernel. I'm sure this issue will iron itself out in future releases so just sit tight.
I too am having the problem on the Cyanogen 3.4 build. Its definately a change in 3.4 as I didn't have this problem in any of the 3.3 betas. I'm doing Apps2SD as well.
One thing I have noticed as well is that networking has been acting flakier than normal.
I had this issue on the pre-cupcake radio but not as frequent, so maybe it's just an amplified version of the same problem? There was a thread about it before but I'm too lazy to search for it.
The hangs was the only reason I moved to virtududes rogers rom v3
I'm going to try and get this sorted out tomorrow. For some reason the OOM killer kicks in sometimes and kills a critical process like zygote.
atleast you don't have this problem!
I've reflashed,wiped,formatted and apps2sd2 or sdpsplit, so many times already... trying different ways for each. But same thing always happens... my memory card gets damaged then wiped all by itself.
Uninstall toggle Setting and use Reparing Ext partition with Cyonagen recovery seems to fix this issue
So happy I found this thread! I'm using Google Ion and having this issue since yesterday. So annoying. Anyone got a fix?
I`m having the same problem, the phone freeze, looks like is a hardware problem, i`m on CRC1
I have started to have this issue as well. I am currently running Cyan4.1.999. It happened yesterday while on a call, after a call, and also while the phone was on charge.
Solutions?
this started happening randomly about 2 weeks ago now
I've tried 3 different roms, but the problem still exists
it first started happening when i had the eneryrom flashed
but now i believe its not the roms thats causing this, i think its the hardware in my x1 or something, im not sure
what can i do to fix this?
basically my x1 restarts by it self, randomly at random times
maybe every other day, and sometimes even twice in a day
its really weird and not looking good at all
any help is appreciated, i just want to fix this
qritikal said:
this started happening randomly about 2 weeks ago now
I've tried 3 different roms, but the problem still exists
it first started happening when i had the eneryrom flashed
but now i believe its not the roms thats causing this, i think its the hardware in my x1 or something, im not sure
what can i do to fix this?
basically my x1 restarts by it self, randomly at random times
maybe every other day, and sometimes even twice in a day
its really weird and not looking good at all
any help is appreciated, i just want to fix this
Click to expand...
Click to collapse
Did you install any kind of softwares or applications? Could be due to an unstable application
Also, does it restart when you are using it or doing something on your phone? or does it just restart while sitting on the table?
If it just restarts when the phone is in your pocket while walking/running (when u r not using it), then it could be possible that your battery is loose.
Check to see if you battery fits perfectly. stick in a folded small piece of paper at one of the bottom side of the battery to tighten the battery if your battery is loose.
Let me know if this is the case.
I would suggest flashing back to stock rom and see if the problem still exists....sd card could be a factor also...
Regards,
WC
haroonazeem638 said:
Did you install any kind of softwares or applications? Could be due to an unstable application
Also, does it restart when you are using it or doing something on your phone? or does it just restart while sitting on the table?
Click to expand...
Click to collapse
nope i didnt install any softwares of applications, i just use the roms how they are
also yes it only restarts when its sitting on the table
haroonazeem638 said:
If it just restarts when the phone is in your pocket while walking/running (when u r not using it), then it could be possible that your battery is loose.
Check to see if you battery fits perfectly. stick in a folded small piece of paper at one of the bottom side of the battery to tighten the battery if your battery is loose.
Let me know if this is the case.
Click to expand...
Click to collapse
i will check my battey, doesnt seem like battery is loose but i will double check, and get back about that
Wild Child said:
I would suggest flashing back to stock rom and see if the problem still exists....sd card could be a factor also...
Regards,
WC
Click to expand...
Click to collapse
i;ve been using roms for months, it never happened before just recently
its really hectic for me to flash back to stock but if thats the only option i will do it
also if its sd card,,,how could i fix that, should i reformat it or something?
This has happened to me in the past when using an HTC Touch Diamond. I think it has something to do with not wiping the device or doing a hard reset before flashing a new rom. Does it hard reset when the phone restarts?
Zaslav said:
This has happened to me in the past when using an HTC Touch Diamond. I think it has something to do with not wiping the device or doing a hard reset before flashing a new rom. Does it hard reset when the phone restarts?
Click to expand...
Click to collapse
nope just a regular restart
i've installed my rom's with the right procedures, including a hard reset its not that
any other solutions please?
I mentioned the flashing back to stock to rule out its not a hardware issue....but a software issue....remove your sd card copy the contents of it to your hard driver....reformat the card....Im not saying this will solve it...but i have seen the sd card becaue of reminants of other flashes mess some things up...
Regards,
WC
qritikal said:
i;ve been using roms for months, it never happened before just recently
its really hectic for me to flash back to stock but if thats the only option i will do it
also if its sd card,,,how could i fix that, should i reformat it or something?
Click to expand...
Click to collapse
reflash your stock rom.. if your phone is not functioning as normal, then i suggest to check with SE
I would download the ROM and re-flash your phone. Could be possible that the download got corrupted. Wouldn't hurt.
Wild Child said:
I mentioned the flashing back to stock to rule out its not a hardware issue....but a software issue....remove your sd card copy the contents of it to your hard driver....reformat the card....Im not saying this will solve it...but i have seen the sd card becaue of reminants of other flashes mess some things up...
Regards,
WC
Click to expand...
Click to collapse
i flashed back to the latest stock rom
i thought it was okay at first but still my phone restarts at random time when its laying on the table
i have no clue what to do anymore
i did also reformat the sd card
i dont think i have warranty with SE any more, i dont have my receipts n etc
what can i do? please help
Remove the sd card and see what it does...other then that...your device may be giving up the ghost and may need to be sent to a service center....
Regards,
WC
qritikal said:
i flashed back to the latest stock rom
i thought it was okay at first but still my phone restarts at random time when its laying on the table
i have no clue what to do anymore
i did also reformat the sd card
i dont think i have warranty with SE any more, i dont have my receipts n etc
what can i do? please help
Click to expand...
Click to collapse
tried everything, im sure there something wrong with the phone
cant do anything about it, but thanks for the help guys
ok first off i love the fresh roms so im not bashing.
does anyone else have an issue that seams to be directly related to flashing the new fresh 2.1.1 rom.
when im in a call and end it with the power button it restarts the phone.
is this because of what i think it is or something else.
i wiped everything when i flashed so i dont know what else it could be, in the mean time i guess i have to go back to fresh 1.1 sense i cant find a fresh 2.0d download link anymore and i deleted my nandroid and the 2.0d rom off my computer like an idiot. uneless someone could point me to a 2.0d link
shawnwojcik said:
ok first off i love the fresh roms so im not bashing.
does anyone else have an issue that seams to be directly related to flashing the new fresh 2.1.1 rom.
when im in a call and end it with the power button it restarts the phone.
is this because of what i think it is or something else.
i wiped everything when i flashed so i dont know what else it could be, in the mean time i guess i have to go back to fresh 1.1 sense i cant find a fresh 2.0d download link anymore and i deleted my nandroid and the 2.0d rom off my computer like an idiot. uneless someone could point me to a 2.0d link
Click to expand...
Click to collapse
probably should be in q&a or fresh's thread but here is a link all fresh's downloads are on geekfor.me should be at the bottom
http://geekfor.me/category/android21/page/2/
I found that the restarting issue on my end was linked to the battery stats and roation stats. After i wiped those, for some reason, i stopped restarting.
sdotcarlisle said:
probably should be in q&a or fresh's thread but here is a link all fresh's downloads are on geekfor.me should be at the bottom
http://geekfor.me/category/android21/page/2/
Click to expand...
Click to collapse
sorry i wasnt sure where to put it. sould i start a new thread in there or can a mod move this one?
Powers16 said:
I found that the restarting issue on my end was linked to the battery stats and roation stats. After i wiped those, for some reason, i stopped restarting.
Click to expand...
Click to collapse
Can you elaborate on this? How do you wipe these stats?
i had the same problem but it was on fresh and damage control, i figured out it was the app i was using to call people with...called quick connect...
it didn't happen if i dailed with the stock dialer or through people...
jasonevil said:
i had the same problem but it was on fresh and damage control, i figured out it was the app i was using to call people with...called quick connect...
it didn't happen if i dialed with the stock dialer or through people...
Click to expand...
Click to collapse
Alright I did everything mentioned, above. i wiped the battery and rotation stats in ra recovery i even re partitioned my sd card and did a wipe data/factory reset plus the ext and dalvik-cache. then re flashed fresh 2.1.1.
also i am not using any other dialer that i know of. just the one that comes backed in the rom.
so why am i still resetting randomly!!! it even did it when i was doing nothing at all not just in a call like before.
this is on two seperate sprint htc heros that this is happening to.
anyone please help!
shawnwojcik said:
Alright I did everything mentioned, above. i wiped the battery and rotation stats in ra recovery i even re partitioned my sd card and did a wipe data/factory reset plus the ext and dalvik-cache. then re flashed fresh 2.1.1.
also i am not using any other dialer that i know of. just the one that comes backed in the rom.
so why am i still resetting randomly!!! it even did it when i was doing nothing at all not just in a call like before.
this is on two seperate sprint htc heros that this is happening to.
anyone please help!
Click to expand...
Click to collapse
couple questions.
1. are you using any aggressive process killers, like the one found in spare parts?
2. what, exactly, do you mean by resetting? do you mean a quick 10 second restart of rosie, or a full on 1.5 minute reboot?
Nextelian said:
couple questions.
1. are you using any aggressive process killers, like the one found in spare parts?
2. what, exactly, do you mean by resetting? do you mean a quick 10 second restart of rosie, or a full on 1.5 minute reboot?
Click to expand...
Click to collapse
sorry i took so long to reply.
no process killers.
Im now able to replicate it restarting (not randomly) if i let the phone go to sleep by its self and sit for a minute when i hit the end button to wake it up nothing lights up like it should instead it does a full on 1.5 minute reboot every time.
on a separate thread someone suggested i try a different battery because whenever they put a different battery in it stopped resetting. (I was not able to try this yet because i don't have any spare batteries laying around)
I just find this hard to believe only a few people are having these problems and why no one seems to have a definitive answer.
This is kind of one of those bugs where I have to say it's something going on with your phone. Fresh Rom 2.1.1 has been downloaded over 4000 times. I restart mine constantly while testing things which means I am constantly duplicating your situation of restarting the phone, letting it sleep, and then turning it on via the power button, and I have never had this happen.
Please post a debug log of it happening and we'll see if we can figure out why your phone is doing it.
My sister had this issue even on stock 1.5. Rooted, added recovery still had it. Flashed 2.0d, still had it, went to recovery and wiped battery stats.
Haven't had it happen since. Now on 2.1.1 and all is well...go figure.
flipzmode said:
This is kind of one of those bugs where I have to say it's something going on with your phone. Fresh Rom 2.1.1 has been downloaded over 4000 times. I restart mine constantly while testing things which means I am constantly duplicating your situation of restarting the phone, letting it sleep, and then turning it on via the power button, and I have never had this happen.
Please post a debug log of it happening and we'll see if we can figure out why your phone is doing it.
Click to expand...
Click to collapse
thank you for helping flipz, sorry for thinking it was something to do with your rom (foot in mouth). I now believe it a hardware issue related to any 2.1 fw.
This has happened to me on 2 different phones. Mine and my friends. Mine restarted "randomly" once i wiped the battery and rotation stats and it fixed mine. My friends on the other hand i could not get to stop restarting for the life of me. So i was forced to switch back to a 1.5 fw rom.
Point being it will take me a few days to get back over there and put a 2.1 fw back on it and get a debug log off of it. for now i can try using his battery in my phone and see if i have any issues. im crossing my fingers in hope i will so we can buy a new battery and see if it goes away for him.
in the mean time i can post a debug log for my phone but it probably wont do any good
i will try to post the results of the battery swap later today.
again thanx flipz i am confident with your help we can resolve this.
ok i thought i attached a error log but i guess its too big, so ill try zipping it and attaching it.
hero
I noticed reinserting the root file helped me also make sure your not using otwidhet or super pc unless u have a rom for it i use fresh toast 2.1 no problems quickquickquick
REDSCARFACE said:
I noticed reinserting the root file helped me also make sure your not using otwidhet or super pc unless u have a rom for it i use fresh toast 2.1 no problems quickquickquick
Click to expand...
Click to collapse
I kind of a noob, what do you mean reinserting the root file? i thought the root was the main directory not a file.
Also i dont know what "otwidhet" or "super pc" are, im assuming im not using them if they didnt come with the rom. right?
whoops, i forgot to post the results of swapping my battery with my fiends to see if i could single out a bad bad battery.
i didnt have any luck making my phone reset itself with his battery. One of these days im going to buy a couple new batteries put on in my friends hero and flash fresh 2.1.2 on it. Im also going to try using different radios on a hunch from a different thread i read.
i dont mean to waste anyones time im just busy and messing with phone is something i cant devote alot of time to especially sense i put a 1.5 fw rom on my friends phone and he no longer has any issues.
thanks for the patients in helping me guys.
ok im at a loss. i really need your guys help.
I put a 2.1fw on my buddies phone. put my battery in his phone let it go to sleep by itself and hit the end button to wake it up and it still does a reset. now i guess im not sure if it s a full on reset but it takes about a minute to reset.
so i put his battery in my phone and let it go to sleep and het the end button to wake it up and it also reset, now i did not clear the battery stats either and now after one time i can not get my phone with his battery to self reset for the life of me...???
no matter what bettery i try his phone will not stop resetting.
im posting an error log from his phone i got off adb using
adb bugreport > errorlog.txt
is that what im suppose to do? please help i would have been just fine with the 1.5fw on his phone but there was an audio issue that on some calls the person on the other end could not hear him.
does anyone know if the flipz audio fix will work for that or is that not a good ides?
Here is his error log, i hope this is what im suppose to post.
if anyone has any ideas about the audio fix for the 1.5fw that would be awesome cause now i gotta go back to that becasue i cant leave his phone with porblems.
Could it be that it is just Sense restarting and not the whole phone. Try using Fresh 2.1.2 with LauncherPro and see if you still have the problems. Make sure that you are not using the vanilla launcher in 2.1.1 as I had several instances where it caused instability.
lineman78 said:
Could it be that it is just Sense restarting and not the whole phone. Try using Fresh 2.1.2 with LauncherPro and see if you still have the problems. Make sure that you are not using the vanilla launcher in 2.1.1 as I had several instances where it caused instability.
Click to expand...
Click to collapse
I dont think thats the issue, my phone now restarts itself abuot once a day and i am using launcher pro. i also have my friends battey in my phone. so i guess is could still be the battery.
Im still confused on what i have to do to get some help from the devs. i posted a error log like asked if i was suppse tp post something else could someone please tell me? this is getting extremely frustrating. am i the only one here???
please someone help.
Long time reader, first time poster (hello everyone!). I was wondering what the opinion of the folks here might be and if they've any suggestions. Today my rooted Nook Color suddenly started acting up. Applications are very often not responding as they should, bringing up the 'Wait' and 'Force Close' box (happens when pressing the soft back and menu buttons as well). It's really quite weird, earlier today I was using it just fine, and suddenly it started acting like this. I tried the usual things like fixing permissions and clearing the dalvik cache, nothing helps. Also, annoyingly restoring a backup from a previous 'known working' state didn't help either. (I suppose I should note that I'm not running CM7 or anything like that)
Any suggestions or ideas on what could have happened? Should I perhaps return it to stock and try to exchange it for a new one (I've only had it for about a month)? The fact that it seemed to still be happening when I restored a back up makes me wonder if it's some kind of hardware issue.
The thing driving me crazy is how it's so suddenly acting strangely. I've been using it rooted (and overclocked, on dalingrin's excellent kernel) just fine for about a month and it's never seemed unstable or anything.
I forgot to mention (not that it probably matters) but the volume buttons caused the wait/force close thing too. Guess I'll be calling them tomorrow.
Having same problems. And VERY SLOW. Wait or Force Close
Very weird, but I noticed today that it started acting flaky in my Nookie Froyo 0.6.8.
I installed Amazon's app store on there today and angry birds rio. The apps seem to be okay, but general opening and navigating are herky jerky.
Something else that is weird, I was just using it and it completely locked up on me to the point of needing to do a hard shutdown by holding down the power. At the exact same time, I happened to look at my phone and it also had rendomly rebooted itself at the exact same time. My phone is running CM7 (Droid1).
Coincidence?
HI,
I had a variety of problems with similar symptoms as you describe, but I had
been playing with several uSD installs of HC/Froyo/CM7 internal/Froyo internal etc.
I believe that the main cause of my problem was due to an interaction between
the EXT3 and EXT4 formatting of the cache partition. The solution for me was to
reformat the cache partition for my current installation.
Other threads I looked at made suggestions such as:
Reformat the cache partition.
Clear the Dalvik cache.
Run ROM manager and select fix permissions.
Not sure if any of these are relevant to you though.
Good luck.
Peter
Try installing a custom ROM (not a backup), making sure to clear everything before install. If it still happens, then yeah it sounds like a problem with the device itself. I've had this problem on my Droid twice and it ended up being (the first time) an app I downloaded and (the second time) an app that I updated. It made the whole phone unstable!
pmilford said:
HI,
Other threads I looked at made suggestions such as:
Reformat the cache partition.
Clear the Dalvik cache.
Run ROM manager and select fix permissions.
Click to expand...
Click to collapse
Thanks, but I tried those already (I forgot to mention it in the first post, but I did try reformatting the cache partition).
JLCollier2005 said:
Try installing a custom ROM (not a backup), making sure to clear everything before install. If it still happens, then yeah it sounds like a problem with the device itself. I've had this problem on my Droid twice and it ended up being (the first time) an app I downloaded and (the second time) an app that I updated. It made the whole phone unstable!
Click to expand...
Click to collapse
Yeah, I guess that's a good idea. Then I'll be even more sure it's the hardware itself. I'll let everyone know how it goes. Also...it's kind of nice to know I'm not the only one with random issues.
9thSage said:
Then I'll be even more sure it's the hardware itself. I'll let everyone know how it goes. Also...it's kind of nice to know I'm not the only one with random issues.
Click to expand...
Click to collapse
All I'd need to do to install Froyo from here is format/factory reset everything with clockwork and then install the zip from within CWM, correct?
Couldn't get it to work for some reason. Since I wasn't sure, I decided to format data, cache, and system, then use one of the excellent "Nook Color Restore to Stock" zips. It seemed like it was ok (couldn't test it more since I forget my B&N password and evidently made a typo when tying my mother's maiden name ), decided to try that back up again since I knew the back up worked at one time with no problem (and the md5 was fine, so that shouldn't have changed) and it worked fine for maybe 20 minutes, but now it's weird again.
I'll have to try Froyo again tommorow when I'm hopefully less out of it. I suppose that's probably a more meaningful test.
I know I said I was going to install Froyo, but I decided to try bringing it back to stock and re-rooting it from scratch. I've been using it for a while (reinstalling apps, changing settings back...etc) and it's worked absolutely fine. Been using it on and off for a few hours.
I'll be sure to really bang on it today to make sure it's stable, but so far so good.
I think I can declare it stable. Thanks a lot to all who helped out. I wonder what happened? What a strange, strange problem.
9thSage said:
I think I can declare it stable. Thanks a lot to all who helped out. I wonder what happened? What a strange, strange problem.
Click to expand...
Click to collapse
Glad to hear! I actually just had a similar problem (again on my Droid) that it ended up being the ROM, but yet everyone else I know had no problem on that rom....just goes to show you Android is different for every unit.