[Q] Synergy Phone FC's - Droid Incredible Q&A, Help & Troubleshooting

Running Synergy RLS1 my phone app (com.android.phone) keeps not responding apparently so I get the popup for wait or force close. If i reboot it fixes it for a while but it keeps happening. Im worried im missing calls or texts. And what if theres an emergency and I cant make a call lol. Is this a Synergy issue or what? PS I tried fixing permissions.

You have proper version of hboot and at least a 2.1.x radio?
Sent from my ADR6300 using XDA Premium App

To be honest, I have no clue. How can I find out and is that something I can fix without reflashing/wiping/etc.?

Boot into hboot menu; device off, hold volume DOWN and power until booted into white screen. Hboot version is listed at the top. Use volume button to navigate and power button to select. Radio version ; Settings, About Phone, software information, look at the baseband version, that's the radio.
Sent from my ADR6300 using XDA Premium App

Hboot 0.92.0000
Radio 2.15.00.07.28

Hmm, which version of CWM does the thread say is required, and are those versions of hboot and radio acceptable per the thread?
Got ample space on the sd?
Sent from my ADR6300 using XDA Premium App

What clockworkmod recovery version are you using and what was your rom installation procedure?

ive been using rls1 since it was released and this just started happening the other day. i think it may have something to do with Faceniff. I remember it starting sometime around installing and using that app

Do you know what a clockworkmod is Paintboarder? Its a recovery system and you can find out easily what version you are running by using Rom Manager in your app drawer, and just look under recovery, and it says current recovery: Clockworkmod ?.?.?.?
Hope that helps you if you dont already know. And maybe your getting FC's because you didnt do a clean wipe and install. Did you try fixing permissions?

im completely aware what clockworkmod is. im not that much of a noob. im running 3.0.0.8. like i said. my installation process couldnt be the issue since i have been running without issues since the release of rls1

the issue is seeming to have receded a little since removing Faceniff. That doesnt mean it doesnt still happen. It does. And btw read the OP. I did try fixing permissions.

My bad, didnt mean to downgrade you just wanted to be sure. Well im running Synergy RLS1 right now and i havent experienced that issue. If it were me i would just try reflashing it. So far it is an amazing ROM.
Sorry man i guess i looked past that part about the fixing permissions.

flashed a different radio i saw in someones signature. seems to be working fine now. also i had the 3G and 1X connectivity issues and the solution in the ROM thread fixed it.

I'm using the older incredible without slcd and have had no issues, wonder if that connectivity issue is tied to that in any way? Guys with the newer incredible vs. Old
Dink sporting Synergy RLS1. Xda app.

Mods and not wiping seem to cause pretty much every error with FCs that I run into. Only time I get them reintroduced it seems is if I freeze/remove something that's needed by another program or if I restore data for certain programs (which were backed up under another ROM).

I have RLS 1 installed too and it ran fine for about 6 days before I started getting fc's. I was rebooting at least once a day the first 6 days then I didn't reboot for 2 days and started getting fc's. So I started rebooting daily again and I don't seem to have any more problems.

Related

Help, constant crashes & reboots

