Related
When HTC Evo 4G is in recovery and you press reboot it has a bunch of weird looking lines that are diffrent colors and this used to never happpen. I do not know how to fix this or if anyone has had this problem my phone seems to still run fine but i am curious of what it is if anyone knows how to fix this or knows what it is please help me i have attaced a picture of it please take a look
Originally Posted by Unknownforce
I have this same thing with Clockwork recovery 2.6.0.1, recovery works just fine, flashing ANY files, (tried roms, kernels, application installs, theme changes etc...) no issues other than the actual display when it reboots...
This is exactly what is happening to me does anyone know how to fix it
what?.........
thin about your question, find out what you are talking about, look in the correct thread....
stuff to think about next time
1. what recovery are you talking about
2. what rom are you using
3. what are you trying to do when this happens
You're going to get drilled if I don't say this, so please post questions in the Q&A section from now on (some people are REALLY uptight about that :\)
Anyhow, is it just an aesthetic thing? Or is it actually causing problems?
Nygel said:
what?.........
thin about your question, find out what you are talking about, look in the correct thread....
stuff to think about next time
1. what recovery are you talking about
2. what rom are you using
3. what are you trying to do when this happens
Click to expand...
Click to collapse
Cut him some slack...he's new.
And how would a ROM affect recovery?
mkeller96 said:
When HTC Evo 4G is in recovery and you press reboot it has a bunch of weird looking lines that are diffrent colors and this used to never happpen. I do not know how to fix this or if anyone has had this problem my phone seems to still run fine but i am curious of what it is if anyone knows how to fix this or knows what it is please help me i have attaced a picture of it please take a look
Click to expand...
Click to collapse
Which recovery are you running?
sorry how do i delete this form i made a new one in questions
I have this same thing with Clockwork recovery 2.6.0.1, recovery works just fine, flashing ANY files, (tried roms, kernels, application installs, theme changes etc...) no issues other than the actual display when it reboots...
Unknownforce said:
I have this same thing with Clockwork recovery 2.6.0.1, recovery works just fine, flashing ANY files, (tried roms, kernels, application installs, theme changes etc...) no issues other than the actual display when it reboots...
Click to expand...
Click to collapse
this is exactly what im taking about
mkeller96 said:
sorry how do i delete this form i made a new one in questions
Click to expand...
Click to collapse
Don't worry, the mods will take care of it for you
Many things have been changed in new recoveries to make them run faster and work a little smoother.
(Kernel updates within recovery, etc)
I have noticed this too and it is not an issue, don't worry it's common.
its just called screen tearing the easiest and IMO best fix would be to switch to amon ras recovery and itll go away just like that
Yea when I flash clockwork recovery the other day to dl a cm7 nightly it did that and now I'm back to amon ra so my guess is its just cw
Sent from my PC36100 using XDA App
mkeller96 said:
When HTC Evo 4G is in recovery and you press reboot it has a bunch of weird looking lines that are diffrent colors and this used to never happpen. I do not know how to fix this or if anyone has had this problem my phone seems to still run fine but i am curious of what it is if anyone knows how to fix this or knows what it is please help me i have attaced a picture of it please take a look
Originally Posted by Unknownforce
I have this same thing with Clockwork recovery 2.6.0.1, recovery works just fine, flashing ANY files, (tried roms, kernels, application installs, theme changes etc...) no issues other than the actual display when it reboots...
This is exactly what is happening to me does anyone know how to fix it
Click to expand...
Click to collapse
mine does the same thing but it works fine i was using clockwork until updated then went to the new RA but now it wont do backups and im back at clockwork and i get the same nasty looking lines, but as you said my phone as well as backups are working just fine..
kybeck55 said:
mine does the same thing but it works fine i was using clockwork until updated then went to the new RA but now it wont do backups and im back at clockwork and i get the same nasty looking lines, but as you said my phone as well as backups are working just fine..
Click to expand...
Click to collapse
what do you mean Amon wont do backups and also if you go into the Amon recovery thread there is discussion about screen tearing. I know people use clockwork but after trying both IMO Amon does it all and seems to be causing way less issues than Clockwork...
Hello all...I am currently running cm6....everything works great...mytouch slide 3g rooted, and s-off with alpha-rev
I downloaded the cm7 rc2 and the correct gapps as well...gb-20110307....I reboot into recovery, and select wipe data/factory reset etc....I clear cache etc....I then choose install from sd card....pick the cm7....it says installation complete, I then do the same for the gapps...says it installed....then I reboot phone....and it just sits at the s-off alpharev boot screen.....no cm android screen comes up.....ive tried like 5 times now and I wait like 20 minutes each time, but nothing evr happens.....Can someone give me some advice?...what the heck am I doing wrong?.....Thanks so much for your time.....DIrtylarry
Are you running the latest clockworkmod? No clue if it makes a difference, but an idea.
ummm....I think so?.....I guess I dont know for sure.....link maybe?....
Download Rom Manager from the market or make sure its updated if you already have it installed.
Open Rom Manager and hit "Flash ClockworkMod Recovery". Then try again.
Try the 0120 gb gapps, some people have had issues with the latest 0307 ones.
ok....so i reinstalled 6.0 cm and now want to go to 7.....so clockworkmod recovey.....then wipe etc....then 7.0 from sd card.....and then gapps?....what i find weird is that 6.0cm has a yellow status bar that goes across screen when installing, and neither of the 7.0 rc and rc2 have this, and neither will install.......make sense?,,ty
Do you have custom MTD partition sizes setup? If so, it's possible that your system partition isn't large enough..
Have you tried pulling a logcat while booting the phone?
JTB
Had a prob like this once b4 on mt3g and I fixed by putting latest radio....do u have the latest radio 7.15 cux cm7 have wifi calling and hotspot.....just putting in my 2 cent
thanks for the advice guys....after 6 hours of no solution i decided to go with a different rom....and EVERYTHING worked instantly...I'm sure all this has to do with a size constraint on the mtd?......Now....I need to research this and figure out how to get more space on the internal....as I am almost full again with even moving apps to sd........if I can figure this out...Ill be a happy androider....lol....
dirtylarry10 said:
thanks for the advice guys....after 6 hours of no solution i decided to go with a different rom....and EVERYTHING worked instantly...I'm sure all this has to do with a size constraint on the mtd?......Now....I need to research this and figure out how to get more space on the internal....as I am almost full again with even moving apps to sd........if I can figure this out...Ill be a happy androider....lol....
Click to expand...
Click to collapse
Do what I do and delete all the ringtones/notfications/alarms that you don't use. What radio are you on?
Sent from my T-Mobile myTouch 3G Slide using Tapatalk
Hey everyone.
I know there's a couple other threads with this problem, but none of them included their last_kmsg files. It took a bunch of tries before I could stay booted up long enough to grab it, but I have one.
I'm getting a significant number of reboots on my EVO. Like almost unusable at times. It seems fairly random, although there's a slight suspicion is has something to do with the GPS. Maps has been a crash-cause before and the most recent bout last night was brought on by foursquare. (the annoying part is I had just used 4sq fine 30 minutes prior with no issues. Then, booted it up, refreshed locations and my phone was unusable for hours.)
I've done all the standard things. Fix permissions, wipe cache, wipe dalvik, wipe data/system, reinstall the latest CM7 build (update-cm-7.0.2.1-Supersonic-signed.zip), wipe cache, wipe dalvik. I entered my google account info but told it not to sync anything. It is now rebooting less than a minute after it starts up. I haven't installed any apps at all since this most recent wipe/reload of CM7. It reboots with and without the sd card installed.
I'm at a loss here and getting incredibly frustrated. Many replies say it's as easy to fix as wipe everything and re-do it. Obviously something abnormal is screwed up on my phone and I can't figure it out.
Here's the pastebin from this morning: pastebin.com/Ki7H8bH3 (Crap, I don't post here enough to be allowed to post links. Just add the http part to that.)
And then when I got awake enough, I did another complete wipe/reload. The rebooting is even worse now, it's taken me almost an hour to get to a point I can install es explorer to try and pull another file. And when I did, it was blank.
Any ideas?
Thanks!
1. Go to the link below and download the PC36IMG.zip file for amon RA v2.3 and place it on the root of your SD card.
http://forum.xda-developers.com/showthread.php?t=705026
2. Shutdown your device.
3. Simultaneously press the DOWN volume button and the power button until your device starts. There will be a short pause and then a few lines of text will scroll across the screen. Afterwards, the bootloader will automatically detect the PC36IMG.zip file and prompt you to install it. Follow the easy prompts to install. Installation will take less than 10 seconds to complete. Afterwards, reboot into your new recovery. Go to the backup/restore menu and make a nandroid backup of your current setup.
4. Now go to the wipe menu and wipe EVERYTHING in it EXCEPT the SD card.
5. Go to the flash menu and flash the rom you desire to flash.
On many occasions, reflashing the recovery solved rebooting issues and hopefully, it will solve yours.
posting & replying via the XDA Premium app.
Hi dougjamal,
Thanks for the reply.
I've made some progress. Last night I had done a majority of what you suggested, with installing amon RA. I've also just formatted my entire sd card just to be sure.
I haven't tried wiping things other than cache and dalvik, so I'll try that.
My progress I mentioned is that I had CM7 up and running until I flashed a new kernel and gapps in there. So I guess I'll just stick with the stock CM7 kernel, try your extra wiping and see how that works.
Thanks!
grifta67 said:
Hi dougjamal,
Thanks for the reply.
I've made some progress. Last night I had done a majority of what you suggested, with installing amon RA. I've also just formatted my entire sd card just to be sure.
I haven't tried wiping things other than cache and dalvik, so I'll try that.
My progress I mentioned is that I had CM7 up and running until I flashed a new kernel and gapps in there. So I guess I'll just stick with the stock CM7 kernel, try your extra wiping and see how that works.
Thanks!
Click to expand...
Click to collapse
You're very welcome. Sorry for the delayed response. I was having a late lunch and then drove home. Anyway, keep us informed of your progress and enjoy the rest of your day.
posting & replying via the XDA Premium app.
No worried on any delay, just glad to have someone that took a read and time to reply!
Ugh, it's the randomness of this that has me so frustrated. I thought I had a good install again, I left it sit on the "touch the android" screen for a few minutes and it stayed on. Made it through the setup process ok. I allowed the setup to "auto-download" a handful of the google apps it asks if you want. Once they got to about 38%... boom, restart.
So I did another toooootal wipe and I'll manually install those apps one by one. We'll see...
dougjamal said:
1. Go to the link below and download the PC36IMG.zip file for amon RA v2.3 and place it on the root of your SD card.
http://forum.xda-developers.com/showthread.php?t=705026
2. Shutdown your device.
3. Simultaneously press the DOWN volume button and the power button until your device starts. There will be a short pause and then a few lines of text will scroll across the screen. Afterwards, the bootloader will automatically detect the PC36IMG.zip file and prompt you to install it. Follow the easy prompts to install. Installation will take less than 10 seconds to complete. Afterwards, reboot into your new recovery. Go to the backup/restore menu and make a nandroid backup of your current setup.
4. Now go to the wipe menu and wipe EVERYTHING in it EXCEPT the SD card.
5. Go to the flash menu and flash the rom you desire to flash.
On many occasions, reflashing the recovery solved rebooting issues and hopefully, it will solve yours.
posting & replying via the XDA Premium app.
Click to expand...
Click to collapse
Seems like this gets posted quite often, huh??? lol
Don't rule out a corrupt download. If you have the time, download both Salvage-Mod 1.2.1 and the gapps zip from http://www.salvage-mod.com/node/4. If you like CM7, you may like Salvage-Mod. It is pure gingerbread. If you decide to flash it, see whether or not you get bootloops with it.
posting & replying via the XDA Premium app.
HipKat said:
Seems like this gets posted quite often, huh??? lol
Click to expand...
Click to collapse
Indeed, my friend...lol...but it works.
posting & replying via the XDA Premium app.
HipKat said:
Seems like this gets posted quite often, huh??? lol
Click to expand...
Click to collapse
It does and it wish it was that easy. It's frustrating to read that others seem to have no issues at all yet when I follow those directions, which are everywhere, nothing seems to work.
dougjamal said:
Don't rule out a corrupt download. If you have the time, download both Salvage-Mod 1.2.1 and the gapps zip from http://www.salvage-mod.com/node/4. If you like CM7, you may like Salvage-Mod. It is pure gingerbread. If you decide to flash it, see whether or not you get bootloops with it.
posting & replying via the XDA Premium app.
Click to expand...
Click to collapse
I re-downloaded CM7 this morning thinking that might be the issue, but it hasn't seemed to help. I'll give a different rom a try probably, maybe there's something other than CM7 I'd be content with.
Whelp, I downloaded SalvageMod and their gapps. Wiped everything, installed salvage, installed gapps, rebooted.
I got through set-up, was ok for a couple minutes, then as I was going into my contacts to see if they had sync'd yet... reboot.
This makes me think this can't be a ROM issue.
Any other ideas?
Does the same thing happen when you run a stock (or close-to-stock) rom? Main reason I ask is that this might actually be some sort of hardware problem, but one of the best ways to test for that is to be running on stock software. I wouldn't necessarily suggest flashing an RUU to get to the latest official release, but there are stock rooted roms out there that you could try.
You probably went with CM specifically to get away from Sense and the default HTC stuff (that's most people's reasons anyway), but if you flash a stock rom and it's still rebooting like that then I'd say chances are REALLY good that it's hardware and that you'd have grounds for getting a replacement phone (just remember to unroot first.)
And if it stops randomly rebooting on you then you'll have at least narrowed things down a bit.
jesuspgt said:
Does the same thing happen when you run a stock (or close-to-stock) rom? Main reason I ask is that this might actually be some sort of hardware problem, but one of the best ways to test for that is to be running on stock software. I wouldn't necessarily suggest flashing an RUU to get to the latest official release, but there are stock rooted roms out there that you could try.
You probably went with CM specifically to get away from Sense and the default HTC stuff (that's most people's reasons anyway), but if you flash a stock rom and it's still rebooting like that then I'd say chances are REALLY good that it's hardware and that you'd have grounds for getting a replacement phone (just remember to unroot first.)
And if it stops randomly rebooting on you then you'll have at least narrowed things down a bit.
Click to expand...
Click to collapse
Hey jesuspgt,
I haven't tried that yet. I'll look around for a rooted stock ROM later and give that a shot.
My current status is back to uncertainty. At the moment, my evo has been sitting here fine, not rebooting, for the past hour or two. It's still the Salvage ROM I first installed (i.e. I haven't reinstalled it since it rebooted). Now I haven't really used it any, so it might go to hell as soon as I do that, but for now, it's on and only had that one (maybe two, I can't keep track...) initial reboot.
That's what makes it tricky to diagnose. I know using any custom ROM runs the risk of loosing stability and all ROMs probably produce a reboot here and there. Tough to tell if it's just a "comes with the territory" type of reboot or an actual problem.
Even though I'm sure there's some CM features I'll miss, maybe Salvage is my answer.
Thanks!
*sigh* Well I decided to try using some apps and guess what... reboot.
All I was doing was trying to play a game of Androminion, which is about as basic and not-tasking as possible, so I can't imagine that's what crashed things.
The only thing I can think of that you *may* need to do is reflash your hboot and/or your baseband, PRI & NV from within recovery. You can download it from the link below.
http://forum.xda-developers.com/showthread.php?t=715485
posting & replying via the XDA Premium app.
dougjamal said:
The only thing I can think of that you *may* need to do is reflash your hboot and/or your baseband, PRI & NV from within recovery. You can download it from the link below.
http://forum.xda-developers.com/showthread.php?t=715485
posting & replying via the XDA Premium app.
Click to expand...
Click to collapse
Excellent, I'm going to try that. My hboot is still 0.93!
Hey dougjamal,
Just wanted to drop an update. I know how annoying it is to help someone out and never hear how things ended up!
Who knows what combo helped, but I'm fairly stable now. After updating my hboot, I flashed to Sprint Lovers, did the ##GPSCLRX# trick and then flashed to the latest nightly of CM7 (63 I believe). Only one or two crashes and one bootloop since then.
Of course, as luck would have it, a new problem showed up in the form of a dead spot on my touch screen. Right about where the "Clear" button is for notifications, that entire strip across the phone won't respond to touch. I was hoping it was a nightly issue, but I switched to a different rom and the issue was still there. Looks like it's going in for a warranty claim after-all!
Thanks for all your help
-grifta67
Ok so im having some major issues. After wiping everything, il flash a rom using AmonRa recovery and it will start up like normal with no issues.. But when i need to restart my phone, or pull the battery or shut off or w/e, it wont get past start up screen.. Doesn't matter what rom i use..
All i remember is after flashing a bad Ice cream sandwich rom, i started having the issues.. Heard someone say something about my hboot? if it could be that, its version 6. 16. 1002.
Need help badly =( My phones my main source of communication and i hate having to reflash it daily
I had the same problem I flashed a miui ROM from amonra recovery and it just got stuck on the bootload screen... I fixed my issue by putting another ROM on the root of my SD card and flashed it you made sure you wiped the cache,dalvik cache,and factory reset right?? That's how I messed mine up I flashed cm7 to fix mine.. hopefully this helps if it didn't I'm sorry
Sent from my PC36100 using Tapatalk
http://forum.cyanogenmod.com/topic/32459-cyanogenmod-7-for-the-htc-evo-4g-v710-9-oct-2011/
will this cm7 work? not sure if its some system tweak or an actual rom lol
Download that one and I'm sure you won't need the gapps make sure you back up your current ROM and wipe the dalvik cache,cache,and factory reset etc.. plz let me know how it goes
Sent from my PC36100 using Tapatalk
Didnt work =/ I was ableto run it on first time, but not 2nd.. then tryed wiping and everything else to a new rom.. no changes in start up paterns D=
Damn I have no idea how to fix it then that's crazy I wish I could help you more but i just don't know what else could be wrong LOL sorry
Sent from my PC36100 using Tapatalk
Wholy crap,i'm not sure i want to mess with the reaper crowd,i'm not wanting to die anytime soon,ok guys.Anyway,the best thing i can tell you to do is,either install a new recovery and try that route,or unroot,then reroot,to see if that helps,here a link for the rooting and unrooting... http://forum.xda-developers.com/showthread.php?t=1245649
Normally, if you're having probs like this, it might be good to drop 10 and punt.
Run the RUU for your phone's version, and basically start over. I'm not sure about the newer H-Boot versions, but you may still be S-Off after running RUU. I know on mine, it's that way, but mine is from before Gingerbread
From common knowledge around the root community, that sounds completely like the wrong path lol...
Generally there is a much more simple solution lol.. I know that much..
and nice to see my signatures all over this website lol =D Clearly people like the clean slate Team Noctural sig i created.
I've had a ROM or two in the past do something similar. It would boot the first time and everything worked great but upon reboot would stick at the HTC screen. Try wiping your regular cache and dalvik cache and reboot and see if it will start again.
I was wondering if anyone could help me out please. I've tried searching the forums, but I haven't been able to find my exact issue. Basically, I feel as if my phone seems to have increasing issues with flashing through Clockwork Recovery; here's the details:
I originally rooted my phone using the Odin flash method. I flashed the Juggernaut available at the time, wiping data/factory, cache, dalvik, and battery stats through clockwork first, and letting it chill for 15 minutes with the first boot. I follow the same steps each time I flash another rom ( I've read that I should also wipe /system, but Juggernaut seems to do that itself, so I haven't ). A month and a half ago, I wanted to add a few things, so I wiped, then flashed the latest Juggernaut, rebooted, let it settle,and then flashed the ICS Ultimate Theme, no wipe, then after another settle, flashed the Pdroid zip ( no wipe ) I made with the v1.27 auto-patcher. Everything seemed to work flawlessly for a month or so, then I started having issues that just kept getting worse: phone freezing while installing market apps then unfreezing, camera lagging, random freeze & reboots, etc. I tried fix permissions, and no luck. I wiped and tried reflashing everything the way I had, and the phone kept freezing after the faux kernel loading screen. Installing Juggernaut or another rom by itself, or a nandroid restore, is the only thing that got it past boot. Not even themes flashed over roms that they're made for get past boot. I restored my phone to stock using this method, wiped both SD cards, and re-rooted then flashed Juggernaut again, but this time I used clockwork's wipes and darkside's super wipe before flashing, but I still can't flash anything but the rom itself without a boot loop, even with fix permissions. I had a similar issue on my old mytouch Espresso; consecutive flashes seemed to almost eat away at my phone and make things worse, but that phone also had hardware issues. I'm using a new MicroSD since then. Also, if it means anything, I tried flashing the new clockwork touch from the zip on these forums after these issues started, and it never took, however, flashing through Rom Manager's after I purchased it worked fine.
Sorry about the long post, but I wanted to detail everything I've tried that I could think of before bothering anyone here. Does anyone know what could be the issue? I would really appreciate some help, because this issue is really frustrating, and I have no idea what's causing it.
Could someone help me with this please? I can try and get a log cat if needed. I'm just really hoping to get to the bottom of these issues.
I will be glad to help you out!
One big problem I see is that your not using Darkside Superwipe before flashing new roms.
So I would highly recommend you flash Darkside Superwipe first (clears all cache, partitions, ect very very thorughly) Better option than manually clearing cache and all that in clockwork mod.
Try Darkside Superwipe install the rom and see if you get any problems.
Here's how to use it if you dont know how to:
techfanatic9 said:
I will be glad to help you out!
One big problem I see is that your not using Darkside Superwipe before flashing new roms.
So I would highly recommend you flash Darkside Superwipe first (clears all cache, partitions, ect very very thorughly) Better option than manually clearing cache and all that in clockwork mod.
Try Darkside Superwipe install the rom and see if you get any problems.
Here's how to use it if you dont know how to:
Click to expand...
Click to collapse
I'd like to point out that he does in fact use tdjs super wipe.
OP: have you tried other ROMs or kernels. In my past experiences, faux kernel did not meet my expectations so I moved along to another one. Give my configuration a go (refer to my signature) and let me know of the problem persists
Sent from my Galaxy Nexus using Tapatalk 2
Thanks for the replies!
techfanatic9 - I originally just wiped through clockwork ( before darkside superwipe was standard ), but now I use that too, and I'm still having those issues. I watched through the entire video just in case, and I'm doing it just like they say to.
iLeopard - I have tried Digital Warfare, but I still have the same issue when flashing things over it ( ICS Theme and/or PDroid ), even if it's supposed to be compatible, though I haven't tried kernels yet. I'll give your sig's setup a try and report back.
Meanwhile, could anything else be the issue? As you can probably tell, I've tried almost every mistake I could think of, and since my last phone had the same issue, a similar hardware issue seems unlikely.
All right, I've been running that ROM and kernel combo for a few days now. I don't seem to have any issues when I just flash the ROM and kernel, but I get stuck at the boot screen if I try to flash something else on top of it. Also, when I try to restore my text message backups through Gosms ( around 9800 texts that I want to keep ), the phone freezes halfway through the restore, and from that point on, the phone will freeze 5-10 minutes after rebooting, unless I reflash. I make sure I don't have the phone running and I leave it alone while restoring, and it doesn't help. I've only had this gosms issue since my flashing issue, and sometimes it restores fine.
Does anyone know what could be causing that?