Power button reboots phone with Skyraider 3.3 - Droid Incredible Q&A, Help & Troubleshooting

Hey all
I've searched for an answer to my problem but have been able to find it. Anyway, I have tried about 8 different ROMS over the past month or so and Skyraider is easily my favorite. However, I had to remove due to the fact that whenever I would try to power down the device, it would reboot instead.
I've tried installing both manually and from ROM manager with the same outcome. I've cleared date & davlik and performed full wipes each time. My last hope was fixing permissions but that failed to correct the issue as well.
Again, I really enjoy using this ROM and do not relish the thought of not being able to use it. Does anyone have any thoughts on a possible fix?

patsfan1130 said:
Hey all
I've searched for an answer to my problem but have been able to find it. Anyway, I have tried about 8 different ROMS over the past month or so and Skyraider is easily my favorite. However, I had to remove due to the fact that whenever I would try to power down the device, it would reboot instead.
I've tried installing both manually and from ROM manager with the same outcome. I've cleared date & davlik and performed full wipes each time. My last hope was fixing permissions but that failed to correct the issue as well.
Again, I really enjoy using this ROM and do not relish the thought of not being able to use it. Does anyone have any thoughts on a possible fix?
Click to expand...
Click to collapse
You sure its Skyraider? That happened to me... Phone wouldnt shut off, if your in dark you can see the screen doesnt even shut down. With me though, it would shut off if plugged in.. Turned out the phone was damaged, a power surge damaged it. Got it replaced. If you flash another rom and it still wont shut down, then your gonna need a replacement.

Thanks for the response Mike. No, It does not happen with any other ROM I flash. Been bouncing between CM, Virtuous and uncommon for a week now and the power button works as it should.
I dunno, I realize I am a n00b with all of this but it simply doesnt make sense to me
Again, Thank you for the response

What radio are you using? A lot of people using 2.05 were having that issue and it went away when they upgraded to a 2.15 radio baseband.

No problem. But what you have going on is very odd, i wasnt aware that a ruu could do that. Try upgrading to the latest radio.

That's the baseband version correct? Sorry, I'm not too saavy with radios. Anyway..it says 2.15.00.07.28

patsfan1130 said:
That's the baseband version correct? Sorry, I'm not too saavy with radios. Anyway..it says 2.15.00.07.28
Click to expand...
Click to collapse
Yes, that's the baseband version and you should be good to go with the one you are using. The only other things I can come up with is to ensure you are S-OFF and running HBOOT 0.79 or higher.

Please forgive my ignorance here. I am definately S-off but I am unsure how to see what HBOOT I am running. I go into recovery but I dont see any version.

patsfan1130 said:
Please forgive my ignorance here. I am definately S-off but I am unsure how to see what HBOOT I am running. I go into recovery but I dont see any version.
Click to expand...
Click to collapse
Not a problem. This is how we learn. To find your HBOOT version power down then reboot into recovery. When you get to the white recovery screen look in the top left corner. The first line should state S-OFF and the second line should state your HBOOT version.

I was really hoping I would see it lower than 0.79 but it's 0.92. ah well..I suppose it's simply my phone doesn't play well with this ROM.
Thank you for the suggestions

I had this happen to me on Skyraider 3.3 after I tried to install a taskbar or battery icon from his older roms. Try just the stock rom for now until he updates.

patsfan1130 said:
I was really hoping I would see it lower than 0.79 but it's 0.92. ah well..I suppose it's simply my phone doesn't play well with this ROM.
Thank you for the suggestions
Click to expand...
Click to collapse
Well that's unfortunate. I read a couple of posts in the Skyraider thread that sounded as though a couple of people had the "recommended" setup (like you) but also had the reboot problem. Those posts seemed to get no response so I guess there was no fix found. Most of the discussion on this problem starts around post #2432 in the Skyraider thread if you want to do some more digging but I couldn't really find anything more.
Some other factors to consider:
When you first flashed the ROM did you wipe all data? (factory reset, wipe data cache, wipe dalvik cache).
If you flashed a custom kernel, try going back to the stock kernel.
What version of ClockworkModRecovery are you running? They released a buggy update a couple of weeks ago and it was pulled shortly after release so if you have a version higher than 2.5.0.5 then you should revert to an older version of CWM.
You could flash the 2.15.00.09.01 radio baseband but I don't think it would make a difference with this problem. Also, if you screw up or accidentally flash the same radio over itself then you will have a brick so use extreme caution if you decide to go that route.
That pretty much exhausts my knowledge on the subject so if everything is as it should be then you could always try wiping everything and flashing the ROM again.
RebelShadow said:
I had this happen to me on Skyraider 3.3 after I tried to install a taskbar or battery icon from his older roms. Try just the stock rom for now until he updates.
Click to expand...
Click to collapse
I didn't think of that but definitely a possibility. Good call.
Best of luck.