Sorry about double posting, but I am getting desperate (posted on Q&A).
Can't find an answer to this on google or xda. Didn't know if I should post this in General or Q&A.
I have been using my Incredible since it came out. I quickly learned about rooting, roms, s-off... with no problems. I have been running Skyraider almost from the beginning.
Here is the problem: A few days ago, I noticed on the SR thread that there were updates for the radio and hboot. So, I went ahead and flashed them. Almost immediately I started noticing the screen becoming unresponsive. After a minute or two I did a battery pull, rebooted, and again after a little while, freeze and reboot. I also noticed that even when the phone is awake but screen off, it would wake itself up. The rebooting and freezing makes it impossible to use my phone.
I tried everything I could think of:
Nandroid restore (obviously didn't work since this doesn't effect hboot or radio).
Reinstalled fresh SR Rom wiping everything, including dalvik, and did factory reset.
Finally, I downgraded back to the hboot and radio versions I had before, still no effect. (Baseband version 2.15.00.07.28, hboot .79 ).
I tried installing another ROM (Uncommon sense) to make sure it wasn't a ROM issue, ..same problem.
Please, any help would be much appreciated. I don't know what my next step should be.
PS, I am not overclocking, just using stock kernel.
Sent from my ADR6300 using XDA App
try downgrading to completely stock 2.1 then see if it keeps doing it...otherwise I'd say that maybe you did something wrong installing a file and it's bricked...that's what it sounds like anyways
Sent from my ADR6300 using XDA App
pete_kowalski83 said:
try downgrading to completely stock 2.1 then see if it keeps doing it...otherwise I'd say that maybe you did something wrong installing a file and it's bricked...that's what it sounds like anyways
Sent from my ADR6300 using XDA App
Click to expand...
Click to collapse
Today it's running a bit better. I'll keep testing it, if it continues to crash, I will take your suggestion and go back to 2.1 and start over.
Just a thought: are you restoring your stuff via Titanium? If so, you may be restoring a bad / incompatible system instruction. You might try this: Do a master reset and restore your important apps (not data) one at a time to check performance. Install data later (also individually) as needed.
HTH!
rfarrah said:
Just a thought: are you restoring your stuff via Titanium? If so, you may be restoring a bad / incompatible system instruction. You might try this: Do a master reset and restore your important apps (not data) one at a time to check performance. Install data later (also individually) as needed.
HTH!
Click to expand...
Click to collapse
I did use Titanium (apps & data, but not system). I am currently testing Uncommon Sense Rom. Been running fine last 2 days. Idk why.
Sent from my ADR6300 using XDA App

[Q] Recovery problems after Uncommon Sense

Wondering if I could get some ideas on why I experienced the following failure.
Was rooted with UnrEVOked 3.x for awhile. Installed ROM Manager and experimented with CM6. Didn't like it, restored back to stock with no major
issues. Today, I experimented with Uncommon Sense (did cache/data wipe and backup before). I used "MyBackup Pro" to get all my Apps back and some data. Loved it! After about 4 hrs, I started getting FC on mostly Google apps, but even some HTC apps. Exchange mail wouldn't sync. Phone, TXT, Web all worked fine.
I recovered with Clockwork to the backup I made just before going to Uncommon but all the FC issues persisted. I recovered again 2-3 times, making sure I did data/cache/delvik wipes. FC issues persisted. I pulled the battery sometime in there after a power down. No help.
Finally, I recovered to a backup I had from 6 days ago when I was experiementing with CM6. Fortunately this worked. No FC issues.
Now I'm paranoid about trying out other ROMs. If I cannot cleanly recover after an update, I really don't want to try another ROM.
Any help out there?
1) Why did Uncommon melt down? I'm running pretty standard stuff. No kernal changes, etc.
2) Why did the issues persist when I recovered? Any bullet proof ways of preventing this?
Crispy
Did you try running the "fix permissions" utility in ROM Manager? Noted there that it normal fixes force close issues.
Currently I am running Myn's Warm2.2 RLS3 but had previously loaded Uncommon Sense 1.0 and 1.1 anmd had no major issues with it. ( Myn's is nice! )
Try that permission fix utility and see if that solves your problem.
Yes, I tried the fix permissions utility, but I think it gave me errors.
crispy1 said:
Yes, I tried the fix permissions utility, but I think it gave me errors.
Click to expand...
Click to collapse
Download a terminal emulator, type in
su
fix_permissions
The reboot when done.
Sent from my ADR6300 using XDA App
Thank you. I could try that if I'm brave enough to go to Uncommon Sense again. Any explanation as to the cause? Is what happened to me normal when flashing ROMs and recovering?
Sent from my ADR6300 using XDA App
crispy1 said:
Thank you. I could try that if I'm brave enough to go to Uncommon Sense again. Any explanation as to the cause? Is what happened to me normal when flashing ROMs and recovering?
Sent from my ADR6300 using XDA App
Click to expand...
Click to collapse
ROM's are self contained entities - you probably just had an issue with that particular ROM. I've had awesome experience with the "Revolution" rom by HeyItsLou, Myn's Warm, Skyraider, and Virtuous.

bacon-bits owned my phone few weeks ago, always wondered why

