This has happened to me a few times, but when I was flashing the Savaged-Zen RC2 today, my phone booted to the white HTC Evo 4G splash screen, the screen then went black, it then rebooted to the splash screen again before finally going to the boot animation and loading fully. Why is it doing this? After a successful boot, it never does it again, but all these phones bricking lately has me nervous. It did the same thing last week with Miui. I've noticed no ill effects, but it's done this with Mikfroyo (a few months ago), MIUI, and now Savaged-Zen. Ideas?
We've discussed this before here:
http://forum.xda-developers.com/showthread.php?t=1028744&highlight=double+white
I have this problem too but I'm not incredibly concerned about it. It did go away for a minute for me, but it's back. Even after I wiped everything that AmonRa 2.3 would let me and did a completely clean install of CM7. No idea. I really do think it has something to do with flashing Savaged Zen though since I never had a problem with it before I flashed that. I may be a bit crass on placing blame there but that's one thing that we've all had in common.
Thanks for the heads up. I tried searching, but I didn't come across that thread probably because of the wording.
Sent from my PC36100 using Tapatalk
If I remember correctly, this is happening with the latest S-Z kernel. It's because of the built-in sbc/no-sbc toggle. Not a bug ... simply designed that way.
Related
So i bought my incredible the second day they were released, and rooted it when unrevoked came out with their first one-click root program (so needless to say im not exactly a "new" root user). i've ran a couple roms, and lately have run stock leaks w/ added .zips for a little customization (about the past three months or so). i've been on the latest leak for like a month ish (i think its the latest one) possibly little bit longer than that. i never had a random reboot or even really any lag up, which was really amazing. then, i tried to install a custom flat black notifications bar, and i installed the update zip through recovery but it didnt do anything.
about two weeks later, i installed that new status bar power menu thing, and started to get the occasional random reboot and bog up. no really enough to really be a problem, but tonight right before bed my phone started boot looping after a random reboot (it would boot for a min or two then reboot after a lockup). so i pulled the battery and powered back on. then it loaded to the lockscreen, but every single app that should have started at startup began to repeatedly force close, so i couldnt use the phone. i tried three times but it happened every time. im nandroiding now, im sure that'll fix the problem, but any ideas what caused this? thanks!
just happened again on ruby 2.0.0, but this time all of the apps force closed AND the "click android to start" setup screen came up. I got a random reboot (which i rarely to never have), pulled battery and powered back up, it loaded to lockscreen, then it went into a soft reboot and froze at the looping bootscreen, then once i pulled battery again and powered up, i got the crashes. any idea what it is? this time, it did happen like 15 min after i had dropped my phone from about 2 feet off the ground, i guess that could be it? idk
For what it's worth, I was running 2.3 and it wouldn't mount internal or SD. This happened even after installing other ROM's. I downloaded the latest RUU, unrooted, and started from scratch.
I reformatted the SD card too. I re-rooted, and restored my SD backup. I re-downloaded the ROM I wanted, and installed it. It fixed the weird issues I was having. You may want to consider starting over from scratch.
Sent from my Incredible using XDA App
I've been having issues with the phone turning off randomly and restarting, seems to do it when it gets hot. Also the phone not responding to power button. Doesn't matter which rom I flash it keeps happening. Thinking about converting back to stock to see if it helps. But I'm unsure why this started happening all the sudden any one else have similar issues??
How often is it happening? Often enough that you may be able to troubleshoot it? Such as.. turn of gps, mobile data, sync, then slowly add them back in one at a time to see what could be causing the problem.
Swyped from my Raided Evo
Also, are you under clocking or over clocking your kernel?
Swyped from my Raided Evo
My wife's Evo had that exact same problem, but hers is unrooted. We brought it into Sprint and she's getting a brand new phone tonight. They tried running diagnostics on it, but came up with nothing, so that was their last resort...
This seems to only happen to me on aosp roms and not sense.
Sent from my PC36100
[Q] My boot loops don't taste good...with or without milk...what is the reason?
My real questions are:
Has anybody experienced my experience and how did they solve the issue?
and
Can someone help me diagnose the issue?
I am seeking help on this topic also.
I have battled and one once before but don't know what was the actual fix.
I tried in the past, couple weeks ago, to upgrade to the new 2.3 roms and have had a lot of trouble with the ol' "random reboots". I don't recall what rom exactly that I tried to put on there but I don't believe that the rom was the issue in this situation do to flashing other roms and encountering the exact same reboot issues.
I originally undervolted using vipermod, updated to the new radios from the present "All Radios" post that was grouped together and then flashed a kernal over the rom that I was trying to use.
I got it booted up no problem, went through the setup and then when it was trying to get the reception and/or 3g established it rebooted...the white HTC boot screen appeared and rebooted over and over again.
I tried reflashing the rom, flashing a different rom and so on.
I sort of ruled out the radios after downgrading them and not getting any different results and started to think it was an overheating issue because when I would leave it off for a while it would work longer before the boot party began.
I read something on another thread that when you remove the battery for so long and boot it back up, it clears the internal memory or something similar to that. I searched the market for a boot logger program and found bootlog, I believe that was the name, and checked the log after pulling the battery and letting it boot up all the way. After reviewing the log I noticed that it had stuff like lowmem, deathpening, killing and what not. I then came to the conclusion that it was more than likely the memory, not a clue if it is internal or talking about the temporary stuff that it may store on the sdcard.
I then decided to check out the partitioning of the sdcard. I decided to raise the swap to something like 1 gig and the ext to 2 gig.
I loaded up CM7, nothing extra, and all was good besides maybe one or two reboots that ended up booting all the way up instead of doing the loop at the white HTC screen.
But now, I followed the instructions that was left on http://forum.xda-developers.com/showthread.php?t=1071547&page=1161 (no blame to the post or rom, just a reference) so I can try out a new sense rom...and...if you don't know by now...mayhem/boot loops. I cannot upload any of the logs because I followed the partition instructions.
I have upgraded and downgraded the PRI and the radios with no luck, I am now going to try the partition swap size again and report back.
I am writing this prior so I can get some helpful suggestions coming my way in the mean time, in case me and the Captain can't make this happen, or be able to post my method to fix my scenario so others may benefit.
Thanks in advance.
EDIT: I have S-OFF, HBOOT 0.97, radio 2.15.00.11.19
I still have been having tons of issues and I've gone back to roms I ran 6 months ago n still having the same problem. It just randomly shuts off and turns back on sometimes like 5 or 6 times in a row. This is getting very frustrating I'm gonna have to put it back to stock and take it in. I want to smash my evo with a hammer and then blow torch the sh*t out of it.
I'm having the same problem, only with the Inspire 4G though. I notice mine only happens when the screen turns off.. I'm thinking mine might be an underclocking issue or something because if I have an unread message or if the led is on or flashing at all, it works fine.. Wait, no, it just did it again fml
This is why I dont want to upgrade my radios, you say you ruled out those, but your phone is still jackin up on old roms.
It jus seems I never see an issue that cant be solved by reflashing the rom or a redownload the rom and flash, unless......you mess with the radios, then u get issues like this..im no expert, but this is what I see.
....Radios scare me!
If it was me I would proly unroot it and bring it in, or
Copy SD card to your PC.
Format SD.
Run an RUU that matches your original radios.
Copy SD card data back.
Re-root.
Should be brand new then....
EDIT: Scratch that I wouldnt unroot and bring it in. Easier to runn the RUU like I said
Sent from my PC36100 using XDA App
Never flashed a radio unless a rom came packaged with one... Couldn't tell you which one because I've flashed a bunch already seeing if that was the problem or not. I'm partitioning my SD card right now to see if that helps.. Oh, and I bought my phone off eBay cause AT&T sucks at life and it's not a year wait anymore to upgrade. God how I miss Cingular.
Think i figured it out on my end... I don't think my phone likes to be underclocked so I bumped up the mhz a little for screen off and I haven't had a problem yet
Sent from my HTC Desire HD using XDA Premium App
Again I spoke too soon
I swear I tried Google search on this, but to no avail.
I finally talked The Wife into letting me root her phone, all seemed to go well. However, when I rebooted, it started having 2 different alternating touchscreen issues:
1. No response at all
2. Mirrored right to left, including capacitive buttons. Search is home, home is search, presses on left register on right of screen.
Any ideas?
Sounds like a rom issue, have you tried different roms to see if it changes?
-Nipqer
That's what's interesting, I never flashed a ROM. After rooting it, and rebooting, I was about to flash CM7, but the touch screen was dead, so I pulled the battery and let it sit a minute, and when it came back on, touch was mirrored. Rebooted again, touch was dead again.
I'll try flashing cm7 tonight.
Thanks. Looks like flashing cm7 fixed the issue. I had midnight paranoia after rooting an HTC phone for the first time. Samsung phones are so much easier to root. :beer:
Hey, this is my first post so let me first say sorry if I'm doing something wrong here and thanks a ton to anyone who can help me out in some way...
So long story short - I just looked down at my phone and it was on the white "Evo 4G" screen, so I thought it must have just restarted for some reason (which has never happened, but I usually try to remain optimistic) and I went about my business...about 10/15 minutes later it was still on the white screen, so I pulled the battery and left it out for a minute and then tried turning it on again. No luck-right back being stuck at the white screen. So I pulled the battery again and waited about a half hour before trying with my other battery, which is definitely fully charged and cool, and it is still sticking at the white screen. I don't know what the heck is going on. Anyway, I have an Evo 4G running Warm 2.2 with some netarchy kernel of some sort (one that is suggested on his thread) if that even matters. I can get into recovery, but that's actually another set of issues in itself so if this can be solved without doing a restore I'd prefer that. Okay, sorry to give too many details. Thanks again to anyone who has any thoughts!
this is why you make nandroid backups
If you do happen to have a recent nandroid backup you might wanna restore to that, otherwise the only other other option I can suggest which may still not work but it's worth a try...
recovery > wipe cache > wipe dalvich cache > flash the same warm 2.2 zip you are running and do not flash the custom kernel just yet, see it that gets you to boot
colindelong said:
Hey, this is my first post so let me first say sorry if I'm doing something wrong here and thanks a ton to anyone who can help me out in some way...
So long story short - I just looked down at my phone and it was on the white "Evo 4G" screen, so I thought it must have just restarted for some reason (which has never happened, but I usually try to remain optimistic) and I went about my business...about 10/15 minutes later it was still on the white screen, so I pulled the battery and left it out for a minute and then tried turning it on again. No luck-right back being stuck at the white screen. So I pulled the battery again and waited about a half hour before trying with my other battery, which is definitely fully charged and cool, and it is still sticking at the white screen. I don't know what the heck is going on. Anyway, I have an Evo 4G running Warm 2.2 with some netarchy kernel of some sort (one that is suggested on his thread) if that even matters. I can get into recovery, but that's actually another set of issues in itself so if this can be solved without doing a restore I'd prefer that. Okay, sorry to give too many details. Thanks again to anyone who has any thoughts!
Click to expand...
Click to collapse
I would suggest wiping cache and dalvik cache and trying to boot up the phone again. I have ran into this a few times using the fastboot option, otherwise never had the problem.
Phone decided to start acting strange.
Barely responsive like processor went bad or it has no ram.
I reflashed SPH-D700-FC09-8Gb-REL.tar.md5 though odin thinking it might clear it up like its a kernal issue.
But now I got stock bootloader and I cannot even use the options in it It wont boot otherwise, just sits at the S logo and the graphic plays really really slow. 1 frame every 5 seconds or so.
not sure what's going on.
I don't keep up on the kernals and roms and all that, I was running a rom from june last year and was happy with it.
What am I missing?
A lot of the development links are starting to go bad for things like roms and such.
Okay. so after flashing this and doing that and messing with this and that.
I can get it to boot now. Sometimes it works good, other times its boot hanging on me.
When I do get it to boot, the screen will not respond.
So if I flash the FC09 stock rom, it will let me touch the button on the first pop up, but after that the screen is locked out or something.
I found a clean rom and installed that.
Looks like the rest of my files and such are already the same ones that are currently being used, no major advancements in the last year. That makes it easy.
So currently getting boot lockup after flash and reset. Not sure whats going on there.
I just dont' do this often enough.
And the screen lock up.
Not sure on the screen lock up after clean kernal install.
It's re-flashing fc09 again and I'm tired and going to bed.
Touch screen only working when keyboard slid out.
Very weird.
Not really getting anywhere with this.
First fc09 install will boot.
Screen will not work right.
after restart wont move past samsung screen.
After a deodex install and CWM, it acts really slow again.
I'm going to guess it has memory corruption.
During one of my installs the phone worked like normal and after the deodex update it started working laggy again and has been that way ever since.
ODIN?
To clarify, you used ODIN to flash FC09? In case not, instructions are here
http://forum.xda-developers.com/showthread.php?p=24694921
Also, I think other people have reported general weirdness on their OG Epic 4g's when the battery is bad. There's a battery thread in the Q/A forums.
good luck
pentium0 said:
To clarify, you used ODIN to flash FC09? In case not, instructions are here
http://forum.xda-developers.com/showthread.php?p=24694921
Also, I think other people have reported general weirdness on their OG Epic 4g's when the battery is bad. There's a battery thread in the Q/A forums.
good luck
Click to expand...
Click to collapse
Wasn't a bad battery. I have multiples.
Just went and got a new phone. Something was wrong with the hardware.
Thanks for the help though.
sarinhighwind said:
Wasn't a bad battery. I have multiples.
Just went and got a new phone. Something was wrong with the hardware.
Thanks for the help though.
Click to expand...
Click to collapse
If you run into it again you may have a bad download or cable. Bothe resulted in all the errors you where discribing. Solved it with a good download and a different cable.
Expereanced slow 'S' boot and boot loops with a bad cable mainly and bad downloads caused all sorts of slowness, hangs, unresponsiveness and one moment of very warm lap.
Sent from either my SPH-D700 or myTouch3Gs using XDA app
"it never hurts to help"
I had an issue where my modem wouldn't work...ever. it was totally bricked. In my quest I found the pc re-recognizes the device when I used a different usb cable,(from my note 2) & I changed the com port in device manager. I know its lame to pump my own stuff but at the end of my thread in this section, I have a pic that shows how & where you can pick your own com port in advanced settings in windows. I hope any of this helps.