RebelShadow said:
I had this happen to me on Skyraider 3.3 after I tried to install a taskbar or battery icon from his older roms. Try just the stock rom for now until he updates.
Click to expand...
Click to collapse
Well wouldn't you know it! Problem solved
I did not know the add ons were not compatible
Thanks everyone!

I'm glad I was able to help...
Really though, good to hear you got it working. Enjoy.

Related

How to get access to copyrighted apps in the market place after ROOT?

Ok, so I did part 1 and part 2 of Toast's root for full NAND access
I also flashed to the latest radio
how do I fix it so I can see apps like NYTimes, etc? Thanks
I have the same issue. Any details on this would be greatly appreciated.
Not sure if I completely understand, but I am fully rooted (Toast 1/2 Nand etc). I just searched for NY times in App Market, downloaded, installed, and it works fine.
I have new Radio, and Running Bugless Beast Rom.
sterlinron said:
Not sure if I completely understand, but I am fully rooted (Toast 1/2 Nand etc). I just searched for NY times in App Market, downloaded, installed, and it works fine.
I have new Radio, and Running Bugless Beast Rom.
Click to expand...
Click to collapse
Well, you have a custom ROM loaded, so that would change the result. I too have the latest radio, but I'm still using the stock ROM with my recovery. There has to be something we can do fix this issue. I don't want to load any custom ROM's because I haven't seen one that appeals to me. I'm wondering of users that have kept the stock ROM, but have it rooted via Toast method have this issue or are they using apps that aren't effected by this????? Someone has to know of a fix or a file that we can copy over the one that has broken us.
Well at least we know there is a cure for it. Either run a custom rom, or talk to the dev who made it work in his ROM to see what he did to cure it.
sterlinron said:
Well at least we know there is a cure for it. Either run a custom rom, or talk to the dev who made it work in his ROM to see what he did to cure it.
Click to expand...
Click to collapse
I agree, but that's why this thread was made, in hope that someone who knew how to fix this issue would chime in here and let us know, so that we didn't have to bother anyone for a fix....
Wishful thinking I guess....
well guys..the only way i fixed my issue was flashing to the OMJ rom..now it all works fine
eyecon82 said:
well guys..the only way i fixed my issue was flashing to the OMJ rom..now it all works fine
Click to expand...
Click to collapse
I wish you would have waited.... I am testing a fix now...
LilRico said:
I wish you would have waited.... I am testing a fix now...
Click to expand...
Click to collapse
.i was using “Supersonic_1.32.651.1_rooted.zip" which has known issues with the market place....
FIXED!!!!
Many thanks to XpAcErX on this post!
http://forum.xda-developers.com/showpost.php?p=6838616&postcount=809
XpAcErX said:
those apps were missing from the market for me when i had toasts PC36IMG.zip rom flashed from the root in part 1, perhaps you nandroid restored that rom.
flashing flipz OTA Update 1.32.651.6 and the newest radio fixed the issue for me.
flipz OTA Update 1.32.651.6: http://geekfor.me/evo/21/ota1326516
Radio: http://geekfor.me/evo/radio/radio139000531/
Click to expand...
Click to collapse
I flashed the flipz OTA Update 1.32.651.6 in recovery mode, and then flashed the radio but it made my phone go in a constant re-boot. I did a wipe, Dalvik wipe and a cache wipe and success!!!! I was booting with no issues AND all the apps that I wanted in the market were showing up with no issues + I had full root access!!!! I lost some of my data, but that's a small price to pay... Good thing I had my backups! Thanks again to XpAcErX. OP should link to this post for future reference.