So... I seen baconbits shortly after rooting and flashing, I installed baconbits, phone booted, than right from start up I get forceclose on every app and process... than I tried to do a backup, I got an error on cwm so than I wiped data and tried to reflash fresh and start over, that would not work. So I recovered the stock froyo and fixed cwm than I flashed fire and ice cm7 rom.. everything has been fine since I fixed it.. it was still frustrating tho..
But when ever I go to my boot loader before recovery, I get this green font that says blah blah blah not found (its trying to locate files to install that stock froyo, but after it doesn't locate the file I'm free to access recovery or do whatever.. is there a way to delete that "cannot find" ****, it takes about 20 seconds from holding power and volume down to give me control.. that's why I want it gone its annoying.. even if I can't fix it, I guess its not a major setback..
melodicjunkie said:
So... I seen baconbits shortly after rooting and flashing, I installed baconbits, phone booted, than right from start up I get forceclose on every app and process... than I tried to do a backup, I got an error on cwm so than I wiped data and tried to reflash fresh and start over, that would not work. So I recovered the stock froyo and fixed cwm than I flashed fire and ice cm7 rom.. everything has been fine since I fixed it.. it was still frustrating tho..
But when ever I go to my boot loader before recovery, I get this green font that says blah blah blah not found (its trying to locate files to install that stock froyo, but after it doesn't locate the file I'm free to access recovery or do whatever.. is there a way to delete that "cannot find" ****, it takes about 20 seconds from holding power and volume down to give me control.. that's why I want it gone its annoying.. even if I can't fix it, I guess its not a major setback..
Click to expand...
Click to collapse
thats internal feature of Hboot... it looks for pc10img.zip on sd card.... not at all an error....
and it can be useful in a situation where you mess up your recovery and rom ... you would be able to save your phone via that ....
also its used to go back to stock rom and unroot when needed
+1 for hispeedword. Best possible answer right there - that's exactly what's going on. Use ROM Manager to reboot straight to recovery from now on and it will skip HBOOT so you don't have to wait through all of that. CM and most other roms also allow that option when you hold down the power button.
Now, you said "shortly after rooting and flashing" - what exactly did you flash? You do know baconbits is ONLY meant to be used with the stock rom right? The exact one that you rooted and that came on your phone. If you flash ANY other rom - even a 'stock rooted rom' then you run into tons of errors when flashing baconbits.
Dont flash baconbits, its not needed
Sent from my HTC Vision using XDA App
TheMod'sPolice said:
Dont flash baconbits, its not needed
Sent from my HTC Vision using XDA App
Click to expand...
Click to collapse
Yeah I was being stupid, I didn't even know at the time when my phone messed up that it was from me flashing baconbits...until I did a back up, than flashed a different rom and reflashed baconbits, lmao..
so your saying to use baconbits if you rooted but didn't flash custom roms, than it works fine?
I'm thinking of switching to a sense rom, I don't even know why.. what are the pros/cons of sense? Thanks.
Assuming you've already answered your question up there, sense roms usually consume more battery life because of the plethora of constantly active widgets. However, if you're VERY social or buisiness, Id recommend it. The battery drain only cuts down on a few hours, depending on your usage, cpu governers and radio, and for that, you get a lot of functionality from the rom. Plus the new elegant blues ported theme for sense roms is just gorgeous. I also like the whole manual link to facebook in the contacts. Still hoping for a port for that xP try it out.
Sent from my HTC Vision using XDA Premium App

[Q] Nonstop rebooting, even after full wipe/reinstall - last_kmsg inside

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

Stuck on white Htc EVo screen after succesful flash w/ almost every Rom

Hello everyone,
I just want to say I did not make this thread prematurely. Iv had this current issue for over a month. Iv talked to various people on here and other related forums and tried everything others have suggested with nothing working, So I come here to hopefully, somehow, get an answer or a fix.
I've had my Evo since Feb, rooted almost immediately and have been trying different roms ever since. Yet I always found myself going back to CM. Well just recently, Iv run into a problem where ALMOST every rom I try to flash, it gets stuck at the white htc evo 4g screen, constantly rebooting over and over. I actually waited once for hours to see if it eventually would go into the rom but it didnt. Iv tried battery pulls, clearing cache and davlich, nothing works.
Here is what works with no issues that iv tried: Any CM, Miui, Mikfroyo, MikZ, Myns, MynsZ
WHat iv tried and does not work:Mikg, Virus, Kings, Leo, Alliance, Stock Gb,
Btw, I was originally using clockwork and was told to go to Amon Ra(latest version yes)-
Heres what exactly happens:
I download the rom, which Iv tried from my phone and my pc both. Put it on root of sd. reboot into recovery. Wipe: Cache,Davlick,Boot,System,Sd ext.,Data,Sd secure, All userdata/factory reset in that order and sometimes 2 and 3 times. I then flash the rom. The screen shows the progress of the installation of w/e rom it is, always says complete or successful. Reboot.
Almost immediately Shows the screen with the squigley colored lines then after a second or 2, phone vibrates, reboots right to white evo 4g screen. Sits on that screen for approx.10-15 seconds, vibrates goes black for 2-3 seconds and then back to the white evo 4g screen and it does this over and over til im forced to pull the battery. Very VERy frustrating.
I was told maybe the links of the downloads were bad so i tried multiple downloads of the same zip. I was told to check to see if the md5 sum thing matched, it did. I was told to download sd formatter, did that. I was told to update all the latest radios,prl,ext.
I do not know a whole lot about this but Im thinking that every Gb rom i try doesnt work. With the exception of 2 Aosp roms(cm and miui). I could be way off here but im just throwing that out there.
One thing I will mention. In the middle of trying to figure all this out, I deleted my sd card when trying to wipe. Now what is important is this issue was def. happening before I ever made this mistake. SO maybe its a moot point, I just want to mention everything.
Im hoping, praying that some of you MUCH more knowledgeable flashmatics can point me in the right direction because Iv been pulling my hair out for over a month trying everything I can read or was told to come to a conclusion as to why this would be happening.
Thank you for your time. Its much appreciated.
Try downloading and flashing a stock HTC kernel,then reflash the Rom you're trying to run .
Sent from my PC36100 using XDA App
BrianBusby2038 said:
Try downloading and flashing a stock HTC kernel,then reflash the Rom you're trying to run .
Sent from my PC36100 using XDA App
Click to expand...
Click to collapse
You are the only response Iv gotten so i thank you.
Someone else mentioned this.
So I downloaded: Htc kernel #15
WHat I did was flash the rom(had been various ones) then flashed this kernel, rebooted, same result. Is this what you mean?
Have youve ever even heard of this? WHere every froyo rom iv tried works, 2 specific gb roms work(CM and miui) yet various other(gb) will not work.
Has anyone EVER heard of anything like this?
What hboot version?
Sent from my PC36100 using XDA Premium App
My suggestion is go completely stock. Unroot with a 3.70 RUU and then root your phone again. Start from scratch and then load up or attempt to load up one of the Sprint Lovers rom and see what happens. Maybe just maybe you had a bad root. I do recommend Amon as well though.
Or try this get Caulkins wipe all zip and format your phones harddrive and load up Sprint Lovers and see what happens
I would recommend flashing the kernel first before the ROM,however,since you can successfully flash froyo ROMS,playa may be right and you should try running the ruu and starting over.I was thinking the problem was an incompatibility between an ASOP ROM and a Sense kernel but doesn't hold water if you can get froyo based ROMS to boot up.
Sent from my PC36100 using XDA App
unvivid said:
What hboot version?
Sent from my PC36100 using XDA Premium App
Click to expand...
Click to collapse
not sure how do i find that out? I though if I updated all radios, ext. it included that. If im way off here sorry.
playya said:
My suggestion is go completely stock. Unroot with a 3.70 RUU and then root your phone again. Start from scratch and then load up or attempt to load up one of the Sprint Lovers rom and see what happens. Maybe just maybe you had a bad root. I do recommend Amon as well though.
Or try this get Caulkins wipe all zip and format your phones harddrive and load up Sprint Lovers and see what happens
Click to expand...
Click to collapse
Like I said I will try anything, so I will be trying to do this as soon as I have time. I may run into problems with how to do this, can you possibly point me in the direction or a how to? I mean I obviously would know how to flash a sprint lovers rom but im talking about the un-rooting step regarding 3.70 ruu??, Iv never did it and probably would be lost(noob).
htcevo4g03 said:
not sure how do i find that out? I though if I updated all radios, ext. it included that. If im way off here sorry.
Click to expand...
Click to collapse
Not a problem. Turn your phone off and hold the power button and the volume down button. This will take you to the bootloader screen. The hboot and radio versions should be at the top. I'm betting your hboot is .76
I had the same issue that you did and nothing worked, I was unable to flash any new GB Rom besides cm. I tried flashing stock, using multiple versions of clockwork and amon ra. Nothing worked, updating my hboot to the latest version fixed my issue, I'm guessing its something to do with the hboot version and hardware combination. You may lose fastboot commands, if you're unsure of what those commands are I doubt you'll miss them. And recent developments have allowed for downgrading of hboot. I'll dig the link up for the latest hboot.
Edit: http://forum.xda-developers.com/showthread.php?p=7027238
I personally flashed the 2.02 hboot for downgradability. I'd avoid 2.16 since it is so new and I've heard of issues after flashing. Anything prior to that should be fine.
Sent from my PC36100 using XDA Premium App
unvivid said:
Not a problem. Turn your phone off and hold the power button and the volume down button. This will take you to the bootloader screen. The hboot and radio versions should be at the top. I'm betting your hboot is .76
I had the same issue that you did and nothing worked, I was unable to flash any new GB Rom besides cm. I tried flashing stock, using multiple versions of clockwork and amon ra. Nothing worked, updating my hboot to the latest version fixed my issue, I'm guessing its something to do with the hboot version and hardware combination. You may lose fastboot commands, if you're unsure of what those commands are I doubt you'll miss them. And recent developments have allowed for downgrading of hboot. I'll dig the link up for the latest hboot.
Edit: http://forum.xda-developers.com/showthread.php?p=7027238
I personally flashed the 2.02 hboot for downgradability. I'd avoid 2.16 since it is so new and I've heard of issues after flashing. Anything prior to that should be fine.
Sent from my PC36100 using XDA Premium App
Click to expand...
Click to collapse
This.
I was having the same problem htcevo4g03 was having and I had hboot 0.76.2000. Here is what I did:
Made a nandroid backup
Using rom manager I downgraded to clockworkmod 2.5.0.7
Downloaded hboot 2.10.0001 under Evo Stock and Radios
Wiped data and cache (I don't know is this is necessary but probably not a bad idea)
Flashed hboot 2.10.0001
Downloaded and flashed fresh evo 4.2 (a rom that wouldn't flash before) via recovery and it worked!
unvivid said:
Not a problem. Turn your phone off and hold the power button and the volume down button. This will take you to the bootloader screen. The hboot and radio versions should be at the top. I'm betting your hboot is .76
I had the same issue that you did and nothing worked, I was unable to flash any new GB Rom besides cm. I tried flashing stock, using multiple versions of clockwork and amon ra. Nothing worked, updating my hboot to the latest version fixed my issue, I'm guessing its something to do with the hboot version and hardware combination. You may lose fastboot commands, if you're unsure of what those commands are I doubt you'll miss them. And recent developments have allowed for downgrading of hboot. I'll dig the link up for the latest hboot.
Edit: http://forum.xda-developers.com/showthread.php?p=7027238
I personally flashed the 2.02 hboot for downgradability. I'd avoid 2.16 since it is so new and I've heard of issues after flashing. Anything prior to that should be fine.
Sent from my PC36100 using XDA Premium App
Click to expand...
Click to collapse
Hey Man,
I haven't tried anything yet but im going to this morning.
Looking at the bootloader screen, says:
Supersonic EVT2-3 SHIP S-OFF
HBOOT-2.10.001
MICROP-041f
RADIO-2.15.00.05.02
Ok so I should download anything prior to 2.16 and flash like a rom?
Thoughts after youve seen my version?
TeamGold said:
This.
I was having the same problem htcevo4g03 was having and I had hboot 0.76.2000. Here is what I did:
Made a nandroid backup
Using rom manager I downgraded to clockworkmod 2.5.0.7
Downloaded hboot 2.10.0001 under Evo Stock and Radios
Wiped data and cache (I don't know is this is necessary but probably not a bad idea)
Flashed hboot 2.10.0001
Downloaded and flashed fresh evo 4.2 (a rom that wouldn't flash before) via recovery and it worked!
Click to expand...
Click to collapse
looks like the hboot version youve downgraded too is the one Iv had
unvivid said:
Not a problem. Turn your phone off and hold the power button and the volume down button. This will take you to the bootloader screen. The hboot and radio versions should be at the top. I'm betting your hboot is .76
I had the same issue that you did and nothing worked, I was unable to flash any new GB Rom besides cm. I tried flashing stock, using multiple versions of clockwork and amon ra. Nothing worked, updating my hboot to the latest version fixed my issue, I'm guessing its something to do with the hboot version and hardware combination. You may lose fastboot commands, if you're unsure of what those commands are I doubt you'll miss them. And recent developments have allowed for downgrading of hboot. I'll dig the link up for the latest hboot.
Edit: http://forum.xda-developers.com/showthread.php?p=7027238
I personally flashed the 2.02 hboot for downgradability. I'd avoid 2.16 since it is so new and I've heard of issues after flashing. Anything prior to that should be fine.
Sent from my PC36100 using XDA Premium App
Click to expand...
Click to collapse
I downloaded and flashed Hboot 2.02 from the evo stock and radios and then tried to flashed Virus and Synergy, but the same thing is happening.
Im going to try hboot 2.15 but it sure dont look good. This is UNREAL
Bump:
Anyone of you guys that replied earlier in the thread or Anyone else out there?
Any help would be very much appreciated!
Sent from my PC36100 using XDA App
Might sound weird, but have you tried reformatting the SD card?
tnEVo said:
Might sound weird, but have you tried reformatting the SD card?
Click to expand...
Click to collapse
hey the reply is much appreciated!
If you read my op, I mentioned someone told me to dl sd formatter on my pc which I went through the steps and it didnt work.
Hey man If you get a chance please read my op, this is prob going on a month and a half and no fix to this point. I would have though if I brought the issue here, it would be resolved like that but it hasnt. Iv tried everything ppl have thrown at me and not a thing has worked. Other than froyo roms and 2 gb roms(cm7/miui), cannot getting anything to work. Ill flash a rom, it always says successful I reboot, turns to the white screen and gets stuck, rebooting over and ove, always back to the white screen and Im forced with a battery pull to do anything else. AMAZING!
If you can just look over the OP maybe just maybe you might have something you think could work.
The very last thing i tried, in which 2 ppl said they were having the same issue, was to downgrade the Hboot. I did this and it didnt work. SO frustrating.
The one thing I did not try that was said to do was unroot, go back to stock, and root again.
SO lost here. Again thanks for contributing to this thread.
htcevo4g03 said:
hey the reply is much appreciated!
If you read my op, I mentioned someone told me to dl sd formatter on my pc which I went through the steps and it didnt work.
Hey man If you get a chance please read my op, this is prob going on a month and a half and no fix to this point. I would have though if I brought the issue here, it would be resolved like that but it hasnt. Iv tried everything ppl have thrown at me and not a thing has worked. Other than froyo roms and 2 gb roms(cm7/miui), cannot getting anything to work. Ill flash a rom, it always says successful I reboot, turns to the white screen and gets stuck, rebooting over and ove, always back to the white screen and Im forced with a battery pull to do anything else. AMAZING!
If you can just look over the OP maybe just maybe you might have something you think could work.
The very last thing i tried, in which 2 ppl said they were having the same issue, was to downgrade the Hboot. I did this and it didnt work. SO frustrating.
The one thing I did not try that was said to do was unroot, go back to stock, and root again.
SO lost here. Again thanks for contributing to this thread.
Click to expand...
Click to collapse
Sent from my PC36100 using XDA App
I would just go ahead a unroot,wipe the hell out of it then go a reroot the see what you get. With everything you have tried so far that maybe the thing you need,sorry I couldn't be more help.
Same situation here now
So.. i'm in basically the same situation.. with a wrinkle.
I just tried.. about 8 roms.. ALL of them get stuck on the white screen
Except.. CM 7.0.3.1.. that seems to install
Any thoughts on what the heck that could be?
Roms I tried:
miui
warm 2.2
calkins new one
kings 3d
fresh 4.2
I agree... unroot, run the s-on tool form unrevoked.
run the RUU for your phone
re-root
flash Amon Ra recovery and try a new ROM
Hey hip,
OK if I have to start from scratch I will. But since I'm a super noob, can you please be a little more specific on the steps I have to take? I don't know much about s-off and s-on tool and also what ruu is. If you can just point me in the right direction then I can follow the directions.
And ty for your time
Sent from my PC36100 using XDA App

Categories

Resources