Constant Reboot After Unrevoked3 - EVO 4G Q&A, Help & Troubleshooting

I'm not sure why it's rebooting. I've tried battery pull, factory reset, etc. NOTHING! Any other ideas?

Did you try to flash a rom? If you don;t have nand unlock, some (pretty sure it's mainly with kernel replacements) will put you in a boot loop.
Course, you said reboots...maybe you mean random and not constant.

yea it would start up...sometimes it would just restart itself as soon as it loaded up...other times it would work for alil while...then reboot itself...well i just tried completely restoring it. everything went back to stock. even went back to S-ON. i just rooted it again but used simple root this time. made sure all the drivers were installed right on my pc. so far so good. no random reboot yet. i'll flash a rom and see what happens.

update: nope...i installed fresh rom and it's rebooting...rebooted 4 times now.

snrbobo said:
update: nope...i installed fresh rom and it's rebooting...rebooted 4 times now.
Click to expand...
Click to collapse
Unrevoked3 doesn't unlock Nand, which some roms require. You can either use Toasts root method #2 or just flash Unrevoked Forever, which I did, and you should be good to go after that.

snrbobo said:
update: nope...i installed fresh rom and it's rebooting...rebooted 4 times now.
Click to expand...
Click to collapse
Did you wipe?
Flipzmode said:
A full data wipe is required. I recommend doing a full data wipe, then flashing the rom, then flashing the radio, then flashing the wimax radio (if you don’t already have the updated radios). I’ve also had the best luck with Facebook syncing properly by setting up my gmail account during the inital setup screen but not setting up Facebook until you have booted in to the OS.
Click to expand...
Click to collapse

i'm sorry, i did unrevoked forever afterwards too. but i just installed cm6 rc2. so far so good! whats weird is...it hasn't rebooted ever since i swamped sd cards. i even rebooted it myself and still no reboot. hopefully it stays this way

Related

all Roms lead to random reboots

recently, my phone has just started a habit of randomly rebooting. i was using myn rls5 with net kernel 4.3.2, but i decided to try something different in an attempt to stop the problem, so i went to mikfroyo with its default kernel. right after i startthe phone and it gets to the homescreen, it starts restarting again. i cleared data and cache between roms, and im using clockworkmod 3.0.0.5
You should always perform a full wipe, to include factory/data, when flashing a new rom.
teh roxxorz said:
You should always perform a full wipe, to include factory/data, when flashing a new rom.
Click to expand...
Click to collapse
i did. every time
ryohei47 said:
i did. every time
Click to expand...
Click to collapse
Also, the dalvik, under advanced? And not flashing a kernel with it?
I found out that Clockwork never cleared Dalvik for me. I changed to AR and after clearing the dalvik I stopped getting reboots or bootloops. Maybe your phone doesn't like the new Clockwork...
Shigster said:
I found out that Clockwork never cleared Dalvik for me. I changed to AR and after clearing the dalvik I stopped getting reboots or bootloops. Maybe your phone doesn't like the new Clockwork...
Click to expand...
Click to collapse
that could be it. everytime i install RA though, it complains and doesnt boot into recovery correctly
oohhh. that sucks. try unrooting or using a stock rom for a while. if it keeps rebooting when you browse the web, play games, anything that works the phone, then there is nothing you can do. the phone is fried. wait until it is bad enough that you can do it whenever you want by firing up a game and playing for a few minutes. then bring to the sprint store and they will replace. hah why do i have to be the person who brings the bad news?
again, try unrooting first. you can even leave s-off to re root easily. if you have no reboots, then the problem can be fixed.
i feel so bad giving this news... hah
My phone recently started doing this. Doesn't matter what ROM I'm on, doesn't matter if I un-root with a factory RUU or re-root, doesn't matter what recovery I use, doesn't matter if I completely format my SD card or boot without one. It got to the point I had to take it to Sprint and have them order me a new one.
It would randomly reboot and then go into a bootloop that not even a factory reset would cure, just decides when to stop bootlooping on its own and occasionally works.
ryohei47 said:
that could be it. everytime i install RA though, it complains and doesnt boot into recovery correctly
Click to expand...
Click to collapse
If you're using ROM Manager, don't! Download the PC36IMG.zip file from amon's thread and place it on the root of your SD card. Shutdown your device. While pressing the down arrow key, press the power button. You will then enter the bootloader screen. After a few seconds, a few lines of text will appear and the bootloader will automatically detect the. PC36IMG.zip file and prompt you to install it. Follow the prompts to install. The installation will take less than 10 seconds to complete. Afterwards, reboot into your new recovery. The recovery version will be listed at the bottom of the screen. Go to the wipe menu and wipe EVERYTHING except the SD card itself then go to the flash menu and flash whatever rom you wish to flash.
Posting & replying via the XDA Premium app
awesomeindeed said:
My phone recently started doing this. Doesn't matter what ROM I'm on, doesn't matter if I un-root with a factory RUU or re-root, doesn't matter what recovery I use, doesn't matter if I completely format my SD card or boot without one. It got to the point I had to take it to Sprint and have them order me a new one.
It would randomly reboot and then go into a bootloop that not even a factory reset would cure, just decides when to stop bootlooping on its own and occasionally works.
Click to expand...
Click to collapse
Were you one of the unlucky ones who were using CM7 when the bootlooping began?
Posting & replying via the XDA Premium app
dougjamal said:
Were you one of the unlucky ones who were using CM7 when the bootlooping began?
Posting & replying via the XDA Premium app
Click to expand...
Click to collapse
No, I had already moved away from CM7 when it began. It started out of nowhere and just got worse on a daily basis.
I had also never used Unrevoked. I rooted with toast's original root method way back last August or so and was using the .76 ENG bootloader.
I had similar issues, in terms of both posts, and it got to the point that I just got it replaced from Sprint. It just progressively got worse no matter what was done. Has happened to others ... sounds like the phone might just be going.
=(
sent from my
My new phone arrived today. It's a refurb. HW 0003. Made it about 2 hours without a random reboot. Made it about another 4 before doing it again. This sucks.
awesomeindeed said:
My new phone arrived today. It's a refurb. HW 0003. Made it about 2 hours without a random reboot. Made it about another 4 before doing it again. This sucks.
Click to expand...
Click to collapse
Damn, that sucks. Is that stock, before u even rooted it? I would just take it right back to Sprint.
Sent from my PC36100 using XDA App
k2buckley said:
Damn, that sucks. Is that stock, before u even rooted it? I would just take it right back to Sprint.
Sent from my PC36100 using XDA App
Click to expand...
Click to collapse
Yep, stock. Only apps installed are GoSMS and XDA. I guess I'll give it a factory reset and see if that fixes it, or else it's going back.
awesomeindeed said:
My new phone arrived today. It's a refurb. HW 0003. Made it about 2 hours without a random reboot. Made it about another 4 before doing it again. This sucks.
Click to expand...
Click to collapse
umm... might have been one of the 2 i got with that problem... srry!
i just hate unrooting, the whole process will end up taking a few hours. im probably gonna unroot, and if the basics work, i'll just stick with some simple z4 root and call it a day. any other options? cause htis is already my second phone, not exactly crazy about getting a third.
ryohei47 said:
i just hate unrooting, the whole process will end up taking a few hours. im probably gonna unroot, and if the basics work, i'll just stick with some simple z4 root and call it a day. any other options? cause htis is already my second phone, not exactly crazy about getting a third.
Click to expand...
Click to collapse
Unrooting take like 5 minutes...flash s-on tool, then the 5 minutes to run the ruu, then another 5 minutes to re-root.
ryohei47 said:
recently, my phone has just started a habit of randomly rebooting. i was using myn rls5 with net kernel 4.3.2, but i decided to try something different in an attempt to stop the problem, so i went to mikfroyo with its default kernel. right after i startthe phone and it gets to the homescreen, it starts restarting again. i cleared data and cache between roms, and im using clockworkmod 3.0.0.5
Click to expand...
Click to collapse
My phone never has random reboots. Never. And I have a list of roms as long as my arm that I have flashed.
HipKat said:
My phone never has random reboots. Never. And I have a list of roms as long as my arm that I have flashed.
Click to expand...
Click to collapse
There are a bunch of bad EVOs floating around. If you have this problem, you're more likely to get one of these as a refurb as they are the ones they get back. They'll replace the display, etc. But its the mobo that is probably the issue, and they don't replace that. They probably just make sure that it boots up and can make a call..
Sent from my PC36100 using Tapatalk

[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

Uber kingdom revo 3d rls7

Installed, went to reboot system, all it does it go to the htc incredible screen, reboot, htc incredible screen, then goes to recovery. wtf over?
so i formated the cache, dalvik, and fixed permissions and still no luck.
what do i do next?
I second this...
In fact, today was the very first day it wouldn't do that when I flashed a Sense 3.0 ROM... now it's back to not flashing them anymore.
They weren't kidding in the instructions where it says to wipe cache/data three times. I started from scratch, wiped everything a bunch of times, reinstalled and it worked. My phone is very picky, because when I flash any ROM, it will never load the first time unless I go back and re-wipe everything. It's a pain, but it's a nice rom. Only thing i found that doesn't work is the flash on my camera, and the flashlight.??
RMinor205 said:
They weren't kidding in the instructions where it says to wipe cache/data three times. I started from scratch, wiped everything a bunch of times, reinstalled and it worked. My phone is very picky, because when I flash any ROM, it will never load the first time unless I go back and re-wipe everything. It's a pain, but it's a nice rom. Only thing i found that doesn't work is the flash on my camera, and the flashlight.??
Click to expand...
Click to collapse
What version of Clockworkmod are you using?
I had made sure I had done it several times.... and it's very arbitrary to be honest it seems whether a ROM will flash or not. RLS7 seems to flash just fine... but I can't get .5 on there again... I'll see what I can do..
Yeah... so apparently my phone is an exception of sorts... it seems like I've been having trouble flashing any sort of Gingersense ROM... but I am able to get RLS7 onto my phone. It's booting now. But I can't for the life of me seem to be able to get .5 on there. What's the difference anyways? Anyone.\lol
**By the way, I am 100% sure I wiped everything 3 times... and it would still get stuck on splash screen.
BrettApple said:
What version of Clockworkmod are you using?
Click to expand...
Click to collapse
3.0.0.8
i'm going to update to RLS 0.5... maybe. Just to see if that fixes the bug.
It says "flash disabled due to cold weather, low battery, or use of an app that uses a lot of battery power".
I live in Florida, have a full battery, and haven't re installed any apps.
Installing 0.5 - hopefully it worked.
Wiping several times DOES NOTHING. No matter if you say it did or not. The way to fix that, as I have had it happen is simply flash the rom again without wiping. So, say you wipe and flash, reboot, it goes back to recovery, just install zip again.
I also have the "flash disabled due to cold weather, low battery, or use of an app that uses a lot of battery power". Full battery, no high power apps running.

[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] Serious (BIG) problem with DHD. No GUI, can't even finish setup.

So 2 days ago a friend bought an HTC Desire HD. It was working fine, but since it was second hand he wanted to hard reset it, and so he did. After he did that it started doing what I am showing in the video below(but it was with an older version, gingerbread I think). It was also going in CWM 10 sec after it was put into a charger. After I tried installing custom roms and roots, I installed what is said to be a stock ruu:
RUU_Ace_Sense30_S_HTC_WWE_3.12.405.1_Radio_12.65.60.29_26.14.04.28_M_release_225512_signed
Click to expand...
Click to collapse
It is obviously(visually) a newer version of the software the phone uses, than the one it had when he first gave the phone to me.
Nothing seems to have worked at this point, I'm desperate. After that 4th option of the setup(scheduled sync) it just goes black screen with a status bar and nothing. When he first gave it to me it used to display an error that said something like setup couldn't load, and with options to close it, wait for it, or tell HTC about it. It CAN receive SMS and calls, but there just isn't any GUI(menu, or whatever it's called).
I'm also providing a picture of the bootloader below.
I don't need the phone to be rooted or with any particular ROM or version, I just need it working normally.
Any help/assistance will be welcome! Thanks in advance
VIDEO:
youtube.com/watch?v=aNI1t4KjY-0&feature=youtu.be
youtube.com/watch?v=aNI1t4KjY-0&feature=youtu.be
Just makes it easier to click on it. :beer:
Edit: Try booting without the sd card, but aside from that, no idea.
You can also try flashing a stable gb rom see if you get the same issue.
Sent from a dream.
<-------- new user here. cant post links thanks
iLoveAlkohola said:
<-------- new user here. cant post links thanks
Click to expand...
Click to collapse
If you already have s-off and cwm, why not just flash rooted stock rom? It should work fine if the rom can be flashed successfully.
If it is not, it is most probably hardware issues, although i am not so sure myself.
yumm91 said:
If you already have s-off and cwm, why not just flash rooted stock rom? It should work fine if the rom can be flashed successfully.
If it is not, it is most probably hardware issues, although i am not so sure myself.
Click to expand...
Click to collapse
As I said, before installing the newest stock ruu(with which I lost cwm and can''t seem to get it back), I installed some custom roms, all of them with the same effect. But thanks for the suggestion.
iLoveAlkohola said:
As I said, before installing the newest stock ruu(with which I lost cwm and can''t seem to get it back), I installed some custom roms, all of them with the same effect. But thanks for the suggestion.
Click to expand...
Click to collapse
Make a full wipe before flashing the Ruu. Flash a custom recovery in fastboot, do a full wipe, then flash a ROM (stock or custom) To see what happens
Already did all that. When I first got the phone I used the full wipe function of cwm(and of the stock recovery) a couple of times, but every time it was stuck at that point of the initial setup with the error showing up.
Is there a file SPECIFICALLY for the initial setup that I can flash to the phone, because I flashed different recoveries, roms, boots and even radios manually before installing the stock ruu. I haven't set up a phone before, so I'm not sure, but as I can see there are still 2 or 3 options left to select ,after that scheduled sync option, before the phone could run the main menu(gui or whatever).
Oh, and btw, when I updated it with that ruu, the setup visually changed and by that I figure out it gets flashed as part of the ruu, but still with the same problem. Can it be some kind of hardware problem of the internal memory? No matter how much I searched and where I looked I never found someone with a problem even close to this one.
Teichopsia said:
Edit: Try booting without the sd card, but aside from that, no idea.
You can also try flashing a stable gb rom see if you get the same issue.
Sent from a dream.
Click to expand...
Click to collapse
Whatever I was doing to the phone it didn't usually have an sdcard in it and was booting without an sd card, tried with and without, no changes.
After I installed that sense ruu i can't seem to get back to gb, any ideas how to do it? I also can't get cwm to work now, even though it flashes without any error or problem I can only ge the htcdev root(already did) with this ruu, I think but I don't get any changes except that there is a watermark on the first line of bootloader.

Categories

Resources