Related
WARNING This is a long post describing various events of my G1 and things I was going through, so Im basically doing a dump of my thoughts and possible reasonings to put everything I can report, case it is a ROM, Hardware, or Software flaw somewhere or just user error. But since this forum is about feedback for devs or rom providers =)
Ok I dont know where to begin with this post. Last night my G1 needed a wipe. Why? Cause all it did was reboot over and over not getting past 1st home screen, then finally android screen. What happened before this? All I have of the things going on during that time frame was this:
(Now before the below stuff, earlier that day, Quest Live glitched on me, and when I was at the home screen, I tried to scroll left and right and it got stuck half way, which WORRIED me since I thought the touch screen was messed up. To my luck after a reboot and iso alcohol rub down on screen, it was fixed. Tho only after I unplugged it from the car charger (Which seems to really make the G1 % battery jump in record speed.. glicth?) Or Power Manager issues? Tho this wasnt the updated one, so the new one may have fixed the issues the dev said power manager was causing.
I plugged in the usb to a ubuntu running PC. To charge it, thus triggering Power Manager. Same time, I was trying to install SnapPhoto, which it downloaded, but didnt install, I was also noticing abit of lag, So I ran task manager to turn off some apps running in background, Camera, Gallery, Gaming Buzz Widget, Weather app Widget, Calender. (Then as I rem.. I tried to update AdFree when the new version came out.. it didnt install but same time when I tried to load it, it just came up black.. sign of a bigger issue maybe?)
After that of course couple of them came back. Then I tried to change the volume using the side button, It didnt respond, The on screen worked fine tho. So I decided ok, time to reboot fresh on the phone. Rebooted, Then it loaded to home screen before radio signal, then rebooted. After getting tired of not booting, (I had unplugged it from the USB btw which at 1st kept the charging light on before I rebooted it. ) I pulled the battery out. Which MAYBE I pulled it out at the wrong time during the android screen. Cause after that and I put it back in, all it did was goto the G1, then Android cycling screen, but no longer went to the home screen to try to load. Then was too late for this trick, but the Safe mode attempt. Which MAY have worked when it made it to the home screen, but once it was on Android only, safe mode didnt load at all. Just endless stuck on Android. So I had to wipe 1st then I reapplied the JF 1.51 update.zip to fix it and get the G1 to turn on again and boot.
Advice tip: If you can still boot to the home screen "somewhat" next time it cycles, try holding "Menu" in to have the G1 bypass any apps and load into safe mode, which may allow you to uninstall or fix whatever the issue is.
To my surprise. The Apps when the G1 started installing again went to the SD card. (I do not use apps2sd, Only Lucids orig) Now thats when I noticed more hell.. I went to the market to look at "My Downloads" and WHAM, the 10 apps it auto downloaded (Which I guess was a sync) are the only ones in the My Download section.. nothing from my past downloads.. Which is 110 more apps.
Advice tip: Use Atrackdog to "Export" your database to a text file and keep that on your PC. This way if ANYTHING happens, you least know which apps to look for.
Advice Tip: Upon reflection I probably should have made a nandroid backup after 1.51 was smooth. So if you havent, Id suggest looking at it) I know I will once Im set back up.
So now I am left with a interesting ponder. I msged Lucid to see if his scripts would allow me to use my 2GB which had my 1.51 data on it and somehow relink it to the G1 and have everything restored, then recopy to the 4GB which is my current one. But chances are I need to 1 by 1 install again. (Anyone know how you get apps back that arent on the market anymore? Extract from the SD card maybe?)
Anyways now I am wondering, If you install too much to the G1, will it in the end cause a problem? Im not a dev so I dont know how that all works with the ROM builds. But that wouldnt be good news if you have 129 apps, things could start messing up. (Tho not sure if that was a cause for any of the above)
Another thing I learned, if you have a GOOD screen protector on the G1 (Not the one it came with) and it smears up, or gets smudgy it seems it may interfere with the response of the touch screen. Ive notice if the screen thinks its being pressed in, a app could hang, lock up or choke the G1 to where it fixes itself by doing a reboot. Now that sounds odd that the G1 is sensitive to smudges or oil from your hands (If you had a humid hot day). Anyways fixed that with iso rubbing alcohol and a soft wipe cloth. Then rebooted.
Now my next task is to 1: Find out if my Cache since the wipe is running on the SD still, or if its on Internal. The app "Move Cache" I hear could do that, but I heard it messes up market, maps etc.. so not what I wanna do atm. Then I just gotta see if I can restore apps from SD using a app or terminal, which I am studying now, but just wanna end this post for now.
Will post more as I get around to it. Maybe I can restore the market cache manually.
do you still experiencing the touch screen error problem after all the steps you have taken? because i have the same problem. sometimes when i use touch screen to switch screens, the screen get stuck in the middle and shaking. i also cannot select anything correctly by touching. and i've read from various forums that this has something to do with the charger / charging process. i think that my problem occured because i charged using usb cable to my computer. because i never done that before (i usually charge my phone using a wall charger) and when i did, the problem happened.
How I fixed it? I turned off the G1, used rubbing alcohol with a tissue to gently wipe the screen off and clean it. Then turned back on and it was fine.
Hey
I have a problem, my phone keeps rebooting, i have rootet it with the Hero Rom, and yesterday everything worked perfectly, but when i wanted to use the camera i little while ago, the phone restarted. So i thought i would try andd do a phone reset, but when i did, the phone keeps restarting, it shows the HERO logo, and then kind of reboot, the screen goes black and its showing the HERO logo again. It keeps doing that until i take out the battery.
Can any1 help me with this problem? any suggestions will be appreciated, im kind of desperate
Per
omg i having the same problem...did you fix your phone yet?
I'm having this problem too Anyone have a solution? My HTC Magic just keeps showing the "htc" logo and refreshes every ~5 seconds. Tried taking battery and microSD out, no luck. The last app I used was Alarmania.
i wonder if i could download a different rom to a different sdcard an then load it up to my MT3G
Issue Solved!
I just called Rogers and spoke to a very helpful Rogers tech support rep. This is the solution he offered and it worked for me:
1. When the phone is off, press and hold the Home and Power button until the phone comes on.
2. You should see a little icon with an exclamation mark. Now press and hold the Home and Power button again.
3. You should see some instructions and some options. Use the trackball to select Factory reset. This will erase all your phone's data, but if you're in the cloud (ie your contacts are with Google), you should be fine, you'll just have to reconfigure everything (ie mail accounts, keyboard calibration, home screens, app downloads and preferences).
I hope that helps. I just spent a very unhappy 12 hours without my phone.
FYI: I have a non-rooted Rogers HTC Magic with no mods whatsoever. The problem started one random night when I wasn't using my phone, it just got stuck at the HTC logo like it was about to restart, and it just kept refreshing the logo.
dang my phone is rooted
Another 24 hours later and I have the same problem. My phone went into a perpetual restart last night, it just got stuck at the boot screen, so I had to do a factory reset again. Any advice on what I should do? The nightly factory reset is not a solution.
Spoke to someone on another forum with the same problem. This problem seems to happen when you use alarm clock apps. The problem happened to me whenever I was setting an alarm in Alarmania or Alarming. I'll try the phone without an alarm clock app and keep you guys updated.
I've been doing a lot of research on this the past week. I did not have this problem on my sapphire until after I rooted my phone. I've tried 3 different android custom roms. They all seem to work well at the beginning and then the random reboot occurs maybe a day or two into regular use.
Whats seems to be interesting is I've heard a lot of people in the US say it was after the 1.6 update. So I'm going to try using 1.5 again to see what happens.
I haven't even tried the HERO Rom. I had no interest in it I just wanted my phone to run faster. This could be an underlying problem in the android OS. It could also be the crappy HTC quality starting to come out .
this is the first thread that I've seen someone who didnt have a rooted phone with this issue. Could mean it IS a hardware thing.
Anyways I'll keep you guys posted. Its a crappy problem for sure.
try using another sd card,format a new sd to fat 32 ,copy paste the custom rom you want,boot into recovery mode,wipe data,wipe cache and flash the rom,that works for me.
kerdum said:
I've been doing a lot of research on this the past week. I did not have this problem on my sapphire until after I rooted my phone. I've tried 3 different android custom roms. They all seem to work well at the beginning and then the random reboot occurs maybe a day or two into regular use.
Whats seems to be interesting is I've heard a lot of people in the US say it was after the 1.6 update. So I'm going to try using 1.5 again to see what happens.
I haven't even tried the HERO Rom. I had no interest in it I just wanted my phone to run faster. This could be an underlying problem in the android OS. It could also be the crappy HTC quality starting to come out .
this is the first thread that I've seen someone who didnt have a rooted phone with this issue. Could mean it IS a hardware thing.
Anyways I'll keep you guys posted. Its a crappy problem for sure.
Click to expand...
Click to collapse
I can confirm this. I have a mytouch 3g, and with 1.5, the camera was working fine. As soon as I got the OTA 1.6 update, the camera would cause random rebooting.
I called T-Mobile USA and had a replacement phone sent to me. I got the phone, didn't install any apps, and waited until I got the OTA 1.6 update again, tested the camera several times, and got no reboots. I flashed dwang's 1.6 ROM and I am still reboot-free.
this prob anyone got fixed??
hi there,
it seems as if i had the same problem. i got an htc magic with android 1.5 (swiss edition), i guess, and after i installed alarmania and had it alarming, it rebooted. instead of showing me the home screen, it just shows a htc brand and makes a sound, and repeats this after maybe 30 seconds.
i tried taking out the battery for some minutes, didnt work. i tried to go to safe mode (pressing menu and power), but it fell into the same circle, as well as when i tried to do a factory reset. i also tried to take out the battery for 20 hours, but same reaction.
does anyone have an idea what to do? ill try to call htc tomorrow.
thx for your help,
aeronaut
ps: please excuse my bad english, but im swiss. this is the only forum where i found similar problems to mine.
aeronaut said:
hi there,
it seems as if i had the same problem. i got an htc magic with android 1.5 (swiss edition), i guess, and after i installed alarmania and had it alarming, it rebooted. instead of showing me the home screen, it just shows a htc brand and makes a sound, and repeats this after maybe 30 seconds.
i tried taking out the battery for some minutes, didnt work. i tried to go to safe mode (pressing menu and power), but it fell into the same circle, as well as when i tried to do a factory reset. i also tried to take out the battery for 20 hours, but same reaction.
does anyone have an idea what to do? ill try to call htc tomorrow.
thx for your help,
aeronaut
ps: please excuse my bad english, but im swiss. this is the only forum where i found similar problems to mine.
Click to expand...
Click to collapse
This won't help you at this point but there seems to be a trend happening. Could it be Alarmania!? My suggestion would be to not use that app as it seems to cause problems. As per the camera causing the same issue, I'm not sure if there is an update for your phones but I just recieved an update for mine (Rogers HTC Magic) and I also got stuck in a boot loop after installing the first update. I had to use a Mini SDcard adapter that I purchased at my nearest electronics dealer for ei. BestBuy. It came with a class 4 4gb SDcard and it fits on my keychain. Basically you can use this to put a new IMG on your SDcard and then reboot your phone into fastboot. The IMG will automatically install (just follow the instructions). One issue may be finding the new correct IMG that you need but I`m sure you won`t have too much of a problem finding it on an established forum such as XDA. Good luck
thx for your help, but im not able to "restart" my phone normally - as i said, not even the factory reset mode is working. any other idea without flashing the ROM?
flashing only
thank goodness I've made recovery image just before installing Alarmania - Alarms is the same
Alarmed Litle is one that worked but it crash every system start
I was having the same problem, but this, which I found on the "Canadian HTC Magic Gets Sense UI and 911 Fix" threat at androidguys.com
"If you're getting the never-ending boot screen, your phone is -not- bricked. you just haven't finished the second part. you NEED a micro-sd adapter. Turn the phone off (take out the battery), and have a micro-sd card adapter. while the phone is off, take out the sd card and plug it on your comp and delete SAPPIMG.zip from the memory card. Once that's deleted, you need to extract "HTC_Magic_Update_File2.zip" and move "SAPPIMG.zip to the memory card (it's got the same name as the first "SAPPIMG.zip" file, but the second one is supposed to be around 85mb, so don't confuse the two) after that, just repeat steps 3-8 from the first part and that should finish the update on the phone. (this part takes a while, so be patient)"
Cheers
Yes but it is only when "flashing phone was aborted".
It is not for "after instaling Alarmania" on a phone without
Sense UI.
Data WIPE not worked for me, only reflashing phone with my saved flash image (thank gooddess that I've backuped my phone beforehand) done the trick.
well, its funny, i understood the reset page on the htc homepage wrong - i called their hotline, and i was able to reset it. but some days after, i have the same prob. i dunno if it is caused by any other app i have installed during these days (i do not remember as well), but ill try to get a newer rom onto my magic
Close to two months ago I installed the latest Phiremod ROM onto my Nook Color. (Phiremod 7 I think) I followed a webpage tutorial and referenced XDAdevelopers instructions. Has been working excellent for the past couple months. Got everything set up and working great... youtube, hulu, netflix, etc. Now all of the sudden my Nook Color won't bootup but gets stuck. I turned it on yesterday to check the battery life because I haven't used it in a couple days and it was at 15% and everything was fine. I remember hearing the notification sound last night so I looked and said battery was dead so I plugged it in and left it last night. This morning I noticed the screen was on, even though it was a black screen.
Now after I hold the power button for 10 seconds it goes to the "Touch the future of reading" page for a few seconds, next it shows "loading..." in white letters in the middle of the screen for less than a second before going to the screen where "ANDROID_" is spelled in small light blue letters vertically in the upper left hand side of the screen. It will stay at this "ANDROID_" screen indefinitely until the display goes black after about 10 minutes, or until I hold the power button for 10 seconds to turn it off.
Any ideas how I can fix this or get it to boot up? I don't understand why it has worked great for two months and then out of the blue quit working? I haven't installed anything, modded anything, or stuff like that before it quit working. In fact the last few days before it quit this morning all I have done is turned it on briefly to check the battery level (because I decided to monitor it more, loses about 25% battery per day just sitting turned off). Any help is greatly appreciated, really have enjoyed using the NC as an android tablet.
rjl2001 said:
Close to two months ago I installed the latest Phiremod ROM onto my Nook Color. (Phiremod 7 I think) I followed a webpage tutorial and referenced XDAdevelopers instructions. Has been working excellent for the past couple months. Got everything set up and working great... youtube, hulu, netflix, etc. Now all of the sudden my Nook Color won't bootup but gets stuck. I turned it on yesterday to check the battery life because I haven't used it in a couple days and it was at 15% and everything was fine. I remember hearing the notification sound last night so I looked and said battery was dead so I plugged it in and left it last night. This morning I noticed the screen was on, even though it was a black screen.
Now after I hold the power button for 10 seconds it goes to the "Touch the future of reading" page for a few seconds, next it shows "loading..." in white letters in the middle of the screen for less than a second before going to the screen where "ANDROID_" is spelled in small light blue letters vertically in the upper left hand side of the screen. It will stay at this "ANDROID_" screen indefinitely until the display goes black after about 10 minutes, or until I hold the power button for 10 seconds to turn it off.
Any ideas how I can fix this or get it to boot up? I don't understand why it has worked great for two months and then out of the blue quit working? I haven't installed anything, modded anything, or stuff like that before it quit working. In fact the last few days before it quit this morning all I have done is turned it on briefly to check the battery level (because I decided to monitor it more, loses about 25% battery per day just sitting turned off). Any help is greatly appreciated, really have enjoyed using the NC as an android tablet.
Click to expand...
Click to collapse
I had a similar problem, or at least similar symptoms (but it was caused by an ID-10-T error) and I ended up just booting into recovery and restoring my last nandroid (oddly enough this nandroid didn't include any of the apps I had installed and it has been a while since my last TiBa so I have a lot of "manual recovery" to take care of).
So I would go ahead and try to restore. Sorry I can't be more help.
Drachen, thanks for the reply. I'll take any advice or information anyone has. I would definitely be happy to restore, losing all my apps is better than having a bricked NookColor lying around.
Do you know where I can find directions on how to do a restore? I'm not too technical when it comes to this stuff, I've just rooted it a couple different times because I had some clear and precise step by step instructions of exactly how to do so. I know I'm unable to boot into the recovery mode like I was able to do before when I was first installing Phiremod. Also since it has been a couple months a lot of the steps and details are not fresh in my mind.
There was no version7 2 months ago.
Sent from Nook Color on Phiremod 6.3 @1.3Ghz
OK, I guess I don't remember which version is installed then.
Well I am able to boot into ClockworkMod Recovery v3.0.2.8 , so this gives me some hope now. However, I'm still unsure what the next course of action is. Any reboots still get hung up on that one screen. I had erased the Phiremod files from the SD card, so I don't think I can reboot using it, nor do I have any backups listed on ClockworkMod.
rjl2001 said:
OK, I guess I don't remember which version is installed then.
Well I am able to boot into ClockworkMod Recovery v3.0.2.8 , so this gives me some hope now. However, I'm still unsure what the next course of action is. Any reboots still get hung up on that one screen. I had erased the Phiremod files from the SD card, so I don't think I can reboot using it, nor do I have any backups listed on ClockworkMod.
Click to expand...
Click to collapse
Download the phiremod zip here, put it on the root of your SD card, and then boot into recovery>install zip from sd card>choose zip from sd card>Phiremod zip.
Finally figured it out after a few weeks of a Nook paperweight and hours of googling and trying different methods. What wound up working for me was totally restoring it back to stock. This website "Maurice Mongeon - Nook Color: Recover Any Bricked Device/return to stock" had great step by step directions on how to do it, and it was actually easy. Now I just need to figure out if it is worth rooting again, or would it just fail out of the blue like it did this time?? Anyways, thanks for the help.
First off, thank you to all. Normally i can search and lil reading and be well on my way. But this Droid X has driven me nuts. Its now 2am and i bow to the guru's. So i'll start from the beginning, I got Droid x from a second hand person today, i took home and formatted to stock via normal menu. I then activated phone as it makes you. then proceeded to root with pete 1 click. which worked instantly. So then i added koush installer, which gives two options. Top option tells you success right after you click it. Well then in my wisdom used titanium backup to restore my fiancee's apps to this phone. Her old one was a original droid. Didn't think i added any of the system data but i must have, cause after a reboot a while later. the phone was in a no service state. Couldn't check about phone or really any menu after the initial settings menu at home page. So then after a lot of bad words, =) end up doing a factory reset again. Which is what got me to new problem.... The phone isn't rooted & when trying to root it fails on restarts because after RED Logo appears screen faintly is lit & hangs forever. But if pull battery and turn on, seems to be just fine. Also seems to do it only when plugged in usb to pc. Which can't reroot without the connection right? or does zroot work? So my thinking is that the person before put a bootloader on here, and i didn't know. So perhaps there is now two partial installs of loaders. that a factory reset/wipe won't fix. & having never had to do anything crazy on my Droid 3 or the other 2 original droids im really frustrated at myself. cause im sure im missing a very simple item in this process. Thank you for reading this jumbled problem as i typed it, & appreciate any and all responses.
This is a Nexus 6P (32GB) I rooted shortly after getting it (new) in September 2016, and updated to stock 7.1.2 in August 2017, but I otherwise haven't modified it from its out-of-the-box state.
Until recently, I'd never experienced any issues - no random reboots, battery was still pretty good, etc. Then last week, the phone rebooted suddenly, and appeared to "boot loop". I hadn't yet heard about the issues the 6P has with this so I powered it down, left it alone for a while, then turned it back on later, booted without incident, and forgot about it.
Last night it happened again, at which point I searched and learned of the dreaded "boot loop of death" the 6P specifically has had issues with. Hoping that wasn't the issue, I again powered down and tried it this morning, and it only stayed awake for about 5 minutes before going into boot loop. At this point I looked up and applied the fix described in this thread, but to my dismay it had no (visible) effect - I still see the initial "bootloader is unlocked" screen, then the google + open lock icon, repeat ad nauseum.
About all I can do with the phone right now is load into fastboot. The phone has data on it I'd really like to recover, is there a way I can do that from there? If not, is there any way to connect with ADB without getting through a full boot? Are there alternative boot loop fixes, alternative steps to the fix described? I've read several threads here and can't tell if any apply to me, and can't find any answers to the above.
I've accepted that the phone is probably never going to be the same again but I need to get my data off there and do a few quick things before I consign this one to paperweight duty. Thanks in advance
chmmr said:
This is a Nexus 6P (32GB) I rooted shortly after getting it (new) in September 2016, and updated to stock 7.1.2 in August 2017, but I otherwise haven't modified it from its out-of-the-box state.
Until recently, I'd never experienced any issues - no random reboots, battery was still pretty good, etc. Then last week, the phone rebooted suddenly, and appeared to "boot loop". I hadn't yet heard about the issues the 6P has with this so I powered it down, left it alone for a while, then turned it back on later, booted without incident, and forgot about it.
Last night it happened again, at which point I searched and learned of the dreaded "boot loop of death" the 6P specifically has had issues with. Hoping that wasn't the issue, I again powered down and tried it this morning, and it only stayed awake for about 5 minutes before going into boot loop. At this point I looked up and applied the fix described in this thread, but to my dismay it had no (visible) effect - I still see the initial "bootloader is unlocked" screen, then the google + open lock icon, repeat ad nauseum.
About all I can do with the phone right now is load into fastboot. The phone has data on it I'd really like to recover, is there a way I can do that from there? If not, is there any way to connect with ADB without getting through a full boot? Are there alternative boot loop fixes, alternative steps to the fix described? I've read several threads here and can't tell if any apply to me, and can't find any answers to the above.
I've accepted that the phone is probably never going to be the same again but I need to get my data off there and do a few quick things before I consign this one to paperweight duty. Thanks in advance
Click to expand...
Click to collapse
I have the exact same issue. I run the same version operating system as you have an unlocked bootloader otherwise have not modified the typical system install. I did already have the fix applied from an earlier incident but now it is boot looping and won't stop. I have red threads here and there that have advised to apply heat to the phone and that might get it to boot at least to get your data off. Myself I have had no such luck with this technique but perhaps it will work for you otherwise I have since moved on to the OnePlus 6t. A very awesome replacement not to mention at a decent price for more horsepower and storage
Sent from my ONEPLUS A6013 using Tapatalk
Just in case it helps anyone with this phone and issue, I was able to get a couple more boots out of it, enough to rescue some data, by doing the "15 minutes in the freezer in a ziploc bag" trick.
RIP Nexus 6P, shame about the BLOD!