Related
ok, guys... something is totally effed up with my evo. i was trying to reroot after doing a factory reset, but now all it does is reboot from the "htc evo 4g" screen constantly. it won't even bring up sprint's 4g boot screen...
please help!
nothing?? =/
trying to do a factory reset through the android os? I dont think that takes away root. But in any case, can you still manage to get into recovery? If so you could do a nandroid restore, or flash a new rom
elegantai said:
trying to do a factory reset through the android os? I dont think that takes away root. But in any case, can you still manage to get into recovery? If so you could do a nandroid restore, or flash a new rom
Click to expand...
Click to collapse
it's weird. i tried that. it's still loops. i tried to do a nandroid restore as well, no success. i flashed dc 3.2.3 (what i was on previously) with no success.
it just loops with the htc evo 4g logo screen and then powers off and then repeats. i even tried a different microsd card, but again, no success.
Have you tried wiping cache, or even full data/cache/dalvik and then flashing a rom?
elegantai said:
Have you tried wiping cache, or even full data/cache/dalvik and then flashing a rom?
Click to expand...
Click to collapse
i'm on my 5th attempt right now...
aaaand... nope, no success.
So all you did is do a factory reset from the settings and it started boot looping? Is your recovery method up to date (if clockwork)
elegantai said:
So all you did is do a factory reset from the settings and it started boot looping? Is your recovery method up to date (if clockwork)
Click to expand...
Click to collapse
yea, i wanted to reroot it and apply a new rom. i use amon ra recovery. it was up-to-date, from what i understand.
Well crap! The only thing I can recommend is to use the starting over guide, possibly trying to use a ruu to return it to stock and the try rerooting and flashing a new Rom
Just so I can sleep comfortably tonight, you were just rerooting for fun? Because you know you don't have to reroot to flash a new Rom correct?
elegantai said:
Well crap! The only thing I can recommend is to use the starting over guide, possibly trying to use a ruu to return it to stock and the try rerooting and flashing a new Rom
Just so I can sleep comfortably tonight, you were just rerooting for fun? Because you know you don't have to reroot to flash a new Rom correct?
Click to expand...
Click to collapse
trying to use a ruu would work, if i could only boot up, which i can't =/
and yea, i wanted to get a better feel for rooting. i know i don't have to reroot, i just wanted to wipe everything and start fresh, you know, wipe the slate clean. i'm trying the recovery-windows.bat batch file now. worst scenario, i'll go to sprint tomorrow and try to get a replacement.
still, thanks for the help man!
Hmm, do you think there is a possibility you could have used the wrong image when you were trying to reroot? Or if you didn't get that far, starting at toast part 2 might get you out of the loop.
I'm sure you'll get it though!
elegantai said:
Hmm, do you think there is a possibility you could have used the wrong image when you were trying to reroot? Or if you didn't get that far, starting at toast part 2 might get you out of the loop.
I'm sure you'll get it though!
Click to expand...
Click to collapse
it's entirely possible i may have used the wrong image. i'm trying to see what this batch file will do, though it's been hung for quite some time. i tried doing toast's part 2, i got the error that the sdcard folder doesn't exist... when it was already mounted lol.. something funky is going on.
thanks i hope so...
having the same problem tried to go back to stock so i could exchange the phone. now i am stuck with the reboot loop also. if anyone figures out what to do would really love the help.
i let the recover-windows.bat batch file run overnight and it seems to be stuck at this spot:
C:\Android SDK\android-sdk-windows\tools\evo-recovery>adb-windows.exe shell nohu
p /sbin/recovery
nohup: appending output to nohup.out
i ran it while i was in recovery, and the recovery menu is weird, switching between the main menu and sub menus if i use the volume rocker to move up and down the selections... i think i'm going to go to the sprint store, act stupid, and try to get a replacement.
i bought mine at bestbuy so sprint wont look at it. until my 30 days is up with bestbuy. and cant get a replacement at bestbuy since they are out of stock. hopefully someone can fix this problem. because right now iam sol.
I have absolutely no idea what would cause this, I will try searching around to see if a similar problem was resolved. I just can't believe that it won't let you do anything from recovery. Have you guys tried a different Rom, maybe stock Rom before root? Clueless, I am hoping someone will chime in with something else to try.
Can you still remount the system as rw? Using the command: adb remount rw?
If so maybe try flashing the recovery, wiping, and then flash a stock rom?
elegantai said:
I have absolutely no idea what would cause this, I will try searching around to see if a similar problem was resolved. I just can't believe that it won't let you do anything from recovery. Have you guys tried a different Rom, maybe stock Rom before root? Clueless, I am hoping someone will chime in with something else to try.
Click to expand...
Click to collapse
it's really weird. i can't get past initial boot. i went to the sprint store and they're out of stock, so i have to wait a few days
in the meantime, i'm going to try and continue to force my will onto my evo lol. this is heartbreaking...
do you know where i can find a stock rom unroot? like a zip file? maybe that'll work? i doubt it, but worth a shot.
Yea let me get the link. Will edit...
Here is a cache of the wiki, it has links for Stock rooted roms which I would give one of those a shot. I can only find the unrooted in an exe form. I am not sure but in the boot screen you could try fast boot usb and see if the exe would run that way but I am entirely unsure about that
http://webcache.googleusercontent.c...iki&cd=1&hl=en&ct=clnk&gl=us&client=firefox-a
Also, did you see if your nand was still unlocked? And did you try reflashing recovery? Not sure, just throwing ideas out there!
elegantai said:
Yea let me get the link. Will edit...
Here is a cache of the wiki, it has links for Stock rooted roms which I would give one of those a shot. I can only find the unrooted in an exe form. I am not sure but in the boot screen you could try fast boot usb and see if the exe would run that way but I am entirely unsure about that
http://webcache.googleusercontent.c...iki&cd=1&hl=en&ct=clnk&gl=us&client=firefox-a
Click to expand...
Click to collapse
awesome! thanks!..
at this point, i'm willing to try any and all voodoo tricks as well to get my baby up and running. i'll update with what happens.
edit. no success still... i'm trying all versions of exe files.
Since you can boot into recovery, amon ra will let you mount your sdcard as a drive into windows where you can download the stock 1.47 RUU and copy it into the root of your sdcard. Once you do that, unmount via the recovery menu and wipe data/dalvik and then flash the ruu to try and get it to boot. You shouldn't need to boot fully to flash the ruu. Find the starting over post by whitslack to get the ruu.
Sent from my PC36100 using XDA App
Can someone please tell me how long a nandroid restore can take as a maximum?
I am running a nandroid restore as I type.
From CM6 RC1 with snap kernel
To Nandroid back up of Fresh 3.1.0.1.
It's been going for 2+ hours, the dots are still progressing but this seems like its taking longer than it should.
Question: Is this amount of time a sign that something is severely wrong?
How can I correct the issue? What will a battery pull do to my device?
Update: Battery pull did the job and my phone isn't bricked.
Shouldn't take that long.. I've done dozens of restores and most it took was 10 minutes or so.
Pull the battery and try again.. might be a r/w issue with the card.. You should still be able to get to recovery.
did you do the backup with clockwork, and trying to restore with RA, or the other way around? I heard that can cause issues.
yep, 10 minutes is the longest I've ever had one go. Also, fwiw, it always seems to finish somewhere around the fifth line of dots..
fachadick said:
did you do the backup with clockwork, and trying to restore with RA, or the other way around? I heard that can cause issues.
Click to expand...
Click to collapse
Nope, all done with Amon. Still not sure what the issue was. Resolved, I just flashed the rom again instead.
Last night after i did my nightly backup, i noticed that i couldn't exit the menu. After i did a backup, no buttons will work. I had to do a battery pull. I did three different backups, having to do a battery pull each time. Menu works fine, until i do the backup. It even says backup complete. The 3rd time i deleted the nandroid folder before running the backup, yet the problem is still there. I'm using the org HBOOT 0.76 eng, AMON_RA 1.8.0, CM 6.1.1, Zendroid kernel. Only thing i can think of is re-flashing the recovery and formatting the card. Anyone had this happen before???
Formatting the card did nothing. Re-flashed recovery did nothing. Any ideas???
You do a backup every night? Dang! I only one every couple weeks...
-Z
zzelinka said:
You do a backup every night? Dang! I only one every couple weeks...
-Z
Click to expand...
Click to collapse
Yea i do, i keep only the last 4 though. Just thought i would update this in-case it happens to someone else. To fix this, i had to repartition my sdcard in recovery, then reinstall my ROM. I guess what happen was when i installed the ROM on the new sdcard, without partitioning the new sdcard, it installed it wrong. This was causing the error.
This is one of the cases where your program failed working and is frozen like out of battery kinda fishy thingy there, I wish I could explain but It's bad mojo jojo.
I don't even use backups on my SDCARD, i put them on my computer, then switch roms/kernels with my pc on to my phone EVO. :/
THat sucks, sorry bro.
i dont have that problem with my nandroid backups but i keep gettin restore via adb on them...i keep about 3roms backed up on my card and this keeps happening...anyone have any ideas how to fix?
I'd try asking over the in Amon_RA recovery thread or you can @Amon_RA on Twitter. I've honestly never heard of or seen this issue.
Sounds like something is over-writing your recovery. "The moving over writer having writ moves on."
So start with all new "stuff" (os, recovery,downloads)
The recoveries are not very good about telling you what the Nandroid error was. You should run it via adb just as described:
adb shell
nandroid-mobile.sh -b (or I think -r for restore?)
Then you get a much better idea of what's going on. Happened to me once because my battery was too low to do a backup; recovery didn't tell me why, but running it from the shell did.
bwcorvus said:
To fix this, i had to repartition my sdcard in recovery, then reinstall my ROM. I guess what happen was when i installed the ROM on the new sdcard, without partitioning the new sdcard, it installed it wrong. This was causing the error.
Click to expand...
Click to collapse
Already fixed but thank you all
what was the issue? so others can find out as well.
Hey guys, I was wondering if you all could help me with an issue I've been having lately.
For some reason, I can't flash any ROMs. When I do, it hangs and hangs and hangs on the Splash Screen. It hasn't always been this way, everything worked just fine until last month I flashed MIUI. It worked, but after I decided I didn't like it, I couldn't flash any new ROM, and none of my backups worked until I wiped data and what not.
I've reformated my SD card, and I still can't flash any new ROMs. Help?
I'm kind of worried that if I decide to flash the stock 2.3 update when it comes, I'll brick my phone.
I struggled with my phone for three days trying to flash roms recently. At one point I went to an older version of CWM 3.0.0.5 and it worked once, but then it stopped flashing again.
Tried Amon_Ra and didnt have any luck either due to signatures or something. Went back to CWM 3.0.0.8 and havent had any problems since. CWM must be messing up every once in a while or something.
Good Luck
Sorrows said:
Hey guys, I was wondering if you all could help me with an issue I've been having lately.
For some reason, I can't flash any ROMs. When I do, it hangs and hangs and hangs on the Splash Screen. It hasn't always been this way, everything worked just fine until last month I flashed MIUI. It worked, but after I decided I didn't like it, I couldn't flash any new ROM, and none of my backups worked until I wiped data and what not.
I've reformated my SD card, and I still can't flash any new ROMs. Help?
I'm kind of worried that if I decide to flash the stock 2.3 update when it comes, I'll brick my phone.
Click to expand...
Click to collapse
I've had the same problem then someone suggested I flash a temporary 2.x clockworkmod to whipe bc clockworkmod 3.x has reported issues of not wiping completely.
Here's the zip I used, flashing will temporarily give 2.5.1.2. When you reboot, it will be back to whatever you had before. Also try repeatedly wiping data, cache, dalvik 3x or more. Hope this helps
http://forum.xda-developers.com/attachment.php?attachmentid=549325&d=1300835217
MojoRisin011 said:
I've had the same problem then someone suggested I flash a temporary 2.x clockworkmod to whipe bc clockworkmod 3.x has reported issues of not wiping completely.
Here's the zip I used, flashing will temporarily give 2.5.1.2. When you reboot, it will be back to whatever you had before. Also try repeatedly wiping data, cache, dalvik 3x or more. Hope this helps
http://forum.xda-developers.com/attachment.php?attachmentid=549325&d=1300835217
Click to expand...
Click to collapse
And that could cause it to hang on the Splash Screen?
Sorrows said:
And that could cause it to hang on the Splash Screen?
Click to expand...
Click to collapse
I'm just speaking from personal experience.. it can't hurt.
Is your hboot version .92?
Sent from my ADR6300 using XDA App
INCREDIBLEC XD SHIP S-OFF
HBOOT-0.92.0000
MICROP-0417
TOUCH PANEL-ATMELC03_16ac
RADIO-2.15.00.07.28
And it could hurt actually, because it is incredibly difficult for my phone to restore even.
Also, I can't flash the alternate recovery for some reason. Every time I try, it says there was an error.
Sorrows said:
INCREDIBLEC XD SHIP S-OFF
HBOOT-0.92.0000
MICROP-0417
TOUCH PANEL-ATMELC03_16ac
RADIO-2.15.00.07.28
And it could hurt actually, because it is incredibly difficult for my phone to restore even.
Also, I can't flash the alternate recovery for some reason. Every time I try, it says there was an error.
Click to expand...
Click to collapse
You know.. its interesting that you mention this..
I have been following the CM7 nightlies for a while, and got fed up at one point and just stuck with one of there nightlies. Well... I noticed I couldn't flash ANYTHING at one point. Couldn't upgrade the kernel, radio, ROM... it would all cause it to hang up at the boot screen. I had to get EVERYTHING back to exactly how it was and then restore the most recent image I had created. It's the only thing that will work on my phone as of now. I wonder what happened, I feel like the phone lost its writing ability or something..
I had a similar problem a while back. I had a 2GB laying around as a spare, made sure it was formatted on my comp FAT32 and then put whatever ROM I wanted on it and tried it from there. It stopped the looping issues I was having. So I saved all my stuff from my daily SD card (16GB) and formatted that and put it back in the Inc and I haven't had a problem since. Maybe try a new SD?
Hypcrsy said:
I had a similar problem a while back. I had a 2GB laying around as a spare, made sure it was formatted on my comp FAT32 and then put whatever ROM I wanted on it and tried it from there. It stopped the looping issues I was having. So I saved all my stuff from my daily SD card (16GB) and formatted that and put it back in the Inc and I haven't had a problem since. Maybe try a new SD?
Click to expand...
Click to collapse
Your right, I think I'm going to try another SD card... or back this one up and format it...
But the weird thing is I can flash tweaks to the ROM, but I can't change kernels, ROM, radio.... without it getting stuck on the splash screen...
But I'm gonna go ahead and try another SD, because I had another SD that messed up on me, and it gave me similar issues. I just haven't had any problems with this one... so yeah.
If that doesn't work, you might try doing an RUU completely back to stock. then try flashing a new ROM.
Good luck!
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.