[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

[Q] Constant Reboots...

Hello everyone. I have not been too particularly active here mainly because I have had no real reason to post. I give thanks when needed, but don't really post. Well, now I am having an issue that I genuinely cannot figure out. I recently dropped my phone and the digitizer cracked big-time. When I went to replace it, the connector for the ribbon cable broke. So instead of buying a new logic board, I just decided to buy a new Evo. However, I couldn't afford the approx. $600 for the "without a contract" price. So I went to a local Sprint dealer in my town and bought a factory refurbished Evo. Here is where the problems start.
I have been having reboots constant with this phone. I knew that there were some issues with the Evo randomly rebooting, but I have never seen something like this. It happens about every minute or so. Sometimes sooner. Sometimes I luck out and it doesn't reboot for a few hours. I notice that it does not reboot at all while it is in recovery, which is a great thing. I have tried multiple different ROMs and each one does it. I am completely out of ideas. I don't necessarily want to take it back, mainly because returning it to stock would be a pain. However, it is looking like I have to. Does anyone have any idea? It is obvious that it is not a bootloop, because I am able to actually get into the launcher. However, within a minute, it reboots. Can old radios cause it to reboot like this? It did this even with stock unrooted.
If any information is needed, please let me know. I really want to get this working without returning.
Thanks
StompySan
EDIT: It would seem that flashing my Nandroid backup of stock rooted seems to stop the rebooting issues. Could the ROMs I am installing be conflicting with the radios, causing it to reboot?
If I were you, without unrooting, I would flash the RUU for your phone. Then flash the pc36img for Amon Ra.
Before all that, I'd also back up your SD Card, then reformat it, so you are basically starting from scratch. A good idea, before you restore everything to your SD Card, but after you flash Amon Ra, is to partition it for EXT3. ( http://themikmik.com/showthread.php?5669-GUIDE-TUTORIAL-Apps2SD-Guide&highlight=partition+sdcard )
A lot of the ROMS now will take advantage of that. Once that's done, you can restore your SD Card backup to your phone.
Then I'd make a nandroid of that stock/rooted ROM, so you can always go back to it if you need to. When I nandroid, I backup everything except cache.
Figure out which ROM you want, put it on your card along with DT A2SD and the kernel you want to use. Make sure it's a kernel for the type of ROM you want, either AOSP or Sense. Personally, I keep the best rated kernel for each on mine.
Go to Wipe in Recovery and wipe everything, EVERYTHING, except the SD Card, then flash your ROM, and in the same recovery session, flash DT A2SD.
Let it boot up and let it settle in before you do anything. For me, that means once the screen shuts itself off.
Back to recovery, wipe Cache and Dalvik-Cache, then flash your kernel, reboot and let it settle in again.
THEN setup your Google accounts and preferences.
For me, I'd go back to recovery and nandroid that setup, before you've restored your apps, and make another nandroid, so you have one of your ROM's Base.
Then, reboot and see if the problem is fixed. If it is, restore your apps and see how it goes. If it starts rebooting, you know it's in your apps, so you can go back to the nandroid you made and start form there, installing a few apps at a time
Thanks for your reply HipKat.
I followed your tutorial step-by-step. However, after flashing A2SD and rebooting, it bootlooped (not like what I was getting, but an actual no boot logo bootloop). I am assuming that the ROM that I flashed didn't like the A2SD. So I restarted the tutorial, skipping the part where you flash the A2SD script. It seems like it is doing great now! I have no clue what I was doing wrong. I was using CWM. Maybe that was the problem. Could it have not been wiping it properly?
Thanks again for the quick response!
1.There are some roms that provides a CPU speed of 1.2G. With those roms and setcpu installed manually by myself, my evo rebooted just like yours. I don't know why, too.
But after I wipe everything(as HipKat said) and flash other rom, my evo 4g works just fine.
2. Before flashing new roms, wipe everything is absolutely required, otherwise strange problems will keep coming out.
What I comprehend is that flash roms on phone is like upgrading OS on your computer, you can't run windows7 with XP's configuration, right?
Hey HipKat, I've noticed that you advise people to wipe everything but the SD card in Amon Ra. You may want to note that wiping battery stats is only good if you have a full battery and plan on calibrating properly. If you wipe battery stats at 70%, your phone won't charge past 70% (thinking that it's full) unless you use an sbc kernel. Just something to keep in mind.
I'm not knocking your directions, you help a lot of people out. It's just something to think about.
Sent from my PC36100 using Tapatalk
plainjane said:
Hey HipKat, I've noticed that you advise people to wipe everything but the SD card in Amon Ra. You may want to note that wiping battery stats is only good if you have a full battery and plan on calibrating properly. If you wipe battery stats at 70%, your phone won't charge past 70% (thinking that it's full) unless you use an sbc kernel. Just something to keep in mind.
I'm not knocking your directions, you help a lot of people out. It's just something to think about.
Sent from my PC36100 using Tapatalk
Click to expand...
Click to collapse
You're right! I keep overlooking that because I never flash unless I'm fully charged.
My mistake on those posts. Thanks!
I was still getting reboots after doing all of that. I thought it went away, but it didnt.
79x1 said:
1.There are some roms that provides a CPU speed of 1.2G. With those roms and setcpu installed manually by myself, my evo rebooted just like yours. I don't know why, too.
But after I wipe everything(as HipKat said) and flash other rom, my evo 4g works just fine.
Click to expand...
Click to collapse
This has to be it. I changed the speed to 1.15GHz in SetCPU and it has not done it since. Thanks!
EDIT: Well, it was OK, but it has started again. I have no clue why it is doing it again...
Maybe you should try some classic roms that don't require app2sd, like kings' kinged kingdom.
Before I partition my sd card, with shooter E3D and synerge, my evo also sometimes reboot, but not so frequently as yours.
And the CPU speed should be below 998MHz on my device (HW version:004)! Set your cpu frequency lower first, then try some other roms.
79x1 said:
And the CPU speed should be below 998MHz on my device (HW version:004)! Set your cpu frequency lower first, then try some other roms.
Click to expand...
Click to collapse
It doesn't matter what speed I set it to. I had it at 998 before and it still rebooted.
79x1 said:
Maybe you should try some classic roms that don't require app2sd, like kings' kinged kingdom.
Before I partition my sd card, with shooter E3D and synerge, my evo also sometimes reboot, but not so frequently as yours
Click to expand...
Click to collapse
I am going to flash Synergy real quick. I have already tried the following:
EVOlvedROM r3chargeD
Cyanogenmod
Are there any other ROMs I should try?
EDIT: I recorded a video of exactly what it is doing. I am currently encoding it. I will throw a YouTube link up soon.
Kings' Alliance is the steadiest rom i've ever used, without sense 3.0 though. If you don't mind you could try this:
http://forum.xda-developers.com/showthread.php?t=1180048
Here is the video of the rebooting problem. Sorry it is so long. It seems like the one time I want it to reboot it took forever for it to. lol.
79x1 said:
Kings' Alliance is the steadiest rom i've ever used, without sense 3.0 though. If you don't mind you could try this:
http://forum.xda-developers.com/show....php?t=1180048
Click to expand...
Click to collapse
I will try this ROM later tonight. I probably won't be able to reply tomorrow, because I have to work from 10AM to 10PM (I hate long days, lol), but will reply as soon as possible.
MIUI, for the win, man!
OK, I can pretty much confirm that it is a hardware problem. I have tried every ROM I can think of. It always seem to restart when it tries to turn on the Mobile access. If it is connected to WiFi, it will not reboot. The moment it is disconnected, it starts. However, I know it is not because of a bad radio flash. I have tried re-flashing the radios and it still doesn't work. I have restored it completely back to stock (while keeping S-Off, naturally) and it still does it. So, I am going to be returning it tomorrow. However, I have one real quick question. I know how to unroot, but I am not sure on how to achieve S-On with the Revolutionary root. Can you just flash the Unrevoked S-On zip with this root, or is there a different method? I wasn't able to find anything out on this.
Thanks again for all of your help. I really can't believe how quick people on here replied.
It isn't your hardware, I had a similar issue on my phone, it wouldn't go past the evo screen (for hours), I updated my firmware and it worked.
Clear caches, flash this rom (supersonic_4.24.651.1_odexed-signed2 google it), it will update your firmware, then flash the rom you want on top of it
stompysan said:
OK, I can pretty much confirm that it is a hardware problem. I have tried every ROM I can think of. It always seem to restart when it tries to turn on the Mobile access. If it is connected to WiFi, it will not reboot. The moment it is disconnected, it starts. However, I know it is not because of a bad radio flash. I have tried re-flashing the radios and it still doesn't work. I have restored it completely back to stock (while keeping S-Off, naturally) and it still does it. So, I am going to be returning it tomorrow. However, I have one real quick question. I know how to unroot, but I am not sure on how to achieve S-On with the Revolutionary root. Can you just flash the Unrevoked S-On zip with this root, or is there a different method? I wasn't able to find anything out on this.
Thanks again for all of your help. I really can't believe how quick people on here replied.
Click to expand...
Click to collapse
You can flash S-On.zip directly from the recovery, I suggest you try out the method I mentioned in the previous post, before you go doing something drastic.
prometh1us said:
It isn't your hardware, I had a similar issue on my phone, it wouldn't go past the evo screen (for hours), I updated my firmware and it worked.
Clear caches, flash this rom (supersonic_4.24.651.1_odexed-signed2 google it), it will update your firmware, then flash the rom you want on top of it
Click to expand...
Click to collapse
Nonono, it goes past the Evo screen. It goes past the standard boot logo. However, once you are in the lockscreen, and it tries to connect to 3G, it reboots. It is not a standard no boot logo bootloop.
stompysan said:
Nonono, it goes past the Evo screen. It goes past the standard boot logo. However, once you are in the lockscreen, and it tries to connect to 3G, it reboots. It is not a standard no boot logo bootloop.
Click to expand...
Click to collapse
If you're gonna trade it in, you don't need to unroot. Chances are no one will ever know, as long as you have a stock ROM on there.
HipKat said:
If you're gonna trade it in, you don't need to unroot. Chances are no one will ever know, as long as you have a stock ROM on there.
Click to expand...
Click to collapse
Yeah. That's what I was reading. Plus, I rooted with Revolutionary, which doesn't have a method to enable S-On.
Last night I flashed the latest stock ROM. As soon as it booted up and got to the lockscreen, it restarted. I can't see it not being a hardware problem. I am going to return it today. Hopefully they don't notice that it is S-Off. Any suggestions on what to say if they do?
same issue
i have an old evo that is doing the same thing, i flashed the original ruu and it still does it. i just reported it lost.

[Q] Every Rom = Bootloop, even stock. What should I do?

I can't really do anything with this phone right now. Every single rom, including stock rom, gets stuck in a bootloop. This is after wiping everything. I tried changing up the radios. I tried changing recoveries (RA 2.3, 1.8 and a few Clockworks). Tried PRI/NV changes. Nothing works. Tried booting with no SD card. Same problem, no matter what. I even tried to go s-on and flash an RUU. S-on didn't work, and the RUU has the same bootloop situation.
The Story:
Two days ago, I got a refurb 0002 Evo to replace a 0004 that had screen issues...I promptly rooted the new Evo, with revolutionary.
I tried to install CM 7.1, which worked fine on my previous evo. I wiped like normal and installed it...I got it running but it was randomly rebooting every so often.
I couldn't solve the problem, and decided to try downgrading the radios on teh new phone to what I had on the old phone, where CM 7 worked. This is when it started bootlooping. Flashing the 2.15.00.0808 radios, which the phone had originally, has not helped.
Any ideas? I have tried stock, fresh, miui, CM 7.1, CM 7.03 all multiple times. The phone is HBOOT 6.16, radio 2.15.00.808, PRI/NV 2.15.
IIRC you can't downgrade your radio. The newer radio versions wont allow downgrading. There have been a lot of people having the bootloop problem. And most of them seem to be running CM7. Not sure if you're in the bootloop of death or not. Hopefully someone else can chime in with more experience concerning this issue.
Concordium said:
IIRC you can't downgrade your radio. The newer radio versions wont allow downgrading. There have been a lot of people having the bootloop problem. And most of them seem to be running CM7. Not sure if you're in the bootloop of death or not. Hopefully someone else can chime in with more experience concerning this issue.
Click to expand...
Click to collapse
Idk why people are getting bootloops. Been on CM7 since 'nam and I'm currently on the same radio as the op for couple months now, and haven't experienced any issues.
I'd true flashing/using amon ra , EVERYTHING besides the sd card [wipe especially the boot and system] and try reflashing.
teh roxxorz said:
Idk why people are getting bootloops. Been on CM7 since 'nam and I'm currently on the same radio as the op for couple months now, and haven't experienced any issues.
I'd true flashing/using amon ra , EVERYTHING besides the sd card [wipe especially the boot and system] and try reflashing.
Click to expand...
Click to collapse
I'm not sure either. I've been using CM7 damn near since it came out for the Evo. I've never had any issues with bootlooping.
Concordium said:
I'm not sure either. I've been using CM7 damn near since it came out for the Evo. I've never had any issues with bootlooping.
Click to expand...
Click to collapse
Either he has a bad boot image or corrupted NV files, in which if the latter, his evo is toast.
teh roxxorz said:
Either he has a bad boot image or corrupted NV files, in which if the latter, his evo is toast.
Click to expand...
Click to collapse
Is there no way to overwrite NV files?
Concordium said:
Is there no way to overwrite NV files?
Click to expand...
Click to collapse
Nope, its read only. You can flash the NV like you do radios, though changing them, no.
That's lame
Update
Ok, I made some progress. Thanks for the help.
I flashed a new RUU and got myself back to a working ROM. However, the phone still randomly reboots.
I think that this is a hardware issue and not a result of something I did, as it was present in CM 7.1 when I first rooted the phone and before I did anything firmware related.
My plan is to return the phone as defective refurb since I only got it two days ago. To do that, I need to get S-on.
I've tried a couple of times with the gingerbread s-on tool, but it doesn't seem to work. Do you guys have any ideas about that? I've read all the threads about it, and people seem to suggest just running the tool a billion times until it works.
Concordium said:
IIRC you can't downgrade your radio. The newer radio versions wont allow downgrading. There have been a lot of people having the bootloop problem. And most of them seem to be running CM7. Not sure if you're in the bootloop of death or not. Hopefully someone else can chime in with more experience concerning this issue.
Click to expand...
Click to collapse
Well, I'm not sure if I managed to downgrade my radio or not. It showed it was downgraded in the HBOOT. In any case, I now have a 2.15.00.05.02 radio due to the RUU I flashed.
aeilos said:
Well, I'm not sure if I managed to downgrade my radio or not. It showed it was downgraded in the HBOOT. In any case, I now have a 2.15.00.05.02 radio due to the RUU I flashed.
Click to expand...
Click to collapse
To get s-on, you need to check your bootloader version, so you know what method to use.
I got s-on...not sure what I was doing wrong before but the revolutionary s-on tool worked. Maybe I was just tired. Flashed a PC36IMG.zip that had the tool, and it put s-on for me.
Should I flash another RUU? Also, do you think that the random reboots must be some kind of hardware issue?
aeilos said:
I got s-on...not sure what I was doing wrong before but the revolutionary s-on tool worked. Maybe I was just tired. Flashed a PC36IMG.zip that had the tool, and it put s-on for me.
Should I flash another RUU? Also, do you think that the random reboots must be some kind of hardware issue?
Click to expand...
Click to collapse
Well you should be stock now. Go a day on stock, take an OTA, and see if you get reboots. If so, you can rule it to be hardware.
What did you wipe between flashes? I wipe everything in the amon 2.3 wipe menu except sdcard. Never had a problem. Btw Idk what it is with cyanogen 7.1 but for me it was buggy rebooted every 20 min and force closes like it was its day job. But I have been running decks 1.3 which is based off of cm7.1 and its perfect in everyway. So.... might want to try this rom if you haven't. Just throwing it out there
Edit: nvm didn't see that you unrooted... my bad haha
Sent from my PC36100 using XDA App
I've been curious about the CM7 thing myself, as per the number of people that have gotten boot loops of death.
It may not even be due to CM7 and running it on those particular phones, but it is odd that so many cases have been while people were using that ROM
HipKat said:
I've been curious about the CM7 thing myself, as per the number of people that have gotten boot loops of death.
It may not even be due to CM7 and running it on those particular phones, but it is odd that so many cases have been while people were using that ROM
Click to expand...
Click to collapse
Yeah its pretty odd. Considering that the nightly builds were usually rock solid.
Sent from my PC36100 using XDA App
aeilos said:
I got s-on...not sure what I was doing wrong before but the revolutionary s-on tool worked. Maybe I was just tired. Flashed a PC36IMG.zip that had the tool, and it put s-on for me.
Should I flash another RUU? Also, do you think that the random reboots must be some kind of hardware issue?
Click to expand...
Click to collapse
Did you get it to work and not bootloop finally? I'm trying to fix my friends evo and it keeps doing the same thing. His was stock and just started doing it all of a sudden, so maybe it is a hardware issue.

Categories

Resources