So what happens if you change the splash screen and then get hit by this bug? You're screwed right? It's a dead giveaway that your phone was rooted at some point.
There won't be a custom splach screen, just the white HTC EVO 4G over and over. The only way someone would know you were rooted is by s-off or seeing the red revolutionary. That's why it's crucial to get s-on before taking it in to Sprint
do I understand correctly that this may be an issue with the version of radios? And the newest version is the suspect?
I upgraded to the new radios but haven't seen where it did me any good, or bad, for that matter. I wonder if it would hurt anything to flash older radios back to my phone.
I have heard of the Sprintlovers rom that i seem to understand also flashes your radios. Is that correct? What version were they in that rom? would it be a problem to flash that rom at this point? would it change my radios to an older version again?
that being said, if I understood correctly, a rom CAN change your radios. I am sure these CM guys are way more knowledgeable than I am, wouldn't they know if their code had the potential of messing them up?
What would be the pros and cons of flashing older radios?
I'm not totally sure if the radios or wimax or NV.... changes causes the death boot. I'm just curious as to what radios people were on so maybe we can pinpoint the reasoning for the death boot. If people remember Virus's early Kingdom rom required to flash the 1.77 PRI, maybe if we can figure what's the cause for the death boot and if there's any correlation to the radios or if it's sincerely just bad luck
No this issue reared its head before the current radio version
probably true but it seems that the death boot is rearing it's ugly head more and more often. Again, that's why I'm curious if this could be something more with the radios..... and not the rom.
Ok, reading through this thread has me scared. Thanks to the OP for letting all of us readers know what happened and how you got a replacement.
But now I am thinking the same thing MizzouBrent is -- I've flashed a different splash screen as well. Would it be prudent to flash a stock one, or since we flash those in bootloader/as PC36IMG files, can we hope to be able to replace it without getting into recovery if we hit this bad luck?
I mean, I should be prepared if this is a CM issue, because you know I won't be able to resist flashing CM9.
If the death boot rears its ugly head, unfortunately without a known solution, there will be nothing you can do
So......flash away
but come on, though. i may sound like a dick, but getting a replacement evo doeznt really fix the problem or go towards fixing this issue, does it?
The unlucky few who simply can't bring this fon to sprint(such as myself) are still interested in finding out what can be done.
i started a thread on this exact problem n never found a solution.
now im on da latest ruu, stuck on s-off, but able to change splashscreens, etc, but da damn fon just won't boot :'(
You can't change the splash screens can you? I don't think this is possible without a working recovery
Andy was on miui when his went down. Really sucks for all that had the death boot strike their piece down. I'd cry...seriously weep like a little girl.
Thanks Granite
yes, I was on MIUI. I did weep for a little while but after I got my replacement, I rooted it within a couple of hours
By all means if there was a real solution to the problem that was known about we would provide it, but at this point theres nothing you can do but get another phone
+1
No known solution to the problem at this point
I remember hearing about this a while back. Scary. I'll probably be leaving CM7 because my paranoia is increasing.
I wouldn't be too concerned but I'm like you, I will probably NOT flash MIUI anytime soon. But I will be flashing ICS AOSP roms so hopefully the death boot will not happen again
there are plenty of cm7 users who never had this issue and there are plenty of sense users who experience hardware failure. You just never know.
My guess is that the death boot is affecting very few phones but again I would like to know if there's any sort of correlation to death boot to the radios. Also, I haven't totally ruled out the sbc kernel but........
Well, I have been reading alot about this to and it has been happening to random CM7 users but it has happened to others also, maybe not as often but it has. I to am a bit nervous I have CM7.1 on and I love it and the other day it got hung up for a sec and rebooted and I thought Uh-Oh but it came back up just fine and now everytime I am gonna reboot I get nervous.
My question would be how many using cm7 are having this problem, and how long had they been running it? Was it CM7, or CM7.1 or both? Had you experienced any other problems, however minor, before hand?
My experience in telecommunication and sat. communications, in the past has shown that all soft loops(loops caused by software glitch i. e. ROM or Kernel, even stubborn ones) are fixable or can be unlooped. Here i would question the kernel before the ROM since kernel control voltages and voltages control switches and switches allows things to flow etc. etc. Now why I would question the kernel is voltages, this could cause spikes or undervolts that the hardware may not like, though it may tolerate it for a bit it can be bad in the long run. That is one reason why I would ask how long were you running before the loop?
An example of a very stubborn software loop existed in Direct TV cards back in 2002. Actually DTV sent down a code to put hacked cards into a loop though it affected some legit cards to,. The cards would not go past the boot sector. DTV did this in hopes of catching hacked cards from those dumb enough to send them back for repleacement. They could get them unlooped and retrieve the code off the cards therefore also helping combat the hacking of the cards. The solution was like a brute force hack. The cards had to be bombarded with different data sequences or hexadecimals which eventually cause it to pop.
I'd be interested in buying the bricked/bootlooped phone to play with it.
I believe the sbc kernel that I was using still could be a possibility but who knows. You are more than welcome to have my death boot phone but if you have any suggestions as to what else anyone can do let me know. I will be more than happy to try anything. I would love to find the solution to this death boot issue
Sorry don't mean to ramble on but here are a cuple other things to consider. First I have noticed CM7.1 loads its own kernel, Does CM7 also??
Second, those that have gone into loop, how well did they wipe the system before they loaded?
Had they gone from a sense ROM to CM7? Had they continually been changing ROMs or Kernels or messing with Kernel settings?
Had they been using various scripts or not? Downloading numerous apps??
Those with the problem should share all info, there might be one tiny common thing that could give the developers a hint to a possible fix as long as it is not a harware problem.
1. CM7 and CM7.1 has the same kernel
2. Believe me, I wipe everything before messing with a new rom
3. I don't believe going from a sense rom to an AOSP rom would cause the death boot issue but who knows
4. Changing roms and kernels? Are you new here?
Flashing roms and kernels is the business of a rooted phone
5. I didn't use any specific scripts at the time. 10/14 MIUI build with the Tiamat 4.1 sbc kernel.
6. I usually have around 35-40 applications installed on the phone
7. I was on the latest radio, wimax.... from Calkulin's thread on xda.
So to sum up, I don't know a solution but I will gladly take any suggestions as I still have my death boot phone and I'm continually trying things to try and find a solution
